diff --git a/locale/ar/LC_MESSAGES/administration.po b/locale/ar/LC_MESSAGES/administration.po index 4ce4581b5..b53c877b7 100644 --- a/locale/ar/LC_MESSAGES/administration.po +++ b/locale/ar/LC_MESSAGES/administration.po @@ -9060,6 +9060,10 @@ msgid "" "`General Data Protection Regulation page `_ to " "learn more about how Odoo handles your data and privacy." msgstr "" +"The Upgrade platform follows the same `Privacy Policy " +"`_ as the other Odoo.com services. Visit the " +"`General Data Protection Regulation page `_ to " +"learn more about how Odoo handles your data and privacy." #: ../../content/administration/upgrade.rst:92 msgid "" diff --git a/locale/ar/LC_MESSAGES/finance.po b/locale/ar/LC_MESSAGES/finance.po index e0081955e..f6f08297e 100644 --- a/locale/ar/LC_MESSAGES/finance.po +++ b/locale/ar/LC_MESSAGES/finance.po @@ -35268,7 +35268,7 @@ msgstr "External reverse charge" #: ../../content/applications/finance/fiscal_localizations/italy.rst:387 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:212 msgid "Invoices" -msgstr "الفواتير" +msgstr "فواتير العملاء " #: ../../content/applications/finance/fiscal_localizations/italy.rst:158 msgid "" @@ -42722,14 +42722,6 @@ msgstr "" ":guilabel:`Connect to HMRC`. Enter your company information on the HMRC " "platform. You only need to do it once." -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "Periodic submission to HMRC" diff --git a/locale/ar/LC_MESSAGES/marketing.po b/locale/ar/LC_MESSAGES/marketing.po index 68e69e5a8..db8fe3cd0 100644 --- a/locale/ar/LC_MESSAGES/marketing.po +++ b/locale/ar/LC_MESSAGES/marketing.po @@ -3438,7 +3438,7 @@ msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:168 msgid "Activity and applied filters" -msgstr "" +msgstr "الأنشطة والفلاتر المستخدَمة " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:170 msgid "" @@ -3446,6 +3446,9 @@ msgid "" "Activities` pop-up form, there is the :guilabel:`Activity Filter` and " ":guilabel:`Applied Filter` fields." msgstr "" +"عند الانتقال إلى قسم :guilabel:`النطاق` في الاستمارة المنتبثقة " +":guilabel:`إنشاء أنشطة`، هناك حقلان :guilabel:`فلتر النشاط` و " +":guilabel:`الفلتر المستخدَم`. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:173 msgid "" @@ -3454,6 +3457,9 @@ msgid "" "activities. In works in the same fashion as a typical target audience " "filter." msgstr "" +"يمنحك حقل :guilabel:`فلتر النشاط` خيار تهيئة النطاق لفلتر المستلم الذي ينطبق" +" على هذا النشاط *بالإضافة إلى* أنشطته الفرعية. إنه يعمل بنفس الضريقة التي " +"يعمل بها فلتر الفئة المستهدَفة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:177 msgid "" @@ -3461,18 +3467,23 @@ msgid "" ":guilabel:`Activity Filter` field and proceed to configure a custom activity" " filter equation rule(s)." msgstr "" +"لإضافة فلتر نشاط، اضغط على :guilabel:`إضافة شرط` في حقل :guilabel:`فلتر " +"النشاط` وقم بتهيئة قاعدة (قواعد) معادلة فلتر مخصصة للأنشطة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 msgid "" "How to add an activity filter to a workflow activity in Odoo Marketing " "Automation." msgstr "" +"كيفية إضافة فلتر نشاط إلى نشاط سير عمل في تطبيق أتمتة التسويق لدى أودو. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:184 msgid "" "This option is not a required field. If left alone, the activity applies to " "all records related to the target audience of the overall campaign." msgstr "" +"هذا الخيار ليس حقلاً مطلوباً. إذا تركته وشأنه، سينطبق النشاط على كافة " +"السحلات المتعلقة بالفئة المستهدَفة في الحملة بأكملها. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:190 msgid "" @@ -3481,6 +3492,9 @@ msgid "" "specified domain (e.g. the rules configured in the :guilabel:`Activity " "Filter` field)." msgstr "" +"لا يمكن تهيئة حقل :guilabel:`الفلتر المطبق`. إنه ملخص لموعد أداء النشاط، " +"*فقط* إذا كان يتوافق مع النطاق المحدد (مثال: القواعد التي قد تمت تهيئتها في " +"حقل :guilabel:`فلتر النشاط`). " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:195 msgid "" @@ -3491,10 +3505,15 @@ msgid "" ":guilabel:`Discard` to delete the activity and return to the marketing " "automation campaign form." msgstr "" +"بعد أن تتم تهيئة إعدادات النشاط بشكل تام، اضغط على :guilabel:`حفظ وإغلاق` " +"لحفظ النشاط والرجوع إلى استمارة حملة أتمتة التسويق، ثم اضغط على " +":guilabel:`حفظ وإنشاء جديد` للحفظ وإنشاء واحد جديد على الفور في نافذة منبثقة" +" جديدة لـ :guilabel:`إنشاء أنشطة`، أو :guilabel:`إهمال` لحذف النشاط والعودة " +"إلى استمارة حملة أتمتة التسويق. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:202 msgid "Workflow activity" -msgstr "" +msgstr "نشاط سير العمل " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:204 msgid "" @@ -3503,10 +3522,13 @@ msgid "" "automation campaign form. The analytics related to each activity is " "displayed as a line graph." msgstr "" +"بمجرد أن قد تم إنشاء وحفظ النشاط، سيظهر كبطاقة نشاط في قسم :guilabel:`سير " +"العمل` الموجود أسفل استمارة حملة أتمتة التسويق. يتم عرض التحليلات المتعلقة " +"بكل نشاط كرسم بياني خطي. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 msgid "Typical workflow activity in Odoo Marketing Automation." -msgstr "" +msgstr "نشاط سير عمل تقليدي في تطبيق أتمتة التسويق لدى أودو. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:212 msgid "" @@ -3514,6 +3536,8 @@ msgid "" "the left of the :guilabel:`Workflow Activity` card in the " ":guilabel:`Workflow` section." msgstr "" +"ستجد وقت :guilabel:`التشغيل` لذلك النشاط إلى يمين بطاقة :guilabel:`نشاط سير" +" العمل` في قسم :guilabel:`سير العمل`. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:215 msgid "" @@ -3521,6 +3545,8 @@ msgid "" ":guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to " "the right of the graph." msgstr "" +"عندما يتم تشغيل النشاط، سيتم عرض رقم يمثل عدد الأنشطة :guilabel:`الناجحة` أو" +" :guilabel:`المرفوضة` إلى يسار الرسم البياني. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:219 msgid "" @@ -3530,10 +3556,15 @@ msgid "" " percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, " "or :guilabel:`Bounced`." msgstr "" +"إذا تم تعيين :guilabel:`نوع النشاط` لـ :guilabel:`البريد الإلكتروني` أو " +":guilabel:`الرسائل النصية القصيرة`، ستكون هناك تحليلات تفصيلية أكثر تحت " +"بيانات الرسم البياني للنشاط، توضح عدد الرسائل التي قد :guilabel:`تم " +"إرسالها`، ونسبة الرسائل التي :guilabel:`تم الضغط عليها` من بين الرسائل " +"المرسلة، أو :guilabel:`تم الرد عليها` أو، :guilabel:`المرتدة`. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:225 msgid "Child activities" -msgstr "" +msgstr "الأنشطة التابعة " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:227 msgid "" @@ -3541,6 +3572,9 @@ msgid "" ":guilabel:`Add child activity`, located at the bottom of each activity block" " in the :guilabel:`Workflow` section of a marketing campaign form." msgstr "" +"هناك أيضاً خيار إضافة *نشاط تابع* عن طريق الضغط على زر :guilabel:`إضافة نشاط" +" تابع`، الموجود أسفل كل مربع نشاط في قسم :guilabel:`سير العمل` في استمارة " +"الحملة التسويقية. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:231 msgid "" @@ -3549,10 +3583,13 @@ msgid "" "activity is easy to recognize, as its slightly indented beneath its parent " "activity." msgstr "" +"الأنشطة التابعة هي أنشطة فرعية متصلة بالنشاط الذي يعلوها ويتم تشغيلها فور " +"انتهائه، والذي يُعرَف بـ *النشاط الأساسي*. من السهل تمييز النشاط الفرعي، حيث" +" إنه يدنو النشاط الأساسي بقليل. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 msgid "A typical child activity indented beneath its parent activity." -msgstr "" +msgstr "نشاط تابع عادي يدنو النشاط الأساسي. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:239 msgid "" @@ -3561,68 +3598,88 @@ msgid "" "activity. Under the desired parent activity, hover over :guilabel:`Add child" " activity`, to reveal a menu of child activity trigger options." msgstr "" +"يوفر أودو العديد من خيارات التشغيل لتفعيل نشاط تابع - يعتمد ذلك على تهيئة " +"المشغلات المتعلقة بالنشاط الأساسي. تحت النشاط الأساسي المطلوب، قم بالتمرير " +"فوق :guilabel:`إضافة نشاط تابع`، لإظهار قائمة من خيارات مشغلات الأنشطة " +"التابعة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 msgid "" "The various child activity trigger options in the workflow section of a " "campaign." -msgstr "" +msgstr "خيارات مشغلات الأنشطة التابعة في قسم سير عمل الحملة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:247 msgid "Select any of the following child activity triggers:" -msgstr "" +msgstr "قم بتحديد أي من مشغلات الأنشطة التابعة التالية: " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:249 msgid ":guilabel:`Add Another Activity`: instantly adds another activity." -msgstr "" +msgstr "يؤدي :guilabel:`إضافة نشاط آخر`: إلى إضافة نشاط آخر فوراً. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:250 msgid "" ":guilabel:`Opened`: the next activity will be triggered if the recipient " "opens the mailing." msgstr "" +":guilabel:`تم الفتح`: تعني أنه سيتم تشغيل النشاط التالي إذا قام المستلم بفتح" +" الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:251 msgid "" ":guilabel:`Not Opened`: the next activity will be triggered if the recipient" " does not open the mailing." msgstr "" +":guilabel:`لم يتم الفتح`: تعني أنه سيتم تشغيل النشاط التالي إذا لم يقم " +"المستلم بفتح الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:253 msgid "" ":guilabel:`Replied`: the next activity will be triggered if the recipient " "replies to the mailing." msgstr "" +":guilabel:`تم الرد`: تعني أنه سيتم تشغيل النشاط التالي إذا قام المستلم بالرد" +" على الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:254 msgid "" ":guilabel:`Not Replied`: the next activity will be triggered if the " "recipient does not reply to the mailing." msgstr "" +":guilabel:`لم يتم الرد`: تعني أنه سيتم تشغيل النشاط التالي إذا لم يقم " +"المستلم بالرد على الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:256 msgid "" ":guilabel:`Clicked`: the next activity will be triggered if the recipient " "clicks on a link included in the mailing." msgstr "" +":guilabel:`تم الضغط`: تعني أنه سيتم تشغيل النشاط التالي إذا قام المستلم " +"بالضغط على رابط موجود في الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:258 msgid "" ":guilabel:`Not Clicked`: the next activity will be triggered if the " "recipient does not click on a link included in the mailing." msgstr "" +":guilabel:`لم يتم الضغط`: تعني أنه سيتم تشغيل النشاط التالي إذا لم يقم " +"المستلم بالضغط على رابط موجود في الرسالة. " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:260 msgid "" ":guilabel:`Bounced`: the next activity will be triggered if the mailing is " "bounced (not sent)." msgstr "" +":guilabel:`المرتدة`: تعني أنه سيتم تشغيل النشاط التالي إذا ارتدّت الرسالة " +"(لم يتم إرسالها). " #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:262 msgid "" "Once a trigger is selected, the user can configure the child activity the " "same way they would for a regular workflow activity." msgstr "" +"بمجرد أن يتم تحديد المشغل، بإمكان المستخدم تهيئة النشاط التابع بنفس الطريقة " +"التي يقوم بتهيئة نشاط سير العمل العادي. " #: ../../content/applications/marketing/sms_marketing.rst:8 msgid "SMS Marketing" @@ -3631,11 +3688,11 @@ msgstr "التسويق عبر الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials.rst:5 #: ../../content/applications/marketing/social_marketing/essentials.rst:5 msgid "Essentials" -msgstr "" +msgstr "الأساسيات " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3 msgid "Mailing lists and blacklists" -msgstr "" +msgstr "القوائم البريدية والقوائم السوداء " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5 msgid "" @@ -3645,6 +3702,10 @@ msgid "" "company is migrating from another system, and already has a established " "audience." msgstr "" +"يعد إنشاء أو استيراد القوائم البريدية في أودو أمراً مفيداً جداً عند تقديم " +"المحتوى لمجموعات محددة من الأفراد الذين نيشاركون نفس الاهتمامات والفئة " +"العمرية. القوائم البريدية رائعة أيضاً للبدء إذا كانت الشركة تنتقل من نظام " +"آخر، ولديها جمهور محدد بالفعل. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10 msgid "" @@ -3652,6 +3713,9 @@ msgid "" "mailings, helps businesses maintain good customer relations, by giving " "recipients the power to control what they are (and aren't) sent." msgstr "" +"إضافة إلى ذلك، منح الجمهور خيار \"إلغاء الاشتراك\" من المراسلات الجماعية " +"يساعد الأعمال على المحافظة على العلاقات جيدة مع العملاء، عن طريق منح " +"المستلمين خيار التحكم في ما يتم إرساله (وما لا يتم إرساله) إليهم. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17 msgid "" @@ -3659,18 +3723,26 @@ msgid "" "called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with " "options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`." msgstr "" +"في تطبيق :guilabel:`التسويق عبر الرسائل النصية القصيرة` يوجد خيار في قائمة " +"الترويسة يسمى :guilabel:`القوائم البريدية`. عند الضغط عليه، ستظهر قائمة " +"فرعية مع خيارات لـ :guilabel:`القوائم البريدية` و :guilabel:`جهات اتصال " +"القوائم البريدية`. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21 msgid "" "Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of" " all mailing lists in the database." msgstr "" +"اضغط على :menuselection:`القوائم البريدية --> القوائم البريدية` لتحصل على " +"نظرة عامة على كافة القوائم البريدية في قاعدة بياناتك. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "" "View of the main SMS mailing list page on the Odoo SMS Marketing " "application." msgstr "" +"نظرة عامة على صفحة القائمة البريدية الرئيسية للرسائل النصية القصيرة في تطبيق" +" التسويق عبر الرسائل النصية القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28 msgid "" @@ -3678,6 +3750,8 @@ msgid "" ":guilabel:`Mailing Lists` page, and proceed to modify it in a number of " "ways." msgstr "" +"لتحرير أي قائمة موجودة، قم بتحديد القائمة المطلوبة من صفحة " +":guilabel:`القوائم البريدية` ثم باشر بتعديلها بطرق مختلفة. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31 msgid "" @@ -3685,10 +3759,15 @@ msgid "" "corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank " "mailing list template form." msgstr "" +"لإنشاء قائمة بريدية جديدة، اضغط على :guilabel:`إنشاء` في الزاوية العلوية إلى" +" يمين صفحة :guilabel:`القوائم البريدية`. سيؤدي القيام بذلك إلى إظهار استمارة" +" قالب قائمة مراسلة فارغة. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "View of the mailing list pop-up window in Odoo SMS Marketing." msgstr "" +"عرض النافذة المنبثقة للقائمة البريدية في تطبيق التسويق عبر الرسائل النصية " +"القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38 msgid "" @@ -3697,12 +3776,18 @@ msgid "" "recipients on the :guilabel:`Subscription Management page`. Doing so allows " "users to update their subscription preferences at any time." msgstr "" +"أولاً، اختر اسماً لـ :guilabel:`القائمة البريدية`, وقم بتفعيل خيار " +":guilabel:`عام`، لتمكين المستلمين من الوصول إلى القائمة البريدية في " +":guilabel:`صفحة إدارة الاشتراكات`. يتيح القيام بذلك للمستخدمين تحديث تفضيلات" +" اشتراكاتهم في أي وقت. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43 msgid "" "Checking the :guilabel:`Is Public` box is not required, but is recommended " "to maintain good customer relations." msgstr "" +"ليس من الضروري تحديد مربع خيار :guilabel:`عام`، ولكن نوصي بذلك للمحافظة على " +"العلاقات الجيدة مع العملاء. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46 msgid "" @@ -3710,6 +3795,9 @@ msgid "" "form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing " "list that was just created will be accessible." msgstr "" +"عندما تتم تعبئة هذه الحقول، اضغط على :guilabel:`إنشاء` للانتهاء من " +"الاستمارة. بعد ذلك، في لوحة البيانات الرئيسية :guilabel:`القوائم البريدية`، " +"سيكون بالإمكان الوصول إلى القائمة البريدية الجديدة التي قد تم إنشاؤها للتو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49 msgid "" @@ -3717,6 +3805,9 @@ msgid "" "the main :guilabel:`Mailing Lists` page to reveal the mailing list detail " "form." msgstr "" +"لتحرير القائمة البريدية أو تخصيصها بشكل أكبر، قم بتحديد القائمة البريدية من " +"الصفحة الرئيسية :guilabel:`القوائم البريدية` للكشف عن استمارة تفاصيل القائمة" +" البريدية. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52 msgid "" @@ -3724,31 +3815,41 @@ msgid "" "smart buttons displaying statistics for different metrics related to the " "mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)." msgstr "" +"على طول الجزء العلوي من استمارة تفاصيل القائمة البريدية، توجد العديد من " +"الأزرار التحليلية الذكية التي تعرض إحصائيات لمقاييس مختلفة متعلقة بالقائمة " +"البريدية (على سبيل المثال: :guilabel:`المستلمون`، :guilabel:`المراسلات`، وما" +" إلى ذلك). " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56 msgid "" "To review or edit any of those elements, click the desired smart button to " "reveal a separate page with in-depth data associated with the mailing list." msgstr "" +"لمراجعة أو تحرير أي من هذه العناصر، اضغط على الزر الذكي المطلوب لإظهار صفحة " +"منفصلة تحتوي على بيانات تفصيلية متعلقة بالقائمة البريدية. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59 msgid "" "To make changes to the mailing list itself, click the :guilabel:`Edit` " "button in the upper-left corner of the mailing list detail form." msgstr "" +"لإجراء تغييرات على القائمة البريدية نفسها، اضغط على زر :guilabel:`تحرير` " +"الموجود في الزاوية العلوية إلى اليمين في استمارة تفاصيل القائمة البريدية. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "View of the mailing list template form in Odoo SMS Marketing." msgstr "" +"عرض قالب استمارة القائمة البريدية في تطبيق التسويق عبر الرسائل النصية " +"القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67 msgid "" "Don't forget to hit the :guilabel:`Save` button once changes have been made." -msgstr "" +msgstr "لا تنس الضغط على الزر :guilabel:`حفظ` بمجرد إجراء التغييرات. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70 msgid "Mailing lists contacts" -msgstr "" +msgstr "جهات اتصال القوائم البريدية " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72 msgid "" @@ -3757,12 +3858,18 @@ msgid "" "dashboard with with all the contacts associated with one or more of the " "configured mailing lists in the database." msgstr "" +"تمكن من الوصول إلى معلومات جهات الاتصال من قائمة بريدية واحدة أو أكثر، اذهب " +"إلى :menuselection:`القوائم البريدية --> جهات اتصال القائمة البريدية` لإظهار" +" لوحة بيانات تحتوي على كافة جهات الاتصال المرتبطة بواحدة أو أكثر من القوائم " +"البريدية التي قد تمت تهيئتها في قاعدة البيانات. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "" "View of the mailing lists contact page in the Odoo SMS Marketing " "application." msgstr "" +"عرض صفحة جهات الاتصال الخاصة بالقوائم البريدية في تطبيق التسويق عبر الرسائل " +"النصية القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81 msgid "" @@ -3771,10 +3878,14 @@ msgid "" "only showing contact information for recipients who still want to receive " "communications and mailings." msgstr "" +"يقوم أودو افتراضياً بإظهار صفحة :guilabel:`جهات اتصال القائمة البريدية` مع " +"فلتر :guilabel:`استثناء أرقام الهواتف المدرجة في القائمة السوداء` في شريط " +"البحث. ولذلك، يتم عرض معلومات الاتصال فقط للمستلمين الذين ما زالوا يرغبون في" +" تلقي الاتصالات والرسائل البريدية. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86 msgid "Communication history in the Chatter" -msgstr "" +msgstr "سجِل التواصل في الدردشة " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88 msgid "" @@ -3782,6 +3893,9 @@ msgid "" "*chatter* section, located beneath a recipient's contact form (in the " "*Contacts* application)." msgstr "" +"يتم الاحتفاظ بسجل يمكن الوصول إليه لكل رسالة (رسائل) بريدية مرسلة في قسم " +"*الدردشة* الخاص بكل مستلم، والموجود أسفل استمارة التواصل الخاصة بالمستلم (في" +" تطبيق *جهات الاتصال*). " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91 msgid "" @@ -3789,6 +3903,8 @@ msgid "" "communications, and see a history of interactions with contacts and " "prospects." msgstr "" +"بوسع مستخدمي قاعدة البيانات الرجوع إلى الدردشة لتتبع الاتصالات بسهولة، " +"والاطلاع على سجل التفاعلات مع جهات الاتصال والعملاء المحتملين. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94 msgid "" @@ -3796,10 +3912,13 @@ msgid "" "which :abbr:`SMS (Short Message Service)` mailing promotions a certain " "customer has received (or not received)." msgstr "" +"على سبيل المثال، بوسع مندوبي المبيعات استخدام الدردشة لمعرفة أي عروض " +"المراسلات الترويجية :abbr:`SMS (الرسائل النصية القصيرة)` التي تلقاها عميل " +"معين (أو لم يتلقاها). " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "View of what the chatter looks like in the Odoo Contacts app." -msgstr "" +msgstr "عرض لما تبدو عليه الدردشة في تطبيق جهات الاتصال لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:104 msgid "" @@ -3807,6 +3926,10 @@ msgid "" "recipients with the power to add their phone number to a list of people who " "no longer want to receieve communications or mailings." msgstr "" +"يحتوي تطبيق *التسويق عبر الرسائل النصية القصيرة* لدى أودو على خاصية " +":guilabel:`القائمة السوداء` التي تمنح المستلمين إمكانية إضافة أرقام هواتفهم " +"إلى قائمة الأشخاص الذين لم يعودوا يرغبون في تلقي الاتصالات أو الرسائل " +"البريدية. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108 msgid "" @@ -3815,6 +3938,10 @@ msgid "" "their :guilabel:`Subscription Management` page. Customers can also be added " "manually to the blacklist, if necessary." msgstr "" +"يُعرف ذلك أيضاً بعملية إلغاء الاشتراك: ستتم إضافة العملاء تلقائياً إلى " +"*القائمة السوداء*، إذا قاموا بالضغط على :guilabel:`إلغاء الاشتراك`، عن طريق " +"صفحة :guilabel:`إدارة الاشتراك` الخاصة بهم. ويمكن أيضاً إضافة العملاء يدوياً" +" إلى القائمة السوداء، إذا لزم الأمر. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112 msgid "" @@ -3823,10 +3950,15 @@ msgid "" "Numbers` to reveal a dashboard containing every blacklisted phone number in " "the database." msgstr "" +"لرؤية مجموعة كاملة من الأرقام المدرجة في القائمة السوداء، اذهب إلى " +":menuselection:`تطبيق التسويق عبر الرسائل النصية القصيرة --> التهيئة --> " +"أرقام الهواتف المدرجة في القائمة السوداء` لإظهار لوحة بيانات تحتوي على كل " +"رقم هاتف مدرج في القائمة السوداء في قاعدة البيانات. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "SMS Blacklist menu in the application." msgstr "" +"قائمة الأرقام المدرجة في القائمة السوداء للرسائل النصية القصيرة في التطبيق. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120 msgid "" @@ -3835,6 +3967,10 @@ msgid "" " next page's form. There's also a checkbox to indicate whether that " "particular phone numnber is :guilabel:`Active` (or not)." msgstr "" +"لإضافة رقم إلى القائمة السوداء يدوياً، اضغط على زر :guilabel:`إنشاء` في " +"الزاوية العلوية إلى اليمين في لوحة البيانات، وقم بإدخال رقم الهاتف في " +"استمارة الصفحة التالية. يوجد أيضاً مربع اختيار للإشارة إلى ما إذا كان رقم " +"الهاتف المحدد :guilabel:`نشطاً` (أم لا). " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128 msgid "" @@ -3843,10 +3979,14 @@ msgid "" "blacklist, select the desired number on the dashboard, and then, on the " "phone number's form, click :guilabel:`Unblacklist`." msgstr "" +"بمجرد اكتمال الاستمارة، قم بالضغط على :guilabel:`حفظ` لإضافته إلى قائمة " +":guilabel:`أرقام الهواتف المدرجة في القائمة السوداء`. لإزالة أي رقم من " +"القائمة السوداء، حدد الرقم المطلوب على لوحة البيانات، ثم في استمارة رقم " +"الهاتف، اضغط على زر :guilabel:`إزالة من القائمة السوداء`. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133 msgid "Importing blacklists" -msgstr "" +msgstr "استيراد القوائم السوداء " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135 msgid "" @@ -3855,6 +3995,9 @@ msgid "" "already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` " "mailings." msgstr "" +"أثناء نقل البرنامج/المنصة، من الممكن استيراد قائمة سوداء موجودة بالفعل لجهات" +" الاتصال. سيشمل ذلك العملاء الذين طلبوا أن يتم إدراجهم في القائمة السوداء " +"لمراسلات :abbr:`SMS (خدمة الرسائل النصية القصيرة)`. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139 msgid "" @@ -3863,14 +4006,20 @@ msgid "" "drop-down menu (beneath the search bar), and click :guilabel:`Import " "records`." msgstr "" +"للقيام بذلك، اذهب إلى :menuselection:`تطبيق التسويق عبر الرسائل النصية " +"القصيرة --> التهيئة --> أرقام الهواتف المدرجة في القائمة السوداء`، ثم حدد " +"القائمة المنسدلة :guilabel:`المفضلة` (أسفل شريط البحث)، واضغط على :guilabel " +":`استيراد السجلات`. " #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "View of how to import a blacklist in Odoo SMS Marketing." msgstr "" +"عرض كيفية استيراد القوائم السوداء في تطبيق التسويق عبر الرسائل النصية " +"القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3 msgid "SMS campaign settings" -msgstr "" +msgstr "إعدادات حملة الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5 msgid "" @@ -3879,16 +4028,22 @@ msgid "" " way to remind people about upcoming events, issued invoices, and so much " "more." msgstr "" +"استخدام حملات :abbr:`SMS (خدمة الرسائل النصية القصيرة)` مع تطبيق أودو " +"*التسويق عبر الرسائل النصية القصيرة* ليس استراتيجية تسويقية فعلة فحسب، بل " +"تعد طريقة رائعة لتذكير الأفراد بالفعاليات القادمة والفواتير التي تم إصدارها " +"وغير ذلك الكثير. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9 msgid "" "But, before :abbr:`SMS (Short Message Service)` campaigns can be created " "(and sent), a few specific settings and features must be enabled first." msgstr "" +"ولكن قبل أن يتم إنشاء حملات :abbr:`SMS (خدمة الرسائل النصية القصيرة)` " +"(وإرسالها)، يجب أن يتم تمكين بعض الإعدادات والخصائص المحددة أولاً. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13 msgid "SMS campaign setting" -msgstr "" +msgstr "إعداد حملة الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15 msgid "" @@ -3897,16 +4052,23 @@ msgid "" ":menuselection:`Email Marketing --> Configuration --> Settings`, and then " "enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes." msgstr "" +"لتمكين حملات :abbr:`SMS (خدمة الرسائل النصية القصيرة)` في أودو، تأكد من أن " +"خاصية *الحملات البريدية* قد تم تفعيلها، عن طريق الذهاب إلى " +":menuselection:`التسويق عبر الرسائل النصية القصيرة --> التهيئة --> " +"الإعدادات`، ثم قم بتفعيل :guilabel:`الحملات البريدية` ثم اضغط على " +":guilabel:`حفظ` التغييرات. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "View of the mailing campaigns setting in Odoo." -msgstr "" +msgstr "عرض إعدادات الحملات البريدية في أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24 msgid "" "Activating the *Mailing Campaigns* feature in the *General Settings* also " "enables the *A/B Test* feature." msgstr "" +"يؤدي تفعيل خاصية *الحملات البريدية* في *الإعدادات العامة* إلى تمكين خاصية " +"*اختبار A/B* " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27 msgid "" @@ -3915,10 +4077,15 @@ msgid "" "available for use. Similarly, the :guilabel:`A/B Test` tab is now also " "available on every :abbr:`SMS (Short Message Service)` template form." msgstr "" +"بمجرد أن قد تم تفعيل الإعداد، عد إلى تطبيق :menuselection:`التسويق عبر " +"الرسائل النصية القصيرة`، ولاحظ أن قائمة :guilabel:`الحملات` في الترويسة باتت" +" الآن متاحة للاستخدام. وبنفس الطريقة، أصبحت علامة تبويب :guilabel:`اختبار " +"A/B` متاحة الآن في كل قالب استمارة :abbr:`SMS (خدمة الرسائل النصية " +"القصيرة)`." #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32 msgid "A/B tests" -msgstr "" +msgstr "اختبارات A/B " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34 msgid "" @@ -3927,6 +4094,10 @@ msgid "" "order to compare which version is the most successful in producing " "engagement and/or conversion outcomes." msgstr "" +"تسمح :guilabel:`اختبارات A/B` لأي مراسلات من :abbr:`SMS (خدمة الرسائل النصية" +" القصيرة)` بأن يتم اختبارها مقابل الإصدارات الأخرى ضمن نفس الحملة، حتى تتمكن" +" من مقارنة أي الخيارين أكثر نجاحاً فيما يتعلق بتحفيز التفاعل و/أو زيادة معدل" +" التحول إلى عملاء. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38 msgid "" @@ -3934,21 +4105,28 @@ msgid "" ":guilabel:`A/B Tests` tab, initially, there's only a single checkbox " "labeled: :guilabel:`Allow A/B Testing.`" msgstr "" +"في قالب استمارة :abbr:`SMS (خدمة الرسائل النصية القصيرة)`، تحت علامة تبويب " +":guilabel:`اختبارات A/B`، مبدئياً، يوجد مربع اختيار واحد فقط يسمى: " +":guilabel:`السماح باختبارات A/B.` " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41 msgid "When clicked, a series of other options appear." -msgstr "" +msgstr "عند الضغط عليه، ستظهر مجموعة من الخيارات الأخرى. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "The A/B Test tab is located on an Odoo SMS Marketing app campaign form." msgstr "" +"تقع علامة تبويب اختبار A/B في استمارة حملة التسويق عبر الرسائل النصية " +"القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47 msgid "" "In the first field, enter a desired percentage of recipients to conduct the " "A/B Test on." msgstr "" +"في الحقل الأول، قم بإدخال النسبة المطلوبة من المستلمين الذين سيتم إجراء " +"اختبار A/B عليهم. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49 msgid "" @@ -3956,6 +4134,9 @@ msgid "" " is what Odoo will use to determine the successful result of an A/B Test. In" " other words, this tells Odoo how to pick a winning A/B test." msgstr "" +"تحت حقل النسبة المئوية، يقع حقل :guilabel:`تحديد الفائز`. هذا ما سيستخدمه " +"أودو لتحديد النتيجة الناجحة لاختبار A/B. بمعنى آخر، إنه يخبر أودو كيفية " +"اختيار الفائز في اختبار A/B. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53 msgid "" @@ -3963,6 +4144,9 @@ msgid "" " Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or " ":guilabel:`Revenues`." msgstr "" +"الأقسام التالية متاحة: :guilabel:`يدوي`، :guilabel:`أعلى نسبة نقر`، " +":guilabel:`العملاء المهتمون`، :guilabel:`عروض الأسعار`، أو " +":guilabel:`الإيرادات`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56 msgid "" @@ -3971,23 +4155,31 @@ msgid "" "variation. Then, Odoo sends that winning mailing variation to the remaining " "recipients, who weren't involved in the test, at that prior date and time." msgstr "" +"وأخيراً، يكون حقل :guilabel:`إرسال النهائي في` مدرجاً. يمثل ذلك التاريخ الذي" +" يستخدمه أودو كموعد نهائي لتحديد النسخة الفائزة من المراسلات. بعد ذلك، يقوم " +"أودو بإرسال النسخة الفائزة من المراسلات إلى المستخدمين المتبقين الذين لم " +"يكونوا جزءاً من الاختبار في ذلك التاريخ والوقت السابق. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62 msgid "" "Quickly create different versions of the mailing to add to the A/B Test by " "clicking the :guilabel:`Create an Alternate Version` button." msgstr "" +"تمكن من إنشاء نسخ مختلفة من المراسلات لإضافتها إلى اختبار A/B عن طريق الضغط " +"على زر :guilabel:`إنشاء نسخة بديلة`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66 msgid "" "Remember, the winning mailing variation is based on the criteria selected in" " the :guilabel:`Winner Selection` field." msgstr "" +"تذكر أن النسخة الفائزو من المراسلات تعتمد على الفئة المحددة في حقل " +":guilabel:`الخيار الفائز`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70 #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 msgid "Campaigns page" -msgstr "" +msgstr "صفحة الحملات " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72 msgid "" @@ -3997,16 +4189,23 @@ msgid "" "related to the mailings associated with that campaign (e.g. number of " "emails, social posts, SMSs, and push notifications)." msgstr "" +"لإنشاء أو تحرير أو تحليل أي حملة، اضغط على :menuselection:`الحملات` في قائمة" +" ترويسة تطبيق :guilabel:`التسويق عبر الرسائل النصية القصيرة`. في صفحة " +":guilabel:`الحملات`، تعرض كل حملة العديد من المعلومات المختلفة المتعلقة " +"بالمراسلات المرتبطة بتلك الحملة (مثال: عدد رسائل البريد الإلكتروني " +"والمنشورات الاجتماعية ,الرسائل النصية القصيرة والإشعارات المنبثقة). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, " "separated by stage." msgstr "" +"عرض لوحة البيانات لحملات مختلفة في تطبيق التسويق عبر الرسائل النصية القصيرة " +"لدى أودو، مفصولة حسب المراحل. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 msgid "Campaign templates" -msgstr "" +msgstr "قوالب الحملات " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84 msgid "" @@ -4015,10 +4214,15 @@ msgid "" "made campaign in order to duplicate, review, or edit its campaign template " "form." msgstr "" +"اضغط على :guilabel:`إنشاء` لإنشاء حملة جديدة، وسيكشف أودو عن قالب استمارة " +"حملة فارغ حتى تقوم بتعبئته. يمكنك أيضاً تحديد أي حملة قد تم إطلاقها في " +"السابق حتى تقوم بنسخها ومراجعتها أو تحديد قالب استمارة الحملة الخاص بها. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "View of an SMS campaign template in Odoo SMS marketing." msgstr "" +"عرض قالب حملة الرسائل النصية القصيرة في تطبيق التسويق عبر الرسائل النصية " +"القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92 msgid "" @@ -4026,6 +4230,9 @@ msgid "" ":guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push " "Notifications` are available above the template form." msgstr "" +"مع كل حملة، تكون الخيارات :guilabel:`إرسال مراسلات جديدة`، :guilabel:`إرسال " +"رسائل نصية قصيرة`، :guilabel:`إرسال منشور اجتماعي`، و :guilabel:`الاشعارات " +"المنبثقة` متاحة أعلى قالب الاستمارة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96 msgid "" @@ -4034,6 +4241,9 @@ msgid "" "of messages can be reviewed or edited, along with various data sets related " "to each specific mailing." msgstr "" +"عندما تتم إضافة إحدى خيارات التواصل تلك إلى الحملة، سيقوم أودو بإنشاء علامة " +"تبويب جديدة مقابِلة في قالب الاستمارة، حيث يمكن عرض أو تحرير الرسائل من ذلك " +"النوع، بالإضافة إلى مختلف مجموعات البيانات المتعلقة بالمراسلات المحددة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100 msgid "" @@ -4042,6 +4252,9 @@ msgid "" " :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate " "page." msgstr "" +"في أعلى القالب، توجد عدة أزرار ذكية تحليلية. عند الضغط عليها، يُظهِر أودو " +"مقاييس تفصيلية متعلقة بذلك الموضوع المحدد (مثال: :guilabel:`التفاعل`، " +":guilabel:`الفرص`، إلخ.) في صفحة منفصلة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104 msgid "" @@ -4049,16 +4262,21 @@ msgid "" ":guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be" " added, as well (if necessary)." msgstr "" +"أسفل الأزرار الذكية، توجد حقول لـ :guilabel:`اسم الحملة` و " +":guilabel:`المسؤول`. يسمح أودو بإضافة العديد من :guilabel:`علامات التصنيف` " +"كذلك (إذا لزم الأمر). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108 msgid "Sending SMSs through the Contacts app" -msgstr "" +msgstr "إرسال الرسائل النصية القصيرة عبر تطبيق جهات الاتصال " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110 msgid "" "Sending :abbr:`SMS (Short Message Service)` mailings directly through a " "contact's form is available by default." msgstr "" +"خاصية إرسال :abbr:`SMS (الرسائل النصية القصيرة)` مباشرة من خلال استمارة " +"التواصل متاحة بشكل افتراضي. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113 msgid "" @@ -4067,11 +4285,15 @@ msgid "" " the database, and click on the :guilabel:`SMS` icon on the contact form " "(next to the :guilabel:`Phone Number` field)." msgstr "" +"حتى تتمكن من إرسال :abbr:`SMS (رسالة نصية قصيرة)` بهذه الطريقة، اذهب إلى " +"تطبيق :menuselection:`جهات الاتصال` وقم بتحديد جهة الاتصال المطلوبة في قاعدة" +" البيانات، ثم اضغط على أيقونة :guilabel:`SMS` في استمارة التواصل (بجانب حقل " +":guilabel:`رقم الهاتف`). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "The SMS icon is located on an individual's contact form in Odoo Contacts." -msgstr "" +msgstr "أيقونة SMS موجودة في استمارة التواصل في تطبيق جهات الاتصال لدى أودو. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121 msgid "" @@ -4080,15 +4302,20 @@ msgid "" "View`, and select all the desired contacts to whom the message should be " "sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`." msgstr "" +"لإرسال رسالة إلى عدة جهات اتصال دفعة واحدة، اذهب إلى لوحة البيانات الرئيسية " +"لتطبيق :menuselection:`جهات الاتصال`، واختر :guilabel:`نافذة عرض القائمة`، " +"ثم قم بتحديد كافة جهات الاتصال المطلوبة التي يجب أن يتم إرسال الرسائل إليها." +" تحت :guilabel:`الإجراء`، قم بتحديد خيار :guilabel:`إرسال رسالة نصية قصيرة`." +" " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "Select a number of contacts, click action, and select send multiple SMSs." -msgstr "" +msgstr "حدد عدد جهات الاتصال ثم اضغط على الإجراء وحدد عدة رسائل نصية قصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130 msgid "Set up SMS templates for future use" -msgstr "" +msgstr "قم بإعداد قوالب للرسائل النصية القصيرة، لاستخدامها في المستقبل " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132 msgid "" @@ -4098,6 +4325,11 @@ msgid "" "app`. Then, scroll down to the :guilabel:`Developer Tools` section, and " "click :guilabel:`Activate the Developer Mode`." msgstr "" +"حتى تتمكن من إعداد :guilabel:`قوالب الرسائل النصية القصيرة` لاستخدامها " +"مستقبلاً، قم بتفعيل :ref:`وضع المطور `، عن طريق الذهاب إلى " +"لوحة بيانات أودو الرئيسية المليئة بالتطبيقات، ثم قم بتحديد " +":menuselection:`تطبيق الإعدادات`. بعد ذلك، مرر إلى الأسفل إلى قسم " +":guilabel:`أدوات المطوِّر`، واضغط على :guilabel:`تفعيل وضع المطوِّر`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137 msgid "" @@ -4106,6 +4338,9 @@ msgid "" "of the dashboard; this bug icon indicates that developer mode is currently " "active." msgstr "" +"بمجرد أن قد تم تفعيل *وضع المطوِّر*، ستظهر لوحة بيانات أودو الرئيسية مرة " +"أخرى، وستكون بها أيقونة على شكل حشرة، أعلى يمين لوحة البيانات؛ تشير أيقونة " +"الحشرة تلك إلى أن وضع المطوِّر مفعّل حالياً. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141 msgid "" @@ -4114,12 +4349,18 @@ msgid "" " to begin setting up :abbr:`SMS (Short Message Service)` templates for " "future marketing campaigns." msgstr "" +"تالياً، عد إلى :menuselection:`تطبيق الإعدادات` وفي قوائم الترويسة المرئية " +"حالياً في الأعلى، اختر :menuselection:`تقني --> قوالب الرسائل النصية " +"القصيرة` لبدء إعداد قوالب :abbr:`SMS (خدمة الرسائل النصية القصيرة)` للحملات " +"التسويقية القادمة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "Select the SMS Template option in the Technical dropdown on the Settings " "app." msgstr "" +"قم بتحديد خيار قالب الرسائل النصية القصيرة في القائمة المنسدلة التقنية في " +"تطبيق الإعدادات. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149 msgid "" @@ -4128,22 +4369,30 @@ msgid "" ":guilabel:`List` view showcases each template's name, and to which " "recipients it applies." msgstr "" +"داخل لوحة بيانات :guilabel:`قوالب الرسائل النصية القصيرة`، يُظهِر أودو صفحة " +"كاملة من قوالب :abbr:`SMS (الرسائل النصية القصيرة)`. تُظهِر نافذة عرض " +":guilabel:`القائمة` الافتراضية اسم كل قالب، ومجموعة المستلمين الذين ينطبق " +"عليهم ذلك القالب. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153 msgid "" "On this page, :abbr:`SMS (Short Message Service)` templates can be edited or" " created from scratch." msgstr "" +"في هذه الصفحة، يمكن تحرير قوالب :abbr:`SMS (الرسائل النصية القصيرة)` أو " +"إنشاؤها من الصفر. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 msgid "" "The SMS Templates page in Odoo is available after enabling developer mode in the General\n" "Settings" msgstr "" +"تصبح صفحة قوالب الرسائل النصية القصيرة في أودو متاحة بعد تمكين وضع المطوِّر في الإعدادات \n" +"العامة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3 msgid "SMS essentials" -msgstr "" +msgstr "أساسيات الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5 msgid "" @@ -4151,6 +4400,10 @@ msgid "" "strategies can help companies expand their market reach, especially in some " "countries, where emails might not be very common, or even used at all." msgstr "" +"يمكن أن يساعد استخدام التمدد في استراتيجيات التواصل عبر :abbr:`SMS (الرسائل " +"النصية القصيرة)` الشركات على التوسع في سوق العمل، خاصة في بعض الدول التي قد " +"لا يكون استخدام البريد الإلكتروني شائعاً فيها أو قد لا يكون البريد " +"الإلكتروني مستخدماً على الإطلاق. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9 msgid "" @@ -4160,10 +4413,16 @@ msgid "" "yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through" " rate)` outcomes." msgstr "" +"بوسع تطبيق *التسويق عبر الرسائل النصية القصيرة* لدى أودو أن يساعد على تعزيز " +"تسبة تحول المستلمين إلى عملاء عند الإجراءات القيّمة، كتسجيلات الفعاليات " +"والتجارب المجانية وعمليات الشراء وما إلى ذلك، بما أن الرسائل النصية وقنوات " +"التسويق عبر الهاتف المحمول تجدي نفعاً أكبر عادةً، فيما يتعلق بنواتج " +":abbr:`CTOR (نسبة الضغط على الرسالة لفتحها)` و :abbr:`CTR (نسبة الضغط على " +"الروابط)`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15 msgid "SMS marketing dashboard" -msgstr "" +msgstr "لوحة بيانات التسويق عبر الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17 msgid "" @@ -4172,6 +4431,10 @@ msgid "" "been created, along with pertinent information and data related to that " "specific message." msgstr "" +"عندما يكون التطبيق مفتوحاً، يقوم أودو بعرض لوحة البيانات الرئيسية لتطبيق " +":guilabel:`التسويق عبر الرسائل النصية القصيرة`، والتي تُظهِر المراسلات " +"المختلقة عبر الرسائل النصية القصيرة التي قد تم إنشاؤها، إضافة إلى معلومات " +"وبيانات دقيقة متعلقة بتلك الرسالة بالتحديد. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21 msgid "" @@ -4179,6 +4442,9 @@ msgid "" " opened, which provides an organized display of the SMS mailings that have " "been created, and what their current status is at the moment." msgstr "" +"يستخدم أودو نافذة عرض :guilabel:`كانبان` بشكل افتراضي عند فتح التطبيق، والذي" +" يقدم عرضاً منظماً للمراسلات عبر الرسائل النصية القصيرة التي قد تم إنشاؤها، " +"وحالاتها في الوقت الراهن. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26 msgid "" @@ -4186,6 +4452,9 @@ msgid "" " statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or " ":guilabel:`Sent`." msgstr "" +"يمكن أن يكون للمراسلات عبر :abbr:`SMS (الرسائل النصية القصيرة)` إحدى الحالات" +" التالية: :guilabel:`مسودة`، :guilabel:`قيد الانتظار`، :guilabel:`جاري " +"الإرسال`، أو :guilabel:`تم الإرسال`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29 msgid "" @@ -4193,12 +4462,18 @@ msgid "" "there are a few different view options to choose from. Each one provides a " "unique take on the same SMS information." msgstr "" +"في الزاوية العلوية إلى اليمين للوحة البيانات الرئيسية لتطبيق " +":guilabel:`التسويق عبر الرسائل النصية القصيرة`، توجد بضع خيارات للعرض " +"للاختيار من بينها. يقدم كل منها مظهراً فريداً لنفس معلومات الرسائل النصية " +"القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32 msgid "" "The :guilabel:`List` view provides the same useful data related to SMS " "mailings, but in a more traditional list layout." msgstr "" +"تمنح نافذة عرض :guilabel:`القائمة` نفس البيانات المفيدة المتعلقة بالمراسلات " +"عبر الرسائل النصية القصيرة، ولكن بطريقة عرض القائمة التقليدية. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35 msgid "" @@ -4207,6 +4482,11 @@ msgid "" "date is clicked, Odoo reveals a blank SMS template that, when completed, " "will be scheduled to be sent on that specific future date." msgstr "" +"تمنح نافذة عرض :guilabel:`التقويم` تقويماً بسيطاً سهل القراءة، حتى يكون من " +"السهل رؤية الأوقات التي سيتم إرسال الرسائل النصية القصيرة فيها (أو الرسائل " +"التي قد تم إرسالها بالفعل). إذا قمت بالضغط على تاريخ في المستقبل، يُظهِر " +"أودو قالب رسالة نصية قصيرة فارغ. عند إكماله، ستتم جدولته ليتم إرساله في ذلك " +"التاريخ المحدد في المستقبل. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39 msgid "" @@ -4214,10 +4494,13 @@ msgid "" "series of graphs and charts. Odoo also provides various ways to sort and " "group the data for more detailed analysis." msgstr "" +"وأخيراً، تُصوِّر طريقة عرض :guilabel:`الرسم البياني` نفس البيانات المتعلقة " +"بالرسائل النصية القصيرة في سلسلة من الرسوم البيانية والمخططات. يوفر أودو " +"أيضاً طرقاً مختلفة لفرز البيانات وتجميعها لإجراء تحليل أكثر تفصيلاً. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43 msgid "Create SMS messages" -msgstr "" +msgstr "إنشاء رسالة نصية قصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45 msgid "" @@ -4225,16 +4508,19 @@ msgid "" "dashboard, and Odoo reveals a blank SMS template form, which can be " "configured in a number of different ways." msgstr "" +"للبدء، اضغط على :guilabel:`إنشاء` في لوحة البيانات الرئيسية لتطبيق " +":guilabel:`التسويق عبر الرسائل النصية القصيرة`، وسيُظهِر أودو قالب استمارة " +"رسائل نصية قصيرة فارغ، والذي يمكن تهيئته بعدة طرق مختلفة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "Creating an SMS marketing template." -msgstr "" +msgstr "إنشاء قالب للتسويق عبر الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52 msgid "" "First, give the mailing a :guilabel:`Subject`, which describes what the " "mailing is about." -msgstr "" +msgstr "أولاً، أعطِ الرسالة :guilabel:`موضوعاً` يصف مضمون الرسالة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54 msgid "" @@ -4245,6 +4531,11 @@ msgid "" "send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select " "Mailing List` field." msgstr "" +"بعد ذلك، في حقل :guilabel:`المستلمين`، اختر من الذي سيتم إرسال هذه " +":abbr:`SMS (الرسالة النصية القصيرة)` إليه. يحتوي أودو افتراضياً على " +":guilabel:`قائمة بريدية` محددة. إذا كان ذلك هو خيار الحقل المطلوب لـ " +":guilabel:`المستلمين`، حدد أي القوائم البريدية على أودو إرسال هذه :abbr:`SMS" +" (الرسالة النصية القصيرة)` إليها في حقل :guilabel:`تحديد القائمة البريدية`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60 msgid "" @@ -4253,22 +4544,31 @@ msgid "" "along with various types of data related to that specific list (e.g. number " "of contacts, mailings, recipients, etc.)." msgstr "" +"لإنشاء (أو تحرير) قائمة بريدية، اذهب إلى :menuselection:`القوائم البريدية " +"--> القائمة اببريدية`. يعرض أودو هناك كافة القوائم البريدية التي قد تم " +"إنشاؤها سابقاً، بالإضافة إلى مختلف أنواع البيانات المتعلقة بتلك القائمة " +"بالتحديد (مثال: عدد جهات الاتصال، المراسلات، المستلمين، إلخ). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 msgid "" "To learn more about mailing lists and contacts, check out " ":doc:`mailing_lists_blacklists`" msgstr "" +"لمعرفة المزيد عن القوائم البريدية وجهات الاتصال، ألقِ نظرة على " +":doc:`mailing_lists_blacklists` " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "View of the mailing list page in the SMS marketing application." msgstr "" +"عرض صفحة القائمة البريدية في تطبيق التسويق عبر الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 msgid "" "To reveal all the possible options in the :guilabel:`Recipients` field, " "click the field to see all the choices Odoo makes available." msgstr "" +"لإظهار كافة الخيارات الممكنة في حقل :guilabel:`المستلمين`، اضغط على الحقل " +"لرؤية كافة الخيارات التي يجعلها أودو متاحة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 msgid "" @@ -4278,6 +4578,11 @@ msgid "" "can be customized to fit any business need), or, if no default recipient " "filter equation is present, an :guilabel:`Add Filter` button will appear." msgstr "" +"عندما يتم تحديد حقل آخر (غيرحقل :guilabel:`القائمة البريدية`)، يُصبح خيار " +"تحديد ذلك الحقل المحدد بكل أكبر متاحاً — إما بمعادلة فلتر المستلم الافتراضية" +" التي تظهر تلقائياً (والتي يمكن تخصيصها لتناسب احتياجات أي عمل)، أو، في حال " +"لم يكن هناك معادلة فلتر افتراضية للمستلم، سيظهر زر لـ :guilabel:`إضافة " +"فلتر`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79 msgid "" @@ -4285,6 +4590,9 @@ msgid "" "domain rule fields, which can be configured similar to an equation. You can " "create multiple recipient rules, if necessary." msgstr "" +"عند الضغط على زر :guilabel:`إضافة فلتر`، ستظهر حقول نطاق قابل للتخصيص " +"تماماً، والتي يمكن تهيئتها بطريقة مماثلة للمعادلة. يمكنك إنشاء عدة قواعد " +"مستلمين، إذا استدعى الأمر. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82 msgid "" @@ -4292,6 +4600,9 @@ msgid "" "recipients who fit into whatever criteria is configured in those fields. " "Multiple rules can be added." msgstr "" +"بعد ذلك، سيرسل أودو فقط :abbr:`SMS (الرسائل النصية القصيرة)` إلى المستلمين " +"الذين يقعون ضمن الفئة التي قد تمت تهيئتها في تلك الحقول. يمكن إضافة عدة " +"حقول. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86 msgid "" @@ -4300,6 +4611,9 @@ msgid "" "Message Service)`, by default — unless more specific recipient rules are " "entered." msgstr "" +"إذا كانت :guilabel:`جهة الاتصال` محددة،كافة سجلات *جهات الاتصال* في قاعدة " +"بيانات أودو ستتسلم (vendors, customers, etc.) :abbr:`SMS (الرسائل النصية " +"القصيرة)`، افتراضياً — إلا إذا تم إدخال قواعد مستلمين أكثر تحديداً. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90 msgid "" @@ -4308,14 +4622,19 @@ msgid "" "Name` equals `United States`), and they haven't blacklisted themselves from " "any mailings (e.g. `Blacklist` > `is` > `not set`)." msgstr "" +"على سبيل المثال، سيتم إرسال الرسالة أدناه فقط إلى جهات الاتصال في قاعدة " +"البيانات، المتواجدين في الولايات المتحدة الأمريكية (مثال: `الدولة` > `اسم " +"الدولة` يساوي `الولايات المتحدة الأمريكية`)، والذين لم يقوموا بإدراج أنفسهم " +"في القائمة السوداء للمراسلات (مثال: `القائمة السوداء` > `هي` > `لم يتم " +"تعيينها`). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0 msgid "Contact recipients on SMS marketing." -msgstr "" +msgstr "جهات الاتصال المستلمة في تطبيق التسويق عبر الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99 msgid "Writing SMS messages" -msgstr "" +msgstr "كتابة الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101 msgid "" @@ -4325,16 +4644,23 @@ msgid "" "used in the message, along with how many :abbr:`SMS (Short Message Service)`" " mailings it will take to deliver the complete message." msgstr "" +"قم بإدخال محتوى :abbr:`SMS (الرسالة النصية القصيرة)` في حقل النص الموجود في " +"علامة تبويب :guilabel:`محتوى الرسالة النصية القصيرة`. يمكن أيضاً أن تشمل " +"الروابط والرموز التعبيرية. أسفل حقل النص، يُظهِر أودو عدد الخانات المستخدمة " +"في الرسالة، إضافة إلى عدد المراسلات :abbr:`SMS (الرسائل النصية القصيرة)` " +"المطلوبة لإيصال الرسالة كاملة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107 msgid "" "To check the price of sending an :abbr:`SMS (Short Message Service)` for a " "country, click on the :guilabel:`Information` icon." msgstr "" +"للتحقق من سعر إرسال :abbr:`SMS (رسالة نصية قصيرة)` لدولة ما، اضغط على أيقونة" +" :guilabel:`المعلومات`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "SMS price check icon." -msgstr "" +msgstr "أيقونة التحقق من سعر الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115 msgid "" @@ -4342,14 +4668,19 @@ msgid "" "Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be " "sent without credits." msgstr "" +"ميجب أن تقوم بشراء الرصيد من أودو حتى تتمكن من الاستفادة من تطبيق *التسويق " +"عبر الرسائل النصية القصيرة*؛ لن تم إرسال :abbr:`SMS (الرسائل النصية " +"القصيرة)` دون رصيد. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119 msgid "`Odoo SMS - FAQ `_" msgstr "" +"`الرسائل النصية القصيرة في أودو - FAQ `_ " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122 msgid "Track links used in SMS messages" -msgstr "" +msgstr "تتبع الروابط المستخدمة في الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124 msgid "" @@ -4358,14 +4689,18 @@ msgid "" "related to those specific links, which can be found by going to " ":menuselection:`Configuration --> Link Tracker`." msgstr "" +"عندما يتم استخدام الروابط في :abbr:`SMS (الرسائل النصية القصيرة)`، يقوم أودو" +" تلقائياً بإنشاء متتبع روابط لجمع البيانات التحليلية والمقاييس المتعلقة بتلك" +" الروابط بالتحديد، والتي يمكن العثور عليها عن طريق الذهاب إلى " +":menuselection:`التهيئة --> متتبع الروابط`. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "SMS Link Tracker page." -msgstr "" +msgstr "صفحة متتبع روابط الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:133 msgid "Adjust SMS settings" -msgstr "" +msgstr "تعديل إعدادات الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:135 msgid "" @@ -4373,26 +4708,34 @@ msgid "" "to :guilabel:`Include opt-out link`. If activated, the recipient is able to " "unsubscribe from the mailing list, thus avoiding all future mailings." msgstr "" +"تحت علامة تبويب :guilabel:`الإعدادات` لقالب الرسائل النصية القصيرة، يوجد " +"خيار لـ :guilabel:`تضمين رابط للانسحاب`. إذا تم تفعيله، سيكون المستلم " +"قادراً على إلغاء اشتراكه في القائمة البريدية، وبالتالي، تجنب كافة الرسائل " +"التي سيتم إرسالها في المستقبل. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:139 msgid "" "An employee can be designated as the :guilabel:`Responsible` in the " ":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." msgstr "" +"يمكن أن يتم تعيين موظف كـ :guilabel:`المسؤول` في قسم :guilabel:`التتبع` في " +"علامة تبويب :guilabel:`الإعدادات` أيضاً. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "SMS Settings tab." -msgstr "" +msgstr "علامة تبويب إعدادات الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:147 msgid "Send SMS messages" -msgstr "" +msgstr "إرسال الرسائل النصية القصيرة " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:149 msgid "" "Once a mailing is created, choose when Odoo should deliver the message from " "the following options:" msgstr "" +"بمجرد أن قد تم إنشاء الرسالة، اختر متى يجب أن يقوم أودو بإيصال الرسالة من " +"الخيارات التالية: " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:151 msgid "" @@ -4400,6 +4743,9 @@ msgid "" "if the recipient list is highly refined, or in cases that involve fast " "approaching deadlines, such as a \"flash sale.\"" msgstr "" +"يؤدي خيار :guilabel:`إرسال`: إلى إرسال الرسالة على الفور. يكون استخدام هذا " +"الخيار مناسباً إذا كانت قائمة المستلمين محددة إلى حد كبير، أو في الحالات " +"التي تتضمن مواعيد نهائية قريبة، مثل \"الخصومات المفاجئة.\" " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:153 msgid "" @@ -4408,6 +4754,10 @@ msgid "" "Such a method can also be used to promote a limited-time offer, or to help " "plan a company's content strategy in advance." msgstr "" +":guilabel:`جدولة`: قم بتحديد يوم (ووقت) يقوم فيه أودو بإرسال الرسائل. عادة " +"ما يكون ذلك الخيار الأمثل للرسائل المتعلقة بفعالية محددة. يمكن استخدام تلك " +"الطريقة للترويج عن عرض لفترة محدودةـ أو للمساعدة في التخطيط لاستراتيجية " +"محتوى الشركة بشكل مسبق. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:156 msgid "" @@ -4415,10 +4765,13 @@ msgid "" "sent to one or multiple numbers for test purposes. Remember to use a comma " "between phone numbers if multiple numbers are used as recipients." msgstr "" +"يتيح خيار :guilabel:`الاختبار`: بأن يتم إرسال :abbr:`SMS (رسالة نصية قصيرة)`" +" إلى عضو أو أكثر بغرض الاختبار. لا تنسَ استخدام فاصلة بين أرقام الهواتف إذا " +"تم استخدام عدة أرقام كمستلمين. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:161 msgid "Visualize reports" -msgstr "" +msgstr "تصوَّر التقارير " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:163 msgid "" @@ -4428,6 +4781,11 @@ msgid "" " to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, " ":guilabel:`List`, and :guilabel:`Cohort` views.)" msgstr "" +"في صفحة :guilabel:`إعداد التقارير` (يمكن الوصول إليها عن طريق خيار " +":menuselection:`إعداد التقارير` في قائمة الترويسة)، توجد خيارات لتطبيق " +"تركيبات مختلفة من :guilabel:`الفلاتر` و :guilabel:`المقاييس` لإظهارها بعدد " +"من طرق العرض والمخططات المختلفة (مثال: طرق عرض :guilabel:`الرسم البياني`، و " +":guilabel:`القائمة`، و:guilabel:`الجماعي`.) " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:168 msgid "" @@ -4442,10 +4800,14 @@ msgid "" "can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop " "down menu)." msgstr "" +"على سبيل المثال، عندما تكون في نافذة عرض :guilabel:`الرسم البياني` " +"الافتراضية، يتم تصوّر بيانات :abbr:`SMS (الرسائل النصية القصيرة)` كرسومات " +"ومخططات بيانية مختلفة، والتي يمكن فرزها وتجميعها بطرق مختلفة (مثال: القائمة " +"المنسدلة لـ :guilabel:`المقاييس`). " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 msgid "Reporting page in SMS Marketing." -msgstr "" +msgstr "صفحة إعداد التقارير في تطبيق التسويق عبر الرسائل النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:180 msgid ":doc:`sms_campaign_settings`" @@ -4457,45 +4819,52 @@ msgstr ":doc:`mailing_lists_blacklists`" #: ../../content/applications/marketing/sms_marketing/pricing.rst:5 msgid "Pricing and FAQ" -msgstr "" +msgstr "الأسعار والأسئلة الشائعة " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 msgid "SMS Pricing and FAQ" -msgstr "" +msgstr "أسعار الرسائل النصية القصيرة والأسئلة الشائعة " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 msgid "What do I need to send SMSs?" -msgstr "" +msgstr "ما الذي أحتاج إليه لإرسال الرسائل النصية القصيرة؟ " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 msgid "" "SMS Text Messaging is an In-App Purchase (IAP) service that *requires " "prepaid credits* to work." msgstr "" +"الرسائل النصية القصيرة هي خدمة عملية شراء داخل التطبيق (IAP) *تتطلب رصيداً " +"مسبق الدفع* حتى تعمل. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 msgid "How many types of SMSs are there?" -msgstr "" +msgstr "كم عدد الرسائل النصية القصيرة الموجودة؟ " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 msgid "There are 2 types: GSM7 and UNICODE." -msgstr "" +msgstr "يوجد نوعان 2: GSM7 و UNICODE. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 msgid "" "**GSM7** is the standard format, with a limit of 160 characters per message," " that includes the following characters:" msgstr "" +"**GSM7** هو التنسيق القياسي، مع 160 رمز كحد أقصى لكل رسالة. يشمل ذلك الرموز " +"التالية: " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 msgid "GSM7 characters available in Odoo SMS Marketing." msgstr "" +"رموز GSM7 متاحة في تطبيق التسويق عبر الرسائل النصية القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 msgid "" "**UNICODE** is the format applied if a special character, that *is not* in " "the GSM7 list, is used. Limit per SMS: 70 characters." msgstr "" +"**UNICODE** هو التنسيق الذي يتم تطبيقه عند استخدام رمز خاص غير موجود في " +"قائمة GSM7. الحد الأقصى لكل رسالة نصية قصيرة: 70 رمز. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 msgid "" @@ -4505,10 +4874,15 @@ msgid "" "in real-time, the system displays the number of SMS mailings the message " "represents." msgstr "" +"بالنسبة للرسائل النصية القصيرة بتنسيق GSM7، أكبر حجم ممكن هو 160 رمز، أما " +"بالنسبة لـ Unicode فهو 70. *سيتم تقسيم محتوى الرسالة إلى عدة رسائل إذا زاد " +"حجمها عن الحد المسموح به* وسيقل الحد الأقصى للرموز إلى 153 بالنسبة لتنسيق " +"GSM7 و 67 لتنسيق Unicode. بعدها، يعرض النظام عدد الرسائل النصية القصيرة التي" +" تمثلها كل رسالة. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 msgid "How much does it cost to send an SMS?" -msgstr "" +msgstr "ما تكلفة إرسال رسالة نصية قصيرة واحدة؟ " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 msgid "" @@ -4517,97 +4891,117 @@ msgid "" "consult**: `Odoo SMS - FAQ `_." msgstr "" +"يعتمد سعر الرسالة النصية الواحدة على الوجهة وعلى طول الرسالة (عدد الرموز). " +"لرؤية **السعر حسب الدولة، ألقِ نظرة على**: `الرسائل النصية القصيرة في أودو -" +" الأسئلة الشائعة `_. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 msgid "" "The number of SMSs a message represents will always be available in the " "database." msgstr "" +"عدد الرسائل النصية القصيرة التي تمثل رسالة واحدة سيكون متاحاً دائماً في " +"قاعدة البيانات. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 msgid "" "Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." msgstr "" +"عدد رموز GSM7 التي تتسع في رسالة نصية قصيرة في تطبيق التسويق عبر الرسائل " +"النصية القصيرة لدى أودو. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 msgid "How to buy credits" -msgstr "" +msgstr "كيفية شراء الرصيد " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 msgid "Go to :menuselection:`Settings --> Buy Credits`." -msgstr "" +msgstr "اذهب إلى :menuselection:`الإعدادات --> شراء رصيد`. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 msgid "Buying credits for SMS Marketing in Odoo settings." msgstr "" +"شراء الرصيد في تطبيق التسويق عبر الرسائل النصية القصيرة، في إعدادات أودو. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 msgid "Or go to :menuselection:`Settings --> View my Services`." -msgstr "" +msgstr "أو اذهب إلى :menuselection:`الإعدادات --> عرض خدماتي`. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." msgstr "" +"استخدام نظام الشراء داخل التطبيق لشحن الرصيد في تطبيق التسويق عبر الرسائل " +"النصية القصيرة، في إعدادات أودو. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 msgid "" "If Odoo Online (Saas) is being used, along with the Enterprise version, free" " trial credits are available to test the feature." msgstr "" +"إذا كان أودو أونلاين (Saas) قيد الاستخدام، بالإضافة إلى إصدار المؤسسات، " +"سيكون هناك رصيد مجاني تجريبي لاختبار الخاصية. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 msgid "More common questions" -msgstr "" +msgstr "المزيد من الأسئلة الشائعة " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Is there an expiration time for my credits?**" -msgstr "" +msgstr "**أيوجد تاريخ انتهاء صلاحية لرصيدي؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "No, credits do not expire." -msgstr "" +msgstr "لا، لا تنتهي صلاحية الأرصدة. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 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 "" +"**أيمكنني إرسال رسالة نصية قصيرة إلى رقم هاتف (ليس رقم هاتف محمول) لأنني أرى" +" الأيقونة أمام حقل \"الهاتف\"؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Only if that phone number supports SMS (e.g. SIP phones)." msgstr "" +"فقط إذا كان رقم الهاتف يدعم الرسائل النصية القصيرة (مثال: هواتف SIP). " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Do I receive an invoice to buy my credits?**" -msgstr "" +msgstr "**هل ستصلني فاتورة لشراء الرصيد؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Yes." -msgstr "" +msgstr "نعم. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can the recipient answer me?**" -msgstr "" +msgstr "**هل بوسع المستلم الرد علي؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "No, it is not possible to reply to the SMS." -msgstr "" +msgstr "لا، لا يمكن الرد على الرسالة النصية القصيرة. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**What happens if I send multiple SMSs at once, but I don't have enough " "credits to send them all?**" msgstr "" +"**ما الذي سيحدث إذا قمت بإرسال عدة رسائل نصية قصيرة في الوقت ذاته، ولكن لم " +"يكن لدي الرصيد الكافي لإرسالها جميعاً؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "Multiple SMS communications at once at are counted as a single transaction, " "so no SMSs will be sent until there are enough credits to send them all." msgstr "" +"تُعد الرسائل النصية القصيرة المتعددة معاملة واحدة، ولذلك لن يتم إرسال أي " +"رسالة نصية قصيرة ما لم يكن لديك الرصيد الكافي لإرسالها جميعاً. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Do I have a history of the sent SMSs?**" -msgstr "" +msgstr "**هل سيكون لدي سجل للرسائل النصية القصيرة المرسلة؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" @@ -4616,6 +5010,11 @@ msgid "" " column of the main :guilabel:`SMS Marketing` dashboard (while in " ":guilabel:`Kanban` view)." msgstr "" +"ستجد سجلاً يحتوي على كافة الرسائل النصية القصيرة المرسلة، بالإضافة إلى " +"معلومات دقيقة حول جهات الاتصال التي قد تم إرسال الرسائل إليها (والرسائل بحد " +"ذاتها)، في عمود :guilabel:`تم الإرسال` في لوحة البيانات الرئيسية لـ " +":guilabel:`التسويق عبر الرسائل النصية القصيرة` (عندما تكون في نافذة عرض " +":guilabel:`كانبان`). " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 msgid "" @@ -4623,20 +5022,26 @@ msgid "" "(in :guilabel:`Kanban` view), and click on either link in the blue banner " "above the SMS detail form to learn more." msgstr "" +"للمزيد من المعلومات التفصيلية، قم بتحديد الرسالة النصية القصيرة المطلوبة من " +"لوحة البيانات الرئيسية (في نافذة عرض :guilabel:`كانبان`)، ثم اضغط على أي " +"الرابطين على العارضة الزرقاء أعلى استمارة تفاصيل الرسائل النصية القصيرة " +"لمعرفة المزيد. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can I send as many SMSs I want at once?**" -msgstr "" +msgstr "**أيمكنني إرسال أي كم أريده من الرسائل النصية القصيرة دفعة واحدة؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Yes, if you have enough credits." -msgstr "" +msgstr "نعم، إذا كنت تملك الرصيد الكافي. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**If an SMS is sent to a number that doesn't exist in the list of " "recipients, will credits be lost?**" msgstr "" +"**إذا تم إرسال رسالة نصية قصيرة إلى رقم غير موجود في قائمة المستلمين، هل " +"سيهدر الرصيد؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" @@ -4644,40 +5049,50 @@ msgid "" " However, if the SMS is sent to the wrong person (or to a fake number), the " "credit for that SMS will be lost." msgstr "" +"لا، إذا كان رقم الهاتف مكتوباً بطريقة خاطئة (مثال: يحتوى على أعداد أكثر مما " +"تحتوي عليه أرقام الهواتف الصحيحة). ولكن، إذا تم إرسال الرسالة النصية القصيرة" +" إلى الشخص الخطأ (أو إلى رقم مزيف)، سيضيع الرصيد الذي تم استخدامع لإرسالها. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**What happens if I send my SMS to a paying number (e.g.: a contest to win a" " ticket for a festival)?**" msgstr "" +"**ماذا سيحدث إذا قمت بإرسال الرسالة النصية القصيرة إلى رقم مدفوع (مثال: " +"مسابقة للفوز بتذاكر لحضور مهرجان)؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "The SMS will not be delivered to that kind of number, so no charges will be " "made." msgstr "" +"لن يتم إيصال الرسالة النصية القصيرة إلى ذلك النوع من الأرقام، وبالتالي، لن " +"يحدث أي تغيير. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "**Can I identify the numbers that do not exist when I send several SMSs?**" msgstr "" +"**أيمكنني تمييز الأرقام غير الموجودة عندما أقوم بإرسال عدة رسائل نصية " +"قصيرة؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "Only the ones that have an invalid format." -msgstr "" +msgstr "فقط الأرقام المكتوبة بتنسيق غير صحيح. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**How does the GDPR regulation affect this service?**" -msgstr "" +msgstr "**كيف تؤثر لوائح GDPR على هذه الخدمة؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" "Please find our `Privacy Policy here `__." msgstr "" +"ألقِ نظرة على `سياسة الخصوصية هنا `__. " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "**Can I use my own SMS provider?**" -msgstr "" +msgstr "**أيمكنني استخدام مزود الرسائل النصية القصيرة الخاص بي؟** " #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 msgid "" @@ -4685,6 +5100,9 @@ msgid "" "a database to allow for the use of a personal SMS provider. Please check our" " success packs `here `_." msgstr "" +"نعم، ولكن لا يمكن القيام بذلك مباشرة دون إعداد. بإمكان خبراء أودو المساعدة " +"في تخصيص قاعدة البيانات للسماح باستخدام مزود رسائل نصية قصيرة خاص. ألقِ نظرة" +" على باقاتنا الاستشارية `هنا `_. " #: ../../content/applications/marketing/social_marketing.rst:8 msgid "Social Marketing" @@ -4692,7 +5110,7 @@ msgstr "التسويق على وسائل التواصل الإجتماعي" #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 msgid "Social marketing campaigns" -msgstr "" +msgstr "حملات التسويق الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 msgid "" @@ -4701,6 +5119,9 @@ msgid "" "customers, explaining the value of a product or service, or when advertising" " an upcoming event or product release." msgstr "" +"تساعد حملات التسويق الاجتماعي الشركات على الاتصال مباشرة بالسوق. تكون تلك " +"الحملات مفيدة عندما التعريف بمنتج جديد إلى العملاء، أو إيضاح قيمة منتج أو " +"خدمة، أو عند الإعلان عن فعالية قادمة أو إصدار منتج. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 msgid "" @@ -4710,6 +5131,10 @@ msgid "" " and analyze all of the various content and content channels within a single" " dashboard." msgstr "" +"أكثر حملات التسويق الاجتماعي فعالية تتضمن عادةً عدة قنوات لتوزيع المحتوى " +"لأوسع مدى، ويعمل تطبيق *التسويق الاجتماعي* لدى أودو كمركز تحكم واحد للمراقبة" +" والتخطيط وتتبع وتحليل المحتوى أالمختلف وقنوات المحتوى في لوحة بيانات واحدة." +" " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 msgid "" @@ -4718,10 +5143,14 @@ msgid "" ":menuselection:`Campaigns` from the header menu. Doing so reveals a separate" " page with every campaign in a default kanban view." msgstr "" +"لتحصل على نظرة عامة كاملة على كافة حملات التسويق الاجتماعي، افتح تطبيق " +":menuselection:`التسويق الاجتماعي` ثم اضغط على :menuselection:`الحملات` من " +"القائمة الرئيسية. يؤدي القيام بذلك إلى الكشف عن صفحة منفصلة تحتوي على كل " +"حملة معروضة بطريقة عرض كانبان الافتراضية. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 msgid "View of the campaigns page in the Odoo Social Marketing application." -msgstr "" +msgstr "نظرة عامة على صفحة الحملات في تطبيق التسويق الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 msgid "" @@ -4729,6 +5158,9 @@ msgid "" ":guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located" " to the right of the stage title." msgstr "" +"يمكن تحرير كل *مرحلة* في عرض كانبان، عن طريق الضغط على :guilabel:`أيقونة " +"الترس` الموجودة يسار :guilabel:`+ (علامة الزائد)` - الموجودة يمين عنوان " +"المرحلة. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 msgid "" @@ -4737,6 +5169,9 @@ msgid "" "the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and " ":guilabel:`Delete`." msgstr "" +"تظهر **أيقونة الترس** *فقط* عند تحريك المؤشر إلى يسار **+ (علامة زائد)**. " +"عند الضغط على أيقونة الترس، تظهر قائمة منسدلة الخيارات التالية: " +":guilabel:`طي`، :guilabel:`تحرير المرحلة`، و:guilabel:`حذف`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 msgid "" @@ -4744,6 +5179,9 @@ msgid "" "column can be restored by clicking the folded version of it on the main " ":guilabel:`Campaigns` dashboard in the default kanban view." msgstr "" +"يؤدي الضغط على :guilabel:`طي` إلى تصغير عمود تلك المرحلة المحددة. يمكن " +"استعادة عمود المرحلة عن طريق النقر على النسخة المطوية منه في لوحة التحكم " +"الرئيسية :guilabel:`الحملات` في طريقة عرض كانبان الافتراضية. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 msgid "" @@ -4751,10 +5189,13 @@ msgid "" "and the sequence of the stage can be modified. If changes are made, be sure " "to click :guilabel:`Save`." msgstr "" +"يؤدي تحديد خيار :guilabel:`تحرير المرحلة` إلى ظهور نافذة منبثقة، حيث يمكن " +"تعديل اسم وتسلسل المرحلة. إذا تم إجراء أي تغييرات، لا تنسَ الضغط على " +":guilabel:`حفظ`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 msgid "Clicking :guilabel:`Delete` removes the stage entirely." -msgstr "" +msgstr "يؤدي الضغط على زر :guilabel:`حذف` إلى إزالة المرحلة تماماً. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 msgid "" @@ -4762,6 +5203,9 @@ msgid "" ":guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in " "the desired information, and click :guilabel:`Add`." msgstr "" +"لإضافة مرحلة جديدة إلى مخطط سير العمل، قم بالتمرير جانبياً إلى اليمين في " +"لوحة بيانات :guilabel:`الحملات`، ثم اضغط على :guilabel:`إضافة عمود`، وأدخل " +"المعلومات المطلوبة، ثم اضغط على :guilabel:`إضافة`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 msgid "" @@ -4769,16 +5213,21 @@ msgid "" "dashboard can also be viewed as a list, by selecting the :guilabel:`List` " "option, located under the search bar, in the upper-right corner." msgstr "" +"يمكن أيضاً عرض نفس معلومات حملة التسويق الاجتماعي الموجودة في لوحة بيانات " +":guilabel:`الحملات` كقائمة، عن طريق تحديد خيار :guilabel:`قائمة`، الموجود " +"أسفل شريط البحث، في الزاوية العلوية اليمنى. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 msgid "Create social marketing campaigns" -msgstr "" +msgstr "إنشاء حملات تسويق اجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 msgid "" "First, open the :menuselection:`Social Marketing` application, and select " ":guilabel:`Campaigns` from the header menu." msgstr "" +"أولا، قم بفتح تطبيق :menuselection:`التسويق الاجتماعي` وقم بتحديد " +":guilabel:`الحملات` من قائمة الترويسة. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 msgid "" @@ -4788,16 +5237,25 @@ msgid "" "can also be created by clicking :guilabel:`Create` in the upper-left corner " "of the :guilabel:`Campaigns` dashboard." msgstr "" +"في لوحة بيانات :guilabel:`الحملات`، يمكن إنشاء حملة جديدة عن طريق الضغط على " +"علامة الإضافة السريعة :guilabel:`+ (علامة زائد)` الموجودة في الزاوية العلوية" +" إلى اليمين لكل مرحلة في مخطط سير العمل، وتكون مرئية في نافذة عرض كانبان. " +"يمكن أيضاً إنشاء الحملات عن طريق الضغط على :guilabel:`إنشاء` في الزاوية " +"العلوية إلى اليسار للوحة بيانات :guilabel:`الحملات`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 msgid "" "Both options reveal a new campaign detail window directly on the " ":guilabel:`Campaigns` dashboard when clicked." msgstr "" +"يُظهِر كلا الخيارين نافذة جديدة بها تفاصيل الحملة، مباشرة على لوحة بيانات " +":guilabel:`الحملات` عند الضغط عليهما. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 msgid "View of the quick add option for campaigns in Odoo Social Marketing." msgstr "" +"نظرة عامة على خيار الإضافة السريعة للحملات في تطبيق التسويق الاجتماعي لدى " +"أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 msgid "" @@ -4805,10 +5263,13 @@ msgid "" ":guilabel:`Tags` can be entered. When all modifications are complete, click " ":guilabel:`Add` to add the campaign to the database." msgstr "" +"يمكن هنا إدخال :guilabel:`اسم الحملة` و :guilabel:`المسؤول` و " +":guilabel:`علامات التصنيف`. عند الانتهاء من كافة التعديلات، اضغط على زر " +":guilabel:`إضافة` لإضافة القائمة إلى قاعدة البيانات. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 msgid "Edit social marketing campaigns" -msgstr "" +msgstr "تحرير حملات التسويق الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 msgid "" @@ -4817,18 +5278,25 @@ msgid "" "be accessed and modified, accordingly. There are multiple ways to access a " "template page for a campaign." msgstr "" +"حتى تتمكن من تحرير الحملة بتفاصيل أكثر، وإنشاء/إرسال سبل تواصل مختلفة متعلقة" +" بها، يجب الوصول إلى صفحة قالب تلك الحملة وتعديلها كما يجب. توجد عدة طرق " +"للوصول إلى صفحة قالب حملة. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 msgid "" "After entering the pertinent information in the :guilabel:`Quick Add` " "campaign drop-down, click :guilabel:`Edit`." msgstr "" +"بعد إدخال المعلومات الدقيقة في القائمة المنسدلة :guilabel:`الإضافة السريعة` " +"في الحملة، اضغط على :guilabel:`تحرير`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 msgid "" "Simply select the desired campaign from the :guilabel:`Campaigns` dashboard " "in list or kanban view." msgstr "" +"بكل بساطة، قم بتحديد الحملة المطلوبة من لوحة بيانات :guilabel:`الحملات` في " +"نافذتي عرض القائمة أو كانبان. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 msgid "" @@ -4836,16 +5304,20 @@ msgid "" ":guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and " "select :guilabel:`Edit`." msgstr "" +"في لوحة بيانات :guilabel:`الحملات` في نافذة عرض كانبان، قم بتحديد قائمة " +":guilabel:`⋮ (النقاط الرأسية الثلاث)` المنسدلة في الحملة المطلوبة، ثم قم " +"بتحديد خيار :guilabel:`تحرير`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 msgid "" "Any of the above routes will reveal the *Campaign Template* page for that " "specific campaign." msgstr "" +"ستُظهِر أي من المسارات أعلاه صفحة *قالب الحملة* لتلك الحملة بالتحديد. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 msgid "Social marketing campaign templates" -msgstr "" +msgstr "قوالب حملة التسويق الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 msgid "" @@ -4853,10 +5325,14 @@ msgid "" " and various forms of communications can be created, modified, and sent or " "scheduled. Below is a sample of a completed campaign template." msgstr "" +"في صفحة *قالب الحملة*، يمكن تخصيص العديد من العناصر أو تعديلها، ويمكن إنشاء " +"العديد من وسائل التواصل أو تعديلها أو إرسالها أو جدولتها. ستجد أدناه مثالاً " +"على قالب حملة مكتمل. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 msgid "View of a sample campaign template page in Odoo Social Marketing." msgstr "" +"نظرة عامة على صفحة قالب حملة تجريبي في تطبيق التسويق الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 msgid "" @@ -4866,16 +5342,23 @@ msgid "" "Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing " "Campaigns`, and click :guilabel:`Save`." msgstr "" +"حتى يظهر خيار :guilabel:`إرسال رسالة جديدة` في قوالب الحملة، تأكد من أن " +"خاصية *الحملات البريدية* قد تم تمكينها في تطبيق التسويق عبر البريد " +"الإلكتروني. للقيام بذلك، اذهب إلى :menuselection:`التسويق عبر البريد " +"الإلكتروني --> التهيئة --> لإعدادات`، ثم تفعيل :guilabel:`الحملات " +"البريدية`، والضغط على زر :guilabel:`حفظ`.- " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 msgid "" "In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS " "Marketing* application must be installed on the database." msgstr "" +"حتى يظهر خيار :guilabel:`إرسال رسالة نصية قصيرة`، يجب أن يتم تثبيت تطبيق " +"*التسويق عبر الرسائل النصية القصيرة* في قاعدة البيانات. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 msgid "Add content and communications to campaigns" -msgstr "" +msgstr "إضافة المحتوى وسبل التواصل إلى الحملات " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 msgid "" @@ -4884,18 +5367,25 @@ msgid "" "campaigns. Each of these options are displayed as buttons in the upper-left " "corner of the campaign template page." msgstr "" +"إذا تم تثبيت الإعدادات والتطبيقات المناسبة (كما هو موضح أعلاه)، توجد أربع " +"وسائل تواصل/أنواع محتوى يمكن إضافته إلى الحملات. يتم عرض كل من تلك الخيارات " +"كزر في الزاوية العلوية إلى اليسار في صفحة قالب الحملة. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 msgid "" ":guilabel:`Send New Mailing`: reveals a blank email template on a separate " "page, in which the message can be fully customized in a variety of ways." msgstr "" +"يُظهِر خيار :guilabel:`إرسال رسالة جديدة` قالب بريد إلكتروني فارغ في صفحة " +"منفصلة، حيث يمكن تخصيص الرسالة بشكل كامل بطرق مختلفة. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 msgid "" ":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in " "which a SMS communication can be created and configured." msgstr "" +"يُظهِر خيار :guilabel:`إرسال رسالة نصية قصيرة` قالب رسالة نصية قصيرة فارغ في" +" صفحة منفصلة، حيث يمكن إنشاء الرسالة النصية القصيرة وتهيئتها. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 msgid "" @@ -4903,6 +5393,9 @@ msgid "" "separate page, in which a post can be created, and applied to social media " "accounts that are already connected to the database." msgstr "" +"يُظهِر خيار :guilabel:`إرسال منشور اب منشور اجتماعي فارغ في صفحة منفصلة، حيث" +" يمكن إنشاء منشور ونشره على حسابات التواصل الاجتماعي المتصلة بالفعل بقاعدة " +"البيانات. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 msgid "" @@ -4910,6 +5403,9 @@ msgid "" "on a separate page, however, the :guilabel:`Push Notification` options are " "already pre-selected in the :guilabel:`Post on` field." msgstr "" +"يُظهِر :guilabel:`الإشعار المنبثق` قالب منشور اجتماعي فارغ شبيه في صفحة " +"مختلفة، ولكن، خيارات :guilabel:`الإشعار المنبثق` محددة بالفعل في حقل " +":guilabel:`النشر في`. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 msgid "" @@ -4919,6 +5415,10 @@ msgid "" ":guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push " "Notifications`)." msgstr "" +"أياً كان شكل الاتصال الذي يتم إنشاؤه، بمجرد اكتماله، يعود أودو إلى صفحة " +":guilabel:`قالب الحملة`، ويعرض ذلك المحتوى الجديد في علامة التبويب المقابلة " +"له (مثال: :guilabel:`المراسلات`، :guilabel:`الرسائل النصية القصيرة`، " +":guilabel :`وسائل التواصل الاجتماعي` و/أو :guilabel:`الإشعارات المنبثقة`). " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 msgid "" @@ -4927,6 +5427,10 @@ msgid "" "(e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, " "etc.)." msgstr "" +"عند إضافة المحتوى والاتصالات إلى الحملة، تظهر علامات التبويب الخاصة بتلك " +"الوسائط المحددة، إضافة إلى مجموعة متنوعة من الأزرار التحليلية الذكية (مثال: " +":guilabel:`الإيرادات`، :guilabel:`عروض الأسعار`، :guilabel:`العملاء " +"المهتمين`، إلخ. ). " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 msgid "" @@ -4936,12 +5440,18 @@ msgid "" "particular element of the campaign, allowing for quicker, more organized " "analysis." msgstr "" +"تعرض هذه الأزرار الذكية، الموجودة أعلى القالب، مقاييس مختلفة تتعلق بالحملة " +"واتصالاتها ومحتواها المتنوع. يؤدي الضغط على أي زر ذكي إلى ظهور صفحة منفصلة " +"مخصصة لذلك العنصر المحدد من الحملة، مما يسمح بإجراء تحليل أسرع وأكثر " +"تنظيماً. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 msgid "" "The Odoo *Social Marketing* app is integrated with other Odoo applications, " "such as *Sales*, *Invoicing*, *CRM*, and *Website*." msgstr "" +"تطبيق *التسويق الاجتماعي* لدى أودو مدمج مع تطبيقات أودو الأخرى، مثل " +"*المبيعات* و*الفوترة* و*إدارة علاقات العملاء* و*الموقع الإلكتروني*. " #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 msgid "" @@ -4951,7 +5461,7 @@ msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 msgid "Social marketing essentials" -msgstr "" +msgstr "أساسيات التسويق الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 msgid "" @@ -4960,10 +5470,13 @@ msgid "" "effectiveness, and engage directly with social media followers in one, " "centralized location." msgstr "" +"يساعد تطبيق *التسويق الاجتماعي* لدى أودو مسوّقي المحتوى على إنشاء وجدولة " +"المنشورات وإدارة مختلف حسابات الوسائط الاجتماعية وتحليل مدى فاعلية المحتوى " +"والتفاعل مباشرة مع متابعي الوسائط الاجتماعية، في مكان واحد مركزي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 msgid "Social media accounts" -msgstr "" +msgstr "حسابات الوسائط الاجتماعية " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 msgid "" @@ -4971,6 +5484,9 @@ msgid "" "Marketing*, social media accounts **must** be added as a *stream* on the " "application's main dashboard." msgstr "" +"حتى تتمكن من إنشاء منشورات اجتماعية وتحليل المحتوى باستخدام تطبيق *التسويق " +"الاجتماعي* لدى أودو، **يجب** أن تتم إضافة حسابات الوسائط الاجتماعية كـ " +"*وسائط* في لوحة البيانات الرئيسية للتطبيق. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 msgid "" @@ -4978,6 +5494,9 @@ msgid "" "use of Odoo *Social Marketing* is to manage and analyze business accounts on" " social media platforms." msgstr "" +"لا تنسَ أنه **لا يمكن** إضافة ملفات التعريف الشخصية كوسائط. الاستخدام " +"الأساسي لتطبيق *التسويق الاجتماعي* لدى أودو هو إدارة وتحليل حسابات الأعمال " +"على منصات التواصل الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:20 msgid "" @@ -4987,12 +5506,19 @@ msgid "" "present in a multi-company environment because of how the API is " "constructed." msgstr "" +"تطبيق *التسويق الاجتماعي* لدى أودو به بعض التقييدات فيما يتعلق بحسابات " +"التواصل الاجتماعي. على سبيل المثال، **لا يستطيع** أودو التعامل مع الكميات " +"الكبيرة من الصفحات المختلفة (مثال: ~40صفحة) ضمن نفس الشركة. نفس التقييدات " +"موجودة في البيئات متعددة الشركات، نظراً للطريقة التي تم تصميم الواجهة " +"البرمجية بها. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:26 msgid "" "In multi-company environments, if every company doesn't activate a page at " "once, it will result in a permission error." msgstr "" +"في البيئات متعددة الشركات، إذا لم تقم كل شركة بتفعيل صفحة مرة واحدة، سيتسبب " +"ذلك في خطأ في الإذن. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 msgid "" @@ -5000,6 +5526,10 @@ msgid "" "dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those" " pages will be accesible on the *Social Marketing* dashboard." msgstr "" +"على سبيل المثال، إذا كانت الشركة 1 هي الشركة الوحيدة التي قد تم تحديدها من " +"لوحة البيانات الرئيسية لدى أودو، وقامت بتفعيل *صفحة فيسبوك 1* و*صفحة فيسبوك " +"2*، عندها سيكون من الممكن الوصول إلى تلك الصفحات على لوحة بيانات تطبيق " +"*التسويق الاجتماعي*. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:33 msgid "" @@ -5007,16 +5537,20 @@ msgid "" "drop-down menu in the header, and attempts to add those same streams, it " "results in a permission error." msgstr "" +"ولكن، إذا قام المستخدم بإضافة الشركة 2 في نفس قاعدة البيانات من القائمة " +"المنسدلة للشركة الموجودة في الترويسة، وحاول إضافة تلك الوسائط ذاتها، يؤدي " +"ذلك إذا خطأ في الإذن. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 msgid "" "View of the permission error that appears when incorrectly attempting to add" " stream." msgstr "" +"نظرة عامة على خطأ الإذن الذي يظهر عند محاولة إضافة وسائط بشكل غير صحيح. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:41 msgid "Social media streams" -msgstr "" +msgstr "وسائط التواصل الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:43 msgid "" @@ -5025,12 +5559,18 @@ msgid "" "Stream` button located in the upper-left corner. Doing so reveals an " ":guilabel:`Add a Stream` pop-up window." msgstr "" +"لإضافة حساب التواصل الاجتماعي للأعمال كأحد الوسائط، اذهب إلى " +":menuselection:`تطبيق التسويق الاجتماعي` ثم قم بالضغط على زر " +":guilabel:`إضافة وسائط` الموجود في الزاوية العلوية إلى اليسار. سيؤدي القيام " +"بذلك إلى إظهار النافذة المنبثقة :guilabel:إضافة وسائط`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "View of the pop-up window that appears when Add a Stream is selected in " "Odoo." msgstr "" +"نظرة عامة على النافذة المنبثقة التي تظهر عندما يتم تحديد خيار إضافة وسائط في" +" أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:51 msgid "" @@ -5039,6 +5579,10 @@ msgid "" "platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, " ":guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`." msgstr "" +"في النافذة المنبثقة التي تُظهِر خيار :guilabel:`إضافة وسائط`، اختر " +":guilabel:`ربط حساب جديد` للأعمال من أي من منصات التواصل الاجتماعي المعروفة " +"التالية: :guilabel:`Facebook` و :guilabel:`Instagram` و :guilabel:`LinkedIn`" +" و :guilabel:`Twitter` و :guilabel:`YouTube`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:55 msgid "" @@ -5048,12 +5592,18 @@ msgid "" " Odoo to add that particular social media account as a stream to the *Social" " Marketing* application." msgstr "" +"بعض الغط على منصة التواص الاجتماعي المطلوبة من النافذة المنبثقة " +":guilabel:`إضافة وسائط`، يأخذك أودو مباشرة إلى صفحة تفويض منصة التواصل " +"الاجتماعي تلك، حيث يجب منح الأذونات حتى يتمكن أودو من إضافة حساب التواصل " +"الاجتماعي ذاك كأحد الوسائط في تطبيق *التسويق الاجتماعي*. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Sample of a populated social marketing dashboard with social media streams " "and content." msgstr "" +"مثال على لوحة بيانات تسويق اجتماعي تم إنشاؤها مع محتوى ووسائط تواصل اجتماعي." +" " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 msgid "" @@ -5061,6 +5611,9 @@ msgid "" "the main :guilabel:`Social Marketing` dashboard, and a new column, with that" " account's posts, is added. Accounts/streams can be added at any time." msgstr "" +"بمجرد أن قد تم منح الاذن، يعود بك أودو إلى :guilabel:`الموجزات` في لوحة " +"البيانات الرئيسية لـ :guilabel:`التسويق الاجتماعي`، وتتم إضافة عمود جديد " +"يحتوي على منشورات ذلك الحساب. يمكن إضافة الحسابات/الوسائط في أي وقت. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:69 msgid "" @@ -5068,6 +5621,9 @@ msgid "" " account that grants permission is the administrator for the page. It should" " also be noted that different pages can be added for different streams." msgstr "" +"يمكن إضافة صفحة :guilabel:`Facebook` كالما أن حساب :guilabel:`Facebook` الذي" +" يمنح الإذن هو حساب المدير. يُرجى العلم أيضاً بأنه يمكن إضافة صفحات مختلفة " +"للوسائط المختلفة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:74 msgid "" @@ -5076,6 +5632,10 @@ msgid "" "account needs to be linked to a :guilabel:`Facebook` account in order for it" " to show up as a stream in Odoo." msgstr "" +"تتم إضافة حسابات :guilabel:`Instagram` باستخدام بيانات تسجيل الدخول الخاصة " +"بـ :guilabel:`Facebook` لأنها تستخدم نفس الواجهة البرمجية. هذا يعني أن حساب " +":guilabel:`Instagram` يجب أن يكون مرتبطاً بحساب :guilabel:`Facebook` حتى " +"يظهر كأحد الوسائط في أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:79 msgid "Posts" @@ -5087,12 +5647,17 @@ msgid "" "showcasing the content of that specific post, along with all the engagement " "data related to it (e.g. likes, comments, etc.)." msgstr "" +"يؤدي الضغط على منشور في إحدى وسائط التواصل الاجتماعي إلى الكشف عن نافذة " +"منبثقة تُظهِر محتوى ذلك المنشور بالتحديد، بالإضافة إلى كافة معلومات التفاعل " +"المتعلقة به (الإعجابات، التعليقات، إلخ). " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Sample of a social media post's pop-up window in Odoo Social Marketing " "application." msgstr "" +"مثال على نافذة منبثقة بها منشور اجتماعي، في تطبيق التسويق الاجتماعي لدى " +"أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:88 msgid "" @@ -5100,16 +5665,21 @@ msgid "" "pop-up window, by typing one in the :guilabel:`Write a comment...` field, " "and clicking :guilabel:`Enter` to post that comment." msgstr "" +"إذا أراد المستخدم، بوسعه ترك تعليق جديد في المنشور من النافذة المنبثقة " +"للمنشور، عن طريق كتابة تعليق في حقل :guilabel:`اكتب تعليقاً...`، ثم الضغط " +"على :guilabel:`إدخال` لنشر ذلك التعليق. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:93 msgid "Create leads from comments" -msgstr "" +msgstr "الحصول على العملاء المهتمين من التعليقات " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:95 msgid "" "Odoo *Social Marketing* also provides the ability to create leads directly " "from social media comments." msgstr "" +"يقدم تطبيق التسويق الاجتماعي لدى أودو أيضاً إمكانية إنشاء العملاء المهتمين " +"مباشرة من تعليقات مواقع التةاصل الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:98 msgid "" @@ -5118,28 +5688,38 @@ msgid "" "window. Then, scroll to the desired comment, and click the :guilabel:`three " "vertical dots` icon to the right of that comment." msgstr "" +"لإنشاء عميل مهتم من تعليق مكتوب في إحدى المنشورات الاجتماعية، اضغط على " +"المنشور المطلوب من لوحة البيانات لإظهار النافذة المنبثقة الخاصة بذلك " +"المنشور. بعد ذلك، قم بالتمرير للتعليق المطلوب ثم اضغط على أيقونة " +":guilabel:`النقاط الرأسية الثلاث` يسار ذلك التعليق. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:102 msgid "" "Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." msgstr "" +"سيؤدي القيام بذلك إلى الكشف عن قائمة منسدلة بها خيار: :guilabel:`إنشاء عميل " +"مهتم`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "The drop-down menu beside a comment revealing the option to create a lead." -msgstr "" +msgstr "تُظهِر القائمة المنسدلة بجانب التعليق خيار إنشاء عميل مهتم. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:108 msgid "" "Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a " ":guilabel:`Conver Post to Lead` pop-up window appears." msgstr "" +"عند الضغط على زر :guilabel:`إنشاء عميل مهتم` من القائمة المنسدلة للتعليق، " +"ستظهر نافذة منبثقة لـ :guilabel:`تحويل المنشور إلى عميل مهتم`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "The convert post to lead pop-up window that appears in Odoo Social " "Marketing." msgstr "" +"النافذة المنبثقة لتحويل المنشور إلى عميل مهتم، التي تظهر في تطبيق التسويق " +"الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:115 msgid "" @@ -5147,6 +5727,8 @@ msgid "" ":guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a " "customer`." msgstr "" +"في هذه النافذة المنبثقة، اختر إما :guilabel:`إنشاء عميل جديد` أو " +":guilabel:`الربط بعميل موجود` أو :guilabel:`عدم الربط بعميل`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:119 msgid "" @@ -5154,6 +5736,9 @@ msgid "" ":guilabel:`Customer` field appears beneath those options, wherein a customer" " can be chosen to be linked to this lead." msgstr "" +"إذا تم تحديد خيار :guilabel:`الربط بعميل موجود`، سيظهر حقل جديد لـ " +":guilabel:`العميل` أسفل تلك الخيارات، حيث يمكن أن يتم اختيار العملاء ليتم " +"ربطهم بهذا العميل المهتم. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 msgid "" @@ -5162,12 +5747,18 @@ msgid "" "Doing so reveals a fresh lead detail form, where the necessary information " "can be entered and processed." msgstr "" +"بمجرد أن قد تم تحديد الخيار المطلوب، اضغط على زر :guilabel:`تحويل` أسفل " +"النافذة المنبثقة :guilabel:`تحويل المنشور إلى عميل معتم`. يؤدي القيام بذلك " +"إلى الكشف عن استمارة جديدة لبيانات العميل المهتم، حيث يُمكن إدخال المعلومات " +"المهمة ومعالجتها. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "New lead detail form generated from a social media comment in Odoo Social " "Marketing." msgstr "" +"استمارة عميل مهتم جديدة تم إنشاؤها من تعليق على إحدى المنشورات الاجتماعية " +"على تطبيق التسويق الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:131 msgid "Insights" @@ -5179,6 +5770,9 @@ msgid "" "dashboard, each stream also displays and links that specific social media " "platform's KPIs (if the platform has them)." msgstr "" +"عندما تتم إضافة حساب تواصل اجتماعي إلى لوحة بيانات *التسويق الاجتماعي*، تعرض" +" وتربط كل من الوسائط مؤشرات الأداء الرئيسية لمنصة التواصل الاجتماعي (إذا " +"كانت المنصة تملك مؤشرات للأداء). " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:136 msgid "" @@ -5186,18 +5780,24 @@ msgid "" "account's KPIs, click on the :guilabel:`Insights` link, located at the top " "of each stream." msgstr "" +"حتى تتم إعادة توجيهك إلى الإحصائيات والمقاييس المتعلقة بمؤشرات الأداء " +"الرئيسية لوسائل التواصل الاجتماعي، اضغط على رابط :guilabel:`الرؤى` المتواجد " +"أعلى كل من الوسائط. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Visual of how the Insights link appears on the dashboard of the Social " "Marketing app." msgstr "" +"تمثيل لكيفية ظهور رابط الرؤى على لوحة بيانات تطبيق التسويق الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 msgid "" "In a multi-company environment, if not *all* pages are selected, de-" "authentication happens." msgstr "" +"في البيئة متعددة الشركات، إذا لم يتم تحديد *كافة* الصفحات، سيتم إلغاء " +"المصادقة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:146 msgid "" @@ -5206,6 +5806,9 @@ msgid "" "authenticated, and access to the initial page's insights/analytics will be " "lost." msgstr "" +"على سبيل المثال، إذا كان للشركات 3 صفحات *Facebook*، ولكن تمنح صلاحيات " +"الوصول إلى 1 فقط وتحاول منح صلاحية الوصول إلى أخرى في وقت لاحق، سيتم إلغاء " +"المصادقة وستضيع صلاحيات الوصول إلى رؤى/تحليلات الصفحة الأولى. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:150 msgid "" @@ -5213,16 +5816,21 @@ msgid "" "environment to avoid this issue. If a page gets de-autenticated, simply " "remove the stream, and re-establish it." msgstr "" +"ولذلك، تأكد من إضافة *كافة* الصفحات *لكافة* الشركات في البيئة متعددة الشركات" +" لتجنب هذه المشكلة. إذا تم إلغاء مصادقة صفحة، ببساطة قم بإزالة تلك المنصة " +"وقم بإعدادها مجدداً. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:154 msgid "Create and post social media content" -msgstr "" +msgstr "قم بإنشاء ونشر محتوى التواصل الاجتماعي " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:156 msgid "" "Odoo *Social Marketing* offers the ability to create and post content for " "social media accounts directly through the application." msgstr "" +"يمنحك تطبيق *التسويق الاجتماعي* لدى أودو إمكانية إنشاء ونشر المحتوى لحسابات " +"التواصل الاجتماعي من خلال التطبيق مباشرة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:159 msgid "" @@ -5230,24 +5838,32 @@ msgid "" ":menuselection:`Social Marketing app`, and click :guilabel:`New Post` " "located in the upper-right corner of the *Social Marketing* dashboard." msgstr "" +"لإنشاء محتوى لحسابات التواصل الاجتماعي، اذهب إلى :guilabel:`تطبيق التسويق " +"الاجتماعي` ثم اضغط على زر :guilabel:`منشور جديد` الموجود في الزاوية العلوية " +"إلى اليمين، في لوحة بيانات *التسويق الاجتماعي*. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "New Post button on the main dashboard of the Odoo Social Marketing " "application." msgstr "" +"زر \"منشور جديد\" في لوحة البيانات الأرئيسية لتطبيق التسويق الاجتماعي لدى " +"أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:167 msgid "" "Or, navigate to :menuselection:`Social Marketing app --> Posts` and click " "the :guilabel:`New` button." msgstr "" +"أو انتقل إلى :menuselection:`تطبيق التسويق الاجتماعي --> المنشورات` ثم اضغط " +"على زر :guilabel:`جديد`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "New button on the Social Posts page in the Odoo Social Marketing " "application." msgstr "" +"زر جديد في صفحةالمنشورات الاجتماعية في تطبيق التسويق الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:174 msgid "" @@ -5261,13 +5877,14 @@ msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 msgid "Post detail form" -msgstr "" +msgstr "استمارة تفاصيل المنشور " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:184 msgid "" "The social media post detail form in Odoo *Social Marketing* has many " "different configurable options available." msgstr "" +"استمارة تفاصيل منشور *التسويق الاجتماعي* لها عدة خيارات تهيئة مختلفة متاحة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:188 msgid "Company" @@ -5280,6 +5897,9 @@ msgid "" ":guilabel:`Company`. In this field, select the company that should be " "connected to this specific social media post." msgstr "" +"إذا كنت تعمل في بيئة متعددة الشركات، أول حقل في قسم :guilabel:`منشورك` " +"لاستمارة تفاصيل المنشور الاجتماعي هو :guilabel:`الشركة`. في ذلك الحقل، قم " +"بتحديد الشركة التي يجب أو يتم وصلها بمنشور التواصل الاجتماعي هذا بالتحديد. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:195 msgid "Post on" @@ -5294,6 +5914,11 @@ msgid "" "visitors this post should be sent to, via push notification, by checking the" " box beside the desired option(s)." msgstr "" +"إذا كنت تعمل في بيئة ذات شركة واحدة، سيكون أول حقل في قسم :guilabel:`منشورك`" +" في استمارة تفاصيل المنشور الاجتماعي :guilabel:`النشر على`. في ذلك الحقل، قم" +" بتحديد أي منصات (الوسائط الاجتماعية) من المفترض أن يتم نشر ذلك المنشور " +"عليه، و/أو أي زائري الموقع الإلكتروني يجب أن يتم إرسال هذا المنشور إليه عن " +"طريق الإشعارات المنبثقة عن طريق تحديد الخيار المطلوب. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 msgid "" @@ -5302,6 +5927,9 @@ msgid "" "account hasn't been added as a stream to the *Social Marketing* application," " it will **not** appear as an option on the post template." msgstr "" +"يقدم أودو تلقائياً كل حساب تواصل اجتماعي متاح مرتبط بقاعدة البيانات كخيار في" +" هذا القسم. إذا لم تتم إضافة حساب تواصل اجتماعي كأحد الوسائط في تطبيق " +"*التسويق الاجتماعي*، **لن** يظهر كخيار في قالب المنشور. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 msgid "" @@ -5309,6 +5937,8 @@ msgid "" ":guilabel:`Post on` field. At least **one** option in the :guilabel:`Post " "on` field *must* be selected." msgstr "" +"يمكن تحديد عدة منصات (مسارات) تواصل اجتماعي في حقل :guilabel:`النشر على`. " +"يجب أن يتم تحديد- خيار **واحد** على الأقل في حقل :guilabel:`النشر على`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:210 msgid "" @@ -5316,6 +5946,9 @@ msgid "" "social media post detail form in Odoo *Social Marketing*, make sure the " "*Enable Web Push Notifications* feature is enabled in the *Website* app." msgstr "" +"حتى يظهر خيار :guilabel:`الإشعارات المنبثقة` على استمارة تفاصيل المنشور " +"الاجتماعي في تطبيق *التسويق الاجتماعي* لدى أودو، تأكد من أن خاصية *تمكين " +"إشعارات الويب المنبثقة* قد تم تمكينه في تطبيق *الموقع الإلكتروني*. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:214 msgid "" @@ -5323,6 +5956,9 @@ msgid "" "Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the " "corresponding fields, and click :guilabel:`Save`." msgstr "" +"للقيام بذلك، اذهب إلى :menuselection:`تطبيق الموقع الإلكتروني --> التهيئة " +"--> الإعدادات`، ثم قم بتفعيل خيار :guilabel:`تمكين إشعارات الويب` وقم بتعبئة" +" الحقول المقابلة واضغط على :guilabel:`حفظ`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:219 msgid "Message" @@ -5333,6 +5969,8 @@ msgid "" "Next, there's the :guilabel:`Message` field. This is where the main content " "of the post is created." msgstr "" +"تالياً، يوجد حقل :guilabel:`الرسالة`. إنه المكان الذي يتم فيه إنشاء المحتوى " +"الرئيسي للمنشور. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:223 msgid "" @@ -5341,12 +5979,18 @@ msgid "" " visual samples of how the post will look on all the previously selected " "social media accounts (and/or websites, as push notifications)." msgstr "" +"في حقل :guilabel:`الرسالة`، قم بكتابة الرسالة المطلوبة للمنشور الاجتماعي. " +"بعد الكتابة، اضغط بعيداً عن حقل :guilabel:`الرسالة` لإظهار الأمثلة المرئية " +"لما سيبدو عليه المنشور على كافة حسابات التواصل الاجتماعي التي تم تحديدها " +"مسبقاً (ز/أو المواقع الإلكترونية كالإشعارات المنبثقة). " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Sample social media post with visual samples of how it will appear on social" " media outlets." msgstr "" +"مثال على منشور اجتماعي مع أمثلة مرئية لما سيظهر عليه المنشور على منصات " +"التواصل الاجماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:232 msgid "" @@ -5355,12 +5999,18 @@ msgid "" "of the :guilabel:`Message` field to the far right. Clicking this icon " "reveals a drop-down menu containing numerous emojis to choose from." msgstr "" +"يمكن أيضاً إضافة الرموز التعبيرية مباشرة إلى النص الموجود في حقل " +":guilabel:`الرسالة`. فقط قم بالضغط على أيقونة :guilabel:`🙂 (الوجه المبتسم)` " +"الموجودة في خط حقل :guilabel:`الرسالة` في أقصى اليمين. ستُظهِر هذه الأيقونة" +" قائمة منسدلة تحتوي على أعداد كبيرة من الرموز التعبيرية للاختيار من بينها. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 msgid "" "If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a " "character counter appears beneath the :guilabel:`Message` field." msgstr "" +"إذا كان :guilabel:`Twitter` محدداً في حقل :guilabel:`النشر على`، سيظهر عدّاد" +" لعدد الرموز أسفل حقل :guilabel:`الرسالة`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:241 msgid "Attach Images" @@ -5374,6 +6024,10 @@ msgid "" "this pop-up window, select the desired image from the hard drive, and upload" " it." msgstr "" +"إذا كان سيتم استخدام الصور في المنشور، فاضغط على زر :guilabel:`إرفاق صور`، " +"في حقل :guilabel:`إرفاق صور`، الموجود أسفل حقل :guilabel:`الرسالة`. عند " +"الضغط عليه، يكشف أودو عن نافذة منبثقة. في هذه النافذة المنبثقة، قم بتحديد " +"الصورة المطلوبة من القرص الصلب، وقم برفعها. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:248 msgid "" @@ -5381,12 +6035,17 @@ msgid "" " new preview of the social media post, complete with the newly-added image, " "on the right side of the detail form." msgstr "" +"بعد رفع الصورة المطلوبة وإرفاقها بنجاح، سيُظهِر أودو معاينة جديدة لمنشور " +"اجتماعي، مكتملة بالصورة التي تمت إضافتها حديثاً، على الجانب الأيمن من " +"استمارة التفاصيل. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Visualized samples of post with newly-attached images in Odoo Social " "Marketing." msgstr "" +"أمثلة مصورة عللمنشورات مع الصور التي تم إرفاقها حديثاً في تطبيق التسويق " +"الاجتماعي لدى أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 msgid "Campaign" @@ -5397,6 +6056,8 @@ msgid "" "Next, there is the :guilabel:`Campaign` field. This non-required field " "provides the options to attach this post to a specific marketing campaign." msgstr "" +"بعد ذلك، يوجد حقل :guilabel:`الحملة`. يوفر هذا الحقل غير المطلوب خيارات " +"لإرفاق هذا المنشور بحملة تسويقية محددة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:261 msgid "" @@ -5405,6 +6066,10 @@ msgid "" "existing campaigns in the database. Select the desired campaign from this " "drop-down menu to add this post to that campaign." msgstr "" +"لإضافة هذا المنشور إلى حملة موجودة مسبقاً، اضغط على حقل :guilabel:`الحملة` " +"الفارغ لإظهار قائمة منسدلة تحتوي على كافة الحملات الموجودة في قاعدة " +"البيانات. قم بتحديد الحملة المطلوبة من هذه القائمة المنسدلة لإضافة هذا " +"المنشور إلى تلك الحملة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 msgid "" @@ -5413,17 +6078,22 @@ msgid "" "field, and select either :guilabel:`Create` or :guilabel:`Create and " "edit...`." msgstr "" +"لإنشاء حملة جديدة مباشرة من استمارة تفاصيل المنشور الاجتماعي، ابدأ بكتابة " +"اسم الحملة الجديدة في حقل :guilabel:`الحملة` الفارغ، وحدد إما " +":guilabel:`إنشاء` أو :guilabel:`إنشاء وتحرير ...`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Drop-down menu options of Create or Create and edit in the Campaign field." -msgstr "" +msgstr "خيارات القائمة المنسدلة \"إنشاء\" أو \"إنشاء وتحرير\" في حقل الحملة. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:273 msgid "" "Clicking :guilabel:`Create` creates the campaign, which can be " "edited/customized later." msgstr "" +"يؤدي الضغط على :guilabel: `إنشاء` إلى إنشاء الحملة، والتي يمكن " +"تحريرها/تخصيصها لاحقاً. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 msgid "" @@ -5432,18 +6102,25 @@ msgid "" "Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly " "configured." msgstr "" +"يؤدي الضغط على :guilabel: `إنشاء وتحرير...` إلى إنشاء الحملة، ويُظهِر " +"استمارة منبثقة لـ :guilabel:`إنشاء الحملة`، حيث يوجد :guilabel:`مُعرّف " +"الحملة`، و :guilabel:`المسؤول`، ويمكن تهيئة :guilabel:`علامات التصنيف` على " +"الفور. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Create campaign pop-up window that appears on a social media post detail " "form." msgstr "" +"قم بإنشاء نافذة منبثقة للحملة تظهر في استمارة تفاصيل المنشور الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 msgid "" "When all the desired settings have been entered, click :guilabel:`Save & " "Close` to save the campaign and return to the social media post detail form." msgstr "" +"عند إدخال كافة الإعدادات المطلوبة، اضغط على زر :guilabel: `حفظ وإغلاق` لحفظ " +"الحملة والعودة إلى استمارة تفاصيل المنشور الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:287 msgid "When" @@ -5455,6 +6132,9 @@ msgid "" "have Odoo publish the post immediately, or :guilabel:`Schedule later` to " "have Odoo publish the post at a later date and time." msgstr "" +"بعد ذلك، في حقل :guilabel:`متى`، اختر إما :guilabel:`إرسال الآن` حتى يقوم " +"أودو بنشر المنشور على الفور، أو :guilabel:`الجدولة في وقت لاحق` حتى يقوم " +"أودو بنشر المنشور في وقت وتاريخ لاحقين. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:293 msgid "" @@ -5462,12 +6142,17 @@ msgid "" "field appears. Clicking the empty field reveals a pop-up calendar, in which " "a future date and time can be designated." msgstr "" +"إذا تم تحديد خيار :guilabel:`الجدولة في وقت لاحق`، فسيظهر حقل جديد لـ " +":guilabel:`التاريخ المجدول`. يؤدي الضغط على زر الحقل الفارغ إلى ظهور تقويم " +"منبثق، حيث يمكن تحديد التاريخ والوقت المستقبليين. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "" "Schedule date pop-up window that appears on social media post detail form in" " Odoo." msgstr "" +"النافذة المنبثقة لجدولة الوقت التي تظهر على استمارة تفاصيل المنشور الاجتماعي" +" في أودو. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 msgid "" @@ -5475,6 +6160,9 @@ msgid "" " will promptly publish the post at that specific date and time on the pre-" "detemined social media account(s)." msgstr "" +"بعد تحديد التاريخ والوقت المطلوبين، اضغط على زر :guilabel:`تطبيق`. بعد ذلك، " +"سيقوم أودو بنشر المنشور على الفور في ذلك التاريخ والوقت المحددين على حساب " +"(حسابات) وسائل التواصل الاجتماعي المحددة مسبقاً. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:304 msgid "" @@ -5482,12 +6170,17 @@ msgid "" "media post detail form changes to :guilabel:`Schedule`. Be sure to click " ":guilabel:`Schedule` after completing the social media post detail form." msgstr "" +"في حالة جدولة منشور، يتغير زر :guilabel:`نشر` الموجود أعلى استمارة تفاصيل " +"المنشور الاجتماعي إلى :guilabel:`جدولة`. تأكد من الضغط على زر " +":guilabel:`جدولة` بعد إكمال استمارة تفاصيل المنشور الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 msgid "" "Doing so, locks in that specific date/time for Odoo to send the post, and it" " changes the status of the post to :guilabel:`Scheduled`." msgstr "" +"يؤدي القيام بذلك إلى حجز التاريخ/الوقت المحدد الذي سيقوم أودو بإرسال المنشور" +" فيه، وستتغير حالة المنشور إلى :guilabel:`تمت جدولته`. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 msgid "Push Notification Options" @@ -5499,14 +6192,17 @@ msgid "" "the :guilabel:`Post on` field, a specific :guilabel:`Push Notification " "Options` section appears at the bottom of the social media post detail form." msgstr "" +"إذا تم اختيار خيار واحد (أو عدة خيارات) :guilabel:`[إشعارات منبثقة]` في حقل " +":guilabel:`النشر على`، فسيظهر قسم :guilabel:`خيارات الإشعارات المنبثقة` أسفل" +" استمارة تفاصيل المنشور الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 msgid "Push notification options section on a social media post detail form." -msgstr "" +msgstr "قسم خيارات الإشعارات المنبثقة في استمارة تفاصيل المنشور الاجتماعي. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 msgid "It should be noted that *none* of these fields are required." -msgstr "" +msgstr "من المهم معرفة أنه *لا يوجد* أي حقل مطلوب من بين هذه الحقول. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:324 msgid "" @@ -5514,6 +6210,8 @@ msgid "" "field, there is the option to add a custom title to the push notification " "that will be sent." msgstr "" +"الحقل الأول في هذا القسم هو :guilabel:`عنوان الإشعار`. في هذا الحقل، يوجد " +"خيار لإضافة عنوان مخصص إلى الإشعار المنبثق الذي سيتم إرساله. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 msgid "" @@ -5522,6 +6220,10 @@ msgid "" "Then, once a visitor reaches that specific page, Odoo will display the push " "notification." msgstr "" +"لتعيين صفحة معينة على الموقع الإلكتروني من شأنها تشغيل الإشعار المنبثق هذا، " +"قم بإدخال رابط URL لتلك الصفحة في حقل :guilabel:`رابط URL المستهدف`. بعد " +"ذلك، بمجرد وصول الزائر إلى تلك الصفحة المحددة، سيقوم أودو بعرض الإشعار " +"المنبثق. " #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:331 msgid "" diff --git a/locale/ar/LC_MESSAGES/sales.po b/locale/ar/LC_MESSAGES/sales.po index 4f6d31265..f0e7f9094 100644 --- a/locale/ar/LC_MESSAGES/sales.po +++ b/locale/ar/LC_MESSAGES/sales.po @@ -6118,7 +6118,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 msgid "Invoices" -msgstr "الفواتير" +msgstr "فواتير العملاء " #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 msgid "" diff --git a/locale/he/LC_MESSAGES/finance.po b/locale/he/LC_MESSAGES/finance.po index b12b53fe4..2daa0f035 100644 --- a/locale/he/LC_MESSAGES/finance.po +++ b/locale/he/LC_MESSAGES/finance.po @@ -37,7 +37,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: he\n" -"Plural-Forms: nplurals=3; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: (n % 10 == 0 && n % 1 == 0 && n > 10) ? 2 : 3;\n" +"Plural-Forms: nplurals=3; plural=(n == 1 && n % 1 == 0) ? 0 : (n == 2 && n % 1 == 0) ? 1: 2;\n" #: ../../content/applications/finance.rst:5 msgid "Finance" @@ -35579,12 +35579,6 @@ msgid "" "platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "" diff --git a/locale/hi/LC_MESSAGES/administration.po b/locale/hi/LC_MESSAGES/administration.po new file mode 100644 index 000000000..af06ad697 --- /dev/null +++ b/locale/hi/LC_MESSAGES/administration.po @@ -0,0 +1,9300 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:55+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/administration.rst:8 +msgid "Install and Maintain" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid "" +":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration/install.rst:5 +msgid "Install" +msgstr "" + +#: ../../content/administration/install.rst:7 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration/install.rst:10 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in production " +"or to try it." +msgstr "" + +#: ../../content/administration/install.rst:12 +msgid "" +":doc:`Packaged installers ` are suitable for testing Odoo " +"and developing modules. They can be used for long-term production with " +"additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration/install.rst:16 +msgid "" +":doc:`Source install ` provides greater flexibility, as it " +"allows, for example, running multiple Odoo versions on the same system. It " +"is adequate to develop modules and can be used as a base for production " +"deployment." +msgstr "" + +#: ../../content/administration/install.rst:20 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration/install.rst:26 +msgid "Editions" +msgstr "" + +#: ../../content/administration/install.rst:28 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration/install.rst:30 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration/install.rst:34 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration/install.rst:39 +msgid "" +":doc:`Switch from Community to Enterprise ` at any time" +" (except for the source install)." +msgstr "" + +#: ../../content/administration/install/cdn.rst:3 +msgid "Set up a content delivery network (CDN)" +msgstr "" + +#: ../../content/administration/install/cdn.rst:8 +msgid "Deploying with KeyCDN" +msgstr "" + +#: ../../content/administration/install/cdn.rst:10 +msgid "" +"A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, " +"is a geographically distributed network of servers that provides high speed " +"internet content. The :abbr:`CDN (Content Delivery Network)` provides quick," +" high-quality content delivery for content-heavy websites." +msgstr "" + +#: ../../content/administration/install/cdn.rst:14 +msgid "" +"This document will guide you through the setup of a KeyCDN_ account with an " +"Odoo powered website." +msgstr "" + +#: ../../content/administration/install/cdn.rst:17 +msgid "Create a pull zone in the KeyCDN dashboard" +msgstr "" + +#: ../../content/administration/install/cdn.rst:19 +msgid "" +"On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` " +"menu item on the left. On the form, give a value to the :guilabel:`Zone " +"Name`, which will appear as part of the :abbr:`CDN (Content Delivery " +"Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the " +":guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the " +":guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, " +"under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this " +"address should be the full Odoo database :abbr:`URL (Uniform Resource " +"Locator)`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:28 +msgid "" +"Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* " +"subdomain prefix with the actual name of the database. A custom :abbr:`URL " +"(Uniform Resource Locator)` can be used, as well, in place of the Odoo " +"subdomain that was provided to the database." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN's Zone configuration page." +msgstr "" + +#: ../../content/administration/install/cdn.rst:36 +msgid "" +"Under the :guilabel:`General Settings` heading below the zone form, click " +"the :guilabel:`Show all settings` button to expand the zone options. This " +"should be the last option on the page. After expanding the " +":guilabel:`General Settings` ensure that the :guilabel:`CORS` option is " +":guilabel:`enabled`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:41 +msgid "" +"Next, scroll to the bottom of the zone configuration page and " +":guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be" +" deployed. This can take about 10 minutes." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN deploying the new Zone." +msgstr "" + +#: ../../content/administration/install/cdn.rst:49 +msgid "" +"A new :guilabel:`Zone URL` has been generated for your Zone, in this example" +" it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each " +"database." +msgstr "" + +#: ../../content/administration/install/cdn.rst:52 +msgid "" +"Copy this :guilabel:`Zone URL` to a text editor for later, as it will be " +"used in the next steps." +msgstr "" + +#: ../../content/administration/install/cdn.rst:55 +msgid "Configure the Odoo instance with the new zone" +msgstr "" + +#: ../../content/administration/install/cdn.rst:57 +msgid "" +"In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and" +" then activate the :guilabel:`Content Delivery Network (CDN)` setting and " +"copy/paste the :guilabel:`Zone URL` value from the earlier step into the " +":guilabel:`CDN Base URL` field. This field is only visible and configurable " +"when :doc:`Developer Mode <../../applications/general/developer_mode>` is " +"activated." +msgstr "" + +#: ../../content/administration/install/cdn.rst:63 +msgid "" +"Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN" +" Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." +msgstr "" + +#: ../../content/administration/install/cdn.rst:66 +msgid ":guilabel:`Save` the settings when complete." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Activate the CDN setting in Odoo." +msgstr "" + +#: ../../content/administration/install/cdn.rst:72 +msgid "" +"Now the website is using the CDN for the resources matching the " +":guilabel:`CDN filters` regular expressions." +msgstr "" + +#: ../../content/administration/install/cdn.rst:75 +msgid "" +"In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` " +"integration is evidenced as working properly by checking the :abbr:`URL " +"(Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen" +" by using your web browser's :guilabel:`Inspect` feature on the Odoo " +"website. Look for it's record by searching within the :guilabel:`Network` " +"tab inside of devtools." +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "" +"The CDN Base URL can be seen using the inspect function on the Odoo website." +msgstr "" + +#: ../../content/administration/install/cdn.rst:85 +msgid "" +"Prevent security issues by activating cross-origin resource sharing (CORS)" +msgstr "" + +#: ../../content/administration/install/cdn.rst:87 +msgid "" +"A security restriction in some browsers (such as Mozilla Firefox and Google " +"Chrome) prevents a remotely linked CSS file to fetch relative resources on " +"this same external server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:90 +msgid "" +"If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in " +"the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard " +"Odoo website will be the lack of *Font Awesome* icons because the font file " +"declared in the *Font Awesome* CSS won't be loaded from the remote server." +msgstr "" + +#: ../../content/administration/install/cdn.rst:95 +msgid "" +"When these cross-origin resource issues occur, a security error message " +"similar to the output below will appear in the web browser's developer " +"console:" +msgstr "" + +#: ../../content/administration/install/cdn.rst:98 +msgid "" +"``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from " +"loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-" +"Allow-Origin' header is present on the requested resource. Origin " +"'http://yourdatabase.odoo.com' is therefore not allowed access.``" +msgstr "" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Error message populated in the browser console." +msgstr "" + +#: ../../content/administration/install/cdn.rst:106 +msgid "" +"Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the " +":abbr:`CDN (Content Delivery Network)` settings fixes this issue." +msgstr "" + +#: ../../content/administration/install/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/install/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../install>`, and is " +"not generally necessary for a development systems that is not exposed on the" +" internet." +msgstr "" + +#: ../../content/administration/install/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/install/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/install/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/install/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/install/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/install/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/install/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/install/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/install/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:46 +#: ../../content/administration/install/deploy.rst:58 +#: ../../content/administration/install/deploy.rst:153 +#: ../../content/administration/install/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/install/deploy.rst:76 +#: ../../content/administration/install/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/install/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/install/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/install/deploy.rst:95 +#: ../../content/administration/install/deploy.rst:145 +#: ../../content/administration/install/deploy.rst:235 +#: ../../content/administration/install/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/install/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/install/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/install/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/install/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/install/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/install/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/install/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/install/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/install/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/install/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/install/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/install/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/install/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/install/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/install/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/install/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/install/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/install/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/install/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/install/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/install/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/install/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/install/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/install/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/install/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/install/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/install/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/install/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/install/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/install/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/install/deploy.rst:225 +#: ../../content/administration/install/deploy.rst:412 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/install/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/install/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/install/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/install/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/install/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/install/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/install/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/install/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/install/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/install/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/install/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/install/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:361 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/install/deploy.rst:363 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/install/deploy.rst:369 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:375 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/install/deploy.rst:386 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/install/deploy.rst:388 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/install/deploy.rst:394 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:399 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:401 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/install/deploy.rst:406 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/install/deploy.rst:414 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/install/deploy.rst:420 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:429 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/install/deploy.rst:431 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/install/deploy.rst:436 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/install/deploy.rst:438 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/install/deploy.rst:442 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/install/deploy.rst:447 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/install/deploy.rst:474 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/install/deploy.rst:481 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/install/deploy.rst:483 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:487 +#: ../../content/administration/install/deploy.rst:501 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:494 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/install/deploy.rst:496 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/install/deploy.rst:509 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/install/deploy.rst:511 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/install/deploy.rst:516 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:526 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/install/deploy.rst:528 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:537 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/install/deploy.rst:546 +msgid "Security" +msgstr "" + +#: ../../content/administration/install/deploy.rst:548 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/install/deploy.rst:552 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/install/deploy.rst:558 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:561 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:564 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/install/deploy.rst:569 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/install/deploy.rst:573 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`db_filter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/install/deploy.rst:580 +msgid "" +"Once your ``db_name`` and ``db_filter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/install/deploy.rst:586 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:591 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/install/deploy.rst:595 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:598 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:605 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/install/deploy.rst:611 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/install/deploy.rst:615 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/install/deploy.rst:619 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/install/deploy.rst:623 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/install/deploy.rst:634 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/install/deploy.rst:645 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/install/deploy.rst:648 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/install/deploy.rst:651 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/install/deploy.rst:659 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/install/deploy.rst:661 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/install/deploy.rst:665 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/install/deploy.rst:667 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:671 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:676 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/install/deploy.rst:678 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:685 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:687 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/install/deploy.rst:701 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/install/deploy.rst:703 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/install/deploy.rst:705 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/install/deploy.rst:708 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/install/deploy.rst:714 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/install/deploy.rst:720 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/install/deploy.rst:723 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``db_filter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/install/deploy.rst:728 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/install/deploy.rst:732 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/install/deploy.rst:736 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/install/deploy.rst:742 +msgid "which will generate a 32 characters pseudorandom printable string." +msgstr "" + +#: ../../content/administration/install/deploy.rst:745 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/install/deploy.rst:747 +msgid "" +"Odoo supports all the major desktop and mobile browsers available on the " +"market, as long as they are supported by their publishers." +msgstr "" + +#: ../../content/administration/install/deploy.rst:750 +msgid "Here are the supported browsers:" +msgstr "" + +#: ../../content/administration/install/deploy.rst:752 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/install/deploy.rst:753 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/install/deploy.rst:754 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/install/deploy.rst:755 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/install/deploy.rst:757 +msgid "" +"Please make sure your browser is up-to-date and still supported by its " +"publisher before filing a bug report." +msgstr "" + +#: ../../content/administration/install/deploy.rst:762 +msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." +msgstr "" + +#: ../../content/administration/install/deploy.rst:765 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/install/deploy.rst:768 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/install/deploy.rst:772 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:30 +#: ../../content/administration/install/email_gateway.rst:45 +msgid "Resources" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:38 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:47 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/install/email_gateway.rst:50 +msgid "" +"If you don't have access/manage your email server, use :ref:`inbound " +"messages `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:11 +msgid "" +"Download both the GeoLite2 City and Country `databases " +"`_. You should end up with " +"two files called :file:`GeoLite2-City.mmdb` and " +":file:`GeoLite2-Country.mmdb`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:25 +msgid "" +"If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`," +" use the :option:`--geoip-city-db ` and " +":option:`--geoip-country-db ` options of the " +"Odoo command line interface. These options take the absolute path to the " +"GeoIP database file and use it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:41 +msgid "" +"Edit a web page to include some geo-ip information such as the country name " +"of the current request IP address. To do so:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:54 +msgid "" +"Geo-ip is working if you read your country name displayed in bold in the " +"middle of the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:58 +msgid "" +"The browsing IP address is the localhost (``127.0.0.1``) or a local area " +"network one. If you don't know, you can access your website using mobile " +"data." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:60 +msgid "" +"You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't " +"start Odoo with the proxy-mode enabled. See :option:`proxy mode `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:62 +msgid "" +"The GeoIP database is corrupt, missing or unaccessible. In such case a " +"warning was logged in the server logs." +msgstr "" + +#: ../../content/administration/install/online.rst:3 +msgid "Online" +msgstr "" + +#: ../../content/administration/install/online.rst:5 +msgid "" +"Online instances are accessed using any web browser and do not require a " +"local installation." +msgstr "" + +#: ../../content/administration/install/online.rst:8 +msgid "Demo" +msgstr "" + +#: ../../content/administration/install/online.rst:10 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/install/online.rst:14 +#: ../../content/administration/maintain/domain_names.rst:166 +#: ../../content/administration/maintain/domain_names.rst:236 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:90 +#: ../../content/administration/upgrade.rst:307 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/install/online.rst:16 +msgid "" +"`Odoo Online `_ provides private instances which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/install/online.rst:21 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/install/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/install/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/install/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/install/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/install/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/install/packages.rst:19 +msgid "" +"It is required to be logged in as a paying customer or partner to download " +"the Enterprise packages." +msgstr "" + +#: ../../content/administration/install/packages.rst:25 +#: ../../content/administration/install/source.rst:52 +#: ../../content/administration/install/source.rst:129 +#: ../../content/administration/install/source.rst:152 +#: ../../content/administration/install/source.rst:174 +#: ../../content/administration/install/source.rst:199 +#: ../../content/administration/install/source.rst:228 +#: ../../content/administration/install/source.rst:271 +#: ../../content/administration/install/source.rst:384 +#: ../../content/administration/install/source.rst:446 +msgid "Linux" +msgstr "" + +#: ../../content/administration/install/packages.rst:28 +#: ../../content/administration/install/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/install/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/install/packages.rst:34 +#: ../../content/administration/install/packages.rst:70 +#: ../../content/administration/install/packages.rst:100 +#: ../../content/administration/install/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/install/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/install/packages.rst:44 +#: ../../content/administration/install/packages.rst:80 +#: ../../content/administration/install/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/install/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/install/packages.rst:57 +#: ../../content/administration/install/source.rst:416 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/install/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/install/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/install/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/install/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/install/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/install/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/install/packages.rst:103 +msgid "" +"Odoo 17 'deb' package currently supports `Debian Buster " +"`_ and `Ubuntu 18.04 " +"`_ or above." +msgstr "" + +#: ../../content/administration/install/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/install/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/install/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/install/packages.rst:135 +msgid "Odoo 17 'rpm' package supports Fedora 36." +msgstr "" + +#: ../../content/administration/install/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/install/packages.rst:148 +#: ../../content/administration/install/source.rst:70 +#: ../../content/administration/install/source.rst:133 +#: ../../content/administration/install/source.rst:158 +#: ../../content/administration/install/source.rst:180 +#: ../../content/administration/install/source.rst:208 +#: ../../content/administration/install/source.rst:239 +#: ../../content/administration/install/source.rst:324 +#: ../../content/administration/install/source.rst:393 +#: ../../content/administration/install/source.rst:456 +msgid "Windows" +msgstr "" + +#: ../../content/administration/install/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/install/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/install/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/install/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/install/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/install/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/install/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/install/source.rst:3 +msgid "Source" +msgstr "" + +#: ../../content/administration/install/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/install/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/install/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/install/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/install/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/install/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/install/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/install/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/install/source.rst:28 +#: ../../content/administration/install/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/install/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/install/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/install/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/install/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/install/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/install/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/install/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/install/source.rst:56 +#: ../../content/administration/install/source.rst:74 +#: ../../content/administration/install/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/install/source.rst:63 +#: ../../content/administration/install/source.rst:81 +#: ../../content/administration/install/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/install/source.rst:88 +#: ../../content/administration/install/source.rst:141 +#: ../../content/administration/install/source.rst:164 +#: ../../content/administration/install/source.rst:186 +#: ../../content/administration/install/source.rst:213 +#: ../../content/administration/install/source.rst:253 +#: ../../content/administration/install/source.rst:347 +#: ../../content/administration/install/source.rst:405 +#: ../../content/administration/install/source.rst:467 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/install/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/install/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/install/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/install/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/install/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/install/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/install/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/install/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/install/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.7 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/install/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/install/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/install/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/install/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/install/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/install/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/install/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/install/source.rst:236 +#: ../../content/administration/install/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/install/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/install/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/install/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/install/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/install/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/install/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/install/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/install/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/install/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/install/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/install/source.rst:280 +msgid "" +"For Debian-based systems, the packages are listed in the `debian/control " +"`_ file of the Odoo " +"sources." +msgstr "" + +#: ../../content/administration/install/source.rst:283 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/install/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/install/source.rst:292 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/install/source.rst:295 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/install/source.rst:301 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:305 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/install/source.rst:312 +#: ../../content/administration/install/source.rst:334 +#: ../../content/administration/install/source.rst:353 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/install/source.rst:316 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/install/source.rst:326 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/install/source.rst:330 +#: ../../content/administration/install/source.rst:349 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:338 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/install/source.rst:357 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/install/source.rst:367 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/install/source.rst:370 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/install/source.rst:376 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/install/source.rst:379 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/install/source.rst:386 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/install/source.rst:387 +#: ../../content/administration/install/source.rst:396 +#: ../../content/administration/install/source.rst:409 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/install/source.rst:395 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/install/source.rst:402 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/install/source.rst:407 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/install/source.rst:424 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/install/source.rst:426 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:429 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/install/source.rst:433 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/install/source.rst:437 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/install/source.rst:439 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/install/source.rst:440 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/install/source.rst:442 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/install/source.rst:453 +#: ../../content/administration/install/source.rst:474 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/source.rst:463 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/source.rst:477 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/install/source.rst:482 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users/manage_users>`." +msgstr "" + +#: ../../content/administration/install/source.rst:483 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/install/source.rst:487 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/maintain.rst:5 +msgid "Maintain" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:3 +msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:5 +msgid "" +"Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order " +"to send and receive secure emails from a custom domain, all that is required" +" is to configure a few settings on the Azure platform and on the back end of" +" the Odoo database. This configuration works with either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:11 +msgid "" +"`Microsoft Learn: Register an application with the Microsoft identity " +"platform `_" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:15 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/outlook`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:19 +msgid "Setup in Microsoft Azure Portal" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:22 +msgid "Create a new application" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:24 +msgid "" +"To get started, go to `Microsoft's Azure Portal " +"`_. Log in with the :guilabel:`Microsoft Outlook " +"Office 365` account if there is one, otherwise log in with the personal " +":guilabel:`Microsoft account`. A user with administrative access to the " +"Azure Settings will need to connect and perform the following configuration." +" Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID`" +" (formally *Azure Active Directory*)." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:30 +msgid "" +"Now, click on :guilabel:`Add (+)`, located in the top menu, and then select " +":guilabel:`App registration`. On the :guilabel:`Register an application` " +"screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. " +"Under the :guilabel:`Supported account types` section select " +":guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID " +"directory - Multitenant) and personal Microsoft accounts (e.g. Skype, " +"Xbox)`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:36 +msgid "" +"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " +"platform, and then input `https:///microsoft_outlook/confirm`" +" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at " +"which your Odoo instance can be reached in the URL field." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:41 +msgid "" +"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the " +"database's subdomain, assuming it's hosted on Odoo.com" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:44 +msgid "" +"After the URL has been added to the field, :guilabel:`Register` the " +"application so it is created." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:47 +msgid "API permissions" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:49 +msgid "" +"The :guilabel:`API permissions` should be set next. Odoo will need specific " +"API permissions to be able to read (IMAP) and send (SMTP) emails in the " +"Microsoft 365 setup. First, click the :guilabel:`API permissions` link, " +"located in the left menu bar. Next, click on the :guilabel:`(+) Add a " +"Permission` button and select :guilabel:`Microsoft Graph` under " +":guilabel:`Commonly Used Microsoft APIs`. After, select the " +":guilabel:`Delegated Permissions` option." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:55 +msgid "" +"In the search bar, search for the following :guilabel:`Deregulated " +"permissions` and click :guilabel:`Add permissions` for each one:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:58 +msgid ":guilabel:`SMTP.Send`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:59 +msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:62 +msgid "The :guilabel:`User.Read` permission will be added by default." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"API permissions needed for Odoo integration are listed under the Microsoft " +"Graph." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:69 +msgid "Assign users and groups" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:71 +msgid "" +"After adding the API permissions, navigate back to the :guilabel:`Overview` " +"of the :guilabel:`Application` in the top of the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:74 +msgid "" +"Now, add users to this application. Under the :guilabel:`Essentials` " +"overview table, click on the link labeled :guilabel:`Managed Application in " +"Local Directory`, or the last option on the bottom right-hand side of the " +"table." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"Add users/groups by clicking the Managed application in local directory link for the\n" +"created application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:83 +msgid "" +"In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click " +"on :guilabel:`(+) Add User/Group`. Depending on the account, either a " +":guilabel:`Group` and a :guilabel:`User` can be added, or only " +":guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` " +"to be added." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:88 +msgid "" +"Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None " +"Selected` and add the users or group of users that will be sending emails " +"from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the " +"users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to " +"the application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:94 +msgid "Create credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:96 +msgid "" +"Now that the Microsoft Azure app is set up, credentials need to be created " +"for the Odoo setup. These include the :guilabel:`Client ID` and " +":guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied" +" from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or" +" :guilabel:`Application ID` is located under the :guilabel:`Display Name` in" +" the :guilabel:`Essentials` overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Application/Client ID located in the Overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:106 +msgid "" +"Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this" +" value, click on :guilabel:`Certificates & Secrets` in the left sidebar " +"menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do" +" this, click on the :guilabel:`(+) New Client Secret` button." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:110 +msgid "" +"A window on the right will populate with a button labeled :guilabel:`Add a " +"client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or " +"something recognizable, and then set the :guilabel:`expiration date`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:115 +msgid "" +"A new :guilabel:`Client Secret` will need to be produced and configured if " +"the first one expires. In this event, there could be an interruption of " +"service, so the expiration date should be noted and set to the furthest " +"possible date." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:119 +msgid "" +"Next, click on :guilabel:`Add` when these two values are entered. A " +":guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. " +"It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret " +"Value` into a notepad as it will become encrypted after leaving this page. " +"The :guilabel:`Secret ID` is not needed." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Client Secret Value or Value in the app's credentials." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:128 +msgid "" +"After these steps, the following items should be ready to be set up in Odoo:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:130 +msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:131 +msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:133 +msgid "" +"This completes the setup on the :guilabel:`Microsoft Azure Portal` side." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:136 +#: ../../content/administration/maintain/google_oauth.rst:111 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:139 +msgid "Enter Microsoft Outlook credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:141 +msgid "" +"First, open the Odoo database and navigate to the :guilabel:`Apps` module. " +"Then, remove the :guilabel:`Apps` filter from the search bar and type in " +"`Outlook`. After that, install the module called :guilabel:`Microsoft " +"Outlook`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:145 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` is checked. This populates a new option for" +" :guilabel:`Outlook Credentials`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:149 +msgid ":guilabel:`Save` the progress." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:151 +msgid "" +"Then, copy and paste the :guilabel:`Client ID` (Application ID) and " +":guilabel:`Client Secret (Client Secret Value)` into the respective fields " +"and :guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Outlook Credentials in Odoo General Settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:159 +#: ../../content/administration/maintain/google_oauth.rst:127 +msgid "Configure outgoing email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:161 +msgid "" +"On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email " +"Servers` setting, click the :guilabel:`Outgoing Email Servers` link to " +"configure the Microsoft account." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:164 +msgid "" +"Then, create a new email server and check the box for :guilabel:`Outlook`. " +"Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft " +"Outlook email :guilabel:`Username`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:167 +msgid "" +"If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain " +"or email address `." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:170 +msgid "Then, click on :guilabel:`Connect your Outlook account`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:172 +msgid "" +"A new window from Microsoft opens to complete the :guilabel:`authorization " +"process`. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Permission page to grant access between newly created app and Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:179 +msgid "" +"Then, allow Odoo to access the Microsoft account by clicking on " +":guilabel:`Yes`. After this, the page will navigate back to the newly " +"configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration " +"automatically loads the :guilabel:`token` in Odoo, and a tag stating " +":guilabel:`Outlook Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Valid Outlook Token indicator." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:188 +msgid "" +"Finally, click :guilabel:`Test Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Microsoft" +" Outlook using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:194 +msgid "Configuration with a single outgoing mail server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:196 +msgid "" +"Configuring a single outgoing server is the simplest configuration available" +" for Microsoft Azure and it doesn't require extensive access rights for the " +"users in the database." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:199 +msgid "" +"A generic email address would be used to send emails for all users within " +"the database. For example it could be structured with a `notifications` " +"alias (`notifications@example.com`) or `contact` alias " +"(`contact@example.com`). This address must be set as the :guilabel:`FROM " +"Filtering` on the server. This address must also match the " +"`{mail.default.from}@{mail.catchall.domain}` key combination in the system " +"parameters." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:206 +#: ../../content/administration/maintain/azure_oauth.rst:247 +msgid "" +"For more information on the from filter visit: " +":ref:`email_communication/default`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:209 +#: ../../content/administration/maintain/azure_oauth.rst:254 +msgid "" +"The :guilabel:`System Parameters` can be accessed by activating " +":ref:`developer-mode` in the :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:212 +msgid "" +"When using this configuration, every email that is sent from the database " +"will use the address of the configured `notification` mailbox. However it " +"should be noted that the name of the sender will appear but their email " +"address will change:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Name from real sender with static email." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:221 +msgid "Single outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:223 +msgid "" +"Outgoing mail server **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:224 +msgid "" +"Outgoing mail server :guilabel:`FROM Filtering` = " +"`notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:225 +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "`mail.catchall.domain` in system parameters = `example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:226 +#: ../../content/administration/maintain/azure_oauth.rst:280 +msgid "`mail.default.from` in system parameters = `notifications`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:229 +msgid "User-specific (multiple user) configuration" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:231 +msgid "" +"In addition to a generic email server, individual email servers can be set " +"up for users in a database. These email addresses must be set as the " +":guilabel:`FROM Filtering` on each individual server for this configuration " +"to work." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:235 +msgid "" +"This configuration is the more difficult of the two Microsoft Azure " +"configurations, in that it requires all users configured with email servers " +"to have access rights to settings in order to establish a connection to the " +"email server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:240 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:242 +msgid "" +"Each user should have a separate email server set up. The :guilabel:`FROM " +"Filtering` should be set so that only the user's email is sent from that " +"server. In other words, only a user with an email address that matches the " +"set :guilabel:`FROM Filtering` is able to use this server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:249 +msgid "" +"A :ref:`fallback server ` must be setup to allow " +"for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering`" +" for this server should have the value of the " +"`{mail.default.from}@{mail.catchall.domain}`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:258 +msgid "" +"The configuration for this transactional email server can work alongside an " +"outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the " +"mass-mailing email server can remain empty, but it's require to be added in " +"the settings of the *Email Marketing* application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:263 +msgid "" +"For more information on setting the mass-mailing email server visit " +":ref:`email_communication/mass_mails`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:267 +msgid "Multiple user outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "User #1 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:271 +msgid "" +"Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "User #2 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:274 +msgid "" +"Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "Notifications mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "" +"Outgoing mail server #3 **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:277 +msgid "" +"Outgoing mail server #3 :guilabel:`FROM Filtering` = " +"`notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "System Parameters" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:283 +msgid "Configure incoming email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:285 +msgid "" +"The incoming account should be configured in a similar way to the outgoing " +"email account. Navigate to the :guilabel:`Incoming Mail Servers` in the " +":guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check" +" or Select the button next to :guilabel:`Outlook Oauth Authentication` and " +"enter the :guilabel:`Microsoft Outlook username`. Click on " +":guilabel:`Connect your Outlook account`. Odoo will state: " +":guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the " +"account. The account should be ready to receive email to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:293 +msgid ":doc:`../../applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:3 +#: ../../content/administration/maintain/odoo_online.rst:70 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:5 +msgid "" +"A **domain name** works as an address for your website. It makes the " +"Internet much more accessible as it allows users to type a meaningful web " +"address, such as ``www.odoo.com``, rather than its server's IP address with " +"a series of numbers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:9 +msgid "" +"You can use a custom domain name to access your Odoo database and websites:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:11 +msgid "" +"By :ref:`registering a free domain name with Odoo ` (for Odoo Online databases)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:13 +msgid "" +"By :ref:`configuring a custom domain that you already own `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:16 +msgid "" +"Odoo Online and Odoo.sh databases, including their websites, use by default " +"a subdomain of ``odoo.com`` for both the URL and the emails (e.g., " +"``https://example.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:20 +msgid "" +"Odoo offers a :ref:`free custom domain name ` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:25 +msgid "" +"`Odoo Tutorials: Register a Free Domain Name " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:27 +msgid "" +"`Odoo Quick Tips: Get a free domain name! " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:32 +msgid "About domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:34 +msgid "" +"Having a **good domain name** is as important to your branding as the name " +"of your business or organization as it is the first thing your visitors will" +" notice. We recommend you keep them *simple, short, easy to remember and " +"spell*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:38 +msgid "" +"A **subdomain** is a domain that is a part of another domain. It often " +"refers to the additional part that comes before the main domain name. " +"Traditionally, most websites use the ``www.`` subdomain, but any string of " +"letters can be used as well. You can use subdomains to direct your visitors " +"to other websites than your main website or to specific pages (e.g., " +"``experience.odoo.com`` points to a specific page.)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:44 +msgid "" +"All domain names are referenced in the **Domain Name System**, or **DNS**, " +"which works as a giant directory for the Internet. There are many DNS " +"servers, so any modification to the DNS can take up to 72 hours to propagate" +" worldwide on all servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:51 +msgid "Indexing of domain names by search engines" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:53 +msgid "" +"Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots " +"that explore and analyze the web`) to index all websites and their related " +"domain names. These crawlers discover new URLs thanks to links on known web " +"pages. As a result, search engines should index domain names automatically " +"after a while, as long as their URLs are mentioned elsewhere on the " +"Internet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:58 +msgid "" +"Improving the appearance and positioning of web pages on search engines is a" +" practice named \"Search Engine Optimization\" (SEO)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:62 +msgid "" +"Adding relevant content, optimizing metadata, and building high-quality " +"backlinks can all help improve a website's search engine visibility." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:65 +msgid "" +"Some search engines provide tools for web admins, such as `Google Search " +"Console `_ and `Bing Webmaster " +"Tools `_, to help you analyze and improve " +"your page ranking. To use these services, you must prove that you are the " +"owner of your domain name. One way to verify the ownership of your domain " +"name is by adding a DNS record. You can do this for :ref:`domain names " +"registered with Odoo ` and for domain names managed" +" by other providers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:74 +msgid ":doc:`/applications/websites/website/pages/seo`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:75 +msgid "" +"`Google Search Console Help - Verify your site ownership " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:76 +msgid "" +"`Bing Webmaster Tools - Add and Verify site " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:81 +msgid "Register a free domain name with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:83 +msgid "" +"You can register a domain name for your Odoo Online database directly from " +"Odoo Website or your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:87 +msgid "" +"Your domain name is **free for one year** if you register it with Odoo!" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:88 +msgid "" +"The domain name is registered with `Gandi `_, the " +"domain name registrar." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:90 +msgid "" +"You are the owner of the domain name and can use it for other purposes." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:91 +msgid "Odoo manages payment and technical support for you." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:92 +msgid "" +"This offer doesn't include any mailbox. However, you can :ref:`configure " +"your MX records ` to use your own email server or " +"solution such as Google Workspace." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:95 +msgid "" +"To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, " +"open your `database manager `_, click on " +"the :guilabel:`settings` button next to your database, then on " +":guilabel:`Domain names`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Clicking on Domain Names from an Odoo website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:103 +msgid "" +"Search for the domain name of your choice to check its availability, then " +"select the one you want to register for your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "" +"The search of the domain name example.com shows which associated domains are" +" available." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:110 +msgid "" +"Next, fill in the form with your information to become the domain name " +"owner." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:112 +msgid "" +"Your domain name is directly linked to your database, but you still have to " +":ref:`map your domain name with your website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:116 +msgid "" +"Free domain names are also available for free Odoo Online databases (if you " +"installed one app only, for example). In this case, Odoo reviews your " +"request and your website to avoid abuse. This process can take several days " +"due to the success of the offer." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:119 +msgid "This is not available for Odoo.sh databases yet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:124 +msgid "Manage your domain name registered with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:126 +msgid "" +"To manage the DNS records of your domain name registered with Odoo or to " +"visualize the contacts associated with it, open your `database manager " +"`_, click on the :guilabel:`settings` " +"button next to your database, on :guilabel:`Domain names`, and then on " +":guilabel:`Contacts` or :guilabel:`DNS`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Management of the domain names linked to an Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:136 +msgid "" +"Please `submit a support ticket `_ if you need " +"further assistance to manage your domain name." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:142 +msgid "Configure your existing domain name" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:144 +msgid "" +"If you already own a domain name, you can use it to point to your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:146 +msgid "" +"To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions " +"in this order:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:149 +msgid "" +":ref:`Add a CNAME record ` on your domain name's DNS " +"zone." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:150 +msgid "" +":ref:`Map your domain name with your Odoo database `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:151 +msgid "" +":ref:`Map your domain name with your Odoo website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:156 +msgid "Add a CNAME record" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:158 +msgid "" +"A **CNAME record** is a type of DNS record that points to the domain of " +"another website rather than directly to an IP address." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:161 +msgid "" +"You need a CNAME record that points to your Odoo database. The requirements " +"are detailed in your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:168 +msgid "" +"The target address is the current address of your database, as defined at " +"its creation (e.g., ``example.odoo.com``)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:171 +#: ../../content/administration/maintain/domain_names.rst:250 +#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:173 +msgid "" +"Your project's main address is defined in :menuselection:`Settings --> " +"Project Name`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:175 +msgid "" +"If you want to target a specific branch (production, staging or " +"development), go to :menuselection:`Branches --> select your branch --> " +"Settings --> Custom domains`, and click on :guilabel:`How to set up my " +"domain?`. A message indicates which address your CNAME record should target." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:180 +#: ../../content/administration/maintain/domain_names.rst:222 +msgid "Open your domain name's manager dashboard." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:181 +msgid "" +"Open the **DNS zone** management page for the domain name you want to " +"configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:182 +msgid "Create a **CNAME record** pointing to the address of your database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:184 +msgid "" +"While Odoo suggests creating a CNAME record for your ``www.`` subdomain " +"(``www.example.com``), you can of course use any domain name of your choice," +" with any subdomain (e.g., ``anything.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:189 +msgid "" +"You own the domain name ``example.com``, and you have an Odoo Online " +"database at the address ``example.odoo.com``. You want to access your Odoo " +"database primarily with the domain ``www.example.com`` but also with the " +":ref:`naked domain ` ``example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:194 +msgid "" +"To do so, you create a CNAME record for the ``www`` subdomain, with " +"``example.odoo.com`` as the target. The DNS zone manager generates the " +"following rule and adds it to your DNS zone: ``www IN CNAME " +"example.odoo.com.``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:198 +msgid "" +"You also create a redirection from ``example.com`` to ``wwww.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:200 +msgid "Your new DNS records are propagated to all DNS servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:203 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:205 +msgid "`GoDaddy `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:206 +msgid "" +"`Namecheap " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:207 +msgid "" +"`OVH " +"`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:208 +msgid "" +"`CloudFlare `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:209 +msgid "" +"`Google Domains `_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:214 +msgid "Naked domain" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:216 +msgid "" +"A **naked domain** is a domain name that doesn't have any subdomain at the " +"beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:219 +msgid "" +"You may want your naked domain to redirect to your website as some visitors " +"may not type the full domain name to access your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:223 +msgid "" +"Create a **redirection** from the naked domain (``example.com``) to your " +"main domain name (``www.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:227 +msgid "" +"Depending on your domain name registrar, this redirection may be already " +"pre-configured." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:232 +msgid "Map your domain name with your Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:238 +msgid "" +"Open your `database manager `_, click on " +"the :guilabel:`settings` button next to your database, on :guilabel:`Domain " +"names`, and then on :guilabel:`Use my own domain` at the bottom of the right" +" column." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:242 +msgid "" +"Type the domain name you want to add to this database, then click on " +":guilabel:`Verify` to check if the CNAME record is correctly configured. " +"Once done, click on :guilabel:`I confirm, it's done`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "" +"Verification of the CNAME records of a domain name before mapping it with a " +"database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:252 +msgid "" +"Go to :menuselection:`Branches --> select your branch --> Settings --> " +"Custom domains`, type the domain name you want to add to this database, then" +" click on :guilabel:`Add domain`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "Mapping a domain name with an Odoo.sh branch" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:260 +msgid "" +":ref:`Odoo.sh branches: settings tab `" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:263 +msgid "" +"Make sure to :ref:`add a CNAME record ` to your domain " +"name's DNS **before** mapping your domain name with your Odoo database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:266 +msgid "" +"Failing to do so may impede the validation of the :ref:`SSL certificate " +"` and would result in a *certificate name mismatch* error. " +"This is often displayed by web browsers as a warning such as *\"Your " +"connection is not private\"*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:270 +msgid "" +"If this is the case and you have added the domain name to your database's " +"settings less than five days ago, wait 24 hours as the validation may still " +"happen. Otherwise, please `submit a support ticket " +"`_ including screenshots of your CNAME records." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:277 +msgid "SSL encryption (HTTPS protocol)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:279 +msgid "" +"**SSL encryption** is an encryption-based Internet security protocol. It " +"allows your visitors to navigate your website through a secure connection, " +"which appears as an ``https://`` protocol at the beginning of your web " +"address, rather than a non-secure ``http://`` protocol." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:283 +msgid "" +"Odoo generates a separate SSL certificate for each domain :ref:`mapped in " +"the database manager `, using integration with `Let's " +"Encrypt Certificate Authority and ACME protocol " +"`_." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:288 +msgid "The certificate generation may take up to 24h." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:289 +msgid "" +"Several attempts to validate your certificate are made during the five days " +"following the moment you add your domain name in your database's settings." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:291 +msgid "" +"If you already use another service, you can keep using it or simply change " +"for Odoo." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:296 +msgid "Web base URL of a database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:299 +msgid "" +"If you have Odoo Website, you can disregard this part and directly :ref:`map" +" your domain name with your website `." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:302 +msgid "" +"The **web base URL** of a database, or **root URL** affects your main " +"website address and all the links sent to your customers (e.g., quotations, " +"portal links, etc.)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:305 +msgid "" +"To configure it, access your Odoo database with your custom address, then " +"log in as an administrator of your database (any user in the *Settings* " +"group) from the login screen." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:309 +msgid "" +"Connecting to your database with the original Odoo subdomain address (e.g., " +"``example.odoo.com`` also updates the web base URL of your database. See " +"below to prevent these automatic updates." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:312 +msgid "" +"Alternatively, you can do it manually. To do so, activate the " +":ref:`developer mode `, then go to :menuselection:`Settings " +"--> Technical --> System Parameters`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:315 +msgid "" +"Find the key called ``web.base.url`` (or create it if it does not exist) and" +" enter the full address of your website as value, such as " +"``https://www.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:319 +msgid "" +"The URL must include the protocol ``https://`` (or ``http://``) and must not" +" end with a slash (``/``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:322 +msgid "" +"To prevent the automatic update of the web base URL when an administrator " +"logs in the database, you can create the following System Parameter:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:325 +msgid "key: ``web.base.url.freeze``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:326 +msgid "value: ``True``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:331 +msgid "Map your domain name with your website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:333 +msgid "" +"Mapping your domain name to your website isn't the same as mapping it with " +"your database:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:335 +msgid "" +"It defines your domain name as the main one for your website, helping search" +" engines to index your website properly." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:337 +msgid "" +"It defines your domain name as the base URL for your database, including the" +" portal links sent by email to your customers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:339 +msgid "" +"If you have multiple websites, it maps your domain name with the appropriate" +" website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:341 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings --> Website " +"Info`. If you have multiple websites, select the one you want to configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:344 +msgid "" +"In the :guilabel:`Domain` field, fill in the web address of your website " +"(e.g., ``https://www.example.com``) and click on :guilabel:`Save`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Configuring https://www.example.com as the Domain of the website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:352 +msgid "" +"Mapping your domain name with your Odoo website prevents Google from " +"indexing both your custom domain name ``www.example.com`` and your original " +"odoo database address ``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:355 +msgid "" +"If both addresses are already indexed, it may take some time before Google " +"removes the indexation of the second address. You may also try using the " +"`Google Search Console `_ to fix " +"this." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:360 +msgid "" +"If you have multiple websites and companies on your database, make sure that" +" you select the right :guilabel:`Company` in the website settings, next to " +"the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as" +" the :ref:`base URL ` according to the company in " +"use." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:366 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:12 +#: ../../content/administration/maintain/enterprise.rst:31 +#: ../../content/administration/maintain/enterprise.rst:63 +#: ../../content/administration/maintain/enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:17 +#: ../../content/administration/maintain/enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../install/source`)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:3 +msgid "Connect Gmail to Odoo using Google OAuth" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:5 +msgid "" +"Odoo is compatible with Google's OAuth for Gmail. In order to send secure " +"emails from a custom domain, all that is required is to configure a few " +"settings on Google's *Workspace* platform, as well as on the back end of the" +" Odoo database. This configuration works by using either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:11 +msgid "" +"For more information, visit `Google's documentation " +"`_ on setting up OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:15 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:19 +msgid "Setup in Google" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:22 +msgid "Create a new project" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:24 +msgid "" +"To get started, go to the `Google API Console " +"`_. Log in with your *Google " +"Workspace* account if you have one, otherwise log in with your personal " +"Gmail account (this should match the email address you want to configure in " +"Odoo)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:28 +msgid "" +"After that, click on :guilabel:`Create Project`, located on the far right of" +" the :guilabel:`OAuth consent screen`. If a project has already been created" +" in this account, then the :guilabel:`New Project` option will be located on" +" the top right under the :guilabel:`Select a project` drop-down menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:33 +msgid "" +"On the :menuselection:`New Project` screen, rename the :guilabel:`Project " +"name` to `Odoo` and browse for the :guilabel:`Location`. Set the " +":guilabel:`Location` as the *Google Workspace organization*. If you are " +"using a personal Gmail account, then leave the :guilabel:`Location` as " +":guilabel:`No Organization`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Project Name and Location for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:42 +msgid "Click on :guilabel:`Create` to finish this step." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:45 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:47 +msgid "" +"If the page doesn't redirect to the :menuselection:`User Type` options, " +"click on :guilabel:`OAuth consent screen` in the left menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:50 +msgid "" +"Under :guilabel:`User Type` options, select the appropriate :guilabel:`User " +"Type`, and then click on :guilabel:`Create` again, which will finally " +"navigate to the :menuselection:`Edit app registration` page." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:55 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:59 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:63 +msgid "Edit app registration" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:65 +msgid "Next we will configure the app registration of the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:67 +msgid "" +"On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App " +"information` section, enter `Odoo` in the :guilabel:`App name` field. Select" +" the organization's email address under the :guilabel:`User support` email " +"field." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:71 +msgid "" +"Next, under :menuselection:`App Domain --> Authorized domains`, click on " +":guilabel:`Add Domain` and enter `odoo.com`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:74 +msgid "" +"After that, under the :guilabel:`Developer contact information` section, " +"enter the organization's email address. Google uses this email address to " +"notify the organization about any changes to your project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:78 +msgid "" +"Next, click on the :guilabel:`Save and Continue` button. Then, skip the " +":menuselection:`Scopes` page by scrolling to the bottom and clicking on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:81 +msgid "" +"If continuing in testing mode (External), add the email addresses being " +"configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:85 +msgid "" +"Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to " +"finish setting up the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:89 +msgid "Create Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:91 +msgid "" +"Now that the project is set up, credentials should be created, which " +"includes the *Client ID* and *Client Secret*. First, click on " +":guilabel:`Credentials` in the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:94 +msgid "" +"Then, click on :guilabel:`Create Credentials` in the top menu and select " +":guilabel:`OAuth client ID` from the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:97 +msgid "" +"Under :guilabel:`Application Type`, select :guilabel:`Web Application` from " +"the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:98 +msgid "In the :guilabel:`Name` field, enter `Odoo`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:99 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` label, click the button " +":guilabel:`ADD URI`, and then input " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1`" +" field. Be sure to replace the *yourdbname* part of the URL with the actual " +"Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:102 +msgid "" +"Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID`" +" and :guilabel:`Client Secret`. Finally, copy each generated value for later" +" use when configuring in Odoo, and then navigate to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Client ID and Client Secret for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:114 +msgid "Enter Google Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:116 +msgid "" +"First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove " +"the :guilabel:`Apps` filter from the search bar and type in `Google`. " +"Install the module called :guilabel:`Google Gmail`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:120 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is " +"checked. This populates a new option for :guilabel:`Gmail Credentials` or " +":guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values " +"into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and " +":guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:129 +msgid "" +"To configure the external Gmail account, return to the top of the " +":guilabel:`Custom Email Servers` setting and then click the " +":guilabel:`Outgoing Email Servers` link." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Configure Outgoing Email Servers in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:136 +msgid "" +"Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email " +"server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the " +"email :guilabel:`Username` (if required)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:139 +msgid "" +"Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` " +"(under the :guilabel:`Authenticate with` or :guilabel:`Connection` section)." +" Finally, click on :guilabel:`Connect your Gmail Account`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:143 +msgid "" +"A new window labeled :guilabel:`Google` opens to complete the authorization " +"process. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:146 +msgid "" +"If the email address is a personal account, then an extra step pops up, so " +"click :guilabel:`Continue` to allow the verification and connect the Gmail " +"account to Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:149 +msgid "" +"Then, allow Odoo to access the Google account by clicking on " +":guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates " +"back to the newly configured outgoing email server in Odoo. The " +"configuration automatically loads the token in Odoo, and a tag stating " +":guilabel:`Gmail Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:158 +msgid "" +"Finally, :guilabel:`Test the Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Google " +"using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:162 +msgid "Google OAuth FAQ" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:165 +msgid "Production VS Testing Publishing Status" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:167 +msgid "" +"Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` " +"(instead of :guilabel:`Testing`) will display the following warning message:" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "OAuth is Limited to 100 Sensitive Scope Logins." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:174 +msgid "" +"To correct this warning, navigate to the `Google API Platform " +"`_. If the " +":guilabel:`Publishing status` is :guilabel:`In Production`, click " +":guilabel:`Back to Testing` to correct the issue." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:179 +msgid "No Test Users Added" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:181 +msgid "" +"If no test users are added to the OAuth consent screen, then a 403 access " +"denied error will populate." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "403 Access Denied Error." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:188 +msgid "" +"To correct this error, return to the :guilabel:`OAuth consent screen` under " +":guilabel:`APIs & Services` and add test user(s) to the app. Add the email " +"that you are configuring in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:192 +msgid "Gmail Module not updated" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:194 +msgid "" +"If the *Google Gmail* module in Odoo has not been updated to the latest " +"version, then a :guilabel:`Forbidden` error message populates." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "" +"Forbidden you don't have the permission to access the requested resource." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:201 +msgid "" +"To correct this error, go to the :menuselection:`Apps` module and clear out " +"the search terms. Then, search for `Gmail` or `Google` and upgrade the " +":guilabel:`Google Gmail` module. Finally, click on the three dots on the " +"upper right of the module and select :guilabel:`Upgrade`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:206 +msgid "Application Type" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:208 +msgid "" +"When creating the credentials (OAuth *Client ID* and *Client Secret*), if " +":guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an" +" :guilabel:`Authorization Error` appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Error 400 Redirect URI Mismatch." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:215 +msgid "" +"To correct this error, delete the credentials already created and create new" +" credentials, selecting :guilabel:`Web Application` for the " +":guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect " +"URIs`, click :guilabel:`ADD URI` and type: " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure " +"to replace *yourdbname* in the URL with the Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:3 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:5 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:9 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:12 +#: ../../content/administration/maintain/hosting_changes.rst:80 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:15 +#: ../../content/administration/maintain/hosting_changes.rst:83 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:16 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:18 +msgid "Create a :ref:`duplicate ` of the database." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:19 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:20 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:21 +msgid "" +"`Submit a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:23 +#: ../../content/administration/maintain/hosting_changes.rst:88 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:24 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:25 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:27 +#: ../../content/administration/maintain/hosting_changes.rst:95 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:31 +#: ../../content/administration/maintain/hosting_changes.rst:99 +msgid "" +"If you have time constraints, `submit a support ticket " +"`_ as soon as possible to schedule the transfer." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:35 +#: ../../content/administration/maintain/hosting_changes.rst:67 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:37 +#: ../../content/administration/maintain/hosting_changes.rst:73 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:41 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:44 +msgid "" +"Odoo Online's :ref:`intermediary versions ` cannot be " +"hosted on-premise as that type of hosting does not support those versions. " +"Therefore, if the database to transfer is running an intermediary version, " +"it must be upgraded first to the next :ref:`major version " +"`, waiting for its release if necessary." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:50 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:54 +msgid "" +"Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo " +"Online database manager `_ to display " +"its version number." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:58 +#: ../../content/administration/maintain/hosting_changes.rst:108 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:60 +#: ../../content/administration/maintain/hosting_changes.rst:69 +msgid "" +"Sign in to `the Odoo Online database manager " +"`_ and click the gear icon " +"(:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. " +"If the download fails due to the file being too large, `contact Odoo support" +" `_." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:64 +#: ../../content/administration/maintain/hosting_changes.rst:111 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:77 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:85 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:86 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:89 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:90 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:91 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:92 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:93 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:101 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:102 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:103 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:105 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:110 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:3 +msgid "Mailjet API" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:5 +msgid "" +"Odoo is compatible with Mailjet's :abbr:`API (Application Programming " +"Interface)` for mass mailing. Set up a dedicated mass mailing server through" +" Mailjet by configuring settings in the Mailjet account and the Odoo " +"database. In some circumstances, settings need to be configured on the " +"custom domain's :abbr:`DNS (Domain Name System)` settings as well." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:11 +msgid "Set up in Mailjet" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:14 +msgid "Create API credentials" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:16 +msgid "" +"To get started, sign in to the `Mailjet Account Information " +"`_ page. Next, navigate to the " +":guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND " +"API Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "" +"SMTP and Send API Settings link in the Senders & Domains section of Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:24 +msgid "" +"Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration " +"settings onto a notepad. They can be found under the " +":guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail " +"Transfer Protocol)` configuration settings include the server address, the " +"security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS " +"(Transport Layer Security)`), and the port number. The settings are needed " +"to configure Mailjet in Odoo, which is covered in the :ref:`last section " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:32 +msgid "" +"`Mailjet: How can I configure my SMTP parameters? " +"`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:36 +msgid "" +"Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See " +"reference here `." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "SMTP configuration from Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:43 +msgid "" +"Next, click on the button labeled :guilabel:`Retrieve your API credentials` " +"to retrieve the Mailjet API credentials." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:46 +msgid "" +"Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key" +" to a notepad, as this serves as the :guilabel:`Username` in the Odoo " +"configuration. Next, click on the :guilabel:`Generate Secret Key` button to " +"generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this " +"serves as the :guilabel:`Password` in the Odoo configuration." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:52 +msgid "Add verified sender address(es)" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:54 +msgid "" +"The next step is to add a sender address or a domain to the Mailjet account " +"settings so that the email address or domain is approved to send emails " +"using Mailjet's servers. First, navigate to the `Mailjet Account Information" +" `_ page. Next, click on the :guilabel:`Add" +" a Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Add a sender domain or address in the Mailjet interface." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:63 +msgid "" +"Determine if a sender's email address or the entire domain needs to be added" +" to the Mailjet settings. It may be easier to configure the domain as a " +"whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the " +":ref:`Add a domain ` section for steps on " +"adding the domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:69 +msgid "" +"Either all email addresses of the Odoo database users who are sending emails" +" using Mailjet's servers need to be configured or the domain(s) of the " +"users' email addresses can be configured." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:72 +msgid "" +"By default, the email address originally set up in the Mailjet account is " +"added as a trusted sender. To add another email address, click on the button" +" labeled :guilabel:`Add a sender address`. Then, add the email address that " +"is configured to send from the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:76 +msgid "" +"At minimum the following email addresses should be set up in the provider " +"and verified in Mailjet:" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:78 +msgid "notifications\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:79 +msgid "bounce\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:80 +msgid "catchall\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:83 +msgid "" +"Replace `yourdomain` with the custom domain for the Odoo database. If there " +"isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:86 +msgid "" +"After that, fill out the :guilabel:`Email Information` form, making sure to " +"select the appropriate email type: transactional email or mass emails. After" +" completing the form, an activation email is sent to the email address and " +"the trusted sender can be activated." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:90 +msgid "" +"It is recommended to set up the :abbr:`SPF (Sender Policy " +"Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, and Conformance)` settings on the " +"domain of the sender." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:95 +#: ../../content/administration/maintain/mailjet_api.rst:162 +msgid "" +"`Mailjet's SPF/DKIM/DMARC documentation " +"`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:99 +msgid "" +"If the database is not using a custom domain, then in order to verify the " +"sender's address, a temporary alias (of the three email addresses mentioned " +"above) should be set up in Odoo CRM to create a lead. Then, the database is " +"able to receive the verification email and verify the accounts." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:107 +msgid "Add a domain" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:109 +msgid "" +"By adding an entire domain to the Mailjet account, all the sender addresses " +"related to that domain are automatically validated for sending emails using " +"Mailjet servers. First, navigate to the `Mailjet Account Information " +"`_ page. Next, click on :guilabel:`Add a " +"Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section. Then, click on :guilabel:`Add domain` to add the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:116 +msgid "" +"The domain needs to be added to the Mailjet account and then validated " +"through the :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:119 +msgid "" +"After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and " +"click :guilabel:`Continue`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:122 +msgid "" +"After adding the domain, a validation page will populate. Unless the Odoo " +"database is on-premise (in which case, choose :guilabel:`Option 1`), choose " +":guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information " +"to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name " +"System)` provider to complete validation." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "The TXT record information to input on the domain's DNS." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:132 +msgid "Setup in the domain's DNS" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:134 +msgid "" +"After getting the TXT record information from the Mailjet account, add a TXT" +" record to the domain's :abbr:`DNS (Domain Name System)`. This process " +"varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult " +"the provider for specific configuration processes. The TXT record " +"information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste " +"these into the corresponding fields in the TXT record." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:141 +msgid "Return to Mailjet account information" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:143 +msgid "" +"After adding the TXT record to the domain's :abbr:`DNS (Domain Name " +"System)`, navigate back to the Mailjet account. Then, navigate to " +":menuselection:`Account Information --> Add a Sender Domain or Address`, " +"click the gear icon next to :guilabel:`Domain`, and select " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:147 +msgid "" +"This action can also be done by going to the `Sender domains & addresses " +"`_ page on the Mailjet account " +"information and clicking on :guilabel:`Manage`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:150 +msgid "" +"Next, click :guilabel:`Check Now` to validate the TXT record that was added " +"on the domain. A success screen will appear if the domain is configured " +"correctly." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Check DNS record in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:157 +msgid "" +"After successfully setting up the domain, there is an option to " +":guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates " +":abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified " +"Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Authenticate the domain with SPF/DKIM records in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:172 +msgid "Set up in Odoo" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:174 +msgid "" +"To complete the setup, navigate to the Odoo database and go to the " +":guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the " +":menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, " +"create a new outgoing server configuration by clicking on the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:179 +msgid "" +"Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or " +"465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet " +"account. They can also be found `here " +"`_. It is recommended to use " +":abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` " +"even though Mailjet may not require it." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:184 +msgid "" +"For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the " +":guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from " +"the Mailjet account to the notepad earlier. These settings can be found on " +":menuselection:`Mailjet --> Account Settings --> SMTP and SEND API " +"Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:189 +msgid "" +"Then, if the Mailjet server is used for mass emailing, set the " +":guilabel:`Priority` value higher than that of any transactional email " +"server(s). Finally, save the settings and :guilabel:`Test the Connection`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Odoo outgoing email server settings." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:198 +msgid "" +"In order for the notifications feature to work using Mailjet, there are " +"three settings that need to be set in Odoo." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:201 +msgid "" +"The :guilabel:`From Filter` needs to be set on the server configuration. It " +"is recommended to set it as a domain and not a full email address. It should" +" match the domain in the two proceeding steps. More information can be " +"referenced :ref:`here `." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:205 +msgid "" +"The :guilabel:`mail.default.from` system parameter must have the value " +"`notifications\\@yourdomain.com`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:207 +msgid "" +"The :guilabel:`mail.default.from_filter` system parameter must have the " +"value `yourdomain.com`. Replace `yourdomain` with the custom domain for the " +"Odoo database. If there isn't one, then use the " +":guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:211 +msgid "" +"For more information see :ref:`Using a default email address " +"`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:213 +msgid "" +"The :guilabel:`System Parameters` can be accessed by activating " +":doc:`../../applications/general/developer_mode` in the " +":menuselection:`Settings --> Technical --> Parameters --> System Parameters`" +" menu." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:217 +msgid "" +"Once the setup is complete, the Odoo database is ready to use the Mailjet " +"email server for mass mailing or transactional emails!" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:3 +msgid "Odoo Online database management" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:5 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:8 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:15 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:16 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:17 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:18 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:19 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:20 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:21 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:22 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:23 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:28 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:77 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:30 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:33 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:39 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:41 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:45 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:47 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:52 +msgid "Rename" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:54 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:59 +msgid "Download" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:61 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:64 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:72 +msgid "" +"Use a custom :doc:`domain name ` to access the database via " +"another URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:75 +msgid "" +"You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:80 +msgid "Tags" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:82 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:85 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:90 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:92 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:95 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:98 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:105 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:106 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:107 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:113 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:115 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:121 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:123 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:129 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:132 +msgid ":doc:`/applications/general/users/manage_users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:133 +msgid ":doc:`/applications/general/users/odoo_account`" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:3 +msgid "On-premise database management" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:6 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:8 +msgid "" +"To register your database, you just need to enter your Subscription Code in " +"the banner in the App Switcher. Make sure you do not add extra spaces before" +" or after your subscription code. If the registration is successful, it will" +" turn green and will provide you with the Expiration Date of your freshly-" +"registered database. You can check this Expiration Date in the About menu " +"(Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:16 +msgid "Registration Error Message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:18 +msgid "" +"If you are unable to register your database, you will likely encounter this " +"message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"Something went wrong while registering your database, you can try again or contact Odoo\n" +"Help" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:27 +#: ../../content/administration/maintain/on_premise.rst:100 +#: ../../content/administration/maintain/on_premise.rst:127 +msgid "Solutions" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:29 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:31 +msgid "" +"Check if your subscription details get the tag \"In Progress\" on your `Odoo" +" Account `__ or with your Account" +" Manager" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:35 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:37 +msgid "" +"You can link only one database per subscription. (Need a test or a " +"development database? `Find a partner `__)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:41 +msgid "" +"You can unlink the old database yourself on your `Odoo Contract " +"`__ with the button \"Unlink " +"database\"" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:47 +msgid "" +"A confirmation message will appear; make sure this is the correct database " +"as it will be deactivated shortly:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:53 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:55 +#: ../../content/administration/maintain/on_premise.rst:159 +msgid "" +"From July 2016 onward, Odoo 9 now automatically change the uuid of a " +"duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:58 +msgid "" +"If it's not the case, you may have multiple databases sharing the same UUID." +" Please check on your `Odoo Contract " +"`__, a short message will appear " +"specifying which database is problematic:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:66 +msgid "" +"In this case, you need to change the UUID on your test databases to solve " +"this issue. You will find more information about this in :ref:`this section " +"`." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:69 +msgid "" +"For your information, we identify database with UUID. Therefore, each " +"database should have a distinct UUID to ensure that registration and " +"invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:73 +msgid "Check your network and firewall settings" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:75 +msgid "" +"The Update notification must be able to reach Odoo's subscription validation" +" servers. In other words, make sure that the Odoo server is able to open " +"outgoing connections towards:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:79 +msgid "services.odoo.com on port 443 (or 80)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:80 +msgid "services.openerp.com on port 443 (or 80) for older deployments" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:82 +msgid "" +"Once you activated your database, you must keep these ports open, as the " +"Update notification runs once a week." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:86 +msgid "Error message due to too many users" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:88 +msgid "" +"If you have more users in your local database than provisionned in your Odoo" +" Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"This database will expire in X days, you have more users than your " +"subscription allows" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:96 +msgid "" +"When the message appears you have 30 days before the expiration. The " +"countdown is updated everyday." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:102 +msgid "" +"**Add more users** on your subscription: follow the link and Validate the " +"upsell quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:104 +msgid "" +"**Deactivate users** as explained in this `documentation " +"`_ and **Reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:107 +msgid "" +"Once your database has the correct number of users, the expiration message " +"will disappear automatically after a few days, when the next verification " +"occurs. We understand that it can be a bit frightening to see the countdown," +" so you can :ref:`force an Update Notification ` to make the " +"message disappear right away." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:114 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:116 +msgid "" +"If your database reaches its expiration date before your renew your " +"subscription, you will encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "This database has expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:123 +msgid "" +"This **blocking** message appears after a non-blocking message that lasts 30" +" days. If you fail to take action before the end of the countdown, the " +"database is expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:131 +msgid "" +"Renew your subscription: follow the link and renew your subscription - note " +"that" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:130 +msgid "" +"if you wish to pay by Wire Transfer, your subscription will effectively be " +"renewed only when the payment arrives, which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:133 +msgid "Contact our `Support `__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:135 +msgid "" +"None of those solutions worked for you? Please contact our `Support " +"`__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:143 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:145 +msgid "" +"You can duplicate your database by accessing the database manager on your " +"server (/web/database/manager). In this page, you can easily " +"duplicate your database (among other things)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:152 +msgid "" +"When you duplicate a local database, it is **strongly** advised to change " +"the duplicated database's uuid (Unniversally Unique Identifier), since this " +"uuid is how your database identifies itself with our servers. Having two " +"databases with the same uuid could result in invoicing problems or " +"registration problems down the line." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:162 +msgid "" +"The database uuid is currently accessible from the menu " +":menuselection:`Settings --> Technical --> System Parameters`, we advise you" +" to use a `uuid generator `_ or to use the unix " +"command ``uuidgen`` to generate a new uuid. You can then simply replace it " +"like any other record by clicking on it and using the edit button." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` " +"them regularly." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:34 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:36 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:65 +#: ../../content/administration/maintain/supported_versions.rst:66 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:83 +#: ../../content/administration/maintain/supported_versions.rst:84 +#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 +msgid "|green|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:93 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:39 +msgid "November 2026 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:40 +msgid "Odoo saas~16.4" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:79 +msgid "N/A" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:44 +msgid "August 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:46 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:59 +#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:89 +#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:96 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:101 +#: ../../content/administration/maintain/supported_versions.rst:102 +#: ../../content/administration/maintain/supported_versions.rst:103 +msgid "|red|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:50 +msgid "June 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:52 +msgid "Odoo saas~16.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:56 +msgid "March 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:58 +msgid "Odoo saas~16.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:62 +msgid "February 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:64 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:99 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:69 +msgid "November 2025 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:70 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:74 +msgid "March 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:75 +msgid "January 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:76 +msgid "Odoo saas~15.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:80 +msgid "February 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:81 +msgid "July 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:82 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:86 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:87 +msgid "November 2024 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:88 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:92 +msgid "October 2020" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:94 +msgid "**Odoo 13.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:98 +msgid "October 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:100 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:104 +msgid "Before 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:105 +msgid "Before 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:107 +msgid "Legend" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:109 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:111 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:116 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/maintain/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/maintain/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/maintain/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/maintain/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/maintain/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/maintain/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/maintain/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/maintain/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/maintain/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/maintain/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../install>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/maintain/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/maintain/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/maintain/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/maintain/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/maintain/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/maintain/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/maintain/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/maintain/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/maintain/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/maintain/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/maintain/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/maintain/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/maintain/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/maintain/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/maintain/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/maintain/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:170 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:109 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:117 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:124 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF " +"` and :ref:`DKIM " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of " +"Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../maintain/on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../install/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/getting_started` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are two levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid "Admin: has access to all features of Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:39 +msgid "" +"User: does not have access to the project settings nor to the production and" +" staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:41 +msgid "" +"The user group is meant for developers who can make modifications in your " +"code but are not allowed to access the production data. Users of this group " +"cannot connect to the production and staging databases using the *1-click " +"connect* feature, but they can of course use their regular account on these " +"databases if they have one, using their regular credentials." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:46 +msgid "" +"In addition, they cannot use the webshell nor have access to the server " +"logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "User" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:97 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +msgid "Production & Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +msgid "|green|\\*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:120 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +msgid "\\* Only in staging branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:145 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:147 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:152 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to connect to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:155 +msgid "" +"In addition, visitors have access to the logs, shell and mails of your " +"development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:157 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:162 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:164 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:172 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:183 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:188 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:190 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:192 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:193 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:196 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:198 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:200 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:202 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:203 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:204 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:205 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:208 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:210 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:215 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:217 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:219 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:222 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:225 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:231 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:239 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:245 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:247 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:254 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:256 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/upgrade.rst:7 +msgid "" +"An upgrade is the process of moving your database from an older version to a" +" newer :doc:`supported version ` (e.g., Odoo " +"14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes " +"with new and improved features, bug fixes, and security patches." +msgstr "" + +#: ../../content/administration/upgrade.rst:15 +msgid "" +"The Rolling Release process allows Odoo Online customers to upgrade their " +"database directly from a message prompt sent to the database administrator " +"as soon as a new version is released. The invitation to upgrade is only sent" +" if no issues are detected during the automatic tests." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:22 +msgid "" +"It is strongly recommended to manually :ref:`test the upgrade first " +"`. Clicking :guilabel:`I want to test first` redirects" +" to `the database manager `_, where it " +"is possible to request an upgraded test database and check it for any " +"discrepancies." +msgstr "" + +#: ../../content/administration/upgrade.rst:27 +msgid "" +"It is **not** recommended to click :guilabel:`Upgrade Now` without testing " +"first, as it immediately triggers the live production database upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:30 +msgid "" +"If the Rolling Release process detects an issue with the upgrade, it will be" +" deactivated until the issue is resolved." +msgstr "" + +#: ../../content/administration/upgrade.rst:33 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:35 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:36 +msgid "" +":doc:`Switching editions ` (e.g., from Community to " +"Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +":doc:`Changing hosting type ` " +"(e.g., from on-premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:39 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:42 +msgid "" +"If your database contains custom modules, it cannot be upgraded until a " +"version of your custom modules is available for the target version of Odoo. " +"For customers maintaining their own custom modules, we recommend to " +"parallelize the process by :ref:`requesting an upgraded database " +"` while also :doc:`upgrading the source code " +"of your custom modules `." +msgstr "" + +#: ../../content/administration/upgrade.rst:50 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "" +"If applicable, upgrade the source code of your custom module to be " +"compatible with the new version of Odoo (see " +":doc:`/developer/howtos/upgrade_custom_db`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "" +"Report any issue encountered during the testing to Odoo via the `support " +"page `__." +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +msgid "" +"Once all issues are resolved and you are confident that the upgraded " +"database can be used as your main database without any issues, plan the " +"upgrade of your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:67 +msgid "" +"Request the upgrade for the production database, rendering it unavailable " +"for the time it takes to complete the process (see :ref:`upgrading the " +"production database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:70 +msgid "" +"Report any issue encountered during the upgrade to Odoo via the `support " +"page `__." +msgstr "" + +#: ../../content/administration/upgrade.rst:76 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:78 +msgid "" +"The `Upgrade page `_ is the main platform for " +"requesting an upgraded database. However, depending on the hosting type, you" +" can upgrade from the command line (on-premise), the `Odoo Online database " +"manager `_, or your `Odoo.sh project " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +msgid "" +"The Upgrade platform follows the same `Privacy Policy " +"`_ as the other Odoo.com services. Visit the " +"`General Data Protection Regulation page `_ to " +"learn more about how Odoo handles your data and privacy." +msgstr "" + +#: ../../content/administration/upgrade.rst:92 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "" +"The database manager displays all databases associated with the user's " +"account. Databases not on the most recent version of Odoo display an arrow " +"in a circle icon next to their name, indicating that they can be upgraded." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:102 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:104 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:105 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:106 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:112 +msgid "" +"The :guilabel:`Upgrade in progress` tag is displayed next to the database " +"name until completion. Once the process succeeds, an email containing a link" +" to the upgraded test database is sent to the address provided. The database" +" can also be accessed from the database manager by clicking the dropdown " +"arrow before the database name." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:122 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:127 +msgid "" +"The **latest production daily automatic backup** is then sent to the " +"`upgrade platform `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:130 +msgid "" +"Once the upgrade platform is done upgrading the backup and uploading it on " +"the branch, it is put in a **special mode**: each time a **commit is " +"pushed** on the branch, a **restore operation** of the upgraded backup and " +"an **update of all the custom modules** occur. This allows you to test your " +"custom modules on a pristine copy of the upgraded database. The log file of " +"the upgrade process can be found in your newly upgraded staging build by " +"going to :file:`~/logs/upgrade.log`." +msgstr "" + +#: ../../content/administration/upgrade.rst:138 +msgid "" +"In databases where custom modules are installed, their source code must be " +"up-to-date with the target version of Odoo before the upgrade can be " +"performed. If there are none, the \"update on commit\" mode is skipped, the " +"upgraded database is built as soon as it is transferred from the upgrade " +"platform, and the upgrade mode is exited." +msgstr "" + +#: ../../content/administration/upgrade.rst:143 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:145 +#: ../../content/administration/upgrade.rst:341 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/upgrade.rst:147 +msgid "" +"The standard upgrade process can be initiated by entering the following " +"command line on the machine where the database is hosted:" +msgstr "" + +#: ../../content/administration/upgrade.rst:154 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:160 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:164 +msgid "" +"In databases where custom modules are installed, their source code must be " +"up-to-date with the target version of Odoo before the upgrade can be " +"performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for" +" more information." +msgstr "" + +#: ../../content/administration/upgrade.rst:169 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:170 +msgid "" +"For storage reasons, the database's copy is submitted without a filestore to" +" the upgrade server. Therefore, the upgraded database does not contain the " +"production filestore." +msgstr "" + +#: ../../content/administration/upgrade.rst:172 +msgid "" +"Before restoring the upgraded database, its filestore must be merged with " +"the production filestore to be able to perform tests in the same conditions " +"as it would be in the new version." +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:177 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"A `filestore` folder containing files extracted from in-database records " +"into attachments (if there are any) and new standard Odoo files from the " +"targeted Odoo version (e.g., new images, icons, payment provider's logos, " +"etc.). This is the folder that should be merged with the production " +"filestore in order to get the full upgraded filestore." +msgstr "" + +#: ../../content/administration/upgrade.rst:185 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:190 +msgid "" +"When an upgrade request is completed, an upgrade report is attached to the " +"successful upgrade email, and it becomes available in the Discuss app for " +"users who are part of the \"Administration / Settings\" group. This report " +"provides important information about the changes introduced by the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:198 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:200 +msgid "" +"It is essential to spend some time testing the upgraded test database to " +"ensure that you are not stuck in your day-to-day activities by a change in " +"views, behavior, or an error message once the upgrade goes live." +msgstr "" + +#: ../../content/administration/upgrade.rst:205 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:208 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:209 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +msgid "" +"Bank synchronization is disabled. Should you want to test the " +"synchronization, contact your bank synchronization provider to get sandbox " +"credentials." +msgstr "" + +#: ../../content/administration/upgrade.rst:214 +msgid "" +"Testing as many of your business flows as possible is strongly recommended " +"to ensure they are working correctly and to get more familiar with the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:217 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:219 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:222 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:223 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:224 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:226 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:227 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:228 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:229 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:233 +msgid "" +"Checking a random product in your product catalog and comparing its test and" +" production data to verify everything is the same (product category, selling" +" price, cost price, vendor, accounts, routes, etc.)." +msgstr "" + +#: ../../content/administration/upgrade.rst:236 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:237 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:238 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:243 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:244 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:246 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:247 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:249 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:251 +msgid "" +"Making an online order (Website apps) from the product selection in your " +"shop until the checkout process and checking if everything behaves as in " +"your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:256 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo via the `support page " +"`__ by selecting the option related " +"to testing the upgrade. In any case, it is essential to report any problem " +"encountered during the testing to fix it before upgrading your production " +"database." +msgstr "" + +#: ../../content/administration/upgrade.rst:261 +msgid "" +"You might encounter significant differences with standard views, features, " +"fields, and models during testing. Those changes cannot be reverted on a " +"case-by-case basis. However, if a change introduced by a new version breaks " +"a customization, it is the responsibility of the maintainer of your custom " +"module to make it compatible with the new version of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:267 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:270 +msgid "" +"Workflows between different apps (online sales with eCommerce, converting a " +"lead all the way to a sales order, delivery of products, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:273 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "" +"Server actions in the action menu on form views, as well as by selecting " +"multiple records on list views" +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +msgid "" +"Once the :ref:`tests ` are completed and you are " +"confident that the upgraded database can be used as your main database " +"without any issues, it is time to plan the go-live day. It can be planned in" +" coordination with Odoo's upgrade support analysts, reachable via the " +"`support page `__." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"Your production database will be unavailable during its upgrade. Therefore, " +"we recommend planning the upgrade at a time when the use of the database is " +"minimal." +msgstr "" + +#: ../../content/administration/upgrade.rst:290 +msgid "" +"As the standard upgrade scripts and your database are constantly evolving, " +"it is also recommended to frequently request another upgraded test database " +"to ensure that the upgrade process is still successful, especially if it " +"takes a long time to finish. **Fully rehearsing the upgrade process the day " +"before upgrading the production database is also recommended.**" +msgstr "" + +#: ../../content/administration/upgrade.rst:296 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:298 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:299 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:300 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:309 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"`, except for the purpose option, which must " +"be set to :guilabel:`Production` instead of :guilabel:`Test`." +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +msgid "" +"Once the upgrade is requested, the database will be unavailable until the " +"upgrade is finished. Once the process is completed, it is impossible to " +"revert to the previous version." +msgstr "" + +#: ../../content/administration/upgrade.rst:320 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:326 +msgid "" +"The process is **triggered as soon as a new commit is made** on the branch. " +"This allows the upgrade process to be synchronized with the deployment of " +"the custom modules' upgraded source code. If there are no custom modules, " +"the upgrade process is triggered immediately." +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The database is unavailable throughout the process. If anything goes wrong, " +"the platform automatically reverts the upgrade, as it would be for a regular" +" update. In case of success, a backup of the database before the upgrade is " +"created." +msgstr "" + +#: ../../content/administration/upgrade.rst:336 +msgid "" +"The update of your custom modules must be successful to complete the entire " +"upgrade process. Make sure the status of your staging upgrade is " +":guilabel:`successful` before trying it in production. More information on " +"how to upgrade your custom modules can be found on " +":doc:`/developer/howtos/upgrade_custom_db`." +msgstr "" + +#: ../../content/administration/upgrade.rst:343 +msgid "" +"The command to upgrade a database to production is similar to the one of " +"upgrading a test database except for the argument `test`, which must be " +"replaced by `production`:" +msgstr "" + +#: ../../content/administration/upgrade.rst:350 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_. Once the database is uploaded, any " +"modification to your production database will **not** be present on your " +"upgraded database. This is why we recommend not using it during the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:357 +msgid "" +"When requesting an upgraded database for production purposes, the copy is " +"submitted without a filestore. Therefore, the upgraded database filestore " +"must be merged with the production filestore before deploying the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:361 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo via the `support page " +"`__ by selecting the option " +"related to the upgrade in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:369 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:371 +msgid "" +"With Odoo Enterprise, upgrading a database to the most recent version of " +"Odoo is **free**, including any support required to rectify potential " +"discrepancies in the upgraded database." +msgstr "" + +#: ../../content/administration/upgrade.rst:374 +msgid "" +"Information about the upgrade services included in the Enterprise Licence is" +" available in the :ref:`Odoo Enterprise Subscription Agreement `. " +"However, this section clarifies what upgrade services you can expect." +msgstr "" + +#: ../../content/administration/upgrade.rst:379 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:381 +msgid "" +"Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or " +"self-hosted (On-Premise) can benefit from upgrade services at all times for:" +msgstr "" + +#: ../../content/administration/upgrade.rst:384 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:385 +msgid "" +"the upgrade of all **customizations created with the Studio app**, as long " +"as Studio is still installed and the respective subscription is still " +"active; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:387 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:390 +msgid "" +"Upgrade services are limited to the technical conversion and adaptation of a" +" database (standard modules and data) to make it compatible with the version" +" targeted by the upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:394 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:396 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:398 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "" +"the upgrade of **custom modules created in-house or by third parties**, " +"including Odoo partners;" +msgstr "" + +#: ../../content/administration/upgrade.rst:400 +msgid "" +"lines of **code added to standard modules**, i.e., customizations created " +"outside the Studio app, code entered manually, and :ref:`automated actions " +"using Python code `; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:403 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:406 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:407 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/hi/LC_MESSAGES/applications.po b/locale/hi/LC_MESSAGES/applications.po new file mode 100644 index 000000000..ba048665d --- /dev/null +++ b/locale/hi/LC_MESSAGES/applications.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-11-08 08:46+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications.rst:9 +msgid "User Docs" +msgstr "" + +#: ../../content/applications.rst:11 +msgid "Discover our user guides and configuration tutorials per application." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/finance.po b/locale/hi/LC_MESSAGES/finance.po new file mode 100644 index 000000000..40b6da9c0 --- /dev/null +++ b/locale/hi/LC_MESSAGES/finance.po @@ -0,0 +1,39355 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/finance.rst:5 +msgid "Finance" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:5 +msgid "Accounting and Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:7 +msgid "" +"**Odoo Invoicing** is a standalone invoicing app to create invoices, send " +"them to your customers, and manage payments." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:10 +msgid "" +"**Odoo Accounting** is a full featured accounting app. Accountant " +"productivity is at the core of its development with features such as AI-" +"powered invoice recognition, synchronization with your bank accounts, smart " +"matching suggestions, etc." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:15 +msgid "" +"`Odoo Tutorials: Accounting `_" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:56 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:58 +msgid "" +"Odoo automatically creates all the underlying journal entries for all " +"accounting transactions (e.g., customer invoices, vendor bills, point-of-" +"sales orders, expenses, inventory valuations, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:61 +msgid "" +"Odoo uses the double-entry bookkeeping system, whereby every entry needs a " +"corresponding and opposite counterpart in a different account, with one " +"account debited and the other credited. It ensures that all transactions are" +" recorded accurately and consistently and that the accounts always balance." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:67 +#: ../../content/applications/finance/accounting.rst:222 +msgid ":doc:`Accounting Cheat Sheet `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:70 +msgid "Accrual and cash basis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:72 +msgid "" +"Both accrual and cash basis accounting are supported in Odoo. This allows " +"reporting income and expense either when the transaction occurs (accrual " +"basis) or when the payment is made or received (cash basis)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:77 +msgid ":doc:`Cash basis `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:80 +msgid "Multi-company" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:82 +msgid "" +"Several companies can be managed within the same database. Each company has " +"its :doc:`chart of accounts `, " +"which is also useful to generate consolidation reports. Users can access " +"several companies but can only work on a single company's accounting at a " +"time." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:88 +msgid "Multi-currency environment" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:90 +msgid "" +"A :doc:`multi-currency ` environment " +"with an automated exchange rate to ease international transactions is " +"available in Odoo. Every transaction is recorded in the company's default " +"currency; for transactions occurring in another currency, Odoo stores both " +"the value in the company's currency and the transactions' currency value. " +"Odoo generates currency gains and losses after reconciling the journal " +"items." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:97 +msgid "" +":doc:`Manage a bank in a foreign currency " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:100 +msgid "Branch management" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:102 +msgid "" +"Multiple branches can be managed thanks to multi-company hierarchies. This " +"allows to post journal entries on each branch as well as setting up a common" +" lock date managed by the main company." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:106 +msgid "International standards" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:108 +msgid "" +"Odoo Accounting supports more than 70 countries. It provides the central " +"standards and mechanisms common to all nations, and thanks to country-" +"specific modules, local requirements are fulfilled. Fiscal positions exist " +"to address regional specificities like the chart of accounts, taxes, or any " +"other requirements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:114 +msgid ":doc:`Fiscal localization packages `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:117 +msgid "Accounts receivable and payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:119 +msgid "" +"By default, there is a single account for the account receivable entries and" +" one for the account payable entries. As transactions are linked to your " +"**contacts**, you can run a report per customer, vendor, or supplier." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:123 +msgid "" +"The **Partner Ledger** report displays the balance of your customers and " +"suppliers. It is available by going to :menuselection:`Accounting --> " +"Reporting --> Partner Ledger`." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:127 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:77 +#: ../../content/applications/finance/accounting/reporting.rst:5 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:77 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:129 +msgid "" +"The following financial :doc:`reports ` are available " +"and updated in real-time:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:133 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:28 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1157 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 +msgid "Financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:135 +msgid "Statement" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:135 +#: ../../content/applications/finance/accounting/customer_invoices.rst:216 +msgid "Balance sheet" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:137 +#: ../../content/applications/finance/accounting/customer_invoices.rst:206 +msgid "Profit and loss" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:139 +msgid "Cash flow statement" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:141 +#: ../../content/applications/finance/accounting.rst:180 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:77 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:38 +msgid "Tax report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:143 +msgid "ES sales list" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:145 +msgid "Audit" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:145 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1076 +msgid "General ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:147 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 +msgid "Trial balance" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:149 +msgid "Journal report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:151 +msgid "Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:153 +msgid "Check register" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:155 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:138 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:138 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:325 +msgid "Partner" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:155 +msgid "Partner ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:157 +msgid "Aged receivable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:159 +msgid "Aged payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:161 +msgid "Management" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:161 +msgid "Invoice analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:163 +msgid "Unrealized currency gains/losses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:165 +msgid "Depreciation schedule" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:167 +msgid "Disallowed expenses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:169 +msgid "Budget analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:171 +msgid "Product margins" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:173 +msgid "1099 report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:177 +msgid "" +":doc:`Create and customize reports ` with " +"Odoo's report engine." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:182 +msgid "" +"Odoo computes all accounting transactions for the specific tax period and " +"uses these totals to calculate the tax obligation." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:186 +msgid "" +"Once the tax report has been generated for a period, Odoo locks it and " +"prevents the creation of new journal entries involving VAT. Any correction " +"to customer invoices or vendor bills has to be recorded in the next period." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:191 +msgid "" +"Depending on the country's localization, an XML version of the tax report " +"can be generated to be uploaded to the VAT platform of the relevant taxation" +" authority." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:195 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:5 +msgid "Bank synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:197 +msgid "" +"The bank synchronization system directly connects with your bank institution" +" to automatically import all transactions into your database. It gives an " +"overview of your cash flow without logging into an online banking system or " +"waiting for paper bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:202 +msgid ":doc:`Bank synchronization `" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:205 +msgid "Inventory valuation" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:207 +msgid "" +"Both periodic (manual) and perpetual (automated) inventory valuations are " +"supported in Odoo. The available methods are standard price, average price, " +":abbr:`LIFO (Last-In, First-Out)` and :abbr:`FIFO (First-In, First-Out).`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:212 +msgid "" +":doc:`../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:215 +msgid "Retained earnings" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:217 +msgid "" +"Retained earnings are the portion of income retained by a business. Odoo " +"calculates current year earnings in real-time, so no year-end journal or " +"rollover is required. The profit and loss balance is automatically reported " +"on the balance sheet report." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:227 +msgid "Fiduciaries" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:229 +msgid "" +"The :guilabel:`Accounting Firms` mode can be activated by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Firms mode`. When enabled:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:232 +msgid "The document's sequence becomes editable on all documents;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:233 +msgid "" +"The :guilabel:`Total (tax incl.)` field appears to speed up and control the " +"encoding by automating line creation with the right account and tax;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:235 +msgid "" +":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when " +"encoding a transaction." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:236 +msgid "" +"A :guilabel:`Quick encoding` option is available for customer invoices and " +"vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:5 +msgid "Bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:7 +msgid "" +"You can manage as many bank or cash accounts as needed on your database. " +"Configuring them well allows you to have all your banking data up-to-date " +"and ready for :doc:`reconciliation ` with your journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:11 +msgid "" +"In Odoo Accounting, each bank account has a dedicated journal set to post " +"all entries in a dedicated account. Both the journal and the account are " +"automatically created and configured whenever you add a bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:16 +msgid "Cash journals and accounts must be configured manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:18 +msgid "" +"Bank journals are displayed by default on the :guilabel:`Accounting " +"Dashboard` in the form of cards which include action buttons." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "" +"Bank journals are displayed on the Accounting Dashboard and contain action " +"buttons" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:27 +msgid "Manage your bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:30 +msgid "Connect your bank for automatic synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:32 +msgid "" +"To connect your bank account to your database, go to " +":menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`," +" select your bank in the list, click on :guilabel:`Connect`, and follow the " +"instructions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:37 +#: ../../content/applications/finance/accounting/bank.rst:135 +#: ../../content/applications/finance/accounting/get_started.rst:188 +msgid ":doc:`bank/bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:40 +msgid "Create a bank account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:42 +msgid "" +"If your banking institution is not available in Odoo, or if you don't want " +"to connect your bank account to your database, you can configure your bank " +"account manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:45 +msgid "" +"To manually add a bank account, go to :menuselection:`Accounting --> " +"Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it`" +" (at the bottom right), and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:49 +msgid "" +"Odoo automatically detects the bank account type (e.g., IBAN) and enables " +"some features accordingly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:51 +msgid "" +"A default bank journal is available and can be used to configure your bank " +"account by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Bank`. Open it and edit the different fields to " +"match your bank account information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:56 +msgid "Create a cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:58 +msgid "" +"To create a new cash journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`, click on :guilabel:`Create` and " +"select :guilabel:`Cash` in the :guilabel:`Type` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:61 +msgid "" +"For more information on the accounting information fields, read the " +":ref:`bank_accounts/configuration` section of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:65 +msgid "" +"A default cash journal is available and can be used straight away. You can " +"review it by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:69 +msgid "Edit an existing bank or cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:71 +msgid "" +"To edit an existing bank journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals` and select the journal you want to " +"modify." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:77 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:22 +#: ../../content/applications/finance/accounting/bank/cash_register.rst:9 +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:16 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:69 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:27 +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:14 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:13 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:29 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:63 +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:11 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 +#: ../../content/applications/finance/accounting/payments/follow_up.rst:14 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:12 +#: ../../content/applications/finance/accounting/payments/online.rst:21 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:10 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:45 +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:10 +#: ../../content/applications/finance/accounting/reporting/budget.rst:11 +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 +#: ../../content/applications/finance/accounting/taxes.rst:51 +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:14 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:17 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 +#: ../../content/applications/finance/accounting/taxes/retention.rst:11 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:18 +#: ../../content/applications/finance/documents.rst:16 +#: ../../content/applications/finance/fiscal_localizations.rst:21 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:8 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:329 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:424 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:878 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:6 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:45 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:570 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:58 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:8 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:40 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:769 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:29 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:6 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:6 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:42 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:6 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:6 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 +#: ../../content/applications/finance/payment_providers.rst:276 +#: ../../content/applications/finance/payment_providers/adyen.rst:17 +#: ../../content/applications/finance/payment_providers/alipay.rst:12 +#: ../../content/applications/finance/payment_providers/authorize.rst:9 +#: ../../content/applications/finance/payment_providers/authorize.rst:60 +#: ../../content/applications/finance/payment_providers/demo.rst:9 +#: ../../content/applications/finance/payment_providers/mollie.rst:8 +#: ../../content/applications/finance/payment_providers/paypal.rst:101 +#: ../../content/applications/finance/payment_providers/sips.rst:9 +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:30 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:79 +msgid "" +"You can edit the accounting information and bank account number according to" +" your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Manually configure your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:85 +#: ../../content/applications/finance/accounting/bank.rst:109 +msgid ":doc:`get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:86 +#: ../../content/applications/finance/accounting/bank.rst:136 +msgid ":doc:`bank/transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:91 +msgid "Suspense account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:93 +msgid "" +"Bank statement transactions are posted on the :guilabel:`Suspense Account` " +"until the final reconciliation allows finding the right account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:97 +msgid "Profit and loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:99 +msgid "" +"The :guilabel:`Profit Account` is used to register a profit when the ending " +"balance of a cash register differs from what the system computes, while the " +":guilabel:`Loss Account` is used to register a loss when the ending balance " +"of a cash register differs from what the system computes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:104 +msgid "Currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:106 +msgid "You can edit the currency used to enter the statements." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:112 +msgid "Account number" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:114 +msgid "" +"If you need to **edit your bank account details**, click on the external " +"link arrow next to your :guilabel:`Account Number`. On the new page, click " +"on the external link arrow next to your :guilabel:`Bank` and update your " +"bank information accordingly. These details are used when registering " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Edit your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:123 +msgid "Bank feeds" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:125 +msgid "" +":guilabel:`Bank Feeds` defines how the bank statements are registered. Three" +" options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:127 +msgid "" +":guilabel:`Undefined yet`, which should be selected when you don’t know yet " +"if you will synchronize your bank account with your database or not." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:129 +msgid "" +":guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if " +"you want to import your bank statement using a different format." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:131 +msgid "" +":guilabel:`Automated Bank Synchronization`, which should be selected if your" +" bank is synchronized with your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:141 +msgid "Outstanding accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:143 +msgid "" +"By default, payments are registered through transitory accounts named " +"**outstanding accounts**, before being recorded in your bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:146 +msgid "" +"An **outstanding payments account** is where outgoing payments are posted " +"until they are linked with a withdrawal from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:148 +msgid "" +"An **outstanding receipts account** is where incoming payments are posted " +"until they are linked with a deposit from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:151 +msgid "" +"These accounts should be of :ref:`type ` " +":guilabel:`Current Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:154 +msgid "" +"The movement from an outstanding account to a bank account is done " +"automatically when you reconcile the bank account with a bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:158 +msgid "Default accounts configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:160 +msgid "" +"The outstanding accounts are defined by default. If necessary, you can " +"update them by going to :menuselection:`Accounting --> Configuration --> " +"Settings --> Default Accounts` and update your :guilabel:`Outstanding " +"Receipts Account` and :guilabel:`Outstanding Payments Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:165 +msgid "Bank and cash journals configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:167 +msgid "" +"You can also set specific outstanding accounts for any journal with the " +":ref:`type ` :guilabel:`Bank` or :guilabel:`Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:170 +msgid "" +"From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of" +" the journal you want to configure, and click on :guilabel:`Configuration`, " +"then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the " +"outstanding accounts column, click on the toggle button and check the " +":guilabel:`Outstanding Receipts/Payments accounts`, then update the account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Select the toggle button and click on outstanding Accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:180 +msgid "" +"If you do not specify an outstanding payments account or an outstanding " +"receipts account for a specific journal, Odoo uses the default outstanding " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:182 +msgid "" +"If your main bank account is added as an outstanding receipts account or " +"outstanding payments account, when a payment is registered, the invoice or " +"bill's status is directly set to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:7 +msgid "" +"Odoo can synchronize directly with your bank institution to get all bank " +"statements imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:10 +msgid "" +"To check if your bank is compatible with Odoo, go to `Odoo Accounting " +"Features `_, and click on " +":guilabel:`See list of supported institutions`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:14 +msgid "Odoo supports more than 25,000 institutions around the world." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:16 +msgid "To connect to the banks, Odoo uses multiple web-services:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:18 +msgid "**Plaid**: United States of America and Canada" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:19 +msgid "**Yodlee**: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:20 +msgid ":doc:`Salt Edge `: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:21 +msgid ":doc:`Ponto `: Europe" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:22 +msgid "" +":doc:`Enable Banking `: Scandinavian " +"countries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:25 +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:18 +msgid ":doc:`transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:31 +msgid "On-Premise users" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:33 +msgid "" +"To be able to use this service, you need to have a valid Odoo Enterprise " +"subscription. So make sure that your database is registered with your Odoo " +"Enterprise contract. We also use a proxy between your database and the third" +" party provider so, in case of a connection error, please check that you " +"don't have a firewall or a proxy blocking the following address:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:39 +msgid "https://production.odoofin.com/" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:42 +msgid "First synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:44 +msgid "" +"You can start synchronization either by going to the Accounting app and " +":menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank" +" Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:47 +msgid "" +"Now you can search for your bank institution. Select it and follow the steps" +" to synchronize with it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:50 +msgid "" +"If you have any issues during your first synchronization, please verify that" +" your web browser doesn't block pop-ups and that your ad-blocker is " +"disabled." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:54 +msgid "" +"When setting up the bank statement synchronization, Odoo automatically " +"starts recording the accounting transactions from the last transaction’s " +"date +1 day (if the last transaction day is 31/12/2022, the recording starts" +" on 01/01/2023). If the journal contains no transaction, Odoo retrieves " +"transactions as far back as possible. You can limit how far back Odoo " +"retrieves transactions by opening the Accounting app, going to " +":menuselection:`Accounting --> Lock Dates`, and setting a date in the " +":guilabel:`Journal Entries Lock Date` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:61 +msgid "" +"You must provide a phone number during your first synchronization to secure " +"your account. We ask for such information because we don't want your data " +"falling into the wrong hands. Therefore, if we detect suspicious activities " +"on your account, we block all requests coming from your account, and you " +"need to reactivate it using that phone number." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:66 +msgid "" +"The third-party provider may request more information in order to connect " +"with your bank institution. This information is not stored on Odoo's " +"servers." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:69 +msgid "" +"By default, transactions fetched from an online source are grouped inside " +"the same statement, and one bank statement is created per month. You can " +"change the bank statement creation periodicity in your journal settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:73 +msgid "" +"You can find all your synchronizations by going to " +":menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:77 +msgid "Synchronize manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:79 +msgid "" +"After your first synchronization, the created journals are synchronized by " +"default every 12 hours. If you wish, you can synchronize manually by " +"clicking on the :guilabel:`Synchronize Now` button on the dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:83 +msgid "" +"Or you can go to :menuselection:`Accounting Dashboard --> Configuration --> " +"Accounting: Online Synchronization`, select your institution and then click " +"on the :guilabel:`fetch transactions` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:88 +msgid "" +"Some institutions do not allow transactions to be fetched automatically. For" +" such institutions, during the automatic synchronization of the account, you" +" receive an error message asking you to disable the automatic " +"synchronization. This message can be found in the chatter of your online " +"synchronizations. In this case, make sure to perform manual " +"synchronizations." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:94 +msgid "Issues" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:97 +msgid "Synchronization in error" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:99 +msgid "" +"To report a connection error to the `Odoo support " +"`_, go to :menuselection:`Accounting Dashboard-->" +" Configuration --> Accounting: Online Synchronization`, select the " +"connection that failed, and copy the error description and the reference." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:104 +msgid "Synchronization disconnected" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:106 +msgid "" +"If your connection with the proxy is disconnected, you can reconnect with " +"the proxy using the :guilabel:`Fetch Account` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:110 +msgid "" +"If you are unable to reconnect using the :guilabel:`Reconnect` button, " +"please contact the `support `_ directly with your" +" client id or the reference of the error listed in the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:117 +msgid "Migration process for users having installed Odoo before December 2020" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:119 +msgid "" +"If you are on-premise, please first make sure that your source is up-to-date" +" with the latest version of Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:122 +msgid "" +"Users who have created a database before December 2020 need to install the " +"new module manually to use the new functionalities." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:125 +msgid "" +"To do so, go to :menuselection:`Apps --> Update Apps List`, remove the " +"default filter in the search bar and type `account_online_synchronization`. " +"You can then click on :guilabel:`Install`. Finally, make sure all your users" +" refresh their Odoo page by pressing CTRL+F5." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:131 +msgid "" +"All previous synchronizations are disconnected during the installation and " +"won't work anymore." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:132 +msgid "" +"You can find them directly in the synchronization menu " +"(:menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`). It is not possible to resynchronize these " +"connections; you have to make new ones." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:136 +msgid "" +"Do not uninstall `account_online_sync`, which is the previous module for " +"online synchronization. The new one overrides it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:138 +msgid "" +"By default, `account_online_synchronization` is installed automatically with" +" Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:141 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:95 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:81 +msgid "FAQ" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:144 +msgid "The synchronization is not working in real-time. Is that normal?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:146 +msgid "" +"The process is not intended to work in real-time as third party providers " +"synchronize your accounts at different intervals. To force the " +"synchronization and fetch the statements, go to your :guilabel:`Accounting " +"Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can " +"also synchronize and fetch transactions through :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`. Some " +"providers only allow one refresh per day, so it is possible that clicking on" +" :guilabel:`Synchronize Now` does not get your latest transactions if you " +"already performed such action earlier in the day." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:154 +msgid "" +"A transaction can be visible on your bank account but not be fetched if it " +"has the status :guilabel:`Pending`. Only transactions with the " +":guilabel:`Posted` status will be retrieved. If the transaction is not " +"**Posted** yet, you will have to wait until the status changes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:159 +msgid "Is the Online Bank Synchronization feature included in my contract?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:161 +msgid "" +"**Community Version**: No, this feature is not included in the Community " +"Version." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:162 +msgid "" +"**Online Version**: Yes, even if you benefit from the One App Free contract." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:163 +msgid "" +"**Enterprise Version**: Yes, if you have a valid enterprise contract linked " +"to your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:166 +msgid "Some banks have a status \"Beta.\" What does this mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:168 +msgid "" +"This means that banking institutions are not yet fully supported by our " +"Third Party Provider. Bugs or other problems may arise. Odoo does not " +"support technical problems that occur with banks in the Beta phase, but the " +"user may still choose to connect. Connecting with these banks contributes to" +" the development process since the Provider will have real data and feedback" +" from the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:174 +msgid "Why do my transactions only synchronize when I refresh manually?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:176 +msgid "" +"Some banks have additional security measures and require extra steps, such " +"as an SMS/email authentication code or another type of MFA. Because of this," +" the integrator cannot pull transactions until the security code is " +"provided." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:181 +msgid "Not all of my past transactions are in Odoo, why?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:183 +msgid "" +"For some institutions, transactions can only be fetched up to 3 months in " +"the past." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:186 +msgid "Why don't I see any transactions?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:188 +msgid "" +"During your first synchronization, you selected the bank accounts you " +"decided to synchronize with Odoo. If you didn't synchronize any of your " +"accounts, you can go to :menuselection:`Accounting Dashboard --> " +"Configuration --> Accounting: Online Synchronization` to click on the " +":guilabel:`Fetch Account` button on the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:193 +msgid "There may also be no new transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:195 +msgid "" +"If your bank account is properly linked to a journal and posted transactions" +" are not visible in your database, please `submit a support ticket " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:199 +msgid "How can I update my bank credentials?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:201 +msgid "" +"You can update your credentials by going to :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`,open the" +" connection you want to update your credentials and click on the " +":guilabel:`Update Credentials` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:3 +msgid "Enable Banking" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:5 +msgid "" +"**Enable Banking** is a third-party provider aggregating banking information" +" from bank accounts all in one place. It offers non-intrusive connectivity " +"to ASPSPs' official APIs across Europe without storing data." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst-1 +msgid "Enable Banking logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:13 +msgid "" +"**Odoo** synchronizes directly with banks to get access to all bank " +"transactions and automatically import them into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:17 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:20 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:18 +msgid ":doc:`../bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:18 +msgid "`Enable Banking website `_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:24 +msgid "Link bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:26 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:28 +msgid "Select your bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:29 +msgid "" +"Make sure you give your consent to share your account information with Odoo " +"by clicking :guilabel:`Continue authentication`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:0 +msgid "Enable Banking authentication page" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:36 +msgid "Finally, you are redirected to your bank's login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:3 +msgid "Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:5 +msgid "" +"**Ponto** is a service that allows companies and professionals to aggregate " +"their accounts in one place and directly see all their transactions within " +"one app. It is a third-party solution that is continuously expanding the " +"number of bank institutions that can be synchronized with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst-1 +msgid "Logo of the Ponto brand" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:13 +msgid "" +"**Odoo** can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:16 +msgid "" +"Ponto is a paid third-party provider that can handle the synchronization " +"between your bank accounts and Odoo. `Its pricing is 4€/month per " +"account/integration `_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:19 +msgid ":doc:`../transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:27 +msgid "Link your bank accounts with Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:29 +msgid "Go to `Ponto's website (https://myponto.com) `_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:30 +msgid "Create an account if you don't have one yet." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:31 +msgid "Once you are logged in, create an *organization*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Fill out the form to add an organization in Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "You might have to add your **Billing Information** first." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:39 +msgid "" +"Select your country, your bank institutions, give your consent to Ponto, and" +" follow the steps on-screen to link your bank account with your Ponto " +"account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Add bank accounts to your Ponto account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:46 +msgid "" +"Make sure to add all bank accounts you want to synchronize with your Odoo " +"database before moving on to the next steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:50 +msgid "Link your Ponto account with your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:52 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:53 +msgid "" +"Search your institution, make sure to select the right institution. By " +"selecting the institution, you can verify that the third party provider is " +"Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:55 +msgid "Click on *Connect* and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:56 +msgid "" +"At some point, you will have to authorize the accounts you want to access in" +" Odoo. Please select **all the accounts** you want to synchronize. Even the " +"ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Selection of the accounts you wish to synchronize with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:64 +msgid "Finish the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:67 +msgid "" +"You have to authorize all the accounts you want to access in Odoo, but Odoo " +"will filter the accounts based on the institution you selected in the second" +" step." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:71 +msgid "Update your synchronization credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:73 +msgid "" +"You might have to update your Ponto credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:75 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:87 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to fetch the other " +"accounts. Click on *Fetch Accounts* button to start the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:79 +msgid "" +"During the update, select **all the accounts** you want to synchronize, even" +" the ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:83 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:69 +msgid "Fetch new accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:85 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:71 +msgid "You might want to add new online accounts to your connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:91 +msgid "" +"Don't forget to keep authorization for existing accounts (for all " +"institutions that you have synchronized with Ponto)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:98 +msgid "After my synchronization, no account appears" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:100 +msgid "" +"You selected an institution from the list and did not authorize any accounts" +" from this institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:103 +msgid "I have an error about that my authorization has expired" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:105 +msgid "" +"Every **3 months** (90 days) you must re-authorize the connection between " +"your bank account and Ponto. This must be done from the `Ponto website " +"`_. If you do not do this, the synchronization will " +"stop for these accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:110 +msgid "I have some errors with my beta institution" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:112 +msgid "" +"Ponto provides institutions in *beta*, these institutions are not directly " +"supported by Odoo and we advise you to contact Ponto directly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:116 +msgid "" +"Using an institution in beta is beneficial for Ponto, it allows them to have" +" real feedback on the connection with the institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:3 +msgid "Salt Edge" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:5 +msgid "" +"**Salt Edge** is a third-party provider that aggregates banking information " +"from your bank accounts. It supports ~5000 institutions in more than 50 " +"countries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst-1 +msgid "Salt Edge Logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:14 +msgid "" +"Odoo can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:25 +msgid "Link your bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:27 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:29 +msgid "" +"Select the institution you want to synchronize. You can see if Salt Edge is " +"the third party provider of the institution by selecting it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:31 +msgid "" +"After giving your phone number, you are asked for an email address. This " +"email address is used to create your Salt Edge account. Please make sure you" +" enter a valid email address, as otherwise, you will not be able to access " +"your Salt Edge account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "" +"Email address to provide to Salt Edge for the creation of your account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:40 +msgid "" +"After entering your email address, you are redirected to Salt Edge to " +"continue the synchronization process." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge Login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:47 +msgid "Make sure you give your consent by checking the consent checkbox." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge give consent page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:53 +msgid "Complete the synchronization by following the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:57 +msgid "Update your credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:59 +msgid "" +"You might have to update your Salt Edge credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:61 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to update credentials. " +"Click on the *Update Credentials* button to start the flow and follow the " +"steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:65 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:77 +msgid "" +"Don't forget to check the consent checkbox. Otherwise, Odoo may not be able " +"to access your information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:73 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution to fetch the new accounts. Click" +" on the *Fetch Accounts* button to start the flow and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:84 +msgid "I have an error when I try to delete my synchronization within Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:86 +msgid "" +"Odoo can't permanently delete the connection you have created with the " +"banking institution. However, it can revoke the consent you gave so that " +"Odoo won't be able to access your account anymore. The error you are seeing " +"is probably a message telling you that the consent was revoked, but the " +"record could not be deleted as it still exists within Salt edge. If you want" +" to remove the connection completely, please connect to your `Salt Edge " +"account `_ and manually delete your " +"synchronization. Once this is done, you can go back to Odoo to delete the " +"record." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:95 +msgid "I have an error saying that I have already synchronized this account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:97 +msgid "" +"You have probably already synchronized your bank account with Salt Edge, " +"please check on your `dashboard `_ that " +"you don't already have a connection with the same credentials." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:101 +msgid "" +"In case you already have a synchronization with the same credentials present" +" on your Salt Edge dashboard and this synchronization has not been created " +"with Odoo, please delete it and create it from your Odoo database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:105 +msgid "" +"In case you already have a connection with the same credentials present on " +"your Salt Edge dashboard and this synchronization was created with Odoo, you" +" will normally be able to find it by going to :menuselection:`Accounting -->" +" Configuration --> Online Synchronization`. Please make sure to do an " +"*Update Credentials* to reactivate the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:3 +msgid "Cash register" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:5 +msgid "" +"The cash register is a journal to register receivings and payments " +"transactions. It calculates the total money in and out, computing the total " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:14 +msgid "" +"Configure the Cash journal in :menuselection:`Accounting --> Configuration " +"--> Journals`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:17 +msgid "" +"In the tab Journal Entries, the Default Debit and Credit Account can be " +"configured as well as the currency of the journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:21 +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:34 +msgid "Usage" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:24 +msgid "How to register cash payments?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:26 +msgid "" +"To register a cash payment specific to another customer, you should follow " +"these steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:29 +msgid "" +"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register " +"Transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:32 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:34 +msgid "" +"Register the transactions, specifying the customers linked to the " +"transaction" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:37 +msgid "Put money in" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:39 +msgid "" +"Put money in is used to placed your cash manually before starting your " +"transactions. From the Register Transactions window, go to " +":menuselection:`More --> Put money in`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:47 +msgid "Take money out" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:49 +msgid "" +"Take money out is used to collect/get yor your cash manually after ending " +"all your transactions. From the Register Transaction windows, go to " +":menuselection:`More --> Take money out`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:56 +msgid "" +"The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:3 +msgid "Manage a bank account in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:5 +msgid "" +"In Odoo, every transaction is recorded in the default currency of the " +"company, and reports are all based on that default currency. When you have a" +" bank account in a foreign currency, for every transaction, Odoo stores two " +"values:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:9 +msgid "The debit/credit in the currency of the *company*;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:10 +msgid "The debit/credit in the currency of the *bank account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:12 +msgid "" +"Currency rates are updated automatically using the web services of a banking" +" institution. By default, Odoo uses the European Central Bank's web services" +" but other options are available." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:19 +msgid "Activate multi-currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:21 +msgid "" +"To work with multiple currencies, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and tick :guilabel:`Multi-" +"Currencies`. Under :guilabel:`Post Exchange difference entries in:`, provide" +" a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss " +"Account`, and then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:27 +msgid "Configure currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:29 +msgid "" +"Once Odoo is configured to support multiple currencies, they are all created" +" by default, but not necessarily active. To activate the new currencies, " +"click on :guilabel:`Activate Other Currencies` under the :guilabel:`Multi-" +"Currencies` setting or go to :menuselection:`Accounting --> Configuration " +"--> Accounting: Currencies`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:34 +msgid "" +"When the currencies are activated, you can choose to **automate** the " +"currency rate update, or leave it on **manual**. To configure the rate " +"update, go back to :menuselection:`Accounting --> Configuration --> Settings" +" --> Currencies`, check :guilabel:`Automatic Currency Rates`, set " +":guilabel:`Interval` to your desired frequency, and then click on " +":guilabel:`Save`. You also have the option to choose the :guilabel:`Service`" +" you wish to obtain currency rates from." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:40 +msgid "" +"Click on the Update now button (:guilabel:`🗘`) besides the :guilabel:`Next " +"Run` field to update the currency rates manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:44 +msgid "Create a new bank account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:46 +msgid "" +"In the accounting application, go to :menuselection:`Accounting --> " +"Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal" +" Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal " +"Entries` tab, enter a **short code**, a **currency**, and then finally click" +" on the :guilabel:`Bank Account` field to create a new account. In the pop-" +"up window of the account creation, enter a name, a code (ex.: 550007), set " +"its type to `Bank and Cash`, set a currency type, and save. When you are " +"back on the **journal**, click on the :guilabel:`Account Number` field, and " +"in the pop-up window, fill out the :guilabel:`Account Number`, " +":guilabel:`Bank` of your account, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Example of a created bank journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:59 +msgid "" +"Upon creation of the journal, Odoo automatically links the bank account to " +"the journal. It can be found under :menuselection:`Accounting --> " +"Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:63 +msgid "Vendor bill in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:65 +msgid "" +"To pay a bill in a foreign currency, simply select the currency next to the " +":guilabel:`Journal` field and register the payment. Odoo automatically " +"creates and posts the foreign **exchange gain or loss** as a new journal " +"entry." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "How to set a bill currency." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:74 +msgid "" +"Note that you can pay a foreign bill with another currency. In that case, " +"Odoo automatically converts between the two currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:78 +msgid "Unrealized Currency Gains/Losses Report" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:80 +msgid "" +"This report gives an overview of all unrealized amounts in a foreign " +"currency on your balance sheet, and allows you to adjust an entry or " +"manually set an exchange rate. To access this report, go to " +":menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`." +" From here, you have access to all open entries in your **balance sheet**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "View of the Unrealized Gains/Losses journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:89 +msgid "" +"If you wish to use a different currency rate than the one set in " +":menuselection:`Accounting --> Configuration --> Settings --> Currencies`, " +"click the :guilabel:`Exchange Rates` button and change the rate of the " +"foreign currencies in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Menu to manually change exchange rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:97 +msgid "" +"When manually changing **exchange rates**, a yellow banner appears allowing " +"you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset" +" to Odoo's Rate`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Banner to reset back to Odoo's rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:104 +msgid "" +"In order to update your **balance sheet** with the amount of the " +":guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` " +"button. In the pop-up window, select a :guilabel:`Journal`, " +":guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and " +"process the **unrealized gains and losses**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:109 +msgid "" +"You can set the date of the report in the :guilabel:`Date` field. Odoo " +"automatically reverses the booking entry to the date set in " +":guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:112 +msgid "" +"Once posted, the :guilabel:`adjustment` column should indicate `0.00`, " +"meaning all **unrealized gains/losses** have been adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Unrealized Currency Gains/Losses report once adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:3 +#: ../../content/applications/finance/accounting/payments/batch.rst:52 +msgid "Bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:5 +msgid "" +"**Bank reconciliation** is the process of matching your :doc:`bank " +"transactions ` with your business records, such as " +":doc:`customer invoices <../customer_invoices>`, :doc:`vendor bills " +"<../vendor_bills>`, and :doc:`payments <../payments>`. Not only is this " +"compulsory for most businesses, but it also offers several benefits, such as" +" reduced risk of errors in financial reports, detection of fraudulent " +"activities, and improved cash flow management." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:11 +msgid "" +"Thanks to the bank :doc:`reconciliation models `, " +"Odoo pre-selects the matching entries automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:15 +msgid "" +"`Odoo Tutorials: Bank reconciliation " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:17 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:128 +msgid ":doc:`bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:21 +msgid "Bank reconciliation view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:23 +msgid "" +"To access a bank journal's **reconciliation view**, go to your " +":guilabel:`Accounting Dashboard` and either:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:26 +msgid "" +"click the journal name (e.g., :guilabel:`Bank`) to display all transactions," +" including those previously reconciled or" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:28 +msgid "" +"click the :guilabel:`Reconcile items` button to display all transactions " +"Odoo pre-selected for reconciliation. You can remove the :guilabel:`Not " +"Matched` filter from the search bar to include previously reconciled " +"transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst-1 +msgid "Reaching the bank reconciliation tool from your accounting dashboard" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:35 +msgid "" +"The bank reconciliation view is structured into three distinct sections: " +"transactions, counterpart entries, and resulting entry." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst-1 +msgid "The user interface of the reconciliation view of a bank journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:43 +#: ../../content/applications/finance/accounting/bank/transactions.rst:3 +msgid "Transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:42 +msgid "" +"The transactions section on the left shows all bank transactions, with the " +"newest displayed first. Click a transaction to select it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:50 +msgid "Counterpart entries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:46 +msgid "" +"The counterpart entries section on the bottom right displays the options to " +"match the selected bank transaction. Multiple tabs are available, including " +":ref:`reconciliation/existing-entries`, :ref:`reconciliation/batch-" +"payments`, :ref:`reconciliation/manual-operations`, and :guilabel:`Discuss`," +" which contains the chatter for the selected bank transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:56 +msgid "Resulting entry" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:53 +msgid "" +"The resulting entry section on the top right displays the selected bank " +"transaction matched with the counterpart entries and includes any remaining " +"debits or credits. In this section, you can validate the reconciliation or " +"mark it as :guilabel:`To Check`. Any :ref:`reconciliation model buttons " +"` are also available in the resulting entry " +"section." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:59 +msgid "Reconcile transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:61 +msgid "" +"Transactions can be matched automatically with the use of " +":doc:`reconciliation models `, or they can be matched" +" with :ref:`existing entries `, :ref:`batch" +" payments `, :ref:`manual operations " +"`, and :ref:`reconciliation model buttons " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:67 +msgid "Select a transaction among unmatched bank transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:68 +msgid "" +"Define the counterpart. There are several options for defining a " +"counterpart, including :ref:`matching existing entries " +"`, :ref:`manual operations " +"`, :ref:`batch payments " +"`, and :ref:`reconciliation model buttons " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:72 +msgid "" +"If the resulting entry is not fully balanced, balance it by adding another " +"existing counterpart entry or writing it off with a :ref:`manual operation " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:74 +msgid "" +"Click the :guilabel:`Validate` button to confirm the reconciliation and move" +" to the next transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:78 +msgid "" +"If you are not sure how to reconcile a particular transaction and would like" +" to deal with it later, use the :guilabel:`To Check` button instead. All " +"transactions marked as :guilabel:`To Check` can be displayed using the " +":guilabel:`To Check` filter." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:83 +msgid "" +"Bank transactions are posted on the **journal's suspense account** until " +"reconciliation. At this point, reconciliation modifies the transaction " +"journal entry by replacing the bank suspense account with the corresponding " +"receivable, payable, or outstanding account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:90 +msgid "Match existing entries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:92 +msgid "" +"This tab contains matching entries Odoo automatically pre-selects according " +"to the reconciliation models. The entry order is based on " +":ref:`reconciliation models `, with " +"suggested entries appearing first." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:97 +msgid "" +"The search bar within the :guilabel:`Match Existing Entries` tab allows you " +"to search for specific journal items." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:103 +msgid "Batch payments" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:105 +msgid "" +"`Batch payments `_ allow you to group different " +"payments to ease reconciliation. Use the :guilabel:`Batch Payments` tab to " +"find batch payments for customers and vendors. Similarly to the " +":guilabel:`Match Existing Entries` tab, the :guilabel:`Batch Payments` tab " +"has a search bar that allows you to search for specific batch payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:113 +msgid "Manual operations" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:115 +msgid "" +"If there is not an existing entry to match the selected transaction, you may" +" instead wish to reconcile the transaction manually by choosing the correct " +"account and amount. Then, complete any of the relevant optional fields." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:120 +msgid "" +"You can use the :guilabel:`fully paid` option to reconcile a payment, even " +"in cases where only a partial payment is received. A new line appears in the" +" resulting entry section to reflect the open balance registered on the " +"Account Receivable by default. You can choose another account by clicking on" +" the new line in the resulting entry section and selecting the " +":guilabel:`Account` to record the open balance." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:127 +msgid "" +"Lines are silently reconciled unless a write-off entry is required, which " +"launches a reconciliation wizard." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:0 +msgid "Click on fully paid to manually set an invoice as entirely paid." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:135 +msgid "Reconciliation model buttons" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:137 +msgid "" +"Use a :ref:`reconciliation model button ` for " +"manual operations that are frequently used. These custom buttons allow you " +"to quickly reconcile bank transactions manually and can also be used in " +"combination with existing entries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:3 +msgid "Reconciliation Models" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:5 +msgid "" +"Once the bank statements are correctly imported, it is essential to " +"*reconcile* the records properly and ensure all *Journal Entries* are " +"balanced and in agreement. To ease and speed up the reconciliation process, " +"you can configure **Reconciliation Models**, which are particularly useful " +"with recurrent entries such as bank fees." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:10 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:67 +msgid "Todo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:10 +msgid "" +"Add a link to the Reconciliation process in the paragraph above, once the " +"doc will have been updated." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:14 +msgid "" +"Reconciliation Models are also useful to handle *Cash Discounts*. Please " +"refer to :doc:`this documentation <../customer_invoices/cash_discounts>` for" +" more information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:21 +msgid "Types of Reconciliation Models" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:23 +msgid "There are three types of Reconciliation Models:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:25 +msgid ":ref:`Write-off Button `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:26 +msgid "" +":ref:`Suggestion of counterpart values `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:27 +msgid ":ref:`Match existing invoices/bills `" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:32 +msgid "Manually create a write-off on clicked button" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:34 +msgid "" +"When you are reconciling an entry with an *Open Balance*, you can use the " +"buttons available under the *Manual Operations* tab to pre-fill all the " +"values automatically, before validating the reconciliation. Each button is a" +" different Reconciliation Model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model with a write-off button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:45 +msgid "Suggest counterpart values" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:47 +msgid "" +"This type of Reconciliation Model suggests immediately counterpart values " +"that only need to be validated. This automation is based on a set of rules " +"defined in the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model that suggests counterpart values in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:57 +msgid "Match existing invoices/bills" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:59 +msgid "" +"This type of Reconciliation Model automatically selects the right Customer " +"Invoice or Vendor Bill that matches the payment. All that is left to do is " +"to validate the entry. This automation is based on a set of rules defined in" +" the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model that matches existing invoices and bills automatically\n" +"in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:71 +msgid "" +"To manage or create new **Reconciliation Models**, go to " +":menuselection:`Accounting --> Reconciliation --> Reconciliation Models`. " +"Alternatively, you can also open this menu from the Accounting Overview, by " +"going to your Bank Journal card, clicking on the three little dots, and then" +" on *Reconciliation Models*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Open the Reconciliation Model menu from the overview dashboard in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:81 +msgid "" +"The first entry, named *Invoices Matching Rule*, is the one responsible for " +"the current matching of invoices and bills. Therefore, it is advised to " +"leave it at the top of the list and not to delete it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:85 +msgid "" +"Open the model you want to modify, or click on *Create* to create a new one," +" then fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:88 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:43 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 +msgid "Type" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:90 +msgid "" +"See :ref:`above ` for an explanation about the " +"different types of Reconciliation Models." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:94 +msgid "" +"If the *Documents* application is installed on your database, an additional " +"**Activity type** field appears when *To check* is ticked. Selecting the " +"value *Reconciliation request* implies that, whenever you use this model, a " +"*Request Document* window pops up to request a document from a user." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:100 +msgid "Conditions on Bank Statement Line" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:102 +msgid "" +"Define here all the conditions that are required for a Reconciliation Model " +"to be applied." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:105 +msgid "" +"If a record matches with several Reconciliation Models, the first one in the" +" *sequence* of models will be applied. The sequence is simply the order of " +"the models in the *list view*. They can be rearranged by dragging-and-" +"dropping the handle next to the name." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Conditions for the Reconciliation Model to be applied in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:114 +msgid "Counterpart Values" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:116 +msgid "" +"This section comprises the values that are applied by the Reconciliation " +"Model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:118 +msgid "" +"If the value to reconcile needs to be written-off in two separate accounts, " +"click on *Add a second line*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "Counterparts values of a Reconciliation Model in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:127 +msgid ":doc:`reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:129 +msgid ":doc:`../customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:5 +msgid "" +"Importing transactions from your bank statements allows keeping track of " +"bank account transactions and reconciling them with the ones recorded in " +"your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:8 +msgid "" +":doc:`Bank synchronization ` automates the process. " +"However, if you do not want to use it or if your bank is not yet supported, " +"other options exist:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:11 +msgid "" +":ref:`Import bank transactions ` delivered by your " +"bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:12 +msgid ":ref:`Register bank transactions ` manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:15 +msgid "" +":ref:`Grouping transactions by statement ` is " +"optional." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:20 +msgid "Import transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:22 +msgid "Odoo supports multiple file formats to import transactions:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:24 +msgid "SEPA recommended Cash Management format (CAMT.053);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:25 +msgid "Comma-separated values (.CSV);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:26 +msgid "Open Financial Exchange (.OFX);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:27 +msgid "Quicken Interchange Format (.QIF);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:28 +msgid "Belgium: Coded Statement of Account (.CODA)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:30 +msgid "" +"To import a file, go to the :guilabel:`Accounting Dashboard`, and in the " +":guilabel:`Bank` journal, click on :guilabel:`Import Transactions`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst-1 +msgid "Import bank transactions from the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:36 +msgid "Next, select the file and upload it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:38 +msgid "" +"After setting the necessary formatting options and mapping the file columns " +"with their related Odoo fields, you can run a :guilabel:`Test` and " +":guilabel:`Import` your bank transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:42 +msgid ":doc:`/applications/general/export_import_data`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:47 +msgid "Register bank transactions manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:49 +msgid "" +"You can also record your bank transactions manually. To do so, go to " +":guilabel:`Accounting Dashboard`, click on the :guilabel:`Bank` journal, and" +" then on :guilabel:`New`. Make sure to fill out the :guilabel:`Partner` and " +":guilabel:`Label` fields to ease the reconciliation process." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:56 +msgid "Statements" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:58 +msgid "" +"A **bank statement** is a document provided by a bank or financial " +"institution that lists the transactions that have occurred in a particular " +"bank account over a specified period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:61 +msgid "" +"In Odoo Accounting, it is optional to group transactions by their related " +"statement, but depending on your business flow, you may want to record them " +"for control purposes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:65 +msgid "" +"If you want to compare the ending balances of your bank statements with the " +"ending balances of your financial records, *don't forget to create an " +"opening transaction* to record the bank account balance as of the date you " +"begin synchronizing or importing transactions. This is necessary to ensure " +"the accuracy of your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:70 +msgid "" +"To access a list of statements, go to your :guilabel:`Accounting Dashboard`," +" click on the vertical ellipsis (:guilabel:`⋮`) button next to the bank or " +"cash journal you want to check, then on :guilabel:`Statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:75 +msgid "Statement creation from the kanban view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:77 +msgid "" +"Open the bank reconciliation view by clicking on the name of the bank " +"journal, and identify the transaction corresponding to the last transaction " +"of your bank statement. Click on the :guilabel:`STATEMENT` button when " +"hovering on the upper separator line." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst-1 +msgid "" +"A \"STATEMENT\" button is visible when hovering on the line separating two " +"transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:84 +msgid "" +"Fill out the statement's details and save. The newly created statement " +"includes the previous transactions following the last statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:88 +msgid "Statement creation from the list view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:90 +msgid "" +"Open the list of transactions by clicking on the name of the bank journal " +"and switching to the list view. Select all the transactions corresponding to" +" the bank statement, and, in the :guilabel:`Statement` column, select an " +"existing statement or create a new one by typing its reference, clicking on " +":guilabel:`Create and edit...`, filling out the statement's details, and " +"saving." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:5 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:352 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:346 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 +msgid "Customer invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:8 +msgid "From Customer Invoice to Payments Collection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:10 +msgid "" +"Odoo supports multiple invoicing and payment workflows, so you can choose " +"and use the ones that match your business needs. Whether you want to accept " +"a single payment for a single invoice, or process a payment spanning " +"multiple invoices and taking discounts for early payments, you can do so " +"efficiently and accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:17 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:19 +msgid "" +"If we pick up at the end of a typical 'order to cash' scenario, after the " +"goods have been shipped, you will: issue an invoice; receive payment; " +"deposit that payment at the bank; make sure the Customer Invoice is closed; " +"follow up if Customers are late; and finally present your Income on the " +"Profit and Loss report and show the decrease in Assets on the Balance Sheet " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:26 +msgid "" +"Invoicing in most countries occurs when a contractual obligation is met. If " +"you ship a box to a customer, you have met the terms of the contract and can" +" bill them. If your supplier sends you a shipment, they have met the terms " +"of that contract and can bill you. Therefore, the terms of the contract is " +"fulfilled when the box moves to or from the truck. At this point, Odoo " +"supports the creation of what is called a Draft Invoice by Warehouse staff." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:284 +msgid "Invoice creation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:37 +msgid "" +"Draft invoices can be manually generated from other documents such as Sales " +"Orders, Purchase Orders,etc. Although you can create a draft invoice " +"directly if you would like." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:41 +msgid "" +"An invoice must be provided to the customer with the necessary information " +"in order for them to pay for the goods and services ordered and delivered. " +"It must also include other information needed to pay the invoice in a timely" +" and precise manner." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:47 +msgid "Draft invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:49 +msgid "" +"The system generates invoice which are initially set to the Draft state. " +"While these invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:52 +msgid "" +"remain unvalidated, they have no accounting impact within the system. There " +"is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:55 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:57 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:58 +msgid "Product: iMac" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:59 +msgid "Quantity: 1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:60 +msgid "Unit Price: 100" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:61 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:67 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:69 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:70 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:71 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:74 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:76 +msgid "" +"An invoice will usually include the quantity and the price of goods and/or " +"services, the date, any parties involved, the unique invoice number, and any" +" tax information." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:80 +msgid "" +"\"Validate\" the invoice when you are ready to approve it. The invoice then " +"moves from the Draft state to the Open state." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:83 +msgid "" +"When you have validated an invoice, Odoo gives it a unique number from a " +"defined, and modifiable, sequence." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:88 +msgid "" +"Accounting entries corresponding to this invoice are automatically generated" +" when you validate the invoice. You can see the details by clicking on the " +"entry in the Journal Entry field in the \"Other Info\" tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:96 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:98 +msgid "" +"After validating the customer invoice, you can directly send it to the " +"customer via the 'Send by email' functionality." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:103 +msgid "" +"A typical journal entry generated from a validated invoice will look like as" +" follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:56 +msgid "**Account**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:40 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Debit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Credit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:58 +msgid "Accounts Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "115" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/taxes.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:167 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:180 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:366 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:376 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:73 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:246 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:121 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:116 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:51 +msgid "Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "15" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:142 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:146 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:150 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:154 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:158 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:162 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "Sales" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:112 +msgid "100" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:117 +msgid "Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:119 +msgid "" +"In Odoo, an invoice is considered to be paid when the associated accounting " +"entry has been reconciled with the payment entries. If there has not been a " +"reconciliation, the invoice will remain in the Open state until you have " +"entered the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:124 +msgid "" +"A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:67 +msgid "Bank" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:138 +msgid "" +"You can manually enter your bank statements in Odoo, or you can import them " +"in from a csv file or from several other predefined formats according to " +"your accounting localisation." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:142 +msgid "" +"Create a bank statement from the accounting dashboard with the related " +"journal and enter an amount of $100 ." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:148 +msgid "Reconcile" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:150 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:154 +msgid "" +"You can now go through every transaction and reconcile them or you can mass " +"reconcile with instructions at the bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:156 +msgid "" +"After reconciling the items in the sheet, the related invoice will now " +"display \"You have outstanding payments for this customer. You can reconcile" +" them to pay this invoice. \"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:164 +msgid "" +"Apply the payment. Below, you can see that the payment has been added to the" +" invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:170 +msgid "Payment Followup" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:172 +msgid "" +"There's a growing trend of customers paying bills later and later. " +"Therefore, collectors must make every effort to collect money and collect it" +" faster." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:176 +msgid "" +"Odoo will help you define your follow-up strategy. To remind customers to " +"pay their outstanding invoices, you can define different actions depending " +"on how severely overdue the customer is. These actions are bundled into " +"follow-up levels that are triggered when the due date of an invoice has " +"passed a certain number of days. If there are other overdue invoices for the" +" same customer, the actions of the most overdue invoice will be executed." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:184 +msgid "" +"By going to the customer record and diving into the \"Overdue Payments\" you" +" will see the follow-up message and all overdue invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:194 +msgid "Customer aging report:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:196 +msgid "" +"The customer aging report will be an additional key tool for the collector " +"to understand the customer credit issues, and to prioritize their work." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:200 +msgid "" +"Use the aging report to determine which customers are overdue and begin your" +" collection efforts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:208 +msgid "" +"The Profit and Loss statement displays your revenue and expense details. " +"Ultimately, this gives you a clear image of your Net Profit and Loss. It is " +"sometimes referred to as the \"Income Statement\" or \"Statement of Revenues" +" and Expenses.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:218 +msgid "" +"The balance sheet summarizes your company's liabilities, assets and equity " +"at a specific moment in time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:225 +msgid "" +"For example, if you manage your inventory using the perpetual accounting " +"method, you should expect a decrease in account \"Current Assets\" once the " +"material has been shipped to the customer." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:3 +msgid "Cash discounts and tax reduction" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:5 +msgid "" +"**Cash discounts** are reductions in the amount a customer must pay for " +"goods or services offered as an incentive for paying their invoice promptly." +" These discounts are typically a percentage of the total invoice amount and " +"are applied if the customer pays within a specified time. Cash discounts can" +" help a company maintain a steady cash flow." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:11 +msgid "" +"You issue a €100 invoice on the 1st of January. The full payment is due " +"within 30 days, and you also offer a 2% discount if your customer pays you " +"within seven days." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:14 +msgid "" +"The customer can pay €98 up to the 8th of January. After that date, they " +"would have to pay €100 by the 31st of January." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:17 +msgid "" +"A :ref:`tax reduction ` can also be applied " +"depending on the country or region." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:21 +msgid ":doc:`payment_terms`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:67 +msgid ":doc:`../payments`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:29 +msgid "" +"To grant cash discounts to customers, you must first verify the :ref:`gain " +"and loss accounts `. Then, configure " +":ref:`payment terms ` and add a cash discount " +"by checking the :guilabel:`Early Discount` checkbox and filling in the " +"discount percentage, discount days, and :ref:`tax reduction ` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:38 +msgid "Cash discount gain/loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:40 +msgid "" +"With a cash discount, the amount you earn depends on whether the customer " +"benefits from the cash discount or not. This inevitably leads to gains and " +"losses, which are recorded on default accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:43 +msgid "" +"To modify these accounts, go to :menuselection:`Accounting --> Configuration" +" --> Settings`, and, in the :guilabel:`Default Accounts` section, select the" +" accounts you want to use for the :guilabel:`Cash Discount Gain account` and" +" :guilabel:`Cash Discount Loss account`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:50 +msgid "Payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:52 +msgid "" +"Cash discounts are defined on :doc:`payment terms `. " +"Configure them to your liking by going to :menuselection:`Accounting --> " +"Configuration --> Payment Terms`, and make sure to fill out the discount " +"percentage, discount days, and :ref:`tax reduction ` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"Configuration of payment terms named \"2/7 Net 30\". The field \"Description on Invoices\"\n" +"reads: \"Payment terms: 30 Days, 2% Early Payment Discount under 7 days\"." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:64 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:66 +msgid "" +"Depending on the country or region, the base amount used to compute the tax " +"can vary, which can lead to a **tax reduction**. Since tax reductions are " +"set on individual payment terms, each term can use a specific tax reduction." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:70 +msgid "" +"To configure how the tax reduction is applied, go to a payment term with the" +" :guilabel:`Early Discount` checkbox enabled, and select one of the three " +"following options:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:75 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:94 +msgid "Always (upon invoice)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:74 +msgid "" +"The tax is always reduced. The base amount used to compute the tax is the " +"discounted amount, whether the customer benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:80 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:109 +msgid "On early payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:78 +msgid "" +"The tax is reduced only if the customer pays early. The base amount used to " +"compute the tax is the same as the sale: if the customer benefits from the " +"reduction, then the tax is reduced. This means that, depending on the " +"customer, the tax amount can vary after the invoice is issued." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:84 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:124 +msgid "Never" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:83 +msgid "" +"The tax is never reduced. The base amount used to compute the tax is the " +"full amount, whether the customer benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:88 +msgid "" +"You issue a €100 invoice (tax-excluded) on the 1st of January, with a 21% " +"tax rate. The full payment is due within 30 days, and you also offer a 2% " +"discount if your customer pays you within seven days." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:99 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:114 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:129 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +msgid "Due date" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:100 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:115 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:130 +msgid "Total amount due" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:101 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:116 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:131 +msgid "Computation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:102 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:117 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:132 +msgid "8th of January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:103 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:118 +msgid "€118.58" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:104 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:119 +msgid "€98 + (21% of €98)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:120 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:135 +msgid "31st of January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:106 +msgid "€120.58" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:107 +msgid "€100 + (21% of €98)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:121 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:136 +msgid "€121.00" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:122 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:137 +msgid "€100 + (21% of €100)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:133 +msgid "€119.00" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:134 +msgid "€98 + (21% of €100)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:140 +msgid "" +":ref:`Tax grids `, which are used for the tax report," +" are correctly computed according to the :ref:`type of tax reduction ` you configured." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:143 +msgid "" +"The **type of cash discount tax reduction** may be correctly pre-configured," +" depending on your :ref:`fiscal localization package " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:149 +msgid "Apply a cash discount to a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:151 +msgid "" +"On a customer invoice, apply a cash discount by selecting the :ref:`payment " +"terms you created `. Odoo automatically " +"computes the correct amounts, tax amounts, due dates, and accounting " +"records." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:155 +msgid "" +"Under the :guilabel:`Journal Items` tab, you can display the discount " +"details by clicking on the \"toggle\" button and adding the " +":guilabel:`Discount Date` and :guilabel:`Discount Amount` columns." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"An invoice of €100.00 with \"2/7 Net 30\" selected as payment terms. The \"Journal Items\" tab\n" +"is open, and the \"Discount Date\" and \"Discount Amount\" columns are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:162 +msgid "" +"The discount amount and due date are also displayed on the generated invoice" +" report sent to the customer if the :guilabel:`Show installment dates` " +"option is checked on the payment terms." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"An invoice of €100.00 with the following text added to the terms and conditions: \"30\n" +"Days, 2% Early Payment Discount under 7 days. 118.58 € due if paid before 01/08/2023.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:170 +msgid "Payment reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:172 +msgid "" +"When you record a :doc:`payment <../payments>` or :doc:`reconcile your bank " +"transactions <../bank/reconciliation>`, Odoo takes the customer payment's " +"date into account to determine if the customer can benefit from the cash " +"discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:177 +msgid "" +"If your customer pays the discount amount *after* the discount date, you can" +" always decide to mark the invoice as fully paid with a write-off or as " +"partially paid." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and enable " +"*Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:22 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`, and " +"click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:25 +msgid "" +"Define here your *Rounding Precision*, *Rounding Strategy*, and *Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:28 +msgid "Odoo supports two **rounding strategies**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:30 +msgid "" +"**Add a rounding line**: a *rounding* line is added on the invoice. You have" +" to define which account records the cash roundings." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:33 +msgid "**Modify tax amount**: the rounding is applied in the taxes section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:36 +msgid "Apply roundings" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:38 +msgid "" +"When editing a draft invoice, open the *Other Info* tab, go to the " +"*Accounting Information* section, and select the appropriate *Cash Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:3 +msgid "Credit notes and refunds" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:5 +msgid "" +"A **credit/debit note**, or **credit/debit memo**, is a document issued to a" +" customer that notifies them that they have been *credited/debited* a " +"certain amount." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:8 +msgid "Several use cases can lead to a credit note, such as:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:10 +msgid "a mistake in the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:11 +msgid "a return of the goods, or a rejection of the services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:12 +msgid "the goods delivered are damaged" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:14 +msgid "" +"Debit notes are less common but are most frequently used to track debts owed" +" by customers or to vendors because of modifications to confirmed customer " +"invoices or vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:18 +msgid "" +"Issuing a credit/debit note is the only legal way to cancel, refund, or " +"modify a validated invoice. Do not forget to **register the payment** " +"afterward if you need to send money back to your customer and/or validate " +"the :doc:`return ` if a " +"storable product is returned." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:27 +msgid "Issue a credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:29 +msgid "" +"You can create a credit note from scratch by going to " +":menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking " +"on :guilabel:`Create`. Filling out a credit note form works the same way as " +"an invoice form." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:33 +msgid "" +"However, most of the time, credit notes are generated directly from the " +"related invoices. To do so, go to :menuselection:`Accounting --> Customers " +"--> Invoices`, open the related **customer invoice**, and click on " +":guilabel:`Credit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:37 +msgid "You can choose between three options:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:39 +msgid ":guilabel:`Partial Refund`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:40 +msgid ":guilabel:`Full Refund`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:41 +msgid ":guilabel:`Full refund and new draft invoice`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:44 +msgid "" +"A credit note sequence starts with `R` and is followed by the number of the " +"related document (e.g., RINV/2019/0004 is related to the invoice " +"INV/2019/0004)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:48 +msgid "Partial refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:50 +msgid "" +"When selecting the :guilabel:`Partial Refund` option, Odoo creates a draft " +"credit note already prefilled with all the necessary information from the " +"original invoice. This is the option to choose if you wish to do a partial " +"refund or if you want to modify any detail of the credit note." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:55 +msgid "This is the only option for invoices marked as *in payment* or *paid*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:58 +msgid "Full refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:60 +msgid "" +"When selecting the :guilabel:`Full Refund` option, Odoo creates a credit " +"note, automatically validates it, and reconciles it with the related " +"invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst-1 +msgid "Full refund credit note." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:66 +msgid "" +"This is the option to choose for a full refund or to **cancel** a " +"*validated* invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:69 +msgid "Full refund and new draft invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:71 +msgid "" +"When selecting the :guilabel:`Full refund and new draft invoice` option, " +"Odoo creates a credit note, automatically validates it, reconciles it with " +"the related invoice, and opens a new draft invoice prefilled with the same " +"details from the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:75 +msgid "This is the option to **modify** the content of a *validated* invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:80 +msgid "Issue a debit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:82 +msgid "" +"You can create a debit note from scratch by going to " +":menuselection:`Accounting --> Customers --> Invoices` or by clicking on the" +" related invoice you wish to issue a debit note for. On the invoice form " +"view, click :guilabel:`Cog icon (⚙) --> Debit Note`, fill in the " +"information, and click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:88 +msgid "Record a vendor refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:90 +msgid "**Vendor refunds** are recorded the same way as credit notes:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:92 +msgid "" +"You can either create a credit note from scratch by going to " +":menuselection:`Accounting --> Vendors --> Refund`, and by clicking on " +":guilabel:`Create`; or by opening the related **vendor bill**, and clicking " +"on :guilabel:`Credit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:97 +msgid "Record a debit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:99 +msgid "" +"**Debit notes** from vendors are recorded in a similar way to how they are " +"issued to customers:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:101 +msgid "" +"Go to :menuselection:`Accounting --> Vendors --> Bills`, open the related " +"bill you wish to record a debit note for, and click :guilabel:`Cog icon (⚙) " +"--> Debit Note`. Fill in the information, and click :guilabel:`Create Debit " +"Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:106 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 +#: ../../content/applications/finance/accounting/payments/checks.rst:84 +msgid "Journal entries" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:108 +msgid "" +"Issuing a credit/debit note from an invoice/bill creates a **reverse entry**" +" that zeroes out the journal items generated by the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:113 +msgid "The journal invoice of an entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:0 +msgid "Invoice journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:118 +msgid "" +"And here is the credit note’s journal entry generated to reverse the " +"original invoice above:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:0 +msgid "Credit note journal entry reverses the invoice journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:3 +msgid "Delivery and invoice addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:5 +msgid "" +"Companies often have multiple locations, and it is common that a customer " +"invoice should be sent to one address and the delivery should be sent to " +"another. Odoo's **Customer Addresses** feature is designed to handle this " +"scenario by making it easy to specify which address to use for each case." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:10 +msgid ":doc:`overview`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:15 +msgid "" +"To specify a sales order's invoice and delivery addresses, first go to " +":menuselection:`Accounting --> Configuration --> Settings`. In the " +":guilabel:`Customer Invoices` section, enable :guilabel:`Customer Addresses`" +" and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:19 +msgid "" +"On quotations and sales orders, there are now fields for :guilabel:`Invoice " +"Address` and :guilabel:`Delivery Address`. If the customer has an invoice or" +" delivery address listed on their contact record, the corresponding field " +"will use that address by default, but any contact's address can be used " +"instead." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:25 +msgid "Invoice and deliver to different addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:27 +msgid "" +"Delivery orders and their delivery slip reports use the address set as the " +":guilabel:`Delivery Address` on the sales order. By default, invoice reports" +" show both the shipping address and the invoice address to assure the " +"customer that the delivery is going to the correct location." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:31 +msgid "" +"Emails also go to different addresses. The quotation and sales order are " +"sent to the main contact's email, as usual, but the invoice is sent to the " +"email of the address set as the :guilabel:`Invoice Address` on the sales " +"order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 +msgid "" +"Reports, such as the delivery slip and invoice report, can be " +":doc:`customized using Studio " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:38 +msgid "" +"If :doc:`Send by Post ` is checked when you click :guilabel:`Send" +" & Print`, the invoice will be mailed to the invoice address." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:5 +msgid "" +"**Deferred revenues**, or **unearned revenues**, are invoices addressed to " +"customers for goods yet to be delivered or services yet to be rendered." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:8 +msgid "" +"The company cannot report them on the current **profit and loss statement**," +" or *income statement*, since the goods and services will be effectively " +"delivered/rendered in the future." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:11 +msgid "" +"These future revenues must be deferred on the company's balance sheet among " +"the current liabilities until they can be **recognized**, at once or over a " +"defined period, on the profit and loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:15 +msgid "" +"For example, let's say a business sells a software license of $1200 for 1 " +"year. They immediately invoice it to the customer but can't consider it " +"earned yet, as the future months of licensing have not yet been delivered. " +"Therefore, they post this new revenue in a deferred revenue account and " +"recognize it on a monthly basis. Each month, for the next 12 months, $100 " +"will be recognized as revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:21 +msgid "" +"Odoo Accounting handles deferred revenues by spreading them in multiple " +"entries that are posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:25 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:25 +msgid "" +"The server checks once a day if an entry must be posted. It might then take " +"up to 24 hours before you see a change from :guilabel:`Draft` to " +":guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:31 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:31 +msgid "" +"Make sure the default settings are correctly configured for your business. " +"To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"The following options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:34 +msgid "Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:35 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:35 +msgid "The deferral entries are posted in this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:36 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:36 +msgid "Deferred Expense Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:37 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:37 +msgid "" +"Expenses are deferred on this Current Asset account until they are " +"recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:38 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:38 +msgid "Deferred Revenue Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:39 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:39 +msgid "" +"Revenues are deferred on this Current Liability account until they are " +"recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:43 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:43 +msgid "Generate Entries" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:41 +msgid "" +"By default, Odoo :ref:`automatically generates " +"` the deferral entries " +"when you post a customer invoice. However, you can also choose to " +":ref:`generate them manually `" +" by selecting the :guilabel:`Manually & Grouped` option instead." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:48 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:48 +msgid "Amount Computation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:46 +msgid "" +"Suppose an invoice of $1200 must be deferred over 12 months. The " +":guilabel:`Equal per month` computation accounts for $100 each month, while " +"the :guilabel:`Based on days` computation accounts for different amounts " +"depending on the number of days in each month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:53 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:53 +msgid "Generate deferral entries on validation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:56 +msgid "" +"Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are " +"visible in the :guilabel:`Invoice Lines` tab. In most cases, the " +":guilabel:`Start Date` should be in the same month as the :guilabel:`Invoice" +" Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 +msgid "" +"For each line of the invoice that should be deferred, specify the start and " +"end dates of the deferral period." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:63 +msgid "" +"If the :guilabel:`Generate Entries` field in the **Settings** is set to " +":guilabel:`On invoice/bill validation`, Odoo automatically generates the " +"deferral entries when the invoice is validated. Click the " +":guilabel:`Deferred Entries` smart button to see them." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:67 +msgid "" +"One entry, dated on the same day as the invoice, moves the invoice amounts " +"from the income account to the deferred account. The other entries are " +"deferral entries which, month after month, move the invoice amounts from the" +" deferred account to the income account to recognize the revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:72 +msgid "" +"You can defer a January invoice of $1200 over 12 months by specifying a " +"start date of 01/01/2023 and an end date of 12/31/2023. At the end of " +"August, $800 is recognized as an income, whereas $400 remains on the " +"deferred account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:79 +msgid "" +"The deferred revenue report computes an overview of the necessary deferral " +"entries for each account. To access it, go to :menuselection:`Accounting -->" +" Reporting --> Deferred Revenue`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:82 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:82 +msgid "" +"To view the journal items of each account, click on the account name and " +"then :guilabel:`Journal Items`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Deferred revenue report" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:89 +msgid "" +"Only invoices whose accounting date is before the end of the period of the " +"report are taken into account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:95 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:95 +msgid "Generate grouped deferral entries manually" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:97 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 +msgid "" +"If you have a lot of deferred revenues and wish to reduce the number of " +"journal entries created, you can generate deferral entries manually. To do " +"so, set the :guilabel:`Generate Entries` field in the **Settings** to " +":guilabel:`Manually & Grouped`. Odoo then aggregates the deferred amounts in" +" a single entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:102 +msgid "" +"At the end of each month, go to :menuselection:`Accounting --> Reporting -->" +" Deferred Revenue` and click the :guilabel:`Generate Entries` button. This " +"generates two deferral entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:105 +msgid "" +"One dated at the end of the month which aggregates, for each account, all " +"the deferred amounts of that month. This means that a part of the deferred " +"revenue is recognized at the end of that period." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:108 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:108 +msgid "" +"The reversal of this created entry, dated on the following day (i.e., the " +"first day of the next month) to cancel the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:112 +msgid "There are two invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:114 +msgid "Invoice A: $1200 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 +msgid "Invoice B: $600 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "In January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:118 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:119 +msgid "" +"At the end of January, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:121 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:122 +msgid "Entry 1 dated on the 31st January:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:123 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:140 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:156 +msgid "" +"Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both" +" invoices)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:124 +msgid "" +"Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of invoice A " +"and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +msgid "" +"Line 3: Deferred account 1800 - 150 = **1650** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:128 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:129 +msgid "Entry 2 dated on the 1st February, the reversal of the previous entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:130 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:131 +msgid "Line 1: Expense account **1800**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:131 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:132 +msgid "Line 2: Deferred account **-150**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "Line 3: Expense account **-1650**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "In February" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:135 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:136 +msgid "" +"At the end of February, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:138 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:139 +msgid "Entry 1 dated on the 28th February:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:141 +msgid "" +"Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of invoice A " +"and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:143 +msgid "" +"Line 3: Deferred account 1800 - 300 = **1500** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "Entry 2 dated on the 1st March, the reversal of the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "From March to October" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "The same computation is done for each month until October." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "In November" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:151 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:152 +msgid "" +"At the end of November, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:154 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:155 +msgid "Entry 1 dated on the 30th November:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 +msgid "" +"Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of invoice " +"A and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:159 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:159 +msgid "" +"Line 3: Deferred account 1800 - 1650 = **150** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "Entry 2 dated on the 1st December, the reversal of the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:166 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:166 +msgid "In December" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:165 +msgid "" +"There is no need to generate entries in December. Indeed, if we do the " +"computation for December, we have an amount of 0 to be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "In total" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:169 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:169 +msgid "If we aggregate everything, we would have:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:171 +msgid "invoice A and invoice B" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 +msgid "" +"two entries (one for the deferral and one for the reversal) for each month " +"from January to November" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +msgid "" +"Therefore, at the end of December, invoices A and B are fully recognized as " +"income only once in spite of all the created entries thanks to the reversal " +"mechanism." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:3 +msgid "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:5 +msgid "" +"EDI, or electronic data interchange, is the inter-company communication of " +"business documents, such as purchase orders and invoices, in a standard " +"format. Sending documents according to an EDI standard ensures that the " +"machine receiving the message can interpret the information correctly. " +"Various EDI file formats exist and are available depending on your company's" +" country." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:10 +msgid "" +"EDI feature enables automating the administration between companies and " +"might also be required by some governments for fiscal control or to " +"facilitate the administration." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:13 +msgid "" +"Electronic invoicing of your documents such as customer invoices, credit " +"notes or vendor bills is one of the application of EDI." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:16 +msgid "Odoo supports, among others, the following formats." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:21 +msgid "Format Name" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:22 +msgid "Applicability" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:23 +msgid "Factur-X (CII)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:24 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:26 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:28 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:50 +msgid "All customers" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:25 +msgid "Peppol BIS Billing 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:27 +msgid "XRechnung (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:29 +msgid "Fattura PA (IT)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:30 +msgid "Italian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:31 +msgid "CFDI (4.0)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:32 +msgid "Mexican companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:33 +msgid "Peru UBL 2.1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:34 +msgid "Peruvian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:35 +msgid "SII IVA Llevanza de libros registro (ES)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:36 +msgid "Spanish companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:37 +msgid "UBL 2.1 (Columbia)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:38 +msgid "Colombian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:39 +msgid "Egyptian Tax Authority" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:40 +msgid "Egyptian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:41 +msgid "E-Invoice (IN)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:42 +msgid "Indian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:43 +msgid "NLCIUS (Netherlands)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:44 +msgid "Dutch companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:45 +msgid "EHF 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:46 +msgid "Norwegian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:47 +msgid "SG BIS Billing 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:48 +msgid "Singaporean companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:49 +msgid "A-NZ BIS Billing 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:53 +msgid "" +"The **Factur-X (CII)** format enables validation checks on the invoice and " +"generates PDF/A-3 compliant files." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:55 +msgid "" +"Every PDF generated by Odoo includes an integrated **Factur-X** XML file." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 +msgid ":doc:`../../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:65 +msgid "" +"By default, the format available in the :ref:`send window " +"` depends on your customer's country." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 +msgid "" +"You can define a specific e-invoicing format for each customer. To do so, go" +" to :menuselection:`Accounting --> Customers --> Customers`, open the " +"customer form, go to the :guilabel:`Accounting` tab and select the " +"appropriate format." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Select an EDI format for a specific customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:76 +msgid "National electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:78 +msgid "" +"Depending on your company's country (e.g., :doc:`Italy " +"<../../fiscal_localizations/italy>`, :doc:`Spain " +"<../../fiscal_localizations/spain>`, :doc:`Mexico " +"<../../fiscal_localizations/mexico>`, etc.), you may be required to issue " +"e-invoicing documents in a specific format for all your invoices. In this " +"case, you can define a default e-invoicing format for your sales journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:84 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open your sales journal, go to the :guilabel:`Advanced Settings` tab, and " +"enable the formats you need for this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:90 +msgid "E-invoices generation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:92 +msgid "" +"From a confirmed invoice, click :guilabel:`Send & Print` to open the send " +"window. Check the e-invoicing option to generate and attach the e-invoice " +"file." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "" +"The Peppol option is checked and an e-invoicing XML file is attached to the " +"email." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:99 +msgid "Peppol" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:101 +msgid "" +"The `Peppol `_ network ensures the exchange of " +"documents and information between enterprises and governmental authorities. " +"It is primarily used for electronic invoicing, and its access points " +"(connectors to the Peppol network) allow enterprises to exchange electronic " +"documents." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:106 +msgid "" +"Odoo is an **access point** and an :abbr:`SMP (Service Metadata Publisher)`," +" enabling electronic invoicing transactions without the need to send " +"invoices and bills by email or post." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:109 +msgid "" +"If not done yet, :ref:`install ` the :guilabel:`Peppol` " +"module (`account_peppol`)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:112 +msgid "Peppol registration is **free** and available in Odoo Community" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:113 +msgid "" +"You can send **Customer Invoices** and **Credit Notes** and receive **Vendor" +" Bills** and **Refunds** via Peppol." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:115 +msgid "" +"You can send in one of the following supported document formats: **BIS " +"Billing 3.0, XRechnung CIUS, NLCIUS**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "" +"The following **countries** are eligible for **Peppol registration in " +"Odoo**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "" +"Andorra, Albania, Austria, Bosnia and Herzegovina, Belgium, Bulgaria, " +"Switzerland, Cyprus, Czech Republic, Germany, Denmark, Estonia, Spain, " +"Finland, France, United Kingdom, Greece, Croatia, Hungary, Ireland, Iceland," +" Italy, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Montenegro, " +"North Macedonia, Malta, Netherlands, Norway, Poland, Portugal, Romania, " +"Serbia, Sweden, Slovenia, Slovakia, San Marino, Turkey, Holy See (Vatican " +"City State)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:125 +msgid "Registration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:127 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. If you do " +"not have the Peppol module installed, first tick the :guilabel:`Enable " +"PEPPOL` checkbox and then **manually save**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Peppol module installation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:134 +msgid "Fill in the following information:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:136 +msgid "" +":guilabel:`Peppol EAS`. This is the Peppol Electronic Address Scheme and " +"usually depends on your company's country. Odoo often prefills this with the" +" most commonly used EAS code in your country. For example, the preferred EAS" +" code for most companies in Belgium is 0208." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:139 +msgid "" +":guilabel:`Peppol Endpoint`. This is usually a Company Registry number or a " +"VAT number." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:140 +msgid "" +":guilabel:`Phone Number`, including the country code (e.g., `+32` in " +"Belgium)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:141 +msgid ":guilabel:`Primary contact email`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:144 +msgid "" +"`Peppol EAS - European Commision `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:145 +msgid "" +"`Peppol Endpoint - OpenPeppol eDEC Code Lists " +"`_ (open the \"Participant " +"Identifier Schemes\" as HTML page)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:148 +msgid "" +"If you are migrating from another access point, insert the " +":guilabel:`Migration key` from the previous provider." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Configuration for peppol" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:154 +msgid "" +"Finally, click :guilabel:`Validate registration`. If you want to explore or " +"demo Peppol, you can choose to register in :guilabel:`Demo` mode. Otherwise," +" select :guilabel:`Live`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol demo mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:161 +msgid "" +"When testing Peppol, the system parameter `account_peppol.edi.mode` can be " +"changed to `test`. Then, a radio button appears with the option to register " +"on the test server." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode parameter" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:170 +msgid "" +"Now, you can request a verification code to be sent to you by clicking " +":guilabel:`Verify phone number`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "phone validation request verification" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:176 +msgid "" +"A text message containing a code is sent to the phone number provided to " +"finalize the verification process." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "phone validation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:182 +msgid "" +"Once you enter the code and click :guilabel:`Confirm`, you can see that your" +" registration is pending activation. From this point onwards, the default " +"journal for receiving Vendor Bills can be set." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "pending application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:188 +msgid "It should be automatically activated within a day." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:191 +msgid "" +"It is also possible to manually trigger the cron that checks the " +"registration status by going to :menuselection:`Settings --> Technical --> " +"Scheduled Actions --> PEPPOL\\: update participant status`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:195 +msgid "" +"Your application status should be updated soon after you are registered on " +"the Peppol network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "active application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:200 +msgid "" +"All invoices and vendor bills can now be sent directly using the Peppol " +"network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:203 +msgid "Contact verification" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:205 +msgid "" +"Before sending an invoice to a contact using the Peppol network, it is " +"necessary to verify that they are also registered as a Peppol participant." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:208 +msgid "" +"To do so, go to :menuselection:`Accounting --> Customers --> Customers` and " +"open the customer's form. Then go to :menuselection:`Accounting tab --> " +"Electronic Invoicing`, select the correct format, and make sure their " +":guilabel:`Peppol EAS code` and the :guilabel:`Endpoint` are filled in. " +"Then, click :guilabel:`Verify`. If the contact exists on the network, their " +"Peppol endpoint validity is set to Valid." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "verify contact registration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:218 +msgid "" +"While Odoo prefills both the EAS code and the Endpoint number based on the " +"information available for a contact, it is better to confirm these details " +"directly with the contact." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:221 +msgid "" +"It is possible to verify the Peppol participant status of several customers " +"at once. To do so, go to :menuselection:`Accounting --> Customers --> " +"Customers` and switch to the list view. Select the customers you want to " +"verify and then click :menuselection:`Actions --> Verify Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:226 +msgid "Send invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:228 +msgid "" +"Once ready to send an invoice via the Peppol network, simply click " +":guilabel:`Send & Print` on the invoice form. To queue multiple invoices, " +"select them in the list view and click :menuselection:`Actions --> Send & " +"Print`; they will be sent in a batch later on. Both :guilabel:`BIS Billing " +"3.0` and :guilabel:`Send via PEPPOL` checkboxes need to be ticked." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Send peppol invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:236 +msgid "" +"Posted invoices that can be sent via Peppol are marked as :guilabel:`Peppol " +"Ready`. To display them, use the :guilabel:`Peppol Ready` filter or access " +"the Accounting dashboard and click :guilabel:`Peppol ready invoices` on the " +"corresponding sales journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Filter Peppol ready invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:243 +msgid "" +"Once the invoices are sent via Peppol, the status is changed to " +":guilabel:`Processing`. The status is changed to `Done` after they have been" +" successfully delivered to the contact's Access Point." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Peppol message status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:251 +msgid "" +"By default, the Peppol status column is hidden on the Invoices list view. " +"You can choose to have it displayed by selecting it from the optional " +"columns, accessible from the top right corner of the Invoices list view." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:255 +msgid "" +"A cron runs regularly to check the status of these invoices. It is possible " +"to check the status before the cron runs by clicking :guilabel:`Fetch Peppol" +" invoice status` in the corresponding sales journal on the Accounting " +"dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Fetch invoice Peppol status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:263 +msgid "Receive vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:265 +msgid "" +"Once a day, a cron checks whether any new documents have been sent to you " +"via the Peppol network. These documents are imported, and the corresponding " +"vendor bills are created automatically as drafts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "peppol receive bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:272 +msgid "" +"If you want to retrieve incoming Peppol documents before the cron runs, you " +"can do so from the Accounting dashboard on the main Peppol purchase journal " +"that you set up in the settings. Just click :guilabel:`Fetch from Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Fetch bills from Peppol" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 +msgid "EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:5 +msgid "" +"European Payments Council quick response codes, or **EPC QR codes**, are " +"two-dimensional barcodes that customers can scan with their **mobile banking" +" applications** to initiate a **SEPA credit transfer (SCT)** and pay their " +"invoices instantly." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:9 +msgid "" +"In addition to bringing ease of use and speed, it greatly reduces typing " +"errors that would potentially make for payment issues." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:13 +msgid "" +"This feature is only available for companies in several European countries " +"such as Austria, Belgium, Finland, Germany, and the Netherlands." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:17 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:126 +msgid ":doc:`../bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:18 +msgid "" +"`Odoo Academy: QR Code on Invoices for European Customers " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:23 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and " +"activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer " +"Payments` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:27 +msgid "Configure your bank account's journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:29 +msgid "" +"Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo" +" with your IBAN and BIC." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:31 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open your bank journal, then fill out the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Bank Account Number` column." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "Bank account number column in the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:39 +msgid "Issue invoices with EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:41 +msgid "" +"EPC QR codes are added automatically to your invoices. Customers whose bank " +"supports making payments via EPC QR codes will be able to scan the code and " +"pay the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:44 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a " +"new invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:46 +msgid "" +"Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically " +"fills out the :guilabel:`Recipient Bank` field with your IBAN." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:50 +msgid "" +"In the :guilabel:`Other Info` tab, the account indicated in the " +":guilabel:`Recipient Bank` field is used to receive your customer's payment." +" Odoo automatically populates this field with your IBAN by default and uses " +"it to generate the EPC QR code." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:54 +msgid "" +"When the invoice is printed or previewed, the QR code is included at the " +"bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "QR code on a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:60 +msgid "" +"If you want to issue an invoice without an EPC QR code, remove the IBAN " +"indicated in the :guilabel:`Recipient Bank` field, under the " +":guilabel:`Other Info` tab of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:3 +msgid "Incoterms" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:5 +msgid "" +":abbr:`Incoterms (International Commercial Terms)` are standardized trade " +"terms used in international transactions to define the rights and " +"responsibilities of buyers and sellers. They establish the obligations " +"related to the delivery of goods, the transfer of risks, and the " +"distribution of costs between the parties involved. Incoterms specify " +"important details, such as the point at which the risk and costs transfer " +"from the seller to the buyer, the responsibility for transportation, " +"insurance, customs clearance, and other relevant aspects of the transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:13 +msgid "By default, all 11 Incoterms are available in Odoo:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:15 +msgid "**EXW**: Ex works" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:16 +msgid "**FCA**: Free carrier" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:17 +msgid "**FAS**: Free alongside ship" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:18 +msgid "**FOB**: Free on board" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:19 +msgid "**CFR**: Cost and freight" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:20 +msgid "**CIF**: Cost, insurance and freight" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:21 +msgid "**CPT**: Carriage paid to" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:22 +msgid "**CIP**: Carriage and insurance paid to" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:23 +msgid "**DPU**: Delivered at place unloaded" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:24 +msgid "**DAP**: Delivered at place" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:25 +msgid "**DDP**: Delivered duty paid" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:28 +msgid ":doc:`../reporting/intrastat`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:29 +msgid ":doc:`../customer_invoices`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:30 +msgid ":doc:`../vendor_bills`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:35 +msgid "Define an Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:37 +msgid "" +"To define an Incoterm manually, create an invoice or bill, click the " +":guilabel:`Other Info` tab, and select the :guilabel:`Incoterm`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:41 +msgid "Incoterm location" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:43 +msgid "" +"A location relevant to the chosen Incoterm can be added to the invoice or " +"bill under :guilabel:`Other Info` in the :guilabel:`Incoterm Location` " +"field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:47 +msgid "" +"If the chosen Incoterm code is `CIF` (Cost, Insurance, Freight), the " +"associated location might be the destination port where the goods will be " +"delivered." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:53 +msgid "Default Incoterm configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:55 +msgid "" +"You can set a default Incoterm rule to **automatically** populate the " +"Incoterm field on all newly created invoices and bills. Under " +":menuselection:`Accounting/Invoicing --> Configuration --> Settings`, scroll" +" down to the :guilabel:`Customer Invoices` section, and select an Incoterm " +"in the :guilabel:`Default Incoterm` field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:3 +msgid "Invoicing processes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:21 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:25 +msgid "" +"Invoice manually: use a button on the sale order to trigger the draft " +"invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:28 +msgid "" +"Invoice before delivery: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:33 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:37 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice the " +"whole order, invoice a percentage (advance), invoice some lines, invoice a " +"fixed advance." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:45 +msgid ":doc:`/applications/sales/sales/invoicing/proforma`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:48 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:50 +msgid "" +"Retailers and eCommerce usually invoice based on delivery orders, instead of" +" sales order. This approach is suitable for businesses where the quantities " +"you deliver may differs from the ordered quantities: foods (invoice based on" +" actual Kg)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:55 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:61 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:64 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:66 +msgid "" +"An eCommerce order will also trigger the creation of the order when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:72 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:75 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:77 +msgid "" +"If you use contracts, you can trigger invoice based on time and material " +"spent, expenses or fixed lines of services/products. Every month, the " +"salesperson will trigger invoice based on activities on the contract." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:81 +msgid "Activities can be:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:83 +msgid "" +"fixed products/services, coming from a sale order linked to this contract" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:84 +msgid "materials purchased (that you will re-invoice)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:85 +msgid "time and material based on timesheets or purchases (subcontracting)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:86 +msgid "" +"expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:88 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:94 +msgid ":doc:`/applications/sales/sales/invoicing/time_materials`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:95 +msgid ":doc:`/applications/sales/sales/invoicing/expense`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:96 +msgid ":doc:`/applications/sales/sales/invoicing/milestone`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:101 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:106 +msgid ":doc:`/applications/sales/subscriptions`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:109 +msgid "Others" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:112 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:114 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:119 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:122 +msgid "if you need to create a refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:124 +msgid "If you need to give a discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:126 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:128 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:131 +msgid "Specific modules" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:133 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:135 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:137 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:140 +msgid "Resequencing of the invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:142 +msgid "" +"It remains possible to resequence the invoices but with some restrictions:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:144 +msgid "The feature does not work when entries are previous to a lock date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:145 +msgid "" +"The feature does not work if the sequence is inconsistent with the month of " +"the entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:146 +msgid "It does not work if the sequence leads to a duplicate." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:147 +msgid "The order of the invoice remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:148 +msgid "" +"It is useful for people who use a numbering from another software and who " +"want to continue the current year without starting over from the beginning." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:152 +msgid "Invoice digitization with optical character recognition (OCR)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:154 +msgid "" +"**Invoice digitization** is the process of automatically encoding " +"traditional paper invoices into invoices forms in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:157 +msgid "" +"Odoo uses OCR and artificial intelligence technologies to recognize the " +"content of the documents. Vendor bills and customer invoices forms are " +"automatically created and populated based on scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:162 +msgid "" +":doc:`/applications/finance/accounting/vendor_bills/invoice_digitization`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:3 +msgid "Payment terms and installment plans" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:5 +msgid "" +"**Payment terms** specify all the conditions of a sale's payment to help " +"ensure customers pay their invoices correctly and on time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:8 +msgid "" +"Payment terms are generally defined on documents such as sales orders, " +"customer invoices, and vendor bills. Payment terms cover:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:11 +msgid "The due date(s)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:12 +msgid "Early payment discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:13 +msgid "Any other conditions on the payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:15 +msgid "" +"An **installment plan** allows the customers to pay an invoice in parts, " +"with the amounts and payment dates defined beforehand by the seller." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:19 +msgid "Immediate Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:20 +msgid "The full payment is due on the day of the invoice's issuance." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:21 +msgid "15 Days (or Net 15)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:22 +msgid "The full payment is due 15 days after the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:23 +msgid "21 MFI" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:24 +msgid "" +"The full payment is due by the 21st of the month following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:26 +msgid "30% Advance End of Following Month" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:26 +msgid "" +"30% is due on the day of the invoice's issuance. The remaining balance is " +"due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:29 +msgid "2% 10, Net 30 EOM" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:29 +msgid "" +"A 2% :doc:`cash discount ` if the payment is received within" +" ten days. Otherwise, the full payment is due at the end of the month " +"following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:33 +msgid "" +"Payment terms are not to be confused with :doc:`down payment invoices " +"`. If, for a specific " +"order, you issue multiple invoices to your customer, that is neither a " +"payment term nor an installment plan but an invoicing policy." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:37 +msgid "" +"This page is about the *payment terms* feature, not :doc:`terms & conditions" +" `, which can be used to declare contractual obligations " +"regarding content use, return policies, and other policies surrounding the " +"sale of goods and services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:42 +msgid "" +"`Odoo Tutorials: payment terms `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:43 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:48 +msgid "To create new payment terms, follow these steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:50 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and " +"click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:52 +msgid "" +"Enter a name in the :guilabel:`Payment Terms` field. This field is the name " +"displayed both internally and on sales orders." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:54 +msgid "" +"Tick the :guilabel:`Early Discount` checkbox and fill out the discount " +"percentage, discount days, and :ref:`tax reduction ` fields to add a :doc:`cash discount `, if " +"desired." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:57 +msgid "" +"In the :guilabel:`Due Terms` section, add a set of rules (terms) to define " +"what needs to be paid and by which due date(s). Defining terms automatically" +" calculates the payments' due date(s). This is particularly helpful for " +"managing **installment plans** (:dfn:`payment terms with multiple terms`)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:62 +msgid "" +"To add a term, click on :guilabel:`Add a line`, define the discount's value " +"and type in the :guilabel:`Due` fields, then fill out the :guilabel:`After` " +"fields to determine the due date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:64 +msgid "" +"Enter the text to be displayed on the document (sales order, invoice, etc.) " +"in the gray textbox in the :guilabel:`Preview` column." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:66 +msgid "" +"Tick the :guilabel:`Show installment dates` checkbox to display a breakdown " +"of each payment and its due date on the invoice report, if desired." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:70 +msgid "" +"To instead specify a number of days *before the end of the month*, use a " +"negative value in the :guilabel:`After` field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:73 +msgid "" +"To test that your payment terms are configured correctly, enter an invoice " +"date on the :guilabel:`Example` line to generate the payments that would be " +"due and their due dates using these payment terms." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:78 +msgid "Terms are computed in the order of their due dates." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:81 +msgid "" +"In the following example, 30% is due on the day of issuance, and the " +"remaining 70% is due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"Example of Payment Terms. The first line is the 30% due immediately. The second line is\n" +"the remaining 70% due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:89 +msgid "Using payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:91 +msgid "" +"Payment terms can be defined using the :guilabel:`Payment Terms` field on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:93 +msgid "" +"**Contacts:** To automatically set default payment terms on a contact's new " +"sales orders, invoices, and bills. This can be modified in the contact form," +" under the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:96 +msgid "" +"**Quotations/Sales Orders:** To set specific payment terms automatically on " +"all invoices generated from a quotation or sales order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:99 +msgid "" +"Payment terms can be defined using the :guilabel:`Due Date` field, with the " +":guilabel:`Terms` drop-down list on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:102 +msgid "**Customer invoices:** To set specific payment terms on an invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:103 +msgid "**Vendor bills:** To set specific payment terms on a bill." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:106 +msgid "" +"Setting payment terms on a vendor bill is mostly useful for managing vendor " +"terms with multiple installments or cash discounts. Otherwise, manually " +"setting the **due date** is enough. If payment terms are already defined, " +"empty the field to select a date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 +msgid "" +"Invoices with specific payment terms generate different *journal entries*, " +"with one *journal item* for every computed *due date*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:116 +msgid "" +"This makes for easier :doc:`follow-ups " +"` and " +":doc:`reconciliation `" +" since Odoo takes each due date into account, rather than just the balance " +"due date. It also helps to get an accurate :ref:`aged receivable report " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 +msgid "" +"The amount debited to the account receivable is split into two journal items with\n" +"distinct due dates" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:126 +msgid "" +"In this example, an invoice of $1000 has been issued with the following " +"payment terms: *30% is due on the day of issuance, and the remaining 70% is " +"due at the end of the following month.*" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "Account Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +msgid "February 21" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +msgid "300" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +msgid "March 31" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +msgid "700" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:136 +msgid "Product Sales" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:136 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "1000" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:139 +msgid "" +"The $1000 debited to the account receivable is split into two distinct " +"journal items. Both of them have their own due date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:5 +msgid "Snailmail" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:7 +msgid "" +"Sending direct mail can be an effective strategy for grabbing people's " +"attention, especially when their email inboxes are overflowing. With Odoo, " +"you have the ability to send invoices and follow-up reports through postal " +"mail worldwide, all from within your database." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:14 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" +" invoices` section to activate :guilabel:`Snailmail`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:17 +msgid "" +"To make it a by-default feature, select :guilabel:`Send by Post` in the " +":guilabel:`Default Sending Options` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst-1 +msgid "Under settings enable the snailmail feature in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:25 +msgid "Send invoices by post" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:27 +msgid "" +"Open your invoice, click on :guilabel:`Send & Print` and select " +":guilabel:`Send by Post`. Make sure your customer’s address is set " +"correctly, including the country, before sending the letter." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:31 +msgid "" +"Your document must respect the following rules to pass the validation before" +" being sent:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:33 +msgid "" +"Margins must be **5 mm** on all sides. As Odoo forces the outer margins by " +"filling them with white before sending the snailmail, it can results in the " +"user's custom being cut off if it protrudes into the margins. To check the " +"margins, activate the :ref:`developer mode `, go to " +":menuselection:`General Settings --> Technical --> Reporting section: Paper " +"Format`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:38 +msgid "" +"A square of **15mm by 15mm** on the bottom left corner has to stay clear." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:39 +msgid "" +"The postage area has to stay clear (click :download:`here " +"` to get more info about the area)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:41 +msgid "" +"Pingen (Odoo Snailmail service provider) scans the area to process the " +"address, so if something gets written outside the area, it is not counted as" +" part of the address." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:45 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:84 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:47 +msgid "" +"Snailmail is an :doc:`/applications/general/in_app_purchase` service that " +"requires prepaid stamps (=credits) to work. Sending one document consumes " +"one stamp." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:50 +msgid "" +"To buy stamps, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Customer invoices: Snailmail`, click on :guilabel:`Buy " +"credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`," +" and click on :guilabel:`View my Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:94 +msgid "" +"If you are on Odoo Online and have the Enterprise version, you benefit from " +"free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:57 +msgid "" +"Click `here `_ to know about our " +"*Privacy Policy*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:3 +msgid "Default terms and conditions (T&C)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:5 +msgid "" +"Specifying terms and conditions is essential to establish important " +"contractual points, such as return and refunds, warranty, and after-sale " +"services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:8 +msgid "" +"You can add default terms and conditions at the bottom of all customer " +"invoices, sales orders, and quotations, either as text or a link to a web " +"page." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:12 +msgid "" +"`Odoo Tutorial: Terms & Conditions `_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:17 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Customer Invoices`, enable :guilabel:`Default Terms & " +"Conditions`. By default, the :guilabel:`Add a Note` option is selected, and " +"the terms and conditions are displayed at the bottom of the document. Enter " +"the terms and conditions in the text box below." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst-1 +msgid "Example of terms and conditions as a note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:26 +msgid "" +"You can also add a PDF version of your terms and conditions as an attachment" +" when sending the document via email. Edit the email templates if you want " +"to include them by default." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:29 +msgid "" +"Alternatively, to display the terms and conditions on a web page, select the" +" :guilabel:`Add a link to a Web Page` option and click :guilabel:`Save`. " +"Click :guilabel:`Update Terms`, edit the content, and click " +":guilabel:`Save`. The link to that page is then added as a note in your " +"document." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:34 +msgid "" +"You can edit the layout and content of the page using the :doc:`Website " +"` app. If the Website app is activated, the " +":guilabel:`Edit in Website Builder` option then replaces :guilabel:`Update " +"Terms`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst-1 +msgid "Example of terms and conditions as a web page" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:7 +msgid "" +"When you first open your Odoo Accounting app, the *Accounting Overview* page" +" welcomes you with a step-by-step onboarding banner, a wizard that helps you" +" get started. This onboarding banner is displayed until you choose to close " +"it." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:11 +msgid "" +"The settings visible in the onboarding banner can still be modified later by" +" going to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:15 +msgid "" +"Odoo Accounting automatically installs the appropriate **Fiscal Localization" +" Package** for your company, according to the country selected at the " +"creation of the database. This way, the right accounts, reports, and taxes " +"are ready-to-go. :ref:`Click here ` for more " +"information about Fiscal Localization Packages." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:21 +msgid "Accounting onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:23 +msgid "" +"The step-by-step Accounting onboarding banner is composed of four steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:28 +msgid ":ref:`accounting-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:29 +msgid ":ref:`accounting-setup-bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:30 +msgid ":ref:`accounting-setup-periods`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:31 +msgid ":ref:`accounting-setup-chart`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:36 +#: ../../content/applications/finance/accounting/get_started.rst:137 +msgid "Company Data" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:38 +msgid "" +"This menu allows you to add your company’s details such as the name, " +"address, logo, website, phone number, email address, and Tax ID, or VAT " +"number. These details are then displayed on your documents, such as on " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:46 +msgid "" +"You can also change these settings by going to :menuselection:`Settings --> " +"General Settings --> Settings --> Companies` and clicking on **Update " +"Info**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:52 +msgid "Bank Account" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:54 +msgid "" +"Connect your bank account to your database and have your bank statements " +"synced automatically. To do so, find your bank in the list, click on " +"*Connect*, and follow the instructions on-screen." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:58 +msgid "" +":doc:`Click here ` for more information about " +"this feature." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:60 +msgid "" +"If your Bank Institution can’t be synchronized automatically, or if you " +"prefer not to sync it with your database, you may also configure your bank " +"account manually by clicking on *Create it*, and filling out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:64 +msgid "**Name**: the bank account's name, as displayed on Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:65 +msgid "**Account Number**: your bank account number (IBAN in Europe)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:66 +msgid "" +"**Bank**: click on *Create and Edit* to configure the bank's details. Add " +"the bank institution's name and its Identifier Code (BIC or SWIFT)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:68 +msgid "" +"**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By" +" default, Odoo creates a new Journal with this Short Code." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:70 +msgid "" +"**Journal**: This field is displayed if you have an existing Bank Journal " +"that is not linked yet to a bank account. If so, then select the *Journal* " +"you want to use to record the financial transactions linked to this bank " +"account or create a new one by clicking on *Create and Edit*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:75 +msgid "" +"You can add as many bank accounts as needed with this tool by going to " +":menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank " +"Account*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:77 +msgid ":doc:`Click here ` for more information about Bank Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:83 +msgid "Accounting Periods" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:85 +msgid "" +"Define here your **Fiscal Years**’ opening and closing dates, which are used" +" to generate reports automatically, and your **Tax Return Periodicity**, " +"along with a reminder to never miss a tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:89 +msgid "" +"By default, the opening date is set on the 1st of January and the closing " +"date on the 31st of December, as this is the most common use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:93 +msgid "" +"You can also change these settings by going to :menuselection:`Accounting " +"--> Configuration --> Settings --> Fiscal Periods` and updating the values." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:99 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 +msgid "Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:101 +msgid "" +"With this menu, you can add accounts to your **Chart of Accounts** and " +"indicate their initial opening balances." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:104 +msgid "" +"Basic settings are displayed on this page to help you review your Chart of " +"Accounts. To access all the settings of an account, click on the *double " +"arrow button* at the end of the line." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "" +"Setup of the Chart of Accounts and their opening balances in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:111 +msgid "" +":doc:`Click here ` for more information on " +"how to configure your Chart of Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:115 +msgid "Invoicing onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:117 +msgid "" +"There is another step-by-step onboarding banner that helps you take " +"advantage of your Odoo Invoicing and Accounting apps. The *Invoicing " +"onboarding banner* is the one that welcomes you if you use the Invoicing app" +" rather than the Accounting app." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:121 +msgid "" +"If you have Odoo Accounting installed on your database, you can reach it by " +"going to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:124 +msgid "The Invoicing onboarding banner is composed of four main steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:129 +msgid ":ref:`invoicing-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:130 +msgid ":ref:`invoicing-setup-layout`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:131 +msgid ":ref:`invoicing-setup-payment`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:132 +msgid ":ref:`invoicing-setup-sample`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:139 +msgid "" +"This form is the same as :ref:`the one presented in the Accounting " +"onboarding banner `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:145 +msgid "Invoice Layout" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:147 +msgid "" +"With this tool, you can design the appearance of your documents by selecting" +" which layout template, paper format, colors, font, and logo you want to " +"use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:150 +msgid "" +"You can also add your *Company Tagline* and the content of the documents’ " +"*footer*. Note that Odoo automatically adds the company's phone number, " +"email, website URL, and Tax ID (or VAT number) to the footer, according to " +"the values you previously configured in the :ref:`Company Data `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Document layout configuration in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:159 +msgid "" +"Add your **bank account number** and a link to your **General Terms & " +"Condition** in the footer. This way, your contacts can find the full content" +" of your GT&C online without having to print them on the invoices you issue." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:164 +msgid "" +"These settings can also be modified by going to :menuselection:`Settings -->" +" General Settings`, under the *Business Documents* section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:170 +msgid "Payment Method" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:172 +msgid "" +"This menu helps you configure the payment methods with which your customers " +"can pay you." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:175 +msgid "" +"Configuring a *Payment Provider* with this tool also activates the *Invoice " +"Online Payment* option automatically. With this, users can directly pay " +"online, from their Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:181 +msgid "Sample Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:183 +msgid "" +"Send yourself a sample invoice by email to make sure everything is correctly" +" configured." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:186 +msgid ":doc:`bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:187 +msgid ":doc:`get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:189 +msgid ":doc:`../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:190 +msgid "" +"`Odoo Tutorials: Accounting and Invoicing - Getting started [video] " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:3 +msgid "Average price on returned goods" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:8 +msgid "" +"*Average cost valuation* (AVCO) is an inventory valuation method that " +"evaluates cost based on the total cost of goods bought or produced during a " +"period, divided by the total number of items on-hand. Inventory valuation is" +" used to:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:12 +msgid "reflect the value of a company's assets;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:13 +msgid "keep track of the amount of unsold goods;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:14 +msgid "account for monetary value in goods that have yet to generate profit;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:15 +msgid "report on flow of goods throughout the quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:17 +msgid "" +"Because |AVCO| uses the weighted average to evaluate the cost, it is a good " +"fit for companies that sell only a few different products in large " +"quantities. In Odoo, this costing analysis is *automatically updated* each " +"time products are received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:21 +msgid "" +"Thus, when shipments are returned to their supplier, Odoo automatically " +"generates accounting entries to reflect the change in inventory valuation. " +"However, Odoo does **not** automatically update the |AVCO| calculation, " +"because :ref:`this can potentially create inconsistencies with inventory " +"valuation `." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 +msgid "" +"This document addresses a specific use case for theoretical purposes. " +"Navigate :ref:`here ` for " +"instructions on how to set up and use |AVCO| in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:32 +msgid "" +":ref:`Using inventory valuation `" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 +msgid "" +":ref:`Other inventory valuation methods " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 +msgid "" +"To use average cost inventory valuation on a product, navigate to " +":menuselection:`Inventory --> Configuration --> Product Categories` and " +"select the category that will be using |AVCO|. On the product category page," +" set :guilabel:`Costing Method` to `Average Cost (AVCO)` and " +":guilabel:`Inventory Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:44 +msgid "" +":ref:`Inventory valuation configuration " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:47 +msgid "Using average cost valuation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:49 +msgid "" +"The average cost method adjusts the inventory valuation when products are " +"received in the warehouse. This section explains how it works, but if the " +"explanation is unnecessary, skip to the :ref:`return to supplier use case " +"` section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +msgid "Formula" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:58 +msgid "" +"When new products arrive, the new average cost for each product is " +"recomputed using the formula:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 +msgid "" +"Avg~Cost = \\frac{(Old~Qty \\times Old~Avg~Cost) + (Incoming~Qty \\times Purchase~Price)}{Final~Qty}\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 +msgid "**Old Qty**: product count in stock before receiving the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 +msgid "" +"**Old Avg Cost**: calculated average cost for a single product from the " +"previous inventory valuation;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 +msgid "**Incoming Qty**: count of products arriving in the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 +msgid "" +"**Purchase Price**: estimated price of products at the reception of products" +" (since vendor bills may arrive later). The amount includes not only the " +"price for the products, but also added costs, such as shipping, taxes, and " +":ref:`landed costs `. At reception of the " +"vendor bill, this price is adjusted;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:71 +msgid "**Final Qty**: quantity of on-hand stock after the stock move." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:76 +msgid "" +"When products leave the warehouse, the average cost **does not** change. " +"Read about why the average cost valuation is **not** adjusted :ref:`here " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +msgid "Compute average cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +msgid "" +"To understand how the average cost of a product changes with each shipment, " +"consider the following table of warehouse operations and stock moves. Each " +"is a different example of how the average cost valuation is affected." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Operation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +msgid "Incoming Value" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Inventory Value" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Qty On Hand" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "Receive 8 tables at $10/unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "8 * $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "$80" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "8" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "$10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "Receive 4 tables at $16/unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "4 * $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +msgid "$144" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "Deliver 10 tables" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "-10 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "$24" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +msgid "" +"Ensure comprehension of the above computations by reviewing the \"Receive 8 " +"tables at $10/unit\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 +msgid "Initially, the product stock is 0, so all values are $0." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:108 +msgid "" +"In the first warehouse operation, `8` tables are received at `$10` each. The" +" average cost is calculated using the :ref:`formula " +"`:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 +msgid "" +"Avg~Cost = \\frac{0 + 8 \\times $10}{8} = \\frac{$80}{8} = $10\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 +msgid "" +"Since the *incoming quantity* of tables is `8` and the *purchase price* for " +"each is `$10`," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:115 +msgid "The inventory value in the numerator is evaluated to `$80`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:116 +msgid "`$80` is divided by the total amount of tables to store, `8`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +msgid "`$10` is the average cost of a single table from the first shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +msgid "" +"To verify this in Odoo, in the *Purchase* app, order `8` quantities of a new" +" product, `Table`, with no previous stock moves, for `$10` each." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 +msgid "" +"In the table's :guilabel:`Product Category` field in the :guilabel:`General " +"Information` tab of the product form, click the :guilabel:`➡️ (arrow)` icon," +" to open an :guilabel:`External Link` to edit the product category. Set the " +":guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory" +" Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:127 +msgid "" +"Then, return to the purchase order. Click :guilabel:`Confirm Order`, and " +"click :guilabel:`Receive Products` to confirm receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +msgid "" +"Next, check the inventory valuation record generated by the product " +"reception by navigating to :menuselection:`Inventory --> Reporting --> " +"Inventory Valuation`. Select the drop-down for `Table`, and view the " +":guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory " +"valuation at a specific point in time = on-hand quantity * unit price`). The" +" 8 tables in-stock are worth $80." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show inventory valuation of 8 tables in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:141 +msgid "" +"When the product category's :guilabel:`Costing Method` is set to " +":guilabel:`AVCO`, then the average cost of a product is also displayed on " +"the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, " +"on the product page itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +msgid "Product delivery (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "" +"For outgoing shipments, :ref:`outbound products have no effect on the " +"average cost valuation `. Although the " +"average cost valuation is not recalculated, the inventory value still " +"decreases because the product is removed from stock and delivered to the " +"customer location." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "" +"To demonstrate that the average cost valuation is not recalculated, examine " +"the \"Deliver 10 tables\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 +msgid "" +"Avg~Cost = \\frac{12 \\times $12 + (-10) \\times $12}{12-10} = \\frac{24}{2} = $12\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "" +"Because 10 tables are being sent out to customers, the *incoming quantity* " +"is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's " +"*purchase price*;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:162 +msgid "The *incoming inventory value* is `-10 * $12 = -$120`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 +msgid "" +"The old *inventory value* (`$144`) is added to the *incoming inventory " +"value* (`-$120`), so `$144 + -$120 = $24`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 +msgid "" +"Only `2` tables remain after shipping out `10` tables from `12`. So the " +"current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:167 +msgid "" +"`$24 / 2 = $12`, which is the same average cost as the previous operation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:169 +msgid "" +"To verify this in Odoo, sell `10` tables in the *Sales* app, validate the " +"delivery, and then review the inventory valuation record by going to in " +":menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the " +"topmost valuation layer, delivering `10` tables reduces the product's value " +"by `-$120`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:174 +msgid "" +"**Note**: What is not represented in this stock valuation record is the " +"revenue made from this sale, so this decrease is not a loss to the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show how deliveries decrease inventory valuation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:184 +msgid "Return items to supplier (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:186 +msgid "" +"Because the price paid to suppliers can differ from the price the product is" +" valued at with the |AVCO| method, Odoo handles returned items in a specific" +" way." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 +msgid "" +"Products are returned to suppliers at the original purchase price, but;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:190 +msgid "The internal cost valuation remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 +msgid "" +"The above :ref:`example table ` is updated as" +" follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +msgid "Qty*Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "Return 1 table bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "-1 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +msgid "" +"In other words, returns to vendors are perceived by Odoo as another form of " +"a product exiting the warehouse. To Odoo, because the table is valued at $12" +" per unit, the inventory value is reduced by `$12` when the product is " +"returned; the initial purchase price of `$10` is unrelated to the table's " +"average cost." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:208 +msgid "" +"To return a single table that was purchased for `$10`, navigate to the " +"receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise " +"1 ` by going to the :guilabel:`Inventory Overview`," +" clicking on :guilabel:`Receipts`, and selecting the desired receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:213 +msgid "" +"Then, click :guilabel:`Return` on the validated delivery order, and modify " +"the quantity to `1` in the reverse transfer window. This creates an outgoing" +" shipment for the table. Select :guilabel:`Validate` to confirm the outgoing" +" shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:217 +msgid "" +"Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` " +"to see how the outgoing shipment decreases the inventory value by $12." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Inventory valuation for return." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:227 +msgid "Eliminate stock valuation errors in outgoing products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:229 +msgid "" +"Inconsistencies can occur in a company's inventory when the average cost " +"valuation is recalculated on outgoing shipments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 +msgid "" +"To demonstrate this error, the table below displays a scenario in which 1 " +"table is shipped to a customer and another is returned to a supplier at the " +"purchased price." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +msgid "Qty*Price" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "Ship 1 product to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "-1 \\* $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "Return 1 product initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "-1 \\* $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$2**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "**0**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +msgid "" +"In the final operation above, the final inventory valuation for the table is" +" `$2` even though there are `0` tables left in stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 +msgid "Correct method" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:250 +msgid "" +"Use the average cost to value the return. This does not mean the company " +"gets $12 back for a $10 purchase; the item returned for $10 is valued " +"internally at $12. The inventory value change represents a product worth $12" +" no longer being accounted for in company assets." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:255 +msgid "Anglo-Saxon accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:257 +msgid "" +"In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** " +"also keep a holding account that tracks the amount to be paid to vendors. " +"Once a vendor delivers an order, **inventory value** increases based on the " +"vendor price of the products that have entered the stock. The holding " +"account (called **stock input**) is credited and only reconciled once the " +"vendor bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:263 +msgid "" +":ref:`Anglo-Saxon vs. Continental " +"`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:265 +msgid "" +"The table below reflects journal entries and accounts. The *stock input* " +"account stores the money intended to pay vendors when the vendor bill has " +"not yet been received. To balance accounts when returning products that have" +" a price difference between the price the product is **valued at** and the " +"price it was bought for, a *price difference* account is created." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Stock Input" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Price Diff" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "Receive 8 tables at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "($80)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "Receive 4 tables at $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "($64)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "Deliver 10 tables to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "Return 1 table initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$10**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$12**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:293 +msgid "Product reception" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 +msgid "Summary" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:298 +msgid "" +"At product reception, Odoo ensures companies can pay for goods that were " +"purchased by preemptively moving an amount matching the price of received " +"goods into the :doc:`liability account " +"`, **Stock " +"Input**. Then, once the bill has been received, the amount in the holding " +"account is transferred to *Accounts Payable*. Transfers into this account " +"means the bill has been paid. **Stock Input** is reconciled once the vendor " +"bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:305 +msgid "" +"Inventory valuation is a method of calculating how much each in-stock " +"product is worth internally. Since there is a difference between the price " +"the product is **valuated at** and the price the product was actually " +"**purchased for**, the **Inventory Valuation** account is unrelated to the " +"crediting and debiting operations of the **Stock Input** account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:310 +msgid "To conceptualize all this, follow the breakdown below." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 +msgid "Accounts balanced at received products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:315 +msgid "" +"In this example, a company starts with zero units of a product, `table`, in " +"stock. Then, 8 tables are received from the vendor:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 +msgid "" +"The **Stock Input** account stores `$80` of credit owed to the vendor. The " +"amount in this account is unrelated to the inventory value." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:320 +msgid "" +"`$80` worth of tables came **in** (**debit** the *Inventory Value* account " +"`$80`), and" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 +msgid "" +"`$80` must be paid **out** for received goods (**credit** the *Stock Input* " +"account `$80`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:367 +msgid "In Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:326 +msgid "" +"Odoo generates an accounting journal entry when shipments that use |AVCO| " +"costing method are received. Configure a :guilabel:`Price Difference " +"Account` by selecting the :guilabel:`➡️ (arrow)` icon next to the " +":guilabel:`Product Category` field on the product page." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:330 +msgid "" +"Under :guilabel:`Account Properties`, create a new :guilabel:`Price " +"Difference Account` by typing in the name of the account and clicking " +":guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as " +"`Expenses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Create price difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:338 +msgid "" +"Then, receive the shipment in the *Purchase* app or *Inventory* app, and " +"navigate to the :menuselection:`Accounting app --> Accounting --> Journal " +"Entries`. In the list, find the :guilabel:`Reference` that matches the " +"warehouse reception operation for the relevant product." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show accounting entry of 8 tables from the list." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:346 +msgid "" +"Click on the line for 8 tables. This accounting journal entry shows that " +"when the 8 tables were received, the `Stock Valuation` account increased by " +"`$80`. Conversely, the **Stock Input** account (set as `Stock Interim " +"(Received)` account by default) is credited `$80`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Debit stock valuation and credit stock input 80 dollars." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:355 +msgid "Accounts balanced at received vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:357 +msgid "" +"In this example, a company starts with zero units of a product, table, in " +"stock. Then, 8 tables are received from the vendor. When the bill is " +"received from vendor for 8 tables:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 +msgid "" +"Use `$80` in the **Stock Input** account to pay the bill. This cancels out " +"and the account now holds `$0`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:362 +msgid "Debit **Stock Input** `$80` (to reconcile this account)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 +msgid "" +"Credit **Accounts payable** `$80`. This account stores the amount the " +"company owes others, so accountants use the amount to write checks to " +"vendors." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:369 +msgid "" +"Once the vendor requests payment, navigate to the :menuselection:`Purchase " +"app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for " +"8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create " +"Bill`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:373 +msgid "" +"Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred" +" from the holding account, `Stock Interim (Received)` to `Accounts Payable`." +" :guilabel:`Confirm` the bill to record the payment to the vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show bill linked to the purchase order for 8 tables." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:382 +msgid "On product delivery" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:384 +msgid "" +"In the :ref:`above example table `, when 10" +" products are delivered to a customer, the **Stock Input** account is " +"untouched because there are no new products coming in. To put it simply:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:388 +msgid "" +"**Inventory valuation** is credited `$120`. Subtracting from inventory " +"valuation represents `$120` worth of products exiting the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:390 +msgid "Debit **Accounts Receivable** to record revenue from the sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show journal items linked to sale order." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:398 +msgid "" +"In the accounting journal entry invoicing a customer for 10 tables, the " +"accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** " +"all pertain to the sale of the product. **Accounts Receivable** is the " +"account where the customer payment will be received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:402 +msgid "" +"Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the " +"sale is made. So, up until the product is sold, scrapped, or returned, costs" +" of keeping the product in stock are not accounted for. The **Expense** " +"account is debited `$120` to log the costs of storing 10 tables during this " +"period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:408 +msgid "On product return" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:410 +msgid "" +"In the :ref:`above example table `, when " +"returning 1 product to a vendor purchased at `$10`, a company expects `$10` " +"in the **Accounts Payable** account from the vendor. However, **Stock " +"Input** account must be debited `$12` because the average cost is `$12` at " +"the time of the return. The missing `$2` is accounted for in the " +":guilabel:`Price Difference Account`, which is set up in the product's " +":guilabel:`Product Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:417 +msgid "" +"Behavior of *price difference accounts* varies from localization. In this " +"case, the account is intended to store differences between vendor price and " +"*automated* inventory valuation methods." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 +msgid "Summary:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:422 +msgid "" +"Debit **Stock Input** account `$10` to move the table from stock to stock " +"input. This move is to indicate that the table is to be processed for an " +"outgoing shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:424 +msgid "" +"Debit **Stock Input** an additional `$2` to account for the **Price " +"Difference**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 +msgid "" +"Credit **Stock Valuation** `$12` because the item is leaving the stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "2 dollar difference expensed in Price Difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:431 +msgid "Once the vendor's refund is received," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:433 +msgid "" +"Credit **Stock Input** account `$10` to reconcile the price of the table." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 +msgid "" +"Debit **Accounts Payable** `$10` to have the accountants collect and " +"register the payment in their journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Return to get 10 dollars back." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:146 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:361 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:65 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 +msgid "Chart of accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:5 +msgid "" +"The **chart of accounts (COA)** is the list of all the accounts used to " +"record financial transactions in the general ledger of an organization. The " +"chart of accounts can be found under :menuselection:`Accounting --> " +"Configuration --> Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:9 +msgid "" +"When browsing your chart of accounts, you can sort the accounts by " +":guilabel:`Code`, :guilabel:`Account Name`, or :guilabel:`Type`, but other " +"options are available in the drop-down menu" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Drop-down toggle button" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Group the accounts by type in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +msgid "Configuration of an account" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:21 +msgid "" +"The country you select during the creation of your database (or additional " +"company in your database) determines which :doc:`fiscal localization package" +" <../../fiscal_localizations>` is installed by default. This package " +"includes a standard chart of accounts already configured according to the " +"country's regulations. You can use it directly or set it according to your " +"company's needs." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:26 +msgid "" +"To create a new account, go to :menuselection:`Accounting --> Configuration " +"--> Chart of Accounts`, click :guilabel:`Create`, and fill in (at the " +"minimum) the required fields (:guilabel:`Code, Account Name, Type`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:31 +msgid "" +"It is not possible to modify the **fiscal localization** of a company once a" +" journal entry has been posted." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:35 +msgid "Code and name" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:37 +msgid "" +"Each account is identified by its :guilabel:`Code` and :guilabel:`Name`, " +"which also indicate the account's purpose." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 +msgid "" +"Correctly configuring the **account type** is critical as it serves multiple" +" purposes:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 +msgid "Information on the account's purpose and behavior" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:48 +msgid "Generate country-specific legal and financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:49 +msgid "Set the rules to close a fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 +msgid "Generate opening entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +msgid "" +"To configure an account type, open the :guilabel:`Type` field's drop-down " +"selector and select the corresponding type from the following list:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Report" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Category" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Account Types" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/reporting.rst:36 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:23 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 +msgid "Balance Sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 +msgid "Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 +msgid "Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 +msgid "Bank and Cash" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:83 +msgid "Current Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 +msgid "Non-current Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 +msgid "Prepayments" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 +msgid "Fixed Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +msgid "Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 +msgid "Payable" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 +msgid "Credit Card" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 +msgid "Current Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 +msgid "Non-current Liabilities" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 +msgid "Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 +msgid "Current Year Earnings" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:24 +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 +msgid "Profit & Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +msgid "Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +msgid "Other Income" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 +msgid "Expense" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 +msgid "Depreciation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 +msgid "Cost of Revenue" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +msgid "Other" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +msgid "Off-Balance Sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:98 +msgid "" +"Some **account types** can **automate** the creation of :ref:`asset ` entries. To **automate** entries, click :guilabel:`View` on an " +"account line and go to the :guilabel:`Automation` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:102 +msgid "You have three choices for the :guilabel:`Automation` tab:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 +msgid ":guilabel:`No`: this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +msgid "" +":guilabel:`Create in draft`: whenever a transaction is posted on the " +"account, a draft entry is created but not validated. You must first fill out" +" the corresponding form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 +msgid "" +":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred " +"Expense Model`. Whenever a transaction is posted on the account, an entry is" +" created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 +#: ../../content/applications/finance/accounting/taxes.rst:14 +msgid "Default taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +msgid "" +"In the :guilabel:`View` menu of an account, select a **default tax** to be " +"applied when this account is chosen for a product sale or purchase." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:117 +#: ../../content/applications/finance/documents.rst:52 +#: ../../content/applications/finance/sign.rst:236 +msgid "Tags" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:119 +msgid "" +"Some accounting reports require **tags** to be set on the relevant accounts." +" To add a tag, under :guilabel:`View`, click the :guilabel:`Tags` field and " +"select an existing tag or :guilabel:`Create` a new one." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:124 +msgid "Account groups" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +msgid "" +"**Account groups** are useful to list multiple accounts as *sub-accounts* of" +" a bigger account and thus consolidate reports such as the **Trial " +"Balance**. By default, groups are handled automatically based on the code of" +" the group. For example, a new account `131200` is going to be part of the " +"group `131000`. You can attribute a specific group to an account in the " +":guilabel:`Group` field under :guilabel:`View`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:133 +msgid "Create account groups manually" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:136 +msgid "" +"Regular users should not need to create account groups manually. The " +"following section is only intended for rare and advanced use cases." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:139 +msgid "" +"To create a new account group, activate :ref:`developer mode ` and head to :menuselection:`Accounting --> Configuration --> Account " +"Groups`. Here, create a new group and enter the :guilabel:`name, code " +"prefix, and company` to which that group account should be available. Note " +"that you must enter the same code prefix in both :guilabel:`From` and " +":guilabel:`to` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account groups creation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:147 +msgid "" +"To display your **Trial Balance** report with your account groups, go to " +":menuselection:`Accounting --> Reporting --> Trial Balance`, then open the " +":guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account Groups in the Trial Balance in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:155 +msgid "Allow reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:157 +msgid "" +"Some accounts, such as accounts made to record the transactions of a payment" +" method, can be used for the reconciliation of journal entries." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:160 +msgid "" +"For example, an invoice paid with a credit card can be marked as " +":guilabel:`paid` if reconciled with its payment. Therefore, the account used" +" to record credit card payments needs to be configured as **allowing " +"reconciliation**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:164 +msgid "" +"To do so, check the :guilabel:`Allow Reconciliation` box in the account's " +"settings, and :guilabel:`Save`; or enable the button from the chart of " +"accounts view." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Allow reconciliation for accounts in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:171 +msgid "Deprecated" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:173 +msgid "" +"It is not possible to delete an account once a transaction has been recorded" +" on it. You can make them unusable by using the **Deprecated** feature: " +"check the :guilabel:`Deprecated` box in the account's settings, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 +msgid ":doc:`cheat_sheet`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 +msgid ":doc:`../vendor_bills/assets`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 +msgid ":doc:`../vendor_bills/deferred_expenses`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 +msgid ":doc:`../customer_invoices/deferred_revenues`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 +msgid "" +"`Odoo Tutorials: Chart of accounts `_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 +msgid "" +"`Odoo Tutorials: Update your chart of accounts " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:7 +msgid "Accounting cheat sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:13 +msgid "" +"The **Balance Sheet** is a snapshot of the company's finances at a specific " +"date (as opposed to the Profit and Loss, which is an analysis over a " +"period)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:18 +msgid "" +"**Assets** represent the company's wealth and the goods it owns. Fixed " +"assets include buildings and offices, while current assets include bank " +"accounts and cash. The money owed by a client is an asset. An employee is " +"not an asset." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:24 +msgid "" +"**Liabilities** are obligations from past events that the company will have " +"to pay in the future (utility bills, debts, unpaid suppliers). Liabilities " +"could also be defined as a source of financing which is provided to the " +"company, also called *leverage*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:30 +msgid "" +"**Equity** is the amount of the funds contributed by the owners of the " +"company (founders or shareholders) plus previously retained earnings (or " +"losses). Each year, net profits (or losses) may be reported as retained " +"earnings or distributed to the shareholders (as a dividend)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:34 +msgid "" +"What is owned (an asset) has been financed through debts to reimburse " +"(liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "A difference is made between **assets** and **expenses**:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:38 +msgid "" +"An **asset** is a resource with economic value that an individual, " +"corporation, or country owns or controls with the expectation that it will " +"provide a future benefit. Assets are reported on a company's balance sheet. " +"They are bought or created to increase a firm's value or benefit its " +"operations." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:48 +msgid "" +"The **profit and loss** (P&L) report shows the company's performance over a " +"specific period of time, usually a quarter or a fiscal year." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:53 +msgid "" +"The **revenue** refers to the money earned by the company by selling goods " +"and/or services." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:57 +msgid "" +"The **cost of goods sold** (COGS, or also known as \"Cost of Sale\") refers " +"to the sale of goods' costs (e.g., the cost of the materials and labor used " +"to create the goods)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:62 +msgid "" +"The **Gross profit** equals the revenues from sales minus the cost of goods " +"sold." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:66 +msgid "" +"**Operating expenses** (OPEX) include administration, sales and R&D " +"salaries, rent and utilities, miscellaneous costs, insurances, and anything " +"beyond the costs of products sold or the cost of sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:76 +msgid "Assets = Liabilities + Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:81 +msgid "" +"The **chart of accounts** lists all the company's accounts: both Balance " +"sheet accounts and P&L accounts. Every transaction is recorded by debiting " +"and crediting multiple accounts in a journal entry. In a way, a chart of " +"accounts is like a company's DNA!" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:85 +msgid "" +"Every account listed in the chart of accounts belongs to a specific " +"category. In Odoo, each account has a unique code and belongs to one of " +"these categories:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:92 +msgid "**Equity and subordinated debts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:89 +msgid "" +"**Equity** is the amount of money invested by a company's shareholders to " +"finance the company's activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:91 +msgid "" +"**Subordinated debts** are the amount of money lent by a third party to a " +"company to finance its activities. In the event of the dissolution of a " +"company, these third parties are reimbursed before the shareholders." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:94 +msgid "" +"**Fixed assets** are tangible (i.e., physical) items or properties that a " +"company purchases and uses to produce its goods and services. Fixed assets " +"are long-term assets. This means the assets have a useful life of more than " +"one year. They also include properties, plants, and equipments (also known " +"as \"PP&E\") and are recorded on the balance sheet with that classification." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "**Current assets and liabilities**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:99 +msgid "" +"The **current assets** account is a balance sheet line item listed under the" +" Assets section, which accounts for all company-owned assets that can be " +"converted to cash within one year. Current assets include cash, cash " +"equivalents, accounts receivable, stock inventory, marketable securities, " +"prepaid liabilities, and other liquid assets." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "" +"**Current liabilities** are a company's short-term financial obligations due" +" within one year. An example of a current liability is money owed to " +"suppliers in the form of accounts payable." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "**Bank and cash accounts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:106 +msgid "" +"A **bank account** is a financial account maintained by a bank or other " +"financial institution in which the financial transactions between the bank " +"and a customer are recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "" +"A **cash account**, or cash book, may refer to a ledger in which all cash " +"transactions are recorded. The cash account includes both the cash receipts " +"and the cash payment journals." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:115 +msgid "**Expenses and income**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:111 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues. It is simply defined as the cost one is required to spend on " +"obtaining something. Common expenses include supplier payments, employee " +"wages, factory leases, and equipment depreciation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:114 +msgid "" +"The term \"**income**\" generally refers to the amount of money, property, " +"and other transfers of value received over a set period of time in exchange " +"for services or products." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:118 +msgid "Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:122 +msgid "" +"\\*: Customer Refund and Customer Payment boxes cannot be simultaneously " +"selected as they are contradictory." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:126 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:137 +msgid "" +"Every financial document of the company (e.g., an invoice, a bank statement," +" a pay slip, a capital increase contract) is recorded as a journal entry, " +"impacting several accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:140 +msgid "" +"For a journal entry to be balanced, the sum of all its debits must be equal " +"to the sum of all its credits." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:145 +msgid "" +"examples of accounting entries for various transactions. (see entries.js)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:150 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +msgid "Reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:152 +msgid "" +":doc:`Reconciliation <../../accounting/bank/reconciliation>` is the process " +"of linking journal items of a specific account and matching credits and " +"debits." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:155 +msgid "" +"Its primary purpose is to link payments to their related invoices to mark " +"them as paid. This is done by doing a reconciliation on the accounts " +"receivable account and/or the accounts payable account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:158 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:160 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:161 +msgid "" +"the links between the payments and the invoices are detected at the bank " +"matching process" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +msgid "Invoice 1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +msgid "Partial payment 1/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +msgid "70" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +msgid "Invoice 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +msgid "65" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "Partial payment 2/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "30" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +msgid "Payment 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 +msgid "Invoice 3" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 +msgid "50" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 +msgid "Total to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 +#: ../../content/applications/finance/accounting/reporting.rst:149 +msgid "Bank Reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:192 +msgid "" +"Bank reconciliation is the matching of bank statement lines (provided by " +"your bank) with transactions recorded internally (payments to suppliers or " +"from customers). For each line in a bank statement, it can be:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:196 +msgid "" +"**matched with a previously recorded payment**: a payment is registered when" +" a check is received from a customer, then matched when checking the bank " +"statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:198 +msgid "" +"**recorded as a new payment**: the payment's journal entry is created and " +"reconciled with the related invoice when processing the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:200 +msgid "" +"**recorded as another transaction**: bank transfer, direct charge, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:202 +msgid "" +"Odoo should automatically reconcile most transactions; only a few should " +"need manual review. When the bank reconciliation process is finished, the " +"balance on the bank account in Odoo should match the bank statement's " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:209 +msgid "Checks Handling" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:211 +msgid "" +"There are two approaches to managing checks and internal wire transfers:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:213 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:214 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:218 +msgid "" +"The first journal entry is created by registering the payment on the " +"invoice. The second one is created when registering the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +msgid "Invoice ABC" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +msgid "Undeposited funds" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +msgid "Check 0123" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:243 +msgid "" +"A journal entry is created by registering the payment on the invoice. When " +"reconciling the bank statement, the statement line is linked to the existing" +" journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +msgid "Bank Statement" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +msgid "Statement XYZ" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:3 +msgid "Multi-currency system" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:5 +msgid "" +"Odoo allows you to issue invoices, receive bills, and record transactions in" +" currencies other than the main currency configured for your company. You " +"can also set up bank accounts in other currencies and run reports on your " +"foreign currency activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:10 +msgid ":doc:`../bank/foreign_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:20 +msgid "Main currency" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:22 +msgid "" +"The **main currency** is defined by default according to the company's " +"country. You can change it by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and changing the currency in the " +":guilabel:`Main Currency` setting." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:29 +msgid "Enable foreign currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:31 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Currencies`, and " +"enable the currencies you wish to use by toggling the :guilabel:`Active` " +"button." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Enable the currencies you wish to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:41 +msgid "Currency rates" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:44 +msgid "Manual update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:46 +msgid "" +"To manually create and set a currency rate, go to :menuselection:`Accounting" +" --> Configuration --> Currencies`, click on the currency you wish to change" +" the rate of, and under the :guilabel:`Rates` tab, click :guilabel:`Add a " +"line` to create a new rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Create or modify the currency rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:55 +msgid "Automatic update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:57 +msgid "" +"When you activate a second currency for the first time, :guilabel:`Automatic" +" Currency Rates` appears under :menuselection:`Accounting Dashboard --> " +"Configuration --> Settings --> Currencies`. By default, you have to click on" +" the **Update now** button (:guilabel:`🗘`) to update the rates." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:61 +msgid "" +"Odoo can update the rates at regular intervals. To do so, change the " +":guilabel:`Interval` from :guilabel:`Manually` to :guilabel:`Daily`, " +":guilabel:`Weekly`, or :guilabel:`Monthly`. You can also select the web " +"service from which you want to retrieve the latest currency rates by " +"clicking on the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:69 +msgid "Exchange difference entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:71 +msgid "" +"Odoo automatically records exchange differences entries on dedicated " +"accounts, in a dedicated journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:74 +msgid "" +"You can define which journal and accounts to use to **post exchange " +"difference entries** by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Default Accounts` and editing the " +":guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:79 +msgid "" +"If you receive a payment for a customer invoice one month after it was " +"issued, the exchange rate has likely changed since. Therefore, this " +"fluctuation implies some profit or loss due to the exchange difference, " +"which Odoo automatically records in the default **Exchange Difference** " +"journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:89 +msgid "" +"Each account can have a set currency. By doing so, all moves relevant to the" +" account are forced to have that account's currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:92 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Charts of " +"Accounts` and select a currency in the field :guilabel:`Account Currency`. " +"If left empty, all active currencies are handled instead of just one." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:252 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:159 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:278 +#: ../../content/applications/finance/fiscal_localizations/france.rst:194 +#: ../../content/applications/finance/fiscal_localizations/india.rst:101 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:299 +msgid "Journals" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:101 +msgid "" +"If a currency is set on a **journal**, that journal only handles " +"transactions in that currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:103 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the journal you want to edit, and select a currency in the field " +":guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency for the journal to handle." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 +msgid "Multi-currency accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 +msgid "Invoices, bills, and other documents" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 +msgid "" +"For all documents, you can select the currency and journal to use for the " +"transaction on the document itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:130 +#: ../../content/applications/finance/accounting/payments/checks.rst:58 +msgid "Payment registration" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:132 +msgid "" +"To register a payment in a currency other than your company's main currency," +" click on the :guilabel:`Register Payment` payment button of your document " +"and, in the pop-up window, select a **currency** in the :guilabel:`Amount` " +"field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use before registering the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:143 +msgid "Bank transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:145 +msgid "" +"When creating or importing bank transactions, the amount is in the company's" +" main currency. To input a **foreign currency**, select a currency in the " +":guilabel:`Foreign Currency`. Once selected, enter the :guilabel:`Amount` in" +" your main currency for it to automatically get converted in the foreign " +"currency in the :guilabel:`Amount in Currency field`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "The extra fields related to foreign currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:154 +msgid "" +"When reconciling, Odoo displays both the foreign currency amount and the " +"equivalent amount in your company's main currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:160 +msgid "Exchange rate journal entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:162 +msgid "" +"To see **exchange difference journal entries**, go to " +":menuselection:`Accounting Dashboard --> Accounting --> Journals: " +"Miscellaneous`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Exchange rate journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:3 +msgid "VAT units" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:6 +msgid "This is only applicable to multi-company environments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:8 +msgid "" +"A **VAT unit** is a group of VAT-taxable enterprises that are legally " +"independent of each other but are closely linked financially, " +"organizationally, and economically and therefore considered the same VAT-" +"taxable enterprise. **VAT units** are not mandatory, but if created, " +"constituent companies of the unit must belong to the same **country**, use " +"the same **currency**, and one company must be designated as the " +"**representative** company of the **VAT unit**. **VAT units** receive a " +"specific **tax ID** intended only for **tax returns**. **Constituent** " +"companies keep their **tax ID** used for **commercial purposes**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:17 +msgid "" +"Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can " +"recover €280.000,00 of VAT taxes. They form up as a **VAT unit** so that the" +" two amounts balance out and must conjointly only pay €20.000,00 of VAT " +"taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:24 +msgid "" +"To configure a **VAT unit**, go to :menuselection:`Settings --> General " +"Settings`, scroll down to the :guilabel:`Companies` section, and click " +":guilabel:`Manage Companies`. Select the company to serve the " +"**representative** role, and in the :guilabel:`General Information` tab, " +"fill in the mandatory fields for the .XML export when exporting the **tax " +"report**: :guilabel:`Company Name`, :guilabel:`Address`, :guilabel:`VAT`, " +":guilabel:`Currency`, :guilabel:`Phone`, and :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "General information tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:35 +msgid "" +"Then, click on the :guilabel:`VAT Units` tab, :guilabel:`Add a line`, and " +"either select an existing **VAT unit**, or create a new one. Enter a " +"**name** for the unit, :guilabel:`Country` of the constituent companies and " +"tax report, the :guilabel:`Companies`, the :guilabel:`Main Company` that " +"serves the **representative** role, and the :guilabel:`Tax ID` of the **VAT " +"unit**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT units tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:45 +msgid "Fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:47 +msgid "" +"As transactions between constituents of the same **VAT unit** are not " +"subject to VAT, it is possible to create a :doc:`tax mapping (fiscal " +"position) <../taxes/fiscal_positions>` to avoid the application of VAT on " +"inter-constituent transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:51 +msgid "" +"Be sure a constituent company has been selected before, then go to " +":menuselection:`Accounting --> Configuration --> Fiscal Positions`, and " +":guilabel:`Create` a new **fiscal position**. Click the :guilabel:`Tax " +"Mapping` tab, select the :guilabel:`Tax on Product` usually applied for " +"**non-constituent** transactions, and in :guilabel:`Tax to Apply`, select " +"the 0% tax to apply for **constituent** transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:57 +msgid "" +"Do the same for the :guilabel:`Account Mapping` tab if required, and repeat " +"this process for **each** constituent company on your database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:61 +msgid "" +"Depending on your :doc:`localization package " +"`, taxes may vary from the " +"screenshot displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:0 +msgid "Tax mapping of fiscal position for VAT unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:68 +msgid "" +"Then, assign the fiscal position by opening the **Contacts** app. Search for" +" a **constituent** company, and open the contact's **card**. Click the " +":guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` " +"field, input the **fiscal position** created for the **VAT unit**. Repeat " +"the process for each **constituent** company card form, on each company " +"database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:74 +msgid ":doc:`../taxes/fiscal_positions`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:79 +msgid "" +"The **representative** company can access the aggregated tax report of the " +"**VAT unit** by going to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, and selecting the **VAT unit** in :guilabel:`Tax Unit`. This report" +" contains the aggregated transactions of all **constituents** and the .XML " +"export contains the name and VAT number of the **main** company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT unit tax report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:5 +msgid "Payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:7 +msgid "" +"In Odoo, payments can either be automatically linked to an invoice or bill " +"or be stand-alone records for use at a later date:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:10 +msgid "" +"If a payment is **linked to an invoice or bill**, it reduces/settles the " +"amount due of the invoice. You can have multiple payments related to the " +"same invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:13 +msgid "" +"If a payment is **not linked to an invoice or bill**, the customer has an " +"outstanding credit with your company, or your company has an outstanding " +"debit with a vendor. You can use those outstanding amounts to reduce/settle " +"unpaid invoices/bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:18 +msgid ":doc:`Internal transfers `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:19 +msgid ":doc:`bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:20 +msgid "" +"`Odoo Tutorials: Bank Configuration `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:24 +msgid "Registering payment from an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:26 +msgid "" +"When clicking :guilabel:`Register payment` in a customer invoice or vendor " +"bill, it generates a new journal entry and changes the amount due according " +"to the payment amount. The counterpart is reflected in an :ref:`outstanding " +"` **receipts** or **payments** account. At this " +"point, the customer invoice or vendor bill is marked as :guilabel:`In " +"payment`. Then, when the outstanding account is reconciled with a bank " +"statement line, the invoice or vendor bill changes to the :guilabel:`Paid` " +"status." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:33 +msgid "" +"The information icon near the payment line displays more information about " +"the payment. You can access additional information, such as the related " +"journal, by clicking :guilabel:`View`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "See detailed information of a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:40 +msgid "" +"The customer invoice or vendor bill must be in the :guilabel:`Posted` status" +" to register the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:42 +msgid "" +"If you unreconcile a payment, it still appears in your books but is no " +"longer linked to the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:44 +msgid "" +"If you (un)reconcile a payment in a different currency, a journal entry is " +"automatically created to post the currency exchange gains/losses (reversal) " +"amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:46 +msgid "" +"If you (un)reconcile a payment and an invoice having cash basis taxes, a " +"journal entry is automatically created to post the cash basis tax (reversal)" +" amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:50 +msgid "" +"If your main bank account is set as an :ref:`outstanding account " +"`, and the payment is registered in Odoo (not " +"through a related bank statement), invoices and bills are directly " +"registered as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:55 +msgid "Registering payments not tied to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:57 +msgid "" +"When a new payment is registered via :menuselection:`Customers / Vendors -->" +" Payments` menu, it is not directly linked to an invoice or bill. Instead, " +"the account receivable or the account payable is matched with the " +"**outstanding account** until it is manually matched with its related " +"invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:63 +msgid "Matching invoices and bills with payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:65 +msgid "" +"A blue banner appears when you validate a new invoice/bill and an " +"**outstanding payment** exists for this specific customer or vendor. It can " +"easily be matched from the invoice or bill by clicking :guilabel:`ADD` under" +" :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:72 +msgid "" +"The invoice or bill is now marked as :guilabel:`In payment` until it is " +"reconciled with its corresponding bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:78 +msgid "Batch payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:80 +msgid "" +"Batch payments allow you to group different payments to ease " +":doc:`reconciliation `. They are also useful when you " +"deposit :doc:`checks ` to the bank or for :doc:`SEPA " +"payments `. To do so, go to :menuselection:`Accounting " +"--> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors " +"--> Batch Payments`. In the list view of payments, you can select and group " +"several payments in a batch by clicking :menuselection:`Action --> Create " +"Batch Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:88 +msgid ":doc:`payments/batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:89 +msgid ":doc:`payments/batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:94 +msgid "Payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:96 +msgid "" +"The :guilabel:`Payments matching` tool opens all unreconciled customer " +"invoices or vendor bills and allows you to process them individually, " +"matching all payments and invoices in one place. You can reach this tool " +"from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor" +" Bills`, click the drop-down menu button (:guilabel:`⋮`), and select " +":guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> " +"Accounting --> Reconciliation`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Payments matching menu in the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:106 +msgid "" +"During the :doc:`reconciliation `, if the sum of the " +"debits and credits does not match, there is a remaining balance. This either" +" needs to be reconciled at a later date or needs to be written off directly." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:111 +msgid "Batch payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:113 +msgid "" +"You can use the **batch reconciliation feature** to reconcile several " +"outstanding payments or invoices simultaneously for a specific customer or " +"vendor. Go to your **Accounting Dashboard** and open your **bank journal**. " +"In the **bank reconciliation** view, select a **transaction**, and click the" +" :guilabel:`Batch Payments` tab. From here, you can reconcile your " +":doc:`batch payments ` with your outstanding payments or " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "The batch payment reconcile option." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:123 +msgid "Registering a partial payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:125 +msgid "" +"To register a **partial payment**, click :guilabel:`Register payment` from " +"the related invoice or bill, and enter the amount received or paid. Upon " +"entering the amount, a prompt appears to decide whether to :guilabel:`Keep " +"open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select " +":guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or " +"bill is now marked as :guilabel:`Partial`. Select :guilabel:`Mark as fully " +"paid` if you wish to settle the invoice or bill with a difference in the " +"amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Partial payment of an invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:136 +msgid "Reconciling payments with bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:138 +msgid "" +"Once a payment has been registered, the status of the invoice or bill is " +":guilabel:`In payment`. The next step is :doc:`reconciling " +"` it with the related bank statement line to have the " +"transaction finalized and the invoice or bill marked as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:3 +msgid "Batch payments by bank deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:5 +msgid "" +"A **batch deposit** is a convenient way to group customer payments and " +"deposit them into your bank account. The feature lets you list multiple " +"payments and generate a detailed deposit slip with a batch reference. This " +"reference can be used when reconciling to match bank statement lines with " +"transactions in the batch deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:13 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" +" Payments` and tick :guilabel:`Batch Payments` to activate the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:17 +msgid "Deposit multiple payments in batch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:20 +msgid "Register payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:22 +msgid "" +"Before performing a batch deposit, it is necessary to register each " +"transaction's payment. To do so, open the corresponding customer invoice and" +" click :guilabel:`Register Payment`. In the pop-up window, select the " +":guilabel:`Journal` linked to your bank account and :guilabel:`Batch " +"Deposit` as the :guilabel:`Payment Method`, and click :guilabel:`Create " +"Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Registering a customer payment as part of a batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:31 +msgid "Add payments to a batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:33 +msgid "" +"To add payments to a batch deposit, go to :menuselection:`Accounting --> " +"Customers --> Batch Payments`, and click :guilabel:`New`. Next, select the " +":guilabel:`Bank` and choose :guilabel:`Batch Deposit` as the " +":guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Filling out a new inbound batch payment form" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:40 +msgid "" +"Click :guilabel:`Add a line`. In the pop-up window, tick all payments to " +"include in the batch deposit, then click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Selecting all payments to include in the batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:46 +msgid "Once done, click :guilabel:`Validate` to finalize the batch deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:49 +msgid "" +"Click :guilabel:`Print` to download a PDF file to include with the deposit " +"slip." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:54 +msgid "" +"Once the bank transactions are on your database, you can reconcile bank " +"statement lines with the batch payment. To do so, go to the " +":guilabel:`Accounting Dashboard` and click :guilabel:`Reconcile Items` on " +"the related bank account. Go to the :guilabel:`Batch Payments` tab to select" +" a specific batch and click :guilabel:`Validate` to finalize the process." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Reconciling the batch payment with all its transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:63 +msgid "" +"If a specific payment could not be processed by the bank or is missing, " +"remove the related payment before reconciling." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:68 +msgid ":doc:`batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:3 +msgid "Batch payments: SEPA Direct Debit (SDD)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.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 " +"euros. With **SEPA Direct Debit** (SDD), your customers can sign a mandate " +"that authorizes you to collect future payments from their bank accounts. " +"This is particularly useful for recurring payments based on a subscription." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:10 +msgid "" +"You can record customer mandates in Odoo, and generate `.xml` files " +"containing pending payments made with an SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"SDD is supported by all SEPA countries, which includes the 27 member states " +"of the European Union as well as additional countries." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"`List of all SEPA countries " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:22 +msgid "" +"Go to :menuselection:`Accounting app --> Configuration --> Settings`, " +"activate :guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`." +" Enter your company's :guilabel:`Creditor Identifier`. This number is " +"provided by your bank institution, or the authority responsible for " +"delivering them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Add a SEPA Creditor Identifier to Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:32 +msgid "SEPA Direct Debit Mandates" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:35 +msgid "Create a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:37 +msgid "" +"The :abbr:`SDD (sepa direct debit)` Mandate is the document that your " +"customers sign to authorize you to collect money directly from their bank " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:40 +msgid "" +"To create a new mandate, go to :menuselection:`Accounting app --> Customers " +"--> Direct Debit Mandates`, on :guilabel:`Create`, and fill out the form. " +"Export the PDF file by clicking on :guilabel:`Print`. It is then up to your " +"customer to sign this document. Once done, upload the signed file and click " +"on :guilabel:`Validate` to start running the mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:46 +msgid "" +"Make sure that the **IBAN bank accounts details** are correctly recorded on " +"the debtor’s contact form, under the :guilabel:`Accounting` tab, and in your" +" own :doc:`Bank Account <../bank>` settings." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:50 +msgid "SEPA Direct Debit as a payment method" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:52 +msgid "" +"SDD can be used as a payment method both on your **eCommerce** or on the " +"**Customer Portal** by activating SDD as a **Payment Provider**. With this " +"method, your customers can create their mandates. To ensure the validity of " +"the information given by the customer, they will have to confirm each " +"mandate with one successful bank transfer of the expected amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:57 +msgid "" +"To do so, go to :menuselection:`Accounting app --> Configuration --> Payment" +" Providers`, click on :guilabel:`SEPA Direct Debit`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:61 +msgid "" +"Make sure to change the :guilabel:`State` field to :guilabel:`Enabled` and " +"set the provider as \"Published\" so that it is available for your " +"customers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:64 +msgid "" +"Customers using SDD as payment method get prompted to add their IBAN, email " +"address, and to sign their SEPA Direct Debit mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:68 +msgid "Add link to future **Payment Provider** documentation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:71 +msgid "Close or revoke a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:73 +msgid "" +"Direct debit mandates are closed automatically after their :guilabel:`End " +"Date`. If this field is left blank, the mandate keeps being **Active** until" +" it is **Closed** or **Revoked**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:76 +msgid "" +"Clicking on :guilabel:`Close` updates the mandate’s end day to the current " +"day. This means that invoices issued after the present day will not be " +"processed with an SDD payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:79 +msgid "" +"Clicking on :guilabel:`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 are still included in " +"the next SDD `.xml` file." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:84 +msgid "" +"Once a mandate has been :guilabel:`closed` or :guilabel:`revoked`, it cannot" +" be reactivated." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:87 +msgid "Get paid with SEPA Direct Debit batch payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:92 +msgid "" +"You can register SDD payments for invoices issued to customers who have an " +"active SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:94 +msgid "" +"To do so, open the invoice, click on :guilabel:`Register Payment`, and " +"choose :guilabel:`SEPA Direct Debit` as payment method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:98 +msgid "Generate SEPA Direct Debit `.XML` files to submit payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:100 +msgid "" +"`.xml` files with all SDD payment instructions can be uploaded to your " +"online banking interface to process all payments at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:104 +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 "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:109 +msgid "" +"To generate your `.xml` file of multiple pending SDD payments, you can " +"create a batch payment. To do so, go to :menuselection:`Accounting app --> " +"Customers --> Payments`, select the needed payments, then click on " +":guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once you" +" click on :guilabel:`Validate`, the `.xml` file is directly available for " +"download." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Generate an .XML file for your SDD payments in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:118 +msgid "" +"Finally, upload this file to your online banking interface to process the " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:121 +msgid "" +"You can retrieve all the generated SDD `.xml` files by going to " +":menuselection:`Accounting app --> Customers --> Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:125 +msgid ":doc:`batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:127 +msgid "" +"`List of all SEPA countries " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:129 +msgid "" +"`Sepa guidelines `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:3 +msgid "Checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:5 +msgid "" +"There are two ways to handle payments received by checks in Odoo, either by " +"using :ref:`outstanding accounts ` or by " +":ref:`bypassing the reconciliation process `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:9 +msgid "" +"**Using outstanding accounts is recommended**, as your bank account balance " +"stays accurate by taking into account checks yet to be cashed." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:13 +msgid "" +"Both methods produce the same data in your accounting at the end of the " +"process. But if you have checks that have not been cashed in, the " +"**Outstanding Account** method reports these checks in the **Outstanding " +"Receipts** account. However, funds appear in your bank account whether or " +"not they are reconciled, as the bank value is reflected at the moment of the" +" bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:20 +msgid ":ref:`Outstanding accounts `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:21 +msgid ":ref:`Bank reconciliation `" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:26 +msgid "Method 1: Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:28 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` by check on the invoice. Then, when your bank " +"account is credited with the check's amount, you reconcile the payment and " +"statement to move the amount from the **Outstanding Receipt** account to the" +" **Bank** account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:33 +msgid "" +"You can create a new payment method named *Checks* if you would like to " +"identify such payments quickly. To do so, go to :menuselection:`Accounting " +"--> Configuration --> Journals --> Bank`, click the :guilabel:`Incoming " +"Payments` tab, and :guilabel:`Add a line`. As :guilabel:`Payment Method`, " +"select :guilabel:`Manual`, and enter `Checks` as name." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:41 +msgid "Method 2: Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:43 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` on the related invoice. The amount is then moved " +"from the **Account Receivable** to the **Bank** account, bypassing the " +"reconciliation and creating only **one journal entry**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:47 +msgid "" +"To do so, you *must* follow the following setup. Go to " +":menuselection:`Accounting --> Configuration --> Journals --> Bank`. Click " +"the :guilabel:`Incoming Payments` tab and then :guilabel:`Add a line`, " +"select :guilabel:`Manual` as :guilabel:`Payment Method`, and enter `Checks` " +"as :guilabel:`Name`. Click the toggle menu button, tick " +":guilabel:`Outstanding Receipts accounts`, and in the :guilabel:`Outstanding" +" Receipts accounts` column, and set the :guilabel:`Bank` account for the " +"**Checks** payment method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Bypass the Outstanding Receipts account using the Bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:61 +msgid "By default, there are two ways to register payments made by check:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:63 +msgid "**Manual**: for single checks;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:64 +msgid "**Batch**: for multiple checks at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:66 +msgid "" +"This documentation focuses on **single-check** payments. For **batch " +"deposits**, see :doc:`the batch payments documentation `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:69 +msgid "" +"Once you receive a customer check, go to the related invoice " +"(:menuselection:`Accounting --> Customer --> Invoices)`, and click " +":guilabel:`Register Payment`. Fill in the payment information:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:72 +msgid ":guilabel:`Journal: Bank`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:73 +msgid "" +":guilabel:`Payment method`: :guilabel:`Manual` (or **Checks** if you have " +"created a specific payment method);" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:75 +msgid ":guilabel:`Memo`: enter the check number;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:76 +msgid "Click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Check payment info" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:81 +msgid "" +"The generated journal entries are different depending on the payment " +"registration method chosen." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:87 +msgid "Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:89 +msgid "" +"The invoice is marked as :guilabel:`In Payment` as soon as you record the " +"payment. This operation produces the following **journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Statement Match" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +msgid "100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:76 +msgid "Outstanding Receipts" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:100 +msgid "" +"Then, once you receive the bank statements, match this statement with the " +"check of the **Outstanding Receipts** account. This produces the following " +"**journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "X" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:111 +msgid "" +"If you use this approach to manage received checks, you get the list of " +"checks that have not been cashed in the **Outstanding Receipt** account " +"(accessible, for example, from the general ledger)." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:115 +msgid "Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:117 +msgid "" +"The invoice is marked as :guilabel:`Paid` as soon as you record the check." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:119 +msgid "" +"With this approach, you bypass the use of **outstanding accounts**, " +"effectively getting only one journal entry in your books and bypassing the " +"reconciliation:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:3 +msgid "Follow-up on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:5 +msgid "" +"A follow-up message can be sent to customers when a payment is overdue. Odoo" +" helps you identify late payments and allows you to schedule and send the " +"appropriate reminders using **follow-up actions** that automatically trigger" +" one or more actions according to the number of overdue days. You can send " +"your follow-ups via different means, such as email, post, or SMS." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:11 +msgid "" +"`Odoo Tutorials: Payment Follow-up " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:16 +msgid "" +"To configure a :guilabel:`Follow-Up Action`, go to " +":menuselection:`Accounting --> Configuration --> Follow-up Levels`, and " +"select or create (a) new follow-up level(s). Several follow-up actions are " +"available by default under the :guilabel:`Notification` tab, and the " +"**name** as well as the **number of days** can be changed. The follow-up " +":guilabel:`Actions` available are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:21 +msgid ":guilabel:`Send Email`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:22 +msgid ":ref:`Send a Letter `;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:23 +msgid ":ref:`Send an SMS message `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:25 +msgid "" +"You can use a pre-filled template for your messages by selecting a " +":guilabel:`Content Template`. To change the template used, hover over the " +"field and click the :guilabel:`-->`. If enabled, SMS messages have a " +"specific :guilabel:`Sms Template` field." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:29 +msgid "" +"It is possible to automatically send a reminder by enabling the " +":guilabel:`Automatic` option, and attaching the *open* invoice(s) by " +"enabling :guilabel:`Attach Invoices`, within a specific follow-up action." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:33 +msgid "" +"By clicking on the :guilabel:`Activity` tab, scheduling activities (tasks) " +"is possible. That way, an activity is automatically scheduled when the " +"follow-up is triggered. To do so, enable :guilabel:`Schedule Activity`, and " +"select a :guilabel:`Responsible` person for the task. Choose an " +":guilabel:`Activity Type`, and enter a :guilabel:`Summary` on how to handle " +"the activity, if desired." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:40 +msgid "" +"Set a negative number of days to send a reminder before the actual due date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:43 +msgid "Follow-up reports" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:45 +msgid "" +"Overdue invoices you need to follow up on are available in " +":menuselection:`Accounting --> Customers --> Follow-up Reports`. By default," +" Odoo filters by :guilabel:`Overdue Invoices`, but you can also filter by " +":guilabel:`In need of action` in the :guilabel:`Filters` menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:49 +msgid "" +"When selecting an invoice, you can see all of the customer's unpaid invoices" +" (overdue or not), with the due dates of late invoices appearing in red. You" +" can exclude invoices from a reminder by clicking :guilabel:`Exclude from " +"Follow-ups`. You can set either :guilabel:`Automatic` or :guilabel:`Manual` " +"reminders as well as a :guilabel:`Responsible` person for that customer." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:54 +msgid "" +"To send reminders, click on :guilabel:`Follow up`, and select the action(s) " +"you want to perform from:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:57 +msgid ":guilabel:`Print`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:58 +msgid ":guilabel:`Email`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:59 +msgid ":guilabel:`Sms`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:60 +msgid ":guilabel:`By post`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:62 +msgid "" +"You can :guilabel:`Attach Invoices` and change the content templates from " +"this view. When done, click :guilabel:`Send` or :guilabel:`Send & Print`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:66 +msgid "" +"The contact information on the invoice or the contact form is used to send " +"the reminder." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:67 +msgid "" +"When the reminder is sent, it is documented in the chatter of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:68 +msgid "" +"If it is not the right time for a reminder, you can specify the " +":guilabel:`Next Reminder` date. You will get the next report according to " +"the next reminder date set." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:72 +msgid "" +"Reconcile all bank statements right before launching the follow-up process " +"to avoid sending a reminder to a customer that has already paid." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:76 +msgid "Debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:78 +msgid "" +"To know whether a customer usually pays late or not, you can set a trust " +"level by marking them as :guilabel:`Good Debtor`, :guilabel:`Normal Debtor`," +" or :guilabel:`Bad Debtor` on their follow-up report. To do so, click on the" +" bullet next to the customer's name and select a trust level." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst-1 +msgid "Set debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:86 +msgid "Send reminders in batches" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:88 +msgid "" +"You can send reminder emails in batches from the :guilabel:`Follow-up " +"Reports` page. To do so, select all the reports you would like to process, " +"click on the :guilabel:`Action` gear icon, and select :guilabel:`Process " +"follow-ups`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:93 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:94 +msgid ":doc:`../../../marketing/sms_marketing/pricing/pricing_and_faq`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:95 +msgid ":doc:`../customer_invoices/snailmail`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:3 +msgid "Forecast future bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:5 +msgid "" +"In Odoo, you can manage payments by setting automatic **Payments Terms** and" +" **follow-ups**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:8 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:10 +msgid "" +"In order to track vendor conditions, we use **Payment Terms** in Odoo. They " +"allow keeping track of due dates on invoices. Examples of **Payment Terms** " +"are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:13 +msgid "50% within 30 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:14 +msgid "50% within 45 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:16 +msgid "" +"To create them, go to :menuselection:`Accounting --> Configuration --> " +"Invoicing: Payment Terms` and click on :guilabel:`Create` to add new terms " +"or click existing ones to modify them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:20 +msgid "" +"`Odoo Tutorials: Payment Terms `_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:23 +msgid "" +"Once **Payment Terms** are defined, you can assign them to your vendor by " +"default. To do so, go to :menuselection:`Vendors --> Vendors`, select a " +"vendor, click the :guilabel:`Sales & Purchase` tab, and select a specific " +"**Payment Term**. This way, every time you purchase from this vendor, Odoo " +"automatically proposes the chosen Payment Term." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:29 +msgid "" +"If you do not set a specific Payment Term on a vendor, you can still set one" +" on the vendor bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:32 +msgid "Forecast bills to pay with the aged payable report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:34 +msgid "" +"To track amounts to be paid to the vendors, use the **Aged Payable** report." +" To access it, go to :menuselection:`Accounting --> Reporting --> Partner " +"Reports: Aged Payable`. This report gives you a summary per vendor of the " +"amounts to pay, compared to their due date (the due date being computed on " +"each bill using the terms). This report tells you how much you will have to " +"pay within the following months." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:41 +msgid "Select bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:43 +msgid "" +"You can get a list of all your vendor bills by going to " +":menuselection:`Vendors --> Bills`. To view only the bills that you need to " +"pay, click :menuselection:`Filters --> Bills to Pay`. To view only overdue " +"payments, select the :guilabel:`Overdue` filter instead." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:47 +msgid "" +"You can also group bills by their due date by clicking :menuselection:`Group" +" By --> Due Date` and selecting a time period." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:3 +msgid "Internal transfers" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:5 +msgid "" +"Internal money transfers can be handled in Odoo. At least two bank accounts " +"are needed to make internal transfers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 +msgid ":doc:`How to add an additional bank account <../bank>`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:14 +msgid "" +"An internal transfer account is automatically created on your database based" +" on your company's localization and depending on your country’s legislation." +" To modify the default :guilabel:`Internal transfer account`, go to " +":menuselection:`Accounting --> Configuration --> Settings` and scroll down " +"to the :guilabel:`Default Accounts` section." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:20 +msgid "Register an internal transfer from one bank to another" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:22 +msgid "" +"If you want to transfer money from one bank to another, access the " +"Accounting Dashboard, click the drop-down selection button (:guilabel:`⋮`) " +"on the bank from which you want to make the transfer, then click " +":guilabel:`Payments`. Select or create a payment, tick the " +":guilabel:`Internal Transfer` checkbox, and select a :guilabel:`Destination " +"Journal` before you :guilabel:`Confirm` the internal transfer." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:28 +msgid "" +"The money is now booked in the transfer account and another payment is " +"automatically created in the destination journal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:33 +msgid "Bank journal (Bank A)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:42 +msgid "Outstanding Payments account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:44 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:60 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:45 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:62 +msgid "**Internal transfer account**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:46 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:64 +msgid "**$1,000**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:49 +msgid "Bank journal (Bank B)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:59 +msgid "Outstanding Receipts account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:66 +msgid "" +"There is **one outstanding payment** and **one outstanding receipt** pending" +" in your two bank account journals because the bank statement confirming the" +" sending and receiving of the money has not been booked yet." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 +msgid "" +"Once this is done, you can book and reconcile your bank statement lines as " +"usual." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:73 +msgid ":doc:`../bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:5 +msgid "Online payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:11 +msgid "" +"To make it more convenient for your customers to pay the invoices you issue," +" you can activate the **Invoice Online Payment** feature, which adds a *Pay " +"Now* button on their **Customer Portal**. This allows your customers to see " +"their invoices online and pay directly with their favorite payment method, " +"making the payment process much easier." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Payment provider choice after having clicked on \"Pay Now\"" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:23 +msgid "" +"Make sure your :ref:`Payment Providers are correctly configured " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:26 +msgid "" +"By default, \":doc:`Wire Transfer " +"`\" is the only " +"Payment Provider activated, but you still have to fill out the payment " +"details." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:29 +msgid "" +"To activate the Invoice Online Payment, go to :menuselection:`Accounting -->" +" Configuration --> Settings --> Customer Payments`, enable **Invoice Online " +"Payment**, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:33 +msgid "Customer Portal" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:35 +msgid "" +"After issuing the invoice, click on *Send & Print* and send the invoice by " +"email to the customer. They will receive an email with a link that redirects" +" them to the invoice on their **Customer Portal**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Email with a link to view the invoice online on the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:42 +msgid "" +"They can choose which Payment Provider to use by clicking on *Pay Now*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "\"Pay now\" button on an invoice in the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:49 +msgid ":doc:`/applications/finance/payment_providers`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:3 +msgid "Install the patch to disable online invoice payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:5 +msgid "" +"Following recent changes in Odoo 16, you might be warned that disabling the " +":guilabel:`Invoice Online Payment` setting will uninstall modules. If you " +"want to disable the feature without uninstalling modules, follow the steps " +"below to install the module **Payment - Account / Invoice Online Payment " +"Patch**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:0 +msgid "" +"If your Odoo database is created after the module **Payment - Account / " +"Invoice Online Payment Patch** was released, you don't have anything to do." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:0 +msgid "" +"To check if the module is already installed, go to :guilabel:`Apps`, remove " +"the `Apps` filter, and search for `account_payment`. If the module **Payment" +" - Account / Invoice Online Payment Patch** is present and marked as " +"installed, your Odoo database is already up-to-date and you are able to " +"disable the feature without side-effect." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:19 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:21 +msgid "" +"The possibility to disable the :guilabel:`Invoice Online Payment` setting " +"without side-effect is made available through a new Odoo module; to be able " +"to install it, you must make sure that your Odoo source code is up-to-date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:25 +msgid "" +"If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-" +"date and you can proceed to the next step." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:28 +msgid "" +"If you use Odoo with an on-premise setup or through a partner, you must " +"update your installation as detailed in :doc:`this documentation page " +"`, or by contacting your integrating " +"partner." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:33 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:35 +msgid "" +"New modules must be *discovered* by your Odoo instance to be available in " +"the **Apps** menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:37 +msgid "" +"To do so, activate the :ref:`developer mode `, and go to " +":menuselection:`Apps --> Update Apps List`. A wizard will ask for " +"confirmation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:41 +msgid "Install the module Invoice Online Payment Patch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:44 +msgid "" +"You should never install new modules in your production database without " +"first testing them in a duplicate or staging environment. For Odoo.com " +"customers, a duplicate database can be created from the database management " +"page. For Odoo.sh users, you should use a staging or duplicate database. For" +" on-premise users, you should use a staging environment---contact your " +"integrating partner for more information regarding how to test a new module " +"in your particular setup." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:50 +msgid "" +"The module should now be available in your :guilabel:`Apps` menu. Remove the" +" ``Apps`` filter and search for ``account_payment``; the module " +":guilabel:`Payment - Account / Invoice Online Payment Patch` should be " +"available for installation. If you cannot find the module after having " +"updated the list of available modules, it means your Odoo source code is not" +" up-to-date; refer to step one of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:56 +msgid "" +"Once the module is installed, disabling the feature will work as intended " +"and will not ask you to uninstall installed applications or modules." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:3 +msgid "Pay by checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:5 +msgid "" +"Once you decide to pay a supplier bill, you can select to pay by check. You " +"can then print all the payments registered by check. Finally, the bank " +"reconciliation process will match the checks you sent to suppliers with " +"actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:13 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:15 +msgid "" +"To activate the checks payment method, go to :menuselection:`Accounting --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Vendor " +"Payments` section. There, you can activate the payment method as well as set" +" up the :guilabel:`Check Layout`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:20 +msgid "" +"Once the :guilabel:`Checks` setting is activated, the **Checks** payment " +"method is automatically set up in the :guilabel:`Outgoing Payments` tabs of " +"**bank** journals." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:22 +msgid "" +"Some countries require specific modules to print checks; such modules may be" +" installed by default. For instance, the :guilabel:`U.S. Checks Layout` " +"module is required to print U.S. checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:27 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:30 +msgid "United States" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:32 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 +msgid "" +"**Quickbooks & Quicken**: check on top, stubs in the middle and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 +msgid "**Peachtree**: check in the middle, stubs on top and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:36 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:39 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:41 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 +msgid "registering a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:45 +msgid "reconciling bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:48 +msgid "Register a payment by check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:50 +msgid "" +"To register a payment, open any supplier bill from the menu " +":menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is " +"validated, you can register a payment. Set the :guilabel:`Payment Method` to" +" :guilabel:`Checks` and validate the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:56 +msgid "Print checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:58 +msgid "" +"On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, " +"you can see the number of checks registered. By clicking on " +":guilabel:`Checks to print` you have got the possibility to print the " +"reconciled checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:62 +msgid "" +"To print all checks in batch, select all payments from the list view and " +"click on :guilabel:`Print`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:3 +msgid "Pay with SEPA" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European Union to simplify bank transfers denominated in euros. SEPA " +"allows you to send payment orders to your bank to automate bank wire " +"transfers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:9 +msgid "SEPA is supported by the banks of the 27 EU member states, as well as:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:11 +msgid "EFTA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:13 +msgid "Iceland;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:14 +msgid "Liechtenstein;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:15 +msgid "Norway;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:16 +msgid "Switzerland." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:18 +msgid "Non-EEA SEPA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:20 +msgid "Andorra;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:21 +msgid "Monaco;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:22 +msgid "San Marino;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:23 +msgid "United Kingdom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:24 +msgid "Vatican City State." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:26 +msgid "Non-EEA territories:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:28 +msgid "Saint-Pierre-et-Miquelon;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:29 +msgid "Guernsey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:30 +msgid "Jersey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:31 +msgid "Isle of Man." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:33 +msgid "" +"When paying a bill in Odoo, you can select SEPA mandates as a payment " +"option. At the day's end, you can generate the SEPA file containing all bank" +" wire transfers and send it to the bank." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:36 +msgid "" +"By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** " +"specifications. This is a well-defined standard among banks. However, for " +"Swiss and German companies, other formats are used " +"**'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for " +"Germany." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:40 +msgid "" +"Once the payments are processed by your bank, you can directly import the " +"account statement in Odoo. The bank reconciliation process will seamlessly " +"match the SEPA orders you sent to your bank with actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:48 +msgid "Activate SEPA Credit Transfer (SCT)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:50 +msgid "" +"To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** " +"setting. To do so, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Vendor Payments: SEPA Credit Transfer (SCT)`. By activating the" +" setting and filling out your company data, you will be able to use the SCT " +"option when paying your vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:56 +msgid "" +"According to the localization package installed, the **SEPA Direct Debit** " +"and **SEPA Credit Transfer** modules may be installed by default. If not, " +"they need to be :ref:`installed `." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:60 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:62 +msgid "" +"From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) " +"on your bank journal and select :guilabel:`Configuration`. Click the " +":guilabel:`Outgoing Payments` tab, and, if not already present, add " +":guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:66 +msgid "" +"Make sure to specify the IBAN account number (domestic account numbers do " +"not work with SEPA) and the BIC (bank identifier code) in the " +":guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:70 +msgid "Registering payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:72 +msgid "" +"You can register and vendor payments made with SEPA. To do so, go to " +":menuselection:`Accounting --> Vendors --> Payments`. When creating your " +"payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment " +"Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:76 +msgid "" +"The first time you pay a vendor with SEPA, you have to fill in the " +":guilabel:`Recipient Bank Account` field with the bank name, IBAN, and BIC " +"(Bank Identifier Code). Odoo automatically verifies if the IBAN format is " +"respected." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:80 +msgid "" +"For future payments to this vendor, Odoo will automatically suggest you the " +"bank account, but it remains possible to select a new one." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:83 +msgid "" +"Once your payment is registered, do not forget to confirm it. You can also " +"pay vendor bills from the bill directly using the :guilabel:`Register " +"Payment` button at the top of a vendor bill. The form is the same, but the " +"payment is directly linked to the bill and will be automatically reconciled " +"with it." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:3 +msgid "Trusted accounts (send money)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:5 +msgid "" +"To protect users from sending money to scammers, vendor bank account numbers" +" must be marked as trusted before you can use them to make an outgoing " +"payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:8 +msgid "" +"To do so, open the vendor bank account and click on the :guilabel:`Send " +"Money` toggle switch button." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst-1 +msgid "" +"Example of a vendor bank account with the \"Send Money\" toggle button " +"switched to \"trusted.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:15 +msgid "All accounts are initially marked as untrusted." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:18 +msgid "Phishing attacks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:20 +msgid "" +"A **phishing attack** is an online scam designed to trick individuals or " +"companies into giving away sensitive information or money by sending out " +"fraudulent communication. Fraudsters pretend to be legitimate companies and " +"may use partial information to give credibility to their requests." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:24 +msgid "" +"There are several types of phishing attacks, including **invoice fraud**. In" +" this case, the fraudster pretends to be a genuine supplier following up on " +"unpaid bills or sending a new invoice, but with different payment " +"information than usual and with fake contact details." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:28 +msgid "" +"To protect yourself from these types of phishing attacks, remain vigilant " +"when you receive unexpected invoices or payment requests." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:32 +msgid "" +"In case of doubt, **we recommend contacting the vendor by phone**. Make sure" +" to call an official phone number by searching yourself, as the URLs, email " +"addresses, and phone numbers written in the communication you received may " +"be fake." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:37 +msgid "Elements to check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:39 +msgid "" +"There are several elements you can check by yourself when you receive an " +"outgoing payment request to a new account:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:46 +msgid "Communication style" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:43 +msgid "" +"Fraudulent emails and invoices often use a different communication style, " +"such as **different wording**, and may include **spelling and grammatical " +"mistakes**. Examine and **compare** them with previous ones that you know to" +" be authentic (e.g., payment instructions, language, company logo, etc.).*" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:50 +msgid "Urgency" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:49 +msgid "" +"Invoice frauds often use **urgent or threatening language** and change the " +"**payment deadline**. Check if you really received a late payment reminder " +"previously." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:53 +msgid "Type of account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:53 +msgid "" +"A company is unlikely to replace a bank account with a **money transfer " +"service**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:60 +msgid "Email and links domain names" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:56 +msgid "" +"Double-check the **email address domain** (`example@domain.com`). However, " +"be wary that fraudsters can make their email addresses look genuine or even " +"hack email addresses from your vendor's employees or even someone within " +"your own organization." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:60 +msgid "" +"Hover over the links in your email and check that the URLs they redirect to " +"are genuine. Your internet browser usually displays the link's target at the" +" bottom left of the window." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:8 +msgid "Main reports available" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:10 +msgid "" +"Besides the reports created specifically in each localisation module, a few " +"very useful **generic** and **dynamic reports** are available for all " +"countries :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:14 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:15 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:16 +msgid "**Executive Summary**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:17 +msgid "**General Ledger**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:18 +msgid "**Aged Payable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:19 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:20 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:21 +msgid "**Tax Report**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:22 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:24 +msgid "" +"You can annotate every reports to print them and report to your adviser. " +"Export to xls to manage extra analysis. Drill down in the reports to see " +"more details (payments, invoices, journal items, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:28 +msgid "" +"You can also compare values with another period. Choose how many periods you" +" want to compare the chosen time period with. You can choose up to 12 " +"periods back from the date of the report if you don't want to use the " +"default **Previous 1 Period** option." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:38 +msgid "" +"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity" +" of your organisation as at a particular date." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:44 +msgid "Profit and Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:46 +msgid "" +"The **Profit and Loss** report (or **Income Statement**) shows your " +"organisation's net income, by deducting expenses from revenue for the report" +" period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:53 +msgid "Executive Summary" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:55 +msgid "" +"The **Executive Summary** allows for a quick look at all the important " +"figures you need to run your company." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:58 +msgid "" +"In very basic terms, this is what each of the items in this section is " +"reporting :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "**Performance:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:64 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:63 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales (things like labour, materials, etc)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:70 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:67 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales, as well as any fixed overheads your " +"company has (things like rent, electricity, taxes you need to pay as a " +"result of those sales)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "" +"The ratio of net profit made, to the amount of assets the company used to " +"make those profits." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:93 +msgid "**Position:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:77 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:77 +msgid "" +"The average number of days it takes your customers to pay you (fully), " +"across all your customer invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:80 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:80 +msgid "" +"The average number of days it takes you to pay your suppliers (fully) across" +" all your bills." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:85 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:83 +msgid "" +"How much cash is expected in or out of your organisation in the next month " +"i.e. balance of your **Sales account** for the month less the balance of " +"your **Purchases account** for the month." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:93 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:88 +msgid "" +"Also referred to as **current ratio**, this is the ratio of current assets " +"(assets that could be turned into cash within a year) to the current " +"liabilities (liabilities which will be due in the next year). This is " +"typically used as as a measure of a company's ability to service its debt." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:98 +msgid "General Ledger" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:100 +msgid "" +"The **General Ledger Report** shows all transactions from all accounts for a" +" chosen date range. The initial summary report shows the totals for each " +"account and from there you can view a detailed transaction report or any " +"exceptions. This report is useful for checking every transaction that " +"occurred during a certain period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:111 +msgid "Aged Payable" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:113 +msgid "" +"Run the **Aged Payable Details** report to display information on individual" +" bills, credit notes and overpayments owed by you, and how long these have " +"gone unpaid." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:122 +msgid "Aged Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:124 +msgid "" +"The **Aged Receivables** report shows the sales invoices that were awaiting " +"payment during a selected month and several months prior." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:130 +msgid "Cash Flow Statement" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:132 +msgid "" +"The **Cash Flow Statement** shows how changes in balance sheet accounts and " +"income affect cash and cash equivalents, and breaks the analysis down to " +"operating, investing and financing activities." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:141 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:101 +msgid "Tax Report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:143 +msgid "" +"This report allows you to see the **net** and **tax amounts** for all the " +"taxes grouped by type (sale/purchase)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:3 +msgid "Analytic accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:5 +msgid "" +"Analytic accounting helps you track costs and revenues, as well as analyze " +"the profitability of a project or service. When creating your journal " +"entries, the analytic widget allows the distribution of costs in one or more" +" analytic accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:12 +msgid "" +"Enable the :guilabel:`Analytic Accounting` feature by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Analytics`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:16 +msgid "Analytic accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:18 +msgid "The analytic accounts give an overview of your costs and revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:20 +msgid "" +"Access your existing analytic accounts by going to " +":menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Accounts`. To create a new analytic account, click :guilabel:`New`," +" and fill in the required information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:24 +msgid ":guilabel:`Analytic Account`: add the name of your analytic account;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:25 +msgid ":guilabel:`Customer`: select the customer related to your project;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:26 +msgid "" +":guilabel:`Reference`: add a reference to make it easier to find the account" +" when you are on your bill;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:28 +msgid "" +":guilabel:`Plan`: add an :ref:`analytic plan " +"`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:29 +msgid "" +":guilabel:`Company`: if you are managing multiple companies, select the " +"company for which the analytic account will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:31 +msgid ":guilabel:`Currency`: select the currency of the analytic account;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:33 +msgid "Then, fill in your :doc:`budget ` information." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:38 +msgid "Analytic plans" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:40 +msgid "" +"The analytic plans allow you to analyze your accounting. For example, to " +"track costs and revenues by project or department." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:43 +msgid "" +"You can access the analytic plans by going to :menuselection:`Accounting -->" +" Configuration --> Analytic Accounting: Analytic Plans`. Click " +":guilabel:`New` to create a new plan." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst-1 +msgid "create an analytic plan" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:50 +msgid "The following information must be completed:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:52 +msgid "" +":guilabel:`Parent`: link your plan to another :guilabel:`Analytic Plan` to " +"build a hierarchy between your plans;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:54 +msgid "" +":guilabel:`Default Applicability`: decide how your plan behaves in the " +"widget when creating a new journal entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:57 +msgid "" +":guilabel:`Optional`: if selected, it is not mandatory to add the analytic " +"plan in the widget;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:58 +msgid "" +":guilabel:`Mandatory`: if selected, an orange bullet is visible in the " +"widget next to the plan until the analytic distribution is done (the bullet " +"then turns to green); it is not possible to confirm the entry if no analytic" +" account is selected;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:61 +msgid "" +":guilabel:`Unavailable`: if selected, the plan is not available in the " +"widget." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:63 +msgid "" +":guilabel:`Color`: select the color of the tag related to this specific " +"plan;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:64 +msgid ":guilabel:`Company`: add the company to which the plan applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:66 +msgid "" +"You can also fine-tune your plans' applicability by filling in the " +":guilabel:`Applicability` tab:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:68 +msgid "" +":guilabel:`Domain`: choose to which accounting document your plan applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:69 +msgid "" +":guilabel:`Financial Accounts Prefix`: select the prefix of the account(s) " +"to which this plan should be applied;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:71 +msgid "" +":guilabel:`Product Category`: decide to which product category the plan " +"applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:73 +msgid "" +":guilabel:`Applicability`: decide how your plan behaves in the widget when " +"creating a new journal" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:73 +msgid "" +"entry. The applicability you set here always overrides the default " +"applicability." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:75 +msgid "Two smart buttons are available in the top-right corner:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:77 +msgid "" +":guilabel:`Subplans`: can be created to have a more complex analytic " +"structure. Click the :guilabel:`Subplans` smart button, and then " +":guilabel:`New` to add a subplan;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:79 +msgid "" +":guilabel:`Analytic Accounts`: to reach the analytic accounts related to the" +" plan." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:82 +msgid "" +"The analytic widget is prefilled based on the applicability, and the " +":ref:`Analytic Distribution Models `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:84 +msgid "Each analytic plan must have at least one analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:87 +msgid "Analytic distribution" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:89 +msgid "" +"Add a plan in the :guilabel:`Analytic` column when creating an invoice or " +"bill. This field is mandatory only if you previously linked your analytic " +"plan to at least one analytic account. After adding the plan, a **widget** " +"opens where you can fill in the different information. You can add **tags** " +"to reflect the related analytic accounts and decide how to split the costs " +"between the accounts by modifying the percentage." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst-1 +msgid "create a distribution template" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:102 +msgid "Analytic distribution models" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:104 +msgid "" +"The analytic distribution models automatically apply a specific distribution" +" based on defined criteria." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:107 +msgid "" +"To create a new analytic distribution model, go to " +":menuselection:`Accounting --> Configuration --> Analytic Distribution " +"Models`, click :guilabel:`New` and set the conditions your model has to meet" +" to automatically apply:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:111 +msgid "" +":guilabel:`Accounts Prefix`: this analytic distribution will apply to all " +"financial accounts sharing the prefix specified;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:113 +msgid "" +":guilabel:`Partner`: select a partner for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:114 +msgid "" +":guilabel:`Partner Category`: this field is not visible by default: add it " +"by clicking on the columns selection button, and tick the :guilabel:`Partner" +" Category` box. Add the partner category for which the analytic distribution" +" will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:117 +msgid "" +":guilabel:`Product`: select a product for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:118 +msgid "" +":guilabel:`Product Category`: this field is not visible by default: add it " +"by clicking on the columns selection button, and tick the :guilabel:`Product" +" Category` box. Select a product category for which the analytic " +"distribution will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:121 +msgid "" +":guilabel:`Analytic`: add the analytic accounts and their distribution;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:122 +msgid "" +":guilabel:`Company`: select a company for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:123 +msgid "" +":guilabel:`Analytic Distribution`: if the above conditions are met, the " +":guilabel:`Analytic plan` defined in this field as well as the distribution " +"to be applied between the different analytic accounts is selected " +"automatically on the entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:128 +msgid "" +"To **mass edit** several entries simultaneously, go to " +":menuselection:`Accounting --> Accounting --> Journal items`, and select the" +" ones that need to be updated. Add the required distribution in the " +":guilabel:`Analytic Distribution` column, and click on the :guilabel:`floppy" +" disk` icon to save. The analytic distribution template pops up, and you can" +" save it for later use." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:3 +msgid "Financial budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:5 +msgid "" +"Managing budgets is an essential part of running a business. Budgets help " +"people become more intentional with how money is spent and direct people to " +"organize and prioritize their work to meet financial goals. They allow the " +"planning of a desired financial outcome and then measure the actual " +"performance against the plan. Odoo manages budgets using both **general** " +"and **analytic accounts**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:13 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Analytics section`, and enable :guilabel:`Budget Management`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:17 +msgid "Budgetary positions" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:19 +msgid "" +"Budgetary positions are lists of accounts for which you want to keep budgets" +" (typically expense or income accounts)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:22 +msgid "" +"To define budgetary positions, go to :menuselection:`Accounting --> " +"Configuration --> Management: Budgetary Positions` and :guilabel:`New`. Add " +"a :guilabel:`Name` to your budgetary position and select the " +":guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one " +"or more accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:28 +msgid "" +"Each budgetary position can have any number of accounts from the chart of " +"accounts, though it must have at least one." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:32 +msgid "Use case" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:34 +msgid "Let’s illustrate this with an example." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:36 +msgid "" +"We just started a project with *Smith & Co*, and we would like to budget the" +" income and expenses of that project. We plan on having a revenue of 1000, " +"and we don’t want to spend more than 700." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:39 +msgid "" +"First, we need to define what accounts relate to our project’s expenses. Go " +"to :menuselection:`Accounting --> Configuration --> Management: Budgetary " +"positions`, and click :guilabel:`New` to add a position. Add the accounts " +"wherein expenses will be booked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:47 +msgid "" +"Let's repeat the steps to create a budgetary position that reflects the " +"revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co revenue" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:54 +msgid "Analytical accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:56 +msgid "" +"Odoo needs to know which costs or expenses are relevant to a specified " +"budget, as the above general accounts may be used for different projects. Go" +" to :menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Accounts` and click :guilabel:`New` to add a new **Analytic " +"Account** called *Smith & Co*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:61 +msgid "" +"The :guilabel:`Plan` field has to be completed. Plans group multiple " +"analytic accounts; they distribute costs and benefits to analyze business " +"performance. **Analytic Plans** can be created or configured by going to " +":menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Plans`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:66 +msgid "" +"When creating a new customer invoice and/or vendor bill, you have to refer " +"to this analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "add analytic accounts in a new invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:73 +msgid "Define the budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:75 +msgid "" +"Let’s set our targets. We specified that we expect to gain 1000 with this " +"project, and we would like not to spend more than 700. Go to " +":menuselection:`Accounting --> Management: Budgets` and click " +":guilabel:`New` to create a new budget for *Smith & Co* project." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:79 +msgid "" +"First, fill in your :guilabel:`Budget Name`. Then, select the " +":guilabel:`Period` wherein the budget is applicable. Next, add the " +":guilabel:`Budgetary Position` you want to track, define the related " +":guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "budget lines display" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:88 +msgid "" +"When recording a planned amount related to expenses, the amount must be " +"negative." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:91 +msgid "Check your budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:93 +msgid "" +"Go to :menuselection:`Accounting --> Management: Budgets` and find the " +"*Smith & Co* Project to see how it evolves according to the expenses or " +"income for the related analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:96 +msgid "" +"The :guilabel:`Practical Amount` evolves when a new journal entry related to" +" your analytic account and an account from your budgetary position is " +"created." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:99 +msgid "" +"The :guilabel:`Theoretical Amount` represents the amount of money you " +"theoretically could have spent or should have received based on the date. " +"For example, suppose your budget is 1200 for 12 months (January to " +"December), and today is 31 of January. In that case, the theoretical amount " +"will be 100 since this is the actual amount that could have been made." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:3 +msgid "Custom reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:5 +msgid "" +"Odoo comes with a powerful and easy-to-use reporting framework. The engine " +"allows you to create new reports, such as **tax reports**, or **balance " +"sheets** and **income statements** with **specific groupings** and " +"**layouts**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:10 +msgid "" +"Activate the :ref:`developer mode ` to access the accounting" +" report creation interface." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:13 +msgid "" +"To create a new report, go to :menuselection:`Accounting --> Configuration " +"--> Management: Accounting Reports`. From here, you can either create a " +":ref:`root report ` or a :ref:`variant `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Accounting reports engine." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:24 +msgid "Root reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:26 +msgid "" +"Root reports can be regarded as generic, neutral accounting reports. They " +"serve as models on which local accounting versions are built. If a report " +"has no root report, it is considered to be a root report itself." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:31 +msgid "" +"A tax report for Belgium and the US would both use the same generic version " +"as a base and adapt it for their domestic regulations." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:34 +msgid "" +"When creating a new root report, you need to create a **menu item** for it. " +"To do so, open the report and then, on that same report, click on " +":menuselection:`Action --> Create Menu Item`. Refresh the page; the report " +"is now available under :menuselection:`Accounting --> Reporting`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:39 +msgid "" +"Cases that require creating a new root report are rare, such as when a " +"country's tax authorities require a new and specific type of report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Create Menu Item button." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:49 +msgid "Variants" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:51 +msgid "" +"Variants are country-specific versions of root reports and, therefore, " +"always refer to a root report. To create a variant, select a generic (root) " +"report in the :guilabel:`Root Report` field when creating a new report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:55 +msgid "" +"When a root report is opened from one of the accounting app's main menus, " +"all its variants are displayed in the variant selector in the top right " +"corner of the view." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:59 +msgid "" +"In the following image, :guilabel:`VAT Report (BE)` is the variant of the " +"root :guilabel:`Generic Tax report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "Report variant selection." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:67 +msgid "Lines" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:69 +msgid "" +"After having created a report (either root or variant), you need to fill it " +"with lines. You can either create a new one by clicking on :guilabel:`Add a " +"line`, or modify an existing line by clicking on it. All lines *require* a " +":guilabel:`Name`, and can have an optional additional :guilabel:`Code` (of " +"your choice) if you wish to use their value in formulas." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Engine lines options." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:79 +msgid "Expressions" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:81 +msgid "" +"Each line can contain one or multiple **expressions**. Expressions can be " +"seen as **sub-variables** needed by a report line. To create an expression, " +"click on :guilabel:`Add a line` *within* a line report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:85 +msgid "" +"When creating an expression, you must attribute a :guilabel:`label` used to " +"refer to that expression. Therefore, it has to be **unique** among the " +"expressions of each line. Both a :guilabel:`Computation Engine` and a " +":guilabel:`Formula` must also be indicated. The **engine** defines how your " +"**formula(s)** and **subformula(s)** are interpreted. It is possible to mix " +"expressions using different computation engines under the same line if you " +"need to." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:92 +msgid "Depending on the engine, :guilabel:`subformulas` may also be required." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:95 +msgid "'Odoo Domain' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:97 +msgid "" +"With this engine, a formula is interpreted as an :ref:`Odoo domain " +"` targeting `account.move.line` objects." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:100 +msgid "" +"The subformula allows you to define how the move lines matching the domain " +"are used to compute the value of the expression:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:104 +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 +msgid "`sum`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:104 +msgid "The result is the sum of all the balances of the matched move lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:108 +msgid "`sum_if_pos`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:107 +msgid "" +"The result is the sum of all the balances of the matched move lines if this " +"amount is positive. Otherwise, it is `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:112 +msgid "`sum_if_neg`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:111 +msgid "" +"The result is the sum of all the balances of the matched move lines if this " +"amount is negative. Otherwise, it is `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:117 +msgid "`count_rows`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:115 +msgid "" +"The result is the number of sub-lines of this expression. If the parent line" +" has a group-by value, this will correspond to the number of distinct " +"grouping keys in the matched move lines. Otherwise, it will be the number of" +" matched move lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:119 +msgid "" +"You can also put a `-` sign at the beginning of the subformula to " +"**reverse** the sign of the result." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Expression line within a line report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:127 +msgid "'Tax Tags' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:129 +msgid "" +"A formula made for this engine consists of a name used to match tax tags. If" +" such tags do not exist when creating the expression, they will be created." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:132 +msgid "" +"When evaluating the expression, the expression computation can roughly be " +"expressed as: **(amount of the move lines with** `+` **tag)** `-` **(amount " +"of the move lines with** `-` **tag)**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:136 +msgid "" +"If the formula is `tag_name`, the engine matches tax tags `+tag_name` and " +"`-tag_name`, creating them if necessary. To exemplify further: two tags are " +"matched by the formula. If the formula is `A`, it will require (and create, " +"if needed) tags `+A` and `-A`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:141 +msgid "'Aggregate Other Formulas' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:143 +msgid "" +"Use this engine when you need to perform arithmetic operations on the " +"amounts obtained for other expressions. Formulas here are composed of " +"references to expressions separated by one of the four basic arithmetic " +"operators (addition `+`, subtraction `-`, division `/`, and multiplication " +"`*`). To refer to an expression, type in its parent line's **code** followed" +" by a period `.` and the expression's **label** (ex. **code.label**)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:149 +msgid "**Subformulas** can be one of the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:153 +msgid "`if_above(CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:152 +msgid "" +"The value of the arithmetic expression will be returned only if it is " +"greater than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:157 +msgid "`if_below(CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:156 +msgid "" +"The value of the arithmetic expression will be returned only if it is lower " +"than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:161 +msgid "`if_between(CUR1(amount1), CUR2(amount2))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:160 +msgid "" +"The value of the arithmetic expression will be returned only if it is " +"strictly between the provided bounds. Otherwise, it will be brought back to " +"the closest bound." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:166 +msgid "`if_other_expr_above(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:164 +msgid "" +"The value of the arithmetic expression will be returned only if the value of" +" the expression denoted by the provided line code and expression label is " +"greater than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:171 +msgid "`if_other_expr_below(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:169 +msgid "" +"The value of the arithmetic expression will be returned only if the value of" +" the expression denoted by the provided line code and expression label is " +"lower than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:173 +msgid "" +"`CUR` is the currency code in capital letters, and `amount` is the amount of" +" the bound expressed in that currency." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:176 +msgid "" +"You can also use the `cross_report` subformula to match an expression found " +"in another report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:179 +msgid "'Prefix of Account Codes' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:181 +msgid "" +"This engine is used to match amounts made on accounts using the prefixes of " +"these accounts' codes as variables in an arithmetic expression." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "Arithmetic expressions can also be a single prefix, such as here." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21 + 10 - 5`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula adds the balances of the move lines made on accounts whose " +"codes start with `21` and `10`, and subtracts the balance of the ones on " +"accounts with the prefix `5`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:193 +msgid "It is also possible to ignore a selection of sub-prefixes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21 + 10\\\\(101, 102) - 5\\\\(57)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula works the same way as the previous example but ignores the " +"prefixes `101`, `102`, and `57`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:200 +msgid "" +"You can apply 'sub-filtering' on **credits and debits** using the `C` and " +"`D` suffixes. In this case, an account will only be considered if its prefix" +" matches, *and* if the total balance of the move lines made on this account " +"is **credit/debit**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:205 +msgid "" +"Account `210001` has a balance of -42 and account `210002` has a balance of " +"25. The formula `21D` only matches the account `210002`, and hence returns " +"25. `210001` is not matched, as its balance is *credit*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:209 +msgid "Prefix exclusions can be mixed with the `C` and `D` suffixes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21D + 10\\\\(101, 102)C - 5\\\\(57)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula adds the balances of the move lines made on accounts whose code" +" starts with `21` *if* it is debit (`D`) and `10` *if* it is credit (`C`), " +"but ignores prefixes `101`, `102`, and subtracts the balance of the ones on " +"accounts with the prefix `5`, ignoring the prefix `57`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:217 +msgid "" +"To match the letter `C` or `D` in a prefix and not use it as a suffix, use " +"an empty exclusion `()`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21D\\\\()`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose code starts with `21D`, regardless of " +"their balance sign." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:223 +msgid "" +"In addition to using code prefixes to include accounts, you can also match " +"them with **account tags**. This is especially useful, for example, if your " +"country lacks a standardized chart of accounts, where the same prefix might " +"be used for different purposes across companies." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(25)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose associated tags contain the one with id " +"*25*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:231 +msgid "" +"If the tag you reference is defined in a data file, an xmlid can be used " +"instead of the id." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose associated tags include the tag denoted " +"by *my_module.my_tag*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:238 +msgid "" +"You can also use arithmetic expressions with tags, possibly combining them " +"with prefix selections." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag) + tag(42) + 10`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"The balances of accounts tagged as *my_module.my_tag* will be summed with " +"those of accounts linked to the tag with ID *42* and accounts with the code " +"prefix `10`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:245 +msgid "`C` and `D` suffixes can be used in the same way with tags." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)C`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts with the tag *my_module.my_tag* and a credit " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:251 +msgid "Prefix exclusion also works with tags." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)\\\\(10)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts with the tag *my_module.my_tag* and a code not" +" starting with `10`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:260 +msgid "'External Value' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:262 +msgid "" +"The 'external value' engine is used to refer to **manual** and **carryover " +"values**. Those values are not stored using `account.move.line`, but with " +"`account.report.external.value`. Each of these objects directly points to " +"the expression it impacts, so very little needs to be done about their " +"selection here." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:267 +msgid "**Formulas** can be one of the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 +msgid "" +"If the result must be the sum of all the external values in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "`most_recent`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "" +"If the result must be the value of the latest external value in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:275 +msgid "In addition, **subformulas** can be used in two ways:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "`rounding=X`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "" +"Replacing `X` with a number instructs to round the amount to X decimals." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:282 +msgid "`editable`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:281 +msgid "" +"Indicates this expression can be edited manually, triggering the display of " +"an icon in the report, allowing the user to perform this action." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:285 +msgid "" +"Manual values are created at the `date_to` currently selected in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:287 +msgid "Both subformulas can be mixed by separating them with a `;`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`editable;rounding=2`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "is a correct subformula mixing both behaviors." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:294 +msgid "'Custom Python Function' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:296 +msgid "" +"This engine is a means for developers to introduce custom computation of " +"expressions on a case-by-case basis. The formula is the name of a **python " +"function** to call, and the subformula is a **key** to fetch in the " +"**dictionary** returned by this function. Use it only if you are making a " +"custom module of your own." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:302 +msgid "Columns" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:304 +msgid "" +"Reports can have an **indefinite number** of columns to display. Each column" +" gets its values from the **expressions** declared on the **lines**. The " +"field :guilabel:`expression_label` of the column gives the label of the " +"expressions whose value is displayed. If a line has no **expression** in " +"that field, then nothing is displayed for it in this column. If multiple " +"columns are required, you must use different **expression** labels." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Columns of report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:314 +msgid "" +"When using the **period comparison** feature found under the " +":guilabel:`Options` tab of an accounting report, all columns are repeated in" +" and for each period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:3 +msgid "Data inalterability check report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:5 +msgid "" +"Tax authorities in some countries require companies to **prove their posted " +"accounting entries are inalterable**, meaning that once an entry has been " +"posted, it can no longer be changed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:8 +msgid "" +"To do so, Odoo can use the **SHA-256 algorithm** to create a unique " +"fingerprint for each posted entry. This fingerprint is called a hash. The " +"hash is generated by taking an entry's essential data (the values of the " +"`date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and " +"`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash" +" function, which then outputs a fixed size (256-bit) string of characters. " +"The hash function is deterministic (:dfn:`the same input always creates the " +"same output`): any minor modification to the original data would completely " +"change the resulting hash. Consequently, the SHA-256 algorithm is often " +"used, among others, for data integrity verification purposes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:17 +msgid "" +"In addition, the previous entry's hash is always added to the next entry to " +"form a **hash chain**. This is used to ensure a new entry is not added " +"afterward between two posted entries, as doing so would break the hash " +"chain." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:22 +msgid "" +"Hashes generated by the SHA-256 algorithm are theoretically not unique, as " +"there is a finite number of possible values. However, this number is " +"exceptionally high: 2²⁵⁶, which is a lot bigger than the number of atoms in " +"the known universe. This is why hashes are considered unique in practice." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:30 +msgid "Lock posted entries with hash" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:32 +msgid "" +"To start using the hashing function, go to :menuselection:`Accounting --> " +"Configuration > Journals`. Open the journal for which you want to activate " +"the feature, go to the :guilabel:`Advanced Settings` tab, and enable " +":guilabel:`Lock Posted Entries with Hash`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:37 +msgid "" +"Once you post an entry on a locked journal, you cannot disable the feature " +"anymore, nor edit any posted entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:43 +msgid "Report download" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:45 +msgid "" +"To download the data inalterability check report, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Reporting` and" +" click on :guilabel:`Download the Data Inalterability Check Report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:48 +msgid "" +"The report's first section is an overview of all your journals and their " +"configuration. Under the inalterability check column, you can see whether or" +" not a journal's posted entries are locked with a hash (V) or not (X). The " +"coverage column tells you when a journal's posted entries started being " +"locked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Configuration report for two journals" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:57 +msgid "" +"The second section gives you the result of the data consistency check for " +"each hashed journal. You can view the first hashed entry and its " +"corresponding hash and the last hashed entry and its corresponding hash." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Data consistency check report for a journal" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:3 +msgid "Intrastat" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 +msgid "" +"Intrastat is the data collection and statistics production system for goods " +"traded among EU member states. It collects data on:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:8 +msgid "" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +msgid "" +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:12 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:15 +msgid "" +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"`_, referring instead to" +" *intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:20 +msgid "" +"`Eurostat Statistics Explained - Glossary: Intrastat " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:26 +msgid "General configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:28 +msgid "" +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the :guilabel:`Customer Invoices` " +"section, tick :guilabel:`Intrastat` and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:35 +msgid "Default transaction codes: invoice and refund" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:37 +msgid "" +"You can set a default :ref:`transaction code ` " +"for all newly created invoice and refund transactions. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select a " +":guilabel:`Default invoice transaction code` and/or a :guilabel:`Default " +"refund transaction code` and then :guilabel:`Save`. The code will be set " +"automatically on all respective invoice lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "Region code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:47 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "" +"If your warehouses are located in more than one region, you can define the " +"region code at the level of each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:63 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:65 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:70 +msgid "Commodity code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:72 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature `_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:75 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:79 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:85 +msgid "Quantity: weight and supplementary unit" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:87 +msgid "" +"Depending on the nature of the goods, it is necessary to specify either the " +"product's weight in kilos (without packaging) or the product's supplementary" +" unit, such as square meter (`m2`), number of items (`p/st`), liter (`l`), " +"or gram (`g`)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:91 +msgid "" +"To add a product's weight or supplementary unit, go to " +":menuselection:`Accounting --> Customers --> Products` and select a product." +" Under the :guilabel:`Accounting` tab, depending on the commodity code set, " +"either fill in the product :guilabel:`Weight` or its " +":guilabel:`Supplementary Units`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:98 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:100 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:106 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:108 +msgid "" +"Once products are properly configured, several settings must be configured " +"on the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:114 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:116 +msgid "" +"Transaction codes are used to identify a transaction's nature. :ref:`Default" +" transaction codes ` can be set for " +"invoice and refund transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "" +"To set a transaction code on an invoice line, create an invoice or a bill, " +"click the columns selection button, tick :guilabel:`Intrastat`, and use the " +"newly-added :guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:134 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "" +"The partner country represents the vendor's country for bills and the " +"customer's country for invoices. It is automatically filled in using the " +"country set in the contact's :guilabel:`Country` field." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:140 +msgid "" +"To edit the partner country manually, create an invoice or a bill, click the" +" :guilabel:`Other Info` tab, and select the :guilabel:`Intrastat Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:146 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:148 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"To add the transport code, create an invoice or a bill, go to the " +":guilabel:`Other info` tab, and select the :guilabel:`Intrastat Transport " +"Mode`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:157 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:159 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:167 +msgid "" +"Two fields from the partner's contact form are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set ` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:172 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:174 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration ` and the " +"information found on the :ref:`products `, " +":ref:`invoices and bills `, and " +":ref:`partners `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:180 +msgid "" +"Export the report as a PDF, XLSX, or XML file to post it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:182 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:184 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:185 +msgid "" +"System, which is a code automatically generated depending on whether the " +"document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:187 +msgid "" +":ref:`Country `, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:189 +msgid ":ref:`Transaction Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:190 +msgid "" +"(If your company is located in Belgium) :ref:`Region Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:191 +msgid ":ref:`Commodity Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:192 +msgid ":ref:`Origin Country `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:193 +msgid ":ref:`Partner VAT `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:194 +msgid ":ref:`Transport Code `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:195 +msgid ":doc:`Incoterm Code <../customer_invoices/incoterms>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:196 +msgid ":ref:`Weight `;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:197 +msgid ":ref:`Supplementary Units `; and" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:198 +msgid "" +":ref:`Value `, which is always expressed in euros even if " +"the original invoice or bill used another currency." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 +msgid "Silverfin integration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:5 +msgid "" +"`Silverfin `_ is a third-party service provider " +"that offers a cloud platform for accountants." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:8 +msgid "" +"Odoo and Silverfin provide an integration to automate the synchronization of" +" data." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:13 +msgid "" +"To configure this integration, you need to input the following data into " +"your Silverfin account:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:15 +msgid "user's email address" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:16 +msgid ":ref:`Odoo API key `" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:17 +msgid "URL of the Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:18 +msgid "name of your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:23 +msgid "Odoo API key" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:25 +msgid "" +"You can create Odoo external API keys either :ref:`for a single database " +"` (hosting: Odoo Online, On-premise, and Odoo.sh) or" +" :ref:`for all databases managed by a single user ` (hosting: Odoo Online)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:30 +msgid "" +"These API keys are personal and provide full access to your user account. " +"Store it securely." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:31 +msgid "" +"You can copy the API key only at its creation. It is not possible to " +"retrieve it later." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:32 +msgid "If you need it again, create a new API key (and delete the old one)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:35 +msgid ":doc:`/developer/reference/external_api`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 +msgid "Per database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:42 +msgid "" +"To add an API key to a **single** database, connect to the database, enable " +"the :ref:`developer mode `, click on the user menu, and then" +" :guilabel:`My Profile` / :guilabel:`Preferences`. Under the " +":guilabel:`Account Security` tab, click on :guilabel:`New API Key`, confirm " +"your password, give a descriptive name to your new key, and copy the API " +"key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for a database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:51 +msgid ":ref:`api/external_api/keys`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:56 +msgid "For all databases (fiduciaries)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:58 +msgid "" +"To add an API key to **all** databases managed by a single user at the same " +"time **(the easiest method for fiduciaries)**, navigate to `Odoo's website " +"`_ and sign in with your administrator account. Next," +" open `your account security settings in developer mode " +"`_, click on :guilabel:`New API " +"Key`, confirm your password, give a descriptive name to your new key, and " +"copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:65 +msgid "" +"Open the `database manager `_ to view all" +" databases that will be linked to the single API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for an Odoo user" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:3 +msgid "Tax carryover" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:5 +msgid "" +"When performing tax reports, the **tax carryover** feature allows carrying " +"amounts from one period to another without creating new entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:8 +msgid "" +"It has been created to meet the legal requirements of specific locations, " +"where amounts must be transferred from period to period (for example, " +"because the total of the line is negative)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:11 +msgid "" +"The feature is activated by default in countries where it is required, such " +"as Belgium, France, and Italy. There is no specific configuration required." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:14 +msgid "" +"Let’s take an example of a Belgian company that created a credit note of 100" +" for one of their customers. The due tax is 21%." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "Illustration with a credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:21 +msgid "" +"In this case, as per local regulation, grid 81 of the tax report may contain" +" a negative amount. But it must be declared to the government as zero, and " +"the negative amount should be carried over to the next period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:25 +msgid "" +"If we go to :menuselection:`Accounting app --> Reporting --> Tax Report`, a " +"pop-up on line 81 explains that the amount will be carried over in the next " +"period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "" +"pop-up message stating the amount will be carried over to the next period" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:32 +msgid "" +"At the time of the tax closing period, the tax report shows that the amount " +"was carried over from the previous period. It also indicates the amount that" +" will be carried over to this line in the next period based on the existing " +"transactions and the carryover from the previous period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "Illustration of the tax return" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:3 +msgid "Tax return (VAT declaration)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:5 +msgid "" +"Companies with a registered :abbr:`VAT (Value Added Tax)` number must submit" +" a **tax return** on a monthly or quarterly basis, depending on their " +"turnover and the registration regulation. A tax return - or VAT return - " +"gives the tax authorities information about the taxable transactions made by" +" the company. The **output tax** is charged on the number of goods and " +"services sold by a business, while the **input tax** is the tax added to the" +" price when goods or services are purchased. Based on these values, the " +"company can calculate the tax amount they have to pay or be refunded." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:14 +msgid "" +"You can find additional information about VAT and its mechanism on this page" +" from the European Commission: `\"What is VAT?\" " +"`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 +msgid "Prerequisites" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:25 +msgid "Tax Return Periodicity" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:27 +msgid "" +"The configuration of the **Tax Return Periodicity** allows Odoo to compute " +"your tax return correctly and also to send you a reminder to never miss a " +"tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:30 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"Under the :guilabel:`Tax Return Periodicity`, you can set:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:33 +msgid "" +":guilabel:`Periodicity`: define here whether you submit your tax return on a" +" monthly or quarterly basis;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:35 +msgid "" +":guilabel:`Reminder`: define when Odoo should remind you to submit your tax " +"return;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:36 +msgid "" +":guilabel:`Journal`: select the journal in which to record the tax return." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure how often tax returns have to be made in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:43 +msgid "" +"This is usually configured during the :doc:`app's initial set up " +"<../get_started>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:48 +msgid "Tax Grids" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:50 +msgid "" +"Odoo generates tax reports based on the :guilabel:`Tax Grids` settings that " +"are configured on your taxes. Therefore, it is crucial to make sure that all" +" recorded transactions use the right taxes. You can see the :guilabel:`Tax " +"Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "see which tax grids are used to record transactions in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:59 +msgid "" +"To configure your tax grids, go to :menuselection:`Accounting --> " +"Configuration --> Taxes`, and open the tax you want to modify. There, you " +"can edit your tax settings, along with the tax grids that are used to record" +" invoices or credit notes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure taxes and their tax grids in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:68 +msgid "" +"Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal" +" localization package ` is installed " +"according to the country you select at the creation of your database." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:75 +msgid "Close a tax period" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:80 +msgid "Tax Lock Date" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:82 +msgid "" +"Any new transaction whose accounting date prior to the :guilabel:`Tax Lock " +"Date` has its tax values moved to the next open tax period. This is useful " +"to make sure that no change can be made to a report once its period is " +"closed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:86 +msgid "" +"Therefore, we recommend locking your tax date before working on your " +":guilabel:`Closing Journal Entry`. This way, other users cannot modify or " +"add transactions that would have an impact on the :guilabel:`Closing Journal" +" Entry`, which can help you avoid some tax declaration errors." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:91 +msgid "" +"To check the current :guilabel:`Tax Lock Date`, or to edit it, go to " +":menuselection:`Accounting --> Accounting --> Actions: Lock Dates`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Lock your tax for a specific period in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:103 +msgid "" +"Once all the transactions involving taxes have been posted for the period " +"you want to report, open your :guilabel:`Tax Report` by going to " +":menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`. " +"Make sure to select the right period you want to declare by using the date " +"filter, this way you can have an overview of your tax report. From this " +"view, you can easily access different formats of your tax report, such as " +"`PDF` and XLSX. These include all the values to report to the tax " +"authorities, along with the amount you have to pay or be refunded." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "download the PDF with your Tax Report in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:115 +msgid "" +"If you forgot to lock your tax date before clicking on :guilabel:`Closing " +"Journal Entry`, then Odoo automatically locks your fiscal period on the same" +" date as the accounting date of your entry. This safety mechanism can " +"prevent some fiscal errors, but it is advised to lock your tax date manually" +" before, as described above." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:117 +#: ../../content/applications/finance/accounting/taxes/retention.rst:42 +msgid ":doc:`../taxes`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:122 +msgid ":doc:`../get_started`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:3 +msgid "Year-end closing" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:5 +msgid "" +"Year-end closing is vital for maintaining financial accuracy, complying with" +" regulations, making informed decisions, and ensuring transparency in " +"reporting." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:11 +msgid "Fiscal years" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:13 +msgid "" +"By default, the fiscal year is set to last 12 months and end on December " +"31st. However, its duration and end date can vary due to cultural, " +"administrative, and economic considerations." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:16 +msgid "" +"To modify these values, go to :menuselection:`Accounting --> Configuration " +"--> Settings`. Under the :guilabel:`Fiscal Periods` section, change the " +":guilabel:`Last Day` field if necessary." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:19 +msgid "" +"If the period lasts *more* than or *less* than 12 months, enable " +":guilabel:`Fiscal Years` and :guilabel:`Save`. Go back to the " +":guilabel:`Fiscal Periods` section and click :guilabel:`➜ Fiscal Years`. " +"From there, click :guilabel:`Create`, give it a :guilabel:`Name`, and both a" +" :guilabel:`Start Date` and :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:25 +msgid "" +"Once the set fiscal period is over, Odoo automatically reverts to the " +"default periodicity, taking into account the value specified in the " +":guilabel:`Last Day` field." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:31 +msgid "Year-end checklist" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:34 +msgid "Before closure" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:36 +msgid "" +"Before closing a fiscal year, ensure first everything is accurate and up-to-" +"date:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:38 +msgid "" +"Make sure all bank accounts are fully :doc:`reconciled " +"<../bank/reconciliation>` up to year-end, and confirm that the ending book " +"balances match the bank statement balances." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:40 +msgid "" +"Verify that all :doc:`customer invoices <../customer_invoices>` have been " +"entered and approved and that there are no draft invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:42 +msgid "" +"Confirm that all :doc:`vendor bills <../vendor_bills>` have been entered " +"and agreed upon." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:43 +msgid "" +"Validate all :doc:`expenses <../../expenses>`, ensuring their accuracy." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:44 +msgid "" +"Corroborate that all :doc:`received payments <../payments>` have been " +"encoded and recorded accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:46 +msgid "Close all :ref:`suspense accounts `." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:47 +msgid "" +"Book all :doc:`depreciation <../vendor_bills/assets>` and :doc:`deferred " +"revenue <../customer_invoices/deferred_revenues>` entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:51 +msgid "Closing a fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:53 +msgid "Then, to close the fiscal year:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:55 +msgid "" +"Run a :ref:`tax report `, and verify that all tax " +"information is correct." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:56 +msgid "" +"Reconcile all accounts on the :ref:`balance sheet `:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:58 +msgid "" +"Update the bank balances in Odoo according to the actual balances found on " +"the bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:59 +msgid "" +"Reconcile all transactions in the cash and bank accounts by running the " +":ref:`aged receivables ` and :ref:`aged payables " +"` reports." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:61 +msgid "" +"Audit all accounts, being sure to fully understand all transactions and " +"their nature, making sure to include loans and fixed assets." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:63 +msgid "" +"Optionally, run :ref:`payments matching ` to validate any" +" open vendor bills and customer invoices with their payments. While this " +"step is optional, it could assist the year-end closing process if all " +"outstanding payments and invoices are reconciled, potentially finding errors" +" or mistakes in the system." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:68 +msgid "" +"Next, the accountant likely verifies balance sheet items and book entries " +"for:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:70 +msgid "year-end manual adjustments," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:71 +msgid "work in progress," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:72 +msgid "depreciation journal entries," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:73 +msgid "loans," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:74 +msgid "tax adjustments," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:75 +msgid "etc." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:77 +msgid "" +"If the accountant is going through the year-end audit, they may want to have" +" paper copies of all balance sheet items (such as loans, bank accounts, " +"prepayments, sales tax statements, etc.) to compare these with the balances " +"in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:82 +msgid "" +"During this process, it is good practice to set a :guilabel:`Journal Entries" +" Lock Date` to the last day (inclusive) of the preceding fiscal year by " +"going to :menuselection:`Accounting --> Accounting --> Lock Dates`. This " +"way, the accountant can be confident that nobody changes the transactions " +"while auditing the books. Users from the *accountant* access group can still" +" create and modify entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:89 +msgid "Current year's earnings" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:91 +msgid "" +"Odoo uses a unique account type called **current year's earnings** to " +"display the amount difference between the **income** and **expenses** " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:95 +msgid "" +"The chart of accounts can only contain one account of this type. By default," +" it is a 999999 account named :guilabel:`Undistributed Profits/Losses`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:98 +msgid "" +"To allocate the current year's earnings, create a miscellaneous entry to " +"book them to any equity account. Once done, confirm whether or not the " +"current year's earnings in the **balance sheet** is correctly reporting a " +"balance of zero. If that is the case, set an :guilabel:`All Users Lock Date`" +" to the last day of the fiscal year by going to :menuselection:`Accounting " +"--> Accounting --> Lock Dates`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:105 +msgid "" +"Setting an :guilabel:`All Users Lock Date` is **irreversible** and cannot be" +" removed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:108 +msgid "" +"A specific year-end closing entry is **optional** in order to close out the " +"**profit and loss statement**. The reports are created in real-time, meaning" +" that the profit and loss statement corresponds directly with the year-end " +"date specified in Odoo. Therefore, any time the **income statement** is " +"generated, the beginning date corresponds with the beginning of the **fiscal" +" year** and all account balances should equal zero." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:7 +msgid "" +"There are numerous types of **taxes**, and their application varies greatly," +" depending mostly on your company's localization. To make sure they are " +"recorded with accuracy, Odoo's tax engine supports all kinds of uses and " +"computations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:16 +msgid "" +"**Default taxes** define which taxes are automatically selected when " +"creating a new product. They are also used to prefill the :guilabel:`Taxes` " +"field when adding a new line on an invoice in :ref:`Accounting Firms " +"` mode." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "" +"Odoo fills out the Tax field automatically according to the Default Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:23 +msgid "" +"To change your **default taxes**, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes --> Default Taxes`, select the " +"appropriate taxes for your default sales tax and purchase tax, and click on " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Define which taxes to use by default on Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:31 +msgid "" +"**Default taxes** are automatically set up according to the country selected" +" at the creation of your database, or when you set up a :ref:`fiscal " +"localization package ` for your company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:38 +msgid "Activate sales taxes from the list view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:40 +msgid "" +"As part of your :ref:`fiscal localization package " +"`, most of your country's sales taxes are " +"already preconfigured on your database. However, only a few taxes are " +"activated by default. To activate taxes relevant to your business, go to " +":menuselection:`Accounting --> Configuration --> Taxes` and enable the " +"toggle button under the :guilabel:`Active` column." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Activate pre-configured taxes in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:53 +msgid "" +"To edit or create a **tax**, go to :menuselection:`Accounting --> " +"Configuration --> Taxes` and open a tax or click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Edition of a tax in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:60 +msgid "Basic options" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:65 +msgid "Tax name" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:67 +msgid "" +"The **tax name** is displayed for backend users in the :guilabel:`Taxes` " +"field in :doc:`sales orders <../../sales/sales>`, :doc:`invoices " +"`, product forms, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:73 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:306 +msgid "Tax computation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:75 +msgid "**Group of Taxes**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:77 +msgid "" +"The tax is a combination of multiple sub-taxes. You can add as many taxes as" +" you want, in the order you want them to be applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:81 +msgid "" +"Make sure that the tax sequence is correct, as the order in which they are " +"may impact the taxes' amounts computation, especially if one of the taxes " +":ref:`affects the base of the subsequent ones `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:85 +msgid "**Fixed**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:87 +msgid "" +"The tax has a fixed amount in the default currency. The amount remains the " +"same, regardless of the sales price." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:91 +msgid "" +"A product has a sales price of $1000, and we apply a $10 *fixed* tax. We " +"then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Product sales price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Price without tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:92 +msgid "Tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Total" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:127 +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "10" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +msgid "1,010.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:100 +msgid "**Percentage of price**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:102 +msgid "" +"The *sales price* is the taxable basis: the tax amount is computed by " +"multiplying the sales price by the tax percentage." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:106 +msgid "" +"A product has a sales price of $1000, and we apply a *10% of Price* tax. We " +"then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:112 +msgid "1,100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:115 +msgid "**Percentage of Price Tax Included**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:117 +msgid "" +"The **total** is the taxable basis: the tax amount is a percentage of the " +"total." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:120 +msgid "" +"A product has a Sales Price of $1000, and we apply a *10% of Price Tax " +"Included* tax. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "1,111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:130 +msgid "**Python code**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:132 +msgid "" +"A tax defined as **Python code** consists of two snippets of Python code " +"that are executed in a local environment containing data such as the unit " +"price, product or partner. :guilabel:`Python Code` defines the amount of the" +" tax, and :guilabel:`Applicable Code` defines if the tax is to be applied. " +"The formula is found at the bottom of the :guilabel:`Definition` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:138 +msgid "" +":guilabel:`Python Code`: `result = price_unit * 0.10` :guilabel:`Applicable " +"Code`: `result = true`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:144 +msgid "Active" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:146 +msgid "Only **active** taxes can be added to new documents." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:149 +msgid "" +"It is not possible to delete taxes that have already been used. Instead, you" +" can deactivate them to prevent future use." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:153 +msgid "" +"This field can be modified from the :ref:`list view " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:158 +msgid "Tax type" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:160 +msgid "" +"The :guilabel:`Tax Type` determines the tax application, which also " +"restricts where it is displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:162 +msgid "**Sales**: Customer invoices, product customer taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:163 +msgid "**Purchase**: Vendor bills, product vendor taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:164 +msgid "**None**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:167 +msgid "" +"You can use :guilabel:`None` for taxes that you want to include in a " +":ref:`Group of Taxes ` but that you do not want to list " +"along with other sales or purchase taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:171 +msgid "Tax scope" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:173 +msgid "" +"The :guilabel:`Tax Scope` restricts the use of taxes to a type of product, " +"either **goods** or **services**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:179 +msgid "Definition tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:181 +msgid "" +"Allocate with precision the amount of the taxable basis or percentages of " +"the computed tax to multiple accounts and tax grids." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Allocate tax amounts to the right accounts and tax grids" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:187 +msgid "**Based On**:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:189 +msgid ":guilabel:`Base`: the price on the invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:190 +msgid ":guilabel:`% of tax`: a percentage of the computed tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:192 +msgid "**Account**: if defined, an additional journal item is recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:193 +msgid "" +"**Tax Grids**: used to generate :doc:`tax reports ` " +"automatically, according to your country's regulations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:199 +msgid "Advanced options tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:204 +msgid "Label on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:206 +msgid "" +"The tax label is displayed on each invoice line in the :guilabel:`Taxes` " +"column. This is visible to *front-end* users on exported invoices, in " +"customer portals, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The label on invoices is displayed on each invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:215 +msgid "Tax group" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:217 +msgid "" +"Select which **tax group** the tax belongs to. The tax group name is the " +"displayed above the **total** line on exported invoices and in customer " +"portals." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:220 +msgid "" +"Tax groups include different iterations of the same tax. This can be useful " +"when you must record the same tax differently according to :doc:`fiscal " +"positions `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The Tax Group name is different from the Label on Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:228 +msgid "" +"In the example above, the :guilabel:`0% EU S` tax for intra-community " +"customers in Europe records the amount on specific accounts and tax grids. " +"However, it remains a 0% tax to the customer. This is why the label " +"indicates :guilabel:`0% EU S`, and the tax group name above the " +":guilabel:`Total` line indicates :guilabel:`VAT 0%`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:234 +msgid "" +"Taxes have three different labels, each one having a specific use. Refer to " +"the following table to see where they are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Name `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Label on Invoice `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Group `" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Backend" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid ":guilabel:`Taxes` column on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Above the :guilabel:`Total` line on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:249 +msgid "Include in analytic cost" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "" +"With this option activated, the tax amount is assigned to the same " +"**analytic account** as the invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:257 +msgid "Included in price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:259 +msgid "" +"With this option activated, the total (including the tax) equals the **sales" +" price**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:261 +msgid "`Total = Sales Price = Computed Tax-Excluded price + Tax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:264 +msgid "" +"A product has a sales price of $1000, and we apply a *10% of Price* tax, " +"which is *included in the price*. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "900.10" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "90.9" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "1,000.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:275 +msgid "" +"If you need to define prices accurately, both tax-included and tax-excluded," +" please refer to the following documentation: :doc:`taxes/B2B_B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:279 +msgid "" +"By default, only the :guilabel:`Tax excluded` column is displayed on " +"invoices. To display the :guilabel:`Tax included` column, click the " +"**dropdown toggle** button and check :guilabel:`Tax incl.`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:288 +msgid "Affect base of subsequent taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:290 +msgid "" +"With this option, the total tax-included becomes the taxable basis for the " +"other taxes applied to the same product." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:293 +msgid "" +"You can configure a new :ref:`group of taxes ` to include" +" this tax or add it directly to a product line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The eco-tax is taken into the basis of the 21% VAT tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:300 +msgid "" +"The order in which you add the taxes on a product line has no effect on how " +"amounts are computed. If you add taxes directly on a product line, only the " +"tax sequence determines the order in which they are applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:304 +msgid "" +"To reorder the sequence, go to :menuselection:`Accounting --> Configuration " +"--> Taxes`, and drag and drop the lines with the handles next to the tax " +"names." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:0 +msgid "The taxes' sequence in Odoo determines which tax is applied first" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:311 +msgid ":doc:`taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:312 +msgid ":doc:`taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:313 +msgid ":doc:`taxes/taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:314 +msgid ":doc:`reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:3 +msgid "B2B (tax excluded) and B2C (tax included) pricing" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:5 +msgid "" +"When working with consumers, prices are usually expressed with taxes " +"included in the price (e.g., in most eCommerce). But, when you work in a B2B" +" environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:9 +msgid "" +"Odoo manages both use cases easily, as long as you register your prices on " +"the product with taxes excluded or included, but not both together. If you " +"manage all your prices with tax included (or excluded) only, you can still " +"easily do sales order with a price having taxes excluded (or included): " +"that's easy." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:15 +msgid "" +"This documentation is only for the specific use case where you need to have " +"two references for the price (tax included or excluded), for the same " +"product. The reason of the complexity is that there is not a symmetrical " +"relationship with prices included and prices excluded, as shown in this use " +"case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:25 +msgid "" +"But for the same use case, if you register the price without taxes on the " +"product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:31 +msgid "" +"So, depending on how you register your prices on the product form, you will " +"have different results for the price including taxes and the price excluding" +" taxes:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:40 +msgid "" +"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You " +"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** " +"Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:45 +msgid "" +"This documentation explains how to handle the very specific use case where " +"you need to handle the two prices (tax excluded and included) on the product" +" form within the same company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:50 +msgid "" +"In terms of finance, you have no more revenues selling your product at 10€ " +"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the " +"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in " +"Belgium, make your customer a favor and set your price at 9.99€ instead of " +"10€. Please note that this does not apply to 20€ or 30€, or other tax rates," +" or a quantity >1. You will also make you a favor since you can manage " +"everything tax excluded, which is less error prone and easier for your " +"salespeople." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:413 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:10 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:65 +msgid "" +"The best way to avoid this complexity is to choose only one way of managing " +"your prices and stick to it: price without taxes or price with taxes " +"included. Define which one is the default stored on the product form (on the" +" default tax related to the product), and let Odoo compute the other one " +"automatically, based on the pricelist and fiscal position. Negotiate your " +"contracts with customers accordingly. This perfectly works out-of-the-box " +"and you have no specific configuration to do." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:73 +msgid "" +"If you can not do that and if you really negotiate some prices with tax " +"excluded and, for other customers, others prices with tax included, you " +"must:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:77 +msgid "" +"always store the default price **tax excluded** on the product form, and " +"apply a tax (price excluded on the product form)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:80 +msgid "" +"create a pricelist with prices in **tax included**, for specific customers" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:83 +msgid "" +"create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:86 +msgid "" +"assign both the pricelist and the fiscal position to customers who want to " +"benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ tax excluded" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, tax included, in our shops or eCommerce " +"website" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:99 +msgid "eCommerce" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:101 +msgid "" +"If you only use B2C or B2B prices on your website, simply select the " +"appropriate setting in the **Website** app settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:104 +msgid "" +"If you have both B2B and B2C prices on a single website, please follow these" +" instructions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:106 +msgid "" +"Activate the :ref:`developer mode ` and go to " +":menuselection:`General Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:108 +msgid "" +"Open either `Technical / Tax display B2B` or `Technical / Tax display B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:109 +msgid "" +"Under the :guilabel:`Users` tab, add the users requiring access to the price" +" type. Add B2C users in the B2C group and B2B users in the B2B group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:113 +msgid "Setting your products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:115 +msgid "" +"Your company must be configured with tax excluded by default. This is " +"usually the default configuration, but you can check your **Default Sale " +"Tax** from the menu :menuselection:`Configuration --> Settings` of the " +"Accounting application." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:123 +msgid "" +"Once done, you can create a **B2C** pricelist. You can activate the " +"pricelist feature per customer from the menu: :menuselection:`Configuration " +"--> Settings` of the Sale application. Choose the option **different prices " +"per customer segment**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:128 +msgid "" +"Once done, create a B2C pricelist from the menu " +":menuselection:`Configuration --> Pricelists`. It's also good to rename the " +"default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:132 +msgid "" +"Then, create a product at 8.26€, with a tax of 21% (defined as tax not " +"included in price) and set a price on this product for B2C customers at 10€," +" from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:141 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:143 +msgid "" +"From the accounting application, create a B2C fiscal position from this " +"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal " +"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax " +"included in price)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:152 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:154 +msgid "" +"Create a quotation from the Sale application, using the " +":menuselection:`Sales --> Quotations` menu. You should have the following " +"result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:161 +msgid "" +"Then, create a quotation but **change the pricelist to B2C and the fiscal " +"position to B2C** on the quotation, before adding your product. You should " +"have the expected result, which is a total price of 10€ for the customer: " +"8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:169 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:172 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:174 +msgid "" +"If you negotiate a contract with a customer, whether you negotiate tax " +"included or tax excluded, you can set the pricelist and the fiscal position " +"on the customer form so that it will be applied automatically at every sale " +"of this customer." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:179 +msgid "" +"The pricelist is in the **Sales & Purchases** tab of the customer form, and " +"the fiscal position is in the accounting tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:182 +msgid "" +"Note that this is error prone: if you set a fiscal position with tax " +"included in prices but use a pricelist that is not included, you might have " +"wrong prices calculated for you. That's why we usually recommend companies " +"to only work with one price reference." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:3 +msgid "Avatax integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:5 +msgid "Avatax is a tax calculation provider that can be integrated in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:10 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:98 +msgid "Credential configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:12 +msgid "" +"To integrate Avatax with Odoo, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes` and add your Avatax credentials in the" +" :guilabel:`Avatax` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:16 +msgid "" +"If you do not yet have credentials, click on :guilabel:`How to Get " +"Credentials`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Configure Avatax settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:25 +msgid "Tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:27 +msgid "" +"The Avatax integration is available on Sale Orders and Invoices with the " +"included Avatax fiscal position." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:30 +msgid "" +"Before using the integration, specify an :guilabel:`Avatax Category` on the " +"product categories." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Specify Avatax Category on products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:36 +msgid "" +"Avatax Categories may be overridden or set on individual products as well." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Override product categories as needed" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:45 +msgid "Address validation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:47 +msgid "" +"Manually validate customer addresses by clicking the :guilabel:`Validate " +"address` link in the customer form view." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Validate customer addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:54 +msgid "" +"If preferred, choose to keep the newly validated address or the original " +"address in the wizard that pops up." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Address validation wizard" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:64 +msgid "Tax calculation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:66 +msgid "" +"Automatically calculate taxes on Odoo quotations and invoices with Avatax by" +" confirming the documents. Alternatively, calculate the taxes manually by " +"clicking the :guilabel:`Compute taxes using Avatax` button while these " +"documents are in draft mode." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:70 +msgid "" +"Use the :guilabel:`Avalara Code` field that's available on customers, " +"quotations, and invoices to cross-reference data in Odoo and Avatax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:74 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 +msgid ":doc:`fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:3 +msgid "Cash basis taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:5 +msgid "" +"Cash basis taxes are due when the payment is made, as opposed to standard " +"taxes that are due when the invoice is confirmed. Reporting your income and " +"expenses to the government based on the cash basis method is mandatory in " +"some countries and under some conditions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:10 +msgid "" +"You sell a product in the 1st quarter of your fiscal year, and the payment " +"is received in the 2nd quarter. Based on the cash basis method, the tax you " +"must pay is for the 2nd quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and under " +"the :guilabel:`Taxes` section, enable :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:19 +msgid "" +"Then, define the :guilabel:`Tax Cash Basis Journal`. Click on the external " +"link button next to the journal to update its default properties such as the" +" :guilabel:`Journal Name`, :guilabel:`Type` or :guilabel:`Short Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "Select your Tax Cash Basis Journal and click on the external link" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:28 +msgid "" +"By default, the journal entries of the :guilabel:`Cash Basis Taxes` journal " +"are named using the :guilabel:`CABA` short code." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:31 +msgid "" +"Once this is done, go to :menuselection:`Accounting --> Configuration --> " +"Accounting: Taxes` to configure your taxes. You can either " +":guilabel:`Create` a new tax or update an existing one by clicking on it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:35 +msgid "" +"The :guilabel:`Account` column reflects the proper transitional accounts to " +"post taxes until the payment is registered." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the account column with a transitional accounts where taxes go until the payment\n" +"is registered" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:43 +msgid "" +"In the :guilabel:`Advanced Options` tab, decide of the :guilabel:`Tax " +"Exigilibity`. Select :guilabel:`Based on Payment`, so the tax is due when " +"the payment of the invoice is received. You can then also define the " +":guilabel:`Cash Basis Transition Account` where the tax amount is recorded " +"as long as the original invoice has not been reconciled." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the Cash Basis Transition Account where taxes amounts go until payment\n" +"reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:54 +msgid "Impact of cash basis taxes on accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:56 +msgid "" +"To illustrate the impact of cash basis taxes on accounting transactions, " +"let's take an example with the sales of a product that costs 1,000$, with a " +"cash basis tax of 15%." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:63 +msgid "" +"The following entries are created in your accounting, and the tax report is " +"currently empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:66 +msgid "**Customer journal (INV)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:70 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:86 +msgid "Receivable $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:72 +msgid "Income $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:74 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:103 +msgid "Temporary tax account $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:77 +msgid "When the payment is then received, it is registered as below :" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:80 +msgid "**Bank journal (BANK)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:84 +msgid "Bank $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:90 +msgid "" +"Once the payment is registered, you can use the :guilabel:`Cash Basis " +"Entries` smart button on the invoice to access them directly." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:93 +msgid "" +"Finally, upon reconciliation of the invoice with the payment, the below " +"entry is automatically created:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:97 +msgid "**Tax Cash Basis Journal (Caba)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:101 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:105 +msgid "Income account $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:107 +msgid "Tax Received $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:110 +msgid "" +"The journal items :guilabel:`Income account` vs. :guilabel:`Income account` " +"are neutral, but they are needed to ensure correct tax reports in Odoo with " +"accurate base tax amounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:113 +msgid "" +"Using a default :guilabel:`Base Tax Received Account` is recommended so your" +" balance is at zero and your income account is not polluted by unnecessary " +"accounting movements. To do so, go to :menuselection:`Configuration --> " +"Settings --> Taxes`, and select a :guilabel:`Base Tax Received Account` " +"under :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:3 +msgid "EU intra-community distance selling" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:5 +msgid "" +"EU intra-community distance selling involves the cross-border trade of goods" +" and services from vendors registered for VAT purposes to individuals (B2C) " +"located in a European Union member state. The transaction is conducted " +"remotely, typically through online platforms, mail orders, telephone, or " +"other means of communication." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:10 +msgid "" +"EU intra-community distance selling is subject to specific VAT rules and " +"regulations. The vendor must charge VAT per the VAT rate applicable in the " +"buyer's country." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:14 +msgid "" +"This remains applicable even if the vendor is located outside of the " +"European Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:19 +msgid "" +"The **EU Intra-community Distance Selling** feature helps you comply with " +"this regulation by creating and configuring new **fiscal positions** and " +"**taxes** based on your company's country. To enable it, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick " +":guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "" +"EU intra-community Distance Selling feature in Odoo Accounting settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:28 +msgid "" +"Whenever you add or modify taxes, you can automatically update your fiscal " +"positions. To do so, go to :menuselection:`Accounting/Invoicing --> Settings" +" --> Taxes --> EU Intra-community Distance Selling` and click on the " +":guilabel:`Refresh tax mapping`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:33 +msgid "" +"We highly recommend checking that the proposed mapping is suitable for the " +"products and services you sell before using it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:42 +msgid "One-Stop Shop (OSS)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:44 +msgid "" +"The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union " +"simplifies VAT collection for **cross-border** sales of goods and services. " +"It primarily applies to business-to-consumer **(B2C)** cases. With the OSS, " +"businesses can register for VAT in their home country and use a single " +"online portal to handle VAT obligations for their sales within the EU. There" +" are **two primary schemes**: the **Union OSS** scheme for cross-border " +"services and the **Import OSS** scheme for goods valued at or below €150." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:876 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 +msgid "Reports" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:54 +msgid "" +"To generate **OSS sales** or **OSS imports** reports and submit them onto " +"the OSS portal, go to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, click :guilabel:`Report: Generic Tax report`, and select either " +":guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click on " +":guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left " +"corner. This generates the currently-opened report in the selected format. " +"Once generated, log into the platform of your competent federal authority to" +" submit it onto the OSS portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "OSS reports view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:65 +msgid "" +"`European Commission: OSS | Taxation and Customs Union " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:3 +msgid "Fiscal positions (tax and account mapping)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:5 +msgid "" +"Default taxes and accounts are set on products and customers to create new " +"transactions on the fly. However, depending on the customers' and providers'" +" localization and business type, using different taxes and accounts for a " +"transaction might be necessary." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:9 +msgid "" +"**Fiscal positions** allow the creation of rules to adapt the taxes and " +"accounts used for a transaction automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:12 +msgid "" +"They can be applied :ref:`automatically `, " +":ref:`manually `, or :ref:`assigned to a partner " +"`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:16 +msgid "" +"Several default fiscal positions are available as part of your :ref:`fiscal " +"localization package `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:25 +msgid "Tax and account mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:27 +msgid "" +"To edit or create a fiscal position, go to :menuselection:`Accounting --> " +"Configuration --> Fiscal Positions`, and open the entry to modify or click " +"on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:30 +msgid "" +"The mapping of taxes and accounts is based on the default taxes and accounts" +" defined in the product form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:33 +msgid "" +"To map to another tax or account, fill out the right column (:guilabel:`Tax " +"to Apply`/ :guilabel:`Account to Use Instead`)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position's tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position's account mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:44 +msgid "To remove a tax, leave the field :guilabel:`Tax to Apply` empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:45 +msgid "" +"To replace a tax with several other taxes, add multiple lines using the same" +" :guilabel:`Tax on Product`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:49 +msgid "" +"The mapping only works with *active* taxes. Therefore, make sure they are " +"active by going to :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:53 +msgid "Application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:58 +msgid "Automatic application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:60 +msgid "" +"To automatically apply a fiscal position following a set of conditions, go " +"to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, open " +"the fiscal position to modify, and tick :guilabel:`Detect Automatically`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:64 +msgid "From there, several conditions can be activated:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:66 +msgid "" +":guilabel:`VAT Required`: the customer's VAT number must be present on their" +" contact form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:67 +msgid "" +":guilabel:`Country Group` and :guilabel:`Country`: the fiscal position is " +"only applied to the selected country or country group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position automatic application settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:75 +msgid "" +"If the :doc:`Verify VAT Numbers ` feature is enabled, any " +"fiscal positions with :guilabel:`VAT required` enabled will require Intra-" +"Community valid VAT numbers to apply automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:78 +msgid "" +"Taxes on **eCommerce orders** are automatically updated once the customer " +"has logged in or filled out their billing details." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:82 +msgid "" +"The fiscal positions' **sequence** defines which fiscal position is applied " +"if all conditions set on multiple fiscal positions are met simultaneously." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:85 +msgid "" +"For example, suppose the first fiscal position in a sequence targets " +"*country A* while the second fiscal position targets a *country group* that " +"comprises *country A*. In that case, only the first fiscal position will be " +"applied to customers from *country A*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:92 +msgid "Manual application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:94 +msgid "" +"To manually select a fiscal position, open a sales order, invoice, or bill, " +"go to the :guilabel:`Other Info` tab and select the desired " +":guilabel:`Fiscal Position` before adding product lines." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Selection of a fiscal position on a sales order, invoice, or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:105 +msgid "Assign to a partner" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:107 +msgid "" +"To define which fiscal position must be used by default for a specific " +"partner, go to :menuselection:`Accounting --> Customers --> Customers`, " +"select the partner, open the :guilabel:`Sales & Purchase` tab, and select " +"the :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Selection of a fiscal position on a customer" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:118 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:3 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:28 +msgid "Withholding taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:5 +msgid "" +"A **withholding tax**, also known as retention tax, mandates the payer of a " +"customer invoice to deduct a tax from the payment and remit it to the " +"government. Typically, a tax is included in the subtotal to calculate the " +"total amount paid, while withholding taxes are directly subtracted from the " +"payment." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:13 +msgid "" +"In Odoo, a withholding tax is defined by creating a negative tax. To create " +"one, go to :menuselection:`Accounting --> Configuration --> Taxes` and, in " +"the :guilabel:`Amount` field, enter a negative amount." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "negative tax amount in field" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:20 +msgid "" +"Then, go to the :menuselection:`Advanced Options` tab and create a retention" +" :guilabel:`Tax Group`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "tax group for retention tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:26 +msgid "" +"If the retention is a percentage of a regular tax, create a :guilabel:`Tax` " +"with a :guilabel:`Tax Computation` as a :guilabel:`Group of Taxes`. Then, " +"set both the regular tax and the retention one in the :guilabel:`Definition`" +" tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:31 +msgid "Retention taxes on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:33 +msgid "" +"Once the retention tax has been created, it can be used on customer forms, " +"sales orders, and customer invoices. Several taxes can be applied on a " +"single customer invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "invoice lines with taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:3 +msgid "TaxCloud integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:6 +msgid "" +"The out-of-the-box Odoo TaxCloud integration has begun its decommissioning. " +"Starting in Odoo 17, new installations are prohibited, and in Odoo 18 the " +"TaxCloud module(s) won't exist at all. Odoo recommends the use of the Avatax" +" platform." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:10 +msgid "" +"If you are hosted on-premise or on Odoo.SH and you wish to use Taxcloud, you" +" can contact them directly `here `_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:14 +msgid ":doc:`avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:3 +msgid "VAT numbers verification (VIES)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:5 +msgid "" +"`VAT Information Exchange System " +"`_, or " +"**VIES**, is a tool provided by the European Commission that allows you to " +"check the validity of VAT numbers for companies registered in the European " +"Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:9 +msgid "" +"Odoo's VAT Validation feature uses the VIES to verify your contacts' VAT " +"numbers directly from Odoo's interface." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:13 +msgid "" +"Regardless of whether or not the Verify VAT Numbers feature is enabled, Odoo" +" checks the format of a contact's VAT against the `expected format of VAT " +"numbers `_ from " +"that country." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:18 +msgid "VIES VAT number verification" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:20 +msgid "" +"To activate this feature, go to :menuselection:`Accounting --> Configuration" +" --> Settings`. In the :guilabel:`Taxes` section, enable the " +":guilabel:`Verify VAT Numbers` feature, and click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:24 +msgid "" +"Once the :guilabel:`Verify VAT Numbers` feature is enabled, if the contact's" +" :guilabel:`Tax ID` field is populated *and* its country is different from " +"your company's country, Odoo displays an :guilabel:`Intra-Community Valid` " +"checkbox. Odoo tests the VAT number through the VIES and automatically " +"checks or unchecks the :guilabel:`Intra-Community Valid` checkbox depending " +"on the validity of the VAT number." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst-1 +msgid "Intra-community valid checkbox on the contact record" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:34 +msgid "" +"It is possible to manually override the :guilabel:`Intra-Community Valid` " +"field on a contact in case the automatic VIES check is incorrect (for " +"example, if the company was recently created and its VAT is not yet in the " +"VIES). This change is logged in the chatter for transparency." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:39 +msgid "" +"Odoo can :ref:`automatically apply fiscal positions " +"`. If the Verify VAT Numbers feature is enabled," +" any fiscal positions with VAT required enabled will require Intra-Community" +" valid VAT numbers to apply automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:279 +msgid "Vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:7 +msgid "" +"In Odoo, we can register vendor bills **manually** or **automatically**, " +"while the **Aged Payable report** provides an overview of all outstanding " +"bills to help us pay the correct amounts on time." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:12 +msgid "" +"Tutorial `Registering a vendor bill " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:13 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:16 +msgid "Bill creation" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:19 +msgid "Manually" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:21 +msgid "" +"Create a vendor bill manually by going to :menuselection:`Accounting --> " +"Vendors --> Bills` and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:25 +msgid "Automatically" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:27 +msgid "" +"Vendor bills can be automatically created by **sending an email** to an " +":ref:`email alias ` associated with the " +"purchase journal, or by **uploading a PDF** in :menuselection:`Accounting " +"--> Vendors --> Bills` and then clicking :guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:32 +msgid "Bill completion" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:34 +msgid "" +"Whether the bill is created manually or automatically, make sure the " +"following fields are appropriately completed:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:37 +msgid "" +":guilabel:`Vendor`: Odoo automatically fills some information based on the " +"vendor's registered information, previous purchase orders, or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:39 +msgid "" +":guilabel:`Bill Reference`: add the sales order reference provided by the " +"vendor and is used to do the :ref:`matching ` when you " +"receive the products." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:41 +msgid "" +":guilabel:`Auto-Complete`: select a past bill/purchase order to " +"automatically complete the document. The :guilabel:`Vendor` field should be " +"completed prior to completing this field." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:43 +msgid ":guilabel:`Bill Date`: is the issuance date of the document." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:44 +msgid "" +":guilabel:`Accounting Date`: is the date on which the document is registered" +" in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:45 +msgid "" +":guilabel:`Payment Reference`: when registering the payment, it is " +"automatically indicated in the :guilabel:`Memo` field." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:47 +msgid "" +":guilabel:`Recipient Bank`: to indicate to which account number the payment " +"has to be made." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:48 +msgid ":guilabel:`Due Date` or :guilabel:`Terms` to pay the bill." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:49 +msgid "" +":guilabel:`Journal`: select in which journal the bill should be recorded and" +" the :doc:`Currency `." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst-1 +msgid "filling the vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:57 +msgid "" +"Bills can be :doc:`digitized ` for " +"automatic completion by clicking :guilabel:`Send for Digitization`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:59 +msgid "" +"If you upload the bill, the PDF document is displayed on the right of the " +"screen, allowing you to easily fill in the bill information." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:63 +msgid "Bill confirmation" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:65 +msgid "" +"Click :guilabel:`Confirm` when the document is completed. The status of your" +" document changes to :guilabel:`Posted` and a journal entry is generated " +"based on the configuration on the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:69 +msgid "" +"Once confirmed, it is no longer possible to update it. Click " +":guilabel:`Reset to draft` if changes are required." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:73 +msgid "Bill Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:75 +msgid "" +"Upon payment of the vendor bill, click on :guilabel:`Register Payment`. A " +"new window pops up." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:77 +msgid "" +"Select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the " +":guilabel:`Amount` you wish to pay (full or partial payment), and the " +":guilabel:`Currency`. Odoo fills the :guilabel:`Memo` field automatically if" +" the :guilabel:`Payment Reference` has been set correctly in the vendor " +"bill. If the field is empty, we recommend you select the vendor invoice " +"number as a reference." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:82 +msgid "" +"Once confirmed, an :guilabel:`In Payment` banner appears on the bill until " +"it is :doc:`reconciled `." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:86 +msgid "Aged payable report" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:88 +msgid "" +"To get an overview of your open vendor bills and their related due dates, " +"you can use the **Aged Payable report**. Go to :menuselection:`Accounting " +"--> Reporting --> Partner Reports: Aged payable`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:92 +msgid "" +"Click on a vendor's name to open up the details of all outstanding bills, " +"the amounts due, the due dates, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:96 +msgid "" +"By clicking the :guilabel:`Save` button, you can export the information " +"available on the screen as a PDF or XLSX file and save it in the folder of " +"your choice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:98 +msgid "" +"You might receive several bills for the same purchase order if your vendor " +"is in back-order and is sending you invoices as they ship the products, or " +"if your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:3 +msgid "Non-current assets and fixed assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:5 +msgid "" +"**Non-current Assets**, also known as **long-term assets**, are investments " +"that are expected to be realized after one year. They are capitalized rather" +" than being expensed and appear on the company's balance sheet. Depending on" +" their nature, they may undergo **depreciation**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:9 +msgid "" +"**Fixed Assets** are a type of Non-current Assets and include the properties" +" bought for their productive aspects, such as buildings, vehicles, " +"equipment, land, and software." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:12 +msgid "" +"For example, let's say we buy a car for $ 27,000. We plan to amortize it " +"over five years, and we will sell it for $ 7,000 afterward. Using the " +"linear, or straight-line, depreciation method, $ 4,000 are expensed each " +"year as **depreciation expenses**. After five years, the **Accumulated " +"Depreciation** amount reported on the balance sheet equals $ 20,000, leaving" +" us with $ 7,000 of **Not Depreciable Value**, or Salvage value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:18 +msgid "" +"Odoo Accounting handles depreciation by creating all depreciation entries " +"automatically in *draft mode*. They are then posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:21 +msgid "Odoo supports the following **Depreciation Methods**:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:23 +msgid "Straight Line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:24 +msgid "Declining" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:25 +msgid "Declining Then Straight Line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 +msgid "" +"The server checks once a day if an entry must be posted. It might then take " +"up to 24 hours before you see a change from *draft* to *posted*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:34 +msgid "" +"Such transactions must be posted on an **Assets Account** rather than on the" +" default expense account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:38 +msgid "Configure an Assets Account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 +msgid "" +"To configure your account in the **Chart of Accounts**, go to " +":menuselection:`Accounting --> Configuration --> Chart of Accounts`, click " +"on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Configuration of an Assets Account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:48 +msgid "" +"This account's type must be either *Fixed Assets* or *Non-current Assets*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:51 +msgid "Post an expense to the right account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:54 +msgid "Select the account on a draft bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:56 +msgid "" +"On a draft bill, select the right account for all the assets you are buying." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:65 +msgid "Choose a different Expense Account for specific products" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:67 +msgid "" +"Start editing the product, go to the *Accounting* tab, select the right " +"**Expense Account**, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Change of the Assets Account for a product in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:75 +msgid "" +"It is possible to :ref:`automate the creation of assets entries ` for these products." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 +msgid "Change the account of a posted journal item" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:83 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, select the journal item you want to modify, " +"click on the account, and select the right one." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Modification of a posted journal item's account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:92 +msgid "Assets entries" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 +msgid "Create a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:99 +msgid "" +"An **Asset entry** automatically generates all journal entries in *draft " +"mode*. They are then posted one by one at the right time." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:102 +msgid "" +"To create a new entry, go to :menuselection:`Accounting --> Accounting --> " +"Assets`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:105 +msgid "" +"Click on **select related purchases** to link an existing journal item to " +"this new entry. Some fields are then automatically filled out, and the " +"journal item is now listed under the **Related Purchase** tab." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets entry in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:113 +msgid "" +"Once done, you can click on *Compute Depreciation* (next to the *Confirm* " +"button) to generate all the values of the **Depreciation Board**. This board" +" shows you all the entries that Odoo will post to depreciate your asset, and" +" at which date." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Depreciation Board in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 +msgid "What does \"Prorata Temporis\" mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:124 +msgid "" +"The **Prorata Temporis** feature is useful to depreciate your assets the " +"most accurately possible." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:126 +msgid "" +"With this feature, the first entry on the Depreciation Board is computed " +"based on the time left between the *Prorata Date* and the *First " +"Depreciation Date* rather than the default amount of time between " +"depreciations." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:130 +msgid "" +"For example, the Depreciation Board above has its first depreciation with an" +" amount of $ 241.10 rather than $ 4,000.00. Consequently, the last entry is " +"also lower and has an amount of $ 3758.90." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:134 +msgid "What are the different Depreciation Methods" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:136 +msgid "" +"The **Straight Line Depreciation Method** divides the initial Depreciable " +"Value by the number of depreciations planned. All depreciation entries have " +"the same amount." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:139 +msgid "" +"The **Declining Depreciation Method** multiplies the Depreciable Value by " +"the **Declining Factor** for each entry. Each depreciation entry has a lower" +" amount than the previous entry. The last depreciation entry doesn't use the" +" declining factor but instead has an amount corresponding to the balance of " +"the depreciable value so that it reaches $0 by the end of the specified " +"duration." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:144 +msgid "" +"The **Declining Then Straight Line Depreciation Method** uses the Declining " +"Method, but with a minimum Depreciation equal to the Straight Line Method. " +"This method ensures a fast depreciation at the beginning, followed by a " +"constant one afterward." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:149 +msgid "Assets from the Purchases Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:151 +msgid "" +"You can create an asset entry from a specific journal item in your " +"**Purchases Journal**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:153 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, and select the journal item you want to " +"record as an asset. Make sure that it is posted in the right account (see: " +":ref:`journal-assets-account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:157 +msgid "" +"Then, click on *Action*, select **Create Asset**, and fill out the form the " +"same way you would do to :ref:`create a new entry `." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Create Asset Entry from a journal item in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:165 +msgid "Modification of an Asset" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:167 +msgid "" +"You can modify the values of an asset to increase or decrease its value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:169 +msgid "" +"To do so, open the asset you want to modify, and click on *Modify " +"Depreciation*. Then, fill out the form with the new depreciation values and " +"click on *Modify*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:172 +msgid "" +"A **decrease in value** posts a new Journal Entry for the **Value Decrease**" +" and modifies all the future *unposted* Journal Entries listed in the " +"Depreciation Board." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:175 +msgid "" +"An **increase in value** requires you to fill out additional fields related " +"to the account movements and creates a new Asset entry with the **Value " +"Increase**. The Gross Increase Asset Entry can be accessed with a Smart " +"Button." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Gross Increase smart button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:184 +msgid "Disposal of Fixed Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:186 +msgid "" +"To **sell** an asset or **dispose** of it implies that it must be removed " +"from the Balance Sheet." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:188 +msgid "" +"To do so, open the asset you want to dispose of, click on *Sell or Dispose*," +" and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Disposal of Assets in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:194 +msgid "" +"Odoo Accounting then generates all the journal entries necessary to dispose " +"of the asset, including the gain or loss on sale, which is based on the " +"difference between the asset's book value at the time of the sale and the " +"amount it is sold for." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:199 +msgid "" +"To record the sale of an asset, you must first post the related Customer " +"Invoice so you can link the sale of the asset with it." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:203 +msgid "Assets Models" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:205 +msgid "" +"You can create **Assets Models** to create your Asset entries faster. It is " +"particularly useful if you recurrently buy the same kind of assets." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:208 +msgid "" +"To create a model, go to :menuselection:`Accounting --> Configuration --> " +"Assets Models`, click on *Create*, and fill out the form the same way you " +"would do to create a new entry." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:212 +msgid "" +"You can also convert a *confirmed Asset entry* into a model by opening it " +"from :menuselection:`Accounting --> Accounting --> Assets` and then, by " +"clicking on the button *Save Model*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:217 +msgid "Apply an Asset Model to a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:219 +msgid "" +"When you create a new Asset entry, fill out the **Fixed Asset Account** " +"with the right asset account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 +msgid "" +"New buttons with all the models linked to that account appear at the top of " +"the form. Clicking on a model button fills out the form according to that " +"model." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets model button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:232 +msgid "Automate the Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:234 +msgid "" +"When you create or edit an account of which the type is either *Non-current " +"Assets* or *Fixed Assets*, you can configure it to create assets for the " +"expenses that are credited on it automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:238 +msgid "You have three choices for the **Automate Assets** field:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:241 +msgid "" +"**Create in draft:** whenever a transaction is posted on the account, a " +"draft *Assets entry* is created, but not validated. You must first fill out " +"the form in :menuselection:`Accounting --> Accounting --> Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:244 +msgid "" +"**Create and validate:** you must also select an Asset Model (see: `Assets " +"Models`_). Whenever a transaction is posted on the account, an *Assets " +"entry* is created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Automate Assets on an account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:252 +msgid "" +"You can, for example, select this account as the default **Expense Account**" +" of a product to fully automate its purchase. (see: :ref:`product-assets-" +"account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 +msgid ":doc:`../get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:3 +msgid "Deferred expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:5 +msgid "" +"**Deferred expenses** and **prepayments** (also known as **prepaid " +"expenses**) are both costs that have already occurred for products or " +"services yet to be received." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:8 +msgid "" +"Such costs are **assets** for the company that pays them since it already " +"paid for products and services but has either not yet received them or not " +"yet used them. The company cannot report them on the current **profit and " +"loss statement**, or *income statement*, since the payments will be " +"effectively expensed in the future." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:13 +msgid "" +"These future expenses must be deferred on the company's balance sheet until " +"the moment in time they can be **recognized**, at once or over a defined " +"period, on the profit and loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:16 +msgid "" +"For example, let's say we pay $1200 at once for one year of insurance. We " +"already pay the cost now but haven't used the service yet. Therefore, we " +"post this new expense in a *prepayment account* and decide to recognize it " +"on a monthly basis. Each month, for the next 12 months, $100 will be " +"recognized as an expense." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:21 +msgid "" +"Odoo Accounting handles deferred expenses by spreading them across multiple " +"entries that are posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:41 +msgid "" +"By default, Odoo :ref:`automatically generates " +"` the deferral entries when " +"you post a vendor bill. However, you can also choose to :ref:`generate them " +"manually ` by selecting the " +":guilabel:`Manually & Grouped` option instead." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:46 +msgid "" +"Suppose a bill of $1200 must be deferred over 12 months. The " +":guilabel:`Equal per month` computation recognizes $100 each month, while " +"the :guilabel:`Based on days` computation recognizes different amounts " +"depending on the number of days in each month." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:56 +msgid "" +"Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are " +"visible in the :guilabel:`Invoice Lines` tab. In most cases, the " +":guilabel:`Start Date` should be in the same month as the :guilabel:`Bill " +"Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:60 +msgid "" +"For each line of the bill that should be deferred, specify the start and end" +" dates of the deferral period." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 +msgid "" +"If the :guilabel:`Generate Entries` field is set to :guilabel:`On " +"invoice/bill validation`, Odoo automatically generates the deferral entries " +"when the bill is validated. Click on the :guilabel:`Deferred Entries` smart " +"button to see them." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:67 +msgid "" +"One entry, dated on the same day as the bill, moves the bill amounts from " +"the expense account to the deferred account. The other entries are deferral " +"entries which will, month after month, move the bill amounts from the " +"deferred account to the expense account to recognize the expense." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:72 +msgid "" +"You can defer a January bill of $1200 over 12 months by specifying a start " +"date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800" +" is recognized as an expense, whereas $400 remains on the deferred account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:79 +msgid "" +"The deferred expense report computes an overview of the necessary deferral " +"entries for each account. To access it, go to :menuselection:`Accounting -->" +" Reporting --> Deferred Expense`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Deferred expense report" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:89 +msgid "" +"Only bills whose accounting date is before the end of the period of the " +"report are taken into account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:102 +msgid "" +"At the end of each month, go to the Deferred Expenses report and click the " +":guilabel:`Generate Entries` button. This generates two deferral entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:105 +msgid "" +"One dated at the end of the month which aggregates, for each account, all " +"the deferred amounts of that month. This means that at the end of that " +"period, a part of the deferred expense is recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:113 +msgid "There are two bills:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:115 +msgid "Bill A: $1200 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 +msgid "Bill B: $600 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:124 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:141 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 +msgid "" +"Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both" +" bills)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:125 +msgid "" +"Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of bill A and " +"bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:142 +msgid "" +"Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of bill A and " +"bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:158 +msgid "" +"Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of bill A " +"and bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:165 +msgid "" +"There is no need to generate entries in December. Indeed, if we do the " +"computation for December, we will have an amount of 0 to be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:171 +msgid "bill A and bill B" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "" +"Therefore, at the end of December, bills A and B are fully recognized as " +"expense only once in spite of all the created entries thanks to the reversal" +" mechanism." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:3 +msgid "AI-powered document digitization" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:5 +msgid "" +"**Invoice digitization** is the process of converting paper documents into " +"vendor bill and customer invoice forms in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:8 +msgid "" +"Odoo uses :abbr:`OCR (optical character recognition)` and artificial " +"intelligence technologies to recognize the content of the documents. Vendor " +"bill and customer invoice forms are automatically created and populated " +"based on the scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:13 +msgid "" +"`Test Odoo's invoice digitization `_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:14 +msgid "" +"`Odoo Tutorials: Invoice Digitization with OCR " +"`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:20 +msgid "" +"In :menuselection:`Accounting --> Configuration --> Settings --> " +"Digitization`, check the box :guilabel:`Document Digitization` and choose " +"whether :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` (this " +"includes customer credit notes) should be processed automatically or on " +"demand." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:25 +msgid "" +"If you enable the :guilabel:`Single Invoice Line Per Tax` option, only one " +"line is created per tax in the new bill, regardless of the number of lines " +"on the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:29 +msgid "Invoice upload" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:32 +msgid "Upload invoices manually" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:34 +msgid "" +"From the :guilabel:`Accounting Dashboard`, click on the :guilabel:`Upload` " +"button of your vendor bills journal. Alternatively, go to " +":menuselection:`Accounting --> Customers --> Invoices` or " +":menuselection:`Accounting --> Vendors --> Bills` and select " +":guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:42 +msgid "Upload invoices using an email alias" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:44 +msgid "" +"You can configure your connected scanner to send scanned documents to an " +"email alias. Emails sent to these aliases are converted into new draft " +"customer invoices or vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:47 +msgid "" +"You can modify the email alias of a journal. To do so, go to the " +":guilabel:`Settings` app. Under :guilabel:`General Settings: Discuss`, " +"enable :guilabel:`Custom Email Servers`, add an :guilabel:`Alias Domain`, " +"and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:51 +msgid "" +"The email alias is now available in the :guilabel:`Advanced Settings` tab of" +" the journal. Emails sent to this address will be converted automatically " +"into new invoices or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:55 +msgid "" +"If you use the :doc:`Documents <../../documents>` app, you can automatically" +" send your scanned invoices to the :guilabel:`Finance` workspace (e.g., " +"`inbox-financial@example.odoo.com`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:58 +msgid "" +"The default email aliases `vendor-bills@` and `customer-invoices@` followed " +"by the :guilabel:`Alias Domain` you set are automatically created for the " +":guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` journals, " +"respectively. Emails sent to these addresses are converted automatically " +"into new invoices or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:63 +msgid "" +"To change a default email alias, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`. Select the journal you want to " +"edit, click on the :guilabel:`Advanced Settings` tab, and edit the `Email " +"Alias`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:68 +msgid "Invoice digitization" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:70 +msgid "" +"According to your settings, the document is either processed automatically, " +"or you need to click on :guilabel:`Send for digitization` to do it manually." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:73 +msgid "" +"Once the data is extracted from the PDF, you can correct it if necessary by " +"clicking on the respective tags (available in :guilabel:`Edit` mode) and " +"selecting the proper information instead." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:77 +msgid "Data recognition with AI" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:79 +msgid "" +"It is essential to review and correct (if needed) the information uploaded " +"during digitization. Then, you have to post the document by clicking on " +":guilabel:`Confirm`. In this manner, the AI learns, and the system " +"identifies the correct data for future digitizations." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:86 +msgid "" +"The **invoice digitization** is an In-App Purchase (IAP) service that " +"requires prepaid credits to work. Digitizing one document consumes one " +"credit." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:89 +msgid "" +"To buy credits, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to " +":menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My " +"Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:98 +msgid "`Our Privacy Policy `_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:99 +msgid ":doc:`/applications/general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:3 +msgid "Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:5 +msgid "" +"**Odoo Documents** allows you to store, view, and manage files within Odoo." +msgstr "" + +#: ../../content/applications/finance/documents.rst:7 +msgid "" +"You can upload any file (max 64MB per file on Odoo Online) and organize them" +" in various workspaces." +msgstr "" + +#: ../../content/applications/finance/documents.rst:10 +msgid "`Odoo Documents: product page `_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:11 +msgid "" +"`Odoo Tutorials: Documents basics [video] " +"`_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:13 +msgid "" +"`Odoo Tutorials: Using Documents with your Accounting App [video] " +"`_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:18 +msgid "" +"By going to :menuselection:`Documents --> Configuration --> Settings`, you " +"can enable the centralization of files attached to a specific area of your " +"activity. For example, by ticking :guilabel:`Human Resources`, your HR " +"documents are automatically available in the HR workspace, while documents " +"related to Payroll are automatically available in the Payroll sub-workspace " +". You can change the default workspace using the dropdown menu and edit its " +"properties by clicking the internal link button (:guilabel:`➔`)." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "" +"Enable the centralization of files attached to a specific area of your " +"activity." +msgstr "" + +#: ../../content/applications/finance/documents.rst:29 +msgid "" +"If you enable the centralization of your accounting files and documents, it " +"is necessary to click on :guilabel:`Journals` and define each journal " +"independently to allow automatic synchronization." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "Enable the centralization of files attached to your accounting." +msgstr "" + +#: ../../content/applications/finance/documents.rst:36 +msgid "" +"If you select a new workspace, existing documents aren't moved. Only newly " +"created documents will be found under the new workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:40 +msgid "Workspaces" +msgstr "" + +#: ../../content/applications/finance/documents.rst:42 +msgid "" +"Workspaces are hierarchical folders having their own set of tags and " +":ref:`actions `. Default workspaces exist, but " +"you can create your own by going to :menuselection:`Documents --> " +"Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page," +" fill in the following information:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:47 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:48 +msgid "" +":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select " +"its :guilabel:`Parent Workspace`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:54 +msgid "" +"Tags are used within workspaces to add a level of differentiation between " +"documents. They are organized per category, and filters can be used to sort " +"them." +msgstr "" + +#: ../../content/applications/finance/documents.rst:57 +msgid "" +"Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a " +"line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." +msgstr "" + +#: ../../content/applications/finance/documents.rst:61 +msgid "" +"The tags of a parent workspace apply to the child workspaces automatically;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:62 +msgid "" +"Tags can be created and modified by going to :menuselection:`Configuration " +"--> Tags`;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:63 +msgid "" +"Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` " +"on the left menu." +msgstr "" + +#: ../../content/applications/finance/documents.rst:66 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/finance/documents.rst:68 +msgid "" +"To manage your workspace access rights, go to :menuselection:`Documents --> " +"Configuration --> Workspaces`, open the workspace you want to edit, and go " +"to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` " +"that can view, create, and edit the workspace's documents. You can also add " +":guilabel:`Read Groups` that can only view the workspace's documents." +msgstr "" + +#: ../../content/applications/finance/documents.rst:74 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/india.rst:18 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +msgid "Description" +msgstr "" + +#: ../../content/applications/finance/documents.rst:76 +msgid "" +"You can add descriptive information to your workspace by going to " +":menuselection:`Documents --> Configuration --> Workspaces`, opening the " +"workspace you want to describe and going to the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/finance/documents.rst:81 +msgid "" +"Workspaces can also be created and edited by clicking the gear icon " +":guilabel:`⚙` on the left menu." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "Create sub-workspaces from the left menu" +msgstr "" + +#: ../../content/applications/finance/documents.rst:88 +msgid "Documents management" +msgstr "" + +#: ../../content/applications/finance/documents.rst:90 +msgid "" +"When selecting or opening a document, the right panel displays different " +"options. On the top, additional options might be available: " +":guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, " +":guilabel:`Lock` or :guilabel:`Split`. It is also possible to " +":guilabel:`Open chatter` or :guilabel:`Archive` the document." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "right panel options" +msgstr "" + +#: ../../content/applications/finance/documents.rst:99 +msgid "" +"Then, you can modify the name of your file by clicking on " +":guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be " +"assigned. The related :guilabel:`Workspace` can be modified and it is " +"possible to access the related :guilabel:`Journal Entry` or add " +":guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:105 +msgid "" +"The :guilabel:`Contact` is the person related to the document and assigned " +"to it. He can only view the document and not modify it. I.e.: an existing " +"supplier in your database is the contact for their bill." +msgstr "" + +#: ../../content/applications/finance/documents.rst:108 +msgid "" +"The person who creates a document is, by default :guilabel:`Owner` of it and" +" has complete rights to it. It is possible to replace the owner of a " +"document. I.e., an employee must be owner of a document to be able to see it" +" in \"My Profile\"." +msgstr "" + +#: ../../content/applications/finance/documents.rst:112 +msgid "" +"Different :ref:`Actions ` are available at the " +"bottom of the right panel, depending on the workspace where your document is" +" stored." +msgstr "" + +#: ../../content/applications/finance/documents.rst:116 +msgid "Split PDF documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:118 +msgid "" +"Select the PDF you want to split, and click the scissors icon. A new view " +"displays all the pages of the document." +msgstr "" + +#: ../../content/applications/finance/documents.rst:121 +msgid "" +"By default, each page of the document will be split when clicking " +":guilabel:`Split`. To remove a split between two pages, click on the " +"scissors icon." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "split your documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:128 +msgid "" +"To merge documents from your dashboard, select them and click the scissors " +"icon. Click on the scissors between the two documents and click " +":guilabel:`Split` to merge the documents." +msgstr "" + +#: ../../content/applications/finance/documents.rst:132 +#: ../../content/applications/finance/payment_providers.rst:175 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/finance/documents.rst:134 +msgid "" +"Select a workspace and click the arrow next to the :guilabel:`Upload` button" +" to access additional features:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:138 +msgid "Request" +msgstr "" + +#: ../../content/applications/finance/documents.rst:140 +msgid "" +"You can create \"missing documents\" and organize them as documents, to " +"remind users to download them." +msgstr "" + +#: ../../content/applications/finance/documents.rst:142 +msgid "" +"Select the workspace where the file should be stored, click " +":guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document " +"Name`, select the person you need it from in the :guilabel:`Request To` " +"field, fill in the :guilabel:`Due Date In`, confirm the " +":guilabel:`Workspace`, the document should belong to, and add " +":guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click " +":guilabel:`Request`. A placeholder for the missing document is created in " +"the workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:149 +msgid "When your document is available, click the placeholder to upload it." +msgstr "" + +#: ../../content/applications/finance/documents.rst:151 +msgid "" +"You can see all missing documents by going to the **Activity** view and to " +"the :guilabel:`Requested Document` column." +msgstr "" + +#: ../../content/applications/finance/documents.rst:155 +msgid "" +"From the :guilabel:`Activity` view, you can send a **reminder email** to " +"users from whom you are expecting a document. Go to the :guilabel:`Requested" +" Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:159 +msgid "" +"Click on a date to see the details of a specific request. You can update it " +"by clicking on the pen icon, :guilabel:`Preview` the content of the reminder" +" email, or :guilabel:`Send Now` to send a reminder email." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "send a reminder email from the Activity view" +msgstr "" + +#: ../../content/applications/finance/documents.rst:167 +msgid "Add a link" +msgstr "" + +#: ../../content/applications/finance/documents.rst:169 +msgid "" +"To add a link to your documents dashboard, click on :guilabel:`Add a Link`, " +"enter the :guilabel:`URL`, and :guilabel:`Name` it." +msgstr "" + +#: ../../content/applications/finance/documents.rst:173 +msgid "Share" +msgstr "" + +#: ../../content/applications/finance/documents.rst:175 +msgid "" +"You can create a share link to a document or all documents of a workspace. " +"It allows anyone to download the file(s) or upload files to a workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:178 +msgid "" +"To do so, select the workspace or the document and click the arrow next to " +"the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the " +"share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with " +"anyone. :guilabel:`Name` the share link and set a validity date for the URL " +"by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include" +" Sub Folders` box if you also want to share a workspace's sub-folders. To " +"let users upload their own documents, select :guilabel:`Download and " +"Upload`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:186 +msgid "" +"It is possible to only share one or more documents (without their workspace)" +" by selecting them and clicking :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:190 +msgid "New spreadsheet" +msgstr "" + +#: ../../content/applications/finance/documents.rst:192 +msgid "" +"To create a new :doc:`spreadsheet `, click :guilabel:`New " +"Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an " +":doc:`existing template `." +msgstr "" + +#: ../../content/applications/finance/documents.rst:198 +msgid "Workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:200 +msgid "" +"Workflow actions help manage documents and overall business operations. " +"These are automated actions that can be created and customized for each " +"workspace. With a single click you can, for example, create, move, sign, and" +" add tags to a document, and process bills." +msgstr "" + +#: ../../content/applications/finance/documents.rst:204 +msgid "" +"These workflow actions appear on the right panel when a document meets the " +"set criteria." +msgstr "" + +#: ../../content/applications/finance/documents.rst:207 +msgid "Create workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:209 +msgid "" +"To create workflow actions, go to :menuselection:`Documents --> " +"Configuration --> Actions` and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:213 +msgid "" +"An action applies to all **sub-workspaces** under the :guilabel:`Related " +"Workspace` you selected." +msgstr "" + +#: ../../content/applications/finance/documents.rst:216 +msgid "Set the conditions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:218 +msgid "" +"You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one." +" You can define the :guilabel:`Action Name` and then set the conditions that" +" trigger the appearance of the action button (:guilabel:`▶`) on the right-" +"side panel when selecting a file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:222 +msgid "There are three basic types of conditions you can set:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:224 +msgid "" +":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does " +"not contain` conditions, meaning the files *must have* or *mustn't have* the" +" tags set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:227 +msgid "" +":guilabel:`Contact`: the files must be associated with the contact set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:229 +msgid "" +":guilabel:`Owner`: the files must be associated with the owner set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's basic condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:235 +msgid "" +"If you don't set any conditions, the action button appears for all files " +"inside the selected workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:239 +msgid "Advanced condition type: domain" +msgstr "" + +#: ../../content/applications/finance/documents.rst:242 +msgid "" +"It is recommended to have some knowledge of Odoo development to configure " +"*Domain* filters properly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:245 +msgid "" +"The :ref:`developer mode ` needs to be activated to access " +"the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once " +"done, select the :guilabel:`Domain` condition type and click :guilabel:`Add " +"condition`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:249 +msgid "" +"To create a rule, you typically select a :guilabel:`field`, an " +":guilabel:`operator`, and a :guilabel:`value`. For example, if you want to " +"add a workflow action to all the PDF files inside a workspace, set the " +":guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, " +"and the pdf :guilabel:`value`." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's domain condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:257 +msgid "" +"Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add" +" conditions and sub-conditions. You can then specify if your rule should " +"match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the " +"rule directly using the :guilabel:`Code editor`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:262 +msgid "Configure the actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:264 +msgid "" +"Select the :guilabel:`Actions` tab to set up your action. You can " +"simultaneously:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:266 +msgid "" +"**Set Contact**: add a contact to the file, or replace an existing contact " +"with a new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:267 +msgid "" +"**Set Owner**: add an owner to the file, or replace an existing owner with a" +" new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:268 +msgid "**Move to Workspace**: move the file to any workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:269 +msgid "" +"**Create**: create one of the following items attached to the file in your " +"database:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:271 +msgid "" +"**Link to record**: link the document to a record (i.e. link to a vehicle in" +" Fleet);" +msgstr "" + +#: ../../content/applications/finance/documents.rst:272 +msgid "**Product template**: create a product you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:273 +msgid "**Task**: create a Project task you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:274 +msgid "**Signature PDF template**: create a new Sign template to send out;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:275 +msgid "**PDF to sign**: create a PDF to sign;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:276 +msgid "**Applicant**: create a new HR application you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:277 +msgid "" +"**Vendor bill**: create a vendor bill using OCR and AI to scrape information" +" from the file content;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:279 +msgid "" +"**Customer invoice**: create a customer invoice using OCR and AI to scrape " +"information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:281 +msgid "" +"**Vendor credit note**: create a vendor credit note using OCR and AI to " +"scrape information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:283 +msgid "" +"**Credit note**: create a customer credit note using OCR and AI to scrape " +"information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:285 +msgid "" +"**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous " +"Operations` in Accounting;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:287 +msgid "**Bank Statement**: create a Bank Statement in Finance;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:288 +msgid "" +"**Expense**: create an expense automatically based on a file's content." +msgstr "" + +#: ../../content/applications/finance/documents.rst:290 +msgid "**Set Tags**: add, remove, and replace any number of tags." +msgstr "" + +#: ../../content/applications/finance/documents.rst:291 +msgid "" +"**Activities - Mark all as Done**: mark all activities linked to the file as" +" done." +msgstr "" + +#: ../../content/applications/finance/documents.rst:292 +msgid "" +"**Activities - Schedule Activity**: create a new activity linked to the file" +" as configured in the action. You can choose to set the activity on the " +"document owner." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:299 +msgid "Digitize documents with AI and optical character recognition (OCR)" +msgstr "" + +#: ../../content/applications/finance/documents.rst:301 +msgid "" +"Documents available in the Finance workspace can be digitized. Select the " +"document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create " +"Customer Invoice`, or :guilabel:`Create credit note`, and then click " +":guilabel:`Send for Digitization`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:306 +msgid "" +":doc:`AI-powered document digitization " +"<../finance/accounting/vendor_bills/invoice_digitization>`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:5 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:104 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:107 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:110 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:113 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:7 +msgid "" +"Odoo **Expenses** streamlines the management of expenses. After an employee " +"submits their expenses in Odoo, the expenses are reviewed by management and " +"accounting teams. Once approved, payments can then be processed and " +"disbursed back to the employee for reimbursement(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:12 +msgid "`Odoo Expenses: product page `_" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:15 +msgid "Set expense categories" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:17 +msgid "" +"The first step to track expenses is to configure the different types of " +"expenses for the company (managed as *expense categories* in Odoo). Each " +"category can be as specific or generalized as needed. Go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories` to " +"view the current expensable categories in a default list view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Set expense costs on products." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:26 +msgid "" +"To create a new expense category, click :guilabel:`New`. A product form will" +" appear, with the description field labeled :guilabel:`Product Name`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:30 +msgid "" +"Expense categories are managed like products in Odoo. The expense category " +"form follows the standard product form in Odoo, and the information entered " +"is similar. Expense products will be referred to as expense categories " +"throughout this document since the main menu refers to these as " +":guilabel:`Expense Categories`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:35 +msgid "" +"Only two fields are required, the :guilabel:`Product Name` and the " +":guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the " +"field, and select the :guilabel:`Unit of Measure` from the drop-down menu " +"(most products will be set to :guilabel:`Units`)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:40 +msgid "" +"The *Sales* app is where specification on the units of measure are created " +"and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales " +"app --> Configuration --> Settings` and ensure `Units of Measure` is enabled" +" in the `Product Catalog` section. Click on the :guilabel:`Units of Measure`" +" internal link to :doc:`view, create, and edit the units of measure " +"<../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:50 +msgid "" +"The :guilabel:`Cost` field on the product form is populated with a value of " +"`0.00` by default. When a specific expense should always be reimbursed for a" +" particular price, enter that amount in the :guilabel:`Cost` field. " +"Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will " +"report the actual cost when submitting an expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:56 +msgid "" +"The :guilabel:`Cost` field is always visible on the expense category form, " +"but the :guilabel:`Sales Price` field is *only* visible if the " +":guilabel:`Sales Price` is selected under the :guilabel:`Re-Invoice " +"Expenses` section. Otherwise, the :guilabel:`Sales Price` field is hidden." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:62 +msgid "" +"Here are some examples for when to set a specific :guilabel:`Cost` on a " +"product vs. leaving the :guilabel:`Cost` at `0.00`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:65 +msgid "" +"**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense for a meal, they enter the actual amount of the bill and will be " +"reimbursed for that amount. An expense for a meal costing $95.23 would equal" +" a reimbursement for $95.23." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:68 +msgid "" +"**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an " +"expense for \"mileage\", they enter the number of miles driven in the " +":guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. " +"An expense for 100 miles would equal a reimbursement for $30.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:72 +msgid "" +"**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee " +"logs an expense for \"monthly parking\", the reimbursement would be for " +"$75.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:74 +msgid "" +"**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense that is not a meal, mileage, or monthly parking, they use the " +"generic :guilabel:`Expenses` product. An expense for a laptop costing " +"$350.00 would be logged as an :guilabel:`Expenses` product, and the " +"reimbursement would be for $350.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:79 +msgid "" +"Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It" +" is recommended to check with the accounting department to determine the " +"correct account to reference in this field as it will affect reports." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:83 +msgid "" +"Set a tax on each product in the :guilabel:`Vendor Taxes` and " +":guilabel:`Customer Taxes` fields, if applicable. It is considered good " +"practice to use a tax that is configured with :ref:`Tax Included in Price " +"`. Taxes will be automatically configured if this " +"is set." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:90 +msgid "Record expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:93 +msgid "Manually create a new expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:95 +msgid "" +"To record a new expense, begin in the main :menuselection:`Expenses` app " +"dashboard, which presents the default :guilabel:`My Expenses` view. This " +"view can also be accessed from :menuselection:`Expenses app --> My Expenses " +"--> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:99 +msgid "" +"First, click :guilabel:`New`, and then fill out the various fields on the " +"form." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:101 +msgid "" +":guilabel:`Description`: Enter a short description for the expense in the " +":guilabel:`Description` field. This should be short and informative, such as" +" `lunch with client` or `hotel for conference`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:104 +msgid "" +":guilabel:`Category`: Select the expense category from the drop-down menu " +"that most closely corresponds to the expense. For example, an airplane " +"ticket would be appropriate for an expense :guilabel:`Category` named " +":guilabel:`Air Travel`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:107 +msgid "" +":guilabel:`Total`: Enter the total amount paid for the expense in one of two" +" ways:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:109 +msgid "" +"If the expense is for one single item/expense, and the category selected was" +" for a single item, enter the cost in the :guilabel:`Total` field (the " +":guilabel:`Quantity` field is hidden)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:111 +msgid "" +"If the expense is for multiples of the same item/expense with a fixed price," +" the :guilabel:`Unit Price` is displayed. Enter the quantity in the " +":guilabel:`Quantity` field, and the total cost is automatically updated with" +" the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = " +"the total). Be advised, the word \"total\" does not appear, the total cost " +"simply appears below the :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:118 +msgid "" +"For example, in the case of mileage driven, the :guilabel:`Unit Price` is " +"populated as the cost *per mile*. Set the :guilabel:`Quantity` to the " +"*number of miles* driven, and the total is calculated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:122 +msgid "" +":guilabel:`Included Taxes`: If taxes were configured on the expense " +"category, the tax percentage and amount appear automatically after entering " +"either the :guilabel:`Total` or the :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:127 +msgid "" +"When a tax is configured on an expense category, the :guilabel:`Included " +"Taxes` value will update in real time as the :guilabel:`Total` or " +":guilabel:`Quantity` is updated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:130 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee this " +"expense is for." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:131 +msgid "" +":guilabel:`Paid By`: Click the radio button to indicate who paid for the " +"expense and should be reimbursed. If the employee paid for the expense (and " +"should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the " +"company paid directly instead (e.g. if the company credit card was used to " +"pay for the expense) select :guilabel:`Company`. Depending on the expense " +"category selected, this field may not appear." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:136 +msgid "" +":guilabel:`Bill Reference`: If there is any reference text that should be " +"included for the expense, enter it in this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:138 +msgid "" +":guilabel:`Expense Date`: Using the calendar module, enter the date the " +"expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)`" +" arrows to navigate to the correct month, then click on the specific day to " +"enter the selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:141 +msgid "" +":guilabel:`Account`: Select the expense account that this expense should be " +"logged on from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:143 +msgid "" +":guilabel:`Customer to Reinvoice`: If the expense is something that should " +"be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer " +"that will be invoiced for this expense from the drop-down menu. All sales " +"orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well " +"as the company the sales order is written for, but after the expense is " +"saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is" +" visible on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:150 +msgid "" +"A customer wishes to have an on-site meeting for a custom garden (design and" +" installation) and agrees to pay for the expenses associated with it (such " +"as travel, hotel, meals, etc.). All expenses tied to that meeting would " +"indicate the sales order for the custom garden (which also references the " +"customer) as the :guilabel:`Customer to Reinvoice`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:155 +msgid "" +":guilabel:`Analytic Distribution`: Select the account(s) the expense should " +"be written against from the drop-down menu for either :guilabel:`Projects`, " +":guilabel:`Departments`, or both. Multiple accounts can be listed for each " +"category if needed. Adjust the percentage for each analytic account by " +"typing in the percentage value next to the account." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:159 +msgid "" +":guilabel:`Company`: If multiple companies are set up, select the company " +"this expense should be filed for from the drop-down menu. The current " +"company will automatically populate this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:161 +msgid "" +":guilabel:`Notes...`: If any notes are needed in order to clarify the " +"expense, enter them in the notes field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "A filled in expense form for a client lunch." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:169 +msgid "Attach a receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:171 +msgid "" +"After the expense is created, the next step is to attach a receipt. Click " +"the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate" +" to the receipt to be attached, and click :guilabel:`Open`. The new receipt " +"is recorded in the chatter, and the number of receipts will appear next to " +"the :guilabel:`📎 (paperclip)` icon beneath the expense form. More than one " +"receipt can be attached to an individual expense, as needed. The number of " +"receipts attached to the expense will be noted on the paperclip icon." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Attach a receipt and it appears in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:183 +msgid "Create new expenses from a scanned receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:185 +msgid "" +"Rather than manually inputting all of the information for an expense, " +"expenses can be created by scanning a PDF receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:188 +msgid "" +"First, in the main :guilabel:`Expenses` app dashboard view (this view can " +"also be accessed from :menuselection:`Expenses app --> My Expenses --> My " +"Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to" +" the receipt to be uploaded, click on it to select it, and then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" +"view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:198 +msgid "" +"The receipt is scanned, and a new entry is created with today's date as the " +":guilabel:`Expense Date`, and any other fields it can populate based on the " +"scanned data, such as the total. Click on the new entry to open the " +"individual expense form, and make any changes needed. The scanned receipt " +"appears in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:204 +msgid "Automatically create new expenses from an email" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:206 +msgid "" +"Instead of individually creating each expense in the *Expenses* app, " +"expenses can be automatically created by sending an email to an email alias." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:209 +msgid "" +"To do so, first, an email alias needs to be configured. Go to " +":menuselection:`Expenses app --> Configuration --> Settings`. Ensure " +":guilabel:`Incoming Emails` is enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Create the domain alias by clicking the link." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:217 +msgid "" +"If the domain alias needs to be set up, :guilabel:`Setup your domain alias` " +"will appear beneath the incoming emails check box instead of the email " +"address field. Refer to this documentation for setup instructions and more " +"information: :doc:`/administration/maintain/domain_names`. Once the domain " +"alias is configured, the email address field will be visible beneath the " +"incoming emails section." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:223 +msgid "" +"Next, enter the email address to be used in the email field, and then click " +":guilabel:`Save`. Now that the email address has been entered, emails can be" +" sent to that alias to create new expenses without having to be in the Odoo " +"database." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:227 +msgid "" +"To submit an expense via email, create a new email and enter the product's " +"*internal reference* code (if available) and the amount of the expense in " +"the email subject. Next, attach the receipt to the email. Odoo creates the " +"expense by taking the information in the email subject and combining it with" +" the receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:232 +msgid "" +"To check an expense categories internal reference, go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`. If " +"an internal reference is listed on the expense category, it is listed in the" +" :guilabel:`Internal Reference` column." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Internal reference numbers are listed in the main Expense Categories view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:240 +msgid "" +"To add an internal reference on an expense category, click on the category " +"to open the form. Enter the internal reference in the field. Beneath the " +":guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use " +"this reference as a subject prefix when submitting by email.`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Internal reference numbers are listed in the main Expense Products view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:249 +msgid "" +"For security purposes, only authenticated employee emails are accepted by " +"Odoo when creating an expense from an email. To confirm an authenticated " +"employee email address, go to the employee card in the " +":menuselection:`Employees` app, and refer to the :guilabel:`Work Email`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:258 +msgid "" +"If submitting an expense via email for a $25.00 meal during a work trip, the" +" email subject would be `FOOD $25.00`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:261 +msgid "Explanation:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:263 +msgid "" +"The :guilabel:`Internal Reference` for the expense category `Meals` is " +"`FOOD`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:264 +msgid "The :guilabel:`Cost` for the expense is `$25.00`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:269 +msgid "Create an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:271 +msgid "" +"When expenses are ready to submit (such as at the end of a business trip, or" +" once a month), an *expense report* needs to be created. Go to the main " +":menuselection:`Expenses` app dashboard, which displays a default " +":guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My " +"Expenses --> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:276 +msgid "" +"Expenses are color coded by status. Any expense with a status of " +":guilabel:`To Report` (expenses that still need to be added to an expense " +"report) the text appears in blue. All other statuses (:guilabel:`To Submit`," +" :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:280 +msgid "" +"First, select each individual expense for the report by clicking the check " +"box next to each entry, or quickly select all the expenses in the list by " +"clicking the check box next to :guilabel:`Expense Date`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:284 +msgid "" +"Another way to quickly add all expenses that are not on an expense report is" +" to click :guilabel:`Create Report` without selecting any expenses, and Odoo" +" will select all expenses with a status of :guilabel:`To Submit` that are " +"not already on a report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the expenses to submit, then create the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:293 +msgid "" +"Any expense can be selected from the :guilabel:`My Expenses` list, " +"regardless of status. The :guilabel:`Create Report` button is visible as " +"long as there is a minimum of 1 expense with a status of :guilabel:`To " +"Report` selected. When the :guilabel:`Create Report` button is clicked, only" +" expenses with a status of :guilabel:`To Submit` that are *not* currently on" +" another expense report will appear in the newly created expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:299 +msgid "" +"Once the expenses have been selected, click the :guilabel:`Create Report` " +"button. The new report appears with all the expenses listed in the " +":guilabel:`Expense` tab. If there is a receipt attached to an individual " +"expense, a :guilabel:`📎 (paperclip)` icon appears next to the " +":guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` " +"columns." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:304 +msgid "" +"When the report is created, the date range for the expenses appears in the " +":guilabel:`Expense Report Summary` field by default. It is recommended to " +"edit this field with a short summary for each report to help keep expenses " +"organized. Enter a short description for the expense report (such as `Client" +" Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report " +"Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu " +"to assign a manager to review the report. If needed, the :guilabel:`Journal`" +" can be changed. Use the drop-down menu to select a different " +":guilabel:`Journal`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Enter a short description and select a manager for the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:316 +msgid "" +"If some expenses are not on the report that should be, they can still be " +"added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense`" +" tab. A pop up appears with all the available expenses that can be added to " +"the report (with a status of :guilabel:`To Submit`). Click the check box " +"next to each expense to add, then click :guilabel:`Select`. The items now " +"appear on the report that was just created. If a new expense needs to be " +"added that does *not* appear on the list, click :guilabel:`New` to create a " +"new expense and add it to the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Add more expenses to the report before submitting." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:328 +msgid "Expense reports can be created in one of three places:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:330 +msgid "" +"Go to the main :menuselection:`Expenses` app dashboard (also accessed by " +"going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:332 +msgid "Go to :menuselection:`Expenses app --> My Expenses --> My Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:333 +msgid "Go to :menuselection:`Expenses app --> Expense Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:335 +msgid "" +"In any of these views, click :guilabel:`New` to create a new expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:340 +msgid "Submit an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:342 +msgid "" +"When an expense report is completed, the next step is to submit the report " +"to a manager for approval. Reports must be individually submitted, and " +"cannot be submitted in batches. Open the specific report from the list of " +"expense reports (if the report is not already open). To view all expense " +"reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:347 +msgid "" +"If the list is large, grouping the results by status may be helpful since " +"only reports that have a :guilabel:`To Submit` status need to be submitted, " +"reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:351 +msgid "" +"The :guilabel:`To Submit` expenses are easily identifiable not just from the" +" :guilabel:`To Submit` status, but the text appears in blue, while the other" +" expenses text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Submit the report to the manager." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:359 +msgid "" +"The status of each report is shown in the :guilabel:`Status` column on the " +"right. If the :guilabel:`Status` column is not visible, click the " +":guilabel:`Additional Options (two dots)` icon at the end of the row, and " +"enable :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:363 +msgid "" +"Click on a report to open it, then click :guilabel:`Submit To Manager`. " +"After submitting a report, the next step is to wait for the manager to " +"approve it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:367 +msgid "" +"The :ref:`expenses/approve`, :ref:`expenses/post`, and " +":ref:`expenses/reimburse` sections are **only** for users with the " +"*necessary rights*." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:373 +msgid "Approve expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:375 +msgid "" +"In Odoo, not just anyone can approve expense reports— only users with the " +"necessary rights (or permissions) can. This means that a user must have at " +"least *Team Approver* rights for the *Expenses* app. Employees with the " +"necessary rights can review expense reports, approve or reject them, and " +"provide feedback thanks to the integrated communication tool." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:380 +msgid "" +"To see who has rights to approve, go to the main :menuselection:`Settings` " +"app and click on :guilabel:`Manage Users`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:384 +msgid "" +"If the *Settings* app is not available, then certain rights are not set on " +"the account. Check the :guilabel:`Access Rights` tab of a user's card in the" +" :menuselection:`Settings` app. the :guilabel:`Administration` section " +"(bottom right of the :guilabel:`Access Rights` tab) is set to one of three " +"options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:389 +msgid "" +":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:390 +msgid "" +":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & " +"Companies` section of the *Settings* app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:392 +msgid "" +":guilabel:`Settings`: The user has access to the entire *Settings* app with " +"no restrictions." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:394 +msgid "" +"Please refer to :doc:`this document " +"` to learn more about managing " +"users and their access rights." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:397 +msgid "" +"Click on an individual to view their card, which displays the " +":guilabel:`Access Rights` tab in the default view. Scroll down to the " +":guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are " +"four options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:401 +msgid "" +":guilabel:`None (blank)`: A blank field means the user has no rights to view" +" or approve expense reports, and can only view their own." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:403 +msgid "" +":guilabel:`Team Approver`: The user can only view and approve expense " +"reports for their own specific team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:405 +msgid "" +":guilabel:`All Approver`: The user can view and approve any expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:406 +msgid "" +":guilabel:`Administrator`: The user can view and approve any expense report," +" as well as access the reporting and configuration menus in the *Expenses* " +"app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:409 +msgid "" +"Users who are able to approve expense reports (typically managers) can " +"easily view all expense reports they have access rights to. Go to " +":menuselection:`Expenses app --> Expense Reports`, and a list appears with " +"all expense reports that have a status of either :guilabel:`To Submit`, " +":guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or " +":guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are " +"hidden in the default view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Reports to validate are found on the Reports to Approve page." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:419 +msgid "" +"When viewing expense reports, there is a panel of filters that can be " +"enabled or disabled on the left side. The three categories that filters can " +"be applied on are :guilabel:`Status`, :guilabel:`Employee`, and " +":guilabel:`Company`. To view only expense reports with a particular status, " +"enable the specific status filter to display the expense reports with only " +"that status. Disable the specific status filter to hide the reports with " +"that status. To view expense reports for a particular employee and/or " +"company, enable the specific employee name filter and/or company filter in " +"the :guilabel:`Employee` and :guilabel:`Company` sections." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:427 +msgid "" +"Reports can be approved in two ways (individually or several at once) and " +"refused only one way. To approve multiple expense reports at once, remain in" +" the list view. First, select the reports to approve by clicking the check " +"box next to each report, or click the box next to :guilabel:`Employee` to " +"select all the reports in the list." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:433 +msgid "" +"Only reports with a status of :guilabel:`Submitted` can be approved. It is " +"recommended to only display the submitted reports by adjusting the status " +"filter on the left side by only having the :guilabel:`Submitted` filter " +"enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:437 +msgid "" +"If a report is selected that is unable to be approved, the " +":guilabel:`Approve Report` button **will not appear**, indicating there is a" +" problem with the selected report(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:440 +msgid "Next, click the :guilabel:`Approve Report` button." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Approve multiple reports by clicking the checkboxes next to each report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:446 +msgid "" +"To approve an individual report, click on a report to go to a detailed view " +"of that report. In this view, several options are presented: " +":guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`," +" or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the " +"report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:450 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to Refuse Expense` " +"field, and then click :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Send messages in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:457 +msgid "" +"Team managers can easily view all the expense reports for their team " +"members. While in the :guilabel:`Expense Reports` view, click the drop-down " +"arrow in the right-side of the search box, and click on :guilabel:`My Team` " +"in the :guilabel:`Filters` section. This presents all the reports for the " +"manager's team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the My Team filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:467 +msgid "" +"If more information is needed, such as a missing receipt, communication is " +"easy from the chatter. In an individual report, simply click :guilabel:`Send" +" message` to open the message text box. Type in a message, tagging the " +"proper person (if needed), and post it to the chatter by clicking " +":guilabel:`Send`. The message is posted in the chatter, and the person " +"tagged will be notified via email of the message, as well as any followers." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:473 +msgid "" +"The only people that can be tagged in a message are *followers*. To see who " +"is a follower, click on the :guilabel:`👤 (person)` icon to display the " +"followers of the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:483 +msgid "Post expenses in accounting" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:485 +msgid "" +"Once an expense report is approved, the next step is to post the report to " +"the accounting journal. To view all expense reports, go to " +":menuselection:`Expenses app --> Expense Reports`. To view only the expense " +"reports that have been approved and need to be posted, adjust the filters on" +" the left side so that only the :guilabel:`Approved` status is enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to post by clicking on expense reports, then reports to post." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:494 +msgid "" +"Just like approvals, expense reports can be posted in two ways (individually" +" or several at once). To post multiple expense reports at once, remain in " +"the list view. First, select the reports to post by clicking the check box " +"next to each report, or click the box next to :guilabel:`Employee` to select" +" all the reports in the list. Next, click :guilabel:`Post Entries`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Post multiple reports at a time from the Expense Reports view, with the " +"Approved filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:503 +msgid "" +"To post an individual report, click on a report to go to the detailed view " +"of that report. In this view, several options are presented: :guilabel:`Post" +" Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, " +"or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to " +"post the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:508 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to Refuse Expense` " +"field, and then click :guilabel:`Refuse`. Refused reports can be viewed by " +"going to :menuselection:`Expenses app --> Expense Reports`, then adjusting " +"the filters on the left so that only :guilabel:`Refused` is selected. This " +"will only show the refused expense reports." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:515 +msgid "" +"To post expense reports to an accounting journal, the user must have " +"following access rights:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:517 +msgid "Accounting: Accountant or Adviser" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:518 +msgid "Expenses: Manager" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:523 +msgid "Reimburse employees" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:525 +msgid "" +"After an expense report is posted to an accounting journal, the next step is" +" to reimburse the employee. To view all the expense reports to pay, go to " +":menuselection:`Expenses app --> Expense Reports --> Reports To Pay`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to pay by clicking on expense reports, then reports to pay." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:533 +msgid "" +"Just like approvals and posting, expense reports can be paid in two ways " +"(individually or several at once). To pay multiple expense reports at once, " +"remain in the list view. First, select the reports to pay by clicking the " +"check box next to each report, or click the box next to :guilabel:`Employee`" +" to select all the reports in the list. Next, click :guilabel:`Register " +"Payment`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Post multiple reports by selecting them, clicking the gear, and then post " +"the entries." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:542 +msgid "" +"To pay an individual report, click on a report to go to a detailed view of " +"that report. Click :guilabel:`Register Payment` to pay the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:545 +msgid "" +"A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, " +":guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if" +" needed. When the selections are correct, click :guilabel:`Create Payment` " +"to send the payment to the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:549 +msgid "" +"To pay an individual report, click on a report in the list view to go to a " +"detailed view of that report. Click :guilabel:`Register Payment` to pay the " +"employee. A :guilabel:`Register Payment` pop-up appears, but when paying an " +"individual expense report instead of several at once, more options appear in" +" the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment " +"Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank " +"Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the " +"employee's bank account from the drop-down menu to directly deposit the " +"payment to their account. When all other selections are correct, click " +":guilabel:`Create Payment` to send the payment to the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Different options appear when registering an individual expense report versus multiple\n" +"expense reports at once." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:564 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:566 +msgid "" +"If expenses are tracked on customer projects, expenses can be automatically " +"charged back to the customer. This is done by creating an expense, " +"referencing the :abbr:`SO (Sales Order)` the expense should be added to, and" +" then creating the expense report. Next, managers approve the expense " +"report, and the accounting department posts the journal entries. Finally, " +"once the expense report is posted to a journal, the expense(s) appears on " +"the :abbr:`SO (Sales Order)` that was referenced. The sales order can then " +"be invoiced, thus invoicing the customer for the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:574 +#: ../../content/applications/finance/fiscal_localizations/india.rst:55 +#: ../../content/applications/finance/fiscal_localizations/india.rst:195 +msgid "Setup" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:576 +msgid "" +"First, specify the invoicing policy for each expense category. Go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`. " +"Click on the expense category to open the expense category form. Under the " +":guilabel:`Invoicing` section, click the radio button next to the desired " +"selection for :guilabel:`Re-Invoicing Expenses`. Options are " +":guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:582 +msgid ":guilabel:`Re-Invoicing Expenses`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:584 +msgid ":guilabel:`None`: Expense category will not be re-invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:585 +msgid "" +":guilabel:`At cost`: Expense category will invoice expenses at their real " +"cost." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:586 +msgid "" +":guilabel:`At sales price`: Expense category will invoice the price set on " +"the sale order." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:589 +msgid "Create an expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:591 +msgid "" +"First, when :ref:`creating a new expense `, the correct " +"information needs to be entered in order to re-invoice a customer. Select " +"the *sales order* the expense will appear on in the :guilabel:`Customer to " +"Reinvoice` section, from the drop-down menu. Next, select the " +":guilabel:`Analytic Account` the expense will be posted to. After the " +"expense(s) are created, the expense report needs to be :ref:`created " +"` and :ref:`submitted ` as usual." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Ensure the customer to be invoiced is called out on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:603 +msgid "" +"Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is " +"critical, since this is what causes the expenses to be automatically " +"invoiced after an expense report is approved." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:606 +msgid "" +"The :guilabel:`Customer to Reinvoice` field can be modified *until an " +"expense report is* **approved**, then the field is no longer able to be " +"modified." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:610 +msgid "Validate and post expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:612 +msgid "" +"Only employees with permissions (typically managers or supervisors) can " +":ref:`approve expenses `. Before approving an expense " +"report, ensure the :guilabel:`Analytic Distribution` is set on every expense" +" line of a report. If an :guilabel:`Analytic Distribution` is missing, " +"assign the correct account(s) from the drop-down menu, and then click " +":guilabel:`Approve` or :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:618 +msgid "" +"The accounting department is typically responsible for :ref:`posting journal" +" entries `. Once an expense report is approved, it can then " +"be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the " +"journal entries are posted*. One the journal entries are posted, the " +"expenses now appear on the referenced :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:624 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:626 +msgid "" +"Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice " +"the customer. After the expense report has been approved and the journal " +"entries have been posted, click the :guilabel:`Sales Orders` smart button to" +" open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now " +"on the :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"After the expense report is posted to the journal entry, the sales order can be called up\n" +"by clicking on the sales order number." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:637 +msgid "" +"More than one :abbr:`SO (Sales Order)` can be referenced on an expense " +"report. If more than one :abbr:`SO (Sales Order)` is referenced, the " +":guilabel:`Sales Orders` smart button will list the number of :abbr:`SO " +"(Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the " +":guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO" +" (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)`" +" to open the individual :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:644 +msgid "" +"The expenses are listed in the :abbr:`SO (Sales Order)` :guilabel:`Order " +"Lines` tab." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "See the expenses listed on the sales order after clicking into it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:650 +msgid "" +"Next, click :guilabel:`Create Invoice`, and select if the invoice is for a " +":guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a " +":guilabel:`Down payment (fixed amount)` by clicking the radio button next to" +" it. Then, click :guilabel:`Create Invoice`. The customer has now been " +"invoiced for the expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:5 +msgid "Fiscal localizations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:10 +msgid "Fiscal localization packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:12 +msgid "" +"**Fiscal Localization Packages** are country-specific modules that install " +"pre-configured taxes, fiscal positions, chart of accounts, and legal " +"statements on your database. Some additional features, such as the " +"configuration of specific certificates, are also added to your Accounting " +"app, following your fiscal administration requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:18 +msgid "" +"Odoo continuously adds new localizations and improves the existing packages." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:23 +msgid "" +"Odoo automatically installs the appropriate package for your company, " +"according to the country selected at the creation of the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:27 +msgid "" +"As long as you haven't posted any entry, you can still select another " +"package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:29 +msgid "" +"To select a fiscal localization package for your company, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Fiscal " +"Localization`, select the appropriate package from the list and save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst-1 +msgid "Select your country's fiscal localization package in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:37 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Use" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:39 +msgid "" +"These packages require you to fine-tune your chart of accounts according to " +"your needs, activate the taxes you use, and configure your country-specific " +"statements and certifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:43 +msgid ":doc:`accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:44 +msgid ":doc:`accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:49 +msgid "List of supported countries" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:51 +msgid "" +"Odoo Accounting can be used in many countries out of the box by installing " +"the appropriate module. Here is a list of all :ref:`fiscal localization " +"package ` that are available on Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:55 +msgid "Algeria - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:56 +msgid ":doc:`Argentina - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:57 +msgid ":doc:`Australian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:58 +msgid ":doc:`Austria - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:59 +msgid ":doc:`Belgium - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:60 +msgid "Bolivia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:61 +msgid ":doc:`Brazilian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:62 +msgid "Canada - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:63 +msgid ":doc:`Chile - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:64 +msgid "China - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:65 +msgid ":doc:`Colombia - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:66 +msgid "Costa Rica - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:67 +msgid "Croatia - Accounting (RRIF 2012)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:68 +msgid "Czech - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:69 +msgid "Denmark - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:70 +msgid "Dominican Republic - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:71 +msgid ":doc:`Ecuadorian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:72 +msgid ":doc:`Egypt - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:73 +msgid "Ethiopia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:74 +msgid "Finnish Localization" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:75 +msgid ":doc:`France - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:76 +msgid "Generic - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:77 +msgid ":doc:`Germany `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:79 +msgid "Germany SKR03 - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:80 +msgid "Germany SKR04 - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:82 +msgid "Greece - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:83 +msgid "Guatemala - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:84 +msgid "Honduras - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:85 +msgid ":doc:`Hong Kong - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:86 +msgid "Hungarian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:87 +msgid ":doc:`Indian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:88 +msgid ":doc:`Indonesian - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:89 +msgid "Ireland - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:90 +msgid "Israel - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:91 +msgid ":doc:`Italy - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:92 +msgid "Japan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:93 +msgid ":doc:`Kenya - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:94 +msgid "Lithuania - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:95 +msgid ":doc:`Luxembourg - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:96 +msgid "Maroc - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:97 +msgid ":doc:`Mexico - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:98 +msgid "Mongolia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:99 +msgid ":doc:`Netherlands - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:100 +msgid "New Zealand - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:101 +msgid "Norway - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:102 +msgid "OHADA - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:103 +msgid "Pakistan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:104 +msgid "Panama - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:105 +msgid ":doc:`Peru - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:106 +msgid ":doc:`Philippines - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:107 +msgid "Poland - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:108 +msgid "Portugal - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:109 +msgid ":doc:`Romania - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:110 +msgid ":doc:`Saudi Arabia - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:111 +msgid ":doc:`Singapore - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:112 +msgid "Slovak - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:113 +msgid "Slovenian - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:114 +msgid "South Africa - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:115 +msgid ":doc:`Spain - Accounting (PGCE 2008) `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:116 +msgid "Sweden - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:117 +msgid ":doc:`Switzerland - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:118 +msgid "Taiwan - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:119 +msgid ":doc:`Thailand - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:120 +msgid "Turkey - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:121 +msgid "" +":doc:`United Arab Emirates - Accounting " +"`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:122 +msgid ":doc:`UK - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:123 +msgid "Ukraine - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:124 +msgid "United States - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:125 +msgid "Uruguay - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:126 +msgid "Venezuela - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:127 +msgid ":doc:`Vietnam - Accounting `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:3 +msgid "Argentina" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:18 +msgid "Webinars" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 +msgid "" +"Below you can find videos with a general description of the localization, " +"and how to configure it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:10 +msgid "" +"`Webinar - Localización de Argentina " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:11 +msgid "" +"`eCommerce - Localización de Argentina " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:14 +msgid "" +"`Smart Tutorial - Localización de Argentina " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:20 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:37 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:61 +msgid "Modules installation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:22 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Argentinean localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:14 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/india.rst:16 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:14 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +msgid "Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:15 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:31 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 +#: ../../content/applications/finance/fiscal_localizations/india.rst:17 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:15 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:32 +msgid ":guilabel:`Argentina - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:33 +msgid "`l10n_ar`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:34 +msgid "" +"Default :ref:`fiscal localization package `, " +"which represents the minimal configuration to operate in Argentina under the" +" :abbr:`AFIP (Administración Federal de Ingresos Públicos)` regulations and " +"guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:37 +msgid ":guilabel:`Argentinean Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:38 +msgid "`l10n_ar_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:39 +msgid "VAT Book report and VAT summary report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:40 +msgid ":guilabel:`Argentinean Electronic Invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:41 +msgid "`l10n_ar_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:42 +msgid "" +"Includes all technical and functional requirements to generate electronic " +"invoices via web service, based on the AFIP regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:44 +msgid ":guilabel:`Argentinean eCommerce`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:45 +msgid "`l10n_ar_website_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:46 +msgid "" +"(optional) Allows the user to see Identification Type and AFIP " +"Responsibility in the eCommerce checkout form in order to create electronic " +"invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:50 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:37 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:70 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:47 +msgid "Configure your company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:52 +msgid "" +"Once the localization modules are installed, the first step is to set up the" +" company's data. In addition to the basic information, a key field to fill " +"in is the :guilabel:`AFIP Responsibility Type`, which represents the fiscal " +"obligation and structure of the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP Responsibility Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:61 +msgid "Chart of account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:63 +msgid "" +"In Accounting, there are three different :guilabel:`Chart of Accounts` " +"packages to choose from. They are based on a company's AFIP responsibility " +"type, and consider the difference between companies that do not require as " +"many accounts as the companies that have more complex fiscal requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:68 +msgid "Monotributista (227 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:69 +msgid "IVA Exento (290 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:70 +msgid "Responsable Inscripto (298 Accounts)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select Fiscal Localization Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:77 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:143 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:238 +msgid "Configure master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:80 +msgid "Electronic Invoice Credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:83 +msgid "Environment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:85 +msgid "" +"The AFIP infrastructure is replicated in two separate environments, " +"**testing** and **production**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:87 +msgid "" +"Testing is provided so that the companies can test their databases until " +"they are ready to move into the **Production** environment. As these two " +"environments are completely isolated from each other, the digital " +"certificates of one instance are not valid in the other one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:91 +msgid "" +"To select a database environment, go to :menuselection:`Accounting --> " +"Settings --> Argentinean Localization` and choose either :guilabel:`Prueba " +"(Testing)` or :guilabel:`Produccion (Production)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP database environment: Testing or Production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:99 +msgid "AFIP certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:101 +msgid "" +"The electronic invoice and other AFIP services work with :guilabel:`Web " +"Services (WS)` provided by the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:104 +msgid "" +"In order to enable communication with the AFIP, the first step is to request" +" a :guilabel:`Digital Certificate` if you do not have one already." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:107 +msgid "" +":guilabel:`Generate Certificate Sign Request (Odoo)`. When this option is " +"selected, a file with extension `.csr` (certificate signing request) is " +"generated to be used in the AFIP portal to request the certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Request a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:114 +msgid "" +":guilabel:`Generate Certificate (AFIP)`. Access the AFIP portal and follow " +"the instructions described in `this document " +"`_ " +"to get a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:118 +msgid "" +":guilabel:`Upload Certificate and Private Key (Odoo)`. Once the certificate " +"is generated, upload it to Odoo using the :guilabel:`Pencil` icon next to " +"the field :guilabel:`Certificado` and select the corresponding file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Upload Certificate and Private Key." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:126 +msgid "" +"In case you need to configure the Homologation Certificate, please refer to " +"the AFIP official documentation: `Homologation Certificate " +"`_. Furthermore, " +"Odoo allows the user to test electronic invoicing locally without a " +"Homologation Certificate. The following message will be in the chatter when " +"testing locally:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "" +"Invoice validated locally because it is in a testing environment without testing\n" +"certificate/keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:141 +msgid "Identification type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:143 +msgid "" +"As part of the Argentinean localization, document types defined by the AFIP " +"are now available in the **Partner form**. Information is essential for most" +" transactions. There are six :guilabel:`Identification Types` available by " +"default, as well as 32 inactive types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of AR Localization document types in Odoo, as defined by AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:152 +msgid "" +"The complete list of :guilabel:`Identification Types` defined by the AFIP is" +" included in Odoo, but only the common ones are active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:156 +msgid "AFIP responsibility type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:158 +msgid "" +"In Argentina, the document type and corresponding transactions associated " +"with customers and vendors is defined by the AFIP Responsibility type. This " +"field should be defined in the **Partner form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:169 +msgid "" +"As part of the localization module, the taxes are created automatically with" +" their related financial account and configuration, e.g., 73 taxes for " +":guilabel:`Responsable Inscripto`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list of AR Localization taxes with financial amount and configuration in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:177 +msgid "Taxes types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:179 +msgid "Argentina has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:181 +msgid "" +":guilabel:`VAT`: this is the regular VAT and can have various percentages;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:182 +msgid "" +":guilabel:`Perception`: advance payment of a tax that is applied on " +"invoices;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:183 +msgid "" +":guilabel:`Retention`: advance payment of a tax that is applied on payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:186 +msgid "Special taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:188 +msgid "" +"Some Argentinean taxes are not commonly used for all companies, and those " +"less common options are labeled as inactive in Odoo by default. Before " +"creating a new tax, be sure to check if that tax is not already included as " +"inactive." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list showing less common Argentinean tax options, which are labeled as inactive in Odoo\n" +"by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:200 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:252 +msgid "Document types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:202 +msgid "" +"In some Latin American countries, like Argentina, some accounting " +"transactions such as invoices and vendor bills are classified by document " +"types defined by the governmental fiscal authorities. In Argentina, the " +"`AFIP `__ is the governmental fiscal authority " +"that defines such transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:207 +msgid "" +"The document type is an essential piece of information that needs to be " +"clearly displayed in printed reports, invoices, and journal entries that " +"list account moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:210 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the document type includes the " +"country in which the document is applicable (this data is created " +"automatically when the localization module is installed)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:214 +msgid "" +"The information required for the :guilabel:`Document Types` is included by " +"default so the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of document types in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:222 +msgid "" +"There are several :guilabel:`Document Types` types that are inactive by " +"default, but can be activated as needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:226 +msgid "Letters" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:228 +msgid "" +"For Argentina, the :guilabel:`Document Types` include a letter that helps " +"indicate the type of transaction or operation. For example, when an invoice " +"is related to a(n):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:231 +msgid "" +":guilabel:`B2B transaction`, a document type :guilabel:`A` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:232 +msgid "" +":guilabel:`B2C transaction`, a document type :guilabel:`B` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:233 +msgid "" +":guilabel:`Exportation Transaction`, a document type :guilabel:`E` must be " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:235 +msgid "" +"The documents included in the localization already have the proper letter " +"associated with each :guilabel:`Document Type`, so there is no further " +"configuration necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "document types grouped by letters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:243 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 +msgid "Use on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:245 +msgid "" +"The :guilabel:`Document Type` on each transaction will be determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:247 +msgid "" +"The journal entry related to the invoice (if the journal uses documents);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:248 +msgid "" +"The onditions applied based on the type of issuer and receiver (e.g., the " +"type of fiscal regime of the buyer and the type of fiscal regime of the " +"vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:254 +msgid "" +"In the Argentinean localization, the journal can have a different approach " +"depending on its usage and internal type. To configure journals, go to " +":menuselection:`Accounting --> Configuration --> Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:258 +msgid "" +"For sales and purchase journals, it's possible to activate the option " +":guilabel:`Use Documents`, which enables a list of :guilabel:`Document " +"Types` that can be related to the invoices and vendor bills. For more detail" +" on invoices, please refer to the section :ref:`2.3 document types " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:263 +msgid "" +"If the sales or purchase journals do not have the :guilabel:`Use Documents` " +"option activated, they will not be able to generate fiscal invoices, " +"meaning, their use case will be mostly limited to monitoring account moves " +"related to internal control processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:268 +msgid "AFIP information (also known as AFIP Point of Sale)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:270 +msgid "" +"The :guilabel:`AFIP POS System` is a field only visible for the **Sales** " +"journals and defines the type of AFIP POS that will be used to manage the " +"transactions for which the journal is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:273 +msgid "The AFIP POS defines the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:275 +msgid "the sequences of document types related to the web service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:276 +msgid "the structure and data of the electronic invoice file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A AFIP POS System field which is available on Sales journals in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:283 +msgid "Web services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:285 +msgid "" +"**Web services** help generate invoices for different purposes. Below are a " +"few options to choose from:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:288 +msgid "" +":guilabel:`wsfev1: Electronic Invoice`: is the most common service, which is" +" used to generate invoices for document types A, B, C, M with no detail per" +" item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:290 +msgid "" +":guilabel:`wsbfev1: Electronic Fiscal Bond`: is for those who invoice " +"capital goods and wish to access the benefit of the Electronic Tax Bonds " +"granted by the Ministry of Economy. For more details go to: `Fiscal Bond " +"`__;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:294 +msgid "" +":guilabel:`wsfexv1: Electronic Exportation Invoice`: is used to generate " +"invoices for international customers and transactions that involve " +"exportation processes, the document type related is type \"E\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Web Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:302 +msgid "Here are some useful fields to know when working with web services:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:304 +msgid "" +":guilabel:`AFIP POS Number`: is the number configured in the AFIP to " +"identify the operations related to this AFIP POS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:306 +msgid "" +":guilabel:`AFIP POS Address`: is the field related to the commercial address" +" registered for the POS, which is usually the same address as the company. " +"For example, if a company has multiple stores (fiscal locations) then the " +"AFIP will require the company to have one AFIP POS per location. This " +"location will be printed in the invoice report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:310 +msgid "" +":guilabel:`Unified Book`: when the AFIP POS System is Preimpresa, then the " +"document types (applicable to the journal) with the same letter will share " +"the same sequence. For example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:313 +msgid "Invoice: FA-A 0001-00000002;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:314 +msgid "Credit Note: NC-A 0001-00000003;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:315 +msgid "Debit Note: ND-A 0001-00000004." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:318 +msgid "Sequences" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:320 +msgid "" +"For the first invoice, Odoo synchronizes with the AFIP automatically and " +"displays the last sequence used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:324 +msgid "" +"When creating :guilabel:`Purchase Journals`, it's possible to define whether" +" they are related to document types or not. In the case where the option to " +"use documents is selected, there would be no need to manually associate the " +"document type sequences, since the document number is provided by the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:391 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:351 +msgid "Usage and testing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:333 +msgid "Invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:335 +msgid "" +"The information below applies to invoice creation once the partners and " +"journals are created and properly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:339 +msgid "Document type assignation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:341 +msgid "" +"When the partner is selected, the :guilabel:`Document Type` field will be " +"filled in automatically based on the AFIP document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:344 +msgid "" +"**Invoice for a customer IVA Responsable Inscripto, prefix A** is the type " +"of document that shows all the taxes in detail along with the customer's " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for a customer IVA Responsable Inscripto, prefix A." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:350 +msgid "" +"**Invoice for an end customer, prefix B** is the type of document that does " +"not detail the taxes, since the taxes are included in the total amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for an end customer, prefix B." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:356 +msgid "" +"**Exportation Invoice, prefix E** is the type of document used when " +"exporting goods that shows the incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Exportation Invoice, prefix E" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:362 +msgid "" +"Even though some invoices use the same journal, the prefix and sequence are " +"given by the :guilabel:`Document Type` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:365 +msgid "" +"The most common :guilabel:`Document Type` will be defined automatically for " +"the different combinations of AFIP responsibility type but it can be updated" +" manually by the user before confirming the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:370 +msgid "Electronic invoice elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:372 +msgid "" +"When using electronic invoices, if all the information is correct then the " +"invoice is posted in the standard way unless there is an error that needs to" +" be addressed. When error messages pop up, they indicate both the issue that" +" needs attention along with a proposed solution. If an error persists, the " +"invoice remains in draft until the issue is resolved." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:377 +msgid "" +"Once the invoice is posted, the information related to the AFIP validation " +"and status is displayed in the AFIP tab, including:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:380 +msgid ":guilabel:`AFIP Autorisation`: CAE number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:381 +msgid "" +":guilabel:`Expiration Date`: deadline to deliver the invoice to the " +"customers (normally 10 days after the CAE is generated);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:383 +msgid "" +":guilabel:`Result:` indicates if the invoice has been :guilabel:`Aceptado en" +" AFIP` and/or :guilabel:`Aceptado con Observaciones`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP Status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:391 +msgid "Invoice taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:393 +msgid "" +"Based on the :guilabel:`AFIP Responsibility type`, the VAT tax can apply " +"differently on the PDF report:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:396 +msgid "" +":guilabel:`A. Tax excluded`: in this case the taxed amount needs to be " +"clearly identified in the report. This condition applies when the customer " +"has the following AFIP Responsibility type of **Responsable Inscripto**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax excluded." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:403 +msgid "" +":guilabel:`B. Tax amount included`: this means that the taxed amount is " +"included as part of the product price, subtotal, and totals. This condition " +"applies when the customer has the following AFIP Responsibility types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:407 +msgid "IVA Sujeto Exento;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:408 +msgid "Consumidor Final;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:409 +msgid "Responsable Monotributo;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:410 +msgid "IVA liberado." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax amount included." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:417 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:646 +msgid "Special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:420 +msgid "Invoices for services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:422 +msgid "" +"For electronic invoices that include :guilabel:`Services`, the AFIP requires" +" to report the service starting and ending date, this information can be " +"filled in the tab :guilabel:`Other Info`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoices for Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:429 +msgid "" +"If the dates are not selected manually before the invoice is validated, the " +"values will be filled automatically with the first and last day of the " +"invoice's month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Service Dates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:437 +msgid "Exportation invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:439 +msgid "" +"Invoices related to :guilabel:`Exportation Transactions` require that a " +"journal uses the AFIP POS System **Expo Voucher - Web Service** so that the " +"proper document type(s) can be associated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Exporation journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:446 +msgid "" +"When the customer selected in the invoice is configured with an AFIP " +"responsibility type :guilabel:`Cliente / Proveedor del Exterior` - " +":guilabel:`Ley N° 19.640`, Odoo automatically assigns the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:450 +msgid "Journal related to the exportation Web Service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:451 +msgid "Exportation document type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:452 +msgid "Fiscal position: Compras/Ventas al exterior;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:453 +msgid "Concepto AFIP: Products / Definitive export of goods;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:454 +msgid "Exempt Taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice fields autofilled in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:461 +msgid "" +"The Exportation Documents require Incoterms to be enabled and configured, " +"which can be found in :menuselection:`Other Info --> Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice - Incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:469 +msgid "Fiscal bond" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:471 +msgid "" +"The :guilabel:`Electronic Fiscal Bond` is used for those who invoice capital" +" goods and wish to access the benefit of the Electronic Tax Bonds granted by" +" the Ministry of Economy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:474 +msgid "" +"For these transactions, it is important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:476 +msgid "Currency (according to the parameter table) and invoice quotation;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:477 +msgid "Taxes;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:478 +msgid "Zone;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:479 +msgid "Detail each item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:481 +msgid "Code according to the Common Nomenclator of Mercosur (NCM);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:482 +msgid "Complete description;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:483 +msgid "Unit Net Price;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:484 +msgid "Quantity;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:485 +msgid "Unit of measurement;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:486 +msgid "Bonus;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:487 +msgid "VAT rate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:490 +msgid "Electronic credit invoice MiPyme (FCE)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:492 +msgid "" +"For SME invoices, there are several document types that are classified as " +"**MiPyME**, which are also known as **Electronic Credit Invoice** (or " +"**FCE** in Spanish). This classification develops a mechanism that improves " +"the financing conditions for small and medium-sized businesses, and allows " +"them to increase their productivity, through the early collection of credits" +" and receivables issued to their clients and/or vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:498 +msgid "" +"For these transactions it's important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:500 +msgid "specific document types (201, 202, 206, etc);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:501 +msgid "the emitter should be eligible by the AFIP to MiPyME transactions;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:502 +msgid "the amount should be bigger than 100,000 ARS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:503 +msgid "" +"A bank account type CBU must be related to the emisor, otherwise the invoice" +" cannot be validated, having an error message such as the following." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Bank account relation error." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:510 +msgid "" +"To set up the :guilabel:`Transmission Mode`, go to settings and select " +"either :guilabel:`SDC` or :guilabel:`ADC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:517 +msgid "" +"To change the :guilabel:`Transmission Mode` for a specific invoice, go to " +"the :guilabel:`Other Info` tab and change it before confirming." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:521 +msgid "" +"Changing the :guilabel:`Transmission Mode` will not change the mode selected" +" in :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode on Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:528 +msgid "" +"When creating a :guilabel:`Credit/Debit` note related to a FCE document:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:530 +msgid "" +"use the :guilabel:`Credit and Debit Note` buttons, so all the information " +"from the invoice is transferred to the new :guilabel:`Credit and Debit " +"Note`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:532 +msgid "" +"the document letter should be the same as than the originator document " +"(either A or B);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:533 +msgid "" +"the same currency as the source document must be used. When using a " +"secondary currency there is an exchange difference if the currency rate is " +"different between the emission day and the payment date. It is possible to " +"create a credit/debit note to decrease/increase the amount to pay in ARS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Credit & debit notes buttons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:541 +msgid "When creating a :guilabel:`Credit Note` we can have two scenarios:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:543 +msgid "" +"the FCE is rejected so the :guilabel:`Credit Note` should have the field " +":guilabel:`FCE, is Cancellation?` as *True*; or;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:545 +msgid "" +"the :guilabel:`Credit Note`, is created to annulate the FCE document, in " +"this case the field :guilabel:`FCE, is Cancellation?` must be *empty* " +"(false)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "FCE: Es Cancelación?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:553 +msgid "Invoice printed report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:555 +msgid "" +"The :guilabel:`PDF Report` related to electronic invoices that have been " +"validated by the AFIP includes a barcode at the bottom of the format which " +"represents the CAE number. The expiration date is also displayed as it is a " +"legal requirement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoice printed report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:564 +msgid "Troubleshooting and auditing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:566 +msgid "" +"For auditing and troubleshooting purposes, it is possible to obtain detailed" +" information of an invoice number that has been previously sent to the AFIP." +" To retrieve this information, activate the :ref:`developer mode `, then go to the :menuselection:`Accounting` menu and click on the " +"button :guilabel:`Consult Invoice` button in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult invoice in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Details of invoice consulted in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:579 +msgid "" +"It is also possible to retrieve the last number used in AFIP for a specific " +"document type and POS Number as a reference for any possible issues on the " +"sequence synchronization between Odoo and AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult the last invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:590 +msgid "" +"Based on the purchase journal selected for the vendor bill, the " +":guilabel:`Document Type` is now a required field. This value is auto-" +"populated based on the AFIP Responsibility type of Issuer and Customer, but " +"the value can be changed if necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Changing journal and document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:598 +msgid "" +"The :guilabel:`Document Number` field needs to be registered manually and " +"the format will be validated automatically. However, in case the format is " +"invalid, a user error will be displayed indicating the correct format that " +"is expected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Vendor bill document number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:606 +msgid "" +"The vendor bill number is structured in the same way as the customer " +"invoices, excepted that the document sequence is entered by the user using " +"the following format: *Document Prefix - Letter - Document Number*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:611 +msgid "Validate vendor bill number in AFIP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:613 +msgid "" +"As most companies have internal controls to verify that the vendor bill is " +"related to an AFIP valid document, an automatic validation can be set in " +":menuselection:`Accounting --> Settings --> Argentinean Localization --> " +"Validate document in the AFIP`, considering the following levels:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:617 +msgid "" +":guilabel:`Not available:` the verification is not done (this is the default" +" value);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:618 +msgid "" +":guilabel:`Available:` the verification is done. In case the number is not " +"valid it, only displays a warning but still allows the vendor bill to be " +"posted;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:620 +msgid "" +":guilabel:`Required:` the verification is done and it does not allow the " +"user to post the vendor bill if the document number is not valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify Vendor Bills validity in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:628 +msgid "Validate vendor bills in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:630 +msgid "" +"With the vendor validation settings enabled, a new button shows up on the " +"vendor bills inside of Odoo, labeled :guilabel:`Verify on AFIP`, which is " +"located next to the :guilabel:`AFIP Authorization code` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify on AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:638 +msgid "" +"In case the vendor bill cannot be validated in AFIP, a value of " +":guilabel:`Rejected` will be displayed on the dashboard and the details of " +"the invalidation will be added to the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP authorization Rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:649 +msgid "Untaxed concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:651 +msgid "" +"There are some transactions that include items that are not a part of the " +"VAT base amount, such as fuel and gasoline invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:654 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and an additional item to register the amount " +"of the exempt concept." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT exempt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:662 +msgid "Perception taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:664 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and the perception tax can be added in any of " +"the product lines. As a result, there will be one tax group for the VAT and " +"another for the perception. The perception default value is always " +":guilabel:`0.10`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:669 +msgid "" +"To edit the VAT perception and set the correct amount, you should use the " +":guilabel:`Pencil` icon that is the next to the :guilabel:`Perception` " +"amount. After the VAT perception amount has been set, the invoice can then " +"be validated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Enter the perception amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:678 +msgid "Check management" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:680 +msgid "" +"To install the *Third Party and Deferred/Electronic Checks Management* " +"module, go to :menuselection:`Apps` and search for the module by its " +"technical name `l10n_latam_check` and click the :guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "l10n_latam_check module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:688 +msgid "" +"This module enables the required configuration for journals and payments to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:690 +msgid "Create, manage, and control your different types of checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:691 +msgid "Optimize the management of *own checks* and *third party checks*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:692 +msgid "" +"Have an easy and effective way to manage expiration dates from your own and " +"third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:694 +msgid "" +"Once all the configurations are made for the Argentinian electronic invoice " +"flow, it is also needed to complete certain configurations for the own " +"checks and the third party checks flows." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:698 +msgid "Own checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:700 +msgid "" +"Configure the bank journal used to create your own checks by going to " +":menuselection:`Accounting --> Configuration --> Journals`, selecting the " +"bank journal, and opening the :guilabel:`Outgoing Payments` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:704 +msgid "" +":guilabel:`Checks` should be available as a :guilabel:`Payment Method`. If " +"not, click :guilabel:`Add a line` and type `Checks` under :guilabel:`Payment" +" Method` to add them" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:706 +msgid "Enable the :guilabel:`Use electronic and deferred checks` setting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:709 +msgid "" +"This last configuration **disables** the printing ability but enables to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:711 +msgid "Enter check numbers manually" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:712 +msgid "Adds a field to allocate the payment date of the check" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Bank journal configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:719 +msgid "Management of own checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:721 +msgid "" +"Own checks can be created directly from the vendor bill. For this process, " +"click on the :guilabel:`Register Payment` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:724 +msgid "" +"On the payment registration modal, select the bank journal from which the " +"payment is to be made and set the :guilabel:`Check Cash-In Date`, and the " +":guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with own check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:732 +msgid "" +"To manage current checks, the :guilabel:`Check Cash-In Date` field must be " +"left blank or filled in with the current date. To manage deferred checks, " +"the :guilabel:`Check Cash-In Date` must be set in the future." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:736 +msgid "" +"To manage your existing own checks, navigate to :menuselection:`Accounting " +"--> Vendors --> Own Checks`. This window shows critical information such as " +"the dates when checks need to be paid, the total quantity of checks, and the" +" total amount paid in checks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Own checks menu location." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:744 +msgid "" +"It is important to note that the list is pre-filtered by checks that are " +"still *not reconciled* with a bank statement - that were not yet debited " +"from the bank - which can be verified with the :guilabel:`Is Matched with a " +"Bank Statement` field. If you want to see all of your own checks, delete the" +" :guilabel:`No Bank Matching` filter by clicking on the :guilabel:`X` " +"symbol." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Own checks menu organization and filtering." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:754 +msgid "Cancel an own check" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:756 +msgid "" +"To cancel an own check created in Odoo, navigate to " +":menuselection:`Accounting --> Vendors --> Own Checks` and select the check " +"to be canceled, then click on the :guilabel:`Void Check` button. This will " +"break the reconciliation with the vendor bills and the bank statements and " +"leave the check in a **canceled** state." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Empty Check button to cancel Own Checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:766 +msgid "Third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:768 +msgid "" +"In order to register payments using third party checks, two specific " +"journals need to be configured. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Journals` and create two " +"new journals:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:772 +msgid "`Third Party Checks`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:773 +msgid "`Rejected Third Party Checks`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:776 +msgid "" +"You can manually create more journals if you have multiple points of sale " +"and need journals for those." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:779 +msgid "" +"To create the *Third Party Checks* journal, click the :guilabel:`New` button" +" and configure the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:782 +msgid "Type `Third Party Checks` as the :guilabel:`Journal Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:783 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:817 +msgid "Select :guilabel:`Cash` as :guilabel:`Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:784 +msgid "" +"In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to " +"`1.1.1.02.010 Cheques de Terceros`, input a :guilabel:`Short Code` of your " +"choice, and select a :guilabel:`Currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Automatically created cash account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:791 +msgid "The available payment methods are listed in the *payments* tabs:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:793 +msgid "" +"For new incoming third party checks, go to :menuselection:`Incoming Payments" +" tab --> Add a line` and select :guilabel:`New Third Party Checks`. This " +"method is used to create *new* third party checks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:796 +msgid "" +"For incoming and outgoing existing third party checks, go to " +":menuselection:`Incoming Payments tab --> Add a line` and select " +":guilabel:`Existing Third Party Checks`. Repeat the same step for the " +":guilabel:`Outgoing Payments` tab. This method is used to receive and/or pay" +" vendor bills using already *existing* checks, as well as for internal " +"transfers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:802 +msgid "" +"You can delete pre-existing payment methods appearing by default when " +"configuring the third party checks journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment methods automatically created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:809 +msgid "" +"The *Rejected Third Party Checks* journal also needs to be created and/or " +"configured. This journal is used to manage rejected third party checks and " +"can be utilized to send checks rejected at the moment of collection or when " +"coming from vendors when rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:813 +msgid "" +"To create the *Rejected Third Party Checks* journal, click the " +":guilabel:`New` button and configure the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:816 +msgid "Type `Rejected Third Party Checks` as the :guilabel:`Journal Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:818 +msgid "" +"In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to " +"`1.1.1.01.002 Rejected Third Party Checks`, input a :guilabel:`Short Code` " +"of your choice, and select a :guilabel:`Currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:822 +msgid "Use the same payment methods as the *Third Party Checks* journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:825 +msgid "New third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:827 +msgid "" +"To register a *new* third party check for a customer invoice, click the " +":guilabel:`Register Payment` button. In the pop-up window, you must select " +":guilabel:`Third Party Checks` as journal for the payment registration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:831 +msgid "" +"Select :guilabel:`New Third Party Checks` as :guilabel:`Payment Method`, and" +" fill in the :guilabel:`Check Number`, :guilabel:`Payment Date`, and " +":guilabel:`Check Bank`. Optionally, you can manually add the " +":guilabel:`Check Issuer Vat`, but this is automatically filled by the " +"customer's VAT number related to the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with New Third Party Check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:841 +msgid "Existing third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:843 +msgid "" +"To pay a vendor bill with an *existing* check, click the :guilabel:`Register" +" Payment` button. In the pop-up window, you must select :guilabel:`Third " +"Party Checks` as journal for the payment registration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:847 +msgid "" +"Select :guilabel:`Existing Third Party Checks` as :guilabel:`Payment " +"Method`, and select a check from the :guilabel:`Check` field. The field " +"shows all **available existing checks** to be used as payment for vendor " +"bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with Existing Third Party Check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:855 +msgid "" +"When an **existing third party check** is used, you can review the " +"operations related to it. For example, you can see if a third party check " +"made to pay a customer invoice was later used as an existing third party " +"check to pay a vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:859 +msgid "" +"To do so, either go to :menuselection:`Accounting --> Customers --> Third " +"Party Checks` or :menuselection:`Accounting --> Vendors --> Own Checks` " +"depending on the case, and click on a check. In the :guilabel:`Check Current" +" Journal` field, click on :guilabel:`=> Check Operations` to bring up the " +"check's history and movements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Check Operations menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:868 +msgid "" +"The menu also displays critical information related to these operations, " +"such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:870 +msgid "" +"The :guilabel:`Payment Type`, allowing to classify whether it is a payment " +"*sent* to a vendor or a payment *received* from a customer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:872 +msgid "The :guilabel:`Journal` in which the check is currently registered" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:873 +msgid "" +"The **partner** associated with the operation (either customer or vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:878 +msgid "" +"As part of the localization installation, financial reporting for Argentina " +"was added to the :guilabel:`Accounting` dashboard. Access these reports by " +"navigating to :menuselection:`Accounting --> Reporting --> Argentinean " +"Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Argentinean reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:887 +msgid "VAT reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:890 +msgid "Sales VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:892 +msgid "" +"In this report, all the sales are recorded, which are taken as the basis for" +" the accounting records to determine the VAT (Tax Debit)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:895 +msgid "" +"The :guilabel:`Sales VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Sales VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:903 +msgid "Purchases VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:905 +msgid "" +"The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Purchases VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:913 +msgid "VAT summary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:915 +msgid "" +"Pivot table designed to check the monthly VAT totals. This report is for " +"internal usage, it is not sent to the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT Summary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:923 +msgid "IIBB - Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:926 +msgid "IIBB - Sales by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:928 +msgid "" +"Pivot table where you can validate the gross income in each jurisdiction. " +"Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Sales by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:936 +msgid "IIBB - Purchases by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:938 +msgid "" +"Pivot table where you can validate the gross purchases in each jurisdiction." +" Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Purchases by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:14 +msgid "Module Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:15 +msgid "Module Key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:17 +msgid ":guilabel:`Australia - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +msgid "`l10n_au`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:19 +msgid "" +"Installed by default when the Accounting :guilabel:`Fiscal Localization` " +"package is set to :guilabel:`Australia`. This module also installs the " +":guilabel:`ABA credit transfer` and the :guilabel:`Remittance Advice report`" +" module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:22 +msgid ":guilabel:`Australian Reports - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:23 +msgid "`l10n_au_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:24 +msgid "" +"Includes the :guilabel:`Taxable Payments Annual Reports (TPAR)` and the " +":guilabel:`BAS report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:26 +msgid ":guilabel:`Australia - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:27 +msgid "`l10n_au_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:28 +msgid "Payroll localisation for Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:29 +msgid ":guilabel:`Australia - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:30 +msgid "`l10n_au_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:31 +msgid "" +"Installs the link between Australian payroll and accounting. The module also" +" installs the modules: :guilabel:`Australian - Accounting`; " +":guilabel:`Australian Reports - Accounting`; and :guilabel:`Australia - " +"Payroll`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:34 +msgid ":guilabel:`Accounting Customer Statements`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:35 +msgid "`l10n_account_customer_statements`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:36 +msgid "" +"Allows the management and sending of monthly customer statements from the " +"partner ledger and the contact form. Also used in New Zealand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:38 +msgid ":guilabel:`Employment Hero Australian Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:39 +msgid "`l10n_au_keypay`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:40 +msgid "" +"Synchronises all pay runs from Employment Hero with Odoo’s journal entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:47 +msgid "" +"The Australian chart of accounts is included in the **Australia - " +"Accounting** module. Go to :menuselection:`Accounting --> Configuration --> " +"Chart of Accounts` to access it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:373 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:79 +msgid ":doc:`../accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:56 +msgid "Taxes and GST" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:58 +msgid "" +"The default Australian taxes impact the :ref:`BAS Report `, " +"which can be accessed through :menuselection:`Accounting --> Reporting --> " +"BAS Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:61 +msgid "" +"In Australia, the standard **Goods and Services Tax** (GST) rate is 10%, but" +" different rates and exemptions exist for specific categories of goods and " +"services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Default GST of Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:68 +msgid "Tax Mapping" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:70 +msgid "" +"Within the Australian localisation package, tax names encompass the tax rate" +" as an integral part of their naming convention." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:73 +msgid "" +"Despite the high amount of taxes in Odoo, these taxes are pretty similar " +"(mostly 0% and 10%), with different tax grid variations for:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:76 +msgid "Goods" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:77 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:165 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:169 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:173 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:177 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:185 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:189 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:193 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:197 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:201 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:205 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:213 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:217 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:221 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:225 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:229 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:233 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:237 +msgid "Services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:78 +msgid "TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:79 +msgid "TPAR without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:82 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:79 +msgid ":doc:`Taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:84 +msgid "" +"Taxes including a **TPAR** mention impact not only the **BAS** report but " +"also the **TPAR** report. Businesses from certain industries need to report " +"payments made to subcontractors from relevant services during the financial " +"year. Odoo combines the use of taxes and fiscal positions to report these " +"payments on the **TPAR** report. Taxes with the mention **TPAR without ABN**" +" are used to record amounts withheld from subcontractors without an **ABN** " +"for the **ATO**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:91 +msgid ":ref:`TPAR `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:93 +msgid "Here are the taxes for Australia in Odoo 17." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:99 +msgid "GST Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:101 +msgid "GST Scope" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:102 +msgid "GST Type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:103 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:139 +msgid "10%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:104 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:164 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:168 +msgid "GST Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:106 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:110 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:114 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:118 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:122 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:126 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:130 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:134 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:138 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:166 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:170 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:174 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:182 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:186 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:190 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:194 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:198 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:202 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:206 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:210 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:214 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:218 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:222 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:226 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:230 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:234 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:238 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:107 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:143 +msgid "10% INC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:108 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:172 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:176 +msgid "GST Inclusive Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:111 +msgid "10% C" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:112 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:180 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:184 +msgid "Capital Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:115 +msgid "0% C" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:116 +msgid "Zero Rated Purch" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:119 +msgid "100% T EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:120 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:196 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:200 +msgid "Purchase (Taxable Imports) - Tax Paid Separately" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:123 +msgid "10% I" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:124 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:204 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:208 +msgid "Purchases for Input Taxed Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:127 +msgid "10% P" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:128 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:212 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:216 +msgid "Purchases for Private use or not deductible" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:131 +msgid "100% EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:132 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:220 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:224 +msgid "GST Only on Imports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:135 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:159 +msgid "10% Adj" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:136 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:228 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:232 +msgid "Tax Adjustments (Purchases)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:140 +msgid "GST Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:144 +msgid "GST Inclusive Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:147 +msgid "0% EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:148 +msgid "Zero Rated (Export) Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:151 +msgid "0% EXEMPT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:152 +msgid "Exempt Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:155 +msgid "0% I" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:156 +msgid "Input Taxed Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:160 +msgid "Tax Adjustments (Sales)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:163 +msgid "10% TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:167 +msgid "10% TPAR NO ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:171 +msgid "10% INC TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:175 +msgid "10% INC TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:179 +msgid "10% C TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:183 +msgid "10% C TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:187 +msgid "0% C TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:188 +msgid "Zero Rated Purch TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:191 +msgid "0% C TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:192 +msgid "Zero Rated Purch TPAR without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:195 +msgid "100% T EX TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:199 +msgid "100% T EX TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:203 +msgid "10% I TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:207 +msgid "100% I TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:211 +msgid "10% P TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:215 +msgid "10% P TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:219 +msgid "100% EX TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:223 +msgid "100% EX TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:227 +msgid "10% Adj TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:231 +msgid "10% Adj TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:235 +msgid "47% WH" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:236 +msgid "Tax Withheld for Partners without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:243 +msgid "BAS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:245 +msgid "" +"The **Business Activity Statement (BAS)** report is a critical tax reporting" +" requirement for businesses registered for **Goods and Services Tax (GST)** " +"in Australia. The **BAS** is used to report and remit various taxes to the " +"**Australian Taxation Office (ATO)**. With the Odoo **BAS** feature, " +"businesses can report on the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:250 +msgid "Goods and Services Tax (GST)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:251 +msgid "PAYG tax withheld" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "BAS report in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:256 +msgid "" +"The taxes for GST are collected from the **tax grid**, which is pre-" +"configured in the system. The **tax grid** can also be manually set up for " +"any additional special GST. Once the tax for each account is set up, the " +"system automatically slots journal items into the correct tax category. This" +" ensures the **BAS** report is accurate and reflective of the business's " +"financial activities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "GST grids in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:264 +msgid "" +"In addition, the **BAS** report includes the **PAYG** tax withheld " +"components (**W1** to **W5**, then **summary, section 4**). This integration" +" ensures that all payroll-related withholding taxes are accurately captured " +"and reflected within the report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "PAYG Tax Withheld and Summary of BAS report in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:271 +msgid "" +"The module incorporates built-in rules that facilitate the automatic " +"calculation of taxes for types **W1** to **W5**. For a detailed walkthrough " +"and more information on the calculation process for these taxes, please " +"refer to the Payroll app documentation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:276 +msgid ":ref:`Payroll `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:279 +msgid "Closing the BAS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:281 +msgid "" +"When it is time to file the tax return with the **ATO**, click " +":guilabel:`Closing entry`. The tax return period can be configured in " +":menuselection:`configuration --> Settings --> Tax Return Periodicity`. " +"Also, the start date of the tax return period can be defined through the " +"**period button** (marked by a calendar icon 📅)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:287 +msgid ":doc:`Year-end closing <../accounting/reporting/year_end>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:290 +msgid "" +"Odoo uses the *calendar quarter* rather than the Australian FY quarter, " +"which means **July to September is Q3 in Odoo**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:293 +msgid "" +"Before closing the entry for the first time, the default **GST payable " +"account** and **GST receivable account** need to be set. A notification pops" +" up and redirects the user to tax group configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:297 +msgid "" +"Once the **GST payable** and **GST receivable** accounts are set up, the " +"**BAS** report generates an accurate journal closing entry automatically, " +"which balances out the GST balance with the GST clearing account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "GST accounts for the BAS report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:304 +msgid "" +"The balance between **GST receivable** and **payable** is set against the " +"tax clearing account defined on the tax group. The amount to be paid to or " +"received from the **ATO** can be reconciled against a bank statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "BAS tax payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:312 +msgid "" +"The **BAS** report is not directly submitted to the **ATO**. Odoo helps you " +"automatically compute the necessary values in each section, with the " +"possibility to audit them to better understand the history behind these " +"numbers. Businesses can copy these values and enter them on the `ATO’s " +"portal `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:320 +msgid "TPAR report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:322 +msgid "" +"Odoo allows businesses to report payments made to contractors or " +"subcontractors during the financial year. This is done by generating a " +":abbr:`TPAR (Taxable Payments Annual Report)`. If you are unsure your " +"business needs this report, refer to the documentation provided by the `ATO " +"`_. You can find " +"this report in :menuselection:`Accounting --> Reporting --> Taxable Payments" +" Annual Reports (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:331 +msgid "" +"Under :menuselection:`Accounting --> Customers` or " +":menuselection:`Accounting --> Vendors`, select a your contractor and set a " +":guilabel:`Fiscal Position` under the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "TPAR fiscal position" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:337 +msgid "" +"Upon billing a contact with a fiscal position set to :guilabel:`TPAR` or " +":guilabel:`TPAR without ABN`, the report is automatically generated in " +":menuselection:`Accounting --> Reporting --> Taxable Payments Annual Reports" +" (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:341 +msgid "" +"The report includes the **ABN**, **Total GST**, **Gross Paid**, and **Tax " +"Withheld** from their **TPAR** subcontractors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:344 +msgid "**Total GST**: the total tax paid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:345 +msgid "" +"**Gross Paid amounts**: shows after registering a payment for those bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:346 +msgid "" +"**Tax Withheld**: shown if the subcontractor is registered with a fiscal " +"position set to :guilabel:`TPAR without ABN`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:349 +msgid "The **TPAR** report can be exported to PDF, XLSX, and TPAR formats." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:354 +msgid "Customer statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:356 +msgid "" +"Customer statements allow customers to see their financial transactions with" +" the company over a certain period, and overdue statement details. These " +"statements can be sent out to customers by email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Customer statement in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:363 +msgid "There are **two** ways for customers to download these statements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:365 +msgid "" +"**From the contact form:** Customer statements are under " +":menuselection:`Customers --> Customers`. Select a customer, click the " +"**gear icon (⚙)**, and then :guilabel:`Print Customer Statements`. This " +"prints out the statement from the beginning of the month to today's date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:370 +msgid "" +"**From the partner ledger:** This option allows for more flexibility in " +"selecting a statement's start and end date. You can access it by going to " +":menuselection:`Accounting --> Reporting --> Partner Ledger`. From here, " +"specify a date range in the **calendar menu (📅)** for the statement, hover " +"over a partner, and click the :guilabel:`Customer Statements` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Customer statement from partner ledger report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:381 +msgid "Remittance advice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:383 +msgid "" +"A remittance advice is a document used as proof of payment to a business. In" +" Odoo, it can be accessed by going to :menuselection:`Accounting ‣ Vendors ‣" +" Payments`, selecting the payment(s), and clicking :menuselection:`Print -->" +" Payment Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Remittance advice in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:393 +msgid "E-Invoicing via Peppol" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:395 +msgid "" +"Odoo is compliant with Australia's and New Zealand's `PEPPOL requirements " +"`_. You can find " +"and set up **electronic invoicing** settings per partner under " +":menuselection:`Accounting --> Customers` or :menuselection:`Accounting --> " +"Vendors`, select a partner, and click the :guilabel:`Accounting` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Peppol settings from a partner in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:404 +msgid "" +"Validating an invoice or credit note for a partner on the PEPPOL network " +"will download a compliant XML file that can be manually uploaded to your " +"PEPPOL network." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:410 +msgid "ABA files for batch payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:415 +msgid "" +"An ABA file is a digital format developed by the `Australian Bankers' " +"Association `_. It is designed for business " +"customers to facilitate bulk payment processing by uploading a single file " +"from their business management software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:419 +msgid "" +"The main advantage of using ABA files is to improve payment and matching " +"efficiency. This is achieved by consolidating numerous payments into one " +"file for batch processing, which can be submitted to all Australian banks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:427 +msgid "Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:429 +msgid "" +"To enable **batch payments**, go to :menuselection:`Accounting --> " +"Configuration --> Setting --> Batch Payment` and enable :guilabel:`Allow " +"Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:433 +msgid "Bank journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:435 +msgid "" +"Then, go to :menuselection:`Accounting --> Configuration --> Journals` and " +"select the :guilabel:`Bank` journal type. In the :guilabel:`Journal Entries`" +" tab, enter the :guilabel:`Account Number` and click :guilabel:`Create and " +"edit`. In the pop-up window, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:440 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:477 +msgid ":guilabel:`Bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:441 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:478 +msgid ":guilabel:`Account Holder Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:442 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:479 +msgid ":guilabel:`BSB`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:443 +msgid ":guilabel:`Account Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Account Number settings for ABA in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:449 +msgid "The :guilabel:`Send Money` field must be **enabled**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:452 +msgid "The :guilabel:`Currency` field is optional." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:454 +msgid "" +"Go back to the :guilabel:`Journal Entries` tab and fill in the following " +"fields related to the ABA:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:456 +msgid ":guilabel:`BSB`: This field is auto-formatted from the bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:457 +msgid "" +":guilabel:`Financial Institution Code`: The official 3-letter abbreviation " +"of the financial institution (e.g., WBC for Westpac)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:459 +msgid "" +":guilabel:`Supplying User Name`: 6-digit number provided by your bank. " +"Contact or check your bank website if you need to know." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:463 +msgid "" +":guilabel:`Include Self-Balancing Transactions`: Selecting this option adds " +"an additional" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:462 +msgid "" +"\"self-balancing\" transaction to the end of the ABA file, which some " +"financial institutions require when generating ABA files. Check with your " +"bank to see if you need this option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:465 +msgid "" +"Then, go to the :guilabel:`Outgoing Payments` tab on the same " +":guilabel:`Bank` type journal. Click :guilabel:`Add a line` and select " +":guilabel:`ABA Credit Transfer` as the **payment method**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:469 +msgid "Partners’ bank accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:471 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> Customers` or " +":menuselection:`Accounting --> Vendors --> Vendors` and select a partner for" +" whom you want to add banking information. Once selected, click the " +":guilabel:`Accounting` tab, and under the :guilabel:`Bank Accounts` section," +" click :guilabel:`Add a line` to fill in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:476 +msgid ":guilabel:`Account Number` of that partner" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:480 +msgid ":guilabel:`Accounter Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:481 +msgid "" +":guilabel:`Send Money` defines the bank account as *trusted*, which is " +"essential for ABA files and must be enabled if to be used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:485 +msgid "Generate an ABA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:487 +msgid "" +"To generate an **ABA** file, :guilabel:`Create` a vendor bill (manually or " +"from a purchase order). :guilabel:`Confirm` the bill and ensure the vendor’s" +" banking information is set up correctly before registering a payment.." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:491 +msgid "" +"Next, click :guilabel:`Register Payment` in the pop-up window: select the " +":guilabel:`Bank` journal, select :guilabel:`ABA Credit Transfer` as " +":guilabel:`Payment Method`, and select the right :guilabel:`Recipient Bank " +"Account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:495 +msgid "" +"Once payments are confirmed, they appear in :menuselection:`Accounting --> " +"Vendors --> Payments`. Tick the box of the payments to be included in the " +"batch, then click :guilabel:`Create Batch`. Verify all information is " +"correct and finally :guilabel:`Validate`. Once validated, the ABA file " +"becomes available in the **chatter** on the right." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:500 +msgid "" +"After uploading it to your bank’s portal, an ABA transaction line will " +"appear in your bank feed at the following bank feed iteration. You will need" +" to reconcile it against the **batch payment** made in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:505 +msgid ":doc:`Batch Payment <../accounting/payments/batch>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:510 +msgid "Buy Now, Pay Later solutions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:512 +msgid "" +"Buy Now, Pay Later solutions are popular payment methods for eShops in " +"Australia. Some of these solutions are available via the `Stripe " +"`_ and `AsiaPay " +"`_ payment providers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:517 +msgid ":doc:`AsiaPay Payment Provider <../payment_providers/asiapay>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:518 +msgid ":doc:`Stripe Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:521 +msgid "POS terminals for Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:523 +msgid "" +"If you wish to have a direct connection between Odoo and your PoS terminal " +"in Australia, you *must* have a **Stripe** terminal. Odoo supports the " +"**EFTPOS** payment solution in Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:527 +msgid "" +"You do not need a Stripe payment terminal to use Odoo as your main PoS " +"system. The only drawback of not using Stripe is that cashiers must manually" +" enter the final payment amount on the terminal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:532 +msgid ":doc:`Stripe Odoo Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:533 +msgid "" +":doc:`Stripe Odoo Payment Terminal " +"`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:534 +msgid "`Stripe Dashboard `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:535 +msgid "`Stripe Terminal `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:540 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:543 +msgid "Odoo is currently not compliant with STP Phase 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:546 +msgid "Create your employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:548 +msgid "" +"To create an **employee form** and fill in mandatory information, go to the " +"**Employees** app and click :guilabel:`Create`. In the :guilabel:`HR " +"Settings` tab, you can input the mandatory information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:552 +msgid "" +":guilabel:`TFN Status`: if the employee provides a TFN, make sure to add it " +"to the “TFN” field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:553 +msgid ":guilabel:`Non-resident`: if the employee is a foreign resident" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:554 +msgid "" +":guilabel:`Tax-free Threshold`: if the employee is below or above the " +"threshold" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:555 +msgid "" +":guilabel:`HELP / STSL`: for all types of study and training support loans " +"(e.g. HELP, VSL, SSL…)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:556 +msgid ":guilabel:`Medicare levy Deduction`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:557 +msgid ":guilabel:`Medicare levy Exemption`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:558 +msgid ":guilabel:`Withholding for Extra Pay`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:559 +msgid "..." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:562 +msgid "Manage Australian contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:564 +msgid "" +"Once the employee form has been created, ensure the contract is enabled by " +"clicking the :guilabel:`Contracts` smart button or by going to " +":menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:569 +msgid "" +"Only one contract can be active simultaneously per employee, but an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:572 +msgid "" +"Contractual information related to Australia can be found in the following " +"**three** places:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:574 +msgid "" +"Before assigning a salary amount, pay frequency, and other important details" +" to a contract, defining the **salary structure**, **start date**, and " +"**work entry** source is important. In Australia, a \"Salary Structure\" is " +"employed to specify the tax schedule applicable to that contract, as defined" +" by the Australian Taxation Office (ATO). Most contracts will fall under the" +" following **three structures**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:580 +msgid "" +"**Regular (Schedule 1)**: the great majority of Australian employees will " +"fall in this category; hence, this structure is assigned by default to all " +"contracts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:582 +msgid "" +"**Working holiday makers (Schedule 15)**. When employing working holiday " +"makers (WHMs), other taxes apply. For detailed information on these specific" +" tax implications, refer to the documentation provided by the **ATO**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:585 +msgid "" +"**No TFN**. Choose this structure if the employee hasn’t provided a **TFN** " +"for over **28** days." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Employees form in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:592 +msgid "" +"The structures **Horticulture/Shearing (Schedule 2)** and **Artists and " +"Performers (Schedule 3)** are only partially complete, and proper tests " +"should be performed before using them to pay employees in your production " +"database. Send your feedback to au-feedback@mail.odoo.com." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:596 +msgid "" +"The field :guilabel:`Work Entry Source` is also significant and defines how " +"**working hours** and **days** are accounted for in the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:599 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee’s working schedule, starting from the contract's start " +"date.. For example, let’s assume that an employee works 38 hours a week, and" +" their contract’s begins on January 1st. Today is January 16th, and the user" +" generates a pay run from January 14th to 20th. The working hours on the " +"payslip will be automatically calculated to be 38 hours (5 * 7.36 hours) if " +"no leave is taken." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:604 +msgid "" +":guilabel:`Attendances`: The default working schedule is ignored, and work " +"entries are only generated after clocking in and out of the attendance app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:606 +msgid "" +":guilabel:`Planning`: The default working schedule is ignored, and work " +"entries are generated from planning shifts only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:610 +msgid "" +"Additional configurations are necessary to ensure that Odoo’s payslips " +"automatically compute various **penalty rates** as defined by an **award " +"(overtime rate, public holiday rate, etc)**. To create these configurations," +" create new work-entry types for each penalty rate and then assign a penalty" +" rate in % to each. Once this one-time configuration is done, work entries " +"can be manually imported for each period, and Odoo will separate the pay " +"items and rates on the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:618 +msgid "Timesheets do not impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:620 +msgid "" +"The :guilabel:`Salary Information` tab contains a few essential fields " +"impacting the frequency of pay runs and the management of payslip rules in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:623 +msgid "" +":guilabel:`Wage Type`: Select the :guilabel:`Fixed Wage` pay type for full-" +"time and part-time employees. For casual workers and other :guilabel:`Hourly" +" Wage` type. For employees being paid hourly, make sure to define the " +"correct **casual loading**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:626 +msgid "" +":guilabel:`Schedule Pay`: In Australia, only the following pay run " +"frequencies are accepted: **daily, weekly, bi-weekly (or fortnightly), " +"monthly, and quarterly**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:628 +msgid "" +":guilabel:`Wage` (/period): Assign a wage to the contract according to their" +" pay frequency. On payslips, the corresponding annual and hourly rates will " +"be automatically computed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:632 +msgid "" +"For hourly workers, please note that the hourly wage should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:634 +msgid "" +"The :guilabel:`Australia` tab. Most of the fields in this tab are used for " +"**Single Touch Payroll** (or **STP**) reporting, which requires a thorough " +"understanding of several details from an employee’s contract. Review the " +"information on this tab before moving forward with pay runs. This includes " +"the following **four** fields which impact payslip computations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:639 +msgid "" +":guilabel:`Withholding Variation`: use this field in case the employee’s " +"withholding must be varied upward or downward according to their " +"circumstances. E.g., if employee X benefits from a 25% withholding " +"variation, their percentage of tax withheld will vary from whatever amount " +"they were supposed to pay according to their salary structure and situation " +"to a fixed 25%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:643 +msgid "" +":guilabel:`Leave Loading`: if the employee benefits from a regular leave " +"loading, the value set in the field :guilabel:`Leave Loading Rate` (e.g., " +"17.5%) is added to any amount earned when taking annual or long service " +"leaves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:646 +msgid "" +":guilabel:`Salary Sacrifice Superannuation`: any amount added to this field " +"is deducted, per pay frequency, from the employee’s basic salary before the " +"computation of the gross salary. Then, this amount is added to the super " +"guarantee line of their payslip. E.g., if employee Y earns 5,000 AUD per " +"month and sacrifices 300 AUD to superannuation, their gross salary will be " +"4,700 AUD, and 300 AUD will be added on top of their normal super " +"contributions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:651 +msgid "" +":guilabel:`Salary Sacrifice Other`: any amount added to this field is " +"deducted, per pay frequency, from the employee’s basic salary before the " +"computation of the gross salary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:654 +msgid "" +"Once all important information has been entered, ensure the transition of " +"the contract's status from \"New\" to \"Running\" to facilitate its use in " +"pay runs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "\"Australia\" payroll tab in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:661 +msgid "Assign superannuation accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:663 +msgid "" +"Upon receipt of superannuation details from a new employee, ensure the " +"creation of a new account in :menuselection:`Payroll --> Configuration --> " +"Super Accounts` to link it to the employee. Input the :guilabel:`Super " +"Fund`, :guilabel:`Member Since` date, and :guilabel:`TFN` number of the " +"employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:667 +msgid "" +"Suppose the employee uses a superannuation fund that does not exist in the " +"database yet. In that case Odoo creates a new one and centralises basic " +"information about this fund, such as its **ABN**, **address**, type " +"(**APRA** or **SMSF**), **USI**, and **ESA**. Super funds can be created or " +"imported in :menuselection:`Payroll --> Configuration --> Super Funds`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:673 +msgid "Odoo is currently not **SuperStream-compliant**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:676 +msgid "Create pay runs with payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:678 +msgid "" +"Odoo can create pay runs in **two** ways: via **batch** or via " +"**individual** payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:681 +msgid "Create a batch of payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:683 +msgid "" +"When preparing to generate employees’ draft payslips (e.g., at the end of " +"every week, fortnight, or month), navigate to :menuselection:`Payroll --> " +"Payslips --> Batches` and click :guilabel:`New`. Fill in the necessary info," +" click :guilabel:`Generate Payslips`, select the :guilabel:`Salary " +"Structure`, :guilabel:`Department`, :guilabel:`Employees`, and " +":guilabel:`Generate`. This method allows the creation of multiple payslips " +"corresponding to each employee in a single batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:690 +msgid "Give the batch a name. (E.g., `2024 – Weekly W1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:691 +msgid "" +"Choose the pay run's start and end date. (E.g., 01/01/2024 to 07/01/2024)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:692 +msgid "" +"Click on :guilabel:`Generate`. A pop-up window asks to confirm which " +"employees should be included in the batch. By default, all active employees " +"are included. You can leave :guilabel:`Salary Structure` field blank as Odoo" +" automatically selects the structure linked to each employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:696 +msgid "" +"The batch creates as many payslips as there are employees. There is no limit" +" to the number of payslips created in a batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:698 +msgid "" +"Verify important information on each payslip. After payslips from a batch " +"have been generated, there is no need to manually compute payslip lines; " +"Odoo does it for you." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:702 +msgid "Create an individual payslip" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:704 +msgid "" +"In cases where the pay run does not fall into the category of regular " +"payslips, the option exists to create a pay run dedicated to a single " +"employee. Go to :menuselection:`Payroll --> Payslips --> All Payslips` and " +"click :guilabel:`New`. Employ this method when processing **one-time " +"payments** for employees, including **return-to-work** payments (**ATO " +"Schedule 4**), **employment termination** payments (**ATO Schedule 7 and " +"11**), and **commissions and bonuses** (**ATO Schedule 5**). When generating" +" an individual payslip, make sure to proceed with the following steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:711 +msgid "" +"Select an :guilabel:`Employee`; their :guilabel:`Contract` will be filled " +"out automatically" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:712 +msgid "Add a pay :guilabel:`Period`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:713 +msgid "Select a salary :guilabel:`Structure` (e.g., return-to-work payment)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:714 +msgid "" +"Unlike payslips generated from a batch, the payroll user must click the " +":guilabel:`Compute Sheet` button to generate payslip lines" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "One-time payments in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:721 +msgid "Understand payslip features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:723 +msgid "" +"The same features apply no matter how payslips are created (individually or " +"via batch)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:725 +msgid "" +"Depending on how work entries are created, the :guilabel:`Worked Days & " +"Inputs` table automatically shows the number of days and hours the employee " +"worked during the payslip period next to the corresponding total gross " +"amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:730 +msgid "" +"There is one line per work entry type, meaning **paid** and **unpaid time-" +"off**, in addition to custom **hourly penalty rates** (overtime, public " +"holidays, etc.) which are automatically added to the table." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Worked days and hours in Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:737 +msgid "" +"In the :guilabel:`Other Inputs` section, You can add entries such as " +"**allowances** and **extra pay** items in the :guilabel:`Other Inputs` " +"section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:740 +msgid "" +"To incorporate various **allowances** into an employee's payslip, create " +"**allowances** in :menuselection:`Payroll --> Configuration --> Other Input " +"Types`. Once created, tick the :guilabel:`Is an Allowance` checkbox for the " +"involved allowances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:745 +msgid "" +"Withholding for allowances is not computed automatically. The payroll user " +"has to use the field :guilabel:`Withholding for allowance` under the other " +"inputs table to manually add the total amount to be withheld across all " +"allowances on that payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:749 +msgid "" +"**Extra pay** items are other inputs added to the **payslip’s gross** and, " +"as a result, to the **withholding amount**. An example lies in regular sales" +" commissions, taxed at the same rate as the regular salary (unlike " +"discretionary bonuses, which fall under the ATO’s Schedule 5 and its " +"corresponding salary structure). To configure such a custom pay item, go to " +":menuselection:`Payroll --> Configuration --> Other Input Types` and create " +"a new entry with the code **EXTRA**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Extra pay item input type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:759 +msgid "" +"In the :guilabel:`Salary Computation` tab, the payroll user can verify " +"whether all the pay rules have been computed correctly as per employee, " +"contract and salary structure. Here are a few guidelines to better " +"understand the data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Salary computation in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:766 +msgid "" +"**Basic salary:** amount from which tax-deductible lines can be subtracted" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:767 +msgid "" +"**Gross salary:** amount subject to the taxes defined by the salary " +"structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:768 +msgid "**Withholding:** tax amount to be paid to the **ATO**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:769 +msgid "**Net salary:** amount to be paid to the employee’s bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:770 +msgid "" +"**Superannuation Guarantee:** amount to be provisioned for quarterly " +"payments to the employee’s super account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:772 +msgid "" +"**Allowances & Extra pay items:** these lines will show if other inputs are " +"added to the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:773 +msgid "" +"**Other lines:** depending on the employee and contract specifics (Medicare," +" child support, salary, sacrifice, etc.)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:776 +msgid "" +"When satisfied with the payslip, click :guilabel:`Create Draft entry` to " +"generate a draft accounting journal entry that the accountant can review. " +"Note that in the case of a payslip batch, this accounting entry will sum up " +"balances from all payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:781 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:783 +msgid "" +"After a batch or a payslip’s journal entry has been posted, the company can " +"pay their employees. The user can choose between **two** different **payment" +" methods**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:786 +msgid "" +"Pay the employee in batch via **ABA** files. This is **only** possible from " +"the **payslip batch** level. Ensure the batch’s journal entry has been " +"posted to generate the **ABA** file. From the batch form view, click " +":guilabel:`Create ABA File` and choose the desired bank journal. The newly " +"generated **ABA** file becomes available for download in the field " +":guilabel:`ABA File`. It is possible to re-generate the ABA file after " +"applying corrections to existing payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:793 +msgid "" +"It is always possible to include an individual payslip into an existing " +"batch in an **ABA** file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:797 +msgid "" +"An ABA file can only be generated if both the company’s bank account and " +"each employee’s bank account have been properly :ref:`configured " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:800 +msgid "" +"From the employee's payslip (:menuselection:`Payroll --> Payslips`), once " +"the payslip's journal entry has been posted, click :guilabel:`Register " +"Payment`. The process is the same as :doc:`paying vendor bills " +"<../accounting/payments>`: select the desired bank journal and payment " +"method, then later reconcile the payment with the corresponding bank " +"statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:806 +msgid "One-time payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:808 +msgid "" +"Certain payments, such as **Return-to-Work** payments and **Employment " +"Termination Payments** **(ETP)**, are processed only once and require a " +"slightly different approach." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:812 +msgid "Return-to-Work payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:814 +msgid "" +"A **Return-to-Work** payment is a payment made to an employee to resume " +"working. To process one, create an individual payslip, select the employee, " +"and modify its **regular structure** to :guilabel:`Australia: Return to " +"work`. Then, add the **gross amount** of that payment in the " +":guilabel:`Other Inputs` section and compute the payslip. Odoo automatically" +" computes the **PAYG withholding**, the **net amount**, and the **super " +"guarantee** corresponding to that payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Return-to-work payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:824 +msgid "Termination payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:826 +msgid "" +"Before proceeding with the employee’s ETP, make sure that a **Contract End " +"Date** has been set on that employee’s contract so that Odoo can " +"automatically compute the final prorated salary of that employee for the " +"current month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:830 +msgid "" +"First, create the final salary for that employee this month. To do so, " +"create an individual payslip. If the contract end date is set correctly, " +"Odoo will automatically compute the prorated salary up to the final payslip " +"date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Termination payment worked days computation in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:838 +msgid "" +"We recommend creating a batch on the fly for that payslip, in which the ETP " +"is added as a second payslip of that same batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:841 +msgid "" +"Create a second individual payslip and include it in the same batch. Change " +"the salary structure on that payslip to :guilabel:`Australia: Termination " +"Payments`. Before computing the sheet, it is important to provide the " +"payslip with termination details ." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Termination payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:848 +msgid "" +":guilabel:`Genuine` or :guilabel:`Non-Genuine Redundancy`. This choice " +"impacts the amounts and caps defined per **ETP** type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:850 +msgid "" +"**ETP types**: see the full list of termination payment types in " +":guilabel:`Other Input Types` by filtering by `ETP Type is Set`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Payslip other inputs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:856 +msgid "" +"Add the relevant **ETP type** in the :guilabel:`Other Inputs` table of the " +"payslip, then compute the payslip. Odoo computes the **gross ETP**, the " +"**withholding**, the **unused leaves**, and the **net salary** according to " +"the rules defined on the **ETP**, the **employee**, and their **contract**. " +"Once payment for both payslips is ready to be processed, an **ABA** file can" +" be created directly from the batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:865 +msgid "Employment Hero Australian Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:867 +msgid "" +"If your business is already up and running with `Employment Hero " +"`_, you can use our connector as an alternative" +" payroll solution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:870 +msgid "" +"The Employment Hero module synchronises payslip accounting entries (e.g., " +"expenses, social charges, liabilities, taxes) automatically from Employment " +"Hero to Odoo. Payroll administration is still done in Employment Hero. We " +"only record the **journal entries** in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:875 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:880 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Australian " +"Payroll` module (`l10n_au_keypay`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:882 +msgid "" +"Configure the **Employment Hero API** by going to :menuselection:`Accounting" +" --> Configuration --> Settings`. More fields become visible after clicking " +"on :guilabel:`Enable Employment Hero Integration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:890 +msgid "" +"You can find the API Key in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:895 +msgid "" +"The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:898 +msgid "Do not change the **pre-filled Payroll URL**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:900 +msgid "" +"You can find the **Business ID** in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "The Employment Hero \"Business ID\" number is in the URL" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:905 +msgid "You can choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:908 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:910 +msgid "" +"The API syncs the journal entries from Employment Hero to Odoo and leaves " +"them in draft mode. The reference includes the Employment Hero payslip entry" +" ID in brackets for the user to easily retrieve the same record in " +"Employment Hero and Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:917 +msgid "" +"By default, the synchronisation happens once per week. You can fetch the " +"records manually by going to :menuselection:`Accounting --> Configuration " +"--> Settings` and, in the :guilabel:`Enable Employment Hero Integration` " +"option, click on :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:921 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:923 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:928 +msgid "" +"For the API to work, you need to create the same accounts as the default " +"accounts of your Employment Hero business (**same name and same code**) in " +"Odoo. You also need to choose the correct account types in Odoo to generate " +"accurate financial reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:3 +msgid "Austria" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:8 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Austrian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:17 +msgid ":guilabel:`Austria - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:18 +msgid "`l10n_at`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:19 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:19 +msgid "" +"Default :ref:`fiscal localization package `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:20 +msgid ":guilabel:`Austria - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:21 +msgid "`l10n_at_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:22 +msgid "Adds localized versions of financial reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:23 +msgid ":guilabel:`Austrian SAF-T Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:24 +msgid "`l10n_at_saft`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:25 +msgid "Adds the SAF-T export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:30 +msgid "The following localized reports are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:32 +msgid "" +"Balance sheet according to `§ 224 UGB " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:33 +msgid "" +"Profit and loss according to `§ 231 UGB " +"`_" +" (Gesamtkostenverfahren)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:36 +msgid ":doc:`Accounting reporting documentation <../accounting/reporting>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:39 +msgid "SAF-T (Standard Audit File for Tax)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:41 +msgid "" +"The Austrian tax office may request a SAF-T. The Austrian SAF-T Export " +"module allows exporting the report in XML format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:47 +msgid "" +"This section explains how to configure the database to ensure all the " +"information required by the SAF-T is available. If anything is missing, a " +"warning message listing which information is needed will be displayed during" +" the export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:52 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:68 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 +msgid "Company information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:54 +msgid "" +"Open the database :guilabel:`Settings`. Under the :guilabel:`Companies` " +"section, click :guilabel:`Update Info` and ensure the following fields are " +"correctly filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:57 +msgid ":guilabel:`Address`, by providing at least the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:59 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:76 +msgid ":guilabel:`Street`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:60 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +msgid ":guilabel:`City`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:61 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:79 +msgid ":guilabel:`ZIP`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:62 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 +msgid ":guilabel:`Country`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:64 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:82 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 +msgid ":guilabel:`Phone`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:65 +msgid ":guilabel:`Company ID` by providing your company's tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:66 +msgid "" +":guilabel:`Tax ID` by providing, if you have one, your :abbr:`UID-Nummer " +"(Umsatzsteueridentifikationsnummer)` (including the country prefix)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:70 +msgid "Contact person" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:72 +msgid "" +"At least one **contact person** must be linked to your company in the " +":guilabel:`Contacts` app, and:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:74 +msgid "Ensure the contact type is set to :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:75 +msgid "Select your company in the :guilabel:`Company name` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:76 +msgid "" +"Provide at least one phone number using the :guilabel:`Phone` or " +":guilabel:`Mobile` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:79 +msgid "Customer and supplier information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:81 +msgid "" +"Using the :guilabel:`Contacts` app, fill in the :guilabel:`Address` of any " +"partner that appears in your invoices, vendor bills, or payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:84 +msgid "" +"For partners that are companies, fill in the VAT number (including the " +"country prefix) in the :guilabel:`Tax ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:88 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +msgid "Accounting settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:90 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Austrian localization` section, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:93 +msgid ":guilabel:`ÖNACE-Code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:94 +msgid ":guilabel:`Profit Assessment Method`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:97 +msgid "" +"`ÖNACE information on the Austrian Economic Chambers website " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:101 +msgid "Chart of accounts mapping" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:103 +msgid "" +"The Austrian SAF-T specifications define a chart of accounts (COA). All " +"relevant accounts for the SAF-T export must be annotated with a fitting " +"account from this COA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:106 +msgid "" +"The needed mapping information is supplied by adding tags to the accounts. " +"For example, adding the `1000` tag to an account maps it (virtually) to the " +"SAF-T COA account with the code `1000`. Any number can be used as long as " +"there is an account in the SAF-T COA with that code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:110 +msgid "" +"The :guilabel:`Austria - Accounting` module adds a tag for each SAF-T COA " +"account. Furthermore, it automatically maps many accounts from the default " +"Austrian COA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:113 +msgid "" +"You can try exporting the SAF-T report to check if there are unmapped " +"accounts (or mapped to multiple SAF-T accounts). A warning will be displayed" +" if there is any issue with your configuration or the mapping. Clicking " +":guilabel:`View Problematic Accounts` lets you view them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:118 +msgid "" +":doc:`Chart of accounts documentation " +"<../accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:121 +msgid "Exporting the SAF-T report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:123 +msgid "" +"To export the SAF-T report, go to :menuselection:`Accounting --> Reports -->" +" General Ledger`. Click the right side of the :guilabel:`PDF` button and " +"select :guilabel:`SAF-T`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst-1 +msgid "The SAF-T button to export the file in XML format" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 +msgid "" +"Install the :guilabel:`🇧🇪 Belgium` :ref:`fiscal localization package " +"` to get all the default accounting features " +"of the Belgian localization, following the :abbr:`IFRS(International " +"Financial Reporting Standards)` rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 +msgid "" +"You can reach the :guilabel:`Chart of accounts` by going to " +":menuselection:`Accounting --> Configuration --> Accounting: Chart of " +"Accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:22 +msgid "" +"The Belgian chart of accounts includes pre-configured accounts as described " +"in the :abbr:`PCMN(Plan Comptable Minimum Normalisé)`. To add a new account," +" click :guilabel:`New`. A new line appears. Fill it in, click " +":guilabel:`Save`, and then :guilabel:`Setup` to configure it further." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:34 +msgid "" +"Default Belgian taxes are created automatically when the :guilabel:`Belgium " +"- Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are " +"installed. Each tax impacts the Belgian :guilabel:`Tax Report`, available by" +" going to :menuselection:`Accounting --> Reporting --> Statements Reports: " +"Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +msgid "" +"In Belgium, the standard VAT rate is **21%**, but there are lower rates for " +"some categories of goods and services. An intermediate rate of **12%** is " +"applied on social housing and food served in restaurants, while a reduced " +"rate of **6%** applies to most basic goods, such as food, water supply, " +"books, and medicine. A **0%** rate applies to some exceptional goods and " +"services, such as some daily and weekly publications, as well as recycled " +"goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +msgid "Non-deductible taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +msgid "" +"In Belgium, some taxes are not fully deductible, such as taxes on the " +"maintenance of cars. This means a part of these taxes is considered as an " +"expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +msgid "" +"In Odoo, you can configure non-deductible taxes by creating tax rules for " +"these taxes and linking them to the corresponding accounts. This way, the " +"system automatically calculates the taxes and allocates them to the " +"appropriate accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:57 +msgid "" +"To configure a new non-deductible tax, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Taxes`, and click :guilabel:`New`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:60 +msgid "" +":guilabel:`Add a line` and select :guilabel:`Base` in the :guilabel:`Based " +"On` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:61 +msgid "" +":guilabel:`Add a line`, then select :guilabel:`on tax` in the " +":guilabel:`Based on` column and enter the **non-deductible** percentage in " +"the :guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:63 +msgid "" +"On the :guilabel:`of tax` line, select the :guilabel:`Tax Grid(s)` related " +"to your tax;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +msgid "" +":guilabel:`Add a line` with the **deductible** percentage in the " +":guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:65 +msgid "Set :guilabel:`of tax` in :guilabel:`Based On`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +msgid "" +"Select :guilabel:`411000 VAT recoverable` as account, and select the related" +" tax grid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 +msgid "" +"Once you have created a non-deductible tax, you can apply it to your " +"transactions by selecting the appropriate tax during the encoding of bills " +"and credit notes. The system automatically calculates the tax amount and " +"allocates it to the corresponding accounts based on the tax rules " +"configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 +msgid "" +"With the Belgian localization, the **21% car** tax is created by default " +"(50% non-deductible)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Example of not-fully deductible tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:80 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:50 +msgid ":doc:`../accounting/reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:87 +msgid "Here is the list of Belgian-specific reports available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:89 +msgid "Balance sheet;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:90 +msgid "Profit & loss;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:91 +msgid "Tax report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:92 +msgid "Partner VAT Listing;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:93 +msgid "EC Sales List;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:94 +msgid "Intrastat." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:96 +msgid "" +"You can access Belgian-specific versions of reports by clicking on the " +"**book** icon when on a report and selecting its Belgian version: **(BE)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Belgian version of reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:103 +msgid ":doc:`../accounting/reporting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:108 +msgid "Disallowed expenses report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:110 +msgid "" +"**Disallowed expenses** are expenses that can be deducted from your " +"accounting result but not from your fiscal result." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:113 +msgid "" +"The **disallowed expenses report** is available by going to " +":menuselection:`Accounting --> Reporting --> Management: Disallowed " +"Expenses`. It allows financial results in real-time, and periodic changes. " +"This report is generated based on the **disallowed expenses categories** " +"that you can reach by going to :menuselection:`Accounting --> Configuration " +"--> Management: Disallowed Expenses Categories`. Some categories already " +"exist by default but do not have any rates. Click on :guilabel:`Set Rates` " +"to update a specific category." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:121 +msgid "" +"You can add multiple rates for various dates. In that case, the rate used to" +" calculate the expense depends on the date at which it is calculated, and " +"the rate set for that date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:123 +msgid "" +"If you have the **Fleet** app installed, tick the :guilabel:`Car Category` " +"box when applicable. This makes the vehicle mandatory while booking a vendor" +" bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:126 +msgid "" +"To link a disallowed expenses category with a specific account, go to " +":menuselection:`Accounting --> Configuration --> Acounting: Chart of " +"Accounts`. Find the account you want, and click on :guilabel:`Setup`. Add " +"the :guilabel:`Disallowed Expense category` in the :guilabel:`Disallowed " +"Expenses` field. From now, when an expense is created with this account, the" +" disallowed expense is calculated based on the rate mentioned in the " +":guilabel:`Disallowed Expense category`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:132 +msgid "Let's take an example reflecting **restaurant** and **car expenses**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:137 +msgid "Restaurant expenses" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:139 +msgid "" +"In Belgium, 31% of **restaurant** expenses are non-deductible. Create a new " +"**disallowed expenses category** and set both :guilabel:`Related Account(s)`" +" and :guilabel:`Current Rate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Disallowed expenses categories" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:148 +msgid "Car expenses: vehicle split" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:150 +msgid "" +"In Belgium, the deductible percentage varies from car to car and, therefore," +" should be indicated for each vehicle. To do so, open :menuselection:`Fleet`" +" and select a vehicle. In the :guilabel:`Tax info` tab, go to the " +":guilabel:`Disallowed Expenses Rate` section and click on :guilabel:`Add a " +"line`. Add a :guilabel:`Start Date` and a :guilabel:`%`. The amounts go in " +"the same account for all car expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:156 +msgid "" +"When you create a bill for car expenses, you can link each expense to a " +"specific car by filling the :guilabel:`Vehicle` column, so the right " +"percentage is applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:162 +msgid "" +"The :guilabel:`vehicle split` option available in the disallowed expenses " +"report allows you to see the rate and disallowed amount for each car." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:171 +msgid "Fee form 281.50 and form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:176 +msgid "Fee form 281.50" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:178 +msgid "" +"Annually, a **281.50 fee form** must be reported to the fiscal authorities. " +"To do so, the tag `281.50` must be added on the **contact form** of the " +"entities concerned by the **281.50** fee. To add the tag, open " +":menuselection:`Contacts`, select the person or company you want to create a" +" **281.50 fee form** for, and add the `281.50` tag in the :guilabel:`Tags` " +"field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "add the tag 281.50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:187 +msgid "" +"Make sure the **street, zip code, country**, and **VAT number** are also " +"informed on the **Contact form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:190 +msgid "" +"Then, depending on the nature of the expense, add the corresponding `281.50`" +" tag on the impact accounts. To do so, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Chart of Accounts`, and click on " +":guilabel:`Setup` to add the corresponding `281.50` tag on the impacted " +"accounts, i.e., :guilabel:`281.50 - Commissions`, depending on the nature of" +" the expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:198 +msgid "Form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:200 +msgid "" +"You can create a **325 form** by going to :menuselection:`Accounting --> " +"Reporting --> Belgium: Create 325 form`. A new page pops up: select the " +"right options and click :guilabel:`Generate 325 form`. To open an already " +"generated **325 form**, go to :menuselection:`Accounting --> Reporting --> " +"Belgium: Open 325 forms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Add the tag 281-50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:211 +msgid "CODA and SODA statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:216 +msgid "CODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:218 +msgid "" +"**CODA** is an electronic XML format used to import Belgian bank statements." +" You can download CODA files from your bank and import them directly into " +"Odoo by clicking :guilabel:`Import Statement` from your :guilabel:`Bank` " +"journal on your dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Import CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:226 +msgid ":ref:`Import bank statements files `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:231 +msgid "SODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:233 +msgid "" +"**SODA** is an electronic XML format used to import accounting entries " +"related to salaries. SODA files can be imported into the journal you use to " +"record salaries by going to your Accounting **dashboard** and clicking " +":guilabel:`Upload` in the related journal card form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:237 +msgid "" +"Once your **SODA** files are imported, the entries are created automatically" +" in your 'salary' journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Import SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:246 +msgid "CodaBox" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:248 +msgid "" +"**CodaBox** is a service that allows Belgian accounting firms accessing " +"their clients' bank information and statements. Odoo provides a way to " +"import such statements automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:252 +msgid "" +"As an accounting firm, you must manage your clients on separate databases " +"and configure them individually to avoid mixing up their data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:258 +msgid "" +"The configuration must be done on each client database. In the following " +"instructions, we will refer to your client's company as *Company* and to " +"your accounting firm as *Accounting Firm*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:262 +msgid "" +"You must first :ref:`Install ` :guilabel:`CodaBox` and " +":guilabel:`CodaBox Bridge` to start." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:266 +msgid "" +"Make sure the company settings are correctly configured, i.e., the country " +"is set to :guilabel:`Belgium`, the :guilabel:`Tax ID` and " +":guilabel:`Accounting Firm` fields are filled, as well as the :guilabel:`Tax" +" ID` of the accounting firm (unless it is the same as the company's " +":guilabel:`Tax ID`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:272 +msgid "Configure the Journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:276 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:351 +msgid "For CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:278 +msgid ":doc:`Create a new bank journal <../accounting/bank>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:279 +msgid "Set the right IBAN in the :guilabel:`Account Number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:280 +msgid "" +"Select :guilabel:`CodaBox synchronisation` as the :guilabel:`Bank Feed`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a CODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:286 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:361 +msgid "For SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:288 +msgid "Create a new miscellaneous journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:289 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 +msgid "Select the journal you just created in the SODA journal field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a SODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:299 +msgid "Configure the Connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:301 +msgid "" +"First, you must select which users can access the **CodaBox** connection " +"settings. To do so, go to :menuselection:`Settings --> Users & Companies -->" +" Groups`, and search for the group :guilabel:`Allow to show and modify the " +"CodaBox Connection Settings`. Add the users you want to this group. By " +"default, only the :guilabel:`Administrator` is part of this group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:306 +msgid "" +"Then, to configure the connection itself, go to :menuselection:`Accounting " +"--> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:309 +msgid "" +"The procedure differs depending on whether **CodaBox** is being setup for a " +"first client or an additional one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 +msgid "First connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:316 +msgid "" +"Click on :guilabel:`Connect`, where you are redirected to the **CodaBox** " +"platform, here validate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:318 +msgid "" +"Once redirected back to Odoo, the :guilabel:`Status` should be set to " +":guilabel:`Connected` and a new field :guilabel:`Access Token` should " +"appear." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configured connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 +msgid "" +"This :guilabel:`Access Token` will be used to create new connections for " +"other clients without having to validate the connection again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:329 +msgid "Following connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:331 +msgid "Copy the :guilabel:`Access Token` from a previous connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 +msgid "Click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +msgid "" +"The **CodaBox** connection linked to the :guilabel:`Access Token` should " +"still exist, therefore there is no need to validate the connection again. A " +"new and different :guilabel:`Access Token` is generated, and the " +":guilabel:`Status` should be set to :guilabel:`Connected`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:340 +msgid "" +"By having a different :guilabel:`Access Token` for each client, you can " +"easily revoke the access of a client to your CodaBox account without " +"affecting the other clients. One client cannot interfere with another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 +msgid "Synchronisation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:347 +msgid "" +"Once the connection is established, Odoo can be synchronized with CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:353 +msgid "" +"CODA files are automatically imported from CodaBox every 12 hours. You do " +"not have to do anything. However, if you wish, it can also be done manually," +" by clicking on :guilabel:`Fetch CODA's` in the Accounting Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch CODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:363 +msgid "" +"SODA files are automatically imported from CodaBox once a day as draft. You " +"do not have to do anything. However, if you wish, it can also be done " +"manually, by clicking on :guilabel:`Fetch SODA's` in the Accounting " +"Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 +msgid "" +"By default, if an account in the SODA is not mapped to an account in Odoo, " +"the Suspense Account (499000) is used and a note is left in the created " +"journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch SODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 +msgid "" +"You can access the mapping between the SODA accounts and the Odoo accounts " +"by clicking on the :guilabel:`SODA Mapping` button in " +":menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:380 +msgid "" +"The connection between Odoo and CodaBox can be revoked by using the " +":guilabel:`Revoke` button in the CodaBox settings, which will revoke the " +"link on Odoo's side only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:384 +msgid "" +"If you have multiple connections, you will still be able to use the Access " +"Token of one of them to easily reconnect Odoo and CodaBox for another " +"client." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:388 +msgid "" +"However, if you have only one (remaining) connection, you will not be able " +"to use its Access Token to create new connections. In that case, you will " +"have to revoke the connection from the CodaBox platform too, and then " +"recreate a new one following the steps in the :ref:`first connection " +"` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 +msgid "Potential issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "CodaBox is not configured. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "Either the Company VAT of the Accounting Firm VAT is not set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "" +"It seems that the fiduciary VAT number you provided is not valid. Please " +"check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "" +"Either the Company VAT of the Accounting Firm VAT is in the wrong format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "" +"It seems that the fiduciary VAT number you provided does not exist in " +"CodaBox. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "" +"The Accounting Firm VAT number you provided is not registered in CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 +msgid "Error while connecting to the IAP server. Please contact Odoo support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:407 +msgid "" +"It seems that Odoo's IAP server is down or unreachable. Please contact Odoo " +"support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:414 +msgid "" +"It seems that your CodaBox connection is not valid anymore. Please check " +"your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 +msgid "" +"It seems that you have either revoked the access of Odoo to your CodaBox " +"account, or that you have not completed the configuration process. In this " +"case, you must click on the :guilabel:`Revoke connection` button in the " +"settings, and follow again the steps in the :ref:`first connection " +"` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:423 +msgid "" +"A previous CodaBox registration already exists. Paste the access token from " +"a previous connection here. Odoo will generate a new one, exclusive to this " +"database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 +msgid "" +"It seems that you have already your Accounting Firm with Odoo, but that the " +"Access Token is either not filled or wrong. You should follow the steps in " +"the :ref:`following connection ` " +"tab section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 +msgid "" +"If you have lost your Access Token, you have to go on the CodaBox platform, " +"and revoke the access of Odoo to your CodaBox account. Then, you will have " +"to follow the steps in the :ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "" +"The provided access token is not valid for this fiduciary. Please check your" +" configuration. If you have lost your access token, please contact Odoo " +"support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "Same as above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:433 +msgid "" +"It seems that no connection linked to your database/VAT number exists. " +"Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 +msgid "" +"You may obtain this error when revoking or trying to fetch files from " +"CodaBox if the pair (Accounting Firm VAT, Company VAT) is not registered " +"yet. This may happen if you have changed the company VAT after the " +"connection was established for instance. For security reasons, you have to " +"recreate a connection for this company VAT by following the steps in the " +":ref:`first connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:438 +msgid "No files were found. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 +msgid "" +"This may occur if the company VAT has changed after the connection was " +"established. In that case, you must click on the :guilabel:`Revoke " +"connection` button in the settings, and recreate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:443 +msgid "" +"It seems you have already created a connection to CodaBox with this " +"fiduciary. To create a new connection, you must first revoke the old one on " +"myCodaBox portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:441 +msgid "" +"You must go on the CodaBox platform, and revoke the access of Odoo to your " +"CodaBox account. Then, you will have to follow the steps in the :ref:`first " +"connection ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:446 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 +msgid "Electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:448 +msgid "" +"Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing " +"format. To enable it for a customer, go to :menuselection:`Accounting --> " +"Customers --> Customers`, open their contact form, and under the " +":guilabel:`Accounting` tab, select the :guilabel:`Peppol BIS Billing 3.0` " +"format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:453 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:94 +msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 +msgid "Cash discount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:460 +msgid "" +"In Belgium, if an early payment discount is offered on an invoice, the tax " +"is calculated based on the discounted total amount, whether the customer " +"benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 +msgid "" +"To apply the right tax amount and report it correctly in your VAT return, " +"set the tax reduction as :guilabel:`Always (upon invoice)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:467 +msgid ":doc:`../accounting/customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 +msgid "Fiscal certification: POS restaurant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:474 +msgid "" +"In Belgium, the owner of a cooking business such as a restaurant or food " +"truck is required by law to use a government-certified **Cash Register " +"System** for their receipts. This applies if their yearly earnings " +"(excluding VAT, drinks, and take-away food) exceed 25,000 euros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 +msgid "" +"This government-certified system entails the use of a :ref:`certified POS " +"system `, along with a device called a :ref:`Fiscal " +"Data Module ` (or **black box**) and a :ref:`VAT Signing Card " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:483 +msgid "" +"Do not forget to register as *foodservice industry manager* on the `Federal " +"Public Service Finance registration form " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:489 +msgid "Certified POS system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:491 +msgid "" +"The Odoo POS system is certified for the major versions of databases hosted " +"on **Odoo Online** and **Odoo.sh**. Please refer to the following table to " +"ensure that your POS system is certified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:499 +#: ../../content/applications/finance/payment_providers/stripe.rst:17 +msgid "Odoo Online" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:500 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:501 +msgid "On-Premise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:502 +msgid "Odoo 16.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:503 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:504 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:511 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:512 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:515 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:516 +msgid "Certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:505 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:507 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:508 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:509 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:513 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:517 +msgid "Not certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:506 +msgid "Odoo 15.2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:510 +msgid "Odoo 15.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:514 +msgid "Odoo 14.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:520 +msgid ":doc:`/administration/maintain/supported_versions`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:522 +msgid "" +"A `certified POS system " +"`_ must " +"adhere to rigorous government regulations, which means it operates " +"differently from a non-certified POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 +msgid "On a certified POS, you cannot:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:528 +msgid "" +"Set up and use the **global discounts** feature (the `pos_discount` module " +"is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:530 +msgid "" +"Set up and use the **loyalty programs** feature (the `pos_loyalty` module is" +" blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 +msgid "" +"Reprint receipts (the `pos_reprint` module is blacklisted and cannot be " +"activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:533 +msgid "Modify prices in order lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 +msgid "Modify or delete order lines in POS orders." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:535 +msgid "Sell products without a valid VAT number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 +msgid "Use a POS that is not connected to an IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:538 +msgid "" +"The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` " +"feature must be activated and set to a :guilabel:`Rounding Precision` of " +"`0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:541 +msgid "" +"Taxes must be set as included in the price. To set it up, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, and from the " +":guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form " +"by clicking the arrow next to the default sales tax field. There, click " +":guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:545 +msgid "" +"At the start of a POS session, users must click :guilabel:`Work in` to clock" +" in. Doing so allows the registration of POS orders. If users are not " +"clocked in, they cannot make POS orders. Likewise, they must click " +":guilabel:`Work Out` to clock out at the end of the session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:550 +msgid "" +"If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you " +"cannot use it again without it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:556 +msgid "Fiscal Data Module (FDM)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:558 +msgid "" +"An FDM, or **black box**, is a government-certified device that works " +"together with the Point of Sale application and saves your POS orders " +"information. Concretely, a **hash** (:dfn:`unique code`) is generated for " +"each POS order and added to its receipt. This allows the government to " +"verify that all revenue is declared." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:564 +msgid "" +"Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 " +"`_ is supported by Odoo. `Contact the manufacturer" +" (GCV BMC) `_ to order one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:572 +msgid "" +"Before setting up your database to work with an FDM, ensure you have the " +"following hardware:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:574 +msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 +msgid "an RS-232 serial null modem cable per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:576 +msgid "an RS-232 serial-to-USB adapter per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:577 +msgid "an :ref:`IoT Box ` (one IoT box per FDM); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:578 +msgid "a receipt printer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:583 +msgid "Black box module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:585 +msgid "" +"As a pre-requisite, :ref:`activate ` the `Belgian " +"Registered Cash Register` module (technical name: `pos_blackbox_be`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "black box modules for belgian fiscal certification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:591 +msgid "" +"Once the module is activated, add your VAT number to your company " +"information. To set it up, go to :menuselection:`Settings --> Companies --> " +"Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national " +"registration number for every staff member who operates the POS system. To " +"do so, go to the :guilabel:`Employees` app and open an employee form. There," +" go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and " +"fill in the :guilabel:`INSZ or BIS number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "ISNZ or BIS number field on employee form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:601 +msgid "" +"To input your information, click on your avatar, go to :menuselection:`My " +"Profile --> Preference tab`, and enter your INSZ or BIS number in the " +"designated field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:605 +msgid "" +"You must configure the :abbr:`FDM (Fiscal Data Module)` directly in the " +"production database. Utilizing it in a testing environment may result in " +"incorrect data being stored within the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:611 +msgid "IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:613 +msgid "" +"In order to use an :abbr:`FDM (Fiscal Data Module)`, you need a registered " +"IoT Box. To register your IoT box, you must contact us through our `support " +"contact form `_ and provide the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:617 +msgid "your VAT number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:618 +msgid "your company's name, address, and legal structure; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:619 +msgid "the Mac address of your IoT Box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:621 +msgid "" +"Once your IoT box is certified, :doc:`connect " +"<../../productivity/iot/config/connect>` it to your database. To verify that" +" the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the " +":guilabel:`IOT Device` section, which should display the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Hardware status page on a registered IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:628 +msgid "" +"Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale" +" --> Configuration --> Point of Sale`, select your POS, scroll down to the " +":guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. " +"Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:633 +msgid "" +"To be able to use an FDM, you must at least connect one :guilabel:`Receipt " +"Printer`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:638 +msgid "VAT signing card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:640 +msgid "" +"When you open a POS session and make your initial transaction, you are " +"prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`." +" The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` " +"upon `registration " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:3 +msgid "Brazil" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:12 +msgid "" +"With the Brazilian localization, sales taxes can be automatically computed " +"and electronic invoices (NF-e) for goods can be sent using AvaTax (Avalara) " +"through |API| calls. Moreover, taxes for services can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:16 +msgid "" +"For the goods tax computation and electronic invoicing process, you need to " +"configure the :ref:`contacts `, :ref:`company " +"`, :ref:`products `, and :ref:`create an " +"account in Avatax ` need to be configured in the " +"general settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:21 +msgid "" +"For the services taxes, you can create and configure them from Odoo directly" +" without computing them with AvaTax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:24 +msgid "" +"The localization also includes taxes and a chart of accounts template that " +"can be modified if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:30 +msgid "" +"Install the :guilabel:`🇧🇷 Brazil` :ref:`fiscal localization package " +"` to get all the default accounting features " +"of the Brazilian localization, following the :abbr:`IFRS (International " +"Financial Reporting Standards)` rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:39 +msgid "" +"To configure your company information, go to the :menuselection:`Contacts` " +"app and search the name given to your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 +msgid "" +"Select the :guilabel:`Company` option at the top of the page. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:45 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:245 +msgid ":guilabel:`Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:46 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:246 +msgid "" +":guilabel:`Address` (add :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip" +" Code`, :guilabel:`Country`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:49 +msgid "" +"In the :guilabel:`Street` field, enter the street name, number, and any " +"additional address information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:51 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:250 +msgid "In the :guilabel:`Street 2` field, enter the neighborhood." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:53 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:252 +msgid ":guilabel:`Identification Number` (:guilabel:`CNPJ`, :guilabel:`CPF`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:54 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:253 +msgid ":guilabel:`Tax ID` (associated with the identification type)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:55 +msgid ":guilabel:`IE` (State registration)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:56 +msgid ":guilabel:`IM` (Municipal registration)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:57 +msgid "" +":guilabel:`SUFRAMA code` (Superintendence of the Manaus Free Trade Zone - " +"add if applicable)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:58 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:257 +msgid ":guilabel:`Phone`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:59 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:258 +msgid ":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Company configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 +msgid "" +"Configure the :guilabel:`Fiscal Information` within the :guilabel:`Sales and" +" Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:66 +msgid "" +"Add the :guilabel:`Fiscal Position` for :ref:`Avatax Brazil `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:67 +msgid ":guilabel:`Tax Regime` (Federal Tax Regime)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:68 +msgid "" +":guilabel:`ICMS Taxpayer Type` (indicates ICMS regime, Exempt status, or " +"Non-Taxpayer)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:69 +msgid ":guilabel:`Main Activity Sector`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Company fiscal configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:74 +msgid "Finally, upload a company logo and save the contact" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:77 +msgid "" +"If you are a simplified regime, you need to configure the ICMS rate under " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes --> " +"Avatax Brazil`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:83 +msgid "Configure AvaTax integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 +msgid "" +"Avalara AvaTax is a tax calculation and electronic invoicing provider that " +"can be integrated in Odoo to automatically compute taxes by taking into " +"account the company, contact (customer), product, and transaction " +"information to retrieve the correct tax to be used and process the e-invoice" +" afterward with the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:90 +msgid "" +"Using this integration requires :doc:`In-App-Purchases (IAPs) " +"<../../general/in_app_purchase>` to compute the taxes and to send the " +"electronic invoices. Whenever you compute taxes, an |API| call is made using" +" credits from your |IAP| credits balance." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 +msgid "Odoo is a certified partner of Avalara Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:100 +msgid "" +"To activate AvaTax in Odoo, you need to create an account. To do so, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and in" +" the :guilabel:`AvaTax Brazil` section, add the administration email address" +" to be used for the AvaTax portal in the :guilabel:`Avatax Portal Email`, " +"and then click on :guilabel:`Create account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:106 +msgid "" +"When **testing** an :guilabel:`Avatax Portal Email` integration in a testing" +" or sandbox database, use an alternate email address. It is **not** possible" +" to re-use the same email address on the production database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:110 +msgid "" +"After you create the account from Odoo, you need to go to the Avalara Portal" +" to set up your password:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:113 +msgid "" +"Access the `Avalara portal `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:114 +msgid "Click on :guilabel:`Meu primeiro acesso`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:115 +msgid "" +"Add the email address you used in Odoo to create the Avalara/Avatax account," +" and then click :guilabel:`Solicitar Senha`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:117 +msgid "" +"You will receive an email with a token and a link to create your password. " +"Click on this link and copy-paste the token to allocate your desired " +"password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:121 +msgid "" +"You can start using AvaTax in Odoo for tax computation **only** without " +"creating a password and accessing the Avalara portal in the Odoo database. " +"However, in order to use the electronic invoice service, you **must** access" +" the AvaTax portal and upload your certificate there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Avatax account configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:129 +msgid "" +"You can transfer |API| credentials. Use this only when you have already " +"created an account in another Odoo instance and wish to reuse it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:133 +msgid "A1 certificate upload" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:135 +msgid "" +"In order to issue electronic invoices, a certificate needs to be uploaded to" +" the `AvaTax portal `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:138 +msgid "" +"The certificate will be synchronized with Odoo, as long as the external " +"identifier number in the AvaTax portal matches - without special characters " +"- with the CNPJ number, and the identification number (CNPJ) in Odoo matches" +" with the CNPJ in AvaTax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:148 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"is installed by default as part of the data set included in the localization" +" module. The accounts are mapped automatically in their corresponding taxes," +" and the default account payable and account receivable fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:153 +msgid "" +"The chart of accounts for Brazil is based on the SPED CoA, which gives a " +"baseline of the accounts needed in Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:250 +msgid "You can add or delete accounts according to the company's needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:161 +msgid "" +"In Brazil, a *series* number is linked to a sequence number range for " +"electronic invoices. The series number can be configured in Odoo on a sales " +"journal from the :guilabel:`Series` field. If more than one series is " +"needed, then a new sales journal will need to be created and a new series " +"number assigned to it for each series needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:166 +msgid "" +"The :guilabel:`Use Documents` field needs to be selected. When issuing " +"electronic and non-electronic invoices, the :guilabel:`Type` field selects " +"the document type used when creating the invoice. The :guilabel:`Type` field" +" will only be displayed if the :guilabel:`Use Documents` field is selected " +"on the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Journal configuration with the Use Documents? field checked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:175 +msgid "" +"When creating the journal, ensure the field :guilabel:`Dedicated Credit Note" +" Sequence` is unchecked, as in Brazil, sequences between invoices, credit " +"notes, and debit notes are shared per series number, which means per " +"journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:182 +msgid "" +"Taxes are automatically created when installing the Brazilian localization. " +"Taxes are already configured, and some of them are used by Avalara when " +"computing taxes on the sales order or invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:185 +msgid "" +"Taxes can be edited, or more taxes can be added. For example, some taxes " +"used for services need to be manually added and configured, as the rate may " +"differ depending on the city where you are offering the service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:190 +msgid "" +"Taxes attached to services are not computed by AvaTax. Only goods taxes are " +"computed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:192 +msgid "" +"When configuring a tax used for a service that is included in the final " +"price (when the tax is not added or subtracted on top of the product price)," +" set the :guilabel:`Tax Computation` to :guilabel:`Percentage of Price Tax " +"Included`, and, on the :guilabel:`Advanced Options` tab, check the " +":guilabel:`Included in Price` option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Tax configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:201 +msgid "" +"Do not delete taxes, as they are used for the AvaTax tax computation. If " +"deleted, Odoo creates them again when used in an |SO| or invoice and " +"computing taxes with AvaTax, but the account used to register the tax needs " +"to be re-configured in the tax's :guilabel:`Definition` tab, under the " +":guilabel:`Distribution for invoices` and :guilabel:`Distribution for " +"refunds` sections." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:207 +msgid ":doc:`Taxes functional documentation <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:212 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:253 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:820 +msgid "Products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:214 +msgid "" +"To use the AvaTax integration on sale orders and invoices, first specify the" +" following information on the product:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:217 +msgid "" +":guilabel:`CEST Code` (Code for products subject to ICMS tax substitution)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 +msgid "" +":guilabel:`Mercosul NCM Code` (Mercosur Common Nomenclature Product Code)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:219 +msgid "" +":guilabel:`Source of Origin` (Indicates the origin of the product, which can" +" be foreign or domestic, among other possible options depending on the " +"specific use case)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 +msgid "" +":guilabel:`SPED Fiscal Product Type` (Fiscal product type according to SPED " +"list table)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:222 +msgid "" +":guilabel:`Purpose of Use` (Specify the intended purpose of use for this " +"product)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Product configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:228 +msgid "" +"Odoo automatically creates three products to be used for transportation " +"costs associated with sales. These are named `Freight`, `Insurance`, and " +"`Other Costs`. They are already configured, if more need to be created, " +"duplicate and use the same configuration (configuration needed: " +":guilabel:`Product Type` `Service`, :guilabel:`Transportation Cost Type` " +"`Insurance`, `Freight`, or `Other Costs`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:265 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:40 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:239 +msgid "" +"Before using the integration, specify the following information on the " +"contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:241 +msgid "General information about the contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:243 +msgid "" +"Select the :guilabel:`Company` option for a contact with a tax ID (CNPJ), or" +" check :guilabel:`Individual` for a contact with a CPF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:249 +msgid "" +"In the :guilabel:`Street` field, enter the street, number, and any extra " +"address information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:254 +msgid ":guilabel:`IE`: state tax identification number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:255 +msgid ":guilabel:`IM`: municipal tax identification number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:256 +msgid ":guilabel:`SUFRAMA code`: SUFRAMA registration number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:264 +msgid "" +"The :guilabel:`CPF`, :guilabel:`IE`, :guilabel:`IM`, and :guilabel:`SUFRAMA " +"code` fields are are hidden until the :guilabel:`Country` is set to " +"`Brazil`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 +msgid "" +"Fiscal information about the contact under the :guilabel:`Sales \\& " +"Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:269 +msgid "" +":guilabel:`Fiscal Position`: add the AvaTax fiscal position to automatically" +" compute taxes on sale orders and invoices automatically" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:271 +msgid ":guilabel:`Tax Regime`: federal tax regime" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:272 +msgid "" +":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is " +"within the ICMS regime, if it is exempt, or if it is a non-taxpayer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:274 +msgid "" +":guilabel:`Main Activity Sector`: list of main activity sectors of the " +"contact" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Contact fiscal configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:282 +msgid "Fiscal positions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:284 +msgid "" +"To compute taxes and send electronic invoices on sale orders and invoices, " +"both the :guilabel:`Detect Automatically` and the :guilabel:`Use AvaTax API`" +" options need to be enabled in the :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:288 +msgid "" +"The :guilabel:`Fiscal Position` can be configured on the contact or selected" +" when creating a sales order or an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Fiscal position configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 +msgid "Workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:297 +msgid "" +"This section provides an overview of the actions that trigger `API calls " +"`_ for tax computation, and how to send " +"an electronic invoice for goods (NF-e) for government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:302 +msgid "" +"Please note that each |API| call incurs a cost. Be mindful of the actions " +"that trigger these calls to manage costs effectively." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 +msgid "Tax calculations on quotations and sales orders" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:311 +msgid "" +"Trigger an |API| call to calculate taxes on a quotation or sales order " +"automatically with AvaTax in any of the following ways:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:314 +msgid "**Quotation confirmation**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:315 +msgid "Confirm a quotation into a sales order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:316 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:332 +msgid "**Manual trigger**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:317 +msgid "Click on :guilabel:`Compute Taxes Using Avatax`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:318 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:334 +msgid "**Preview**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:319 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:335 +msgid "Click on the :guilabel:`Preview` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:320 +msgid "**Email a quotation / sales order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:321 +msgid "Send a quotation or sales order to a customer via email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:324 +msgid "**Online quotation access**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:323 +msgid "" +"When a customer accesses the quotation online (via the portal view), the " +"|API| call is triggered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:327 +msgid "Tax calculations on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:329 +msgid "" +"Trigger an |API| call to calculate taxes on a customer invoice automatically" +" with AvaTax any of the following ways:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:333 +msgid "Click on :guilabel:`Compute Taxes Using AvaTax`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +msgid "**Online invoice access**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +msgid "" +"When a customer accesses the invoice online (via the portal view), the |API|" +" call is triggered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:340 +msgid "" +"The :guilabel:`Fiscal Position` must be set to `Automatic Tax Mapping " +"(Avalara Brazil)` for any of these actions to compute taxes automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:344 +msgid "" +":doc:`Fiscal positions (tax and account mapping) " +"<../accounting/taxes/fiscal_positions>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:92 +msgid "Electronic documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:354 +msgid "" +"To process an electronic invoice for goods (NF-e), the invoice needs to be " +"confirmed and taxes need to be computed by Avalara. Once that step is done, " +"click on the :guilabel:`Send \\& Print` button in the upper left corner, and" +" a pop-up will appear. Then click on :guilabel:`Process e-invoice` and any " +"of the other options - :guilabel:`Download` or :guilabel:`Email`. Finally, " +"click on :guilabel:`Send \\& Print` to process the invoice against the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:360 +msgid "" +"Before sending the electronic invoice for goods (NF-e) some fields need to " +"be filled out on the invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:363 +msgid ":guilabel:`Customer` with all the customer information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:364 +msgid "" +":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:365 +msgid "" +":guilabel:`Fiscal Position` set as the :guilabel:`Automatic Tax Mapping " +"(Avalara Brazil)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:368 +msgid "" +":guilabel:`Document Type` set as :guilabel:`(55) Electronic Invoice (NF-e)`." +" This is the only" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:367 +msgid "" +"electronic document supported at the moment. Non-electronic invoices can be " +"registered, and other document types can be activated if needed" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:370 +msgid "" +"There are some other optional fields that depend on the nature of the " +"transaction. These fields are not required, so no errors will appear from " +"the government if these optional fields are not populated for most cases:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:374 +msgid "" +":guilabel:`Freight Model` determines how the goods are planned to be " +"transported - domestic" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 +msgid "" +":guilabel:`Transporter Brazil` determines who is doing the transportation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Invoice information needed to process an electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Process electronic invoice pop-up in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:384 +msgid "" +"All of the fields available on the invoice used to issue an electronic " +"invoice are also available on the sales order, if needed. When creating the " +"first invoice, the field :guilabel:`Document Number` is displayed, allocated" +" as the first number to be used sequentially for subsequent invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:390 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 +msgid "Credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:392 +msgid "" +"If a sales return needs to be registered, then a credit note can be created " +"in Odoo to be sent to the government for validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:396 +msgid ":ref:`Issue a credit note `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:399 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:585 +msgid "Debit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:401 +msgid "" +"If additional information needs to be included, or values need to be " +"corrected that were not accurately provided in the original invoice, a debit" +" note can be issued." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:405 +msgid "" +"Only the products included in the original invoice can be part of the debit " +"note. While changes can be made to the product's unit price or quantity, " +"products **cannot** be added to the debit note. The purpose of this document" +" is only to declare the amount that you want to add to the original invoice " +"for the same or fewer products." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:411 +msgid ":ref:`Issue a debit note `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:414 +msgid "Invoice cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:416 +msgid "" +"It is possible to cancel an electronic invoice that was validated by the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:419 +msgid "" +"Check whether the electronic invoice is still within the cancellation " +"deadline, which may vary according to the legislation of each state." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:422 +msgid "" +"This can be done in Odoo by clicking :guilabel:`Request Cancel` and adding a" +" cancellation :guilabel:`Reason` on the pop-up that appears. If you want to " +"send this cancellation reason to the customer via email, activate the " +":guilabel:`E-mail` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Invoice cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:430 +msgid "Correction letter" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 +msgid "" +"A correction letter can be created and linked to an electronic invoice that " +"was validated by the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:435 +msgid "" +"This can be done in Odoo by clicking :guilabel:`Correction Letter` and " +"adding a correction :guilabel:`Reason` on the pop-up that appears. To send " +"this correction reason to a customer via email, activate the " +":guilabel:`E-mail` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Correction letter reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:443 +msgid "Invalidate invoice number range" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:445 +msgid "" +"A range of sequences that are assigned to sales journals can be invalidated " +"with the government if they are not currently used, **and** will not be used" +" in the future. To do so, navigate to the journal, and click the " +":menuselection:`⚙️ (gear) icon --> Invalidate Number Range (BR)`. On the " +":guilabel:`Invalidate Number Range (BR)` wizard, add the :guilabel:`Initial " +"Number` and :guilabel:`End Number` of the range that should be canceled, and" +" enter an invalidation :guilabel:`Reason`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Number range invalidation selection in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Number range invalidation wizard in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:459 +msgid "" +"The log of the canceled numbers along with the XML file are recorded in the " +"chatter of the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:465 +msgid "" +"On the vendor bills side, when receiving an invoice from a supplier, you can" +" encode the bill in Odoo by adding all the commercial information together " +"with the same Brazilian specific information that is recorded on the " +":ref:`customer invoices `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:469 +msgid "These Brazilian specific fields are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:471 +msgid "" +":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:472 +msgid ":guilabel:`Document Type` used by your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:473 +msgid ":guilabel:`Document Number` (the invoice number from your supplier)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:474 +msgid "" +":guilabel:`Freight Model` (how goods are planned to be transported - " +"domestic)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:475 +msgid ":guilabel:`Transporter Brazil` (who is doing the transportation)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:3 +msgid "Chile" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:6 +msgid "" +"Watch the two webinar recordings below for a general presentation of the " +"localization, and search the playlist for tutorials to discover practical " +"workflows while using Odoo in Chile." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:9 +msgid "`Webinar: intro and demo `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:10 +msgid "`Webinar: delivery guide `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:11 +msgid "" +"`Playlist of tutorials " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:15 +msgid "" +"`Chilean localization app tour " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:16 +msgid "" +"`Chilean localization smart tutorial `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:22 +msgid "Modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:24 +msgid "" +":ref:`Install ` the following modules to utilize all the " +"features of the Chilean localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:33 +msgid ":guilabel:`Chile - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:34 +msgid "`l10n_cl`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:35 +msgid "" +"Adds the minimal accounting features required for a company to operate in " +"Chile under the :abbr:`SII (Servicio de Impuestos Internos)` regulations and" +" guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:37 +msgid ":guilabel:`Chile - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:38 +msgid "`l10n_cl_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:39 +msgid "" +"Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:40 +msgid ":guilabel:`Chile - E-invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:41 +msgid "`l10n_cl_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:42 +msgid "" +"Includes all technical and functional requirements to generate and receive " +"electronic invoices online based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:44 +msgid ":guilabel:`Chile - Electronic Receipt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:45 +msgid "`l10n_cl_boletas`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:46 +msgid "" +"Includes all technical and functional requirements to generate and receive " +"electronic invoices digitally based on the :abbr:`SII (Servicio de Impuestos" +" Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:48 +msgid ":guilabel:`Electronic Exports of Goods for Chile`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:49 +msgid "`l10n_cl_edi_exports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:50 +msgid "" +"Includes technical and functional requirements to generate electronic " +"invoices for exporting goods based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` and customs regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:52 +msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:53 +msgid "`l10n_cl_edi_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:54 +msgid "" +"Includes all technical and functional requirements to generate delivery " +"guides via web service based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:58 +msgid "" +"Odoo automatically installs the appropriate package for the company " +"according to the country selected at the creation of the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:60 +msgid "" +"The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* " +"application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:63 +msgid "" +"All features are only available if the company already completed the `SII " +"Sistema de Facturación de Mercado " +"`_" +" certification process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:70 +msgid "" +"Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure " +"the following company information is up-to-date and correctly filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:73 +msgid ":guilabel:`Company Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 +msgid ":guilabel:`Address`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +msgid ":guilabel:`State`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 +msgid "" +":guilabel:`Tax ID`: enter the identification number for the selected " +":ref:`Taxpayer Type `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 +msgid ":guilabel:`Activity Names`: select up to four activity codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:85 +msgid "" +":guilabel:`Company Activity Description`: enter a short description of the " +"company's activity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:90 +msgid "" +"Next, navigate to :menuselection:`Accounting --> Configuration --> Settings " +"--> Chilean Localization` and follow the instructions to configure the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:93 +msgid ":ref:`Fiscal information `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 +msgid ":ref:`Electronic invoice data `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:95 +msgid ":ref:`DTE incoming email server `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:96 +msgid ":ref:`Signature certificates `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:101 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 +msgid "Fiscal information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:103 +msgid "Configure the following :guilabel:`Tax payer information`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 +msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 +msgid "" +":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to " +"customers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:108 +msgid "" +":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees" +" receipt (Boleta)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 +msgid ":guilabel:`End consumer`: only issues receipts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:110 +msgid ":guilabel:`Foreigner`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 +msgid "" +":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de " +"Impuestos Internos)` regional office" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:118 +msgid "Electronic invoice data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:120 +msgid "Select your :guilabel:`SII Web Services` environment:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 +msgid "" +":guilabel:`SII - Test`: for test databases using test :abbr:`CAFs (Folio " +"Authorization Code)` obtained from the :abbr:`SII (Servicio de Impuestos " +"Internos)`. In this mode, the direct connection flows can be tested, with " +"the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +msgid ":guilabel:`SII - Production`: for production databases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:127 +msgid "" +":guilabel:`SII - Demo Mode`: files are created and accepted automatically in" +" demo mode but are **not** sent to the :abbr:`SII (Servicio de Impuestos " +"Internos)`. For this reason, rejection errors or *Accepted with Objections* " +"will not appear in this mode. Every internal validation can be tested in " +"demo mode. Avoid selecting this option in a production database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:132 +msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:134 +msgid ":guilabel:`SII Resolution N°`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:135 +msgid ":guilabel:`SII Resolution Date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Required information for electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:144 +msgid "DTE incoming email server" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:146 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`Email Box " +"Electronic Invoicing` can be defined to receive your customers' claim and " +"acceptance emails. Enabling this option from :menuselection:`Accounting --> " +"Configuration --> Settings --> Chilean Localization` is necessary if you " +"want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` incoming email server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:153 +msgid "" +"In order to receive your SII documents, it's necessary to set up your own " +"email server. More information on how to do this can be found in this " +"documentation: :doc:`../../general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 +msgid "" +"Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click " +":guilabel:`New` to add a server and fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:160 +msgid ":guilabel:`Name`: give the server a name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +msgid ":guilabel:`Server Type`: select the server type used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:163 +msgid ":guilabel:`IMAP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +msgid ":guilabel:`POP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 +msgid "" +":guilabel:`Local Server`: uses a local script to fetch emails and create new" +" records. The script can be found in the :guilabel:`Configuration` section " +"with this option selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 +msgid "" +":guilabel:`Gmail OAuth Authentication`: requires your Gmail API credentials " +"to be configured in the general settings. A direct link to the configuration" +" can be found in the :guilabel:`Login Information` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 +msgid "" +":guilabel:`DTE Server`: enable this option. By checking this option, this " +"email account will be used to receive the electronic invoices from the " +"suppliers, and communications from the :abbr:`SII (Servicio de Impuestos " +"Internos)` regarding the electronic invoices issued. In this case, this " +"email should match both emails declared on the :abbr:`SII (Servicio de " +"Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL " +"CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:178 +msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:180 +msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:181 +msgid ":guilabel:`Port`: enter the server port." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 +msgid "" +":guilabel:`SSL/TLS`: enable this option if connections are encrypted using " +"the SSL/TLS protocol." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:183 +msgid ":guilabel:`Username`: enter the server login username." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 +msgid ":guilabel:`Password`: enter the server login password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Incoming email server configuration for Chilean DTE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:191 +msgid "" +"Before going live, it is recommended to archive or remove all emails related" +" to vendor bills that are not required to be processed in Odoo from your " +"inbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:197 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:219 +msgid "Certificate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:199 +msgid "" +"A digital certificate in `.pfx` format is required to generate the " +"electronic invoice signature. To add one, click :guilabel:`Configure " +"Signature Certificates` under the :guilabel:`Signature Certificates` " +"section. Then, click :guilabel:`New` to configure the certificate:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 +msgid "" +":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select " +"the `.pfx` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:204 +msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:205 +msgid "" +":guilabel:`Subject Serial Number`: depending on the certificate format, the " +"field might not be automatically populated. In that case, enter the " +"certificate's legal representative :abbr:`RUT (Rol Único Tributario)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +msgid "" +":guilabel:`Certificate Owner`: select one if you need to restrict the " +"certificate for a specific user. Leave the field empty to share it with all " +"billing users." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Digital certificate configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:216 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:230 +msgid "Multicurrency" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:218 +msgid "" +"The official currency rate is provided by `Chilean mindicador.cl " +"`_. Navigate to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies: Automatic Currency Rates` to set " +"an :guilabel:`Interval` for when the rate is automatically updated, or to " +"select another :guilabel:`Service`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 +#: ../../content/applications/finance/fiscal_localizations/france.rst:306 +msgid "Partner information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:228 +msgid "" +"Configuring partner contacts is also required to send :abbr:`SII (Servicio " +"de Impuestos Internos)` electronic invoices. Open the " +":menuselection:`Contacts` app to do so and fill in the following fields on a" +" new or existing contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 +msgid ":guilabel:`Identification Number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:235 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +msgid ":guilabel:`Taxpayer Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 +msgid ":guilabel:`Activity Description`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 +msgid "In the :guilabel:`Electronic Invoicing` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 +msgid "" +":guilabel:`DTE Email`: enter the sender's email address for the partner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:241 +msgid "" +":guilabel:`Delivery Guide Price`: select which price the delivery guide " +"displays, if any." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:244 +msgid "" +"The :guilabel:`DTE Email` is the email used for sending electronic documents" +" and must be set in the contact that will be part of an electronic document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean electronic invoice data for partners." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 +msgid "" +"Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos " +"Internos)`-defined document types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:257 +msgid "" +"Document types are created automatically upon installation of the " +"localization module, and can be managed by navigating to " +":menuselection:`Accounting --> Configuration --> Document Types`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean fiscal document types list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:265 +msgid "" +"Several document types are inactive by default but can be activated by " +"toggling the :guilabel:`Active` option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 +msgid "The document type on each transaction is determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 +msgid "" +"The journal related to the invoice, identifying if the journal uses " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:274 +msgid "" +"The condition applied based on the type of issuer and recipient (e.g., the " +"buyer or vendor's fiscal regime)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:280 +msgid "" +"*Sales journals* in Odoo usually represent a business unit or location." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:283 +msgid "Ventas Santiago." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:284 +msgid "Ventas Valparaiso." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 +msgid "" +"For retail stores it is common to have one journal per :abbr:`POS (Point of " +"Sale)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:289 +msgid "Cashier 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 +msgid "Cashier 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 +msgid "" +"The *purchase* transactions can be managed with a single journal, but " +"sometimes companies use more than one journal in order to handle some " +"accounting transactions that are not related to vendor bills. This " +"configuration can easily be set by using the following model." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:297 +msgid "Tax payments to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:298 +msgid "Employees payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:301 +msgid "Create a sales journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:303 +msgid "" +"To create a sales journal, navigate to :menuselection:`Accounting --> " +"Configuration --> Journals`. Then, click the :guilabel:`New` button, and " +"fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:306 +msgid "" +":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for " +"customer invoice journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:307 +msgid "" +":guilabel:`Point of sale type`: if the sales journal will be used for " +"electronic documents, the option :guilabel:`Online` must be selected. " +"Otherwise, if the journal is used for invoices imported from a previous " +"system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` " +"portal *Facturación MiPyme*, you can use the option :guilabel:`Manual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:311 +msgid "" +":guilabel:`Use Documents`: check this field if the journal will use document" +" types. This field is only applicable to purchase and sales journals that " +"can be related to the different sets of document types available in Chile. " +"By default, all the sales journals created will use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 +msgid "" +"Next, from the :guilabel:`Jounal Entries` tab, define the :guilabel:`Default" +" Income Account` and :guilabel:`Dedicated Credit Note Squence` in the " +":guilabel:`Accounting Information` section. Configuring these fields is " +"required for one of the debit notes :ref:`use cases `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:322 +msgid "CAF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:324 +msgid "" +"A *folio authorization code* (CAF) is required for each document type that " +"will be issued electronically. The :abbr:`CAF (Folio Authorization Code)` is" +" a file the :abbr:`SII (Servicio de Impuestos Internos)` provides to the " +"issuer with the folios/sequences authorized for the electronic invoice " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:329 +msgid "" +"Your company can request multiple folios and obtain several :abbr:`CAFs " +"(Folio Authorization Codes)` linked to different folio ranges. These " +":abbr:`CAFs (Folio Authorization Code)` are shared within all journals, so " +"you only need one active :abbr:`CAF (Folio Authorization Code)` per document" +" type, and it will be applied to all journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:334 +msgid "" +"Please refer to the `SII documentation " +"`_ to check the details on how " +"to acquire the :abbr:`CAF (Folio Authorization Code)` files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:338 +msgid "" +"The :abbr:`CAFs (Folio Authorization Code)` required by the :abbr:`SII " +"(Servicio de Impuestos Internos)` are different from production to test " +"(certification mode). Make sure you have the correct :abbr:`CAF (Folio " +"Authorization Code)` set depending on your environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:343 +msgid "Upload CAF files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:345 +msgid "" +"Once the :abbr:`CAF (Folio Authorization Code)` files have been acquired " +"from the :abbr:`SII (Servicio de Impuestos Internos)` portal, they need to " +"be uploaded in the database by navigating to :menuselection:`Accounting --> " +"Configuration: Chilean SII --> CAFs`. Then, click the :guilabel:`New` begin " +"the configuration. On the :abbr:`CAF (Folio Authorization Code)` form, " +"upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the " +":guilabel:`Upload your file` button and then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:352 +msgid "" +"Once uploaded, the status changes to :guilabel:`In Use`. At this moment, " +"when a transaction is used for this document type, the invoice number takes " +"the first folio in the sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:356 +msgid "" +"The document types have to be active before uploading the :abbr:`CAF (Folio " +"Authorization Code)` files. In case some folios have been used in the " +"previous system, the next valid folio has to be set when the first " +"transaction is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:363 +msgid "" +"The chart of accounts is installed by default as part of the data set " +"included in the localization module. The accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:367 +msgid "Default Account Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:75 +msgid "Default Account Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:369 +msgid "Transfer Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 +msgid "Conversion Rate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:378 +msgid "" +"As part of the localization module, taxes are created automatically with " +"their related financial account and configuration. These taxes can be " +"managed from :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:382 +msgid "Chile has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:384 +msgid "**VAT**: the regular VAT can have several rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:385 +msgid "**ILA**: the tax for alcoholic drinks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:388 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:106 +msgid ":doc:`../accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:394 +msgid "Electronic invoice workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:396 +msgid "" +"In the Chilean localization, the electronic invoice workflow includes " +"customer invoice issuance and vendor bill reception. The following diagram " +"explains how information is shared to the :abbr:`SII (Servicio de Impuestos " +"Internos)`, customers, and vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Diagram with Electronic invoice transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:405 +msgid "Customer invoice emission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:407 +msgid "" +"After the partners and journals are created and configured, the invoices are" +" created in the standard way. For Chile, one of the differences is the " +"document type that is automatically selected based on the taxpayer. The " +"document type can be changed manually if needed on the invoice by navigating" +" to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Customer invoice document type selection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:417 +msgid "" +":guilabel:`Documents type 33` electronic invoice must have at least one item" +" with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` " +"rejects the document validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:423 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 +msgid "Validation and DTE status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:425 +msgid "" +"Once all invoice information is filled, either manually or automatically " +"when generated from a sales order, validate the invoice. After the invoice " +"is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:428 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file is created " +"automatically and recorded in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio " +"de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "DTE XML File displayed in chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:437 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` status is updated " +"automatically by Odoo with a scheduled action that runs every day at night, " +"if the response from the :abbr:`SII (Servicio de Impuestos Internos)` is " +"needed immediately, you can do it manually as well by following the " +":abbr:`DTE (Documentos Tributarios Electrónicos)` status workflow:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Transition of DTE status flow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:446 +msgid "" +"The first step is to send the :abbr:`DTE (Documentos Tributarios " +"Electrónicos)` to the :abbr:`SII (Servicio de Impuestos Internos)`. This can" +" be sent manually by clicking the :guilabel:`Enviar Ahora` button. This " +"generates a :guilabel:`SII Tack number` for the invoice, which is used to " +"check the details sent by the :abbr:`SII (Servicio de Impuestos Internos)` " +"via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for" +" Status`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:451 +msgid "" +"Once the :abbr:`SII (Servicio de Impuestos Internos)` response is received, " +"Odoo updates the :guilabel:`DTE status`. To do it manually, click on the " +"button :guilabel:`Verify on SII`. The result can either be " +":guilabel:`Accepted`, :guilabel:`Accepted With Objection` or " +":guilabel:`Rejected`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Identification transaction for invoice and Status update." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:461 +msgid "" +"There are intermediate statuses in the :abbr:`SII (Serviciqo de Impuestos " +"Internos)` before acceptance or rejection. It's recommended to **NOT** " +"continuously click :guilabel:`Verify in SII` for smooth processing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Electronic invoice data statuses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:469 +msgid "" +"The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can" +" take on one of these values:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:472 +msgid "" +":guilabel:`Accepted`: indicates the invoice information is correct, our " +"document is now fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 +msgid "" +":guilabel:`Accepted with objections`: indicates the invoice information is " +"correct, but a minor issue was identified, nevertheless the document is now " +"fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:477 +msgid "" +":guilabel:`Rejected`: indicates the invoice information is incorrect and " +"must be corrected. Details are sent to emails you registered in the " +":abbr:`SII (Servicio de Impuestos Internos)`. If it is properly configured " +"in Odoo, the details are also retrieved in the chatter once the email server" +" is processed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:482 +msgid "If the invoice is rejected please follow these steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 +msgid "Change the document to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:485 +msgid "" +"Make the required corrections based on the message received from the " +":abbr:`SII (Servicio de Impuestos Internos)` in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:487 +msgid "Post the invoice again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Message when an invoice is rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:494 +msgid "Crossed references" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 +msgid "" +"When the invoice is created, as a result of another fiscal document, the " +"information related to the originator document must be registered in the " +":guilabel:`Cross-Reference` tab. This tab is commonly used for credit or " +"debit notes, however, in some cases it can be used for customer invoices, as" +" well. In the case of the credit and debit notes, they are set automatically" +" by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Crossed referenced document(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:508 +#: ../../content/applications/finance/fiscal_localizations/india.rst:133 +#: ../../content/applications/finance/fiscal_localizations/india.rst:271 +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Invoice PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:510 +msgid "" +"Once the invoice is accepted and validated by the :abbr:`SII (Servicio de " +"Impuestos Internos)` and the PDF is printed, it includes the fiscal elements" +" that indicate that the document is fiscally valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "SII Validation fiscal elements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:519 +msgid "" +"If you are hosted in Odoo SH or On-Premise, you should manually install the " +"`pdf417gen `_ library. Use the " +"following command to install it: :command:`pip install pdf417gen`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 +msgid "Commercial validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +msgid "Once the invoice has been sent to the customer:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 +msgid "The customer must send a reception confirmation email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +msgid "" +"Subsequently, if commercial terms and invoice data are correct, an " +"acceptance confirmation is sent; otherwise, a claim is sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Message with the commercial acceptance from the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 +msgid "Processed for claimed invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 +msgid "" +"Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos " +"Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for" +" your customer, the correct way to proceed is with a credit note to either " +"cancel the invoice or correct it. Please refer to the :ref:`chile/credit-" +"notes` section for more details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Commercial status updated to claimed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:551 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 +msgid "Common errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 +msgid "" +"There are multiple reasons behind a rejection from the :abbr:`SII (Servicio " +"de Impuestos Internos)`, but these are some of the common errors you might " +"have and how to solve them:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `RECHAZO- DTE Sin Comuna Origen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** make sure the company address is properly filled including the " +"state and city." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `en Monto - IVA debe declararse`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** the invoice lines should include one VAT tax, make sure you add " +"one on each invoice line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Rut No Autorizado a Firmar`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** the :abbr:`RUT (Rol Único Tributario)` entered is not allowed to " +"invoice electronically, make sure the company :abbr:`RUT (Rol Único " +"Tributario)` is correct and is valid in the :abbr:`SII (Servicio de " +"Impuestos Internos)` to invoice electronically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Error:** `Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : " +"(Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** try to add a new CAF related to this document as the one you're " +"using is expired." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Error:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element " +"is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** Make sure the field :guilabel:`Document Type` and :guilabel:`VAT` " +"are set in the customer and in the main company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Usuario sin permiso de envio.`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** this error indicates that most likely, your company has not passed" +" the `Certification process " +"`_" +" in the :abbr:`SII (Servicio de Impuestos Internos)` - Sistema de " +"Facturación de Mercado. If this is the case, please contact your Account " +"Manager or Customer Support as this certification is not part of the Odoo " +"services, but we can give you some alternatives. If you already passed the " +"certification process, this error appears when a user different from the " +"owner of the certificate is trying to send :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` files to the :abbr:`SII (Servicio de Impuestos " +"Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `CARATULA`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** there are just five reasons why this error could show up and all " +"of them are related to the *Caratula* section of the XML:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 +msgid "" +"The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or " +"missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 +msgid "" +"The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect" +" or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 +msgid "" +"The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol Único " +"Tributario)` number (this should be correct by default) is incorrect or " +"missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +msgid "The resolution date is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:590 +msgid "The resolution number is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 +msgid "" +"When a cancellation or correction is needed over a validated invoice, a " +"credit note must be generated. It is important to consider that a :abbr:`CAF" +" (Folio Authorization Code)` file is required for the credit note, which is " +"identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII " +"(Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section " +"` for more information on the process to load the " +":abbr:`CAF (Folio Authorization Code)` on each document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Creation of CAF for Credit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:609 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 +msgid "Cancel referenced document" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 +msgid "" +"In case you need to cancel or invalidate an invoice, navigate to " +":menuselection:`Accounting --> Customers --> Invoices` and select the " +"desired invoice. Then, use the button :guilabel:`Add Credit Note` and select" +" :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos" +" Internos)` reference code is automatically set to :guilabel:`Anula " +"Documento de referencia`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note canceling the referenced document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 +msgid "Correct referenced document" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 +msgid "" +"If a correction in the invoice information is required, for example the " +"street name on the original invoice is wrong, then use the button " +":guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select " +"the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII" +" Reference Code` field is automatically set to :guilabel:`Corrects " +"Referenced Document Text`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note correcting referenced document text." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:635 +msgid "" +"Odoo creates a credit note with the corrected text in an invoice and " +":guilabel:`Price` `0.00`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note with the corrected value on the invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:642 +msgid "" +"Make sure to define the :guilabel:`Default Credit Account` in the sales " +"journal specifically for this use case." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 +msgid "Corrects referenced document amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 +msgid "" +"When a correction on the amounts is required, use the button :guilabel:`Add " +"Credit note` and select :guilabel:`Partial Refund`. In this case the " +":guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el" +" monto del Documento de Referencia`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Credit note for partial refund to correct amounts, using the SII reference " +"code 3." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +msgid "Debit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 +msgid "" +"In Chilean localization, debit notes, in addition to credit notes, can be " +"created using the :guilabel:`Add Debit Note` button, with two main use " +"cases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 +msgid "Add debt on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 +msgid "" +"The primary use case for debit notes is to increase the value of an existing" +" invoice. To do so, select option :guilabel:`3. Corrige el monto del " +"Documento de Referencia` for the :guilabel:`Reference Code SII` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Debit note correcting referenced document amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:678 +msgid "" +"In this case Odoo automatically includes the :guilabel:`Source Invoice` in " +"the :guilabel:`Cross Reference` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Automatic reference to invoice in a debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 +msgid "" +"You can only add debit notes to an invoice already accepted by the SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 +msgid "Cancel credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 +msgid "" +"In Chile, debits notes are used to cancel a valid credit note. To do this, " +"click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: " +"Anula Documentos de referencia` option for the :guilabel:`Reference Code " +"SII` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Debit note to cancel the referenced document (credit note)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 +msgid "" +"As part of the Chilean localization, you can configure your incoming email " +"server to match the one you have registered in the :abbr:`SII (Servicio de " +"Impuestos Internos)` in order to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 +msgid "" +"Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios " +"Electrónicos)` and create the vendor bill based on this information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 +msgid "Automatically send the reception acknowledgement to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 +msgid "Accept or claim the document and send this status to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +msgid "Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 +msgid "" +"As soon as the vendor email with the attached :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` is received:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 +msgid "The vendor bill maps all the information included in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 +msgid "An email is sent to the vendor with the reception acknowledgement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +msgid "" +"The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 +msgid "Acceptation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 +msgid "" +"If all the commercial information is correct on your vendor bill, then you " +"can accept the document using the :guilabel:`Aceptar Documento` button. Once" +" this is done, the :guilabel:`DTE Acceptation Status` changes to " +":guilabel:`Accepted` and an email of acceptance is sent to the vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Button for accepting vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 +msgid "Claim" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:734 +msgid "" +"In case there is a commercial issue or the information is not correct on " +"your vendor bill, you can claim the document before validating it, using the" +" :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation" +" Status` changes to :guilabel:`Claim` and a rejection email is sent to the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Claim button in vendor bills to inform the vendor all the document is commercially\n" +"rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:744 +msgid "" +"If you claim a vendor bill, the status changes from :guilabel:`Draft` to " +":guilabel:`Cancel` automatically. Considering this as best practice, all the" +" claimed documents should be canceled as they won't be valid for your " +"accounting records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 +msgid "Delivery guide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +msgid "" +"To install the :guilabel:`Delivery Guide` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery " +"Guide`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 +msgid "" +":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with " +":guilabel:`Chile - Facturación Electrónica`. Odoo will install the " +"dependency automatically when the :guilabel:`Delivery Guide` module is " +"installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:760 +msgid "" +"The *Delivery Guide* module includes the ability to send the :abbr:`DTE " +"(Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos " +"Internos)` and the stamp in PDF reports for deliveries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), delivery guides need their own :abbr:`CAFs " +"(Folio Authorization Code)`. Please refer to the :ref:`CAF documentation " +"` to check the details on how to acquire the " +":abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 +msgid "" +"Verify the following important information in the :guilabel:`Price for the " +"Delivery Guide` configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 +msgid "" +":guilabel:`From Sales Order`: delivery guide takes the product price from " +"the sales order and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +msgid "" +":guilabel:`From Product Template`: Odoo takes the price configured in the " +"product template and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 +msgid ":guilabel:`No show price`: no price is shown in the delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +msgid "" +"Electronic delivery guides are used to move stock from one place to another " +"and they can represent sales, sampling, consignment, internal transfers, and" +" basically any product move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 +msgid "Delivery guide from a sales process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 +msgid "" +"A delivery guide should **not** be longer than one page or contain more than" +" 60 product lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +msgid "" +"When a sales order is created and confirmed, a delivery order is generated. " +"After validating the delivery order, the option to create a delivery guide " +"is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Create Delivery Guide button on a sales process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 +msgid "" +"When clicking on :guilabel:`Create Delivery Guide` for the first time, a " +"warning message pops up, stating the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:799 +msgid "" +"`No se encontró una secuencia para la guía de despacho. Por favor, " +"establezca el primer número dentro del campo número para la guía de " +"despacho`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "First Delivery Guide number warning message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 +msgid "" +"This warning message means the user needs to indicate the next sequence " +"number Odoo has to take to generate the delivery guide (e.g. next available " +":abbr:`CAF (Folio Authorization Code)` number), and only happens the first " +"time a delivery guide is created in Odoo. After the first document has been " +"correctly generated, Odoo takes the next available number in the :abbr:`CAF " +"(Folio Authorization Code)` file to generate the following delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 +msgid "After the delivery guide is created:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:814 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " +"Document) is automatically created and added to the :guilabel:`chatter`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 +msgid "" +"The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chatter notes of Delivery Guide creation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 +msgid "" +"The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled" +" action that runs every night. To get a response from the :abbr:`SII " +"(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" +" to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +msgid "" +"Once the delivery guide is sent, it may then be printed by clicking on the " +":guilabel:`Print Delivery Guide` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Printing Delivery Guide PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:833 +msgid "" +"Delivery guide will have fiscal elements that indicate that the document is " +"fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* " +"remember to manually add the :guilabel:`pdf417gen` library mentioned in the " +":ref:`Invoice PDF report section `)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 +msgid "Electronic receipt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 +msgid "" +"To install the :guilabel:`Electronic Receipt` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:846 +msgid "" +":guilabel:`Chile - Electronic Receipt` has a dependency with " +":guilabel:`Chile - Facturación Electrónica`. Odoo will install the " +"dependency automatically when the :guilabel:`E-invoicing Delivery Guide` " +"module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:850 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), electronic receipts need their own " +":abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF " +"documentation ` to check the details on how to " +"acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:856 +msgid "" +"Electronic receipts are useful when clients do not need an electronic " +"invoice. By default, there is a partner in the database called " +":guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol Único " +"Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. " +"This partner can be used for electronic receipts or a new record may be " +"created for the same purpose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Electronic Receipt module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 +msgid "" +"Although electronic receipts should be used for final consumers with a " +"generic :abbr:`RUT (Rol Único Tributario)`, it can also be used for specific" +" partners. After the partners and journals are created and configured, the " +"electronic receipts are created in the standard way as electronic invoice, " +"but the type of document :guilabel:`(39) Electronic Receipt` should be " +"selected in the invoice form:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Document type 39 for Electronic Receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +msgid "" +"When all of the electronic receipt information is filled, manually (or " +"automatically) proceed to validate the receipt from the sales order. By " +"default, :guilabel:`Electronic Invoice` is selected as the " +":guilabel:`Document Type`, however in order to validate the receipt " +"correctly, make sure to edit the :guilabel:`Document Type` and change to " +":guilabel:`Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 +msgid "After the receipt is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " +"Document) is created automatically and added to the :guilabel:`chatter`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Electronic Receipts STE creation status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 +msgid "" +"The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled" +" action that runs every day at night. To get a response from the :abbr:`SII " +"(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" +" to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +msgid "" +"Please refer to the :ref:`DTE Workflow ` for electronic invoices as the workflow for electronic receipt " +"follows the same process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 +msgid "Electronic export of goods" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 +msgid "" +"To install the :guilabel:`Electronic Exports of Goods` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for" +" Chile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:907 +msgid "" +":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency " +"with :guilabel:`Chile - Facturación Electrónica`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:910 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), electronic exports of goods need their own " +":abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF " +"documentation ` to check the details on how to " +"acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:916 +msgid "" +"Electronic invoices for the export of goods are tax documents that are used " +"not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also " +"used with customs and contain the information required by it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:921 +msgid "Contact configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Taxpayer Type needed for the Electronic Exports of Goods module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 +msgid "Chilean customs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 +msgid "" +"When creating an electronic exports of goods invoice, these new fields in " +"the :guilabel:`Other Info` tab are required to comply with Chilean " +"regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean customs fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 +msgid "PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 +msgid "" +"Once the invoice is accepted and validated by the :abbr:`SII (Servicio de " +"Impuestos Internos)` and the PDF is printed, it includes the fiscal elements" +" that indicate that the document is fiscally valid and a new section needed " +"for customs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "PDF report section for the Electronic Exports of Goods PDF Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 +msgid "eCommerce electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +msgid "" +"To install the :guilabel:`Chilean eCommerce` module, go to " +":menuselection:`Apps, search for the module by its technical name " +"`l10n_cl_edi_website_sale`, and click the :guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "l10n_cl eCommerce module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:958 +msgid "This module enables the features and configurations to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:960 +msgid "Generate electronic documents from the *eCommerce* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:961 +msgid "Support for required fiscal fields in the *eCommerce* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 +msgid "" +"Effectively let the final client decide the electronic document to be " +"generated for their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 +msgid "" +"Once all of the configurations are made for the Chilean :ref:`electronic " +"invoice ` flow, the following configurations are " +"required for the eCommerce flow to be integrated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 +msgid "" +"To configure your website to generate electronic documents during the sale " +"process, go to :menuselection:`Website --> Configuration --> Settings --> " +"Invoicing` and activate the :guilabel:`Automatic Invoice` feature. " +"Activating this feature allows electronic documents to be automatically " +"generated when an online payment is confirmed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Policy and Automatic Invoice configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:978 +msgid "" +"Since an online payment needs to be confirmed for the *automatic invoice* " +"feature to generate the document, a payment provider must be configured for " +"the related website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:982 +msgid "" +"Review the :doc:`../payment_providers` documentation for information on " +"which payment providers are supported in Odoo, and how to configure them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:985 +msgid "" +"It is also recommended to configure your products so they are able to be " +"invoiced when an online payment is confirmed. To do so, go to " +":menuselection:`Website --> eCommerce --> Products` and select the product " +"template of the desired product. Then, set the :guilabel:`Invoicing Policy` " +"to :guilabel:`Ordered quantities`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Policy configuration in Products." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:995 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1081 +msgid "Invoicing flows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:997 +msgid "" +"Clients from Chile will be able to select if they need an **invoice** or a " +"**ballot** for their purchase with an extra step added during the checkout " +"process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Option for EDI Documents for clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1004 +msgid "" +"If the customer selects the :guilabel:`Electronic Invoice` option, fiscal " +"fields are required to be filled out, including the :guilabel:`Activity " +"Description`, the :guilabel:`Identification Number` and their :guilabel:`DTE" +" Email`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Fiscal fields required for an Invoice to be requested." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1012 +msgid "" +"If the client selects the :guilabel:`Electronic Receipts` option, they will " +"be directed to the next step, and the electronic document will be generated " +"for the *Consumidor Final Anónimo* contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1015 +msgid "" +"Clients from countries other than Chile, will have their electronic receipts" +" automatically generated for them by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 +msgid "" +"If a purchase through eCommerce requires an export, the customer will need " +"to contact your company to generate an electronic export invoice (*document " +"type 110*), which can be done from the *Accounting* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1024 +msgid "Point of Sale electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1026 +msgid "" +"To install the :guilabel:`Chilean Module for Point of Sale`, go to the " +":menuselection:`Apps` application on the main Odoo dashboard, search for the" +" module by its technical name `l10n_cl_edi_pos`, and click the " +":guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "l10n_cl POS EDI module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 +msgid "This module enables the following features and configurations to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1036 +msgid "Generate electronic documents from the *Point of Sale* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1037 +msgid "" +"Support the required fiscal fields for contacts created in the *Point of " +"Sale* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1038 +msgid "" +"Effectively lets the final client decide the type of electronic document to " +"be generated for their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1040 +msgid "Print QR or 5-digit codes in tickets to access to electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 +msgid "" +"To configure contacts with the required fiscal information, review the " +":ref:`partner information ` section, or directly " +"modify a contact. Navigate to :menuselection:`Point of Sale --> Session --> " +"Customers --> Details`, and edit any of the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1049 +msgid ":guilabel:`Identification Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1050 +msgid ":guilabel:`Tax Payer Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1051 +msgid ":guilabel:`Type Giro`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 +msgid ":guilabel:`DTE Email`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 +msgid ":guilabel:`RUT`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Contact with fiscal information created from POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1059 +msgid "" +"To configure the products, navigate to :menuselection:`Point of Sale --> " +"Products --> Products` and select a product record. In the :guilabel:`Sales`" +" tab of the product form, it is necessary to mark the product as " +":guilabel:`Available for POS`, this makes the product available for sale in " +"the *Point of Sale* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Product with fiscal information created from POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 +msgid "" +"Optionally, the following features are available for configuration in the " +":menuselection:`Point of Sale --> Configuration --> Settings --> Bills & " +"Receipts section`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1071 +msgid "" +":guilabel:`Use QR code on ticket`: this feature enables a QR code to be " +"printed on the user's receipt so they can easily request an invoice after " +"their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 +msgid "" +":guilabel:`Generate a code on ticket`: this feature enables a 5-digit code " +"to be generated on the receipt, allowing the user to request an invoice " +"through the customer portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Configuration to generate QR or 5 digit codes on tickets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 +msgid "" +"The following sections cover the invoicing flows for the *Point of Sale* " +"application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 +msgid "Electronic receipts: anonymous end user" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1088 +msgid "" +"When making a purchase as an anonymous user that does not request an " +"electronic invoice, Odoo automatically selects :guilabel:`Consumidor Final " +"Anónimo` as the contact for the order and generates the electronic receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Automatic contact selection of an anonymous end consumer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 +msgid "" +"If the client requests a credit note due to a return of their purchase, the " +"credit note should be made using the *Accounting* app. See the :doc:`credit " +"notes and refunds <../accounting/customer_invoices/credit_notes>` " +"documentation for detailed instructions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 +msgid "Electronic receipts: specific customer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1104 +msgid "" +"When specific user makes a purchase that does not request an electronic " +"invoice, Odoo automatically selects the contact for the order as the " +":guilabel:`Consumidor Final Anónimo`, and allows you to select or create the" +" required customer contact with their fiscal information for the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of contact for the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1113 +msgid "" +"If the client requests a credit note because of a return of this type of " +"purchase, the credit note and return process can be managed directly from " +"the :abbr:`POS (Point of Sale)` session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 +msgid "Electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1119 +msgid "" +"When clients request an electronic invoice, it is possible to select or " +"create the required contact with their fiscal information. When the payment " +"is being made, select the option :guilabel:`Invoice` to generate the " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of invoice option at payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1128 +msgid "" +"For both the electronic receipts and invoices, if the product is not " +"affected by taxes, Odoo detects this and generates the correct type of " +"document for tax-exempt sales." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 +msgid "Returns" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1134 +msgid "" +"For electronic receipts (not generated for the *Consumidor Final Anónimo*) " +"and electronic invoices, it is possible to manage the process to return " +"products sold in a :abbr:`POS (Point of Sale)` order by selecting the " +":guilabel:`Refund` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Refund option in the POS application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1142 +msgid "" +"Orders can be searched by the order status or by contact, and be selected " +"for the refund to be based on the client's original order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of order for the refund process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1149 +msgid "" +"When the return payment is validated, Odoo generates the necessary credit " +"note, referencing the original receipt or invoice, partially or fully " +"canceling the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 +msgid "" +"`Smart tutorial - Electronic invoicing for point of sale " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1160 +msgid "Balance tributario de 8 columnas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 +msgid "" +"This report presents the accounts in detail (with their respective " +"balances), classifying them according to their origin and determining the " +"level of profit or loss that the business had within the evaluated period of" +" time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 +msgid "" +"You can find this report in :menuselection:`Accounting --> Reporting --> " +"Balance Sheet` and selecting in the :guilabel:`Report` field the option " +":guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Location of the Reporte Balance Tributario de 8 Columnas." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean Fiscal Balance (8 Columns)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1179 +msgid "Propuesta F29" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 +msgid "" +"The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos " +"Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales " +"Books*. This report is integrated by Purchase Register (CR) and the Sales " +"Register (RV). Its purpose is to support the transactions related to VAT, " +"improving its control and declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1186 +msgid "" +"This record is supplied by the electronic tax documents (DTE's) that have " +"been received by the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1189 +msgid "" +"You can find this report in :menuselection:`Accounting --> Reporting --> Tax" +" Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta " +"F29 (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Location of the Propuesta F29 (CL) Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1196 +msgid "" +"It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` " +"and the :guilabel:`Proportional Factor for the fiscal year` from the " +":menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1204 +msgid "" +"Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Manual PPM for the Propuesta F29 Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:3 +msgid "Colombia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:7 +msgid "" +"Odoo's Colombian localization package provides accounting, fiscal, and legal" +" features for databases in Colombia – such as chart of accounts, taxes, and " +"electronic invoicing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 +msgid "" +"In addition, a series of videos on the subject is also available. These " +"videos cover how to start from scratch, set up configurations, complete " +"common workflows, and provide in-depth looks at some specific use cases as " +"well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:15 +msgid "" +"`Smart Tutorial - Colombian Localization `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 +msgid ":guilabel:`Colombia - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 +msgid "`l10n_co`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:38 +msgid "" +"Default :ref:`fiscal localization package `. " +"This module adds the base accounting features for the Colombian " +"localization: chart of accounts, taxes, withholdings, and identification " +"document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 +msgid ":guilabel:`Colombian - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 +msgid "`l10n_co_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 +msgid "" +"Includes accounting reports for sending certifications to suppliers for " +"withholdings applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 +msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 +msgid "`l10n_co_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 +msgid "" +"This module includes the features required for integration with Carvajal, " +"and generates the electronic invoices and support documents related to the " +"vendor bills, based on |DIAN| regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:49 +msgid ":guilabel:`Colombian - Point of Sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 +msgid "`l10n_co_pos`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:51 +msgid "Includes Point of Sale receipts for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:54 +msgid "" +"When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`," +" Odoo automatically installs certain modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:58 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:60 +msgid "" +"To configure your company information, go to the :menuselection:`Contacts` " +"app, and search for your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:63 +msgid "" +"Alternatively, activate :ref:`developer mode ` and navigate " +"to :menuselection:`General Setting --> Company --> Update Info --> Contact`." +" Then, edit the contact form and configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 +msgid ":guilabel:`Company Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:68 +msgid "" +":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and " +":guilabel:`ZIP` code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 +msgid "" +":guilabel:`Identification Number`: Select the :guilabel:`Identification " +"Type` (`NIT`, `Cédula de Ciudadanía`, `Registro Civil`, etc.). When the " +":guilabel:`Identification Type` is `NIT`, the :guilabel:`Identification " +"Number` **must** have the *verification digit* at the end of the ID prefixed" +" by a hyphen (`-`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:74 +msgid "" +"Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales &" +" Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:76 +msgid "" +":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal " +"responsibility for the company (`O-13` Gran Contribuyente, `O-15` " +"Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de " +"tributación simple, `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 +msgid "" +":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this " +"option should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:81 +msgid "" +":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, " +"`INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:83 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:177 +msgid "" +":guilabel:`Commercial Name`: If the company uses a specific commercial name," +" and it needs to be displayed in the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:87 +msgid "Carjaval credentials configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:89 +msgid "" +"Once the modules are installed, the user credentials **must** be configured," +" in order to connect with Carvajal Web Service. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Settings` and scroll to the" +" :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the " +"required configuration information provided by Carvajal:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 +msgid "" +":guilabel:`Username` and :guilabel:`Password`: Username and password " +"(provided by Carvajal) to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:96 +msgid "" +":guilabel:`Company Registry`: Company's NIT number *without* the " +"verification code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:97 +msgid ":guilabel:`Account ID`: Company's NIT number followed by `_01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:98 +msgid "" +":guilabel:`Colombia Template Code`: Select one of the two available " +"templates (`CGEN03` or `CGNE04`) to be used in the PDF format of the " +"electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "" +"Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal " +"testing environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:103 +msgid "" +"Once Odoo and Carvajal are fully configured and ready for production, " +"deactivate the :guilabel:`Test mode` checkbox to use the production " +"database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Configure credentials for Carvajal web service in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:111 +msgid "" +":guilabel:`Test mode` must **only** be used on duplicated databases, **not**" +" the production environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:115 +msgid "Report data configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:117 +msgid "" +"Report data can be defined for the fiscal section and bank information of " +"the PDF as part of the configurable information sent in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:120 +msgid "" +"Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and " +"scroll to the :guilabel:`Colombian Electronic Invoicing` section, in order " +"to find the :guilabel:`Report Configuration` fields. Here the header " +"information for each report type can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +msgid ":guilabel:`Gran Contribuyente`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +msgid ":guilabel:`Tipo de Régimen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:126 +msgid ":guilabel:`Retenedores de IVA`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:127 +msgid ":guilabel:`Autorretenedores`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:128 +msgid ":guilabel:`Resolución Aplicable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:129 +msgid ":guilabel:`Actividad Económica`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:130 +msgid ":guilabel:`Bank Information`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:135 +msgid "Master data configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:140 +msgid "" +"Partner contacts can be created in the *Contacts* app. To do so, navigate to" +" :menuselection:`Contacts`, and click the :guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:143 +msgid "" +"Then, name the contact, and using the radio buttons, select the contact " +"type, either :guilabel:`Individual` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:146 +msgid "" +"Complete the full :guilabel:`Address`, including the :guilabel:`City`, " +":guilabel:`State`, and :guilabel:`ZIP` code. Then, complete the " +"identification and fiscal information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 +msgid "Identification information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 +msgid "" +"Identification types, defined by the |DIAN|, are available on the partner " +"form, as part of the Colombian localization. Colombian partners **must** " +"have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document " +"Type` set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:157 +msgid "" +"When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification " +"Number` needs to be configured in Odoo, including the *verification digit at" +" the end of the ID, prefixed by a hyphen (`-`)*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:164 +msgid "" +"The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro " +"único tributario)` document) are included as part of the electronic " +"invoicing module, as it is required by the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:167 +msgid "" +"The required fields can be found under :menuselection:`Partner --> Sales & " +"Purchase Tab --> Fiscal Information section`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:170 +msgid "" +":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal " +"responsibility for the company (`O-13` Gran Contribuyente, `O-15` " +"Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de " +"tributación simple, or `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:175 +msgid "" +":guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, " +"`INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:183 +msgid "" +"To manage products, navigate to :menuselection:`Accounting --> Customers -->" +" Products`, then click on a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "" +"When adding general information on the product form, it is required that " +"either the :guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or " +":guilabel:`Internal Reference` (:guilabel:`General Information` tab) field " +"is configured. Be sure to :guilabel:`Save` the product once configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:194 +msgid "" +"To create or modify taxes, go to :menuselection:`Accounting --> " +"Configuration --> Taxes`, and select the related tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:197 +msgid "" +"If sales transactions include products with taxes, the :guilabel:`Value " +"Type` field in the :guilabel:`Advanced Options` tab needs to be configured " +"per tax. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, " +":guilabel:`Fuente`) are also included. This configuration is used to display" +" taxes correctly in the invoice PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:85 +msgid "Sales journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:211 +msgid "" +"Once the |DIAN| has assigned the official sequence and prefix for the " +"electronic invoice resolution, the sales journals related to the invoice " +"documents **must** be updated in Odoo. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Journals`, and select an " +"existing sales journal, or create a new one with the :guilabel:`Create` " +"button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:216 +msgid "" +"On the sales journal form, input the :guilabel:`Journal Name`, " +":guilabel:`Type`, and set a unique :guilabel:`Short Code` in the " +":guilabel:`Journals Entries` tab. Then, configure the following data in the " +":guilabel:`Advanced Settings` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:220 +msgid "" +":guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:221 +msgid "" +":guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the " +"company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:222 +msgid ":guilabel:`Resolution Date`: Initial effective date of the resolution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:223 +msgid "" +":guilabel:`Resolution end date`: End date of the resolution's validity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:224 +msgid "" +":guilabel:`Range of Numbering (minimum)`: First authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:225 +msgid "" +":guilabel:`Range of Numbering (maximum)`: Last authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:228 +msgid "" +"The sequence and resolution of the journal **must** match the one configured" +" in Carvajal and the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:232 +msgid "Invoice sequence" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +msgid "" +"The invoice sequence and prefix **must** be correctly configured when the " +"first document is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:237 +msgid "" +"Odoo automatically assigns a prefix and sequence to the following invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 +msgid "Purchase journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:242 +msgid "" +"Once the |DIAN| has assigned the official sequence and prefix for the " +"*support document* related to vendor bills, the purchase journals related to" +" their supporting documents need to be updated in Odoo. The process is " +"similar to the configuration of the :ref:`sales journals `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:249 +msgid "" +"The :doc:`chart of accounts " +"` is " +"installed by default as part of the localization module, the accounts are " +"mapped automatically in taxes, default account payable, and default account " +"receivable. The chart of accounts for Colombia is based on the PUC (Plan " +"Unico de Cuentas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +msgid "Main workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:262 +msgid "" +"The following is a breakdown of the main workflow for electronic invoices " +"with the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:265 +msgid "Sender creates an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:266 +msgid "Electronic invoice provider generates the legal XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:267 +msgid "" +"Electronic invoice provider creates the CUFE (Invoice Electronic Code) with " +"the electronic signature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:269 +msgid "Electronic invoice provider sends a notification to |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:270 +msgid "|DIAN| validates the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:271 +msgid "|DIAN| accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +msgid "Electronic invoice provider generates the PDF invoice with a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:273 +msgid "Electronic invoice provider sends invoice to the acquirer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 +msgid "" +"Acquirer sends a receipt of acknowledgement, and accepts or rejects the " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:275 +msgid "Sender downloads a :file:`.zip` file with the PDF and XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Electronic invoice workflow for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:287 +msgid "" +"The functional workflow taking place before an invoice validation does " +"**not** alter the main changes introduced with the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:290 +msgid "" +"Electronic invoices are generated and sent to both the |DIAN| and customer " +"through Carvajal's web service integration. These documents can be created " +"from your sales order or manually generated. To create a new invoice, go to " +":menuselection:`Accounting --> Customers --> Invoices`, and select " +":guilabel:`Create`. On the invoice form configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:295 +msgid ":guilabel:`Customer`: Customer's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:296 +msgid ":guilabel:`Journal`: Journal used for electronic invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 +msgid "" +":guilabel:`Electronic Invoice Type`: Select the type of document. By " +"default, :guilabel:`Factura de Venta` is selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 +msgid "" +":guilabel:`Invoice Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 +msgid "When done, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 +#: ../../content/applications/finance/fiscal_localizations/india.rst:116 +#: ../../content/applications/finance/fiscal_localizations/india.rst:257 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:389 +msgid "Invoice validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 +msgid "" +"After the invoice confirmation, an XML file is created and sent " +"automatically to Carvajal. The invoice is then processed asynchronously by " +"the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in " +"the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Carvajal XML invoice file in Odoo chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:316 +msgid "" +"The :guilabel:`Electronic Invoice Name` field is now displayed in the " +":guilabel:`EDI Documents` tab, with the name of the XML file. Additionally, " +"the :guilabel:`Electronic Invoice Status` field is displayed with the " +"initial value :guilabel:`To Send`. To process the invoice manually, click on" +" the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:324 +msgid "Reception of legal XML and PDF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:326 +msgid "" +"The electronic invoice vendor (Carvajal) receives the XML file, and proceeds" +" to validate its structure and information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:329 +msgid "" +"After validating the electronic invoice, proceed to generate a legal XML " +"which includes a digital signature and a unique code (CUFE), a PDF invoice " +"that includes a QR code and the CUFE is also generated. If everything is " +"correct the :guilabel:`Electronic Invoicing` field value changes to " +":guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:334 +msgid "" +"A :file:`.zip` containing the legal electronic invoice (in XML format) and " +"the invoice in (PDF format) is downloaded and displayed in the invoice " +"chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "ZIP file displayed in the invoice chatter in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 +msgid "The electronic invoice status changes to :guilabel:`Accepted`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:346 +msgid "" +"The process for credit notes is the same as for invoices. To create a credit" +" note with reference to an invoice, go to :menuselection:`Accounting --> " +"Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note`, " +"and complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:350 +msgid ":guilabel:`Credit Method`: Select the type of credit method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:352 +msgid "" +":guilabel:`Partial Refund`: Use this option when it is a partial amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:353 +msgid "" +":guilabel:`Full Refund`: Use this option if the credit note is for the full " +"amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:354 +msgid "" +":guilabel:`Full refund and new draft invoice`: Use this option if the credit" +" note is auto-validated and reconciled with the invoice. The original " +"invoice is duplicated as a new draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:358 +msgid ":guilabel:`Reason`: Enter the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:359 +msgid "" +":guilabel:`Reversal Date`: Select if you want a specific date for the credit" +" note or if it is the journal entry date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:361 +msgid "" +":guilabel:`Use Specific Journal`: Select the journal for your credit note or" +" leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:363 +msgid "" +":guilabel:`Refund Date`: If you chose a specific date, select the date for " +"the refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +msgid "Once reviewed, click the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +msgid "" +"The process for debit notes is similar to credit notes. To create a debit " +"note with reference to an invoice, go to :menuselection:`Accounting --> " +"Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit " +"Note` button, and enter the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:374 +msgid ":guilabel:`Reason`: Type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:375 +msgid ":guilabel:`Debit note date`: Select the specific options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:376 +msgid "" +":guilabel:`Copy lines`: Select this option if you need to register a debit " +"note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +msgid "" +":guilabel:`Use Specific Journal`: Select the printer point for your debit " +"note, or leave it empty if you want to use the same journal as the original " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:381 +msgid "When done, click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:384 +msgid "Support document for vendor bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:386 +msgid "" +"With master data, credentials, and the purchase journal configured for " +"support documents related to vendor bills, you can start using *support " +"documents*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:389 +msgid "" +"Support documents for vendor bills can be created from your purchase order " +"or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and " +"fill in the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:392 +msgid ":guilabel:`Vendor`: Enter the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:393 +msgid ":guilabel:`Bill Date`: Select the date of the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:394 +msgid "" +":guilabel:`Journal`: Select the journal for support documents related to the" +" vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:395 +msgid "" +":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:397 +msgid "" +"Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an " +"XML file is created and automatically sent to Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:405 +msgid "" +"During the XML validation, the most common errors are related to missing " +"master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such " +"cases, error messages are shown in the chatter after updating the electronic" +" invoice status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:409 +msgid "" +"After the master data is corrected, it's possible to reprocess the XML with " +"the new data and send the updated version, using the :guilabel:`Retry` " +"button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "XML validation errors shown in the invoice chatter in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:421 +msgid "Certificado de Retención en ICA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:423 +msgid "" +"This report is a certification to vendors for withholdings made for the " +"Colombian Industry and Commerce (ICA) tax. The report can be found under " +":menuselection:`Accounting --> Reporting --> Colombian Statements --> " +"Certificado de Retención en ICA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en ICA report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:432 +msgid "Certificado de Retención en IVA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:434 +msgid "" +"This report issues a certificate on the amount withheld from vendors for VAT" +" withholding. The report can be found under :menuselection:`Accounting --> " +"Reporting --> Colombian Statements --> Certificado de Retención en IVA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en IVA report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:443 +msgid "Certificado de Retención en la Fuente" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:445 +msgid "" +"This certificate is issued to partners for the withholding tax that they " +"have made. The report can be found under :menuselection:`Accounting --> " +"Reporting --> Colombian Statements --> Certificado de Retención en Fuente`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en Fuente report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:3 +msgid "Ecuador" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:8 +msgid "" +"With the Ecuadorian localization you can generate electronic documents with " +"its XML, Fiscal folio, with electronic signature and direct connection to " +"tax authority SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:11 +msgid "" +"The supported documents are Invoices, Credit Notes, Debit Notes, Purchase " +"Liquidations and Withholds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:14 +msgid "" +"The localization also Includes automations to easily predict the withholding" +" tax to be applied to each purchase invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:18 +msgid "" +"`App Tour - Localización de Ecuador " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:19 +msgid "" +"`Smart Tutorial - Localización de Ecuador " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:22 +#: ../../content/applications/finance/spreadsheet.rst:26 +msgid "Glossary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:24 +msgid "Here are some terms that are essential on the Ecuadorian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:26 +msgid "" +"**SRI**: meaning *Servicio de Rentas Internas*, the government organization " +"that enforces pay of taxes in Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:28 +msgid "" +"**EDI**: stands for *Electronic Data Interchange*, which refers to the " +"sending of Electronics Documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:30 +msgid "" +"**RIMPE**: stands for *Regimen Simplificado para Emprendedores y Negocios*, " +"the type of taxpayer qualified for SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:39 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Ecuadorian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:49 +msgid ":guilabel:`Ecuadorian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:50 +msgid "`l10n_ec`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:51 +msgid "" +"The default :doc:`fiscal localization package <../fiscal_localizations>`, " +"adds accounting characteristics for the Ecuadorian localization, which " +"represent the minimum configuration required for a company to operate in " +"Ecuador according to the guidelines set by the :abbr:`SRI (servicio de " +"rentas internas)`. The module's installation automatically loads: Chart of " +"Accounts, taxes, documents types, tax support types. Additionally, the " +"generation of forms 103 and 104 are automatic." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:57 +msgid ":guilabel:`Ecuadorian Accounting EDI`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:58 +msgid "`l10n_ec_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:59 +msgid "" +"Includes all the technical and functional requirements to generate and " +"validate :doc:`Electronics Documents " +"<../accounting/customer_invoices/electronic_invoicing>`, based on the " +"Technical documentation published by the SRI. The authorized documents are: " +"Invoices, Credit Notes, Debit Notes, Withholdings and Purchase liquidations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:66 +msgid "" +"When you install a database from scratch selecting `Ecuador` as the country," +" Odoo automatically installs the base module :guilabel:`Ecuadorian - " +"Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:72 +msgid "" +"To configure your company information, go to the :guilabel:`Contacts` app " +"and search the name given to your company or activate :ref:`developer mode " +"` and go to :menuselection:`Company --> Contact` and then " +"edit the contact to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:76 +msgid "Check the :guilabel:`Company` option on top" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:79 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:85 +msgid "Upload company logo and save" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Populate company data for Ecuador in Odoo Contacts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:94 +msgid "" +"To upload your information for electronic documents go to " +":menuselection:`Accounting --> Configuration --> Settings` and search for " +":command:`Ecuadorian Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 +msgid "Configure the next information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 +msgid ":guilabel:`Company legal name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 +msgid "" +":guilabel:`Use production servers`: check the checkbox if your company is " +"going to do electronic documents in the production environment. If you want " +"to use the testing environment for electronic documents then keep the " +"checkbox unchecked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:103 +msgid "" +":guilabel:`Regime`: select if your company is in General Regular or is " +"qualified as RIMPE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:104 +msgid "" +":guilabel:`Forced to keep accounting books`: check the checkbox if your " +"company has this condition." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:106 +msgid ":guilabel:`Default taxes for withholdings`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:107 +msgid "" +":guilabel:`Issue withholds`: check the checkbox if your company is going to " +"do electronic withholds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 +msgid "" +":guilabel:`Withhold consumibles`: put the code of the withholding for when " +"you buy goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:110 +msgid "" +":guilabel:`Withhold services`: put the code of the withholding for when you " +"buy services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 +msgid "" +":guilabel:`Withhold credit card`: put the code of the withholding for when " +"you buy with credit card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:113 +msgid "" +":guilabel:`Withhold agent number`: put the company withholding agent " +"resolution number, if applicable for your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:115 +msgid "" +":guilabel:`Electronic Certificate File`: upload electronic certificate and " +"password, then save it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 +msgid "" +":guilabel:`Special tax contributor number`: if your company is qualified as " +"a special taxpayer, fill out this field with it's corresponding tax " +"contributor number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Electronic signature for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:124 +msgid "" +"When configuring the withholdings in the configuration menu, these suggested" +" withholdings are only for domestic suppliers when no withholdings are setup" +" on their *Taxpayer Type*. Moreover, the Credit Card withholding set up is " +"always used when a Credit or Debit Card SRI Payment Metho is used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 +msgid "VAT withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 +msgid "" +"This configuration only applies if you are qualified as a *Withholding " +"Agent* by the SRI, otherwise skip this step. To configure your VAT " +"withholding, go to :menuselection:`Accounting --> Accounting --> " +"Configuration --> Ecuadorian SRI: Taxpayer Type SRI`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:136 +msgid "" +"You must configure the withholding percentage that applies for each type of " +"taxpayer, specify the :guilabel:`Goods VAT Withholding` and the " +":guilabel:`Services VAT Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxpayer Type configuration for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:144 +msgid "" +"In the case that the :guilabel:`Taxpayer Type` is `RIMPE`, also configure " +"the :guilabel:`Profit Withholding` percentage." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:148 +msgid "Printer points" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:150 +msgid "" +"To configure your printer points, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:153 +msgid "" +"Printer points need to be configured for each type of electronic document " +"that you need. For example: Customer Invoice, Credit Notes, and Debit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:156 +msgid "" +"For each printer point, you need to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:158 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Sales Documents`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:160 +msgid ":guilabel:`Type`: refers to the type of journal, select `Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:161 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:195 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:222 +msgid "" +":guilabel:`Use Documents?`: this checkbox is automatically checked, leave it" +" checked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:162 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:196 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:223 +msgid ":guilabel:`Emission Entity`: configure the establishment number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:163 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:197 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:224 +msgid ":guilabel:`Emission Point`: configure the printer point." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:164 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:198 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:225 +msgid "" +":guilabel:`Emission address`: configure the address of the establishment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:165 +msgid "" +":guilabel:`Default income account`: configure the default income account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:166 +msgid "" +":guilabel:`Dedicated Credit Note Sequence`: check the checkbox if *Credit " +"Notes* are to be generated from this printer point - journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:168 +msgid "" +":guilabel:`Short Code`: This is the unique code for the sequence of " +"accounting entries, enter a unique 5-digit code, for example: `VT001`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:171 +msgid "" +"Customer Invoice, Credit Notes and Debit Notes need to use the same journal " +"as the :guilabel:`Emission Point`, and the :guilabel:`Entity Point` should " +"be unique per journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring a printer point for Ecuador electronic document type of Customer" +" Invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 +msgid "" +"In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic " +"Invoicing` checkbox to enable it for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:186 +msgid "Withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:188 +msgid "" +"A Withholding Journal must be defined, go to go to " +":menuselection:`Accounting --> Configuration --> Accounting: Journals` " +"where you need to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:191 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:193 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:220 +msgid "" +":guilabel:`Type`: refers to the type of journal, select `Miscellaneous`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:194 +msgid ":guilabel:`Withhold Type`: Configure Purchase Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:199 +msgid ":guilabel:`Default account`: configure the default income account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:200 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:226 +msgid "" +":guilabel:`Short Code`: This is the unique code for the sequence of " +"accounting entries, enter a unique 5-digit code, for example: `RT001`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring withholding for Ecuador electronic document type of Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:208 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:234 +msgid "" +"In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic " +"Invoicing` checkbox to enable the sending of electronic invoicing for the " +"withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 +msgid "Purchase Liquidations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:214 +msgid "" +"When using Purchase Liquidations, a specific journal must be created, go to " +":menuselection:`Accounting --> Configuration --> Accounting: Journals` and " +"configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:218 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Withhold`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:221 +msgid "" +":guilabel:`Purchase Liquidations`: check the checkbox to enable purchase " +"liquidations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring purchase liquidations for Ecuador electronic document type of " +"Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"is installed by default as part of the set of data included in the " +"localization module, the accounts are mapped automatically in Taxes, Default" +" Account Payable, Default Account Receivable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:247 +msgid "" +"The chart of accounts for Ecuador is based on the most updated version of " +"Superintendency of Companies, which is grouped in several categories and is " +"compatible with NIIF accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 +msgid "" +"In addition to the basic information in your products, you must add the " +"configuration of the withholding code (tax) that applies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 +msgid "" +"Go to :menuselection:`Accounting --> Vendors: Products` under the tab " +"\"Purchase\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Product for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 +msgid "Configure the next information when you create a contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:269 +msgid "" +"Check the :guilabel:`Company` option on top if it is a contact with RUC, or " +"check :guilabel:`Individual` if it is a contact with cedula or passport." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 +msgid "" +":guilabel:`Address`: :guilabel:`Street` is a required field to confirm the " +"Electronic Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:273 +msgid "" +":guilabel:`Identification Number`: select an identification type `RUC`, " +"`Cedula`, or `Passport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:274 +msgid ":guilabel:`Taxpayer Type`: select the contact's SRI Taxpayer Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Contacts for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:283 +msgid "" +"The :guilabel:`SRI Taxpayer Type` has inside the configuration of which VAT " +"and Profit withholding will apply when you use this contact on Vendor Bill, " +"and then create a withholding from there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 +msgid "Review your taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 +msgid "" +"As part of the localization module, taxes are automatically created with its" +" configuration and related financial accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxes for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:297 +msgid "The following options have been automatically configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:299 +msgid "" +":guilabel:`Tax Support`: to be configured only in the IVA tax, this option " +"is useful when you register purchase withholdings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:301 +msgid "" +":guilabel:`Code ATS`: to be configured only for income tax withholding " +"codes, it is important when you register the withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:303 +msgid "" +":guilabel:`Tax Grids`: configure the codes of 104 form if it is a IVA tax " +"and configure the codes of 103 form if it is a income tax withholding code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:305 +msgid ":guilabel:`Tax Name`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 +msgid "" +"For IVA tax, format the name as: `IVA [percent] (104, [form code] [tax " +"support code] [tax support short name])`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:309 +msgid "" +"For income tax withholding code, format the name as: `Code ATS [Percent of " +"withhold] [withhold name]`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:312 +msgid "" +"Once the Ecuador module is installed, the most common taxes are " +"automatically configured. If you need to create an additional one, you can " +"do so, for which you must base yourself on the configuration of the existing" +" taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxes with tax support for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:321 +msgid "Review your Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:323 +msgid "" +"Some accounting transactions like *Customer Invoices* and *Vendor Bills* are" +" classified by document types. These are defined by the government fiscal " +"authorities, in this case by the SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the document type includes the " +"country on which the document is applicable; also the data is created " +"automatically when the localization module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:330 +msgid "" +"The information required for the document types is included by default so " +"the user does not need to fill anything there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Document types for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 +msgid "" +"Once you have configured your database, you can register your documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:343 +msgid "Sales documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:348 +msgid "" +":guilabel:`Customer invoices` are electronic documents that, when validated," +" are sent to SRI. These documents can be created from your sales order or " +"manually. They must contain the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:351 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:395 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:428 +msgid ":guilabel:`Customer`: type the customer's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:352 +msgid "" +":guilabel:`Journal`: select the option that matches the printer point for " +"the customer invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:353 +msgid "" +":guilabel:`Document Type`: type document type in this format `(01) Invoice`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:354 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:474 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:512 +msgid "" +":guilabel:`Payment Method (SRI)`: select how the invoice is going to be " +"paid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:475 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:513 +msgid ":guilabel:`Products`: specify the product with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer invoice for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:362 +msgid "Customer credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:364 +msgid "" +"The :doc:`Customer credit note " +"<../accounting/customer_invoices/credit_notes>` is an electronic document " +"that, when validated, is sent to SRI. It is necessary to have a validated " +"(posted) invoice in order to register a credit note. On the invoice there is" +" a button named :guilabel:`Credit note`, click on this button to be directed" +" to the :guilabel:`Create credit note` form, then complete the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 +msgid ":guilabel:`Credit Method`: select the type of credit method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 +msgid "" +":guilabel:`Partial Refund`: use this option when you need to type the first " +"number of documents and if it is a partial credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:374 +msgid "" +":guilabel:`Full Refund`: use this option if the credit note is for the total" +" invoice and you need the credit note to be auto-validated and reconciled " +"with the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:376 +msgid "" +":guilabel:`Full refund and new draft invoice`: use this option if the credit" +" note is for the total invoice and you need the credit note to be auto-" +"validated and reconciled with the invoice, and auto-create a new draft " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:380 +msgid ":guilabel:`Reason`: type the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 +msgid ":guilabel:`Rollback Date`: select the :guilabel:`specific` options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:382 +msgid ":guilabel:`Reversal Date`: type the date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:383 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:416 +msgid "" +":guilabel:`Use Specific Journal`: select the printer point for your credit " +"note, or leave it empty if you want to use the same journal as the original " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:386 +msgid "Once reviewed, you can click on the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Add Customer Credit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:392 +msgid "" +"When the :guilabel:`Partial Refund` option is used, you can change the " +"amount of the credit note and then validate it. Before validating the credit" +" note, review the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:396 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:429 +msgid "" +":guilabel:`Journal`: select the printer point for the customer Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:397 +msgid "" +":guilabel:`Document Type`: this is the document type `(04) Credit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:398 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 +msgid "" +":guilabel:`Products`: It must specify the product with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer Credit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:405 +msgid "Customer debit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:407 +msgid "" +"The :guilabel:`Customer debit note` is an electronic document that, when " +"validated, is sent to SRI. It is necessary to have a validated (posted) " +"invoice in order to register a debit note. On the invoice there is a button " +"named :guilabel:`Debit Note`, click on this button to be directed to the " +":guilabel:`Create debit note` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:412 +msgid ":guilabel:`Reason`: type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:413 +msgid ":guilabel:`Debit note date`: select the :guilabel:`specific` options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 +msgid "" +":guilabel:`Copy lines`: select this option if you need to register a debit " +"note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:419 +msgid "" +"Once reviewed you can click on the :guilabel:`Create Debit Note` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Add Customer Debit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:425 +msgid "" +"You can change the debit note amount, and then validate it. Before " +"validating the debit note, review the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:430 +msgid "" +":guilabel:`Document Type`: this is the document type `(05) Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer Debit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:438 +msgid "Customer withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:440 +msgid "" +"The :guilabel:`Customer withholding` is a non-electronic document for your " +"company, this document is issued by the client in order to apply a " +"withholding to the sale." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:443 +msgid "" +"It is necessary to have a validated (posted) invoice in order to register a " +"customer withholding. On the invoice there is a button named :guilabel:`Add " +"Withhold`, click on this button to be directed to the :guilabel:`Customer " +"withholding` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 +msgid ":guilabel:`Document Number`: type the withholding number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:448 +msgid "" +":guilabel:`Withhold Lines`: select the taxes that the customer is " +"withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:450 +msgid "" +"Before validating the withholding, review that the amounts for each tax are " +"the same as the original document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer withhold for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:458 +msgid "Purchase Documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:461 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:130 +msgid "Vendor bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:463 +msgid "" +"The :guilabel:`Vendor bill` is a non-electronic document for your company, " +"this document is issued by your vendor when your company generates a " +"purchase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:466 +msgid "" +"The bills can be created from the purchase order or manually, it must " +"contain the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:469 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:506 +msgid ":guilabel:`Vendor`: type the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:470 +msgid ":guilabel:`Bill Date`: select the date of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:471 +msgid ":guilabel:`Journal`: it is the journal for vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:472 +msgid ":guilabel:`Document Type`: this is the document type `(01) Invoice`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:473 +msgid ":guilabel:`Document number`: type the document number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchases for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:482 +msgid "" +"When creating the purchase withholding, verify that the bases (base amounts)" +" are correct. If you need to edit the amount of the tax in the " +":guilabel:`Vendor bill`, click the :guilabel:`Edit` button. Otherwise, from " +"the :guilabel:`Journal Items` tab click the :guilabel:`Edit` button and set " +"the adjustment to go where you want." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 +msgid "Purchase liquidation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 +msgid "" +"The :guilabel:`Purchase liquidation` is an electronic document that, when " +"validated, is sent to SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 +msgid "" +"Companies issue this type of electronic document when they purchase, and the" +" vendor does not issue an invoice due to one or more of the following cases:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:495 +msgid "Services were provided by non-residents of Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:496 +msgid "" +"Services provided by foreign companies without residency or establishment in" +" Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:497 +msgid "" +"Purchase of goods or services from natural persons not registered with a " +"RUC, who due to their cultural level or hardiness are not able to issue " +"sales receipts or customer invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:499 +msgid "" +"Reimbursement for the purchase of goods or services to employees in a " +"dependency relationship (full-time employee)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:501 +msgid "" +"Services provided by members of collegiate bodies for the exercise of their " +"function." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:503 +msgid "" +"These types of electronic documents can be created from the " +":guilabel:`Purchase Order` or manually from the :guilabel:`Vendor Bills` " +"form view. It must contain the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 +msgid "" +":guilabel:`Journal`: select the journal for the :guilabel:`Purchase " +"Liquidation` with the correct printer point." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 +msgid "" +":guilabel:`Document Type`: this is the document type `(03) Purchase " +"Liquidation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:510 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:530 +msgid "" +":guilabel:`Document number`: type the document number (sequence), you will " +"only have to do this once, then the sequence will be automatically assigned " +"for the next documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:515 +msgid "" +"Once you review the information you can validate the :guilabel:`Purchase " +"Liquidation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchase liquidation for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:522 +msgid "Purchase withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:524 +msgid "" +"The :guilabel:`Purchase withholding` is an electronic document that, when " +"validated, is sent to SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 +msgid "" +"It is necessary to have an invoice in a validated state in order to register" +" a :guilabel:`Purchase withholding`. On the invoice, there is a button named" +" :guilabel:`Add Withhold`, click on this button to be directed to the " +":guilabel:`Withholding` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 +msgid "" +":guilabel:`Withhold lines`: The taxes appear automatically according to the " +"configuration of products and vendors, you should review if the taxes and " +"tax support are correct, and, if it is not correct, you can edit and select " +"the correct taxes and tax support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:536 +msgid "" +"Once you review the information you can validate the " +":guilabel:`Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchase withhold for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 +msgid "" +"You can't change the tax support for one that was not included in the " +"configuration of the taxes used on the :guilabel:`Vendor Bill`. To do so, go" +" to the tax applied on the :guilabel:`Vendor Bill` and change the " +":guilabel:`Tax Support` there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:547 +msgid "" +"A withholding tax can be divided into two or more lines, this will depend on" +" whether two or more withholdings percentages apply." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:551 +msgid "" +"The system suggests a VAT withholding of 30% with tax support 01, you can " +"add your VAT withholding of 70% in a new line with the same tax support, the" +" system will allow you as long as the total of the bases matches the total " +"from the :guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:556 +msgid "Financial Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:558 +msgid "" +"In Ecuador, there are fiscal reports that the company presents to SRI. In " +"Odoo, we have two of the main financial reports used by companies. These are" +" the reports 103 and 104." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:561 +msgid "" +"To get these reports go to the :guilabel:`Accounting` app and select " +":menuselection:`Reporting --> Statements Reports --> Tax Report` and then " +"filter by `Tax Report 103` or `Tax Report 104`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:565 +msgid "Report 103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:567 +msgid "" +"This report contains information of income tax withholdings in a given " +"period, this can be reported monthly or semi-annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:570 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 +msgid "" +"You can see the information needed to report, which includes base and tax " +"amounts, which also includes the tax code within the parenthesis in order to" +" report it to the SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Report 103 form for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:578 +msgid "Report 104" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 +msgid "" +"This report contains information on VAT tax and VAT withholding for a given " +"period, this can be monthly or semi-annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Report 104 form for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:8 +#: ../../content/applications/finance/fiscal_localizations/india.rst:8 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:8 +msgid "Installation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egyptian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:19 +msgid ":guilabel:`Egypt - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:20 +msgid "``l10n_eg``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:21 +#: ../../content/applications/finance/fiscal_localizations/india.rst:21 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:19 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:20 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:19 +msgid "" +"Default :ref:`fiscal localization package `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:22 +msgid ":guilabel:`Egyptian E-invoice Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:23 +msgid "``l10n_eg_edi_eta``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:24 +msgid "" +":ref:`Egyptian Tax Authority (ETA) e-invoicing integration " +"`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:29 +msgid "Egyptian e-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:31 +msgid "" +"Odoo is compliant with the **Egyptian Tax Authority (ETA) e-invoicing** " +"requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:34 +msgid "" +"Egyptian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade " +"` your database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:38 +msgid "" +"`Video: Egypt E-invoicing `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:39 +msgid ":doc:`/administration/upgrade`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:44 +msgid "Register Odoo on your ETA portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:46 +msgid "" +"You must register your Odoo ERP system on your ETA portal to get your API " +"credentials. You need these codes to :ref:`configure your Odoo Accounting " +"app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:49 +msgid "" +"Access your company profile on the ETA portal by clicking on :guilabel:`View" +" Taxpayer Profile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Clicking on \"View Taxpayer Profile\" on an ETA invoicing portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:55 +msgid "" +"Next, go to the :guilabel:`Representatives` section and then click on " +":guilabel:`Register ERP`. Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``)" +" and leave the other fields empty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Filling out of the form to register an ERP system on the ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:62 +msgid "" +"Once successfully registered, the website displays your API credentials:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:64 +msgid "Client ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:65 +msgid "Client Secret 1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:66 +msgid "Client Secret 2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:69 +msgid "" +"ETA should give you a username and a password to access their online portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:70 +msgid "Ask ETA to provide you with preproduction portal access as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:71 +msgid "These codes are confidential and should be stored safely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:76 +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:37 +#: ../../content/applications/finance/payment_providers/asiapay.rst:34 +#: ../../content/applications/finance/payment_providers/buckaroo.rst:27 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:29 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:30 +#: ../../content/applications/finance/payment_providers/razorpay.rst:37 +msgid "Configuration on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:78 +msgid "" +"To connect your Odoo database to your ETA portal account, go to " +":menuselection:`Accounting --> Configuration --> Settings --> ETA " +"E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and " +":guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on " +"your ETA portal `. Set an invoicing threshold " +"if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Configuration of the ETA E-Invoicing credentials in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:88 +msgid "" +"**Test on your preproduction portal** before starting to issue real invoices" +" on the production ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:90 +msgid "" +"**Credentials** for preproduction and production environments are different." +" Make sure to update them on Odoo when you move from one environment to " +"another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:92 +msgid "" +"If not done yet, fill out your company details with your company's full " +"address, country, and Tax ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:98 +msgid "ETA codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:100 +msgid "" +"E-invoicing works with a set of codes provided by the ETA. You can use the " +"`ETA documentation `_ to " +"code your business attributes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:103 +msgid "" +"Most of these codes are handled automatically by Odoo, provided that your " +":ref:`branches `, :ref:`customers " +"`, and :ref:`products ` are correctly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:107 +msgid "Company Information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:109 +msgid "Company Tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Branch ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "If you have only one branch, use ``0`` as the branch code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:112 +msgid "Activity type Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:114 +msgid "Other Information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Product Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Your company's products should be coded and matched with their **GS1** or " +"**EGS** codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Tax Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Most of the taxes codes are already configured on Odoo in the :guilabel:`ETA" +" Code (Egypt)` field. We advise you to make sure these codes match your " +"company's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:123 +msgid "" +"`Egyptian eInvoicing & eReceipt SDK - Code Tables " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:130 +msgid "Branches" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:132 +msgid "" +"Create a contact and a journal for each branch of your company and configure" +" its ETA settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:134 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"then click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:137 +msgid "" +"Name the journal according to your company's branch and set the " +":guilabel:`Type` as :guilabel:`Sales`. Next, open the " +":menuselection:`Advanced Settings` tab and fill out the :guilabel:`Egyptian " +"ETA settings` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:141 +msgid "" +"In the :guilabel:`Branch` field, select the branch's contact or create it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:142 +msgid "Set the :guilabel:`ETA Activity Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:143 +msgid "" +"Set the :guilabel:`ETA Branch ID` (use ``0`` if you have one branch only)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Sales journal configuration of an Egyptian company's branch" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:150 +msgid "" +"The contact selected in the :guilabel:`Branch` field must be set as a " +":guilabel:`Company` (**not** as an :guilabel:`Individual`), and the " +":guilabel:`Address` and :guilabel:`Tax ID` fields must be filled out." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:157 +msgid "Customers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:159 +msgid "" +"Make sure your customers' contact forms are correctly filled out so your " +"e-invoices are valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:161 +msgid "contact type: :guilabel:`Individual`: or :guilabel:`Company`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:162 +msgid ":guilabel:`Country`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:163 +msgid "" +":guilabel:`Tax ID`: Tax ID or Company registry for companies. National ID " +"for individuals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:166 +msgid "" +"You can edit your customers' contact forms by going to " +":menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:174 +msgid "" +"Make sure your products are correctly configured so your e-invoices are " +"valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:176 +msgid ":guilabel:`Product Type`: storable products, consumables, or services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:177 +msgid "" +":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled" +" :doc:`Units of Measure " +"<../../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:179 +msgid ":guilabel:`Barcode`: **GS1** or **EGS** barcode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:180 +msgid "" +":guilabel:`ETA Item code` (under the :menuselection:`Accounting` tab): if " +"the barcode doesn't match your ETA item code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:184 +msgid "" +"You can edit your products by going to :menuselection:`Accounting --> " +"Customers --> Products`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:189 +msgid "USB authentication" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:191 +msgid "" +"Each person who needs to electronically sign invoices needs a specific USB " +"key to authenticate and send invoices to the ETA portal through an ERP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:195 +msgid "" +"You can contact the :abbr:`ETA (Egyptian Tax Authority)` or `Egypt Trust " +"`_ to get these USB keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:201 +msgid "Install Odoo as a local proxy on your computer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:203 +msgid "" +"An Odoo local server works as a bridge between your computer and your Odoo " +"database hosted online." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:205 +msgid "" +"Download the Odoo Community installer from the page " +"https://www.odoo.com/page/download and start the installation on your " +"computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:208 +msgid "Select :guilabel:`Local Proxy Mode` as the type of install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "" +"Selection of \"Local Proxy Mode\" during the installation of Odoo Community." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:215 +msgid "" +"This installation of Odoo only works as a server and does not install any " +"Odoo apps on your computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:218 +msgid "" +"Once the installation is complete, the installer displays your **access " +"token** for the Odoo Local Proxy. Copy the token and save it in a safe place" +" for later use." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:222 +msgid "`Odoo: Download Odoo `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:223 +msgid ":doc:`../../../administration/install`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:228 +msgid "Configure the USB key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:230 +msgid "" +"Once the local proxy server is installed on your computer, you can link it " +"with your Odoo database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:232 +msgid "" +"Go to :menuselection:`Accounting --> Configurations --> Thumb Drive` and " +"click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:234 +msgid "" +"Input a :guilabel:`Company` name, the :guilabel:`ETA USB Pin` given to you " +"by your USB key provider, and the :guilabel:`Access Token` provided at the " +"end of the :ref:`local proxy installation `, " +"then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:237 +msgid "Click on :guilabel:`Get certificate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Creating a new thumb drive for the e-invoicing of an egyptian company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:3 +msgid "France" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:8 +msgid "FEC - Fichier des Écritures Comptables" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:10 +msgid "" +"An FEC :dfn:`Fichier des Écritures Comptables` audit file contains all the " +"accounting data and entries recorded in all the accounting journals for a " +"financial year. The entries in the file must be arranged in chronological " +"order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:14 +msgid "" +"Since January 1st, 2014, every French company is required to produce and " +"transmit this file upon request by the tax authorities for audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:18 +msgid "FEC Import" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:20 +msgid "" +"To make the onboarding of new users easier, Odoo Enterprise's French " +":ref:`fiscal localization package ` includes " +"the **FEC Import** feature (module name: ``l10n_fr_fec_import``), which " +"enables the import of existing FEC files from older software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:24 +msgid "" +"To enable this feature, go to :menuselection:`Accounting --> Configuration " +"--> Settings --> Accounting Import`, enable **FEC Import**, and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:27 +msgid "" +"Next, go to :menuselection:`Accounting --> Configuration --> FEC Import`, " +"upload your FEC file, and click on *Import*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Importing FEC files from different year takes no particular action or " +"computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Should multiple files contain any \"Reports à Nouveaux\" (RAN) with the " +"starting balance of the year, you might need to cancel those entries in the " +"User Interface. Odoo makes those entries (RAN) useless." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:38 +msgid "File formats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:40 +msgid "" +"FEC files can only be in CSV format, as the XML format is not supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:44 +msgid "" +"The FEC CSV file has a plain text format representing a data table, with the" +" first line being a header and defining the list of fields for each entry, " +"and each following line representing one accounting entry, in no " +"predetermined order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:48 +msgid "" +"Our module expects the files to meet the following technical specifications:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:50 +msgid "**Encoding**: UTF-8, UTF-8-SIG and iso8859_15." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:51 +msgid "**Separator**: any of these: `;` or `|` or `,` or `TAB`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:52 +msgid "" +"**Line terminators**: both CR+LF (`\\\\r\\\\n`) and LF (`\\\\n`) character " +"groups are supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:53 +msgid "**Date format**: `%Y%m%d`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:56 +msgid "Fields description and use" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "#" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Field name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Format" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "01" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "JournalCode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "Journal Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "`journal.code` and `journal.name` if `JournalLib` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Alphanumeric" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "02" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "JournalLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "Journal Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "`journal.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "03" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "EcritureNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "Numbering specific to each journal sequence number of the entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "`move.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "04" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "EcritureDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "Accounting entry Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "`move.date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Date (yyyyMMdd)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "05" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "CompteNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "Account Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "`account.code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "06" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "CompteLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "Account Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "`account.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "07" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "CompAuxNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "Secondary account Number (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "`partner.ref`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "08" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "CompAuxLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "Secondary account Label (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "`partner.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "09" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "PieceRef" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "Document Reference" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "`move.ref` and `move.name` if `EcritureNum` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "PieceDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "Document Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "11" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "EcritureLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "Account entry Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "`move_line.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "`move_line.debit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Float" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "13" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit amount (Field name \"Crédit\" is not allowed)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "`move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "14" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "EcritureLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "Accounting entry cross reference (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "`move_line.fec_matching_number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "DateLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "Accounting entry date (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "unused" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "16" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "ValidDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Accounting entry validation date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "17" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Montantdevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Currency amount (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "`move_line.amount_currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "18" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Idevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Currency identifier (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "`currency.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:108 +msgid "" +"These two fields can be found in place of the others in the sence above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Montant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "`move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Sens" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Can be \"C\" for Credit or \"D\" for Debit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "determines `move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Char" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 +msgid "Implementation details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:121 +msgid "" +"The following accounting entities are imported from the FEC files: " +"**Accounts, Journals, Partners**, and **Moves**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:124 +msgid "" +"Our module determines the encoding, the line-terminator character, and the " +"separator that are used in the file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:127 +msgid "" +"A check is then performed to see if every line has the correct number of " +"fields corresponding to the header." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:130 +msgid "" +"If the check passes, then the file is read in full, kept in memory, and " +"scanned. Accounting entities are imported one type at a time, in the " +"following order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:134 +msgid "Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:136 +msgid "" +"Every accounting entry is related to an account, which should be determined " +"by the field `CompteNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:140 +msgid "Code matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:142 +msgid "" +"Should a similar account code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:145 +msgid "" +"Accounts in Odoo generally have a number of digits that are default for the " +"fiscal localization. As the FEC module is related to the French " +"localization, the default number of relevant digits is 6." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:148 +msgid "" +"This means that the account codes the trailing zeroes are right-trimmed, and" +" that the comparison between the account codes in the FEC file and the ones " +"already existing in Odoo is performed only on the first six digits of the " +"codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:153 +msgid "" +"The account code `65800000` in the file is matched against an existing " +"`658000` account in Odoo, and that account is used instead of creating a new" +" one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:157 +msgid "Reconcilable flag" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:159 +msgid "" +"An account is technically flagged as *reconcilable* if the first line in " +"which it appears has the `EcritureLet` field filled out, as this flag means " +"that the accounting entry is going to be reconciled with another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:165 +msgid "" +"In case the line somehow has this field not filled out, but the entry still " +"has to be reconciled with a payment that hasn't yet been recorded, this " +"isn't a problem anyway; the account is flagged as reconcilable as soon as " +"the import of the move lines requires it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:170 +msgid "Account type and Templates matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:172 +msgid "" +"As the **type** of the account is not specified in the FEC format, **new** " +"accounts are created with the default type *Current Assets* and then, at the" +" end of the import process, they are matched against the installed Chart of " +"Account templates. Also, the *reconcile* flag is also computed this way." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:177 +msgid "" +"The match is done with the left-most digits, starting by using all digits, " +"then 3, then 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:54 +msgid "Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "Full comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "3-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "2-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_providers/authorize.rst:83 +msgid "Template" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40100000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`401`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "**Result**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "Match **found**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 +msgid "" +"The type of the account is then flagged as *payable* and *reconcilable* as " +"per the account template." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:196 +msgid "" +"Journals are also checked against those already existing in Odoo to avoid " +"duplicates, also in the case of multiple FEC files imports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:199 +msgid "" +"Should a similar journal code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:202 +msgid "New journals have their name prefixed by the string ``FEC-``." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:205 +msgid "`ACHATS` -> `FEC-ACHATS`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:207 +msgid "" +"The journals are *not* archived, the user is entitled to handle them as he " +"wishes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:210 +msgid "Journal type determination" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:212 +msgid "" +"The journal type is also not specified in the format (as per the accounts) " +"and therefore it is at first created with the default type `general`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:215 +msgid "" +"At the end of the import process, the type is determined as per these rules " +"regarding related moves and accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`bank`: Moves in these journals always have a line (debit or credit) " +"impacting a liquidity account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`cash` / `bank` can be interchanged, so `bank` is set everywhere when this " +"condition is met." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`sale`: Moves in these journals mostly have debit lines on receivable " +"accounts and credit lines on tax income accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Sale refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`purchase`: Moves in these journals mostly have credit lines on payable " +"accounts and debit lines on expense accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Purchase refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "`general`: for everything else." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:231 +msgid "A minimum of three moves is necessary for journal type identification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:232 +msgid "" +"A threshold of 70% of moves must correspond to a criteria for a journal type" +" to be determined." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:235 +msgid "Suppose we are analyzing the moves that share a certain `journal_id`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +#: ../../content/applications/finance/fiscal_localizations/france.rst:269 +msgid "Moves" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Count" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Percentage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "that have a sale account line and no purchase account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "that have a purchase account line and no sale account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "25%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "that have a liquidity account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "3" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "**75%**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "**Total**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "4" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "100%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 +msgid "" +"The journal `type` would be `bank`, because the bank moves percentage (75%) " +"exceeds the threshold (70%)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:253 +msgid "Partners" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:255 +msgid "Each partner keeps its `Reference` from the field `CompAuxNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:259 +msgid "" +"These fields are searchable, in line with former FEC imports on the " +"accounting expert's side for fiscal/audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:264 +msgid "" +"Users can merge partners with the Data Cleaning App, where Vendors and " +"Customers or similar partner entries may be merged by the user, with " +"assistance from the system that groups them by similar entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:271 +msgid "" +"Entries are immediately posted and reconciled after submission, using the " +"`EcritureLet` field to do the matching between the entries themselves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:274 +msgid "" +"The `EcritureNum` field represents the name of the moves. We noticed that " +"sometimes it may not be filled out. In this case, the field `PieceRef` is " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:278 +msgid "Rounding issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:280 +msgid "" +"There is a rounding tolerance with a currency-related precision on debit and" +" credit (i.e., 0.01 for EUR). Under this tolerance, a new line is added to " +"the move, named *Import rounding difference*, targeting the accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:284 +msgid "`658000` Charges diverses de gestion courante, for added debits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:285 +msgid "`758000` Produits divers de gestion courante, for added credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:288 +msgid "Missing move name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:290 +msgid "" +"Should the `EcritureNum` not be filled out, it may also happen that the " +"`PieceRef` field is also not suited to determine the move name (it may be " +"used as an accounting move line reference) leaving no way to actually find " +"which lines are to be grouped in a single move, and effectively impeding the" +" creation of balanced moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:295 +msgid "" +"One last attempt is made, grouping all lines from the same journal and date " +"(`JournalLib`, `EcritureDate`). Should this grouping generate balanced moves" +" (sum(credit) - sum(debit) = 0), then each different combination of journal " +"and date creates a new move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:300 +msgid "" +"`ACH` + `2021/05/01` --> new move on journal `ACH` with name `20210501`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:302 +msgid "" +"Should this attempt fail, the user is prompted an error message with all the" +" move lines that are supposedly unbalanced." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:308 +msgid "" +"If a line has the partner information specified, the information is copied " +"to the accounting move itself if the targeted Journal is of type *payable* " +"or *receivable*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:312 +msgid "Export" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:314 +msgid "" +"If you have installed the French :ref:`fiscal localization package " +"`, you should be able to download the FEC. To" +" do so, go to :menuselection:`Accounting --> Reporting --> France --> FEC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:320 +msgid "" +"If you do not see the submenu **FEC**, go to :menuselection:`Apps`, remove " +"the *Apps* filter, then search for the module named **France-FEC** and make " +"sure it is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:325 +msgid "" +"`Official Technical Specification (fr) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:327 +msgid "" +"`Test-Compta-Demat (Official FEC Testing tool) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:331 +msgid "French Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:333 +msgid "" +"If you have installed the French Accounting, you will have access to some " +"accounting reports specific to France:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:336 +msgid "Bilan comptable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:337 +msgid "Compte de résultats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:338 +msgid "Plan de Taxes France" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:341 +msgid "Get the VAT anti-fraud certification with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:343 +msgid "" +"As of January 1st 2018, a new anti-fraud legislation comes into effect in " +"France and DOM-TOM. This new legislation stipulates certain criteria " +"concerning the inalterability, security, storage and archiving of sales " +"data. These legal requirements are implemented in Odoo, version 9 onward, " +"through a module and a certificate of conformity to download." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:350 +msgid "Is my company required to use anti-fraud software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:352 +msgid "" +"Your company is required to use an anti-fraud cash register software like " +"Odoo (CGI art. 286, I. 3° bis) if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:355 +msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:356 +msgid "Some of your customers are private individuals (B2C)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:358 +msgid "" +"This rule applies to any company size. Auto-entrepreneurs are exempted from " +"VAT and therefore are not affected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:362 +msgid "Get certified with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:364 +msgid "Getting compliant with Odoo is very easy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:366 +msgid "" +"Your company is requested by the tax administration to deliver a certificate" +" of conformity testifying that your software complies with the anti-fraud " +"legislation. This certificate is granted by Odoo SA to Odoo Enterprise users" +" `here `_. If you " +"use Odoo Community, you should :doc:`upgrade to Odoo Enterprise " +"` or contact your Odoo service " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:373 +msgid "In case of non-conformity, your company risks a fine of €7,500." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:375 +msgid "To get the certification, just follow the following steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:377 +msgid "" +"If you use **Odoo Point of Sale**, :ref:`install ` the " +"**France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 " +"bis)** module by going to :menuselection:`Apps`, removing the *Apps* filter," +" then searching for *l10n_fr_pos_cert*, and installing the module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:381 +msgid "" +"Make sure a country is set on your company, otherwise your entries won’t be " +"encrypted for the inalterability check. To edit your company’s data, go to " +":menuselection:`Settings --> Users & Companies --> Companies`. Select a " +"country from the list; Do not create a new country." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:385 +msgid "" +"Download the mandatory certificate of conformity delivered by Odoo SA `here " +"`__." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:389 +msgid "" +"To install the module in any system created before December 18th 2017, you " +"should update the modules list. To do so, activate the :ref:`developer mode " +"`. Then go to the *Apps* menu and press *Update Modules " +"List* in the top-menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:393 +msgid "" +"In case you run Odoo on-premise, you need to update your installation and " +"restart your server beforehand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:395 +msgid "" +"If you have installed the initial version of the anti-fraud module (prior to" +" December 18th 2017), you need to update it. The module's name was *France -" +" Accounting - Certified CGI 286 I-3 bis*. After an update of the modules " +"list, search for the updated module in *Apps*, select it and click " +"*Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is" +" installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:404 +msgid "Anti-fraud features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:406 +msgid "The anti-fraud module introduces the following features:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:408 +msgid "" +"**Inalterability**: deactivation of all the ways to cancel or modify key " +"data of POS orders, invoices and journal entries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:410 +msgid "**Security**: chaining algorithm to verify the inalterability;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:411 +msgid "" +"**Storage**: automatic sales closings with computation of both period and " +"cumulative totals (daily, monthly, annually)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:415 +msgid "Inalterability" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:417 +msgid "" +"All the possible ways to cancel and modify key data of paid POS orders, " +"confirmed invoices and journal entries are deactivated, if the company is " +"located in France or in any DOM-TOM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:423 +msgid "" +"If you run a multi-companies environment, only the documents of such " +"companies are impacted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:426 +msgid "Security" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:428 +msgid "" +"To ensure inalterability, every order or journal entry is encrypted upon " +"validation. This number (or hash) is calculated from the key data of the " +"document as well as from the hash of the precedent documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:433 +msgid "" +"The module introduces an interface to test the data inalterability. If any " +"information is modified on a document after its validation, the test will " +"fail. The algorithm recomputes all the hashes and compares them against the " +"initial ones. In case of failure, the system points out the first corrupted " +"document recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:439 +msgid "" +"Users with *Manager* access rights can launch the inalterability check. For " +"POS orders, go to :menuselection:`Point of Sales --> Reporting --> French " +"Statements`. For invoices or journal entries, go to " +":menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:446 +msgid "Storage" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:448 +msgid "" +"The system also processes automatic sales closings on a daily, monthly and " +"annual basis. Such closings distinctly compute the sales total of the period" +" as well as the cumulative grand totals from the very first sales entry " +"recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:454 +msgid "" +"Closings can be found in the *French Statements* menu of Point of Sale, " +"Invoicing and Accounting apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:459 +msgid "" +"Closings compute the totals for journal entries of sales journals (Journal " +"Type = Sales)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:461 +msgid "" +"For multi-companies environments, such closings are performed by company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:463 +msgid "" +"POS orders are posted as journal entries at the closing of the POS session. " +"Closing a POS session can be done anytime. To prompt users to do it on a " +"daily basis, the module prevents from resuming a session opened more than 24" +" hours ago. Such a session must be closed before selling again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:469 +msgid "" +"A period’s total is computed from all the journal entries posted after the " +"previous closing of the same type, regardless of their posting date. If you " +"record a new sales transaction for a period already closed, it will be " +"counted in the very next closing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:476 +msgid "" +"For test & audit purposes such closings can be manually generated in the " +":ref:`developer mode `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:478 +msgid "" +"Then go to :menuselection:`Settings --> Technical --> Automation --> " +"Scheduled Actions`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:481 +msgid "Responsibilities" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:483 +msgid "" +"Do not uninstall the module! If you do so, the hashes will be reset and none" +" of your past data will be longer guaranteed as being inalterable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:486 +msgid "" +"Users remain responsible for their Odoo instance and must use it with due " +"diligence. It is not permitted to modify the source code which guarantees " +"the inalterability of data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:490 +msgid "" +"Odoo absolves itself of all and any responsibility in case of changes in the" +" module’s functions caused by 3rd party applications not certified by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:494 +msgid "More Information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:496 +msgid "" +"You can find more information about this legislation in the following " +"official documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:500 +msgid "" +"`Frequently Asked Questions " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:502 +msgid "" +"`Official Statement " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:504 +msgid "" +"`Item 88 of Finance Law 2016 " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:3 +msgid "Germany" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:6 +msgid "German Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:8 +msgid "" +"The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can " +"choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the Fiscal Localization " +"section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:12 +msgid "" +"Be careful, you can only change the accounting package as long as you have " +"not created any accounting entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:16 +msgid "" +"When you create a new Odoo Online database, the SKR03 is installed by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:19 +msgid "German Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:21 +msgid "" +"Here is the list of German-specific reports available on Odoo Enterprise:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:25 +msgid "Tax Report (Umsatzsteuervoranmeldung)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:26 +msgid "Partner VAT Intra" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:29 +msgid "Export from Odoo to Datev" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:31 +msgid "" +"It is possible to export your accounting entries from Odoo to Datev. To be " +"able to use this feature, the german accounting localization needs to be " +"installed on your Odoo Enterprise database. Then you can go in " +":menuselection:`Accounting --> Reporting --> General Ledger` then click on " +"the **Export Datev (csv)** button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:39 +msgid "Point of Sale in Germany: Technical Security System" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:41 +msgid "" +"The **Kassensicherungsverordnung** (The Act on Protection against " +"Manipulation of Digital Records) requires that electronic record-keeping " +"systems - including the :doc:`point of sale " +"` systems - must be equipped with a " +"**Technical Security System** (also called **TSS** or **TSE**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:46 +msgid "" +"Odoo offers a service that is compliant with the help of `fiskaly " +"`_, a *cloud-based solution*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:50 +msgid "" +"Since this solution is cloud-based, a working internet connection is " +"required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:53 +msgid "" +"The only VAT rates allowed are given by fiskaly. You can check these rates " +"by consulting: `fiskaly DSFinV-K API: VAT Definition " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:63 +msgid "" +"If your database was created before June 2021, :ref:`upgrade " +"` your **Point of Sale** app (`point_of_sale`) and the " +"**Restaurant** module (`pos_restaurant`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:65 +msgid "" +":ref:`Install ` the **Germany - Certification for Point of " +"Sale** (`l10n_de_pos_cert`) and **Germany - Certification for Point of Sale " +"of type restaurant** (`l10n_de_pos_res_cert`) modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:70 +msgid "" +"If these modules are not listed, :ref:`update the app list " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Upgrading Odoo Point of Sale from the Apps dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:77 +msgid "Register your company at the financial authority" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:79 +msgid "" +"To register your company, go to :menuselection:`Settings --> General " +"Settings --> Companies --> Update Info`, fill out the following fields and " +"*Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:82 +msgid "**Company name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:83 +msgid "Valid **address**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:84 +msgid "**VAT** number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:85 +msgid "" +"**St.-Nr** (Steuernummer): this number is assigned by the tax office to " +"every taxable natural or legal person. (e.g., `2893081508152`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:87 +msgid "" +"**W-IdNr** (Wirtschafts-Identifikationsnummer): this number is used as a " +"permanent identification number for economically active persons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:90 +msgid "" +"You can then **register your company through fiskaly** by opening the " +"*fiskaly* tab and clicking on the *fiskaly Registration* button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Button to register a company through fiskaly in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:98 +msgid "" +"If you do not see the *fiskaly Registration* button, make sure that you " +"*saved* your company details and are not in *editing mode* anymore." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:101 +msgid "Once the registration has been finalized, new fields appear:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:103 +msgid "" +"**fiskaly organization ID** refers to the ID of your company at the fiskaly " +"side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:104 +msgid "" +"**fiskaly API key** and **secret** are the credentials the system uses to " +"access the services offered by fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "fiskaly keys as displayed on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:112 +msgid "" +"It is possible to request new credentials if there is any issue with the " +"current ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:115 +msgid "Create and link a Technical Security System to your PoS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Create TSS option from a point of sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:121 +msgid "" +"To use your point of sale in Germany, you first have to create a :abbr:`TSS " +"(Technical Security System)` for it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:124 +msgid "" +"To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of" +" Sale`, open the point of sale you want to edit, then check the box next to " +"**Create TSS** and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Example of TSS ID and Client ID from fiskaly in Odoo Point of Sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:131 +msgid "" +"Once the creation of the TSS is successful, you can find your **TSS ID** and" +" **Client ID** under the *fiskaly API* section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:134 +msgid "**TSS ID** refers to the ID of your TSS at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:135 +msgid "**Client ID** refers to your PoS but at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:138 +msgid "DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Menu to export DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:144 +msgid "" +"Whenever you close a PoS session, the orders' details are sent to the " +":abbr:`DSFinV-K (Digitale Schnittstelle der Finanzverwaltung für " +"Kassensysteme)` service of fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:147 +msgid "" +"In case of an audit, you can export the data sent to DSFinV-K by going to " +":menuselection:`Point of Sale --> Orders --> DSFinV-k exports`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:150 +msgid "These fields are mandatory:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:152 +msgid "**Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:153 +msgid "" +"**Start Datetime** (export data with dates larger than or equal to the given" +" start date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:154 +msgid "" +"**End Datetime** (export data with dates smaller than or equal to the given " +"end date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:156 +msgid "" +"Leave the **Point of Sale** field blank if you want to export the data of " +"all your points of sale. Specify a Point of Sale if you want to export this " +"specific PoS' data only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:159 +msgid "" +"The creation of a DSFinV-K export triggers on export at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Pending DSFinV-K export on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:165 +msgid "" +"As you can see, the **State** is *Pending*. This means that the export has " +"been successfully triggered and is being processed. You have to click on " +"*Refresh State* to check if it is ready." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:171 +msgid "German Tax Accounting Standards: Odoo's guide to GoBD Compliance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:173 +msgid "" +"**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung" +" von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum" +" Datenzugriff " +"`_." +" In short, it is a **guideline for the proper management and storage of " +"books, records, and documents in electronic form, as well as for data " +"access**, that is relevant for the German tax authority, tax declaration, " +"and balance sheet." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:180 +msgid "" +"These principles have been written and published by the Federal Ministry of " +"Finance (BMF) in November 2014. Since January 2015, **they have become the " +"norm** and replace previously accepted practices linked to computer-based " +"accounting. Several changes have been made by the BMF in 2019 and January " +"2020 to specify some of the content and due to the development of digital " +"solutions (cloud hosting, paperless companies, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:187 +msgid "Odoo gives you **the means to be compliant with GoBD**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:190 +msgid "" +"What do you need to know about GoBD when relying on accounting software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:193 +msgid "" +"If you can, the best way to understand GoBD is to Read the `Official GoBD " +"text " +"`_." +" It is a bit long but quite readable for non-experts. But in short, here is " +"what to expect:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:197 +msgid "" +"The **GoBD is binding for companies that have to present accounts, which " +"includes SMEs, freelancers, and entrepreneurs, to the financial " +"authorities**. As such, **the taxpayer himself is the sole responsible** for" +" the complete and exhaustive keeping of fiscal-relevant data (above-" +"mentioned financial and related data)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:202 +msgid "" +"Apart from software requirements, the user is required to ensure Internal " +"control systems (*in accordance with sec. 146 of the Fiscal Code*):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:205 +msgid "Access rights control;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:206 +msgid "Segregation of Duties, Functional separating;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:207 +msgid "Entry controls (error notifications, plausibility checks);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:208 +msgid "Reconciliation checks at data entry;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:209 +msgid "Processing controls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:210 +msgid "" +"Measures to prevent intentional or unintentional manipulation of software, " +"data, or documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:212 +msgid "" +"The user must distribute tasks within its organization to the relevant " +"positions (*control*) and verify that the tasks are properly and completely " +"performed (*supervision*). The result of these controls must be recorded " +"(*documentation*), and should errors be found during these controls, " +"appropriate measures to correct the situation should be put into place " +"(*prevention*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:218 +msgid "What about data security?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:220 +msgid "" +"**The taxpayer must secure the system against any data loss due to " +"deletion, removal, or theft of any data**. If the entries are not " +"sufficiently secured, the bookkeeping will be regarded as not in accordance " +"with the GoBD guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:224 +msgid "" +"Once bookings have been finally posted, they can no longer be changed or " +"deleted via the application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:227 +msgid "" +"If Odoo is used in the cloud, regular backups are part of the Odoo Online " +"service. In addition, regular backups can be downloaded and backed up on " +"external systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:231 +msgid "" +"`Odoo Cloud Hosting - Service Level Agreement `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:233 +msgid "" +"If the server is operated locally, it is the responsibility of the user to " +"create the necessary backup infrastructure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:237 +msgid "" +"In some cases, data has to be kept for ten years or more, so always have " +"backups saved. It is even more important if you decide to change software " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:241 +msgid "Responsibility of the software editor" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:243 +msgid "" +"Considering GoBD only applies between the taxpayer and the financial " +"authority, **the software editor can by no means be held responsible for the" +" accurate and compliant documentation of financial transactional data of " +"their users**. It can merely provide the necessary tools for the user to " +"respect the software related guidelines described in the GoBD." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:249 +msgid "How can Odoo help you achieve Compliance?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:251 +msgid "" +"The key words, when it comes to GoBD, are: **traceable, verifiable, true, " +"clear, and continuous**. In short, you need to have audit-proof archiving in" +" place and Odoo provides you with the means to achieve all of these " +"objectives:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Traceability and verifiability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Each record in Odoo is stamped with the creator of the document, the " +"creation date, the modification date, and who modified it. In addition, " +"relevant fields are tracked thus it can be seen which value was changed by " +"whom in the chatter of the relevant object." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Completeness**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"All financial data must be recorded in the system, and there can be no gaps." +" Odoo ensures that there is no gap in the numbering of the financial " +"transactions. It is the responsibility of the user to encode all financial " +"data in the system. As most financial data in Odoo is generated " +"automatically, it remains the responsibility of the user to encode all " +"vendor bills and miscellaneous operations completely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Accuracy**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Odoo ensures with the correct configuration that the correct accounts are " +"used. In addition, the control mechanisms between purchase orders and sales " +"orders and their respective invoices reflect the business reality. It is the" +" responsibility of the user to scan and attach the paper-based vendor bill" +" to the respective record in Odoo. *Odoo Document helps you automate this " +"task*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Timely booking and record-keeping**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"As most financial data in Odoo is generated by the transactional objects " +"(for example, the invoice is booked at confirmation), Odoo ensures out-of-" +"the-box timely record-keeping. It is the responsibility of the user to " +"encode all incoming vendor bills in a timely manner, as well as the " +"miscellaneous operations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Financial data stored in Odoo is per definition ordered and can be reordered" +" according to most fields present in the model. A specific ordering is not " +"enforced by the GoBD, but the system must ensure that a given financial " +"transaction can be quickly found by a third-party expert. Odoo ensures this " +"out-of-the-box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Inalterability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"With the German Odoo localization, Odoo is in standard configured in such a " +"way that the inalterability clause can be adhered to without any further " +"customization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:286 +msgid "Do you need a GoBD-Export?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:288 +msgid "" +"In the case of fiscal control, the fiscal authority can request three levels" +" of access to the accounting system (Z1, Z2, Z3). These levels vary from " +"direct access to the interface to the handover of the financial data on a " +"storage device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:292 +msgid "" +"In case of a handover of the financial data on a storage device, the format " +"is **not** enforced by the GoBD. It can be, for example, in XLS, CSV, XML, " +"Lotus 123, SAP-format, AS/400-format, or else. Odoo supports the CSV and " +"XLS-export of financial data out-of-the-box. The GoBD **recommends** the " +"export in a specific XML-based GoBD-format (see \"Ergänzende Informationen " +"zur Datenntträgerüberlassung\" §3) but it is not binding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:299 +msgid "What is the role and meaning of the compliance certification?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:301 +msgid "" +"The GoBD clearly states that due to the nature of a state of the art " +"accounting software, their configuration possibilities, changing nature, and" +" various forms of use, **no legally binding certification can be given**, " +"nor can the software be made liable towards a public authority. Third-party " +"certificates can indeed have **an informative value** for customers to make " +"software buying decisions but are by no means legally binding or of any " +"other legal value (A. 12, § 181)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:307 +msgid "" +"A GoBD certificate states nothing more than that if you use the software " +"according to its guidelines, the software will not refrain you from " +"respecting the GoBD. These certifications are very expensive in terms of " +"time and cost, and their value is very relative. Thus we focus our efforts " +"on ensuring GoBD compliance rather than pay for a marketing tool which does " +"not, however, offer our customer any legal certainty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:314 +msgid "" +"The BMF actually states the following in the `Official GoBD text " +"`_:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:317 +msgid "" +"180. Positive attestations on the correctness of the bookkeeping - and thus " +"on the correctness of IT-based bookkeeping systems - are not issued either " +"in the context of a tax field audit or in the context of binding " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:320 +msgid "" +"181. \"Certificates\" or \"attestations\" from third parties can serve as a " +"decision criterion for the company when selecting a software product, but " +"develop from the in margin no. 179 is not binding on the tax authorities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:325 +msgid "" +"The previous content was `automatically translated from German with Google " +"Translate " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:330 +msgid "What happens if you are not compliant?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:332 +msgid "" +"In the event of an infringement, you can expect a fine but also a court " +"order demanding the implementation of specific measures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:6 +msgid "Add FPS QR codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:8 +msgid "" +":abbr:`FPS (Faster Payment System)` is a payment service platform that " +"allows customers to make instant domestic payments to individuals and " +"merchants in Hong Kong dollars or Renminbi via online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:13 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:12 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:125 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:12 +msgid "Activate QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:14 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:127 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:14 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Customer Payments` section, activate the :guilabel:`QR Codes` " +"feature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:19 +msgid "FPS bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:21 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate FPS. Set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:26 +msgid "" +"The account holder's country must be set to Hong Kong on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:27 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 +msgid "" +"You could also include the invoice number in the QR code by checking the " +":guilabel:`Include Reference` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:34 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:33 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:144 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:34 +msgid ":doc:`../accounting/bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:37 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:36 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:147 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:37 +msgid "Bank journal configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:39 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:38 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:39 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Journals`, open the " +"bank journal, then fill out the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +msgid "Bank Account's journal configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:46 +msgid "Issue invoices with FPS QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:48 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:47 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:48 +msgid "" +"When creating a new invoice, open the :guilabel:`Other Info` tab and set the" +" :guilabel:`Payment QR-code` option to *EMV Merchant-Presented QR-code*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +msgid "Select EMV Merchant-Presented QR-code option" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:54 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the FPS QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:3 +msgid "India" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Indian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:19 +msgid ":guilabel:`Indian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:20 +msgid "`l10n_in`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:22 +msgid ":guilabel:`Indian E-invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:23 +msgid "`l10n_in_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:24 +msgid ":ref:`Indian e-invoicing integration `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:25 +msgid ":guilabel:`Indian E-waybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:26 +msgid "`l10n_in_edi_ewaybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:27 +msgid ":ref:`Indian E-way bill integration `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:28 +msgid ":guilabel:`Indian - GSTR India eFiling`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:29 +msgid "`l10n_in_reports_gstr`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:30 +msgid ":ref:`Indian GST Return filing `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:31 +msgid ":guilabel:`Indian - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:32 +msgid "`l10n_in_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:33 +msgid ":ref:`Indian tax reports `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:34 +msgid ":guilabel:`Indian - Purchase Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:35 +msgid "`l10n_in_purchase`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:36 +msgid "Indian GST Purchase report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:37 +msgid ":guilabel:`Indian - Sale Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:38 +msgid "`l10n_in_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:39 +msgid "Indian GST Sale report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:40 +msgid ":guilabel:`Indian - Stock Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:41 +msgid "`l10n_in_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:42 +msgid "Indian GST Stock report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:50 +msgid "e-Invoice system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:52 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) e-Invoice " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:60 +msgid "NIC e-Invoice registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:62 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` e-Invoice" +" portal to get your **API credentials**. You need these credentials to " +":ref:`configure your Odoo Accounting app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:66 +msgid "" +"Log in to the `NIC e-Invoice portal `_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:70 +msgid "" +"If you are already registered on the NIC portal, you can use the same login " +"credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Register Odoo ERP system on e-invoice web portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:75 +msgid "" +"From the dashboard, go to :menuselection:`API Registration --> User " +"Credentials --> Create API User`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:77 +msgid "" +"After that, you should receive an :abbr:`OTP (one-time password)` code on " +"your registered mobile number. Enter the OTP code and click " +":guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:79 +msgid "" +"Select :guilabel:`Through GSP` for the API interface, set :guilabel:`Tera " +"Software Limited` as GSP, and type in a :guilabel:`Username` and " +":guilabel:`Password` for your API. Once it is done, click " +":guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit API specific Username and Password" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:89 +#: ../../content/applications/finance/fiscal_localizations/india.rst:228 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:91 +msgid "" +"To enable the e-Invoice service in Odoo, go to :menuselection:`Accounting " +"--> Configuration --> Settings --> Indian Electronic Invoicing`, and enter " +"the :guilabel:`Username` and :guilabel:`Password` previously set for the " +"API." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Setup e-invoice service" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:103 +msgid "" +"To automatically send e-Invoices to the NIC e-Invoice portal, you must first" +" configure your *sales* journal by going to :menuselection:`Accounting --> " +"Configuration --> Journals`, opening your *sales* journal, and in the " +":guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data " +"Interchange`, enable :guilabel:`E-Invoice (IN)` and save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:111 +#: ../../content/applications/finance/fiscal_localizations/india.rst:240 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:118 +msgid "" +"Once an invoice is validated, a confirmation message is displayed at the " +"top. Odoo automatically uploads the JSON-signed file of validated invoices " +"to the NIC e-Invoice portal after some time. If you want to process the " +"invoice immediately, click :guilabel:`Process now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-invoicing confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:126 +#: ../../content/applications/finance/fiscal_localizations/india.rst:266 +msgid "" +"You can find the JSON-signed file in the attached files in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:127 +msgid "" +"You can check the document's :abbr:`EDI (electronic data interchange)` " +"status under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic " +"invoicing` field of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:135 +msgid "" +"Once an invoice is validated and submitted, the invoice PDF report can be " +"printed. The report includes the :abbr:`IRN (Invoice Reference Number)`, " +":guilabel:`Ack. No` (acknowledgment number) and :guilabel:`Ack. Date` " +"(acknowledgment date), and QR code. These certify that the invoice is a " +"valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "IRN and QR code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:146 +msgid "e-Invoice cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:148 +msgid "" +"If you want to cancel an e-Invoice, go to the :guilabel:`Other info` tab of " +"the invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel" +" remarks` fields. Then, click :guilabel:`Request EDI cancellation`. The " +"status of the :guilabel:`Electronic invoicing` field changes to " +":guilabel:`To Cancel`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:154 +msgid "" +"Doing so cancels both the :ref:`e-Invoice ` and the " +":ref:`E-Way bill `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:161 +msgid "" +"If you want to abort the cancellation before processing the invoice, then " +"click :guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:163 +msgid "" +"Once you request to cancel the e-Invoice, Odoo automatically submits the " +"JSON-signed file to the NIC e-Invoice portal. You can click " +":guilabel:`Process now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:170 +msgid "GST e-Invoice verification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:172 +msgid "" +"After submitting an e-Invoice, you can verify if the invoice is signed from " +"the GST e-Invoice system website itself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:175 +msgid "" +"Download the JSON file from the attached files. It can be found in the " +"chatter of the related invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:177 +msgid "" +"Open the `NIC e-Invoice portal `_ and go to " +":menuselection:`Search --> Verify Signed Invoice`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:179 +msgid "Select the JSON file and submit it;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "select the JSON file for verify invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:184 +msgid "If the file is signed, a confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "verified e-invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:192 +msgid "E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:197 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) E-waybill " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:202 +msgid "API registration on NIC E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:204 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` E-Way " +"bill portal to create your **API credentials**. You need these credentials " +"to :ref:`configure your Odoo Accounting app `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:208 +msgid "" +"Log in to the `NIC E-Way bill portal `_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:210 +msgid "From your dashboard, go to :menuselection:`Registration --> For GSP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:211 +msgid "" +"Click :guilabel:`Send OTP`. Once you have received the code on your " +"registered mobile number, enter it and click :guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:213 +msgid "" +"Check if :guilabel:`Tera Software Limited` is already on the registered " +"GSP/ERP list. If so, use the username and password used to log in to the NIC" +" portal. Otherwise, follow the next steps;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "E-Way bill list of registered GSP/ERP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:219 +msgid "" +"Select :guilabel:`Add/New`, select :guilabel:`Tera Software Limited` as your" +" GSP Name, create a :guilabel:`Username` and a :guilabel:`Password` for your" +" API, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit GSP API registration details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:230 +msgid "" +"To set up the E-Way bill service, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Indian Electronic WayBill --> Setup E-Way " +"bill`, and enter your :guilabel:`Username` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill setup odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:245 +msgid "Send an E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:247 +msgid "" +"You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`." +" To send the E-Way bill automatically when an invoice or a bill is " +"confirmed, enable :guilabel:`E-Way bill (IN)` in your :ref:`Sales or " +"Purchase journal `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Send E-waybill button on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:259 +msgid "" +"Once an invoice has been issued and sent via :guilabel:`Send E-Way bill`, a " +"confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-Way bill confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:267 +msgid "" +"Odoo automatically uploads the JSON-signed file to the government portal " +"after some time. Click :guilabel:`Process now` if you want to process the " +"invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:273 +msgid "" +"You can print the invoice PDF report once you have submitted the E-Way bill." +" The report includes the **E-Way bill number** and the **E-Way bill validity" +" date**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill acknowledgment number and date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:282 +msgid "E-Way bill cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:284 +msgid "" +"If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of" +" the related invoice and fill out the :guilabel:`Cancel reason` and " +":guilabel:`Cancel remarks` fields. Then, click :guilabel:`Request EDI " +"Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:289 +msgid "" +"Doing so cancels both the :ref:`e-Invoice ` (if " +"applicable) and the :ref:`E-Way bill `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:296 +msgid "" +"If you want to abort the cancellation before processing the invoice, click " +":guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:298 +msgid "" +"Once you request to cancel the E-Way bill, Odoo automatically submits the " +"JSON-signed file to the government portal. You can click :guilabel:`Process " +"Now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:305 +msgid "Indian GST Return filing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:310 +msgid "Enable API access" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:312 +msgid "" +"To file GST Returns in Odoo, you must first enable API access on the GST " +"portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:314 +msgid "" +"Log into the `GST portal `_ by " +"entering your :guilabel:`Username` and :guilabel:`Password`, and go to " +":guilabel:`My Profile` on your **profile menu**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Click On the My Profile from profile" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:321 +msgid "" +"Select :guilabel:`Manage API Access`, and click :guilabel:`Yes` to enable " +"API access;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Click Yes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:326 +msgid "" +"Doing so enables a :guilabel:`Duration` drop-down menu. Select the " +":guilabel:`Duration` of your preference, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:332 +msgid "Indian GST Service In Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:334 +msgid "" +"Once you have enabled the :ref:`API access ` on the GST " +"portal, you can set up the :guilabel:`Indian GST Service` in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:337 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Indian " +"GST Service` and enter the :guilabel:`GST Username`. Click :guilabel:`Send " +"OTP`, enter the code, and finally, :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Please enter your GST portal Username as Username" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:347 +msgid "File-in GST Return" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:349 +msgid "" +"When the :guilabel:`Indian GST Service` is configured, you can file your GST" +" return. Go to :menuselection:`Accounting --> Reporting --> India --> GST " +"Return periods` and create a new **GST Return Period** if it does not exist." +" GST Return file-in is done in **three steps** in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:354 +msgid "" +"**Tax Return Periodicity** can be :doc:`configured " +"<../accounting/reporting/tax_returns>` according to the user's needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:361 +msgid "Send GSTR-1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:363 +msgid "" +"The user can verify the :ref:`GSTR-1 ` report before " +"uploading it to the **GST portal** by clicking :guilabel:`GSTR-1 Report`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:365 +msgid "" +"If the **GSTR-1** report is correct, then click :guilabel:`Push to GSTN` to " +"send it to the **GST portal**. The status of the :guilabel:`GSTR-1` report " +"changes to :guilabel:`Sending`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Sending Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:371 +msgid "" +"After a few seconds, the status of the **GSTR-1** report changes to " +":guilabel:`Waiting for Status`. It means that the **GSTR-1** report has been" +" sent to the :guilabel:`GST Portal` and is being verified on the " +":guilabel:`GST Portal`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Waiting for Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:378 +msgid "" +"Once more, after a few seconds, the status either changes to " +":guilabel:`Sent` or :guilabel:`Error in Invoice`. The status " +":guilabel:`Error in Invoice` indicates that some of the invoices are not " +"correctly filled out to be validated by the **GST portal**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:382 +msgid "" +"If the state of the **GSTR-1** is :guilabel:`Sent`, it means your **GSTR-1**" +" report is ready to be filed on the **GST portal**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Sent" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:388 +msgid "" +"If the state of the **GSTR-1** is :guilabel:`Error in Invoice`, invoices can" +" be checked for errors in the :guilabel:`Log Note`. Once issues have been " +"resolved, the user can click :guilabel:`Push to GSTN` to submit the file " +"again on the **GST portal**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Error in Invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Error in Invoice Log" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:398 +msgid "" +"Click :guilabel:`Mark as Filed` after filing the **GSTR-1** report on the " +"**GST portal**. The status of the report changes to :guilabel:`Filed` in " +"**Odoo**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Filed Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:407 +msgid "Receive GSTR-2B" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:409 +msgid "" +"Users can retrieve the **GSTR-2B Report** from the **GST portal**. This " +"automatically reconciles the **GSTR-2B** report with your Odoo bills;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:412 +msgid "" +"Click :guilabel:`Fetch GSTR-2B Summary` to retrieve the **GSTR-2B** summary." +" After a few seconds, the status of the report changes to :guilabel:`Waiting" +" for Reception`. This means Odoo is trying to receive the **GSTR-2B** report" +" from the **GST portal**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B in Waiting for Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:419 +msgid "" +"Once more, after a few seconds, the status of the **GSTR-2B** changes to the" +" :guilabel:`Being Processed`. It means Odoo is reconciling the **GSTR-2B** " +"report with your Odoo bills;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:425 +msgid "" +"Once it is done, the status of the **GSTR-2B** report changes to either " +":guilabel:`Matched` or :guilabel:`Partially Matched`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:428 +msgid "If the status is :guilabel:`Matched`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Matched" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:433 +msgid "" +"If the status is :guilabel:`Partially Matched`, you can make changes in " +"bills by clicking :guilabel:`View Reconciled Bills`. Once it is done, click " +":guilabel:`re-match`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Partially Matched" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Reconciled Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:445 +#: ../../content/applications/finance/fiscal_localizations/india.rst:490 +msgid "GSTR-3 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:447 +msgid "" +"The :ref:`GSTR-3 ` report is a monthly summary of " +"**sales** and **purchases**. This return is auto-generated by extracting " +"information from **GSTR-1** and **GSTR-2**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:450 +msgid "" +"Users can compare the **GSTR-3** report with the **GSTR-3** report available" +" on the **GST portal** to verify if they match by clicking :guilabel:`GSTR-3" +" Report`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:453 +msgid "" +"Once the **GSTR-3** report has been verified by the user and the tax amount " +"on the **GST portal** has been paid. Once paid, the report can be **closed**" +" by clicking :guilabel:`Closing Entry`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:459 +msgid "" +"In :guilabel:`Closing Entry`, add the tax amount paid on the **GST portal** " +"using challan, and click :guilabel:`POST` to post the :guilabel:`Closing " +"Entry`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Post Entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:465 +msgid "" +"Once posted, the **GSTR-3** report status changes to :guilabel:`Filed`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Filed" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:473 +msgid "Tax reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:478 +msgid "GSTR-1 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:480 +msgid "" +"The :guilabel:`GSTR-1` report is divided into sections. It displays the " +":guilabel:`Base` amount, :abbr:`CGST (Central Goods and Services Tax)`, " +":abbr:`SGST (State Goods and Service Tax)`, :abbr:`IGST (Integrated Goods " +"and Services Tax)`, and :guilabel:`CESS` for each section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:492 +msgid "The :guilabel:`GSTR-3` report contains different sections:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:494 +msgid "Details of inward and outward supply subject to a **reverse charge**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:495 +msgid "Eligible :abbr:`ITC (Income Tax Credit)`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:496 +msgid "Values of **exempt**, **Nil-rated**, and **non-GST** inward supply;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:497 +msgid "Details of inter-state supplies made to **unregistered** persons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:3 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:8 +msgid "E-Faktur Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:10 +msgid "" +"The **E-Faktur Module** is installed by default with the Indonesian " +"localization module. It allows one to generate a CSV file for one tax " +"invoice or for a batch of tax invoices to upload to the **Tax Office " +"e-Faktur** application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:17 +msgid "NPWP/NIK settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Company**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"This information is used in the FAPR line in the effect file format. You " +"need to set a VAT number on the related partner of your Odoo company. If you" +" don't, it won't be possible to create an e-Faktur from an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Clients**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. " +"You can use the VAT field on the customer's contact to set the NPWP needed " +"to generate the e-Faktur file. If your customer does not have an NPWP, just " +"enter the NIK in the same VAT field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:39 +msgid "Generate Tax Invoice Serial Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:41 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be" +" able to export customer invoices as e-Faktur for the Indonesian government," +" you need to put here the ranges of numbers you were assigned by the " +"government. When you validate an invoice, a number will be assigned based on" +" these ranges. Afterwards, you can filter the invoices still to export in " +"the invoices list and click on *Action*, then on *Download e-Faktur*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:46 +msgid "" +"After receiving new serial numbers from the Indonesian Revenue Department, " +"you can create a set of tax invoice serial numbers group through this list " +"view. You only have to specify the Min and Max of each serial numbers' group" +" and Odoo will format the number automatically to a 13-digits number, as " +"requested by the Indonesia Tax Revenue Department." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:50 +msgid "" +"There is a counter to inform you how many unused numbers are left in that " +"group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:58 +msgid "Generate e-faktur csv for a single invoice or a batch invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:60 +msgid "" +"Create an invoice from :menuselection:`Accounting --> Customers --> " +"Invoices`. If the invoice customer's country is Indonesia and the customer " +"is set as *ID PKP*, Odoo will allow you to create an e-Faktur." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:63 +msgid "" +"Set a Kode Transaksi for the e-Faktur. There are constraints related to the " +"Kode transaksi and the type of VAT applied to invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:69 +msgid "" +"Odoo will automatically pick the next available serial number from the " +"e-Faktur number table (see the :ref:`section above " +"`) and generate the e-faktur number " +"as a concatenation of Kode Transaksi and serial number. You can see this " +"from the invoice form view under the page *Extra Info* in the box " +"*Electronic Tax*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:77 +msgid "" +"Once the invoice is posted, you can generate and download the e-Faktur from " +"the *Action* menu item *Download e-faktur*. The checkbox *CSV created* will " +"be set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:83 +msgid "" +"You can select multiple invoices in list view and generate a batch e-Faktur " +".csv." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:88 +msgid "Kode Transaksi FP (Transaction Code)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:90 +msgid "" +"The following codes are available when generating an e-Faktur. - 01 Kepada " +"Pihak yang Bukan Pemungut PPN (Customer Biasa) - 02 Kepada Pemungut " +"Bendaharawan (Dinas Kepemerintahan) - 03 Kepada Pemungut Selain Bendaharawan" +" (BUMN) - 04 DPP Nilai Lain (PPN 1%) - 06 Penyerahan Lainnya (Turis Asing) -" +" 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam) -" +" 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu) - 09 " +"Penyerahan Aktiva (Pasal 16D UU PPN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:103 +msgid "" +"Correct an invoice that has been posted and downloaded: Replace Invoice " +"feature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:105 +msgid "" +"Cancel the original wrong invoice in Odoo. For instance, we will change the " +"Kode Transakski from 01 to 03 for the INV/2020/0001." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:107 +msgid "" +"Create a new invoice and set the canceled invoice in the *Replace Invoice* " +"field. In this field, we can only select invoices in *Cancel* state from the" +" same customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:109 +msgid "" +"As you validate, Odoo will automatically use the same e-Faktur serial number" +" as the canceled and replaced invoice replacing the third digit of the " +"original serial number with *1* (as requested to upload a replacement " +"invoice in the e-Faktur app)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:120 +msgid "" +"Correct an invoice that has been posted but not downloaded yet: Reset " +"e-Faktur" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:122 +msgid "Reset the invoice to draft and cancel it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:123 +msgid "Click on the button *Reset e-Faktur* on the invoice form view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:124 +msgid "" +"The serial number will be unassigned, and we will be able to reset the " +"invoice to draft, edit it and re-assign a new serial number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:3 +msgid "Italy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Italian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:20 +msgid "Italy - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:21 +msgid "`l10n_it`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:23 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:26 +msgid "Italy - E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:24 +msgid "`l10n_it_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:25 +msgid "e-invoice implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:27 +msgid "`l10n_it_edi_withholding`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:28 +msgid "e-invoice withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:29 +msgid "Italy - Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:30 +msgid "`l10n_it_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:31 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:25 +msgid "Country-specific reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:32 +msgid "Italy - Stock DDT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:33 +msgid "`l10n_it_stock_ddt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:34 +msgid "Transport documents - Documento di Trasporto (DDT)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:43 +msgid "" +"Configuring the company's information ensures your Accounting database is " +"properly set up. To add information, go to :menuselection:`Settings --> " +"General Settings`, and in the :guilabel:`Companies` section, click " +":guilabel:`Update info`. From here, fill out the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:47 +msgid ":guilabel:`Address`: the address of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:48 +msgid ":guilabel:`VAT`: VAT of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:49 +msgid ":guilabel:`Codice Fiscale`: the fiscal code of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:50 +msgid ":guilabel:`Tax System`: the tax system under which the company falls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Company information to provide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:57 +msgid "E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:59 +msgid "" +"The :abbr:`SdI (Sistema di Interscambio)` is the electronic invoicing system" +" used in Italy. It enables to send and receive electronic invoices to and " +"from customers. The documents must be in XML format and formally validated " +"by the system before being delivered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:63 +msgid "" +"To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di" +" Interscambio)` service must be notified that the user's files are to be " +"sent to **Odoo** and processed on their behalf. To so, you must set up " +"Odoo's :guilabel:`Codice Destinatario` on the **Agenzia Delle Entrate** " +"portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:68 +msgid "" +"Go to https://ivaservizi.agenziaentrate.gov.it/portale/ and authenticate;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:69 +msgid "Go to section :menuselection:`Fatture e Corrispettivi`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:70 +msgid "" +"Set the user as Legal Party for the VAT number you wish to configure the " +"electronic address;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:71 +msgid "" +"In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> " +"Registrazione dell’indirizzo telematico dove ricevere tutte le fatture " +"elettroniche`, insert Odoo's :guilabel:`Codice Destinatario` `K95IV18`, and " +"confirm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:76 +msgid "Electronic Data Interchange (EDI)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:78 +msgid "" +"Odoo uses the **FatturaPA** :abbr:`EDI (Electronic Data Interchange)` format" +" for the Italian localization and is enabled on the default journals when " +"installed. When the **file processing authorization** has been set, all " +"**invoices** and **bills** are automatically sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:83 +msgid "" +"You can :ref:`enable electronic invoicing for other sales and purchase " +"journals ` than the default ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:86 +msgid "" +"You can check the current status of an invoice by the :guilabel:`Electronic " +"invoicing` field. The XML file can be found in the **chatter** of the " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Electronic invoicing status (waiting for confirmation)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:97 +msgid "File processing authorization (Odoo)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:99 +msgid "" +"Since the files are transmitted through Odoo's server before being sent to " +"the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you " +"need to authorize Odoo to process your files from your database. To do so, " +"go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Electronic Document Invoicing`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:104 +msgid "There are **three** modes available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:108 +msgid ":guilabel:`Demo`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:107 +msgid "" +"This mode simulates an environment in which invoices are sent to the " +"government. In this mode, invoices need to be *manually* downloaded as XML " +"files and uploaded to the **Agenzia delle Entrate**'s website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:112 +msgid ":guilabel:`Test (experimental)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:111 +msgid "" +"This mode sends invoices to a non-production (i.e., test) service made " +"available by the **Agenzia delle Entrate**. Saving this change directs all " +"companies on the database to use this configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 +msgid ":guilabel:`Official`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 +msgid "" +"This is a production mode that sends your invoices directly to the **Agenzia" +" delle Entrate**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:117 +msgid "" +"Once a mode is selected, you need to accept the **terms and conditions** by " +"ticking :guilabel:`Allow Odoo to process invoices`, and then " +":guilabel:`Save`. You can now record your transactions in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:122 +msgid "" +"Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is " +"**irreversible**. Once in :guilabel:`Official` mode, it is not possible to " +"select :guilabel:`Test (experimental)` or :guilabel:`Demo`, and same for " +":guilabel:`Test (experimental)`. We recommend creating a separate database " +"for testing purposes only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:128 +msgid "" +"When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have " +"a partner using one of the following fake :guilabel:`Codice Destinatario` " +"given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. " +"Any real production :guilabel:`Codice Destinario` of your customers will not" +" be recognized as valid by the test service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italy's electronic document invoicing options" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:138 +msgid "Taxes configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:140 +msgid "" +"Many of the e-invoicing features are implemented using Odoo's tax system. As" +" such, it is very important that taxes are properly configured in order to " +"generate invoices correctly and handle other billing use cases. For example," +" specific configurations are required for the **reverse charge** type of " +"taxes. In case of a **reverse charge** tax, the seller does *not* charge the" +" customer for the VAT but, instead, the customer pays the VAT *themselves* " +"to their government. There are **two** main types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:147 +msgid ":ref:`external reverse charge `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:148 +msgid ":ref:`internal reverse charge `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:153 +msgid "External reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:156 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:387 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:212 +msgid "Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:158 +msgid "" +"To make an export invoice, make sure that the invoice lines all use a tax " +"configured for **reverse charge**. The **Italian** localization contains an " +"**example** of a reverse charge tax for export in the EU to be used as " +"reference (`0% EU`, invoice label `00eu`), which can be found under " +":menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt " +"from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has " +"exoneration of tax (Italy)` option ticked, with both the " +":guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "External reverse charge settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:170 +msgid "" +"If you need to use a different kind of :guilabel:`Exoneration`, click " +":menuselection:`Action --> Duplicate` within the tax menu to create a copy " +"of an existing similar tax. Then, select another :guilabel:`Exoneration`, " +"and :guilabel:`Save`. Repeat this process as many times as you need " +"different kind of :guilabel:`Exoneration` taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:176 +msgid "" +"**Rename** your taxes in the :guilabel:`Name` field according to their " +":guilabel:`Exoneration` to differentiate them easily." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:179 +msgid "" +"On your invoice, select the corresponding tax you need in the " +":guilabel:`Taxes` field. You can find the following **additional info** by " +"opening the **XML** file of the issued invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:182 +msgid "" +":guilabel:`SdI address (Codice Destinatario)`: must be filled for both " +"**EU** or **non-EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:183 +msgid "" +":guilabel:`Country Id`: must contain the country of the foreign seller in " +"the two-letter ISO (Alpha-2) code (ex., `IT` for 'Italy');" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:185 +msgid ":guilabel:`CAP`: must be filled with `00000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:186 +msgid "" +":guilabel:`Partita Iva` (**VAT number**): must contain the **VAT** number " +"for **EU businesses** and `OO99999999999` (double 'O' **letter**, not " +"'zero') for **non-EU businesses**. In case of private customers without " +"**VAT** number, use `0000000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:189 +msgid "" +":guilabel:`Fiscal Code`: for foreign entities without an actual **Codice " +"Fiscale**, any recognizable identifier is valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:193 +msgid "Odoo does not support sending user-modified XML files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:195 +msgid "" +"For **invoices**, multiple configurations are technically identified by a " +":guilabel:`Tipo Documento` code:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:198 +msgid "`TD02` - Down payments;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:199 +msgid "`TDO7` - Simplified invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:200 +msgid "`TD08` - Simplified credit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:201 +msgid "`TD09` - Simplified debit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:202 +msgid "`TD24` - Deferred invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:206 +msgid "`TD02`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:208 +msgid "Down payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:210 +msgid "" +"**Down payment** invoices are imported/exported with a different " +":guilabel:`Tipo Documento` code `TDO2` than regular invoices. Upon import of" +" the invoice, it creates a regular vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:214 +msgid "Odoo exports moves as `TD02` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:216 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:274 +msgid "Is an invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:217 +msgid "" +"All invoice lines are related to **sales order lines** that have the flag " +"`is_downpayment` set as `True`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:220 +msgid "`TD07`, `TD08`, and `TD09`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:222 +msgid "Simplified invoices, and credit/debit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:224 +msgid "" +"Simplified invoices and credit notes can be used to certify **domestic " +"transactions** under **400 EUR** (VAT included). Its status is the same as a" +" regular invoice, but with fewer information requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:228 +msgid "For a **simplified** invoice to be established, it must include:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:230 +msgid "" +":guilabel:`Customer Invoice` reference: **unique** numbering sequence with " +"**no gaps**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:231 +msgid ":guilabel:`Invoice Date`: issue **date** of the invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:232 +msgid "" +":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number," +" name, full address) under :menuselection:`General Settings --> Companies " +"(section)`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:234 +msgid "" +":guilabel:`VAT`: the **buyer**'s VAT/TIN number (on their profile card);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:235 +msgid ":guilabel:`Total`: the total **amount** (VAT included) of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:237 +msgid "" +"In the :abbr:`EDI (Electronic Data Interchange)`, Odoo exports invoices as " +"simplified if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:239 +msgid "It is a **domestic** transaction (i.e., the partner is from Italy);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:240 +msgid "The buyer's data is **insufficient** for a regular invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:241 +msgid "" +"The **required fields** for a regular invoice (address, ZIP code, city, " +"country) are provided;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:243 +msgid "The total amount VAT included is **less** than **400 EUR**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:246 +msgid "" +"The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in " +"the Gazzetta Ufficiale " +"`_. We " +"advise you to check the current official value." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:250 +msgid "`TD24`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:252 +msgid "Deferred invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:254 +msgid "" +"The **deferred invoice** is an invoice that is **issued at a later time** " +"than the sale of goods or the provision of services. A **deferred invoice** " +"has to be issued at the latest within the **15th day** of the month " +"following the delivery covered by the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:258 +msgid "" +"It usually is a **summary invoice** containing a list of multiple sales of " +"goods or services, carried out in the month. The business is allowed to " +"**group** the sales into **one invoice**, generally issued at the **end of " +"the month** for accounting purposes. Deferred invoices are default for " +"**wholesaler** having recurrent clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:263 +msgid "" +"If the goods are transported by a **carrier**, every delivery has an " +"associated **Documento di Transporto (DDT)**, or **Transport Document**. The" +" deferred invoice **must** indicate the details of all the **DDTs** " +"information for better tracing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:268 +msgid "" +"E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` " +":ref:`module `. In this case, a dedicated :guilabel:`Tipo " +"Documento` `TD24` is used in the e-invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:272 +msgid "Odoo exports moves as `TD24` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:275 +msgid "" +"Is associated to deliveries whose **DDTs** have a **different** date than " +"the issuance date of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:281 +msgid "" +"Italian companies buying goods or services from EU countries (or services " +"from non-EU countries) must send the information contained within the bill " +"received to the **Agenzia delle Entrate**. This allows you to complete tax-" +"related information on your bill, and to send it. The seller must be set as " +":guilabel:`Cedente/Prestatore`, and the buyer as " +":guilabel:`Cessionario/Committente`. Contained within the **XML** document " +"for the vendor bill, the vendor's credentials show as " +":guilabel:`Cedente/Prestatore`, and your company's credentials as " +":guilabel:`Cessionario/Committente`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:290 +msgid "" +"Self-billing invoices or VAT invoice integrations must be issued and sent to" +" the tax agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:292 +msgid "" +"When inputting taxes in a vendor bill, it is possible to select **reverse " +"charge** taxes. These are automatically activated in the Italian fiscal " +"position. By going to :menuselection:`Accounting --> Configuration --> " +"Taxes`, the `10%` and `22%` :guilabel:`Goods` and :guilabel:`Services` tax " +"scopes are activated and preconfigured with the correct tax grids. These are" +" set up automatically to ensure the correct booking of accounting entries " +"and display of the tax report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:298 +msgid "" +"For **vendor bills**, **three** types of configurations are technically " +"identified by a code called :guilabel:`Tipo Documento`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:301 +msgid "`TD17` - Buying services from **EU** and **non-EU** countries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:302 +msgid "`TD18` - Buying **goods** from **EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:303 +msgid "" +"`TD19` - Buying **goods** from a **foreign** vendor, but the **goods** are " +"already in **Italy** in a **VAT deposit**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:308 +msgid "`TD17`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:310 +msgid "Buying **services** from **EU** and **non-EU** countries:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:312 +msgid "" +"The foreign *seller* invoices a service with a **VAT-excluded** price, as it" +" is not taxable in Italy. The VAT is paid by the *buyer* in Italy;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:315 +msgid "" +"Within EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:317 +msgid "" +"Non-EU: the *buyer* sends themselves an invoice (i.e., **self-billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:319 +msgid "" +"Odoo exports a transaction as `TD17` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:321 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:335 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:351 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:411 +msgid "Is a vendor bill;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:322 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:336 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:412 +msgid "" +"At least one tax on the invoice lines targets the tax grids :ref:`VJ " +"`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:323 +msgid "" +"All invoice lines either have :guilabel:`Services` as **products**, or a tax" +" with the :guilabel:`Services` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:326 +msgid "`TD18`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:328 +msgid "Buying **goods** from **EU**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:330 +msgid "" +"Invoices issued within the EU follow a **standard format**, therefore only " +"an integration of the existing invoice is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:333 +msgid "" +"Odoo exports a transaction as `TD18` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:337 +msgid "" +"All invoice lines either have :guilabel:`Consumable` as **products**, or a " +"tax with the :guilabel:`Goods` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:340 +msgid "`TD19`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:342 +msgid "" +"Buying **goods** from a **foreign** vendor, but the **goods** are already in" +" **Italy** in a **VAT deposit**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:345 +msgid "" +"From EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:347 +msgid "" +"Non-EU: the *buyer* sends an invoice to *themselves* (i.e., **self-" +"billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:349 +msgid "Odoo exports a move as a `TD19` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:352 +msgid "" +"At least one tax on the invoice lines targets the tax grid :ref:`VJ3 " +"`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:353 +msgid "" +"All invoice lines either have :guilabel:`Consumable` products, or a tax with" +" :guilabel:`Goods` as tax scope." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:357 +msgid "" +"Odoo does not offer the `Conservazione Sostitutiva " +"`_ " +"requirements. Other providers and **Agenzia delle Entrate** supply free and " +"certified storage to meet the requested conditions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:365 +msgid "Internal reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:368 +msgid "" +"Odoo currently does not support domestic **internal reverse charge** " +"processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:373 +msgid "'Reverse Charge' tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:375 +msgid "" +"The Italian localization has a specific **tax grid** section for **reverse " +"charge** taxes. These tax grids are identifiable by the :ref:`VJ " +"` tag, and can be found under :menuselection:`Accounting --> " +"Reporting --> Audit Reports: Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian reverse charge tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:384 +msgid "San Marino" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:389 +msgid "" +"San Marino and Italy have special agreements on e-invoicing operations. As " +"such, **invoices** follow the regular **reverse charge** rules. Additional " +"requirements are not enforced by Odoo, however, the user is requested by the" +" **State** to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:393 +msgid "" +"Select a tax with the option :guilabel:`Has exoneration of tax (Italy)` " +"ticked, and the :guilabel:`Exoneration` set to `N3.3`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:395 +msgid "" +"Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice " +"Destinatario` `2R4GT08`. The invoice is then routed by a dedicated office in" +" San Marino to the correct business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:399 +msgid "Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:401 +msgid "" +"When a **paper bill** is received from San Marino, any Italian company " +"**must** submit that invoice to the **Agenzia delle Entrate** by indicating " +"the e-invoice's :guilabel:`Tipo Documento` field with the special value " +"`TD28`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:407 +msgid "`TD28`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:409 +msgid "Odoo exports a move as `TD28` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:413 +msgid "The **country** of the partner is **San Marino**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:416 +msgid "Pubblica amministrazione (B2G)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:419 +msgid "" +"Odoo does **not** send invoices directly to the government as they need to " +"be signed. If we see that the codice destinatario is 6 digits, then it is " +"not sent to the PA automatically, but you can download the XML, sign it with" +" an external program and send it through the portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:424 +msgid "Digital qualified signature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:426 +msgid "" +"For invoices and bills intended to the **Pubblica Amministrazione (B2G)**, a" +" **Digital Qualified Signature** is required for all files sent through the " +":abbr:`SdI (Sistema di Interscambio)`. The **XML** file must be certified " +"using a certificate that is either:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:430 +msgid "a **smart card**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:431 +msgid "a **USB token**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:432 +msgid "a **Hardware Security Module (HSM)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:435 +msgid "CIG, CUP, DatiOrdineAcquisto" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:437 +msgid "" +"To ensure the effective traceability of payments by public administrations, " +"electronic invoices issued to the public administrations must contain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:440 +msgid "" +"The :abbr:`CIG (Codice Identificativo Gara)`, except in cases of exclusion " +"from traceability obligations provided by law n. 136 of August 13, 2010;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:442 +msgid "" +"The :abbr:`CUP (Codice Unico di Progetto)`, in case of invoices related to " +"public works." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:444 +msgid "" +"If the **XML** file requires it, the **Agenzia Delle Entrate** can *only* " +"proceed payments of electronic invoices when the **XML** file contains a " +":abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di " +"Progetto)`. For each electronic invoice, it is **necessary** to indicate the" +" :abbr:`CUU (Codice Univoco Ufficio)`, which represents the unique " +"identifier code that allows the :abbr:`SdI (Sistema di Interscambio)` to " +"correctly deliver the electronic invoice to the recipient office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:452 +msgid "" +"The :abbr:`Codice Unico di Progetto)` and the :abbr:`CIG (Codice " +"Identificativo Gara)` must be included in one of the **2.1.2** " +"(DatiOrdineAcquisto), **2.1.3** (Dati Contratto), **2.1.4** " +"(DatiConvenzione), **2.1.5** (Date Ricezione), or **2.1.6** (Dati Fatture " +"Collegate) information blocks. These correspond to the elements named " +":guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice " +"**XML** file, whose table can be found on the government `website " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:458 +msgid "" +"The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic " +"invoice corresponding to the element **1.1.4** " +"(:guilabel:`CodiceDestinario`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:3 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Kenyan localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:19 +msgid ":guilabel:`Kenyan - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:20 +msgid "`l10n_ke`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:21 +msgid "" +"Installing this module grants you access to the list of accounts used in the" +" local GAAP and the list of common taxes (VAT, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:23 +msgid ":guilabel:`Kenyan - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:24 +msgid "`l10n_ke_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:25 +msgid "" +"Installing this module grants you access to improved accounting reports for " +"Kenya, such as Profit and Loss and Balance Sheets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:28 +msgid "" +"You also have to install the **Kenya Tremol Device EDI Integration** package" +" to be able to report your taxes to the **Kenya Revenue Authority (KRA)** " +"using the Tremol G03 Control Unit:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:37 +msgid ":guilabel:`Kenya Tremol Device EDI Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:38 +msgid "`l10n_ke_edi_tremol`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:39 +msgid "" +"Installing this module integrates with the Kenyan G03 Tremol control unit " +"device to report taxes to KRA through TIMS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "The three modules for the Kenya Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:47 +msgid "Kenyan TIMS integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:49 +msgid "" +"The Kenya Revenue Authority (KRA) has decided to go digital for tax " +"collection through the **Tax Invoice Management System (TIMS)**. As of " +"December 1st, 2022, all VAT-registered persons should comply with TIMS. The " +"goal is to reduce VAT fraud, increase tax revenue, and increase VAT " +"compliance through standardization, validation, and transmission of invoices" +" to KRA on a real-time or near real-time basis." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:55 +msgid "" +"All VAT-registered taxpayers should use a **compliant tax register**. Odoo " +"decided to develop the integration of the **Tremol G03 Control Unit (type " +"C)**, which can be run locally through USB. This device validates invoices " +"to ensure financial documents meet the new regulations and send the " +"validated tax invoices directly to KRA. Installing a proxy server that " +"provides a gateway between users and the internet is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:62 +msgid "Installing the proxy server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:64 +msgid "" +"Go to `odoo.com/download `_, fill out " +"the required information and click :guilabel:`Download`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Install the Proxy Server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:71 +msgid "" +"Once it is loaded on your computer, a wizard opens. You have to read and " +"agree with the terms of the agreement. On the next page, select the " +":guilabel:`type of install: Odoo IoT`. Then, click :guilabel:`Next` and " +":guilabel:`Install`. Once completed, click :guilabel:`Next`. Check the " +":guilabel:`Start Odoo` box to be redirected to Odoo automatically, and then " +"click :guilabel:`Finish`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 +msgid "" +"A new page opens, confirming your :doc:`IoT Box " +"<../../productivity/iot/config/connect>` is up and running. Connect your " +"physical device **Tremol G03 Control Unit (type C)** to your laptop via USB." +" In the :guilabel:`IoT Device` section, check that your Tremol G03 Control " +"Unit (type C) appears, confirming the connection between the device and your" +" computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Your IoT box is up and running" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:86 +msgid "" +"If the device is not detected, try to plug it in again or click on the " +":guilabel:`Restart` button in the top right corner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 +msgid "" +":doc:`Connect an IoT box to your database " +"<../../productivity/iot/config/connect>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 +msgid "Sending the data to KRA using the Tremol G03 Control Unit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:95 +msgid "" +"As a pre-requisite, check out that the :ref:`Kenyan Accounting modules " +"` are installed on your database. Then, go" +" to :menuselection:`Accounting --> Configuration --> Settings --> Kenya TIMS" +" Integration section`, and check that the :guilabel:`control Unit Proxy " +"Address` matches the address of the IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:100 +msgid "" +"To send data to KRA, create a new invoice by going to " +":menuselection:`Accounting Dashboard --> Customer Invoice card` and clicking" +" :guilabel:`New Invoice`. Upon confirmation of a new invoice, the " +":guilabel:`Send invoice to Fiscal Device` button appears. Clicking on it " +"sends the invoice details to the device and from the device to the " +"government. The :guilabel:`CU Invoice Number` field is now completed in your" +" invoice, confirming the information has been sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:106 +msgid "" +"The :guilabel:`Tremol G03 Fiscal Device` tab contains fields that are " +"automatically completed once the invoice is sent to the government:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:109 +msgid "" +":guilabel:`CU QR Code`: Url from the KRA portal which reflects a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:110 +msgid "" +":guilabel:`CU Serial Number`: reflects the serial number of the device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:111 +msgid "" +":guilabel:`CU Signing Date and Time`: The date and time when the invoice has" +" been sent to KRA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:113 +msgid "" +"If you click on :guilabel:`Send and Print`, a .pdf of the invoice is " +"generated. The :guilabel:`Kenyan Fiscal Device Info` is mentioned on the " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:117 +msgid "" +"To verify KRA has received the invoice information, take the :guilabel:`CU " +"Invoice Number` and enter it in the :guilabel:`Invoice Number Checker` " +"section on `Kenya Revenue Authority website `_. Click :guilabel:`Validate` and find the invoice details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:3 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:8 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Luxembourgish localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:17 +msgid ":guilabel:`Luxembourg - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:18 +msgid "`l10n_lu`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:20 +msgid ":guilabel:`Luxembourg - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:21 +msgid "`l10n_lu_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:23 +msgid ":guilabel:`Luxembourg - Annual VAT Report`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:24 +msgid "`l10n_lu_reports_annual_vat`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"The three modules for the Luxembourgish Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:32 +msgid "" +"Installing the module :guilabel:`Luxembourg - Accounting Reports` installs " +"all three modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:36 +msgid "Standard Chart of Accounts - PCN 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:38 +msgid "" +"Odoo's :ref:`fiscal localization package ` " +"for Luxembourg includes the current **Standard Chart of Accounts (PCN " +"2020)**, effective since January 2020." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:42 +msgid "eCDF tax return" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:44 +msgid "" +"Tax returns in Luxembourg require a specific XML file to upload on the eCDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:46 +msgid "" +"To download it, go to :menuselection:`Accounting --> Report --> Audit " +"Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:51 +msgid "" +"`Platform for electronic gathering of financial data (eCDF) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:54 +msgid "Annual tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:56 +msgid "" +"You can generate an XML file to electronically file your annual tax report " +"with the tax office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:58 +msgid "" +"To do so, go to :menuselection:`Accounting --> Report --> Luxembourg --> " +"Annual Tax Report`, click on :guilabel:`Create`, then define the annual " +"period in the :guilabel:`Year` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:61 +msgid "" +"The **simplified annual declaration** is automatically generated. You can " +"manually add values in all the fields to get a **complete annual " +"declaration**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"Odoo Accounting (Luxembourg localization) generates an annual tax " +"declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:68 +msgid "" +"To help you complete it, you can use the information provided on the " +":guilabel:`Tax Report`. To do so, go to :menuselection:`Accounting --> " +"Report --> Audit Reports --> Tax Report`, then click on the :guilabel:`Tax " +"Report` dropdown menu and select the type of report you want to display." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "Dropdown menu to select the type of Tax Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:76 +msgid "Finally, click on :guilabel:`Export XML` to download the XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:79 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Annual VAT Report` " +"to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:82 +msgid "FAIA (SAF-T)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:84 +msgid "" +"**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured " +"file that facilitates the exchange of information between the taxpayers' " +"accounting system and the tax office. It is the Luxembourgish version of the" +" OECD-recommended SAF-T (Standard Audit File for Tax)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:88 +msgid "" +"Odoo can generate an XML file that contains all the content of an accounting" +" period according to the rules imposed by the Luxembourg tax authorities on " +"digital audit files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:92 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Accounting Reports`" +" to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:95 +msgid "Export FAIA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:97 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Audit Reports --> " +"General Ledger`, then click on :guilabel:`FAIA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:3 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 +msgid "" +"A video on the Mexican localization is also available. This video covers how" +" to implement this localization from scratch, including how to set up the " +"configurations, how to complete common workflows, and provides an in-depth " +"look at several specific use cases, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:24 +msgid "" +"`Video webinar of a complete demo " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:29 +msgid "" +"The Odoo Mexican localization modules allow for the signing of electronic " +"invoices, according to the specifications of the |SAT| for `version 4.0 of " +"the CFDI `_, " +"a legal requirement, as of January 1, 2022. These modules also add relevant " +"accounting reports (such as: the |DIOT|, enables foreign trade, and the " +"creation of delivery guides)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 +msgid "" +"In order to electronically sign any documents in Odoo, ensure the *Sign* " +"application is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 +msgid "Requirements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:45 +msgid "" +"It is necessary to meet the following requirements before configuring the " +"Mexican localization modules in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:50 +msgid "Be registered in the |SAT|, with a valid |RFC|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 +msgid "" +"Have a `Certificate of Digital Seal `_ (CSD)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:53 +msgid "" +"Choose a PAC (Proveedor Autorizado de Certificación / Authorized " +"Certification Provider). Currently, Odoo works with the following |PAC|\\s: " +"`Solución Factible `_, `Quadrum (formerly " +"Finkok) `_ and `SW Sapien - Smarter Web " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 +msgid "" +"Have knowledge and experience with billing, sales, and accounting in Odoo. " +"This documentation **only** contains the necessary information needed to use" +" Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:61 +msgid "Installing modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:63 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Mexican localization. The :doc:`Accounting <../accounting>` " +"and *Contacts* modules are required to be installed for this configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:74 +msgid ":guilabel:`Mexico - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 +msgid "`l10n_mx`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +msgid "" +"The default :doc:`fiscal localization package <../fiscal_localizations>`, " +"adds accounting characteristics for the Mexican localization, such as: the " +"most common taxes and the chart of accounts – based on `the SAT account " +"grouping code " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:80 +msgid ":guilabel:`EDI for Mexico`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 +msgid "`l10n_mx_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +msgid "" +"Includes all the technical and functional requirements to generate and " +"validate :doc:`Electronics Documents " +"<../accounting/customer_invoices/electronic_invoicing>` — based on the " +"technical documentation published by the |SAT|. This allows you to send " +"invoices (with or without addedums) and payment complements to the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:86 +msgid ":guilabel:`EDI v4.0 for Mexico`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 +msgid "`l10n_mx_edi_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:88 +msgid "" +"Necessary to create XML documents with the correct specifications of the " +"CFDI 4.0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:89 +msgid ":guilabel:`Odoo Mexican Localization Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:90 +msgid "`l10n_mx_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 +msgid "" +"Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial " +"Balance, and |DIOT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:93 +msgid ":guilabel:`Mexico - Localization Reports for Closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:94 +msgid "`l10n_mx_reports_closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 +msgid "" +"Necessary to create the Closing Entry (Also known as the *month 13th move*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:96 +msgid ":guilabel:`Odoo Mexican XML Polizas Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 +msgid "`l10n_mx_xml_polizas`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 +msgid "" +"Allows the export of XML files of Journal Entries for a compulsory audit." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 +msgid ":guilabel:`Odoo Mexican XML Polizas Export Edi bridge`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 +msgid "`l10n_mx_xml_polizas_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 +msgid "Complements the module `l10n_mx_xml_polizas`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:104 +msgid "" +"When installing a database from scratch and selecting :guilabel:`Mexico` as " +"the country, Odoo automatically installs the following modules: " +":guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and " +":guilabel:`EDI v4.0 for Mexico`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +msgid "" +"The following modules are optional. It's recommended to install them *only* " +"if meeting a specific requirement. Make sure that they are needed for the " +"business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:118 +msgid ":guilabel:`EDI for Mexico (Advanced Features)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:119 +msgid "`l10n_mx_edi_extended`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:120 +msgid "" +"Adds the external trade complement to invoices: A legal requirement for " +"selling products to foreign countries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 +msgid ":guilabel:`EDI v4.0 for Mexico (COMEX)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 +msgid "`l10n_mx_edi_extended_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 +msgid "Adapts the module `l10n_mx_edi_extended` for CFDI 4.0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 +msgid ":guilabel:`Mexico - Electronic Delivery Guide`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 +msgid "`l10n_mx_edi_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +msgid "" +"Lets you create a *Carta Porte*: A bill of lading that proves to the " +"government you are sending goods between A & B with a signed electronic " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 +msgid ":guilabel:`Electronic Delivery Guide for Mexico CFDI 4.0`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 +msgid "`l10n_mx_edi_stock_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 +msgid "Adapts the module `l10n_mx_edi_stock` for CFDI 4.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 +msgid ":guilabel:`Odoo Mexico Localization for Stock/Landing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 +msgid "`l10n_mx_edi_landing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 +msgid "" +"Allows managing customs numbers related to landed costs in electronic " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +msgid "" +"After installing the correct modules, the next step is to verify that your " +"company is configured with the correct data. To do so, go to " +":menuselection:`Settings --> General Settings --> Companies`, and select " +":guilabel:`Update Info` under your company name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:143 +msgid "" +"Enter the full :guilabel:`Address` in the resulting form, including: " +":guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| " +"(:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:146 +msgid "" +"According to the requirements of the CFDI 4.0, the name of the main company " +"contact **must** coincide with your business name registered in the |SAT|, " +"without the legal entity abbreviation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Main company contact requirements for a correct invoicing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:154 +msgid "" +"From a legal point of view, a Mexican company **must** use the local " +"currency (MXN). Therefore, Odoo does not provide features to manage an " +"alternative configuration. If you want to manage another currency, let MXN " +"be the default currency and use a :doc:`pricelist " +"<../../sales/sales/products_prices/prices/pricing>`, instead." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:159 +msgid "" +"Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing" +" (MX) --> Fiscal Regime`, then select the regime that applies to your " +"company from the drop-down list, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Fiscal regime configuration in the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:168 +msgid "" +"If you want to test the Mexican localization, the company can be configured " +"with a real address within Mexico (including all fields), and add " +"`EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the " +":guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use " +":guilabel:`General de Ley Personas Morales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:176 +msgid "" +"To create a contact that can be invoiced, go to :menuselection:`Contacts -->" +" Create`. Then, enter the contact name, full :guilabel:`Address` including: " +":guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| " +"(:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 +msgid "" +"As with your own company, all of your contacts needs to have their correct " +"business name registered in the |SAT|. This also applies to the " +":guilabel:`Fiscal Regime`, which needs to be added in the :guilabel:`MX EDI`" +" tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:188 +msgid "" +"Some additional configurations for factor type and tax objects need to be " +"added to the sales taxes in order to properly sign invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +msgid "Factor type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:194 +msgid "" +"The *Factor Type* field is pre-loaded in the default taxes. If new taxes are" +" created, you need to make sure to configure this field. To do so, go to " +":menuselection:`Accounting --> Configuration --> Taxes`, then enable the " +":guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for " +"all records, with the :guilabel:`Tax Type` set as :guilabel:`Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Factor Type Sales tax type configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:204 +msgid "" +"Mexico manages two different kinds of 0% VAT to accommodate two scenarios:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:206 +msgid "*0% VAT* set the :guilabel:`Factor Type` as :guilabel:`Tasa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 +msgid "*VAT Exempt* set the :guilabel:`Factor Type` as :guilabel:`Exento`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:210 +msgid "Tax object" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:212 +msgid "" +"One requirement of the CFDI 4.0 is that the resulting XML file needs (or " +"does not need) to break down the taxes of the operation. There are three " +"different possible values that are added in the XML file:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 +msgid "" +"`01`: Not subject to tax - this value is added automatically if your invoice" +" line doesn't contain any taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:218 +msgid "" +"`02`: Subject to tax - this is the default configuration of any invoice line" +" that contains taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:219 +msgid "" +"`03`: Subject to tax and not forced to break down - this value can be " +"triggered on-demand for certain customers to replace the value 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:222 +msgid "" +"To use the `03` value, navigate to :menuselection:`Contacts --> your " +"customer's invoice --> MX EDI tab`, and activate the :guilabel:`No Tax " +"Breakdown` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "No Tax Breakdown option on the MX EDI tab of the customer's invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 +msgid "" +"The :guilabel:`No Tax Breakdown` value applies **only** to specific fiscal " +"regimes and/or taxes. Consult your accountant first to see if it is needed " +"for your business before making any modification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:235 +msgid "Other tax configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:237 +msgid "" +"When registering a payment, Odoo will carry out the movement of taxes from " +"the *Cash Basis Transition Account* to the account set in the " +":guilabel:`Definition` tab. For such movement, a tax base account will be " +"used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the " +"journal entry when reclassifying taxes. **Do not delete this account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 +msgid "" +"If you create a new tax in :menuselection:`Accounting --> Configuration --> " +"Taxes`, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, " +"`ISR` or `IEPS`). Odoo **only** supports these three groups of taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Tax accounts available for Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 +msgid "" +"To configure products, go to :menuselection:`Accounting --> Customers --> " +"Products`, then select a product to configure, or :guilabel:`Create` a new " +"one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product" +" Category` field, select the category that represents the product. The " +"process can be done manually, or through :doc:`a bulk import " +"<../../general/export_import_data>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:259 +msgid "" +"All products need to have an |SAT| code associated with them in order to " +"prevent validation errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:266 +msgid "PAC credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:268 +msgid "" +"After you have processed your `Private Key (CSD) " +"`_ with the |SAT|, you **must** register " +"directly with the :ref:`PAC ` of your choice before you " +"start creating invoices from Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 +msgid "" +"Once you've created your account with any of these providers, go to " +":menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. " +"Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your" +" credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Configuring PAC credentials from the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 +msgid "" +"If you do not have credentials, but want to test the electronic invoicing, " +"you can activate the :guilabel:`MX PAC test environment` checkbox, and " +"select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a " +"username or password for a test environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:287 +msgid ".cer and .key certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:289 +msgid "" +"The `digital certificates of the company " +"`_ " +"must be uploaded within the :guilabel:`MX Certificates` section. To do so, " +"navigate to :menuselection:`Settings --> Accounting --> Electronic Invoicing" +" (MX)`. Under the :guilabel:`MX Certificates` section, select :guilabel:`Add" +" a line`, and a window will open. Click :guilabel:`Create`, and from there, " +"upload your digital :guilabel:`Certificate` (:file:`.cer` file), your " +":guilabel:`Certificate Key` (:file:`.key` file), and your " +":guilabel:`Certificate Password`. To finish, click on :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Certificate and key upload inputs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +msgid "" +"If you still do not have one of the contracted |PAC|\\s and you want to test" +" electronic invoicing, you can use the following |SAT| test certificates:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 +msgid ":download:`Certificate `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:307 +msgid ":download:`Certificate Key `" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 +msgid "**Password**: ``12345678a``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:316 +msgid "" +"The invoicing process in Odoo is based on `Annex 20 " +"`_ version" +" 4.0 of electronic invoicing of the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:323 +msgid "" +"To start invoicing from Odoo, a customer invoice must be created using the " +":doc:`standard invoicing flow <../accounting/customer_invoices>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:326 +msgid "" +"While the document is in draft mode, changes can be made to it (the correct " +":guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require" +" can be added, for example.)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 +msgid "" +"After you :guilabel:`Confirm` the customer invoice, a blue message appears " +"stating: :guilabel:`The invoice will be processed asynchronously by the " +"following E-invoicing service: CFDI (4.0)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:332 +msgid "" +"Pressing the :guilabel:`Process Now` button sends the document to the " +"government so it can be signed. After receiving the signed document back " +"from the government, the :guilabel:`Fiscal Folio` field appears on the " +"document, and the XML file is attached in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 +msgid "" +"If you click :guilabel:`Retry` in the :guilabel:`SAT status` field on the " +"invoice, you can confirm if the XML file is valid in the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:340 +msgid "" +"If you are in a testing environment, you will always receive the message " +":guilabel:`Not Found`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:342 +msgid "" +"To send the signed invoice to your client by mail, you can send both the XML" +" and PDF files together, directly from Odoo, by clicking the :guilabel:`Send" +" & Print` button. You can also download the PDF file to your computer, by " +"clicking the :guilabel:`Print` button, and selecting the desired print " +"option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 +msgid "" +"While an invoice is a document type \"I\" (Ingreso), a credit note is a " +"document type \"E\" (Egreso)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 +msgid "" +"The only addition to the :doc:`standard flow for credit notes " +"<../accounting/customer_invoices/credit_notes>` is that, as a requirement of" +" the |SAT|, there has to be a relation between a credit note and an invoice " +"through the fiscal folio." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:356 +msgid "" +"Because of this requirement, the field :guilabel:`CFDI Origin` adds this " +"relation with a `01|`, followed by the fiscal folio of the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example CFDI Origin number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:364 +msgid "" +"For the :guilabel:`CFDI Origin` field to be automatically added, use the " +":guilabel:`Add Credit Note` button from the invoice, instead of creating it " +"manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:368 +msgid "Payment complements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:373 +msgid "" +"One addition of the Mexican localization is the :guilabel:`Payment Policy` " +"field . `According to the SAT documentation " +"`_, there may be 2 types of payments:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 +msgid "`PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 +msgid "" +"`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or " +"Deferred)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:381 +msgid "" +":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:383 +msgid "" +"The difference lies in the *Due Date* or *Payment Terms* of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:385 +msgid "" +"To configure |PUE| invoices, navigatge to :menuselection:`Accounting --> " +"Customers --> Invoices`, and either select an invoice :guilabel:`Due Date` " +"within the same month, or choose a payment term that does not imply changing" +" the due month (immediate payment, 15 days, 21 days, all falling within the " +"current month)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example of an invoice with the PUE requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +msgid "" +"Some :guilabel:`Payment Terms` are already installed by default, and can be " +"managed from :menuselection:`Accounting --> Configuration --> Payment " +"Terms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 +msgid "" +"To configure |PPD| invoices, navigate to :menuselection:`Accounting --> " +"Customers --> Invoices`, and select an invoice with a :guilabel:`Due Date` " +"after the first day of the following month. This also applies if your " +":guilabel:`Payment Term` is due in the following month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example of an invoice with the PPD requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 +msgid "" +"Because the |PPD| policy implies that an invoice is not going to get paid at" +" the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is " +":guilabel:`99 - Por Definir` (To define)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:412 +msgid "Payment flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:414 +msgid "" +"In both cases, the payment process in Odoo :doc:`is the same " +"<../accounting/customer_invoices>`, the main difference being payments " +"related to |PPD| invoices trigger the creation of a document type \"P\" " +"(Pago)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:418 +msgid "" +"If a payment is related to a |PUE| invoice, it can be registered with the " +"wizard, and be associated with the corresponding invoice. To do so, navigate" +" to :menuselection:`Accounting --> Customers --> Invoices`, and select an " +"invoice. Then, click the :guilabel:`Register Payment` button. The invoice " +"status changes to :guilabel:`In Payment`, since the payment is effectively " +"validated when it is bank reconciled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:425 +msgid ":doc:`../accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 +msgid "" +"While this process is the same for PPD invoices, the addition of the " +"creating an :doc:`electronic document " +"<../accounting/customer_invoices/electronic_invoicing>` means some " +"additional requirements are needed to correctly send the document to the " +"|SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +msgid "" +"From an invoice, you need to confirm the specific :guilabel:`Payment Way` " +"where you received the payment. Because of this, the :guilabel:`Payment Way`" +" field **cannot** be set as `99 - Por Definir (To Define)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:435 +msgid "" +"If you are going to add a bank account number in the :guilabel:`Accounting` " +"tab of a customer's contact card, it must have a valid account number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:439 +msgid "" +"The exact configurations are in the `Anexo 20 of the SAT " +"`_. " +"Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for " +"transfers, 16 for credit or debit cards." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:443 +msgid "" +"If a payment is related to a signed invoice with the :guilabel:`Payment " +"Policy` `PPD`, Odoo generates the corresponding payment complement " +"automatically, once you click :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI (4.0) E-invoicing service process payment now message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:452 +msgid "" +"A payment in MXN **cannot** be used to pay multiple invoices in USD. " +"Instead, the payment should be separated into multiple payments, using the " +":guilabel:`Register Payment` button on the corresponding invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 +msgid "Invoice cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:459 +msgid "" +"It is possible to cancel the EDI documents sent to the |SAT|. According to " +"the `Reforma Fiscal 2022 `_, since January 1st, 2022, there are two " +"requirements for this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:463 +msgid "" +"With all cancellation requests, you **must** specify a *cancellation " +"reason*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:464 +msgid "" +"After 24 hours have passed since the creation of the invoice, the client " +"**must** be asked to accept the cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:467 +msgid "" +"There are four different cancellation reasons. In Odoo, you can cancel " +"invoices with the reasons *01 Invoices sent with errors with a relation*, " +"and *02 Invoices sent with errors without a relation*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:470 +msgid "" +"The following sections break down the process of canceling invoices for each" +" cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:474 +msgid "" +"Odoo has certain limitations to canceling invoices in the |SAT|: The reasons" +" 03 and 04 (*Operation did not take place* and *Nominative transactions " +"related to a global invoice*, respectively) are not currently supported by " +"Odoo. For this, you need to cancel the invoice directly in the |SAT|, and " +"press :guilabel:`Retry` in the :guilabel:`SAT Status field`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:480 +msgid "01 - invoices sent with errors with a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +msgid "" +"This cancellation reason must be used when a new invoice needs to substitute" +" the original one, due to an error in any field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 +msgid "" +"Begin by navigating to :menuselection:`Accounting --> Customers --> " +"Invoices`, and select the old invoice. Copy the :guilabel:`Fiscal Folio` " +"from the old invoice. Then, navigate to the new invoice, and in the " +":guilabel:`CFDI Origin` field, add the value `04|` and paste the " +":guilabel:`Fiscal Folio` of the old invoice after the value. Finally, sign " +"the new document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:490 +msgid "" +"Next, navigate back to the old invoice, and notice the " +":guilabel:`Substituted By` field is now available. Click the " +":guilabel:`Request EDI Cancellation` button on the old invoice, and then " +"click :guilabel:`Process Now` in the blue section that appears. The invoice " +"status changes to :guilabel:`Canceled`, and a confirmation is logged in the " +"chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:495 +msgid "" +"Now, the invoice should be canceled in the |SAT| as well. You can confirm " +"this was done correctly, by pressing :guilabel:`Retry` in the |SAT| status " +"field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 +msgid "" +"If the document was canceled more than 24 hours after its creation, you may " +"need to ask the client to accept the cancellation in their “Buzón " +"Tributario” directly from the `SAT website `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:503 +msgid "" +"The `04|` is only a code that helps Odoo to perform this process. It has no " +"relation to the method 04 reason for cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Old invoice with CFDI Origin." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "" +"Invoice with the Substituted By field referencing the CFDI Origin invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 +msgid "02 - invoices sent with errors without a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 +msgid "" +"This cancellation reason has to be used when an invoice was sent with an " +"error in any field, and does not need to be replaced by another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:520 +msgid "" +"For this case, navigate to :menuselection:`Accounting --> Customers --> " +"Invoices`, and select the old invoice. From here, the only requirement is to" +" click the :guilabel:`Request EDI Cancellation` button, and then click the " +":guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:524 +msgid "" +"Because the field :guilabel:`Substituted By` does not appear when using this" +" cancellation reason, the |SAT| should automatically detect that the " +"cancellation reason is 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 +msgid "Payment cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:530 +msgid "" +"It is also possible to cancel *Payment Complements*. For this, go to the " +"payment, via :menuselection:`Accounting --> Customers --> Payments`, and " +"select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button" +" will appear. Click :guilabel:`Process now`, and the document will be sent " +"to the |SAT|. After a few seconds, you can click :guilabel:`Retry` to " +"confirm the current |SAT| status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:536 +msgid "Finally, the payment status is moved to :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:539 +msgid "" +"Just like invoices, when you create a new *Payment Complement*, you can add " +"the relation of the original document, by adding a `04|` plus the fiscal " +"folio in the :guilabel:`CFDI Origin` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:543 +msgid "Invoicing special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:546 +msgid "CFDI to public" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +msgid "" +"If the customer you are selling goods or services to does not require an " +"invoice, a *CFDI to Public* has to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:551 +msgid "" +"If you use the :guilabel:`Customer` name `PUBLICO EN GENERAL`, an error will" +" be triggered. This is a main change in the CFDI 4.0 that requires invoices " +"with that specific name to need additional fields, which Odoo does not " +"currently support. So, for a *CFDI to Public* to be created, you need to add" +" any name to your customer that is **not** `PUBLICO EN GENERAL`. (For " +"example: `CLIENTE FINAL`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:556 +msgid "" +"In addition to this, it is required that the :guilabel:`ZIP` code of your " +"company is added, the generic |RFC| is set as `XAXX010101000`, and the " +":guilabel:`Fiscal Regime` of your customer must be set as: `Sin obligaciones" +" fiscales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI to Public Customer field configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 +msgid "" +"The main currency in Mexico is MXN. While this is mandatory for all Mexican " +"companies, it is possible to send and receive invoices (and payments) in " +"different currencies. To enable the use of :doc:`multicurrency " +"<../accounting/get_started/multi_currency>`, navigate to the " +":menuselection:`Accounting --> Settings --> Currencies`, and set " +":guilabel:`Mexican Bank` as the :guilabel:`Service` in the " +":guilabel:`Automatic Currency Rates` section. Then, set the " +":guilabel:`Interval` field to the frequency you wish to update the exchange " +"rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:574 +msgid "" +"This way, the XML file of the document will have the correct exchange rate, " +"and the total amount, in both the foreign currency and in MXN." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:577 +msgid "" +"It is highly recommended to use :doc:`a bank account for each currency " +"<../accounting/bank/foreign_currency>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:581 +msgid "" +"The only currencies that automatically update their exchange rate daily are:" +" USD, EUR, GBP, and JPY." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Multi-currency configuration in the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 +msgid "Down payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:591 +msgid "" +"There can be cases where you receive a payment in advance from a customer " +"that needs to be applied to an invoice later. In order to do this in Odoo, " +"it is required to properly link invoices to each other with the " +":guilabel:`CFDI Origin` field. To do so, it is necessary to have the " +":doc:`Sales <../../sales>` app installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:597 +msgid "" +"`The official documentation for registration of down payments in Mexico " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 +msgid "" +"First, navigate to the :menuselection:`Sales` app to create a product " +"`Anticipo` and configure it. The :guilabel:`Product Type` must be " +":guilabel:`Service`, and use the :guilabel:`UNSPSC Category` must be: " +"`84111506 Servicios de facturación`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 +msgid "" +"Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down " +"Payments`, and add the *Anticipo* product as the default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 +msgid "" +"Create a sales order with the total amount, and create a down payment " +"(either using a percentage or fixed amount). Then, sign the document, and " +":guilabel:`Register the Payment`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:610 +msgid "" +"When the time comes for the customer to get the final invoice, create it " +"again from the same sales order. In the :guilabel:`Create Invoices` wizard, " +"select :guilabel:`Regular Invoice`, and uncheck :guilabel:`Deduct down " +"payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 +msgid "" +"Then, copy the :guilabel:`Fiscal Folio` from the first invoice, and paste it" +" into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix " +"`07|` before the value. Then, sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:618 +msgid "" +"After this, create a credit note for the first invoice. Copy the " +":guilabel:`Fiscal Folio` from the second invoice, and paste it in the " +":guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Then, " +"sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:622 +msgid "" +"With this, all electronic documents are linked to each other. The final step" +" is to fully pay the new invoice. At the bottom of the new invoice, you can " +"find the credit note in the :guilabel:`Outstanding credits` - add it as " +"payment. Finally, register the remaining amount with the :guilabel:`Register" +" Payment` wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 +msgid "External trade" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 +msgid "" +"The external trade is a complement to a regular invoice that adds certain " +"values in both the XML and PDF, to invoices with a foreign customer " +"according to `SAT regulations " +"`_," +" such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 +msgid "The specific address of the receiver and the sender" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 +msgid "" +"The addition of a :guilabel:`Tariff Fraction` that identifies the type of " +"product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +msgid "" +"The correct :guilabel:`Incoterm` (International Commercial Terms), among " +"others (*certificate of origin* and *special units of measure*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:639 +msgid "" +"This allows the correct identification of exporters and importers, in " +"addition to expanding the description of the merchandise sold." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:642 +msgid "" +"Since January 1, 2018, external trade is a requirement for taxpayers, who " +"carry export operations of type A1. While the current CFDI is 4.0, the " +"external trade is currently on version 1.1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:645 +msgid "" +"In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` " +"and :guilabel:`l10n_mx_edi_extended_40` have to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:649 +msgid "" +"Before installing, make sure your business needs to use this feature. " +"Consult your accountant first, if needed, before installing any modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:658 +msgid "" +"To configure your company contact for external trade, navigate to " +":menuselection:`Accounting --> Customers --> Customers`, and select your " +":guilabel:`Company`. While the CFDI 4.0 requirements ask you to add a valid " +":guilabel:`ZIP` code in your contact, the external trade complement adds the" +" requirement that your :guilabel:`City` and the :guilabel:`State` must also " +"be valid. All three fields must coincide with the `Official SAT Catalog " +"`_, or you will receive an error." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 +msgid "" +"Add the :guilabel:`City` and :guilabel:`State` in the company's *contact*, " +"not in the company itself. You can find your company's contact in " +":menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:669 +msgid "" +"The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and" +" can be added in the company directly in :menuselection:`Settings --> " +"General Settings --> Companies`. These two fields have to coincide with the " +"data in the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Optional external trade company fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +msgid "" +"To configure the contact data for a foreign receiving client, navigate to " +":menuselection:`Accounting --> Customers --> Customers`, and select the " +"foreign client's contact. The contact must have the following fields " +"completed to avoid errors:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:681 +msgid "" +"The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` " +"code and the foreign :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +msgid "" +"The format of the foreign :guilabel:`VAT` (tax identification number, for " +"example: Colombia `123456789-1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +msgid "" +"In the :guilabel:`MX EDI` tab, you need to address if the customer receives " +"goods for a period of time temporarily (:guilabel:`Temporary`) or " +"permanently (:guilabel:`Definitive`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:689 +msgid "" +"If the new contact was created by duplicating another existing contact from " +"Mexico, make sure to delete any carried over information from the " +":guilabel:`Fiscal Regime` field. In addition, do not enable the " +":guilabel:`No Tax Breakdown` option. Selecting this option hides mandatory " +"fields that are required for external trade contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Required external trade customer fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:699 +msgid "" +"In the resulting XML and PDF files, the :guilabel:`VAT` is automatically " +"replaced by the generic VAT for abroad transactions: `XEXX010101000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:705 +msgid "" +"All products involved with external trade have four fields that are " +"required, two of them exclusive to external trade." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:708 +msgid "" +"The :guilabel:`Internal Reference` of the product is in the " +":guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 +msgid "The :guilabel:`Weight` of the product must be more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 +msgid "" +"The `correct `_" +" :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` " +"tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:712 +msgid "" +"The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Required external trade product fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:719 +msgid "" +"If the UoM code of the :guilabel:`Tariff Fraction` is `01`, the correct " +":guilabel:`UMT Aduana` is `kg`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:721 +msgid "" +"If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct " +":guilabel:`UMT Aduana` is `Units`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 +msgid "Invoicing flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:727 +msgid "" +"Before creating an invoice, it is important to take into account that " +"external trade invoices require to convert the amounts of your product into " +"USD. Therefore, :doc:`multicurrency " +"<../accounting/get_started/multi_currency>` **must** be enabled and *USD* " +"**must** be activated in the :guilabel:`Currencies` section. The correct " +":guilabel:`Service` to run is :guilabel:`Mexican Bank`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:733 +msgid "" +"Then, with the correct exchange rate set up in :menuselection:`Accounting " +"--> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` " +"and the optional :guilabel:`Certificate Source` in the :guilabel:`Other " +"Info` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "External trade Other Info tab of a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 +msgid "" +"Finally, sign the invoice with the same process as a regular invoice, and " +"click the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:747 +msgid "" +"A `Carta Porte `_ is a bill of lading: a document that states the type, quantity, " +"and destination of goods being carried." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:750 +msgid "" +"On December 1st, 2021, version 2.0 of this CFDI was implemented for all " +"transportation providers, intermediaries, and owners of goods. Odoo is able " +"to generate a document type \"T\" (Traslado), which, unlike other documents," +" is created in a delivery order instead of an invoice or payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:754 +msgid "" +"Odoo can create XML and PDF files with (or without) ground transport, and " +"can process materials that are treated as *Dangerous Hazards*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:757 +msgid "" +"In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, " +":guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and " +":guilabel:`l10n_mx_edi_stock_40` have to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:761 +msgid "" +"In addition to this, it is necessary to have the :doc:`Inventory " +"<../../inventory_and_mrp/inventory>` and :doc:`Sales <../../sales/sales>` " +"apps installed, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 +msgid "" +"Odoo does not support Carta Porte type document type \"I\" (Ingreso), air, " +"or marine transport. Consult your accountant first if this feature is needed" +" before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 +msgid "Odoo manages two different types of CFDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 +msgid "" +"**No Federal Highways**: Is used when the *Distance to Destination* is `less" +" than 30 KM " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 +msgid "" +"**Federal Transport**: Is used when the *Distance to Destination* exceeds 30" +" KM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:777 +msgid "" +"Other than the standard requirements of regular invoicing (The |RFC| of the " +"customer, the UNSPSC code, etc.), if you are using *No Federal Highways*, no" +" external configuration is needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:780 +msgid "" +"For *Federal Transport*, several configurations have to be added to " +"contacts, vehicle setups, and products. Those configurations are added to " +"the XML and PDF files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 +msgid "Contacts and vehicles" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 +msgid "" +"Like the external trade feature, the :guilabel:`Address` in both the company" +" and the final customer must be complete. The :guilabel:`ZIP` code, " +":guilabel:`City`, and :guilabel:`State` must coincide with the `Official SAT" +" Catalog for Carta Porte _`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 +msgid "The field, :guilabel:`Locality`, is optional for both addresses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:798 +msgid "" +"The origin address used for the delivery guide is set in " +":menuselection:`Inventory --> Configuration --> Warehouses Management --> " +"Warehouses`. While this is set as the company address by default, you can " +"change it according to your correct warehouse address." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:802 +msgid "" +"Another addition to this feature is the :guilabel:`Vehicle Setups` menu " +"found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets " +"you add all the information related to the vehicle used for the delivery " +"order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:806 +msgid "All fields are mandatory to create a correct delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +msgid "" +"The fields, :guilabel:`Vehicle Plate Number` and :guilabel:`Number Plate`, " +"must contain between 5 to 7 characters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:812 +msgid "" +"In the :guilabel:`Intermediaries` section, you must add the operator of the " +"vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` " +"and :guilabel:`Operator Licence`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide vehicle configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 +msgid "" +"Similar to regular invoicing, all products must have a :guilabel:`UNSPSC " +"category`. In addition to this, there are two extra configurations for " +"products involved in delivery guides:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:825 +msgid "" +"The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for" +" stock movements to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 +msgid "" +"In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have " +"more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:830 +msgid "" +"Creating a delivery guide of a product with the value `0` will trigger an " +"error. As the :guilabel:`Weight` has been already stored in the delivery " +"order, it is needed to return the products, and create the delivery order " +"(and delivery guide) again with the correct amounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide product configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:839 +msgid "Sales and inventory flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:841 +msgid "" +"To create a delivery guide, first, you need to create and confirm a sales " +"order from :menuselection:`Sales --> Sales Order`. This generates a " +":guilabel:`Delivery` smart button. Click it, and :guilabel:`Validate` the " +"transfer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:845 +msgid "" +"After the status is set to :guilabel:`Done`, you can edit the transfer, and " +"select the :guilabel:`Transport Type` (either :guilabel:`No Federal " +"Highways` or :guilabel:`Federal Transport`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 +msgid "" +"If your delivery guide has the type :guilabel:`No Federal Highways`, you can" +" save the transfer, and then click :guilabel:`Generate Delivery Guide`. The " +"resulting XML can be found in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:853 +msgid "" +"Other than the :guilabel:`UNSPSC` in all products, delivery guides that use " +":guilabel:`No Federal Highways` do not require any special configuration to " +"be sent to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 +msgid "" +"If your delivery guide has the type, :guilabel:`Federal Transport`, the tab " +":guilabel:`MX EDI` appears. There, enter a value in :guilabel:`Distance to " +"Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` " +"used for this delivery." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide MX EDI tab configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +msgid "Dangerous hazards" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:867 +msgid "" +"Certain values in the :guilabel:`UNSPSC Category` are considered in the " +"`official SAT catalog " +"`_" +" as *dangerous hazards*. These categories need additional considerations " +"when creating a delivery guide with :guilabel:`Federal Transport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:872 +msgid "" +"First, select your product from :menuselection:`Inventory --> Products --> " +"Products`. Then, in the :guilabel:`Accounting` tab, the fields " +":guilabel:`Hazardous Material Designation Code (MX)` and " +":guilabel:`Hazardous Packaging (MX)` must be filled with the correct code " +"from the |SAT| catalog." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide hazardous material product required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 +msgid "" +"In :menuselection:`Inventory --> Settings --> Mexico --> Vehicle Setup`, the" +" data from the :guilabel:`Environment Insurer` and :guilabel:`Environment " +"Insurance Policy` has to be filed, as well. After this, continue with the " +"regular process to create a delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery Guide environment insurer required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:889 +msgid "Customs numbers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:891 +msgid "" +"A *customs declaration* (Pedimento Aduanero) is a fiscal document that " +"certifies that all contributions to the fiscal entity (the |SAT|) has been " +"paid for, including the import/export of goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 +msgid "" +"According to the `Annex 20 " +"`_ of CFDI" +" 4.0, in documents where the invoiced goods come from a first-hand import " +"operation, the field, :guilabel:`Customs Number`, needs to be added to all " +"lines of products involved with the operation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:899 +msgid "" +"To do so, the module :guilabel:`l10n_mx_edi_landing` must be installed, in " +"addition to the :doc:`Inventory <../../inventory_and_mrp/inventory>`, " +":doc:`Purchase <../../inventory_and_mrp/purchase>` and :doc:`Sales " +"<../../sales/sales>` apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 +msgid "" +"Do not confuse this feature with external trade. The customs numbers are " +"directly related to importing goods, while the external trade complement is " +"related to exporting. Consult your accountant first if this feature is " +"needed before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +msgid "" +"In order to track the correct customs number for a specific invoice, Odoo " +"uses :doc:`landed costs " +"<../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs>`." +" Go to :menuselection:`Inventory --> Configuration --> Settings --> " +"Valuation`. Make sure that :guilabel:`Landed Costs` is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +msgid "" +"Begin by creating a *service*-type product called, `Pedimento`. In the " +":guilabel:`Purchase` tab, activate :guilabel:`Is a Landed Cost`, and select " +"a :guilabel:`Default Split Method`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 +msgid "" +"Then, configure the *storable products* that hold the customs numbers. To do" +" so, create the storable products, and make sure the :guilabel:`Product " +"Category` has the following configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:922 +msgid "" +":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 +msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 +msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:925 +msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 +msgid "" +":guilabel:`Stock Input Account`: :guilabel:`115.05.01 Mercancías en " +"tránsito`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 +msgid "" +":guilabel:`Stock Output Account`: :guilabel:`115.05.01 Mercancías en " +"tránsito`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Storable products general configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Storable product category configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:938 +msgid "Purchase and sales flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:940 +msgid "" +"After you configure your product, follow the standard :doc:`purchase flow " +"<../../inventory_and_mrp/purchase>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 +msgid "" +"Create a purchase order from :menuselection:`Purchase --> Orders --> " +"Purchase Order`. Then, confirm the order to display a :guilabel:`Receipt` " +"smart button. Click on the :guilabel:`Receipt` smart button to " +":guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 +msgid "" +"Go to :menuselection:`Inventory --> Operations --> Landed Costs`, and create" +" a new record. Add the transfer that you just created, and both: the product" +" `Pedimento` and :guilabel:`Customs number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 +msgid "" +"Optionally, you can add a cost amount. After this, validate the landed cost." +" Once :guilabel:`Posted`, all products related to that receipt have the " +"customs number assigned." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:954 +msgid "" +"You can only add the *Pedimentos* number **once**, so be careful when " +"associating the correct number with the transfer(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Customs number on a landed costs Inventory record." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:961 +msgid "" +"Now, create a sales order, and confirm it. This should trigger a " +":guilabel:`Delivery` smart button. Validate it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:964 +msgid "" +"Finally, create an invoice from the sales order, and confirm it. The invoice" +" line related to your product has a customs number in it. This number should" +" match the customs number added in the *Landed Costs* record you created " +"earlier." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Customs number on confirmed sales order product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:973 +msgid "Electronic accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:975 +msgid "" +"For Mexico, `Electronic Accounting " +"`_ refers to the obligation to keep accounting records and " +"entries through electronic means, and to enter accounting information on a " +"monthly basis, through the |SAT| website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:980 +msgid "It consists of three main XML files:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:982 +msgid "" +"The updated list of the chart of accounts that you are currently using." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:983 +msgid "" +"A monthly trial balance, plus a closing entry report, also known as: *Trial " +"Balance Month 13*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:984 +msgid "" +"Either optional, or for a compulsory audit, an export of the journal entries" +" in your general ledger." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:987 +msgid "" +"The resulting XML files follow the requirements of the `Anexo Técnico de " +"Contabilidad Electrónica 1.3 " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:990 +msgid "" +"In addition to this, you can generate the `DIOT " +"`_: A report of vendor's " +"journal entries that involve IVA taxes that can be exported in a " +":file:`.txt` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:995 +msgid "" +"In order to use these reports, the modules :guilabel:`l10n_mx_reports`, " +":guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and " +":guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the " +":doc:`Accounting <../accounting/get_started>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1000 +msgid "" +"You can find the *Chart of accounts*, *Trial Balance Month 13*, and *DIOT* " +"reports in :menuselection:`Accounting --> Reporting --> Mexico`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1004 +msgid "" +"The specific characteristics and obligations of the reports that you send " +"might change according to your fiscal regime. Always contact your accountant" +" before sending any documents to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1013 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"in México follows a specific pattern based on |SAT|'s' `Código agrupador de " +"cuentas " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1017 +msgid "" +"You can create any account, as long as it respects |SAT|'s encoding group: " +"the pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1021 +msgid "Some examples are `102.01.99` or `401.01.001`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1023 +msgid "" +"When a new account is created in :menuselection:`Accounting --> " +"Configuration --> Chart of Accounts`, with the |SAT| encoding group pattern," +" the correct grouping code appears in :guilabel:`Tags`, and your account " +"appears in the *COA* report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1027 +msgid "" +"Once you create all your accounts, make sure the correct :guilabel:`Tags` " +"are added." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +msgid "" +"You cannot use any pattern that ends a section with a 0 (such as " +"`100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the " +"report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +msgid "" +"Once everything is set up, you can go to :menuselection:`Accounting --> " +"Reporting --> Mexico --> COA`, and click the :guilabel:`SAT (XML)` button to" +" generate an XML file containing all of your accounts, which will be ready " +"to upload to the |SAT| website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 +msgid "" +"The trial balance reports the initial balance, credit, and total balance of " +"your accounts, provided that you added their correct :ref:`encoding group " +"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1043 +msgid "" +"This report can be generated monthly, and a corresponding XML file is " +"created, if you go to :menuselection:`Accounting --> Reporting --> Mexico " +"--> Trial Balance`, and click the :guilabel:`SAT (XML)` button. Select the " +"month you want to download beforehand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial balance report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1052 +msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1054 +msgid "" +"An additional report is the *Month 13*: a closing balance sheet that shows " +"any adjustments or movements made in the accounting to close the year." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 +msgid "" +"To generate this XML document, navigate to :menuselection:`Accounting --> " +"Accounting --> Miscellaneous --> Journal Entries`, and create a new " +"document. Here, add all amounts to modify, and balance the debit and/or " +"credit of each one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1061 +msgid "" +"After this is done, click :guilabel:`Mark as Closing Entry`, and the report " +"found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial " +"Balance Month 13`, contains the total amount of the year, plus all the " +"additions of the journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1065 +msgid "" +"The XML file is generated by pressing the :guilabel:`SAT (XML)` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial Balance Month 13 setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial Balance Month 13 report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1078 +msgid "" +"By law, all transactions in Mexico must be recorded digitally. Since Odoo " +"automatically creates all the underlying journal entries of your invoicing " +"and payments, you can export your journal entries to comply with |SAT|'s " +"audits and/or tax refunds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1083 +msgid "" +"You can filter by period, or by journal, according to your current needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1085 +msgid "" +"To create the XML, go to :menuselection:`Accounting --> Reporting --> Audit " +"Reports --> General Ledger`, and click :guilabel:`XML (Polizas)`. Here, you " +"can select between four types of :guilabel:`Export` types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1089 +msgid ":guilabel:`Tax audit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1090 +msgid ":guilabel:`Audit certification`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 +msgid ":guilabel:`Return of goods`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1092 +msgid ":guilabel:`Compensation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1094 +msgid "" +"For :guilabel:`Tax audit`, or :guilabel:`Audit certification`, you need to " +"write the :guilabel:`Order Number` provided by the |SAT|. For " +":guilabel:`Return of goods`, or :guilabel:`Compensation`, you need to write " +"your :guilabel:`Process Number`, also provided by the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 +msgid "" +"If you want to see this report without sending it, use `ABC6987654/99` for " +":guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process " +"Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1104 +msgid "DIOT report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1106 +msgid "" +"The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative" +" Declaration of Operations with Third Parties*) is an additional obligation " +"with the |SAT|, where the current status of creditable and non-creditable " +"payments, withholdings, and refunds of VAT from your vendor bills, are " +"provided to the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1111 +msgid "" +"Unlike other reports, the |DIOT| is uploaded to a software provided by the " +"|SAT| that contains the A-29 form. In Odoo, you can download the records of " +"your transactions as a :file:`.txt` file that can be uploaded to the form, " +"avoiding direct capture of this data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1115 +msgid "" +"The transactions file contains the total amount of your payments registered " +"in vendor bills, broken down into the corresponding types of IVA. The " +":guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1119 +msgid "" +"To get the |DIOT| report, go to :menuselection:`Accounting --> Reports --> " +"Mexico --> Transactions with third parties [DIOT]`. Select the month that " +"suits you, and click :guilabel:`DIOT (TXT)` to download the :file:`.txt` " +"file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "A Vendor Bill that is In Payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "DIOT (TXT) download button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 +msgid "" +"You need to fill the field, :guilabel:`L10N Mx Type of Operation`, in the " +":guilabel:`Accounting` tab of each one of your vendors to prevent validation" +" errors. Make sure that your foreign customers have their country set up for" +" :guilabel:`L10N Mx Nationality` to appear automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT information on a vendor contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:6 +msgid "XAF Export" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:8 +msgid "" +"With the Dutch accounting localization installed, you will be able to export" +" all your accounting entries in XAF format. For this, you have to go in " +":menuselection:`Accounting --> Reporting --> General Ledger`, you define the" +" entries you want to export using the filters (period, journals, ...) and " +"then you click on the button **EXPORT (XAF)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:15 +msgid "Dutch Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:17 +msgid "" +"If you install the Dutch accounting localization, you will have access to " +"some reports that are specific to the Netherlands such as :" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:21 +msgid "Tax Report (Aangifte omzetbelasting)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:22 +msgid "Intrastat Report (ICP)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:3 +msgid "Peru" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:8 +msgid "" +"The Peruvian localization has been improved and extended, in this version " +"the next modules are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:11 +msgid "" +"**l10n_pe**: Adds accounting features for the Peruvian localization, which " +"represent the minimal configuration required for a company to operate in " +"Peru and under the SUNAT regulations and guidelines. The main elements " +"included in this module are: Chart of account, taxes, document types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:16 +msgid "" +"**l10n_pe_edi**: includes all technical and functional requirements to " +"generate and validate Electronic Invoice, based on the SUNAT specification " +"to create and process valid electronic documents, for more technical detail " +"you can access the `SUNAT EDI specifications " +"`_, that keeps track of new changes and " +"updates. The features of this module are based on the resolutions published " +"on the `SUNAT Legislation " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:25 +msgid "`App Tour - Localización de Peru `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:26 +msgid "" +"`Smart Tutorial - Localización de Peru `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:32 +msgid "Install the Peruvian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:34 +msgid "" +"Go to *Apps* and search for Peru, then click Install in the module Peru EDI." +" This module has a dependency with *Peru - Accounting*. In case this last " +"one is not installed, Odoo installs it automatically within EDI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "The \"Module\" filter is set on \"Peru\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:43 +msgid "" +"When you install a database from scratch selecting Peru as country, Odoo " +"automatically installs the base module: Peru - Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:49 +msgid "" +"In addition to the basic information in the Company, we need to set Peru as " +"the Country, this is essential for the Electronic Invoice to work properly. " +"The field **Address Type Code** represents the establishment code assigned " +"by the SUNAT when companies register their RUC (Unique Contributor " +"Registration):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Company data for Peru including RUC and Address type code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:60 +msgid "" +"In case the Address type code is unknown, you can set it as the default " +"value: 0000. Be aware that if an incorrect value is entered, the Electronic " +"invoice validation might have errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:64 +msgid "The NIF should be set following the RUC format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:68 +msgid "Chart of Account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:70 +msgid "" +"The chart of accounts is installed by default as part of the set of data " +"included in the localization module, the accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:74 +msgid "Default Account Payable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:77 +msgid "" +"The chart of accounts for Peru is based on the most updated version of the " +":abbr:`PCGE (Plan Contable General Empresarial)`, which is grouped in " +"several categories and is compatible with NIIF accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:82 +msgid "Accounting Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:84 +msgid "" +"Once the modules are installed and the basic information of your company is " +"set, you need to configure the elements required for Electronic Invoice. For" +" this, go to :menuselection:`Accounting --> Settings --> Peruvian " +"Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:89 +msgid "Basic Concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:91 +msgid "Here are some terms that are essential on the Peruvian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:93 +msgid "" +"**EDI**: Electronic Data Interchange, which in this refers to the Electronic" +" Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:94 +msgid "" +"**SUNAT**: is the organization that enforces customs and taxation in Peru." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:95 +msgid "" +"**OSE**: Electronic Service Operator, `OSE SUNAT's definition " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:97 +msgid "**CDR**: Receipt certificate (Constancia de Recepción)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:98 +msgid "" +"**SOL Credentials**: Sunat Operaciones en Línea. User and password are " +"provided by the SUNAT and grant access to Online Operations systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:103 +msgid "Signature Provider" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:105 +msgid "" +"As part of the requirements for Electronic Invoice in Peru, your company " +"needs to select a Signature Provider that will take care of the document " +"signing process and manage the SUNAT validation response. Odoo offers three " +"options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:109 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:116 +msgid "IAP (Odoo In-App Purchase)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:110 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:174 +msgid "Digiflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:111 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:190 +msgid "SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:113 +msgid "" +"Please refer to the sections below to check the details and considerations " +"for each option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:118 +msgid "" +"This is the default and the suggested option, considering the digital " +"ceritificate is included as part of the service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "IAP option as signature providers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:126 +msgid "What is the IAP?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:128 +msgid "" +"This is a signature service offered directly by Odoo, the service takes care" +" of the next process:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:130 +msgid "" +"Provides the Electronic invoice Certificate, so you do not need to acquire " +"one by yourself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:131 +msgid "Send the document to the OSE, in this case, Digiflow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:132 +msgid "Receive the OSE validation and CDR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:135 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:137 +msgid "" +"The service requires Credits in order to process your electronic documents. " +"Odoo provides 1000 credits for free in new databases. After these credits " +"are consumed, you need to buy a Credit Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "Credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "EUR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "22" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "5000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "110" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:148 +msgid "10,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:148 +msgid "220" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:150 +msgid "20,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:150 +msgid "440" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:153 +msgid "The credits are consumed per each document that is sent to the OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:156 +msgid "" +"If you have a validation error and the document needs to be sent one more " +"time, one additional credit will be charged. Therefore, it is paramount that" +" you verify all information is correct before sending your document to the " +"OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:161 +msgid "What do you need to do?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:163 +msgid "" +"In Odoo, once your enterprise contract is activated and you start working in" +" Production, you need to buy credits once the first 1000 are consumed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:165 +msgid "" +"As Digiflow is the OSE used in the IAP, you need to affiliate it as the " +"official OSE for your company on the SUNAT website. This is a simple " +"process. For more information, please check `OSE Affiliation guide " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:169 +msgid "" +"Register Digiflow as the authorized PSE, please check `PSE Affiliation guide" +" " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:176 +msgid "" +"This option can be used as an alternative, instead of using the IAP services" +" you can send your document validation directly to Digiflow. In this case " +"you need to consider:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:179 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:196 +msgid "" +"Buy your own digital Certificate: For more detail regarding the official " +"vendor list, and the process to acquire it, please refer to `SUNAT Digital " +"Ceritifcates " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:182 +msgid "" +"Sign a service agreement directly with `Digiflow " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:183 +msgid "Provide your SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:192 +msgid "" +"In case your company wants to sign directly with the SUNAT, it is possible " +"to select this option in your configuration. In this case you need to " +"consider: - Get the SUNAT Certification process accepted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:200 +msgid "Provide you SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:203 +msgid "" +"When using direct connection with the SUNAT, the SOL User must be set with " +"the Company RUT + User Id. Example: ``20121888549JOHNSMITH``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:207 +msgid "Testing environment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:209 +msgid "" +"Odoo provides a testing environment that can be activated before your " +"company goes into production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:211 +msgid "" +"When using the testing environment and the IAP signature, you don’t need to " +"buy testing credits for your transactions as all of them are validated by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:215 +msgid "" +"By default the databases are set to work on production, make sure to enable " +"the testing mode if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:221 +msgid "" +"In case you don’t use Odoo IAP, in order to generate the electronic invoice " +"signature, a digital certificate with the extension ``.pfx`` is required. " +"Proceed to this section and load your file and password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "EDI Certificate wizard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:232 +msgid "" +"The official currency exchange rate in Peru is provided by the Bank of Peru." +" Odoo can connect directly to its services and get the currency rate either " +"automatically or manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Bank of Peru is displayed in Multicurrency Service option" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:239 +msgid "" +"Please refer to the next section in our documentation for more information " +"about :doc:`multicurrencies <../accounting/get_started/multi_currency>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:243 +msgid "Configure Master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:248 +msgid "" +"As part of the localization module the taxes are created automatically with " +"their related financial account and electronic invoice configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "List of default taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:256 +msgid "EDI Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:258 +msgid "" +"As part of the taxes configuration, there are three new fields required for " +"electronic invoice, the taxes created by default have this data included, " +"but in case you create new taxes make sure you fill in the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Taxes EDI data for Peru" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:268 +msgid "Fiscal Positions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:270 +msgid "" +"There are two main fiscal positions included by default when you install the" +" Peruvian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:272 +msgid "" +"**Extranjero - Exportación**: Set this fiscal position on customers for " +"Exportation transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:274 +msgid "**Local Peru**: Set this fiscal position on local customers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:277 +msgid "Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:279 +msgid "" +"In some Latin American countries, including Peru, some accounting " +"transactions like invoices and vendor bills are classified by document " +"types, defined by the government fiscal authorities, in this case by the " +"SUNAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:283 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the Document Type includes the " +"country on which the document is applicable;the data is created " +"automatically when the localization module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:287 +msgid "" +"The information required for the document types is included by default so " +"the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Document Type list" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:295 +msgid "" +"Currently the documents supported on customer invoices are: Invoice, Boleta," +" Debit Note and Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:301 +msgid "" +"When creating Sales Journals, the following information must be filled, in " +"addition to the standard fields on the Journals:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:305 +msgid "Use Documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:307 +msgid "" +"This field is used to define if the journal uses Document Types. It is only " +"applicable to Purchase and Sales journals, which are the ones that can be " +"related to the different set of document types available in Peru. By " +"default, all the sales journals created use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:312 +msgid "Electronic Data Interchange" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:314 +msgid "" +"This section indicates which EDI workflow is used in the invoice, for Peru " +"we must select “Peru UBL 2.1”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Journal EDI field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:322 +msgid "" +"By default, the value Factur-X (FR) is always displayed, make sure you can " +"uncheck it manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:328 +msgid "Identification Type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:330 +msgid "" +"As part of the Peruvian localization, the identification types defined by " +"the SUNAT are now available on the Partner form, this information is " +"essential for most transactions either on the sender company and in the " +"customer, make sure you fill in this information in your records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Partner identification type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:340 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:109 +msgid "Product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:342 +msgid "" +"Additional to the basic information in your products, for the Peruvian " +"localization, the UNSPC Code on the product is a required value to be " +"configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "UNSPC Code on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:354 +msgid "Customer invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:357 +msgid "EDI Elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:359 +msgid "" +"Once you have configured your master data, the invoices can be created from " +"your sales order or manually. Additional to the basic invoice information " +"described on :doc:`our page about the invoicing process " +"<../accounting/customer_invoices/overview>`, there are a couple of fields " +"required as part of the Peru EDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:364 +msgid "" +"**Document type**: The default value is “Factura Electronica” but you can " +"manually change the document type if needed and select Boleta for example." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice document type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:371 +msgid "" +"**Operation type**: This value is required for Electronic Invoice and " +"indicates the transaction type, the default value is “Internal Sale” but " +"another value can be selected manually when needed, for example Export of " +"Goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice operation type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:379 +msgid "" +"**EDI Affectation Reason**: In the invoice lines, additional to the Tax " +"there is a field “EDI Affectation Reason” that determines the tax scope " +"based on the SUNAT list that is displayed. All the taxes loaded by default " +"are associated with a default EDI affection reason, if needed you can " +"manually select another one when creating the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Tax affectation reason in invoice line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:391 +msgid "" +"Once you check all the information in your invoice is correct, you can " +"proceed to validate it. This action registers the account move and triggers " +"the Electronic invoice workflow to send it to the OSE and the SUNAT. The " +"following message is displayed at the top of the invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Sending of EDI Invoice in blue" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:399 +msgid "" +"Asynchronous means that the document is not sent automatically after the " +"invoice has been posted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:402 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:496 +msgid "Electronic Invoice Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:404 +msgid "" +"**To be Sent**: Indicates the document is ready to be sent to the OSE, this " +"can be done either automatically by Odoo with a *cron* that runs every hour," +" or the user can send it immediately by clicking on the button “Sent now”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Send EDI manually" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:412 +msgid "" +"**Sent**: Indicates the document was sent to the OSE and was successfully " +"validated. As part of the validation a ZIP file is downloaded and a message " +"is logged in the chatter indicating the correct Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Message on chatter when the invoice is valid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:420 +msgid "" +"In case there is a validation error the Electronic Invoice status remains in" +" “To be sent” so the corrections can be made and the invoice can be sent " +"again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:424 +msgid "" +"One credit is consumed each time that you send a document for validation, in" +" this sense if an error is detected on an invoice and you send it one more " +"time, two credits are consumed in total." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:429 +msgid "Common Errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:431 +msgid "" +"There are multiple reasons behind a rejection from the OSE or the SUNAT, " +"when this happens Odoo sends a message at the top of the invoice indicating " +"the error details and in the most common cases a hint to fix the issue." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:435 +msgid "If a validation error is received, you have two options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:437 +msgid "" +"In case the error is related to master data on the partner, customer or " +"taxes, you can simply apply the change on the record (example customer " +"identification type) and once it is done click on the Retry button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:440 +msgid "" +"If the error is related to some data recorded on the invoice directly " +"(Operation type, missing data on the invoice lines), the correct solution is" +" to reset the invoice to Draft, apply the changes, and then send the invoice" +" again to the SUNAT for another validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "List of common errors on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:449 +msgid "" +"For more detail please refert to `Common errors in SUNAT " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:453 +msgid "Invoice PDF Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:455 +msgid "" +"After the invoice is accepted and validated by the SUNAT, the invoice PDF " +"report can be printed. The report includes a QR code, indicating the invoice" +" is a valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:463 +msgid "IAP Credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:465 +msgid "" +"Odoo’s Electronic IAP offers 1000 credits for free, after these credits are " +"consumed in your production database, your company must buy new credits in " +"order to process your transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:468 +msgid "" +"Once you run out of credits a red label is displayed at the top of the " +"invoice indicating that additional credits are required, you can easily buy " +"them by accessing the link provided in the message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Buying credits in the IAP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:476 +msgid "" +"In the IAP service includes packages with different pricing based on the " +"number of credits. The price list in the IAP is always displayed in EUR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:480 +msgid "Special Use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:483 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:519 +msgid "Cancellation process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:485 +msgid "" +"Some scenarios require an invoice cancellation, for example, when an invoice" +" was created by mistake. If the invoice was already sent and validated by " +"the SUNAT, the correct way to proceed is by clicking on the button Request " +"Cancellation:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Request invoice cancellation button" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:493 +msgid "In order to cancel an invoice, please provide a cancellation Reason." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:498 +msgid "" +"**To Cancel**: Indicates the cancellation request is ready to be sent to " +"the OSE, this can be done either automatically by Odoo with a *cron* that " +"runs every hour, or the user can send it immediately by clicking on the " +"button “Send now”. Once it is sent, a cancellation ticket is created, as a " +"result the next message and CDR File are logged in the chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Cancellation CDR sent by the SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:507 +msgid "" +"**Cancelled**: Indicates the cancellation request was sent to the OSE and " +"was successfully validated. As part of the validation a ZIP file is " +"downloaded and a message is logged in the chatter indicating the correct " +"Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "nvoice after cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:516 +msgid "One credit is consumed on each cancellation request." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:521 +msgid "" +"When creating exportation invoices, take into account the next " +"considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:523 +msgid "The Identification type on your customer must be Foreign ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:524 +msgid "Operation type in your invoice must be an Exportation one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:525 +msgid "The taxes included in the invoice lines should be EXP taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Exportation invoices main data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:532 +msgid "Advance Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:534 +msgid "Create the advance payment Invoice and apply its related payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:535 +msgid "Create the final invoice without considering the advance payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:536 +msgid "" +"Create a credit note for the Final invoice with the advance payment amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:537 +msgid "Reconcile the Credit note with the final invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:538 +msgid "" +"The remaining balance on the final invoice should be paid with a regular " +"payment transaction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:541 +msgid "Detraction Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:543 +msgid "" +"When creating invoices that is subject to Detractions, take into account the" +" next considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:545 +msgid "" +"All the products included in the invoice must have these fields configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction fields on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:551 +msgid "Operation type in your invoice must be ``1001``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction code on invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:558 +msgid "Credit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:560 +msgid "" +"When a correction or refund is needed over a validated invoice, a credit " +"note must be generated, for this just click on the button “Add Credit Note”," +" a part of the Peruvian localization you need to prove a Credit Reason " +"selecting one of the options in the list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Add Credit Note from invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:569 +msgid "" +"When creating your first credit Note, select the Credit Method: Partial " +"Refund, this allows you to define the credit note sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:572 +msgid "By default the Credit Note is set in the document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Credit Note document type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:578 +msgid "" +"To finish the workflow please follow the instructions on :doc:`our page " +"about Credit Notes <../accounting/customer_invoices/credit_notes>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:582 +msgid "" +"The EDI workflow for the Credit notes works in the same way as the invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:587 +msgid "" +"As part of the Peruvian localization, besides creating credit notes from an " +"existing document you can also create debit Notes. For this just use the " +"button “Add Debit Note”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:590 +msgid "By default the Debit Note is set in the document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:3 +msgid "Philippines" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:8 +msgid "" +":ref:`Install ` the :guilabel:`🇵🇭 Philippines` :ref:`fiscal" +" localization package ` to get all the " +"default accounting features of the Philippine localization, such as a chart " +"of accounts, taxes, and the BIR 2307 report. These provide a base template " +"to get started with using Philippine accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:14 +msgid "" +"When creating a new database and `Philippines` is selected as a country, the" +" fiscal localization module **Philippines - Accounting** is automatically " +"installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:16 +msgid "" +"If installing the module in an existing company, the **chart of accounts** " +"and **taxes** will *not* be replaced if there are already posted journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:18 +msgid "" +"The BIR 2307 report is installed, but the withholding taxes may need to be " +"manually created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:21 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:28 +msgid "Chart of accounts and taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:23 +msgid "" +"A minimum configuration default chart of accounts is installed, and the " +"following types of taxes are installed and also linked to the relevant " +"account:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:26 +msgid "VAT 12%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:27 +msgid "VAT Exempt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:30 +msgid "" +"For the withholding taxes, there is an additional :guilabel:`Philippines " +"ATC` field under the :guilabel:`Philippines` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Philippines ATC code field set on taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:36 +msgid "" +"Taxes' ATC codes are used for the BIR 2307 report. If a tax is created " +"manually, its ATC code must be added." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:42 +msgid "" +"When a company or an individual (not belonging to a company) contact is " +"located in the Philippines, fill in the :guilabel:`Tax ID` field with their " +"`Taxpayer Identification Number (TIN)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:45 +msgid "" +"For individuals not belonging to a company, identify them by using the " +"following additional fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:47 +msgid ":guilabel:`First Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:48 +msgid ":guilabel:`Middle Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:49 +msgid ":guilabel:`Last Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Individual type contact with First, Middle, and Last Name fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:55 +msgid "" +"For both :guilabel:`Company` and :guilabel:`Individual`, the TIN should " +"follow the `NNN-NNN-NNN-NNNNN` format. The branch code should follow the " +"last digits of the TIN, or else it can be left as `00000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:60 +msgid "BIR 2307 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:62 +msgid "" +"**BIR 2307** report data, also known as *Certificate of Creditable Tax " +"Withheld at Source*, can be generated for purchase orders and vendor " +"payments with the applicable withholding taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:65 +msgid "" +"To generate a BIR 2307 report, select one or multiple vendor bills from the " +"list view, and click :menuselection:`Action --> Download BIR 2307 XLS`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Multiple vendor bills selected with action to \"Download BIR 2307 XLS\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:71 +msgid "The same action can be performed on a vendor bill from the form view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:73 +msgid "" +"A pop-up appears to review the selection, then click on " +":guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Pop up menu to generate BIR 2307 XLS file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:78 +msgid "" +"This generates the `Form_2307.xls` file that lists all the vendor bill lines" +" with the applicable withholding tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:81 +msgid "" +"The same process above can also be done for a *single* vendor :doc:`payment " +"<../accounting/payments>` if they were linked to one or more :doc:`vendor " +"bills <../accounting/payments>` with applied withholding taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:86 +msgid "" +"If there is no withholding tax applied, then the XLS file will not generate " +"records for those vendor bill lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:88 +msgid "" +"When grouping payments for multiple bills, Odoo splits the payments based on" +" the contact. From a payment, clicking :menuselection:`Action --> Download " +"BIR 2307 XLS`, generates a report that only includes vendor bills related to" +" that contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:93 +msgid "" +"Odoo cannot generate the BIR 2307 PDF report or DAT files directly. The " +"generated `Form_2307.xls` file can be exported to an *external* tool to " +"convert it to BIR DAT or PDF format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:3 +msgid "Romania" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:8 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Romanian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:17 +msgid ":guilabel:`Romania - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:18 +msgid "`l10n_ro`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:20 +msgid ":guilabel:`Romanian SAF-T Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:21 +msgid "`l10n_ro_saft`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:22 +msgid "Module to generate the **D.406 declaration** in the SAF-T format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "Modules for the Romanian localization" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:28 +msgid "D.406 declaration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:30 +msgid "" +"Starting January 1, 2023, companies registered for tax purposes in Romania " +"must report their accounting data to the Romanian Tax Agency monthly or " +"quarterly in the D.406 declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:33 +msgid "" +"Odoo provides all you need to export the data of this declaration in the " +"SAF-T XML format, which you can validate and sign using the software " +"provided by the Romanian Tax Agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:37 +msgid "" +"Currently, Odoo only supports the generation of the monthly/quarterly D.406 " +"declaration (containing journal entries, invoices, vendor bills, and " +"payments). The yearly declaration (including assets) and the on-demand " +"declaration (including inventory) are not yet supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:45 +msgid "Company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:47 +msgid "" +"Under :guilabel:`Settings --> General Settings`, in the **Companies** " +"section, click :guilabel:`Update Info` and fill in the company's " +":guilabel:`Country`, :guilabel:`City`, and :guilabel:`Telephone Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:50 +msgid "" +"Provide your company's :abbr:`CUI (Codul Unic de Inregistrare)` number or " +":abbr:`CIF (*Codul de identificare fiscală*)` number (for foreign companies)" +" in the :guilabel:`Company ID` field, without the `RO` prefix (e.g., " +"`18547290`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:53 +msgid "" +"If your company is **registered** for VAT in Romania, fill in the " +":guilabel:`Tax ID` field number, including the `RO` prefix (e.g., " +"`RO18547290`). If the company is **not** registered for VAT in Romania, you " +"**must not** fill in the :guilabel:`Tax ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:56 +msgid "" +"Open the **Contacts** app and search for your company. Open your company's " +"profile, and in the :guilabel:`Accounting` tab, click :guilabel:`Add a line`" +" and add your **bank account number** if not informed already. Make sure the" +" profile is set as :guilabel:`Company` above the **name**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:60 +msgid "" +"You must have at least one **contact person** linked to your company in the " +"**Contacts** app. If no **contact person** is linked, create a new one by " +"clicking :guilabel:`New`, set it as :guilabel:`Individual`, and select your " +"company in the :guilabel:`Company name` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:67 +msgid "" +"To generate a file receivable by the Romanian Tax Agency, the chart of " +"accounts must not deviate from an official chart of accounts, such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:70 +msgid "" +"the chart of accounts for commercial companies (*PlanConturiBalSocCom*), " +"which is installed by default when creating a company with the Romanian " +"localization or;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:72 +msgid "" +"the chart of accounts for companies following `IFRS " +"`_ (*PlanConturiIFRS*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:74 +msgid "" +"Under :guilabel:`Settings --> Accounting`, in the **Romanian localization** " +"section, set the :guilabel:`Tax Accounting Basis` to reflect the accounting " +"regulations and Chart of Accounts used by the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:82 +msgid "Customer and supplier" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:84 +msgid "" +"Fill in the :guilabel:`Country`, :guilabel:`City`, and :guilabel:`Zip Code` " +"of each partner that appears in your invoices, vendor bills, or payments " +"through the **Contacts** app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:87 +msgid "" +"For partners that are companies, you must fill in the VAT number (including " +"the country prefix) in the :guilabel:`Tax ID` field. If the partner is a " +"company based in Romania, you may instead fill in the CUI number (without " +"the 'RO' prefix) in the :guilabel:`Company ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:94 +msgid "" +"You must indicate the :guilabel:`Romanian SAF-T Tax Type` (3-digit number) " +"and :guilabel:`Romanian SAF-T Tax Code` (6-digit number) on each of the " +"taxes you use. This is already done for the taxes that exist by default in " +"Odoo. To do so, go to :menuselection:`Accounting --> Configuration --> " +"Taxes`, select the tax you wish to modify, click the :guilabel:`Advanced " +"Options` tab, and fill in the **tax type** and **tax code** fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:101 +msgid "" +"The **tax type** and **tax code** are codes defined by the Romanian Tax " +"Agency for the **D.406 declaration**. These can be found in the Excel " +"spreadsheet published as guidance for completing the declaration, which you " +"can find on the `website of the Romanian Tax Agency " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:111 +msgid "" +"For some types of goods transactions, the :guilabel:`Intrastat Code` (Cod " +"NC) must be configured on the product, as it is required by Romanian law:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:114 +msgid "import / export transactions;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:115 +msgid "" +"acquisitions / supplies of food products subjected to reduced VAT rate;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:116 +msgid "intra-community movements subjected to intrastat reporting;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:117 +msgid "" +"acquisitions / supplies subjected to local reversed VAT charge (depending on" +" Cod NC); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:118 +msgid "" +"transactions with excisable products for which excise duties are determined " +"based on the Cod NC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:120 +msgid "" +"If the Intrastat Code is not specified on a non-service product, the default" +" code '0' will be used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:122 +msgid "" +"To configure the :guilabel:`Intrastat Codes`, go to " +":menuselection:`Accounting --> Customers --> Products`, select a product, " +"and in the :guilabel:`Accounting` tab, set a :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:127 +msgid ":doc:`../accounting/reporting/intrastat`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:132 +msgid "" +"You must check the :guilabel:`Is self-invoice (RO)?` checkbox in the " +":guilabel:`Other Info` tab for any vendor bill that is a self-invoice (i.e. " +"a vendor bill that you issued yourself in the absence of an invoice document" +" received from a supplier)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:137 +msgid "Generating the declaration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:140 +msgid "Exporting your data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:142 +msgid "" +"To export the XML for the D.406 declaration, go to " +":menuselection:`Accounting --> Reports --> General Ledger` and click on " +":guilabel:`SAF-T`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "Click on the 'SAF-T' button to export the D.406 XML declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:149 +msgid "" +"You can then validate and sign the XML file using the Romanian Tax Agency's " +"validation software, *DUKIntegrator*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:153 +msgid "Signing the report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:155 +msgid "" +"Download and install the *DUKIntegrator* validation software found on the " +"`website of the Romanian Tax Agency " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:158 +msgid "" +"Once you have generated the XML, open 'DUKIntegrator' and select the file " +"you have just generated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:160 +msgid "" +"Click on :guilabel:`Validare + creare PDF` to create an **unsigned** PDF " +"containing your report, or :guilabel:`Validare + creare PDF semnat` to " +"create a **signed** PDF containing your report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "The DUKIntegrator validation software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:167 +msgid "" +"If the *DUKIntegrator* validator detects errors or inconsistencies in your " +"data, it generates a file that explains the errors. In this case, you need " +"to correct those inconsistencies in your data before you can submit the " +"report to the Romanian Tax Agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:3 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:8 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Saudi Arabian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:18 +msgid "Saudi Arabia - Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:19 +msgid "`l10n_sa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:21 +msgid "Saudi Arabia - E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:22 +msgid "`l10n_sa_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:23 +msgid "ZATCA e-invoices implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:24 +msgid "Saudi Arabia - Point of Sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:25 +msgid "`l10n_sa_pos`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:26 +msgid "Point of Sale compliance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:29 +msgid "ZATCA e-invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:31 +msgid "" +"The ZATCA e-invoicing system is designed to streamline and digitize the " +"invoicing process for businesses operating in Saudi Arabia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:35 +msgid "" +"`ZATCA e-invoicing page " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:40 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Companies`, click " +":guilabel:`Update info`, and ensure the following company information is " +"complete and up-to-date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:43 +msgid "The full :guilabel:`Company Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:44 +msgid "" +"All relevant :guilabel:`Address` fields, including the :guilabel:`Building " +"Number` and :guilabel:`Plot Identification` (four digits each)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:46 +msgid "" +"Select an enterprise :guilabel:`Identification Scheme`. It is recommended to" +" use the :guilabel:`Commercial Registration Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:48 +msgid "" +"Enter the :guilabel:`Identification Number` for the selected " +":guilabel:`Identification Scheme`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:49 +msgid "The :guilabel:`VAT` number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:50 +msgid "Ensure the :guilabel:`Currency` is set to :guilabel:`SAR`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:53 +msgid "" +"It is also necessary to fill out similar information for partner companies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:56 +msgid "Simulation mode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:59 +msgid "" +"It is strongly recommended to thoroughly test all invoicing workflows using " +"the Fatoora **simulation** portal first, as **any** invoice submitted to the" +" regular Fatoora portal will be accounted for, which could lead to fines and" +" penalties." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:64 +msgid "Fatoora simulation portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:66 +msgid "" +"Log in on the `Fatoora portal `_ using the " +"company's ZATCA credentials. Then, click the :guilabel:`Fatoora Simulation " +"Portal` button to switch to the simulation portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:71 +msgid "" +"`ZACTA Fatoora portal user manual version 3 (May 2023) " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:76 +msgid "ZATCA API integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:78 +msgid "" +"On Odoo, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"Under :guilabel:`ZATCA API Integration`, select the :guilabel:`Simulation " +"(Pre-Production)` :guilabel:`API mode` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:87 +msgid "" +"Each sales journal on Odoo needs to be configured. To do so, go to " +":menuselection:`Accounting --> Configuration --> Journals`, open any sales " +"journal (e.g., Customer Invoices), and go to the :guilabel:`ZATCA` tab. Once" +" there, enter any :guilabel:`Serial Number` to identify the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:92 +msgid "" +"The same serial number can be used for all of the company's sales journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:94 +msgid "" +"Next, click :guilabel:`Onboard Journal`. In the dialog box, providing an " +":abbr:`OTP (one-time password)` code is required. To retrieve it, open the " +"`Fatoora simulation portal `_, click " +":guilabel:`Onboard New Solution Unit/Device`, choose the number of OTP codes" +" to generate (one per journal to configure), and click :guilabel:`Generate " +"OTP Code`. Copy an OTP code, it into the dialog box on Odoo, and click " +":guilabel:`Request`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:101 +msgid "OTP codes expire after one hour." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:104 +msgid "" +"If any issue occurs during onboarding, click :guilabel:`Regenerate CSR` to " +"start again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:107 +msgid "Testing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:109 +msgid "" +"When confirming an invoice, there is now an option to process the invoice, " +"sending it directly the Fatoora simulation portal. Odoo displays the " +"portal's response after each submission. Only rejected invoices can be reset" +" to draft and edited on Odoo. Furthermore, at the end of each day, Odoo " +"sends all unprocessed invoices to the portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:115 +msgid "" +"Testing all invoicing workflows, preferably with real invoices and for a " +"reasonable amount of time, is recommended." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:117 +msgid "" +"Compare the invoices received statistics page on the Fatoora simulation " +"portal with the list of invoices on Odoo to ensure both align." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:123 +msgid "" +"When using a **0% tax** in a customer invoice, it is necessary to specify " +"the reason behind such a rate. To configure taxes, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and " +"open the tax to edit. Under the :guilabel:`Advanced Options`, select an " +":guilabel:`Exemption Reason Code` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:128 +msgid "" +"When using **retention** or **withholding an amount** in a customer invoice," +" the tax used to retain the amount needs to be specified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:132 +msgid "Production mode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:134 +msgid "" +"When ready for production, change the :ref:`API mode ` to :guilabel:`Production` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:138 +msgid "" +"Setting the :guilabel:`API mode` to :guilabel:`Production` is " +"**irreversible**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:140 +msgid "" +"The sales journals initially linked to the simulation portal now needs to be" +" linked to the regular portal. To do so, :ref:`onboard the journals ` again, ensuring to use the regular `Fatoora portal " +"`_ this time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:3 +msgid "Singapore" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:6 +msgid "Add PayNow QR codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:8 +msgid "" +"PayNow is a payment service platform that allows customers to make instant " +"domestic payments to individuals and merchants in Singapore dollars via " +"online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:18 +msgid "PayNow bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:20 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate PayNow. Set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:25 +msgid "" +"The account holder's country must be set to Singapore on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:45 +msgid "Issue invoices with PayNow QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:53 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the PayNow QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:3 +msgid "Spain" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:6 +msgid "Spanish chart of accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:8 +msgid "Several Spanish charts of accounts are available by default in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:10 +msgid "PGCE PYMEs 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:11 +msgid "PGCE Completo 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:12 +msgid "PGCE Entitades" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:14 +msgid "" +"To choose the one you want, go to :menuselection:`Accounting --> " +"Configuration --> Settings`, then select a package in the :guilabel:`Fiscal " +"localization` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:18 +msgid "" +"When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed" +" by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:21 +msgid "" +"You can only change the accounting package as long as you have not created " +"any accounting entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:24 +msgid "Spanish accounting reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:26 +msgid "" +"If the Spanish accounting localization is installed, you have access to " +"accounting reports specific to Spain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:30 +msgid "Tax Report (Modelo 111)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:31 +msgid "Tax Report (Modelo 115)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:32 +msgid "Tax Report (Modelo 303)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:33 +msgid "Tax Report (Modelo 347)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:34 +msgid "Tax Report (Modelo 349)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:35 +msgid "Tax Report (Modelo 390)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:3 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:6 +msgid "ISR (In-payment Slip with Reference number)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:8 +msgid "" +"The ISRs are payment slips used in Switzerland. You can print them directly " +"from Odoo. On the customer invoices, there is a new button called *Print " +"ISR*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:16 +msgid "" +"The button *Print ISR* only appears there is well a bank account defined on " +"the invoice. You can use CH6309000000250097798 as bank account number and " +"010391391 as CHF ISR reference." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:23 +msgid "Then you open a pdf with the ISR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:28 +msgid "" +"There exists two layouts for ISR: one with, and one without the bank " +"coordinates. To choose which one to use, there is an option to print the " +"bank information on the ISR. To activate it, go in " +":menuselection:`Accounting --> Configuration --> Settings --> Customer " +"Invoices` and enable **Print bank on ISR**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:38 +msgid "ISR reference on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:40 +msgid "" +"To ease the reconciliation process, you can add your ISR reference as " +"**Payment Reference** on your invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:43 +msgid "" +"To do so, you need to configure the Journal you usually use to issue " +"invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the Journal you want to modify (By default, the Journal is named " +"*Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab." +" In the **Communication Standard** field, select *Switzerland*, and click on" +" *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst-1 +msgid "" +"Configure your Journal to display your ISR as payment reference on your " +"invoices in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:53 +msgid "Currency Rate Live Update" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:55 +msgid "" +"You can update automatically your currencies rates based on the Federal Tax " +"Administration from Switzerland. For this, go in :menuselection:`Accounting " +"--> Settings`, activate the multi-currencies setting and choose the service " +"you want." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:64 +msgid "Updated VAT for January 2018" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:66 +msgid "" +"Starting from the 1st January 2018, new reduced VAT rates will be applied in" +" Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate" +" for the hotel sector will switch from 3.8% to 3.7%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:71 +msgid "" +"How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:73 +msgid "" +"If you have the V11.1 version, all the work is already been done, you don't " +"have to do anything." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:76 +msgid "" +"If you have started on an earlier version, you first have to update the " +"module \"Switzerland - Accounting Reports\". For this, you go in " +":menuselection:`Apps --> remove the filter \"Apps\" --> search for " +"\"Switzerland - Accounting Reports\" --> open the module --> click on " +"\"upgrade\"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:83 +msgid "" +"Once it has been done, you can work on creating new taxes for the updated " +"rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:87 +msgid "" +"**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want " +"to keep them since you may have to use both rates for a short period of " +"time. Instead, remember to archive them once you have encoded all your 2017 " +"transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:92 +msgid "The creation of such taxes should be done in the following manner:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:94 +msgid "" +"**Purchase taxes**: copy the origin tax, change its name, label on invoice, " +"rate and tax group (effective from v10 only)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:97 +msgid "" +"**Sale taxes**: copy the origin tax, change its name, label on invoice, rate" +" and tax group (effective from v10 only). Since the vat report now shows the" +" details for old and new rates, you should also set the tags accordingly to" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:102 +msgid "" +"For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: " +"grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:105 +msgid "" +"For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: " +"grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:108 +msgid "" +"You'll find below, as examples, the correct configuration for all taxes " +"included in Odoo by default" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Rate**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Label on Invoice**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Group (effective from V10)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Scope**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tag**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "TVA 7.7% sur achat B&S (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "7.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA 7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "Switzerland VAT Form: grid 400" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "TVA 7.7% sur achat B&S (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "7.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "TVA 7.7% sur invest. et autres ch. (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "7.7% invest." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Switzerland VAT Form: grid 405" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "7.7% invest. Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "TVA 3.7% sur achat B&S (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "3.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA 3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "TVA 3.7% sur achat B&S (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "3.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "TVA 3.7% sur invest. et autres ch. (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "3.7% invest" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "3.7% invest Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +msgid "TVA due a 7.7% (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "" +"Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA due à 7.7% (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +msgid "TVA due à 3.7% (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "" +"Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA due a 3.7% (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:139 +msgid "" +"If you have questions or remarks, please contact our support using " +"odoo.com/help." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:143 +msgid "" +"Don't forget to update your fiscal positions. If you have a version 11.1 (or" +" higher), there is nothing to do. Otherwise, you will also have to update " +"your fiscal positions accordingly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:3 +msgid "Thailand" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:8 +msgid "" +":ref:`Install ` the :guilabel:`🇹🇭 Thailand` localization " +"package to get all the features of the Thai localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:17 +msgid ":guilabel:`Thailand - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:18 +msgid "`l10n_th`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:20 +msgid ":guilabel:`Thailand - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:21 +msgid "`l10n_th_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:22 +msgid "Country-specific accounting reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Thailand localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:30 +msgid "" +"Odoo's fiscal localization package for Thailand includes the following " +"taxes:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:32 +msgid "VAT 7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:33 +msgid "VAT-exempted" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:34 +msgid "Withholding tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:35 +msgid "Withholding income tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:40 +msgid "" +"Odoo allows users to generate Excel files to submit their VAT to the " +"**Revenue Department** of Thailand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:44 +msgid "Sales and purchase tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:46 +msgid "" +"To generate a sales and purchase tax report, go to " +":menuselection:`Accounting --> Reporting --> Tax Report`. Select a specific " +"time or time range on the tax report, and click :guilabel:`VAT-202-01 " +"(xlsx)` for purchase tax and :guilabel:`VAT-202-02 (xlsx)` for sales tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Thai purchase and sales taxes reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:54 +msgid "Withholding PND tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:56 +msgid "" +"PND report data displays the summarized amounts of the applicable " +"**withholding corporate income tax returns (domestic)** from vendor bills " +"under the :guilabel:`PND53 (TH)` and :guilabel:`PND3 (TH)` tax reports. It " +"is installed by default with the Thai localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PND tax reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:64 +msgid "" +"Withholding corporate income tax returns (domestic) is the tax used in case " +"the company has withheld the tax from “**Personal (PND3)**” or “**Corporate " +"(PND53)**” services provided such as rental, hiring, transportation, " +"insurance, management fee, consulting, etc." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:68 +msgid "" +"The PND tax report allows users to generate a CSV file for bills to upload " +"on the `RDprep for Thailand e-Filling application " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:71 +msgid "" +"To generate a PND CSV file, go to :menuselection:`Accounting --> Reporting " +"--> Tax Report`, select a specific time or time range on the tax report, and" +" click :guilabel:`PND3` or :guilabel:`PND53`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:74 +msgid "" +"This generates the :file:`Tax Report PND3.csv` and :file:`Tax Report " +"PND53.csv` files that lists all the vendor bill lines with the applicable " +"withholding tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PND3 and PND53 CSV files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:81 +msgid "" +"Odoo cannot generate the PND or PDF report or **withholding tax " +"certificate** directly. The generated :file:`Tax Report PND3.csv` and " +":file:`Tax Report PND53.csv` files must be exported to an external tool to " +"convert them into a **withholding PND** report or a **PDF** file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:86 +msgid "Tax invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:88 +msgid "" +"The **tax invoice PDF** report can be generated from Odoo through the " +"**Invoicing** module. Users have the option to print PDF reports for normal" +" invoices and tax invoices. To print out **tax invoices**, users can click " +"on :guilabel:`Print Invoices` in Odoo. Regular invoices can be printed as " +"**commercial invoices** by clicking on :menuselection:`Cog button (⚙️) --> " +"Print --> Commercial Invoice`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Commercial invoice printing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:98 +msgid "Headquarter/Branch number settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:100 +msgid "" +"You can inform a company's **Headquarters** and **Branch number** in the " +"**Contacts** app. Once in the app, open the **contact form** of the company " +"and under the :guilabel:`Sales & Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:103 +msgid "" +"If the contact is identified as a branch, input the **Branch number** in the" +" :guilabel:`Company ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:105 +msgid "" +"If the contact is a **Headquarters**, leave the :guilabel:`Company ID` field" +" **blank**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Company Headquarter/Branch number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:111 +msgid "" +"This information is used in the **tax invoice** PDF report and PND **tax " +"report** export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:114 +msgid "PromptPay QR code on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:116 +msgid "" +"The **PromptPay QR code** is a QR code that can be added to invoices to " +"allow customers to pay their bills using the PromptPay-supported bank mobile" +" application. The QR code is generated based on the **invoice amount** and " +"one of the following **merchant information**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:120 +msgid "Ewallet ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:121 +msgid "Merchant Tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:122 +msgid "Mobile Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:131 +msgid "PromptPay QR bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:133 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate PromptPay QR. Set the" +" :guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the chosen type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:138 +msgid "" +"The :guilabel:`Include Reference` checkbox doesn't work for PromptPay QR " +"codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PromptPay bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:149 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Journals`, open the " +"bank journal, then fill in the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:156 +msgid "Issue invoices with PromptPay QR code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:158 +msgid "" +"When creating a new invoice, open the :guilabel:`Other Info` tab and set the" +" :guilabel:`Payment QR-code` option to :guilabel:`EMV Merchant-Presented QR-" +"code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:164 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the PromptPay QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:10 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:19 +msgid ":guilabel:`United Arab Emirates - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:20 +msgid "``l10n_ae``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:21 +msgid "" +"Default :doc:`fiscal localization package " +"`. Includes all accounts, taxes," +" and reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`U.A.E. - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:24 +msgid "``l10n_ae_hr_payroll``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`U.A.E. - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:27 +msgid "``l10n_ae_hr_payroll_account``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:29 +msgid ":guilabel:`United Arab Emirates - Point of Sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:30 +msgid "``l10n_ae_pos``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:31 +msgid "Includes the UAE-compliant POS receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the modules to install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:40 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Chart of Accounts` to" +" view all default accounts available for the UAE localization package. You " +"can filter by :guilabel:`Code` using the numbers on the far left or by " +"clicking on :menuselection:`Group By --> Account Type`. You can " +":guilabel:`Enable`/:guilabel:`Disable` reconciliation or **configure** " +"specific accounts according to your needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:47 +msgid "" +"Always keep at least one **receivable account** and one **payable account** " +"active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:48 +msgid "" +"It is also advised to **keep the accounts below active**, as they are used " +"either as transitory accounts by Odoo or are specific to the **UAE " +"localization package**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:55 +msgid "Account Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:57 +msgid "102011" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:60 +msgid "102012" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:61 +msgid "Accounts Receivable (POS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:63 +msgid "201002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:64 +msgid "Payables" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:66 +msgid "101004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:69 +msgid "105001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:70 +msgid "Cash" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:72 +msgid "100001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:73 +msgid "Liquidity Transfer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:75 +msgid "101002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:78 +msgid "101003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:79 +msgid "Outstanding Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:81 +msgid "104041" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:82 +msgid "VAT Input" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:84 +msgid "100103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:85 +msgid "VAT Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:87 +msgid "101001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:88 +msgid "Bank Suspense Account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:90 +msgid "201017" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:91 +msgid "VAT Output" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:93 +msgid "202001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:94 +msgid "End of Service Provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:96 +msgid "202003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:97 +msgid "VAT Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:99 +msgid "999999" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:100 +msgid "Undistributed Profits/Losses" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:102 +msgid "400003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:103 +msgid "Basic Salary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:105 +msgid "400004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:106 +msgid "Housing Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:108 +msgid "400005" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:109 +msgid "Transportation Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:111 +msgid "400008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:112 +msgid "End of Service Indemnity" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:118 +msgid "" +"To access your taxes, go to :menuselection:`Accounting --> Configuration -->" +" Taxes`. Activate/deactivate, or :doc:`configure " +"` the taxes relevant to your " +"business by clicking on them. Remember to only set tax accounts on the " +"**5%** tax group, as other groups do not need closing. To do so, enable the " +":doc:`developer mode <../../general/developer_mode>` and go to " +":menuselection:`Configuration --> Tax Groups`. Then, set a :guilabel:`Tax " +"current account (payable)`, :guilabel:`Tax current account (receivable)`, " +"and an :guilabel:`Advance Tax payment account` for the **5%** group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:127 +msgid "The :abbr:`RCM (Reverse Charge Mechanism)` is supported by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Preview of the UAE localization package's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:134 +msgid "Currency exchange rates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:136 +msgid "" +"To update the currency exchange rates, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies`. Click on the update button " +"(:guilabel:`🗘`) found next to the :guilabel:`Next Run` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:140 +msgid "" +"To launch the update automatically at set intervals, change the " +":guilabel:`Interval` from :guilabel:`Manually` to the desired frequency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:144 +msgid "" +"By default, the UAE Central Bank exchange rates web service is used. Several" +" other providers are available under the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:152 +msgid "" +"The :guilabel:`UAE - Payroll` module creates the necessary **salary rules** " +"in the Payroll app in compliance with the UAE rules and regulations. The " +"salary rules are linked to the corresponding accounts in the **chart of " +"accounts**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "The UAE Employee Payroll Structure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:161 +msgid "Salary rules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:163 +msgid "" +"To apply these rules to an employee's contract, go to " +":menuselection:`Payroll --> Contracts --> Contracts` and select the " +"employee's contract. In the :guilabel:`Salary Structure Type` field, select " +":guilabel:`UAE Employee`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the Salary Structure Type to apply to the contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:171 +msgid "" +"Under the :guilabel:`Salary Information` tab, you can find details such as " +"the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:173 +msgid ":guilabel:`Wage`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:174 +msgid ":guilabel:`Housing Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:175 +msgid ":guilabel:`Transportation Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:176 +msgid ":guilabel:`Other Allowances`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:177 +msgid "" +":guilabel:`Number of Days`: used to calculate the :ref:`end of service " +"provision `." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:181 +msgid "" +"**Leave deductions** are calculated using a salary rule linked to the " +"**unpaid leave** time-off type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:183 +msgid "" +"Any other deductions or reimbursements are made *manually* using other " +"inputs;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:184 +msgid "" +"**Overtimes** are added *manually* by going to :menuselection:`Work Entries " +"--> Work Entries`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:185 +msgid "" +"**Salary attachments** are generated by going to :menuselection:`Contracts " +"--> Salary Attachments`. Then, :guilabel:`Create` an attachment and select " +"the :guilabel:`Employee` and the :guilabel:`Type (Attachment of Salary, " +"Assignment of Salary, Child Support)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:190 +msgid "" +"To prevent a rule from appearing on a paycheck, go to " +":menuselection:`Payroll --> Configuration --> Rules`. Click on " +":guilabel:`UAE Employee Payroll Structure`, select the rule to hide, and " +"uncheck :guilabel:`Appears on Payslip`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:197 +msgid "End of service provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:199 +msgid "" +"The provision is defined as the total monthly allowance *divided* by 30 and " +"then *multiplied* by the number of days set in the field :guilabel:`Number " +"of days` at the bottom of a contract's form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:202 +msgid "" +"The provision is then calculated via a salary rule associated with two " +"accounts: the **End Of Service Indemnity (Expense account)** and the **End " +"of Service Provision (Non-current Liabilities account)**. The latter is used" +" to pay off the **end of service amount** by settling it with the **payables" +" account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:208 +msgid "" +"The end of service amount is calculated based on the gross salary and the " +"start and end dates of the employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:214 +msgid "" +"The UAE localization package allows the generation of invoices in English, " +"Arabic, or both. The localization also includes a line to display the **VAT " +"amount** per line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:3 +msgid "United Kingdom" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:8 +msgid "" +":ref:`Install ` the :guilabel:`UK - Accounting` and the " +":guilabel:`UK - Accounting Reports` modules to get all the features of the " +"UK localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 +msgid ":guilabel:`UK - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 +msgid "`l10n_uk`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 +msgid "CT600-ready chart of accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 +msgid "VAT100-ready tax structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 +msgid "Infologic UK counties listing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 +msgid ":guilabel:`UK - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 +msgid "`l10n_uk_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 +msgid "Accounting reports for the UK" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 +msgid "Allows sending the tax report via the MTD-VAT API to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst-1 +msgid "Odoo uk packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:32 +msgid "Only UK-based companies can submit reports to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:33 +msgid "" +"Installing the module :guilabel:`UK - Accounting Reports` installs all two " +"modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:36 +msgid "" +"`HM Revenue & Customs `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 +msgid "" +"`Overview of Making Tax Digital " +"`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:43 +msgid "" +"The UK chart of accounts is included in the :guilabel:`UK - Accounting` " +"module. Go to :menuselection:`Accounting --> Configuration --> Accounting: " +"Chart of Accounts` to access it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:46 +msgid "" +"Setup your :abbr:`CoA (chart of accounts)` by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Import section` and choose to :guilabel:`Review Manually` or " +":guilabel:`Import (recommended)` your initial balances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:53 +msgid "" +"As part of the localization module, UK taxes are created automatically with " +"their related financial accounts and configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:56 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` " +"to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return " +"Periodicity` or to :guilabel:`Configure your tax accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:60 +msgid "" +"To edit existing taxes or to :guilabel:`Create` a new tax, go to " +":menuselection:`Accounting --> Configuration --> Accounting: Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:64 +msgid ":doc:`taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 +msgid "" +"Tutorial: `Tax report and return `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:69 +msgid "Making Tax Digital (MTD)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:71 +msgid "" +"In the UK, all VAT-registered businesses have to follow the MTD rules by " +"using software to submit their VAT returns." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:74 +msgid "" +"The **UK - Accounting Reports** module enables you to comply with the `HM " +"Revenue & Customs `_ requirements regarding `Making Tax Digital " +"`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:80 +msgid "" +"If your periodic submission is more than three months late, it is no longer " +"possible to submit it through Odoo, as Odoo only retrieves open bonds from " +"the last three months. Your submission has to be done manually by contacting" +" HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:87 +msgid "Register your company to HMRC before the first submission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:89 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on " +":guilabel:`Connect to HMRC`. Enter your company information on the HMRC " +"platform. You only need to do it once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 +msgid "Periodic submission to HMRC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:99 +msgid "" +"Import your obligations HMRC, filter on the period you want to submit, and " +"send your tax report by clicking :guilabel:`Send to HMRC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:103 +msgid "Periodic submission to HMRC for multi-company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:105 +msgid "" +"Only one company and one user can connect to HMRC simultaneously. If several" +" UK-based companies are on the same database, the user who submits the HMRC " +"report must follow these instructions before each submission:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:109 +msgid "Log into the company for which the submission has to be done." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:110 +msgid "" +"Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, " +"click :guilabel:`Manage Users`. Select the user who is connected to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:112 +msgid "" +"Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset " +"Authentication Credentials` or :guilabel:`Remove Authentication Credentials`" +" button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:114 +msgid "" +"You can now :ref:`register your company to HMRC ` and submit the tax report for this company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 +msgid "Repeat the steps for other companies' HMRC submissions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:119 +msgid "" +"During this process, the :guilabel:`Connect to HMRC` button no longer " +"appears for other UK-based companies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:3 +msgid "Vietnam" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:6 +msgid "Add Vietnamese QR banking codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:8 +msgid "" +"Vietnamese QR banking is a payment service platform that allows customers to" +" make instant domestic payments to individuals and merchants in Vietnamese " +"dong via online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:18 +msgid "Vietnamese QR banking bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:20 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate Vietnamese QR " +"banking. Set the :guilabel:`Bank Identifier Code` on the bank. Then set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:26 +msgid "" +"The account holder's country must be set to Vietnam on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:46 +msgid "Issue invoices with Vietnamese QR banking QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:54 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the Vietnamese QR banking QR code." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:5 +msgid "Payment providers (credit cards, online payments)" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:27 +msgid "" +"Odoo embeds several **payment providers** that allow your customers to pay " +"on their *Customer Portals* or your *eCommerce website*. They can pay sales " +"orders, invoices, or subscriptions with recurring payments with their " +"favorite payment methods such as **Credit Cards**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:31 +msgid "" +"Offering several payment methods increases the chances of getting paid in " +"time, or even immediately, as you make it more convenient for your customers" +" to pay with the payment method they prefer and trust." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "" +"Pay online in the customer portal and select which payment provider to use." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:40 +msgid "" +"Odoo apps delegate the handling of sensitive information to the certified " +"payment provider so that you don't ever have to worry about PCI compliance." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:43 +msgid "" +"This means that no sensitive information (such as credit card numbers) is " +"stored on Odoo servers or Odoo databases hosted elsewhere. Instead, Odoo " +"apps use a unique reference number to the data stored safely in the payment " +"providers' systems." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:50 +msgid "Supported payment providers" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:52 +msgid "" +"From an accounting perspective, we can distinguish two types of payment " +"providers: the payment providers that are third-party services and require " +"you to follow another accounting workflow, and the payments that go directly" +" on the bank account and follow the usual reconciliation workflow." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:59 +msgid "Online payment providers" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:67 +msgid "Payment flow from" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:68 +msgid ":ref:`Tokenization `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:69 +msgid ":ref:`Manual capture `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:70 +msgid ":ref:`Refunds `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:71 +msgid ":ref:`Express checkout `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:72 +msgid ":doc:`Adyen `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:73 +#: ../../content/applications/finance/payment_providers.rst:91 +#: ../../content/applications/finance/payment_providers.rst:127 +#: ../../content/applications/finance/payment_providers.rst:139 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:74 +#: ../../content/applications/finance/payment_providers.rst:92 +#: ../../content/applications/finance/payment_providers.rst:104 +#: ../../content/applications/finance/payment_providers.rst:128 +#: ../../content/applications/finance/payment_providers.rst:140 +#: ../../content/applications/finance/payment_providers.rst:143 +msgid "|V|" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:75 +#: ../../content/applications/finance/payment_providers.rst:76 +#: ../../content/applications/finance/payment_providers.rst:130 +#: ../../content/applications/finance/payment_providers.rst:142 +msgid "Full and partial" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:78 +msgid "" +":doc:`Amazon Payment Services `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:79 +#: ../../content/applications/finance/payment_providers.rst:85 +#: ../../content/applications/finance/payment_providers.rst:97 +#: ../../content/applications/finance/payment_providers.rst:103 +#: ../../content/applications/finance/payment_providers.rst:109 +#: ../../content/applications/finance/payment_providers.rst:115 +#: ../../content/applications/finance/payment_providers.rst:121 +#: ../../content/applications/finance/payment_providers.rst:133 +msgid "The provider website" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:84 +msgid ":doc:`AsiaPay `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:90 +msgid ":doc:`Authorize.Net `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:93 +#: ../../content/applications/finance/payment_providers.rst:94 +#: ../../content/applications/finance/payment_providers.rst:129 +#: ../../content/applications/finance/payment_providers.rst:141 +msgid "Full only" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:96 +msgid ":doc:`Buckaroo `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:102 +msgid ":doc:`Flutterwave `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:108 +msgid ":doc:`Mercado Pago `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:114 +msgid ":doc:`Mollie `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:120 +msgid ":doc:`PayPal `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:126 +msgid ":doc:`Razorpay `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:132 +msgid ":doc:`SIPS `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:138 +msgid ":doc:`Stripe `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:148 +msgid "" +"Some of these online payment providers can also be added as :doc:`bank " +"accounts <../finance/accounting/bank>`, but this is **not** the same process" +" as adding them as payment providers. Payment providers allow customers to " +"pay online, and bank accounts are added and configured on your Accounting " +"app to do a bank reconciliation, which is an accounting control process." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:155 +msgid "" +"In addition to the regular payment providers that integrate with an API such" +" as Stripe, PayPal, or Adyen, Odoo bundles the :doc:`Demo payment provider " +"`. This payment provider allows you to make demo " +"payments to test business flows involving online payments. No credentials " +"are required as the demo payments are fake." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:163 +msgid "Bank payments" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid ":doc:`Wire Transfer `" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid "" +"When selected, Odoo displays your payment information with a payment " +"reference. You have to approve the payment manually once you have received " +"it on your bank account." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid ":doc:`SEPA Direct Debit <../finance/accounting/payments/batch_sdd>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid "" +"Your customers can make a bank transfer to register a SEPA Direct Debit " +"mandate and get their bank account charged directly." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:177 +msgid "" +"Some payment providers support additional features for the payment flow. " +"Refer to the :ref:`table above ` to " +"check if your payment provider supports these features." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:184 +msgid "Tokenization" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:186 +msgid "" +"If your payment provider supports this feature, customers can choose to save" +" their card for later. A **payment token** is created in Odoo and can be " +"used as a payment method for subsequent payments without having to enter the" +" card details again. This is particularly useful for the eCommerce " +"conversion rate and for subscriptions that use recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:191 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Allow Saving Payment " +"Methods` checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:195 +msgid "" +"You remain fully PCI-compliant when you enable this feature because Odoo " +"does not store the card details directly. Instead, it creates a payment " +"token that only holds a reference to the card details stored on the payment " +"provider's server." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:202 +msgid "Manual capture" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:204 +msgid "" +"If your payment provider supports this feature, you can authorize and " +"capture payments in two steps instead of one. When you authorize a payment, " +"the funds are reserved on the customer's payment method but they are not " +"immediately charged. The charge is only made when you manually capture the " +"payment later on. You can also void the authorization to release the " +"reserved funds; this is equivalent to a regular cancellation. Capturing " +"payments manually can prove itself useful in many situations:" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:211 +msgid "" +"Receive the payment confirmation and wait until the order is shipped to " +"capture the payment." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:212 +msgid "" +"Review and verify that orders are legitimate before the payment is completed" +" and the fulfillment process starts." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:214 +msgid "" +"Avoid potentially high processing fees for cancelled payments: payment " +"providers will not charge you for voiding an authorization." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:216 +msgid "" +"Hold a security deposit to return later, minus any deductions (e.g., after a" +" damage)." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:218 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Capture Amount Manually`" +" checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:221 +msgid "" +"To capture the payment after it was authorized, go to the related sales " +"order or invoice and click on the :guilabel:`CAPTURE TRANSACTION` button. To" +" release the funds, click on the :guilabel:`VOID TRANSACTION` button." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:225 +msgid "" +"If your provider supports partial capture, you can select to capture only a " +"**partial amount** of the full amount. The **remaining (uncaptured) amount**" +" can either be voided or partially captured again later." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:230 +msgid "" +"Some payment providers support capturing only part of the authorized amount." +" The remaining amount can then be either captured or voided. These providers" +" have the value **Full and partial** in the :ref:`table above " +"`. The providers that only support " +"capturing or voiding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:234 +msgid "" +"The funds are likely not reserved forever. After a certain time, they may be" +" automatically released back to the customer's payment method. Refer to your" +" payment provider's documentation for the exact reservation duration." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:237 +msgid "" +"Odoo does not support this feature for all payment providers but some allow " +"the manual capture from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:243 +msgid "Refunds" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:245 +msgid "" +"If your payment provider supports this feature, you can refund payments " +"directly from Odoo. It does not need to be enabled first. To refund a " +"customer payment, navigate to it and click on the :guilabel:`REFUND` button." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:250 +msgid "" +"Some payment providers support refunding only part of the amount. The " +"remaining amount can then optionally be refunded too. These providers have " +"the value **Full and partial** in the :ref:`table above " +"`. The providers that only support " +"refunding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:254 +msgid "" +"Odoo does not support this feature for all payment providers but some allow " +"to refund payments from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:260 +msgid "Express checkout" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:262 +msgid "" +"If your payment provider supports this feature, customers can use the " +"**Google Pay** and **Apple Pay** buttons to pay their eCommerce orders in " +"one click without filling the contact form. Using one of those buttons, " +"customers go straight from the cart to the confirmation page, stopping by " +"the payment form of Google or Apple to validate the payment." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:267 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Allow Express Checkout` " +"checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:271 +msgid "" +"All prices shown in the express checkout payment form are always taxes " +"included." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:279 +msgid "" +"Each provider has its specific configuration flow, depending on :ref:`which " +"feature is available `." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:285 +msgid "Add a new payment provider" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:287 +msgid "" +"To add a new payment provider and make it available to your customers, go to" +" :menuselection:`Accounting --> Configuration --> Payment Providers`, look " +"for your payment provider, install the related module, and activate it. To " +"do so, open the payment provider and change its state from *Disabled* to " +"*Enabled*." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "" +"Click on install, then on activate to make the payment provider available on" +" Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:297 +msgid "" +"We recommend using the *Test Mode* on a duplicated database or a test " +"database. The Test Mode is meant to be used with your test/sandbox " +"credentials, but Odoo generates Sales Orders and Invoices as usual. It isn't" +" always possible to cancel an invoice, and this could create some issues " +"with your invoices numbering if you were to test your payment providers on " +"your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:305 +#: ../../content/applications/finance/payment_providers/adyen.rst:25 +#: ../../content/applications/finance/payment_providers/alipay.rst:18 +#: ../../content/applications/finance/payment_providers/authorize.rst:15 +#: ../../content/applications/finance/payment_providers/mollie.rst:14 +#: ../../content/applications/finance/payment_providers/sips.rst:15 +msgid "Credentials tab" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:307 +msgid "" +"If not done yet, go to the online payment provider website, create an " +"account, and make sure to have the credentials required for third-party use." +" Odoo requires these credentials to communicate with the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:311 +msgid "" +"The form in this section is specific to the payment provider you are " +"configuring. Please refer to the related documentation for more information." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:317 +#: ../../content/applications/finance/payment_providers/authorize.rst:38 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:319 +msgid "" +"You can change the payment provider's front-end appearance by modifying its " +"name under the **Displayed as** field, and the supported credit card icons " +"displayed under the **Supported Payment Methods** field." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:326 +msgid "Currencies" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:328 +msgid "" +"All payment providers have a different list of available currencies. They " +"are preconfigured and available in the :guilabel:`Configuration` tab. They " +"serve as a first filter during payment operations, i.e. the payment provider" +" is not displayed as available for payment if the currency is not in the " +"supported list." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:334 +msgid "" +"As there might be errors, updates, and unknowns in the lists of available " +"currencies, it is possible to add or remove currencies." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:337 +msgid "" +"If the list of supported currencies is empty, it either means the list is " +"too long to be displayed, or Odoo does not have information on that payment " +"provider. The payment provider remains available, even though it is possible" +" the payment will be refused at a later stage should the currency not be " +"supported. This field is required if the user needs to select a currency " +"when setting up their payment provider account." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:346 +msgid "Countries" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:348 +msgid "" +"Restrict the use of the payment provider to a selection of countries. Leave " +"this field blank to make the payment provider available in all countries." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:352 +msgid "Maximum Amount" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:354 +msgid "" +"Restrict the maximum amount that can be paid with the selected provider. " +"Leave this field to `0.00` to make the payment provider available regardless" +" of the payment amount." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:358 +msgid "" +"This feature is not intended to work on pages which allow the customer to " +"update the payment amount. For example, the **Donation** snippet of the " +"Website app, and the **Checkout** page of the **eCommerce** app when paid " +"delivery methods are enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:365 +msgid "Payment journal" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:367 +msgid "" +"The **Payment journal** selected for your payment provider must be a *Bank* " +"journal." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:372 +msgid "Publish on the website" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:374 +msgid "" +"By default, payment providers are *unpublished*, which means that only " +"internal users can see them on the website. Your customers cannot make " +"payments through an unpublished provider but they can still manage " +":dfn:`(delete and assign to a subscription)` their already existing tokens " +"linked to such an provider. This conveniently allows you to test an provider" +" while preventing making payments and registering new tokens." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:380 +msgid "" +"Click on the :guilabel:`Publish` button located in the top right corner of " +"the provider's form to publish it on the website and make it available to " +"your customers. Click on the :guilabel:`Unpublish` button to unpublish it." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:385 +msgid "" +"Payment providers are automatically published and unpublished when you " +"respectively change their state to `enabled` and `test`." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:391 +msgid "Accounting perspective" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:393 +msgid "" +"The **Bank Payments** that go directly to one of your bank accounts follow " +"their usual reconciliation workflows. However, payments recorded with " +"**Online Payment Providers** require you to consider how you want to record " +"your payments' journal entries. We recommend you to ask your accountant for " +"advice." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:398 +msgid "" +"You need to select a *Payment Journal* on your provider configuration to " +"record the payments, on a **Outstanding Account**. The Journal's **type** " +"must be *Bank Journal*." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:401 +msgid "" +"You can use a single journal for many payment methods. And for each payment " +"method, you can either:" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:403 +msgid "" +"Define an **Accounting Account** to separate these payments from another " +"payment method." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:404 +msgid "" +"Leave blank to fallback on the default account, which you can see or change " +"in the settings." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "A bank journal in the \"Incoming Payments Tab\"." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:410 +msgid "" +"You can have the same bank account for the whole company, or for some " +"journals only, or a single payment method... What best suit your needs." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:414 +msgid ":doc:`payment_providers/wire_transfer`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:415 +msgid ":doc:`payment_providers/adyen`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:416 +msgid ":doc:`payment_providers/alipay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:417 +msgid ":doc:`payment_providers/authorize`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:418 +msgid ":doc:`payment_providers/asiapay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:419 +msgid ":doc:`payment_providers/buckaroo`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:420 +msgid ":doc:`payment_providers/demo`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:421 +msgid ":doc:`payment_providers/mercado_pago`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:422 +msgid ":doc:`payment_providers/mollie`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:423 +msgid ":doc:`payment_providers/ogone`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:424 +msgid ":doc:`payment_providers/paypal`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:425 +msgid ":doc:`payment_providers/razorpay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:426 +msgid ":doc:`payment_providers/sips`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:427 +msgid ":doc:`payment_providers/stripe`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:428 +msgid ":doc:`../websites/ecommerce/checkout_payment_shipping/payments`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:3 +msgid "Adyen" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:5 +msgid "" +"`Adyen `_ is a Dutch company that offers several " +"online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:9 +#: ../../content/applications/finance/payment_providers/adyen.rst:20 +#: ../../content/applications/finance/payment_providers/alipay.rst:15 +#: ../../content/applications/finance/payment_providers/authorize.rst:12 +#: ../../content/applications/finance/payment_providers/demo.rst:12 +#: ../../content/applications/finance/payment_providers/mollie.rst:11 +#: ../../content/applications/finance/payment_providers/ogone.rst:9 +#: ../../content/applications/finance/payment_providers/paypal.rst:86 +#: ../../content/applications/finance/payment_providers/sips.rst:12 +#: ../../content/applications/finance/payment_providers/stripe.rst:12 +msgid ":ref:`payment_providers/add_new`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:10 +#: ../../content/applications/finance/payment_providers/adyen.rst:163 +#: ../../content/applications/finance/payment_providers/alipay.rst:39 +#: ../../content/applications/finance/payment_providers/asiapay.rst:50 +#: ../../content/applications/finance/payment_providers/authorize.rst:51 +#: ../../content/applications/finance/payment_providers/buckaroo.rst:37 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:44 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:39 +#: ../../content/applications/finance/payment_providers/mollie.rst:31 +#: ../../content/applications/finance/payment_providers/paypal.rst:121 +#: ../../content/applications/finance/payment_providers/razorpay.rst:54 +#: ../../content/applications/finance/payment_providers/sips.rst:32 +#: ../../content/applications/finance/payment_providers/stripe.rst:133 +msgid ":doc:`../payment_providers`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:13 +msgid "" +"Adyen works only with customers processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1.000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:22 +msgid "" +"First, reach Adyen support to enable :guilabel:`multiple partial capture` " +"for you." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:27 +msgid "" +"Odoo needs your **API Credentials** to connect with your Adyen account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:29 +msgid "" +"**Merchant Account**: The code of the merchant account to use with Adyen." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:30 +msgid "" +":ref:`API Key `: The API key of the webservice " +"user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:31 +msgid "" +":ref:`Client Key `: The client key of the " +"webservice user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:32 +msgid ":ref:`HMAC Key `: The HMAC key of the webhook." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:33 +msgid "" +":ref:`Checkout API URL `: The base URL for the Checkout API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:34 +msgid "" +":ref:`Recurring API URL `: The base URL for the Recurring API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:36 +msgid "" +"You can copy your credentials from your Adyen account, and paste them in the" +" related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:40 +msgid "" +"If you are trying Adyen as a test, with an Adyen *test account*, head to " +":menuselection:`Accounting --> Configuration --> Payment Providers`. There, " +"click on :guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your " +"credentials in the :guilabel:`Credentials` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:48 +msgid "API Key and Client Key" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:50 +msgid "" +"In order to retrieve the API Key and the Client Key, log into your Adyen " +"account, go to :menuselection:`Developers --> API Credentials`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:53 +msgid "If you already have an API user, open it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:54 +msgid "If you don't have an API user yet, click on **Create new credential**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:56 +msgid "" +"Go to :menuselection:`Server settings --> Authentification` and copy or " +"generate your **API Key**. Be careful to copy your API key as you'll not be " +"allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:60 +msgid "" +"Now, head to :menuselection:`Client settings --> Authentification` and cody " +"or generate your **Client Key**. This is also the place where you can " +":ref:`allow payments to be made from your website `." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:67 +msgid "HMAC key" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:69 +msgid "" +"In order to retrieve the HMAC Key, you'll need to configure a `Standard " +"Notification` webhook. For this, log into your Adyen account then go to " +":menuselection:`Developers --> Webhooks --> Add webhook --> Add Standard " +"notification`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Configure a webhook." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:77 +msgid "" +"There, in :menuselection:`General --> Server configuration --> URL`, enter " +"your server address followed by `/payment/adyen/notification`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Enter the notification URL." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:84 +msgid "" +"Then enter :menuselection:`Security --> HMAC Key --> Generate`. Be careful " +"to copy the key as you will not be allowed to do it later without generating" +" a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Generate a HMAC key and save it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:91 +msgid "You have to save the webhook to finalize its creation." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:96 +msgid "API URLs" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:98 +msgid "" +"All Adyen API URLs include a customer area-specific prefix generated by " +"Adyen. To configure the URLs, proceed as follows:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:101 +msgid "" +"Log into your Adyen account, then go to :menuselection:`Developers --> API " +"URLs`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:102 +msgid "" +"Copy the :guilabel:`Prefix` for your live Customer area (i.e., **data " +"center**) and save it for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:0 +msgid "Copy the prefix for the Adyen APIs" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:108 +msgid "" +"In Odoo, :ref:`navigate to the payment provider Adyen " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:109 +msgid "" +"In the :guilabel:`Checkout API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-checkout-live.adyenpayments.com/checkout`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:112 +msgid "" +"In the :guilabel:`Recurring API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-pal-live.adyenpayments.com/pal/servlet/Recurring`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:117 +msgid "" +"If you are trying Adyen as a test, you can use the following URLs instead:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:119 +msgid ":guilabel:`Checkout API URL`: `https://checkout-test.adyen.com`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:120 +msgid "" +":guilabel:`Recurring API URL`: `https://pal-" +"test.adyen.com/pal/servlet/Recurring`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:123 +msgid "Adyen Account" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:128 +msgid "Allow payments from a specific origin" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:130 +msgid "" +"To allow payment originated from your website, follow the steps in " +":ref:`adyen/api_and_client_keys` to navigate to your API user and go to " +":menuselection:`Add allowed origins`, then add the URLs from where payments " +"will be made (the URLs of the servers hosting your Odoo instances)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Allows payments originated from a specific domain." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:139 +#: ../../content/applications/finance/payment_providers/authorize.rst:41 +msgid "Place a hold on a card" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:141 +msgid "" +"Adyen allows you to capture an amount manually instead of having an " +"immediate capture." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:143 +msgid "" +"To set it up, enable the **Capture Amount Manually** option on Odoo, as " +"explained in the :ref:`payment providers documentation " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:146 +msgid "" +"Then, open your Adyen Merchant Account, go to :menuselection:`Account --> " +"Settings`, and set the **Capture Delay** to **manual**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Capture Delay settings in Adyen" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:154 +msgid "" +"If you configure Odoo to capture amounts manually, make sure to set the " +"**Capture Delay** to **manual** on Adyen. Otherwise, the transaction will be" +" blocked in the authorized state in Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:159 +msgid "" +"After **7 days**, if the transaction has not been captured yet, the customer" +" has the right to **revoke** it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:3 +msgid "Alipay" +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:5 +msgid "" +"`Alipay `_ is an online payments platform " +"established in China by Alibaba Group." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:9 +msgid "" +"The provider Alipay is deprecated. It is recommended to use :doc:`asiapay` " +"instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:20 +msgid "" +"Odoo needs your **API Credentials** to connect with your Alipay account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:22 +msgid "" +"**Account**: Depending on where you are situated - `Express Checkout` if " +"your are a Chinese Merchant. - `Cross-border` if you are not." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:25 +msgid "" +"**Alipay Seller Email**: Your public Alipay partner email (for express " +"checkout only)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:26 +msgid "" +"**Merchant Partner ID**: The public partner ID solely used to identify the " +"account with Alipay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:27 +msgid "**MD5 Signature Key**: The signature key." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:29 +msgid "" +"You can copy your credentials from your Alipay account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:32 +msgid "" +"To retrieve them, log into your Alipay account, they are on the front page." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:35 +msgid "" +"If you are trying Alipay as a test, in the *sandbox*, change the **State** " +"to *Test Mode*. We recommend doing this on a test Odoo database, rather than" +" on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:3 +msgid "Amazon Payment Services" +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:5 +msgid "" +"`Amazon Payment Services `_ or APS is " +"an online payment provider established in Dubai offering several online " +"payment options." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:11 +msgid "Configuration on APS Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:13 +msgid "" +"Log into your `Amazon Payment Services Dashboard " +"`_ and go to :menuselection:`Integration Settings" +" --> Security Settings`. Generate the :guilabel:`Access Code` if none has " +"been generated yet. Copy the values of the :guilabel:`Merchant Identifier`, " +":guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and :guilabel:`SHA " +"Response Phrase` fields, and save them for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:18 +msgid "" +"Enter your Odoo database URL in the :guilabel:`Origin URL`, for example: " +"`https://yourcompany.odoo.com/`. Then, click on :guilabel:`Save Changes`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:20 +msgid "" +"Navigate to :menuselection:`Integration Settings --> Technical Settings` and" +" click on :guilabel:`Redirection`. Make sure :guilabel:`Status` is set to " +"`Active` and select your preferred payment methods underneath in " +":guilabel:`Payment Options`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "" +"Set :guilabel:`Send Response Parameters` to :guilabel:`Yes` and enter your " +"database URL followed by `/payment/aps/return` in the :guilabel:`Redirection" +" URL`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "For example `https://yourcompany.odoo.com/payment/aps/return`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "" +"Enter your database URL followed by `/payment/aps/webhook` in the " +":guilabel:`Direct Transaction Feedback` and :guilabel:`Notification URL` " +"fields." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "For example `https://yourcompany.odoo.com/payment/aps/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "Click on :guilabel:`Save Changes`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:30 +msgid "" +"Under :menuselection:`Integration Settings --> Payment Page Template` you " +"can customize the look and feel of the Amazon Payment Services payment page " +"(where customers fill out their credit card details during payment)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:39 +msgid "" +":ref:`Navigate to the payment provider Amazon Payment Services " +"`, change its state to :guilabel:`Enabled`, and " +"make sure it is :guilabel:`Published`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:41 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant " +"Identifier`, :guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and " +":guilabel:`SHA Response Phrase` with the values you saved at the step " +":ref:`payment_providers/aps/configure-dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:44 +#: ../../content/applications/finance/payment_providers/asiapay.rst:47 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:36 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 +#: ../../content/applications/finance/payment_providers/razorpay.rst:44 +msgid "Configure the rest of the options to your liking." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:3 +msgid "AsiaPay" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:5 +msgid "" +"`AsiaPay `_ is an online payments provider " +"established in Hong Kong and covering several Asian countries and payment " +"methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:11 +msgid "Configuration on AsiaPay Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:13 +msgid "" +"Log into AsiaPay Dashboard according to the account provided by AsiaPay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:15 +msgid "" +"`PayDollar `_: For " +"markets in HK, CN, MO, TW, SG, MY, IN, VN, NZ and AU" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:17 +msgid "" +"`PesoPay `_: For market" +" in PH" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:18 +msgid "" +"`SiamPay `_: For market" +" in TH" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:19 +msgid "" +"`BimoPay `_: For market" +" in ID" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:21 +msgid "" +"Go to :menuselection:`Profile --> Account Information`. Copy the values of " +"the :guilabel:`Currency` and :guilabel:`Secure Hash` fields and save them " +"for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Go to :menuselection:`Profile --> Payment Account Settings` and enable the " +"option :guilabel:`Return Value Link (Datefeed)`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Enter your Odoo database URL followed by `/payment/asiapay/webhook` in the " +":guilabel:`Return Value Link (Datefeed)` text field. For example: " +"`https://yourcompany.odoo.com/payment/asiapay/webhook`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Click on :guilabel:`Test` to check if the webhook is working correctly." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:29 +msgid "Click on :guilabel:`Update` to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:36 +msgid "" +":ref:`Navigate to the payment provider AsiaPay ` " +"and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"In the :guilabel:`Credentials` tab, choose the :guilabel:`Brand` of your " +"Asiapay account. Then fill in the :guilabel:`Merchant ID` and " +":guilabel:`Secure Hash Secret`, and the :guilabel:`Currency` in the " +":guilabel:`Configuration` tab with the values you saved at the step " +":ref:`payment_providers/asiapay/configure_dashboard`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"By default, the payment provider AsiaPay is configured to verify the secret " +"hash with the hash function `SHA1`. If a different function is :ref:`set on " +"your account `, activate the " +":ref:`developer mode ` and set the same value to the field " +":guilabel:`Secure Hash Function` in the :guilabel:`Credentials` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:3 +msgid "Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:5 +msgid "" +"`Authorize.Net `_ is a United States-based online" +" payment solution provider, allowing businesses to accept **credit cards**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:17 +msgid "" +"Odoo needs your **API Credentials & Keys** to connect with your " +"Authorize.Net account, which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:20 +msgid "" +"**API Login ID**: The ID solely used to identify the account with " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:21 +msgid "**API Transaction Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:22 +msgid "**API Signature Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:23 +msgid "**API Client Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:25 +msgid "" +"To retrieve them, log into your Authorize.Net account, go to " +":menuselection:`Account --> Settings --> Security Settings --> API " +"Credentials & Keys`, generate your **Transaction Key** and **Signature " +"Key**, and paste them on the related fields in Odoo. Then, click on " +"**Generate Client Key**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:31 +msgid "" +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:34 +msgid "" +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:43 +msgid "" +"With Authorize.Net, you can enable the :ref:`manual capture " +"`. If enabled, the funds are " +"reserved for 30 days on the customer's card, but not charged yet." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:48 +msgid "" +"After **30 days**, the transaction is **voided automatically** by " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:54 +msgid "ACH payments (USA only)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:56 +msgid "" +":abbr:`ACH (automated clearing house)` is an electronic funds transfer " +"system used between bank accounts in the United States." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:62 +msgid "" +"To give customers the possibility to pay using ACH, `sign up for " +"Authorize.Net eCheck's service " +"`_. Once eCheck is " +"activated, duplicate the previously configured Authorize.Net payment " +"provider on Odoo by going to :menuselection:`Accounting --> Configuration " +"--> Payment Providers --> Authorize.net`. Then, click the cog icon " +"(:guilabel:`⛭`) and select :guilabel:`Duplicate`. Change the provider's name" +" to differentiate both versions (e.g., `Authorize.net - Banks`)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:69 +msgid "" +"Open the :guilabel:`Configuration` tab, set the :guilabel:`Allow Payments " +"From` field to :guilabel:`Bank Account (USA only)`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:72 +msgid "" +"When ready, change the provider's :guilabel:`State` to :guilabel:`Enabled` " +"for a regular account or :guilabel:`Test Mode` for a sandbox account." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:76 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:79 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:85 +msgid "" +"`Download the Excel import template " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:87 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:89 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:90 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:91 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:93 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template `." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:106 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:109 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:111 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:112 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:114 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:115 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:117 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:119 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template `. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:126 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:129 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:131 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:133 +msgid "Open the :ref:`Excel import template `." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:134 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:136 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:139 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:140 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:142 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template ` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:147 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template ` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:155 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:157 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:159 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:161 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:163 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:165 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:170 +msgid "" +"List of `eCheck.Net return codes " +"`_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:3 +msgid "Buckaroo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:5 +msgid "" +"`Buckaroo `_ is a Dutch-based company that offers " +"several online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:11 +msgid "Configuration on Buckaroo Plaza" +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:13 +msgid "" +"Log into `Buckaroo Plaza `_, go to " +":menuselection:`My Buckaroo --> Websites` and select the :guilabel:`Push " +"settings` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:15 +msgid "" +"Tick the :guilabel:`Enable Push Response` check box in the " +":guilabel:`Delayed and Push responses` section." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:17 +msgid "" +"Enter the URL of your Odoo database, followed by `/payment/buckaroo/webhook`" +" in both the :guilabel:`Push URI Success/Pending` and :guilabel:`Push URI " +"Failure` text fields. For example: " +"`https://yourcompany.odoo.com/payment/buckaroo/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:20 +msgid "Leave the other fields as they are and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:21 +msgid "" +"In the :guilabel:`General` tab, copy the website :guilabel:`Key` (i.e., the " +"key used to uniquely identify your website with Buckaroo) and save it for " +"later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:23 +msgid "" +"Go to :menuselection:`Configuration --> Security --> Secret key`, enter or " +":guilabel:`Generate` a :guilabel:`Secret key` and click :guilabel:`Save`. " +"Save the key for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:29 +msgid "" +":ref:`Navigate to the payment provider Buckaroo `" +" and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:31 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Website Key` and " +":guilabel:`Secret Key` fields with the values you saved at the step " +":ref:`payment_providers/buckaroo/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:34 +msgid "Configure the options in the other tabs to your liking." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:3 +msgid "Demo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:5 +msgid "" +"Odoo's **Demo Payment Provider** allows you to test business flows involving" +" online transactions without requiring real banking credentials." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:15 +msgid "Switch the state to :guilabel:`Test Mode`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:18 +msgid "Payment outcome" +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:20 +msgid "" +"Upon checkout or when paying a bill online, you can choose the payment " +"outcome when using the demo payment provider. To do so, click on the " +":guilabel:`Payment Status` drop-down menu and select the desired outcome." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst-1 +msgid "Payment status outcomes." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:29 +msgid "Transaction state" +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:31 +msgid "" +"If you selected :guilabel:`Pending` as **payment outcome**, you can change " +"the state of the transaction straight from its form view. To access a " +"transaction's form view, activate the :ref:`developer mode `, and go to :menuselection:`Accounting / Website --> Configuration -->" +" Payment Transactions`. Then, change the status of a transaction by clicking" +" on the state bar (:guilabel:`Draft, Pending, Authorized, Confirmed, " +"Canceled, Error`)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst-1 +msgid "Transaction's status bar." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:3 +msgid "Flutterwave" +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:5 +msgid "" +"`Flutterwave `_ is an online payments provider " +"established in Nigeria and covering several African countries and payment " +"methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:11 +msgid "Configuration on Flutterwave Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:13 +msgid "" +"Log into `Flutterwave Dashboard `_ and " +"go to :menuselection:`Settings --> API`. Copy the values of the " +":guilabel:`Public Key` and :guilabel:`Secret Key` fields and save them for " +"later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:0 +msgid "" +"Go to :menuselection:`Settings --> Webhooks` and enter your Odoo database " +"URL followed by `/payment/flutterwave/webhook` in the :guilabel:`URL` text " +"field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:0 +msgid "" +"For example: `https://yourcompany.odoo.com/payment/flutterwave/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:19 +msgid "" +"Fill the :guilabel:`Secret hash` with a password that you generate and save " +"its value for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:20 +msgid "Make sure *all* the remaining checkboxes are ticked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:21 +msgid "Click on **Save** to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst-1 +msgid "Flutterwave settings" +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:31 +msgid "" +":ref:`Navigate to the payment provider Flutterwave " +"` and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:33 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Public Key`, " +":guilabel:`Secret Key`, and :guilabel:`Webhook Secret` with the values you " +"saved at the step :ref:`payment_providers/flutterwave/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:39 +msgid "" +"If you choose to allow saving payment methods, it is recommended to only " +"enable card payments from Flutterwave dashboard, as only cards can be saved " +"as payment tokens. To do so, go to your Flutterwave Dashboard and then to " +":menuselection:`Settings --> Account Settings`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:3 +msgid "Mercado Pago" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:5 +msgid "" +"`Mercado Pago `_ is an online payment provider" +" covering several countries, currencies and payment methods in Latin " +"America." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:11 +msgid "Configuration on Mercado Pago Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:13 +msgid "" +"Log into the `Mercado Pago Dashboard " +"`_ and select your " +"application or create a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:15 +msgid "" +"Select :guilabel:`Credenciales de producción` in the left part of the " +"application page, then select the industry, optionally enter your domain, " +"and click :guilabel:`Activar credenciales de producción`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:18 +msgid "Copy the :guilabel:`Access token` and save it for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:21 +msgid "" +"If you are trying Mercado Pago as a test, select :guilabel:`Credienciales de" +" prueba` in the left part of the application page, then copy the test " +":guilabel:`Access token`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst-1 +msgid "Production and testing credentials in Mercado Pago." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:32 +msgid "" +":ref:`Navigate to the payment provider Mercado Pago " +"` and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:34 +msgid "" +"In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` " +"with the value you saved at the " +":ref:`payment_providers/mercado_pago/configure_dashboard` step." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:40 +msgid "" +"`Mercado Pago Odoo webinar `_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:3 +msgid "Mollie" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:5 +msgid "" +"`Mollie `_ is an online payments platform " +"established in the Netherlands." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:16 +msgid "" +"Odoo needs your **API Credentials** to connect with your Mollie account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:18 +msgid "" +"**API Key**: The test or live API Key depending on the configuration of the " +"provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:20 +msgid "" +"You can copy your credentials from your Mollie account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:23 +msgid "" +"To retrieve your API key, log into your Mollie account, go to " +":menuselection:`Developers --> API keys`, and copy your Test or Live **API " +"Key**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:27 +msgid "" +"If you are trying Mollie as a test, with the Test API key, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:3 +msgid "Ogone" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:5 +msgid "" +"`Ogone `_, also known as **Ingenico Payment " +"Services** is a France-based company that provides the technology involved " +"in secure electronic transactions." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:10 +msgid "" +"`Ogone's documentation `_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:13 +msgid "" +"The provider Ogone is deprecated. It is recommended to use :doc:`stripe` " +"instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:16 +msgid "Settings in Ogone" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:19 +msgid "Create an API user" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:21 +msgid "" +"Log into your Ogone account and head to the :guilabel:`Configuration` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:23 +msgid "" +"You need to create an **API user** to be used in the creation of " +"transactions from Odoo. While you can use your main account to do so, using " +"an **API user** ensures that if the credentials used in Odoo are leaked, no " +"access to your Ogone configuration is possible. Additionally, passwords for " +"**API users** do not need to be updated regularly, unlike normal users." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:28 +msgid "" +"To create an **API user**, go to :menuselection:`Configuration --> Users` " +"and click on :guilabel:`New User`. The following fields must be configured:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:33 +msgid ":guilabel:`UserID`: you can choose anything you want." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:34 +msgid "" +":guilabel:`User's Name, E-mail and Timezone`: you can enter the information " +"you want." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:35 +msgid ":guilabel:`Profile`: should be set to :guilabel:`Admin`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:36 +msgid ":guilabel:`Special user for API`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:38 +msgid "" +"After the creation of the user, you are required to generate a password. " +"Save the password and **UserID**, as they will be required later on during " +"the setup." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:42 +msgid "" +"If you already have an user set up, make sure it is activated without any " +"error. If not, simply click the :guilabel:`Activate(Errors)` button to reset" +" the user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:46 +msgid "Set up Ogone for Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:48 +msgid "" +"Ogone must now be configured to accept payments from Odoo. Head to " +":menuselection:`Configuration --> Technical Information --> Global Security " +"Parameters`, select :guilabel:`SHA-512` as :guilabel:`Hash Algorithm` and " +":guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the " +":guilabel:`Data and Origin verification` tab of the same page and leave the " +"URL field of the :guilabel:`e-Commerce and Alias Gateway` section blank." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:55 +msgid "" +"If you need to use another algorithm, such as `sha-1` or `sha-256`, within " +"Odoo, activate the :ref:`developer mode ` and go to the " +"**Payment Providers** page in :menuselection:`Accounting --> Configuration " +"--> Payment Providers`. Click on :guilabel:`Ogone`, and in the " +":guilabel:`Credentials` tab, select the algorithm you wish to use in the " +":guilabel:`Hash function` field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:61 +msgid "" +"You are now required to generate **SHA-IN** passphrases. **SHA-IN** and " +"**SHA-OUT** passphrases are used to digitally sign the transaction requests " +"and responses between Odoo and Ogone. By using these secret passphrases and " +"the `sha-1` algorithm, both systems can ensure that the information they " +"receive from the other was not altered or tampered with." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:66 +msgid "" +"Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for " +"e-Commerce & Alias Gateway` and :guilabel:`Checks for DirectLink and Batch " +"(Automatic)`. You can leave the IP address field blank." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:69 +msgid "" +"Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between" +" 16 and 32 characters long. Make sure to use the same **SHA-IN** and **SHA-" +"OUT** passphrases throughout the entire Ogone configuration, as Odoo only " +"allows a single **SHA-IN** and single **SHA-OUT** passphrase." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:73 +msgid "" +"In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to" +" :menuselection:`Configuration --> Technical Information --> Transaction " +"feedback --> All transaction submission modes`, and get or generate your " +"**API Key** and **Client Key**. Be careful to copy your API key as you’ll " +"not be allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:78 +msgid "" +"When done, head to :menuselection:`Configuration --> Technical Information " +"--> Transaction Feedback` and check the following options:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:81 +msgid "" +"The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` " +"can be left empty, as Odoo will specify these URLs for every transaction " +"request." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:83 +msgid "" +":guilabel:`I would like to receive transaction feedback parameters on the " +"redirection URLs`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:85 +msgid "" +":guilabel:`Direct HTTP server-to-server request`: should to be set to " +"`Online but switch to a deferred request when the online request fails`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:87 +msgid "" +"Both **URL** fields should contain the same following URL, with `` " +"replaced by your database: `https:///payment/ogone/return`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:90 +msgid "" +":guilabel:`Dynamic eCommerce Parameters` should contain the following " +"values: `ALIAS`, `AMOUNT`, `CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` " +"`ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other parameters can be " +"included (if you have another integration with Ogone that requires them), " +"but are not advised." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:94 +msgid "" +"In the :guilabel:`All transaction submission modes` section, fill out **SHA-" +"OUT** passphrase and disable `HTTP request for status change`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:97 +msgid "" +"To allow your customers to save their credit card credentials for future " +"use, head to :menuselection:`Configuration --> Alias --> My alias " +"information`. From this tab, you can configure how the user can have its " +"card details saved, for how long the information is saved, if a checkbox to " +"save the card information should be displayed, etc." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:103 +#: ../../content/applications/finance/payment_providers/paypal.rst:83 +msgid "Settings in Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:105 +msgid "" +"To set up Ogone in Odoo, head to :menuselection:`Accounting --> " +"Configuration --> Payment Providers` and open the Ogone provider. In the " +":guilabel:`Credentials` tab, enter the **PSPID** of your Ogone account, and " +"fill out the other fields as configured in your :ref:`Ogone portal " +"`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:3 +msgid "PayPal" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:5 +msgid "" +"`Paypal `_ is an American online payment provider " +"available worldwide, and one of the few that does not charge a subscription " +"fee." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:9 +msgid "" +"While PayPal is available in `over 200 countries/regions " +"`_, only `a selection " +"of currencies are supported " +"`_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:14 +msgid "Settings in PayPal" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:16 +msgid "" +"To access your PayPal account settings, log into PayPal, open the " +":guilabel:`Account Settings`, and open the :guilabel:`Website payments` " +"menu." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst-1 +msgid "PayPal account menu" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:24 +msgid "" +"Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return " +"` and :ref:`PDT ` **must** be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:30 +msgid "Auto Return" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:32 +msgid "" +"The **Auto Return** feature automatically redirects customers to Odoo once " +"the payment is processed." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:34 +msgid "" +"From :guilabel:`Website payments`, go to :menuselection:`Website preferences" +" --> Update --> Auto return for website payments --> Auto return` and select" +" :guilabel:`On`. Enter the address of your Odoo database (e.g., " +"`https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:40 +msgid "" +"Any URL does the job. Odoo only needs the setting to be enabled since it " +"uses another URL." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:45 +msgid "Payment Data Transfer (PDT)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:47 +msgid "" +":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations," +" displays the payment status to the customers, and verifies the authenticity" +" of the payments. From :menuselection:`Website preferences --> Update`, " +"scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:52 +msgid "" +"PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return " +"` and :ref:`Payment Data Transfer (PDT) ` " +"are enabled. If you need the **PDT Identity Token**, disable and re-enable " +":guilabel:`Payment data transfer` to display the token again." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:57 +msgid "PayPal Account Optional" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:59 +msgid "" +"We advise not to prompt customers to log in with a PayPal account upon " +"payment. It is better and more accessible for customers to pay with a " +"debit/credit card. To disable that prompt, go to :menuselection:`Account " +"Settings --> Website payments --> Update` and select :guilabel:`On` for " +":guilabel:`PayPal account optional`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:65 +msgid "Payment Messages Format" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:67 +msgid "" +"If you use accented characters (or anything other than primary Latin " +"characters) for customer names or addresses, then you **must** configure the" +" encoding format of the payment request sent by Odoo to PayPal. If you do " +"not, some transactions fail without notice." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:71 +msgid "" +"To do so, go to `your production account `_. Then, click " +":guilabel:`More Options` and set the two default encoding formats as " +":guilabel:`UTF-8`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:76 +msgid "" +"For Encrypted Website Payments & EWP_SETTINGS error, please check the " +"`Paypal documentation `_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:78 +msgid "" +"Configure your :ref:`Paypal Sandbox account `, then follow " +"this `link `_ to configure the " +"encoding format in a test environment." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:88 +msgid "" +"Odoo needs your **API Credentials** to connect with your PayPal account. To " +"do so, go to :menuselection:`Accounting --> Configuration --> Payment " +"Providers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account " +"credentials in the :guilabel:`Credentials` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:92 +msgid ":guilabel:`Email`: the login email address in Paypal;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:93 +msgid "" +":guilabel:`PDT Identity Token`: the key used to verify the authenticity of " +"transactions." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:98 +msgid "Test environment" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:103 +msgid "" +"Thanks to PayPal sandbox accounts, you can test the entire payment flow in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:105 +msgid "" +"Log into the `Paypal Developer Site `_ using " +"your PayPal credentials, which creates two sandbox accounts:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:108 +msgid "" +"A business account (to use as merchants, e.g., " +"`pp.merch01-facilitator@example.com " +"`_);" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:110 +msgid "" +"A default personal account (to use as shoppers, e.g., " +"`pp.merch01-buyer@example.com `_)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:113 +msgid "" +"Log into PayPal sandbox using the merchant account and follow the same " +"configuration instructions. Enter your sandbox credentials in Odoo " +"(:menuselection:`Accounting --> Configuration --> Payment Providers --> " +"PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set " +"on :guilabel:`Test Mode`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:118 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:3 +msgid "Razorpay" +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:5 +msgid "" +"`Razorpay `_ is an online payments provider " +"established in India and covering more than 100 payment methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:11 +msgid "Configuration on Razorpay Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:13 +msgid "" +"Log into `Razorpay Dashboard `_ and go to " +":menuselection:`Settings --> API Keys`. Generate the new keys and copy the " +"values of the :guilabel:`Key Id` and :guilabel:`Secret Key` fields and save " +"them for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:0 +msgid "" +"Go to :menuselection:`Settings --> Webhooks`, click on :guilabel:`Create New" +" Webhook`, and enter your Odoo database URL followed by " +"`/payment/razorpay/webhook` in the :guilabel:`Webhook URL` text field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:0 +msgid "For example: `https://example.odoo.com/payment/razorpay/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:20 +msgid "" +"Fill the :guilabel:`Secret` field with a password of your choice and save it" +" for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:21 +msgid "" +"Make sure the :guilabel:`payment.authorized`, :guilabel:`payment.captured`, " +":guilabel:`payment.failed`, :guilabel:`refund.failed` and " +":guilabel:`refund.processed` checkboxes are ticked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:24 +msgid "Click on :guilabel:`Create Webhook` to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:29 +msgid "" +"The :guilabel:`Recurring payments` feature must be activated if you want to " +"make recurring payments. Send a request to the `Razorpay Support team " +"`_ to enable recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:39 +msgid "" +":ref:`Navigate to the payment provider Razorpay `" +" and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:41 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Key Id`, " +":guilabel:`Key Secret`, and :guilabel:`Webhook Secret` with the values you " +"saved at the step :ref:`payment_providers/razorpay/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:47 +msgid "If you configure Odoo to capture amounts manually:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:49 +msgid "" +"Be aware that the **manual voiding** of a transaction is not supported by " +"Razorpay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:50 +msgid "" +"After **five days**, if the transaction hasn't been captured yet, it'll " +"automatically be **voided**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:3 +msgid "SIPS" +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:5 +msgid "" +"`SIPS `_ is an online payments solution from " +"the multinational Worldline." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:17 +msgid "" +"Odoo needs your **API Credentials** to connect with your SIPS account, which" +" comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:19 +msgid "" +"**Merchant ID**: The ID solely used to identify the merchant account with " +"SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:20 +msgid "**Secret Key**: The key to sign the merchant account with SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:21 +msgid "**Secret Key Version**: The version of the key, pre-filled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:22 +msgid "**Interface Version**: Pre-filled, don't change it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:24 +msgid "" +"You can copy your credentials from your SIPS environment info documentation," +" in the section **PROD**, and paste them in the related fields under the " +"**Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:28 +msgid "" +"If you are trying SIPS as a test, with the *TEST* credentials, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:3 +msgid "Stripe" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:5 +msgid "" +"`Stripe `_ is a United States-based online payment " +"solution provider, allowing businesses to accept **credit cards** and other " +"payment methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:9 +msgid "Link your Stripe Account with Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:14 +msgid "The method to acquire your credentials depends on your hosting type:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:19 +#: ../../content/applications/finance/payment_providers/stripe.rst:35 +msgid "" +"Go to the **eCommerce** or the **Sales** app and click on the *Activate " +"Stripe* or the *Set payments* button on the onboarding banner." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:21 +#: ../../content/applications/finance/payment_providers/stripe.rst:37 +msgid "Fill in the requested information and submit the form." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:22 +#: ../../content/applications/finance/payment_providers/stripe.rst:38 +msgid "Confirm your email address when Stripe sends you a confirmation email." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:23 +msgid "" +"At the end of the process, you are redirected to Odoo. If you submitted all " +"the requested information, you are all set and your payment provider is " +"enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:25 +msgid "Your can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:28 +msgid "" +"To use your own API keys, :ref:`activate the Developer mode ` and :ref:`enable Stripe manually `. You " +"can then :ref:`Fill in your credentials `, :ref:`generate a" +" webhook ` and enable the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:33 +msgid "Odoo.sh or On-premise" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:39 +msgid "" +"At the end of the process, you are redirected to the payment provider " +"**Stripe** on Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:40 +msgid ":ref:`Fill in your credentials `." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:41 +msgid ":ref:`Generate a webhook `." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:42 +msgid "Enable the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:43 +msgid "" +"You are all set and can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:46 +msgid "" +"To connect your Stripe account after the onboarding is already completed, go" +" to :menuselection:`Accounting --> Configuration --> Payment Providers --> " +"Stripe` and click on the *Connect Stripe* button." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:51 +msgid "" +"If you are testing Stripe (in **test mode**), change the **State** to *Test " +"Mode*. We recommend doing this on a test Odoo database rather than on your " +"main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:57 +msgid "Fill in your credentials" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:59 +msgid "" +"In case your **API Credentials** are required to connect with your Stripe " +"account, these are the credentials that must be completed:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:62 +msgid "" +":ref:`Publishable Key `: The key solely used to identify " +"the account with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:63 +msgid "" +":ref:`Secret Key `: The key to sign the merchant account " +"with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:64 +msgid "" +":ref:`Webhook Signing Secret `: When you enable your webhook" +" on your Stripe account, this signing secret must be set to authenticate the" +" messages sent from Stripe to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:67 +msgid "" +"To retrieve the publishable and secret keys, follow this `link to your API " +"keys `_, or log into your " +"Stripe dashboard and go to :menuselection:`Developers --> API Keys --> " +"Standard Keys`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:74 +msgid "Generate a webhook" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:76 +msgid "" +"In case your **Webhook Signing Secret** is required to connect with your " +"Stripe account, you can create a webhook either automatically or manually." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:80 +msgid "Create the webhook automatically" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:82 +msgid "" +"Make sure your :ref:`Publishable and Secret keys ` are " +"filled in, then click on the *Generate your Webhook* button." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:85 +msgid "Create the webhook manually" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:87 +msgid "" +"Visit the `webhooks page on Stripe " +"`_, or log into your Stripe dashboard" +" and go to :menuselection:`Developers --> Webhooks`. Then, click on **Add " +"endpoint** in your **Hosted endpoints** and insert the following data into " +"the pop-up form:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "In the **Endpoint URL**, enter your Odoo database's URL followed by" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "`/payment/stripe/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "For example: `https://yourcompany.odoo.com/payment/stripe/webhook`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:94 +msgid "" +"At the end of the form, you can **Select events** to listen to. Click on it " +"and, in the **Checkout** section, select **checkout.session.completed**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:98 +msgid "" +"It is possible to select other events, but they are currently not processed " +"by Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:100 +msgid "" +"When you click on **Add endpoint**, your Webhook is configured. You can then" +" click on **reveal** to display your signing secret." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:106 +msgid "Enable local payment methods" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:108 +msgid "" +"Local payment methods are payment methods that are only available for " +"certain merchants and customers countries and currencies." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:111 +msgid "Odoo supports the following local payment methods:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:113 +msgid "Bancontact" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:114 +msgid "EPS" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:115 +msgid "giropay" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:116 +msgid "iDEAL" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:117 +msgid "Przelewy24 (P24)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:119 +msgid "" +"To enable some of these local payment methods with Stripe, list them as " +"supported payment icons. To do so, go to :menuselection:`Payment Providers " +"--> Stripe --> Configuration` and add the desired payment methods in the " +"**Supported Payment Icons** field. If the desired payment method is already " +"listed, you do not have anything to do." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst-1 +msgid "Select and add icons of the payment methods you want to enable" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:128 +msgid "" +"If a payment method record does not exist in the database and its related " +"local payment method is listed above, it is considered enabled with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:130 +msgid "" +"If a local payment method is not listed above, it is not supported and " +"cannot be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:3 +msgid "Wire transfers" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:5 +msgid "" +"The **Wire transfer** payment method allows you to provide payment " +"instructions to your customers, such as the bank details and communication. " +"They are displayed:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:8 +msgid "" +"at the end of the checkout process, once the customer has selected " +":guilabel:`Wire transfer` as a payment method and clicked the :guilabel:`Pay" +" now` button:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:0 +msgid "Payment instructions at checkout" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:14 +msgid "on the customer portal:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:0 +msgid "Payment instructions on the customer portal" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:20 +msgid "" +"While this method is very accessible and requires minimal setup, it is very " +"inefficient process-wise. We recommend setting up a :doc:`payment provider " +"<../payment_providers>` instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:22 +msgid "" +"Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) " +"stage until you receive the payment and :guilabel:`Confirm` the order." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:26 +msgid "" +"**Wire transfer** can be used as a template for other payment methods that " +"are processed manually, such as checks, by renaming or duplicating it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:32 +msgid "" +"To configure **Wire Transfer**, go to :menuselection:`Accounting / Website " +"--> Configuration --> Payment Providers`, and open the :guilabel:`Wire " +"Transfer` card. Then, in the :guilabel:`Configuration` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:36 +msgid "Select the :guilabel:`Communication` to be used;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:38 +msgid ":guilabel:`Based on Document Reference`: sales order or invoice number" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:39 +msgid ":guilabel:`Based on Customer ID`: customer identifier" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:41 +msgid "" +"Tick the :guilabel:`Enable QR codes` check box to activate :doc:`QR code " +"payments <../accounting/customer_invoices/epc_qr_code>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:44 +msgid "Define the payment instructions in the :guilabel:`Messages` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst-1 +msgid "Define payment instructions" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:49 +msgid "" +"If you have already defined :doc:`a bank account <../accounting/bank>`, the " +"account number will be automatically added to the default message generated " +"by Odoo. You can also add it afterwards and update the message by clicking " +":guilabel:`Reload pending message`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:54 +msgid ":ref:`payment_providers/journal`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:3 +msgid "Sign" +msgstr "" + +#: ../../content/applications/finance/sign.rst:5 +msgid "" +"**Odoo Sign** allows you to send, sign, and approve documents online, using " +"electronic signatures." +msgstr "" + +#: ../../content/applications/finance/sign.rst:7 +msgid "" +"An **electronic signature** shows a person's agreement to the content of a " +"document. Just like a handwritten signature, the electronic one represents a" +" legal bounding by the terms of the signed document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:11 +msgid "" +"With Sign, you can upload any PDF file and add fields to it. These fields " +"can be automatically filled in with the user's details present in your " +"database." +msgstr "" + +#: ../../content/applications/finance/sign.rst:15 +msgid "`Odoo Sign: product page `_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:16 +msgid "`Odoo Tutorials: Sign [video] `_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:19 +msgid "Validity of electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:21 +msgid "" +"Documents signed via the Sign app are valid electronic signatures in the " +"European Union and the United States of America. They also meet the " +"requirements for electronic signatures in most countries. The legal validity" +" of electronic signatures generated by Odoo depends on your country's " +"legislation. Companies doing business abroad should also consider other " +"countries' electronic signature laws." +msgstr "" + +#: ../../content/applications/finance/sign.rst:28 +msgid "European Union" +msgstr "" + +#: ../../content/applications/finance/sign.rst:30 +msgid "" +"The `eIDAS regulation `_ " +"establishes the framework for electronic signatures in the `27 member states" +" of the European Union `_. It distinguishes three types of electronic signatures:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:35 +msgid "Simple electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:36 +msgid "Advanced electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:37 +msgid "Qualified electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:39 +msgid "" +"Odoo generates the first type, **simple electronic signatures**; these " +"signatures are legally valid in the EU, as stated in the eIDAS regulation." +msgstr "" + +#: ../../content/applications/finance/sign.rst:42 +msgid "" +"Electronic signatures may not be automatically recognized as valid. You may " +"need to bring supporting evidence of a signature's validity. While the Sign " +"app provides a simple electronic signature, some supporting evidence is " +"automatically collected during the signature process, such as:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:47 +msgid "Email and SMS validation (if enabled)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:48 +msgid "" +"Strong identity proof through itsme® (available in Belgium and the " +"Netherlands)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:49 +msgid "" +"Timestamped, IP and geographically traceable access logs to the documents " +"and their associated signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:51 +msgid "" +"Document traceability and inalterability (any alteration made to a signed " +"document is detected by Odoo with the use of cryptographic proofs)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:55 +msgid "United States of America" +msgstr "" + +#: ../../content/applications/finance/sign.rst:57 +msgid "" +"The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) " +"`_, at the " +"interstate and international levels, and the `UETA (Uniform Electronic " +"Transactions Act) `_," +" at the state level, provide the legal framework for electronic signatures. " +"Note that `Illinois " +"`_ and `New York " +"`_ have not " +"adopted the UETA, but similar acts instead." +msgstr "" + +#: ../../content/applications/finance/sign.rst:66 +msgid "" +"Overall, to be recognized as valid, electronic signatures have to meet five " +"criteria:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:68 +msgid "" +"The signer must show a clear **intent to sign**. For example, using a mouse " +"to draw a signature can show intent. The signer must also have the option to" +" opt out of the electronic document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:70 +msgid "" +"The signer must first express or imply their **consent to conduct business " +"electronically**." +msgstr "" + +#: ../../content/applications/finance/sign.rst:71 +msgid "" +"**The signature must be clearly attributed**. In Odoo, metadata, such as the" +" signer's IP address, is added to the signature, which can be used as " +"supporting evidence." +msgstr "" + +#: ../../content/applications/finance/sign.rst:73 +msgid "" +"**The signature must be associated with the signed document**, for example, " +"by keeping a record detailing how the signature was captured." +msgstr "" + +#: ../../content/applications/finance/sign.rst:75 +msgid "" +"Electronically signed documents need to be **retained and stored** by all " +"parties involved; for example, by providing the signer either a fully-" +"executed copy or the possibility to download a copy." +msgstr "" + +#: ../../content/applications/finance/sign.rst:80 +msgid "" +"The above information has no legal value; it is only provided for general " +"informational purposes. As laws governing electronic signatures rapidly " +"evolve, we cannot guarantee that all information is up-to-date. We advise " +"contacting a local attorney for legal advice regarding electronic signature " +"compliance and validity." +msgstr "" + +#: ../../content/applications/finance/sign.rst:86 +msgid "Send a document to sign" +msgstr "" + +#: ../../content/applications/finance/sign.rst:89 +msgid "One-time signature" +msgstr "" + +#: ../../content/applications/finance/sign.rst:91 +msgid "" +"You can click :guilabel:`Upload a PDF to sign` from your dashboard for a " +"one-time signature. Select your document, open it, and drag and drop the " +"required :ref:`fields ` in your document. You can modify the " +":ref:`role ` assigned to a field by clicking on it and selecting " +"the one you want." +msgstr "" + +#: ../../content/applications/finance/sign.rst:96 +msgid "" +"When ready, click :guilabel:`Send`, and fill in the required fields. Once " +"sent, your document remains available. Go to :menuselection:`Documents --> " +"All Documents` to see your document and the status of the signatures." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Signature status" +msgstr "" + +#: ../../content/applications/finance/sign.rst:104 +msgid "Validity dates and reminders" +msgstr "" + +#: ../../content/applications/finance/sign.rst:106 +msgid "" +"You can set **validity dates** on limited-duration agreement documents or " +"send **automatic email reminders** to obtain signatures on time. From your " +"dashboard, click :guilabel:`Send` on your document. On the new page, go to " +"the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and " +":guilabel:`Reminder` fields." +msgstr "" + +#: ../../content/applications/finance/sign.rst:112 +#: ../../content/applications/finance/spreadsheet/templates.rst:3 +msgid "Templates" +msgstr "" + +#: ../../content/applications/finance/sign.rst:114 +msgid "" +"You can create document templates when you have to send the same document " +"several times. From your dashboard, click :guilabel:`Upload a PDF template`." +" Select the document and add the required :ref:`fields `. You " +"can modify the :ref:`role ` of a field by clicking on it and " +"selecting the one you want." +msgstr "" + +#: ../../content/applications/finance/sign.rst:119 +msgid "" +"Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your " +"template, define a :guilabel:`Signed Document Workspace`, add " +":guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will " +"be available in the signature confirmation message received after the " +"signature, or define :guilabel:`Authorized Users` if you want to restrict " +"the use of your template to specific authorized users or groups." +msgstr "" + +#: ../../content/applications/finance/sign.rst:125 +msgid "" +"Your templates are visible by default on your dashboard. You can click " +":guilabel:`Send` to quickly send a document template to a signer or " +":guilabel:`Sign Now` if you are ready to sign your document immediately." +msgstr "" + +#: ../../content/applications/finance/sign.rst:130 +msgid "" +"You can **create a template from a document that was previously sent**. To " +"do so, go to :menuselection:`Documents --> All Documents`. On the document " +"you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), " +"then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) " +"again, then :guilabel:`Restore`. Your document now appears on your dashboard" +" next to your other templates." +msgstr "" + +#: ../../content/applications/finance/sign.rst:139 +msgid "Roles" +msgstr "" + +#: ../../content/applications/finance/sign.rst:141 +msgid "" +"Each field in a Sign document is related to a role corresponding to a " +"specific person. When a document is being signed, the person assigned to the" +" role must fill in their assigned fields and sign it." +msgstr "" + +#: ../../content/applications/finance/sign.rst:145 +msgid "" +"Roles are available by going to :menuselection:`Sign --> Configuration --> " +"Roles`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:147 +msgid "" +"It is possible to update existing roles or to create new roles by clicking " +"on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra " +"Authentication Step` to confirm the identity of the signing person, and if " +"the document can be reassigned to another contact, select :guilabel:`Change " +"Authorized` for the role. A :guilabel:`Color` can also be chosen for the " +"role. This color can help understand which roles are responsible for which " +"field when configuring a template." +msgstr "" + +#: ../../content/applications/finance/sign.rst:155 +msgid "Secured identification" +msgstr "" + +#: ../../content/applications/finance/sign.rst:157 +msgid "" +"As the owner of a document, you may request an :guilabel:`Extra " +"Authentication Step` through :ref:`SMS verification ` or via " +":ref:`Itsme® ` (available in Belgium and the Netherlands). Both " +"authentication options require :ref:`credits `. If you " +"do not have any credits left, the authentication steps will be skipped." +msgstr "" + +#: ../../content/applications/finance/sign.rst:163 +msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:164 +msgid "" +":doc:`SMS pricing and FAQ " +"<../marketing/sms_marketing/pricing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:169 +msgid "SMS verification" +msgstr "" + +#: ../../content/applications/finance/sign.rst:171 +msgid "" +"Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the " +":guilabel:`Extra Authentication Step` column for the role, and select " +":guilabel:`Unique Code Via SMS`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:175 +msgid "" +"Before being able to send SMS Text Messages, you need to register your phone" +" number. To do so, go to :menuselection:`Sign --> Configuration --> " +"Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by" +" SMS`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:179 +msgid "" +"Go to the document to sign, add the field for which the SMS verification is " +"required, for example, the :guilabel:`Signature` field, and click " +":guilabel:`Send`. On the new page, select the :guilabel:`customer` and click" +" :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:183 +msgid "" +"The person signing the document fills in the :guilabel:`Signature` field, " +"then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed " +"Document`. A :guilabel:`Final Validation` page pops up where to add their " +"phone number. One-time codes are sent by SMS." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Add a hash to your document" +msgstr "" + +#: ../../content/applications/finance/sign.rst:191 +msgid "This feature is enabled by default." +msgstr "" + +#: ../../content/applications/finance/sign.rst:192 +msgid "" +"As soon as the :guilabel:`Extra Authentication Step` applies to a role, this" +" validation step is requested for any field assigned to this role." +msgstr "" + +#: ../../content/applications/finance/sign.rst:198 +msgid "Itsme®" +msgstr "" + +#: ../../content/applications/finance/sign.rst:200 +msgid "" +"Itsme® authentication can be used to allow signatories to provide their " +"identity using itsme®. This feature is only available in **Belgium** and the" +" **Netherlands**." +msgstr "" + +#: ../../content/applications/finance/sign.rst:203 +msgid "" +"The feature can be enabled in :guilabel:`Sign Settings` and applies " +"automatically to the :guilabel:`Customer (identified with itsme®)` role. To " +"enable it for other roles, go to :menuselection:`Sign --> Configuration --> " +"Roles`. Click in the :guilabel:`Extra Authentication Step` column for the " +"role, and select :guilabel:`Via itsme®`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:208 +msgid "" +"Go to the document that needs to be signed and add the :guilabel:`Signature`" +" field. Switch to any role configured to use the feature, and click " +":guilabel:`Validate` and :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "select customer identified with itsme®" +msgstr "" + +#: ../../content/applications/finance/sign.rst:214 +msgid "" +"Upon signing the document, the signer completes the :guilabel:`Signature` " +"field and proceeds by clicking on :guilabel:`Validate & Send Completed " +"Document`, triggering a :guilabel:`Final verification` page where " +"authentication via itsme® is required." +msgstr "" + +#: ../../content/applications/finance/sign.rst:219 +msgid "Signatory hash" +msgstr "" + +#: ../../content/applications/finance/sign.rst:221 +msgid "" +"Each time someone signs a document, a **hash** - a unique digital signature " +"of the operation - is generated to ensure traceability, integrity, and " +"inalterability. This process guarantees that any changes made after a " +"signature is affixed can be easily detected, maintaining the document's " +"authenticity and security throughout its lifecycle." +msgstr "" + +#: ../../content/applications/finance/sign.rst:226 +msgid "" +"A visual security frame displaying the beginning of the hash is added to the" +" signatures. Internal users can hide or show it by turning the " +":guilabel:`Frame` option on or off when signing the document." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Adding the visual security frame to a signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:238 +msgid "" +"Tags can be used to categorize and organize documents, allowing users to " +"quickly search for and filter documents based on specific criteria." +msgstr "" + +#: ../../content/applications/finance/sign.rst:241 +msgid "" +"You can manage tags by going to :menuselection:`Configuration --> Tags`. To " +"create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag" +" Name` and select a :guilabel:`Color Index` for your tag." +msgstr "" + +#: ../../content/applications/finance/sign.rst:245 +msgid "" +"To apply a tag to a document, use the dropdown list available in your " +"document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:248 +msgid "" +"You can modify the tags of a signed document by going to " +":menuselection:`Documents --> All Documents`, clicking the vertical ellipsis" +" (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying " +"your :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:253 +msgid "Sign order" +msgstr "" + +#: ../../content/applications/finance/sign.rst:255 +msgid "" +"When a document needs to be signed by different parties, the signing order " +"lets you control the order in which your recipients receive it for " +"signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:258 +msgid "" +"After uploading a PDF with at least two signature fields with two different " +"roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing " +"Order` button and search for the signer's name or email information to add " +"them. You can decide on the signing order by typing **1** or **2** in the " +"first column." +msgstr "" + +#: ../../content/applications/finance/sign.rst:263 +msgid "" +"Each recipient receives the signature request notification only once the " +"previous recipient has completed their action." +msgstr "" + +#: ../../content/applications/finance/sign.rst:267 +msgid "" +"`Odoo Quick Tips: Sign order [video] " +"`_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:272 +msgid "Field types" +msgstr "" + +#: ../../content/applications/finance/sign.rst:274 +msgid "" +"Fields are used in a document to indicate what information must be completed" +" by the signers. You can add fields to your document simply by dragging and " +"dropping them for the left column into your document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:278 +msgid "" +"Various field types can be used to sign documents (placeholder, " +"autocompletion, etc.). By configuring your own field types, also known as " +"signature item types, the signing process can be even faster for your " +"customers, partners, and employees." +msgstr "" + +#: ../../content/applications/finance/sign.rst:282 +msgid "" +"To create and edit field types, go to :menuselection:`Sign --> Configuration" +" --> Settings --> Edit field types`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:285 +msgid "" +"You can select an existing field by clicking on it, or you can " +":guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, " +"select a :guilabel:`Field Type`:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:288 +msgid "" +":guilabel:`Signature`: users are asked to enter their signature either by " +"drawing it, generating an automatic one based on their name, or uploading a " +"local file (usually an image). Each subsequent :guilabel:`Signature` field " +"type then reuses the data entered in the first field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:291 +msgid "" +":guilabel:`Initial`: users are asked to enter their initials, in a similar " +"way to the :guilabel:`Signature` field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:293 +msgid ":guilabel:`Text`: users enter text on a single line." +msgstr "" + +#: ../../content/applications/finance/sign.rst:294 +msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." +msgstr "" + +#: ../../content/applications/finance/sign.rst:295 +msgid "" +":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or " +"consent)." +msgstr "" + +#: ../../content/applications/finance/sign.rst:296 +msgid "" +":guilabel:`Selection`: users choose a single option from a variety of " +"options." +msgstr "" + +#: ../../content/applications/finance/sign.rst:298 +msgid "" +"The :guilabel:`Auto-fill Partner Field` setting is used to automatically " +"fill in a field during the signature process. It uses the value of one of " +"the fields on the contact (`res.partner`) model of the person signing the " +"document. To do so, enter the contact model field's technical name." +msgstr "" + +#: ../../content/applications/finance/sign.rst:303 +msgid "" +"To know the technical name of a field, enable developer mode and hover your " +"mouse on the question mark next to the field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:307 +msgid "" +"Auto-completed values are suggestions and can be modified as required by the" +" person signing the document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:310 +msgid "" +"The size of the fields can also be changed by editing the :guilabel:`Default" +" Width` and :guilabel:`Default Height`. Both sizes are defined as a " +"percentage of the full page expressed as a decimal, with 1 equalling the " +"full page's width or height. By default, the width of new fields you create " +"is set to 15% (0.150) of a full page's width, while their height is set to " +"1.5% (0.015) of a full page's height." +msgstr "" + +#: ../../content/applications/finance/sign.rst:316 +msgid "" +"Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-" +"hand side of the user's screen during the signing process to help them " +"understand what the step entails (e.g., \"Sign here\" or “Fill in your " +"birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed" +" inside the field before it is completed." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Tip and placeholder example in Odoo Sign" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:6 +msgid "Spreadsheet" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:14 +msgid "" +"Spreadsheet lets you organize, analyze, and visualize your data in tabular " +"form. Among others, you can:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:17 +msgid "" +":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) " +"`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:18 +msgid "" +":doc:`Use default templates or create new ones `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:19 +msgid "Format data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:20 +msgid "Use formulas and functions." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:21 +msgid "Sort and filter data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:28 +msgid "" +"Some of Spreadsheet's main :abbr:`UI (user interface)` elements are " +"highlighted and defined below." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst-1 +msgid "Spreadsheet main UI elements" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:34 +msgid "Menu bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:35 +msgid "Top bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:36 +msgid "Formula bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:37 +msgid "Filters button" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:38 +msgid "Row header" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:39 +msgid "Column header" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:40 +msgid "Cell menu" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:41 +msgid "Bottom bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:3 +msgid "Link Odoo data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:5 +msgid "" +"You can insert and link several elements from your database in your " +"spreadsheets, namely:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:7 +msgid "pivots," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:8 +msgid "graphs," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:9 +msgid "lists, and" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:10 +msgid "links to menus (i.e., a clickable link to a view of a specific model)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:12 +msgid "" +"Before inserting :ref:`pivots `, :ref:`graphs " +"`, or lists, ensure they are tailored to your needs, " +"as some elements are more quickly - or only - configurable in their " +"respective view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:16 +msgid "" +"To insert pivots and graphs, click :guilabel:`Insert in spreadsheet` from " +"any pivot or graph view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:17 +msgid "" +"To insert lists, click :menuselection:`Favorites --> Insert list in " +"spreadsheet` from any list view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:19 +msgid "" +"To insert links to menus, click :menuselection:`Favorites --> Link menu in " +"spreadsheet` from any view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:22 +msgid "" +"In the pop-up box, either create a new spreadsheet by selecting " +":guilabel:`Blank spreadsheet` or insert it in an existing one by selecting " +"it and clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst-1 +msgid "Inserting a pivot in a spreadsheet" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:30 +msgid "" +"By default, new spreadsheets are saved under the :guilabel:`Spreadsheet` " +"workspace of the Documents app." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:36 +msgid "Updating data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:38 +msgid "" +"Once inserted in a spreadsheet, your data is kept up-to-date, reflecting any" +" changes made to your database. Reopening the spreadsheet reloads the linked" +" data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:42 +msgid "" +"To update pivots and lists data without reopening a spreadsheet, go to the " +"menu bar and click :menuselection:`Data --> Refresh all data`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:46 +msgid "Pivot data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:48 +msgid "" +"Using :guilabel:`Refresh all data` only updates existing pivot cells. If new" +" cells need to be added, go to the menu bar and click :menuselection:`Data " +"--> Re-insert pivot` to fully update the pivot. Alternatively, click " +":guilabel:`Insert pivot`, select the pivot, and tick :guilabel:`Display " +"missing cells only` to preview first the missing data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:0 +msgid "Displaying missing cells in a pivot" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:57 +msgid "" +"To change which records are :ref:`used by the pivot `, right-click on a pivot cell, select :guilabel:`See pivot " +"properties`, and click :guilabel:`Edit domain`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:5 +msgid "" +"Spreadsheet templates allow you to quickly create spreadsheets without " +"starting from scratch." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:7 +msgid "" +"Several pre-built templates are available when creating a new spreadsheet " +"from the **Documents** app, such as:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:10 +msgid ":ref:`budget reports `," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:11 +msgid ":ref:`pipeline revenue reports `, or" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:12 +msgid ":ref:`sales commission report `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "View of all the default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:17 +msgid "" +"You can also :ref:`save any spreadsheet as a template ` and " +":ref:`manage and edit existing templates `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:21 +msgid "Default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:26 +msgid "Accounting: budget reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:28 +msgid "" +"Budget reports compare a company's actual spending with its budget over a " +"defined period. Two templates are available: one uses quarterly intervals " +"(:guilabel:`Budget Report (Quarterly)`), while the other uses monthly " +"intervals (:guilabel:`Budget Report (Monthly)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a budget report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:35 +msgid "" +"The cells under the :guilabel:`Actuals` column are automatically filled in " +"with the amount of money made and spent over the corresponding period (month" +" or quarter). The data is taken from posted journal items under :ref:`income" +" and expense accounts `." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:40 +msgid "" +"Journal items under the :guilabel:`Other Income` account type are not " +"considered when collecting data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:43 +msgid "" +"To analyze your budget's performance, fill the cells under the " +":guilabel:`Budget` column with how much money you expect to make " +"(:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the " +"related period and per account. Then, the performance (:guilabel:`Perf.`) " +"column compares :guilabel:`Actuals` data to their corresponding budget, " +"expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:48 +msgid "" +"Lastly, the :guilabel:`Net Profit` row represents the total " +":guilabel:`Income` minus the total :guilabel:`Expenses` for the " +":guilabel:`Actuals` and :guilabel:`Budget` columns." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:54 +msgid "CRM: pipeline revenue reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:56 +msgid "" +"Two pipeline revenue reports are available. The :guilabel:`Pipeline Revenue " +"Report (Monthly)` is dedicated to one-time revenue (:abbr:`NRR (non-" +"recurring revenue)`), while the :guilabel:`MRR/NRR Pipeline Revenue Report " +"(Monthly)` covers recurring and non-recurring revenue (:abbr:`MRR (monthly " +"recurring revenue)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:62 +msgid "" +"Enable :guilabel:`Recurring Revenues` by going to :menuselection:`CRM --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a pipeline revenue report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:68 +msgid "" +"The cells under the :guilabel:`Actuals` column are automatically filled in " +"with the amount of monthly revenue from **won** opportunities." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:71 +msgid "" +"To compute the revenue performance, fill in the monthly revenue targets." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:73 +msgid "" +"For the :guilabel:`Revenue by Team` sheet, fill in the cells under the " +":guilabel:`Target` columns for each sales team." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:75 +msgid "" +"For the :guilabel:`Revenue by Salesperson` sheet, open the " +":guilabel:`Targets` sheet and fill in the cells next to each salesperson. " +"Use the :guilabel:`Monthly Factor` table below to adapt the main targets " +"depending on the month of the year." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:79 +msgid "" +"Then, the performance (:guilabel:`Perf.`) column compares " +":guilabel:`Actuals` data to their related budget, expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:82 +msgid "" +"Lastly, the :guilabel:`Forecasted` column gathers the monthly revenue of " +"leads multiplied by their :guilabel:`Probability` percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:86 +msgid "For actuals and forecasts:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:88 +msgid "" +"The :guilabel:`Expected Closing` date found on leads is used to assign them " +"to a month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:89 +msgid "" +"The recurring monthly revenue is used even if the recurring plan's number of" +" months is set to a different value than 1 month. For example, a yearly " +"plan's revenue is divided by 12 months." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:95 +msgid "Sales: sales commission" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:97 +msgid "" +"This report presents the monthly commission earned or due to each " +"salesperson." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a sales commission report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:102 +msgid "" +"The :guilabel:`Rate` column is pre-filled with the percentage rate from the " +":guilabel:`Rates` tab, which can be customized for each product category " +"according to the company's policy. Adjusting the rate for a specific product" +" category automatically updates the commission amount for that category." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:106 +msgid "" +"The :guilabel:`Invoiced` column shows the total amount of untaxed invoices " +"grouped by salesperson and month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:109 +msgid "" +"Lastly, the :guilabel:`Comm.` column is computed by multiplying the invoiced" +" amount with the rate percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:115 +msgid "Save a spreadsheet as a template" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:117 +msgid "" +"Any spreadsheet can be saved as a template. From the menu bar, click " +":menuselection:`File --> Save as template`. Modify the default " +":guilabel:`Template Name` if necessary and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:122 +msgid "Templates are available to all users on the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:127 +msgid "Manage and edit templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:129 +msgid "" +"Manage templates by going to :menuselection:`Documents --> Configuration -->" +" Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter " +"` to view all templates in the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:133 +msgid "" +"To edit an existing template, click `✎ Edit` next to the desired template. " +"Modifications are automatically saved." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:137 +msgid "" +"Use the download button under the :guilabel:`Data` column to export a " +"template in JSON format. The file can be imported into another database." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/general.po b/locale/hi/LC_MESSAGES/general.po new file mode 100644 index 000000000..bc3ee8663 --- /dev/null +++ b/locale/hi/LC_MESSAGES/general.po @@ -0,0 +1,6075 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/general.rst:3 +msgid "Miscellaneous" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:3 +msgid "Apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:5 +msgid "" +"You can :ref:`install `, :ref:`upgrade ` " +"and :ref:`uninstall ` all apps and modules from the " +":menuselection:`Apps` dashboard." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:8 +msgid "" +"By default, an *Apps* filter is applied. If you want to search for modules, " +"click on *Filters* and select *Extra*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst-1 +msgid "Add \"Extra\" filter in Odoo Apps" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:16 +msgid "" +"Odoo is *not a smartphone*, and its apps shouldn't be installed or " +"uninstalled carelessly. Apply caution when adding or removing apps and " +"modules on your database since this may impact your subscription costs." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Installing or uninstalling apps and managing users is up to you.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"As the administrator of your database, you are responsible for its usage, as" +" you know best how your organization works." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Odoo apps have dependencies.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"Installing some apps and features with dependencies may also install " +"additional apps and modules that are technically required, even if you won't" +" actively use them." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Test app installation/removal on a duplicate of your database.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"This way, you can know what app dependencies may be required or what data " +"may be erased." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:32 +msgid "Install apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:34 +msgid "" +"Go to :menuselection:`Apps`, and click on the *Install* button of the app " +"you want to install." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:37 +msgid "" +"If the module you are looking for is not listed, you can **update the app " +"list**." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:39 +msgid "" +"To do so, activate the :ref:`developer mode `, then go to " +":menuselection:`Apps --> Update Apps List` and click on *Update*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:45 +msgid "Upgrade apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:47 +msgid "" +"On some occasions, new improvements or app features are added to " +":doc:`supported versions of Odoo " +"`. To be able to use them, you " +"must **upgrade** your app." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:51 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to upgrade, then on *Upgrade*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:57 +msgid "Uninstall apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:59 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to uninstall, then on *Uninstall*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:65 +msgid "" +"Some apps have dependencies, meaning that one app requires another. " +"Therefore, uninstalling one app may uninstall multiple apps and modules. " +"Odoo warns you which dependent apps and modules are affected by it." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:72 +msgid "To complete the uninstallation, click on *Confirm*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:75 +msgid "" +"Uninstalling an app also uninstalls all its dependencies and permanently " +"erases their data." +msgstr "" + +#: ../../content/applications/general/auth.rst:5 +#: ../../content/applications/general/auth/azure.rst:79 +msgid "Authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:3 +msgid "Two-factor Authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:5 +msgid "" +"Two-factor authentication (\"2FA\") is a good way to improve the security of" +" an account, to make it less likely that an other person will manage to log " +"in instead of you." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:9 +msgid "" +"Practically, it means storing a secret inside an *authenticator* (usually " +"your cell phone) and exchanging a code from the authenticator when you try " +"to log in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:13 +msgid "" +"This means an attacker needs *both* to have guessed (or found) your password" +" and to access (or steal) your authenticator, a more difficult proposition " +"than either one or the other." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:18 +msgid "Requirements" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:20 +msgid "" +"These lists are just examples, they are not endorsements of any specific " +"software." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:23 +msgid "" +"If you don't already have one, you will need to choose an authenticator." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:26 +msgid "" +"Phone-based authenticators are the easiest and most common so we will assume" +" you'll pick and install one on your phone, examples include `Authy " +"`_, `FreeOTP `_, `Google " +"Authenticator `_, " +"`LastPass Authenticator `_, `Microsoft " +"Authenticator `_, ...; password managers also " +"commonly include :abbr:`2FA (two-factor authentication)` support e.g. " +"`1Password `_, `Bitwarden" +" `_, ..." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:39 +msgid "" +"For the sake of demonstration we will be using Google Authenticator (not " +"because it is any good but because it is quite common)." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:43 +msgid "Setting up two-factor authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:45 +msgid "" +"Once you have your authenticator of choice, go to the Odoo instance you want" +" to setup :abbr:`2FA (two-factor authentication)`, then open " +":guilabel:`Preferences` (or :guilabel:`My Profile`):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:52 +msgid "" +"Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable " +"two-factor authentication` button:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:58 +msgid "" +"Because this is a security-sensitive action, you will need to input your " +"password:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:64 +msgid "After which you will see this screen with a barcode:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:69 +msgid "" +"In most applications, you can simply *scan the barcode* via the " +"authenticator of your choice, the authenticator will then take care of all " +"the setup:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:78 +msgid "" +"If you can not scan the screen (e.g. because you are doing this set-up on " +"the same phone as the authenticator application), you can click the provided" +" link, or copy the secret to manually set-up your authenticator:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:89 +msgid "" +"Once this is done, the authenticator should display a *verification code* " +"with some useful identifying information (e.g. the domain and login for " +"which the code is):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:96 +msgid "" +"You can now input the code into the :guilabel:`Verification Code` field, " +"then click the :guilabel:`Enable two-factor authentication` button." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:100 +msgid "" +"Congratulation, your account is now protected by two-factor authentication!" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:107 +msgid "Logging in" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:109 +msgid "You should now :guilabel:`Log out` to follow along." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:111 +msgid "" +"On the login page, input the username and password of the account for which " +"you set up :abbr:`2FA (two-factor authentication)`, rather than immediately " +"enter Odoo you will now get a second log-in screen:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:118 +msgid "" +"Get your authenticator, input the code it provides for the domain and " +"account, validate, and you're now in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:121 +msgid "" +"And that's it. From now on, unless you disable :abbr:`2FA (two-factor " +"authentication)` you will have a two-step log-in process rather than the old" +" one-step process." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:125 +msgid "" +"Don't lose your authenticator, if you do, you will need an *Odoo " +"Administrator* to disable :abbr:`2FA (two-factor authentication)` on the " +"account." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:3 +msgid "Microsoft Azure sign-in authentication" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:5 +msgid "" +"The Microsoft Azure OAuth sign-in authentication is a useful function that " +"allows Odoo users to sign in to their database with their Microsoft Azure " +"account." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:8 +msgid "" +"This is particularly helpful if the organization uses Azure Workspace, and " +"wants employees within the organization to connect to Odoo using their " +"Microsoft Accounts." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:12 +msgid "" +"Databases hosted on Odoo.com should not use OAuth login for the owner or " +"administrator of the database as it would unlink the database from their " +"Odoo.com account. If OAuth is set up for that user, the database will no " +"longer be able to be duplicated, renamed, or otherwise managed from the " +"Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:19 +msgid ":doc:`../../productivity/calendar/outlook`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:20 +#: ../../content/applications/general/email_communication/email_servers.rst:67 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:23 +#: ../../content/applications/general/auth/google.rst:24 +#: ../../content/applications/general/voip/axivox.rst:16 +#: ../../content/applications/general/voip/onsip.rst:17 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:25 +msgid "" +"Integrating the Microsoft sign-in function requires configuration on " +"Microsoft and Odoo." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:28 +msgid "Odoo System Parameter" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:30 +msgid "" +"First activate the :ref:`developer mode `, and then go to " +":menuselection:`Settings --> Technical --> System Parameters`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:33 +msgid "" +"Click :guilabel:`Create` and on the new/blank form that appears, add the " +"following system parameter `auth_oauth.authorization_header` to the " +":guilabel:`Key` field, and set the :guilabel:`Value` to `1`. Then click " +":guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:38 +msgid "Microsoft Azure dashboard" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:41 +msgid "Create a new application" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:43 +msgid "" +"Now that the system parameters in Odoo have been set up, it's time to create" +" a corresponding application inside of Microsoft Azure. To get started " +"creating the new application, go to `Microsoft's Azure Portal " +"`_. Log in with the :guilabel:`Microsoft Outlook " +"Office 365` account if there is one, otherwise, log in with a personal " +":guilabel:`Microsoft account`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:50 +msgid "" +"A user with administrative access to the *Azure Settings* must connect and " +"perform the following configuration steps below." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:53 +msgid "" +"Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` " +"(formally *Azure Active Directory*). The location of this link is usually in" +" the center of the page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:56 +msgid "" +"Now, click on the :guilabel:`Add (+)` icon, located in the top menu, and " +"then select :guilabel:`App registration` from the drop-down menu. On the " +":guilabel:`Register an application` screen, rename the :guilabel:`Name` " +"field to `Odoo Login OAuth` or a similarly recognizable title. Under the " +":guilabel:`Supported account types` section select the option for " +":guilabel:`Accounts in this organizational directory only (Default Directory" +" only - Single tenant)`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:63 +msgid "" +"The :guilabel:`Supported account types` can vary by Microsoft account type " +"and end use of the OAuth. For example: Is the login meant for internal users" +" within one organization or is it meant for customer portal access? The " +"above configuration is used for internal users in an organization." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:68 +msgid "" +"Choose :guilabel:`Personal Microsoft accounts only` if the target audience " +"is meant for portal users. Choose :guilabel:`Accounts in this organizational" +" directory only (Default Directory only - Single tenant)` if the target " +"audience is company users." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:72 +msgid "" +"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " +"platform, and then input `https:///auth_oauth/signin` in the " +":guilabel:`URL` field. The Odoo base :abbr:`URL (Uniform Resource Locator)` " +"is the canonical domain at which your Odoo instance can be reached (e.g. " +"*mydatabase.odoo.com* if you are hosted on Odoo.com) in the :guilabel:`URL` " +"field. Then, click :guilabel:`Register`, and the application is created." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:81 +msgid "" +"Edit the new app's authentication by clicking on the " +":guilabel:`Authentication` menu item in the left menu after being redirected" +" to the application's settings from the previous step." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:84 +msgid "" +"Next, the type of *tokens* needed for the OAuth authentication will be " +"chosen. These are not currency tokens but rather authentication tokens that " +"are passed between Microsoft and Odoo. Therefore, there is no cost for these" +" tokens; they are used merely for authentication purposes between two " +":abbr:`APIs (application programming interfaces)`. Select the tokens that " +"should be issued by the authorization endpoint by scrolling down the screen " +"and check the boxes labeled: :guilabel:`Access tokens (used for implicit " +"flows)` and :guilabel:`ID tokens (used for implicit and hybrid flows)`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Authentication settings and endpoint tokens." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:96 +msgid "Click :guilabel:`Save` to ensure these settings are saved." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:99 +msgid "Gather credentials" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:101 +msgid "" +"With the application created and authenticated in the Microsoft Azure " +"console, credentials will be gathered next. To do so, click on the " +":guilabel:`Overview` menu item in the left-hand column. Select and copy the " +":guilabel:`Application (client) ID` in the window that appears. Paste this " +"credential to a clipboard / notepad, as this credential will be used in the " +"Odoo configuration later." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:106 +msgid "" +"After finishing this step, click on :guilabel:`Endpoints` on the top menu " +"and click the *copy icon* next to :guilabel:`OAuth 2.0 authorization " +"endpoint (v2)` field. Paste this value in the clipboard / notepad." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:115 +msgid "Odoo setup" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:117 +msgid "" +"Finally, the last step in the Microsoft Azure OAuth configuration is to " +"configure some settings in Odoo. Navigate to :menuselection:`Settings --> " +"Integrations --> OAuth Authentication` and check the box to activate the " +"OAuth login feature. Click :guilabel:`Save` to ensure the progress is saved." +" Then, sign in to the database once the login screen loads." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:122 +msgid "" +"Once again, navigate to :menuselection:`Settings --> Integrations --> OAuth " +"Authentication` and click on :guilabel:`OAuth Providers`. Now, select " +":guilabel:`New` in the upper-left corner and name the provider `Azure`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:126 +msgid "" +"Paste the :guilabel:`Application (client) ID` from the previous section into" +" the :guilabel:`Client ID` field. After completing this, paste the new " +":guilabel:`OAuth 2.0 authorization endpoint (v2)` value into the " +":guilabel:`Authorization URL` field." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:130 +msgid "" +"For the :guilabel:`UserInfo URL` field, paste the following :abbr:`URL " +"(Uniform Resource Locator)`: `https://graph.microsoft.com/oidc/userinfo`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:133 +msgid "" +"In the :guilabel:`Scope` field, paste the following value: `openid profile " +"email`. Next, the Windows logo can be used as the CSS class on the login " +"screen by entering the following value: `fa fa-fw fa-windows`, in the " +":guilabel:`CSS class` field." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:137 +msgid "" +"Check the box next to the :guilabel:`Allowed` field to enable the OAuth " +"provider. Finally, add `Microsoft Azure` to the :guilabel:`Login button " +"label` field. This text will appear next to the Windows logo on the login " +"page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Odoo provider setup in the Settings application." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:145 +msgid "" +":guilabel:`Save` the changes to complete the OAuth authentication setup in " +"Odoo." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:148 +msgid "User experience flows" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:150 +msgid "" +"For a user to log in to Odoo using Microsoft Azure, the user must be on the " +":menuselection:`Odoo password reset page`. This is the only way that Odoo is" +" able to link the Microsoft Azure account and allow the user to log in." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:155 +msgid "" +"Existing users must :ref:`reset their password ` to " +"access the :menuselection:`Odoo password reset page`. New Odoo users must " +"click the new user invitation link that was sent via email, then click on " +":guilabel:`Microsoft Azure`. Users should not set a new password." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:160 +msgid "" +"To sign in to Odoo for the first time using the Microsoft Azure OAuth " +"provider, navigate to the :menuselection:`Odoo password reset page` (using " +"the new user invitation link). A password reset page should appear. Then, " +"click on the option labeled :guilabel:`Microsoft Azure`. The page will " +"redirect to the Microsoft login page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Microsoft Outlook login page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:169 +msgid "" +"Enter the :guilabel:`Microsoft Email Address` and click :guilabel:`Next`. " +"Follow the process to sign in to the account. Should :abbr:`2FA (Two Factor " +"Authentication)` be turned on, then an extra step may be required." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Enter Microsoft login credentials." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:177 +msgid "" +"Finally, after logging in to the account, the page will redirect to a " +"permissions page where the user will be prompted to :guilabel:`Accept` the " +"conditions that the Odoo application will access their Microsoft " +"information." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "" +"Accept Microsoft conditions for permission access to your account " +"information." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:3 +msgid "Google Sign-In Authentication" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:5 +msgid "" +"The *Google Sign-In Authentication* is a useful function that allows Odoo " +"users to sign in to their database with their Google account." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:8 +msgid "" +"This is particularly helpful if the organization uses Google Workspace, and " +"wants employees within the organization to connect to Odoo using their " +"Google Accounts." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:12 +msgid "" +"Databases hosted on Odoo.com should not use Oauth login for the owner or " +"administrator of the database as it would unlink the database from their " +"Odoo.com account. If Oauth is set up for that user, the database will no " +"longer be able to be duplicated, renamed or otherwise managed from the " +"Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:18 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:19 +#: ../../content/applications/general/email_communication/email_servers.rst:66 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:26 +msgid "" +"The integration of the Google sign-in function requires configuration both " +"on Google *and* Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:31 +msgid "Google API Dashboard" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:33 +msgid "" +"Go to the `Google API Dashboard `_." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:34 +msgid "" +"Make sure the right project is opened. If there isn't a project yet, click " +"on :guilabel:`Create Project`, fill out the project name and other details " +"of the company, and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the details of a new project." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:43 +msgid "Choose the name of the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:48 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:50 +msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Google OAuth consent selection menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:56 +msgid "" +"Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and" +" click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Choice of a user type in OAuth consent." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:64 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:68 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:71 +msgid "" +"Fill out the required details and domain info, then click on :guilabel:`Save" +" and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:72 +msgid "" +"On the :menuselection:`Scopes` page, leave all fields as is, and click on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:74 +msgid "" +"Next, if continuing in testing mode (*External*), add the email addresses " +"being configured under the :guilabel:`Test users` step by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:77 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:82 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:84 +msgid "On the left side menu, click on :menuselection:`Credentials`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Credentials button menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:90 +msgid "" +"Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client " +"ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "OAuth client id selection." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:96 +msgid "" +"Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now," +" configure the allowed pages on which Odoo will be redirected." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:99 +msgid "" +"In order to achieve this, in the :guilabel:`Authorized redirect URIs` field," +" enter the database's domain immediately followed by `/auth_oauth/signin`. " +"For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:103 +msgid "" +"Now that the *OAuth client* has been created, a screen will appear with the " +":guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the " +":guilabel:`Client ID` for later, as it will be necessary for the " +"configuration in Odoo, which will be covered in the following steps." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:110 +msgid "Google Authentication on Odoo" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:115 +msgid "Retrieve the Client ID" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:117 +msgid "" +"Once the previous steps are complete, two keys are generated on the Google " +"API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the" +" :guilabel:`Client ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst-1 +msgid "Google OAuth Client ID generated." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:127 +msgid "Odoo activation" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:129 +msgid "" +"Go to :menuselection:`Odoo General Settings --> Integrations` and activate " +":guilabel:`OAuth Authentication`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:133 +msgid "Odoo may prompt the user to log-in again after this step." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:135 +msgid "" +"Go back to :menuselection:`General Settings --> Integrations --> OAuth " +"Authentication`, activate the selection and :guilabel:`Save`. Next, return " +"to :menuselection:`General Settings --> Integrations --> Google " +"Authentication` and activate the selection. Then fill out the " +":guilabel:`Client ID` with the key from the Google API Dashboard, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the client id in Odoo settings." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:145 +msgid "" +"Google OAuth2 configuration can also be accessed by clicking on " +":guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` " +"heading in :menuselection:`Integrations`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:151 +msgid "Log in to Odoo with Google" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:153 +msgid "" +"To link the Google account to the Odoo profile, click on :guilabel:`Log in " +"with Google` when first logging into Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Reset password screen with \"Log in with Google\" button." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:161 +msgid "" +"Existing users must :ref:`reset their password ` to " +"access the :menuselection:`Reset Password` page, while new users can " +"directly click on :guilabel:`Log in with Google`, instead of choosing a new " +"password." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:166 +msgid "" +"`Google Cloud Platform Console Help - Setting up OAuth 2.0 " +"`_" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:3 +msgid "Sign in with LDAP" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:5 +msgid "Install the LDAP module in General Settings." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:7 +msgid "Click on **Create** in Setup your LDAP Server." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:15 +msgid "Choose the company about to use the LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:20 +msgid "" +"In **Server Information**, enter the IP address of your server and the port " +"it listens to." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:22 +msgid "Tick **User TLS** if your server is compatible." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:27 +msgid "" +"In **Login Information**, enter ID and password of the account used to query" +" the server. If left empty, the server will be queried anonymously." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:32 +msgid "" +"In **Process Parameter**, enter the domain name of your LDAP server in LDAP " +"nomenclature (e.g. ``dc=example,dc=com``)." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:34 +msgid "In **LDAP filter**, enter ``uid=%s``" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:39 +msgid "" +"In **User Information**, tick *Create User* if you want Odoo to create a " +"User profile the first time someone log in with LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:41 +msgid "" +"In **Template User**, indicate a template for the new profiles created. If " +"left blanked, the admin profile will be used as template." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:5 +msgid "Developer Mode (debug mode)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:7 +msgid "" +"The developer mode (or debug mode) unlocks access to extra and advanced " +"tools in Odoo. There are several ways to activate the developer mode: " +"through the :ref:`settings `, the " +":ref:`browser extension `, through" +" the :ref:`command palette ` or the" +" :ref:`URL `." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:17 +msgid "Activate through the Settings" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:19 +msgid "" +"The debug mode can be activated in the Odoo database settings. Go to " +":menuselection:`Settings --> General Settings --> Developer Tools` and click" +" on :guilabel:`Activate the developer mode`. At least one application needs " +"to be installed for the :guilabel:`Developer Tools` section to appear in the" +" :guilabel:`Settings` module." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of the debug options under settings in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:29 +msgid "" +":guilabel:`Activate the developer mode (with assets)` is used by developers;" +" :guilabel:`Activate the developer mode (with tests assets)` is used by " +"developers and testers." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:32 +msgid "" +"Once activated, the :guilabel:`Deactivate the developer mode` option becomes" +" available." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:37 +msgid "Activate through the browser extension" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:39 +msgid "" +"Within a web browser, navigate to the browser settings and extensions and " +"search for the `Odoo Debug` extension. Once the extension is installed, a " +"new icon will be shown on the browser's toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:43 +msgid "" +"For the *Odoo Debug* extension, a single click enables a normal version of " +"the mode, while a double click enables it with assets. To deactivate it, use" +" a single click." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "View of Odoo's debug icon in a Google Chrome toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:53 +msgid "Activate through the command palette" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:55 +msgid "" +"In Odoo, the command palette tool has a command to activate the debug mode. " +"First, open the command palette tool with the keyboard shortcut `ctrl+k` and" +" then type `debug`. A command will show up to activate the debug mode." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Command palette with debug command." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:68 +msgid "Activate through the URL" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:70 +msgid "" +"The debug mode can also be activated by adding an extra query string to the " +"database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To" +" deactivate the debug mode, change the value to `?debug=0` instead." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a URL with the debug mode command added." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:79 +msgid "" +"Additional modes are available for developers: `?debug=assets` enables the " +":ref:`assets mode `, and " +"`?debug=tests` enables the :ref:`tests mode " +"`." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:86 +msgid "Locate the developer mode tools" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:88 +msgid "" +"Once developer mode is activated, the developer mode tools can be accessed " +"from the :guilabel:`Open Developer Tools` button, the bug icon located in " +"the header of the Odoo database." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a console page and the debug icon being shown in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:95 +msgid "" +"This menu contains additional tools that are useful to understand or edit " +"technical data, such as the views or actions of a page. On a page that has " +"filters, actions, and view options, the developer mode tools contain some " +"useful menu items such as:" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:99 +msgid ":guilabel:`Edit Action`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:100 +msgid ":guilabel:`Manage Filters`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:101 +msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:102 +msgid "See the :guilabel:`Fields View Get`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:3 +msgid "Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:5 +msgid "" +"**Digest Emails** are periodic snapshots sent to your organization via email" +" that include high-level information about how your business is performing." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:8 +msgid "" +"Navigate to Digest Emails by going to :menuselection:`Settings --> General " +"Settings --> Statistics`, then activate the **Digest Emails** feature and " +"click on save." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Digest Emails section inside General Settings." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:15 +msgid "You can control a variety of settings for your Digest Emails, such as:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:17 +msgid "which KPIs are shared in the Digest" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:18 +msgid "how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:19 +msgid "who in your organization receives Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:20 +msgid "creating custom Digest Email templates" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:21 +msgid "adding additional KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:24 +msgid "" +"By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* " +"serves as the primary template, which includes all KPI measurements across " +"your Odoo database and is sent daily to administrators." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:31 +msgid "Customize *Your Odoo Periodic Digest*" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:33 +msgid "" +"To customize the default Digest Email (*Your Odoo Periodic Digest*), go to " +":menuselection:`Settings --> General Settings --> Statistics --> Digest " +"Email`, select *Your Odoo Periodic Digest* and click on the *external link* " +"next to the dropdown selection." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:37 +msgid "" +"A popup window appears and presents a variety of editable settings, which " +"include:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:39 +msgid "**Digest Title** - what you want your Digest Email to be called" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:40 +msgid "" +"**Periodicity** - control the regimen in how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:41 +msgid "" +"**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:42 +msgid "**Recipients** - add/remove users who receive your Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:43 +msgid "**Custom** - add your own KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Customize default Digest Email settings and custom KPIs." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:52 +msgid "Custom digest emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:54 +msgid "To do so, click on **Configure Digest Emails** and then **Create**." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:56 +msgid "" +"From there, give your Digest Email a title, specify periodicity, and choose " +"your desired KPIs and recipients fields as needed." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:59 +msgid "" +"After you click **Save**, your new custom Digest Email is available as a " +"selection in the **General Settings** dropdown menu." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:65 +msgid "Custom KPIs with Studio" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:67 +msgid "" +"For either *Your Odoo Periodic Digest* or your own custom Digest Email, you " +"can add your own KPIs by using Odoo Studio." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:70 +msgid "" +"To begin, click the **Toggle Studio** icon or click the **Recipients** tab " +"and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit " +"the template or add additional fields." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:73 +msgid "" +"In order to create additional fields, you must create two fields on the " +"digest object:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:75 +msgid "" +"create a boolean field called `kpi_myfield` and display it in the KPIs tab" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:76 +msgid "" +"create a computed field called `kpi_myfield_value` that computes your " +"customized KPI" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:77 +msgid "select your KPI(s) in the KPIs tab." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:80 +msgid "Computed values reference table" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "LABEL" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "VALUE" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "Connected Users" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "`kpi_res_users_connected_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "Messages Sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "`kpi_mail_message_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "New Leads" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "`kpi_crm_lead_created_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "Opportunities Won" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "`kpi_crm_opportunities_won_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "Open Tasks" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "`kpi_project_task_opened_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "Tickets Closed" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "`kpi_helpdesk_tickets_closed_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "% of Happiness" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "`kpi_livechat_rating_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "Conversations handled" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "`kpi_livechat_conversations_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "Time to answer (sec)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "`kpi_livechat_response_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "All Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "`kpi_all_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "eCommerce Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "`kpi_website_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "Revenue" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "`kpi_account_total_revenue_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "Bank & Cash Moves" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "`kpi_account_bank_cash_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "POS Sales" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "`kpi_pos_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "New Employees" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "`kpi_hr_recruitment_new_colleagues_value`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:5 +msgid "Email Communication" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:3 +msgid "Configure DNS records to send emails in Odoo" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:6 +msgid "SPAM labels overview" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:8 +msgid "" +"Sometimes, emails from Odoo are misclassified by the different email " +"providers and end up in spam folders. At the moment, some settings are out " +"of Odoo's control, notably the way the different email providers classify " +"Odoo's emails according to their own restriction policy and/or limitations." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:12 +msgid "" +"It is standard in Odoo that emails are received from ``\"name of the " +"author\" ``. In other words this can be " +"translated to: ``\"name of the author\" " +"<{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands " +"for `ir.config.parameters`, which are the System Parameters. Deliverability " +"is greatly improved with the :ref:`notifications configuration " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:18 +msgid "" +"In order for servers to accept emails from Odoo on a more regular basis, one" +" of the solutions is for customers to create rules within their own mailbox." +" A filter can be added to the email inbox so that when email is received " +"from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It " +"is also possible to add the Odoo database domain onto a safe senders list or" +" whitelist on the receiving domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:24 +msgid "" +"If an Odoo email server appears on a blacklist, notify Odoo via a `new help " +"ticket `_ and the support team will work to get " +"the servers removed from the blacklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:28 +msgid "" +"Should the Odoo database be using a custom domain for sending emails from " +"Odoo there are three records that should be implemented on the custom " +"domain's DNS to ensure deliverability of email. This includes setting " +"records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys " +"Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)`. Ultimately though, it is up to the discretion of" +" the final receiving mailbox." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:38 +msgid "Be SPF compliant" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:40 +msgid "" +"The Sender Policy Framework (SPF) protocol allows the owner of a domain name" +" to specify which servers are allowed to send emails from that domain. When " +"a server receives an incoming email, it checks whether the IP address of the" +" sending server is on the list of allowed IPs according to the sender's " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:46 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` verification is performed on the " +"domain mentioned in the `Return-Path` field of the email. In the case of an " +"email sent by Odoo, this domain corresponds to the value of the " +"`mail.catchall.domain` key in the database system parameters." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:50 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a " +"TXT record. The way to create or modify a TXT record depends on the provider" +" hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In " +"order for the verification to work properly, each domain can only have one " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:55 +msgid "" +"If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)`" +" record, create one using the following input: `v=spf1 include:_spf.odoo.com" +" ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:58 +msgid "" +"If the domain name already has a :abbr:`SPF (Sender Policy Framework)` " +"record, the record must be updated (and do not create a new one)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:63 +msgid "" +"If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add " +"`include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com " +"include:_spf.google.com ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:66 +msgid "" +"Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a " +"free tool like `MXToolbox SPF `_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:72 +msgid "Enable DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:74 +msgid "" +"The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails " +"with a digital signature." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:77 +msgid "" +"When sending an email, the Odoo server includes a unique :abbr:`DKIM " +"(DomainKeys Identified Mail)` signature in the headers. The recipient's " +"server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified " +"Mail)` record in the database's domain name. If the signature and the key " +"contained in the record match, this guarantees that the message is authentic" +" and has not been altered during transport." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:83 +msgid "" +"To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME " +"(Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the" +" domain name:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:86 +msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:89 +msgid "" +"If the domain name is `mycompany.com`, make sure to create a subdomain " +"`odoo._domainkey.mycompany.com` whose canonical name is " +"`odoo._domainkey.odoo.com.`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:92 +msgid "" +"The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends " +"on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the " +"domain name. The most common providers are :ref:`listed below " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:96 +msgid "" +"Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with " +"a free tool like `DKIM Core `_. If a selector " +"is asked, enter `odoo`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:100 +msgid "Check the DMARC policy" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:102 +msgid "" +"The Domain-based Message Authentication, Reporting, & Conformance (DMARC) " +"record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and " +":abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the" +" :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name tell the destination server what to do" +" with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)`" +" and/or :abbr:`DKIM (DomainKeys Identified Mail)` check." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:110 +msgid "DMARC: TXT record" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:112 +msgid "`v=DMARC1; p=none;`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:114 +msgid "" +"There are three :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` policies:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:117 +msgid "`p=none`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:118 +#: ../../content/applications/general/email_communication/email_domain.rst:171 +msgid "`p=quarantine`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:119 +msgid "`p=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:121 +msgid "" +"`p=quarantine` and `p=reject` instruct the server that receives an email to " +"quarantine that email or ignore it if the :abbr:`SPF (Sender Policy " +"Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:125 +msgid "" +"If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` and has defined one of these policies, the domain" +" must be :abbr:`SPF (Sender Policy Framework)` compliant or enable " +":abbr:`DKIM (DomainKeys Identified Mail)`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:130 +msgid "" +"Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, & Conformance)` policy set to " +"`p=reject`. Odoo strongly advises against using an *@yahoo.com* or " +"*@aol.com* address for the database users. These emails will never reach " +"their recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:135 +msgid "" +"`p=none` is used for the domain owner to receive reports about entities " +"using their domain. It should not impact the deliverability if the " +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:139 +msgid "" +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` records are comprised of tags in the form of :abbr:`DNS " +"(Domain Name System)` records. These tags/parameters allow for reporting, " +"such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF " +"(Reporting URI for forensic reports)`, along with more precise specification" +" like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P " +"(Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the" +" OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode " +"for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message " +"Authentication, Reporting, & Conformance)` policy should not start out being" +" too restrictive." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:148 +msgid "The following chart displays available tags:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:154 +msgid "Tag Name" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:155 +msgid "Purpose" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:156 +msgid "Example" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:157 +msgid "v" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:158 +msgid "Protocol version" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:159 +msgid "`v=DMARC1`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:160 +msgid "pct" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:161 +msgid "Percentage of messages subjected to filtering" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:162 +msgid "`pct=20`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:163 +msgid "ruf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:164 +msgid "Reporting URI for forensic reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:165 +msgid "`ruf=mailto:authfail@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:166 +msgid "rua" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:167 +msgid "Reporting URI of aggregate reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:168 +msgid "`rua=mailto:aggrep@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:169 +msgid "p" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:170 +msgid "Policy for organizational domain" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:172 +msgid "sp" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:173 +msgid "Policy for subdomains of the OD" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:174 +msgid "`sp=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:175 +msgid "adkim" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:176 +msgid "Alignment mode for DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:177 +msgid "`adkim=s`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:178 +msgid "aspf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:179 +msgid "Alignment mode for SPF" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:180 +msgid "`aspf=r`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:182 +msgid "" +"Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name with a tool like `MXToolbox DMARC " +"`_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:186 +msgid "" +"`DMARC.org is another great resource to learn about DMARC records. " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:192 +msgid "SPF, DKIM & DMARC documentation of common providers" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:194 +msgid "" +"`OVH DNS " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:195 +msgid "" +"`OVH SPF `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:196 +msgid "" +"`GoDaddy TXT record `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:197 +msgid "`GoDaddy SPF `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:198 +msgid "" +"`GoDaddy DKIM `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:199 +msgid "" +"`NameCheap " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:201 +msgid "" +"`CloudFlare DNS `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:202 +msgid "" +"`Google Domains `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:203 +msgid "" +"`Azure DNS `_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:205 +msgid "" +"To fully test the configuration, use the `Mail-Tester `_ tool, which gives a full overview of the content and " +"configuration in one sent email. Mail-Tester can also be used to configure " +"records for other, lesser-known providers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:210 +msgid "" +"`Using Mail-Tester to set SPF Records for specific carriers " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:3 +msgid "Send and receive emails in Odoo with an email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:6 +msgid "Odoo Online or Odoo.sh users" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:8 +msgid "" +"Since **Odoo sets up its own mail servers for the database**, outgoing and " +"incoming emails already work out-of-the-box. So for **Odoo Online** and " +"**Odoo.sh** customers, nothing needs to be configured!" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:12 +msgid "" +"Unless an external mail server is required to send large batches of mass " +"emails, simply use the standard online Odoo database normally since it has " +"already been pre-configured to send email." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:16 +msgid "" +"The Odoo server is subject to a daily email limit to prevent abuse. The " +"default limit is 200 emails sent per day for databases with an " +"**Enterprise** subscription. This limit can be increased under certain " +"conditions. See the :doc:`FAQ ` or contact support for more " +"information." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:22 +msgid "Scope of this documentation" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:24 +msgid "" +"This document is **mainly dedicated to Odoo on-premise databases** who don't" +" benefit from an out-of-the-box solution to send and receive emails in Odoo," +" unlike `Odoo Online `_ and `Odoo.sh " +"`_. Incoming and outgoing servers must be configured " +"for on-premise databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:29 +msgid "" +"The following sections below contain information on how to integrate an " +"external email server with Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:33 +msgid "" +"If no one in the company is employed to manage email servers, Odoo Online " +"and Odoo.sh are strongly recommended. In these Odoo hosting types email " +"sending and receiving works instantly and is monitored by professionals. " +"Nevertheless, a company can use their own email server if they want to " +"manage the email server's reputation themselves. For more information see " +":doc:`Configure DNS records to send emails in Odoo `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:42 +msgid "Default notifications system" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:44 +msgid "" +"Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, " +"etc.) have a discussion thread, called *chatter*." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:47 +msgid "" +"When a database user posts a message in the chatter, this message is sent by" +" email to the followers of the document as a notification (except to the " +"sender). If a follower replies to the message, the reply updates the " +"chatter, and Odoo relays another reply to the followers as a notification. " +"Messages sent back to the chatter from users or external users will appear " +"in the chatter from their respective email, or as the name listed in their " +"*Contacts* record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:53 +msgid "" +"These notifications are sent using a default from address. For more " +"information see :ref:`Use a default email address " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:57 +msgid "Manage outbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:59 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings --> " +"Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. " +"Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers`" +" and click :guilabel:`Create` to create a new outgoing mail server record in" +" Odoo. Reference the SMTP data of the external email server. Once all the " +"information has been filled out, click :guilabel:`Test Connection`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:70 +msgid "" +"Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, " +":abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based " +"Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS " +"(Domain Name System)` will improve deliverability. For more information see " +":doc:`email_domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:78 +msgid "Port restriction" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:80 +msgid "" +"Note that port 25 is blocked for security reasons on the Odoo Online and " +"Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:86 +msgid "Use a default \"From\" email address" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:88 +msgid "" +"Sometimes, an email's \"From\" (outgoing) address can belong to a different " +"domain, and that can be a problem." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:91 +msgid "" +"For example, if a customer with the email address " +"`mary\\@customer.example.com` responds to a message, Odoo will try to " +"redistribute that same email to the other subscribers in the thread. " +"However, if the domain `customer.example.com` forbids that kind of usage for" +" security, the email that Odoo is trying to redistribute would get rejected " +"by some recipients' email servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:96 +msgid "" +"To avoid that problem, Odoo sends all emails using a \"From\" address from " +"the same authorized domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:99 +msgid "" +"Access the :guilabel:`System Parameters` by activating :ref:`developer mode " +"` and going to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:102 +msgid "" +"To force the email address from which emails are sent, a combination of the " +"following keys needs to be set in the system parameters of the database:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:105 +msgid "" +"`mail.default.from`: accepts the local part or a complete email address as " +"value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:106 +msgid "" +"`mail.default.from_filter`: accepts a domain name or a full email address as" +" value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:109 +msgid "" +"The `mail.default.from_filter` works only for `odoo-bin` configurations or " +"the default Odoo email server, otherwise this parameter can be set using the" +" `from_filter` field on `ir.mail_server`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:112 +msgid "" +"The field can be a domain name or an entire email address, or it can remain " +"empty. If the sender's email address does not match this set filter, then " +"the email will be encapsulated using a combination of the two system " +"parameters: `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:117 +msgid "" +"In the following example, the from email address is replaced with the " +"combination of the the two system parameters (`mail.default.from` and " +"`mail.catchall.domain`). This is the default\\ notifications configuration " +"in Odoo: ``“Admin” `` => ``“Admin” " +"``." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:122 +msgid "" +"In other words if the email address of the author does not match " +"`mail.default.from_filter`, the email address is replaced by " +"`mail.default.from` (if it contains a full email address) or a combination " +"of `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:126 +msgid "" +"If the `from_filter` contains a full email address, and if the " +"`mail.default.from` is the same as this address, then all of the email " +"addresses that are different from `mail.default.from` will be encapsulated " +"in `mail.default.from`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:133 +msgid "Utilizing the \"From\" filter on an outgoing email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:135 +msgid "" +"The :guilabel:`FROM Filtering` field allows for the use of a specific " +"outgoing email server depending on the :guilabel:`From` email address or " +"domain that Odoo is sending on behalf of. This setting can be used to " +"improve the deliverability or sending success rate of emails sent from the " +"database. Setting the :guilabel:`FROM Filtering` field can also be used to " +"send from different domains in a multi-company environment. Access this " +"field in Odoo by navigating to :menuselection:`Settings --> Discuss --> " +"Custom Mail Servers --> Outgoing Mail Servers --> New`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst-1 +msgid "Outgoing email server settings and the FROM filter settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:146 +msgid "" +"When an email is sent from Odoo while the :guilabel:`FROM Filtering` field " +"is set, an email server is chosen in the following sequence:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:149 +msgid "" +"First, Odoo searches for an email server that has the same :guilabel:`FROM " +"Filtering` value as the :guilabel:`From` value (email address) defined in " +"the outgoing email. For example, if the :guilabel:`From` value (email " +"address) is `test\\@example.com`, only the email servers that have the " +":guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:153 +msgid "" +"However, if no email servers are found that use the :guilabel:`From` value, " +"then Odoo searches for an email server that has the same *domain* as the " +":guilabel:`From` value (email address) defined in the outgoing email. For " +"example, if the :guilabel:`From` email address is `test\\@example.com`, only" +" the email servers that have the :guilabel:`FROM Filtering` value equal to " +"`example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:159 +msgid "" +"If no email servers are found after checking for the domain, then Odoo " +"returns all email servers that do not have any :guilabel:`FROM Filtering` " +"value(s) set." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:162 +msgid "" +"Should this query return no results, then Odoo performs a search for an " +"email server using the system parameter: `mail.default.from`. First, the " +"email address listed attempts to match an email server, and then the domain " +"attempts to find a match. If no email server is found, Odoo returns the " +"first outgoing email server (sorted by priority)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:168 +msgid "" +"If several email servers are found, then Odoo uses the first one according " +"to its priority. For example, if there are two email servers, one with a " +"priority of `10` and the other with a priority of `20`, then the email " +"server with a priority of `10` is used first." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:175 +msgid "Set up different dedicated servers for transactional and mass emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:177 +msgid "" +"In Odoo a separate email server can be used for transactional emails and " +"mass mailings. Example: Use Postmark or SendinBlue for transactional emails," +" and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet " +"` for mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:182 +msgid "" +"A default outgoing email server is already configured. Do not create an " +"alternative one unless a specific external outgoing email server is needed " +"for technical reasons." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:185 +msgid "" +"To do this, first activate the :ref:`developer mode `, and " +"then go to :menuselection:`Settings --> Technical --> Outgoing` email " +"servers. There, create two outgoing email server settings; one for the " +"transactional emails and one for the mass mailing server. Make sure to give " +"priority to the transactional server over the mass mailing server by " +"providing a lower priority number for the transactional email server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:191 +msgid "" +"Now, go to :menuselection:`Email Marketing --> Settings` and enable " +":guilabel:`Dedicated Server`. Choose the appropriate email server. With " +"these settings, Odoo uses the server with the lower priority for " +"transactional emails, and the server here selected for mass mails. Note that" +" in this case, the domain's Sender Policy Framework (SPF) records must be " +"set to include both transactional and mass mail servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:198 +msgid ":doc:`email_domain`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:203 +msgid "Manage inbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:205 +msgid "Odoo relies on generic email aliases to fetch incoming messages." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:207 +msgid "" +"**Reply messages** of messages sent from Odoo are routed to their original " +"discussion thread (and to the inbox of all its followers) by the alias of " +"the model if there is any or by the catchall alias (**catchall@**). Replies " +"to messages of models that don't have a custom alias will use the catchall " +"alias (`catchall@mycompany.odoo.com`). The catchall address, however, does " +"not have another action attached to it like other aliases might, it is only " +"used to collect replies." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:212 +msgid "" +"**Bounced messages** are used as a Return-Path. One example this is " +"especially useful for is in `Odoo Email Marketing " +"`__. In this case bounces are " +"opt-out based on if the email bounced too many times (5) in the last month " +"and the bounces are separated by one week. This is done to avoid " +"blacklisting someone because of a mail server error. If these circumstances " +"are met then the email is considered invalid and is blacklisted. A log note " +"is added on the contact under :guilabel:`Blacklisted Email Addresses` on the" +" :guilabel:`Email Marketing Configuration Menu`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:220 +msgid "" +"Messages that bounce in the chatter (outside of Email Marketing) will " +"populate a red envelope indicating the failed delivery. This can be helpful " +"to know that a Sales Order or an Invoice did not reach its final " +"destination." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:223 +msgid "" +"**Original messages**: several business objects have their own alias to " +"create new records in Odoo from incoming emails:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:226 +msgid "" +"Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:228 +msgid "" +"Support channel (to create *Tickets* in `Odoo Helpdesk " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:229 +msgid "" +"Projects (to create new *Tasks* in `Odoo Project `_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:231 +msgid "" +"Job positions (to create *Applicants* in `Odoo Recruitment " +"`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:234 +msgid "" +"Depending on the mail server, there might be several methods to fetch " +"emails. The easiest and most recommended method is to manage one email " +"address per Odoo alias in the mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:237 +msgid "" +"Create the corresponding email addresses in the mail server (**catchall@**, " +"**bounce@**, **sales@**, etc.)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:239 +msgid "" +"Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> " +"General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will " +"change the catchall's domain for the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:242 +msgid "" +"If the database's hosting type is Odoo on-premise, create an " +":guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new " +"incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail " +"Servers --> Incoming Mail Servers --> New` Fill out the form according to " +"the email provider's settings. Leave the :guilabel:`Actions to Perform on " +"Incoming Mails` field blank. Once all the information has been filled out, " +"click on :guilabel:`TEST & CONFIRM`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "Incoming mail server configuration on Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:252 +msgid "" +"If the database's hosting type is Odoo Online or Odoo.sh, redirecting or " +"forwarding incoming messages to Odoo's domain name instead of the external " +"email server is recommended. That way, incoming messages can be received " +"without delay. Redirections for all email addresses should be set to Odoo's " +"domain name in the email server (e.g. `catchall\\@mydomain.ext` to " +"`catchall\\@mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:258 +msgid "" +"All the aliases are customizable in Odoo. Object aliases can be edited from " +"their respective configuration view by navigating to " +":menuselection:`Settings --> Technical Menu --> Email --> Aliases`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:262 +msgid "" +"To edit catchall and bounce aliases, first activate the :ref:`developer mode" +" `. Then, go to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` to customize the aliases " +"(`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should" +" be completed prior to the database going live. If a customer replies after " +"a change is made then the system will not recognize the old alias and the " +"reply won't be received." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:268 +msgid "" +"By default, inbound messages are fetched every 5 minutes for on-premise " +"databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:271 +msgid "" +"This value can be changed in :ref:`developer mode `. Go to " +":menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`" +" and look for :guilabel:`Mail: Fetchmail Service`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:276 +msgid "System parameters that prevent feedback loops" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:278 +msgid "" +"There are two system parameters that help prevent email loops from occurring" +" in Odoo. These parameters were introduced in Odoo 16 to prevent aliases " +"from creating too many records and to prevent feedback loops on the catchall" +" reply-to email address. They are present in database but not in the *System" +" Parameters*. To override the following defaults they need to be added in." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:283 +msgid "The two system parameters are as follows:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:285 +msgid "`mail.incoming.limit.period` (60 minutes by default)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:286 +msgid "`mail.incoming.limit.alias` (5 by default)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:288 +msgid "" +"Add these fields in Odoo by first enabling :ref:`developer mode `, and then navigating to :menuselection:`Settings --> Technical Menu " +"--> Parameters --> System Parameters`. Change the value of these parameters," +" as needed." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:292 +msgid "" +"When an email is received in the Odoo database on the catchall email address" +" or on any alias, Odoo looks at the mail received for the given period of " +"time defined in the system parameter `mail.incoming.limit.period`. If the " +"received email was sent to an alias then Odoo will reference the " +"`mail.incoming.limit.alias` system parameter and determine the value as the " +"number of records this alias is allowed to create in the given period of " +"time (value of `mail.incoming.limit.period`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:298 +msgid "" +"In addition, when email is received to the catchall email address, Odoo will" +" reference the emails received to the database during the set period of time" +" (as stated by the value in the system parameter: " +"`mail.incoming.limit.period`). Odoo will then determine whether any of the " +"emails received match that of the email(s) being received during the " +"specified time-frame, and will prevent a feedback loop from occurring if a " +"duplicate email is detected." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:3 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:5 +msgid "" +"Email templates are saved emails that are used repeatedly to send emails " +"from the database. They allow users to send quality communications, without " +"having to compose the same text repeatedly." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:8 +msgid "" +"Creating different templates that are tailored to specific situations lets " +"users choose the right message for the right audience. This increases the " +"quality of the message and the overall engagement rate with the customer." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:13 +msgid "" +"Email templates in Odoo use QWeb or XML, which allows for editing emails in " +"their final rendering, making customizations more robust, without having to " +"edit any code whatsoever. This means that Odoo can use a Graphical User " +"Interface (GUI) to edit emails, which edits the backend code. When the " +"received email is read by the end user's program, different formatting and " +"graphics will appear in the final form of it." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:19 +msgid "" +"Access email templates in :ref:`developer mode ` by " +"navigating to :menuselection:`Settings app --> Technical menu --> Email --> " +"Email Templates`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:23 +msgid "Editing email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:25 +msgid "" +"The *powerbox* feature can be used when working with email templates. This " +"feature provides the ability to directly edit the formatting and text in an " +"email template, as well as the ability to add links, buttons, appointment " +"options, or images." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:29 +msgid "" +"Additionally, the XML/HTML code of the email template can be edited " +"directly, via the :guilabel:`` icon. Dynamic placeholders (referencing " +"fields within Odoo) are also available for use in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:34 +msgid "Powerbox" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:36 +msgid "" +"The *powerbox* feature is an enriched text editor with various formatting, " +"layout, and text options. It can also be used to add XML/HTML features in an" +" email template. The powerbox feature is activated by typing a forward slash" +" `/` in the body of the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:40 +msgid "" +"When a forward slash `/` is typed in the body of an email template, a drop-" +"down menu appears with the following options:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:43 +msgid ":guilabel:`Structure`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:45 +msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:46 +msgid ":guilabel:`Numbered list`: Create a list with numbering." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:47 +msgid ":guilabel:`Checklist`: Track tasks with a checklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:48 +msgid ":guilabel:`Table`: Insert a table." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:49 +msgid ":guilabel:`Separator`: Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:50 +msgid ":guilabel:`Quote`: Add a blockquote section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:51 +msgid ":guilabel:`Code`: Add a code section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:52 +msgid ":guilabel:`2 columns`: Convert into two columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:53 +msgid ":guilabel:`3 columns`: Convert into three columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:54 +msgid ":guilabel:`4 columns`: Convert into four columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:56 +msgid ":guilabel:`Format`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:58 +msgid ":guilabel:`Heading 1`: Big section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:59 +msgid ":guilabel:`Heading 2`: Medium section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:60 +msgid ":guilabel:`Heading 3`: Small section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:61 +msgid ":guilabel:`Switch direction`: Switch the text's direction." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:62 +msgid ":guilabel:`Text`: Paragraph block." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:64 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:66 +msgid ":guilabel:`Image`: Insert an image." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:67 +msgid ":guilabel:`Article`: Link an article." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:69 +msgid ":guilabel:`Navigation`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:71 +msgid ":guilabel:`Link`: Add a link." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:72 +msgid ":guilabel:`Button`: Add a button." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:73 +msgid ":guilabel:`Appointment`: Add a specific appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:74 +msgid ":guilabel:`Calendar`: Schedule an appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:76 +msgid ":guilabel:`Widgets`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:78 +msgid ":guilabel:`3 Stars`: Insert a rating over three stars." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:79 +msgid ":guilabel:`5 Stars`: Insert a rating over five stars." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:81 +msgid ":guilabel:`Basic Blocks`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:83 +msgid ":guilabel:`Signature`: Insert your signature." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:85 +msgid ":guilabel:`Marketing Tools`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:87 +msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:90 +msgid "" +"To use any of these options, click on the desired feature from the powerbox " +"drop-down menu. To format existing text with a text-related option (e.g. " +":guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the " +"text, then type in the activator key (forward slash) `/`, and select the " +"desired option from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Powerbox feature in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:100 +msgid "" +":ref:`Using dynamic placeholders `" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:103 +msgid "XML/HTML code editor" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:105 +msgid "" +"To access the XML/HTML editor for an email template, first enter " +":ref:`developer mode `. Then, click the :guilabel:`` icon" +" in the upper-right corner of the template, and proceed to edit the " +"XML/HTML. To return to the standard text editor, click the :guilabel:`` " +"icon again." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "HTML editor in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:115 +msgid "" +"The XML/HTML editor should be accessed with caution as this is the backend " +"code of the template. Editing the code can cause the email template to break" +" immediately or when upgrading the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:122 +msgid "Dynamic placeholders" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:124 +msgid "" +"*Dynamic placeholders* reference certain fields within the Odoo database to " +"produce unique data in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:128 +msgid "" +"Many companies like to customize their emails with a personalized piece of " +"customer information to grab attention. This can be accomplished in Odoo by " +"referencing a field within a model by inserting a dynamic placeholder. For " +"example, a customer's name can be referenced in the email from the " +":guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic" +" placeholder for this field is: `{{ object.partner_id }}`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:134 +msgid "" +"Dynamic placeholders are encoded to display fields from within the database." +" Dynamic placeholders can be used in the :guilabel:`Body` " +"(:guilabel:`Content` Tab) of the email template. They can also be used in " +"the fields present in the :guilabel:`Email Configuration` tab, the " +":guilabel:`Subject` of the email, and the :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:139 +msgid "" +"To use the dynamic placeholders in the :guilabel:`Body` of an email open the" +" **powerbox** feature by typing in `/` into the body of the email template " +"under the :guilabel:`Content` tab. Scroll to the bottom of the options list," +" to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic " +"Placeholder`. Then select the dynamic placeholder from a list of available " +"options and follow the prompts to configure it with the desired " +"corresponding Odoo field. Each dynamic placeholder will vary in " +"configuration." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Using dynamic placeholders in an email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:151 +msgid "" +"Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and " +":guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it " +"as a combination to the field that is being created." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:155 +msgid "" +"To search the available fields, simply type in the front-end name (on user-" +"interface) of the field in the search. This will find a result from all of " +"the available fields for the model that the email template is created for." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:160 +msgid "Customizing email templates are out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:163 +msgid "Rich text editor" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:165 +msgid "" +"A rich text editor toolbar can be accessed by highlighting text in the email" +" template. This can be used to change the heading, font size/style, color, " +"add a list type, or a link." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Rich text editor in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:173 +msgid "Resetting email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:175 +msgid "" +"Should the email template not work because the code has been altered it can " +"be reset to restore it back to the out-of-box default template. Simply click" +" on the :guilabel:`Reset Template` button in the upper left-hand of the " +"screen and the template will be reset." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Resetting the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:184 +msgid "Default reply on email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:186 +msgid "" +"Under the :guilabel:`Email Configuration` tab on an email template, there is" +" a :guilabel:`Reply To` field. In this field, add email addresses to which " +"replies are redirected when sending emails en masse using this template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:191 +msgid "" +"Add multiple email addresses by adding a comma `,` between the addresses or " +"dynamic placeholders." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Reply-to field on template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:198 +msgid "" +"The :guilabel:`Reply To` field is **only** used for mass mailing (sending " +"emails in bulk). Bulk emails can be sent in almost every Odoo application " +"that has a list view option." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:201 +msgid "" +"To send mass mails, while in :guilabel:`list` view, check the boxes next to " +"the desired records where the emails are to be sent, click the " +":guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and" +" select the desired email option from the :guilabel:`Action` drop-down menu." +" Email options can vary by the particular list view and application." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:206 +msgid "" +"If it is possible to send an email, a mail composer pop-up window appears, " +"with values that can be defined and customized. This option will be " +"available on the :guilabel:`Action` button on pages where emails can be sent" +" in bulk---for example, on the :guilabel:`Customers` page of the CRM app. " +"This action occurs throughout the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Email composer in mass mailing mode with reply-to highlighted." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:216 +msgid "Transactional emails and corresponding URLs" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:218 +msgid "" +"In Odoo, multiple events can trigger the sending of automated emails. These " +"emails are known as *transactional emails*, and sometimes contain links " +"redirecting to the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:221 +msgid "" +"By default, links generated by the database use the dynamic `web.base.url` " +"key defined in the system parameters. For more information about this, see " +":ref:`system parameters `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:225 +msgid "" +"If the *Website* application is not installed, the `web.base.url` key will " +"always be the default parameter used to generate all the links." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:229 +msgid "" +"The `web.base.url` key can only have a single value, meaning that, in a " +"multi-website or multi-company database environment, even if there is a " +"specific domain name for each website, the links generated to share a " +"document (or the links within a transactional email) may remain the same, " +"regardless of which website/company is related to the sending of the " +"email/document." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:235 +msgid "" +"If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is" +" equal to `https://www.mycompany.com` and there are two separate companies " +"in Odoo with different website URLs: `https://www.mycompany2.com` and " +"`https://www.mycompany1.com`, the links created by Odoo to share a document," +" or send a transactional email, come from the domain: " +"`https://www.mycompany.com`, regardless of which company sends the document " +"or email." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:241 +msgid "" +"This is not always the case, as some Odoo applications (*eCommerce*, for " +"example) have a link established in the database with the *Website* " +"application. In that case, if a specific domain is defined for the website, " +"the URL generated in the email template uses the domain defined on the " +"corresponding website of the company." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:247 +msgid "" +"When a customer makes a purchase on an Odoo *eCommerce* website, the order " +"has an established link with that website. As a result, the links in the " +"confirmation email sent to the customer use the domain name for that " +"specific website." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:252 +msgid "" +"A document shared using the *Documents* application will **always** use the " +"`web.base.url` key, as the document shared is not associated with any " +"particular website. This means that the URL will always be the same (the " +"`web.base.url` key value), no matter what company it's shared from. This is " +"a known limitation." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:257 +msgid "" +"For more information about how to configure domains, check out the " +":doc:`domain name documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:261 +msgid "Updating translations within email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:263 +msgid "" +"In Odoo, email templates are automatically translated for all users in the " +"database for all of the languages installed. Changing the translations " +"shouldn't be necessary. However, if for a specific reason, some of the " +"translations need to be changed, it can be done." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:268 +msgid "" +"Like any modification in the code, if translation changes are not done " +"correctly (for example, modifications leading to bad syntax), it can break " +"the template, and as a result, the template will appear blank." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:272 +msgid "" +"In order to edit translations, first enter :ref:`developer mode `. Then, on the email template, click on the :guilabel:`Edit` button, " +"and then click on the language button, represented by the initials of the " +"language currently being used (e.g. :guilabel:`EN` for English)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Edit the language of a template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:281 +msgid "" +"If there aren't multiple languages installed and activated in the database, " +"or if the user does not have administration access rights, the language " +"button will not appear." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:284 +msgid "" +"A pop-up window with the different languages installed on the database " +"appears. From this pop-up, editing of translations is possible. When the " +"desired changes have been made, click the :guilabel:`Save` button to save " +"the changes." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Translation of the body of the Appointment Booked template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:293 +msgid "" +"When editing the translations, the default language set in the database " +"appears in **bold**." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:3 +msgid "Email issues" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:5 +msgid "" +"This document contains an explanation of the most recurring emailing issues " +"in Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:8 +msgid "Outgoing emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:13 +msgid "Email is not sent" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:15 +msgid "" +"The first indicator showing that an email has not been sent is the presence " +"of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the " +"message, located in the chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Red envelope icon displayed in chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:22 +msgid "" +"Unsent emails also appear in the Odoo email queue. In :ref:`developer mode " +"`, the email queue can be accessed by going to " +":menuselection:`Settings app --> Technical menu --> Email --> Emails`. " +"Unsent emails appear in turquoise, while sent emails appear in grey." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:27 +msgid "Common error messages" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:32 +msgid "Daily limit reached" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Warning in Odoo upon email limit reached." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:38 +msgid "" +"Each email service provider has its own email sending limits. The limits may" +" be daily, hourly, or sometimes, per minute. This is the same for Odoo, " +"which limits a customer's sending to prevent Odoo's email servers from being" +" blacklisted." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:42 +msgid "Here are the default limits for new databases:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:44 +msgid "" +"**200 emails per day** for Odoo Online and Odoo.sh databases with an active " +"subscription." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:45 +msgid "**20 emails per day** for one-app free databases." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:46 +msgid "**50 emails per day** for trial databases." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:47 +msgid "" +"In the case of migration, the daily limit might be reset to 50 emails per " +"day." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:49 +msgid "If the daily limit is reached:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:51 +msgid "" +"Contact the Odoo support team, who may increase the daily limit depending on" +" the following factors:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:54 +msgid "How many users are in the database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:55 +msgid "Which apps are installed?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:56 +msgid "" +"The bounce rate: the percentage of email addresses that did not receive " +"emails because they were returned by a mail server on its way to the final " +"recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:59 +msgid "" +"Use an external outgoing email server to be independent of Odoo's mail limit" +" (refer to the corresponding :doc:`email documentation " +"`)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:62 +msgid "" +"Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the " +"email. In :ref:`developer mode `, go to " +":menuselection:`Settings app --> Technical menu --> Email --> Emails`, then " +"click the :guilabel:`Retry` button next to an unsent email." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:67 +msgid "" +"The daily email limit is comprehensive to the database. By default, any " +"internal message, notification, logged note, etc. counts as an email in the " +"daily limit if it notifies someone via email. This can be mitigated by " +"receiving :ref:`notifications in Odoo " +"`, instead of emails." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:73 +msgid "SMTP error" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:75 +msgid "" +"Simple Mail Transport Protocol (SMTP) error messages explain why an email " +"wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport " +"Protocol)` is a protocol to describe the email structure, and transmits data" +" from messages over the Internet. The error messages generated by email " +"services are helpful tools to diagnose and troubleshoot email problems." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:81 +msgid "" +"This is an example of a 554 SMTP permanent delivery error: `554: delivery " +"error: Sorry, your message to ------@yahoo.com cannot be delivered. This " +"mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this " +"line is a copy of the message.`" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:85 +msgid "" +"The debug menu can be used to investigate SMTP sending issues from a " +"database. To access the menu, :ref:`developer mode ` must be" +" activated. Once activated, navigate to the :menuselection:`Debug Menu` in " +"the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), " +":menuselection:`Debug Menu --> Manage Messages`" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:90 +msgid "" +"The :guilabel:`Manage Messages` menu opens a list of all the messages sent " +"in a particular record. Within each message there is information on sending," +" including the type, and subtype, of the message." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:94 +msgid "" +"Other information includes to whom the message was sent, and whether Odoo " +"received a bounce-back message from an email server." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Manage messages menu option on the debug menu." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:102 +msgid "" +"A user must be on a view in Odoo that has a chatter in order for the " +":guilabel:`Manage Messages` menu option to appear." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:106 +msgid "No error populated" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:108 +msgid "" +"Odoo is not always capable of providing information for the reason it " +"failed. The different email providers implement a personalized policy of " +"bounced emails, and it is not always possible for Odoo to interpret it " +"correctly." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:112 +msgid "" +"If this is a recurring problem with the same client, or the same domain, do " +"not hesitate to contact `Odoo Support `_ for help" +" in finding a reason." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:116 +msgid "" +"One of the most common reasons for an email failing to send with no error " +"message is related to :ref:`SPF ` and/or " +":ref:`DKIM ` configuration. Also, check " +"to make sure the `mail.bounce.alias` is defined in the *system parameters*. " +"Access system parameters in :ref:`developer mode ` by " +"navigating to :menuselection:`Settings app --> Technical menu --> Parameters" +" --> System Parameters`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:124 +msgid "Email is sent late" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:126 +msgid "" +"Email campaigns send at a scheduled time, using a delay pre-programed in the" +" database. Odoo uses a delayed task to send emails that are considered \"not" +" urgent\" (newsletter formats, such as: mass mailing, marketing automation, " +"and events). The system utility **cron** can be used to schedule programs to" +" run automatically at predetermined intervals. Odoo uses that policy in " +"order to avoid cluttering the mail servers and, instead, prioritizes " +"individual communication. This **cron** is called :guilabel:`Mail: Email " +"Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Email scheduled to be sent later." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:140 +msgid "" +"What is a **cron**? A cron is an action that Odoo runs in the background to " +"execute particular code to complete a task." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:144 +msgid "" +"By default, the *Mass Mailing cron* runs every 60 minutes. This can be " +"changed to no less than 5 minutes. However, running the action every 5 " +"minutes would bog down the Odoo database (stress the system), so this is not" +" recommended. To edit the mass mailing cron, select the scheduled action " +":guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary " +"adjustments." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:149 +msgid "" +"Emails that are considered urgent (communication from one person to another," +" such as sales orders, invoices, purchase orders, etc.) are sent " +"immediately." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:153 +msgid "Incoming emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:155 +msgid "" +"When there is an issue with incoming emails, there might not be an " +"indication, per se, in Odoo. It is the sending email client, who tries to " +"contact a database, that will get a bounce-back message (most of the time a " +":guilabel:`550: mailbox unavailable` error message)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:160 +msgid "Email is not received" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:162 +msgid "" +"The steps that should be taken depend on the Odoo platform where the " +"database is hosted." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:164 +msgid "" +"**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:166 +msgid "" +"Logs are a stored collection of all the tasks completed in a database. They " +"are a text-only representation, complete with timestamps of every action " +"taken on the Odoo database. This can be helpful to track emails leaving the " +"database. Failure to send can also be seen by logs that indicate that the " +"message tried to send repeatedly. Logs will show every action to the email " +"servers from the database." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:172 +msgid "" +"The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh " +"dashboard) of an Odoo.sh database contains a list of files containing the " +"logs of the database. The log files are created everyday at 5:00 AM (UTC)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:177 +msgid "" +"The two most recent days (today and yesterday) are not compressed, while the" +" older ones are, in order to save space. The naming of the files for today " +"and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:181 +msgid "" +"For the following days, they are named with their dates, and then " +"compressed. Use the command :command:`grep` and :command:`zgrep` (for the " +"compressed ones) to search through the files." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:185 +msgid "" +"For more information on logs and how to access them via the Odoo.sh " +"dashboard, see :ref:`this administration documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:188 +msgid "" +"For more information on accessing logs via the command line visit :ref:`this" +" developer documentation `." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:191 +msgid "" +"**Odoo Online** users won't have access to the logs. However `Odoo Support " +"`_ can be contacted if there is a recurring issue" +" with the same client or domain." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:196 +msgid "Get help from Odoo support" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:198 +msgid "" +"In order to get helped efficiently, please provide as much information as " +"possible. Here is a list of what can be helpful when reaching out to the " +"Odoo Support team about an issue:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:201 +msgid "" +"Send a copy of the email headers. The `.EML` file (or **headers**) of the " +"email is the file format containing all the technical information required " +"for an investigation. The documentation from the email provider might " +"explain how to access the EML file/header files. Once the headers of the " +"email are obtained, adding it into the Odoo Support ticket is the most " +"efficient way for the Odoo Support team to investigate." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:208 +msgid "" +"`Gmail documentation on headers " +"`_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:209 +msgid "" +"`Outlook documentation on headers `_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:212 +msgid "" +"Explain the exact flow that is being followed to normally receive those " +"emails in Odoo. Here are examples of questions whose answers can be useful:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:215 +msgid "Is this a notification message from a reply being received in Odoo?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:216 +msgid "Is this a message being sent from the Odoo database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:217 +msgid "" +"Is there an incoming email server being used, or is the email somehow being " +"redirected?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:218 +msgid "Is there an example of an email that has been correctly forwarded?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:220 +msgid "Provide answers to the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:222 +msgid "" +"Is it a generic issue, or is it specific to a use case? If specific to a use" +" case, which one exactly?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:224 +msgid "" +"Is it working as expected? In case the email is sent using Odoo, the bounce " +"email should reach the Odoo database, and display the :ref:`red envelope " +"`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:228 +msgid "" +"The bounce system parameter needs to be set in the technical settings in " +"order for the database to correctly receive bounce messages. To access this " +"setting, go to :menuselection:`Settings app --> Technical menu --> " +"Parameters --> System Parameters`. Then select the parameter name " +":guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't " +"already set." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:8 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:10 +msgid "" +"When working with a database, it sometimes is necessary to export your data " +"in a distinct file. Doing so can help to do reporting over your activities " +"(even if Odoo offers a precise and easy reporting tool with each available " +"application)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:14 +msgid "" +"With Odoo, you can export the values from any field in any record. To do so," +" activate the list view on the items that need to be exported, click on " +"*Action*, and, then, on *Export*." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "view of the different things to enable/click to export data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:22 +msgid "" +"Pretty simple, this action still comes with some specificities. In fact, " +"when clicking on *Export*, a pop-up window appears with several options for " +"the data to export:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "" +"overview of all the options to take into account when exporting data in Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:30 +msgid "" +"With the *I want to update data* option ticked, the system only shows the " +"fields which can be imported. This is very helpful in case you want to " +"update existing records. Basically, this works like a filter. Leaving the " +"box unticked gives way more field options because it shows all the fields, " +"not just the ones which can be imported." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:36 +msgid "" +"When exporting, you can choose between two formats: .csv and .xls. With " +".csv, items are separated with a comma, while .xls holds information about " +"all the worksheets in a file, including both content and formatting." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:39 +msgid "" +"Those are the items you may want to export. Use the arrows to display more " +"sub-field options. Of course, you can use the search bar to find specific " +"fields more easily. To use the search option more efficiently, display all " +"the fields by clicking on all the arrows!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:44 +msgid "The + button is there to add fields to the \"to export\" list." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:45 +msgid "" +"The \"handles\" next to the selected fields allow you to move the fields up " +"and down to change the order in which they must be displayed in the exported" +" file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:48 +msgid "The trashcan is there if you need to remove fields." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:49 +msgid "" +"For recurring reports, it might be interesting to save export presets. " +"Select all the needed ones and click on the template bar. There, click on " +"*New template* and give a name to yours. The next time you need to export " +"the same list, simply select the related template." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:56 +msgid "" +"It’s good to keep the field’s external identifier in mind. For example, " +"*Related Company* is equal to *parent_id*. Doing so helps export only what " +"you would like to import next." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:63 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:66 +msgid "How to start" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:68 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:72 +msgid "" +"Open the view of the object you want to populate and click on " +":menuselection:`Favorites --> Import records`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:78 +msgid "" +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:83 +msgid "How to adapt the template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:85 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:86 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:87 +#: ../../content/applications/general/export_import_data.rst:376 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:92 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:100 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:104 +msgid "How to import from another application" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:106 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:114 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:120 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:122 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:131 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:139 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:141 +msgid "" +"Odoo can automatically detect if a column is a date, and it will try to " +"guess the date format from a set of most commonly used date formats. While " +"this process can work for many date formats, some date formats will not be " +"recognized. This can cause confusion due to day-month inversions; it is " +"difficult to guess which part of a date format is the day and which part is " +"the month in a date such as '01-03-2016'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:147 +msgid "" +"To view which date format Odoo has found from your file you can check the " +"**Date Format** that is shown when clicking on **Options** under the file " +"selector. If this format is incorrect you can change it to your liking using" +" the *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:152 +msgid "" +"If you are importing an excel (.xls, .xlsx) file, you can use date cells to " +"store dates as the display of dates in excel is different from the way it is" +" stored. That way you will be sure that the date format is correct in Odoo " +"whatever your locale date format is." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:157 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:159 +msgid "" +"Yes, we fully support numbers with parenthesis to represent negative sign as" +" well as numbers with currency sign attached to them. Odoo also " +"automatically detect which thousand/decimal separator you use (you can " +"change those under **options**). If you use a currency symbol that is not " +"known to Odoo, it might not be recognized as a number though and it will " +"crash." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:164 +msgid "" +"Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:166 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:167 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:168 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:169 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:170 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:171 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:172 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:174 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:176 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:177 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:180 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:182 +msgid "" +"By default the Import preview is set on commas as field separators and " +"quotation marks as text delimiters. If your csv file does not have these " +"settings, you can modify the File Format Options (displayed under the Browse" +" CSV file bar after you select your file)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:186 +msgid "" +"Note that if your CSV file has a tabulation as separator, Odoo will not " +"detect the separations. You will need to change the file format options in " +"your spreadsheet application. See the following question." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:191 +msgid "" +"How can I change the CSV file format options when saving in my spreadsheet " +"application?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:193 +msgid "" +"If you edit and save CSV files in spreadsheet applications, your computer's " +"regional settings will be applied for the separator and delimiter. We " +"suggest you use OpenOffice or LibreOffice Calc as they will allow you to " +"modify all three options (in :menuselection:`'Save As' dialog box --> Check " +"the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:198 +msgid "" +"Microsoft Excel will allow you to modify only the encoding when saving (in " +":menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> " +"Encoding tab`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:202 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:204 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When you" +" want to import such fields, Odoo will have to recreate links between the " +"different records. To help you import such fields, Odoo provides three " +"mechanisms. You must use one and only one mechanism per field you want to " +"import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:209 +msgid "" +"For example, to reference the country of a contact, Odoo proposes you 3 " +"different fields to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:211 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:212 +msgid "" +"Country/Database ID: the unique Odoo ID for a record, defined by the ID " +"postgresql column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:213 +msgid "" +"Country/External ID: the ID of this record referenced in another application" +" (or the .XML file that imported it)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:216 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:218 +msgid "Country: Belgium" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:219 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:220 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:222 +msgid "" +"According to your need, you should use one of these 3 ways to reference " +"records in relations. Here is when you should use one or the other, " +"according to your need:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:225 +msgid "" +"Use Country: This is the easiest way when your data come from CSV files that" +" have been created manually." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:227 +msgid "" +"Use Country/Database ID: You should rarely use this notation. It's mostly " +"used by developers as it's main advantage is to never have conflicts (you " +"may have several records with the same name, but they always have a unique " +"Database ID)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:230 +msgid "" +"Use Country/External ID: Use External ID when you import data from a third " +"party application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:232 +msgid "" +"When you use External IDs, you can import CSV files with the \"External ID\"" +" column to define the External ID of each record you import. Then, you will " +"be able to make a reference to that record with columns like " +"\"Field/External ID\". The following two CSV files give you an example for " +"Products and their Categories." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:237 +msgid "" +":download:`CSV file for categories " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:240 +msgid "" +":download:`CSV file for Products " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:244 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:246 +msgid "" +"If for example you have two product categories with the child name " +"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " +"Products/Sellable\"), your validation is halted but you may still import " +"your data. However, we recommend you do not import the data because they " +"will all be linked to the first 'Sellable' category found in the Product " +"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of " +"the duplicates' values or your product category hierarchy." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:252 +msgid "" +"However if you do not wish to change your configuration of product " +"categories, we recommend you use make use of the external ID for this field " +"'Category'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:256 +msgid "" +"How can I import a many2many relationship field (e.g. a customer that has " +"multiple tags)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:258 +msgid "" +"The tags should be separated by a comma without any spacing. For example, if" +" you want your customer to be linked to both tags 'Manufacturer' and " +"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column" +" of your CSV file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:262 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:266 +msgid "" +"How can I import a one2many relationship (e.g. several Order Lines of a " +"Sales Order)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:268 +msgid "" +"If you want to import sales order having several order lines; for each order" +" line, you need to reserve a specific row in the CSV file. The first order " +"line will be imported on the same row as the information relative to order. " +"Any additional lines will need an additional row that does not have any " +"information in the fields relative to the order. As an example, here is " +"``purchase.order_functional_error_line_cant_adpat.CSV`` file of some " +"quotations you can import, based on demo data." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:275 +msgid "" +":download:`File for some Quotations " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:277 +msgid "" +"The following CSV file shows how to import purchase orders with their " +"respective purchase order lines:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:280 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:282 +msgid "" +"The following CSV file shows how to import customers and their respective " +"contacts:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:284 +msgid "" +":download:`Customers and their respective contacts " +"`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:287 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:289 +msgid "" +"If you import a file that contains one of the column \"External ID\" or " +"\"Database ID\", records that have already been imported will be modified " +"instead of being created. This is very useful as it allows you to import " +"several times the same CSV file while having made some changes in between " +"two imports. Odoo will take care of creating or modifying each record " +"depending if it's new or not." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:294 +msgid "" +"This feature allows you to use the Import/Export tool of Odoo to modify a " +"batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:298 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:300 +msgid "" +"If you do not set all fields in your CSV file, Odoo will assign the default " +"value for every non defined fields. But if you set fields with empty values " +"in your CSV file, Odoo will set the EMPTY value in the field, instead of " +"assigning the default value." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:305 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:307 +msgid "" +"If you need to import data from different tables, you will have to recreate " +"relations between records belonging to different tables. (e.g. if you import" +" companies and persons, you will have to recreate the link between each " +"person and the company they work for)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:311 +msgid "" +"To manage relations between tables, you can use the \"External ID\" " +"facilities of Odoo. The \"External ID\" of a record is the unique identifier" +" of this record in another application. This \"External ID\" must be unique " +"across all the records of all objects, so it's a good practice to prefix " +"this \"External ID\" with the name of the application or table. (like " +"'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:317 +msgid "" +"As an example, suppose you have a SQL database with two tables you want to " +"import: companies and persons. Each person belong to one company, so you " +"will have to recreate the link between a person and the company he work for." +" (If you want to test this example, here is a :download:`dump of such a " +"PostgreSQL database `)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:322 +msgid "" +"We will first export all companies and their \"External ID\". In PSQL, write" +" the following command:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:328 +msgid "This SQL command will create the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:337 +msgid "" +"To create the CSV file for persons, linked to companies, we will use the " +"following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:343 +msgid "It will produce the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:353 +msgid "" +"As you can see in this file, Fabien and Laurence are working for the Bigees " +"company (company_1) and Eric is working for the Organi company. The relation" +" between persons and companies is done using the External ID of the " +"companies. We had to prefix the \"External ID\" by the name of the table to " +"avoid a conflict of ID between persons and companies (person_1 and company_1" +" who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:359 +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 "" + +#: ../../content/applications/general/export_import_data.rst:364 +msgid "How to adapt an import template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:366 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). You can open them with " +"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, " +"etc.)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:372 +msgid "How to customize the file" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:374 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:381 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:388 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:392 +msgid "Why an “ID” column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:394 +msgid "" +"The **ID** (External ID) is an unique identifier for the line item. Feel " +"free to use the one of your previous software to ease the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:397 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:399 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:400 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:403 +msgid "How to import relation fields" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:405 +msgid "" +"An Odoo object is always related to many other objects (e.g. a product is " +"linked to product categories, attributes, vendors, etc.). To import those " +"relations you need to import the records of the related object first from " +"their own list menu." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:409 +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 "" + +#: ../../content/applications/general/in_app_purchase.rst:3 +msgid "In-App Purchase (IAP)" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:5 +msgid "" +"In-App Purchases (IAP) gives access to additional services through Odoo. For" +" instance, it allows you to send SMS Text Messages or to send Invoices by " +"post directly from your database." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:11 +msgid "Buying Credits" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:13 +msgid "" +"Each IAP Service relies on prepaid credits to work and has its own pricing. " +"To consult your current balance or to recharge your account, go to " +":menuselection:`Settings --> Odoo IAP --> View my Services`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:21 +msgid "" +"If you are on Odoo Online and have the Enterprise version, you benefit from " +"free credits to test our IAP features." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:25 +msgid "IAP accounts" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:27 +msgid "" +"Credits to use IAP services are stored on IAP accounts, which are specific " +"to each service. By default, IAP accounts are common to all companies, but " +"can be restricted to specific ones. Activate the :ref:`developer mode " +"`, then go to :menuselection:`Technical Settings --> IAP " +"Account`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:36 +msgid "" +"An IAP account can be disabled by appending `+disabled` to its token. " +"Reverting this change will re-enable the account." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:40 +msgid "IAP Portal" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:42 +msgid "" +"The IAP Portal is a platform regrouping your IAP Services. It is accessible " +"from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From " +"there, you can view your current balance, recharge your credits and set a " +"reminder when your balance falls below a threshold." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:50 +msgid "Get notified when credits are low" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:52 +msgid "" +"To be notified when it’s time to recharge your credits, you can go to your " +"IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my " +"Services`, unfold a service and check the Receive threshold warning option. " +"Then, you can provide a minimum amount of credits and email addresses. Now, " +"every time that the limit is reached, an automatic reminder will be sent by " +"email!" +msgstr "" + +#: ../../content/applications/general/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/general/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/general/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/general/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/general/reporting.rst-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/general/reporting.rst-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/general/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/general/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/general/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/general/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/general/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/general/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/general/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/general/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/general/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/general/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/general/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:169 +#: ../../content/applications/general/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/general/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/general/search.rst:3 +msgid "Search and filter records" +msgstr "" + +#: ../../content/applications/general/search.rst:5 +msgid "" +"Odoo uses filters to include only the most relevant records depending on the" +" purpose of the view you are on. However, you can edit the default filter or" +" search for specific values." +msgstr "" + +#: ../../content/applications/general/search.rst:11 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/general/search.rst:13 +msgid "" +"You can modify the default selection of records by clicking " +":guilabel:`Filters` and selecting one or several **preconfigured filters**." +msgstr "" + +#: ../../content/applications/general/search.rst:17 +msgid "" +"On the Sales Analysis report, only records at the sales order stage are " +"selected by default. However, you could *also* include records at the " +"quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could " +"*only* include records from a specific year, for example *2022*, by " +"selecting :menuselection:`Order Date --> 2022`." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:27 +msgid "" +"If you select preconfigured filters from the same group (i.e., that are " +"*not* separated by an horizontal line), the records can match *any* " +"condition to be included. However, if you select filters from different " +"groups, the records have to match *all* condition to be included." +msgstr "" + +#: ../../content/applications/general/search.rst:34 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/general/search.rst:36 +msgid "" +"You can create custom filters using most fields present on the model by " +"clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, " +"an operator, a value, and clicking :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/search.rst:41 +msgid "" +"You could *only* include records from a single salesperson on the Sales " +"Analysis report, for example *Mitchell Admin*, by selecting " +":guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the " +"operator, and typing `Mitchell Admin` as the value." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Using a custom filter on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:50 +msgid "" +"If the records should *only* match one of several conditions, click " +":guilabel:`Add a condition` before applying a custom filter. If the records " +"should match *all* conditions, add new custom filters instead." +msgstr "" + +#: ../../content/applications/general/search.rst:57 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/general/search.rst:59 +msgid "" +"You can use the search field to quickly look for specific values and add " +"them as a filter. Either type the full value you are searching for and " +"select the desired field, or type a part of the value, click the dropdown " +"button (:guilabel:`⏵`) before the chosen field, and select the exact value " +"you are looking for." +msgstr "" + +#: ../../content/applications/general/search.rst:65 +msgid "" +"Instead of adding a custom filter to select records where *Mitchell Admin* " +"is the salesperson on the Sales Analysis report, you could search for " +"`Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search" +" Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:75 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a custom filter. If you enter a partial value and directly select the" +" desired field, *all* records containing the characters you typed for the " +"selected field will be included." +msgstr "" + +#: ../../content/applications/general/search.rst:82 +msgid "Group records" +msgstr "" + +#: ../../content/applications/general/search.rst:84 +msgid "" +"You can click :guilabel:`Group By` below the search field to cluster records" +" together according to one of the **preconfigured groups**." +msgstr "" + +#: ../../content/applications/general/search.rst:88 +msgid "" +"You could group the records by salesperson on the Sales Analysis report by " +"clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No " +"records are filtered out." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:95 +msgid "" +"You can **customize groups** by using a wide selection of fields present on " +"the model. To do so, click :menuselection:`Group By --> Add Custom Group`, " +"select a field, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/search.rst:99 +msgid "" +"You can use several groups at the same time. The first group you select is " +"the main cluster, the next one you add further divides the main group's " +"categories, and so on." +msgstr "" + +#: ../../content/applications/general/users.rst:5 +msgid "Users and companies" +msgstr "" + +#: ../../content/applications/general/users.rst:7 +msgid "" +"Odoo defines a *user* as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:3 +msgid "Access Rights" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:5 +msgid "" +"Activate the :ref:`developer mode `, then go to " +":menuselection:`Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:9 +msgid "Groups" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:14 +msgid "" +"When choosing the groups the user can have access under :ref:`Access Rights " +"`, details of the rules and inheritances of that group" +" are not shown, so this is when the menu *Groups* comes along. *Groups* are " +"created to define rules to models within an application." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:16 +msgid "" +"Under *Users*, have a list of the current ones. The ones with administrative" +" rights are shown in black." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab users in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:22 +msgid "" +"*Inherited* means that users added to this application group are " +"automatically added to the following ones. In the example below, users who " +"have access to the group *Administrator* of *Sales* also have access to " +"*Website/Restricted Editor* and *Sales/User: All Documents*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab inherited in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:32 +msgid "" +"Remember to always test the settings being changed in order to ensure that " +"they are being applied to the needed and right users." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:35 +msgid "" +"The *Menus* tab is where you define which menus (models) the user can have " +"access to." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab menus in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:42 +msgid "" +"*Access Rights* rules are the first level of rights. The field is composed " +"of the object name, which is the technical name given to a model. For each " +"model, enable the following options as appropriate:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:45 +msgid "*Read*: the values of that object can be only seen by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:46 +msgid "*Write*: the values of that object can be edited by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:47 +msgid "*Create*: values for that object can be created by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:48 +msgid "*Delete*: the values of that object can be deleted by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab access rights in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:55 +msgid "" +"As a second layer of editing and visibility rules, *Record Rules* can be " +"formed. They overwrite, or refine, the *Access Rights*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:58 +msgid "" +"A record rule is written using a *Domain*. Domains are conditions used to " +"filter or searching data. Therefore, a domain expression is a list of " +"conditions. For each rule, choose among the following options: *Read*, " +"*Write*, *Create* and *Delete* values." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab record rules in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:65 +msgid "" +"Making changes in access rights can have a big impact on the database. For " +"this reason, we recommend you to contact your Odoo Business Analyst or our " +"Support Team, unless you have knowledge about Domains in Odoo." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:3 +msgid "Companies" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:5 +msgid "" +"A centralized management environment allows you to select multiple companies" +" simultaneously and set their specific warehouses, customers, equipment, and" +" contacts. It provides you the ability to generate reports of aggregated " +"figures without switching interfaces, which facilitates daily tasks and the " +"overall management process." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:13 +msgid "Manage companies and records" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:15 +msgid "" +"Go to :menuselection:`Settings --> Manage Companies` and fill in the form " +"with your company’s information. If a *Parent Company* is selected, records " +"are shared between the two companies (as long as both environments are " +"active)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "Overview of a new company's form in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:24 +msgid "" +"Activate the :ref:`developer mode ` to choose a *Favicon* " +"for each of your companies, and easily identify them by the browser tabs. " +"Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and " +"ICO are extensions accepted." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:0 +msgid "" +"View of a web browser and the favicon for a specific company chosen in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:33 +msgid "" +"Switch between or select multiple companies by enabling their selection " +"boxes to activate them. The grayed company is the one which environment is " +"in use. To switch environments, click on the company’s name. In the example " +"below, the user has access to three companies, two are activated, and the " +"environment in use is of *JS Store US*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of the companies menu through the main dashboard in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:42 +msgid "" +"Data such as Products, Contacts, and Equipment can be shared or set to be " +"shown for a specific company only. To do so, on their forms, choose between:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:45 +msgid "*A blank field*: the record is shared within all companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:46 +msgid "" +"*Adding a company*: the record is visible to users logged in to that " +"specific company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of a product's form emphasizing the company field in Odoo Sales" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:53 +msgid "Employees' access" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:55 +msgid "" +"Once companies are created, manage your employees' :doc:`Access Rights " +"` for *Multi Companies*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of an user form emphasizing the multi companies field under the access rights tabs\n" +"in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:64 +msgid "" +"If a user has multiple companies *activated* on his database, and he is " +"**editing** a record, the editing happens on the record's related company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:67 +msgid "" +"Example: if editing a sale order issued under JS Store US while working on " +"the JS Store Belgium environment, the changes are applied under JS Store US " +"(the company from which the sale order was issued)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:68 +msgid "When **creating** a record, the company taken into account is:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:70 +msgid "The current company (the one active) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:71 +msgid "No company is set (on products and contacts’ forms for example) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:72 +msgid "" +"The company set is the one linked to the document (the same as if a record " +"is being edited)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:75 +msgid "Documents’ format" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:77 +msgid "" +"To set documents' formats according to each company, *activate* and *select*" +" the respective one and, under *Settings*, click on *Configure Document " +"Layout*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the document layout field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:85 +msgid "Inter-Company Transactions" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:87 +msgid "" +"First, make sure each one of your companies is properly set in relation to:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:89 +msgid "" +":doc:`Chart of Accounts " +"<../../finance/accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:90 +msgid ":doc:`Taxes <../../finance/accounting/taxes>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:91 +msgid "" +":doc:`Fiscal Positions <../../finance/accounting/taxes/fiscal_positions>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:92 +msgid ":doc:`Journals <../../finance/accounting/bank>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:93 +msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:94 +msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:96 +msgid "" +"Now, activate the *Inter-Company Transactions* option under *Settings*. With" +" the respective company *activated* and *selected*, choose if you would like" +" operations between companies to be synchronized at an invoice/bills level " +"or at a sales/purchase orders level." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the inter company transaction field in" +" Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:104 +msgid "" +"**Synchronize invoice/bills**: generates a bill/invoice when a company " +"confirms a bill/invoice for the selected company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:107 +msgid "" +"*Example:* an invoice posted on JS Store Belgium, for JS Store US, " +"automatically creates a vendor bill on the JS Store US, from the JS Store " +"Belgium." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:114 +msgid "" +"**Synchronize sales/purchase order**: generates a drafted purchase/sales " +"order using the selected company warehouse when a sales/purchase order is " +"confirmed for the selected company. If instead of a drafted purchase/sales " +"order you rather have it validated, enable *Automatic Validation*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:118 +msgid "" +"*Example:* when a sale order for JS Store US is confirmed on JS Store " +"Belgium, a purchase order on JS Store Belgium is automatically created (and " +"confirmed if the *Automatic Validation* feature was enabled)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the purchase created on JS Store US from JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:127 +msgid "" +"Products have to be configured as *Can be sold* and must be shared between " +"the companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:130 +msgid "" +"Remember to test all workflows as an user other than the administrator." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:133 +msgid ":doc:`Multi-company Guidelines `" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:134 +msgid ":doc:`../../finance/accounting/get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/general/users/language.rst:3 +msgid "Change language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:5 +msgid "" +"Odoo provides you with the option to manage Odoo in different languages, and" +" each user can use Odoo in his own language ." +msgstr "" + +#: ../../content/applications/general/users/language.rst:9 +msgid "Load your desired language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:11 +msgid "" +"The first thing to do is to load your desired language on your Odoo " +"instance." +msgstr "" + +#: ../../content/applications/general/users/language.rst:14 +msgid "" +"From the general dashboard click on the **Settings** app; on the top left of" +" the page select :menuselection:`Translations --> Load a Translation`, " +"select a language to install and click on **LOAD.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:23 +msgid "" +"If you check the \"Websites to translate\" checkbox you will have the option" +" to change the navigation language on your website." +msgstr "" + +#: ../../content/applications/general/users/language.rst:27 +msgid "Change your language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:29 +msgid "" +"You can change the language to the installed language by going to the drop-" +"down menu at the top right side of the screen, choose **Preferences**." +msgstr "" + +#: ../../content/applications/general/users/language.rst:36 +msgid "" +"Then change the Language setting to your installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:42 +msgid "Open a new menu to view the changes." +msgstr "" + +#: ../../content/applications/general/users/language.rst:45 +msgid "Change another user's language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:47 +msgid "" +"Odoo also gives you the possibility for each user to choose his preferred " +"language." +msgstr "" + +#: ../../content/applications/general/users/language.rst:50 +msgid "" +"To change the language for a different user, choose :menuselection:`Users " +"--> Users` from the Settings app. Here you have a list of all users and you " +"can choose the user who you'd like to change the language for. Select the " +"user and click on **Edit** in the top left corner. Under Preferences you can" +" change the Language to any previously installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:61 +msgid ":doc:`../../websites/website/configuration/translate`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:3 +msgid "Manage users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:5 +msgid "" +"Odoo defines a **user** as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:10 +msgid ":doc:`language`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:11 +msgid ":doc:`access_rights`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:16 +msgid "Add individual users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:18 +msgid "" +"Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of the settings page emphasizing the manage users field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:27 +msgid "" +"Fill in the form with the needed information. Under the tab :doc:`Access " +"Rights ` choose the group within each application the user " +"can have access to." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:28 +msgid "" +"The list of applications shown is based on the applications installed on the" +" database." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the access rights tab in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:34 +msgid "" +"When you are done editing the page and have *Saved* it, an invitation email " +"is automatically sent to the user. The user must click on it to accept the " +"invitation and create a login." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form with a notification that the invitation email has been" +" sent in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:42 +msgid "" +"Remember that subscription prices follow the number of users. Refer to our " +"`pricing page `_ for more information." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:46 +msgid "" +"With the :ref:`developer mode ` activated, *User Types* can " +"be selected." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form in developer mode emphasizing the user type field in " +"Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:53 +msgid "" +"The *Portal* and *Public* options do not allow you to choose access rights. " +"Members have specific ones (such as record rules and restricted menus) and " +"usually do not belong to the usual Odoo groups." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:60 +msgid "Deactivate users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:62 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, open the " +"user you want to deactivate, click on *Action*, and then on *Archive*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:66 +msgid "**Never** deactivate the main user (*admin*)." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:71 +msgid "Passwords management" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:76 +msgid "Reset passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:81 +msgid "Enable password resets from login page" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:83 +msgid "It is possible to enable password resets directly from the login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:85 +msgid "" +"To do so, go to :menuselection:`Settings --> Permissions`, activate " +"**Password Reset** and *Save*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Enabling Password Reset in Odoo Settings" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:94 +msgid "Send reset instructions to users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:96 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, select the " +"user out of the list and click on *Send Password Reset Instructions* on its " +"user form. An email is automatically sent to them." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:101 +msgid "" +"The *Send Password Reset Instructions* button only appears if the Odoo " +"invitation email has already been confirmed by the user." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:104 +msgid "" +"This email contains all the instructions needed to reset the password, along" +" with a link redirecting the user to an Odoo login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Example of an email with a password reset link for an Odoo account" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:114 +msgid "Change users’ passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:116 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users` and select " +"a user to access its form. Click on the *Action* button and select *Change " +"Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Change another user's password on Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:123 +msgid "Enter a new password and confirm by clicking on *Change Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:126 +msgid "" +"This operation only modifies the password of the users locally and does not " +"affect their odoo.com account. If you want to change the odoo.com password, " +"you can :ref:`send the password reset instructions `." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:130 +msgid "" +"Click on *Change Password* one more time. You are then redirected to an Odoo" +" login page where you can reaccess your database using your new password." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:136 +msgid "Multi Companies" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:138 +msgid "" +"The *Multi Companies* field allows you to set to which of the multiple " +"companies database you hold the user can have access." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:142 +msgid "" +"Note that if not handled correctly, it may be the source of a lot of " +"inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is" +" required. For technical explanations refer to :doc:`this " +"` documentation." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:152 +msgid ":doc:`companies`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:3 +msgid "Odoo.com account changes" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:5 +msgid "" +"This documentation is dedicated to edits made to an Odoo.com account. The " +"following processes describe how to delete an Odoo.com account, and how to " +"change the password on an Odoo.com account." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:9 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:11 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:15 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:20 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:23 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:30 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:34 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:36 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:41 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:47 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:51 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:55 +#: ../../content/applications/general/users/portal.rst:143 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:57 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:62 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:65 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:71 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:74 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:76 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:77 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:78 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:3 +msgid "Portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:7 +msgid "" +"Portal access is given to users who need the ability to view certain " +"documents or information within an Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:10 +msgid "" +"Some common use cases for providing portal access include allowing customers" +" to read/view any or all of the following in Odoo:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:13 +msgid "leads/opportunities" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:14 +msgid "quotations/sales orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:15 +msgid "purchase orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:16 +msgid "invoices & bills" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:17 +msgid "projects" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:18 +msgid "tasks" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:19 +msgid "timesheets" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:20 +msgid "tickets" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:21 +msgid "signatures" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:22 +msgid "subscriptions" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:25 +msgid "" +"Portal users only have read/view access, and will not be able to edit any " +"documents in the database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:29 +msgid "Provide portal access to customers" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:31 +msgid "" +"From the main Odoo dashboard, select the :guilabel:`Contacts` application. " +"If the contact is not yet created in the database, click on the " +":guilabel:`Create` button, enter the details of the contact, and then click " +":guilabel:`Save`. Otherwise, choose an existing contact, and then click on " +"the :guilabel:`Action` drop-down menu located at the top-center of the " +"interface." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "Use the Contacts application to give portal access to users." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:40 +msgid "" +"Then select :guilabel:`Grant portal access`. A pop-up window appears, " +"listing three fields:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:42 +msgid "" +":guilabel:`Contact`: the recorded name of the contact in the Odoo database" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:43 +msgid "" +":guilabel:`Email`: the contact's email address that they will use to log " +"into the portal" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:44 +msgid ":guilabel:`In Portal`: whether or not the user has portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:46 +msgid "" +"To grant portal access, first enter the contact's :guilabel:`Email` they " +"will use to log into the portal. Then, check the box under the :guilabel:`In" +" Portal` column. Optionally, add text to the invitation message the contact " +"will receive. Then click :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "" +"An email address and corresponding checkbox for the contact need to be filled in before\n" +"sending a portal invitation." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:55 +msgid "" +"An email will be sent to the specified email address, indicating that the " +"contact is now a portal user for that Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:59 +msgid "" +"To grant portal access to multiple users at once, navigate to a company " +"contact, then click :menuselection:`Action --> Grant portal access` to view " +"a list of all of the company's related contacts. Check the box under the " +":guilabel:`In Portal` column for all the contacts that need portal access, " +"then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:65 +msgid "" +"At any time, portal access can be revoked by navigating to the contact, " +"clicking :menuselection:`Action --> Grant portal access`, and then " +"unselecting the checkbox under the :guilabel:`In Portal` column and clicking" +" :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:72 +msgid "Change portal username" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:74 +msgid "" +"There may be times when a portal user wants to change their user login. This" +" can be done by any user in the database with administrator access rights. " +"The following process outlines the necessary steps to change the portal user" +" login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:79 +msgid "" +":doc:`See the documentation on setting access rights " +"`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:82 +msgid "" +"First, navigate to :menuselection:`Settings app --> Users`. Then, under " +":guilabel:`Filters`, select :guilabel:`Portal Users`, or select " +":guilabel:`Add Custom Filter` and set the following configuration " +":guilabel:`Groups` > :guilabel:`contains` > `portal`. After making this " +"selection, search for (and open) the portal user that needs to be edited." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:87 +msgid "" +"Next, click :guilabel:`Edit` (if necessary), click into the :guilabel:`Email" +" Address` field, and proceed to make any necessary changes to this field. " +"The :guilabel:`Email Address` field is used to log into the Odoo portal." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:92 +msgid "" +"Changing the :guilabel:`Email Address` (or login) only changes the " +"*username* on the customer's portal login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:95 +msgid "" +"In order to change the contact email, this change needs to take place on the" +" contact template in the *Contacts* app. Alternatively, the customer can " +"change their email directly from the portal, but the login **cannot** be " +"changed. :ref:`See change customer info `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:100 +msgid "Customer portal changes" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:102 +msgid "" +"There may be times when the customer would like to make changes to their " +"contact information, password/security, or payment information attached to " +"the portal account. This can be performed by the customer from their portal." +" The following process is how a customer can change their contact " +"information." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:110 +msgid "Change customer info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:112 +msgid "" +"First enter the username and password (login) into the database login page " +"to access the portal user account. A portal dashboard will appear upon " +"successfully logging in. Portal documents from the various installed Odoo " +"applications will appear with the number count of each." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:117 +msgid ":ref:`Portal access documentation `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:119 +msgid "" +"Next, navigate to the upper-right corner of the portal, and click the " +":guilabel:`Edit` button, next to the :guilabel:`Details` section. Then, " +"change the pertinent information, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:124 +msgid "Change password" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:126 +#: ../../content/applications/general/users/portal.rst:145 +#: ../../content/applications/general/users/portal.rst:162 +msgid "" +"First enter the username and password (login) into the database login page " +"to access the portal user account. A portal dashboard will appear upon " +"successfully logging in." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:129 +msgid "" +"If the customer would like to change their password for portal access, click" +" on the :guilabel:`Edit Security Settings` link, below the " +":guilabel:`Account Security` section. Then, make the necessary changes, by " +"typing in the current :guilabel:`Password`, :guilabel:`New Password`, and " +"verify the new password. Lastly, click on :guilabel:`Change Password` to " +"complete the password change." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:135 +msgid "" +"If a customer would like to change the login, as documented above, contact " +"the Odoo database point-of-contact. :ref:`See above documentation on " +"changing the portal username `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:139 +msgid "" +"Passwords for portal users and Odoo.com users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:148 +msgid "" +"If the customer would like to turn on two-factor authentication (2FA) for " +"portal access, click on the :guilabel:`Edit Security Settings` link, below " +"the :guilabel:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:151 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Confirm the current portal password in the " +":guilabel:`Password` field. Then, click on :guilabel:`Confirm Password`. " +"Next, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-" +"factor authentication)` app (Google Authenticator, Authy, etc.), by scanning" +" the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:157 +msgid "" +"Finally, click :guilabel:`Enable two-factor authentication` to complete the " +"setup." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:160 +msgid "Change payment info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:165 +msgid "" +"If the customer would like to manage payment options, navigate to the " +":guilabel:`Manage payment methods` in the menu on the right. Then, add the " +"new payment information, and select :guilabel:`Add new card`." +msgstr "" + +#: ../../content/applications/general/voip.rst:5 +msgid "VoIP (Voice over Internet Protocol)" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:3 +msgid "Configure your VoIP Asterisk server for Odoo" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:9 +msgid "Dependencies" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:13 +msgid "wget" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:14 +msgid "gcc" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:15 +msgid "g++" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:38 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:44 +msgid "**run:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:50 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:58 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:64 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:70 +msgid "**The result should be:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:87 +msgid "Asterisk" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:89 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there `_." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:92 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:98 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:104 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:110 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:116 +msgid "" +"In the menuselect, go to the resources option and ensure that res_srtp is " +"enabled. If there are 3 x’s next to res_srtp, there is a problem with the " +"srtp library and you must reinstall it. Save the configuration (press x). " +"You should also see stars in front of the res_pjsip lines." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:120 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:126 +msgid "" +"If you need the sample configs you can run 'make samples' to install the " +"sample configs. If you need to install the Asterisk startup script you can " +"run 'make config'." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:130 +msgid "DTLS Certificates" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:132 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:138 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:144 +msgid "" +"Create the DTLS certificates (replace pbx.mycompany.com with your ip address" +" or dns name, replace My Super Company with your company name):" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:152 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:154 +msgid "" +"For WebRTC, a lot of the settings that are needed MUST be in the peer " +"settings. The global settings do not flow down into the peer settings very " +"well. By default, Asterisk config files are located in /etc/asterisk/. Start" +" by editing http.conf and make sure that the following lines are " +"uncommented:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:166 +msgid "" +"Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and " +"icesupport to be enabled. In most cases, directmedia should be disabled. " +"Also under the WebRTC client, the transport needs to be listed as ‘ws’ to " +"allow websocket connections. All of these config lines should be under the " +"peer itself; setting these config lines globally might not work:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:197 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:204 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:213 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:215 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:221 +msgid "" +"The SIP Login/Browser's Extension is the number you configured previously in" +" the sip.conf file (in our example: 1060)." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:224 +msgid "The SIP Password is the secret you chose in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:226 +msgid "" +"The extension of your office's phone is not a required field but it is used " +"if you want to transfer your call from Odoo to an external phone also " +"configured in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:230 +msgid "" +"The configuration should also be done in the General Settings under the " +"\"Integrations\" section." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:235 +msgid "" +"The PBX Server IP should be the same as the IP you define in the http.conf " +"file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:237 +msgid "" +"The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to" +" be the same as the IP defined previously and \"XXXX\" needs to be the port " +"defined in the http.conf file." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:3 +msgid "Use VoIP services in Odoo with Axivox" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:6 +#: ../../content/applications/general/voip/onsip.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with `Axivox " +"`_. In that case, an :doc:`Asterisk server " +"` is not necessary as the infrastructure is hosted and managed by " +"Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:12 +msgid "" +"To use this service, `contact Axivox `_ to " +"open an account. Before doing so, verify that Axivox covers your area and " +"the areas you wish to call." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:18 +msgid "Go to :menuselection:`Apps` and install the **VoIP Module**." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "VoIP module installation on an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:24 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Integrations`, and " +"fill out the **Asterisk (VoIP)** field:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:27 +msgid "" +"**PBX Server IP**: set the domain created by Axivox for your account (e.g., " +"*yourcompany.axivox.com*)" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:29 +msgid "**WebSocket**: type in ``wss://pabx.axivox.com:3443``" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:30 +msgid "**VoIP Environment**: set as *Production*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox as VoIP provider in an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:37 +msgid "Configure the VOIP user in the Odoo's user" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:39 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, then open " +"the user's form you want to configure. Under the **Preferences** tab, fill " +"out the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:42 +msgid "**SIP Login / Browser's Extension**: the Axivox *username*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:43 +msgid "**SIP Password**: the Axivox *SIP Password*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox user in the Odoo user preference" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:50 +msgid "" +"You can find all this information by logging in at " +"https://manage.axivox.com/, selecting the user you want to configure, and " +"referring to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "SIP credentials in the Axivox manager" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:58 +msgid "Phone Calls" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:60 +msgid "" +"You can make phone calls by clicking on the phone icon in the navigation " +"bar." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:62 +msgid "" +"You can also receive phone calls. Odoo rings and displays a notification." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:65 +msgid "Your number is the one provided by Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Incoming VoIP call in Odoo" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:72 +msgid "" +"If you see a *Missing Parameter* message in the **Odoo softphone**, refresh " +"your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:80 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g., +16506913277 (where +1 is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:3 +msgid "Use VoIP services in Odoo with OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with OnSIP (www.onsip.com). In that" +" case, the installation and setup of an Asterisk server is not necessary as " +"the whole infrastructure is hosted and managed by OnSIP." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:12 +msgid "" +"You will need to open an account with OnSIP to use this service. Before " +"doing so, make sure that your area and the areas you wish to call are " +"covered by the service. After opening an OnSIP account, follow the " +"configuration procedure below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:19 +msgid "Go to Apps and install the module **VoIP OnSIP**." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:24 +msgid "" +"Go to Settings/General Settings. In the section Integrations/Asterisk " +"(VoIP), fill in the 3 fields:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:26 +msgid "" +"**OnSIP Domain** is the domain you chose when creating an account on " +"www.onsip.com. If you don't know it, log in to https://admin.onsip.com/ and " +"you will see it in the top right corner of the screen." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:29 +msgid "**WebSocket** should contain wss://edge.sip.onsip.com" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:30 +msgid "**Mode** should be Production" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:35 +msgid "" +"Go to **Settings/Users**. In the form view of each VoIP user, in the " +"Preferences tab, fill in the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:38 +msgid "**SIP Login / Browser's Extension**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:39 +msgid "**OnSIP authorization User**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:40 +msgid "**SIP Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:41 +msgid "**Handset Extension**: the OnSIP 'Extension'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:43 +msgid "" +"You can find all this information by logging in at " +"https://admin.onsip.com/users, then select the user you want to configure " +"and refer to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:49 +msgid "" +"You can now make phone calls by clicking the phone icon in the top right " +"corner of Odoo (make sure you are logged in as a user properly configured in" +" Odoo and in OnSIP)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:53 +msgid "" +"If you see a *Missing Parameters* message in the Odoo softphone, make sure " +"to refresh your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:60 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g.: `+16506913277` (where `+1` is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:67 +msgid "" +"You can now also receive phone calls. Your number is the one provided by " +"OnSIP. Odoo will ring and display a notification." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:74 +msgid "OnSIP on Your Cell Phone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:76 +msgid "" +"In order to make and receive phone calls when you are not in front of your " +"computer, you can use a softphone app on your cell phone in parallel of Odoo" +" VoIP. This is useful for on-the-go calls, but also to make sure to hear " +"incoming calls, or simply for convenience. Any SIP softphone will work." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:80 +msgid "" +"On Android and iOS, OnSIP has been successfully tested with `Grandstream " +"Wave `_. " +"When creating an account, select OnSIP in the list of carriers. You will " +"then have to configure it as follows:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:84 +msgid "**Account name**: OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:85 +msgid "**SIP Server**: the OnSIP 'Domain'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:86 +msgid "**SIP User ID**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:87 +msgid "**SIP Authentication ID**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:88 +msgid "**Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:90 +msgid "" +"Aside from initiating calls from Grandstream Wave on your phone, you can " +"also initiate calls by clicking phone numbers in your browser on your PC. " +"This will make Grandstream Wave ring and route the call via your phone to " +"the other party. This approach is useful to avoid wasting time dialing phone" +" numbers. In order to do so, you will need the Chrome extension `OnSIP Call " +"Assistant `_." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:97 +msgid "" +"The downside of using a softphone on your cell phone is that your calls will" +" not be logged in Odoo, as the softphone acts as an independent, separate " +"app." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/index.po b/locale/hi/LC_MESSAGES/index.po new file mode 100644 index 000000000..42c38362e --- /dev/null +++ b/locale/hi/LC_MESSAGES/index.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-11-08 08:46+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/index.rst:5 +msgid "Odoo Documentation" +msgstr "" diff --git a/locale/hi/LC_MESSAGES/inventory_and_mrp.po b/locale/hi/LC_MESSAGES/inventory_and_mrp.po new file mode 100644 index 000000000..3b27e8298 --- /dev/null +++ b/locale/hi/LC_MESSAGES/inventory_and_mrp.po @@ -0,0 +1,23598 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/inventory_and_mrp.rst:5 +msgid "Inventory & MRP" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:8 +msgid "Barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:10 +msgid "" +"**Odoo Barcode** allows users to assign barcodes to individual products and " +"product categories, and track inventory movements using those barcodes. By " +"connecting a barcode scanner, certain inventory processes can be triggered " +"by scanning barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:15 +msgid "" +"`Odoo Tutorials: Barcode Basics `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:5 +msgid "Daily operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:3 +msgid "Apply inventory adjustments with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:5 +msgid "" +"In a warehouse, the recorded inventory counts in the database might not " +"always match the actual, real inventory counts. In such cases, inventory " +"adjustments can be made to reconcile the differences, and ensure that the " +"recorded counts in the database match the actual counts in the warehouse. In" +" Odoo, the *Barcode* app can be used to make these adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:10 +msgid "" +"These adjustments can be done in real time using an Odoo-compatible barcode " +"scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:14 +msgid "" +"For a list of Odoo-compatible barcode mobile scanners, and other hardware " +"for the *Inventory* and *Barcode* apps, refer to the `Odoo Inventory • " +"Hardware page `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:19 +msgid "" +":doc:`../../inventory/warehouses_storage/inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:22 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:15 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:13 +msgid "Enable Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:24 +msgid "" +"To use the *Barcode* app to create and apply inventory adjustments, it " +"**must** be installed by enabling the feature from the settings of the " +"*Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:27 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click " +"the checkbox next to the :guilabel:`Barcode Scanner` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:31 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:24 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:22 +msgid "" +"Once the checkbox is ticked, click :guilabel:`Save` at the top of the page " +"to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:33 +msgid "" +"After saving, a new drop-down menu appears under the :guilabel:`Barcode " +"Scanner` option, labeled :guilabel:`Barcode Nomenclature`, where either " +":guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can" +" be selected. Each nomenclature option determines how scanners interpret " +"barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:38 +msgid "" +"There is also a :guilabel:`Configure Product Barcodes` internal link arrow, " +"along with a set of :guilabel:`Print` buttons for printing barcode commands " +"and a barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Enabled Barcode feature in Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:46 +msgid "" +"For more information on setting up and configuring the :guilabel:`Barcode` " +"app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and" +" :doc:`Activate the Barcodes in Odoo <../setup/software>` docs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:51 +msgid "Perform an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:53 +msgid "" +"Begin by navigating to the :menuselection:`Barcode app --> Barcode Scanning`" +" dashboard, where different options will be displayed, including " +":guilabel:`Operations`, :guilabel:`Inventory Adjustments`, and " +":guilabel:`Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:57 +msgid "" +"To create and apply inventory adjustments, click on the :guilabel:`Inventory" +" Adjustments` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:60 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:123 +msgid "" +"Doing so navigates to the *Barcode Inventory Client Action* page, labeled as" +" :guilabel:`Inventory Adjustment` in the top header section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Barcode app start screen with scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:67 +msgid "" +"To begin the adjustment, first scan the *source location*, which is the " +"current location in the warehouse of the product whose count should be " +"adjusted. Then, scan the product barcode(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:70 +msgid "" +"The barcode of a specific product can be scanned multiple times to increase " +"the quantity of that product in the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:74 +msgid "" +"If the warehouse *multi-location* feature is **not** enabled in the " +"database, a source location does not need to be scanned. Instead, simply " +"scan the product barcode to start the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:78 +msgid "" +"Alternatively, the quantity can be changed by clicking the :guilabel:`✏️ " +"(pencil)` icon on the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:81 +msgid "" +"Doing so opens a separate window with a keypad. Edit the number in the " +":guilabel:`Quantity` line to change the quantity. Additionally, the " +":guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract " +"quantity of the product, and the number keys can be used to add quantity, as" +" well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:86 +msgid "" +"In the below inventory adjustment, the source location `WH/Stock/Shelf/2` " +"was scanned, assigning the location. Then, the barcode for the product " +"`[FURN_7888] Desk Stand with Screen` was scanned 3 times, increasing the " +"units in the adjustment. Additional products can be added to this adjustment" +" by scanning the barcodes for those specific products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Barcode Inventory Client Action page with inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:95 +msgid "" +"To complete the inventory adjustment, click the green :guilabel:`✅ Apply` " +"button with the check mark at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:98 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:150 +msgid "" +"Once applied, Odoo navigates back to the :guilabel:`Barcode Scanning` " +"screen. A small green banner appears in the top right corner, confirming " +"validation of the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:180 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:103 +msgid "" +"Odoo's *Barcode* application provides demo data with barcodes to explore the" +" features of the app. These can be used for testing purposes, and can be " +"printed from the home screen of the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:106 +msgid "" +"To access this demo data, navigate to the :menuselection:`Barcode app` and " +"click :guilabel:`stock barcodes sheet` and :guilabel:`commands for " +"Inventory` (bolded and highlighted in blue) in the information pop-up window" +" above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Demo data prompt pop-up on Barcode app main screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:115 +msgid "Manually add products to inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:117 +msgid "" +"When the barcodes for the location or product are not available, Odoo " +"*Barcode* can still be used to perform inventory adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:120 +msgid "" +"To do this, navigate to the :menuselection:`Barcode app --> Barcode Scanning" +" --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:126 +msgid "" +"To manually add products to this adjustment, click the white :guilabel:`➕ " +"Add Product` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:129 +msgid "" +"This navigates to a new, blank page where the desired product, quantity, and" +" source location must be chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Keypad to add products on Barcode Inventory Client Action page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:136 +msgid "" +"First, click the :guilabel:`Product` line, and choose the product whose " +"stock count should be adjusted. Then, manually enter the quantity of that " +"product, either by changing the `1` in the :guilabel:`Quantity` line, or by " +"clicking the :guilabel:`+1` and :guilabel:`-1` buttons to add or subtract " +"quantity of the product. The number pad can be used to add quantity, as " +"well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:141 +msgid "" +"Below the number pad is the :guilabel:`location` line, which should read " +"`WH/Stock` by default. Click this line to reveal a drop-down menu of " +"locations to choose from, and choose the :guilabel:`source location` for " +"this inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:145 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:147 +msgid "" +"To apply the inventory adjustment, click the green :guilabel:`✅ Apply` " +"button with the check mark, at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:8 +msgid "Overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/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 sale which sells products in" +" bulk, in which 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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:13 +msgid "Create a Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:15 +msgid "" +"Odoo supports Barcode Nomenclatures, which determine the mapping and " +"interpretation of the encoded information. You can configure your barcode " +"nomenclature being in :ref:`developer mode `. To do so, go " +"to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:20 +msgid "" +"You can create a barcode nomenclature from there, and then add a line to " +"create your first rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:26 +msgid "" +"The first step is to specify the **rule name**, for example Weight Barcode " +"with 3 Decimals. You then have to specify the type for barcode nomenclature," +" in our case it will be Weighted Product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:33 +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" +" simply to identify the product in question. The “N” define a number and the" +" “D” define the decimals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:40 +msgid "" +"The encoding allows to specify the barcode encoding on which the rule should" +" be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:44 +msgid "" +"You can define different rules and order their priority thanks to the " +"sequence. The first rule which matches the scanned barcode will be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:49 +msgid "Configure your Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:51 +msgid "The barcode of the product should start by “21”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:52 +msgid "" +"The 5 “dots” are the other numbers of your product barcode, allowing to " +"identify the product;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:53 +msgid "" +"The barcode should contain 0’s where you did defined D’s or N’s. In our case" +" we need to set 5 zeros because we configured “21…..{NNDDD}”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:54 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:59 +msgid "" +"In case you weight 1,5 Kg of pasta, the balance will print you the following" +" barcode 2112345015002. If you scan this barcode in your POS or when " +"receiving products in your barcode application, Odoo will automatically " +"create a new line for the Pasta product for a quantity of 1.5 Kg. For the " +"point of sale, a price depending on the quantity will also be computed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:70 +msgid "Rule Types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:72 +msgid "" +"**Priced Product**: allows you to identify the product and specify its " +"price, used in POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:73 +msgid "" +"**Discounted Product**: allows you to create one barcode per applied " +"discount. You can then scan your product in the POS and then scan the " +"discount barcode, discount will be applied on the normal price of the " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:74 +msgid "" +"**Weighted Product**: allows you to identify the product and specify its " +"weight, used in both POS (in which the price is computed based on the " +"weight) and in inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:75 +msgid "" +"**Client**: allows you to identify the customer, for example used with " +"loyalty program." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:76 +msgid "**Cashier**: allows you to identify the cashier when entering the POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:77 +msgid "" +"**Location**: allows you to identify the location on a transfer when multi-" +"location is activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:78 +msgid "" +"**Package**: allows you to identify packages on a transfer when packages are" +" activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:79 +msgid "" +"**Credit Card**: doesn’t need manual modification, exists for data from the " +"Mercury module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:80 +msgid "" +"**Unit Product**: allows you to identify a product for both POS and " +"transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:83 +msgid "" +"When the barcode pattern contains .*, it means that it can contain any " +"number of characters, those characters being any number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:3 +msgid "GS1 barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:12 +msgid "" +"`GS1 nomenclature `_ consolidates various product " +"and supply chain data into a single barcode. Odoo takes in `unique Global " +"Trade Item Numbers `_ (GTIN), " +"purchased by businesses, to enable global shipping, sales, and eCommerce " +"product listing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:17 +msgid "" +"Configure GS1 nomenclature to scan barcodes of sealed boxes and identify " +"essential product information, such as |GTIN|, lot number, quantity " +"information, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:21 +msgid "" +"|GTINs| are unique product identification that **must** be `purchased from " +"GS1 `_ to use GS1 barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:25 +msgid "" +"`All GS1 barcodes `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:26 +msgid "" +":ref:`Odoo's default GS1 rules `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:27 +msgid "" +":ref:`Why's my barcode not working? `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:34 +msgid "" +"To use GS1 nomenclature, navigate to the :menuselection:`Inventory app --> " +"Configuration --> Settings`. Then under the :guilabel:`Barcode` section, " +"check the :guilabel:`Barcode Scanner` box. Next, select " +":menuselection:`Barcode Nomenclature --> Default GS1 Nomenclature` from the " +"default barcode nomenclature options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst-1 +msgid "" +"Choose GS1 from dropdown and click the external link to see the list of GS1 " +"rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:43 +msgid "" +"The list of GS1 *rules* and *barcode patterns* Odoo supports by default is " +"accessible by clicking the :guilabel:`➡️ (arrow)` icon to the right of the " +":guilabel:`Barcode Nomenclature` selection." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:46 +msgid "" +"In the :guilabel:`Open: Nomenclature` pop-up table, view and edit the GS1 " +":guilabel:`Rule Names` available in Odoo. The table contains all the " +"information that can be condensed with a GS1 barcode, along with the " +"corresponding :guilabel:`Barcode Pattern`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:51 +msgid "" +"After setting GS1 as the barcode nomenclature, the :menuselection:`Barcode " +"Nomenclatures` settings can also be accessed by a hidden menu that's " +"discoverable after enabling :ref:`developer mode `. Once " +"enabled, navigate to the :menuselection:`Inventory app --> Configuration -->" +" Barcode Nomenclatures` menu and finally, select :guilabel:`Default GS1 " +"Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:60 +msgid "Use GS1 barcodes in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:62 +msgid "" +"For product identification using GS1 barcodes in Odoo, businesses obtain a " +"`unique GTIN `_ as an " +"internationally distinct product identifier purchased from GS1. This |GTIN| " +"is combined with specific product details following GS1's designated " +"*barcode pattern*. The barcode pattern's arrangement of numbers and letters " +"must adhere to GS1 conventions for accurate interpretation by global systems" +" along the supply chain." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:68 +msgid "" +"Every barcode starts with a 2-4 digit `application identifier " +"`_ (A.I.). " +"This required prefix universally indicates what kind of information the " +"barcode contains. Odoo follows GS1 rules for identifying information, as " +"detailed in the :ref:`default GS1 rules list `. Including the relevant |AI| from the list enables " +"Odoo to correctly interpret GS1 barcodes. While most barcode patterns have a" +" fixed length requirement, certain ones, such as lots and serial numbers, " +"have flexible length." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:77 +msgid "" +"For flexible-length barcode patterns not placed at the end of the GS1 " +"barcode, use the FNC1 separator (`\\\\x1D`) to end the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:80 +msgid "" +"Example: The barcode pattern for lot numbers is 20 characters long. Instead " +"of creating a 20-character lot number barcode, like `LOT00000000000000001`, " +"use the FNC1 separator to make it shorter: `LOT001\\x1D`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:84 +msgid "" +"Refer to the :ref:`GS1 nomenclature list ` to see a comprehensive list of all barcode patterns " +"and rules to follow. Otherwise, refer to :ref:`this GS1 usage doc " +"` for specific examples of combining |GTIN| to" +" product information and configuring the workflow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:90 +msgid ":ref:`Lots workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:91 +msgid ":ref:`Non-unit quantities workflow `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:98 +msgid "" +"GS1 rules are a specific format of information contained in the barcode, " +"beginning with an |AI| and containing a defined length of characters. " +"Scanning GS1 barcodes from the :ref:`default GS1 list " +"` auto-fills corresponding" +" data in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:103 +msgid "" +"Adding GS1 barcode rules in Odoo ensures accurate interpretation of unique, " +"non-standard GS1 formats." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:106 +msgid "" +"To do so, begin by turning on :ref:`developer mode ` and " +"navigating to the :guilabel:`Barcode Nomenclatures` list in " +":menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. " +"Then, select the :guilabel:`Default GS1 Nomenclature` list item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:110 +msgid "" +"On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a " +"line` at the bottom of the table, which opens a window to create a new rule." +" The :guilabel:`Rule Name` field is used internally to identify what the " +"barcode represents. The barcode :guilabel:`Types` are different " +"classifications of information that can be understood by the system (e.g. " +"product, quantity, best before date, package, coupon). The " +":guilabel:`Sequence` represents the priority of the rule; this means the " +"smaller the value, the higher the rule appears on the table. Odoo follows " +"the sequential order of this table and will use the first rule it matches " +"based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence " +"of letters or numbers is recognized by the system to contain information " +"about the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:120 +msgid "" +"After filling in the information, click the :guilabel:`Save & New` button to" +" make another rule or click :guilabel:`Save & Close` to save and return to " +"the table of rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:126 +msgid "Barcode troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:128 +msgid "" +"Since GS1 barcodes are challenging to work with, here are some checks to try" +" when the barcodes are not working as expected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:131 +msgid "" +"Ensure that the :guilabel:`Barcode Nomenclature` setting is set as " +":menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature " +"setup section ` for more " +"details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:134 +msgid "" +"Ensure that the fields scanned in the barcode are enabled in Odoo. For " +"example, to scan a barcode containing lots and serial numbers, make sure the" +" :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's " +"settings ` and :ref:`on the product " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:138 +msgid "" +"Omit punctuation such as parentheses `()` or brackets `[]` between the " +":abbr:`A.I. (Application Identifier)` and the barcode sequence. These are " +"typically used in examples for ease of reading and should **not** be " +"included in the final barcode. For more details on building GS1 barcodes, go" +" to :ref:`this section `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:142 +msgid "" +"When a single barcode contains multiple encoded fields, Odoo requires all " +"rules to be listed in the barcode nomenclature for Odoo to read the barcode." +" :ref:`This section ` details how to " +"add new rules in the barcode nomenclature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:146 +msgid "" +"Test barcodes containing multiple encoded fields, piece by piece, to figure " +"out which field is causing the issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:150 +msgid "" +"When testing a barcode containing the |GTIN|, lot number, and quantity, " +"start by scanning the |GTIN| alone. Then, test the |GTIN| with the lot " +"number, and finally, try scanning the whole barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:154 +msgid "" +"After diagnosing the encoded field is unknown, :ref:`add new rules " +"` to Odoo's default list to recognize " +"GS1 barcodes with unique specifications." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:159 +msgid "" +"While the new field will be read, the information won't link to an existing " +"field in Odoo without developer customizations. However, adding new rules is" +" necessary to ensure the rest of the fields in the barcode are interpreted " +"correctly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:166 +msgid "GS1 nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:168 +msgid "" +"The table below contains Odoo's default list of GS1 rules. Barcode patterns " +"are written in regular expressions. Only the first three rules require a " +"`check digit `_ as the " +"final character." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Rule Name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Barcode Pattern" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "GS1 Content Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Odoo field" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Serial Shipping Container Code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "(00)(\\\\d{18})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "Numeric identifier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "Global Trade Item Number (GTIN)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Unit Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "(01)(\\\\d{14})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid ":guilabel:`Barcode` field on product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "GTIN of contained trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "(02)(\\\\d{14})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Packaging" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "Ship to / Deliver to global location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Destination location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "(410)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Ship / Deliver for forward" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "(413)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Source location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "I.D. of a physical location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "(414)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "Batch or lot number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Lot" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Alpha-numeric name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Serial number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "(13)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Pack date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "(15)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "(17)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiry date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "Variable count of items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "Quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "(30)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +msgid "UoM: Units" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Count of trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "(37)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Qty in units for containers (AI 02)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Net weight: kilograms (kg)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "(310[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Qty in kg" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Length in meters (m)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "(311[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Qty in m" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Net volume: liters (L)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "(315[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Qty in L" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Net volume: cubic meters (m\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "(316[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Qty in m\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Length in inches (in)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "(321[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Qty in inches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Net weight/volume: ounces (oz)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "(357[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Qty in oz" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Net volume: cubic feet (ft\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "(365[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Qty in ft\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Package type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:3 +msgid "GS1 barcode usage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:10 +msgid "" +"GS1 barcodes provide a standardized format that barcode scanners can " +"interpret. They encode information in a :ref:`specific structure recognized " +"globally `, allowing scanners to understand and " +"process supply chain data consistently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:14 +msgid "" +"Odoo *Barcode* interprets and prints GS1 barcodes, automating product " +"identification and tracking in warehouse operations such as receiving, " +"picking, and shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:17 +msgid "" +"The following sections contain examples of how Odoo uses GS1 barcodes " +"provided by the business to identify common warehouse items and automate " +"certain warehouse workflows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:21 +msgid "" +"Odoo **does not** create GS1 barcodes. Businesses must purchase a unique " +"Global Trade Item Number (GTIN) from GS1. Then, they can combine their " +"existing GS1 barcodes with product and supply chain information (also " +"provided by GS1) to create barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:26 +msgid "`Purchase GTINs `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:27 +msgid ":ref:`GS1 nomenclature `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:32 +msgid "Configure barcodes for product, quantity, and lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:34 +msgid "" +"To build a GS1 barcode that contains information about a product, its " +"quantities, and the lot number, the following barcode patterns and " +"Application Identifiers (A.I.) are used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "A.I." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Field in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:135 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:203 +msgid "01" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:139 +msgid "30" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid ":guilabel:`Units` field on transfer form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "Lot Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:41 +msgid "10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid ":guilabel:`Lot` on Detailed Operations pop-up" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:52 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:39 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:54 +msgid "" +"First, :ref:`enable product tracking using lots " +"` by navigating to " +":menuselection:`Inventory app --> Configuration --> Settings`, and checking " +"the box for :guilabel:`Lots & Serial Numbers` under the " +":guilabel:`Traceability` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:58 +msgid "" +"Then, set up the product barcode by navigating to the intended product form " +"in :menuselection:`Inventory app --> Products --> Products` and selecting " +"the product. On the product form, click :guilabel:`Edit`. Then, in the " +":guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field " +"with the unique 14-digit `Global Trade Item Number (GTIN) " +"`_, which is a universally " +"recognized identifying number that is provided by GS1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:66 +msgid "" +"On the product form, omit the |AI| `01` for |GTIN| product barcode pattern, " +"as it is only used to encode multiple barcodes into a single barcode that " +"contains detailed information about the package contents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:72 +msgid "" +"To record the GS1 barcode for the product, `Fuji Apple`, enter the 14-digit " +"|GTIN| `20611628936004` in the :guilabel:`Barcode` field on the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "Enter 14-digit GTIN into the Barcode field on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:80 +msgid "" +"To view a list of *all* products and their corresponding barcodes in the " +"Odoo database, navigate to :menuselection:`Inventory app --> Configuration " +"--> Settings`. Under the :guilabel:`Barcode` heading, click on the " +":guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode " +"Scanner` section. Enter the 14-digit |GTIN| into the :guilabel:`Barcode` " +"column, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "View the Product Barcodes page from inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:92 +msgid "" +"After activating tracking by lots and serial numbers from the settings page," +" specify that this feature is to be applied on each product by navigating to" +" the :guilabel:`Inventory` tab on the product form. Under " +":guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst-1 +msgid "" +"Enable product tracking by lots in the \"Inventory\" tab of the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:176 +msgid "Scan barcode on receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:103 +msgid "" +"To ensure accurate lot interpretation in Odoo on product barcodes scanned " +"during a receipt operation, navigate to the :menuselection:`Barcode` app to " +"manage the :ref:`receipt picking process `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:107 +msgid "" +"From the :guilabel:`Barcode Scanning` dashboard, click the " +":guilabel:`Operations` button, then the :guilabel:`Receipts` button to view " +"the list of vendor receipts to process. Receipts generated from :abbr:`POs " +"(Purchase Orders)` are listed, but new receipt operations can also be " +"created directly through the :menuselection:`Barcode` app using the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:112 +msgid "" +"On the list of receipts, click on the warehouse operation (`WH/IN`) and scan" +" product barcodes and lot numbers with a barcode scanner. The scanned " +"product then appears on the list. Use the :guilabel:`✏️ (pencil)` button to " +"open a window and manually enter quantities for specific lot numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:118 +msgid "" +"After placing a :abbr:`PO (Purchase Order)` for fifty apples, navigate to " +"the associated receipt in the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:121 +msgid "" +"Scan the barcode containing the |GTIN|, quantity, and lot number. For " +"testing with a barcode scanner, below is an example barcode for the fifty " +"Fuji apples in Lot 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:129 +msgid "50 Fuji apples in Lot0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:131 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:199 +msgid "2D Matrix" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "" +"2D matrix of GS1 barcode of 50 fuji apples with an assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:134 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:202 +msgid "|AI| (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:136 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:204 +msgid "GS1 Barcode (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:137 +msgid "20611628936004" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:138 +msgid "|AI| (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:140 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:208 +msgid "GS1 Barcode (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:141 +msgid "00000050" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:142 +msgid "|AI| (lot)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:144 +msgid "GS1 Barcode (lot #)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:145 +msgid "LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:146 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:210 +msgid "Full GS1 barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:147 +msgid "0120611628936004 3000000050 10LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:149 +msgid "" +":ref:`If the configuration is correct `," +" `50/50` :guilabel:`Units` processed will be displayed and the " +":guilabel:`Validate` button turns green. Click the :guilabel:`Validate` " +"button to complete the reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "" +"Scan the barcode for a product on the reception picking page in the " +"*Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:160 +msgid "Configure barcode for product and non-unit quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:162 +msgid "" +"To build a GS1 barcode that contains products measured in a non-unit " +"quantity, like kilograms, for example, the following barcode patterns are " +"used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "Quantity in kilograms" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "310[0-5]" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:178 +msgid "" +"To confirm that quantities are correctly interpreted in Odoo, place an order" +" in the *Purchase* app using the appropriate unit of measure " +"(:guilabel:`UoM`) for the quantity of products to be purchased." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:183 +msgid "" +":ref:`Simplify vendor unit conversions with UoMs `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:185 +msgid "" +"After the order is placed, navigate to the :menuselection:`Barcode` app to " +":ref:`receive the vendor shipment `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:189 +msgid "" +"On the receipt in the *Barcode* app, receive an order for `52.1 kg` of " +"peaches by scanning the barcode containing the |GTIN| and quantity of " +"peaches in kilograms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:197 +msgid "52.1 kg of Peaches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:205 +msgid "00614141000012" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:206 +msgid "|AI| (kg, 1 decimal point)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:207 +msgid "3101" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:209 +msgid "000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:211 +msgid "0100614141000012 3101000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:213 +msgid "" +":ref:`If the configuration is correct `," +" `52.1 / 52.1` :guilabel:`kg` will be displayed and the :guilabel:`Validate`" +" button turns green. Finally, press :guilabel:`Validate` to complete the " +"validation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "Scan barcode screen for a reception operation in the Barcode app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:222 +msgid "Verify product moves" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:224 +msgid "" +"For additional verification, the quantities of received products are also " +"recorded on the :guilabel:`Product Moves` report, accessible by navigating " +"to :menuselection:`Inventory app --> Reporting --> Product Moves`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:228 +msgid "" +"The items on the :guilabel:`Product Moves` report are grouped by product by " +"default. To confirm the received quantities, click on a product line to open" +" its collapsible drop-down menu, which displays a list of *stock move lines*" +" for the product. The latest stock move matches the warehouse reception " +"reference number (e.g. `WH/IN/00013`) and quantity processed in the barcode " +"scan, demonstrating that the records processed in the *Barcode* app were " +"properly stored in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst-1 +msgid "Reception stock move record for 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:3 +msgid "Process receipts and deliveries with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:7 +msgid "" +"The *Barcode* app can be used to process receipts, deliveries, and other " +"types of operations in real time using a barcode scanner or the Odoo mobile " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:10 +msgid "" +"This makes it possible to process operations on the warehouse floor when " +"they happen, instead of having to wait to validate transfers from a " +"computer. Processing operations this way can help to properly attribute " +"barcodes to the appropriate products, pickings, locations, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:17 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:15 +msgid "" +"To use the *Barcode* app to process transfers, it must be installed by " +"enabling the feature from the settings of the *Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:20 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:18 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click " +"the checkbox next to the :guilabel:`Barcode Scanner` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:26 +msgid "" +"Once the page has refreshed, new options will be displayed under the " +":guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with " +"a corresponding drop-down menu), where either :guilabel:`Default " +"Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:30 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:29 +msgid "" +"There is also a :guilabel:`Configure Product Barcodes` internal link arrow, " +"and a set of :guilabel:`Print` buttons for printing barcode commands and a " +"barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:37 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:36 +msgid "" +"For more on setting up and configuring the :guilabel:`Barcode` app, refer to" +" the :doc:`Set up your barcode scanner <../setup/hardware>` and " +":doc:`Activate the Barcodes in Odoo <../setup/software>` documentation " +"pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:44 +msgid "Scan barcodes for receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:46 +msgid "" +"To process warehouse receipts for incoming products, there first needs to be" +" a purchase order (PO) created, and a receipt operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:49 +msgid "" +"To create a :abbr:`PO (purchase order)`, navigate to the " +":menuselection:`Purchase app --> Create` to create a new request for " +"quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:52 +msgid "" +"From the blank :abbr:`RFQ (request for quotation)` form, click the drop-down" +" menu next to the :guilabel:`Vendor` field to add a vendor. Then, on the " +":guilabel:`Product` line under the :guilabel:`Products` tab, click " +":guilabel:`Add a product`, and select the desired product(s) to add to the " +"quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:57 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form, then click " +":guilabel:`Confirm Order` to confirm the :abbr:`RFQ (request for quotation)`" +" to a :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Completed purchase order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:64 +msgid "" +"To process and scan barcodes for warehouse receipts, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:66 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented. To process receipts, click" +" on the :guilabel:`Operations` button at the bottom of the screen. This " +"navigates to an :menuselection:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:74 +msgid "" +"From this page, locate the :guilabel:`Receipts` card, and click the " +":guilabel:`# To Process` button to view all outstanding receipts. Then, " +"select the desired receipt operation to process. This navigates to the " +"barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:79 +msgid "" +"If *only* using a barcode scanner or the Odoo mobile app, the barcodes for " +"each transfer of a corresponding operation type can be scanned to be " +"processed easily. Once scanned, the products that are part of an existing " +"transfer can be scanned, and new products can be added to the transfer, as " +"well. Once all products have been scanned, validate the transfer to proceed " +"with the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:85 +msgid "" +"From this screen, an overview of all receipts to process within that " +"transfer (**WH/IN/000XX**) is shown. At the bottom of the screen, there are " +"options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if " +"products need to be added to the operation, or if the whole operation should" +" be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Overview of receipts in transfer to scan." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:94 +msgid "" +"To process and scan each product individually, choose a specific product " +"line. The :guilabel:`+#` button (in this case, :guilabel:`+10`) can be " +"clicked to indicate receipt of that product, or the :guilabel:`pencil` icon " +"can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:98 +msgid "" +"From this screen, the product that's being received is listed. Under the " +"product name, the :guilabel:`Quantity` line can be edited. Either change the" +" `0` in the line to the desired quantity, or click the :guilabel:`/# Units` " +"button (in this case, :guilabel:`/10 Units`) to automatically fill the " +"quantity ordered from the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:104 +msgid "" +"In the reception operation `WH/IN/00019`, `10 Units` of the `Barcode " +"Product` is expected to be received. `[BARCODE_PROD]` is the " +":guilabel:`Internal Reference` set on the product form. Scan the barcode of " +"the `Barcode Product` to receive one unit. Afterwards, click the " +":guilabel:`pencil` icon to manually enter the received quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Product line editor for individual transfer in Barcode app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:113 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:179 +msgid "" +"Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked " +"to add or subtract quantity of the product, and the :guilabel:`number keys` " +"can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:116 +msgid "" +"Below the :guilabel:`number keys` is the :guilabel:`location` line, which " +"reads `WH/Stock` by default, unless another *location* is listed on the " +"product itself. Click this line to reveal a drop-down menu of additional " +"locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:120 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:158 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:211 +msgid "" +"Once ready, click :guilabel:`Confirm` to confirm the changes made to the " +"product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:122 +msgid "" +"Then, from the overview page with all receipts to process within that " +"transfer (**WH/IN/000XX**), click the :guilabel:`+#` button on the product " +"line for the products being received, and click :guilabel:`Validate`. The " +"receipt has now been processed, and the :guilabel:`Barcode app` can be " +"closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Overview of receipts in transfer to validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:132 +msgid "Scan barcodes for delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:134 +msgid "" +"To process warehouse deliveries for outgoing products, there first needs to " +"be a sales order (SO) created, and a delivery operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:137 +msgid "" +"To create a :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales " +"app --> Create` to create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:140 +msgid "" +"From the blank quotation form, click the drop-down menu next to the " +":guilabel:`Customer` field to add a customer. Then, on the " +":guilabel:`Product` line under the :guilabel:`Order Lines` tab, click " +":guilabel:`Add a product`, and select the desired product(s) to add to the " +"quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:144 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form, and click " +":guilabel:`Confirm Order` to confirm the quotation to a :abbr:`SO (sales " +"order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Completed sales order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:151 +msgid "" +"To process and scan barcodes for warehouse deliveries, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:153 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented. To process deliveries, " +"click on the :guilabel:`Operations` button at the bottom of the screen. This" +" navigates to an :guilabel:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:157 +msgid "" +"From this page, locate the :guilabel:`Delivery Orders` card, and click the " +":guilabel:`# To Process` button to view all outstanding deliveries. Then, " +"select the desired delivery order to process. This navigates to the barcode " +"transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Operations overview page in Barcode app dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:165 +msgid "" +"From this screen, an overview of all deliveries to process within that " +"transfer (**WH/OUT/000XX**) is shown. At the bottom of the screen, there are" +" options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if" +" products need to be added to the operation, or if the whole operation " +"should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:170 +msgid "" +"To process and scan each product individually, choose a specific product " +"line. The :guilabel:`+1` button can be clicked to indicate delivery of that " +"product, or the :guilabel:`pencil icon` can be clicked to open a new screen " +"to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:174 +msgid "" +"From this screen, the product that's being delivered is listed. Under the " +"product name, the :guilabel:`Quantity` line can be edited. Either change the" +" `0` in the line to the desired quantity, or click the :guilabel:`/# Units` " +"button (in this case, :guilabel:`/10 Units`) to automatically fill the " +"quantity ordered from the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:182 +msgid "" +"Below the :guilabel:`number keys` is the :guilabel:`location` line, which " +"reads `WH/Stock` by default, unless another location is listed on the " +"product itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:185 +msgid "" +"This is the location that the product is being pulled from for delivery. " +"Click this line to reveal a drop-down menu of additional locations to choose" +" from (if this product is stored in multiple locations in the warehouse)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:190 +msgid "" +"For warehouses that have multiple different storage locations, putaway " +"rules, and removal strategies, additional steps can be added for various " +"operation types, while using the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:196 +msgid "" +"Then, from the overview page with all receipts to process within that " +"transfer (**WH/OUT/000XX**), click the :guilabel:`+#` button on the product " +"line for the products being received, and click :guilabel:`Validate`. The " +"delivery has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Overview of deliveries in transfer to validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:3 +msgid "Create and process transfers with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:5 +msgid "" +"The *Barcode* app can be used to process internal transfers for all types of" +" products, including transfers for products tracked using lots or serial " +"numbers. Transfers can be created from scratch in real time using an Odoo-" +"compatible barcode scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:9 +msgid "" +"For a list of Odoo-compatible barcode mobile scanners, and other hardware " +"for the *Inventory* app, refer to the `Odoo Inventory • Hardware page " +"`_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:24 +msgid "" +"When the page has refreshed, new options are displayed under the " +":guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with " +"a corresponding drop-down menu), where either :guilabel:`Default " +"Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. The " +"nomenclature selected changes how scanners interpret barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:41 +msgid "Scan barcodes for internal transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:43 +msgid "" +"To create and process internal transfers for products in a warehouse, the " +":guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features " +"**must** be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:46 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Warehouse` section, and click" +" the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-" +"Step Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:50 +msgid "Then, click :guilabel:`Save` at the top of the page to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:53 +msgid "Create an internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:55 +msgid "" +"To process existing internal transfers, there first needs to be an internal " +"transfer created, and an operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:58 +msgid "" +"To create an internal transfer, navigate to the :menuselection:`Inventory " +"app`. From the :guilabel:`Inventory Overview` dashboard, locate the " +":guilabel:`Internal Transfers` card, and click on the :guilabel:`0 To " +"Process` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:62 +msgid "" +"Then, click :guilabel:`Create` in the top left of the resulting page. This " +"navigates to a new :guilabel:`Internal Transfer` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:65 +msgid "" +"On this blank form, the :guilabel:`Operation Type` is automatically listed " +"as :guilabel:`Internal Transfers`. Under that field, the :guilabel:`Source " +"Location` and :guilabel:`Destination Location` are set as " +":guilabel:`WH/Stock` by default, but can be changed to whichever locations " +"the products are being moved from, and moved to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "" +"Blank internal transfer form with source location and destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:74 +msgid "" +"Once the desired locations have been selected, products can be added to the " +"transfer. On the :guilabel:`Product` line under the :guilabel:`Products` " +"tab, click :guilabel:`Add a product`, and select the desired product(s) to " +"add to the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:78 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form to save the new " +"internal transfer. Once saved, click the :guilabel:`Detailed Operations` " +"icon (four lines, at the far right of the :guilabel:`Product` line) to open " +"the :guilabel:`Detailed Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Internal transfer detailed operations pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:86 +msgid "From the pop-up, click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:88 +msgid "" +"Then, in the :guilabel:`To` column, change the location from " +":guilabel:`WH/Stock` to a different location, where the products should be " +"moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:91 +msgid "" +"Next, in the :guilabel:`Done` column, change the quantity to the desired " +"quantity to transfer. Once ready, click :guilabel:`Confirm` to close out the" +" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:95 +msgid "Scan barcodes for internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:97 +msgid "" +"To process and scan barcodes for internal transfers, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:99 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:102 +msgid "" +"To process internal transfers, click on the :guilabel:`Operations` button at" +" the bottom of the screen. This navigates to an :menuselection:`Operations` " +"overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:109 +msgid "" +"From this page, locate the :guilabel:`Internal Transfers` card, and click " +"the :guilabel:`# To Process` button to view all outstanding internal " +"transfers. Then, select the desired operation to process. This navigates to " +"the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:114 +msgid "" +"When using the *Barcode* app without the *Inventory* app (**only** if using " +"a barcode scanner or the Odoo mobile app), the barcodes for each transfer of" +" a corresponding operation type can be scanned to be processed easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:118 +msgid "" +"Once scanned, the products that are part of an existing transfer can be " +"scanned, and new products can be added to the transfer, as well. Once all " +"products have been scanned, validate the transfer to proceed with the stock " +"moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:122 +msgid "" +"From this screen, an overview of all products to process within that " +"specific internal transfer (**WH/INT/000XX**) is shown. At the bottom of the" +" screen, there are options to :guilabel:`Add Product` or " +":guilabel:`Validate`, depending on if products need to be added to the " +"operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:131 +msgid "" +"Then, scan the barcode of the product to process the internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:133 +msgid "" +"Or, to process and scan each product individually, choose a specific product" +" line. The :guilabel:`+ 1` button can be clicked to add additional quantity " +"of that product to the transfer, or the :guilabel:`pencil icon` can be " +"clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:137 +msgid "" +"In the product's pop-up window, the product and the units to process is " +"displayed with a number pad. Under the product name, the " +":guilabel:`Quantity` line can be edited. Change the number in the line to " +"the quantity listed to be transferred on the internal transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:142 +msgid "" +"In the internal transfer operation `WH/INT/000XX`, `50 Units` of the " +"`Transfer Product` is moved from `WH/Stock` to `WH/Stock/Shelf 1`. " +"`[TRANSFER_PROD]` is the :guilabel:`Internal Reference` set on the product " +"form. Scan the barcode of the `Transfer Product` to receive one unit. " +"Afterwards, click the :guilabel:`pencil icon` to manually enter the " +"transferred quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:151 +msgid "" +"Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked " +"to add or subtract quantity of the product, and the number keys can be used " +"to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:154 +msgid "" +"Below the number keys are the two :guilabel:`location` lines, which read " +"whichever locations were previously specified on the internal transfer form," +" in this case `WH/Stock` and `WH/Stock/Shelf 1`. Click these lines to reveal" +" a drop-down menu of additional locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:160 +msgid "" +"Then, from the overview page with all products to process within that " +"transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The receipt has now" +" been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:165 +msgid "" +"The *Barcode* app can also be used to scan products in internal transfers " +"containing unique lot numbers and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:168 +msgid "" +"From the barcode transfer screen, scan the barcode of a lot or serial " +"number, and Odoo automatically increases the quantity of the product to the " +"quantity recorded in the database. If the same lot or serial number is " +"shared between different products, scan the product barcode first, then the " +"barcode of the lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:174 +msgid "Create a transfer from scratch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:176 +msgid "" +"In addition to processing and scanning barcodes for existing, previously-" +"created internal transfers, the *Barcode* app can also be used to create " +"transfers from scratch, simply by scanning a printed operation type barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:182 +msgid "" +"Odoo's *Barcode* application provides demo data with barcodes to explore the" +" features of the app. These can be used for testing purposes, and can be " +"printed from the home screen of the app. To access this demo data, navigate " +"to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes " +"sheet` (bolded and highlighted in blue) in the information pop-up above the " +"scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:191 +msgid "" +"To do this, first navigate to the :menuselection:`Barcode app`. Once inside " +"the *Barcode* app, a :guilabel:`Barcode Scanning` screen displaying " +"different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:194 +msgid "" +"From this screen, when using a USB or bluetooth barcode scanner, directly " +"scan the product barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:196 +msgid "" +"When using a smartphone as the barcode scanner, click the :guilabel:`Tap to " +"Scan` button (next to the camera icon, at the center of the screen). This " +"opens a :guilabel:`Barcode Scanner` pop-up screen that enables the camera of" +" the device being used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:200 +msgid "" +"Face the camera toward the printed operation type barcode to scan it. Doing " +"so processes the barcode, and navigates to a barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:203 +msgid "" +"From this screen, an overview of all products to process within that " +"specific internal transfer (**WH/INT/000XX**) is shown. Since this is a new " +"transfer created from scratch, however, there should not be any products " +"listed on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:207 +msgid "" +"To add products, scan the product barcode. If the barcode is not available, " +"manually enter the product into the system by clicking the :guilabel:`Add " +"Product` button at the bottom of the screen, and add the products and " +"product quantities that should be transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Blank product editor in scratch internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:217 +msgid "" +"Then, from the overview page with all products to process within that " +"transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The internal " +"transfer has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup.rst:5 +msgid "Setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:3 +msgid "Set up your barcode scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:7 +msgid "" +"Follow this guide to choose and set up a barcode scanner compatible with " +"Odoo's *Inventory* and *Barcode* apps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:14 +msgid "An image of an example barcode scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:17 +msgid "Scanner types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:19 +msgid "" +"Before setting up a barcode scanner, it is important to determine which " +"scanner type best meets the needs of the business. There are three main " +"types, each with their own benefits and use cases:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:22 +msgid "" +"**USB scanners** are connected to a computer, and are suitable for " +"businesses that scan products at a fixed location, like at the checkout in a" +" grocery store. Ensure the chosen USB scanner is compatible with the " +"keyboard layout of the computer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:26 +msgid "" +"**Bluetooth scanners** pair with a smartphone or tablet, making them an " +"ideal cost-effective and portable barcode scanner option. In this scenario, " +"Odoo is installed on the smartphone, allowing warehouse operators to handle " +"operations, and check stock directly through their mobile devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:30 +msgid "" +"**Mobile computer scanners** are mobile devices with a built-in barcode " +"scanner. First, ensure the device can run the Odoo mobile app properly. " +"Recent models that use Android OS with the Google Chrome browser, or Windows" +" OS with Microsoft Edge, should work. However, testing is crucial due to the" +" variety of available models and configurations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:36 +msgid "" +"`Compatible hardware with Odoo Inventory " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:41 +msgid "" +"When setting up the barcode scanner, make sure the following configurations " +"are correct so the scanner can properly interpret barcodes with Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:45 +msgid "Keyboard layout" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:47 +msgid "" +"When using a USB barcode scanner, match its keyboard layout with the " +"operating system's layout for proper interpretation of characters. " +"Generally, the scanning mode should be set to accept a USB keyboard (HID), " +"with the language set based on the keyboard that is in use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:51 +msgid "" +"To configure the keyboard layout for a **Zebra** scanner, scan the keyboard " +"wedge barcode for the desired language in the scanner's user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "Example of a user manual for keyboard layout." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "" +"Examples of keyboard language settings in the Zebra scanner user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:60 +msgid "Automatic carriage return" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:62 +msgid "" +"Odoo has a default 100-millisecond delay between scans to prevent accidental" +" double scanning. To synchronize with the barcode scanner, set it to include" +" a *carriage return* (:dfn:`character like the \"Enter\" key on a keyboard`)" +" after each scan. Odoo interprets the carriage return as the end of the " +"barcode input; so Odoo accepts the scan, and waits for the next one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:67 +msgid "" +"Typically, on the scanner, a carriage return is included by default. Ensure " +"it is set by scanning a specific barcode in the user manual, like `CR suffix" +" ON` or `Apply Enter for suffix`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:71 +msgid "Zebra scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:73 +msgid "" +"When using Zebra scanners, ensure the following keystroke configurations are" +" set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:75 +msgid "" +"Begin on the Zebra scanner's home screen, and select the " +":guilabel:`DataWedge` app (the icon for the app is a light blue barcode). On" +" the :guilabel:`DataWedge Profiles` page, select the profile option to " +"access the Zebra scanner's settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:79 +msgid "" +"Scroll down to the :guilabel:`Keyboard Output` option, and ensure the " +":guilabel:`Enable/disable keystroke output` option is :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst-1 +msgid "Show keystroke option in the Zebra scanner's DataWedge app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:86 +msgid "" +"Now, go back to the :guilabel:`Profile` options page, and select " +":guilabel:`Key event options`. Here, ensure the :guilabel:`Send Characters " +"as Events` option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:3 +msgid "Activate the Barcodes in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:7 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:16 +msgid "" +"To use this feature, you first need to activate the *Barcode* functionality " +"via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you " +"have ticked the feature, you can hit save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:24 +msgid "Set Product Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:26 +msgid "" +"You can easily assign barcodes to your different products via the " +"*Inventory* app. To do so, go to :menuselection:`Settings --> Configure " +"Products Barcodes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:32 +msgid "" +"Then, you have the possibility to assign barcodes to your products directly " +"at creation on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:42 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:49 +msgid "Set Locations Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:51 +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 --> " +"Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:62 +msgid "" +"You can easily print the barcode you allocate to the locations via the " +"*Print* menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:66 +msgid "Barcode Formats" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:68 +msgid "" +"Most retail products use EAN-13 barcodes, also known as GTIN (Global Trade " +"Identification Numbers). GTIN are used by companies to uniquely identify " +"their products and services. While GTIN and UPC are often used synonymously," +" GTIN refers to the number a barcode represents, while UPC refers to the " +"barcode itself. More information about GTIN can be found on the GS1 website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:73 +msgid "" +"In order to create GTIN for items, a company must have a GS1 Company Prefix." +" This prefix is the number that will appear at the beginning of each GTIN, " +"and will identify the company as the owner of the barcode any the products " +"it appears on. To learn more about GS1 Company Prefixes, or purchase a " +"license for a prefix, visit the GS1 Company Prefix page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:78 +msgid "" +"Odoo users are able to use GTIN barcodes to identify their products. " +"However, since Odoo supports any numeric string as a barcode, it is also " +"possible to define a custom barcode for internal use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:8 +msgid "Inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:10 +msgid "" +"Odoo *Inventory* is both an inventory application and a warehouse management" +" system. The app allows users to easily manage lead times, automate " +"replenishment, configure advanced routes, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:14 +msgid "" +"`Odoo Tutorials: Inventory `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management.rst:5 +msgid "Product management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment.rst:5 +msgid "Product replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:3 +msgid "Replenish on order (MTO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:9 +msgid "" +"*Replenish on order*, also known as *MTO* (make to order), is a " +"replenishment strategy that creates a draft order for a product every time a" +" sales order is created for it. For products that are purchased from a " +"vendor, a request for quotation (RFQ) is created, while a sales order for a " +"product manufactured in-house triggers the creation of a manufacturing " +"order. The creation of a |RFQ| or manufacturing order occurs every time a " +"sales order is created, regardless of the current stock level of the product" +" being ordered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:19 +msgid "" +"By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| " +"is a somewhat niche workflow that is only used by certain companies. " +"However, it is easy to unarchive the route in just a few simple steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:23 +msgid "" +"To do so, begin by navigating to :menuselection:`Inventory --> Configuration" +" --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` " +"button and select the :guilabel:`Archived` option. This shows all routes " +"that are currently archived." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The archived filter on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:31 +msgid "" +"Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click" +" the :guilabel:`Action` button to reveal a drop-down menu. From the drop-" +"down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The unarchive action on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:38 +msgid "" +"Finally, remove the :guilabel:`Archived` filter from the " +":guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all " +"available routes, including :guilabel:`Replenish on Order (MTO)`, which is " +"now selectable on the inventory tab of each product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The MTO route appears on the Routes page after unarchiving it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:47 +msgid "Configure a product to use the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:49 +msgid "" +"With the |MTO| route unarchived, products can now be properly configured to " +"use replenish on order. To do so, begin by going to " +":menuselection:`Inventory --> Products --> Products`, then select an " +"existing product, or click :guilabel:`Create` to configure a new one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:53 +msgid "" +"On the product page, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` " +"section, along with one other route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:57 +msgid "" +"The :guilabel:`Replenish on Order (MTO)` route **does not** work unless " +"another route is selected as well. This is because Odoo needs to know how to" +" replenish the product when an order is placed for it (buy it, manufacture " +"it, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "Select the MTO route and a second route on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:65 +msgid "" +"If the product is purchased from a vendor to fulfill sales orders, enable " +"the :guilabel:`Can be Purchased` checkbox under the product name. Doing so " +"makes the :guilabel:`Purchase` tab appear alongside the other settings tabs " +"below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:69 +msgid "" +"Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the" +" :guilabel:`Price` they sell the product for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:76 +msgid "" +"If the product is manufactured, make sure that it has a bill of materials " +"(BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` " +"smart button at the top of the screen, then click :guilabel:`Create` on the " +":guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:81 +msgid "" +"On the blank |BOM| form, add the components used to manufacture the product " +"on the :guilabel:`Components` tab, along with the operations required for " +"the manufacturing workflow on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:85 +msgid "Finally, click :guilabel:`Save` to save the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:88 +msgid "Fulfill a sales order using the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:90 +msgid "" +"After configuring a product to use the |MTO| route, a replenishment order is" +" created for it every time a sales order including the product is confirmed." +" The type of order created depends on the second route selected in addition " +"to |MTO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:94 +msgid "" +"For example, if *Buy* was the second route selected, then a purchase order " +"is created upon confirmation of a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:98 +msgid "" +"When the |MTO| route is enabled for a product, a replenishment order is " +"always created upon confirmation of a sales order. This is the case even if " +"there is enough stock of the product on-hand to fulfill the sales order, " +"without buying or manufacturing additional units of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:102 +msgid "" +"While the |MTO| route can be used in unison with a variety of other routes, " +"the *Buy* route is used as the example for this workflow. Begin by " +"navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`," +" which opens a blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:106 +msgid "" +"On the blank quotation form, add a :guilabel:`Customer`, then click " +":guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a" +" product that has been configured to use the *MTO* and *Buy* routes. Click " +":guilabel:`Confirm` and the quotation is turned into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:110 +msgid "" +"A :guilabel:`Purchase` smart button now appears in the top-right corner of " +"the sales order. Clicking it opens the |RFQ| associated with the sales " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:113 +msgid "" +"Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a " +"purchase order. A green :guilabel:`Receive Products` button now appears at " +"the top of the purchase order. Once the products are received, click " +":guilabel:`Receive Products` to register them into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:117 +msgid "" +"Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by " +"navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting " +"the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:120 +msgid "" +"Finally, click the :guilabel:`Delivery` smart button in the top-right of the" +" order to be taken to the delivery order. Once the products have been " +"shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:3 +msgid "Reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:7 +msgid "" +"Reordering rules are used to keep forecasted stock levels above a certain " +"threshold without exceeding a specified upper limit. This is accomplished by" +" specifying a minimum quantity that stock should not fall below and a " +"maximum quantity that stock should not exceed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:11 +msgid "" +"Reordering rules can be configured for each product based on the route used " +"to replenish it. If a product uses the *Buy* route, then a Request for " +"Quotation (RFQ) is created when the reordering rule is triggered. If a " +"product uses the *Manufacture* route, then a Manufacturing Order (MO) is " +"created instead. This is the case regardless of the selected replenishment " +"route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:17 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:19 +msgid "" +"In order to use reordering rules for a product, it must first be correctly " +"configured. Begin by navigating to :guilabel:`Inventory --> Products --> " +"Products`, then select an existing product, or create a new one by clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 +msgid "" +"First, on the :guilabel:`General Information` tab, make sure that the " +":guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is " +"necessary because Odoo only tracks stock quantities for storable products, " +"and this number is used to trigger reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Set the Product Type as Storable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:31 +msgid "" +"Next, click on the :guilabel:`Inventory` tab and select one or more routes " +"from the :guilabel:`Routes` section. Doing so tells Odoo which route to use " +"to replenish the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Select one or more routes on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:38 +msgid "" +"If the product is reordered using the :guilabel:`Buy` route, confirm that " +"the :guilabel:`Can be Purchased` checkbox is enabled under the product name." +" This makes the :guilabel:`Purchase` tab appear. Click on the " +":guilabel:`Purchase` tab, and specify at least one vendor, and the price " +"that they sell the product for, so that Odoo knows which company the product" +" should be purchased from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Specify a vendor and price on the Purchase tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:47 +msgid "" +"If the product is replenished using the :guilabel:`Manufacture` route, it " +"needs to have at least one Bill of Materials (BoM) associated with it. This " +"is necessary because Odoo only creates manufacturing orders for products " +"with a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:51 +msgid "" +"If a :abbr:`BoM (Bill of Materials)` does not already exist for the product," +" select the :guilabel:`Bill of Materials` smart button at the top of the " +"product form, then click :guilabel:`Create` to configure a new :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "The Bill of Materials smart button on a product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:60 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:62 +msgid "" +"To create a new reordering rule, navigate to :menuselection:`Inventory --> " +"Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill" +" out the new line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:65 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:67 +msgid "" +":guilabel:`Min Quantity`: The minimum quantity that can be forecasted " +"without the rule being triggered. When forecasted stock falls below this " +"number, a replenishment order for the product is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:70 +msgid "" +":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up " +"to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 +msgid "" +":guilabel:`Multiple Quantity`: Specify if the product should be replenished " +"in batches of a certain quantity (e.g., a product could be replenished in " +"batches of 20)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:73 +msgid "" +":guilabel:`UoM`: The unit of measure used for reordering the product. This " +"value can simply be `Units` or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "The form for creating a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:81 +msgid "" +"Reordering rules can also be created from each product form. To do so, " +"navigate to :menuselection:`Inventory --> Products --> Products`, then " +"select a product. Click on :menuselection:`Reordering Rules --> Create`, " +"then fill out the new line as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:85 +msgid "" +"Once a reordering rule has been created for a product, if its forecasted " +"quantity is below the rule's minimum quantity when the scheduler runs, a " +"replenishment order for the product is automatically generated. By default, " +"the scheduler runs once each day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:90 +msgid "" +"To manually trigger a reordering rule before the scheduler runs, select " +":menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select " +"the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be " +"aware that this also triggers any other scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 +msgid "" +"If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for " +"Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for " +"Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests " +"for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:98 +msgid "" +"If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO " +"(Manufacturing Order)` is generated. To view and manage :abbr:`MOs " +"(Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> " +"Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:103 +msgid "Set a preferred route for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:105 +msgid "" +"Odoo allows for multiple routes to be selected under the " +":guilabel:`Inventory` tab on each product form. For instance, it is possible" +" to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling " +"the functionality of both routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:109 +msgid "" +"Odoo also enables users to set a preferred route for a product's reordering " +"rule. This is the route that the rule defaults to if multiple are selected. " +"To select a preferred route, begin by navigating to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:113 +msgid "" +"By default, the :guilabel:`Preferred Route` column is hidden on the " +":guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ " +"(three-dot)` option button on the right side of the page and checking the " +":guilabel:`Preferred Route` checkbox. Doing so reveals the " +":guilabel:`Preferred Route` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:118 +msgid "" +"Click inside of the column on the row of a reordering rule and a drop-down " +"menu shows all available routes for that rule. Select one to set it as the " +"preferred route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Select a preferred route from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:126 +msgid "" +"If multiple routes are enabled for a product but no preferred route is set " +"for its reordering rule, the product is reordered using the selected route " +"that is listed first on the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:3 +msgid "Scrap inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:5 +msgid "" +"In some cases, a product in inventory may be damaged or found to be " +"defective. If it is not possible to repair or return the product, Odoo " +"*Inventory* allows users to scrap it, ensuring that usable inventory counts " +"remain accurate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 +msgid "" +"Scrap orders can be viewed by navigating to :menuselection:`Inventory --> " +"Operations --> Scrap`. Each scrap order shows the date and time the order " +"was created, along with the product and quantity that was scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:14 +msgid "" +"To view the total quantity of each item scrapped, navigate to " +":menuselection:`Inventory --> Configuration --> Locations`. Remove the " +":guilabel:`Internal` filter from the :guilabel:`Search...` bar to display " +"virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:19 +msgid "" +"By default, scrapping a product removes it from physical inventory, and " +"places it in a virtual location titled *Virtual Locations/Scrap*. A virtual " +"location is **not** a physical space, but rather a designation in Odoo that " +"is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:30 +msgid "Learn more" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:25 +msgid "" +"For more information about virtual locations, see the documentation about " +"the different types of :ref:`locations `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:29 +msgid "Scrap from stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:31 +msgid "" +"To scrap a product located in inventory, begin by navigating to " +":menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap" +" Orders` page, click :guilabel:`Create` to configure a new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:35 +msgid "" +"On the scrap order, select the product being scrapped from the " +":guilabel:`Product` drop-down menu, then enter the quantity in the " +":guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the " +"location where the product is stored, and the :guilabel:`Scrap Location` " +"defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be " +"changed by selecting a different location from their respective drop-down " +"menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "A new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:45 +msgid "" +"Finally, click :guilabel:`Validate` to scrap the product. The on-hand " +"inventory count for the scrapped product updates to subtract the scrapped " +"quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:49 +msgid "Scrap from a receipt, transfer, or delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:51 +msgid "" +"It is also possible to scrap products during the receipt, transfer, and " +"delivery operations. This can be necessary if any products are found to be " +"defective when receiving them into inventory, transferring them from one " +"location to another, or preparing them for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:55 +msgid "" +"To scrap a product during the receipt, transfer, or delivery operations, " +"begin by navigating to the :menuselection:`Inventory` app. On the " +":guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the" +" :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or " +":guilabel:`Delivery Orders` card, depending on the type of operation the " +"product is being scrapped from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:61 +msgid "" +"For the :guilabel:`Internal Transfers` card to appear on the " +":menuselection:`Overview` page of the :menuselection:`Inventory` app, the " +":guilabel:`Storage Locations` setting must be enabled. To do so, navigate to" +" :menuselection:`Configuration --> Settings`, then enable the checkbox next " +"to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:66 +msgid "" +"Alternatively, a list of all delivery orders, receipts, and transfers can be" +" viewed by navigating to :menuselection:`Inventory --> Operations --> " +"Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:69 +msgid "" +"Next, open a delivery order, receipt, or transfer from the corresponding " +"page by clicking on it. A :guilabel:`Scrap` button appears at the top of the" +" page. Click it to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "The scrap pop-up in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:78 +msgid "" +"The :guilabel:`Scrap` button will only appear on a receipt that has been " +"validated. This is because Odoo only allows products to be scrapped once " +"they have been entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:81 +msgid "" +"On the :guilabel:`Scrap` pop-up window, select the product being scrapped " +"from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the" +" :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:84 +msgid "" +"The :guilabel:`Source Location` defaults to the location where the product " +"is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual" +" Locations/Scrap`, but either of these can be changed by selecting a " +"different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:88 +msgid "" +"Finally, click :guilabel:`Done` to scrap the product. After doing so, the " +":guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart " +"button appears in the top right of the page. Click it to view all of the " +"scrap orders created from that operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "The Scraps smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:3 +msgid "Selecting a replenishment strategy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:10 +msgid "" +"In Odoo, there are two strategies for automatically replenishing inventory: " +"*reordering rules* and the *make to order (MTO)* route. Although these " +"strategies differ slightly, they both have similar consequences: triggering " +"the automatic creation of a |PO| or |MO|. The choice of which strategy to " +"use depends on the business's manufacturing and delivery processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:6 +msgid "Terminology" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:56 +msgid "Replenishment report and reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:21 +msgid "" +"The replenishment report is a list of all products that have a negative " +"forecast quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:23 +msgid "" +"*Reordering rules* are used to ensure there's always a minimum amount of a " +"product in-stock, in order to manufacture products and/or fulfill sales " +"orders. When the stock level of a product reaches its minimum, Odoo " +"automatically generates a purchase order with the quantity needed to reach " +"the maximum stock level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:28 +msgid "" +"Reordering rules can be created and managed in the replenishment report, or " +"from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:33 +msgid "Make to order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:35 +msgid "" +"*Make to order (MTO)* is a procurement route that creates a draft purchase " +"order (or manufacturing order) each time a sales order is confirmed, " +"**regardless of the current stock level**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:38 +msgid "" +"Unlike products replenished using reordering rules, Odoo automatically links" +" the sales order to the |PO| or |MO| generated by the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:41 +msgid "" +"Another difference between reordering rules and |MTO| is, with |MTO|, Odoo " +"generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With" +" reordering rules, Odoo generates a draft |PO| or |MO| when the product's " +"forecasted stock falls below the set minimum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:45 +msgid "" +"In addition, Odoo automatically adds quantities to the |PO| or |MO| as the " +"forecast changes, so long as the |PO| or |MO| is not confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:48 +msgid "" +"The |MTO| route is the best replenishment strategy for products that are " +"customized, and/or for products that have no stock kept on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:58 +msgid "" +"To access the replenishment report, go to :menuselection:`Inventory app --> " +"Operations --> Replenishment.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:61 +msgid "" +"By default, the replenishment report dashboard shows every product that " +"needs to be manually reordered. If there is no specific rule for a product, " +"Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock" +" are both `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:66 +msgid "" +"For products that don't have a set reordering rule, Odoo calculates the " +"forecast based on confirmed sales orders, deliveries, and receipts. For " +"products that have a set reordering rule, Odoo calculates the forecast " +"normally, but also takes into account the purchase/manufacturing lead time " +"and security lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:72 +msgid "" +"Before creating a new reordering rule, make sure the product has a *vendor* " +"or a *bill of materials* configured on the product form. To check this, go " +"to :menuselection:`Inventory app --> Products --> Products`, and select the " +"product to open its product form. The vendor, if configured, is listed in " +"the :guilabel:`Purchase` tab, and the bill on materials, if configured, is " +"found in the :guilabel:`Bill of Materials` smart button at the top of the " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:78 +msgid "" +"The :guilabel:`Product Type`, located in the :guilabel:`General Information`" +" tab on the product form, **must** be set to :guilabel:`Storable Product`. " +"By definition, a consumable product does not have its inventory levels " +"tracked, so Odoo cannot account for a consumable product in the " +"replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Replenishment report listing all items needing to be purchased to meet " +"current needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:87 +msgid "" +"To create a new reordering rule from the replenishment report, go to " +":menuselection:`Inventory app --> Operations --> Replenishment`, click " +":guilabel:`Create`, and select the desired product from the drop-down menu " +"in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` " +"and a :guilabel:`Max Quantity` can be configured in the corresponding " +"columns on the :guilabel:`Replenishment` report page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:93 +msgid "" +"To create a new reordering rule from the product form, go to " +":menuselection:`Inventory app --> Products --> Products`, and select a " +"product to open its product form. Click the :guilabel:`Reordering Rules` " +"smart button, click :guilabel:`Create`, and fill out the fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:98 +msgid "Replenishment report fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:100 +msgid "" +"The following fields are on the :guilabel:`Replenishment` report. If any of " +"these fields are not visible, click the :guilabel:`⋮ (additional options)` " +"icon on the far right side of the report, then click the checkbox next to a " +"field to make it visible." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:104 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:105 +msgid "" +":guilabel:`Location`: the specific location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:106 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:107 +msgid ":guilabel:`On Hand`: the amount of product currently available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:108 +msgid "" +":guilabel:`Forecast`: the amount of product available after all current " +"orders (sales, manufacturing, purchase, etc.) are taken into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:110 +msgid "" +":guilabel:`Preferred Route`: how the product is procured, either " +":guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:112 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:113 +msgid "" +":guilabel:`Bill of Materials`: the bill of materials for the product (if one" +" is configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:114 +msgid "" +":guilabel:`Trigger`: how the replenishment is created, either " +":guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes " +"below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the " +"replenishment is requested)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:117 +msgid "" +":guilabel:`Procurement Group`: the reference number for how the product is " +"being acquired, such as a sales order, purchase order, or manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:119 +msgid "" +":guilabel:`Min Quantity`: the minimum amount of product that should be " +"available. When inventory levels goes below this number, the replenishment " +"is triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:121 +msgid "" +":guilabel:`Max Quantity`: the amount of product that should be available " +"after replenishing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:123 +msgid "" +":guilabel:`Multiple Quantity`: if the product should be ordered in specific " +"quantities, enter the number that should be ordered. For example, if the " +":guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 " +"products are replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:126 +msgid "" +":guilabel:`To Order`: the amount of product that is currently needed, and " +"will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate " +"Orders` button is clicked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:128 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:129 +msgid ":guilabel:`Company`: the company for which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:131 +msgid "" +"By default, the quantity in the :guilabel:`To Order` field is the quantity " +"required to reach the set :guilabel:`Max Quantity`. However, the " +":guilabel:`To Order` quantity can be adjusted by clicking on the field and " +"changing the value. To replenish a product manually, click :guilabel:`Order " +"Once`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:135 +msgid "" +"To automate a replenishment from the :guilabel:`Replenishment` page, click " +":guilabel:`Automate Orders` on the right-side of the line, represented by a " +":guilabel:`🔄 (circular arrow)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:138 +msgid "" +"When this button is clicked, Odoo will automatically generate a draft " +"|PO|/|MO| every time the forecasted stock level falls below the set " +":guilabel:`Min Quantity` of the reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:141 +msgid "" +"On the :guilabel:`Replenishment` page, a reordering rule or manual " +"replenishment can be temporarily deactivated for a given period, by clicking" +" the :guilabel:`🔕 (snooze)` icon on the far-right of the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Snooze options to turn off notifications for reordering for a period of " +"time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:149 +msgid "" +"A |PO| or |MO| created by a manual replenishment has a " +":guilabel:`Replenishment Report` as the source document. A |PO| or |MO| " +"created by an automated reordering rule has the |SO| reference number(s) " +"that triggered the rule as the source document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Quote request list shows which quotes are directly from the replenishment " +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:158 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:160 +msgid "" +"Since the |MTO| route is recommended for customized products, the route is " +"hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:169 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:163 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:164 +msgid "" +"Activate the :guilabel:`Multi-Step Routes` setting, located under the " +":guilabel:`Warehouse` section, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:166 +msgid "" +"Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:167 +msgid "" +"Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:168 +msgid "" +"Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click " +"on :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:172 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting also activates " +":guilabel:`Storage Locations`. If these features aren't applicable to the " +"warehouse, disable these settings after unarchiving the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:176 +msgid "" +"To set a product's procurement route to |MTO|, go to " +":menuselection:`Inventory app --> Products --> Products`, and click on the " +"desired product to open its product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:179 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` " +"section of options, select :guilabel:`Replenish on Order (MTO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:182 +msgid "" +"For products purchased directly from a vendor, make sure the :guilabel:`Buy`" +" route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a vendor is configured in the :guilabel:`Purchase` " +"tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:186 +msgid "" +"For products manufactured in-house, make sure the :guilabel:`Manufacture` " +"route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a bill of materials is configured for the product, " +"which is accessible via the :guilabel:`Bill of Materials` smart button on " +"the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:192 +msgid "" +"The |MTO| route cannot be selected alone. |MTO| **only** works if the " +":guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "Replenish on Order selected on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:3 +msgid "Use different units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:7 +msgid "" +"In some cases, handling products in different units of measure is necessary." +" For example, a business can buy products from a country that uses the " +"metric system, and then sell those products in a country that uses the " +"imperial system, so the business needs to convert the units. Another case " +"for unit conversion is when a business buys products in a big pack from a " +"supplier and then sells those products in individual units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:13 +msgid "Odoo can be set up to use different units of measure for one product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:18 +msgid "" +"To use different units of measure in Odoo, first go to " +":menuselection:`Inventory --> Configuration --> Settings --> Products` and " +"activate the :guilabel:`Units of Measure` setting. Then, click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "Enable Units of Measure in the Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:27 +msgid "Units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:29 +msgid "" +"After enabling the units of measure setting, view the default units of " +"measure categories in :menuselection:`Inventory --> Configuration --> Units " +"of Measures --> UoM Categories`. The category is important for unit " +"conversion, Odoo can only convert a product's units from one unit to another" +" only if both units belong to the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "Set units of measure categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:38 +msgid "" +"Each units of measure category has a reference unit. The reference unit is " +"highlighted in blue in the :guilabel:`Uom` column of the :guilabel:`Units of" +" Measure Categories` page. Odoo uses the reference unit as a base for any " +"new units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:42 +msgid "" +"To create a new unit, first select the correct category. For example, to " +"sell a product in a box of six units, click on the :guilabel:`Unit` category" +" line. Next, click :guilabel:`Edit`. After that, click :guilabel:`Add a " +"line`. Then, in the :guilabel:`Unit of Measure` field, title the new unit " +"`Box of 6`. In the :guilabel:`Type` field, select :guilabel:`Bigger than the" +" reference Unit of Measure`. In the :guilabel:`Ratio` field, enter `6.00000`" +" since a box of six is six times bigger than the reference unit (`1.00000`)." +" Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:49 +msgid "Click on the :guilabel:`Unit` category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:51 +msgid "" +"Click :guilabel:`Add a line`. As an example, we will create a Box of 6 units" +" that we will use for the Egg product. The box of 6 is 6 times bigger than " +"the reference unit of measure for the category which is “Units” here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "" +"Convert products from one unit to another as long as they belong to the same" +" category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:60 +msgid "Specify a product's units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:62 +msgid "" +"To set units of measure on a product, first go to :menuselection:`Inventory " +"--> Products --> Products` and click on a product to open its settings. " +"Then, click on :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:65 +msgid "" +"In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of " +"Measure` field to specify the unit of measure that the product is sold in. " +"The specified unit will also be the unit used to keep track of the product's" +" inventory and internal transfers. Edit the :guilabel:`Purchase UoM` field " +"to specify the unit of measure that the product is purchased in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:71 +msgid "Unit conversion" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:74 +msgid "Buy products in the Purchase UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:76 +msgid "" +"When creating a new request for quotation (RFQ) in the Purchase app, Odoo " +"automatically uses the product's specified purchase unit of measure. " +"However, if needed, the :guilabel:`UoM` can be manually edited on the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:80 +msgid "" +"After the RFQ is confirmed into a purchase order (PO), click on the " +":guilabel:`Receipt` smart button at the top right corner of the PO. Odoo " +"automatically converts the purchase unit of measure into the product's " +"sales/inventory unit of measure, so the :guilabel:`Demand` column of the " +"delivery receipt shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:85 +msgid "" +"For example, if the product's purchase UoM is `Box of 6` and its " +"sales/inventory unit of measure is `Units`, the PO shows the quantity in " +"boxes of six, and the delivery receipt shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:90 +msgid "Replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:92 +msgid "" +"A request for quotation for a product can also be generated directly from " +"the product form using the :guilabel:`Replenish` button. After clicking " +":guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit " +"of measure can be manually edited here if needed. Then, click " +":guilabel:`Confirm` to create the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:97 +msgid "" +"Next, click the :guilabel:`Units Forecasted` smart button on the product " +"form and scroll down to :menuselection:`Forecasted Inventory --> Requests " +"for quotation`. Click on the RFQ reference number to open the draft RFQ. The" +" purchase UoM can also be edited here if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:102 +msgid "Sell in a different UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:104 +msgid "" +"When creating a new quotation in the Sales app, Odoo automatically uses the " +"product's specified unit of measure. However, if needed, the :guilabel:`UoM`" +" can be manually edited on the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:107 +msgid "" +"After the quotation is sent to the customer and confirmed into a sales order" +" (SO), click on the :guilabel:`Delivery` smart button at the top right " +"corner of the SO. Odoo automatically converts the unit of measure into the " +"product's inventory unit of measure, so the :guilabel:`Demand` column of the" +" delivery shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:112 +msgid "" +"For example, if the product's UoM on the SO was changed to `Box of 6`, but " +"its inventory unit of measure is `Units`, the SO shows the quantity in boxes" +" of six, and the delivery shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:5 +msgid "Product tracking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 +msgid "Difference between lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:5 +msgid "" +"*Lots* and *serial numbers* are the two ways to identify and track products " +"in Odoo. While there are similarities between the two traceability methods, " +"there are also notable differences that affect receipts, deliveries, and " +"inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:9 +msgid "" +"A *lot* usually indicates a specific batch of an item that was received, is " +"currently stored, or was shipped from a warehouse. However, it can also " +"pertain to a batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:13 +msgid "" +"A *serial number* is a unique identifier assigned incrementally (or " +"sequentially) to an item or product, used to distinguish it from other items" +" or products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:17 +msgid ":doc:`lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:23 +msgid "" +"To track products using lots and serial numbers, the *Lots & Serial Numbers*" +" feature must be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:26 +msgid "" +"To do that, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Traceability` section, and click " +"the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " +":guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled lots and serial numbers feature in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:35 +msgid "When to use lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:37 +msgid "" +"Lots are useful for products that are manufactured or received in large " +"quantities, such as clothes or food. Lots and can be used to trace a product" +" back to a group, which is especially useful when managing product recalls " +"or expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "Created lot with quantity of products in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 +msgid "" +"Manufacturers assign lot numbers to groups of products that have common " +"properties; this can lead to multiple goods sharing the same lot number. " +"This helps identify a number of products in a single group, and allows for " +"end-to-end traceability of these products through each step in their life " +"cycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:52 +msgid "When to use serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:54 +msgid "" +"The goal of assigning serial numbers to individual products is to make sure " +"every item's history is identifiable when it travels through the supply " +"chain. This can be especially useful for manufacturers that provide after-" +"sales services related to products they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "List of serial numbers for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:63 +msgid "" +"Serial numbers can contain many different types of characters: numbers, " +"letters, typographical symbols, or a mixture of all three types." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 +msgid "Traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 +msgid "" +"Manufacturers and companies can refer to traceability reports to see the " +"entire life cycle of a product. These reports include vital information, " +"like where it came from (and when), where it was stored, and to whom it was " +"sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:73 +msgid "" +"To see the full traceability of a product, or group products by lots and/or " +"serial numbers, go to :menuselection:`Inventory app --> Products --> " +"Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` " +"dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:77 +msgid "" +"From here, products with lots or serial numbers assigned to them are listed " +"by default. They can also be expanded to show what lots or serial numbers " +"have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:80 +msgid "" +"To group by lots or serial numbers, first remove any default filters from " +"the search bar in the upper-right corner. Then, click :guilabel:`Group By`, " +"and select :guilabel:`Add Custom Group`, which reveals a mini drop-down " +"menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, " +"and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:85 +msgid "" +"Doing so reveals all existing lots and serial numbers, and each can be " +"expanded to show all product quantities with that assigned number. For " +"unique serial numbers that are *not* reused, there should *only* be one " +"product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst-1 +msgid "Reporting page with drop-down lists of lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:94 +msgid "" +"For additional information regarding an individual lot number or serial " +"number, click the line item for the lot or serial number to reveal that " +"specific number's :guilabel:`Lot` or :guilabel:`Serial Number` form. From " +"this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart" +" buttons to see all stock on-hand using that serial number. Any operations " +"made using that lot or serial number can be found here, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 +msgid "Expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:7 +msgid "" +"In Odoo, *expiration dates* can be used to manage and track the lifecycles " +"of perishable products, from purchase to sale. Using expiration dates " +"reduces product loss due to unexpected expiry, and helps to avoid sending " +"expired products to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:11 +msgid "" +"In Odoo, only products that are tracked using *lots* and *serial numbers* " +"can be assigned expiration information. Once a lot or serial number has been" +" assigned, an expiration date can be set. This is especially helpful for " +"companies (such as food manufacturers) that consistently, or exclusively, " +"buy and sell perishable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:17 +msgid ":doc:`../product_tracking/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:18 +msgid ":doc:`../product_tracking/serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:21 +msgid "Enable expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:23 +msgid "" +"To enable the use of *expiration dates*, go to :menuselection:`Inventory app" +" --> Configuration --> Settings`, and scroll down to the " +":guilabel:`Traceability` section. Then, click the checkbox to enable the " +":guilabel:`Lots & Serial Numbers` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:27 +msgid "" +"Once that feature is activated, a new option will appear to enable " +":guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and" +" be sure to :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Enabled lots and serial numbers and expiration dates settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:35 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional " +"features appear to :guilabel:`Display Lots & Serial Numbers on Delivery " +"Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to " +":guilabel:`Display Expiration Dates on Delivery Slips`. Activating these " +"features helps with end-to-end traceability, making it easier to manage " +"product recalls, identify \"bad\" batches of products, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:42 +msgid "Configure expiration dates on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:44 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` " +"features have been enabled in the settings of the *Inventory* app, " +"expiration information can be configured on individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:48 +msgid "" +"To do so, go to :menuselection:`Inventory app --> Products --> Products`, " +"and select a product to edit. Selecting a product reveals the product form " +"for that particular item. Once on the product form, click :guilabel:`Edit` " +"in the upper-left corner to make changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:53 +msgid "" +"To be tracked using lots or serial numbers, or to configure expiration " +"information, products *must* have their :guilabel:`Product Type` set as " +":guilabel:`Storable Product` under the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:57 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and scroll down to the " +":guilabel:`Traceability` section. From here, make sure that either " +":guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:61 +msgid "" +"Once it is, a new :guilabel:`Expiration Date` checkbox appears that must " +"also be clicked. When both are enabled, a new :guilabel:`Dates` field " +"appears to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:65 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed in order " +"to assign lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:70 +msgid "" +"For processing large quantities of products on receipts or deliveries, it is" +" recommended to track using lots, so multiple products can be traced back to" +" the same lot, if any issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Expiration dates configuration on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:77 +msgid "" +"Under the :guilabel:`Dates` field, there are four categories of expiration " +"information to configure for the product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:80 +msgid "" +":guilabel:`Expiration Time`: the number of days after receiving products " +"(either from a vendor or in stock after production) in which goods may " +"become dangerous and should not be used or consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:82 +msgid "" +":guilabel:`Best Before Time`: the number of days before the expiration date " +"in which the goods start deteriorating, **without** necessarily being " +"dangerous yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:84 +msgid "" +":guilabel:`Removal Time`: the number of days before the expiration date in " +"which the goods should be removed from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:86 +msgid "" +":guilabel:`Alert Time`: the number of days before the expiration date in " +"which an alert should be raised on goods in a particular lot or containing a" +" particular serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:90 +msgid "" +"The values entered into these fields automatically compute the expiration " +"date for goods entered into stock, whether purchased from a vendor or " +"manufactured in-house." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:93 +msgid "" +"Once all the expiration information has been configured, click " +":guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:96 +msgid "" +"If the :guilabel:`Dates` field is not populated with any values for " +"expiration information, dates (and lots) can be manually assigned upon " +"receipts and deliveries in and out of the warehouse. Even when assigned, " +"they can still be overwritten and changed manually if needed, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:101 +msgid "Set expiration dates on receipts with lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:103 +msgid "" +"Generating expiration dates for **incoming** goods can be done directly from" +" the purchase order. To create a purchase order, go to the " +":menuselection:`Purchase` app and click :guilabel:`Create` to create a new " +"request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:107 +msgid "" +"Then, fill out the information by adding a :guilabel:`Vendor`, and add " +"products to the :guilabel:`Product` lines by clicking :guilabel:`Add a " +"product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:110 +msgid "" +"Choose the desired quantity to order by changing the number in the " +":guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This " +"converts the :abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:114 +msgid "" +"Click the :guilabel:`Receipt` smart button at the top of the purchase order " +"to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:118 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities causes a :guilabel:`User Error` popup to appear. " +"The popup requires entry of a lot or serial number for the ordered products." +" The :abbr:`RFQ (request for quotation)` cannot be validated without an " +"assigned lot or serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:127 +msgid "" +"From here, click the :guilabel:`Additional Options` menu (hamburger) icon " +"located on the far-right of the product line. When clicked, a " +":guilabel:`Detailed Operations` pop-up will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:130 +msgid "" +"In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial " +"number under the :guilabel:`Lot/Serial Number Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:133 +msgid "" +"An expiration date automatically populates, based on the configuration on " +"the product form (if previously configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:137 +msgid "" +"If the :guilabel:`Dates` field on the product form has not been configured, " +"this date can be manually entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:140 +msgid "" +"After the expiration date has been established, mark the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, " +"click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "" +"Detailed operations popup showing expiration dates for ordered products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:147 +msgid "" +"A :guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial " +"#`; and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:153 +msgid "Set expiration dates on manufactured products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:155 +msgid "" +"Expiration dates can also be generated for products manufactured in-house. " +"To assign expiration dates to manufactured products, a manufacturing order " +"(MO) needs to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:158 +msgid "" +"To create a :abbr:`MO (manufacturing order)`, go to " +":menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, " +"and click :guilabel:`Create`. Choose a product to manufacture from the " +":guilabel:`Product` field drop-down menu, then select the " +":guilabel:`Quantity` to produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Manufacturing order for product with expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:167 +msgid "" +"To manufacture a product, there must be materials to consume in the lines in" +" the :guilabel:`Product` column. This can be achieved either by creating a " +":guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding" +" materials to consume by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:172 +msgid "Once ready, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:174 +msgid "" +"Next to :guilabel:`Lot/Serial Number`, either select an existing lot number " +"from the drop-down menu, or click the green :guilabel:`+` sign to " +"automatically assign a new lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:177 +msgid "" +"Then, select a number of units for the :guilabel:`Quantity` field, and click" +" :guilabel:`Mark as Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:180 +msgid "" +"Click on the :guilabel:`External Link` icon in the assigned " +":guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail " +"form for that specific number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:183 +msgid "" +"On that pop-up, under the :guilabel:`Dates` tab, all expiration information " +"that was previously configured for the product is displayed. That same " +"information is also available on the detail form for that specific product, " +"or by going to :menuselection:`Inventory app --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Dates tab with expiration information for specific lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:193 +msgid "Sell products with expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:195 +msgid "" +"Selling perishable products with expiration dates is done the same as any " +"other type of product. The first step in selling perishable products is to " +"create a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:198 +msgid "" +"To do that, go to :menuselection:`Sales app --> Create` to create a new " +"quotation, and fill out the information on the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:201 +msgid "" +"Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the " +"desired products to the :guilabel:`Product` lines, and set a " +":guilabel:`Quantity` for the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:204 +msgid "" +"Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` " +"section, change the :guilabel:`Delivery Date` to a date after the expected " +"date, and click the :guilabel:`green checkmark` icon to confirm the date. " +"Finally, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:208 +msgid "" +"Next, click the :guilabel:`Delivery` smart button at the top of the sales " +"order to see the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:211 +msgid "" +"On the warehouse receipt form, click :guilabel:`Validate`, and then " +":guilabel:`Apply` in the accompanying pop-up window, to automatically " +"process all :guilabel:`Done` quantities, and deliver the products to the " +"customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:215 +msgid "" +"If the products are delivered before the :guilabel:`Alert Date` set on the " +"product form, then no alerts will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:219 +msgid "" +"To sell perishable products with expiration dates, the :guilabel:`Removal " +"Strategy` for the :guilabel:`Location` the products are stored in must be " +"set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock " +"of perishable products in one lot, Odoo will automatically take the " +"remaining quantity required from a second lot with the next-soonest " +"expiration date. Removal strategies can also be set on :guilabel:`Product " +"Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:226 +msgid ":doc:`../../warehouses_storage/advanced_operations_warehouse/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:229 +msgid "View expiration dates for lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:231 +msgid "" +"To view (and/or group) all products with expiration dates by lot number, go " +"to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:234 +msgid "" +"Once there, remove any default search filters from the :guilabel:`Search...`" +" bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`," +" and select the :guilabel:`Expiration Date` parameter from the drop-down " +"menu. Finally, click :guilabel:`Apply` to apply the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:238 +msgid "" +"Doing so breaks down all perishable products, their expiration dates, and " +"the assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Group by expiration dates on lots and serial numbers page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:245 +msgid "Expiration alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:247 +msgid "" +"To see expiration alerts, go to :menuselection:`Inventory app --> Products " +"--> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:249 +msgid "" +"Then, click into a :guilabel:`Lot/Serial Number` with perishable products. " +"Doing so reveals the serial number detail form. On the serial number detail " +"form, click the :guilabel:`Dates` tab to see all expiration information " +"related to the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:253 +msgid "" +"To edit the form, click :guilabel:`Edit` in the upper-left corner of the " +"form, then change the :guilabel:`Expiration Date` to today's date (or " +"earlier), and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:257 +msgid "" +"After saving, the lot number form displays a red :guilabel:`Expiration " +"Alert` at the top of the form to indicate that the products in this lot are " +"either expired or expiring soon. From here, click back to the " +":guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:261 +msgid "" +"To see the new expiration alert, or any expiration alerts for products that " +"are expired (or will expire soon), remove all of the search filters from the" +" :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:265 +msgid "" +"Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Expiration alert for product past the expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:3 +msgid "Use lots to manage groups of products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:5 +msgid "" +"*Lots* are one of the two ways to identify and track products in Odoo. A lot" +" usually indicates a specific batch of an item that was received, is " +"currently stored, or was shipped from a warehouse, but can also pertain to a" +" batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:9 +msgid "" +"Manufacturers assign lot numbers to groups of products that have common " +"properties; this can lead to multiple goods sharing the same lot number. " +"This helps to identify a number of products in a single group, and allows " +"for end-to-end traceability of these products through each step in their " +"lifecycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:14 +msgid "" +"Lots are useful for products that are manufactured or received in large " +"quantities (such as clothes or food), and can be used to trace a product " +"back to a group. This is especially useful when managing product recalls or " +"expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 +msgid "" +"To track products using lots, the *Lots & Serial Numbers* feature must be " +"enabled. Go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Traceability` section, and click " +"the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " +":guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 +msgid "Track products by lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:38 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be configured to be tracked using lots. To do " +"this, go to the :menuselection:`Inventory app --> Products --> Products`, " +"and choose a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:42 +msgid "" +"Once on the product form, click :guilabel:`Edit` to make changes to the " +"form. Then, click the :guilabel:`Inventory` tab. In the " +":guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click " +":guilabel:`Save` to save changes. Existing or new lot numbers can now be " +"assigned to newly-received or manufactured batches of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:48 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed to assign" +" lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled tracking by lots feature on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:56 +msgid "Create new lots for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:58 +msgid "" +"New lots can be created for products already in stock with no assigned lot " +"number. To do this, go to the :menuselection:`Inventory app --> Products -->" +" Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a " +"separate page where a new :guilabel:`Lot/Serial Number` is generated " +"automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:64 +msgid "" +"While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to " +"follow the most recent number, it can be edited and changed to any desired " +"number, by clicking the line under the :guilabel:`Lot/Serial Number` field, " +"and changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:68 +msgid "" +"Once the new :guilabel:`Lot/Serial Number` is generated, click the blank " +"field next to :guilabel:`Product` to reveal a drop-down menu. From this " +"menu, select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:72 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and assign this specific lot or serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:77 +msgid "" +"A detailed description of this specific lot or serial number can also be " +"added in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:81 +msgid "" +"When all desired configurations are complete, click the :guilabel:`Save` " +"button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "New lot number creation form with assigned product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:86 +msgid "" +"After a new lot number has been created, saved, and assigned to the desired " +"product, navigate back to the product form in the :menuselection:`Inventory`" +" app, by going to :menuselection:`Products --> Products`, and selecting the " +"product to which this newly-created lot number was just assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:90 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new lot number. When additional quantity of this " +"product is received or manufactured, this new lot number can be selected and" +" assigned to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:95 +msgid "Manage lots for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:97 +msgid "" +"Lot numbers can be assigned for both **incoming** and **outgoing** goods. " +"For incoming goods, lot numbers are assigned directly on the purchase order " +"form. For outgoing goods, lot numbers are assigned directly on the sales " +"order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 +msgid "Manage lots on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 +msgid "" +"Assigning lot numbers to **incoming** goods can be done directly from the " +"purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:108 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app " +"--> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:111 +msgid "" +"On this :abbr:`RFQ (request for quotation)`, fill out the necessary " +"information by adding a :guilabel:`Vendor`, and adding the desired products " +"to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` " +"(under the :guilabel:`Products` tab)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:115 +msgid "" +"Choose the desired quantity of the product to order by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:118 +msgid "" +"Once the :abbr:`RFQ (request for quotation)` has been filled out, click " +":guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is " +"confirmed, it becomes a :guilabel:`Purchase Order`, and a " +":guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` " +"smart button to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:124 +msgid "" +"Clicking :guilabel:`Validate` before assigning a lot number to the ordered " +"product quantities will result in a :guilabel:`User Error` pop-up. The pop-" +"up requires entry of a lot or serial number for the ordered products. The " +":abbr:`RFQ (request for quotation)` **cannot** be validated without a lot " +"number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Add lot/serial number user error popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:133 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +":guilabel:`hamburger (four horizontal lines)` icon, located to the right of " +"the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:137 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` " +"column, located at the bottom of the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +msgid "" +"There are two ways to assign lot numbers: **manually** and **copy/paste**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:142 +msgid "" +"**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the" +" location the products will be stored in under the :guilabel:`To` column. " +"Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` " +"quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "Assign lot number detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:151 +msgid "" +"If quantities should be processed in multiple locations and lots, click " +":guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for " +"additional quantities. Repeat until the :guilabel:`Quantity Done` matches " +"the :guilabel:`Demand`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:155 +msgid "" +"**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with " +"all of the lot numbers received from the supplier (or manually chosen to " +"assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial" +" Number Name` column. Odoo will automatically create the necessary number of" +" lines based on the amount of numbers pasted in the column. From here, the " +":guilabel:`To` locations and :guilabel:`Done` quantities can be manually " +"entered in each of the lot number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "List of lot numbers copied on excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:165 +msgid "" +"Once all product quantities have been assigned a lot number, click " +":guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:168 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`" +" assigned, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 +msgid "Manage lots on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 +msgid "" +"Assigning lot numbers to **outgoing** goods can be done directly from the " +"sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:178 +msgid "" +"To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app " +"--> Create`. Doing so reveals a new, blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:181 +msgid "" +"On this blank quotation form, fill out the necessary information by adding a" +" :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines " +"(in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:221 +msgid "" +"Then, choose the desired quantity to sell by changing the number in the " +":guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:187 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, it becomes an " +":abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 +msgid "" +"Click the :guilabel:`Delivery` smart button to view the warehouse receipt " +"form for that specific :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:230 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +"`hamburger` icon (four horizontal lines, located to the right of the " +":guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:198 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with the full :guilabel:`Reserved` quantity taken from that specific lot (if" +" there is enough stock in that particular lot)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:202 +msgid "" +"If there is insufficient stock in that lot, or if partial quantities of the " +":guilabel:`Demand` should be taken from multiple lots, change the quantity " +"in the :guilabel:`Done` column to only include that specific part of the " +"total quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:207 +msgid "" +"The lot automatically chosen for delivery orders varies, depending on the " +"selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO " +"(Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will " +"also depend on the quantity ordered, and if there is enough quantity in one " +"lot to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:215 +msgid "" +"Then, click :guilabel:`Add a line`, select an additional (different) " +":guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click" +" the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Detailed operations popup for source lot number on sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:223 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:228 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order, if the product quantities shared " +"the same lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 +msgid "Manage lots for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:234 +msgid "" +"In Odoo, the creation of new lots is only allowed upon **receiving** " +"products from a purchase order, by default. **Existing** lot numbers cannot " +"be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:237 +msgid "" +"For sales orders, the opposite is true: new lot numbers cannot be created on" +" the delivery order, only existing lot numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:240 +msgid "" +"To change the ability to use new (or existing) lot numbers on any operation " +"type, go to the :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:244 +msgid "" +"For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` " +"page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be " +"enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside" +" the :guilabel:`Use Existing Lots/Serial Numbers` option (in the " +":guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button" +" to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:249 +msgid "" +"For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking " +"the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. " +"Be sure to click the :guilabel:`Save` button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled traceability setting on operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:258 +msgid "" +"For inter-warehouse transfers involving products tracked by lots, it can be " +"useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for" +" warehouse receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 +msgid "Lots traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:264 +msgid "" +"Manufacturers and companies can refer to traceability reports to see the " +"entire lifecycle of a product: where (and when) it came from, where it was " +"stored, and who (and when) it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:267 +msgid "" +"To see the full traceability of a product, or group by lots, go to the " +":menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :menuselection:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:271 +msgid "" +"From here, products with lot numbers assigned to them will be listed by " +"default, and can be expanded to show the lot numbers those products have " +"assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:274 +msgid "" +"To group by lots (or serial numbers), begin by removing any filters in the " +"search bar. Then, click the :guilabel:`Group By` drop-down, select " +":guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from " +"the drop-down menu. Then, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:278 +msgid "" +"Doing so displays all existing lots and serial numbers, and can be expanded " +"to show all quantities of products with that assigned number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Lots and serial numbers traceability report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:286 +msgid ":doc:`differences`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 +msgid "Use serial numbers to track products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:5 +msgid "" +"*Serial numbers* are one of the two ways to identify and track products in " +"Odoo. A serial number is a unique identifier assigned incrementally (or " +"sequentially) to an item or product, used to distinguish it from other items" +" and products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:9 +msgid "" +"Serial numbers can consist of many different types of characters: they can " +"be strictly numerical, they can contain letters and other typographical " +"symbols, or they can be a mix of all of the above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:12 +msgid "" +"The goal of assigning serial numbers to individual products is to make sure " +"that every item's history is identifiable when it travels through the supply" +" chain. This can be especially useful for manufacturers that provide after-" +"sales services to products that they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:17 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 +msgid "" +"To track products using serial numbers, the :guilabel:`Lots & Serial " +"Numbers` feature must be enabled. To enable this, go to " +":menuselection:`Inventory app --> Configuration --> Settings`, scroll down " +"to the :guilabel:`Traceability` section, and click the box next to " +":guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` " +"button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled lots and serial numbers setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:34 +msgid "Configure serial number tracking on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:36 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be tracked using serial numbers. To configure " +"this, go to :menuselection:`Inventory app --> Products --> Products`, and " +"choose a desired product to track." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:40 +msgid "" +"Once on the product form, click :guilabel:`Edit`, and click the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:42 +msgid "" +"Once on the product form, click :guilabel:`Edit`, navigate to the " +":guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` " +"section. Then, select the :guilabel:`By Unique Serial Number` option, and " +"click :guilabel:`Save` to save the changes. Existing or new serial numbers " +"can now be selected and assigned to newly-received or manufactured batches " +"of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled serial number tracking on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:52 +msgid "" +"If a product doesn't have a serial number assigned to it, a user error pop-" +"up window will appear. The error message states that the product(s) in stock" +" have no lot/serial number. However, a lot/serial number can be assigned to " +"the product by making an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:57 +msgid "Create new serial numbers for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:59 +msgid "" +"New serial numbers can be created for products already in stock with no " +"assigned serial number. To do this, go to :menuselection:`Inventory --> " +"Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so " +"reveals a blank lots/serial numbers form. On this form, a new " +":guilabel:`Lot/Serial Number` is generated automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:65 +msgid "" +"While Odoo automatically generates a new lot/serial number to follow the " +"most recent number, it can be edited and changed to any desired number, by " +"clicking the line under the :guilabel:`Lot/Serial Number` field, and " +"changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:69 +msgid "" +"Once the :guilabel:`Lot/Serial Number` is generated, click the blank field " +"next to :guilabel:`Product` to reveal a drop-down menu. From this menu, " +"select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:73 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, to " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and to assign this specific lot/serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:78 +msgid "" +"A detailed description of this specific lot/serial number can also be added " +"in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "New serial number created for existing product stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:87 +msgid "" +"After a new serial number has been created, assigned to the desired product," +" and saved, navigate back to the product form, by going to " +":menuselection:`Products --> Products`, and selecting the product that this " +"newly-created serial number was just assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:91 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:95 +msgid "Manage serial numbers for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:97 +msgid "" +"Serial numbers can be assigned for both **incoming** and **outgoing** goods." +" For incoming goods, serial numbers are assigned directly on the purchase " +"order form. For outgoing goods, serial numbers are assigned directly on the " +"sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:102 +msgid "Manage serial numbers on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:104 +msgid "" +"Assigning serial numbers to **incoming** goods can be done directly from the" +" purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:106 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase " +"app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:109 +msgid "" +"On this :abbr:`RFQ (request for quotation)` form, fill out the necessary " +"information, by adding a :guilabel:`Vendor`, and by adding the desired " +"products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a " +"product`, under the :guilabel:`Products` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:113 +msgid "" +"Choose the desired quantity of the product to order, by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:116 +msgid "" +"When the necessary configurations are complete, click :guilabel:`Confirm " +"Order`. This will convert the :abbr:`RFQ (request for quotation)` to a " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:119 +msgid "" +"Then, click the :guilabel:`Receipt` smart button to be taken to the " +"warehouse receipt form page for that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:123 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities will cause a :guilabel:`User Error` pop-up to " +"appear. The pop-up requires entry of a lot or serial number for the ordered " +"products. The :abbr:`RFQ (request for quotation)` **cannot** be validated " +"without a serial number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "User error popup prompting serial number entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:136 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a serial number (or serial numbers) under the " +":guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-" +"up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:140 +msgid "" +"There are three ways to do this: manually assigning serial numbers, " +"automatically assigning serial numbers, and copy/pasting serial numbers from" +" a spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:144 +msgid "Assign serial numbers manually" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:146 +msgid "" +"To assign serial numbers manually, click :guilabel:`Add a line` from the " +":guilabel:`Detailed Operations` pop-up, and first choose the location where " +"the product will be stored under the :guilabel:`To` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:150 +msgid "" +"Then, type a new :guilabel:`Serial Number Name`, and set the " +":guilabel:`Done` quantity in the appropriate columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:153 +msgid "" +"Repeat this process for the quantity of products shown in the " +":guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field " +"displays the correct (matching) number of products processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:157 +msgid "Assign serial numbers automatically" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:159 +msgid "" +"If a large quantity of products need individual serial numbers assigned to " +"them, Odoo can automatically generate and assign serial numbers to each of " +"the individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:162 +msgid "" +"To accomplish this, start with the :guilabel:`First SN` field in the " +":guilabel:`Detailed Operations` pop-up window, and type the first serial " +"number in the desired order to be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:165 +msgid "" +"Then, in the :guilabel:`Number of SN` field, type the total number of items " +"that need newly-generated unique serial numbers assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:168 +msgid "" +"Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate " +"with new serial numbers matching the ordered quantity of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Automatic serial number assignment in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:176 +msgid "Copy/paste serial numbers from a spreadsheet" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:178 +msgid "" +"To copy and paste serial numbers from an existing spreadsheet, first " +"populate a spreadsheet with all of the serial numbers received from the " +"supplier (or manually chosen upon receipt). Then, copy and paste them in the" +" :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create " +"the necessary number of lines based on the amount of numbers pasted in the " +"column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:183 +msgid "" +"From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can " +"be manually entered in each of the serial number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "List of serial numbers copied in Excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:191 +msgid "" +"For purchase orders that include large quantities of products to receive, " +"the best method of serial number assignment is to automatically assign " +"serial numbers using the :guilabel:`Assign Serial Numbers` button located on" +" the :abbr:`PO (purchase order)`. This prevents any serial numbers from " +"being reused or duplicated, and improves traceability reporting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:196 +msgid "" +"Once all product quantities have been assigned a serial number, click the " +":guilabel:`Confirm` button to close the pop-up. Then, click " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:199 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 +msgid "" +"Once all product quantities have been assigned a serial number, click " +":guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A " +":guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:211 +msgid "Manage serial numbers on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:213 +msgid "" +"Assigning serial numbers to **outgoing** goods can be done directly from the" +" sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:215 +msgid "" +"To create an :abbr:`SO (sales order)`, navigate to the " +":menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing " +"so reveals a new, blank quotation form. On this blank quotation form, fill " +"out the necessary information, by adding a :guilabel:`Customer`, and adding " +"products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` " +"tab), by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:223 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, the quotation " +"becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button" +" appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:234 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with each product of the total :guilabel:`Reserved` quantity listed with " +"their unique serial numbers (most likely listed in sequential order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:238 +msgid "" +"To manually change a product's serial number, click the drop-down menu under" +" :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial " +"number. Then, mark the :guilabel:`Done` quantities, and click " +":guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:242 +msgid "" +"Finally, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Serial numbers listed in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:248 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:253 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order (PO), if any of the product " +"quantities shared a serial number assigned during receipt of that specific " +":abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:258 +msgid "Manage serial numbers for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:260 +msgid "" +"By default in Odoo, the creation of new serial numbers is only allowed upon " +"**receiving** products from a purchase order. **Existing** serial numbers " +"cannot be used. For sales orders, the opposite is true: new serial numbers " +"cannot be created on the delivery order, only existing serial numbers can be" +" used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:265 +msgid "" +"To change the ability to use new (or existing) serial numbers on any " +"operation type, go to :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:269 +msgid "" +"For the :guilabel:`Receipts` operation type, found on the " +":guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the " +":guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then " +"clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial " +"Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the" +" :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:275 +msgid "" +"For the :guilabel:`Delivery Orders` operation type, located on the " +":guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` " +"from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and " +"clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` " +"option (in the :guilabel:`Traceability` section). Be sure to click " +":guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled traceability setting in operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:286 +msgid "Serial number traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:288 +msgid "" +"Manufacturers and companies can refer to the traceability reports to see the" +" entire lifecycle of a product: where it came from (and when), where it was " +"stored, and who it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:291 +msgid "" +"To see the full traceability of a product, or group by serial numbers, go to" +" :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:295 +msgid "" +"From here, products with serial numbers assigned to them will be listed by " +"default, and can be expanded to show what serial numbers have been " +"specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:298 +msgid "" +"To group by serial numbers (or lots), first remove any default filters from " +"the search bar in the upper-right corner. Then, click :guilabel:`Group By`, " +"and select :guilabel:`Add Custom Group`, which reveals a mini drop-down " +"menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, " +"and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:303 +msgid "" +"Doing so reveals all existing serial numbers and lots, and can be expanded " +"to show all quantities of products with that assigned number. For unique " +"serial numbers that are not reused, there should be just one product per " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Serial numbers reporting page with drop-down lists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:312 +msgid "" +"For additional information regarding an individual serial number (or lot " +"number), click the line item for the serial number to reveal that specific " +"serial number's :guilabel:`Serial Number` form. From this form, click the " +":guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all " +"stock on-hand using that serial number, and any operations made using that " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 +msgid "Shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse.rst:5 +msgid "Advanced operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:12 +msgid "" +"It will allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:20 +msgid "" +"If the delivery order is not **Validated**, then the request hasn't been " +"made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:24 +msgid "" +"If you have clicked on **Validate**, the request has been made and you " +"should have received the tracking number and the label. You can still cancel" +" the request. Simply click on the **Cancel** button next to the **Carrier " +"Tracking Ref**:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:42 +msgid "" +"After cancelling the shipping request, you can change the carrier you want " +"to use. Confirm it by clicking on the **Send to shipper** button. You will " +"get a new tracking number and a new label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:115 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:3 +msgid "Use dropshipping to ship directly from suppliers to customers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:5 +msgid "" +"Dropshipping is an order fulfillment strategy that allows sellers to have " +"items shipped directly from suppliers to customers. Normally, a seller " +"purchases a product from a supplier, stores it in their inventory, and ships" +" it to the end customer once an order is placed. With dropshipping, the " +"supplier is responsible for storing and shipping the item. This benefits the" +" seller by reducing inventory costs, including the price of operating " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 +msgid "" +"To use dropshipping as a fulfillment strategy, navigate to the " +":menuselection:`Purchase` app and select :menuselection:`Configuration --> " +"Settings`. Under the :guilabel:`Logistics` heading, click the " +":guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:18 +msgid "" +"Next, go to the :menuselection:`Sales` app, click :menuselection:`Products " +"--> Products` and choose an existing product or select :guilabel:`Create` to" +" configure a new one. On the :guilabel:`Product` page, make sure that the " +":guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are " +"enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the " +"product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:27 +msgid "" +"Click on the :guilabel:`Purchase` tab and specify a vendor and the price " +"that they sell the product for. Multiple vendors can be added, but the " +"vendor at the top of the list will be the one automatically selected for " +"purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:35 +msgid "" +"Finally, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 +msgid "" +"When a customer completes an online purchase for a dropshipped product, a " +"sales order will be automatically created with an associated request for " +"quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales " +"orders can be viewed in the :menuselection:`Sales` app by selecting " +":menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart " +"button at the top right of a sales order to view the associated :abbr:`RFQ " +"(Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:52 +msgid "" +"Dropship sales orders can also be created manually through the " +":menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders " +"--> Create` and adding a product configured for dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"A dropship sales order with the Purchase smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:60 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a " +"purchase order and a dropship receipt is created and linked to it. The " +"receipt can be viewed by clicking the :guilabel:`Receipt` smart button in " +"the top right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"A dropship purchase order with the Receipt smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:68 +msgid "" +"The dropship receipt will list the supplier in the :guilabel:`Receive From` " +"section and the customer in the :guilabel:`Destination Location` section. " +"Upon delivery of the product to the customer, click on the " +":guilabel:`Validate` button at the top left of the dropship receipt to " +"confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:77 +msgid "" +"To view all dropship orders, simply navigate to the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal" +" :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"Click the green button on the Dropship card to view all dropship orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:12 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:15 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:20 +msgid "" +"To configure the price of your delivery methods, go to the **Inventory** " +"app, click on :menuselection:`Configuration --> Delivery --> Delivery " +"Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:23 +msgid "" +"You can manually set a price for the shipping: It can be fixed or based on " +"rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:26 +msgid "" +"Or you can use the transportation company computation system by " +":doc:`integrating a third-party shipper " +"<../setup_configuration/third_party_shipper>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:33 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 +msgid "" +"On your sale order, choose the carrier that will be used. Click on " +"**Delivery Method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 +msgid "" +"The price is computed when you **save** the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:44 +msgid "" +"To invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 +msgid "" +"When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:55 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:63 +msgid "" +"The price is computed when you **save** the sale order. Confirm the sale " +"order and proceed to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:66 +msgid "" +"The real shipping cost is computed when the delivery order is validated, you" +" can see the real cost in the chatter of the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:72 +msgid "" +"Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:78 +msgid "" +"When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 +msgid "" +"If you split the delivery and make several ones, each delivery order will " +"add a line to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:89 +msgid ":doc:`../setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:90 +msgid ":doc:`labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:8 +msgid "" +"In Odoo, there are a variety of different types of shipping labels that can " +"be selected for delivery orders. Depending on the types of shipping packages" +" used, different label sizes may be more appropriate, and can be configured " +"to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:15 +msgid "" +"In the :menuselection:`Inventory` module, go to " +":menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a" +" delivery method to choose it. For the following example, *FedEx " +"International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:23 +msgid "" +"In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose " +"one of the label types available. The availability varies depending on the " +"carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:30 +msgid "" +"When a sales order with the corresponding shipping company is confirmed and " +"a delivery order is validated, the shipping label will be automatically " +"created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:37 +msgid "" +"In the :menuselection:`Sales` application, click :guilabel:`Create` and " +"select an international customer. Click :guilabel:`Add A Product` and select" +" an item. Click :guilabel:`Add Shipping`, select a shipping method, then " +"click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:45 +msgid "" +"Once the quotation is confirmed by clicking :guilabel:`Confirm`, a " +":guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:52 +msgid "" +"Once the delivery order is validated by clicking :guilabel:`Validate` in the" +" delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:62 +msgid "" +"The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example " +"of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers " +"linked with the transportation company tracking system. It allows you to " +"manage the transport company, the real prices and the destination. And " +"finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:20 +msgid "" +"In the **Inventory** module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:28 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:35 +msgid "Configure the delivery method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:37 +msgid "" +"To configure your delivery methods, go to the **Inventory** module, click on" +" :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:41 +msgid "" +"In the **Pricing** tab, the name of the provider means that the delivery " +"will be handled and computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:46 +msgid "" +"The first one is linked to **your account** (develop key, password,...). For" +" more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 +msgid "" +"The second column varies according to the **provider**. You can choose the " +"packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:67 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:79 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:81 +msgid "" +"In order to compute the right price, the provider needs your company " +"information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:88 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:94 +msgid "" +"The shipper companies need the weight of your product, otherwise the price " +"computation cannot be done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:73 +msgid "" +"Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open " +"the products you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:80 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to do" +" the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:87 +msgid "" +"The delivery order created from the sale order will take the shipping " +"information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:137 +msgid "" +"If you create a delivery transfer from the inventory module, you can add the" +" third party shipper in the additional info tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:96 +msgid "" +"Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:153 +msgid "" +"The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:110 +msgid "" +"If you are doing multi-packages shippings, most of the time, there will be " +"one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 +msgid "Multi-package shipments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:5 +msgid "" +"In some cases, a delivery order with multiple items may need to be shipped " +"in more than one package. This may be necessary if the items are too large " +"to ship in a single package, or if certain items cannot be packaged " +"together. Shipping a single delivery order in multiple packages provides " +"flexibility for how each item is packaged, without the need to create " +"multiple delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:13 +msgid "" +"In order to split a delivery order across multiple packages, the *Packages* " +"setting must be enabled. To do so, navigate to :menuselection:`Inventory -->" +" Configuration --> Settings`, then enable the checkbox next to " +":guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Packages setting on the Inventory app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:24 +msgid "Ship items in multiple packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:26 +msgid "" +"To split items in the same delivery order across multiple packages, begin by" +" navigating to :menuselection:`Inventory --> Delivery Orders`, then select a" +" delivery order that has multiple items, a multiple quantity of the same " +"item, or both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:30 +msgid "" +"On the :guilabel:`Operations` tab, select the :guilabel:`⁞≣ (menu)` icon in " +"the line of the product that will be shipped in the first package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The menu icon for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:37 +msgid "" +"This makes a :guilabel:`Detailed Operations` pop-up window appear. In the " +"table at the bottom of the pop-up window, the :guilabel:`Reserved` column " +"shows the total quantity of the product included in the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:41 +msgid "" +"If the full quantity will be shipped in the first package, enter the number " +"from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less" +" than the full quantity will be shipped in the first package, enter a " +"smaller number than the one that appears in the :guilabel:`Reserved` column." +" Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and " +"close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Detailed Operations pop-up for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:51 +msgid "" +"Repeat the same steps for every item quantity that is included in the first " +"package. Then, click :guilabel:`Put In Pack` to create a package with all of" +" the selected items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Put In Pack button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:58 +msgid "" +"For the next package, follow the same steps as detailed above, marking the " +"quantity of each item to be included in the package as :guilabel:`Done` " +"before clicking :guilabel:`Put In Pack` on the delivery order. Continue " +"doing so until the full quantity of all items are added to a package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:62 +msgid "" +"Finally, after all of the packages have been shipped, click " +":guilabel:`Validate` to confirm that the delivery order has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:66 +msgid "" +"After one or more packages are created, a :guilabel:`Packages` smart button " +"appears in the top-right corner of the delivery order. Click the " +":guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for" +" the delivery order, where each package can be selected to view all of the " +"items included in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:0 +msgid "The Packages smart button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:76 +msgid "Create a backorder for items to be shipped later" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:78 +msgid "" +"If some items will be shipped at a later date than others, there is no need " +"to put them in a package until they are ready to be shipped. Instead, create" +" a backorder for the items being shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:81 +msgid "" +"Begin by shipping the items that will be shipped immediately. If they will " +"be shipped in multiple packages, follow the :ref:`steps above " +"` to package them as required. If they" +" will be shipped in a single package, simply mark in the :guilabel:`Done` " +"column the quantity of each item being shipped, but **do not** click the " +":guilabel:`Put In Pack` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:86 +msgid "" +"After all quantities being shipped immediately are marked as " +":guilabel:`Done`, click the :guilabel:`Validate` button, and a " +":guilabel:`Create Backorder?` pop-up window appears. Then, click the " +":guilabel:`Create Backorder` button. Doing so confirms the items being " +"shipped immediately and creates a new delivery order for the items that will" +" be shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Create Backorder? pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:95 +msgid "" +"The backorder delivery order will be listed in the chatter of the original " +"delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX" +" has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to " +"view the backorder delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "" +"The backorder delivery order listed in the chatter of the original delivery " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:103 +msgid "" +"The backorder delivery order can also be accessed by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on" +" the :guilabel:`Delivery Orders` card, and selecting the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Back Orders button on the Delivery Orders card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:111 +msgid "" +"Once the remaining items are ready to be shipped, navigate to the backorder " +"delivery order. The items can be shipped in a single package by clicking " +":guilabel:`Validate` and selecting :guilabel:`Apply` on the " +":guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in " +"multiple packages by following the steps detailed in the section above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:116 +msgid "" +"It is also possible to ship out some of the items while creating another " +"backorder for the rest. To do so, simply follow the same steps used to " +"create the first backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 +msgid "Scheduled delivery dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:5 +msgid "" +"Accurately forecasting delivery dates is vital for fulfilling customer " +"expectations. In Odoo, the *Inventory* app allows for comprehensive lead " +"time configuration, allowing coordination and planning of manufacturing " +"orders, deliveries, and receptions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 +msgid "Lead time types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:12 +msgid "" +"Different lead times for different operations can impact various stages of " +"the order fulfillment process. Here's a summary of the types of lead times " +"in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "Show graphic of all lead times working together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:19 +msgid "" +":ref:`Customer lead time `: The default " +"time frame for fulfilling customer orders. The customer lead time is the " +"number of days from the date the sales order (SO) is confirmed to the date " +"the products are shipped from the warehouse. This is also known as *delivery" +" lead time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 +msgid "" +":ref:`Sales security lead time `: " +"moves the *scheduled delivery date* forward by a specified number of days. " +"This serves as a buffer to allow the team ample time to prepare the outgoing" +" shipment earlier, considering the possibility of delays in the fulfillment " +"process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 +msgid "" +":ref:`Purchase lead time `: the number of " +"days from the confirmation of a purchase order (PO) to the receipt of " +"products. It provides insight on the time it takes for products to arrive at" +" the warehouse, facilitating effective scheduling and planning of supplier " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 +msgid "" +":ref:`Purchase security lead time `: advances the order deadline on a :abbr:`PO (Purchase Order)` by a " +"specified number of days. This proactive approach of placing orders earlier " +"mitigates the risk of vendor or shipping delays. Thus, for products that are" +" set to replenish to order, the need appears on the *Replenishment report* " +"earlier, according to the specified number of days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:40 +msgid "" +":ref:`Manufacturing lead time `: the number " +"of days needed to complete a manufacturing order (MO) from the date of " +"confirmation. This lead time includes weekends (non-working hours in Odoo), " +"and is used to forecast an approximate production date for a finished good." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 +msgid "" +":ref:`Manufacturing security lead time `: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` " +"forward by a specified number of days. When used in conjunction with " +":ref:`replenish to order `, the " +"security lead time makes the need appear earlier on the replenishment " +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:53 +msgid "Sales lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:55 +msgid "" +"Customer lead times and sales security lead times can be configured to " +"automatically compute an *expected delivery date* on a :abbr:`SO (Sales " +"Order)`. The expected delivery date ensures a realistic *delivery dates* " +"setting for shipments from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:59 +msgid "" +"Odoo issues a warning message if the set delivery date is earlier than the " +"expected date, as it may not be feasible to fulfill the order by that time, " +"which would impact other warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:63 +msgid "" +"A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is " +"confirmed on July 11th. The product has a customer lead time of 14 days, and" +" the business uses a sales security lead time of 1 day. Based on the lead " +"time inputs, Odoo suggests a delivery date in 15 days, on July 26th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Set *Delivery Date* in a sales order. Enables delivery lead times feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 +msgid "" +"The following sections demonstrate how to automatically compute expected " +"delivery dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:74 +msgid "Customer lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:76 +msgid "" +"Set the customer lead time on each product form, by navigating to the " +"products page. To do so, go to :menuselection:`Sales app --> Products --> " +"Products`. From there, select the desired product, and switch to the " +":guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` " +"field, fill in the number of calendar days required to fulfill the delivery " +"order from start to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:82 +msgid "" +"Set a 14-day customer lead time for the `Coconut-scented candle` by " +"navigating to its product form. Then, in the :guilabel:`Inventory` tab, type" +" `14.00` days into the :guilabel:`Customer Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Set *Customer Lead Time* on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:93 +msgid "Sales security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:95 +msgid "" +"*Sales security lead time* is set globally for the business in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 +msgid "" +"On the configuration page, under the :guilabel:`Advanced Scheduling` " +"heading, locate the box for :guilabel:`Security Lead Time for Sales`, and " +"click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:101 +msgid "" +"Next, enter the desired number of calendar days. This security lead time is " +"a buffer notifying the team to prepare for outgoing shipments earlier than " +"the scheduled date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:105 +msgid "" +"Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes " +"the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. " +"In that case, if a product is initially scheduled for delivery on April 6th," +" but with a one-day security lead time, the new scheduled date for the " +"delivery order would be April 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"View of the security lead time for sales configuration from the sales " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:115 +msgid "Deliver several products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 +msgid "" +"For orders that include multiple products with different lead times, the " +"lead times can be configured directly from the quotation itself. On a " +"quotation, click the :guilabel:`Other Info` tab, and set the " +":guilabel:`Shipping Policy` to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 +msgid "" +":guilabel:`As soon as possible` to deliver products as soon as they are " +"ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is " +"determined by adding today's date to the shortest lead time among the " +"products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:125 +msgid "" +":guilabel:`When all products are ready` to wait to fulfill the entire order " +"at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` " +"is determined by adding today's date to the longest lead time among the " +"products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:134 +msgid "" +"In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the " +"products have a lead time of 8 days and 5 days, respectively. Today's date " +"is April 2nd." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 +msgid "" +"When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as " +"possible`, the scheduled delivery date is 5 days from today: April 7th. On " +"the other hand, selecting :guilabel:`When all products are ready` configures" +" the scheduled date to be 8 days from today: April 10th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:144 +msgid "Purchase lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:146 +msgid "" +"Automatically determining the dates on which to place orders from suppliers " +"can help simplify the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:149 +msgid "" +"Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO " +"(Purchase Order)` deadline, based on the required date the product is needed" +" in the warehouse. By working backwards from the receipt date, vendor lead " +"times and purchase security lead times are taken into account, in order to " +"determine the :abbr:`PO (Purchase Order)` deadline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:154 +msgid "" +"This deadline is the date by which the order should be confirmed, in order " +"to ensure timely arrival by the expected receipt date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Visualization of PO deadline and receipt date used with vendor lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 +msgid "" +":ref:`PO scheduling with reordering rules " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 +msgid "Vendor lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:167 +msgid "" +"To set a vendor lead time for orders arriving in the warehouse from a vendor" +" location, begin by navigating to a product form through " +":menuselection:`Purchase app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 +msgid "" +"Next, select the desired product, and switch to the :guilabel:`Purchase` " +"tab. In the editable vendor pricelist, click the :guilabel:`Add a line` " +"button to add vendor details, such as the :guilabel:`Vendor` name, " +":guilabel:`Price` offered for the product, and lastly, the " +":guilabel:`Delivery Lead Time`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:176 +msgid "" +"Multiple vendors and lead times can be added to the vendor pricelist. The " +"default vendor and lead time selected will be the entry at the top of the " +"list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:180 +msgid "" +"On the vendor pricelist of the product form, the :guilabel:`Delivery Lead " +"Time` for the selected vendor is set to `10 days.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Add delivery lead times to vendor pricelist on a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:187 +msgid "" +"By setting the vendor lead time, the expected arrival date of the item is " +"automatically determined as the date of the :abbr:`PO (Purchase Order)` " +"confirmation, plus the vendor lead time. This ensures that warehouse " +"employees are notified, if the products do **not** arrive within the " +"expected timeframe." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:193 +msgid "" +"On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product " +"configured with a 10-day vendor lead time, Odoo automatically sets the " +":guilabel:`Receipt Date` to July 21st. The receipt date also appears as the " +":guilabel:`Scheduled Date` on the warehouse receipt form, accessible from " +"the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase" +" Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Show expected *Receipt Date* of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Show expected *Scheduled Date* of arrival of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 +msgid "Purchase security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:211 +msgid "" +"*Purchase security lead time* is set globally for the business in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:214 +msgid "" +"On the configuration page, under the :guilabel:`Advanced Scheduling` " +"heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and" +" click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:217 +msgid "" +"Next, enter the desired number of calendar days. By configuring the security" +" lead time, a buffer is set to account for potential delays in supplier " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:221 +msgid "" +"Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, " +"pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that " +"case, if a product is initially scheduled to arrive on April 6th, with a " +"two-day security lead time, the new scheduled date for the receipt would be " +"April 8th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Set security lead time for purchase from the Inventory > Configuration > " +"Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 +msgid "Manufacturing lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:235 +msgid "" +"Lead times can help simplify the procurement process for consumable " +"materials and components used in manufactured products with bills of " +"materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:238 +msgid "" +"The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to " +"begin the manufacturing process to complete the product by the scheduled " +"delivery date, can be determined by configuring the manufacturing lead times" +" and manufacturing security lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Visualization of the determination of planned MO date manufacturing lead " +"times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:247 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 +msgid "" +"Configure the manufacturing lead time directly on the product form, by " +"navigating to :menuselection:`Manufacturing app --> Products --> Products`, " +"and select the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 +msgid "" +"In the :guilabel:`Inventory` tab of the product, specify the calendar days " +"needed to the manufacture the product in the :guilabel:`Manufacturing Lead " +"Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 +msgid "" +"Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly " +"in the :guilabel:`Inventory` tab of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"View of the manufacturing lead time configuration from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 +msgid "" +"Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the " +"*expected delivery date*, indicated in the :guilabel:`Scheduled Date` field " +"of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 +msgid "" +"The :abbr:`MO (Manufacturing Order)` deadline, which is the " +":guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is" +" calculated as the *expected delivery date* subtracted by the manufacturing " +"lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 +msgid "" +"This ensures the manufacturing process begins on time, in order to meet the " +"delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 +msgid "" +"However, it's important to note that lead times are based on calendar days. " +"Lead times do **not** consider weekends, holidays, or *work center capacity*" +" (:dfn:`the number of operations that can be performed at the work center " +"simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 +msgid ":ref:`Manufacturing planning `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 +msgid "" +":ref:`Configure automatic MO scheduling with reordering rules " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 +msgid "" +"A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is " +"August 15th. The product requires 14 days to manufacture. So, the latest " +"date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment " +"date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 +msgid "" +"*Manufacturing security lead time* is set globally for the business in " +":menuselection:`Manufacturing app --> Configuration --> Settings`. Under the" +" :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead " +"Time`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 +msgid "" +"Next, enter the desired number of calendar days. By configuring the security" +" lead time, a buffer is set to account for potential delays in the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"View of the security lead time for manufacturing from the manufacturing app " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:303 +msgid "" +"A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` " +"set for August 15th. The manufacturing lead time is 7 days, and " +"manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled " +"Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to " +"begin the manufacturing order. In this example, the planned date on the " +":abbr:`MO (Manufacturing Order)` is August 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:310 +msgid "Global example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 +msgid "" +"See the following example to understand how all the lead times work together" +" to ensure timely order fulfillment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:315 +msgid "**Sales security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:316 +msgid "**Manufacturing security lead time**: 2 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 +msgid "**Manufacturing lead time**: 3 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:318 +msgid "**Purchase security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:319 +msgid "**Vendor lead time**: 4 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:321 +msgid "" +"The customer places an order for a manufactured product on September 1st, " +"and the scheduled delivery date from the warehouse is on September 20th. " +"Odoo uses lead times and automated reordering rules to schedule the " +"necessary operations, based on the outgoing shipment delivery date, " +"September 20th:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Show timeline of how lead times work together to schedule warehouse " +"operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:329 +msgid "**September 1st**: Sales order created, confirmed by salesperson." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:331 +msgid "" +"**September 9th**: Deadline to order components to ensure they arrive in " +"time when manufacturing begins (4-day supplier lead time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:334 +msgid "" +"**September 13th**: Scheduled date of receipt for components. Initially, it " +"was set to 9/14, but the 1-day purchase security lead time pushed the date " +"earlier by 1 day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:337 +msgid "" +"**September 14th**: Deadline to begin manufacturing. Calculated by " +"subtracting the manufacturing lead time of 3 days, and the manufacturing " +"security lead time of 2 days, from the expected delivery date of September " +"19th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:341 +msgid "" +"**September 19th**: :guilabel:`Scheduled Date` on the delivery order form " +"indicates the updated expected delivery date, which was originally set as " +"September 20th. But the sales security lead time pushed the date forward by " +"a day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:345 +msgid "" +"Odoo's replenishment planning maps a business' order fulfillment process, " +"setting pre-determined deadlines and raw material order dates, including " +"buffer days for potential delays. This ensures products are delivered on " +"time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:3 +msgid "Process deliveries in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:7 +msgid "" +"Some companies process large amounts of deliveries every day, many of which " +"include multiple products or require special packaging. To make this " +"efficient, a packing step is needed before shipping out products. For this, " +"Odoo has a three step process for delivering goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:11 +msgid "" +"In the default three-step delivery process, products that are part of a " +"delivery order are picked in the warehouse according to their removal " +"strategy, and brought to a packing zone. After the items have been packed " +"into the different shipments in the packing zone, they are brought to an " +"output location before being shipped. These steps can be modified if they do" +" not fit the needs of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:20 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize three step deliveries. First, make sure the *Multi-Step" +" Routes* option is enabled in :menuselection:`Inventory --> Configuration " +"--> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step " +"Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:30 +msgid "" +"Next, the warehouse needs to be configured for three step deliveries. To do " +"this, go to :menuselection:`Inventory app --> Configuration --> Warehouses`," +" and click on the :guilabel:`warehouse` to edit. Then, select " +":guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for " +":guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "Set outgoing shipment option to deliver in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:39 +msgid "" +"Activating three-step receipts and deliveries creates two new internal " +"locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To " +"rename these locations, go to :menuselection:`Inventory app --> " +"Configuration --> Locations`, click on the :guilabel:`Location` to change, " +"and update the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 +msgid "Deliver in three steps (pick + pack + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:50 +msgid "" +"To create a new quote, navigate to :menuselection:`Sales app --> Create`, " +"which reveals a blank quotation form. On the blank quotation form, select a " +":guilabel:`Customer`, add a storable :guilabel:`Product`, and click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:54 +msgid "" +"A :guilabel:`Delivery` smart button appears in the top right of the " +"quotation form. Clicking it shows the picking order, packing order, and the " +"delivery order associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing three items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:63 +msgid "Process a picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:65 +msgid "" +"The picking, packing, and delivery orders will be created once the sales " +"order is confirmed. To view these transfers, go to " +":menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"Ready status for the pick operation while the packing and delivery operations are waiting\n" +"another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:73 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be packed. The status of the packing " +"order and delivery order will both be :guilabel:`Waiting Another Operation`," +" since the packing and delivery cannot happen until the picking is " +"completed. The status of the delivery order will only change to " +":guilabel:`Ready` when the packing has been marked :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:79 +msgid "" +"The receipt can also be found in the *Inventory* application. In the " +":guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The pick order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 +msgid "" +"Click on the picking to process. If the product is in stock, Odoo will " +"automatically reserve the product. Click :guilabel:`Validate` to mark the " +"picking as done, and complete the transfer to the :guilabel:`Packing Zone`. " +"Then the packing order will be ready. Since the documents are linked, the " +"products which have been previously picked are automatically reserved on the" +" packing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "Validate the picking by clicking Validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 +msgid "Process a packing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 +msgid "" +"The packing order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pack` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The packing order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 +msgid "" +"Click on the packing order associated with the sales order, then click on " +":guilabel:`Validate` to complete the packing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"Click Validate on the packing order to transfer the product from the packing zone to the\n" +"output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 +msgid "" +"Once the packing order is validated, the product leaves the " +":guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` " +"location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 +msgid "Process a delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:121 +msgid "" +"The delivery order will be ready to be processed once the packing is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The delivery order can be seen in the Delivery Orders Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:129 +msgid "" +"Click on the delivery order associated with the sales order, then click on " +":guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Click Validate on the delivery order to transfer the product from the output location to\n" +"the customer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:137 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location and moves to the " +":guilabel:`Partners/Customers` location. Then, the status of the document " +"will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 +msgid "Process receipts and deliveries in one step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 +msgid "" +"By default, incoming shipments are configured to be received directly into " +"stock, and outgoing shipments are configured to be delivered directly from " +"stock to the customer; the default setting for warehouses in Odoo is one " +"step receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 +msgid "" +"Incoming and outgoing shipments do not need to be configured with the same " +"steps. For example, products can be received in one step, but shipped in " +"three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 +msgid "" +"In the following example, one step will be used for both receipts and " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 +msgid "Configure the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 +msgid "" +"If another receiving or shipping configuration is set on the warehouse, they" +" can easily be set back to the one step setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:23 +msgid "" +"Begin by navigating to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, and click on the desired warehouse to edit. Next, on the " +":guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` " +"section, select :guilabel:`Receive goods directly (1 step)` for " +":guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 " +"step)` for :guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in one " +"step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:34 +msgid "Receive goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 +msgid "Create a purchase order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 +msgid "" +"On the main :menuselection:`Purchase` application dashboard, start by making" +" a new quote by clicking :guilabel:`New`. Then, select (or create) a " +":guilabel:`Vendor` from the drop-down field, add a storable " +":guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` " +"to finalize the quote as a new purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:98 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top-right corner of " +"the :abbr:`PO (purchase order)` form — click it to reveal the associated " +"receipt for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Receipt smart button appears on the confirmed purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 +msgid "" +"Purchase order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "Receipt kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 +msgid "" +"When viewing the receipt (associated with the purchase order above), click " +":guilabel:`Validate` to then complete the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Validate the purchase order via the Validate smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 +msgid "" +"If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ " +"(bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon " +"enables the :guilabel:`Detailed Operations` screen to pop-up. This allows " +"the location(s) to be specified for the received product(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "" +"Select the Storage Location for the products being received in the Detailed Operations\n" +"pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:80 +msgid "" +"Once the receipt is validated, the product leaves the :guilabel:`Supplier " +"Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives " +"here, it will be available for manufacturing, sales, etc. Then, the status " +"of the document will change to :guilabel:`Done`, thus completing the " +"reception process in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:88 +msgid "Deliver goods directly (1 step)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 +msgid "" +"Start my navigating to the main :menuselection:`Sales` app dashboard, and " +"make a new quote by clicking :guilabel:`New`. Then select (or create) a " +":guilabel:`Customer` from the drop-down field, add a storable " +":guilabel:`Product` that is in stock to the order lines, and click " +":guilabel:`Confirm` to finalize the quotation as a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 +msgid "" +"A :guilabel:`Delivery` smart button will appear in the top-right corner of " +"the :abbr:`SO (Sales Order)` form — click it to reveal the associated " +"delivery order for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "The Delivery smart button appears after the sales order is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:109 +msgid "" +"Delivery orders can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "Delivery Orders kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 +msgid "Process the delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 +msgid "" +"When viewing the delivery order (associated with the sales order above), " +"click :guilabel:`Validate` to then complete the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Validate the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:127 +msgid "" +"Once the picking order is validated, the product leaves the " +":guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers" +" location`. Then, the status of the document will change to " +":guilabel:`Done`, thus completing delivery in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 +msgid "Process receipts and deliveries in two steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:7 +msgid "" +"Depending on a company's business processes, multiple steps may be needed " +"before receiving or shipping products. In the two-step receipt process, " +"products are received in an input area, then transferred to stock. Two-step " +"receipts work best when various storage locations are being used, such as " +"locked or secured areas, freezers and refrigerators, or various shelves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 +msgid "" +"Products can be sorted according to where they are going to be stored, and " +"employees can stock all the products going to a specific location. The " +"products are not available for further processing until they are transferred" +" into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:16 +msgid "" +"In the two-step delivery process, products that are part of a delivery order" +" are picked from the warehouse according to their removal strategy, and " +"brought to an output location before being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 +msgid "" +"One situation where this would be useful is when using either a :abbr:`FIFO " +"(First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO " +"(First Expired, First Out)` removal strategy, where the products that are " +"being picked need to be selected based on their receipt date or expiration " +"date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize two-step receipts and deliveries. Incoming and outgoing" +" shipments do not need to be set to have the same steps. For example, " +"products can be received in two steps, but shipped in one step. In the " +"following example, two steps will be used for both receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 +msgid "Configure multi-step routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 +msgid "" +"First, make sure the :guilabel:`Multi-Step Routes` option is enabled in " +":menuselection:`Inventory --> Configuration --> Settings`, under the " +":guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` " +"the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting will also activate the " +":guilabel:`Storage Locations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 +msgid "" +"Next, the warehouse needs to be configured for two-step receipts and " +"deliveries. Go to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, and click on the warehouse to change the warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 +msgid "" +"Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for" +" :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and " +"then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in two " +"steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 +msgid "" +"Activating two-step receipts and deliveries will create new *input* and " +"*output* locations, which by default, are labeled :guilabel:`WH/Input` and " +":guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard." +" To rename these locations, go to :menuselection:`Configuration --> " +"Locations`, and select the :guilabel:`Location` to change. On the location " +"form, update the :guilabel:`Location Name`, and make any other changes (if " +"necessary)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 +msgid "Process a receipt in two steps (input + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 +msgid "" +"For businesses with multiple warehouses that have different step " +"configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase " +"Order)` form may need to be specified as the correct *input location* " +"connected to the two-step warehouse, which can be done by selecting the " +"warehouse from the drop-down selection that includes the `Receipts` label at" +" the end of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 +msgid "" +"After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` " +"smart button will appear in the top of the :abbr:`PO (Purchase Order)` form " +"— click it to reveal the associated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "After confirming a purchase order, a Receipt smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 +msgid "One receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 +msgid "" +"The receipt and internal transfer will be created once the purchase order is" +" confirmed. The status of the receipt will be :guilabel:`Ready`, since the " +"receipt must be processed first. The status of the internal transfer will be" +" :guilabel:`Waiting Another Operation`, since the transfer cannot happen " +"until the receipt is completed. The status of the internal transfer will " +"only change to :guilabel:`Ready` once the receipt has been marked as " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 +msgid "" +"Click on the :guilabel:`Receipt` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"the :guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, then the product will be transferred to the\n" +"WH/Input location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 +msgid "Process the internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product into stock. Navigate to the " +":menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` " +"dashboard, click the :guilabel:`# To Process` smart button in the " +":guilabel:`Internal Transfers` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"One Internal Transfer ready to process in the Inventory Overview kanban " +"view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"stock. Once the transfer is validated, the product enters the stock and is " +"available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "Validate the internal transfer to move the item to stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 +msgid "Process a delivery order in two steps (pick + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 +msgid "" +"In the :menuselection:`Sales` application, create a new quote by clicking " +":guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable " +":guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 +msgid "" +"After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart " +"button will appear in the top, above the :abbr:`SO (Sales Order)` form. " +"Click the :guilabel:`Delivery` smart button to reveal the associated " +"receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing two items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 +msgid "" +"Sales order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"To Process` smart button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 +msgid "The pick order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 +msgid "Process the picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 +msgid "" +"The picking and delivery order will be created once the sales order is " +"confirmed. When the :guilabel:`Delivery` smart button appears, click it to " +"reveal the :guilabel:`Transfers` dashboard, which lists both the picking and" +" the delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be shipped. The status of the delivery " +"order will be :guilabel:`Waiting Another Operation`, since the delivery " +"cannot happen until the picking is completed. The status of the delivery " +"order will only change to :guilabel:`Ready` once the picking has been marked" +" as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Ready status for the pick operation while the delivery operation is Waiting Another\n" +"Operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 +msgid "" +"Click on the picking delivery order to begin processing it. If the product " +"is in stock, Odoo will automatically reserve the product. Click " +":guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the " +"delivery order will be ready for processing. Since the documents are linked," +" the products which have been previously picked are automatically reserved " +"on the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 +msgid "" +"The delivery order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application, " +"on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To " +"Process` smart button in the :guilabel:`Delivery Orders` kanban card to " +"begin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 +msgid "" +"The delivery order associated with the :abbr:`SO (Sales Order)` can also be " +"quickly accessed by clicking on the :guilabel:`Delivery` smart button again," +" and choosing the delivery order on the :guilabel:`Transfers` page (which " +"should now be marked as :guilabel:`Ready`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "The delivery order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 +msgid "" +"Click on the delivery order associated with the :abbr:`SO (Sales Order)`, " +"then click on :guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and " +"moves to the :guilabel:`Partners/Customers` location. Then, the status of " +"the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 +msgid "Process receipts in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:7 +msgid "" +"Some companies require a quality control process before receiving goods from" +" suppliers. To accomplish this, Odoo has a three-step process for receiving " +"goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:10 +msgid "" +"In the three-step receipt process, products are received in an input area, " +"then transferred to a quality area for inspection. Products that pass the " +"quality inspection are then transferred into stock. The products are not " +"available for further processing until they are transferred out of the " +"quality area and into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:18 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" `, so the settings need to be changed" +" in order to utilize three-step receipts. First, make sure the *Multi-Step " +"Routes* option is enabled in :menuselection:`Inventory --> Configuration -->" +" Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes`" +" will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 +msgid "" +"Next, the warehouse needs to be configured for three-step receipts. To do " +"that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`," +" and select the desired warehouse to be edited. Doing so reveals the detail " +"form for that specific warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 +msgid "" +"On that :guilabel:`Warehouse` detail form page, select :guilabel:`Receive " +"goods in input, then quality and then stock (3 steps)` for " +":guilabel:`Incoming Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "Set incoming shipment option to receive in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 +msgid "" +"Activating three-step receipts and deliveries creates two new internal " +"locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). " +"To rename these locations, go to :menuselection:`Inventory app --> " +"Configuration --> Locations`, then click on the desired location to change " +"(or update) the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 +msgid "Receive in three steps (input + quality + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 +msgid "" +"To create a new :abbr:`RfQ (Request for Quotation)`, navigate to " +":menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ " +"(Request for Quotation)` form page. On this page, select a " +":guilabel:`Vendor`, add a storable :guilabel:`Product`, and click " +":guilabel:`Confirm Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top right, and the " +"receipt will be associated with the purchase order. Clicking on the " +":guilabel:`Receipt` smart button will show the receipt order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 +msgid "Process a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 +msgid "" +"One receipt and two internal transfers (one transfer to quality, and a " +"subsequent transfer to stock) will be created once the purchase order is " +"confirmed. To view these transfers, go to :menuselection:`Inventory --> " +"Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"The status of the three receipt transfers will show which operation is ready and which ones\n" +"are waiting another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 +msgid "" +"The status of the receipt transferring the product to the input location " +"will be :guilabel:`Ready`, since the receipt must be processed before any " +"other operation can occur. The status of the two internal transfers will be " +":guilabel:`Waiting Another Operation`, since the transfers cannot be " +"processed until the linked step before each transfer is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 +msgid "" +"The status of the first internal transfer to *quality* will only change to " +":guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The " +"status for the second internal transfer to *stock* will be marked " +":guilabel:`Ready` only after the transfer to quality has been marked " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 +msgid "" +"The receipt can also be found in the :menuselection:`Inventory` application." +" In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` " +"smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "One Receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 +msgid "" +"Click on the receipt associated with the purchase order, then click " +":guilabel:`Validate` to complete the receipt and move the product to the " +":guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, and the product will be transferred to the\n" +"WH/Quality location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 +msgid "Process a transfer to Quality Control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product to :guilabel:`Quality Control`. In the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard, click the " +":guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` " +"kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the transfer and move the product to " +"the :guilabel:`Quality Control` location. Once the transfer is validated, " +"the product is ready for the quality inspection, but is not available for " +"manufacturing or delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Validate the internal transfer to move the item to the Quality Control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 +msgid "Process a transfer to stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 +msgid "" +"Once the product is in the :guilabel:`Quality Control` location, the final " +"internal transfer is ready to move the product to :guilabel:`Stock`. In the " +":guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process`" +" smart button in the :guilabel:`Internal Transfers` Kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 +msgid "" +"Click on the final :guilabel:`Transfer` associated with the purchase order, " +"then click :guilabel:`Validate` to complete the transfer and move the " +"product to stock. Once the transfer is validated, the product enters the " +"stock and is available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 +msgid "Incoming shipments and delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 +msgid "" +"There are several ways to handle how a warehouse receives products " +"(receipts) and ships products (deliveries). Depending on several factors, " +"such as the type of products stocked and sold, warehouse size, and the " +"amount of daily confirmed receipts and delivery orders, the way products are" +" handled when coming in and out of the warehouse can vary a lot. Different " +"settings can be configured for receipts and deliveries; they do not have to " +"be configured to have the same number of steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 +msgid "" +"`Using Routes (eLearning Tutorial) `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:13 +msgid "" +"`Push & Pull Rules (eLearning Tutorial) " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 +msgid "Choosing the right inventory flow to handle receipts and deliveries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:19 +msgid "" +"By default, Odoo handles shipping and receiving in three different ways: in " +"one, two, or three steps. The simplest configuration is one step, which is " +"the default. Each additional step required for a warehouse for either the " +"receiving or shipping process will add an additional layer of operations to " +"perform before a product is either received or shipped. These configurations" +" depend entirely on the requirements for the products stored, such as " +"performing quality checks on received products, or using special packaging " +"on shipped products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:27 +msgid "One-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 +msgid "" +"The receiving and shipping rules for a one-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 +msgid "" +"**Receipt**: Receive products directly into stock. No intermediate steps " +"between receipt and stock occur, such as a transfer to a quality control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:33 +msgid "" +"**Shipping**: Ship products directly from stock. No intermediate steps " +"between stock and shipping occur, such as a transfer to a packing location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:35 +msgid "" +"Can only be used if not using :abbr:`FIFO (First In, First Out)`, " +":abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First " +"Out)` removal strategies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:37 +msgid "Receipts and/or deliveries are handled quickly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:38 +msgid "" +"Recommended for small warehouses with low stock levels, and for non-" +"perishable items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 +msgid "Items are received or shipped directly into/from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:42 +msgid "" +":ref:`Process receipts and deliveries in one step " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 +msgid "Two-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 +msgid "" +"The receiving and shipping rules for a two-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 +msgid "" +"**Input + stock**: Bring products to an input location *before* moving into " +"stock. Products can be organized by different internal storage locations, " +"such as various shelves, freezers, and locked areas, before being stocked in" +" the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:52 +msgid "" +"**Pick + ship**: Bring products to an output location before shipping. " +"Packages can be organized by different carriers or shipping docks before " +"being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 +msgid "" +"Minimum requirement to use lot numbers or serial numbers to track products " +"with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`" +" or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 +msgid "" +"Recommended for larger warehouses with high stock levels, or when stocking " +"large items (such as mattresses, large furniture, heavy machinery, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 +msgid "" +"Products received will not be available for manufacturing, shipping, etc., " +"until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 +msgid "" +":ref:`Process receipts and deliveries in two steps " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 +msgid "Three-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:68 +msgid "" +"The receiving and shipping rules for a three-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:70 +msgid "" +"**Input + quality + stock**: Receive products at the input location, " +"transfer them to a quality control area, and move the ones that pass " +"inspection into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:72 +msgid "" +"**Pick + pack + ship**: Pick products according to their removal strategy, " +"pack them in a dedicated packing area, and bring them to an output location " +"for shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 +msgid "" +"Can be used when tracking products by lot or serial numbers when using a " +":abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or " +":abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:77 +msgid "Recommended for very large warehouses with very high stock levels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 +msgid "" +"Required for any warehouse needing to perform quality control inspections " +"before receiving items into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 +msgid "" +":ref:`Process receipts in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:85 +msgid "" +":ref:`Process deliveries in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 +msgid "Setup and configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 +msgid "Delivery methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:5 +msgid "" +"When activated in Odoo, the *Delivery Methods* setting adds the option of " +"calculating the cost of shipping on sales orders and e-commerce shopping " +"carts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:8 +msgid "" +"When integrated with a :ref:`third-party carrier " +"`, shipping prices are calculated based on " +"the carrier's pricing and packaging information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:12 +msgid "" +":ref:`Third-party shipping carrier setup `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:13 +msgid "" +"`Odoo Tutorials: Delivery Prices " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:19 +msgid "" +"To calculate shipping on sales orders and e-commerce, the *Delivery Costs* " +"module must be installed. To do so, navigate to the :menuselection:`Apps` " +"application from the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:22 +msgid "" +"Then, remove the :guilabel:`Apps` filter, and type in `Delivery Costs` in " +"the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` " +"module, click :guilabel:`Activate` to install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "Install the *Delivery Costs* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 +msgid "Add shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 +msgid "" +"To configure delivery methods, go to :menuselection:`Inventory app --> " +"Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:36 +msgid "" +"If the :guilabel:`Shipping Methods` option is not available from the " +":guilabel:`Configuration` drop-down menu, verify whether the feature is " +"enabled by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:39 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:40 +msgid "" +"Scroll to the :guilabel:`Shipping` section and enable the " +":guilabel:`Delivery Methods` feature by checking the corresponding checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "" +"Enable the *Delivery Methods* feature by checking the box in Configuration >" +" Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:47 +msgid "" +"On the :guilabel:`Shipping Methods` page, add a method by clicking " +":guilabel:`New`. Doing so opens a form to provide details about the shipping" +" provider, including:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:50 +msgid "" +":guilabel:`Shipping Method` (*Required field*): the name of the delivery " +"method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:52 +msgid "" +":guilabel:`Provider` (*Required field*): choose the delivery service, like " +"Fedex, if using a :ref:`third-party carrier " +"`. Ensure the integration with the shipping " +"carrier is properly installed and select the provider from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:56 +msgid "" +"For more details on configuring custom shipping methods, such as :ref:`fixed" +" price `, :ref:`based on rules " +"`, or :ref:`pickup in store " +"` options, refer to their respective sections " +"below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 +msgid "" +":guilabel:`Website`: configure shipping methods for an e-commerce page. " +"Select the applicable website from the drop-down menu, or leave it blank to " +"apply the method to all web pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 +msgid "" +":guilabel:`Company`: if the shipping method should apply to a specific " +"company, select it from the drop-down menu. Leave the field blank to apply " +"the method to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:63 +msgid "" +":guilabel:`Delivery Product` (*Required field*): the product listed on the " +":ref:`sales order line ` as the delivery " +"charge." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:65 +msgid "" +":guilabel:`Free if order amount is above`: checking this box enables free " +"shipping if the customer spends above the specified amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 +msgid "" +"For examples on how to configure specific shipping methods, refer to the " +"sections below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:73 +msgid "Fixed price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:75 +msgid "" +"To configure a shipping price that is the same for all orders, go to " +":menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then," +" click :guilabel:`New`, and on the shipping method form, set the " +":guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this " +"option makes the :guilabel:`Fixed Price` field become available, which is " +"where the fixed rate shipping amount is defined." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:81 +msgid "" +"To enable free shipping if the amount of the order exceeds a specified " +"amount, check the box :guilabel:`Free if order amount is above` and fill in " +"the amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:85 +msgid "" +"To set up `$20` flat-rate shipping that becomes free if the customer spends " +"over `$100`, fill in the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 +msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:89 +msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:90 +msgid ":guilabel:`Fixed Price`: `$20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 +msgid ":guilabel:`Free if order amount is above`: `$100.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 +msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Example of filling out a shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:101 +msgid "Based on rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:103 +msgid "" +"To calculate the price of shipping based on pricing rules, set the " +":guilabel:`Provider` field to the :guilabel:`Based on Rules` option. " +"Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional " +"margin` to include additional shipping costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:108 +msgid "Create pricing rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:110 +msgid "" +"Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. " +"Doing so opens the :guilabel:`Create Pricing Rules` window, where the " +":guilabel:`Condition` related to the product weight, volume, price, or " +"quantity is compared to a defined amount to calculate the " +":guilabel:`Delivery Cost`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:115 +msgid "" +"Once finished, click either :guilabel:`Save & New` to add another rule, or " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 +msgid "" +"To charge customers $20 in shipping for orders with five or fewer products, " +"set the :guilabel:`Condition` to `Quantity <= 5.00`, and the " +":guilabel:`Delivery Cost` to `$20`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "" +"Display window to add a pricing rule. Set a condition and delivery cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:125 +msgid "" +"To restrict shipping to specific destinations on the eCommerce website, in " +"the shipping method form, navigate to the :guilabel:`Destination " +"Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, " +"and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations " +"apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:130 +msgid "Calculate delivery cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:132 +msgid "" +"Shipping cost is the :guilabel:`Delivery cost` specified in the rule that " +"satisfies the :guilabel:`Condition`, plus any extra charges from the " +":guilabel:`Margin on rate` and :guilabel:`Additional margin`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:136 +msgid "" +"Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" +"\n" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:140 +msgid "With the two following rules set up:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:142 +msgid "If the order contains five or fewer products, shipping is $20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 +msgid "If the order contains more than five products, shipping is $50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 +msgid "" +":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is " +"`$9.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "" +"Show example of \"Based on rules\" shipping method with margins configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:151 +msgid "" +"When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + " +"9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * " +"50) + 9)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:157 +msgid "Pickup in store" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:159 +msgid "" +"To configure in-store pickup, select :guilabel:`Pickup in store` in the " +":guilabel:`Provider` field and specify the pickup location in " +":guilabel:`Warehouse`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 +msgid "" +"To invoice the customer for the shipping cost to the pickup location, choose" +" the :guilabel:`Get Rate and Create Shipment` option in the " +":guilabel:`Integration Level` field. Then, pick either the " +":guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the " +":guilabel:`Invoicing Policy` field to decide whether the added shipping " +"charge on the sales order is the precise cost from the shipping carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:169 +msgid ":ref:`Invoice cost of shipping `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:174 +msgid "Add shipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:176 +msgid "" +"Shipping methods can be added to sales orders in the form of delivery " +"products, which appear as individual line items. First, navigate to the " +"desired sales order by going to :menuselection:`Sales app --> Orders --> " +"Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:180 +msgid "" +"On the sales order, click the :guilabel:`Add shipping` button, which opens " +"the :guilabel:`Add a shipping method` pop-up window. Then, choose a " +":guilabel:`Shipping Method` from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 +msgid "" +"The :guilabel:`Total Order Weight` is pre-filled based on product weights " +"(that are defined in the :guilabel:`Inventory` tab for each product form). " +"Edit the field to specify the exact weight, and then click :guilabel:`Add` " +"to add the shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:188 +msgid "" +"The amount defined in :guilabel:`Total Order Weight` overwrites the total " +"product weights defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 +msgid "" +"The shipping cost is added to the *sales order line* as the " +":guilabel:`Delivery Product` detailed on the shipping method form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:195 +msgid "" +"`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is " +"added to sales order `S00088`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Show delivery order on the sales order line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:203 +msgid "Delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:205 +msgid "" +"The shipping method added to the sales order is linked to the shipping " +"carrier details on the delivery order. To add or change the delivery method " +"on the delivery itself, go to the :guilabel:`Additional Info` tab and modify" +" the :guilabel:`Carrier` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "Shipping carrier information on the delivery form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:9 +msgid "A DHL Password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:11 +msgid "A DHL Account Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:15 +msgid "" +"Getting SiteID and password for countries other than United States (UK and " +"Rest of the world)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:17 +msgid "" +"You should contact DHL account manager and request integration for XML " +"Express API. The presales should provide you live credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:22 +msgid "" +"You need to write to xmlrequests@dhl.com along with your full Account " +"details like account number, region, address, etc. to get API Access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 +msgid "Set up Sendcloud shipping services in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 +msgid "" +"Sendcloud is a shipping service aggregator that facilitates the integration " +"of European shipping carriers with Odoo. Once integrated, users can select " +"shipping carriers on inventory operations in their Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:10 +msgid "" +"`Sendcloud integration documentation `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:14 +msgid "Setup in Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:17 +msgid "Create an account and activate carriers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:19 +msgid "" +"To get started, go to `Sendcloud's platform `_ to" +" configure the account and generate the connector credentials. Log in with " +"the Sendcloud account, or create a new one if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:24 +msgid "" +"For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Added " +"Tax Identification)` number or :abbr:`EORI (Economic Operators' Registration" +" and Identification)` number. After completing the account setup, activate " +"(or deactivate) the shipping carriers that will be used in the Odoo " +"database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:30 +msgid "" +"Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank" +" account is linked, since Sendcloud won't ship for free. To use shipping " +"rules or individual custom carrier contacts, a paid plan of Sendcloud is " +"required." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 +msgid "Warehouse configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 +msgid "" +"Once logged into the Sendcloud account, navigate to :menuselection:`Settings" +" --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse" +" address`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Adding addresses in the Sendcloud settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:44 +msgid "" +"To allow Sendcloud to process returns as well, a :guilabel:`Return Address` " +"is required. Under the :guilabel:`Miscellaneous section`, there is a field " +"called :guilabel:`Address Name (optional)`. The Odoo warehouse name should " +"be entered here, and the characters should be exactly the same." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**SendClould configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Miscellaneous`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address Name (optional)`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Brand`: `Default`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**Odoo warehouse configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Warehouse`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Short Name`: `WH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Company`: `My company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address`: `My Company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:61 +msgid "" +"Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo" +" configuration and the Sendcloud configuration, are the exact same." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:65 +msgid "Generate Sendcloud credentials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 +msgid "" +"In the Sendcloud account, navigate to :menuselection:`Settings --> " +"Integrations` in the menu on the right. Next, search for :guilabel:`Odoo " +"Native`. Then, click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:70 +msgid "" +"After clicking on :guilabel:`Connect`, the page redirects to the " +":guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and " +"Secret Keys` are produced. The next step is to name the " +":guilabel:`Integration`. The naming convention is as follows: `Odoo " +"CompanyName`, with the user's company name replacing `CompanyName` (e.g. " +"`Odoo StealthyWood`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:75 +msgid "" +"Then, check the box next to :guilabel:`Service Points` and select the " +"shipping services for this integration. After saving, the :guilabel:`Public " +"and Secret Keys` are generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Configuring the Sendcloud integration and receiving the credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:86 +msgid "Install the Sendcloud shipping module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:88 +msgid "" +"After the Sendcloud account is set up and configured, it's time to configure" +" the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, " +"search for the :guilabel:`Sendcloud Shipping` integration, and install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Sendcloud Shipping module in the Odoo Apps module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 +msgid "Sendcloud shipping connector configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 +msgid "" +"Once installed, activate the :guilabel:`Sendcloud Shipping` module in " +":menuselection:`Inventory --> Configuration --> Settings`. The " +":guilabel:`Sendcloud Connector` setting is found under the " +":guilabel:`Shipping Connectors` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:103 +msgid "" +"After activating the :guilabel:`Sendcloud Connector`, click on the " +":guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once" +" on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:108 +msgid "" +":guilabel:`Shipping Methods` can also be accessed by going to " +":menuselection:`Inventory --> Configuration --> Delivery --> Shipping " +"Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:111 +msgid "" +"Fill out the following fields in the :guilabel:`New Shipping Method` form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:113 +msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:114 +msgid "" +":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:115 +msgid "" +":guilabel:`Delivery Product`: set the product that was configured for this " +"shipping method or create a new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:117 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab, enter the " +":guilabel:`Sendcloud Public Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:118 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab, enter the " +":guilabel:`Sendcloud Secret Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:119 +msgid "" +"Manually :guilabel:`Save` the form by clicking the cloud icon next to the " +":guilabel:`Shipping Methods / New` breadcrumbs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:122 +msgid "" +"After configuring and saving the form, follow these steps to load the " +"shipping products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New " +"Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping " +"products` link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 +msgid "" +"Select the shipping products the company would like to use for deliveries " +"and returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 +msgid "Click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 +msgid "Sample Sendcloud shipping products configured in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`DELIVERY`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Shipping Product`: `DPD Home 0-31.5kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Maximum Weight`: `31.50`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:138 +msgid "" +":guilabel:`Countries`: `Austria` `Belgium` `Bosnia` `Herzegovina` `Bulgaria`" +" `Croatia` `Czech` `Republic` `Denmark` `Estonia` `Finland` `France` " +"`Germany` `Greece` `Hungary` `Iceland` `Ireland` `Italy` `Latvia` " +"`Liechtenstein` `Lithuania` `Luxembourg` `Monaco` `Netherlands` `Norway` " +"`Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` " +"`Sweden` `Switzerland`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`RETURN`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Shipping Product`: `DPD Return 0-20kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Maximum Weight`: `20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Countries`: `Belgium` `Netherlands`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Example of shipping products configured in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:156 +msgid "" +"Sendcloud does not provide test keys when a company tests the sending of a " +"package in Odoo. This means if a package is created, the configured " +"Sendcloud account will be charged, unless the associated package is canceled" +" within 24 hours of creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:160 +msgid "" +"Odoo has a built-in layer of protection against unwanted charges when using " +"test environments. Within a test environment, if a shipping method is used " +"to create labels, then those labels are immediately canceled after the " +"creation — this occurs automatically. The test and production environment " +"settings can be toggled back and forth from the :guilabel:`Smart Buttons`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:166 +msgid "Generate a label with Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:168 +msgid "" +"When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud " +"shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label " +"documents are automatically generated in the chatter, which include the " +"following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:172 +msgid ":guilabel:`Shipping label(s)` depending on the number of packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 +msgid "" +":guilabel:`Return label(s)` if the Sendcloud connector is configured for " +"returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:174 +msgid "" +":guilabel:`Customs document(s)` should the destination country require them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:176 +msgid "Additionally, the tracking number is now available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:179 +msgid "" +"When return labels are created, Sendcloud will automatically charge the " +"configured Sendcloud account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 +msgid "FAQ" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 +msgid "Shipment is too heavy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:188 +msgid "" +"If the shipment is too heavy for the Sendcloud service that is configured, " +"then the weight is split to simulate multiple packages. Products will need " +"to be put in different :guilabel:`Packages` to :guilabel:`Validate` the " +"transfer and generate labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:192 +msgid "" +":guilabel:`Rules` can also be set up in Sendcloud to use other shipping " +"methods when the weight is too heavy. However, note that these rules will " +"not apply to the shipping price calculation on the calculation on the sales " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 +msgid "When using a personal carrier contract" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:199 +msgid "" +"When using a personal carrier contract in Sendcloud, if the the price is not" +" accurately reflected when creating a quotation in Odoo, then the pricing " +"information needs to be updated in Sendcloud." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:203 +msgid "Measuring volumetric weight" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:205 +msgid "" +"Many carriers have several measures for weight. There is the actual weight " +"of the products in the parcel, and there is the *volumetric weight* " +"(:dfn:`Volumetric weight is the volume that a package occupies when in " +"transit. In other words it is the physical size of a package`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:210 +msgid "" +"Check to see if selected carrier(s) already have defined formulas to compute" +" the volumetric weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:214 +msgid "" +"`Sendcloud: How to calculate & automate parcel volumetric weight " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:219 +msgid "Unable to calculate shipping rate" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 +msgid "" +"First, verify that product being shipped has a weight that is supported by " +"the selected shipping method. If this is set, then verify that the " +"destination country (from the customer address) is supported by the carrier." +" The country of origin (warehouse address) should also be supported by the " +"carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo can be linked with the transportation company tracking system. It will " +"allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 +msgid "" +"In the inventory module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:31 +msgid "" +"If you want to integrate delivery methods in your e-commerce, you'll have to" +" install the **eCommerce Delivery** module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:40 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created. Most of the time, there will be **2** delivery methods for the same" +" provider: one for **international** shipping and the other for **domestic**" +" shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:45 +msgid "" +"You can create other methods with the same provider with other " +"configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:48 +msgid "" +"You can change the **Name** of the delivery method. This is the name that " +"will appear on your ecommerce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:51 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 +msgid "" +"In the pricing tab, the name of the provider chosen under the **Price " +"computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:59 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:61 +msgid "" +"The first one is linked to **your account** (developer key, password,...). " +"For more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:69 +msgid "" +"Finally you can limit the delivery method to a few destinations. You can " +"limit it to some countries, states or even zip codes. This feature limits " +"the list of countries on your e-commerce. It is useful for the domestic " +"providers. For example, USPS US only delivers from the United States to the " +"United States." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:97 +msgid "" +"Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products" +" you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:104 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to " +"make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:109 +msgid "Sale process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:112 +msgid "Sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:117 +msgid "" +"You can now choose the carrier on your sale order. Click on **Delivery " +"method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:120 +msgid "" +"The price is computed when you save the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 +msgid "" +"If you want to invoice the price of the delivery charge on the sale order, " +"click on **Set price**, it will add a line with the name of the delivery " +"method as a product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:127 +msgid "" +"Otherwise, the real price (computed when the delivery is validated) will " +"automatically be added to the invoice. For more information, please read the" +" document :doc:`../advanced_operations_shipping/invoicing`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 +msgid "Delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:134 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it. You can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:143 +msgid "" +"The weight is computed based on the products weights. The shipping cost will" +" be computed once the transfer is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 +msgid "" +"Click on **Validate** to receive the tracking number. The **Carrier Tracking" +" ref** field will automatically be filled. Click on the **Tracking** button " +"to check your delivery on the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:160 +msgid ":doc:`../advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:161 +msgid ":doc:`../advanced_operations_shipping/labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:13 +msgid "" +"An Access Key is a 16 character alphanumeric code that allows access to the " +"UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:19 +msgid "" +"Note that only customers located in the US can open a UPS account online. If" +" you are located outside the US, you will need to contact UPS Customer " +"Service in order to to open an account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:23 +msgid "" +"You can read additional information about opening a UPS account on the their" +" website, on the page, `How to Open a UPS Account Online " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:27 +msgid "" +"If you don't already have a UPS account, you can create one along with your " +"online profile by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:30 +msgid "" +"1. Access the UPS.com web site at `www.ups.com `__, and" +" click the **New User** link at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:34 +msgid "" +"2. Click the **Register for MyUPS** button, and follow the prompts to " +"complete the registration process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:37 +msgid "" +"If you already have a UPS account, you can add it to your online profile as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:39 +msgid "" +"Log in to the `UPS.com website `_) using your UPS.com " +"User ID and Password." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:41 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:43 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:45 +msgid "" +"4. Click the **Add an Existing UPS Account** link in the **UPS Account " +"Details** section of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:48 +msgid "" +"5. In the **Add New Account** screen, enter the **UPS Account Number**, " +"**Account Name**, and **Postal Code** fields. The country defaults to United" +" States.q" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:52 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:55 +msgid "Get an Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:57 +msgid "" +"After you have added your UPS account number to your user profile you can " +"request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:60 +msgid "" +"Go to the `UPS Developer Kit web page " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:61 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:62 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:63 +msgid "Verify your contact information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:64 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:66 +msgid "" +"The **Access Key** will be provided to you on the web page, and an email " +"with the Access Key will be sent to the email address of the primary " +"contact." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 +msgid "Warehouses and storage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:3 +msgid "Batch picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:7 +msgid "" +"*Batch picking* enables a single picker to handle multiple orders at once, " +"reducing the time needed to navigate to the same location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:10 +msgid "" +"When picking in batches, orders are grouped and consolidated into a picking " +"list. After the picking, the batch is taken to an output location, where the" +" products are sorted into their respective delivery packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 +msgid "" +":ref:`Use Barcode app for pickings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 +msgid "" +"Since orders *must* be sorted at the output location after being picked, " +"this picking method suits businesses with a few products that are ordered " +"often. Storing high-demand items in easily accessible locations can increase" +" the number of orders that are fulfilled efficiently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:24 +msgid "" +"To activate the batch picking option, begin by going to " +":menuselection:`Inventory app --> Configuration --> Settings`. Under the " +":guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:32 +msgid "" +"Since batch picking is a method to optimize the *pick* operation in Odoo, " +"the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options " +"under the :guilabel:`Warehouse` heading must also be checked on this " +"settings page. When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "" +"Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration" +" > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:40 +msgid "" +"Lastly, enable the warehouse picking feature, by navigating to the warehouse" +" settings page, which is accessible from :menuselection:`Inventory app --> " +"Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:43 +msgid "" +"From here, select the desired warehouse from the list. Then, from the radio " +"options available for :guilabel:`Outgoing Shipments`, select either the " +":guilabel:`Send goods in output and then deliver (2 steps)` or " +":guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:131 +msgid ":ref:`Delivery in two steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:132 +msgid ":ref:`Delivery in three steps `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Set up 2-step or 3-step outgoing shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:56 +msgid "Create batch transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:58 +msgid "" +"Manually create batch transfers directly from the :menuselection:`Inventory " +"app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` " +"button to begin creating a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:61 +msgid "On the batch transfer form, fill the following fields out accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:63 +msgid "" +":guilabel:`Responsible`: employee assigned to the picking. Leave this field " +"blank if *any* worker can fulfill this picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:65 +msgid "" +":guilabel:`Operation Type`: from the drop-down menu, select the operation " +"type under which the picking is categorized." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:67 +msgid "" +":guilabel:`Scheduled Date`: specifies the date by which the " +":guilabel:`Responsible` person should complete the transfer to the output " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:70 +msgid "" +"Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to " +"open the :guilabel:`Add: Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:73 +msgid "" +"If the :guilabel:`Operation Type` field was filled, the list will filter " +"transfer records matching the selected :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:76 +msgid "Click the :guilabel:`New` button to create a new transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:78 +msgid "" +"Once the transfer records are selected, click :guilabel:`Confirm` to confirm" +" the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:81 +msgid "" +"A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`," +" for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` " +"is set to `August 11`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "View of *Batch Transfers* form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:88 +msgid "" +"Clicking the :guilabel:`Add a line` button opens the " +":guilabel:`Add:Transfers` window, displaying only pickings. This is because " +"the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:92 +msgid "" +"Click the checkbox to the left of the transfers, `WH/PICK/00001` and " +"`WH/PICK/00002`, to include them in the new transfer. Then, click the " +":guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Select multiple transfers from the *Add:Transfers* window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:101 +msgid "Add batch from transfers list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:103 +msgid "" +"Another method of creating batch transfers is available using the " +":guilabel:`Add to batch` option in a list. Navigate to the " +":menuselection:`Inventory app --> Operations` drop-down menu, and select any" +" of the :guilabel:`Transfers` to open a filtered list of transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "" +"Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" +"Manufacturings, Batch Transfers, Dropships." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:112 +msgid "" +"On the transfers list, select the checkbox to the left of the selected " +"transfers to add in a batch. Next, navigate to the :guilabel:`Actions ⚙️ " +"(gear)` button, and click :guilabel:`Add to batch` from the resulting drop-" +"down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Use *Add to batch* button, from the *Action* button's list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:151 +msgid "" +"Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the " +"employee :guilabel:`Responsible` for the picking can be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:123 +msgid "" +"Choose from the two radio options to add to :guilabel:`an existing batch " +"transfer` or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:126 +msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:160 +msgid "Conclude the process by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "Show *Add to batch* window to create a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:135 +msgid "Process batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:137 +msgid "" +"Handle batch transfers in the :menuselection:`Inventory app --> Operations " +"--> Batch Transfers` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:140 +msgid "" +"From here, select the intended transfer from the list. Then, on the batch " +"transfer form, input the :guilabel:`Done` quantities for each product, under" +" the :guilabel:`Detailed Operations` tab. Finally, select " +":guilabel:`Validate` to complete the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:145 +msgid "" +"Be certain the batch transfer is complete when the :guilabel:`Validate` " +"button is highlighted in purple. If the :guilabel:`Check Availability` " +"button is highlighted instead, that means there are items in the batch that " +"are currently *not* available in-stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:152 +msgid "" +"In a batch transfer involving products from pickings, `WH/PICK/00001` and " +"`WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the " +"product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` " +"column matches the value in the :guilabel:`Reserved` column. However, `0.00`" +" quantities have been picked for the other product, `Cable Management Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "" +"Show batch transfer of products from two pickings in the *Detailed " +"Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:161 +msgid "" +"Only in-stock products are visible in the :guilabel:`Detailed Operations` " +"tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:163 +msgid "" +"To view the complete product list, switch to the :guilabel:`Operations` tab." +" On this list, the :guilabel:`Demand` column indicates the required quantity" +" for the order. The :guilabel:`Reserved` column shows the available stock to" +" fulfill the order. Lastly, the :guilabel:`Done` column specifies the " +"products that have been picked, and are ready for the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:169 +msgid "" +"The product, `Desk Pad`, from the same batch as the :ref:`example above " +"`, is only visible in the " +":guilabel:`Operations` tab because there are no :guilabel:`Reserved` " +"quantities in-stock to fulfill the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:173 +msgid "" +"Click the :guilabel:`Check Availability` button to search the stock again " +"for available products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Show unavailable reserved quantities in the *Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:180 +msgid "Create backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:182 +msgid "" +"On the batch transfer form, if the :guilabel:`Done` quantity of the product " +"is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:185 +msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:187 +msgid "" +"Clicking the :guilabel:`Create Backorder` button automatically creates a new" +" batch transfer, containing the remaining products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:190 +msgid "" +"Click :guilabel:`No Backorder` to finish the picking *without* creating " +"another batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:192 +msgid "" +"Click :guilabel:`Discard` to cancel the validation, and return to the batch " +"transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Show the *Create Backorder* pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:201 +msgid "Process batch transfer: Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:203 +msgid "" +"Created batch transfers are also listed in the :menuselection:`Barcode` app," +" accessible by selecting the :guilabel:`Batch Transfers` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:206 +msgid "" +"By default, confirmed batch pickings appear on the :guilabel:`Batch " +"Transfers` page. On that page, click on the desired batch transfer to open " +"the detailed list of products for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Show list of to-do batch transfers in *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:213 +msgid "" +"For the chosen batch transfer, follow the instructions at the top of the " +"page in the black background. Begin by scanning the product's barcode to " +"record a single product for picking. To record multiple quantities, click " +"the :guilabel:`✏️ (pencil)` icon, and enter the required quantities for the " +"picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:219 +msgid "" +"Products from the same order are labeled with the same color on the left. " +"Completed pickings are highlighted in green." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:223 +msgid "" +"In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, " +"and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate " +"that the last two product pickings are complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:227 +msgid "" +"`1/2` units of the `Cabinet with Doors` has already been picked, and after " +"scanning the product barcode for the second cabinet, Odoo prompts the user " +"to `Scan a serial number` to record the unique serial number for " +":ref:`product tracking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Display products to be picked in barcode view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:235 +msgid "" +"Once all the products have been picked, click on :guilabel:`Validate` to " +"mark the batch transfer as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:3 +msgid "Closest location removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:5 +msgid "" +"For the *Closest Location* removal strategy, products are picked based on " +"the alphanumeric order of storage location titles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:8 +msgid "" +"The goal of this strategy is to save the warehouse worker from taking a long" +" journey to a farther shelf when the product is also available at a closer " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:13 +msgid ":doc:`About removal strategies `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:16 +msgid "" +"To understand *location sequence* in the closest removal strategy, consider " +"the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:19 +msgid "" +"A product is stored in the following locations: `Shelf A/Pallet`, `Shelf " +"A/Rack 1`, and `Shelf A/Rack 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 +msgid "Show a mockup of real storage location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:26 +msgid "" +"The sublocation, `Pallet`, is on the ground level. Products stored here are " +"easier to retrieve, compared to requiring a forklift to reach `Rack 1` and " +"`Rack 2`. The storage locations were strategically named in alphabetic " +"order, based on ease of access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:31 +msgid "" +"To use this removal strategy, the :guilabel:`Storage Locations` and " +":guilabel:`Multi-Step Routes` settings **must** be enabled in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:35 +msgid "" +":ref:`Set up removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:40 +msgid "Location names" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:42 +msgid "" +"To configure location names, begin by navigating to " +":menuselection:`Inventory app --> Configuration --> Locations`. Then, select" +" an existing location, or click :guilabel:`New` to create a new one, and " +"then enter the desired name in the :guilabel:`Location Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:46 +msgid "" +"Once the locations are named in alphabetical order, based on their proximity" +" to the output or packing location, set the removal strategy on the " +":ref:`parent location `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:50 +msgid "" +"To do that, in the :guilabel:`Locations` list, select the parent location of" +" the alphabetically named storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:53 +msgid "" +"Doing so opens the form for the parent location. In the :guilabel:`Removal " +"Strategy` field, select :guilabel:`Closest Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:57 +msgid "" +"In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest " +"to the packing area, where products retrieved from shelves are packed for " +"shipment. The popular product, `iPhone charger` is stored in three " +"locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:62 +msgid "" +"To use closest location, set the removal strategy on the parent location, " +"'WH/Stock'." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:30 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:67 +msgid "" +"To see how the closest location removal strategy works, consider the " +"following example, featuring the popular product, `iPhone charger`, which is" +" stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:71 +msgid "" +"Fifteen, five, and thirty units are in stock at each respective location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:74 +msgid "" +"To check the on-hand stock at each storage location, navigate to the product" +" form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:0 +msgid "Show on-hand stock at all locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:81 +msgid "" +"Create a :ref:`delivery order ` for eighteen " +"units of the `iPhone charger` by navigating to the :menuselection:`Sales " +"app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:84 +msgid "" +"After adding the products, clicking :guilabel:`Confirm` creates a delivery " +"order that reserves items stored at the closest location, using the removal " +"strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:87 +msgid "" +"For more details about *where* the units were picked, select the " +":guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so " +"opens the :guilabel:`Open: Stock move` pop-up window that displays how the " +"reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:91 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked. All fifteen of the units stored at the closest location, " +"`WH/Stock/Shelf 1`, are picked first. The remaining three units are then " +"selected from the second closest location, `WH/Stock/Shelf 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 +msgid "Display *Pick From* quantities for the order for iPhone chargers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 +msgid "Cluster picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:10 +msgid "" +"Cluster picking is an advanced order fulfillment approach derived from " +":ref:`batch picking `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:13 +msgid "" +"In this strategy, pickers load a cart with multiple packages, each " +"designated for a specific *sales order* (SO). Then, the picker travels to " +"each storage location, and places the products directly in the package of " +"the associated order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:17 +msgid "" +"This method is most efficient for medium-sized companies, with high order " +"volumes, and relatively few unique products, since the method eliminates the" +" need for sorting products into packages for customers after picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:21 +msgid "" +"However, cluster picking does have some disadvantages. For instance, urgent " +"orders cannot be prioritized, and optimized batches must be manually created" +" beforehand. As a result, the picking process can lead to bottlenecks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:28 +msgid "|SO| 1 calls for one apple and orange" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:29 +msgid "|SO| 2 calls for one apple and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:30 +msgid "|SO| 3 calls for one apple, orange, and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:32 +msgid "" +"Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:34 +msgid "" +"To pick products for three orders at once, the cart is loaded with three " +"empty packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:36 +msgid "" +"Starting at Shelf A, the picker places apples into each package. Next, the " +"picker navigates to Shelf B, and places oranges in the packages designated " +"for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and " +"loads packages for |SO| 2 and |SO| 3 with a banana, each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:40 +msgid "" +"With the packages for all three |SOS| packed, the picker pushes the cart to " +"the output location, where the packages are sealed and prepared for " +"shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Show example of fulfilling sales orders 2 and 3 at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:50 +msgid "" +"To enable cluster picking, begin by navigating to :menuselection:`Inventory " +"app --> Configuration --> Settings`. Under the :guilabel:`Operations` " +"heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` " +"options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "Activate *Packages* and *Batch Transfers* features in the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:58 +msgid "" +"Since batch picking is used to optimize the *pick* operation in Odoo, the " +":guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, " +"under the :guilabel:`Warehouse` heading, must also be checked on this " +"settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:62 +msgid "" +"*Storage locations* allow products to be stored in specific locations they " +"can be picked from, while *multi-step routes* enable the picking operation " +"itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:65 +msgid "When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:74 +msgid "Packages setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:76 +msgid "" +"After the :guilabel:`Packages` feature is enabled, navigate to " +":menuselection:`Inventory app --> Products --> Packages`, and click the " +":guilabel:`New` button to create a new package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:79 +msgid "" +"On the new package form, the :guilabel:`Package Reference` is pre-filled " +"with the next available `PACK` number in the system. :guilabel:`Pack Date` " +"is automatically set to the creation date of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:83 +msgid "" +"For the :guilabel:`Package Use` field, the :guilabel:`Disposable Box` option" +" should be selected if the package is used for a shipping. Alternatively, " +"the :guilabel:`Reusable Box` option should be selected if the package is " +"simply used as a method of grouping products from the same |SO| together " +"before they are moved to the intended shipping box at the output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 +msgid ":ref:`Packages `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:92 +msgid "" +"A package intended for cluster picking is named `CLUSTER-PACK-3` for easy " +"identification. For this workflow, the products are directly packed using " +"their intended shipping boxes, so :guilabel:`Package Use` is set to " +":guilabel:`Disposable Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Create new package form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:101 +msgid "Create cluster batch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:103 +msgid "" +"To see how cluster picking works in Odoo, navigate to the " +":menuselection:`Sales` app, and create |SOS| that will be fulfilled together" +" in the same batch. After confirming an |SO|, the :guilabel:`Delivery` smart" +" button becomes visible. Displayed inside the icon is a number representing " +"the amount of steps in the outgoing shipment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:109 +msgid "" +"Begin by creating three |SOS| for the apples, oranges, and bananas, as shown" +" in the :ref:`example above `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:112 +msgid "" +"After confirming the |SO|, the :guilabel:`Delivery` smart button displays " +"the number `2`, indicating there are two operations to complete: `Pick` and " +"`Delivery`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example sales order for an apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:119 +msgid "" +"With the |SOS| created, orders now must be grouped into batches. To do so, " +"navigate to the *Inventory* dashboard and select the operation type card, " +":guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first " +"operation in the delivery flow)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:123 +msgid "" +"Doing so displays a filtered list of outgoing operations with the " +":guilabel:`Ready` status, indicating that all the products in the |SO| are " +"in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:127 +msgid "" +"Cluster pick batches can be created for outgoing shipments in one, two, or " +"three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:130 +msgid ":ref:`Delivery in one step `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:134 +msgid "" +"Click the checkbox to the left of the corresponding outgoing operation to " +"add them to the batch. With the desired pickings selected, click the " +":guilabel:`⚙️ Actions (gear)` button, and select the :guilabel:`Add to " +"batch` option from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:139 +msgid "" +"To create a cluster batch, as shown in the :ref:`example above " +"`, in a warehouse configured with " +"two-step outgoing shipments, the following pick operations are selected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:143 +msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:144 +msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:145 +msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:154 +msgid "" +"Choose from the two options in the :guilabel:`Add to` field to either: add " +"to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch " +"transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:157 +msgid "" +"To create draft batch pickings to be confirmed at a later date, select the " +":guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:167 +msgid "Process batches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:169 +msgid "" +"To process batches, navigate to :menuselection:`Inventory app --> Operations" +" --> Batch Transfers`. Click on a batch to select it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:172 +msgid "" +"In the :guilabel:`Detailed Operations` tab, products that are to be picked " +"are grouped by location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:174 +msgid "" +"Under the :guilabel:`Source Package` or :guilabel:`Destination Package` " +"field, enter the package used for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:178 +msgid "" +"Use the :guilabel:`Source Package` field when the picking package is " +"configured as *reusable* on the :ref:`package form `. This means the products are temporarily placed in a container " +"during picking, before getting transferred to their final shipping box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:182 +msgid "" +"Alternatively, use the :guilabel:`Destination Package` field when the " +"product is directly placed in its *disposable* shipping box during picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:186 +msgid "" +"Process the cluster batch for the three orders of apples, oranges, and " +"bananas :ref:`example ` by assigning" +" each picking to a dedicated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:189 +msgid "" +"At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in" +" all three pickings to one of the three disposable packages, `CLUSTER-" +"PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:192 +msgid "" +"Record this in Odoo using the :guilabel:`Destination Package` field in the " +":guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of processing cluster pickings in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:200 +msgid "In Barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:202 +msgid "" +"To process cluster pickings directly from the *Barcode* app, select the " +":guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, " +"select the desired batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:205 +msgid "" +"On the batch transfer screen, the products in the picking are grouped by " +"location, and each line is color-coded to associate products in the same " +"picking together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:208 +msgid "" +"Then, follow the prompt to :guilabel:`Scan the source location` barcode for " +"the storage location of the first product. Then, scan the barcode for the " +"product and package to process the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:211 +msgid "" +"Repeat this for all products, and click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:214 +msgid "" +"To find the package barcode, navigate to :menuselection:`Inventory app --> " +"Products --> Packages`, select the desired package, click the :guilabel:`⚙️ " +"(gear)` icon at the top of the package form, and select the " +":guilabel:`Print` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:218 +msgid "" +"Next, select one of the three print options to generate the package barcode " +"from the :guilabel:`Package Reference` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Display where the package barcode can be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:226 +msgid "" +"Begin processing the cluster picking by going to the first storage location," +" `Shelf A`, and scanning the :ref:`location barcode " +"`. Doing so highlights all the pickings that need " +"products from this particular location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:230 +msgid "" +"Scan the barcode for the apple, which highlights the picking (labeled in " +"red) for the product `Apple`, for the picking, `WH/PICK/00007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:233 +msgid "" +"Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in " +"the designated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of cluster batch from the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:240 +msgid "" +"After creating a batch transfer and assigning a package to a picking, Odoo " +"suggests the specified package by displaying the name *in italics* under the" +" product name, ensuring pickers place products into the correct boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:3 +msgid "Organize a cross-dock in a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:5 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:13 +msgid "" +"For more information on how to organize your warehouse, read our blog: `What" +" is cross-docking and is it for me? `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:20 +msgid "" +"In the *Inventory* app, open :menuselection:`Configuration --> Settings` and" +" activate the *Multi-Step Routes*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:27 +msgid "Doing so will also enable the *Storage Locations* feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:29 +msgid "" +"Now, both *Incoming* and *Outgoing* shipments should be configured to work " +"with 2 steps. To adapt the configuration, go to :menuselection:`Inventory " +"--> Configuration --> Warehouses` and edit your warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:36 +msgid "" +"This modification will lead to the creation of a *Cross-Docking* route that " +"can be found in :menuselection:`Inventory --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:43 +msgid "Configure products with Cross-Dock Route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:45 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:55 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:68 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:77 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:86 +msgid "" +"The delivery order is now ready to be processed and can be validated too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:5 +msgid "" +"For most companies, warehouse stock only needs to be counted once a year. " +"This is why, by default, after making an *inventory adjustment* in Odoo, the" +" scheduled date for the next inventory count is set for the 31st of December" +" of the current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:9 +msgid "" +"However, for some businesses, it's crucial to have an accurate inventory " +"count at all times. These companies use *cycle counts* to keep critical " +"stock levels accurate. Cycle counting is a method by which companies count " +"their inventory more often in certain *locations*, to ensure that their " +"physical inventory counts match their inventory records." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:15 +msgid "Activate storage locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:17 +msgid "" +"In Odoo, cycle counts are location-based. Therefore, the *storage locations*" +" feature needs to be enabled before performing a cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:20 +msgid "" +"To enable this feature, navigate to :menuselection:`Inventory app --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` " +"section. Then, click the checkbox next to :guilabel:`Storage Locations`. " +"Click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Enabled storage locations setting in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:29 +msgid "Change inventory count frequency by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:31 +msgid "" +"Now that the storage locations setting is enabled, the inventory count " +"frequency can be changed for specific locations created in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:34 +msgid "" +"To view and edit locations, navigate to :menuselection:`Inventory app --> " +"Configuration --> Locations`. This reveals a :guilabel:`Locations` page " +"containing every location currently created and listed in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:38 +msgid "" +"From this page, click into a location to reveal the settings and " +"configuration page for that location. Click :guilabel:`Edit` to edit the " +"location settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:41 +msgid "" +"Under the :guilabel:`Cyclic Inventory` section, locate the " +":guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if" +" this location has not been edited previously). In this field, change the " +"value to whichever number of days is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Location frequency setting on location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:50 +msgid "" +"A location that needs an inventory count every 30 days should have the " +":guilabel:`Inventory Frequency (Days)` value set to `30`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:53 +msgid "" +"Once the frequency has been changed to the desired number of days, click " +":guilabel:`Save` to save changes. Now, once an inventory adjustment is " +"applied to this location, the next scheduled count date is automatically " +"set, based on the value entered into the :guilabel:`Inventory Frequency " +"(Days)` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 +msgid "" +"To perform a cycle count for a specific location in the warehouse, navigate " +"to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. " +"This reveals an :guilabel:`Inventory Adjustments` page containing all " +"products currently in stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 +msgid "" +"From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at" +" the top of the page, under the :guilabel:`Search...` bar), can be used to " +"select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 +msgid "" +"To select a specific location and view all products within that location, " +"click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to " +"reveal a new drop-down menu to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 +msgid "" +"Click :guilabel:`Location` from the drop-down menu, then click " +":guilabel:`Apply`. The page now displays condensed drop-down menus of each " +"location in the warehouse that has products in stock, and a cycle count can " +"be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 +msgid "" +"In large warehouses with multiple locations and a high volume of products, " +"it might be easier to search for the specific location desired. To do this, " +"from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. " +"Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right." +" Click this menu to reveal three drop-downs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 +msgid "" +"For the first field, click and select :guilabel:`Location` from the drop-" +"down. For the second field, leave the :guilabel:`contains` value as is. For " +"the third field, type in the name of the location that is being searched " +"for. Click :guilabel:`Apply` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Applied filters and group by on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 +msgid "" +"While cycle counts are typically performed per location, the scheduled date " +"for full inventory counts of everything in-stock in the warehouse can also " +"be manually changed to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 +msgid "" +"To modify the default scheduled date, go to :menuselection:`Inventory app " +"--> Configuration --> Settings`. Then, in the :guilabel:`Operations` " +"section, locate the :guilabel:`Annual Inventory Day and Month` setting " +"field, which includes a drop-down that is set to `31` :guilabel:`December` " +"by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 +msgid "" +"To change the day, click the `31`, and change it to a day within the range " +"`1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 +msgid "" +"Then, to change the month, click :guilabel:`December` to reveal the drop-" +"down menu, and select the desired month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 +msgid "" +"Once all changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 +msgid ":doc:`../inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:3 +msgid "FEFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:5 +msgid "" +"The *First Expired, First Out* (FEFO) removal strategy targets products for " +"removal based on their assigned removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:9 +msgid ":doc:`Other removal strategies `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:14 +msgid "Removal date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:16 +msgid "" +"Products **must** be removed from inventory before their *removal date*, " +"which is set as a certain number of days before the product's *expiration " +"date*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:19 +msgid "" +"The user sets this number of days by navigating to the product form's " +":guilabel:`Inventory` tab. Under the :guilabel:`Traceability` section, " +"ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` " +"or :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:23 +msgid "" +"Next, select the :guilabel:`Expiration Date` option, which makes the " +":guilabel:`Removal Date` field (and other date fields) appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:27 +msgid "" +"The :guilabel:`Lots and Serial Numbers` and :guilabel:`Expiration Dates` " +"features **must** be enabled in :menuselection:`Inventory app --> " +"Configuration --> Settings` to track expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:31 +msgid "" +"The expiration date of a product is determined by adding the date the " +"product was received to the number of days specified in the " +":guilabel:`Expiration Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:34 +msgid "" +"The removal date takes this expiration date, and subtracts the number of " +"days specified in the :guilabel:`Removal Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:38 +msgid "" +":doc:`Expiration dates " +"<../../product_management/product_tracking/expiration_dates>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:41 +msgid "" +"In the :guilabel:`Inventory` tab of the product, `Egg`, the following " +":guilabel:`Dates` are set by the user:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:44 +msgid ":guilabel:`Expiration Date`: `30` days after receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:45 +msgid ":guilabel:`Removal Date`: `15` days before expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "Display expiration and removal dates set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:51 +msgid "" +"A shipment of Eggs arrive at the warehouse on January 1st. So, the " +"expiration date of the Eggs is **January 31st** (Jan 1st + 30). By " +"extension, the removal date is **January 16th** (Jan 31 - 15)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:57 +msgid "" +"To view the expiration dates of items in stock, navigate to the product " +"form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:60 +msgid "" +"Next, click the additional options icon, located on the far-right, and " +"select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal " +"Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "" +"Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" +"smart button from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:71 +msgid "" +"Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures " +"that products with the nearest removal date are picked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:74 +msgid "" +"To understand how this removal strategy works, consider the following " +"example below about the product, `Carton of eggs`, which is a box containing" +" twelve eggs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:77 +msgid "" +"The product is tracked :guilabel:`By Lots`, and the product category's " +":guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First" +" Out (FEFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:24 +msgid "" +":ref:`Set up force removal strategy `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:25 +msgid ":ref:`Enable lots tracking `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:83 +msgid "" +"`Odoo Tutorials: Perishable Products " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:35 +msgid "LOT1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:36 +msgid "LOT2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:37 +msgid "LOT3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:38 +msgid "On-hand stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:73 +msgid "5" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:75 +msgid "2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:96 +msgid "1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 +msgid "Expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:98 +msgid "April 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:99 +msgid "April 10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:100 +msgid "April 15" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:101 +msgid ":ref:`Removal date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:102 +msgid "February 26" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:103 +msgid "March 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:104 +msgid "March 9" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:106 +msgid "" +"To see the removal strategy in action, go to the :menuselection:`Sales app` " +"and create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:109 +msgid "" +"Clicking :guilabel:`Confirm` creates a delivery order for today, December " +"29th, and the lot numbers with the soonest expiration dates are reserved, " +"using the :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:113 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the Carton of egg's product line, in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:117 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:120 +msgid "" +"Since the order demanded six Cartons of eggs, using the :abbr:`FEFO (First " +"Expired, First Out)` removal strategy, all five Cartons from `LOT1`, with " +"the removal date of February 26th, are picked. The remaining Carton is " +"selected from `LOT2`, which has a removal date of March 4th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "The stock moves window that shows the lots to be removed using FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:3 +msgid "FIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:5 +msgid "" +"The *First In, First Out* (FIFO) removal strategy selects products with the " +"earliest arrival dates. This method is useful for companies selling products" +" that have short demand cycles, like clothes, for example. By using " +":abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock " +"retention of specific styles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:11 +msgid ":doc:`Other removal methods `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:14 +msgid "" +"Various quantities of the product, `T-shirt`, tracked by lot numbers, arrive" +" on August 1st and August 25th. For an order made on September 1st, the " +":abbr:`FIFO (First In, First Out)` removal strategy prioritizes lots that " +"have been in stock the longest. So, products received on August 1st are " +"selected first for picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Illustration of FIFO selecting the oldest products in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:24 +msgid "" +":ref:`Lot/serial number setup details `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:29 +msgid "Arrival date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:31 +msgid "" +"To see the product lot or serial number that arrived in inventory first, " +"navigate to :menuselection:`Inventory app --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:34 +msgid "" +"Then, select the :guilabel:`▶️ (right-pointing arrow)` icon on the left of a" +" product line, in order to reveal a list of the product's lots or serial " +"numbers that are in stock. The :guilabel:`Created On` field shows the " +"lot/serial number creation date, which is, essentially, the arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:39 +msgid "" +"Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on" +" December 29th, as displayed in the :guilabel:`Created On` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Display arrival date of a lot for an item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:49 +msgid "" +"To understand how :abbr:`FIFO (First In, First Out)` rotates products out, " +"consider the following example, focusing on three lots of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:52 +msgid "" +"The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In," +" First Out)` is set as the :guilabel:`Force Removal Strategy`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:55 +msgid "" +"The white shirts are tracked :guilabel:`By Lots` in the " +":guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:62 +msgid "" +"The following table represents the on-hand stock and lot number details of " +"white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:74 +msgid "3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:42 +msgid ":ref:`Created on `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:77 +msgid "March 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:78 +msgid "April 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:79 +msgid "May 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:81 +msgid "" +"To see the removal strategy in action, create a :ref:`delivery order " +"` for six white shirts by navigating to the " +":menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:84 +msgid "" +"After clicking :guilabel:`Confirm` on the sales order, a delivery order with" +" the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO " +"(First In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:87 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the white shirt's product line in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:91 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from. Since the order demanded six shirts, all five shirts from " +"`LOT1`, and one shirt from `LOT2`, are selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:3 +msgid "Least packages removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:5 +msgid "" +"The *Least Packages* removal strategy fulfills an order by opening the " +"fewest number of packages, which is ideal for maintaining organized stock " +"without needing to open multiple boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:10 +msgid "" +"`Odoo Tutorials: Least Packages " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:12 +msgid "" +"To understand how the removal strategy works, consider the following " +"example, featuring a warehouse that stores packages of flour in bulk " +"packages of `100 kg`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:15 +msgid "" +"To minimize moisture, and/or prevent pests from entering open packages, the " +"least packages removal strategy is used to pick from a single, opened " +"package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:21 +msgid "" +"A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some " +"orders. There are other packages of `100 kg` in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:24 +msgid "" +"When an order for `14 kg` of flour is placed, the package of `54 kg` is " +"selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:25 +msgid "" +"When an order for *more* than `54 kg` of flour is placed, an unopened `100 " +"kg` package is used to fulfill the order. While this temporarily results in " +"two open packages, these open packages are prioritized in the next picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:32 +msgid "" +"Using the least package removal strategy, the fewest number of packages is " +"used to fulfill an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:35 +msgid "" +"The :ref:`Packages feature ` " +"**must** be enabled to use this strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:38 +msgid "" +"Consider the following example, featuring the product, `Flour`. The " +"product's :guilabel:`Units of Measure` field, located on the product form, " +"is set to `kg`. The product is stored in packages of `100 kg`, with one " +"remaining package containing `54 kg`. The product category's " +":guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:44 +msgid "" +":ref:`Set removal strategy on product category " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:47 +msgid "" +"To check the product's on-hand stock, navigate to the product form, and " +"click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:0 +msgid "Show on-hand stock in each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:54 +msgid "" +"Create a :ref:`delivery order ` for eighty " +"kilograms of flour by going to the :menuselection:`Sales app` and creating a" +" new quotation. After clicking :guilabel:`Confirm`, the delivery order is " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:58 +msgid "" +"On the delivery order, the :guilabel:`Quantity` field displays the amount " +"automatically picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:61 +msgid "" +"For more details about *where* the units were picked, select the " +":guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so " +"opens the :guilabel:`Open: Stock move` pop-up window, displaying how the " +"reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:65 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked. Since the order demanded eighty kilograms, which exceeds the " +"quantity in the opened package of `54 kg`, an unopened package of `100 kg` " +"is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst-1 +msgid "Show which package was picked in the *Pick From* field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:3 +msgid "LIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:5 +msgid "" +"The *Last In, First Out* (LIFO) removal strategy picks the **newest** " +"products on-hand, based on the date they entered a warehouse's stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:8 +msgid "" +"Every time an order is placed for products using the :abbr:`LIFO (Last In, " +"First Out)` strategy, a transfer is created for the lot/serial number that " +"has most recently entered the stock (the **last** lot/serial number that " +"entered the warehouse's inventory)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:16 +msgid "" +"In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy is" +" banned, since it can potentially result in old, expired, or obsolete " +"products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:19 +msgid "" +"Consider the following example, with the product, `Cinder Block`, which is " +"tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product " +"form. The :guilabel:`Force Removal Strategy` for the cinder block's product " +"category is set to :guilabel:`Last In, First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:26 +msgid ":ref:`Check arrival date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:28 +msgid "" +"The following table represents the cinder blocks in stock, and their various" +" lot number details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:43 +msgid "June 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:44 +msgid "June 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:45 +msgid "June 6" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:47 +msgid "" +"To see the removal strategy in action, create a :ref:`delivery order " +"` for seven cinder blocks by navigating to the " +":menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:51 +msgid "" +":guilabel:`Confirm` the sales order to create a delivery order. Doing so " +"reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First " +"Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:54 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the cinder block's product line in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:58 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from. Since the order demanded seven cinder blocks, the newest cinder" +" blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First " +"Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst-1 +msgid "" +"The detailed operations shows which lots are being selected for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 +msgid "Consignment: buy and sell stock without owning it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:5 +msgid "" +"Most of the time, products stored in a company's warehouse are either " +"purchased from suppliers, or are manufactured in-house. However, suppliers " +"will sometimes let companies store and sell products in the company's " +"warehouse, without having to buy those items up-front. This is called " +"*consignment*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:10 +msgid "" +"Consignment is a useful method for suppliers to launch new products, and " +"easily deliver to their customers. It's also a great way for the company " +"storing the products (the consignee) to earn something back for their " +"efforts. Consignees can even charge a fee for the convenience of storing " +"products they don't actually own." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:16 +msgid "Enable the consignment setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:18 +msgid "" +"To receive, store, and sell consignment stock, the feature needs to be " +"enabled in the settings. To do this, go to :menuselection:`Inventory --> " +"Configuration --> Settings`, and under the :guilabel:`Traceability` section," +" check the box next to :guilabel:`Consignment`, and then click " +":guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Enabled Consignment setting in Inventory configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:28 +msgid "Receive (and store) consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:30 +msgid "" +"With the feature enabled in Odoo, consignment stock can now be received into" +" a warehouse. From the main :menuselection:`Inventory` dashboard, click into" +" the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:35 +msgid "" +"Consignment stock is not actually purchased from the vendor; it is simply " +"received and stored. Because of this, there are no quotations or purchase " +"orders involved in receiving consignment stock. So, *every* receipt of " +"consignment stock will start by creating manual receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:39 +msgid "" +"Choose a vendor to enter in the :guilabel:`Receive From` field, and then " +"choose the same vendor to enter in the :guilabel:`Assign Owner` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:43 +msgid "" +"Since the products received from the vendor will be owned by the same " +"vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields " +"must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:46 +msgid "" +"Once the vendor-related fields are set, enter products into the " +":guilabel:`Product` lines, and set the quantities to be received into the " +"warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of " +"Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be " +"changed, as well. Once all the consignment stock has been received, " +":guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:58 +msgid "" +"Once consignment stock has been received into the warehouse, it can be sold " +"the same as any other in-stock product that has the :guilabel:`Can Be Sold` " +"option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:61 +msgid "" +"To create a sales order, navigate to the :menuselection:`Sales` app, and " +"from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, " +"choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:66 +msgid "" +"The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` " +"that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:69 +msgid "" +"Add the consignment product under the :guilabel:`Product` column in the " +"order lines, set the :guilabel:`Quantity`, and fill out any other pertinent " +"product details on the form. Once the quotation is complete, click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:77 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will " +"become a sales order. From here, the products can be delivered by clicking " +"on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate`" +" to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:84 +msgid "" +"Although consignment stock is owned by the vendor who supplied it, and not " +"by the company storing it in their warehouse, consignment products will " +"*still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:87 +msgid "" +"To find inventory reports, go to :menuselection:`Inventory --> Reporting`, " +"and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:91 +msgid "" +"Since the consignee does not actually own consigment stock, these products " +"are *not* reflected in the :guilabel:`Stock Valuation` report, and have no " +"impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:98 +msgid "" +"To view all information about on-hand stock moves, navigate to the the " +":guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory " +"--> Reporting --> Product Moves`. For consignment products, the information " +"in this report is the same as any other product: the history of its product " +"moves can be reviewed; the :guilabel:`Quantity Done` and " +":guilabel:`Reference` document are available; and its :guilabel:`Locations` " +"are available, as well. The consignment stock will originate from " +":guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:106 +msgid "" +"To view a consignment product's moves by ownership, select the " +":guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` " +"parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to " +"finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:115 +msgid "" +"To see forecasted units of consignment stock, go to " +":menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:121 +msgid "" +"View the :guilabel:`Stock On Hand` dashboard by navigating to " +":menuselection:`Inventory --> Reporting --> Inventory Report`. From this " +"report, the :guilabel:`Locations` of all stock on-hand are displayed, in " +"addition to the quantities per location. For consigment products, the " +":guilabel:`Owner` column will be populated with the owner of those products," +" or the original vendor who supplied the products in the first place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:3 +msgid "Putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:6 +msgid "What is a Putaway Rule?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:8 +msgid "" +"A good warehouse implementation makes sure that products automatically move " +"to their appropriate destination location. To make that process easier, Odoo" +" uses *Putaway Rules*. Putaway is the process of taking products from the " +"received shipments and putting them into the appropriate location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:13 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:20 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Activate Multi-Step Routes in Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:29 +msgid "Setting up a putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:31 +msgid "" +"In some cases, like for a retail shop storing fruits and vegetables, " +"products should be stored in different locations depending on several " +"factors like frequency, size, product category, specific environment needs, " +"and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:35 +msgid "" +"In this example, suppose there is one warehouse location, **WH/Stock**, with" +" the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:38 +msgid "WH/Stock/Pallets" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:40 +msgid "WH/Stock/Pallets/PAL1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:41 +msgid "WH/Stock/Pallets/PAL2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:42 +msgid "WH/Stock/Pallets/PAL3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:44 +msgid "WH/Stock/Shelf 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:46 +msgid "WH/Stock/Shelf 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:48 +msgid "WH/Stock/Shelf 2/Small Refrigerator" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:50 +msgid "WH/Stock/Shelf 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:52 +msgid "" +"Manage those locations with putaway rules. To create a putaway rule, open " +"the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> " +"Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway " +"rule that indicated the main location the product will enter before being " +"redirected to the right storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:58 +msgid "" +"The putaway rules can be defined either per product/product category and/or " +"package type (the :guilabel:`Packages` setting must be enabled for that). " +"Putaway rules are read sequentially until a match is found." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:62 +msgid "Take the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:64 +msgid "" +"If water (category All/drinks) is received, whatever the package, it will be" +" redirected to WH/Stock/Shelf 2/Small Refrigerator." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:66 +msgid "" +"If orange juice cans, packaged in boxes, are received, they will be " +"redirected to WH/Stock/Shelf 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:68 +msgid "" +"If water or apple juice bottles, packaged in boxes, are received, they will " +"be redirected to WH/Stock/Shelf 3." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:70 +msgid "" +"If a pallet of lemonade cans are receieved, it will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:77 +msgid "Using Storage Categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:79 +msgid "" +"A *Storage Category* is an extra location attribute. Storage categories " +"allow the user to define the quantity of products that can be stored in the " +"location and how the location will be selected with putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:86 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Storage Categories` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:91 +msgid "Create a Storage Category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:93 +msgid "" +"To create a storage category, go to :menuselection:`Inventory --> " +"Configuration --> Storage Categories` and click :guilabel:`Create`. Then, " +"click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to " +":menuselection:`Configuration --> Storage Categories` to create a new " +"storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "" +"Create Storage Categories inside Odoo Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:102 +msgid "" +"First, click :guilabel:`Create` and type a name for the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 +msgid "" +"Then, there are options to limit the capacity by weight, by product, or by " +"package type. The :guilabel:`Allow New Product` field defines when the " +"location is considered available to store a product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 +msgid "" +":guilabel:`If location is empty`: a product can be added there only if the " +"location is empty." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:109 +msgid "" +":guilabel:`If products are the same`: a product can be added there only if " +"the same product is already there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:111 +msgid "" +":guilabel:`Allow mixed products`: several different products can be stored " +"in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:114 +msgid "" +"Once the storage category settings are saved, the storage category can be " +"linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "" +"When a Storage Category is created, it can be linked to a warehouse " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:121 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:123 +msgid "" +"To continue the example from above, apply the \"High Frequency Pallets\" on " +"the PAL1 and PAL2 locations and rework the putaway rules as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:126 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 +msgid "" +"If PAL1 and PAL2 are empty, the pallet will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 +msgid "" +"If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:130 +msgid "" +"If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Storage Categories used in a variety of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:3 +msgid "Removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:5 +msgid "" +"For companies with warehouses, *removal strategies* determine **which** " +"products are taken from the warehouse, and **when**. For example, for " +"perishable products, prioritizing the picking of goods with the nearest " +"expiration date helps minimize food spoilage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:9 +msgid "" +"The following columns in the table below list the removal strategies " +"available in Odoo, and detail how pickings are determined along with the " +"picking order. Leverage these removal strategies to have Odoo automatically " +"select how products are selected for orders:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:18 +msgid ":doc:`FIFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:19 +msgid ":doc:`LIFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:20 +msgid ":doc:`FEFO `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 +msgid ":doc:`Closest Location `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:22 +msgid ":doc:`Least Packages `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:23 +msgid "Based on" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:25 +msgid ":ref:`Incoming date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:26 +msgid ":ref:`Removal date `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:27 +msgid ":ref:`Location sequence `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:28 +msgid ":ref:`Package quantity `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:29 +msgid "Selection order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:30 +msgid "First in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:31 +msgid "Last in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:32 +msgid ":ref:`First to expire `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 +msgid "" +":ref:`Alphanumeric name of location `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:34 +msgid "Quantity closest to fulfilling demand" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:36 +msgid "" +"For comprehensive examples for how to use each removal strategy, refer to " +"each individual documentation page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:44 +msgid "" +"Removal strategies are set on either the product category or storage " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "" +"Change the Force Removal Strategy for either the Product Categories or " +"Locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:50 +msgid "" +"Configure removal strategies on the location by going to " +":menuselection:`Inventory --> Configuration --> Locations`, and selecting " +"the desired location. On the location form, choose a removal strategy from " +"the :guilabel:`Removal Strategy` field's drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:55 +msgid "" +"To set a removal strategy on a location, the :guilabel:`Storage Locations` " +"and :guilabel:`Multi-Step Routes` settings **must** be enabled in " +":menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 +msgid "" +"These features are **only** necessary when setting the removal strategy on a" +" location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:61 +msgid "" +"Configure removal strategies on product categories by going to " +":menuselection:`Inventory --> Configuration --> Product Categories` and " +"selecting the intended product category. Next, choose a removal strategy " +"from the :guilabel:`Force Removal Strategy` drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:66 +msgid "" +"When there are different removal strategies applied on both the location and" +" product category for a product, the value set on the :guilabel:`Force " +"Removal Strategy` field set on a :guilabel:`Product Category` form is " +"applied as top priority." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:91 +msgid "Required features" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:73 +msgid "" +"While some removal strategies are available by default, some additional " +"features **must** be enabled in :menuselection:`Inventory --> Configuration " +"--> Settings` for the removal strategy option to appear in the drop-down " +"menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal " +"Strategy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:78 +msgid "" +"Refer to the table below for a summary of required features. Otherwise, " +"refer to the dedicated sections for the removal strategy for more details on" +" requirements and usage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:86 +msgid "FIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 +msgid "LIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:88 +msgid "FEFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:89 +msgid "Closest Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 +msgid "Least Packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:93 +msgid "Lots & Serial Numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:94 +msgid "Lots & Serial Numbers, Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:95 +msgid "Storage Locations, Multi-Step Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 +msgid "Packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:101 +msgid "Lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:103 +msgid "" +"Lots and serial numbers differentiate identical products and track " +"information like arrival or expiration dates. To enable this feature, " +"navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under" +" the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots " +"& Serial Numbers` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 +msgid "" +"Next, ensure the intended product is tracked by lots or serial numbers by " +"navigating to the product form through :menuselection:`Inventory --> " +"Products --> Products`, and selecting the desired product. On the product " +"form, switch to the :guilabel:`Inventory` tab, and under the " +":guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial " +"Number` or :guilabel:`By Lots` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 +msgid "" +"After enabling the features, assign lot or serial numbers to products using " +"an :doc:`inventory adjustment <../inventory_management/count_products>` or " +"during :ref:`product reception `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 +msgid "Locations and routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:125 +msgid "" +"**Storage locations** and **multi-step routes** are necessary features for " +"setting **all** types of removal strategies on a location. However, these " +"features are specifically required for the closest location removal strategy" +" since it is only applied at the location level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 +msgid "" +"To activate these features, navigate to :menuselection:`Inventory --> " +"Configuration --> Settings`. Under the :guilabel:`Warehouse` heading, enable" +" the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` " +"features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable the locations and route features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 +msgid "" +"Enable the **expiration date** feature to track expiration dates, best " +"before dates, removal dates, and alert dates on a lot or serial number by " +"navigating to :menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 +msgid "" +"Under the :guilabel:`Traceability` heading, ensure the :guilabel:`Lots & " +"Serial Numbers` feature is selected, and then select the check box for " +":guilabel:`Expiration Dates` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable expiration dates feature for FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:158 +msgid "" +"The *packages* feature is used to group products together and is required " +"for the least packages removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:161 +msgid "" +"Navigate to :menuselection:`Inventory --> Configuration --> Settings` and " +"select the check box for the :guilabel:`Packages` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable the packages feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:170 +msgid "" +":doc:`2-step delivery " +"<../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:171 +msgid "" +":doc:`3-step delivery " +"<../../shipping_receiving/daily_operations/delivery_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 +msgid "Sell stock from multiple warehouses using virtual locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:5 +msgid "" +"While keeping stock and selling inventory from one warehouse might work for " +"smaller companies, bigger companies might need to keep stock in, or sell " +"from, multiple warehouses in multiple locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:9 +msgid "" +"In Odoo, sometimes products included in a single sales order might take " +"stock from two (or more) warehouses. In Odoo, pulling products from multiple" +" warehouses to satisfy sales demands can be done by using *virtual " +"locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:14 +msgid "" +"In order to create virtual locations in warehouses and proceed to the " +"following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step" +" Routes` features will need to be enabled in the :menuselection:`Settings` " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:18 +msgid "" +"To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, " +"scroll down to the :guilabel:`Warehouse` section, and click the checkboxes " +"next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. " +"Then, :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:23 +msgid "Create and configure a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:25 +msgid "" +"Before creating any virtual stock locations, a new warehouse will need to be" +" created. This new warehouse will act as a *virtual* warehouse, and will be " +"the *parent* location of other physical warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:31 +msgid "" +"Virtual warehouses are great for companies with multiple physical " +"warehouses. This is because a situation might arise when one warehouse runs " +"out of stock of a particular product, but another warehouse still has stock " +"on-hand. In this case, stock from these two (or more) warehouses could be " +"used to fulfill a single sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:36 +msgid "" +"The \"virtual\" warehouse acts as a single aggregator of all the inventory " +"stored in a company's physical warehouses, and is used (for traceability " +"purposes) to create a hierarchy of locations in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:58 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:43 +msgid "" +"To create a new warehouse, go to :menuselection:`Inventory --> Configuration" +" --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse " +":guilabel:`Name` and :guilabel:`Short Name` can be changed, and other " +"warehouse details can be changed under the :guilabel:`Warehouse " +"Configuration` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:48 +msgid "" +"Under the :guilabel:`Shipments` heading, set the number of steps used to " +"process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by" +" selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and " +":guilabel:`3 steps` radio buttons. The desired option for " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will " +"depend on the warehouse's procurement process, and might differ for " +"individual products or product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:55 +msgid "" +":doc:`How to choose the right flow to handle receipts and deliveries? " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:58 +msgid "" +"Under the :guilabel:`Resupply` heading, configure the method(s) for how the " +"warehouse resupplies its inventory:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:61 +msgid "" +":guilabel:`Resupply Subcontractors`: resupply subcontractors with components" +" from this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:62 +msgid "" +":guilabel:`Manufacture to Resupply`: when products are manufactured, they " +"can be manufactured in this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:64 +msgid "" +":guilabel:`Manufacture`: to produce right away, move the components to the " +"production location directly and start the manufacturing process; to pick " +"first and then produce, unload the components from the stock to input " +"location first, and then transfer it to the production location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:68 +msgid "" +":guilabel:`Buy to Resupply`: when products are bought, they can be delivered" +" to this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:69 +msgid "" +":guilabel:`Resupply From`: automatically create routes to resupply this " +"warehouse from another chosen warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:73 +msgid "" +"*Routes* can be set and configured directly from the :guilabel:`Warehouse` " +"form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse" +" is configured, virtual *Locations* can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "The edit screen for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:81 +msgid "" +"In order to apply this virtual warehouse as the *parent* location of two " +"*child* location warehouses, there need to be two warehouses configured with" +" physical stock locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid "**Parent Warehouse**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Location`: `VWH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid "**Child Warehouses**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:95 +msgid "Create a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:98 +msgid "" +"In order to take stock from multiple warehouses to fulfill a sales order, " +"there need to be at least **two** warehouses acting as *child locations* of " +"the *virtual parent location* warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:101 +msgid "" +"To create and edit *Locations*, go to :menuselection:`Inventory --> " +"Configuration --> Locations`. All :guilabel:`Locations` are listed here, " +"including the *Stock* :guilabel:`Location` of the virtual warehouse that was" +" created. Click into the *Stock* :guilabel:`Location` for the virtual " +"warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:106 +msgid "" +"Then, under the :guilabel:`Additional Information` section, change the " +":guilabel:`Location Type` from :guilabel:`Internal Location` to " +":guilabel:`View`. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:109 +msgid "" +"This identifies this :guilabel:`Location` as a *virtual location*, which is " +"used to create a hierarchical structure for a warehouse and aggregate its " +"*child locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:113 +msgid "" +"Products can *not* be stored in a :guilabel:`View` :guilabel:`Location " +"Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Warehouse location types in location creation screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:120 +msgid "Configure physical warehouse locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:122 +msgid "" +"Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), " +"and remove any filters in the :guilabel:`Search Bar`. Then, click into the " +"first physical warehouse :guilabel:`Location` that was previously created to" +" be a *child location*, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:126 +msgid "" +"Under :guilabel:`Parent Location`, select the virtual warehouse from the " +"drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the " +":guilabel:`Locations` overview, and repeat this step for the second physical" +" warehouse stock location. Be sure to :guilabel:`Save` changes again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:130 +msgid "" +"Both locations are now *child locations* of the virtual warehouse *parent " +"location*. This allows stock to be taken from multiple locations to fulfill " +"a single sales order, if there is not enough stock in any one location " +"(provided they are both tied to the same virtual warehouse *parent " +"location*)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:136 +msgid "Example flow: Sell a product from a virtual warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:139 +msgid "" +"To sell products from multiple warehouses using a virtual *parent* location " +"in this flow, there must be at least **two** products and at least **two** " +"warehouses configured - with at least **one** product with quantity on-hand " +"in each warehouse, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:143 +msgid "" +"To create a new request for quotation, or RFQ, navigate to the " +":menuselection:`Sales` app, and click :guilabel:`Create` from the " +":guilabel:`Quotations` overview. Fill out the information on the new " +"quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a " +"product` to add the two products stored in the two warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:148 +msgid "" +"Then, click the :guilabel:`Other Info` tab on the sales order form. Under " +"the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field " +"value listed to the virtual warehouse that was previously created. Once the " +"warehouse has been changed, click :guilabel:`Confirm` to convert the " +"quotation into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:153 +msgid "" +"Now that the quotation has been confirmed as a sales order, click the " +":guilabel:`Delivery` smart button. From the warehouse delivery form, confirm" +" that the :guilabel:`Source Location` value matches the " +":guilabel:`Warehouse` field value from the sales order. Both should list the" +" virtual warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:159 +msgid "" +"The :guilabel:`Source Location` on the warehouse delivery form and the " +":guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales " +"order form *must* match in order for the products included in the sales " +"order to be pulled from different warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:163 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Source Location`" +" field on the warehouse delivery form, then click :guilabel:`Edit`, make the" +" change, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:166 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Warehouse` field" +" on the sales order, then a new quotation may need to be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:168 +msgid "" +"If the :guilabel:`Warehouse` field is missing on the sales order form, then " +"the virtual warehouse (and its children warehouses) may not have been set up" +" correctly, in which case, review the documentation above again to make sure" +" all settings/configuration were done properly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Delivery order with matching source and child locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:176 +msgid "" +"Finally, on the warehouse delivery form, under the :guilabel:`Detailed " +"Operations` tab, confirm that the *Locations* values under the " +":guilabel:`From` column for each product matches to the *child locations* " +"that are tied to the virtual *parent location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:181 +msgid "" +"To view which *Locations* the products are coming from on the drop-down " +"menus, click the :guilabel:`internal link (arrow)` icon to expand the " +"*Location* information. If needed, it can be changed from here (granted " +"there is quantity on hand for the product in that location)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:185 +msgid "" +"Once everything has been properly set, click :guilabel:`Validate` and then " +":guilabel:`Apply` to validate the delivery. Then, navigate back to the sales" +" order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to " +"invoice for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:190 +msgid "" +"To use a virtual *parent* location as the default warehouse for sales " +"orders, each salesperson can have the virtual warehouse assigned to them " +"from the drop-down menu next to :guilabel:`Default Warehouse` on their " +"employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Default warehouse location on employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:3 +msgid "Units of measure, packages, and packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:5 +msgid "" +"In Odoo, there are a variety of ways to specify the amount of products being" +" bought, stocked, and sold. *Units of measure*, *packages*, and *packagings*" +" are all available to streamline inventory flows, allowing for a variety of " +"configurations for products as they enter and leave the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:12 +msgid "Units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:14 +msgid "" +"A *unit of measure (UoM)* refers to any of the different standards used to " +"measure and handle a quantifiable amount of products, such a units, weight, " +"time, or size. Different :abbr:`UoMs (Units of Measure)` for weight, for " +"example, can be kilos, pounds, ounces, grams, and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:18 +msgid "" +"In Odoo, stock management and purchasing from suppliers are streamlined by " +"specifying different :abbr:`UoMs (Units of Measure)` for both buying and " +"selling products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 +msgid "Specify unit of measure for selling a product vs purchasing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:25 +msgid "" +"Once a product has a default :guilabel:`Unit of Measure` and " +":guilabel:`Purchase Unit of Measure` set on the product form, Odoo " +"automatically converts the different units in the product's purchase/sales " +"orders and the corresponding delivery orders/receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:29 +msgid "" +"The only condition is that all of the units have to be in the *same " +"category* (unit, weight, volume, length, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:33 +msgid "On the product form for `Rope`, the following fields are set as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:35 +msgid ":guilabel:`Unit of Measure` in `ft` (feet), and" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:36 +msgid ":guilabel:`Purchase Unit of Measure` in `cm` (centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:38 +msgid "" +"Because the vendor sells rope in `cm`, the purchase :guilabel:`UoM` is used " +"to represent the quantity on the :abbr:`PO (Purchase Order)`, which is also " +"in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Display purchase order for the product, rope, in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:45 +msgid "" +"After confirming the :abbr:`PO (Purchase Order)`, the quantity of product " +"(found under the now visible :guilabel:`Demand` column) is converted from " +"the purchase :abbr:`UoM (Unit of Measure)` to the :guilabel:`Unit of " +"Measure`. Then, when the product is received by clicking the " +":guilabel:`Validate` button, the quantity in :guilabel:`Done` is " +"automatically adjusted to match the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:52 +msgid "" +"On the *receipt* for `Rope`, the quantities are automatically converted from" +" `500 cm` that was requested on the purchase order, to `16.40 ft` to match " +"the internal/stock :guilabel:`Unit of Measure` value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Rope quantity is converted from cm to ft during warehouse reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:61 +msgid "" +":ref:`Use Different Units of Measure " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:68 +msgid "" +"Packages are a physical container that holds one or several products from a " +"picking, typically used for outgoing deliveries or internal transfers. " +"Packages can be a reusable or disposable (shipping) box, and are **not** " +"specific to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:72 +msgid "" +"Reusable boxes temporarily hold products during a picking to be brought to " +"either a packing or shipping area. Disposable boxes are the actual shipping " +"containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are " +"used to ship the products out to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:76 +msgid "" +"Multiple items in a sales order (SO) can be separated into different " +"packages to accommodate the products. For example, an :abbr:`SO (Sales " +"Order)` that has 20 boxes of pencils and 4 boxes of erasers can be separated" +" into two separate packages, each containing 10 boxes of pencils and 2 boxes" +" of erasers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:82 +msgid "" +"Products do *not* have to be divided equally. Products can be divided into " +"as many packages that are needed to accommodate the :abbr:`SO (Sales " +"Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:85 +msgid "" +"In Odoo, the quantity of products in each package needs to be recorded, so " +"there is a full history for each product, including which package each item " +"is shipped out in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:88 +msgid "" +"To use this method, ensure the :guilabel:`Packages` option is enabled, by " +"navigating to :menuselection:`Inventory app --> Configuration --> Settings " +"--> Operations`. Click the :guilabel:`Packages` check box, and then " +":guilabel:`Save` to activate the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:92 +msgid "" +"On a delivery order, assign which package to use by clicking on the " +":guilabel:`≣ (Detailed Operations)` icon to the right of each product in the" +" :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 +msgid "Find detailed operations icon to the right on the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:99 +msgid "" +"Clicking the :guilabel:`≣ (Detailed Operations)` icon of a product reveals a" +" pop-up window. In this window, the :guilabel:`Product` name, " +":guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed " +"above the customizable product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:103 +msgid "" +"Here, the warehouse location the product is coming from can be modified, in " +"addition to the :guilabel:`Source Package` and :guilabel:`Destination " +"Package`, which represents what package(s) the product(s) will be packaged " +"into." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:107 +msgid "" +"Click :guilabel:`Add a line` to include each additional package used. Enter " +"the desired amount in the :guilabel:`Done` field to specify the amount of " +"products that will go into the :guilabel:`Destination Package`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:112 +msgid "Multiple packages in a single delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:114 +msgid "" +"Although a :abbr:`DO (Delivery Order)` is typically associated with a single" +" package, orders can be split by clicking the :guilabel:`≣ (Detailed " +"Operations)` icon next to the products on an :abbr:`SO (Sales Order)` line. " +"This opens the :guilabel:`Detailed Operations` window with an editable table" +" to specify which products are intended for which package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:120 +msgid "" +"To package 10 boxes of pencils with 2 boxes of erasers from the same " +":abbr:`SO (Sales Order)`, begin by navigating to the :abbr:`DO (Delivery " +"Order)`. Then, select the :guilabel:`≣ (four horizontal lines)` icon to the " +"right of the product, `Box of Pencils`. Clicking the icon opens the " +":guilabel:`Detailed Operations` window that is used to detail how products, " +"like the 20 `Box of Pencils`, are packaged." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:126 +msgid "" +"Type in `10` under the :guilabel:`Done` field to package 10 products into " +"the :guilabel:`Destination Package`. To specify the destination package, " +"type the name of an existing package (such as `PACK0000006`) under the " +"field, :guilabel:`Destination Package`. If the package does not exist, Odoo " +"displays the :guilabel:`Create` button to create a new package. Click " +":guilabel:`Add a line` to assign the remaining products in another package, " +"`PACK0000007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "" +"Detailed operations pop-up where the amount of product going in a pack can " +"be specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:136 +msgid "" +"Select :guilabel:`Detailed Operations` on the product line for `Box of " +"Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and " +"`PACK0000007` each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Put in pack button to match the done amount matches the demand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:143 +msgid "" +"Once all the products for each line have been entered, click " +":guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:146 +msgid "" +"The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as " +"products are selected for each package. When the :guilabel:`Done` amount " +"matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button" +" to complete the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:151 +msgid "" +"The :guilabel:`Put In Pack` button is intended to quickly package all " +"products in the :abbr:`DO (Delivery Order)` into one new package. The option" +" to rename the package, or modify its contents, is available in the " +":guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:155 +msgid "" +"Clicking on the :guilabel:`Packages` smart button in the upper-right corner " +"of the delivery order reveals a separate page, showing all the packages used" +" in that :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:159 +msgid "Packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:161 +msgid "" +"*Packaging* is product specific, and refers to a disposable container that " +"holds several units of a specific product. Unlike packages, packagings " +"cannot be reusable, and each specific packaging must be defined on the " +"individual product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:165 +msgid "" +"For example, different packages for cans of soda can be configured as a " +"6-pack, a 12-pack, or a case of 36. Each flavor of soda would need a `6`, " +"`12`, and `36` can packaging configured on the individual product since " +"packagings are product specific, not generic." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:170 +msgid "Set up packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:172 +msgid "" +"To use packagings, ensure the :guilabel:`Product Packagings` feature is " +"enabled. To do that, navigate to :menuselection:`Inventory app --> " +"Configuration --> Settings`. Then, under the :guilabel:`Products` heading, " +"check the box next to :guilabel:`Product Packagings`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:177 +msgid "" +"In Odoo, product packagings are used on sales/purchase orders and inventory " +"transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:179 +msgid "" +"Next, to create packagings, navigate to :menuselection:`Inventory app --> " +"Products --> Products` and click on the desired product, then click " +":guilabel:`Edit` on the product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:182 +msgid "" +"Under the :guilabel:`Inventory` tab, scroll down to the " +":guilabel:`Packaging` section, and click :guilabel:`Add a line`. Then, a " +"pop-up window appears, in which the following information for each packaging" +" should be entered:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:186 +msgid "" +":guilabel:`Packaging`: name of packaging that appears on sales/purchase " +"orders as a packaging option for the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:188 +msgid ":guilabel:`Contained quantity`: amount of product in the packaging" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:189 +msgid "" +":guilabel:`Barcode`: identifier used with the :ref:`Barcode app " +"` to trace the packaging of a product during stock" +" moves or pickings. Leave blank if not in use" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:191 +msgid "" +":guilabel:`Company`: indicates the packaging is only available at the " +"selected company. Leave blank to make the packaging available across all " +"companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:195 +msgid "" +"Create a packaging type for 6 cans of the product, `Grape Soda`, by naming " +"the :guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained " +"quantity` to `6` in the pop-up window that appears after clicking on " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Create 6-pack case for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:203 +msgid "" +"When all the necessary information has been entered, either click " +":guilabel:`Save & Close` to save the packaging and return to the product " +"detail form, or :guilabel:`Save & New` to save the packaging and create " +"another one in a fresh pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:208 +msgid "" +"View all product packagings in the :guilabel:`Inventory` tab of the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "" +"Show packaging and contained quantities, specified on the product page form in the\n" +"Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:216 +msgid "View all packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:218 +msgid "" +"To view all packagings that have been created, go to " +":menuselection:`Inventory app --> Configuration --> Product Packagings`. " +"Doing so reveals the :guilabel:`Product Packagings` page with a complete " +"list of all packagings that have been created for all products. Create new " +"packagings by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:224 +msgid "" +"Two soda products, `Grape Soda` and `Diet Coke`, have three types of " +"packaging configured. On the :guilabel:`Product Packagings` page, each " +"product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 " +"products, or a `Case` of 32 products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "List of different packagings for products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:233 +msgid "Apply packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:235 +msgid "" +"When creating a sales order in the :menuselection:`Sales` app, specify the " +"packagings that should be used for the product(s). The chosen packaging is " +"displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` " +"field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:240 +msgid "" +"18 cans of the product, `Grape Soda`, is packed using three 6-pack " +"packagings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Assign packagings on the Sales Order Line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:247 +msgid "" +"Packaging can be used in conjunction with Odoo :ref:`Barcode " +"`. When receiving products from suppliers, " +"scanning the packaging barcode automatically adds the number of units in the" +" packaging to the internal count of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:5 +msgid "" +"While a batch transfer is a group of several pickings, a **wave transfer** " +"only contains some parts of different pickings. Both methods are used to " +"pick orders in a warehouse, and depending on the situation, one method may " +"be a better fit than the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:9 +msgid "" +"To handle orders of a specific product category, or fetch products that are " +"at the same location, wave transfers are the ideal method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:12 +msgid "" +"In Odoo, wave transfers are actually batch transfers with an extra step: " +"transfers are split before being grouped in a batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:18 +msgid "" +"Before a wave transfer can be created, the :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers` options must be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:21 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings`. In " +"the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "" +"View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:32 +msgid "" +"Now that the settings are activated, start a wave transfer by adding " +"products to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:34 +msgid "" +"Wave transfers can only contain product lines from transfers of the same " +"operation type. To view all the transfers and product lines in a specific " +"operation, first go to the :guilabel:`Inventory` dashboard and locate the " +"desired operation type's card. Then, open the options menu (the three dots " +"icon in the corner of the operation type's card) and click " +":guilabel:`Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:43 +msgid "" +"On the operations page, select the product lines you want to add in a new or" +" existing wave. Then, click :guilabel:`Add to Wave`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:51 +msgid "" +"Use the :guilabel:`Filters` in the search bar to group lines with the same " +"product, location, carrier, etc..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:56 +msgid "" +"To add the selected lines to an existing wave transfer, select the " +":guilabel:`an existing wave transfer` option and select the existing wave " +"transfer from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:59 +msgid "" +"To create a new wave transfer, select the :guilabel:`a new wave transfer` " +"option. If creating a new wave transfer, an employee can also be set in the " +"optional :guilabel:`Responsible` field. Once the desired options are " +"selected, click :guilabel:`Confirm` to add the product lines to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:66 +msgid "" +"To view all wave transfers and their statuses, go to " +":menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers" +" can also be viewed in the :guilabel:`Barcode` app by going to " +":menuselection:`Barcode --> Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:5 +msgid "Inventory management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:3 +msgid "Inventory adjustments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:7 +msgid "" +"In any warehouse management system, the recorded inventory counts in the " +"database might not always match the actual inventory counts in the " +"warehouse. The discrepancy between the two counts can be due to damages, " +"human errors, theft, or other factors. As such, inventory adjustments must " +"be made to reconcile the differences, and ensure that the recorded counts in" +" the database match the actual counts in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:14 +msgid "Inventory Adjustments page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:16 +msgid "" +"To view the *Inventory Adjustments* page, navigate to " +":menuselection:`Inventory app --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "In stock products listed on the Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:23 +msgid "" +"On the :guilabel:`Inventory Adjustments` page, all products that are " +"currently in stock are listed, with each product line containing the " +"following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 +msgid "" +":guilabel:`Location`: the specific location in the warehouse where a product" +" is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:27 +msgid "" +":guilabel:`Product`: the product whose quantity is listed on the inventory " +"adjustment line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:28 +msgid "" +":guilabel:`Lot/Serial Number`: the tracking identifier assigned to the " +"specific product listed. It can contain letters, numbers, or a combination " +"of both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:32 +msgid "" +"If a specific product has a quantity of more than `1.00` in stock, and more " +"than one serial number (or lot number) assigned to it, each uniquely-" +"identified product is displayed on its own product line with its own " +"lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:37 +msgid "" +":guilabel:`On Hand Quantity`: the quantity of the product currently recorded" +" in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:38 +msgid "" +":guilabel:`UoM`: the *unit of measure* in which the product is measured. " +"Unless otherwise specified (i.e., in :guilabel:`Pounds` or " +":guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is " +":guilabel:`Units`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:41 +msgid "" +":guilabel:`Counted Quantity`: the real quantity counted during an inventory " +"count. This field is left blank by default, but can be changed, depending on" +" if it matches the :guilabel:`On Hand Quantity` or not." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:44 +msgid "" +":guilabel:`Difference`: the difference between the :guilabel:`On Hand " +"Quantity` and :guilabel:`Counted Quantity`, once an inventory adjustment is " +"made. The difference is automatically calculated after every inventory " +"adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 +msgid "" +":guilabel:`Scheduled Date`: the date at which a count should be made. If not" +" otherwise specified, this date will default to the 31st of December of the " +"current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 +msgid "" +":guilabel:`User`: the person assigned to the count in the database. This can" +" either be the person physically counting the inventory, or applying the " +"count in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:51 +msgid "" +":guilabel:`Product Category`: the category assigned internally to a specific" +" product. Unless otherwise specified (i.e., as :guilabel:`Consumable` or " +":guilabel:`Rental`), the default *Product Category* is set to " +":guilabel:`All`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:54 +msgid "" +":guilabel:`Available Quantity`: the quantity of a specific product that is " +"currently available, based on any outstanding/uncompleted sales orders, " +"purchase orders, or manufacturing orders that might change the available " +"quantity once fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 +msgid "" +":guilabel:`Accounting Date`: the date on which the adjustments will be " +"accounted in the Odoo *Accounting* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:59 +msgid "" +":guilabel:`Company`: the company whose database these inventory adjustments " +"are being made on. The company is listed in the top right corner of the " +"database, next to the user currently logged in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:63 +msgid "" +"Some columns are hidden by default. To reveal these columns, click the " +":guilabel:`additional options` button (three dots icon) to the far right of " +"the form's top row, and select any desired column to reveal by clicking the " +"checkbox next to that option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 +msgid "Create an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:70 +msgid "" +"To create a new inventory adjustment from the :menuselection:`Inventory " +"Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank " +"inventory adjustment line at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:74 +msgid "" +"On this blank inventory adjustment line, click the drop-down menu under the " +":guilabel:`Product` column, and select a product. If the selected product is" +" tracked using either lots or serial numbers, the desired lot or serial " +"number can also be chosen from the drop-down menu under the " +":guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:79 +msgid "" +"Next, set the value in the :guilabel:`Counted Quantity` column to the " +"quantity counted for that product during the inventory adjustment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:83 +msgid "" +"The :guilabel:`Counted Quantity` for new inventory adjustments is set to " +"`0.00` by default. An inventory move with `0.00` :guilabel:`Quantity Done` " +"is recorded in the product's inventory adjustment history, so it should be " +"set to reflect the actual quantity counted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:87 +msgid "" +"To the right of the :guilabel:`Counted Quantity` column, the " +":guilabel:`Scheduled Date` and :guilabel:`User` can also be changed via " +"their respective drop-down menus. Changing the :guilabel:`Scheduled Date` " +"changes the date that the inventory adjustment should be processed on, and " +"selecting a responsible :guilabel:`User` assigns a user to the specific " +"inventory adjustment (for traceability purposes)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:93 +msgid "" +"Once all changes have been made to the new inventory adjustment line, click " +"away from the line. Doing so saves the adjustment, and moves the line to the" +" top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:158 +msgid "" +"If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand " +"Quantity`, the value in the :guilabel:`Difference` column is **green**. If " +"the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand " +"Quantity`, the value in the :guilabel:`Difference` column is **red**. If the" +" quantities match, and haven't been changed at all, no value appears in the " +":guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Difference column on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:106 +msgid "" +"At this stage, the count (:dfn:`inventory adjustment`) is recorded, but not " +"yet applied. This means that the quantity on hand before the adjustment has " +"not yet been updated to match the new, real counted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:110 +msgid "" +"There are two ways to apply the new inventory adjustment. The first way is " +"to click the :guilabel:`Apply` button on the line at the far right of the " +"page. The second way is to click the checkbox on the far left of the line. " +"Doing so reveals new button options at the top of the page, one of which is " +"an :guilabel:`Apply` button. Clicking this button instead causes an " +":guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:116 +msgid "" +"From this pop-up menu, a reference or reason can be assigned to the " +"inventory adjustment. By default, the :guilabel:`Inventory Reference / " +"Reason` field is pre-populated with the date the adjustment is being made " +"on, but can be changed to reflect whatever reference or reason is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:120 +msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Apply all option applies the inventory adjustment once a reason is " +"specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 +msgid "Count products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 +msgid "" +"Counting products is a recurring activity in a warehouse. Once a count is " +"complete, go to :menuselection:`Inventory app --> Operations --> Inventory " +"Adjustments` to update the :guilabel:`Counted Quantity` column for each " +"product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:133 +msgid "" +"On each product line, identify whether the value in the :guilabel:`On Hand " +"Quantity` column recorded in the database matches the newly-counted value. " +"If the recorded value and the counted value do match, click the " +":guilabel:`Set` button (target icon) at the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:137 +msgid "" +"Doing so copies the value from the :guilabel:`On Hand Quantity` column over " +"to the :guilabel:`Counted Quantity` column, and sets the value of the " +":guilabel:`Difference` column to `0.00`. Subsequently, once applied, an " +"inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the " +"product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Zero count inventory adjustment move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:146 +msgid "" +"If the newly-counted value for a given product does **not** match the value " +"in the :guilabel:`On Hand Quantity` recorded in the database, instead of " +"clicking the :guilabel:`Set` button, record the real value in the field in " +"the :guilabel:`Counted Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:150 +msgid "" +"To do so, click the field in the :guilabel:`Counted Quantity` column on the " +"specific inventory adjustment line for the product whose count is being " +"changed. This automatically assigns a :guilabel:`Counted Quantity` of " +"`0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:154 +msgid "" +"To change this value, type in a new value that matches the real, newly-" +"counted value. Then, click away from the line. Doing so saves the " +"adjustment, and automatically adjusts the value in the " +":guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:164 +msgid "" +"Subsequently, once applied, a move with the difference between the " +":guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is " +"recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Inventory Adjustments History dashboard detailing a list of prior product " +"moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:172 +msgid "" +"Sometimes a count occurs, but cannot be applied in the database right away. " +"In the time between the actual count and applying the inventory adjustment, " +"product moves can occur. In that case, the on-hand quantity in the database " +"can change and no longer be consistent with the counted quantity. As an " +"extra precaution, Odoo asks for confirmation before applying the inventory " +"adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 +msgid "Change inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 +msgid "" +"By default, the *scheduled date* for inventory adjustments are always " +"scheduled for the 31st of December of the current year. However, for some " +"companies, it is crucial that they have an accurate inventory count at all " +"times. In such cases, the default scheduled date can be modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:185 +msgid "" +"To modify the default scheduled date, go to :menuselection:`Inventory app " +"--> Configuration --> Settings`. Then, in the :guilabel:`Operations` " +"section, locate the :guilabel:`Annual Inventory Day and Month` setting, " +"which includes a drop-down menu that is set to `31 December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Adjust the next inventory count date with the Annual Inventory Day and Month" +" setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:193 +msgid "" +"To change the day, click the :guilabel:`31`, and change it to a day within " +"the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:199 +msgid "" +"Once all desired changes have been made, click :guilabel:`Save` to save all " +"changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 +msgid "Plan big inventory counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 +msgid "" +"To plan big inventory counts, such as a full count of everything currently " +"in stock, first navigate to :menuselection:`Inventory app --> Operations -->" +" Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:207 +msgid "" +"Then, select the desired products to be counted by clicking the checkbox on " +"the far left of each product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:211 +msgid "" +"To request a count of **all** products currently in stock, click the " +"checkbox at the very top of the table, in the header row next to the " +":guilabel:`Location` label. This selects **all** product lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Request a count popup on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:219 +msgid "" +"Once all desired products have been selected, click the :guilabel:`Request a" +" Count` button at the top of the page. This causes a :guilabel:`Request a " +"Count` pop-up window to appear. From this pop-up, fill in the following " +"information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 +msgid ":guilabel:`Inventory Date`: the planned date of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +msgid ":guilabel:`User`: the user responsible for the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 +msgid "" +":guilabel:`Accounting Date`: the date at which the inventory adjustment will" +" be accounted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 +msgid "" +":guilabel:`Count`: to leave the on-hand quantity of each product line blank," +" select :guilabel:`Leave Empty`. To prefill the on-hand quantity of each " +"product line with the current value recorded in the database, select " +":guilabel:`Set Current Value`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:230 +msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:233 +msgid "" +"In the Odoo *Barcode* app, users can only view inventory counts that are " +"assigned to **them**, and are scheduled for **today** or **earlier**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:237 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 +msgid "Create a second warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 +msgid "" +"A *warehouse* is a physical building or space where items are stored. In " +"Odoo, it is possible to set up multiple warehouses and transfer stored items" +" between them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:8 +msgid "" +"By default, the Odoo platform has one warehouse that is already configured, " +"with the address set as the company's address. To create a second warehouse," +" select :menuselection:`Configuration --> Warehouses`, then click " +":guilabel:`Create` and configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:12 +msgid ":guilabel:`Warehouse`: the full name of the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 +msgid "" +":guilabel:`Short Name`: the abbreviated code by which the warehouse is " +"referred to; the short name for the default warehouse in Odoo is **WH**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 +msgid "" +":guilabel:`Company`: the company that owns the warehouse; this can be set as" +" the company that owns the Odoo database or the company of a customer or " +"vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:17 +msgid ":guilabel:`Address`: the address where the warehouse is located" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:20 +msgid "" +"The options below will only appear if the :guilabel:`Multi-Step Routes` " +"checkbox is enabled in :menuselection:`Configuration --> Settings` under the" +" :guilabel:`Warehouse` heading. For more information about routes and how " +"they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 +msgid "" +":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and" +" outgoing shipments should follow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:27 +msgid "" +":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied " +"from this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:28 +msgid "" +":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in " +"this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:29 +msgid "" +":guilabel:`Manufacture`: select the route that should be followed when " +"manufacturing goods inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:31 +msgid "" +":guilabel:`Buy to Resupply`: check the box to allow for purchased products " +"to be delivered to the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:33 +msgid "" +":guilabel:`Resupply From`: select warehouses that can be used to resupply " +"the warehouse being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "A filled out form for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:41 +msgid "" +"Creating a second warehouse will automatically enable the *Storage " +"Locations* setting, which allows location tracking of products within a " +"warehouse. To toggle this setting, navigate to :menuselection:`Configuration" +" --> Settings` and click the checkbox under the :guilabel:`Warehouse` " +"heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:46 +msgid "" +"After filling out the form, click :guilabel:`Save` and the new warehouse " +"will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 +msgid "Add inventory to a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:51 +msgid "" +"If a new warehouse is created that has existing inventory in it, the " +"inventory counts should be added to Odoo so that the stock listed in the " +"Odoo database reflects what is in the physical warehouse. To add inventory " +"to a new warehouse, navigate to :menuselection:`Inventory --> Operations -->" +" Inventory Adjustments`, and then click :guilabel:`Create`. The inventory " +"adjustment form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:57 +msgid "" +":guilabel:`Inventory Reference`: the name or code that the inventory " +"adjustment can be referred to by" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 +msgid "" +":guilabel:`Locations`: the location(s) where the inventory is stored; " +"include the new warehouse and any locations within it that inventory will be" +" added to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:61 +msgid "" +":guilabel:`Products`: include all products that will be added to inventory " +"or leave blank to select any product during the next step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:63 +msgid "" +":guilabel:`Include Exhausted Products`: include products with a quantity of " +"zero; does not affect inventory adjustments for new warehouses since they " +"have no existing inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:65 +msgid "" +":guilabel:`Accounting Date`: the date used by accounting teams for " +"bookkeeping related to the inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:67 +msgid "" +":guilabel:`Company`: the company that owns the inventory; can be set as the " +"user's company or as a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:69 +msgid "" +":guilabel:`Counted Quantities`: choose whether the counted quantities for " +"products being added should default to stock on hand or zero; does not " +"affect inventory adjustments for new warehouses since they have no existing " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "A filled out form for an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:77 +msgid "" +"Once the form is properly configured, click on :guilabel:`Start Inventory` " +"to be taken to the next page where products can be added to the inventory " +"adjustment. Add a new product by clicking on :guilabel:`Create` and then " +"fill out the product line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:81 +msgid ":guilabel:`Product`: the product being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 +msgid "" +":guilabel:`Location`: the location where the product is currently stored in " +"the new warehouse; this can be set as the overall warehouse or a location " +"within the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:84 +msgid "" +":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the " +"serial number used to identify it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:86 +msgid "" +":guilabel:`On Hand`: the total quantity of the product stored in the " +"location for which inventory is being adjusted; this should be zero for a " +"new location or warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:88 +msgid "" +":guilabel:`Counted`: the amount of the product that is being added to " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:89 +msgid "" +":guilabel:`Difference`: the difference between the *On Hand* and *Counted* " +"values; this will automatically update to reflect the value entered in the " +":guilabel:`Counted` column" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 +msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "Include a line for each product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 +msgid "" +"After adding all the products already stored in the new warehouse, click " +":guilabel:`Validate Inventory` to complete the inventory adjustment. The " +"values in the :guilabel:`On Hand` column will update to reflect those in the" +" :guilabel:`Counted` column and the products added will appear in the " +"inventory of the new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:5 +msgid "" +"A common use case for multiple warehouses is to have one central warehouse " +"that resupplies multiple shops, and in this case, each shop is considered a " +"local warehouse. When a shop wants to replenish a product, the product is " +"ordered to the central warehouse. Odoo allows the user to easily set which " +"warehouse(s) can resupply another warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:13 +msgid "" +"To resupply from another warehouse, first go to :menuselection:`Inventory " +"--> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-" +"Step Routes`. Then, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "Enable Multi-Step Routes in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:21 +msgid "" +"View all the configured warehouses by going to :menuselection:`Inventory -->" +" Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:24 +msgid "" +"Create a new warehouse by clicking :guilabel:`Create`. Then, give the " +"warehouse a name and a :guilabel:`Short Name`. Finally, click " +":guilabel:`Save` to finish creating the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:27 +msgid "" +"After that, go back to the :guilabel:`Warehouses` page and open the " +"warehouse that will be resupplied by the second warehouse. Then, click " +":guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the" +" :guilabel:`Resupply From` field, and check the box next to the second " +"warehouse's name. If the warehouse can be resupplied by more than one " +"warehouse, make sure to check those warehouses' boxes too. Finally, click " +":guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can " +"resupply this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:41 +msgid "" +"After configuring which warehouse(s) to resupply from, a new route is now " +"available on all product forms. The new route appears as :guilabel:`Supply " +"Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a " +"product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route" +" with a reordering rule or the make to order (MTO) route to replenish stock " +"by moving the product from one warehouse to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "" +"Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:51 +msgid "" +"When a product's reordering rule is triggered and the product has the " +":guilabel:`Supply Product from [Warehouse Name]` route set, Odoo " +"automatically creates two pickings. One picking is a *delivery order* from " +"the second warehouse, which contains all the necessary products, and the " +"second picking is a *receipt* with the same products for the main warehouse." +" The product move from the second warehouse to the main warehouse is fully " +"tracked in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:57 +msgid "" +"On the picking/transfer records created by Odoo, the :guilabel:`Source " +"Document` is the product's reordering rule. The location between the " +"delivery order and the receipt is a transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "" +"A reordering rule automatically creates two receipts for stock between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 +msgid "Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:5 +msgid "" +"A *location* is a specific space within a warehouse. This can be a shelf, " +"room, aisle, etc. There are three types of locations in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 +msgid "" +"*Physical locations* are spaces within a warehouse owned by the user's " +"company. These can be a an area where items are stored like an aisle or " +"shelf, or an area where operations take place, like loading and unloading " +"bays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 +msgid "" +"*Partner locations* are the same as physical locations except that they " +"exist within the warehouse of a customer or vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:13 +msgid "" +"*Virtual locations* are locations that do not exist physically, but where " +"items that are not in inventory can be placed. These can be items that have " +"not yet entered inventory, like products that are on the way to a warehouse," +" or items that are no longer in inventory due to loss or other factors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:19 +msgid "" +"In order to use locations, the :guilabel:`Storage Locations` setting must be" +" enabled. To do so, navigate to :menuselection:`Inventory --> Configuration " +"--> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable " +"the :guilabel:`Storage Locations` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 +msgid "Create a new location inside a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 +msgid "" +"Starting from the :menuselection:`Inventory` app, select " +":menuselection:`Configuration --> Locations --> Create`. The new location " +"form can then be configured as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:29 +msgid "" +":guilabel:`Location Name`: the name that will be used to reference the " +"location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:30 +msgid "" +":guilabel:`Parent Location`: the location or warehouse that the new location" +" exists within" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 +msgid "" +":guilabel:`Location Type`: choose the category that the location belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 +msgid "" +":guilabel:`Company`: the company that owns the warehouse that the location " +"is inside of" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 +msgid "" +":guilabel:`Is a Scrap Location?`: check this box to allow for " +"scrapped/damaged goods to be stored in this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 +msgid "" +":guilabel:`Is a Return Location?`: check this box to allow products to be " +"returned to this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 +msgid ":guilabel:`Barcode`: the barcode number assigned to the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 +msgid "" +":guilabel:`Removal Strategy`: the :doc:`strategy " +"<../advanced_operations_warehouse/removal>` for how items should be taken " +"from inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst-1 +msgid "The form for creating a new location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 +msgid "Create location hierarchies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 +msgid "" +"The *Parent Location* setting on the new location form allows for a location" +" to exist within a warehouse or another location. Every location can serve " +"as a parent location, and every parent location can have multiple locations " +"within it, allowing for the creation of a virtually infinite hierarchical " +"structure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 +msgid "" +"Location hierarchy could be organized so that a shelf is located within an " +"aisle, which is located within a room, which is located within the overall " +"warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 +msgid "" +"To create the location hierarchy in the example above, set the warehouse as " +"the parent of the room, the room as the parent of the aisle, and the aisle " +"as the parent of the shelf. This can be adapted to a hierarchy of any " +"magnitude." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 +msgid "Routes and Pull/Push Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 +msgid "" +"In inventory management, the supply chain strategy determines when products " +"should be purchased/manufactured, delivered to distribution centers, and " +"made available to the retail channel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:11 +msgid "" +"In Odoo, a product's supply chain strategy can be configured using *Routes*," +" which feature *Pull and Push Rules*. Once everything is properly " +"configured, the Inventory app can automatically generate transfers following" +" the configured push/pull rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:16 +msgid "Inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:18 +msgid "" +"In a generic warehouse, there are receiving docks, a quality control area, " +"storage locations, picking and packing areas, and shipping docks. All " +"products go through all these locations. As the products move through the " +"locations, each location triggers the products' specified route and rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic warehouse with stock and quality control area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:27 +msgid "" +"In this example, vendor trucks unload pallets of ordered products at the " +"receiving docks. Operators then scan the products in the receiving area. " +"Depending on the product's route and rules, some of these products are sent " +"to a quality control area (for example, products that are components used in" +" the manufacturing process), while others are directly stored in their " +"respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic push to rule when receiving products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 +msgid "" +"Here is an example of a fulfillment route. In the morning, items are picked " +"for all the orders that need to be prepared during the day. These items are " +"picked from storage locations and moved to the picking area, close to where " +"the orders are packed. Then, the orders are packed in their respective boxes" +" and conveyors bring them close to the shipping docks, ready to be delivered" +" to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic pull from rule when preparing deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:47 +msgid "Pull rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:49 +msgid "" +"With *Pull Rules*, a demand for some products triggers procurements, while " +"*Push Rules* are triggered by products arriving in a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:52 +msgid "" +"Pull Rules are used to fulfill a sales order. Odoo generates a need at the " +"*Customer Location* for each product in the order. Because pull rules are " +"triggered by a need, Odoo looks for a pull rule defined on the *Customer " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:56 +msgid "" +"In this case, a \"delivery order\" pull rule that transfers products from " +"the *Shipping Area* to the *Customer Location* is found, and a transfer " +"between the two locations is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:59 +msgid "" +"Then, Odoo finds another pull rule that tries to fulfill the need for the " +"*Shipping Area*: the \"packing\" rule that transfers products from the " +"*Packing Area* to the *Shipping Area*. Finally, other pull rules are " +"triggered until a transfer between the *Stock* and the *Picking Area* is " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:65 +msgid "" +"All these product transfers are automatically generated by Odoo based on the" +" pull rules, starting from the end (the customer location) and going " +"backward (the stock warehouse). While working, the operator processes these " +"transfers in the opposite order: first the picking, then the packing, and " +"finally the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:71 +msgid "Push rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:73 +msgid "" +"On the other hand, *Push Rules* are much easier to understand. Instead of " +"generating documents based on needs, they are triggered in real time when " +"products arrive in a specific location. Push rules basically say: \"when a " +"product arrives at a specific location, move it to another location.\"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:77 +msgid "" +"An example of a push rule would be: when a product arrives in the *Receipt " +"Area*, move it to the *Storage Location*. As different push rules can be " +"applied to different products, the user can assign different storage " +"locations for different products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:81 +msgid "" +"Another push rule could be: when products arrive at a location, move them to" +" the *Quality Control Area*. Then, once the quality check is done, move them" +" to their *Storage Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:85 +msgid "" +"Push rules can only be triggered if there are no pull rules that have " +"already generated the product transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:89 +msgid "" +"Sets of push/pull rules like those are called *Routes*. The grouping on the " +"rule decides if products are grouped in the same transfer or not. For " +"example, during the picking operation, all orders and their products are " +"grouped in one transfer, whereas the packing operation respects the grouping" +" per customer order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:97 +msgid "Use routes and rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:99 +msgid "" +"Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you " +"manage advanced route configurations such as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 +msgid "Manage product manufacturing chains." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 +msgid "Manage default locations per product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:104 +msgid "" +"Define routes within the stock warehouse according to business needs, such " +"as quality control, after-sales services, or supplier returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:106 +msgid "" +"Help rental management by generating automated return moves for rented " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:108 +msgid "" +"To configure a route for a product, first, open the :guilabel:`Inventory` " +"application and go to :menuselection:`Configuration --> Settings`. Then, in " +"the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` " +"feature and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "Activate the Multi-Step Routes feature in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:117 +msgid "" +"The :guilabel:`Storage Locations` feature is automatically activated with " +"the :guilabel:`Multi-Step Routes` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:120 +msgid "" +"Once this first step is completed, the user can use pre-configured routes " +"that come with Odoo, or they can create custom routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:124 +msgid "Pre-configured routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:126 +msgid "" +"To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> " +"Configuration --> Warehouses`. Then, open a warehouse form. In the " +":guilabel:`Warehouse Configuration` tab, the user can view the warehouse's " +"pre-configured routes for :guilabel:`Incoming Shipments` and " +":guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "A preconfigured warehouse in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:135 +msgid "" +"Some more advanced routes, such as pick-pack-ship, are also available. The " +"user can select the route that best fits their business needs. Once the " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are" +" set, head to :menuselection:`Inventory --> Configuration --> Routes` to see" +" the specific routes that Odoo generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of all the preconfigured routes Odoo offers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:144 +msgid "" +"On the :guilabel:`Routes` page, click on a route to open the route form. In " +"the route form, the user can view which places the route is " +":guilabel:`Applicable On`. The user can also set the route to only apply on " +"a specific :guilabel:`Company`. This is useful for multi-company " +"environments; for example, a user can have a company and warehouse in " +"Country A and a second company and warehouse in Country B." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of a route example applicable on product categories and warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:154 +msgid "" +"At the bottom of the route form, the user can view the specific " +":guilabel:`Rules` for the route. Each :guilabel:`Rule` has an " +":guilabel:`Action`, a :guilabel:`Source Location`, and a " +":guilabel:`Destination Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "An example of rules with push & pull actions in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:163 +msgid "Custom Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:165 +msgid "" +"To create a custom route, go to :menuselection:`Inventory --> Configuration " +"--> Routes`, and click on :guilabel:`Create`. Next, choose the places where " +"this route can be selected. A route can be applicable on a combination of " +"places." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a pick-pack-ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:173 +msgid "" +"Each place has a different behavior, so it is important to tick only the " +"useful ones and adapt each route accordingly. Then, configure the " +":guilabel:`Rules` of the route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:176 +msgid "" +"If the route is applicable on a product category, the route still needs to " +"be manually set on the product category form by going to " +":menuselection:`Inventory --> Configuration --> Product Categories`. Then, " +"select the product category and open the form. Next, click :guilabel:`Edit` " +"and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:181 +msgid "" +"When applying the route on a product category, all the rules configured in " +"the route are applied to **every** product in the category. This can be " +"helpful if the business uses the dropshipping process for all the products " +"from the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a route applied to the \"all\" product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:189 +msgid "" +"The same behavior applies to the warehouses. If the route can apply to " +":guilabel:`Warehouses`, all the transfers occurring inside the chosen " +"warehouse that meet the conditions of the route's rules will then follow " +"that route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the warehouse drop-down menu when selecting applicable on warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:197 +msgid "" +"If the route is applicable on :guilabel:`Sales Order Lines`, it is more or " +"less the opposite. The route must be manually chosen when creating a " +"quotation. This is useful if some products go through different routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:201 +msgid "" +"Remember to toggle the visibility of the :guilabel:`Route` column on the " +"quotation/sales order. Then, the route can be chosen on each line of the " +"quotation/sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the menu allowing to add new lines to sales orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:208 +msgid "" +"Finally, there are routes that can be applied to products. Those work more " +"or less like the product categories: once selected, the route must be " +"manually set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:211 +msgid "" +"To set a route on a product, go to :menuselection:`Inventory --> Products " +"--> Products` and select the desired product. Then, go to the " +":guilabel:`Inventory` tab and under the :guilabel:`Operations` section, " +"select the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a product form, where the route must be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:220 +msgid "Rules must be set on the route in order for the route to work." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:223 +msgid "Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:225 +msgid "" +"The rules are defined on the route form. First, go to " +":menuselection:`Inventory --> Configuration --> Routes` and open the desired" +" route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` " +"section, click on :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the rules menu, where it is possible to add new rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:233 +msgid "" +"The available rules trigger various actions. If Odoo offers *Push* and " +"*Pull* rules, others are also available. Each rule has an " +":guilabel:`Action`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:236 +msgid "" +":guilabel:`Pull From`: this rule is triggered by a need for the product in a" +" specific location. The need can come from a sales order being validated or " +"from a manufacturing order requiring a specific component. When the need " +"appears in the destination location, Odoo generates a picking to fulfill " +"this need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:240 +msgid "" +":guilabel:`Push To`: this rule is triggered by the arrival of some products " +"in the defined source location. In the case of the user moving products to " +"the source location, Odoo generates a picking to move those products to the " +"destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:243 +msgid "" +":guilabel:`Pull & Push`: this rule allows the generation of pickings in the " +"two situations explained above. This means that when products are required " +"at a specific location, a transfer is created from the previous location to " +"fulfill that need. This creates a need in the previous location and a rule " +"is triggered to fulfill it. Once the second need is fulfilled, the products " +"are pushed to the destination location and all the needs are fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:248 +msgid "" +":guilabel:`Buy`: when products are needed at the destination location, a " +"request for quotation is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:250 +msgid "" +":guilabel:`Manufacture`: when products are needed in the source location, a " +"manufacturing order is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" +"zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:258 +msgid "" +"The :guilabel:`Operation Type` must also be defined on the rule. This " +"defines which kind of picking is created from the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:261 +msgid "" +"If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or " +":guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The " +":guilabel:`Supply Method` defines what happens at the source location:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:265 +msgid "" +":guilabel:`Take From Stock`: the products are taken from the available stock" +" of the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:267 +msgid "" +":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to " +"bring the products to the source location. The available stock is ignored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:269 +msgid "" +":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the " +"products are taken from the available stock of the source location. If there" +" is no stock available, the system tries to find a rule to bring the " +"products to the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 +msgid "" +"In the *Scheduling* section, you can determine how Odoo behaves when one of " +"the chain's pickings is rescheduled. In case you decide to **Propagate " +"Rescheduling**, the next move is also to be rescheduled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:277 +msgid "" +"If you prefer having the choice to reschedule the next move, you can decide " +"to receive an alert in the form of a *next activity*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 +msgid "Sample full route flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:283 +msgid "" +"In this example, let's use a custom *Pick - Pack - Ship* route to try a full" +" flow with an advanced custom route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:286 +msgid "" +"First, a quick look at the route's rules and their supply methods. There are" +" three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply " +"Methods` for each rule are the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:289 +msgid "" +":guilabel:`Take From Stock`: When products are needed in the " +":guilabel:`WH/Packing Zone`, *picks* (internal transfers from " +":guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from " +":guilabel:`WH/Stock` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:292 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`WH/Output`, *packs* (internal transfers from " +":guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from " +":guilabel:`WH/Packing Zone` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`Partner Locations/Customers`, *delivery orders* are created from " +":guilabel:`WH/Output` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "Overview of all the transfers created by the pick - pack - ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 +msgid "" +"This means that, when a customer orders products that have a *pick - pack - " +"ship* route set on it, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the operations created by a pull from transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 +msgid "" +"If the source document for multiple tranfers is the same sales order, the " +"status is not the same. The status will be :guilabel:`Waiting Another " +"Operation` if the previous transfer in the list is not done yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the transfers' various statuses at the beginning of the process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:319 +msgid "" +"To prepare the delivery order, packed products are needed at the output " +"area, so an internal transfer is requested from the packing zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the packing and " +"output zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:326 +msgid "" +"Obviously, the packing zone needs products ready to be packed. So, an " +"internal transfer is requested to the stock and employees can gather the " +"required products from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the stock and packing" +" zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:333 +msgid "" +"As explained in the introduction of the documentation, the last step in the " +"process (for this route, the delivery order) is the first to be triggered, " +"which then triggers other rules until we reach the first step in the process" +" (here, the internal transfer from the stock to the packing area). Now, " +"everything is ready to be processed so the customer can get the ordered " +"items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:338 +msgid "" +"In this example, the product is delivered to the customer when all the rules" +" have been triggered and the transfers are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the transfers' statuses when the route is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:5 +msgid "" +"For companies that use multiple warehouses, it is often necessary to " +"transfer items between them. This is referred to as an *inter-warehouse " +"transfer*. Odoo *Inventory* handles the administrative process of inter-" +"warehouse transfers to ensure that inventory counts remain accurate during " +"and after the transfer. This document will detail the method for conducting " +"an inter-warehouse transfer using replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:14 +msgid "" +"First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by " +"navigating to :menuselection:`Inventory --> Configuration --> Settings`, and" +" then check the box under the :guilabel:`Warehouse` tab. This will provide " +"additional configuration options when creating a second warehouse that are " +"needed for inter-warehouse replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:19 +msgid "" +"By default, Odoo comes with a main warehouse already configured. If an " +"additional warehouse has not already been created, do so now from the " +":guilabel:`Inventory` module by selecting :menuselection:`Configuration --> " +"Warehouses --> Create`. Otherwise, select the warehouse that products will " +"be transferred to from the :guilabel:`Warehouses` page and then click " +":guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:25 +msgid "" +":guilabel:`Warehouse`: choose a name that is not already being used for " +"another warehouse (e.g. `Alternative Warehouse`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:27 +msgid "" +":guilabel:`Short Name`: choose a short name by which the warehouse will be " +"identified (e.g. `ALT_WH`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:30 +msgid "" +"Click :guilabel:`Save` and the new warehouse will be created. In addition, a" +" new :guilabel:`Resupply From` field will appear on the warehouse's form. " +"Click :guilabel:`Edit` and then check the box next to the warehouse that " +"will be used to resupply the warehouse that is currently being configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "" +"A warehouse settings form configured to allow resupplying between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:39 +msgid "" +"For the purposes of this demonstration, the warehouse that products are " +"transferred from (outgoing) will be titled \"San Francisco\", and the " +"warehouse that products are transferred to (incoming) will be titled \"San " +"Francisco 2\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:46 +msgid "" +"Products must also be configured properly in order for them to be " +"transferred between warehouses. Navigate to :menuselection:`Inventory --> " +"Products --> Products` and select an existing product or :guilabel:`Create` " +"a new one, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:50 +msgid "" +"Then, on the product form, go to the :guilabel:`Inventory` tab and enable " +"the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the " +"warehouse receiving the transferred products and *Y* being the warehouse " +"that products are transferred from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "Enable the checkbox to resupply one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:61 +msgid "" +"Starting in the :menuselection:`Inventory` module, select " +":menuselection:`Products --> Products` and then choose the product that will" +" be replenished. Click the :guilabel:`Replenish` button on the top left of " +"the product page and fill out the pop-up form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:65 +msgid "" +":guilabel:`Quantity`: the number of units that will be sent to the warehouse" +" being replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:66 +msgid "" +":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to " +"take place" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:68 +msgid "" +":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* " +"being the warehouse to be replenished and *Y* being the warehouse that the " +"product will be transferred from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "The form for replenishing a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:75 +msgid "" +"Click :guilabel:`Confirm` and a delivery order will be created for the " +"outgoing warehouse along with a receipt for the warehouse that will receive " +"the product. Depending on the configuration settings for the outgoing and " +"incoming warehouses, processing delivery orders and receipts will require " +"between one and three steps. This document will detail how to process one-" +"step deliveries and receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:84 +msgid "" +"The first stage of a replenishment order is processing the delivery from the" +" warehouse that the product is being transferred from. On the " +":menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` " +"button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, " +"then the delivery order created for the replenishment. On the delivery order" +" page, click the :guilabel:`Check Availability` button in the top left to " +"reserve the quantity of the product to be transferred. Once the delivery has" +" been dispatched, click the :guilabel:`Validate` button to register the " +"quantities shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "The delivery orders card for the outgoing warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 +msgid "" +"Once the goods arrive at the incoming warehouse, the receipt created for " +"that warehouse must be processed as well. Return to the " +":menuselection:`Inventory` dashboard and select the :guilabel:`X to Process`" +" button on the :guilabel:`Receipts` card for the incoming warehouse, then " +"the receipt created for the replenishment. On the receipt page, click the " +":guilabel:`Validate` button in the top left of the page to register the " +"quantities received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:109 +msgid "" +"After processing the receipt, the products transferred will now appear in " +"the inventory of the incoming warehouse. The stock numbers for both " +"warehouses can be viewed by returning to the product page and selecting the " +":guilabel:`X Units On Hand` button at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:116 +msgid "" +"Using reordering rules, it is possible to automate the process of " +"replenishing one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:119 +msgid "" +"To get started, navigate to :menuselection:`Inventory --> Products --> " +"Products`, and then choose the product that will be replenished. From the " +"product page, select the :guilabel:`Reordering Rules` smart button at the " +"top of the form, and then on the next page, click :guilabel:`Create` to " +"configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:124 +msgid "" +":guilabel:`Location`: the location that the reordering rule will replenish " +"when triggered, in this case, the incoming warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:126 +msgid "" +":guilabel:`Min Quantity`: when the quantity on hand at the incoming " +"warehouse falls below this number, the reordering rule will be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:128 +msgid "" +":guilabel:`Max Quantity`: when the reordering rule is triggered, the product" +" will be replenished at the incoming warehouse up to this quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:130 +msgid "" +":guilabel:`Multiple Quantity`: specify if the product should be replenished " +"in batches of a certain quantity; for example, a product could be " +"replenished in batches of 20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:132 +msgid "" +":guilabel:`UoM`: the unit of measure used for reordering the product; this " +"value can simply be `Units`, or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "A fully configured reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:139 +msgid "" +"Finish by clicking :guilabel:`Save` and the reordering rule will be created." +" Now, when the scheduler runs automatically each day, a transfer will be " +"created for each reordering rule that has been triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:144 +msgid "" +"To manually trigger reordering rules, start from the " +":menuselection:`Inventory` module and select :menuselection:`Operation --> " +"Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the" +" pop-up that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:148 +msgid "" +"After the scheduler runs, a delivery order and receipt will be created for " +"the outgoing and incoming warehouses, respectively. Both the delivery order " +"and receipt should be processed using the same method as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:3 +msgid "Manage Warehouses and Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:9 +msgid "Warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:11 +msgid "" +"In Odoo, a **Warehouse** is the actual building/place in which a company's " +"items are stocked. Multiple warehouses can be set up in Odoo and the user " +"can create moves between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:19 +msgid "" +"A **Location** is a specific space within the warehouse. It can be a " +"sublocation of the warehouse (a shelf, a floor, an aisle, and so on). " +"Therefore, a location is part of one warehouse only and it is not possible " +"to link one location to multiple warehouses. In Odoo, as many locations can " +"be configured as needed under one warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:24 +msgid "There are three types of locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:26 +msgid "" +"The **Physical Locations** are internal locations that are part of the " +"warehouses that the company owns. They can be the loading and unloading " +"areas of the warehouse, a shelf, a department, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:30 +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 they are not owned by the user's company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:34 +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 recording lost products (**Inventory " +"Loss**), or accounting for products that are on their way to the warehouse " +"(**Procurements**)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:39 +msgid "" +"In Odoo, locations are structured hierarchically. Locations can be " +"structured as a tree, dependent on a parent-child relationship. This gives " +"more detailed levels of analysis of the stock operations and the " +"organization of the warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 +msgid "" +"To activate locations, go to :menuselection:`Configuration --> Settings` and" +" enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Enable the storage location feature in Odoo Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:54 +msgid "" +"To manage several routes within the warehouses, also enable " +":guilabel:`Multi-Step Routes` and check " +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:60 +msgid "" +"To create a warehouse, go to :menuselection:`Configuration --> Warehouse " +"Management --> Warehouses` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:63 +msgid "" +"Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. " +"The short name is five characters maximum." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Short name field of a warehouse on Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:71 +msgid "" +"The :guilabel:`Short Name` appears on transfer orders and other warehouse " +"documents. Odoo recommends using an understandable one like \"WH/[first " +"letters of location]\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:74 +msgid "" +"Now, go back to the :guilabel:`Inventory` dashboard. There, new operations " +"related to the newly created warehouse have been automatically generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "" +"Inventory app dashboard displaying new transfer types for the recently " +"created warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:82 +msgid "" +"Adding a second warehouse will automatically activate the " +":guilabel:`Locations` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:85 +msgid "Create a new location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:87 +msgid "" +"To create a location, go to :menuselection:`Configuration --> Warehouse " +"Management --> Locations` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:90 +msgid "" +"Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location`" +" and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Create a new warehouse location in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 +msgid "Inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:3 +msgid "Integrating additional costs to products (landed costs)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:7 +msgid "" +"The landed cost feature in Odoo allows the user to include additional costs " +"(shipment, insurance, customs duties, etc.) into the cost of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:13 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings --> " +"Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also " +"gives the option to set a :guilabel:`Default Journal` in which the landed " +"costs accounting entries will be recorded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Activate the landed cost feature in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:22 +msgid "Add costs to products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:25 +msgid "Receive the vendor bill" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:27 +msgid "" +"After a vendor fulfills a purchase order and sends a bill, click " +":guilabel:`Create Bill` on the purchase order to create a vendor bill in " +"Odoo. If the vendor bill includes landed costs, such as custom duties, tick " +"the box in the :guilabel:`Landed Costs` column on the vendor bill invoice " +"line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Enable Landed Costs option on vendor bill line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:35 +msgid "" +"For charges that are always landed costs, create a landed cost product in " +"Odoo. That way, the landed cost product can be quickly added to the vendor " +"bill as an invoice line instead of manually entering the landed cost " +"information every time a vendor bill comes in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:39 +msgid "" +"First, create a new product in :menuselection:`Inventory --> Products --> " +"Products --> Create`. Next, name the landed cost product. Then, set the " +":guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must " +"always be a service product type. After that, go to the :guilabel:`Purchase`" +" tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click " +":guilabel:`Save` to finish creating the landed cost product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:45 +msgid "" +"If this product is always a landed cost, you can also define it on the " +"product and avoid having to tick the box on each vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Option to define a product as a landed cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:52 +msgid "" +"Once the landed cost is added to the vendor bill (either by checking the " +":guilabel:`Landed Cost` option on the invoice line or adding a landed cost " +"product to the bill), click the :guilabel:`Create Landed Costs` button at " +"the top of the bill. Odoo automatically creates a landed cost record with " +"the set landed cost pre-filled in the :guilabel:`Additional Costs` product " +"lines. From here, decide which picking the additional costs apply to by " +"clicking :guilabel:`Edit` and selecting the picking reference number from " +"the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "" +"Use a warehouse transfer to cover a landed cost in the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:64 +msgid "" +"After setting the picking, click :guilabel:`Compute` on the landed cost " +"record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the " +"impact of the landed costs. Finally, click :guilabel:`Validate` to post the " +"landed cost entry to the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:68 +msgid "" +"The user can access the journal entry that has been created by the landed " +"cost by clicking on the :guilabel:`Journal Entry`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:72 +msgid "" +"The product that the landed cost is applied to must have a product category " +"set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average " +"Costing)` method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Landed cost journal entry" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 +msgid "" +"Landed cost records can also be directly created in " +":menuselection:`Inventory --> Operations --> Landed Costs`, it is not " +"necessary to create a landed cost record from the vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:3 +msgid "Inventory valuation configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:7 +msgid "" +"All of a company's stock on-hand contributes to the valuation of its " +"inventory. That value should be reflected in the company's accounting " +"records to accurately show the value of the company and all of its assets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:11 +msgid "" +"By default, Odoo uses a periodic inventory valuation (also known as manual " +"inventory valuation). This method implies that the accounting team posts " +"journal entries based on the physical inventory of the company, and that " +"warehouse employees take the time to count the stock. In Odoo, this method " +"is reflected inside each product category, where the :guilabel:`Costing " +"Method` field will be set to `Standard Price` by default, and the " +":guilabel:`Inventory Valuation` field will be set to `Manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst-1 +msgid "" +"The Inventory Valuation fields are located on the Product Categories form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:22 +msgid "" +"Alternatively, automated inventory valuation is an integrated valuation " +"method that updates the inventory value in real-time by creating journal " +"entries whenever there are stock moves initiated between locations in a " +"company's inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:27 +msgid "" +"Automated inventory valuation is a method recommended for expert " +"accountants, given the extra steps involved in journal entry configuration. " +"Even after the initial setup, the method will need to be periodically " +"checked to ensure accuracy, and adjustments may be needed on an ongoing " +"basis depending on the needs and priorities of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:35 +msgid "Types of accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:37 +msgid "" +"Accounting entries will depend on the accounting mode: *Continental* or " +"*Anglo-Saxon*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 +msgid "" +"Verify the accounting mode by activating the :ref:`developer-mode` and " +"navigating to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:43 +msgid "" +"In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported " +"when products are sold or delivered. This means that the cost of a good is " +"only recorded as an expense when a customer is invoiced for a product. " +"*Interim Stock Accounts* are used for the input and output accounts, and are" +" both *Asset Accounts* in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:48 +msgid "" +"In *Continental* accounting, the cost of a good is reported as soon as a " +"product is received into stock. Additionally, a single *Expense* account is " +"used for both input and output accounts in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:55 +msgid "Costing methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:57 +msgid "" +"Below are the three costing methods that can be used in Odoo for inventory " +"valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 +msgid "" +"**Standard Price**: is the default costing method in Odoo. The cost of the " +"product is manually defined on the product form, and this cost is used to " +"compute the valuation. Even if the purchase price on a purchase order " +"differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:63 +msgid "" +"**Average Cost (AVCO)**: calculates the valuation of a product based on the " +"average cost of that product, divided by the total number of available stock" +" on-hand. With this costing method, inventory valuation is *dynamic*, and " +"constantly adjusts based on the purchase price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 +msgid "" +"**First In First Out (FIFO)**: tracks the costs of incoming and outgoing " +"items in real-time and uses the real price of the products to change the " +"valuation. The oldest purchase price is used as the cost for the next good " +"sold until an entire lot of that product is sold. When the next inventory " +"lot moves up in the queue, an updated product cost is used based on the " +"valuation of that specific lot. This method is arguably the most accurate " +"inventory valuation method for a variety of reasons, however, it's highly " +"sensitive to input data and human error." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:74 +msgid "" +"Changing the costing method greatly impacts inventory valuation. It's highly" +" recommended to consult an accountant first before making any adjustments " +"here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 +msgid "Configure automated inventory valuation in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:80 +msgid "" +"Make changes to inventory valuation options by navigating to " +":menuselection:`Inventory --> Configuration --> Product Categories`, and " +"choose the category/categories where the automated valuation method should " +"apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 +msgid "" +"It is possible to use different valuation settings for different product " +"categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:87 +msgid "" +"Under the :guilabel:`Inventory Valuation` heading are two labels: " +":guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the " +"desired :guilabel:`Costing Method` using the drop-down menu (e.g. " +":guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First " +"In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to " +":guilabel:`Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:93 +msgid "" +":ref:`Using the inventory " +"valuation`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +msgid "" +"When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing " +"Method`, changing the numerical value in the :guilabel:`Cost` field for " +"products in the respective product category creates a new record in the " +"*Inventory Valuation* report to adjust the value of the product. The " +":guilabel:`Cost` amount will then automatically update based on the average " +"purchase price both of inventory on hand and the costs accumulated from " +"validated purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 +msgid "" +"When the :guilabel:`Costing Method` is changed, products already in stock " +"that were using the :guilabel:`Standard` costing method **do not** change " +"value; rather, the existing units keep their value, and any product moves " +"from then on affect the average cost, and the cost of the product will " +"change. If the value in the :guilabel:`Cost` field on a product form is " +"changed manually, Odoo will generate a corresponding record in the " +"*Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 +msgid "" +"On the same screen, the :guilabel:`Account Stock Properties` fields will " +"appear, as they are now required fields given the change to automated " +"inventory valuation. These accounts are defined as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 +msgid "" +":guilabel:`Stock Valuation Account`: when automated inventory valuation is " +"enabled on a product, this account will hold the current value of the " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 +msgid "" +":guilabel:`Stock Input Account`: counterpart journal items for all incoming " +"stock moves will be posted in this account, unless there is a specific " +"valuation account set on the source location. This is the default value for " +"all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:118 +msgid "" +":guilabel:`Stock Output Account`: counterpart journal items for all outgoing" +" stock moves will be posted in this account, unless there is a specific " +"valuation account set on the destination location. This is the default value" +" for all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:124 +msgid "Access reporting data generated by inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 +msgid "" +"To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`." +" At the top of the dashboard, change the :guilabel:`As of` field value to " +":guilabel:`Today`, and adjust the filtering :guilabel:`Options` to " +":guilabel:`Unfold All` in order to see all of the latest data displayed, all" +" at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +msgid "" +"Under the parent :guilabel:`Current Assets` line item, look for the nested " +":guilabel:`Stock Valuation Account` line item, where the total valuation of " +"all of the inventory on hand is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +msgid "" +"Access more specific information with the :guilabel:`Stock Valuation " +"Account` drop-down menu, by selecting either the :guilabel:`General Ledger` " +"to see an itemized view of all of the journal entries, or by selecting " +":guilabel:`Journal Items` to review all of the individualized journal " +"entries that were submitted to the account. As well, annotations to the " +":guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, " +"filling in the text box, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst-1 +msgid "See the full inventory valuation breakdown in Odoo Accounting app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:3 +msgid "Using inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:7 +msgid "" +"*Inventory valuation* is a quintessential accounting procedure that " +"calculates the value of on-hand stock. Once determined, the inventory " +"valuation amount is then incorporated into a company's overall value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:11 +msgid "" +"In Odoo, this process can be conducted manually— by warehouse employees " +"physically counting the products— or automatically through the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:15 +msgid "Automatic inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:17 +msgid "" +"To use Odoo to automatically generate a trail of inventory valuation " +"entries, first navigate to the :menuselection:`Product Categories` list by " +"going to :menuselection:`Inventory app --> Configuration --> Product " +"Categories` and select the desired product category. On the form, set the " +":guilabel:`Inventory Valuation` as :guilabel:`Automated` and the " +":guilabel:`Costing Method` to any of the three options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:24 +msgid "" +":ref:`Set up inventory valuation " +"`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:26 +msgid "" +"In order to understand how moving products in and out of stock affects the " +"company's overall value, consider the following product and stock moves " +"scenario below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:30 +msgid "Receive a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:32 +msgid "" +"To track the value of incoming products, such as a simple *table*, configure" +" the product category on the the product itself. To get there, navigate to " +":menuselection:`Inventory app --> Products --> Products` and click the " +"desired product. On the product form, click the :guilabel:`➡️ (right arrow)`" +" icon beside the :guilabel:`Product Category` field, which opens an internal" +" link to edit the product category. Next, set the :guilabel:`Costing Method`" +" as :guilabel:`First In First Out (FIFO)` and :guilabel:`Inventory " +"Valuation` as :guilabel:`Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:40 +msgid "" +"Alternatively access the :guilabel:`Product Categories` dashboard by " +"navigating to :menuselection:`Inventory app --> Configuration --> Product " +"Categories` and select the desired product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:44 +msgid "" +"Next, assume 10 tables are purchased at a price of $10.00, each. The " +":abbr:`PO (Purchase Order)` for those tables will show the subtotal of the " +"purchase as $100, plus any additional costs or taxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Purchase order with 10 tables products valued at $10.00 each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:51 +msgid "" +"After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, the" +" :guilabel:`Valuation` smart button is enabled. Clicking on this button " +"displays a report showing how the inventory valuation for the table was " +"affected by this purchase." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:56 +msgid "" +":ref:`Developer mode ` **must** be turned on to see the " +":guilabel:`Valuation` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:60 +msgid "" +"The :doc:`consignment " +"`" +" feature allows ownership to items in stock. Thus, products owned by other " +"companies are not accounted for in the host company's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "See Valuation smart button on a receipt, with Developer mode enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:68 +msgid "" +"For a comprehensive dashboard that includes the inventory valuation of all " +"product shipments, inventory adjustments, and warehouse operations, refer to" +" the :ref:`stock valuation report `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:73 +msgid "Deliver a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:75 +msgid "" +"In the same logic, when a table is shipped to a customer and leaves the " +"warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart " +"button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock " +"valuation record as it does on a :abbr:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Decreased stock valuation after a product is shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:86 +msgid "Inventory valuation report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:88 +msgid "" +"To view the current value of all products in the warehouse, first turn on " +":ref:`Developer mode ` and navigate to " +":menuselection:`Inventory app --> Reporting --> Valuation`. The " +":guilabel:`Stock Valuation` dashboard displays detailed records of products " +"with the :guilabel:`Date`, :guilabel:`Quantity`, :guilabel:`Unit Value`, and" +" :guilabel:`Total Value` of the inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:95 +msgid "" +":ref:`Developer mode ` **must** be enabled to see the " +":guilabel:`Valuation` option under :guilabel:`Reporting`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Inventory valuation report showing multiple products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:102 +msgid "" +"The :guilabel:`Valuation At Date` button, located in the top-left corner of " +"the :guilabel:`Stock Valuation` page, reveals a pop-up window. In this pop-" +"up, the inventory valuation of products available during a prior specified " +"date can be seen and selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:107 +msgid "" +"View a detailed record of a product's inventory value, stock move, and on-" +"hand stock by selecting the teal :guilabel:`➡️ (right arrow)` button to the " +"right of the :guilabel:`Reference` column value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:112 +msgid "Update product unit price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:114 +msgid "" +"For any company: lead times, supply chain failures, and other risk factors " +"can contribute to invisible costs. Although Odoo attempts to accurately " +"represent the stock value, *manual valuation* serves as an additional tool " +"to update the unit price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:119 +msgid "" +"Manual valuation is intended for products that can be purchased and received" +" for a cost greater than 0, or have product categories set with " +":guilabel:`Costing Method` set as either :guilabel:`Average Cost (AVCO)` or " +":guilabel:`First In First Out (FIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Add manual valuation of stock value to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:127 +msgid "" +"Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard" +" by first navigating to :menuselection:`Inventory app --> Reporting --> " +"Valuation`. Next, to enable the *product revaluation* feature, select " +":menuselection:`Group by --> Product` to organize all the records by " +"product. Click on the gray :guilabel:`▶️ (drop-down triangle)` icon to " +"reveal stock valuation line items below, as well as a teal :guilabel:`➕ " +"(plus)` button on the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:133 +msgid "" +"Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product" +" Revaluation` form. Here, the inventory valuation for a product can be " +"recalculated, by increasing or decreasing the unit price of each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:138 +msgid "" +"The :guilabel:`▶️ (drop-down triangle)` and :guilabel:`➕ (plus)` buttons are" +" only visible after grouping entries by product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "" +"Product revaluation form adding a value of $1.00 with the reason being " +"inflation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:146 +msgid "Inventory valuation journal entries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:148 +msgid "" +"In Odoo, automatic inventory valuation records are also recorded in the " +":menuselection:`Accounting app --> Accounting --> Journal Entries` " +"dashboard. On this comprehensive list of accounting entries, inventory " +"valuation records are identified by checking values in the " +":guilabel:`Journal` column, or looking for the :guilabel:`Reference` column " +"value which matches the warehouse operation reference (e.g. `WH/IN/00014` " +"for receipts)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:154 +msgid "" +"Clicking on an inventory valuation journal entry opens a *double-entry " +"accounting* record. These records are generated by Odoo to track the change " +"of value in inventory valuation as products are moved in and out of the " +"warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:159 +msgid "" +"To view the inventory valuation of 10 *tables*, costing $10.00 each, upon " +"reception from the vendor, go to the :menuselection:`Journal Entries` page " +"found in :menuselection:`Accounting app --> Accounting --> Journal Entries`." +" Here, click the journal line where the :guilabel:`Reference` column value " +"matches the reference on the receipt, `WH/IN/00014`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Stock valuation page depicting the products within a shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:168 +msgid "" +"`Stock interim` is a holding account for money intended to pay vendors for " +"the product. The `stock valuation` account stores the value of all on-hand " +"stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Accounting entry for the inventory valuation of 10 tables." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:176 +msgid "" +"`Odoo Tutorial: Inventory Valuation " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:8 +msgid "Maintenance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:10 +msgid "" +"**Odoo Maintenance** helps extend the effectiveness of equipment by keeping " +"track of maintenance requirements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:14 +msgid "" +"`Odoo Tutorials: Managing Equipment Maintenance " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management.rst:5 +msgid "Equipment management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:3 +msgid "Add new equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:7 +msgid "" +"In Odoo, *equipment* refers to any item that is used in everyday operations," +" including the manufacturing of products. This can mean a piece of machinery" +" on a production line, a tool that is used in different locations, or a " +"computer in an office space. Equipment registered in Odoo can be owned by " +"the company that uses the Odoo database, or by a third party, such as a " +"vendor in the case of equipment rentals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:13 +msgid "" +"Using Odoo *Maintenance*, it is possible to track individual pieces of " +"equipment, along with information about their maintenance requirements. To " +"add a new piece of equipment, navigate to the :guilabel:`Maintenance` " +"module, select :menuselection:`Equipments --> Machines & Tools --> Create`, " +"and configure the equipment as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:18 +msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:19 +msgid "" +":guilabel:`Equipment Category`: the category that the equipment belongs to; " +"for example, computers, machinery, tools, etc.; new categories can be " +"created by navigating to :menuselection:`Configuration --> Equipment " +"Categories` and clicking :guilabel:`Create`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:22 +msgid "" +":guilabel:`Company`: the company that owns the equipment; again, this can be" +" the company that uses the Odoo database, or a third-party company" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:24 +msgid "" +":guilabel:`Used By`: specify if the equipment is used by a specific " +"employee, department, or both; select :guilabel:`Other` to specify both an " +"employee and a department" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:26 +msgid "" +":guilabel:`Maintenance Team`: the team responsible for servicing the " +"equipment; new teams can be created by navigating to " +":menuselection:`Configuration --> Maintenance Teams` and selecting " +":guilabel:`Create`; the members of each team can also be assigned from this " +"page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:29 +msgid "" +":guilabel:`Technician`: the person responsible for servicing the equipment; " +"this can be used to assign a specific individual in the event that no " +"maintenance team is assigned or when a specific member of the assigned team " +"should always be responsible for the equipment; any person added to Odoo as " +"a user can be assigned as a technician" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:33 +msgid "" +":guilabel:`Used in location`: the location where the equipment is used; this" +" is a simple text field that can be used to specify locations that are not " +"work centers, like an office, for example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:36 +msgid "" +":guilabel:`Work Center`: if the equipment is used at a work center, specify " +"it here; equipment can also be assigned to a work center by navigating to " +":menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a " +"work center or creating a new one using the :guilabel:`Create` button, and " +"clicking the :guilabel:`Equipment` tab on the work center form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "An example of a fully configured new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:46 +msgid "Include additional product information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:48 +msgid "" +"The :guilabel:`Product Information` tab at the bottom of the form can be " +"used to provide further details about the piece of equipment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:51 +msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:52 +msgid "" +":guilabel:`Vendor Reference`: the reference code assigned to the vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:53 +msgid ":guilabel:`Model`: the specific model of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:54 +msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:55 +msgid "" +":guilabel:`Effective Date`: the date that the equipment became available for" +" use; this is used to calculate the :abbr:`MTBF (Mean Time Between " +"Failures)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:57 +msgid ":guilabel:`Cost`: the amount the equipment was purchased for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:58 +msgid "" +":guilabel:`Warranty Expiration Date`: the date on which the equipment's " +"warranty will expire" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "The product information tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:65 +msgid "Add maintenance details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:67 +msgid "" +"The :guilabel:`Maintenance` tab includes information that can be useful to " +"maintenance teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 +msgid "" +":guilabel:`Preventive Maintenance Frequency`: specifies how often " +"maintenance should be performed to prevent equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:71 +msgid "" +":guilabel:`Maintenance Duration`: the amount of time required to fix the " +"equipment when it fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:72 +msgid "" +":guilabel:`Expected Mean Time Between Failure`: the average amount of time " +"that the equipment is expected to operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "The maintenance tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:80 +msgid "" +"The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean " +"Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest" +" Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated " +"automatically based on maintenance requests if any exist." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:86 +msgid "" +"To see the maintenance requests for a piece of equipment, go to the page for" +" the equipment and select :guilabel:`Maintenance` in the top right corner of" +" the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 +msgid "Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:10 +msgid "" +"**Odoo Manufacturing** helps manufacturers schedule, plan, and process " +"manufacturing orders. With the work center control panel, put tablets on the" +" shop floor to control work orders in real-time and allow workers to trigger" +" maintenance operations, feedback loops, quality issues, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 +msgid "`Odoo Tutorials: MRP `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 +msgid "" +"`Odoo Tutorials: Barcode Scanner `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:17 +msgid ":doc:`IoT Boxes (MES) `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 +msgid "Manufacturing workflows" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 +msgid "Bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:7 +msgid "" +"A *bill of materials* (or *BoM* for short) is a document that defines the " +"quantity of each component required to make or deliver a finished product. " +"It can also include various operations and the individual step guidelines " +"needed to complete a production process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:11 +msgid "" +"In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be " +"linked to each product, so even product variants can have their own tailored" +" :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:14 +msgid "" +"Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the " +"manufacturing process and save time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 +msgid "Set up a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:20 +msgid "" +"The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations" +" or instructions, only components. In this case, the production is solely " +"managed using *Manufacturing Orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:23 +msgid "" +"To create a :abbr:`BoM (Bill of Materials)` from the " +":guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills " +"of Materials`. Then, click :guilabel:`Create`. Next, specify the " +":guilabel:`Product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:28 +msgid "" +"A :abbr:`BoM (Bill of Materials)` can also be created directly from the " +"product form, in which case the :guilabel:`Product` field is pre-filled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:31 +msgid "" +"For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type`" +" to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line`" +" to specify the various components that make up the production of the final " +"product and their respective quantities. New components can be created " +"quickly through the :abbr:`BoM (Bill of Materials)`, or can be created " +"beforehand in :menuselection:`Manufacturing --> Products --> Products --> " +"Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Set up a Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 +msgid "Specify a bill of materials (BoM) for a product variant" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:45 +msgid "" +":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product " +"Variants*, with two setup options available to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:49 +msgid "" +"In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, " +"the product's variant attributes must already be configured on the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:52 +msgid "" +"The first method is to create one :abbr:`BoM (Bill of Materials)` per " +"variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the" +" :guilabel:`Product Variant`. The second method is to create one master " +":abbr:`BoM (Bill of Materials)` that contains all of the components, and " +"specify which variant each component applies to using the :guilabel:`Apply " +"on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Product Variants in the Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 +msgid "Set up operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:64 +msgid "" +"Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify" +" instructions for production and register time spent on an operation. To use" +" this feature, first enable the :guilabel:`Work Orders` feature in " +":menuselection:`Manufacturing --> Configuration --> Settings --> " +"Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:69 +msgid "" +"Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the " +":guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new " +"operation. In the :guilabel:`Create Operations` box, give the operation a " +"name, specify the :guilabel:`Work Center` and duration settings. Like " +"components, Odoo gives the option to specify a product variant in the " +":guilabel:`Apply on Variants` field so the operation only applies to that " +"variant. Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:76 +msgid "" +"Each operation is unique, as it is always exclusively linked to one " +":abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a" +" new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing " +"Operations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Copy Existing Operations feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 +msgid "Add by-products to a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 +msgid "" +"A *By-Product* is a residual product that is created during production in " +"addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike " +"the primary product, there can be more than one by-product on a :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:91 +msgid "" +"To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the " +":guilabel:`By-Products` feature in :menuselection:`Manufacturing --> " +"Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:94 +msgid "" +"Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill " +"of Materials)` by clicking on the :guilabel:`Operations` tab and clicking " +":guilabel:`Add a line`. Then, name the by-product and indicate the " +":guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM " +"(Bill of Materials)` has configured operations, specify exactly which " +"operation the by-product is produced from in the :guilabel:`Produced in " +"Operation` field. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:3 +msgid "Manufacturing product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:8 +msgid "" +"In order to manufacture a product in Odoo *Manufacturing*, the product must " +"be properly configured. Doing so consists of enabling the *Manufacturing* " +"route and configuring a bill of materials (BoM) for the product. Once these " +"steps are completed, the product is selectable when creating a new " +"manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:14 +msgid "Activate the Manufacture route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:16 +msgid "" +"The Manufacture route is activated for each product on its own product page." +" To do so, begin by navigating to :menuselection:`Manufacturing --> Products" +" --> Products`. Then, select an existing product, or create a new one by " +"clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:20 +msgid "" +"On the product page, select the :guilabel:`Inventory` tab, then enable the " +":guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This " +"tells Odoo the product can be manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Manufacturing route on the Inventory tab of a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:28 +msgid "Configure a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:30 +msgid "" +"Next, a |BOM| must be configured for the product so Odoo knows how it is " +"manufactured. A |BOM| is a list of the components and operations required to" +" manufacture a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:33 +msgid "" +"To create a |BOM| for a specific product, navigate to " +":menuselection:`Manufacturing --> Products --> Products`, then select the " +"product. On the product page, click the :guilabel:`Bill of Materials` smart " +"button at the top of the page, then select :guilabel:`New` to configure a " +"new |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Bill of Materials smart button on a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:41 +msgid "" +"On the |BOM|, the :guilabel:`Product` field auto-populates with the product." +" In the :guilabel:`Quantity` field, specify the number of units that the BoM" +" produces." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:44 +msgid "" +"Add a component to the |BOM| by selecting the :guilabel:`Components` tab and" +" clicking :guilabel:`Add a line`. Select a component from the " +":guilabel:`Component` drop-down menu, then enter the quantity in the " +":guilabel:`Quantity` field. Continue adding components on new lines until " +"all components have been added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Components tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:53 +msgid "" +"Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` " +"and a :guilabel:`Create Operations` pop-up window appears. In the " +":guilabel:`Operation` field, specify the name of the operation being added " +"(e.g. Assemble, Cut, etc.). Select the work center where the operation will " +"be carried out from the :guilabel:`Work Center` drop-down menu. Finally, " +"click :guilabel:`Save & Close` to finish adding operations, or " +":guilabel:`Save & New` to add more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:60 +msgid "" +"The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` " +"setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> " +"Configuration --> Settings`, then enable the :guilabel:`Work Orders` " +"checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Operations tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:70 +msgid "" +"The section above provides instructions for creating a basic |BOM| that " +"allows a product to be manufactured in Odoo. However, it is by no means an " +"exhaustive summary of all the options available when configuring a |BOM|. " +"For more information about bills of materials, see the documentation on how " +"to :ref:`create a bill of materials `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 +msgid "Use kits" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5 +msgid "" +"In Odoo, a *kit* is a type of bill of materials (BoM) that can be " +"manufactured and sold. Kits are sets of unassembled components sold to " +"customers. They may be sold as standalone products, but are also useful " +"tools for managing more complex bills of materials (BoMs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10 +msgid "" +"To use, manufacture, and sell kits, both the :guilabel:`Manufacturing` and " +":guilabel:`Inventory` apps need to be installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:14 +msgid "Create the kit as a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16 +msgid "" +"To use a kit as a sellable product, or simply as a component organization " +"tool, the kit should first be created as a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:19 +msgid "" +"To create a kit product, go to :menuselection:`Inventory app --> Products " +"--> Products`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22 +msgid "" +"Then, assign a name to the new kit product. Next, under the " +":guilabel:`General Information` tab, set the :guilabel:`Product Type` to " +":guilabel:`Consumable`. Kit products work best as consumables, because the " +"stock on-hand for kits is typically not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:27 +msgid "" +"Although kits should almost always be set to :guilabel:`Consumable`, " +"companies using **Anglo-Saxon** accounting might need to create kits as a " +":guilabel:`Storable Product`. This is because when processing invoices for " +"kits, the Cost of Goods Sold (COGS) will be posted in accounting journals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:32 +msgid "" +"Unlike storable products, the :guilabel:`Routes` designation under the " +":guilabel:`Inventory` tab does not matter for kits, since Odoo uses the " +"routes of the kit's individual components for replenishment purposes. All " +"other parameters for the kit product may be modified according to " +"preference. Once ready, click :guilabel:`Save` to save the new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:37 +msgid "" +"The kit's components must also be configured as products via " +":menuselection:`Inventory app --> Products --> Products`. These components " +"require no specific configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41 +msgid "Set up the kit BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:43 +msgid "" +"After fully configuring the kit product and its components, a new :abbr:`BoM" +" (bill of materials)` can be created for the kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46 +msgid "" +"To do so, go to :menuselection:`Manufacturing app --> Products --> Bills of " +"Materials`, and click :guilabel:`Create`. Next to the :guilabel:`Product` " +"field, click the drop-down menu to reveal a list of products, and select the" +" previously configured kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:50 +msgid "" +"Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Kit` option." +" Finally, under the :guilabel:`Components` tab, click :guilabel:`Add a " +"line`, and add each desired component, and specify their quantities under " +"the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:54 +msgid "" +"Once ready, click :guilabel:`Save` to save the newly-created :abbr:`BoM " +"(bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit selection on the bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60 +msgid "" +"If the kit is solely being used as a sellable product, then only components " +"need to be added under the :guilabel:`Components` tab, and configuring " +"manufacturing operations is not necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:64 +msgid "" +"When a kit is sold as a product, it appears as a single line item on the " +"quotation and sales order. However, on delivery orders, each component of " +"the kit is listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68 +msgid "Use kits to manage complex BoMs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:70 +msgid "" +"Kits are also used to manage multi-level :abbr:`BoMs (bills of materials)`. " +"These are products that contain **other** :abbr:`BoM (bill of materials)` " +"products as components, and therefore require *nested* :abbr:`BoMs (bills of" +" materials)`. Incorporating pre-configured kits into multi-level :abbr:`BoMs" +" (bills of materials)` allows for cleaner organization of bundled products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:75 +msgid "" +"To configure this type of :abbr:`BoM (bill of materials)` with a kit as a " +"component, go to :menuselection:`Manufacturing app --> Products --> Bills of" +" Materials`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:79 +msgid "" +"Next to the :guilabel:`Product` field, click the drop-down menu to reveal a " +"list of products, and select the desired :abbr:`BoM (bill of materials)` " +"product. Then, for the :guilabel:`BoM Type` field, select the " +":guilabel:`Manufacture this product` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:83 +msgid "" +"Under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and " +"select a kit as the component. Adding the kit as a component eliminates the " +"need to add the kit's components individually. Any :guilabel:`BoM Type` can " +"be used for the higher-level product's :abbr:`BoM (bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:88 +msgid "Once ready, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit as a component in a multilevel bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:95 +msgid "Structure & cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:97 +msgid "" +"To access a comprehensive overview of the multi-level :abbr:`BoM's (bill of " +"material's)` components, click on the :guilabel:`Structure & Cost` smart " +"button. Sublevel :abbr:`BoMs (bills of materials)` can be expanded and " +"viewed from this report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Expanded kit in the Structure and Cost report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:105 +msgid "" +"When creating a manufacturing order for a product with a multi-level " +":abbr:`BoM (bill of materials)`, the kit product automatically expands to " +"show all components. Any operations in the kit's :abbr:`BoM (bill of " +"materials)` are also added to the list of work orders on the manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:111 +msgid "" +"Kits are primarily used to bundle components together for organization or " +"sale. To manage multi-level products that require manufactured sub-" +"components, refer to :doc:`this documentation ` on sub-" +"assemblies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:3 +msgid "Manufacturing backorders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:5 +msgid "" +"In some cases, the full quantity of a manufacturing order cannot be produced" +" immediately. When this happens, Odoo *Manufacturing* allows for the " +"manufacturing of partial quantities of the order and creates a *backorder* " +"for the remaining amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:9 +msgid "" +"In the *Manufacturing* app, creating a backorder splits the original " +"manufacturing order into two orders. The reference tag for each order is the" +" tag used for the original order, followed by a hyphen and then an " +"additional number to indicate that it's a backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:14 +msgid "" +"A company creates a manufacturing order with the reference tag " +"*WH/MO/00175*, for 10 units of *Product X*. After starting work on the " +"manufacturing order, the employee working the production line realizes there" +" are only enough components in stock to produce five units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:18 +msgid "" +"Instead of waiting for additional stock of the components, they manufacture " +"five units and create a backorder for the remaining five. This splits the " +"manufacturing order into two separate orders: *WH/MO/00175-001* and " +"*WH/MO/00175-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:22 +msgid "" +"Order *001* contains the five units that have been manufactured, and is " +"immediately marked as :guilabel:`Done`. Order *002* contains the five units " +"that still need to be manufactured and is marked as :guilabel:`In Progress`." +" Once the remaining components are available, the employee returns to order " +"*002* and manufactures the remaining units before closing the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:28 +msgid "Create a manufacturing backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:30 +msgid "" +"To create a backorder for part of a manufacturing order, begin by navigating" +" to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order with a quantity of two or more or create one by" +" clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:34 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:86 +msgid "" +"If a new manufacturing order is created, select a product from the " +":guilabel:`Product` drop-down menu and enter a quantity of two or more in " +"the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm " +"the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:38 +msgid "" +"After manufacturing the quantity that is being produced immediately, enter " +"that number in the :guilabel:`Quantity` field at the top of the " +"manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The quantity field on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:45 +msgid "" +"Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than " +"initial demand` pop-up window appears, from which a backorder can be " +"created. Click :guilabel:`Create Backorder` to split the manufacturing order" +" into two separate orders, with the reference tags *WH/MO/XXXXX-001* and " +"*WH/MO/XXXXX-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "" +"The Create Backorder button on the \"You produced less than initial demand\"" +" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:54 +msgid "" +"Order *001* contains the items that have been manufactured, and is closed " +"immediately. Order *002* is the backorder that contains the items that have " +"yet to be manufactured, and remains open, to be completed at a later date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:58 +msgid "" +"Once the remaining units can be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select the backorder manufacturing order. If all of the remaining units" +" are manufactured immediately, simply click :guilabel:`Validate` to close " +"the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:63 +msgid "" +"If only some of the remaining units are manufactured immediately, create " +"another backorder for the remainder by following the steps detailed in this " +"section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:67 +msgid "Create a backorder from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:69 +msgid "" +"Backorders for manufacturing orders can also be created from the work order " +"tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:72 +msgid "" +"In order to use tablet view, the *Work Orders* setting must be enabled. To " +"enable it, navigate to :menuselection:`Manufacturing --> Configuration --> " +"Settings`. On the :guilabel:`Settings` page, enable the checkbox next to " +":guilabel:`Work Orders`, then click :guilabel:`Save` to save the change. " +"This makes the :guilabel:`Work Orders` tab appear on manufacturing orders, " +"from which the tablet view can be opened." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:0 +msgid "The Work Orders setting on the Manufacturing settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82 +msgid "" +"To create a backorder from the tablet view, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order with a quantity of two or more or create one by" +" clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:90 +msgid "" +"After confirming the manufacturing order, select the :guilabel:`Work Orders`" +" tab and click the :guilabel:`📱 (tablet view)` button located on the line of" +" the first work order to enter the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The tablet view button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:97 +msgid "" +"Once in tablet view, enter the quantity being manufactured immediately in " +"the :guilabel:`Units` field at the top left of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The Units field in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:104 +msgid "" +"The steps for the rest of the workflow depend on whether the manufacturing " +"order being processed requires the completion of a single work order or " +"multiple work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:108 +msgid "Single work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:110 +msgid "" +"If the manufacturing order only requires the completion of a single work " +"order, complete the work order, then click :guilabel:`Mark As Done And Close" +" MO`. The manufacturing order is closed and a backorder for the units that " +"still need to be manufactured is created automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "" +"The Mark As Done And Close MO button in the tablet view of a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:118 +msgid "" +"Once the remaining units are ready to be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select the backorder manufacturing order, which is titled using the " +"reference tag of the original backorder with *002* added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:122 +msgid "" +"On the backorder manufacturing order, select the :guilabel:`Work Orders` tab" +" and click the :guilabel:`📱 (tablet view)` button located on the line of the" +" work order to open the tablet view. If all of the units in the backorder " +"will be completed immediately, simply click :guilabel:`Mark As Done And " +"Close MO` after completing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:127 +msgid "" +"If only some of the remaining units will be manufactured immediately, enter " +"the number in the :guilabel:`Units` field at the top left of the tablet " +"view, then click :guilabel:`Mark As Done And Close MO` to create another " +"backorder for the remaining units. The new backorder can be processed using " +"the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:133 +msgid "Multiple work orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:135 +msgid "" +"If the manufacturing order requires the completion of multiple work orders, " +"complete the first work order, and then click :guilabel:`Record Production`." +" This splits the manufacturing order into two separate orders, titled " +"*WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*, with *XXXXX* being the number of " +"the original order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The Record Production button on a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:144 +msgid "" +"The tablet view defaults to showing the first work order for the *002* " +"manufacturing order. Since this manufacturing order will not be completed " +"immediately, back out of tablet view by clicking the :guilabel:`⬅️ (back)` " +"button twice. Doing so will take you to the *001* order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:148 +msgid "" +"To finish the *001* order, select the :guilabel:`Work Orders` tab and click " +"the :guilabel:`tablet view` button located on the line of the next work " +"order. Finally, complete the remaining work orders, then click " +":guilabel:`Mark As Done And Close MO` to close the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:152 +msgid "" +"Once the remaining units are ready to be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select the *002* order. Select the :guilabel:`Work Orders` tab and click " +"the :guilabel:`tablet view` button located on the line of the first work " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:157 +msgid "" +"If all of the units in the backorder will be completed immediately, simply " +"click :guilabel:`Mark As Done And Close MO` after completing all of the work" +" orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:160 +msgid "" +"If only some of the remaining units will be manufactured immediately, enter " +"the number in the :guilabel:`Units` field at the top left of the tablet " +"view, then click :guilabel:`Record Production` to create an additional " +"backorder for the remaining units, with *003* at the end of its reference " +"tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:165 +msgid "" +"The *002* backorder and *003* backorder can be completed by following the " +"steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:169 +msgid "" +"It is also possible to create a backorder in the middle of a manufacturing " +"order, when some but not all of the work orders have already been completed." +" Doing so marks the completed work order(s) as :guilabel:`Finished` on the " +"backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:174 +msgid "" +"A manufacturing order for four chairs requires the completion of two work " +"orders: *Paint* and *Assemble*. While the paint step can be completed " +"immediately for all four chairs, there are only enough screws to assemble " +"two of them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:178 +msgid "" +"As a result, the employee responsible for producing the chairs begins by " +"painting all four, and marking the *Paint* work order as " +":guilabel:`Finished` for all of them. Then, they move on to the *Assemble* " +"work order. They assemble two of the four chairs, enter that number in the " +":guilabel:`Units` field of the tablet view, and click :guilabel:`Record " +"Production`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:183 +msgid "" +"A backorder manufacturing order is created for the remaining two chairs. On " +"the backorder, the *Paint* work order is already marked as " +":guilabel:`Finished`, and only the *Assemble* work order is left to be " +"completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:187 +msgid "" +"Once more screws are available, the manufacturing employee assembles the " +"remaining chairs and clicks :guilabel:`Mark As Done And Close MO` to " +"complete the *Assemble* work order and close the backorder manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:3 +msgid "One-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using one-step manufacturing, Odoo creates a " +"manufacturing order (MO), but does not generate transfers for the movement " +"of components out of inventory or finished products into stock. Inventory " +"counts still update based on the number of components used and products " +"manufactured, but the act of transferring them to and from inventory is not " +"tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:16 +msgid "" +"The number of steps used in manufacturing is set at the warehouse level, " +"allowing for each warehouse to use a different number of steps. To change " +"the number of steps used for a specific warehouse, begin by navigating to " +":menuselection:`Inventory --> Configuration --> Warehouses`, and then select" +" a warehouse from the :guilabel:`Warehouses` screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:20 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:21 +msgid "" +"On the :guilabel:`Warehouse Configuration` tab, find the " +":guilabel:`Manufacture` radio input field, and select one of the three " +"options: :guilabel:`Manufacture (1 step)`, :guilabel:`Pick components and " +"then manufacture (2 steps)`, or :guilabel:`Pick components, manufacture and " +"then store products (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:0 +msgid "The Manufacture radio input field on a warehouse configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:31 +msgid "" +"Products must be properly configured before they can be manufactured in " +"Odoo. For details on how to do so, see the documentation on how to " +":ref:`configure a product for manufacturing " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:36 +msgid "Create manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:38 +msgid "" +"To manufacture a product in Odoo *Manufacturing*, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:42 +msgid "" +"On the new |MO|, select the product to be produced from the " +":guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field " +"auto-populates with the associated bill of materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:45 +msgid "" +"If a product has more than one |BOM| configured for it, the specific |BOM| " +"can be selected in the :guilabel:`Bill of Material` field, and the " +":guilabel:`Product` field auto-populates with the associated product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:49 +msgid "" +"After a |BOM| has been selected, the :guilabel:`Components` and " +":guilabel:`Work Orders` tabs auto-populate with the components and " +"operations specified on the |BOM|. If additional components or operations " +"are required for the |MO| being configured, add them to the " +":guilabel:`Components` and :guilabel:`Work Orders` tabs by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:55 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:80 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:77 +msgid "Process manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:79 +msgid "" +"An |MO| is processed by completing all of the work orders listed under its " +":guilabel:`Work Orders` tab. This can be done on the |MO| itself, or from " +"the work order tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:83 +msgid "Basic workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:85 +msgid "" +"To complete work orders from the |MO| itself, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:91 +msgid "" +"On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins " +"on the first work order that needs to be completed, click the " +":guilabel:`Start` button for that work order. Odoo *Manufacturing* then " +"starts a timer that keeps track of how long the work order takes to " +"complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +msgid "The Start button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:96 +msgid "" +"When the work order is completed, click the :guilabel:`Done` button for that" +" work order. Repeat the same process for each work order listed on the " +":guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +msgid "The Done button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:103 +msgid "" +"After completing all of the work orders, click :guilabel:`Produce All` at " +"the top of the screen to mark the |MO| as :guilabel:`Done`, and register the" +" manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:107 +msgid "Tablet view workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:112 +msgid "" +"To complete the work orders for an |MO| using the tablet view, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:91 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:116 +msgid "" +"Next, click on the :guilabel:`Work Orders` tab, and then select the " +":guilabel:`📱 (tablet)` button on the line of the first work order to be " +"processed. This opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:98 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:119 +msgid "" +"After opening the tablet view, Odoo *Manufacturing* automatically starts a " +"timer that keeps track of how long the work order takes to complete. After " +"completing the work order, click the :guilabel:`Mark as Done` button in the " +"top-right corner of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:102 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:123 +msgid "" +"Clicking :guilabel:`Mark as Done` while there is at least one more work " +"order left to complete opens a page that lists the next work order. Click on" +" that work order to open it in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:105 +msgid "" +"Once the final work order for the |MO| has been reached, a :guilabel:`Mark " +"as Done and Close MO` button appears on the tablet view in addition to the " +":guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO`" +" to mark the |MO| as :guilabel:`Done` and register the manufactured " +"product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:110 +msgid "" +"It is also possible to complete the final operation while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed later by clicking the :guilabel:`Produce All` button on the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 +msgid "Managing BoMs for product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 +msgid "" +"Odoo allows one bill of materials (BoM) to be used for multiple variants of " +"the same product. Having a consolidated :abbr:`BoM (bill of materials)` for " +"a product with variants saves time by preventing the need to manage multiple" +" :abbr:`BoMs (bills of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 +msgid "Activate product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 +msgid "" +"To activate the product variants feature, navigate to " +":menuselection:`Inventory app --> Configuration --> Settings`, and scroll " +"down to the :guilabel:`Products` section. Then, click the checkbox to enable" +" the :guilabel:`Variants` option. After that, click :guilabel:`Save` to " +"apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:17 +msgid "" +"For more information on configuring product variants, refer to the " +":doc:`product variants " +"<../../../sales/sales/products_prices/products/variants>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Selecting \"Variants\" from Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 +msgid "Create custom product attributes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:27 +msgid "" +"Once the product variants feature is activated, create and edit product " +"attributes on the :guilabel:`Attributes` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:30 +msgid "" +"The :guilabel:`Attributes` page is accessible either from " +":menuselection:`Inventory app --> Configuration --> Settings` by clicking " +"the :guilabel:`Attributes` button, or by clicking :menuselection:`Inventory " +"app --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:34 +msgid "" +"Once on the :guilabel:`Attributes` page, either click into an existing " +"attribute, or click :guilabel:`Create` to create a new one. Clicking " +":guilabel:`Create` reveals a new, blank form for customizing an attribute. " +"For an existing attribute, click :guilabel:`Edit` on its form to make " +"changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +msgid "" +"Assign an :guilabel:`Attribute Name`, and choose a category from the " +":guilabel:`Category` field's drop-down menu. Then, select the desired " +"options next to the :guilabel:`Display Type` and :guilabel:`Variants " +"Creation Mode` fields. Once the desired options are selected, click " +":guilabel:`Add a line` under the :guilabel:`Attribute Values` tab to add a " +"new value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:45 +msgid "" +"Included on the :guilabel:`Value` row is a :guilabel:`Is custom value` " +"checkbox. If selected, this value will be recognized as a custom value, " +"which allows customers to type special customization requests upon ordering " +"a custom variant of a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:0 +msgid "Product variant attribute configuration screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:54 +msgid "" +"Once all desired :guilabel:`Values` have been added, click :guilabel:`Save` " +"to save the new attribute." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:58 +msgid "Add product variants on the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:60 +msgid "" +"Created attributes can be applied on specific variants for particular " +"products. To add product variants to a product, navigate to the product form" +" by going to :menuselection:`Inventory app --> Products --> Products`. To " +"make changes to the product, click :guilabel:`Edit`. Then, click the " +":guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:65 +msgid "" +"Under the :guilabel:`Attribute` header, click :guilabel:`Add a line` to add " +"a new attribute, and select one to add from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:68 +msgid "" +"Then, under the :guilabel:`Values` header, click the drop-down menu to " +"choose from the list of existing values. Click on each desired value to add " +"them, and repeat this process for any additional attributes that should be " +"added to the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:72 +msgid "Once finished, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Product form variants tab with values and attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:79 +msgid "" +":abbr:`BoM (bill of materials)` products with multiple variants that are " +"manufactured in-house should either have a **0,0 reordering rule** set up, " +"or have their replenishment routes set to *Replenish on Order (MTO)*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:84 +msgid "Apply BoM components to product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:86 +msgid "" +"Next, create a new :abbr:`BoM (bill of materials)`. Or, edit an existing " +"one, by going to :menuselection:`Manufacturing app --> Products --> Bills of" +" Materials`. Then, click :guilabel:`Create` to open a new :guilabel:`Bills " +"of Materials` form to configure from scratch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:90 +msgid "" +"Add a product to the :abbr:`BoM (bill of materials)` by clicking the drop-" +"down menu in the :guilabel:`Product` field and selecting the desired " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:93 +msgid "" +"Then, add components by clicking :guilabel:`Add a line` under the " +":guilabel:`Component` section of the :guilabel:`Components` tab, and " +"choosing the desired components from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:96 +msgid "" +"Choose the desired values in the :guilabel:`Quantity` and :guilabel:`Product" +" Unit of Measure` columns. Then, choose the desired values in the " +":guilabel:`Apply on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:100 +msgid "" +"The :guilabel:`Apply on Variants` option to assign components to specific " +"product variants on the :abbr:`BoM (bill of materials)` is available once " +"the :guilabel:`Variants` setting is activated from the " +":menuselection:`Inventory` application. If the :guilabel:`Apply on Variants`" +" field is not immediately visible, activate it from the additional options " +"menu (three-dots icon, to the right of the header row)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "\"Apply on Variants\" option on the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:110 +msgid "" +"Each component can be assigned to multiple variants. Components with no " +"variants specified are used in every variant of the product. The same " +"principle applies when configuring operations and by-products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:114 +msgid "" +"When defining variant :abbr:`BoMs (bills of material)` by component " +"assignment, the :guilabel:`Product Variant` field in the main section of the" +" :abbr:`BoM (bill of materials)` should be left blank. This field is *only* " +"used when creating a :abbr:`BoM (bill of materials)` specifically for one " +"product variant." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:119 +msgid "" +"When all desired configurations have been made to the :abbr:`BoM (bill of " +"materials)`, click :guilabel:`Save` at the top of the form to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:123 +msgid "" +"For components that only apply for specific variants, choose which " +"operations the components should be consumed in. If the :guilabel:`Consumed " +"in Operation` column is *not* immediately visible, activate it from the " +"additional options menu (three-dots icon, to the right of the header row)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:129 +msgid "Sell and manufacture variants of BoM products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:131 +msgid "" +"To sell and manufacture variants of :abbr:`BoM (bill of materials)` products" +" to order, navigate to :menuselection:`Sales app --> Create` to create a new" +" quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:135 +msgid "Sell variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:137 +msgid "" +"Once on the blank :guilabel:`Quotation` form, click the drop-down next to " +"the :guilabel:`Customer` field to add a customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:140 +msgid "" +"Then, under the :guilabel:`Order Lines` tab, click :guilabel:`Add a " +"product`, and select the previously-created :abbr:`BoM (bill of materials)` " +"product with variants from the drop-down menu. Doing so reveals a " +":guilabel:`Configure a product` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:144 +msgid "" +"From the pop-up window, click the desired attribute options to configure the" +" correct variant of the product to manufacture. Then, click the green " +":guilabel:`+` or :guilabel:`-` icons next to the `1` to change the quantity " +"to sell and manufacture, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Configure a product pop-up for choosing variant attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:152 +msgid "" +"Once all the specifications have been chosen, click :guilabel:`Add`. This " +"will change the pop-up to a second :guilabel:`Configure` pop-up, where " +"available optional products will appear, if they have been created " +"previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:156 +msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:158 +msgid "" +"Then, click :guilabel:`Save` to save all changes, and click " +":guilabel:`Confirm` at the top of the :guilabel:`Quotation` form to create " +"and confirm a new sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:162 +msgid "Manufacture variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:164 +msgid "" +"Once the :abbr:`SO (sales order)` is confirmed, a :guilabel:`Manufacturing` " +"smart button appears at the top of the :abbr:`SO (sales order)` form. Click " +"the :guilabel:`Manufacturing` smart button to open the " +":guilabel:`Manufacturing Order` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:168 +msgid "" +"On this form, under the :guilabel:`Components` tab, the appropriate " +"components for the chosen variant are listed. And, depending on the variant," +" different components will be listed. To see any mandatory or optional " +":guilabel:`Operation` steps, click the :guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:172 +msgid "" +"To enter the tablet view work order screen, click the :guilabel:`tablet " +"icon` to the right of the row for the desired operation to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:175 +msgid "" +"From the tablet view, click :guilabel:`Mark as Done` as the operation " +"progresses to complete the operation steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:178 +msgid "" +"Alternatively, click the :guilabel:`Mark as Done` button at the top of the " +"manufacturing order form to complete the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Manufacturing order for variant of BoM product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:185 +msgid "" +"Then, navigate back to the :abbr:`SO (sales order)` via the breadcrumbs at " +"the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:187 +msgid "" +"Now that the product has been manufactured, click the :guilabel:`Delivery` " +"smart button to deliver the product to the customer. From the " +":guilabel:`Delivery Order` form, click :guilabel:`Validate`, then click " +":guilabel:`Apply` to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:191 +msgid "" +"To finish the sale, click back to the :abbr:`SO (sales order)` via the " +":guilabel:`breadcrumbs` at the top of the page again. Then, click " +":guilabel:`Create Invoice` followed by :guilabel:`Create Invoice` again to " +"invoice the customer for the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:3 +msgid "Scrap during manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:5 +msgid "" +"During the manufacturing process, the need to scrap manufacturing components" +" or finished products may arise. This can be necessary if a component or " +"product is damaged, or unusable for any other reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:9 +msgid "" +"By default, scrapping a component or finished product removes it from " +"physical inventory and places it in a virtual location titled *Virtual " +"Locations/Scrap*. A virtual location is **not** a physical space, but rather" +" a designation in Odoo that is used to track items that are no longer in " +"physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:14 +msgid "" +"Odoo *Manufacturing* allows for both components and finished products to be " +"scrapped within a manufacturing order. The specific type of item that can be" +" scrapped during a manufacturing order depends on the stage of the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:23 +msgid "" +"To view the total quantity of each item scrapped, navigate to " +":menuselection:`Inventory --> Configuration --> Locations`, then remove the " +":guilabel:`Internal` filter from the :guilabel:`Search...` bar to display " +"all virtual locations. From the list, select the :guilabel:`Virtual " +"Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:29 +msgid "Scrap manufacturing components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:31 +msgid "" +"To scrap components during the manufacturing process, begin by navigating to" +" :menuselection:`Manufacturing --> Manufacturing Orders`, then select a " +"manufacturing order or click :guilabel:`Create` to configure a new one. If a" +" new manufacturing order is created, select a product from the " +":guilabel:`Product` drop-down menu, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:36 +msgid "" +"Once the manufacturing order has been confirmed, a :guilabel:`Scrap` button " +"appears at the top of the page. Click the button and a :guilabel:`Scrap` " +"pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The scrap button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:43 +msgid "" +"From the :guilabel:`Product` drop-down menu on the :guilabel:`Scrap` pop-up " +"window, select the component that is being scrapped, then enter the quantity" +" in the :guilabel:`Quantity` field. Finally, click :guilabel:`Done` to scrap" +" the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The Scrap pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:52 +msgid "" +"Before clicking :guilabel:`Mark As Done` on a manufacturing order, only the " +"components of the finished product can be scrapped, **not** the finished " +"product itself. This is because Odoo recognizes that the finished product " +"cannot be scrapped before it has been manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:56 +msgid "" +"After scrapping a component, continue the manufacturing process using the " +"required quantity of the component that was scrapped. The on-hand stock " +"count for the component that was scrapped updates to reflect both the " +"scrapped quantity and the quantity consumed during manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:61 +msgid "" +"If the manufacturing of a table requires four units of a table leg, and two " +"units of the table leg were scrapped during the manufacturing process, the " +"total quantity of table legs consumed will be six: four units used to " +"manufacture the table plus two units scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:66 +msgid "Scrap components from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:68 +msgid "" +"Components can also be scrapped from the manufacturing tablet view. To do " +"so, select the :guilabel:`Work Orders` tab on a manufacturing order, then " +"click the :guilabel:`📱 (tablet view)` icon for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The tablet view icon for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:76 +msgid "" +"With tablet view open, click the :guilabel:`☰ (menu)` button at the top left" +" of the screen, then select the :guilabel:`Scrap` button on the " +":guilabel:`Menu` pop-up window. The :guilabel:`Scrap` pop-up window then " +"appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "" +"The Scrap button on the Menu pop-up window of the manufacturing tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:84 +msgid "" +"Finally, select a component from the :guilabel:`Product` drop-down menu and " +"enter the quantity being scrapped in the :guilabel:`Quantity` field. Click " +":guilabel:`Done` to scrap the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:88 +msgid "Scrap finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:90 +msgid "" +"Odoo also allows for finished products to be scrapped from a manufacturing " +"order once the order is completed. After clicking :guilabel:`Mark as Done`, " +"click the :guilabel:`Scrap` button to make the :guilabel:`Scrap` pop-up " +"window appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:94 +msgid "" +"Since the components have been consumed to create the finished product, they" +" will no longer appear in the :guilabel:`Product` drop-down menu. Instead, " +"the finished product will be available as an option. Select the finished " +"product and enter the quantity to be scrapped in the :guilabel:`Quantity` " +"field. Click :guilabel:`Done` to scrap the finished product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:99 +msgid "" +"The on-hand stock count for the product that was scrapped will update to " +"reflect both the scrapped quantity and the quantity produced during " +"manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:103 +msgid "" +"If five units of a chair were manufactured, but two units were scrapped " +"after manufacturing was completed, then the on-hand inventory of the chair " +"will increase by three: five units manufactured minus two units scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:3 +msgid "Split and merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:5 +msgid "" +"In Odoo *Manufacturing*, it is possible to create manufacturing orders for a" +" single unit of an item, or multiple units of the same item. In some cases, " +"it may be necessary to split a manufacturing order that contains multiple " +"units into two or more orders, or to merge two or more orders into a single " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:11 +msgid "" +"A manufacturing order can only contain one unit of a product, or multiple " +"units of a single product that all use the same Bill of Materials (BoM). As " +"a result, it is only possible to merge manufacturing orders when every order" +" contains the same product being manufactured with the same BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:17 +msgid "Split manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:19 +msgid "" +"To split a manufacturing order into multiple orders, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select a manufacturing order. At the top of the page, next to the " +":guilabel:`New` button, the manufacturing order's reference number appears " +"with a :guilabel:`⚙️ (settings)` button next to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:24 +msgid "" +"Click the :guilabel:`⚙️ (settings)` button to open the general settings for " +"the manufacturing order, then select :guilabel:`Split`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Settings and Split buttons on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:31 +msgid "" +"After selecting :guilabel:`Split`, a :guilabel:`Split production` pop-up " +"window appears. In the :guilabel:`Split #` field, enter the number of " +"manufacturing orders that the original order should be split into, then " +"click outside of the field. A table appears below, with a line for each new " +"manufacturing order that will be created by the split. In the " +":guilabel:`Quantity To Produce` column, enter the number of units that will " +"be assigned to each new manufacturing order. Finally, click " +":guilabel:`Split` to split the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Split production pop-up window for a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:42 +msgid "" +"After clicking :guilabel:`Split`, the original manufacturing order is split " +"into the number of orders that was specified in the :guilabel:`Split #` " +"field. The reference numbers for the new manufacturing orders are the " +"reference number for the original order with *-###* tags added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:48 +msgid "" +"Manufacturing order *WH/MO/00012* is split into three separate orders. The " +"reference numbers for the new orders are *WH/MO/00012-001*, " +"*WH/MO/00012-002*, and *WH/MO/00012-003*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:52 +msgid "Merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:54 +msgid "" +"To merge two or more manufacturing orders into a single order, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`. Select the manufacturing orders that will be merged by activating " +"the checkbox to the left of the name of each order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "" +"Select manufacturing orders that will be merged by clicking the checkbox for" +" each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:62 +msgid "" +"Once all manufacturing orders have been selected, click the " +":guilabel:`Actions` button at the top of the page, then select " +":guilabel:`Merge` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Actions and Merge buttons on the Manufacturing Orders page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:69 +msgid "" +"The selected manufacturing orders are merged into a single order. The " +"reference number for the new manufacturing order is the next sequential " +"number that has *not* already been assigned to an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:73 +msgid "" +"The last reference number used for a manufacturing order was *WH/MO/00012*. " +"Two manufacturing orders, *WH/MO/00008* and *WH/MO/00009*, are merged into a" +" single order. The reference number for the manufacturing order created by " +"the merger is *WH/MO/00013*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:77 +msgid "" +"In the :guilabel:`Source` field for the manufacturing order created by the " +"merger, the reference numbers of the manufacturing orders that were merged " +"are listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:81 +msgid "" +"Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create " +"*WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* " +"and *WH/MO/00010*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 +msgid "Manage semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:5 +msgid "" +"A *semi-finished product*, also known as a *subassembly*, is a manufactured " +"product that is used as a component in another product's bill of materials " +"(BoM). Semi-finished products are used to simplify complex :abbr:`BoMs " +"(Bills of Materials)` or to more accurately represent a manufacturing flow. " +"A :abbr:`BoM (Bill of Materials)` that contains semi-finished products is " +"referred to as a *multilevel BoM*, where the main *top-level product* and " +"its subassemblies are distinguished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:12 +msgid "Configure semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:14 +msgid "" +"To set up a multilevel :abbr:`BoM (Bill of Materials)`, the top-level " +"product and semi-finished products must be configured. Therefore, the first " +"step is to create the semi-finished products and their :abbr:`BoMs (Bills of" +" Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:19 +msgid ":doc:`bill_configuration`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A bill of materials for a semi-finished product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:26 +msgid "Create the top-level bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:28 +msgid "" +"After the semi-finished products are fully configured, navigate to " +":menuselection:`Manufacturing --> Products --> Products`. Then, " +":guilabel:`Create` the top-level product. Configure the product's " +"specifications as desired, and be sure to :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:32 +msgid "" +"Once the top-level product is configured, click the :guilabel:`Bill of " +"Materials` smart button on the product form, then click :guilabel:`Create` " +"to make a :abbr:`BoM (Bill of Materials)` for the top-level product. Then, " +"simply add the semi-finished products to this :abbr:`BoM (Bill of " +"Materials)`, along with any other necessary components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "" +"A bill of materials for a top-level product, containing a subassembly " +"component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:42 +msgid "Manage production planning" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:44 +msgid "" +"There are several methods to manage manufacturing order automation for " +"products with multilevel :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:48 +msgid "" +"Semi-finished products are specifically used to manage manufacturable " +"products with multilevel BoMs. If a BoM is being created simply to organize " +"components or bundle sellable products, using :doc:`Kits ` is " +"the more appropriate option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:52 +msgid "" +"To automatically trigger manufacturing orders for semi-finished products " +"after confirming a manufacturing order for the main product, there are two " +"options:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:55 +msgid "" +"**Option 1 (recommended):** Create *Reordering Rules* for the semi-finished " +"products and set both the minimum and maximum desired stock quantities to " +"`0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:59 +msgid ":doc:`../../purchase/products/reordering`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:61 +msgid "" +"**Option 2:** Activate the :guilabel:`Replenish on Order (MTO)` and " +":guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the " +"semi-finished product's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:64 +msgid "" +"Option 1 is more flexible than Option 2 and is therefore recommended. " +"Reordering rules do not directly link demand to replenishment, and therefore" +" allow stocks to be unreserved and redirected to other orders, if necessary." +" The Replenish on Order (MTO) route creates a unique link between the semi-" +"finished and top-level products, exclusively reserving quantities for the " +"confirmed top-level manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:70 +msgid "" +"Regardless of the method chosen, semi-finished products must be fully " +"manufactured before manufacturing can begin on the top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A manufacturing order for a top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:3 +msgid "Subcontract your Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:5 +msgid "" +"Outsourcing a portion or all of your company’s manufacturing needs is not " +"easy. To make it work correctly, you have to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:8 +msgid "Manage the inventory of raw materials at your subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:9 +msgid "Ship raw material to your subcontractors, at the right time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:10 +msgid "Control incoming goods quality" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:11 +msgid "Control subcontractors bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:13 +msgid "" +"Here is an example of subcontracting the manufacturing of “C”, which is " +"produced out of raw materials “A” and “B”." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:20 +msgid "" +"With its MRP subcontracting feature, Odoo helps you handle this flow easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:25 +msgid "" +"To use the subcontracting feature, go to :menuselection:`Manufacturing --> " +"Configuration --> Settings` and tick the box *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:32 +msgid "" +"To define if a product must be subcontracted, use a *Bill of Materials " +"(BoM)* of type *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:35 +msgid "" +"To create a new *BoM*, go to :menuselection:`Manufacturing --> Products --> " +"Bill of Materials` and hit create. Then, list the components your " +"subcontractor needs to manufacture the product. For costing purposes, you " +"might want to register all the components, even the ones that are sourced " +"directly from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:41 +msgid "" +"Once you have set the *BoM Type* to *Subcontracting*, specify one or several" +" subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:49 +msgid "Basic Subcontracting Flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:51 +msgid "" +"To let your subcontractor know how many products you need, create and send " +"them purchase orders (PO). To do so, go to the *Purchase* app and create a " +"new purchase order. Be sure to send the PO to a vendor that is defined as a " +"subcontractor on the *BoM* of these products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:60 +msgid "" +"Once the *PO* is validated (1), a pending receipt is created. When the " +"products are received, validate the receipt (2), with the actual quantity " +"received. As a result, Odoo does the following things for you:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:64 +msgid "" +"Consumes the respective components at the subcontractor’s location, based on" +" the *BoM* and your input (3);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:66 +msgid "Produces the finished goods at the subcontractor’s location (4);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:68 +msgid "" +"Moves products from that subcontractor’s location to YourCompany via the " +"validated receipt (5)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:73 +msgid "" +"The *PO* is optional. If you create a receipt manually, with the right " +"subcontractor, Odoo still performs all the moves. This can be useful if the " +"subcontractor does not bill a fixed price per item, but rather the time and " +"materials used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:79 +msgid "Inventory Valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:81 +msgid "The cost of the manufactured product “C” is defined as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:83 +msgid "**C = A + B + s**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:85 +msgid "With:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:87 +msgid "**A**: Cost of raw materials coming from YourCompany;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "**B**: Cost of raw materials sourced directly from the" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "subcontractor;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:92 +msgid "**s**: Cost of the subcontracted service." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:94 +msgid "" +"Sending raw materials to your subcontractors (**A**) does not impact the " +"inventory valuation, as the components are still valued as part of your " +"stock. This is managed by making the *Subcontracting Location* an *Internal " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:99 +msgid "" +"Then, the vendor price set on the product C form has to be what has to be " +"paid to the subcontractor for his parts and service time: **B + s**. The " +"product cost has to be: **A + B + s**, how much the product is valued in the" +" accounting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:104 +msgid "" +"Finally, the subcontractor bill then matches the purchase order, with the " +"proposed price coming from the finished products C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:108 +msgid "" +"If managing the replenishment of raw materials **B** at your subcontractor’s" +" location is not needed, simply include the cost of **B** in the " +"subcontractor’s price **s** and remove the products *B* from the *BoM*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 +msgid "" +"In case the received products from the subcontractor contain tracked " +"components, their serial or lot numbers need to be specified during the " +"receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:120 +msgid "" +"In that case, on the receipt of the subcontracted product, a *Record " +"Components* button appears. Click on it to open a dialog box and record the " +"serial/lot numbers of the components. If the finished product is also " +"tracked, its serial/lot number can be registered here too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:129 +msgid "" +"For audit purposes, it is possible to check the lot numbers recorded on a " +"receipt by using the icon on the right of the finished products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:136 +msgid "" +"Also note that in case flexible consumption has been selected on the " +"subcontracted BOM for a non-tracked product, the record components option " +"will also appear optionally on each move line, if you want to register more " +"or less component consumption at your subcontracting location, when " +"receiving your final product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:145 +msgid "" +"As you can see, the reception of both of these non-tracked products can " +"either be executed by selecting the 'Set Quantities' Option or via the move " +"line hamburger menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:149 +msgid "Automate Replenishment of Subcontractors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:151 +msgid "" +"There are two ways to automate the supply of raw materials to your " +"subcontractors when purchasing the final product. The chosen method depends " +"on whether or not you want the materials to transit through your warehouse. " +"Both of these methods are described as pull style mechanisms as their " +"trigger is the inital PO to the subcontractor, which creates a need at the " +"subcontracting location, for raw material." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:158 +msgid "" +"If you are supplying your subcontractor with raw material from your own " +"warehouse, you must activate the 'Resupply Subcontractor on Order' route as " +"shown below. If this is a component that you buy from a vendor, the buy " +"route should also be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:169 +msgid "" +"Now, if you want your vendor to resupply your subcontractor directly, you " +"must choose the 'Dropship Subcontractor on Order' option instead. In order " +"for this option to be active on the product form, you must first activate " +"the dropship option from :menuselection:`Purchase --> Configuration --> " +"Settings --> Dropshipping`. Once the PO to the subcontractor is validated, " +"this route will create a dropship RFQ from your vendor to that " +"subcontractor. You then just need to review and validate it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:182 +msgid "" +"Note that the buy route is not selected in this case, as the dropship route " +"is a buy route already." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:185 +msgid "" +"Finally, if you want to track the stock of these raw materials at your " +"subcontracting location(s), then you must activate *Multi-locations* in " +":menuselection:`Inventory --> Configuration --> Settings --> Storage " +"locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:189 +msgid "From the location form, you are then able to access the Current Stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:198 +msgid "Manual Replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:200 +msgid "You can also choose to replenish your subcontractors manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:202 +msgid "" +"If you want to send components to your subcontractor at your own " +"convenience, select the 'Resupply Subcontractor' Operation Type from the " +"*Inventory* Module, and create a picking, specifying to which subcontractor " +"you are delivering to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:210 +msgid "" +"Alternatively, you can also manually ask your vendor to resupply your " +"subcontractor by creating a dropship type PO, with your subcontractor set as" +" the delivery address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:3 +msgid "Three-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using three-step manufacturing, Odoo creates a pick " +"components transfer, a manufacturing order (MO), and a store finished " +"products transfer, and updates inventory counts based on the number of " +"components removed, and finished products created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:42 +msgid "" +"On the new |MO|, select the product to be produced from the " +":guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field " +"auto-populates with the associated Bill of Materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:53 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:54 +msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:57 +msgid "Process pick components transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:58 +msgid "" +"After confirming a three-step |MO|, a :guilabel:`Transfers` smart button " +"appears at the top of the page. Click it to be taken to the " +":guilabel:`Transfers` page for the |MO|. The page lists two transfers: " +"*WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store " +"finished products transfer)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:63 +msgid "" +"Select :guilabel:`WH/PC/XXXXX` to open the pick components transfer for the " +"|MO|. This transfer is used to track the movement of components from the " +"locations where they are stored to the location where they are used to " +"manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:64 +msgid "" +"After transferring the components out of their storage location, click " +":guilabel:`Validate` at the top of the transfer, followed by " +":guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that " +"appears. Doing so marks the transfer as :guilabel:`Done`, and updates " +"inventory counts to reflect the quantity of components transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:69 +msgid "" +"Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` " +"breadcrumb at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The manufacturing order bread crumb on a pick components transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:88 +msgid "" +"To complete work orders from the |MO| itself, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +msgid "The Start button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +msgid "The Done button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:130 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:126 +msgid "" +"Once the final work order for the |MO| has been reached, a :guilabel:`Mark " +"as Done and Close MO` button appears on the tablet view in addition to the " +":guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO`" +" to mark the |MO| as :guilabel:`Done`, and register the manufactured " +"product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:135 +msgid "" +"It is also possible to complete the final work order while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed at a later time by clicking the :guilabel:`Produce All` button on the" +" |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:140 +msgid "Process finished product transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:142 +msgid "" +"After completing the |MO|, return to the order's :guilabel:`Transfers` page " +"by clicking the :guilabel:`Transfers` button at the top of the order. This " +"time, select :guilabel:`WH/SFP/XXXXX` to open the store finished products " +"transfer. This transfer is used to track the movement of finished products " +"from the location where they were manufactured to the location where they " +"are stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:147 +msgid "" +"After transferring the finished products to their storage location, click " +":guilabel:`Validate` at the top of the transfer, followed by " +":guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that " +"appears. Doing so marks the transfer as :guilabel:`Done`, and updates " +"inventory counts to reflect the quantity of finished products transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:3 +msgid "Two-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using two-step manufacturing, Odoo creates a " +"manufacturing order (MO) and a pick components transfer, but does not " +"generate a transfer for the movement of finished products into stock. " +"Inventory counts still update based on the number of products manufactured, " +"but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:59 +msgid "" +"After confirming a two-step |MO|, a :guilabel:`Transfers` smart button " +"appears at the top of the page. Click it to open the pick components " +"transfer for the |MO|. This transfer is used to track the movement of " +"components from the locations where they are stored to the location where " +"they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:88 +msgid "" +"On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins " +"on the first work order that needs to be completed, click the " +":guilabel:`Start` button for that operation. Odoo *Manufacturing* then " +"starts a timer that keeps track of how long the work order takes to " +"complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The Start button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The Done button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:109 +msgid "" +"To complete the work orders for an |MO| using the tablet view, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:112 +msgid "" +"Next, click on the :guilabel:`Work Orders` tab, then select the :guilabel:`📱" +" (tablet)` button on the line of the first work order to be processed. This " +"opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:131 +msgid "" +"It is also possible to complete the final operation while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed at a later time by clicking the :guilabel:`Produce All` button on the" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 +msgid "Use the Master Production Schedule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:7 +msgid "" +"The Master Production Schedule (MPS) is a valuable tool to plan your " +"production based on your demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 +msgid "" +"Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` " +"and activate the Master Production Schedule feature before hitting save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 +msgid "" +"In the MPS settings, you can define the time range of your MPS " +"(month/week/day) and the number of periods you want to display at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 +msgid "" +"Now, go to :menuselection:`Planning --> Master Production Schedule` and " +"click on *add a product*. You can now define your safety stock target (= the" +" stock you want to have on hand at the end of the period) and the minimum " +"and maximum quantities that must or can be replenished in each period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 +msgid "" +"In the MPS view, you can decide which information you would like to display " +"by clicking on *rows*. For instance, the *Actual demand* will show you which" +" quantity of products has already been ordered for the period, or *Available" +" to Promise*, what can still be sold during that same period (what you plan " +"to replenish - what is already sold during the period). You can also decide " +"to hide rows if you like." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 +msgid "Estimate your demand and launch replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:40 +msgid "" +"The next step is to estimate the demand for the chosen period. This is done " +"in the *Forecasted Demand* Row. You can easily, at any time, compare the " +"demand forecast with the actual demand (= confirmed sales). The demand " +"forecast for a finished product will impact the indirect demand for its " +"components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 +msgid "" +"Once the forecasted demand has been set, the quantity to replenish for the " +"different periods will automatically be computed. The replenishments you are" +" supposed to launch based on your lead times (vendor lead time or " +"manufacturing lead time) are then displayed in green. You can now launch the" +" replenishment by clicking on the replenish button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 +msgid "" +"Depending on the configuration of the product (buy vs. manufacture), " +"requests for quotations or manufacturing orders will be created. You can " +"easily access those by clicking on the *Actual Replenishment* cell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 +msgid "" +"In case you manually edit the *Suggested Replenishment* quantity, a small " +"cross will appear on the left hand side of the cell. In case you want to go " +"back to the automatically computed value given by Odoo, simply click the " +"cross." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 +msgid "Cells color signification" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:69 +msgid "" +"The cells, which are part of the *Suggested Replenishment* line, can take " +"different colors depending on the situation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 +msgid "" +"**Grey**: replenishment order has already been generated, and its quantity " +"still matches current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 +msgid "" +"**Red**: replenishment order has already been generated, and its quantity " +"was too high considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 +msgid "" +"**Orange**: replenishment order has already been generated, and its quantity" +" was too low considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 +msgid "" +"The *Forecasted stock* line can also contain red cells, which means the " +"stock will be negative during the period in question." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 +msgid "What if I have underestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:86 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 +msgid "What if I have overestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:93 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 +msgid "What if I wrongly added a product to the MPS?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 +msgid "" +"You can easily remove a product from the MPS by clicking the small bin on " +"the right of its name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:3 +msgid "Manage work orders using work centers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:5 +msgid "" +"Odoo Manufacturing allows for work orders to be carried out at specific work" +" centers. When a manufacturing order is created for a product, any work " +"orders listed in the :guilabel:`Operations` tab of the product bill of " +"materials (BoM) will be automatically created as well and assigned to the " +"specified work center. Work orders can be managed in the " +":guilabel:`Manufacturing` module by selecting :menuselection:`Operations -->" +" Work Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 +msgid "" +"In order to use work centers, the :guilabel:`Work Orders` feature must first" +" be enabled. To do so, go to the :guilabel:`Manufacturing` module, select " +":menuselection:`Configuration --> Settings`, and activate the checkbox next " +"to :guilabel:`Work Orders`. Work centers can then be created and managed by " +"selecting :menuselection:`Configuration --> Work Centers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 +msgid "Create a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:19 +msgid "" +"Within the :guilabel:`Manufacturing` module, select " +":menuselection:`Configuration --> Work Centers --> Create`. The work center " +"form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 +msgid "" +":guilabel:`Work Center Name`: give the work center a concise name that " +"describes the type of operations it will be used for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 +msgid "" +":guilabel:`Alternative Workcenters`: specify an alternative work center for " +"operations to be carried out at if the main work center is not available" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:26 +msgid ":guilabel:`Code`: assign the work center a reference code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:27 +msgid "" +":guilabel:`Working Hours`: define the number of hours that the work center " +"can be in use each week" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:28 +msgid "" +":guilabel:`Company`: select the company that the work center belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "An example of a fully configured work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 +msgid "Set standards for work center productivity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:39 +msgid "" +"The :guilabel:`General Information` tab on the work center form allows for " +"productivity goals to be assigned to a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 +msgid "" +":guilabel:`Time Efficiency`: used to calculate the expected duration of a " +"work order at the work center; for example, if a work order normally takes " +"one hour and the efficiency is set to 200%, the work order will take 30 " +"minutes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 +msgid "" +":guilabel:`Capacity`: the number of operations that can be performed at the " +"work center simultaneously" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +msgid "" +":guilabel:`Time before prod.`: setup time required before work can commence" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +msgid "" +":guilabel:`Time after prod.`: breakdown or cleanup time required after work " +"is finished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 +msgid "" +":guilabel:`Cost per hour`: the cost of operating the work center for one " +"hour" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 +msgid "" +":guilabel:`Analytic Account`: the account where the cost of the work center " +"should be recorded" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The general information tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 +msgid "Assign equipment to a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:60 +msgid "" +"Using the :guilabel:`Equipment` tab, it is possible for specific pieces of " +"equipment to be assigned to a work center. The following information will be" +" displayed for each piece of equipment added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +msgid "" +":guilabel:`Technician`: the technician responsible for servicing the " +"equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 +msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 +msgid "" +":guilabel:`MTBF`: mean time between failures; the average time that the " +"piece of equipment will operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 +msgid "" +":guilabel:`MTTR`: mean time to recovery; the average time it takes for the " +"equipment to become fully operational again" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 +msgid "" +":guilabel:`Est. Next Failure`: an estimate of when the next equipment " +"failure will occur" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The equipment tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 +msgid "" +":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are " +"all calculated automatically based on past failure data, if any exists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 +msgid "Integrate IoT devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 +msgid "" +"The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT " +"(Internet of Things)` devices with a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +msgid ":guilabel:`Device`: specifies the IoT device to be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 +msgid ":guilabel:`Key`: the security key for the device" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:90 +msgid ":guilabel:`Action`: the IoT device action triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The IoT Triggers tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 +msgid "Use case: configure an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 +msgid "" +"When a work center is at capacity, it cannot accept any new work orders. " +"Instead of waiting for the work center to become available, it is possible " +"to specify an alternative work center where surplus work orders should be " +"carried out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 +msgid "" +"Begin by creating a new work center. Configure the :guilabel:`Equipment` tab" +" so that it has all of the same equipment as the main work center. This will" +" ensure that the same tasks can be carried out at both work centers. " +"Navigate to the main work center and include the new work center in the " +":guilabel:`Alternative Workcenters` selection field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 +msgid "" +"Now, create a new manufacturing order that uses the main work center for one" +" of its operations. The main work center will automatically be selected for " +"the operation in the :guilabel:`Work Orders` tab. After confirming the " +"manufacturing order, click the :guilabel:`Plan` button that appears at the " +"top left of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "" +"Click the plan button to automatically select an available work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 +msgid "" +"If the main work center is at capacity, the work center selected for the " +"operation will be automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The alternative work center is automatically selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 +msgid "Monitor work center performance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 +msgid "" +"Performance for an individual work center can be viewed by selecting " +":menuselection:`Configuration --> Work Centers`, and clicking on a work " +"center. A variety of metrics showing work center performance can be viewed " +"at the top right of the form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +msgid "" +":guilabel:`OEE`: overall effective efficiency, the percentage of time that " +"the work center has been fully productive" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 +msgid "" +":guilabel:`Load`: the amount of time it will take to complete the current " +"workload" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 +msgid "" +":guilabel:`Performance`: the real duration of work time, shown as a " +"percentage of the expected duration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 +msgid "Make work centers unavailable using Time Off" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5 +msgid "" +"In Odoo, *work centers* are used to carry out manufacturing operations at " +"specific locations. However, if a work center cannot be used for some " +"reason, work orders begin to pile up at the work center until it is " +"operational again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 +msgid "" +"As a result, it is necessary to make the work center unavailable in Odoo so " +"that the platform routes new work orders to alternative work centers that " +"are operational. Using Odoo *Time Off*, it is possible to designate a work " +"center as being unavailable for a set period of time. Doing so ensures that " +"manufacturing operations can continue until the impacted work center is " +"available again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 +msgid "" +"Before a work center can be designated as unavailable, the Odoo platform " +"must be properly configured. First, it is necessary to enable " +":ref:`developer mode `. This allows the :guilabel:`Time Off`" +" smart button to appear on each work center's :guilabel:`Working Hours` pop-" +"up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 +msgid "" +"Enable developer mode by going to :menuselection:`Settings`, scrolling to " +"the bottom of the page, and clicking :guilabel:`Activate the developer mode`" +" under the :guilabel:`Developer Tools` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Activate the developer mode\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29 +msgid "" +"Next, install the *Time Off* app. This is the app used for assigning time " +"off to all resources within Odoo, including employees and work centers. " +"Navigate to :menuselection:`Apps`, then type `Time Off` in the " +":guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module " +"should be the only one that appears on the page. Click the green " +":guilabel:`Install` button on the card to install the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off module installation card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39 +msgid "" +"The last step is to properly configure work centers. For this workflow, it " +"is necessary to have at least two work centers: one that is made unavailable" +" and a second that receives the work orders that the other cannot accept. If" +" no second work center is configured, Odoo cannot route work orders away " +"from the unavailable work center and they will pile up in its queue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 +msgid "" +"To create a work center, navigate to :menuselection:`Manufacturing --> " +"Configuration --> Work Centers --> Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 +msgid "" +"Make sure that both work centers have the same equipment listed under the " +":guilabel:`Equipment` tab. This ensures that operations carried out at one " +"work center can also be performed at the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The equipment tab on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 +msgid "" +"For the work center that will be made unavailable, select the second work " +"center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo " +"knows to send work orders to the second work center when the first is " +"unavailable for any reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "A work center form configured with an alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 +msgid "Add time off for a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65 +msgid "" +"With configuration completed, time off can now be assigned to the work " +"center that will be made unavailable. Begin by navigating to " +":menuselection:`Manufacturing --> Configuration --> Work Centers` and " +"selecting the affected work center. Click :guilabel:`Edit`, and then the " +":guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` " +"drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Working Hours \"External link\" button on the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 +msgid "" +"A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard " +"working hours for the work center are listed here, along with various other " +"details about it. Since developer mode was enabled, there is a " +":guilabel:`Time Off` button in the top right of the pop-up. Click it to be " +"taken to the :guilabel:`Resource Time Off` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off button on the Working Hours pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 +msgid "" +"On this page, click :guilabel:`Create` to configure a new time-off entry. On" +" the time-off form, note the :guilabel:`Reason` for the work center closure " +"(broken, maintenance, etc.), select the affected work center as the " +":guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End" +" Date` to specify the period during which the work center will be " +"unavailable. Click :guilabel:`Save` and the time off for the work center is " +"logged in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Resource Time Off\" form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94 +msgid "Route orders to an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96 +msgid "" +"Once a work center is within its specified time-off period, work orders sent" +" to it can be automatically routed to an alternative work center using the " +":guilabel:`Plan` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 +msgid "" +"Begin by creating a new manufacturing order by selecting " +":menuselection:`Operations --> Manufacturing Orders --> Create`. On the " +"manufacturing order form, specify a :guilabel:`Product` that uses the " +"unavailable work center for one of its operations. Click :guilabel:`Confirm`" +" to confirm the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 +msgid "" +"On the confirmed work order, select the :guilabel:`Work Orders` tab. By " +"default, the unavailable work center is specified in the :guilabel:`Work " +"Center` column. There is also a green :guilabel:`Plan` button on the top " +"left of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Plan button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112 +msgid "" +"Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work " +"Orders` tab is automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "" +"The selected work center updates automatically after clicking the Plan " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 +msgid "" +"Once the time-off period for the unavailable work center ends, Odoo " +"recognizes that the work center is available again. At this point, clicking " +"the :guilabel:`Plan` button does not route work orders to an alternative " +"work center unless the first one is at capacity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:3 +msgid "Work order dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:7 +msgid "" +"When manufacturing certain products, specific operations may need to be " +"completed before others can begin. In order to ensure operations are carried" +" out in the correct order, Odoo *Manufacturing* features a *work order " +"dependencies* setting. Enabling this setting allows for operations on a Bill" +" of Materials (BoM) to be *blocked* by other operations that should occur " +"first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:15 +msgid "" +"The *work order dependencies* setting is not enabled by default. To enable " +"it, begin by navigating to :menuselection:`Manufacturing --> Configuration " +"--> Settings`. Then, enable the :guilabel:`Work Orders` setting, if it is " +"not already active." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:19 +msgid "" +"After enabling the :guilabel:`Work Orders` setting, the :guilabel:`Work " +"Order Dependencies` setting appears below it. Enable :guilabel:`Work Order " +"Dependencies`, then click :guilabel:`Save` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:24 +msgid "Add dependencies to BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:26 +msgid "" +"Work order dependencies are configured on a product's |BOM|. To do so, " +"navigate to :menuselection:`Manufacturing --> Products --> Bills of " +"Materials`, then select a |BOM|, or create a new one by clicking " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:32 +msgid "" +"For a complete guide on how to properly configure a new |BOM|, see the " +"documentation on :ref:`creating a bill of materials " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:35 +msgid "" +"On the |BOM|, click on the :guilabel:`Miscellaneous` tab, then enable the " +":guilabel:`Operation Dependencies` checkbox. This makes a new " +":guilabel:`Blocked By` option available in the settings of the " +":guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The Operation Dependencies checkbox on the Miscellaneous tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:43 +msgid "" +"Next, click on the :guilabel:`Operations` tab. On the top-right of the tab, " +"click on the tab's :guilabel:`settings` button, then enable the " +":guilabel:`Blocked By` checkbox. This makes a :guilabel:`Blocked By` field " +"appear for each operation on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The settings for the Operations tab on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:51 +msgid "" +"In the line of the operation that should be blocked by another operation, " +"click the :guilabel:`Blocked By` field, and an :guilabel:`Open: Operations` " +"pop-up window appears. In the :guilabel:`Blocked By` drop-down field on the " +"pop-up window, select the blocking operation that must be completed *before*" +" the operation that is blocked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The Blocked By drop-down field for an operation on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:60 +msgid "Finally, save the |BOM| by clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:63 +msgid "Plan work orders using dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:65 +msgid "" +"Once work order dependencies have been configured on a |BOM|, Odoo " +"*Manufacturing* is able to plan when work orders are scheduled, based on " +"their dependencies. To plan the work orders for a manufacturing order, begin" +" by navigating to :menuselection:`Manufacturing --> Operations --> " +"Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:70 +msgid "" +"Next, select a manufacturing order for a product with work order " +"dependencies set on its |BOM|, or create a new manufacturing order by " +"clicking :guilabel:`New`. If a new manufacturing order is created, select a " +"|BOM| configured with work order dependencies from the :guilabel:`Bill of " +"Material` drop-down field, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:75 +msgid "" +"After confirming the manufacturing order, select the :guilabel:`Work Orders`" +" tab to view the work orders required to complete it. Any work orders that " +"are *not* blocked by a different work order display a `Ready` tag in the " +":guilabel:`Status` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:79 +msgid "" +"Work orders that are blocked by one or more work orders display a `Waiting " +"for another WO` tag instead. Once the blocking work order(s) are completed, " +"the tag updates to `Ready`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The status tags for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:86 +msgid "" +"To schedule the manufacturing order's work orders, click the " +":guilabel:`Plan` button at the top of the page. After doing so, the " +":guilabel:`Scheduled Start Date` field for each work order on the " +":guilabel:`Work Orders` tab auto-fills with the scheduled start date and " +"time. A blocked work order is scheduled at the end of the time period " +"specified in the :guilabel:`Expected Duration` field of the work order that " +"precedes it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "" +"The Scheduled Start Date field for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:97 +msgid "" +"A manufacturing order is created for Product A. The manufacturing order has " +"two operations: Cut and Assemble. Each operation has an expected duration of" +" 60 minutes, and the Assemble operation is blocked by the Cut operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:101 +msgid "" +"The :guilabel:`Plan` button for the manufacturing order is clicked at 1:30 " +"pm, and the Cut operation is scheduled to begin immediately. Since the Cut " +"operation has an expected duration of 60 minutes, the Assemble operation is " +"scheduled to begin at 2:30 pm." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:106 +msgid "Planning by workcenter" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:108 +msgid "" +"To see a visual representation of how work orders are planned, navigate to " +"the :guilabel:`Work Orders Planning` page by going to " +":menuselection:`Manufacturing --> Planning --> Planning by Workcenter`. This" +" page shows a timeline of all the work orders scheduled for each operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:112 +msgid "" +"If one work order is blocked by the completion of another, the work order " +"that is blocked is shown as scheduled to start after the work order blocking" +" it. In addition, an arrow connects the two work orders, leading from the " +"blocking operation to the blocked operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "" +"The arrow connecting a blocked work order to the work order blocking it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 +msgid "Shop Floor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:3 +msgid "Shop Floor overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:9 +msgid "" +"The *Shop Floor* module is a companion module to the *Manufacturing* app. " +"*Shop Floor* provides a visual interface for processing manufacturing orders" +" (MOs) and work orders. It also allows manufacturing employees to track the " +"amount of time spent working on manufacturing and work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:13 +msgid "" +"The *Shop Floor* module is installed alongside the *Manufacturing* app. It " +"cannot be installed by itself. To install the *Manufacturing* app, navigate " +"to :menuselection:`Apps`, search for `manufacturing` in the " +":guilabel:`Search...` bar, and then click :guilabel:`Install` on the " +":guilabel:`Manufacturing` app card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:19 +msgid "" +"The *Shop Floor* module replaces the tablet view functionality of the " +"*Manufacturing* app, and is only available in Odoo versions 16.4 and later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:22 +msgid "" +"To check the version number of an Odoo database, navigate to " +":menuselection:`Settings` and scroll down to the :guilabel:`About` section " +"at the bottom of the page. The version number is displayed there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:26 +msgid "" +"To switch to a newer version of Odoo, see the documentation on " +":ref:`upgrading a database `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:30 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:32 +msgid "" +"*Shop Floor* is broken down into three main views, which can be selected " +"from the navigation bar at the top of the module:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:35 +msgid "" +"The :guilabel:`All` page serves as the main dashboard for the module, and " +"displays information cards for |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:37 +msgid "" +"Each work center also has a dedicated page, which shows information cards " +"for work orders assigned to that work center. Work center pages can be " +"toggled on or off by clicking the :guilabel:`+ (plus)` button in the " +"navigation bar, selecting or deselecting them on the pop-up window that " +"appears, and then clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:41 +msgid "" +"The :guilabel:`My` page shows information cards for all work orders assigned" +" to the employee whose profile is currently active in the operator panel on " +"the left side of the module. Other than only showing work orders assigned to" +" the active employee, this page functions the same as the pages for each " +"work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:47 +msgid "" +"To isolate an |MO| or work order, so that no other orders appear, simply " +"search the reference number of the |MO| in the :guilabel:`Search...` bar at " +"the top of the module. This search filter remains active while switching " +"between the different module views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:51 +msgid "" +"On the left side of the module is the operator panel, which shows all of the" +" employees currently signed in to *Shop Floor*, and allows new employees to " +"sign in. The operator panel is always available in the module, regardless of" +" which view is selected. It can be toggled on or off by clicking the " +":guilabel:`sidebar` button at the extreme left of the navigation bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"The \"sidebar\" button, which is used to toggle the operator panel on or " +"off." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:61 +msgid "All page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:63 +msgid "" +"By default, the :guilabel:`All` page shows an information card for every " +"|MO| that is *ready to start*. An |MO| is considered ready to start once it " +"has been confirmed, and all required components are available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:67 +msgid "" +"To view every confirmed |MO| regardless of readiness, click the " +":guilabel:`x` button on the :guilabel:`Ready to Start` filter to remove it " +"from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:71 +msgid "MO information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:73 +msgid "" +"An |MO| information card on the :guilabel:`All` page shows all of the " +"relevant details of the associated |MO|, and also provides employees with " +"options for processing the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:76 +msgid "" +"The header for an |MO| card shows the |MO| number, the product and number of" +" units being produced, and the status of the |MO|. If work has not yet begun" +" on the |MO|, the status appears as :guilabel:`Confirmed`. Once work has " +"begun, the status updates to :guilabel:`In Progress`. If all work orders for" +" an |MO| have been completed and the |MO| is ready to close, the status " +"updates to :guilabel:`To Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:82 +msgid "" +"The main body of an |MO| card shows a line for each completed work order, if" +" any, followed by the current work order that needs to be completed. " +"Completed work orders are indicated by a green check mark to the right of " +"title of the work order. The current work order is indicated by a button " +"that opens the page for the work center to which the order is assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:87 +msgid "" +"Below the current work order is a line titled :guilabel:`Register " +"Production`, which is used to record the number of product units produced. " +"To manually enter the number of units produced, click on the " +":guilabel:`Register Production` line, enter a value in the :guilabel:`Units`" +" field of the resulting pop-up window, then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:92 +msgid "" +"Alternatively, click the :guilabel:`# Units` button on the right side of the" +" line, which automatically records the number of units the |MO| was created " +"for as the number of units produced. For example, if an |MO| is created for " +"10 units of a dining table, clicking the :guilabel:`10 units` button records" +" that 10 units were produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:97 +msgid "" +"The footer of the |MO| card displays a :guilabel:`Close Production` button. " +"This is used to close the |MO| once production is completed. However, if " +"there are any quality checks required for the |MO| as a whole (not the work " +"orders within it), a :guilabel:`Quality Checks` button appears instead. " +"Clicking :guilabel:`Quality Checks` opens a pop-up window, from which any " +"required quality checks can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:103 +msgid "" +"After clicking :guilabel:`Close Production`, the |MO| card begins to fade " +"away, and an :guilabel:`Undo` button appears on the footer. Clicking " +":guilabel:`Undo` causes the |MO| to remain open. Once the |MO| card " +"disappears completely, the work order is closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:107 +msgid "" +"On the right side of the footer is an :guilabel:`⋮ (options)` button, which " +"opens a pop-up window with additional options for the |MO|:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:171 +msgid "" +":guilabel:`Scrap` is used to send components to a scrap location when they " +"are found to be defective." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:112 +msgid "" +":guilabel:`Add Work Order` is used to add an additional work order to the " +"|MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:173 +msgid "" +":guilabel:`Add Component` is used to add an additional component to the " +"|MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:114 +msgid ":guilabel:`Open Backend MO` opens the |MO| in the Manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"An information card for an MO on the \"All\" page of the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:121 +msgid "Work center pages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:123 +msgid "" +"By default, the page for each work center shows an information card for " +"every work order assigned to it that is *ready to start*. A work order is " +"considered ready to start once the |MO| it is a part of is ready to start, " +"and any preceding work orders have been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:127 +msgid "" +"To view every confirmed work order assigned to a work center regardless of " +"readiness, click the :guilabel:`x` button on the :guilabel:`Ready to Start` " +"filter to remove it from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:132 +msgid "Work order information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:134 +msgid "" +"A work order information card on a work center's page shows all of the " +"relevant details of the associated work order, and also provides employees " +"with options for processing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:137 +msgid "" +"The header for a work order card shows the reference number of the |MO| that" +" the work order is a part of, the product and number of units being " +"produced, and the status of the work order. If work has not yet begun on the" +" work order, the status appears as :guilabel:`To Do`. Once work has begun, " +"the status updates to display a timer showing the total time the work order " +"has been worked on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:142 +msgid "" +"The main body of a work order card shows a line for each step required to " +"complete the work order. Work order steps can be completed by clicking on " +"the line, then following the instructions on the pop-up window that appears." +" Alternatively, clicking the checkbox on the right side of each line " +"automatically marks the step as completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:147 +msgid "" +"Below the final step of the work order is a line titled :guilabel:`Register " +"Production`, which functions the same as the :guilabel:`Register Production`" +" line on an |MO| card. Registering the number of units produced using the " +":guilabel:`Register Production` line on a work order card also completes the" +" step for the associated |MO| card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:152 +msgid "" +"If the work order being processed is the final work order for the |MO|, a " +":guilabel:`Close Production` button appears on the footer of the work order " +"card. Clicking :guilabel:`Close Production` closes both the work order and " +"the |MO|, unless a quality check is required for the |MO|. In this case, the" +" quality check must be completed from the |MO| card before the |MO| can be " +"closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:158 +msgid "" +"Alternatively, if the |MO| requires the completion of additional work " +"orders, a :guilabel:`Mark as Done` button appears instead. Clicking " +":guilabel:`Mark as Done` marks the current work order as completed, and " +"causes the next work order to appear on the page for the work center it is " +"assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:163 +msgid "" +"After clicking :guilabel:`Close Production` or :guilabel:`Mark as Done`, the" +" work order card begins to fade away, and an :guilabel:`Undo` button appears" +" on the footer. Clicking :guilabel:`Undo` causes the work order to remain " +"open. Once the work order card disappears completely, the work order is " +"marked as :guilabel:`Finished` on the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:168 +msgid "" +"On the right side of the footer is an :guilabel:`⋮ (options)` button, which " +"opens a pop-up window with additional options for the work order:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:174 +msgid "" +":guilabel:`Move to work center` is used to transfer the work order to a " +"different work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:175 +msgid "" +":guilabel:`Suggest a Worksheet improvement` allows the user to propose a " +"change to the work order's instructions or steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:177 +msgid "" +":guilabel:`Create a Quality Alert` opens a quality alert form that can be " +"filled out to alert a quality team about a potential issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "An information card for a work order in the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:185 +msgid "Operator panel" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:187 +msgid "" +"The operator panel is used to manage the employees that are signed in to the" +" *Shop Floor* module. The panel shows the name and profile picture of every " +"employee that is currently signed in across all instances of the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:191 +msgid "" +"To interact with *Shop Floor* as a specific employee, click the employee's " +"name to activate their profile. Profiles that are not active appear with " +"their names and profile pictures greyed-out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:194 +msgid "" +"When an employee is selected in the operator panel, they can begin working " +"on a work order by clicking the work order's heading. If an employee is " +"working on one or more work orders, the work order title(s) appear under " +"their name, along with a timer showing how long they've been working on each" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:199 +msgid "" +"To add a new employee to the operator panel, click the :guilabel:`+ Add " +"Operator` button at the bottom of the panel. Then, select an employee from " +"the :guilabel:`Select Employee` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:202 +msgid "" +"To remove an employee from the operator panel, simply click the " +":guilabel:`x` button next to their name in the panel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"The operator panel of the Shop Floor module, showing three employees signed " +"in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:8 +msgid "Product lifecycle management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:10 +msgid "" +"Odoo *Product Lifecycle Management* (*PLM*) offers a systematic approach for" +" testing, collaboration, and iteration of products across concept " +"development, design, manufacturing, marketing, and post-launch support " +"stages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:14 +msgid "" +"With approvals, key stakeholders can review changes before implementation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes.rst:3 +msgid "Change management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:10 +msgid "ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:12 +msgid "" +"An *ECO type* is assigned to *engineering change orders* (ECOs) to organize " +"and track changes to products and bills of materials (BoMs). Each |ECO| type" +" separates |ECOs| into a project in Gantt view, ensuring collaborators and " +"stakeholders **only** view and assist with relevant |BOM| improvements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:17 +msgid "" +"For example, an electronic chip manufacturer might use 'New Product " +"Introduction', 'Product Improvement', 'Component Change', and 'Firmware " +"Update' |ECO| types. Then, designers and engineers can focus on |ECOs| in " +"the 'New Product Introduction' and 'Product Improvement' projects, avoiding " +"unrelated supplier change or firmware update |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:23 +msgid "Create ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:25 +msgid "" +"To access and manage ECO types, navigate to :menuselection:`PLM app --> " +"Configuration --> ECO Types`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:28 +msgid "" +"Create a new ECO type by clicking :guilabel:`New`. On the new :guilabel:`ECO" +" Types` form, fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:31 +msgid "" +":guilabel:`Name`: the name of the |ECO| type, which will organize all of the" +" |ECOs| of this *type* in a project." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:33 +msgid "" +":guilabel:`Email Alias`: if this optional field is filled, emails submitted " +"to this email address automatically generate |ECOs| in the left-most stage " +"of this |ECO| type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:37 +msgid "" +"The `Formulation change` |ECO| type is used to organize and track related " +"|ECOs| in a single project. Configuring the :guilabel:`Email Alias` field " +"generates |ECOs| in the `Formulation change` project sent to the email " +"address, `pawlish-change@pawlished-glam.odoo.com`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Example of an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:46 +msgid "Edit ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:48 +msgid "" +"Modify existing |ECO| type names and email aliases by navigating to the " +":menuselection:`PLM app --> Configuration --> ECO Types` page. There, click " +"on the desired |ECO| type from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:51 +msgid "" +"On the form for each |ECO| type, proceed to edit the :guilabel:`Name` and " +":guilabel:`Email Alias` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:57 +msgid "Stages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:59 +msgid "" +"Within an |ECO| type project, *stages* are like milestones and are used to " +"identify the progress of the |ECO| before the changes are ready to be " +"applied. (e.g. 'Feedback', 'In Progress', 'Approved', 'Complete')" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:63 +msgid "" +"Additionally, required approvers can be added to each stage, ensuring that " +"changes to the production |BOM| cannot proceed until the approver reviews " +"and approves the |ECO|. Doing so prevents errors on the production |BOM| by " +"enforcing at least one review of suggested changes before they're applied on" +" a production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:68 +msgid "" +"For best practice, there should be at least one *verification* stage, which " +"is a stage with a required approver, and one *closing* stage, which stores " +"|ECOs| that have been either canceled or approved for use as the next " +"production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:73 +msgid "Create stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:75 +msgid "" +"To add a stage, go to the :menuselection:`PLM` app and select the intended " +"project for an |ECO| type from the :guilabel:`PLM Overview` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:78 +msgid "" +"Then, on the :guilabel:`Engineering Change Orders` project pipeline for the " +"|ECO| type, click the :guilabel:`+ Stage` button. Doing so reveals a text " +"box to fill in the name of the stage. After filling it in, click the " +":guilabel:`Add` button to finish adding the stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:83 +msgid "" +"A new `Assigned` stage separates assigned |ECOs| from the unassigned ones in" +" the `New` stage. Adding another stage helps the product manager track " +"unassigned tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Create a new stage in a project for an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:91 +msgid "Verification stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:93 +msgid "" +"Click an ECO type from :menuselection:`PLM app --> Overview` to open a " +"kanban view of |ECOs| of this type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:96 +msgid "" +"To configure a verification stage, hover over the intended stage, and select" +" the :guilabel:`⚙️ (gear)` icon. Then, click :guilabel:`Edit` to open a pop-" +"up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:99 +msgid "" +"Configure the verification stage in the edit stage pop-up window, by " +"checking the box for :guilabel:`Allow to apply changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:102 +msgid "" +"Then, add an approver in the :guilabel:`Approvers` section, by clicking " +":guilabel:`Add a line`, and specifying the :guilabel:`Role` of the reviewer," +" their :guilabel:`User`, and :guilabel:`Approval Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:106 +msgid "" +"Make sure at least one approver is configured with the :guilabel:`Approval " +"Type`: :guilabel:`Is required to approve`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:109 +msgid "" +"The approver listed is automatically notified when |ECOs| are dropped in the" +" stage specified in the pop-up window. Once finished, click :guilabel:`Save " +"& Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:113 +msgid "" +"In the |ECO| type `New Product Introduction`, the verification stage " +"`Validated` is configured by clicking the :guilabel:`⚙️ (gear)` icon, and " +"selecting :guilabel:`Edit`. Doing so opens the :guilabel:`Edit: Validated` " +"pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:117 +msgid "" +"By adding the `Engineering manager` as an approver, only |ECOs| approved by " +"this user can proceed to the next stage, and have the changes applied on the" +" production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:120 +msgid "" +"Additionally, check the :guilabel:`Allow to apply changes` option to ensure " +"proper behavior." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Show \"Allow to apply changes\" option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:127 +msgid "Closing stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:129 +msgid "" +"Configure a closing stage by opening the :guilabel:`Edit: [stage]` pop-up " +"window. To do so, hover over the intended stage and click the :guilabel:`⚙️ " +"(gear)` icon that appears in the top-right corner. Then, click " +":guilabel:`Edit` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:133 +msgid "" +"On the :guilabel:`Edit: [stage]` pop-up window, select the check boxes for " +":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes` and " +":guilabel:`Final Stage`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:137 +msgid "" +"The closing stage, `Effective` is configured by checking the " +":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes`, and " +":guilabel:`Final Stage` options" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst-1 +msgid "Show configurations of the closing stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:3 +msgid "Engineering change orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:12 +msgid "" +"Utilize *engineering change orders* (*ECOs*) to track, implement, and revert" +" change versions made to products, and :ref:`bills of materials " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:15 +msgid "Engineering change orders can be created:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:17 +msgid ":ref:`directly in the ECO type `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:18 +msgid "" +"by an operator in the :ref:`tablet view ` of an " +"operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:19 +msgid "" +"automatically from feedback submitted to the :ref:`ECO type's email alias " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:24 +msgid "Create ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:26 +msgid "" +"To create a new |ECO|, begin by navigating to the *PLM* app. Then, select " +"the |ECO| type card that will be used to track the progress of the change. " +"On the :guilabel:`Engineering Change Orders` page, click the :guilabel:`New`" +" button in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:31 +msgid "" +"Learn how to create new :ref:`ECO types ` to categorize " +"and organize change orders. Doing so ensures employees only view the |ECOs| " +"related to their responsibilities, whether it involves new product " +"introductions, targeted product line updates, or regulatory compliance " +"fulfillment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:36 +msgid "On the |ECO| form, fill in the following fields accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:38 +msgid ":guilabel:`Description` is a brief summary of the improvement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:39 +msgid "" +":guilabel:`Type`: specifies the |ECO| type project for organizing the " +"|ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:40 +msgid "" +":guilabel:`Apply on` determines if the |ECO| changes the :guilabel:`Bill of " +"Materials` or the :guilabel:`Product Only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:42 +msgid ":guilabel:`Product` indicates the product being improved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:43 +msgid "" +":guilabel:`Bill of Materials` specifies the changed |BOM|. It auto-populates" +" if the product in :guilabel:`Product` field has an existing |BOM|. If " +"multiple |BOMs| exist, select the intended radio options from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:46 +msgid "" +":guilabel:`Company` field is used in multi-company databases. Specify if the" +" change applies to products in a specific company, or leave blank if the " +"change applies to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:48 +msgid "" +":guilabel:`Responsible` represents the assignee in charge of this |ECO|. " +"(Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:49 +msgid "" +":guilabel:`Effective` specifies when the |ECO| becomes live. Choosing " +":guilabel:`As soon as possible` means the |ECO| applies to the production " +"|BOM| as soon as an authorized user :ref:`applies the changes " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:53 +msgid "" +"On the other hand, choosing :guilabel:`At Date`, and setting a specific " +"date, leaves a date that makes it easier to track the version history of the" +" |BOM|, and the specific date |BOMs|, used for production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:56 +msgid "" +":guilabel:`Tags` are assigned to |ECOs| for prioritization and organization." +" Create a new tag by typing the name in the field and selecting " +":guilabel:`Create` from the drop-down menu. (Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:59 +msgid "" +"After filling out the |ECO| form, click the :guilabel:`Start Revision` " +"button to begin implementing the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:62 +msgid "By pressing :guilabel:`Start Revision`, three actions occur:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:64 +msgid "" +"The :guilabel:`Documents` smart button appears, storing relevant files of " +"the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:65 +msgid "" +"A copy of the production |BOM| is stored in the newly-appeared " +":guilabel:`Revision` smart button of the |ECO|. The next available version " +"number (e.g., `V2`, `V3`, ...) is also assigned to keep track of all |BOM| " +"versions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:68 +msgid "" +"The stages of the |ECO| :guilabel:`Type` are displayed in the top-right " +"corner of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:71 +msgid "" +"The :guilabel:`Revision` smart button is available **only** when the " +":guilabel:`Bill of Materials` radio button is selected in the " +":guilabel:`Apply on` field, and the :guilabel:`Start Revision` button has " +"been pressed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "" +"ECO with overview of stages in the top-right corner, and *Revision* smart " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:80 +msgid "Change components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:82 +msgid "" +"To modify the components in a |BOM|, click the :guilabel:`Revision` smart " +"button on an |ECO| to access the new version of the |BOM|. Odoo " +"distinguishes the non-production version of the |BOM| from the current " +"version, by flagging the test |BOM| with a large :guilabel:`Archived` tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:87 +msgid "" +"After clicking the :guilabel:`Start Revision` button for an |ECO| for the " +"product, `[D_0045 Stool]`, make changes to the product's |BOM| by clicking " +"the :guilabel:`Revision` smart button. Doing so opens the archived |BOM|, " +"marked with a large red :guilabel:`Archived` flag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show the archived Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:95 +msgid "" +"On the new |BOM|, in the :guilabel:`Components` tab, proceed to modify the " +"components list, by changing the :guilabel:`Quantity` of existing " +"components, adding new components using the :guilabel:`Add a line` button, " +"and removing components with the :guilabel:`🗑️ (trash)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:102 +msgid "" +"In version two of the |BOM| for a keyboard, the component quantities are " +"reduced, and an additional component, `Stabilizers`, is added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Make changes to components by going to the new BoM with the *Revision* smart" +" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:110 +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:153 +msgid "Compare changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:112 +msgid "" +"Once the changes are complete, navigate back to the |ECO|, by clicking " +"`ECO00X` in the breadcrumbs located in the top-left corner. On the |ECO| " +"form, a new :guilabel:`BoM Changes` tab displays the differences between the" +" current |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:116 +msgid "" +"Blue text indicates new components added to the revised |BOM| that are not " +"in the production |BOM|. Black text represents updates shared by both " +"|BOMs|, while red text indicates components removed in the revised |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:120 +msgid "" +"Changes and tests are encapsulated in the revised |BOM|, and do **not** " +"affect the |BOM| currently used in production. That is, until the " +":ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:124 +msgid "" +"View the summary of the differences between the current and revised keyboard" +" |BOMs| in the :guilabel:`BoM Changes` tab of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View summary of component changes in the *BoM Changes* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:132 +msgid "Change operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:134 +msgid "" +"To modify the operations in a |BOM|, click the :guilabel:`Revision` smart " +"button on an |ECO| to access the archived, new version of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:137 +msgid "" +"In the new |BOM| version, switch to the :guilabel:`Operations` tab to view " +"and edit |BOM| operations. To make changes, select each operation, which " +"opens the corresponding :guilabel:`Open: Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:142 +msgid "" +"The :guilabel:`Operations` tab is *not* available by default. To enable it, " +"navigate to :menuselection:`Manufacturing app --> Configuration --> " +"Settings`, and check the :guilabel:`Work Orders` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:146 +msgid "" +"Make changes to any of the fields in the :guilabel:`Open: Operations` pop-up" +" window, then click :guilabel:`Save` once completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:149 +msgid "" +"Create new operations by clicking the :guilabel:`Add a line` button, and " +"remove new operations by clicking the :guilabel:`Archive Operation` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:155 +msgid "" +"Once the changes are complete, navigate back to the |ECO|, by clicking " +"`ECO00X` in the breadcrumbs located in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:158 +msgid "" +"On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the " +"differences between the current production |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:161 +msgid "" +"Blue text indicates new operations added to the revised |BOM| that do not " +"yet exist in the production |BOM|. Black text represents updates shared by " +"both |BOMs|, while red text indicates operations removed in the revised " +"|BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:165 +msgid "" +"Modifications to the |BOM| in an |ECO| will **not** affect the |BOM| used in" +" production. That is, until the :ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:168 +msgid "" +"In the :guilabel:`Operation Changes` tab, each row of details, beneath the " +"columns in the table, reflect the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:171 +msgid ":guilabel:`Operation`: Name of the operation that was modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:172 +msgid "" +":guilabel:`Step`: specifies the quality control point, visible when the " +"operation includes detailed instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:176 +msgid "" +"To check for instructions, click the operation line item in the " +":guilabel:`Operations` tab of a |BOM|. Then, in the :guilabel:`Open: " +"Operations` pop-up window, look for the :guilabel:`Instructions` smart " +"button displayed at the top." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:181 +msgid "" +"The `Assembly` :guilabel:`Operation` includes `10` detailed " +":guilabel:`Instructions` to complete it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Show *Instructions* smart button to check whether an operation has additional\n" +"instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:189 +msgid "" +":guilabel:`Step Type` details the type of quality control for further " +"instructions in the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:191 +msgid "" +":guilabel:`Type` corresponds with the colored text to specify how the " +"revised |BOM| differs from the production |BOM|. Operation change types can " +"be :guilabel:`Add`, :guilabel:`Remove`, or :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:194 +msgid "" +":guilabel:`Work Center` specifies the work center at which the operation is " +"performed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:195 +msgid "" +":guilabel:`Manual Duration Change` refers to the change in the " +":guilabel:`Default Duration` field in the :guilabel:`Open: Operations` pop-" +"up window, which specifies the expected time for completing the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:200 +msgid "" +"The :guilabel:`Operation Changes` tab compares the production |BOM| with the" +" revised |BOM| in the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:203 +msgid "" +"In the revised |BOM|, a new `Assembly` :guilabel:`Operation` at the " +":guilabel:`Work Center` `Assembly Line 1` is added. In addition, the " +"expected duration of the operation is `20.00` minutes, as specified by the " +":guilabel:`Manual Duration Change`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:207 +msgid "" +"To supplement the `Assembly` operation, two quality control point " +"instructions are added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:209 +msgid "" +"The first is the :guilabel:`Step` `QCP00039`, a :guilabel:`Step Type` to " +":guilabel:`Register Production` of components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:211 +msgid "" +"The second :guilabel:`Step` is `QCP00034`, an `Instructions` :guilabel:`Step" +" Type` that provides additional assembly details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show *Operation Changes* tab in an |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:221 +msgid "Apply changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:223 +msgid "" +"After verifying the changes, move the |ECO| to a :ref:`verification stage " +"`, which are stages that require approval before the " +"revised changes can be applied to the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:227 +msgid "" +"Once the approvers accept the changes, the :guilabel:`Apply Changes` button " +"becomes available. Click this button, and the |ECO| is automatically moved " +"to a closing stage. The changes are applied, which archives the original " +"production |BOM|, and the revised |BOM| becomes the new production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:232 +msgid "Verify changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:234 +msgid "" +"To ensure the changes are live, from the |ECO| where the :guilabel:`Apply " +"Changes` button was just pressed, return to the revised |BOM| by clicking " +"the :guilabel:`Revision` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:237 +msgid "" +"On the revised |BOM|, the large red :guilabel:`Archived` flag is removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:239 +msgid "" +"To further verify the changes, check the production |BOM| by going to " +":menuselection:`Manufacturing app --> Products --> Products` and select the " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:242 +msgid "" +"Then, on the product form, click the :guilabel:`Bill of Materials` smart " +"button, and select the |BOM| from the list. In the :guilabel:`Miscellaneous`" +" tab of the |BOM|, the :guilabel:`Version` field is updated to match the " +"version number shown on the :guilabel:`Revision` smart button of the latest " +"|ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:248 +msgid "" +"After applying the changes of the |ECO| for the :ref:`keyboard " +"`, view the version of the current keyboard |BOM| " +"in the :guilabel:`Miscellaneous` tab. Here, the :guilabel:`Version` number " +"has been updated to `2`, matching the `V2` that appears in the " +":guilabel:`Revision` smart button of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View current *BOM* version in the Miscellaneous tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:260 +msgid "Create ECO from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:262 +msgid "" +"Operators can directly suggest clearer operation instructions, while " +"performing manufacturing orders (MOs) in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:265 +msgid "" +"To create |ECOs| in this manner, begin by navigating to " +":menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. " +"Then, select the desired :abbr:`MO (Manufacturing Order)` and switch to the " +":guilabel:`Work Orders` tab. Then, click the :guilabel:`📱 (mobile phone)` " +"icon for the desired work order to open the *tablet view* of the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:271 +msgid "" +"The :guilabel:`📱 (mobile phone)` icon is **only** available for :abbr:`MOs " +"(Manufacturing Orders)` with a :guilabel:`Confirmed` or :guilabel:`In " +"Progress` status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "Find the tablet icon for each operation, second from the far right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:278 +msgid "" +"Next, add an instructional step, by clicking the :guilabel:`☰ (three " +"horizontal lines)` icon in the tablet view of an operation. Doing so opens " +"the :guilabel:`Menu` of action items for a :abbr:`MO (Manufacturing Order)`." +" Then, click the :guilabel:`Add a step` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "" +"Open the *Add a Step* pop-up by clicking the three horizontal lines icon in " +"tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:286 +msgid "" +"Clicking the button reveals an :guilabel:`Add a step` pop-up window, where " +"the proposed changes are submitted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:289 +msgid "" +"In the :guilabel:`Title` field, enter a short step description. Next, in the" +" :guilabel:`Instruction` text field, type the instructions of the step in " +"greater detail. Optionally, add an image to the :guilabel:`Document` field. " +"Once completed, finish by clicking the :guilabel:`Propose Change` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:295 +msgid "" +"To propose an additional check for broken components, enter the details in " +"the :guilabel:`Add a Step` pop-up window. Doing so creates an instructional " +"quality control point that will be reviewed in the following section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Fill out the *Add a Step* form to suggest an additional quality control " +"point." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:303 +msgid "" +"Based on the inputs from the :guilabel:`Add a Step` pop-up window, an |ECO| " +"is created with the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:306 +msgid "" +":guilabel:`Description` is the name of the operation, followed by the " +":abbr:`MO (Manufacturing Order)` number for reference." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:308 +msgid "The |ECO| :guilabel:`Type` is automatically assigned to `BOM Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:309 +msgid "" +":guilabel:`Product` and :guilabel:`Bill of Materials` fields are " +"automatically populated, based on the |BOM| used in the :abbr:`MO " +"(Manufacturing Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:311 +msgid ":guilabel:`Responsible` is the operator who submitted the feedback." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:314 +msgid "View ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:316 +msgid "" +"To review the proposed changes, navigate to the :menuselection:`PLM app --> " +"Overview`. In the `BOM Updates` |ECO| type card, the :guilabel:`X " +"Engineering Changes` button represents the amount of operational changes " +"created from the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:320 +msgid "" +"Click on the :guilabel:`X Engineering Changes` button to open the kanban " +"view of the |ECO| type. To view the suggestion, select an |ECO| in the `New`" +" stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:323 +msgid "" +"On the |ECO|, view a summary of the proposed changes in the " +":guilabel:`Operation Changes` tab. Click the :guilabel:`Revision` smart " +"button to navigate to the revised |BOM| and look into the proposed changes " +"in greater detail." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:328 +msgid "" +"An operator suggested another check for broken components by adding a step " +"from the tablet view, while performing the `Assemble switches` operation for" +" the :abbr:`MO (Manufacturing Order)` `WH/MO/00010` for the product, " +"`Keyboard`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:332 +msgid "" +"Then, this created |ECO| can be viewed by navigating to the `BOM Changes` " +"ECO type found in :menuselection:`PLM app --> Overview`. By default, |ECOs| " +"created from tablet view are set to spawn in the `New` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:336 +msgid "" +"The :guilabel:`Responsible` field is assigned to the operator who made the " +"suggestion, allowing the employee revising the |BOM| to seek further " +"clarification from the person who proposed the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Find the new ECO in the \"BOM Changes\" ECO type, in the *New* stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:344 +msgid "" +"On the revised |BOM|, switch to the :guilabel:`Operations` tab, and select " +"the :guilabel:`☰ (three horizontal lines)` icon. Doing so opens a list of " +":guilabel:`Steps` to perform the operation, with the newest instruction " +"titled `New Step Suggestion:`, followed by the user-entered title. Click the" +" line item to view the suggested changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "\"Show Instructions\" icon in the *Operations* tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:353 +msgid "" +"On the :ref:`quality control point ` form, ensure the following form fields are accurately " +"filled out to give detailed instructions for operators:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:356 +msgid "" +":guilabel:`Title`: rename to give a concise description of the new " +"instruction." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:357 +msgid "" +":guilabel:`Control per`: using the drop-down menu, determine whether this " +"instruction applies broadly for the :guilabel:`Product`, specifically for " +"this :guilabel:`Operation` *only*, or a particular :guilabel:`Quantity` of " +"the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:360 +msgid "" +":guilabel:`Type`: categorizes the control point type. From the drop-down " +"menu, select :guilabel:`Instructions` to detail an instruction for the " +"worker. To receive input from the workers, select the :guilabel:`Take a " +"Picture`, :guilabel:`Register Consumed Materials`, :guilabel:`Print Label`, " +"or other :ref:`quality check options `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:367 +msgid "" +":ref:`Configure quality control points `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:369 +msgid "" +"Once the quality control point is configured, return to the " +":guilabel:`Steps` list using the breadcrumbs. Finally, drag the last quality" +" control line item to its intended order of instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:373 +msgid "" +"Drag and reorder the `Check for broken switches` instruction, by clicking " +"and dragging its \"6 dots\" icon to move it from the bottom to the second " +"position." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Drag and reorder instructions by selecting the \"6 dots\" icon on the far " +"left." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:3 +msgid "Version control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:10 +msgid "" +"Use Odoo's *Product Lifecycle Management (PLM)* to manage previous versions " +"of bills of materials (BoMs). Store former assembly instructions, component " +"details, and past product design files while keeping the past details out of" +" the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:14 +msgid "" +"Easily revert to previous |BOM| versions, when needed. Additionally, use " +"*PLM* to trace which |BOM| version was active on specific dates for recalls " +"or customer complaints." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:17 +msgid "" +"Every |BOM| version is stored in an *engineering change order* (ECO) for " +"organized testing and improvements without disrupting normal manufacturing " +"operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:21 +msgid ":ref:`Engineering change order `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:24 +msgid "Current BoM version" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:26 +msgid "" +"To see the current version of the |BOM| used in production, go to " +":menuselection:`PLM app --> Master Data --> Bill of Materials`, and select " +"the desired |BOM| from the list. Then, switch to the " +":guilabel:`Miscellaneous` tab, where the currently live :guilabel:`Version` " +"of the |BOM| is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:32 +msgid "" +"|BOMs| can also be accessed from :menuselection:`Manufacturing app --> " +"Products --> Bill of Materials`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show the current version BOM in the Misc tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:40 +msgid "Version history" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:42 +msgid "" +"To manage all former, current, and future versions of a |BOM|, begin by " +"navigating to :menuselection:`Manufacturing app --> Products --> Bills of " +"Materials` and click the desired |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:45 +msgid "" +"From the |BOM| page, click the :guilabel:`ECO` smart button, and switch to " +"list view by selecting the :guilabel:`≣ (four horizontal lines)` icon on the" +" top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:49 +msgid "" +"The :guilabel:`ECO` smart button is visible on the |BOM| **only** if the " +"*PLM* app is installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show ECO smart button on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:55 +msgid "" +"In the list of |ECOs| for the product, navigate to the search bar at the " +"top, and click the :guilabel:`▼ (down arrow)` icon on the right to access a " +"drop-down menu of :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:58 +msgid "" +"Next, filter by :guilabel:`Done` |ECOs| to view: the revision history of the" +" |BOM|, the :guilabel:`Responsible` user who applied the change, and the " +":guilabel:`Effective Date` of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:62 +msgid "" +"Click each |ECO| to view the past components, operations, and design files " +"associated with the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Display ECO revision history for a BoM for a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:70 +msgid "" +"If the :guilabel:`Effective Date` field is empty, the :guilabel:`Effective` " +"date of the |ECO| is automatically set to :guilabel:`As soon as possible` " +"and no dates are recorded in the revision history of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "List of BOM effective dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:79 +msgid "" +"A workaround for checking when the |BOM| went live is by navigating to the " +"chatter, and hovering over the time the |ECO| was moved to the :ref:`closing" +" stage `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:83 +msgid "Design files" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:85 +msgid "" +"Attach computer-aided design (CAD) files, PDFs, images, or other design " +"material to the |BOM| itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:88 +msgid "" +"To do so, navigate to :menuselection:`PLM app --> Master Data --> Bill of " +"Materials`, and select the desired |BOM|. On the |BOM|, navigate to the " +"*chatter*, and click the :guilabel:`📎 (paperclip)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:92 +msgid "" +"The files associated with the |BOM| are displayed in the :guilabel:`Files` " +"section. To add more design files, select the :guilabel:`Attach files` " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show paperclip icon in the chatter to attach files to a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:100 +msgid "Manage design files in an ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:102 +msgid "" +"Add, modify, and remove files in an |ECO|. Once the |ECO| is approved and " +"applied, the new files are automatically linked to the production |BOM|. " +"Archived files are removed from the |BOM|, but are still accessible in the " +"|ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:106 +msgid "" +"To manage the design files in the |ECO|, begin by navigating to " +":menuselection:`PLM app --> Changes` and choose the desired |ECO|. Next, " +"open the :guilabel:`Attachments` page by clicking the :guilabel:`Documents` " +"smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:110 +msgid "" +"Hover over each attachment to reveal the :guilabel:`︙ (three vertical dots)`" +" icon. From there, choose whether to :guilabel:`Edit`, :guilabel:`Remove`, " +"or :guilabel:`Download` the file. Any changes made to these files are " +"contained within the |ECO|, and will only apply to the production |BOM| once" +" the :ref:`changes are applied `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:116 +msgid "" +"In the `Create 60% keyboard` |ECO|, the design files are from the original " +"`100% keyboard` |BOM|. To replace the keyboard PDF, begin by selecting the " +":guilabel:`Documents` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Show *Documents* smart button from an active ECO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:123 +msgid "" +"On the :guilabel:`Attachments` page, hover over the `100% keyboard " +"manual.pdf` design file, and click the :guilabel:`︙ (three vertical dots)` " +"icon. Then, click the :guilabel:`Remove` option to archive the file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:127 +msgid "" +"Next, on the same :guilabel:`Attachments` page, click the :guilabel:`Upload`" +" button to upload the new design file, named `60% keyboard manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "" +"View of *Attachments* page from the *Documents* smart button. Displays one archived and\n" +"one newly added attachment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:136 +msgid "" +"Archived files are **not** permanently deleted — they can still be accessed " +"in the previous |ECO|, or as an archived file in the latest |ECO|, where the" +" archival occurred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:140 +msgid "Apply rebase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:142 +msgid "" +"Odoo simplifies merge conflict resolution for concurrent |ECOs| on the same " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:144 +msgid "" +"Conflicts can occur when the production |BOM| is updated while other |ECOs| " +"are modifying the previous version. Differences between the new and previous" +" production |BOMs| are displayed in the :guilabel:`Previous Eco Bom Changes`" +" tab, visible only in this scenario." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:148 +msgid "" +"To resolve conflicts and retain |ECO| changes, click the :guilabel:`Apply " +"Rebase` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:151 +msgid "" +"Two |ECOs|, `ECO0011` and `ECO0012`, are created when the current |BOM| " +"version is `5`. In `ECO0011`, a new component, `Space stabilizer`, is added," +" and the changes are applied. This means the current |BOM| version has " +"become `6`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Apply changes to an ECO to update the production BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:159 +msgid "" +"This means `ECO0012` is modifying an outdated |BOM|. As shown in the " +":guilabel:`Previous Eco Bom Changes` tab, the |BOM| is missing the `Space " +"stabilizer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:162 +msgid "" +"To ensure the changes applied by `ECO0011` are kept when the changes occur " +"in `ECO0012`, click the :guilabel:`Apply Rebase` button to apply the " +"previous |ECO| changes, without affecting the changes already made to " +"`ECO0012`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "" +"Click the *Apply Rebase* button to update the BOM to match the production " +"BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management.rst:3 +msgid "Project management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:3 +msgid "Approvals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:10 +msgid "" +"Notify stakeholders and managers automatically by assigning approvers to " +"stages of :ref:`engineering change orders ` (ECOs) under review. " +"Changes can only be applied after the assigned approver accepts them. " +"Approvals ensure reviews by team members, which prevents mistakes and " +"premature actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:16 +msgid ":ref:`Stage configuration `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:19 +msgid "Add approver" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:21 +msgid "" +"To add an approver, first go to the :menuselection:`PLM app`, and click on " +"the project card of an ECO type to open the Gantt view of the |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:24 +msgid "" +"On the :guilabel:`Engineering Change Orders` page, hover over the intended " +"stage, and select the :guilabel:`⚙️ (gear)` icon. Then, click " +":guilabel:`Edit` to open a pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:28 +msgid "" +"Approvers can be added to any stage, but it's strongly recommended to assign" +" them to the *verification* stage, which comes before the *closing* stage, " +"where |ECOs| are applied, and the :abbr:`BoM (Bill of Materials)` version is" +" updated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:32 +msgid "" +"See the documentation about :ref:`stage types ` for " +"more information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:36 +msgid "" +"In the :guilabel:`Edit` stage pop-up window, click the :guilabel:`Add a " +"line` button, located under :guilabel:`Approvals`. Then, type in the " +"approver's position (or title) under :guilabel:`Role` (e.g. `Engineering " +"Manager`, `Quality Team`, etc.), and select the relevant :guilabel:`User` " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:41 +msgid "" +"Next, set the :guilabel:`Approval Type` to :guilabel:`Is required to " +"approve`, :guilabel:`Approves, but the approval is optional`, or " +":guilabel:`Comments only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:45 +msgid "" +"Assign the `CTO`, \"Mitchell Admin,\" as a required approver for |ECOs| in " +"the `Validated` stage in the `New Product Introduction` ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:48 +msgid "" +"Approvals from the quality and marketing teams are **not** required to apply" +" changes to the |ECO| because their :guilabel:`Approval Type` is set to " +":guilabel:`Approves, but the approval is optional` and :guilabel:`Comments " +"only`, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "" +"Set an approver that \"Is required to approve\" ECOs in the \"Validated\" " +"stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:57 +msgid "Manage approvals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:59 +msgid "" +"Approvers can easily track their to-do approvals by navigating to the " +":menuselection:`PLM app`, and looking at the card for an ECO type, which " +"shows the count of open tasks assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:62 +msgid "Here's what each button on an ECO project card does:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:64 +msgid "" +"The :guilabel:`# Engineering Changes` button displays a count of in-progress" +" |ECOs| of this ECO type. Clicking the button opens the Gantt view of the " +":guilabel:`Engineering Change Orders` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:66 +msgid "" +":guilabel:`My Validations` displays a count of |ECOs| the approver must " +"accept or reject. Clicking on this button displays |ECOs| pending approval " +"or rejected (marked with the red :guilabel:`Blocked` state)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:69 +msgid "" +"The :guilabel:`All Validations` button shows the count of |ECOs| awaiting " +"approval or rejected by any approver. Clicking it reveals these pending " +"|ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:71 +msgid "" +":guilabel:`To Apply` displays a count of |ECOs| to which the user needs to " +"apply changes. Clicking on the button displays all the |ECOs| to approve, " +"and apply changes to, in the verification stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:75 +msgid "" +"|ECOs| marked with the green :guilabel:`Done` stage have already been " +"approved, and the user just needs to click on the |ECO| to enter the form " +"view, and click the :guilabel:`Apply Changes` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "" +"Display count of validations to-do and buttons to open filtered list of " +"ECOs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:84 +msgid "Approve ECOs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:86 +msgid "" +"Navigate to an |ECO| in a verification stage, while logged in as the " +"assigned approver, to see the :guilabel:`Approve`, :guilabel:`Reject`, and " +":guilabel:`Apply Changes` buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:89 +msgid "" +"To approve the |ECO|, and apply the changes onto the production :abbr:`BoM " +"(Bill of Materials)`, click :guilabel:`Approve`, and then :guilabel:`Apply " +"Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:92 +msgid "" +"Note that the :guilabel:`Apply Changes` button will **not** work unless the " +":guilabel:`Approve` button was clicked first. Additionally, the chatter logs" +" the history of the clicked buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:96 +msgid "" +"When the :guilabel:`Approval Type` is **not** set to :guilabel:`Is required " +"to approve`, approval from the associated user is not needed before applying" +" changes with the :guilabel:`Apply Changes` button. Thus, the " +":guilabel:`Apply Changes` button **will work** without requiring the " +":guilabel:`Approve` button to be clicked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:102 +msgid "Automated activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:104 +msgid "" +"When an |ECO| is moved to a verification stage, a planned activity is " +"automatically created for assigned approvers to review the |ECO|. Approvers " +"receive a notification in their activities inbox, accessible through the " +":guilabel:`🕘 (clock)` icon at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:108 +msgid "" +"In the to-do task list, the :guilabel:`Engineering Change Order (ECO)` " +"notification displays the number of activities marked :guilabel:`Late`, " +":guilabel:`Today`, and :guilabel:`Future`. Clicking on each of these buttons" +" shows a filtered Gantt view of the respective |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:113 +msgid "" +"Scheduled activities are shown as a number on the :guilabel:`🕘 (clock)` " +"icon, with `5` |ECOs| pending approval :guilabel:`Today`. Currently, there " +"are `0` :guilabel:`Late` or :guilabel:`Future` |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Show scheduled approvals notifications for the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:121 +msgid "" +"By clicking a pending |ECO|, a *planned activity* for :guilabel:`ECO " +"Approval` is recorded in the chatter. Click on the :guilabel:`i (Info)` icon" +" to view additional information, including the approval's " +":guilabel:`Created` date, the approver :guilabel:`Assigned to` it, and the " +"due date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "Show additional details of the planned ECO approval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:130 +msgid "Follow-up activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:132 +msgid "" +"When |ECOs| are rejected, tasks need to be assigned to project members for " +"required modifications before |ECO| approval. To create tasks with " +"deadlines, navigate to the rejected |ECO| form, and go to the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:136 +msgid "" +"Select the :guilabel:`Mark Done` button in the :guilabel:`Planned " +"Activities` section of the chatter to close the activity, and open a pop-up " +"window for creating tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "" +"Show *Mark Done* window to show *Done & Schedule Next*, *Done*, and *Discard* buttons to\n" +"close the planned activity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:144 +msgid "" +"In the :guilabel:`Mark Done` window, click :guilabel:`Done & Schedule Next` " +"to open a new :guilabel:`Schedule an Activity` window. Next, set the " +":guilabel:`Assigned to` team member and the :guilabel:`Due Date` for " +"completing the changes. Provide task details in the :guilabel:`Summary` " +"field and the text box. Click the :guilabel:`Schedule` button to close the " +"window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:149 +msgid "" +"After closing the window, on the |ECO| form, move the |ECO| back one stage. " +"Doing so ensures that when the team member completes the changes, and " +"returns the |ECO| to the verification stage, a new :guilabel:`ECO Approval` " +"task is created for the approver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:154 +msgid "" +"The approver creates an activity for the :guilabel:`Responsible` of the " +"|ECO|, `Laurie Poiret`, that details the changes required for the approver " +"to :guilabel:`Accept` the |ECO|. Clicking the :guilabel:`Schedule` button " +"creates a planned activity for Laurie due on `08/15/2023`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Create a scheduled activity for follow-up changes to a rejected ECO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:8 +msgid "Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:10 +msgid "" +"**Odoo Purchase** helps keep track of purchase agreements, quotations, and " +"purchase orders. Learn how to monitor purchase tender, automate " +"replenishment, and follow up on your orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:14 +msgid "`Odoo Tutorials: Purchase `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:3 +msgid "Analyze the performance of your purchases" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:5 +msgid "" +"If your company regularly purchases products, you have several reasons to " +"track and analyze your performance. The insights gathered can help you to " +"better forecast and plan your future orders. For example, you can assess if " +"your business is dependent on particular vendors, and the data can help you " +"negotiate discounts on prices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:11 +msgid "Generate customized reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:13 +msgid "" +"Go to *Reporting* to access the purchase analysis. Simply by accessing the " +"reporting dashboard, you can get a quick overview of your actual " +"performance. By default, the reporting dashboard displays a line chart " +"presenting the untaxed amount of your purchase orders per day, and below it," +" key metrics and a pivot table." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting dashboard in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:22 +msgid "" +"While the data initially presented is useful, there are several tools and " +"features you can use to get even more insights on your purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:26 +msgid "Use filters to select the data you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:28 +msgid "" +"Odoo offers several default filters you can use and combine by clicking on " +"*Filters*. When you select one or several filters, Odoo looks for all the " +"orders that match at least one of the filters you have chosen and populates " +"the chart, key metrics, and pivot table with the data. The pre-configured " +"filters are:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:33 +msgid "All *Requests for Quotation*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:35 +msgid "All *Purchase Orders*, except canceled ones" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:37 +msgid "" +"*Confirmation Date Last Year* includes all orders that were confirmed the " +"previous year, canceled purchase orders included" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:40 +msgid "" +"*Order Date* includes all orders - request for quotations and purchases " +"orders (canceled ones included) - depending on their date of creation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:43 +msgid "" +"*Confirmation Date* includes all confirmed orders, canceled ones included, " +"depending on their date of confirmation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:47 +msgid "" +"When you have to select a period, you can use multiple years, and, with at " +"least one year selected, multiple quarters and the three most recent months." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 +msgid "" +"If you use the *Order Date* or *Confirmation Date* filters, the *Comparison*" +" feature appears next to *Filters*. It enables you to compare the period you" +" filtered with the previous one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting filters in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:59 +msgid "Add custom filters" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:61 +msgid "" +"Thanks to the 31 filtering options to choose from, the possibilities of your" +" customizing your dataset are almost limitless. Go to " +":menuselection:`Filters --> Add Custom Filter`, specify the condition the " +"filtering option should meet (e.g. *is equal to*, *contains*, etc.), and " +"click on *Apply*. If you want to select orders matching several conditions " +"simultaneously (*and* operator), repeat the process to add another custom " +"filter. If you want to use the *or* operator, don't click on *Apply*, and " +"click on *Add a condition* instead. Once you have added all the desired " +"filtering options, click on *Apply*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Custom reporting filter in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:74 +msgid "" +"To avoid having to recreate custom filters every time, save them by clicking" +" on :menuselection:`Favorites --> Save current search --> Save`. The " +"customized search filter can then be accessed by clicking on *Favorites* or " +"can even be set as the default filter when you open the reporting dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:80 +msgid "Measure exactly what you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:82 +msgid "" +"Before selecting what you want to measure, you need to decide whether you " +"prefer using the graph view or the pivot view. By default, the dashboard " +"presents both views. However, the measures you select won't be applied to " +"both views. You can access each view separately by clicking on the icons at " +"the top right of the dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Switch reporting view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:92 +msgid "Visualize your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:94 +msgid "" +"You can transform the main graph in just a click by selecting one of the " +"three charts: bar, line or pie. Fourteen different measures are available, " +"but you can only use one at a time. However, you can group the measure using" +" one or several of the 19 *Groups*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting graph view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:102 +msgid "" +"For bar and line charts, the selected measure is your y-axis, and the first " +"group you select is used to create the x-axis. Adding more group adds " +"additional lines (line chart) or transforms your bar chart into a stacked " +"bar chart. For pie charts, the more groups you select, the more slices are " +"displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:108 +msgid "Explore your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:110 +msgid "" +"The pivot table view enables you to explore your data in great detail. " +"Unlike the graph view, the pivot table enables you to add several measures " +"at the same time. By clicking on *Measures* or on the **+** sign in the " +"*Total* column, you can add as many as you want, each assigned to a new " +"column. By clicking on the **+** sign in the *Total* row, you can add " +"*Groups*. If you click on a group's **+** sign, you can add a sub-group, and" +" so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Pivot table view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:121 +msgid "" +"You can insert your pivot table's data directly in the Spreadsheet app or " +"export it as an Excel file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals.rst:5 +msgid "Manage deals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:3 +msgid "Use blanket orders to create purchase agreements with vendors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:5 +msgid "" +"Blanket orders are long-term purchase agreements between a company and a " +"vendor to deliver products on a recurring basis with predetermined pricing. " +"Using blanket orders are useful when products are always purchased from the " +"same vendor, but in different quantities at different times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:9 +msgid "" +"By simplifying the ordering process, blanket orders not only save time, they" +" also save money, since they can be advantageous when negotiating bulk " +"pricing with vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:13 +msgid ":doc:`calls_for_tenders`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:16 +msgid "Create a new blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:18 +msgid "" +"To create blanket orders, the *Purchase Agreements* feature first needs to " +"be enabled in the settings of the *Purchase* app. To do this, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and under the " +":guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase " +"Agreements`. Doing so will enable the ability to create blanket orders, as " +"well as alternative requests for quotation (RFQs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Purchase Agreements enabled in the Purshase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:28 +msgid "" +"To create a blanket order, go to :menuselection:`Purchase --> Orders --> " +"blanket orders`, and click :guilabel:`New`. This creates (and navigates to) " +"a new blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:31 +msgid "" +"From this new blanket order form, different fields and settings can be " +"configured, so there are pre-determined rules that the recurring long-term " +"agreement must follow:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:34 +msgid "" +":guilabel:`Purchase Representative`: is the user assigned to this specific " +"blanket order. By default, this is the user who created the agreement; the " +"user can be changed directly from the drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:37 +msgid "" +":guilabel:`Agreement Type`: is the type of purchase agreement this blanket " +"order is classified as. In Odoo, blanket orders are the only official " +"purchase agreement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:39 +msgid "" +":guilabel:`Vendor`: is the supplier to whom this agreement is tied, either " +"once or on a recurring basis. The vendor can be selected directly from the " +"drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:41 +msgid "" +":guilabel:`Currency`: is the agreed-upon currency that will be used for this" +" exchange. If multiple currencies have been activated in the database, the " +"currency can be changed from the drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:44 +msgid "" +":guilabel:`Agreement Deadline`: is the date that this purchase agreement " +"will be set to expire on (if desired). If this blanket order should not " +"expire, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:46 +msgid "" +":guilabel:`Ordering Date`: is the date that this blanket order should be " +"placed on if a new quotation is created directly from the blanket order " +"form. If a new quotation is created, this value will automatically populate " +"the *Order Deadline* field on the :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:50 +msgid "" +":guilabel:`Delivery Date`: is the expected delivery date that the products " +"included in an :abbr:`RFQ (Request for Quotation)` created directly from the" +" blanket order form will be expected to arrive. If a new quotation is " +"created, this value will automatically populate the *Expected Arrival* field" +" on the :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:54 +msgid "" +":guilabel:`Source Document`: is the source purchase order (PO) that this " +"blanket order will be tied to. If this blanket order should not be tied to " +"any existing :abbr:`POs (Purchase Orders)`, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:57 +msgid "" +":guilabel:`Company`: is the company assigned to this specific blanket order." +" By default, this is the company that the user creating the blanket order is" +" listed under. If the database is not a multi-company database, this field " +"can not be changed, and will default to the only company listed in the " +"database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New blanket order purchase agreement with added products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:66 +msgid "" +"Once all relevant fields have been filled out, click :guilabel:`Add a line` " +"to add products under the :guilabel:`Product` column. Then, change the " +"quantity of each product in the :guilabel:`Quantity` column (if desired), " +"and set a price in the :guilabel:`Unit Price` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:71 +msgid "" +"When adding products to a new blanket order, the pre-existing prices of " +"products will not be added automatically to the product lines. The prices " +"must be manually assigned by changing the value in the :guilabel:`Unit " +"Price` column to an agreed-upon price with the listed vendor. Otherwise, the" +" price will remain **0**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:76 +msgid "" +"To view and change the default purchase agreement settings for blanket " +"orders directly from the blanket order form, click the :guilabel:`internal " +"link (arrow icon)` next to the :guilabel:`Agreement Type` field where " +":guilabel:`Blanket Order` is listed. This navigates to the blanket order " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:81 +msgid "" +"From here, the settings for blanket orders can be edited. Under the " +":guilabel:`Agreement Type` section, the name of the :guilabel:`Agreement " +"Type` can be changed (if desired), and the :guilabel:`Agreement Selection " +"Type` can be changed, as well. There are two options that can be activated " +"for the type of selection:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:86 +msgid "" +":guilabel:`Select only one RFQ (exclusive)`: when a purchase order is " +"confirmed, the remaining purchase orders will be canceled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:88 +msgid "" +":guilabel:`Select multiple RFQ (non-exclusive)`: when a purchase order is " +"confirmed, remaining purchase orders will ***not** be canceled. Instead, " +"multiple purchase orders are allowed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:91 +msgid "" +"Under the :guilabel:`Data For New Quotations` section, the settings for how " +"product lines and quantities will be populated on new quotations using this " +"purchase agreeement can be changed next to the :guilabel:`Lines` and " +":guilabel:`Quantities` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Purchase Agreement type edit screen for blanket orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:99 +msgid "There are two options that can be activated for :guilabel:`Lines`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:101 +msgid "" +":guilabel:`Use lines of agreement`: when creating a new quotation, the " +"product lines will pre-populate with the same products listed on the blanket" +" order, if said blanket order is chosen on the new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:104 +msgid "" +":guilabel:`Do not create RfQ lines automatically`: when creating a new " +"quotation and selecting an existing blanket order, the settings will carry " +"over to the new quotation, but the product lines will not populate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:108 +msgid "" +"And, there are two options that can be activated for :guilabel:`Quantities`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:110 +msgid "" +":guilabel:`Use quantities of agreement`: when creating a new quotation, the " +"product quantities listed on the blanket order will pre-populate on the " +"product lines, if said blanket order is chosen on the new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:113 +msgid "" +":guilabel:`Set quantities manually`: when creating a new quotation and " +"selecting an existing blanket order, the product lines will pre-populate, " +"but all quantities will be set to **0**. The quantities will need to be " +"manually set by the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:117 +msgid "" +"Once the desired changes have been made (if any), click :guilabel:`New` (via" +" the breadcrumbs, at the top of the page) to navigate back to the blanket " +"order form, and click :guilabel:`Confirm` to save this new purchase " +"agreement. Once confirmed, the blanket order changes from *Draft* to " +"*Ongoing*, meaning this agreement can be selected and used when creating new" +" :abbr:`RFQs (Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:124 +msgid "" +"After creating and confirming a blanket order, products, quantities, and " +"prices can still be edited, added, and removed from the purchase agreement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:128 +msgid "" +"Create a new :abbr:`RFQ (Request for Quotation)` from the blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:130 +msgid "" +"After confirming a blanket order, new quotations can be created directly " +"from the blanket order form that will use the rules set on the form and pre-" +"populate the new quotation with the correct information. Additionally, this " +"new quotation will be automatically linked to this blanket order form via " +"the :guilabel:`RFQs/Orders` smart button at the top right of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:135 +msgid "" +"To create a new quotation from the blanket order form, click :guilabel:`New " +"Quotation`. This creates (and navigates to) a new :abbr:`RFQ (Request for " +"Quotation)`, that is pre-populated with the correct information, depending " +"on the settings configured on the blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:139 +msgid "" +"From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send" +" by Email` to compose and send an email to the listed vendor; click " +":guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once" +" ready, click :guilabel:`Confirm Order` to confirm the purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New quotation with copied products and rules from blanket order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:147 +msgid "" +"Once the :abbr:`PO (Purchase Order)` has been confirmed, click back to the " +"blanket order form (via the breadcrumbs, at the top of the page). From the " +"blanket order form, there is now one :abbr:`RFQ (Request for Quotation)` " +"listed in the :guilabel:`RFQs/Orders` smart button at the top right of the " +"form. Click the :guilabel:`RFQs/Orders` smart button to see the purchase " +"order that was just created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "RFQs and Orders smart button from blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:157 +msgid "Create a new blanket order from an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:159 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:49 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:148 +msgid "" +"To create a new :abbr:`RFQ (Request for Quotation)`, navigate to the " +":menuselection:`Purchase` app, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:162 +msgid "" +"Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a" +" vendor from the drop-down menu next to the :guilabel:`Vendor` field, and " +"click :guilabel:`Add a product` to select a product from the drop-down menu " +"in the :guilabel:`Product` column. Then, set the desired purchase quantity " +"in the :guilabel:`Quantity` column, and change the purchase price in the " +":guilabel:`Unit Price` column, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:168 +msgid "" +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item. Repeat these steps to" +" add as many additional options as desired, including the :guilabel:`UoM` " +"(Units of Measure) to purchase the products in, and the :guilabel:`Expected " +"Arrival` date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:173 +msgid "" +"Before confirming the new quotation and creating a purchase order, click the" +" drop-down menu next to the :guilabel:`Blanket Order` field, and type a new " +"name for the new blanket order. This creates a brand new purchase agreement," +" and saves the information entered in the fields of the purchase order form," +" as well as the product information entered on the product lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:178 +msgid "" +"From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send" +" by Email` to compose and send an email to the listed vendor; click " +":guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once" +" ready, click :guilabel:`Confirm Order` to confirm the :abbr:`PO (purchase " +"order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New blanket order created directly from quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:188 +msgid "" +"To see the newly-created blanket order purchase agreement, go to " +":menuselection:`Orders --> Blanket Orders`, and click into the new blanket " +"order. From here, settings and rules can be changed, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:193 +msgid "Blanket orders and replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:195 +msgid "" +"Once a blanket order is confirmed, a new vendor line is added under the " +":guilabel:`Purchase` tab of of the products included in the :abbr:`BO " +"(Blanket Order)`. This makes blanket orders useful with :doc:`automated " +"replenishment <../../purchase/products/reordering>`, because information " +"about the :guilabel:`Vendor`, :guilabel:`Price`, and the " +":guilabel:`Agreement` are referenced on the vendor line. This information is" +" used to determine where, when, and for what price this product could be " +"replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Product form with replenishment agreement linked to blanket order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:3 +msgid "Create alternative requests for quotation for multiple vendors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:5 +msgid "" +"Sometimes, companies might want to request offers from multiple vendors at " +"the same time, by inviting those vendors to submit offers for similar goods " +"or services all at once. This helps companies to select the cheapest (and " +"fastest) vendors, depending on their specific business needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:9 +msgid "" +"In Odoo, this can be done by adding alternative requests for quotation " +"(RFQs) for different vendors. Once a response is received from each vendor, " +"the product lines from each :abbr:`RFQ (Request for Quotation)` can be " +"compared, and a decision can be made for which products to purchase from " +"which vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:14 +msgid "" +"Sometimes referred to as a *call for tender*, this process is primarily used" +" by organizations in the public sector, who are legally bound to use it when" +" making a purchase. However, private companies can also use alternative " +":abbr:`RFQs (Requests for Quotation)` to spend money efficiently, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:20 +msgid ":doc:`blanket_orders`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:23 +msgid "Configure purchase agreement settings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:25 +msgid "" +"To create alternative :abbr:`RFQs (Requests for Quotation)` directly from a " +"quotation, the *Purchase Agreements* feature first needs to be enabled in " +"the settings of the *Purchase* app. To do this, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and under the " +":guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase " +"Agreements`. Doing so will enable the ability to create alternative " +":abbr:`RFQs (Requests for Quotation)`, as well as the ability to create " +"*blanket orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Purchase Agreements enabled in the Purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:37 +msgid "" +"To save time on a *call for tender*, custom vendors, prices, and delivery " +"lead times can be set in the :guilabel:`Purchase` tab on a product form. To " +"do so, navigate to :menuselection:`Purchase --> Products --> Products`, and " +"select a product to edit. From the product form, click the " +":guilabel:`Purchase tab`, then click :guilabel:`Add a line`. From the drop-" +"down menu, choose a vendor to set under the :guilabel:`Vendor` column, and " +"set a :guilabel:`Price` and :guilabel:`Delivery Lead Time` if desired. " +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:47 +msgid "Create an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:52 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:151 +msgid "" +"Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a" +" vendor from the drop-down next to the :guilabel:`Vendor` field, and click " +":guilabel:`Add a product` to select a product from the drop-down menu in the" +" :guilabel:`Product` column. Then, set the desired purchase quantity in the " +":guilabel:`Quantity` column, and change the purchase price in the " +":guilabel:`Unit Price` column, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:58 +msgid "" +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item. Repeat these steps to" +" add as many options as desired, including the :guilabel:`UoM` (Units of " +"Measure) to purchase the products in, and the :guilabel:`Expected Arrival` " +"date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:63 +msgid "" +"Once ready, click :guilabel:`Send by Email`. This causes a " +":guilabel:`Compose Email` pop-up window to appear, wherein the message to " +"the vendor can be customized. Once ready, click :guilabel:`Send`. This turns" +" the :abbr:`RFQ (Request for Quotation)` into a purchase order (PO), and " +"sends an email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Compose and send quotation email pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:73 +msgid "" +"Sending emails to each vendor can be useful when creating alternative " +":abbr:`RFQs (Requests for Quotation)`, because vendors can confirm if their " +"past prices still hold today, which can help companies choose the best " +"offers for them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:78 +msgid "Create alternatives to an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:80 +msgid "" +"Once a :abbr:`PO (Purchase Order)` is created and sent by email to a vendor," +" alternative :abbr:`RFQs (Requests for Quotation)` can be created and sent " +"to additional, alternate vendors to compare prices, delivery times, and " +"other factors to make a decision from which vendors to order which products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:85 +msgid "" +"To create alternative :abbr:`RFQs (Requests for Quotation)`, click the " +":guilabel:`Alternatives` tab from the purchase order form, then click " +":guilabel:`Create Alternative`. When clicked, a :guilabel:`Create " +"alternative` pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Calls for tenders pop-up to create alternative quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:93 +msgid "" +"From this window, select a new/different vendor from the drop-down menu next" +" to the :guilabel:`Vendor` field to assign this alternative quotation to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:96 +msgid "" +"Next to this, there is a :guilabel:`Copy Products` checkbox that is selected" +" by default. When selected, the product quantities of the original :abbr:`PO" +" (Purchase Order)` are copied to the alternative. For this first alternative" +" quotation, leave the checkbox checked. Once finished, click " +":guilabel:`Create Alternative`. This creates (and navigates to) a new " +":abbr:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:101 +msgid "" +"Since the :guilabel:`Create Alternative` checkbox was left checked, this new" +" purchase order form is already populated with the same products, " +"quantities, and other details as the previous, original :abbr:`PO (Purchase " +"Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:106 +msgid "" +"When the :guilabel:`Copy Products` checkbox is selected while creating an " +"alternative quotation, additional products do not need to be added on the " +"purchase order form unless desired. However, if a chosen vendor is listed in" +" the :guilabel:`Vendor` column under the :guilabel:`Purchase` tab on a " +"product form included in the purchase order, the values set on the product " +"form carry over to the :abbr:`PO (Purchase Order)`, and have to be changed " +"manually, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:112 +msgid "" +"Once ready, create a second alternative quotation by clicking the " +":guilabel:`Alternatives` tab, and once again, click :guilabel:`Create " +"Alternative`. This causes the :guilabel:`Create alternative` pop-up window " +"to appear again. This time, choose a different vendor from the drop-down " +"menu next to :guilabel:`Vendor`, and this time, *uncheck* the " +":guilabel:`Copy Products` checkbox. Then, click :guilabel:`Create " +"Alternative`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:119 +msgid "" +"If an alternative quotation needs to be removed from the " +":guilabel:`Alternatives` tab, they can be individually removed by clicking " +"on the :guilabel:`Remove (X)` icon at the end of their row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:122 +msgid "" +"This creates a third, new purchase order. But, since the product quantities " +"of the original :abbr:`PO (Purchase Order)` were *not* copied over, the " +"product lines are empty, and new products need to be added by clicking " +":guilabel:`Add a product`, and selecting the desired products from the drop-" +"down menu. Once the desired number of products are added, click " +":guilabel:`Send by Email`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Blank alternative quotation with alternatives in breadcrumbs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:131 +msgid "" +"This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the" +" message to the vendor can be customized. Once ready, click :guilabel:`Send`" +" to send an email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:135 +msgid "" +"From this newest purchase order form, click the :guilabel:`Alternatives` " +"tab. Under this tab, all three purchase orders can be seen in the " +":guilabel:`Reference` column. Additionally, the vendors are listed under the" +" :guilabel:`Vendor` column, and the order :guilabel:`Total` and " +":guilabel:`Status` of the orders are in the rows, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:141 +msgid "Link a new :abbr:`RFQ (Request for Quotation)` to existing quotations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:143 +msgid "" +"Creating alternative quotations directly from a purchase order form under " +"the :guilabel:`Alternatives` tab is the easiest way to create and link " +"quotations. However, separate :abbr:`RFQs (Requests for Quotation)` can also" +" be linked *after* the fact, even if they are created completely separately " +"at first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:157 +msgid "" +"Once ready, click :guilabel:`Send by Email`. This causes a " +":guilabel:`Compose Email` pop-up window to appear, wherein the message to " +"the vendor can be customized. Once ready, click :guilabel:`Send` to send an " +"email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:161 +msgid "" +"Then, click the :guilabel:`Alternatives` tab once more. Since this new " +":abbr:`PO (Purchase Order)` was created separately, there are no other " +"orders linked yet. To link this order with the alternatives created " +"previously, click :guilabel:`Link to Existing RfQ` on the first line in the " +":guilabel:`Vendor` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "pop-up to link new quotation to existing RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:170 +msgid "" +"This causes an :guilabel:`Add: Alternative POs` pop-up window to appear. " +"Select the three purchase orders created previously, and click " +":guilabel:`Select`. All of these orders are now copied to this :abbr:`PO " +"(Purchase Order)` under the :guilabel:`Alternatives` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:175 +msgid "" +"If a large number of purchase orders are being processed and the previous " +":abbr:`POs (Purchase Orders)` can't be located, try clicking " +":menuselection:`Group By --> Vendor` under the search bar at the top of the " +"pop-up window to group by the vendors selected on the previous orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:181 +msgid "Compare product lines" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:183 +msgid "" +"When there are multiple :abbr:`RFQs (Requests for Quotation)` linked as " +"alternatives, they can be compared side-by-side in order to determine which " +"vendors offer the best deals on which products. To compare each quotation, " +"go to the :menuselection:`Purchase` app, and select one of the quotations " +"created previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:188 +msgid "" +"Then, click the :guilabel:`Alternatives` tab to see all the linked " +":abbr:`RFQs (Requests for Quotation)`. Next, under the :guilabel:`Create " +"Alternative` tab, click :guilabel:`Compare Product Lines`. This navigates to" +" a Compare Order Lines page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Compare Product Lines page for alternative RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:196 +msgid "" +"The Compare Order Lines page, by default, groups by :guilabel:`Product`. " +"Each product included in any of the :abbr:`RFQs (Requests for Quotation)` is" +" displayed in its own drop-down, along with all of the :abbr:`PO (Purchase " +"Order)` numbers in the :guilabel:`Reference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:200 +msgid "" +"Additional columns on this page include the :guilabel:`Vendor` from which " +"products were ordered, the :guilabel:`Status` of the quotation (i.e., RFQ, " +"RFQ Sent); the :guilabel:`Quantity` of products ordered from each vendor; " +"the :guilabel:`Unit Price` per product and :guilabel:`Total` price of the " +"order, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:206 +msgid "" +"To remove product lines from the Compare Order Lines page, click " +":guilabel:`Clear` at the far right end of that product line's row. This " +"removes this product as a chooseable option from the page, and changes the " +":guilabel:`Total` price of that product on the page to **0**. On the " +"purchase order form in which that product was included, its ordered quantity" +" is changed to **0**, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:212 +msgid "" +"Once the best offers have been identified, at the end of each row, " +"individual products can be selected by clicking :guilabel:`Choose`. Once all" +" the desired products have been chosen, click :guilabel:`Requests for " +"Quotation` (in the breadcrumbs, at the top of the page) to navigate back to " +"an overview of all :abbr:`RFQs (Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:218 +msgid "Cancel (or keep) alternatives" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:220 +msgid "" +"Now that the desired products have been chosen, based on which vendors " +"provided the best offer, the other :abbr:`RFQs (Requests for Quotation)` " +"(from which no products were chosen) can be canceled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:223 +msgid "" +"Under the :guilabel:`Total` column, at the far right of each row, the orders" +" from which no products were chosen have automatically had their total cost " +"set to **0**. Although they haven't been canceled yet, this means that they " +"can ultimately be canceled without repercussions, *after* the desired " +"purchase orders have been confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Canceled quotations in the Purchase app overview." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:232 +msgid "" +"To confirm a quotation that contains the chosen product quantities, click " +"into one. Then, click :guilabel:`Confirm Order`. This causes an " +":guilabel:`Alternative Warning` pop-up window to appear. From there, either " +":guilabel:`Cancel Alternatives` or :guilabel:`Keep Alternatives` can be " +"clicked. If this :abbr:`PO (Purchase Order)` should *not* be confirmed, " +"click :guilabel:`Cancel`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:237 +msgid "" +":guilabel:`Cancel Alternatives` automatically cancels the alternative " +"purchase orders. :guilabel:`Keep Alternatives` keeps the alternative " +"purchase orders open, so they can still be accessed if any additional " +"product quantities need to be ordered. Once all products are ordered, " +":guilabel:`Cancel Alternatives` can be selected from whichever :abbr:`PO " +"(Purchase Order)` is open." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:242 +msgid "" +"To view a detailed form of one of the :abbr:`RFQs (Requests for Quotation)` " +"listed, click the line item for that quotation. This causes an " +":guilabel:`Open: Alternative POs` pop-up window to appear, from which all " +"details of that particular quotation can be viewed. Click :guilabel:`Close` " +"when finished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Keep or cancel pop-up for alternative RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:251 +msgid "" +"From the :guilabel:`Alternative Warning` pop-up window, click " +":guilabel:`Keep Alternatives` to keep all alternative quotations open for " +"now. Then, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at " +"the top of the page) to navigate back to an overview of all :abbr:`RFQs " +"(Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:256 +msgid "" +"Click into the remaining quotation(s) that contain products that need to be " +"ordered, and click :guilabel:`Confirm Order`. This causes the " +":guilabel:`Alternative Warning` pop-up window to appear again. This time, " +"click :guilabel:`Cancel Alternatives` to cancel all other alternative " +":abbr:`RFQs` linked with this quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:261 +msgid "" +"Finally, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at " +"the top of the page) to navigate back to an overview of all :abbr:`RFQs " +"(Requests for Quotation)`. The canceled orders can be seen greyed out and " +"listed with a :guilabel:`Cancelled` status under the :guilabel:`Status` " +"column at the far right of their rows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:266 +msgid "" +"Now that all product quantities have been ordered, the purchase process can " +"be followed, and continued to completion, until the products are received " +"into the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15 +msgid "Bill control policies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:5 +msgid "" +"In Odoo, the *bill control* policy determines the quantities billed by " +"vendors on every purchase order, for ordered or received quantities. The " +"policy selected in the settings will act as the default value and will be " +"applied to any new product created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:12 +msgid "" +"To view the default bill control policy and make changes, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and scroll down to" +" the :guilabel:`Invoicing` section. Here, there are the two :guilabel:`Bill " +"Control` policy options: :guilabel:`Ordered quantities` and " +":guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "" +"The policy selected will be the default for any new product created. The " +"definition of each policy is as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:20 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +msgid "" +":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase " +"order is confirmed. The products and quantities in the purchase order are " +"used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:22 +msgid "" +":guilabel:`Received quantities`: a bill is created only *after* part of the " +"total order has been received. The products and quantities *received* are " +"used to generate a draft bill. An error message will appear if creation of a" +" vendor bill is attempted without receiving anything." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Bill control policy draft bill error message." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:31 +msgid "" +"If one or two products need a different control policy, the default bill " +"control setting can be overridden by going to the :guilabel:`Purchase` tab " +"in a product's template and modifying its :guilabel:`Control Policy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36 +msgid "Example flow: Ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:38 +msgid "" +"To complete an example workflow using the *ordered quantities* bill control " +"policy, first go to :menuselection:`Purchase --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Invoicing` section, and select " +":guilabel:`Ordered quantities`. Then, :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:42 +msgid "" +"In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for " +"Quotation)`. Fill out the information on the quotation form, add products to" +" the invoice lines, and click :guilabel:`Confirm Order`. Then, click " +":guilabel:`Create Bill`. Since the policy is set to *ordered quantities*, " +"the draft bill can be confirmed as soon as it is created, without any " +"products actually being received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:48 +msgid "Example flow: Received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:50 +msgid "" +"To complete an example workflow using the *received quantities* bill control" +" policy, first go to :menuselection:`Purchase --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Invoicing` section, and select " +":guilabel:`Received quantities`. Then, :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:54 +msgid "" +"In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for " +"Quotation)`. Fill out the information on the quotation form, add products to" +" the invoice lines, and click :guilabel:`Confirm Order`. Then, click on the " +":guilabel:`Receipt smart button`. Set the quantities in the :guilabel:`Done`" +" column to match the quantities in the :guilabel:`Demand` column, and " +":guilabel:`Validate` the changes. Then, in the purchase order, click " +":guilabel:`Create Bill` and :guilabel:`Confirm`. Since the policy is set to " +"*received quantities*, the draft bill can be confirmed *only* when at least " +"some of the quantities are received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:63 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 +msgid "3-way matching" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:65 +msgid "" +"Activating :guilabel:`3-way matching` ensures that vendor bills are only " +"paid once some or all of the products included in the purchase order have " +"actually been received. To activate it, go to :menuselection:`Purchase --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` " +"section. Then, click :guilabel:`3-way matching: purchases, receptions, and " +"bills`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:72 +msgid "" +"3-way matching is *only* intended to work when the bill control policy is " +"set to *received quantities*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:76 +msgid "Pay vendor bills with 3-way matching" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:78 +msgid "" +"When :guilabel:`3-way matching` is activated, vendor bills will display the " +":guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When " +"a new vendor bill is created, the field will be set to :guilabel:`Yes`, " +"since a bill can't be created until at least some of the products included " +"in a purchase order have been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Draft bill should be paid field status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:88 +msgid "" +"If the total quantity of products from a purchase order has not been " +"received, Odoo only includes the products that *have* been received in the " +"draft vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:91 +msgid "" +"Draft bills can be edited to increase the billed quantity, change the price " +"of the products in the bill, and add additional products to the bill. If " +"this is done, the :guilabel:`Should Be Paid` field status will be set to " +":guilabel:`Exception`. This means that Odoo notices the discrepancy, but " +"doesn't block the changes or display an error message, since there might be " +"a valid reason for making changes to the draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:97 +msgid "" +"Once payment has been registered for a vendor bill and displays the green " +":guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status will be" +" set to :guilabel:`No`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:101 +msgid "" +"The :guilabel:`Should Be Paid` status on bills is set automatically by Odoo." +" However, the status can be changed manually by clicking the field's drop-" +"down menu inside the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:106 +msgid "View a purchase order's billing status" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:108 +msgid "" +"When a purchase order is confirmed, its :guilabel:`Billing Status` can be " +"viewed under the :guilabel:`Other Information` tab on the purchase order " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Purchase order billing status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:115 +msgid "" +"Below is a list of the different statuses that a :guilabel:`Billing Status` " +"could appear as and when they are displayed, depending on the bill control " +"policy used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 +msgid ":guilabel:`Billing Status`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 +msgid "**Conditions**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 +msgid "*On received quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 +msgid "*On ordered quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid ":guilabel:`Nothing to Bill`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid "PO confirmed; no products received" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid "*Not applicable*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid ":guilabel:`Waiting Bills`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid "All/some products received; bill not created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid "PO confirmed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid ":guilabel:`Fully Billed`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid "All/some products received; draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid "Draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3 +msgid "Manage vendor bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7 +msgid "" +"A *vendor bill* is an invoice received for products and/or services that a " +"company purchases from a vendor. Vendor bills record payables as they arrive" +" from vendors, and can include amounts owed for the goods and/or services " +"purchased, sales taxes, freight and delivery charges, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11 +msgid "" +"In Odoo, a vendor bill can be created at different points in the purchasing " +"process, depending on the *bill control* policy chosen in the *Purchase* app" +" settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17 +msgid "" +"To view and edit the default bill control policy and make changes to it, go " +"to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll " +"down to the :guilabel:`Invoicing` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21 +msgid "" +"Here, there are two :guilabel:`Bill Control` policy options: " +":guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a " +"policy is selected, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Bill control policies in purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 +msgid "" +":guilabel:`Received quantities`: a bill is only created **after** part of " +"the total order has been received. The products and quantities **received** " +"are used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37 +msgid "" +"If a product needs a different control policy, the default bill control " +"policy can be overridden by going to the :guilabel:`Purchase` tab in a " +"product's template, and modifying its :guilabel:`Control Policy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Control policy field on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48 +msgid "" +"*3-way matching* ensures vendor bills are only paid once some (or all) of " +"the products included in the purchase order have actually been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 +msgid "" +"To activate it, go to :menuselection:`Purchase app --> Configuration --> " +"Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check" +" the box next to :guilabel:`3-way matching: purchases, receptions, and " +"bills`, and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 +msgid "" +":guilabel:`3-way matching` is **only** intended to work with the " +":guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Activated three-way matching feature in purchase settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64 +msgid "Create and manage vendor bills on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +msgid "" +"When products are received into a company's warehouse, receipts are created." +" Once the company processes the received quantities, they can choose to " +"create a vendor bill directly from the warehouse receipt form. Depending on " +"the bill control policy chosen in the settings, vendor bill creation is " +"completed at different steps of the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 +msgid "With the bill control policy set to ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74 +msgid "" +"To create and manage vendor bills on receipts using the *ordered quantities*" +" bill control policy, first go to :menuselection:`Purchase app --> " +"Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new request for quotation (RFQ). Doing so reveals a blank " +":abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 +msgid "" +"On the blank detail form, add a vendor to the :abbr:`RFQ (request for " +"quotation)` in the :guilabel:`Vendor` field, and add products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 +msgid "" +"Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the " +":guilabel:`Confirm Order` button above the detail form. Doing so turns the " +":abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90 +msgid "" +"Then, click the :guilabel:`Create Bill` button to create a vendor bill for " +"the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92 +msgid "" +"Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft " +"Bill` page for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 +msgid "" +"On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify " +"the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed," +" add additional products to the :guilabel:`Product` lines by clicking " +":guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 +msgid "" +"Next, confirm the bill by clicking the :guilabel:`Confirm` button on the " +":guilabel:`Draft Bill` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103 +msgid "" +"Since the bill control policy is set to *ordered quantities*, the draft bill" +" can be confirmed as soon as it is created, before any products have been " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +msgid "" +"On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number," +" which can be used to match the bill with additional documents (such as the " +":abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> " +"Register Payment`. Doing so causes a pop-up to appear, wherein a payment " +":guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; " +"and a :guilabel:`Recipient Bank Account` can be selected from a drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the " +":guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` " +"banner to display on the :abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Vendor bill form for ordered quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122 +msgid "" +"Each vendor bill provides the option to either :guilabel:`Add Credit Note` " +"or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a " +"vendor or supplier of goods get some quantity of products back from the " +"customer to whom they were sold, while *debit notes* are reserved for goods " +"returned from the customer/buyer to the vendor or supplier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128 +msgid "With the bill control policy set to received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 +msgid "" +"If the creation of a vendor bill is attempted without receiving any " +"quantities of a product (while using the *received quantities* bill control " +"policy), an error message appears, and settings must be changed before " +"proceeding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +msgid "" +"To create and manage vendor bills on receipts using the *received " +"quantities* bill control policy, first go to :menuselection:`Purchase app " +"--> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Received quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a " +"blank :abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +msgid "" +"Finally, click the :guilabel:`Create Bill` button to create a bill for the " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 +msgid "" +"Clicking :guilabel:`Create Bill` before any products have been received will" +" cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase " +"Order` requires the receipt of at least partial quantity of the items " +"included on the order to create a vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "User error pop-up for received quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163 +msgid "" +"Next, click the :guilabel:`Receipt` smart button to view the warehouse " +"receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 +msgid "" +"On the warehouse receipt form, click :menuselection:`Validate --> Apply` to " +"mark the :guilabel:`Done` quantities. Then, navigate back to the " +":menuselection:`Purchase Order` (via the breadcrumbs), and click the " +":guilabel:`Create Bill` button on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 +msgid "" +"Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the " +":guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a " +":guilabel:`Bill Date`. If needed, add additional products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +msgid "" +"Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft " +"Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +msgid "" +"Since the bill control policy is set to *received quantities*, the draft " +"bill can **only** be confirmed when at least some of the quantities are " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the vendor " +"bill. Doing so causes a green **In Payment** banner to display on the " +":abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191 +msgid "Create and manage vendor bills in Accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 +msgid "" +"Vendor bills can also be created directly from the *Accounting* app, " +"**without** having to create a purchase order first. To do this, go to " +":menuselection:`Accounting app --> Vendors --> Bills`, and click " +":guilabel:`Create`. Doing so reveals a blank vendor bill detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197 +msgid "" +"On this blank vendor bill detail form, add a vendor in the " +":guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines " +"(under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a " +"line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any " +"other necessary information. Finally, click :guilabel:`Confirm` to confirm " +"the bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 +msgid "" +"From here, click the :guilabel:`Journal Items` tab to view (or change) the " +":guilabel:`Account` journals that were populated based on the configuration " +"on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206 +msgid "" +"Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add" +" credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` " +"number (while in :guilabel:`Edit` mode)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 +msgid "" +"Then, when ready, click :menuselection:`Register Payment --> Create Payment`" +" to complete the :guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213 +msgid "" +"To tie the draft bill to an existing purchase order, click the drop-down " +"menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase " +"order)` from the menu. The bill will auto-populate with the information from" +" the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Auto-complete drop-down list on draft vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 +msgid "Batch billing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224 +msgid "" +"Vendor bills can be processed and managed in batches in the *Accounting* " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226 +msgid "" +"To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. " +"Then, click the :guilabel:`checkbox` at the top left of the page, beside the" +" :guilabel:`Number` column, under the :guilabel:`Create` button. This " +"selects all existing vendor bills with a :guilabel:`Posted` or " +":guilabel:`Draft` :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 +msgid "" +"From here, click the :guilabel:`Action` gear icon to export, delete, or send" +" & print the bills; click the :guilabel:`Print` icon to print the invoices " +"or bills; or click :guilabel:`Register Payment` to create and process " +"payments for multiple vendor bills at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235 +msgid "" +"When :guilabel:`Register Payment` is selected, a pop-up appears. In this " +"pop-up window, select the appropriate journal in the :guilabel:`Journal` " +"field, choose a payment date in the :guilabel:`Payment Date` field, and " +"choose a :guilabel:`Payment Method`. There is also the option to " +":guilabel:`Group Payments` on this pop-up, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 +msgid "" +"When ready, click the :guilabel:`Create Payment` button, which creates a " +"list of journal entries on a separate page. This list of journal entries are" +" all tied to their appropriate vendor bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Batch billing register payment pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +msgid "" +"The :guilabel:`Register Payment` option for vendor bills in batches will " +"only work for journal entries whose :guilabel:`Status` is set to " +":guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252 +msgid "" +":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 +msgid "Products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3 +msgid "Configure reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:5 +msgid "" +"For certain products, it is necessary to ensure that there is always a " +"minimum amount available on hand at any given time. By adding a reordering " +"rule to a product, it is possible to automate the reordering process so that" +" a purchase order is automatically created whenever the amount on hand falls" +" below a set threshold." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:11 +msgid "The *Inventory* module must be installed to use reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:14 +msgid "Configure products for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:16 +msgid "" +"Products must be configured in a specific way before a reordering rule can " +"be added to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:18 +msgid "" +"Starting from the :menuselection:`Inventory`, " +":menuselection:`Manufacturing`, :menuselection:`Purchase`, or " +":menuselection:`Sales` module, navigate to :menuselection:`Products --> " +"Products` and then click :guilabel:`Create` to make a new product. " +"Alternatively, find a product that already exists in the database and click " +"into it's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:23 +msgid "" +"Next, on the product form, enable reordering by checking the :guilabel:`Can " +"be Purchased` option underneathe the :guilabel:`Product Name` field. " +"Finally, set the :guilabel:`Product Type` to `Storable Product` under the " +":guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure a product for reordering in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:32 +msgid "Add a reordering rule to a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:34 +msgid "" +"After properly configuring a product, a reordering rule can be added to it " +"by selecting the now visible :guilabel:`Reordering Rules` tab at the top of " +"that product's form, and then clicking :guilabel:`Create` on the " +":guilabel:`Reordering Rules` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Access reordering rules for a product from the product page in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:42 +msgid "" +"Once created, the reordering rule can be configured to generate purchase " +"orders automatically by defining the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:45 +msgid "" +":guilabel:`Location` specifies where the ordered quantities should be stored" +" once they are received and entered into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:47 +msgid "" +":guilabel:`Min Quantity` sets the lower threshold for the reordering rule " +"while :guilabel:`Max Quantity` sets the upper threshold. If the stock on " +"hand falls below the minimum quantity, a new purchase order will be created " +"to replenish it up to the maximum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:52 +msgid "" +"If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is " +"set to `25` and the stock on hand falls to four, a purchase order will be " +"created for 21 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:55 +msgid "" +":guilabel:`Multiple Quantity` can be configured so that products are only " +"ordered in batches of a certain quantity. Depending on the number entered, " +"this can result in the creation of a purchase order that would put the " +"resulting stock on hand above what is specified in the :guilabel:`Max " +"Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:61 +msgid "" +"If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple " +"Quantity` is set to order the product in batches of `200`, a purchase order " +"will be created for 200 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:65 +msgid "" +":guilabel:`UoM` specifies the unit of measurement by which the quantity will" +" be ordered. For discrete products, this should be set to `Units`. However, " +"it can also be set to units of measurement like `Volume` or `Weight` for " +"non-discrete products like water or bricks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure the reordering rule in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:74 +msgid "Manually trigger reordering rules using the scheduler" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:76 +msgid "" +"Reordering rules will be automatically triggered by the scheduler, which " +"runs once a day by default. To trigger reordering rules manually, navigate " +"to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-" +"up window, confirm the manual action by clicking :guilabel:`Run Scheduler`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82 +msgid "" +"Manually triggering reordering rules will also trigger any other scheduled " +"actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:85 +msgid "Manage reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:87 +msgid "" +"To manage the reordering rules for a single product, navigate to that " +"product page's form and select the :guilabel:`Reordering Rules` tab at the " +"top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:90 +msgid "" +"To manage all reordering rules for every product, go to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`. From this" +" dashboard, typical bulk actions in Odoo can be performed such as exporting " +"data or archiving rules that are no longer needed. As well, the " +":guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form " +"are available to search for and/or organize the reordering rules as desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3 +msgid "Purchase in different units of measure than sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:5 +msgid "" +"When you purchase a product, it may happen that your vendor uses a different" +" unit of measure than you do when you sell it. This can cause confusion " +"between sales and purchase representatives. It is also time-consuming to " +"convert measures manually every time. With Odoo, you can configure your " +"product once and let Odoo handle the conversion." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:10 +msgid "Consider the following examples:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:12 +msgid "" +"You purchase orange juice from an American vendor, and they use **gallons**." +" However, your customers are European and use **liters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:15 +msgid "" +"You buy curtains from a vendor in the form of **rolls** and you sell pieces " +"of the rolls to your customers using **square meters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:19 +msgid "Enable units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:21 +msgid "" +"Open your Sales app and go to :menuselection:`Configuration --> Settings`. " +"Under Product Catalog, enable *Units of Measure*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Enable the units of measure option in Odoo Sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:29 +msgid "Specify sales and purchase units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:32 +msgid "Standard units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:34 +msgid "" +"A variety of units of measure are available by default in your database. " +"Each belongs to one of the five pre-configured units of measure categories: " +"*Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:39 +msgid "" +"You can create your new units of measure and units of measure categories " +"(see next section)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:41 +msgid "" +"To specify different units of measures for sales and purchases, open the " +"Purchase app and go to :menuselection:`Products --> Products`. Create a " +"product or select an existing one. Under the product's *General Information*" +" tab, first select the *Unit of Measure* to be used for sales (as well as " +"for other apps such as inventory). Then, select the *Purchase Unit of " +"Measure* to be used for purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:47 +msgid "" +"Back to the first example, if you purchase orange juice from your vendor in " +"**gallons** and sell it to your customers in **liters**, first select *L* " +"(liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase" +" Unit of Measure*, then click on *Save*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Configure a product's units of measure in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:56 +msgid "Create new units of measure and units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:58 +msgid "" +"Sometimes you need to create your own units and categories, either because " +"the measure is not pre-configured in Odoo or because the units do not relate" +" with each other (e.g. kilos and centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:62 +msgid "" +"If you take the second example where you buy curtains from a vendor in the " +"form of **rolls** and you sell pieces of the rolls using **square meters**, " +"you need to create a new *Units of Measure Category* in order to relate both" +" units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:66 +msgid "" +"To do so, go to :menuselection:`Configuration --> Units of Measure " +"Categories`. Click on *Create* and name the category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new units of measure category in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73 +msgid "" +"The next step is to create the two units of measures. To do so, go to " +":menuselection:`Configuration --> Units of Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:76 +msgid "" +"First, create the unit of measure used as the reference point for converting" +" to other units of measure inside the category by clicking on *Create*. Name" +" the unit and select the units of measure category you just created. For the" +" *Type*, select *Reference Unit of Measure for this category type*. Enter " +"the *Rounding Precision* you would like to use. The quantity computed by " +"Odoo is always a multiple of this value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:82 +msgid "" +"In the example, as you cannot purchase less than 1 roll and won't use " +"fractions of a roll as a unit of measure, you can enter 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new reference unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89 +msgid "" +"If you use a *Rounding Precision* inferior to 0.01, a warning message might " +"appear stating that it is higher than the *Decimal Accuracy* and that it " +"might cause inconsistencies. If you wish to use a *Rounding Precision* lower" +" than 0.01, first activate the :ref:`developer mode `, then " +"go to :menuselection:`Settings --> Technical --> Database Structure --> " +"Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* " +"accordingly. For example, if you want to use a rounding precision of " +"0.00001, set *Digits* to 5." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:96 +msgid "" +"Next, create a second unit of measure, name it, and select the same units of" +" measure category as your reference unit. As *Type*, select *Smaller* or " +"*Bigger than the reference Unit of Measure*, depending on your situation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:100 +msgid "" +"As the curtain roll equals to 100 square meters, you should select " +"*Smaller*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:102 +msgid "" +"Next, you need to enter the *Ratio* between your reference unit and the " +"second one. If the second unit is smaller, the *Ratio* should be greater " +"than 1. If the second unit is larger, the ratio should be smaller than 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:106 +msgid "For your curtain roll, the ratio should be set to 100." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a second unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112 +msgid "" +"You can now configure your product just as you would using Odoo's standard " +"units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Set a product's units of measure using your own units in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality.rst:8 +msgid "Quality" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality.rst:10 +msgid "" +"**Odoo Quality** helps ensure product quality throughout manufacturing " +"processes and inventory movements. Conduct quality checks, automate quality " +"inspection frequency, and create quality alerts when issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality.rst:15 +msgid "" +"`Odoo Tutorials: Managing Quality Checks " +"`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types.rst:5 +msgid "Quality check types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:3 +msgid "Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:7 +msgid "" +"In Odoo *Quality*, an *Instructions* check is one of the quality check types" +" that can be selected when creating a new quality check or quality control " +"point (QCP). *Instructions* checks consist of a text entry field that allows" +" the creator to provide instructions for how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:11 +msgid "" +"For a full overview of how to configure a quality check or a |QCP|, see the " +"documentation on :ref:`quality checks ` and :ref:`quality control points " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:16 +msgid "Process an Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:18 +msgid "" +"There are multiple ways that *Instructions* quality checks can be processed." +" If a quality check is assigned to a specific manufacturing, inventory, or " +"work order, the check can be processed on the order itself. Alternatively, a" +" check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:23 +msgid "Process from the quality check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:25 +msgid "" +"To process an *Instructions* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:29 +msgid "" +"If the product passes the check, click the :guilabel:`Pass` button above the" +" quality check form. If the product does not pass the check, click the " +":guilabel:`Fail` button, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:33 +msgid "Process quality check on an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:35 +msgid "" +"To process an *Instructions* quality check on an order, select a " +"manufacturing order or inventory order (receipt, delivery, return, etc.) for" +" which a check is required. Manufacturing orders can be selected by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and clicking on an order. Inventory orders can be selected by " +"navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " +"Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:42 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears above the order. Click the button " +"to open the :guilabel:`Quality Check` pop-up window, from which any quality " +"checks created for the order can be processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst-1 +msgid "The Quality Check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:50 +msgid "" +"To complete an *Instructions* quality check, follow the instructions " +"detailed in the :guilabel:`Quality Check` pop-up window. Finally, click " +":guilabel:`Validate` to confirm that the check has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:54 +msgid "" +"If an issue or defect is found during the quality check, a quality alert may" +" need to be created to notify a quality team. To do so, click the " +":guilabel:`Quality Alert` button that appears at the top of the " +"manufacturing or inventory order after the check is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:58 +msgid "" +"Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page." +" For a complete guide on how to fill out quality alert forms, view the " +"documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:63 +msgid "Process work order quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:65 +msgid "" +"When configuring a |QCP| that is triggered by a manufacturing order, a " +"specific work order can also be specified in the :guilabel:`Work Order " +"Operation` field on the |QCP| form. If a work order is specified, an " +"*Instructions* quality check is created for that specific work order, rather" +" than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:70 +msgid "" +"Quality checks configured for work orders must be completed from the tablet " +"view. To do so, begin by navigating to :menuselection:`Manufacturing --> " +"Operations --> Manufacturing Orders`. Select a manufacturing order that " +"includes a work order for which a quality check is required. Open the tablet" +" view for that work order by clicking the :guilabel:`📱 (tablet)` button on " +"the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:75 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Instructions* quality check step is reached. Upon reaching" +" the check, the instructions for how to complete it will appear at the top " +"of the screen. Follow the instructions, then click :guilabel:`Next` to move " +"on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst-1 +msgid "An Instructions check for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:84 +msgid "" +"If an issue or defect is found during the quality check, a quality alert may" +" need to be created to notify a quality team. To do so, click the " +":guilabel:`☰ (menu)` button in the tablet view, and then select " +":guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:88 +msgid "" +"Clicking :guilabel:`Quality Alert` opens a :guilabel:`Quality Alerts` pop-up" +" window, from which a quality alert can be created. For a complete guide to " +"quality alert creation, view the documentation on :ref:`quality alerts " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:3 +msgid "Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Measure* check is one of the quality check types that " +"can be selected when creating a new quality check or quality control point " +"(QCP). *Measure* checks prompt users to measure a certain aspect of a " +"product and record the measurement in Odoo. For the quality check to pass, " +"the recorded measurement must be within a certain *tolerance* of a *norm* " +"value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:14 +msgid "Create a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:16 +msgid "" +"There are two distinct ways that *Measure* quality checks can be created. A " +"single check can be manually created. Alternatively, a |QCP| can be " +"configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:20 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Measure* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"` and :ref:`quality control " +"points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:26 +msgid "Quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:29 +msgid "" +"To create a single *Measure* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:32 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` " +"quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:34 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:33 +msgid "" +"In the :guilabel:`Team` drop-down field, select the quality team responsible" +" for managing the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:35 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:35 +msgid "" +"In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, " +"enter instructions for how the picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A quality check form configured for a Measure quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:43 +msgid "Quality control point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:45 +msgid "" +"To create a |QCP| that generates *Measure* quality checks automatically, " +"navigate to :menuselection:`Quality --> Quality Control --> Control Points`," +" and click :guilabel:`New`. Fill out the new |QCP| form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:49 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` " +"quality check type. Doing so causes two new fields to appear: " +":guilabel:`Norm` and :guilabel:`Tolerance`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:52 +msgid "" +"Use the first text-entry field of the :guilabel:`Norm` field to record the " +"ideal measurement that the product should conform to. Use the second text-" +"entry field to specify the unit of measurement that should be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:55 +msgid "" +"The :guilabel:`Tolerance` field features two sub-fields: :guilabel:`from` " +"and :guilabel:`to`. Use the :guilabel:`from` field to specify the minimum " +"acceptable measurement, and the :guilabel:`to` field to specify the maximum " +"acceptable measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:59 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:51 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:54 +msgid "" +"In the :guilabel:`Team` drop-down field, select the quality team responsible" +" for managing the checks created by the |QCP|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:61 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how the " +"measurement should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A QCP form configured to create Measure quality checks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:69 +msgid "Process a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:71 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:63 +msgid "" +"Once created, there are multiple ways that *Measure* quality checks can be " +"processed. If a quality check is assigned to a specific inventory, " +"manufacturing, or work order, the check can be processed on the order " +"itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:76 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:68 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:71 +msgid "From the check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:78 +msgid "" +"To process a *Measure* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to take the measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:82 +msgid "" +"After taking the measurement, record the value in the :guilabel:`Measure` " +"field on the quality check form. To manually pass or fail the check, click " +":guilabel:`Pass` or :guilabel:`Fail` at the top-left corner of the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:86 +msgid "" +"Alternatively, if the quality check is assigned to a |QCP| for which *norm* " +"and *tolerance* values have been specified, click :guilabel:`Measure` at the" +" top-left corner of the check instead. Doing so automatically marks the " +"check as *Passed* if the recorded value is within the specified *tolerance*," +" or *Failed* if the value is outside of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:92 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:78 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:87 +msgid "On an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:94 +msgid "" +"To process a *Measure* quality check on an order, select a manufacturing " +"order or inventory order (receipt, delivery, return, etc.), for which a " +"check is required. Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:101 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:96 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears at the top of the page. Click the " +"button to open the :guilabel:`Quality Check` pop-up window, which shows all " +"of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:105 +msgid "" +"To process a *Measure* quality check, measure the product as instructed, " +"then enter the value in the :guilabel:`Measure` field on the pop-up window. " +"Finally, click :guilabel:`Validate` to register the recorded value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "" +"A Measure quality check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:113 +msgid "" +"If the value entered is within the range specified in the " +":guilabel:`Tolerance` section of the |QCP|, the quality check passes and the" +" pop-up window closes. The rest of the manufacturing or inventory order can " +"then be processed as usual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:117 +msgid "" +"However, if the value entered is outside of the specified range, a new pop-" +"up window appears, titled :guilabel:`Quality Check Failed`. The body of the " +"pop-up shows a warning message that states, :guilabel:`You measured # units " +"and it should be between # units and # units.`, as well as the instructions " +"entered in the :guilabel:`Message If Failure` tab of the |QCP|. At the " +"bottom of the pop-up, two buttons appear: :guilabel:`Correct Measure` and " +":guilabel:`Confirm Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "The \"Quality Check Failed\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:127 +msgid "" +"If the measurement was not entered correctly and should be changed, select " +":guilabel:`Correct Measure`. Doing so re-opens the :guilabel:`Quality Check`" +" pop-up window. Enter the corrected measurement in the :guilabel:`Measure` " +"field, and then click :guilabel:`Validate` to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:132 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:185 +msgid "" +"If the measurement was entered correctly, click :guilabel:`Confirm Measure` " +"instead, and the quality check fails. Follow any instructions that were " +"listed on the :guilabel:`Quality Check Failed` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:136 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert " +"form on a new page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:140 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:193 +msgid "" +"For a complete guide on how to fill out the quality alert form, view the " +"documentation on :ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:144 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:106 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:120 +msgid "On a work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:146 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Measure* quality " +"check is created for that specific work order, rather than the manufacturing" +" order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:151 +msgid "" +"*Measure* quality checks created for work orders must be processed from the " +"tablet view. To do so, begin by navigating to :menuselection:`Manufacturing " +"--> Operations --> Manufacturing Orders`. Select a manufacturing order that " +"includes a work order for which a quality check is required. Open the tablet" +" view for that work order by selecting the :guilabel:`Work Orders` tab, and " +"then clicking the :guilabel:`📱 (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:157 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Measure* quality check step is reached. Upon reaching the " +"check, the instructions for how to take the measurement appear at the top of" +" the screen. Enter the measured value in the :guilabel:`Measure` field above" +" the instructions, and then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A Measure quality check in the Manufacturing tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:166 +msgid "" +"If the measurement entered is within the range specified in the " +":guilabel:`Tolerance` section of the |QCP|, the quality check passes and the" +" tablet view moves on to the next step of the work order. However, if the " +"measurement entered is outside of the specified range, a pop-up window " +"appears, titled :guilabel:`Quality Check Failed`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:171 +msgid "" +"The body of the :guilabel:`Quality Check Failed` pop-up window shows a " +"warning message that states, :guilabel:`You measured # units and it should " +"be between # units and # units.`, as well as the instructions entered in the" +" :guilabel:`Message If Failure` tab of the |QCP|. At the bottom of the pop-" +"up, two buttons appear: :guilabel:`Correct Measure` and :guilabel:`Confirm " +"Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:180 +msgid "" +"If the measurement was not entered correctly, and should be changed, select " +":guilabel:`Correct Measure`. Doing so opens a new pop-up window, titled " +":guilabel:`Quality Check`. Enter the corrected measurement in the " +":guilabel:`Measure` field, then click :guilabel:`Validate` to complete the " +"check, and move on to the next step of the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:189 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(three horizontal lines)` button, and selecting :guilabel:`Quality Alert` " +"from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up" +" window appears, from which a quality alert can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:3 +msgid "Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Pass - Fail* check is one of the quality check types " +"that can be selected when creating a new quality check or quality control " +"point (QCP). *Pass - Fail* checks consist of a text field that allows the " +"creator to specify a certain criteria that a product must meet to pass the " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:14 +msgid "Create a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:16 +msgid "" +"There are two distinct ways that *Pass - Fail* quality checks can be " +"created. A single check can be manually created. Alternatively, a |QCP| can " +"be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:20 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Pass - Fail* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"` and :ref:`quality control " +"points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:29 +msgid "" +"To create a single *Pass - Fail* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:50 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Pass - Fail` " +"quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:36 +msgid "" +"In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, " +"enter instructions for how to complete the quality check and the criteria " +"that must be met for the check to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "A quality check form configured for a Pass - Fail quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:44 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:43 +msgid "Quality Control Point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:46 +msgid "" +"To create a |QCP| that generates *Pass - Fail* quality checks automatically," +" begin by navigating to :menuselection:`Quality --> Quality Control --> " +"Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:53 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how to " +"complete the quality check and the criteria that must be met for the check " +"to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "" +"A Quality Control Point (QCP) form configured to create a Pass - Fail " +"quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:61 +msgid "Process a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:70 +msgid "" +"To process a *Measure* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:74 +msgid "" +"If the criteria for the check is met, click the :guilabel:`Pass` button at " +"the top-left corner of the page. If the criteria is not met, click the " +":guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:80 +msgid "" +"To process a *Pass - Fail* quality check on an order, select a manufacturing" +" order or inventory order (receipt, delivery, return, etc.), for which a " +"check is required. Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:87 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears at the top of the order. Click the" +" button to open the :guilabel:`Quality Check` pop-up window, which shows all" +" of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:91 +msgid "" +"To process a *Pass - Fail* quality check, follow the instructions shown on " +"the :guilabel:`Quality Check` pop-up window. If the criteria for the check " +"is met, click the :guilabel:`Pass` button at the bottom of the window. If " +"the criteria is not met, click the :guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "" +"A Pass - Fail quality check pop-up window on a manufacturing or inventory " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:99 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert " +"form on a new page. For a complete guide on how to fill out quality alert " +"forms, view the documentation on :ref:`quality alerts " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:108 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Pass - Fail* " +"quality check is created for that specific work order, rather than the " +"manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:113 +msgid "" +"*Pass - Fail* quality checks configured for work orders must be processed " +"from the tablet view. To do so, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order that includes a work order for which a quality " +"check is required. Open the tablet view for that work order by selecting the" +" :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " +"button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:119 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Pass - Fail* quality check step is reached. Upon reaching " +"the check, follow the instructions that appear at the top of the screen. If " +"the criteria for the check is met, click the :guilabel:`Pass` button at the " +"top-right of the screen. If the criteria is not met, click the " +":guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "A Pass - Fail check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:128 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(menu)` button in the tablet view, and selecting :guilabel:`Quality Alert` " +"from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up" +" window appears, from which a quality alert can be created. For a complete " +"guide on how to fill out quality alert forms, view the documentation on " +":ref:`quality alerts `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:3 +msgid "Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Take a Picture* check is one of the quality check " +"types that can be selected when creating a new quality check or quality " +"control point (QCP). *Take a Picture* checks require a picture to be " +"attached to the check, which can then be reviewed by a quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:13 +msgid "Create a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:15 +msgid "" +"There are two distinct ways that *Take a Picture* quality checks can be " +"created. A single check can be manually created. Alternatively, a |QCP| can " +"be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:19 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Take a Picture* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"` and :ref:`quality control " +"points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:28 +msgid "" +"To create a single *Take a Picture* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:32 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:49 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Take a " +"Picture` quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A quality check form configured for a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:45 +msgid "" +"To create a |QCP| that will generate *Take a Picture* quality checks " +"automatically, navigate to :menuselection:`Quality --> Quality Control --> " +"Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:50 +msgid "" +"If the *Maintenance* app is installed, a :guilabel:`Device` field appears " +"after selecting the *Take a Picture* check type. Use this field to specify a" +" device that should be used to take quality check pictures. For information " +"about managing devices in the *Maintenance* app, see the documentation on " +":ref:`adding new equipment " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:56 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how the " +"picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "" +"A Quality Control Point (QCP) form configured to create a Take a Picture " +"quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:64 +msgid "Process a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:66 +msgid "" +"Once created, there are multiple ways that *Take a Picture* quality checks " +"can be processed. If a quality check is assigned to a specific inventory, " +"manufacturing, or work order, the check can be processed on the order " +"itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:73 +msgid "" +"To process a *Take a Picture* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and then select a quality check. Follow the " +":guilabel:`Instructions` for how to take the picture." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:77 +msgid "" +"After taking the picture, make sure it is stored on the device being used to" +" process the quality check (computer, tablet, etc.). Then, click the " +":guilabel:`✏️ (pencil)` button in the :guilabel:`Picture` section to open " +"the device's file manager. In the file manager, navigate to the picture, " +"select it, and click :guilabel:`Open` to attach it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "The edit button (pencil) on a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:89 +msgid "" +"To process a *Take a Picture* quality check on an order, select a " +"manufacturing order or inventory order (receipt, delivery, return, etc.), " +"for which a check is required. Manufacturing orders can be selected by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and clicking on an order. Inventory orders can be selected by " +"navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " +"Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:100 +msgid "" +"Follow the instructions detailing how to take the picture, which are shown " +"on the :guilabel:`Quality Check` pop-up window. After taking the picture, " +"make sure it is stored on the device being used to process the quality check" +" (computer, tablet, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:104 +msgid "" +"Then, click the :guilabel:`Take a Picture` button in the :guilabel:`Picture`" +" section to open the device's file manager. In the file manager, navigate to" +" the picture, select it, and click :guilabel:`Open` to attach it. Finally, " +"click :guilabel:`Validate` on the :guilabel:`Quality Check` pop-up window to" +" complete the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "" +"A Take a Picture quality check pop-up window on a manufacturing or inventory" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:113 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check is validated. Clicking :guilabel:`Quality Alert` opens a quality " +"alert form on a new page. For a complete guide on how to fill out quality " +"alert forms, view the documentation on :ref:`quality alerts " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:122 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Take a Picture* " +"quality check is created for that specific work order, rather than the " +"manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:127 +msgid "" +"*Take a Picture* quality checks created for work orders must be completed " +"from the tablet view. To do so, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order that includes a work order for which a quality " +"check is required. Open the tablet view for that work order by selecting the" +" :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " +"button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Take a Picture* quality check step is reached. Upon " +"reaching the check, follow the instructions for how to take the picture, " +"which appear at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:137 +msgid "" +"After taking the picture, make sure it is stored on the device being used to" +" process the work order (computer, tablet, etc.). Then, click the " +":guilabel:`Take a Picture` button to open the device's file manager. In the " +"file manager, navigate to the picture, select it, and click :guilabel:`Open`" +" to attach it. Finally, click :guilabel:`Validate` to complete the quality " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A Take a Picture check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:146 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(three horizontal lines)` button in the tablet view, and selecting " +":guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window. A " +":guilabel:`Quality Alerts` pop-up window appears, from which a quality alert" +" can be created. For a complete guide on how to fill out quality alert " +"forms, view the documentation on :ref:`quality alerts " +"`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:153 +msgid "Review a picture attached to a check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:155 +msgid "" +"After a picture has been attached to a check, it can then be reviewed by " +"quality team members or other users. To do so, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and select " +"a quality check to review." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:159 +msgid "" +"The attached picture appears in the :guilabel:`Picture` section of the " +"quality check form. After reviewing the picture, click the :guilabel:`Pass` " +"button if the check passes, or the :guilabel:`Fail` button if the check " +"fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A Take a Picture check with a picture attached." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management.rst:5 +msgid "Quality control basics" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:3 +msgid "Create quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:7 +msgid "" +"Configuring quality control points is a great way to ensure that quality " +"checks are performed at routine stages during specific operations. However, " +"quality issues can often appear outside of these scheduled checks. Using " +"Odoo *Quality*, users can create quality alerts for issues that are not " +"detected by automated processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:13 +msgid ":doc:`Add quality control points `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:16 +msgid "Find and fill out the quality alerts form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:18 +msgid "" +"In some situations, it is necessary to manually create quality alerts within" +" the *Quality* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:21 +msgid "" +"A helpdesk user who is notified of a product defect by a customer ticket can" +" create an alert that brings the issue to the attention of the relevant " +"quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:24 +msgid "" +"To create a new quality alert, start from the :menuselection:`Quality` " +"module and select :menuselection:`Quality Control --> Quality Alerts --> " +"Create`. The quality alert form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:28 +msgid "" +":guilabel:`Title`: choose a concise, yet descriptive title for the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:29 +msgid "" +":guilabel:`Product`: the product about which the quality alert is being " +"created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:30 +msgid "" +":guilabel:`Product Variant`: the specific variant of the product that has " +"the quality issue, if applicable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:32 +msgid ":guilabel:`Lot`: the lot number assigned to the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:33 +msgid "" +":guilabel:`Work Center`: the work center where the quality issue originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:34 +msgid "" +":guilabel:`Picking`: the picking operation during which the quality issue " +"originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:35 +msgid "" +":guilabel:`Team`: the quality team that will be notified by the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:36 +msgid "" +":guilabel:`Responsible`: the individual responsible for managing the quality" +" alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:37 +msgid "" +":guilabel:`Tags`: classify the quality alert based on user-created tags" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:38 +msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:39 +msgid "" +":guilabel:`Priority`: assign a priority between one and three stars to " +"ensure more urgent issues are prioritized" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:42 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:42 +msgid "" +"The tabs at the bottom of the form can be used to provide additional " +"information to quality teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:44 +msgid "" +":guilabel:`Description`: provide additional details about the quality issue" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:45 +msgid "" +":guilabel:`Corrective Actions`: the method for fixing affected products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:46 +msgid "" +":guilabel:`Preventive Actions`: procedures for preventing the issue from " +"occurring in the future" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:48 +msgid "" +":guilabel:`Miscellaneous`: the product vendor (if applicable), the company " +"that produces the product, and the date assigned" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst-1 +msgid "An example of a completed quality alert form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:56 +msgid "Add quality alerts during the manufacturing process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:58 +msgid "" +"Odoo enables manufacturing employees to create quality alerts within a work " +"order without accessing the *Quality* module. From the work order tablet " +"view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner " +"and select :guilabel:`Quality Alert`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst-1 +msgid "Access the work order menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:66 +msgid "" +"The quality alert form can then be filled out as detailed in the previous " +"section. After saving the form, a new alert will appear on the " +":guilabel:`Quality Alerts` dashboard that can be found through the " +":menuselection:`Quality --> Quality Control` menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:71 +msgid "Manage existing quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:73 +msgid "" +"By default, quality alerts are organized in a kanban board view. The stages " +"of the kanban board are fully configurable and alerts can be moved from one " +"stage to the next by dragging and dropping or from within each alert. " +"Additional options are available for viewing alerts, including graph, " +"calendar, and pivot table views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:79 +msgid "" +"Filter alerts based on diverse criteria like date assigned or date closed. " +"Alerts can also be grouped by quality team, root cause, or other parameters " +"found under the :guilabel:`Filters` button menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:3 +msgid "Quality checks" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:8 +msgid "" +"Quality checks are manual inspections conducted by employees, and are used " +"to ensure the quality of products. In Odoo, a quality check can be conducted" +" for a single product, or multiple products within the same inventory " +"operation or manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:12 +msgid "" +"Using a Quality Control Point (QCP), it is possible to create quality checks" +" automatically at regular intervals. When quality checks are created by a " +"|QCP|, they appear on a manufacturing or inventory order, where the employee" +" processing the order will be prompted to complete them. For a full " +"explanation of how to create and configure a |QCP|, see the documentation on" +" :ref:`quality control points `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:18 +msgid "" +"While quality checks are most commonly created automatically by a |QCP|, it " +"is also possible to manually create a single quality check. Creating a check" +" manually is useful when an employee wants to schedule a quality check that " +"will only occur once, or register a quality check that they conduct " +"unprompted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:24 +msgid "Manual quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:26 +msgid "" +"To manually create a single quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. On the quality check form, begin by selecting an option " +"from the :guilabel:`Control per` drop-down menu:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:30 +msgid "" +":guilabel:`Operation` requests a check for an entire operation (ex. delivery" +" order) and all products within it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:32 +msgid "" +":guilabel:`Product` requests a check for every unit of a product that is " +"part of an operation (ex. every unit of a product within a delivery order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:34 +msgid "" +":guilabel:`Quantity` requests a check for every quantity of a product that " +"is part of an operation (ex. one check for five units of a product within a " +"delivery order). Selecting :guilabel:`Quantity` also causes a " +":guilabel:`Lot/Serial` drop-down field to appear, from which can be selected" +" a specific lot or serial number that the quality check should be conducted " +"for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:39 +msgid "" +"Next, select an inventory operation from the :guilabel:`Picking` drop-down " +"menu or a manufacturing order from the :guilabel:`Production Order` drop-" +"down menu. This is necessary because Odoo needs to know for which operation " +"the quality check is being conducted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:43 +msgid "" +"If the quality check should be assigned to a specific |QCP|, select it from " +"the :guilabel:`Control Point` drop-down menu. This is useful if the quality " +"check is being created manually, but should still be recognized as belonging" +" to a specific |QCP|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:47 +msgid "Select a quality check type from the :guilabel:`Type` drop-down field:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:49 +msgid "" +":guilabel:`Instructions` provides specific instructions for how to conduct " +"the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:50 +msgid "" +":guilabel:`Take a Picture` requires a picture to be attached to the check " +"before the check can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:52 +msgid "" +":guilabel:`Pass - Fail` is used when the product being checked must meet a " +"certain criteria to pass the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:54 +msgid "" +"Selecting :guilabel:`Measure` causes a :guilabel:`Measure` input field to " +"appear, in which a measurement must be entered before the check can be " +"completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:56 +msgid "" +"Selecting :guilabel:`Worksheet` causes a :guilabel:`Quality Template` drop-" +"down field to appear. Use it to select a quality worksheet that must be " +"filled out to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:59 +msgid "" +"In the :guilabel:`Team` field, select the quality team that is responsible " +"for the quality check. In the :guilabel:`Company` field, select the company " +"that owns the product being inspected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:62 +msgid "" +"On the :guilabel:`Notes` tab at the bottom of the form, enter any relevant " +"instructions in the :guilabel:`Instructions` text entry box (ex. 'Attach a " +"picture of the product'). In the :guilabel:`Notes` text entry box, enter any" +" relevant information about the quality check (who created it, why it was " +"created, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:67 +msgid "" +"Finally, if the check is being processed immediately, click the " +":guilabel:`Pass` button at the top left of the screen if the check passes, " +"or the :guilabel:`Fail` button if the check fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "A quality check form filled out for a Pass - Fail check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:75 +msgid "Process quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:77 +msgid "" +"Quality checks can be processed directly on the quality check's page, or " +"from a manufacturing or inventory order for which a check is required. " +"Alternatively, if a quality check is created for a specific work order " +"operation, the check is processed in the tablet view for the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:82 +msgid "" +"It is not possible to manually create a single quality check that is " +"assigned to a specific work order operation. Quality checks for work order " +"operations can only be created by a |QCP|. See the documentation on " +":ref:`Quality Control Points ` for information about how to configure a |QCP| that will create " +"quality checks for a specific work order operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:89 +msgid "Quality check page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:91 +msgid "" +"To process a quality check from the check's page, begin by navigating to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, then select" +" the check to process. Follow the instructions for how to complete the " +"check, listed in the :guilabel:`Instructions` field of the :guilabel:`Notes`" +" tab at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:96 +msgid "" +"If the quality check passes, click the :guilabel:`Pass` button at the top of" +" the page. If the check fails, click the :guilabel:`Fail` button, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:100 +msgid "Quality check on order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:102 +msgid "" +"To process a quality check on an order, select a manufacturing or inventory " +"order (receipt, delivery, return, etc.), for which a check is required. " +"Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:108 +msgid "" +"On the selected inventory or manufacturing order, a purple " +":guilabel:`Quality Checks` button appears at the top of the order. Click the" +" button to open the :guilabel:`Quality Check` pop-up window, which shows all" +" of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:112 +msgid "" +"Follow the instructions that appear on the :guilabel:`Quality Check` pop-up " +"window. If a Pass - Fail check is being processed, complete the check by " +"clicking :guilabel:`Pass` or :guilabel:`Fail` at the bottom of the pop-up " +"window. For all other quality check types, a :guilabel:`Validate` button " +"appears instead. Click it to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "The \"Quality Check\" pop-up window on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:122 +msgid "Quality check on work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:124 +msgid "" +"To process a quality check for a work order, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select a manufacturing order. Select the :guilabel:`Work Orders` tab, then " +"click the :guilabel:`📱 (tablet)` tablet view button for the work order that " +"requires the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the quality check step is reached, then follow the instructions" +" at the top of the screen. If a Pass - Fail check is being processed, " +"complete the check by clicking :guilabel:`Pass` or :guilabel:`Fail` at the " +"top of the screen. For all other quality check types, a :guilabel:`Next` " +"button appears instead. Click it to complete the check and move on to the " +"next step of the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "A quality check for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:3 +msgid "Add quality controls" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:7 +msgid "" +"Use Odoo *Quality* to control the quality of products before they are " +"registered into stock, during picking operations, and when leaving the " +"warehouse for a delivery order. By creating *quality control points*, " +"manufacturers can set up quality checks that automatically trigger at " +"specific points during production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:13 +msgid "Configure quality control points" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:15 +msgid "" +"To create a new quality control point, go to :menuselection:`Quality Control" +" --> Control Points --> Create`. Then, fill in the following form fields, " +"accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:18 +msgid "" +":guilabel:`Title`: give the quality control point a simple, but informative " +"title so production floor and quality check teams can understand it easily" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:20 +msgid "" +":guilabel:`Products`: indicate which product(s) should pass through the " +"specific quality control point" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:22 +msgid "" +":guilabel:`Operations`: determine which operations team(s) should perform " +"the quality control check (e.g., `Manufacturing`, `Receipts`, `Delivery " +"Orders`, etc.)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:24 +msgid "" +":guilabel:`Work Order Operation`: for manufacturing operations, use the " +"drop-down menu to indicate which type of work order the quality control " +"point applies to: :guilabel:`Manual Assembly`, :guilabel:`Packing`, " +":guilabel:`Assembly`, :guilabel:`Testing` or :guilabel:`Long time assembly`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:28 +msgid "" +":guilabel:`Company`: add the company that will implement the quality control" +" point. Usually this will be the company that owns the Odoo database. " +"However, a multi-company or vendor profile can be selected, as well, for " +"cases where there are multiple manufacturing or engineering locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:31 +msgid "" +":guilabel:`Control Type`: using the drop-down menu, choose from " +":guilabel:`All Operations`, :guilabel:`Randomly` or :guilabel:`Periodically`" +" to determine how often the control point should executed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:34 +msgid "" +":guilabel:`Type`: using the drop-down menu, choose the control point type: " +":guilabel:`Instructions`, :guilabel:`Take a Picture`, :guilabel:`Pass - " +"Fail`, or :guilabel:`Measure`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:37 +msgid "" +":guilabel:`Team`: decide which quality team should receive the results of " +"the quality control point check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:39 +msgid "" +":guilabel:`Responsible`: add a point person to manage the status and " +"evolution of the quality control point over time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:44 +msgid ":guilabel:`Instructions`: describe the quality check to be performed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:45 +msgid "" +":guilabel:`Message If Failure`: detail what should be done if the check " +"fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:46 +msgid ":guilabel:`Notes`: use to include any additional information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst-1 +msgid "" +"An example of a completed quality control point form for a Pass-Fail test." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:52 +msgid "" +"Once a control point has been configured, a quality check will be " +"automatically created and assigned when the specified operation or work " +"order has been reached. Quality checks can be managed by selecting " +":menuselection:`Quality Control --> Quality Checks`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:57 +msgid "" +"To see all of the quality checks created by a control point, go to " +":menuselection:`Quality Control --> Control Points`, select a control point," +" and click :guilabel:`Quality Checks` in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:62 +msgid "Use case: configure a measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:64 +msgid "" +"To ensure that a product meets specific measurement requirements, select " +":guilabel:`Measure` from the :guilabel:`Type` drop-down menu. Selecting the " +":guilabel:`Measure` quality check type reveals three new fields: " +":guilabel:`Device`, :guilabel:`Norm`, and :guilabel:`Tolerance`. These " +"fields can be configured so that only products within a certain tolerance " +"will pass the check:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:69 +msgid "" +":guilabel:`Device`: select the measuring device that should be used to take " +"the measurement (e.g., measuring tape)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:71 +msgid "" +":guilabel:`Norm`: specify the desired measurement that the product should " +"conform to and the unit of measurement that should be used" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:73 +msgid "" +":guilabel:`Tolerance`: select the range that a measurement can be within " +"while still passing the check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to`" +" 60.5 mm)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst-1 +msgid "" +"An example of a quality control point form configured for a measure quality " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:80 +msgid "" +"When the quality control points form is complete, click :guilabel:`Save`. " +"Now, this measurement-based test will trigger for products that were " +"specified on the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:83 +msgid "" +"When production of the specified product reaches the operation that requires" +" a measure quality check, the manufacturing employee responsible will be " +"prompted to record and validate the measured value in the tablet view. For " +"products that measure within the values indicated in the " +":guilabel:`Tolerance` fields, the test will pass. However, for products that" +" measure outside of those values, the test will fail. In that case, the " +"worker who performed the check would create a quality alert from the tablet " +"view. That quality alert can then be addressed by the quality management " +"team." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/marketing.po b/locale/hi/LC_MESSAGES/marketing.po new file mode 100644 index 000000000..5d7158d31 --- /dev/null +++ b/locale/hi/LC_MESSAGES/marketing.po @@ -0,0 +1,6521 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/marketing.rst:5 +msgid "Marketing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:6 +msgid "Email marketing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:8 +msgid "" +"Emails are an effective, fully-customizable form of communication that are " +"able to reach any target audience - large or small. The success of an email " +"is easily measurable, especially when a creative call-to-action is involved." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:12 +msgid "" +"Odoo *Email Marketing* provides professional-grade email design tools, " +"templates, and features, designed to simplify the otherwise complex process " +"required to create engaging emails, build successful campaigns, and track " +"their overall effectiveness in a single application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:17 +#: ../../content/applications/marketing/email_marketing.rst:219 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74 +msgid ":doc:`/applications/marketing/email_marketing/mailing_lists`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:18 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:136 +msgid ":doc:`/applications/marketing/email_marketing/unsubscriptions`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:21 +msgid "Email marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:23 +msgid "" +"To get started, click on the :menuselection:`Email Marketing` app icon, " +"located on the main Odoo dashboard, which leads to the main :guilabel:`Email" +" Marketing` dashboard (in the default kanban view)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:27 +msgid "" +"To see all the mailings in the database, remove the default :guilabel:`My " +"Mailings` filter from the search bar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the main dashboard of the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:35 +msgid "" +"In the search bar, by default, the filter: :guilabel:`My Mailings` is " +"present. That means the only information being seen (at that time) on the " +":guilabel:`Email Marketing` dashboard are emails that the current user has " +"created, sent, or is responsible for." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:39 +msgid "" +"This filter can be removed by clicking the :guilabel:`X` next to " +":guilabel:`My Mailings` in the search bar. Doing so, reveals all the " +"information for every email in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:43 +msgid "Default kanban view and stages" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:45 +msgid "" +"The four kanban columns each represent the various stages of emails that " +"have been built or sent within the *Email Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:48 +msgid "" +"The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, " +":guilabel:`Sending`, :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:50 +msgid ":guilabel:`Draft`: means the email is still being written/created." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:51 +msgid "" +":guilabel:`In Queue`: means the email is scheduled, and sent at a later " +"date." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:52 +msgid "" +":guilabel:`Sending`: means the email is currently being sent to its " +"recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:53 +msgid "" +":guilabel:`Sent`: means the email has already been sent to its recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:55 +msgid "" +"In each stage, there are drag-and-drop cards representing the email " +"campaigns that have been created, and the stage they are in represents the " +"current status of that mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:58 +msgid "" +"Each mailing block on the :guilabel:`Email Marketing` dashboard provides key" +" information related to that specific email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:61 +msgid "" +"When the cursor hovers over the upper-right corner of an email campaign " +"card, three vertical dots (:guilabel:`⋮`) appear. When clicked, a mini drop-" +"down menu reveals the option to color-code the email :guilabel:`Delete` the " +"email altogether, or :guilabel:`Archive` the message for potential future " +"use." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the three-dot drop-down menu on the Odoo Email Marketing dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:70 +msgid "" +"In the upper-right corner of the main :guilabel:`Email Marketing` dashboard," +" there are other view options to choose from: :guilabel:`List` and " +":guilabel:`Graph`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:74 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 +msgid "List view" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:76 +msgid "" +"The :guilabel:`List` view (represented by the :guilabel:`☰ (three vertical " +"lines)` icon) provides the same key information, but in a classic list " +"format." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "How the List view appears in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:84 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:86 +msgid "" +"The :guilabel:`Graph` view (represented by the :guilabel:`📊 (bar graph)` " +"icon) provides the same key information, but in a variety of customizable " +"graph (and chart) layouts." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "How the Graph view appears in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:93 +msgid "" +"In the upper-left corner, there is a :guilabel:`Measures` menu, providing " +"even more filter options to further customize the graph views." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:96 +msgid "" +"Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage`, " +":guilabel:`Color Index`, and :guilabel:`Count` (which is selected, by " +"default)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:100 +msgid "Filters, Group By, and Favorites search options" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:102 +msgid "" +"Regardless of the view chosen for the :guilabel:`Email Marketing` dashboard," +" the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` " +"options are always available." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:105 +msgid "" +"These options provide various ways to specify and organize the information " +"seen on the :guilabel:`Email Marketing` dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:110 +msgid "Filters" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:112 +msgid "" +"This drop-down menu provides different ways to filter email campaigns on the" +" dashboard. The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`," +" :guilabel:`Archived`, and :guilabel:`Add Custom Filter`. If :guilabel:`Add " +"Custom Filter` is selected, Odoo reveals an additional drop-down menu, with " +"three customizable fields to fill in, in order to retrieve results that fit " +"more specific criteria." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of filters drop-down menu options on the Odoo Email Marketing " +"dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:121 +msgid "Group By" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:123 +msgid "" +"This drop-down menu provides additional ways to organize the data on the " +"dashboard by grouping them in specific ways. Using this drop-down menu, the " +"data can be grouped by the messages' :guilabel:`Status`, or who it was " +":guilabel:`Sent By`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:127 +msgid "" +"There is also the option to group the data by :guilabel:`Sent Period`, which" +" has its own sub-menu of options to choose from. The :guilabel:`Sent Period`" +" options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, " +":guilabel:`Week`, and :guilabel:`Day`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:131 +msgid "" +"If none of the above :guilabel:`Group By` options deliver the desired " +"results, click :guilabel:`Add Custom Group` at the bottom of the drop-down " +"menu. Doing so reveals a new field, wherein custom criteria can be selected " +"and applied, thus delivering any grouping of data that may be desired." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of the Group By drop-down menu on the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:139 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:141 +msgid "" +"This drop-down menu provides different ways to incorporate past search " +"filters and other record-related options to customize the dashboard. The " +"options are: :guilabel:`Save current search`, :guilabel:`Import records`, " +":guilabel:`Add to my dashboard`, and :guilabel:`Add to Google Spreadsheet`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of the Favorites drop-down menu on the Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:150 +msgid "Settings" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:152 +msgid "" +"To view (and modify) the *Email Marketing* settings, navigate to " +":menuselection:`Email Marketing application --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the Settings page in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:159 +msgid "" +"On this :guilabel:`Settings` page, there are three features available. The " +"features are: :guilabel:`Mailing Campaigns`, :guilabel:`Blacklist Option " +"when Unsubscribing`, and :guilabel:`Dedicated Server`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:163 +msgid "" +":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:164 +msgid "" +":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to " +"blacklist themselves from future mailings during the unsubscribing process." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:166 +msgid "" +":guilabel:`Dedicated Server`: provides the option to utilize a separate, " +"dedicated server for mailings. When enabled, Odoo reveals a new field (and " +"link), in which the specific server configurations must be entered, in order" +" for it to connect properly to Odoo." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:171 +msgid "Create an email" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:173 +msgid "" +"To create an email, open the :menuselection:`Email Marketing` application, " +"and click the :guilabel:`Create` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:176 +msgid "Clicking :guilabel:`Create` reveals a blank email detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of a blank email detail form in Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:182 +msgid "" +"First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is " +"visible in the recipients' inbox, allowing them to get quickly see what the " +"message is about." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:186 +msgid "" +"The :guilabel:`Subject` field is mandatory. An email can not be sent without" +" a :guilabel:`Subject`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:190 +msgid "" +"The :guilabel:`☺ (smiley face)` icon at the end of the :guilabel:`Subject` " +"field (and :guilabel:`Preview Text` field) represents emojis. Click that " +":guilabel:`☺ (smiley face)` icon to reveal a menu of emojis that can be used" +" in either field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:194 +msgid "" +"Next, there is the option to enter some :guilabel:`Preview Text`. This text " +"is a catchy preview sentence that encourages recipients to open the message." +" In most inboxes, this is displayed next to the subject." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:199 +msgid "" +"Keep the :guilabel:`Preview Text` empty to show the first characters of the " +"email content, instead." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:203 +msgid "Recipients" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:205 +msgid "" +"After that, it's time to choose the recipients of this email, which can be " +"completed in the :guilabel:`Recipients` field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of recipients drop-down menu in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:212 +msgid "" +"The default option is :guilabel:`Mailing List`. If :guilabel:`Mailing List` " +"option is selected, a specific :guilabel:`Mailing List` needs to be chosen " +"from the adjacent :guilabel:`Select mailing lists` field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:216 +msgid "" +"Then, Odoo will only send this email to contacts on that specific mailing " +"list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:221 +msgid "" +"When the :guilabel:`Recipients` field is clicked, a drop-down menu of other " +"options is revealed. Each option provides different ways Odoo can create a " +"target audience for the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:224 +msgid "" +"Those options (excluding the default :guilabel:`Mailing List`) provide the " +"option to create a more specified recipient filter, in an equation-like " +"format." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:227 +msgid "The :guilabel:`Recipients` field options are as follows:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:229 +msgid "" +":guilabel:`Applicant`: filter focuses on specific job applicants in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:230 +msgid "" +":guilabel:`Contact`: filter focuses on specific contacts in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:231 +msgid "" +":guilabel:`Event Registration`: filter focuses on people in the database who" +" purchased event registrations." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:233 +msgid "" +":guilabel:`Event Track`: filter focuses on people in the database who hosted" +" a specific talk (track) at an event." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:235 +msgid "" +":guilabel:`Lead/Opportunity`: filter focuses on leads or opportunities in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:236 +msgid "" +":guilabel:`Mailing Contact`: filter focuses on specific mailing contacts in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:237 +msgid "" +":guilabel:`Sales Order`: filter focuses on a specific sales orders in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:239 +msgid "" +"If the specified recipient fields don't automatically reveal themselves, " +"simply click the :guilabel:`Add Filter` button beneath the " +":guilabel:`Recipients` field, and Odoo reveals the necessary equation fields" +" to further drill down the target recipients for this mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:244 +msgid "Add a recipient filter" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:246 +msgid "" +"To add a more specified recipient filter, select any recipient option (other" +" than :guilabel:`Mailing List`), and clicking :guilabel:`Add Filter`, if " +"needed, to reveal three fields, formatted like an equation." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:250 +msgid "" +"To reveal the sub-menu options, click each field, and make the desired " +"selections, until the preferred configuration has been achieved. The number " +"of :guilabel:`Records` that match the rule(s) are indicated to the right of " +"the :guilabel:`Recipients` field, in green." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of how recipient filters can be customized in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:259 +#: ../../content/applications/marketing/events/event_essentials.rst:191 +msgid "" +"Some sub-menu options in the first rule field allow for a second choice to " +"provide even more specificity." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:262 +msgid "" +"To the right of each rule, are :guilabel:`× (Delete node)`, :guilabel:`＋ " +"(Add node)`, and :guilabel:`⋯ (Add branch)` icons." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:265 +msgid "" +"The :guilabel:`× (Delete node)` icon deletes a specific node (line) of the " +"rule. The :guilabel:`＋ (Add node)` icon adds a node (line) to the rule. And," +" the :guilabel:`⋯ (Add branch)` icon adds a branch to the node. A branch " +"means two additional, indented sub-nodes are added to the rule, providing " +"even more specificity to the line above it." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:271 +msgid "Mail body tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:273 +msgid "" +"At the bottom of the email form are two tabs: :guilabel:`Mail Body` and " +":guilabel:`Settings`. Let's focus on :guilabel:`Mail Body` tab first." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:276 +msgid "" +"In the :guilabel:`Mail Body` tab, there are a number of pre-configured " +"message templates to choose from. Select the desired template, and modify " +"every element of its design details with Odoo's drag-and-drop building " +"blocks, located on the right sidebar. Each building block provides unique " +"features and professional design elements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the building blocks used to create mailings in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:286 +msgid "" +"To build an email from scratch, select the :guilabel:`Plain Text` template, " +"and Odoo provides a blank email canvas, which can be customized in a number " +"of ways - either by using the front-end rich text editor that accepts slash " +"(:guilabel:`/`) commands, or with the XML code editor when :ref:`Developer " +"Mode (debug mode) ` is engaged, and the :guilabel:`` icon" +" is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:293 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:295 +msgid "" +"To the right of the :guilabel:`Mail Body` tab is the :guilabel:`Settings` " +"tab." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:298 +msgid "" +"The options available in the :guilabel:`Settings` tab will be different, " +"depending on if the :guilabel:`Mailing Campaigns` feature is activated in " +"the :guilabel:`Settings` page of the :menuselection:`Email Marketing` " +"application (:menuselection:`Email Marketing --> Configuration --> " +"Settings`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:303 +msgid "" +"Without the :guilabel:`Mailing Campaigns` feature activated, the " +":guilabel:`Settings` tab on the email detail form looks like this:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of settings tab in Odoo Email Marketing app, without settings " +"activated." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:310 +msgid "" +":guilabel:`Responsible`: choose an employee (in the database) to be " +"responsible for this particular email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:312 +msgid "" +":guilabel:`Send From`: designate an email alias that'll display as the " +"sender of this particular email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:314 +msgid "" +":guilabel:`Reply To`: designate an email alias to whom all the replies to " +"this particular email will be sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:316 +msgid "" +":guilabel:`Attachments`: if any specific documents are required (or helpful)" +" for this event invite, they can be sent along with this email, by clicking " +":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:320 +msgid "" +"When the :guilabel:`Mailing Campaigns` feature *is* activated, additional " +":guilabel:`Marketing` options appear in the :guilabel:`Settings` tab, which " +"look like this:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of settings tab in Odoo Email Marketing when settings are activated." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:327 +msgid "" +"The additional features are: :guilabel:`Mailing Campaign`, :guilabel:`Allow " +"A/B Testing`, and :guilabel:`A/B Testing percentage`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:331 +msgid "Mailing campaigns" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:333 +msgid "" +"The :guilabel:`Mailing Campaign` field provides the option to add this " +"particular email to a previously-made email campaign in the database. Click " +"the empty field to reveal a drop-down menu containing all previously-made " +"mailing campaigns in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of a mailing campaign drop-down menu in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:341 +msgid "" +"If the desired campaign isn't available in the initial drop-down menu, " +"select :guilabel:`Search More` to reveal a complete list of all mailing " +"campaigns in the database. Or, type the name of the desired mailing campaign" +" in the :guilabel:`Mailing Campaign` field, until Odoo reveals the desired " +"campaign in the drop-down menu. Then, select the desired campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:347 +msgid "Create new mailing campaign (from Settings tab)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:349 +msgid "" +"To create a new campaign from this :guilabel:`Mailing Campaign` field, start" +" typing the name of this new campaign, and select :guilabel:`Create " +"[Campaign Name]` or :guilabel:`Create and Edit...`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:352 +msgid "" +"Click :guilabel:`Create` to add this new mailing campaign to the database, " +"and modify its settings in the future. And click :guilabel:`Create and " +"Edit...` to add this new mailing campaign to the database, and Odoo reveals " +"a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the email mailing campaign pop-up window in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:360 +msgid "" +"Here, the new mailing campaign can be further customized. Adjust the " +":guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add " +":guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:363 +msgid "" +"The top row of the :guilabel:`Create: Mailing Campaign` pop-up window is " +"filled with analytical smart buttons. Each of which displays various metrics" +" related to the campaign. When clicked, Odoo reveals a separate, more " +"detailed page with even more in-depth statistics." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:367 +msgid "" +"The option to instantly a new communication from this pop-up window is " +"available in the upper-left corner. The adjustable status bar is located in " +"the upper-right." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:370 +msgid "" +"When all modifications are ready to be finalized, click :guilabel:`Save`. To" +" delete the entire campaign, click :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:374 +msgid "Create new mailing campaign (from Campaigns page)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:376 +msgid "" +"When the :guilabel:`Mailing Campaigns` feature is activated, a new " +":guilabel:`Campaigns` option appears in the header of the *Email Marketing* " +"application. Campaigns can also be created on this :guilabel:`Campaigns` " +"page in the *Email Marketing* app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:380 +msgid "" +"To do that, navigate to :menuselection:`Email Marketing app --> Campaigns " +"--> Create`. When that's clicked, a pop-up window appears, in which the " +":guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can" +" be added directly on the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the campaign pop-up window in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:388 +msgid "" +"Click :guilabel:`Add` to add the campaign to the database, and freely edit " +"it later on. Or, click :guilabel:`Edit` and Odoo reveals the campaign " +"template form on a separate page, providing the opportunity to further edit " +"the campaign, send communications related to the campaign, and analyze " +"various metrics related to the campaign, via the smart buttons at the top of" +" the form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:394 +msgid "A/B testing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:396 +msgid "" +"Back in the :guilabel:`Settings` tab of the mailing, if the :guilabel:`Allow" +" A/B Testing` box is checked, recipients are only be mailed to once. This " +"allows different mailings to be sent to randomly selected recipients. This " +"tests the overall effectiveness of the mailing, and eliminates the need for " +"duplicate messages." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:401 +msgid "" +"The :guilabel:`A/B Testing percentage` field represents the percentage of " +"contacts in the database that this message will be mailed to, as a part of " +"the :guilabel:`A/B Testing`. Enter a number between `1-100`. The recipients " +"are randomly chosen." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:406 +msgid "Send, schedule, or test" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:408 +msgid "" +"After finalizing the mailing, Odoo provides the following options in the " +"upper-left corner of the email template page. Those options are: " +":guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:412 +msgid "" +"While in :guilabel:`Edit` mode, there are also buttons to :guilabel:`Save` " +"or :guilabel:`Discard` the mailing, as well." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:415 +msgid "" +":guilabel:`Send` - Click to have Odoo send the email to the desired " +"recipients. When Odoo has sent the mailing, the status changes to *Sent*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:417 +msgid "" +":guilabel:`Schedule` - Click to reveal a pop-up window, in which a future " +"date-time is chosen. Odoo sends the mailing to the desired recipients at " +"that specified date-time. When a date-time is chosen, the status of the " +"mailing changes to *In Queue*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:420 +msgid "" +":guilabel:`Test` - Click to reveal a pop-up window, in which Odoo allows a " +"sample email to be sent for testing purposes. Enter the desired recipient's " +"email address in the :guilabel:`Recipients` field, and click :guilabel:`Send" +" Sample Mail`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:423 +msgid "" +":guilabel:`Save` - Click to save the mailing as a draft, which can be edited" +" (and sent) at a later date. When clicked, the status of the mailing stays " +"as :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:425 +msgid "" +":guilabel:`Discard` - Click to discard any changes that have been made since" +" the last save." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:428 +msgid "" +"When :guilabel:`Save` or :guilabel:`Discard` is selected (while in " +":guilabel:`Edit` mode), those options are replaced with an :guilabel:`Edit` " +"button and a :guilabel:`Create` button. Click :guilabel:`Edit` to re-enter " +":guilabel:`Edit` mode. Click :guilabel:`Create` to start creating a new " +"mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:434 +msgid "" +"By default, there's a daily limit applied for **all emails** sent throughout" +" *all* applications. So, if there are remaining emails to be sent after a " +"limit has been reached, those mailings *will not* be sent automatically the " +"next day. The sending needs to be forced, by opening the email and clicking " +":guilabel:`Retry`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3 +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15 +msgid "Mailing lists" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:5 +msgid "" +"Mailing lists are important for a number of reasons. Mailing lists can " +"provide valuable leads for sales teams, communicate with focus groups " +"participants, contact consumers directly for useful feedback, and more." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:10 +msgid "Create mailing lists" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:12 +msgid "" +"To create a mailing list in the *Email Marketing* application, navigate to " +":menuselection:`Mailing lists --> Mailing lists --> Create`. Clicking " +":guilabel:`Create` reveals a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the mailing list pop-up in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:19 +msgid "" +"In the pop-up, name the mailing list and designate if the mailing list " +"should be public with the :guilabel:`Is Public` checkbox." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:22 +msgid "" +"The :guilabel:`Is Public` option allows the mailing list to be accessible by" +" recipients in the unsubscription page, making it possible for them to " +"update their subscription preferences." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:25 +msgid "" +"After those options have been configured, click :guilabel:`Create` to create" +" the mailing list, which Odoo automatically adds to the :guilabel:`Mailing " +"Lists` page." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:29 +msgid "Add contacts to a mailing list" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:31 +msgid "" +"After a mailing list has been created (and added to the :guilabel:`Mailing " +"Lists` dashboard), click on the desired mailing list to add contacts to the " +"list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:34 +msgid "" +"Clicking the desired mailing list reveals a separate :guilabel:`Mailing List" +" Contacts` page, in which contacts can be added to this specific list by " +"clicking :guilabel:`Create`, and adding contact information directly on a " +"separate contact detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:38 +msgid "" +"Or, while in the :menuselection:`Email Marketing` application, navigate to " +":menuselection:`Mailing Lists --> Mailing List Contacts`. Doing so reveals a" +" separate page with all the mailing list contacts in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:42 +msgid "" +"From here, click :guilabel:`Create`, and add a contact with the same " +"previous steps. Or, click the :guilabel:`Import` icon (to the right of the " +":guilabel:`Create` button) to import contacts into the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:46 +msgid "" +"Once contacts are in the database, click into the desired contact's detail " +"form, and add the preferred mailing list in the :guilabel:`Mailing List` tab" +" (at the bottom of the contact detail form), by clicking :guilabel:`Add a " +"line`, and selecting the desired mailing list. Multiple mailing lists can be" +" added to a single contact's detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of a contact detail form with mailing list tab in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:56 +msgid "Create new mailing list from contact detail form" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:58 +msgid "" +"To create a mailing list from a contact detail form, click :guilabel:`Add a " +"line`, and type in the name of a new mailing list in the empty field that " +"appears. Then, select either :guilabel:`Create` or :guilabel:`Create and " +"Edit...`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the new mailing list drop-down on contact form in Odoo Email " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:66 +msgid "" +"The :guilabel:`Create` option quickly creates the mailing list to the " +"contact detail form, and the list can be configured at a later date. The " +":guilabel:`Create and Edit...` option creates the mailing list, and reveals " +"a pop-up window, in which the new mailing list can be configured right away." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the create and edit mailing list pop-up in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:76 +msgid "Link a mailing list to website (Newsletter blocks)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:78 +msgid "" +"When a mailing list is created in the database, Odoo provides the option to " +"directly link the mailing list on the Odoo-built website (created via Odoo's" +" :guilabel:`Website` application)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:81 +msgid "" +"To link a mailing list to a website, navigate to the front-end of the " +"website, and enter :guilabel:`Edit` mode by clicking :guilabel:`Edit` in the" +" upper-right corner. When clicked, Odoo reveals a right-sidebar, filled with" +" drag-and-drop *Building Blocks* that are packed with various features, " +"options, and design elements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:86 +msgid "" +"Then, to add a *subscription field* for a specific mailing list onto a " +"website, drag-and-drop any of the :guilabel:`Newsletter` options " +"(:guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup`, or " +":guilabel:`Newsletter`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:91 +msgid "" +"To quickly locate the :guilabel:`Newsletter` building block options (while " +"in :guilabel:`Edit` mode on the front-end of the website), type `Newsletter`" +" into the search bar, located in the right sidebar, under the " +":guilabel:`Blocks` tab, and Odoo reveals the three different " +":guilabel:`Newsletter` block options." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "" +"View of how to quickly search for Newsletter blocks in the Odoo Website " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:100 +msgid "" +"When a :guilabel:`Newsletter` block is dragged onto the body of the website," +" Odoo reveals a pop-up window, in which the desired mailing list is selected" +" from a drop-down menu (and linked) to this block on the website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "View of the add mailing list subscription pop-up on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:108 +msgid "" +":guilabel:`Newsletter Block` - Adds a block onto the webpage, providing " +"visitors with the option to add their email address to this mailing list, " +"and subscribe to future communications." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:111 +msgid "Here's an example of a :guilabel:`Newsletter Block`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a sample newsletter block in the Odoo Website application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:116 +msgid "" +":guilabel:`Newsletter Popup` - Tells Odoo to reveal a subscription pop-up " +"window to occur at a certain part of the webpage. When the visitor scrolls " +"to this predetermined point, a pop-up subscription window appears, asking " +"for their email address to subscribe to the mailing list. The pop-up window " +"can be edited further to fit any business needs." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:121 +msgid "Here's an example of a :guilabel:`Newsletter Popup`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a sample newsletter pop-up sample on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:126 +msgid "" +":guilabel:`Newsletter` - Provides visitors with a simple field to add their " +"email address to the mailing list, and subscribe to future mailings in the " +"footer (or anywhere else on the page)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:129 +msgid "Here's an example of a :guilabel:`Newsletter` dynamic block." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a Newsletter dynamic block on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:135 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:73 +msgid ":doc:`/applications/marketing/email_marketing`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:3 +msgid "Manage unsubscriptions (Blacklist)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:5 +msgid "" +"Providing recipients with the power to unsubscribe from mailing lists is not" +" only a smart business practice, it's often a legal requirement. By allowing" +" recipients to unsubscribe from a mailing list establishes a sense of trust " +"with an audience, and helps companies appear genuine (and not spammy)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:10 +msgid "Enable the Blacklist feature" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:12 +msgid "" +"First, the *Blacklist* feature must be enabled. To do that, navigate to " +":menuselection:`Email Marketing app --> Configuration --> Settings`, enable " +"to :guilabel:`Blacklist Options when Unsubscribing`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "" +"View of the blacklist feature in the Settings page of the Odoo Email " +"Marketing app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20 +msgid "" +"With that feature activated, an *Unsubscribe* link appears in mailings. If a" +" recipient clicks that link, Odoo reveals a :guilabel:`Unsubscriptions` " +"page, where they can directly manage their subscriptions." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:25 +msgid "" +"With a test mailing, clicking the :guilabel:`Unsubscribe` link reveals an " +"error page (*error 403 - Access Denied*). To make sure the link is working " +"properly, create the mailing, and only send it to a personal email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:30 +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102 +msgid "Blacklist" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:32 +msgid "" +"In addition to having the option to *Unsubscribe* from specific mailing " +"lists, the recipient can also *Blacklist* themselves, meaning they will not " +"receive *any* more emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:36 +msgid "" +"The mailing list has to be configured as *Public* in order to be visible for" +" users." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:38 +msgid "" +"To view a complete collection of blacklisted email addresses, navigate to " +":menuselection:`Email Marketing app --> Configuration --> Blacklisted Email " +"Addresses`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "View of the blacklisted email addresses page in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:45 +msgid "" +"When a blacklisted record is selected from this page, Odoo reveals a " +"separate page with that blacklisted recipient's contact information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "View of a blacklisted contact detail form in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:52 +msgid "" +"In the :guilabel:`Chatter` of this page, there's a time-stamped message, " +"informing the user when that recipient blacklisted themselves (via a " +":guilabel:`Mail Blacklist created` log note)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56 +msgid "Unblacklist contacts" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:58 +msgid "" +"To *Unblacklist* contacts, click the :guilabel:`Unblacklist` button in the " +"upper-left corner to remove the contact from the blacklist, allowing them to" +" receive mailings once again." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61 +msgid "" +"When :guilabel:`Unblacklist` is clicked, a pop-up appears. In this pop-up, " +"the specific email address is listed, and there's a :guilabel:`Reason` " +"field, in which a reason can be entered, explaining why this particular " +"contact was removed from the blacklist." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "" +"View of the unblacklist pop-up window in the Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:69 +msgid "" +"After filling in the fields, click :guilabel:`Confirm` to officially remove " +"that particular contact from the blacklist." +msgstr "" + +#: ../../content/applications/marketing/events.rst:5 +msgid "Events" +msgstr "" + +#: ../../content/applications/marketing/events.rst:8 +msgid "`Odoo Tutorials: Events `_" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:3 +msgid "Event essentials" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:5 +msgid "" +"Odoo Events provides event coordinators with an arsenal of planning, " +"communications, and reporting tools to create immersive and engaging " +"experiences for customers. Namely, staff can create and publish events on " +"their website, sell tickets online, scan tickets with Odoo barcode, send out" +" automated emails, and generate rich reporting data once the event accepts " +"registrations." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:11 +msgid "Kanban concepts and organization" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:13 +msgid "" +"To get started, click on the :guilabel:`Events` application on the home " +"dashboard, which then leads to the kanban view populated with a variety of " +"pipeline stages. Key information is listed on each event card, such as the " +"date/time of the event, along with the number of expected (and confirmed) " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:18 +msgid "" +"To create a new stage, click :guilabel:`Add a Column` and provide a " +"befitting title to reflect the purpose of that stage." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:21 +msgid "" +"To reorganize the stages, just drag-and-drop them until they are in the " +"correct order. Stages can also be “folded” in the kanban for a cleaner " +"presentation, via the :guilabel:`Settings` menu to the right of each stage's" +" title, which is represented by a gear icon." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:26 +msgid "" +"The gear icon, by default, is hidden and will appear next to the " +":guilabel:`+` icon when moused over." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:29 +msgid "When clicked, a drop-down menu of settings will appear." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "Overview of events setting with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:36 +msgid "Create a new event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:38 +msgid "" +"To create an event, click :guilabel:`Create` from the Events dashboard. Odoo" +" will then direct the page to a blank event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:41 +msgid "" +"From the event form, fill out the necessary fields, either by choosing from " +"existing data in the Odoo database or by creating and editing new field " +"data. Key information to enter for the event includes:" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:45 +msgid ":guilabel:`Event Name`: give the event a title." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:46 +msgid "" +":guilabel:`Date`: includes the start and end dates/times for the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:47 +msgid "" +":guilabel:`Timezone`: covers the timezone for when the event is taking " +"place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:48 +msgid "" +":guilabel:`Template`: choose from a pre-built event template or build a " +"custom one and connect it here." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:50 +msgid "" +":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. " +"`tradeshow`). Tags help better organize event cards in the kanban and are " +"useful when using search filters during reporting periods." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:53 +msgid "" +":guilabel:`Organizer`: detail the organizer(s) for the event. This field is " +"usually the company that owns the Odoo database, or a vendor." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:55 +msgid "" +":guilabel:`Responsible`: name the point person who is responsible for " +"organizing the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:56 +msgid "" +":guilabel:`Website`: indicate which Odoo website(s) the event event should " +"be published to." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:57 +msgid "" +":guilabel:`Venue`: list the venue details here if it's a new record, or " +"choose from an existing location." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:59 +msgid "" +":guilabel:`Limit Registrations`: when enabled, this setting caps the " +"attendee registrations to a specified amount" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:61 +msgid "" +":guilabel:`Autoconfirmation`: when enabled, this setting skips the " +"confirmation request that gets sent by email to event registrants, and " +"automatically confirms their registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:64 +msgid "" +"Once the fields in the event form are set, move on to the " +":guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the " +":guilabel:`Questions` tab if registrations should require additional " +"information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:69 +msgid "Add and sell event tickets" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:71 +msgid "" +"Under the :guilabel:`Tickets` tab, add line items for each type of ticket " +"the event plans to offer. Here, determine the ticket price, start/end dates " +"for registrations, as well as the maximum number of tickets that can be " +"sold." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:75 +msgid "" +"If selling tickets isn't necessary for the event, a simple " +":guilabel:`Registration` button will be displayed on the event's page by " +"default." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the ticket tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:83 +msgid "Send automated emails, text, and social posts to event attendees" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:85 +msgid "" +"Under the :guilabel:`Communication` tab, configure personalized email, SMS, " +"or social post messages to keep in touch with event attendees. For each " +"communication, click :guilabel:`Add a line` in the :guilabel:`Communication`" +" tab form, and then choose (or create) a communications template using the " +"drop-down menu under the :guilabel:`Template` column." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:90 +msgid "" +"Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how " +"often the communication should be sent; use these time fields to specify the" +" frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " +":guilabel:`Months` communications should be sent. There is also the option " +"to send communications `Immediately` after a specified :guilabel:`Trigger` " +"is activated." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:96 +msgid "" +"In the last column, determine the :guilabel:`Trigger` which controls how and" +" when the communication is sent. For this action, choose between: " +":guilabel:`Before the event`, :guilabel:`After each registration`, or " +":guilabel:`After the event`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the communication tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:105 +msgid "Attach a questionnaire to event registrations" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:107 +msgid "" +"Implementing a questionnaire during event sign up is an effective way to " +"gauge the wants, needs, and interests of the event's attendees ahead of " +"time. Questionnaires also act as informative analytics tools for reporting " +"periods before (or after) events take place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:111 +msgid "" +"To create a questionnaire, from the :guilabel:`Events` application, navigate" +" to :menuselection:`Configuration --> Settings` and then enable the " +":guilabel:`Questions` setting." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:114 +msgid "" +"With the setting enabled, questions and answers can now be added (and " +"recorded) under the the :guilabel:`Questions` tab back on the event form. " +"For each question, specify if it should only be asked once with the " +":guilabel:`Ask once per order` checkbox, or if the question requires a " +":guilabel:`Mandatory Answer`, which will make the question required for " +"registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:120 +msgid "" +"If the :guilabel:`Once per order` checkbox is enabled, then a single " +"registration for 3 event attendees will show the questionnaire only once." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:123 +msgid "" +"There are two :guilabel:`Question Types` to choose from: " +":guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` " +"type, allows attendees to select an answer from pre-configured options, " +"which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text " +"Input` type allows attendees to write in their own answer to the question in" +" a text box." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of an event form, open the questions tab, and add a question." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:133 +msgid "Log internal notes or add ticket instructions" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:135 +msgid "" +"In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` " +"and/or :guilabel:`Ticket instructions`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:138 +msgid "" +"Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, " +"contact information, etc.) for event staff to reference. In the " +":guilabel:`Ticket instructions` field, helpful information for staff and " +"attendees can be shared (like, directions to the venue, opening/closing " +"times, etc.)" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:144 +msgid "" +"Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket " +"instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These " +"options provide various formatting options to ensure vital internal " +"information is organized for event staff to review." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the Notes tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:153 +msgid "Invite attendees to the event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:155 +msgid "" +"To invite people to an event, click the :guilabel:`Invite` button located in" +" the top left corner of the event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:158 +msgid "" +"Inside the invite template form, are options to sent email or SMS invites. " +"Each message can be fully customized, and recipients can be added." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:161 +msgid "" +"Adding a :guilabel:`Subject` line for the invite message is required, but " +"the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text`" +" is a catchy preview sentence meant to encourage recipients to open the " +"email." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:166 +msgid "" +"In most cases, the :guilabel:`Preview Text` is displayed next to the " +"subject. Keep this field empty to ensure the first characters of the email " +"content appear, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:170 +msgid "Select invitees and configure recipient filters" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:172 +msgid "" +"In the middle of the invitation form, find and click the " +":guilabel:`Recipients` field, to reveal a drop-down menu of recipient " +"options. These choices represent where Odoo will find the desired " +"recipients' information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:176 +msgid "" +"Once an option from this menu is selected (e.g. :guilabel:`Applicant`, " +":guilabel:`Contact`, :guilabel:`Event Registration`, " +":guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all " +"recipients who match that initial rule. Additional rules can be added to " +"narrow down the target recipients, by clicking :guilabel:`Add Filter`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the add filter button beneath the recipients field in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:185 +msgid "" +"Clicking :guilabel:`Add Filter` reveals three fields, formatted like an " +"equation. To reveal the sub-menu options, click each field, and make the " +"desired selections, until the preferred configuration has been acheived. The" +" number of :guilabel:`Records` that match the rule(s) are indicated to the " +"right of the :guilabel:`Recipients` field, in green." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:194 +msgid "" +"To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and " +":guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line)" +" of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, " +"the :guilabel:`...` icon adds a branch to the node. A branch means two " +"additional, indented sub-nodes are added to the rule, providing even more " +"specificity to the line above it." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:201 +msgid "Build a custom event invite" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:203 +msgid "" +"In the :guilabel:`Mail Body` tab, there are a number of pre-configured " +"message templates to choose from. Select the desired template, and modify " +"every element of its design details with Odoo's drag-and-drop web builder, " +"located on the right sidebar." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the drag and drop building blocks used to customize event invite " +"emails." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:212 +msgid "" +"To build an email event invite from scratch, select the :guilabel:`Plain " +"Text` template, and Odoo will provide a blank email canvas, which can be " +"customized either by using the frontend rich text editor that accepts slash " +"(`/`) commands, or the XML code editor when :ref:`developer mode ` is engaged and the :guilabel:`` icon is pressed." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:218 +msgid "" +"The :guilabel:`Mail Body` tab (and template options), are only available if " +"the event invite :guilabel:`Mailing Type` is designated as an " +":guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a " +":guilabel:`SMS Content` tab (consisting of a blank text space), is " +"available, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:224 +msgid "Modify event invite settings" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:226 +msgid "" +"The options under the :guilabel:`Settings` tab are different, depending on " +"the specified :guilabel:`Mailing Type`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:229 +msgid "" +"If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`," +" an employee can be designated as the :guilabel:`Responsible`, meaning that " +"person is the one responsible for this particular invite message. " +":guilabel:`Send From` and :guilabel:`Reply To` email aliases can be " +"designated here, as well." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:234 +msgid "" +"Also, if any specific documents are required (or helpful) for this event " +"invite, they can be sent along with this email, by clicking " +":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:238 +msgid "" +"If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a" +" :guilabel:`Responsible` can be designated, and the option to " +":guilabel:`Include an opt-out link` is available." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:242 +msgid "Send event invitations to recipients" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:244 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are " +"three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, " +"and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:247 +msgid "" +"The :guilabel:`Send` option sends the invite right away. The " +":guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time" +" can be selected for the email to be sent. The :guilabel:`Test` option " +"reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email " +"addresses can be entered for Odoo to send them the current version of the " +"mailing for review before officially sending it out to prospective event " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:253 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four " +"options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, " +":guilabel:`Schedule`, and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:256 +msgid "" +"The :guilabel:`Put in Queue` option schedules an SMS message to all " +"recipients (that match the designated rules, if any) in the near future. " +"Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. " +"When confirmed, a blue banner appears on the event invite template form, " +"indicating that the SMS will be sent later that day." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:262 +msgid "" +"The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options" +" all function the same way for both :guilabel:`Mailing Type` options." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:266 +msgid "Publish events" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:268 +msgid "" +"Until an event is published, it will remain hidden from public view on the " +"website and registering for it will not be possible. To publish an event, " +"navigate to it either from the backend of Odoo through the " +":guilabel:`Events` application, or access the hidden event page through the " +"frontend as either a priveliged user or administrator." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:273 +msgid "" +"If navigating from the backend, go to the event form, and click the " +":guilabel:`Go to Website` smart button to reach the event page on the " +"website (on the frontend). If starting from the frontend , simply navigate " +"to the event page that needs to be published." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:277 +msgid "" +"No matter the route, an event page can only be published from the frontend. " +"In the upper right corner of the event page on the website, toggle the " +"switch from the red :guilabel:`Unpublished` status to the green " +":guilabel:`Published` status. Doing so instantly makes the event page " +"accessible to the public on the website." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of a website page and the option to publish the event in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:3 +msgid "Sell tickets" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:5 +msgid "" +"Create custom ticket tiers (with various price points) for potential " +"attendees to choose from, directly on the event template form, under the " +":guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by " +"providing plenty of payment method options." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:10 +#: ../../content/applications/marketing/events/track_manage_talks.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:12 +msgid "" +"First, in order to enable the creation (and selling of) event tickets, go to" +" :menuselection:`Configuration --> Settings`, then enable the " +":guilabel:`Tickets` and :guilabel:`Online Ticketing` features." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:16 +msgid "" +"The :guilabel:`Tickets` feature allows tickets to be sold for an event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:18 +msgid "" +"The :guilabel:`Online Tickets` feature allows for the sale of tickets to " +"occur through the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:21 +msgid "" +"If these options are *not* enabled, a default :guilabel:`Register` button " +"will be available for free registrations." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of the settings page for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:29 +msgid "Sell tickets through sales orders" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:31 +msgid "" +"In the :guilabel:`Sales` application, choose a previously-created Event " +"Registration (as if it were a product), and add it as a product line. Upon " +"adding the registration, a pop-up appears, which allows for the selection of" +" a specific event (and ticket tier). That specific event ticket is then " +"attached to the sales order." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of a sales order and option to choose the specific event in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:40 +msgid "" +"Events with tickets sold online or through sales orders have a " +":guilabel:`Sales Smart Button` shortcut, located at the top of the event " +"template form (in the :guilabel:`Events` application)." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:43 +msgid "" +"Clicking the :guilabel:`Sales Smart Button` reveals a page with all the " +"sales orders related to that event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of an event's form and the sales smart button in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of an event form highlighting the column product under the tickets tab in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:56 +msgid "Sell tickets through the website" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:58 +msgid "" +"With tickets purchased through the website, the process is similar to " +"creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` " +"product. Here, tickets are added to a virtual cart, and the transaction can " +"be completed as usual - utilizing any of the pre-configured payment methods " +"options that have been set up on the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:63 +msgid "" +"The completed purchase is automatically produced in a :guilabel:`Sales " +"Order`, which can be easily accessed in the back end of the database." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of website transaction for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +msgid "Track and manage talks" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:5 +msgid "" +"With Odoo Events, it's possible to provide attendees with the power to " +"propose presenters to speak at events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:11 +msgid "" +"First, go to :menuselection:`Events --> Configuration --> Settings` and " +"enable :guilabel:`Schedule & Tracks`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:14 +msgid "" +"When that feature is enabled, two more options become available: *Live " +"Broadcast* and *Event Gamification*." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:17 +msgid "" +":guilabel:`Live Broadcast` allows for the airing of tracks online through a " +"YouTube integration." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:19 +msgid "" +":guilabel:`Event Gamification` allows for the sharing of a quiz with your " +"attendees, once a track (talk) is over." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:23 +msgid "" +":guilabel:`Event Gamification` isn't necessary for tracks to appear on the " +"event page on the website, but it can enhance the engagement and overall " +"enjoyablity of the event for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:27 +msgid "Talks, talk proposals, and agenda" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:29 +msgid "" +"Once those two features are enabled, the following links are automatically " +"added to the sub-header menu, located on the event page on the website: " +":guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any " +"attendee can freely access these menu items and their corresponding content." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:33 +msgid "" +"The :guilabel:`Talks` link takes the attendee to a page full of all the " +"talks for that event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:35 +msgid "" +"The :guilabel:`Talks Proposals` link takes the attendee to a form page, " +"where they can propose talks for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:38 +msgid "" +"The :guilabel:`Agenda` link takes the attendee to a page with all the talks " +"for the event, but in a calendar/time-slot format." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the published website and the talks, talk proposals, and agenda in " +"Odoo Events" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:46 +msgid "Manage talk proposals" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:48 +msgid "" +"When attendees fill out and submit a talk proposal form on the website, a " +"new :guilabel:`Proposal` is instantly created in the back end for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:52 +msgid "" +"All talks (Proposals, Confirmed, Announced, etc.) are accessible via the " +":guilabel:`Tracks` smart button on the event form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the talks' proposals page emphasizing the column proposal in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:59 +msgid "" +"If a proposal is accepted, move the :guilabel:`Event Track` to the " +"appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to " +"that particular event's template form, and click the :guilabel:`Go to " +"Website` smart button to reach that specific talk's page on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:63 +msgid "" +"In the upper right corner, toggle the switch from :guilabel:`Unpublished` to" +" :guilabel:`Published`, and the talk is instantly accessible on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:67 +msgid "Without publishing a talk, attendees will never be able to access it." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "View of the website page to publish a proposed talk for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:74 +msgid "Attendees list and attendance" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:76 +msgid "" +"Once attendees have registered for a specific event, they are added to the " +":guilabel:`Attendee List` for that event, which is accessible via the " +":guilabel:`Attendees` smart button on the event template form, or " +":menuselection:`Reporting --> Attendees` and sorted by event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:81 +msgid "" +"When an attendee arrives at the event, they will be marked as attending " +"(:guilabel:`Confirmed Attendance`), and the status of that attendee will " +"change to :guilabel:`Attended.`" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Overview of events with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:88 +msgid "" +"When analyzing an :guilabel:`Attendees list`, Odoo provides different ways " +"to view the information. Each view option presents the same information, but" +" in a slightly different layout. To change the view, click on the icons in " +"the upper right hand of the screen." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Various view options on the attendees list page." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:96 +msgid "" +"In the :guilabel:`Kanban` view, it can be confirmed whether the attendees " +"have already paid or remain unpaid." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:99 +msgid "" +"The :guilabel:`List` view provides information in a more traditional list " +"formation." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:101 +msgid "" +"The :guilabel:`Calendar` view provides a clear schedule visualization of " +"which attendees are arriving on specific dates of the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:104 +msgid "" +"The :guilabel:`Graph` view provides graphical representations of that " +"event's attendees, along with numerous filters and customizable measures for" +" deeper analysis." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:107 +msgid "" +"The :guilabel:`Cohort` view lays out attendee data to better analyze the " +"number of registration dates." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:111 +msgid "" +"Tickets sold through sales orders validate attendees as soon as the " +"quotation is confirmed." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:114 +msgid "Manage registrations" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:116 +msgid "" +"Upon selecting an attendee, Odoo reveals that specific attendee's detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:118 +msgid "" +"From here, event badges can be sent manually, by selecting :guilabel:`Send " +"By Email`. The :guilabel:`Attendee` can also be marked as " +":guilabel:`Attended`, or the registration can be canceled altogether via the" +" :guilabel:`Cancel Registration` button." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:128 +msgid "Lead Generation Rules" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:130 +msgid "With Odoo, leads can be generated from events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:132 +msgid "" +"To create and configure a :guilabel:`Lead Generation Rule` related to " +"events, navigate to :menuselection:`Events app --> Configuration --> Lead " +"Generation`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:135 +msgid "" +"On the :guilabel:`Lead Generation Rule` page, every configured " +":guilabel:`Lead Generation Rule` can be found, along with pertinent data " +"related to those rules." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule page looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:142 +msgid "" +"To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, " +"and fill out the :guilabel:`Lead Generation Rule` form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule template looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:149 +msgid "" +"After naming the rule, configure *how* the lead should be created (either " +":guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should " +"be created, (when :guilabel:`Attendees are created`, when " +":guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` " +"the event)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:154 +msgid "" +"In the :guilabel:`For any of these Events` section, there are fields to " +"attach this rule to any specific event categories, company, and/or event. To" +" add even more specificity to the rule, a domain filter rule can be " +"configured to ensure the rule only applies to a specific target audience of " +"attendees (found in the :guilabel:`If the Attendees meet these Conditions` " +"section)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:159 +msgid "" +"Lastly, in the :guilabel:`Lead Default Values` section, designate a " +":guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` " +"(and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:8 +msgid "Marketing Automation" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:11 +#: ../../content/applications/marketing/sms_marketing.rst:11 +#: ../../content/applications/marketing/social_marketing.rst:11 +msgid "" +"`Odoo Tutorials: Marketing `_" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3 +msgid "Campaign metrics" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5 +msgid "" +"*Campaign metrics* are detailed statistics and analytics within a marketing " +"campaign, measuring its success and effectiveness. Triggered marketing " +"activities populate relevant activity blocks with real-time metrics, in the " +"campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10 +msgid "Activity analytics" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:12 +msgid "" +"In the :guilabel:`Workflow` section of a campaign detail form in the " +"*Marketing Automation* app, where the various campaign activities are " +"located, a collection of useful data can be found on every individual " +"activity block, like number of communications :guilabel:`Sent`, percentage " +"of messages that have been :guilabel:`Clicked`, and more." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"An activity block in the workflow section with useful analytical data in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:21 +msgid "" +"To the left of the activity block, the configured :doc:`trigger time " +"<../getting_started/workflow_activities>` is displayed as a duration (either" +" :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " +":guilabel:`Months`) if it corresponds to period after the workflow begins." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27 +msgid "" +"If the trigger time is dependent on another activity or triggering action " +"(e.g. :guilabel:`Mail: Replied`, etc.) the time is displayed, along with the" +" necessary action for that activity to be activated (e.g. `Replied after 2 " +"Hours`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "" +"Time trigger display when dependent on another activity in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:35 +msgid "" +"In the activity block, an icon represents each activity type. An " +":guilabel:`✉️ (envelope)` icon means the activity is an email. Three tiny, " +"interlocking :guilabel:`⚙️ (gear)` icons means the activity is an internal " +"action. And, a small, basic :guilabel:`📱 (mobile)` icon means the activity " +"is an SMS." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41 +msgid "" +"The activity type name is also displayed in smaller font below the activity " +"title." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:43 +msgid "" +"Beside the activity icon, at the top of the activity block, is the title of " +"the activity. To the right of the activity title, there are :guilabel:`Edit`" +" and :guilabel:`Delete` buttons." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:46 +msgid "" +"Click :guilabel:`Edit` to open the :guilabel:`Open: Activities` pop-up form " +"for that specific activity, in which that activity can be modified. Click " +"the :guilabel:`Delete` button to completely delete that specific activity " +"from the workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:51 +msgid "" +":doc:`/applications/marketing/marketing_automation/getting_started/workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54 +msgid "Activity graph tab" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:56 +msgid "" +"In every activity block, the :guilabel:`Graph (pie chart icon)` tab is open " +"by default, displaying related metrics as a simple line graph. The success " +"metrics are represented in `green` and the rejected metrics are represented " +"in `red`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:60 +msgid "" +"Numerical representations of both :guilabel:`Success` and " +":guilabel:`Rejected` activities are shown to the right of the line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64 +msgid "" +"Hovering over any point in the line graph of the activity block reveals a " +"notated breakdown of data for that specific date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "" +"Hovering over any point in line graph reveals notated breakdown of data in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71 +msgid "" +"Beneath the graph in the activity block, for *Email* or *SMS* activity " +"types, a line of accessible data figures provide a bird's eye view of the " +"campaign activity, including: :guilabel:`Sent` (numerical), " +":guilabel:`Clicked` (percentage), :guilabel:`Replied` (percentage), and " +":guilabel:`Bounced` (percentage)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:77 +msgid "" +"Clicking any of those stats on the :guilabel:`DETAILS` line, beneath the " +"line graph, reveals a separate page containing every specific record for " +"that particular data point." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:81 +msgid "Activity filter tab" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:83 +msgid "" +"Next to the :guilabel:`Graph` tab on the activity block, there's the option " +"to open a :guilabel:`Filter` tab (represented by a :guilabel:`filter/funnel`" +" icon)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"What a campaign activity filter tab looks like in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:90 +msgid "" +"Clicking the :guilabel:`Filter` tab on an activity block, reveals what the " +"specific filters are for that particular campaign activity, and how many " +"records in the database match that specific criteria." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:95 +msgid "" +"Clicking the :guilabel:`records` link beneath the displayed filter reveals a" +" separate pop-up window containing a list of all the records that match that" +" specific campaign activity rule(s)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:99 +msgid "Link tracker" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:101 +msgid "" +"Odoo tracks all URLs used in marketing campaigns. To access and analyze " +"those URLs, navigate to :menuselection:`Marketing Automation app --> " +"Reporting --> Link Tracker`. Doing so reveals a :guilabel:`Link Statistics` " +"page, wherein all campaign-related URLs can be analyzed." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:109 +msgid "" +"The default view on the :guilabel:`Link Statistics` page is the " +":guilabel:`Bar Chart` view, but there are different view options available " +"in the upper-left corner. There is the option to view the statistics as a " +":guilabel:`Line Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:113 +msgid "" +"Beside that, there is also the option to view the statistics as " +":guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or " +":guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:116 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Number of " +"Clicks` or total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:121 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:153 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:180 +msgid "" +"Also, in the upper-right corner of the :guilabel:`Link Statistics` page, to " +"the far-right of the search bar, there are additional view options to choose" +" from: the default :guilabel:`Graph` view, the :guilabel:`Pivot` table view," +" and the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:126 +msgid "Traces" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:128 +msgid "" +"Odoo tracks all activities used in every marketing campaign. The data " +"related to these activities can be accessed and analyzed in the " +":guilabel:`Traces` page, which can be found by navigating to " +":menuselection:`Marketing Automation app --> Reporting --> Traces`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "The Traces page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:136 +msgid "" +"The default view on the :guilabel:`Traces` page is the :guilabel:`Bar Chart`" +" view, but there are different view options available in the upper-left " +"corner. There is the option to view the statistics as a :guilabel:`Line " +"Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:140 +msgid "" +"At the top of the graph, there's a color key, informing the user which " +"activities have been :guilabel:`Processed`, :guilabel:`Scheduled`, and " +":guilabel:`Rejected`. There's also an outline indicator to inform users of " +"the :guilabel:`Sum` of certain activities, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:144 +msgid "" +"Beside the various view option in the upper-left corner of the " +":guilabel:`Traces` page, there is also the option to view the statistics as " +":guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or " +":guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:148 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Document ID` or " +"total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:158 +msgid "Participants" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:160 +msgid "" +"Odoo tracks all participants related to every marketing campaign. The data " +"related to these participants can be accessed and analyzed in the " +":guilabel:`Participants` page, which can be found by navigating to " +":menuselection:`Marketing Automation app --> Reporting --> Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "The Participants page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:168 +msgid "" +"The default view on the :guilabel:`Participants` page is the :guilabel:`Pie " +"Chart` view, but there are different view options available in the upper-" +"left corner. There is the option to view the statistics as a :guilabel:`Line" +" Chart` or :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:172 +msgid "" +"At the top of the graph, there's a color key that describes the type of " +"participants found in the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:175 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Record ID` or " +"total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started.rst:5 +msgid "Getting Started" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3 +msgid "Marketing automation campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5 +msgid "" +"The Odoo *Marketing Automation* app automates a variety of marketing tasks " +"by combining specific rules and filters to generate timed actions. Instead " +"of manually having to build each stage of a campaign (like a series of timed" +" massmails), the *Marketing Automation* app allows marketers to build the " +"entire campaign, and all of its stages, in one place---on one dashboard." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11 +msgid "Campaign configuration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13 +msgid "" +"To create a new automated marketing campaign, navigate to " +":menuselection:`Marketing Automation app --> New` to reveal a blank campaign" +" form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"A blank marketing automation campaign form in Odoo Marketing Automation " +"application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:20 +msgid "" +"After entering a name for the marketing campaign, configure the target " +"audience in the remaining fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23 +msgid "" +"A target audience can be configured by entering specific criteria for Odoo " +"to use when determining to whom this marketing automation campaign should be" +" sent." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26 +msgid "" +"In the :guilabel:`Target` field, use the drop-down menu to choose which " +"model the target audience filters should be based on (e.g. " +":guilabel:`Contact`, :guilabel:`Lead/Opportunity`, :guilabel:`Sales Order`, " +"etc.)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:30 +msgid "" +"Select :guilabel:`Search More...` from the drop-down menu to reveal a " +":guilabel:`Search: Target` pop-up window containing all of the available " +"targeting options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:33 +msgid "" +"Once a :guilabel:`Target` is selected, there's a :guilabel:`Unicity based " +"on` field. This field is used to avoid duplicates based on the model chosen " +"in the :guilabel:`Target` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:37 +msgid "" +"If :guilabel:`Customers` is chosen as the :guilabel:`Target`, select " +":guilabel:`Email` in the :guilabel:`Unicity based on` field so Odoo only " +"processes one record for each customer email address." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:41 +msgid "" +"Select :guilabel:`Search More...` from the :guilabel:`Unicity based on` " +"drop-down menu to reveal all available options in a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:44 +msgid "" +"Last on the campaign form is the :guilabel:`Filter` field. This is where " +"more specific targeting options can be layered into the campaign to further " +"narrow the number and type of recipients that receive the marketing " +"automation material." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:48 +msgid "" +"If left alone, the :guilabel:`Filter` field reads: :guilabel:`Match all " +"records`. That means Odoo uses the :guilabel:`Target` and :guilabel:`Unicity" +" based on` fields to determine who the recipients will be. The number of " +"recipients is represented beneath as :guilabel:`record(s)`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:53 +msgid "Campaign filter rules" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:55 +msgid "" +"To add a more specific filter to a marketing automation campaign, click the " +":guilabel:`Add condition` button in the :guilabel:`Filter` field. Doing so " +"reveals a series of other configurable filter rule fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59 +msgid "" +"In the rule fields, customizable equations can be configured for Odoo to use" +" when filtering who to include or exclude in this specific marketing " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"How the filter rule equation fields look in Odoo Marketing Automation " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:67 +msgid "" +":guilabel:`Records` refer to contacts in the system that fit the specified " +"criteria for a campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:70 +msgid "" +"Also, once :guilabel:`Add condition` is clicked, the ability to " +":guilabel:`Save as Favorite Filter` becomes available on the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:73 +msgid "" +"There is also the option to match records with :guilabel:`all` or " +":guilabel:`any` of the rules configured in the :guilabel:`Filter` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:76 +msgid "" +"To choose either of those options, click :guilabel:`all` from the middle of " +"the sentence \":guilabel:`Match records with all of the following rules`\" " +"to reveal a drop-down menu with those options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"Match records with all or any of the rules in Filter field for marketing " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:84 +msgid "" +"When the first field of the rule equation is clicked, a nested drop-down " +"menu of options appears on the screen where specific criteria is chosen " +"based on needs of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:87 +msgid "" +"The remaining fields on the rule equation further define the criteria, which" +" is used to determine which records in the database to include or exclude in" +" the execution of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:90 +msgid "" +"To add another rule, either click the :guilabel:`➕ (plus sign)` icon to the " +"right of the filtering rule, or click :guilabel:`New Rule` beneath the rule " +"equation fields. When either are clicked, a new series of rule fields " +"appears." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:94 +msgid "" +"To add a branch of multiple rules at the same time, click the " +":guilabel:`branch` icon, located to the right of the :guilabel:`➕ (plus " +"sign)` icon. When clicked, two additional sub-rule equation fields appear " +"beneath the initial rule." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"Sample of how the rule branches look in the filter section of a marketing " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:102 +msgid "" +"There is also the option to have the filter apply to :guilabel:`any` or " +":guilabel:`all` of the configured branch rules." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:105 +msgid "" +"For further information on marketing automation campaign filter " +"configuration, refer to :doc:`this documentation page `." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:109 +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:153 +msgid ":doc:`workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:110 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:266 +msgid ":doc:`testing_running`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3 +msgid "Target an audience" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 +msgid "" +"Delivering marketing campaigns to the right audience is paramount when " +"trying to grow a business. The Odoo *Marketing Automation* application helps" +" marketers to do just that by providing detailed filtering tools, which can " +"be as simple (or as complex) as necessary, to reach the right customers at " +"the right time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 +msgid "Configure target filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 +msgid "" +"When configuring the target filters on a marketing campaign, there are some " +"options that have an :guilabel:`> (arrow)` icon beside them. The " +":guilabel:`> (arrow)` icon signifies that the particular filter has more " +"refined parameters within it that can be customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "The drop-down filter menu in the Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21 +msgid "" +"Filters can be extended by adding *branches* and *nodes*. A *node* adds " +"another filtering parameter to a group of targeting conditions (e.g. a new " +"line), and a *branch* creates a narrowly refined cluster of parameters, " +"allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` " +"statements." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 +msgid "Every time a new branch is created, there are two options:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28 +msgid "" +"Either the records can match :guilabel:`ALL` criteria for the upcoming rules" +" (creating an AND statement where *all* criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30 +msgid "" +"Or, the records can match :guilabel:`ANY` criteria for the upcoming rules " +"(creating an OR statement where *only one* of the criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33 +msgid "" +"To change between these two options, simply click the drop-down arrow icon " +"in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36 +msgid "" +"To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add " +"another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node" +" or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47 +msgid "" +"The following scenarios outline different combinations of filters a " +"marketing campaign might commonly use." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51 +msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, search for " +":guilabel:`Lead/Opportunity`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, " +"click on the default :guilabel:`ID` filter option in the first portion of " +"the filter equation. Doing so reveals a drop-down menu full of filter " +"options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62 +msgid "" +"Keep the second portion of the filter equation on the default :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64 +msgid "" +"Next, change the third (and final) portion of the filter equation from " +":guilabel:`Lead` to :guilabel:`Opportunity`. The number of " +":guilabel:`Records` that fit this specific filter equation changes as the " +"equation is customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68 +msgid "" +"Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` " +"icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71 +msgid "" +"With \"new\" opportunities being the target of this filter, the second node " +"will focus on *only* locating opportunities that are in the :guilabel:`New` " +"stage of the pipeline. To do that, select the default :guilabel:`ID` from " +"the first portion of the second filter equation, and scroll down (or search " +"for) :guilabel:`Stage` from the field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76 +msgid "" +"Once again, leave the second portion of the filter equation on :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78 +msgid "" +"Lastly, highlight the default value in the third (and final) portion of the " +"second filter equation, and type in `New`. With that in place, Odoo only " +"targets opportunities that are in the \"New\" stage of the pipeline." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "" +"A standard scenario using filters in the Odoo Marketing Automation app." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87 +msgid "" +"Scenario #2: Narrow down target to event attendees who purchased a specific " +"ticket" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, scroll down (or " +"search for) :guilabel:`Event`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on" +" the default :guilabel:`ID` filter option in the first portion of the filter" +" equation. Doing so reveals a drop-down menu full of filter options. From " +"this drop-down, scroll down (or search for) :guilabel:`Event`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98 +msgid "" +"Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of " +"the filter equation. This reveals a drop-down menu. From this drop-down " +"menu, select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101 +msgid "" +"In the third (and final) empty portion of the filter equation, type in the " +"name of the event(s) that Odoo should consider for this campaign filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104 +msgid "" +"Then, add another node to this filter by clicking the :guilabel:`➕ (plus " +"sign)` icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107 +msgid "" +"The second node will focus on targeting this campaign to attendees who " +"purchase a specific type of ticket to the aforementioned event(s) mentioned " +"in the first filter equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110 +msgid "" +"To do that, select the default :guilabel:`ID` from the first portion of the " +"second filter equation, and scroll down (or search for) :guilabel:`Event " +"Ticket` from the field drop-down menu. Then, in that same drop-down menu, " +"select :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:114 +msgid "" +"Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second " +"portion of the filter equation, and select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117 +msgid "" +"Lastly, in the third (and final) portion of the second filter equation, " +"which is blank, type in the name of the ticket type that should be used for " +"the filter. In this case, :guilabel:`Standard` is the name of the event " +"ticket type for this sample filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "An event ticket filter in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 +msgid "Testing/running campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 +msgid "" +"The Odoo *Marketing Automation* app allows users to test marketing campaigns" +" (and mailings) before officially running them to check for errors and " +"correct any mistakes before it reaches its target audience." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:10 +msgid "Test campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:12 +msgid "" +"To test a marketing campaign, open the :menuselection:`Marketing Automation " +"app`, and select the desired campaign to test, which reveals the campaign's " +"detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 +msgid "" +"On the campaign detail form, make sure the campaign already has activities " +"configured in the workflow (or build a campaign by following the directions " +"on :doc:`this documentation " +"`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:20 +msgid "" +"Testing marketing automation campaigns is meant to be performed in the " +"production version of the database. Duplicate (or trial) databases have " +"limited email sending capabilities." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:23 +msgid "" +"To start a test, click the :guilabel:`Launch a Test` button at the top of " +"the campaign form, to the right of the :guilabel:`Start` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Launch a test button on a campaign detail form in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:30 +msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Launch a test pop-up window that appears in Odoo Markting Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:36 +msgid "" +"In the :guilabel:`Launch a test` pop-up window, click the :guilabel:`Pick or" +" create a/an Contact to generate a Test Participant` field to reveal a drop-" +"down menu of contacts. From this drop-down menu, select an existing contact " +"(or create a new one) to run the test on." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:41 +msgid "" +"Only one contact can be selected from the :guilabel:`Launch a test` pop-up " +"window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:43 +msgid "" +"To create a new contact directly from the :guilabel:`Launch a test` pop-up " +"window, start typing the name of the new contact in the blank field, and " +"click :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Typing in a new contact directly from the launch a test pop-up window in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "" +"Doing so reveals a blank :guilabel:`Create Record` pop-up form, in which the" +" necessary contact information (:guilabel:`Email`, :guilabel:`Mobile`, etc.)" +" *must* be entered, in order for the test to work. When the necessary " +"information is entered, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"A blank contact form from a launch test pop-up window in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:58 +msgid "" +"When all the necessary fields have been entered, click :guilabel:`Save & " +"Close` to return to the :guilabel:`Launch a test` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:61 +msgid "" +"Once a contact is selected, click :guilabel:`Launch` to reveal the campaign " +"test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Test screen in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:67 +msgid "" +"On the campaign test page, the name of the :guilabel:`Record` being tested " +"is visible, along with the precise time this test workflow was started in " +"the :guilabel:`Workflow Started On` field. Beneath that, in the " +":guilabel:`Workflow` section is the first activity (or activities) in the " +"workflow that's being tested." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:72 +msgid "" +"To start a test, click the :guilabel:`Run` button, represented by a " +":guilabel:`▶️ (play button)` icon beside the first activity in the workflow." +" When clicked, the page reloads, and Odoo shows the various results (and " +"analytics) connected to that specific activity as they occur, in real-time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:77 +msgid "" +"If a child activity is scheduled beneath a parent activity, that child " +"activity will be revealed slightly indented in the workflow, once that " +"parent activity has been run, via the :guilabel:`▶️ (play button)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Workflow test progress in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:85 +msgid "" +"Once all the workflow activities are completed, the test ends, and the " +"status bar (in the upper-right corner) moves to the :guilabel:`Completed` " +"stage." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:88 +msgid "" +"To stop a test before all the workflow activities are completed, click the " +":guilabel:`Stop` button in the upper-left corner of the campaign test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:92 +msgid "Run campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:94 +msgid "" +"To run a campaign, navigate to :menuselection:`Marketing Automation app`, " +"and select the desired campaign to run." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:97 +msgid "" +"On the campaign detail form, with all the desired activities ready in the " +":guilabel:`Workflow` section, click :guilabel:`Start` in the upper-left " +"corner to officially run the campaign to the configured target audience " +"specified on the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:101 +msgid "" +"Clicking :guilabel:`Start` launches the campaign, and the status bar of the " +"campaign switches to :guilabel:`Running`, which is located in the upper-" +"right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The status of a marketing campaign changing to running in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:109 +msgid "" +"If some participants are already running on a campaign, and was stopped for " +"any reason, clicking the :guilabel:`Start` button again prompts a pop-up " +"warning. This warning advises the user to click an :guilabel:`Update` button" +" to apply any modifications made to the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The workflow has been modified warning pop-up window of a marketing campaign" +" form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:117 +msgid "" +"Be aware that participants that had already gone through an entire campaign " +"in its original state **can** be reintroduced into the newly-modified " +"campaign, and new traces could be created for them." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:121 +msgid "" +"Then, as the mailings and actions are triggered in the :guilabel:`Workflow`," +" the various stats and data related to each activity appear in each activity" +" block. There is also a series of stat-related smart buttons that appear at " +"the top of the campaign detail form, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:125 +msgid "" +"These analytical smart buttons will *also* populate with real-time data as " +"the campaign progresses: :guilabel:`Templates`, :guilabel:`Clicks`, " +":guilabel:`Tests`, :guilabel:`Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The row of smart buttons that appear in a currently running marketing " +"campaign in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:133 +msgid "Stop campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:135 +msgid "" +"To stop a campaign that's currently running, navigate to the " +":menuselection:`Marketing Automation app`, and select the desired campaign " +"to stop. On the campaign detail form, click the :guilabel:`Stop` button in " +"the upper-left corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The stop button on a typical campaign detail form in Odoo Marketing " +"Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:143 +msgid "" +"When clicked, the campaign is officially stopped, and the status changes to " +":guilabel:`Stopped` in the upper-right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Marketing campaign's stopped status on a campaign detail form in Odoo " +"Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:151 +msgid ":doc:`first_campaign`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:152 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:188 +msgid ":doc:`target_audience`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 +msgid "Campaign workflow activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 +msgid "" +"When creating a marketing campaign in the *Marketing Automation* app, users " +"can plan marketing activities that can be triggered when certain actions or " +"inactions occur. These can be activities such as, automated emails, SMS, or " +"internal server actions." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10 +msgid "Add workflow activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:12 +msgid "" +"To add workflow activities to a marketing campaign, navigate to the bottom " +"of a pre-existing or new campaign detail form, beneath the target audience " +"configuration fields, and click :guilabel:`Add new activity`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:16 +msgid "" +"Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up " +"window is a blank activity template, where specific parameters can be set " +"for that particular activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A workflow activity template pop-up window in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 +msgid "" +"First, enter a name for the activity in the :guilabel:`Activity Name` field." +" Then, proceed to configure the following options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:26 +msgid "" +"Once ready, either click: :guilabel:`Save & Close` to save the activity and " +"close the pop-up form, :guilabel:`Save & New` to save the activity and " +"instantly create an additional activity on a fresh :guilabel:`Create " +"Activities` pop-up form, or :guilabel:`Discard` to delete the activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:33 +msgid "" +"Then, select the :guilabel:`Activity Type`. Choose between " +":guilabel:`Email`, :guilabel:`Server Action` (an internal action within the " +"database), or :guilabel:`SMS`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 +msgid "" +"The field below the :guilabel:`Activity Type` changes, depending on the " +"chosen :guilabel:`Activity Type`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 +msgid "Email activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 +msgid "" +"If :guilabel:`Email` is the :guilabel:`Activity Type`, the option to choose " +"a premade/pre-configured :guilabel:`Mail Template` becomes available. A mail" +" template can also be created on-the-fly, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:46 +msgid "" +"To create a new template directly from the :guilabel:`Mail Template` field, " +"start typing the title of the new template into the blank field beside " +":guilabel:`Mail Template`, and select :guilabel:`Create and edit...` to " +"reveal a :guilabel:`Create Marketing Template` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create and edit email drop-down option on create activities pop-up " +"window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:54 +msgid "" +"In that pop-up window, proceed to create and configure the new email " +"template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create marketing template email pop-up window in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 +msgid "Server action activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:63 +msgid "" +"If :guilabel:`Server Action` is the :guilabel:`Activity Type`, the option to" +" choose a specific :guilabel:`Server Action` (e.g. Message for sales person," +" Create Leads on Website clicks, etc.) becomes available." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:67 +msgid "" +"The option to create a new server action directly from the :guilabel:`Server" +" Action` is also available. To do that, type in the name of the new action, " +"then click :guilabel:`Create and Edit...` from the drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create and edit option in the server action field on campaign detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 +msgid "" +"Or, as an alternative, click the empty :guilabel:`Server Action` field to " +"reveal a drop-down menu, and select :guilabel:`Search More...` to reveal a " +":guilabel:`Search: Server Action` pop-up window, containing all the pre-" +"configured server action options to choose from." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79 +msgid "" +"To create a new server action from this pop-up window, and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The new button found on a server action pop-up in Odoo marketing automation " +"application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85 +msgid "" +"Either option reveals a blank :guilabel:`Create Server Action` pop-up, " +"wherein a custom server action can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "SMS activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:91 +msgid "" +"If :guilabel:`SMS` is the :guilabel:`Activity Type`, the option to choose a " +"premade/pre-configured :guilabel:`SMS Template` becomes available. A SMS " +"template can also be created on-the-fly directly from this field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:95 +msgid "" +"To create a new template directly from the :guilabel:`SMS Template` field, " +"start typing the title of the new template into the blank field beside " +":guilabel:`SMS Template`, and select :guilabel:`Create and edit...` from the" +" drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:103 +msgid "" +"Doing so reveals a :guilabel:`Create Marketing Template` pop-up window. In " +"that pop-up window, proceed to create and configure the new SMS template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create marketing template pop-up window to create a SMS template on-the-" +"fly." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:111 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:113 +msgid "" +"The :guilabel:`Trigger` field on the :guilabel:`Create Activities` pop-up " +"form allows users to choose when the designated workflow activity should be " +"triggered." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:116 +msgid "" +"Start by selecting a number in the top field. In the next " +":guilabel:`Trigger` field, designate if it should be :guilabel:`Hours`, " +":guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, click the " +"final field, where it reads :guilabel:`beginning of the workflow` be default" +" to reveal a a drop-down menu of other trigger options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A list of the trigger options available on the workflow activities pop-up " +"form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:125 +msgid "The trigger options are as follows:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:127 +msgid "" +":guilabel:`beginning of the workflow`: the activity will be triggered at the" +" previously-configured time after the beginning of the entire workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:129 +msgid "" +":guilabel:`another activity`: the activity will be triggered at the " +"previously-configured time after another specific activity in the workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:131 +msgid "" +":guilabel:`Mail:opened`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been opened by the " +"recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:133 +msgid "" +":guilabel:`Mail:not opened`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"opened by the recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:135 +msgid "" +":guilabel:`Mail: replied`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been replied to by the " +"recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:137 +msgid "" +":guilabel:`Mail: not replied`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"replied to by the recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:139 +msgid "" +":guilabel:`Mail: clicked`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been clicked by the " +"recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:141 +msgid "" +":guilabel:`Mail: not clicked`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"clicked by the recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:143 +msgid "" +":guilabel:`Mail: bounced`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been bounced back for " +"any reason." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:145 +msgid "" +":guilabel:`SMS: clicked`: the activity will be triggered at the previously-" +"configured time if the sent SMS in the workflow has been clicked by the " +"recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:147 +msgid "" +":guilabel:`SMS: not clicked`: the activity will be triggered at the " +"previously-configured time if the sent SMS in the workflow has not been " +"clicked by the recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:149 +msgid "" +":guilabel:`SMS: bounced`: the activity will be triggered at the previously-" +"configured time if the sent SMS in the workflow has been bounced back for " +"any reason." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:153 +msgid "Expiry duration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:155 +msgid "" +"Next, on the :guilabel:`Create Activities` pop-up form is the " +":guilabel:`Expiry Duration` option." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:157 +msgid "" +"The :guilabel:`Expiry Duration` checkbox provides the option to configure " +"the activity to stop the actions after a specific amount of time (after the " +"scheduled date)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:160 +msgid "" +"When selected, a :guilabel:`Cancel after` field appears, in which the number" +" of :guilabel:`Hours, Days, Weeks, or Months` can be configured for the " +"actions to cease after the initial date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A list of the expiry duration options available on the workflow activities " +"pop-up form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:168 +msgid "Activity and applied filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:170 +msgid "" +"Moving down into the :guilabel:`Domain` section of the :guilabel:`Create " +"Activities` pop-up form, there is the :guilabel:`Activity Filter` and " +":guilabel:`Applied Filter` fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:173 +msgid "" +"The :guilabel:`Activity Filter` field provides the option to configure a " +"recipient filter domain that applies to this activity *and* its child " +"activities. In works in the same fashion as a typical target audience " +"filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:177 +msgid "" +"To add an activity filter, click :guilabel:`Add condition` in the " +":guilabel:`Activity Filter` field and proceed to configure a custom activity" +" filter equation rule(s)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"How to add an activity filter to a workflow activity in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:184 +msgid "" +"This option is not a required field. If left alone, the activity applies to " +"all records related to the target audience of the overall campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:190 +msgid "" +"The :guilabel:`Applied Filter` field is non-configurable. It's simply a " +"summary of when the activity will be performed, *only* if it satisfies the " +"specified domain (e.g. the rules configured in the :guilabel:`Activity " +"Filter` field)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:195 +msgid "" +"After the activity's settings are fully configured, click :guilabel:`Save & " +"Close` to save the activity and return to the marketing automation campaign " +"form, :guilabel:`Save & New` to save the activity and immediately create " +"another one in a fresh :guilabel:`Create Activities` pop-up window, or " +":guilabel:`Discard` to delete the activity and return to the marketing " +"automation campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:202 +msgid "Workflow activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:204 +msgid "" +"Once an activity is created and saved, it appears as an activity card in the" +" :guilabel:`Workflow` section, located at the bottom of the marketing " +"automation campaign form. The analytics related to each activity is " +"displayed as a line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "Typical workflow activity in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:212 +msgid "" +"The configured :guilabel:`Trigger` time for that activity can be found to " +"the left of the :guilabel:`Workflow Activity` card in the " +":guilabel:`Workflow` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:215 +msgid "" +"Once the activity has been triggered, a figure representing the number of " +":guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to " +"the right of the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:219 +msgid "" +"If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`" +" or :guilabel:`SMS`, there are more in-depth analytics beneath the activity " +"graph data, detailing how many messages have been :guilabel:`Sent`, and what" +" percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, " +"or :guilabel:`Bounced`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:225 +msgid "Child activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:227 +msgid "" +"There is also the option to add a *child activity* by clicking " +":guilabel:`Add child activity`, located at the bottom of each activity block" +" in the :guilabel:`Workflow` section of a marketing campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:231 +msgid "" +"Child activities are sub-activities that are connected to and triggered by " +"the activity above it, which is known as its *parent activity*. A child " +"activity is easy to recognize, as its slightly indented beneath its parent " +"activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "A typical child activity indented beneath its parent activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:239 +msgid "" +"Odoo provides a number of triggering options to launch a child activity - " +"all of which depend on the trigger configurations related to its parent " +"activity. Under the desired parent activity, hover over :guilabel:`Add child" +" activity`, to reveal a menu of child activity trigger options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The various child activity trigger options in the workflow section of a " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:247 +msgid "Select any of the following child activity triggers:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:249 +msgid ":guilabel:`Add Another Activity`: instantly adds another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:250 +msgid "" +":guilabel:`Opened`: the next activity will be triggered if the recipient " +"opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:251 +msgid "" +":guilabel:`Not Opened`: the next activity will be triggered if the recipient" +" does not open the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:253 +msgid "" +":guilabel:`Replied`: the next activity will be triggered if the recipient " +"replies to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:254 +msgid "" +":guilabel:`Not Replied`: the next activity will be triggered if the " +"recipient does not reply to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:256 +msgid "" +":guilabel:`Clicked`: the next activity will be triggered if the recipient " +"clicks on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:258 +msgid "" +":guilabel:`Not Clicked`: the next activity will be triggered if the " +"recipient does not click on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:260 +msgid "" +":guilabel:`Bounced`: the next activity will be triggered if the mailing is " +"bounced (not sent)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:262 +msgid "" +"Once a trigger is selected, the user can configure the child activity the " +"same way they would for a regular workflow activity." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:8 +msgid "SMS Marketing" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials.rst:5 +#: ../../content/applications/marketing/social_marketing/essentials.rst:5 +msgid "Essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3 +msgid "Mailing lists and blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5 +msgid "" +"Creating or importing mailing lists in Odoo is very useful when curating " +"content to specific groups of people that already share similar demographics" +" or interests. Mailing lists are also a great way to get started if a " +"company is migrating from another system, and already has a established " +"audience." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10 +msgid "" +"Moreover, providing an audience with the option to 'unsubscribe' from " +"mailings, helps businesses maintain good customer relations, by giving " +"recipients the power to control what they are (and aren't) sent." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17 +msgid "" +"In the :guilabel:`SMS Marketing` app, there's an option on the header menu " +"called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with " +"options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21 +msgid "" +"Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of" +" all mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the main SMS mailing list page on the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28 +msgid "" +"To edit any existing list, select the desired list from the " +":guilabel:`Mailing Lists` page, and proceed to modify it in a number of " +"ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31 +msgid "" +"To create a new mailing list, click :guilabel:`Create` in the upper left " +"corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank " +"mailing list template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list pop-up window in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38 +msgid "" +"First, choose a name for the :guilabel:`Mailing List`, and activate the " +"option :guilabel:`Is Public`, to make the mailing list accessible to " +"recipients on the :guilabel:`Subscription Management page`. Doing so allows " +"users to update their subscription preferences at any time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43 +msgid "" +"Checking the :guilabel:`Is Public` box is not required, but is recommended " +"to maintain good customer relations." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46 +msgid "" +"When those fields are filled in, click :guilabel:`Create` to finalize the " +"form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing " +"list that was just created will be accessible." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49 +msgid "" +"To edit or customize the mailing list further, select the mailing list from " +"the main :guilabel:`Mailing Lists` page to reveal the mailing list detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52 +msgid "" +"Along the top of the mailing list detail form, there are various analytical " +"smart buttons displaying statistics for different metrics related to the " +"mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56 +msgid "" +"To review or edit any of those elements, click the desired smart button to " +"reveal a separate page with in-depth data associated with the mailing list." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59 +msgid "" +"To make changes to the mailing list itself, click the :guilabel:`Edit` " +"button in the upper-left corner of the mailing list detail form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list template form in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67 +msgid "" +"Don't forget to hit the :guilabel:`Save` button once changes have been made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70 +msgid "Mailing lists contacts" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72 +msgid "" +"Access contacts information from one or more mailing lists navigate to " +":menuselection:`Mailing Lists --> Mailing List Contacts` to reveal a " +"dashboard with with all the contacts associated with one or more of the " +"configured mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the mailing lists contact page in the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81 +msgid "" +"By default, Odoo reveals the :guilabel:`Mailing List Contacts` page with the" +" :guilabel:`Exclude Blacklisted Phone` filter in the search bar. Therefore " +"only showing contact information for recipients who still want to receive " +"communications and mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86 +msgid "Communication history in the Chatter" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88 +msgid "" +"An accessible record of every sent mailing(s) is kept on each recipient's " +"*chatter* section, located beneath a recipient's contact form (in the " +"*Contacts* application)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91 +msgid "" +"Database users can reference the chatter to easily keep track of " +"communications, and see a history of interactions with contacts and " +"prospects." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94 +msgid "" +"For example, sales representatives can use the chatter to quickly find out " +"which :abbr:`SMS (Short Message Service)` mailing promotions a certain " +"customer has received (or not received)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of what the chatter looks like in the Odoo Contacts app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:104 +msgid "" +"Odoo *SMS Marketing* has a :guilabel:`Blacklist` feature that provides " +"recipients with the power to add their phone number to a list of people who " +"no longer want to receieve communications or mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108 +msgid "" +"This is also known as the unsubscribe process: customers will automatically " +"be added onto a *blacklist*, if they click :guilabel:`Unsubscribe`, via " +"their :guilabel:`Subscription Management` page. Customers can also be added " +"manually to the blacklist, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112 +msgid "" +"To see a complete collection of blacklisted numbers, navigate to the " +":menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone " +"Numbers` to reveal a dashboard containing every blacklisted phone number in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "SMS Blacklist menu in the application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120 +msgid "" +"To manually add a number to a blacklist, click the :guilabel:`Create` button" +" in the upper-left corner of the dashboard and enter the phone number on the" +" next page's form. There's also a checkbox to indicate whether that " +"particular phone numnber is :guilabel:`Active` (or not)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128 +msgid "" +"Once the form is completed, click :guilabel:`Save` to add it to the " +":guilabel:`Blacklisted Phone Numbers` list. To remove any number from the " +"blacklist, select the desired number on the dashboard, and then, on the " +"phone number's form, click :guilabel:`Unblacklist`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133 +msgid "Importing blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135 +msgid "" +"During a software/platform migration, it is possible to import an already " +"existing blacklist of contacts. This would include customers, who have " +"already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` " +"mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139 +msgid "" +"To do that, navigate to :menuselection:`SMS Marketing app --> Configuration " +"--> Blacklisted Phone Numbers`, and then select the :guilabel:`Favorites` " +"drop-down menu (beneath the search bar), and click :guilabel:`Import " +"records`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of how to import a blacklist in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3 +msgid "SMS campaign settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` campaigns with Odoo *SMS " +"Marketing* isn't just an effective advertisement strategy, it's also a great" +" way to remind people about upcoming events, issued invoices, and so much " +"more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9 +msgid "" +"But, before :abbr:`SMS (Short Message Service)` campaigns can be created " +"(and sent), a few specific settings and features must be enabled first." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13 +msgid "SMS campaign setting" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15 +msgid "" +"To enable :abbr:`SMS (Short Message Service)` campaigns in Odoo, make sure " +"the *Mailing Campaigns* feature is activated by going to " +":menuselection:`Email Marketing --> Configuration --> Settings`, and then " +"enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of the mailing campaigns setting in Odoo." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24 +msgid "" +"Activating the *Mailing Campaigns* feature in the *General Settings* also " +"enables the *A/B Test* feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27 +msgid "" +"Once the setting is enabled, navigate back to the :menuselection:`SMS " +"Marketing` app, and notice the :guilabel:`Campaigns` header menu is now " +"available for use. Similarly, the :guilabel:`A/B Test` tab is now also " +"available on every :abbr:`SMS (Short Message Service)` template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32 +msgid "A/B tests" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34 +msgid "" +":guilabel:`A/B Tests` allows any :abbr:`SMS (Short Message Service)` " +"mailings to be tested against other versions within the same campaign, in " +"order to compare which version is the most successful in producing " +"engagement and/or conversion outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38 +msgid "" +"On an :abbr:`SMS (Short Message Service)` template form, under the " +":guilabel:`A/B Tests` tab, initially, there's only a single checkbox " +"labeled: :guilabel:`Allow A/B Testing.`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41 +msgid "When clicked, a series of other options appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The A/B Test tab is located on an Odoo SMS Marketing app campaign form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47 +msgid "" +"In the first field, enter a desired percentage of recipients to conduct the " +"A/B Test on." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49 +msgid "" +"Beneath the percentage field is the :guilabel:`Winner Selection` field. This" +" is what Odoo will use to determine the successful result of an A/B Test. In" +" other words, this tells Odoo how to pick a winning A/B test." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53 +msgid "" +"The following sections are available: :guilabel:`Manual`, :guilabel:`Highest" +" Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or " +":guilabel:`Revenues`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56 +msgid "" +"Finally, the :guilabel:`Send Final On` field is listed. This represents the " +"date-time that Odoo uses as a deadline to determine the winning mailing " +"variation. Then, Odoo sends that winning mailing variation to the remaining " +"recipients, who weren't involved in the test, at that prior date and time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62 +msgid "" +"Quickly create different versions of the mailing to add to the A/B Test by " +"clicking the :guilabel:`Create an Alternate Version` button." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66 +msgid "" +"Remember, the winning mailing variation is based on the criteria selected in" +" the :guilabel:`Winner Selection` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70 +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 +msgid "Campaigns page" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72 +msgid "" +"To create, edit, or analyze any campaign, click :menuselection:`Campaigns` " +"in the header menu of the :guilabel:`SMS Marketing` app. On the " +":guilabel:`Campaigns` page, each campaign displays various information " +"related to the mailings associated with that campaign (e.g. number of " +"emails, social posts, SMSs, and push notifications)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, " +"separated by stage." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 +msgid "Campaign templates" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84 +msgid "" +"Click :guilabel:`Create` to create a new campaign, and Odoo reveals a blank " +"campaign template form to fill out. Alternatively, select any previously-" +"made campaign in order to duplicate, review, or edit its campaign template " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of an SMS campaign template in Odoo SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92 +msgid "" +"With each campaign, the options to :guilabel:`Send New Mailing`, " +":guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push " +"Notifications` are available above the template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96 +msgid "" +"Whenever one of those communication options is added to the campaign, Odoo " +"will create a new corresponding tab on the template form, where those types " +"of messages can be reviewed or edited, along with various data sets related " +"to each specific mailing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100 +msgid "" +"At the top of the template, there are various analytical smart buttons. When" +" clicked, Odoo reveals in-depth metrics related to that specific topic (e.g." +" :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate " +"page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104 +msgid "" +"Beneath the smart buttons, are fields for :guilabel:`Campaign Name` and " +":guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be" +" added, as well (if necessary)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108 +msgid "Sending SMSs through the Contacts app" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110 +msgid "" +"Sending :abbr:`SMS (Short Message Service)` mailings directly through a " +"contact's form is available by default." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113 +msgid "" +"In order to send an :abbr:`SMS (Short Message Service)` in this fashion, " +"navigate to the :menuselection:`Contacts` app, select the desired contact in" +" the database, and click on the :guilabel:`SMS` icon on the contact form " +"(next to the :guilabel:`Phone Number` field)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS icon is located on an individual's contact form in Odoo Contacts." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121 +msgid "" +"To send a message to multiple contacts at once, navigate to the main " +":menuselection:`Contacts` app main dashboard, choose the :guilabel:`List " +"View`, and select all the desired contacts to whom the message should be " +"sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select a number of contacts, click action, and select send multiple SMSs." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130 +msgid "Set up SMS templates for future use" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132 +msgid "" +"In order to set up :guilabel:`SMS Templates` for future use, activate " +":ref:`developer mode `, by navigating to the main Odoo " +"dashboard that is full of apps, and select the :menuselection:`Settings " +"app`. Then, scroll down to the :guilabel:`Developer Tools` section, and " +"click :guilabel:`Activate the Developer Mode`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137 +msgid "" +"Once *developer mode* is activated, the main Odoo dashboard appears once " +"more, with a now-visible bug icon, which is located at the top-right corner " +"of the dashboard; this bug icon indicates that developer mode is currently " +"active." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141 +msgid "" +"Next return to the :menuselection:`Settings app` and, in the now-visible " +"header menus at the top, choose :menuselection:`Technical --> SMS Templates`" +" to begin setting up :abbr:`SMS (Short Message Service)` templates for " +"future marketing campaigns." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select the SMS Template option in the Technical dropdown on the Settings " +"app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149 +msgid "" +"Inside of the :guilabel:`SMS Templates` dashboard, Odoo reveals an entire " +"page of :abbr:`SMS (Short Message Service)` templates. The default " +":guilabel:`List` view showcases each template's name, and to which " +"recipients it applies." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153 +msgid "" +"On this page, :abbr:`SMS (Short Message Service)` templates can be edited or" +" created from scratch." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS Templates page in Odoo is available after enabling developer mode in the General\n" +"Settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3 +msgid "SMS essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` outreach in communication " +"strategies can help companies expand their market reach, especially in some " +"countries, where emails might not be very common, or even used at all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9 +msgid "" +"Odoo's *SMS Marketing* application can also help boost conversion rates " +"around valuable actions, such as event registrations, free trials, " +"purchases, etc., since text and mobile-based marketing channels typically " +"yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through" +" rate)` outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15 +msgid "SMS marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17 +msgid "" +"When the application is opened, Odoo displays the main :guilabel:`SMS " +"Marketing` dashboard, which showcases the various SMS mailings that have " +"been created, along with pertinent information and data related to that " +"specific message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21 +msgid "" +"The :guilabel:`Kanban` view is the default Odoo uses when the application is" +" opened, which provides an organized display of the SMS mailings that have " +"been created, and what their current status is at the moment." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26 +msgid "" +"An :abbr:`SMS (Short Message Service)` mailing can have one of the following" +" statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or " +":guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29 +msgid "" +"In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, " +"there are a few different view options to choose from. Each one provides a " +"unique take on the same SMS information." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32 +msgid "" +"The :guilabel:`List` view provides the same useful data related to SMS " +"mailings, but in a more traditional list layout." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35 +msgid "" +"The :guilabel:`Calendar` view provides a simple calendar, making it easy to " +"see when SMS mailings are going to be sent (or have been sent). If a future " +"date is clicked, Odoo reveals a blank SMS template that, when completed, " +"will be scheduled to be sent on that specific future date." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39 +msgid "" +"Lastly, the :guilabel:`Graph` view visualizes that same SMS-related data in " +"series of graphs and charts. Odoo also provides various ways to sort and " +"group the data for more detailed analysis." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43 +msgid "Create SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45 +msgid "" +"To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` " +"dashboard, and Odoo reveals a blank SMS template form, which can be " +"configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Creating an SMS marketing template." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52 +msgid "" +"First, give the mailing a :guilabel:`Subject`, which describes what the " +"mailing is about." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54 +msgid "" +"Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS " +"(Short Message Service)` will be sent. By default, Odoo has " +":guilabel:`Mailing List` selected. If this is the desired " +":guilabel:`Recipients` field option, specify which mailing list Odoo should " +"send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select " +"Mailing List` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60 +msgid "" +"To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> " +"Mailing List`. There, Odoo displays all previously created mailing lists, " +"along with various types of data related to that specific list (e.g. number " +"of contacts, mailings, recipients, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 +msgid "" +"To learn more about mailing lists and contacts, check out " +":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "View of the mailing list page in the SMS marketing application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 +msgid "" +"To reveal all the possible options in the :guilabel:`Recipients` field, " +"click the field to see all the choices Odoo makes available." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 +msgid "" +"When another field (other than :guilabel:`Mailing List`) is selected, the " +"option to specify that chosen field even further becomes available — either " +"with a default recipient filter equation that appears automatically (which " +"can be customized to fit any business need), or, if no default recipient " +"filter equation is present, an :guilabel:`Add Filter` button will appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79 +msgid "" +"Clicking the :guilabel:`Add Filter` button, reveals fully customizable " +"domain rule fields, which can be configured similar to an equation. You can " +"create multiple recipient rules, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82 +msgid "" +"Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to " +"recipients who fit into whatever criteria is configured in those fields. " +"Multiple rules can be added." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86 +msgid "" +"If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo " +"database (vendors, customers, etc.) will receive the :abbr:`SMS (Short " +"Message Service)`, by default — unless more specific recipient rules are " +"entered." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90 +msgid "" +"For instance, the message below will only be sent to contacts in the " +"database that are located in the United States (e.g. `Country` > `Country " +"Name` equals `United States`), and they haven't blacklisted themselves from " +"any mailings (e.g. `Blacklist` > `is` > `not set`)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0 +msgid "Contact recipients on SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99 +msgid "Writing SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101 +msgid "" +"Enter the content of the :abbr:`SMS (Short Message Service)` in the text " +"field, found in the :guilabel:`SMS Content` tab. Links and emojis can also " +"be included. Beneath the text field, Odoo displays how many characters are " +"used in the message, along with how many :abbr:`SMS (Short Message Service)`" +" mailings it will take to deliver the complete message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107 +msgid "" +"To check the price of sending an :abbr:`SMS (Short Message Service)` for a " +"country, click on the :guilabel:`Information` icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS price check icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115 +msgid "" +"Credits must be purchased from Odoo in order to take advantage of the *SMS " +"Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be " +"sent without credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119 +msgid "`Odoo SMS - FAQ `_" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122 +msgid "Track links used in SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124 +msgid "" +"When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo " +"automatically generates link trackers to gather analytical data and metrics " +"related to those specific links, which can be found by going to " +":menuselection:`Configuration --> Link Tracker`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Link Tracker page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:133 +msgid "Adjust SMS settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:135 +msgid "" +"Under the :guilabel:`Settings` tab of the SMS template, there is an option " +"to :guilabel:`Include opt-out link`. If activated, the recipient is able to " +"unsubscribe from the mailing list, thus avoiding all future mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:139 +msgid "" +"An employee can be designated as the :guilabel:`Responsible` in the " +":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Settings tab." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:147 +msgid "Send SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:149 +msgid "" +"Once a mailing is created, choose when Odoo should deliver the message from " +"the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:151 +msgid "" +":guilabel:`Send`: sends the message immediately. Consider using this option " +"if the recipient list is highly refined, or in cases that involve fast " +"approaching deadlines, such as a \"flash sale.\"" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:153 +msgid "" +":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. " +"This is typically the best option for mailings related to a specific event. " +"Such a method can also be used to promote a limited-time offer, or to help " +"plan a company's content strategy in advance." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:156 +msgid "" +":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be " +"sent to one or multiple numbers for test purposes. Remember to use a comma " +"between phone numbers if multiple numbers are used as recipients." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:161 +msgid "Visualize reports" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:163 +msgid "" +"On the :guilabel:`Reporting` page (accessible via the " +":menuselection:`Reporting` option in the header menu), there are options to " +"apply different combinations of :guilabel:`Filters` and :guilabel:`Measures`" +" to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, " +":guilabel:`List`, and :guilabel:`Cohort` views.)" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:168 +msgid "" +"Each :guilabel:`Reporting` metric view option allows for more extensive " +"performance analysis of :abbr:`SMS (Short Message Service)` mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:171 +msgid "" +"For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short " +"Message Service)` data is visualized as different graphs and charts, which " +"can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop " +"down menu)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Reporting page in SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:180 +msgid ":doc:`sms_campaign_settings`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:181 +msgid ":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing.rst:5 +msgid "Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 +msgid "SMS Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 +msgid "What do I need to send SMSs?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 +msgid "" +"SMS Text Messaging is an In-App Purchase (IAP) service that *requires " +"prepaid credits* to work." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 +msgid "How many types of SMSs are there?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 +msgid "There are 2 types: GSM7 and UNICODE." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 +msgid "" +"**GSM7** is the standard format, with a limit of 160 characters per message," +" that includes the following characters:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "GSM7 characters available in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 +msgid "" +"**UNICODE** is the format applied if a special character, that *is not* in " +"the GSM7 list, is used. Limit per SMS: 70 characters." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 +msgid "" +"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above" +" these limits, the content is divided into a multi-part message* and the " +"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, " +"in real-time, the system displays the number of SMS mailings the message " +"represents." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 +msgid "How much does it cost to send an SMS?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 +msgid "" +"The price of an SMS depends on the destination and the length (number of " +"characters) of the message. To see the **price per country, please " +"consult**: `Odoo SMS - FAQ `_." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 +msgid "" +"The number of SMSs a message represents will always be available in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "" +"Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 +msgid "How to buy credits" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 +msgid "Go to :menuselection:`Settings --> Buy Credits`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Buying credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 +msgid "Or go to :menuselection:`Settings --> View my Services`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 +msgid "" +"If Odoo Online (Saas) is being used, along with the Enterprise version, free" +" trial credits are available to test the feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 +msgid "More common questions" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Is there an expiration time for my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, credits do not expire." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +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 "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only if that phone number supports SMS (e.g. SIP phones)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I receive an invoice to buy my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can the recipient answer me?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, it is not possible to reply to the SMS." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send multiple SMSs at once, but I don't have enough " +"credits to send them all?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Multiple SMS communications at once at are counted as a single transaction, " +"so no SMSs will be sent until there are enough credits to send them all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I have a history of the sent SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"A history of sent SMSs, along with all pertinent information related to its " +"sent contacts (and the message itself), can be found in the :guilabel:`Sent`" +" column of the main :guilabel:`SMS Marketing` dashboard (while in " +":guilabel:`Kanban` view)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 +msgid "" +"For more detailed information, select a desired SMS from the main dashboard " +"(in :guilabel:`Kanban` view), and click on either link in the blue banner " +"above the SMS detail form to learn more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I send as many SMSs I want at once?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes, if you have enough credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**If an SMS is sent to a number that doesn't exist in the list of " +"recipients, will credits be lost?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"No, not if the phone number is incorrectly formatted (e.g. too many digits)." +" However, if the SMS is sent to the wrong person (or to a fake number), the " +"credit for that SMS will be lost." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send my SMS to a paying number (e.g.: a contest to win a" +" ticket for a festival)?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"The SMS will not be delivered to that kind of number, so no charges will be " +"made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**Can I identify the numbers that do not exist when I send several SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only the ones that have an invalid format." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**How does the GDPR regulation affect this service?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Please find our `Privacy Policy here `__." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I use my own SMS provider?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Yes, but it is not possible out-of-the-box. Odoo experts can help customize " +"a database to allow for the use of a personal SMS provider. Please check our" +" success packs `here `_." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:8 +msgid "Social Marketing" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 +msgid "Social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 +msgid "" +"Social marketing campaigns help companies connect directly with the " +"marketplace. These campaigns are helpful when introducing a new product to " +"customers, explaining the value of a product or service, or when advertising" +" an upcoming event or product release." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 +msgid "" +"The most effective social marketing campaigns typically involve multiple " +"channels to maximize content distribution, and Odoo's *Social Marketing* " +"application acts as a singular control center to monitor, plan, post, track," +" and analyze all of the various content and content channels within a single" +" dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 +msgid "" +"To access a complete overview of all social marketing campaigns, open the " +":menuselection:`Social Marketing` application, and click " +":menuselection:`Campaigns` from the header menu. Doing so reveals a separate" +" page with every campaign in a default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the campaigns page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 +msgid "" +"Each *stage* in the kanban view can be edited, by clicking the " +":guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located" +" to the right of the stage title." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 +msgid "" +"The **gear icon** *only* appears when the cursor hovers to the left of the " +"**+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals " +"the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 +msgid "" +"Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage " +"column can be restored by clicking the folded version of it on the main " +":guilabel:`Campaigns` dashboard in the default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 +msgid "" +"Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name " +"and the sequence of the stage can be modified. If changes are made, be sure " +"to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 +msgid "Clicking :guilabel:`Delete` removes the stage entirely." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 +msgid "" +"To add a new stage to the pipeline, side-scroll to the right on the " +":guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in " +"the desired information, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 +msgid "" +"The same social marketing campaign information on the :guilabel:`Campaigns` " +"dashboard can also be viewed as a list, by selecting the :guilabel:`List` " +"option, located under the search bar, in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 +msgid "Create social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 +msgid "" +"First, open the :menuselection:`Social Marketing` application, and select " +":guilabel:`Campaigns` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 +msgid "" +"On the :guilabel:`Campaigns` dashboard, a new campaign can be created by " +"clicking the quick add :guilabel:`+ (plus sign)` located in the top-right " +"corner of each stage in the pipeline, visible in the kanban view. Campaigns " +"can also be created by clicking :guilabel:`Create` in the upper-left corner " +"of the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 +msgid "" +"Both options reveal a new campaign detail window directly on the " +":guilabel:`Campaigns` dashboard when clicked." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the quick add option for campaigns in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 +msgid "" +"Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and " +":guilabel:`Tags` can be entered. When all modifications are complete, click " +":guilabel:`Add` to add the campaign to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 +msgid "Edit social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 +msgid "" +"In order to edit a campaign in greater detail, and create/send various forms" +" of communications related to it, the template page for that campaign must " +"be accessed and modified, accordingly. There are multiple ways to access a " +"template page for a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 +msgid "" +"After entering the pertinent information in the :guilabel:`Quick Add` " +"campaign drop-down, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 +msgid "" +"Simply select the desired campaign from the :guilabel:`Campaigns` dashboard " +"in list or kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 +msgid "" +"On the :guilabel:`Campaigns` dashboard in the kanban view, select the " +":guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and " +"select :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 +msgid "" +"Any of the above routes will reveal the *Campaign Template* page for that " +"specific campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 +msgid "Social marketing campaign templates" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 +msgid "" +"On a *Campaign Template* page, numerous elements can be customized/modified," +" and various forms of communications can be created, modified, and sent or " +"scheduled. Below is a sample of a completed campaign template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of a sample campaign template page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 +msgid "" +"In order for the :guilabel:`Send New Mailing` option to appear on campaign " +"templates, make sure the *Mailing Campaigns* feature is enabled in the " +"*Email Marketing* app. To do that, navigate to :menuselection:`Email " +"Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing " +"Campaigns`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 +msgid "" +"In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS " +"Marketing* application must be installed on the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 +msgid "Add content and communications to campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 +msgid "" +"If the proper settings and applications are installed (as instructed above)," +" there are four forms of communication/content options that can be added to " +"campaigns. Each of these options are displayed as buttons in the upper-left " +"corner of the campaign template page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 +msgid "" +":guilabel:`Send New Mailing`: reveals a blank email template on a separate " +"page, in which the message can be fully customized in a variety of ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 +msgid "" +":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in " +"which a SMS communication can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 +msgid "" +":guilabel:`Send Social Post`: reveals a blank social post template on a " +"separate page, in which a post can be created, and applied to social media " +"accounts that are already connected to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 +msgid "" +":guilabel:`Push Notification`: reveals a similar blank social post template " +"on a separate page, however, the :guilabel:`Push Notification` options are " +"already pre-selected in the :guilabel:`Post on` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 +msgid "" +"Whichever form of communication is created, once it's completed, Odoo " +"returns to the :guilabel:`Campaign Template` page, showcasing that new " +"content in its corresponding tab (e.g. :guilabel:`Mailings`, " +":guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push " +"Notifications`)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 +msgid "" +"As content and communications are added to a campaign, tabs for those " +"specific mediums appear, along with a variety of analytical smart buttons " +"(e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, " +"etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 +msgid "" +"These smart buttons, located at the top of the template, display different " +"metrics related to the campaign, and its various communications and content." +" Clicking any smart button reveals a separate page dedicated to that " +"particular element of the campaign, allowing for quicker, more organized " +"analysis." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 +msgid "" +"The Odoo *Social Marketing* app is integrated with other Odoo applications, " +"such as *Sales*, *Invoicing*, *CRM*, and *Website*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_essentials`" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 +msgid "Social marketing essentials" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 +msgid "" +"Odoo's *Social Marketing* application helps content marketers create and " +"schedule posts, manage various social media accounts, analyze content " +"effectiveness, and engage directly with social media followers in one, " +"centralized location." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 +msgid "Social media accounts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 +msgid "" +"In order to create social posts and analyze content with Odoo *Social " +"Marketing*, social media accounts **must** be added as a *stream* on the " +"application's main dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 +msgid "" +"Be aware that personal profiles **cannot** be added as a stream. The main " +"use of Odoo *Social Marketing* is to manage and analyze business accounts on" +" social media platforms." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:20 +msgid "" +"Odoo *Social Marketing* has some limitations in regards to social media " +"accounts. For example, Odoo **cannot** handle a large quantity of various " +"pages (e.g. ~40 pages) under the same company. The same limitations are " +"present in a multi-company environment because of how the API is " +"constructed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:26 +msgid "" +"In multi-company environments, if every company doesn't activate a page at " +"once, it will result in a permission error." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 +msgid "" +"For example, if Company 1 is the only company selected from the main Odoo " +"dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those" +" pages will be accesible on the *Social Marketing* dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:33 +msgid "" +"However, if on that same database, the user adds Company 2 from the company " +"drop-down menu in the header, and attempts to add those same streams, it " +"results in a permission error." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"View of the permission error that appears when incorrectly attempting to add" +" stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:41 +msgid "Social media streams" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:43 +msgid "" +"To add a social media business account as a stream, navigate to " +":menuselection:`Social Marketing app` and select the :guilabel:`Add A " +"Stream` button located in the upper-left corner. Doing so reveals an " +":guilabel:`Add a Stream` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the pop-up window that appears when Add a Stream is selected in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:51 +msgid "" +"In the :guilabel:`Add a Stream` pop-up window, choose to :guilabel:`Link a " +"new account` for a business from any of the following popular social media " +"platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, " +":guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:55 +msgid "" +"After clicking the desired social media outlet from the :guilabel:`Add a " +"Stream` pop-up window, Odoo navigates directly to that specific social media" +" outlet's authorization page, where permission must be granted, in order for" +" Odoo to add that particular social media account as a stream to the *Social" +" Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample of a populated social marketing dashboard with social media streams " +"and content." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +msgid "" +"Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on " +"the main :guilabel:`Social Marketing` dashboard, and a new column, with that" +" account's posts, is added. Accounts/streams can be added at any time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:69 +msgid "" +"A :guilabel:`Facebook` page can be added as long as the :guilabel:`Facebook`" +" account that grants permission is the administrator for the page. It should" +" also be noted that different pages can be added for different streams." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:74 +msgid "" +":guilabel:`Instagram` accounts are added through a :guilabel:`Facebook` " +"login because it uses the same API. This means, an :guilabel:`Instagram` " +"account needs to be linked to a :guilabel:`Facebook` account in order for it" +" to show up as a stream in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:79 +msgid "Posts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 +msgid "" +"Clicking on a post from a social media stream reveals a pop-up window, " +"showcasing the content of that specific post, along with all the engagement " +"data related to it (e.g. likes, comments, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample of a social media post's pop-up window in Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:88 +msgid "" +"If desired, the user can leave a new comment of the post from the post's " +"pop-up window, by typing one in the :guilabel:`Write a comment...` field, " +"and clicking :guilabel:`Enter` to post that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:93 +msgid "Create leads from comments" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:95 +msgid "" +"Odoo *Social Marketing* also provides the ability to create leads directly " +"from social media comments." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:98 +msgid "" +"To create a lead from a comment left on a social media post, click on the " +"desired post from the dashboard to reveal that post's specific pop-up " +"window. Then, scroll to the desired comment, and click the :guilabel:`three " +"vertical dots` icon to the right of that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:102 +msgid "" +"Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"The drop-down menu beside a comment revealing the option to create a lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:108 +msgid "" +"Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a " +":guilabel:`Conver Post to Lead` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"The convert post to lead pop-up window that appears in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:115 +msgid "" +"In this pop-up window, select to either: :guilabel:`Create a new customer`, " +":guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a " +"customer`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:119 +msgid "" +"If :guilabel:`Link to an existing customer` is selected, a new " +":guilabel:`Customer` field appears beneath those options, wherein a customer" +" can be chosen to be linked to this lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 +msgid "" +"Once the desired selection has been made, click the :guilabel:`Convert` " +"button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. " +"Doing so reveals a fresh lead detail form, where the necessary information " +"can be entered and processed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New lead detail form generated from a social media comment in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:131 +msgid "Insights" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:133 +msgid "" +"When a social media account stream is added to the *Social Marketing* " +"dashboard, each stream also displays and links that specific social media " +"platform's KPIs (if the platform has them)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:136 +msgid "" +"To get redirected to the statistics and metrics related to any social media " +"account's KPIs, click on the :guilabel:`Insights` link, located at the top " +"of each stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Visual of how the Insights link appears on the dashboard of the Social " +"Marketing app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 +msgid "" +"In a multi-company environment, if not *all* pages are selected, de-" +"authentication happens." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:146 +msgid "" +"For example, if the companies have 3 *Facebook* pages, but only grant access" +" to 1, and try to grant access to another at a later date, they will be de-" +"authenticated, and access to the initial page's insights/analytics will be " +"lost." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:150 +msgid "" +"So, be sure to add *all* pages for *all* companies in a multi-company " +"environment to avoid this issue. If a page gets de-autenticated, simply " +"remove the stream, and re-establish it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:154 +msgid "Create and post social media content" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:156 +msgid "" +"Odoo *Social Marketing* offers the ability to create and post content for " +"social media accounts directly through the application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:159 +msgid "" +"To create content for social media accounts, navigated to the " +":menuselection:`Social Marketing app`, and click :guilabel:`New Post` " +"located in the upper-right corner of the *Social Marketing* dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New Post button on the main dashboard of the Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:167 +msgid "" +"Or, navigate to :menuselection:`Social Marketing app --> Posts` and click " +"the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New button on the Social Posts page in the Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:174 +msgid "" +"Either route reveals a blank social media post detail form that can be " +"customized and configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "Blank social media post detail page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 +msgid "Post detail form" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:184 +msgid "" +"The social media post detail form in Odoo *Social Marketing* has many " +"different configurable options available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:188 +msgid "Company" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:190 +msgid "" +"If working in a multi-company environment, the first field in the " +":guilabel:`Your Post` section of the social media post detail form is " +":guilabel:`Company`. In this field, select the company that should be " +"connected to this specific social media post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:195 +msgid "Post on" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 +msgid "" +"If working in a single-company environment, the first field in the " +":guilabel:`Your Post` section of the social media post detail form is " +":guilabel:`Post on`. In this field, determine which social media outlets " +"(streams) this post is intended to be posted on, and/or which website's " +"visitors this post should be sent to, via push notification, by checking the" +" box beside the desired option(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 +msgid "" +"Odoo automatically provides every available social media account that's been" +" linked to the database as an option in this section. If a social media " +"account hasn't been added as a stream to the *Social Marketing* application," +" it will **not** appear as an option on the post template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 +msgid "" +"Multiple social media outlets (streams) and websites can be selected in the " +":guilabel:`Post on` field. At least **one** option in the :guilabel:`Post " +"on` field *must* be selected." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:210 +msgid "" +"In order for the :guilabel:`Push Notification` option to appear on the " +"social media post detail form in Odoo *Social Marketing*, make sure the " +"*Enable Web Push Notifications* feature is enabled in the *Website* app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:214 +msgid "" +"To do that, navigate to :menuselection:`Website app --> Configuration --> " +"Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the " +"corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:219 +msgid "Message" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:221 +msgid "" +"Next, there's the :guilabel:`Message` field. This is where the main content " +"of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:223 +msgid "" +"In the :guilabel:`Message` field, type in the desired message for the social" +" post. After typing, click away from the :guilabel:`Message` field to reveal" +" visual samples of how the post will look on all the previously selected " +"social media accounts (and/or websites, as push notifications)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample social media post with visual samples of how it will appear on social" +" media outlets." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:232 +msgid "" +"Emojis can also be added directly to the text in the :guilabel:`Message` " +"field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line " +"of the :guilabel:`Message` field to the far right. Clicking this icon " +"reveals a drop-down menu containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +msgid "" +"If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a " +"character counter appears beneath the :guilabel:`Message` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:241 +msgid "Attach Images" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:243 +msgid "" +"If images are to be used in the post, click the :guilabel:`Attach Images` " +"button, in the :guilabel:`Attach Images` field, located beneath the " +":guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In " +"this pop-up window, select the desired image from the hard drive, and upload" +" it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:248 +msgid "" +"After successfully uploading and attaching the desired image, Odoo reveals a" +" new preview of the social media post, complete with the newly-added image, " +"on the right side of the detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Visualized samples of post with newly-attached images in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 +msgid "Campaign" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:258 +msgid "" +"Next, there is the :guilabel:`Campaign` field. This non-required field " +"provides the options to attach this post to a specific marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:261 +msgid "" +"To add this post to a pre-existing campaign, click the empty " +":guilabel:`Campaign` field to reveal a drop-down menu, containing all the " +"existing campaigns in the database. Select the desired campaign from this " +"drop-down menu to add this post to that campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 +msgid "" +"To create a new campaign directly from the social media post detail form, " +"start typing the name of the new campaign in the blank :guilabel:`Campaign` " +"field, and select either :guilabel:`Create` or :guilabel:`Create and " +"edit...`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Drop-down menu options of Create or Create and edit in the Campaign field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:273 +msgid "" +"Clicking :guilabel:`Create` creates the campaign, which can be " +"edited/customized later." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +msgid "" +"Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a " +":guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign " +"Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly " +"configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Create campaign pop-up window that appears on a social media post detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 +msgid "" +"When all the desired settings have been entered, click :guilabel:`Save & " +"Close` to save the campaign and return to the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:287 +msgid "When" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:289 +msgid "" +"Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to " +"have Odoo publish the post immediately, or :guilabel:`Schedule later` to " +"have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:293 +msgid "" +"If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` " +"field appears. Clicking the empty field reveals a pop-up calendar, in which " +"a future date and time can be designated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Schedule date pop-up window that appears on social media post detail form in" +" Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 +msgid "" +"After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo" +" will promptly publish the post at that specific date and time on the pre-" +"detemined social media account(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:304 +msgid "" +"If scheduling a post, the :guilabel:`Post` button at the top of the social " +"media post detail form changes to :guilabel:`Schedule`. Be sure to click " +":guilabel:`Schedule` after completing the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 +msgid "" +"Doing so, locks in that specific date/time for Odoo to send the post, and it" +" changes the status of the post to :guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +msgid "Push Notification Options" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 +msgid "" +"If one (or multiple) :guilabel:`[Push Notification]` options are chosen in " +"the :guilabel:`Post on` field, a specific :guilabel:`Push Notification " +"Options` section appears at the bottom of the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "Push notification options section on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 +msgid "It should be noted that *none* of these fields are required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:324 +msgid "" +"The first field in this section is :guilabel:`Notification Title`. In this " +"field, there is the option to add a custom title to the push notification " +"that will be sent." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +msgid "" +"To designate a specific page on the website that should trigger this push " +"notification, enter that page's URL in the :guilabel:`Target URL` field. " +"Then, once a visitor reaches that specific page, Odoo will display the push " +"notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:331 +msgid "" +"Below that field is the option to add a custom :guilabel:`Icon Image` to the" +" push notification. This is an icon that appears beside the push " +"notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:334 +msgid "" +"To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering " +"over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up " +"window, in which the desired icon image can be located on the hard drive, " +"and subsequently uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:338 +msgid "" +"Once that's complete, Odoo automatically updates the visual preview of how " +"the icon appears on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:342 +msgid "" +"Next, if the post is scheduled to be posted later, there is the option to " +"ensure the post is sent in the visitor's timezone, by enabling the " +":guilabel:`Local Time` option. If enabled, Odoo will send it at the " +"appropriate, pre-determined time, taking the visitor's location into " +"consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"The Local Time option in the Push Notification Options section of features." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:351 +msgid "" +"Then, there is the :guilabel:`Match all records` field. This field provides " +"the ability to target a specific group of recipients in the database, based " +"on certain criteria, and can be applied to match :guilabel:`all` or " +":guilabel:`any` of the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:355 +msgid "" +"To utilize this field, click the :guilabel:`+ Add condition` button, which " +"reveals an equation-like rule field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:358 +msgid "" +"In this equation-like rule field, specifiy the specific criteria Odoo should" +" take into account when sending this post to a particular target audience." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Push notification conditions set up to match a specific amount of records in" +" the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:365 +msgid "" +"To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the " +"far-right of the rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:367 +msgid "" +"To add a branch (series of additional rules based on the previous rule, to " +"further specify a target audience), click the unique :guilabel:`branch " +"icon`, located to the right of the :guilabel:`➕ (plus sign) icon`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:371 +msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:373 +msgid "" +"The size of the specified target audience of recipients is represented by " +"the number of :guilabel:`Records` displayed beneath the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:377 +msgid "Posts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:379 +msgid "" +"To see a complete overview of posts, go to Odoo :menuselection:`Social " +"Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every " +"post that has been created and posted with Odoo can be seen and accessed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:383 +msgid "" +"There are four different view options for the :guilabel:`Social Posts` page " +"data: *kanban*, *calendar*, *list*, and *pivot*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:386 +msgid "" +"The view options are located in the upper right corner of the " +":guilabel:`Posts` page, beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:393 +msgid "" +"By default, Odoo displays the posts in a kanban view. The information on " +"this page can be sorted even further, via the left sidebar, where all " +"connected social accounts and posts can be quickly seen, accessed, and " +"analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:397 +msgid "" +"The kanban view is represented by an :guilabel:`inverted bar graph icon` in " +"the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"Kanban view of the posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 +msgid "Calendar view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:406 +msgid "" +"The calendar view option displays a visual representation of posts in a " +"calendar format of when posts were published, or are scheduled to be " +"published. This option provides a clear overview of any planned day, week, " +"or month, and Odoo displays all drafted, scheduled, and published posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:411 +msgid "" +"Clicking on a date reveals a blank social media post detail form, in which a" +" social media post can be created, and Odoo will post it on that specific " +"date/time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:414 +msgid "" +"The calendar view is represented by a :guilabel:`calendar icon` in the " +"upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "Example of the calendar view in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:422 +msgid "" +"The list view option is similar to the kanban option, but instead of " +"individual blocks, all post information is displayed in a clear, list " +"layout. Each line of the list displays the :guilabel:`Social Accounts`, " +":guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:426 +msgid "" +"There is also a helpful left sidebar that organizes all posts by " +":guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as " +"well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:429 +msgid "" +"The list view is represented by four vertical lines in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the list option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:435 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:437 +msgid "" +"The pivot view option provides a fully customizable grid table, where " +"different measures of data can be added and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the pivot option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:444 +msgid "" +"The pivot view option provides numerous analytical options, allowing for in-" +"depth, detailed analysis of various posts and metrics." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:447 +msgid "" +"Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot " +"table to reveal more metric options to add to the grid." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:450 +msgid "" +"While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is " +"available, located to the right of the :guilabel:`Measures` drop-down menu, " +"in the upper-left corner of the :guilabel:`Social Posts` page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:454 +msgid "" +"Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to" +" the pivot view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:456 +msgid "From left to right, those options are:" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:458 +msgid "" +":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid " +"table." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:459 +msgid "" +":guilabel:`Expand All`, which expands each line in the grid, revealing more " +"detailed information related to it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:461 +msgid "" +":guilabel:`Download`, which, when clicked, instantly downloads the pivot " +"table as a spreadsheet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:465 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:467 +msgid "" +"To see a complete overview of all the people who have visited the website(s)" +" connected to the database, navigate to :menuselection:`Social Marketing app" +" --> Visitors`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "View of the Visitors page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:474 +msgid "" +"Here, Odoo provides a detailed layout of all the visitors' pertinent " +"information in a default kanban view. If visitors already have contact " +"information in the database, the option to send them an :guilabel:`Email` " +"and/or an :guilabel:`SMS` is available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:478 +msgid "" +"This same visitor data can also be viewed as a list or a graph. Those view " +"options are located in the upper-right corner of the :guilabel:`Visitors` " +"page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:482 +msgid "Social media page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:484 +msgid "" +"Another way to quickly link social media accounts to Odoo *Social Marketing*" +" can be done on the :guilabel:`Social Media` page. To access the " +":guilabel:`Social Media` page, navigate to :menuselection:`Social Marketing " +"app --> Configuration --> Social Media`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:488 +msgid "" +"On the :guilabel:`Social Media` page there is a collection of all social " +"media options, each complete with a :guilabel:`Link account` button: " +":guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, " +":guilabel:`Twitter`, :guilabel:`YouTube`, and :guilabel:`Push " +"Notifications`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social media page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:497 +msgid "Social accounts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:499 +msgid "" +"To see a list of all social accounts and websites linked to the database, go" +" to :menuselection:`Social Marketing app --> Configuration --> Social " +"Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, " +"the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, " +"who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it " +"is associated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social accounts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:509 +msgid "" +"To edit/modify any of the social accounts on this page, simply select the " +"desired account from the list on this page, and proceed to make any " +"adjustments necessary." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:513 +msgid "Social streams page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:515 +msgid "" +"To view a separate page with all the social media streams that have been " +"added to the main *Social Marketing* dashboard, navigate to " +":menuselection:`Social Marketing app --> Configuration --> Social Streams`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:523 +msgid "" +"Here, the social stream information is organized in a list with the " +":guilabel:`Social Media`, the :guilabel:`Title` of the stream, the " +":guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`," +" etc.), who it was :guilabel:`Created by`, and the :guilabel:`Company` to " +"which it is associated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:528 +msgid "" +"To modify any stream's information, simply click the desired stream from the" +" list, and proceed to make any necessary adjustments." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:532 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:5 +msgid "Surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:8 +msgid "`Odoo Tutorials: Surveys `_" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:3 +msgid "Survey essentials" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:5 +msgid "" +"Companies often use surveys to collect valuable information from their " +"customers and employees, which in turn, allows them to make more informed " +"business decisions." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:8 +msgid "" +"In Odoo, surveys are used to collect customer feedback, evaluate the success" +" of a recent event, measure the satisfaction of customers (or employees), " +"and gain more insight into shifting market sentiments." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:13 +msgid "Getting started" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:15 +msgid "" +"To begin, open the :guilabel:`Surveys` application and click " +":guilabel:`Create`. Odoo then redirects the page to a blank survey template " +"form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:18 +msgid "" +"On the survey form, add a :guilabel:`Survey Title` and then add a cover " +"image to the survey by hovering over the photo icon and clicking on the " +":guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose " +"an image from the local files." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:22 +msgid "" +"Below the :guilabel:`Survey Title` are various tabs in which the survey " +"questions and format can be created and customized. These tabs are labeled " +"as follows:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:25 +msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:26 +msgid "" +":guilabel:`Description`: contextual information to aid in understanding the " +"survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:27 +msgid "" +":guilabel:`Options`: choices for survey respondents to answer the questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "Various tabs that can be found on the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:34 +msgid "Questions tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:36 +msgid "" +"Add questions and sections to the survey in the :guilabel:`Questions` tab. A" +" section divides the survey into parts in order to visually group similar " +"questions together. To make a section, click :guilabel:`Add a section` and " +"type in a section name. Then, add questions or drag and drop questions into " +"the divided sections." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:41 +msgid "" +"Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and" +" Questions` pop-up to create and customize the survey question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "The survey question pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:49 +msgid "Create questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:51 +msgid "" +"In the :guilabel:`Create Sections and Questions` pop-up, type the question " +"in the :guilabel:`Question` field. Then, choose the :guilabel:`Question " +"Type`. A preview of how the question type looks is shown in the preview " +"window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:55 +msgid "Choose from the following :guilabel:`Question Types`:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:57 +msgid ":guilabel:`Multiple Lines Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:58 +msgid ":guilabel:`Single Line Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:59 +msgid ":guilabel:`Numerical Value`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:60 +msgid ":guilabel:`Date`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:61 +msgid ":guilabel:`Datetime`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:62 +msgid ":guilabel:`Multiple choice: only one answer`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:63 +msgid ":guilabel:`Multiple choice: multiple answers allowed`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:64 +msgid ":guilabel:`Matrix`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:67 +msgid "" +"Different features appear in the :guilabel:`Answers` and :guilabel:`Options`" +" tabs, depending on the :guilabel:`Question Type` chosen. However, the " +":guilabel:`Description` tab always remains the same, regardless of what " +"question is chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:72 +msgid "Create sections and questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:74 +msgid "" +"Once a :guilabel:`Question Type` has been selected, there are three possible" +" tabs where information can be customized for the question. These include " +"the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and " +":guilabel:`Options` tabs." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:78 +msgid "" +"Each tab offers a variety of different features depending on what " +":guilabel:`Question Type` was chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:81 +msgid "" +"For example, in the :guilabel:`Options` tab, the following options may " +"appear:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:83 +msgid ":guilabel:`Mandatory Answer`: the question must be answered." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:84 +msgid "" +":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or " +"multiple choices can be selected per row." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:86 +msgid ":guilabel:`Number of columns`: select how many columns are displayed." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:87 +msgid ":guilabel:`Images on answers`: allow images on the answer options." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:88 +msgid "" +":guilabel:`Conditional Display`: determine if the question is displayed " +"based on the participant's answer to a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:90 +msgid "" +":guilabel:`Show Comments Field`: allow the participant to type a comment in " +"a text box." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:91 +msgid "" +":guilabel:`Question Time Limit`: for live session surveys, set a time limit " +"for the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:94 +msgid "Conditional Display" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:96 +msgid "" +":guilabel:`Conditional Display` means the question is only displayed if the " +"specified conditional answer has been selected in a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:99 +msgid "" +"When the box next to :guilabel:`Conditional Display` is selected, the " +":guilabel:`Triggering Question` field appears. Select a question from the " +"survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:102 +msgid "" +"Then, a :guilabel:`Triggering Answer` field appears. Here, select which " +"answer will trigger this :guilabel:`Conditional Display` question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:106 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:108 +msgid "" +"Back on the main survey template form, under the :guilabel:`Options` tab, " +"there are different sections of settings that can be modified." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:111 +msgid "The sections include:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:113 +msgid "" +":guilabel:`Questions`: focuses on the overall presentation of the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:114 +msgid ":guilabel:`Scoring`: decides how the survey is scored" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:115 +msgid ":guilabel:`Candidates`: manages access to the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:116 +msgid "" +":guilabel:`Live Session`: enables the survey into a real-time group " +"activity." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:119 +msgid "Questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:121 +msgid "" +"First, select the :guilabel:`Layout` of the survey. The following options " +"can be chosen:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:123 +msgid ":guilabel:`One page with all the questions`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:124 +msgid ":guilabel:`One page per section`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:125 +msgid ":guilabel:`One page per question`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:127 +msgid "" +"If either the :guilabel:`One page per section` or :guilabel:`One page per " +"question` options are chosen, then the :guilabel:`Back Button` option " +"appears. If selected, the :guilabel:`Back Button` option allows the " +"participant to go back to a question during the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:131 +msgid "" +"Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` " +"setting, which indicates how the participant's progress during the survey is" +" displayed. It is shown as either a :guilabel:`Percentage` or a " +":guilabel:`Number`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:135 +msgid "" +"Next, there is an option available to add a :guilabel:`Survey Time Limit`. " +"To implement this option, simply check the box, and enter the amount of time" +" (in minutes) participants have to complete the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:139 +msgid "" +"After the :guilabel:`Survey Time Limit` option is a section labeled " +":guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per " +"section`, in other words, the number of random questions can be configured " +"by section. This mode is ignored in a live session." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:144 +#: ../../content/applications/marketing/surveys/scoring.rst:56 +msgid ":doc:`time_random`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:147 +msgid "Scoring" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:149 +msgid "" +"The following options are available when deciding how a :guilabel:`Scoring` " +"method:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:151 +msgid ":guilabel:`No scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:152 +msgid ":guilabel:`Scoring with answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:153 +msgid ":guilabel:`Scoring without answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:155 +msgid "" +"If either the :guilabel:`Scoring with answers at the end` or " +":guilabel:`Scoring without answers at the end` options are selected, a " +":guilabel:`Success %` field appears. Set the percentage of correct answers " +"needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:159 +msgid "" +"Next, there is the option to make the survey a certification. To do so, " +"check the box next to the option labeled :guilabel:`Is a Certification`, and" +" two additional fields appear. Select a color theme in the " +":guilabel:`Certification Template` field and then choose an :guilabel:`Email" +" Template`. When a participant passes the certification with the required " +"score, an email from Odoo will automatically be sent to that person using " +"the selected email template." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:165 +msgid "" +"If the :guilabel:`Give Badge` feature is enabled and the " +":guilabel:`Certification Badge` is set, the survey participant also receives" +" a badge upon passing the certification." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:169 +#: ../../content/applications/marketing/surveys/time_random.rst:48 +msgid ":doc:`scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:172 +msgid "Candidates" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:174 +msgid "" +"To determine access to the survey, the :guilabel:`Access Mode` has two " +"options to choose between: :guilabel:`Anyone with the link` and " +":guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:177 +msgid "" +"Below the :guilabel:`Appraisal Managers Only` checkbox is the " +":guilabel:`Login Required` option to require a login to participate in the " +"survey. If this option is activated, an :guilabel:`Attempts Limit` field " +"also populates, in which the number of survey attempts is defined for the " +"participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:182 +msgid "Live Session" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:184 +msgid "" +"The :guilabel:`Live Session` section is dedicated to users who are " +"conducting surveys in real-time, wherein they directly engage with and " +"collect answers from a live audience." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:187 +msgid "" +"Customize the :guilabel:`Session Code` here; this code is needed for " +"participants to access the live session survey. Reward participants for " +"quick answers by selecting the checkbox labeled :guilabel:`Reward quick " +"answers`. By checking it, attendees will get more points if they answer " +"quickly." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:193 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:195 +msgid "" +"Back on the main survey template page is the :guilabel:`Description` tab, " +"where a custom description of the survey can be added. This is displayed " +"beneath the title on the survey's homepage, which is on the front end of the" +" website made through the Odoo :guilabel:`Website` app." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:200 +msgid "Test and share the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:202 +msgid "" +"Once the survey is created and saved, run a test to check for possible " +"errors before finally sending it out to the participants by clicking " +":guilabel:`Test` in the upper left corner of the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:206 +msgid "" +"When activated, Odoo redirects the page to a test version of the survey on " +"the front end of the website. This page displays how the survey will look to" +" participants. Proceed to run through the survey, like a normal participant," +" to check for errors." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:210 +msgid "" +"To return to the survey template form in the backend, simply click the " +":guilabel:`This is a test survey. Edit Survey` link in the blue banner along" +" the top of the page. Once Odoo redirects the page to the survey template in" +" the backend, make any further changes, as needed, before officially sending" +" the survey out to participants." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:215 +msgid "" +"When the survey is ready to be shared with the audience, click the " +":guilabel:`Start Survey` button in the upper-left corner of the survey " +"template form. Then, click :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:218 +msgid "" +"In the pop-up window, add the survey recipients in the " +":guilabel:`Recipients` field (for existing contacts in the Odoo database) or" +" the :guilabel:`Additional emails` field (for contacts that do not want to " +"be listed in the Odoo database). Finally, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:222 +msgid "" +"As answers are received, check them by clicking the :guilabel:`Answers` " +"smart button on the survey template form, or the :guilabel:`See Results` " +"button in the upper left corner. To end the survey, click the " +":guilabel:`Close` button on the survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:3 +msgid "Scoring surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:5 +msgid "" +"To measure a survey participant's performance, knowledge, or overall " +"satisfaction, Odoo ascribes points to survey answers. At the end of the " +"survey, these points are summed up, resulting in the participant's final " +"score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:9 +msgid "" +"To add points to questions, open the :guilabel:`Surveys` application, choose" +" the desired survey form, and then click on the :guilabel:`Options` tab. " +"Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring " +"with answers at the end` or :guilabel:`Scoring without answers at the end`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:14 +msgid "" +":guilabel:`Scoring with answers at the end` shows the survey participant " +"their answers after completing the survey, and displays which questions they" +" got right or wrong. On questions where there was an incorrect answer, the " +"correct answer will be highlighted." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:18 +msgid "" +":guilabel:`Scoring without answers at the end` does not show the survey " +"participant their answer choices after completing the survey, only their " +"final score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:21 +msgid "" +"To indicate correct answers, click on the :guilabel:`Questions tab` and " +"choose a question. In the question form, check the :guilabel:`Is a correct " +"answer` box for the choice that is the correct answer and attach a score " +"value." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:25 +msgid "" +"Back on the :guilabel:`Options` tab of the survey, set the " +":guilabel:`Success %`. The percentage entered determines what percentage of " +"correct answers is needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:28 +msgid "" +"Further on the :guilabel:`Options` tab of the survey, survey administrators " +"can also choose to make the survey a certification. A certification " +"indicates that the survey asks questions to test the participants' knowledge" +" level on a subject." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:32 +msgid "" +"When enabling the :guilabel:`Is a certification` option, choose a " +":guilabel:`Certification email template`. The certification will " +"automatically be emailed using this email template to users who pass the " +"survey with a final score that is greater than or equal to the set " +":guilabel:`Success %`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:36 +msgid "" +"In the :guilabel:`Candidates` section, participants can be required to log " +"in to take the survey. If the :guilabel:`Login Required` setting is enabled," +" two new options appear: the :guilabel:`Attempts Limit` checkbox, which " +"limits the number of times a participant can attempt the survey, and the " +"option to :guilabel:`Give Badge`, located beneath the " +":guilabel:`Certification` options in the :guilabel:`Scoring` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "" +"Setting the Required Score (percentage), login required, and certification " +"template." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:46 +msgid "" +"Badges are displayed on the eLearning portion of a given user's portal, and " +"are a way to set milestones and reward participants for passing surveys or " +"gaining points. Besides the awardee, website visitors who access the " +":guilabel:`Courses` page will also be able to see the granted badges." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "Example of how a badge looks on the eLearning portion of the website." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:3 +msgid "Timed and randomized questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:5 +msgid "" +"When creating a survey in Odoo, there are options to set a time limit on the" +" survey and randomize the questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:9 +msgid "Time limit" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:11 +msgid "" +"During a timed survey, participants must finish the survey within a " +"specified period of time. A common use case for implementing a time limit is" +" that it greatly reduces the chance of participants looking up responses via" +" external resources (e.g. web search), and reduces the survey to a \"closed " +"book\" testing environment." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:16 +msgid "" +"Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` " +"tab of the survey form, under the :guilabel:`Questions` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Time limit field in the options tab of a survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:23 +msgid "" +"When the :guilabel:`Survey Time Limit` option is checked, a timer will be " +"displayed on every page of the survey, letting participants keep track of " +"the time remaining while the survey is active." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:27 +msgid "" +"Participants that do not submit their survey by the preconfigured time limit" +" will *not* have their answers saved." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:31 +msgid "Randomized selection" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:33 +msgid "" +"When a survey is randomized, Odoo shuffles the questions and reveals them in" +" a random order every time a participant begins the questionnaire. Using " +"randomization as a survey method discourages participants from looking at " +"each other's responses, and helps control for individual testing." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:37 +msgid "" +"To randomize a survey, click the :guilabel:`Options` tab on the survey form." +" In the :guilabel:`Questions` section, select :guilabel:`Randomized per " +"section` for the :guilabel:`Selection` field. After enabling, navigate to " +"the :guilabel:`Questions` tab and look in the :guilabel:`Random questions " +"count` column. From there, determine how many questions (per section) Odoo " +"should select and display during the shuffling of questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Randomized question count in the questions tab of a survey." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/productivity.po b/locale/hi/LC_MESSAGES/productivity.po new file mode 100644 index 000000000..dd718d2cb --- /dev/null +++ b/locale/hi/LC_MESSAGES/productivity.po @@ -0,0 +1,10161 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/productivity.rst:5 +msgid "Productivity" +msgstr "" + +#: ../../content/applications/productivity/calendar.rst:5 +#: ../../content/applications/productivity/studio/views.rst:201 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:3 +msgid "Synchronize Google calendar with Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:5 +msgid "" +"Synchronize Google Calendar with Odoo to see and manage meetings from both " +"platforms (updates go in both directions). This integration helps organize " +"schedules, so a meeting is never missed." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:9 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:10 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:13 +msgid "Setup in Google" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:16 +msgid "Select (or create) a project" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:18 +msgid "" +"Create a new Google API project and enable the Google Calendar API. First, " +"go to the `Google API Console `_ and " +"log into the Google account." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:22 +msgid "" +"If this is the first time visiting this page, Google will prompt the user to" +" enter a country and agree to the Terms of Service. Select a country from " +"the drop-down list and agree to the :abbr:`ToS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:26 +msgid "" +"Next, click :guilabel:`Select a project` and select (or create) an API " +"project to configure OAuth in, and store credentials. Click :guilabel:`New " +"Project`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Create a new API project to store credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:34 +msgid "" +"Give the API Project a clear name, like \"Odoo Sync\", so it can be easily " +"identified." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:37 +msgid "Enable Google calendar API" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:39 +msgid "" +"Now, click on :guilabel:`Enabled APIs and Services` in the left menu. Select" +" :guilabel:`Enabled APIs and Services` again if the :guilabel:`Search bar` " +"doesn't appear." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable APIs and Services on the API Project." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:46 +msgid "" +"After that, search for `Google Calendar API` using the search bar and select" +" :guilabel:`Google Calendar API` from the search results. Click " +":guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable the Google Calendar API." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:54 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:56 +msgid "" +"Now that the API project has been created, OAuth should be configured. To do" +" that, click on :guilabel:`OAuth consent` in the left menu and then select " +"the :guilabel:`User Type`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:60 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:64 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:67 +msgid "" +"In the second step, :guilabel:`OAuth Consent Screen`, type `Odoo` in the " +":guilabel:`App name` field, select the email address for the :guilabel:`User" +" support email` field, and type the email address for the " +":guilabel:`Developer contact information` section. Then, click " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:72 +msgid "" +"Skip the third step, :menuselection:`Scopes`, by clicking :guilabel:`Save " +"and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:74 +msgid "" +"Next, if continuing in testing mode (External), add the email addresses " +"being configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:78 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:80 +msgid "" +"Now, the OAuth consent has been configured, and it's time to create " +"credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:83 +msgid "Create credentials" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:85 +msgid "" +"The *Client ID* and the *Client Secret* are both needed to connect Google " +"Calendar to Odoo. This is the last step in the Google console. Begin by " +"clicking :guilabel:`Credentials` in the left menu. Then, click " +":guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, " +"Google will open a guide to create credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:90 +msgid "" +"Under :menuselection:`Create OAuth Client ID`, select :guilabel:`Website " +"application` for the :guilabel:`Application Type` field, and type `My Odoo " +"Database` for the :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:93 +msgid "" +"Under the :guilabel:`Authorized JavaScript Origins` section, click " +":guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform " +"Resource Locator)` address." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:95 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ " +"Add URI` and type the company's Odoo :abbr:`URL (Uniform Resource Locator)` " +"address followed by `/google_account/authentication`. Finally, click " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Add the authorized JavaScript origins and the authorized redirect URIs." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:103 +msgid "" +"A :guilabel:`Client ID` and :guilabel:`Client Secret` will appear, copy " +"these to a notepad." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:106 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:108 +msgid "" +"Once the *Client ID* and the *Client Secret* are located, open the Odoo " +"database and go to :menuselection:`Settings --> General Settings --> " +"Integrations --> Google Calendar`. Check the box next to :guilabel:`Google " +"Calendar`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "The Google Calendar checkbox in General Settings." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:116 +msgid "" +"Next, copy and paste the *Client ID* and the *Client Secret* from the Google" +" Calendar API credentials page into their respective fields below the " +":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:121 +msgid "Sync calendar in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:123 +msgid "" +"Finally, open the :menuselection:`Calendar` app in Odoo and click on the " +":guilabel:`Google` sync button to sync Google Calendar with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Click the Google sync button in Odoo Calendar to sync Google Calendar with " +"Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:131 +msgid "" +"When syncing Google Calendar with Odoo for the first time, the page will " +"redirect to the Google Account. From there, select the :guilabel:`Email " +"Account` that should have access, then select :guilabel:`Continue` (should " +"the app be unverifed), and finally select :guilabel:`Continue` (to give " +"permission for the transfer of data)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Give Odoo permission to access Google Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:140 +msgid "Now, Odoo Calendar is successfully synced with Google Calendar!" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:143 +msgid "" +"Odoo highly recommends testing the Google calendar synchronization on a test" +" database and a test email address (that is not used for any other purpose) " +"before attempting to sync the desired Google Calendar with the user's " +"production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:147 +msgid "Once a user synchronizes their Google calendar with the Odoo calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:149 +msgid "" +"Creating an event in Odoo causes Google to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:150 +msgid "" +"Deleting an event in Odoo causes Google to send a cancellation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:151 +msgid "" +"Adding a contact to an event causes Google to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:152 +msgid "" +"Removing a contact from an event causes Google to send a cancellation to all" +" event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:154 +msgid "" +"Events can be created in Google Calendar without sending a notification by " +"selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:3 +msgid "Outlook Calendar synchronization" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:5 +msgid "" +"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping " +"track of their tasks and appointments across all related applications." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:9 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:10 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:13 +msgid "Register the application with Microsoft Azure" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:15 +msgid "" +"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account" +" is needed. Creating an account is free for users who have never tried or " +"paid for Azure. For more information, `click here " +"`_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:19 +msgid "" +"Refer to `Microsoft's documentation `_ on how to" +" set up an Microsoft Entra ID (formally called *Microsoft Azure Active " +"Directory (Azure AD)*), which is a representation of an organization to " +"manage and register apps." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:24 +msgid "" +"Then, `Register an Application `_, choosing the " +"appropriate :guilabel:`Supported account type`. Users who wish to connect " +"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any " +"organizational directory (Any Microsoft Entra ID directory - Multitenant) " +"and personal Microsoft accounts (e.g. Skype, Xbox)` option for " +":guilabel:`Supported account types`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:30 +msgid "" +"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and " +"copy the Odoo database URI (URL) followed by " +"`/microsoft_account/authentication`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:34 +msgid "" +"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` " +"for the :guilabel:`Redirect URI`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "" +"The \"Supported account type\" and \"Redirect URI\" settings in the " +"Microsoft Entra ID portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:41 +msgid "" +"For more information on the restrictions and limitations of URIs, `check " +"this page `_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:44 +msgid "" +"Regarding the application credentials, the user *must* add a client secret, " +"which allows Odoo to authenticate itself, requiring no interaction from the " +"user's side. :guilabel:`Certificates` are optional." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:48 +msgid "" +"To do add a client secret, click :guilabel:`Add a certificate or secret` and" +" then click :guilabel:`New client secret`. Next, type a " +":guilabel:`Description` and select when the client secret " +":guilabel:`Expires`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:52 +msgid "" +"Since resetting the synchronization can be tricky, Odoo recommends setting " +"the maximum allowed expiration date for the client secret (24 months), so " +"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to " +"generate the client secret (:guilabel:`Secret ID`)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:57 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:59 +msgid "" +"In the Odoo database, go to :menuselection:`Settings --> General Settings " +"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook Calendar\" setting activated in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:66 +msgid "" +"From the Microsoft Azure portal, under the :guilabel:`Overview` section of " +"the application, copy the :guilabel:`Application (Client) ID`, and paste it " +"into the :guilabel:`Client ID` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client ID\" in the Microsoft Azure portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:73 +msgid "" +"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` " +"section, copy the :guilabel:`Client Secret Value` and paste it into the " +":guilabel:`Client Secret` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:80 +msgid "" +"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:85 +msgid "Sync with Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:89 +msgid "" +"Odoo highly recommends testing the Outlook calendar synchronization on a " +"test database and a test email address (that is not used for any other " +"purpose) before attempting to sync the desired Outlook Calendar with the " +"user's production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:93 +msgid "" +"If the user has any past, present, or future events on their Odoo calendar " +"before syncing their Outlook calendar, Outlook will treat the events pulled " +"from Odoo's calendar during the sync as new events, causing an email " +"notification to be sent from Outlook to all the event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:97 +msgid "" +"To avoid unwanted emails being sent to all past, present, and future event " +"attendees, the user must add the events from the Odoo calendar to the " +"Outlook calendar before the first ever sync, delete the events from Odoo, " +"and then start the sync." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:101 +msgid "" +"Even after synchronizing the Odoo Calendar with the Outlook calendar, " +"Outlook will still send a notification to all event participants every time " +"an event is edited (created, deleted, unarchived, or event date/time " +"changed), with no exceptions. This is a limitation that cannot be fixed from" +" Odoo's side." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:106 +msgid "" +"In summary, once a user synchronizes their Outlook calendar with the Odoo " +"calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:108 +msgid "" +"Creating an event in Odoo causes Outlook to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:109 +msgid "" +"Deleting an event in Odoo causes Outlook to send a cancellation to all event" +" attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:110 +msgid "" +"Unarchiving an event in Odoo causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:111 +msgid "" +"Archiving an event in Odoo causes Outlook to send a cancellation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:112 +msgid "" +"Adding a contact to an event causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:113 +msgid "" +"Removing a contact from an event causes Outlook to send a cancellation to " +"all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:116 +msgid "Sync Odoo Calendar and Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:118 +msgid "" +"In the Odoo database, go to the :guilabel:`Calendar` module and click the " +":guilabel:`Outlook` sync button. The page will redirect to a Microsoft login" +" page, and the user is asked to log in to their account, if they are not " +"already, and grant the required permissions." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook\" sync button in Odoo Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:126 +msgid "" +"The synchronization is a two-way process, meaning that events are reconciled" +" in both accounts (Outlook and Odoo)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:130 +msgid "" +"All users that want to use the synchronization simply need to :ref:`sync " +"their calendar with Outlook `. The configuration of " +"Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' " +"Client IDs and Client Secrets are unique, and represent an organization that" +" helps the user to manage a specific instance of Microsoft cloud services " +"for their internal and external users." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:137 +msgid ":doc:`../mail_plugins/outlook`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:138 +msgid ":doc:`google`" +msgstr "" + +#: ../../content/applications/productivity/discuss.rst:8 +msgid "Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:3 +msgid "Configure ICE servers with Twilio" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:5 +msgid "" +"Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and " +"video calls. If one of the call attendees is behind a symmetric NAT, you " +"need to configure an ICE server to establish a connection to the call " +"attendee. To set up an ICE server, first, create a Twilio account for video " +"calls, and then, connect that Twilio account to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:11 +msgid "Create a Twilio account" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13 +msgid "" +"First, go to `Twilio `_ and click :guilabel:`Sign " +"up` to create a new Twilio account. Next, enter your name and email address," +" create a password, and accept Twilio's terms of service. Then, click " +":guilabel:`Start your free trial`. Verify your email address with Twilio, as" +" per their instructions." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 +msgid "" +"Next, enter your phone number into Twilio. Then, Twilio will send you an SMS" +" text message containing a verification code. Enter the verification code " +"into Twilio to verify your phone number." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:22 +msgid "" +"After that, Twilio redirects to a welcome page. Use the following list to " +"answer Twilio's questions:" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:25 +msgid "" +"For :guilabel:`Which Twilio product are you here to use?`, select " +":guilabel:`Video`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:26 +msgid "" +"For :guilabel:`What do you plan to build with Twilio?`, select " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:27 +msgid "" +"For :guilabel:`How do you want to build with Twilio?`, select " +":guilabel:`With no code at all`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:28 +msgid "" +"For :guilabel:`What is your goal today?`, select :guilabel:`3rd party " +"integrations`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The Twilio welcome page." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34 +msgid "" +"If necessary, change the billing country. Finally, click :guilabel:`Get " +"Started with Twilio`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:37 +msgid "Locate the Twilio Account SID and Auth Token" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:39 +msgid "" +"To locate the Account SID and Auth Token, go to the Twilio account " +"dashboard. Then, click :guilabel:`Develop` on the sidebar. In the " +":guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the" +" :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "" +"The Twilio Account SID and Auth Token can be found uner the Account Info " +"section." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49 +msgid "Connect Twilio to Odoo" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:51 +msgid "" +"Open the Odoo database and go to :menuselection:`Settings --> General " +"Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE " +"servers` and enter the Twilio account's :guilabel:`Account SID` and " +":guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these " +"changes." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61 +msgid "Define a list of custom ICE servers" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:63 +msgid "" +"This step is not required for the Twilio configuration. However, if Twilio " +"is not configured or is not working at any given moment, Odoo will fall back" +" on the custom ICE servers list. The user must define the list of custom ICE" +" servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:67 +msgid "" +"In :menuselection:`Settings --> General Settings --> Discuss`, click the " +":guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE Servers\" button in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74 +msgid "" +"Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define " +"your own list of ICE servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE servers\" page in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:82 +msgid "" +"For on-premise instances of Odoo, the package `python3-gevent` is necessary " +"for the Discuss module to run calls/video calls on Ubuntu (Linux) servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:3 +msgid "Get started with Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:5 +msgid "" +"Odoo *Discuss* is an internal communication app that allows users to connect" +" through messages, notes, and file sharing, either through a persistent chat" +" window that works across applications, or through the dedicated *Discuss* " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:12 +msgid "Choose notifications preference" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:14 +msgid "" +"Access user-specific preferences for the *Discuss* app by navigating to " +":menuselection:`Settings app --> Users --> User --> Preferences tab`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the Preferences tab for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:21 +msgid "" +"By default, the :guilabel:`Notification` field is set as :guilabel:`Handle " +"by Emails`. With this setting enabled, a notification email will be sent by " +"Odoo every time a message is sent from the chatter, a note is sent with an " +"`@` mention (from chatter), or a notification is sent for a record that the " +"user follows. Something that triggers a notification is changing of the " +"stage (if an email\\ is configured to be sent, for example if the task is " +"set to :guilabel:`Done`)." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:27 +msgid "" +"By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in" +" the *Discuss* app's *inbox*. Messages can have the following actions taken " +"on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or " +"reply to the message by clicking on :guilabel:`Reply`. Additional actions " +"may include starring the message by clicking :guilabel:`Marked as Todo`, or " +"pinning the message by selecting :guilabel:`Pin` or even mark the message as" +" unread by selecting :guilabel:`Marked as unread`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of an inbox message and its action options in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:38 +msgid "" +"Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the " +":guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the " +"message to :guilabel:`History`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of messages marked as todo in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:46 +msgid "Start chatting" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:48 +msgid "" +"The first time a user logs in to their account, OdooBot sends a message " +"asking for permission to send desktop notifications for chats. If accepted, " +"the user will receive push notifications on their desktop for the messages " +"they receive, regardless of where the user is in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of the messages under the messaging menu emphasizing the request for push\n" +"notifications for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:58 +msgid "" +"To stop receiving desktop notifications, reset the notifications settings of" +" the browser." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:60 +msgid "" +"To start a chat, go to the :menuselection:`Discuss` app and click on the " +":guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or " +":guilabel:`Channels` in the left menu of the dashboard." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n" +"Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:69 +msgid "" +"A company can also easily create :doc:`public and private channels " +"`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:73 +msgid "Mentions in the chat and on the chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:75 +msgid "" +"To mention a user within a chat or the chatter, type `@user-name`; to refer " +"to a channel, type `#channel-name`. The user mentioned will be notified in " +"their *inbox* or through an email, depending on their communication " +"settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of a couple of chat window messages for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:84 +msgid "" +"When a user is mentioned, the search list (list of names) suggests values " +"first based on the task's followers, and secondly on employees. If the " +"record being searched does not match with either a follower or employee, the" +" scope of the search becomes all partners." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:89 +msgid "User status" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:91 +msgid "" +"It is helpful to see what colleagues are up to and how quickly they can " +"respond to messages by checking their *status*. The status is shown on the " +"left side of a contact's name on the :guilabel:`Discuss` sidebar, on the " +"*messaging menu* and when listed in the *chatter*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:95 +msgid "Green = online" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:96 +msgid "Orange = away" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 +msgid "White = offline" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 +msgid "Airplane = out of the office" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the contacts' status for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:106 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:107 +msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 +msgid "" +"*Activities* are follow-up tasks tied to a record in an Odoo database. " +"Activities can be scheduled on any page of the database that contains a " +"chatter thread, kanban view, list view, or activities view of an " +"application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 +msgid "" +"One way that activities are created is by clicking the :guilabel:`Schedule " +"Activity` button, located at the top of the *chatter* on any record. On the " +"pop-up window that appears, select an :guilabel:`Activity Type` from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 +msgid "" +"Enter a title for the activity in the :guilabel:`Summary` field, located in " +"the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 +msgid "" +"To assign the activity to a different user, select a name from the " +":guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the " +"activity is automatically assigned." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 +msgid "" +"Lastly, feel free to add any additional information in the optional " +":guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 +msgid "" +"The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up " +"window auto-populates based on the configuration settings for the selected " +":guilabel:`Activity Type`. However, this date can be changed by selecting a " +"day on the calendar in the :guilabel:`Due Date` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 +msgid "" +":guilabel:`Schedule`: adds the activity to the chatter under " +":guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 +msgid "" +":guilabel:`Mark as Done`: adds the details of the activity to the chatter " +"under :guilabel:`Today`. The activity is not scheduled, it is automatically " +"marked as completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 +msgid "" +":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` " +"marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 +msgid "" +"Depending on the activity type, the :guilabel:`Schedule` button may be " +"replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` " +"button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 +msgid "" +"Scheduled activities are added to the chatter for the record under " +":guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57 +msgid "" +"Activities can also be scheduled from the kanban, list, or activities view " +"of an application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 +msgid "" +"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 " +"(clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill " +"out the pop-up form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 +msgid "List view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72 +msgid "" +"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 " +"(clock)` icon, then :guilabel:`Schedule An Activity`. If the record already " +"has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 " +"(phone)` or an :guilabel:`✉️ (envelope)` icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82 +msgid "" +"To open the activity view for an application, select the :guilabel:`🕘 " +"(clock)` icon from the menu bar anywhere in the database. Select any " +"application from the drop-down menu, and click the :guilabel:`🕘 (clock)` " +"icon for the desired app." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Activity menu drop down with focus on where to open activity view for CRM." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90 +msgid "" +"Select a record on which to schedule an activity. Move across the row to " +"find the desired activity type, then click the :guilabel:`＋ (plus sign)`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98 +msgid "" +"Activity colors, and their relation to an activity's due date, is consistent" +" throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 +msgid "" +"Activities that appear in **green** indicate a due date sometime in the " +"future." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 +msgid "**Yellow** indicates that the activity's due date is today." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 +msgid "" +"**Red** indicates that the activity is overdue and the due date has passed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 +msgid "" +"For example, if an activity is created for a phone call, and the due date " +"passes, the activity appears with a red phone in list view, and a red clock " +"on the kanban view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 +msgid "View scheduled activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 +msgid "" +"To view scheduled activities, open either the :menuselection:`Sales app` or " +":menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located " +"to the far-right side of the other view options." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114 +msgid "" +"Doing so opens the activities menu, showcasing all the scheduled activities " +"for the user, by default. To show all activities for every user, remove the " +":guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118 +msgid "" +"To view a consolidated list of activities separated by the application where" +" they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on" +" the header menu to see the activities for that specific application in a " +"drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122 +msgid "" +"The possibility to :guilabel:`Add new note` and :guilabel:`Request a " +"Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘" +" (clock)` icon on the header menu is clicked." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of CRM leads page emphasizing the activities menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 +msgid "Configure activity types" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 +msgid "" +"To configure the types of activities in the database, go to " +":menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of the settings page emphasizing the menu activity types." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 +msgid "" +"To edit an existing activity type, select it from the list, then click " +":guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 +msgid "" +"At the top of a blank activity type form, start by choosing a " +":guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157 +msgid "" +"The *Action* field specifies the intent of the activity. Some actions " +"trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160 +msgid "" +"If :guilabel:`Upload Document` is selected, a link to upload a document is " +"added directly to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162 +msgid "" +"If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users " +"have the option to open their calendar to schedule a time for this activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 +msgid "" +"If :guilabel:`Request Signature` is selected, a link is added to the planned" +" activity in the chatter that opens a signature request pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 +msgid "" +"The actions available to select on an activity type vary, depending on the " +"applications currently installed in the database." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 +msgid "Default user" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174 +msgid "" +"To automatically assign this activity to a specific user when this activity " +"type is scheduled, choose a name from the :guilabel:`Default User` drop-down" +" menu. If this field is left blank, the activity is assigned to the user who" +" creates the activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181 +msgid "" +"To include notes whenever this activity type is created, enter them into the" +" :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192 +msgid "" +"To automatically suggest, or trigger, a new activity after an activity has " +"been marked complete, the :guilabel:`Chaining Type` must be set." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198 +msgid "" +"In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next " +"Activity`. Upon doing so, the field underneath changes to: " +":guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to " +"select any activities to recommend as follow-up tasks to this activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230 +msgid "" +"In the :guilabel:`Schedule` field, choose a default deadline for these " +"activities. To do so, configure a desired number of :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur " +":guilabel:`after completion date` or :guilabel:`after previous activity " +"deadline`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 +msgid "" +"This :guilabel:`Schedule` field information can be altered before the " +"activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "Schedule activity popup with emphasis on recommended activities." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 +msgid "" +"If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest " +"Next Activity`, and has activities listed in the :guilabel:`Suggest` field, " +"users are presented with recommendations for activities as next steps." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 +msgid "" +"Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` " +"immediately launches the next activity once the previous one is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226 +msgid "" +"If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining " +"Type` field, the field beneath changes to: :guilabel:`Trigger`. From the " +":guilabel:`Trigger` field drop-down menu, select the activity that should be" +" launched once this activity is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"Schedule new activity popup with emphasis on Done and launch next button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244 +msgid "" +"When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger" +" Next Activity`, marking the activity as `Done` immediately launches the " +"next activity listed in the :guilabel:`Trigger` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249 +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:113 +msgid ":doc:`get_started`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 +msgid ":doc:`team_communication`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 +msgid "Use channels for team communication" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:5 +msgid "" +"Use channels in the Odoo *Discuss* app to organize discussions between " +"individual teams, departments, projects, or any other group that requires " +"regular communication. With channels, employees can communicate inside " +"dedicated spaces within the Odoo database around specific topics, updates, " +"and latest developments having to do with the organization." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:11 +msgid "Public and private channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:13 +msgid "" +"A *Public* channel can be seen by everyone, while a *Private* one is only " +"visible to users invited to it. To create a new channel, navigate to the " +":menuselection:`Discuss` app, and then click on the :guilabel:`➕ (plus)` " +"icon next to the :guilabel:`Channels` heading in the left-side menu. After " +"typing the name of the channel, two selectable options will appear: The " +"first is a channel with a hashtag (`#`) to indicate that it is a public " +"channel; the second option is a channel with a lock icon (`🔒`) next to it, " +"to indicate that it is a private channel. Select the channel type that best " +"fits the communication needs." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of discuss's sidebar and a channel being created in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:26 +msgid "" +"A public channel is best used when many employees need to access information" +" (such as company announcements), whereas a private channel could be used " +"whenever information should be limited to specific groups (such as a " +"specific department)." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:31 +msgid "Configuration options" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:33 +msgid "" +"The channel's :guilabel:`Group Name`, :guilabel:`Description`, and " +":guilabel:`Privacy` settings can be modified by clicking on the channel's " +"settings, represented by a :guilabel:`⚙️ (gear)` icon in the left sidebar " +"menu, next to the channel's name." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel's settings form in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:42 +msgid "Privacy and Members tabs" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:44 +msgid "" +"Changing :guilabel:`Who can follow the group's activities?` controls which " +"groups can have access to the channel." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:48 +msgid "" +"Allowing :guilabel:`Everyone` to follow a private channel lets other users " +"view and join it, as they would a public one." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:51 +msgid "" +"When choosing :guilabel:`Invited people only`, specify in the " +":guilabel:`Members` tab which members should be invited. Inviting members " +"can also be done from the *Discuss* app's main dashboard, by selecting the " +"channel, clicking the *add user* icon in the top-right corner of the " +"dashboard, and finally clicking :guilabel:`Invite to Channel` once all the " +"users have been added." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of Discuss' option to invite members in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:60 +msgid "" +"When the :guilabel:`Selected group of users` option is selected, it reveals " +"the ability to add an :guilabel:`Authorized Group`, along with the options " +"to :guilabel:`Auto Subscribe Groups` and :guilabel:`Auto Subscribe " +"Departments`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:64 +msgid "" +"The option to :guilabel:`Auto Subscribe Groups` automatically adds users of " +"that particular user group as followers. In other words, while " +":guilabel:`Authorized Groups` limits which users can access the channel, " +":guilabel:`Auto Subscribe Groups` automatically adds users as members as " +"long as they are part of a specific user group. The same is true for " +":guilabel:`Auto Subscribe Departments`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:70 +msgid "Quick search bar" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:72 +msgid "" +"Once at least 20 channels, direct messages, or live chat conversations (if " +"*Live Chat* module is installed on the database) are pinned in the sidebar, " +"a :guilabel:`Quick search…` bar is displayed. This feature is a convenient " +"way to filter conversations and quickly find relevant communications." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of the Discuss' sidebar emphasizing the quick search bar in Odoo " +"Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:81 +msgid "Finding channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:83 +msgid "" +"Click on the settings :guilabel:`⚙️ (gear)` icon, located in the left " +"sidebar, to the right of the :guilabel:`CHANNELS` collapsible menu item. " +"Doing so will lead to a mosaic view containing all the public channels " +"available. Users can join or leave channels on this screen by clicking the " +":guilabel:`JOIN` or :guilabel:`LEAVE` buttons that appear in the channel " +"boxes." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:88 +msgid "" +"There is also the ability to apply filtering criteria and save them for " +"later use. The :guilabel:`Search...` function accepts wildcards by using the" +" underscore character [ `_` ], and specific searches can be saved by using " +"the :menuselection:`Favorites --> Save Current Search` drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel being searched through filters in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:98 +msgid "Linking channel in chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:100 +msgid "" +"Channels can be linked in the chatter (log note) of a record in Odoo. To do " +"so, simply type: `#` and the channel name. Click or press enter on the " +"*channel* name. Upon logging the note a link to the channel will appear. " +"After clicking on the link a chat window with the channel conversation will " +"pop up in the lower right corner of the screen." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:105 +msgid "" +"Users are able to contribute to this group channel (either public or member " +"based) by typing messages in window and pressing *enter*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"Channel linked in chatter with the channel open on the lower right quadrant." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:114 +msgid ":doc:`plan_activities`" +msgstr "" + +#: ../../content/applications/productivity/iot.rst:8 +msgid "Internet of Things (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot.rst:17 +msgid "" +"The Open Platform Communications (OPC) Unified Architecture (UA) protocol is" +" now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open" +" Platform Communications)` :abbr:`UA (United Architecture)` is an open " +"standard that specifies information exchange for industrial communication on" +" devices, between machines and between systems. This includes communication " +"between information technology and operational technology. :abbr:`OPC (Open " +"Platform Communications)` :abbr:`UA (United Architecture)` can be used with " +"any software platform, on a wide variety of devices, and deployed securely. " +"The :abbr:`IoT (Internet of Things)` box has entered the world of the " +"Industry 4.0 standard and can be utilized in a wide variety of industries, " +"and for things like building automation, packaging, utilities, etc." +msgstr "" + +#: ../../content/applications/productivity/iot/config.rst:5 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:3 +msgid "Connect an IoT box to Odoo" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:5 +msgid "" +"An Internet of Things (IoT) box is a micro-computer device that allows for " +"the connection of input and output devices to an Odoo database. An " +":abbr:`IoT (Internet of Things)` box subscription is required in order to " +"use the :abbr:`IoT (Internet of Things)` box with a secured connection. A " +"computer is also required to set up the :abbr:`IoT (Internet of Things)` " +"box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:13 +msgid "" +"Begin the :abbr:`IoT (Internet of Things)` configuration process by " +":ref:`installing the IoT app ` on the Odoo database through" +" the :menuselection:`Apps` application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The Internet of Things (IoT) app on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:20 +msgid "" +"Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app " +"--> IoT Boxes`, and then click on the :guilabel:`Connect` button located in " +"the upper-left corner of the :menuselection:`IoT Boxes` dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connecting an IoT box to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:28 +msgid "" +"There are two recommended ways to connect the :abbr:`IoT (Internet of " +"Things)` box to the database once the *IoT app* is installed. Follow the " +"steps in either of the next two sections to connect the :abbr:`IoT (Internet" +" of Things)` box via :ref:`wired ethernet connection `" +" or via :ref:`WiFi `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connection steps for a wired connection or WiFi connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:38 +msgid "" +"The disk image that the :abbr:`IoT (Internet of Things)` box SD card is " +"formatted with is unique to the version of the Odoo database that the " +":abbr:`IoT (Internet of Things)` box is running on. Ensure that the " +":abbr:`IoT (Internet of Things)` box is :doc:`flashed ` with " +"the most up-to-date disk image." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:46 +msgid "Ethernet connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:48 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via an ethernet cable to the Odoo database (by way of the ethernet " +"port; RJ-45)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:51 +msgid "" +"First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box" +" (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, " +"an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of " +"Things)` box into a power source." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:55 +msgid "" +"Immediately after the unit powers on and boots up, read the *pairing code* " +"from the screen or from the printout of a receipt printer connected to the " +":abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:59 +msgid "" +"By default, the :abbr:`IoT (Internet of Things)` box will display the " +"*pairing code* for a maximum of 5 minutes after the unit boots up. After 5 " +"minutes, the *pairing code* will disappear for security purposes and the " +":abbr:`IoT (Internet of Things)` box will need to be rebooted manually by " +"unplugging the unit from the power source for ten seconds and re-plugging it" +" back in." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:65 +msgid "" +"If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then " +"the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)`" +" box homepage by clicking on the :guilabel:`POS Display` button. For " +"instructions on how to access the :abbr:`IoT (Internet of Things)` box " +"homepage visit :ref:`iot_connect/token`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:70 +msgid "" +"On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and " +"then click on the :guilabel:`Connect` button located in the upper-left " +"corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing " +"code* in the :guilabel:`Pairing Code` field and click on the " +":guilabel:`Pair` button. The database will now link to the :abbr:`IoT " +"(Internet of Things)` box and it will appear on the :menuselection:`IoT " +"Boxes` page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:81 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via a WiFi connection to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:84 +msgid "" +"First, ensure there is no ethernet cable plugged into the :abbr:`IoT " +"(Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT" +" (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, " +"etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:88 +msgid "" +"After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box " +"into to a power source. On the computer, navigate to :menuselection:`IoT app" +" --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in" +" the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then" +" copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as " +"this will later be used to link the Odoo database to the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:94 +msgid "" +"Back on the computer, navigate to the available WiFi networks and connect to" +" the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network " +"dispersed by the :abbr:`IoT (Internet of Things)` box will start with " +"`IoTBox-xxxxxxxxxx`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:102 +msgid "" +"Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser " +"will automatically redirect to the :menuselection:`Configure Iot Box` " +"wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the " +"previously copied *token* into the :guilabel:`Server Token` field, and then " +"click on :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:112 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't " +"start, then see the documentation on :ref:`connecting with a token " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:115 +msgid "" +"Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box " +"will connect with (enter the password if there is one) and click on " +":guilabel:`Connect`. Wait a few seconds and the browser will redirect to the" +" :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be " +"manually re-connected back to the original WiFi connection, if this does not" +" happen automatically." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:124 +msgid "" +"After completing each step, the :abbr:`IoT (Internet of Things)` box should " +"appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo" +" database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:132 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted " +"upon successfully connecting via WiFi for the box to appear in the *IoT app*" +" on the Odoo database. To do so, simply unplug the device and plug it back " +"into the power source after ten seconds." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:141 +msgid "" +"A manual connection of the :abbr:`IoT (Internet of Things)` box to the " +":abbr:`IoT (Internet of Things)` app can be made using the *token*, from a " +"computer. The *token* can be found by navigating to :menuselection:`IoT app " +"--> IoT Boxes` and clicking on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:145 +msgid "" +"Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an " +"IoT Box` page that appears, click :guilabel:`Copy` to the right of the " +":guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet " +"of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:149 +msgid "" +"Access the :abbr:`IoT (Internet of Things)` box homepage by entering the " +":abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of " +"Things)` box into a browser window from a computer on the same network as " +"the :abbr:`IoT (Internet of Things)` box (preferably by ethernet " +"connection)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:154 +msgid "" +"The :abbr:`IP (Internet Protocol)` address can be accessed by the router " +"admin console that the :abbr:`IoT (Internet of Things)` box is connected to," +" or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` " +"box. A receipt will print out with the :abbr:`IoT (Internet of Things)` " +"box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:159 +msgid "" +"On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* " +"under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. " +"Then, paste the *token* into the :guilabel:`Server Token` field and click " +":guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link" +" to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 +msgid "Flashing the SD card" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 +msgid "" +"In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD " +"Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT " +"(Internet of Things)` image update. This means that the Odoo :abbr:`IoT " +"(Internet of Things)` box software may need to be updated." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 +msgid "" +"Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to " +":menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP " +"address` of the :abbr:`IoT (Internet of Things)` box. Then click on " +":guilabel:`Update` (next to the version number)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 +msgid "" +"If a new version of the :abbr:`IoT (Internet of Things)` Box image is " +"available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the " +"bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT" +" (Internet of Things)` box will then flash itself to the new version. All of" +" the previous configurations will be saved." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 +msgid "" +"This process can take more than 30 minutes. Do not turn off or unplug the " +":abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent" +" state. This means that the :abbr:`IoT (Internet of Things)` box will need " +"to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "IoT box software upgrade in the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 +msgid "" +"A computer with a micro SD card reader/adapter is required in order to re-" +"flash the micro SD card." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 +msgid "" +"Navigate to Balena's website and download `Etcher " +"`_. It's a free and open-source utility used for " +"burning image files onto drives. Click to `download " +"`_. Install and launch the " +"program on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 +msgid "" +"Then download the version-specific :abbr:`IoT (Internet of Things)` image " +"from `nightly `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 +msgid "" +"The following are image versions on the `nightly " +"`_ website with their corresponding " +"Odoo database version:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 +msgid "" +"The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 +msgid "" +"After this step is complete, insert the :abbr:`IoT (Internet of Things)` " +"box's micro SD card into the computer or reader. Open *Etcher* and select " +":guilabel:`Flash from file`, then find and select the image just downloaded " +"and extracted. Next, select the drive the image should be burned to. Lastly," +" click on :guilabel:`Flash` and wait for the process to finish." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 +msgid "" +"An alternative software for flashing the micro SD card is *Raspberry Pi " +"Imager*. Download the *Raspberry Pi* software `here " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 +msgid "HTTPS certificate (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 +msgid "What is HTTPS?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 +msgid "" +"*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of " +"*Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to " +"send data back and forth between a web browser and a website. :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` is encrypted in order to increase the " +"security of data transfer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption " +"protocol to encrypt communications. The protocol is called *Transport Layer " +"Security* (TLS), although formerly it was known as *Secure Sockets Layer* " +"(SSL)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the " +"transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure " +"Sockets Layer)` certificates, which verify that a particular provider is who" +" they say they are." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 +msgid "" +"In this documentation and throughout Odoo the term \"HTTPS certificate\" " +"will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` " +"certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 +msgid "Why is it needed?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 +msgid "" +"In order to communicate with certain network devices (in particular for " +"payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` certificate isn't valid, some devices won't be able to interact " +"with the :abbr:`IoT (Internet of Things)` Box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 +msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 +msgid "" +"The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate is automatic." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 +msgid "" +"The :abbr:`IoT (Internet of Things)` Box will send a specific request to " +"``_ which will send back the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of " +"Things)` box and database are eligible." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 +msgid "Internet of Things (IoT) eligibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 +msgid "" +"The database should be a **production** instance. The database instance " +"should not be a copy, a duplicate, a staging, or a development environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 +msgid "The Odoo subscription must:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 +msgid "Have an :guilabel:`IoT Box Subscription` line." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 +msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 +msgid "" +"If the subscription is linked to a ``_ portal user " +"check the information on the portal subscription page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 +msgid "" +"In this case, both subscriptions are considered \"in progress\" as the " +":guilabel:`Filter By\\: In Progress` was used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 +msgid "" +"If the subscription is in question, contact the database's Account Manager " +"or Partner regarding the matter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 +msgid "" +"Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate " +"errors" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 +msgid "" +"If anything goes wrong during the process of the \"HTTPS certificate\" " +"generation or reception, a specific error will code be given on the " +":abbr:`IoT (Internet of Things)` box home page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 +msgid "" +"Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for " +"the presence of the \"HTTPS certificate\" and will attempt its generation if" +" it is missing. As such, if there is an error on the :abbr:`IoT (Internet of" +" Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home " +"page to see if the error disappears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 +msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:132 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:149 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:166 +msgid "Reason:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:87 +msgid "" +"The configuration regarding the server is missing. In other words, the Odoo " +"instance is not connected with the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:114 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:137 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:159 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 +msgid "Solution:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +msgid "Ensure that the server is configured." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 +#: ../../content/applications/productivity/iot/config/windows_iot.rst:99 +msgid ":doc:`/applications/productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 +msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 +msgid "" +"An unhandled error happened when trying to read the existing :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +msgid "" +"Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate file is readable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 +msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +msgid "" +"The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is " +"missing." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 +msgid "" +"Ensure that both values are configured as intended. To modify them, go to " +"the :abbr:`IoT (Internet of Things)` box home page, and navigate to " +":guilabel:`Credential`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 +msgid "" +"An unexpected error happened when the :abbr:`IoT (Internet of Things)` box " +"tried to reach ``_. The causes are likely due to the " +"network infrastructure/configuration:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 +msgid "" +"The :abbr:`IoT (Internet of Things)` box does not have access to internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 +msgid "" +"The network does not allow the :abbr:`IoT (Internet of Things)` box to " +"communicate with ``_. This may be due to network " +"devices preventing the communication (firewalls, etc.) or the network " +"configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 +msgid "" +"More information regarding the error that occurred can be found in the full " +"request exception details, which are in the :abbr:`IoT (Internet of Things)`" +" box logs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure and goes beyond Odoo " +"support's service scope." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:140 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:143 +msgid "" +"The IoT-box was able to reach ``_ but received an " +"unusual `HTTP response (status codes) `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:147 +msgid "" +"This error code will also give the HTTP response status codes. For example, " +"if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the" +" page returned a 404 error, which is the \"Page Not Found\" code." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:152 +msgid "" +"Check if ``_ is down using a web browser, as it's " +"possible that it is down due to maintenance." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:155 +msgid "" +"If ``_ is down due to maintenance, unfortunately there" +" is nothing that can be done but instead wait for it to recover." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:157 +msgid "" +"If ``_ is not down due to maintenance, open a `support" +" ticket `_ on the matter. Ensure that the 3 " +"digits status code next to the code error is included in the support ticket." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:162 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:165 +msgid "" +"The :abbr:`IoT (Internet of Things)` box was able to reach " +"``_ but it refused to deliver the :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:169 +msgid "" +"Ensure that the :abbr:`IoT (Internet of Things)` box and database are " +"eligible for a certificate: :ref:`Internet of Things (IoT) eligibility " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:173 +msgid "How to ensure that the HTTPS certificate is correct" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:175 +msgid "" +"If the certificate has been applied successfully, a new :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)`" +" for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` " +"will appear on the Odoo database, inside of the :menuselection:`IoT` " +"application on that specific device's form." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:184 +msgid "" +"When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a" +" secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will " +"be established." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 +msgid "Example of valid SSL certificate details on the browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 +msgid "" +"Padlock in Chrome on Windows 10 attesting the fact that the connection is " +"secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:194 +msgid "" +"The IoT-box homepage will now display an `OK` status next to `HTTPS " +"certificate`. The drop-down menu icon, when clicked, will reveal information" +" regarding the certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "IoT box homepage with HTTPS certificate OK status." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:202 +msgid "Domain Name System (DNS) issue" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:204 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box can be accessed from its " +":abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: " +"`.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely " +"running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it " +"will give an error code mentioning :abbr:`DNS (Domain Name System)` (like " +"`DNS_PROBE_FINISHED_NXDOMAIN`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:209 +msgid "" +"These :abbr:`DNS (Domain Name System)` issues may appear as the following in" +" different browsers:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:213 +msgid "Chrome" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:219 +msgid "DNS issue on Chrome browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:222 +msgid "Firefox" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:228 +msgid "DNS issue on Firefox browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:230 +msgid "Edge" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:236 +msgid "DNS issue on Edge browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:240 +msgid "Domain Name System (DNS) issue solution" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:242 +msgid "" +"Should the router allow the :abbr:`DNS (Domain Name System)` to be manually " +"changed, change the DNS to use `Google DNS " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:244 +msgid "" +"If your router doesn't allow for this, then a change will need to be made on" +" the :abbr:`DNS (Domain Name System)` settings of each of the devices using " +"`Google DNS `_. This will " +"need to occur on **every** device that plans to interact with the :abbr:`IoT" +" (Internet of Things)` box (e.g. computer, tablet or phone). The individual " +"device configuration processes can be found on the website of the device's " +"manufacturer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:252 +msgid "" +"Other :abbr:`IoT (Internet of Things)` devices such as payment terminals " +"likely won't need their :abbr:`DNS (Domain Name System)` settings changed as" +" they are already configured with custom :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:257 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure, and it goes beyond " +"Odoo support's service scope." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:3 +msgid "Use an IoT box with a PoS" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:6 +msgid "Prerequisites" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:11 +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:12 +msgid "" +"Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* " +"applications installed." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:13 +msgid "" +"A local network set up with :abbr:`DHCP (Dynamic Host Configuration " +"Protocol)` (this is the default setting)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:15 +msgid "" +"An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already " +"built in)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:16 +msgid "" +"Any of the supported hardware (receipt printer, barcode scanner, cash " +"drawer, payment terminal, scale, customer display, etc.). The list of " +"supported hardware can be found on the `POS Hardware page " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:21 +msgid "Setup" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:27 +msgid "" +"To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to" +" connect an :abbr:`IoT (Internet of Things)` box to the database. To do " +"this, follow these instructions: :doc:`Connect an Internet of Things (IoT) " +"box to the Odoo database `." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:31 +msgid "" +"Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)`" +" box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:37 +msgid "Device Name" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:38 +msgid "Instructions" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:39 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:40 +msgid "" +"Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` " +"port or to the network, and power it on. Refer to " +":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:43 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:391 +msgid "Cash drawer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:44 +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:45 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:359 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:46 +msgid "" +"In order for the barcode scanner to be compatible it must end barcodes with " +"an `ENTER` character (keycode 28). This is most likely the default " +"configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:48 +msgid "Scale" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:49 +msgid "" +"Connect the scale and power it on. Refer to " +":doc:`/applications/productivity/iot/devices/scale`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:51 +msgid "Customer display" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:52 +msgid "" +"Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the " +":abbr:`PoS (Point of Sale)` order. Refer to " +":doc:`/applications/productivity/iot/devices/screen`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:54 +msgid "Payment terminal" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:55 +msgid "" +"The connection process depends on the terminal. Refer to the :doc:`payment " +"terminals documentation " +"`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:58 +msgid "" +"Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to " +"the :menuselection:`PoS` application. To do this, go to " +":menuselection:`Point of Sale --> Configuration --> PoS`, tick the " +":guilabel:`IoT Box` option, and select the devices to be used in this " +":abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst-1 +msgid "Configuring the connected devices in the POS application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:67 +msgid "" +"Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be " +"launched." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 +#: ../../content/applications/productivity/iot/config/windows_iot.rst:105 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 +msgid "IoT box connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 +msgid "Unable to locate the pairing code to connect the IoT box" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 +msgid "" +"The pairing code should be printed on receipt printers connected to the " +":abbr:`IoT (Internet of Things)` box and should also be displayed on " +"connected monitors." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 +msgid "The pairing code doesn't show under the following circumstances:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo " +"database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 +msgid "" +"The code is only valid for 5 minutes after the :abbr:`IoT (Internet of " +"Things)` box has started. It's automatically removed from connected displays" +" when this time has expired." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 +msgid "" +"The version of the :abbr:`IoT (Internet of Things)` box image is too old. If" +" the :abbr:`IoT (Internet of Things)` box image is from an earlier version, " +"then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be" +" re-flashed to update the image (see :doc:`Flashing the SD Card " +"`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 +msgid "" +"If none of the cases listed above correct the issue, then make sure that the" +" :abbr:`IoT (Internet of Things)` box has correctly started, by checking " +"that a fixed green LED is showing next to the power port." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it's not showing in the database" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 +msgid "" +"When an :abbr:`IoT (Internet of Things)` box connects to a database, it may " +"restart. If so, it can take up to five minutes before appearing in the " +"database. If the :abbr:`IoT (Internet of Things)` box is still not showing " +"after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box " +"can reach the database and that the server doesn't use a multi-database " +"environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 +msgid "" +"To access the database from the :abbr:`IoT (Internet of Things)` box, open a" +" browser and type in the database address." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 +msgid "" +"Make sure that the :abbr:`IoT (Internet of Things)` box and the computer " +"running the browser are located on the same network, as the :abbr:`IoT " +"(Internet of Things)` box cannot be reached from outside the local network." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate doesn't generate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 +msgid "" +"In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate, an IoT box subscription is required for the :abbr:`IoT " +"(Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` " +"box prior to configuring an :abbr:`IoT (Internet of Things)` subscription " +"for the database and :abbr:`IoT (Internet of Things)` box with the Account " +"Manager will result in an unsecured connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 +msgid "" +"In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating correctly. In this " +"case, deactivate the firewall until the certificate is successfully " +"generated. It should also be noted that certain devices, such as a router " +"that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) `" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 +msgid "" +"If a printer doesn't show up in the devices list, go to the :abbr:`IoT " +"(Internet of Things)` box homepage and make sure that it is listed under " +":guilabel:`Printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 +msgid "" +"If the printer is not present on the :abbr:`IoT (Internet of Things)` box " +"homepage, click :guilabel:`Printers Server`, go to the " +":guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the " +"printer is not present in the list, it's likely not connected properly." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 +msgid "" +"For most printers, the correct driver should be automatically detected and " +"selected. However, in some cases, the automatic detection mechanism might " +"not be enough, and if no driver is found, the printer might print random " +"characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 +msgid "" +"The solution is to manually select the corresponding driver. On the " +":abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers " +"Server`, go to the :guilabel:`Printers` tab and select the printer in the " +"list. In the :guilabel:`Administration` dropdown, click on :guilabel:`Modify" +" Printer`. Follow the steps and select the *make* and *model* corresponding " +"to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 +msgid "" +"Epson and Star receipt printers and Zebra label printers do not need a " +"driver to work. Make sure that no driver is selected for those printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 +msgid "Epson configuration special case" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 +msgid "" +"Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of " +"Sale)` using the `GS v 0` command. However, the following Epson printer " +"models do not support this command:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 +msgid "TM-U220" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 +msgid "TM-U230" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 +msgid "TM-P60" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 +msgid "TMP-P60II" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:113 +msgid "" +"Bypass this issue by configuring the printer to use the `ESC *` command " +"instead." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:116 +msgid "Process to force ESC * command" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:119 +msgid "Epson printer compatibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 +msgid "" +"The first step is to check whether the printer is incompatible with `GS v 0`" +" command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:125 +msgid "" +"`Epson GS v 0 documentation `_ for `GS v 0` " +"compatible printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 +msgid "" +"`Epson ESC * documentation `_ for `ESC *` " +"compatible printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:130 +msgid "" +"If the printer is not compatible with the `ESC *` command then the following" +" process is not possible. Should the printer be compatible to use the `ESC " +"*` command to print, follow this process to configure the printer with the " +":abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 +msgid "IoT box configuration for ESC *" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:137 +msgid "" +"To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` " +"command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by" +" navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the " +":guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of " +"Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:142 +msgid "**Choosing the printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:144 +msgid "" +"Now click on the :guilabel:`Printers server` button. This will redirect the " +"browser to the *CUPS* page. Next, go to :menuselection:`Administration --> " +"Printers --> Add Printer`, choose the printer that should be modified, and " +"then click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "" +"If the name of the printer is still uncertain, take the following steps:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:151 +msgid "Take note of the listed printers on the *CUPS* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "Turn the printer off and refresh the page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:153 +msgid "" +"Now compare the difference with the first list to see which printer " +"disappeared." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "Turn the printer back on and refresh the page again." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:155 +msgid "Double-check the list again to see if the printer re-appears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:156 +msgid "" +"The printer that disappeared and reappears again on the listed printers is " +"the name of the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:160 +msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:162 +msgid "**CUPS naming convention**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:164 +msgid "" +"`CUPS` will prompt the admin for three pieces of information: the " +":guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The " +"last two pieces of information do not need to be specific, however, the " +":guilabel:`Name` should follow a particular convention to work with the `ESC" +" *` command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:169 +msgid "" +"The :guilabel:`Name` should match this convention: " +"`__IMC___...___`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:172 +msgid "A breakdown of the naming convention:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:174 +msgid "" +"`printer_name`: This is the printer name. It can be any character as long as" +" it does not contain `_`, `/`, `#`, or ` ` (space character)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:176 +msgid "" +"`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC " +"*`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 +msgid "`param_1`: This stands for the specific parameter:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:179 +msgid "" +"`SCALE`: Scale of the picture (with the same aspect ratio). `X` should be" +" an integer describing the scale percentage that should be used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:183 +msgid "" +"`100` is the original size, `50` is half the size, `200` is twice the size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:185 +msgid "" +"`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not" +" specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:186 +msgid "" +"`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if" +" not specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:189 +msgid "" +"*Density* parameters might need to be configured in a particular way " +"depending on the printer model." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:193 +msgid "" +"Visit `Epson's ESC * documentation `_ and click on the " +"printer model printer in the table above to see if the printer should set " +"these parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:198 +msgid "The following are examples of proper and improper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:200 +msgid "Proper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:202 +msgid "`EPSONTMm30II__IMC__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 +msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:205 +msgid "" +"Improper name formatting (this will not prevent printing, but the result " +"might not have the expected printed output):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:208 +msgid "`EPSON TMm 30II` -> The name can't have spaces." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 +msgid "" +"`EPSONTMm30II` -> The name itself is correct, but it won't use `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:210 +msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 +msgid "" +"`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing" +" parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:212 +msgid "" +"`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale " +"value." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:214 +msgid "**Finish adding a printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:216 +msgid "" +"After setting the name of the printer with the appropriate naming " +"convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value" +" to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to " +":guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:220 +msgid "" +"After completing these steps, click :guilabel:`Add Printer`. If everything " +"was done correctly, the page should redirect to the *Banners* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:223 +msgid "" +"At this point the printer should have been created, now the :abbr:`IoT " +"(Internet of Things)` box just needs to detect it and then sync to Odoo's " +"server (this could take a few minutes)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:226 +msgid "**Adding the printer to Odoo PoS**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:228 +msgid "" +"Once the printer is visible on the Odoo database, don't forget to choose it " +"in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet " +"of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> " +"Connected Devices --> IoT Box --> Receipt Printer --> Save`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:234 +msgid "" +"If the printer was set up incorrectly (it is still printing random text or " +"the printed receipt is too big or small), then it cannot be modified via the" +" printer name with *CUPS*. Instead, the above process can be repeated to set" +" up another printer from scratch to create one with modified parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:239 +msgid "**Example setup of the Epson TM-U220B printer using ESC**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:244 +msgid "" +"The following is an example of the troubleshooting process for a TM-U220B " +"printer model using the `ESC *` command. The receipt pictured below is an " +"example of a receipt that is printing correctly due to proper formatting (in" +" theory):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Properly formatted receipt picture from a demo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:252 +msgid "" +"Trying to print this receipt right-away prior to the proper formatting will " +"not work as the TM-U220B printer model does not support `GS v 0`. Instead " +"random characters will print:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Printer paper with seemingly random characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:259 +msgid "" +"To properly configure formatting for the Epson TM-U220B printer model take " +"the following steps." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:261 +msgid "" +"After consulting Epson's website for compatibility for both of the commands:" +" `GS v 0 `_ and `ESC * " +"`_, it can be seen that " +"indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with " +"`ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson compatibility evaluation from Epson website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:270 +msgid "" +"When adding the printer, *CUPS* will ask which printer should be added:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Administration menu, add printer selection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:276 +msgid "" +"In this case, the printer is connected via :abbr:`USB (Universal Serial " +"Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. " +"Instead it is likely part of the :guilabel:`Unknown` selection under " +":guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB " +"(Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box " +"and refreshing the page, the :guilabel:`Unknown` printer disappears. By " +"plugging it back in, the printer reappears, so it can be said that this is " +"the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:283 +msgid "" +"For the naming convention, since it will need to print using the `ESC *` " +"command, it is imperative to add `__IMC`. Reference the printer model on " +"`Epson's ESC * site `_ to find out more about" +" the *density* parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturer's website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:292 +msgid "" +"For this particular model, TM-U220, `m` should be equal to 0 or 1. While " +"referencing the :guilabel:`Description` below the pink box in the above " +"picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, " +"the `m` value can NOT be 32 or 33 (otherwise there will be random characters" +" printed)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:297 +msgid "" +"The table includes the numeric values: 32 and 33, they both occur if the " +":guilabel:`Number of bits for vertical data` is set to 24. This means that " +"is a *High Vertical Density*. In the case of configuring the Epson TM-U220, " +"the *Low Vertical Density* will need to be forced, as this printer model " +"does not support *High Vertical Density* for this command `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:302 +msgid "" +"To add a *Low Vertical Density*, add the `LDV` parameter to the naming " +"convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:308 +msgid "" +"Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value " +"to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to " +":guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturers website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:315 +msgid "" +"However when trying to print with the naming convention: " +"`EpsonTMU220B__IMC_LDV__`, it will print the receipt, but it will be too big" +" and outside the margin. To resolve this, add a new printer (and naming " +"convention) with the `SCALE` parameter to adapt to our receipt size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:319 +msgid "Here are some examples:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:324 +msgid "Printer Naming Convention" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:325 +msgid "`EpsonTMU220B__IMC_LDV__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:326 +msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:327 +msgid "`EpsonTMU220B__IMC_LDV_LDH__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:328 +msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt example format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:346 +msgid "The Zebra printer doesn't print anything" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:348 +msgid "" +"Zebra printers are quite sensitive to the format of the Zebra Programming " +"Language (ZPL) code that is printed. If nothing comes out of the printer or " +"blank labels are printed, try changing the format of the report that is sent" +" to the printer by accessing :menuselection:`Settings --> Technical --> User" +" Interface --> Views` in :ref:`developer mode ` and look for" +" the corresponding template." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:355 +msgid "" +"Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming " +"Language)` files `here `_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:362 +msgid "The characters read by the barcode scanner don't match the barcode" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:364 +msgid "" +"By default, most barcode scanners are configured in the US QWERTY format. If" +" the barcode scanner uses a different layout, go to the form view of the " +"device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select " +"the correct format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:369 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:371 +msgid "" +"Make sure that the correct device is selected in the :menuselection:`Point " +"of Sale` configuration and that the barcode is configured to send an `ENTER`" +" character (keycode 28) at the end of every barcode. To do so, navigate to " +":menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> " +"Edit`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:377 +msgid "The barcode scanner is detected as a keyboard" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:380 +msgid "" +"Some barcode scanners do not advertise themselves as barcode scanners but as" +" a USB keyboard instead, and will not be recognized by the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:383 +msgid "" +"The device type can be manually changed by going to its form view " +"(:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the" +" :guilabel:`Is scanner` option." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Modifying the form view of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:394 +msgid "The cash drawer does not open" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:396 +msgid "" +"The cash drawer should be connected to the printer and the :guilabel:`Cash " +"drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` " +"configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu " +"on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer " +"checkbox`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:3 +msgid "Connect Windows IoT Odoo" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:5 +msgid "" +"A Virtual IoT box is a computer program that needs to be downloaded and " +"installed on a Windows computer. This requires a Windows operating system " +"with an Odoo 16 or later database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:8 +msgid "" +"The Windows virtual :abbr:`IoT (Internet of Things)` box works the same way " +"as a physical :abbr:`IoT (Internet of Things)` box, with the ability to run " +"most of the same devices. All :abbr:`POS (Point of Sale)` devices work with " +"it, such as a scale or printer. Payment terminals will also work, but it " +"should be noted that :abbr:`MRP (Material Requirement Planning)` devices are" +" not compatible. *These include cameras or measurement tools.*" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:15 +msgid "Pre-requisites" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:17 +msgid "" +"The following items will be needed to complete the Windows :abbr:`IoT " +"(Internet of Things)` installation." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:20 +msgid "Odoo 16 database or any version above." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:21 +msgid "" +":abbr:`IoT (Internet of Things)` compatible devices (except those mentioned " +"above). Refer to: `Odoo's compatible IoT devices " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:23 +msgid "Device drivers for Windows." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:26 +msgid "" +"Odoo recommends using an updated, recent version of Windows (Windows 10/11) " +"as some older operating systems can cause the Windows virtual :abbr:`IoT " +"(Internet of Things)` to not work." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:29 +msgid "Windows computer (laptop, desktop, or server)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:30 +msgid "" +"Odoo :abbr:`IoT (Internet of Things)` subscription. Refer to: :ref:`iot/iot-" +"eligibility`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:33 +msgid "Connect the Windows virtual Iot box to an Odoo database" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:35 +msgid "" +"The Windows virtual IoT box is simple to setup in just a few easy steps. " +"Follow this process when installing the Windows virtual IoT software for the" +" first time." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:39 +msgid "Download and initial installation" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:41 +msgid "" +"To begin the installation, navigate to the Odoo 16 or higher installation " +"package for Enterprise or Community - Windows edition at `Odoo's download " +"page `_. Next, install and setup the Odoo " +":file:`.exe` file. After the instructions screen, click :guilabel:`Next` to " +"start the installation and agree to the :abbr:`TOS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:46 +msgid "" +"During the next step of the installation, select :guilabel:`Odoo IoT` from " +"the :guilabel:`Select the type of install` dropdown." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:50 +msgid "For reference, the following should be installed:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:52 +msgid "**Odoo server**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:53 +msgid "**Odoo IoT**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:54 +msgid "**Nginx WebServer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:55 +msgid "**Ghostscript interpreter**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:57 +msgid "" +"Ensure there is enough space on the computer for the installation and click " +":guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:60 +msgid "Setting the destination and completing the installation" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:62 +msgid "" +"To complete the installation, select the :guilabel:`Destination Folder` and " +"click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:66 +msgid "" +"Choosing ``C:\\odoo`` as the install location will allow for the Nginx " +"server to start. If the folder doesn't exist, then create it. Otherwise the " +"installation files will be spread throughout the hard drive." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:71 +msgid "" +"Odoo's Windows virtual IoT software shouldn't be installed inside any of the" +" Window's User's directories. Doing so won't allow for Nginx to initialize." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:74 +msgid "" +"The installation may take a few minutes. When complete, click " +":guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:76 +msgid "" +"Ensure that the :guilabel:`Start Odoo` box is checked and click " +":guilabel:`Finish`. After installation, the Odoo server will run and " +"automatically open `http://localhost:8069` on your web browser. The webpage " +"should display the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:81 +msgid "" +"A restart of the Windows IoT program may be necessary should the web browser" +" not display anything. :ref:`iot/restart_windows_iot`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:85 +msgid "Connecting devices" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:87 +msgid "" +"Next, connect the :abbr:`IoT (Internet of Things)` devices to the Windows " +"computer. Windows should automatically detect the device because the driver " +"is pre-installed on the computer. If not, search for and install the Windows" +" driver for the device." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:91 +msgid "" +"Following connecting devices to the computer, refresh the :abbr:`IoT " +"(Internet of Things)` box homepage and verify the device is seen. If not, " +"reload the handlers through the :abbr:`IoT (Internet of Things)` box " +"homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:95 +msgid "" +"Finally, connect Windows :abbr:`IoT (Internet of Things)` to a database " +"using existing instructions (manually using the Token)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:101 +msgid "" +"Now the installation is complete, the devices connected to :abbr:`IoT " +"(Internet of Things)` can be used to complete processes/actions." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:110 +msgid "Restart Windows IoT box" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:112 +msgid "" +"In some instances a manual restart of the physical :abbr:`IoT (Internet of " +"Things)` box can resolve the issue of an :abbr:`IoT (Internet of Things)` " +"box not showing up on the database. For the Windows virtual :abbr:`IoT " +"(Internet of Things)` box a manual restart of the Odoo server can resolve " +"database connection issues." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:117 +msgid "To restart the virtual Windows IoT server:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:119 +msgid "Type `Services` into the Windows :guilabel:`Search Bar`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:120 +msgid "" +"Select the :menuselection:`Services` App and scroll down to the " +":guilabel:`Odoo` service." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:121 +msgid "" +"Right click on :guilabel:`Odoo` and select :guilabel:`Start` or " +":guilabel:`Restart`. This action will manually restart the Odoo IoT server." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:125 +msgid "Firewalls" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:127 +msgid "" +"Firewalls keep devices safe and secure. Sometimes they can block connections" +" that should be made though. The Windows virtual :abbr:`IoT (Internet of " +"Things)` box software may not be reachable to the :abbr:`LAN (Local Area " +"Network)` due to a firewall preventing the connection. Consult your local IT" +" support team to make exceptions (network discovery) in the :abbr:`OS " +"(Operating System)` or firewall program. Windows has their own firewall as " +"do other virus protection programs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:134 +msgid "" +"A client might encounter a time when they are able to reach the homepage of " +"the :abbr:`IoT (Internet of Things)` box, yet they cannot access it from " +"another computer/mobile device/tablet on the same network." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:139 +msgid "Making an exception on Windows Defender" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:141 +msgid "" +"It's possible to allow other devices to access the Windows virtual " +":abbr:`IoT (Internet of Things)` box while keeping the firewall on. This is " +"done by creating a rule on *Windows Defender* and allowing communication " +"through port `8069`. The following process describes the steps to take in " +"order to make this exception." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:147 +msgid "Create a rule in Windows Defender" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:149 +msgid "" +"First, open the *Windows Firewall* by navigating to the " +":menuselection:`Start Menu` and typing in `Firewall`. Then, open the " +":menuselection:`Windows Defender Firewall` program. In the left-hand menu, " +"navigate to :guilabel:`Advanced Settings`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:153 +msgid "" +"Once :guilabel:`Advanced Settings` have been selected, click " +":guilabel:`Inbound Rules` in the left-hand menu. Then, in the right-hand " +"menu column (under :guilabel:`Inbound Rules`), click on :guilabel:`New Rule`" +" to create a new rule." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:158 +msgid "Configure new rule" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:160 +msgid "" +"On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then " +"click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page " +"leave the rule application to :guilabel:`TCP`. Then, select " +":guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the " +"text box, type in `8069`. Finally click :guilabel:`Next` to continue to the " +"next step." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:165 +msgid "" +"On the :menuselection:`Actions` page, select :guilabel:`Allow the " +"connection` and click :guilabel:`Next`. The following page on the " +":menuselection:`Rule Configuration` wizard is the :guilabel:`Profile` page. " +"On this page, select whichever connection type applies to the network the " +"Windows machine is operating on. Ideally, select :guilabel:`Private` only " +"connections. The *Private* connection type is the most secure connection " +"while allowing the selected port to communicate. Click :guilabel:`Next` to " +"continue." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:172 +msgid "" +"Finally, assign a new, unique name to the rule. For example, this name can " +"be `Odoo`. Optionally, add a brief description in the " +":guilabel:`Description` field. Click :guilabel:`Finish` to complete the " +":guilabel:`Rule Configuration` wizard. Now, the new rule is active and " +"devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` " +"box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:178 +msgid "Uninstalling Windows IoT" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:180 +msgid "" +"Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is " +"done through the Windows program manager. Using any Windows version, search " +"for `program`. Then, select :guilabel:`Add or Remove Programs` located in " +"the control panel. Search for `Odoo` and click the :guilabel:`three dot " +"menu` to uninstall." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:185 +msgid "" +"Confirm the un-installation and follow the steps to uninstall through the " +"Odoo uninstall guide." +msgstr "" + +#: ../../content/applications/productivity/iot/devices.rst:5 +msgid "Devices" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:3 +msgid "Connect a camera" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:5 +msgid "" +"A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an" +" Odoo database in just a few steps. Once a camera is connected to an " +":abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing " +"process, or it can be linked to a quality control point/quality check. Doing" +" so allows for the taking of pictures when a chosen quality control " +"point/check has been reached, or when a specific key is pressed during " +"manufacturing." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:12 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 +#: ../../content/applications/productivity/iot/devices/printer.rst:11 +#: ../../content/applications/productivity/iot/devices/scale.rst:10 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 +msgid "Connection" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:14 +msgid "" +"To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply " +"connect the two via cable. This is usually done with a :abbr:`USB (Universal" +" Serial Bus)` cable of some sort." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:17 +msgid "" +"If the camera is `supported `_, " +"there is no need to set up anything, as it'll be detected as soon as it's " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Camera recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:25 +msgid "Link camera to quality control point in manufacturing process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:27 +msgid "" +"In the :menuselection:`Quality app`, a device can be set up on a " +":guilabel:`Quality Control Point`. To do that, navigate to the " +":menuselection:`Quality app --> Quality Control --> Control Points` and open" +" the desired :guilabel:`Control Point` that'll be linked to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:31 +msgid "" +"On the control point form, edit the control point by selecting the " +":guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the " +"drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein " +"the attached *device* can be selected. :guilabel:`Save` the changes, if " +"required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Setting up the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:40 +msgid "" +"The camera is now useable with the selected quality control point. When the " +"quality control point is reached during the manufacturing process, the " +"database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:48 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`. From here, select the device. There is" +" a :guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:53 +msgid "" +"On a quality check form, the :guilabel:`Type` of check can also be specified" +" to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> " +"Quality Control --> Quality Checks --> New` to create a new quality check " +"from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:58 +#: ../../content/applications/productivity/iot/devices/printer.rst:70 +msgid "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:59 +#: ../../content/applications/productivity/iot/devices/printer.rst:71 +msgid "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:64 +msgid "" +"To link a camera to an action, it first needs to be configured on a work " +"center. Navigate to :menuselection:`Manufacturing app --> Configuration --> " +"Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a " +"camera will be used to reveal that specific work center's detail form. From " +"here, add the device in the :guilabel:`IoT Triggers` tab, in the " +":guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:70 +msgid "" +"Now, the camera device can be linked to the :guilabel:`Action` column drop-" +"down option labeled :guilabel:`Take a Picture`. A key can also be added to " +"trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:74 +msgid "" +"The first trigger listed is chosen first. The order of triggers matters, and" +" they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:78 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:82 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92 +#: ../../content/applications/productivity/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:3 +msgid "Connect a footswitch" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:5 +msgid "" +"When working in a manufacturing environment, it's always better for an " +"operator to have both hands available at all times. Odoo's :abbr:`IoT " +"(Internet of Things)` box makes this possible when using a footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 +msgid "" +"In fact, with a footswitch, the operator is able to go from one screen to " +"another, and perform actions using their foot. This can be configured in " +"just a few steps on the work center in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 +msgid "" +"To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect" +" the two devices via cable. More often than not, this is done with a " +":abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 +msgid "" +"If the footswitch is a `supported device `_, there is no need to take further action, since it'll be " +"automatically detected when connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 +msgid "" +"To link a footswitch to an action, it first needs to be configured on a work" +" center. Navigate to :menuselection:`Manufacturing app --> Configuration -->" +" Work Centers`. From here, go to the desired :guilabel:`Work Center` in " +"which the footswitch will be used, and add the device in the :guilabel:`IoT " +"Triggers` tab, under the :guilabel:`Device` column, by selecting " +":guilabel:`Add a Line`. Doing so means the footswitch can be linked to an " +"option in the :guilabel:`Action` column drop-down, and optionally, a key can" +" be added to trigger it. An example of an :guilabel:`Action` in the " +"*Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as " +"Done` buttons on a manufacturing work order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 +msgid "" +"It should be noted that the first listed trigger is chosen first. So, the " +"order matters, and these triggers can be dragged into any order. In the " +"picture above, using the footswitch automatically skips the part of the " +"process that's currently being worked on." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 +msgid "Connect a measurement tool" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7 +msgid "" +"With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect " +"measurement tools to the Odoo database for use in the *Quality app* on a " +"quality control point/quality check, or for use in a work center during the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11 +msgid "" +"Find the list of supported devices here: `Supported devices " +"`_." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +msgid "Connect with universal serial bus (USB)" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17 +msgid "" +"To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the " +":abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of " +"Things)` box, and the device appears in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +msgid "Connect with bluetooth" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28 +msgid "" +"Activate the Bluetooth functionality on the device (see the device manual " +"for further explanation), and the :abbr:`IoT (Internet of Things)` box " +"automatically connects to the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +msgid "" +"Link a measurement tool to a quality control point in the manufacturing " +"process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, navigate to :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the measurement" +" tool should be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a" +" field called :guilabel:`Device`, where the attached device can be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 +msgid "" +"Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. " +":guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50 +msgid "" +"At this point, the measurement tool is linked to the chosen quality control " +"point. The value, which usually needs to be changed manually, is " +"automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58 +#: ../../content/applications/productivity/iot/devices/printer.rst:60 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`, then select the device. There is a " +":guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Measure`. Access a new quality check detail page, by" +" navigating to :menuselection:`Quality app --> Quality Control --> Quality " +"Checks --> New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68 +msgid "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69 +msgid "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74 +msgid "" +"To link a measurement tool to an action, it first needs to be configured on " +"a work center. To do that, navigate to :menuselection:`Manufacturing app -->" +" Configuration --> Work Centers`. Then, select the desired work center in " +"which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78 +msgid "" +"On the work center page, add the device in the :guilabel:`IoT Triggers` tab," +" under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. " +"Then, the measurement tool can be linked to the :guilabel:`Action` drop-down" +" menu option labeled :guilabel:`Take Measure`. A key can be added to trigger" +" the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84 +msgid "" +"It should be noted that the first listed trigger is chosen first. The order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:3 +msgid "Connect a printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:5 +msgid "" +"Printer installation can be done in a few easy steps. The printer can be " +"used to print receipts, labels, orders, or even reports from the different " +"Odoo apps. In addition, printer actions can be assigned as an *action on a " +"trigger* during the manufacturing process, or added onto a quality control " +"point or a quality check." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:13 +msgid "" +"The :abbr:`IoT (Internet of Things)` box supports printers connected through" +" :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. " +"`Supported printers `__ are detected" +" automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer as it would appear in the IoT app devices list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:23 +msgid "" +"The printer can take up to two minutes to appear in the *IoT app* devices " +"list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:26 +msgid "Link printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:29 +msgid "Link printer to work orders" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:31 +msgid "" +"*Work Orders* can be linked to printers, via a quality control point, to " +"print labels for manufactured products." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:34 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, go to the :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the printer " +"will be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:39 +msgid "" +"A *Manufacturing Operation* and *Work Order Operation* need to be attached " +"to a quality control point before the :guilabel:`Type` field allows for the " +":guilabel:`Print Label` option to be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:43 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and selecting :guilabel:`Print Label` from the drop-down menu of options. " +"Doing so reveals a field called :guilabel:`Device`, where the attached " +"*device* can be selected. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "This is the quality control point setup." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:52 +msgid "" +"The printer can now be used with the selected quality control point. When " +"the quality control point is reached during the manufacturing process, the " +"database presents the option to print labels for a specific product." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:65 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Print Label`. To create new quality checks, navigate" +" to :menuselection:`Quality app --> Quality Control --> Quality Checks --> " +"New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:76 +msgid "" +"To link a printer to an action, it first needs to be configured on a work " +"center. To do that, navigate to :menuselection:`Manufacturing app --> " +"Configuration --> Work Centers`. From here, select the desired work center " +"in which the printer will be used. Next, add the device in the " +":guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by " +"selecting :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:82 +msgid "" +"Then, the printer can be linked to either of the following options in the " +":guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, " +":guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can " +"also be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:87 +msgid "" +"The first listed trigger on the form will be chosen first. So, the order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:91 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:98 +msgid "Link printer to reports" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:100 +msgid "" +"It's also possible to link a type of report to a certain printer. In the " +"*IoT app*, go to the :guilabel:`Devices` menu, and select the desired " +"printer that needs to be configured." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:103 +msgid "" +"From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` " +"tab, and select :guilabel:`Add a line`. In the window that appears, check " +"all the types of :guilabel:`Reports` that should be linked to this printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer devices listed in the IoT Devices menu." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:111 +msgid "" +"Now, each time :guilabel:`Print` is selected in the control panel, instead " +"of downloading a PDF, Odoo sends the report to the selected printer, and " +"automatically prints it." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:115 +msgid "" +":doc:`POS Order Printing " +"<../../../sales/point_of_sale/restaurant/kitchen_printing>`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:118 +msgid "" +"Reports can also be configured in the :guilabel:`Technical Menu` while in " +":ref:`debug mode `. To do that, navigate to " +":menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. " +"From here, the individual report can be found in this list, where the " +":guilabel:`IoT Device` can be set on the report." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:3 +msgid "Connect a scale" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:5 +msgid "" +"A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an " +"Odoo database in a few easy steps. After setup, the *Point of Sale* app can " +"be used to weigh products, which is helpful if their prices are calculated " +"based on weight." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:12 +msgid "" +"To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it " +"with a :abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:16 +msgid "" +"In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter " +"may be needed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:18 +msgid "" +"If the scale is `compatible with Odoo IoT Box " +"`_, there is no need to set up " +"anything because it will be automatically detected as soon as it is " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "IOT box auto detection." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:25 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be restarted and the " +"scale's drivers may need to be downloaded to the box in some cases. To " +"update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage " +"and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load " +"Drivers`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "View of the IoT box settings and driver list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:34 +msgid "" +"If loading the drivers still doesn't allow for the scale to function, it may" +" be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of " +"Things)` box. In this case, a different scale will need to be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:41 +msgid "" +"To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app " +"--> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT " +"(Internet of Things)` box feature. After this is complete, the scale device " +"can be set." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:45 +msgid "" +"Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then " +"click :guilabel:`Save` to save the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "List of the external tools that can be used with PoS and the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:52 +msgid "" +"The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. " +"Now, if a product has a price per weight set, clicking on it on the " +":guilabel:`PoS` screen opens the scale screen, where the cashier can weigh " +"the product and add the correct price to the cart." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "Electronic Scale dashboard view when no items are being weighed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:3 +msgid "Connect a screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:5 +msgid "" +"In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a " +"screen display. After being configured, the screen can be used to display a " +"Point of Sale (PoS) order to a client." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:10 +msgid "An example of a PoS (point of sale) order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:12 +msgid "" +"Access the customer display by going to the :abbr:`IoT (Internet of Things)`" +" box homepage and clicking on the :guilabel:`PoS Display` button. To get to " +"the :abbr:`IoT (Internet of Things)` box homepage, navigate to " +":menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet" +" of Things)` box homepage link." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:20 +msgid "" +"The way to connect the screen display to the :abbr:`IoT (Internet of " +"Things)` box differs depending on the model." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:25 +msgid "IoT Box model 4" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:27 +msgid "" +"Connect up to two screens with micro-HDMI cables on the side of the " +":abbr:`IoT (Internet of Things)` box. If two screens are connected, they can" +" display distinct content (see :ref:`Screen Usage `)." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:31 +msgid "IoT Box model 3" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:33 +msgid "" +"Connect the screen with an HDMI cable on the side of the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema `." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:39 +msgid "" +"Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` " +"box is switched on. If it is already on, connect the screen(s), and then " +"restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten " +"seconds and plugging it back into its power source." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:44 +msgid "" +"The usage of HDMI/micro-HDMI adapters may cause issues which will result in " +"a blank, black screen on the screen display. Using the specific cable for " +"the display connection is recommended." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:47 +msgid "" +"If the connection was successful, the screen should display the " +":guilabel:`POS Client display` screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The default \"POS Client Display\" screen that appears when a screen display is successfully\n" +"connected to an IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:55 +msgid "" +"The screen should also appear in the list of :guilabel:`Displays` on the " +":abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display " +"can be seen by accessing :menuselection:`IoT app --> Devices`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a screen display name shown on the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:64 +msgid "" +"If no screen is detected, a default display named :guilabel:`Distant " +"Display` will be displayed instead. This indicates that there is no hardware" +" screen connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:0 +msgid "The \"Distant Display\" screen name will be used if no screen is detected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:74 +msgid "Usage" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:79 +msgid "" +"To use the screen in the *Point of Sale app*, go to :menuselection:`Point of" +" Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of " +"Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT " +"Box` feature." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:83 +msgid "" +"Next, select the screen from the :guilabel:`Customer Display` drop-down " +"menu. Then click :guilabel:`Save`, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:90 +msgid "" +"The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A " +"screen icon will appear in the menu at the top of the screen to indicate the" +" screen's connection status." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The \"screen\" icon on the Point of Sale display shows the connection status with the\n" +"screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:98 +msgid "" +"The screen will automatically show the :abbr:`PoS (Point of Sale)` orders " +"and update when changes are made to the order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a PoS order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:106 +msgid "Display a website on the screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:108 +msgid "" +"Open the screen form view by accessing :menuselection:`IoT app --> Devices " +"--> Customer Display`. This allows the user to choose a particular website " +"URL to display on the screen using the :guilabel:`Display URL` field." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:7 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:203 +msgid "Knowledge" +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:9 +msgid "" +"**Odoo Knowledge** is a multipurpose productivity app that allows internal " +"users to enrich their business knowledge base and provide individually or " +"collaboratively gathered information." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:12 +msgid "" +"The pages on which they gather content are called *articles*. They are " +"mainly composed of a title and a body. The latter is an HTML field " +"containing text, images, links to other articles, records from other models," +" templates, etc." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:17 +msgid "`Knowledge product page `_" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:3 +msgid "Articles editing" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:6 +msgid "Add and style content" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:8 +msgid "" +"To start adding content, click anywhere on the page. Your cursor is " +"automatically set to write the article's first-level header. Once you are " +"done writing the title, press **enter** on your keyboard to move to the next" +" line." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst-1 +msgid "knowledge's user interface" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:17 +msgid "" +"Click :guilabel:`Untitled` on the left side of the top bar to automatically " +"match your h1 :dfn:`(First-level header)` title and the article's name. To " +"change the name of your article later, you must do it manually. To do so, " +"click the name on the top bar and proceed to the modification." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:23 +msgid "Text editor" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:25 +msgid "To stylize the text using the text editor, select the text to format." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:27 +msgid "Then, you can:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:29 +msgid "" +"Change the style by clicking :guilabel:`Normal`. Doing so opens a dropdown " +"menu with multiple styles to choose from (:guilabel:`Normal, Code, Header 1 " +"→ Header 6, Quote`);" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:31 +msgid "" +"Format the text. Click :guilabel:`B` to put it in bold, :guilabel:`I` to put" +" it in italic, :guilabel:`U` to underline, and :guilabel:`S` to " +"strikethrough;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:33 +msgid "" +"Change the font color by clicking :guilabel:`A` or the background color by " +"clicking the **pencil** icon:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:36 +msgid "" +"To choose from a predefined theme color, click :guilabel:`Theme` and select " +"the desired color." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:37 +msgid "" +"To customize, click :guilabel:`Solid` and define a color using the wheel, by" +" typing its hex code, or its RGBA values." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:39 +msgid "" +"To use a gradient, click :guilabel:`Gradient`, choose a predefined gradient " +"or click :guilabel:`Custom` to create a personalized gradient." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:42 +msgid "" +"To change the text's size, click the **size number** and select the desired " +"size;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:43 +msgid "" +"Click the **lists** icons to turn the paragraph into an unordered list, an " +"ordered list, or a checklist;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:45 +msgid "Click the **chain** icon to insert or edit an URL link." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:51 +msgid "" +"To format a whole paragraph, type `/` anywhere in the text. Doing so opens " +"the **powerbox**, which allows:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:54 +msgid "Changing a paragraph into lists (unordered, ordered, checklists)." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:55 +msgid "" +"Changing a paragraph into a header (1 → 6), normal text, `code`, or " +"*quotes*." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:58 +msgid "Cover pictures" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:60 +msgid "" +"You can customize your article by adding a cover picture and an icon. Hover " +"above the h1 title and click :guilabel:`Add Cover`. A pop-up window opens to" +" set a cover picture." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:63 +msgid "" +"If your database and your Unsplash account are associated, the cover picture" +" is automatically selected based on the article's name. To modify it, hover " +"over the picture to make the buttons appear, click :guilabel:`Change Cover`," +" and select another image." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:67 +msgid "Retrieve images from different sources:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:69 +msgid "Search the **Unsplash** database." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:70 +msgid "Enter a picture's **URL**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:71 +msgid "**Upload** an image from a computer." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:73 +msgid "" +"To remove the cover, hover over it to make the buttons appear and click " +":guilabel:`Remove Cover`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:76 +msgid "" +"To associate Unsplash with your database, please refer to " +":doc:`../../websites/website/configuration/unsplash`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:78 +msgid "" +"The articles are responsive, and so are the cover pictures. As a result, the" +" images cannot be repositioned manually to fit a particular screen, as they " +"automatically resize depending on the device." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:83 +msgid "Icons" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:85 +msgid "" +"To add an icon, hover above the h1 title and click :guilabel:`Add Icon`. " +"Doing this sets a random emoji automatically. To change it, click it and " +"select one from the emoji window. To remove it, proceed equally and click " +"the red-circled :guilabel:`x`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:90 +msgid "" +"The emoji is also displayed before the corresponding article in the side " +"panel hierarchic tree." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:91 +msgid "" +"Click the emoji on the side panel to change it without opening the related " +"article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:94 +msgid "Commands" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:96 +msgid "" +"To use a command, type `/` and open the **powerbox**. Type the command's " +"name or select from multiple features to insert blocks, images, files, etc. " +"Some of them, such as `/Image` or `/Article` are common to all the apps, but" +" others are inherent to the knowledge app and cannot be found or used in any" +" other application." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:102 +msgid "List of commands" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:104 +msgid "Commands are divided into multiple categories depending on their use." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:107 +msgid "Structure" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:114 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:144 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:164 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:178 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:196 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:210 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:235 +msgid "Command" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:115 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:145 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:165 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:179 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:197 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:211 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:236 +msgid "Use" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:116 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:117 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:118 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:119 +msgid "Create a list with numbering." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:120 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:121 +msgid "Track tasks with a checklist." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:122 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:123 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:124 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:125 +msgid "Insert an horizontal rule separator." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:126 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:127 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:128 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:129 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:130 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:131 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:132 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:133 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:134 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:135 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:137 +msgid "Format" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:146 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:147 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:148 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:149 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:150 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:151 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:154 +#: ../../content/applications/productivity/knowledge/properties.rst:34 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:155 +msgid "Paragraph block." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:157 +msgid "Media" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:166 +msgid ":guilabel:`Image`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:167 +msgid "Insert an image." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:168 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:169 +msgid "Link an article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:171 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:180 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:181 +msgid "Add a link." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:182 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:183 +msgid "Add a button." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:184 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:185 +msgid "Add a specific appointment." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:186 +msgid ":guilabel:`Calendar`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:187 +msgid "Schedule an appointment." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:189 +msgid "Widget" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:198 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:199 +msgid "Insert a rating over 3 stars." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:200 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:201 +msgid "Insert a rating over 5 stars." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:212 +msgid ":guilabel:`Table of Content`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:213 +msgid "Add a table of content with the article's headings." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:214 +msgid ":guilabel:`Index`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:215 +msgid "Show the first level of nested articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:216 +msgid ":guilabel:`Outline`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:217 +msgid "Show all nested articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:218 +msgid ":guilabel:`Item Kanban`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:219 +msgid "Insert a kanban view of article items." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:220 +msgid ":guilabel:`Item List`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:221 +msgid "Insert a list view of article items." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:222 +msgid ":guilabel:`File`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:223 +msgid "Embed a file that can be downloaded." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:224 +msgid ":guilabel:`Template`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:225 +msgid "" +"Add a template section that can be inserted in messages, terms & conditions," +" or description in other applications." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:228 +msgid "Basic Blocks" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:237 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:238 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:241 +msgid "Content from other apps" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:243 +msgid "" +"Knowledge allows to retrieve content views from other applications. To do " +"so, go to the targeted app and create the desired view. Then, click " +":menuselection:`Favorite --> Insert view in article` and select an article. " +"The view is inserted at the bottom of the selected article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:248 +msgid "" +"To retrieve the view below, we created it by going to :menuselection:`Sales " +"--> Graph icon --> Pie Chart icon` and inserted it by clicking " +":menuselection:`Favorite --> Insert view in article` and selecting the " +"*Sales Playbook* article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:0 +msgid "article view from the Sales app" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:257 +msgid "" +"Users who do **not** have access to the view will **not** be able to access " +"it in **Knowledge** even though they have access to the article containing " +"the view." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:3 +msgid "Articles management" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:5 +msgid "" +"Managing articles effectively is key to maximizing the value of your " +"knowledge resources, whether working on a research project, studying for an " +"exam, or building a knowledge database for your business. Knowledge allows " +"you to fully manage your articles, from :ref:`creation ` " +"to :ref:`removal `, through :ref:`sharing " +"` and :ref:`structure `." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:11 +msgid "" +"You can find most tools to manage articles by clicking the vertical ellipsis" +" button (:guilabel:`⋮`) at the right side of the top bar. From there, you " +"can move, lock, delete, or duplicate an article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Menu with tools for the management of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:18 +msgid "Creation, sharing, and removal of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:23 +msgid "Creation" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:25 +msgid "" +"To create articles, click the :guilabel:`+ New` button on the right side of " +"the top bar or the :guilabel:`+` button next to a category or another " +"article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:29 +msgid "" +"Create private articles quickly with the Alt/Option + C keyboard shortcut." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:34 +msgid "Sharing" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:36 +msgid "" +"You can share articles with internal or external users. To do so, open the " +"share menu by clicking :guilabel:`Share` in the top-right menu of articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:40 +msgid "Invite users" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:42 +msgid "" +"To share articles with specific users (internal or external, such as a " +"partner or a customer), click :guilabel:`Invite`. This opens a pop-up window" +" in which you can choose the :guilabel:`Permission` :ref:`(i.e, access " +"rights) ` and enter the :guilabel:`Recipients`' name " +"or email." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:47 +msgid "" +"You can also restrict a specific user from accessing the article by " +"selecting :guilabel:`No access` permission." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "pop-up window to invite users to access a Knowledge article" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:54 +msgid "Share online" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:56 +msgid "" +"To share articles **online**, activate the :guilabel:`Share to web` button. " +"Doing so generates a URL link anyone can use to view the article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:59 +msgid "" +"Additionally, the share menu displays the default permission for internal " +"members along with all the users who have been granted specific permission." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Sharing menu with URL for online sharing and the list of members." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:68 +msgid "Removal" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:70 +msgid "To remove an article, you can either **delete** it or **archive** it." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:72 +msgid "" +"To delete an article, open it and click the vertical ellipsis button " +":menuselection:`(⋮) --> Delete`. The article is moved to the trash for 30 " +"days before being permanently deleted. To restore it, click :guilabel:`Open " +"the Trash`, select the article, and click :guilabel:`Restore`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:76 +msgid "" +"To archive articles, click :guilabel:`Search`, select the article(s), and " +"click :menuselection:`Action --> Archive --> Archive`. Archived articles are" +" hidden from the search menu. To retrieve an archived article, add a custom " +"filter to display them (:menuselection:`Search --> Filters --> Add Custom " +"Filter`, and set :guilabel:`Active` as :guilabel:`is No`). Then, select the " +"article(s) and go to :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:85 +msgid "Structure of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:87 +msgid "" +"Articles are organized into a hierarchical structure wherein the article on " +"top is a parent article, and those underneath are called nested articles. " +"This structure allows the grouping of related articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:91 +msgid "" +"To establish this hierarchy, create new articles by clicking the " +":guilabel:`+` button next to the parent-to-be article, or move existing " +"articles by either dragging and dropping them under the parent-to-be or by " +"clicking the vertical ellipsis button (:guilabel:`⋮`), clicking " +":guilabel:`Move To` on the toolbox and selecting the article to use as a " +"parent." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:99 +msgid "Categories" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:101 +msgid "" +"Additionally, articles are divided into four categories that can be found on" +" the left sidebar. These categories give articles default **access rights**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:104 +msgid "" +":guilabel:`Favorites`: You can set any article you can access as a favorite." +" To do so, click the star-shaped icon (:guilabel:`★`) in the top-right menu " +"of articles. Marking articles as **favorites** is user-specific and does not" +" affect other users." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:107 +msgid "" +":guilabel:`Workspace`: Articles displayed in that category are available to " +"all internal users. These users have the right to read, modify or share " +"these articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:109 +msgid "" +":guilabel:`Shared`: Articles displayed in that category are those you shared" +" with internal users, external users, or shared with you." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:111 +msgid "" +":guilabel:`Private`: Articles displayed in that category are only available " +"to you." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Categories displayed in the left sidebar of Odoo Knowledge" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:3 +#: ../../content/applications/productivity/studio/fields.rst:453 +msgid "Properties" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:5 +msgid "" +"Properties are fields containing data and that can be added to articles by " +"any user with **write** access. These fields are shared between all the " +"child articles and article items under the same parent." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:10 +msgid "" +"To be able to add properties, an article must be either a **child article** " +"or an **article item**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:14 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:16 +msgid "" +"Hover above the first-level header to make the buttons appear. Click " +":menuselection:`⚙ Add Properties --> Field Type`, select the type and add a " +"default value if needed. To make the fields appear in **kanban views**, " +"check :guilabel:`View in Kanban` as well. To validate and close the property" +" creation window, click anywhere." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst-1 +msgid "Dropdown of property fields types" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:25 +msgid "The different types assess what the field content can be:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:32 +#: ../../content/applications/productivity/knowledge/properties.rst:58 +msgid "Types" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:33 +#: ../../content/applications/productivity/knowledge/properties.rst:59 +msgid "Uses" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:35 +msgid "Allows adding any content with no restriction." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:36 +msgid ":guilabel:`Checkbox`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:37 +msgid "Add a checkbox." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:38 +msgid ":guilabel:`Integer`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:39 +msgid "Allows adding integer numbers." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:40 +msgid ":guilabel:`Decimal`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:41 +msgid "Allows adding any number." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:42 +msgid ":guilabel:`Date`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:43 +msgid "Allows selecting a date." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:44 +msgid ":guilabel:`Date & Time`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:45 +msgid "Allows selecting a date and time." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:47 +msgid "Some **field types** need to be configured:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst-1 +msgid "property configuration form" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:60 +msgid ":guilabel:`Selection`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:61 +msgid "" +"Add a drop-down selection menu with restricted values that have been set at " +"the property creation." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:64 +msgid "" +"To set it up, click :guilabel:`Add a Value` next to the :guilabel:`Values` " +"field. Enter predetermined values and press **enter** to validate; you can " +"enter as many values as needed. Click anywhere to close the property " +"creation window." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:67 +msgid ":guilabel:`Tags`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:68 +msgid "Allows creating and applying as many tags as needed." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:70 +msgid "" +"To set it up, enter your `new_tag` in the :guilabel:`Tags` field, and press " +"**enter** or click :guilabel:`Create \"new_tag\"`. Click anywhere to close " +"the window. Then, add the tags into the property field. To do so, click the " +"property field and choose from the created tags; enter the tags' name and " +"press **enter**; enter a new tag's name and create a new one on the spot." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:75 +msgid ":guilabel:`Many2one`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:76 +msgid "" +"Choose from a list of records that result from a model's domain. You can " +"only select one result." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:79 +#: ../../content/applications/productivity/knowledge/properties.rst:86 +msgid "" +"To set it up, click :guilabel:`Search a Model` in the :guilabel:`Model` " +"field, select the model. Match all records by clicking :guilabel:`## " +"Record(s)`, or filter the results by clicking :guilabel:`+ Add Filter` and " +"show the records by clicking :guilabel:`## Record(s)`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:82 +msgid ":guilabel:`Many2many`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:83 +msgid "" +"Choose from a list of records that result from a model's domain. You can " +"select as many results as needed." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:91 +msgid "Delete property fields" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:93 +msgid "" +"To remove a property, click the **pencil** icon next to the targeted " +"property, then click :menuselection:`Delete --> Delete`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:97 +msgid "Once a property field is deleted, you cannot retrieve it." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:100 +msgid "Hide the property panel" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:102 +msgid "" +"To hide the property sidebar panel, click the gear :guilabel:`(⚙)` button." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:5 +msgid "Mail Plugins" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:13 +msgid "" +"Mail Plugins are connectors that bridge your mailbox with your Odoo " +"database. With them, you can interact with your Odoo database directly from " +"your mailbox by:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:16 +msgid "Creating leads and centralizing prospects' emails into the CRM app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:17 +msgid "Generating tasks in any Odoo project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:18 +msgid "Creating tickets in the Helpdesk app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:19 +msgid "Searching and storing insights on your contacts." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:21 +msgid "" +"Mail Plugins are available for :doc:`Outlook ` and " +":doc:`Gmail `." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:27 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:29 +msgid "Mail Plugins are **free** to install and use." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:31 +msgid "" +"However, they can provide **Lead Enrichment**, which is part of a paid " +"service known as **Lead Generation**." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:34 +msgid "" +"Mail plugins allow you to test Lead Enrichment for free, whether you connect" +" the plugins to a database or not. After a while, the plugins ask you to buy" +" :doc:`../general/in_app_purchase` credits if you would like to keep using " +"this service." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:41 +msgid "Lead Generation IAP service" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:43 +msgid "" +"Lead Enrichment uses the *Lead Generation IAP service*. Each request " +"consumes one *Lead Generation credit*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:46 +msgid "" +"To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment " +"--> Buy credits` and select a package." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:50 +msgid "" +"If you are out of credits, the only information populated when clicking on " +"the suggested company is its website link and logo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:52 +msgid "" +"Check out the `Lead Generation IAP service Privacy Policy " +"`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:56 +msgid ":doc:`../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:57 +msgid "`Odoo Tutorials: Lead Enrichment `_" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:3 +msgid "Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:5 +msgid "" +"The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users " +"can keep track of all their work between Gmail and Odoo, without losing any " +"information." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:9 +msgid "Odoo Online users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:11 +msgid "" +"For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to " +"configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:15 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:94 +msgid "Install the Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:17 +msgid "" +"First, log in to the Gmail account that the user wishes to connect to Odoo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:19 +msgid "" +"From the Gmail inbox, click the plus sign icon on the right side panel to " +"get add-ons. If the side panel is not visible, click on the arrow icon at " +"the bottom right corner of the inbox to reveal it." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Plus sign icon on the Gmail inbox side panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:26 +msgid "" +"Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo" +" Inbox Addin`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Odoo Inbox Addin on Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:32 +msgid "" +"Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google " +"Workspace Marketplace " +"`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:35 +msgid "" +"Once the plugin is located, click :guilabel:`Install`. Then, click " +":guilabel:`Continue` to start the installation." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:38 +msgid "" +"Next, select which Gmail account the user wishes to connect to Odoo. Then " +"click :guilabel:`Allow` to let Odoo access the Google account. Google will " +"then show a pop-up window confirming that the installation was successful." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:43 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:134 +msgid "Configure the Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:45 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:136 +msgid "" +"The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in " +"order to use the Gmail Plugin. To enable the feature, go to " +":menuselection:`Settings --> General Settings`. Under the " +":guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then" +" click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "The Mail Plugin feature in the Settings." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:55 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:145 +msgid "Configure the Gmail inbox" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:57 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:147 +msgid "" +"In the Gmail inbox, a purple Odoo icon is now visible on the right side " +"panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click" +" on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin" +" window to grant Odoo access to the Gmail inbox." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"The Authorize Access button in the right sidebar of the Odoo plugin panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:65 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:155 +msgid "" +"Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that" +" the user wishes to connect to the Gmail inbox, and log in to the database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:69 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:159 +msgid "" +"Use the general URL for the database, not the URL of a specific page in the " +"database. For example, use `https://mycompany.odoo.com`, not " +"`https://mycompany.odoo.com/web#cids=1&action=menu`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:73 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:163 +msgid "" +"Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The " +"browser will then show a :guilabel:`Success!` message. After that, close the" +" window. The Gmail inbox and Odoo database are now connected." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:78 +msgid "Odoo On-Premise users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:80 +msgid "" +"For databases hosted on servers other than Odoo Online (or Odoo.sh), follow " +"the steps below to configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:84 +msgid "" +"As part of their security guidelines, Google requires add-on creators to " +"provide a list of URLs that can be used in actions and redirections launched" +" by the add-on. This protects users by ensuring, for example, that no add-on" +" redirects users toward a malicious website. (Read more on `Google Apps " +"Script `_.)" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:89 +msgid "" +"Since Odoo can only list the `odoo.com` domain and not every on-premise " +"customer's unique server domain, on-premise customers cannot install the " +"Gmail Plugin from the Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:96 +msgid "" +"First, access the `GitHub repository `_ for the Odoo Mail Plugins. Next, click on the green " +":guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download " +"the Mail Plugin files onto the user's computer." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"Download the ZIP file from the Odoo GitHub repository for Mail Plugins." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:104 +msgid "" +"Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-" +"extensions-master --> gmail --> src --> views`, and open the " +":file:`login.ts` file using any text editor software, such as Notepad " +"(Windows), TextEdit (Mac), or Visual Studio Code." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:108 +msgid "" +"Delete the following three lines of text from the :file:`login.ts` file:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:116 +msgid "" +"This removes the `odoo.com` domain constraint from the Gmail Plugin program." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:118 +msgid "" +"Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master " +"--> gmail`, and open the file called :guilabel:`appsscript.json`. In the " +":guilabel:`urlFetchWhitelist` section, replace all the references to " +"`odoo.com` with the Odoo customer's unique server domain." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:122 +msgid "" +"Then, in the same :guilabel:`gmail` folder, open the file called " +":guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` " +"file to push the Gmail Plugin files as a Google Project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:126 +msgid "" +"The computer must be able to run Linux commands in order to follow the " +"instructions on the :guilabel:`README.md` file." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:129 +msgid "" +"After that, share the Google Project with the Gmail account that the user " +"wishes to connect to Odoo. Then, click :guilabel:`Publish` and " +":guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-" +"on` to install the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:3 +msgid "Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:5 +msgid "" +"Outlook allows for third-party applications to connect in order to execute " +"database actions from emails. Odoo has a plugin for Outlook that allows for " +"the creation of an opportunity from the email panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:12 +msgid "" +"The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both" +" on Odoo and Outlook." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 +msgid "Enable Mail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:19 +msgid "" +"First, enable the *Mail Plugin* feature in the database. Go to " +":menuselection:`Settings --> General Settings --> Integrations`, enable " +":guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:25 +msgid "Install the Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:27 +msgid "" +"Download (:menuselection:`Save Page As --> Web Page XML only`) the following" +" XML file to upload later: " +"`https://download.odoocdn.com/plugins/outlook/manifest.xml " +"`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:31 +msgid "" +"Next, open the Outlook mailbox, and select any email. After completing this," +" click on the :guilabel:`More actions` button in the upper right-side and " +"select :guilabel:`Get Add-ins`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 +msgid "" +"Following this step, select the :guilabel:`My add-ins` tab on the left-side." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "My add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:44 +msgid "" +"Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ " +"Add a custom add-in`, and then on :guilabel:`Add from file...`" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Custom add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:51 +msgid "" +"For the next step, attach the `manifest.xml` file downloaded above, and " +"press :guilabel:`OK`. Next, read the warning and click on " +":guilabel:`Install`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Custom add-in installation warning in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:61 +msgid "Connect the database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:63 +msgid "" +"Now, Outlook will be connected to the Odoo database. First, open any email " +"in the Outlook mailbox, click on the :guilabel:`More actions` button in the " +"upper right-side, and select :guilabel:`Odoo for Outlook`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Odoo for Outlook add-in button" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:71 +msgid "" +"The right-side panel can now display **Company Insights**. At the bottom, " +"click on :guilabel:`Login`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Logging in the Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:79 +msgid "" +"Only a limited amount of **Company Insights** (*Lead Enrichment*) requests " +"are available as a trial database. This feature requires :ref:`prepaid " +"credits `." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:83 +msgid "" +"If, after a short while, the panel is still empty, it is possible that the " +"browser cookie settings prevented it from loading. Note that these settings " +"also change if the browser is in \"Incognito\" mode." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:87 +msgid "" +"To fix this issue, configure the browser to always allow cookies on Odoo's " +"plugin page." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:89 +msgid "" +"For Google Chrome, change the browser cookie settings by following the guide" +" at: `https://support.google.com/chrome/answer/95647 " +"`_ and adding " +"`download.odoo.com` to the list of :guilabel:`Sites that can always use " +"cookies`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 +msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Entering the Odoo database URL" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 +msgid "Next, click on :guilabel:`Allow` to open the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "New window pop-up warning" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:108 +msgid "" +"If the user isn't logged into the database, enter the credentials. Click on " +":guilabel:`Allow` to let the Outlook Plugin connect to the database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Allowing the Outlook Plugin to connect to a database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 +msgid "Add a shortcut to the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:120 +msgid "" +"By default, the Outlook Plugin can be opened from the *More actions* menu. " +"However, to save time, it's possible to add it next to the other default " +"actions." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:123 +msgid "" +"In the Outlook mailbox, click on :guilabel:`Settings`, then on " +":guilabel:`View all Outlook settings`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Viewing all Outlook settings" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:130 +msgid "" +"Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on " +":guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Odoo for Outlook customized action" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 +msgid "Following this step, open any email; the shortcut should be displayed." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 +msgid "Using the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:146 +msgid "" +"Now that the plug-in is installed and operational, all that needs to be done" +" to create a lead is to click on the `O` [Odoo icon] or navigate to " +":guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side" +" panel will appear on the right-side, and under :guilabel:`Opportunities` " +"click on :guilabel:`New`. A new window with the created opportunity in the " +"Odoo database will populate." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:17 +msgid "" +"Studio is a toolbox that allows you to customize Odoo without coding " +"knowledge. For example, you can, on any app, add or modify:" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:20 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:21 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:22 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:23 +msgid ":doc:`Automated actions `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:24 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:25 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:26 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:28 +msgid "" +"Or you can :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:31 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:3 +msgid "Automated actions (automations)" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:5 +msgid "" +"Automated actions are used to trigger automatic changes based on user " +"actions (e.g., apply a modification when a field is set to a specific value)" +" or on time conditions (e.g., archive a record 7 days after its last " +"update)." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:9 +msgid "" +"To create an automated action with Studio, go to :guilabel:`Automations` " +"from anywhere within Studio." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:12 +msgid "" +"For every automated action you create, the following elements should be " +"defined: the :ref:`studio/automated-actions/model`, the " +":ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-" +"actions/apply-on`, and the :ref:`studio/automated-actions/action`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an automated action on the Subscription model" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:25 +msgid "Model" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:27 +msgid "Select the model where the automated action should be applied." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:30 +msgid "" +"The model you are on when you click on :guilabel:`Automations` is pre-" +"selected by default." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:35 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:37 +msgid "" +"Define when the automated action should be applied. Six triggers are " +"available." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:42 +msgid "On Creation" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:44 +msgid "The action is triggered when a record is created and then saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:49 +msgid "On Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:51 +msgid "" +"The action is triggered when a previously saved record is edited and then " +"saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:53 +msgid "" +"Use :guilabel:`Trigger Fields` to specify which fields - and only those - " +"trigger the action on their update." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:55 +msgid "" +"To detect when a record changes from one state to another, define a " +":guilabel:`Before Update Domain` filter, which checks if the condition is " +"satisfied before the record is updated. Then set an :ref:`studio/automated-" +"actions/apply-on` filter, which checks if the condition is met after the " +"record is updated." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:61 +msgid "" +"If you want the automated action to happen when an email address is set on a" +" contact, define the :guilabel:`Before Update Domain` to `Email is not set`," +" and the :guilabel:`Apply on` domain to `Email is set`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an On Update trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:72 +msgid "On Creation & Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:74 +msgid "" +"The action is triggered when a record is created and saved or edited " +"afterward and saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:79 +msgid "On Deletion" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:81 +msgid "The action is triggered when a record is deleted." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:84 +msgid "" +"This trigger is rarely used, as archiving records is usually preferred to " +"deletion." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:89 +msgid "Based on Form Modification" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:91 +msgid "" +"The action is triggered when any change is done to a trigger field's value " +"on the :ref:`Form view `, even before saving the " +"record. This trigger only works on the user interface when a modification is" +" made by a user. If the field is changed through another action and not by " +"the user, the action will not run." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:97 +msgid "" +"This trigger can only be used with the :ref:`Execute Python Code action " +"`, so development is required." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:103 +msgid "Based on Timed Condition" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:105 +msgid "" +"The action is triggered when a trigger field's date or date & time value is " +"reached." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:107 +msgid "" +"To trigger the action after the :guilabel:`Trigger Date`, add a number of " +"minutes, hours, days, or months under :guilabel:`Delay after trigger date`. " +"To trigger the action before, add a negative number instead." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:112 +msgid "" +"If you want to send a reminder email 30 minutes before the start of a " +"calendar event, select the :guilabel:`Start (Calendar Event)` under " +":guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to" +" **-30** :guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Based on Timed Condition trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:121 +msgid "By default, the scheduler checks for trigger dates every 4 hours." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:126 +msgid "Apply on" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:128 +msgid "" +"Define on which records of the model the automated action should be applied." +" It works the same way as when you apply filters on a model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:136 +msgid "" +"Determine what the automated action should do (server action). There are " +"eight types of action to choose from." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:142 +msgid "Execute Python Code" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:144 +msgid "" +"The action is used to execute Python code. The available variables are " +"described on the :guilabel:`Python Code` tab, which is also used to write " +"your code, or on the :guilabel:`Help` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:147 +msgid "" +"To allow the action to be run through the website, tick :guilabel:`Available" +" on the Website` and add a :guilabel:`Website Path`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:153 +msgid "Create a new Record" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:155 +msgid "The action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:158 +msgid "" +"Selecting a :guilabel:`Target Model` is only required if you want to target " +"another model than the one you are on." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:161 +msgid "" +"To link the record that triggered the creation of the new record, select a " +"field under :guilabel:`Link Field`. For example, you could create a contact " +"automatically when a lead is turned into an opportunity." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:164 +msgid "" +":guilabel:`Data to Write` tab: the tab is used to specify the new record's " +"values. After selecting a :guilabel:`Field`, select its " +":guilabel:`Evaluation Type`:" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:167 +msgid "" +":guilabel:`Value`: used to directly give the field's raw value in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:168 +msgid "" +":guilabel:`Reference`: used to select the record under the " +":guilabel:`Record` column and let Studio add the internal ID in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:172 +msgid "" +"If an automated action creates a new task in a project, you can assign it to" +" a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible " +"User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, " +"and the :guilabel:`Record` to a specific user." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create a new Record action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:181 +msgid "" +":guilabel:`Python expression`: used to dynamically define the newly created " +"record’s value for a field using Python code in the :guilabel:`Value` " +"column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:187 +msgid "Update the Record" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:189 +msgid "" +"The action is used to set value(s) for field(s) of any record on the current" +" model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:192 +msgid "" +"The process to fill in the :guilabel:`Data to Write` tab is the same as " +"described under :ref:`studio/automated-actions/action/new-record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:198 +msgid "Execute several actions" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:200 +msgid "" +"The action is used to trigger multiple actions at the same time. To do so, " +"click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the " +":guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure " +"the action." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:207 +msgid "Send Email" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:209 +msgid "" +"The action is used to send an email to a contact linked to a specific " +"record. To do so, select or create an :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:215 +msgid "Add Followers" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:217 +msgid "The action is used to subscribe existing contacts to the record." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:222 +msgid "Create Next Activity" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:224 +msgid "" +"The action is used to schedule a new activity linked to the record. Use the " +":guilabel:`Activity` tab to set it up as usual, but instead of the " +":guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. " +"Select :guilabel:`Specific User` and add the user under " +":guilabel:`Responsible` if the activity should always be assigned to the " +"same user. To dynamically target a user linked to the record, select " +":guilabel:`Generic User From Record` instead and change the :guilabel:`User " +"field name` if necessary." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:232 +msgid "" +"After a lead is turned into an opportunity, you want your automated action " +"to set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity " +"User Type` to :guilabel:`Generic User From Record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create Next Activity action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:243 +msgid "Send SMS Text Message" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:245 +msgid "" +"The action is used to send an SMS to a contact linked to the record. To do " +"so, select or create an :guilabel:`SMS Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:249 +msgid "" +"If you want sent messages to be logged in the Chatter, tick :guilabel:`Log " +"as Note`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:26 +#: ../../content/applications/productivity/studio/fields.rst:325 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:36 +#: ../../content/applications/productivity/studio/fields.rst:220 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:38 +#: ../../content/applications/productivity/studio/fields.rst:71 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:66 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:68 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:82 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:84 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:87 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:89 +#: ../../content/applications/productivity/studio/fields.rst:118 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:91 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:103 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:105 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:109 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:112 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the later " +"as it offers more functionalities." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:115 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:116 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:120 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:131 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:133 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:136 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:149 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:151 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:153 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:164 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:166 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:168 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:180 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:182 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:185 +msgid "" +":guilabel:`Date`: used to record the time without displaying it on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:186 +msgid "" +":guilabel:`Remaining days`: displays the remaining number of days before the" +" selected date (e.g., *In 5 days*), based on the current date and time." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:198 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:200 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:203 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:204 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:215 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:217 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:222 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:224 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:228 +#: ../../content/applications/productivity/studio/fields.rst:352 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:231 +msgid "" +"By default, radio buttons are organized vertically. Tick :guilabel:`display " +"horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:243 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:245 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default " +"and four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:253 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:266 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:268 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:271 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:274 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:276 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:288 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:290 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:297 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:303 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:305 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:311 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:320 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:322 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:330 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:332 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:336 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:345 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:347 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:348 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:350 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:357 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:359 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:363 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:371 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-" +"search of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:378 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:380 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:384 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:397 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:399 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:405 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:413 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:414 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:421 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:423 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:430 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:441 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:443 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:447 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:455 +msgid "" +":guilabel:`Invisible`: When it is not necessary for users to view a field on" +" the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing " +"the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:460 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:465 +msgid "" +"The :guilabel:`Invisible` attribute also applies to Studio. To view hidden " +"fields inside Studio, click on a view's :guilabel:`View` tab and tick " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:469 +msgid "" +":guilabel:`Required`: If a field should always be completed by the user " +"before being able to proceed, tick :guilabel:`Required`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:471 +msgid "" +":guilabel:`Read only`: If users should not be able to modify a field, tick " +":guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:474 +msgid "" +"You can choose to apply these three properties only for specific records by " +"clicking on :guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:477 +msgid "" +":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:480 +msgid "" +"This is not the same name as used in the PostgreSQL database. To view and " +"change the latter, activate the :ref:`Developer mode `, and " +"edit the :guilabel:`Technical Name`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:483 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, write a " +"description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip" +" box when hovering with your mouse over the field's label." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:486 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, write it under :guilabel:`Placeholder`. It is displayed in light " +"gray in lieu of the field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:488 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:490 +msgid "" +":guilabel:`Default value`: To add a default value to a field when a record " +"is created, use :guilabel:`Default value`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:492 +msgid "" +":guilabel:`Limit visibility to groups`: To limit which users can see the " +"field, select a user access group." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +":guilabel:`Studio customizations` is added to your database." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:217 +msgid "" +"To export these customizations, go to :menuselection:`Main dashboard --> " +"Studio --> Customizations --> Export` to download a ZIP file containing all " +"customizations." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:220 +msgid "" +"To import and install these customizations in another database, connect to " +"the destination database and go to :menuselection:`Main dashboard --> Studio" +" --> Customizations --> Import`, then upload the exported ZIP file before " +"clicking on the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:225 +msgid "" +"Before importing, make sure the destination database contains the same apps " +"and modules as the source database. Studio does not add the underlying " +"modules as dependencies of the exported module." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can edit existing PDF reports (e.g., orders and quotations)" +" or create new ones." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:8 +msgid "" +"To edit a standard PDF report, it is strongly recommended to **duplicate** " +"it and make changes to the duplicated version, as changes made to standard " +"reports will be overwritten after an Odoo upgrade. To duplicate a report, go" +" to :menuselection:`Studio --> Reports`. Hover the mouse pointer on the top " +"right corner of the report, click the vertical ellipsis icon " +"(:guilabel:`⋮`), and then select :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:20 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:22 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings --> Companies: Document Layout --> Configure " +"Document Layout`. Layout settings apply to all reports but only to the " +"current company." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:27 +msgid "" +"Use :guilabel:`Download PDF Preview` to view how the different settings " +"affect the layout of a sample invoice." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:33 +msgid "Layout" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:35 +msgid "Four layouts are available." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:39 +msgid "Light" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:44 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:49 +msgid "Bold" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:54 +msgid "Striped" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:62 +msgid "Font" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:64 +msgid "" +"Seven fonts are available. Click on the links below to preview them on " +"`Google Fonts `_." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:67 +msgid "`Lato `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:68 +msgid "`Roboto `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:69 +msgid "`Open Sans `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:70 +msgid "" +"`Montserrat `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:71 +msgid "`Oswald `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:72 +msgid "`Raleway `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:73 +msgid "`Tajawal `_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:76 +msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:81 +msgid "Company logo" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:83 +msgid "Upload an image file to add a :guilabel:`Company Logo`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:86 +msgid "" +"This adds the logo to the company’s record on the *Company* model, which you" +" can access by going to :menuselection:`General Settings --> Companies --> " +"Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:92 +msgid "Colors" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:94 +msgid "" +"Change the primary and secondary colors used throughout reports to highlight" +" important elements. The default colors are automatically generated based on" +" the colors of the logo." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:100 +msgid "Layout background" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:102 +msgid "Change the :guilabel:`Layout Background` of the report:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:104 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:105 +msgid "" +":guilabel:`Geometric`: an image featuring geometric shapes is displayed in " +"the background." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:106 +msgid ":guilabel:`Custom`: use a custom background image by uploading one." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:111 +msgid "Company tagline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:113 +msgid "" +"The :guilabel:`Company Tagline` is displayed on the header of :ref:`External" +" reports `. You can add multiple " +"lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:119 +msgid "Company details" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:121 +msgid "" +"The :guilabel:`Company Details` are displayed on the header of " +":ref:`External reports `. You can" +" add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:127 +msgid "Footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:129 +msgid "" +"Use the :guilabel:`Footer` field to put any text in the :ref:`External " +"reports' ` footers. You can add " +"multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:135 +msgid "Paper format" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:137 +msgid "" +"Use the :guilabel:`Paper format` field to change the paper size of reports. " +"You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US " +"Letter` (21.59 cm x 27.54 cm)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:141 +msgid "" +"You can change the :guilabel:`Paper format` on individual reports. Open the " +"app containing the report, then go to :menuselection:`Studio --> Reports -->" +" Select or Create a report --> Report --> Select a Paper format`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Configuration pop-up window for the default layout of PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:151 +msgid "Header and footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:153 +msgid "" +"When creating a new report in Studio, you must choose between one of three " +"styles of reports first. This is solely used to determine what is displayed " +"on the header and footer. To do so, go to the app on which you want to add a" +" new report, click the **Toggle Studio** button, then click " +":guilabel:`Reports`. Click :guilabel:`New` and select :ref:`studio/pdf-" +"reports/header-footer/external`, :ref:`studio/pdf-reports/header-" +"footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:163 +msgid "External" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:165 +msgid "" +"The header displays the company :ref:`studio/pdf-reports/default-" +"layout/logo` and several values set on the *Company* model: the " +":guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and " +":guilabel:`Website`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:170 +msgid "" +"To change a company's information, go to :menuselection:`Settings --> " +"Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External header" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:175 +msgid "" +"The footer displays the values set on the :ref:`studio/pdf-reports/default-" +"layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and " +":ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page" +" number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:185 +msgid "Internal" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:187 +msgid "" +"The header displays the user's current date and time, :guilabel:`Company " +"Name`, and page number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:189 +msgid "There is no footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:194 +msgid "Blank" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:196 +msgid "There is neither a header nor a footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:201 +msgid "Add tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:203 +msgid "" +"After opening an existing report or creating a new one, go to the " +":guilabel:`Add` tab to add or edit elements. The elements are organized into" +" four categories: :ref:`studio/pdf-reports/elements/block`, " +":ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-" +"reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:211 +msgid "Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:213 +msgid "" +"Block elements start on a new line and occupy the full width of the page." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:216 +msgid "" +"You can set an element's width by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:218 +#: ../../content/applications/productivity/studio/pdf_reports.rst:247 +msgid ":guilabel:`Text`: add any text using small font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:220 +msgid "" +":guilabel:`Title Block`: add any text using larger font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:222 +msgid "" +":guilabel:`Image`: add an image. You can either upload one from your device," +" add one from an URL, or select one already existing on your database." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:225 +#: ../../content/applications/productivity/studio/pdf_reports.rst:249 +msgid ":guilabel:`Field`: dynamically add a field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:227 +msgid "" +":guilabel:`Field & Label`: to dynamically add a field's value and label." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:229 +msgid "" +":guilabel:`Address Block`: to dynamically add the values, if any, of a " +"contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and " +"*Email*." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of an Address Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:238 +msgid "Inline" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:240 +msgid "" +"Inline elements are used around other elements. They do not start on a new " +"line and the width adapts to length of the content." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:244 +msgid "" +"You can set an element's width and margins by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:254 +msgid "Table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:256 +msgid "Table elements are used together to create a data table." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:258 +msgid "" +":guilabel:`Data table`: create a table and dynamically add a first column " +"displaying the *Name* values of a :ref:`Many2Many ` or :ref:`One2Many ` field on your model." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of a Data table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:265 +msgid "" +":guilabel:`Field Column`: add a new column to the table displaying the " +"values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:269 +msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:271 +msgid "" +":guilabel:`Field in Cell`: add, within an existing table cell, the values of" +" a :ref:`Related Field ` to " +"the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:275 +msgid "" +":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's " +"value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts " +"are added before the total amount." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:281 +msgid "Column" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:283 +msgid "" +"Columns are used to add multiple :ref:`blocks ` elements on the same line." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:286 +msgid ":guilabel:`Two Columns`: add any text in two different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:288 +msgid ":guilabel:`Three Columns`: add any text in three different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:291 +msgid "Report tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:293 +msgid "" +"Several configuration options are available under the :guilabel:`Report` " +"tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:295 +msgid "" +":guilabel:`Name`: change the report name. The new name is applied everywhere" +" (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:298 +msgid ":guilabel:`Paper format`: change the paper size of the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:300 +msgid "" +":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` " +"button available on the record." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:303 +msgid "" +":guilabel:`Limit visibility to groups`: limit the availability of the PDF " +"report to specific :doc:`user groups <../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:307 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:309 +msgid "" +"Select an element on the report to access the element's options and edit it." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "The Options tab for a text element" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:315 +msgid "" +"You can select and edit multiple elements at the same time by clicking on " +"the different sections or divisions (e.g., `div`, `table`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:318 +msgid "Below are presented some of the most common options:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:320 +msgid "" +":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, " +":guilabel:`bottom`, and :guilabel:`left` of the element." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:323 +msgid ":guilabel:`Width`: set the element's maximum width." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:325 +msgid "" +":guilabel:`Visible if`: set under which condition(s) the element should be " +"displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:327 +msgid "" +":guilabel:`Visible for`: set for which :doc:`users groups " +"<../../general/users/access_rights>` the element should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:330 +msgid "" +":guilabel:`Remove from View`: remove the element from the report's view." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:332 +msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:334 +msgid "" +":guilabel:`Alignment`: align the element to the left, center, or right of " +"the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:336 +msgid ":guilabel:`Font style`: use one of the default font styles." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:338 +msgid ":guilabel:`Colors`: change the font's color and the background color." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:341 +msgid "" +"You may need to select a section or division above the element you want to " +"edit to see some of the options described above." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +"model. One model can have several views, which are simply different ways to " +"show the same data. In Studio, views are organized into four categories: " +":ref:`general `, :ref:`multiple records " +"`, :ref:`timeline `, " +"and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:12 +msgid "" +"To change the default view of a model, go to :menuselection:`Studio --> " +"Views --> Dropdown menu (⋮) --> Set as Default`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:16 +msgid "" +"You can modify views by using the built-in XML editor. To do so, activate " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab and then click on :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:21 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard views and inherited views, as those would be reset and " +"would not be kept in case of an update or module upgrade. Always make sure " +"you select the right Studio inherited views. Indeed, when you modify a view " +"in Studio by drag-and-dropping a new field, a specific Studio inherited view" +" and its XPath, the latter which defines which part of the view is modified," +" are automatically generated." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:31 +msgid "General views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:34 +#: ../../content/applications/productivity/studio/views.rst:97 +#: ../../content/applications/productivity/studio/views.rst:195 +#: ../../content/applications/productivity/studio/views.rst:311 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:40 +msgid "Form" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:42 +msgid "" +"The :guilabel:`Form` view is used when creating and editing records, such as" +" contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:45 +msgid "" +"To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:47 +#: ../../content/applications/productivity/studio/views.rst:132 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:59 +msgid "Activity" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:61 +msgid "" +"The :guilabel:`Activity` view is used to schedule and have an overview of " +"activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:65 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:76 +msgid "Search" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:78 +msgid "" +"The :guilabel:`Search` view is added on top of other views to filter, group," +" and search records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:80 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:82 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:94 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:103 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:105 +msgid "" +"The :guilabel:`Kanban` view is often used to support business flows by " +"moving records across stages or as an alternative way to display records " +"inside *cards*." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:109 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:112 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:113 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:115 +msgid "" +"To change the way records are grouped by default, select a new group under " +":guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:127 +msgid "List" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:129 +msgid "" +"The :guilabel:`List` view is used to overview many records at once, look for" +" records, and edit simple records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:134 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`New record on top` or :guilabel:`New record at the bottom` under " +":guilabel:`Editable`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:138 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:141 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:142 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:145 +msgid "" +"To add a drag handle icon to reorder records manually, add an :ref:`Integer " +"field ` with the :guilabel:`Handle` " +"widget." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:161 +msgid "Map" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:163 +msgid "" +"The :guilabel:`Map` view is used to display records on a map. For example, " +"it is used in the Field Service app to plan an itinerary between different " +"tasks." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:167 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:170 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:172 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:174 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:175 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:187 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:190 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:203 +msgid "" +"The :guilabel:`Calendar` view is used to overview and manage records inside " +"a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:205 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:209 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:213 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:217 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:220 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:223 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:227 +msgid "" +"You can also use :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` " +"field on the model which specifies the duration of the event. However, if " +"you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not " +"be taken into account." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:242 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:244 +msgid "" +"The :guilabel:`Cohort` view is used to examine the life cycle of records " +"over a time period. For example, it is used in the Subscriptions app to view" +" the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:247 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:249 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:251 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:255 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:268 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:270 +msgid "" +"The :guilabel:`Gantt` view is used to forecast and examine the overall " +"progress of records. Records are represented by a bar under a time scale." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:273 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:275 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:279 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:282 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:283 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:284 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:286 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:288 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:292 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:294 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:308 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:317 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:319 +msgid "" +"The :guilabel:`Pivot` view is used to explore and analyze the data contained" +" in records in an interactive manner. It is especially useful to aggregate " +"numeric data, create categories, and drill down the data by expanding and " +"collapsing different levels of data." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:323 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:325 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:327 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:329 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:341 +msgid "Graph" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:343 +msgid "" +"The :guilabel:`Graph` view is used to showcase data from records in a bar, " +"line, or pie chart." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:345 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:347 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:349 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:351 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:354 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:356 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:368 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:370 +msgid "" +"The :guilabel:`Dashboard` view is used to display multiple reporting views " +"and key performance indicators. Which elements are displayed on the view " +"depends on the configuration of the other reporting views." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Dashboard view" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:3 +msgid "To-do" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:5 +msgid "To-do assists you in organizing and managing personal tasks." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:8 +msgid "Creating to-dos" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:10 +msgid "" +"To create a to-do, click :guilabel:`New` or the plus button (:guilabel:`➕`) " +"next to a stage name. Add a title to your to-do, then click :guilabel:`Add` " +"to save it or :guilabel:`Edit` to access more options." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:14 +msgid "" +"If you choose to :guilabel:`Edit` a to-do, you have the option to add " +":guilabel:`Tags`, :guilabel:`Assignees`, or more information using the Odoo " +"Editor." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:18 +msgid "Adding :guilabel:`Assignees` shares the to-do with the users selected." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:19 +msgid "" +"Type `/` in the editor box to structure and format your content. You can " +"also add media, links, and widgets." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:23 +msgid "" +"You can create a new to-do on the fly from anywhere in Odoo by opening the " +"**command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking " +":guilabel:`Add a To-Do`, or by clicking the clock button and then " +":guilabel:`Add a To-Do`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:0 +msgid "Adding a to-do on the fly" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:31 +msgid "Converting to-dos into project tasks" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:33 +msgid "" +"If you use the :doc:`Project app <../services/project>`, you can convert to-" +"dos into project tasks. To do so, open a to-do and click the gear button " +"(:guilabel:`⚙`), then :guilabel:`Convert to Task`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:36 +msgid "" +"Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and " +":guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a" +" project task and appears in the selected project." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Converting a to-do into a task" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:43 +msgid "Managing the to-do pipeline" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:45 +msgid "" +"Your assigned **to-dos** are displayed on the app dashboard. You can drag " +"and drop a to-do to move it from one stage to another." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Example of a to-do pipeline" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:52 +msgid "" +"Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to" +" create a new stage." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:54 +msgid "" +"Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, " +":guilabel:`Edit`, or :guilabel:`Delete` it." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:0 +msgid "Stage settings button" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:61 +msgid "Scheduling activities" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:63 +msgid "" +"To schedule an activity on a to-do, click the clock button on the app " +"dashboard, then the :guilabel:`+ Schedule an activity` button." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Scheduling an activity from the To-do dashboard" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:69 +msgid "To create the activity:" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:71 +msgid "Select an :guilabel:`Activity Type`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:72 +msgid "Select a :guilabel:`Due date`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:73 +msgid "Choose who the activity should be :guilabel:`Assigned to`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:74 +msgid "" +"Add a brief :guilabel:`Summary` if needed. You can add a more elaborate " +"description in the :guilabel:`Log a note` box." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:77 +msgid "Click :guilabel:`Schedule` to complete the action." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:80 +msgid "" +"The :guilabel:`To Do` activity is *not* a to-do task. Selecting it does not " +"create a to-do task." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:83 +msgid "Viewing to-dos in the Project app" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:85 +msgid "" +"If you use the :doc:`Project app <../services/project>`, your to-dos also " +"appear as private tasks under the :guilabel:`My Tasks` view." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Example of a \"My Tasks\" pipeline in the Project app" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:92 +msgid "" +"A padlock icon is visible on your private tasks to quickly identify them " +"among your project tasks." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:3 +msgid "WhatsApp" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:5 +msgid "" +"**WhatsApp** is an instant messaging and voice-over-IP app that allows users" +" to send messages, make calls, and share content. Businesses can use " +"`WhatsApp Business `_ to" +" communicate with their customers by text, send documents and provide " +"support." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:10 +msgid "" +"With the **Odoo WhatsApp** app, a company can connect a WhatsApp Business " +"Account (WABA) to an Odoo database, which allows for the following:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:13 +msgid "Receive and reply to WhatsApp messages directly from an Odoo database" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:14 +msgid "Create new templates with dynamic placeholders/variables" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:15 +msgid "Send pre-approved templates that use dynamic variables, such as:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:17 +msgid "Quotations from the Sales app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:18 +msgid "Receipts and invoices from the Point of Sale app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:19 +msgid "Tickets from the Events app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:22 +msgid "" +"`Meta Business: create message templates for the WhatsApp Business account " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:24 +msgid "" +"`Meta Business: connect a phone number to the WhatsApp Business account " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:26 +msgid "" +"`Meta Business: change the WhatsApp Business display name " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:29 +msgid "" +"WhatsApp is a messaging service operated by Meta, which is the parent " +"company of Facebook. WhatsApp is commonly used as a communication tool in " +"many countries and by many businesses. This documentation will cover the " +"integration of a WhatsApp Business Account with Odoo. The company's Meta " +"account is configured in Odoo via an :abbr:`API (Application Programming " +"Interface)` connection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:35 +msgid "" +"The WhatsApp connector supports two flows: company initiated, and customer " +"initiated. A company can initiate a discussion by sending a template to one " +"or more people. Once the template is sent, the recipient can answer in order" +" to trigger a discussion between the sender and the receiver (a *Discuss* " +"chat window will pop up if the customer answers within 15 days)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:40 +msgid "" +"If the discussion is initiated by the client (e.g. by sending to the " +"company's public WhatsApp number), then Odoo will open a group chat with all" +" operators responsible for this WhatsApp channel." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:44 +msgid "" +"It is recommended to set up multiple WhatsApp accounts for different " +"departments. For example, the help desk team and sales teams can chat on " +"different channels." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:48 +msgid "WhatsApp configuration in a Meta" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:50 +msgid "" +"A WhatsApp integration with Odoo uses a standard :abbr:`API (Application " +"Programming Interface)` connection, and is configured on Meta in the " +"following steps:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:53 +msgid "Create a Meta business account" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:54 +msgid "Create a Meta developer account" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:55 +msgid "Setup an *app* and WhatsApp *product* on Meta's developer console" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:56 +msgid "Test the API connection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:58 +msgid "" +"Once connected, messages are then sent and received through Odoo's *Discuss*" +" application using the WhatsApp :abbr:`API (Application Programming " +"Interface)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:62 +msgid "Meta business account setup" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:64 +msgid "" +"To create a Business account with Meta (owner of Facebook) navigate to: " +"`Facebook Business Manager `_. Begin" +" by clicking :guilabel:`Create account` and then enter the business name, " +"the administrator's name, and a work email address. Then click " +":guilabel:`Next`, and a pop-up window will appear prompting to confirm the " +"email address. After confirming, click :guilabel:`Done` to close the window." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:70 +msgid "" +"Next, follow the instructions in the email sent by Facebook to confirm the " +"creation of the business account and to complete the setup process." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:74 +msgid "" +"`Set up a Meta business account " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:78 +msgid "" +"If the business account is linked to a personal Facebook account then the " +"administrator must toggle between the personal account to the business " +"account for the remainder of the configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:82 +msgid "" +"To toggle to the business account navigate to the `Facebook Developer " +"Console `_ and click on the *account name* " +"in the upper right corner. Under the :guilabel:`Business Accounts` heading, " +"click on the desired business that the WhatsApp configuration should take " +"place in. This will be the account for which Odoo will send and receive " +"WhatsApp messages." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Toggle between Meta personal and business accounts." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:93 +msgid "" +"In order to create a Meta business account, the user must already have a " +"personal Facebook account that has existed for a minimum of one hour prior " +"to setting up the Facebook Business account. Trying to create the business " +"account prior to this time will result in an error." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:98 +msgid "App creation" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:100 +msgid "" +"On the `Meta for Developers `_ dashboard, " +"sign in with the Meta developer account. If no account is configured yet, " +"link a Facebook account to create a Meta developer account." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:105 +msgid "" +"A Facebook *developer* account is different than a Facebook *business* " +"account. While developer accounts are made up of personal Facebook accounts," +" business accounts are **not** as they represent a business and manage all " +"of the business's assets in Meta, such as apps." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:110 +msgid "" +"`Set up the WhatsApp Business Platform " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:113 +msgid "" +"Click on :guilabel:`My Apps` in the top right corner after successfully " +"signing in to the Meta developer account. This will redirect the " +"administrator to all the apps the developer has configured in this specific " +"developer account. Click on :guilabel:`Create App` to begin the process of " +"configuring a new Meta application." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:119 +msgid "App type" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:121 +msgid "" +"On the :menuselection:`Create an app` page, select :guilabel:`Other` under " +"the section labeled, :guilabel:`Looking for something else?`, and then click" +" :guilabel:`Next` to be directed to another page in order to select the app " +"type. Then, click on the first option listed under the :guilabel:`Select an " +"app type` label, titled :guilabel:`Business`. This selection allows for the " +"creation and management of the WhatsApp :abbr:`API (Application Programming " +"Interface)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:127 +msgid "" +"Now, click :guilabel:`Next` to configure the app, as desired. When the app " +"*type* has been configured, the administrator will move onto the app " +"*details* section." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:131 +msgid "App details" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:133 +msgid "" +"On the :guilabel:`Details` section of the :guilabel:`Create an app` process," +" enter `Odoo` in the field under the :guilabel:`Add an app name` label." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:137 +msgid "" +"The app name can be changed at a later time in the settings, if necessary." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:140 +msgid "" +"Trademarks and branded elements may not be used in this text section. These " +"include the Meta group of companies. Do not include the word: `WhatsApp` or " +"the system will flag this in error." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:143 +msgid "" +"Next, enter the developer email address in the field under the " +":guilabel:`App contact email` label." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:145 +msgid "" +"Lastly, set the :guilabel:`Business Account - Optional` field to the Meta " +"business account profile, using the drop-down menu. To finish, click " +":guilabel:`Create app`. This action will create the app and prompts the " +"*Meta Platform Terms* and *Developer Policies* agreements." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:149 +msgid "" +"To accept the agreements, enter the Facebook password for security purposes," +" and click :guilabel:`Submit` to finalize the app creation. The browser will" +" then direct to the :guilabel:`Meta for Developers` dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:154 +msgid "" +"If the Meta business account is prohibited from advertising, claiming an app" +" won't be allowed. To resolve this issue navigate to " +"``_ for assistance." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:157 +msgid "" +"For more information, see `Meta's documentation on advertising restrictions " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:161 +msgid "Add a WhatsApp product to the app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:163 +msgid "" +"Now that the basic structure of the app has been created, a product will " +"need to be added to the app. Begin by accessing the Meta app dashboard by " +"navigating to ``_, and clicking on the" +" app that is being configured." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:167 +msgid "" +"On the next page: since WhatsApp will be used, click :guilabel:`Set up` next" +" to the box containing WhatsApp, located towards the bottom of the page." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:171 +msgid "" +"`Meta's WhatsApp developer documentation " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:173 +msgid "" +"The page then directs to the configuration page for the :guilabel:`WhatsApp " +"Business Platform API`. Use the drop-down menu to select the Meta business " +"to be configured for the :guilabel:`Select a Meta Business Account` option, " +"and then click :guilabel:`Continue` to confirm the selection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:178 +msgid "" +"When :guilabel:`Continue` is clicked, the administrator agrees to Meta's " +"terms and conditions as linked on the :guilabel:`Meta App Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:182 +msgid "" +"Once the WhatsApp product is added to the app, Meta will provide a WhatsApp " +"test phone number with 5 test messages." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:186 +msgid "Start using the WhatsApp API" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:188 +msgid "" +"After finishing the previous WhatsApp product wizard, and clicking " +":guilabel:`Continue`, the browser should have directed to the WhatsApp " +":guilabel:`Quickstart` page; this :guilabel:`Quickstart` page is where to " +"begin configuring the WhatsApp API by adding a phone number and then sending" +" an initial test message." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Navigating to the WhatsApp quickstart wizard in Meta for Developer " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:198 +msgid "" +"If the browser isn't on the :guilabel:`Quickstart` page for WhatsApp, " +"navigate to ``_ and click on the app " +"that is being configured, (the app name is `Odoo` if the instructions above " +"were followed)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:202 +msgid "" +"Then, in the menu on the left-hand side of the page, click the :guilabel:`v " +"(menu toggle)` icon next to the :guilabel:`WhatsApp` section heading. A " +"small menu will open, containing the following options:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:206 +msgid ":guilabel:`Quickstart`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:207 +msgid ":guilabel:`API Setup`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:208 +msgid ":guilabel:`Configuration`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:210 +msgid "" +"Click the :guilabel:`Quickstart` option, and then click :guilabel:`Start " +"using the API`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:213 +msgid "API Setup" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:215 +msgid "" +"After clicking on :guilabel:`Start using the API`, the page navigates to the" +" :guilabel:`API Setup`. Now that the test number has been created, a test " +"message can be sent to confirm that WhatsApp is working properly. To begin, " +"navigate to the section on the page labeled :guilabel:`Send and receive " +"messages` and click the drop-down menu next to :guilabel:`To`, under " +":guilabel:`Step 1 Select phone numbers`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:221 +msgid "" +"Now, select the only option available: :guilabel:`Manage phone number list`." +" Follow the steps and add up to five numbers to send the free test messages " +"to. After entering the appropriate country code and phone number, click on " +":guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:226 +msgid "" +"Adding a phone number to send to in this step will allow for a successful " +"test to be sent by the terminal. This is critical to ensure the WhatsApp " +":abbr:`API (Application Programming Interface)` is working." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:230 +msgid "" +"A verification code from WhatsApp Business is then sent to the phone number," +" which needs to be input on the next screen to verify ownership of the " +"number. Enter the verification code and click :guilabel:`Next` to verify the" +" number." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:235 +msgid "Send a test message via terminal" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:237 +msgid "" +"Next, send a test message via the terminal. Under the section labeled " +":guilabel:`Step 2 Send messages with the API`, click :guilabel:`Send " +"Message`. A test message will then be sent to the phone number that was set " +"in the previous section." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:241 +msgid "" +"Upon successfully receiving the message to the number, move onto the next " +"section to produce and configure webhooks." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:247 +msgid "WhatsApp configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:249 +msgid "" +"The next steps configured in this section are all within the Odoo database. " +"A few different values for a token, phone number, and account IDs all need " +"to be configured in Odoo; these values are necessary in order to create a " +":guilabel:`Callback URL` and :guilabel:`Webhook Verify Token`, which are " +"then used to configure the webhooks (in order to receive messages back into " +"the database)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:254 +msgid "" +"In Odoo, navigate to :menuselection:`WhatsApp app --> Configuration --> " +"WhatsApp Business Accounts`. Then click :guilabel:`New` to configure the " +"WhatsApp business account in Odoo." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:257 +msgid "" +"In another browser tab, navigate to " +":menuselection:`https://developers.facebook.com --> My Apps --> WhatsApp -->" +" API Configuration`, and then copy the following values from the Meta " +"developer console into the corresponding fields in Odoo:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:265 +#: ../../content/applications/productivity/whatsapp.rst:669 +msgid "Name" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:266 +msgid "Meta Console" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:267 +msgid "Odoo Interface" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:268 +msgid "Phone" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:269 +msgid ":guilabel:`Phone number ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:270 +msgid ":guilabel:`Phone Number ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:271 +msgid "Token" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:272 +msgid ":guilabel:`Temporary access token`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:273 +msgid ":guilabel:`Access Token`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:274 +msgid "App ID" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:275 +#: ../../content/applications/productivity/whatsapp.rst:276 +msgid ":guilabel:`App ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:277 +msgid "Account ID" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:278 +msgid ":guilabel:`WhatsApp Business Account ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:279 +msgid ":guilabel:`Account ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:281 +msgid "" +"To retrieve the :guilabel:`App Secret`, navigate to the Meta developer " +"console, ``_ and select the app that " +"Odoo is being configured in. Then in the left-side menu, under " +":guilabel:`App settings`, select :guilabel:`Basic`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:285 +msgid "" +"Next, click :guilabel:`Show` next to the field :guilabel:`App secret`, and " +"enter the account password to verify ownership. Copy the :guilabel:`App " +"secret` and then paste that copied value into the :guilabel:`App Secret` " +"field on the Odoo :guilabel:`WhatsApp Business Account` configuration " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:290 +msgid "" +"To complete the setup of the WhatsApp business account in Odoo, click " +":guilabel:`Test Connection`. A successful message in green will populate in " +"the upper-right corner of the dashboard if the configuration is set " +"correctly." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:295 +msgid "Configuring webhooks" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:297 +msgid "" +"To configure the webhooks for WhatsApp in Odoo, navigate to " +"``_ and select the app that Odoo is " +"being configured in. Next under the :guilabel:`WhatsApp` menu heading on the" +" left side of the screen, click on the :guilabel:`API Setup` menu item. " +"Finally go to the section marked :guilabel:`Step 3: Configure webhooks to " +"receive messages` and click on :guilabel:`Configure webhooks`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:304 +msgid "" +"Another way to configure *Webhooks* is to navigate to " +"``_ and select the app that Odoo is " +"being configured in. Then select :guilabel:`Webhooks` in the left hand menu." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Manually navigating to the Whatsapp webhooks configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:312 +msgid "" +"On the :menuselection:`Webhook configuration` page, click on " +":guilabel:`Edit`, where both the :guilabel:`Callback URL` and " +":guilabel:`Webhook Verify Token` values from the Odoo will be added." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:316 +msgid "" +"Both the :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token` " +"values were automatically populated after clicking on :guilabel:`Test " +"Connection` in the previous step." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:319 +msgid "" +"In a separate browser window, retrieve the necessary values in Odoo by " +"navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp " +"Business Accounts` and select the account that is being configured. Locate " +"the values under the section labeled :guilabel:`Receiving Messages`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:324 +msgid "" +"Copy and paste the :guilabel:`Callback URL` from Odoo into the " +":guilabel:`Callback URL` field in Meta. Similarly, copy and paste the " +":guilabel:`Webhook Verify Token` into the :guilabel:`Verify Token` field on " +"the Meta developer console, as well." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:328 +msgid "" +"Finally, click :guilabel:`Verify and save` to record the values in the Meta " +"developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:331 +msgid "Webhook fields" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:333 +msgid "" +"Now input individual webhook fields into Meta's developer console, under the" +" :guilabel:`Webhook fields` section. Click :guilabel:`Manage` and when the " +"pop-up window appears, check the boxes in the :guilabel:`Subscribe` column " +"for the following *field names*:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:337 +msgid "account_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:338 +msgid "message_template_quality_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:339 +msgid "message_template_status_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:340 +msgid "messages" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:341 +msgid "template_category_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:343 +msgid "After making the selections, click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:345 +msgid "" +"The finished :guilabel:`Webhooks` configuration will appear like this in the" +" Meta developer console:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "WhatsApp webhooks set in the Meta developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:352 +msgid "" +"The :guilabel:`Webhook fields` will only appear once the subscription is " +"confirmed using the :guilabel:`Callback URL` and :guilabel:`Webhook Verify " +"Token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:356 +msgid "" +"`Meta's WhatsApp documentation on setting webhooks " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:360 +msgid "Add phone number" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:362 +msgid "" +"To configure the phone number to use for WhatsApp in Odoo, navigate back to " +"the Meta developer console (``_) and " +"again select the app that Odoo is being configured in. Under the " +":guilabel:`WhatsApp` menu heading on the left side of the screen, click on " +"the :guilabel:`API Setup` menu item. From there, go to the section marked: " +":guilabel:`Step 5: Add a phone number`, and click on :guilabel:`Add phone " +"number`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:368 +msgid "" +"In the fields, enter a :guilabel:`Business name` as well as a " +":guilabel:`Business website or profile page`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:372 +msgid "" +"The :guilabel:`Business website or profile page` field can be a social media" +" page's :abbr:`URL (Uniform Resource Locator)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:375 +msgid "" +"Complete filling out the business information by next selecting the country " +"that the company does business in from the drop-down menu in the " +":guilabel:`Country` section. Add an address if desired, however, this " +"information is optional. After adding the location, click :guilabel:`Next` " +"to continue." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:380 +msgid "" +"The following page contains information for the :guilabel:`WhatsApp Business" +" profile`. Complete the following sections, accordingly:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:383 +msgid ":guilabel:`WhatsApp Business Profile Display Name`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:384 +msgid ":guilabel:`Timezone`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:385 +msgid ":guilabel:`Category`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:386 +msgid ":guilabel:`Business description` (optional)" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:388 +msgid "" +"Once these sections are complete, click :guilabel:`Next`. The page refreshes" +" and then prompts the administrator to :guilabel:`Add a phone number for " +"WhatsApp` in the respective field. Here, enter the phone number to configure" +" in WhatsApp." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:393 +msgid "" +"`Migrate an Existing WhatsApp Number to a Business Account " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:397 +msgid "" +"Next, choose a verification method for the phone number. Select either " +":guilabel:`Text message` or :guilabel:`Phone call`, and then click " +":guilabel:`Next` proceed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:400 +msgid "" +"The phone number entered will receive either a text or a phone call by " +"WhatsApp with a code, depending on the verification method chosen. Enter " +"that verification code into the :guilabel:`Verification code` field and " +"click :guilabel:`Next` to finish." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:405 +msgid "" +"If a payment method hasn't been added this will be necessary to proceed. " +"`Visit Meta's documentation on how to add a payment method in Meta's " +"Business Manager " +"`_." +" This is part of Meta's fraud detection system, in order to ensure that the " +"account/company are real a payment method is required to proceed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:412 +msgid "" +"`Meta for Developers: Add a Phone Number " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:418 +msgid "Permanent token" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:420 +msgid "" +"After configuration and testing are complete, a permanent token should be " +"created to replace the :guilabel:`Temporary token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:424 +msgid "" +"`Meta for Developers: System User Access Tokens " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:428 +msgid "" +"Begin by navigating to ``_ and then go to " +":menuselection:`Business settings --> User --> System Users`. Select an " +"existing system user or create a new system user by clicking on " +":guilabel:`Add`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:432 +msgid "" +"Assets now must be added to the system user and then a permanent token can " +"be generated." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:434 +msgid "" +"Click on :guilabel:`Add assets`, and when the pop-up window appears select " +":guilabel:`Apps` under the :guilabel:`Select asset type`. Then, select the " +"Odoo app and toggle the permissions to *On* under the :guilabel:`Full " +"control` option. Set this new permission setting by clicking :guilabel:`Save" +" Changes`, to which a confirmation window will appear, acknowledging the " +"addition of the asset to the system user. Finish by clicking " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:440 +msgid "" +"Next, the permanent token will be generated. Click on :guilabel:`Generate " +"new token`, and a pop-up window will appear asking which app this token " +"should be generated for. Select the :guilabel:`App` that this token is for. " +"Then determine the expiration date of either :guilabel:`60 days` or " +":guilabel:`Never`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:445 +msgid "" +"Finally, when Meta asks which permissions should the system user allow, add " +"all of the following permissions:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:448 +msgid "WhatsApp_business_messaging" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:449 +msgid "WhatsApp_business_management" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:451 +msgid "" +"When permissions are set, click :guilabel:`Generate token`. Copy the token " +"value that populates on the screen that follows." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:454 +msgid "" +"With that token value, update the :guilabel:`Access Token` field in the " +"WhatsApp business account in Odoo by navigating to :menuselection:`WhatsApp " +"app --> Configuration --> WhatsApp Business Accounts`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:459 +msgid "Go live with the Meta app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:461 +msgid "" +"Finally, to launch the app, the Meta app must be set to :guilabel:`Live` in " +"the Meta developer console. Navigate to " +"``_ and click on the app that is being" +" configured. In the top menu, toggle the :guilabel:`App Mode` field from " +":guilabel:`Development` to :guilabel:`Live`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:467 +msgid "" +"If the app status is not set to *live*, then the database will only be able " +"to contact the test numbers specified in the developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:471 +msgid "" +"A privacy policy URL must be set in order for the app to be set to live. Go " +"to the Meta developer console, ``_ and" +" select the app that Odoo is being configured in. Then, using the menu on " +"the left side of the screen, go to :menuselection:`App Settings --> Basic`. " +"Then, enter the privacy policy hyperlink address under the " +":guilabel:`Privacy Policy URL` field of the form. Click :guilabel:`Save " +"changes` to apply the privacy policy to the app." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:478 +msgid "" +"Once the app has gone live in the Meta developer console, a confirmation " +"email is sent to the administrator." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:484 +msgid "WhatsApp templates" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:486 +msgid "" +"WhatsApp templates are saved messages that are used repeatedly to send " +"messages from the database. They allow users to send quality communications," +" without having to compose the same text repeatedly." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:489 +msgid "" +"Creating different templates that are tailored to specific situations lets " +"users choose the right message for the right audience. This increases the " +"quality of the message and the overall engagement rate with the customer." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:493 +msgid "" +"WhatsApp templates can be created on both the Odoo and Meta consoles. The " +"following process will overview the process for creating templates in Odoo " +"and then afterward in Meta." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:497 +msgid "" +"WhatsApp has an approval process that must be completed before the template " +"can be used. :ref:`productivity/whatsapp/approval`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:503 +msgid "Creating templates in Odoo" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:505 +msgid "" +"To access and create WhatsApp templates, begin by navigating to the " +":menuselection:`WhatsApp app --> Templates` dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:508 +msgid "" +"At the bottom of an individual template's form, there are three tabs: " +":guilabel:`Body`, :guilabel:`Buttons`, and :guilabel:`Variables`; these " +"three tabs combined create the WhatsApp template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:512 +msgid "" +"The text is entered into the :guilabel:`Body` tab, and dynamic content that " +"is called out in the :guilabel:`Body` tab is specified in the " +":guilabel:`Variables` tab. Every piece of dynamic content (e.g., " +"placeholders) in the message (body) is specifically called out and specified" +" in the :guilabel:`Variables` tab." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:517 +msgid "" +"Templates are prefabricated layouts that allow users to send professional " +"looking messages to customers. These templates are capable of containing " +"dynamic data that will populate in the end message using variables that are " +"set in the template configuration. For example, messages can contain the end" +" user's name, call out specific products, or reference a sales order, to " +"name a few convenient and impactful variables." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:523 +msgid "" +"To create a WhatsApp template, go to the :menuselection:`WhatsApp app --> " +"Templates` dashboard and click :guilabel:`New`. On the form, enter a " +":guilabel:`Name` for the template, and select a :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:528 +msgid "" +"In order to complete this next task, administrator access rights are needed " +"to edit the :guilabel:`Applies to` field. See this :doc:`access rights " +"documentation <../general/users/access_rights>` for more information." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:532 +msgid "" +"In the :guilabel:`Account` drop-down menu, select the *WhatsApp business " +"account* in Odoo that this template should link to. Next, under the " +":guilabel:`Applies to` field select the *model* the server action will apply" +" to for this template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:537 +msgid "" +"These models can also be accessed in :ref:`developer mode `." +" On a contact form (or similar relevant form in Odoo), navigate to the model" +" that will be referenced, and hover over any field name. A box of backend " +"information will reveal itself with the specific Odoo :guilabel:`Model` name" +" in the backend. Search (using the front-end name) for this model in the " +":guilabel:`Applies to` drop-down menu in the WhatsApp template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:544 +msgid "" +"Often when changing the model or :guilabel:`Applies to` field, the " +":guilabel:`Phone Field` may produce an error The :guilabel:`Phone Field` " +"should always be set to the `Phone` or `Mobile` model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:548 +msgid "" +"To search available fields, type in the front-end name in the " +":guilabel:`Search...` box. This will find a result from all of the " +"available fields for the model (:guilabel:`Applies to`) that the template is" +" created for." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:553 +msgid "" +"In order to find specific fields, multiple levels may need to be navigated " +"in the search results box. Use the :guilabel:`> (right chevron)` and " +":guilabel:`⬅️ (left arrow)` icons to navigate between the menu levels." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "Searching for the phone field in the search bar." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:561 +msgid "" +"Change the :guilabel:`Category` to fit either a :guilabel:`Marketing`, " +":guilabel:`Utility`, or :guilabel:`Authentication` category. In most " +"instances the first two options will be used, unless the user would like to " +"send a password reset or something security related. Set to " +":guilabel:`Marketing` should there be anything promotional being sent and " +"set to :guilabel:`Utility` should there be general transactional messages " +"being sent (i.e., sales order, event ticket, etc)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:568 +msgid "" +"Specifying an incorrect category can cause a flag/rejected status from Meta " +"during the approval process." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:571 +msgid "" +"Add any :guilabel:`Users` that are allowed to use this template. In the " +"right-side column, a :guilabel:`Header type` can be configured along with a " +":guilabel:`Header message`, as well." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:574 +msgid "The available :guilabel:`Header types` are as follows:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:576 +msgid "Text" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:577 +msgid "Image" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:578 +msgid "Video" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:579 +msgid "Document" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:580 +msgid "Location (variables need to be set)" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:582 +msgid "" +"Navigate to the :guilabel:`Body` tab to configure the main message of the " +"template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:584 +msgid "" +"When all the necessary changes are made to the template, click on the " +":guilabel:`Submit for approval` button in the upper-left corner. This will " +"cause the status of the template to change to :guilabel:`Pending`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:588 +msgid "" +"The status will remain in :guilabel:`Pending` until a decision has been made" +" by Meta, whereby a confirmation email will then be sent indicating that the" +" template has been approved (or rejected). The templates will then need to " +"be synced from the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:592 +msgid "" +"See this section for more information on :ref:`syncing templates " +"`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:595 +msgid "" +"There are pre-configured demo data templates available in Odoo to use or " +"modify. These templates can be used as-is or modified to suit a specific " +"business need." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:598 +msgid "" +"To use these templates, navigate to :menuselection:`WhatsApp app --> " +"Templates` and select a pre-configured template. Click :guilabel:`Submit for" +" Approval` to start the approval process. An email will be sent to the " +"administrator of the Meta account when the template has been approved." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:603 +msgid "Buttons" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:605 +msgid "" +"Buttons can be added into the message from the :guilabel:`Buttons` tab. " +"Enter the :guilabel:`Type` (either :guilabel:`Visit Website`, " +":guilabel:`Call Number`, or :guilabel:`Quick Reply`), and then specify the " +":guilabel:`Button Text`, :guilabel:`Call Number` or :guilabel:`Website URL` " +"(including :guilabel:`Url Type`), depending on the :guilabel:`Type` of " +"button." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:611 +msgid "" +"Buttons can also be added on the Meta business console. See Meta's WhatsApp " +"template dashboard by navigating to " +"``_. Then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:616 +msgid "Using placeholders and variables" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:618 +msgid "" +"Dynamic variables reference certain fields within the Odoo database to " +"produce unique data in the WhatsApp message when using a template. Dynamic " +"variables are encoded to display fields from within the database, " +"referencing fields from within a model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:623 +msgid "" +"Many companies like to customize their WhatsApp messages with a personalized" +" piece of customer information to grab attention. This can be accomplished " +"in Odoo by referencing a field within a model by setting a dynamic variable." +" For example, a customer's name can be referenced in the email from the " +":guilabel:`Customer` field on the :guilabel:`Sales Order` model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "WhatsApp message with dynamic variables highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:632 +msgid "" +"Dynamic variables can be added in to the :guilabel:`Body` by adding " +":guilabel:`placeholders` in the *text*. To add a placeholder in the *message" +" body* enter the following text `{{1}}`. For the second placeholder enter " +"`{{2}}` and increase incrementally as more placeholders are added to the " +"text." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:637 +msgid "*The following is the text from payment receipt template body:*" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:639 +msgid "Dear {{1}}," +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Here is your invoice *{{2}}* from *{{3}}* for a total of *{{4}}{{5}}*." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "To review your invoice or pay online: {{6}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:644 +msgid "Thank you" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:647 +msgid ":ref:`productivity/whatsapp/templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:649 +msgid "" +"These placeholders must be configured on the :guilabel:`Variables` tab of " +"the template before submitting for approval from Meta. To edit the dynamic " +"variables on a template, first change the :guilabel:`Type` to " +":guilabel:`Field of Model`. This allows Odoo to reference a field within a " +"model to produce unique data in the message being sent." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:654 +msgid "" +"Next, edit the :guilabel:`Field` of the dynamic variables. The " +":guilabel:`Applies to` field in the template should be edited prior to " +"ensure the correct model and field are referenced." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:657 +msgid "" +"To search the available fields, type in the front-end name of the field in " +"the search box. This will find a result from all of the available fields for" +" the model (:guilabel:`Applies to`) that the template is created for. There " +"may be multiple levels that need to be configured." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:662 +msgid "" +"The following is an example of the variables set for the above placeholders " +"in the payment receipt noted above:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:670 +msgid "Sample Value" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:671 +msgid "Type" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:672 +msgid "Field" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:673 +msgid "body - {{1}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:674 +msgid "Azure Interior" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:675 +#: ../../content/applications/productivity/whatsapp.rst:679 +#: ../../content/applications/productivity/whatsapp.rst:683 +#: ../../content/applications/productivity/whatsapp.rst:687 +#: ../../content/applications/productivity/whatsapp.rst:691 +msgid "Field of Model" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:676 +msgid "`Partner`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:677 +msgid "body - {{2}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:678 +msgid "INV/2022/00001" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:680 +msgid "`Number`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:681 +msgid "body - {{3}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:682 +msgid "My Company" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:684 +msgid "`Company`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:685 +msgid "body - {{4}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:686 +msgid "$" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:688 +msgid "`Currency > Symbol`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:689 +msgid "body - {{5}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:690 +msgid "4000" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:692 +msgid "`Amount`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:693 +msgid "body - {{6}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:694 +msgid "\\https://.." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:695 +msgid "Portal link" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:699 +msgid "" +"For example, in the :guilabel:`Body` tab, if the following is typed, \"Hello" +" {{1}},\", then `{{1}}` must be set in the :guilabel:`Variables` tab. For " +"this specific case, the message should greet the customer by name, so the " +"`{{1}}` should be configured to populate the `{{1}}` :guilabel:`Field` with " +"the :guilabel:`Customer` name." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:705 +msgid "Customizing WhatsApp templates is out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:710 +msgid "Meta template approval" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:712 +msgid "" +"After updating the dynamic variables on the template, the template needs to " +"be submitted to Meta for approval again. Click :guilabel:`Submit for " +"Approval` to start the approval process. An email will be sent to the " +"administrator of the Meta account when the template has been approved." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:716 +msgid "" +"Following the approval from Meta, sync the templates again in the Odoo " +"database. See this documentation: :ref:`productivity/whatsapp/sync`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:720 +msgid "" +"To see the status to Meta's WhatsApp template dashboard by navigating to " +"``_. Then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:727 +msgid "Syncing templates" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:729 +msgid "" +"Templates must be synced on the Odoo database once they are approved by the " +"Meta team. To do so, begin by navigating to :menuselection:`WhatsApp app -->" +" Configuration --> WhatsApp Business Accounts` and select the configuration " +"that should be synced. Under the section marked :menuselection:`Sending " +"messages`, towards the bottom, click on :guilabel:`Sync Templates`. Meta " +"will update the templates that are approved so that they can be utilized " +"with various apps in the database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Syncing Meta WhatsApp templates to the Odoo database, with the 'Sync Templates'\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:741 +msgid "" +"A successful message in green appears in the upper-right corner with the " +"number of templates updated." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:745 +msgid "" +"Templates can also be synced individually from the template itself. Navigate" +" to the :menuselection:`WhatsApp app --> Templates` dashboard and select the" +" template to sync. Then, click on the :guilabel:`Sync Template` button " +"located in the top menu of the template's form." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:750 +msgid "Creating templates in Meta" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:752 +msgid "" +"First, navigate to `Meta's WhatsApp template dashboard " +"`_, and then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Account tools highlighted in business manager with the manage templates link" +" highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:760 +msgid "" +"To create a WhatsApp template, click on the blue :guilabel:`Create template`" +" button, and then select the :guilabel:`Category`. The options listed " +"include: :guilabel:`Marketing`, :guilabel:`Utility`, and " +":guilabel:`Authentication`. In most instances the first two options will be " +"used, unless the user would like to send a password reset or something " +"security related." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:765 +msgid "" +"Enter the :guilabel:`Name` of the template and then select the " +":guilabel:`Language` for the template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:769 +msgid "" +"Multiple languages can be selected by typing the language name(s) and " +"selecting the other languages as needed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Template configuration options listed, with Marketing, Utility, Name and Language\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:777 +msgid "" +"After making the appropriate selections, click on :guilabel:`Continue` in " +"the upper-right corner. The page redirects to the :guilabel:`Edit template` " +"page. Here the :guilabel:`Header`, :guilabel:`Body`, :guilabel:`Footer` and " +":guilabel:`Buttons` are configured. To the right of the template is a " +"preview of what the template will look like in production." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "Edit the template using a header, body, footer and buttons." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:786 +msgid "" +"When all the necessary changes are made to the template, click on the " +":guilabel:`Submit` button in the upper-right corner. A confirmation window " +"appears to confirm the language— click :guilabel:`Confirm` to approve and " +"then another window appears stating that the template will be submitted to " +"Meta for review and approval." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:791 +msgid "" +"The :guilabel:`Status` of the template will remain in :guilabel:`In review` " +"until a decision has been made by Meta. Once an email confirmation is " +"received approving the template, the templates will need to be synced from " +"within the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:796 +msgid "" +"For more information on configuring templates on the Meta developer console " +"visit `Meta's WhatsApp template documentation " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:801 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:803 +msgid "" +"Notifications in WhatsApp are handled similar to a message conversation in " +"Odoo. A pop-up window appears with the received conversation from the " +"customer. By default, notifications are set in the WhatsApp business account" +" configuration in Odoo." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:807 +msgid "" +"Notification settings can be adjusted by navigating to " +":menuselection:`WhatsApp app --> Configuration --> WhatsApp Business " +"Accounts`. From there, select the account and scroll down to the " +":menuselection:`Control` section where notifications are handled. Under the " +":guilabel:`Notify users` heading, type in the field which user(s) should be " +"notified for this particular WhatsApp channel." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:813 +msgid "" +"Once a conversation is initiated between a user and a customer, " +"notifications to all the users specified in the WhatsApp business account " +"configuration won't occur. Only notifications to the user(s) in the " +"conversation will occur. Should the user not respond within 15 days, the " +"customer's reply after the 15 days will populate once again to all the users" +" specified in the WhatsApp configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:820 +msgid "Adding users to chat" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:822 +msgid "" +"Users can be added to a WhatsApp chat by expanding the WhatsApp pop-up " +"window. WhatsApp conversations are located in the *Discuss* app. Click on " +"the :guilabel:`👤+ (add user)` icon next to it, and a window appears to " +"invite users to the conversation." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Adding users to a WhatsApp conversation, with the add user icon highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:831 +msgid "WhatsApp API FAQ" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:834 +msgid "Verification" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:836 +msgid "" +"As of February 1, 2023, if the Meta app requires advanced level access to " +"permissions, a complete business verification may need to be completed. This" +" includes submitting office business documents to Meta. `See this " +"documentation " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:842 +msgid "" +"`Meta's WhatsApp access verification documentation " +"`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:846 +msgid "Template errors" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:848 +msgid "" +"Editing templates can cause tracebacks and errors unless the exact process " +"is followed above, here: (:ref:`productivity/whatsapp/templates`)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:852 +msgid "Duplicate validation error" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:854 +msgid "" +"When syncing the templates there may be an instance when there are multiple " +"templates with the same name on Meta's business manager and in Odoo. This " +"causes a duplicate validation error. To correct this issue, rename the " +"duplicate template name on Odoo and sync the templates once again by " +"following the steps here: :ref:`productivity/whatsapp/sync`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "User error populated in Odoo when a duplicate template exists." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:864 +msgid "Token errors" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:867 +msgid "User error" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:869 +msgid "" +"Should the temporary token not be replaced with a permanent token a user " +"error will populate in Odoo when testing the connection after sending fails." +" To correct this issues see :ref:`productivity/whatsapp/token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "User error populated in Odoo when token expires." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:878 +msgid "System user error 100" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:880 +msgid "" +"Should the system user be an :guilabel:`Employee` when setting up the " +"permanent token, a user error 100 will populate." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:883 +msgid "" +"To correct this error, create an :guilabel:`Admin` system user, following " +"the process outlined here: :ref:`productivity/whatsapp/token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"User error populated in Odoo when an employee token is generated instead of " +"a Admin user." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/sales.po b/locale/hi/LC_MESSAGES/sales.po new file mode 100644 index 000000000..d94cad1f8 --- /dev/null +++ b/locale/hi/LC_MESSAGES/sales.po @@ -0,0 +1,18645 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/sales.rst:5 +#: ../../content/applications/sales/sales.rst:8 +msgid "Sales" +msgstr "" + +#: ../../content/applications/sales/crm.rst:8 +msgid "CRM" +msgstr "" + +#: ../../content/applications/sales/crm.rst:10 +msgid "" +"**Odoo CRM** helps you organize your sales activities: track leads, close " +"opportunities and get accurate forecasts. Keep opportunities organized with " +"the pipeline and manage your day-to-day activities with meetings and next " +"activities." +msgstr "" + +#: ../../content/applications/sales/crm.rst:15 +msgid "`Odoo Tutorials: CRM `_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads.rst:5 +msgid "Acquire leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:3 +msgid "Convert leads into opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 +msgid "" +"*Leads* act as qualifying steps before an opportunity is created. This " +"provides additional time before a potential opportunity is assigned to a " +"sales person." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 +#: ../../content/applications/sales/crm/optimize/gamification.rst:11 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 +#: ../../content/applications/sales/point_of_sale/configuration.rst:6 +#: ../../content/applications/sales/point_of_sale/employee_login.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:52 +#: ../../content/applications/sales/point_of_sale/restaurant.rst:20 +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:34 +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:24 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 +#: ../../content/applications/sales/subscriptions/closing.rst:31 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:11 +msgid "" +"To activate the *Leads* setting, navigate to :menuselection:`CRM app --> " +"Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. " +"Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Leads setting on CRM configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:18 +msgid "" +"Activating this feature adds a new menu, :guilabel:`Leads`, to the header " +"menu bar at the top of the screen." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Leads menu on CRM application." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:25 +msgid "" +"Once the *Leads* setting has been activated, it applies to all sales teams " +"by default. To turn off leads for a specific team, navigate to " +":menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a " +"team from the list to open the record, and uncheck the :guilabel:`Leads` " +"box. Once done, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35 +msgid "Convert a lead into an opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:37 +msgid "" +"To convert a lead into an *opportunity*, navigate to :menuselection:`CRM -->" +" Leads`, and click on a :guilabel:`Lead` from the list to open it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:40 +msgid "" +"In the upper-left corner of the screen, click the :guilabel:`Convert to " +"Opportunity` button, which opens a :guilabel:`Convert to opportunity` pop-up" +" window." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Create opportunity button on a lead record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:47 +msgid "" +"On the :guilabel:`Convert to opportunity` pop-up window, in the " +":guilabel:`Conversion action` field, select the :guilabel:`Convert to " +"opportunity` option." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 +msgid "" +"If a lead, or an opportunity, already exists in the database for this " +"customer, Odoo automatically suggests merging both leads/opportunities. For " +"more information on merging leads and opportunities, see the section on how " +"to :ref:`merge leads ` below." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:56 +msgid "" +"Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which" +" the opportunity should be assigned." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59 +msgid "" +"If the lead has already been assigned to a salesperson or a team, these " +"fields automatically populate with that information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Create opportunity pop-up." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:66 +msgid "" +"Under the :guilabel:`Customer` heading, choose from the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:68 +msgid "" +":guilabel:`Create a new customer`: Choose this option to use the information" +" in the lead to create a new customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:70 +msgid "" +":guilabel:`Link to an existing customer`: Choose this option, then select a " +"customer from the resulting drop-down menu, to link this opportunity to the " +"existing customer record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:72 +msgid "" +":guilabel:`Do not link to a customer`: Choose this option to convert the " +"lead, but not link it to a new or existing customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:75 +msgid "" +"Lastly, when all configurations are complete, click :guilabel:`Create " +"Opportunity`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:80 +msgid "Merge leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:82 +msgid "" +"Odoo automatically detects similar leads and opportunities by comparing the " +"email addresses of the associated contacts. If a similar lead/opportunity is" +" found, a :guilabel:`Similar Lead` smart button appears at the top of the " +"lead/opportunity record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Similar leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:90 +msgid "" +"To compare the details of the similar leads/opportunities, click the " +":guilabel:`Similar Leads` button. This opens a kanban view with only the " +"similar leads/opportunities. Click into each card to view the details for " +"each lead/opportunity, and confirm if they should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 +msgid "" +"When merging, Odoo gives priority to whichever lead/opportunity was created " +"in the system first, merging the information into the first created " +"lead/opportunity. However, if a lead and an opportunity are being merged, " +"the resulting record is referred to as an opportunity, regardless of which " +"record was created first." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:100 +msgid "" +"After confirming that the leads/opportunities should be merged, return to " +"the kanban view using breadcrumbs, or by clicking the :guilabel:`Similar " +"Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to " +"change to list view." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:104 +msgid "" +"Check the box on the left of the page for the leads/opportunities to be " +"merged. Then, click the :guilabel:`Action ⚙️ (gear)` icon at the top of the " +"page, to reveal a drop-down menu. From that drop-down menu, select the " +":guilabel:`Merge` option to merge the selected opportunities (or leads)." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:108 +msgid "" +"When :guilabel:`Merge` is selected from the :guilabel:`Action ⚙️ (gear)` " +"drop-down menu, a :guilabel:`Merge` pop-up window appears. In that pop-up " +"window, decide to :guilabel:`Assign opportunities to` a " +":guilabel:`Salesperson` and/or :guilabel:`Sales Team`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:112 +msgid "" +"Below those fields, the leads/opportunities to merge are listed, along with " +"their related information. To merge those selected leads/opportunities, " +"click :guilabel:`Merge`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:116 +msgid "" +"When merging opportunities, no information is lost. Data from the other " +"opportunity is logged in the chatter, and the information fields, for " +"reference." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Merge option from action menu in list view." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 +msgid "Generate leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5 +msgid "" +"Two key ways to generate new leads or opportunities for your business are " +"through email aliases and website contact forms. Odoo automatically creates " +"leads in your CRM whenever someone sends a message to a Sales Team email " +"alias or fills out a contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10 +msgid "Configure email aliases" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12 +msgid "" +"Each Sales Team can use its own unique email alias to generate " +"leads/opportunities. Any email sent to a Sales Team's email alias will " +"automatically create a lead (if leads are activated in your CRM settings) or" +" an opportunity in the pipeline for that particular team. Configure custom " +"email aliases on the configuration page for each Sales Team by navigating to" +" :menuselection:`CRM --> Configuration --> Sales Teams`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Configuring Sales Teams" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 +msgid "Use Contact Forms on your website" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25 +msgid "" +"By default, your website's *Contact Us* page displays Odoo's ready-to-use " +"Contact Form. Whenever someone submits this form, a lead or an opportunity " +"is generated in your database." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Default Contact Us page" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 +msgid "" +"The Contact Form can be activated or deactivated at any time by going to " +":menuselection:`Website --> Go to Website --> Customize --> Contact Form`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form toggle" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 +msgid "" +"When the Form is deactivated, the *Contact Us* page simply displays a button" +" to email your company directly. Any email sent this way will generate a " +"lead/opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Us Page using email" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 +msgid "" +"Choose which Sales Team or salesperson is automatically assigned to the " +"leads/opportunities created from the Contact Form by going to " +":menuselection:`Website --> Configuration --> Settings --> Communication`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form settings" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 +msgid "Customize Contact Forms" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57 +msgid "" +"Contact Forms can be customized for the specific information your team " +"needs, using the free *Form Builder* module." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60 +msgid "" +"The *Form Builder* module is installed automatically when a Form element is " +"added to a web page via the Website Builder. It can also be installed " +"manually from the :guilabel:`Apps` page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Form Builder building blocks" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 +msgid "" +"Forms can be created from scratch to serve a wide variety of purposes. " +"However, Odoo's default *Contact Us* page is designed to fit most users' " +"needs. Start with the default form and modify from there." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73 +msgid "Edit Contact Form fields" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75 +msgid "" +"In Edit mode on your website, click on any field to start editing it. The " +"following information can be edited for each field on the Contact Form:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78 +msgid "" +":guilabel:`Type`: Choose a custom field option or an existing field. " +"Examples include phone, file upload, language, etc." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80 +msgid "" +":guilabel:`Input Type`: Determine the type of entry customers should input. " +"Available options are text,email, telephone, and URL." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:82 +msgid "" +":guilabel:`Input Placeholder`: Type in an example to guide users how to " +"input information where formatting is important, such as a phone number or " +"email address." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:84 +msgid "" +":guilabel:`Label Name`: Type in the display name to show users what " +"information is needed from them." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:86 +msgid "" +":guilabel:`Label Position`: Choose the way the label is aligned with the " +"rest of the form. The label can be hidden, above the field, to the far left " +"of the field, or right adjusted and closer to the field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:89 +msgid "" +":guilabel:`Required`: Toggle this option for information that you absolutely" +" need entered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:90 +msgid "" +":guilabel:`Hidden`: Toggle this option to hide the field without deleting " +"it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:91 +msgid "" +":guilabel:`Shown on Mobile`: Toggle this option to show the field to users " +"on mobile devices." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Editable field options" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97 +msgid "" +"By default, when a Form is submitted, it sends you an email with the " +"customer's inputted information. To have it automatically generate a " +"lead/opportunity instead, edit the Form and select :guilabel:`Create an " +"Opportunity` as the Action." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:102 +msgid "" +"If leads are activated in your CRM settings, selecting :guilabel:`Create an " +"Opportunity` generates a lead instead. To learn more about activating leads " +"in the CRM settings, head over to :doc:`convert`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3 +msgid "Lead mining" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5 +msgid "" +"Lead mining is a feature that allows CRM users to generate new leads " +"directly into their Odoo database. To ensure lead qualification, lead mining" +" output is determined by a variety of filtering criteria, such as the " +"country, the company size, and the industry." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:12 +msgid "" +"To get started, go to :menuselection:`CRM --> Configuration --> Settings` " +"and activate :guilabel:`Lead Mining`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Activate lead mining in Odoo CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:20 +msgid "Generate leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22 +msgid "" +"After the :guilabel:`Lead Mining` setting is activated, a new button called " +":guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` " +"pipeline. Lead mining requests are also available through " +":menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through " +":menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate " +"Leads` button is also available." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "The Generate Leads button to use the lead mining feature." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:32 +msgid "" +"Click on the :guilabel:`Generate Leads` button, and a window will appear " +"offering a variety of criteria by which to generate leads." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "" +"The pop-up window with the selection criteria in order to generate leads in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39 +msgid "" +"Choose to generate leads for :guilabel:`Companies` to get company " +"information only, or choose :guilabel:`Companies and their Contacts` to get " +"company information as well as individual employee contact information. When" +" targeting :guilabel:`Companies and their Contacts`, there is an option to " +"filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44 +msgid "Additional filtering options include:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46 +msgid "" +":guilabel:`Size`: filter leads based on the number of employees at the " +"company" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47 +msgid "" +":guilabel:`Countries`: filter leads based on the country (or countries) they" +" are located in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48 +msgid "" +":guilabel:`States`: further filter leads based on the state they are located" +" in, if applicable" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49 +msgid "" +":guilabel:`Industries`: filter leads based on the specific industry they " +"work in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50 +msgid "" +":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned " +"to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 +msgid "" +":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads " +"will be assigned to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52 +msgid "" +":guilabel:`Default Tags`: choose which tags are applied directly to the " +"leads once found" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:55 +msgid "" +"Make sure to be aware of the latest EU regulations when receiving contact " +"information. Get more information about the General Data Protection " +"Regulation on `Odoo GDPR `_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 +#: ../../content/applications/sales/rental.rst:88 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 +msgid "" +"Lead mining is an *In-App Purchase* feature and each generated lead costs " +"one credit." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63 +msgid "" +"Choosing to generate :guilabel:`Companies and their Contacts` costs one " +"additional credit for each contact generated." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67 +msgid "" +"See here for full pricing information: `Lead Generation by Odoo IAP " +"`_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70 +msgid "" +"To buy credits, navigate to :menuselection:`CRM --> Configuration --> " +"Settings`. In the :guilabel:`Lead Generation` section, under the " +":guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits from the lead mining settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78 +msgid "" +"Credits may also be purchased by navigating to the :menuselection:`Settings " +"--> General Settings`. In the :guilabel:`In-App Purchases` section, under " +"the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits in the Odoo IAP settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88 +msgid "" +"Users of Odoo Online (SaaS) Enterprise automatically have free trial credits" +" in their database to test any IAP features." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 +msgid "Create and send quotations" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:5 +msgid "" +"Once a qualified lead has been converted into an opportunity, the next step " +"is to create and deliver a quotation. This process can be easily handled " +"through Odoo's *CRM* application." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:9 +msgid "Create a new quotation" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:11 +msgid "" +"To create a new quotation, open the :menuselection:`CRM app`, revealing the " +":guilabel:`Pipeline` page on the main *CRM* dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:14 +msgid "" +"From here, click on any opportunity to open it. Review the existing " +"information and update any fields, if necessary." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:18 +msgid "" +"If a quotation has already been created for this opportunity, it can be " +"found by clicking on the :guilabel:`Quotations` smart button at the top of " +"the top of the form. The number of existing quotations is listed on the " +"smart button, as well." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:22 +msgid "" +"At the top-left of the form, click the :guilabel:`New Quotation` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 +msgid "Qualified lead form with New Quotation button emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:29 +msgid "" +"The :guilabel:`Customer` field is **not** required on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:31 +msgid "" +"However, customer information must be added or linked before a quotation can" +" be sent. If the :guilabel:`Customer` field is left blank on the " +"opportunity, clicking the :guilabel:`New Quotation` button opens a pop-up " +"window with the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:35 +msgid "" +":guilabel:`Create a new customer`: creates a new customer record, using any " +"available information provided on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:37 +msgid "" +":guilabel:`Link to an existing customer`: opens a drop-down field with " +"existing customer names. Select a name to link this new quotation to an " +"existing customer record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:39 +msgid "" +":guilabel:`Do not link to a customer`: the quotation will **not** be linked " +"to a customer, and no changes are made to the customer information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:42 +msgid "" +"Once this button is clicked, a new quotation form appears. Confirm the " +"information in the top half of the form, and update any missing or incorrect" +" fields:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:45 +msgid "" +":guilabel:`Customer`: the company or contact for whom this quotation was " +"created." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46 +msgid "" +":guilabel:`Referrer`: if this customer was referred by another customer or " +"contact, select it from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:48 +msgid "" +":guilabel:`Invoice Address`: physical address where the invoice should be " +"sent." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49 +msgid "" +":guilabel:`Delivery Address`: physical address where any products should be " +"delivered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50 +msgid "" +":guilabel:`Quotation Template`: if applicable, select a pre-configured " +":doc:`quotation template " +"` from this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52 +msgid ":guilabel:`Expiration`: date when this quotation is no longer valid." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53 +msgid "" +":guilabel:`Quotation Date`: creation date of draft/sent orders, confirmation" +" date of confirmed orders. Note that this field is only visible if " +":doc:`Developer mode (debug mode) ` is" +" active." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56 +msgid "" +":guilabel:`Recurring Plan`: if this quotation is for a recurring product or " +"subscription, select the recurring plan configuration to be used." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:58 +msgid ":guilabel:`Pricelist`: select a pricelist to be applied to this order." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:59 +msgid "" +":guilabel:`Payment Terms`: select any applicable payment terms for this " +"quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:66 +msgid "" +"The :guilabel:`Expiration` field automatically populates based on the " +"creation date of the quotation, and the default validity time frame." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:69 +msgid "" +"To update the default validity time frame, navigate to :menuselection:`Sales" +" app --> Configuration --> Settings --> Quotations & Orders` and update the " +":guilabel:`Default Quotation Validity` field. To disable automatic " +"expiration, enter `0` in this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:73 +msgid "When the desired changes are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:75 +msgid "" +"When using a quotation template, the expiration date is based off of the " +":guilabel:`Quotation Validity` field on the template. To alter the validity " +"date computation on a template, go to :menuselection:`Sales app --> " +"Configuration --> Sales Orders --> Quotation Templates`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:79 +msgid "" +"Then, click on a template to open it, and update the number in the " +":guilabel:`Quotation Validity` field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:83 +msgid "Order lines" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:85 +msgid "" +"After updating the customer, payment, and deadline information on the new " +"quotation, the :guilabel:`Order Lines` tab can be updated with the " +"appropriate product information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:88 +msgid "" +"To do that, click :guilabel:`Add a product` in the :guilabel:`Order Lines` " +"tab." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:90 +msgid "" +"Next, type the name of an item into the :guilabel:`Product` field to search " +"through the product catalog. Then, select a product from the drop-down menu," +" or create a new one by selecting :guilabel:`Create` or :guilabel:`Create " +"and Edit`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:94 +msgid "" +"After selecting a product, update the :guilabel:`Quantity`, if necessary. " +"Confirm the information in the remaining fields." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:97 +msgid "" +"To remove a line from the quotation, click the :guilabel:`🗑️ (trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:99 +msgid "Repeat the steps above until the quotation is complete." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:102 +msgid "Preview and send quotation" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:104 +msgid "" +"To see a preview of the quotation as the customer will see it, click the " +":guilabel:`Preview` button. Doing so opens a preview in the " +":guilabel:`Customer Portal`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:107 +msgid "" +"After reviewing the customer preview, click :guilabel:`Return to edit mode` " +"to return to the quotation form in the backend." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:110 +msgid "" +"When the quotation is ready to deliver to the customer, click the " +":guilabel:`Send by Email` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:112 +msgid "" +"Doing so opens a pop-up window with a pre-configured email message. " +"Information from the quotation, including the contact information, total " +"cost, and quotation title are be imported from the quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:116 +msgid "A PDF of the quotation is added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:119 +msgid "" +"A pre-loaded template is used to create the email message. To alter the " +"template, click the internal link to the right of the :guilabel:`Load " +"template` field, located at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:123 +msgid "" +"To select a new template, select an option from the :guilabel:`Load " +"template` drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:125 +msgid "" +"Proceed to make any necessary changes to the email, then click " +":guilabel:`Send`. A copy of the message is added to the *Chatter* of the of " +"the record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:128 +msgid "" +"After a quotation is sent, the originating opportunity's " +":guilabel:`Quotations` smart button updates with a new count. This " +"quotation, and all other quotations can be accessed through this smart " +"button at the top of the opportunity in the *CRM* app." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:132 +msgid "" +"Any quotations attached to the opportunity that are confirmed, and have " +"therefore been converted to sales orders, will be deducted from the number " +"listed on the :guilabel:`Quotations` smart button. Instead, the value of the" +" sales order will appear in the :guilabel:`Orders` smart button located in " +"the same control panel." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:138 +msgid "" +"`Quotation templates " +"`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:139 +msgid "" +"`Optional products " +"`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140 +msgid "" +"`Quotation deadlines `_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143 +msgid "Mark an opportunity won or lost" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:145 +msgid "" +"In order to keep the pipeline up to date and accurate, opportunities need to" +" be identified as *won* or *lost* once a customer has responded to a " +"quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 +msgid "" +"To mark an opportunity as *won* or *lost*, return to the opportunity using " +"the breadcrumbs at the top-left of the quotation form. Or navigate to " +":menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct " +"opportunity to open it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:152 +msgid "" +"At the top-left of the form, click on either the :guilabel:`Won` or " +":guilabel:`Lost` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:154 +msgid "" +"If the opportunity is marked *won*, a green :guilabel:`Won` banner is added " +"to the record, and it is moved to the :guilabel:`Won` stage." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:157 +msgid "" +"Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a " +":guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be " +"entered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:160 +msgid "" +"From the :guilabel:`Lost Reason` drop-down field, choose an existing lost " +"reason. If no applicable reason is available, create a new one by entering " +"it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:165 +msgid "" +"It's best practice to try and use pre-configured :guilabel:`Lost Reason` " +"values as much as possible or to limit the creation of new values only to " +"sales team leads. Using consistent values for this parameter will make " +"pipeline analysis easier and more accurate when filtering for the " +":guilabel:`Lost Reason` parameter." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:170 +msgid "" +"To set up new values for this field, navigate to :menuselection:`CRM --> " +"Configuration --> Lost Reasons`, and click both :guilabel:`New`and " +":guilabel:`Save` for each new entry added to the list." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:174 +msgid "" +"Additional notes and comments can be added in the :guilabel:`Closing Note` " +"field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:176 +msgid "" +"When all the desired information has been entered in the :guilabel:`Mark " +"Lost` pop-up window, click :guilabel:`Mark as Lost`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 +msgid "" +"Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and " +"Odoo returns to the opportunity form, where a new red :guilabel:`Lost` " +"banner is now present in the upper-right corner of the opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:183 +msgid "" +"Once an opportunity is marked as *lost*, it is no longer considered active, " +"and it is removed from the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:186 +msgid "" +"In order to view a *lost* opportunity from the pipeline, click the " +":guilabel:`down arrow icon` to the right of the search bar, and select " +"either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that" +" appears." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:191 +msgid "" +"While opportunities that have been marked as *lost* are considered " +"*Archived*, be advised that, in order for an opportunity to be included as " +"*lost* in reporting, it **must** be specifically marked as *lost*, not " +"*Archived*." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:196 +msgid "" +"`Manage lost opportunities " +"`_" +msgstr "" + +#: ../../content/applications/sales/crm/optimize.rst:5 +msgid "Optimize your Day-to-Day work" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:5 +msgid "" +"Challenging your employees to reach specific targets with goals and rewards " +"is an excellent way to reinforce good habits and improve your salespeople " +"productivity. The Gamification module gives you simple and creative ways to " +"motivate and evaluate your employees with real-time recognition and badges " +"inspired by game mechanics." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:13 +msgid "" +"Install the *Gamification* module, or the *CRM gamification* one, which adds" +" some useful data (goals and challenges) that can be used on *CRM/Sale*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the gamification module being installed in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:21 +msgid "Create a challenge" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:23 +msgid "" +"Now, create your first challenge by going to :menuselection:`Settings --> " +"Gamification Tools --> Challenges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:27 +msgid "" +"As the gamification tool is a one-time technical setup, you need to activate" +" the technical features in order to access the configuration. To do so, go " +"to *Settings* and *Activate the developer mode*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View if the gamification tools menu in Odoo Settings" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:35 +msgid "" +"A challenge is a mission that you send to your sales team. It can include " +"one or several goals, set for a specific period of time. Configure your " +"challenge as follows:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:38 +msgid "Assign the salespeople to be challenged;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:39 +msgid "Assign a responsible;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:40 +msgid "Set up the periodicity along with the start and the end date;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:41 +msgid "Select your goals;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:42 +msgid "Set up your rewards (badges)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:45 +msgid "" +"Badges are granted when a challenge is finished. This is either at the end " +"of a running period (eg: end of the month for a monthly challenge), at the " +"end date of a challenge (if no periodicity is set), or when the challenge is" +" manually closed." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:49 +msgid "" +"In the example below, 2 employees are being challenged with a *Monthly Sales" +" Target*. The challenge is based on 2 goals: the total amount invoiced and " +"number of new leads generated. At the end of the month, the winner will be " +"granted with a badge." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the challenge form and a challenge being created for Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:58 +msgid "Set up goals" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:60 +msgid "" +"The users can be evaluated using goals and numerical objectives to reach." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:62 +msgid "" +"**Goals** are assigned through *challenges* that evaluate (see image above) " +"and compare members of a team throughout time." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:66 +msgid "" +"You can create a new goal on the fly from a *Challenge* by clicking on *Add " +"new item*, under *Goals*. Select the business object according to your " +"company's needs. Examples: number of new leads, time to qualify a lead, " +"total amount invoiced in a specific week, month or any other time frame " +"based on your management preferences, etc." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the goal definition form and a goal definition being created for " +"Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:73 +msgid "" +"Goals may include your database setup as well (e.g. set your company data " +"and a timezone, create new users, etc.)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:77 +msgid "Set up rewards" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:79 +msgid "" +"For non-numerical achievements, **Badges** can be granted to users. From a " +"simple thank you to an exceptional achievement, a badge is an easy way to " +"express gratitude to a user for their good work. To create and grant badges " +"to your employees based on their performance, go to :menuselection:`Settings" +" --> Gamification Tools --> Badges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the badges page in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 +msgid "Enrich your contacts base with Partner Autocomplete" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 +msgid "" +"Partner Autocomplete helps you to enrich your contacts database with " +"corporate data. Select one of the companies suggested in the dropdown, and " +"quickly get all the information you need." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 +msgid "" +"Go to :menuselection:`Settings --> Contacts` and activate the *Partner " +"Autocomplete* feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "View of settings page and the activations of the feature in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:18 +msgid "Enrich your contacts with corporate data" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:22 +msgid "" +"From any module, once you start to create a new contact typing the name of " +"it, the system will suggest a potential match. If you select it, the contact" +" will be populated with corporate data." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:23 +msgid "" +"For example, after typing *Odoo*, you will get the following information:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "Creating a new contact in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "" +"View of the information being shown about odoo with the autocomplete option " +"in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:33 +msgid "" +"Partner Autocomplete also works if you enter a VAT number instead of a " +"company name." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 +msgid "" +"*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires" +" prepaid credits to be used. Each request will consume one credit." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:41 +msgid "" +"To buy credits, go to :menuselection:`Settings --> Contacts --> Partner " +"Autocomplete or Odoo IAP --> View My Services` and select a package." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:44 +msgid "" +"If you run out of credits, the only information that will be populated when " +"clicking on the suggested company will be the website link and the logo." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46 +msgid "" +"If you are on Odoo Online and you have the Enterprise version, you benefit " +"from free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 +msgid "" +"Learn about our *Privacy Policy* `here " +"`_." +msgstr "" + +#: ../../content/applications/sales/crm/performance.rst:5 +msgid "Analyze performance" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:3 +msgid "Pipeline Analysis" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:5 +msgid "" +"The *CRM* app manages the sales pipeline as leads/opportunities move from " +"stage to stage, origination to sale (**Won**) or archival (**Lost**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:8 +msgid "" +"After organizing the pipeline, use the search options and reports available " +"on the *Pipeline Analysis* page to gain insight into the effectiveness of " +"the pipeline and its users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:11 +msgid "" +"To access the *Pipeline Analysis* page, go to :menuselection:`CRM app --> " +"Reporting --> Pipeline`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"Open the CRM app and click on the Reporting tab along the top, then click " +"Pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:20 +msgid "Navigate the pipeline analysis page" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:22 +msgid "" +"Upon accessing the :guilabel:`Pipeline Analysis` page, a bar graph " +"showcasing the leads from the past year automatically populates. The bars " +"represent the number of leads in each stage of the sales pipeline, color-" +"coded to show the month the lead reached that stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The default state of the Pipeline Analysis page is a graph, with many " +"options to change it." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:30 +msgid "" +"The interactive elements of the :guilabel:`Pipeline Analysis` page " +"manipulate the graph to report different metrics in several views. From " +"left-to-right, top-to-bottom, the elements include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:33 +msgid "" +":guilabel:`Actions`: represented by the :guilabel:`⚙️ (gear)` icon, located " +"next to the :guilabel:`Pipeline Analysis` page title. When clicked, a drop-" +"down menu appears with three options, each with their own sub-menu: " +":guilabel:`Knowledge`, :guilabel:`Dashboard`, :guilabel:`Spreadsheet`. (See " +":ref:`Save and share reports ` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:39 +msgid "" +"The :guilabel:`Knowledge` option is for linking to or inserting the graph in" +" a *Knowledge* app article." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:41 +msgid "" +"The :guilabel:`Dashboard` option is for adding the graph to a dashboard in " +"the *Dashboards* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:42 +msgid "" +"The :guilabel:`Spreadsheet` option is for linking the graph in a spreadsheet" +" in the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:44 +msgid "" +":guilabel:`Search...` bar: shows the filters and groupings currently being " +"applied to the graph. To add new filters/groups, type them into the search " +"bar, or click the :guilabel:`⬇️ (down arrow)` icon, at the end of the bar, " +"to open a drop-down menu of options. (See :ref:`Search Options " +"` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:49 +msgid "" +"In the upper-right corner, there are view options represented by different " +"icons. (See :ref:`View Options ` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:52 +msgid "" +":guilabel:`Graph` view: displays the data in a bar graph. This is the " +"default view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:53 +msgid "" +":guilabel:`Pivot` view: displays the data in a customizable, categorized " +"metrics table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:54 +msgid "" +":guilabel:`Cohort` view: displays and organizes the data, based on their " +":guilabel:`Created on` and :guilabel:`Closed Date` week (default), day, " +"month, or year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:56 +msgid ":guilabel:`List` view: displays the data in a list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:58 +msgid "" +"Located on the far-left side of the page, beneath the :guilabel:`Pipeline " +"Analysis` page title, there are more configurable filter and view options." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:61 +msgid "" +":guilabel:`Measures`: opens a drop-down menu of different measurement " +"options that can be seen in the graph, pivot, or cohort view. The " +":guilabel:`Measure` drop-down menu is not available in the list view. (See " +":ref:`Measurement Options ` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:64 +msgid "" +":guilabel:`Insert in Spreadsheet`: opens a pop-up window with options for " +"adding a graph or pivot table to a spreadsheet in the *Documents* app or a " +"dashboard in the *Dashboards* app. This option is not available in the " +"cohort or list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:68 +msgid "With the graph view selected, the following options are available:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:70 +msgid ":guilabel:`Bar Chart`: switches the graph to a bar chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:71 +msgid ":guilabel:`Line Chart`: switches the graph to a line chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:72 +msgid ":guilabel:`Pie Chart`: switches the graph to a pie chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:73 +msgid "" +":guilabel:`Stacked`: when selected, the results of each stage of the graph " +"are stacked on top of each other. When not selected, the results in each " +"stage are shown as individual bars." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:75 +msgid "" +":guilabel:`Descending`: re-orders the stages in the graph in descending " +"order from left-to-right. Click the icon a second time to deselect it. " +"Depending on the search criteria, this option may not be available." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:78 +msgid "" +":guilabel:`Ascending`: re-orders the stages in the graph in ascending order " +"from left-to-right. Click the icon a second time to deselect it. Depending " +"on the search criteria, this option may not be available." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:82 +msgid "With the pivot view selected, the following options are available:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:84 +#: ../../content/applications/sales/crm/performance/win_loss.rst:326 +msgid ":guilabel:`Flip Axis`: flips the X and Y axis for the entire table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:85 +#: ../../content/applications/sales/crm/performance/win_loss.rst:327 +msgid "" +":guilabel:`Expand All`: when additional groupings are selected using the " +":guilabel:`➕ (plus sign)` icons, this button opens those groupings under " +"every row." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:87 +#: ../../content/applications/sales/crm/performance/win_loss.rst:329 +msgid ":guilabel:`Download xlsx`: downloads the table as an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:92 +msgid "Search options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:94 +msgid "" +"The :guilabel:`Pipeline Analysis` page can be customized with various " +"filters and grouping options." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:96 +msgid "" +"To add new search criteria, type the desired criteria into the search bar, " +"or click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, to " +"open a drop-down menu of all options. See the sections below for more " +"information on what each option does." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"Clicking on the down arrow next to the search bar opens a menu of filters " +"for the analysis." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:106 +msgid "Filters" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:108 +msgid "" +"The :guilabel:`Filters` section allows users to add pre-made and custom " +"filters to the search criteria. Multiple filters can be added to a single " +"search." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:111 +msgid ":guilabel:`My Pipeline`: show leads assigned to the current user." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:112 +msgid "" +":guilabel:`Opportunities`: show leads that have been qualified as " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:113 +msgid "" +":guilabel:`Leads`: show leads that have yet to be qualified as " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:114 +msgid ":guilabel:`Active`: show active leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:115 +msgid ":guilabel:`Inactive`: show inactive leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:116 +msgid ":guilabel:`Won`: show leads that have been marked **Won**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:117 +msgid ":guilabel:`Lost`: show leads that have been marked **Lost**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:118 +msgid "" +":guilabel:`Created On`: show leads that were created during a specific " +"period of time. By default, this is the past year, but it can be adjusted as" +" needed, or removed entirely." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:120 +msgid "" +":guilabel:`Expected Closing`: show leads that are expected to close (marked " +"**Won**) during a specific period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:122 +msgid "" +":guilabel:`Date Closed`: show leads that were closed (marked **Won**) during" +" a specific period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:124 +msgid "" +":guilabel:`Archived`: show leads that have been archived (marked **Lost**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:125 +msgid "" +":guilabel:`Add Custom Filter`: allows the user to create a custom filter " +"with numerous options. (See :ref:`Add Custom Filters and Groups " +"` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:129 +msgid "Group By" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:131 +msgid "" +"The :guilabel:`Group By` section allows users to add pre-made and custom " +"groupings to the search results. Multiple groupings can be added to split " +"results into more manageable chunks." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:135 +msgid "" +"The order that groupings are added affects how the final results are " +"displayed. Try selecting the same combinations in a different order to see " +"what works best for each use case." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:139 +msgid "" +":guilabel:`Salesperson`: groups the results by the Salesperson to whom a " +"lead is assigned." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:140 +msgid "" +":guilabel:`Sales Team`: groups the results by the Sales Team to whom a lead " +"is assigned." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:141 +msgid "" +":guilabel:`City`: groups the results by the city from which a lead " +"originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:142 +msgid "" +":guilabel:`Country`: groups the results by the country from which a lead " +"originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:143 +msgid "" +":guilabel:`Company`: groups the results by the company to which a lead " +"belongs (if multiple companies are activated in the database)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:145 +msgid "" +":guilabel:`Stage`: groups the results by the stages of the sales pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:146 +msgid "" +":guilabel:`Campaign`: groups the results by the marketing campaign from " +"which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:148 +msgid "" +":guilabel:`Medium`: groups the results by the medium (Email, Google Adwords," +" Website, etc.) from which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:150 +msgid "" +":guilabel:`Source`: groups the results by the source (Search engine, Lead " +"Recall, Newsletter, etc.) from which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:152 +msgid "" +":guilabel:`Creation Date`: groups the results by the date a lead was added " +"to the database." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:153 +msgid "" +":guilabel:`Conversion Date`: groups the results by the date a lead was " +"converted to an opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:155 +msgid "" +":guilabel:`Expected Closing`: groups the results by the date a lead is " +"expected to close (marked \"Won\")." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:157 +msgid "" +":guilabel:`Closed Date`: groups the results by the date a lead was " +"closed(marked \"Won\")." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:158 +msgid "" +":guilabel:`Lost Reason`: groups the results by the reason selected when a " +"lead was marked \"Lost.\"" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:160 +msgid "" +":guilabel:`Add Custom Group`: allows the user to create a custom group with " +"numerous options. (See :ref:`Adding Custom Filters and Groups " +"` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:164 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:166 +msgid "" +"The :guilabel:`Comparison` section allows users to add comparisons to the " +"same search criteria over another period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:169 +msgid "" +"This option is only available if the search includes time-based filters, " +"such as :guilabel:`Created On`, :guilabel:`Expected Closing`, or " +":guilabel:`Date Closed`. While multiple time-based filters can be added at " +"once, only one comparison can be selected at a time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:174 +msgid "" +":guilabel:`Previous Period`: adds a comparison to the same search criteria " +"from the previous period." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:176 +msgid "" +":guilabel:`Previous Year`: adds a comparison to the same search criteria " +"from the previous year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:179 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:181 +msgid "" +"The :guilabel:`Favorites` section allows users to save a search for later, " +"so it does not need to be recreated every time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:184 +msgid "" +"Multiple searches can be saved, shared with others, or even set as the " +"default for whenever the :guilabel:`Pipeline Analysis` page is opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:187 +msgid "" +":guilabel:`Save current search`: save the current search criteria for later." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:189 +msgid "" +":guilabel:`Default filter`: when saving a search, check this box to make it " +"the default search filter when the :guilabel:`Pipeline Analysis` page is " +"opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:191 +msgid "" +":guilabel:`Shared`: when saving a search, check this box to make it " +"available to other users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:197 +msgid "Add custom filters and groups" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:199 +msgid "" +"In addition to the pre-made options in the search bar, the " +":guilabel:`Pipeline Analysis` page can also utilize custom filters and " +"groups." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:202 +msgid "" +"Custom filters are complex rules that further customize the search results, " +"while custom groups display the information in a more organized fashion." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:205 +msgid "**To add a custom filter:**" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:207 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " +"icon next to the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:209 +msgid "In the drop-down menu, click :guilabel:`Add Custom Filter`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:210 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window appears with a default rule " +"(:guilabel:`Country is in _____`) comprised of three unique fields. These " +"fields can be edited to make a custom rule, and multiple rules can be added " +"to a single custom filter." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:213 +msgid "" +"To edit a rule, start by clicking the first field (:guilabel:`Country`), and" +" select an option from the drop-down menu. The first field determines the " +"primary subject of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:215 +msgid "" +"Next, click the second field, and select an option from the drop-down menu. " +"The second field determines the relationship of the first and third fields, " +"and is usually an **is** or **is not** statement, but can also be **greater " +"than or less than** statements, and more." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:218 +msgid "" +"Finally, click the third field, and select an option from the drop-down " +"menu. The third field determines the secondary subject of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:220 +msgid "With all three fields selected, the rule is complete." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:222 +msgid "" +"**To add more rules:** click :guilabel:`New Rule` and repeat steps 4-7, as " +"needed." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:223 +msgid "" +"**To delete a rule:** click the :guilabel:`🗑️ (trash)` icon to the right of " +"the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:224 +msgid "" +"**To duplicate an existing rule:** click the :guilabel:`➕ (plus sign)` icon " +"to the right of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:226 +msgid "" +"**To create more complex rules:** click the :guilabel:`Add branch` icon to " +"the right of the rule. This adds another modifier below the rule for adding " +"an \"all of\" or \"any of\" statement." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The add branch feature allows the creation of more complex all or any " +"statements for rules." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:233 +msgid "" +"Once all rules have been added, click :guilabel:`Add` to add the custom " +"filter to the search criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:236 +msgid "" +"**To remove a custom filter:** click the :guilabel:`✖️ (x)` icon beside the " +"filter in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:239 +msgid "**To add a custom group:**" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:241 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " +"icon next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:243 +msgid "" +"In the drop-down menu that appears, click :guilabel:`Add Custom Group`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:244 +msgid "" +"Scroll through the options in the drop-down menu, and select one or more " +"groups." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:246 +msgid "" +"**To remove a custom group:** click the :guilabel:`✖️ (x)` icon beside the " +"custom group in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:252 +msgid "Measurement options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:254 +msgid "" +"By default, the :guilabel:`Pipeline Analysis` page measures the total " +":guilabel:`Count` of leads that match the search criteria, but can be " +"changed to measure other items of interest." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:257 +msgid "" +"To change the selected measurement, click the :guilabel:`Measures` button on" +" the top-left of the page, and select one of the following options from the " +"drop-down menu:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:260 +msgid "" +":guilabel:`Days to Assign`: measures the number of days it took a lead to be" +" assigned after creation." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:262 +msgid "" +":guilabel:`Days to Close`: measures the number of days it took a lead to be " +"closed (marked **Won**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:264 +msgid "" +":guilabel:`Days to Convert`: measures the number of days it took a lead to " +"be converted to an opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:266 +msgid "" +":guilabel:`Exceeded Closing Days`: measures the number of days by which a " +"lead exceeded its Expected Closing date." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:268 +msgid "" +":guilabel:`Expected MRR`: measures the Expected Recurring Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:269 +msgid ":guilabel:`Expected Revenue`: measures the Expected Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:270 +msgid "" +":guilabel:`Prorated MRR`: measures the Prorated Monthly Recurring Revenue of" +" a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:271 +msgid "" +":guilabel:`Prorated Recurring Revenues`: measures the Prorated Recurring " +"Revenues of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:272 +msgid ":guilabel:`Prorated Revenue`: measures the Prorated Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:273 +msgid "" +":guilabel:`Recurring Revenues`: measures the Recurring Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:274 +msgid "" +":guilabel:`Count`: measures the total amount of leads that match the search " +"criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:279 +msgid "View options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:281 +msgid "" +"After configuring filters, groupings, and measurements, the " +":guilabel:`Pipeline Analysis` page can display the data in a variety of " +"ways. By default, the page uses the graph view, but can be changed to a " +"pivot view, cohort view, or list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:285 +msgid "" +"To change the pipeline to a different view, click one of the four view " +"icons, located in the top-right of the :guilabel:`Pipeline Analysis` page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:290 +msgid "Graph View" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:292 +msgid "" +"The graph view is the default selection for the :guilabel:`Pipeline " +"Analysis` page. It displays the analysis as either a: bar chart, line chart," +" or pie chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:295 +msgid "" +"This view option is useful for quickly visualizing and comparing simple " +"relationships, like the :guilabel:`Count` of leads in each stage, or the " +"leads assigned to each :guilabel:`Salesperson`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:299 +msgid "" +"By default, the graph measures the :guilabel:`Count` of leads in each group," +" but this can be changed by clicking the :guilabel:`Measures` button, and " +":ref:`selecting another option ` from the resulting drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"The Graph View displays the analysis as a Bar Chart, Line Chart, or Pie " +"Chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:308 +msgid "" +"When using a bar chart in this view, consider deselecting the " +":guilabel:`Stacked` option, in order to make the breakdown of results more " +"legible." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:311 +#: ../../content/applications/sales/crm/performance/win_loss.rst:512 +msgid "Pivot View" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:313 +msgid "" +"The pivot view displays the results of the analysis as a table. By default, " +"the table groups the results by the stages of the sales pipeline, and " +"measures :guilabel:`Expected Revenue`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:316 +msgid "" +"The pivot view is useful for analyzing more detailed numbers than the graph " +"view can handle, or for adding the data to a spreadsheet, where custom " +"formulas can be set up, like in an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Pivot View displays the analysis as a table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:324 +msgid "" +"The three icons at the top-left of the page perform the following functions:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:332 +msgid "" +"The :guilabel:`Stage` grouping cannot be removed, but the measurement can be" +" changed by clicking the :guilabel:`Measures` button, and selecting another " +"option." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:335 +msgid "Cohort View" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:337 +msgid "" +"The cohort view displays the analysis as periods of time (cohorts) that can " +"be set to days, weeks, months, or years. By default, :guilabel:`Week` is " +"selected." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:340 +msgid "" +"This view option is useful specifically for comparing how long it has taken " +"to close leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Cohort View displays the analysis as individual weeks of the year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:346 +msgid "" +"From left-to-right, top-to-bottom, the columns in the chart represent the " +"following:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:348 +msgid "" +":guilabel:`Created On`: rows in this column represent the weeks of the year," +" in which records matching the search criteria exist." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:351 +msgid "" +"When set to :guilabel:`Week`, a row with the label :guilabel:`W52 2023` " +"means the results occurred in: Week 52 of the Year 2023." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:353 +msgid "" +":guilabel:`Measures`: the second column in the chart is the measurement of " +"the results. By default, it is set to :guilabel:`Count`, but can be changed " +"by clicking the :guilabel:`Measures` button, and selecting an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:356 +msgid "" +":guilabel:`Closed Date - By Day/Week/Month/Year`: this column looks at what " +"percentage of the measured results were closed in subsequent " +"days/weeks/months/years." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:358 +msgid "" +":guilabel:`Average`: this row provides the average of all other rows in the " +"column." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:360 +msgid "" +"The cohort view can also be downloaded as an Excel file, by clicking the " +":guilabel:`Download` icon in the top-left of the page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:363 +#: ../../content/applications/sales/crm/performance/win_loss.rst:537 +msgid "List View" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:365 +msgid "" +"The list view displays a single list of all leads matching the search " +"criteria. Clicking a lead opens the record for closer review. Additional " +"details such as :guilabel:`Country`, :guilabel:`Medium`, and more can be " +"added to the list, by clicking the :guilabel:`Filters` icon in the top-right" +" of the list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:370 +msgid "This view option is useful for reviewing many records at once." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"The List View displays a single list of all records matching the search " +"criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:376 +msgid "" +"Clicking the :guilabel:`⚙️ (gear)` icon opens the Actions drop-down menu, " +"with options for the following:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:379 +msgid "" +":guilabel:`Import records`: opens a page for uploading a spreadsheet of " +"data, as well as a template spreadsheet to easily format that data." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:381 +msgid ":guilabel:`Export All`: downloads the list as an xlsx file for Excel." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:382 +msgid "" +":guilabel:`Knowledge`: inserts a view of, or link to, the list in an article" +" in the *Knowledge* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:384 +msgid "" +":guilabel:`Dashboard`: adds the list to *My Dashboard* in the *Dashboards* " +"app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:385 +msgid "" +":guilabel:`Spreadsheet`: links to, or inserts, the list in a spreadsheet in " +"the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:389 +msgid "" +"On the list view, clicking :guilabel:`New` closes the list, and opens the " +"*New Quotation* page. Clicking :guilabel:`Generate Leads` opens a pop-up " +"window for lead generation. Neither feature is intended to manipulate the " +"list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:396 +msgid "Create reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:398 +msgid "" +"After understanding how to :ref:`navigate the pipeline analysis page " +"`, the :guilabel:`Pipeline Analysis` page can be used to " +"create and share different reports. Between the pre-made options and custom " +"filter and groupings, almost any combination is possible." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:402 +msgid "" +"Once created, reports can be :ref:`saved to favorites, shared with other " +"users, and/or added to dashboards and spreadsheets `." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:405 +msgid "" +"A few common reports that can be created using the :guilabel:`Pipeline " +"Analysis` page are detailed below." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:411 +msgid "Win/Loss reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:413 +msgid "" +"Win/Loss is a calculation of active or previously active leads in a pipeline" +" that were either marked as **Won** or **Lost** over a specific period of " +"time. By calculating opportunities won over opportunities lost, teams can " +"clarify key performance indicators (KPIs) that are converting leads into " +"sales, such as specific teams or team members, certain marketing mediums or " +"campaigns, and so on." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:419 +msgid "" +"\\begin{equation}\n" +"Win/Loss Ratio = \\frac{Opportunities Won}{Opportunities Lost}\n" +"\\end{equation}\n" +"\n" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:424 +msgid "" +"A win/loss report filters the leads from the past year, whether won or lost," +" and groups the results by their stage in the pipeline. Creating this report" +" requires a custom filter, and grouping the results by :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The search criteria for win/loss reports is Created On, Stage, and Active is" +" in true false." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:432 +msgid "Follow the steps below to create a win/loss report:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:434 +msgid "Navigate to :menuselection:`CRM app --> Reporting --> Pipeline`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:435 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " +"arrow)` icon, next to the search bar, to open a drop-down menu of filters " +"and groupings." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Search menu containing the filters for a basic win/loss report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:442 +msgid "" +"In drop-down menu that appears, under the :guilabel:`Group By` heading, " +"click :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:443 +msgid "" +"Under the :guilabel:`Filters` heading, click :guilabel:`Add Custom Filter` " +"to open another pop-up menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:445 +msgid "" +"In the :guilabel:`Add Custom Filter` pop-up menu, click on the first field " +"in the :guilabel:`Match any of the following rules:` section. By default, " +"this field displays :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:448 +msgid "" +"Clicking that first field reveals a sub-menu with numerous options to choose" +" from. From this sub-menu, locate and select the :guilabel:`Active` option. " +"Doing so automatically populates the remaining fields." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:452 +msgid "" +"The first field reads: :guilabel:`Active`. The second field reads: " +":guilabel:`is`. And lastly, the third field reads: :guilabel:`set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:455 +msgid "In total, the rule reads: :guilabel:`Active is set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:456 +msgid "" +"Click :guilabel:`New Rule`, change the first field to :guilabel:`Active`, " +"and the last field to :guilabel:`not set`. In total, the rule reads " +":guilabel:`Active is not set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:458 +#: ../../content/applications/sales/crm/performance/win_loss.rst:640 +msgid "Click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The Add Custom Filter menu showing two rules: (1) Active is set, and (2) " +"Active is not set." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:464 +msgid "" +"The report now displays the total :guilabel:`Count` of leads, whether " +"\"Won\" or \"Lost,\" grouped by their stage in the CRM pipeline. Hover over " +"a section of the report to see the number of leads in that stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"A basic win/loss report showing all leads whether won or lost grouped by " +"stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:473 +msgid "Customize win/loss reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:475 +msgid "" +"After :ref:`creating a win/loss report `, consider using " +"the options below to customize the report for different needs." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:479 +msgid "" +"A sales manager might group wins and losses by salesperson, or sales team, " +"to see who has the best conversion rate. Or, a marketing team might group by" +" sources, or medium, to determine where their advertising has been most " +"successful." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:485 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:487 +msgid "" +"To add more filters and groups, click the :guilabel:`⬇️ (down arrow)` icon, " +"next to the search bar, and select one or more options from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:490 +msgid "Some useful options include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:492 +msgid "" +":guilabel:`Created on`: adjusting this filter to a different period of time," +" such as the last 30 days, or the last quarter, can provide more timely " +"results." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:494 +msgid "" +":guilabel:`Add Custom Filter`: clicking this option, and scrolling through " +"the numerous options in the drop-down menu, opens up additional search " +"criteria, like :guilabel:`Last Stage Update` or :guilabel:`Lost Reason`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:497 +msgid "" +":guilabel:`Add Custom Group > Active`: Clicking :menuselection:`Add Custom " +"Group --> Active` separates the results into **Won** (:guilabel:`true`) or " +"**Lost** (:guilabel:`false`). This shows at what stage leads are being " +"marked **Won** or **Lost**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:500 +msgid "" +":guilabel:`Multiple Groupings`: add multiple :guilabel:`Group By` selections" +" to split results into more relevant and manageable chunks." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:503 +msgid "" +"Adding :guilabel:`Salesperson` or :guilabel:`Sales Team` breaks up the total" +" count of leads in each :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:505 +msgid "" +"Adding :guilabel:`Medium` or :guilabel:`Source` can reveal what marketing " +"avenues generate more sales." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Search menu open and the Won and Lost filters highlighted." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:514 +msgid "" +"By default, pivot view groups win/loss reports by :guilabel:`Stage` and " +"measures :guilabel:`Expected Revenue`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:517 +msgid "To flesh out the table:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:519 +msgid "Click the :guilabel:`⬇️ (down arrow)` next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:520 +msgid "" +"In the pop-up menu, replace the :guilabel:`Stage` grouping with something " +"like :guilabel:`Salesperson` or :guilabel:`Medium`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:522 +msgid "" +"Click the :guilabel:`Measures` button and click :guilabel:`Count` to add the" +" number of leads back into the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:525 +msgid "" +"Other useful measures for pivot view include :guilabel:`Days to Assign` and " +":guilabel:`Days to Close`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "A win/loss report in Pivot View displays the data in table form." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:533 +msgid "" +"In pivot view, the :guilabel:`Insert In Spreadsheet` button may be greyed " +"out due to the report containing :guilabel:`duplicate group bys`. To fix " +"this, replace the :guilabel:`Stage` grouping in the search bar with another " +"option." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:539 +msgid "In list view, a win/loss report displays all leads on a single page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:541 +msgid "" +"To better organize the list, click the :guilabel:`⬇️ (down arrow)` next to " +"the search bar, and add more relevant groupings or re-organize the existing " +"ones. To re-order the nesting, remove all :guilabel:`Group By` options and " +"re-add them in the desired order." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:545 +msgid "To add more columns to the list:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:547 +msgid "Click the :guilabel:`Filters` icon in the top-right of the page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:548 +msgid "" +"Select options from the resulting drop-down menu. Some useful filters " +"include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:550 +msgid "**Campaign**: Shows the marketing campaign that originated each lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:551 +msgid "" +"**Medium**: Shows the marketing medium (Banner, Direct, Email, Google " +"Adwords, Phone, Website, etc.) that originated each lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:553 +msgid "" +"**Source**: Shows the source of each lead (Newsletter, Lead Recall, Search " +"Engine, etc.)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"A win/loss report in List View displays all leads in an easy-to-read list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:562 +msgid "Save and share reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:564 +msgid "" +"After :ref:`creating a report `, the search criteria can " +"be saved, so the report does not need to be created again in the future. " +"Saved searches automatically update their results every time the report is " +"opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:568 +msgid "" +"Additionally, reports can be shared with others, or added to " +"spreadsheets/dashboards for greater customization and easier access." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:573 +msgid "Save to Favorites" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:575 +msgid "To save a report for later:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:577 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " +"arrow)` icon, next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:579 +msgid "" +"In the drop-down menu that appears, under the :guilabel:`Favorites` heading," +" click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:581 +msgid "In the next drop-down menu that appears, enter a name for the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:583 +msgid "" +"Checking the :guilabel:`Default filter` box sets this report as the default " +"analysis when the :guilabel:`Pipeline Analysis` page is accessed." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:585 +msgid "" +"Checking the :guilabel:`Shared` box makes this report available to other " +"users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:587 +msgid "" +"Finally, click :guilabel:`Save`. The report is now saved under the " +":guilabel:`Favorites` heading." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"Under the Favorites heading, click Save current search and save the report " +"for later." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:594 +msgid "Add to a Spreadsheet" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:596 +msgid "" +"Inserting a report into a spreadsheet not only saves a copy of the report, " +"it allows users to add charts and formulas like in an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:599 +msgid "To save a report as a spreadsheet:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:601 +msgid "**In Graph or Pivot View**:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:603 +msgid "Click the :guilabel:`Insert in spreadsheet` button." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:604 +msgid "In the pop-up menu that appears, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:606 +msgid "**In Cohort or List View**:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:608 +msgid "Click the :guilabel:`⚙️ (gear)` icon." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:609 +msgid "" +"In the drop-down menu that appears, hover over :guilabel:`Spreadsheet`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:610 +msgid "" +"In the next drop-down menu, click either :guilabel:`Insert in spreadsheet` " +"or :guilabel:`Link in spreadsheet`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:613 +msgid "Saved reports are viewable in the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"Pivot View reports especially benefit from being inserted in spreadsheets." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:620 +msgid "" +"After modifying a spreadsheet and adding additional formulas, consider then " +"adding the entire spreadsheet to a dashboard. Using this method, the " +"spreadsheet can be added to a public dashboard instead of only :guilabel:`My" +" Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:624 +msgid "Click :menuselection:`File --> Add to dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:625 +msgid "" +"In the pop-up menu that appears, name the spreadsheet and select a " +":guilabel:`Dashboard Section` to house the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:627 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:629 +msgid "Add to a Dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:631 +msgid "" +"Adding a report to a dashboard saves it for later and makes it easy to view " +"alongside the rest of :guilabel:`My Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:634 +msgid "To add a report to :guilabel:`My dashboard`:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:636 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⚙️ (gear)` " +"icon." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:637 +msgid "In the drop-down menu that appears, hover over :guilabel:`Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:638 +msgid "" +"In the :guilabel:`Add to my dashboard` drop-down menu, enter a name for the " +"report (by default, it is named :guilabel:`Pipeline`)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:642 +msgid "To view a saved report:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:644 +msgid "" +"Return to the main apps page, and navigate to :menuselection:`Dashboards app" +" --> My Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"To access the saved report, open the Dashboard app and click My Dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:652 +msgid ":doc:`../acquire_leads/convert`" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:653 +msgid ":doc:`../acquire_leads/send_quotes`" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:654 +msgid ":doc:`../pipeline/lost_opportunities`" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline.rst:5 +msgid "Organize the pipeline" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:3 +msgid "Manage lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 +msgid "" +"Not all opportunities result in successful sales. In order to keep the " +"pipeline up to date, lost opportunities need to be identified. Specifying " +"the reason why an opportunity was lost provides additional insight that can " +"prove useful for future opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 +msgid "Mark a lead as lost" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 +msgid "" +"To mark a lead as lost, open the :menuselection:`CRM` application, and " +"select a lead from the pipeline, by clicking on its corresponding kanban " +"card. Doing so reveals that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 +msgid "" +"Then, click :guilabel:`Lost`, located at the top of the lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "" +"Buttons from the top of an opportunity record with the lost button " +"emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 +msgid "" +"This opens the :guilabel:`Lost Reason` popup. From the drop-down, choose an " +"existing lost reason. If no applicable reason is available, create a new one" +" by entering it into the :guilabel:`Lost Reason` field, and clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 +msgid "" +"Additional notes and comments can be added below the lost reason designated " +"in the :guilabel:`Lost Reason` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 +msgid "" +"When all the desired information has been entered in the :guilabel:`Lost " +"Reason` pop-up window, click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Lost reasons popup with sample reasons." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 +msgid "" +"Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo " +"returns to the lead detail form, where a new red :guilabel:`Lost` banner is " +"now present in the upper-right corner of the lead." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 +msgid "Create/edit lost reasons" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 +msgid "" +"To create a new lost reason, or edit an existing one, navigate to " +":menuselection:`CRM app --> Configuration --> Lost Reasons`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 +msgid "" +"To edit an existing reason, click on the reason that should be modified. " +"When clicked, that reason becomes highlighted. Once highlighted, change the " +"description of the selected lost reason by editing the " +":guilabel:`Description` field. When done, click :guilabel:`Save` in the " +"upper-left corner." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 +msgid "" +"To create a new lost reason, click :guilabel:`Create` in the upper-left " +"corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank " +"line in the :guilabel:`Description` field. Then, proceed to type in the new " +"lost reason in that new line. Once ready, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 +msgid "Retrieve lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 +msgid "" +"To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM " +"app` to the main :guilabel:`Pipeline` dashboard. Then, click the " +":guilabel:`Filters` drop-down menu, located beneath the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Search bar with lost filter emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +msgid "" +"From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` " +"option. Upon selecting :guilabel:`Lost`, only the leads that have been " +"marked as `Lost` appear on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 +msgid "" +"To filter leads by a specific lost reason, select :menuselection:`Filters " +"--> Add Custom Filter`. Doing so reveals another drop-down menu with three " +"fields." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 +msgid "" +"In the top field drop-down menu, select :guilabel:`Lost Reason`. In the " +"second field drop-down menu, select :guilabel:`Contains`. Then, in the third" +" field of the :guilabel:`Add Custom Field` sub menu, type in the specific " +"keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking " +":guilabel:`Apply`, Odoo reveals all the lost leads with a reason that " +"contains that specified keyword(s)." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Search bar with custom filter added for lost reason." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 +msgid "" +"To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` " +"dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and" +" select the :guilabel:`Lost` option. Doing so reveals all the lost " +"opportunities on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 +msgid "" +"Then, click on the kanban card of the desired lost opportunity to restore, " +"which opens that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +msgid "" +"From the lost lead's detail form, click :guilabel:`Restore` in the upper-" +"left corner. Doing so removes the red :guilabel:`Lost` banner from the lead " +"form, signifying the lead has been restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Lost opportunity with emphasis on the Restore button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 +msgid "Restore multiple opportunities at once" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 +msgid "" +"To restore multiple opportunities at once, navigate to the main " +":guilabel:`Pipeline` dashboard in the *CRM* app, open the " +":guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 +msgid "" +"Next, select the list view option, which is represented by the three-line " +":guilabel:`☰ (list)` icon in the upper-right corner. Doing so places all the" +" leads from the :guilabel:`Pipeline` page in a list form. With the list form" +" chosen, select the checkbox to the left of each desired opportunity/lead to" +" be restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 +msgid "" +"Once the desired opportunities/leads have been selected, click the " +":guilabel:`⚙️ Action (gear)` drop-down menu at the top of the " +":guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down " +"menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 +msgid "" +"Doing so removes those selected lost opportunities from the " +":guilabel:`Pipeline` page because they no longer fit into the `Lost` filter " +"criteria. To reveal these newly-restored leads, delete the `Lost` filter " +"from the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Action button from list view with the Unarchive option emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 +msgid ":doc:`../performance/win_loss`" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 +msgid "Multiple sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 +msgid "" +"Use the *Sales Teams* feature to manage several sales teams, departments, or" +" channels, each with their own unique sales processes." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 +msgid "Create a new sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 +msgid "" +"To create a new sales team, go to :menuselection:`CRM --> Configuration --> " +"Sales Teams`, then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 +msgid "" +"On the creation page, set an :guilabel:`Email Alias` to automatically " +"generate a lead/opportunity for this sales team every time a message is sent" +" to that unique email address. Choose whether to accept emails from " +":guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or " +":guilabel:`Followers Only`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 +msgid "" +"Set an :guilabel:`Invoicing Target` if this team has specific monthly " +"revenue goals. Set a :guilabel:`Domain` to assign leads/opportunities to " +"this sales team based on specific filters, such as country, language, or " +"campaign." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Create a sales team in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 +msgid "Add members to a sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 +msgid "" +"To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab" +" when editing the sales team's configuration page. Select a salesperson from" +" the drop-down menu or create new salesperson. Set a maximum number of leads" +" that can be assigned to this salesperson in a 30-day period to ensure that " +"they do not overwork." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Add a salesperson in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 +msgid "" +"One person can be added as a team member or :guilabel:`Team Leader` to " +"multiple sales teams, allowing them to access all of the pipelines that they" +" need to." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 +msgid "Sales team dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 +msgid "" +"To view the sales team dashboard, go to :menuselection:`CRM --> Sales --> " +"Teams`. Odoo users will see any teams that they are a part of as dashboard " +"tiles." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 +msgid "" +"Each tile gives an overview of the sales team's open opportunities, " +"quotations, sales orders, and expected revenue, as well as a bar graph of " +"new opportunities per week and an invoicing progress bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Sales team overview dashboard in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 +msgid "" +"Click on the three dots in the corner of a tile to open a navigational menu " +"that lets users quickly view documents or reports, create new quotations or " +"opportunities, pick a color for this team, or access the team's " +"configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "" +"Click the Three Dot Menu in Odoo CRM dashboard to view documents and create " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 +msgid "" +"Click on the :guilabel:`Pipeline` button to go directly to that team's CRM " +"pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads.rst:5 +msgid "Assign and track leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 +msgid "Assign leads with predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 +msgid "" +"The Odoo *CRM* app can automatically assign leads/opportunities to sales " +"teams and salespeople. A standard practice is to assign leads based on the " +"probability of winning each lead. Companies can prioritize the leads that " +"are more likely to result in successful deals by quickly assigning them to " +"the appropriate salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 +msgid "" +"Odoo automatically calculates the probability of winning each lead using a " +"method called *predictive lead scoring*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 +msgid "Predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16 +msgid "" +"Predictive lead scoring is a machine-learning model that uses historical " +"data from Odoo *CRM* to score open leads/opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 +msgid "" +"As a company processes opportunities through the CRM pipeline, Odoo collects" +" data on which opportunities are won and lost. Predictive lead scoring uses " +"this data to predict the probability of winning each new lead or " +"opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 +msgid "" +"The more opportunities that are sent through the CRM pipeline, the more data" +" Odoo collects, resulting in more accurate probabilities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 +msgid "" +"Specifically, Odoo's predictive lead scoring uses the *naive Bayes* " +"probability model:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:28 +msgid "" +"\\begin{equation}\n" +"P(A | B) = \\frac{P(A) \\times P(B | A)}{P(B)}\n" +"\\end{equation}\n" +"\n" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 +msgid "" +"The probability of success of each opportunity is displayed on the " +"opportunity form, and it updates automatically as the opportunity progresses" +" through the CRM pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The probability of success displayed on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +msgid "" +"When an opportunity moves to the next stage, its probability of success " +"automatically increases according to the predictive lead scoring algorithm." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 +msgid "" +"Predictive lead scoring is always active in Odoo *CRM*. However, the " +"variables used to calculate the probability of success can be customized in " +"the settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 +msgid "" +"To customize the variables used by predictive lead scoring, go to " +":menuselection:`CRM --> Configuration --> Settings`. Under " +":guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update " +"Probabilities` button." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 +msgid "" +"Then, click on the drop-down menu to choose which variables the predictive " +"lead scoring feature will take into account." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The Update Probabilities window in the Predictive Lead Scoring settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +msgid "Any number of the following variables can be activated:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +msgid "" +":guilabel:`State`: the geographical state from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 +msgid "" +":guilabel:`Country`: the geographical country from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 +msgid "" +":guilabel:`Phone Quality`: whether or not a phone number is listed for the " +"opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +msgid "" +":guilabel:`Email Quality`: whether or not an email address is listed for the" +" opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 +msgid "" +":guilabel:`Source`: the source of an opportunity (e.g. search engine, social" +" media)" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 +msgid ":guilabel:`Language`: the spoken language specified on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 +msgid ":guilabel:`Tags`: the tags placed on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 +msgid "" +"The variables `Stage` and `Team` are always in effect. `Stage` refers to the" +" CRM pipeline stage that an opportunity is in. `Team` refers to the sales " +"team that is assigned to an opportunity. Predictive lead scoring *always* " +"takes into account these two variables, regardless of which optional " +"variables are selected." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 +msgid "" +"Next, click on the date field next to the option :guilabel:`Consider leads " +"created as of the:` to select the date from which predictive lead scoring " +"will begin its calculations." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 +msgid "Lastly, click :guilabel:`Confirm` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 +msgid "Change the probability manually" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 +msgid "" +"An opportunity's probability of success can be changed manually on the " +"opportunity form. Click on the probability number to edit it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 +msgid "" +"Manually changing the probability removes the automatic probability updates " +"for that opportunity. The probability will no longer update automatically as" +" the opportunity moves through each stage of the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 +msgid "" +"To reactivate automatic probability, click on the gear icon next to the " +"probability percentage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The gear icon used to reactivate automatic probability on an opportunity " +"form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 +msgid "Assign leads based on probability" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 +msgid "" +"Odoo *CRM* can assign leads/opportunities to sales teams and salespeople " +"based on specified rules. Create assignment rules based on the leads' " +"probability of success to prioritize those that are more likely to result in" +" deals." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 +msgid "Configure rule-based assignment" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 +msgid "" +"To activate *rule-based assignment*, navigate to :menuselection:`CRM --> " +"Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 +msgid "" +"The rule-based assignment feature can be set to run :guilabel:`Manually`, " +"meaning an Odoo user must manually trigger the assignment, or " +":guilabel:`Repeatedly`, meaning Odoo will automatically trigger the " +"assignment according to the chosen time period." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 +msgid "" +"To set up automatic lead assignment, select :guilabel:`Repeatedly` for the " +":guilabel:`Running` section. Then, customize how often Odoo will trigger the" +" automatic assignment in the :guilabel:`Repeat every` section." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The Rule-Based Assignment setting in CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 +msgid "" +"If rule-based assignment is set to run :guilabel:`Repeatedly`, the " +"assignment can still be triggered manually using the circular arrow icon in " +"the :guilabel:`Rule-Based Assignment` settings (or using the " +":guilabel:`Assign Leads` button on the sales team configuration page)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +msgid "Configure assignment rules" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 +msgid "" +"Next, configure the *assignment rules* for each sales team and/or " +"salesperson. These rules determine which leads Odoo assigns to which people." +" To get started, navigate to :menuselection:`CRM --> Configuration --> Sales" +" Teams`, and select a sales team." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 +msgid "" +"On the sales team configuration form, under :guilabel:`Assignment Rules`, " +"click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to " +"determine lead assignment for this sales team. The rules can include " +"anything that may be relevant for this company or team, and any number of " +"rules can be added." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 +msgid "" +"Click :guilabel:`Add Filter` to start creating assignment rules. Click on " +"the :guilabel:`+` sign on the right of the assignment rule to add another " +"line. Click on the :guilabel:`x` symbol to remove the line." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 +msgid "" +"To create an assignment rule based on an opportunity's probability of " +"success, click on the far left drop-down menu of an assignment rule line, " +"and select :guilabel:`Probability`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 +msgid "" +"From the middle drop-down menu, select the desired equation symbol—most " +"likely the symbol for *greater than*, *less than*, *greater than or equal " +"to*, or *less than or equal to*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 +msgid "" +"In the far right space, enter the desired number value of the probability. " +"Finally, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 +msgid "" +"To configure an assignment rule such that a sales team receives leads that " +"have a probability of success of 20% or greater, create a :guilabel:`Domain`" +" line that reads: `Probability >= 20`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:0 +msgid "" +"Sales team domain set to probability greater than or equal to twenty " +"percent." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 +msgid "" +"Separate assignment rules can also be configured for individual team " +"members. From the sales team configuration page, click on a team member in " +"the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click" +" :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 +msgid "" +"If automatic lead assignment is configured in the settings, both the sales " +"team and individual team members have the option to :guilabel:`Skip auto " +"assignment`. Check this box to omit a particular sales team or salesperson " +"from being assigned leads automatically by Odoo's rule-based assignment " +"feature. If :guilabel:`Skip auto assignment` is activated, the sales team or" +" salesperson can still be assigned leads manually." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 +msgid "" +"To manually assign leads to this sales team, click on the :guilabel:`Assign " +"Leads` button at the top of the sales team configuration page. This will " +"assign any leads that are currently unassigned and match this team's " +"specified domain." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:3 +msgid "Track your prospects visits" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5 +msgid "" +"Tracking your website pages will give you much more information about the " +"interests of your website visitors." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8 +msgid "" +"Every tracked page they visit will be recorded on your lead/opportunity if " +"they use the contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14 +msgid "" +"To use this feature, install the free module *Lead Scoring* under your " +"*Apps* page (only available in Odoo Enterprise)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21 +msgid "Track a webpage" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23 +msgid "" +"Go to any static page you want to track on your website and under the " +"*Promote* tab you will find *Optimize SEO*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29 +msgid "There you will see a *Track Page* checkbox to track this page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35 +msgid "See visited pages in your leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37 +msgid "" +"Now each time a lead is created from the contact form it will keep track of " +"the pages visited by that visitor. You have two ways to see those pages, on " +"the top right corner of your lead/opportunity you can see a *Page Views* " +"button but also further down you will see them in the chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43 +msgid "" +"Both will update if the viewers comes back to your website and visits more " +"pages." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52 +msgid "" +"The feature will not repeat multiple viewings of the same pages in the " +"chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55 +msgid "Your customers will no longer be able to keep any secrets from you!" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:6 +msgid "Point of Sale" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:8 +msgid "" +"With **Odoo Point of Sale**, run your shops and restaurants easily. The app " +"works on any device with a web browser, even if you are temporarily offline." +" Product moves are automatically registered in your stock, you get real-time" +" statistics, and your data is consolidated across all shops." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:13 +msgid "" +"`Odoo Tutorials: Point of Sale Tutorials `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:14 +msgid ":doc:`IoT Boxes Documentations `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:19 +msgid "Start a session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:21 +msgid "" +"From the **POS dashboard**, click :guilabel:`New Session`, and at the " +":guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to " +"start a POS session, or click :guilabel:`Continue Selling` if the session is" +" already opened." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:26 +msgid "" +":doc:`Multiple users ` can be logged into the " +"same session at the same time. However, the session can only be opened once " +"on the same browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:32 +msgid "Sell products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:34 +msgid "" +"Click on products to add them to the cart. To change the **quantity**, click" +" :guilabel:`Qty` and enter the number of products using the keypad. To add a" +" **discount** or modify the product **price**, click respectively " +":guilabel:`% Disc` or :guilabel:`Price` and enter the amounts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:38 +msgid "" +"Once an order is completed, proceed to checkout by clicking " +":guilabel:`Payment`. Select the **payment method**, enter the received " +"amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move " +"on to the next customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "POS session interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:46 +msgid "You can use both `,` and `.` on your keyboard as decimal separators." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:47 +msgid "" +"**Cash** is selected by default if you enter the amount without choosing a " +"payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:52 +msgid "Set customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:54 +msgid "" +"Registering your customer is necessary to :doc:`collect their loyalty points" +" and grant them rewards `, automatically " +"apply the :doc:`attributed pricelist `, or" +" :ref:`generate and print an invoice `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:59 +msgid "" +"You can create customers from an :ref:`open POS session `" +" by clicking :menuselection:`Customer --> Create`, and filling in the " +"contact information. You can also create customers from the backend by going" +" to :menuselection:`Point of Sale --> Orders --> Customers` and clicking " +":guilabel:`New`. Then, fill in the information and save." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:64 +msgid "" +"To set a customer during an order, access the list of customers by clicking " +":guilabel:`Customer` on the POS interface. You can also set a customer at " +"the payment screen by clicking :guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:71 +msgid "Customer notes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:73 +msgid "" +"You can add **customer notes** about specific products directly from an open" +" :ref:`POS session `. For instance, to provide cleaning " +"and maintenance tips. They can also be used to track a customer's particular" +" request, such as not wanting the product to be assembled for them." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:77 +msgid "" +"To do so, select a product and click :guilabel:`Customer Note` on the pad. " +"Doing so opens a pop-up window in which you can add or modify content for " +"the note." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:81 +msgid "" +"Product notes from an :doc:`imported SO ` " +"are displayed identically in the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer note button and notes (SO and POS session) on products in the cart" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:87 +msgid "" +"Customer notes appear on customers' receipts and invoices similarly to how " +"they appear in the cart, under the related product." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer receipt with notes from an SO and from the customer note feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:96 +msgid "Return and refund products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:98 +msgid "To return and refund a product," +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:100 +msgid ":ref:`start a session ` from the **POS dashboard**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:101 +msgid "click :guilabel:`Refund` and select the corresponding order;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:102 +msgid "select the product and the quantity to refund using the keypad;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:103 +msgid "click :guilabel:`Refund` to go back to the previous screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:104 +msgid "" +"once the order is completed, click :guilabel:`Payment` to proceed to the " +"refund;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:105 +msgid "" +"click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next " +"customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "refund view from a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:111 +msgid "" +"You can filter the **orders list** by :guilabel:`Receipt Number`, " +":guilabel:`Date` or :guilabel:`Customer` using the search bar." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:113 +msgid "" +"You can also refund a product by selecting the returned product from an open" +" session, and setting a negative quantity that equals the number of returned" +" products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by " +"the quantity of returned products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:120 +msgid "Manage the cash register" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:122 +msgid "" +"To add or take out cash from the register, click the **menu icon** in the " +"upper right corner of your screen and :guilabel:`Cash In/Out`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Dropdown menu to close a POS session, reach the backend, add or take cash out or check\n" +"orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:129 +msgid "" +"Doing so opens a pop-up window on which you can select :guilabel:`Cash In` " +"or :guilabel:`Cash Out`, enter the amount and the reason, and click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:135 +msgid "Close the POS session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:137 +msgid "" +"To close your session, click the **menu icon** in the upper right corner of " +"your screen and :guilabel:`Close Session`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:140 +msgid "" +"Doing so opens the :guilabel:`Closing Control` pop-up screen. From this " +"screen, you can retrieve various information:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:143 +msgid "" +"the number of orders made and the total amount made during the session;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:144 +msgid "the expected amounts grouped by payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:146 +msgid "" +"Before closing this window, count your cash using the calculator icon. Doing" +" so opens a pop-up window that computes the total amount in the cash drawer " +"depending on the coins and bills counted and added manually. Then, click " +":guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed" +" amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money " +"Details` are specified in the **Notes** section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "How to close a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:155 +msgid "" +"Once you are done controlling the amounts, click :guilabel:`Close Session` " +"to close and go back to the **POS dashboard**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:159 +msgid "" +"To reach the backend without closing the session, click :guilabel:`Backend` " +"on the dropdown menu." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:161 +msgid "To abort, click :guilabel:`Discard` on the pop-up window." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:162 +msgid "" +"Depending on your setup, you might only be allowed to close a session if the" +" expected cash revenue equals the counted cash. To close it anyway, click " +":guilabel:`Ok` on the :guilabel:`Payments Difference` screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:167 +msgid "" +"It is strongly advised to close your POS session at the end of each day." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:168 +msgid "" +"To look at all your previous sessions, go to :menuselection:`Point of Sale " +"--> Orders --> Sessions`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:11 +msgid "Access POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:13 +msgid "" +"To access the general POS settings, go to :menuselection:`Point of Sale --> " +"Configuration --> Settings`. Then, open the dropdown menu in the " +":guilabel:`Point of Sale` field and select the POS to configure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "Dropdown menu to select the POS in the app settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:21 +msgid "" +"These settings are available to users with the :doc:`access rights " +"` :guilabel:`Administration` set " +"as :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:25 +msgid "" +"You can also configure some settings from the dashboard by clicking the " +"vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a " +"popup window, from which you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:28 +msgid ":doc:`Enable multiple employees to log in. `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:29 +msgid "" +":doc:`Connect and set up an IoT box. <../../productivity/iot/config/pos>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:30 +msgid ":doc:`Connect and set up an ePOS printer. `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "popup window to access quick settings in POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:36 +msgid "" +"These settings are available to users with the :doc:`access rights " +"` :guilabel:`Point of Sale` set as" +" :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:41 +msgid "Make products available" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:43 +msgid "" +"To make products available for sale, go to :menuselection:`Point of Sale -->" +" Products --> Products`, and select a product to open the product form. In " +"the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "Making a product available in your POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 +msgid "Self-signed certificate for ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 +msgid "" +"ePOS printers are designed to work seamlessly with Point of Sale systems. " +"Once connected, the two devices automatically share information, enabling " +"the direct printing of tickets from the POS system to the ePOS printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 +msgid "" +"These `Epson ePOS printers `_ are compatible with " +"Odoo:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 +msgid "TM-H6000IV-DT (Receipt printer only)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 +msgid "TM-T70II-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 +msgid "TM-T88V-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 +msgid "TM-L90-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 +msgid "TM-T20II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 +msgid "TM-T70-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 +msgid "TM-T82II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 +msgid "TM-T83II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 +msgid "TM-T88V-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 +msgid "TM-U220-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 +msgid "TM-m10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 +msgid "TM-m30" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 +msgid "TM-P20 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 +msgid "TM-P60II (Receipt: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 +msgid "TM-P60II (Peeler: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 +msgid "TM-P80 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 +msgid "" +"To work with Odoo, some models that can be used without an :doc:`IoT box " +"<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " +"protocol ` to establish a secure connection between the browser and " +"the printer. However, trying to reach the printer's IP address using HTTPS " +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection `, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 +msgid "" +"The connection is lost after closing the browser window. Therefore, this " +"method should only be used as a **workaround** or as a pre-requisite for the" +" :ref:`following instructions `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 +msgid "Generate, export, and import self-signed certificates" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 +msgid "" +"For a long-term solution, you must generate a **self-signed certificate**. " +"Then, export and import it into your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 +msgid "" +"**Generating** an SSL certificate should only be done **once**. If you " +"create another certificate, devices using the previous one will lose HTTPS " +"access." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +msgid "Windows 10 & Linux OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191 +msgid "Generate a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 +msgid "" +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207 +msgid "" +"Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " +"section, and click :guilabel:`create` to generate a new **Self-Signed " +"Certificate**. The :guilabel:`Common Name` should be automatically filled " +"out. If not, fill it in with the printer IP address number. Select the years" +" the certificate will be valid in the :guilabel:`Validity Period` field, " +"click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " +"printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +msgid "" +"The self-signed certificate is generated. Reload the page and click " +":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " +"**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " +"Certificate` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 +msgid "Export a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 +msgid "" +"The export process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser. Start by accessing your ePOS printer settings on your web " +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225 +msgid "If you are using **Google Chrome**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 +msgid "" +"click :guilabel:`Not secure` next to the search bar, and " +":guilabel:`Certificate is not valid`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 +msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234 +msgid "" +"add `.crt` at the end of the file name to ensure it has the correct " +"extension;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235 +msgid "" +"select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " +"of the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 +msgid "save, and the certificate is exported." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 +msgid "" +"Make sure that the certificate ends with the extension `.crt`. Otherwise, " +"some browsers might not see the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243 +msgid "If you are using **Mozilla Firefox**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 +msgid "click the **lock-shaped** icon on the left of the address bar;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246 +msgid "" +"go to :menuselection:`Connection not secure --> More information --> " +"Security tab --> View certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox browser" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252 +msgid "scroll down to the :guilabel:`Miscellaneous` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253 +msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +msgid "Import a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 +msgid "" +"The import process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 +msgid "Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 +msgid "" +"Windows 10 manages certificates, which means that self-signed certificates " +"must be imported from the certification file rather than the browser. To do " +"so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +msgid "" +"open the Windows File Explorer and locate the downloaded certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 +msgid "" +"right-click on the certification file and click :guilabel:`Install " +"Certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +msgid "" +"select where to install the certificate and for whom - either for the " +":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " +"click :guilabel:`Next`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +msgid "" +"on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" +" the following store`, click :guilabel:`Browse...`, and select " +":guilabel:`Trusted Root Certification Authorities`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 +msgid "click :guilabel:`Finish`, accept the pop-up security window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 +msgid "restart the computer to make sure that the changes are applied." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 +msgid "Linux" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +msgid "open Chrome;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 +msgid "" +"go to :menuselection:`Settings --> Privacy and security --> Security --> " +"Manage certificates`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 +msgid "" +"go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " +"the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +msgid "accept all warnings;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 +msgid "click :guilabel:`ok`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +msgid "restart your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 +msgid "open Firefox;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 +msgid "" +"go to :menuselection:`Settings --> Privacy & Security --> Security --> View " +"Certificates... --> Import`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 +msgid "select the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +msgid "tick the checkboxes and validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +msgid "Mac OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +msgid "" +"On Mac OS, you can secure the connection for all browsers by following these" +" steps:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +msgid "" +"open Safari and navigate to your printer's IP address. Doing so leads to a " +"warning page;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 +msgid "" +"on the warning page, go to :menuselection:`Show Details --> visit this " +"website --> Visit Website`, validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 +msgid "reboot the printer so you can use it with any other browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +msgid "" +"To generate and export an SSL certificate and send it to IOS devices, open " +"**Google Chrome** or **Mozilla Firefox**. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240 +msgid "" +"Make sure that the certificate ends with the extension `.crt`. Otherwise, " +"some browsers might not find the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 +msgid "Android OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 +msgid "" +"To import an SSL certificate into an Android device, first create and export" +" it from a computer. Next, transfer the `.crt` file to the device using " +"email, Bluetooth, or USB. Once the file is on the device," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262 +msgid "open the settings and search for `certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263 +msgid "click :guilabel:`Certificate AC` (Install from device storage);" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264 +msgid "select the certificate file to install it on the device." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 +msgid "" +"The specific steps for installing a certificate may vary depending on the " +"version of Android and the device manufacturer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270 +msgid "iOS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 +msgid "" +"To import an SSL certificate into an iOS device, first create and export it " +"from a computer. Then, transfer the `.crt` file to the device using email, " +"Bluetooth, or any file-sharing service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276 +msgid "" +"Downloading this file triggers a warning pop-up window. Click " +":guilabel:`Allow` to download the configuration profile, and close the " +"second pop-up window. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279 +msgid "go to the **Settings App** on the iOS device;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 +msgid "click :guilabel:`Profile Downloaded` under the user's details box;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281 +msgid "locate the downloaded `.crt` file and select it;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 +msgid "click :guilabel:`Install` on the top right of the screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283 +msgid "if a passcode is set on the device, enter the passcode;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284 +msgid "" +"click :guilabel:`Install` on the top right of the certificate warning screen" +" and the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286 +msgid "click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290 +msgid "" +"The certificate is installed, but it still needs to be authenticated. To do " +"so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292 +msgid "" +"go to :menuselection:`Settings --> General --> About > Certificate Trust " +"Settings`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293 +msgid "enable the installed certificate using the **slide button**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294 +msgid "click :guilabel:`Continue` on the pop-up window." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297 +msgid "" +"If you need to export SSL certificates from an operating system or web " +"browser that has not been mentioned, search for `export SSL certificate` + " +"`the name of your browser or operating system` in your preferred search " +"engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 +msgid "" +"Similarly, to import SSL certificates from an unmentioned OS or browser, " +"search for `import SSL certificate root authority` + `the name of your " +"browser or operating system` in your preferred search engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 +msgid "Check if the certificate was imported correctly" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 +msgid "" +"To confirm your printer's connection is secure, connect to its IP address " +"using HTTPS. For example, navigate to `https://192.168.1.25` in your " +"browser. If the SSL certificate has been applied correctly, you should no " +"longer see a warning page, and the address bar should display a padlock " +"icon, indicating that the connection is secure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 +msgid "Secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 +msgid "" +"If **Direct Devices** is enabled in a Point of Sale settings (for example, " +"if you use an ePos printer), HTTP becomes the default protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 +msgid "Force your Point of Sale to use a secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 +msgid "" +"Add a new **key** in the **System Parameters** to force your Point of Sale " +"to use a secure connection with the HTTPS protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 +msgid "" +"To do so, activate the :ref:`developer mode `, go to " +":menuselection:`Settings --> Technical --> Parameters --> System " +"Parameters`, then create a new parameter, add the following values and click" +" on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 +msgid "**Key**: `point_of_sale.enforce_https`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 +msgid "**Value**: `True`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 +msgid ":doc:`epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:3 +msgid "Multi-employee management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:5 +msgid "" +"Odoo Point of Sale allows you to manage access to a specific POS by enabling" +" the **Multi Employees per Session** feature. When activated, :ref:`you can " +"select which users can log into the POS ` and :ref:`keep" +" track of the employees involved in each order `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:15 +msgid "" +":ref:`Access the POS settings ` and select your POS," +" or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and " +"click :guilabel:`Edit`. Then, enable :guilabel:`Multi Employees per " +"Session`, and add the allowed employees in the :guilabel:`Allowed Employees`" +" field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "setting to enable multiple cashiers in POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:26 +msgid "Practical application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:28 +msgid "" +"Once the feature is activated, cashiers can log in :ref:`by scanning their " +"badge ` or selecting their name from the list of " +"allowed employees to :ref:`open the session `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "window to open a session when the multiple cashiers feature is enabled" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:35 +msgid "" +"To switch to another user :ref:`from an open session `, " +"click the employee name at the top-right of the screen and select the " +"employee to swap with from the list." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "button to switch from one cashier to another." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:41 +msgid "" +"You can also require your employees to enter a pin code every time they log " +"into a POS to prevent them from logging in as someone else. To define the " +"code, go to the **Employees** app, open the employee form, and click the " +":guilabel:`HR settings` tab. Then, enter a pin code of your choice in the " +":guilabel:`PIN Code` field of the :guilabel:`Attendance/Point of Sale` " +"category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "setting on the employee form to assign a badge ID and a PIN code." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:52 +msgid "Log in using badges" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:54 +msgid "" +"For your employees to be able to log in by scanning their badge, they must " +"have a badge ID assigned. To do so, go to the **Employees** app, open the " +"employee form, and click the :guilabel:`HR settings` tab. Then, enter the " +"badge ID of your choice in the :guilabel:`Badge ID` field of the " +":guilabel:`Attendance/Point of Sale` category or click :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:59 +msgid "" +"To switch to another user, lock the session by clicking the lock-shaped icon" +" (:guilabel:`🔓`) at the top-right of the screen and scan your badge." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:65 +msgid "Analytics" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:67 +msgid "" +"Once you close and post the POS session, access the comprehensive report to " +"review all session activities, including who initiated the session and who " +"handled specific orders. To access the session's report, click the vertical " +"ellipsis button (:guilabel:`⋮`) on the POS card and select " +":guilabel:`Sessions` from the :guilabel:`View` section. Then, select a " +"specific session for more detailed information, and click the " +":guilabel:`Orders` button to view a list of all orders placed during that " +"session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:74 +msgid "" +"To get an overview of all orders, regardless of the session, click the " +"vertical ellipsis button (:guilabel:`⋮`) on the POS card and select " +":guilabel:`Orders` from the :guilabel:`View` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 +msgid "Payment methods" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:7 +msgid "" +"To add a payment method, you first need to create it. Go to " +":menuselection:`Point of Sale --> Configuration --> Payment Methods --> " +"New`, and set a name. Check :guilabel:`Identify Customer` to allow this " +"payment method *exclusively* for registered customers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:11 +msgid "" +"Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this " +"payment method for cash payments, or :guilabel:`Bank` to use it for card " +"payments." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst-1 +msgid "Creating a new payment method for a POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 +msgid "" +"Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a" +" Payment Terminal` field in which you can add your :doc:`payment terminal's " +"information `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 +msgid ":doc:`payment_methods/terminals`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 +msgid "" +"Once the payment method is created, you can select it in your POS settings. " +"To do so, go to the :ref:`POS' settings `, click " +":guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` " +"section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 +msgid "Payment terminals" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 +msgid "" +"Connecting and integrating a payment terminal with your POS system allows " +"you to accept multiple payment options, including credit and debit cards, " +"making the payment process more efficient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 +msgid "" +"Go to the :doc:`application settings <../configuration>`, scroll down to the" +" :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1 +msgid "checkbox in the settings to enable a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 +msgid "Then, follow the corresponding documentation to configure your device:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 +msgid ":doc:`Adyen configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 +msgid ":doc:`Ingenico configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 +msgid ":doc:`SIX configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 +msgid ":doc:`Stripe configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 +msgid ":doc:`Vantiv configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 +msgid ":doc:`Worldline configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 +msgid "" +"Once the terminal is configured, you can :doc:`create the corresponding " +"payment method and add it to the POS <../payment_methods>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 +msgid "Adyen" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:5 +msgid "" +"Connecting an **Adyen payment terminal** allows you to offer a fluid payment" +" flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 +msgid "" +"Adyen works only with businesses processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1,000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 +msgid "" +"Start by creating your Adyen account on `Adyen's website " +"`_. Then, board your terminal following the steps " +"described on your terminal's screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 +msgid "" +"`Adyen Docs - Payment terminal quickstart guides " +"`_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 +msgid "Configure the payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 +msgid "" +"First, go to :menuselection:`Point of Sale --> Configuration --> Settings " +"--> Payment Terminals`, and enable :guilabel:`Adyen`. Then, go to " +":menuselection:`Configuration --> Payment Methods` and create a new payment " +"method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` " +"field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 +msgid "" +"The selected journal **must** be a bank journal for the :guilabel:`Use a " +"payment terminal` field to appear." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 +msgid "" +"Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an" +" :guilabel:`Adyen Terminal Identifier`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38 +msgid "Generate an Adyen API key" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 +msgid "" +"The **Adyen API key** is a key used to authenticate your requests. To " +"generate an API key, go to your **Adyen account**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43 +msgid "" +"Then, go to :menuselection:`Developers --> API credentials`. Create a new " +"credential or click on an existing one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 +msgid "" +"Click on :guilabel:`Generate an API key` and copy-paste that key onto the " +"Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49 +msgid "" +"`Adyen Docs - API credentials `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 +msgid "Locate the Adyen terminal identifier" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 +msgid "" +"The **Adyen Terminal Identifier** is your terminal's serial number, which is" +" used to identify the hardware." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 +msgid "" +"To find this number, go to your **Adyen account**. Then, go to " +":menuselection:`Point of Sale --> Terminals`, select the terminal to link, " +"and copy-paste its serial number onto the Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63 +msgid "Set the Event URLs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 +msgid "" +"For Odoo to know when a payment is made, you must set the terminal **Event " +"URLs**. To do so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 +msgid "log in to `Adyen's website `_;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 +msgid "" +"go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and" +" select the connected terminal;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:70 +msgid "from the terminal settings, click :guilabel:`Integrations`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71 +msgid "" +"set the :guilabel:`Switch to decrypted mode to edit this setting` field as " +":guilabel:`Decrypted`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:72 +msgid "" +"click the **pencil icon** button and enter your server address, followed by " +"`/pos_adyen/notification` in the :guilabel:`Event URLs` field; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74 +msgid "" +"click :guilabel:`Save` at the bottom of the screen to save the changes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77 +msgid "Add a new payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 +msgid "" +"To add a new **payment method** to a point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, " +"select the POS and go to :menuselection:`Payments --> Payment Methods`, and " +"add your new method for Adyen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:65 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86 +msgid "Pay with a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86 +msgid "" +"When processing a payment, select :guilabel:`Adyen` as the payment method. " +"Check the amount and click on :guilabel:`Send`. Once the payment is " +"successful, the status changes to :guilabel:`Payment Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +msgid "" +"In case of connection issues between Odoo and the payment terminal, force " +"the payment by clicking on :guilabel:`Force Done`, which allows you to " +"validate the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +msgid "" +"This option is only available after receiving an error message informing you" +" that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:95 +msgid "To cancel the payment request, click on :guilabel:`cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 +msgid "Ingenico" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 +msgid "" +"Please note that Ingenico is currently only available for customers in the " +"Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15 +msgid "Connect an IoT Box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 the :doc:`IoT documentation " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 +msgid "Configure the Lane/5000 for Ingenico BENELUX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 +msgid "" +"Click on the F button of the terminal, then go in the :menuselection:`PoS " +"Menu --> Settings` and enter the settings password." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 +msgid "" +"Now, click on connection 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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 +msgid "" +"First, go in the general settings of the POS app, and activate the Ingenico " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44 +msgid "" +"Go back in :menuselection:`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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 +msgid "" +"If you want to cancel the payment request, click on cancel. You can still " +"retry to send the payment request." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:67 +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 connection between the terminal and Odoo has issues." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 +msgid "" +"This option will only be available if you received an error message telling " +"you the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:76 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 +msgid "SIX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 +msgid "" +"Connecting a **SIX payment terminal** allows you to offer a fluid payment " +"flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 +msgid "" +"Even though Worldline has acquired SIX Payment Services and both companies " +"use Yomani payment terminals, the firmware they run is different. Terminals " +"received from Worldline are, therefore, not compatible with this " +"integration." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17 +msgid "Install the POS IoT Six module" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 +msgid "" +"To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the " +":guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds " +"the necessary driver and interface to your database to detect Six terminals." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24 +msgid "This module replaces the **POS Six** module." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27 +msgid "Connect an IoT box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 +msgid "" +"Connecting a Six payment terminal to Odoo is requires :doc:`using a " +"Raspberry Pi or virtual (for Windows OS only) IoT box " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 +msgid "Configure the terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35 +msgid "" +"Navigate to your IoT Box homepage, where you can find the :guilabel:`Six " +"payment terminal` field once your database server is connected to the IoT " +"box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field " +"with the ID received from Six, and click :guilabel:`Connect`. Your Six " +"terminal ID should appear in the :guilabel:`Current Terminal Id` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Setting the Six terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43 +msgid "" +"Odoo automatically restarts the IoT box when the Six terminal ID is " +"configured. If your Six terminal is online, it will be automatically " +"detected and connected to the database. Check the IoT box homepage under the" +" :guilabel:`Payments` section to confirm the connection." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Confirming the connection to the Six payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 +msgid "" +"From your database, go to :menuselection:`Point of Sale --> Configuration " +"--> Payment Methods` to create a new payment method specifically for Six. " +"Click :guilabel:`New`, enter a :guilabel:`Name`, set the :guilabel:`Journal`" +" field as :guilabel:`Bank`, the :guilabel:`Use a Payment Terminal` field as " +":guilabel:`SIX IOT`, and select the corresponding device in the " +":guilabel:`Payment Terminal Device` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Creating a new payment method for the SIX payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:67 +msgid "" +"When processing a payment, select :ref:`your Six payment method " +"` in the :guilabel:`Payment Method` section and click " +":guilabel:`Send`. To cancel the payment request, click :guilabel:`Cancel`. " +"Once the payment is successful, the status switches to :guilabel:`Payment " +"Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Paying with Six" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:76 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 +msgid "" +"Once your payment is processed, the type of card used and the transaction ID" +" appear on the payment record." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:78 +msgid "" +"The language used for error messages is the same as the Six terminal. " +"Configure the terminal to change the language or contact Six." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:80 +msgid "By default, the port used by the Six terminal is `7784`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83 +msgid "" +"If there are connection issues between the payment terminal and Odoo, you " +"can still force the payment validation in Odoo using the :guilabel:`Force " +"Done` button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3 +msgid "Stripe" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:9 +msgid "" +":doc:`Use Stripe as payment provider. " +"<../../../../finance/payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:17 +msgid "" +"Activate **Stripe** in the settings by going to :menuselection:`Point of " +"Sale --> Configuration --> Settings --> Payment Terminals` and enabling " +":guilabel:`Stripe`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:20 +msgid "Then, create the payment method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, " +"click :guilabel:`Create`, and complete the :guilabel:`Method` field with " +"your payment method's name;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:24 +msgid "" +"Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use" +" a Payment Terminal` field as :guilabel:`Stripe`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:26 +msgid "" +"Enter your payment terminal serial number in the :guilabel:`Stripe Serial " +"Number` field;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:27 +msgid "" +"Click :guilabel:`Don't forget to complete Stripe connect before using this " +"payment method.`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 +msgid "payment method creation form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 +msgid "" +"Click :guilabel:`Identify Customer` to allow this payment method " +"**exclusively** for identified customers. For any unidentified customers to " +"be able to pay with Stripe, leave the :guilabel:`Identify Customer` field " +"unchecked." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:37 +msgid "" +"The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account`" +" can stay empty to use the default accounts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:39 +msgid "" +"Find your payment terminal serial number under the device or on `Stripe's " +"dashboard `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:43 +msgid "Connect Stripe to Odoo" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:45 +msgid "" +"Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a " +"configuration page. Fill in all the information to create your Stripe " +"account and link it with Odoo. Once the forms are completed, the API keys " +"(:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on" +" **Stripe's** website. To do so, click :guilabel:`Get your Secret and " +"Publishable keys`, click the keys to copy them, and paste them into the " +"corresponding fields in Odoo. Your terminal is ready to be configured in a " +"POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 +msgid "stripe connection form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:57 +msgid "" +"When you use **Stripe** exclusively in Point of Sale, you only need the " +"**Secret Key** to use your terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:59 +msgid "" +"When you use Stripe as **payment provider**, the :guilabel:`State` can stay " +"set as :guilabel:`Disabled`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:61 +msgid "" +"For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button " +"does not work. To retrieve the API keys manually, log in to your `Stripe " +"dashboard `_, type `API` in the search bar, " +"and click :guilabel:`Developers > API`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:67 +msgid "Configure the payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:69 +msgid "" +"Swipe right on your payment terminal, click :guilabel:`Settings`, enter the " +"admin PIN code, validate and select your network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:73 +msgid "The device must be connected to a secured WI-FI network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 +msgid "Your Odoo database and payment terminal must share the same network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:75 +msgid "" +"You must enter the admin PIN code to access your payment terminal settings. " +"By default, this code is `07139`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:79 +msgid "Link the payment method to a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 +msgid "" +"To add a **payment method** to your point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`. Select the " +"POS, scroll down to the :guilabel:`Payments` section, and add your payment " +"method for **Stripe** in the :guilabel:`Payment Methods` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 +msgid "" +"When processing a payment, select :guilabel:`Stripe` as the payment method. " +"Check the amount and click :guilabel:`Send`. Once the payment is successful," +" the status changes to :guilabel:`Payment Successful`. To cancel the payment" +" request, click :guilabel:`cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:97 +msgid "The terminal must have at least 10% battery level to use it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:98 +msgid "The device does not work for payments under €0.50." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:101 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 +msgid "Payment terminal unavailable in your Stripe account" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:106 +msgid "" +"If the payment terminal is unavailable in your Stripe account, you must add " +"it manually:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 +msgid "" +"Log into your `Stripe's dashboard `_ and go to" +" :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:110 +msgid "" +"Add a location by clicking the :guilabel:`+ New` button or selecting an " +"already created location;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 +msgid "" +"Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill " +"in the required information." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 +msgid "" +"You must provide a **registration code**. To retrieve that code, swipe right" +" on your device, enter the admin PIN code (by default: `07139`), validate, " +"and click :guilabel:`Generate a registration code`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 +msgid "Vantiv" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 +msgid "" +"Please note MercuryPay only operates with US and Canadian banks, making this" +" procedure only suitable for North American businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +msgid "" +"Vantiv card readers should be purchased exclusively from Vantiv, as certain " +"Vantiv terminals bought on Amazon do not include the correct encryption " +"needed to be used with an Odoo database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 +msgid "Configure the Payment Method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 +msgid "" +"First, go in the general settings of the POS app, and activate the Vantiv " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 +msgid "" +"Back in :menuselection:`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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 +msgid "Pay with a Payment Terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 +msgid "" +"In your PoS interface, at the moment of the payment, select your Vantiv " +"payment method and… that’s all." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 +msgid "Worldline" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 +msgid "Please note that Worldline is currently only available in the Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 +msgid "" +"Connecting a Worldline Payment Terminal to Odoo is a feature that requires " +"an IoT Box. For more information on how to connect one to your database, " +"please refer to the :doc:`IoT documentation " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22 +msgid "Configure the protocol" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 2`. Then, click on :menuselection:`Change --> " +"CTEP (as Protocole ECR) --> OK`. Click on **OK** thrice on the subsequent " +"screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). " +"Finally, press **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:31 +msgid "Set the IP address" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> " +"TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK`" +" (*TCP Configuration client* screen)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:38 +msgid "Finally, set up the hostname and port number." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41 +msgid "Hostname" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44 +msgid "" +"To set up the hostname, enter your IoT box's IP address' sequence numbers " +"and press **OK** at each \".\" until you reach the colon symbol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 +msgid "Then, press **OK** twice." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "Here's an IP address sequence: `10.30.19.4:8069`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "" +"On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> " +"19 --> OK --> 4 --> OK --> OK`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:53 +msgid "" +"Your IoT box's IP address is available in your IoT Box application's " +"database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:56 +msgid "Port number" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58 +msgid "" +"On the *Port number* screen, enter **9001** (or **9050** for Windows) and " +"click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> " +"OK`. Click on **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:65 +msgid "" +"From the Point of Sale application, go to :menuselection:`Configuration --> " +"Settings --> Payment terminals` and activate the *Worldline* payment " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:71 +msgid "" +"Then, go to :menuselection:`Configuration --> Payment methods` and create a " +"new payment method for *Worldline*. Select the payment terminal *Worldline* " +"and your payment terminal device on your *Payment Method form*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:78 +msgid "Technician password: `1235789`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:79 +msgid "" +"To reach Wordline's technical assistance, call `02 727 61 11` and choose " +"\"merchant\". Your call is automatically transferred to the desired service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 +msgid "" +"Configure the cashier terminal if you have both a customer and a cashier " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:82 +msgid "" +"To avoid blocking the terminal, check the initial configuration beforehand." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83 +msgid "" +"Set a fixed IP to your IoT Box’s router to prevent losing the connexion." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 +msgid "" +"When processing a payment, select *Worldline* as payment method. Check the " +"amount and click on *Send*. Once the payment is successful, the status " +"changes to *Payment Successful*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 +msgid "" +"In case of connexion issues between Odoo and the payment terminal, force the" +" payment by clicking on *Force Done*, which allows you to validate the " +"order. This option is only available after receiving an error message " +"informing you that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 +msgid "To cancel the payment request, click on **cancel**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing.rst:5 +msgid "Pricing features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:13 +msgid "" +"Each point of sale in Odoo can be configured to apply cash rounding to the " +"totals of its bills or receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Settings` and " +"enable *Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " +"open the point of sale you want to configure, and enable the *Cash Rounding*" +" option." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 +msgid "" +"To define the **Rounding Method**, open the drop-down list and click on " +"*Create and Edit...*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 +msgid "" +"Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*," +" then save both the Rounding Method and your Point of Sale settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 +msgid "" +"All total amounts of this point of sale now add a line to apply the rounding" +" according to your settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 +msgid "" +"Odoo Point of Sale only supports the :guilabel:`Add a rounding line` " +"rounding strategy." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 +msgid "Discount tags (barcode scanner)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 +msgid "" +"If you want to sell your products with a discount, for a product getting " +"close to its expiration date for example, you can use discount tags. They " +"allow you to scan discount barcodes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 +msgid "To use discount tags you will need to use a barcode scanner." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 +msgid "Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 +msgid "To use discounts tags, we need to learn about barcode nomenclature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 +msgid "" +"Let's say you want to have a discount for the product with the following " +"barcode:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 +msgid "" +"You can find the *Default Nomenclature* under the settings of your PoS " +"interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 +msgid "" +"Let's say you want 50% discount on a product you have to start your barcode " +"with 22 (for the discount barcode nomenclature) and then 50 (for the %) " +"before adding the product barcode. In our example, the barcode would be:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 +msgid "Scan the products & tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 +msgid "You first have to scan the desired product (in our case, a lemon)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 +msgid "" +"And then scan the discount tag. The discount will be applied and you can " +"finish the transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 +msgid "Discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:5 +msgid "" +"By offering discounts, you can entice your customers and drastically " +"increase your revenue. It is vital to offer discounts, whether they are " +"time-limited, seasonal or manually given." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 +msgid "" +"To manage discounts, Odoo has powerful features that help set up a pricing " +"strategy tailored to every business." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 +msgid "Apply manual discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 +msgid "" +"If you seldom use discounts, applying manual ones might be the easiest " +"solution for your Point of Sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 +msgid "" +"You can either apply a discount on the whole order or on specific products " +"inside an order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 +msgid "From your PoS session interface, use the *Disc* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount button for manual discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 +msgid "" +"Then, you can input a discount over the product that is currently selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 +msgid "Apply a global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 +msgid "" +"To apply a discount on the whole order, go to :menuselection:`Point of Sales" +" --> Configuration --> Point of Sale` and select your PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 +msgid "" +"Once on your PoS form, select *Global Discounts*, under the *Pricing* " +"category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the feature to enable for global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 +msgid "Now, you have a new *Discount* button appearing on your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the button to use for global discount via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 +msgid "Click on it and enter the wanted discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount offered in the payment summary" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 +msgid "" +"On this example, there is a global discount of 50% as well as a specific 50%" +" discount on oranges." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 +msgid "" +"To activate time-limited discounts, you must activate the *Pricelists* " +"feature. To do so, go to :menuselection:`Point of Sales --> Configuration " +"--> Point of Sale` and open your PoS. Then, enable the pricelist feature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the pricelist feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 +msgid "" +"Once activated, you must choose the pricelists you want to make available in" +" the PoS and define a default one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 +msgid "Create a pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 +msgid "" +"By default, Odoo has a *Public Pricelist* configured. To create more, go to " +":menuselection:`Point of Sale --> Products --> Pricelists`. Then click on " +"create." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 +msgid "" +"When creating a pricelist, you can set several criteria to use a specific " +"price: period, min. quantity, etc. You can also decide to apply that " +"pricelist on specific products or on the whole range." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of a time-limited pricelist for two products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 +msgid "Using a pricelist with the PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 +msgid "" +"On the PoS interface, a new button appears. Use it to select a pricelist." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "" +"View of the button to use for time-limited discounts via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 +msgid "" +"Click on it to instantly update the prices with the selected pricelist. " +"Then, you can finalize the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 +msgid "Flexible taxes (fiscal positions)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 +msgid "" +"When running a business, you may need to apply different taxes and record " +"transactions on various accounts based on the location and type of business " +"of your customers and providers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:8 +msgid "" +"The **fiscal positions** feature enables you to establish rules that " +"automatically select the right taxes and accounts used for each transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:12 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:51 +msgid ":doc:`../../../finance/accounting/taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 +msgid ":doc:`../../../finance/accounting/taxes`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:18 +msgid "" +"To enable the feature, go to :menuselection:`Point of Sale --> Configuration" +" --> Settings`, scroll down to the :guilabel:`Accounting` section, and " +"enable :guilabel:`Flexible Taxes`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 +msgid "" +"Then, set a default fiscal position that should be applied to all sales in " +"the selected POS in the :guilabel:`Default` field. You can also add more " +"fiscal positions to choose from in the :guilabel:`Allowed` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:28 +msgid "" +"According to the :doc:`fiscal localization package " +"<../../../finance/fiscal_localizations>` activated, several fiscal positions" +" are preconfigured and can be set and used in POS. However, you can also " +":ref:`create new fiscal positions `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 +msgid "" +"If you do not set a fiscal position, the tax remains as defined in the " +"**customer taxes** field on the product form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:37 +msgid "Use fiscal positions" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:39 +msgid "" +"Open a :ref:`POS session ` to use one of the allowed " +"fiscal positions. Then, click the :guilabel:`Tax` button next to the **book-" +"shaped** icon and select a fiscal position from the list. Doing so applies " +"the defined rules automatically to all the products subject to the chosen " +"fiscal position's regulations." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:48 +msgid "" +"If a default fiscal position is set, the tax button displays the name of the" +" fiscal position." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 +msgid "Loyalty programs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 +msgid "" +"Encourage your customers to continue to shop at your point of sale with a " +"*Loyalty Program*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 +msgid "" +"To activate the *Loyalty Program* feature, go to :menuselection:`Point of " +"Sale --> Configuration --> Point of sale` and select your PoS interface. " +"Under the Pricing features, select *Loyalty Program*" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 +msgid "From there you can create and edit your loyalty programs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 +msgid "" +"You can decide what type of program you wish to use, if the reward is a " +"discount or a gift, make it specific to some products or cover your whole " +"range. Apply rules so that it is only valid in specific situation and " +"everything in between." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 +msgid "Use the loyalty program in your PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 +msgid "" +"When a customer is set, you will now see the points they will get for the " +"transaction and they will accumulate until they are spent. They are spent " +"using the button *Rewards* when they have enough points according to the " +"rules defined in the loyalty program." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 +msgid "" +"You can see the price is instantly updated to reflect the pricelist. You can" +" finalize the order in your usual way." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 +msgid "" +"If you select a customer with a default pricelist, it will be applied. You " +"can of course change it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 +#: ../../content/applications/sales/subscriptions/products.rst:108 +msgid "Pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 +msgid "" +"Pricelists allow you to adjust product prices depending on various criteria " +"automatically. For example, you can set POS-specific prices, create " +"temporary discount periods, reward specific customers, or offer discounts " +"when set quantities are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:14 +msgid "" +"Navigate to the :ref:`general POS app settings ` and" +" ensure :guilabel:`Flexible Pricelists` are enabled under the " +":guilabel:`Pricing` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 +msgid "" +":ref:`Multiple prices per product ` is the default " +"pricelist option for setting simple fixed price rules per product. Select " +":ref:`Advanced price rules (discounts, formulas) ` to " +"apply price rules to multiple products at once and to compute prices " +"dynamically using percentage discounts or more complex formulas in addition " +"to setting fixed prices." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Enabling pricelists in the general P0S settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 +msgid "" +"The selected pricelist type applies to the entire database, including the " +":doc:`Sales <../../sales/products_prices/prices/pricing>` and " +":ref:`eCommerce ` apps." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 +msgid "Create pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:35 +msgid "" +"Go to :menuselection:`Point of Sale --> Products --> Pricelists` and click " +":guilabel:`New` or select an existing pricelist. The pricelist setup differs" +" depending on the :ref:`selected pricelist option " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 +msgid "Multiple prices per product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:44 +msgid "" +"When pricelists are configured to use the :guilabel:`Multiple prices per " +"product` option, it is possible to use multiple fixed prices for different " +"products or their variants depending, if necessary, on one or several " +"conditions. To add a new price rule to a pricelist:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48 +msgid "" +"Click :guilabel:`Add a line`, and select a **product** and its **variant** " +"if needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:49 +msgid "Add the condition(s):" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:51 +msgid "" +"a product quantity to be reached by using the :guilabel:`Min. Quantity` " +"column;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:52 +msgid "" +"a determined period during which the pricelist is applied by using the " +":guilabel:`Start Date` and :guilabel:`End Date` columns." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:55 +msgid "" +"Add the :guilabel:`Price` to be applied when the conditions are met (if " +"any)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Setup form of a multiple prices pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:312 +msgid "Advanced price rules" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:65 +msgid "" +"When pricelists are configured to use the :guilabel:`Advanced price rules " +"(discounts, formulas)` option, it is possible to use percentage " +"discounts/mark-ups and formulas in addition to using fixed prices. To add a " +"new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up " +"windows:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:69 +msgid "Select a :guilabel:`Computation` method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:71 +msgid "" +":guilabel:`Fixed Price` to set a new fixed price (similarly to the " +":guilabel:`Multiple prices per product` option)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73 +msgid "" +":guilabel:`Discount` to compute a percentage discount (e.g., `10.00` %) or " +"mark-up (e.g., `-10.00` %)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:75 +msgid "" +":guilabel:`Formula` to compute the price according to a formula. It is " +"required to define what the calculation is **based on** (:guilabel:`Sales " +"Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:79 +msgid "Apply a percentage :guilabel:`Discount` or mark-up." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:80 +msgid "" +"Add an :guilabel:`Extra Fee` (e.g., $ `5.00`) or subtract a fixed amount " +"(e.g., $ `-5.00`)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:81 +msgid "" +"Define a :doc:`Rounding Method ` by forcing the price after " +":guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra" +" Fee` is applied afterward." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:86 +msgid "" +"To have the final price end with `.99`, set the :guilabel:`Rounding Method` " +"to `1.00` and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89 +msgid "" +"Specify the minimum (e.g., $ `20.00` ) and maximum (e.g., $ `50.00` ) profit" +" :guilabel:`Margins` for computations based on :guilabel:`Cost`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:92 +msgid "Select on which product(s) the price rule should be **applied**:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:94 +msgid ":guilabel:`All Products`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:95 +msgid "a :guilabel:`Product Category`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:96 +msgid "a :guilabel:`Product`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:97 +msgid "a :guilabel:`Product Variant`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:99 +msgid "" +"Add conditions, such as a specific quantity to reach for the price to change" +" by using the :guilabel:`Min. Quantity` field or a specific period during " +"which the pricelist should be applied by using the :guilabel:`Validity` " +"fields." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Setup form to configure an advanced pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:107 +msgid "Select pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:109 +msgid "" +"Go to the :ref:`specific POS settings ` and add all " +"the available pricelists in the :guilabel:`Available` field. Then, set its " +"**default pricelist** in the :guilabel:`Default` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:113 +msgid "" +"When you :ref:`open a POS session `, click the " +"**pricelists** button, and select the desired pricelist from the list." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Button to select a pricelist on the POS frontend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:120 +msgid "" +"Multiple pricelists must be selected for the **pricelist button** to be " +"displayed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:121 +msgid "" +"If a pricelist is selected on a POS order while its conditions are **not** " +"met, the price will **not** be adjusted." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:125 +msgid "" +"You can also set a pricelist to be selected automatically once a specific " +":ref:`customer is set `. To do so, go to the customer form " +"and switch to the preferred pricelist in the :guilabel:`Pricelist` field of " +"the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:130 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:131 +msgid "" +":ref:`How to use pricelists in an ecommerce environment " +"`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 +msgid "Receipts and invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 +msgid "Receipts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:8 +msgid "" +"Set up receipts by going to :menuselection:`Point of Sale --> Configuration " +"--> Point of Sale`, selecting a POS, and scrolling down to the " +":guilabel:`Bills & Receipts` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 +msgid "" +"To **customize** the **header** and **footer**, activate :guilabel:`Header &" +" Footer` and fill in both fields with the information to be printed on the " +"receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:14 +msgid "" +"To **print receipts** automatically once the payment is registered, enable " +"the :guilabel:`Automatic Receipt Printing` setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "POS receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:21 +msgid ":doc:`restaurant/bill_printing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24 +msgid "Reprint a receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 +msgid "" +"From the POS interface, click :guilabel:`Orders`, open the dropdown " +"selection menu next to the search bar, and change the default :guilabel:`All" +" active orders` filter to :guilabel:`Paid`. Then, select the corresponding " +"order and click :guilabel:`Print Receipt`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "Print receipt button from the backend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:34 +msgid "" +"You can filter the list of orders using the search bar. Type in your " +"reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or " +":guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 +msgid "Invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 +msgid "" +"Point of Sale allows you to issue and print invoices for :ref:`registered " +"customers ` upon payment and retrieve all past invoiced " +"orders." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 +msgid "" +"An invoice created in a POS creates an entry into the corresponding " +":ref:`accounting journal `, previously :ref:`set up " +"`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 +msgid "" +"To define what journals will be used for a specific POS, go to the " +":ref:`POS' settings ` and scroll down to the " +"accounting section. Then, you can determine the accounting journals used by " +"default for orders and invoices in the :guilabel:`Default Journals` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "accounting section in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:63 +msgid "Invoice a customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 +msgid "" +"Upon processing a payment, click :guilabel:`Invoice` underneath the " +"customer's name to issue an invoice for that order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:68 +msgid "" +"Select the payment method and click :guilabel:`Validate`. The **invoice** is" +" automatically issued and ready to be downloaded and/or printed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 +msgid "" +"To be able to issue an invoice, a :ref:`customer ` must be " +"selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75 +msgid "Retrieve invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 +msgid "To retrieve invoices from the **POS dashboard**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 +msgid "" +"access all orders made through your POS by going to :menuselection:`Point of" +" Sale --> Orders --> Orders`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 +msgid "" +"to access an order's invoice, open the **order form** by selecting the " +"order, then click :guilabel:`Invoice`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "invoice smart button from an order form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:88 +msgid "" +"**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in " +"the :guilabel:`Status` column." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 +msgid "" +"You can filter the list of orders to invoiced orders by clicking " +":guilabel:`Filters` and :guilabel:`Invoiced`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:94 +msgid "QR codes to generate invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 +msgid "" +"Customers can also request an invoice by scanning the **QR code** printed on" +" their receipt. Upon scanning, they must fill in a form with their billing " +"information and click :guilabel:`Get my invoice`. On the one hand, doing so " +"generates an invoice available for download. On the other hand, the order " +"status goes from :guilabel:`Paid` or :guilabel:`Posted` to " +":guilabel:`Invoiced` in the Odoo backend." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "order status change" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:105 +msgid "" +"To use this feature, you have to enable QR codes on receipts by going to " +":menuselection:`Point of Sale --> Configuration --> Settings`. Then, select " +"the POS in the :guilabel:`Point of Sale` field, scroll down to the " +":guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on " +"ticket`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:6 +msgid "View statistics" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:8 +msgid "" +"To access your statistics, go to :menuselection:`Point of Sale --> Reporting" +" --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis " +"(:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:12 +msgid "" +"These statistics are available in a graph or pivot view that you can filter " +"or group depending on your needs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:5 +msgid "Restaurant features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:7 +msgid "" +"Managing a restaurant or a bar comes with specific needs. The Point of Sale " +"application provides various features that allow performing all the required" +" tasks in such businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:10 +msgid "Once the POS is set to be used in a restaurant or a bar, you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:12 +msgid "" +":doc:`organize your floors and tables to reflect your interior " +"`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:13 +msgid ":ref:`take orders `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:14 +msgid "" +":doc:`communicate with the kitchen or the bar through the POS " +"`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:15 +msgid "" +":doc:`print bills in advance and split them `;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:16 +msgid ":doc:`collect tips `; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:17 +msgid "" +":doc:`set different taxes for takeaway food `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:22 +msgid "" +"To enable the restaurant and bar-specific features, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, select the " +"POS, and activate :guilabel:`Is a Bar/Restaurant`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:25 +msgid "" +"These features are displayed in the :guilabel:`Restaurant & Bar` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst-1 +msgid "restaurant and bar-specific features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 +msgid "Bills" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 +msgid "" +"Typical practices in restaurants or bars are to request the bill before " +"proceeding to payment or splitting it based on the items ordered. Odoo POS " +"provides two features to perform these tasks seamlessly: **Bill Printing** " +"and **Bill Splitting**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 +msgid "" +"To activate the features, go to :menuselection:`Point of Sale --> " +"Configuration --> Settings`, select the POS, and activate :guilabel:`Early " +"Receipt Printing` and :guilabel:`Allow Bill Splitting` in the " +":guilabel:`Restaurant & Bar` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 +msgid "" +"activate the bill printing and bill splitting features in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 +msgid "Bill printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 +msgid "" +"From an open session, click :menuselection:`Bill --> Print` at any moment to" +" generate and print a bill." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 +msgid "" +"The printed bill is **not** final and will be updated to reflect any changes" +" to the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 +msgid "Bill splitting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 +msgid "" +"From an open session, click :guilabel:`Split` to select the items to " +"regroup. Once everything is selected, click :guilabel:`Payment` and proceed " +"to checkout for these items. Repeat for each guest." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 +msgid "" +"Once you return to the table, the selected items are no longer on order, as " +"they have been paid for." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 +msgid "The feature is available as soon as at least two items are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 +msgid ":doc:`floors_tables`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 +msgid "Floors and tables management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6 +msgid "Add a floor" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8 +msgid "" +"Once your *Point of Sale* has been configured, select *Table Management* " +"under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. " +"Then, click on *Floors* to create and name your floor and tables." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the table management feature. Way to manage and create floors for a " +"pos" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"Backend view of a restaurant floor. Table name and number of sits for each " +"table" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21 +msgid "Don’t forget to link your floor to your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24 +msgid "Add tables" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26 +msgid "" +"To add tables, you can also open your PoS interface to see your floor(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the floors menu to manage several floors at the same time" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33 +msgid "" +"Then, click on *Edit Mode* (pencil icon on the upper right corner) to be " +"allowed to create, move, modify tables, etc." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the floor management. Add tables, the number of sits, their name and" +" their shape" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41 +msgid "" +"To make your table easier to be found, you can rename them, change their " +"shape, size or even color. It is also possible to add the maximum number of " +"sits the table can have." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50 +msgid "" +"To register an order, click on the respective table. By doing so, you are " +"taken to your main interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the pos interface to register orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60 +msgid "" +"If your customers want to move to another table after they already ordered, " +"use the transfer button. This way, the order is also moved to the new table." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64 +msgid "To do so, select the table your customer is currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the restaurant tables, one having a pending order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70 +msgid "" +"Now, click on the transfer button and select the table to which you are " +"transferring your customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the pos interface and transfer button. How to transfer customers from one table\n" +"to another" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79 +msgid "Register an additional order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81 +msgid "" +"When registering an order, use the + button to simultaneously proceed to " +"another one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 +msgid "" +"Then, you can shift between your orders and process the payment when needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the - button, allowing employees to close/remove an order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92 +msgid "The - button allows you to remove the order you are currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 +msgid "Orders printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 +msgid "" +"Integrating printers in a restaurant or bar's workflow can enhance " +"communication and collaboration between the front-of-house and back-of-house" +" teams, leading to a more streamlined and efficient service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:15 +msgid "Enable and create printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:17 +msgid "" +"To enable sending orders to a kitchen or bar printer, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, scroll down " +"to the :guilabel:`Restaurant & Bar` section, and enable :guilabel:`Kitchen " +"Printers`. Type in a name for the printer in the :guilabel:`Printers` field " +"and click :guilabel:`Create and edit...` to open a setup form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22 +msgid "" +"To get a list of all the printers already created or to modify an already " +"created printer, click :guilabel:`--> Printers` and select the desired " +"printer to open the setup form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "settings to enable the kitchen printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:32 +msgid "Setup form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34 +msgid "" +"From the :ref:`setup form `, select the " +":guilabel:`Printer Type` according to your installation:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37 +msgid "" +"If your printer is connected to an IoT box, select :guilabel:`Use a printer " +"connected to the IoT Box` and select the device in the :guilabel:`IoT " +"Device` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39 +msgid "" +"If you use an Epson printer that does not need an IoT box, select " +":guilabel:`Use an Epson printer` and enter the printer's IP address in the " +":guilabel:`Epson Printer IP Address` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:43 +msgid ":doc:`../../../productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 +msgid ":doc:`../../../productivity/iot/devices/printer`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:45 +msgid ":doc:`../configuration/epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:47 +msgid "" +"Set your printer to print specific products based on their POS category. To " +"do so, click :guilabel:`Add a line` in the :guilabel:`Printed Product " +"Categories` field. If you leave this field empty, all products are sent to " +"the printer regardless of their POS category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "setup form to configure a kitchen printer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:56 +msgid "Print orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:58 +msgid "" +"From an open session, start taking an order and click :guilabel:`Order` to " +"send it to the bar or the kitchen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "order button from the POS UI to send orders to a kitchen or a bar" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:66 +msgid "" +"When products can be printed, they appear in green in the cart, and the " +"order button turns green." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 +msgid "Tips" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:5 +msgid "" +"Tipping is customary in multiple countries. Point of Sale allows tipping in " +":ref:`shops `, :doc:`bars <../restaurant>`, or :doc:`restaurants " +"<../restaurant>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:13 +msgid "" +"To allow tipping in your POS, activate the :guilabel:`Tips` feature in " +":menuselection:`Point of Sale --> Configuration --> Settings`. At the top of" +" the page, select the POS in which you wish to allow **tipping**, scroll " +"down to the :guilabel:`Payment` section and check :guilabel:`Tips`. Once " +"enabled, add a :guilabel:`Tip Product` in the corresponding field, and save." +" The designated product will be used as a reference on customers' receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "enable tips in a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:25 +msgid "Tip products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:27 +msgid "" +"**Tip products** can be created on the spot. To do so, enter a product's " +"name in the :ref:`Tip Product ` field and click " +":guilabel:`Create` or press **enter**. The product is automatically " +"configured to be used as a tip at the payment screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:31 +msgid "" +"However, if you wish to be able to select the tip product in a POS session, " +"you must activate the **Available in POS** setting. To do so, click " +":guilabel:`Create and edit...` to open the product configuration form. Then," +" go to the :guilabel:`Sales` tab, tick the :guilabel:`Available in POS` " +"checkbox, and click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:37 +msgid "" +"When you create a product to use as a tip, leave the **product type** as " +":guilabel:`Consumable` to avoid unnecessary inventory movements." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:39 +msgid "" +"You can only select one tip product per POS, but you can choose a different " +"one for each." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:42 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:72 +msgid "Tip using an Adyen terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:44 +msgid "" +"If you use an :doc:`Adyen <../payment_methods/terminals/adyen>` payment " +"terminal and wish to enable **tips** using the terminal, check " +":guilabel:`Add tip through payment terminal (Adyen)` below the :ref:`tip " +"settings `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:49 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:79 +msgid "Tip after payment" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:51 +msgid "" +"If you use a POS system in a bar or a restaurant, you can enable " +":guilabel:`Add tip after payment (North America specific)`. Doing so " +"generates a bill to print and complete manually by the customer and the " +"waiter. That bill indicates the tip value the customer chooses to give after" +" the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:56 +msgid "" +"To use this feature, the selected payment method must have a bank journal " +"attributed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:59 +msgid "Add tips" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:61 +msgid "" +"To add tips to an order, :ref:`access the payment screen ` and " +"click :guilabel:`♥ Tip`. Then, enter the tipping amount, click " +":guilabel:`Confirm` to validate, and process the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "tip popup window" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:67 +msgid "" +"Alternatively, you can select the :ref:`tip product ` on the " +"POS interface to add it to the cart. When selected, the product is " +"automatically set as a tip, and its default value equals its **Sales " +"Price**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:74 +msgid "" +"During checkout, select **Adyen** as the payment terminal, and send the " +"payment request to the device by clicking :guilabel:`Send`. The customers " +"are asked to enter the desired tipping amount on the terminal's screen " +"before proceeding to the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:81 +msgid "" +"At checkout, select a card payment method and click :guilabel:`Close Tab`. " +"Doing so generates a bill to complete by the customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "tipping bill after payment to complete by customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:87 +msgid "" +"On the following screen, click the percentage (:guilabel:`15%`, " +":guilabel:`20%`, :guilabel:`25%`), :guilabel:`No Tip`, or enter the tipping " +"amount the customer chose to give. Then, click :guilabel:`Settle` to move to" +" the following order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "screen to select a tip amount to collect after payment" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop.rst:5 +msgid "Shop features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 +msgid "Barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:5 +msgid "" +"Using a barcode scanner to process point-of-sale orders improves your " +"efficiency in providing quicker customer service. Barcode scanners can be " +"used both to scan products or to log employees into a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:12 +msgid "" +"To use a barcode scanner, you must enable the feature in the Inventory app. " +"Go to :menuselection:`Inventory --> Configuration --> Settings`, in the " +":guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst-1 +msgid "barcode setting in the Inventory application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 +msgid "" +":doc:`Set up a barcode scanner " +"`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22 +msgid "" +":doc:`Activate barcode scanners " +"`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24 +msgid "" +"Once enabled in **Inventory**, you can use the barcode feature in **Point of" +" Sale** with products that have a barcode number assigned." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:28 +msgid "Assign barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:31 +msgid "To your products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 +msgid "" +"To use this feature in POS, your products must have barcodes assigned. To do" +" so, go to :menuselection:`Point of Sale --> Products --> Products` and open" +" a **product form**. Add a barcode number in the :guilabel:`Barcode` field " +"in the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:38 +msgid "To your employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:40 +msgid "" +"To add an identification number to an employee, go to the **Employees** app " +"and open an **employee form**. Choose an identification number for your " +"employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR " +"Settings` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:45 +msgid "Use barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:48 +msgid "Scan products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:50 +msgid "" +"Scan a product's barcode using a barcode scanner. Doing so adds it directly " +"to the cart. To change the quantity, scan a product as many times as needed," +" or click :guilabel:`Qty` and enter the number of products using the keypad." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:54 +msgid "" +"You can also enter the barcode number manually in the search bar to look for" +" the product. Then, click it to add it to the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 +msgid "Log employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 +msgid "" +"You can also use a barcode scanner to log your employees. To do so, " +":ref:`restrict access ` to the POS and " +":ref:`use barcodes to log your employees in ` your " +"POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 +msgid "Sales orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 +msgid "" +"When working in retail, you might need to order products directly from your " +"Point of sale. Fortunately, Odoo Point of Sale is fully integrated with Odoo" +" Sales, meaning that you can create a sales order and pay for it directly " +"from your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:10 +msgid "Select a sales order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:12 +msgid "" +"From the **Point of Sale** application, open a new session. Then, click on " +":guilabel:`Quotations/Orders` to get the complete list of quotations and " +"sales orders created on the sales application." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "Quotations and sales order button on the Point of Sale interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 +msgid "" +"To ease finding the right sales order, you can filter that list on the " +"**customer** or on the **order reference**. You can also set the customer " +"before clicking on :guilabel:`Quotations/Orders` to reduce the list to one " +"particular customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:26 +msgid "Apply a down payment or settle the order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:28 +msgid "From the list of sales order, select one to make a payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "list view of sales orders and quotations" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 +msgid "You can either:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:36 +msgid "" +"Settle the order **partially**: after clicking on :guilabel:`Apply a down " +"payment`, enter the percentage of down payment you want the customer to pay." +" Then, click on :guilabel:`ok` and proceed with the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:39 +msgid "" +"Settle the order **completely**: click on :guilabel:`Settle the order` to " +"pay for the total of the sales order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:43 +msgid "" +"Once you settle a sales order, the applied down payment is automatically " +"deducted from the total amount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:47 +msgid ":doc:`/applications/sales/sales/invoicing/down_payment`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:3 +msgid "Serial numbers and lots" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:5 +msgid "" +"Working with **serial numbers** and **lots** allows tracking your products' " +"movements. When products are tracked, the system identifies their location " +"based on their last movement." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:8 +msgid "" +"To enable traceability, go to :menuselection:`Point of Sale --> Products -->" +" Products`. Then, select a product and check the :guilabel:`Tracking By " +"Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Enable traceability settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 +msgid "Serial numbers and lots importation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:19 +msgid "" +"You can import serial numbers in Point of Sale. To do so, select a **sales " +"order** or a **quotation** containing tracked products. Then, agree to load " +"the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Pop-up window for serial number import" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 +msgid "" +"The imported tracking numbers appear below the tracked products. You can " +"modify them by clicking on the list-view button next to the products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:37 +msgid ":doc:`../shop/sales_order`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:40 +msgid "Serial numbers and lots creation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:42 +msgid "" +"If a tracked product is available in your POS, adding the product to the " +"cart opens a pop-up window where you can type or scan the product's serial " +"or lot numbers. To add more than one of the same tracked products, click on " +"**enter** to validate and start a new line." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "adding new serial and lots numbers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 +msgid "" +"Changing a tracked product's quantity using the numpad turns the list-view " +"button red. Click on it to add the missing lot and serial numbers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:54 +msgid "" +":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked " +"products but not mandatory. Meaning that not attributing some or any does " +"**not** prevent from completing the sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" +msgstr "" + +#: ../../content/applications/sales/rental.rst:3 +msgid "Rental" +msgstr "" + +#: ../../content/applications/sales/rental.rst:5 +msgid "" +"The Odoo *Rental* application provides comprehensive solutions to configure " +"and manage rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:7 +msgid "" +"Send quotations, confirm orders, schedule rentals, register products when " +"they are picked up and returned, and invoice customers from this single " +"platform." +msgstr "" + +#: ../../content/applications/sales/rental.rst:11 +msgid "`Odoo Rental: product page `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:12 +msgid "`Odoo Tutorials: Rental `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:17 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/sales/rental.rst:19 +msgid "" +"Upon opening the *Rental* application, the :guilabel:`Rental Orders` " +"dashboard is revealed." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Example of the Rental Orders dashboard available in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:25 +msgid "" +"In the default kanban view, all rentals are visible. Each rental card " +"displays the customer name, the price of the rental, the related sales order" +" number, along with the status of the rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:29 +msgid "" +"Rental kanban cards that do **not** display a rental status means those " +"rentals have confirmed quotations, but have not been picked up yet." +msgstr "" + +#: ../../content/applications/sales/rental.rst:32 +msgid "" +"On the left sidebar, the :guilabel:`Rental Status` for each rental can be " +"found. Beneath that, the :guilabel:`Invoice Status` of the rentals is " +"accessible. Clicking any option in the left sidebar filters the displayed " +"rentals on the dashboard." +msgstr "" + +#: ../../content/applications/sales/rental.rst:37 +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 +msgid "Settings" +msgstr "" + +#: ../../content/applications/sales/rental.rst:39 +msgid "" +"To configure additional rental delay costs, availability of rental items, or" +" minimum time of rental, navigate to :menuselection:`Rental app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "How the Settings page appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:46 +msgid "" +"In the :guilabel:`Rental` section, there are options to configure " +":guilabel:`Default Delay Costs` and :guilabel:`Default Padding Time`. There " +"is also the option to activate :guilabel:`Rental Transfers` and " +":guilabel:`Digital Documents`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:50 +msgid ":guilabel:`Default Delay Costs` are additional costs for late returns." +msgstr "" + +#: ../../content/applications/sales/rental.rst:51 +msgid "" +":guilabel:`Default Padding Time` represents the minimum amount of time " +"between two rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:52 +msgid "" +":guilabel:`Rental Transfers` means stock deliveries and receipts can be used" +" for rental orders." +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "" +":guilabel:`Digital Documents` allows users to upload documents for customers" +" to sign prior to" +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "confirming their rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:56 +msgid "" +"In the :guilabel:`Rent Online` section, there are options to configure a " +":guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability " +"days`, or days during which pickup and return are not possible." +msgstr "" + +#: ../../content/applications/sales/rental.rst:61 +msgid "Rental products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:63 +msgid "" +"To view all products that can rented in the database, navigate to " +":menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be" +" Rented` search filter appears in the search bar." +msgstr "" + +#: ../../content/applications/sales/rental.rst:66 +msgid "" +"Each product kanban card displays that product's name, rental price, and " +"product image (if applicable)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:70 +msgid "Rental pricing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:72 +msgid "" +"To adjust the rental pricing on a product, go to the :guilabel:`Products` " +"page in the *Rental* app, then select the desired product or click " +":guilabel:`New` to create a new product from scratch." +msgstr "" + +#: ../../content/applications/sales/rental.rst:75 +msgid "" +"On the product form, ensure the :guilabel:`Can be Rented` checkbox is " +"ticked. Then, open the :guilabel:`Rental prices` tab." +msgstr "" + +#: ../../content/applications/sales/rental.rst:83 +msgid "" +"If creating a rental product outside of the *Rental* app, just ensure the " +":guilabel:`Can be Rented` checkbox is ticked on the product form. By " +"default, this checkbox is ticked whenever a product is created directly in " +"the *Rental* application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:90 +msgid "" +"Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, " +"designate custom rental prices and rental periods for the product." +msgstr "" + +#: ../../content/applications/sales/rental.rst:93 +msgid "" +"To add pricing for a rental, click :guilabel:`Add a price`. Then, choose a " +"*pricing period* (:dfn:`the unit of duration of the rental`) in the " +":guilabel:`Period` column, or create a new pricing period by typing in the " +"name and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:97 +msgid "" +"Next, decide whether or not to apply this custom rental price to a specific " +":guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:99 +msgid "" +"Lastly, enter the desired :guilabel:`Price` for that specific " +":guilabel:`Period`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:102 +msgid "" +"There is no limit to how many pricing lines can be added. Multiple pricing " +"options for rental products are typically used to give discounts for " +"customers who agree to longer rental durations." +msgstr "" + +#: ../../content/applications/sales/rental.rst:105 +msgid "" +"To delete any rental pricing option, click the :guilabel:`🗑️ (trash)` icon, " +"and that row is deleted." +msgstr "" + +#: ../../content/applications/sales/rental.rst:109 +msgid "Reservations" +msgstr "" + +#: ../../content/applications/sales/rental.rst:111 +msgid "" +"Under the :guilabel:`Reservations` section of the :guilabel:`Rental prices` " +"tab, there is the option to configure additional fines for any " +":guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to " +"return a rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:115 +msgid "" +"There is also the option to set a :guilabel:`Security Time`, expressed in " +"hours, to make the rental product temporarily unavailable between two rental" +" orders. Such a feature may prove useful if maintenance or cleaning is " +"required between rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:120 +msgid "Price computing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:122 +msgid "" +"Odoo always uses two rules to compute the price of a product when a rental " +"order is created:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:124 +msgid "Only one price line is used." +msgstr "" + +#: ../../content/applications/sales/rental.rst:125 +msgid "The cheapest line is selected." +msgstr "" + +#: ../../content/applications/sales/rental.rst:128 +msgid "Consider the following rental pricing configuration for a product:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:130 +msgid "1 day: $100" +msgstr "" + +#: ../../content/applications/sales/rental.rst:131 +msgid "3 days: $250" +msgstr "" + +#: ../../content/applications/sales/rental.rst:132 +msgid "1 week: $500" +msgstr "" + +#: ../../content/applications/sales/rental.rst:134 +msgid "" +"A customer wants to rent this product for eight days. What price will they " +"pay?" +msgstr "" + +#: ../../content/applications/sales/rental.rst:136 +msgid "" +"After an order is created, Odoo selects the second line as this is the " +"cheapest option. The customer has to pay three times '3 days' to cover the " +"rental's eight days, for a total of $750." +msgstr "" + +#: ../../content/applications/sales/rental.rst:142 +msgid "Rental orders" +msgstr "" + +#: ../../content/applications/sales/rental.rst:144 +msgid "" +"To create a rental order in the *Rental* app, navigate to " +":menuselection:`Rental app --> Orders --> Orders`, and click " +":guilabel:`New`. Doing so reveals a blank rental order form to be filled in " +"accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Sample of a filled out rental order available in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:152 +msgid "" +"Start by adding a :guilabel:`Customer`, then configure the desired duration " +"of the rental in the :guilabel:`Rental period` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:155 +msgid "" +"To adjust the rental duration, click the first date in the :guilabel:`Rental" +" period` field, and select the range of dates to represent the rental " +"duration from the pop-up calendar form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Sample of a rental period calendar pop-up window in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:163 +msgid "" +"Once complete, click :guilabel:`Apply` in the calendar pop-up form. " +"Following that, the pop-up form disappears, and the designated time period " +"of the rental is represented in the :guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:167 +msgid "" +"Next, add a rental product in the :guilabel:`Order Lines` tab, by clicking " +":guilabel:`Add a product`, and selecting the desired rental product to add " +"to the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst:171 +msgid "" +"If a rental product is added *before* the :guilabel:`Rental period` field " +"has been properly configured, the user can *still* adjust the " +":guilabel:`Rental period` field accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:174 +msgid "" +"Simply select the desired range of dates to represent the duration of the " +"rental, then click :guilabel:`Update Rental Prices` in the " +":guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The update rental prices option that appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:181 +msgid "" +"Doing so reveals a :guilabel:`Confirmation` pop-up window. If everything is " +"correct, click :guilabel:`Ok`, and Odoo recalculates the rental price " +"accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:184 +msgid "" +"Once all the information has been entered correctly on the rental order " +"form, click the :guilabel:`Send by Email` button to send the quotation to " +"the customer, or click the :guilabel:`Confirm` button to confirm the order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:189 +msgid "Customer signature" +msgstr "" + +#: ../../content/applications/sales/rental.rst:191 +msgid "" +"Upon confirming a rental order, the :guilabel:`Sign Documents` button " +"appears. This gives the ability to request the customer sign a rental " +"agreement, outlining the arrangement between the company and customer, " +"*before* they pick up the rental product(s)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:195 +msgid "" +"Such documents can ensure everything is returned on-time and in its original" +" condition." +msgstr "" + +#: ../../content/applications/sales/rental.rst:198 +msgid "" +"The :guilabel:`Sign Documents` button/option **only** appears if the " +":guilabel:`Digital Documents` feature has been activated in the *Rental* " +"application settings. To do so, navigate to :menuselection:`Rental app --> " +"Configuration --> Settings`, activate :guilabel:`Digital Documents`, and " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:204 +msgid "" +"This feature also requires the :doc:`Sign <../finance/sign>` app. If " +"necessary, Odoo automatically installs it after activating the " +":guilabel:`Digital Documents` setting." +msgstr "" + +#: ../../content/applications/sales/rental.rst:207 +msgid "" +"To request a customer signature on a rental agreement, select a confirmed " +"rental order, and click the :guilabel:`Sign Documents` button to reveal a " +":guilabel:`Sign Documents` pop-up window." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The Sign Documents pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:214 +msgid "" +"From here, select the desired document from the :guilabel:`Document " +"Template` field. Then, click :guilabel:`Sign Document`. Doing so reveals a " +":guilabel:`New Signature Request` pop-up window." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The New Signature Request pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:221 +msgid "" +"Upon confirming the information in the :guilabel:`New Signature Request` " +"pop-up form, click :guilabel:`Sign Now` to initiate the signing process." +msgstr "" + +#: ../../content/applications/sales/rental.rst:224 +msgid "" +"A separate page is then revealed, showcasing the document to be signed, " +"which is accessible to the customer via the customer portal." +msgstr "" + +#: ../../content/applications/sales/rental.rst:227 +msgid "" +"Odoo guides the customer through the signing process with clear, clickable " +"indicators, and allows them to create electronic signatures to quickly " +"complete the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The adopt your signature pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:234 +msgid "" +"Once the document has been signed and completed, click the " +":guilabel:`Validate & Send Completed Document` button at the bottom of the " +"document." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The validate and send completed document button in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:241 +msgid "" +"Upon clicking the :guilabel:`Validate & Send Completed Document` button, " +"Odoo presents the option to download the signed document for record-keeping " +"purposes, if necessary." +msgstr "" + +#: ../../content/applications/sales/rental.rst:245 +msgid "`Odoo Tutorials: Sign `_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:250 +msgid "Pickup products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:252 +msgid "" +"When a customer picks up the product(s), navigate to the appropriate rental " +"order, click the :guilabel:`Pickup` button, and then click " +":guilabel:`Validate` in the :guilabel:`Validate a pickup` pop-up form that " +"appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:256 +msgid "" +"Doing so places a :guilabel:`Picked-up` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:259 +msgid "Return products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:261 +msgid "" +"When a customer returns the product(s), navigate to the appropriate rental " +"order, click the :guilabel:`Return` button, and validate the return by " +"clicking :guilabel:`Validate` in the :guilabel:`Validate a return` pop-up " +"form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:265 +msgid "" +"Doing so places a :guilabel:`Returned` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:268 +msgid "Print pickup and return receipts" +msgstr "" + +#: ../../content/applications/sales/rental.rst:270 +msgid "" +"Pickup and return receipts can be printed for customers when they pick up " +"and/or return rental products." +msgstr "" + +#: ../../content/applications/sales/rental.rst:273 +msgid "" +"To print pickup and/or return receipts, navigate to the appropriate rental " +"order, click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The pickup and return receipt print option in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:280 +msgid "" +"From this drop-down menu, hover over the :guilabel:`Print` option to reveal " +"a sub-menu. Then select :guilabel:`Pickup and Return Receipt`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:283 +msgid "" +"Odoo generates and downloads a PDF, detailing all information about the " +"current status of the rented item(s)." +msgstr "" + +#: ../../content/applications/sales/sales.rst:10 +msgid "" +"**Odoo Sales** is the application to run your sales process (from quotation " +"to sales order) and deliver and invoice what has been sold." +msgstr "" + +#: ../../content/applications/sales/sales.rst:14 +msgid "" +"`Odoo Tutorials: Sales Tutorials `_" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector.rst:5 +msgid "Amazon Connector" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:3 +msgid "Amazon Connector features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:5 +msgid "" +"The *Amazon Connector* synchronizes orders between Amazon and Odoo, which " +"considerably reduces the amount of time spent manually entering Amazon " +"orders (from the Amazon Seller account) into Odoo. It also allows users to " +"accurately keep track of Amazon sales in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:10 +msgid "Supported features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:12 +msgid "The Amazon Connector is able to:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:14 +msgid "" +"Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM), and " +"their order items, which include:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:17 +msgid "product name, description, and quantity" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:18 +msgid "shipping costs for the product" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:19 +msgid "gift wrapping charges" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:21 +msgid "" +"Create any missing partner related to an order in Odoo (contact types " +"supported: contact and delivery address)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:24 +msgid "Notify Amazon of confirmed shipment in Odoo (FBM) to get paid." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:26 +msgid "" +"Synchronize (Odoo to Amazon) all available quantities of your products " +"(FBM)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:28 +msgid "Support multiple seller accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:30 +msgid "Support multiple marketplaces per seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:32 +msgid "" +"The following table lists capabilities provided by Odoo when using the " +"Amazon Connector:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Fulfilled By Amazon (FBA)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Fulfilled By Merchant (FBM)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "**Orders**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize shipped and canceled orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize unshipped and canceled orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "**Shipping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "" +"Shipping cost is computed by Amazon, and included in the synchronized order." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "" +"Shipping cost is computed by Amazon and included in the synchronized orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "Shipping done by Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "" +"A delivery order is automatically created in Odoo for each new order. Once " +"it has been processed in Odoo, the status is then synchronized in Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "**Gift Wrapping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Handled by Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "" +"Cost is computed by Amazon, and included in the synchronized order. Gift " +"message is added on a line of the order and on the delivery order. Then it " +"is up to the user." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "**Stock Management**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "" +"Managed by Amazon, and synchronized with a virtual location to follow it in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "Managed in Odoo Inventory app, and synchronized with Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "**Delivery Notifications**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Send by Amazon, based on delivery status synchronized from Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +msgid "" +"The Amazon Connector is designed to synchronize the data of sales orders. " +"Other actions, such as downloading monthly fees reports, handling disputes, " +"or issuing refunds, **must** be managed from the *Amazon Seller Central*, as" +" usual." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +msgid "Supported marketplaces" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:75 +msgid "The Amazon Connector supports all the current marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:77 +msgid "" +"If a marketplace is not listed in your Amazon marketplaces, it's possible to" +" :ref:`add a new marketplace `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:81 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 +msgid ":doc:`setup`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 +msgid ":doc:`manage`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 +msgid "Amazon order management" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 +msgid "Order synchronization" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 +msgid "" +"Orders are automatically fetched from Amazon, and synchronized in Odoo, at " +"regular intervals." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:10 +msgid "" +"The synchronization is based on the Amazon status: only orders whose status " +"has changed since the last synchronization are fetched from Amazon. This " +"includes changes on either end (Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:13 +msgid "" +"For *FBA* (Fulfilled by Amazon), only *Shipped* and *Canceled* orders are " +"fetched." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 +msgid "" +"For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and " +"*Canceled* orders. For each synchronized order, a sales order and customer " +"are created in Odoo (if the customer is not already registered in the " +"database)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 +msgid "" +"When an order is canceled in Amazon, and was already synchronized in Odoo, " +"the corresponding sales order is automatically canceled in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:24 +msgid "Force synchronization" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26 +msgid "" +"In order to force the synchronization of an order, whose status has **not** " +"changed since the previous synchronization, start by activating the " +":ref:`developer mode `. This includes changes on either end " +"(Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 +msgid "" +"Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> " +"Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon " +"Accounts`), and modify the date under :menuselection:`Orders Follow-up --> " +"Last Order Sync`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:34 +msgid "" +"Be sure to pick a date that occurs prior to the last status change of the " +"desired order to synchronize and save. This will ensure synchronization " +"occurs correctly." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:39 +msgid "" +"To immediately synchronize the orders of an Amazon account, switch to " +":ref:`developer mode `, head to the Amazon account in Odoo, " +"and click :guilabel:`Sync Orders`. The same can be done with pickings by " +"clicking :guilabel:`Sync Pickings`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:44 +msgid "Manage deliveries in FBM" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 +msgid "" +"Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a " +"picking is instantly created in the *Inventory* app, along with a sales " +"order and customer record. Then, decide to either ship all the ordered " +"products to the customer at once, or ship products partially using " +"backorders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:50 +msgid "" +"When a picking related to the order is confirmed, a notification is then " +"sent to Amazon, who, in turn, notifies the customer that the order (or a " +"part of it) is on its way." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 +msgid "" +"Amazon requires users to provide a tracking reference with each delivery. " +"This is needed to assign a carrier." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 +msgid "" +"If the carrier doesn't automatically provide a tracking reference, one must " +"be set manually. This rule applies to all Amazon marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:61 +msgid "" +"If the chosen carrier isn't supported by Odoo, a carrier with the same name " +"can still be created (e.g. create a carrier named `easyship`). The name used" +" is **not** case sensitive, but be mindful to avoid typos. If there are " +"typos, Amazon will **not** recognize them. Next, create a delivery carrier " +"named `Self Delivery` to inform Amazon that the user will make the " +"deliveries. Even with this route, a tracking reference still **must** be " +"entered. Remember, the customer is notified by email about the delivery, and" +" the carrier, along with the tracking reference, are displayed in the email " +"to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:70 +msgid "" +":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75 +msgid "Manage errors when synchronizing deliveries" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:77 +msgid "" +"Sometimes, Amazon can fail to correctly process all the information sent by " +"Odoo. In this case, Odoo sends an email listing all the shipments that " +"failed and the errors Amazon sent with them. In addition, these shipments " +"are flagged with a :guilabel:`Synchronization with Amazon failed` tag." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 +msgid "" +"Usually, the error can be corrected directly in the Amazon backend or in " +"Odoo. If the problem is corrected in Odoo, synchronize the shipment again " +"using the :guilabel:`Retry Amazon Sync` button." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:85 +msgid "" +"It might happen that Odoo receives a notification from Amazon saying that " +"some delivery information was not processed, but without specifying which " +"shipments were affected. In that case, all the shipments in an unknown state" +" will be treated as if they failed to synchronize. Once Odoo receives a " +"notification from Amazon saying that a shipment was processed, its tag will " +"change to :guilabel:`Synchronized with Amazon`. To speed up this process, on" +" your Amazon account, click on :guilabel:`Sync Orders` to manually " +"synchronize these orders, or click on :guilabel:`Recover Order` and enter " +"the relevant Amazon Order Reference." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:94 +msgid "Follow deliveries in FBA" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +msgid "" +"When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock " +"move is recorded in the *Inventory* app for each sales order item. That way," +" it's saved in the system." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:99 +msgid "" +"Inventory managers can access these stock moves by navigating to " +":menuselection:`Inventory app --> Reporting --> Moves History`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102 +msgid "" +"For FBA orders, the stock move is automatically created in Odoo by the " +"Amazon connector, thanks to the shipping status of Amazon. When sending new " +"products to Amazon, the user should manually create a picking (delivery " +"order) to transfer these products from their warehouse to the Amazon " +"location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:107 +msgid "" +"To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after " +"replenishing stock. An automated replenishment from reordering rules can " +"also be triggered on the Amazon location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:110 +msgid "" +"The Amazon location is configurable by accessing the Amazon account managed " +"in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales" +" app --> Configuration --> Settings --> Connectors --> Amazon Sync --> " +"Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 +msgid "" +"All accounts of the same company use the same Amazon location, by default. " +"However, it is possible to follow the stock filtered by marketplace." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:117 +msgid "" +"To do that, first remove the marketplace, where the desired stock to follow " +"separately can be found, from the list of synchronized marketplaces, which " +"can be found by navigating to :menuselection:`Sales app --> Configuration " +"--> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:122 +msgid "" +"Next, create another registration for this account, and remove all " +"marketplaces--- **except** the marketplace this is desired to be isolated " +"from the others." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:125 +msgid "" +"Lastly, assign another stock location to the second registration of the " +"account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128 +msgid "Invoice and register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 +msgid "Issue invoices" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133 +msgid "" +"Due to Amazon's policy of not sharing customer email addresses, it is " +"**not** possible to send invoices directly to Amazon customers from Odoo. " +"However, it **is** possible to manually upload the generated invoices from " +"Odoo to the Amazon back-end." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:137 +msgid "" +"Additionally, for B2B clients, it is currently required to manually retrieve" +" VAT numbers from the Amazon back-end **before** creating an invoice in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:141 +msgid "" +"For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: " +"invoices created from Amazon sales orders are **not** synchronized with " +"TaxCloud, since Amazon already includes them in its own tax report to " +"TaxCloud." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:146 +msgid "TaxCloud integration will be decommissioned in Odoo 17+." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 +msgid "Register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151 +msgid "" +"Since customers pay Amazon as an intermediary, creating a dedicated *Bank* " +"journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* " +"intermediary account is recommended." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:154 +msgid "" +"Additionally, as Amazon makes a single monthly payment, selecting all the " +"invoices linked to a single payment is necessary when registering payments." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:157 +msgid "" +"To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon " +"payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment " +"Method`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:160 +msgid "" +"Then, select all the generated payments, and click :menuselection:`Actions " +"--> Create batch payment --> Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:164 +msgid "" +"This same action can be performed with vendor bills from Amazon dedicated to" +" commissions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 +msgid "" +"When the balance is received in the bank account at the end of the month, " +"and the bank statements are recorded, credit the Amazon intermediary account" +" by the amount received." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:170 +msgid "Follow Amazon sales in sales reporting" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 +msgid "" +"On the Amazon account profile in Odoo, a sales team is set under the " +":guilabel:`Order Follow-up` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:175 +msgid "" +"This gives quick access to important metrics related to sales reporting. By " +"default, the Amazon account's sales team is shared between all of the " +"company's accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:178 +msgid "" +"If desired, the sales team on the account can be changed for another, in " +"order to perform a separate reporting for the sales of this account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:182 +msgid "It is also possible to perform reporting on a per-marketplace basis." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 +msgid "" +"First, remove the desired marketplace from the list of synchronized " +"marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:186 +msgid "" +"To access the list of synchronized marketplaces in Odoo, navigate to " +":menuselection:`Sales app --> Configuration --> Settings --> Connectors --> " +"Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:189 +msgid "" +"Then, create another registration for this account, and remove all other " +"marketplaces **except** the one to isolate." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:192 +msgid "" +"Lastly, assign another sales team to one of the two registrations of the " +"account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:195 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 +msgid ":doc:`features`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:3 +msgid "Amazon Connector configuration" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:5 +msgid "" +"Odoo allows users to register an Amazon seller account in the database, but " +"the user **must** have a paid Amazon Seller account prior to completing the " +"configuration." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:8 +msgid "" +"Set up a paid Seller account on Amazon by first logging into the Amazon " +"platform, and navigating to :menuselection:`Account \\& Lists --> Start a " +"Selling Account` from the drop-down menu located in the header section." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:12 +msgid "" +"Then on the :guilabel:`Sell with Amazon` page, follow the sign-up process " +"and finally proceed to follow the instructions below to register and link " +"that Amazon Seller account in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:16 +msgid "`Sell with Amazon `_" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:19 +msgid "Connect Amazon Seller account to Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:23 +msgid "" +"To connect an Amazon Seller account in Odoo, navigate to " +":menuselection:`Sales app --> Configuration --> Settings --> Connectors " +"section`, activate the :guilabel:`Amazon Sync` feature, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:27 +msgid "" +"Then, return to :menuselection:`Sales app --> Configuration --> Settings -->" +" Connectors section`, and click on the :guilabel:`Amazon Accounts` link " +"under the :guilabel:`Amazon Sync` setting." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "" +"The Amazon Accounts link beneath the Amazon Sync settings in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:34 +msgid "" +"Doing so reveals a separate :guilabel:`Amazon Accounts` page. From here, " +"click :guilabel:`New` to create and link a new Amazon account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:37 +msgid "" +"On the blank :guilabel:`Amazon Account` form page, start by choosing a name " +"for the account (e.g. `American Marketplace`). Then, in the " +":guilabel:`Credentials` tab, select the marketplace on which the seller " +"account was initially created from the :guilabel:`Home Marketplace` drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "A typical Amazon Account form page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:45 +msgid "" +"After saving, the field in the :guilabel:`Credentials` tab is replaced by a " +":guilabel:`Link with Amazon` button." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "" +"A typical Amazon Account form page and Link with Amazon button in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:52 +msgid "" +"Clicking that button redirects to either the Amazon login page, or directly " +"to the required consent page, if the user is already logged in to Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:55 +msgid "On the login page, log in to the desired Amazon seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:57 +msgid "" +"On the consent page, confirm that Amazon is allowed to give Odoo access to " +"the account and related data." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:60 +msgid "" +"Upon confirmation, Amazon returns the user to Odoo, and the account has been" +" registered." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:62 +msgid "" +"With the Amazon account successfully registered, the marketplaces available " +"to this specific account are synchronized with Odoo and listed under the " +":guilabel:`Marketplaces` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:65 +msgid "" +"If desired, remove items from the list of synchronized marketplaces to " +"disable synchronization." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:68 +msgid "Amazon orders in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:70 +msgid "" +"When an Amazon order is synchronized, up to three line items are created on " +"the sales order in Odoo. Each one represents a product sold on Amazon: one " +"for the product that was sold on Amazon Marketplace, one for the shipping " +"charges (if any), and one for the gift wrapping charges (if any)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 +msgid "" +"The selection of a database product for a sales order item is done by " +"matching its :guilabel:`Internal Reference` (a customizable product " +"reference idenifier in Odoo, like `FURN001`) with the Amazon *SKU* for " +"marketplace items, the Amazon *Shipping Code* for delivery charges, and the " +"Amazon *Gift Wrapping* code for gift wrapping charges." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:81 +msgid "" +"For marketplace products, pairings are saved as *Amazon Offers*, which are " +"listed under the :guilabel:`Offers` smart button on the account form." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "The Amazon Offers smart button on the account form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 +msgid "" +"Offers are automatically created when the pairing is established, and " +"they're used for subsequent orders to lookup SKUs. If no offer with a " +"matching SKU is found, :ref:`the internal reference is used instead " +"`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 +msgid "" +"It's possible to force the pairing of a marketplace item with a specific " +"product, by changing either the product or the SKU of an offer to ensure " +"they match. The offer can be manually created if it was not automatically " +"done yet." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:97 +msgid "" +"This is useful if the internal reference is not used as the SKU, or if the " +"product sells under different conditions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:100 +msgid "" +"If no database product with a matching internal reference is found for a " +"given Amazon SKU or gift wrapping code, then a default database product, " +"*Amazon Sale*, is used. The same is done with the default product *Amazon " +"Shipping* if no database product is found for a given Amazon shipping code." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:105 +msgid "" +"To modify default products, activate the :ref:`developer mode `, and navigate to :menuselection:`Sales app --> Configuration --> " +"Settings --> Connectors --> Amazon Sync --> Default Products`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:110 +msgid "Product tax configuration" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:112 +msgid "" +"To allow for tax reporting of Amazon sales with Odoo, the taxes applied to " +"the sales order items are those set on the product, or determined by the " +"fiscal position." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:115 +msgid "" +"Make sure to have the correct taxes set on your products in Odoo, or have it" +" done by a fiscal position, to avoid discrepancies in the subtotals between " +"*Amazon Seller Central* and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 +msgid "" +"As Amazon does not necessarily apply the same taxes as those configured in " +"Odoo, it may happen that order totals differ by a few cents between Odoo and" +" *Amazon Seller Central*. Those differences can be resolved with a write-off" +" when reconciling the payments in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:126 +msgid "Add a new marketplace" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:128 +msgid "" +"All marketplaces are supported by the Amazon Connector. To add a new " +"marketplace, proceed as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 +msgid "Activate the :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:132 +msgid "" +"Go to :menuselection:`Sales app --> Configuration --> Settings --> " +"Connectors --> Amazon Sync --> Amazon Marketplaces`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:134 +msgid "Click :guilabel:`New` to create a new marketplace record." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:135 +msgid "" +"Enter the Marketplace ID in the :guilabel:`API Idenifier` field, and select " +"the :guilabel:`Amazon Region` for your marketplace as described in the " +"`Amazon Documentation for marketplace IDs and regions `_, and the " +":guilabel:`Seller Central URL` as described in the `Amazon Documentation for" +" seller central URLs `_." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:140 +msgid "" +"Set the :guilabel:`Name` of the record to `Amazon.` to easily " +"retrieve it (e.g. `Amazon.se`). The :guilabel:`API Identifier`, the " +":guilabel:`Region` and the :guilabel:`Seller Central URL` fields should " +"respectively hold the *Marketplace ID*, the selected Amazon region, and the " +"*Seller Central URL* values from the Amazon Documentation." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:144 +msgid "" +"Once the marketplace is saved, update the Amazon Account configuration by " +"going to :menuselection:`Sales app --> Configuration --> Settings --> " +"Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:147 +msgid "" +"Select the account on which to use the new marketplace, go to the " +":guilabel:`Marketplaces` tab, and click on :guilabel:`Update available " +"marketplaces`. An animation should confirm the success of the operation. " +"Newly added marketplaces are automatically added to the list of synchronized" +" marketplaces. If the new marketplace is not added to the list, it means " +"that it is either incompatible or unavailable for the seller account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector.rst:5 +msgid "eBay Connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:3 +msgid "Linking existing listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:5 +msgid "" +"Once the eBay account is linked existing listings from within the eBay " +"seller account need to be added manually to the Odoo product listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:8 +msgid "" +"The process will be as follows: - Turn off eBay scheduled actions - Add " +"products and link listings - Turn on eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:14 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:28 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:15 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:6 +msgid "To learn more about the eBay connector visit these pages as well:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:32 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:19 +msgid ":doc:`troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:21 +msgid "Turn off eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:23 +msgid "" +"To start linking existing listings in eBay, first turn off the eBay " +"notifications in the scheduled actions in Odoo. The reason for this is so " +"that no orders or eBay data syncs during this process. The " +":guilabel:`Scheduled Actions` can be accessed by first activating " +":ref:`developer mode `. After doing so, go to " +":menuselection:`Settings --> Technical --> Automation --> Scheduled " +"Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:30 +msgid "" +":doc:`../../../general/developer_mode` must be activated to ensure the " +"technical menu appears for the user." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:33 +msgid "" +"Disabling scheduled actions enables users to sync and validate eBay data " +"before receiving orders. The following are descriptions of scheduled actions" +" that need to be temporarily deactivated:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:36 +msgid "" +":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo" +" (based on :guilabel:`client_order_reference`, or :guilabel:`sales order " +"reference` field). This command also updates existing orders, where changes " +"we made in eBay. New and updated orders are then placed in draft mode. " +"Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:40 +msgid "" +":guilabel:`eBay: synchronize stock`: eBay displays Odoo's stock on hand." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:41 +msgid "" +":guilabel:`eBay: update categories`: eBay will push updated monthly " +"categories (only up to fourth layer; a manual update required for the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:44 +msgid "" +"To toggle off the eBay notification, select the entry from the " +":guilabel:`Scheduled Actions` list. Then, on the page, click the " +":guilabel:`Active` toggle button to turn it off." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:48 +msgid "Sync eBay categories" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:50 +msgid "" +"To ensure that Odoo's eBay products have all the categories available on " +"eBay, the eBay categories should be synced to Odoo next." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:53 +msgid "" +"Navigate to :menuselection:`Settings --> Technical --> Automation --> " +"Scheduled Actions`. Click into the scheduled action labeled: " +":guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`." +" This action will populate the :menuselection:`Sales --> Configuration --> " +"eBay Categories` menu item with all standard eBay product categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:59 +msgid "" +"Odoo only recognizes eBay category paths up to four layers deep. If a " +"product has a listing of more than four, the category field will only " +"populate up to the fourth layer." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:62 +msgid "" +"If product categories beyond four paths are required, users need to manually" +" add those paths. This has historically been done by getting a list of all " +"product categories beyond 4 paths, manually importing them into the Product " +"Category model in Odoo, then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:67 +msgid "" +"Users can import the remaining product categories into the eBay product " +"categories manually using using the :guilabel:`Action` menu and " +":guilabel:`Import` feature." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:71 +msgid "Link eBay listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:73 +msgid "" +"To add eBay listings in Odoo, either manually add products, using a listing " +"ID, or establish an automatic listing link between Odoo and eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:77 +msgid "" +"For more information on listing a product from scratch visit: :ref:`How to " +"list a product? `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:81 +msgid "Manual listing link" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:83 +msgid "" +"To add an eBay listing to products in Odoo, begin by going to " +":menuselection:`Sales app --> Products --> Products` and selecting the " +"desired product. Click on :guilabel:`Sell on eBay` (either in the " +":guilabel:`eBay` tab or under the :guilabel:`Product name`). Select " +":guilabel:`Save` if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:87 +msgid "" +"Still the product form, click :guilabel:`link to listing` in the top menu " +"and enter in listing ID from eBay in the pop up (the listing ID is in the " +"eBay product URL)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:91 +msgid "" +"An example URL would be as such: " +"`www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The " +"listing ID is `272222656444` in this case. Once the listing ID has been " +"entered the eBay listing information will sync into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:97 +msgid "Turn on eBay scheduled Actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:99 +msgid "" +"The next step is to turn on the eBay notifications in the scheduled actions " +"in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled " +"Actions` can be accessed by first activating :ref:`developer mode " +"` and go to :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:104 +msgid "" +"Turning on the following scheduled actions allows users to sync and validate" +" eBay data automatically." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:107 +msgid "" +":guilabel:`eBay: get new orders`: eBay will push all new orders not already " +"in Odoo (based on client_order_reference, or sales order reference field), " +"and will update orders if there has been a change from eBay. Orders will be " +"put in draft mode. Customers will be created if they are not already in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:111 +msgid "" +":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:112 +msgid "" +":guilabel:`eBay: update categories`: eBay will push updated monthly " +"categories (only up to fourth layer, will need to manually update the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:116 +msgid "" +"If an order comes in and the listing from the order is not linked to a " +"product, eBay will create a consumable product.product in its place. These " +"consumables should be altered on the *Sales Order* while in draft state to " +"represent a storable product, and then the user can link to the listing as " +"they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:127 +msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153 +msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:124 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 +msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 +msgid "How to list a product?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:7 +msgid "" +"In order to list a product on eBay and Odoo there are two methods in Odoo to" +" do so:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:9 +msgid "Make a product in Odoo and list the item eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:11 +msgid "" +"Click :guilabel:`List Item on eBay` in the top menu of the product template." +" The product template can be accessed by navigating to :menuselection:`Sales" +" app --> Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 +msgid "" +"List the item on eBay, then create the product in Odoo, and finally link " +"product to the item on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 +msgid "" +"Click :guilabel:`Link With Existing eBay Listing` in the top menu on the " +"product template.The product template can be accessed by navigating to " +":menuselection:`Sales app --> Product --> Product` and selecting the " +"individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:22 +msgid "" +"If an order comes in and the listing from the order is not linked to a " +"product, eBay will create a consumable product.product in its place. These " +"consumables should be altered on the *sales order* while in draft state to " +"represent a storable product, and then the user can link to the listing as " +"they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:31 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:10 +msgid ":doc:`linking_listings`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 +msgid "Listing without variation" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 +msgid "" +"Access the product template by navigating to :menuselection:`Sales app --> " +"Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:40 +msgid "" +"In order to list a product, select the :guilabel:`Sell on eBay` field on a " +"product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` " +"tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if " +"necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 +msgid "The eBay template form listed in the product template in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:48 +msgid "" +"When the :guilabel:`Use Stock Quantity` field is checked, the quantity set " +"on eBay will be the Odoo *Forecast Quantity* (Odoo *Inventory* app)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:51 +msgid "" +"The :guilabel:`Description Template` allows the administrator to use " +"templates in listings. The default template only use the :guilabel:`eBay " +"Description` field of the product. HTML can be used inside the " +":guilabel:`Description Template` and in the :guilabel:`eBay Description` in " +"Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in " +"the template and description. Simply type a forward slash `/` to reveal a " +"menu with formatting, layout, and text options. To add an image, type " +"`/image`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:58 +msgid "" +"To use images in the listing, another option is to add them as *Attachments*" +" on the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:62 +msgid "" +"For more information on template configuration in Odoo visit: " +":doc:`../../../general/email_communication/email_template`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 +msgid "Listing with variations" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68 +msgid "" +"When the :guilabel:`Sell on eBay` is checked on a product containing " +"variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the " +"eBay form is slightly different. Go to the :guilabel:`Variants` tab to or " +"click :guilabel:`Configure Variants` in the top menu to configure the " +"variant settings. Pricing can be configured for each variation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 +msgid "" +"When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, " +"Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in " +"which the :guilabel:`Fixed Price` can be entered, and the decision to " +":guilabel:`Publish on eBay` can be made for specific variants, along with " +"other options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 +msgid "" +"The fixed price listing type in the eBay tab on a product form in Odoo " +"sales." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:83 +msgid "Product identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85 +msgid "" +"Products identifiers such as EAN, UPC, Brand or MPN are required in most of " +"the eBay categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:88 +msgid "EAN and UPC identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 +msgid "" +"The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` " +"field of the product variant. If the :guilabel:`Barcode` field is empty or " +"is value is not valid, the EAN and UPC values will be set as 'Does not " +"apply' as recommended by eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:94 +msgid "" +"Barcodes can be found on the product template, under the the " +":guilabel:`General Information` tab. Access the product template, first, by " +"navigating to :menuselection:`Sales app --> Products --> Product` and " +"selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:99 +msgid "Listing with item specifics" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 +msgid "" +"In order to add item specifics, one should create a product attribute with a" +" single value in the :guilabel:`Attributes & Variants` tab on the product " +"form. Examples of item specifics include: `MPN` or `Brand`. The Brand and " +"MPN values are working as item specifics and should be defined in the " +":guilabel:`Attributes & Variants` tab on the product form. If these values " +"are not set, 'Does not apply' will be used for the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 +msgid "Process invoices and payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111 +msgid "Posting payment" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113 +msgid "" +"When eBay orders are placed they are always paid for up front, via the eBay " +"site. At no point will users pay for items on eBay through Odoo. Therefore, " +"once orders are synced into Odoo from eBay they are already paid for. Odoo's" +" invoicing and payment functionalities are not utilized. However, invoices " +"need to be created and marked as Paid to “close” the *Sales Order*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 +msgid "" +"Users can opt to mass create and post invoices in batches. To do so, " +"navigate to Quotations in the list view by going to :menuselection:`Sales " +"app --> Orders --> Quotations`. In the upper right corner, select the list " +"view icon. Hover over the icons to reveal the name of each. Then check the " +"boxes on the left that invoices should be made for and go to the " +":guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create " +"Invoices`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:124 +msgid "" +"A pop-up will appear and click on the :guilabel:`Create and view invoice` " +"button. A new screen will populate with the newly created invoices. Next, " +"select all of them by clicking on the box icon next to :guilabel:`Number` in" +" the header row of the list, this will select all the records. Then navigate" +" to the :guilabel:`Action` menu and click :guilabel:`Post entries`. " +"Following this step, a pop-up will appear and click on :guilabel:`Post " +"journal entries`. This will take the invoices out of *draft* and set them to" +" *posted*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:132 +msgid "Reconciling payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134 +msgid "" +"Users typically utilize PayPal to receive payment from eBay, and then send " +"lump sums from PayPal into their bank account. To reconcile this income, " +"users can reconcile the one PayPal transfer with all related invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:138 +msgid "" +"First navigate to the :guilabel:`Accounting Dashboard` by going to the " +":menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a" +" new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out " +"the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on " +":guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:143 +msgid "" +"For the :guilabel:`Ending Balance` field, enter the same account that was " +"entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, " +"open the new balance that needs to be reconciled. Under the tab marked: " +":guilabel:`Match Existing Entries` select the entries that are included in " +"this balance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:148 +msgid "" +"After adding all the necessary entries, click :guilabel:`Validate` to " +"complete the reconciliation. To verify the payment, navigate to " +":menuselection:`Customers --> Invoices` and select the desired customer " +"invoice. The *Paid* label should appear under the :guilabel:`Payment Status`" +" column." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:154 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 +msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 +msgid "eBay connector setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 +msgid "Overview" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 +msgid "" +"Odoo's eBay connector allows eBay listings to connect with Odoo products. " +"Once connected, :doc:`updates to the listings ` can be " +"made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* " +"are created in Odoo for the user to review and confirm. Once the sales order" +" is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull " +"products out of inventory, and allow the user to create invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 +msgid "eBay - Odoo linked fields" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 +msgid "" +"The following are eBay product details. Each of these eBay fields update " +"corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:27 +msgid "eBay URL" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:28 +msgid "eBay status" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 +msgid "Quantity sold" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:30 +msgid "Start date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:31 +msgid "Title" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:32 +msgid "Subtitle" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 +msgid "Item condition" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:34 +msgid "Category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:35 +msgid "Category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 +msgid "Store category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:37 +msgid "Store category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:38 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:39 +msgid "Seller profiles" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 +msgid "Postal code" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:41 +msgid "Shipping policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 +msgid "Listing type (fixed price or auction)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:44 +msgid "Starting price for Auction" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:45 +msgid "Buy it now price" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 +msgid "Fixed Price amount" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:48 +msgid "Use stock quantity" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:49 +msgid "Quantity on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:50 +msgid "Duration" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 +msgid "Allow best offer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 +msgid "Private listing" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 +msgid "eBay description" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 +msgid "eBay product image" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:55 +msgid "Country" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 +msgid "eBay terms" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 +msgid "" +"*Variations* group multiple products into one, with variation (or variant) " +"options. Variations can sync to Odoo's attributes and values. Variations " +"will appear in drop down menus near the top of the page when viewing an eBay" +" listing. These are comparable to product variants in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "An example on eBay of the variations that can be added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:68 +msgid "" +"*Item specifics*, located at the bottom of the listing, detail product-" +"specific information. These specifics don't sync with Odoo fields by " +"default; a development is required to link these fields." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Item specifics listed on an eBay product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:75 +msgid "" +"*Sandbox* and *Production* are terms that are used to categorize the eBay " +"environments as either still in development/testing (*Sandbox*) or for use " +"in the real instance of the database with real customer information/dataset " +"(*Production*). It is recommended to start first in the *Sandbox* to test, " +"and then following the processes below, create a *Production* instance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 +msgid "" +"eBay's sandbox environment can be accessed by navigating to `eBay's sandbox " +"portal `_ at `https://sandbox.ebay.com/`. eBay's " +"production environment can be accessed by navigating to `eBay.com portal " +"`_ or `https://www.ebay.com/`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:87 +msgid "" +"The environment selection **must** remain the same for all environment " +"settings on eBay and on Odoo throughout this setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:91 +msgid "eBay actions available on Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:93 +msgid "" +"The following are built-in actions in Odoo that add or update eBay listings:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 +msgid "" +"**List**/ **Link**: generate a new eBay listing with an Odoo product by " +"clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay" +" Listing`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 +msgid "" +":guilabel:`Revise item` button: after making changes to an eBay listing in " +"Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to" +" update the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:99 +msgid "" +"**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` " +"was not selected, a user can relist the item from Odoo. The start date will " +"reset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:101 +msgid "" +":guilabel:`End item's listing` button: end a listing on eBay directly from " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:102 +msgid "" +"**Unlink product listings**: users can unlink a product from the eBay " +"listing; the listing will stay intact on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:106 +msgid "Setup required on Odoo prior to eBay setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:108 +msgid "" +"To link eBay with Odoo, install the eBay module by navigating to the Odoo " +"dashboard and clicking into the :guilabel:`Apps` application. Search the " +"term `eBay` and install the `eBay Connector` module." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 +msgid "The following items must be configured before eBay is set up:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:114 +msgid "" +"In Odoo, create and configure products that are intended to be listed in " +"eBay. eBay does not import new products into Odoo. All products must first " +"be created in Odoo, and then linked to listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 +msgid "" +"Odoo does not allow multiple eBay listings to be linked per product in Odoo." +" If the company sells the same product for multiple listings, follow these " +"instructions:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 +msgid "" +"Set up one *base* product (noted in the :guilabel:`Component` field of the " +":abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull " +"from. This will be a storable product so stock can be kept. Highlighted in " +"green below, this product will be included in the kit on each subsequent " +"“linked” product below." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 +msgid "" +"Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the " +":abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type" +" will be determined by the company's accounting settings, as explained in " +"the Odoo documentation. Highlighted in yellow below, each product should " +"have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base " +"product as a :guilabel:`Component` of the kit. When this linked eBay product" +" is sold, the delivery order created will have the base product listed in " +"lieu of the linked product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:0 +msgid "Setting up bill of materials with base product and linked products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:138 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/management/bill_configuration/`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 +msgid "" +"eBay does not automatically create invoices for eBay orders that get pushed " +"into Odoo. Set invoicing policy on eBay products: invoicing policy will " +"dictate when the product can be invoiced. Since most eBay users collect " +"payment before the product is shipped, “invoice on ordered” will allow users" +" to mass create invoices for eBay orders every day." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:144 +msgid "" +"Set the :guilabel:`Outgoing Shipments` route for the warehouse to " +":guilabel:`Deliver goods directly (1 step)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:148 +msgid "" +"When the :guilabel:`Outgoing Shipments` route is set to two or three steps, " +"a known bug occurs: eBay wrongly marks orders as delivered when the pick " +"operation in Odoo is confirmed. The expected behavior is to mark orders as " +"delivered **after** the *delivery order* is confirmed. This mislabeling " +"prevents tracking numbers in eBay from being imported onto the delivery " +"order." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:152 +msgid "" +"If the Accounting/Invoicing apps are installed, practice registering payment" +" and reconciling invoices created from eBay orders with incoming eBay money." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:156 +msgid ":doc:`../../..//finance/accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:158 +msgid "" +"Generate a marketplace account deletion/closure notification token. To " +"begin, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`. Under the :guilabel:`eBay` heading, change the mode to " +":guilabel:`Production`, and input random text values for the " +":guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` " +"button under the :guilabel:`eBay Marketplace Account Deletion/Closure " +"Notifications` section. This token will be used during the setup on eBay for" +" the deletion/closure notifications configuration." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Generate a verification token in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:170 +msgid "Set up on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:173 +msgid "Set up eBay developer account" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:175 +msgid "" +"To start, create an eBay developer account via `eBay's developer portal " +"`_. This site requires a different login and" +" password than the eBay account, though the same email address can be used " +"to register. The verification to create a developer account is around 24 " +"hours." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:181 +msgid "Set up eBay keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:183 +msgid "" +"Once the eBay developer account is created, set up an application on `eBay's" +" developer portal `_. Next, navigate to the " +":guilabel:`Hi [username]` heading at top right of screen, then from the " +"drop-down menu options, click :guilabel:`Application Keysets`. Doing so " +"opens a pop-up that prompts the user to :guilabel:`Enter Application Title` " +"(up to fifty characters), and choose a development environment " +"(:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate " +"first keyset. This application title is not saved until the keyset is " +"generated. Click on :guilabel:`Create a keyset` to generate the keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:192 +msgid "" +"The newly created *production keyset* is disabled by default. Activate it by" +" subscribing to the eBay Marketplace 'account deletion or closure " +"notifications' or by applying to eBay for an exemption. Once enabled, the " +"database can make 5000 calls per day using this keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Disabled keyset present after creating a keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:201 +msgid "Configure account deletion / notification settings (Production)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:203 +msgid "" +"To configure notifications or delete the database on a production " +"environment, navigate to the `eBay developer portal " +"`_. Configure the account " +"deletion/notification settings in eBay by navigating to the `Hi [username]` " +"at top right of screen, then :guilabel:`Application Keysets`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:208 +msgid "" +"Next, click the :guilabel:`marketplace deletion/account closure " +"notification` option under the :guilabel:`Production` keyset column. Enter " +"an email under :guilabel:`Email to notify if marketplace account deletion " +"notification endpoint is down`. Click :guilabel:`Save` to enable the email." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:212 +msgid "" +"Following this action, enter the :guilabel:`Marketplace account deletion " +"notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in" +" Odoo by navigating to :menuselection:`Sales app --> Configuration --> " +"Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure " +"Notifications` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:217 +msgid "" +"Clicking the :guilabel:`Generate Token` button in Odoo below this field " +"creates a verification token for the eBay production environment. In Odoo, " +":guilabel:`Copy` the newly created token and navigate to eBay to fill in the" +" :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the " +":guilabel:`Event Notification Delivery Method`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Configuring account deletion / notification settings in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:226 +msgid "" +"After completing the above fields, click :guilabel:`Send Test Notification` " +"to test the new notifications. Proceed to the next step when the green check" +" mark appears. Revisit the above settings if the test post is not as " +"expected." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:230 +msgid "" +"After configuring notification settings, go back to the " +":menuselection:`Application Keys` page to generate production keysets." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:234 +msgid "Creating the keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:236 +msgid "" +"A successful setup of the notifications enables the ability to create " +"Production Keysets which are needed in the remainder of the Odoo " +"configuration. Navigate back to the :menuselection:`Application Keys` page " +"generate a production keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:240 +msgid "" +"The administrator is prompted to :menuselection:`Confirm the Primary " +"Contact`. Enter or confirm the account owner (the person legally responsible" +" for the eBay API License Agreement). Fill out :guilabel:`First Name`, " +":guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select " +"either the :guilabel:`Individual` or :guilabel:`Business` options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:246 +msgid "" +"The provided email address or phone number does **not** have to match the " +"account's. eBay uses this information to contacting the business or " +"individual in case of issues with user tokens. Additional contacts can be " +"added from the :guilabel:`Profile & Contacts` page on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:250 +msgid "" +"Click on :guilabel:`Continue to Create Keys` to confirm the primary contact." +" The :guilabel:`Application Keys` populates in a new screen and an email is " +"also sent to the developer account. An :guilabel:`App ID (Client ID)`, " +":guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Application keys are populated after creating the app in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:259 +msgid "" +"Copy these values down as they will be input into Odoo later in the process." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:262 +msgid "Create eBay user token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:264 +msgid "" +"Now, create a *user token* in eBay by navigating to the `Hi [username]` at " +"top right of screen, then :guilabel:`User Access Tokens`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Generate user token s on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:271 +msgid "" +"Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing " +"or :guilabel:`Production` for the live database. Maintain the same selection" +" for all environment settings on both eBay and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:275 +msgid "Next, select the radio button labeled :guilabel:`Auth'n'Auth`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:277 +msgid "" +"Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` " +"to get a user token in the chosen environment. This button varies based on " +"the selection made above for either :guilabel:`Sandbox` or " +":guilabel:`Production`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:281 +msgid "" +"Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal " +"Address`. Complete the required fields, which are :guilabel:`First Name`, " +":guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`," +" and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either " +":guilabel:`Individual` or :guilabel:`Business`. To complete the " +"confirmation, click :guilabel:`Sign into eBay to get a Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:288 +msgid "" +"eBay will contact this individual or business should there be any issues " +"with the application keys. Other contacts can be added on the " +":menuselection:`Profile & Contacts` eBay page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:291 +msgid "" +"The administrator will be redirected to either a sandbox or production sign-" +"in page for eBay. This login is different than the eBay developer's console," +" it is the eBay account where the items will be sold on. This email and/or " +"login can differ from the eBay developer account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:295 +msgid "" +"Enter the :guilabel:`Email` or :guilabel:`Username` for the eBay account and" +" sign into the eBay account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:299 +msgid "" +"Should an additional user be needed for the sandbox simulation, a test user " +"needs to be created. Visit `eBay's Register for Sandbox form " +"`_. Detailed instructions can " +"be found on eBay's help pages: `Create a test Sandbox user " +"`_." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:305 +msgid "Grant application access" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:307 +msgid "" +"After signing into the production or sandbox environment, eBay presents the " +"administrator with an *agreement* to grant access to the user's eBay data." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:310 +msgid "" +"Clicking :guilabel:`Agree` allows eBay to link the eBay account with the " +"*application programming interface* (API). This agreement can be changed at " +"any time by visiting eBay's account preferences." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:314 +msgid "" +"eBay has a timed sequence between signing in and agreeing to the terms for " +"the :abbr:`API (Application Programming Interface)` linkage to the account. " +"Once complete a :guilabel:`User Token` will populate on the " +":menuselection:`User Tokens` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:318 +msgid "" +"A :guilabel:`User Token` will populate on the screen. Make sure to copy this" +" token down as it will be used in the next steps along with the " +":guilabel:`Application Keyset`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "" +"Generated user token and API explorer link on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:326 +msgid "" +"Signing in to the eBay account is necessary to create to the token. The eBay" +" developer can also revoke the token by clicking on the :guilabel:`Revoke a " +"Token` link." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:330 +msgid "API explorer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:332 +msgid "" +"Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have " +"been created, a test can be executed via the `API Explorer " +"`_ to " +"ensure that the :abbr:`API (Application Programming Interface)` is " +"configured correctly. This test will execute a simple search using the " +":abbr:`API (Application Programming Interface)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:338 +msgid "" +"To begin the :abbr:`API (Application Programming Interface)` test, click on " +":guilabel:`Get OAuth Application Token`. This will populate the key into the" +" :guilabel:`Token` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:341 +msgid "" +"A basic search function is set to execute. Click on :guilabel:`Execute` to " +"complete the test. A successful test will respond with a :guilabel:`Call " +"Response` of `200 OK` with a corresponding :guilabel:`Time`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:346 +msgid "Entering credentials into Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:348 +msgid "" +"The previously copied :guilabel:`User Token` and :guilabel:`Application " +"Keyset` are now ready to be entered into the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:351 +msgid "" +"Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> " +"Configuration --> Settings --> eBay`) and paste the following credentials " +"from eBay into the corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:358 +msgid "Platform" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:359 +msgid "Dev Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:360 +msgid "Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:361 +msgid "App Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:362 +msgid "Cert Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:363 +msgid "eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:364 +msgid "Dev ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:365 +msgid "User Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:366 +msgid "App ID (Client ID)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:367 +msgid "Cert ID (Client Secret)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:368 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:102 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:369 +msgid "Developer Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:370 +msgid "Production/Sandbox Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:371 +msgid "Production/Sandbox App Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:372 +msgid "Production/Sandbox Cert Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:375 +msgid "" +"The :guilabel:`Application Keyset` can be accessed by going to `eBay's " +"developer portal `_ and navigate to the `Hi " +"[username]` at top right of screen, then click on :guilabel:`Application " +"Keysets`. Get to the *User Token* in eBay by navigating to the `Hi " +"[username]` at top right of screen, then :guilabel:`User Access Tokens` and " +"click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also" +" be accessed by clicking on :guilabel:`User Tokens` from the " +":menuselection:`Application Keys` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:382 +msgid "" +"Confirm that the setup is correct by saving the credentials in Odoo. Once " +"the initial setup is complete, a new menu tab in products will appear called" +" `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` " +"documentation on how to list products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:387 +msgid "" +"Sync product categories by clicking :guilabel:`Product Categories`. After " +"syncing, a new menu item, `eBay Category`, appears available for products to" +" be configured with. These eBay categories are imported from the Odoo " +"database and are available when listing an item on eBay through Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:393 +msgid "" +"If Product Categories beyond four paths are required, users will need to " +"manually add those paths. This has historically been done by getting a list " +"of all product categories beyond four paths, manually importing them into " +"the Product Category model in Odoo, and then linking them individually to " +"the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:399 +msgid "Now that the setup is complete, proceed to either:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:401 +msgid ":doc:`Create listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:402 +msgid ":doc:`Link existing listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:3 +msgid "Troubleshooting eBay connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:13 +msgid "Accept account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:15 +msgid "" +"Since September 2021, **eBay requires supporting customer account " +"deletion/closure notifications**. As such, when eBay receives an account " +"request for deletion, all eBay partners must confirm the reception of the " +"request and take further action if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:19 +msgid "" +"Odoo has a notification endpoint to receive those notifications, confirm the" +" reception of the request, and handle the first set of actions to anonymize " +"the account details in *Contacts* and remove the customer's access to the " +"portal." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:24 +msgid "" +"Make sure to correctly :ref:`set up the subscription to the marketplace " +"account deletion notifications ` as eBay may temporarily disable the related eBay account " +"until the subscription is completed." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:29 +msgid "Verify the installation of Odoo is up to date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:31 +msgid "" +"In order to activate the endpoint, the module *eBay Connector - Account " +"Deletion* must be installed. If the Odoo database was first created after " +"September 2021, the module is installed automatically and the administrator " +"can proceed to the :ref:`next step `." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:36 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:38 +msgid "" +"The notification endpoint is made available through a new Odoo module; to be" +" able to install it, the administrator must make sure that the Odoo source " +"code is up-to-date." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:41 +msgid "" +"If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is " +"already up-to-date, so proceed to the next step." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 +msgid "" +"If the company uses Odoo with an on-premise setup or through a partner, then" +" the administrator must update the installation as detailed in :doc:`this " +"documentation page ` or by contacting an " +"integrating partner." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:50 +msgid "" +"New modules must be *discovered* by the Odoo instance to be available in the" +" :menuselection:`Apps` menu." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:53 +msgid "" +"To do so, activate the :ref:`developer mode `, and go to " +":menuselection:`Apps -> Update Apps List`. A wizard will ask for " +"confirmation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:57 +msgid "Install the eBay Connector - Account Deletion update" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:60 +msgid "" +"**Never** install new modules in the production database without testing " +"them in a duplicate or staging environment. For Odoo.com customers, a " +"duplicate database can be created from the database management page. For " +"Odoo.sh users, the administrator should use a staging or duplicate database." +" For on-premise users, the administrator should use a staging environment - " +"contact the integrating partner for more information regarding how to test a" +" new module in a particular setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:67 +msgid "" +"To install the module, go to the :menuselection:`Apps` menu, remove the " +"`Apps` search facet and search for `eBay`. If the module *eBay Connector - " +"Account Deletion* is present and marked as installed, the Odoo database is " +"already up-to-date and the administrator can proceed with the next step. If " +"it is not yet installed, install it now." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:75 +msgid "Retrieve endpoint details from Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:77 +msgid "" +"The endpoint details can be found in :menuselection:`Sales --> Configuration" +" --> Settings --> eBay`. First, input random text values for the " +":guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. " +"Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification " +"Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:89 +msgid "Subscribe to account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:91 +msgid "" +"Navigate to the `eBay developer portal `_. " +"Configure the account deletion/notification settings in eBay by navigating " +"to the `Hi [username]` at the top right of screen, then go to " +":guilabel:`Alerts & Notifications`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:99 +msgid "" +"To subscribe to deletion/closure notifications, eBay needs a few details:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:101 +msgid "" +"An *email address* to send notifications to if the endpoint is unreachable." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:102 +msgid "The *endpoint details*:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:104 +msgid "The URL to Odoo's account deletion notification endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:105 +msgid "A verification token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Dedicated fields to enter the endpoint details" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:112 +msgid "" +"The administrator can edit the last two fields once the email address field " +"is filled out." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:115 +msgid "Verify the connectivity with the endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:117 +msgid "" +"After setting the retrieved endpoint details in eBay's dashboard, consider " +"testing the connectivity with the :guilabel:`Send Test Notification` button." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:120 +msgid "" +"The following confirmation message should be received: \"A test notification" +" was sent successfully!\"" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Button to send test notification" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing.rst:5 +msgid "Invoicing Method" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 +msgid "Down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 +msgid "" +"A down payment is a partial payment made by the buyer when a sales contract " +"is concluded. This implies both parties' (seller and buyer) full commitment " +"to honor the contract." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 +msgid "" +"With a down payment, the buyer pays a portion of the total amount owed while" +" agreeing to pay the remaining amount at a later date. In turn, the seller " +"provides goods or services to the buyer after accepting the down payment, " +"trusting that the remaining amount will be paid later on." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 +msgid "Create invoices" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 +msgid "" +"When a sales order is confirmed, the option to create an invoice becomes " +"available, via the :guilabel:`Create Invoice` button, located in the upper-" +"left corner of the sales order form. When clicked, a :guilabel:`Create " +"invoices` pop-up appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "Create invoices pop-up form that appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 +msgid "" +"Invoices are automatically created as drafts, so they can be reviewed before" +" validation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:26 +msgid "" +"On the :guilabel:`Create invoices` pop-up, there are 3 options to choose " +"from in the :guilabel:`Create Invoice` field:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +msgid ":guilabel:`Regular invoice`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:42 +msgid ":guilabel:`Down payment (percentage)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:31 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 +msgid ":guilabel:`Down payment (fixed amount)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 +msgid "" +"If :guilabel:`Regular Invoice` is selected, the other fields disappear, as " +"they only pertain to down payment configurations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 +msgid "Initial down payment request" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:40 +msgid "" +"On the :guilabel:`Create invoices` pop-up form, the down payment options " +"are:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:45 +msgid "" +"Once the desired down payment option is selected in the :guilabel:`Create " +"Invoice` field on the pop-up form, designate the desired amount, either as a" +" percentage or a fixed amount, in the :guilabel:`Down Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:49 +msgid "" +"Then, select the appropriate income account for the invoice in the " +":guilabel:`Income Account` field. Next, select a tax amount, if necessary, " +"in the :guilabel:`Customer Taxes` drop-down field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"A create invoices pop-up form with down payment fields filled in with " +"information." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 +msgid "" +"Once all fields are filled in with the desired information, click the " +":guilabel:`Create Draft Invoice` button. Upon clicking this button, Odoo " +"reveals the :guilabel:`Customer Invoice Draft`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:59 +msgid "" +"In the :guilabel:`Invoice Lines` tab of the :guilabel:`Customer Invoice " +"Draft`, the down payment that was just configured in the :guilabel:`Create " +"invoices` pop-up form appears as a :guilabel:`Product`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Down payment as a product in the invoice lines tab of a customer invoice " +"draft in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:68 +msgid "" +"When the :guilabel:`Down payment` product in the :guilabel:`Invoice Lines` " +"tab is clicked, Odoo reveals the product form for the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 +msgid "" +"By default, the :guilabel:`Product Type` of down payment products generated " +"for invoices are set as :guilabel:`Service`, with the :guilabel:`Invoicing " +"Policy` set to :guilabel:`Prepaid/Fixed Price`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Down payment product form with service product type and invoicing policy " +"field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:79 +msgid "This product can be edited/modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 +msgid "" +"If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the " +":guilabel:`Invoicing Policy`, an invoice will **not** be able to be created." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:86 +msgid "Example: request 50% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:89 +msgid "" +"The following example involves a 50% amount down payment on a product " +"(:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the " +":guilabel:`Invoicing Policy`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:0 +msgid "Cabinet with doors product form showcasing various details and fields." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:97 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:260 +#: ../../content/applications/sales/sales/invoicing/expense.rst:226 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:238 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:71 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:166 +msgid ":doc:`invoicing_policy`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 +msgid "" +"First, navigate to :menuselection:`Sales app --> New`, and add a " +":guilabel:`Customer` to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:102 +msgid "" +"Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, " +"and select the :guilabel:`Cabinet with Doors` product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "" +"When the order is confirmed (via the :guilabel:`Confirm` button), the " +"quotation turns into a sales order. Once this occurs, create and view the " +"invoice by clicking :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Cabinet with doors sales order that's been confirmed in the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "" +"Next, on the :guilabel:`Create invoices` pop-up window that appears, select " +":guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down " +"Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:116 +msgid "" +"The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are " +"*not* required fields, and they will *not* appear if they've already been " +"preconfigured in previous down payment requests." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:120 +msgid "" +"For more information, check out the documentation on :ref:`customer taxes " +"modification on down payments ` and :ref:`income account modification on down payments " +"`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:124 +msgid "" +"Lastly, click :guilabel:`Create Draft Invoice` to create and view the " +"invoice draft." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "" +"Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which " +"includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice" +" Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:129 +msgid "" +"From there, the invoice can be confirmed and posted by clicking " +":guilabel:`Confirm`. Confirming the invoice changes the status from " +":guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of " +"buttons at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "A sample draft invoice with down payment mentioned in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:137 +msgid "" +"From those buttons, the payment can be registered by clicking " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Showcase of the Register Payment button on a confirmed customer invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:143 +msgid "" +"Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-" +"populated with the necessary information. Confirm the information provided " +"is correct and make any necessary adjustments. When ready, click the " +":guilabel:`Create Payment` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Showcase of the Register Payment pop-up window with create payment button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:151 +msgid "" +"After clicking :guilabel:`Create Payment`, Odoo reveals the customer " +"invoice, now with a green :guilabel:`In Payment` banner in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Customer Invoice with a green In Payment banner located in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "" +"Now, when the customer wants to pay the remaining amount of the order, " +"another invoice must be created. To do that, return to the sales order, via " +"the breadcrumb links." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:161 +msgid "" +"Back on the sales order, a new :guilabel:`Down Payments` section is present " +"in the :guilabel:`Order Lines` tab, along with the down payment that was " +"just invoiced and posted." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The down payments section in the order lines tab of a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:168 +msgid "Next, click the :guilabel:`Create Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "" +"On the :guilabel:`Create invoices` pop-up window that appears, there are two" +" new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"The deduct down payment option on the create invoices pop up in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:177 +msgid "" +"If the remaining amount is ready to be paid, select the :guilabel:`Regular " +"Invoice` option. Odoo will create an invoice for the exact amount needed to " +"complete the total payment, as indicated in the :guilabel:`Amount to " +"invoice` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:181 +msgid "Once ready, click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 +msgid "" +"Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing " +"*all* the invoices for that specific sales order in the :guilabel:`Invoice " +"Lines` tab. Each invoice line item displays all the necessary information " +"related to each invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:187 +msgid "" +"To complete the flow, click :guilabel:`Confirm`, which changes the status of" +" the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:190 +msgid "" +"Once again, the :guilabel:`Register Payment` appears, with all fields auto-" +"populated with the necessary information, including the remaining amount " +"left to be paid on the order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The second register payment pop-up form in Odoo sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:197 +msgid "" +"After confirming that information, click :guilabel:`Create Payment`. Doing " +"so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In" +" Payment` banner in the upper-right corner. Also, both down payments are " +"present in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The second down payment invoice with in payment banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:205 +msgid "At this point, the flow is now complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:208 +msgid "" +"This flow is also possible with the :guilabel:`Fixed amount` down payment " +"option." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:211 +msgid "" +"If a down payment is used with a product that has a :guilabel:`Delivered " +"quantities` invoicing policy, the down payments will **not** be able to be " +"deducted when it comes time to invoice the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:215 +msgid "" +"This is because, due to the invoicing policy, the product(s) would have to " +"be delivered *before* creating the final invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:218 +msgid "" +"If nothing has been delivered, a :guilabel:`Credit Note` is created, which " +"cancels the draft invoice that was created after the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:221 +msgid "" +"To utilize the :guilabel:`Credit Note` option, the *Inventory* application " +"must be installed, in order to confirm the delivery. Otherwise, the " +"delivered quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:228 +msgid "Customer taxes modification on down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:230 +msgid "" +"To adjust the income account and customer taxes attached to a down payment, " +"navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> " +"Products --> Products`), search for the `Down Payment` product in the search" +" bar, and select it to reveal the product detail page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:234 +msgid "" +"On the :guilabel:`Down Payment` product page, in the :guilabel:`General " +"Information` tab, the customer taxes can be modified in the " +":guilabel:`Customer Taxes` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How to modify the income account link to down payments." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 +msgid "Income account modification on down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:246 +msgid "" +"To change or adjust the income account attached to the :guilabel:`Down " +"Payment` product page, the *Accounting* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:249 +msgid "" +"With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes " +"available on the product page. That tab will **not** be accessible without " +"the *Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:252 +msgid "" +"In the :guilabel:`Accounting` tab, the income account can be changed in the " +":guilabel:`Income Account` field, located in the :guilabel:`Receivables` " +"section." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:3 +msgid "Reinvoice expenses to customers" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:5 +msgid "" +"While working on a project for a client, employees often have to spend their" +" own money on various expenses related to the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:8 +msgid "" +"For example, an employee may need to use their own money to pay for a hotel," +" while they provide an on-site service for a client. As a company, this " +"expense should be reinvoiced to the customer. With Odoo, these kinds of " +"expenses can quickly be reinvoiced to the customer related to the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:13 +msgid "Expenses application" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:15 +msgid "" +"To be able to reinvoice a customer for an expense, the *Expenses* " +"application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:17 +msgid "" +"To install the *Expenses* application, navigate to :menuselection:`main Odoo" +" dashboard --> Apps`, and click :guilabel:`Install` on the *Expenses* " +"application block. When clicked, Odoo installs the application, refreshes " +"the page, and returns to the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:22 +msgid "Add expenses to sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:24 +msgid "" +"To begin, have a sales order confirmed in the *Sales* app to which a " +"reinvoiced expense can be added. Or, create a new sales order from scratch. " +"To do that, navigate to the :menuselection:`Sales app --> New`. Doing so " +"reveals a blank quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:28 +msgid "" +"Then, add a :guilabel:`Customer`, and add a product to the :guilabel:`Order " +"Lines` tab, by clicking :guilabel:`Add a product`. Next, select a product " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:31 +msgid "Lastly, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"This is how a confirmed sales order looks in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:37 +msgid "With the sales order confirmed, it's time to create an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:39 +msgid "" +"To do that, navigate to the *Expenses* application, by going to " +":menuselection:`main Odoo dashboard --> Expenses`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:42 +msgid "" +"Then, from the *Expenses* dashboard, click :guilabel:`New` to reveal a blank" +" expenses form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A blank expenses form in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:48 +msgid "" +"On the expenses form, add a :guilabel:`Description` to easily reference the " +"expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:50 +msgid "" +"Then, in the :guilabel:`Category` field, select one of the following options" +" from the drop-down menu:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:53 +msgid "" +":guilabel:`Communication`: any form of communication related to a " +"project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:54 +msgid "" +":guilabel:`Others`: expense that doesn't fit into any other categories." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:55 +msgid ":guilabel:`Meals`: any form of meal costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:56 +msgid ":guilabel:`Gifts`: any form of gift costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:57 +msgid "" +":guilabel:`Mileage`: any form of mileage (gas) costs related to " +"project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:58 +msgid "" +":guilabel:`Travel \\& Accommodation`: any travel or accommodation costs " +"related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:61 +msgid "" +"New expense categories can be created from an expense form, by clicking the " +":guilabel:`Category` field drop-down menu, selecting :guilabel:`View All`, " +"and clicking :guilabel:`New` from the :guilabel:`Search:Category` pop-up " +"window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:0 +msgid "" +"The Search:Category expenses pop-up window from a blank expenses form in " +"Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:69 +msgid "" +"For this sample workflow, which will reinvoice a customer for a brief hotel " +"stay, the :guilabel:`Category` for this example is :guilabel:`[TRANS \\& " +"ACC] Travel \\& Accommodation`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:73 +msgid "" +"The following example requires the *Sales*, *Accounting*, and *Expense* apps" +" to view/modify all the fields mentioned during the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:76 +msgid "" +"Beneath the :guilabel:`Category` field, enter in the amount to be expensed " +"in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:79 +msgid "" +"Next, designate if there are any :guilabel:`Included taxes` in the " +":guilabel:`Total`. If a preconfigured tax amount is selected from the " +":guilabel:`Included taxes` field, Odoo auto-calculates the taxed amount, " +"based on the amount entered in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:83 +msgid "" +"Then, choose which :guilabel:`Employee` was responsible for the expense, and" +" choose an option in the :guilabel:`Paid By` field: :guilabel:`Employee (to " +"reimburse)` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:86 +msgid "" +"In this case, our employee paid for the hotel with their own money, so the " +":guilabel:`Employee (to reimburse)` option is chosen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:89 +msgid "" +"On the right-hand side of the expenses form, the option to add a " +":guilabel:`Bill Reference` is available. Beneath that, the auto-populated " +":guilabel:`Expense Date` and :guilabel:`Account` fields are available." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:94 +msgid "" +"The :guilabel:`Expense Date` and :guilabel:`Account` field can be modified, " +"if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:96 +msgid "" +"Next, in the :guilabel:`Customer to Reinvoice` field, click the blank field " +"to reveal a drop-down menu. From this drop-down menu, select the appropriate" +" sales order to which this expense should be attached. This field **must** " +"be filled, in order to reinvoice a customer for an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:100 +msgid "" +"Lastly, the option to modify the :guilabel:`Analytic Distribution` and " +":guilabel:`Company` fields are available. These fields are *not* required to" +" complete a reinvoiced expense to a customer, but are available to modify, " +"if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:104 +msgid "" +"Also, at the bottom of the expense form, there is a :guilabel:`Notes...` " +"section, wherein any notes related to this expense can be added, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A filled out expenses form in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:111 +msgid "" +"At the top of the expense form, there are buttons to :guilabel:`Attach " +"Receipt`, :guilabel:`Create Report`, and :guilabel:`Split Expense`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:114 +msgid "" +"If there is a physical or digital receipt that should be attached to the " +"expense, click :guilabel:`Attach Receipt`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:117 +msgid "" +"If the cost of this expense needs to be split, click :guilabel:`Split " +"Expense`. This feature can be used for a number of reasons (spitting expense" +" with another employee, to accommodate different tax rates, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:121 +msgid "" +"If neither of these options are necessary, click :guilabel:`Create Report` " +"to lock in the expense report that was just configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:124 +msgid "" +"Doing so reveals an :guilabel:`Expense Report Summary` for the new expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "An expense report summary in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:130 +msgid "" +"Here, once the details related to the expense have been confirmed, click " +":guilabel:`Submit to Manager`. This sends the expense report to the " +"approving manager, who will review the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:133 +msgid "" +"The manager in charge of reviewing and approving the expense will inspect " +"the details related to the expense, and if there are no issues, they will " +"click the :guilabel:`Approve` button — which *only* appears on the manager's" +" view of the :guilabel:`Expense Report Summary` that's been submitted to the" +" manager by the employee." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"An expense report summary that a manager will approve with an Approve " +"button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:142 +msgid "" +"Once approved, the buttons at the top of the :guilabel:`Expense Report " +"Summary` change once again. At this point, the buttons at the top of the " +":guilabel:`Expense Report Summary` are: :guilabel:`Post Journal Entries`, " +":guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, and :guilabel:`Reset" +" to Draft`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"An expense report summary with post journal entries button at the top of the" +" form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:151 +msgid "" +"When the manager is satisfied with the :guilabel:`Expense Report Summary`, " +"they'll click :guilabel:`Post Journal Entries`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:154 +msgid "" +"Upon clicking :guilabel:`Post Journal Entries`, that button disappears, and " +"the :guilabel:`Analytic Distribution` column in the :guilabel:`Expense` tab " +"is filled with the sales order that was initially configured to the expense " +"in the :guilabel:`Customer to Reinvoice` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:159 +msgid "Reinvoice expense" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:161 +msgid "" +"With those steps completed, it's time to return to the sales order to " +"complete the reinvoice of the expense to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:164 +msgid "" +"To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, " +"and select the appropriate sales order that should be reinvoiced for the " +"expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:167 +msgid "" +"On the sales form, the newly-configured expense is now in the " +":guilabel:`Order Lines` tab, with its :guilabel:`Delivered` column filled " +"in, and ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A sales order with the configured expense ready to be invoiced in the Order " +"Lines tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:174 +msgid "" +"After confirming the details of the expense, click :guilabel:`Create " +"Invoice` at the top of the sales order. When clicked, a :guilabel:`Create " +"invoices` pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A create invoices pop-up window that appears when the Create Invoice is " +"clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:181 +msgid "" +"From this pop-up window, leave the :guilabel:`Create Invoice` field on the " +"default :guilabel:`Regular invoice` option, and click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:184 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` showing *only* the " +"expense in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A customer invoice draft with the expense in the Invoice Lines tab of the " +"form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:191 +msgid "" +"If all the information related to the expense is correct, click " +":guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the" +" invoice from :guilabel:`Draft` to :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:194 +msgid "" +"To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing" +" so reveals a :guilabel:`Send` pop-up window, with a preconfigured message " +"and PDF invoice in the body of the message. The message can be reviewed and " +"modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:198 +msgid "" +"Once ready, click :guilabel:`Send \\& Print` to send the invoice to the " +"customer. When clicked, the pop-up window disappears, and Odoo sends the " +"message/invoice to the customer. Additionally, a PDF of the invoice is " +"automatically downloaded for record-keeping and/or printing purposes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:202 +msgid "" +"Back on the :guilabel:`Customer Invoice`, click the :guilabel:`Register " +"Payment` button when the customer pays for the invoiced expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A customer invoice with the register payment button ready to be clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:209 +msgid "" +"When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment`" +" pop-up window appears. In this pop-up window, the necessary fields are " +"auto-populated with the correct information. After reviewing the " +"information, click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A register payment pop-up window on a customer invoice in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:217 +msgid "" +"Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, " +"and a green :guilabel:`In Payment` banner is in the upper-right corner of " +"the invoice, signifying this invoice is paid for in full. Thus, completing " +"the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:227 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:236 +msgid ":doc:`time_materials`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:228 +msgid ":doc:`milestone`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:3 +msgid "Invoice based on delivered or ordered quantities" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:5 +msgid "" +"Different business policies might require different options for invoicing:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:7 +msgid "" +"The *Invoice what is ordered* rule is used as the default mode in Odoo " +"*Sales*, which means customers are invoiced once the sales order is " +"confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:9 +msgid "" +"The *Invoice what is delivered* rule invoices customers once the delivery is" +" done. This rule is often used for businesses that sell materials, liquids, " +"or food in large quantities. In these cases, the ordered quantity may differ" +" slightly from the delivered quantity, making it preferable to invoice the " +"quantity actually delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:14 +msgid "" +"Being able to have different invoicing options provides more flexibility." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:17 +msgid "Invoicing policy features" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:19 +msgid "" +"To activate the necessary invoicing policy features, go to " +":menuselection:`Sales app --> Configuration --> Settings`, and under the " +":guilabel:`Invoicing` heading, select an :guilabel:`Invoicing Policy` rule: " +":guilabel:`Invoice what is ordered` or :guilabel:`Invoice what is " +"delivered`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "Choosing an invoicing policy on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:29 +msgid "" +"If the :guilabel:`Invoice what is delivered` rule is chosen, it is **not** " +"possible to activate the :guilabel:`Automatic Invoice` feature, which " +"automatically generates invoices when an online payment is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:34 +msgid "Invoicing policy on product form" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:36 +msgid "" +"On any product page, via the :menuselection:`Sales app --> Products --> " +"Products dashboard`, locate the :guilabel:`Invoicing Policy` option located " +"under the :guilabel:`General Information` tab. It can be changed manually " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to change your invoicing policy on a product form on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:45 +msgid "Impact on sales flow" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:47 +msgid "" +"In Odoo *Sales*, the basic sales flow starts with the creation of a " +"quotation. Then, that quotation is sent to a customer. Next, it needs to be " +"confirmed, which turns the quotation into a sales order. This, in turn, " +"creates an invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:51 +msgid "" +"The following is a breakdown of how invoicing policy rules impact the " +"aforementioned sales flow:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:53 +msgid "" +":guilabel:`Invoice what is ordered`: No impact on the basic sales flow. An " +"invoice is created as soon as a sale is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:55 +msgid "" +":guilabel:`Invoice what is delivered`: Minor impact on sales flow, because " +"the delivered quantity needs to be manually entered on the sales order. Or, " +"the *Inventory* app can be installed and used to confirm the delivered " +"quantity before creating an invoice with the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:60 +msgid "" +"If a user attempts to create an invoice without validating the delivered " +"quantity, the following error message appears: :guilabel:`There is no " +"invoiceable line. If a product has a Delivered quantities invoicing policy, " +"please make sure that a quantity has been delivered.`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0 +msgid "" +"If Delivered Quantities invoicing policy is chosen, ensure a quantity has " +"been delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:69 +msgid "" +"Once a quotation is confirmed, and the status changes from " +":guilabel:`Quotation sent` to :guilabel:`Sales order`, the delivered and " +"invoiced quantities are available to view, directly from the sales order. " +"This is true for both invoicing policy rule options." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to see your delivered and invoiced quantities on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:77 +msgid "" +"Odoo automatically adds the quantities to the invoice, both " +":guilabel:`Delivered` and :guilabel:`Invoiced`, even if it's a partial " +"delivery, when the quotation is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:80 +msgid "" +"Finally, there are a few different options to create an invoice: " +":guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)` or " +":guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:84 +msgid "" +"Be sure to check out the documentation explaining down payment options to " +"learn more: :doc:`/applications/sales/sales/invoicing/down_payment`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:3 +msgid "Invoice project milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:5 +msgid "" +"Invoicing based on project milestones can be used for expensive or large-" +"scale projects. The series of milestones in a project represent a clear " +"sequence of work that will inevitably result in the completion of a project " +"and/or contract." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:9 +msgid "" +"This method of invoicing ensures the company gets a consistent flow of money" +" throughout the lifetime of the project. Customers can closely monitor every" +" phase of the project's development as it happens, in addition to paying a " +"large bill in several installments, instead of all at once." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:14 +msgid "Create milestone products" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:16 +msgid "" +"In Odoo, each milestone of a project is considered as an individual product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:18 +msgid "" +"To create and/or configure products to work like this, first navigate to " +":menuselection:`Sales app --> Products --> Products`. Then, click on a " +"product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:22 +msgid "" +"The option to invoice based on milestones is only available for certain " +"product types." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:24 +msgid "" +"On the product form, under the :guilabel:`General Information` tab, the " +":guilabel:`Product Type` field *must* be set on any of the following " +"options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event " +"Booth`, or :guilabel:`Course`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The invoicing policy field drop-down menu with options on product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:32 +msgid "" +"With any of those :guilabel:`Product Type` options selected, choose " +":guilabel:`Based on Milestones` from the :guilabel:`Invoicing Policy` drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:39 +msgid "Beneath that is the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:41 +msgid "" +"To ensure workflows are as seamless as possible, it is recommended that an " +"option in the :guilabel:`Create on Order` field is selected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:45 +msgid "" +"Leaving it on the default :guilabel:`Nothing` option won't negatively affect" +" the desired workflow. However, a project *must* then be created directly " +"from a sales order form with that specific product. Once a project is " +"created *then* milestones and tasks can be created and configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:50 +msgid "" +"When the :guilabel:`Create on Order` default option of :guilabel:`Nothing` " +"is clicked, a drop-down menu is revealed with the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:53 +msgid "" +":guilabel:`Task`: Odoo creates a task related to this milestone product in " +"the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:55 +msgid "" +":guilabel:`Project \\& Task`: Odoo creates a project and task related to " +"this milestone product in the *Projects* app when this specific product is " +"ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:57 +msgid "" +":guilabel:`Project`: Odoo creates a project related to this milestone " +"product in the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:60 +msgid "" +"When :guilabel:`Task` is selected, a :guilabel:`Project` field appears. In " +"this field, select to which existing project in the *Projects* app this " +"created task should be connected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Project field appears when the Task option is selected in Create on " +"Order field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:67 +msgid "" +"When :guilabel:`Project \\& Task` or :guilabel:`Project` is selected, two " +"new fields appear: :guilabel:`Project Template` and :guilabel:`Workspace " +"Template`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Project template and workspace template fields that appear on milestone " +"product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:74 +msgid "" +"The :guilabel:`Project Template` field provides template options to use for " +"the project that will be created when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:77 +msgid "" +"The :guilabel:`Workspace Template` field provides template options to use " +"for the workspace (for the *Documents* app, not the *Projects* app) that " +"will be automatically generated for the project when this specific product " +"is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:82 +msgid "" +"For organizational purposes, click the :guilabel:`Sales` tab on the product " +"form, and enter a custom 'Milestone' related descriptor in the " +":guilabel:`Sales Description` field. This information appears in the " +":guilabel:`Description` column on the :guilabel:`Order Lines` tab of the " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:87 +msgid "" +"Or, directly edit/modify the :guilabel:`Description` field on the " +":guilabel:`Order Lines` tab of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:90 +msgid "This is *not* a requirement." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:93 +msgid "Invoice milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:96 +msgid "" +"The following flow features a trio of milestone products that have " +":guilabel:`Service` set as their :guilabel:`Product Type`, and " +":guilabel:`Task` set on their :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:0 +msgid "" +"Product with Service \"Product Type\" and \"Task\" in the Create on Order " +"field on form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:104 +msgid "" +"Those tasks are then attached to a pre-existing :guilabel:`Project`, which, " +"in this case, is titled, :guilabel:`Rebranding Projects`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:107 +msgid "" +"To invoice milestones, create a sales order with the milestone product(s). " +"To do that, go to :menuselection:`Sales app --> New`. Doing so reveals a " +"blank quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:110 +msgid "" +"From this quotation form, add a :guilabel:`Customer`. Then, click " +":guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Next, add the " +"milestone product(s) to the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:113 +msgid "" +"Once the corresponding milestone product(s) have been added, click " +":guilabel:`Confirm` to confirm the order, which turns the quotation into a " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:116 +msgid "" +"When the order is confirmed, new smart buttons appear at the top of the " +"sales order based on what was selected in the :guilabel:`Create on Order` " +"field on the product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:119 +msgid "" +"From the sales order, click the :guilabel:`Milestones` smart button. Doing " +"so reveals a blank :guilabel:`Milestones` page. Click :guilabel:`New` to add" +" milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "Adding milestones to a sales order with milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:126 +msgid "" +"Enter a :guilabel:`Name` for the milestone. Next, apply it to the " +"corresponding :guilabel:`Sales Order Item`. Lastly, assign a " +":guilabel:`Deadline` to the milestone, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:129 +msgid "Repeat that process for all milestone sales order items." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:131 +msgid "" +"Then, return to the sales order, via the breadcrumbs. From the sales order, " +"click the :guilabel:`Tasks` smart button. Doing so reveals a " +":guilabel:`Tasks` page with a task for each sales order item with that " +"option designated in the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"Sample tasks page accessed via the smart button from a sales order with " +"milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:139 +msgid "" +"To manually assign a configured milestone to a task, click the desired task," +" which reveals the task form. On the task form, select the appropriate " +"milestone to which this task should be connected, in the " +":guilabel:`Milestone` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The milestone field on the task form when dealing with milestone products in" +" Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:147 +msgid "Repeat this process for all milestone tasks." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:149 +msgid "" +"With those tasks properly configured, employees log in their progress as " +"they work on the task, in addition to adding any notes related to the task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:152 +msgid "" +"Then, when that task is complete, that means that milestone has been " +"reached. At that point, it is time to invoice that milestone." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:155 +msgid "" +"To invoice a milestone, first return to the sales order — either via the " +"breadcrumb links, or by navigating to :menuselection:`Sales app --> Orders " +"--> Orders` and picking the appropriate sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:159 +msgid "" +"Back on the sales order form, click the :guilabel:`Milestones` smart button," +" and check the box in the :guilabel:`Reached` column for that particular " +"task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"What it looks like to mark a milestone as reached via the milestone smart " +"button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:166 +msgid "" +"Next, return to the sales order — either by clicking :guilabel:`View Sales " +"Order` on the :guilabel:`Milestones` page, or via the breadcrumb links." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:169 +msgid "" +"Back on the sales order, the line item for the milestone that's been reached" +" has its :guilabel:`Delivered` column filled. That's because the milestone " +"has been reached, and therefore delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"A milestone product that's been reached marked as delivered on the sales " +"order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:177 +msgid "" +"Click :guilabel:`Create Invoice` in the upper-left corner. Doing so reveals " +"a :guilabel:`Create invoices` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The create invoices pop-up window that appears when create invoice button is" +" clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:184 +msgid "" +"On the :guilabel:`Create invoices` pop-up window, leave the " +":guilabel:`Create Invoice` option on the default :guilabel:`Regular Invoice`" +" selection, and click the :guilabel:`Create Draft Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:188 +msgid "" +"Upon clicking :guilabel:`Create Draft Invoice`, Odoo reveals the " +":guilabel:`Customer Invoice Draft`, *only* showing that reached milestone in" +" the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"A customer invoice draft showing only the milestone product that's been " +"reached." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:195 +msgid "" +"From this invoice page, click the :guilabel:`Confirm` button to confirm the " +"invoice. Then, when the customer has paid for this milestone, click " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:198 +msgid "" +"When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment`" +" pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Register Payment pop-up window that appears when Register Payment is " +"clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:204 +msgid "" +"On this pop-up window, confirm the accuracy of the auto-populated fields, " +"then click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:207 +msgid "" +"When clicked, the pop-up window disappears, and Odoo returns to the invoice " +"for that milestone, which now has a green :guilabel:`In Payment` banner in " +"the upper-right corner. This banner signifies the invoice has been paid." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"An invoice with a milestone product that has been paid with an In Payment " +"banner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:215 +msgid "" +"Then, return to the sales order, via the breadcrumb links. Back on the sales" +" order, in the :guilabel:`Order Lines` tab, the reached milestone that's " +"been invoiced and paid for, now has its :guilabel:`Invoiced` column filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Invoiced column of a milestone product that's been paid for is filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:223 +msgid "" +"There is also a new :guilabel:`Invoices` smart button at the top of the " +"sales order. Clicking that reveals all the invoices that are connected to " +"this sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The invoices smart button that appears at the top of a sales order with " +"milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:230 +msgid "" +"Simply repeat the above process for each milestone as it is worked on, and " +"subsequently, completed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:232 +msgid "" +"Continue that process until the entire project has been completed, each " +"milestone has been invoiced, and the entire order has been paid for in full." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:237 +msgid ":doc:`proforma`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:3 +msgid "Pro-forma invoices" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:5 +msgid "" +"A *pro-forma invoice* is an abridged or estimated invoice sent in advance of" +" a delivery of goods. It notes the kind and quantity of goods, their value, " +"and other important information, such as weight and transportation charges." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:9 +msgid "" +"Pro-forma invoices are commonly used as preliminary invoices with a " +"quotation. They are also used during importation for customs purposes. They " +"differ from a normal invoice, in that they are *not* a demand (or request) " +"for payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:16 +msgid "" +"In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature " +"**must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:18 +msgid "" +"To enable this feature, navigate to :menuselection:`Sales app --> " +"Configuration --> Settings`, and in the :guilabel:`Quotations \\& Orders` " +"section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, " +"click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:27 +msgid "Send pro-forma invoice" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:29 +msgid "" +"With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send" +" a pro-forma invoice is now available on any quotation or sales order, via " +"the :guilabel:`Send Pro-Forma Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:37 +msgid "" +"Pro-forma invoices can **not** be sent for a sales order or quotation if an " +"invoice for a down payment has already been sent, or for a recurring " +"subscription." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "" +"In either case, the :guilabel:`Send Pro-Froma Invoice` button does **not** " +"appear." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:42 +msgid "" +"However, pro-forma invoices **can** be sent for services, event " +"registrations, courses, and/or new subscriptions. Pro-forma invoices are not" +" limited to physical, consumable, or storable goods." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:45 +msgid "" +"When the :guilabel:`Send Pro-Forma Invoice` button is clicked, a pop-up " +"window appears, from which an email can be sent." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "" +"In the pop-up window, the :guilabel:`Recipients` field is auto-populated " +"with the customer from the sales order or quotation. The :guilabel:`Subject`" +" field and the body of the email can be modified, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:52 +msgid "" +"The pro-forma invoice is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:54 +msgid "" +"When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with" +" the attached pro-forma invoice, to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The email pop-up window that appears with pro-forma invoice attached in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:62 +msgid "" +"To preview what the pro-forma invoice looks like, click on the PDF at the " +"bottom of the email pop-up window *before* clicking :guilabel:`Send`. When " +"clicked, the pro-forma invoice is downloaded instantly. Open that PDF to " +"view (and review) the pro-forma invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:0 +msgid "Sample pro-forma invoice PDF from Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 +msgid "Invoicing based on time and materials" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:5 +msgid "" +"Invoicing based on time and/or materials is typically used when accurately " +"estimating the size of a project isn't possible, or when the requirements of" +" a project may change." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:8 +msgid "" +"This is different from a fixed-price contract, when a customer agrees to pay" +" a specified total for the fulfillment of the contract---no matter what " +"needs to be paid to the employees, sub-contractors, vendors, suppliers, and " +"so on." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:12 +msgid "" +"The Odoo *Sales* app can invoice for time and various other expenses (e.g. " +"transport, lodging), as well as purchases needed to fulfill an order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:16 +msgid "App and settings configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:18 +msgid "" +"First, in order to accurately keep track of the progress of a project, the " +"Odoo *Project* and *Accounting* apps **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:21 +msgid "" +"To install the *Project* app, navigate to :menuselection:`Odoo main " +"dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Project` app block, and click :guilabel:`Activate`. The page " +"automatically refreshes and returns to the main Odoo dashboard, where the " +"*Project* app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:26 +msgid "Repeat the same process to install the *Accounting* application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:28 +msgid "" +"After installation, click the :guilabel:`Accounting` app icon from the main " +"Odoo dashboard, and navigate to :menuselection:`Configuration --> Settings`." +" On the :guilabel:`Settings` page, scroll down to the :guilabel:`Analytics` " +"section, and ensure the box next to :guilabel:`Analytic Accounting` is " +"checked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How it looks to activate the Analytic Accounting setting in Odoo Accounting " +"Setting page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:37 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:43 +msgid "Then, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:39 +msgid "" +"Then, navigate to :menuselection:`Odoo main dashboard --> Project app --> " +"Configuration --> Settings`. On the :guilabel:`Settings` page, in the " +":guilabel:`Time Management` section, ensure the box beside the " +":guilabel:`Timesheets` feature is checked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"What the Timesheets feature looks like on the Odoo Project settings page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:52 +msgid "Service product configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:54 +msgid "" +"With the *Timesheets* feature activated in the *Project* app, it is now " +"possible to invoice for time spent on a project, but **only** when the " +"following product configurations have been made." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:58 +msgid "" +"Invoicing for time spent on a project is **only** possible with products " +"that have *Service* set as the *Product Type* on their product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:61 +msgid "" +"To configure a service product, first navigate to :menuselection:`Sales app " +"--> Products --> Products`. On the :guilabel:`Products` page, select the " +"desired service product to be configured, or click :guilabel:`New` to create" +" a new product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:65 +msgid "" +"From the product form, in the :guilabel:`General Information` tab, set the " +":guilabel:`Product Type` to :guilabel:`Service`. Then, open the drop-down " +"menu in the :guilabel:`Invoicing Policy` field, and select :guilabel:`Based " +"on Timesheets`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:69 +msgid "" +"Next, from the :guilabel:`Create on Order` drop-down menu, select " +":guilabel:`Project \\& Task`. That setting indicates that, when a sales " +"order is created with this specific service product, a new project and task " +"is created in the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"The correct settings for Invoicing Policy and Create on Order fields for " +"service product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:78 +msgid "" +"The option :guilabel:`Task` can be chosen instead from the :guilabel:`Create" +" on Order` drop-down menu. If :guilabel:`Task` is chosen, select an existing" +" project that the task will appear in from :guilabel:`Project` field, which " +"only appears if :guilabel:`Task` is chosen in the :guilabel:`Create on " +"Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:84 +msgid "Add time spent to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:86 +msgid "" +"After properly configuring a service product with the correct *Invoicing " +"Policy* and *Create on Order* options, it is possible to add time spent to a" +" sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:89 +msgid "" +"To see that in action, navigate to :menuselection:`Sales app --> New` to " +"open a blank quotation form. Then, proceed to add a :guilabel:`Customer`, " +"and in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and" +" select the properly :ref:`configured service product " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:94 +msgid "Next, click :guilabel:`Confirm` to confirm the order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:96 +msgid "" +"After confirming the sales order, two smart buttons appear at the top of the" +" order form: :guilabel:`Projects` and :guilabel:`Tasks`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How the Projects and Tasks smart buttons look on a Sales Order in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:103 +msgid "" +"If the :guilabel:`Projects` smart button is clicked, it reveals the specific" +" project related to this sales order. If the :guilabel:`Tasks` smart button " +"is clicked, it reveals the specific project task related to this sales " +"order. Both are also accessible in the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:107 +msgid "" +"In order to add time spent on a sales order, click the :guilabel:`Tasks` " +"smart button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:109 +msgid "" +"On the task form, select the :guilabel:`Timesheets` tab. From the " +":guilabel:`Timesheets` tab, employees can be assigned to work on the " +"project, and the time they spend working on the task can be added by the " +"employees or by the person who created the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:113 +msgid "" +"To add an employee, and the time spent working on the task, click " +":guilabel:`Add a line` in the :guilabel:`Timesheets` tab. Then, select the " +"appropriate :guilabel:`Date` and :guilabel:`Employee`. There is also the " +"option to add a brief description of the work done during this time in the " +":guilabel:`Description` column, but it's not required." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:118 +msgid "" +"Lastly, enter the amount of time worked on the task in the :guilabel:`Hours " +"Spent` column, and click away to complete that line in the " +":guilabel:`Timesheets` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:122 +msgid "" +"The time entered in the :guilabel:`Hours Spent` column is immediately " +"reflected in the :guilabel:`Allocated Time` field (located near the top of " +"the task form) as a percentage, which reflects how much of the total " +"allocated work hours have been done so far." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:126 +msgid "" +"That same information is found as numerical hours in the :guilabel:`Hours " +"Spent` and :guilabel:`Remaining Hours` fields, located at the bottom of the " +":guilabel:`Timesheets` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "" +"How the Timesheets tab appears on a task form in Odoo Sales and Odoo " +"Project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:133 +msgid "" +"Repeat this process for however many employees and hours have been worked on" +" the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:136 +msgid "Invoice time spent" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:138 +msgid "" +"Once all the necessary employees and time spent have been added to the " +"project task, return to the sales order to invoice the customer for those " +"hours. To do that, either click the :guilabel:`Sales Order` smart button at " +"the top of the task form, or return to the sales order via the breadcrumb " +"links, located in the upper-left of the screen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:143 +msgid "" +"Back on the sales order form, the time that was added to the task is " +"reflected in the :guilabel:`Order Lines` tab (in the :guilabel:`Delivered` " +"column) and in the new :guilabel:`Recorded Hours` smart button at the top of" +" the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:147 +msgid "" +"To invoice the customer for time spent on the project, click " +":guilabel:`Create Invoice`, and select :guilabel:`Regular invoice` from the " +":guilabel:`Create invoices` pop-up window. Then, click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:151 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft`, clearly showing all " +"the work that's been done in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:155 +msgid "" +"Pay attention to the :guilabel:`Analytic Distribution` column in the " +":guilabel:`Customer Invoice`, as that information is necessary to ensure " +"other time/material invoicing tasks are completed properly and accurately." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "Invoice draft showing time spent on sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:163 +msgid "" +"Click :guilabel:`Confirm` to confirm the invoice and continue with the " +"invoicing process." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:169 +msgid "Expenses configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:171 +msgid "" +"In order to track and invoice expenses related to a sales order, the Odoo " +"*Expenses* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:174 +msgid "" +"To install the *Expenses* app, navigate to :menuselection:`Odoo main " +"dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Expenses` app block, and click :guilabel:`Activate`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:178 +msgid "" +"The page automatically refreshes and returns to the main Odoo dashboard, " +"where the :guilabel:`Expenses` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:184 +msgid "Add expenses to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:186 +msgid "" +"To add an expense to a sales order, first navigate to the " +":menuselection:`Expenses` app. Then, from the main *Expenses* dashboard, " +"click :guilabel:`New`, which reveals a blank expense form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:189 +msgid "" +"On the expense form, add a :guilabel:`Description` of the expense (e.g. " +"`Hotel Stay`, `Plane Ticket`). Next, in the :guilabel:`Category` field, " +"select the appropriate option from the drop-down menu (e.g. " +":guilabel:`Meals`, :guilabel:`Miles`, :guilabel:`Travel \\& Accommodation`)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:194 +msgid "" +"Expense categories can be added and modified by navigating to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:197 +msgid "" +"Then, enter the total amount of the expense in the :guilabel:`Total` field, " +"as well as any :guilabel:`Included Taxes` that may apply. Next, ensure that " +"the correct :guilabel:`Employee` is selected, and designate who paid for the" +" expense in the :guilabel:`Paid By` field: the :guilabel:`Employee (to " +"reimburse)` or the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:202 +msgid "" +"Next, in the :guilabel:`Customer to Reinvoice` field, select the appropriate" +" sales order from the drop-down menu. Then, select that same sales order " +"information from the :guilabel:`Analytic Distribution` field, as well." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:207 +msgid "" +"The :guilabel:`Analytic Distribution` field will **only** have the " +"corresponding sales order as an option if the sales order contains a service" +" product that is billed based on *Timesheets*, *Milestones*, or *Delivered " +"Quantities*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to properly fill out an expense form that's attached to a sales order in" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:215 +msgid "" +"If there are any receipts that should be uploaded and attached to the " +"expense, click the :guilabel:`Attach Receipt` button, and upload the " +"necessary documents to the expense. This is **not** required, but it may " +"affect whether or not an expense is approved." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:219 +msgid "" +"When all the information has been entered, click :guilabel:`Create Report` " +"to create an expense report detailing all the expense information that was " +"just entered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "How an Expense Report Summary looks in Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:226 +msgid "" +"Then, there's the option to :guilabel:`Submit to Manager` for approval. Once" +" approved, the :guilabel:`Report in Next Payslip` appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:229 +msgid "" +"To showcase a complete flow in this example, select :guilabel:`Submit to " +"Manager`. Then, the manager would click :guilabel:`Approve` to approve this " +"expense, and click :guilabel:`Post Journal Entries` to post this expense to " +"the accounting journal." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:234 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:236 +msgid "" +"To invoice a customer for an :ref:`expense on a sales order " +"`, navigate to the related sales " +"order, either from the :menuselection:`Sales` app or from the expense report" +" in the :menuselection:`Expenses` app. From the expense report, click the " +":guilabel:`Sales Orders` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:241 +msgid "" +"If the expense report was linked to the sales order, the newly-configured " +"expense now has its own line in the :guilabel:`Order Lines` tab, and can be " +"invoiced to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"An expense appearing on Order Lines tab of a Sales Order in Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:248 +msgid "" +"To invoice the customer for the expense on the sales order, click " +":guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the " +":guilabel:`Create invoices` pop-up window, then click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:252 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` for the expense. Then," +" the invoicing process can be completed as usual." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Sample customer invoice for an expense generated from a sales order in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:260 +msgid "Purchase configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:262 +msgid "" +"In order to invoice a customer for purchases made on a sales order, the " +"*Purchase* application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:265 +msgid "" +"To install the *Purchase* application, navigate to :menuselection:`Odoo main" +" dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Purchase` app block, and click :guilabel:`Activate`. The page " +"automatically refreshes and returns to the main Odoo dashboard, where the " +":guilabel:`Purchase` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:273 +msgid "Add purchase to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:275 +msgid "" +"To add a purchase to a sales order, a purchase order must first be created. " +"To create a purchase order, navigate to :menuselection:`Purchase app --> " +"New` to reveal a blank purchase order form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:278 +msgid "" +"First, add a :guilabel:`Vendor` to the purchase order. Then, under the " +":guilabel:`Products` tab, click the :guilabel:`extra column options` drop-" +"down menu, represented by two horizontal lines with dots on them, located to" +" the far-right of the column headers. From that drop-down menu, select " +":guilabel:`Analytic Distribution`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to add analytic distribution column on purchase order form in Odoo " +"Purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:287 +msgid "" +"After adding the :guilabel:`Analytic Distribution` column to the headers on " +"the :guilabel:`Products` tab of the purchase order form, proceed to add the " +"product(s) to the purchase order. To do that, click :guilabel:`Add a " +"product`, and select the desired product from the drop-down menu. Repeat for" +" all the products to add." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:293 +msgid "" +"In order for a purchase to be properly invoiced on a sales order, the " +"product on the purchase order **must** be marked as :guilabel:`Can be " +"Expensed`, have an :guilabel:`Invoicing Policy` set to :guilabel:`Delivered " +"quantities`, and have the :guilabel:`At cost` option selected in the " +":guilabel:`Re-Invoice Expenses` field on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "" +"Product settings for a purchase order to be invoiced on a sales order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:302 +msgid "" +"Then, select the appropriate :guilabel:`Analytic Distribution` associated " +"with the sales order to which this purchase order is related. To do that, " +"click the empty :guilabel:`Analytic Distribution` field to reveal an " +":guilabel:`Analytic` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:306 +msgid "" +"Then, from the :guilabel:`Departments` drop-down menu, select the analytic " +"distribution associated with the desired sales order to be invoiced for the " +"purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to select the Analytic Distribution department from a purchase order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:313 +msgid "" +"Once all the information is entered in the :guilabel:`Products` tab of the " +"purchase order, confirm the order by clicking :guilabel:`Confirm Order`. " +"Then, click :guilabel:`Receive Products` when the products have been " +"received. This creates a receipt form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:318 +msgid "" +"If any serial/lot numbers must be entered before validating the receipt of " +"products, then on the receipt form, click the :guilabel:`details` icon " +"represented by four horizontal lines located to the far-right of the product" +" line." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:322 +msgid "" +"This reveals a :guilabel:`Detailed Operations` tab, in which the necessary " +":guilabel:`Lot/Serial Number(s)` and :guilabel:`Done` quantity can be added." +" When ready, click :guilabel:`Confirm` to confirm the data." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:326 +msgid "Then, click :guilabel:`Validate` to validate the purchase order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:328 +msgid "" +"Next, return to the purchase order, via the breadcrumb links at the top of " +"the page, and click :guilabel:`Create Bill` to create a vendor bill that can" +" be invoiced to the customer on the attached sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Vendor bill draft for a purchase order to be invoiced to a customer in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:337 +msgid "" +"Make sure to enter a :guilabel:`Bill Date` on the :guilabel:`Vendor Bill " +"Draft` before confirming. If a :guilabel:`Bill Date` is *not* entered, an " +"error window appears, requesting that information to be entered before " +"confirmation can occur." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:341 +msgid "" +"Then, click :guilabel:`Confirm` to confirm the vendor bill, which is then " +"automatically added to the sales order, where it can be invoiced directly to" +" the customer attached to it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:345 +msgid "Invoice purchase" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:347 +msgid "" +"To invoice a customer for a purchase on a sales order, first :ref:`add the " +"purchase to the sales order `, " +"then navigate to the desired sales order in the :menuselection:`Sales` app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:351 +msgid "" +"On the sales order that was attached to the purchase order, the purchased " +"product now has its own product line under the :guilabel:`Order Lines` tab, " +"and it is ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Purchase order product on sales order to be invoiced to customer via Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:358 +msgid "" +"To invoice the customer for the purchase, simply click :guilabel:`Create " +"Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create " +"invoices` pop-up window, then click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:362 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` with the newly-added " +"purchase order product in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Customer invoice draft with purchase product attached to sales order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:369 +msgid "" +"To complete the invoicing process, click :guilabel:`Confirm` to confirm the " +"invoice, and then click :guilabel:`Register Payment` in the " +":guilabel:`Register Payment` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices.rst:5 +msgid "Products & Prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:3 +msgid "Use eWallets and gift cards" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:5 +msgid "" +"With Odoo, customers can use **eWallets** and **gift cards** for online and " +"in-store shopping." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:7 +msgid "" +"To enable eWallets and gift cards for eCommerce and Point of Sale (PoS), " +"first enable :guilabel:`Discounts, Loyalty & Gift Card` under " +":menuselection:`Sales app --> Configuration --> Settings --> Pricing " +"section`. Once enabled, go to :menuselection:`Sales app --> Products --> " +"Gift cards & eWallet` and :guilabel:`Create` a new eWallet or gift card " +"program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:13 +msgid "eWallets" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:15 +msgid "" +"eWallets allow customers to save credits on their online account and use " +"these credits as a payment method when buying items in an online store or a " +"brick-and-mortar store. eWallets can also be used to centralize multiple " +":ref:`gift cards `." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:19 +msgid "" +"Before creating an eWallet program, it is necessary to create an eWallet " +"**top-up** product. Top-ups are pre-defined digital credit values added to " +"an eWallet in exchange for its equivalent in real currency. These credits " +"can then be used as a payment method in the eCommerce shop or :abbr:`PoS " +"(Point of Sale)`. Top-up values can be of different amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:25 +msgid "" +"A $50 top-up can be bought for $50, and adds that same amount of credits to " +"the eWallet." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:27 +msgid "" +"To create a top-up product, go to :menuselection:`Sales app --> Products -->" +" Products` and :guilabel:`Create` a new product. On the product template, " +"configure the options as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:30 +msgid "" +":guilabel:`Product Name`: enter a name for the top-up product (for example, " +"`$50 Top-Up`)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:31 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:92 +msgid ":guilabel:`Can be Sold`: enabled" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:32 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:93 +msgid ":guilabel:`Product Type`: select :guilabel:`Service`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:33 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:94 +msgid ":guilabel:`Invoicing Policy`: select :guilabel:`Prepaid/Fixed Price`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:34 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:95 +msgid ":guilabel:`Create on Order`: select :guilabel:`Nothing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:35 +msgid ":guilabel:`Sales Price`: enter the amount of the top-up" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:38 +msgid "" +"In order to have eWallet top-ups of different amounts, create multiple top-" +"up products and modify the :guilabel:`Sales Price` accordingly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:41 +msgid "" +"Once the top-up is created, go to :menuselection:`Sales app --> Products -->" +" Gift cards & eWallet` to :guilabel:`Create` an eWallet program. The " +"following configuration options are available:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:44 +msgid ":guilabel:`Program Name`: enter a name for the eWallet program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:45 +msgid ":guilabel:`Program Type`: select :guilabel:`eWallet`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:46 +msgid "" +":guilabel:`eWallet Products`: select the eWallet top-up created earlier. " +"Repeat the process if you created top-ups of different amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:48 +msgid "" +":guilabel:`Email template`: select the email template used for the email " +"sent to the customer. To create a new template, click on the field, select " +":guilabel:`Search More`, and then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:51 +msgid "" +":guilabel:`Currency`: select the currency to use for the eWallet program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:52 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:115 +msgid "" +":guilabel:`Company`: select the company for which the program is valid and " +"available" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:53 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:116 +msgid "" +":guilabel:`Available On`: select the applications on which the program is " +"valid and available" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:54 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:117 +msgid "" +":guilabel:`Website`: select the website on which the program is valid and " +"available. Leave this field empty to include all websites." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:56 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:119 +msgid "" +":guilabel:`Point of Sale`: select the :abbr:`PoS (Point of Sale)` in which " +"the program is valid and available. Leave this field empty to include all " +":abbr:`PoS (Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "eWallet program configuration page" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:63 +msgid "" +"Once the program is configured, click the :guilabel:`Generate eWallet` " +"button in the upper-left corner to generate eWallets. eWallets can be " +"generated based on :guilabel:`Customers` and/or :guilabel:`Customer Tags`. " +"The quantity is automatically adapted according to the :guilabel:`Customers`" +" and :guilabel:`Customer Tags` selected. Then, set the :guilabel:`eWallet " +"value`. Finally, set the :guilabel:`Valid Until` period if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:69 +msgid "" +"Generated eWallets can be accessed through the :guilabel:`eWallets` smart " +"button in the upper-right corner. From there, :guilabel:`Send` or " +":guilabel:`Share` the eWallets via email or a URL link." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "eWallets send and share buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:76 +msgid "" +"Click on an eWallet to change the :guilabel:`Expiration Date`, " +":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of an " +"eWallet *cannot* be changed, deleted, or duplicated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:82 +msgid "Gift cards" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:84 +msgid "" +"Gift cards can be purchased by customers, and in turn used as a payment " +"method upon checkout at an eCommerce shop or :abbr:`PoS (Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:87 +msgid "" +"Before creating a new gift card program, it is necessary to first create " +"gift cards as products. To do so, go to :menuselection:`Sales app --> " +"Products --> Products` and :guilabel:`Create` a product. On the product " +"template, configure the options as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:91 +msgid ":guilabel:`Product Name`: enter a name for the gift card product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:96 +msgid ":guilabel:`Sales Price`: enter the amount of the gift card" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:99 +msgid "" +"In order to have gift cards of different amounts, create multiple gift card " +"products and modify the :guilabel:`Sales Price` accordingly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:102 +msgid "" +"Once the gift card product is created, go to :menuselection:`Sales app --> " +"Products --> Gift cards & eWallet` to :guilabel:`Create` a gift card " +"program. The following configuration options are available:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:106 +msgid ":guilabel:`Program Name`: enter a name for the gift card program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:107 +msgid ":guilabel:`Program Type`: select :guilabel:`Gift Card`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:108 +msgid "" +":guilabel:`Gift Card Products`: select the gift card product created " +"earlier. Repeat the process if you created gift card products of different " +"amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:110 +msgid "" +":guilabel:`Email template`: select the default :guilabel:`Gift Card: Gift " +"Card Information` template, or create a new template by clicking on the " +"field, selecting :guilabel:`Search More`, and then clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:113 +msgid ":guilabel:`Print Report`: select :guilabel:`Gift Card`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:114 +msgid "" +":guilabel:`Currency`: select the currency to use for the gift card program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "Gift card program configuration page" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:126 +msgid "" +"Once the program is configured, click the :guilabel:`Generate Gift Cards` " +"button in the upper-left corner to generate gift cards. Gift cards can be " +"generated either for :guilabel:`Anonymous Customers` or :guilabel:`Selected " +"Customers`. Set the :guilabel:`Quantity to generate` for " +":guilabel:`Anonymous Customers`, or select the :guilabel:`Customers` and/or " +":guilabel:`Customer Tags` for :guilabel:`Selected Customers`. Then, set the " +":guilabel:`Gift Card value`. Finally, set the :guilabel:`Valid Until` period" +" if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:133 +msgid "" +"Generated gift cards can be accessed through the :guilabel:`Gift Cards` " +"smart button in the upper-right corner. From there, :guilabel:`Send` or " +":guilabel:`Share` the gift cards via email or a URL link." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "Gift cards send and share buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:141 +msgid "" +"Click on a gift card to change the :guilabel:`Expiration Date`, " +":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of a gift " +"card *cannot* be changed, deleted, or duplicated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:3 +msgid "Discount and loyalty programs" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:5 +msgid "" +"The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow users " +"to create discount and loyalty programs that customers can use for online " +"and in-store shopping. These programs offer more varied, public, and time-" +"sensitive pricing options than :doc:`pricelists " +"`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:11 +msgid "Configure the settings" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:13 +msgid "" +"To begin using discount and loyalty programs, navigate to " +":menuselection:`Sales --> Configuration --> Settings`. Under the " +":guilabel:`Pricing` heading, activate the :guilabel:`Discounts, Loyalty & " +"Gift Card` setting by checking the box next to the feature. Finally, click " +":guilabel:`Save` to save the changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:19 +msgid "Configure discount and loyalty programs" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:21 +msgid "" +"To create discount and loyalty programs, go to :menuselection:`Sales --> " +"Products --> Discount & Loyalty`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:24 +msgid "" +"If no discount or loyalty programs have been created yet, Odoo provides a " +"choice of templates to help create the first program. Choose one of the " +"template cards, or click :guilabel:`New` to create a new program from " +"scratch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:28 +msgid "" +"Or, if there are already existing programs, select an existing program to " +"edit it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Discount and loyalty program template cards." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:35 +msgid "" +"Templates only appear when no programs have been created, and they disappear" +" once the first program is created." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:38 +msgid "Creating or editing a program opens the program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:40 +msgid "The program form contains the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:42 +msgid "" +":guilabel:`Program Name`: Enter the name of the program. The program name is" +" *not* visible to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44 +msgid "" +":guilabel:`Program Type`: Select the desired :ref:`program type " +"`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46 +msgid ":guilabel:`Currency`: Select the currency used for the program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:47 +msgid "" +":guilabel:`Points Unit`: Enter the name of the points used for the " +":guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit " +"name *is* visible to the customer. This field is only available when the " +":guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:50 +msgid "" +":guilabel:`Validity`: Select the date until which the program is valid. " +"Leave this field blank for no end date, meaning the program is always valid " +"and does not expire." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:52 +msgid "" +":guilabel:`Limit Usage`: Check this box and enter a number to limit the " +"number of times the program can be used during the :guilabel:`Validity` " +"period." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:54 +msgid "" +":guilabel:`Company`: In the case of multiple companies, choose the company " +"for which the program is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:56 +msgid "" +":guilabel:`Available On`: Select the app(s) on which the program is " +"available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57 +msgid "" +":guilabel:`Website`: Select the website(s) on which the program is " +"available. Leave this field blank to make it available on all websites." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:59 +msgid "" +":guilabel:`Point of Sale`: Select the point(s) of sale at which the program " +"is available. Leave this field blank to make it available at all :abbr:`PoS " +"(Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Program options on the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:67 +msgid "" +"The options available on the program form vary depending on the " +":ref:`Program Type ` selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:70 +msgid "" +"All of the existing cards, codes, coupons, etc. that have been generated for" +" the program are accessible through the smart button located in the upper-" +"right corner of the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Program items smart button on the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:80 +msgid "Program types" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:82 +msgid "" +"The different :guilabel:`Program Types` available on the program form are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:84 +msgid "" +":guilabel:`Coupons`: Generate and share single-use coupon codes that grant " +"immediate access to rewards." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:86 +msgid "" +":guilabel:`Next Order Coupons`: Generate and share single-use coupon codes " +"that grant access to rewards on the customer's next order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:88 +msgid "" +":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates " +"points to exchange for rewards on future orders." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:90 +msgid "" +":guilabel:`Promotions`: Set conditional rules for ordering products, which, " +"when fulfilled, grant access to rewards for the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:92 +msgid "" +":guilabel:`Discount Code`: Set codes which, when entered upon checkout, " +"grant discounts to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:94 +msgid "" +":guilabel:`Buy X Get Y`: For every X item bought, the customer is granted 1 " +"credit. After accumulating a specified amount of credits, the customer can " +"trade them in to receive Y item." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:98 +msgid "Conditional rules" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:100 +msgid "" +"Next, configure the :guilabel:`Conditional rules` that determine when the " +"program applies to a customer's order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:103 +msgid "" +"In the :guilabel:`Rules & Rewards` tab, click :guilabel:`Add` next to " +":guilabel:`Conditional rules` to add *conditions* to the program. This " +"reveals a :guilabel:`Create Conditional rules` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Rules & Rewards tab of the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:112 +msgid "" +"The options for :guilabel:`Conditional rules` vary depending on the selected" +" :ref:`Program Type `." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:115 +msgid "The following options are available for configuring conditional rules:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:117 +msgid "" +":guilabel:`Discount Code`: Enter a custom code to be used for the " +":guilabel:`Discount Code` program, or use the default one generated by Odoo." +" This field is only available when the :guilabel:`Program Type` is set to " +":guilabel:`Discount Code`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:120 +msgid "" +":guilabel:`Minimum Quantity`: Enter the minimum number of products that must" +" be purchased in order to access the reward. Set the minimum quantity to at " +"least `1` to ensure that the customer must make a purchase in order to " +"access the reward." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:123 +msgid "" +":guilabel:`Minimum Purchase`: Enter the minimum amount (in currency), with " +":guilabel:`tax Included` or :guilabel:`tax Excluded`, that must be spent in " +"order to access the reward. If both a minimum quantity *and* minimum " +"purchase amount are entered, then the customer's order must meet both " +"conditions." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:127 +msgid "" +":guilabel:`Products`: Select the specific product(s) for which the program " +"applies. Leave this field blank to apply it to all products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:129 +msgid "" +":guilabel:`Categories`: Select the category of products for which the " +"program applies. Choose :guilabel:`All` to apply it to all product " +"categories." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:131 +msgid "" +":guilabel:`Product Tag:` Select a tag to apply the program to products with " +"that specific tag." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:132 +msgid "" +":guilabel:`Grant`: Enter the number of points the customer earns " +":guilabel:`per order`, :guilabel:`per currency spent`, or :guilabel:`per " +"unit paid` (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` " +"programs)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "" +"Conditional rules configuration window for a discount or loyalty program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:140 +msgid "" +"Click :guilabel:`Save & Close` to save the rule and close the pop-up window," +" or click :guilabel:`Save & New` to save the rule and immediately create a " +"new one." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:144 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:146 +msgid "" +"In the :guilabel:`Rules & Rewards` tab of the program form, click " +":guilabel:`Add` next to :guilabel:`Rewards` to add *rewards* to the program." +" This reveals a :guilabel:`Create Rewards` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:151 +msgid "" +"The options for :guilabel:`Rewards` vary depending on the selected " +":ref:`Program Type `." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:154 +msgid "The following options are available for configuring rewards:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:156 +msgid "" +":guilabel:`Reward Type`: Select the reward type among :guilabel:`Free " +"Product`, :guilabel:`Discount`, and :guilabel:`Free Shipping`. The other " +"options for reward configuration depend on the :guilabel:`Reward Type` " +"selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:160 +msgid ":guilabel:`Free Product`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162 +msgid "" +":guilabel:`Quantity Rewarded`: Select the number of free products rewarded " +"to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:163 +msgid "" +":guilabel:`Product`: Select the product given for free as a reward. Only one" +" product can be selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:165 +msgid "" +":guilabel:`Product Tag`: Select a tag to further specify the free product " +"eligible for the reward." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:168 +msgid ":guilabel:`Discount`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:170 +msgid "" +":guilabel:`Discount`: Enter the discounted amount in either " +":guilabel:`percentage`, :guilabel:`currency per point`, or " +":guilabel:`currency per order`. Then, select whether the discount applies to" +" the entire :guilabel:`Order`, only the :guilabel:`Cheapest Product` on the " +"order, or only :guilabel:`Specific Products`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:174 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:179 +msgid "" +":guilabel:`Max Discount`: Enter the maximum amount (in currency) that this " +"reward may grant as a discount. Leave this field at `0` for no limit." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:177 +msgid ":guilabel:`Free Shipping`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:182 +msgid "" +":guilabel:`In exchange of`: Enter the number of points required to exchange " +"for the reward (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get " +"Y` programs)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:184 +msgid "" +":guilabel:`Description on order`: Enter the description of the reward, which" +" is displayed to the customer upon checkout." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Rewards configuration window for a discount or loyalty program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices.rst:5 +msgid "Manage your pricing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:3 +msgid "Foreign currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5 +msgid "" +"With Odoo, pricelists can be used to manage prices in a number of foreign " +"currencies. Specifically, Odoo has the ability to work with 167 total " +"currencies." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:9 +msgid "" +"In order to use multiple currencies in Odoo *Sales*, the *Accounting* " +"application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:15 +msgid "" +"Once the *Accounting* app has been installed, foreign currencies can be " +"added to the database. Navigate to :menuselection:`Accounting app --> " +"Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, " +"and locate the :guilabel:`Main Currency` setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "" +"How the main currency feature appears on settings page in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:23 +msgid "" +"Odoo automatically sets the main currency as the currency of the country the" +" company is based in." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:25 +msgid "" +"To change the main currency of the company, select the drop-down menu in the" +" :guilabel:`Currency` field, select the desired currency, and be sure to " +":guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:29 +msgid "" +"To ensure currency rates are updated automatically, enable the *automatic " +"currency rates* feature on the *Accounting* settings page " +"(:menuselection:`Accounting app --> Configuration --> Settings --> " +"Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:37 +msgid "" +"Click the checkbox beside the :guilabel:`Automatic Currency Rates` feature, " +"choose a designated bank to get the currency rates from in the " +":guilabel:`Service` field drop-down menu, and select an :guilabel:`Interval`" +" of time for the updates to take place. Then determine when the date of the " +":guilabel:`Next Run` should be." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42 +msgid "" +"To instantly update the currency rates, click the :guilabel:`🔁 (circular " +"arrows)` icon, located to the right of the :guilabel:`Next Run` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:45 +msgid "" +"When all configurations are complete, be sure to :guilabel:`Save` all " +"changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:48 +msgid "" +"All payment methods **must** be in the same currency as the sales journal, " +"or the company currency, if the company currency is not set. If it is not " +"the same, a :guilabel:`Validation Error` message appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:53 +msgid "View, edit, and add currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:55 +msgid "" +"To view, edit, and add currencies to the database, making them available on " +"pricelists and on the :guilabel:`Main Currency` drop-down menu, click the " +":guilabel:`Currencies` link, located beneath the :guilabel:`Currency` field " +"on the :menuselection:`Accounting app --> Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:59 +msgid "" +"When the :guilabel:`Currencies` link is clicked, a separate " +":guilabel:`Currencies` page is revealed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How the main currencies page appears in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:65 +msgid "" +"On this page, Odoo provides a master list of 167 global currencies. Each row" +" shows the corresponding :guilabel:`Currency`, :guilabel:`Symbol`, " +":guilabel:`Name`, date of the :guilabel:`Last Update`, and " +":guilabel:`Current Rate` (compared to the default currency of the country in" +" which the company is based)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:70 +msgid "" +"To the far right, there are two columns, which can be toggled on or off:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:72 +msgid "" +":guilabel:`Use on eBay`: this currency can be used with the connected eBay " +"account (if applicable)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:74 +msgid "" +":guilabel:`Active`: this currency is activated, which means it can be added " +"to a pricelist, or used as the main currency of the company, if desired (via" +" :menuselection:`Accounting app --> Configuration --> Settings --> " +"Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:79 +msgid "" +"By default, all the :guilabel:`Active` currency options are at the top of " +"the list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:82 +msgid "" +"It is recommended that *at least* one pricelist is created per " +":guilabel:`Active` currency. See :doc:`./pricing` to learn more about " +"pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:85 +msgid "" +"To toggle options on/off, click the toggle switch in the row for the " +"corresponding column. When *on* the color of the switch is green. When " +"*off*, the color of the switch is grey." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:89 +msgid "Currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:91 +msgid "" +"To edit any currency on the :guilabel:`Currencies` page, click the desired " +"currency to reveal the detail form for that specific currency, and proceed " +"to make any necessary changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:98 +msgid "" +"On the currency detail form, the relevant currency code appears in the " +":guilabel:`Currency` field. Beneath that, the name for the currency is in " +"the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:101 +msgid "" +"Then, toggle the currency's availability with the :guilabel:`Active` toggle:" +" *on* is indicated with a green switch, and *off* is indicated with a grey " +"switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:104 +msgid "" +"On the right of the currency detail form, the appropriate " +":guilabel:`Currency Unit` (e.g. `Dollars`) and :guilabel:`Currency Subunit` " +"(e.g. `Cents`) can be found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:107 +msgid "" +"If the currency is meant to be used for eBay purposes, toggle the " +":guilabel:`Use on eBay` option to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:110 +msgid "" +"Next, under the :guilabel:`Rates` tab, the various conversion rates can be " +"viewed, added, or deleted. Each row shows the :guilabel:`Date` of that " +"specific rate, the :guilabel:`Company` to which it is connected, followed by" +" the :guilabel:`Unit per...` and :guilabel:`...per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:115 +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:166 +msgid "" +"The *...* in each of the last two columns represents the main currency set " +"for the company. For example, if the main currency is set to `USD`, the " +"columns are titled :guilabel:`Unit per USD` and :guilabel:`USD per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:119 +msgid "" +"To add a new rate, click :guilabel:`Add a line` in the :guilabel:`Rates` " +"tab, and proceed to fill in the necessary information in the aforementioned " +"columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:123 +msgid "Main currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:125 +msgid "" +"If the selected currency is the main currency of the company, a blue banner " +"appears at the top of the currency detail form with the message: " +":guilabel:`This is your company's currency.`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a main currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:132 +msgid "" +"All the fields are the same as a typical currency detail form, but there " +"will **not** be a :guilabel:`Rates` tab because all other currency rates are" +" based off the main currency of the company." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:137 +msgid "Create new currency" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:139 +msgid "" +"If a desired currency isn't on the :guilabel:`Currencies` page, click the " +":guilabel:`New` button to open a blank currency template form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:143 +msgid "" +"The same :guilabel:`New` button is located in the upper-right corner of any " +"currency detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a blank currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:149 +msgid "" +"On the blank currency detail form, proceed to enter the desired currency " +"code in the :guilabel:`Currency` field. Beneath that, enter the name for the" +" currency in the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:153 +msgid "" +"Then, toggle the currency's availability with the :guilabel:`Active` toggle " +"switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:155 +msgid "" +"On the right of the currency detail form, enter the appropriate " +":guilabel:`Currency Unit` (e.g. `Dollars`) and appropriate " +":guilabel:`Currency Subunit` (e.g. `Cents`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:158 +msgid "" +"If the currency is meant to be used for eBay purposes, toggle the " +":guilabel:`Use on eBay` to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:161 +msgid "" +"Next, under the :guilabel:`Rates` tab, add a new rate by clicking " +":guilabel:`Add a line`. Then, proceed to confirm and adjust the " +":guilabel:`Date`, :guilabel:`Company`, :guilabel:`Unit per...`, and " +":guilabel:`...per Unit` fields to ensure all the auto-populated information " +"is accurate." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:171 +msgid "Currency-specific pricelists" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:173 +msgid "" +"It is recommended that *at least* one pricelist is created per active " +"currency in the database. To create (or assign) a pricelist to a specific " +"currency, start by navigating to :menuselection:`Sales app --> Products --> " +"Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:177 +msgid "" +"From the :guilabel:`Pricelists` page, either select an existing pricelist to" +" edit, or click :guilabel:`New` to create a new pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:180 +msgid "" +"On the pricelist detail form, for either a new or existing pricelist, adjust" +" the :guilabel:`Currency` field as desired." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:184 +msgid ":doc:`./pricing` to learn more about pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:187 +msgid "Auto-conversion from public price" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:189 +msgid "" +"It should be noted that the public price seen on products is directly " +"related to the main currency the company has set, which is configured by " +"navigating to :menuselection:`Accounting app --> Configuration --> Settings " +"--> Currencies section --> Main Currency --> Currency drop-down menu`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:193 +msgid "" +"The sales price automatically updates if the pricelist is changed to a " +"different pricelist that has a different currency than the company's main " +"currency. The change in price is directly related to the updated conversion " +"rate for that currency." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:198 +msgid "Set product prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:200 +msgid "" +"In order to have product prices set in place to avoid any changes in " +"currency rates, start by navigating to :menuselection:`Sales app --> " +"Products --> Products`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:203 +msgid "" +"From the :guilabel:`Products` page, select the desired product to modify. " +"Or, create a new product by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:206 +msgid "" +"Then, on the product detail form, click the :guilabel:`Extra Prices` smart " +"button, located in the upper-left corner. Doing so reveals a separate " +":guilabel:`Price Rules` page, specific to that particular product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "" +"How to set product prices based on foreign currency pricelists in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:214 +msgid "" +"Click :guilabel:`New`, and select the desired pricelist from the drop-down " +"menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:217 +msgid "" +"The :guilabel:`Applied On` field is auto-populated with the product, so " +"proceed to enter in the desired figures in the :guilabel:`Min. Quantity` and" +" :guilabel:`Price` fields." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:221 +msgid "" +"The figure in the :guilabel:`Min. Quantity` field means the " +":guilabel:`Price` being set will **only** trigger if at least that amount of" +" product is purchased." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:224 +msgid "" +"If necessary, configure a :guilabel:`Start Date` and :guilabel:`End Date` " +"for the set prices. Leaving those columns blank ensures the set price will " +"remain valid, regardless of the date of sale." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:227 +msgid "" +"If working in a multi-company environment, designate to which company this " +"price rule should be applied in the :guilabel:`Company` field. Leaving that " +"field blank ensures the price rule applies to all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:231 +msgid "" +"With those configurations complete, regardless of any changes/updates in " +"conversion, whenever those designated pricelists are applied to a customer " +"trying to purchase this specific product, these pre-determined set prices " +"appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:236 +msgid ":doc:`./pricing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3 +msgid "Pricelists, discounts, and formulas" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5 +msgid "" +"Odoo *Sales* has a useful pricelist feature that can be tailored to fit any " +"unique pricing strategy." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:7 +msgid "" +"A *pricelist* is a list of prices (or price rules) that Odoo uses to " +"determine the appropriate price for a customer. These pricelists can be set " +"with specific criteria (such as time periods, minimum quantity sold, and " +"more) in order to apply certain prices or discounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:11 +msgid "" +"Pricelists suggest certain prices, but they can always be overridden on the " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:14 +msgid "Pricing strategy options" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:16 +msgid "" +"To choose a pricing strategy, first navigate to :menuselection:`Sales app " +"--> Configuration --> Settings`. In the :guilabel:`Pricing` section, click " +"the checkbox next to the :guilabel:`Pricelists` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 +msgid "" +"Doing so reveals two additional options beneath it: :guilabel:`Multiple " +"prices per product` and :guilabel:`Advanced price rules (discounts, " +"formulas)`. A link labeled :guilabel:`Pricelists` also appears, which leads " +"to a separate pricelists page, wherein pricelists can be created and/or " +"modified." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25 +msgid "" +":guilabel:`Multiple prices per product`: provides the option to set several " +"different prices per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:27 +msgid "" +":guilabel:`Advanced price rules (discounts, formulas)`: provides the option " +"to create detailed price rules and apply discounts, margins, and roundings." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelist feature setting looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:34 +msgid "" +"After clicking the checkbox beside the :guilabel:`Pricelists` feature, " +"select one of those two options, then click :guilabel:`Save` to save all " +"changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:40 +msgid "" +"After activating and saving the :guilabel:`Pricelists` feature, the " +":guilabel:`Settings` page reloads and, from here, either select the " +":guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on " +"the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app -->" +" Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:328 +msgid "" +"Either option reveals the :guilabel:`Pricelists` page, in which pricelists " +"can be created and/or modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelists page looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:267 +msgid "" +"The :guilabel:`Public Pricelist` is the default pricelist used with Odoo " +"*Sales* and *eCommerce*." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:55 +msgid "" +"From the :guilabel:`Pricelists` page, either select the desired pricelist to" +" edit, or click :guilabel:`New` to create a new pricelist, which reveals a " +"blank pricelist form that can be configured in a number of different ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelist detail form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63 +msgid "" +"When creating a new pricelist, start by adding a name for the pricelist at " +"the top of the form, in the blank field. Next, select which " +":guilabel:`Currency` should be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:66 +msgid "" +"Then, if working in a multi-company environment, select which company this " +"pricelist should apply to in the :guilabel:`Company` field. If this field is" +" left blank, the pricelist is automatically applied to all companies in the " +"database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:71 +msgid "Price rules tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:73 +msgid "" +"The :guilabel:`Price Rules` tab functionality on a pricelist form varies " +"depending on the :guilabel:`Pricelists` setting chosen: either " +":guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules " +"(discounts, formulas)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77 +msgid "" +"However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` " +"tab are always the same, regardless of the chosen :guilabel:`Pricelists` " +"setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:81 +msgid "Price rules tab (multiple prices per product)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 +msgid "" +"With the :guilabel:`Multiple prices per product` setting activated, the " +":guilabel:`Price Rules` tab on pricelist forms provides the option to add " +"specific products, with a specific price, to a pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:87 +msgid "" +"To add a specific product and price to a pricelist form, click the " +":guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the " +":guilabel:`Products` column. Then, select the desired product for which a " +"specific price should be applied." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:91 +msgid "" +"Next, if necessary, select a product variant under the :guilabel:`Variants` " +"column (e.g. a specific product size, color, etc.). If no variants are " +"selected, then this price will apply to all variants of the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95 +msgid "" +"If a minimum amount of the product must be purchased in order to apply the " +"specific price, enter the amount under the :guilabel:`Min. Quantity` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 +msgid "" +"To configure the price of the product for this specific pricelist, enter the" +" desired amount under the :guilabel:`Price` column. Then, there is the " +"option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the " +"configured product price, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:102 +msgid "" +"To add another product line, click :guilabel:`Add a line` again, and repeat " +"the process. There is no limit to how many products can be added in the " +":guilabel:`Price Rules` tab of a pricelist form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105 +msgid "" +"For more information, check out the following section: :ref:`Multiple prices" +" per product `." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:109 +msgid "Price rules tab (advanced price rules)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 +msgid "" +"With the :guilabel:`Advanced price rules (discounts, formulas)` setting " +"activated, the :guilabel:`Price Rules` tab on pricelist forms provides the " +"option to configure detailed price rules based on formulas." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 +msgid "" +"Check out the :ref:`Advanced price rules (discounts, formulas) " +"` section for detailed steps on how to add " +"advanced price rules to a pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 +msgid "Time-based rules tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:121 +msgid "" +"Time-based rules are used specifically with :doc:`subscription products " +"`. Be sure to check out the Odoo" +" *Subscriptions* :doc:`documentation `." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125 +msgid "" +"Under the :guilabel:`Time-based rules` tab, the same functionality of the " +":guilabel:`Price Rules` tab is present, with the only difference being that " +"a repeating time period can be applied in the :guilabel:`Period` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:129 +msgid "" +"After a :guilabel:`Product` and potential :guilabel:`Variant` are selected " +"in the :guilabel:`Time-based rules` tab, select the blank field in the " +":guilabel:`Period` column to reveal a drop-down menu of pre-designated " +"recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133 +msgid "" +"New recurrence periods can also be directly created from this column, by " +"typing in the new name for the :guilabel:`Period` and then selecting " +":guilabel:`Create` to create the time period, which can be edited later. Or," +" select :guilabel:`Create and edit...` to reveal a pop-up form, in which the" +" new recurrence period can be directly configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Custom time period pop-up form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 +msgid "" +"From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, " +":guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). " +"When finished, click :guilabel:`Save and Close`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 +msgid "" +"Lastly, add the desired price for this time-based rule in the " +":guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:148 +msgid ":doc:`/applications/sales/subscriptions`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 +msgid "" +"Under the :guilabel:`Configuration` tab, there are a few options that can " +"further customize the pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Configuration tab on pricelist detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 +msgid "" +"From here, under the :guilabel:`Availability` section, in the " +":guilabel:`Country Groups` field, certain country groups can be added to the" +" pricelist. There is no limit to how many country groups can be added in " +"this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:165 +msgid "" +"If no country is set for a customer, Odoo takes the first pricelist without " +"any country group." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:167 +msgid "" +"Under the :guilabel:`Website` section, there are a few options that can be " +"configured. In the :guilabel:`Website` field, this pricelist can be applied " +"to a specific website, if working in a multi-website environment. If left " +"blank, the pricelist will be applied to all websites in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:172 +msgid "" +"Click the :guilabel:`Selectable` checkbox to have this pricelist as a " +"selectable option for customers to choose as they shop. If the " +":guilabel:`Selectable` box is left unchecked, customers **cannot** select " +"this pricelist for themselves as they shop." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 +msgid "" +"Lastly, there is the option to add an :guilabel:`E-commerce Promotional " +"Code`. To add a code, type in the desired promo code that, when entered " +"during the checkout process, applies the pricelist to the customer, even if " +"the customer does not fall into the previously-specified criteria." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 +msgid "Show discount percentage to customers" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 +msgid "" +"With Odoo *Sales*, the option to show the public price *and* the computed " +"discount percentage on the product catalog is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:186 +msgid "" +"To do that, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`, and in the :guilabel:`Pricing` section, click the checkbox next " +"to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to " +"save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 +msgid "" +"After activating the :guilabel:`Discounts` feature, navigate to the " +"pricelists page, either by clicking the :guilabel:`Pricelists` link from the" +" :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> " +"Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:194 +msgid "" +"On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On" +" the pricelist form, click into the :guilabel:`Configuration` tab. In the " +":guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` " +"section is now available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "" +"What the discount options are on the configuration tab of a pricelist in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:202 +msgid "The options available in this section are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:204 +msgid "" +":guilabel:`Discount included in the price`: shows the customer only the " +"final price with the discount already included." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:206 +msgid "" +":guilabel:`Show public price & discount to the customer`: shows the customer" +" the public price *and* the discount they're earning." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:210 +msgid "Customer pricelist application" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:212 +msgid "" +"While the default pricelist applied to any customer is the :guilabel:`Public" +" Pricelist`, Odoo provides the opportunity to directly apply a different " +"pricelist to customers on their contact form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 +msgid "" +"To do that, open the desired customer's contact form, either by navigating " +"to :menuselection:`Sales app --> Orders --> Customers` and selecting the " +"customer from the main :guilabel:`Customers` page, or by clicking on the " +"customer's name on a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Sample customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 +msgid "" +"On the desired customer's contact form, under the :guilabel:`Sales & " +"Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist " +"should be applied to this specific customer from the drop-down menu in the " +":guilabel:`Pricelist` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "The pricelist field in a customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:236 +msgid "" +"To apply several prices per individual product, select the " +":guilabel:`Multiple prices per product` option, after enabling the " +":guilabel:`Pricelists` feature on the *Sales* app setting page " +"(:menuselection:`Sales app --> Configuration --> Settings`), and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:240 +msgid "" +"Next, apply pricelists to specific products using the product form. Navigate" +" to the :menuselection:`Sales app --> Products --> Products` and select the " +"product for which multiple prices should be applied. Selecting a product " +"from the :guilabel:`Products` page reveals that specific product's product " +"form on a separate page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 +msgid "" +"On the product form, click the :guilabel:`Extra Prices` smart button, " +"located at the top of the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the extra prices smart button appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:252 +msgid "" +"Doing so reveals a separate page displaying the :guilabel:`Price Rules` that" +" are specific to that particular product. Here, price rules can be edited or" +" created at any time." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the extra price rules per product page appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 +msgid "" +"To create a new price rule for a product from this specific :guilabel:`Price" +" Rules` page, click :guilabel:`New` to add a new, customizable row that has " +"the desired product already populated in the :guilabel:`Applied On` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 +msgid "" +"Next, select which :guilabel:`Pricelist` this specific product price rule " +"should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 +msgid "" +"To create a new pricelist from this page, type in the desired name of the " +"new pricelist in the :guilabel:`Pricelist` column, then select " +":guilabel:`Create` from the drop-down menu. All pricelists can be modified " +"at any time, by navigating to :menuselection:`Sales app --> Products --> " +"Pricelists`. Pricelists can also be created on that specific " +":guilabel:`Pricelists` page, as well." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +msgid "" +"After the desired pricelist is added to the row, designate a :guilabel:`Min." +" Quantity` for the price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 +msgid "" +"If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the " +":guilabel:`Price` column will be applied to orders of 2 or more products. " +"So, in theory, if a single product costs $100, customers can be encouraged " +"to buy more, if the :guilabel:`Price` is set at $85 per product for a " +":guilabel:`Min. Quantity` of `2` products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +msgid "" +"Next, enter the desired amount in the :guilabel:`Price` column. Then, if " +"needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the " +"product's price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 +msgid "" +"And lastly, if working in a multi-company environment, select which company " +"this price rule should be applied to in the :guilabel:`Company` field. " +"Leaving this field blank means the price rule applies for all companies in " +"the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 +msgid "" +"Click away from the row to activate Odoo's auto-save capability, meaning " +"that newly-created price rule is now ready to be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 +msgid "" +"Proceed to add as many unique price rules per product as desired. There is " +"no limit to how many price rules can be added per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 +msgid "" +"With the price rule(s) in place for a specific product, customers who fall " +"into those corresponding pricelists automatically see those new prices " +"applied. The number of price rules applied to a particular product are also " +"displayed in the :guilabel:`Extra Prices` smart button, located on every " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +msgid "" +"When a price rule/pricelist is added to a product via the :guilabel:`Extra " +"Prices` smart button, it is also reflected on the pricelist itself. " +"Similarly, when a price rule for a specific product is added to a pricelist," +" it is also reflected on the product form via the :guilabel:`Extra Prices` " +"smart button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 +msgid "" +"The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature" +" provides the option to set price change rules based on discounts and " +"formulas. These changes can be relative to the product list/catalog price, " +"the product's cost, or another pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 +msgid "" +"To use advanced pricing rules, with discounts and formulas, select the " +":guilabel:`Advanced price rules (discounts, formulas)` option, after " +"enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page " +"(:menuselection:`Sales app --> Configuration --> Settings`), and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +msgid "" +"After activating and saving that :guilabel:`Pricelists` feature, the " +":guilabel:`Settings` page reloads and, from here, either select the " +":guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on " +"the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app -->" +" Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 +msgid "" +"From the :guilabel:`Pricelists` page, select a desired pricelist to modify, " +"or create a new pricelist by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +msgid "" +"On the pricelist form, under the :guilabel:`Price Rules` tab, click " +":guilabel:`Add a line` to add an advanced price rule. Doing so reveals a " +":guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule " +"is configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +msgid "Price computation" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 +msgid "" +"On this form, first choose one of the three :guilabel:`Computation` options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 +msgid "" +":guilabel:`Fixed Price`: the price computation is based on a fixed price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 +msgid ":guilabel:`Discount`: the price computation is based on a discount." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 +msgid ":guilabel:`Formula`: the price computation is based on a formula." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +msgid "" +"Each :guilabel:`Computation` option reveals its own computation-specific " +"fields on the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +msgid "" +"If :guilabel:`Fixed Price` is selected, enter the desired price in the " +":guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, " +"enter the desired discount percentage in the :guilabel:`Discount` field that" +" appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +msgid "" +"If :guilabel:`Formula` is selected, a number of configurable options appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "The various formula computation options present in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 +msgid "" +"To configure the :guilabel:`Formula` computation option, start by selecting " +"an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, " +":guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the " +"advanced price rule formula will be based on." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 +msgid "" +"Next, in the :guilabel:`Discount` field, determine how much of a discount " +"should be applied. It should be noted that a mark-up can be applied by " +"setting a negative discount in this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 +msgid "" +"To formulate a 100% markup (or 2 times the cost of the product), with a $5 " +"minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the " +":guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is " +"often seen in retail situations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "" +"How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 +msgid "" +"Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or " +"subtract) to the amount calculated with the discount. After that, enter a " +"desired figure in the :guilabel:`Rounding Method` field. The rounding method" +" sets the price so that it is a multiple of the value in the field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +msgid "Rounding is applied *after* the discount and *before* the surcharge." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +msgid "" +"To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10`" +" and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 +msgid "" +"Lastly, specify the minimum amount of margin over the base price in the " +":guilabel:`Margins` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 +msgid "" +"Once all formula-related configurations are complete, Odoo provides an " +"example of the formula in a blue block to the right of the configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +msgid "" +"To apply 20% discounts, with prices rounded up to 9.99, set the " +":guilabel:`Based on` field to :guilabel:`Sales Price`, the " +":guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to " +"`-0.01`, and the :guilabel:`Rounding Method` field to `10`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 +msgid "" +"At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the " +":guilabel:`Conditions` section." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +msgid "" +"Here, start by selecting one of the options in the :guilabel:`Apply On` " +"field:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 +msgid "" +":guilabel:`All Products`: the advanced pricelist rule will be applied to all" +" products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 +msgid "" +":guilabel:`Product Category`: the advanced pricelist rule will be applied to" +" a specific category of products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +msgid "" +":guilabel:`Product`: the advanced pricelist rule will be applied to a " +"specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +msgid "" +":guilabel:`Product Variant`: the advanced pricelist rule will be applied to " +"a specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +msgid "" +"If any of those options, apart from :guilabel:`All Products`, are selected, " +"a new option-specific field appears, in which the specific " +":guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product " +"Variant` must be chosen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 +msgid "" +"Then, select a minimum quantity to be applied to the advanced pricelist rule" +" in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for" +" the pricelist item validation in the :guilabel:`Validity` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 +msgid "" +"Once all configurations are complete, either click :guilabel:`Save & Close` " +"to save the advanced pricelist rule, or click :guilabel:`Save & New` to " +"immediately create another advanced pricelist rule on a fresh form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +msgid "" +"If a price rule is set for a particular product, and another one for its " +"product category, Odoo takes the rule of the product itself." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 +msgid "" +":doc:`/applications/websites/ecommerce/managing_products/price_management`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products.rst:5 +msgid "Manage your products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:3 +msgid "Import products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:5 +msgid "" +"Odoo *Sales* provides a template for importing products with categories and " +"variants, which can be opened and edited with any spreadsheet software " +"(Microsoft Excel, OpenOffice, Google Sheets, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:8 +msgid "" +"When this spreadsheet is filled out properly, it can be quickly uploaded to " +"the Odoo database. When uploaded, those products are instantly added, " +"accessible, and editable in the product catalog." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:12 +msgid "Import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:14 +msgid "" +"In order to import products with categories and variants, the *Import " +"Template for Products* **must** be downloaded. Once downloaded, the template" +" can be adjusted and customized, and then uploaded back into the Odoo " +"database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:18 +msgid "" +"To download the necessary import template, navigate to :menuselection:`Sales" +" app --> Products --> Products`. On the :guilabel:`Products` page, click the" +" :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:22 +msgid "" +"From this drop-down menu, select the :guilabel:`Import records` option." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The Import records option selectable from the gear icon on the Products page" +" in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:28 +msgid "" +"Selecting :guilabel:`Import records` reveals a separate page with a link to " +"download the :guilabel:`Import Template for Products`. Click that link to " +"download the template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:35 +msgid "" +"Once the template download is complete, open the spreadsheet file to " +"customize it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:38 +msgid "Customize product import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:40 +msgid "" +"When the import template has been downloaded and opened, it's time to modify" +" its contents. However, before any changes are made, there are a few " +"elements to keep in mind during the process:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:43 +msgid "" +"Feel free to remove any columns that aren't deemed necessary. But, it is " +"*strongly* advised that the :guilabel:`Internal Reference` column remains." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:46 +msgid "" +"While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in " +"the :guilabel:`Internal Reference` column for each product can be helpful in" +" many cases. This can even be from previous software spreadsheets to ease " +"the transition into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:50 +msgid "" +"For example, when updating imported products, the same file can be imported " +"several times without creating duplicates, thus enhancing the efficiency and" +" simplicity of imported product management." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:52 +msgid "" +"Do **not** change the labels of columns that are meant to be imported. " +"Otherwise, Odoo won't recognize them, forcing the user to map them on the " +"import screen manually." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:54 +msgid "" +"Feel free to add new columns to the template spreadsheet, if desired. " +"However, to be added, those fields **must** exist in Odoo. If Odoo can't " +"match the column name with a field, it can be matched manually during the " +"import process." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:58 +msgid "" +"During the import process of the completed template, Odoo reveals a page " +"showcasing all the elements of the newly-configured product template " +"spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, " +"and :guilabel:`Comments`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:62 +msgid "" +"To manually match a column name with a field in Odoo, click the " +":guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` " +"that needs a manual adjustment, and select the appropriate field from that " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:0 +msgid "" +"The Odoo Field drop-down menu next to a Field Column that needs to be " +"manually adjusted." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:71 +msgid "Import product template spreadsheet" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:73 +msgid "" +"After customizing the product template spreadsheet, return to the Odoo " +"product import page, where the template download link is found, and click " +"the :guilabel:`Upload File` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The upload file button on the import products template download page in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:81 +msgid "" +"Then, a pop-up window appears, in which the completed product template " +"spreadsheet file should be selected and uploaded to Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:84 +msgid "" +"After that, Odoo reveals a page showcasing all the elements of the newly-" +"configured product template spreadsheet, separated by :guilabel:`File " +"Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The import a file page in Odoo Sales after a product template has been " +"uploaded." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:91 +msgid "" +"From here, the :guilabel:`File Column` can be manually assigned to an " +":guilabel:`Odoo Field`, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:94 +msgid "" +"To make sure everything is appropriate, and all the columns and fields are " +"lined up accurately, click the :guilabel:`Test` button in the upper-left " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:97 +msgid "" +"If everything is lined up and applied correctly, Odoo reveals a blue banner " +"at the top of the page, informing the user that :guilabel:`Everything seems " +"valid`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The everything seems valid message that appears if file columns are entered " +"correctly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:104 +msgid "" +"If there are any errors, Odoo reveals a red banner at the top of the page, " +"with instructions of where to locate the specific issues, and how to fix " +"them." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The import error message that appears if file columns don't match an Odoo " +"Field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:111 +msgid "" +"Once those errors are fixed, click :guilabel:`Test` again to ensure all " +"necessary issues have been remedied appropriately." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:114 +msgid "" +"If additional product template spreadsheets need to be uploaded, click the " +":guilabel:`Load File` button, select the desired product template " +"spreadsheet, and repeat the process." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:117 +msgid "When everything is ready, click the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:119 +msgid "" +"When clicked, Odoo instantly imports those products, and reveals the main " +":guilabel:`Products` page, with a pop-up message in the upper-right corner. " +"This pop-up message informs the user how many products were successfully " +"imported." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The pop-up window that appears after a successful product import process in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:127 +msgid "" +"At this point, all the newly-imported products are accessible and editable " +"via the :guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:131 +msgid "Import relation fields, attributes, and variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:133 +msgid "" +"It's important to note that an Odoo object is always related to many other " +"objects. For example, a product is linked to product categories, attributes," +" vendors, and things of this nature. These links/connections are known as " +"relations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:138 +msgid "" +"In order to import product relations, the records of the related object " +"**must** be imported *first* from their own list menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:142 +msgid "Relation fields" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:144 +msgid "" +"On product forms in Odoo, there are a number of fields that can be modified " +"and customized at any time. These fields are found under every tab on a " +"product form. While these fields are easily editable directly on the product" +" form, they can also be modified via a product import." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:148 +msgid "" +"As mentioned, relation fields of this nature can **only** be imported for " +"products if they already exist in the database. For example, if a user " +"attempts to import a product with a *Product Type*, it can only be one of " +"the preconfigured product types existing in the database (e.g. *Storable " +"Product*, *Consumable*, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:153 +msgid "" +"To import information for a relation field on a product import template " +"spreadsheet, add the name of the field as a column name/title on the " +"spreadsheet. Then, on the appropriate product line, add the desired relation" +" field option." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:157 +msgid "" +"When all desired relation field information has been entered, save the " +"spreadsheet, and import it to the database, per the process mentioned above " +"(:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> " +"Import records --> Upload File`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:161 +msgid "" +"Once the spreadsheet with the newly-configured relation field information " +"has been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:164 +msgid "" +"When the newly-changed/modified products, complete with the new relation " +"field information, has been imported and uploaded, that new information can " +"be found on the :guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:168 +msgid "Attributes and values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:170 +msgid "" +"Odoo also allows users to import product attributes and values that can be " +"used for products that already exist in the database, and/or with imported " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:173 +msgid "" +"To import attributes and values, a separate spreadsheet or CSV file " +"dedicated to attributes and values **must** be imported and uploaded before " +"they can be used for other products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:176 +msgid "" +"The column names/titles of the attributes and values spreadsheet should be " +"as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, " +":guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "An attributes and values spreadsheet template for imports." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:184 +msgid ":guilabel:`Attribute`: name of the attribute (e.g. `Size`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:185 +msgid "" +":guilabel:`Display Type`: display type used in the product configurator. " +"There are three display type options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:188 +msgid ":guilabel:`Radio`: values displayed as radio buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:189 +msgid ":guilabel:`Selection`: values displayed in a selection list" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:190 +msgid ":guilabel:`Color`: values denoted as a color selection" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:192 +msgid "" +":guilabel:`Variant Creation Mode`: how the variants are created when applied" +" to a product. There are three variant creation mode options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:195 +msgid "" +":guilabel:`Instantly`: all possible variants are created as soon as the " +"attribute, and its values, are added to a product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:197 +msgid "" +":guilabel:`Dynamically`: each variant is created **only** when its " +"corresponding attributes and values are added to a sales order" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:199 +msgid ":guilabel:`Never`: variants are **never** created for the attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:202 +msgid "" +"The :guilabel:`Variants Creation Mode` **cannot** be changed once the " +"attribute is used on at least one product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:205 +msgid "" +":guilabel:`Values/Value`: values pertaining to the corresponding attribute. " +"If there are multiple values for the same attribute, the values need to be " +"in individual lines on the spreadsheet." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:208 +msgid "" +"Once the desired attributes and values have been entered and saved in the " +"spreadsheet, it's time to import and upload it into Odoo. To do that, " +"navigate to :menuselection:`Sales app --> Configuration --> Attributes --> " +"⚙️ (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:212 +msgid "" +"Once the spreadsheet with the newly-configured attributes and values has " +"been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Attributes` page. That's where those newly-added attributes and " +"values can be found and edited, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:216 +msgid "" +"As mentioned previously, when attributes and values have been added to the " +"Odoo database, they can be used for existing or imported products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:220 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +msgid "Product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:222 +msgid "" +"When product attributes and values are configured in the database, they can " +"be used on product import spreadsheets to add more information and detail to" +" products being imported." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:225 +msgid "" +"To import products with product attributes and values, the product import " +"template spreadsheet must be configured with specific :guilabel:`Product " +"Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and " +":guilabel:`Name` columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:229 +msgid "" +"There can be other columns, as well, but these columns are **required** in " +"order to properly import products with specific variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"Product variants spreadsheet with product attributes and variants for import" +" purposes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:236 +msgid ":guilabel:`Name`: product name" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:237 +msgid ":guilabel:`Product Attributes / Attribute`: name of attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:238 +msgid "" +":guilabel:`Product Attributes / Values`: values pertaining to the " +"corresponding attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:241 +msgid "" +"To import multiple values, separate them by *just* a comma, **not** a comma " +"followed by a space, in the product import template spreadsheet (e.g. " +"`furniture,couch,home`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:244 +msgid "" +"When the desired products and product variants have been entered and saved " +"in the spreadsheet, it's time to import and upload them into Odoo. To do " +"that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️" +" (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:248 +msgid "" +"Once the spreadsheet with the newly-configured products and product variants" +" has been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Products` page. That's where the newly-added products can be " +"found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:252 +msgid "" +"To view and modify the attributes and variants on any products, select the " +"desired product from the :guilabel:`Products` page, and click the " +":guilabel:`Attributes \\& Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:256 +msgid ":doc:`variants`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 +msgid "Product images with Google Images" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 +msgid "" +"Having appropriate product images in Odoo is useful for a number of reasons." +" However, if a lot of products need images, assigning them can become " +"incredibly time-consuming." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:8 +msgid "" +"Fortunately, by configuring the *Google Custom Search* API within an Odoo " +"database, finding product images for products (based on their barcode) is " +"extremely efficient." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:16 +msgid "" +"In order to utilize *Google Custom Search* within an Odoo database, both the" +" database and the Google API must be properly configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:20 +msgid "" +"Free Google accounts allow users to select up to 100 free images per day. If" +" a higher amount is needed, a billing upgrade is required." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:26 +msgid "Google API dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 +msgid "" +"Go to the `Google Cloud Platform API & Services " +"`_ page to generate Google Custom " +"Search API credentials. Then, log in with a Google account. Next, agree to " +"their :guilabel:`Terms of Service` by checking the box, and clicking " +":guilabel:`Agree and Continue`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:32 +msgid "" +"From here, select (or create) an API project to store the credentials. Start" +" by giving it a memorable :guilabel:`Project Name`, select a " +":guilabel:`Location` (if any), then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:35 +msgid "" +"With the :guilabel:`Credentials` option selected in the left sidebar, click " +":guilabel:`Create Credentials`, and select :guilabel:`API key` from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "API & Services page on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:42 +msgid "" +"Doing so reveals an :guilabel:`API key created` pop-up window, containing a " +"custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the " +"pop-up window -- it will be used later. Once the key is copied (and saved " +"for later use), click :guilabel:`Close` to remove the pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The API key created pop-up window that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:50 +msgid "On this page, search for `Custom Search API`, and select it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 +msgid "" +"From the :guilabel:`Custom Search API` page, enable the API by clicking " +":guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"\"Custom Search API\" page with Enable button highlighted on Google Cloud " +"Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:65 +msgid "Google Programmable Search dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:67 +msgid "" +"Next, go to `Google Programmable Search Engine " +"`_, and click either of the " +":guilabel:`Get started` buttons. Log in with a Google account, if not " +"already logged in." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Google Programmable Search Engine page with the Get Started buttons." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:75 +msgid "" +"On the :guilabel:`Create a new search engine` form, fill out the name of the" +" search engine, along with what the engine should search, and be sure to " +"enable :guilabel:`Image Search` and :guilabel:`SafeSearch`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"Create new search engine form that appears with search engine " +"configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 +msgid "Validate the form by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:84 +msgid "" +"Doing so reveals a new page with the heading: :guilabel:`Your new search " +"engine has been created`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The Your New Search Engine Has Been Created page that appears with copy " +"code." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:91 +msgid "" +"From this page, click :guilabel:`Customize` to open the " +":menuselection:`Overview --> Basic` page. Then, copy the ID in the " +":guilabel:`Search engine ID` field. This ID is needed for the Odoo " +"configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Basic overview page with search engine ID field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 +msgid "" +"In the Odoo database, go to the :menuselection:`Settings app` and scroll to " +"the :guilabel:`Integrations` section. From here, check the box beside " +":guilabel:`Google Images`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Google Images setting in the Odoo Settings app page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:112 +msgid "" +"Next, return to the :menuselection:`Settings app`, and scroll to the " +":guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and " +":guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google " +"Images` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:115 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 +msgid "Product images in Odoo with Google Custom Search API" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:122 +msgid "" +"Adding images to products in Odoo can be done on any product or product " +"variant. This process can be completed in any Odoo application that provides" +" access to product pages (e.g. *Sales* app, *Inventory* app, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:126 +msgid "" +"Below is a step-by-step guide detailing how to utilize the *Google Custom " +"Search API* to assign images to products in Odoo using the Odoo *Sales* " +"application:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:129 +msgid "" +"Navigate to the :guilabel:`Products` page in the *Sales* app " +"(:menuselection:`Sales app --> Products --> Products`). Or, navigate to the " +":guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales " +"app --> Products --> Product Variants`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:132 +msgid "Select the desired product that needs an image." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:135 +msgid "" +"Only products (or product variants) that have a barcode, but **not** an " +"image, are processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:137 +msgid "" +"If a product with one or more variants is selected, each variant that " +"matches the aforementioned criteria is processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:140 +msgid "" +"Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select " +":guilabel:`Get Pictures from Google Images` from the menu that pops up." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The Get Pictures from Google Images option from the Action drop-down menu in" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:147 +msgid "On the pop-up window that appears, click :guilabel:`Get Pictures`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The pop-up that appears in which the user should click Get Picture in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:153 +msgid "Once clicked, the image(s) will appear incrementally." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:156 +msgid "" +"Only the first 10 images are fetched immediately. If you selected more than " +"10, the rest are fetched as a background job." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:159 +msgid "" +"The background job processes about 100 images in a minute. If the quota " +"authorized by Google (either with a free or a paid plan) is reached, the " +"background job puts itself on hold for 24 hours. Then, it will continue " +"where it stopped the day before." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:164 +msgid "" +"`Create, modify, or close your Google Cloud Billing account " +"`_" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 +msgid "" +"Product variants are used to give single products a variety of different " +"characteristics and options for customers to choose from, such as size, " +"style, or color, just to name a few." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:8 +msgid "" +"Products variants can be managed via their individual product template, or " +"by navigating to either the :guilabel:`Product Variants` or " +":guilabel:`Attributes` page. All of these options are located within the " +"Odoo *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 +msgid "" +"An apparel company has the following variant breakdown for one their best-" +"selling t-shirts:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:15 +msgid "Unisex Classic Tee" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:17 +msgid "Color: Blue, Red, White, Black" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:18 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:20 +msgid "" +"Here, the **T-shirt** is the product template, and **T-shirt: Blue, S** is a" +" specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +msgid "" +"**Color** and **Size** are *attributes*, and the corresponding options (like" +" **Blue** and **S**) are *values*." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 +msgid "" +"In this instance, there is a total of twenty different product variants: " +"four **Color** options multiplied by five **Size** options. Each variant has" +" its own inventory count, sales totals, and other similar records in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 +msgid ":doc:`/applications/websites/ecommerce/managing_products/variants`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 +msgid "" +"To use product variants, the *Variants* setting **must** be activated in the" +" Odoo *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 +msgid "" +"To do that, go to :menuselection:`Sales app --> Configuration --> Settings`," +" and locate the :guilabel:`Product Catalog` section at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:42 +msgid "" +"In that section, check the box to enable the :guilabel:`Variants` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Activating product variants on the Settings page of the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:48 +msgid "" +"Then, click :guilabel:`Save` at the top of the :guilabel:`Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:51 +msgid "Attributes" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:53 +msgid "" +"Before product variants can be set up, attributes **must** be created. To " +"create, manage, and modify attributes, navigate to :menuselection:`Sales app" +" --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:57 +msgid "" +"The order of attributes on the :guilabel:`Attributes` page dictates how they" +" appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` " +"dashboard, and :guilabel:`eCommerce` pages." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:61 +msgid "" +"To create a new attribute from the :guilabel:`Attributes` page, click " +":guilabel:`New`. Doing so reveals a blank attributes form that can be " +"customized and configured in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "A blank attribute creation form in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:68 +msgid "" +"First, create an :guilabel:`Attribute Name`, such as `Color` or `Size`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 +msgid "" +"Next, in the optional :guilabel:`Category` field, select a category from a " +"drop-down menu to group similar attributes under the same section for added " +"specificity and organization." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 +msgid "" +"To view the details related to the attribute category selected, click the " +"internal link :guilabel:`➡️ (arrow)` icon to the far-right of the " +":guilabel:`Category` field. Doing so reveals that attribute category's " +"detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"A standard attribute category detail page accessible via its internal link " +"arrow icon." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 +msgid "" +"Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at" +" the top. Followed by :guilabel:`Related Attributes` associated with the " +"category. These attributes can be dragged-and-dropped into a desirable order" +" of priority." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:86 +msgid "" +"Attributes can be directly added to the category, as well, by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:89 +msgid "" +"To create an attribute category directly from this field, start typing the " +"name of the new category, then select either :guilabel:`Create` or " +":guilabel:`Create and edit...` from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:93 +msgid "" +"Clicking :guilabel:`Create` creates the category, which can be modified " +"later. Clicking :guilabel:`Create and edit...` creates the category and " +"reveals a :guilabel:`Create Category` pop-up window, in which the new " +"attribute category can be configured and customized." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 +msgid "" +"Beneath the :guilabel:`Category` field are the :guilabel:`Display Type` " +"options. The :guilabel:`Display Type` determines how this product is shown " +"on the online store, :guilabel:`Point of Sale` dashboard, and " +":guilabel:`Product Configurator`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 +msgid "The :guilabel:`Display Type` options are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:103 +msgid "" +":guilabel:`Radio`: options appear in a bullet-style list on the product page" +" of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104 +msgid "" +":guilabel:`Pills`: options appear as selectable buttons on the product page " +"of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:105 +msgid "" +":guilabel:`Select`: options appear in a drop-down menu on the product page " +"of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 +msgid "" +":guilabel:`Color`: options appear as small, colored squares, which reflect " +"any HTML color codes set, on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Display Types on Product Configurator on the online store in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:113 +msgid "" +"The :guilabel:`Variants Creation Mode` field informs Odoo when to " +"automatically create a new variant once an attribute is added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:116 +msgid "" +":guilabel:`Instantly`: creates all possible variants as soon as attributes " +"and values are added to a product template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:118 +msgid "" +":guilabel:`Dynamically`: creates variants **only** when corresponding " +"attributes and values are added to a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 +msgid ":guilabel:`Never (option)`: never automatically creates variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123 +msgid "" +"Once added to a product, an attribute's :guilabel:`Variants Creation Mode` " +"cannot be edited." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:125 +msgid "" +"Lastly, the :guilabel:`eCommerce Filter Visibility` field determines whether" +" these attribute options are visible to the customer on the front-end, as " +"they shop on the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 +msgid "" +":guilabel:`Visible`: the attribute values are visible to customers on the " +"front-end." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 +msgid "" +":guilabel:`Hidden`: the attribute values are hidden from customers on the " +"front-end." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:132 +msgid "Attribute values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:134 +msgid "" +"Attribute values should be added to the :guilabel:`Attribute Values` tab. " +"Values can be added to an attribute at any time, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 +msgid "" +"To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute " +"Values` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:139 +msgid "" +"Then, enter the name of the value in the :guilabel:`Value` column. Next, " +"check the box in the :guilabel:`Is custom value` column, if the value is " +"custom (i.e. the customer gets to provide unique specifications that are " +"specific to this particular value)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:144 +msgid "" +"If the :guilabel:`Display Type` - :guilabel:`Color` option is selected, the " +"option to add an HTML color code will appear to the far-right of the value " +"line, to make it easier for salespeople and customers to know exactly what " +"color option they're choosing." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Attribute values tab when add a line is clicked, showing the custom columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 +msgid "" +"To choose a color, click the blank circle in the :guilabel:`Color` column, " +"which reveals an HTML color selector pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Selecting a color from the HTML color pop-up window that appears on " +"attribute form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:159 +msgid "" +"In this pop-up window, select a specific color by dragging the color slider " +"to a particular hue, and clicking on the color portion directly on the color" +" gradient window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:162 +msgid "" +"Or, choose a specific color by clicking the *dropper* icon, and selecting a " +"desired color that's currently clickable on the screen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166 +msgid "" +"Attributes can also be created directly from the product template by adding " +"a new line and typing the name into the :guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +msgid "" +"Once an attribute is added to a product, that product is listed and " +"accessible, via the attribute's :guilabel:`Related Products` smart button. " +"That button lists every product in the database currently using that " +"attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176 +msgid "" +"Once an attribute is created, use the attribute (and its values) to create a" +" product variant. To do that, go to :menuselection:`Sales app --> Products " +"--> Products`, and select an existing product to view that desired product's" +" form. Or, click :guilabel:`Create` to create a new product, to which a " +"product variant can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181 +msgid "" +"On the product form, click the :guilabel:`Attributes \\& Variants` tab to " +"view, manage, and modify attributes and values for the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "The attributes and values tab on a typical product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 +msgid "" +"To add an attribute to a product, and subsequent attribute values, click " +":guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then," +" choose the desired attribute from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:193 +msgid "" +"Attributes can be created directly from the :guilabel:`Attributes \\& " +"Variants` tab of a product form. To do that, start typing the name of the " +"new attribute in the blank field, and select either :guilabel:`Create` or " +":guilabel:`Create and edit...` from the mini drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:198 +msgid "" +"Clicking :guilabel:`Create` creates the attribute, which can be customized " +"later. Clicking :guilabel:`Create and edit...` creates the attribute, and a " +":guilabel:`Create Attribute` pop-up form appears. In the pop-up form, " +"proceed to modify the attribute in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 +msgid "" +"Once an attribute is selected in the :guilabel:`Attribute` column, proceed " +"to select the specific attribute values to apply to the product, via the " +"drop-down menu available in the :guilabel:`Values` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:207 +msgid "There is no limit to how many values can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:210 +msgid "" +"Similar product variant creation processes are accessible through the " +"Purchase, Inventory, and eCommerce applications." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214 +msgid "Configure variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:216 +msgid "" +"To the far-right of the attribute line is a :guilabel:`Configure` button. " +"When clicked, Odoo reveals a separate page showcasing those specific " +":guilabel:`Product Variant Values`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The Product Variant Values page accessible via the Configure button on a " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 +msgid "" +"Here, the specific :guilabel:`Value` name, :guilabel:`HTML Color Index` (if " +"applicable), and :guilabel:`Value Price Extra` are viewable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:227 +msgid "" +"The :guilabel:`Value Price Extra` represents the increase in the sales price" +" if the attribute is selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230 +msgid "" +"When a value is clicked on the :guilabel:`Product Variant Values` page, Odoo" +" reveals a separate page, detailing that value's related details." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"A Product Variant Values page accessible via the Product Variants Values " +"general page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:237 +msgid "" +"On the specific product variant detail page, the :guilabel:`Value` and " +":guilabel:`Value Price Extra` fields can be found, along with an " +":guilabel:`Exclude for` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:240 +msgid "" +"In the :guilabel:`Exclude for` field, different :guilabel:`Product " +"Templates` and specific :guilabel:`Attribute Values` can be added. When " +"added, this specific attribute value will be excluded from those specific " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:245 +msgid "Variants smart button" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247 +msgid "" +"When a product has attributes and variants configured in its " +":guilabel:`Attributes \\& Variants` tab, a :guilabel:`Variants` smart button" +" appears at the top of the product form. The :guilabel:`Variants` smart " +"button indicates how many variants are currently configured for that " +"specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The variants smart button at the top of the product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:255 +msgid "" +"When the :guilabel:`Variants` smart button is clicked, Odoo reveals a " +"separate page showcasing all the specific product variant combinations " +"configured for that specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The variants page accessible via the variants smart button on the product " +"form in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:263 +msgid "Impact of variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:265 +msgid "" +"In addition to offering more detailed product options to customers, product " +"variants have their own impacts that can be taken advantage of throughout " +"the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:268 +msgid "" +":guilabel:`Barcode`: barcodes are associated with each variant, instead of " +"the product template. Each individual variant can have its own unique " +"barcode/SKU." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270 +msgid "" +":guilabel:`Price`: every product variant has its own public price, which is " +"the sum of the product template price *and* any extra charges for particular" +" attributes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:274 +msgid "" +"A red shirt's sales price is $23 -- because the shirt's template price is " +"$20, plus an additional $3 for the red color variant. Pricelist rules can be" +" configured to apply to the product template, or to the variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:278 +msgid "" +":guilabel:`Inventory`: inventory is counted for each individual product " +"variant. On the product template form, the inventory reflects the sum of all" +" variants, but the actual inventory is computed by individual variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281 +msgid "" +":guilabel:`Picture`: each product variant can have its own specific picture." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:284 +msgid "" +"Changes to the product template automatically apply to every variant of that" +" product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:287 +msgid ":doc:`import`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:3 +msgid "Returns and refunds" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:5 +msgid "" +"The Odoo *Sales* app provides two different ways to process returns. The " +"method used depends on whether or not an invoice has been sent." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:9 +msgid "Before invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:11 +msgid "" +"Returns are completed using *Reverse Transfers* when a customer decides to " +"return a product **before** an invoice has been sent or validated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:15 +msgid "" +"In order to use *Reverse Transfers*, the *Inventory* app **must** be " +"installed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:17 +msgid "" +"To start a return before invoicing, navigate to the :menuselection:`Sales` " +"app, select the desired sales order, and click on the :guilabel:`Delivery` " +"smart button to open the associated delivery order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A typical sales order with a highlighted delivery smart button in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:25 +msgid "On the validated delivery order, click :guilabel:`Return`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A validated delivery order with a highlighted Return button in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:31 +msgid "This opens a :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:33 +msgid "" +"By default, the :guilabel:`Quantity` matches the validated quantities from " +"the delivery order. Update the quantities, if necessary. Click on the " +":guilabel:`🗑️ (trash)` icon next to a line item to remove it from the " +"return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The \"Reverse Transfer\" pop-up window, to make a return before invoicing " +"the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:41 +msgid "" +"Next, click :guilabel:`Return` to confirm the return. This generates a new " +"warehouse operation for the incoming returned product(s)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Warehouse operation after a return has been confirmed in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:48 +msgid "" +"Upon receiving the return, the warehouse team validates the warehouse " +"operation by clicking :guilabel:`Validate`. Then, on the original sales " +"order, the :guilabel:`Delivered` quantity updates to reflect the difference " +"between the initial validated quantities and the returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The updated \"Delivered\" quantity on the sales order after the reverse " +"transfer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:56 +msgid "" +"When an invoice is created, the customer receives an invoice **only** for " +"the products they are keeping, if any." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:60 +msgid "After invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:62 +msgid "" +"Sometimes, customers return an item after they receive and/or pay for their " +"invoice. In these cases, a return using only *Reverse Transfers* is " +"insufficient since validated, or sent, invoices cannot be changed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:66 +msgid "" +"However, *Reverse Transfers* can be used in conjunction with *Credit Notes* " +"to complete the customer's return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:69 +msgid "" +"To start a return after invoicing, navigate to the relevant sales order in " +"the :menuselection:`Sales` app." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:72 +msgid "" +"If there is a payment registered on the sales order, the payment details " +"appear in the chatter, and the invoice (accessible through the " +":guilabel:`Invoices` smart button) has a green :guilabel:`In Payment` " +"banner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Sample of a green in payment banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:80 +msgid "" +"From the sales order, click on the :guilabel:`Delivery` smart button to view" +" the validated delivery order. Then, click :guilabel:`Return` to open the " +":guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:83 +msgid "" +"Next, edit the :guilabel:`Product` and/or :guilabel:`Quantity`, as needed " +"for the return. Then, click :guilabel:`Return`. This generates a new " +"warehouse operation for the incoming returned product(s), which is validated" +" by the warehouse team once the return is received by clicking " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:88 +msgid "" +"Then, on the sales order, the :guilabel:`Delivered` quantity updates to " +"reflect the difference between the initial validated quantities and the " +"returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:91 +msgid "" +"To process a refund, navigate to the relevant invoice (from the sales order," +" click on the :guilabel:`Invoices` smart button). Then, click the " +":guilabel:`Credit Note` button at the top of the validated invoice." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A typical customer invoice with a Credit Note button highlighted in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:99 +msgid "Doing so reveals a :guilabel:`Credit Note` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Typical credit note pop-up form that appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:105 +msgid "" +"Start by entering a :guilabel:`Reason displayed on Credit Note` and a " +"specific :guilabel:`Journal` to process the credit. Then, select a specific " +":guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:108 +msgid "" +"After the information is filled in, click :guilabel:`Reverse` or " +":guilabel:`Reverse and Create Invoice`. Then, edit the draft, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:111 +msgid "Lastly, click :guilabel:`Confirm` to confirm the credit note." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:113 +msgid "" +"When complete, a blue banner reading: :guilabel:`You have outstanding " +"credits for this customer. You can allocate them to mark this invoice as " +"paid.` appears at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:117 +msgid ":doc:`../../../finance/accounting/customer_invoices/credit_notes`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations.rst:5 +msgid "Send Quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 +msgid "Quotation deadlines" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:5 +msgid "" +"In the Odoo *Sales* application, it is possible to set deadlines on sales " +"quotations. Doing so encourages customers to act quickly during sales " +"negotiations, for they might fear for missing out on a good deal. As well, " +"deadlines also can also act as protection for a company in case an order has" +" to be fulfilled at a price that is no longer profitable for the business." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 +msgid "Quotation expiration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 +msgid "" +"In Odoo *Sales*, there's the option to add an expiration date to a " +"quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:15 +msgid "" +"To add an expiration date to a quotation, navigate to :menuselection:`Sales " +"app`, and select a desired quotation, or create a new one by clicking " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:18 +msgid "" +"On the quotation form, click the :guilabel:`Expiration` field to reveal a " +"pop-up calendar. From this pop-up calendar, select the desired month and " +"date as the expiration date for the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "The expiration field on a standard quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:26 +msgid "" +"By clicking the :guilabel:`Preview` button on a quotation, Odoo clearly " +"displays when that specific offer expires." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:0 +msgid "How customers will see deadlines on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 +msgid "Quotation template expiration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:36 +msgid "" +"The Odoo *Sales* application also makes it possible to add a deadline " +"expiration date to quotation templates." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:39 +msgid "" +"To add a deadline expiration date to a quotation template, navigate to " +":menuselection:`Sales app --> Configuration --> Quotation Templates`, and " +"either select the desired quotation template to which a deadline should be " +"added, or click :guilabel:`New` to build a new quotation template from " +"scratch." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:43 +msgid "" +"On the quotation template form, add a specific number of days to the " +":guilabel:`Quotation expires after` field, located beneath the quotation " +"template name. The number of days represents how long the quotation will be " +"valid for, before it expires." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "" +"The quotation expires after field on a quotation template form in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:51 +msgid "" +"Then, whenever that specific quotation template is used in a quote, an " +"expiration date is automatically calculated, based on the number of days " +"designated above. However, this date can be overwritten before sending the " +"quotation to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:56 +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:227 +msgid ":doc:`/applications/sales/sales/send_quotations/quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 +msgid "Deliveries and invoices to different addresses" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 +msgid "" +"People and businesses often use separate addresses for billing (invoicing) " +"and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can " +"have different specified addresses for delivery and invoicing." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 +msgid "" +"To properly utilize multiple addresses in Odoo, go to :menuselection:`Sales " +"app --> Configuration --> Settings` and scroll down to the " +":guilabel:`Quotations & Orders` heading. Then, check the box next to " +":guilabel:`Customer Addresses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Activate the Customer Addresses setting." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 +msgid "Contact form configuration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 +msgid "" +"To add multiple addresses to a contact, go to :menuselection:`Sales app --> " +"Orders --> Customers`, and clear any default filters from the search bar. " +"Then, click on the desired customer to open their contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:28 +msgid "Contact forms can be accessed in the *Contacts* application, as well." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30 +msgid "" +"From the contact form, click :guilabel:`Edit`, and then select " +":guilabel:`Add`, which is located under the :guilabel:`Contacts & Addresses`" +" tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which " +"additional addresses can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:38 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field to reveal a drop-down menu of address-" +"related options." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:41 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 +msgid "" +"Once an option is selected, proceed to enter the corresponding contact " +"information that should be used for the specified address type." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:56 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address and immediately input another one." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:60 +msgid "Address added to quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62 +msgid "" +"When a customer is added to a quotation, the :guilabel:`Invoice Address` and" +" :guilabel:`Delivery Address` fields autopopulate with the corresponding " +"addresses specified on the customer's contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Invoice and Delivery Addresses autopopulate on a quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:70 +msgid "" +"The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be" +" edited directly from the quotation by clicking the :guilabel:`Edit` button," +" and then clicking the :guilabel:`➡️ (right arrow)` internal link buttons " +"next to each address line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 +msgid "" +"These addresses can be updated at any time to ensure accurate invoicing and " +"delivery." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:77 +msgid "" +"If any changes are made on a form in Odoo, include *Contacts* forms, " +"remember to click :guilabel:`Save` to save the changes to the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 +msgid "Online payment order confirmation" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 +msgid "" +"The Odoo *Sales* application provides customers with the ability to confirm " +"orders, via an online payment, directly on a sales order. Once the sales " +"order is electronically paid for by the customer, the salesperson attached " +"to the sales order is instantly notified that the order is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10 +msgid "Activate online payments" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 +msgid "" +"In order to have customers confirm orders with an online payment, the " +"*Online Payment* setting **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:15 +msgid "" +"To activate the *Online Payment* feature, go to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " +"Orders` heading, check the box next to the :guilabel:`Online Payment` " +"feature, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:23 +msgid "" +"Beneath the :guilabel:`Online Payment` option on the *Sales* " +":guilabel:`Settings` page, there's a :guilabel:`Default Quotation Validity` " +"field. In this field, there's the option to add a specific number of days " +"for quotations to remain valid by default." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:27 +msgid "" +"To enable this feature on a standard quotation, click the checkbox for the " +":guilabel:`Payment` feature option, located in the :guilabel:`Online " +"confirmation` field, on the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting on a standard quotation in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 +msgid "" +"To enable this feature on a quotation template, click the checkbox for the " +":guilabel:`Payment` feature option, located in the :guilabel:`Online " +"confirmation` field of the quotation template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting on quotation template forms in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43 +msgid "Payment providers" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:45 +msgid "" +"After activating the :guilabel:`Online Payment` feature, a link to configure" +" :guilabel:`Payment Providers` appears beneath it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:48 +msgid "" +"Clicking that link reveals a separate :guilabel:`Payment Providers` page, in" +" which a large variety of payment providers can be enabled, customized, and " +"published." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "Payment providers page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:56 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:91 +msgid ":doc:`../../../finance/payment_providers`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:59 +msgid "Register a payment" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:61 +msgid "" +"After opening quotations in their customer portal, customers can click " +":guilabel:`Accept \\& Pay` to confirm their order with an online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The accept and pay button on an online quotation in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:68 +msgid "" +"After clicking :guilabel:`Accept \\& Pay`, customers are presented with " +":guilabel:`Validate Order` pop-up window containing different options for " +"them to make online payments, in the :guilabel:`Pay with` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "" +"How to register a payment on a validate order pop-up window in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:77 +msgid "" +"Odoo will **only** offer payment options on the :guilabel:`Validate Order` " +"pop-up window that have been published and configured on the " +":guilabel:`Payment Providers` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:80 +msgid "" +"Once the customer selects their desired method of payment, they will click " +"the :guilabel:`Pay` button on the pop-up window to confirm the order. Odoo " +"instantly notifies the assigned salesperson upon order confirmation with an " +"online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "" +"Sample of notification that appears in the chatter when an online payment is" +" made." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 +msgid ":doc:`quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:245 +msgid ":doc:`get_signature_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 +msgid "Online signatures for order confirmations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 +msgid "" +"The Odoo *Sales* application provides customers with the ability to confirm " +"orders, via an online signature, directly on the sales order. Once the sales" +" order is electronically signed by the customer, the salesperson attached to" +" the sales order is instantly notified that the order is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:11 +msgid "Activate online signatures" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:13 +msgid "" +"In order to have customers confirm orders with an online signature, the " +"*Online Signature* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:16 +msgid "" +"To activate the *Online Signature* feature, go to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " +"Orders` heading, and activate the :guilabel:`Online Signature` feature by " +"checking the box beside it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "" +"The Online Signature feature option in the Settings of the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:24 +msgid "Then, click the :guilabel:`Save` button in the top-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:27 +msgid "" +"When making a quotation template, the online signature feature is the " +":guilabel:`Signature` option, located in the :guilabel:`Online confirmation`" +" field of the quotation template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 +msgid "" +"The Online confirmation signature option found on every quotation template " +"in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:34 +msgid "" +"On standard quotations, the online signature feature is the " +":guilabel:`Signature` option, located under the :guilabel:`Other Info` tab " +"of the quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 +msgid "" +"The online signature feature option in the Other Info tab of a quotation " +"form in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:42 +msgid "Order confirmations with online signatures" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:44 +msgid "" +"When clients access quotations online through their customer portal, there's" +" a :guilabel:`Sign \\& Pay` button directly on the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "The Sign and Pay button present on online quotations in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 +msgid "" +"When clicked, a :guilabel:`Validate Order` pop-up window appears. In this " +"pop-up window, the :guilabel:`Full Name` field is auto-populated, based on " +"the contact information in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "The Validate Order pop-up window for online signatures in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:58 +msgid "" +"Then, customers have the option to enter an online signature with any of the" +" following options: :guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:61 +msgid "" +":guilabel:`Auto` lets Odoo automatically generate an online signature based " +"on the information in the :guilabel:`Full Name` field. :guilabel:`Draw` lets" +" the customer use the cursor to create a custom signature directly on the " +"pop-up window. And :guilabel:`Load` lets the customer upload a previously-" +"created signature file from their computer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:66 +msgid "" +"After the customer has chosen any of the three previously mentioned " +"signature options (:guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`)," +" they will click the :guilabel:`Accept \\& Sign` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:70 +msgid "" +"When :guilabel:`Accept \\& Sign` is clicked, the various payment method " +"options become available for them to choose from (if the *online payment* " +"option applies to this quotation)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:73 +msgid "" +"Then, when the quotation is paid and confirmed, a delivery order is " +"automatically created (if the Odoo *Inventory* app is installed)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 +msgid ":doc:`get_paid_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 +msgid "Optional products" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5 +msgid "" +"The use of optional products is a marketing strategy that involves the " +"cross-selling of products along with a core product. The aim is to offer " +"useful and related products to customers, which may result in an increased " +"sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 +msgid "" +"For instance, if a customer wants to buy a car, they have the choice to " +"order massaging seats, as well, or ignore the offer and simply buy the car. " +"Presenting the choice to purchase optional products enhances the customer " +"experience." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:14 +msgid "Optional products on quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:16 +msgid "" +"With the Odoo *Sales* application, it is possible to add or modify optional " +"products directly on quotations by navigating to the :guilabel:`Optional " +"Products` tab on a quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to add optional products to your quotations on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:23 +msgid "" +"To add an optional product(s) to a quotation, click :guilabel:`Add a " +"product` in the :guilabel:`Optional Products` tab of a quotation. Doing so " +"reveals a blank field in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:179 +msgid "" +"When clicked, a drop-down menu with products from the database appear. " +"Select the desired product from the drop-down menu to add it as an optional " +"product to the quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:31 +msgid "" +"If the desired product isn't readily visible, type the name of the desired " +"product in the field, and the option appears in the drop-down menu. Then, " +"select that desired product to add it to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:36 +msgid "" +"When a product is added, the default :guilabel:`Quantity` is `1`, but that " +"can be edited at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:182 +msgid "" +"To delete any line item from the :guilabel:`Optional Products` tab, click " +"the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:42 +msgid "" +"Click the :guilabel:`Preview` button, located in the upper-left corner of " +"the quotation, to reveal a preview of the quotation customers would receive," +" via email, along with the optional products they can potentially add to " +"their order, located in the :guilabel:`Options` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "Preview your quotations on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:50 +msgid "" +"Customers are able to add different optional products to an order by " +"clicking the :guilabel:`🛒 (shopping cart)` icon, located to the right of the" +" optional product line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:53 +msgid "" +"If a customer selects optional products, these are automatically added to " +"the quotation managed by the salesperson." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:56 +msgid "" +"When the customer adds an optional product(s) to an order, the salesperson " +"is instantly notified about the change, along with any other change the " +"customer makes to an order. This allows salespeople to stay up-to-date with " +"everything related to an order in the backend of the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 +msgid "Optional products on quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 +msgid "" +"Be sure to review the :doc:`quote_template` documentation to better " +"understand how quotation templates work before reading the following " +"information." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:68 +msgid "" +"For quotation templates, just like a typical quotation form, there is also " +"an :guilabel:`Optional Products` tab, wherein related products or services " +"can be added to a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:71 +msgid "" +"To add optional products to a quotation template, navigate to " +":menuselection:`Sales app --> Configuration --> Quotation Templates`. Then, " +"either select an existing quotation template to edit, or create a new one by" +" clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:75 +msgid "" +"On the quotation template form, click the :guilabel:`Optional Products` tab." +" Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, " +"and select the desired product to add as an optional product to the " +"quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:83 +msgid "" +"The products added in the :guilabel:`Optional Products` tab are present in " +"the quotation, by default, whenever that particular quotation template is " +"used. These products can be removed, and additional products can be added, " +"before the quotation is sent to a customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:88 +msgid "" +"It's best to offer optional products that would encourage a customer to add " +"additional items to their order, or entice them to purchase a more expensive" +" version of their initially selected product." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:92 +msgid "" +"For example, if a customer purchases a wooden chair, some optional products " +"could be: a warranty on that chair and/or a wooden chair with leather seats." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:96 +msgid "" +"There is no limit to how many optional products can be added to a quotation " +"template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 +msgid "Product variants on quotations and sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 +msgid "" +"Before getting into detail about how to use product variants on quotations " +"and sales orders, it's recommended to learn about " +":doc:`../products_prices/products/variants` in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:8 +msgid "" +"Once familiarized with the basics surrounding product variants, the " +"following covers how product variants can be added to quotations and sales " +"orders using the *product configurator* or *order grid entry*." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:13 +msgid "" +"It should be noted that the setting is titled, *Variant Grid Entry* on the " +"*Sales* app settings page, and titled, *Order Grid Entry* on product forms. " +"So, be sure to keep that in mind." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:19 +msgid "" +"When working with product variants, Odoo uses the product configurator, by " +"default. To add the variant grid entry option, that feature **must** be " +"enabled in the Odoo *Sales* application. The variant grid entry option " +"provides a pop-up window on the quotation/sales order to simplify the " +"variant selection process." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:24 +msgid "" +"To enable that setting, go to :menuselection:`Sales app --> Configuration " +"--> Settings`, and scroll to the :guilabel:`Product Catalog` section. Then, " +"check the box next to the :guilabel:`Variant Grid Entry` option, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "The variant grid entry setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:33 +msgid "" +"Of course, the :guilabel:`Variants` feature **must** also be activated, in " +"order to use product variants on quotations and sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 +msgid "" +"Once the :guilabel:`Variant Grid Entry` setting is enabled, both options " +"(*Product Configurator* and *Order Grid Entry*) become available on every " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 +msgid "" +"To configure a product form to use either a product configurator or variant " +"grid entry, start by navigating to :menuselection:`Sales app --> Products " +"--> Products` to view all the products in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:46 +msgid "" +"Then, select the desired product to configure, or click :guilabel:`New`, to " +"create a new product from scratch. Once on the product form, click into the " +":guilabel:`Attributes \\& Variants` tab, where product variants can be " +"viewed, modified, and added." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:50 +msgid "" +"At the bottom of the :guilabel:`Attributes \\& Variants` tab, there is a " +":guilabel:`Sales Variant Selection` section with two options: " +":guilabel:`Product Configurator` and :guilabel:`Order Grid Entry`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:55 +msgid "" +"It should be noted that these options **only** appear if at least two values" +" of an attribute have been added to the record." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"Sales variant selection options on the attributes and variants tab on " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62 +msgid "" +"These options determine which method is used when adding product variants to" +" quotations or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:65 +msgid "" +"The :guilabel:`Product Configurator` provides a pop-up window that neatly " +"displays all the available product variants for that particular product when" +" it's added to a quotation. However, only one variant can be selected/added " +"at a time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:69 +msgid "" +"The :guilabel:`Order Grid Entry` provides the same information as the " +":guilabel:`Product Configurator` in a table layout, allowing the user to " +"select larger numbers of unique product variants, and add them to a " +"quotation/sales order, in a single view." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 +msgid "Product configurator" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:76 +msgid "" +"The product configurator feature appears as a :guilabel:`Configure` pop-up " +"window, as soon as a product with (at least two) variants is added to a " +"quotation or sales order, but **only** if the :guilabel:`Product " +"Configurator` option is selected on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"The product configurator pop-up window that appears on a quotation or sales " +"order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:85 +msgid "" +"This :guilabel:`Configure` pop-up window also appears if the " +":guilabel:`Order Grid Entry` setting is **not** activated, as it is the " +"default option Odoo uses when dealing with product variants on quotations " +"and/or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89 +msgid "" +"The :guilabel:`Product Configurator` option lets salespeople choose exactly " +"which product variant to add to the quotation or sales order using a format " +"similar to online shopping." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:93 +msgid "Order grid entry" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95 +msgid "" +"The order grid entry feature appears as a :guilabel:`Choose Product " +"Variants` pop-up window, as soon as a product with (at least two) variants " +"is added to a quotation or sales order, but **only** if the :guilabel:`Order" +" Grid Entry` option is selected on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"The choose product variants pop-up window that appears on a quotation in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103 +msgid "" +"The :guilabel:`Choose Product Variants` pop-up window features all the " +"variant options for that particular product. From this pop-up window, the " +"salesperson can designate how many of each variant they'd like to add to the" +" quotation/sales order at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:107 +msgid "" +"When all the desired quantities and variants have been selected, the " +"salesperson simply clicks :guilabel:`Confirm`, and those orders are " +"instantly added to the quotation/sales order in the :guilabel:`Order Lines` " +"tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"Populated order lines tab after order grid entry has been chosen to select " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:116 +msgid ":doc:`../products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:3 +msgid "PDF quote builder" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:5 +msgid "" +"The *PDF Quote Builder* in Odoo *Sales* provides the opportunity to send " +"customers a fully customized PDF file for quotes, showcasing the company and" +" products, with various information and design elements, instead of just " +"showing the price and total." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:9 +msgid "" +"The PDF Quote Builder groups header pages, product descriptions, the " +"price(s), and footer pages to create a detailed quote. It can also inject " +"dynamic texts in the PDF to personalize the offer for the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:13 +msgid "" +"Having a customized PDF in quotes provides a heightened conclusion to the " +"shopping experience for customers, and adds an elegant level of " +"professionalism to a company." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:17 +msgid "" +"`Odoo Quick Tips - Create a PDF quote [video] " +"`_" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:20 +msgid "" +"It is recommended to edit PDF forms with Adobe software. The form fields on " +"the header and footer PDF templates are necessary to get dynamic values with" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:26 +msgid "" +"In order to add custom PDF files for quotes, the :guilabel:`PDF Quote " +"builder` feature *must* be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:29 +msgid "" +"To do that, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`. Then, on the :guilabel:`Settings` page, scroll to the " +":guilabel:`Quotations & Orders` section, and locate the :guilabel:`PDF Quote" +" builder` feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"The PDF Quote Builder feature located on the Settings page of the Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:37 +msgid "" +"Here, custom :guilabel:`Header pages` and :guilabel:`Footer pages` can be " +"uploaded. To upload either, click the :guilabel:`Upload your file` button, " +"or the :guilabel:`✏️ (pencil)` icon to the right of the desired field, and " +"proceed to locate, select, and upload the desired PDF file." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:42 +msgid "" +"Headers and footers can also be added directly in a quotation template, so " +"it's possible to have different variations per template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:45 +msgid "" +"Clicking the :guilabel:`🗑️ (trash)` icon deletes the current PDF file and " +"replaces the blank field with an :guilabel:`Upload your file` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:48 +msgid "" +"Once the desired PDF file(s) are uploaded in the appropriate fields in the " +":guilabel:`PDF Quote builder` section of the *Sales* :guilabel:`Settings` " +"page, be sure to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:51 +msgid "The files uploaded here will be the default PDF used for all quotes." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:54 +msgid "Values set in the PDF Quote Builder settings are company-specific." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:57 +msgid "Dynamic text in PDFs" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:59 +msgid "" +"While creating custom PDFs for quotes, use *dynamic text* for Odoo to auto-" +"fill the PDF content with information related to the quote from the Odoo " +"database, like names, prices, etc." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:62 +msgid "" +"Dynamic text values are form components (text inputs) that can be added in a" +" PDF file, and Odoo automatically fills those values in with information " +"related to the quote." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:66 +msgid "Dynamic text values" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:68 +msgid "" +"Below are common dynamic text values used in custom PDFs, and what they " +"represent:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:70 +msgid ":guilabel:`name`: Sales Order Reference" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:71 +msgid ":guilabel:`partner_id__name`: Customer Name" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:72 +msgid ":guilabel:`user_id__name`: Salesperson Name" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:73 +msgid ":guilabel:`amount_untaxed`: Untaxed Amount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:74 +msgid ":guilabel:`amount_total`: Total Amount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:75 +msgid ":guilabel:`delivery_date`: Delivery Date" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:76 +msgid ":guilabel:`validity_date`: Expiration Date" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:77 +msgid ":guilabel:`client_order_ref`: Customer Reference" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:80 +msgid "" +"Double underscore notation for :guilabel:`partner_id__name` and " +":guilabel:`user_id__name` values are used in place of the typically used `.`" +" symbol because the library currently does not support the `.` symbol." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:84 +msgid "Product-specific dynamic text values are as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:86 +msgid ":guilabel:`description`: Product Description" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:87 +msgid ":guilabel:`quantity`: Quantity" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:88 +msgid ":guilabel:`uom`: Unit of Measure (UoM)" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:89 +msgid ":guilabel:`price_unit`: Price Unit" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:90 +msgid ":guilabel:`discount`: Discount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:91 +msgid ":guilabel:`product_sale_price`: Product List Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:92 +msgid ":guilabel:`taxes`: Taxes name joined by a comma (`,`)" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:93 +msgid ":guilabel:`tax_excl_price`: Tax Excluded Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:94 +msgid ":guilabel:`tax_incl_price`: Tax Included Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:97 +msgid "" +"When a PDF is built, it's best practice to use common dynamic text values " +"(:guilabel:`name` and :guilabel:`partner_id_name`). When uploaded into the " +"database, Odoo auto-populates those fields with the information from their " +"respective fields." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:101 +msgid "" +"In this case, Odoo would auto-populate the Sales Order Reference in the " +":guilabel:`name` dynamic text field, and the Customer Name in the " +":guilabel:`partner_id_name` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "PDF quote being built using common dynamic placeholders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:108 +msgid "" +"Once the PDF file(s) are complete, save them to the computer's hard drive, " +"and proceed to upload them to Odoo via :menuselection:`Sales app --> " +"Configuration --> Settings --> PDF Quote builder`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:111 +msgid "" +"Upload the created PDF in the :guilabel:`Header pages` or :guilabel:`Footer " +"pages` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:113 +msgid "Once the upload(s) are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:116 +msgid "Add PDF to product" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:118 +msgid "" +"In Odoo *Sales*, it's also possible to add a custom PDF to a product form. " +"When a PDF is added to a product, and that product is used in a quotation, " +"that PDF is also inserted in the final PDF." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:121 +msgid "" +"To add a custom PDF to a product, start by navigating to " +":menuselection:`Sales app --> Products --> Products`, and select the desired" +" product to which a custom PDF should be added." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:125 +msgid "" +"A document could also be added to a product variant, instead of a product. " +"If there are documents on a product *and* on its variant, **only** the " +"documents in the variant are shown." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:128 +msgid "" +"To add a custom document to a product variant, navigate to " +":menuselection:`Sales app --> Products --> Product Variants`. Select the " +"desired variant, click the :guilabel:`Documents` smart button, and proceed " +"to upload the custom document(s) to the specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:132 +msgid "" +"On the product page, click the :guilabel:`Documents` smart button at the top" +" of the page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "The Documents smart button on a product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:138 +msgid "" +"Doing so reveals a separate :guilabel:`Documents` page for that product, " +"wherein files related to that product can be uploaded. From this page, " +"either click :guilabel:`New` or :guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:141 +msgid "" +"Clicking :guilabel:`Upload` instantly provides the opportunity to upload the" +" desired document. Then, the document can be further configured on the " +"document card, or by clicking the three dots icon in the top right corner of" +" the document card, and then clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:145 +msgid "" +"Clicking :guilabel:`New` reveals a blank documents form, in which the " +"desired PDF can be uploaded via the :guilabel:`Upload your file` button on " +"the form, located in the :guilabel:`File Content` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"A standard document form with various fields for a specific product in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:153 +msgid "" +"Various information and configurations related to the uploaded document can " +"be modified here." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:155 +msgid "" +"The first field on the documents form is for the :guilabel:`Name` of the " +"document, and it is grayed-out (not clickable) until a document is uploaded." +" Once a PDF has been uploaded, the :guilabel:`Name` field is auto-populated " +"with the name of the PDF, and it can then be edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:159 +msgid "" +"Prior to uploading a document, there's the option to designate whether the " +"document is a :guilabel:`File` or :guilabel:`URL` from the :guilabel:`Type` " +"drop-down field menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "A standard document form with an uploaded pdf in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:167 +msgid "" +"If a PDF is uploaded, the :guilabel:`Type` field is auto-populated to " +":guilabel:`File`, and it cannot be modified." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:170 +msgid "" +"Then, in the :guilabel:`Sales` section, in the :guilabel:`Visible at` field," +" click the drop-down menu, and select either: :guilabel:`Quotation`, " +":guilabel:`Confirmed order`, or :guilabel:`Inside quote`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:174 +msgid "" +":guilabel:`Quotation`: the document is sent to (and accessible by) customers" +" at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:176 +msgid "" +":guilabel:`Confirmed order`: the document is sent to customers upon the " +"confirmation of an order. This is best for user manuals and other " +"supplemental documents." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:179 +msgid "" +":guilabel:`Inside quote`: the document is included in the PDF of the " +"quotation, between the header pages and the :guilabel:`Pricing` section of " +"the quote." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:183 +msgid "" +"When the :guilabel:`Inside quote` option for the :guilabel:`Visible at` " +"field is chosen, and the custom PDF file, `Sample Builder.pdf` is uploaded, " +"the PDF is visible on the quotation the in the *customer portal* under the " +":guilabel:`Documents` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "" +"Sample of an uploaded pdf with the inside quote option chosen in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:191 +msgid "" +"Lastly, in the :guilabel:`E-Commerce` section, decide whether or not to " +":guilabel:`Show on product page` on the front-end (in the online store)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:195 +msgid "" +"When the :guilabel:`Show on product page` option is enabled, a link to the " +"uploaded document, `Sample Builder.pdf`, appears on the product's page, " +"located on the frontend in the online store." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:198 +msgid "" +"It appears beneath a :guilabel:`Documents` heading, with a link showcasing " +"the name of the uploaded document." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "" +"Showing a link to an uploaded document on a product page using Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:206 +msgid "PDF quote" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:208 +msgid "" +"Once a quote with a pre-configured PDF has been confirmed, Odoo provides the" +" option to print the confirmed quote to check for errors, or to keep for " +"records." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:211 +msgid "" +"To print the PDF quote, navigate to the confirmed quote, and click the " +":guilabel:`⚙️ (gear)` icon to reveal a drop-down menu. From this drop-down " +"menu, select :guilabel:`Print`, then select :guilabel:`PDF Quote`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"Print pdf quote option on drop-down menu located on confirmed sales order in" +" Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:219 +msgid "" +"Doing so instantly downloads the PDF quote. When opened, the PDF quote, " +"along with the configured product PDF that was set to be visible inside the " +"quote, can be viewed and printed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:223 +msgid "" +"Download these :download:`PDF quote builder examples " +"` for added reference." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 +msgid "Quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 +msgid "" +"In Odoo *Sales*, salespeople have the ability to create reusable quotation " +"templates for common products or services that the business offers." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:8 +msgid "" +"By using these templates, quotations can be tailored and sent to customers " +"at a much faster pace, without having to create new quotations from scratch " +"every time a sales negotiation occurs." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:16 +msgid "" +"Begin by activating the setting in :menuselection:`Sales app --> " +"Configuration --> Settings`, and scroll to the :guilabel:`Quotations \\& " +"Orders` heading." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 +msgid "" +"In that section, check the box beside the :guilabel:`Quotation Templates` " +"option. Doing so reveals a new :guilabel:`Default Template` field, in which " +"a default quotation template can be chosen from a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "How to enable quotation templates on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:27 +msgid "" +"Also, upon activating the :guilabel:`Quotation Template` feature, an " +"internal :guilabel:`➡️ Quotation Templates` link appears beneath the " +":guilabel:`Default Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30 +msgid "" +"Clicking that link reveals the :guilabel:`Quotation Templates` page, from " +"which templates can be created, viewed, and edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 +msgid "" +"Before leaving the :guilabel:`Settings` page, don't forget to click the " +":guilabel:`Save` button to save all changes made during the session." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:37 +msgid "Create quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:39 +msgid "" +"Click the :guilabel:`Quotation Templates` link on the :guilabel:`Settings` " +"page, or navigate to :menuselection:`Sales app --> Configuration --> " +"Quotation Templates`. Both options reveal the :guilabel:`Quotation " +"Templates` page, where quotation templates can be created, viewed, and " +"edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Quotation templates page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:47 +msgid "" +"To create a new quotation template, click the :guilabel:`New` button, " +"located in the upper-left corner. Doing so reveals a blank quotation " +"template form that can be customized in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Create a new quotation template on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 +msgid "" +"Start by entering a name for the template in the :guilabel:`Quotation " +"Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 +msgid "" +"Then, in the :guilabel:`Quotation Validity` field, designate how many days " +"the quotation template will remain valid for, or leave the field on the " +"default `0` to keep the template valid indefinitely." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 +msgid "" +"Next, in the :guilabel:`Confirmation Mail` field, click the blank field to " +"reveal a drop-down menu. From the drop-down menu, select a pre-configured " +"email template to be sent to customers upon confirmation of an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 +msgid "" +"To create a new email template directly from the :guilabel:`Confirmation " +"Mail` field, start typing the name of the new email template in the field, " +"and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from" +" the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 +msgid "" +"Selecting :guilabel:`Create` creates the email template, which can be edited" +" later." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 +msgid "" +"Selecting :guilabel:`Create and edit...` creates the email template, and a " +":guilabel:`Create Confirmation Mail` pop-up window appears, in which the " +"email template can be customized and configured right away." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "" +"Create confirmation mail pop-up window from the quotation template form in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 +msgid "" +"When all modifications are complete, click :guilabel:`Save \\& Close` to " +"save the email template and return to the quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 +msgid "" +"If working in a multi-company environment, use the :guilabel:`Company` field" +" to designate to which company this quotation template applies." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:85 +msgid "" +"If a journal is set in the :guilabel:`Invoicing Journal` field, all sales " +"orders with this template will invoice in that specified journal. If no " +"journal is set in this field, the sales journal with the lowest sequence is " +"used." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 +msgid "" +"If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` " +"features are activated in the :guilabel:`Settings` (:menuselection:`Sales " +"app --> Configuration --> Settings`), those options are available on " +"quotation template forms." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 +msgid "" +"Check the box beside :guilabel:`Online Signature` to request an online " +"signature from the customer to confirm an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 +msgid "" +"Check the box beside :guilabel:`Online Payment` to request an online payment" +" from the customer to confirm an order. When :guilabel:`Online Payment` is " +"checked, a new percentage field appears, in which a specific percentage of " +"payment can be entered." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 +msgid "" +"Both options, :guilabel:`Online Signature` and :guilabel:`Online Payment` " +"can be enabled simultaneously, in which case the customer must provide " +"**both** a signature **and** a payment to confirm an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 +msgid "" +"In the :guilabel:`Recurring Plan` field, choose from a variety of pre-" +"configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`," +" etc.) to designate how often this quotation template should occur." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:109 +msgid "" +"The :guilabel:`Recurring Plan` field **only** applies to subscription plans." +" For more information, check out the documentation on " +":doc:`../../subscriptions/plans`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:113 +msgid "Lines tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 +msgid "" +"In the :guilabel:`Lines` tab, products can be added to the quotation " +"template by clicking :guilabel:`Add a product`, organized by clicking " +":guilabel:`Add a section` (and dragging/dropping section headers), and " +"further explained with discretionary information (such as warranty details, " +"terms, etc.) by clicking :guilabel:`Add a note`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 +msgid "" +"To add a product to a quotation template, click :guilabel:`Add a product` in" +" the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a " +"blank field in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:123 +msgid "" +"When clicked, a drop-down menu with existing products in the database " +"appear. Select the desired product from the drop-down menu to add it to the " +"quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 +msgid "" +"If the desired product isn't readily visible, type the name of the desired " +"product in the :guilabel:`Product` field, and the option appears in the " +"drop-down menu. Products can also be found by clicking :guilabel:`Search " +"More...` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132 +msgid "" +"When a product is added to a quotation template, the default " +":guilabel:`Quantity` is `1`, but that can be edited at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135 +msgid "" +"Then, drag-and-drop the product to the desired position, via the " +":guilabel:`six squares` icon, located to the left of each line item." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 +msgid "" +"To add a *section*, which serves as a header to organize the lines of a " +"sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. " +"When clicked, a blank field appears, in which the desired name of the " +"section can be typed. When the name has been entered, click away to secure " +"the section name." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143 +msgid "" +"Then, drag-and-drop the section name to the desired position, via the " +":guilabel:`six squares` icon, located to the left of each line item." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146 +msgid "" +"To add a note, which would appear as a piece of text for the customer on the" +" quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When " +"clicked, a blank field appears, in which the desired note can be typed. When" +" the note has been entered, click away to secure the note." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 +msgid "" +"Then, drag-and-drop the note to the desired position, via the :guilabel:`six" +" squares` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152 +msgid "" +"To delete any line item from the :guilabel:`Lines` tab (product, section, " +"and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right " +"side of the line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 +msgid "Optional Products tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158 +msgid "" +"The use of *optional products* is a marketing strategy that involves the " +"cross-selling of products along with a core product. The aim is to offer " +"useful and related products to customers, which may result in an increased " +"sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 +msgid "" +"Optional products appear as a section on the bottom of sales orders and " +"eCommerce pages. Customers can immediately add them to their online sales " +"orders themselves, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Optional products appearing on a typical sales order with Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:173 +msgid "" +"In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each " +"cross-selling product related to the original items in the :guilabel:`Lines`" +" tab, if applicable. The products added here ideally complement the original" +" offering as added value for the prospective buyer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177 +msgid "" +"Clicking :guilabel:`Add a line` reveals a blank field in the " +":guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 +msgid "Optional products are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:189 +msgid "Terms \\& Conditions tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:191 +msgid "" +"The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add " +"terms and conditions to the quotation template. To add terms and conditions," +" simply type (or copy/paste) the desired terms and conditions in this tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:196 +msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199 +msgid "" +"Terms and conditions are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202 +msgid "PDF Quote Builder tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:204 +msgid "" +"The :guilabel:`PDF Quote Builder` tab provides options to compose an " +"attractive quotation, with more information and visually-pleasing elements, " +"to highlight products and/or services." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207 +msgid "" +"To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, " +"click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages." +" Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:212 +msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:215 +msgid "Use quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:217 +msgid "" +"When creating a quotation (:menuselection:`Sales app --> New`), choose a " +"pre-configured template in the :guilabel:`Quotation Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Quotation templates field on a standard quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:224 +msgid "" +"To view what the customer will see, click the :guilabel:`Preview` button at " +"the top of the page to see how the quotation template appears on the front-" +"end of the website through Odoo's customer portal." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Customer preview of a quotation template in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:233 +msgid "" +"Quotation template design uses the same methodology and functionality with " +"design building blocks as a typical web page design with Odoo *Website*. Be " +"sure to check out the :doc:`../../../websites/website` documentation to " +"learn more." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237 +msgid "" +"When all blocks and customizations are complete, click the :guilabel:`Save` " +"button to put those configurations into place." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:240 +msgid "" +"There is also a blue banner at the top of the quotation template design with" +" a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo " +"returns to the quotation form in the back-end of the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:5 +msgid "Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:7 +msgid "" +"Odoo *Subscriptions* is used to run recurring businesses: :ref:`sell new " +"contracts `, :doc:`upsell customers " +"`, keep the churn under " +"control, and :doc:`generate reports " +"` on the main :abbr:`KPIs (Key " +"Performance Indicators)`: :abbr:`MRR (Monthly Recurring Revenue)`, " +":abbr:`ARR (Annual Recurring Revenue)`, retention, churn, etc." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:15 +msgid "" +"`Odoo Tutorials: Subscriptions " +"`_" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:16 +msgid ":doc:`/applications/sales/subscriptions/products`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:17 +msgid ":doc:`/applications/sales/subscriptions/ecommerce`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:18 +msgid ":doc:`/applications/sales/subscriptions/plans`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:19 +msgid ":doc:`/applications/sales/subscriptions/upselling`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:20 +msgid ":doc:`/applications/sales/subscriptions/renewals`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:21 +msgid ":doc:`/applications/sales/subscriptions/closing`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:22 +msgid ":doc:`/applications/sales/subscriptions/automatic_alerts`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:23 +msgid ":doc:`/applications/sales/subscriptions/reports`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:28 +msgid "Subscription quotations" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:31 +msgid "Sales orders with a defined recurrence become subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:33 +msgid "" +"To create a new subscription, click on :guilabel:`New` from the " +"*Subscription* or the :doc:`Sales ` app. You can " +"either:" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:36 +msgid "" +"Select a :doc:`subscription plan ` " +"to prefill the quotation instantly, or" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:38 +msgid "" +"Fill out the quotation normally, making sure to select a recurrence and an " +"end date if necessary and adding :doc:`recurrent products " +"`." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:42 +msgid "" +"You can define different invoice and delivery addresses by enabling the " +":doc:`Customer Addresses " +"` " +"feature." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:48 +msgid "Confirmation" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:50 +msgid "" +"Send the quotation to the customer for confirmation by clicking on " +":guilabel:`Send by email`, or confirm it immediately by clicking on " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:54 +msgid "" +"Click on :guilabel:`Customer Preview` to preview the customer portal where " +"the customer can view their quotation, sign and pay it, and communicate with" +" you." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:60 +msgid "Automatic payments" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:62 +msgid "" +"You can require the customer to set an automatic payment method and pre-pay " +"the subscription's first occurrence before they can confirm their quotation." +" To do so, go to the :guilabel:`Other Info` tab of the quotation and check " +"the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:67 +msgid "" +"If you leave :guilabel:`Payment` unchecked, the customer doesn't have to " +"pre-pay to start the subscription. This means that the payment is not " +"automatic and that the customer must pay each invoice manually." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:72 +msgid "" +"If the online confirmation requires a pre-payment, your customer can select " +"only the :ref:`payment providers ` " +"that have the :ref:`tokenization feature " +"`. This ensures that the customer " +"is automatically charged at each new period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:3 +msgid "Automatic alerts" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:5 +msgid "" +"Now that your subscriptions are up and running, you want to stay up-to-date " +"with your customers. Some automation would be appreciated since you would " +"not want to go through the list of all your subscribers to check how things " +"are going. This is what the *Automatic Alerts* feature is for." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:9 +msgid "" +"For example, when customers subscribe to your magazine, you would probably " +"want to send them an email to welcome them and express your gratitude. Or, " +"if the satisfaction rate of your customers drops below 50%, you would " +"probably want to schedule a call with them to understand the reasons for " +"their dissatisfaction." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:14 +msgid "" +"With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\"" +" task for one of your salespeople so that he/she can try to understand your " +"customer's dissatisfaction, and finally, why not automatically send " +"satisfaction surveys so customers can evaluate your services? All of that is" +" now possible." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:20 +msgid "Create a new automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:22 +msgid "" +"The following example shows how to create a new automatic alert to send " +"satisfaction surveys to your customers, by email, after one month of " +"subscription. To do so, go to :menuselection:`Subscriptions --> " +"Configuration --> Alerts`, and create a new alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "New automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:30 +msgid "" +"On the *Apply on* section, first give the alert a name. Then, you can choose" +" to apply this alert on a subscription template, on a specific customer, or " +"even on a specific product. If you want to add more specifications, you can " +"also specify the value of your MRR, the change rate of your MRR over a " +"certain period of time, the value of the satisfaction rate, and even the " +"stage to which you want to apply this alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:37 +msgid "" +"In this example, the alert is applied to a specific product, and the stage " +"goes from *Undefined* to *In Progress*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:40 +msgid "" +"For the *Action* section, specify the *Action* and the *Trigger on*. If the " +"*Trigger on* is set to *Modification*, the action is triggered every time " +"there is a change or anything added to the subscription, and all the " +"conditions on the *Apply on* section are met. Now, if the *Trigger on* is " +"set to *Timed condition*, it means that the action is triggered based on the" +" type of *Trigger date*. After that, you can choose your *Action*. You have " +"the choice between *Create next activity*, *Set a tag on the subscription*, " +"*Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the" +" customer* and *Send an SMS Text Message to the customer*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:50 +msgid "" +"In the example above, the *Trigger on* is set to *Timed condition*, " +"therefore, a *Trigger date* and *Delay after trigger* need to be specified. " +"And because the *Send an email to the customer* action was adopted, an " +"*Email template* can be chosen." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:54 +msgid "" +"As a result, this alert will send a rating survey after one month, to the " +"customers who have purchased that specific product. The survey will appear " +"in the chatter of your respective subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "Satisfaction survey in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:63 +msgid "Modify an existing automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:65 +msgid "" +"By default, Odoo suggests you an automatic alert called *Take action on less" +" satisfied clients*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "Modify an existing automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:71 +msgid "" +"This alert is applied to the *Rating Satisfaction* of your customers, and " +"the action is triggered on *Timed condition*. If their satisfaction rate is " +"lower than 50%, a salesperson contacts the customer. This action is " +"automatically assigned to the salesperson who manages the subscription, and " +"the due date is 5 days after the triggering of this action. This alert " +"ensures that your clients are happy and that you are taking actions if they " +"are not. It helps to keep your customer retention rates very high." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:79 +msgid "" +"By editing the alert, you can modify the *Apply on*, the *Action* and " +"*Activity* sections, and adapt them to your own needs." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:83 +#: ../../content/applications/sales/subscriptions/closing.rst:105 +#: ../../content/applications/sales/subscriptions/renewals.rst:85 +#: ../../content/applications/sales/subscriptions/reports.rst:120 +#: ../../content/applications/sales/subscriptions/upselling.rst:103 +msgid ":doc:`../subscriptions`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:84 +#: ../../content/applications/sales/subscriptions/closing.rst:106 +#: ../../content/applications/sales/subscriptions/renewals.rst:86 +#: ../../content/applications/sales/subscriptions/reports.rst:121 +#: ../../content/applications/sales/subscriptions/upselling.rst:104 +msgid ":doc:`plans`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:85 +#: ../../content/applications/sales/subscriptions/closing.rst:107 +#: ../../content/applications/sales/subscriptions/renewals.rst:87 +#: ../../content/applications/sales/subscriptions/reports.rst:122 +#: ../../content/applications/sales/subscriptions/upselling.rst:105 +msgid ":doc:`products`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:3 +msgid "Close a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:5 +msgid "" +"Losing a customer is always difficult, especially if you put a lot of effort" +" into getting them to sign up for your products/services. However, many " +"companies come up with dubious methods to reduce the probability of this " +"happening." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:14 +msgid "" +"If you adopt such methods, you are among companies that actively and " +"indirectly spread the phobia of subscriptions, who do not think about how " +"negatively dissatisfied customers could impact their business and, who " +"frustrate the customers in a way or another. However, at some point, it is " +"understandable that you do not want your customers to be involved in your " +"subscription status." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:19 +msgid "" +"If you do not adopt such methods, you are among companies that continue to " +"evolve in a long-term subscription business model, especially in an era of " +"ultra-fast communications between dissatisfied customers, and who retain " +"their customers by making it easier for them to leave if they want to. By " +"giving them the opportunity to close their own subscriptions, your customers" +" do not feel trapped because they subscribed to your products/services." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:25 +msgid "" +"In summary, the **Odoo Subscriptions** application gives you the " +"**possibility to choose what you want to apply**. Indeed, you can decide " +"whether to give your customers the option to close their subscriptions " +"whenever they want to or to restrict this possibility. It depends on you and" +" we will show you how to do that in our amazing application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:33 +msgid "" +"Go to :menuselection:`Subscriptions --> Configuration --> Subscription " +"templates`. From there, you can create a new *Subscription template* or " +"modify an existing one. When editing your template, underneath the Invoicing" +" tab, you have the possibility to activate the option *Closable by " +"customer*. Once enabled, this option gives your customers the right to close" +" their own subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "Configuration to close your subscription with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:43 +msgid "" +"Be sure to check out our documentation on how to :doc:`Use subscription " +"templates ` to fully understand the importance of this feature in a " +"basic flow using the **Odoo Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:49 +msgid "Close your first subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:52 +msgid "Administrator view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:54 +msgid "" +"Once confirmed, a quotation becomes a sales order and a new subscription is " +"automatically created. Therefore, this subscription has the status *In " +"progress*. From there, you have the possibility to close the subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"Close your subscription from an administration point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:62 +msgid "" +"By using the smart button *Close*, you have to enter a close reason. For " +"example, \"Subscription too expensive\", \"Subscription does not meet my " +"requirements\", \"Subscription reached its end date\", etc. Immediately " +"after confirming your close reason, you can observe that the status of the " +"subscription is now *Closed* and that the close reason is mentioned on the " +"subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "What happens when you close your subscription with Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:72 +msgid "Customer view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:74 +msgid "" +"As previously explained in the *Administrator view* part, from the " +"subscription form, you also have the possibility to visualize what your " +"customers see when managing their subscriptions thanks to the *Customer " +"preview* button. In this example, the customer has the choice to close " +"his/her subscription whenever he/she wants to, due to the *Close " +"Subscription* button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"Close your subscription from a customer point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:83 +msgid "" +"By using this button, the customer can specify the reason for cancelling " +"his/her subscription and he/she can even leave a message." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"What happens when customers close their subscription with Odoo " +"Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:90 +msgid "" +"By confirming the cancellation, the customer is redirected to his/her " +"portal. The administrator is informed of this modification. Indeed, the " +"status of the subscription becomes *Closed* and a note appears in the " +"chatter with the new stage, the end date, the close reason, and the closing " +"text added by the customer." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"What happens when customers close their subscription in Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:100 +msgid "" +"Before closing a subscription, check out our documentation on how to " +":doc:`Create a quotation using subscription products <../subscriptions>` to " +"understand how subscriptions are managed in the **Odoo Subscriptions** " +"application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:3 +msgid "Use subscriptions in the eCommerce shop" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:5 +msgid "" +"Subscription products can be sold in the Odoo *eCommerce* shop just like " +"regular sales products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:7 +msgid "" +"However, by default, the eCommerce product page only displays the shortest " +"recurrence period listed in the :guilabel:`Time-based pricing` tab of the " +"product form. For example, if a subscription product has *monthly* and " +"*yearly* recurrence periods configured, then only the monthly price appears " +"on the eCommerce page for that product by default." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:12 +msgid "" +"To add more recurrence periods to the eCommerce product page, create a " +"*product variant* for each recurrence period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:16 +msgid "" +":doc:`Configure subscription products " +"`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:17 +msgid "" +":doc:`Product variants " +"`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:20 +msgid "Create recurrence periods as product variants" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:22 +msgid "" +"To set up each recurrence period as a product variant, go to " +":menuselection:`Subscriptions --> Subscriptions --> Products` and select a " +"product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add " +"a line`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:26 +msgid "" +"Create an :guilabel:`Attribute` called `Billing Period` (or something " +"similar) by typing in the name and clicking :guilabel:`Create`. This " +"attribute name appears as the option heading on the product page of the " +"eCommerce shop." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:30 +msgid "" +"Next, create :guilabel:`Values` that correspond to the recurrence periods " +"that are configured in the :guilabel:`Time-based pricing` tab of the product" +" form. Type in the name of the recurrence period, then click " +":guilabel:`Create`. These value names appear as selectable options on the " +"product page of the eCommerce shop." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "" +"Recurrence periods configured as product variants in the \"Attributes & Variants\" tab of\n" +"the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:40 +msgid "" +"Click on the :guilabel:`☁️ (cloud)` icon at the top of the page to save " +"manually. After saving, a :guilabel:`Product Variants` column appears on the" +" :guilabel:`Time-based pricing` tab. Assign the product variants to their " +"corresponding recurrence periods and prices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "Product variants on the \"Time-based pricing\" tab of the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:48 +msgid "" +"The product variants are now available for selection on the eCommerce " +"product page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "" +"Recurrence periods configured as product variants on the eCommerce product " +"page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:3 +msgid "Subscription plans" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:5 +msgid "" +"*Subscription plans* are :doc:`quotation templates " +"` used to " +"preconfigure quotations with subscription products. Use subscription plans " +"to quickly create subscription orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:10 +msgid "Configure subscription plans" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:12 +msgid "" +"To configure subscription plans, go to :menuselection:`Subscriptions --> " +"Configuration --> Plans`. Then, click :guilabel:`New` to create a new plan, " +"or select an existing plan to edit it." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:15 +msgid "" +"Since the Odoo *Subscriptions* app is integrated closely with the *Sales* " +"app, subscription plans use the same form as quotation templates." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan (quotation template) configuration form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:22 +msgid "The subscription plan form contains the following options:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:24 +msgid "" +":guilabel:`Name`: Enter a name for the subscription plan at the top of the " +"page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:25 +msgid "" +":guilabel:`Quotation expires after`: Enter the number of days after which " +"the quotation expires, starting from the day the quotation is sent to the " +"customer. Leave this field at zero for the quotation to never expire." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:28 +msgid "" +":guilabel:`Online Confirmation`: Check the boxes next to " +":guilabel:`Signature` or :guilabel:`Payment` to enable the customer to " +"confirm their subscription order by signing or paying for the quotation. " +"Enable both to leave the choice to the customer. Enable neither to only " +"confirm the quotation in the backend." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:32 +msgid "" +":guilabel:`Confirmation Mail`: Select an :doc:`email template " +"` for the " +"confirmation email that is automatically sent to the customer after the " +"quotation is confirmed. Leave this field blank to send nothing." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:37 +msgid "" +"To create a new email template, enter a name for the template, then click " +":guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:39 +msgid "" +"To edit an existing email template, select one from the drop-down menu, then" +" click on the :guilabel:`Internal link` arrow at the end of the line." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:42 +msgid "" +":guilabel:`Recurrence`: Select the recurrence period used for the plan. The " +"recurrence periods available here are the same ones that are configured in " +":menuselection:`Subscriptions --> Configuration --> Recurrence Periods`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:46 +msgid "" +"Selecting a :guilabel:`Recurrence` turns the quotation template into a " +"subscription plan and enables the following additional options:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:49 +msgid "" +":guilabel:`Duration`: Choose whether the subscription plan has no end date " +"(:guilabel:`Forever`) or a :guilabel:`Fixed` duration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:52 +msgid "" +"If the duration is :guilabel:`Forever`, then the subscription plan will " +"continually renew until either the customer or the company manually ends the" +" subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:54 +msgid "" +"If the duration is :guilabel:`Fixed`, then enter an :guilabel:`End After` " +"date, which determines the amount of time after which the subscription will " +"automatically end." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:57 +msgid "" +":guilabel:`Self Closable`: Check this box to enable the customer to " +"terminate their subscription from the :doc:`customer portal " +"`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:60 +msgid "" +":guilabel:`Automatic Closing`: Enter the number of days after which *unpaid*" +" subscriptions *past* the due date are automatically closed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:62 +msgid "" +":guilabel:`Invoicing Journal`: Select the accounting journal in which " +"invoices for this subscription plan are recorded. Leave this field blank to " +"use the sales journal with the lowest sequence." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan with Recurrence selected." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:70 +msgid "" +"In the :guilabel:`Lines` tab, create the order lines for the quotation. " +"Click :guilabel:`Add a product`, select a product to include in the plan, " +"and then enter the :guilabel:`Quantity` and :guilabel:`Unit of Measure`. Add" +" as many products as desired to the order lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:74 +msgid "" +"In the :guilabel:`Optional Products` tab, enter any optional products that " +"the customer can add to their quotation before confirming the order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:77 +msgid "" +"If the subscription plan has unique :doc:`terms and conditions " +"`, add " +"them in the :guilabel:`Terms & Conditions` tab. If terms conditions are " +"specified on a plan, these will be used instead of the default terms and " +"conditions set up in the *Sales* app settings." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan Terms & Conditions tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:87 +msgid "Use subscription plans on quotations" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:89 +msgid "" +"Quotations for subscription products can be created in both the " +"*Subscriptions* app and the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:92 +msgid "" +"From the :guilabel:`Subscriptions` dashboard, click :guilabel:`New` to " +"create a new quotation. Then, select a subscription plan in the " +":guilabel:`Subscription Plan` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:95 +msgid "" +"The :guilabel:`Recurrence`, products, and other information from the plan " +"are automatically filled in. The quotation can then be modified further as " +"needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:98 +msgid "" +"From the :guilabel:`Sales` dashboard, click :guilabel:`New` to create a new " +"quotation. Then, select a subscription plan in the :guilabel:`Quotation " +"Template` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:101 +msgid "" +"All subscription orders will appear on the :guilabel:`Subscriptions` " +"dashboard regardless of whether they were created in the *Subscriptions* app" +" or the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:3 +msgid "Subscription products" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:5 +msgid "" +"By closely integrating with the Odoo *Sales* app, the *Subscriptions* app " +"enables users to sell subscription products alongside regular sales " +"products. While regular products are sold on a one-time basis, subscription " +"products are sold on a renewing basis, generating recurring revenue." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:9 +msgid "In Odoo, subscription products are also called *recurring* products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:12 +msgid "Configure recurrence periods" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:14 +msgid "" +"To get started with subscriptions, the *recurrence periods* must be properly" +" configured, as needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:16 +msgid "" +"Recurrence periods are the time periods in which subscriptions renew. They " +"designate how often the customer pays for (and receives) subscription " +"products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:19 +msgid "" +"To configure recurrence periods, go to :menuselection:`Subscriptions app -->" +" Configuration --> Recurrence periods`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "The recurrence periods page in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:26 +msgid "" +"The *Subscriptions* app comes with some basic recurrence periods already " +"configured:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:28 +msgid ":guilabel:`Monthly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:29 +msgid ":guilabel:`Quarterly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:30 +msgid ":guilabel:`Weekly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:31 +msgid ":guilabel:`2 Weeks`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:32 +msgid ":guilabel:`Yearly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:33 +msgid ":guilabel:`3 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:34 +msgid ":guilabel:`5 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:36 +msgid "New recurrence periods can be added and/or edited at any time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:38 +msgid "" +"To create a new recurrence period, click :guilabel:`New` on the " +":guilabel:`Recurrence Periods` page. Doing so reveals a blank recurrence " +"period form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "A recurrence period form in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:45 +msgid "" +"Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the " +"recurrence period, and select the :guilabel:`Unit` that defines the " +"duration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:49 +msgid "" +"The unit :guilabel:`Days` *cannot* be used as a recurrence period on " +"subscriptions. The daily recurrence is meant for rentals, and **cannot** be " +"added on recurring subscription sales orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:52 +msgid "" +"This limitation is there to avoid sales orders that would generate daily " +"invoices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:55 +msgid "Product form configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:57 +msgid "" +"To create a new subscription product, navigate to " +":menuselection:`Subscriptions app --> Products --> Products`, and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:60 +msgid "" +"Doing so reveals a blank product form, which can be configured and " +"customized in a number of ways." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:63 +msgid "" +"By default, the :guilabel:`Recurring` option is already enabled, prompting " +"Odoo to recognize it as a subscription product. Be sure to leave the " +":guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:67 +msgid "" +"The :guilabel:`Product Type` field is set to :guilabel:`Service` by default," +" as well. However, subscription products *can* be set to other types, if " +"needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "A basic subscription product form in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:75 +msgid "Time-based pricing" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:77 +msgid "" +"Once the desired fields in the :guilabel:`General Information` tab have been" +" entered, click the :guilabel:`Time-based pricing` tab on the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "" +"The time-based pricing tab on a subscription product form in Odoo " +"Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:84 +msgid "" +"From here, click :guilabel:`Add a price` to begin defining recurring prices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:86 +msgid "" +"In the :guilabel:`Period` column, select a desired recurrence period. In the" +" :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the " +":guilabel:`Price` column, enter the price for that recurrence period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:91 +msgid "" +":guilabel:`Daily` and :guilabel:`Hourly` periods **cannot** be used on " +"recurring products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:0 +msgid "The validation error pop-up window that appears in Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:98 +msgid "" +"There is *no limit* to how many lines can be added to the :guilabel:`Time-" +"based pricing` table." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:101 +msgid "" +"An existing product can be made into a subscription product, simply by " +"marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based " +"pricing` on the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:104 +msgid "" +"A subscription product can still be sold as a regular product, by adding it " +"to a quotation and *not* selecting a :guilabel:`Recurrence` on the " +"quotation." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:110 +msgid "" +":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with" +" subscription products to give special pricing to customers included in " +"pricelists." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:113 +msgid "" +"This can be configured either in the :guilabel:`Time-based pricing` tab of " +"the product form, or on the pricelist form in the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:116 +msgid "" +"To create recurring price rules for specific pricelists in the " +":guilabel:`Time-based pricing` tab of the product form, select a pricelist " +"in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "Pricelists in the \"Time-based pricing\" tab of the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:123 +msgid "" +"When pricelists are added to the :guilabel:`Time-based pricing` tab, the " +"pricelist form in the *Sales* app is automatically updated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:126 +msgid "" +"Time-based pricing rules can also be configured directly on the pricelist " +"form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:128 +msgid "" +"To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, " +"and select a pricelist (or click :guilabel:`New` to create a new pricelist)." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:132 +msgid "" +"Pricelists are also accessible through the Odoo *Subscriptions* app by " +"following the same menu steps." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:135 +msgid "" +"Then, on the pricelist form, under the :guilabel:`Time-based rules` tab, " +"click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "The time-based rules tab on a pricelist form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:142 +msgid "" +"Then, select a subscription product in the :guilabel:`Products` column, and " +"select a recurrence period in the :guilabel:`Period` column. Lastly, enter a" +" :guilabel:`Price` for that particular product and period. Add as many lines" +" as needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:146 +msgid "" +"When :guilabel:`Time-based rules` are added to the pricelist form, the " +":guilabel:`Time-based pricing` tab of the product form is automatically " +"updated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:150 +msgid ":doc:`ecommerce`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:3 +msgid "Renew subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:5 +msgid "" +"The foundation of any subscription business model is recurring payments. " +"That's when customers reliably pay a regular amount at specific intervals, " +"in exchange for access to a subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:9 +msgid "" +"The renewal of a subscription is the process followed by customers when they" +" willingly choose to continue their participation (and payment) for a " +"subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:12 +msgid "" +"Subscribers experience the renewal process at different intervals -- weekly," +" monthly, annually, etc. -- depending on the duration of the agreed-upon " +"contract." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:15 +msgid "" +"Most companies that offer subscriptions prefer to automate the renewals " +"process for customers, but, in some cases, manual subscription renewals are " +"still used." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:18 +msgid "" +"With the Odoo *Subscriptions* application, a company can manage all of their" +" subscriptions in one place. Renewals can be processed automatically or " +"manually, include additional products or upsells per renewal order, and be " +"filtered in batch views to quickly locate customers who need to renew their " +"subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:24 +msgid "Subscription renewals" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:26 +msgid "" +"In order to renew a subscription, a quotation with a subscription product " +"**must** be confirmed, with a configured :guilabel:`Recurring Plan` " +"selected, which turns it into a sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:30 +msgid "Only a singular product is required." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:31 +msgid "" +"A subscription service is still a product (albeit a digital, recurring one)" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:33 +msgid "" +"Then, that sales order needs to be confirmed, and payment from the customer " +"for the initial subscription has to be invoiced and registered." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:36 +msgid "" +"When those steps are complete, an :guilabel:`In Progress` tag is applied to " +"the sales order form, and a series of buttons appear at the top of the sales" +" order -- including a button titled, :guilabel:`Renew`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Renew button on subscription sales order with Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:44 +msgid "" +"When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new " +"renewal quotation, complete with a :guilabel:`Renewal Quotation` tag." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Renewal quotation in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:51 +msgid "" +"From here, a standard sales flow can occur in order to confirm the " +"quotation. This typically begins by clicking :guilabel:`Send by Email`. This" +" sends a copy of the quotation to the customer, by email, for them to " +"confirm, and eventually, pay for." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:56 +msgid "" +"In the *Chatter* of the :guilabel:`Renewal Quotation`, it is mentioned that " +"this subscription is the renewal of the subscription from the original sales" +" order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:59 +msgid "" +"Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales " +"order, and a :guilabel:`Sales History` smart button appears at the top of " +"the page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Sales History smart button in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:66 +msgid "" +"When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a " +"separate page, showcasing the different sales orders attached to this " +"subscription, along with their individual :guilabel:`Subscription Status`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:74 +msgid "" +"Additionally, once the :guilabel:`Renewal Quotation` is confirmed, an " +":guilabel:`MRR` smart button also appears at the top of the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "MRR smart button in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:81 +msgid "" +"When clicked, Odoo reveals an :guilabel:`MRR Analysis` page, detailing the " +"monthly recurring revenue related to this specific subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:3 +msgid "Reports" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:5 +msgid "" +"As we know, understanding how our business is going, and where it is going, " +"is key to success. And particularly so when we offer subscription services " +"or products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:8 +msgid "" +"Before getting to the heart of the matter, it is very important to recall " +"certain essential concepts to the proper understanding of the following " +"reports:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:11 +msgid "" +"**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important " +"metric for subscription businesses. It shows the monthly revenue earned with" +" subscription-based products or services. It is a consistent number used to " +"track all recurring revenue over time, in monthly increments." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:15 +msgid "" +"**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based " +"on the current MRR, to estimate the coming year's performance. However, this" +" estimation does not take variations and growth into account." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Difference between MRR and ARR in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:23 +msgid "" +"**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything" +" else than subscription-based products or services. This includes gains of a" +" rare or unique nature that are unlikely to occur in the ordinary course of " +"businesses." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:27 +msgid "" +"**Customer Retention**: Practices to engage existing customers to continue " +"buying products or services from your business. Customer retention can be a " +"challenge, because you must prove you are worthy of your customers' trust." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:31 +msgid "" +"**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the " +"churn rate can be defined, in this case, as the percentage of subscribers " +"who discontinued their subscriptions within a given time period. We can " +"distinguish two types of Churn:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:35 +msgid "**Logo Churn**: It corresponds to the subscription cancellation rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:37 +msgid "" +"**Revenue Churn**: It corresponds to the monthly recurring revenue loss " +"rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:40 +msgid "Let's imagine a 2$ increase in a subscription service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:42 +msgid "" +"We lost 3 customers out of the initial 20, which generates a **Logo Churn** " +"of 15%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "" +"Therefore, the 56$ of MRR difference out of the initial 600$ causes a " +"**Revenue Churn**" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "of 9,33%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "Difference between logo churn and revenue churn in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:50 +msgid "" +"Reminder: even though they seem to evolve in the same direction most of the " +"time, it might not be the case all the time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:53 +msgid "" +"**Customer Lifetime Value (CLV)**: Indicates how much revenue can be " +"expected for a customer during his/her entire contract. This approach " +"emphasizes the importance of customer retention, shifting our focus from a " +"quarterly or yearly approach to a long-term one." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:57 +msgid "" +"Check out the different kinds of reports you can access from the **Odoo " +"Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:61 +msgid "Subscriptions analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:63 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From " +"there, you can change the *Measures*. By default, Odoo uses the *Monthly " +"Recurring Revenue*. In addition to that, you can choose *Quantity*, " +"*Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example," +" *Quantity* is added. This way, you can review both of these measures at the" +" same time. You can even *Group By Start Date* and, more precisely, by " +"*Week*, to get a clear view of your report." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Subscriptions analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:74 +msgid "Retention analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:76 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The " +"default measure applied is *Count*, but you can change to the appropriate " +"one for you. For the example below, *Monthly Recurring Revenue* was chosen, " +"and the *Month* periodicity remains intact. By using these criteria, you can" +" see the progression of the retention from its start." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Retention analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:86 +msgid "Revenue KPIs report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:88 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From " +"there, you can check different KPIs: *Monthly Recurring Revenue*, *Net " +"Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-" +"Rate*, *Lifetime Value*, and more. You can also filter this information on " +"subscriptions, companies, and sales teams. This is useful if you are looking" +" for specific information." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Revenue KPIs report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:98 +msgid "" +"The example below shows the *Monthly Recurring Revenue* detailed report. At " +"the moment, there is no data, which is the typical scenario for a new " +"business. But, as your company grows over the months, these graphs get " +"populated with more and more data. Once again, you can filter these specific" +" KPIs on subscriptions, companies, and sales teams." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Detailed MRR report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:108 +msgid "Salesperson dashboard report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:110 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Salesperson " +"Dashboard`. This page gives you a summary of your *Monthly Recurring " +"Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-" +"Recurring Invoices* for each of your salespeople. You can choose the period " +"you want to apply and the salesperson you want to analyze." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Salesperson dashboard report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:3 +#: ../../content/applications/sales/subscriptions/upselling.rst:44 +msgid "Upsell subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:5 +msgid "" +"Subscriptions are recurrent, and go on indefinitely. As time passes, " +"customers may want to modify them. With that in mind, it's imperative to " +"have the ability to adapt prices, or change quantities, to accommodate any " +"need. That's where the opportunity to upsell a subscription can come into " +"play." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:9 +msgid "Upselling may prove beneficial to the following customer types:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*Loyal Customers*" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "" +"These are customers who already trust the company/brand, and because they " +"have established a pattern of paying for products/services, there's more " +"confidence behind the attempt to sell them a more expensive product/service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*New Customers*" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "" +"For brand new customers unfamiliar with the company/brand, a new, attractive" +" tactic must be employed to entice them to purchase a more expensive " +"product/service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:19 +msgid "" +"In these instances, discounts can be useful. Typically, subscriptions end " +"after a certain period of time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:22 +msgid "" +"So, if these more expensive products/services are offered to new customers " +"at a discount, it can result in a sale, while establishing a strong sense of" +" trust between the customer and the company/brand. In turn, this can " +"increase customer retention, as they'll grow more comfortable and " +"trustworthy over time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:28 +msgid "Discount configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:30 +msgid "" +"In order to have the ability to upsell a subscription to a new customer, " +"with the aid of a discount, the *Discounts* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:33 +msgid "" +"To activate the *Discounts* feature, navigate to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Pricing` section, " +"and tick the checkbox beside :guilabel:`Discounts`. Then, click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "Activation of the discount option in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:41 +msgid "" +"With that feature activated, the ability to grant discounts on sales order " +"lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:46 +msgid "" +"Before upselling a subscription, check out our documentation on how to " +":doc:`Create a quotation <../subscriptions>` using subscription products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:49 +msgid "" +"When a quotation with a subscription is confirmed, it officially becomes a " +"sales order, and a new subscription is created in the Odoo *Subscriptions* " +"application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:53 +msgid "" +"The subscription sales order **must** be invoiced *before* an upsell can " +"occur." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:55 +msgid "" +"When the subscription sales order is opened, either in the *Sales* or " +"*Subscriptions* application, the ability to upsell that subscription is " +"available, via the :guilabel:`Upsell` button at the top of the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "Upsell button for subscription sales orders with Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:63 +msgid "" +"When the :guilabel:`Upsell` button is clicked, a new quotation form appears," +" with an :guilabel:`Upsell` status banner in the upper-right corner. The " +"initial subscription product is already in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:67 +msgid "" +"There is also a warning reminding the user that the recurring products are " +"discounted, according to the prorated period of time, located beneath the " +"initial subscription product in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:71 +msgid "" +"From this new upsell quotation form, add new subscription products in the " +":guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and " +"selecting the desired subscription product." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "" +"Adding products to your subscription via the upsell option in Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:78 +msgid "" +"Once the desired upsell subscription product(s) have been added, it can be " +"sent to the customer for approval by clicking the :guilabel:`Send by Email` " +"button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:82 +msgid "" +"When the quotation is confirmed by the customer, the upsell products are " +"added to the initial subscription. Quotation prices are then prorated to the" +" remaining time of the current invoicing period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:87 +msgid "" +"Before sending the new quotation to the customer, the unit price, taxes, and" +" even discount can be applied." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:90 +msgid "" +"Once the customer approves, click the :guilabel:`Confirm` button on the " +"quotation, making it a sales order. When that's clicked, a :guilabel:`Sales " +"History` smart button appears, displaying how many sales orders are attached" +" to this initial subscription order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:94 +msgid "" +"When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a " +"separate page containing a list of the related sales orders, clearly " +"showcasing their individual :guilabel:`Subscription Status`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "" +"The related sales order viewable from the Sales History smart button in Odoo" +" Subscriptions." +msgstr "" diff --git a/locale/hi/LC_MESSAGES/services.po b/locale/hi/LC_MESSAGES/services.po new file mode 100644 index 000000000..f93bf36f8 --- /dev/null +++ b/locale/hi/LC_MESSAGES/services.po @@ -0,0 +1,4069 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/services.rst:5 +msgid "Services" +msgstr "" + +#: ../../content/applications/services/field_service.rst:8 +msgid "Field Service" +msgstr "" + +#: ../../content/applications/services/field_service.rst:11 +msgid "" +"`Odoo Tutorials: Field Service `_" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:3 +msgid "User default warehouse" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:5 +msgid "" +"Setting up a **default warehouse** can be useful for field technicians who " +"keep a supply in their van or those who always resupply from the same " +"warehouse. It also allows field workers to switch between warehouses from " +"their profiles." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:9 +msgid "" +"Products in sales orders created during field interventions are always " +"pulled from the default warehouse, keeping the inventory accurate." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:13 +msgid ":doc:`../../inventory_and_mrp/inventory`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:16 +#: ../../content/applications/services/project/project_management.rst:17 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:18 +msgid "" +"To set up a user default warehouse, the :doc:`storage locations " +"`" +" feature needs to be activated in the **Inventory** app. It is also " +"necessary to have more than one warehouse in your database." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:23 +msgid "" +"You can either set it up :ref:`for your profile `, or :ref:`for all users `." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:27 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:32 +msgid "For your profile" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:34 +msgid "" +"To set up a default warehouse for yourself, click your **profile icon** in " +"the upper right corner of the screen, then, go to :menuselection:`My Profile" +" --> Preferences --> Default Warehouse`. Select the default warehouse from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:41 +msgid "For all users" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:43 +msgid "" +"To set up a default warehouse for a specific user, go to " +":menuselection:`Settings --> Users --> Manage users`, select a user, then go" +" to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, " +"and select the default warehouse from the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst-1 +msgid "Selection of a default warehouse on a user profile." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:51 +msgid "Use in field service tasks" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:53 +msgid "" +"Once a default warehouse has been configured for a user, the materials used " +"for a sales order related to a Field Service task are pulled from that " +"specific warehouse. Open the related sales order, go to the :guilabel:`Other" +" Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse " +"is applied correctly." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:58 +msgid "" +"Once the Field Service task is marked as done, the stock of the default " +"warehouse is automatically updated." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:3 +msgid "Onsite interventions planning" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:6 +msgid "From a sales order" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:8 +msgid "" +"Allowing your sales team to open onsite interventions creates a seamless " +"experience for your customers. They can receive a quotation they first have " +"to approve before the work even starts." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:11 +msgid "" +"Go to :menuselection:`Field Service --> Configuration --> Products` and " +"create or edit a product." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:13 +msgid "" +"Under the :guilabel:`General Information` tab, select :guilabel:`Service` as" +" :guilabel:`Product Type`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:15 +msgid "" +"Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as " +":guilabel:`Service Invoicing Policy`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:17 +msgid "" +"Select :guilabel:`Create a task in an existing project` as " +":guilabel:`Service Tracking`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:18 +msgid "Select your :guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:19 +msgid "If you use them, select your :guilabel:`Worksheet Template`, and save." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "" +"Product configuration to create tasks from sales orders in Odoo Field " +"Service" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:25 +msgid "" +"From the :doc:`Sales <../../sales/sales>` app, create a quotation with the " +"product and confirm it. A task is automatically set up under your Field " +"Service project. It is directly accessible from the sales order." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Field Service task on a sales order in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:34 +msgid "From helpdesk tickets" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:36 +msgid "" +"The integration with the :doc:`Helpdesk <../helpdesk>` app lets your " +"helpdesk team manage intervention requests directly. Planning field service " +"tasks from tickets speeds up your processes." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:40 +msgid "Configure the helpdesk team" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:42 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select" +" a team and enable :guilabel:`Onsite Interventions`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Onsite interventions settings in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:49 +msgid "" +"The helpdesk tickets of the team now display the :guilabel:`Plan " +"Intervention` button. Click on it to create a new task under your field " +"service project." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:8 +msgid "Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:11 +msgid "`Odoo Tutorials: Helpdesk `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:3 +msgid "After-Sales services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:5 +msgid "" +"*After-Sales* services can be configured in the *Helpdesk* application for " +"individual *teams*. Once enabled, users can issue refunds, process returns, " +"generate coupons, and/or schedule repair and field service interventions " +"directly from a ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:10 +msgid "Set up the after-sales services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:12 +msgid "" +"Start by enabling the after-sales services on specific *Helpdesk* team(s), " +"by going to :menuselection:`Helpdesk --> Configuration --> Teams` and " +"selecting which teams(s) these services should be active on. Then, scroll to" +" the :guilabel:`After-Sales` section on the team's settings page, and choose" +" which of the following options to enable:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:17 +msgid "" +":guilabel:`Refunds`: issues credit notes to refund a customer, or adjust the" +" remaining amount due" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:18 +msgid "" +":guilabel:`Coupons`: offers discounts and free products through an existing " +"coupon program" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:19 +msgid "" +":guilabel:`Returns`: initiates a product return from a customer through a " +"reverse transfer" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20 +msgid "" +":guilabel:`Repairs`: creates repair orders for broken or faulty products" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:21 +msgid "" +":guilabel:`Field Service`: plans onsite intervention through the *Field " +"Service* application" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:26 +msgid "" +"The services that are enabled can vary based on the type of support a team " +"provides." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:29 +msgid "" +"As all of the after-sales services in Odoo require integration with other " +"applications, enabling any of them may result in the installation of " +"additional modules or applications. *Installing a new application on a One-" +"App-Free database will trigger a 15-day trial. At the end of the trial, if a" +" paid subscription has not been added to the database, it will no longer be " +"accessible.*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:35 +msgid "Issue a refund with a credit note" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:37 +msgid "" +"A *credit note* is a document issued to a customer informing them that they " +"have been credited a certain amount of money. They can be used to provide a " +"full refund to a customer, or to adjust any remaining amount due. While they" +" are usually created through the *Accounting* or *Invoicing* applications, " +"they can be created through a *Helpdesk* ticket, as well." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:43 +msgid "Invoices must be posted before a credit note can be generated." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:45 +msgid "" +"To create a credit note, navigate to a ticket on the " +":menuselection:`Helpdesk` application, and click the :guilabel:`Refund` " +"button in the upper-left corner of the ticket dashboard. Then, select the " +"corresponding invoice from the :guilabel:`Invoices to Refund` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a refund creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:53 +msgid "Choose a :guilabel:`Credit Method` from one of the following options:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:55 +msgid "" +":guilabel:`Partial Refund`: the credit note is created in draft and can be " +"edited before being issued" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:57 +msgid "" +":guilabel:`Full Refund`: the credit note is auto-validated and reconciled " +"with the invoice. *This is the option to choose if a validated invoice needs" +" to be canceled*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:59 +msgid "" +":guilabel:`Full refund and new draft invoice`: the credit note is auto-" +"validated and reconciled with the invoice. The original invoice is " +"duplicated as a new draft. *This is the option to choose if a validated " +"invoice needs to be modified*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:64 +msgid "" +"The :guilabel:`Credit Method` options will **not** be available for invoices" +" that have already been paid." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:67 +msgid "" +"Make any necessary changes to the details of the credit note and click " +":guilabel:`Reverse.` Then click :guilabel:`Confirm` to post the credit note." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:70 +msgid "" +"Once the credit note has been posted, a :guilabel:`Credit Notes` smart " +"button will be added to the *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of smart buttons on a ticket focusing on the credit note button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:78 +msgid ":doc:`/applications/finance/accounting/customer_invoices/credit_notes`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:81 +msgid "Generate coupons from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:83 +msgid "" +"Coupons can be used to alter the price of products or orders. The usage " +"constraints of a coupon are defined by conditional rules. *Coupon Programs* " +"are configured in the *Sales* or *Website* applications." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:88 +msgid "" +"The *eCommerce* module must be installed in order to create coupon codes " +"from the *Website*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:90 +msgid "" +"To generate a coupon, open a *Helpdesk* ticket and click on the " +":guilabel:`Coupon` button in the upper left corner. Select an option from " +"the :guilabel:`Coupon Program` drop-down menu, then click " +":guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a coupon generation window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:98 +msgid "" +"The :guilabel:`Coupon Code` can be copied directly from the pop-up window " +"(by clicking the :guilabel:`Copy` button), or sent in an email by clicking " +":guilabel:`Send`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:102 +msgid "" +"When emailing a coupon code, all the followers of the ticket will be added " +"as recipients to the email. Additional recipients can be added to the email " +"as well, in the :guilabel:`Recipients` field of the :guilabel:`Compose " +"Email` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:0 +msgid "View of an email draft window with coupon code." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:110 +msgid "" +"Once a :guilabel:`Coupon Code` has been generated, a :guilabel:`Coupons` " +"smart button will be added to the top of the ticket; click the smart button " +"to view the coupon code, expiration date, and additional information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of the smart buttons on a ticket focusing on the coupon button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:119 +msgid "" +"`Coupons `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:122 +msgid "Facilitate a product return with a reverse transfer" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:124 +msgid "" +"Returns are completed through *reverse transfers*, which generate new " +"warehouse operations for the returning products. Click the " +":guilabel:`Return` button in the top-left corner of a ticket to open the " +":guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a Helpdesk ticket with the return button highlighted." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:133 +msgid "" +"The :guilabel:`Return` button only appears on a ticket if the customer has a" +" recorded delivery in the database." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:136 +msgid "" +"By default, the quantity will match the validated quantity from the delivery" +" order. Update the :guilabel:`Quantity` field if necessary." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a reverse transfer creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:143 +msgid "" +"Click :guilabel:`Return` to confirm the return. This generates a new " +"warehouse operation for the incoming returned product(s). A " +":guilabel:`Return` smart button will then be added to the top of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of the return smart button on a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:152 +msgid ":doc:`/applications/sales/sales/products_prices/returns`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:155 +msgid "Send products for repair from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:157 +msgid "" +"If the ticket is related to an issue with a faulty or broken product, a " +"repair order can be created from the *Helpdesk* ticket, and managed through " +"the *Repairs* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:160 +msgid "" +"To create a new repair order, open a :menuselection:`Helpdesk` ticket and " +"click on the :guilabel:`Repair` button in the upper left corner." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:163 +msgid "" +"Clicking the :guilabel:`Repair` button opens a blank :guilabel:`Repair " +"Reference` form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a repair reference page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:170 +msgid "" +"If a product was specified in the :guilabel:`Product` field on the ticket, " +"it will be added to the :guilabel:`Product to Repair` field automatically. " +"If not, click into the field to select a product from the drop down." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:174 +msgid "" +"Fill out the :guilabel:`Repair Description` field with a brief explanation " +"of the issue. Click the :guilabel:`Sale Order` field and then select the " +"originating :abbr:`SO (Sales Order)` from which the product is being " +"repaired from. If a return has been initiated for the product, select the " +"reference number from the drop-down in the :guilabel:`Return` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:179 +msgid "" +"Choose an :guilabel:`Invoice Method` from the drop-down. Select " +":guilabel:`Before Repair` or :guilabel:`After Repair` to generate an invoice" +" before or after the work is completed. Selecting :guilabel:`No Invoice` " +"means that an invoice cannot be generated for this service." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:183 +msgid "" +"If parts are required for the repair, they can be added in the " +":guilabel:`Parts` tab. Services can be added as product lines on the " +":guilabel:`Operations` tab. Additional information for the internal repair " +"team can be added to the :guilabel:`Repair Notes` tab. Information for the " +"customer can be added to the :guilabel:`Quotation Notes` tab, and will be " +"automatically added to the PDF of the quotations generated from this " +":guilabel:`Repair Reference`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:189 +msgid "" +"A :guilabel:`Repairs` smart button will be added to the ticket, linking to " +"the repair order." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of smart buttons focusing on repair button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:196 +msgid "" +"Once a user creates a repair order from a *Helpdesk* ticket, they will be " +"able to access it through the ticket's :guilabel:`Repair` smart button, or " +"from a link in the :guilabel:`Chatter`, even if they do not have access " +"rights to the *Repair* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:201 +msgid "Create a field service task from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:203 +msgid "" +"On-site interventions can be planned from a ticket and managed through the " +"*Field Service* application. Customers with :doc:`portal access " +"` will be able to track the progress of " +"a :guilabel:`Field Service` task just as they would a *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:207 +msgid "" +"To create a new task, navigate to a :menuselection:`Helpdesk` ticket. Click " +":guilabel:`Create Task` to open the :guilabel:`Create a Field Service task` " +"pop-up. Confirm or update the task :guilabel:`Title`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:212 +msgid "" +"The :guilabel:`Project` field on the :guilabel:`Create a Field Service task`" +" pop-up will default to the same *Field Service* project that was identified" +" on the team's settings page. To change the project for this specific task, " +"select one from the :guilabel:`Project` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:216 +msgid "" +"To change the default *Field Service* project for the team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` to select a " +":guilabel:`Team`. Scroll to the :guilabel:`After-Sales` section and choose " +"new project under :guilabel:`Field Service`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:220 +msgid "Click :guilabel:`Create Task` or :guilabel:`Create & View Task`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a Field Service task creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:226 +msgid "" +"After the task is created, a :guilabel:`Tasks` smart button will be added to" +" the ticket, linking the :guilabel:`Field Service` task to the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of ticket smart buttons focused on task." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:234 +msgid "" +"`Field Service `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3 +msgid "Closing tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5 +msgid "" +"Once work has been completed on a *Helpdesk* ticket in Odoo, there are " +"several ways it can be closed. Manually closing solved tickets keeps the " +"pipeline up to date, while automatically closing inactive tickets prevents " +"unnecessary blocking issues. Allowing customers to close their own tickets " +"minimizes confusion around whether an issue is considered solved or not. " +"This results in increased operational capacity for support teams, and higher" +" customer satisfaction." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12 +msgid "Manually close solved tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14 +msgid "" +"As work on a ticket progresses, it is moved along to the next stage in the " +"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage." +" This marks the ticket as *closed*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17 +msgid "" +"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and " +"click on a team to open the pipeline. Hover over a stage's heading, and then" +" click the gear icon that appears in the top-right corner of that stage's " +"kanban column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "" +"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage" +" option." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26 +msgid "" +"Clicking the gear icon also displays the option to :guilabel:`Fold` the " +"stage. This setting folds the stage *temporarily* to simplify the kanban " +"view. This does *not* close the tickets in this stage. It also does not " +"permanently fold the stage. If a stage needs to be folded so the tickets can" +" be marked as closed, continue following the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31 +msgid "" +"From the menu that appears, select :guilabel:`Edit Stage`. This will open " +"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` " +"towards the top of the window, and then :guilabel:`Save & Close` to confirm " +"the changes. Now, tickets that reach this stage will be considered as " +"*closed*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0 +msgid "Stage settings page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41 +msgid "Automatically close inactive tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43 +msgid "" +"Tickets that are inactive for a set period of time can be automatically " +"closed. At that point, they will be moved to a folded stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46 +msgid "" +"Go to the team's settings page by going to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable" +" :guilabel:`Automatic Closing`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49 +msgid "" +"If one of the team's stages is set to be folded in the kanban view, it will " +"be the default selection in the :guilabel:`Move to Stage` field. If the team" +" has more than one folded stage, the stage that occurs first in the pipeline" +" will be the default. If no stage is folded, the default selection will be " +"the last stage in the pipeline." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54 +msgid "" +"The :guilabel:`After days of inactivity` field defaults to `7`, but can be " +"adjusted if necessary." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57 +msgid "" +"The :guilabel:`After days of inactivity` field does **not** take the working" +" calendar into account when tracking the amount of time a ticket has been " +"inactive." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60 +msgid "" +"If only certain stages should be used to track days of inactivity, they can " +"be added to the :guilabel:`In Stages` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64 +msgid "A team's pipeline is created with the following stages:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66 +msgid "`New`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67 +msgid "`In Progress`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68 +msgid "`Customer Feedback`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69 +msgid "`Closed`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71 +msgid "" +"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once " +"an issue is solved, customers may not respond immediately. At that point, " +"the tickets can be closed automatically. However, tickets in the " +":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due " +"to assignment or workload issues. Closing these tickets automatically would " +"result in issues going unsolved." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77 +msgid "" +"Therefore, the :guilabel:`Automatic Closing` settings would be configured as" +" below\\:\\" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79 +msgid ":guilabel:`Automatic Closing`: *checked*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80 +msgid ":guilabel:`Move to Stage`: `Solved`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81 +msgid ":guilabel:`After``7`:guilabel:`days of inactivity`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82 +msgid ":guilabel:`In Stages`: `Customer Feedback`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0 +msgid "Example of Automatic Closing settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89 +msgid "Allow customers to close their own tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91 +msgid "" +"Enabling the :guilabel:`Closure by Customers` setting allows customers to " +"close their own ticket(s) when they determine that their issue has been " +"resolved." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94 +msgid "" +"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`" +" and select a team. On the team's settings page, scroll to the " +":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by" +" Customers`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Customer closing setting in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102 +msgid "" +"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` " +"button will be available for customers when they view their ticket through " +"the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Customer view of ticket closing in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110 +msgid "" +"Customers are able to view their tickets by clicking the :guilabel:`View the" +" ticket` link they receive by email. The link is included in the " +":guilabel:`Request Acknowledgment` template, which is added to the first " +"stage of a team by default. This link does not require a customer to have " +"access to the portal to view or respond to their ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115 +msgid "" +"Customers with access to the portal will be able to view their tickets under" +" :menuselection:`My Account --> Tickets`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3 +msgid "Track and bill time" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:5 +msgid "" +"Odoo *Helpdesk* provides teams with the ability to track the amount of hours" +" spent working on a ticket, and to bill a customer for that time. Through " +"integrations with the *Sales*, *Timesheets* and *Accounting* applications, " +"customers can be charged once the work is completed, or before it has even " +"begun." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:11 +msgid "" +"Since the *Track & Bill Time* features require integration with other " +"applications, enabling them may result in the installation of additional " +"modules (or applications)." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:14 +msgid "" +"Installing a new application on a *One-App-Free* database triggers a 15-day " +"trial. At the end of the trial, if a paid subscription has not been added to" +" the database, it will no longer be active or accessible." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:19 +msgid "Configure track and bill time features" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:21 +msgid "" +"Before a customer can be invoiced for support services, the *Track & Bill " +"Time* features must first be enabled. These features must be enabled on each" +" *Helpdesk* team where they will be utilized." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:25 +msgid "Enable track and bill time on a helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:27 +msgid "" +"To view and enable the :guilabel:`Track & Bill Time` features on a " +"*Helpdesk* team, first navigate to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. Then select a team from the list or :doc:`create a" +" new one `. This " +"will reveal a team's settings page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:32 +msgid "" +"On the team's settings page, scroll to the :guilabel:`Track & Bill Time` " +"section. Check the boxes labeled :guilabel:`Timesheets` and :guilabel:`Time " +"Billing`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:35 +msgid "" +"Once the :guilabel:`Timesheets` box is checked, a new field appears, labeled" +" :guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:37 +msgid "" +"The project selected in this field is where all the timesheets for this " +"team's tickets will be recorded. Click into the drop-down menu to select a " +":guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:40 +msgid "" +"To create a new project where the timesheets will be recorded, click into " +"the drop-down menu, type a name for the project, and then click " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a helpdesk team settings page emphasizing the track and bill time " +"settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:50 +msgid "Configure service products" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:52 +msgid "" +"When the :guilabel:`Time Billing` feature is enabled, a new product is " +"created in the *Sales* app called :guilabel:`Service on Timesheets`. This " +"product can be found under :menuselection:`Sales --> Products --> Products`." +" Search for `Service on Timesheets` in the :guilabel:`Search...` bar. This " +"is the product that will be used when invoicing for *post-paid support " +"services* after they have been completed." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:58 +msgid "" +"Select :guilabel:`Service on Timesheets` from the product page. This reveals" +" the product detail form. The product is configured with the " +":guilabel:`Product Type` set to :guilabel:`Service` and the " +":guilabel:`Invoicing Policy` set to :guilabel:`Based on Timesheets`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a service product with the invoicing policy set to 'Based on " +"timesheets'." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:66 +msgid "" +"In order to invoice for support services before the work has been completed " +"(also known as *prepaid support services*), a separate product with a " +"different invoicing policy must be created." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:69 +msgid "" +"To create a new service product, go to :menuselection:`Sales --> Products " +"--> Products` and click :guilabel:`New`. This will reveal a blank product " +"detail form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:72 +msgid "" +"On the new product form, add a :guilabel:`Product Name`, and set the " +":guilabel:`Product Type` to :guilabel:`Service`. Then, set the " +":guilabel:`Invoicing Policy` to :guilabel:`Prepaid/Fixed Price`. This means " +"an invoice can be generated and payment can be received for this product " +"before any timesheets entries have been recorded for these services." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a service product with the invoicing policy set to 'prepaid/fixed'." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:81 +msgid "" +"Finally, set the :guilabel:`Sales Price`, and confirm that the " +":guilabel:`Unit of Measure` is set to :guilabel:`Hours`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:85 +msgid "Invoice prepaid support services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:87 +msgid "" +"When support services are billed on a fixed price, an invoice can be created" +" before any work is completed on the issue. In this case, a service product " +"with the invoicing policy set to :guilabel:`Prepaid/Fixed Price` would be " +"used, just like :ref:`the section above `." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:93 +msgid "Create a sales order with prepaid product" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:95 +msgid "" +"To invoice a customer for prepaid support services, first create a sales " +"order (SO) with the support services product. To do this, go to " +":menuselection:`Sales --> Orders --> Quotations --> New`, which reveals a " +"blank quotation form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:99 +msgid "Then, fill out the quotation form with the customer information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:101 +msgid "" +"Go to the :guilabel:`Order Lines` tab of the quotation and click " +":guilabel:`Add a Product`. Then, select the *prepaid services product* " +"configured in the steps above. Update the :guilabel:`Quantity` field with " +"the number of hours." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:105 +msgid "" +"After updating any other necessary information, :guilabel:`Confirm` the " +"quotation. This converts the quotation into an :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:109 +msgid "Create and send an invoice for prepaid services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:111 +msgid "" +"Once the :abbr:`SO (sales order)` has been confirmed, click the " +":guilabel:`Create Invoice` button. This will open a :guilabel:`Create " +"Invoices` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:114 +msgid "" +"If no down payment will be collected, the :guilabel:`Create Invoice` type " +"can remain as :guilabel:`Regular Invoice`. If a down payment will be " +"collected, choose between either :guilabel:`Down payment (percentage)` or " +":guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:118 +msgid "" +"When the necessary information has been entered, click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:120 +msgid "The invoice can then be sent to the customer for payment." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:123 +msgid "Create helpdesk ticket for prepaid services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:125 +msgid "" +"To create a *Helpdesk* ticket for prepaid services, navigate to " +":menuselection:`Helpdesk` and click the :guilabel:`Tickets` button to reveal" +" a specific team's pipeline. Click :guilabel:`New` to create a new ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:129 +msgid "" +"On the blank ticket form, create a ticket :guilabel:`Title`, and enter the " +":guilabel:`Customer` information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:132 +msgid "" +"When the customer name is added, the :guilabel:`Sales Order Item` field will" +" automatically populate with the most recent prepaid sales order item that " +"has time remaining." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:136 +msgid "Track hours on helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:138 +msgid "" +"Time spent working on a *Helpdesk* ticket is tracked on the *Timesheets* tab" +" on the specific ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:140 +msgid "" +"On the ticket detail form, click on the :guilabel:`Timesheets` tab and click" +" :guilabel:`Add a line`. Choose an :guilabel:`Employee`, add a " +":guilabel:`Description` of the task, and enter the number of " +":guilabel:`Hours Spent`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144 +msgid "" +"As new lines are added to :guilabel:`Timesheets` tab, the " +":guilabel:`Remaining Hours on SO` field is automatically updated." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of the timesheets tab on a ticket with an emphasis on the remaining " +"hours on an SO." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:152 +msgid "" +"If the number of hours on the :guilabel:`Timesheets` tab exceeds the number " +"of hours sold, the :guilabel:`Remaining Hours of SO` will turn red." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:155 +msgid "" +"As hours are added to the :guilabel:`Timesheets` tab, they are automatically" +" updated in the :guilabel:`Delivered` field on the :abbr:`SO (sales order)`," +" as well." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:159 +msgid "Invoice post-paid support services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:161 +msgid "" +"When support services are billed based on the amount of time spent on an " +"issue, an invoice cannot be created before the total number of hours " +"required to solve the problem have been entered on a timesheet. In this " +"case, a service product with the invoicing policy set to :guilabel:`Based on" +" Timesheets` would be used, like the one created above." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:167 +msgid "Create a sales order with a time-tracked product" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:169 +msgid "" +"To invoice a customer for post-paid support services, first create a sales " +"order (SO) with the *support services product*. To do this, go to " +":menuselection:`Sales --> Orders --> Quotations --> New`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:173 +msgid "Fill out the quotation with the customer information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:175 +msgid "" +"On the :guilabel:`Order Lines` tab, click :guilabel:`Add a Product`. Select " +"the post-paid services product configured in the steps above. After updating" +" any other necessary information, :guilabel:`Confirm` the quotation." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:180 +msgid "" +"Unlike with the prepaid services quotation, Odoo will not allow an invoice " +"to be created at this time. That is because no services have been performed;" +" in other words nothing has been delivered, therefore, there is nothing to " +"invoice." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:185 +msgid "Create a helpdesk ticket for time-tracked services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:187 +msgid "" +"To record a *Timesheet* entry for time-tracker services, go to " +":menuselection:`Helpdesk` and select the appropriate team for which these " +"services apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:190 +msgid "" +"If there is already an existing ticket for this issue, select it from the " +"kanban view. This will open the ticket details form. If there is no existing" +" ticket for this customer issue, click :guilabel:`New` to create a new " +"ticket and enter the necessary customer information on the blank ticket " +"details form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:195 +msgid "" +"After selecting or creating a ticket, go to the :guilabel:`Sales Order Line`" +" drop-down menu. Select the :abbr:`SO (sales order)` created in the previous" +" step." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:199 +msgid "Track support hours on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:201 +msgid "" +"In order to create an invoice for a product based on timesheets, hours need " +"to be tracked and recorded. At this point, the service is considered " +"*delivered*. To record hours for this support service, click on the " +":guilabel:`Timesheets` tab of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:205 +msgid "" +"Click :guilabel:`Add a Line` to record a new entry. Select an " +":guilabel:`Employee` from the drop-down menu, and record the time spent in " +"the :guilabel:`Hours Spent` column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:208 +msgid "" +"Repeat these steps as needed until all time spent on the issues has been " +"recorded." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of the timesheets tab on a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:215 +msgid "Create an invoice for hours tracked on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:217 +msgid "" +"After the customer's issue has been solved, and it is determined no new " +"timesheet entries will be made, an invoice can be created, and the customer " +"can be billed." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:220 +msgid "" +"To do this, return to the :abbr:`SO (sales order)` by clicking on the " +":guilabel:`Sales Order` smart button at the top of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:223 +msgid "" +"Before creating the invoice, confirm that the number in the " +":guilabel:`Delivered` column matches the total number of :guilabel:`Hours " +"Spent` listed in the :guilabel:`Timesheets` tab on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of a sales order with emphasis on the delivered column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:230 +msgid "" +"Then, click :guilabel:`Create Invoice`. This will open a :guilabel:`Create " +"Invoices` pop-up window. If no down payment will be collected, the " +":guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. " +"If a down payment will be collected, choose between either :guilabel:`Down " +"payment (percentage)` or :guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:236 +msgid "" +"Use the :guilabel:`Timesheets Period` field if this invoice should only " +"include timesheets from a certain time period. If this field is left blank, " +"*all* applicable timesheets that have not yet been invoiced will be " +"included." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of create invoices pop up showing timesheets period fields." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:244 +msgid "" +"When the necessary information has been entered, click :guilabel:`Create " +"Invoice`. The invoice can then be sent to the customer for payment." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview.rst:5 +#: ../../content/applications/services/timesheets/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3 +msgid "Getting started with Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5 +msgid "" +"Odoo :guilabel:`Helpdesk` is a ticket-based customer support application. " +"Teams can track, prioritize, and solve customer issues from their pipeline, " +"which is organized in customizable stages. Multiple teams can be configured " +"and managed in one dashboard." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10 +msgid "Create Helpdesk teams" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:12 +msgid "" +"Setting up multiple teams allows for tickets to be grouped by location or by" +" support type." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14 +msgid "" +"To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. To create a new team, click on the :guilabel:`New`" +" button in the top left of the dashboard. From there, name the new team, and" +" fill out the remaining fields as defined in the following sections on the " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of the Helpdesk teams page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:24 +msgid "Assignment & Visibility" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:27 +msgid "Determine to whom the team will be visible" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:29 +msgid "" +"Under the :guilabel:`Visibility` section, determine who can view this team " +"and its tickets." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:31 +msgid "" +":guilabel:`Invited internal users` have access to the team and tickets they " +"are following. This can be modified on each individual ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:33 +msgid "" +":guilabel:`All internal users` have access to the team and all of its " +"tickets without being a follower." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:35 +msgid "" +":guilabel:`Invited portal users and all internal users` have access to the " +"team without being a follower. Portal users will only be able to access " +"tickets that they are following." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:39 +msgid "" +"A `Customer Support` team intended to handle general issues with shipping " +"and product issues would have the visibility setting :guilabel:`Invited " +"portal users and all internal users`. However, a `Financial Services` team " +"handling tickets related to accounting or tax information would only need to" +" be visible to :guilabel:`Invited internal users`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:45 +msgid "Automatically assign new tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:47 +msgid "" +"When tickets are received, they will need to be assigned to a member of the " +"support team. This can be done manually on each ticket individually, or " +"through :guilabel:`Automatic Assignment`. Check the box next to " +":guilabel:`Automatic Assignment` to enable the feature for this team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of a Helpdesk team settings page emphasizing the assignment and visibility features\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:56 +msgid "" +"Select one of the following assignment methods, based on how workload should" +" be allocated across the team:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60 +msgid "" +":guilabel:`Each user is assigned an equal number of tickets` assigns tickets" +" to team members" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60 +msgid "" +"based on total ticket count, regardless of the number of open or closed " +"tickets they are currently assigned." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64 +msgid "" +":guilabel:`Each user has an equal number of open tickets` assigned tickets " +"to team members based" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:63 +msgid "" +"on how many open tickets they are currently assigned. This option is useful " +"for automatically delegating a heavier workload to high-performers who tend " +"to close tickets quickly." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:66 +msgid "" +"Finally, add the :guilabel:`Team Members` who will be assigned tickets for " +"this team. Leave the field empty to include all employees who have the " +"proper assignments and access rights configured in their user account " +"settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:71 +msgid "" +"If an employee has time off scheduled in the :guilabel:`Time Off` " +"application, they will not be assigned tickets during that time. If no " +"employees are available, the system will look ahead until there is a match." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:76 +msgid ":ref:`Manage users `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:77 +msgid ":doc:`Access rights `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:80 +msgid "Create or modify kanban stages" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:82 +msgid "" +":guilabel:`Stages` are used to organize the *Helpdesk* pipeline and track " +"the progress of tickets. Stages are customizable, and can be renamed to fit " +"the needs of each team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:85 +msgid "" +"To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk --> " +"Configuration --> Stages`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:88 +msgid "" +":ref:`Developer mode ` must be activated in order to access " +"the stages menu. To activate developer mode go to :menuselection:`Settings " +"--> General Settings --> Developer Tools` and click on :guilabel:`Activate " +"the developer mode`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:92 +msgid "" +"The list view shows an overview of all the stages currently available in " +"Helpdesk. They are listed in the order they appear in the pipeline. To " +"change the order of the stages, use the arrow buttons on the left side of " +"the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:97 +msgid "" +"Change the stage order on the kanban view by dragging and dropping " +"individual columns." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of the stage list page emphasizing the option to create a new stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:104 +msgid "" +"To create a new stage, click on the :guilabel:`New` button in the top left " +"of the dashboard. Next, choose a name for the new stage, and add a " +"description (though it is not required). Fill out the remaining fields " +"following the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of a stage's settings page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:113 +msgid "Add email and SMS templates to stages" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:115 +msgid "" +"When an :guilabel:`Email Template` is added to a stage, an email is " +"automatically sent to the the customer when a ticket reaches that specific " +"stage in the helpdesk pipeline. Likewise, adding an :guilabel:`SMS Template`" +" will result in an SMS text message being sent to the customer." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:120 +msgid "" +"SMS Text Messaging is an In-App Purchase (IAP) service that requires prepaid" +" credits to work. Refer to `SMS Pricing FAQ `_ for additional information." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:124 +msgid "" +"To select an existing email template, select it from the :guilabel:`Email " +"Template` field. Click on the arrow key to the right of the field to edit " +"the template." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:127 +msgid "" +"To create a new template, click the field and begin typing a new template " +"title. Then select :guilabel:`Create and edit`, and complete the form " +"details." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:130 +msgid "" +"Follow the same steps to select, edit, or create an :guilabel:`SMS " +"Template`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of an SMS template setup page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:137 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:60 +msgid ":doc:`/applications/general/email_communication/email_template`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:140 +msgid "Assign stages to a team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:142 +msgid "" +"Make a selection in the :guilabel:`Teams` field on the :guilabel:`Stages` " +"form. More than one team may be selected, since the same stage(s) can be " +"assigned to multiple teams." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:0 +msgid "View of stage setup emphasizing teams field" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:150 +msgid "Fold a stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:152 +msgid "" +"Check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form to" +" display this stage as *folded* by default in the kanban view for this team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:156 +msgid "" +"Tickets that reach a *folded* stage are considered closed. Closing a ticket " +"before the work is completed can result in reporting and communication " +"issues. This setting should only be enabled for stages that are considered " +"*closing* stages." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:160 +msgid "" +"Alternatively, stages can be temporarily folded in the kanban view, by " +"clicking on the settings icon and selecting :guilabel:`Fold`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:164 +msgid "" +"Manually folding a stage from the kanban view will not close the tickets in " +"the stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:3 +msgid "Help center" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:5 +msgid "" +"Odoo *Helpdesk* integrates with the *Forum*, *eLearning*, and *Knowledge* " +"apps to create the *help center*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "" +"Overview of the settings page of a team emphasizing the help center " +"features." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:12 +msgid "" +"The *help center* is a centralized location where teams and customers can " +"search for and share detailed information about products and services." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:16 +msgid "" +"In order to activate any of these features on a *Helpdesk* team, (*Forums*, " +"*eLearning*, or *Knowledge*), the :guilabel:`Visibility` of the team has to " +"be set to :guilabel:`Invited portal users and all internal users`. See " +":doc:`Getting Started " +"` for more " +"information on *Helpdesk* team settings and configuration." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:23 +msgid "" +"Since all of the *help center* features require integration with other " +"applications, enabling any of them may result in the installation of " +"additional modules or applications." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:26 +msgid "" +"Installing a new application on a *One-App-Free* database will trigger a " +"15-day trial. At the end of the trial, if a paid subscription has not been " +"added to the database, it will no longer be active or accessible." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:31 +msgid "Knowledge" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:33 +msgid "" +"Odoo's *Knowledge* application is a collaborative library where users can " +"store, edit, and share information. The *Knowledge* app is represented " +"throughout the database by a *book* icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a message in Helpdesk focusing on the Knowledge book icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:41 +msgid "Enable Knowledge on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:43 +msgid "" +"To enable the *Knowledge* feature on a *Helpdesk* team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or " +"create a :doc:`new one " +"`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:47 +msgid "" +"When a team has been selected or created, Odoo displays that team's detail " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:49 +msgid "" +"On the team's detail form, scroll down to the :guilabel:`Self-Service` " +"section. Click the box next to :guilabel:`Knowledge` to activate the " +"*Knowledge* feature. When clicked, a new field labeled :guilabel:`Article` " +"appears." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:53 +msgid "" +"Clicking the :guilabel:`Article` field reveals a drop-down menu. At first, " +"there is only one option in the drop-down menu titled :guilabel:`Help`, " +"which Odoo provides by default. Select :guilabel:`Help` from the drop-down " +"menu to choose this article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:58 +msgid "" +"To create a new article, go to the :menuselection:`Knowledge app`, then " +"hover the cursor next to the :guilabel:`Workspace` section heading, located " +"in the left sidebar. Moving the cursor there reveals a hidden :guilabel:`➕ " +"(plus sign)` icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:62 +msgid "" +"Click the :guilabel:`➕ (plus sign)` to create a new article in the " +":guilabel:`Workspace`. In the upper right corner of the page, click the " +":guilabel:`Share` button, and slide the :guilabel:`Share to Web` toggle " +"switch until it reads :guilabel:`Article Published`. It can then be added to" +" a *Helpdesk* team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:67 +msgid "" +"Once an article has been created and assigned to a *Helpdesk* team, content " +"can be added and organized through the *Knowledge* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:71 +msgid "" +":doc:`Editing Knowledge articles " +"`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:74 +msgid "Search articles from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:76 +msgid "" +"When members of a *Helpdesk* team are trying to solve a ticket, they can " +"search through the content in the *Knowledge* app for more information on " +"the issue." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:79 +msgid "" +"To search *Knowledge* articles, open a ticket — either from the *Helpdesk* " +"app dashboard, or by going to :menuselection:`Helpdesk app --> Tickets --> " +"All Tickets`, and selecting a :guilabel:`Ticket` from the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:83 +msgid "" +"When a :guilabel:`Ticket` is selected, Odoo reveals that ticket's detail " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:85 +msgid "" +"Click the :guilabel:`Knowledge (book)` icon, located above the chatter to " +"open a search window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of knowledge search window from a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:92 +msgid "" +"*Knowledge* articles can also be searched by pressing :command:`Ctrl + K` to" +" open the command palette, then typing :command:`?`, followed by the name of" +" the desired article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:95 +msgid "" +"When Odoo reveals the desired article, click it, or highlight the " +":guilabel:`Article` title, and press :command:`Enter`. This will open the " +"article in the :guilabel:`Knowledge` application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:98 +msgid "To open the article in a new tab, press :command:`Ctrl + Enter`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:101 +msgid "" +"If a more in-depth search is required, press :command:`Alt + B`. That will " +"reveal a separate page, in which a more detailed search can occur." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:105 +msgid "Share articles to the help center" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:107 +msgid "" +"In order for a *Knowledge* article to be available to customers and website " +"visitors, it has to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:111 +msgid "" +"Even though the *Help* article has been enabled on a team, Odoo will not " +"share all the nested articles to the web. Individual articles intended for " +"customers **must** be published for them to be viewable on the website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:115 +msgid "" +"To publish an article, navigate to the desired article, by following the " +"above steps, and click the :guilabel:`Share` icon in the upper-right corner." +" This will reveal a menu. Slide the toggle button labeled :guilabel:`Share " +"to Web` to read :guilabel:`Article Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a knowledge article focused on sharing and publishing options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:124 +msgid "Solve tickets with templates" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:126 +msgid "" +"*Template* boxes can be added to *Knowledge* articles to allow content to be" +" reused, copied, sent as messages, or added to the description on a ticket. " +"This allows teams to maintain consistency when answering customer tickets, " +"and minimize the amount of time spent on responding to repeat questions." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:131 +msgid "Add templates to articles" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:133 +msgid "" +"To create a template, go to :menuselection:`Knowledge --> Help`. Click on an" +" existing nested article or create a new one by clicking the :guilabel:`➕ " +"(plus sign)` icon next to *Help*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:136 +msgid "" +"Type `/` to open the :guilabel:`Powerbox` and view a list of :doc:`commands " +"`. Select or type " +"`template`. A gray template block will be added to the page. Add any " +"necessary content to this block." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a template in knowledge with focus on send and copy options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:145 +msgid "" +"Templates will only display the :guilabel:`Use as description` or " +":guilabel:`Send as Message` options if they are accessed directly from " +"*Helpdesk*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:149 +msgid "Use templates in tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:151 +msgid "" +"Templates can be used to respond directly to a *Helpdesk* ticket as a " +"message, or to add information to the ticket's description." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:154 +msgid "" +"To use templates in a *Helpdesk* ticket, first, open a ticket, either from " +"the :guilabel:`Helpdesk` dashboard or by going to :menuselection:`Helpdesk " +"--> Tickets --> All Tickets` and selecting a :guilabel:`Ticket` from the " +"list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:158 +msgid "" +"Click on the :guilabel:`Knowledge (book)` icon above the chatter for the " +"ticket. This opens a search window. In this search window, select, or search" +" for the desired article. Doing so reveals that article page in the Odoo " +"*Knowledge* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:162 +msgid "" +"To use a template to respond to a ticket, click :guilabel:`Send as message` " +"in the upper right corner of the template box, located in the body of the " +"article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:165 +msgid "" +"Doing so opens a :guilabel:`Compose email` pop-up window. In this window, " +"select the recipients, make any necessary additions or edits to the " +"template, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:169 +msgid "" +"To use a template to add information to a ticket's description, click " +":guilabel:`Use as description` in the upper right corner of the template " +"box, located in the body of the article. Doing so will not replace the " +"existing text in a ticket's description. The template will be added as " +"additional text." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:177 +msgid "Community Forum" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:179 +msgid "" +"A *Community Forum* provides a space for customers to answer each other's " +"questions and share information. By integrating a forum with a *Helpdesk* " +"team, tickets submitted by customers can be converted to posts and shared." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:184 +msgid "Enable forums on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:186 +msgid "" +"To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by " +"navigating to :menuselection:`Helpdesk app --> Configuration --> Teams` and " +"select a team, or create a :doc:`new one " +"`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:190 +msgid "" +"Selecting or creating a team reveals that team's detail form. Scroll down to" +" the :guilabel:`Self-Service` section of features, and enable " +":guilabel:`Community Forum`, by checking the box beside it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:194 +msgid "" +"When activated, a new field labeled :guilabel:`Forums` appears beneath." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:196 +msgid "" +"Click the empty :guilabel:`Forums` field to reveal a drop-down menu. By " +"default, there is only one option to begin with, labeled :guilabel:`Help`. " +"That is the option Odoo automatically created when the :guilabel:`Community " +"Forums` feature was enabled. Select :guilabel:`Help` from the drop-down menu" +" to enable that forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:201 +msgid "" +"To create a new forum, type a name into the blank :guilabel:`Forums` field, " +"then click the :guilabel:`Create and Edit` option. Multiple forums can be " +"selected in this field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:205 +msgid "" +"Check out the :doc:`Forum documentation <../../../websites/forum>` to learn " +"how to configure, use, and moderate a forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:209 +msgid "Create a forum post from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:211 +msgid "" +"When a *Helpdesk* team has a *Forum* enabled, tickets submitted to that team" +" can be converted to forum posts." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:214 +msgid "" +"To do that, select a ticket, either from a team's pipeline or from " +":menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` " +"application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:217 +msgid "" +"At the top of the ticket detail form, click the :guilabel:`Share on Forum` " +"button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "" +"Overview of the Forums page of a website to show the available ones in Odoo " +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:223 +msgid "" +"When clicked, a pop-up appears. Here, the post and title can be edited to " +"correct any typos, or modified to remove any proprietary or client " +"information. :guilabel:`Tags` can also be added to help organize the post in" +" the forum, making it easier for users to locate during a search. When all " +"adjustments have been made, click :guilabel:`Create and View Post`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:229 +msgid "eLearning" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:231 +msgid "" +"Odoo *eLearning* courses offer customers additional training and content in " +"the form of videos, presentations, and certifications/quizzes. Providing " +"additional training enables customers to work through issues and find " +"solutions on their own. They can also develop a deeper understanding of the " +"services and products they are using." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:237 +msgid "Enable eLearning courses on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:239 +msgid "" +"To enable *eLearning* courses on a *Helpdesk* team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or " +"create a :doc:`new one " +"`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:243 +msgid "" +"On the team's settings page, scroll to the :guilabel:`Self-Service` section," +" and check the box next to :guilabel:`eLearning`. A new field will appear " +"below, labeled :guilabel:`Courses`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:246 +msgid "" +"Click the empty field next to :guilabel:`Courses` beneath the " +":guilabel:`eLearning` feature to reveal a drop-down menu. Select an " +"available course from the drop-down menu, or type a title into the field, " +"and click :guilabel:`Create and edit` to create a new course from this page." +" Multiple courses can be assigned to a single team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:252 +msgid "Create an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:254 +msgid "" +"A new *eLearning* course can be created from the :guilabel:`Helpdesk` team's" +" settings page, as in the step above, or from the *eLearning* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:257 +msgid "" +"To create a course directly through the *eLearning* application, navigate to" +" :menuselection:`eLearning --> New`. This reveals a blank course template " +"that can be customized and modified as needed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:261 +msgid "" +"On the course template page, add a :guilabel:`Course Title`, and below that," +" :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:263 +msgid "" +"Click on the :guilabel:`Options` tab. Under :guilabel:`Access Rights`, " +"choose the :guilabel:`Enroll Policy`. This determines which users will be " +"allowed to take the course. Under :guilabel:`Display`, choose the course " +":guilabel:`Type` and :guilabel:`Visibility`. The :guilabel:`Visibility` " +"setting determines whether the course will be available to public site " +"visitors or members." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:269 +msgid "Add content to an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:271 +msgid "" +"To add content to a course, click the :guilabel:`Content` tab and select " +":guilabel:`Add Content`. Choose the :guilabel:`Content Type` from the drop-" +"down menu and upload the file, or paste the link, where instructed. Click " +":guilabel:`Save` when finished. Click :guilabel:`Add Section` to organize " +"the course in sections." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a course being published for Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:281 +msgid "" +"In order to add a certification to a course, go to :menuselection:`eLearning" +" --> Configuration --> Settings`, check the box labeled " +":guilabel:`Certifications`, and :guilabel:`Save` to activate the setting." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:286 +msgid "" +"`Odoo Tutorials: eLearning `_" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:289 +msgid "Publish an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:291 +msgid "" +"To allow customers to enroll in a course, both the course and the contents " +"need to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:293 +msgid "" +"If the course is published, but the contents of the course are not " +"published, customers can enroll in the course on the website, but they won't" +" be able to view any of the course content. Knowing this, it may be " +"beneficial to publish the course first if the course contents are intended " +"to be released over time, such as classes with a weekly schedule." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:298 +msgid "" +"To make the entire course available at once, each piece of course content " +"must be published first, then the course can be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:301 +msgid "" +"To publish a course, choose a course from the *eLearning* dashboard. On the " +"course template page, click the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:304 +msgid "" +"This will reveal the front end of the course's web page. At the top of the " +"course web page, move the :guilabel:`Unpublished` toggle switch to " +":guilabel:`Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:308 +msgid "Publish eLearning course contents from the back-end" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:310 +msgid "" +"To publish *eLearning* course content from the back-end, choose a course " +"from the *eLearning* dashboard. On the course template page, click the " +":guilabel:`Published Contents` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:313 +msgid "" +"Doing so reveals a separate page displaying all the published content " +"related to that course. Remove the default :guilabel:`Published` filter from" +" the search bar in the upper-right corner, to reveal all the content related" +" to the course - even the non-published content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:317 +msgid "" +"Click the :guilabel:`≣ (List View)` icon in the upper-right corner, directly" +" beneath the search bar to switch to list view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:320 +msgid "" +"While in :guilabel:`List View`, there is a checkbox on the far left of the " +"screen, above the listed courses, to the left of the :guilabel:`Title` " +"column. When that checkbox is clicked, all the course contents are selected " +"at once." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:324 +msgid "" +"With all the course content selected, double click any of the boxes in the " +":guilabel:`Is Published` column. This reveals a pop-up window, asking for " +"confirmation that all selected records are intended to be published. Click " +":guilabel:`OK` to automatically publish all course content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a course contents being published in Odoo Helpdesk back-end." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:3 +msgid "Customer ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:5 +msgid "" +"Asking customers to rate the support they received from a *Helpdesk* team " +"provides an opportunity to gauge team performance and track customer " +"satisfaction. Ratings can be published to the portal, providing customers " +"with a general overview of the team's performance." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:10 +msgid "Enable customer ratings on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:12 +msgid "" +"To enable *customer ratings* on a helpdesk team by going to " +":menuselection:`Helpdesk --> Configuration --> Teams`. Select a team from " +"the list and navigate to the settings page. Scroll to the " +":guilabel:`Performance` section, and check the box for :guilabel:`Customer " +"Ratings`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n" +"in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:22 +msgid "Set a ratings request email template on a stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:24 +msgid "" +"To automatically request ratings from customers once their tickets have " +"closed, an email template should be added to the appropriate stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:27 +msgid "" +"Once the :guilabel:`Customer Ratings` setting has been enabled on the team's" +" settings page, (see above) click the :guilabel:`Set an Email Template on " +"Stages` link. Select a stage from the list, or click :guilabel:`New` to " +"create a new stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:32 +msgid "" +"Customers should only be asked to rate tickets once an issue has been " +"resolved and their ticket is closed. Therefore, a *ratings request* email " +"should only be added to a stage that is **folded** in the kanban, as tickets" +" in a *folded stage* are considered closed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:36 +msgid "" +"On the stage's settings page, select `Helpdesk: Ticket Rating Request` in " +"the :guilabel:`Email Template` field. This template has been pre-configured " +"with ratings customers can use to provide feedback. To view the template, " +"click the arrow button to the right of the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:40 +msgid "" +"Once the template has been added to the stage, it will automatically send a " +"message when a ticket is moved to that stage. Customers will be asked to " +"rate the support they received with colored icons." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:43 +msgid "*Green smiling face* - Satisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:44 +msgid "*Yellow neutral face* - Okay" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:45 +msgid "*Red frowning face* - Dissatisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"View of a standard helpdesk customer review email template for Odoo " +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:51 +msgid "" +"After selecting a rating, customers are taken to a webpage where they can " +"provide specific written feedback to support their rating. Once a rating is " +"submitted, it is added to the chatter on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:56 +msgid "" +"Customer ratings can also be viewed through the :guilabel:`Customer Ratings`" +" report. To view this report, go to :menuselection:`Helpdesk --> Reporting " +"--> Customer Ratings`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:63 +msgid "Publish ratings on the customer portal" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:65 +msgid "" +"After enabling the :guilabel:`Customer Ratings` setting, an option to " +"publish ratings on the team's website appears. Enabling this setting " +"provides portal users with an overview of the ratings the team has received " +"over the last thirty days. Specific written feedback will not be included; " +"only statistics of the team's performance will be visible." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:71 +msgid "" +"In order to display ratings on the customer portal, a team has to have their" +" visibility setting set to :guilabel:`Invited portal users and all internal " +"users`. This setting is found on the team's settings page under " +":guilabel:`Visibility`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:75 +msgid "" +"Next, to publish the ratings, go to :menuselection:`Helpdesk --> " +"Configuration --> Teams` and select a team. Scroll to " +":guilabel:`Performance` and enable :guilabel:`Publish this team's ratings on" +" your website`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:79 +msgid "" +"To view the ratings for a team, a customer will log into the portal and " +"navigate to one of their tickets. After clicking on the team name in the " +":guilabel:`Managed By` field, they will be directed to a page with the " +"team's ratings over the past thirty days." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "View of the ratings performance overview from the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:88 +msgid "Manually hide individual ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:90 +msgid "" +"Individual ratings can be manually hidden from the portal. This allows for " +"specific ratings to be kept out of the performance metrics that are shown to" +" customers." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:93 +msgid "" +"To make a rating visible only to internal users, navigate to the page for a " +"rating. This can be done in one of the following ways:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:96 +msgid "" +"Go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings` and click" +" on one of the kanban cards for an individual rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:98 +msgid "" +"Navigate to :menuselection:`Helpdesk --> Tickets --> All Tickets` and remove" +" the :guilabel:`Open` filter from the search bar. Then filter by " +":guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. " +"Select a ticket from the results. Click the :guilabel:`Rating` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:103 +msgid "" +"Once on the rating details page, check the :guilabel:`Visible Internally " +"Only` box." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:110 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:291 +msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:111 +msgid ":doc:`/applications/services/helpdesk/overview/reports`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3 +msgid "Start receiving tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:5 +msgid "" +"Odoo *Helpdesk* offers multiple channels where customers can reach out for " +"assistance, such as email, live chat, and through a website's submission " +"form. The variety of these contact options provides customers with multiple " +"opportunities to receive support quickly, while also giving the support team" +" the ability to manage multi-channel support tickets from one central " +"location." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11 +msgid "Enable channel options to submit tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Teams` and choose an " +"existing team, or click :guilabel:`New` to :doc:`create a new team " +"`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:16 +msgid "" +"On the team's settings page, scroll down to :guilabel:`Channels`. Select one" +" or more channel(s) to enable by checking the respective box(es)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:19 +msgid ":guilabel:`Email Alias`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:20 +msgid ":guilabel:`Website Form`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21 +msgid ":guilabel:`Live Chat`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:24 +msgid "Email Alias" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26 +msgid "" +"The *Email Alias* setting automatically creates tickets from messages sent " +"to that team's specified email alias." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:29 +msgid "" +"To alter a *Helpdesk* team's email alias, navigate to the :guilabel:`Teams` " +"settings page. Find :guilabel:`Email Alias`, under the :guilabel:`Channels` " +"heading, and then type in the desired team alias in the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:33 +msgid "" +"When a new *Helpdesk* team is created, an :guilabel:`Email Alias` is " +"created, as well. This alias can be changed in the :guilabel:`Alias` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:37 +msgid "" +"If the database does not have a custom domain already configured, click " +":guilabel:`Configure a custom domain` to be redirected to the " +":guilabel:`Settings` page. From there, enable :guilabel:`Custom Email " +"Servers`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the email alias feature in Odoo\n" +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:46 +msgid "" +"When an email is received, the subject line from the email becomes the title" +" of a new *Helpdesk* ticket. The body of the email is also added to the " +"ticket under the :guilabel:`Description` tab and in the ticket's " +":guilabel:`Chatter` section." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:51 +msgid "" +"The configuration steps outlined above are for **Odoo Online** and " +"**Odoo.sh** databases. For **On-premise** databases, additional " +"configuration for custom email servers and email aliases may be required." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56 +msgid "Website Form" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:58 +msgid "" +"Enabling the *Website Form* setting adds a new page to the website with a " +"customizable form. A new ticket is created once the required form fields are" +" filled out and submitted." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61 +msgid "" +"To activate the website form, navigate to a team's settings page under " +":menuselection:`Configuration --> Teams`. Find the :guilabel:`Website Form` " +"feature under the :guilabel:`Channels` section, and check the box." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:65 +msgid "" +"After the feature is activated, click the :guilabel:`Go to Website` smart " +"button at the top of the that :guilabel:`Teams` settings page to view and " +"edit the new website form, which is created automatically by Odoo." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:70 +msgid "" +"After enabling the website form, the *Teams* settings page may need to be " +"refreshed before the *Go to Website* smart button appears." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:73 +msgid "" +"As well, if a *Help Center* is published, the smart button will navigate " +"there first. Simply click the :guilabel:`Contact Us` button at the bottom of" +" the forum to navigate to the ticket submission form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the Go to Website button in\n" +"Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:83 +msgid "Customize the website ticket form" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:85 +msgid "" +"To customize the default ticket submission form, click the :guilabel:`Edit` " +"button in the upper right corner of the page. Then click on one of the " +"fields in the form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88 +msgid "" +"Add, remove, or update fields as necessary to alter the information " +"submitted by customers. Fields can be made marked as :guilabel:`Required`, " +"by toggling the switch from gray to blue in the website builder's editor " +"window, located under the :guilabel:`Field` section. As well, other " +"pertinent field information can be edited here, such as:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:93 +msgid "" +":guilabel:`Type`: which matches an Odoo model value to the field (e.g. " +"`Customer Name`)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:94 +msgid "" +":guilabel:`Input Type`: to determine what type of input the field should be," +" like `Text`, `Email`, `Telephone` or `URL`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:96 +msgid "" +":guilabel:`Label`: to give the form field a label (e.g. `Full Name`, `Email " +"Address`, etc.). Also control the label position on the form by using the " +"nested :guilabel:`Position` options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:98 +msgid "" +":guilabel:`Description`: which, optionally, adds an editable line under the " +"input box to provide additional contextual information related to the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:100 +msgid ":guilabel:`Placeholder`: to add a sample input value." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:101 +msgid "" +":guilabel:`Default value`: to add common use case values that most customers" +" would find valuable" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:102 +msgid "" +":guilabel:`Required`: which sets the field as mandatory before the form can " +"be submitted." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:103 +msgid "" +":guilabel:`Visibility`: to allow for absolute or conditional visibility of " +"the field. Nested options, such as device visibility, appear when certain " +"options are selected." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:107 +msgid "" +"Text blocks can be added in the farthest 1/3 column of the ticket form page," +" next to the ticket form. This is an ideal place to include team information" +" such as additional contact details, hours, or common helpful articles that " +"link to the :guilabel:`Forum`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the unpublished website form to submit a ticket for Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:115 +msgid "" +"Once the form has been optimized and is ready for public use, " +":guilabel:`Save` the changes, and then publish the form by clicking on the " +":guilabel:`Unpublished` button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:119 +msgid "Live Chat" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:121 +msgid "" +"The *Live Chat* feature allows website visitors to connect directly with a " +"support agent or chatbot. During these conversations, *Helpdesk* tickets can" +" be instantly created by using the :doc:`response command " +"` `/helpdesk`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125 +msgid "" +"To enable *Live Chat*, navigate to the :menuselection:`Configuration --> " +"Teams` list view, select a team, and on the :guilabel:`Teams` settings page," +" click the check box next to :guilabel:`Live Chat`, under the " +":guilabel:`Channels` heading." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:130 +msgid "" +"If this is the first time *Live Chat* has been enabled on the database, the " +"page may need to be saved manually and refreshed before any further steps " +"can be taken." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:133 +msgid "" +"With the :guilabel:`Live Chat` setting engaged, click on :guilabel:`View " +"Channels`. Then, on the :guilabel:`Website Live Chat Channels` dashboard, " +"select the kanban card for the channel that was created for the *Helpdesk* " +"team, or create a :guilabel:`New` one if necessary. When a kanban card is " +"selected, additional options await on the channel's form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:139 +msgid "Customize the live chat channel" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:141 +msgid "" +"When an individual channel is clicked on the :guilabel:`Website Live Chat " +"Channels` dashboard, Odoo directs the page to the channel form. From there, " +"the :guilabel:`Channel Name` can be edited, however Odoo names this to match" +" the *Helpdesk* team's kanban pipeline, by default." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:146 +msgid "" +"If a *Helpdesk* team is named `Customer Care`, a *Live Chat* channel will be" +" created with the same name." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0 +msgid "View of the kanban cards for the available Live Chat channels." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:153 +msgid "On the channel form, navigate through the tabs to complete the setup." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:156 +msgid "Add operators" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:158 +msgid "" +"*Operators* are the users who will act as agents and respond to live chat " +"requests from customers. The user who originally created the live chat " +"channel will be added by default." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:161 +msgid "" +"To add additional users, navigate and click on the live chat channel from " +"the :guilabel:`Website Live Chat Channels` dashboard, and on the " +":guilabel:`Operators` tab, click :guilabel:`ADD`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:164 +msgid "" +"Then, click the check box next to the users to be added, and click " +":guilabel:`SELECT`. :guilabel:`New` operators can be created and added to " +"the list, as well, by filling out the :guilabel:`Create Operators` form and " +"then clicking :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for " +"multiplerecord creations)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:169 +msgid "" +"As well, current operators can be edited or removed by clicking on their " +"respective boxes in the :guilabel:`Operators` tab, and then adjusting their " +"form values, or by using one of the form buttons located at the bottom of " +"the form, such as :guilabel:`REMOVE`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:174 +msgid "" +"Users can add themselves as an operator by clicking the :guilabel:`Join` " +"button on a *Live Chat* channel." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:178 +msgid "Modify channel options" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:180 +msgid "" +"The :guilabel:`Options` tab contains the visual and text settings for the " +"live chat window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:182 +msgid "" +"Change the text in the :guilabel:`Text of the Button` field to update the " +"greeting displayed in the text bubble when the live chat button appears on " +"the website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:185 +msgid "" +"Edit the :guilabel:`Welcome Message` to change the message a visitor sees " +"when they open the chat window. This message will appear as though it is " +"sent by a live chat operator, and should be an invitation to continue the " +"conversation." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:189 +msgid "" +"Edit the :guilabel:`Chat Input Placeholder` to change the text that appears " +"in the box where visitors will type their replies." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:192 +msgid "" +"Change the :guilabel:`Livechat Button Color` and the :guilabel:`Channel " +"Header Color` by clicking a color bubble to open the color selection window." +" Click the refresh icon to the right of the color bubbles to reset the " +"colors to the default selection." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:197 +msgid "" +"Color selection, for the button or header, can be made manually, or through " +"RGB, HSL or HEX code selection. Different options will be available, " +"depending on your operating system." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:201 +msgid "Create channel rules" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:203 +msgid "" +"The :guilabel:`Channel Rules` tab determines when the live chat window opens" +" on the website by logic of when a :guilabel:`URL Regex` action is triggered" +" (e.g., a page visit)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:206 +msgid "" +"Edit existing rules, or create a new one by clicking :guilabel:`Add a line`," +" and fill out the pop-up form details based on how the rule should apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:209 +msgid "" +"If a :guilabel:`Chatbot` will be included on this channel, select it from " +"the dropdown. If the chatbot will only be active when no operators are " +"available, check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:214 +msgid "" +"If a chatbot is added to a live chat channel, then 3 new smart buttons will " +"appear on the channel settings form: :guilabel:`Chatbots`, " +":guilabel:`Sessions`, and :guilabel:`% Happy`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:217 +msgid "" +"The :guilabel:`Chatbots` smart button is where the chatbot can be programmed" +" with a :guilabel:`Script`. Each line in the :guilabel:`Script` contains a " +":guilabel:`Message`, :guilabel:`Step Type`, :guilabel:`Answers`, and " +"conditional :guilabel:`Only If` logic that applies when certain pre-filled " +"answers are chosen. To create more steps in the :guilabel:`Script`, click " +":guilabel:`Add a line` and fill out the script steps form according to the " +"desired logic." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:223 +msgid "" +":guilabel:`Sessions` is where live chat sessions are recorded in order of " +"descending :guilabel:`Session Date`, by default. Each record includes the " +":guilabel:`Attendees` involved in the live chat session, the :guilabel:`# " +"Messages`, as well as any :guilabel:`Rating` that was received when the " +"session ended." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:227 +msgid "" +"The :guilabel:`% Happy` smart button includes a log of ratings that were " +"left by live chat attendees, and are labeled by date, time, and the support " +"agent who was responsible for the live chat session." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:231 +msgid "" +"Add the URL for the pages this channel will be applied to in the " +":guilabel:`URL Regex` field. If this channel will only be available to users" +" in specific countries, add them to the :guilabel:`Country` field. If this " +"field is left blank, the channel will be available to all site visitors." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:241 +msgid "Use the live chat widget" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:243 +msgid "" +"The :guilabel:`Widget` tab on the live chat channel form offers an " +"embeddable website widget, or a shortcode for instant customer/supplier " +"access to a live chat window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:246 +msgid "" +"The live chat :guilabel:`Widget` can be applied to websites created through " +"Odoo by navigating to the :menuselection:`Website --> Configuration --> " +"Settings`. Then scroll to the :guilabel:`Live Chat` section, and select the " +"channel to add to the site. Click :guilabel:`Save` to apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:250 +msgid "" +"To add the widget to a website created on a third-party platform, click " +":guilabel:`COPY` and paste the code into the `` tag on the site." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:253 +msgid "" +"Likewise, to send a live chat session to a customer or supplier, click the " +"second :guilabel:`COPY` button which contains a link to join directly." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:257 +msgid "Create a support ticket from a live chat session" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:259 +msgid "" +"Once live chat is enabled, operators will be able to communicate with site " +"visitors in real time." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261 +msgid "" +"During the conversation, an operator can use the shortcut :doc:`command " +"` `/helpdesk` to create a ticket " +"without leaving the chat window. The transcript from the conversation will " +"be added to the new ticket, under the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267 +msgid "Prioritizing tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:269 +msgid "" +"All tickets include a :guilabel:`Priority` field. The highest priority " +"tickets will appear at the top of the kanban and list views." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of a team's kanban view and the prioritized tasks in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:276 +msgid "The priority levels are represented by stars:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:278 +msgid "0 stars = *Low Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:279 +msgid "1 star = *Medium Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:280 +msgid "2 stars = *High Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:281 +msgid "3 stars = *Urgent*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:283 +msgid "" +"Tickets will be set to low priority (0 stars) by default. To change the " +"priority level, select the appropriate number of stars on the kanban card, " +"or on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:287 +msgid "" +"As priority levels can be used as criteria for assigning :doc:`SLAs `, " +"changing the priority level of a ticket can alter the :abbr:`SLA (Service " +"Level Agreement)` deadline." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:292 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293 +msgid ":doc:`/applications/websites/livechat`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:5 +msgid "" +"Odoo *Helpdesk* includes several reports that provide the opportunity to " +"track trends for customer support tickets, identify areas for improvement, " +"manage employee workloads, and confirm when customer expectations are met." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:10 +msgid "Available reports" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:12 +msgid "" +"Details about the reports available in Odoo *Helpdesk* can be found below. " +"To view the different reports, go to :menuselection:`Helpdesk --> " +"Reporting`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:16 +msgid "Ticket Analysis" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:18 +msgid "" +"The *Ticket Analysis* report (:menuselection:`Helpdesk --> Reporting --> " +"Ticket Analysis`) provides an overview of every customer support ticket in " +"the database. This includes the number of tickets assigned among teams and " +"individual users." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:22 +msgid "" +"This report is useful in identifying where teams are spending the most time," +" and helps determine if there is an uneven workload distribution among the " +"support staff. The default report counts the number of tickets per team and " +"groups them by stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of Ticket Analysis report default view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:30 +msgid "" +"Alternative measures can be selected to track where the most time is spent " +"at different points in the workflow. To change the measures used for the " +"report that is currently displayed, or to add more, click the " +":guilabel:`Measures` button, and select one or more options from the drop-" +"down menu:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:35 +msgid "" +":guilabel:`Average Hours to Respond`: average number of working hours " +"between a message sent from the customer and the response from the support " +"team. *This is does not include messages sent when the ticket was in a " +"folded stage*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:38 +msgid "" +":guilabel:`Hours Open`: number of hours between the date the ticket was " +"created and the closed date. If there is no closed date on the ticket, the " +"current date is used. **This measure is not specific to working hours**" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:41 +msgid "" +":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. " +"*This measure is only available if Timesheets are enabled on a team, and the" +" current user has the access rights to view them*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:44 +msgid "" +":guilabel:`Hours to Assign`: number of working hours between the date on " +"which the ticket was created and when it was assigned to a team member" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:46 +msgid "" +":guilabel:`Hours to Close`: number of working hours between the date on " +"which the ticket was created and the date it was closed" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:48 +msgid "" +":guilabel:`Hours to First Response`: number of working hours between the " +"date on which the ticket was received and the date one which the first " +"message was sent. *This does not include email sent automatically when a " +"ticket reaches a stage*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:51 +msgid "" +":guilabel:`Hours to SLA Deadline`: number of working hours remaining to " +"reach the last :abbr:`SLA (Service Level Agreement)` deadline on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:53 +msgid "" +":guilabel:`Rating /5`: number valued assigned to the rating received from a " +"customer (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:55 +#: ../../content/applications/services/helpdesk/overview/reports.rst:99 +msgid ":guilabel:`Count`: number of tickets in total" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:58 +msgid "" +"*Working hours* are calculated based on the default working calendar. To " +"view or change the working calendar, go to the :menuselection:`Settings` " +"application and select :menuselection:`Employees --> Company Working Hours`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:63 +msgid "SLA Status Analysis" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:65 +msgid "" +"The *SLA Status Analysis* report (:menuselection:`Helpdesk --> Reporting -->" +" SLA Status Analysis`) tracks how quickly an SLA (Service Level Agreement) " +"is fulfilled, as well as the success rate of individual policies." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:69 +msgid "" +"By default, this report is filtered to show the number of :abbr:`SLAs " +"(Service Level Agreements)` failed, as well as the failure rate over the " +"last 30 days, grouped by team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of Group by options of Ticket Analysis report." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:76 +msgid "" +"To change the measures used for the report that is currently displayed, or " +"to add more, click the :guilabel:`Measures` button, and select one or more " +"options from the drop-down menu:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:79 +msgid "" +":guilabel:`% of Failed SLA`: percentage of tickets that have failed at least" +" one :abbr:`SLA (Service Level Agreement)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:81 +msgid "" +":guilabel:`% of SLA in Progress`: percentage of tickets that have at least " +"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not " +"failed any :abbr:`SLAs (Service Level Agreements)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:84 +msgid "" +":guilabel:`% of Successful SLA`: percentage of tickets where all :abbr:`SLAs" +" (Service Level Agreements)` have been successful" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:86 +msgid "" +":guilabel:`Number of SLA Failed`: number of tickets that have failed at " +"least one :abbr:`SLA (Service Level Agreement)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:88 +msgid "" +":guilabel:`Number of SLA Successful`: number of tickets where all " +":abbr:`SLAs (Service Level Agreements)` have been successful" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:90 +msgid "" +":guilabel:`Number of SLA in Progress`: number of tickets that have at least " +"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not " +"failed any :abbr:`SLAs (Service Level Agreements)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:93 +msgid "" +":guilabel:`Working Hours to Assign`: number of working hours between the " +"date on which the ticket was created and when it was assigned to a team " +"member" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:95 +msgid "" +":guilabel:`Working Hours to Close`: number of working hours between the date" +" on which the ticket was created and the date it was closed" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:97 +msgid "" +":guilabel:`Working Hours to Reach SLA`: number of working hours between the " +"date on which the ticket was created and the date the :abbr:`SLA (Service " +"Level Agreement)` was satisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:102 +msgid "" +"To see the number of tickets that were able to achieve the stated :abbr:`SLA" +" (Service Level Agreement)` objectives, and track the amount of time it took" +" to achieve those objectives, click :menuselection:`Measures --> Number of " +"SLA Successful` and :menuselection:`Measures --> Working Hours to Reach " +"SLA`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:107 +msgid "" +"To sort these results by the team members assigned to the tickets, select " +":menuselection:`Total --> Assigned to`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:111 +msgid "" +":doc:`Service Level Agreements (SLA) " +"`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:114 +msgid "Customer Ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:116 +msgid "" +"The *Customer Ratings* report (:menuselection:`Helpdesk --> Reporting -- " +"Customer Ratings`) displays an overview of the ratings received on " +"individual support tickets, as well as any additional comments submitted " +"with the rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the kanban display in the Customer Ratings report." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:124 +msgid "" +"Click on an individual rating to see additional details about the rating " +"submitted by the customer, including a link to the original ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the details of an individual customer rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:132 +msgid "" +"On the rating's details page, select the :guilabel:`Visible Internally Only`" +" option to hide the rating from the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:135 +msgid "" +"The *Customer Ratings* report is displayed in a kanban view by default, but " +"can also be displayed in graph, list, or pivot view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:139 +msgid ":doc:`Ratings `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:142 +msgid "View and filter options" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:144 +msgid "" +"On any Odoo report, the view and filter options vary, depending on what data" +" is being analyzed, measured, and grouped. See below for additional " +"information on the available views for the *Helpdesk* reports." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:149 +msgid "" +"Only one measure may be selected at a time for graphs, but pivot tables can " +"include multiple measures." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:153 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:155 +msgid "" +"The *pivot* view presents data in an interactive manner. All three " +"*Helpdesk* reports are available in pivot view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:158 +msgid "" +"The pivot view can be accessed on any report by selecting the " +":guilabel:`grid icon` at the top right of the screen." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the SLA status analysis report in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:165 +msgid "" +"To add a group to a row or column to the pivot view, click the :guilabel:`➕ " +"(plus sign)` next to :guilabel:`Total`, and then select one of the groups. " +"To remove one, click the :guilabel:`➖ (minus sign)` and de-select the " +"appropriate option." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:170 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:172 +msgid "" +"The *graph* view presents data in either a *bar*, *line*, or *pie* chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:174 +msgid "" +"Switch to the graph view by selecting the :guilabel:`line chart icon` at the" +" top right of the screen. To switch between the different charts, select the" +" *related icon* at the top left of the chart, while in graph view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:180 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the SLA status analysis report in bar view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:186 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the Customer Ratings report in line view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:192 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the Ticket analysis report in pie chart view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:199 +msgid "" +"Both the *bar chart* and *line chart* can utilize the *stacked* view option." +" This presents two (or more) groups of data on top of each other, instead of" +" next to each other, making it easier to compare data." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:204 +msgid "Save and share a favorite search" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:206 +msgid "" +"The *Favorites* feature found on *Helpdesk* reports allows users to save " +"their most commonly used filters without having to reconstruct them every " +"time they are needed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:209 +msgid "" +"To create and save new *Favorites* on a report, follow the steps below:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:211 +msgid "" +"Set the necessary parameters using the :guilabel:`Filters`, :guilabel:`Group" +" By` and :guilabel:`Measures` options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:213 +msgid "Click :menuselection:`Favorites --> Save current search`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:214 +msgid "Rename the search." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:215 +msgid "" +"Select :guilabel:`Use by default` to have these filter settings " +"automatically displayed when the report is opened. Otherwise, leave it " +"blank." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:217 +msgid "" +"Select :guilabel:`Share with all users` to make this filter available to all" +" other database users. If this box is not checked, it will only be available" +" to the user who creates it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:219 +msgid "Click :guilabel:`Save` to preserve the configuration for future use." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the save favorites option in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:226 +msgid "" +":doc:`Start receiving tickets " +"`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:227 +msgid ":doc:`Odoo reporting `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:3 +msgid "Service Level Agreements (SLA)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:5 +msgid "" +"A Service Level Agreement (SLA) defines the level of service a customer can " +"expect from a supplier. SLAs provide a timeline that tells customers when " +"they can expect results, and keeps the support team on target." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:10 +msgid "Create a new SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:12 +msgid "" +"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to " +"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`." +" Select a team, scroll to the :guilabel:`Performance` section, and then " +"check the selection box next to :guilabel:`SLA Policies` to enable it for " +"that specific team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a team page in Helpdesk focusing on the SLA Policies setting" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:22 +msgid "" +"The value indicated next to the :guilabel:`Working Hours` field is used to " +"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. " +"By default, this is determined by the value set in the :guilabel:`Company " +"Working Hours` field under :menuselection:`Settings app --> Employees --> " +"Work Organization`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:27 +msgid "" +"To create a new policy, click the smart button on the team`s settings page " +"or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`, and " +"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a " +":guilabel:`Description` for the new policy, and proceed to fill out the form" +" using the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:33 +msgid "Define the criteria for an SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:35 +msgid "" +"The :guilabel:`Criteria` section is used to identify what tickets this " +"policy will be applied to. Fill out the following fields to adjust the " +"selection criteria:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:38 +msgid "" +":guilabel:`Team`: a policy can only be applied to one team. *This field is " +"required.*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:39 +msgid "" +":guilabel:`Priority`: the priority level for a ticket is identified by " +"selecting the number of stars representing the priority level on the kanban " +"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will " +"only be applied once the priority level has been updated on the ticket to " +"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is" +" made in this field, this policy will only apply to tickets marked as `Low " +"Priority` (zero stars)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:44 +msgid "" +":guilabel:`Types`: ticket types can be helpful when indicating when a ticket" +" is a customer question, that can be solved with a quick response, or an " +"issue, that may require additional investigation. Multiple ticket types can " +"be selected for this field. If no selection is made, this policy will apply " +"to all ticket types." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:48 +msgid "" +":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is " +"about. Multiple tags can be applied to a single ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:50 +msgid "" +":guilabel:`Customers`: individual contacts or companies may be selected in " +"this field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:51 +msgid "" +":guilabel:`Sales Order Items`: this field is available only if a team has " +"the *Timesheets* app enabled. This allows the ticket to tie directly to a " +"specific line on a sales order, which must be indicated on the ticket in the" +" :guilabel:`Sales Order Item` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:56 +msgid "" +"Unless otherwise indicated, multiple selections can be made for each field. " +"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one " +":guilabel:`Priority` level)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a blank SLA policy record" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:64 +msgid "Establish a target for an SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:66 +msgid "" +"The :guilabel:`Target` is the stage a ticket needs to reach, and the time " +"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service " +"Level Agreement)` policy. Any stage assigned to a team may be selected for " +"the :guilabel:`Reach Stage` field. Time spent in stages selected in " +":guilabel:`Excluding Stages` will not be included in the calculation of the " +":abbr:`SLA (Service Level Agreement)` deadline." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:73 +msgid "" +"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks " +"the working time before a ticket is completed, and would have `Solved` as " +"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level " +"Agreement)` was titled `2 Days to Start`, it tracks the working time before " +"work on a ticket has begun, and would have `In Progress` as the " +":guilabel:`Reach Stage`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:79 +msgid "Meeting SLA deadlines" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:81 +msgid "" +"Once it is determined that a ticket fits the criteria of an :abbr:`SLA " +"(Service Level Agreement)` policy, a deadline is calculated. The deadline is" +" based on the creation date of the ticket, and the targeted working hours. " +"The deadline is then added to the ticket, as well as a white tag indicating " +"the name of the :abbr:`SLA (Service Level Agreement)` applied." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "" +"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo" +" Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:91 +msgid "" +"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level " +"Agreement)`, the earliest occurring deadline will be displayed on the " +"ticket. Once that deadline has passed, the next deadline will be displayed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:95 +msgid "" +"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the" +" :abbr:`SLA (Service Level Agreement)` tag turns green, and the " +":guilabel:`Deadline` field disappears from view on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:103 +msgid "" +"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket " +"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level " +"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level " +"Agreement)` has failed, the red tag will stay on the ticket, even after the " +"ticket is moved to the :guilabel:`Reach Stage`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "" +"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:113 +msgid "Analyzing SLA performance" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:115 +msgid "" +"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA " +"(Service Level Agreement)` is fulfilled, as well as the success rate of " +"individual policies. Navigate to the report and corresponding pivot table by" +" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:121 +msgid "Using the Pivot view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:123 +msgid "" +"By default, the report is displayed in a :guilabel:`Pivot` view, and is " +"filtered to show the number of SLAs failed and the failure rate over the " +"last 30 days, grouped by team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of the SLA status analysis report in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:130 +msgid "" +"To add the number of SLAs passed or in progress, click the " +":guilabel:`Measures` button to reveal a drop-down menu of reporting " +"criteria, and choose from the options available based on the measurements " +"preferred. Whenever a measurement is picked, a check mark will appear in the" +" drop-down menu to indicate that that measurement is included, and a " +"corresponding new column will emerge in the pivot table to show the relevant" +" calculations." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:136 +msgid "" +"To add a group to a row or column, click the plus :guilabel:` + ` button " +"next to :guilabel:`Total`, and then select one of the groups. To remove one," +" click the minus :guilabel:` - ` button and deselect." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:141 +msgid "Using the Graph view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:143 +msgid "" +"The :guilabel:`Status Analysis` report can also be viewed as a " +":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between " +"these views by selecting the appropriate icon at the top of the chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:149 +msgid "Bar Chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in bar view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:155 +msgid "Line Chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in line view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:161 +msgid "Pie Chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in pie chart view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:168 +msgid "" +"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed " +":guilabel:`Stacked`. This presents two or more groups to appear on top of " +"each other instead of next to each other, making it easier to compare data." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:173 +msgid "Using the Cohort view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:175 +msgid "" +"The :guilabel:`Cohort` view is used to track the changes in data over a " +"period of time. To display the :guilabel:`Status Analysis` report in a " +":guilabel:`Cohort` view, click the icon in the top right corner above the " +"chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of the SLA status analysis report in cohort view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:184 +msgid ":ref:`Reporting views `" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:185 +msgid "" +":doc:`Allow customers to close their tickets " +"`" +msgstr "" + +#: ../../content/applications/services/project.rst:8 +msgid "Project" +msgstr "" + +#: ../../content/applications/services/project.rst:10 +msgid "" +"Odoo Project is a tool to manage your ongoing projects. Schedule tasks, " +"assign activities to coworkers, and keep track of each project's " +"profitability." +msgstr "" + +#: ../../content/applications/services/project.rst:14 +#: ../../content/applications/services/timesheets.rst:11 +msgid "" +"`Odoo Tutorials: Project and Timesheets " +"`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:3 +msgid "Project management" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:5 +msgid "" +"Odoo Project uses the **Kanban** project management system. This means all " +"projects are broken down into tasks, which are categorized on a whiteboard " +"according to what production phase they are in." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:8 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:10 +msgid "" +"The word **Kanban** comes from Japanese and refers to the \"visual board\" " +"management method." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:13 +msgid "" +"`Odoo Tutorials: Kanban Project Management " +"`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:19 +msgid "" +"Open the **Project** app and click :guilabel:`Create` to start a new " +"project. Enter a :guilabel:`Name` for your project and click " +":guilabel:`Create Project`." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:22 +msgid "" +"You can customize your existing **projects** from the dashboard by clicking " +"the drop-down toggle button (:guilabel:`⋮`) on your project's **card**." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst-1 +msgid "Project card" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:29 +msgid "This enables a new menu divided into four parts:" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:31 +msgid "" +":guilabel:`View`: see an overview of your project's components, such as its " +":guilabel:`Tasks`, :guilabel:`Milestones` and :guilabel:`Project Updates`. " +"Depending on which apps you have activated, more options may be available, " +"such as :guilabel:`Documents`. All uploaded files can be found under this " +"menu, as well as in the **Documents** app, under :guilabel:`Projects`;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:35 +msgid "" +":guilabel:`Reporting`: analyze your project's progress and profitability " +"through graphics and statistics;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:37 +msgid "" +"**Color**: make a line of color appear on the left side of the card so that " +"your project is more recognizable;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:39 +msgid ":guilabel:`Settings`: you can change the following:" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:41 +msgid "the :guilabel:`Name` of the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:42 +msgid "the :guilabel:`Name of the tasks` found under that project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:43 +msgid "the :guilabel:`Customer` for whom the project is intended;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:44 +msgid "the :guilabel:`Tags` used for filtering;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:45 +msgid "the :guilabel:`Company` responsible for the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:46 +msgid "the employee designated as :guilabel:`Project Manager`;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:47 +msgid "the :guilabel:`Planned Date` of the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:48 +msgid "the total :guilabel:`Allocated Hours` for that project." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:50 +msgid "" +"Additionally, you can mark the project as :guilabel:`Favorite`, allowing you" +" to find it using the :guilabel:`My Favorites` filter on the Kanban view;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst-1 +msgid "Project settings" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:58 +msgid "" +"`Odoo Tutorials: Customize projects " +"`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:61 +msgid "" +"Further settings are available under the :guilabel:`Settings` tab. Most of " +"them are *only* available depending on the activated apps." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:65 +msgid "Scheduling activities" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:67 +msgid "" +"You can schedule **activities** (ex. :guilabel:`Call`, :guilabel:`Meeting`, " +"etc.) per project by clicking on the **clock** icon on a project. Doing so " +"opens a list with already scheduled activities and allows planning **new** " +"activities by clicking :guilabel:`+ Schedule an activity`. On the pop-up " +"window, select the :guilabel:`Activity Type`, enter a :guilabel:`Summary` " +"for that activity, a :guilabel:`Due Date`, and assign it to an employee. " +"According to the :guilabel:`Activity Type`, you may have **additional " +"options** available." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:75 +msgid "" +"If an activity is **already** scheduled, the icon may change to a **phone**," +" **group of people**, or other." +msgstr "" + +#: ../../content/applications/services/project/tasks.rst:5 +msgid "Tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:3 +msgid "Create Project's Tasks from an Email Alias" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:5 +msgid "" +"When you already have an email address that customers know from the top of " +"their heads, changing it is the last thing you want to do. Instead, link " +"that address to your project and transform those conversations into " +"structured work. It automatically creates a task in the first stage of a " +"project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:11 +msgid "Set up an incoming email server" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:14 +msgid "" +"On the *Settings* application, enable *External Email Servers* and define " +"the incoming email alias you would like to use." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:15 +msgid "" +"**For more information**: " +":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:18 +msgid "Configure the email alias in your project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:22 +msgid "" +"Now that you have the incoming email server set up, go to " +":menuselection:`Project --> Configuration --> Projects --> Edit`. Under the " +"*Emails* tab, define the wanted email alias and choose the policy to receive" +" a message." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:23 +msgid "In addition, you can now directly set it when creating a new project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "" +"In the settings of your project, define the emails alias under the tab email" +" in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:30 +msgid "" +"All the recipients of the email (To/Cc/Bcc) are automatically added as " +"followers of the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:32 +msgid "The email can be seen under the name of your project on the dashboard." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:3 +msgid "Recurring tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:5 +msgid "" +"When handling a project, the same task often needs to be performed several " +"times: for example, weekly meetings or status reports. The **recurring " +"tasks** feature allows you to automate the creation of those tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:10 +msgid "" +"`Odoo Tutorials: Recurring tasks " +"`_" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:15 +msgid "" +"To enable recurring tasks, go to :menuselection:`Project --> Configuration " +"--> Settings`, then activate :guilabel:`Recurring Tasks`, and press " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:18 +msgid "" +"Recurring tasks are now activated on all existing projects. The feature can " +"be deactivated on an individual project by clicking the drop-down menu " +"button :guilabel:`⋮` next to the project name, then going to " +":menuselection:`Settings --> Settings --> Task Management` and disabling " +":guilabel:`Recurring Tasks`." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:24 +msgid "Set up task recurrence" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:26 +msgid "" +"In an existing task, press the :guilabel:`Recurrent` button next to the " +":guilabel:`Planned date`. Then, configure :guilabel:`Repeat Every` field " +"according to your needs." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:29 +msgid "" +"A new task in recurrence will be created once either of this conditions is " +"met: - Previous task in recurrence has been closed. - On the day of the " +"planned recurrence." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:33 +msgid "" +"The new task is created on your project dashboard with the following " +"configuration:" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:35 +msgid "" +":guilabel:`Stage`: first stage of the project dashboard (:guilabel:`New` or " +"equivalent);" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36 +msgid "" +":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, " +":guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: copied from " +"the original task;" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:38 +msgid "" +":guilabel:`Milestones`, :guilabel:`Deadline`, :guilabel:`Timesheets`, " +":guilabel:`Chatter`, :guilabel:`Activities`, :guilabel:`Subtasks`: those " +"fields are not copied;" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:41 +msgid "" +"A **smart button** on the task displays the total number of existing " +"recurrences." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:44 +msgid "Edit or stop task recurrence" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:46 +msgid "" +"**To edit** the recurrence, open the last task in recurrence. Any changes " +"made on the task will be applied to the tasks that will be created in the " +"future." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:49 +msgid "" +"**To stop** the recurrence, open the last task in recurrence and press the " +":guilabel:`Recurrent` button next to the :guilabel:`Planned date`." +msgstr "" + +#: ../../content/applications/services/timesheets.rst:8 +msgid "Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:3 +msgid "Create Timesheets upon Time Off Validation" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:5 +msgid "" +"Odoo automatically timesheets on project/tasks upon time off requests. This " +"allows for better overall control over the validation of timesheets, as it " +"does not leave place for forgetfulness and questions after hours that have " +"not been timesheeted by the employee." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:9 +msgid "" +"Activate the :ref:`developer mode `, go to *Timesheets*, and" +" change the *Project* and *Task* set by default, if you like." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of Timesheets setting enabling the feature record time off in Odoo " +"Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:16 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select" +" or create the needed type, and decide if you would like the requests to be " +"validated or not." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of a time off types form emphasizing the time off requests and timesheets section in\n" +"Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:26 +msgid "" +"Now, once the employee has requested his time off and the request has been " +"validated (or not, depending on the setting chosen), the time is " +"automatically allocated on *Timesheets*, under the respective project and " +"task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:27 +msgid "" +"On the example below, the user requested *Paid Time off* from July 13th to " +"15th." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the time off request form in Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:33 +msgid "" +"Considering that validation is not required, the requested time off is " +"automatically displayed in *Timesheets*. If validation is necessary, the " +"time is automatically allocated after the responsible person for validating " +"does it so." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"Video of timesheets emphasizing the requested time off from the employee in " +"Odoo Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:41 +msgid "" +"Click on the magnifying glass, hovering over the concerned cell, to access " +"all the aggregated data on that cell (day), and see details regarding the " +"project/task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the details of a project/task in Odoo Timeheets" +msgstr "" diff --git a/locale/hi/LC_MESSAGES/settings.po b/locale/hi/LC_MESSAGES/settings.po new file mode 100644 index 000000000..ccdac3749 --- /dev/null +++ b/locale/hi/LC_MESSAGES/settings.po @@ -0,0 +1,194 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 14.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-05-18 07:12+0200\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/settings.rst:3 +msgid "Settings" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:6 +msgid "Users and Features" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:8 +msgid "" +"As the administrator of your database, you are responsible for its usage. " +"This includes the Apps you install as well as the number of users currently " +"in use." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:12 +msgid "" +"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) " +"but it is *not* a smartphone. You should apply caution when adding/removing " +"features (especially Apps) on your database since this may impact your " +"subscription amount significantly (or switch you from a free account to a " +"paying one on our online platform)." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:18 +msgid "" +"This page contains some information as to how you can manage your Odoo " +"instances. Before carrying any of these procedures, we **strongly** advise " +"to test them on a duplicate of your database first. That way, if something " +"goes wrong, your day-to-day business is not impacted." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:23 +msgid "" +"You can find guides on how to duplicate your databases both for :ref:`online" +" ` and :ref:`on premise ` " +"installations." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:27 +msgid "" +"If you have questions about the content of this page or if you encounter an " +"issue while carrying out these procedures, please contact us through our " +"`support form `__." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:33 +msgid "Deactivating Users" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:35 +msgid "" +"Make sure you have sufficient **administrative rights** if you want to " +"change the status of any of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:38 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:42 +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|settings|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:42 +msgid "|browse_users|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:45 +msgid "You'll then see the list of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:50 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:55 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:63 +msgid "The user is now deactivated." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:65 +msgid "**Never** deactivate the main user (*admin*)" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:68 +msgid "Uninstalling Apps" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:70 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:74 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|browse_apps|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:82 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:89 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:96 +msgid "" +"Last, after having checked the warning message (if any), click **Confirm**." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:101 +msgid "You have finished uninstalling your application." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:104 +msgid "Good to know" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:106 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:112 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:119 +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/hi/LC_MESSAGES/websites.po b/locale/hi/LC_MESSAGES/websites.po new file mode 100644 index 000000000..8a6fe44dc --- /dev/null +++ b/locale/hi/LC_MESSAGES/websites.po @@ -0,0 +1,8828 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 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 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Hindi (https://app.transifex.com/odoo/teams/41243/hi/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: hi\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: ../../content/applications/websites.rst:5 +msgid "Websites" +msgstr "" + +#: ../../content/applications/websites/blog.rst:3 +msgid "Blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:5 +msgid "" +"**Odoo Blog** allows you to create and manage blog posts on your website to " +"engage your audience and build a community." +msgstr "" + +#: ../../content/applications/websites/blog.rst:9 +msgid "" +"If the Blog module is not yet installed, click :guilabel:`+New` on the " +"website builder, select :guilabel:`Blog Post`, and click " +":guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:13 +msgid "Creating a blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:15 +msgid "" +"To create or edit a blog, go to :menuselection:`Website --> Configuration " +"--> Blogs: Blogs`. Click :guilabel:`New`, and enter the :guilabel:`Blog " +"Name` and the :guilabel:`Blog Subtitle`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:18 +msgid "" +"The :guilabel:`Blog` menu item is added to your website's menu the first " +"time you create a blog and gathers all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:22 +msgid "Adding a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:24 +msgid "" +"Go to your website, click :guilabel:`+New` in the top-right corner, and " +"select :guilabel:`Blog Post`. In the pop-up, **select the blog** where the " +"post should appear, write the post's :guilabel:`Title`, and " +":guilabel:`Save`. You can then write the post's content and customize the " +"page using the website builder." +msgstr "" + +#: ../../content/applications/websites/blog.rst:30 +msgid "" +"Illustrate your articles with copyright-free images from :doc:`Unsplash " +"`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:32 +msgid "Type `/` in the text editor to format and add elements to your text." +msgstr "" + +#: ../../content/applications/websites/blog.rst:35 +msgid "" +"Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right " +"corner to publish your post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:39 +msgid "Using tags" +msgstr "" + +#: ../../content/applications/websites/blog.rst:41 +msgid "" +"Tags let visitors filter all posts sharing the same tag. By default, they " +"are displayed at the bottom of posts, but can also be displayed on the " +"blog's main page. To do so, click :menuselection:`Edit --> Customize` and " +"enable the :guilabel:`Sidebar`. By default, the sidebar's :guilabel:`Tags " +"List` is enabled." +msgstr "" + +#: ../../content/applications/websites/blog.rst:46 +msgid "" +"To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: " +"Tags` and click :guilabel:`New`. Fill in the:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:49 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/websites/blog.rst:50 +msgid "" +":guilabel:`Category`: tag categories let you group tags displayed on the " +"sidebar by theme." +msgstr "" + +#: ../../content/applications/websites/blog.rst:51 +msgid "" +":guilabel:`Used in`: to apply the tag to existing blog posts, click " +":guilabel:`Add a line`, select the posts, and click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:54 +msgid "" +"You can add and create tags directly from posts by clicking " +":menuselection:`Edit --> Customize` and select the post's cover. Under " +":guilabel:`Tags`, click :guilabel:`Choose a record...`, and select or create" +" a tag." +msgstr "" + +#: ../../content/applications/websites/blog.rst-1 +msgid "Adding a tag to a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:62 +msgid "" +"To manage tag categories, go to :menuselection:`Website --> Configuration " +"--> Blogs: Tag Categories`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:66 +msgid "Customizing blog homepages" +msgstr "" + +#: ../../content/applications/websites/blog.rst:68 +msgid "" +"Customize the content of blog homepages by opening a blog homepage and " +"clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:72 +msgid "Settings apply to **all** blogs homepages." +msgstr "" + +#: ../../content/applications/websites/blog.rst:74 +msgid "" +":guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of " +"the latest post on the top banner, while :guilabel:`Drop Zone for Building " +"Blocks` removes the top banner and lets you use any building block instead." +msgstr "" + +#: ../../content/applications/websites/blog.rst:78 +msgid "" +":guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or " +":guilabel:`List`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:80 +msgid ":guilabel:`Cards`: adds a *card* effect." +msgstr "" + +#: ../../content/applications/websites/blog.rst:81 +msgid ":guilabel:`Increase Readability`: improves the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:83 +msgid "" +":guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` " +"section." +msgstr "" + +#: ../../content/applications/websites/blog.rst:85 +msgid "" +":guilabel:`Archives`: allows visitors to select a month and filter all posts" +" created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:87 +msgid "" +":guilabel:`Follow Us`: displays links to your social media networks. They " +"can be configured using the Social Media building block somewhere on your " +"website." +msgstr "" + +#: ../../content/applications/websites/blog.rst:89 +msgid "" +":guilabel:`Tags List`: displays all tags related to a blog. Visitors can " +"select a tag to filter all related posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:92 +msgid "" +":guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and " +":guilabel:`No Cover` hides them." +msgstr "" + +#: ../../content/applications/websites/blog.rst:95 +msgid ":guilabel:`Author`: displays the posts' authors." +msgstr "" + +#: ../../content/applications/websites/blog.rst:96 +msgid "" +":guilabel:`Comments/Views Stats`: displays the posts' number of comments and" +" views." +msgstr "" + +#: ../../content/applications/websites/blog.rst:97 +msgid "" +":guilabel:`Teaser & Tags`: displays the posts' first sentences and tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:100 +msgid "Customizing blog posts" +msgstr "" + +#: ../../content/applications/websites/blog.rst:102 +msgid "" +"Customize posts by opening a blog post and clicking :menuselection:`Edit -->" +" Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:105 +msgid "Settings apply to **all** posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:107 +msgid "" +":guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside" +" the cover image, and :guilabel:`Title above Cover` displays it above." +msgstr "" + +#: ../../content/applications/websites/blog.rst:110 +msgid ":guilabel:`Increase Readability`: increases the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:112 +msgid "" +":guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional " +"options:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:114 +msgid "" +":guilabel:`Archive`: allows visitors to select a month and filter all posts " +"created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:116 +msgid ":guilabel:`Author`: displays the post's author and creation date." +msgstr "" + +#: ../../content/applications/websites/blog.rst:117 +msgid ":guilabel:`Blog List`: displays links to all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:118 +msgid "" +":guilabel:`Share Links`: displays share buttons to several social networks." +msgstr "" + +#: ../../content/applications/websites/blog.rst:119 +msgid ":guilabel:`Tags`: displays the post's tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:121 +msgid ":guilabel:`Breadcrumb`: displays the path to the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:123 +msgid "" +":guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the " +"bottom, and :guilabel:`Comments` enable visitors to comment on the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:126 +msgid "" +":guilabel:`Select To Tweet`: visitors are offered to tweet the text they " +"select." +msgstr "" + +#: ../../content/applications/websites/blog.rst:129 +msgid "" +"Use :ref:`Plausible ` to keep track of the " +"traffic on your blog." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:8 +msgid "eCommerce" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:10 +msgid "" +"Run a modern open-source online store with Odoo eCommerce. Learn how to sell" +" online, promote products and increase your average cart sizes." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:14 +#: ../../content/applications/websites/website.rst:14 +msgid "" +"Odoo offers a :ref:`free custom domain name ` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:19 +msgid ":doc:`Website Documentation `" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:20 +#: ../../content/applications/websites/website.rst:20 +msgid "`Odoo Tutorials: Website `_" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:21 +#: ../../content/applications/websites/website.rst:21 +msgid "" +"`Odoo Tutorials: eCommerce `_" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping.rst:5 +msgid "Checkout, payment, and shipping" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:3 +msgid "Add to cart" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:5 +msgid "" +"The :guilabel:`Add to Cart` button can be customized in multiple ways. You " +"can:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:7 +msgid "" +"Choose on which page customers go after clicking the 'Add to Cart' button;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:8 +msgid "Hide the 'Add to Cart' button to prevent sales;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:9 +msgid "" +"Add a 'Buy Now' button to skip the cart step and lead customers straight to " +"checkout;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:10 +msgid "Create additional 'Add to Cart / Buy Now' buttons;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:11 +msgid "Add an 'Order Again' button to the customer portal." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:14 +msgid ":doc:`checkout`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:17 +msgid "'Add to Cart' action customization" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:19 +msgid "" +"When customers click on the :guilabel:`Add to Cart` button, the product is " +"added to their cart, and customers remain **by default** on the product's " +"page. However, customers can either immediately be **redirected** to their " +"cart, or given the choice on what to do through a **dialog box**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:23 +msgid "" +"To change the default behavior, go to :menuselection:`Website --> " +"Configuration --> Settings`. Under the :guilabel:`Shop - Checkout Process` " +"section, look for :guilabel:`Add to Cart` and select one of the options." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:28 +msgid "" +"If a product has :doc:`optional products " +"<../managing_products/cross_upselling>`, the **dialog box** will always " +"appear." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:32 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:20 +msgid ":doc:`../managing_products/catalog`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:37 +msgid "Replace 'Add to Cart' button by 'Contact Us' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:39 +msgid "" +"You can replace the 'Add to Cart' button with a 'Contact Us' button which " +"redirects users to the URL of your choice." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:43 +msgid "" +"Hiding the :guilabel:`Add to Cart` button is often used by B2B eCommerces " +"that need to restrict purchases only to :ref:`customers with an account " +"`, but still want to display an online product catalog for " +"those without." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:47 +msgid "" +"To do so, go to :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Products` and tick :guilabel:`Prevent Sale of Zero Priced Product`. " +"This creates a new :guilabel:`Button url` field where you can enter the " +"**redirect URL** to be used. Then, set the price of the product to `0.00` " +"either from the **product's template**, or from a :doc:`pricelist " +"<../../../sales/sales/products_prices/prices/pricing>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Contact us button on product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:58 +msgid "" +"The 'Contact Us' button and '*Not Available For Sale*' text can both be " +"modified using the **website builder** on the product's page " +"(:menuselection:`Edit --> Customize`) by clicking on them." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:63 +msgid "Customizable 'Add to Cart' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:65 +msgid "" +"You can also create a customizable 'Add to Cart' button and link it to a " +"specific product. The **customized button** can be added on any page of the " +"website as an **inner content** building block, and is an *additional* " +"button to the regular :guilabel:`Add to Cart` button." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:69 +msgid "" +"To add it, go on the :guilabel:`Shop` page of your choice, click " +":menuselection:`Edit --> Blocks` and place the building block. Once placed, " +"you have the following options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:72 +msgid "" +":guilabel:`Product`: select the product to link the button with. Selecting a" +" product renders the :guilabel:`Action` field available;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:74 +msgid "" +":guilabel:`Action`: choose if the button should :guilabel:`Add to Cart` or " +":guilabel:`Buy Now` (instant checkout)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:84 +msgid "'Buy Now' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:86 +msgid "" +"You can enable the 'Buy Now' button to instantly take the customer to " +"**checkout** instead of adding the product to the cart. The :guilabel:`Buy " +"Now` button is an *additional* button and does not replace the " +":guilabel:`Add to Cart` button. To enable it, go to :menuselection:`Website " +"--> Configuration --> Settings --> Shop - Checkout Process` and tick " +":guilabel:`Buy Now`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Buy Now button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:97 +msgid "Re-order from portal" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:99 +msgid "" +"Customers have the possibility to **re-order** items from **previous sales " +"orders** on the customer portal. To do so, go to :menuselection:`Website -->" +" Configuration --> Settings --> Shop - Checkout Process` and enable " +":guilabel:`Re-order From Portal`. Customers can find the :guilabel:`Order " +"Again` button on their **sales order** from the **customer portal**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Re-order button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:3 +msgid "Checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:5 +msgid "" +"You can customize the **checkout steps**, add more content using the " +"**website builder**, and enable additional features such as **express " +"checkout** and **sign in/up at checkout**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:8 +msgid "" +"You can use **building blocks** to add content at any step of the checkout " +"process. To do so, from any **checkout page**, go to :menuselection:`Edit " +"--> Blocks`, and drag and drop **building blocks** to the page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:13 +msgid "" +"Note that content added through building blocks is **specific** to each " +"step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:16 +msgid "Checkout steps" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:19 +msgid "Review order: promo code (and subtotal)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:21 +msgid "" +"If you have enabled :guilabel:`Discounts, Loyalty, & Gift Card` in the " +"settings (:menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products`), you can enable the :guilabel:`Promo Code` field " +"(:menuselection:`Edit --> Customize`) from any checkout page. Customers can " +"then redeem gift cards and promotional codes at the :guilabel:`Review Order`" +" step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:26 +msgid "" +"Furthermore, you can display the subtotal with discounts applied by enabling" +" :guilabel:`Show Discount in Subtotal`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Subtotal discount" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:34 +msgid "Address: B2B fields" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:36 +msgid "" +"Optional :guilabel:`TIN/VAT` and :guilabel:`Company Name` fields can be " +"added to the :guilabel:`Billing Address` form for B2B customers, at the " +":guilabel:`Address` step. To add the fields, go to :menuselection:`Edit --> " +"Customize` from any checkout page, and enable :guilabel:`Show B2B fields`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:42 +msgid "Request extra info (additional step)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:44 +msgid "" +"You can request :guilabel:`Extra Info` from the customer by adding an " +":guilabel:`Extra Info` step between the :guilabel:`Address` and " +":guilabel:`Confirm Order` steps. To do so, go to :menuselection:`Edit --> " +"Customize` from any checkout page, and enable :guilabel:`Extra Step Option`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:53 +msgid "" +"The :guilabel:`Extra Info` step is an online form linked to the quotation or" +" sales order of the customer. The information added during that step can be " +"found on the quotation or sales order of the customer from the back end, in " +"the **Sales** app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:57 +msgid "" +"When enabled, you can remove, add, and modify fields of the form by clicking" +" on :guilabel:`Edit` in the top-right corner, and then clicking on any of " +"the form's fields. All customization options, as well as the :guilabel:`+ " +"Field` button to add new fields, are available at the bottom of the " +":guilabel:`Customize` menu under the :guilabel:`Field` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Online form customization" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:67 +msgid "Confirm order: terms and conditions" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:69 +msgid "" +"You can ask customers to agree to the :guilabel:`Terms & Conditions` in " +"order to confirm their order by enabling :guilabel:`Accept Terms & " +"Conditions` under :menuselection:`Edit --> Customize` on any checkout page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Terms and conditions" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:78 +msgid "Express checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:80 +msgid "" +"You can enable a :guilabel:`Buy Now` button on products' pages which " +"instantly takes the customer to the :guilabel:`Confirm Order` checkout page," +" instead of adding the product to the cart. To do so, go to " +":menuselection:`Website --> Configuration --> Settings --> Shop - Checkout " +"Process section` and tick :guilabel:`Buy Now`. Alternatively, the " +":guilabel:`Buy Now` button can also be enabled from any product's page by " +"going :menuselection:`Edit --> Customize`, in the :guilabel:`Cart` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:86 +msgid "" +"The button can be found next to the :guilabel:`Add to Cart` button on the " +"product's page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Buy now (express checkout) button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:93 +msgid ":ref:`Product page design: additional functions `" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:98 +msgid "Guest and signed-in checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:100 +msgid "" +"It is possible to introduce a **checkout policy** under which customers can " +"either checkout as **guests** or **signed-in users only**. Customers can " +"also checkout as guest, and **optionally sign up later** in order to track " +"their order, if enabled." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:104 +msgid "" +"To select a policy, go to :menuselection:`Website --> Configuration --> " +"Settings --> Shop - Checkout Process`. You can choose between:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:107 +msgid "" +":guilabel:`Optional`: allows guests to checkout and later register from the " +"**order confirmation** email to track their order;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:109 +msgid "" +":guilabel:`Disabled (buy as guest)`: customers can only checkout as guests;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:110 +msgid "" +":guilabel:`Mandatory (no guest checkout)`: customers can only checkout if " +"they have signed-in." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:113 +msgid ":doc:`../ecommerce_management/customer_accounts`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:114 +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:24 +msgid ":doc:`/applications/general/users/portal`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:117 +msgid "B2B access restriction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:119 +msgid "" +"If you wish to restrict checkout only to **selected B2B customers**, enable " +":guilabel:`Mandatory (no guest checkout)` and go to :menuselection:`Website " +"--> eCommerce --> Customers`. Select the customer you wish to **grant access" +" to**, click :menuselection:`Action --> Grant portal access`, and click " +":guilabel:`Grant Access`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:125 +msgid "" +"Settings are **website-specific**, which means you can set up a B2C website " +"allowing **guest** checkout, and another for B2B customers with **mandatory " +"sign-in**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:129 +msgid "" +"Users can only have one portal access per **email**. They *cannot* be " +"granted access to two different portals with the same **email address**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:133 +msgid "Shared customer accounts" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:135 +msgid "" +"If you enable :guilabel:`Shared Customer Accounts` under " +":menuselection:`Website --> Configuration --> Settings --> Privacy section`," +" you can allow or disallow access to *all* websites for one same account." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:3 +msgid "Payment providers" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:5 +msgid "" +"Odoo supports a multitude of online :doc:`payment providers " +"` for your website, allowing your " +"customers to pay with their preferred payment methods." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:10 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:55 +msgid ":doc:`/applications/sales/sales/products_prices/ewallets_giftcards`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:11 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:12 +msgid ":doc:`../checkout_payment_shipping/checkout`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:14 +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:94 +#: ../../content/applications/websites/website/configuration.rst:5 +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:24 +#: ../../content/applications/websites/website/reporting/link_tracker.rst:10 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:16 +msgid "" +"To set up payment providers on the eCommerce app, go to " +":menuselection:`Website --> Configuration --> Payment Providers`. From here," +" :guilabel:`Activate` the payment providers you wish to have available on " +"your shop, and configure them according to your needs." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:20 +msgid "" +"Alternatively, you can access **payment providers** via " +":menuselection:`Website --> Configuration --> Settings`. In the " +":guilabel:`Shop - Payment` section, you can :guilabel:`Configure SEPA Direct" +" Debit` if you wish to use it, as well as :guilabel:`View other providers`. " +"If you use the :guilabel:`Authorize.net` payment provider, the :ref:`Payment" +" Capture Method ` can be " +"configured in that same menu." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:27 +msgid "" +"If you are using :doc:`/applications/finance/payment_providers/paypal`, you " +"can also enable and configure it here." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:31 +msgid "Checkout payment options" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:33 +msgid "" +"Once activated, customers can choose the payment provider of their choice " +"during the **checkout process**, at the :guilabel:`Confirm Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst-1 +msgid "Payment provider selection at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:41 +msgid "eWallets and gift cards" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:43 +msgid "" +"When checking out, customers can pay with an eWallet or gift cards. To " +"enable these, go to :menuselection:`Website --> Configuration --> Settings`," +" and in the :guilabel:`Shop-Products` section, enable " +":menuselection:`Discounts, Loyalty & Gift Card`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:47 +msgid "" +"Once enabled, customers can enter their gift card **code** or pay with their" +" eWallet at the checkout step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst-1 +msgid "Enter gift card code to process checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:3 +msgid "Shipping methods" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:5 +msgid "" +"Depending on your shipping strategy, you have the choice to either use your " +":ref:`own shipping methods `, or use an integration " +"with an :ref:`existing shipping provider `." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:15 +msgid "Own shipping methods" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17 +msgid "" +"You can create your own custom shipping methods and define rules to compute " +"shipping costs. To do so, go to :menuselection:`Website --> Configuration " +"--> Shipping Methods`, and either select an **existing** shipping method, or" +" :guilabel:`Create` one. When creating a shipping method, you can choose " +"between :doc:`Fixed Price " +"`," +" :doc:`Based on Rules " +"`," +" and :guilabel:`Pickup in store`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26 +msgid "Pickup in store" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:28 +msgid "" +":guilabel:`Pickup in store` must first be **enabled** in the settings " +"(:menuselection:`Website --> Configuration --> Settings --> Shipping " +"section)` by checking :guilabel:`On Site Payments & Picking`. Once enabled, " +"you can select and :guilabel:`Customize Pickup Sites`. :guilabel:`Picking " +"sites` can be made **website-specific**, but are by default available for " +"*all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42 +msgid "Shipping providers" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:44 +msgid "" +"Another solution is to use one of the integrations with an existing shipping" +" provider. The advantage of using an integration is that delivery costs are " +"automatically computed based on each order as well as generating shipping " +"labels." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:204 +msgid "Website availability" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 +msgid "" +"Shipping methods can be made available on **specific** websites *only*, if " +"desired. To do so, go to :menuselection:`Website --> Configuration --> " +"Settings --> Shipping Methods`, and select the desired **shipping method**. " +"In the :guilabel:`Website` field, set the website you want the shipping " +"method to be restrained to. Leave the field **empty** for the method to be " +"available on *all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63 +msgid "Delivery method at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 +msgid "" +"Customers can choose the shipping method at the end of the checkout process," +" at the :guilabel:`Confirm Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst-1 +msgid "Delivery method choice at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management.rst:5 +msgid "eCommerce management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:3 +#: ../../content/applications/websites/website/configuration/multi_website.rst:130 +msgid "Customer accounts" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:5 +msgid "" +"Having customer accounts on an eCommerce allows customers to access all " +"their documents from a single place. To access their account, customers must" +" be **logged-in** on the eCommerce website, click on their **username** in " +"the top-right corner of the screen, and click :guilabel:`My Account`. From " +"there, customers can access their :guilabel:`quotations`, " +":guilabel:`orders`, :guilabel:`invoices`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst-1 +msgid "Customer account log-in" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:16 +msgid "" +"Customers can only have an account if the :ref:`sign in/up at checkout " +"` option allows for accounts creation." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:20 +msgid "" +"Similarly to the rest of the website, the customer account page can be " +"customized with **content blocks** and other features through the **website " +"builder**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:27 +msgid "Access restriction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:29 +msgid "" +"It is possible to allow or restrict the documents to which customers have " +"access through the website builder. Log in your **own** account with your " +"Odoo database credentials, and go to :menuselection:`Edit --> Customize`. " +"From the website builder menu, enable or disable the documents customers can" +" have access to." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst-1 +msgid "Documents to which customers have access to from their account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:39 +msgid "Multi-website account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:41 +msgid "" +"If you own multiple websites, you can make customer accounts available " +"across **all** websites. Then, the customer only needs one account. To do " +"so, go to :menuselection:`Website --> Configuration --> Settings --> Privacy" +" section`, and enable :guilabel:`Shared Customer Accounts`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:3 +msgid "Customer interaction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:5 +msgid "" +"Odoo offers many ways to interact with customers and for customers to " +"interact with your website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:10 +msgid "Product reviews" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:12 +msgid "" +"Customers can give a rating to your products. This is a great way to promote" +" your products or services since reviews can influence purchase processes. " +"To activate the **rating** feature, from your **shop page**, select a " +"product, go to :menuselection:`Edit --> Customize` and enable " +":guilabel:`Rating`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Rating of a product on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:22 +msgid "" +"Only portal users which purchased the product or service can leave ratings." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:25 +msgid "" +"Customer reviews can be hidden by clicking the :guilabel:`Visible` button " +"next to a published review." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:29 +msgid "Live chat" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:31 +msgid "" +"A chatbot is available and can simulate a human-like conversation with " +"website visitors via text messages in a chat box." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:35 +msgid ":doc:`../../livechat`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:36 +msgid ":doc:`../../livechat/ratings`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:37 +msgid ":doc:`../../livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:42 +msgid "Contact forms" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:45 +msgid "Helpdesk" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:47 +msgid "" +"Customers may need support after purchasing a product or subscribing to a " +"service. It is possible to create a **contact form**, which, when fulfilled," +" automatically creates a new ticket for your **support team**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Contact form to submit a ticket to the support team" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:55 +msgid "" +"To add a contact form, **create** a new page (:menuselection:`+ New --> " +"Page`) if necessary, and drag and drop a :guilabel:`Form` block from the " +":guilabel:`Dynamic Content` section onto the page. Once placed, click on the" +" form (while in :guilabel:`Edit` mode), and in the :guilabel:`Action` field," +" select :guilabel:`Create a Ticket`. You can then select to which " +":guilabel:`Helpdesk team` the ticket should be assigned." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Action field to create a task upon submitting a form" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:66 +msgid "Contact us" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:68 +msgid "" +"A 'Contact Us' page makes it easier for customers and prospects to contact " +"your company and get in touch." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:71 +msgid "" +"To have a 'Contact Us' page, create a new page (:menuselection:`+ New --> " +"Page`) if necessary, and click on :menuselection:`Edit --> Customize`. Then," +" drag and drop a :guilabel:`Form` block onto the page. Select the form and " +"define the action to be performed when submitted in the :guilabel:`Action` " +"field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:76 +msgid "" +"When clicking on a field, or when adding a new field (:guilabel:`+ Field`), " +"you can select its :guilabel:`Type`. This enables different options, such as" +" :guilabel:`Multiple Checkboxes`, which customers can use to indicate the " +"services they are interested in, for example." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Tags to be selected on the 'Contact Us' form" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "'Checkboxes' configuration settings" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:89 +msgid "Newsletter" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:91 +msgid "" +"Customers can get updates on your eCommerce activities by subscribing to a " +"newsletter. Visitors subscribing to the newsletter are automatically added " +"to the mailing list of the **Email Marketing** application. You can either " +"choose a newsletter **block**, a newsletter **popup**, or both." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:95 +msgid "" +"**Popup**: prompts up a newsletter box when visitors scroll down the page;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:96 +msgid "" +"**Block**: displays a field on the page where customers can sign up by " +"entering their email." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:98 +msgid "" +"The newsletter **block** can be configured according to different " +":guilabel:`Templates`. To do so, click the **block** while in " +":menuselection:`Edit --> Customize`, and select a :guilabel:`Template` in " +"the :guilabel:`Newsletter Block` section. There are **three** templates " +"available:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:102 +msgid "" +":guilabel:`Email Subscription`: visitors can sign up by email to the " +"newsletter, without any choice to the content. The content is defined in " +":menuselection:`Edit --> Customize` in the :guilabel:`Newsletter` field;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:105 +msgid "" +":guilabel:`SMS Subscription`: is the same as :guilabel:`Email Subscription`," +" but by SMS;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:106 +msgid "" +":guilabel:`Form Subscription`: allows adding several fields, as well as a " +"checkbox for the visitor to agree to the **GDPR policy** of your website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Form subscription configuration and settings" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:114 +msgid "" +"Alternatively, you can select :guilabel:`Subscribe to Newsletter` as " +":guilabel:`Action` when creating a :ref:`contact form `, " +"allowing for the same level of customization. Make sure to add a checkbox " +"stating visitors agree to be added to the mailing list." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:3 +msgid "Order handling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:5 +msgid "" +"When a customer orders on your eCommerce, there are **three** record types " +"required to be handle in Odoo:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:8 +msgid ":ref:`Sales orders `;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:9 +msgid ":ref:`Delivery orders `;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:10 +msgid ":ref:`Invoices & legal requirements `." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:15 +msgid "Sales orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:18 +msgid "Order and payment status" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:20 +msgid "" +"The first step when a customer adds a product to his cart is the creation of" +" a quotation. Orders can be managed either from the **Website** or " +":doc:`Sales ` app. eCommerce orders can " +"automatically be assigned to a specific sales team by going to " +":menuselection:`Website --> Configuration --> Settings`. In the **Shop - " +"Checkout Process** section, select a :guilabel:`Sales Team` or " +":guilabel:`Salesperson` to handle eCommerce orders." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst-1 +msgid "Assignment of online orders to a sales team or salesperson" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:30 +msgid "" +"Orders can be found under :menuselection:`Website --> eCommerce --> " +"Orders/Unpaid Orders`. Each order goes through a different status:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:33 +msgid "" +"**Quotation**: a new product is added to the cart, but the customer has " +"*not* gone through the checkout process yet;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:35 +msgid "" +"**Quotation sent**: the customer has gone through the checkout process and " +"confirmed the order, but the payment is not yet confirmed;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:37 +msgid "" +"**Order**: the customer has gone through the checkout process, confirmed the" +" order, and the payment is received." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst-1 +msgid "Statuses of eCommerce orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:45 +msgid "Abandoned cart" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:47 +msgid "" +"An **abandoned cart** represents an order for which the customer did **not " +"finish** the checkout confirmation process. For these orders, it is possible" +" to send an **email reminder** to the customer automatically. To enable that" +" feature, go to :menuselection:`Website --> Configuration --> Settings` and " +"in the :guilabel:`Email & Marketing` section, enable " +":guilabel:`Automatically send abandoned checkout emails`. Once enabled, you " +"can set the **time-lapse** after which the email is sent and customize the " +"**email template** used." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:55 +msgid "" +"For abandoned cart emails, the customer must either have entered their " +"contact details during the checkout process; or be logged-in when they added" +" the product to their cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:61 +msgid "Delivery orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:64 +msgid "Delivery flow" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:66 +msgid "" +"Once a quotation has been confirmed, a delivery order is automatically " +"created. The next step is to process this delivery." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:69 +msgid "" +"Packing eCommerce orders usually requires picking the product, preparing the" +" packaging, printing the shipping label(s) and shipping to the customer. " +"Depending on the number of orders, strategy, or resources, those steps can " +"be considered as one or multiple actions in Odoo." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:73 +msgid "" +"An automatic email can be sent to the customer when the transfer status in " +"Odoo is “done”. To do so, enable the feature in the settings of the " +":doc:`Inventory ` app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:78 +msgid "" +"If customers are allowed to pay when picking up their order in stores or by " +"wire transfer, the quotation is **not** be confirmed and the stock is " +"**not** be reserved. Orders must be confirmed manually to reserve products " +"in stock." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88 +msgid "Returns and refunds" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:90 +msgid "" +"Customers can only return an order through an online form. It may not be " +"possible to return products depending on the return strategy or type of " +"product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:93 +msgid "" +"Full refunds can be directly sent to customers from within the order " +"interface. A refund-compatible payment provider needs to be enabled first." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:97 +msgid ":doc:`/applications/sales/sales/products_prices/returns`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:98 +msgid ":doc:`/applications/services/helpdesk/advanced/after_sales`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:99 +msgid ":doc:`/applications/finance/payment_providers`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:104 +msgid "Invoice and legal requirements" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:106 +msgid "" +"The final step of an ecommerce order is to generate the invoice and send it " +"to the customer. Depending on the type of business (B2B or B2C), an invoice " +"can either be generated automatically (B2B) or on demand of the customer " +"(B2C). This process can be automated if (and when) the online payment is " +":ref:`confirmed `." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:111 +msgid "" +"To automate invoicing, go to :menuselection:`Website --> Configuration --> " +"Settings` and in the :guilabel:`Invoicing` section, enable " +":guilabel:`Automatic Invoice`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:3 +msgid "Performance monitoring" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:5 +msgid "" +"Odoo integrates a variety of tools to analyze and improve the performance of" +" your eCommerce website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:9 +msgid "Data monitoring" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:11 +msgid "" +"**Website** allows monitoring and analysis of the sales performance of your " +"eCommerce. To access the **reporting view**, go to :menuselection:`Website " +"--> Reporting --> eCommerce`. This dashboard helps you monitor everything " +"related to sales, such as sales performance per product, category, day, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst-1 +msgid "Performance reporting of eCommerce" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:19 +msgid "" +"By clicking :guilabel:`Measures`, you can select the type of measurement " +"used, such as:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:21 +msgid ":guilabel:`Margin`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:22 +msgid ":guilabel:`Qty Invoiced`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:23 +msgid ":guilabel:`Untaxed Total`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:24 +msgid ":guilabel:`Volume`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:25 +msgid "..." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:27 +msgid "" +"Other options include **multiple views (Pivot, etc.), comparison** by " +"periods or years, and directly :guilabel:`insert in spreadsheet`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:31 +#: ../../content/applications/websites/website/configuration/multi_website.rst:153 +msgid "Analytics" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:33 +msgid "" +"It is possible to link your Odoo website with " +":ref:`website/analytics/plausible` and :ref:`website/analytics/GA`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products.rst:5 +msgid "Products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:3 +msgid "Catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:5 +msgid "" +"The eCommerce catalog is the equivalent of your physical store shelves: it " +"allows customers to see what you have to offer. Clear categories, available " +"options, sorting, and navigation threads help you structure it efficiently." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:10 +msgid "Categorize the product catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:12 +msgid "" +"In Odoo, there is a **specific category model** for your eCommerce. Using " +"eCommerce categories for your products allows you to add a navigation menu " +"on your eCommerce page. Visitors can then use it to view all products under " +"the category they select." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:16 +msgid "" +"To do so, go to :menuselection:`Website --> eCommerce --> Products`, select " +"the product you wish to modify, click on the :guilabel:`Sales` tab, and " +"select the :guilabel:`Categories` you want under :guilabel:`eCommerce Shop`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "eCommerce categories under the \"Sales\" tab" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:25 +msgid "A single product can appear under multiple eCommerce categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:27 +msgid "" +"When your product's categories are configured, go to your **main shop page**" +" and click on :menuselection:`Edit --> Customize tab`. In the " +":guilabel:`Categories` option, you can either enable a menu on the " +":guilabel:`Left`, on the :guilabel:`Top`, or both. If you select the " +":guilabel:`Left` category, the option :guilabel:`Collapsable Category " +"Recursive` appears and allows to render the :guilabel:`Left` category menu " +"collapsable." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Categories options for your eCommerce website" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:38 +msgid ":doc:`products`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:43 +msgid "Browsing" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:45 +msgid "" +"The eCommerce category is the first tool to organize and split your " +"products. However, if you need an extra level of categorization in your " +"catalog, you can activate various **filters** such as attributes or sort-by " +"search." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:50 +msgid "Attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:52 +msgid "" +"Attributes refer to **characteristics** of a product, such as **color** or " +"**material**, whereas variants are the different combinations of attributes." +" :guilabel:`Attributes and Variants` can be found under " +":menuselection:`Website --> eCommerce --> Products`, select your product, " +"and :guilabel:`Attributes & Variants` tab." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:58 +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:15 +msgid ":doc:`../../../sales/sales/products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Attributes and variants of your product" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:64 +msgid "" +"To enable **attribute filtering**, go to your **main shop page**, click on " +":menuselection:`Edit --> Customize tab` and select either :guilabel:`Left`, " +":guilabel:`Top`, or both. Additionally, you can also enable :guilabel:`Price" +" Filtering` to enable price filters." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:69 +msgid "" +":guilabel:`Price Filter` works independently from **attributes** and, " +"therefore, can be enabled on its own if desired." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:73 +msgid "" +"You can use **attribute filters** even if you do not work with product " +"variants. When adding attributes to your products, make sure only to specify" +" *one* value per attribute. Odoo does not create variants if no combination " +"is possible." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:78 +msgid "Sort-by search" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:80 +msgid "" +"It is possible to allow the user to manually **sort the catalog** using the " +"search bar. From your **main shop page**, click on :menuselection:`Edit --> " +"Customize tab`; you can enable or disable the :guilabel:`Sort-By` option as " +"well as the :guilabel:`Layout` button. You can also select the " +":guilabel:`Default Sort` of the :guilabel:`Sort-By` button. The default sort" +" applies to *all* categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:86 +msgid "The **sorting** options are:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:88 +msgid "Featured" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:89 +msgid "Newest Arrivals" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:90 +msgid "Name (A-Z)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:91 +msgid "Price - Low to High" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:92 +msgid "Price - High to Low" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:94 +msgid "" +"In addition, you can **manually edit** the catalog's order of a product by " +"going to **the main shop page** and clicking on the product. Under the " +":guilabel:`Product` section of the :guilabel:`Customize` section, you can " +"rearrange the order by clicking on the arrows. `<<` `>>` move the product to" +" the **extreme** right or left, and `<` `>` move the product by **one** row " +"to the right or left. It is also possible to change the catalog's order of " +"products in :menuselection:`Website --> eCommerce --> Products` and drag-" +"and-dropping the products within the list." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Product rearrangement in the catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:107 +msgid "Page design" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:110 +msgid "Category page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:112 +msgid "" +"You can customize the layout of the category page using the website builder." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:115 +msgid "" +"Editing the layout of the category page is global; editing one category " +"layout affects *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:118 +msgid "" +"To do so, go on to your :menuselection:`Category page --> Edit --> " +"Customize`. Here, you can choose the layout, the number of columns to " +"display the products, etc. The :guilabel:`Product Description` button makes " +"the product description visible from the category page, underneath the " +"product picture." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Layout options of the category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:127 +msgid "" +"You can choose the size of the grid, but be aware that displaying too many " +"products may affect performance and page loading speed." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:131 +msgid "Product highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:133 +msgid "" +"You can highlight products to make them more visible on the category or " +"product page. On the page of your choice, go to :menuselection:`Edit --> " +"Customize` and click on the product to highlight. In the :guilabel:`Product`" +" section, you can choose the size of the product image by clicking on the " +"grid, and you can also add a **ribbon** or :guilabel:`Badge`. This displays " +"a banner across the product's image, such as:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:139 +msgid "Sale;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:140 +msgid "Sold out;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:141 +msgid "Out of stock;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:142 +msgid "New." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:144 +msgid "" +"Alternatively, you can activate the :doc:`developer mode " +"<../../../general/developer_mode>` on the **product's template**, and under " +"the :guilabel:`Sales` tab, change or create the ribbon from the " +":guilabel:`Ribbon` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:149 +msgid "" +"The :doc:`developer mode <../../../general/developer_mode>` is only intended" +" for experienced users who wish to have access to advanced tools. Using the " +"**developer mode** is *not* recommended for regular users." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Ribbon highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:158 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:160 +msgid "" +"You can access and enable additional feature buttons such as **add to " +"cart**, **comparison list**, or a **wishlist**. To do so, go to your **main " +"shop page**, and at the end of the :guilabel:`Products Page` category, click" +" on the feature buttons you wish to use. All three buttons appear when " +"hovering the mouse over a product's image." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:165 +msgid "" +":guilabel:`Add to Cart`: adds a button to :doc:`add the product to the cart " +"<../checkout_payment_shipping/cart>`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:167 +msgid "" +":guilabel:`Comparison List`: adds a button to **compare** products based on " +"their price, variant, etc.;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:169 +msgid "" +":guilabel:`Wishlist Button`: adds a button to **wishlist** the product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Feature buttons for add to cart, comparison list, and wishlist" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Appearance of buttons when hoovering over the mouse" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:180 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:112 +msgid "Add content" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:182 +msgid "" +"You can use **building blocks** to add content on the category page, with a " +"variety of blocks ranging from :guilabel:`Structure` to :guilabel:`Dynamic " +"Content`. Specific areas are defined to use blocks are defined and " +"highlighted on the page when **dragging-and-dropping** a block." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Building blocks areas" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:190 +msgid "" +"If you drop a building block **on top** of the product list, it creates a " +"new category header specific to *that* category." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:192 +msgid "" +"If you drop a building **on the top** or **bottom** of the page, it becomes " +"visible on *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:196 +msgid "" +"Adding content to an eCommerce category page is beneficial in terms of " +"**SEO** strategy. Using **keywords** linked to the products or the eCommerce" +" categories improves organic traffic. Additionally, each category has its " +"own specific URL that can be pointed to and is indexed by search engines." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:3 +msgid "Cross-selling and upselling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:5 +msgid "" +"Any sales process is an opportunity to maximize revenues. **Cross-selling " +"and upselling** are sales techniques consisting in selling customers " +"additional or more expensive products and services than what they were " +"originally shopping for. It is a great way to maximize the value of each one" +" of your customers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:10 +msgid "**Cross-selling** can be done via **two** features:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:12 +msgid "" +":ref:`Optional products ` upon **adding to cart**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:13 +msgid "" +":ref:`Accessory products ` on the **checkout " +"page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:15 +msgid "" +"**Upselling** is only done via :ref:`alternative products " +"` on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:19 +msgid ":doc:`catalog`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:22 +msgid "Cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:27 +msgid "Optional products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:29 +msgid "" +"**Optional products** are suggested when customers click :guilabel:`Add to " +"cart`, either from the **product page** or **catalog page**. Upon clicking, " +"a pop-up window opens with the **optional products** displayed in the " +":guilabel:`Available Options` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Optional products cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:37 +msgid "" +"To enable **optional products** go to :menuselection:`Website --> eCommerce " +"--> Products`, select a product, go to the :guilabel:`Sales` tab, and enter " +"the products you wish to feature in the :guilabel:`Optional Products` field." +" Optional products are **linked** to the product(s) they are set up with on " +"the **product template**. They only appear when that product is added to the" +" cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:43 +msgid "" +"You can also access the :guilabel:`Sales` tab of the **product template** by" +" selecting a product on your **main shop page** and clicking " +":guilabel:`Product` in the top-right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:49 +msgid "Accessory products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:51 +msgid "" +"**Accessory products** are displayed in the :guilabel:`Suggested " +"Accessories` section before processing to checkout at the :guilabel:`Review " +"Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Suggested accessories at checkout during cart review" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:58 +msgid "" +"To enable **accessory products**, go to :menuselection:`Website --> " +"eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, " +"and enter the products you wish to feature in the :guilabel:`Accessory " +"Products` field. Suggested accessory products are **linked** to the " +"product(s) they are set up with on the **product template**. They only " +"appear when that product is at the checkout process review." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:65 +msgid "Upselling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:70 +msgid "Alternative products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:72 +msgid "" +"**Alternative products** are suggested on the **product page** and usually " +"incentivize customers to buy a more expensive variant or product than the " +"one they were initially shopping for." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Alternative products on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:79 +msgid "" +"To enable **alternative products**, go to :menuselection:`Website --> " +"eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, " +"and enter the products you wish to feature in the :guilabel:`Alternative " +"Products` field. Then, go to the related **product page** by clicking " +":guilabel:`Go To Website`, and click :menuselection:`Edit`. Stay on the " +":guilabel:`Blocks` tab, and scroll down to the :guilabel:`Dynamic Content` " +"section. Then, drag and drop the :guilabel:`Products` building block " +"anywhere on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:86 +msgid "" +"When placed, in :guilabel:`Edit` mode, click the **block** to access various" +" settings for that :guilabel:`Products` building block. In the " +":guilabel:`Filter` field, select :guilabel:`Alternative Products`. You can " +"configure several additional settings, such as how many elements are " +"displayed (:guilabel:`Fetched Elements`), the :guilabel:`Template` used, " +"etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:3 +msgid "Price management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:5 +msgid "" +"Odoo offers multiple options to select the price displayed on your website, " +"as well as condition-specific prices based on set criteria." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:9 +msgid "Taxes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:12 +msgid "Tax configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:14 +msgid "" +"To add a tax on a product, you can either set a tax in the " +":guilabel:`Customer Taxes` field of the **product template** or use " +":doc:`fiscal positions " +"`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:19 +msgid ":doc:`/applications/finance/accounting/taxes`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:20 +msgid ":doc:`/applications/finance/accounting/taxes/avatax`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:21 +msgid ":doc:`/applications/finance/accounting/taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:24 +msgid "Tax display" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:26 +msgid "" +"Choosing the displayed price tax usually depends on a country's regulations " +"or the type of customers **(B2B vs. B2C)**. To select the type of price " +"displayed, go to :menuselection:`Website --> Configuration --> Settings`, " +"scroll down to the :guilabel:`Shop - Products` category, and select " +":guilabel:`Tax Excluded` or :guilabel:`Tax Included`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:31 +msgid "" +":guilabel:`Tax Excluded`: the price displayed on the website is **tax-" +"excluded**, and the tax is computed at the cart-review step;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:33 +msgid "" +":guilabel:`Tax Included`: the price displayed on the website is **tax-" +"included**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:36 +msgid "" +"This setting is **global**, and the tax-display type is the same for (all " +"of) your website(s). It is, therefore, not possible to select different tax " +"displays for different websites. This may be a significant point of " +"consideration when implementing a database with multiple ecommerce websites " +"aimed at varying customer types (i.e., B2B and B2C)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:41 +msgid "" +"You can choose to display the type of pricing next to the product price by " +"going to :menuselection:`Website --> Site --> Homepage --> Shop`, selecting " +"a product, and then :menuselection:`Edit --> Customize tab` and enabling " +":guilabel:`Tax Indication`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Tax type displayed on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:50 +msgid ":doc:`/applications/finance/accounting/taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:53 +msgid "Price per unit" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:55 +msgid "" +"It is possible to display a :doc:`price per unit " +"`" +" on the product page. To do that, go to :menuselection:`Website --> " +"Configuration --> Settings` and enable :guilabel:`Product Reference Price` " +"under the :guilabel:`Shop - Products` section. When enabled, ensure an " +"amount is set in the :guilabel:`Base Unit Count` field of the **product " +"template**, and in the :guilabel:`Sales Price`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Cost per unit pricing on the product template" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:66 +msgid "" +"The price per unit of measure can be found above the :guilabel:`Add to Cart`" +" button on the product page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Cost per unit pricing on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:74 +msgid "" +"Pay attention that having the price per unit may be **mandatory** in some " +"countries." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:77 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:82 +msgid "Price configuration: pricelists" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:84 +msgid "" +"Pricelists are the primary tool to manage prices on your eCommerce. They " +"allow you to define website-specific prices - different from the price on " +"the product template - based on the **country group**, **currency**, " +"**minimum quantity**, **period**, or **variant**. You can create as many " +"pricelists as needed, but it is mandatory to have at least one pricelist " +"configured per website. If no custom pricelists are added, Odoo defaults to " +"the **Public Pricelist** for all websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:91 +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:119 +msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:96 +msgid "" +"Pricelists can be found under :menuselection:`Website --> eCommerce --> " +"Pricelists`, but must first be activated. For that, head to " +":menuselection:`Website --> Configuration --> Settings` and scroll down to " +"the :guilabel:`Shop - Products` section. There, you can find two options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:100 +msgid ":guilabel:`Multiple prices per product`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:101 +msgid ":guilabel:`Advanced price rules (discounts, formulas)`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:103 +msgid "" +"The **first** option allows you to set different prices per customer " +"*segment*, i.e., registered customers, gold customers, regular customers, " +"etc. The **second** option allows you to set *price change* rules such as " +"**discounts**, **margins**, **roundings**, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:108 +msgid "Foreign currency" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:110 +msgid "" +"If you are selling in **multiple currencies** and have pricelists in foreign" +" currencies, customers can select their corresponding pricelist anywhere on " +"the :guilabel:`Shop` page from the drop-down menu next to the **search " +"bar**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Pricelists selection" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:120 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:123 +msgid "Permanent discount" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:125 +msgid "" +"If you have permanently reduced the price of a product, a popular means to " +"attract customers is the **strikethrough** strategy. The strategy consists " +"in displaying the previous price crossed out and the **new discounted " +"price** next to it." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Price strikethrough" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:133 +msgid "" +"To display a 'striked' price, enable the :guilabel:`Comparison Price` option" +" under :menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products category`. Then, head to the product's template " +"(:menuselection:`Website --> eCommerce --> Products`), and in the " +":guilabel:`Compare to Price` field, enter the **new** price." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:3 +msgid "Product management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:5 +msgid "" +"Odoo allows you to create, import, and manage your products' pages all " +"within the **Website** app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:8 +msgid "Add products to the catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:10 +msgid "To add a product to your catalog, you can either do it in:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:12 +msgid "" +"From anywhere on your website, click :menuselection:`+ New --> Product`. " +"Enter the name of your product, and :guilabel:`Save`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:14 +msgid ":menuselection:`Website --> eCommerce --> Products --> Create`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:15 +msgid "" +"or by :ref:`importing data ` using XLSX or CSV files. To do so," +" go to :menuselection:`Website --> eCommerce --> Products`. Click on " +":guilabel:`Favorites` and :ref:`Import records `." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:21 +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16 +msgid ":doc:`../../../sales/sales/products_prices/products/import`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:22 +msgid ":doc:`Product-related documentation <../../../sales/sales>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:25 +msgid "Publish" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:27 +msgid "" +"Upon creation, products are defaulted as :guilabel:`Unpublished` in your " +"eCommerce catalog. To make a product visible to visitors, go to " +":menuselection:`Website --> Site --> Homepage`, click on your **main shop** " +"page, select the product, and enable it as :guilabel:`Published` in the top-" +"right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:33 +msgid "" +"To publish **large batches** of products, the most convenient fashion is to " +"go to :menuselection:`Website --> eCommerce --> Products`. Here, remove the " +":guilabel:`Published` filter by clicking on the :guilabel:`x` right to it, " +"and then select the :guilabel:`List` view. Next, click the " +":guilabel:`dropdown toggle` button (located right below the :guilabel:`List`" +" button) and enable :guilabel:`Is published`. Click the :guilabel:`Is " +"Published` column to re-order it either by **published** or **unpublished** " +"products. Finally, select the products to publish by ticking their box on " +"the extreme-right, and tick any box of the selected products in the " +":guilabel:`Is Published` column to publish them all." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "List and dropdown toggle buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:47 +msgid "Product page design" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:49 +msgid "" +"Once a product is created, you can access its **product page** through the " +":guilabel:`Shop` page by clicking on the product, and then clicking " +":guilabel:`Edit`. Here, you can change the page's **additional functions**, " +"**layout**, **add content**, etc. Note that **enabled functions** apply to " +"*all* product pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:57 +msgid "Additional functions" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:59 +msgid "" +"In the **website builder** window, click :guilabel:`Customize` to enable " +"additional functions:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:61 +msgid "" +":guilabel:`Customers: Rating` allows customers to submit :ref:`product " +"reviews `; :guilabel:`Share` adds social media and email " +"icon buttons to share the product via those channels;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:64 +msgid "" +":guilabel:`Select Quantity`: if enabled, allows to choose the quantity added" +" to cart;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:65 +msgid "" +":guilabel:`Tax Indication`: notifies if the price is **VAT included** or " +"**excluded**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:66 +msgid "" +":guilabel:`Variants`: shows all possible :doc:`variants " +"` of the " +"product as a :guilabel:`Products List`; :guilabel:`Options` as selectable " +"options to compose the variant yourself;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:70 +msgid "" +":guilabel:`Cart`: :guilabel:`Buy Now` adds a :ref:`checkout button " +"` taking the customer directly to the checkout page; " +":guilabel:`Wishlist` allows to add the product to a wishlist;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:73 +msgid "" +":guilabel:`Specification`: allows you to select where the " +":guilabel:`Specifications` section is displayed. This option displays a list" +" of all variant attributes and values of a product, but only works for " +"products *with* variants." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:78 +msgid "" +"To allow **wishlists**, the option must be enabled in " +":menuselection:`Website --> Configuration --> Settings --> Shop - Products`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:80 +msgid "" +"To access the :guilabel:`Variants` options, the :doc:`Product Variants " +"<../../../sales/sales/products_prices/products/variants>` option must first " +"be enabled under :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Products`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:85 +msgid "Layout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:87 +msgid "" +"Within the same :guilabel:`Customize` tab as the :ref:`functions `, the layout configuration can be changed according to your " +"needs." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:90 +msgid "" +":guilabel:`Images Width`: changes the width of the product images displayed " +"on the page;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:91 +msgid "" +":guilabel:`Layout`: the :guilabel:`Carousel` layout displays a large, main " +"image with smaller ones underneath; whereas the :guilabel:`Grid` displays " +"four images in a square layout (see pictures below);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:94 +msgid "" +":guilabel:`Image Zoom`: choose which image zooms are available, either " +":guilabel:`Pop-up on Click`, when hovering over the image " +"(:guilabel:`Magnifier on hover`), on :guilabel:`Both`, or :guilabel:`None`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:97 +msgid "" +":guilabel:`Thumbnails`: decide how the thumbnails should be aligned, either " +"**vertically** (:guilabel:`Left`), or **horizontally** (:guilabel:`Right`);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:99 +msgid "" +":guilabel:`Main Image`: click :guilabel:`Replace` to change the product's " +"main image;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:100 +msgid "" +":guilabel:`Extra Images`: click :guilabel:`Add` or :guilabel:`Remove all` to" +" add or remove extra product images. You can also add images and videos via " +"**URL**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:104 +msgid "" +"Images must either be in PNG or JPG format. To trigger the zoom, the image " +"has to be bigger than 1024x1024." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Product images layout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:114 +msgid "" +"You can use **building blocks** (:menuselection:`Edit --> Blocks`) to add " +"content to your product page. These blocks can be used to add extra text and" +" picture galleries, features such as :guilabel:`Call to Actions`, " +":guilabel:`Comparisons`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:118 +msgid "" +"Depending on *where* you drop the **building block**, it may be available " +"either on the product page *only*, or on the *whole* website. **Building " +"blocks** dropped at the very top or very bottom of the page are available on" +" the *whole* website, where **building blocks** put underneath the product " +"description are only displayed on the *product* page *(see image below)*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Building blocks on product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:128 +msgid "Download link" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:130 +msgid "" +"To add a downloadable file (ex.: user's manual, notice of use, etc.) on the " +"product page, drag and drop a :guilabel:`Text` block from " +":menuselection:`Edit --> Blocks` on the page. Once placed, click within the " +":guilabel:`Text` block, and under the :guilabel:`Inline Text` section, " +"select either :menuselection:`Insert Media --> Documents` or " +":guilabel:`Insert or edit link` and enter the URL in the :guilabel:`Your " +"URL` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:137 +msgid "" +"The difference with :ref:`digital files ` is that " +"digital files can only be downloaded *after* checkout." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Media and link buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:147 +msgid "Digital files" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:149 +msgid "" +"Should your product be sold with a certificate, manual user, or any other " +"relevant document, it is possible to add a download link for customers at " +"the end of the checkout. To do that, first enable :guilabel:`Digital " +"Content` under :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Checkout Process`. Then, on the **product's template**, click on " +":menuselection:`More --> Digital Files` and :guilabel:`Create` a new file." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Digital Files menu" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:159 +msgid "For the configuration:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:161 +msgid ":guilabel:`Name`: the name of your file;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:162 +msgid "" +":guilabel:`Type:` select if it is either a **file** or a **URL**. " +"Accordingly, you either have a :guilabel:`File Content (base64)` field to " +"upload your file, or a :guilabel:`URL` field to enter your URL." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:165 +msgid "" +":guilabel:`Website`: the website on which that file is *available*. If you " +"want it available for *all* websites, leave it empty." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:168 +msgid "" +"The file is then available after checkout in the **purchase order** section " +"found on the customer's portal." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:172 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:175 +msgid "Multiple languages" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:177 +msgid "" +"If multiple languages are available on your website and you wish to have the" +" product's information translated, it is necessary to encode this translated" +" information in the **product's template**. Fields with multiple languages " +"available are identifiable by their abbreviation language (ex. :abbr:`EN " +"(English)`) next to their field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Field translation" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:186 +msgid "The **eCommerce-related** fields to translate are:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:188 +msgid ":guilabel:`Product name`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:189 +msgid ":guilabel:`Out-of-Stock Message` (under the :guilabel:`Sales` tab);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:190 +msgid ":guilabel:`Sales Description` (under the :guilabel:`Sales` tab);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:193 +msgid "" +"Having untranslated content on a web page may be detrimental to the user " +"experience and :doc:`SEO <../../../websites/website/pages/seo>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:196 +msgid "" +"To check the language(s) of your website, go to :menuselection:`Website --> " +"Configuration --> Settings --> Website Info section`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:200 +msgid ":doc:`../../../websites/website/pages/seo`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:201 +msgid ":ref:`Multi-language support `" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:206 +msgid "" +"A product can be set available on either *one* or *all* websites, but it is " +"not possible to select *some* websites and not others. To define a product's" +" availability, go to :menuselection:`Website --> eCommerce --> Products`, " +"select your product, and in the :guilabel:`Sales` tab, click the " +":guilabel:`Website` you wish the product to be available on. Leave the field" +" empty for the products to be available on *all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:213 +msgid "Stock management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:215 +msgid "" +"Under the :menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products`, you can enable and configure inventory management options." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:219 +msgid "" +"To display the stock level on the product page, the :guilabel:`Product Type`" +" on the **product's form** must be set to :guilabel:`Storable` (only " +"available when the **Inventory** app is installed)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:224 +msgid "Inventory" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:226 +msgid "" +"In the :guilabel:`Inventory Defaults` sub-section, you can select the " +"eCommerce selling strategy of products:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:229 +msgid "" +":guilabel:`Warehouse`: if you have multiple warehouses, you can define the " +"warehouse associated to your website. If you have multiple websites, you can" +" select a different one per website;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:231 +msgid "" +":guilabel:`Out-of-Stock (Continue Selling)`: enabling it allows customers to" +" continue placing orders even when the product is **out-of-stock**. Leave it" +" unchecked to **prevent orders**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:234 +msgid "" +":guilabel:`Show Available Qty`: enabling it displays the available quantity " +"left under a specified threshold on the product page. The available quantity" +" is calculated based on the 'On hand' quantity minus the quantity already " +"reserved for outgoing transfers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:239 +msgid ":ref:`Allow only selected customers to buy `" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:242 +msgid "Selling as kit" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:244 +msgid "" +"If you are selling non-prepackaged kits (i.e., the kits are made of " +"individual products), we recommend you read the related documentation to " +"keep track of your stock." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:248 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/management/kit_shipping`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:251 +msgid "Product comparison" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:253 +msgid "" +"You can enable a **product comparison tool** for your eCommerce by going to " +":menuselection:`Website --> Configuration --> Settings --> Shop - Products`," +" and ticking :guilabel:`Product Comparison Tool`. This tool allows to save " +"products' **specifications** and compare them against each other on a single" +" page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:258 +msgid "" +"On the product page, scroll down to the :guilabel:`Specifications` section " +"and click :guilabel:`Compare`. Repeat the same process for all products you " +"wish to compare. Then, click the :guilabel:`Compare` button of the pop-up " +"window at the bottom of the page to reach the comparison summary." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:264 +msgid "" +"The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes" +" ` are set on the **product's template**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Product comparison window" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3 +msgid "Product variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5 +msgid "" +"Product variants are variations, such as different colors, materials, etc., " +"of the same product. These variations can differ in price and availability " +"from the product. Product variants can either be :doc:`created " +"<../../../sales/sales/products_prices/products/variants>` or :doc:`imported " +"<../../../sales/sales/products_prices/products/import>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10 +msgid "" +"To use product variants, enable them under :menuselection:`Website --> " +"Configuration --> Settings`, in the :guilabel:`Shop - Products` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14 +msgid ":doc:`../managing_products/products`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19 +msgid "Product configurator" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:21 +msgid "" +"Adding attributes and values to a product template allows the enabling of " +"the **product configurator** on the product page. Customers use it to " +"configure and select the product variant of their choice; or in the case of " +"multiple attributes, combine those to create a specific variant." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Variants configurator" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:29 +msgid "" +"The **display type** of each attribute used in the product configurator can " +"be edited through the **website builder** by clicking :menuselection:`Edit " +"--> Customize` on the product page, and then clicking on one of the " +"attributes. You can then select between four options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:33 +msgid ":guilabel:`Radio`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:34 +msgid ":guilabel:`Pills`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:35 +msgid ":guilabel:`Select`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:36 +msgid ":guilabel:`Color`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Display type options for attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:44 +msgid "" +"Alternatively, the **display type** can be edited through " +":menuselection:`Website --> eCommerce --> Attributes`, selecting an " +"**attribute**, and then choosing a :guilabel:`Display Type`; or through the " +"**product template** by going to :menuselection:`eCommerce --> Products`, " +"selecting a product, and then clicking :guilabel:`Attributes and Variants`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:50 +msgid "" +"Specific combinations of values can be excluded from the product " +"configurator. This way, customers are unable to select the excluded " +"combination of values. To do so, go to :menuselection:`Website --> eCommerce" +" --> Products`, select a product, and go to :guilabel:`Attributes and " +"Variants`. Then, click on an **attribute**, select a **value**, and in the " +":guilabel:`Exclude for` section, select a :guilabel:`Product Template` and " +"the :guilabel:`Attribute Values` to exclude." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:58 +msgid "Product specifications" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:60 +msgid "" +"Values used for each attribute are displayed as a **specification list** at " +"the bottom of the product page. To be visible, the **specification list** " +"must first be enabled on the product page by going to :menuselection:`Edit " +"--> Customize` and selecting a placement for the field " +":guilabel:`Specification`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Specifications list on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:70 +msgid "" +"The product **specification list** can also be used on products without " +"variants. For that, make sure to have no values combination. Products with " +"single values for their attributes do not generate variants." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75 +msgid "Filter catalog by attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:77 +msgid "" +"Customers **can** filter the **catalog** based on product attributes and " +"values, allowing them to :ref:`filter ` the catalog " +"based only on the attribute(s) of their choice." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:80 +msgid "" +"To enable **attributes filtering**, go to :menuselection:`Edit --> " +"Customize` from your **main shop page** and click on one of the " +":guilabel:`Categories` in the left column. Here, enable either " +":guilabel:`Left`, :guilabel:`Top`, or **both**, in the " +":guilabel:`Attributes` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Categories buttons" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:3 +msgid "eLearning" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:5 +msgid "" +"The **eLearning** app allows you to easily upload content, define learning " +"objectives, manage attendees, assess students' progress, and even set up " +"rewards. Engaging participants in a meaningful learning experience enhances " +"their attentiveness and fosters heightened productivity." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:10 +msgid "" +"You can manage your eLearning content on the **front end** or the **back " +"end**. The **front end** allows you to create content quickly from your " +"website, while the **back end** provides additional options and allows " +"collaboration. This documentation focuses on using the back end to create " +"your content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:16 +msgid "" +"`Odoo Tutorials: eLearning `_" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:19 +msgid "Courses" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:21 +msgid "" +"By going to :menuselection:`eLearning --> Courses --> Courses`, you can get " +"an overview of all your courses." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:24 +msgid "" +"Click on a course title to edit your course on the back end. Click on " +":guilabel:`View course` to access your course on the front end." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:28 +msgid "Course creation" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:30 +msgid "" +"Click :guilabel:`New` to create a new course. When the page pops up, you can" +" add your :guilabel:`Course Title` and one or more :guilabel:`Tags` to " +"describe your course. You can add an image to illustrate your course by " +"hovering your mouse on the camera placeholder image and clicking on the edit" +" icon. Four tabs allow you to edit your course further: :ref:`Content " +"`, :ref:`Description `, " +":ref:`Options `, and :ref:`Karma `." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Create your elearning course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:44 +msgid "Content tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:46 +msgid "" +"This tab allows you to manage your course content. Click on :guilabel:`Add " +"Section` to divide your course into different sections. Click on " +":guilabel:`Add Content` to create :ref:`content `." +" Click on :guilabel:`Add Certification` to assess the level of understanding" +" of your attendees, certify their skills, and motivate them. " +"**Certification** is part of the :doc:`Surveys " +"<../marketing/surveys/create>` app." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:55 +#: ../../content/applications/websites/elearning.rst:202 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:57 +msgid "" +"You can add a short description or information related to your course in the" +" :guilabel:`Description` tab. It appears under your course title on your " +"website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Add a description to your course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:67 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:69 +msgid "" +"In the :guilabel:`Options` tab, different configurations are available: " +":ref:`Course `, :ref:`Communication " +"`, :ref:`Access rights `, " +"and :ref:`Display `." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Overview of the Options tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:80 +msgid "Course" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:82 +msgid "" +"Assign a :guilabel:`Responsible` user for your course. If you have multiple " +"websites, use the :guilabel:`Website` field to only display the course on " +"the selected website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:88 +msgid "Communication" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:90 +msgid "" +":guilabel:`Allow Reviews`: tick the box to allow attendees to like and " +"comment on your content and to submit reviews on your course;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:92 +msgid "" +":guilabel:`Forum`: add a dedicated forum to your course (only shown if the " +"**Forum** feature is enabled in the app's settings);" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:94 +msgid "" +":guilabel:`New Content Notification`: select an email template sent to your " +"attendees when you upload new content. Click on the internal link button " +"(:guilabel:`➜`) to have access to the email template editor;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:97 +msgid "" +":guilabel:`Completion Notification`: select an email template sent to your " +"attendees once they reach the end of your course. Click on the internal link" +" button (:guilabel:`➜`) to access the email template editor;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:104 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:106 +msgid "" +":guilabel:`Show course to`: define who can access your course and their " +"content between :guilabel:`Everyone`, :guilabel:`Signed In` or " +":guilabel:`Course Attendees`;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:108 +msgid "" +":guilabel:`Enroll Policy`: define how people enroll in your course. Select:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:110 +msgid ":guilabel:`Open`: if you want your course to be available to anyone;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:111 +msgid "" +":guilabel:`On Invitation`: if only people who received an invitation can " +"enroll to your course. If selected, fill in the :guilabel:`Enroll Message` " +"explaining the course's enrollment process. This message appears on your " +"website under the course title;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:114 +msgid "" +":guilabel:`On Payment`: if only people who bought your course can attend it." +" The :guilabel:`Paid Courses` feature must be enabled to get this option. If" +" you select :guilabel:`On Payment`, you must add a :guilabel:`Product` for " +"your course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:119 +msgid "" +"Only products set up with :guilabel:`Course` as their :guilabel:`Product " +"Type` are displayed." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:125 +msgid "Display" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:127 +msgid "" +":guilabel:`Training`: the course content appears as a training program, and " +"the courses must be taken in the proposed order." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:129 +msgid "" +":guilabel:`Documentation`: the content is available in any order. If you " +"choose this option, you can choose which page should be promoted on the " +"course homepage by using the :guilabel:`Featured Content` field." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:136 +msgid "Karma tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:138 +msgid "This tab is about gamification to make eLearning fun and interactive." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:140 +msgid "" +"In the :guilabel:`Rewards` section, choose how many karma points you want to" +" grant your students when they :guilabel:`Review` or :guilabel:`Finish` a " +"course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:143 +msgid "" +"In the :guilabel:`Access Rights` section, define the karma needed to " +":guilabel:`Add Review`, :guilabel:`Add Comment`, or :guilabel:`Vote` on the " +"course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:147 +msgid "" +"From your course, click the :guilabel:`Contact Attendees` button to reach " +"people who are enrolled in the course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:153 +msgid "Course groups" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:155 +msgid "" +"Use the **Course Groups** to inform users and allow them to filter the " +"courses from the :guilabel:`All Courses` dashboard." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:158 +msgid "" +"You can manage them by going to :menuselection:`Configuration --> Course " +"Groups`. Click :guilabel:`New` to create a new course group. Add the " +":guilabel:`Course Group Name`, tick the :guilabel:`Menu Entry` box to allow " +"users to search by course group on the website, and add tags in the " +":guilabel:`Tag Name` column. For each tag, you can select a corresponding " +"color." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:164 +msgid "Settings" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:166 +msgid "" +"You can enable different features to customize your courses by going to " +":menuselection:`eLearning --> Configuration --> Settings`:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:169 +msgid "" +"**Certifications**: to evaluate the knowledge of your attendees and certify " +"their skills;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:170 +msgid "" +"**Paid courses**: to sell access to your courses on your website and track " +"revenues;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:171 +msgid "" +"**Mailing**: to update all your attendees at once through mass mailings;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:172 +msgid "" +"**Forum**: to create a community and let attendees answer each other's " +"questions." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:177 +msgid "Content" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:179 +msgid "" +"Manage your content by going to :menuselection:`eLearning --> Courses --> " +"Contents`. Click :guilabel:`New` to create content. Add your " +":guilabel:`Content Title`, and if you want :ref:`Tags `, " +"then fill in the related information among the different tabs." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Create your content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:188 +msgid "Document tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:190 +msgid ":guilabel:`Course`: select the course your content belongs to;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:191 +msgid ":guilabel:`Content Type`: select the type of your content;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:192 +msgid ":guilabel:`Responsible`: add a responsible person for your content;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:193 +msgid "" +":guilabel:`Duration`: indicate the time required to complete the course;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:194 +msgid "" +":guilabel:`Allow Download`: allow users to download the content of the " +"slide. This option is only visible when the content is a document;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:196 +msgid ":guilabel:`Allow Preview`: the course is accessible by anyone." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:197 +msgid "" +":guilabel:`# of Public Views`: displays the number of views from non-" +"enrolled participants;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:198 +msgid "" +":guilabel:`# Total Views`: displays the total number of views (non-enrolled " +"and enrolled participants)." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:204 +msgid "" +"You can add a description of your content that appears front end in the " +":guilabel:`About` section of your course content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:208 +msgid "Additional Resources tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:210 +msgid "" +"Click :guilabel:`Add a line` to add a link or a file that supports your " +"participants' learning. It appears in the course content on your website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Additional ressources" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:220 +msgid "Quiz tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:222 +msgid "" +"From this tab you can create a quiz to assess your students at the end of " +"the course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:224 +msgid "" +"The :guilabel:`Points Rewards` section lets you give a specific number of " +"karma points depending on how many tries they need to correctly answer the " +"question. Then, create your questions and the possible answers by clicking " +"on :guilabel:`Add a line`. A new window pops up, add the question by filling" +" in the :guilabel:`Question Name` and add multiple answers by clicking on " +":guilabel:`Add a line`. Tick the :guilabel:`Is correct answer` to mark one " +"or more answers as correct. You can also fill in the :guilabel:`Comment` " +"field to display additional information when the answer is chosen by the " +"participant." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:235 +msgid "Content Tags" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:237 +msgid "" +"The **Content Tags** help users to classify the content from the " +":guilabel:`Contents` dashboard." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:239 +msgid "" +"You can manage them by going to :menuselection:`eLearning --> Configuration " +"--> Content Tags`. Click :guilabel:`New` to create a new tag." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:243 +msgid "Publish your content" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:245 +msgid "" +"Everything created on the back end needs to be published from the front end." +" Unpublished content is always visible from your website but still needs to " +"be published to be available to your audience." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:248 +msgid "" +"You must be on your website's front end to publish your content. To do so, " +"click on the :guilabel:`Go To Website` smart button, and tick the " +":guilabel:`Publish` option available in the right-hand corner." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Publish your content." +msgstr "" + +#: ../../content/applications/websites/forum.rst:3 +msgid "Forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:5 +msgid "" +"**Odoo Forum** is a question-and-answer forum designed with providing " +"customer support in mind. Adding a forum to a website enables you to build a" +" community, encourage engagement, and share knowledge." +msgstr "" + +#: ../../content/applications/websites/forum.rst:12 +msgid "Create a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:14 +msgid "" +"To create or edit a forum, go to :menuselection:`Website --> Configuration " +"--> Forum: Forums`. Click :guilabel:`New` or select an existing forum and " +"configure the following elements." +msgstr "" + +#: ../../content/applications/websites/forum.rst:17 +msgid ":guilabel:`Forum Name`: add the name of the forum." +msgstr "" + +#: ../../content/applications/websites/forum.rst:19 +msgid "" +":guilabel:`Mode`: select :guilabel:`Questions` to enable marking an answer " +"as best, meaning questions then appear as *solved*, or " +":guilabel:`Discussions` if the feature is not needed." +msgstr "" + +#: ../../content/applications/websites/forum.rst:23 +msgid "" +"Regardless of the selected mode, only **one answer** per user is allowed on " +"a single post. Commenting multiple times is allowed, however." +msgstr "" + +#: ../../content/applications/websites/forum.rst:26 +msgid ":guilabel:`Default Sort`: choose how questions are sorted by default." +msgstr "" + +#: ../../content/applications/websites/forum.rst:28 +msgid ":guilabel:`Newest`: by latest question posting date" +msgstr "" + +#: ../../content/applications/websites/forum.rst:29 +msgid "" +":guilabel:`Last Updated`: by latest posting activity date (answers and " +"comments included)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:30 +msgid ":guilabel:`Most Voted`: by highest vote tally" +msgstr "" + +#: ../../content/applications/websites/forum.rst:31 +msgid ":guilabel:`Relevance`: by post relevancy (determined by a formula)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:32 +msgid "" +":guilabel:`Answered`: by likelihood to be answered (determined by a formula)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:35 +msgid "" +"Users have several sorting options (total replies, total views, last " +"activity) on the forum front end." +msgstr "" + +#: ../../content/applications/websites/forum.rst:38 +msgid "" +":guilabel:`Privacy`: select :guilabel:`Public` to let anyone view the forum," +" :guilabel:`Signed In` to make it visible only for signed-in users, or " +":guilabel:`Some users` to make it visible only for a specific user access " +"group by selecting one :guilabel:`Authorized Group`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:42 +msgid "" +"Next, configure the :ref:`karma gains ` and the " +":ref:`karma-related rights `." +msgstr "" + +#: ../../content/applications/websites/forum.rst:48 +msgid "Karma points" +msgstr "" + +#: ../../content/applications/websites/forum.rst:50 +msgid "" +"Karma points can be given to users based on different forum interactions. " +"They can be used to determine which forum functionalities users can access, " +"from being able to vote on posts to having moderator rights. They are also " +"used to set user :ref:`ranks `." +msgstr "" + +#: ../../content/applications/websites/forum.rst:55 +msgid "" +"A user's karma points are shared across all forums, courses, etc., of a " +"single Odoo website." +msgstr "" + +#: ../../content/applications/websites/forum.rst:56 +msgid "" +"eLearning users can earn karma points through different :ref:`course " +"interactions ` and by :ref:`completing quizzes " +"`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:62 +msgid "Karma gains" +msgstr "" + +#: ../../content/applications/websites/forum.rst:64 +msgid "Several forum interactions can give or remove karma points." +msgstr "" + +#: ../../content/applications/websites/forum.rst:70 +msgid "Interaction" +msgstr "" + +#: ../../content/applications/websites/forum.rst:71 +#: ../../content/applications/websites/forum.rst:129 +msgid "Description" +msgstr "" + +#: ../../content/applications/websites/forum.rst:72 +msgid "Default karma gain" +msgstr "" + +#: ../../content/applications/websites/forum.rst:73 +msgid ":guilabel:`Asking a question`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:74 +msgid "You post a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:75 +#: ../../content/applications/websites/forum.rst:90 +msgid "2" +msgstr "" + +#: ../../content/applications/websites/forum.rst:76 +msgid ":guilabel:`Question upvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:77 +msgid "Another user votes for a question you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:78 +#: ../../content/applications/websites/forum.rst:139 +msgid "5" +msgstr "" + +#: ../../content/applications/websites/forum.rst:79 +msgid ":guilabel:`Question downvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:80 +msgid "Another user votes against a question you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:81 +#: ../../content/applications/websites/forum.rst:87 +msgid "-2" +msgstr "" + +#: ../../content/applications/websites/forum.rst:82 +msgid ":guilabel:`Answer upvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:83 +msgid "Another user votes for an answer you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:84 +msgid "10" +msgstr "" + +#: ../../content/applications/websites/forum.rst:85 +msgid ":guilabel:`Answer downvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:86 +msgid "Another user votes against an answer you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:88 +msgid ":guilabel:`Accepting an answer`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:89 +msgid "You mark an answer posted by another user as best." +msgstr "" + +#: ../../content/applications/websites/forum.rst:91 +msgid ":guilabel:`Answer accepted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:92 +msgid "Another user marks an answer you posted as best." +msgstr "" + +#: ../../content/applications/websites/forum.rst:93 +msgid "15" +msgstr "" + +#: ../../content/applications/websites/forum.rst:94 +msgid ":guilabel:`Answer flagged`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:95 +msgid "" +"A question or an answer you posted is :ref:`marked as offensive " +"`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:96 +msgid "-100" +msgstr "" + +#: ../../content/applications/websites/forum.rst:99 +msgid "" +"New users receive **three points** upon validating their email address." +msgstr "" + +#: ../../content/applications/websites/forum.rst:101 +msgid "" +"To modify the default values, go to :menuselection:`Website --> " +"Configuration --> Forum: Forums`, select the forum, and go to the " +":guilabel:`Karma Gains` tab. Select a value to edit it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:104 +msgid "" +"If the value is positive (e.g., `5`), the number of points will be added to " +"the user's tally each time the interaction happens on the selected forum. " +"Conversely, if the value is negative (e.g., `-5`), the number of points will" +" be deducted. Use `0` if an interaction should not impact a user's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst:112 +msgid "Karma-related rights" +msgstr "" + +#: ../../content/applications/websites/forum.rst:114 +msgid "" +"To configure how many karma points are required to access the different " +"forum functionalities, go to :menuselection:`Website --> Configuration --> " +"Forum: Forums`, select the forum, and go to the :guilabel:`Karma Related " +"Rights` tab. Select a value to edit it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:119 +msgid "" +"Some functionalities, such as :guilabel:`Edit all posts`, :guilabel:`Close " +"all posts`, :guilabel:`Delete all posts`, :guilabel:`Moderate posts`, and " +":guilabel:`Unlink all comments`, are rather sensitive. Make sure to " +"understand the consequences of giving *any* user reaching the set karma " +"requirements access to such functionalities." +msgstr "" + +#: ../../content/applications/websites/forum.rst:128 +msgid "Functionality" +msgstr "" + +#: ../../content/applications/websites/forum.rst:130 +msgid "Default karma requirement" +msgstr "" + +#: ../../content/applications/websites/forum.rst:131 +msgid ":guilabel:`Ask questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:132 +msgid "Post questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:133 +#: ../../content/applications/websites/forum.rst:136 +msgid "3" +msgstr "" + +#: ../../content/applications/websites/forum.rst:134 +msgid ":guilabel:`Answer questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:135 +msgid "Post answers to questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:137 +msgid ":guilabel:`Upvote`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:138 +msgid "Vote for questions or answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:140 +msgid ":guilabel:`Downvote`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:141 +msgid "Vote against questions or answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:142 +#: ../../content/applications/websites/forum.rst:182 +#: ../../content/applications/websites/forum.rst:188 +msgid "50" +msgstr "" + +#: ../../content/applications/websites/forum.rst:143 +msgid ":guilabel:`Edit own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:144 +msgid "Edit questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:145 +#: ../../content/applications/websites/forum.rst:176 +#: ../../content/applications/websites/forum.rst:179 +msgid "1" +msgstr "" + +#: ../../content/applications/websites/forum.rst:146 +msgid ":guilabel:`Edit all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:147 +msgid "Edit any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:148 +msgid "300" +msgstr "" + +#: ../../content/applications/websites/forum.rst:149 +msgid ":guilabel:`Close own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:150 +msgid "Close questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:151 +#: ../../content/applications/websites/forum.rst:194 +msgid "100" +msgstr "" + +#: ../../content/applications/websites/forum.rst:152 +msgid ":guilabel:`Close all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:153 +msgid "Close any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:154 +#: ../../content/applications/websites/forum.rst:157 +#: ../../content/applications/websites/forum.rst:164 +#: ../../content/applications/websites/forum.rst:170 +#: ../../content/applications/websites/forum.rst:185 +#: ../../content/applications/websites/forum.rst:191 +#: ../../content/applications/websites/forum.rst:197 +msgid "500" +msgstr "" + +#: ../../content/applications/websites/forum.rst:155 +msgid ":guilabel:`Delete own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:156 +msgid "Delete questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:158 +msgid ":guilabel:`Delete all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:159 +msgid "Delete any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:160 +#: ../../content/applications/websites/forum.rst:200 +msgid "1,000" +msgstr "" + +#: ../../content/applications/websites/forum.rst:161 +msgid ":guilabel:`Nofollow links`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:162 +msgid "" +"If you are under the karma threshold, a *nofollow* attribute tells search " +"engines to ignore links you post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:165 +msgid ":guilabel:`Accept an answer on own questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:166 +msgid "Mark an answer as best on questions you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:167 +msgid "20" +msgstr "" + +#: ../../content/applications/websites/forum.rst:168 +msgid ":guilabel:`Accept an answer to all questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:169 +msgid "Mark an answer as best on any question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:171 +msgid ":guilabel:`Editor Features: image and links`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:172 +msgid "Add links and images to your posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:173 +#: ../../content/applications/websites/forum.rst:206 +msgid "30" +msgstr "" + +#: ../../content/applications/websites/forum.rst:174 +msgid ":guilabel:`Comment own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:175 +msgid "Post comments under questions or answers you created." +msgstr "" + +#: ../../content/applications/websites/forum.rst:177 +msgid ":guilabel:`Comment all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:178 +msgid "Post comments under any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:180 +msgid ":guilabel:`Convert own answers to comments and vice versa`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:181 +msgid "Convert comments you posted as answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:183 +msgid ":guilabel:`Convert all answers to comments and vice versa`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:184 +msgid "Convert any comment as answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:186 +msgid ":guilabel:`Unlink own comments`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:187 +msgid "Delete comments you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:189 +msgid ":guilabel:`Unlink all comments`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:190 +msgid "Delete any comment." +msgstr "" + +#: ../../content/applications/websites/forum.rst:192 +msgid ":guilabel:`Ask questions without validation`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:193 +msgid "" +"Questions you post do not require to be :ref:`validated ` " +"first." +msgstr "" + +#: ../../content/applications/websites/forum.rst:195 +msgid ":guilabel:`Flag a post as offensive`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:196 +msgid "Flag a question or answer as offensive." +msgstr "" + +#: ../../content/applications/websites/forum.rst:198 +msgid ":guilabel:`Moderate posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:199 +msgid "Access all :ref:`moderation tools `." +msgstr "" + +#: ../../content/applications/websites/forum.rst:201 +msgid ":guilabel:`Change question tags`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:202 +msgid "" +"Change posted questions' :ref:`tags ` (if you have the right to " +"edit them)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:203 +msgid "75" +msgstr "" + +#: ../../content/applications/websites/forum.rst:204 +msgid ":guilabel:`Create new tags`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:205 +msgid "Create new :ref:`tags ` when posting questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:207 +msgid ":guilabel:`Display detailed user biography`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:208 +msgid "" +"When a user hovers their mouse on your avatar or username, a popover box " +"showcases your karma points, biography, and number of :ref:`badges " +"` per level." +msgstr "" + +#: ../../content/applications/websites/forum.rst:210 +msgid "750" +msgstr "" + +#: ../../content/applications/websites/forum.rst:213 +msgid "" +"Track all karma-related activity and add or remove karma manually by " +":ref:`enabling developer mode ` and going to " +":menuselection:`Settings --> Gamification Tools --> Karma Tracking`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:220 +msgid "Gamification" +msgstr "" + +#: ../../content/applications/websites/forum.rst:222 +msgid "" +"Ranks and badges can be used to encourage participation. Ranks are based on " +"the total :ref:`karma points `, while badges can be granted " +"manually or automatically by completing challenges." +msgstr "" + +#: ../../content/applications/websites/forum.rst:229 +msgid "Ranks" +msgstr "" + +#: ../../content/applications/websites/forum.rst:231 +msgid "" +"To create new ranks or modify the default ones, go to " +":menuselection:`Website --> Configuration --> Forum: Ranks` and click " +":guilabel:`New` or select an existing rank." +msgstr "" + +#: ../../content/applications/websites/forum.rst:234 +msgid "" +"Add the :guilabel:`Rank Name`, the :guilabel:`Required Karma` points to " +"reach it, its :guilabel:`Description`, a :guilabel:`Motivational` message to" +" encourage users to reach it, and an image." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Default forum ranks" +msgstr "" + +#: ../../content/applications/websites/forum.rst:244 +msgid "Badges" +msgstr "" + +#: ../../content/applications/websites/forum.rst:246 +msgid "" +"To create new badges or modify the default ones, go to " +":menuselection:`Website --> Configuration --> Forum: Badges` and click " +":guilabel:`New` or select an existing badge." +msgstr "" + +#: ../../content/applications/websites/forum.rst:249 +msgid "Enter the badge name and description, add an image, and configure it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:252 +msgid "Assign manually" +msgstr "" + +#: ../../content/applications/websites/forum.rst:254 +msgid "" +"If the badge should be granted manually, select which users can grant them " +"by selecting one of the following :guilabel:`Allowance to Grant` options:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:257 +msgid "" +":guilabel:`Everyone`: all non-portal users (since badges are granted from " +"the backend)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:258 +msgid "" +":guilabel:`A selected list of users`: users selected under " +":guilabel:`Authorized Users`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:259 +msgid "" +":guilabel:`People having some badges`: users who have been granted the " +"badges selected under :guilabel:`Required Badges`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:262 +msgid "" +"It is possible to restrict how many times per month each user can grant the " +"badge by enabling :guilabel:`Monthly Limited Sending` and entering a " +":guilabel:`Limitation Number`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:266 +msgid "Assign automatically" +msgstr "" + +#: ../../content/applications/websites/forum.rst:268 +msgid "" +"If the badge should be granted **automatically** when certain conditions are" +" met, select :guilabel:`No one, assigned through challenges` under " +":guilabel:`Allowance to Grant`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:271 +msgid "" +"Next, determine how the badge should be granted by clicking :guilabel:`Add` " +"under the :guilabel:`Rewards for challenges` section. Select a challenge to " +"add it or create one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:276 +msgid "" +"It is possible to give the badge a :guilabel:`Forum Badge Level` " +"(:guilabel:`Bronze`, :guilabel:`Silver`, :guilabel:`Gold`) to give it more " +"or less importance." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Default forum badges" +msgstr "" + +#: ../../content/applications/websites/forum.rst:285 +msgid "Tags" +msgstr "" + +#: ../../content/applications/websites/forum.rst:287 +msgid "Users can use tags to filter forum posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:289 +msgid "" +"To manage tags, go to :menuselection:`Website --> Configuration --> Forum: " +"Tags`. Click :guilabel:`New` to create a tag and select the related " +":guilabel:`Forum`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:293 +msgid "" +"Use the :guilabel:`Tags` section on the forum's sidebar to filter all " +"questions assigned to the selected tag. Click :guilabel:`View all` to " +"display all tags." +msgstr "" + +#: ../../content/applications/websites/forum.rst:295 +msgid "" +"New tags can be created when posting a new message, provided the user has " +"enough :ref:`karma points `." +msgstr "" + +#: ../../content/applications/websites/forum.rst:301 +msgid "Use a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:304 +msgid "" +"Access to many functionalities depends on a user's :ref:`karma points " +"`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:310 +msgid "Post questions" +msgstr "" + +#: ../../content/applications/websites/forum.rst:312 +msgid "" +"To create a new post, access the forum's front end, click :guilabel:`New " +"Post`, and fill in the following:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:315 +msgid ":guilabel:`Title`: add the question or the topic of the post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:316 +msgid ":guilabel:`Description`: add a description for the question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:317 +msgid ":guilabel:`Tags`: add up to five :ref:`tags `." +msgstr "" + +#: ../../content/applications/websites/forum.rst:319 +msgid "Click :guilabel:`Post Your Question`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:324 +msgid "Interact with posts" +msgstr "" + +#: ../../content/applications/websites/forum.rst:326 +msgid "Different actions are possible on a post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:328 +msgid "" +"Mark a question as **favorite** by clicking the star button (:guilabel:`☆`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:329 +msgid "" +"Follow a post and get **notifications** (by email or within Odoo) when it is" +" answered by clicking the bell button (:guilabel:`🔔`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:331 +msgid "" +"**Vote** *for* (up arrow :guilabel:`▲`) or *against* (down arrow " +":guilabel:`▼`) a question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:333 +msgid "" +"Mark an answer as **best** by clicking the check mark button " +"(:guilabel:`✔`). This option is only available if the :guilabel:`Forum Mode`" +" is set to :guilabel:`Questions`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:335 +msgid ":guilabel:`Answer` a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:336 +msgid "" +"**Comment** on a question or answer by clicking the speech bubble button " +"(:guilabel:`💬`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:337 +msgid "" +"**Share** a question on Facebook, Twitter, or LinkedIn by clicking the " +"*share nodes* button." +msgstr "" + +#: ../../content/applications/websites/forum.rst:339 +msgid "Click the ellipsis button (:guilabel:`...`) to:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:341 +msgid ":guilabel:`Edit` a question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:342 +msgid ":guilabel:`Close` a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:343 +msgid "" +":guilabel:`Delete` a question, answer, or comment. It is possible to " +":guilabel:`Undelete` questions afterward." +msgstr "" + +#: ../../content/applications/websites/forum.rst:345 +msgid ":guilabel:`Flag` a question or answer as offensive." +msgstr "" + +#: ../../content/applications/websites/forum.rst:346 +msgid ":guilabel:`Convert` a comment into an answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:347 +msgid "" +":guilabel:`View` the related :ref:`Helpdesk ticket `, if " +"any." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Posts actions" +msgstr "" + +#: ../../content/applications/websites/forum.rst:353 +msgid "" +"By default, 150 karma points are required to view another user's profile. " +"This value can be configured when creating a new website." +msgstr "" + +#: ../../content/applications/websites/forum.rst:359 +msgid "Moderate a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:361 +msgid "" +"On the forum's front end, the sidebar's :guilabel:`Moderation tools` section" +" gathers the essential moderator functionalities." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Forum sidebar moderation tools" +msgstr "" + +#: ../../content/applications/websites/forum.rst:367 +msgid "" +":guilabel:`To Validate`: access all questions and answers waiting for " +"validation before being displayed to non-moderator users." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Question to validate" +msgstr "" + +#: ../../content/applications/websites/forum.rst:374 +msgid "" +"A question is pending if a user does not have the required karma. The user " +"is not able to post questions or answers while awaiting validation. Only one" +" pending question per user is allowed per forum." +msgstr "" + +#: ../../content/applications/websites/forum.rst:378 +msgid "" +":guilabel:`Flagged`: access all questions and answers that have been flagged" +" as offensive. Click :guilabel:`Accept` to remove the offensive flag or " +":guilabel:`Offensive` to confirm it, then select a reason and click " +":guilabel:`Mark as offensive`. The post is then hidden from users without " +"moderation rights, and 100 karma points are deducted from the offending " +"user's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Offensive reason selection" +msgstr "" + +#: ../../content/applications/websites/forum.rst:386 +msgid "" +":guilabel:`Closed`: access all questions that have been closed. It is " +"possible to :guilabel:`Delete` or :guilabel:`Reopen` them. To close a " +"question, open it, click the ellipsis button (:guilabel:`...`), then " +":guilabel:`Close`, select a :guilabel:`Close Reason`, and click " +":guilabel:`Close post`. The post is then hidden from users without " +"moderation rights." +msgstr "" + +#: ../../content/applications/websites/forum.rst:392 +msgid "" +"When selecting :guilabel:`Spam or advertising` or :guilabel:`Contains " +"offensive or malicious remarks` as the reason, 100 karma points are deducted" +" from the poster's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst:396 +msgid "" +"Create and edit close reasons by going to :menuselection:`Website --> " +"Configuration --> Forum: Close Reasons`. Select :guilabel:`Basic` as " +":guilabel:`Reason Type` if the reason should be used when closing a " +"question, and :guilabel:`Offensive` if it should be used for flagged posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:399 +msgid "" +"Manage all posts by going to :menuselection:`Website --> Configuration --> " +"Forum: Forums`, selecting the forum, and clicking the :guilabel:`Posts` " +"smart button. By clicking the :guilabel:`Actions` button, it is possible to " +":guilabel:`Export`, :guilabel:`Archive`, :guilabel:`Unarchive`, or " +":guilabel:`Delete` one or multiple posts." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:6 +msgid "Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:8 +msgid "" +"Odoo *Live Chat* allows users to communicate with website visitors in real " +"time. With *Live Chat*, leads can be qualified for their sales potential, " +"support questions can be answered quickly, and issues can be directed to the" +" appropriate team for further investigation (or follow up). *Live Chat* also" +" provides the opportunity for instant feedback from customers." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:14 +msgid "Enable Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:16 +msgid "" +"In order to enable *Live Chat*, the *Live Chat* application needs to be " +"installed. This can be done in one of two ways." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:19 +msgid "" +"Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:20 +msgid "" +"In the :menuselection:`Website` application, go to " +":menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email " +"& Marketing` section, check the box next to :guilabel:`Livechat`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of the settings page and the live chat feature for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:28 +msgid "" +"After the :guilabel:`Live Chat` application is installed, a live chat " +":guilabel:`Channel` will be created by default and automatically selected in" +" the drop-down." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:32 +msgid "Create a new live chat channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:34 +msgid "" +"To create a new live chat *Channel*, go to :menuselection:`Main Odoo " +"Dashboard --> Live Chat app --> New`. This will open a blank channel detail " +"form. Enter the name of the new channel in the :guilabel:`Channel Name` " +"field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a live chat channel form for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:42 +msgid "" +"To configure the remaining tabs on the channel detail form " +"(:guilabel:`Operators`, :guilabel:`Options`, :guilabel:`Channel Rules`, and " +":guilabel:`Widgets`), follow the steps below." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:46 +msgid "Operators" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:48 +msgid "" +"*Operators* are the users who will respond to live chat requests from " +"customers. When a user is added as an operator in a live chat channel, they " +"will be able to receive chats from website visitors wherever they are in the" +" database. Chat windows will open in the bottom right corner of the screen." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a live chat pop up window in an Odoo database." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:57 +msgid "" +"The user who originally created the live chat channel will be added as an " +"operator by default." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:59 +msgid "" +"To add additional users, navigate back to the :guilabel:`Website Live Chat " +"Channels` dashboard via the breadcrumbs and click on the appropriate " +":guilabel:`Live Chat Channel`. Then, on the channel detail form, under the " +":guilabel:`Operators` tab, click :guilabel:`ADD` to reveal an " +":guilabel:`Add: Operators` pop-up window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:64 +msgid "" +"In the pop-up window, search for the desired user(s). Then, click the " +"checkbox next to the user(s) to be added, and click :guilabel:`SELECT`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:67 +msgid "" +"New operators can be created and added to the list directly from this pop-" +"up, as well, by clicking :guilabel:`New`, and filling out the " +":guilabel:`Create Operators` pop-up form. When the form is complete, click " +":guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiple record " +"creations)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:72 +msgid "" +"Current operators can be edited (or removed) by clicking on their respective" +" boxes in the :guilabel:`Operators` tab, which reveals a separate " +":guilabel:`Open: Operators` pop-up. In that pop-up, adjust any information " +"as needed, and click :guilabel:`Save`, or click :guilabel:`Remove` to remove" +" that operator from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:78 +msgid "Options" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:80 +msgid "" +"The :guilabel:`Options` tab on the live chat channel details form contains " +"the visual and text settings for the live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:84 +msgid "Livechat button" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:86 +msgid "" +"The *Livechat Button* is the icon that appears in the bottom corner of the " +"website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of an Odoo website emphasizing the livechat button." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:92 +msgid "" +"Change the text in the :guilabel:`Text of the Button` field to update the " +"greeting displayed in the text bubble when the live chat button appears on " +"the website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:95 +msgid "" +"Change the :guilabel:`Livechat Button Color` by clicking a color bubble to " +"open the color selection window. Click the :guilabel:`🔄 (refresh)` icon to " +"the right of the color bubbles to reset the colors to the default selection." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:100 +msgid "" +"Color selection, for the button or header, can be made manually using a " +"slider or through RGB, HSL, or HEX color code entries from the pop-up color " +"selection window that appears when either of the color bubbles are clicked. " +"Different options will be available, depending on your operating system." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:106 +msgid "Livechat window" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:108 +msgid "" +"The *Livechat Window* is the space where the live chat conversation with " +"website visitors takes place." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:111 +msgid "" +"Edit the :guilabel:`Welcome Message` to change the message a visitor sees " +"when they open a new chat session. This message will appear as though it is " +"sent by a live chat operator, and acts as both a greeting and an invitation " +"to continue the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:115 +msgid "" +"Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears " +"in the box where visitors will type their replies." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:118 +msgid "" +"The *Channel Header* is the colored bar at the top of the chat window. The " +":guilabel:`Channel Header Color` can be changed following the same steps as " +"the *Livechat Button Color* above." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:124 +msgid "" +"The Livechat Window with a purple header. The chat input placeholder reads " +"\"Ask Something...\"" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:127 +msgid "Channel rules" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:129 +msgid "" +"The :guilabel:`Channel Rules` tab on the live chat channel details form " +"determines when the *Live Chat Window* opens on the website, by configuring " +"when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:133 +msgid "" +"To create a new channel rule, click :guilabel:`Add a line`. This opens the " +":guilabel:`Open: Rules` pop-up." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a channel's rules form for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:141 +msgid "Create new rules" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:143 +msgid "" +"Fill out the fields on the :guilabel:`Open: Rules` pop-up as instructed " +"below, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:148 +msgid "Live Chat Button" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:150 +msgid "" +"The *Livechat Button* is the icon that appears in the bottom corner of the " +"website. Select from one of the following display options:" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:153 +msgid ":guilabel:`Show` displays the chat button on the page(s)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:154 +msgid "" +":guilabel:`Show with notification` displays the chat button, as well as a " +"floating text bubble next to the button." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:156 +msgid "" +":guilabel:`Open automatically` displays the button and automatically opens " +"the chat window after a specified amount of time (designated in the " +":guilabel:`Open automatically timer` field)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:159 +msgid ":guilabel:`Hide` hides the chat button on the page(s)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:161 +msgid "Chatbot" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:163 +msgid "" +"If a *Chatbot* will be included on this channel, select it from the " +"dropdown. If the chatbot will only be active when no operators are active, " +"check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:167 +msgid "URL Regex" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:169 +msgid "" +"In the :guilabel:`URL Regex` field, input the relative URL of the page where" +" the chat button should appear." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:172 +msgid "Open automatically timer" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:174 +msgid "" +"This field designates the amount of time (in seconds) a page will be open " +"before the chat window will open. If the :guilabel:`Livechat Button` for " +"this rule is not set to :guilabel:`Open automatically`, this field will be " +"ignored." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:178 +msgid "Country" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:180 +msgid "" +"If this channel should only be available to site visitors in specific " +"countries, add them to the :guilabel:`Country` field. If this field is left " +"blank, the channel will be available to all site visitors, regardless of " +"location." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:185 +msgid "" +"In order to track the geographical location of visitors, :guilabel:`GeoIP` " +"must be installed on the database. While this feature is installed by " +"default on *Odoo Online*, *On-Premise* databases will require additional " +":doc:`setup steps `." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:190 +msgid "Widget" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:192 +msgid "" +"The :guilabel:`Widget` tab on the live chat channel details form provides " +"the shortcode for an embeddable website widget. This code can be added to a " +"website to provide access to a live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:196 +msgid "" +"The live chat widget can be added to websites created through Odoo by " +"navigating to the :menuselection:`Website --> Configuration --> Settings`. " +"Then scroll to the :guilabel:`Livechat` section, and select the channel to " +"add to the site. Click :guilabel:`Save` to apply." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:200 +msgid "" +"To add the widget to a website created on a third-party platform, click the " +"first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the " +"code into the `` tag on the site." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:203 +msgid "" +"Likewise, to send a live chat session to a customer, click the second " +":guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent" +" directly to a customer, and once they click the link, it will open a new " +"chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the widget tab for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:212 +msgid "Participate in a conversation" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:214 +msgid "" +"As explained above, *operators* are the users who will respond to live chat " +"requests from customers. The information below outlines the necessary steps " +"for operators participating in live chat conversations on an Odoo database." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:219 +msgid "Set an online chat name" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:221 +msgid "" +"Before participating in a live chat, operators should update their *Online " +"Chat Name*. This is the name that will be displayed to site visitors in the " +"live chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:224 +msgid "" +"To update the :guilabel:`Online Chat Name`, click on the user name in the " +"upper-right corner of any page in the database. Select :guilabel:`My " +"Profile` to open the Profile page. On the right side of the " +":guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field " +"and enter the preferred name." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the My Profile option in Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:233 +msgid "" +"If a users :guilabel:`Online Chat Name` is not set, the name displayed will " +"default to the :guilabel:`User Name`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:237 +msgid "" +"A user has their full name as their :guilabel:`User Name`, but they do not " +"want to include their last name in a live chat conversation. They would then" +" set their :guilabel:`Online Chat Name` to include only their first name." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:0 +msgid "View of user profile in Odoo, emphasizing the Online Chat name field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:246 +msgid "Join or leave a channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:248 +msgid "" +"To join a live chat channel, go to the :menuselection:`Live Chat` app and " +"click the :guilabel:`JOIN` button on the kanban card for the appropriate " +"channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:251 +msgid "" +"Any channel where the user is currently active will show a :guilabel:`LEAVE`" +" button. Click this button to disconnect from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of a channel form and the option to join a channel for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:259 +msgid "" +"*Operators* that do not show any activity in Odoo for more than thirty " +"minutes will be considered disconnected, and subsequently removed from the " +"channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:263 +msgid "Manage live chat requests" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:265 +msgid "" +"When an operator is active in a channel, chat windows will open in the " +"bottom right corner of the screen, no matter where they are in the database." +" They can participate in conversations without leaving their current " +"location." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:270 +msgid "" +"Conversations can also be accessed by clicking the :guilabel:`Conversations`" +" icon in the menu bar." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:0 +msgid "View of the menu bar in Odoo emphasizing the conversations icon." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:277 +msgid "" +"Live chat conversations can also be viewed by navigating to " +":menuselection:`Dashboard --> Discuss`. New conversations will appear in " +"bold under the :guilabel:`LIVECHAT` heading along the left panel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of the discuss application with a message sent through live chat in " +"Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:284 +msgid "" +"Click on a conversation in the left panel to select it. This will open the " +"conversation. From this view, an operator can participate in the chat the " +"same as they would in the normal chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:288 +msgid "" +":doc:`Get Started with Discuss " +"`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:289 +msgid ":doc:`/applications/websites/livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:3 +msgid "Chatbots" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:5 +msgid "" +"A *Chatbot* is a program designed to mimic a conversation with a live human." +" Chatbots are assigned a script of pre-written steps to follow. The scripts " +"are designed to anticipate a visitor's potential response, and lead them " +"through a series of questions and answers the same way a live team member " +"would." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:10 +msgid "" +"Chatbots can be customized to fill various roles, from customer support, to " +"creating leads, to collecting contact information. The goal of the chatbot " +"depends on the page of the website they are assigned, and the messages " +"included in the script, among other criteria." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the chat window with a helpdesk ticket created in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:19 +msgid "Build a chatbot" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:21 +msgid "" +"Before creating a new chatbot, the *Live Chat* application must first be " +"installed on the database. This can be done directly from the " +":menuselection:`Apps` menu by searching for `Live Chat` in the " +":guilabel:`search bar` and clicking :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:25 +msgid "" +"Alternatively, *Live Chat* can be installed and enabled by navigating to the" +" :menuselection:`Website application --> Configuration --> Settings`, and " +"checking the box labeled :guilabel:`Livechat`. Once enabled, the database " +"will refresh, and the *Live Chat* application is accessible." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:29 +msgid "" +"Once the *Live Chat* application has been installed on the database, open " +"it, and go to :menuselection:`Configuration --> Chatbots`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:33 +msgid "" +"When the *Live Chat* app is installed, a sample chatbot is created, named " +"*Welcome Bot*. This chatbot has a pre-configured script that walks through a" +" few basic steps, including asking for a visitor's email address, and " +"forwarding the conversation to an operator." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:37 +msgid "" +"*Welcome Bot* can be used as a starting point. The existing steps can be " +"edited or removed, and new steps can be added to customize the script, as " +"needed." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:40 +msgid "*Welcome Bot* can be deleted (or archived)." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "View of the Welcome Bot script in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:46 +msgid "" +"To create a new chatbot, navigate to the :guilabel:`Chatbot` page " +"(:menuselection:`Live Chat app --> Configuration --> Chatbots`) and click " +":guilabel:`New`. This opens a blank chatbot details page." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:49 +msgid "" +"On the blank chatbot details page, enter a name in the :guilabel:`Chatbot " +"Name` field and click on the :guilabel:`Edit Image` icon in the upper right " +"corner of the form to add a photo." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:53 +msgid "Chatbot scripts" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:55 +msgid "" +"Once the new chatbot has been created and named, the next step is to create " +"a script. Chatbot conversations follow an accompanying script. These scripts" +" are comprised of lines of dialogue, each designed to either deliver or " +"capture information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:59 +msgid "" +"To create a chatbot script, navigate to the :guilabel:`Script` tab of the " +"chatbot details page, and click :guilabel:`Add a Line` to open the " +":guilabel:`Create Script Steps` pop-up form." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:62 +msgid "" +"This form must be filled out for each line of text (dialogue) that the " +"chatbot could potentially deliver during the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:65 +msgid "" +"First, enter the content of the message in the :guilabel:`Message` field. " +"Then, select an option from the :guilabel:`Step Types` drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:69 +msgid "Step types" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:71 +msgid "" +"The :guilabel:`Step Type` selected depends on the intended purpose of the " +"message. The available options in the :guilabel:`Step Type` drop-down are " +"listed below, as well as their use, and any additional information:" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:76 +msgid "Text" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:78 +msgid "" +"This step is used for messages where no answer is expected (or necessary). " +"Text steps can be used for greetings and/or to deliver information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:82 +msgid "" +"Text step types are only intended to deliver information, and do not allow " +"for any visitor input. As such, they need to be followed by additional steps" +" to continue the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:86 +msgid "Question" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:88 +msgid "" +"This step asks a question and provides a set of answers. The visitor clicks " +"on one answer, which either leads to a new step in the conversation, or can " +"lead to an optional link to a new webpage." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:92 +msgid "" +"It is helpful to add a catchall answer to question steps (ex: \"Something " +"else\"). This helps visitors continue the conversation, even if their needs " +"don't exactly fit with any of the other answers." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:97 +msgid "Email" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:99 +msgid "" +"This step prompts visitors to provide their email address, which is stored " +"and can be used by team members later to follow up with additional " +"information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:102 +msgid "" +"The only accepted inputs for this step type are email addresses that are in " +"a valid format. If a visitor attempts to enter anything other than a valid " +"email address, the chatbot responds with a message stating it does not " +"recognize the information submitted." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +msgid "View of a chatbot responding to an invalid email." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:111 +msgid "Phone" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:113 +msgid "" +"Similar to email, this step type prompts the visitor to enter their phone " +"number, which can be used at a later time to follow up with additional " +"information, or to schedule demos, and more." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:117 +msgid "" +"Due to the vast number of formats used for phone numbers worldwide, " +"responses to this step type are **not** validated for formatting." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:121 +msgid "Forward to Operator" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:123 +msgid "" +"This step forwards the conversation to an active live chat operator, so that" +" they can continue assisting the visitor. As the conversation transcript is " +"passed on to the operator they are able to pick up where the chatbot left " +"off. This not only saves time for all parties involved, it can also help " +"qualify conversations before they reach live human operators." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:129 +msgid "" +"If no active operator is available on the channel, the chatbot continues the" +" conversation with the visitor. Therefore, additional steps should be added " +"after this one to ensure that there is no abrupt end to the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "" +"View of a chatbot follow up messages when no live chat operator is " +"available." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:138 +msgid "Free Input/Multi-Line" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:140 +msgid "" +"The free input step allows visitors to respond to questions without " +"providing pre-written responses. Information provided in these responses is " +"stored in the chat transcripts." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:143 +msgid "" +"Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-" +"Line)` depending on the type and amount of information being requested from " +"the visitor." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:147 +msgid "Create Lead" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:149 +msgid "" +"This step creates a lead in the *CRM* application. Select an option from the" +" :guilabel:`Sales Team` drop-down to assign the created lead to a specific " +"team." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:153 +msgid "Create Ticket" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:155 +msgid "" +"This step creates a :doc:`ticket " +"` in the " +"*Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` " +"drop-down to assign the created ticket to a specific team." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:160 +msgid "Only if" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:162 +msgid "" +"Chatbot scripts operate on an if/then basis, which means the next question " +"presented to the visitor is determined by the answer they provide to the " +"previous question." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:165 +msgid "" +"To continue the progression of the conversation, the form for a new step " +"contains a field labeled :guilabel:`Only If`. This field is where the " +"progression of questions is defined." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:168 +msgid "" +"If a step is intended to follow all of the previous messages, this field can" +" be left empty. However, if a message should **only** be sent conditionally," +" based on a previous response (or several previous responses), those " +"responses need to be added to this field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:173 +msgid "" +"If there are any selections made in the :guilabel:`Only If` field, the step " +"will **not** be shown in a conversation unless **all** of the answers have " +"been selected. Only include selections in this field if they are necessary " +"for this step to be displayed." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:178 +msgid "" +"In the *Welcome Bot* script, a visitor can ask about pricing information. If" +" the visitor selects this response, a step is included to forward the " +"conversation to an operator. The chatbot first sends a message informing the" +" visitor that it is checking to see if an operator is available to chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:183 +msgid "" +"However, this message should **only** be delivered if the visitor requests " +"pricing information. In that situation, the conversation would proceed as " +"below:" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:186 +msgid "Welcome Bot: \"*What are you looking for?*\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:187 +msgid "Visitor: \"**I have a pricing question.**\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:188 +msgid "" +"Welcome Bot: \"*Hmmm, let me check if I can find someone that could help you" +" with that...*\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:190 +msgid "" +"In the details form for the :guilabel:`Text` step, the *I have a pricing " +"question* response has been selected in the :guilabel:`Only If` field. As " +"such, this step is **only** shown in conversations where that response has " +"been selected." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "View of the new message form emphasizing the Only If field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:199 +msgid "Script testing" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:201 +msgid "" +"In order to ensure all visitors have a satisfactory experience with the " +"chatbot, each message needs to lead to a natural conclusion. Chatbot scripts" +" should be tested to confirm there are no dead-ends, and to get an " +"understanding of what the visitor sees when they interact with the chatbot." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:206 +msgid "" +"If there is an answer or input provided by the visitor that is **not** " +"assigned a corresponding follow-up response, the conversation stops (*dead-" +"end*). Since the visitor cannot re-engage the chatbot, they will have to re-" +"start the conversation, by refreshing the chat window, or their browser." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:211 +msgid "" +"To test the performance of a chatbot, first click on the :guilabel:`Test` " +"button at the top-left of the chatbot script page. Then, upon being " +"redirected to the testing screen, answer the chatbot prompts the same way a " +"potential site visitor would." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:215 +msgid "" +"When the script has reached an end-point, the message *Conversation " +"ended...Restart* appears at the bottom of the chat window. To begin the " +"conversation at the beginning of the script, click on :guilabel:`Restart`. " +"To return to the script page, click :guilabel:`Back to edit mode` at the top" +" of the page." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:221 +msgid "Add chatbot to a channel" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:223 +msgid "" +"After a chatbot has been created and tested, it needs to be added to a live " +"chat channel." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:225 +msgid "" +"First, open the :menuselection:`Live Chat` application, and select the " +"kanban card for a :guilabel:`Channel`, or create a :doc:`new one " +"`. Click on the :guilabel:`Channel Rules` " +"tab. Then, open an existing rule, or create a new one by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:230 +msgid "" +"On the :guilabel:`Create Rules` pop-up detail form, choose the appropriate " +"chatbot in the :guilabel:`Chatbot` field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:233 +msgid "" +"If the chatbot should **only** be active if there are no available live chat" +" operators, check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +msgid "View of the channel rules emphasizing the chatbot field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:241 +msgid ":doc:`Live chat channel rules `" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:3 +msgid "Ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:5 +msgid "" +"At the end of a *Live Chat* conversation, customers have the opportunity to " +"rate the quality of support they received from the live chat *operator*. " +"Customers provide ratings as soon as they close the conversation. This " +"allows operators to receive immediate feedback on their performance. It also" +" allows customers the chance to share any final comments before leaving the " +"chat window." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:11 +msgid "Rate live chat conversations" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:13 +msgid "" +"Customers end a *live chat* conversation by clicking the :guilabel:`X` in " +"the upper right-hand corner of the chat window. They are then prompted to " +"select an icon that reflects their level of satisfaction. The icons " +"represent the following ratings:" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:17 +msgid "**Satisfied** - *green smiling face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:18 +msgid "**Okay** - *yellow neutral face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:19 +msgid "**Dissatisfied** - *red frowning face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the chat window from a user's side for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:26 +msgid "" +"When customers end a conversation, a field marked :guilabel:`Receive a copy " +"of this conversation` appears under the *ratings* icons. Customers can enter" +" their email either before or after they submit a rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:30 +msgid "" +"If the customer selects :guilabel:`Satisfied (smile)` icon, they are " +"presented with a thank you message and a :guilabel:`Close Conversation` " +"link." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of customer's live chat window with thank you message." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:37 +msgid "" +"If the customer selects either :guilabel:`Okay (neutral)` icon or " +":guilabel:`Dissatisfied (frown)` icon, a text box will appear. Customers can" +" add comments in this text box to explain why they chose this rating. This " +"message will be sent to the live chat operator, along with the rating icon." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of a chat window from an operator's window highlighting a rating for " +"Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:46 +msgid "Publish customer ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:48 +msgid "" +"To publish a channel's ratings on the website, first navigate to a live chat" +" channel's record by going to the :menuselection:`Live Chat` app and " +"clicking on the kanban card for that team. Then click on the :guilabel:`Go " +"to Website` smart button. This will open the :guilabel:`Live Chat Channel " +"Statistics` page." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:53 +msgid "" +"In the upper right corner of the page, click the red :guilabel:`Unpublished`" +" slider. The slider changes from :guilabel:`Unpublished` to " +":guilabel:`Published`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the published ratings on the portal for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:61 +msgid "" +"The customer notes that are submitted with the rating will *not* be " +"published on the website. These are kept internal. Only a statistical " +"overview of the operators' performance for the *channel* appears on the " +"website." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:66 +msgid "Add ratings page to site" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:68 +msgid "" +"Once the rating page has been published, it has to be manually added to the " +"website. To do this, go to the main Odoo dashboard and open the *Website* " +"application. :menuselection:`Website app--> Site --> Content --> Pages`, " +"then click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:72 +msgid "" +"This will open a :guilabel:`New Page` pop-up window. In the :guilabel:`Page " +"Title` field, enter `livechat`. This acts as the URL for the published " +"webpage." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:76 +msgid "" +"The URL *must* be named `livechat` in order for the database to recognize " +"and connect the ratings page. After the page has been published, the page " +"title can be changed later under the :guilabel:`Menu Editor`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:80 +msgid "" +"Click :guilabel:`Create`, and the newly created webpage will open. The " +":guilabel:`Webpage Editor` appears in the right panel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:83 +msgid "" +"The page lists the names of the :guilabel:`Live Chat Channels` whose ratings" +" pages have been published. On the left side of the channel name is a speech" +" bubble icon, which users can click on to go to the ratings' page for the " +"respective channel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of the webpage for Live Chat ratings emphasizing the channel icon." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:91 +msgid "" +"Make any desired changes or additions to this page, then click " +":guilabel:`Save` in the top right of the webpage editor. The website editor " +"side panel closes, and the webpage remains on the screen." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:94 +msgid "" +"To publish the `livechat` webpage, return to the list of webpages by " +"navigating to :menuselection:`Site --> Content --> Pages`. Click the " +"checkbox to the left of `livechat` in the list of pages to select the page " +"and highlight the line. Then, click the checkbox under the column labeled " +":guilabel:`Is Published`. The field with the checkbox is highlighted in " +"white. Click the checkbox a second time to activate the :guilabel:`Is " +"Published` box. The webpage is now published." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of the list of pages for a website with the 'is published' box " +"emphasized." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:104 +msgid "" +"Once the page has been added to the site, ratings are set to be published by" +" default. However, individual ratings can be manually selected to be hidden " +"from the public. The rating will still be included in internal reports, and " +"can still be viewed by internal teams. However, public website visitors and " +"portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:109 +msgid "" +"See :ref:`Hide individual ratings ` for more" +" information." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:112 +msgid "Customer ratings report" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:114 +msgid "" +"The :guilabel:`Customer Ratings` report (:menuselection:`Live Chat --> " +"Report --> Customer Ratings`) displays an overview of the ratings received " +"on individual support tickets, as well as any additional comments submitted " +"with the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the customer ratings report in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:122 +msgid "" +"The report defaults to a kanban view, with each rating represented by a " +"different card. To switch to a different view, click on one of the icons in " +"the upper-right corner of the screen. The report is available in *list* " +"view, *pivot* view, and *graph* view." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:126 +msgid "" +"Click on an individual rating to see additional details about the " +"conversation, and the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:131 +msgid "Hide individual ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:133 +msgid "" +"Ratings are set to be published by default. However, individual ratings can " +"be manually selected to be hidden from the public. The rating will still be " +"included in internal reports, and can still be viewed by internal teams. " +"However, public website visitors and portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:137 +msgid "" +"To hide a rating, go to :menuselection:`Live Chat app --> Reports --> " +"Customer Ratings`. Click on the kanban card for the rating to be hidden. On " +"the individual rating's detail page, check the box labeled " +":guilabel:`Visible Internally Only`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of an individual rating's detail page with the visible internally " +"setting checked." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:146 +msgid ":doc:`/applications/websites/livechat`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:147 +msgid ":doc:`responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:148 +msgid ":doc:`/applications/websites/website`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:3 +msgid "Commands and canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:5 +msgid "" +"In the Odoo *Live Chat* application, *commands* allow the user to perform " +"specific actions both inside the chat window, and through other Odoo " +"applications. The *Live Chat* app also includes *canned responses*. These " +"are customized, pre-configured substitutions that allow users to replace " +"shortcut entries in place of longer, well-thought out responses to some of " +"the most common questions and comments." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:11 +msgid "" +"Both commands and canned responses save time, and allow users to maintain a " +"level of consistency throughout their conversations." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:15 +msgid "Execute a command" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:17 +msgid "" +"Live chat *commands* are keywords that trigger pre-configured actions. When " +"a live chat *operator* is participating in a conversation with a customer or" +" website visitor, they can execute a command by typing `/`, followed by the " +"command." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:21 +msgid "" +"Commands, and the resulting actions, are only visible in the conversation " +"window for the live chat operator. A customer will not see any commands that" +" an operator uses in a conversation from their view of the chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:29 +msgid "More information about each available command can be found below." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:32 +msgid "Help" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:34 +msgid "" +"If an operator types `/help` in the chat window, an informative message that" +" includes the potential entry types an operator can make is displayed." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:37 +msgid "" +"Type `@username` to mention a user in the conversation. A notification will " +"be sent to that user's inbox or email, depending on their notification " +"settings." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:39 +msgid "Type `#channel` to mention a *Discuss* channel." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:40 +msgid "Type `/command` to execute a command." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:41 +msgid "" +"Type `:shortcut` to insert a :ref:`canned response `." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the message generated from using the /help command in Odoo Live " +"Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:48 +msgid ":doc:`/applications/productivity/discuss/overview/get_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:49 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:52 +msgid "Helpdesk & Helpdesk search" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:54 +msgid "" +"The `/helpdesk` and `/helpdesk_search` commands allow operators to both " +"create helpdesk tickets directly from a conversation, and search through " +"existing tickets by keyword or ticket number." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:58 +msgid "" +"The `/helpdesk` and `/helpdesk_search` commands can only be used if the " +"*Helpdesk* app has been installed, and *Live Chat* has been activated on a " +"*Helpdesk* team. To activate :guilabel:`Live Chat`, go to " +":menuselection:`Helpdesk application --> Configuration --> Teams`, and " +"select a team. Scroll to the :guilabel:`Channels` section and check the box " +"labeled :guilabel:`Live Chat`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:64 +msgid "Create a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:66 +msgid "" +"If an operator types `/helpdesk` in the chat window, the conversation is " +"used to create a *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:70 +msgid "" +"In version 16.3, the command to create a new ticket is `/ticket`. This only " +"applies to databases running version 16.3." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:73 +msgid "" +"After entering the `/helpdesk` command, type a title for the ticket into the" +" chat window, then press `Enter`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the results from a helpdesk search in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:80 +msgid "" +"The newly created ticket will be added to the *Helpdesk* team that has live " +"chat enabled. If more than one team has live chat enabled, the ticket will " +"automatically be assigned based on the team's priority." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:84 +msgid "" +"The transcript from the conversation will be added to the new ticket, under " +"the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:87 +msgid "" +"To access the new ticket, click on the link in the chat window, or go to the" +" :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on " +"the kanban card for the appropriate team." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:92 +msgid "Search for a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:94 +msgid "" +"If an operator types `/helpdesk_search` in the chat window, they can search " +"through *Helpdesk* tickets by ticket number or keyword." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:98 +msgid "" +"In version 16.3, the command to search through *Helpdesk* tickets is " +"`/search_tickets`. This only applies to databases running version 16.3." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:101 +msgid "" +"After entering the `/helpdesk_search` command, type a keyword or ticket " +"number, then press `Enter`. If one or more related tickets are found, a list" +" of links will be generated in the conversation window." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:110 +msgid "" +"Results from the search command will only be seen by the operator, not the " +"customer." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:113 +msgid "History" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:115 +msgid "" +"If an operator types `/history` in the chat window, it will generate a list " +"of the most recent pages the visitor has viewed on the website (up to 15)." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the results from a /history command in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:123 +msgid "Lead" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:125 +msgid "" +"By typing `/lead` in the chat window, an operator can create a *lead* in the" +" *CRM* application." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "View of the results from a /lead command in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:132 +msgid "" +"The `/lead` command can only be used if the *CRM* app has been installed." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:134 +msgid "" +"After typing `/lead`, create a title for this new lead, then press `Enter`. " +"A link with the lead title appears. Click the link, or navigate to the " +":menuselection:`CRM` app to view the :guilabel:`Pipeline`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:139 +msgid "" +"The link to the new lead can only be seen and accessed by the operator, not " +"the customer." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:141 +msgid "" +"The transcript of that specific live chat conversation (where the lead was " +"created) is added to the :guilabel:`Internal Notes` tab of the lead form." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:144 +msgid "" +"On the :guilabel:`Extra Information` tab of the lead form, the " +":guilabel:`Source` will be listed as :guilabel:`Livechat`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:148 +msgid "Leave" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:150 +msgid "" +"If an operator types `/leave` in the chat window, they can automatically " +"exit the conversation. This command does not cause the customer to be " +"removed from the conversation, nor does it automatically end the " +"conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:155 +msgid ":doc:`/applications/sales/crm/acquire_leads`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:156 +msgid ":doc:`/applications/services/helpdesk/overview/getting_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:161 +msgid "Canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:163 +msgid "" +"*Canned responses* are customizable inputs where a *shortcut* stands in for " +"a longer response. An operator will enter the shortcut, and it will " +"automatically be replaced by the expanded *substitution* response in the " +"conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:168 +msgid "Create canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:170 +msgid "" +"To create a new canned response, go to :menuselection:`Live Chat app --> " +"Configuration --> Canned Responses --> New`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:173 +msgid "" +"From here, type the shortcut command into the :guilabel:`Shortcut` field." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:175 +msgid "" +"Then, click into the :guilabel:`Substitution` field, and enter the custom " +"message that will be sent to visitors in place of the shortcut. Click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:179 +msgid "" +"Try to connect the shortcut to the topic of the substitution. The easier it " +"is for the operators to remember, the easier it will be to use the canned " +"responses in conversations." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:183 +msgid "Use canned responses in a live chat conversation" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:185 +msgid "" +"To use a canned response during a live chat conversation, type a colon (`:`)" +" into the chat window, followed by the shortcut." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:189 +msgid "" +"An operator is chatting with a visitor. As soon as they type `:` they would " +"see a list of available responses. They can manually select one from the " +"list, or continue to type. If they want to use the canned response `'I am " +"sorry to hear that.'`, they would type `:sorry`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of a chat window and the use of a canned response in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:198 +msgid "" +"Typing `:` into a chat window on its own will generate a list of available " +"canned responses. Responses can be manually selected from the list, in " +"addition to the use of shortcuts." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:0 +msgid "View of a chat window and the list of available canned responses." +msgstr "" + +#: ../../content/applications/websites/website.rst:8 +msgid "Website" +msgstr "" + +#: ../../content/applications/websites/website.rst:10 +msgid "" +"Discover the best **Open-Source Website Builder** and learn how to build " +"beautiful websites that convert visitors into leads or revenues." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3 +msgid "Address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:5 +msgid "" +"You can use the Google Places API on your website to ensure that your users'" +" delivery addresses exist and are understood by the carrier. The Google " +"Places API allows developers to access detailed information about places " +"using HTTP requests. The autocompletion predicts a list of places when the " +"user starts typing the address." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst-1 +msgid "Address autocomplete example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:13 +msgid "" +"`Google Maps Platform `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:14 +msgid "" +"`Google Developers Documentation: Google Places API " +"`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:18 +msgid "" +"To do so, go to :menuselection:`Website --> Configuration --> Settings` and " +"enable :guilabel:`Address Autocomplete` in the :guilabel:`SEO` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst-1 +msgid "Enable address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:24 +msgid "" +"Insert your :guilabel:`Google Places API key` in the :guilabel:`API Key` " +"field. If you don't have one, create yours on the `Google Cloud Console " +"`_ and follow these steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:28 +msgid "Step 1: Enable the Google Places API" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:30 +msgid "**Create a New Project:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:32 +msgid "" +"To enable the **Google Places API**, you first need to create a project. To " +"do so, click :guilabel:`Select a project` in the top left corner, " +":guilabel:`New Project`, and follow the prompts to set up your project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:34 +msgid "**Enable the Google Places API:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:36 +msgid "" +"Go to the :guilabel:`Enabled APIs & Services` and click :guilabel:`+ ENABLE " +"APIS AND SERVICES.` Search for :guilabel:`\"Places API\"` and select it. " +"Click on the :guilabel:`\"Enable\"` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:39 +msgid "" +"Google's pricing depends on the number of requests and their complexity." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:42 +msgid "Step 2: Create API Credentials" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:44 +msgid "" +"Go to `APIs & Services --> Credentials " +"`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:46 +msgid "**Create credentials:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:48 +msgid "" +"To create your credentials, go to :guilabel:`Credentials`, click " +":guilabel:`Create Credentials`, and select :guilabel:`API key`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:50 +msgid "Restrict the API Key (Optional)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:52 +msgid "" +"For security purposes, you can restrict the usage of your API key. You can " +"go to the :guilabel:`API restrictions` section to specify which APIs your " +"key can access. For the Google Places API, you can restrict it to only allow" +" requests from specific websites or apps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:57 +msgid "Save Your API Key: Copy your API key and securely store it." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:58 +msgid "Do not share it publicly or expose it in client-side code." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:3 +msgid "Cookies bar" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:5 +msgid "" +"Cookies are small text files sent to your device when you visit a website. " +"They are processed and stored by your browser and contain information about " +"your visit, such as login data, location, language, etc. There are two main " +"types of cookies:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:9 +msgid "" +"Essential cookies, which are necessary for the website to function properly;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:10 +msgid "" +"Non-essential or optional cookies, which are used to analyze your behavior " +"or display advertisements." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1 +msgid "Example of a cookies bar with the popup layout." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:17 +msgid "" +"Notifying users about data collection, as well as its methods and purposes, " +"is required by data protection laws such as `GDPR `_. " +"Cookies bars are commonly used to fulfill this obligation in a user-friendly" +" and transparent manner. They are displayed immediately upon a user's first " +"visit to inform them that the website uses cookies and let them decide " +"whether they want to store non-essential cookies on their device." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:26 +msgid "" +"To enable the cookies bar on your Odoo website, go to " +":menuselection:`Website --> Configuration` and enable :guilabel:`Cookies " +"Bar` in the :guilabel:`Privacy` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:29 +msgid "" +"You can :ref:`customize the appearance of your cookies bar ` and :ref:`edit the content of the related Cookie Policy " +"page `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:35 +msgid "Customization" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:37 +msgid "" +"To adapt the display of the cookies bar, click :guilabel:`Edit` and select " +"the :guilabel:`Cookies Bar` building block in the :guilabel:`Invisible " +"Elements` at the bottom of the panel. Customize it using the options in the " +":guilabel:`Customize` tab in the edit panel. Three :guilabel:`Layouts` are " +"available:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:42 +msgid ":guilabel:`Discrete`: thin bar" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:43 +msgid ":guilabel:`Classic`: banner" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44 +msgid "" +":guilabel:`Popup`: you can change the popup's :guilabel:`Position` to the " +":guilabel:`Top`, :guilabel:`Middle`, or :guilabel:`Bottom` of the screen." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:47 +msgid "You can also:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:49 +msgid "modify the :guilabel:`Size` of the cookies bar;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:50 +msgid "" +"enable :guilabel:`Backdrop` to gray out the page in the background when the " +"cookies bar is displayed on the screen;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:52 +msgid "" +"further customize the appearance of the cookies bar using :guilabel:`Block` " +"and/or :guilabel:`Column` customization options, which are available after " +"clicking anywhere in the building block." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:56 +msgid "" +"To edit the contents of the cookies bar (i.e., the consent message), click " +"directly in the building block." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1 +msgid "Odoo Website's edit panel to customize the cookies bar." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:65 +msgid "Cookie policy" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:67 +msgid "" +"When you enable the cookies bar for your website, Odoo creates the **Cookie " +"Policy** page (`/cookie-policy`) with the list of essential and optional " +"cookies. To access it, click the :guilabel:`Cookie Policy` hyperlink in the " +"cookies bar or open the page from :menuselection:`Website --> Site --> " +"Pages`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:72 +msgid "" +"The contents of the page can be adapted based on your website's features and" +" characteristics if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:76 +msgid "" +"You could add a link providing access to this page, in your website's " +"footer, for example." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:3 +msgid "Multiple websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:5 +msgid "" +"Odoo allows you to create multiple websites from the same database. This can" +" be useful, for example, if you have multiple brands operating under your " +"organization, or to create separate websites for different " +"products/services, or different audiences. In these cases, having different " +"websites can help avoid confusion and make it easier to tailor your digital " +"outreach strategies and reach your target audience." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:11 +msgid "" +"Each website can be designed and configured independently with its own " +":doc:`domain name `, theme, pages, " +"menus, :doc:`languages `, :doc:`products " +"<../../ecommerce/managing_products/products>`, assigned sales team, etc. " +"They can also :ref:`share content and pages `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:18 +msgid "" +"Duplicate content (i.e., pages and content shared between multiple websites)" +" can have a negative impact on :doc:`../pages/seo`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:22 +msgid "Website creation" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:24 +msgid "To create a new website, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:26 +#: ../../content/applications/websites/website/configuration/multi_website.rst:142 +msgid "Go to :menuselection:`Website --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:27 +msgid "Click :guilabel:`+ New Website`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "New website button" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:32 +msgid "" +"Specify the :guilabel:`Website Name` and :guilabel:`Website domain`. Each " +"website must be published under its own :doc:`domain " +"`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:34 +msgid "" +"Adapt the :guilabel:`Company name`, :guilabel:`Languages` and " +":guilabel:`Default language` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:36 +msgid "Click the :guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:38 +msgid "You can then start building your new website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:41 +msgid "" +"By default, all website-related apps that you have installed (e.g. " +"**eCommerce**, **Forum**, **Blog**, etc.) and their related website pages " +"are also available on the new website. You can remove them by amending the " +"website's menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:46 +msgid "Switching websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:48 +msgid "" +"To switch from one website to another, click the menu next to the " +":guilabel:`+New` button in the top right corner and select the website you " +"want to switch to." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Website selector" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:55 +msgid "" +"When you switch websites, you are redirected to the other website, to the " +"same page (URL) as the current one. If the page you are currently viewing " +"does not exist on the other website, you are redirected to a 404 error page." +" Once redirected, click :guilabel:`Create page` to create the page." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "Create a page from a 404 error page" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:64 +msgid "Website-specific configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:66 +msgid "" +"Most website settings are website-specific, which means they can be " +"enabled/disabled per website. To adapt the settings for a website, go to " +":menuselection:`Website --> Configuration --> Settings`. Select the desired " +"website in the field :guilabel:`Settings of Website` at the top of the " +":guilabel:`Settings` page, in the **yellow** banner. Then, adapt the options" +" for that specific website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:73 +msgid "" +"Websites are created with the default settings; the settings are not copied " +"from one website to the other." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:75 +msgid "" +"In a :doc:`multi-company environment <../../../general/users/companies>`, " +"each website can be linked to a specific company in your database so that " +"only company-related data (e.g., products, jobs, events, etc.) is displayed " +"on the website. To display company-specific data, set the desired company in" +" the :guilabel:`Company` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:83 +msgid "Content availability" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:85 +msgid "" +"By default, pages, products, events, etc. created from the frontend (using " +"the :guilabel:`+New` button) are only available on the website from which it" +" was created. Records created from the backend, however, are made available " +"on all websites by default. The content's availability can be changed in the" +" backend, in the :guilabel:`Website` field. For example, for products, go to" +" :menuselection:`eCommerce --> Products`, then select the product and go to " +"the :guilabel:`Sales` tab. For forums, go to :menuselection:`Configuration " +"--> Forums`, then select the forum." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Website field in Forum form" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:98 +msgid "Records and features can be made available:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:100 +msgid "On all websites: leave the :guilabel:`Website` field empty;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:101 +msgid "Only on one website: set the :guilabel:`Website` field accordingly;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:102 +msgid "" +"On some websites: in this case, you should duplicate the item and set the " +":guilabel:`Website` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:106 +msgid "Website pages" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:108 +msgid "" +"To modify the website on which a page is to be published, proceed as " +"follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:110 +msgid "Go to :menuselection:`Website --> Site --> Pages`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:111 +msgid "" +"Open the search panel and select the website on which the page is currently " +"published." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "Display pages per website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:116 +msgid "Tick the check box next to the page(s) you want to change." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:117 +msgid "" +"Click the :guilabel:`Website` field and select the website, or empty it to " +"publish the page on all websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:121 +msgid "" +"Each website must have its own homepage; you may not use the same homepage " +"for several websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:124 +msgid "eCommerce features" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:126 +msgid "" +"eCommerce features such as products, eCommerce categories, pricelists, " +"discounts, payment providers, etc. can be restricted to :ref:`a specific " +"website `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:132 +msgid "" +"You can :doc:`allow your customers to use the same account " +"<../../ecommerce/ecommerce_management/customer_accounts>` on all of your " +"websites by enabling the :guilabel:`Shared Customer Accounts` check box in " +"the website settings." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:137 +msgid "Pricing" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:139 +msgid "" +"Products can be priced differently based on the website using " +":ref:`pricelists `. The following configuration is " +"required:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:143 +msgid "" +"Scroll down to the :guilabel:`Shop - Products` section and select the " +":guilabel:`Pricelists` option :guilabel:`Multiple prices per product`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:145 +msgid "" +"Click :guilabel:`Pricelists` to define new pricelists or edit existing ones." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:146 +msgid "" +"Select the pricelist or click :guilabel:`New` to create a new one, then " +"select the :guilabel:`Configuration` tab and set the :guilabel:`Website` " +"field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:150 +#: ../../content/applications/websites/website/reporting.rst:5 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:155 +msgid "" +"Each website has its own :ref:`analytics `. To " +"switch between websites, click the buttons in the upper right corner." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Switch websites in analytics" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:162 +msgid "Other reporting data" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:164 +msgid "" +"Other reporting data such as eCommerce dashboard data, online sales analyses" +" and visitors can be grouped by website if necessary. Open the search panel " +"and select :guilabel:`Group by --> Website`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:3 +msgid "Forms spam protection" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:5 +msgid "" +":ref:`Cloudflare Turnstile ` and :ref:`Google " +"reCAPTCHA v3 ` protect website forms against spam and " +"abuse. They attempt to distinguish between human and bot submissions using " +"non-interactive challenges based on telemetry and visitor behavior." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:10 +msgid "" +"**Cloudflare Turnstile is recommended** as it is possible to add an " +"interactive check if the automated check fails. Also, Google reCAPTCHA v3 is" +" limited to `1 million assessments per month per domain " +"`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:15 +msgid "" +"All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, " +":guilabel:`Newsletter Popup` snippets, and the eCommerce :guilabel:`Extra " +"Step During Checkout` form are protected by both tools." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:20 +msgid "" +"`Cloudflare Turnstile's documentation " +"`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:21 +msgid "" +"`Google's reCAPTCHA v3 guide " +"`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:26 +msgid "Cloudflare Turnstile configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:29 +msgid "On Cloudflare" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:31 +msgid "" +"`Create `_ a Cloudflare account or use " +"an existing one and `log in `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:33 +msgid "On the dashboard navigation sidebar, click :guilabel:`Turnstile`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:34 +msgid "On the :guilabel:`Turnstile Sites` page, click :guilabel:`Add Site`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:35 +msgid "Add a :guilabel:`Site name` to identify it easily." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:36 +msgid "" +"Enter or select the website's :guilabel:`Domain` (e.g., *example.com* or " +"*subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:37 +msgid "Select a :guilabel:`Widget Mode`:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:39 +msgid "" +"The :guilabel:`Managed` mode is **recommended**, as visitors can be prompted" +" to check a box confirming they are human if deemed necessary by Turnstile." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Cloudflare Turnstile human verification widget" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:45 +msgid "" +"For the :guilabel:`Non-interactive` and :guilabel:`Invisible` modes, " +"visitors are never prompted to interact. In :guilabel:`Non-interactive` " +"mode, a loading widget can be displayed to warn visitors that Turnstile " +"protects the form; however, the widget is not supported by Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:50 +msgid "" +"If the Turnstile check fails, visitors are not able to submit the form, and " +"the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Cloudflare Turnstile verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:56 +#: ../../content/applications/websites/website/pages.rst:27 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "Adding a website to Cloudflare Turnstile" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:61 +msgid "" +"The generated keys are then displayed. Leave the page open for convenience, " +"as copying the keys in Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:65 +#: ../../content/applications/websites/website/configuration/spam_protection.rst:109 +msgid "On Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:67 +msgid "" +"From the database dashboard, click :guilabel:`Settings`. Under " +":guilabel:`Integrations`, enable :guilabel:`Cloudflare Turnstile` and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:69 +msgid "" +"Open the Cloudflare Turnstile page, copy the :guilabel:`Site Key`, and paste" +" it into the :guilabel:`CF Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:71 +msgid "" +"Open the Cloudflare Turnstile page, copy the :guilabel:`Secret Key`, and " +"paste it into the :guilabel:`CF Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:73 +#: ../../content/applications/websites/website/configuration/spam_protection.rst:125 +#: ../../content/applications/websites/website/configuration/translate.rst:95 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:76 +msgid "" +"Navigate to Turnstile on your Cloudflare account to view the solve rates and" +" access more settings." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:82 +msgid "reCAPTCHA v3 configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:85 +msgid "On Google" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:87 +msgid "" +"Open `the reCAPTCHA website registration page " +"`_. Log in or create a Google" +" account if necessary." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:90 +msgid "On the website registration page:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:92 +msgid "Give the website a :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:93 +msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:94 +msgid "" +"Enter one or more :guilabel:`Domains` (e.g., *example.com* or " +"*subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:95 +msgid "" +"Under :guilabel:`Google Cloud Platform`, a project is automatically selected" +" if one was already created with the logged-in Google account. If not, one " +"is automatically created. Click :guilabel:`Google Cloud Platform` to select " +"a project yourself or rename the automatically created project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:99 +msgid "Agree to the terms of service." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:100 +msgid "Click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "reCAPTCHA website registration example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:105 +msgid "" +"A new page with the generated keys is then displayed. Leave it open for " +"convenience, as copying the keys to Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:111 +msgid "" +"From the database dashboard, click :guilabel:`Settings`. Under " +":guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:115 +msgid "" +"Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the " +":guilabel:`Google reCAPTCHA integration` module, as many other modules would" +" also be removed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:118 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it " +"into the :guilabel:`Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:120 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste " +"it into the :guilabel:`Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:122 +msgid "" +"Change the default :guilabel:`Minimum score` (`0.50`) if necessary, using a " +"value between `1.00` and `0.00`. The higher the threshold is, the more " +"difficult it is to pass the reCAPTCHA, and vice versa." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:127 +msgid "" +"You can notify visitors that reCAPTCHA protects a form. To do so, open the " +"website editor and navigate to the form. Then, click somewhere on the form, " +"and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show" +" reCAPTCHA Policy` found under the :guilabel:`Form` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "reCAPTCHA policy message displayed on a form" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:136 +msgid "" +"If the reCAPTCHA check fails, the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Google reCAPTCHA verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:142 +msgid "" +"Analytics and additional settings are available on `Google's reCAPTCHA " +"administration page `_. For " +"example, you can receive email alerts if Google detects suspicious traffic " +"on your website or view the percentage of suspicious requests, which could " +"help you determine the right minimum score." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:3 +msgid "Translations" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:5 +msgid "" +"The contents of your website pages (i.e., text strings) can be translated " +"into different languages directly on your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:8 +msgid "" +"Your website is displayed in the language that matches the visitor's " +"browser's language, unless that particular language has not been installed. " +"In this case, the website is displayed in the :ref:`default language " +"`. The visitor can still select another language" +" in the language menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:14 +msgid "Installing languages" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:16 +msgid "" +"To translate your website, you first have to add the required languages:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:18 +msgid "Go to your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:19 +msgid "Scroll to the bottom of the page to the **language menu**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:20 +msgid "Click the language and select :guilabel:`Add a language`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Add a language to your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:25 +msgid "" +"Click the :guilabel:`Languages` field and select the required language from " +"the drop-down list. Repeat this step for each additional language." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:27 +msgid "Click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:30 +msgid "" +"You can also edit your website's languages from the backend, in the " +":guilabel:`Settings`. Go to :menuselection:`Website –> Configuration –> " +"Settings` and add/remove the required languages in the :guilabel:`Languages`" +" field, in the :guilabel:`Website info` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:37 +msgid "Default language" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:39 +msgid "" +"If the language of the visitor's browser is not installed on your website, " +"the content is displayed in the default language." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:42 +msgid "" +"To define a default language, go to :menuselection:`Website –> Configuration" +" –> Settings`, and select a language in the :guilabel:`Default` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:46 +msgid "" +"This field is visible only if multiple languages are already configured for " +"your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:49 +msgid "Translating the contents" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:51 +msgid "" +"Once the languages have been added, you can translate the contents of your " +"website. To do so, go to your website, select the language from the language" +" menu and click the :guilabel:`Translate` button on the right part of the " +"task bar to activate the **translation mode**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst-1 +msgid "Translate button" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:58 +msgid "As a result:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:60 +msgid "" +"Text strings that have already been translated are highlighted in green;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:61 +msgid "Text strings that need to be translated are highlighted in yellow." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst-1 +msgid "Text to be translated highlighted in yellow" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:66 +msgid "" +"You can then replace the original text with the translation by clicking the " +"block, editing its contents and saving." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:70 +msgid "" +"Once the languages have been installed, you can also translate some items " +"(e.g., the product's name and description) from the backend (e.g., in the " +"product template). To do so, click the language code (e.g., :guilabel:`EN`) " +"next to the text you want to translate (e.g., the product name) and add the " +"translation." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Translate product-related items." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:78 +msgid "" +"You can also :doc:`export/import translations " +"<../../../../developer/howtos/translations>` to translate multiple items " +"(e.g., product names and descriptions) in one go." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:82 +msgid "Language selector menu" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:84 +msgid "To add a language selector menu:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:86 +msgid "Go to your website and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:87 +msgid "" +"Select the block where you want to add the language selector menu (e.g., the" +" header)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:88 +msgid "Select the :guilabel:`Customize` tab." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:89 +msgid "" +"In the :guilabel:`Navbar` section, set the :guilabel:`Language selector` " +"field to either :guilabel:`Dropdown` or :guilabel:`Inline`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Add a language selector menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:3 +msgid "Unsplash" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:5 +msgid "" +"**Unsplash** is a recognized stock photography library integrated with Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:7 +msgid "" +"If your database is hosted on **Odoo Online**, you can access Unsplash " +"pictures without configuration." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:10 +msgid "" +"If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:12 +msgid "" +"To **generate an Unsplash access key**, create or sign in to an `Unsplash " +"account `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:15 +msgid "" +"Access your `applications dashboard " +"`_, click :guilabel:`New " +"Application`, select all checkboxes, and click :guilabel:`Accept terms`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:18 +msgid "" +"In the pop-up window, enter your :guilabel:`Application Name`, starting with" +" the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as" +" an Odoo instance. Then, add a :guilabel:`Description` and click " +":guilabel:`Create application`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:22 +msgid "" +"On the application details page, scroll down to the :guilabel:`Keys` section" +" and copy the :guilabel:`Access Key` and :guilabel:`Application ID`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:25 +msgid "" +"In Odoo, go to :menuselection:`General Settings` and enable the " +":guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash " +":guilabel:`Access Key` and :guilabel:`Application ID`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:29 +msgid "" +"As a non-Odoo Online user, you are limited to a test key with a maximum of " +"50 Unsplash requests per hour." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:3 +msgid "Mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:5 +msgid "" +"The **mail groups** feature allows website visitors to have a public " +"discussion by email. They can join a group to receive emails from other " +"group members (i.e., website users who have subscribed to the group) and " +"send new ones to all group members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:9 +msgid "" +"To activate the feature, :ref:`install ` the " +":guilabel:`Website Mail Group` (`website_mail_group`) module." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:13 +msgid "" +"The **mail groups** feature is not to be confused with the " +":doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing " +"app." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:19 +msgid "Configuring mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:21 +msgid "To configure mail groups, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:23 +msgid "" +"Configure a custom email alias domain by accessing the **General settings**," +" scrolling down to the :guilabel:`Discuss` section, enabling the " +":guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias " +"domain` (e.g., `@mycompany.com`)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:26 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Mailing Lists`, then " +"click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:27 +msgid "" +"Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:28 +msgid "" +"Enable :guilabel:`Moderate this group` and specify the " +":guilabel:`Moderators` if you wish to :ref:`moderate messages " +"` from this group. Alternatively, if the " +"group is not moderated, you can define :guilabel:`Responsible Users` who can" +" manage the messages in the group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:32 +msgid "" +"In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:34 +msgid "" +":guilabel:`Everyone`: to make the mail group public so anyone can subscribe " +"to it;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:35 +msgid "" +":guilabel:`Members only`: to only allow users defined as members to " +"subscribe to the mail group;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:36 +msgid "" +":guilabel:`Selected group of users`: to only allow users from the " +":guilabel:`Authorized group` to subscribe to the mail group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:39 +msgid "" +"If the mail group is moderated, you can automatically notify authors when " +"their message is pending moderation by enabling :guilabel:`Automatic " +"notification` in the :guilabel:`Notify Members` tab and writing the " +":guilabel:`Notification message`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:42 +msgid "" +"If you wish to send out guidelines to new subscribers, enable " +":guilabel:`Send guidelines to new subscribers` and write them in the " +":guilabel:`Guidelines` tab. This is particularly useful when the mail group " +"is moderated." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:47 +msgid "Using mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:50 +msgid "Subscribing/unsubscribing" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:52 +msgid "" +"Based on the :ref:`configuration of the mail group " +"`, users can subscribe to and " +"unsubscribe from mail groups from the website page (`/groups` by default)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst-1 +msgid "Mail group web page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:58 +msgid "" +"Internal users can also do this from :menuselection:`Website --> " +"Configuration --> Mailing Lists`, using the :guilabel:`Join` and " +":guilabel:`Leave` buttons." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:62 +msgid "Sending messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:64 +msgid "" +"To send messages to a mail group, website users can email the :ref:`mail " +"group's email address `. Internal " +"users can also create messages directly from Odoo. To do so, go to " +":menuselection:`Website --> Configuration --> Mailing Lists`, select the " +"mail group, click the :guilabel:`Emails` smart button, and click " +":guilabel:`New`. Then, fill in the fields and click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:71 +msgid "" +"The list of messages can also be accessed by selecting the group from the " +"`/groups` website page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:73 +msgid "" +"Group members can also unsubscribe from the group, access the mail group " +"page, and send emails to the group using the URLs in the footer of any group" +" email they have received." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "URLs in the footer of a group email." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:82 +msgid "Moderating mail group messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:84 +msgid "" +"If the :guilabel:`Moderate this group` feature has been enabled for the " +":ref:`mail group `, one of the " +":guilabel:`Moderators` must approve the group's messages before they are " +"dispatched to the other members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:88 +msgid "" +"To moderate messages, go to :menuselection:`Website --> Configuration --> " +"Mailing Lists`, select the mail group, and click the :guilabel:`To review` " +"smart button. You can moderate messages using the buttons at the end of the " +"message line or select a message to view its content and moderate it " +"accordingly." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "Moderation buttons in the message line." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:96 +msgid "The following actions are available:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:98 +msgid "" +":guilabel:`Accept`: to accept the email and send it to the mail group " +"members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:99 +msgid "" +":guilabel:`Reject`: to reject the email. In the pop-up window that opens, " +"click :guilabel:`Reject Silently` to reject the email without notifying the " +"author, or specify an explanation for rejecting the message, then click " +":guilabel:`Send & Reject` to reject the message and send the explanation to " +"the author." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:103 +msgid "" +":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept " +"all of their emails. As a result, a :ref:`moderation rule " +"` is created for the author's email address " +"with the status :guilabel:`Always allow`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:106 +msgid "" +":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all " +"their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban " +"the author without notifying them, or specify an explanation, then click " +":guilabel:`Send & Ban` to ban the author and send them the explanation. As a" +" result, a :ref:`moderation rule ` is " +"created for the author's email address with the status :guilabel:`Permanent " +"ban`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:113 +msgid "" +"Messages can also be moderated from the group's list of messages. Go to " +":menuselection:`Website --> Groups --> Mailing List Groups`, select the mail" +" group and click the :guilabel:`Emails` smart button." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:120 +msgid "Whitelisting/Blacklisting authors" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:122 +msgid "" +"You can whitelist or blacklist an author either directly :ref:`from a mail " +"group message `, or by creating a moderation" +" rule. To do so, go to :menuselection:`Website --> Configuration --> " +"Moderation Rules` and click :guilabel:`New`. Then, select the " +":guilabel:`Group`, specify the author's :guilabel:`Email` and set the " +":guilabel:`Status` field." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:129 +msgid "" +"You can also access the mail group's moderation rules by going to " +":menuselection:`Website --> Configuration --> Mailing Lists`, selecting the " +"group, then clicking the :guilabel:`Moderations` smart button." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:5 +msgid "Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:7 +msgid "" +"Odoo allows you to create pages for your website and customize their content" +" and appearance to your needs." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:11 +msgid "" +"*Static* pages are pages that have stable content, such as the homepage. You" +" can manually create new ones, define their URL, adapt their " +":ref:`properties `, etc. *Dynamic* pages, on the " +"other hand, are generated dynamically. All pages generated automatically by " +"Odoo, for example when you install an app or module (e.g., `/shop` or " +"`/blog`) or publish a new product or blog post, are dynamic pages and are " +"therefore managed differently." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:18 +msgid "Page creation" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:20 +msgid "" +"Website pages can be created from the **frontend** and the **backend**. To " +"create a new website page, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:23 +msgid "" +"Either open the **Website** app, click :guilabel:`+ New` in the top-right " +"corner, then select :guilabel:`Page`;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:25 +msgid "" +"Or go to :menuselection:`Website --> Site --> Pages` and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:26 +msgid "" +"Enter a :guilabel:`Page Title`; this title is used in the menu, as well as " +"in the page's URL." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:28 +msgid "" +"Customize the page's content and appearance using the website builder, then " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:30 +msgid ":ref:`Publish ` the page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:33 +msgid "" +"Disable :guilabel:`Add to menu` if the page should not appear in the menu." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:36 +msgid "Page management" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:41 +msgid "Publishing/unpublishing pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:43 +msgid "" +"Pages need to be published to make them accessible to website visitors. To " +"publish or unpublish a page, access it, then toggle the switch in the upper-" +"right corner from :guilabel:`Unpublished` to :guilabel:`Published`, or vice " +"versa." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst-1 +msgid "Unpublished/Published toggle" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:51 +msgid "It is also possible to:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:53 +msgid "" +"publish/unpublish a page from the :ref:`page properties " +"`, where you can define a publishing date and/or " +"restrict the page's visibility if needed;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:55 +msgid "" +"publish/unpublish several pages at once: go to :menuselection:`Website --> " +"Site --> Pages`, select the pages, then, click :guilabel:`Action` and select" +" :guilabel:`Publish` or :guilabel:`Unpublish`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:60 +msgid "Homepage" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:62 +msgid "" +"By default, when you create a website, Odoo creates a dedicated " +":guilabel:`Home` page, but you can define any website page as your homepage." +" To do so, go to :menuselection:`Website --> Configuration --> Settings`, " +"then, in the :guilabel:`Website info` section, define the URL of the desired" +" page in the field :guilabel:`Homepage URL` (e.g., `/shop`)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:67 +msgid "" +"Alternatively, you can define any static page as your homepage by going to " +":menuselection:`Website --> Site --> Properties`. Select the " +":guilabel:`Publish` tab and enable :guilabel:`Use as Homepage`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:73 +msgid "Page properties" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:75 +msgid "" +"To modify a static page's properties, access the page you wish to modify, " +"then go to :menuselection:`Site --> Properties`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:78 +msgid "The :guilabel:`Name` tab allows you to:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:80 +msgid "rename the page using the :guilabel:`Page Name` field;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:81 +msgid "" +"modify the :guilabel:`Page URL`. In this case, you can redirect the old URL " +"to the new one if needed. To do so, enable :guilabel:`Redirect Old URL`, " +"then select the :guilabel:`Type` of :ref:`redirection `:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:85 +msgid ":guilabel:`301 Moved permanently`: to redirect the page permanently;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:86 +msgid ":guilabel:`302 Moved temporarily`: to redirect the page temporarily." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:0 +msgid "Redirect old URL" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:91 +msgid "" +"You can further adapt the page's properties in the :guilabel:`Publish` tab:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:93 +msgid "" +":guilabel:`Show in Top Menu`: Disable if you don't want the page to appear " +"in the menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:94 +msgid "" +":guilabel:`Use as Homepage`: Enable if you want the page to be the homepage " +"of your website;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:95 +msgid "" +":guilabel:`Indexed`: Disable if you don't want the page to be shown in " +"search engine results;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:96 +msgid ":guilabel:`Published`: Enable to publish the page;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:97 +msgid "" +":guilabel:`Publishing Date`: To publish the page at a specific moment, " +"select the date, click the clock icon to set the time, then click the green " +"check mark to validate your selection." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:99 +msgid ":guilabel:`Visibility`: Select who can access the page:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:101 +msgid ":guilabel:`All`" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:102 +msgid ":guilabel:`Signed In`" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:103 +msgid "" +":guilabel:`Restricted Group`: Select the :doc:`user access group(s) " +"` in the :guilabel:`Authorized " +"group` field." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:105 +msgid "" +":guilabel:`With Password`: Enter the password in the :guilabel:`Password` " +"field." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:108 +msgid "" +"*Some* of these properties can also be modified from :menuselection:`Website" +" --> Site --> Pages`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:111 +msgid "Duplicating pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:113 +msgid "" +"To duplicate a page, access the page, then go to :menuselection:`Site --> " +"Properties` and click :guilabel:`Duplicate Page`. Enter a :guilabel:`Page " +"Name`, then click :guilabel:`OK`. By default, the new page is added after " +"the duplicated page in the menu, but you can remove it from the menu or " +"change its position using the :doc:`menu editor `." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:121 +msgid "Deleting pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:123 +msgid "To delete a page, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:125 +msgid "" +"Access the page, then go to :menuselection:`Site --> Properties` and click " +":guilabel:`Delete Page`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:127 +msgid "" +"A pop-up window appears on the screen with all links referring to the page " +"you want to delete, organized by category. To ensure website visitors don't " +"land on a 404 error page, you must update all the links on your website " +"referring to the page. To do so, expand a category, then click on a link to " +"open it in a new window. Alternatively, you can set up a :ref:`redirection " +"` for the deleted page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:132 +msgid "" +"Once you have updated the links (or set up a :ref:`redirection `), select the :guilabel:`I am sure about this` check box, then " +"click :guilabel:`OK`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:138 +msgid "URL redirects" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:140 +msgid "" +"Redirecting URLs consists in sending visitors and search engines to a URL " +"that is different from the one they originally requested. This technique is " +"used, for example, to prevent broken links when you :ref:`delete a page " +"`, :ref:`modify its URL `, or " +"move your site to a new :doc:`domain " +"`. It can also be used to improve " +":doc:`pages/seo`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:146 +msgid "" +"To access existing URL redirections and create new ones, :doc:`activate the " +"developer mode ` and go to " +":menuselection:`Website --> Configuration --> Redirects`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:151 +msgid "" +"A record is added automatically every time you :ref:`modify a page's URL " +"` and enable :guilabel:`Redirect Old URL`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:153 +msgid "You can set up redirections for static and dynamic pages." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:155 +msgid "" +"To create a new redirection, click the :guilabel:`New` button, then fill in " +"the fields:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:157 +msgid ":guilabel:`Name`: Enter a name to identify the redirect." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:158 +msgid ":guilabel:`Action`: Select the type of redirection:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:160 +msgid "" +":guilabel:`404 Not found`: visitors are redirected to a 404 error page when " +"they try to access the page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:162 +msgid "" +":guilabel:`301 Moved Permanently`: for permanent redirections of static " +"pages; the new URL is shown in search engine results and the redirect is " +"cached by browsers." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:164 +msgid "" +":guilabel:`302 Moved Temporarily`: for short-term redirections, for example," +" if you are redesigning or updating the page. The new URL is neither cached " +"by browsers, nor shown in search engine results." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:167 +msgid "" +":guilabel:`308 Redirect / Rewrite`: for permanent redirections of dynamic " +"pages; the new URL is shown in search engine results and the redirect is " +"cached by browsers. Use this redirect type to rename a dynamic page, for " +"example, if you wish to rename `/shop` into `/market`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:171 +msgid "" +":guilabel:`URL from`: Enter the URL to be redirected (e.g., `/about-the-" +"company`) or search for the desired dynamic page and select it from the " +"list." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:173 +msgid "" +":guilabel:`URL to`: For 301, 302 and 308 redirects, enter the URL to be " +"redirected to. If you want to redirect to an external URL, make sure to " +"include the protocol (e.g., `https://`)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:175 +msgid ":guilabel:`Website`: Select a specific website." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:176 +msgid "" +":guilabel:`Sequence`: to define the order in which redirections are " +"performed, e.g., in the case of redirect chains (i.e., a series of redirects" +" where one URL is redirected to another one, which is itself further " +"redirected to another URL)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:180 +msgid "Toggle the :guilabel:`Activate` switch to deactivate the redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:183 +msgid "" +"404, 301 and 302 redirections only work if the original page has been " +":ref:`unpublished ` or :ref:`deleted " +"`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:187 +msgid "" +"`Google documentation on redirects and search " +"`_" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:188 +msgid ":doc:`pages/seo`" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:3 +msgid "Menus" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:5 +msgid "" +"Menus are used to organize your website’s content and help visitors navigate" +" through your web pages effectively. User-friendly and well-structured " +"website menus also play a crucial role in improving :doc:`search engine " +"rankings `." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:9 +msgid "" +"Odoo allows you to customize the content and appearance of your website's " +"menu to your needs." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:12 +msgid "Menu editor" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:14 +msgid "" +"The menu editor allows you to edit your website's menu and add :ref:`regular" +" menu items ` and :ref:`mega menus `." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:17 +msgid "" +"To edit your website's menu, go to :menuselection:`Website --> Site --> Menu" +" Editor`. From there, you can:" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:20 +msgid "" +"**rename** a menu item or change its URL using the :guilabel:`Edit Menu " +"Item` icon;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:21 +msgid "**delete** a menu item using the :guilabel:`Delete Menu Item` icon;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:22 +msgid "" +"**move** a menu item by dragging and dropping it to the desired place in the" +" menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:23 +msgid "" +"**create a regular drop-down menu** by dragging and dropping the sub-menu " +"items to the right, underneath their parent menu." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst-1 +msgid "Menu editor with sub-menus" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:31 +msgid "" +"You can also access the menu editor by clicking :guilabel:`Edit`, selecting " +"any menu item and clicking the :guilabel:`Edit Menu` icon." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:0 +msgid "Access the Menu editor while in Edit mode." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:40 +msgid "Adding regular menu items" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:42 +msgid "" +"By default, pages are added to the menu as regular menu items when " +":doc:`they are created <../pages>`. You can also add regular menu items from" +" the menu editor by clicking :guilabel:`Add Menu Item`. Enter the " +":guilabel:`Name` and URL of the related page in the pop-up window that " +"appears on the screen and click :guilabel:`OK`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:48 +msgid "" +"In the :guilabel:`URL or Email` field, you can type `/` to search for a page" +" on your website or `#` to search for an existing custom anchor." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:54 +msgid "Adding mega menus" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:56 +msgid "" +"Mega menus are similar to drop-down menus, but instead of a simple list of " +"sub-menus, they display a panel divided into groups of navigation options. " +"This makes them suitable for websites with large amounts of content, as they" +" can help include all of your web pages in the menu while still making all " +"menu items visible at once. Mega menus can also be structured more visually " +"than regular drop-down menus, for example, through layout, typography, and " +"icons." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst-1 +msgid "Mega menu in the navigation bar." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:65 +msgid "" +"To create a mega menu, go to :menuselection:`Website --> Site --> Menu " +"Editor` and click :guilabel:`Add Mega Menu Item`. Enter the :guilabel:`Name`" +" of the mega menu in the pop-up, click :guilabel:`OK`, then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:69 +msgid "" +"To adapt the options and layout of the mega menu, click it in the navigation" +" bar, then click :guilabel:`Edit`. Mega menus are composed of building " +"blocks, which means you can customize each component individually using " +"inline formatting, as well as the options available in the " +":guilabel:`Customize` tab in the website builder. For example, you can:" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:74 +msgid "edit the text directly in the building block;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:75 +msgid "" +"edit a menu item's URL by selecting the menu item, then clicking the " +":guilabel:`Edit link` button in the small preview pop-up. Type `/` to search" +" for a page on your website, or `#` to search for an existing custom anchor." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:0 +msgid "Edit a mega menu option." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:82 +msgid "" +"move a menu item by dragging and dropping the related block to the desired " +"position in the mega menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:84 +msgid "delete a menu item by deleting the related block." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:87 +msgid "" +"You can adapt the general layout of the mega menu by selecting the desired " +":guilabel:`Template` and :guilabel:`Size` in the :guilabel:`Mega menu` " +"section in the :guilabel:`Customize` tab in the website builder." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:92 +msgid "Header and navigation bar appearance" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:94 +msgid "" +"To customize the appearance of your website's menu, click :guilabel:`Edit`, " +"then select the navigation bar or any menu item. You can then adapt the " +"fields in the :guilabel:`Header` and :guilabel:`Navbar` sections in the " +":guilabel:`Customize` tab in the website builder." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:3 +msgid "Search Engine Optimisation (SEO)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:5 +msgid "" +"Search Engine Optimization (SEO) is a set of good practices to optimize your" +" website so that you get a better ranking in search engines like Google. In " +"short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:9 +msgid "" +"Some examples of SEO rules: your web pages should load fast, your page " +"should have one and only one title ``

``, meta tags (alt-tag, title-tag) " +"should be consistent with the content, your website should have a " +"``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:15 +msgid "" +"To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo " +"abstracts all the technical complexities of SEO and handles everything for " +"you, in the best possible way. This will be explained here below." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:20 +msgid "" +"But first, let see how you can easily boost your ranking by finetuning the " +"content and the meta tags of your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:24 +msgid "Meta Tags" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:27 +msgid "Title, Description" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:29 +msgid "" +"Every web page should define the ```` and ``<description>`` meta " +"data. These information elements are used by search engines to promote your " +"website. They are automatically generated based on page title & content, but" +" you can finetune them. Make sure they fit the content of the page, " +"otherwise you will be downgraded by search engines." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:39 +msgid "Keywords" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:41 +msgid "" +"In order to write quality content and boost your traffic, Odoo provides a " +"``<keyword>`` finder. Those keywords are the searches you want to head " +"towards your website. For each keyword, you see how it is used in the " +"content (H1, H2, page title, page description, page content) and what are " +"the related searches in Google. The more keywords are used the better." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:51 +msgid "" +"If your website is in multiple languages, you can use the Promote tool for " +"every language of a single page and set specific title, description and " +"search tags." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:56 +msgid "Content is King" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:58 +msgid "" +"When it comes to SEO, content is usually king. Odoo provides several modules" +" to help you build your website content:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:61 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:63 +msgid "" +"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their " +"content is automatically indexed on the web page. Example: " +"`odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-" +"channel-1>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:67 +msgid "" +"**Odoo Forum**: let your community create contents for you. Example: " +"`odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com" +" landing pages)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:71 +msgid "" +"**Odoo Mailing List Archive**: publish mailing list archives on your " +"website. Example: `odoo.com/groups/community-59 " +"<https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:77 +msgid "" +"The 404 page is a regular page, that you can edit like any other page in " +"Odoo. That way, you can build a great 404 page to redirect to the top " +"content of your website when visitors get lost in invalid URLs." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:82 +msgid "Use Social Networks" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:84 +msgid "" +"Social media is built for mass sharing. If lots of people share your content" +" on social media, then it's likely more people will link to it, and links " +"are a huge factor for SEO ranking." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:88 +msgid "Odoo embeds several tools to share content through social media:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:91 +msgid "Social Network" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:93 +msgid "" +"Odoo allows to link all your social network accounts in your website footer." +" All you have to do is to refer all your accounts in your company settings." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:100 +msgid "Social Share" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:102 +msgid "" +"Drop the building block *Share* on any page you want your visitors to share." +" By clicking the icon, they are prompted to share the page in their social " +"media wall." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:109 +msgid "" +"Most social media use a picture of the picture to decorate the share post. " +"Odoo uses the website logo by default but you can choose any other image of " +"your page in the Promote tool." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:117 +msgid "Facebook Page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:119 +msgid "" +"Drop the building block *Facebook Page* to display a widget of your Facebook" +" business page and encourage visitors to follow it. You can display the " +"timeline, the next events and the messages." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:124 +msgid "Twitter Scroller" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:126 +msgid "" +"Display the Twitter feeds with customer satifaction on your website. This " +"will increase the number of tweets and shares." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:130 +msgid "Test Your Website" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:132 +msgid "" +"You can compare how your website rank, in terms of SEO, against Odoo using " +"WooRank free services: `woorank.com <https://www.woorank.com>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:137 +msgid "URLs Handling" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:139 +msgid "This section sheds some light on how Odoo makes URLs SEO-friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:142 +msgid "URLs Structure" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:144 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:146 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:148 +msgid "With the following components:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:150 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:152 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:154 +msgid "" +"**/fr\\_FR** = page language. This part of the URL is removed if the visitor" +" browses the main language of the website Thus, the main version of this " +"page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:159 +msgid "" +"**/shop/product** = every module defines its own namespace (/shop is for the" +" catalog of the eCommerce module, /shop/product is for a product page)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:163 +msgid "" +"**my-great-product** = by default, this is the slugified title of the " +"product this page refers to. But you can customize it for SEO purposes. A " +"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending " +"on the namespace, this could be different objects (blog post, page title, " +"forum post, forum comment, product category, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:170 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:172 +msgid "" +"Note that any dynamic component of an URL can be reduced to its ID. As an " +"example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:175 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:177 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:179 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:182 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:185 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:187 +msgid "In the above example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:189 +msgid "*Company News* is the title of the blog" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:191 +msgid "*The Odoo Story* is the title of a specific blog post" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:193 +msgid "" +"When an Odoo page has a pager, the page number is set directly in the URL " +"(does not have a GET argument). This allows every page to be indexed by " +"search engines. Example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:197 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:200 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:202 +msgid "" +"When the URL of a page changes (e.g. a more SEO friendly version of your " +"product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:205 +msgid "Odoo will automatically update all its links to the new URL." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:207 +msgid "" +"If external websites still points to the old URL, a 301 redirect will be " +"done to route visitors to the new address of the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:210 +msgid "As an example, this URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:212 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:214 +msgid "Will automatically redirect to:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:216 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:218 +msgid "" +"In short, just change the title of a blog post or the name of a product, and" +" the changes will apply automatically everywhere in your website. The old " +"link still functions when used by external websites, via a 301 redirect, " +"maintaining the SEO link juice." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:224 +msgid "HTTPS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:226 +msgid "" +"Search engines boost ranking of secure HTTPS/SSL websites. So, by default " +"all Odoo Online instances are fully based on HTTPS. If the visitor accesses " +"your website through a non HTTPS url, it gets a 301 redirect to its HTTPS " +"equivalent." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:232 +msgid "Links: Nofollow Strategy" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:234 +msgid "" +"The more a page is linked from external and quality websites, the better it " +"is for your SEO." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:237 +msgid "Here are Odoo strategies to manage links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:239 +msgid "" +"Every link you add to your website is \"dofollow\", which means that this " +"link will contribute to the SEO Juice for the linked page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:243 +msgid "" +"Every link posted by a contributor (forum post, blog comment, etc.) that " +"links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:246 +msgid "" +"But every link posted by a contributor that links to an external website is " +"\"nofollow\". In that way, you do not run the risk of people posting links " +"on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:251 +msgid "" +"Note that, when using the forum, contributors having a lot of Karma can be " +"trusted. In such case, their links will not have any ``rel=\"nofollow\"`` " +"attribute." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:256 +msgid "Multi-Language Support" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:261 +msgid "Multi-Language URLs" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:263 +msgid "" +"If you run a website in multiple languages, the same content will be " +"available in different URLs, depending on the language used:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:266 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (main language, English " +"here)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:268 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:270 +msgid "" +"In this example, fr\\_FR is the language of the page. You can even have " +"several variations of the same language: pt\\_BR (Portuguese from Brazil) , " +"pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:275 +msgid "Language Annotation" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:277 +msgid "" +"To let search engines know that the second URL is the French translation of " +"the first URL, Odoo will add an HTML link element in the header. In the HTML" +" <head> section of the main version, Odoo automatically adds a link element " +"pointing to the translated versions of that webpage;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:282 +msgid "" +"<link rel=\"alternate\" hreflang=\"fr\" " +"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:285 +msgid "With this approach:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:287 +msgid "" +"Search engines will redirect to the right language according to the visitor " +"language." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:290 +msgid "" +"You do not get penalized by search engines if your page is not translated " +"yet. Indeed, it's not a duplicated content, but a different version of the " +"same content." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:295 +msgid "Language Detection" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:297 +msgid "" +"When a visitor lands for the first time on your website (e.g. " +"yourwebsite.com/shop), they may automatically be redirected to a translated " +"version according to their browser language preference (e.g. " +"yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:302 +msgid "" +"Next time, it keeps a cookie of the current language to avoid any " +"redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:305 +msgid "" +"To force a visitor to stick to the default language, you can use the code of" +" the default language in your link, example: yourwebsite.com/en\\_US/shop. " +"This will always land visitors to the English version of the page, without " +"using the browser language preferences." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:312 +msgid "Page Speed" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:315 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:317 +msgid "" +"The time to load a page is an important criteria for search engines. A " +"faster website not only improves your visitor's experience, but gives you a " +"better page ranking. Some studies have shown that, if you divide the time to" +" load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor " +"abandonment rate is also divided by two. (25% to 12.5%). One extra second to" +" load a page could `cost $1.6b to Amazon in sales " +"<http://www.fastcompany.com/1825005/how-one-second-could-cost-" +"amazon-16-billion-sales>`__." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:328 +msgid "" +"Fortunately, Odoo does all the magic for you. Below, you will find the " +"tricks Odoo uses to speed up your page loading time. You can compare how " +"your website ranks using these two tools:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:332 +msgid "" +"`Google Page Speed " +"<https://developers.google.com/speed/pagespeed/insights/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:334 +msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:337 +msgid "Images" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:339 +msgid "" +"When you upload new images, Odoo automatically compresses them to reduce " +"their sizes (lossless compression for .PNG and .GIF and lossy compression " +"for .JPG)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:343 +msgid "" +"From the upload button, you have the option to keep the original image " +"unmodified if you prefer to optimize the quality of the image rather than " +"performance." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:351 +msgid "" +"Odoo compresses images when they are uploaded to your website, not when " +"requested by the visitor. Thus, it's possible that, if you use a third-party" +" theme, it will provide images that are not compressed efficiently. But all " +"images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:357 +msgid "" +"When you click on an image, Odoo shows you the Alt and title attributes of " +"the ``<img>`` tag. You can click on it to set your own title and Alt " +"attributes for the image." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:364 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:369 +msgid "" +"Odoo's pictograms are implemented using a font (`Font Awesome " +"<https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes)." +" Thus, you can use as many pictograms as you want in your page, they will " +"not result in extra requests to load the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:378 +msgid "Static Resources: CSS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:380 +msgid "" +"All CSS files are pre-processed, concatenated, minified, compressed and " +"cached (server-side and browser-side). The result:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:383 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:385 +msgid "" +"this CSS file is shared and cached amongst pages, so that when the visitor " +"clicks on another page, the browser doesn't have to even load a single CSS " +"resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:389 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:391 +msgid "" +"**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a " +"theme might use another framework, most of `Odoo themes " +"<https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap " +"directly. Since Odoo supports Less and Sass, you can modify CSS rules " +"instead of overwriting them through extra CSS lines, resulting in a smaller " +"file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:398 +msgid "" +"**Concatenated:** every module or library you might use in Odoo has its own " +"set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having " +"several CSS files is great for the modularity, but not good for the " +"performance because most browsers can only perform 6 requests in parallel " +"resulting in lots of files loaded in series. The latency time to transfer a " +"file is usually much longer than the actual data transfer time, for small " +"files like .JS and .CSS. Thus, the time to load CSS resources depends more " +"on the number of requests to be done than the actual file size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:408 +msgid "" +"To address this issue, all CSS / Less / Sass files are concatenated into a " +"single .CSS file to send to the browser. So a visitor has **only one .CSS " +"file to load** per page, which is particularly efficient. As the CSS is " +"shared amongst all pages, when the visitor clicks on another page, the " +"browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "**Both files in the <head>**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:424 +#: ../../content/applications/websites/website/pages/seo.rst:450 +msgid ".text-muted {" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:425 +#: ../../content/applications/websites/website/pages/seo.rst:451 +msgid "color: #666;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:419 +msgid "color: #777;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:419 +msgid "background: yellow" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:420 +msgid "background: yellow;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:420 +#: ../../content/applications/websites/website/pages/seo.rst:421 +#: ../../content/applications/websites/website/pages/seo.rst:426 +#: ../../content/applications/websites/website/pages/seo.rst:452 +msgid "}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:423 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:429 +msgid "" +"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. " +"By doing this, additional page views from the same visitor will not have to " +"load CSS files at all. But some modules might include huge CSS/Javascript " +"resources that you do not want to prefetch at the first page because they " +"are too big. In this case, Odoo splits this resource into a second bundle " +"that is loaded only when the page using it is requested. An example of this " +"is the backend that is only loaded when the visitor logs in and accesses the" +" backend (/web)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:439 +msgid "" +"If the CSS file is very big, Odoo will split it into two smaller files to " +"avoid the 4095 selectors limit per sheet of Internet Explorer. But most " +"themes fit below this limit." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:443 +msgid "" +"**Minified:** After being pre-processed and concatenated, the resulting CSS " +"is minified to reduce its size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "**Before minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "**After minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:455 +msgid "" +"The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:458 +msgid "" +"Then, a cached version is stored server-side (so we do not have to pre-" +"process, concatenate, minify at every request) and browser-side (so the same" +" visitor will load the CSS only once for all pages they visit)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:464 +msgid "Static Resources: Javascript" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:466 +msgid "" +"As with CSS resources, Javascript resources are also concatenated, minified," +" compressed and cached (server-side and browser-side)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:469 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:471 +msgid "" +"One for all pages of the website (including code for parallax effects, form " +"validation, etc.)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:474 +msgid "" +"One for common Javascript code shared among frontend and backend (Bootstrap)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:477 +msgid "" +"One for backend specific Javascript code (Odoo Web Client interface for your" +" employees using Odoo)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:480 +msgid "" +"Most visitors of your website will only need the first two bundles, " +"resulting in a maximum of two Javascript files to load to render one page. " +"As these files are shared across all pages, further clicks by the same " +"visitor will not load any other Javascript resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:486 +msgid "" +"If you work on :ref:`developer mode <developer-mode>`, the CSS and " +"Javascript are neither concatenated, nor minified. Thus, it's much slower. " +"But it allows you to easily debug with the Chrome debugger as CSS and " +"Javascript resources are not transformed from their original versions." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:491 +msgid "CDN" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:493 +msgid "" +"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, " +"images) are loaded from a Content Delivery Network. Using a Content Delivery" +" Network has three advantages:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:497 +msgid "" +"Load resources from a nearby server (most CDN have servers in main countries" +" around the globe)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:500 +msgid "" +"Cache resources efficiently (no computation resources usage on your own " +"server)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:503 +msgid "" +"Split the resource loading on different services allowing to load more " +"resources in parallel (since the Chrome limit of 6 parallel requests is by " +"domain)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:507 +msgid "" +"You can configure your CDN options from the **Website Admin** app, using the" +" Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:514 +msgid "HTML Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:516 +msgid "" +"The HTML pages can be compressed, but this is usually handled by your web " +"server (NGINX or Apache)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:519 +msgid "" +"The Odoo Website builder has been optimized to guarantee clean and short " +"HTML code. Building blocks have been developed to produce clean HTML code, " +"usually using Bootstrap and the HTML editor." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:523 +msgid "" +"As an example, if you use the color picker to change the color of a " +"paragraph to the primary color of your website, Odoo will produce the " +"following code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:527 +msgid "``<p class=\"text-primary\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:529 +msgid "" +"Whereas most HTML editors (such as CKEditor) will produce the following " +"code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:532 +msgid "``<p style=\"color: #AB0201\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:535 +msgid "Responsive Design" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:537 +msgid "" +"Websites that are not mobile-friendly are negatively impacted in search " +"engine rankings. All Odoo themes rely on Bootstrap to render efficiently " +"according to the device: desktop, tablet or mobile." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:544 +msgid "" +"As all Odoo modules share the same technology, absolutely all pages in your " +"website are mobile friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:548 +msgid "Browser Caching" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:550 +msgid "" +"Javascript, images and CSS resources have an URL that changes dynamically " +"when their content change. As an example, all CSS files are loaded through " +"this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css " +"<http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. " +"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of " +"your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:557 +msgid "" +"This allows Odoo to set a very long cache delay (XXX) on these resources: " +"XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:562 +msgid "Scalability" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:564 +msgid "" +"In addition to being fast, Odoo is also more scalable than traditional CMS " +"and eCommerce (Drupal, Wordpress, Magento, Prestashop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:567 +msgid "" +"Here is the slide that summarizes the scalability of Odoo Website & " +"eCommerce." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:573 +msgid "Search Engines Files" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:576 +msgid "Sitemap" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:578 +msgid "" +"The sitemap points out pages to index to search engine robots. Odoo " +"generates a ``/sitemap.xml`` file automatically for you. For performance " +"reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:582 +msgid "" +"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you " +"have a lot of pages, Odoo will automatically create a Sitemap Index file, " +"respecting the `sitemaps.org protocol " +"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 " +"chunks per file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:588 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:590 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:592 +msgid "" +"``<lastmod>`` : last modification date of the resource, computed " +"automatically based on related object. For a page related to a product, this" +" could be the last modification date of the product or the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:597 +msgid "" +"``<priority>`` : modules may implement their own priority algorithm based on" +" their content (example: a forum might assign a priority based on the number" +" of votes on a specific post). The priority of a static page is defined by " +"it's priority field, which is normalized (16 is the default)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:604 +msgid "Structured Data Markup" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:606 +msgid "" +"Structured Data Markup is used to generate Rich Snippets in search engine " +"results. It is a way for website owners to send structured data to search " +"engine robots; helping them understand your content and create well-" +"presented search results." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:611 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:614 +msgid "" +"Odoo implements micro data as defined in the `schema.org " +"<http://schema.org>`__ specification for events, eCommerce products, forum " +"posts and contact addresses. This allows your product pages to be displayed " +"in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:624 +msgid "robots.txt" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:626 +msgid "" +"When indexing your website, search engines take a first look at the general " +"indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, " +"etc.). Odoo automatically creates it. Its content is:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:630 +msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:633 +msgid "" +"It means that all robots are allowed to index your website and there is no " +"other indexing rule than specified in the sitemap to be found at following " +"address." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:637 +msgid "" +"You can customize the file *robots* in :ref:`developer mode <developer-" +"mode>` from *Settings --> Technical --> User Interface --> Views* (exclude " +"robots, exclude some pages, redirect to a custom Sitemap). Make the Model " +"Data of the view *Non Updatable* to not reset the file after system " +"upgrades." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:3 +msgid "Website analytics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:5 +msgid "" +"Website analytics helps website owners understand how people use their site." +" It provides data on visitor demographics, behavior, and interactions, " +"helping improve websites and marketing strategies." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:8 +msgid "" +"You can track your Odoo website's traffic using " +":ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We " +"recommend using Plausible.io as it is privacy-friendly, lightweight, and " +"easy to use." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:12 +msgid "" +"The Plausible analytics dashboard is also integrated into Odoo and can be " +"accessed via :menuselection:`Website --> Reporting --> Analytics`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:18 +msgid "Plausible.io" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:20 +msgid "" +"Odoo hosts its own Plausible.io server and provides a free and ready-to-work" +" Plausible.io solution for **Odoo Online** databases. Go to " +":menuselection:`Website --> Configuration --> Settings`, and enable the " +"feature in the :guilabel:`SEO` section. Odoo automatically creates and sets " +"up your account. You can start using it by going to :menuselection:`Website " +"--> Reporting --> Analytics`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:26 +msgid "" +"**If you already have a Plausible.io account** and you want to connect it to" +" your Odoo Online database, you must create two `ir.config.parameters` to " +"use Plausible.io's servers. To do so, enable the :ref:`developer mode " +"<developer-mode>` and go to :menuselection:`General Settings --> Technical " +"-- System Parameters`. Click :guilabel:`New` and fill in the following " +":guilabel:`Key` and :guilabel:`Value` fields:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:35 +msgid "Key" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:36 +msgid "Value" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:37 +msgid "`website.plausible_script`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:38 +msgid "`https://plausible.io/js/plausible.js`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:39 +msgid "`website.plausible_server`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:40 +msgid "`https://plausible.io`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:42 +msgid "" +"Then, follow the steps below to connect your existing account with " +"Plausible.io servers." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:44 +msgid "" +"If your database is hosted on **Odoo.sh** or **On-premise**, or if you wish " +"to use your own Plausible.io account, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:47 +msgid "" +"Create or sign in to a Plausible account using the following link: " +"`<https://plausible.io/register>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:48 +msgid "" +"If you are creating a new account, go through the registration and " +"activation steps. When asked to provide your website details, add its " +":guilabel:`Domain` without including `www` (e.g., `example.odoo.com`) and " +"change the :guilabel:`Reporting Timezone` if necessary. Click :guilabel:`Add" +" snippet` to proceed to the next step. Ignore the :guilabel:`Add JavaScript " +"snippet` instructions and click :guilabel:`Start collecting data`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:53 +msgid "" +"Once done, click the Plausible logo in the upper-left part of the page to " +"access your `list of websites <https://plausible.io/sites>`_, then click the" +" gear icon next to the website." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Click the gear icon in the list of websites." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:59 +msgid "" +"In the sidebar, select :guilabel:`Visibility`, then click :guilabel:`+ New " +"link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:60 +msgid "" +"Enter a :guilabel:`Name`, leave the :guilabel:`Password` field empty, as the" +" Plausible analytics dashboard integration in Odoo doesn't support it, then " +"click :guilabel:`Create shared link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Credentials creation for the new shared link" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:66 +msgid "Copy the shared link." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Copy the shared link URL from Plausible.io" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:71 +#: ../../content/applications/websites/website/reporting/analytics.rst:118 +msgid "" +"In Odoo, go to :menuselection:`Website --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:72 +msgid "" +"In the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics`, then" +" paste the :guilabel:`Shared Link` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:76 +msgid "" +"If you have :doc:`multiple websites <../configuration/multi_website>`, add " +"your websites to your Plausible.io account by going to " +"`<https://plausible.io/sites>`_ and clicking :guilabel:`+ Add website`. In " +"Odoo, in the **Website settings**, make sure to select the website in the " +":guilabel:`Settings of Website` field before pasting the :guilabel:`Shared " +"link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:82 +msgid "" +"Odoo automatically pushes two custom goals: `Lead Generation` and `Shop`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:85 +msgid "`Plausible Analytics documentation <https://plausible.io/docs>`_" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:90 +msgid "Google Analytics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:92 +msgid "To follow your Odoo website's traffic with Google Analytics:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:94 +msgid "" +"Create or sign in to a Google account using the following link: " +"`<https://analytics.google.com>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:95 +msgid "" +"If you are setting up Google Analytics for the first time, click " +":guilabel:`Start measuring` and go through the account creation step." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:97 +msgid "" +"If you already have a Google Analytics account, sign in and click the gear " +"icon in the bottom-left corner of the page to access the **Admin** page. " +"Then, click :guilabel:`+ Create Property`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Measurement ID in Google Analytics." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:104 +msgid "" +"Complete the next steps: `property creation " +"<https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_," +" business details, and business objectives." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:106 +msgid "" +"When you reach the **Data collection** step, choose the :guilabel:`Web` " +"platform." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Choose a platform for your Google Analytics property." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:111 +msgid "" +"Set up your data stream: Specify your :guilabel:`Website URL` and a " +":guilabel:`Stream name`, then click :guilabel:`Create stream`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:113 +msgid "Copy the :guilabel:`Measurement ID`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:119 +msgid "" +"In the :guilabel:`SEO` section, enable :guilabel:`Google Analytics`, then " +"paste the :guilabel:`Measurement ID` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:123 +msgid "" +"If you have :doc:`multiple websites <../configuration/multi_website>` with " +"separate domains, it is recommended to create `one property " +"<https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_" +" per domain. In Odoo, in the **Website settings**, make sure to select the " +"website in the :guilabel:`Settings of Website` field before pasting the " +":guilabel:`Measurement ID`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:129 +msgid "" +"`Google documentation on setting up Analytics for a website " +"<https://support.google.com/analytics/answer/1008015?hl=en/>`_" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:3 +msgid "Link trackers" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:5 +msgid "" +"Link Trackers allow you to track your marketing campaigns (emails, banner " +"ads, blog posts, social media posts, affiliate links, etc.). This way, you " +"are able to identify your best traffic sources and make informed decisions " +"about the distribution of your marketing budget." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:12 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings` and activate " +"*Link Trackers*." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of Website settings page emphasizing the link trackers field in Odoo " +"Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:19 +msgid "Set up traceable URLs" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:21 +msgid "" +"Go to :menuselection:`Website --> Go to website --> Promote --> Track this " +"page`. Here, you are able to get a specific tracked URL based on the " +"campaign, medium, and source being used." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "View of the link tracker fields for Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:28 +msgid "" +"**URL**: url of the page you want to track (e.g. the home page or a " +"product's page)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:29 +msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:30 +msgid "" +"**Medium**: channel used to share (deliver) your link (e.g. an email or a " +"Facebook ad)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:31 +msgid "" +"**Source**: platform where the traffic originates (e.g. Google or Twitter)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:33 +msgid "" +"Now, click on *Get tracked link* to generate a URL that you can post or send" +" by the source you have decided on." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:37 +msgid "Follow-up on tracked links" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:39 +msgid "" +"To look at statistics of your links, go to :menuselection:`Website --> Go to" +" website --> Promote --> Track this page`. Besides being able to see the " +"*Most Clicked* and *Recently Used* links, you can also see complete " +"statistics by clicking on *Stats*, including the number of clicks, and the " +"country of origin for those clicks." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of the tracked list emphasizing the statistics buttons in Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:50 +msgid "You can also access the link tracker on *odoo.com/r* via your browser." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:51 +msgid "" +"Activate the developer mode (:menuselection:`Settings --> Activate the " +"developer mode`) and get access to the *Link Tracker* module and its back-" +"end functionalities." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:53 +msgid "" +"Integrated with :ref:`website/analytics/GA`, those trackers allow you to see" +" the number of clicks and visitors to keep you on top of your marketing " +"campaigns." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:55 +msgid "" +"The integration with the :doc:`CRM " +"</applications/sales/crm/track_leads/prospect_visits>` application allows " +"you to understand where your leads and opportunities are coming from." +msgstr "" diff --git a/locale/id/LC_MESSAGES/administration.po b/locale/id/LC_MESSAGES/administration.po index ef1f5981c..1a305ea0b 100644 --- a/locale/id/LC_MESSAGES/administration.po +++ b/locale/id/LC_MESSAGES/administration.po @@ -6,8 +6,8 @@ # Translators: # Martin Trigaux, 2023 # Wil Odoo, 2023 -# Abe Manyo, 2024 # Muftiara Syuhada <muftiara.syuhada@gmail.com>, 2024 +# Abe Manyo, 2024 # #, fuzzy msgid "" @@ -16,7 +16,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:55+0000\n" -"Last-Translator: Muftiara Syuhada <muftiara.syuhada@gmail.com>, 2024\n" +"Last-Translator: Abe Manyo, 2024\n" "Language-Team: Indonesian (https://app.transifex.com/odoo/teams/41243/id/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -388,16 +388,22 @@ msgid "" "not generally necessary for a development systems that is not exposed on the" " internet." msgstr "" +"Dokumen ini mendeskripsikan langkah-langkah dasar untuk setup Odoo di " +"production atau server yang menggunakan internet. Ini mengikuti :doc:`instal" +" <../install>`, dan secara umum tidak diperlukan untuk sistem development " +"yang tidak terhubung ke internet." #: ../../content/administration/install/deploy.rst:10 msgid "" "If you are setting up a public server, be sure to check our :ref:`security` " "recommendations!" msgstr "" +"Bila Anda ingin setup server publik, pastikan Anda memeriksa rekomendasi " +":ref:`Keamanan` kami!" #: ../../content/administration/install/deploy.rst:15 msgid "dbfilter" -msgstr "" +msgstr "dbfilter" #: ../../content/administration/install/deploy.rst:17 msgid "" @@ -406,6 +412,10 @@ msgid "" "customizations (starting from the modules being loaded) depending on the " "\"current database\"." msgstr "" +"Odoo adalah sistem multi-tenant: satu sistem Odoo dapat berjalan dan " +"melayani sejumlah instance database. Odoo juga sangat mudah dikustomisasi, " +"dengan kustomisasi (dimulai dari modul yang dimuat) tergantung pada " +"\"database saat ini\"." #: ../../content/administration/install/deploy.rst:21 msgid "" @@ -413,6 +423,9 @@ msgid "" "in company user: the database can be selected when logging in, and " "customizations loaded afterwards." msgstr "" +"Ini tidak merupakan masalah saat bekerja dengan backend (web client) sebagai" +" user perusahaan yang terlogin: database dapat dipilih saat login, dan " +"kustomisasi dimuat setelahnya." #: ../../content/administration/install/deploy.rst:25 msgid "" @@ -423,6 +436,13 @@ msgid "" "multiple databases accessible Odoo needs a rule to know which one it should " "use." msgstr "" +"Namun ini menjadi masalah untuk user yang tidak-login (portal, website) yang" +" tidak terikat ke database: Odoo harus tahu database mana yang akan " +"digunakan untuk membuat halaman website atau melakukan operasi. Bila multi-" +"pengguna tidak digunakan ini tidak merupakan masalah, hanya ada satu " +"database untuk digunakan, tapi bila terdapat lebih dari satu database yang " +"dapat diakses Odoo membutuhkan peraturan untuk mengetahui mana yang harus " +"digunakan." #: ../../content/administration/install/deploy.rst:31 msgid "" @@ -432,6 +452,11 @@ msgid "" "possibly including the dynamically injected hostname (``%h``) or the first " "subdomain (``%d``) through which the system is being accessed." msgstr "" +"Inilah salah satu kegunaan dari :option:`--db-filter <odoo-bin --db-" +"filter>`: dbfilter menentukan bagiamana database harus dipilih berdasarkan " +"nama host (domain) yang diminta. Value adalah `regular expression`_, " +"biasanya termasuk nama host yang di-inject secara dinamis (``%h``) atau " +"subdomain pertama (``%d``) melalui mana sistem akan diakses." #: ../../content/administration/install/deploy.rst:37 msgid "" @@ -439,22 +464,24 @@ msgid "" "``website`` is used, dbfilter **must** be set, otherwise a number of " "features will not work correctly." msgstr "" +"Untuk server yang hosting lebih dari satu database di production, terutama " +"bila ``website`` digunakan, dbfilter **harus** ditetapkan, bila tidak " +"sejumlah fitur tidak akan bekerja dengan tepat." #: ../../content/administration/install/deploy.rst:42 msgid "Configuration samples" -msgstr "" +msgstr "Sampel konfigurasi" #: ../../content/administration/install/deploy.rst:44 msgid "Show only databases with names beginning with 'mycompany'" -msgstr "" -"Hanya tunjukkan basis data dengan nama yang diawali dengan 'mycompany'" +msgstr "Hanya tunjukkan database dengan nama yang diawali dengan 'mycompany'" #: ../../content/administration/install/deploy.rst:46 #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 #: ../../content/administration/install/deploy.rst:280 msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:" -msgstr "" +msgstr "di :ref:`file konfigurasi <reference/cmdline/config_file>` tetapkan:" #: ../../content/administration/install/deploy.rst:53 msgid "" @@ -463,6 +490,10 @@ msgid "" " ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " "``www2.mycompany.com`` or ``helpdesk.mycompany.com``." msgstr "" +"Tunjukkan hanya database yang subdomain pertama-nya cocok setelah ``www``: " +"contohnya database \"mycompany\" akan ditunjukkan bila permintaan yang masuk" +" dikirim ke ``www.mycompany.com`` atau ``mycompany.co.uk``, tapi tidak untuk" +" ``www2.mycompany.com`` atau ``helpdesk.mycompany.com``." #: ../../content/administration/install/deploy.rst:67 msgid "" @@ -473,11 +504,18 @@ msgid "" "database-list`` startup parameter to prevent listing your databases, and to " "block access to the database management screens. See also security_." msgstr "" +"Menetapkan :option:`--db-filter <odoo-bin --db-filter>` yang benar adalah " +"bagian penting dalam mengamankan deployment Anda. Setelah bekerja dengan " +"tepat dan hanya mencocokkan satu database untuk setiap nama host, sangat " +"direkomendasikan untuk memblokir akses ke layar manajer database, dan untuk " +"menggunakan parameter startup ``--no-database-list`` untuk mencegah " +"menampilkan daftar database Anda, dan untuk memblokir akses ke layar " +"manajemen database. Lihat juga keamanan_." #: ../../content/administration/install/deploy.rst:76 #: ../../content/administration/install/source.rst:193 msgid "PostgreSQL" -msgstr "" +msgstr "PostgreSQL" #: ../../content/administration/install/deploy.rst:78 msgid "" @@ -485,6 +523,9 @@ msgid "" " connections (from \"localhost\", the same machine the PostgreSQL server is " "installed on)." msgstr "" +"Secara default, PostgreSQL hanya mengizinkan hubungan melalui koneksi UNIX " +"socket dan loopback (dari \"localhost\", mesin yang sama dengan tempat " +"server PostgreSQL diinstal)." #: ../../content/administration/install/deploy.rst:82 msgid "" @@ -493,6 +534,12 @@ msgid "" "and PostgreSQL to execute on different machines [#different-machines]_ it " "will need to `listen to network interfaces`_ [#remote-socket]_, either:" msgstr "" +"UNIX socket dapat digunakan bila Anda ingin Odoo dan dan PostgreSQL untuk " +"berjalan di mesin yang sama, dan merupakan default saat tidak ada host yang " +"disediakan, tapi bila Anda ingin Odoo dan PostgreSQL untuk berjalan pada " +"mesin yang berbeda [#different-machines]_ maka akan harus `mendengarkan " +"antarmuka jaringan <https://www.postgresql.org/docs/12/runtime-config-" +"connection.html>`_ [#remote-socket]_, baik dengan: " #: ../../content/administration/install/deploy.rst:87 msgid "" @@ -500,6 +547,9 @@ msgid "" "machine on which Odoo runs and the one on which PostgreSQL runs, then " "configure Odoo to connect to its end of the tunnel" msgstr "" +"Hanya menerima hubungan loopback dan gunakan `SSH tunnel`_ di antara mesin " +"yang terdapat Odoo dan mesin yang terdapat PostgreSQL, kemudian atur Odoo " +"untuk terhubung dengan tunnel" #: ../../content/administration/install/deploy.rst:90 msgid "" @@ -507,34 +557,40 @@ msgid "" "ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" " to connect over the network" msgstr "" +"Terima hubungan ke mesin tempat Odoo diinstal, biasanya melalui ssl (lihat " +"`PostgreSQL connection settings`_ untuk detail), kemudian atur Odoo untuk " +"terhubung melalui jaringan" #: ../../content/administration/install/deploy.rst:95 #: ../../content/administration/install/deploy.rst:145 #: ../../content/administration/install/deploy.rst:235 #: ../../content/administration/install/deploy.rst:275 msgid "Configuration sample" -msgstr "" +msgstr "Sampel konfigurasi" #: ../../content/administration/install/deploy.rst:97 msgid "Allow tcp connection on localhost" -msgstr "" +msgstr "Izinkan tcp connection pada localhost" #: ../../content/administration/install/deploy.rst:98 msgid "Allow tcp connection from 192.168.1.x network" -msgstr "" +msgstr "Izinkan tcp connection dari 192.168.1.x network" #: ../../content/administration/install/deploy.rst:100 msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:" msgstr "" +"di ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` tetapkan:" #: ../../content/administration/install/deploy.rst:108 msgid "" "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:" msgstr "" +"di ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` " +"tetapkan:" #: ../../content/administration/install/deploy.rst:119 msgid "Configuring Odoo" -msgstr "" +msgstr "Mengonfigurasi Odoo" #: ../../content/administration/install/deploy.rst:121 msgid "" @@ -543,12 +599,18 @@ msgid "" "<reference/cmdline/server/database>` when your Postgres deployment is not " "local and/or does not use the installation defaults." msgstr "" +"Langsung siap pakai, Odoo akan terhubung ke postgres lokal melalui UNIX " +"socket via port 5432. Ini dapat dikesampingkan menggunakan :ref:`opsi " +"database <reference/cmdline/server/database>` saat deployment Postgres Anda " +"tidak lokal dan/atau tidak menggunakan penginstalan default." #: ../../content/administration/install/deploy.rst:126 msgid "" "The :doc:`packaged installers <packages>` will automatically create a new " "user (``odoo``) and set it as the database user." msgstr "" +":doc:`Paket installer <packages>` akan secara otomatis membuat user baru " +"(``odoo``) dan menetapkannya sebagai user database." #: ../../content/administration/install/deploy.rst:129 msgid "" @@ -558,6 +620,11 @@ msgid "" " randomly generated value to ensure third parties can not use this " "interface." msgstr "" +"Layar manajemen database dilindungi oleh pengaturan ``admin_passwd``. " +"Pengaturan ini hanya dapat ditetapkan menggunakan file konfigurasi, dan " +"diperiksa sebelum melakukan perubahan database. Ini sebaiknya ditetapkan ke " +"value yang secara acak dibuat untuk memastikan pihak ketiga tidak dapat " +"menggunakan antarmuka ini." #: ../../content/administration/install/deploy.rst:134 msgid "" @@ -566,6 +633,10 @@ msgid "" "screen. For the database management screen to work requires that the " "PostgreSQL user have ``createdb`` right." msgstr "" +"Semua operasi database menggunakan :ref:`opsi database " +"<reference/cmdline/server/database>`, termasuk layar manajemen database. " +"Agar layar manajemen database dapat bekerja, user PostgreSQL harus memilki " +"hak ``createdb``." #: ../../content/administration/install/deploy.rst:138 msgid "" @@ -574,22 +645,26 @@ msgid "" "with ``no-createdb`` and the database must be owned by a different " "PostgreSQL user." msgstr "" +"User dapat selalu men-drop database yang mereka miliki. Agar layar manajemen" +" database sepenuhnya non-fungsional, user PostgreSQL harus dibuat dengan " +"``no-createdb`` dan database harus dimiliki oleh user PostgreSQL yang " +"berbeda." #: ../../content/administration/install/deploy.rst:142 msgid "the PostgreSQL user *must not* be a superuser" -msgstr "" +msgstr "User PostgreSQL *tidak boleh* merupakan superuser" #: ../../content/administration/install/deploy.rst:147 msgid "connect to a PostgreSQL server on 192.168.1.2" -msgstr "" +msgstr "terhubung ke server PostgreSQL pada 192.168.1.2" #: ../../content/administration/install/deploy.rst:148 msgid "port 5432" -msgstr "" +msgstr "port 5432" #: ../../content/administration/install/deploy.rst:149 msgid "using an 'odoo' user account," -msgstr "gunakan akun pengguna 'odoo'" +msgstr "menggunakan akun pengguna 'odoo'" #: ../../content/administration/install/deploy.rst:150 msgid "with 'pwd' as a password" @@ -597,11 +672,11 @@ msgstr "dengan kata kunci 'pwd'" #: ../../content/administration/install/deploy.rst:151 msgid "filtering only db with a name beginning with 'mycompany'" -msgstr "" +msgstr "memfilter hanya db dengan nama yang dimulai dengan 'mycompany'" #: ../../content/administration/install/deploy.rst:168 msgid "SSL Between Odoo and PostgreSQL" -msgstr "" +msgstr "SSL Di Antara Odoo dan PostgreSQL" #: ../../content/administration/install/deploy.rst:170 msgid "" @@ -610,21 +685,28 @@ msgid "" "value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " "'verify-full'" msgstr "" +"Semenjak Odoo 11.0, Anda dapat memaksakan hubungan ssl antara Odoo dan " +"PostgreSQL. Di Odoo db_sslmode mengendalikan ssl security hubungan dengan " +"value yang dipilih antara 'disable', 'allow', 'prefer', 'require', 'verify-" +"ca' atau 'verify-full'" #: ../../content/administration/install/deploy.rst:175 msgid "" "`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_" msgstr "" +"`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_" #: ../../content/administration/install/deploy.rst:180 msgid "Builtin server" -msgstr "" +msgstr "Builtin server" #: ../../content/administration/install/deploy.rst:182 msgid "" "Odoo includes built-in HTTP, cron, and live-chat servers, using either " "multi-threading or multi-processing." msgstr "" +"Odoo mengikutsertakan HTTP, cron, dan server live-chat bawaan, baik yang " +"menggunakan multi-threading atau multi-processing." #: ../../content/administration/install/deploy.rst:185 msgid "" @@ -635,6 +717,12 @@ msgid "" "cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " "make the best use of the hardware." msgstr "" +"Server **multi-thread** adalah server lebih sederhana yang secara utama " +"digunakan untuk development, demonstrasi, dan karena kompatibilitanya dengan" +" beragam sistem operasi (termasuk Windows). Thread baru dibuat untuk setiap " +"permintaan HTTP baru, bahkan untuk hubungan yang bertahan lama seperti " +"websocket. Daemonic cron threads ekstra juga dibuat. Oleh karena limitasi " +"Python (GIL), mereka tidak menggunakan hardware sebaik mungkin." #: ../../content/administration/install/deploy.rst:191 msgid "" @@ -642,6 +730,9 @@ msgid "" " It is selected by leaving the :option:`--workers <odoo-bin --workers>` " "option out or setting it to ``0``." msgstr "" +"Server multi-thread adalah server default, juga untuk docker container. Ini " +"dipilih dengan tidak mengikutsertakan opsi :option:`--workers <odoo-bin " +"--workers>` atau dengan menyetelnya ke ``0``." #: ../../content/administration/install/deploy.rst:194 msgid "" @@ -654,67 +745,90 @@ msgid "" "spawned too. A configurable process reaper monitors resource usage and can " "kill/restart failed workers." msgstr "" +"Server **multi-processing** adalah server lengkap yang secara utama " +"digunakan untuk production. Server ini tidak memiliki kekurangan limitasi " +"Python limitation (GIL) yang sama pada penggunaan sumber daya dan oleh " +"karena itu menggunakan hardware sebaik mungkin. Sekelompok worker dibuat " +"pada startup server. Permintaan HTTP baru diurutkan berdasarkan OS sampai " +"terdapat worker yang siap untuk memproses mereka. Event-driven HTTP worker " +"ekstra dibuat untuk live chat pada port alternatif. Cron worker ekstra juga " +"dibuat. Process reaper yang dapat dikonfigurasi memonitor penggunaan sumber " +"daya dan dapat mematikan/me-restart worker yang gagal." #: ../../content/administration/install/deploy.rst:201 msgid "" "The multi-processing server is opt-in. It is selected by setting the " ":option:`--workers <odoo-bin --workers>` option to a non-null integer." msgstr "" +"Server multi-processing bersifat opsional. Server ini dipilih dengan " +"menyetel opsi :option:`--workers <odoo-bin --workers>` menjadi integer non " +"null." #: ../../content/administration/install/deploy.rst:205 msgid "" "Because it is highly customized for Linux servers, the multi-processing " "server is not available on Windows." msgstr "" +"Karena sangat dapat dikustomisasi untuk server Linux, server multi-" +"processing tidak tersedia di Windows." #: ../../content/administration/install/deploy.rst:209 msgid "Worker number calculation" -msgstr "" +msgstr "Kalkulasi jumlah worker" #: ../../content/administration/install/deploy.rst:211 msgid "Rule of thumb : (#CPU * 2) + 1" -msgstr "" +msgstr "Peraturan praktis : (#CPU * 2) + 1" #: ../../content/administration/install/deploy.rst:212 msgid "Cron workers need CPU" -msgstr "" +msgstr "Cron worker membutuhkan CPU" #: ../../content/administration/install/deploy.rst:213 msgid "1 worker ~= 6 concurrent users" -msgstr "" +msgstr "1 worker ~= 6 user bersamaan" #: ../../content/administration/install/deploy.rst:216 msgid "memory size calculation" -msgstr "" +msgstr "Kalkulasi ukuran memori" #: ../../content/administration/install/deploy.rst:218 msgid "" "We consider 20% of the requests are heavy requests, while 80% are simpler " "ones" msgstr "" +"Kami menghitung 20% permintaan adalah permintaan berat, sementara 80% adalah" +" permintaan sederhana" #: ../../content/administration/install/deploy.rst:219 msgid "" "A heavy worker, when all computed field are well designed, SQL requests are " "well designed, ... is estimated to consume around 1GB of RAM" msgstr "" +"Worker berat, saat semua computed field dirancang baik, permintaan SQL " +"dirancang baik, ... diperkirakan mengonsumsi sekitar 1 GB RAM" #: ../../content/administration/install/deploy.rst:220 msgid "" "A lighter worker, in the same scenario, is estimated to consume around 150MB" " of RAM" msgstr "" +"Worker lebih ringan, di skenario yang sama, diperkirakan mengonsumsi sekitar" +" 150MB RAM" #: ../../content/administration/install/deploy.rst:222 msgid "" "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " "+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" msgstr "" +"RAM yang Dibutuhkan = #worker * ( (rasio_worker_ringan * " +"estimasi_ram_worker_ringan) + (rasio_worker_berat * " +"estimasi_ram_worker_berat) )" #: ../../content/administration/install/deploy.rst:225 #: ../../content/administration/install/deploy.rst:412 msgid "LiveChat" -msgstr "" +msgstr "LiveChat" #: ../../content/administration/install/deploy.rst:227 msgid "" @@ -727,40 +841,50 @@ msgid "" " --proxy-mode>` so it uses the real client headers (such as hostname, " "scheme, and IP) instead of the proxy ones." msgstr "" +"Di multi-processing, worker LiveChat khusus secara otomatis dinyalakan dan " +"mendengarkan pada :option:`--gevent-port <odoo-bin --gevent-port>`. Secara " +"default, permintaan HTTP akan terus mengakses worker HTTP normal alih-alih " +"worker LiveChat. Anda harus deploy sebuah proxy di depan Odoo dan " +"mengalihkan ulang permintaan masuk yang mana path-nya dimulai dengan " +"``/websocket/`` ke worker LiveChat. Anda juga harus memulai Odoo di " +":option:`--proxy-mode <odoo-bin --proxy-mode>` supaya Odoo menggunakan " +"header asli klien (seperti hostname, scheme, dan IP) alih-alih milik proxy." #: ../../content/administration/install/deploy.rst:237 msgid "Server with 4 CPU, 8 Thread" -msgstr "" +msgstr "Server dengan 4 CPU, 8 Thread" #: ../../content/administration/install/deploy.rst:238 msgid "60 concurrent users" -msgstr "" +msgstr "60 user bersamaan" #: ../../content/administration/install/deploy.rst:240 msgid "60 users / 6 = 10 <- theoretical number of worker needed" -msgstr "" +msgstr "60 user / 6 = 10 <- jumlah teoretis worker yang dibutuhkan" #: ../../content/administration/install/deploy.rst:241 msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" -msgstr "" +msgstr "(4 * 2) + 1 = 9 <- jumlah teoretis maksimal worker" #: ../../content/administration/install/deploy.rst:242 msgid "" "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " "measure cpu load, and check if it's between 7 and 7.5 ." msgstr "" +"Kita gunakan 8 worker + 1 untuk cron. Kita juga akan menggunakan sistem " +"monitoring untuk mengukur beban cpu, dan memerika apakah di antara 7 dan 7.5" #: ../../content/administration/install/deploy.rst:243 msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" -msgstr "" +msgstr "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM untuk Odoo" #: ../../content/administration/install/deploy.rst:245 msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:" -msgstr "" +msgstr "di :ref:`file konfigurasi <reference/cmdline/config_file>`:" #: ../../content/administration/install/deploy.rst:261 msgid "HTTPS" -msgstr "" +msgstr "HTTPS" #: ../../content/administration/install/deploy.rst:263 msgid "" @@ -769,42 +893,51 @@ msgid "" "Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " "just about any SSL termination proxy, but requires the following setup:" msgstr "" +"Baik diakses melalui website/web client atau web service, Odoo mengirimkan " +"informasi autentikasi dalam cleartext. Ini berarti deployment aman dari Odoo" +" harus menggunakan HTTPS\\ [#switching]_. SSL termination dapat " +"diimplementasikan melalui hampir semua SSL termination proxy, tapi " +"membutuhkan setup berikut:" #: ../../content/administration/install/deploy.rst:268 msgid "" "Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only" " be enabled when Odoo is behind a reverse proxy" msgstr "" +"Aktifkan :option:`proxy mode <odoo-bin --proxy-mode>` Odoo. Ini seharusnya " +"hanya diaktifkan saat Odoo di belakang reverse proxy" #: ../../content/administration/install/deploy.rst:269 msgid "Set up the SSL termination proxy (`Nginx termination example`_)" -msgstr "" +msgstr "Setup SSL termination proxy (contoh `Nginx termination`_)" #: ../../content/administration/install/deploy.rst:270 msgid "Set up the proxying itself (`Nginx proxying example`_)" -msgstr "" +msgstr "Setup proxy tersebut sendiri (contoh `Nginx proxying`_)" #: ../../content/administration/install/deploy.rst:271 msgid "" "Your SSL termination proxy should also automatically redirect non-secure " "connections to the secure port" msgstr "" +"SSL termination proxy Anda harus secara otomatis mengalihkan ulang hubungan " +"yang tidak aman ke port yang aman" #: ../../content/administration/install/deploy.rst:277 msgid "Redirect http requests to https" -msgstr "" +msgstr "Alihkan ulang permintaan http menjadi https" #: ../../content/administration/install/deploy.rst:278 msgid "Proxy requests to odoo" -msgstr "" +msgstr "Permintaan proxy ke odoo" #: ../../content/administration/install/deploy.rst:286 msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" -msgstr "" +msgstr "di ``/etc/nginx/sites-enabled/odoo.conf`` tetapkan:" #: ../../content/administration/install/deploy.rst:361 msgid "HTTPS Hardening" -msgstr "" +msgstr "HTTPS Hardening" #: ../../content/administration/install/deploy.rst:363 msgid "" @@ -814,12 +947,19 @@ msgid "" "this domain at all times, otherwise your users will see security alerts or " "be entirely unable to access it." msgstr "" +"Menambahkan header `Strict-Transport-Security` ke semua permintaan, untuk " +"mencegah browser mengirimkan permintaan HTTP plain ke domain ini. Anda harus" +" selalu menjaga layanan HTTPS yang bekerja dengan sertifikat valid pada " +"domain ini, bila tidak, user-user Anda akan melihat peringatan keamanan atau" +" tidak dapat mengaksesnya sama sekali." #: ../../content/administration/install/deploy.rst:369 msgid "" "Force HTTPS connections during a year for every visitor in NGINX with the " "line:" msgstr "" +"Semua pengunjung yang masuk melalui NGINX diarahkan secara paksa untuk " +"menggunakan koneksi HTTPS selama satu tahun:" #: ../../content/administration/install/deploy.rst:375 msgid "" @@ -827,10 +967,13 @@ msgid "" "`Secure` flag can be added to ensure it is never transmitted over HTTP and " "`SameSite=Lax` to prevent authenticated `CSRF`_." msgstr "" +"Konfigurasi tambahan dapat didefinisikan untuk cookie `session_id`. Flag " +"`Secure` juga dapat ditambahkan untuk memastikan mereka tidak pernah dikirim" +" melalui HTTP dan `SameSite=Lax` untuk mencegah `CSRF`_ yang diautentikasi." #: ../../content/administration/install/deploy.rst:386 msgid "Odoo as a WSGI Application" -msgstr "" +msgstr "Odoo sebagai Aplikasi WSGI" #: ../../content/administration/install/deploy.rst:388 msgid "" @@ -841,6 +984,12 @@ msgid "" ":mod:`odoo.tools.config` rather than through the command-line or a " "configuration file." msgstr "" +"Odoo juga dapat di-mount sebagai aplikasi standar WSGI_. Odoo menyediakan " +"dasar untuk script launcher WSGI sebagai ``odoo-wsgi.example.py``. Script " +"tersebut harus dikustomisasi (sebaiknya setelah menyalinnya langsung dari " +"direktori setup) untuk dengan tepat mengonfigurasinya langsung di " +":mod:`odoo.tools.config` alih-alih melalui command-line atau file " +"konfigurasi." #: ../../content/administration/install/deploy.rst:394 msgid "" @@ -848,10 +997,13 @@ msgid "" "client, website and webservice API. Because Odoo does not control the " "creation of workers anymore it can not setup cron or livechat workers" msgstr "" +"Namun server WSGI hanya akan mengekspos endpoint HTTP utama untuk web " +"client, website dan webservice API. Karena Odoo tidak mengontrol pembuatan " +"worker lagi Odoo tidak dapat setup cron atau livechat worker" #: ../../content/administration/install/deploy.rst:399 msgid "Cron Workers" -msgstr "" +msgstr "Cron Worker" #: ../../content/administration/install/deploy.rst:401 msgid "" @@ -861,6 +1013,11 @@ msgid "" "--no-http>` cli option or the ``http_enable = False`` configuration file " "setting." msgstr "" +"Anda harus memulai salah satu server bawaan Odoo disamping server WSGI untuk" +" dapat memproses cron job. Server tersebut harus dikonfigurasi untuk hanya " +"memproses cron dan bukan permintaan HTTP menggunakan cli option " +":option:`--no-http <odoo-bin --no-http>` atau pengaturan file konfigurasi " +"``http_enable = False``." #: ../../content/administration/install/deploy.rst:406 msgid "" @@ -870,6 +1027,11 @@ msgid "" "--workers>` and :option:`--max-cron-threads=n <odoo-bin --max-cron-threads>`" " cli options." msgstr "" +"Pada sistem seperti Linux, disarankan untuk menggunakan server multi-" +"processing alih-alih multi-threading agar dapat memanfaatkan penggunaan " +"hardware yang lebih baik dan peningkatan stabilitas, misalnya, menggunakan " +"cli option :option:`--workers=-1 <odoo-bin --workers>` dan :option:`--max-" +"cron-threads=n <odoo-bin --max-cron-threads>`." #: ../../content/administration/install/deploy.rst:414 msgid "" @@ -880,6 +1042,13 @@ msgid "" "directed to that server. A regular (thread/process-based) WSGI server should" " be used for all other requests." msgstr "" +"Menggunakan server WSGI yang gevent-compatible dibutuhkan untuk " +"pengoperasian fitur live chat yang tepat. Server tersebut harus dapat " +"menangani banyak hubungan serentak yang berumur panjang tapi tidak " +"membutuhkan banyak processing power. Semua permintaan yang mana path-nya " +"dimulai dengan ``/websocket/`` harus dialihkan ke server tersebut. Server " +"WSGI reguler (berdasarkan thread/process) sebaiknya digunakan untuk " +"permintaan-permintaan lainnya." #: ../../content/administration/install/deploy.rst:420 msgid "" @@ -890,10 +1059,16 @@ msgid "" "--http-port>` (multi-threading server) or on the :option:`--gevent-port " "<odoo-bin --gevent-port>` (multi-processing server)." msgstr "" +"Cron server Odoo juga dapat digunakan untuk melayani permintaan live chat. " +"Cukup drop cli option :option:`--no-http <odoo-bin --no-http>` dari cron " +"server dan pastikan permintaan yang path-nya dimulai dengan ``/websocket/`` " +"dialihkan ke server ini, baik pada :option:`--http-port <odoo-bin --http-" +"port>` (server multi-threading) atau pada :option:`--gevent-port <odoo-bin " +"--gevent-port>` (server multi-processing)." #: ../../content/administration/install/deploy.rst:429 msgid "Serving static files and attachments" -msgstr "" +msgstr "Menyajikan file statik dan lampiran" #: ../../content/administration/install/deploy.rst:431 msgid "" @@ -902,10 +1077,14 @@ msgid "" "performances, and static files should generally be served by a static HTTP " "server." msgstr "" +"Untuk kemudahan development, Odoo secara langsung menyajikan semua file " +"statik dan lampiran dalam modulnya. Ini mungkin tidak ideal bila mengenai " +"performa, dan file statik harus secara umum disajikan oleh server HTTP " +"static." #: ../../content/administration/install/deploy.rst:436 msgid "Serving static files" -msgstr "" +msgstr "Melayani file statik" #: ../../content/administration/install/deploy.rst:438 msgid "" @@ -914,6 +1093,10 @@ msgid "" ":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " "in the various addons paths." msgstr "" +"File statik Odoo berlokasi di setiap folder :file:`static/` module, maka " +"file statik dapat disajikan dengan mencegat semua permintaan ke " +":samp:`/{MODULE}/static/{FILE}`, dan mencari modul (dan file) yang tepat di " +"beragam addon path." #: ../../content/administration/install/deploy.rst:442 msgid "" @@ -923,12 +1106,20 @@ msgid "" ":file:`static/` folder and existing images are final (they do not fetch new " "resources by themselves). However, it is good practice." msgstr "" +"Disarankan untuk menetapkan header ``Content-Security-Policy: default-src " +"'none'`` pada semua gambar yang dikirim oleh web server. Ini tidak harus " +"dilakukan karena user tidak dapat memodifikasi/inject konten di dalam folder" +" :file:`static/` modul dan gambar yang ada bersifat final (mereka tidak " +"mengambil sumber daya baru secara sendiri). Namun, ini tetap merupakan " +"praktik yang baik. " #: ../../content/administration/install/deploy.rst:447 msgid "" "Using the above NGINX (https) configuration, the following ``map`` and " "``location`` blocks should be added to serve static files via NGINX." msgstr "" +"Menggunakan konfigurasi NGINX (https) di atas, blok ``map`` dan ``location``" +" di atas harusnya ditambahkan untuk menyajikan file statik melalui NGINX." #: ../../content/administration/install/deploy.rst:474 msgid "" @@ -936,10 +1127,12 @@ msgid "" "installation, specifically on your :option:`--addons-path <odoo-bin " "--addons-path>`." msgstr "" +"Directive ``root`` dan ``try_files`` yang asli tergantung pada penginstalan " +"Anda, terutama pada :option:`--addons-path <odoo-bin --addons-path>` Anda." #: ../../content/administration/install/deploy.rst:481 msgid "Debian package" -msgstr "" +msgstr "Debian package" #: ../../content/administration/install/deploy.rst:483 msgid "" @@ -947,15 +1140,18 @@ msgid "" "Enterprise, and that the :option:`--addons-path <odoo-bin --addons-path>` is" " ``'/usr/lib/python3/dist-packages/odoo/addons'``." msgstr "" +"Katakan Odoo telah diinstal melalui **debian packages** untuk Community dan " +"Enterprise, dan :option:`--addons-path <odoo-bin --addons-path>` adalah " +"``'/usr/lib/python3/dist-packages/odoo/addons'``." #: ../../content/administration/install/deploy.rst:487 #: ../../content/administration/install/deploy.rst:501 msgid "The ``root`` and ``try_files`` should be:" -msgstr "" +msgstr "``root`` dan ``try_files`` harusnya adalah:" #: ../../content/administration/install/deploy.rst:494 msgid "Git sources" -msgstr "" +msgstr "Git source" #: ../../content/administration/install/deploy.rst:496 msgid "" @@ -965,10 +1161,15 @@ msgid "" "path <odoo-bin --addons-path>` is " "``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." msgstr "" +"Katakan Odoo telah diinstal melalui **sources**, yang mana repositori git " +"Community dan Enterprise-nya diklon di :file:`/opt/odoo/community` dan " +":file:`/opt/odoo/enterprise` sesuai urutan, dan :option:`--addons-path " +"<odoo-bin --addons-path>` adalah " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." #: ../../content/administration/install/deploy.rst:509 msgid "Serving attachments" -msgstr "" +msgstr "Menyajikan lampiran" #: ../../content/administration/install/deploy.rst:511 msgid "" @@ -977,6 +1178,11 @@ msgid "" "them requires multiple lookups in the database to determine where the files " "are stored and whether the current user can access them or not." msgstr "" +"Lampiran adalah file yang disimpan di filestore yang mana aksesnya " +"diregulasi oleh Odoo. Mereka tidak dapat diakses langsung melalui web server" +" statik karena mengakses mereka membutuhkan lebih dari satu lookup di " +"database untuk menentukan di mana file disimpan dan apakah user saat ini " +"dapat mengakses mereka atau tidak." #: ../../content/administration/install/deploy.rst:516 msgid "" @@ -991,18 +1197,30 @@ msgid "" "--x-sendfile>` CLI flag (this unique flag is used for both X-Sendfile and " "X-Accel)." msgstr "" +"Kendati demikian, setelah file telah ditemukan dan hak akses diverifikasi " +"oleh Odoo, merupakan ide baik untuk menyajikan file menggunakan web server " +"statik alih-alih Odoo. Agar Odoo untuk mendelegasikan penyajian file ke web " +"server statik, extension `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ " +"(apache) atau `X-Accel " +"<https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ " +"(nginx) harus diaktifkan dan dikonfigurasikan pada web server statik. " +"Setelah di setup, jalankan Odoo dengan CLI flag :option:`--x-sendfile <odoo-" +"bin --x-sendfile>` (flag unik ini digunakan untuk X-Sendfile dan X-Accel)." #: ../../content/administration/install/deploy.rst:526 msgid "" "The X-Sendfile extension for apache (and compatible web servers) does not " "require any supplementary configuration." msgstr "" +"Extension X-Sendfile untuk apache (dan web server yang kompatibel) tidak " +"membutuhkan konfigurasi tambahan apapun." #: ../../content/administration/install/deploy.rst:528 msgid "" "The X-Accel extension for NGINX **does** require the following additionnal " "configuration:" msgstr "" +"Extension X-Accel untuk NGINX **membutuhkan** konfigurasi tambahan berikut:" #: ../../content/administration/install/deploy.rst:537 msgid "" @@ -1012,6 +1230,11 @@ msgid "" "NGINX). This logs a warnings, the message contains the configuration you " "need." msgstr "" +"Apabila Anda tidak tahu path ke filestore Anda, nyalakan Odoo dengan opsi " +":option:`--x-sendfile <odoo-bin --x-sendfile>` dan navigasi ke URL " +"``/web/filestore`` langsung melalui Odoo (jangan menavigasi ke URL melalui " +"NGINX). Ini akan mencatat peringatan, pesannya akan memiliki konfigurasi " +"yang Anda butuhkan. " #: ../../content/administration/install/deploy.rst:546 msgid "Security" @@ -1023,6 +1246,9 @@ msgid "" "continuous process, not a one-shot operation. At any moment, you will only " "be as secure as the weakest link in your environment." msgstr "" +"Untuk awal-awal, ingat bahwa mengamankan sistem informasi adalah proses yang" +" berkelanjutan, bukan operasi yang sekali-selesai. Kapan pun juga, Anda " +"hanya akan seaman rantai terlemah di environment Anda." #: ../../content/administration/install/deploy.rst:552 msgid "" @@ -1033,12 +1259,20 @@ msgid "" "system and distribution, best practices in terms of users, passwords, and " "access control management, etc." msgstr "" +"Jadi tolong jangan ambil bagian dari dokumentasi ini sebagai daftar " +"termutakhir pengukuran keamanan yang akan mencegah semua masalah keamanan. " +"Pedoman ini hanya ditujukan sebagai ringkasan dari hal-hal pertama yang " +"harus Anda masukkan pada rencana keamanan Anda. Sisanya akan datang dengan " +"praktek keamanan yang baik untuk OS dan distribusi Anda, praktek terbaik " +"dalam hal user, password, dan manajemen kontrol akses, dsb. " #: ../../content/administration/install/deploy.rst:558 msgid "" "When deploying an internet-facing server, please be sure to consider the " "following security-related topics:" msgstr "" +"Saat men-deploy server yang menggunakan internet, mohon pertimbangkan topik-" +"topik terkait keamanan berikut:" #: ../../content/administration/install/deploy.rst:561 msgid "" @@ -1046,6 +1280,9 @@ msgid "" "database management pages as soon as the system is set up. See " ":ref:`db_manager_security`." msgstr "" +"Selalu tetapkan password admin super-admin yang kuat, dan batasi akses ke " +"halaman-halaman manajemen database setelah sistem di-setup. Lihat " +":ref:`db_manager_security`." #: ../../content/administration/install/deploy.rst:564 msgid "" @@ -1055,6 +1292,11 @@ msgid "" "*Never* use any default passwords like admin/admin, even for test/staging " "databases." msgstr "" +"Pilih login yang unik dan password yang kuat untuk semua akun administrator " +"pada semua database. Jangan gunakan 'admin' sebagai login. Jangan gunakan " +"login tersebut untuk operasi keseharian, hanya untuk mengontrol/menangani " +"penginstalan. *Jangan pernah* menggunakan password default apapun seperti " +"admin/admin, bahkan untuk database test/staging." #: ../../content/administration/install/deploy.rst:569 msgid "" @@ -1062,6 +1304,10 @@ msgid "" " data contain default logins and passwords that can be used to get into your" " systems and cause significant trouble, even on staging/dev systems." msgstr "" +"**Jangan** menginstal data demo pada server yang menggunakan internet. " +"Database dengan data demo memiliki secara default login dan password yang " +"dapat digunakan untuk memasuki sistem Anda dan menghasilkan masalah yang " +"signifikan, bahkan pada sistem staging/dev." #: ../../content/administration/install/deploy.rst:573 msgid "" @@ -1072,6 +1318,12 @@ msgid "" "from, instead of letting the system fetch them all from the database " "backend." msgstr "" +"Gunakan filter database yang sesuai ( :option:`--db-filter <odoo-bin --db-" +"filter>`) untuk membatasi visibilitas database Anda sesuai dengan nama host." +" Lihat :ref:`db_filter`. Anda juga mungkin ingin menggunakan :option:`-d " +"<odoo-bin -d>` untuk menyediakan daftar Anda sendiri untuk database yang " +"tersedia (yang dipisahkan koma) untuk difilter, alih-alih membiarkan sistem " +"mengambil mereka semua dari backend database." #: ../../content/administration/install/deploy.rst:580 msgid "" @@ -1214,11 +1466,11 @@ msgstr "" #: ../../content/administration/install/deploy.rst:667 msgid "Failed login::" -msgstr "" +msgstr "Login gagal::" #: ../../content/administration/install/deploy.rst:671 msgid "Successful login::" -msgstr "" +msgstr "Login berhasil::" #: ../../content/administration/install/deploy.rst:676 msgid "" diff --git a/locale/id/LC_MESSAGES/websites.po b/locale/id/LC_MESSAGES/websites.po index fc7e9e832..72290ab69 100644 --- a/locale/id/LC_MESSAGES/websites.po +++ b/locale/id/LC_MESSAGES/websites.po @@ -5,8 +5,8 @@ # # Translators: # Martin Trigaux, 2023 -# Abe Manyo, 2023 # Wil Odoo, 2024 +# Abe Manyo, 2024 # #, fuzzy msgid "" @@ -15,7 +15,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Wil Odoo, 2024\n" +"Last-Translator: Abe Manyo, 2024\n" "Language-Team: Indonesian (https://app.transifex.com/odoo/teams/41243/id/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -7815,7 +7815,7 @@ msgstr "" #: ../../content/applications/websites/website/pages/seo.rst:224 msgid "HTTPS" -msgstr "" +msgstr "HTTPS" #: ../../content/applications/websites/website/pages/seo.rst:226 msgid "" diff --git a/locale/ja/LC_MESSAGES/administration.po b/locale/ja/LC_MESSAGES/administration.po index a70c1347e..940e47730 100644 --- a/locale/ja/LC_MESSAGES/administration.po +++ b/locale/ja/LC_MESSAGES/administration.po @@ -1543,7 +1543,7 @@ msgstr "" #: ../../content/administration/install/source.rst:384 #: ../../content/administration/install/source.rst:446 msgid "Linux" -msgstr "" +msgstr "Linux" #: ../../content/administration/install/packages.rst:28 #: ../../content/administration/install/source.rst:116 @@ -1822,7 +1822,7 @@ msgstr "" #: ../../content/administration/install/source.rst:405 #: ../../content/administration/install/source.rst:467 msgid "Mac OS" -msgstr "" +msgstr "Mac OS" #: ../../content/administration/install/source.rst:107 msgid "" @@ -7672,7 +7672,7 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 msgid "You can either:" -msgstr "" +msgstr "いずれかが可能です:" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 msgid "" diff --git a/locale/ja/LC_MESSAGES/finance.po b/locale/ja/LC_MESSAGES/finance.po index 56ad948d2..c62c5f9ec 100644 --- a/locale/ja/LC_MESSAGES/finance.po +++ b/locale/ja/LC_MESSAGES/finance.po @@ -5,13 +5,13 @@ # # Translators: # Yoshi Tashiro (Quartile) <tashiro@roomsfor.hk>, 2023 -# Ryoko Tsuda <ryoko@quartile.co>, 2023 # 江口和志 <sandwhale1010@gmail.com>, 2023 # Tim Siu Lai <tl@roomsfor.hk>, 2023 # Noma Yuki, 2023 # Martin Trigaux, 2024 # Wil Odoo, 2024 # Junko Augias, 2024 +# Ryoko Tsuda <ryoko@quartile.co>, 2024 # #, fuzzy msgid "" @@ -20,7 +20,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Junko Augias, 2024\n" +"Last-Translator: Ryoko Tsuda <ryoko@quartile.co>, 2024\n" "Language-Team: Japanese (https://app.transifex.com/odoo/teams/41243/ja/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -213,7 +213,7 @@ msgstr "取引明細書" #: ../../content/applications/finance/accounting.rst:135 #: ../../content/applications/finance/accounting/customer_invoices.rst:216 msgid "Balance sheet" -msgstr "バランスシート" +msgstr "貸借対照表" #: ../../content/applications/finance/accounting.rst:137 #: ../../content/applications/finance/accounting/customer_invoices.rst:206 @@ -7448,7 +7448,7 @@ msgstr "勘定科目タイプ" #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 #: ../../content/applications/finance/fiscal_localizations/spain.rst:29 msgid "Balance Sheet" -msgstr "バランスシート" +msgstr "貸借対照表" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 @@ -37923,12 +37923,6 @@ msgid "" "platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "" diff --git a/locale/ja/LC_MESSAGES/inventory_and_mrp.po b/locale/ja/LC_MESSAGES/inventory_and_mrp.po index bb80fadad..3665b1d98 100644 --- a/locale/ja/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/ja/LC_MESSAGES/inventory_and_mrp.po @@ -4806,6 +4806,7 @@ msgstr "" msgid "" ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 msgid "" diff --git a/locale/ja/LC_MESSAGES/productivity.po b/locale/ja/LC_MESSAGES/productivity.po index ccb97bdf2..f4e76b26b 100644 --- a/locale/ja/LC_MESSAGES/productivity.po +++ b/locale/ja/LC_MESSAGES/productivity.po @@ -6,16 +6,16 @@ # Translators: # Andy Yiu, 2023 # Wil Odoo, 2023 -# Junko Augias, 2023 +# Junko Augias, 2024 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Junko Augias, 2023\n" +"Last-Translator: Junko Augias, 2024\n" "Language-Team: Japanese (https://app.transifex.com/odoo/teams/41243/ja/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -2531,7 +2531,7 @@ msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 #: ../../content/applications/productivity/iot/config/windows_iot.rst:105 msgid "Troubleshooting" -msgstr "" +msgstr "トラブルシューティング" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 msgid "IoT box connection" @@ -8425,26 +8425,28 @@ msgstr "" #: ../../content/applications/productivity/to_do.rst:23 msgid "" -"You can create a new to-do on the fly from anywhere in Odoo by clicking the " -"clock button and then :guilabel:`Add a To-Do`." +"You can create a new to-do on the fly from anywhere in Odoo by opening the " +"**command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking " +":guilabel:`Add a To-Do`, or by clicking the clock button and then " +":guilabel:`Add a To-Do`." msgstr "" #: ../../content/applications/productivity/to_do.rst:0 msgid "Adding a to-do on the fly" msgstr "" -#: ../../content/applications/productivity/to_do.rst:30 +#: ../../content/applications/productivity/to_do.rst:31 msgid "Converting to-dos into project tasks" msgstr "" -#: ../../content/applications/productivity/to_do.rst:32 +#: ../../content/applications/productivity/to_do.rst:33 msgid "" "If you use the :doc:`Project app <../services/project>`, you can convert to-" "dos into project tasks. To do so, open a to-do and click the gear button " "(:guilabel:`⚙`), then :guilabel:`Convert to Task`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:35 +#: ../../content/applications/productivity/to_do.rst:36 msgid "" "Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and " ":guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a" @@ -8455,11 +8457,11 @@ msgstr "" msgid "Converting a to-do into a task" msgstr "" -#: ../../content/applications/productivity/to_do.rst:42 +#: ../../content/applications/productivity/to_do.rst:43 msgid "Managing the to-do pipeline" msgstr "" -#: ../../content/applications/productivity/to_do.rst:44 +#: ../../content/applications/productivity/to_do.rst:45 msgid "" "Your assigned **to-dos** are displayed on the app dashboard. You can drag " "and drop a to-do to move it from one stage to another." @@ -8469,13 +8471,13 @@ msgstr "" msgid "Example of a to-do pipeline" msgstr "" -#: ../../content/applications/productivity/to_do.rst:51 +#: ../../content/applications/productivity/to_do.rst:52 msgid "" "Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to" " create a new stage." msgstr "" -#: ../../content/applications/productivity/to_do.rst:53 +#: ../../content/applications/productivity/to_do.rst:54 msgid "" "Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, " ":guilabel:`Edit`, or :guilabel:`Delete` it." @@ -8485,11 +8487,11 @@ msgstr "" msgid "Stage settings button" msgstr "" -#: ../../content/applications/productivity/to_do.rst:60 +#: ../../content/applications/productivity/to_do.rst:61 msgid "Scheduling activities" msgstr "" -#: ../../content/applications/productivity/to_do.rst:62 +#: ../../content/applications/productivity/to_do.rst:63 msgid "" "To schedule an activity on a to-do, click the clock button on the app " "dashboard, then the :guilabel:`+ Schedule an activity` button." @@ -8499,43 +8501,43 @@ msgstr "" msgid "Scheduling an activity from the To-do dashboard" msgstr "" -#: ../../content/applications/productivity/to_do.rst:68 +#: ../../content/applications/productivity/to_do.rst:69 msgid "To create the activity:" msgstr "" -#: ../../content/applications/productivity/to_do.rst:70 +#: ../../content/applications/productivity/to_do.rst:71 msgid "Select an :guilabel:`Activity Type`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:71 +#: ../../content/applications/productivity/to_do.rst:72 msgid "Select a :guilabel:`Due date`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:72 +#: ../../content/applications/productivity/to_do.rst:73 msgid "Choose who the activity should be :guilabel:`Assigned to`." msgstr "" -#: ../../content/applications/productivity/to_do.rst:73 +#: ../../content/applications/productivity/to_do.rst:74 msgid "" "Add a brief :guilabel:`Summary` if needed. You can add a more elaborate " "description in the :guilabel:`Log a note` box." msgstr "" -#: ../../content/applications/productivity/to_do.rst:76 +#: ../../content/applications/productivity/to_do.rst:77 msgid "Click :guilabel:`Schedule` to complete the action." msgstr "" -#: ../../content/applications/productivity/to_do.rst:79 +#: ../../content/applications/productivity/to_do.rst:80 msgid "" "The :guilabel:`To Do` activity is *not* a to-do task. Selecting it does not " "create a to-do task." msgstr "" -#: ../../content/applications/productivity/to_do.rst:82 +#: ../../content/applications/productivity/to_do.rst:83 msgid "Viewing to-dos in the Project app" msgstr "" -#: ../../content/applications/productivity/to_do.rst:84 +#: ../../content/applications/productivity/to_do.rst:85 msgid "" "If you use the :doc:`Project app <../services/project>`, your to-dos also " "appear as private tasks under the :guilabel:`My Tasks` view." @@ -8545,7 +8547,7 @@ msgstr "" msgid "Example of a \"My Tasks\" pipeline in the Project app" msgstr "" -#: ../../content/applications/productivity/to_do.rst:91 +#: ../../content/applications/productivity/to_do.rst:92 msgid "" "A padlock icon is visible on your private tasks to quickly identify them " "among your project tasks." diff --git a/locale/ja/LC_MESSAGES/sales.po b/locale/ja/LC_MESSAGES/sales.po index 2a8f4617f..89ffd15af 100644 --- a/locale/ja/LC_MESSAGES/sales.po +++ b/locale/ja/LC_MESSAGES/sales.po @@ -2143,26 +2143,26 @@ msgstr ":guilabel:`按分されたMRR`: リードの月次経常収益を按分 msgid "" ":guilabel:`Prorated Recurring Revenues`: measures the Prorated Recurring " "Revenues of a lead." -msgstr ":guilabel:`按分された定期収入`: は、リードの按分された定期収入を測定します。" +msgstr ":guilabel:`按分された定期売上`: は、リードの按分された定期売上を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:272 msgid ":guilabel:`Prorated Revenue`: measures the Prorated Revenue of a lead." -msgstr "" +msgstr ":guilabel:`按分収益`: リードの按分売上を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:273 msgid "" ":guilabel:`Recurring Revenues`: measures the Recurring Revenue of a lead." -msgstr "" +msgstr ":guilabel:`定期売上`: はリードの定期売上を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:274 msgid "" ":guilabel:`Count`: measures the total amount of leads that match the search " "criteria." -msgstr "" +msgstr ":guilabel:`件数`: 検索条件に一致するリードの総数を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:279 msgid "View options" -msgstr "" +msgstr "オプションを見る" #: ../../content/applications/sales/crm/performance/win_loss.rst:281 msgid "" @@ -2171,12 +2171,15 @@ msgid "" "ways. By default, the page uses the graph view, but can be changed to a " "pivot view, cohort view, or list view." msgstr "" +"フィルタ、グループ化、測定を設定した後、 :guilabel:`パイプライン分析` " +"ページは様々な方法でデータを表示することができます。デフォルトではグラフビューを使用しますが、ピボットビュー、コホートビュー、リストビューに変更することもできます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:285 msgid "" "To change the pipeline to a different view, click one of the four view " "icons, located in the top-right of the :guilabel:`Pipeline Analysis` page." msgstr "" +"パイプラインを別のビューに変更するには、 :guilabel:`パイプライン分析` ページの右上にある4つのビューアイコンの1つをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:290 msgid "Graph View" @@ -2188,6 +2191,7 @@ msgid "" "Analysis` page. It displays the analysis as either a: bar chart, line chart," " or pie chart." msgstr "" +"グラフビューは :guilabel:`パイプライン分析` ページのデフォルト選択です。棒グラフ、折れ線グラフ、円グラフのいずれかで分析結果を表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:295 msgid "" @@ -2195,6 +2199,8 @@ msgid "" "relationships, like the :guilabel:`Count` of leads in each stage, or the " "leads assigned to each :guilabel:`Salesperson`." msgstr "" +"このビューオプションは、各ステージにおけるリードの :guilabel:`件数` や、各 :guilabel:`販売担当者` " +"に割当てられたリードのように、単純な関係を素早く視覚化して比較するのに便利です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:299 msgid "" @@ -2203,12 +2209,14 @@ msgid "" ":ref:`selecting another option <win_loss/measure>` from the resulting drop-" "down menu." msgstr "" +"デフォルトでは、グラフは各グループのリードの :guilabel:`件数` を測定しますが、 :guilabel:`測定` " +"ボタンをクリックし、ドロップダウンメニューから :ref:`他のオプションを選択 <win_loss/measure>` することで変更できます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "The Graph View displays the analysis as a Bar Chart, Line Chart, or Pie " "Chart." -msgstr "" +msgstr "グラフビューは、分析を棒グラフ、折れ線グラフ、円グラフで表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:308 msgid "" @@ -2216,6 +2224,8 @@ msgid "" ":guilabel:`Stacked` option, in order to make the breakdown of results more " "legible." msgstr "" +"このビューで棒グラフを使用する場合、結果の内訳をより見やすくするために :guilabel:`積み上げ` " +"オプションの選択を解除することを検討して下さい。" #: ../../content/applications/sales/crm/performance/win_loss.rst:311 #: ../../content/applications/sales/crm/performance/win_loss.rst:512 @@ -2228,6 +2238,8 @@ msgid "" "the table groups the results by the stages of the sales pipeline, and " "measures :guilabel:`Expected Revenue`." msgstr "" +"ピボットビューには、分析結果が表として表示されます。既定では、表は販売パイプラインのステージ別に結果をグループ化し、 :guilabel:`見込売上` " +"を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:316 msgid "" @@ -2235,15 +2247,16 @@ msgid "" "view can handle, or for adding the data to a spreadsheet, where custom " "formulas can be set up, like in an Excel file." msgstr "" +"ピボットビューは、グラフビューで扱えるよりも詳細な数値を分析したり、データをスプレッドシートに追加して、Excelファイルのようにカスタム数式を設定したりするのに便利です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Pivot View displays the analysis as a table." -msgstr "" +msgstr "ピボットビューは、分析を表として表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:324 msgid "" "The three icons at the top-left of the page perform the following functions:" -msgstr "" +msgstr "ページの左上にある3つのアイコンは、以下の機能を果たします:" #: ../../content/applications/sales/crm/performance/win_loss.rst:332 msgid "" @@ -2251,6 +2264,8 @@ msgid "" " changed by clicking the :guilabel:`Measures` button, and selecting another " "option." msgstr "" +"guilabel:`ステージ`のグループ分けを削除することはできませんが、 " +":guilabel:`測定`ボタンをクリックし、別のオプションを選択することで測定値を変更することができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:335 msgid "Cohort View" @@ -2262,34 +2277,36 @@ msgid "" "be set to days, weeks, months, or years. By default, :guilabel:`Week` is " "selected." msgstr "" +"コホートビューでは、日、週、月、年を設定できる期間(コホート)として分析を表示します。デフォルトでは :guilabel:`週` が選択されています。" #: ../../content/applications/sales/crm/performance/win_loss.rst:340 msgid "" "This view option is useful specifically for comparing how long it has taken " "to close leads." -msgstr "" +msgstr "このビューオプションは、特にリードの成約にかかった時間を比較するのに便利です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Cohort View displays the analysis as individual weeks of the year." -msgstr "" +msgstr "コホートビューでは、分析結果を1年ごとの週として表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:346 msgid "" "From left-to-right, top-to-bottom, the columns in the chart represent the " "following:" -msgstr "" +msgstr "左から右へ、上から下へ、チャートの列は以下を表しています:" #: ../../content/applications/sales/crm/performance/win_loss.rst:348 msgid "" ":guilabel:`Created On`: rows in this column represent the weeks of the year," " in which records matching the search criteria exist." -msgstr "" +msgstr ":guilabel:`作成日`: この列の行は、検索条件に一致するレコードが存在する年の週を表します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:351 msgid "" "When set to :guilabel:`Week`, a row with the label :guilabel:`W52 2023` " "means the results occurred in: Week 52 of the Year 2023." msgstr "" +"guilabel:`週`に設定すると、 :guilabel:`W52 2023` というラベルの行は、2023年の第52週に発生した結果を意味します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:353 msgid "" @@ -2298,6 +2315,8 @@ msgid "" "by clicking the :guilabel:`Measures` button, and selecting an option from " "the drop-down menu." msgstr "" +":guilabel:`測定`: チャートの2列目は結果の計測値です。デフォルトでは :guilabel:`カウント` に設定されているが、 " +":guilabel:`測定` ボタンをクリックし、ドロップダウンメニューからオプションを選択することで変更することができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:356 msgid "" @@ -2305,18 +2324,21 @@ msgid "" "percentage of the measured results were closed in subsequent " "days/weeks/months/years." msgstr "" +":guilabel:`クローズ日 - 日/週/月/年ごと`: " +"この列では、測定された結果のうち、何パーセントがその後の日/週/月/年にクローズされたかを見ることができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:358 msgid "" ":guilabel:`Average`: this row provides the average of all other rows in the " "column." -msgstr "" +msgstr ":guilabel:`平均`: この行は列内の他の全ての行の平均を提供します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:360 msgid "" "The cohort view can also be downloaded as an Excel file, by clicking the " ":guilabel:`Download` icon in the top-left of the page." msgstr "" +"ページ左上の :guilabel:`ダウンロード` アイコンをクリックすると、コホートビューをエクセルファイルとしてダウンロードすることもできます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:363 #: ../../content/applications/sales/crm/performance/win_loss.rst:537 @@ -2331,50 +2353,55 @@ msgid "" "added to the list, by clicking the :guilabel:`Filters` icon in the top-right" " of the list." msgstr "" +"リストビューには、検索条件に一致するすべてのリードの単一リストが表示されます。リードをクリックするとレコードが開き、詳しく確認することができます。リストの右上にある" +" :guilabel:`フィルタ` アイコンをクリックすると、 :guilabel:`国` や :guilabel:`媒体` " +"などの詳細情報をリストに追加することができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:370 msgid "This view option is useful for reviewing many records at once." -msgstr "" +msgstr "この表示オプションは、一度に多くのレコードを確認するのに便利です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "The List View displays a single list of all records matching the search " "criteria." -msgstr "" +msgstr "リストビューには、検索条件に一致するすべてのレコードの単一リストが表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:376 msgid "" "Clicking the :guilabel:`⚙️ (gear)` icon opens the Actions drop-down menu, " "with options for the following:" -msgstr "" +msgstr "guilabel:`⚙️ (歯車)` アイコンをクリックすると、Actions ドロップダウンメニューが開き、以下のオプションがあります:" #: ../../content/applications/sales/crm/performance/win_loss.rst:379 msgid "" ":guilabel:`Import records`: opens a page for uploading a spreadsheet of " "data, as well as a template spreadsheet to easily format that data." msgstr "" +":guilabel:`レコードをインポート`: " +"データのスプレッドシートをアップロードするためのページと、そのデータを簡単にフォーマットするためのスプレッドシートのテンプレートが開きます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:381 msgid ":guilabel:`Export All`: downloads the list as an xlsx file for Excel." -msgstr "" +msgstr ":guilabel:`全てをエクスポート`: リストをエクセル用のxlsxファイルとしてダウンロードします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:382 msgid "" ":guilabel:`Knowledge`: inserts a view of, or link to, the list in an article" " in the *Knowledge* app." -msgstr "" +msgstr ":guilabel:`ナレッジ`: *ナレッジ*アプリの記事のリストの表示、またはリンクを挿入します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:384 msgid "" ":guilabel:`Dashboard`: adds the list to *My Dashboard* in the *Dashboards* " "app." -msgstr "" +msgstr ":guilabel:`ダッシュボード`: *ダッシュボード*アプリの*自分のダッシュボード*にリストを追加します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:385 msgid "" ":guilabel:`Spreadsheet`: links to, or inserts, the list in a spreadsheet in " "the *Documents* app." -msgstr "" +msgstr ":guilabel:`スプレッドシート`: *ドキュメント*アプリ内のスプレッドシートにリストをリンク、または挿入します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:389 msgid "" @@ -2383,10 +2410,12 @@ msgid "" "window for lead generation. Neither feature is intended to manipulate the " "list view." msgstr "" +"リストビューで :guilabel:`新規` " +"をクリックするとリストが閉じ、*新規見積*ページが開きます。guilabel:`リード生成`をクリックすると、リード生成のポップアップウィンドウが開きます。どちらの機能もリストビューを操作するためのものではありません。" #: ../../content/applications/sales/crm/performance/win_loss.rst:396 msgid "Create reports" -msgstr "" +msgstr "レポート作成" #: ../../content/applications/sales/crm/performance/win_loss.rst:398 msgid "" @@ -2395,22 +2424,25 @@ msgid "" "create and share different reports. Between the pre-made options and custom " "filter and groupings, almost any combination is possible." msgstr "" +"ref:`パイプライン分析のナビゲート <win_loss/pipeline>` 方法を理解した後、 :guilabel:`パイプライン分析` " +"ページを使って様々なレポートを作成し、共有することができます。あらかじめ用意されているオプションとカスタムのフィルターやグループ化の間で、ほとんど全ての組み合わせが可能です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:402 msgid "" "Once created, reports can be :ref:`saved to favorites, shared with other " "users, and/or added to dashboards and spreadsheets <win_loss/save_reports>`." msgstr "" +"一度作成したレポートは、:ref:`お気に入りに保存したり、他のユーザと共有したり、ダッシュボードやスプレッドシート<win_loss/save_reports>`に追加したりすることができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:405 msgid "" "A few common reports that can be created using the :guilabel:`Pipeline " "Analysis` page are detailed below." -msgstr "" +msgstr "guilabel:`パイプライン分析`ページを使って作成できるいくつかの一般的なレポートを以下に詳述します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:411 msgid "Win/Loss reports" -msgstr "" +msgstr "成約/失注レポート" #: ../../content/applications/sales/crm/performance/win_loss.rst:413 msgid "" @@ -2421,6 +2453,7 @@ msgid "" "sales, such as specific teams or team members, certain marketing mediums or " "campaigns, and so on." msgstr "" +"成約/失注は、特定の期間において**成約**または**失注**とマークされた、パイプライン内の有効または以前に有効だったリードの計算です。案件損失よりも成約案件を計算することで、チームは、特定のチームやチームメンバ、特定のマーケティング媒体やキャンペーンなど、リードを売上に転換している主要業績評価指標(KPI)を明確にすることができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:419 msgid "" @@ -2429,6 +2462,10 @@ msgid "" "\\end{equation}\n" "\n" msgstr "" +"\\begin{equation}\n" +"Win/Loss Ratio = \\frac{Opportunities Won}{Opportunities Lost}\n" +"\\end{equation}\n" +"\n" #: ../../content/applications/sales/crm/performance/win_loss.rst:424 msgid "" @@ -2436,20 +2473,22 @@ msgid "" " and groups the results by their stage in the pipeline. Creating this report" " requires a custom filter, and grouping the results by :guilabel:`Stage`." msgstr "" +"成約/失注レポートは、過去1年間のリードの成約または失注をフィルタリングし、パイプラインのステージごとに結果をグループ化します。このレポートを作成するには、カスタムフィルタを作成し、結果を" +" :guilabel:`ステージ` でグループ化する必要があります。" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The search criteria for win/loss reports is Created On, Stage, and Active is" " in true false." -msgstr "" +msgstr "成約/失注レポートの検索条件は、作成日、ステージ、有効が真偽です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:432 msgid "Follow the steps below to create a win/loss report:" -msgstr "" +msgstr "以下の手順に従って、成約/失注レポートを作成して下さい:" #: ../../content/applications/sales/crm/performance/win_loss.rst:434 msgid "Navigate to :menuselection:`CRM app --> Reporting --> Pipeline`." -msgstr "" +msgstr "menuselection:`CRMアプリ --> レポ―ティング --> パイプライン`に移動します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:435 msgid "" @@ -2457,22 +2496,25 @@ msgid "" "arrow)` icon, next to the search bar, to open a drop-down menu of filters " "and groupings." msgstr "" +"guilabel:`パイプライン分析`ページで、検索バーの隣にある :guilabel:`⬇️ " +"(下向き矢印)`アイコンをクリックすると、フィルタとグループ分けのドロップダウンメニューが開きます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Search menu containing the filters for a basic win/loss report." -msgstr "" +msgstr "基本的な成約/失注レポートのフィルタを含む検索メニュー。" #: ../../content/applications/sales/crm/performance/win_loss.rst:442 msgid "" "In drop-down menu that appears, under the :guilabel:`Group By` heading, " "click :guilabel:`Stage`." -msgstr "" +msgstr "表示されたドロップダウンメニューの :guilabel:`グループ分` の下にある :guilabel:`ステージ` をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:443 msgid "" "Under the :guilabel:`Filters` heading, click :guilabel:`Add Custom Filter` " "to open another pop-up menu." msgstr "" +"guilabel:`フィルタ` の下にある :guilabel:`カスタムフィルタを追加` をクリックすると、別のポップアップメニューが開きます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:445 msgid "" @@ -2480,6 +2522,9 @@ msgid "" "in the :guilabel:`Match any of the following rules:` section. By default, " "this field displays :guilabel:`Country`." msgstr "" +"guilabel:`カスタムフィルタ追加`ポップアップメニューで、 " +":guilabel:`次の規則のいずれかに一致する:`セクションの最初のフィールドをクリックします。デフォルトでは、このフィールドには " +":guilabel:`国` が表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:448 msgid "" @@ -2487,16 +2532,20 @@ msgid "" " from. From this sub-menu, locate and select the :guilabel:`Active` option. " "Doing so automatically populates the remaining fields." msgstr "" +"その最初のフィールドをクリックすると、多数のオプションから選択できるサブメニューが表示されます。このサブメニューから :guilabel:`有効` " +"オプションを見つけて選択します。そうすることで、残りのフィールドに自動的に入力されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:452 msgid "" "The first field reads: :guilabel:`Active`. The second field reads: " ":guilabel:`is`. And lastly, the third field reads: :guilabel:`set`." msgstr "" +"最初のフィールドは :guilabel:`有効` " +"です。2番目のフィールドは:guilabel:`が`です。最後に、3番目のフィールドは:guilabel:`設定済`です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:455 msgid "In total, the rule reads: :guilabel:`Active is set`." -msgstr "" +msgstr "全体で規則は、guilabel:`有効が設定済`となります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:456 msgid "" @@ -2504,17 +2553,19 @@ msgid "" "and the last field to :guilabel:`not set`. In total, the rule reads " ":guilabel:`Active is not set`." msgstr "" +"guilabel:`新しい規則`をクリックし、最初のフィールドを :guilabel:`有効`に、最後のフィールドを " +":guilabel:`未設定`に変更する。全体で規則は :guilabel:`有効が未設定` となります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:458 #: ../../content/applications/sales/crm/performance/win_loss.rst:640 msgid "Click :guilabel:`Add`." -msgstr "" +msgstr ":guilabel:`追加`をクリック。" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "The Add Custom Filter menu showing two rules: (1) Active is set, and (2) " "Active is not set." -msgstr "" +msgstr "カスタムフィルタの追加]メニューには、(1)有効が設定済、(2)有効が未設定、の2つの規則が表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:464 msgid "" @@ -2522,22 +2573,24 @@ msgid "" "\"Won\" or \"Lost,\" grouped by their stage in the CRM pipeline. Hover over " "a section of the report to see the number of leads in that stage." msgstr "" +"このレポートでは、\"成約\" or \"失注\"にかかわらず、リードの合計 :guilabel:`件数` " +"をCRMパイプラインのステージごとにグループ化して表示するようになりました。レポートのセクションにカーソルを合わせると、そのステージのリード数が表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst-1 msgid "" "A basic win/loss report showing all leads whether won or lost grouped by " "stage." -msgstr "" +msgstr "基本的な成約/失注レポートは、成約か失注かにかかわらず全てのリードをステージごとにグループ分けして表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:473 msgid "Customize win/loss reports" -msgstr "" +msgstr "成約/失注レポートのカスタマイズ" #: ../../content/applications/sales/crm/performance/win_loss.rst:475 msgid "" "After :ref:`creating a win/loss report <win_loss/win_loss>`, consider using " "the options below to customize the report for different needs." -msgstr "" +msgstr "ref:`成約/失注レポート<win_loss/win_loss>`を作成したら、以下のオプションを使ってレポートをカスタマイズ下さい。" #: ../../content/applications/sales/crm/performance/win_loss.rst:479 msgid "" @@ -2546,10 +2599,11 @@ msgid "" " sources, or medium, to determine where their advertising has been most " "successful." msgstr "" +"販売マネージャは、販売担当者や販売チームごとに成約/失注をグループ化し、誰が最も変換率が高いかを確認するかもしれません。あるいは、マーケティングチームは、広告が最も成功した場所を特定するために、情報源や媒体ごとにグループ化するかもしれません。" #: ../../content/applications/sales/crm/performance/win_loss.rst:485 msgid "Filters and groups" -msgstr "" +msgstr "フィルタとグループ" #: ../../content/applications/sales/crm/performance/win_loss.rst:487 msgid "" @@ -2557,10 +2611,12 @@ msgid "" "next to the search bar, and select one or more options from the drop-down " "menu." msgstr "" +"さらにフィルタやグループを追加するには、検索バーの隣にある :guilabel:`⬇️ " +"(下向き矢印)`アイコンをクリックし、ドロップダウンメニューから1つ以上のオプションを選択します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:490 msgid "Some useful options include:" -msgstr "" +msgstr "便利なオプションに以下があります:" #: ../../content/applications/sales/crm/performance/win_loss.rst:492 msgid "" @@ -2568,6 +2624,7 @@ msgid "" " such as the last 30 days, or the last quarter, can provide more timely " "results." msgstr "" +":guilabel:`作成日`: このフィルタを、直近30日や直近四半期など、異なる期間に調整することで、よりタイムリーな結果を得ることができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:494 msgid "" @@ -2575,6 +2632,8 @@ msgid "" "the numerous options in the drop-down menu, opens up additional search " "criteria, like :guilabel:`Last Stage Update` or :guilabel:`Lost Reason`." msgstr "" +":guilabel:`カスタムフィルタの追加`: このオプションをクリックし、ドロップダウンメニューの多数のオプションをスクロールすると、 " +":guilabel:`最終ステージ更新` や :guilabel:`失注理由` のような追加の検索条件が表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:497 msgid "" @@ -2583,64 +2642,75 @@ msgid "" "**Lost** (:guilabel:`false`). This shows at what stage leads are being " "marked **Won** or **Lost**." msgstr "" +":guilabel:`カスタムグループの追加--> 有効`: menuselection:`カスタムグループの追加 --> " +"有効`をクリックすると、結果が**成約**（:guilabel:`true`）または**失注**（:guilabel:`false`）に分けられます。これはリードがどの段階で**成約**または**失注**とマークされているかを示しています。" #: ../../content/applications/sales/crm/performance/win_loss.rst:500 msgid "" ":guilabel:`Multiple Groupings`: add multiple :guilabel:`Group By` selections" " to split results into more relevant and manageable chunks." msgstr "" +":guilabel:`複数グルーピング`: :guilabel:`グループ分け` 選択を複数追加して、結果をより適切で管理しやすいまとまりに分割します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:503 msgid "" "Adding :guilabel:`Salesperson` or :guilabel:`Sales Team` breaks up the total" " count of leads in each :guilabel:`Stage`." msgstr "" +"guilabel:`販売担当者` または :guilabel:`販売チーム` を追加すると、各 :guilabel:`ステージ` " +"のリードの合計数が分割されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:505 msgid "" "Adding :guilabel:`Medium` or :guilabel:`Source` can reveal what marketing " "avenues generate more sales." msgstr "" +"guilabel:`媒体`や:guilabel:`ソース`を追加することで、どのようなマーケティング手段がより多くの売上を生み出すかを明らかになります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "The Search menu open and the Won and Lost filters highlighted." -msgstr "" +msgstr "検索メニューが開き、成約と失注のフィルタが強調表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:514 msgid "" "By default, pivot view groups win/loss reports by :guilabel:`Stage` and " "measures :guilabel:`Expected Revenue`." msgstr "" +"デフォルトでは、ピボットビューは成約/失注レポートを :guilabel:`ステージ` でグループ化し、 :guilabel:`見込売上` " +"を測定します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:517 msgid "To flesh out the table:" -msgstr "" +msgstr "テーブルを肉付けするために:" #: ../../content/applications/sales/crm/performance/win_loss.rst:519 msgid "Click the :guilabel:`⬇️ (down arrow)` next to the search bar." -msgstr "" +msgstr "検索バーの横にある :guilabel:`⬇️ (下向き矢印)` をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:520 msgid "" "In the pop-up menu, replace the :guilabel:`Stage` grouping with something " "like :guilabel:`Salesperson` or :guilabel:`Medium`." msgstr "" +"ポップアップメニューの :guilabel:`ステージ` のグループ化を :guilabel:`販売担当者` や :guilabel:`媒体` " +"のように置換えます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:522 msgid "" "Click the :guilabel:`Measures` button and click :guilabel:`Count` to add the" " number of leads back into the report." -msgstr "" +msgstr "guilabel:`測定` ボタンをクリックし、:guilabel:`件数` をクリックしてリード数をレポートに追加します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:525 msgid "" "Other useful measures for pivot view include :guilabel:`Days to Assign` and " ":guilabel:`Days to Close`." msgstr "" +"ピボットビューに便利なその他の指標には、 :guilabel:`割当てまでの日数` や :guilabel:`クローズまでの日数` があります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "A win/loss report in Pivot View displays the data in table form." -msgstr "" +msgstr "ピボットビューの成約/失注レポートは、データを表形式で表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:533 msgid "" @@ -2649,10 +2719,12 @@ msgid "" "this, replace the :guilabel:`Stage` grouping in the search bar with another " "option." msgstr "" +"ピボットビューで、レポートに :guilabel:`重複グループ` が含まれているため、:guilabel:`スプレッドシートに挿入` " +"ボタンがグレーアウトすることがあります。これを修正するには、検索バーの :guilabel:`ステージ` グループ化を別のオプションに置換えて下さい。" #: ../../content/applications/sales/crm/performance/win_loss.rst:539 msgid "In list view, a win/loss report displays all leads on a single page." -msgstr "" +msgstr "リストビューでは、成約/失注レポートが全てのリードを1ページに表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:541 msgid "" @@ -2661,45 +2733,48 @@ msgid "" "ones. To re-order the nesting, remove all :guilabel:`Group By` options and " "re-add them in the desired order." msgstr "" +"リストをより整理するには、検索バーの横にある :guilabel:`⬇️ (下向き矢印)` " +"をクリックし、関連するグループ分けを追加するか、既存のグループ分けを再編成して下さい。ネストの順番を入替えるには、全ての " +":guilabel:`グループ分` オプションを削除して、希望の順番で追加し直して下さい。" #: ../../content/applications/sales/crm/performance/win_loss.rst:545 msgid "To add more columns to the list:" -msgstr "" +msgstr "リストに列を追加するには:" #: ../../content/applications/sales/crm/performance/win_loss.rst:547 msgid "Click the :guilabel:`Filters` icon in the top-right of the page." -msgstr "" +msgstr "ページ右上の :guilabel:`フィルタ` アイコンをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:548 msgid "" "Select options from the resulting drop-down menu. Some useful filters " "include:" -msgstr "" +msgstr "ドロップダウンメニューからオプションを選択します。便利なフィルタには次のようなものがあります:" #: ../../content/applications/sales/crm/performance/win_loss.rst:550 msgid "**Campaign**: Shows the marketing campaign that originated each lead." -msgstr "" +msgstr "**キャンペーン**: 各リードを発生させたマーケティングキャンペーンを表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:551 msgid "" "**Medium**: Shows the marketing medium (Banner, Direct, Email, Google " "Adwords, Phone, Website, etc.) that originated each lead." -msgstr "" +msgstr "**媒体**: マーケティング媒体(バナー、ダイレクト、Eメール、Googleアドワーズ、電話、ウェブサイトなど)を表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:553 msgid "" "**Source**: Shows the source of each lead (Newsletter, Lead Recall, Search " "Engine, etc.)." -msgstr "" +msgstr "**ソース**： 各リードのソース(ニュースレター、リードリコール、サーチエンジンなど)を表示します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "A win/loss report in List View displays all leads in an easy-to-read list." -msgstr "" +msgstr "リストビューの成約/失注レポートでは、全てのリードが見やすいリストで表示されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:562 msgid "Save and share reports" -msgstr "" +msgstr "レポートの保存と共有" #: ../../content/applications/sales/crm/performance/win_loss.rst:564 msgid "" @@ -2708,114 +2783,122 @@ msgid "" "Saved searches automatically update their results every time the report is " "opened." msgstr "" +"ref:`レポート<win_loss/reports>を作成`した後、検索条件を保存することができるので、将来レポートを再度作成する必要がありません。保存された検索結果は、レポートを開くたびに自動的に更新されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:568 msgid "" "Additionally, reports can be shared with others, or added to " "spreadsheets/dashboards for greater customization and easier access." msgstr "" +"さらに、レポートを他の人と共有したり、スプレッドシートやダッシュボードに追加して、よりカスタマイズしやすくしたり、アクセスしやすくしたりすることもできます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:573 msgid "Save to Favorites" -msgstr "" +msgstr "お気に入りに保存" #: ../../content/applications/sales/crm/performance/win_loss.rst:575 msgid "To save a report for later:" -msgstr "" +msgstr "レポートを後のために保存するには:" #: ../../content/applications/sales/crm/performance/win_loss.rst:577 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " "arrow)` icon, next to the search bar." -msgstr "" +msgstr "guilabel:`パイプライン分析`ページで、検索バーの隣にある :guilabel:`⬇️ (下矢印)` アイコンをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:579 msgid "" "In the drop-down menu that appears, under the :guilabel:`Favorites` heading," " click :guilabel:`Save current search`." msgstr "" +"表示されたドロップダウンメニューの :guilabel:`お気に入り` の下にある :guilabel:`現在の検索を保存` をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:581 msgid "In the next drop-down menu that appears, enter a name for the report." -msgstr "" +msgstr "次に表示されるドロップダウンメニューで、レポートの名前を入力します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:583 msgid "" "Checking the :guilabel:`Default filter` box sets this report as the default " "analysis when the :guilabel:`Pipeline Analysis` page is accessed." msgstr "" +"guilabel:`デフォルトフィルタ` ボックスをチェックすると、 :guilabel:`パイプライン分析` " +"ページにアクセスしたときに、このレポートがデフォルトの分析として設定されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:585 msgid "" "Checking the :guilabel:`Shared` box makes this report available to other " "users." -msgstr "" +msgstr "guilabel:`共有済`ボックスをチェックすると、このレポートを他のユーザが利用できるようになります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:587 msgid "" "Finally, click :guilabel:`Save`. The report is now saved under the " ":guilabel:`Favorites` heading." -msgstr "" +msgstr "最後に :guilabel:`保存` をクリックします。これでレポートは :guilabel:`お気に入り` の見出しの下に保存されます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "Under the Favorites heading, click Save current search and save the report " "for later." -msgstr "" +msgstr "お気に入り見出の下にある”現在の検索を保存”をクリックし、後で使用するためにレポートを保存します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:594 msgid "Add to a Spreadsheet" -msgstr "" +msgstr "スプレッドシートに追加" #: ../../content/applications/sales/crm/performance/win_loss.rst:596 msgid "" "Inserting a report into a spreadsheet not only saves a copy of the report, " "it allows users to add charts and formulas like in an Excel file." msgstr "" +"スプレッドシートにレポートを挿入すると、レポートのコピーが保存されるだけでなく、Excelファイルのようにグラフや数式を追加することができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:599 msgid "To save a report as a spreadsheet:" -msgstr "" +msgstr "レポートをスプレッドシートとして保存するには" #: ../../content/applications/sales/crm/performance/win_loss.rst:601 msgid "**In Graph or Pivot View**:" -msgstr "" +msgstr "**グラフまたはピボットビュー**:" #: ../../content/applications/sales/crm/performance/win_loss.rst:603 msgid "Click the :guilabel:`Insert in spreadsheet` button." -msgstr "" +msgstr "guilabel:`スプレッドシートに挿入`ボタンをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:604 msgid "In the pop-up menu that appears, click :guilabel:`Confirm`." -msgstr "" +msgstr "表示されるポップアップメニューで、 :guilabel:`確認` をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:606 msgid "**In Cohort or List View**:" -msgstr "" +msgstr "**コホートまたはリストビュー**:" #: ../../content/applications/sales/crm/performance/win_loss.rst:608 msgid "Click the :guilabel:`⚙️ (gear)` icon." -msgstr "" +msgstr "guilabel:`⚙️（歯車）`アイコンをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:609 msgid "" "In the drop-down menu that appears, hover over :guilabel:`Spreadsheet`." -msgstr "" +msgstr "表示されるドロップダウンメニューで、:guilabel:`スプレッドシート`にカーソルを合わせます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:610 msgid "" "In the next drop-down menu, click either :guilabel:`Insert in spreadsheet` " "or :guilabel:`Link in spreadsheet`." msgstr "" +"次のドロップダウンメニューで、 :guilabel:`スプレッドシートに挿入` または :guilabel:`スプレッドシートにリンク` " +"のいずれかをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:613 msgid "Saved reports are viewable in the *Documents* app." -msgstr "" +msgstr "保存されたレポートは*ドキュメント*アプリで閲覧可能です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "Pivot View reports especially benefit from being inserted in spreadsheets." -msgstr "" +msgstr "ピボットビューレポートは、スプレッドシートに挿入することで特に便利です。" #: ../../content/applications/sales/crm/performance/win_loss.rst:620 msgid "" @@ -2824,85 +2907,90 @@ msgid "" "spreadsheet can be added to a public dashboard instead of only :guilabel:`My" " Dashboard`." msgstr "" +"スプレッドシートを変更して数式を追加した後、スプレッドシート全体をダッシュボードに追加することを検討しましょう。この方法を使用すると、スプレッドシートを" +" :guilabel:`自分のダッシュボード` だけでなく、公開ダッシュボードに追加することができます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:624 msgid "Click :menuselection:`File --> Add to dashboard`." -msgstr "" +msgstr "menuselection:`ファイル --> ダッシュボードに追加`をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:625 msgid "" "In the pop-up menu that appears, name the spreadsheet and select a " ":guilabel:`Dashboard Section` to house the report." msgstr "" +"表示されるポップアップメニューで、スプレッドシートに名前を付け、レポートを格納する :guilabel:`ダッシュボードセクション` を選択します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:627 msgid "Click :guilabel:`Create`." -msgstr "" +msgstr " :guilabel:`作成`をクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:629 msgid "Add to a Dashboard" -msgstr "" +msgstr "ダッシュボードに追加" #: ../../content/applications/sales/crm/performance/win_loss.rst:631 msgid "" "Adding a report to a dashboard saves it for later and makes it easy to view " "alongside the rest of :guilabel:`My Dashboard`." msgstr "" +"ダッシュボードにレポートを追加すると、後でそれを保存し、 :guilabel:`マイダッシュボード`の他の部分と一緒に簡単に表示できるようになります。" #: ../../content/applications/sales/crm/performance/win_loss.rst:634 msgid "To add a report to :guilabel:`My dashboard`:" -msgstr "" +msgstr "guilabel:`マイダッシュボード`にレポートを追加します:" #: ../../content/applications/sales/crm/performance/win_loss.rst:636 msgid "" "On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⚙️ (gear)` " "icon." -msgstr "" +msgstr "guilabel:`パイプライン分析`ページで、 :guilabel:`⚙️（歯車）`アイコンをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:637 msgid "In the drop-down menu that appears, hover over :guilabel:`Dashboard`." -msgstr "" +msgstr "表示されたドロップダウンメニューで :guilabel:`ダッシュボード` にカーソルを合わせます。" #: ../../content/applications/sales/crm/performance/win_loss.rst:638 msgid "" "In the :guilabel:`Add to my dashboard` drop-down menu, enter a name for the " "report (by default, it is named :guilabel:`Pipeline`)." msgstr "" +"guilabel:`ダッシュボードに追加`ドロップダウンメニューで、レポートの名前を入力します(デフォルトでは、:guilabel:`パイプライン`という名前になっています)。" #: ../../content/applications/sales/crm/performance/win_loss.rst:642 msgid "To view a saved report:" -msgstr "" +msgstr "保存済レポートを見るには:" #: ../../content/applications/sales/crm/performance/win_loss.rst:644 msgid "" "Return to the main apps page, and navigate to :menuselection:`Dashboards app" " --> My Dashboard`." -msgstr "" +msgstr "メインアプリページに戻り、 :menuselection:`ダッシュボードアプリ --> 自分のダッシュボード` に移動します。" #: ../../content/applications/sales/crm/performance/win_loss.rst:0 msgid "" "To access the saved report, open the Dashboard app and click My Dashboard." -msgstr "" +msgstr "保存されたレポートにアクセスするには、ダッシュボードアプリを開き、毎ダッシュボードをクリックします。" #: ../../content/applications/sales/crm/performance/win_loss.rst:652 msgid ":doc:`../acquire_leads/convert`" -msgstr "" +msgstr ":doc:`../acquire_leads/convert`" #: ../../content/applications/sales/crm/performance/win_loss.rst:653 msgid ":doc:`../acquire_leads/send_quotes`" -msgstr "" +msgstr ":doc:`../acquire_leads/send_quotes`" #: ../../content/applications/sales/crm/performance/win_loss.rst:654 msgid ":doc:`../pipeline/lost_opportunities`" -msgstr "" +msgstr ":doc:`../pipeline/lost_opportunities`" #: ../../content/applications/sales/crm/pipeline.rst:5 msgid "Organize the pipeline" -msgstr "" +msgstr "パイプラインを整理" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:3 msgid "Manage lost opportunities" -msgstr "" +msgstr "失注案件を管理" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 msgid "" @@ -2911,10 +2999,11 @@ msgid "" "the reason why an opportunity was lost provides additional insight that can " "prove useful for future opportunities." msgstr "" +"全ての案件がセールスにつながるわけではありません。パイプラインを最新の状態に保つためには、失注案件を特定する必要があります。案件の失注理由を特定することで、将来の案件に役立つ追加的な洞察が得られます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 msgid "Mark a lead as lost" -msgstr "" +msgstr "リードを失注としてマーク" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 msgid "" @@ -2922,17 +3011,18 @@ msgid "" "select a lead from the pipeline, by clicking on its corresponding kanban " "card. Doing so reveals that lead's detail form." msgstr "" +"リードを失注とマークするには、:menuselection:`CRM`アプリケーションを開き、パイプラインからリードを選択し、対応するかんばんカードをクリックします。そうすると、そのリードの詳細フォームが表示されます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 msgid "" "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." -msgstr "" +msgstr "次に、リードの詳細フォームの上部にある :guilabel:`失注` をクリックします。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "" "Buttons from the top of an opportunity record with the lost button " "emphasized." -msgstr "" +msgstr "失注ボタンが強調された案件レコードの上部からのボタン。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 msgid "" @@ -2941,22 +3031,25 @@ msgid "" " by entering it into the :guilabel:`Lost Reason` field, and clicking " ":guilabel:`Create`." msgstr "" +"これで :guilabel:`失注理由` ポップアップが開きます。ドロップダウンから既存の失注理由を選択します。該当する理由がない場合は、 " +":guilabel:`失注理由` フィールドに入力し、 :guilabel:`作成` をクリックして新しい理由を作成します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 msgid "" "Additional notes and comments can be added below the lost reason designated " "in the :guilabel:`Lost Reason` field." -msgstr "" +msgstr "guilabel:`失注理由`フィールドで指定された失注理由の下に、追加のメモやコメントを追加することができます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 msgid "" "When all the desired information has been entered in the :guilabel:`Lost " "Reason` pop-up window, click :guilabel:`Submit`." msgstr "" +"全ての必要な情報が :guilabel:`失注理由` ポップアップウィンドウに入力されたら、 :guilabel:`送信` をクリックします。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Lost reasons popup with sample reasons." -msgstr "" +msgstr "失注理由のポップアップに理由のサンプルが表示されます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 msgid "" @@ -2964,16 +3057,19 @@ msgid "" "returns to the lead detail form, where a new red :guilabel:`Lost` banner is " "now present in the upper-right corner of the lead." msgstr "" +"guilabel:`送信`をクリックすると、ポップアップウィンドウは消え、Odooはリードの詳細フォームに戻ります。そこでは新しい赤い:guilabel:`失注`バナーがリードの右上隅に表示されるようになりました。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 msgid "Create/edit lost reasons" -msgstr "" +msgstr "失注理由の作成/編集" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 msgid "" "To create a new lost reason, or edit an existing one, navigate to " ":menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" +"新しい失注理由を作成、または既存の失注理由を編集するには、 :menuselection:`CRM アプリ --> 設定 --> " +"失注理由`に移動します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 msgid "" @@ -2983,6 +3079,9 @@ msgid "" ":guilabel:`Description` field. When done, click :guilabel:`Save` in the " "upper-left corner." msgstr "" +"既存の理由を編集するには、修正する理由をクリックして下さい。クリックするとその理由がハイライトされます。ハイライトされたら、 " +":guilabel:`説明` フィールドを編集して、選択した失注理由の説明を変更します。編集が終わったら、左上の :guilabel:`Save` " +"をクリックします。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 msgid "" @@ -2991,10 +3090,13 @@ msgid "" "line in the :guilabel:`Description` field. Then, proceed to type in the new " "lost reason in that new line. Once ready, click :guilabel:`Save`." msgstr "" +"新しい失注理由を作成するには、 :guilabel:`失注理由` ページの左上にある :guilabel:`作成` をクリックします。そうすると " +":guilabel:`説明` フィールドに新しい空白行が現れます。そして、その新しい行に新しい失注理由を入力して下さい。準備ができたら " +":guilabel:`保存` をクリックします。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 msgid "Retrieve lost opportunities" -msgstr "" +msgstr "失注案件を取戻す" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 msgid "" @@ -3002,10 +3104,12 @@ msgid "" "app` to the main :guilabel:`Pipeline` dashboard. Then, click the " ":guilabel:`Filters` drop-down menu, located beneath the search bar." msgstr "" +"Odoo *CRM*で失注案件を取戻すには、 :menuselection:`CRMアプリ` を開き、メインの :guilabel:`パイプライン` " +"ダッシュボードに移動します。次に、検索バーの下にある :guilabel:`Filters` ドロップダウンメニューをクリックします。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Search bar with lost filter emphasized." -msgstr "" +msgstr "失注フィルタが強調された検索バー。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 msgid "" @@ -3013,6 +3117,9 @@ msgid "" "option. Upon selecting :guilabel:`Lost`, only the leads that have been " "marked as `Lost` appear on the :guilabel:`Pipeline` page." msgstr "" +"guilabel:`フィルタ` ドロップダウンメニューから :guilabel:`失注` " +"オプションを選択します。guilabel:`失注`を選択すると、`失注`とマークされたリードだけが :guilabel:`パイプライン` " +"ページに表示されます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 msgid "" @@ -3020,6 +3127,8 @@ msgid "" "--> Add Custom Filter`. Doing so reveals another drop-down menu with three " "fields." msgstr "" +"特定の失注理由でリードをフィルタするには、 :menuselection:`フィルタ --> カスタムフィルタの追加` " +"を選択します。すると、3つのフィールドを持つ別のドロップダウンメニューが表示されます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 msgid "" @@ -3030,14 +3139,18 @@ msgid "" ":guilabel:`Apply`, Odoo reveals all the lost leads with a reason that " "contains that specified keyword(s)." msgstr "" +"一番上のドロップダウンメニューで :guilabel:`失注理由` " +"を選択します。2番目のフィールドのドロップダウンメニューで、:guilabel:`含む`を選択する。次に、:guilabel:`カスタムフィールドを追加`サブメニューの3番目のフィールドに、特定のキーワードを入力します。最後に" +" :guilabel:`適用` " +"をクリックします。guilabel:`適用`をクリックすると、Odooは指定したキーワードを含む理由を持つ失注リードを全て表示します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Search bar with custom filter added for lost reason." -msgstr "" +msgstr "失注理由に追加されたカスタムフィルタつきの検索バー。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 msgid "Restore lost opportunities" -msgstr "" +msgstr "失注案件を復元する" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 msgid "" @@ -3046,12 +3159,15 @@ msgid "" " select the :guilabel:`Lost` option. Doing so reveals all the lost " "opportunities on the :guilabel:`Pipeline` page." msgstr "" +"失注案件を復元するには、*CRM*アプリのメイン :guilabel:`パイプライン` ダッシュボードに移動し、 :guilabel:`フィルタ` " +"ドロップダウンメニューを開き、 :guilabel:`失注` オプションを選択します。そうすると、 :guilabel:`パイプライン` " +"ページにあるすべての失注案件が表示されます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 msgid "" "Then, click on the kanban card of the desired lost opportunity to restore, " "which opens that lead's detail form." -msgstr "" +msgstr "次に、復元したい失注案件のかんばんカードをクリックすると、そのリードの詳細フォームが開きます。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 msgid "" @@ -3059,14 +3175,16 @@ msgid "" "left corner. Doing so removes the red :guilabel:`Lost` banner from the lead " "form, signifying the lead has been restored." msgstr "" +"失注リードの詳細フォームから、左上の :guilabel:`復元` をクリックします。そうすることで、リードフォームから赤い " +":guilabel:`失注` バナーが消え、リードが復元されたことを示します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Lost opportunity with emphasis on the Restore button." -msgstr "" +msgstr "復元ボタンを強調した失注案件" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 msgid "Restore multiple opportunities at once" -msgstr "" +msgstr "一度に複数の案件を復元する" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 msgid "" @@ -3074,6 +3192,8 @@ msgid "" ":guilabel:`Pipeline` dashboard in the *CRM* app, open the " ":guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." msgstr "" +"複数の案件を一度に復元するには、*CRM*アプリのメイン :guilabel:`パイプライン` ダッシュボードに移動し、 " +":guilabel:`フィルタ` ドロップダウンメニューを開き、 :guilabel:`失注` オプションを選択します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 msgid "" @@ -3083,6 +3203,8 @@ msgid "" " chosen, select the checkbox to the left of each desired opportunity/lead to" " be restored." msgstr "" +"これは、右上隅にある三本線の :guilabel:`☰(リスト)` アイコンで表されています。そうすることで、 :guilabel:`パイプライン` " +"ページにある全てのリードがリスト形式で表示されます。リストフォームを選択した状態で、復元したい各案件/リードの左側にあるチェックボックスを選択します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 msgid "" @@ -3091,6 +3213,9 @@ msgid "" ":guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down " "menu, select :guilabel:`Unarchive`." msgstr "" +"希望する案件/リードが選択されたら、 :guilabel:`パイプライン`ページの上部にある :guilabel:`⚙️ アクション(歯車)` " +"ドロップダウンメニューをクリックします。guilabel:`⚙️ アクション (歯車)` ドロップダウンメニューから " +":guilabel:`アーカイブ解除` を選択します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 msgid "" @@ -3099,34 +3224,38 @@ msgid "" "criteria. To reveal these newly-restored leads, delete the `Lost` filter " "from the search bar." msgstr "" +"そうすることで、選択された失注案件が、もはや `失注` フィルタの条件に当てはまらないため、 :guilabel:`パイプライン` " +"ページから削除されます。新たに復元されたリードを表示するには、検索バーから `失注` フィルタを削除します。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 msgid "Action button from list view with the Unarchive option emphasized." -msgstr "" +msgstr "アーカイブ解除オプションが強調されたリストビューのアクションボタン。" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 msgid ":doc:`../performance/win_loss`" -msgstr "" +msgstr ":doc:`../performance/win_loss`" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 msgid "Multiple sales teams" -msgstr "" +msgstr "複数の販売チーム" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 msgid "" "Use the *Sales Teams* feature to manage several sales teams, departments, or" " channels, each with their own unique sales processes." -msgstr "" +msgstr "複数の販売チーム、部門、チャネルを管理するには、それぞれ独自の販売プロセスを持つ*販売チーム*機能を使用します。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 msgid "Create a new sales team" -msgstr "" +msgstr "新しい販売チームの作成" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 msgid "" "To create a new sales team, go to :menuselection:`CRM --> Configuration --> " "Sales Teams`, then click :guilabel:`Create`." msgstr "" +"新しい販売チームを作成するには、 :menuselection:`CRM --> 設定 --> 販売チーム` に進み、 :guilabel:`作成` " +"をクリックします。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 msgid "" @@ -3136,6 +3265,9 @@ msgid "" ":guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or " ":guilabel:`Followers Only`." msgstr "" +"作成ページで、 :guilabel:`Eメールエイリアス` " +"を設定し、その一意のメールアドレスにメッセージが送信されるたびに、この販売チームのリード/案件を自動的に生成します。guilabel:`全員`、:guilabel:`認証済取引先`、" +" :guilabel:`フォロワのみ`のいずれからのメールを受付けるかを選択します。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 msgid "" @@ -3144,14 +3276,15 @@ msgid "" "this sales team based on specific filters, such as country, language, or " "campaign." msgstr "" +"guilabel:`請求書発行目標`を設定することで、このチームに特定の月次収益目標を設定することができます。guilabel:`ドメイン`を設定して、国、言語、キャンペーンなどの特定のフィルタに基づいてリード/案件をこの営業チームに割当てます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 msgid "Create a sales team in Odoo CRM." -msgstr "" +msgstr "OdooCRMで販売チームを作成する" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 msgid "Add members to a sales team" -msgstr "" +msgstr "販売チームにメンバを追加する" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 msgid "" @@ -3161,10 +3294,12 @@ msgid "" " that can be assigned to this salesperson in a 30-day period to ensure that " "they do not overwork." msgstr "" +"チームメンバを追加するには、販売チームの設定ページを編集する際に :guilabel:`メンバ` タブの下にある :guilabel:`追加` " +"をクリックします。ドロップダウンメニューから販売担当者を選択するか、新規販売担当者を作成します。販売担当者の超過労働を防ぐために、30日間にこの販売担当者に割当てられるリードの最大数を設定します。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 msgid "Add a salesperson in Odoo CRM." -msgstr "" +msgstr "OdooCRMに販売担当者を追加する" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 msgid "" @@ -3172,10 +3307,12 @@ msgid "" "multiple sales teams, allowing them to access all of the pipelines that they" " need to." msgstr "" +"1人の担当者をチームメンバまたは :guilabel:`チームリーダー` " +"として複数の販売チームに追加し、必要なパイプライン全てにアクセスできるようにすることができます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 msgid "Sales team dashboard" -msgstr "" +msgstr "販売チームダッシュボード" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 msgid "" @@ -3183,17 +3320,19 @@ msgid "" "Teams`. Odoo users will see any teams that they are a part of as dashboard " "tiles." msgstr "" +"販売チームダッシュボードを表示するには、 :menuselection:`CRM --> 販売 --> " +"チーム`にアクセスして下さい。Odooユーザは自分が所属しているチームがダッシュボードのタイルとして表示されます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 msgid "" "Each tile gives an overview of the sales team's open opportunities, " "quotations, sales orders, and expected revenue, as well as a bar graph of " "new opportunities per week and an invoicing progress bar." -msgstr "" +msgstr "各タイルには、販売チームのオープン案件、見積、販売オーダ、見込売上の概要、週ごとの新規案件の棒グラフ、請求書の進捗バーが表示されます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 msgid "Sales team overview dashboard in Odoo CRM." -msgstr "" +msgstr "OdooCRMでの販売チーム概要ダッシュボード" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 msgid "" @@ -3202,26 +3341,27 @@ msgid "" "opportunities, pick a color for this team, or access the team's " "configuration page." msgstr "" +"タイルの隅にある3つの点をクリックすると、ナビゲーションメニューが表示され、ドキュメントやレポートをすばやく表示したり、新しい見積や案件を作成したり、このチームの色を選んだり、チームの設定ページにアクセスしたりすることができます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 msgid "" "Click the Three Dot Menu in Odoo CRM dashboard to view documents and create " "opportunities." -msgstr "" +msgstr "Odoo CRMダッシュボードの3ドットメニューをクリックすると、ドキュメントを閲覧したり、案件を作成することができます。" #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 msgid "" "Click on the :guilabel:`Pipeline` button to go directly to that team's CRM " "pipeline." -msgstr "" +msgstr "guilabel:`パイプライン`ボタンをクリックすると、そのチームのCRMパイプラインに直接移動します。" #: ../../content/applications/sales/crm/track_leads.rst:5 msgid "Assign and track leads" -msgstr "" +msgstr "リードの割当と追跡" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 msgid "Assign leads with predictive lead scoring" -msgstr "" +msgstr "予測リードスコアリングによるリードの割当" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 msgid "" @@ -3231,22 +3371,24 @@ msgid "" "are more likely to result in successful deals by quickly assigning them to " "the appropriate salespeople." msgstr "" +"Odoo " +"*CRM*アプリはリード/案件を自動的に販売チームや販売担当者に割当ることができます。標準的なプラクティスは、各リードの成約確度に基づいてリードを割当ることです。企業は適切な販売担当者にリードを迅速に割当ることで、取引成功の可能性が高いリードに優先順位をつけることができます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 msgid "" "Odoo automatically calculates the probability of winning each lead using a " "method called *predictive lead scoring*." -msgstr "" +msgstr "Odooは*予測リードスコアリング*と呼ばれる方法で、各リードが獲得できる確度を自動的に計算します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 msgid "Predictive lead scoring" -msgstr "" +msgstr "予測リードスコアリング" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16 msgid "" "Predictive lead scoring is a machine-learning model that uses historical " "data from Odoo *CRM* to score open leads/opportunities." -msgstr "" +msgstr "リードスコアリングは、Odoo *CRM*の履歴データを使用して、オープンリード/案件をスコアリングする機械学習モデルです。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 msgid "" @@ -3255,18 +3397,19 @@ msgid "" "this data to predict the probability of winning each new lead or " "opportunity." msgstr "" +"企業がCRMパイプラインを通して案件を処理する際、Odooは案件の成約と失注に関するデータを収集します。予測リードスコアリングはこのデータを使って、各新規リードや案件の成約確度を予測します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 msgid "" "The more opportunities that are sent through the CRM pipeline, the more data" " Odoo collects, resulting in more accurate probabilities." -msgstr "" +msgstr "CRMパイプラインに送られる案件が多ければ多いほど、Odooはより多くのデータを収集し、より正確な確率を得ることができます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 msgid "" "Specifically, Odoo's predictive lead scoring uses the *naive Bayes* " "probability model:" -msgstr "" +msgstr "具体的には、Odooの予測リードスコアリングは*単純ベイズ*確度モデルを使用しています:" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:28 msgid "" @@ -3275,30 +3418,34 @@ msgid "" "\\end{equation}\n" "\n" msgstr "" +"\\begin{equation}\n" +"P(A | B) = \\frac{P(A) \\times P(B | A)}{P(B)}\n" +"\\end{equation}\n" +"\n" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 msgid "" "The probability of success of each opportunity is displayed on the " "opportunity form, and it updates automatically as the opportunity progresses" " through the CRM pipeline." -msgstr "" +msgstr "各案件の成約確度は、案件フォームに表示され、案件がCRMパイプラインを進むにつれて自動的に更新されます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "The probability of success displayed on the opportunity form." -msgstr "" +msgstr "案件フォームに表示される成約確度。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 msgid "" "When an opportunity moves to the next stage, its probability of success " "automatically increases according to the predictive lead scoring algorithm." -msgstr "" +msgstr "案件が次のステージに進むと、その成約確度は予測リードスコアリングアルゴリズムに従って自動的に上昇します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 msgid "" "Predictive lead scoring is always active in Odoo *CRM*. However, the " "variables used to calculate the probability of success can be customized in " "the settings." -msgstr "" +msgstr "リードスコアリングはOdoo *CRM*で常に有効です。ただし、成約確度の計算に使用する変数は設定でカスタマイズすることができます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 msgid "" @@ -3307,59 +3454,61 @@ msgid "" ":guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update " "Probabilities` button." msgstr "" +"予測リードスコアリングで使用する変数をカスタマイズするには、 :menuselection:`CRM --> 設定 --> " +"管理設定`に進みます。guilabel:`予測リードスコアリング`の下にある、:guilabel:`確立を更新`ボタンをクリックします。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 msgid "" "Then, click on the drop-down menu to choose which variables the predictive " "lead scoring feature will take into account." -msgstr "" +msgstr "次に、ドロップダウンメニューをクリックして、予測リードスコアリング機能が考慮する変数を選択します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "" "The Update Probabilities window in the Predictive Lead Scoring settings." -msgstr "" +msgstr "予測リードスコアリング設定の更新確率ウィンドー。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 msgid "Any number of the following variables can be activated:" -msgstr "" +msgstr "以下の変数はいくつでも有効にできます:" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 msgid "" ":guilabel:`State`: the geographical state from which the opportunity " "originates" -msgstr "" +msgstr ":guilabel:`州・都道府県`: 案件が発生した地理的な州・都道府県。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 msgid "" ":guilabel:`Country`: the geographical country from which the opportunity " "originates" -msgstr "" +msgstr ":guilabel:`国`: 案件が発生した地理的な国。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 msgid "" ":guilabel:`Phone Quality`: whether or not a phone number is listed for the " "opportunity" -msgstr "" +msgstr ":guilabel:`電話品質`: 案件に電話番号が記載されているかどうか。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 msgid "" ":guilabel:`Email Quality`: whether or not an email address is listed for the" " opportunity" -msgstr "" +msgstr ":guilabel:`Eメール品質`: 案件にEメールアドレスが記載されているかどうか。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 msgid "" ":guilabel:`Source`: the source of an opportunity (e.g. search engine, social" " media)" -msgstr "" +msgstr ":guilabel:`ソース`: 案件の発生源(検索エンジンやソーシャルメディアなど)。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 msgid ":guilabel:`Language`: the spoken language specified on the opportunity" -msgstr "" +msgstr ":guilabel:`言語`: 案件で指定された対話言語" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 msgid ":guilabel:`Tags`: the tags placed on the opportunity" -msgstr "" +msgstr ":guilabel:`タグ`: 案件に付けられたタグ" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 msgid "" @@ -3369,6 +3518,8 @@ msgid "" "takes into account these two variables, regardless of which optional " "variables are selected." msgstr "" +"変数 `ステージ` と `チーム` は常に有効です。 `Stage` は、案件が CRM " +"のパイプラインステージにあることを意味します。`チーム`は、案件に割当てられた販売チームを意味します。予測リードスコアリングは、どのオプション変数が選択されているかに関わらず、常にこの2つの変数を考慮します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 msgid "" @@ -3376,20 +3527,22 @@ msgid "" "created as of the:` to select the date from which predictive lead scoring " "will begin its calculations." msgstr "" +"次に、オプション " +":guilabel:`以下の時点で作成されたリードを考慮する:`の隣にある日付フィールドをクリックし、予測リードスコアリングの計算を開始する日付を選択します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 msgid "Lastly, click :guilabel:`Confirm` to save changes." -msgstr "" +msgstr "最後に :guilabel:`確認` をクリックして変更を保存します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 msgid "Change the probability manually" -msgstr "" +msgstr "手動で確度を変更します" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 msgid "" "An opportunity's probability of success can be changed manually on the " "opportunity form. Click on the probability number to edit it." -msgstr "" +msgstr "案件の成功確度は、案件フォームで手動で変更できます。確度の数字をクリックして編集します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 msgid "" @@ -3397,22 +3550,23 @@ msgid "" "for that opportunity. The probability will no longer update automatically as" " the opportunity moves through each stage of the pipeline." msgstr "" +"確度を手動で変更すると、その案件に対する確度の自動更新が削除されます。案件がパイプラインの各ステージに移動すると、確度は自動的に更新されなくなります。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 msgid "" "To reactivate automatic probability, click on the gear icon next to the " "probability percentage." -msgstr "" +msgstr "自動確度を再び有効にするには、確率のパーセンテージの隣にある歯車のアイコンをクリックします。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "" "The gear icon used to reactivate automatic probability on an opportunity " "form." -msgstr "" +msgstr "歯車のアイコンは、案件フォームの自動確度を再有効化するために使用されます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 msgid "Assign leads based on probability" -msgstr "" +msgstr "確度に基づいてリードを割当てる" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 msgid "" @@ -3421,16 +3575,20 @@ msgid "" "probability of success to prioritize those that are more likely to result in" " deals." msgstr "" +"Odoo " +"*CRM*は、指定された規則に基づいてリード/案件を販売チームや販売担当者に割当てることができます。リードの成功確度に基づいて割当て規則を作成し、成約につながる可能性の高いリードを優先的に割当てることができます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 msgid "Configure rule-based assignment" -msgstr "" +msgstr "規則ベースの割当てを設定します" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 msgid "" "To activate *rule-based assignment*, navigate to :menuselection:`CRM --> " "Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." msgstr "" +"*ルールに基づいた割当*を有効にするには、 :menuselection:`CRM --> 設定 --> 管理設定`に移動し、 " +":guilabel:`ルールに基づいた割当`を有効にします。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 msgid "" @@ -3439,6 +3597,8 @@ msgid "" ":guilabel:`Repeatedly`, meaning Odoo will automatically trigger the " "assignment according to the chosen time period." msgstr "" +"ルールに基づいた割当機能は :guilabel:`手動`(Odooユーザが手動で割当を開始)、または " +":guilabel:`繰返し`(選択した期間に従って自動的に割当を開始)に設定できます。つまり、Odooは選択した期間に従って自動的に割当てを開始します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 msgid "" @@ -3446,10 +3606,12 @@ msgid "" ":guilabel:`Running` section. Then, customize how often Odoo will trigger the" " automatic assignment in the :guilabel:`Repeat every` section." msgstr "" +"リードの自動割当てを設定するには、:guilabel:`実行中`セクションで:guilabel:`繰返し`を選択します。次に " +":guilabel:`以下ごとに繰返` セクションで、Odooが自動割当てをトリガする頻度をカスタマイズします。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 msgid "The Rule-Based Assignment setting in CRM settings." -msgstr "" +msgstr "CRM設定のルールに基づいた割当て設定。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 msgid "" @@ -3458,10 +3620,13 @@ msgid "" "the :guilabel:`Rule-Based Assignment` settings (or using the " ":guilabel:`Assign Leads` button on the sales team configuration page)." msgstr "" +"ルールに基づいた割当てが :guilabel:`繰返し` 実行されるように設定されている場合でも、 :guilabel:`ルールに基づいた割当て` " +"設定にある円形の矢印アイコンを使って(または営業チーム設定ページの :guilabel:`リードの割当` " +"ボタンを使って)手動で割当をトリガすることができます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 msgid "Configure assignment rules" -msgstr "" +msgstr "割当てルールを設定する" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 msgid "" @@ -3470,6 +3635,8 @@ msgid "" " To get started, navigate to :menuselection:`CRM --> Configuration --> Sales" " Teams`, and select a sales team." msgstr "" +"次に、販売チームや販売担当者ごとに*割当ルール*を設定します。これらのルールはOdooがどのリードをどの担当者に割当るかを決定します。まずは " +":menuselection:`CRM --> 設定 --> 販売チーム` に移動し、販売チームを選択します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 msgid "" @@ -3479,6 +3646,8 @@ msgid "" "anything that may be relevant for this company or team, and any number of " "rules can be added." msgstr "" +"販売チーム設定フォームの :guilabel:`割当ルール` の下にある :guilabel:`ドメインの編集` " +"をクリックして、この営業チームのリード割当てを決定するためにOdooが使用するルールを設定します。ルールはこの会社やチームに関連するものであれば何でも設定でき、いくつでも追加できます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 msgid "" @@ -3486,6 +3655,8 @@ msgid "" "the :guilabel:`+` sign on the right of the assignment rule to add another " "line. Click on the :guilabel:`x` symbol to remove the line." msgstr "" +":guilabel:`フィルタを追加`をクリックして割当ルールの作成を開始します。割当ルールの右にある :guilabel:`+` " +"記号をクリックすると、もう一行追加されます。行を削除するには :guilabel:`x` 記号をクリックします。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 msgid "" @@ -3493,6 +3664,7 @@ msgid "" "success, click on the far left drop-down menu of an assignment rule line, " "and select :guilabel:`Probability`." msgstr "" +"案件の成功確率に基づいて割当ルールを作成するには、割当ルール行の左端のドロップダウンメニューをクリックし、:guilabel:`確度`を選択します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 msgid "" @@ -3500,12 +3672,13 @@ msgid "" "likely the symbol for *greater than*, *less than*, *greater than or equal " "to*, or *less than or equal to*." msgstr "" +"真ん中のドロップダウンメニューから、必要な方程式の記号を選択します。ほとんどの場合、*が次より大きい*、*が次より小さい*、*が次以上*、または*が次以下*の記号です。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 msgid "" "In the far right space, enter the desired number value of the probability. " "Finally, click :guilabel:`Save` to save changes." -msgstr "" +msgstr "右端のスペースに、希望する確度の数値を入力します。最後に :guilabel:`保存` をクリックして変更を保存します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 msgid "" @@ -3513,12 +3686,14 @@ msgid "" "have a probability of success of 20% or greater, create a :guilabel:`Domain`" " line that reads: `Probability >= 20`." msgstr "" +"販売チームが成約確度20%以上のリードを受け取るように割当ルールを設定するには、 :guilabel:`ドメイン`行を作成して下さい:`確度 >= " +"20`" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:0 msgid "" "Sales team domain set to probability greater than or equal to twenty " "percent." -msgstr "" +msgstr "販売チームのドメインは20％以上の確度に設定されています。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 msgid "" @@ -3527,6 +3702,8 @@ msgid "" "the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click" " :guilabel:`Save` to save changes." msgstr "" +"個々のチームメンバに対して個別の割当ルールを設定することもできます。販売チームの設定ページから、 :guilabel:`メンバ` " +"タブでチームメンバをクリックし、 :guilabel:`ドメイン` セクションを編集します。guilabel:`保存`をクリックして変更を保存します。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 msgid "" @@ -3537,6 +3714,8 @@ msgid "" "feature. If :guilabel:`Skip auto assignment` is activated, the sales team or" " salesperson can still be assigned leads manually." msgstr "" +"設定でリードの自動割当が設定されている場合、販売チームと個々のチームメンバの両方に :guilabel:`自動割当をスキップする` " +"オプションがあります。このボックスにチェックを入れると、Odooのルールベースの割当機能により、特定の販売チームまたは販売担当者にリードが自動割当されなくなります。guilabel:`自動割当をスキップ`が有効になっている場合でも、販売チームまたは販売担当者は手動でリードを割当られます。" #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 msgid "" @@ -3545,46 +3724,49 @@ msgid "" "assign any leads that are currently unassigned and match this team's " "specified domain." msgstr "" +"この販売チームに手動でリードを割当るには、販売チーム設定ページの上部にある :guilabel:`リードを割当` " +"ボタンをクリックして下さい。これにより、現在未割当で、このチームの指定ドメインに一致するリードが割当られます。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:3 msgid "Track your prospects visits" -msgstr "" +msgstr "見込客の訪問を追跡" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5 msgid "" "Tracking your website pages will give you much more information about the " "interests of your website visitors." -msgstr "" +msgstr "ウェブサイトページを追跡することで、ウェブサイト訪問者の興味についてより多くの情報を得ることができます。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8 msgid "" "Every tracked page they visit will be recorded on your lead/opportunity if " "they use the contact form on your website." -msgstr "" +msgstr "もし彼らがウェブサイトのコンタクトフォームを使用した場合、彼らが訪問した全てのトラッキングされたページが、リード/案件に記録されます。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14 msgid "" "To use this feature, install the free module *Lead Scoring* under your " "*Apps* page (only available in Odoo Enterprise)." msgstr "" +"この機能を使用するには、*アプリ*ページの下に無料のモジュール*リードスコアリング*をインストールして下さい(Odoo企業版でのみ使用可能)。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21 msgid "Track a webpage" -msgstr "" +msgstr "ウェブページを追跡" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23 msgid "" "Go to any static page you want to track on your website and under the " "*Promote* tab you will find *Optimize SEO*" -msgstr "" +msgstr "ウェブサイト上の追跡したい静的ページにアクセスすると、*プロモート*タブの下に*SEOの最適化*があります。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29 msgid "There you will see a *Track Page* checkbox to track this page." -msgstr "" +msgstr "そこに、このページを追跡するための*追跡ページ*チェックボックスがあります。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35 msgid "See visited pages in your leads/opportunities" -msgstr "" +msgstr "リード/案件内で訪問されたページを見る" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37 msgid "" @@ -3593,22 +3775,23 @@ msgid "" "the top right corner of your lead/opportunity you can see a *Page Views* " "button but also further down you will see them in the chatter." msgstr "" +"コンタクトフォームからリードが作成されるたびに、その訪問者が閲覧したページが記録されるようになりました。これらのページを見るには2つの方法があります。リード/案件の右上に*ページビュー*ボタンが表示され、さらにその下にあるチャターにも表示されます。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43 msgid "" "Both will update if the viewers comes back to your website and visits more " "pages." -msgstr "" +msgstr "どちらも、閲覧者がウェブサイトに戻ってきて、さらに多くのページを訪れた場合に更新されます。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52 msgid "" "The feature will not repeat multiple viewings of the same pages in the " "chatter." -msgstr "" +msgstr "この機能は、チャターで同じページを何度も繰返し表示することはありません。" #: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55 msgid "Your customers will no longer be able to keep any secrets from you!" -msgstr "" +msgstr "顧客は、もはやあなたから何も隠すことはできません！" #: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" @@ -3621,20 +3804,22 @@ msgid "" " Product moves are automatically registered in your stock, you get real-time" " statistics, and your data is consolidated across all shops." msgstr "" +"**OdooPOS**で店舗やレストランを簡単に経営しましょう。このアプリはウェブブラウザがあればどのデバイスでも動作し、一時的にオフラインの状態でもご利用頂けます。プロダクトの移動は自動的に在庫に登録され、リアルタイムの統計を取得し、データは全ての店舗で統合されます。" #: ../../content/applications/sales/point_of_sale.rst:13 msgid "" "`Odoo Tutorials: Point of Sale Tutorials <https://www.odoo.com/slides/point-" "of-sale-28>`_" msgstr "" +"`Odooチュートリアル: POSチュートリアル <https://www.odoo.com/slides/point-of-sale-28>`_" #: ../../content/applications/sales/point_of_sale.rst:14 msgid ":doc:`IoT Boxes Documentations </applications/productivity/iot>`" -msgstr "" +msgstr ":doc:`IoTボックスドキュメンテーション</applications/productivity/iot>`" #: ../../content/applications/sales/point_of_sale.rst:19 msgid "Start a session" -msgstr "" +msgstr "セッションを開始" #: ../../content/applications/sales/point_of_sale.rst:21 msgid "" @@ -3643,6 +3828,8 @@ msgid "" "start a POS session, or click :guilabel:`Continue Selling` if the session is" " already opened." msgstr "" +"POSダッシュボード**から、 :guilabel:`新規セッション`をクリックし、 :guilabel:`キャッシュコントロールを開く`画面で、 " +":guilabel:`セッションを開く`をクリックしてPOSセッションを開始します。" #: ../../content/applications/sales/point_of_sale.rst:26 msgid "" @@ -3650,10 +3837,11 @@ msgid "" "same session at the same time. However, the session can only be opened once " "on the same browser." msgstr "" +":doc:`複数のユーザ<point_of_sale/employee_login>`が同時に同じセッションにログインすることができます。ただし、同じブラウザ上でセッションを開くことができるのは一度だけです。" #: ../../content/applications/sales/point_of_sale.rst:32 msgid "Sell products" -msgstr "" +msgstr "プロダクトの販売" #: ../../content/applications/sales/point_of_sale.rst:34 msgid "" @@ -3662,6 +3850,8 @@ msgid "" " **discount** or modify the product **price**, click respectively " ":guilabel:`% Disc` or :guilabel:`Price` and enter the amounts." msgstr "" +"プロダクトをクリックしてカートに入れます。**数量**を変更するには、:guilabel:`数量`をクリックし、キーパッドでプロダクト数を入力して下さい。**値引**を追加したり、プロダクトの**価格**を変更するには、それぞれ" +" :guilabel:`% 値引` または :guilabel:`価格` をクリックし、金額を入力して下さい。" #: ../../content/applications/sales/point_of_sale.rst:38 msgid "" @@ -3670,24 +3860,26 @@ msgid "" "amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move " "on to the next customer." msgstr "" +"オーダが完了したら、 :guilabel:`支払` をクリックしてチェックアウトに進みます。**支払方法**を選択し、受取った金額を入力して " +":guilabel:`検証` をクリックします。guilabel:`新規オーダ`をクリックし、次の顧客へ進みます。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "POS session interface." -msgstr "" +msgstr "POSセッションインターフェイス" #: ../../content/applications/sales/point_of_sale.rst:46 msgid "You can use both `,` and `.` on your keyboard as decimal separators." -msgstr "" +msgstr "キーボードの `,` と `.` は小数点の区切り文字として使用できます。" #: ../../content/applications/sales/point_of_sale.rst:47 msgid "" "**Cash** is selected by default if you enter the amount without choosing a " "payment method." -msgstr "" +msgstr "支払方法を選択せずに金額を入力した場合、デフォルトで**現金**が選択されます。" #: ../../content/applications/sales/point_of_sale.rst:52 msgid "Set customers" -msgstr "" +msgstr "顧客の設定" #: ../../content/applications/sales/point_of_sale.rst:54 msgid "" @@ -3696,6 +3888,9 @@ msgid "" "apply the :doc:`attributed pricelist <point_of_sale/pricing/pricelists>`, or" " :ref:`generate and print an invoice <receipts-invoices/invoices>`." msgstr "" +"顧客を登録することは、 :doc:`ロイヤルティポイントを回収して特典を与える<point_of_sale/pricing/loyalty>`、 " +":doc:`属性付き価格表を自動的に適用する<point_of_sale/pricing/pricelists>`、または " +":ref:`請求書を生成して印刷する<receipts-invoices/invoices>` ために必要です。" #: ../../content/applications/sales/point_of_sale.rst:59 msgid "" @@ -3705,6 +3900,9 @@ msgid "" " to :menuselection:`Point of Sale --> Orders --> Customers` and clicking " ":guilabel:`New`. Then, fill in the information and save." msgstr "" +"顧客は :ref:`POSセッションを開く <pos/session-start>` から :menuselection:`顧客 --> 作成` " +"をクリックし、連絡先情報を入力することで作成できます。また、バックエンドから :menuselection:`POS --> オーダ --> 顧客` " +"に行き、 :guilabel:`新規` をクリックして顧客を作成することもできます。その後、情報を入力して保存します。" #: ../../content/applications/sales/point_of_sale.rst:64 msgid "" @@ -3712,10 +3910,12 @@ msgid "" ":guilabel:`Customer` on the POS interface. You can also set a customer at " "the payment screen by clicking :guilabel:`Customer`." msgstr "" +"オーダ中に顧客を設定するには、POSインターフェースの :guilabel:`顧客` をクリックして顧客リストにアクセスします。また、支払画面で " +":guilabel:`顧客` をクリックして顧客を設定することもできます。" #: ../../content/applications/sales/point_of_sale.rst:71 msgid "Customer notes" -msgstr "" +msgstr "顧客メモ" #: ../../content/applications/sales/point_of_sale.rst:73 msgid "" @@ -3724,6 +3924,8 @@ msgid "" "and maintenance tips. They can also be used to track a customer's particular" " request, such as not wanting the product to be assembled for them." msgstr "" +"ref:`POSセッション<pos/session-" +"start>`から直接、特定のプロダクトに関する**顧客メモ**を追加することができます。例えば、クリーニングやメンテナンスのヒントを提供するためです。また、プロダクトを組み立ててほしくないなど、顧客の特別な要望を追跡するために使用することもできます。" #: ../../content/applications/sales/point_of_sale.rst:77 msgid "" @@ -3731,74 +3933,80 @@ msgid "" "Doing so opens a pop-up window in which you can add or modify content for " "the note." msgstr "" +"そのためには、プロダクトを選択し、パッドの :guilabel:`顧客メモ` " +"をクリックします。ポップアップウィンドウが開き、メモの内容を追加または変更することができます。" #: ../../content/applications/sales/point_of_sale.rst:81 msgid "" "Product notes from an :doc:`imported SO <point_of_sale/shop/sales_order>` " "are displayed identically in the cart." msgstr "" +"doc:`インポート済販売オーダ <point_of_sale/shop/sales_order>` " +"のプロダクトメモは、カート内で同じように表示されます。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Customer note button and notes (SO and POS session) on products in the cart" -msgstr "" +msgstr "顧客メモボタンとカート内のプロダクトのメモ(販売オーダとPOSセッション)" #: ../../content/applications/sales/point_of_sale.rst:87 msgid "" "Customer notes appear on customers' receipts and invoices similarly to how " "they appear in the cart, under the related product." -msgstr "" +msgstr "顧客メモは、カート内の関連プロダクトの下に表示されるのと同様に、顧客の領収書や請求書に表示されます。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Customer receipt with notes from an SO and from the customer note feature" -msgstr "" +msgstr "販売オーダからのメモと顧客メモ機能による顧客レシート" #: ../../content/applications/sales/point_of_sale.rst:96 msgid "Return and refund products" -msgstr "" +msgstr "プロダクトの返品と返金" #: ../../content/applications/sales/point_of_sale.rst:98 msgid "To return and refund a product," -msgstr "" +msgstr "プロダクトを返品・返金するには" #: ../../content/applications/sales/point_of_sale.rst:100 msgid ":ref:`start a session <pos/session-start>` from the **POS dashboard**;" -msgstr "" +msgstr ":ref:`POSダッシュボード**からセッション<pos/session-start>`を開始します;" #: ../../content/applications/sales/point_of_sale.rst:101 msgid "click :guilabel:`Refund` and select the corresponding order;" -msgstr "" +msgstr "guilabel:`返金`をクリックし、該当するオーダを選択します;" #: ../../content/applications/sales/point_of_sale.rst:102 msgid "select the product and the quantity to refund using the keypad;" -msgstr "" +msgstr "キーパッドで返金するプロダクトと数量を選択します;" #: ../../content/applications/sales/point_of_sale.rst:103 msgid "click :guilabel:`Refund` to go back to the previous screen;" -msgstr "" +msgstr "guilabel:`返金`をクリックすると前の画面に戻ります;" #: ../../content/applications/sales/point_of_sale.rst:104 msgid "" "once the order is completed, click :guilabel:`Payment` to proceed to the " "refund;" -msgstr "" +msgstr "オーダが完了したら、:guilabel:`支払`をクリックして返金に進みます;" #: ../../content/applications/sales/point_of_sale.rst:105 msgid "" "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next " "customer." -msgstr "" +msgstr "guilabel:`検証` と :guilabel:`新規オーダ` をクリックして次の顧客に進みます。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "refund view from a POS" -msgstr "" +msgstr "POSからの返金ビュー" #: ../../content/applications/sales/point_of_sale.rst:111 msgid "" "You can filter the **orders list** by :guilabel:`Receipt Number`, " ":guilabel:`Date` or :guilabel:`Customer` using the search bar." msgstr "" +"検索バーを使って、 :guilabel:`領収書番号`、 :guilabel:`日付`、 :guilabel:`顧客` " +"で**オーダリスト**をフィルタリングすることができます。" #: ../../content/applications/sales/point_of_sale.rst:113 msgid "" @@ -3807,22 +4015,25 @@ msgid "" " products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by " "the quantity of returned products." msgstr "" +"また、オープンセッションから返品されたプロダクトを選択し、返品されたプロダクトの数と等しいマイナスの数量を設定することで、プロダクトを返金することもできます。そのためには、:guilabel:`数量`と:guilabel:`+/-`の後に返品プロダクトの数量をクリックして下さい。" #: ../../content/applications/sales/point_of_sale.rst:120 msgid "Manage the cash register" -msgstr "" +msgstr "現金レジの管理" #: ../../content/applications/sales/point_of_sale.rst:122 msgid "" "To add or take out cash from the register, click the **menu icon** in the " "upper right corner of your screen and :guilabel:`Cash In/Out`." -msgstr "" +msgstr "レジで現金を追加したり引出したりするには、画面右上の**メニューアイコン**と:guilabel:`現金入金/出金`をクリックします。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "" "Dropdown menu to close a POS session, reach the backend, add or take cash out or check\n" "orders" msgstr "" +"POSセッションを閉じたり、バックエンドにアクセスしたり、現金を引出したりオーダを確認したりするためのドロップダウン\n" +"メニュー。" #: ../../content/applications/sales/point_of_sale.rst:129 msgid "" @@ -3830,31 +4041,33 @@ msgid "" "or :guilabel:`Cash Out`, enter the amount and the reason, and click " ":guilabel:`Confirm`." msgstr "" +"そうするとポップアップウィンドウが開き、 :guilabel:`現金入金` または :guilabel:`現金出勤` を選択し、金額と理由を入力して " +":guilabel:`確認`をクリックします。" #: ../../content/applications/sales/point_of_sale.rst:135 msgid "Close the POS session" -msgstr "" +msgstr "POSセッションを終了する" #: ../../content/applications/sales/point_of_sale.rst:137 msgid "" "To close your session, click the **menu icon** in the upper right corner of " "your screen and :guilabel:`Close Session`." -msgstr "" +msgstr "セッションを終了するには、画面右上の**メニューアイコン**をクリックし、 :guilabel:`セッション終了` をクリックします。" #: ../../content/applications/sales/point_of_sale.rst:140 msgid "" "Doing so opens the :guilabel:`Closing Control` pop-up screen. From this " "screen, you can retrieve various information:" -msgstr "" +msgstr "そうすると :guilabel:`終了管理` ポップアップ画面が開きます。この画面から様々な情報を得ることができます:" #: ../../content/applications/sales/point_of_sale.rst:143 msgid "" "the number of orders made and the total amount made during the session;" -msgstr "" +msgstr "セッション中に行われたオーダの数と合計金額;" #: ../../content/applications/sales/point_of_sale.rst:144 msgid "the expected amounts grouped by payment method." -msgstr "" +msgstr "支払方法ごとにグループ化された見込金額。" #: ../../content/applications/sales/point_of_sale.rst:146 msgid "" @@ -3865,26 +4078,29 @@ msgid "" " amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money " "Details` are specified in the **Notes** section." msgstr "" +"このウィンドウを閉じる前に、電卓アイコンを使用して現金を数えます。そうするとポップアップウィンドウが開き、手動で数えて追加した硬貨と紙幣に応じて、レジ引出しの合計金額を計算します。その後、" +" :guilabel:`確認`または :guilabel:`破棄`をクリックしてウィンドウを閉じます。計算された金額は " +":guilabel:`カウント済` カラムに設定され、 :guilabel:`お金詳細` は **メモ** セクションに指定されます。" #: ../../content/applications/sales/point_of_sale.rst-1 msgid "How to close a POS session." -msgstr "" +msgstr "POSセッション終了方法" #: ../../content/applications/sales/point_of_sale.rst:155 msgid "" "Once you are done controlling the amounts, click :guilabel:`Close Session` " "to close and go back to the **POS dashboard**." -msgstr "" +msgstr "金額の確認が終わったら、:guilabel:`セッションを終了`をクリックして閉じ、**POSダッシュボード**に戻ります。" #: ../../content/applications/sales/point_of_sale.rst:159 msgid "" "To reach the backend without closing the session, click :guilabel:`Backend` " "on the dropdown menu." -msgstr "" +msgstr "セッションを閉じずにバックエンドに到達するには、ドロップダウンメニューの :guilabel:`バックエンド` をクリックします。" #: ../../content/applications/sales/point_of_sale.rst:161 msgid "To abort, click :guilabel:`Discard` on the pop-up window." -msgstr "" +msgstr "中止するには、ポップアップウィンドウの :guilabel:`廃棄` をクリックします。" #: ../../content/applications/sales/point_of_sale.rst:162 msgid "" @@ -3892,21 +4108,23 @@ msgid "" " expected cash revenue equals the counted cash. To close it anyway, click " ":guilabel:`Ok` on the :guilabel:`Payments Difference` screen." msgstr "" +"設定によっては、見込現金売上とカウントされた現金が等しい場合のみ、セッションを閉じることができます。いずれにせよセッションを終了するには、 " +":guilabel:`支払差額` 画面の :guilabel:`OK`をクリックして下さい。" #: ../../content/applications/sales/point_of_sale.rst:167 msgid "" "It is strongly advised to close your POS session at the end of each day." -msgstr "" +msgstr "一日の終わりにPOSセッションを終了することを強くお勧めします。" #: ../../content/applications/sales/point_of_sale.rst:168 msgid "" "To look at all your previous sessions, go to :menuselection:`Point of Sale " "--> Orders --> Sessions`." -msgstr "" +msgstr "過去の全てのセッションを見るには、 :menuselection:`POS --> オーダ --> セッション`にアクセスして下さい。" #: ../../content/applications/sales/point_of_sale/configuration.rst:11 msgid "Access POS settings" -msgstr "" +msgstr "POS設定にアクセス" #: ../../content/applications/sales/point_of_sale/configuration.rst:13 msgid "" @@ -3914,10 +4132,12 @@ msgid "" "Configuration --> Settings`. Then, open the dropdown menu in the " ":guilabel:`Point of Sale` field and select the POS to configure." msgstr "" +"一般的なPOS設定にアクセスするには、 :menuselection:`POS --> 設定 --> 管理設定`に進みます。次に、 " +":guilabel:`POS`フィールドのドロップダウンメニューを開き、設定するPOSを選択します。" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Dropdown menu to select the POS in the app settings" -msgstr "" +msgstr "アプリの設定でPOSを選択するドロップダウンメニュー" #: ../../content/applications/sales/point_of_sale/configuration.rst:21 msgid "" @@ -3925,6 +4145,7 @@ msgid "" "</applications/general/users/manage_users>` :guilabel:`Administration` set " "as :guilabel:`Settings`." msgstr "" +"これらの設定は :doc:`アクセス権 ` :guilabel:`管理`を :guilabel:`管理設定`に設定したユーザが利用できます。" #: ../../content/applications/sales/point_of_sale/configuration.rst:25 msgid "" @@ -3932,23 +4153,24 @@ msgid "" "vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a " "popup window, from which you can:" msgstr "" +"ダッシュボードからPOSカードの縦長の省略記号ボタン(:guilabel:`↪Sm_22EE`)をクリックして、いくつかの設定を行うこともできます。そうするとポップアップウィンドウが開き、以下のことができます:" #: ../../content/applications/sales/point_of_sale/configuration.rst:28 msgid ":doc:`Enable multiple employees to log in. <employee_login>`" -msgstr "" +msgstr ":doc:`複数の従業員がログインできるようにする <employee_login>`" #: ../../content/applications/sales/point_of_sale/configuration.rst:29 msgid "" ":doc:`Connect and set up an IoT box. <../../productivity/iot/config/pos>`" -msgstr "" +msgstr ":doc:`IoTボックスの接続と設定<../../productivity/iot/config/pos>`" #: ../../content/applications/sales/point_of_sale/configuration.rst:30 msgid ":doc:`Connect and set up an ePOS printer. <configuration/epos_ssc>`" -msgstr "" +msgstr ":doc:`ePOSプリンタの接続と設定<configuration/epos_ssc>`" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "popup window to access quick settings in POS" -msgstr "" +msgstr "POSでのクイック設定へアクセスするポップアップウィンドウ" #: ../../content/applications/sales/point_of_sale/configuration.rst:36 msgid "" @@ -3956,10 +4178,11 @@ msgid "" "</applications/general/users/manage_users>` :guilabel:`Point of Sale` set as" " :guilabel:`Administrator`." msgstr "" +"これらの設定は、 :doc:`アクセス権 ` :guilabel:`POS` を :guilabel:`管理者` に設定したユーザが利用できます。" #: ../../content/applications/sales/point_of_sale/configuration.rst:41 msgid "Make products available" -msgstr "" +msgstr "プロダクトを利用可能にする" #: ../../content/applications/sales/point_of_sale/configuration.rst:43 msgid "" @@ -3967,14 +4190,16 @@ msgid "" " Products --> Products`, and select a product to open the product form. In " "the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." msgstr "" +"プロダクトを販売可能にするには、 :menuselection:`POS --> プロダクト --> プロダクト` " +"に進み、プロダクトを選択してプロダクトフォームを開きます。guilabel:`販売` タブで :guilabel:`POSで利用可能` を有効にします。" #: ../../content/applications/sales/point_of_sale/configuration.rst-1 msgid "Making a product available in your POS." -msgstr "" +msgstr "POSでプロダクトを利用可能にします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 msgid "Self-signed certificate for ePOS printers" -msgstr "" +msgstr "ePOSプリンタ用自己署名証明書" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 msgid "" @@ -3982,6 +4207,7 @@ msgid "" "Once connected, the two devices automatically share information, enabling " "the direct printing of tickets from the POS system to the ePOS printer." msgstr "" +"ePOSプリンタは、POSシステムとシームレスに動作するように設計されています。一旦接続されると、2つのデバイスは自動的に情報を共有し、POSシステムからePOSプリンタへのチケットの直接印刷を可能にします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 msgid "" @@ -3989,70 +4215,72 @@ msgid "" "biz.com/modules/community/index.php?content_id=91>`_ are compatible with " "Odoo:" msgstr "" +"これらの `Epson ePOSプリンタ <https://c4b.epson-" +"biz.com/modules/community/index.php?content_id=91>`_ はOdooと互換性があります:" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 msgid "TM-H6000IV-DT (Receipt printer only)" -msgstr "" +msgstr "TM-H6000IV-DT (領収書プリンタのみ)" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 msgid "TM-T70II-DT" -msgstr "" +msgstr "TM-T70II-DT" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 msgid "TM-T88V-DT" -msgstr "" +msgstr "TM-T88V-DT" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 msgid "TM-L90-i" -msgstr "" +msgstr "TM-L90-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 msgid "TM-T20II-i" -msgstr "" +msgstr "TM-T20II-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 msgid "TM-T70-i" -msgstr "" +msgstr "TM-T70-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 msgid "TM-T82II-i" -msgstr "" +msgstr "TM-T82II-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 msgid "TM-T83II-i" -msgstr "" +msgstr "TM-T83II-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 msgid "TM-T88V-i" -msgstr "" +msgstr "TM-T88V-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 msgid "TM-U220-i" -msgstr "" +msgstr "TM-U220-i" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 msgid "TM-m10" -msgstr "" +msgstr "TM-m10" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 msgid "TM-m30" -msgstr "" +msgstr "TM-m30" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 msgid "TM-P20 (Wi-Fi® model)" -msgstr "" +msgstr "TM-P20 (Wi-Fi® model)" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 msgid "TM-P60II (Receipt: Wi-Fi® model)" -msgstr "" +msgstr "TM-P60II (Receipt: Wi-Fi® model)" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 msgid "TM-P60II (Peeler: Wi-Fi® model)" -msgstr "" +msgstr "TM-P60II (Peeler: Wi-Fi® model)" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 msgid "TM-P80 (Wi-Fi® model)" -msgstr "" +msgstr "TM-P80 (Wi-Fi® model)" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 msgid "" @@ -4065,6 +4293,9 @@ msgid "" "allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " "long as the browser window stays open." msgstr "" +"Odooで動作するために、:doc:`IoTボックス<../../../productivity/iot/config/connect>`なしで使用できる一部のモデルでは、ブラウザとプリンタ間の安全な接続を確立するために:doc:`HTTPSプロトコル`<https>が必要になる場合があります。しかし、HTTPSを使用してプリンタのIPアドレスに到達しようとすると、ほとんどのウェブブラウザで警告ページが表示されます。この場合、一時的に" +" :ref:`接続を強制 <epos_ssc/instructions>` " +"を実行することで、ブラウザウィンドウが開いている間はHTTPSでページにアクセスし、OdooでePOSプリンタを使用することができます。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 msgid "" @@ -4072,16 +4303,18 @@ msgid "" "method should only be used as a **workaround** or as a pre-requisite for the" " :ref:`following instructions <epos_ssc/instructions>`." msgstr "" +"ブラウザウィンドウを閉じると接続は失われます。そのため、このメソッドは**回避策**として、または :ref:`指示に従う " +"<epos_ssc/instructions>` の前提条件としてのみ使用して下さい。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 msgid "Generate, export, and import self-signed certificates" -msgstr "" +msgstr "自己署名証明書の生成、エクスポート、インポート" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 msgid "" "For a long-term solution, you must generate a **self-signed certificate**. " "Then, export and import it into your browser." -msgstr "" +msgstr "長期的な解決策としては、**自己署名証明書**を生成する必要があります。そして、それをエクスポートしてブラウザにインポートします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 msgid "" @@ -4089,15 +4322,16 @@ msgid "" "create another certificate, devices using the previous one will lose HTTPS " "access." msgstr "" +"**SSL証明書の生成は一度だけ行って下さい。別の証明書を作成すると、前の証明書を使用しているデバイスはHTTPSアクセスを失うことになります。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 msgid "Windows 10 & Linux OS" -msgstr "" +msgstr "Windows 10 & Linux OS" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191 msgid "Generate a self-signed certificate" -msgstr "" +msgstr "自己署名証明書の生成" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 @@ -4106,15 +4340,17 @@ msgid "" "the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " "[IP address] (unsafe)`." msgstr "" +"ePOSのIPアドレス(例えば`https://192.168.1.25`)に移動し、 :guilabel:`詳細`と :guilabel:` " +"[IPアドレス] (安全でない)へプロセス`をクリックして強制的に接続します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "warning page about the connection privacy on Google Chrome" -msgstr "" +msgstr "Google Chromeの接続プライバシーに関する警告ページ" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 msgid "Warning page on Google Chrome, Windows 10" -msgstr "" +msgstr "Google Chrome, Windows 10の警告ページ" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203 @@ -4123,6 +4359,8 @@ msgid "" "settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " "printer serial number in the :guilabel:`Password` field." msgstr "" +"次に、プリンタの認証情報を使用してサインインし、ePOSプリンタ設定にアクセスします。サインインするには、 :guilabel:`ID` フィールドに " +"`epson` と入力し、 :guilabel:`パスワード` フィールドにプリンタのシリアル番号を入力します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207 @@ -4135,6 +4373,10 @@ msgid "" "click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " "printer." msgstr "" +"guilabel:`認証` セクションの :guilabel:`証明書リスト` をクリックし、 :guilabel:`作成` をクリックして新しい " +"**自己署名証明書** " +"を生成します。guilabel:`共通名`は自動的に入力されるはずです。そうでない場合は、プリンタのIPアドレス番号を入力します。guilabel:`有効期間`フィールドで証明書の有効期間を選択し、" +" :guilabel:`作成` をクリックして :guilabel:`リセット` または手動でプリンタを再起動します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 @@ -4144,11 +4386,13 @@ msgid "" "**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " "Certificate` section." msgstr "" +"自己署名証明書が生成されます。ページをリロードし、 :guilabel:`セキュリティ` セクションの :guilabel:`SSL/TLS` " +"をクリックして、 :guilabel:`サーバ証明書` セクションで **自己署名証明書** が正しく選択されていることを確認します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 msgid "Export a self-signed certificate" -msgstr "" +msgstr "自己署名証明書のエクスポート" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 @@ -4159,101 +4403,104 @@ msgid "" "Then, force the connection as explained in the **Generate a self-signed " "certificate tab**." msgstr "" +"エクスポートプロセスは :abbr:`OS (オペレーティングシステム)` " +"とブラウザに大きく依存します。まず、ウェブブラウザでePOSプリンタの設定にアクセスし、IPアドレス(例：`https://192.168.1.25`)に移動します。次に、**自己署名証明書を生成するタブ**で説明したように、強制的に接続します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225 msgid "If you are using **Google Chrome**," -msgstr "" +msgstr "もし **Googleクローム**を使用している場合、" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 msgid "" "click :guilabel:`Not secure` next to the search bar, and " ":guilabel:`Certificate is not valid`;" -msgstr "" +msgstr "検索バーの横にある :guilabel:`安全ではない` と :guilabel:`証明書が有効ではありません` をクリックして下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection to the printer not secure button in Google Chrome browser." -msgstr "" +msgstr "Google Chromeブラウザで、プリンタへの接続が安全でないボタンが表示されます。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" -msgstr "" +msgstr "guilabel:`詳細`タブを開き、:guilabel:`エキスポート`をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234 msgid "" "add `.crt` at the end of the file name to ensure it has the correct " "extension;" -msgstr "" +msgstr "ファイル名の末尾に`.crt`を追加し、正しい拡張子であることを確認して下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235 msgid "" "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " "of the pop-up window;" -msgstr "" +msgstr "ポップアップウィンドウの下部にある :guilabel:`Base64-ASCIIエンコード済、単一証明書` を選択します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 msgid "save, and the certificate is exported." -msgstr "" +msgstr "保存すると、証明書がエクスポートされます。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not see the file during the import process." msgstr "" +"証明書の末尾が拡張子 `.crt` であることを確認して下さい。そうしないと、インポート処理中にブラウザによってはファイルが表示されないことがあります。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243 msgid "If you are using **Mozilla Firefox**," -msgstr "" +msgstr "もし **Mozilla Firefox**使用している場合、" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 msgid "click the **lock-shaped** icon on the left of the address bar;" -msgstr "" +msgstr "アドレスバーの左にある**時計の形をした**アイコンをクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246 msgid "" "go to :menuselection:`Connection not secure --> More information --> " "Security tab --> View certificate`;" -msgstr "" +msgstr "menuselection:`接続が安全ではない --> 詳細情報 --> セキュリティタブ --> 証明書を見る`にアクセスして下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection is not secure button in Mozilla Firefox browser" -msgstr "" +msgstr "Mozilla Firefoxブラウザの接続が安全ではありませんボタン" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252 msgid "scroll down to the :guilabel:`Miscellaneous` section;" -msgstr "" +msgstr "guilabel:`その他`セクションまでスクロールダウンして下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" -msgstr "" +msgstr "guilabel:`ダウンロード`セクションの :guilabel:`PEM (cert)` をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "Import a self-signed certificate" -msgstr "" +msgstr "自己署名証明書のインポート" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "" "The import process is heavily dependent on the :abbr:`OS (Operating System)`" " and the browser." -msgstr "" +msgstr "インポート処理は :abbr:`OS (Operating System)`とブラウザに大きく依存します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "Windows 10" -msgstr "" +msgstr "Windows 10" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "" @@ -4261,17 +4508,18 @@ msgid "" "must be imported from the certification file rather than the browser. To do " "so," msgstr "" +"Windows 10は証明書を管理しているため、自己署名証明書はブラウザではなく証明書ファイルからインポートする必要があります。そのためには" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "" "open the Windows File Explorer and locate the downloaded certification file;" -msgstr "" +msgstr "Windowsのファイルエクスプローラを開き、ダウンロードした認証ファイルを探します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 msgid "" "right-click on the certification file and click :guilabel:`Install " "Certificate`;" -msgstr "" +msgstr "証明書ファイルを右クリックし、:guilabel:`証明書をインストール`をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 msgid "" @@ -4279,6 +4527,8 @@ msgid "" ":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " "click :guilabel:`Next`;" msgstr "" +"guilabel:`現在のユーザ`またはすべてのユーザ(:guilabel:`ローカルマシン`)のために、証明書をインストールする場所とユーザを選択します。次に" +" :guilabel:`次へ` をクリックします; " #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "" @@ -4286,119 +4536,128 @@ msgid "" " the following store`, click :guilabel:`Browse...`, and select " ":guilabel:`Trusted Root Certification Authorities`;" msgstr "" +" `証明書ストア`スクリーンで、 " +":guilabel:`全ての証明書を以下のストアに配置`をチェックし、:guilabel:`ブラウズ...`をクリックして:guilabel:`信頼できるルート証明機関`を選択します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 msgid "click :guilabel:`Finish`, accept the pop-up security window;" -msgstr "" +msgstr "guilabel:`終了`をクリックし、ポップアップするセキュリティウィンドウを受け入れます;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "restart the computer to make sure that the changes are applied." -msgstr "" +msgstr "コンピュータを再起動して、変更が適用されていることを確認して下さい。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "Linux" -msgstr "" +msgstr "Linux" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 msgid "open Chrome;" -msgstr "" +msgstr "Chromeを開く;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "" "go to :menuselection:`Settings --> Privacy and security --> Security --> " "Manage certificates`;" -msgstr "" +msgstr " :menuselection:`管理設定 --> プライバシーとセキュリティ --> セキュリティ --> 証明書の管理`;に行きます" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "" "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " "the exported certification file;" msgstr "" +" :guilabel:`機関` タブに行き、 :guilabel:`インポート`をクリックして、エクスポート済の証明書ファイルを選択します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 msgid "accept all warnings;" -msgstr "" +msgstr "全ての警告を受け入れる;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 msgid "click :guilabel:`ok`;" -msgstr "" +msgstr " :guilabel:`ok`をクリック;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 msgid "restart your browser." -msgstr "" +msgstr "ブラウザを再スタートして下さい。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 msgid "open Firefox;" -msgstr "" +msgstr "Firefoxを開きます;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 msgid "" "go to :menuselection:`Settings --> Privacy & Security --> Security --> View " "Certificates... --> Import`;" msgstr "" +" :menuselection:`管理設定 --> プライバシー&セキュリティ --> セキュリティ --> 証明書を見る... --> " +"インポート`をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 msgid "select the exported certification file;" -msgstr "" +msgstr "エクスポートされた認証ファイルを選択します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 msgid "tick the checkboxes and validate;" -msgstr "" +msgstr "チェックボックスにチェックを入れ、検証します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 msgid "Mac OS" -msgstr "" +msgstr "Mac OS" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 msgid "" "On Mac OS, you can secure the connection for all browsers by following these" " steps:" -msgstr "" +msgstr "Mac OSでは、以下の手順で全てのブラウザの接続を保護できます: " #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 msgid "" "open Safari and navigate to your printer's IP address. Doing so leads to a " "warning page;" -msgstr "" +msgstr "Safariを開き、プリンタのIPアドレスに移動します。そうすると警告ページが表示されます;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "" "on the warning page, go to :menuselection:`Show Details --> visit this " "website --> Visit Website`, validate;" msgstr "" +"警告ページで :menuselection:`詳細を表示 --> このウェブサイトを表示 --> ウェブサイトを訪問` に進み、検証します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 msgid "reboot the printer so you can use it with any other browser." -msgstr "" +msgstr "プリンタを再起動し、他のブラウザで使用できるようにします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 msgid "" "To generate and export an SSL certificate and send it to IOS devices, open " "**Google Chrome** or **Mozilla Firefox**. Then," msgstr "" +"SSL証明書を生成してエクスポートし、IOSデバイスに送信するには、**Googleクローム**または**Mozilla " +"Firefox**を開きます。それから" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Warning page about the connection privacy on Google Chrome" -msgstr "" +msgstr "Google Chromeの接続プライバシーに関する警告ページ" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection to the printer not secure button in Google Chrome" -msgstr "" +msgstr "Google Chromeのプリンタへの接続が安全ではないことを示すボタン" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240 msgid "" "Make sure that the certificate ends with the extension `.crt`. Otherwise, " "some browsers might not find the file during the import process." msgstr "" +"証明書の末尾が拡張子 `.crt` であることを確認して下さい。そうしないと、インポート処理中にファイルが見つからないブラウザがあるかもしれません。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 msgid "Connection is not secure button in Mozilla Firefox" -msgstr "" +msgstr "Mozilla Firefoxの接続が安全ではないことを示すボタン" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 msgid "Android OS" -msgstr "" +msgstr "Android OS" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 msgid "" @@ -4406,28 +4665,29 @@ msgid "" " it from a computer. Next, transfer the `.crt` file to the device using " "email, Bluetooth, or USB. Once the file is on the device," msgstr "" +"SSL証明書をAndroid端末にインポートするには、まずコンピュータでSSL証明書を作成し、エクスポートします。次に、Eメール、Bluetooth、またはUSBを使用して、`.crt`ファイルをデバイスに転送します。ファイルがデバイスに入ったら" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262 msgid "open the settings and search for `certificate`;" -msgstr "" +msgstr "設定を開き、`証明書`を検索します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263 msgid "click :guilabel:`Certificate AC` (Install from device storage);" -msgstr "" +msgstr "guilabel:`証明書AC`(デバイスストレージからインストール)をクリックします; " #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264 msgid "select the certificate file to install it on the device." -msgstr "" +msgstr "証明書ファイルを選択し、デバイスにインストールします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 msgid "" "The specific steps for installing a certificate may vary depending on the " "version of Android and the device manufacturer." -msgstr "" +msgstr "証明書をインストールする具体的な手順は、Androidのバージョンやデバイスメーカによって異なる場合があります。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270 msgid "iOS" -msgstr "" +msgstr "iOS" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 msgid "" @@ -4435,6 +4695,7 @@ msgid "" "from a computer. Then, transfer the `.crt` file to the device using email, " "Bluetooth, or any file-sharing service." msgstr "" +"iOSデバイスにSSL証明書をインポートするには、まずコンピュータでSSL証明書を作成し、エクスポートします。次に、Eメール、Bluetooth、またはファイル共有サービスを使用して、`.crt`ファイルをデバイスに転送します。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276 msgid "" @@ -4442,56 +4703,57 @@ msgid "" ":guilabel:`Allow` to download the configuration profile, and close the " "second pop-up window. Then," msgstr "" +"このファイルをダウンロードすると、警告のポップアップウィンドウが表示されます。guilabel:`許可する`をクリックして構成プロファイルをダウンロードし、2つ目のポップアップウィンドウを閉じます。次に" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279 msgid "go to the **Settings App** on the iOS device;" -msgstr "" +msgstr "iOSデバイスの**設定アプリ**にアクセスして下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 msgid "click :guilabel:`Profile Downloaded` under the user's details box;" -msgstr "" +msgstr "ユーザの詳細ボックスの下にある :guilabel:`プロファイルダウンロード済` をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281 msgid "locate the downloaded `.crt` file and select it;" -msgstr "" +msgstr "ダウンロードした `.crt` ファイルを探し、選択します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 msgid "click :guilabel:`Install` on the top right of the screen;" -msgstr "" +msgstr "画面右上の :guilabel:`インストール` をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283 msgid "if a passcode is set on the device, enter the passcode;" -msgstr "" +msgstr "デバイスにパスコードが設定されている場合は、パスコードを入力します;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284 msgid "" "click :guilabel:`Install` on the top right of the certificate warning screen" " and the pop-up window;" -msgstr "" +msgstr "証明書の警告画面とポップアップウィンドウの右上にある :guilabel:`インストール` をクリックします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286 msgid "click :guilabel:`Done`." -msgstr "" +msgstr ":guilabel:`完了`をクリックします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290 msgid "" "The certificate is installed, but it still needs to be authenticated. To do " "so," -msgstr "" +msgstr "証明書はインストールされたが、まだ認証が必要です。そのためには" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292 msgid "" "go to :menuselection:`Settings --> General --> About > Certificate Trust " "Settings`;" -msgstr "" +msgstr "menuselection:`管理設定 --> 一般 --> 情報 > 認証信用設定`にアクセスして下さい;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293 msgid "enable the installed certificate using the **slide button**;" -msgstr "" +msgstr "スライドボタン**を使用して、インストールされた証明書を有効にします;" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294 msgid "click :guilabel:`Continue` on the pop-up window." -msgstr "" +msgstr "ポップアップウィンドウの :guilabel:`継続` をクリックします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297 msgid "" @@ -4500,6 +4762,8 @@ msgid "" "`the name of your browser or operating system` in your preferred search " "engine." msgstr "" +"言及されていないオペレーティングシステムやウェブブラウザからSSL証明書をエクスポートする必要がある場合は、お好みの検索エンジンで " +"`SSL証明書のエクスポート `+ `ブラウザまたはオペレーティングシステムの名前 `を検索して下さい。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 msgid "" @@ -4507,10 +4771,12 @@ msgid "" "search for `import SSL certificate root authority` + `the name of your " "browser or operating system` in your preferred search engine." msgstr "" +"同様に、指定されていないOSやブラウザからSSL証明書をインポートするには、お好みの検索エンジンで `SSL証明書のルート機関のインポート `＋ " +"`ブラウザまたはOSの名前 `を検索すします。" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 msgid "Check if the certificate was imported correctly" -msgstr "" +msgstr "証明書が正しくインポートされたか確認して下さい" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 msgid "" @@ -4520,26 +4786,28 @@ msgid "" "longer see a warning page, and the address bar should display a padlock " "icon, indicating that the connection is secure." msgstr "" +"プリンタの接続が安全であることを確認するには、HTTPSを使用してプリンタのIPアドレスに接続します。例えば、ブラウザで`https://192.168.1.25`に移動します。SSL証明書が正しく適用されていれば、警告ページが表示されなくなり、アドレスバーに南京錠のアイコンが表示され、接続が安全であることが示されます。" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 msgid "Secure connection (HTTPS)" -msgstr "" +msgstr "安全な接続 (HTTPS)" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 msgid "" "If **Direct Devices** is enabled in a Point of Sale settings (for example, " "if you use an ePos printer), HTTP becomes the default protocol." msgstr "" +"POSの設定で**直接デバイス**が有効になっている場合（ePosプリンタを使用している場合など）、HTTPがデフォルトのプロトコルになります。" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 msgid "Force your Point of Sale to use a secure connection (HTTPS)" -msgstr "" +msgstr "安全な接続(HTTPS)を使用するようにPOSを強制します。" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 msgid "" "Add a new **key** in the **System Parameters** to force your Point of Sale " "to use a secure connection with the HTTPS protocol." -msgstr "" +msgstr "システムパラメータ**に新しい**キー**を追加して、POSにHTTPSプロトコルによる安全な接続を使用させます。" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 msgid "" @@ -4548,22 +4816,24 @@ msgid "" "Parameters`, then create a new parameter, add the following values and click" " on *Save*." msgstr "" +"そのためには、 :ref:`開発者モード `を有効にし、 :menuselection:`設定 --> 技術 --> パラメータ --> " +"システムパラメータ`に進み、新しいパラメータを作成し、以下の値を追加して*保存*をクリックします。" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 msgid "**Key**: `point_of_sale.enforce_https`" -msgstr "" +msgstr "**キー**: `point_of_sale.enforce_https`" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 msgid "**Value**: `True`" -msgstr "" +msgstr "**値**: `True`" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 msgid ":doc:`epos_ssc`" -msgstr "" +msgstr ":doc:`epos_ssc`" #: ../../content/applications/sales/point_of_sale/employee_login.rst:3 msgid "Multi-employee management" -msgstr "" +msgstr "複数従業員管理" #: ../../content/applications/sales/point_of_sale/employee_login.rst:5 msgid "" @@ -4572,6 +4842,7 @@ msgid "" "select which users can log into the POS <employee_login/use>` and :ref:`keep" " track of the employees involved in each order <employee_login/analytics>`." msgstr "" +"OdooPOSでは、**セッションごと複数従業員**機能を有効にすることで、特定のPOSへのアクセスを管理することができます。この機能を有効にすると、:ref:`POSにログインできるユーザを選択<employee_login/use>`し、:ref:`各オーダに関与した従業員を追跡<employee_login/analytics>`することができます。" #: ../../content/applications/sales/point_of_sale/employee_login.rst:15 msgid "" @@ -4581,14 +4852,18 @@ msgid "" "Session`, and add the allowed employees in the :guilabel:`Allowed Employees`" " field." msgstr "" +":ref:`POS設定 <configuration/settings>` " +"にアクセスしてPOSを選択するか、POSカードの縦長の楕円ボタン(:guilabel:`↪Sm_22EE` )をクリックして " +":guilabel:`編集`をクリックします。次に、 :guilabel:`セッションごとの複数従業員` を有効にし、 " +":guilabel:`許可済従業員` フィールドに許可する従業員を追加します。" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "setting to enable multiple cashiers in POS" -msgstr "" +msgstr "POSで複数のレジを有効にする設定" #: ../../content/applications/sales/point_of_sale/employee_login.rst:26 msgid "Practical application" -msgstr "" +msgstr "実用" #: ../../content/applications/sales/point_of_sale/employee_login.rst:28 msgid "" @@ -4596,10 +4871,12 @@ msgid "" "badge <employee_login/badge>` or selecting their name from the list of " "allowed employees to :ref:`open the session <pos/session-start>`." msgstr "" +"この機能が有効になると、レジ係はバッジ<employee_login/badge>`をスキャンするか、許可された従業員リストから自分の名前を選択してログインし、セッション<pos/session-" +"start>`を開くことができます。" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "window to open a session when the multiple cashiers feature is enabled" -msgstr "" +msgstr "複数のキャッシャー機能が有効な場合に、セッションを開くためのウィンドウ" #: ../../content/applications/sales/point_of_sale/employee_login.rst:35 msgid "" @@ -4607,10 +4884,12 @@ msgid "" "click the employee name at the top-right of the screen and select the " "employee to swap with from the list." msgstr "" +"ref:`開いているセッション<pos/session-" +"start>`から別のユーザに切り替えるには、画面右上の社員名をクリックし、リストから切り替える社員を選択します。" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "button to switch from one cashier to another." -msgstr "" +msgstr "レジを別に切替るボタン" #: ../../content/applications/sales/point_of_sale/employee_login.rst:41 msgid "" @@ -4621,14 +4900,17 @@ msgid "" ":guilabel:`PIN Code` field of the :guilabel:`Attendance/Point of Sale` " "category." msgstr "" +"また、従業員がPOSにログインするたびにPINコードの入力を要求し、他の人物としてログインできないようにすることもできます。コードを定義するには、**従業員**アプリで従業員フォームを開き、" +" :guilabel:`HR管理設定` タブをクリックします。次に、 :guilabel:`勤怠/POS` カテゴリーの " +":guilabel:`PINコード` フィールドに任意のPINコードを入力します。" #: ../../content/applications/sales/point_of_sale/employee_login.rst-1 msgid "setting on the employee form to assign a badge ID and a PIN code." -msgstr "" +msgstr "バッジIDとPINコードを割当てるための従業員フォームの設定。" #: ../../content/applications/sales/point_of_sale/employee_login.rst:52 msgid "Log in using badges" -msgstr "" +msgstr "バッジを使ってログイン" #: ../../content/applications/sales/point_of_sale/employee_login.rst:54 msgid "" @@ -4638,12 +4920,16 @@ msgid "" "badge ID of your choice in the :guilabel:`Badge ID` field of the " ":guilabel:`Attendance/Point of Sale` category or click :guilabel:`Generate`." msgstr "" +"従業員がバッジをスキャンしてログインできるようにするには、バッジIDが割当てられている必要があります。そのためには、**従業員**アプリで従業員フォームを開き、" +" :guilabel:`HR管理設定` タブをクリックします。次に、 :guilabel:`勤怠/POS` カテゴリーの " +":guilabel:`Badge ID` フィールドに任意のバッジIDを入力するか、 :guilabel:`Generate` をクリックします。" #: ../../content/applications/sales/point_of_sale/employee_login.rst:59 msgid "" "To switch to another user, lock the session by clicking the lock-shaped icon" " (:guilabel:`🔓`) at the top-right of the screen and scan your badge." msgstr "" +"他のユーザに切り替えるには、画面右上のロックアイコン(:guilabel:`🔓)をクリックしてセッションをロックし、バッジをスキャンします。" #: ../../content/applications/sales/point_of_sale/employee_login.rst:65 msgid "Analytics" @@ -4660,6 +4946,10 @@ msgid "" ":guilabel:`Orders` button to view a list of all orders placed during that " "session." msgstr "" +"POSセッションを閉じて記帳したら、総合レポートにアクセスして、誰がセッションを開始し、誰が特定のオーダを処理したかなど、全てのセッションアクティビティを確認します。セッションのレポートにアクセスするには、POSカードの縦の省略記号ボタン(:guilabel:`↪Sm_22EE`" +" )をクリックし、 :guilabel:`表示`セクションから :guilabel:`セッション` " +"を選択します。次に、より詳細な情報を見るために特定のセッションを選択し、 " +":guilabel:`Orders`ボタンをクリックすると、そのセッション中に発注された全てのオーダのリストが表示されます。" #: ../../content/applications/sales/point_of_sale/employee_login.rst:74 msgid "" @@ -4667,6 +4957,8 @@ msgid "" "vertical ellipsis button (:guilabel:`⋮`) on the POS card and select " ":guilabel:`Orders` from the :guilabel:`View` section." msgstr "" +"セッションに関係なく、全てのオーダの概要を見るには、POSカードの縦長の楕円ボタン(:guilabel:`↪Sm_22EE`) をクリックし、 " +":guilabel:`表示` セクションから :guilabel:`オーダ` を選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 msgid "Payment methods" @@ -4679,6 +4971,8 @@ msgid "" "New`, and set a name. Check :guilabel:`Identify Customer` to allow this " "payment method *exclusively* for registered customers." msgstr "" +"支払方法を追加するには、まずそれを作成する必要があります。menuselection:`POS --> 設定 --> 支払方法 --> " +"新規`に行き、名前を設定します。guilabel:`顧客を特定`にチェックを入れて、この支払方法を登録された顧客だけに許可します。" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:11 msgid "" @@ -4686,10 +4980,12 @@ msgid "" "payment method for cash payments, or :guilabel:`Bank` to use it for card " "payments." msgstr "" +"次に :guilabel:`仕訳帳` を選択します。この支払方法を現金払いに使用する場合は :guilabel:`現金` を、カード払いに使用する場合は" +" :guilabel:`銀行` を選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods.rst-1 msgid "Creating a new payment method for a POS." -msgstr "" +msgstr "POSの新しい支払い方法を作成。" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 msgid "" @@ -4697,10 +4993,12 @@ msgid "" " Payment Terminal` field in which you can add your :doc:`payment terminal's " "information <payment_methods/terminals>`." msgstr "" +"guilabel:`銀行`仕訳帳を選択すると、自動的に :guilabel:`決済端末を使用` フィールドが追加され、そこに :doc:`決済端末の情報" +" <payment_methods/terminals>` を追加することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 msgid ":doc:`payment_methods/terminals`." -msgstr "" +msgstr ":doc:`payment_methods/terminals`." #: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 msgid "" @@ -4709,10 +5007,13 @@ msgid "" ":guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` " "section." msgstr "" +"一度、支払方法が作成されると、POS設定でそれを選択することができます。そのためには、 :ref:`POS' 管理設定 " +"<configuration/settings>` に行き、 :guilabel:`編集` をクリックし、 :guilabel:`支払` " +"セクションの下に支払方法を追加します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 msgid "Payment terminals" -msgstr "" +msgstr "決済端末" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 msgid "" @@ -4720,50 +5021,53 @@ msgid "" "you to accept multiple payment options, including credit and debit cards, " "making the payment process more efficient." msgstr "" +"POSシステムに決済端末を接続・統合することで、クレジットカードやデビットカードなど、複数の支払オプションを受け入れることができ、支払プロセスがより効率的になります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 msgid "" "Go to the :doc:`application settings <../configuration>`, scroll down to the" " :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." msgstr "" +"doc:`アプリ管理設定 <.../configuration>` に行き、 :guilabel:`決済端末` " +"セクションまでスクロールダウンし、端末のチェックボックスにチェックを入れます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1 msgid "checkbox in the settings to enable a payment terminal" -msgstr "" +msgstr "決済端末を有効にする管理設定のチェックボックス" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 msgid "Then, follow the corresponding documentation to configure your device:" -msgstr "" +msgstr "その後、対応するドキュメントに従ってデバイスを設定して下さい:" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 msgid ":doc:`Adyen configuration <terminals/adyen>`" -msgstr "" +msgstr ":doc:`Adyen設定 <terminals/adyen>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 msgid ":doc:`Ingenico configuration <terminals/ingenico>`" -msgstr "" +msgstr ":doc:`Ingenico設定 <terminals/ingenico>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 msgid ":doc:`SIX configuration <terminals/six>`" -msgstr "" +msgstr ":doc:`SIX設定 <terminals/six>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 msgid ":doc:`Stripe configuration <terminals/stripe>`" -msgstr "" +msgstr ":doc:`Stripe設定 <terminals/stripe>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 msgid ":doc:`Vantiv configuration <terminals/vantiv>`" -msgstr "" +msgstr ":doc:`Vantiv設定<terminals/vantiv>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 msgid ":doc:`Worldline configuration <terminals/worldline>`" -msgstr "" +msgstr ":doc:`Worldline設定 <terminals/worldline>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 msgid "" "Once the terminal is configured, you can :doc:`create the corresponding " "payment method and add it to the POS <../payment_methods>`." -msgstr "" +msgstr "端末が設定されたら、 :doc:`対応する支払方法を作成し、POS <../payment_methods>` に追加することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 msgid "Adyen" @@ -4773,14 +5077,14 @@ msgstr "Adyen" msgid "" "Connecting an **Adyen payment terminal** allows you to offer a fluid payment" " flow to your customers and ease the work of your cashiers." -msgstr "" +msgstr "**Adyen決済端末**を接続することで、お客様にスムーズな支払フローを提供し、レジ係の作業を軽減することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 msgid "" "Adyen works only with businesses processing **more** than **10 million " "annually** or invoicing a **minimum** of **1,000** transactions **per " "month**." -msgstr "" +msgstr "Adyenは、年間**1,000万件以上**の取引、または月間**1,000件以上**の請求書を発行している企業にのみ対応しています。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 msgid "" @@ -4788,12 +5092,16 @@ msgid "" "<https://www.adyen.com/>`_. Then, board your terminal following the steps " "described on your terminal's screen." msgstr "" +" " +"`Adyen'sウェブサイト<https://www.adyen.com/>`_でAdyenアカウントを作成します。それから、端末の画面に表示される手順に従って、端末にログインして下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 msgid "" "`Adyen Docs - Payment terminal quickstart guides " "<https://docs.adyen.com/point-of-sale/user-manuals>`_." msgstr "" +"`Adyenドキュメント - 決済端末クイックスタートガイド <https://docs.adyen.com/point-of-sale/user-" +"manuals>`_." #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 @@ -4801,7 +5109,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 msgid "Configure the payment method" -msgstr "" +msgstr "支払方法の設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 msgid "" @@ -4811,56 +5119,63 @@ msgid "" "method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` " "field." msgstr "" +"まず、 :menuselection:`POS --> 設定 --> 管理設定 --> 決済端末` に進み、 :guilabel:`Adyen` " +"を有効にします。次に、 :menuselection:`設定 --> 支払方法`に進み、新しい支払方法を作成します。guilabel:`決済端末を使用`" +" フィールドで :guilabel:`Adyen` を選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 msgid "" "The selected journal **must** be a bank journal for the :guilabel:`Use a " "payment terminal` field to appear." -msgstr "" +msgstr "guilabel:`決済端末を使用する`フィールドが表示されるためには、選択された仕訳帳は**銀行仕訳帳でなければなりません。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 msgid "" "Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an" " :guilabel:`Adyen Terminal Identifier`." -msgstr "" +msgstr "最後に、必須フィールドに :guilabel:`Adyen APIキー` と :guilabel:`Adyen端末識別子` を入力します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38 msgid "Generate an Adyen API key" -msgstr "" +msgstr "Adyen APIキーを生成" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 msgid "" "The **Adyen API key** is a key used to authenticate your requests. To " "generate an API key, go to your **Adyen account**." -msgstr "" +msgstr "**Adyen APIキー**は要求を認証するために使われます。APIキーを生成するには、**Adyen アカウント**に移動して下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43 msgid "" "Then, go to :menuselection:`Developers --> API credentials`. Create a new " "credential or click on an existing one." msgstr "" +"次に、 :menuselection:`Developers --> " +"API認証情報`に移動します。新しい認証情報を作成するか、既存の認証情報をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 msgid "" "Click on :guilabel:`Generate an API key` and copy-paste that key onto the " "Odoo mandatory field." -msgstr "" +msgstr "guilabel:`APIキーを生成`をクリックし、そのキーをOdooの必須フィールドにコピーペーストします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49 msgid "" "`Adyen Docs - API credentials <https://docs.adyen.com/development-" "resources/api-credentials#generate-api-key>`_." msgstr "" +"`Adyenドキュメント- API認証情報 <https://docs.adyen.com/development-resources/api-" +"credentials#generate-api-key>`_." #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 msgid "Locate the Adyen terminal identifier" -msgstr "" +msgstr "Adyen端末識別子を探す" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 msgid "" "The **Adyen Terminal Identifier** is your terminal's serial number, which is" " used to identify the hardware." -msgstr "" +msgstr "**Adyen端末識別子**は端末のシリアル番号で、ハードウェアを識別するために使用されます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 msgid "" @@ -4868,47 +5183,51 @@ msgid "" ":menuselection:`Point of Sale --> Terminals`, select the terminal to link, " "and copy-paste its serial number onto the Odoo mandatory field." msgstr "" +"この番号を確認するには、**Adyenアカウント**にアクセスして下さい。次に、:menuselection:`POS --> " +"端末`に進み、リンクする端末を選択し、Odooの必須フィールドにシリアル番号をコピーペーストします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63 msgid "Set the Event URLs" -msgstr "" +msgstr "イベントURLを設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 msgid "" "For Odoo to know when a payment is made, you must set the terminal **Event " "URLs**. To do so," -msgstr "" +msgstr "支払が行われたことをOdooに知らせるには、端末**イベントURL**を設定する必要があります。そのためには" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 msgid "log in to `Adyen's website <https://www.adyen.com/>`_;" -msgstr "" +msgstr " `Adyen'sウェブサイト <https://www.adyen.com/>`_;にログインします;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 msgid "" "go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and" " select the connected terminal;" -msgstr "" +msgstr "menuselection:`Adyen'sダッシュボード --> POS --> 端末`に移動し、接続している端末を選択します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:70 msgid "from the terminal settings, click :guilabel:`Integrations`;" -msgstr "" +msgstr "端末設定から :guilabel:`統合` をクリックします;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71 msgid "" "set the :guilabel:`Switch to decrypted mode to edit this setting` field as " ":guilabel:`Decrypted`;" -msgstr "" +msgstr "この設定を編集するには、:guilabel:`復号化モードに切り替える`フィールドを:guilabel:`復号化`に設定します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:72 msgid "" "click the **pencil icon** button and enter your server address, followed by " "`/pos_adyen/notification` in the :guilabel:`Event URLs` field; and" msgstr "" +"**鉛筆アイコン**ボタンをクリックし、:guilabel:`イベントURL` フィールドにサーバアドレスと " +"`/pos_adyen/notification` を入力します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74 msgid "" "click :guilabel:`Save` at the bottom of the screen to save the changes." -msgstr "" +msgstr "画面下の :guilabel:`保存` をクリックして変更を保存します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77 msgid "Add a new payment method" @@ -4921,6 +5240,8 @@ msgid "" "select the POS and go to :menuselection:`Payments --> Payment Methods`, and " "add your new method for Adyen." msgstr "" +"POSに新しい**支払方法**を追加するには、 :menuselection:`POS --> 設定 --> POS`に進みます。次に、POSを選択し、" +" :menuselection:`支払 --> 支払方法` に進み、Adyenの新しい支払方法を追加します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 @@ -4928,7 +5249,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86 msgid "Pay with a payment terminal" -msgstr "" +msgstr "決済端末で支払う" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86 msgid "" @@ -4936,6 +5257,8 @@ msgid "" "Check the amount and click on :guilabel:`Send`. Once the payment is " "successful, the status changes to :guilabel:`Payment Successful`." msgstr "" +"支払を処理する際、支払方法として :guilabel:`Adyen` を選択します。金額を確認し、 :guilabel:`送信` " +"をクリックします。支払が成功すると、ステータスが :guilabel:`支払完了` に変わります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 @@ -4943,18 +5266,18 @@ msgid "" "In case of connection issues between Odoo and the payment terminal, force " "the payment by clicking on :guilabel:`Force Done`, which allows you to " "validate the order." -msgstr "" +msgstr "Odooと決済端末間の接続に問題がある場合、:guilabel:`強制完了`をクリックして決済を強制します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 msgid "" "This option is only available after receiving an error message informing you" " that the connection failed." -msgstr "" +msgstr "このオプションは、接続に失敗したことを知らせるエラーメッセージを受信した後にのみ使用できます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:95 msgid "To cancel the payment request, click on :guilabel:`cancel`." -msgstr "" +msgstr "支払要求を取消するには、:guilabel:`取消`をクリックして下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 msgid "Ingenico" @@ -4966,13 +5289,13 @@ msgstr "Ingenico" msgid "" "Connecting a payment terminal allows you to offer a fluid payment flow to " "your customers and ease the work of your cashiers." -msgstr "" +msgstr "決済端末を接続することで、顧客にスムーズな決済フローを提供し、レジ係の作業を軽減することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 msgid "" "Please note that Ingenico is currently only available for customers in the " "Benelux." -msgstr "" +msgstr " Ingenico は現在ベネルクス諸国のお客様のみご利用頂けます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15 @@ -4986,16 +5309,18 @@ msgid "" "database, please refer to the :doc:`IoT documentation " "</applications/productivity/iot/config/connect>`." msgstr "" +"Ingenico決済端末をOdooに接続するには、IoT Boxが必要です。IoT " +"Boxをデータベースに接続する方法については、:doc:`IoTドキュメンテーション</applications/productivity/iot/config/connect>'をご参照下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 msgid "Configure the Lane/5000 for Ingenico BENELUX" -msgstr "" +msgstr "Ingenico BENELUX用Lane/5000の設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 msgid "" "Click on the F button of the terminal, then go in the :menuselection:`PoS " "Menu --> Settings` and enter the settings password." -msgstr "" +msgstr "端末のFボタンをクリックし、:menuselection:`POSメニュー --> 管理設定`に入り、設定パスワードを入力します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 msgid "" @@ -5004,12 +5329,15 @@ msgid "" "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 "" +"ここで、接続の変更とTCP/IPをクリックします。*IoT Box*のIPを入力する（IoT " +"Boxのフォームビューで確認できます）。次に、ポートに9000を入力します。端末が再起動します。再起動が完了したら、Odooの*IoT " +"Box*フォームに移動し、端末が見つかったことを確認して下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 msgid "" "First, go in the general settings of the POS app, and activate the Ingenico " "setting." -msgstr "" +msgstr "まず、POSアプリの一般設定を開き、Ingenico設定を有効にします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44 msgid "" @@ -5018,6 +5346,8 @@ msgid "" "new payment method for Ingenico, select the payment terminal option " "Ingenico, and select your payment terminal device." msgstr "" +"menuselection:`POS --> 設定 --> " +"POS`に戻り、支払セクションで支払方法にアクセスします。Ingenico用の新しい支払方法を作成し、決済端末オプションIngenicoを選択し、決済端末デバイスを選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 msgid "" @@ -5027,12 +5357,13 @@ msgid "" "*Send*. When the payment is successful, the status will change to *Payment " "Successful*." msgstr "" +"POSインターフェース*で、支払処理する際に、決済端末を使用する*支払方法*を選択します。入札欄の金額が決済端末に送信する金額であることを確認し、*送信*をクリックします。支払が成功すると、ステータスが*支払完了*に変わります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 msgid "" "If you want to cancel the payment request, click on cancel. You can still " "retry to send the payment request." -msgstr "" +msgstr "支払要求を取消したい場合は、取消をクリックして下さい。支払要求の送信を再試行することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:67 msgid "" @@ -5040,28 +5371,29 @@ msgid "" "payment using the *Force Done*. This will allow you to validate the order in" " Odoo even if the connection between the terminal and Odoo has issues." msgstr "" +"決済端末に問題がある場合でも、*強制完了*を使用して強制的に決済を行うことができます。これにより、端末とOdooの接続に問題がある場合でも、Odooでオーダを検証することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 msgid "" "This option will only be available if you received an error message telling " "you the connection failed." -msgstr "" +msgstr "このオプションは、接続に失敗したというエラーメッセージを受信した場合にのみ使用できます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:76 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 "" +msgstr "支払が処理されると、支払記録に使用されたカードの種類と取引IDが表示されます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 msgid "SIX" -msgstr "" +msgstr "SIX" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 msgid "" "Connecting a **SIX payment terminal** allows you to offer a fluid payment " "flow to your customers and ease the work of your cashiers." -msgstr "" +msgstr "**SIX決済端末**を接続することで、お客様にスムーズな支払フローを提供し、レジ係の作業を軽減することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 msgid "" @@ -5070,10 +5402,12 @@ msgid "" "received from Worldline are, therefore, not compatible with this " "integration." msgstr "" +"WorldlineがSIX Payment " +"Servicesを買収し、両社がYomaniの決済端末を使用しているにもかかわらず、両社のファームウェアは異なっています。したがって、Worldlineから受け取った端末は、この統合には対応していません。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17 msgid "Install the POS IoT Six module" -msgstr "" +msgstr "POS IoT Sixモジュールのインストール" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 msgid "" @@ -5081,14 +5415,16 @@ msgid "" ":guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds " "the necessary driver and interface to your database to detect Six terminals." msgstr "" +"POS IoT Sixモジュールを有効にするには、:guilabel:`アプリ`に行き、:guilabel:`アプリ` フィルタを削除し、**POS " +"IoT Six**を検索します。このモジュールはSix端末を検出するために必要なドライバとインターフェースをデータベースに追加します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24 msgid "This module replaces the **POS Six** module." -msgstr "" +msgstr "このモジュールは**POS Six**を置換ます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27 msgid "Connect an IoT box" -msgstr "" +msgstr "IoTボックスを接続" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 msgid "" @@ -5096,10 +5432,11 @@ msgid "" "Raspberry Pi or virtual (for Windows OS only) IoT box " "</applications/productivity/iot/config/connect>`." msgstr "" +"6つの決済端末をOdooに接続するには、:doc:`Raspberry Piまたは仮想(Windows OSのみ)IoTボックス`が必要です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 msgid "Configure the terminal ID" -msgstr "" +msgstr "端末IDの設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35 msgid "" @@ -5109,10 +5446,13 @@ msgid "" "with the ID received from Six, and click :guilabel:`Connect`. Your Six " "terminal ID should appear in the :guilabel:`Current Terminal Id` section." msgstr "" +"データベースサーバがIoTボックスに接続されたら、IoTボックスのホームページに移動し、 " +":guilabel:`Six決済端末`フィールドを見つけます。guilabel:`設定`をクリックし、:guilabel:`端末ID`フィールドにSixから受取ったIDを入力し、:guilabel:`接続`をクリックします。Sixの端末IDが" +" :guilabel:`現在の端末Id` セクションに表示されるはずです。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Setting the Six terminal ID" -msgstr "" +msgstr "Six端末IDを設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43 msgid "" @@ -5121,10 +5461,11 @@ msgid "" "detected and connected to the database. Check the IoT box homepage under the" " :guilabel:`Payments` section to confirm the connection." msgstr "" +"OdooはSix端末IDが設定されると自動的にIoTボックスを再起動します。Six端末がオンラインであれば、自動的に検出されデータベースに接続されます。IoTボックスのホームページの:guilabel:`支払`セクションで接続を確認して下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Confirming the connection to the Six payment terminal" -msgstr "" +msgstr "Six決済端末への接続を確認" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 msgid "" @@ -5135,10 +5476,14 @@ msgid "" ":guilabel:`SIX IOT`, and select the corresponding device in the " ":guilabel:`Payment Terminal Device` field." msgstr "" +"データベースから :menuselection:`POS--> 設定 --> 支払方法` " +"に進み、Six専用の新しい支払方法を作成します。guilabel:`新規`をクリックし、 :guilabel:`名前`を入力し、 " +":guilabel:`仕訳帳`フィールドを :guilabel:`銀行`に、 :guilabel:`決済端末を使用`フィールドを " +":guilabel:`SIX IOT`に設定し、 :guilabel:`決済端末デバイス`フィールドで対応するデバイスを選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Creating a new payment method for the SIX payment terminal" -msgstr "" +msgstr "SIX決済端末の新しい支払方法の作成" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:67 msgid "" @@ -5148,27 +5493,30 @@ msgid "" "Once the payment is successful, the status switches to :guilabel:`Payment " "Successful`." msgstr "" +"支払処理を行う場合、 :guilabel:`支払方法` セクションで :ref:`6つの支払方法<six/configure>` を選択し、 " +":guilabel:`送信` をクリックします。支払要求を取消するには、 :guilabel:`取消` をクリックします。支払が成功すると、ステータスが" +" :guilabel:`支払完了` に切替わります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 msgid "Paying with Six" -msgstr "" +msgstr "Sixで支払う" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:76 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 msgid "" "Once your payment is processed, the type of card used and the transaction ID" " appear on the payment record." -msgstr "" +msgstr "支払が処理されると、使用されたカードの種類と取引IDが支払記録に表示されます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:78 msgid "" "The language used for error messages is the same as the Six terminal. " "Configure the terminal to change the language or contact Six." -msgstr "" +msgstr "エラーメッセージに使用される言語はSix端末と同じです。端末を設定して言語を変更するか、Sixにお問い合わせ下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:80 msgid "By default, the port used by the Six terminal is `7784`." -msgstr "" +msgstr "デフォルトでSix端末に使用されているポートは`7784`です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83 msgid "" @@ -5176,6 +5524,7 @@ msgid "" "can still force the payment validation in Odoo using the :guilabel:`Force " "Done` button." msgstr "" +"決済端末とOdooの接続に問題がある場合でも、Odooの :guilabel:`強制完了` ボタンを使用して強制的に支払を完了させることができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3 msgid "Stripe" @@ -5186,6 +5535,7 @@ msgid "" ":doc:`Use Stripe as payment provider. " "<../../../../finance/payment_providers/stripe>`" msgstr "" +":doc:`決済プロバイダとしてStripeを使用。 <../../../../finance/payment_providers/stripe>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:17 msgid "" @@ -5193,10 +5543,11 @@ msgid "" "Sale --> Configuration --> Settings --> Payment Terminals` and enabling " ":guilabel:`Stripe`." msgstr "" +"menuselection:`POS --> 設定 --> 管理設定 --> 決済端末`を開き、 :guilabel:`Stripe`を有効にします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:20 msgid "Then, create the payment method:" -msgstr "" +msgstr "そして、支払方法を作成します:" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 msgid "" @@ -5204,28 +5555,32 @@ msgid "" "click :guilabel:`Create`, and complete the :guilabel:`Method` field with " "your payment method's name;" msgstr "" +"menuselection:`POS --> 設定 --> 支払方法`に進み、 :guilabel:`作成`をクリックし、 " +":guilabel:`方法`フィールドに支払方法の名前を入力します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:24 msgid "" "Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use" " a Payment Terminal` field as :guilabel:`Stripe`;" msgstr "" +"guilabel:`仕訳帳` フィールドを :guilabel:`銀行` に、 :guilabel:`決済端末を使用` フィールドを " +":guilabel:`Stripe` に設定します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:26 msgid "" "Enter your payment terminal serial number in the :guilabel:`Stripe Serial " "Number` field;" -msgstr "" +msgstr "guilabel:`Stripeシリアル番号`フィールドに決済端末のシリアル番号を入力します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:27 msgid "" "Click :guilabel:`Don't forget to complete Stripe connect before using this " "payment method.`" -msgstr "" +msgstr "guilabel:`この支払方法を使用する前に、Stripeの接続を忘れずに完了して下さい`をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 msgid "payment method creation form" -msgstr "" +msgstr "支払方法作成フォーム" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 msgid "" @@ -5234,22 +5589,26 @@ msgid "" "be able to pay with Stripe, leave the :guilabel:`Identify Customer` field " "unchecked." msgstr "" +"guilabel:`顧客を識別`をクリックすると、この支払方法を**識別された顧客にのみ**許可します。識別されていない顧客にもStripeでの支払を許可する場合は、" +" :guilabel:`顧客を識別` フィールドのチェックを外したままにします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:37 msgid "" "The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account`" " can stay empty to use the default accounts." msgstr "" +"guilabel:`未消込金勘定` と :guilabel:`中間勘定科目` はデフォルトの勘定科目を使用するために空のままにしておくことができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:39 msgid "" "Find your payment terminal serial number under the device or on `Stripe's " "dashboard <https://dashboard.stripe.com>`_." msgstr "" +"決済端末のシリアル番号は、端末の下、またはStripeのダッシュボード<https://dashboard.stripe.com>`_でご確認下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:43 msgid "Connect Stripe to Odoo" -msgstr "" +msgstr "StripeをOdooに接続" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:45 msgid "" @@ -5262,22 +5621,24 @@ msgid "" "corresponding fields in Odoo. Your terminal is ready to be configured in a " "POS." msgstr "" +"guilabel:`Stripeに接続`をクリックします。自動的に設定ページにリダイレクトされます。全ての情報を入力してStripeアカウントを作成し、Odooとリンクします。フォームの入力が完了すると、APIキー(:guilabel:`公開可能キー`と:guilabel:`秘密キー`)を**Stripeの**ウェブサイトで取得できます。これを行うには、:guilabel:`秘密キーと公開可能キーを入手`をクリックし、キーをクリックしてコピーし、Odooの対応するフィールドに貼り付けます。これでPOS端末の設定は完了です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 msgid "stripe connection form" -msgstr "" +msgstr "stripe接続フォーム" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:57 msgid "" "When you use **Stripe** exclusively in Point of Sale, you only need the " "**Secret Key** to use your terminal." -msgstr "" +msgstr "POSで**Stripe**を独占的に使用する場合、**秘密キー**だけで端末を使用できます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:59 msgid "" "When you use Stripe as **payment provider**, the :guilabel:`State` can stay " "set as :guilabel:`Disabled`." msgstr "" +"**決済プロバイダー**としてStripeを使用する場合、:guilabel:`ステータス`は:guilabel:`無効`のままにしておくことができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:61 msgid "" @@ -5286,34 +5647,37 @@ msgid "" "dashboard <https://dashboard.stripe.com>`_, type `API` in the search bar, " "and click :guilabel:`Developers > API`." msgstr "" +"**オンプレミス**でホストされているデータベースの場合、:guilabel:`Stripeに接続`ボタンは機能しません。APIキーを手動で取得するには、" +" `Stripeダッシュボード <https://dashboard.stripe.com>`_ にログインし、検索バーに `API` と入力して " +":guilabel:`開発者 > API` をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:67 msgid "Configure the payment terminal" -msgstr "" +msgstr "決済端末の設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:69 msgid "" "Swipe right on your payment terminal, click :guilabel:`Settings`, enter the " "admin PIN code, validate and select your network." -msgstr "" +msgstr "決済端末を右にスワイプし、:guilabel:`管理設定`をクリックし、管理者用PINコードを入力し、認証してネットワークを選択します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:73 msgid "The device must be connected to a secured WI-FI network." -msgstr "" +msgstr "デバイスは安全なWI-FIネットワークに接続されている必要があります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 msgid "Your Odoo database and payment terminal must share the same network." -msgstr "" +msgstr "Odooデータベースと決済端末は同じネットワークを共有している必要があります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:75 msgid "" "You must enter the admin PIN code to access your payment terminal settings. " "By default, this code is `07139`." -msgstr "" +msgstr "決済端末の設定にアクセスするには、管理者用PINコードを入力する必要があります。デフォルトでは、このコードは`07139`です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:79 msgid "Link the payment method to a POS" -msgstr "" +msgstr "支払方法をPOSにリンクする" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 msgid "" @@ -5322,6 +5686,9 @@ msgid "" "POS, scroll down to the :guilabel:`Payments` section, and add your payment " "method for **Stripe** in the :guilabel:`Payment Methods` field." msgstr "" +"POSに**支払方法**を追加するには、 :menuselection:`POS --> 設定 --> 管理設定`に進みます。POSを選択し、 " +":guilabel:`支払`セクションまでスクロールダウンし、 " +":guilabel:`支払方法`フィールドに**Stripe**用の支払方法を追加します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 msgid "" @@ -5330,46 +5697,51 @@ msgid "" " the status changes to :guilabel:`Payment Successful`. To cancel the payment" " request, click :guilabel:`cancel`." msgstr "" +"支払を処理する場合、支払方法として :guilabel:`Stripe` を選択します。金額を確認し、 :guilabel:`送信` " +"をクリックします。支払が成功すると、ステータスが :guilabel:`支払完了` に変わります。支払要求を取消するには、 :guilabel:`取消`" +" をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:97 msgid "The terminal must have at least 10% battery level to use it." -msgstr "" +msgstr "この端末を使用するには、バッテリー残量が少なくとも10%以上必要です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:98 msgid "The device does not work for payments under €0.50." -msgstr "" +msgstr "このデバイスは0.50ユーロ以下の支払には使用できません。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:101 msgid "Troubleshooting" -msgstr "" +msgstr "トラブルシューティング" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 msgid "Payment terminal unavailable in your Stripe account" -msgstr "" +msgstr "Stripeアカウントで決済端末が利用できません" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:106 msgid "" "If the payment terminal is unavailable in your Stripe account, you must add " "it manually:" -msgstr "" +msgstr "決済端末がStripeアカウントにない場合は、手動で追加する必要があります:" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 msgid "" "Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to" " :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;" msgstr "" +"Stripeのダッシュボード<https://dashboard.stripe.com>`_にログインし、:menuselection:`Stripeダッシュボード" +" --> 支払 --> リーダー --> ロケーション`に進みます;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:110 msgid "" "Add a location by clicking the :guilabel:`+ New` button or selecting an " "already created location;" -msgstr "" +msgstr "guilabel:`+新規`ボタンをクリックするか、すでに作成されている場所を選択して場所を追加します;" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 msgid "" "Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill " "in the required information." -msgstr "" +msgstr "guilabel:`リーダー`ボックスの :guilabel:`+ 新規`ボタンをクリックし、必要な情報を入力します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 msgid "" @@ -5377,22 +5749,24 @@ msgid "" " on your device, enter the admin PIN code (by default: `07139`), validate, " "and click :guilabel:`Generate a registration code`." msgstr "" +"**登録コード**を入力する必要があります。そのコードを取得するには、デバイスを右にスワイプし、管理者用PINコード(デフォルト：`07139`)を入力し、有効にして" +" :guilabel:`登録コードを生成` をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 msgid "Vantiv" -msgstr "" +msgstr "Vantiv" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 "" +msgstr "Vantivの決済端末を接続することで、顧客にスムーズな支払フローを提供し、レジ係の作業を軽減することができます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 msgid "" "Please note MercuryPay only operates with US and Canadian banks, making this" " procedure only suitable for North American businesses." -msgstr "" +msgstr "MercuryPayは米国およびカナダの銀行のみと提携しているため、この手続きは北米の企業のみに適しています。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 msgid "" @@ -5400,16 +5774,17 @@ msgid "" "Vantiv terminals bought on Amazon do not include the correct encryption " "needed to be used with an Odoo database." msgstr "" +"VantivカードリーダーはVantiv社から購入する必要があります。Amazonで購入したVantiv端末の中には、Odooデータベースで使用するために必要な正しい暗号化が含まれていないものがあるからです。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 msgid "Configure the Payment Method" -msgstr "" +msgstr "支払方法を設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 msgid "" "First, go in the general settings of the POS app, and activate the Vantiv " "setting." -msgstr "" +msgstr "まず、POSアプリの一般設定を開き、Vantiv設定を有効にします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 msgid "" @@ -5418,6 +5793,8 @@ msgid "" "payment method for Vantiv, select the payment terminal option Vantiv, and " "create new Vantiv credentials." msgstr "" +"menuselection:`POS --> 設定 --> " +"POS`に戻り、支払セクションで支払方法にアクセスします。Vantiv用の新規支払方法を作成し、決済端末オプションのVantivを選択し、新しいVantiv認証情報を作成します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 msgid "" @@ -5425,16 +5802,17 @@ msgid "" "then save. Make sure the credentials you just created are selected, then " "save the payment method." msgstr "" +"新しいVantiv認証情報を作成するには、マーチャントIDとパスワードを入力し、保存します。作成した認証情報が選択されていることを確認し、支払方法を保存します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 msgid "Pay with a Payment Terminal" -msgstr "" +msgstr "決済端末で支払う" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 msgid "" "In your PoS interface, at the moment of the payment, select your Vantiv " "payment method and… that’s all." -msgstr "" +msgstr "POSインターフェイスで、支払時にVantivの支払方法を選択するだけです。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 msgid "Worldline" @@ -5442,7 +5820,7 @@ msgstr "Worldline" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 msgid "Please note that Worldline is currently only available in the Benelux." -msgstr "" +msgstr "Worldlineは現在ベネルクス諸国でのみご利用いただけます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 msgid "" @@ -5451,10 +5829,12 @@ msgid "" "please refer to the :doc:`IoT documentation " "</applications/productivity/iot/config/connect>`." msgstr "" +"Worldline決済ターミナルをOdooに接続するには、IoTボックスが必要です。IoTボックスをデータベースに接続する方法については、:doc:`IoT" +" documentation'をご参照下さい</applications/productivity/iot/config/connect>`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22 msgid "Configure the protocol" -msgstr "" +msgstr "プロトコルを設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24 msgid "" @@ -5465,10 +5845,14 @@ msgid "" "screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). " "Finally, press **Stop** three times; the terminal automatically restarts." msgstr "" +"ターミナルから :menuselection:`\".\" をクリックします。--> 3 --> 停止 --> 3 --> 0 --> 9`. " +"技術者のパスワード **\"1235789\"** を入力し、 :menuselection:`OK --> 4 --> 2` をクリックします。次に " +":menuselection:`変更 --> CTEP (プロトコルECRとして) --> OK` " +"をクリックします。その後の画面（*CTEPチケットECR*、*ECRチケット幅*、*文字セット*）で**OK**を3回クリックします。最後に**停止**を3回押すと、端末は自動的に再起動します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:31 msgid "Set the IP address" -msgstr "" +msgstr "IPアドレスの設定" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33 msgid "" @@ -5478,44 +5862,51 @@ msgid "" "TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK`" " (*TCP Configuration client* screen)." msgstr "" +"ターミナルから :メニュー選択:`\".\" をクリックします。--> 3 --> 停止 --> 3 --> 0 --> 9`. 技術者のパスワード " +"**\"1235789\"** を入力し、 :menuselection:`OK --> 4 --> 9` をクリックします。次に、 " +":menuselection:`変更 --> TCP/IP`（*TCP物理設定*画面） :メニュー選択:`--> OK --> " +"OK`(*TCP設定クライアント*画面)をクリックします。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:38 msgid "Finally, set up the hostname and port number." -msgstr "" +msgstr "最後に、ホスト名とポート番号を設定します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41 msgid "Hostname" -msgstr "" +msgstr "ホスト名" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44 msgid "" "To set up the hostname, enter your IoT box's IP address' sequence numbers " "and press **OK** at each \".\" until you reach the colon symbol." msgstr "" +"ホスト名を設定するには、IoTボックスのIPアドレスのシーケンス番号を入力し、コロン記号に達するまで、それぞれの\". \"で**OK**を押します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 msgid "Then, press **OK** twice." -msgstr "" +msgstr "そして **OK** を2回押します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 msgid "Here's an IP address sequence: `10.30.19.4:8069`." -msgstr "" +msgstr "IPアドレスシーケンス: `10.30.19.4:8069`です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 msgid "" "On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> " "19 --> OK --> 4 --> OK --> OK`." msgstr "" +"*ホスト名画面*で、:menuselection:`10 --> OK --> 30 --> OK --> 19 --> OK --> 4 --> OK" +" --> OK`と入力します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:53 msgid "" "Your IoT box's IP address is available in your IoT Box application's " "database." -msgstr "" +msgstr "IoTボックスのIPアドレスは、IoTボックスアプリケーションのデータベースで利用可能です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:56 msgid "Port number" -msgstr "" +msgstr "ポート番号" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58 msgid "" @@ -5523,6 +5914,9 @@ msgid "" "click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> " "OK`. Click on **Stop** three times; the terminal automatically restarts." msgstr "" +"*ポート番号*画面で**9001**(Windowsの場合は**9050**)と入力し、 :menuselection:`OK` " +"(*ECRプロトコルSSLなし*) :menuselection:`--> " +"OK`をクリックします。**停止**を3回クリックすると、端末が自動的に再起動します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:65 msgid "" @@ -5530,6 +5924,8 @@ msgid "" "Settings --> Payment terminals` and activate the *Worldline* payment " "terminal." msgstr "" +"POSアプリケーションから、:menuselection:`設定 --> 管理設定 --> " +"決済端末`に進み、*Worldline*決済端末を有効化します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:71 msgid "" @@ -5537,32 +5933,36 @@ msgid "" "new payment method for *Worldline*. Select the payment terminal *Worldline* " "and your payment terminal device on your *Payment Method form*." msgstr "" +"次に、:menuselection:`設定 --> " +"支払方法`に進み、*Worldline*用の新しい支払方法を作成します。*支払方法フォーム*で、決済端末機*Worldline*と決済端末デバイスを選択して下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:78 msgid "Technician password: `1235789`" -msgstr "" +msgstr "技術者パスワード: `1235789`" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:79 msgid "" "To reach Wordline's technical assistance, call `02 727 61 11` and choose " "\"merchant\". Your call is automatically transferred to the desired service." msgstr "" +"Wordlineの技術アシスタンスに連絡するには、`02 727 61 11`に電話し、 " +"\"加盟店\"を選択して下さい。電話は自動的にご希望のサービスに転送されます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 msgid "" "Configure the cashier terminal if you have both a customer and a cashier " "terminal." -msgstr "" +msgstr "顧客端末とレジ端末の両方がある場合は、レジ端末を設定します。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:82 msgid "" "To avoid blocking the terminal, check the initial configuration beforehand." -msgstr "" +msgstr "端末がブロックされるのを避けるため、事前に初期設定を確認して下さい。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83 msgid "" "Set a fixed IP to your IoT Box’s router to prevent losing the connexion." -msgstr "" +msgstr "IoT Boxのルーターに固定IPを設定し、接続が切れるのを防ぎます。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 msgid "" @@ -5570,6 +5970,7 @@ msgid "" "amount and click on *Send*. Once the payment is successful, the status " "changes to *Payment Successful*." msgstr "" +"支払手続きをする際、支払方法として*Worldline*を選択します。金額を確認し、*送信*をクリックします。支払が完了すると、ステータスが*支払完了*に変わります。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 msgid "" @@ -5578,14 +5979,15 @@ msgid "" "order. This option is only available after receiving an error message " "informing you that the connection failed." msgstr "" +"Odooと決済端末間の接続に問題がある場合、*強制完了*をクリックして強制的に支払を実行し、オーダを検証することができます。このオプションは、接続に失敗したというエラーメッセージが表示された場合のみ有効です。" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 msgid "To cancel the payment request, click on **cancel**." -msgstr "" +msgstr "支払要求を取消するには、**cancel**をクリックして下さい。" #: ../../content/applications/sales/point_of_sale/pricing.rst:5 msgid "Pricing features" -msgstr "" +msgstr "価格設定機能" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 msgid "Cash rounding" @@ -5608,48 +6010,48 @@ msgstr "例えば、現金払いの場合、請求書の合計金額を5セン msgid "" "Each point of sale in Odoo can be configured to apply cash rounding to the " "totals of its bills or receipts." -msgstr "" +msgstr "Odooの各POSは、請求書または領収書の合計に現金丸めを適用するように設定できます。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Settings` and " "enable *Cash Rounding*, then click on *Save*." -msgstr "" +msgstr "menuselection:`POS --> 設定 --> 管理設定`に行き、*現金丸め*を有効にし、*保存*をクリックします。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 msgid "" "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " "open the point of sale you want to configure, and enable the *Cash Rounding*" " option." -msgstr "" +msgstr "menuselection:`POS --> 設定 --> POS`に行き、設定したいPOSを開き、*現金丸め*オプションを有効にします。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 msgid "" "To define the **Rounding Method**, open the drop-down list and click on " "*Create and Edit...*." -msgstr "" +msgstr "*丸め方法**を定義するには、ドロップダウンリストを開き、*作成と編集...*をクリックします。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 msgid "" "Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*," " then save both the Rounding Method and your Point of Sale settings." -msgstr "" +msgstr "ここで*丸め精度*、*利益勘定*、*損失勘定*を定義し、丸め方法とPOS設定の両方を保存します。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 msgid "" "All total amounts of this point of sale now add a line to apply the rounding" " according to your settings." -msgstr "" +msgstr "このPOSの全ての合計金額には、設定に従って丸めを適用する行が追加されます。" #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 msgid "" "Odoo Point of Sale only supports the :guilabel:`Add a rounding line` " "rounding strategy." -msgstr "" +msgstr "Odoo POSは :guilabel:`丸め明細を追加する` 丸め方法のみをサポートしています。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 msgid "Discount tags (barcode scanner)" -msgstr "" +msgstr "値引きタグ(バーコードスキャナ)" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 msgid "" @@ -5657,10 +6059,11 @@ msgid "" "close to its expiration date for example, you can use discount tags. They " "allow you to scan discount barcodes." msgstr "" +"賞味期限が迫っている商品などを値引きして販売したい場合、値引きタグを使うことができます。それにより値引きバーコードをスキャンすることができます。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 msgid "To use discount tags you will need to use a barcode scanner." -msgstr "" +msgstr "値引きタグを使用するには、バーコードスキャナを使用する必要があります。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 msgid "Barcode Nomenclature" @@ -5668,19 +6071,19 @@ msgstr "バーコード表現規則" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 msgid "To use discounts tags, we need to learn about barcode nomenclature." -msgstr "" +msgstr "値引タグを使うには、バーコードの命名法について学んで下さい。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 msgid "" "Let's say you want to have a discount for the product with the following " "barcode:" -msgstr "" +msgstr "例えば、次のようなバーコードのプロダクトに値引を適用したいとします:" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 msgid "" "You can find the *Default Nomenclature* under the settings of your PoS " "interface." -msgstr "" +msgstr "*デフォルト命名法*は、PoSインターフェースの管理設定の下にあります。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 msgid "" @@ -5688,20 +6091,21 @@ msgid "" "with 22 (for the discount barcode nomenclature) and then 50 (for the %) " "before adding the product barcode. In our example, the barcode would be:" msgstr "" +"例えば、あるプロダクトを50％値引にしたい場合、バーコードの先頭に22(割引バーコードの命名法)を付け、次に50(％)を付けてからプロダクトバーコードを追加する必要があります。この例では、バーコードは次のようになります:" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 msgid "Scan the products & tags" -msgstr "" +msgstr "プロダクトとタグをスキャンする" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 msgid "You first have to scan the desired product (in our case, a lemon)." -msgstr "" +msgstr "まず、対象プロダクト(この場合はレモン)をスキャンする必要があります。" #: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 msgid "" "And then scan the discount tag. The discount will be applied and you can " "finish the transaction." -msgstr "" +msgstr "そして値引タグをスキャンする。値引が適用され、取引が完了します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 msgid "Discounts" @@ -5713,91 +6117,92 @@ msgid "" "increase your revenue. It is vital to offer discounts, whether they are " "time-limited, seasonal or manually given." msgstr "" +"値引を提供することで、顧客を魅了し、収益を飛躍的に増加させることができます。期間限定であれ、季節限定であれ、手作業であれ、値引の提供は重要です。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 msgid "" "To manage discounts, Odoo has powerful features that help set up a pricing " "strategy tailored to every business." -msgstr "" +msgstr "値引を管理するために、Odooは各ビジネスに合わせた価格戦略を設定するのに役立つ強力な機能を備えています。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 msgid "Apply manual discounts" -msgstr "" +msgstr "手動値引を適用する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 msgid "" "If you seldom use discounts, applying manual ones might be the easiest " "solution for your Point of Sale." -msgstr "" +msgstr "めったに値引を使用しないのであれば、手動の値引を適用するのがPOSシステムにとって最も簡単な解決策かもしれません。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 msgid "" "You can either apply a discount on the whole order or on specific products " "inside an order." -msgstr "" +msgstr "オーダ全体またはオーダ内の特定のプロダクトに対して値引を適用することができます。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 msgid "Apply a discount on a product" -msgstr "" +msgstr "プロダクトに値引を適用する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 msgid "From your PoS session interface, use the *Disc* button." -msgstr "" +msgstr "POSセッションインターフェイスから、*値引*ボタンを使用します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the discount button for manual discount" -msgstr "" +msgstr "手動値引の値引ボタンのビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 msgid "" "Then, you can input a discount over the product that is currently selected." -msgstr "" +msgstr "そして、現在選択されているプロダクトに割引を入力することができます。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 msgid "Apply a global discount" -msgstr "" +msgstr "全体値引を適用する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 msgid "" "To apply a discount on the whole order, go to :menuselection:`Point of Sales" " --> Configuration --> Point of Sale` and select your PoS." -msgstr "" +msgstr "オーダ全体に値引を適用するには、:menuselection:`POS --> 設定 --> POS`に進み、POSを選択します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 msgid "" "Once on your PoS form, select *Global Discounts*, under the *Pricing* " "category." -msgstr "" +msgstr "POSフォームで、*価格設定*カテゴリの下にある*全体値引*を選択します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the feature to enable for global discount" -msgstr "" +msgstr "全体値引の機能ビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 msgid "Now, you have a new *Discount* button appearing on your PoS interface." -msgstr "" +msgstr "これで、POSインターフェイスに新しい*値引*ボタンが表示されました。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the button to use for global discount via the pos interface" -msgstr "" +msgstr "POSインターフェイスで全体値引に使用するボタンのビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 msgid "Click on it and enter the wanted discount." -msgstr "" +msgstr "クリックして、希望の値引を入力します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the discount offered in the payment summary" -msgstr "" +msgstr "支払概要で提供される値引のビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 msgid "" "On this example, there is a global discount of 50% as well as a specific 50%" " discount on oranges." -msgstr "" +msgstr "この例では、50％の全体値引と、オレンジに対する特定の50％値引があります。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 msgid "Apply time-limited discounts" -msgstr "" +msgstr "時間限定値引を適用する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 msgid "" @@ -5805,20 +6210,22 @@ msgid "" "feature. To do so, go to :menuselection:`Point of Sales --> Configuration " "--> Point of Sale` and open your PoS. Then, enable the pricelist feature." msgstr "" +"期間限定値引を有効にするには、*価格表* 機能を有効にする必要があります。これを行うには、 :menuselection:`POS --> 設定 -->" +" POS`に行き、POSを開きます。次に、価格表機能を有効にします。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of the pricelist feature" -msgstr "" +msgstr "価格表機能のビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 msgid "" "Once activated, you must choose the pricelists you want to make available in" " the PoS and define a default one." -msgstr "" +msgstr "有効化したら、POSで利用可能にしたい価格表を選択し、デフォルトの価格表を定義する必要があります。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 msgid "Create a pricelist" -msgstr "" +msgstr "価格表を作成する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 msgid "" @@ -5826,6 +6233,8 @@ msgid "" ":menuselection:`Point of Sale --> Products --> Pricelists`. Then click on " "create." msgstr "" +"デフォルトでは、Odooには*公開価格表*が設定されています。さらに作成するには、 :menuselection:`POS --> プロダクト --> " +"価格表`にアクセスして下さい。次に作成をクリックします。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 msgid "" @@ -5833,56 +6242,57 @@ msgid "" "price: period, min. quantity, etc. You can also decide to apply that " "pricelist on specific products or on the whole range." msgstr "" +"価格表を作成する際、特定の価格を使用するためにいくつかの条件を設定することができます:期間、最小数量など。また、その価格表を特定のプロダクトに適用するか、全プロダクトに適用するかも設定できます。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "View of a time-limited pricelist for two products" -msgstr "" +msgstr "2つのプロダクトの期間限定価格表のビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 msgid "Using a pricelist with the PoS interface" -msgstr "" +msgstr "POSインターフェイスで価格表を使用する" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 msgid "" "On the PoS interface, a new button appears. Use it to select a pricelist." -msgstr "" +msgstr "PoSインターフェイスに新しいボタンが表示されます。これを使って価格表を選択します。" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 msgid "" "View of the button to use for time-limited discounts via the pos interface" -msgstr "" +msgstr "POSインターフェイスで期間限定値引に使用するボタンのビュー" #: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 msgid "" "Click on it to instantly update the prices with the selected pricelist. " "Then, you can finalize the order." -msgstr "" +msgstr "それをクリックすると、選択した価格表で価格が即座に更新されます。その後、オーダを確定することができます。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 msgid "Flexible taxes (fiscal positions)" -msgstr "" +msgstr "柔軟な税(会計ポジション)" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 msgid "" "When running a business, you may need to apply different taxes and record " "transactions on various accounts based on the location and type of business " "of your customers and providers." -msgstr "" +msgstr "ビジネスを運営する場合、顧客や取引先の所在地や業種によって、様々な税金を適用したり、様々な勘定科目で取引を記録したりする必要があります。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:8 msgid "" "The **fiscal positions** feature enables you to establish rules that " "automatically select the right taxes and accounts used for each transaction." -msgstr "" +msgstr "**会計ポジション**機能により、各取引に使用される適切な税金と勘定科目を自動的に選択する規則を設定することができます。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:12 #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:51 msgid ":doc:`../../../finance/accounting/taxes/fiscal_positions`" -msgstr "" +msgstr ":doc:`../../../finance/accounting/taxes/fiscal_positions`" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 msgid ":doc:`../../../finance/accounting/taxes`" -msgstr "" +msgstr ":doc:`../../../finance/accounting/taxes`" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:18 msgid "" @@ -5890,6 +6300,8 @@ msgid "" " --> Settings`, scroll down to the :guilabel:`Accounting` section, and " "enable :guilabel:`Flexible Taxes`." msgstr "" +"この機能を有効にするには、 :menuselection:`POS --> 設定 --> 管理設定` に行き、 :guilabel:`会計` " +"セクションまでスクロールダウンし、 :guilabel:`柔軟な税` を有効にします。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 msgid "" @@ -5897,6 +6309,8 @@ msgid "" "the selected POS in the :guilabel:`Default` field. You can also add more " "fiscal positions to choose from in the :guilabel:`Allowed` field." msgstr "" +"次に、 :guilabel:`デフォルト`フィールドに、選択したPOSの全ての売上に適用されるデフォルトの会計ポジションを設定します。また、 " +":guilabel:`許可済` フィールドに選択する会計ポジションを追加することもできます。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:28 msgid "" @@ -5905,16 +6319,19 @@ msgid "" " are preconfigured and can be set and used in POS. However, you can also " ":ref:`create new fiscal positions <fiscal_positions/mapping>`." msgstr "" +"doc:`会計ローカライゼーションパッケージ <../../../finance/fiscal_localizations>` " +"を有効にすると、いくつかの会計ポジションがあらかじめ設定され、POSで設定・使用できるようになります。しかし、 :ref:`新規会計ポジションを作成 " +"<fiscal_positions/mapping>`することもできます。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 msgid "" "If you do not set a fiscal position, the tax remains as defined in the " "**customer taxes** field on the product form." -msgstr "" +msgstr "会計ポジションを設定しない場合、税金はプロダクトフォームの**顧客税**フィールドで定義されたままとなります。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:37 msgid "Use fiscal positions" -msgstr "" +msgstr "会計ポジションを使用する" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:39 msgid "" @@ -5924,22 +6341,25 @@ msgid "" "the defined rules automatically to all the products subject to the chosen " "fiscal position's regulations." msgstr "" +"ref:`POSセッション<pos/session-" +"start>`を開き、許可された会計ポジションの一つを使用します。次に、**本型**アイコンの横にある :guilabel:`税` " +"ボタンをクリックし、リストから会計ポジションを選択します。そうすることで、選択された会計ポジションの規制の対象となる全てのプロダクトに、定義された規則が自動的に適用されます。" #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:48 msgid "" "If a default fiscal position is set, the tax button displays the name of the" " fiscal position." -msgstr "" +msgstr "デフォルトの会計ポジションが設定されている場合、税金ボタンは会計ポジションの名前を表示します。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 msgid "Loyalty programs" -msgstr "" +msgstr "ロイヤリティプログラム" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 msgid "" "Encourage your customers to continue to shop at your point of sale with a " "*Loyalty Program*." -msgstr "" +msgstr "*ロイヤリティプログラム*で、顧客に継続的な買い物を促しましょう。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 msgid "" @@ -5947,10 +6367,12 @@ msgid "" "Sale --> Configuration --> Point of sale` and select your PoS interface. " "Under the Pricing features, select *Loyalty Program*" msgstr "" +"*ロイヤリティプログラム*機能を有効にするには、 :menuselection:`POS --> 設定 --> " +"POS`に進み、POSインターフェイスを選択して下さい。価格設定機能の下で、*ロイヤリティプログラム*を選択します。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 msgid "From there you can create and edit your loyalty programs." -msgstr "" +msgstr "そこからロイヤリティプログラムを作成・編集することができます。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 msgid "" @@ -5959,10 +6381,11 @@ msgid "" "range. Apply rules so that it is only valid in specific situation and " "everything in between." msgstr "" +"どのようなタイプのプログラムにするか、報酬を割引にするかギフトにするか、特定のプロダクトに限定するか全プロダクトを対象にするか、など自由に決めることができます。特定のシチュエーションでのみ有効であるような規則を適用したり、その中間の全てを適用することもできます。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 msgid "Use the loyalty program in your PoS interface" -msgstr "" +msgstr "POSインターフェイスでロイヤリティプログラムを利用する" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 msgid "" @@ -5971,18 +6394,19 @@ msgid "" "using the button *Rewards* when they have enough points according to the " "rules defined in the loyalty program." msgstr "" +"顧客が設定されると、その取引で得られるポイントが表示され、使用されるまで蓄積されます。ポイントは、ロイヤリティプログラムで定義された規則に従って十分なポイントが貯まったら、*報酬*ボタンを使って使用します。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 msgid "" "You can see the price is instantly updated to reflect the pricelist. You can" " finalize the order in your usual way." -msgstr "" +msgstr "価格は即座に価格表を反映したものに更新されます。いつもの方法でオーダを確定することができます。" #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 msgid "" "If you select a customer with a default pricelist, it will be applied. You " "can of course change it." -msgstr "" +msgstr "デフォルトの価格表を持つ顧客を選択した場合、その価格表が適用されます。もちろん変更することもできます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 @@ -5997,6 +6421,7 @@ msgid "" "temporary discount periods, reward specific customers, or offer discounts " "when set quantities are ordered." msgstr "" +"価格表を使用すると、様々な条件に応じてプロダクト価格を自動的に調整することができます。例えば、POS固有の価格を設定したり、一時的な値引期間を設けたり、特定の顧客に報酬を与えたり、設定された数量がオーダされたときに値引を提供したりすることができます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:14 msgid "" @@ -6004,6 +6429,8 @@ msgid "" " ensure :guilabel:`Flexible Pricelists` are enabled under the " ":guilabel:`Pricing` section." msgstr "" +"ref:`一般POSアプリ管理設定 <configuration/settings>` に移動し、 :guilabel:`価格設定` セクションで " +":guilabel:`柔軟な価格表` が有効になっていることを確認します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 msgid "" @@ -6014,10 +6441,11 @@ msgid "" "dynamically using percentage discounts or more complex formulas in addition " "to setting fixed prices." msgstr "" +":ref:`プロダクト毎に複数価格<pricelists/simple>`は、プロダクトごとに単純な固定価格ルールを設定するためのデフォルトの価格表オプションです。ref:`高度な価格規則(値引、計算式)<pricelists/advanced>`を選択すると、一度に複数のプロダクトに価格規則を適用し、固定価格の設定に加えて、パーセンテージ値引やより複雑な計算式を使って動的に価格を計算することができます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Enabling pricelists in the general P0S settings" -msgstr "" +msgstr "一般P0S管理設定で価格表を有効にする" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 msgid "" @@ -6025,10 +6453,12 @@ msgid "" ":doc:`Sales <../../sales/products_prices/prices/pricing>` and " ":ref:`eCommerce <ecommerce/pricelists>` apps." msgstr "" +"選択した価格表のタイプは、 :doc:`販売 <../../sales/products_prices/prices/pricing>` と " +":ref:`eコマース <ecommerce/pricelists>` のアプリを含むデータベース全体に適用されます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 msgid "Create pricelists" -msgstr "" +msgstr "価格表を作成する" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:35 msgid "" @@ -6037,6 +6467,9 @@ msgid "" " depending on the :ref:`selected pricelist option " "<pricelists/configuration>`." msgstr "" +"menuselection:`POS --> プロダクト --> 価格表`に進み、 " +":guilabel:`新規`をクリックするか、既存の価格表を選択します。価格表の設定は :ref:`選択済価格表オプション " +"<pricelists/configuration>` によって異なります。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 @@ -6050,43 +6483,45 @@ msgid "" "products or their variants depending, if necessary, on one or several " "conditions. To add a new price rule to a pricelist:" msgstr "" +"価格表が :guilabel:`プロダクト毎に複数価格` " +"オプションを使用するように設定されている場合、必要に応じて、1つまたは複数の条件によって、異なるプロダクトまたはそのバリエーションに複数の固定価格を使用することができます。価格表に新しい価格規則を追加するには:" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48 msgid "" "Click :guilabel:`Add a line`, and select a **product** and its **variant** " "if needed." -msgstr "" +msgstr "guilabel:`明細を追加`をクリックし、必要であれば**プロダクト**とその**バリエーション**を選択します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:49 msgid "Add the condition(s):" -msgstr "" +msgstr "条件を追加:" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:51 msgid "" "a product quantity to be reached by using the :guilabel:`Min. Quantity` " "column;" -msgstr "" +msgstr ":guilabel:`最小数量`列を使用することで到達するプロダクト数量;" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:52 msgid "" "a determined period during which the pricelist is applied by using the " ":guilabel:`Start Date` and :guilabel:`End Date` columns." -msgstr "" +msgstr "guilabel:`開始日`列と :guilabel:`終了日`列を使用して、価格表が適用される期間を決定します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:55 msgid "" "Add the :guilabel:`Price` to be applied when the conditions are met (if " "any)." -msgstr "" +msgstr "条件が満たされたときに適用される :guilabel:`価格` を追加します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Setup form of a multiple prices pricelist" -msgstr "" +msgstr "複数価格の価格表の設定フォーム" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:312 msgid "Advanced price rules" -msgstr "" +msgstr "高度な価格規則" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:65 msgid "" @@ -6096,22 +6531,25 @@ msgid "" "new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up " "windows:" msgstr "" +"価格表が :guilabel:`高度な価格規則 (値引き、計算式)` " +"オプションを使用するように設定されている場合、固定価格だけでなく、パーセンテージ値引/値上や計算式を使用することができます。価格表に新しい価格規則を追加するには、" +" :guilabel:`明細を追加` をクリックします。ポップアップウィンドウで:" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:69 msgid "Select a :guilabel:`Computation` method:" -msgstr "" +msgstr "guilabel:`計算` 方法を選択します:" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:71 msgid "" ":guilabel:`Fixed Price` to set a new fixed price (similarly to the " ":guilabel:`Multiple prices per product` option)." -msgstr "" +msgstr ":guilabel:`固定価格`で新しい固定価格を設定します(:guilabel:`プロダクト毎に複数価格`オプションと同様です)" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73 msgid "" ":guilabel:`Discount` to compute a percentage discount (e.g., `10.00` %) or " "mark-up (e.g., `-10.00` %)." -msgstr "" +msgstr ":guilabel:`値引` でパーセント値引(例: `10.00` %)または値上(例: `-10.00` %)を計算します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:75 msgid "" @@ -6119,16 +6557,19 @@ msgid "" "required to define what the calculation is **based on** (:guilabel:`Sales " "Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:" msgstr "" +":guilabel:`計算式` " +"を使用すると、計算式に従って価格を計算することができます。この場合、**何を基準に**計算するのかを定義する必要があります(:guilabel:`販売価格`," +" :guilabel:`原価`, :guilabel:`その他の価格表`)。そうすると" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:79 msgid "Apply a percentage :guilabel:`Discount` or mark-up." -msgstr "" +msgstr "パーセンテージ :guilabel:`割引` または値上を適用します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:80 msgid "" "Add an :guilabel:`Extra Fee` (e.g., $ `5.00`) or subtract a fixed amount " "(e.g., $ `-5.00`)." -msgstr "" +msgstr " :guilabel:`追加料金` (例, $ `5.00`)を追加または定額を差引ます (例., $ `-5.00`)。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:81 msgid "" @@ -6136,38 +6577,44 @@ msgid "" ":guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra" " Fee` is applied afterward." msgstr "" +":guilabel:`値引` の後の価格を強制的に設定値の倍数にすることで、 :doc:`丸め方法 ` を定義します。その後に " +":guilabel:`追加料金` が適用されます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:86 msgid "" "To have the final price end with `.99`, set the :guilabel:`Rounding Method` " "to `1.00` and the :guilabel:`Extra Fee` to `-0.01`." msgstr "" +"最終価格を `.99` で終わらせるには、 :guilabel:`丸め方法` を `1.00` に、 :guilabel:`追加料金` を " +"`-0.01` に設定します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89 msgid "" "Specify the minimum (e.g., $ `20.00` ) and maximum (e.g., $ `50.00` ) profit" " :guilabel:`Margins` for computations based on :guilabel:`Cost`." msgstr "" +" :guilabel:`guilabel:`原価`に基づいて計算される :guilabel:`マージン`の最小値 ($ `20.00` など) と最大値" +" ($ `50.00` など)利益 を指定します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:92 msgid "Select on which product(s) the price rule should be **applied**:" -msgstr "" +msgstr "価格規則を**適用する**プロダクトを選択します:" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:94 msgid ":guilabel:`All Products`" -msgstr "" +msgstr ":guilabel:`全てのプロダクト`" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:95 msgid "a :guilabel:`Product Category`" -msgstr "" +msgstr " :guilabel:`プロダクトカテゴリ`" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:96 msgid "a :guilabel:`Product`" -msgstr "" +msgstr "a :guilabel:`プロダクト`" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:97 msgid "a :guilabel:`Product Variant`" -msgstr "" +msgstr " :guilabel:`プロダクトバリアント`" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:99 msgid "" @@ -6176,14 +6623,15 @@ msgid "" "which the pricelist should be applied by using the :guilabel:`Validity` " "fields." msgstr "" +"guilabel:`最小数量`フィールドを使用して、価格を変更するために到達すべき特定の数量などの条件や、:guilabel:`有効性`フィールドを使用して、価格表を適用する期間を指定することができます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Setup form to configure an advanced pricelist" -msgstr "" +msgstr "高度な価格表を設定するための設定フォーム" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:107 msgid "Select pricelists" -msgstr "" +msgstr "価格表を選択する" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:109 msgid "" @@ -6191,28 +6639,32 @@ msgid "" "the available pricelists in the :guilabel:`Available` field. Then, set its " "**default pricelist** in the :guilabel:`Default` field." msgstr "" +"ref:`特定のPOS管理設定 <configuration/settings>`に移動し、 " +":guilabel:`利用可能`フィールドに利用可能な全ての価格表を追加します。そして、 " +":guilabel:`デフォルト`フィールドに**デフォルト価格表**を設定します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:113 msgid "" "When you :ref:`open a POS session <pos/session-start>`, click the " "**pricelists** button, and select the desired pricelist from the list." msgstr "" +"ref:`POSセッション<pos/session-start>`を開く際、**価格表**ボタンをクリックし、リストから希望する価格表を選択します。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 msgid "Button to select a pricelist on the POS frontend" -msgstr "" +msgstr "POSフロントエンドで価格表を選択するボタン" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:120 msgid "" "Multiple pricelists must be selected for the **pricelist button** to be " "displayed." -msgstr "" +msgstr "**価格表ボタン**を表示するには、複数の価格表を選択する必要があります。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:121 msgid "" "If a pricelist is selected on a POS order while its conditions are **not** " "met, the price will **not** be adjusted." -msgstr "" +msgstr "POSオーダにおいて、その条件が満たされて**いない**状態で価格表が選択された場合、価格は調整され**ません**。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:125 msgid "" @@ -6221,20 +6673,22 @@ msgid "" "and switch to the preferred pricelist in the :guilabel:`Pricelist` field of " "the :guilabel:`Sales & Purchase` tab." msgstr "" +"また、特定の:ref:`顧客が<pos/customers>`に設定されると、自動的に価格表を選択するように設定することもできます。これを行うには、顧客フォームに行き、" +" :guilabel:`販売&購買` タブの :guilabel:`価格表` フィールドで希望する価格表に切替えます。" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:130 msgid ":doc:`../../sales/products_prices/prices/pricing`" -msgstr "" +msgstr ":doc:`../../sales/products_prices/prices/pricing`" #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:131 msgid "" ":ref:`How to use pricelists in an ecommerce environment " "<ecommerce/pricelists>`" -msgstr "" +msgstr ":ref:`eコマース環境における価格表の使い方 <ecommerce/pricelists>`" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 msgid "Receipts and invoices" -msgstr "" +msgstr "領収書と請求書" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 msgid "Receipts" @@ -6246,6 +6700,8 @@ msgid "" "--> Point of Sale`, selecting a POS, and scrolling down to the " ":guilabel:`Bills & Receipts` section." msgstr "" +"menuselection:`POS --> 設定 --> POS`でPOSを選択し、 " +":guilabel:`仕入先請求書&領収書`セクションまでスクロールダウンして領収書を設定します。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 msgid "" @@ -6253,24 +6709,26 @@ msgid "" " Footer` and fill in both fields with the information to be printed on the " "receipts." msgstr "" +"**ヘッダ**とフッタ**を**カスタマイズ**するには、 " +":guilabel:`ヘッダとフッタ`を有効にして、領収書に印刷する情報を両方のフィールドに入力して下さい。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:14 msgid "" "To **print receipts** automatically once the payment is registered, enable " "the :guilabel:`Automatic Receipt Printing` setting." -msgstr "" +msgstr "支払が登録されると自動的に領収書を印刷するには、:guilabel:`自動領収書印刷` 設定を有効にします。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "POS receipt" -msgstr "" +msgstr "POS領収書" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:21 msgid ":doc:`restaurant/bill_printing`" -msgstr "" +msgstr ":doc:`restaurant/bill_printing`" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24 msgid "Reprint a receipt" -msgstr "" +msgstr "領収書を印刷する" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 msgid "" @@ -6279,10 +6737,13 @@ msgid "" " active orders` filter to :guilabel:`Paid`. Then, select the corresponding " "order and click :guilabel:`Print Receipt`." msgstr "" +"POSインターフェイスから :guilabel:`オーダ` をクリックし、検索バーの横にあるドロップダウンメニューを開き、デフォルトの " +":guilabel:`全ての有効なオーダ` フィルタを :guilabel:`支払済` に変更します。次に、該当するオーダを選択し、 " +":guilabel:`領収書を印刷` をクリックします。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "Print receipt button from the backend" -msgstr "" +msgstr "バックエンドからの領収書印刷ボタン" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:34 msgid "" @@ -6290,6 +6751,8 @@ msgid "" "reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or " ":guilabel:`Customer`." msgstr "" +"検索バーを使ってオーダのリストを絞込むことができます。参照先を入力し、 :guilabel:`領収書番号`、 :guilabel:`日付`、 " +":guilabel:`顧客` をクリックして下さい。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 msgid "Invoices" @@ -6301,6 +6764,7 @@ msgid "" "customers <pos/customers>` upon payment and retrieve all past invoiced " "orders." msgstr "" +"POSでは、:ref:`登録済顧客<pos/customers>`に対して、支払時に請求書を発行・印刷したり、過去の請求済オーダを検索したりすることができます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 msgid "" @@ -6308,6 +6772,7 @@ msgid "" ":ref:`accounting journal <cheat_sheet/journals>`, previously :ref:`set up " "<receipts_invoices/invoice_configuration>`." msgstr "" +"POSで作成された請求書は、対応する:ref:`会計仕訳帳<cheat_sheet/journals>`(以前は:ref:`セットアップ<receipts_invoices/invoice_configuration>`)に項目を作成します。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 msgid "" @@ -6316,72 +6781,76 @@ msgid "" "accounting section. Then, you can determine the accounting journals used by " "default for orders and invoices in the :guilabel:`Default Journals` section." msgstr "" +"特定のPOSで使用する仕訳帳を定義するには、 :ref:`POS' 管理設定 <configuration/settings>` " +"に移動し、会計セクションまでスクロールダウンします。そして、 :guilabel:`デフォルト仕訳帳` " +"セクションで、オーダと請求にデフォルトで使用される会計仕訳帳を決定することができます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "accounting section in the POS settings" -msgstr "" +msgstr "POS管理設定内の会計セクション" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:63 msgid "Invoice a customer" -msgstr "" +msgstr "顧客に請求する" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 msgid "" "Upon processing a payment, click :guilabel:`Invoice` underneath the " "customer's name to issue an invoice for that order." -msgstr "" +msgstr "支払処理時、顧客名の下にある :guilabel:`請求書` をクリックすると、そのオーダの請求書が発行されます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:68 msgid "" "Select the payment method and click :guilabel:`Validate`. The **invoice** is" " automatically issued and ready to be downloaded and/or printed." msgstr "" +"支払方法を選択し、:guilabel:`検証`をクリックします。**請求書**が自動的に発行され、ダウンロードまたは印刷することができます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 msgid "" "To be able to issue an invoice, a :ref:`customer <pos/customers>` must be " "selected." -msgstr "" +msgstr "請求書を発行するには、:ref:`顧客 <pos/customers>` が選択されていなければなりません。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75 msgid "Retrieve invoices" -msgstr "" +msgstr "請求書の取得" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 msgid "To retrieve invoices from the **POS dashboard**," -msgstr "" +msgstr " **POSダッシュボード**から請求書を取得するには、" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 msgid "" "access all orders made through your POS by going to :menuselection:`Point of" " Sale --> Orders --> Orders`;" -msgstr "" +msgstr "menuselection:`POS --> オーダ --> オーダ`にアクセスして、POSを通して行われた全てのオーダにアクセスします;" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 msgid "" "to access an order's invoice, open the **order form** by selecting the " "order, then click :guilabel:`Invoice`." -msgstr "" +msgstr "オーダの請求書にアクセスするには、オーダを選択して**オーダフォーム**を開き、 :guilabel:`請求書`をクリックします。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "invoice smart button from an order form" -msgstr "" +msgstr "オーダフォームからの請求書スマートボタン" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:88 msgid "" "**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in " "the :guilabel:`Status` column." -msgstr "" +msgstr "**請求済オーダ**は :guilabel:`ステータス` 列の :guilabel:`請求済` ステータスで識別できます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 msgid "" "You can filter the list of orders to invoiced orders by clicking " ":guilabel:`Filters` and :guilabel:`Invoiced`." -msgstr "" +msgstr "guilabel:`フィルタ`と:guilabel:`請求済`をクリックすると、オーダリストを請求済オーダに絞込むことができます。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:94 msgid "QR codes to generate invoices" -msgstr "" +msgstr "請求書を生成するためのQRコード" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 msgid "" @@ -6392,10 +6861,12 @@ msgid "" "status goes from :guilabel:`Paid` or :guilabel:`Posted` to " ":guilabel:`Invoiced` in the Odoo backend." msgstr "" +"また、領収書に印刷されている**QRコード**をスキャンして請求書を要求することもできます。スキャン後、請求情報をフォームに記入し、:guilabel:`請求書を受取る`をクリックする必要があります。そうすることで、ダウンロード可能な請求書が作成されます。一方、Odooバックエンドではオーダステータスが" +" :guilabel:`支払済` または :guilabel:`記帳済` から :guilabel:`請求済` になります。" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 msgid "order status change" -msgstr "" +msgstr "オーダステイタス変更" #: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:105 msgid "" @@ -6405,6 +6876,9 @@ msgid "" ":guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on " "ticket`." msgstr "" +"この機能を使用するには、 :menuselection:`POS --> 設定 --> 管理設定`で領収書のQRコードを有効にする必要があります。次に " +":guilabel:`POS` フィールドで POS を選択し、 :guilabel:`取引先請求書&領収書` セクションまでスクロールダウンして " +":guilabel:`チケットのQRコードを使用` を有効にします。" #: ../../content/applications/sales/point_of_sale/reporting.rst:3 msgid "Reporting" @@ -6412,7 +6886,7 @@ msgstr "レポーティング" #: ../../content/applications/sales/point_of_sale/reporting.rst:6 msgid "View statistics" -msgstr "" +msgstr "統計を見る" #: ../../content/applications/sales/point_of_sale/reporting.rst:8 msgid "" @@ -6420,16 +6894,19 @@ msgid "" " --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis " "(:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." msgstr "" +"統計情報にアクセスするには、 :menuselection:`POS --> レポーティング --> オーダ` " +"にアクセスして下さい。または、**POSダッシュボード**から、縦の省略記号（:guilabel:`↪Sm_22EE` ）ボタン、 " +":guilabel:`レポート`、 :guilabel:`オーダ` をクリックします。" #: ../../content/applications/sales/point_of_sale/reporting.rst:12 msgid "" "These statistics are available in a graph or pivot view that you can filter " "or group depending on your needs." -msgstr "" +msgstr "これらの統計は、グラフまたはピボット・ビューで利用でき、ニーズに応じてフィルタリングやグループ化を行うことができます。" #: ../../content/applications/sales/point_of_sale/restaurant.rst:5 msgid "Restaurant features" -msgstr "" +msgstr "レストラン機能" #: ../../content/applications/sales/point_of_sale/restaurant.rst:7 msgid "" @@ -6437,40 +6914,41 @@ msgid "" "application provides various features that allow performing all the required" " tasks in such businesses." msgstr "" +"レストランやバーの経営には特有のニーズがあります。POSアプリケーションは、そのようなビジネスで必要なあらゆるタスクを実行するための様々な機能を提供します。" #: ../../content/applications/sales/point_of_sale/restaurant.rst:10 msgid "Once the POS is set to be used in a restaurant or a bar, you can:" -msgstr "" +msgstr "POSをレストランやバーで使用するように設定すると、以下が可能になります:" #: ../../content/applications/sales/point_of_sale/restaurant.rst:12 msgid "" ":doc:`organize your floors and tables to reflect your interior " "<restaurant/floors_tables>`;" -msgstr "" +msgstr ":doc:`フロアとテーブルを整え、内装を反映する <restaurant/floors_tables>`;" #: ../../content/applications/sales/point_of_sale/restaurant.rst:13 msgid ":ref:`take orders <floors_tables/orders>`;" -msgstr "" +msgstr ":ref:`オーダを受ける <floors_tables/orders>`;" #: ../../content/applications/sales/point_of_sale/restaurant.rst:14 msgid "" ":doc:`communicate with the kitchen or the bar through the POS " "<restaurant/kitchen_printing>`;" -msgstr "" +msgstr ":doc:`POSの<restaurant/kitchen_printing>`を通して、キッチンやバーとコミュニケーションをとる;" #: ../../content/applications/sales/point_of_sale/restaurant.rst:15 msgid "" ":doc:`print bills in advance and split them <restaurant/bill_printing>`;" -msgstr "" +msgstr ":doc:`請求書を事前に印刷し、分割する <restaurant/bill_printing>`;" #: ../../content/applications/sales/point_of_sale/restaurant.rst:16 msgid ":doc:`collect tips <restaurant/tips>`; and" -msgstr "" +msgstr ":doc:`チップを回収する <restaurant/tips>`; そして" #: ../../content/applications/sales/point_of_sale/restaurant.rst:17 msgid "" ":doc:`set different taxes for takeaway food <pricing/fiscal_position>`." -msgstr "" +msgstr ":doc:`テイクアウトフードに異なる税を適用する<pricing/fiscal_position>`。" #: ../../content/applications/sales/point_of_sale/restaurant.rst:22 msgid "" @@ -6478,15 +6956,17 @@ msgid "" ":menuselection:`Point of Sale --> Configuration --> Settings`, select the " "POS, and activate :guilabel:`Is a Bar/Restaurant`." msgstr "" +"レストランとバー固有の機能を有効にするには、 :menuselection:`POS --> 設定 --> 管理設定`に行き、POSを選択し、 " +":guilabel:`バー/レストランである` を有効にします。" #: ../../content/applications/sales/point_of_sale/restaurant.rst:25 msgid "" "These features are displayed in the :guilabel:`Restaurant & Bar` section." -msgstr "" +msgstr "これらの機能は :guilabel:`レストラン & バー` セクションに表示されます。" #: ../../content/applications/sales/point_of_sale/restaurant.rst-1 msgid "restaurant and bar-specific features" -msgstr "" +msgstr "レストランとバー固有の機能" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 msgid "Bills" @@ -6499,6 +6979,8 @@ msgid "" "provides two features to perform these tasks seamlessly: **Bill Printing** " "and **Bill Splitting**." msgstr "" +"レストランやバーでの一般的な業務は、支払に進む前に請求書を要求したり、オーダされたプロダクトに基づいて請求書を分割することです。Odoo " +"POSはこれらのタスクをシームレスに実行する2つの機能を提供します: **請求書印刷**と**請求書分割**です。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 msgid "" @@ -6507,31 +6989,34 @@ msgid "" "Receipt Printing` and :guilabel:`Allow Bill Splitting` in the " ":guilabel:`Restaurant & Bar` section." msgstr "" +"機能を有効にするには、 :menuselection:`POS --> 設定 --> 管理設定` に進み、POSを選択し、 " +":guilabel:`レストラン & バー` セクションの :guilabel:`事前領収書印刷` と :guilabel:`請求書分割を許可` " +"を有効にします。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 msgid "" "activate the bill printing and bill splitting features in the POS settings" -msgstr "" +msgstr "POS設定で請求書印刷と請求書分割機能を有効にします。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 msgid "Bill printing" -msgstr "" +msgstr "請求書印刷" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 msgid "" "From an open session, click :menuselection:`Bill --> Print` at any moment to" " generate and print a bill." -msgstr "" +msgstr "開いているセッションから :menuselection:`請求書 --> 印刷` をクリックすると、請求書が作成・印刷されます。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 msgid "" "The printed bill is **not** final and will be updated to reflect any changes" " to the order." -msgstr "" +msgstr "印刷された請求書は最終では**なく**、オーダに変更があった場合は更新されます。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 msgid "Bill splitting" -msgstr "" +msgstr "請求書分割" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 msgid "" @@ -6539,28 +7024,30 @@ msgid "" "regroup. Once everything is selected, click :guilabel:`Payment` and proceed " "to checkout for these items. Repeat for each guest." msgstr "" +"オープンセッションから :guilabel:`分割` をクリックし、再グループ化する項目を選択します。全てを選択したら、 :guilabel:`支払い " +"をクリックし、これらの項目の支払に進みます。これをゲストごとに繰返します。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 msgid "" "Once you return to the table, the selected items are no longer on order, as " "they have been paid for." -msgstr "" +msgstr "テーブルに戻ると、選択した商品は支払済であるため、オーダ中ではなくなります。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 msgid "The feature is available as soon as at least two items are ordered." -msgstr "" +msgstr "この機能は、少なくとも2つの項目がオーダされるとすぐに利用できます。" #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 msgid ":doc:`floors_tables`" -msgstr "" +msgstr ":doc:`floors_tables`" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 msgid "Floors and tables management" -msgstr "" +msgstr "フロアとテーブル管理" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6 msgid "Add a floor" -msgstr "" +msgstr "フロアを追加" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8 msgid "" @@ -6568,125 +7055,129 @@ msgid "" "under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. " "Then, click on *Floors* to create and name your floor and tables." msgstr "" +"**POS*が設定されたら、:menuselection:`POS --> 設定 --> " +"POS`で*テーブル管理*を選択します。次に、*フロア*をクリックしてフロアとテーブルを作成し、名前を付けます。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "" "View of the table management feature. Way to manage and create floors for a " "pos" -msgstr "" +msgstr "テーブル管理機能ビュー。POSのフロアを管理・作成する方法" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "" "Backend view of a restaurant floor. Table name and number of sits for each " "table" -msgstr "" +msgstr "レストランフロアのバックエンドビュー。各テーブルの名前と席数" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21 msgid "Don’t forget to link your floor to your point of sale." -msgstr "" +msgstr "フロアとPOSを忘れずに連動させて下さい。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24 msgid "Add tables" -msgstr "" +msgstr "テーブルを追加" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26 msgid "" "To add tables, you can also open your PoS interface to see your floor(s)." -msgstr "" +msgstr "テーブルを追加するために、POSインターフェイスを開いてフロアを確認することもできます。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "View of the floors menu to manage several floors at the same time" -msgstr "" +msgstr "複数のフロアを同時に管理できるフロアメニュービュー" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33 msgid "" "Then, click on *Edit Mode* (pencil icon on the upper right corner) to be " "allowed to create, move, modify tables, etc." -msgstr "" +msgstr "次に、*編集モード*(右上の鉛筆アイコン)をクリックすると、テーブルの作成、移動、修正などができるようになります。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "" "View of the floor management. Add tables, the number of sits, their name and" " their shape" -msgstr "" +msgstr "フロア管理 テーブル、座席数、名前、形状を追加します。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41 msgid "" "To make your table easier to be found, you can rename them, change their " "shape, size or even color. It is also possible to add the maximum number of " "sits the table can have." -msgstr "" +msgstr "テーブルを見つけやすくするために、名前を変えたり、形や大きさ、色を変えることもできます。また、テーブルの最大席数を追加することも可能です。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48 msgid "Register your table(s) orders" -msgstr "" +msgstr "テーブルオーダを登録する" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50 msgid "" "To register an order, click on the respective table. By doing so, you are " "taken to your main interface." -msgstr "" +msgstr "オーダを登録するには、それぞれの表をクリックして下さい。そうすることで、メインインターフェイスに移動します。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "View of the pos interface to register orders" -msgstr "" +msgstr "オーダを登録するためのPOSインターフェイスビュー" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58 msgid "Transfer customer(s)" -msgstr "" +msgstr "顧客を転送する" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60 msgid "" "If your customers want to move to another table after they already ordered, " "use the transfer button. This way, the order is also moved to the new table." -msgstr "" +msgstr "オーダ後に、顧客が別のテーブルに移動したい場合は、移動ボタンを使用して下さい。そうすれば、オーダも新しいテーブルに移動されます。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64 msgid "To do so, select the table your customer is currently on." -msgstr "" +msgstr "そのためには、顧客が現在居るテーブルを選択します。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "View of the restaurant tables, one having a pending order" -msgstr "" +msgstr "レストランのテーブルビュー、1つのテーブルに保留中オーダあり" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70 msgid "" "Now, click on the transfer button and select the table to which you are " "transferring your customer." -msgstr "" +msgstr "次に、転送ボタンをクリックし、顧客を転送するテーブルを選択します。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "" "View of the pos interface and transfer button. How to transfer customers from one table\n" "to another" msgstr "" +"posのインターフェースと転送ボタンビュー。あるテーブルから別のテーブルへ顧客を\n" +"移動する方法" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79 msgid "Register an additional order" -msgstr "" +msgstr "追加オーダを登録する" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81 msgid "" "When registering an order, use the + button to simultaneously proceed to " "another one." -msgstr "" +msgstr "オーダを登録する際、+ボタンで同時に別のオーダに進むことができます。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 msgid "" "Then, you can shift between your orders and process the payment when needed." -msgstr "" +msgstr "そして、必要なときにオーダを切り替え、支払処理することができます。" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 msgid "View of the - button, allowing employees to close/remove an order" -msgstr "" +msgstr "従業員がオーダをクローズ/削除できるようにする - ボタンのビュー" #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92 msgid "The - button allows you to remove the order you are currently on." -msgstr "" +msgstr "- ボタンをクリックすると、現在進行中のオーダを削除することができます。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 msgid "Orders printing" -msgstr "" +msgstr "オーダ印刷" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 msgid "" @@ -6694,10 +7185,11 @@ msgid "" "communication and collaboration between the front-of-house and back-of-house" " teams, leading to a more streamlined and efficient service." msgstr "" +"レストランやバーのワークフローにプリンタを組み込むことで、フロントとバックのチーム間のコミュニケーションと協力が強化され、より合理的で効率的なサービスにつながります。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:15 msgid "Enable and create printers" -msgstr "" +msgstr "プリンタを有効にして作成する" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:17 msgid "" @@ -6707,6 +7199,10 @@ msgid "" "Printers`. Type in a name for the printer in the :guilabel:`Printers` field " "and click :guilabel:`Create and edit...` to open a setup form." msgstr "" +"キッチンまたはバーのプリンタにオーダを送信できるようにするには、 :menuselection:`POS --> 設定 --> 管理設定` に進み、 " +":guilabel:`レストラン & バー` セクションまでスクロールダウンし、 :guilabel:`厨房プリンタ` " +"を有効にします。guilabel:`プリンタ`フィールドにプリンタの名前を入力し、 " +":guilabel:`作成と編集...`をクリックして設定フォームを開きます。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22 msgid "" @@ -6714,20 +7210,24 @@ msgid "" "created printer, click :guilabel:`--> Printers` and select the desired " "printer to open the setup form." msgstr "" +"すでに作成されている全てのプリンタのリストを取得したり、作成済のプリンタを変更したりするには、 :guilabel:`--> プリンタ` " +"をクリックして目的のプリンタを選択し、設定フォームを開きます。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "settings to enable the kitchen printers" -msgstr "" +msgstr "厨房プリンタを有効にする管理設定" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:32 msgid "Setup form" -msgstr "" +msgstr "セットアップフォーム" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34 msgid "" "From the :ref:`setup form <kitchen_printing/enable>`, select the " ":guilabel:`Printer Type` according to your installation:" msgstr "" +"ref:`セットアップフォーム <kitchen_printing/enable>` から、 :guilabel:`プリンタタイプ` " +"をインストール環境に合わせて選択します:" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37 msgid "" @@ -6735,6 +7235,7 @@ msgid "" "connected to the IoT Box` and select the device in the :guilabel:`IoT " "Device` field." msgstr "" +"プリンタがIoTボックスに接続されている場合は、:guilabel:`IoTボックスに接続されているプリンタを使用する`を選択し、:guilabel:`IoTデバイス`フィールドでデバイスを選択します。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39 msgid "" @@ -6742,18 +7243,20 @@ msgid "" ":guilabel:`Use an Epson printer` and enter the printer's IP address in the " ":guilabel:`Epson Printer IP Address` field." msgstr "" +"IoTボックスを必要としないエプソンプリンタを使用する場合は、 :guilabel:`エプソンプリンタを使用する`を選択し、 " +":guilabel:`エプソンプリンタIPアドレス`フィールドにプリンタのIPアドレスを入力します。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:43 msgid ":doc:`../../../productivity/iot/config/connect`" -msgstr "" +msgstr ":doc:`../../../productivity/iot/config/connect`" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 msgid ":doc:`../../../productivity/iot/devices/printer`" -msgstr "" +msgstr ":doc:`../../../productivity/iot/devices/printer`" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:45 msgid ":doc:`../configuration/epos_ssc`" -msgstr "" +msgstr ":doc:`../configuration/epos_ssc`" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:47 msgid "" @@ -6762,30 +7265,31 @@ msgid "" "Categories` field. If you leave this field empty, all products are sent to " "the printer regardless of their POS category." msgstr "" +"POSカテゴリに基づいて特定のプロダクトを印刷するようにプリンタを設定します。これを行うには、:guilabel:`プリント済プロダクトカテゴリ`フィールドの:guilabel:`明細を追加`をクリックします。このフィールドを空にすると、POSカテゴリに関係なく全てのプロダクトがプリンタに送信されます。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "setup form to configure a kitchen printer" -msgstr "" +msgstr "厨房プリンタを設定するためのセットアップフォーム" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:56 msgid "Print orders" -msgstr "" +msgstr "オーダを印刷する" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:58 msgid "" "From an open session, start taking an order and click :guilabel:`Order` to " "send it to the bar or the kitchen." -msgstr "" +msgstr "オープンセッションから、オーダを取始め、 :guilabel:`オーダ`をクリックしてそれをバーか厨房に送信します。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 msgid "order button from the POS UI to send orders to a kitchen or a bar" -msgstr "" +msgstr "POSのUIからオーダボタンを押すと、キッチンやバーにオーダを送ることができます。" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:66 msgid "" "When products can be printed, they appear in green in the cart, and the " "order button turns green." -msgstr "" +msgstr "印刷能なプロダクトは、カート内に緑色で表示され、オーダボタンも緑色になります。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 msgid "Tips" @@ -6797,6 +7301,8 @@ msgid "" ":ref:`shops <pos/sell>`, :doc:`bars <../restaurant>`, or :doc:`restaurants " "<../restaurant>`." msgstr "" +"複数の国ではチップの習慣があります。POSでは :ref:`店舗 <pos/sell>`、:doc:`バー " +"<../restaurant>`、:doc:`レストラン <../restaurant>`でチップを渡すことができます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:13 msgid "" @@ -6807,14 +7313,18 @@ msgid "" "enabled, add a :guilabel:`Tip Product` in the corresponding field, and save." " The designated product will be used as a reference on customers' receipts." msgstr "" +"POSでチップを許可するには、 :menuselection:`POS --> 設定 --> 管理設定` で :guilabel:`チップ` " +"機能を有効にします。ページ上部で、**チップ**を許可したいPOSを選択し、 :guilabel:`支払` セクションまでスクロールダウンして " +":guilabel:`チップ` をチェックします。有効化したら、対応するフィールドに :guilabel:`チッププロダクト` " +"を追加し、保存します。指定されたプロダクトは顧客の領収書の参照として使用されます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "enable tips in a POS" -msgstr "" +msgstr "POSでチップを有効にする" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:25 msgid "Tip products" -msgstr "" +msgstr "チッププロダクト" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:27 msgid "" @@ -6823,6 +7333,8 @@ msgid "" ":guilabel:`Create` or press **enter**. The product is automatically " "configured to be used as a tip at the payment screen." msgstr "" +"**チッププロダクト**はその場で作成することができます。そのためには、 :ref:`チッププロダクト ` フィールドにプロダクト名を入力し、 " +":guilabel:`作成` をクリックするか、**エンター**キーを押します。プロダクトは自動的に支払画面でチップとして使用されるように設定されます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:31 msgid "" @@ -6832,23 +7344,28 @@ msgid "" " go to the :guilabel:`Sales` tab, tick the :guilabel:`Available in POS` " "checkbox, and click :guilabel:`Save & Close`." msgstr "" +"ただし、POSセッションでチッププロダクトを選択できるようにしたい場合は、**POSで利用可能**設定を有効にする必要があります。そのためには、 " +":guilabel:`作成と編集...`をクリックしてプロダクト設定フォームを開きます。次に、 :guilabel:`販売` タブに移動し、 " +":guilabel:`POSで利用可能` チェックボックスにチェックを入れ、 :guilabel:`保存 & クローズ` をクリックします。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:37 msgid "" "When you create a product to use as a tip, leave the **product type** as " ":guilabel:`Consumable` to avoid unnecessary inventory movements." msgstr "" +"チップとして使用するプロダクトを作成する場合、不必要な在庫移動を避けるために、**プロダクトタイプ**を :guilabel:`消費可能` " +"のままにしておきます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:39 msgid "" "You can only select one tip product per POS, but you can choose a different " "one for each." -msgstr "" +msgstr "1つのPOSにつきチッププロダクトは1つしか選択できませんが、それぞれ異なるプロダクトを選択することができます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:42 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:72 msgid "Tip using an Adyen terminal" -msgstr "" +msgstr "Adyen端末を使用したチップ" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:44 msgid "" @@ -6857,11 +7374,14 @@ msgid "" ":guilabel:`Add tip through payment terminal (Adyen)` below the :ref:`tip " "settings <configuration>`." msgstr "" +"doc:`Adyen <../payment_methods/terminals/adyen>` " +"の決済端末を使用し、端末を使用して**チップ**を有効にしたい場合は、 :ref:`チップの管理設定<configuration>`の下にある " +":guilabel:`決済端末を使用してチップを追加(Adyen)` にチェックを入れます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:49 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:79 msgid "Tip after payment" -msgstr "" +msgstr "支払後のチップ" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:51 msgid "" @@ -6871,16 +7391,17 @@ msgid "" "waiter. That bill indicates the tip value the customer chooses to give after" " the payment." msgstr "" +"バーやレストランでPOSシステムを使用している場合、:guilabel:`支払後にチップを追加(北アメリカ特有)`を有効にすることができます。そうすることで、顧客とウェイターが手動で印刷・記入する請求書が生成されます。その請求書には、顧客が支払後に渡すチップの金額が表示されます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:56 msgid "" "To use this feature, the selected payment method must have a bank journal " "attributed." -msgstr "" +msgstr "この機能を使用するには、選択した支払方法に銀行仕訳帳が付与されている必要があります。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:59 msgid "Add tips" -msgstr "" +msgstr "チップを追加" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:61 msgid "" @@ -6888,10 +7409,12 @@ msgid "" "click :guilabel:`♥ Tip`. Then, enter the tipping amount, click " ":guilabel:`Confirm` to validate, and process the payment." msgstr "" +"オーダにチップを追加するには、:ref:`支払画面<pos/sell>`にアクセスし、:guilabel:`♥ " +"チップ`をクリックします。次に、チップの金額を入力し、:guilabel:`確定`をクリックして確認し、支払を処理します。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "tip popup window" -msgstr "" +msgstr "チップポップアップウィンドウ" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:67 msgid "" @@ -6900,6 +7423,8 @@ msgid "" "automatically set as a tip, and its default value equals its **Sales " "Price**." msgstr "" +"または、POSインターフェイスで :ref:`チッププロダクト<tip-product> ` " +"を選択してカートに追加することもできます。選択されると、そのプロダクトは自動的にチップとして設定され、そのデフォルト値は**販売価格**と等しくなります。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:74 msgid "" @@ -6908,16 +7433,19 @@ msgid "" "are asked to enter the desired tipping amount on the terminal's screen " "before proceeding to the payment." msgstr "" +"チェックアウトの際、決済端末として**Adyen**を選択し、 " +":guilabel:`送信`をクリックして支払要求を端末に送信します。顧客は支払に進む前に、端末の画面で希望するチップ額を入力するよう求められます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:81 msgid "" "At checkout, select a card payment method and click :guilabel:`Close Tab`. " "Doing so generates a bill to complete by the customer." msgstr "" +"チェックアウトの際、カードの支払方法を選択し、:guilabel:`クローズタブ`をクリックします。そうすることで、顧客が記入する請求書が作成されます。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "tipping bill after payment to complete by customers" -msgstr "" +msgstr "顧客による支払完了後のチップ請求書" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:87 msgid "" @@ -6926,18 +7454,19 @@ msgid "" "amount the customer chose to give. Then, click :guilabel:`Settle` to move to" " the following order." msgstr "" +"次の画面で、パーセンテージ(:guilabel:`15%`、:guilabel:`20%`、:guilabel:`25%`)をクリックするか、:guilabel:`チップなし`、または顧客が選択したチップ額を入力します。次に、:guilabel:`確定`をクリックすると、次の順番に移動します。" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "screen to select a tip amount to collect after payment" -msgstr "" +msgstr "支払後に徴収するチップ額を選択する画面" #: ../../content/applications/sales/point_of_sale/shop.rst:5 msgid "Shop features" -msgstr "" +msgstr "店舗機能" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 msgid "Barcodes" -msgstr "" +msgstr "バーコード" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:5 msgid "" @@ -6945,6 +7474,7 @@ msgid "" "efficiency in providing quicker customer service. Barcode scanners can be " "used both to scan products or to log employees into a POS session." msgstr "" +"バーコードスキャナを使用してPOSオーダを処理すると、迅速な顧客サービスを提供する効率が向上します。バーコードスキャナは、プロダクトをスキャンするためにも、従業員をPOSセッションにログインさせるためにも使用できます。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:12 msgid "" @@ -6952,36 +7482,41 @@ msgid "" "Go to :menuselection:`Inventory --> Configuration --> Settings`, in the " ":guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." msgstr "" +"バーコードスキャナーを使用するには、在庫リアプリで機能を有効にする必要があります。menuselection:`在庫 --> 設定 --> " +"管理設定`に移動し、 :guilabel:`バーコード`セクションで、 :guilabel:`バーコードスキャナ`にチェックを入れて保存します。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst-1 msgid "barcode setting in the Inventory application" -msgstr "" +msgstr "インベントリアプリケーションでのバーコード設定" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 msgid "" ":doc:`Set up a barcode scanner " "</applications/inventory_and_mrp/barcode/setup/hardware>`" msgstr "" +":doc:`バーコードスキャナの設定 </applications/inventory_and_mrp/barcode/setup/hardware>`" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22 msgid "" ":doc:`Activate barcode scanners " "</applications/inventory_and_mrp/barcode/setup/software>`" msgstr "" +":doc:`バーコードスキャナの有効化 " +"</applications/inventory_and_mrp/barcode/setup/software>`" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24 msgid "" "Once enabled in **Inventory**, you can use the barcode feature in **Point of" " Sale** with products that have a barcode number assigned." -msgstr "" +msgstr "一度**在庫**で有効にすると、**POS**でバーコード番号が割当てられたプロダクトでバーコード機能を使用することができます。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:28 msgid "Assign barcodes" -msgstr "" +msgstr "バーコード割当" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:31 msgid "To your products" -msgstr "" +msgstr "プロダクトへ" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 msgid "" @@ -6990,10 +7525,13 @@ msgid "" " a **product form**. Add a barcode number in the :guilabel:`Barcode` field " "in the :guilabel:`General Information` tab." msgstr "" +"POSでこの機能を使用するには、プロダクトにバーコードを割当てる必要があります。これを行うには、 :menuselection:`POS --> " +"プロダクト --> プロダクト` に行き、**プロダクトフォーム**を開きます。guilabel:`一般情報`タブの " +":guilabel:`バーコード`フィールドにバーコード番号を追加します。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:38 msgid "To your employees" -msgstr "" +msgstr "従業員へ" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:40 msgid "" @@ -7002,10 +7540,12 @@ msgid "" "employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR " "Settings` tab." msgstr "" +"従業員に識別番号を追加するには、**従業員**アプリに移動し、**従業員フォーム**を開きます。従業員の識別番号を選択し、 " +":guilabel:`HR管理設定` タブの :guilabel:`PINコード` フィールドに入力します。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:45 msgid "Use barcodes" -msgstr "" +msgstr "バーコード使用" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:48 msgid "Scan products" @@ -7017,16 +7557,17 @@ msgid "" "to the cart. To change the quantity, scan a product as many times as needed," " or click :guilabel:`Qty` and enter the number of products using the keypad." msgstr "" +"バーコードスキャナーでプロダクトのバーコードをスキャンします。そうすることで、カートに直接追加されます。数量を変更するには、必要なだけプロダクトをスキャンするか、:guilabel:`Qty`をクリックしてキーパッドでプロダクト数を入力して下さい。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:54 msgid "" "You can also enter the barcode number manually in the search bar to look for" " the product. Then, click it to add it to the cart." -msgstr "" +msgstr "検索バーにバーコード番号を手入力してプロダクトを探すこともできます。その後、クリックしてカートに入れます。" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 msgid "Log employees" -msgstr "" +msgstr "従業員を記録" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 msgid "" @@ -7035,10 +7576,11 @@ msgid "" ":ref:`use barcodes to log your employees in <employee_login/badge>` your " "POS." msgstr "" +"また、バーコードスキャナを使用して従業員を記録することもできます。これを行うには、:ref:POSへの`アクセス<employee_login/configuration>を制限`し、:ref:POSで`バーコードを使用して従業員を記録<employee_login/badge>`します。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 msgid "Sales orders" -msgstr "" +msgstr "販売オーダ" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 msgid "" @@ -7047,10 +7589,11 @@ msgid "" " Sales, meaning that you can create a sales order and pay for it directly " "from your point of sale." msgstr "" +"小売業の場合、POSから直接プロダクトをオーダする必要があるかもしれません。幸いなことに、OdooPOSはOdoo販売と完全に統合されており、POSから直接販売オーダを作成し、代金を支払うことができます。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:10 msgid "Select a sales order" -msgstr "" +msgstr "販売オーダを選択" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:12 msgid "" @@ -7058,10 +7601,12 @@ msgid "" ":guilabel:`Quotations/Orders` to get the complete list of quotations and " "sales orders created on the sales application." msgstr "" +"**POS**アプリケーションから、新しいセッションを開いて下さい。次に、 " +":guilabel:`見積/オーダ`をクリックすると、販売アプリケーションで作成された見積と販売オーダの全リストが表示されます。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 msgid "Quotations and sales order button on the Point of Sale interface" -msgstr "" +msgstr "POSインターフェイスの見積および販売オーダボタン" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 msgid "" @@ -7070,22 +7615,23 @@ msgid "" "before clicking on :guilabel:`Quotations/Orders` to reduce the list to one " "particular customer." msgstr "" +"正しいオーダを見つけやすくするために、**顧客**または**オーダ参照**でリストをフィルタリングすることができます。また、:guilabel:`見積/オーダ`をクリックする前に顧客を設定することで、リストを特定の顧客に絞り込むことができます。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:26 msgid "Apply a down payment or settle the order" -msgstr "" +msgstr "前払金の適用またはオーダの決済" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:28 msgid "From the list of sales order, select one to make a payment." -msgstr "" +msgstr "販売オーダのリストから、支払を行うオーダを選択します。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 msgid "list view of sales orders and quotations" -msgstr "" +msgstr "販売オーダと見積のリスト表示" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 msgid "You can either:" -msgstr "" +msgstr "いずれかが可能です:" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:36 msgid "" @@ -7093,18 +7639,20 @@ msgid "" "payment`, enter the percentage of down payment you want the customer to pay." " Then, click on :guilabel:`ok` and proceed with the order." msgstr "" +"オーダを**部分的に**決済します。 " +":guilabel:`前払金を適用`をクリックした後、顧客に支払ってもらいたい前払金のパーセンテージを入力します。その後、:guilabel:`ok`をクリックしてオーダを進めます。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:39 msgid "" "Settle the order **completely**: click on :guilabel:`Settle the order` to " "pay for the total of the sales order." -msgstr "" +msgstr "オーダを**完全に**決済します。 :guilabel:`オーダを決済する`をクリックして、販売オーダの合計金額を支払います。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:43 msgid "" "Once you settle a sales order, the applied down payment is automatically " "deducted from the total amount." -msgstr "" +msgstr "販売オーダを決済すると、適用された前払金は自動的に合計金額から差引かれます。" #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:47 msgid ":doc:`/applications/sales/sales/invoicing/down_payment`" @@ -7112,7 +7660,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:3 msgid "Serial numbers and lots" -msgstr "" +msgstr "シリアル番号とロット" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:5 msgid "" @@ -7120,6 +7668,7 @@ msgid "" "movements. When products are tracked, the system identifies their location " "based on their last movement." msgstr "" +"**シリアル番号**と**ロット**を使用すると、プロダクトの動きを追跡することができます。プロダクトが追跡されると、システムは最後の移動に基づいて位置を特定します。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:8 msgid "" @@ -7128,14 +7677,17 @@ msgid "" "Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the " ":guilabel:`Inventory` tab." msgstr "" +"トレーサビリティを有効にするには、 :menuselection:`POS --> プロダクト --> プロダクト` " +"に進みます。次に、プロダクトを選択し、 :guilabel:`在庫` タブの :guilabel:`一意のシリアル番号で追跡` または " +":guilabel:`ロットで追跡` ボックスにチェックを入れます。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "Enable traceability settings" -msgstr "" +msgstr "トレーサビリティ設定を有効にする" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 msgid "Serial numbers and lots importation" -msgstr "" +msgstr "シリアル番号とロットインポート" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:19 msgid "" @@ -7143,24 +7695,26 @@ msgid "" "order** or a **quotation** containing tracked products. Then, agree to load " "the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." msgstr "" +"POSでシリアル番号をインポートすることができます。これを行うには、追跡されたプロダクトを含む**販売オーダ**または**見積**を選択します。次に、:abbr:`販売オーダ`にリンクされている**ロットまたはシリアル番号**を読み込むことに同意します。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "Pop-up window for serial number import" -msgstr "" +msgstr "シリアル番号インポート用ポップアップウィンドウ" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 msgid "" "The imported tracking numbers appear below the tracked products. You can " "modify them by clicking on the list-view button next to the products." msgstr "" +"インポートされた追跡番号は、追跡されたプロダクトの下に表示されます。プロダクトの横にあるリストビューボタンをクリックすることで変更することができます。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:37 msgid ":doc:`../shop/sales_order`" -msgstr "" +msgstr ":doc:`../shop/sales_order`" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:40 msgid "Serial numbers and lots creation" -msgstr "" +msgstr "シリアル番号とロット作成" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:42 msgid "" @@ -7169,16 +7723,18 @@ msgid "" "or lot numbers. To add more than one of the same tracked products, click on " "**enter** to validate and start a new line." msgstr "" +"追跡プロダクトがPOSで利用可能な場合、プロダクトをカートに追加するとポップアップウィンドウが開き、プロダクトのシリアル番号またはロット番号を入力またはスキャンできます。同じ追跡対象プロダクトを複数追加するには、**入力**をクリックして有効化し、新しい行を開始します。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 msgid "adding new serial and lots numbers" -msgstr "" +msgstr "新規シリアルおよびロット番号を追加" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 msgid "" "Changing a tracked product's quantity using the numpad turns the list-view " "button red. Click on it to add the missing lot and serial numbers." msgstr "" +"追跡されたプロダクトの数量をテンキーで変更すると、リストビューのボタンが赤くなります。それをクリックすると、不足しているロット番号とシリアル番号が追加されます。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:54 msgid "" @@ -7186,16 +7742,20 @@ msgid "" "products but not mandatory. Meaning that not attributing some or any does " "**not** prevent from completing the sale." msgstr "" +":guilabel:`ロット番号とシリアル番号`は、追跡されたプロダクトでは :guilabel:`必要` " +"ですが、必須ではありません。つまり、いくつか、またはどれかを帰属させなかったとしても、販売の完了を妨げ**ません**。" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 msgid "" ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" msgstr "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 msgid "" ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" #: ../../content/applications/sales/rental.rst:3 msgid "Rental" @@ -7205,7 +7765,7 @@ msgstr "レンタル" msgid "" "The Odoo *Rental* application provides comprehensive solutions to configure " "and manage rentals." -msgstr "" +msgstr "Odoo *レンタル*アプリケーションは、レンタルの設定と管理のための包括的なソリューションを提供します。" #: ../../content/applications/sales/rental.rst:7 msgid "" @@ -7213,14 +7773,15 @@ msgid "" "they are picked up and returned, and invoice customers from this single " "platform." msgstr "" +"見積書の送付、オーダの確認、レンタルの予約、プロダクトの引取・返却時の登録、顧客への請求書発行などをこのプラットフォーム1つで行うことができます。" #: ../../content/applications/sales/rental.rst:11 msgid "`Odoo Rental: product page <https://www.odoo.com/app/rental>`_" -msgstr "" +msgstr "`Odooレンタル: プロダクトページ <https://www.odoo.com/app/rental>`_" #: ../../content/applications/sales/rental.rst:12 msgid "`Odoo Tutorials: Rental <https://www.odoo.com/slides/rental-48>`_" -msgstr "" +msgstr "`Odooチュートリアル: レンタル <https://www.odoo.com/slides/rental-48>`_" #: ../../content/applications/sales/rental.rst:17 msgid "Dashboard" @@ -7230,13 +7791,13 @@ msgstr "ダッシュボード" msgid "" "Upon opening the *Rental* application, the :guilabel:`Rental Orders` " "dashboard is revealed." -msgstr "" +msgstr "*レンタル*アプリケーションを開くと、 :guilabel:`レンタルオーダ` ダッシュボードが表示されます。" #: ../../content/applications/sales/rental.rst-1 msgid "" "Example of the Rental Orders dashboard available in the Odoo Rental " "application." -msgstr "" +msgstr "Odooレンタルアプリケーションで利用可能なレンタルオーダーダッシュボードの例。" #: ../../content/applications/sales/rental.rst:25 msgid "" @@ -7244,12 +7805,13 @@ msgid "" "displays the customer name, the price of the rental, the related sales order" " number, along with the status of the rental." msgstr "" +"デフォルトのかんばん表示では、全てのレンタルが表示されます。各レンタルカードには、顧客名、レンタル価格、関連する販売オーダ番号、レンタルのステータスが表示されます。" #: ../../content/applications/sales/rental.rst:29 msgid "" "Rental kanban cards that do **not** display a rental status means those " "rentals have confirmed quotations, but have not been picked up yet." -msgstr "" +msgstr "レンタル状況が表示されて**ない**レンタルかんばんカードは、見積は確定しているが、まだ引取されていないことを意味します。" #: ../../content/applications/sales/rental.rst:32 msgid "" @@ -7258,6 +7820,8 @@ msgid "" "accessible. Clicking any option in the left sidebar filters the displayed " "rentals on the dashboard." msgstr "" +"左サイドバーには各レンタルの :guilabel:`レンタルステータス` が表示されます。その下にある :guilabel:`請求ステータス` " +"にアクセスすることができます。左サイドバーのオプションをクリックすると、ダッシュボードに表示されるレンタルがフィルタリングされます。" #: ../../content/applications/sales/rental.rst:37 #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 @@ -7272,10 +7836,12 @@ msgid "" " minimum time of rental, navigate to :menuselection:`Rental app --> " "Configuration --> Settings`." msgstr "" +"追加レンタル遅延費用、レンタルアイテムの有無、またはレンタルの最小時間を設定するには、 :menuselection:`レンタルアプリ --> 設定 " +"--> 管理設定`に移動します。" #: ../../content/applications/sales/rental.rst-1 msgid "How the Settings page appears in the Odoo Rental application." -msgstr "" +msgstr "Odooレンタルの設定画面の表示方法" #: ../../content/applications/sales/rental.rst:46 msgid "" @@ -7284,32 +7850,35 @@ msgid "" "is also the option to activate :guilabel:`Rental Transfers` and " ":guilabel:`Digital Documents`." msgstr "" +"guilabel:`レンタル`セクションには、 :guilabel:`デフォルトの遅延コスト` と :guilabel:`デフォルトのパディング時間` " +"を設定するオプションがあります。また、 :guilabel:`レンタル転送` と :guilabel:`デジタルドキュメント` " +"を有効にするオプションもあります。" #: ../../content/applications/sales/rental.rst:50 msgid ":guilabel:`Default Delay Costs` are additional costs for late returns." -msgstr "" +msgstr ":guilabel:`デフォルト遅延コスト`は遅延返却用の追加コストです。" #: ../../content/applications/sales/rental.rst:51 msgid "" ":guilabel:`Default Padding Time` represents the minimum amount of time " "between two rentals." -msgstr "" +msgstr ":guilabel:`デフォルトパディング時間`は、2つのレンタル間の最小時間を表します。" #: ../../content/applications/sales/rental.rst:52 msgid "" ":guilabel:`Rental Transfers` means stock deliveries and receipts can be used" " for rental orders." -msgstr "" +msgstr ":guilabel:`レンタル転送`は、在庫の配達と領収書をレンタルオーダに使用できることを意味します。" #: ../../content/applications/sales/rental.rst:54 msgid "" ":guilabel:`Digital Documents` allows users to upload documents for customers" " to sign prior to" -msgstr "" +msgstr ":guilabel:`デジタルドキュメント`により、ユーザは、顧客が署名するドキュメントをアップロードすることができます。" #: ../../content/applications/sales/rental.rst:54 msgid "confirming their rental." -msgstr "" +msgstr "レンタルを確定する" #: ../../content/applications/sales/rental.rst:56 msgid "" @@ -7317,10 +7886,11 @@ msgid "" ":guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability " "days`, or days during which pickup and return are not possible." msgstr "" +"guilabel:`オンラインでレンタル`セクションには、:guilabel:`最小レンタル期間`を設定するオプションと、:guilabel:`利用不可日`、つまり受取と返却ができない日を指定するオプションがあります。" #: ../../content/applications/sales/rental.rst:61 msgid "Rental products" -msgstr "" +msgstr "レンタルプロダクト" #: ../../content/applications/sales/rental.rst:63 msgid "" @@ -7328,16 +7898,18 @@ msgid "" ":menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be" " Rented` search filter appears in the search bar." msgstr "" +"データベース内のレンタル可能な全商品を表示するには、 :menuselection:`レンタルアプリ --> プロダクト` " +"に移動します。デフォルトでは、検索バーに :guilabel:`レンタル可能` 検索フィルタが表示されます。" #: ../../content/applications/sales/rental.rst:66 msgid "" "Each product kanban card displays that product's name, rental price, and " "product image (if applicable)." -msgstr "" +msgstr "各プロダクトのかんばんカードには、プロダクト名、レンタル価格、プロダクト画像(該当する場合)が表示されます。" #: ../../content/applications/sales/rental.rst:70 msgid "Rental pricing" -msgstr "" +msgstr "レンタル価格" #: ../../content/applications/sales/rental.rst:72 msgid "" @@ -7345,12 +7917,15 @@ msgid "" "page in the *Rental* app, then select the desired product or click " ":guilabel:`New` to create a new product from scratch." msgstr "" +"プロダクトのレンタル価格を調整するには、*レンタル*アプリの :guilabel:`プロダクト` ページに移動し、希望のプロダクトを選択するか、 " +":guilabel:`新規` をクリックしてゼロから新しいプロダクトを作成します。" #: ../../content/applications/sales/rental.rst:75 msgid "" "On the product form, ensure the :guilabel:`Can be Rented` checkbox is " "ticked. Then, open the :guilabel:`Rental prices` tab." msgstr "" +"プロダクトフォームで、:guilabel:`レンタル可能`チェックボックスにチェックが入っていることを確認します。次に、:guilabel:`レンタル価格`タブを開きます。" #: ../../content/applications/sales/rental.rst:83 msgid "" @@ -7359,12 +7934,15 @@ msgid "" "default, this checkbox is ticked whenever a product is created directly in " "the *Rental* application." msgstr "" +"*レンタル*アプリの外でレンタルプロダクトを作成する場合、プロダクトフォームの :guilabel:`レンタル可能` " +"チェックボックスにチェックが入っていることを確認して下さい。デフォルトでは、*レンタル*アプリで直接商品を作成する場合は、常にこのチェックボックスにチェックが入っています。" #: ../../content/applications/sales/rental.rst:90 msgid "" "Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, " "designate custom rental prices and rental periods for the product." msgstr "" +"guilabel:`レンタル価格` タブの :guilabel:`価格` セクションで、プロダクトのカスタムレンタル価格とレンタル期間を指定します。" #: ../../content/applications/sales/rental.rst:93 msgid "" @@ -7373,18 +7951,20 @@ msgid "" ":guilabel:`Period` column, or create a new pricing period by typing in the " "name and clicking :guilabel:`Create`." msgstr "" +"レンタルの価格を追加するには、 :guilabel:`価格の追加` " +"をクリックします。次に、:guilabel:`機関`カラムで*価格設定期間*(:dfn:`レンタル期間の単位`)を選択するか、名前を入力して:guilabel:`作成`をクリックして新しい価格設定期間を作成します。" #: ../../content/applications/sales/rental.rst:97 msgid "" "Next, decide whether or not to apply this custom rental price to a specific " ":guilabel:`Pricelist`." -msgstr "" +msgstr "次に、このカスタムレンタル価格を特定の :guilabel:`価格表` に適用するかどうかを決定します。" #: ../../content/applications/sales/rental.rst:99 msgid "" "Lastly, enter the desired :guilabel:`Price` for that specific " ":guilabel:`Period`." -msgstr "" +msgstr "最後に、その特定の :guilabel:`期間` の :guilabel:`価格` を入力します。" #: ../../content/applications/sales/rental.rst:102 msgid "" @@ -7392,12 +7972,13 @@ msgid "" "options for rental products are typically used to give discounts for " "customers who agree to longer rental durations." msgstr "" +"価格設定明細の数に制限はありません。レンタルプロダクトの複数の価格設定オプションは、通常、長いレンタル期間に同意する顧客に対して値引を提供するために使用されます。" #: ../../content/applications/sales/rental.rst:105 msgid "" "To delete any rental pricing option, click the :guilabel:`🗑️ (trash)` icon, " "and that row is deleted." -msgstr "" +msgstr "guilabel:`🗑️(ゴミ箱)`アイコンをクリックすると、その行が削除されます。" #: ../../content/applications/sales/rental.rst:109 msgid "Reservations" @@ -7410,6 +7991,7 @@ msgid "" ":guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to " "return a rental." msgstr "" +"guilabel:`レンタル料金`タブの:guilabel:`予約`セクションの下に、顧客がレンタルの返却にかかった:guilabel:`延長時間`または:guilabel:`延長日`に対する追加の罰金を設定するオプションがあります。" #: ../../content/applications/sales/rental.rst:115 msgid "" @@ -7418,46 +8000,48 @@ msgid "" " orders. Such a feature may prove useful if maintenance or cleaning is " "required between rentals." msgstr "" +"また、2つのレンタルオーダの間にレンタルプロダクトを一時的に利用できなくするために、時間で表される :guilabel:`セキュリティ時間` " +"を設定するオプションもあります。このような機能は、レンタルの間にメンテナンスやクリーニングが必要な場合に便利です。" #: ../../content/applications/sales/rental.rst:120 msgid "Price computing" -msgstr "" +msgstr "価格計算" #: ../../content/applications/sales/rental.rst:122 msgid "" "Odoo always uses two rules to compute the price of a product when a rental " "order is created:" -msgstr "" +msgstr "Odooはレンタルオーダを作成する際、常に2つの規則でプロダクト価格を計算します:" #: ../../content/applications/sales/rental.rst:124 msgid "Only one price line is used." -msgstr "" +msgstr "1つの価格明細のみ使用されます。" #: ../../content/applications/sales/rental.rst:125 msgid "The cheapest line is selected." -msgstr "" +msgstr "最も安価な明細が選択されます。" #: ../../content/applications/sales/rental.rst:128 msgid "Consider the following rental pricing configuration for a product:" -msgstr "" +msgstr "あるプロダクトについて、次のようなレンタル価格設定を考えてみましょう:" #: ../../content/applications/sales/rental.rst:130 msgid "1 day: $100" -msgstr "" +msgstr "1 日: $100" #: ../../content/applications/sales/rental.rst:131 msgid "3 days: $250" -msgstr "" +msgstr "3 日: $250" #: ../../content/applications/sales/rental.rst:132 msgid "1 week: $500" -msgstr "" +msgstr "1 週間: $500" #: ../../content/applications/sales/rental.rst:134 msgid "" "A customer wants to rent this product for eight days. What price will they " "pay?" -msgstr "" +msgstr "ある顧客がこのプロダクトを8日間レンタルしたい場合、料金はいくらになるでしょうか？" #: ../../content/applications/sales/rental.rst:136 msgid "" @@ -7465,10 +8049,11 @@ msgid "" "cheapest option. The customer has to pay three times '3 days' to cover the " "rental's eight days, for a total of $750." msgstr "" +"オーダが作成されると、Odooは2番目の明細を選択します。顧客はレンタルの8日間をカバーするためにを'3日間を'3回、合計750ドルを支払う必要があります。" #: ../../content/applications/sales/rental.rst:142 msgid "Rental orders" -msgstr "" +msgstr "レンタルオーダ" #: ../../content/applications/sales/rental.rst:144 msgid "" @@ -7477,6 +8062,8 @@ msgid "" ":guilabel:`New`. Doing so reveals a blank rental order form to be filled in " "accordingly." msgstr "" +"*レンタル*アプリでレンタルオーダを作成するには、 :menuselection:`レンタルアプリ --> オーダ --> オーダ` に移動し、 " +":guilabel:`新規` をクリックします。空白のレンタルオーダフォームが表示されますので、必要事項を記入して下さい。" #: ../../content/applications/sales/rental.rst-1 msgid "" diff --git a/locale/ja/LC_MESSAGES/websites.po b/locale/ja/LC_MESSAGES/websites.po index 2bdbcd2e0..1bf9b48d9 100644 --- a/locale/ja/LC_MESSAGES/websites.po +++ b/locale/ja/LC_MESSAGES/websites.po @@ -1230,7 +1230,7 @@ msgstr "" #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:15 msgid "Sales orders" -msgstr "" +msgstr "販売オーダ" #: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:18 msgid "Order and payment status" @@ -6258,7 +6258,7 @@ msgstr "" #: ../../content/applications/websites/website/configuration/spam_protection.rst:56 #: ../../content/applications/websites/website/pages.rst:27 msgid "Click :guilabel:`Create`." -msgstr "" +msgstr " :guilabel:`作成`をクリックします。" #: ../../content/applications/websites/website/configuration/spam_protection.rst-1 msgid "Adding a website to Cloudflare Turnstile" diff --git a/locale/ko/LC_MESSAGES/administration.po b/locale/ko/LC_MESSAGES/administration.po index 4abf5d0ad..25c8a321f 100644 --- a/locale/ko/LC_MESSAGES/administration.po +++ b/locale/ko/LC_MESSAGES/administration.po @@ -223,11 +223,11 @@ msgstr "" msgid "" "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be " "used in the next steps." -msgstr "" +msgstr ":guilabel:`영역 URL`을 텍스트 에디터에 복사하여 다음 단계에서 사용할 수 있도록 합니다." #: ../../content/administration/install/cdn.rst:55 msgid "Configure the Odoo instance with the new zone" -msgstr "" +msgstr "새로운 영역으로 Odoo 인스턴스 환경 설정" #: ../../content/administration/install/cdn.rst:57 msgid "" @@ -238,26 +238,32 @@ msgid "" "when :doc:`Developer Mode <../../applications/general/developer_mode>` is " "activated." msgstr "" +"Odoo :guilabel:`웹사이트` 앱에서 :menuselection:`설정`으로 이동한 다음 :guilabel:`콘텐츠 전송 " +"네트워크 (CDN)` 설정을 활성화하고 이전 단계의 :guilabel:`영역 URL` 값을 :guilabel:`CDN 기본 URL` " +"필드에 복사/붙여넣기합니다. 이 필드는 :doc:`개발자 모드 " +"<../../applications/general/developer_mode>`가 활성화된 경우에만 확인 및 환경 설정할 수 있습니다." #: ../../content/administration/install/cdn.rst:63 msgid "" "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN" " Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." msgstr "" +":guilabel:`CDN Base URL` 앞에 *왼쪽 방향 슬래시*가 두 개 (`//`)있고 :guilabel:`CDN Base " +"URL` 뒤에는 왼쪽 방향으로 슬래시가 하나 (`/`)가 있는지 확인합니다." #: ../../content/administration/install/cdn.rst:66 msgid ":guilabel:`Save` the settings when complete." -msgstr "" +msgstr "설정 완료 후 :guilabel:`저장`합니다." #: ../../content/administration/install/cdn.rst-1 msgid "Activate the CDN setting in Odoo." -msgstr "" +msgstr "Odoo에서 CDN 설정을 활성화합니다." #: ../../content/administration/install/cdn.rst:72 msgid "" "Now the website is using the CDN for the resources matching the " ":guilabel:`CDN filters` regular expressions." -msgstr "" +msgstr "이제 웹사이트에서는 :guilabel:`CDN 필터` 정규식과 일치하는 리소스에 CDN을 사용하고 있습니다." #: ../../content/administration/install/cdn.rst:75 msgid "" @@ -276,12 +282,12 @@ msgstr "" #: ../../content/administration/install/cdn.rst-1 msgid "" "The CDN Base URL can be seen using the inspect function on the Odoo website." -msgstr "" +msgstr "CDN 기본 URL은 Odoo 웹사이트의 검사 기능을 사용하면 확인할 수 있습니다." #: ../../content/administration/install/cdn.rst:85 msgid "" "Prevent security issues by activating cross-origin resource sharing (CORS)" -msgstr "" +msgstr "교차 출처 리소스 공유 (CORS:Cross-Origin Resource Sharing)를 활성화하여 보안 문제 방지" #: ../../content/administration/install/cdn.rst:87 msgid "" @@ -289,6 +295,8 @@ msgid "" "Chrome) prevents a remotely linked CSS file to fetch relative resources on " "this same external server." msgstr "" +"일부 브라우저 (예: Mozilla Firefox 및 Google Chrome)에서는 보안 제한으로 인해 원격으로 연결된 CSS 파일이 " +"동일한 외부 서버에서 관련 리소스를 가져오는 것을 금지하고 있습니다." #: ../../content/administration/install/cdn.rst:90 msgid "" @@ -297,6 +305,9 @@ msgid "" "Odoo website will be the lack of *Font Awesome* icons because the font file " "declared in the *Font Awesome* CSS won't be loaded from the remote server." msgstr "" +":abbr:`CORS (Cross-Origin Resource Sharing)` 옵션이 :guilabel:`CDN 영역`에서 활성화되지 " +"않은 경우, 더 큰 문제는 *Font Awesome* CSS에 선언된 글꼴 파일은 원격 서버에서 로드되지 않기 때문에 표준 Odoo " +"웹사이트에서 *Font Awesome* 아이콘이 없게 된다는 것입니다. " #: ../../content/administration/install/cdn.rst:95 msgid "" @@ -343,7 +354,7 @@ msgstr "" #: ../../content/administration/install/deploy.rst:15 msgid "dbfilter" -msgstr "" +msgstr "dbfilter" #: ../../content/administration/install/deploy.rst:17 msgid "" @@ -1615,7 +1626,7 @@ msgstr "" #: ../../content/administration/upgrade.rst:90 #: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" -msgstr "" +msgstr "Odoo 온라인" #: ../../content/administration/install/online.rst:16 msgid "" @@ -5038,16 +5049,18 @@ msgid "" " so you can :ref:`force an Update Notification <force_ping>` to make the " "message disappear right away." msgstr "" +"데이터베이스 사용자 수가 올바른 경우에는, 다음 인증 시 만료 메시지가 며칠 후 자동으로 사라집니다. 카운트다운이 표시되는 불안한 상황을" +" 피하고자 하는 경우에는, :ref:`업데이트 알림 강제 실행 <force_ping>`으로 메시지가 즉시 사라지게 할 수 있습니다." #: ../../content/administration/maintain/on_premise.rst:114 msgid "Database expired error message" -msgstr "" +msgstr "데이터베이스 만료 오류 메시지" #: ../../content/administration/maintain/on_premise.rst:116 msgid "" "If your database reaches its expiration date before your renew your " "subscription, you will encounter this message:" -msgstr "" +msgstr "구독 갱신을 하기 전에 데이터베이스 날짜가 만료되면 다음의 메시지가 표시됩니다." #: ../../content/administration/maintain/on_premise.rst-1 msgid "This database has expired." @@ -5059,12 +5072,14 @@ msgid "" " days. If you fail to take action before the end of the countdown, the " "database is expired." msgstr "" +"이 **차단** 메시지는 차단되지 않는다는 메시지가 30일 동안 표시된 후 나타납니다. 카운트다운이 종료되기 전에 조치를 취하지 않으면 " +"데이터베이스가 만료됩니다." #: ../../content/administration/maintain/on_premise.rst:131 msgid "" "Renew your subscription: follow the link and renew your subscription - note " "that" -msgstr "" +msgstr "구독 갱신: 링크를 따라 가시면 구독을 갱신할 수 있습니다. 다음에 유의하세요." #: ../../content/administration/maintain/on_premise.rst:130 msgid "" @@ -5072,20 +5087,22 @@ msgid "" "renewed only when the payment arrives, which can take a few days. Credit " "card payments are processed immediately." msgstr "" +"온라인 이체 방식으로 결제하는 경우, 구독은 결제 입금 확인이 된 후에만 유효하게 갱신되며, 입금되기까지 며칠 정도 소요될 수 있습니다." +" 신용카드 결제는 즉시 처리됩니다." #: ../../content/administration/maintain/on_premise.rst:133 msgid "Contact our `Support <https://www.odoo.com/help>`__" -msgstr "" +msgstr "`고객 지원 <https://www.odoo.com/help>`__으로 연락하시기 바랍니다." #: ../../content/administration/maintain/on_premise.rst:135 msgid "" "None of those solutions worked for you? Please contact our `Support " "<https://www.odoo.com/help>`__" -msgstr "" +msgstr "꼭 맞는 솔루션을 아직 찾지 못하셨나요? `고객 지원 <https://www.odoo.com/help>`__으로 문의하세요." #: ../../content/administration/maintain/on_premise.rst:143 msgid "Duplicate a database" -msgstr "" +msgstr "데이터베이스 복사" #: ../../content/administration/maintain/on_premise.rst:145 msgid "" @@ -5093,6 +5110,8 @@ msgid "" "server (<odoo-server>/web/database/manager). In this page, you can easily " "duplicate your database (among other things)." msgstr "" +"서버 데이터베이스 관리자(<odoo-server>/web/database/manager)로 액세스하여 데이터베이스를 복사할 수 있습니다." +" 이 페이지에서는 데이터베이스를 쉽게 복사할 수 있습니다 (다른 내용보다도)." #: ../../content/administration/maintain/on_premise.rst:152 msgid "" @@ -5102,6 +5121,9 @@ msgid "" "databases with the same uuid could result in invoicing problems or " "registration problems down the line." msgstr "" +"로컬 데이터베이스를 복사하는 경우, 복사한 데이터베이스의 고유 식별 번호 (UUID: Universally Unique " +"Identifier)를 변경할 것을 **강력** 권장하며, 이는 해당 데이터베이스를 서버에서 식별하는 방법이 UUID이기 때문입니다. " +"동일한 UUID를 가진 두 개의 데이터베이스가 있을 경우 청구서 발행 문제나 등록 문제가 발생할 수 있습니다." #: ../../content/administration/maintain/on_premise.rst:162 msgid "" @@ -5111,10 +5133,13 @@ msgid "" "command ``uuidgen`` to generate a new uuid. You can then simply replace it " "like any other record by clicking on it and using the edit button." msgstr "" +"데이터베이스 UUID는 현재 :menuselection:`설정 --> 기술 --> 시스템 매개변수`에서 액세스할 수 있습니다. `UUID" +" 생성기 <https://www.uuidtools.com>`_를 사용하거나 유닉스 명령어 ``uuidgen``을 사용하여 새로운 " +"UUID를 생성하는 것이 좋습니다. 그런 다음 해당 레코드를 클릭하고 편집 버튼을 사용하여 다른 레코드처럼 간단히 변경할 수 있습니다." #: ../../content/administration/maintain/supported_versions.rst:7 msgid "Supported versions" -msgstr "" +msgstr "지원되는 버전" #: ../../content/administration/maintain/supported_versions.rst:9 msgid "" @@ -5382,7 +5407,7 @@ msgstr "" #: ../../content/administration/maintain/update.rst:6 msgid "Bugfix updates" -msgstr "" +msgstr "버그 수정 업데이트" #: ../../content/administration/maintain/update.rst:9 msgid "Introduction" @@ -5394,6 +5419,8 @@ msgid "" "corrections and performance boosts, you may need to update your Odoo " "installation from time to time." msgstr "" +"최신 개선 내용, 보안 수정, 버그 수정 및 성능 향상을 적용 받는 혜택을 받으려면 가끔씩 Odoo 설치 업데이트를 해야 할 수 " +"있습니다." #: ../../content/administration/maintain/update.rst:14 msgid "" @@ -5401,16 +5428,18 @@ msgid "" "infrastructure. If you are using one of the Odoo Cloud solutions, updates " "are automatically performed for you." msgstr "" +"본 안내 사항은 자체 호스팅 인프라에서 Odoo를 사용하는 경우에만 적용됩니다. Odoo 클라우드 솔루션 중에서 사용하는 경우 업데이트가" +" 자동으로 수행됩니다." #: ../../content/administration/maintain/update.rst:17 msgid "" "The terminology surrounding software updates is often confusing, so here are" " some preliminary definitions:" -msgstr "" +msgstr "소프트웨어 업데이트와 관련된 용어는 혼동되는 경우가 많으므로 다음과 같이 몇 가지 사전 정의를 안내해 드립니다." #: ../../content/administration/maintain/update.rst:25 msgid "Updating (an Odoo installation)" -msgstr "" +msgstr "업데이트 (Odoo 설치)" #: ../../content/administration/maintain/update.rst:21 msgid "" @@ -5426,7 +5455,7 @@ msgstr "" #: ../../content/administration/maintain/update.rst:35 msgid "Upgrading (an Odoo database)" -msgstr "" +msgstr "업그레이드 (Odoo 데이터베이스)" #: ../../content/administration/maintain/update.rst:28 msgid "" @@ -5456,7 +5485,7 @@ msgstr "" #: ../../content/administration/maintain/update.rst:43 msgid "In a nutshell" -msgstr "" +msgstr "한 마디로," #: ../../content/administration/maintain/update.rst:45 msgid "" @@ -5473,12 +5502,14 @@ msgid "" "The main reference for updating is logically our :doc:`installation guide " "<../install>`, which explains the common installation methods." msgstr "" +"업데이트에 대해서 주로 참조하실 수 있는 자료로는 논리적으로 일반적인 설치 방법을 설명하는 :doc:`설치 가이드 " +"<../install>`가 있습니다." #: ../../content/administration/maintain/update.rst:52 msgid "" "Updating is also most appropriately accomplished by the person who deployed " "Odoo initially, because the procedure is very similar." -msgstr "" +msgstr "업데이트 절차는 매우 유사하기 때문에 Odoo를 초기 배포했던 담당자가 수행하는 것이 가장 적절합니다." #: ../../content/administration/maintain/update.rst:55 msgid "" @@ -5494,7 +5525,7 @@ msgstr "" #: ../../content/administration/maintain/update.rst:64 msgid "Step 1: Download an updated Odoo version" -msgstr "" +msgstr "1단계: 업데이트된 Odoo 버전 다운로드하기" #: ../../content/administration/maintain/update.rst:66 msgid "" @@ -5503,22 +5534,24 @@ msgid "" "into Odoo.com with the same login that is linked to your Odoo Enterprise " "subscription." msgstr "" +"메인 다운로드 페이지는 https://www.odoo.com/page/download 입니다. Odoo 엔터프라이즈 다운로드를 하는 " +"\"구매\" 링크가 표시되면 Odoo 엔터프라이즈 구독 항목 연결을 할 때 동일한 로그인으로 Odoo.com에 로그인되었는지 확인하세요." #: ../../content/administration/maintain/update.rst:70 msgid "" "Alternatively, you can use the unique download link that was included with " "your Odoo Enterprise purchase confirmation email." -msgstr "" +msgstr "또는 Odoo 엔터프라이즈 구매 확인 이메일에 있는 고유 다운로드 링크를 사용할 수 있습니다." #: ../../content/administration/maintain/update.rst:73 msgid "" "Downloading an updated version is not necessary if you installed via Github " "(see below)" -msgstr "" +msgstr "Github를 통해 설치한 경우에는 업데이트된 버전을 다운로드할 필요가 없습니다 (아래 내용 참조)." #: ../../content/administration/maintain/update.rst:77 msgid "Step 2: Make a backup of your database" -msgstr "" +msgstr "2단계: 데이터베이스 백업 만들기" #: ../../content/administration/maintain/update.rst:79 msgid "" @@ -5527,6 +5560,8 @@ msgid "" " on your installation, and to store it somewhere safe, on a different " "computer." msgstr "" +"업데이트 절차는 매우 안전하며 데이터를 변경하지 안 됩니다. 그러나 설치 변경을 하기 전에 항상 전체 데이터베이스를 백업한 후 다른 " +"안전한 컴퓨터에 저장하는 것이 가장 좋습니다." #: ../../content/administration/maintain/update.rst:83 msgid "" @@ -5535,18 +5570,21 @@ msgid "" " selection screen) to download a backup of your database(s). If you disabled" " it, use the same procedure than for your usual backups." msgstr "" +"데이터베이스 관리자 화면을 비활성화하지 않은 경우 (해야 하는 이유를 :ref:`여기 <security>`에서 참조), 활성화하여 " +"(데이터베이스 선택 화면 하단에 있는 링크) 데이터베이스 백업을 다운로드할 수 있습니다. 비활성화한 경우에는 일반적인 백업 절차와 " +"동일하게 진행합니다." #: ../../content/administration/maintain/update.rst:89 msgid "Step 3: Install the updated version" -msgstr "" +msgstr "3단계: 업데이트된 버전 설치" #: ../../content/administration/maintain/update.rst:91 msgid "Choose the method that matches your current installation:" -msgstr "" +msgstr "현재 설치할 내용에 맞는 방법을 선택합니다." #: ../../content/administration/maintain/update.rst:95 msgid "Packaged Installers" -msgstr "" +msgstr "설치 패키지 프로그램" #: ../../content/administration/maintain/update.rst:97 msgid "" @@ -5566,7 +5604,7 @@ msgstr "" #: ../../content/administration/maintain/update.rst:106 msgid "Source Install (Tarball)" -msgstr "" +msgstr "설치 소스 (Tarball)" #: ../../content/administration/maintain/update.rst:108 msgid "" @@ -5576,6 +5614,9 @@ msgid "" "daily and include the latest security fixes (see step #1) After downloading " "the package, extract it to a temporary location on your server." msgstr "" +"원래 \"Tarball\" 버전 (소스 코드 아카이브)으로 Odoo를 설치한 경우에는, 설치 디렉토리를 최신 버전으로 바꿔야 합니다. " +"먼저 Odoo.com에서 최신 Tarball을 다운로드합니다. 업데이트는 매일 시행되며 최신 보안 수정 사항이 포함되어 있습니다 (1단계" +" 참조). 패키지를 다운로드한 후 서버의 임시 위치에 압축을 풉니다." #: ../../content/administration/maintain/update.rst:113 msgid "" @@ -5587,6 +5628,10 @@ msgid "" "it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" " just extracted." msgstr "" +"소스 코드 버전이 표시된 폴더가 예를 들어, \"odoo-13.0+e.20190719\"와 같이 생성되며, \"odoo.egg-" +"info\" 폴더와 \"odoo\" (Odoo 10 이상)라는 실제 소스 코드 폴더나 이전 버전의 경우 \"openerp\"라는 이름으로" +" 폴더가 표시됩니다. odoo.egg-info 폴더는 무시해도 됩니다. 현재 설치 중인 내용이 배포된 폴더를 찾아 방금 압축을 푼 " +"아카이브에 있는 최신 \"odoo\" 또는 \"openerp\" 폴더로 바꿉니다." #: ../../content/administration/maintain/update.rst:119 msgid "" @@ -5597,6 +5642,9 @@ msgid "" "the new folder. Finally, restart the Odoo service or reboot the machine, and" " you are all set." msgstr "" +"폴더 레이아웃이 일치하는지 확인합니다. 예를 들어 소스 코드에 포함된 새로운 \"addons\" 폴더는 이전과 동일한 경로에 있어야 " +"합니다. 다음으로, 이전 폴더에서 직접 복사하거나 수정되었을 수 있는 특정 구성 파일을 찾아서 새 폴더에 복사합니다. 마지막으로 Odoo" +" 서비스를 다시 시작하거나 컴퓨터를 재부팅하면 모든 설정이 완료됩니다." #: ../../content/administration/maintain/update.rst:126 msgid "Source Install (Github)" @@ -6271,7 +6319,7 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:76 msgid "Disabling IAP services" -msgstr "" +msgstr "IAP 서비스 비활성화하기" #: ../../content/administration/odoo_sh/getting_started/branches.rst:78 msgid "" @@ -6294,6 +6342,9 @@ msgid "" " Odoo supports to run the unit tests without the demo data, Odoo.sh will " "then consider running the tests on staging databases." msgstr "" +"Odoo에서 단위 테스트는, 현재 프로덕션 데이터베이스에 로드가 되지 않은 데모 데이터에 의존하기 때문에 실행되지 않습니다. 앞으로 " +"Odoo가 데모 데이터 없이 단위 테스트가 실행되도록 지원한다면 Odoo.sh는 스테이징 데이터베이스에서 테스트를 실행하는 것을 " +"고려하겠습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:88 #: ../../content/administration/odoo_sh/getting_started/builds.rst:81 @@ -6308,6 +6359,9 @@ msgid "" "You can change this list of modules to install in your :ref:`project " "Settings <odoosh-gettingstarted-settings-modules-installation>`." msgstr "" +"개발 브랜치에서는 데모 데이터로 새 데이터베이스를 생성하여 단위 테스트를 실행합니다. 설치된 모듈은 브랜치에 있는 모듈입니다. " +":ref:`프로젝트 설정 <odoosh-gettingstarted-settings-modules-installation>`.에서 설치할 " +"모듈 목록을 변경할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:94 msgid "" @@ -6319,6 +6373,10 @@ msgid "" "be run with custom tags in the :ref:`branch's settings <odoosh-" "gettingstarted-branches-tabs-settings>`." msgstr "" +"이와 같은 브랜치 중 하나에 새 커밋을 푸시하면 처음부터 새로 생성되고 브랜치가 변경되어 새 서버가 시작됩니다. 데모 데이터를 블러와서 " +"기본값으로 단위 테스트가 수행됩니다. 이를 통해 변경 사항 때문에 테스트한 기능이 손상되지 않았는지 확인합니다. 원하는 경우 테스트를 " +"비활성화하거나 :ref:`브랜치 설정 <odoosh-gettingstarted-branches-tabs-settings>`에서 사용자 " +"정의 태그를 사용하여 특정 테스트가 실행되도록 허용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:101 msgid "" @@ -6326,6 +6384,8 @@ msgid "" "a mailcatcher and scheduled actions are not triggered as long as the " "database is not in use." msgstr "" +"스테이징 브랜치와 마찬가지로 이메일은 전송되지 않지만 메일 수집기를 이용하여 차단되고 데이터베이스가 사용 중인 경우가 아니면 예약된 " +"작업은 트리거되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:104 msgid "" @@ -6333,34 +6393,36 @@ msgid "" "three days. After that, they can be automatically garbage collected to make " "room for new databases without prior notice." msgstr "" +"개발 브랜치용으로 생성된 데이터베이스는 약 3일 정도 사용할 수 있습니다. 그 후에는 새 데이터베이스를 위한 공간을 확보하기 위해 사전 " +"안내 없이 자동으로 휴지통으로 이동될 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:110 msgid "Merging your branches" -msgstr "" +msgstr "브랜치 병합하기" #: ../../content/administration/odoo_sh/getting_started/branches.rst:112 msgid "" "You can merge your branches easily by drag and dropping them into each " "other." -msgstr "" +msgstr "브랜치를 서로 끌어다 놓는 방식으로 쉽게 병합할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:117 msgid "" "When you want to test the changes of your development branches with the " "production data, you can either:" -msgstr "" +msgstr "프로덕션 데이터를 사용하여 개발 브랜치의 변경 사항을 테스트하려는 경우 다음 중 선택할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:120 msgid "" "merge the development branch into your staging branch, by drag and dropping " "it onto the desired staging branch," -msgstr "" +msgstr "개발 브랜치를 원하는 스테이징 브랜치에 끌어다 놓고 스테이징 브랜치에 병합합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:121 msgid "" "drag and dropping the development branch on the staging section title, to " "make it become a staging branch." -msgstr "" +msgstr "개발 브랜치를 스테이징 섹션 제목에 끌어다 놓아서 스테이징 브랜치가 되도록 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:123 msgid "" @@ -6368,6 +6430,8 @@ msgid "" "your staging branch onto your production branch to merge and deploy in " "production your newest features." msgstr "" +"최근 변경한 내용을 프로덕션에 적용할 준비가 끝나면, 스테이징 브랜치를 프로덕션 브랜치로 끌어다 놓아서 최신 기능을 프로덕션에 병합하고 " +"배포할 수 있게 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:127 msgid "" @@ -6375,12 +6439,14 @@ msgid "" "production branch as well. It just means you skip the validation of your " "changes with the production data through a staging branch." msgstr "" +"과감하게 개발 브랜치를 프로덕션 브랜치에 병합할 수도 있습니다. 이는 스테이징 브랜치로 프로덕션 데이터에 대한 변경 사항 승인을 " +"생략한다는 의미에 불과합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:131 msgid "" "You can merge your development branches into each other, and your staging " "branches into each other." -msgstr "" +msgstr "개발 브랜치를 서로, 또한 스테이징 브랜치를 서로 병합할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:133 msgid "" @@ -6388,6 +6454,8 @@ msgid "" "to merge your branches. Odoo.sh will be notified when new revisions have " "been pushed in your branches." msgstr "" +"물론 워크스테이션에서 직접 :code:`git merge`를 사용하여 브랜치를 병합할 수도 있습니다. 브랜치에 새로운 개정 사항이 " +"푸시되면 Odoo.sh에서 알림을 받게 됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:136 msgid "" @@ -6395,12 +6463,14 @@ msgid "" "code: Any configuration changes you made in the staging databases are not " "passed to the production database." msgstr "" +"프로덕션 브랜치에 스테이징 브랜치를 병합하는 경우 소스 코드만 병합됩니다. 스테이징 데이터베이스에서 변경한 설정 내용은 프로덕션 " +"데이터베이스로 이전되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:139 msgid "" "If you test configuration changes in staging branches, and want them to be " "applied in the production, you have to either:" -msgstr "" +msgstr "스테이징 브랜치에서 환경 설정에서 변경한 사항을 테스트하고 프로덕션에 적용하려면 다음 중에서 선택하여 진행해야 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:141 msgid "" @@ -6412,12 +6482,15 @@ msgid "" "will use the Git versioning features for all your configuration changes, and" " therefore have a traceability for your changes." msgstr "" +"브랜치의 기본 환경 설정이나 기본 화면을 재지정하도록 XML 데이터 파일에 설정 변경 사항을 기재한 다음 매니페스트 " +"(*__manifest__.py*)에서 모듈 버전을 높여서 스테이징 브랜치를 병합할 때 모듈 업데이트가 트리거되도록 합니다. 이는 설정 " +"변경에 Git 버전 관리 기능을 사용하여 변경 사항을 추적할 수 있으므로 개발 확장성을 향상시키는 데 가장 좋은 방법입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:147 msgid "" "pass them manually from your staging to your production database, by " "copy/pasting them." -msgstr "" +msgstr "스테이징에서 프로덕션 데이터베이스로 복사/붙여넣기를 통해 직접 이전합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:152 msgid "Tabs" @@ -6431,17 +6504,17 @@ msgstr "기록" #: ../../content/administration/odoo_sh/getting_started/branches.rst:157 msgid "An overview of your branch history:" -msgstr "" +msgstr "브랜치 이력에 대한 개요:" #: ../../content/administration/odoo_sh/getting_started/branches.rst:159 msgid "The messages of the commits and their authors," -msgstr "" +msgstr "커밋 및 커밋 작성자 메시지," #: ../../content/administration/odoo_sh/getting_started/branches.rst:160 msgid "" "The various events linked to the platform, such as stage changes, database " "imports, backup restores." -msgstr "" +msgstr "스테이지 변경이나 데이터베이스 가져오기, 백업 복원 등 플랫폼과 연결된 다양한 이벤트입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:165 msgid "" @@ -6451,6 +6524,9 @@ msgid "" "successful backup import, ...). When an operation is successful, you can " "access the database thanks to the *connect* button." msgstr "" +"각 이벤트의 상태는 오른쪽 상단 모서리에 표시됩니다. 데이터베이스에서 진행 중인 작업 (설치, 업데이트, 백업 가져오기 등)이나 해당 " +"결과 (테스트 피드백, 백업 가져오기 성공 등)에 대한 정보를 확인할 수 있습니다. 작업이 성공하면 *연결* 버튼을 누르면 데이터베이스에" +" 액세스할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:173 #: ../../content/administration/odoo_sh/getting_started/settings.rst:73 @@ -6465,10 +6541,13 @@ msgid "" "and staging branches as the emails of your production database are really " "sent instead of being intercepted." msgstr "" +"이 탭에는 메일 수집기가 포함되어 있습니다. 여기에서 데이터베이스에서 전송된 이메일에 대한 전반적인 내용을 확인할 수 있습니다. 메일 " +"수집기는 개발 및 스테이징 브랜치에서 사용할 수 있으며 .프로덕션 데이터베이스의 이메일이 남겨져 있는 대신 실제로 전송될 수 있게 " +"됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:184 msgid "Shell" -msgstr "" +msgstr "셸" #: ../../content/administration/odoo_sh/getting_started/branches.rst:186 msgid "" @@ -6476,6 +6555,8 @@ msgid "" "(:code:`ls`, :code:`top`) and open a shell on your database by typing " ":code:`psql`." msgstr "" +"컨테이너에 대한 셸 액세스입니다. 기본 Linux 명령어 (:code:`ls`, :code:`top`)로 진행하고 " +":code:`psql`을 입력하면 데이터베이스에서 셸을 열 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:192 #: ../../content/administration/odoo_sh/getting_started/branches.rst:208 @@ -6483,12 +6564,13 @@ msgid "" "You can open multiple tabs and drag-and-drop them to arrange the layout as " "you wish, for instance side by side." msgstr "" +"탭을 여러 개 열고 드래그 앤 드롭 기능을 통해 원하는 대로 레이아웃을 정렬할 수 있습니다. 예를 들어, 나란히 배치해 보세요." #: ../../content/administration/odoo_sh/getting_started/branches.rst:196 msgid "" "Long running shell instances are not guaranteed. Idle shells can be " "disconnected at anytime in order to free up resources." -msgstr "" +msgstr "셸 인스턴스는 장기적으로 실행되도록 보장되지 않습니다. 유휴 셸은 리소스를 확보하기 위해 언제든지 연결을 끊을 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:200 msgid "Editor" @@ -6499,15 +6581,17 @@ msgid "" "An online integrated development environment (IDE) to edit the source code. " "You can also open terminals, Python consoles and even Odoo Shell consoles." msgstr "" +"소스 코드를 편집할 수 있는 온라인 통합 개발 환경 (IDE)입니다. 터미널, Python 콘솔 및 Odoo 셸 콘솔까지 열 수 " +"있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:212 #: ../../content/administration/odoo_sh/getting_started/settings.rst:105 msgid "Monitoring" -msgstr "" +msgstr "모니터링" #: ../../content/administration/odoo_sh/getting_started/branches.rst:214 msgid "This link contains various monitoring metrics of the current build." -msgstr "" +msgstr "이 링크에는 현재의 빌드에 대한 다양한 모니터링 측정 항목이 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:219 msgid "" @@ -6515,6 +6599,8 @@ msgid "" "graph. On the graphs, annotations help you relate to changes on the build " "(database import, git push, etc...)." msgstr "" +"각 그래프에서 확대/축소하거나, 시간 범위를 변경할 수 있으며, 특정한 측정 항목을 선택할 수 있습니다. 그래프에서 주석으로 빌드 변경 " +"사항 (데이터베이스 가져오기, git push 등)과 관련된 정보를 안내할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:225 #: ../../content/administration/odoo_sh/getting_started/settings.rst:65 @@ -6524,35 +6610,35 @@ msgstr "로그" #: ../../content/administration/odoo_sh/getting_started/branches.rst:227 msgid "A viewer to have a look to your server logs." -msgstr "" +msgstr "뷰어로 서버 로그를 살펴볼 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:232 msgid "Different logs are available:" -msgstr "" +msgstr "다양한 로그를 사용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:234 msgid "" "install.log: The logs of the database installation. In a development branch," " the logs of the tests are included." -msgstr "" +msgstr "install.log: 데이터베이스 설치 로그입니다. 개발 브랜치에는 테스트 로그가 포함되어 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:235 msgid "pip.log: The logs of the Python dependencies installation." -msgstr "" +msgstr "pip.log: Python 종속성 설치 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:236 msgid "odoo.log: The logs of the running server." -msgstr "" +msgstr "odoo.log: 실행 중인 서버의 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:237 msgid "update.log: The logs of the database updates." -msgstr "" +msgstr "update.log: 데이터베이스 업데이트 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:238 msgid "" "pg_long_queries.log: The logs of psql queries that take an unusual amount of" " time." -msgstr "" +msgstr "pg_long_queries.log: 소요 시간이 비정상적인 psql 쿼리의 로그입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:240 msgid "" @@ -6560,6 +6646,8 @@ msgid "" " you scroll to the bottom, the browser will scroll automatically each time a" " new line is added." msgstr "" +"로그에 새로운 줄이 추가되면 자동으로 표시됩니다. 맨 아래로 스크롤을 이동하면 새 줄이 추가될 때마다 브라우저가 자동으로 스크롤이 " +"이동됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:243 msgid "" @@ -6567,17 +6655,19 @@ msgid "" "upper right corner of the view. The fetching is automatically stopped after " "5 minutes. You can restart it using the play button." msgstr "" +"화면에서 오른쪽 상단에 있는 해당 버튼을 클릭하면 로그 가져오기를 일시 중지할 수 있습니다. 로그 가져오기는 5분 후에 자동으로 " +"중지됩니다. 재생 버튼을 사용하여 다시 시작할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:249 #: ../../content/administration/odoo_sh/getting_started/settings.rst:109 msgid "Backups" -msgstr "" +msgstr "백업" #: ../../content/administration/odoo_sh/getting_started/branches.rst:251 msgid "" "A list of the backups available for download and restore, the ability to " "perform a manual backup and to import a database." -msgstr "" +msgstr "다운로드 및 복원할 수 있는 백업 목록, 수동 백업 수행 및 데이터베이스 가져오기 기능입니다" #: ../../content/administration/odoo_sh/getting_started/branches.rst:257 msgid "" @@ -6585,6 +6675,8 @@ msgid "" "weekly and 3 monthly backups. Each backup includes the database dump, the " "filestore (attachments, binary fields), logs and sessions." msgstr "" +"Odoo.sh에서는 프로덕션 데이터베이스가 매일 백업됩니다. 매일 7회, 매주 4회, 매월 3회 백업이 진행됩니다. 백업에는 데이터베이스" +" 덤프, 파일 저장소(첨부 파일, 바이너리 필드), 로그 및 세션을 포함하여 백업됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:260 msgid "" @@ -6593,6 +6685,8 @@ msgid "" "staging branches, for testing purposes, or to manually recover data that has" " been deleted by accident from the production database." msgstr "" +"스테이징 및 개발 데이터베이스는 백업되지 않습니다. 다만 스테이징 브랜치에서 테스트 목적으로 프로덕션 데이터베이스의 백업을 복원하거나 " +"프로덕션 데이터베이스에서 실수로 삭제된 데이터는 수기로 복구할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:264 msgid "" @@ -6600,6 +6694,8 @@ msgid "" " hosted on. This server only keeps one month of backups: 7 daily and 4 " "weekly backups." msgstr "" +"이 목록에는 프로덕션 데이터베이스가 호스팅되는 서버에 보관된 백업이 포함되어 있습니다. 서버에는 한 달 분량의 백업으로 일일 7회 백업," +" 주간 4회 백업만 보관됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:267 msgid "" @@ -6607,6 +6703,8 @@ msgid "" "monthly backups. To restore or download one of these monthly backups, please" " `contact us <https://www.odoo.com/help>`_." msgstr "" +"전용 백업 서버는 백업을 동일하게 진행하되 월간 3회를 추가로 백업합니다. 월별 백업 중 하나를 복원하거나 다운로드하려면 `문의하기 " +"<https://www.odoo.com/help>`_로 연락주시기 바랍니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:270 msgid "" @@ -6642,35 +6740,37 @@ msgstr "" msgid "" "The *import database* feature accepts database archives in the format " "provided by:" -msgstr "" +msgstr "*데이터베이스 가져오기* 기능을 통해 다음 형식으로 데이터베이스에 보관할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:284 msgid "" "the standard Odoo databases manager, (available for on-premise Odoo servers " "under :code:`/web/database/manager`)" msgstr "" +"표준 Odoo 데이터베이스 관리자 (:code:`/web/database/manager` 아래에 있는 Odoo 온프레미스 서버에서 사용 " +"가능)" #: ../../content/administration/odoo_sh/getting_started/branches.rst:286 msgid "the Odoo online databases manager," -msgstr "" +msgstr "Odoo 온라인 데이터베이스 관리자," #: ../../content/administration/odoo_sh/getting_started/branches.rst:287 msgid "the Odoo.sh backup download button of this *Backups* tab," -msgstr "" +msgstr "이 *백업* 탭에 있는 Odoo.sh 백업 다운로드 버튼," #: ../../content/administration/odoo_sh/getting_started/branches.rst:288 msgid "" "the Odoo.sh dump download button in the :ref:`Builds view <odoosh-" "gettingstarted-builds>`." -msgstr "" +msgstr ":ref:`빌드 화면 <odoosh-gettingstarted-builds>`에 있는 Odoo.sh 덤프 다운로드 버튼." #: ../../content/administration/odoo_sh/getting_started/branches.rst:295 msgid "Available for production and staging branches for valid projects." -msgstr "" +msgstr "유효한 프로젝트에서 프로덕션 및 스테이징 브랜치에 사용할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:298 msgid ":doc:`Upgrade documentation <../../upgrade>`" -msgstr "" +msgstr ":doc:`업그레이드 문서 <../../upgrade>`" #: ../../content/administration/odoo_sh/getting_started/branches.rst:303 #: ../../content/administration/odoo_sh/getting_started/settings.rst:3 @@ -6684,11 +6784,11 @@ msgstr "설정" msgid "" "Here you can find a couple of settings that only apply to the currently " "selected branch." -msgstr "" +msgstr "여기에는 현재 선택한 브랜치에만 적용되는 설정이 몇 가지 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:310 msgid "**Behaviour upon new commit**" -msgstr "" +msgstr "**새로운 커밋에 대한 동작**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:312 msgid "" @@ -6702,15 +6802,20 @@ msgid "" " the production build every time a commit is pushed. A branch that is put " "back from staging to development will automatically be set to 'Do nothing'." msgstr "" +"개발 브랜치 및 스테이징 브랜치의 경우 새로운 커밋을 받으면 브랜치의 동작을 변경할 수 있습니다. 기본적으로, 개발 브랜치는 새 빌드를 " +"생성하고 스테이징 브랜치는 이전 빌드를 업데이트합니다 (:ref:`프로덕션 단계 <stage_production>` 참조). 이 기능은 " +"작업 중인 기능에 특정한 설정이나 환경 설정이 필요한 경우 커밋할 때마다 직접 다시 설정할 필요가 없으므로 특히 유용합니다. 스테이징 " +"브랜치에 새 빌드를 선택하면 커밋이 푸시될 때마다 프로덕션 빌드에서 새로 복사본이 만들어집니다. 스테이징에서 개발로 되돌려진 브랜치는 " +"자동으로 '아무 것도 하지 않음'으로 설정됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:320 msgid "**Modules installation**" -msgstr "" +msgstr "**모듈 설치**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:322 msgid "" "Choose the modules to install automatically for your development builds." -msgstr "" +msgstr "개발 빌드에 자동으로 설치할 모듈을 선택합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:327 msgid "" @@ -6718,6 +6823,8 @@ msgid "" "is the default option. The :ref:`submodules <odoosh-advanced-submodules>` " "are excluded." msgstr "" +"*내 모듈만 설치*는 해당하는 브랜치의 모듈만 설치합니다. 기본 선택 사항입니다. :ref:`하위 모듈 <odoosh-advanced-" +"submodules>`은 제외됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:329 msgid "" @@ -6725,6 +6832,8 @@ msgid "" "the modules included in the submodules and all standard modules of Odoo. " "When running the full installation, the test suite is disabled." msgstr "" +"*전체 설치 (모든 모듈)*는 브랜치의 모듈, 하위 모듈에 포함된 모듈 및 Odoo의 모든 표준 모듈을 설치합니다. 전체 설치를 실행하면" +" 테스트 도구 모음이 비활성화됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:331 msgid "" @@ -6732,6 +6841,7 @@ msgid "" "just below this option. The names are the technical name of the modules, and" " they must be comma-separated." msgstr "" +"*모듈 목록 설치*는 이 옵션의 바로 아래 입력란에 지정되어 있는 모듈을 설치합니다. 이름은 모듈의 기술명이며 쉼표로 구분되어야 합니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:334 msgid "" @@ -6739,10 +6849,12 @@ msgid "" "hour. This setting applies to development builds only. Staging builds " "duplicate the production build and the production build only installs base." msgstr "" +"테스트를 활성화하게 되면 표준 Odoo 모듈 제품군의 경우 최대 1시간까지 소요될 수 있습니다. 개발 빌드에만 이 설정이 적용됩니다. " +"스테이징 빌드는 프로덕션 빌드와 복제되고 프로덕션 빌드는 기본으로만 설치됩니다. " #: ../../content/administration/odoo_sh/getting_started/branches.rst:339 msgid "**Test suite**" -msgstr "" +msgstr "**테스트 도구 모음**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:341 msgid "" @@ -6751,10 +6863,13 @@ msgid "" "restrict them by specifying test tags :ref:`test tags " "<developer/reference/testing/selection>`." msgstr "" +"개발 브랜치의 경우 테스트 도구 모음을 사용 또는 사용하지 않도록 선택할 수 있습니다. 사용하는 것이 기본값으로 되어 있습니다. 테스트 " +"도구 모음이 활성화된 경우 :ref:`태그 테스트<developer/reference/testing/selection>`를 지정하여 " +"제한할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:345 msgid "**Odoo Version**" -msgstr "" +msgstr "**Odoo 버전**" #: ../../content/administration/odoo_sh/getting_started/branches.rst:347 msgid "" @@ -6762,12 +6877,14 @@ msgid "" "you want to test upgraded code or develop features while your production " "database is in the process of being upgraded to a newer version." msgstr "" +"개발 브랜치에 한해, 프로덕션 데이터베이스가 최신 버전으로 업그레이드되는 동안 업그레이드된 코드를 테스트하거나 기능을 개발하려는 경우에 " +"Odoo 버전을 변경할 수 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:350 msgid "" "In addition, for each version you have two options regarding the code " "update." -msgstr "" +msgstr "또한 각 버전별로 코드 업데이트와 관련된 옵션이 두 가지 있습니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:352 msgid "" @@ -6775,6 +6892,8 @@ msgid "" "fixes automatically. The sources of your Odoo server will be updated weekly." " This is the 'Latest' option." msgstr "" +"최신 버그, 보안 및 성능 수정 사항이 자동으로 적용되도록 선택할 수 있습니다. Odoo 서버의 소스는 매주 업데이트됩니다. 현재는 " +"'최신' 상태입니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:354 msgid "" @@ -6783,6 +6902,8 @@ msgid "" " notified by mail when the expiration date approaches and if you don't take " "action afterwards, you will automatically be set to the latest revision." msgstr "" +"날짜 목록에서 Odoo 소스를 선택하여 특정한 개정판에 핀고정하도록 선택할 수 있습니다. 개정판은 3개월 후에 만료됩니다. 만료일에 " +"가까워지면 메일로 알림을 받게 되며 이후에도 아무 조치를 취하지 않을 경우 자동으로 최신 개정판으로 설정됩니다." #: ../../content/administration/odoo_sh/getting_started/branches.rst:359 msgid "**Custom domains**" @@ -7139,6 +7260,8 @@ msgid "" "is considered almost successful. It is highlighted in yellow to notify the " "developer warnings were raised." msgstr "" +"생성 중에 경고가 표시되더라도 오류가 없으면 빌드가 거의 성공한 것으로 간주합니다. 개발자에게 경고가 발생했음을 알리기 위해 노란색으로 " +"강조 표시됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:35 msgid "" @@ -7148,6 +7271,9 @@ msgid "" "database on it. If no errors come up, the build is considered successful, " "and otherwise failed." msgstr "" +"빌드에서 항상 기초부터 데이터베이스가 생성되는 것은 아닙니다. 예를 들어, 프로덕션 브랜치에 변경 사항을 적용할 때 생성된 빌드로는 " +"새로운 개정판으로 서버가 시작되고 여기에 현재 프로덕션 데이터베이스를 로드하려고 시도합니다. 오류가 발생하지 않으면 빌드가 성공한 것으로" +" 간주되고 그렇지 않으면 실패한 것으로 간주됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:46 msgid "" @@ -7155,12 +7281,14 @@ msgid "" "this build is successful, this database is considered as the production " "database of your project." msgstr "" +"프로덕션 브랜치의 첫 번째 빌드는 기초부터 데이터베이스를 생성합니다. 이 빌드가 성공하면 데이터베이스는 프로젝트의 프로덕션 데이터베이스로" +" 간주됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:49 msgid "" "From then, pushes on the production branch will create new builds that " "attempt to load the database using a server running with the new revision." -msgstr "" +msgstr "그런 다음 프로덕션 브랜치를 적용하면 새 개정판으로 실행되는 서버에서 데이터베이스를 로드하는 새로운 빌드가 생성됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:52 msgid "" @@ -7168,6 +7296,7 @@ msgid "" "database will now run with this build, along with the revision associated to" " this build." msgstr "" +"빌드가 성공했거나, 경고는 있으나 오류가 없는 경우 프로덕션 데이터베이스는 이제 해당 빌드에 연결된 개정판과 함께 이 빌드로 실행됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:55 msgid "" @@ -7175,6 +7304,8 @@ msgid "" "successful build is re-used to load the database, and therefore the database" " will run using a server running with the previous successful revision." msgstr "" +"빌드에서 데이터베이스를 로드하거나 업데이트하는 데 실패하면 이전에 성공한 빌드로 다시 데이터베이스를 로드하므로 데이터베이스는 이전에 " +"성공한 개정판으로 실행되는 서버에서 실행됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:59 msgid "" @@ -7182,12 +7313,14 @@ msgid "" "builds list. If a build fails, it is put after the build currently running " "the production database." msgstr "" +"프로덕션 데이터베이스 실행에 사용되는 빌드는 항상 빌드 목록의 첫 번째에 위치합니다. 빌드가 실패하면 현재 프로덕션 데이터베이스를 실행 " +"중인 빌드 뒤에 배치됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:65 msgid "" "Staging builds duplicate the production database, and try to load this " "duplicate with the revisions of the staging branches." -msgstr "" +msgstr "스테이징 브랜치는 프로덕션 데이터베이스를 복제하고 해당 복제본을 스테이징 브랜치의 개정판과 함께 로드하게 됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:68 msgid "" @@ -7195,12 +7328,14 @@ msgid "" "uses a new copy of the production database. The databases are not re-used " "between builds of the same branch. This ensures:" msgstr "" +"스테이징 브랜치에 새 개정판을 적용할 때마다 생성된 빌드는 프로덕션 데이터베이스의 새 복사본을 사용합니다. 데이터베이스는 동일한 브랜치에" +" 있는 빌드 사이에는 재사용되지 않습니다. 이를 통해 다음과 같은 내용이 보장됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:71 msgid "" "staging builds use databases that are close to what the production looks " "like, so you do not make your tests with outdated data," -msgstr "" +msgstr "스테이징 빌드는 프로덕션 환경과 유사한 데이터베이스를 사용하므로 오래된 데이터로 테스트를 만들지 않습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:74 msgid "" @@ -7208,6 +7343,8 @@ msgid "" "you can then ask for a rebuild when you want to restart with a new copy of " "the production." msgstr "" +"동일한 스테이징 데이터베이스에서 마음껏 작업을 수행할 수 있으며, 프로덕션의 새 복사본으로 다시 시작하려는 경우 다시 빌드를 요청할 수 " +"있습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:77 msgid "" @@ -7215,12 +7352,14 @@ msgid "" "databases and do not apply them in the production, they will not be passed " "on the next build of the same staging branch." msgstr "" +"그럼에도 불구하고 스테이징 데이터베이스에서 환경 설정을 변경한 후 프로덕션에 적용하지 않으면 동일한 스테이징 브랜치의 다음 빌드로 " +"이전되지 않습니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:83 msgid "" "Development builds create new databases, load the demo data and run the unit" " tests." -msgstr "" +msgstr "개발 빌드는 새 데이터베이스 생성, 데모 데이터 로드 및 단위 테스트 실행을 하게 됩니다." #: ../../content/administration/odoo_sh/getting_started/builds.rst:85 msgid "" @@ -9108,6 +9247,8 @@ msgid "" "provides important information about the changes introduced by the new " "version." msgstr "" +"업그레이드 요청이 완료되면 업그레이드 성공 안내 이메일에 업그레이드 보고서가 첨부되며 \"관리/설정\" 그룹에 속한 사용자는 메일 및 " +"채팅 앱에서 해당 보고서를 확인할 수 있습니다. 이 보고서에는 새 버전 도입으로 인한 변경 사항과 관련된 중요한 정보를 제공합니다." #: ../../content/administration/upgrade.rst:198 msgid "Testing the new version of the database" @@ -9355,6 +9496,9 @@ msgid "" "takes a long time to finish. **Fully rehearsing the upgrade process the day " "before upgrading the production database is also recommended.**" msgstr "" +"표준 업그레이드 스크립트 및 데이터베이스가 계속하여 발전하고 있으므로 업그레이드 프로세스가 성공적으로 완료될 수 있도록, 특히 완료하는 " +"데 시간이 오래 걸리는 경우에는 업그레이드된 테스트 데이터베이스를 자주 요청하는 것이 좋습니다. **프로덕션 데이터베이스를 업그레이드하기" +" 전날 업그레이드 프로세스를 충분히 테스트해보는 것도 좋습니다.**" #: ../../content/administration/upgrade.rst:296 msgid "Going into production without first testing may lead to:" @@ -9435,6 +9579,9 @@ msgid "" "how to upgrade your custom modules can be found on " ":doc:`/developer/howtos/upgrade_custom_db`." msgstr "" +"전체 업그레이드 프로세스를 완료하려면 커스텀 모듈의 업데이트가 성공해야 합니다. 프로덕션 환경에서 시도하기 전에 스테이지 업그레이드의 " +"상태가 :guilabel:`성공`인지 확인하세요. 사용자 정의 모델을 업그레이드하는 자세한 방법은 " +":doc:`/developer/howtos/upgrade_custom_db`에서 확인하실 수 있습니다." #: ../../content/administration/upgrade.rst:343 msgid "" @@ -9442,6 +9589,8 @@ msgid "" "upgrading a test database except for the argument `test`, which must be " "replaced by `production`:" msgstr "" +"데이터베이스를 프로덕션으로 업그레이드하는 명령어는 테스트 데이터베이스를 업그레이드하는 명령어와 유사하며 반드시 `test` 인수를 " +"`production`으로 대체해야 합니다." #: ../../content/administration/upgrade.rst:350 msgid "" @@ -9451,6 +9600,9 @@ msgid "" "upgraded database. This is why we recommend not using it during the upgrade " "process." msgstr "" +"프로덕션 데이터베이스 업그레이드는 '업그레이드 페이지<https://upgrade.odoo.com/>`_를 통해서도 요청할 수 있습니다." +" 데이터베이스가 업로드되면 프로덕션 데이터베이스에 대한 수정 사항은 업그레이드된 데이터베이스에 나타나지 **않습니다**. 그렇기 때문에 " +"업그레이드 프로세스 중에는 사용하지 않는 것이 좋습니다." #: ../../content/administration/upgrade.rst:357 msgid "" @@ -9459,6 +9611,8 @@ msgid "" "must be merged with the production filestore before deploying the new " "version." msgstr "" +"프로덕션 목적으로 업그레이드된 데이터베이스를 요청할 경우 파일 저장소 없이 복사본이 제출됩니다. 따라서 새 버전을 배포하기 전에 " +"업그레이드된 데이터베이스 파일 저장소를 프로덕션 파일 저장소와 병합해야 합니다." #: ../../content/administration/upgrade.rst:361 msgid "" diff --git a/locale/ko/LC_MESSAGES/finance.po b/locale/ko/LC_MESSAGES/finance.po index 3042dde84..0aeebfdf5 100644 --- a/locale/ko/LC_MESSAGES/finance.po +++ b/locale/ko/LC_MESSAGES/finance.po @@ -23349,22 +23349,23 @@ msgid "" "Then, to configure the connection itself, go to :menuselection:`Accounting " "--> Configuration --> Accounting: CodaBox`." msgstr "" +"그런 다음 연결 자체를 설정하려면 :menuselection:`회계 --> 환경 설정 --> 회계: CodaBox`로 이동합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:309 msgid "" "The procedure differs depending on whether **CodaBox** is being setup for a " "first client or an additional one." -msgstr "" +msgstr "**CodaBox** 설정 대상이 첫 번째 클라이언트인지 아니면 추가 클라이언트인지에 따라 절차가 달라집니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 msgid "First connection" -msgstr "" +msgstr "처음으로 연결하기" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:316 msgid "" "Click on :guilabel:`Connect`, where you are redirected to the **CodaBox** " "platform, here validate the connection." -msgstr "" +msgstr ":guilabel:`연결`을 클릭하면 **CodaBox** 플랫폼으로 리디렉션되며, 여기서 연결의 유효성을 검사합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:318 msgid "" @@ -23372,28 +23373,30 @@ msgid "" ":guilabel:`Connected` and a new field :guilabel:`Access Token` should " "appear." msgstr "" +"Odoo로 다시 리디렉션되면 :guilabel:`상태`가 :guilabel:`연결 완료`로 설정되고 새로운 필드로 " +":guilabel:`액세스 토큰`이 나타납니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 msgid "Configured connection." -msgstr "" +msgstr "연결 설정이 완료되었습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 msgid "" "This :guilabel:`Access Token` will be used to create new connections for " "other clients without having to validate the connection again." -msgstr "" +msgstr "이 :guilabel:`액세스 토큰`을 이용하여 연결을 다시 검증할 필요 없이 다른 클라이언트가 새로 연결할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:329 msgid "Following connection" -msgstr "" +msgstr "다음 연결" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:331 msgid "Copy the :guilabel:`Access Token` from a previous connection." -msgstr "" +msgstr "이전 연결에서 :guilabel:`액세스 토큰`을 복사합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 msgid "Click on :guilabel:`Connect`." -msgstr "" +msgstr ":guilabel:`연결`을 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 msgid "" @@ -23402,6 +23405,8 @@ msgid "" "new and different :guilabel:`Access Token` is generated, and the " ":guilabel:`Status` should be set to :guilabel:`Connected`." msgstr "" +":guilabel:`액세스 토큰`에 연결된 **CodaBox** 연결은 여전히 존재하므로 연결의 유효성을 다시 검사할 필요가 없습니다. " +"다른 :guilabel:`액세스 토큰`을 새로 생성하고 :guilabel:`상태`를 :guilabel:`연결 완료`로 설정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:340 msgid "" @@ -23409,15 +23414,17 @@ msgid "" "easily revoke the access of a client to your CodaBox account without " "affecting the other clients. One client cannot interfere with another." msgstr "" +"클라이언트별로 대해 다른 :guilabel:`액세스 토큰`을 사용하면 다른 클라이언트에 영향을 주지 않으면서도 클라이언트의 CodaBox" +" 계정 접근 권한을 쉽게 취소할 수 있습니다. 클라이언트는 다른 클라이언트를 간섭할 수 없습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 msgid "Synchronisation" -msgstr "" +msgstr "동기화" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:347 msgid "" "Once the connection is established, Odoo can be synchronized with CodaBox." -msgstr "" +msgstr "연결이 설정되면 Odoo를 CodaBox와 동기화할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:353 msgid "" @@ -23425,10 +23432,12 @@ msgid "" "not have to do anything. However, if you wish, it can also be done manually," " by clicking on :guilabel:`Fetch CODA's` in the Accounting Dashboard." msgstr "" +"CODA 파일을 CodaBox에서 12시간마다 자동으로 가져옵니다. 사용자는 아무것도 할 필요가 없습니다. 그러나 원하는 경우 계정 " +"현황판에서 :guilabel:`CODA 가져오기`를 클릭하여 직접 할 수도 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 msgid "Manually fetch CODA's." -msgstr "" +msgstr "CODA를 직접 가져옵니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:363 msgid "" @@ -23437,6 +23446,8 @@ msgid "" "manually, by clicking on :guilabel:`Fetch SODA's` in the Accounting " "Dashboard." msgstr "" +"SODA 파일은 CodaBox에서 하루에 한 번 자동으로 초안 상태로 가져옵니다. 아무것도 할 필요가 없습니다. 그러나 원하는 경우 계정" +" 현황판에서 :guilabel:`SODA 가져오기`를 클릭하여 직접 가져올 수도 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 msgid "" @@ -23444,10 +23455,12 @@ msgid "" "the Suspense Account (499000) is used and a note is left in the created " "journal entry." msgstr "" +"기본적으로 SODA의 계정이 Odoo 계정에 매핑되지 않은 경우, 가계정 (499000)을 사용하며 전표 생성 항목에 메모를 남기게 " +"됩니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 msgid "Manually fetch SODA's." -msgstr "" +msgstr "SODA를 직접 가져옵니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 msgid "" @@ -23455,6 +23468,8 @@ msgid "" "by clicking on the :guilabel:`SODA Mapping` button in " ":menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." msgstr "" +":menuselection:`회계 --> 환경 설정 --> 회계: CodaBox`에서 :guilabel:`SODA 매핑` 버튼을 클릭하여" +" SODA 계정과 Odoo 계정 간 매핑에 액세스할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:380 msgid "" @@ -23462,6 +23477,8 @@ msgid "" ":guilabel:`Revoke` button in the CodaBox settings, which will revoke the " "link on Odoo's side only." msgstr "" +"Odoo와 CodaBox 간의 연결은 CodaBox 설정에서 :guilabel:`취소` 버튼으로 취소할 수 있으며, 이 경우 Odoo " +"측의 링크만 취소됩니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:384 msgid "" @@ -23469,6 +23486,8 @@ msgid "" "Token of one of them to easily reconnect Odoo and CodaBox for another " "client." msgstr "" +"연결이 여러 개 있는 경우, 그 중 하나의 액세스 토큰을 사용하여 다른 클라이언트를 위해 Odoo와 CodaBox를 쉽게 다시 연결할 수" +" 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:388 msgid "" @@ -23478,56 +23497,59 @@ msgid "" "recreate a new one following the steps in the :ref:`first connection " "<belgium/codabox-configuration-connection>` section." msgstr "" +"그러나 연결이 하나만 있는 경우 (남아 있는 경우) , 해당하는 액세스 토큰을 사용하여 새로 연결할 수 있습니다. 이 경우, " +"CodaBox 플랫폼 연결도 해지한 다음 :ref:`첫 번째 연결 <belgium/codabox-configuration-" +"connection>` 섹션에 있는 단계에 따라 다시 새로 연결을 해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 msgid "Potential issues" -msgstr "" +msgstr "잠재적 문제점" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 msgid "CodaBox is not configured. Please check your configuration." -msgstr "" +msgstr "CodaBox가 구성되지 않았습니다. 환경 설정 내용을 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 msgid "Either the Company VAT of the Accounting Firm VAT is not set." -msgstr "" +msgstr "회계법인 부가가치세의 회사 부가세가 설정되어 있지 않습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 msgid "" "It seems that the fiduciary VAT number you provided is not valid. Please " "check your configuration." -msgstr "" +msgstr "입력한 신탁사 부가가치세 번호가 유효하지 않습니다. 설정을 확인해 주세요." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 msgid "" "Either the Company VAT of the Accounting Firm VAT is in the wrong format." -msgstr "" +msgstr "회계법인 부가가치세의 회사 부가세 형식이 잘못되었습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 msgid "" "It seems that the fiduciary VAT number you provided does not exist in " "CodaBox. Please check your configuration." -msgstr "" +msgstr "입력하신 신탁사 부가세 번호가 CodaBox에 없습니다. 설정을 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 msgid "" "The Accounting Firm VAT number you provided is not registered in CodaBox." -msgstr "" +msgstr "입력하신 회계법인 부가세 번호가 CodaBox에 등록되어 있지 않습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 msgid "Error while connecting to the IAP server. Please contact Odoo support." -msgstr "" +msgstr "IAP 서버에 연결하는 동안 오류가 발생했습니다. Odoo 지원팀에 문의합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:407 msgid "" "It seems that Odoo's IAP server is down or unreachable. Please contact Odoo " "support." -msgstr "" +msgstr "Odoo의 IAP 서버가 다운되었거나 연결할 수 없습니다. Odoo 지원팀에 문의합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:414 msgid "" "It seems that your CodaBox connection is not valid anymore. Please check " "your configuration." -msgstr "" +msgstr "CodaBox 연결이 더 이상 유효하지 않습니다. 설정을 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 msgid "" @@ -23537,6 +23559,9 @@ msgid "" "settings, and follow again the steps in the :ref:`first connection " "<belgium/codabox-configuration-connection>` section." msgstr "" +"CodaBox 계정에 대한 Odoo의 접근 권한이 취소되었거나 설정 프로세스가 완료되지 않았습니다. 이 경우 설정에서 " +":guilabel:`연결 취소` 버튼을 클릭한 후 :ref:`첫 번째 연결 <belgium/codabox-configuration-" +"connection>` 섹션의 단계를 다시 따라야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:423 msgid "" @@ -23544,6 +23569,8 @@ msgid "" "a previous connection here. Odoo will generate a new one, exclusive to this " "database." msgstr "" +"이전 CodaBox가 이미 등록되어 있습니다. 이전 연결의 액세스 토큰을 여기에 붙여넣으세요. Odoo가 이 데이터베이스 전용으로 새로 " +"토큰을 생성합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 msgid "" @@ -23552,6 +23579,8 @@ msgid "" "the :ref:`following connection <belgium/codabox-configuration-connection>` " "tab section." msgstr "" +"Odoo에 이미 거래하는 회계법인이 있으나 액세스 토큰이 채워져 있지 않거나 잘못된 것 같습니다. :ref:`다음 연결 " +"<belgium/codabox-configuration-connection>` 탭 섹션의 단계를 따라야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 msgid "" @@ -23560,6 +23589,8 @@ msgid "" "to follow the steps in the :ref:`first connection <belgium/codabox-" "configuration-connection>` section." msgstr "" +"액세스 토큰을 실패한 경우, CodaBox 플랫폼으로 이동하여 Odoo의 CodaBox 계정 액세스 권한을 취소해야 합니다. 그런 다음 " +":ref:`첫 번째 연결 <belgium/codabox-configuration-connection>`` 섹션의 단계를 따라야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 msgid "" @@ -23567,16 +23598,17 @@ msgid "" " configuration. If you have lost your access token, please contact Odoo " "support." msgstr "" +"제공된 액세스 토큰이 이 신탁사에 대해 유효하지 않습니다. 설정을 확인합니다. 액세스 토큰이 실패된 경우 Odoo 지원팀에 문의합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 msgid "Same as above." -msgstr "" +msgstr "위와 동일합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:433 msgid "" "It seems that no connection linked to your database/VAT number exists. " "Please check your configuration." -msgstr "" +msgstr "데이터베이스/부가세 번호에 링크된 연결이 없습니다. 설정을 확인해 주세요." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 msgid "" @@ -23587,10 +23619,14 @@ msgid "" "recreate a connection for this company VAT by following the steps in the " ":ref:`first connection <belgium/codabox-configuration-connection>` section." msgstr "" +"그룹 (회계법인 부가세, 회사 부가세)이 등록되기 전에 CodaBox에서 파일을 해지하거나 가져오려고 하면 이같은 오류가 발생할 수 " +"있습니다. 예를 들어 연결 설정을 한 후에 회사 부가세 번호가 변경된 경우에 이러한 오류가 발생할 수 있습니다. 보안상의 이유로 " +":ref:`첫 번째 연결 <belgium/codabox-configuration-connection>` 섹션의 단계에 따라 회사 부가세 " +"번호를 다시 연결해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:438 msgid "No files were found. Please check your configuration." -msgstr "" +msgstr "파일을 찾을 수 없습니다. 설정을 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 msgid "" @@ -23598,6 +23634,8 @@ msgid "" "established. In that case, you must click on the :guilabel:`Revoke " "connection` button in the settings, and recreate the connection." msgstr "" +"이러한 문제는 연결이 설정된 후 회사 부가세 번호가 변경된 경우 발생할 수 있습니다. 이 경우 설정에서 :guilabel:`연결 취소` " +"버튼을 클릭하고 다시 연결해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:443 msgid "" @@ -23605,6 +23643,7 @@ msgid "" "fiduciary. To create a new connection, you must first revoke the old one on " "myCodaBox portal." msgstr "" +"이 신탁사는 이미 CodaBox에 연결되어 있습니다. 새로 연결하려면 먼저 myCodaBox 포털에서 이전 연결을 해지해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:441 msgid "" @@ -23612,6 +23651,8 @@ msgid "" "CodaBox account. Then, you will have to follow the steps in the :ref:`first " "connection <belgium/codabox-configuration-connection>` section." msgstr "" +"반드시 CodaBox 플랫폼으로 이동하여 Odoo의 CodaBox 계정 접근 권한을 취소해야 합니다. 그런 다음 :ref:`첫 번째 연결" +" <belgium/codabox-configuration-connection>` 섹션의 단계를 따라야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:446 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 @@ -23627,6 +23668,9 @@ msgid "" ":guilabel:`Accounting` tab, select the :guilabel:`Peppol BIS Billing 3.0` " "format." msgstr "" +"Odoo에서는 **Peppol BIS Billing 3.0(UBL)** 전자 청구서 형식이 지원됩니다. 고객을 활성화하려면 " +":menuselection:`회계 --> 고객 --> 고객`으로 이동하여 문의 양식을 열고 :guilabel:`회계` 탭에서 " +":guilabel:`Peppol BIS Billing 3.0` 형식을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:453 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 @@ -23636,7 +23680,7 @@ msgstr ":doc:`../accounting/customer_invoices/electronic_invoicing`" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 msgid "Cash discount" -msgstr "" +msgstr "현금 할인" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:460 msgid "" @@ -23644,12 +23688,15 @@ msgid "" "is calculated based on the discounted total amount, whether the customer " "benefits from the discount or not." msgstr "" +"벨기에에서는 청구서에 조기 결제 할인이 적용된 경우, 고객이 할인을 받았는지 여부에 관계없이 할인된 총 금액을 기준으로 세금이 " +"계산됩니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 msgid "" "To apply the right tax amount and report it correctly in your VAT return, " "set the tax reduction as :guilabel:`Always (upon invoice)`." msgstr "" +"세액을 올바르게 적용하여 부가가치세 신고서에 정확하게 신고하려면 세금 감면을 :guilabel:`항상 (청구 당시)`로 설정합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:467 msgid ":doc:`../accounting/customer_invoices/cash_discounts`" @@ -23657,7 +23704,7 @@ msgstr ":doc:`../accounting/customer_invoices/cash_discounts`" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 msgid "Fiscal certification: POS restaurant" -msgstr "" +msgstr "재정 인증: POS 레스토랑" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:474 msgid "" @@ -23666,6 +23713,8 @@ msgid "" "System** for their receipts. This applies if their yearly earnings " "(excluding VAT, drinks, and take-away food) exceed 25,000 euros." msgstr "" +"벨기에에서는 레스토랑이나 푸드트럭 등 요식업 사업자는 정부가 인증한 **현금 등록 시스템**을 사용하여 결제를 받도록 법으로 규정하고 " +"있습니다. 이는 연간 수입 (부가가치세, 음료, 테이크아웃 식품 제외)이 25,000유로를 초과하는 경우에 적용됩니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 msgid "" @@ -23674,6 +23723,9 @@ msgid "" "Data Module <belgium/fdm>` (or **black box**) and a :ref:`VAT Signing Card " "<belgium/vat>`." msgstr "" +"해당 정부 인증 시스템에는 :ref:`인증된 POS 시스템 <belgium/certified-pos>`과 함께 :ref:`재정 데이터 " +"모듈 <belgium/fdm>` (또는 **블랙박스**) 및 :ref:`부가가치세 서명 카드 <belgium/vat>`라는 장치를 " +"사용해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:483 msgid "" @@ -23681,10 +23733,13 @@ msgid "" "Public Service Finance registration form " "<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_." msgstr "" +"*식품 서비스 산업 관리자*로 연방 공공 서비스 재정 등록 양식 " +"<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_에서 등록하는 것을 " +"잊지 마세요." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:489 msgid "Certified POS system" -msgstr "" +msgstr "인증된 POS 시스템" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:491 msgid "" @@ -23692,11 +23747,13 @@ msgid "" "on **Odoo Online** and **Odoo.sh**. Please refer to the following table to " "ensure that your POS system is certified." msgstr "" +"Odoo POS 시스템은 **Odoo 온라인** 및 **Odoo.sh**에서 호스팅되는 데이터베이스의 주요 버전에 대해 인증을 " +"받았습니다. 다음 표를 참조하여 POS 시스템이 인증되었는지 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:499 #: ../../content/applications/finance/payment_providers/stripe.rst:17 msgid "Odoo Online" -msgstr "" +msgstr "Odoo 온라인" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:500 msgid "Odoo.sh" @@ -23726,7 +23783,7 @@ msgstr "인증됨" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:513 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:517 msgid "Not certified" -msgstr "" +msgstr "미인증" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:506 msgid "Odoo 15.2" @@ -23751,44 +23808,46 @@ msgid "" "adhere to rigorous government regulations, which means it operates " "differently from a non-certified POS." msgstr "" +"`인증된 POS 시스템 <https://www.systemedecaisseenregistreuse.be/systemes-" +"certifies>`_은 반드시 엄격한 정부 규정을 준수해야 한다는 점에서, 비인증 POS와 다르게 작동합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 msgid "On a certified POS, you cannot:" -msgstr "" +msgstr "다음은 인증된 POS에서는 불가능합니다:" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:528 msgid "" "Set up and use the **global discounts** feature (the `pos_discount` module " "is blacklisted and cannot be activated)." -msgstr "" +msgstr "**글로벌 할인** 기능을 설정하여 사용합니다 (`pos_discount` 모듈은 블랙리스트에 등록되어 활성화할 수 없음)." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:530 msgid "" "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is" " blacklisted and cannot be activated)." -msgstr "" +msgstr "**적립 프로그램** 기능 설정 및 사용 (블랙리스트에 `pos_loyalty` 모듈이 있어서 활성화할 수 없음)." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 msgid "" "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be " "activated)." -msgstr "" +msgstr "영수증 재발행 (블랙리스트에 `pos_reprint` 모듈이 있으므로 활성화할 수 없습니다)" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:533 msgid "Modify prices in order lines." -msgstr "" +msgstr "주문 내역의 가격을 수정합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 msgid "Modify or delete order lines in POS orders." -msgstr "" +msgstr "POS 주문서에서 주문 내역을 수정하거나 삭제합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:535 msgid "Sell products without a valid VAT number." -msgstr "" +msgstr "유효한 VAT 번호가 없는 품목을 판매합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 msgid "Use a POS that is not connected to an IoT box." -msgstr "" +msgstr "IoT 박스에 연결되지 않은 POS를 사용합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:538 msgid "" @@ -23796,6 +23855,9 @@ msgid "" "feature must be activated and set to a :guilabel:`Rounding Precision` of " "`0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." msgstr "" +":doc:`현금 반올림 <../../sales/point_of_sale/pricing/cash_rounding>` 기능이 활성화되어 " +"있어야 하며 :guilabel:`반올림 정밀도`는 `0,05`로, :guilabel:`반올림 방법`은 :guilabel:`반올림`으로 " +"설정되어 있어야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:541 msgid "" @@ -23805,6 +23867,9 @@ msgid "" "by clicking the arrow next to the default sales tax field. There, click " ":guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." msgstr "" +"세금은 가격에 포함하여 설정해야 합니다. 설정하려면 :menuselection:`POS --> 환경 설정 --> 설정`으로 이동한 다음" +" :guilabel:`회계` 섹션에서 기본 판매세 필드 옆에 있는 화살표를 클릭하여 :guilabel:`기본 판매세` 양식을 엽니다. " +"거기에서 :guilabel:`고급 옵션`을 클릭하여 :guilabel:`가격에 포함`을 활성화합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:545 msgid "" @@ -23813,16 +23878,21 @@ msgid "" "clocked in, they cannot make POS orders. Likewise, they must click " ":guilabel:`Work Out` to clock out at the end of the session." msgstr "" +"POS 세션을 시작하려면, 사용자는 반드시 :guilabel:`근무 시작`을 클릭하여 출근 처리해야 합니다. 이렇게 해야 POS 주문을 " +"등록할 수 있습니다. 사용자가 로그인하지 않으면 POS 주문이 되지 않습니다. 마찬가지로 세션이 종료되면 :guilabel:`근무 " +"종료`를 클릭해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:550 msgid "" "If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you " "cannot use it again without it." msgstr "" +":abbr:`FDM (Fiscal Data Module)`과 함께 작동하도록 POS를 설정할 경우, POS 없이는 다시 사용할 수 " +"없습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:556 msgid "Fiscal Data Module (FDM)" -msgstr "" +msgstr "회계 데이터 모듈 (FDM)" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:558 msgid "" @@ -23832,6 +23902,9 @@ msgid "" "each POS order and added to its receipt. This allows the government to " "verify that all revenue is declared." msgstr "" +"FDM 또는 **블랙박스**는 POS 애플리케이션과 함께 작동하여 POS 주문 정보를 저장하는 정부 인증 장치입니다. 구체적으로는, " +"**해시** (:dfn:`고유 코드`)가 POS 주문별로 생성되어 영수증에 추가됩니다. 이를 통해 정부에서 모든 수익이 신고되었는지 " +"확인할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:564 msgid "" @@ -23840,46 +23913,51 @@ msgid "" "certifies#FDM%20certifiés>`_ is supported by Odoo. `Contact the manufacturer" " (GCV BMC) <https://www.boîtenoire.be/contact>`_ to order one." msgstr "" +"FDM 인증서 번호가 BMC01 <https://www.systemedecaisseenregistreuse.be/fr/systemes-" +"certifies#FDM%20certifiés>`_인 **Boîtenoire.be**의 FDM만 Odoo에서 지원됩니다. 주문하려면 " +"제조업체 (GCV BMC) <https://www.boîtenoire.be/contact>`_에 문의합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:572 msgid "" "Before setting up your database to work with an FDM, ensure you have the " "following hardware:" -msgstr "" +msgstr "FDM과 작동이 되도록 데이터베이스를 설정하기 전에 다음 하드웨어가 있는지 확인합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:574 msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" -msgstr "" +msgstr "**Boîtenoire.be** (인증서 번호 BMC01) FDM;" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 msgid "an RS-232 serial null modem cable per FDM;" -msgstr "" +msgstr "FDM당 RS-232 직렬 nul 모뎀 케이블 1개;" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:576 msgid "an RS-232 serial-to-USB adapter per FDM;" -msgstr "" +msgstr "FDM당 RS-232 직렬-USB 어댑터 1개;" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:577 msgid "an :ref:`IoT Box <belgium/iotbox>` (one IoT box per FDM); and" -msgstr "" +msgstr ":ref:`IoT 박스 <belgium/iotbox>` (FDM당 하나의 IoT 박스); 및" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:578 msgid "a receipt printer." -msgstr "" +msgstr "수신 프린터." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:583 msgid "Black box module" -msgstr "" +msgstr "블랙박스 모듈" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:585 msgid "" "As a pre-requisite, :ref:`activate <general/install>` the `Belgian " "Registered Cash Register` module (technical name: `pos_blackbox_be`)." msgstr "" +"전제 조건으로, '벨기에 등록 금전 등록기' 모듈 (기술명: `pos_blackbox_be`)을 :ref:`활성화 " +"<general/install>`해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 msgid "black box modules for belgian fiscal certification" -msgstr "" +msgstr "벨기에 재정 인증을 위한 블랙박스 모듈" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:591 msgid "" @@ -23891,10 +23969,14 @@ msgid "" " go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and " "fill in the :guilabel:`INSZ or BIS number` field." msgstr "" +"모듈을 활성화했으면, 회사 정보에 부가가치세 번호를 추가합니다. 설정하려면 :menuselection:`설정 --> 회사 --> 정보 " +"업데이트`로 이동하여 :guilabel:`VAT` 필드를 입력합니다. 그런 다음 POS 시스템으로 업무를 하는 모든 직원의 주민등록번호를" +" 입력합니다. 입력하려면 :guilabel:`직원` 앱으로 이동하여 직원 양식을 엽니다. 거기에서 :menuselection:`HR 설정" +" 탭 --> 근태/POS`로 이동하여 :guilabel:`주민등록번호 또는 BIS 번호` 필드를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 msgid "ISNZ or BIS number field on employee form" -msgstr "" +msgstr "직원 양식의 ISNZ 또는 BIS 번호 필드" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:601 msgid "" @@ -23902,6 +23984,8 @@ msgid "" "Profile --> Preference tab`, and enter your INSZ or BIS number in the " "designated field." msgstr "" +"정보를 입력하려면 아바타를 클릭하여 :menuselection:`: '내 프로필 --> 환경 설정 탭'으로 이동한 후 지정된 필드에 " +"INSZ 또는 BIS 번호를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:605 msgid "" @@ -23909,6 +23993,8 @@ msgid "" "production database. Utilizing it in a testing environment may result in " "incorrect data being stored within the FDM." msgstr "" +"반드시 프로덕션 데이터베이스에서 직접 :abbr:`FDM (재정 데이터 모듈)`을 설정해야 합니다. 테스트 환경에서 사용하면 FDM에 " +"잘못된 데이터가 저장될 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:611 msgid "IoT Box" @@ -23921,18 +24007,20 @@ msgid "" "contact form <https://www.odoo.com/help>`_ and provide the following " "information:" msgstr "" +":abbr:`FDM (재정 데이터 모듈)`을 사용하려면 IoT 박스가 등록되어 있어야 합니다. IoT 박스를 등록하려면 `지원 문의 양식" +" <https://www.odoo.com/help>`_을 통해 당사에 연락하여 다음 정보를 제출해야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:617 msgid "your VAT number;" -msgstr "" +msgstr "부가가치세 번호" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:618 msgid "your company's name, address, and legal structure; and" -msgstr "" +msgstr "회사명, 주소 및 법적 조직 구성 및" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:619 msgid "the Mac address of your IoT Box." -msgstr "" +msgstr "IoT 박스의 Mac 주소" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:621 msgid "" @@ -23941,10 +24029,13 @@ msgid "" " the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the " ":guilabel:`IOT Device` section, which should display the FDM." msgstr "" +"IoT 박스 인증이 완료되면 :doc:`connect <../../productivity/iot/config/connect>`를 " +"데이터베이스에 추가합니다. IoT 박스에서 FDM 인식이 되는지 확인하려면 IoT 홈페이지의 :guilabel:`IOT 장치` 섹션에서 " +"아래로 이동을 했을 때 FDM이 표시되어야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 msgid "Hardware status page on a registered IoT Box" -msgstr "" +msgstr "등록된 IoT Box의 하드웨어 상태 페이지" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:628 msgid "" @@ -23953,16 +24044,19 @@ msgid "" ":guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. " "Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." msgstr "" +"그런 다음 POS에 IoT를 추가합니다. 추가하려면 :menuselection:`POS --> 환경 설정 --> POS`로 이동하여 " +"POS를 선택하고 :guilabel:`연결된 장치` 섹션까지 아래로 스크롤로 이동한 다음 :guilabel:`IoT Box`를 " +"활성화합니다. 마지막으로 :guilabel:`재정 데이터 모듈` 필드에 FMD를 추가합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:633 msgid "" "To be able to use an FDM, you must at least connect one :guilabel:`Receipt " "Printer`." -msgstr "" +msgstr "FDM을 사용하려면 연결되어 있는 :guilabel:`영수증 프린터`가 최소한 하나는 있어야 합니다." #: ../../content/applications/finance/fiscal_localizations/belgium.rst:638 msgid "VAT signing card" -msgstr "" +msgstr "부가가치세 서명 카드" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:640 msgid "" @@ -23972,6 +24066,10 @@ msgid "" "upon `registration " "<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_." msgstr "" +"POS 세션을 시작하여 처음으로 거래를 할 때, :abbr:`VSC (VAT 서명 카드)`와 함께 제공된 PIN을 입력하라는 메시지가 " +"표시됩니다. 이 카드는 '등록 " +"<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_ 시 " +":abbr:`FPS (Service Public Federal Finances)`에서 전달됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:3 msgid "Brazil" @@ -23983,6 +24081,8 @@ msgid "" "and electronic invoices (NF-e) for goods can be sent using AvaTax (Avalara) " "through |API| calls. Moreover, taxes for services can be configured." msgstr "" +"브라질 현지화를 통해 판매세를 자동으로 계산할 수 있으며, 상품에 대한 전자 청구서 (NF-e)는 |API| 호출을 통해 AvaTax " +"(Avalara)를 사용하여 전송할 수 있습니다. 또한 서비스에 대한 세금도 설정할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:16 msgid "" @@ -23992,18 +24092,21 @@ msgid "" "account in Avatax <brazil/avatax-account>` need to be configured in the " "general settings." msgstr "" +"품목 세금 계산 및 전자 청구서 발행 프로세스를 진행하려면 일반 설정에서 :ref:`contacts <brazil/contacts>`, " +":ref:`company <brazil/company>`, :ref:`품목 <brazil/products>` 및 :ref:`avatax " +"계정 만들기 <brazil/avatax-account>` 설정을 해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:21 msgid "" "For the services taxes, you can create and configure them from Odoo directly" " without computing them with AvaTax." -msgstr "" +msgstr "서비스 관련 세금의 경우 AvaTax에서 계산하지 않고 Odoo에서 직접 생성 및 설정할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:24 msgid "" "The localization also includes taxes and a chart of accounts template that " "can be modified if needed." -msgstr "" +msgstr "현지화에는 필요한 경우 수정할 수 있는 세금 및 계정과목표 서식도 들어 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:30 msgid "" @@ -24012,23 +24115,26 @@ msgid "" "of the Brazilian localization, following the :abbr:`IFRS (International " "Financial Reporting Standards)` rules." msgstr "" +":guilabel:`🇧🇷 브라질` :ref:`재정 현지화 패키지 <fiscal_localizations/packages>`를 설치하면 " +":abbr:`IFRS (International Financial Reporting Standards)` 규칙에 따라 브라질 현지화의 " +"기본 회계 기능 전체를 사용할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:39 msgid "" "To configure your company information, go to the :menuselection:`Contacts` " "app and search the name given to your company." -msgstr "" +msgstr "회사 정보를 설정하려면 :menuselection:`연락처` 앱으로 이동하여 회사 이름을 검색합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 msgid "" "Select the :guilabel:`Company` option at the top of the page. Then, " "configure the following fields:" -msgstr "" +msgstr "페이지 상단에서 :guilabel:`회사` 옵션을 선택합니다. 선택한 후, 다음 내용을 입력합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:45 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:245 msgid ":guilabel:`Name`." -msgstr "" +msgstr ":guilabel:`이름`" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:46 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:246 @@ -24036,89 +24142,92 @@ msgid "" ":guilabel:`Address` (add :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip" " Code`, :guilabel:`Country`)." msgstr "" +":guilabel:`주소` (추가 :guilabel:`도시`, :guilabel:`주`, :guilabel:`우편번호`, " +":guilabel:`국가`)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:49 msgid "" "In the :guilabel:`Street` field, enter the street name, number, and any " "additional address information." -msgstr "" +msgstr ":guilabel:`도로명` 필드에는 도로명, 번호 및 추가 주소 정보를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:51 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:250 msgid "In the :guilabel:`Street 2` field, enter the neighborhood." -msgstr "" +msgstr ":guilabel:`도로명 2` 필드에 동 주소를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:53 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:252 msgid ":guilabel:`Identification Number` (:guilabel:`CNPJ`, :guilabel:`CPF`)." -msgstr "" +msgstr ":guilabel:`식별 번호` (:guilabel:`CNPJ`, :guilabel:`CPF`)를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:54 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:253 msgid ":guilabel:`Tax ID` (associated with the identification type)." -msgstr "" +msgstr ":guilabel:`세금 ID` (식별 유형과 연결)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:55 msgid ":guilabel:`IE` (State registration)." -msgstr "" +msgstr ":guilabel:`IE` (주 등록)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:56 msgid ":guilabel:`IM` (Municipal registration)." -msgstr "" +msgstr ":guilabel:`IM` (시 등록)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:57 msgid "" ":guilabel:`SUFRAMA code` (Superintendence of the Manaus Free Trade Zone - " "add if applicable)." -msgstr "" +msgstr ":guilabel:`SUFRAMA 코드` (Manaus 자유 무역 지대 감독관 - 해당되는 경우 추가)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:58 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:257 msgid ":guilabel:`Phone`." -msgstr "" +msgstr ":guilabel:`전화번호`." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:59 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:258 msgid ":guilabel:`Email`." -msgstr "" +msgstr ":guilabel:`이메일`." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Company configuration." -msgstr "" +msgstr "회사 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 msgid "" "Configure the :guilabel:`Fiscal Information` within the :guilabel:`Sales and" " Purchase` tab:" -msgstr "" +msgstr ":guilabel:`판매 및 매입` 탭에서 :guilabel:`재정 정보`를 설정합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:66 msgid "" "Add the :guilabel:`Fiscal Position` for :ref:`Avatax Brazil <brazil/fiscal-" "positions>`." msgstr "" +":ref:`Avatax Brazil <brazil/fiscal-positions>`에 대해 :guilabel:`재정 위치`를 추가합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:67 msgid ":guilabel:`Tax Regime` (Federal Tax Regime)." -msgstr "" +msgstr ":guilabel:`세금 제도 ` (연방 세금 제도)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:68 msgid "" ":guilabel:`ICMS Taxpayer Type` (indicates ICMS regime, Exempt status, or " "Non-Taxpayer)." -msgstr "" +msgstr ":guilabel:`ICMS 납세자 유형` (ICMS 체제, 면제 상태 또는 비과세자 표시)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:69 msgid ":guilabel:`Main Activity Sector`." -msgstr "" +msgstr ":guilabel:`주요 활동 분야`." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Company fiscal configuration." -msgstr "" +msgstr "회사 재정 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:74 msgid "Finally, upload a company logo and save the contact" -msgstr "" +msgstr "마지막으로 회사 로고를 업로드하고 연락처를 저장합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:77 msgid "" @@ -24126,10 +24235,12 @@ msgid "" ":menuselection:`Accounting --> Configuration --> Settings --> Taxes --> " "Avatax Brazil`." msgstr "" +"단순화된 정책을 사용하고 있는 경우 :menuselection:`회계 --> 환경 설정 --> 설정 --> 세금 -->Avatax " +"Brazil `에서 ICMS 요율 설정을 해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:83 msgid "Configure AvaTax integration" -msgstr "" +msgstr "AvaTax 통합 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 msgid "" @@ -24139,6 +24250,8 @@ msgid "" "information to retrieve the correct tax to be used and process the e-invoice" " afterward with the government." msgstr "" +"Avalara Avatax는 세금 계산 및 전자 세금계산서 제공업체로 Odoo에서 연동하여 회사, 연락처 (고객), 품목, 거래 정보를 " +"고려하여 자동으로 세금을 계산하여 정확한 세금을 조회하고 정부에 전자 세금계산서를 사후 처리할 수 있는 서비스입니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:90 msgid "" @@ -24147,10 +24260,13 @@ msgid "" "electronic invoices. Whenever you compute taxes, an |API| call is made using" " credits from your |IAP| credits balance." msgstr "" +"연동하려면 세금을 계산하고 전자 청구서를 전송하기 위해 :doc:`인앱 구매(IAP) " +"<../../general/in_app_purchase>` 기능이 있어야 합니다. 세금을 계산할 때마다 |IAP| 크레딧 잔액에 있는 " +"크레딧을 사용하여 |API| 호출이 이루어집니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 msgid "Odoo is a certified partner of Avalara Brazil." -msgstr "" +msgstr "Odoo는 Avalara 브라질의 인증된 파트너입니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:100 msgid "" @@ -24160,6 +24276,9 @@ msgid "" " to be used for the AvaTax portal in the :guilabel:`Avatax Portal Email`, " "and then click on :guilabel:`Create account`." msgstr "" +"Odoo에서 AvaTax를 활성화하려면 계정을 만들어야 합니다. 생성하려면 :menuselection:`회계 --> 환경 설정 --> " +"설정 --> 세금`으로 이동한 다음 :guilabel:`AvaTax 브라질` 섹션의 :guilabel:`Avatax 포털 이메일`에 " +"AvaTax 포털에 사용할 관리 이메일 주소를 추가한 다음 :guilabel:`계정 만들기`를 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:106 msgid "" @@ -24167,27 +24286,31 @@ msgid "" " or sandbox database, use an alternate email address. It is **not** possible" " to re-use the same email address on the production database." msgstr "" +"테스트 또는 샌드박스 데이터베이스에서 :guilabel:`Avatax 포털 이메일` 연동을 **테스트**하는 경우, 이메일 주소를 다르게" +" 사용합니다. 프로덕션 데이터베이스에서 동일한 이메일 주소를 다시 사용할 수 **없습니다**." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:110 msgid "" "After you create the account from Odoo, you need to go to the Avalara Portal" " to set up your password:" -msgstr "" +msgstr "Odoo에서 계정을 생성한 후 Avalara 포털로 이동하여 비밀번호를 설정해야 합니다:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:113 msgid "" "Access the `Avalara portal <https://portal.avalarabrasil.com.br/Login>`_." -msgstr "" +msgstr "Avalara 포털 <https://portal.avalarabrasil.com.br/Login>`_에 접속합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:114 msgid "Click on :guilabel:`Meu primeiro acesso`." -msgstr "" +msgstr ":guilabel:`Meu primeiro acesso`을 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:115 msgid "" "Add the email address you used in Odoo to create the Avalara/Avatax account," " and then click :guilabel:`Solicitar Senha`." msgstr "" +"Avalara/Avatax 계정을 생성할 때 Odoo에서 사용한 이메일 주소를 추가한 다음 :guilabel:`Solicitar " +"Senha`를 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:117 msgid "" @@ -24195,6 +24318,8 @@ msgid "" "Click on this link and copy-paste the token to allocate your desired " "password." msgstr "" +"토큰과 비밀번호를 생성할 수 있는 링크를 이메일로 받게 됩니다. 이 링크를 클릭한 후 복사한 토큰을 붙여넣어 원하는 비밀번호를 " +"설정합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:121 msgid "" @@ -24203,26 +24328,32 @@ msgid "" "However, in order to use the electronic invoice service, you **must** access" " the AvaTax portal and upload your certificate there." msgstr "" +"Odoo에서 AvaTax를 세금 계산 **전용**으로 Odoo 데이터베이스에서 비밀번호나 Avalara 포털 액세스 없이 사용할 수 " +"있습니다. 다만 전자 청구서 서비스를 사용하려면 반드시 AvaTax 포털에 액세스하여 인증서를 업로드해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Avatax account configuration." -msgstr "" +msgstr "Avatax 계정 환경 설정." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:129 msgid "" "You can transfer |API| credentials. Use this only when you have already " "created an account in another Odoo instance and wish to reuse it." msgstr "" +"|API| 자격 증명을 전송할 수 있습니다. 다른 Odoo 인스턴스에서 이미 계정을 생성하여 다시 사용하려는 경우에만 이 기능을 " +"사용합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:133 msgid "A1 certificate upload" -msgstr "" +msgstr "A1 인증서 업로드" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:135 msgid "" "In order to issue electronic invoices, a certificate needs to be uploaded to" " the `AvaTax portal <https://portal.avalarabrasil.com.br/Login>`_." msgstr "" +"전자 청구서를 발행하려면 `AvaTax 포털 <https://portal.avalarabrasil.com.br/Login>`_에 인증서를" +" 업로드해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:138 msgid "" @@ -24231,6 +24362,8 @@ msgid "" "- with the CNPJ number, and the identification number (CNPJ) in Odoo matches" " with the CNPJ in AvaTax." msgstr "" +"인증서는 AvaTax 포털의 외부 식별자 번호가 특수 문자 없이 CNPJ 번호와 일치하고 Odoo에서의 식별 번호 (CNPJ)가 " +"AvaTax의 CNPJ와 일치할 경우 Odoo와 동기화됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:148 msgid "" @@ -24239,17 +24372,19 @@ msgid "" " module. The accounts are mapped automatically in their corresponding taxes," " and the default account payable and account receivable fields." msgstr "" +":doc:`계정과목표 <../accounting/get_started/chart_of_accounts>`는 현지화 모듈에 포함되어 있는 " +"데이터 집합의 일부로 기본 설치됩니다. 계정은 해당하는 세금과 기본 미지급금 및 미수금 필드에 자동으로 매핑됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:153 msgid "" "The chart of accounts for Brazil is based on the SPED CoA, which gives a " "baseline of the accounts needed in Brazil." -msgstr "" +msgstr "브라질의 계정과목표는 브라질에서 필요한 계정의 기준선을 제공하는 SPED CoA를 기반으로 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:250 msgid "You can add or delete accounts according to the company's needs." -msgstr "" +msgstr "회사의 필요에 따라 계정을 추가하거나 삭제할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:161 msgid "" @@ -24259,6 +24394,9 @@ msgid "" "needed, then a new sales journal will need to be created and a new series " "number assigned to it for each series needed." msgstr "" +"브라질에서는 *일련* 번호가 전자 청구서의 연속된 번호 범위에 연결됩니다. 일련 번호는 판매 전표의 Odoo에서 :guilabel:`일련" +" 번호` 필드에서 설정할 수 있습니다. 일련 번호 항목이 두 개 이상 필요한 경우에는 새로 판매 전표를 생성하고 필요한 각 연련 항목에 " +"대해 새로 일련 번호를 배정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:166 msgid "" @@ -24268,10 +24406,13 @@ msgid "" " will only be displayed if the :guilabel:`Use Documents` field is selected " "on the journal." msgstr "" +":guilabel:`문서 사용` 필드를 선택해야 합니다. 전자 청구서 및 일반 청구서를 발행할 때 :guilabel:`유형` 필드에서 " +"청구서를 작성할 때 사용할 문서 유형을 선택합니다. 전표에서 :guilabel:`유형` 필드가 선택되어 있는 경우에만 " +":guilabel:`문서 사용` 필드가 표시됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Journal configuration with the Use Documents? field checked." -msgstr "" +msgstr "문서 사용? 필드에 표시가 되어 있는 전표 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:175 msgid "" @@ -24280,6 +24421,8 @@ msgid "" "notes, and debit notes are shared per series number, which means per " "journal." msgstr "" +"브라질에서는 청구서, 대변전표, 차변전표 사이의 순서가 일련 번호, 즉 전표별로 공유되므로 전표를 만들 때 :guilabel:`대변전표 " +"전용 일련번호` 필드 선택이 취소되어 있는지 확인합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:182 msgid "" @@ -24287,6 +24430,8 @@ msgid "" "Taxes are already configured, and some of them are used by Avalara when " "computing taxes on the sales order or invoice." msgstr "" +"브라질 현지화를 설치할 때 세금은 자동으로 생성됩니다. 세금은 환경 설정이 이미 완료되어 있으며, 일부는 판매주문서 또는 청구서 관련 " +"세금을 계산할 때 Avalara에서 사용합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:185 msgid "" @@ -24294,12 +24439,14 @@ msgid "" "used for services need to be manually added and configured, as the rate may " "differ depending on the city where you are offering the service." msgstr "" +"세금을 편집하거나, 세금을 더 추가할 수 있습니다. 예를 들어, 서비스가 제공되는 도시에 따라 세율이 다를 수 있으므로 서비스에 사용되는" +" 일부 세금은 직접 추가하고 설정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:190 msgid "" "Taxes attached to services are not computed by AvaTax. Only goods taxes are " "computed." -msgstr "" +msgstr "서비스에 부과되는 세금은 AvaTax에서 계산되지 않습니다. 재화에 대한 세금만 계산됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:192 msgid "" @@ -24309,10 +24456,13 @@ msgid "" "Included`, and, on the :guilabel:`Advanced Options` tab, check the " ":guilabel:`Included in Price` option." msgstr "" +"서비스에 부과된 세금이 최종 가격에 포함되도록 설정하는 경우 (품목 가격에 세금을 더하거나 빼지 않는 경우) :guilabel:`세금 " +"계산`을 :guilabel:`세금 포함가 비율`로 설정하고 :guilabel:`고급 옵션` 탭에서 :guilabel:`가격에 포함` " +"옵션에 표시합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Tax configuration." -msgstr "" +msgstr "세금 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:201 msgid "" @@ -24323,10 +24473,13 @@ msgid "" ":guilabel:`Distribution for invoices` and :guilabel:`Distribution for " "refunds` sections." msgstr "" +"Avatax 세금 계산에 사용되므로, 세금을 삭제하지 마세요. 삭제할 경우, Odoo에서 |판매주문서| 또는 청구서에서 사용할 때 세금을" +" 다시 생성하고 AvaTax로 세금을 계산하지만 세금을 등록하는 데 사용되는 계정은 세금의 :guilabel:`정의` 탭의 " +":guilabel:`청구서용 배포` 및 :guilabel:`환불용 배포` 섹션에서 다시 설정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:207 msgid ":doc:`Taxes functional documentation <../accounting/taxes>`" -msgstr "" +msgstr ":doc:`세금 기능 문서 <../accounting/taxes>`" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:212 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 @@ -24342,40 +24495,40 @@ msgstr "품목" msgid "" "To use the AvaTax integration on sale orders and invoices, first specify the" " following information on the product:" -msgstr "" +msgstr "판매주문서 및 청구서에 AvaTax 통합을 사용하려면 먼저 품목에 다음 정보를 지정합니다:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:217 msgid "" ":guilabel:`CEST Code` (Code for products subject to ICMS tax substitution)." -msgstr "" +msgstr ":guilabel:`CEST 코드` (ICMS 세금 대체 대상 품목 코드)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 msgid "" ":guilabel:`Mercosul NCM Code` (Mercosur Common Nomenclature Product Code)." -msgstr "" +msgstr ":guilabel:`Mercosul NCM 코드` (Mercosur 공통 품목 코드 명명법)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:219 msgid "" ":guilabel:`Source of Origin` (Indicates the origin of the product, which can" " be foreign or domestic, among other possible options depending on the " "specific use case)." -msgstr "" +msgstr ":guilabel:`원산지` (특정 사용 사례별로 가능한 옵션 중에서 외국 또는 국내인 품목의 원산지를 나타냅니다)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 msgid "" ":guilabel:`SPED Fiscal Product Type` (Fiscal product type according to SPED " "list table)." -msgstr "" +msgstr ":guilabel:`SPED 재정 품목 유형` (SPED 목록 표에 따른 재정 품목 유형)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:222 msgid "" ":guilabel:`Purpose of Use` (Specify the intended purpose of use for this " "product)." -msgstr "" +msgstr ":guilabel:`사용 목적` (해당 품목의 사용 목적을 명시합니다)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Product configuration." -msgstr "" +msgstr "품목 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:228 msgid "" @@ -24386,6 +24539,9 @@ msgid "" ":guilabel:`Product Type` `Service`, :guilabel:`Transportation Cost Type` " "`Insurance`, `Freight`, or `Other Costs`)." msgstr "" +"Odoo는 판매와 관련된 운송비에 사용할 세 가지 품목을 자동으로 생성합니다. 품목명은 '운임', '보험', '기타 비용'입니다. 이미 " +"환경 설정이 되어 있으므로 더 생성해야 하는 경우에는 동일한 환경 설정을 복사하여 사용합니다 (환경 설정 필요: :guilabel:`품목" +" 유형` `서비스`, :guilabel:`운송비 유형` `보험`, `운임` 또는 '기타 비용')." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:265 @@ -24399,39 +24555,41 @@ msgstr "연락처" msgid "" "Before using the integration, specify the following information on the " "contact:" -msgstr "" +msgstr "연동 기능을 사용하기 전에 연락처에 다음 정보를 지정합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:241 msgid "General information about the contact:" -msgstr "" +msgstr "연락처에 대한 일반 정보입니다:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:243 msgid "" "Select the :guilabel:`Company` option for a contact with a tax ID (CNPJ), or" " check :guilabel:`Individual` for a contact with a CPF." msgstr "" +"세금 ID (CNPJ)가 연락처에 있는 경우, :guilabel:`회사` 옵션을 선택하고, CPF가 있는 연락처인 경우 " +":guilabel:`개인`을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:249 msgid "" "In the :guilabel:`Street` field, enter the street, number, and any extra " "address information." -msgstr "" +msgstr ":guilabel:`도로명` 필드에는 도로명, 번호 및 추가 주소 정보를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:254 msgid ":guilabel:`IE`: state tax identification number." -msgstr "" +msgstr ":guilabel:`IE`: 지역 세금 식별 번호" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:255 msgid ":guilabel:`IM`: municipal tax identification number." -msgstr "" +msgstr ":guilabel:`IM`: 지방세 식별 번호" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:256 msgid ":guilabel:`SUFRAMA code`: SUFRAMA registration number." -msgstr "" +msgstr ":guilabel:`SUFRAMA 코드`: SUFRAMA 등록 번호" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Contact configuration." -msgstr "" +msgstr "연락처 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:264 msgid "" @@ -24439,42 +24597,47 @@ msgid "" "code` fields are are hidden until the :guilabel:`Country` is set to " "`Brazil`." msgstr "" +":guilabel:`CPF`, :guilabel:`IE`, :guilabel:`IM` 및 :guilabel:`SUFRAMA 코드` 필드는" +" :guilabel:`국가`가 `브라질`로 설정될 때까지 숨겨져 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 msgid "" "Fiscal information about the contact under the :guilabel:`Sales \\& " "Purchase` tab:" -msgstr "" +msgstr ":guilabel:`판매 \\& 매입` 탭 하단에 있는 연락처에 대한 재정 정보:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:269 msgid "" ":guilabel:`Fiscal Position`: add the AvaTax fiscal position to automatically" " compute taxes on sale orders and invoices automatically" msgstr "" +":guilabel:`재정 위치`: AvaTax 재정상의 위치를 추가하여 판매주문서 및 청구서에 대한 세금을 자동으로 계산합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:271 msgid ":guilabel:`Tax Regime`: federal tax regime" -msgstr "" +msgstr ":guilabel:`세금 제도`: 연방 조세 제도" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:272 msgid "" ":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is " "within the ICMS regime, if it is exempt, or if it is a non-taxpayer" msgstr "" +":guilabel:`ICMS 납세자 유형`: 납세자 유형은 연락처가 ICMS 체제 내에 있는지, 면세 대상인지, 비납세자인지를 " +"결정합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:274 msgid "" ":guilabel:`Main Activity Sector`: list of main activity sectors of the " "contact" -msgstr "" +msgstr ":guilabel:`주요 활동 분야`: 연락처의 주요 활동 분야 목록입니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 msgid "Contact fiscal configuration." -msgstr "" +msgstr "연락처 재정 환경 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:282 msgid "Fiscal positions" -msgstr "" +msgstr "재정 위치" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:284 msgid "" @@ -24482,22 +24645,24 @@ msgid "" "both the :guilabel:`Detect Automatically` and the :guilabel:`Use AvaTax API`" " options need to be enabled in the :guilabel:`Fiscal Position`." msgstr "" +"세금을 계산하고 판매주문서 및 청구서에 대한 전자 청구서를 보내려면 :guilabel:`재정 위치`에서 :guilabel:`자동 감지` " +"및 :guilabel:`AvaTax API 사용` 옵션이 모두 활성화되어 있어야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:288 msgid "" "The :guilabel:`Fiscal Position` can be configured on the contact or selected" " when creating a sales order or an invoice." -msgstr "" +msgstr ":guilabel:`재정 위치`는 연락처에서 설정하거나 판매주문서나 청구서를 생성할 때 선택할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Fiscal position configuration" -msgstr "" +msgstr "재정 상태 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" -msgstr "" +msgstr "작업 흐름" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:297 msgid "" @@ -24505,108 +24670,113 @@ msgid "" "<https://en.wikipedia.org/wiki/API>`_ for tax computation, and how to send " "an electronic invoice for goods (NF-e) for government validation." msgstr "" +"이 섹션에서는 세금 계산을 위해 `API 호출 <https://en.wikipedia.org/wiki/API>`_을 트리거하는 작업과 " +"정부에서 승인을 받기 위해 물품에 대한 전자 청구서 (NF-e)를 보내는 방법에 대한 개요를 다룹니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:302 msgid "" "Please note that each |API| call incurs a cost. Be mindful of the actions " "that trigger these calls to manage costs effectively." -msgstr "" +msgstr "|API| 호출에는 비용이 발생합니다. 비용을 효과적으로 관리하려면 이러한 호출을 트리거하는 활동에 유의합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 msgid "Tax calculations on quotations and sales orders" -msgstr "" +msgstr "견적서 및 판매주문서에 대한 세금 계산" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:311 msgid "" "Trigger an |API| call to calculate taxes on a quotation or sales order " "automatically with AvaTax in any of the following ways:" msgstr "" +"다음의 방법 중에서 견적서 또는 판매 주문에 대한 세금을 자동으로 계산하도록 |API| 호출을 트리거하여 AvaTax로 계산합니다:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:314 msgid "**Quotation confirmation**" -msgstr "" +msgstr "**견적 확인**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:315 msgid "Confirm a quotation into a sales order." -msgstr "" +msgstr "견적서를 확인하여 판매주문서로 만듭니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:316 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:332 msgid "**Manual trigger**" -msgstr "" +msgstr "**수동 트리거**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:317 msgid "Click on :guilabel:`Compute Taxes Using Avatax`." -msgstr "" +msgstr ":guilabel:`Avatax를 사용하여 세금 계산`을 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:318 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:334 msgid "**Preview**" -msgstr "" +msgstr "**미리 보기**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:319 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:335 msgid "Click on the :guilabel:`Preview` button." -msgstr "" +msgstr ":guilabel:`미리 보기` 버튼을 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:320 msgid "**Email a quotation / sales order**" -msgstr "" +msgstr "**견적서/판매주문서를 이메일로 보내기**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:321 msgid "Send a quotation or sales order to a customer via email." -msgstr "" +msgstr "이메일을 통해 고객에게 견적서나 판매주문서를 보냅니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:324 msgid "**Online quotation access**" -msgstr "" +msgstr "**온라인 견적서 접근 권한**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:323 msgid "" "When a customer accesses the quotation online (via the portal view), the " "|API| call is triggered." -msgstr "" +msgstr "고객이 온라인으로 (포털 화면을 통하여) 견적서에 액세스하면 |API| 호출이 트리거됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:327 msgid "Tax calculations on invoices" -msgstr "" +msgstr "청구서에 대한 세금 계산" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:329 msgid "" "Trigger an |API| call to calculate taxes on a customer invoice automatically" " with AvaTax any of the following ways:" -msgstr "" +msgstr "다음의 방법 중에서 고객 청구서에 대한 세금을 자동으로 계산하기 위해 |API| 호출을 트리거합니다:" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:333 msgid "Click on :guilabel:`Compute Taxes Using AvaTax`." -msgstr "" +msgstr ":guilabel:`AvaTax를 사용하여 세금 계산`을 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 msgid "**Online invoice access**" -msgstr "" +msgstr "**온라인 청구서 액세스**" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 msgid "" "When a customer accesses the invoice online (via the portal view), the |API|" " call is triggered." -msgstr "" +msgstr "고객이 온라인으로 (포털 화면을 통하여) 청구서에 액세스하면 |API| 호출이 트리거됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:340 msgid "" "The :guilabel:`Fiscal Position` must be set to `Automatic Tax Mapping " "(Avalara Brazil)` for any of these actions to compute taxes automatically." msgstr "" +"세금을 자동으로 계산하려면 반드시 :guilabel:`재정 위치`가 `자동 세금 매핑 (Avalara 브라질)`로 설정되어 있어야 이와 " +"같이 작업을 수행할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:344 msgid "" ":doc:`Fiscal positions (tax and account mapping) " "<../accounting/taxes/fiscal_positions>`" -msgstr "" +msgstr ":doc:`재정 위치 (세금 및 계정 매핑) <../accounting/taxes/fiscal_positions>`" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:92 msgid "Electronic documents" -msgstr "" +msgstr "전자 문서" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:354 msgid "" @@ -24618,39 +24788,44 @@ msgid "" "click on :guilabel:`Send \\& Print` to process the invoice against the " "government." msgstr "" +"품목에 대한 전자 청구서 (NF-e)를 처리하려면 Avalara에서 청구서를 확인하고 세금을 계산해야 합니다. 해당 단계가 완료되면 왼쪽" +" 상단에 있는 :guilabel:`보내기 및 인쇄` 버튼을 클릭하면 팝업이 나타납니다. 그런 다음 :guilabel:`전차 청구서 " +"처리`와 기타 옵션으로 :guilabel:`다운로드` 또는 :guilabel:`이메일` 중 하나를 클릭합니다. 마지막으로 " +":guilabel:`보내기 및 인쇄`를 클릭하여 정부 청구서를 처리합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:360 msgid "" "Before sending the electronic invoice for goods (NF-e) some fields need to " "be filled out on the invoice:" -msgstr "" +msgstr "품목별 전자 청구서 (NF-e) 전송 전에 청구서서 다음 내용을 작성해야 합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:363 msgid ":guilabel:`Customer` with all the customer information" -msgstr "" +msgstr ":guilabel:`고객` 전체 고객 정보 포함" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:364 msgid "" ":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)" -msgstr "" +msgstr ":guilabel:`결제 방법: 브라질` (청구서 결제 방법)" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:365 msgid "" ":guilabel:`Fiscal Position` set as the :guilabel:`Automatic Tax Mapping " "(Avalara Brazil)`" -msgstr "" +msgstr ":guilabel:`재정 위치`를 :guilabel:`자동 세금 매핑(Avalara 브라질)`로 설정" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:368 msgid "" ":guilabel:`Document Type` set as :guilabel:`(55) Electronic Invoice (NF-e)`." " This is the only" -msgstr "" +msgstr ":guilabel:`문서 유형`이 :guilabel:` (55) 전자 청구서 (NF-e)`로 설정되었습니다. 이것이 유일하게" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:367 msgid "" "electronic document supported at the moment. Non-electronic invoices can be " "registered, and other document types can be activated if needed" msgstr "" +"현재 지원되는 전자 문서입니다. 전자 형식이 아닌 청구서를 등록할 수 있으며, 필요한 경우 다른 문서 유형을 활성화할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:370 msgid "" @@ -24658,25 +24833,27 @@ msgid "" "transaction. These fields are not required, so no errors will appear from " "the government if these optional fields are not populated for most cases:" msgstr "" +"거래의 성격에 따라 몇 가지 다른 선택 필드가 있습니다. 이러한 필드는 필수가 아니므로 대부분의 경우 선택 필드를 입력하지 않더라도 정부" +" 문서에서 오류로 표시되지 않습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:374 msgid "" ":guilabel:`Freight Model` determines how the goods are planned to be " "transported - domestic" -msgstr "" +msgstr ":guilabel:'운송 모델'은 화물을 어떻게 운송할 계획인지 방법을 지정합니다 (국내)." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 msgid "" ":guilabel:`Transporter Brazil` determines who is doing the transportation" -msgstr "" +msgstr ":guilabel:`브라질 운송업체`는 어느 업체에서 운송을 담당하는지 지정합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Invoice information needed to process an electronic invoice." -msgstr "" +msgstr "전자청구서를 처리하기 위해 필요한 청구서 정보입니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Process electronic invoice pop-up in Odoo." -msgstr "" +msgstr "Odoo에서 전자 청구서 팝업이 처리됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:384 msgid "" @@ -24685,23 +24862,25 @@ msgid "" "first invoice, the field :guilabel:`Document Number` is displayed, allocated" " as the first number to be used sequentially for subsequent invoices." msgstr "" +"전자 청구서 발행에 사용하는 청구서에서 있는 모든 필드는 필요한 경우 판매주문서에서도 사용할 수 있습니다. 처음으로 청구서를 생성할 때 " +":guilabel:`문서 번호` 필드가 표시되며, 이는 후속 청구서에 순차적으로 사용될 첫 번째 번호로 배정됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:390 #: ../../content/applications/finance/fiscal_localizations/chile.rst:595 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" -msgstr "" +msgstr "대변전표" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:392 msgid "" "If a sales return needs to be registered, then a credit note can be created " "in Odoo to be sent to the government for validation." -msgstr "" +msgstr "판매 반품 등록을 하는 경우 Odoo에서 대변전표를 생성한 후 정부로 전송하여 승인을 받을 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:396 msgid ":ref:`Issue a credit note <accounting/issue-credit-note>`" -msgstr "" +msgstr ":ref:`대변전표 발행 <accounting/issue-credit-note>`" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:399 #: ../../content/applications/finance/fiscal_localizations/peru.rst:585 @@ -24714,6 +24893,7 @@ msgid "" "corrected that were not accurately provided in the original invoice, a debit" " note can be issued." msgstr "" +"추가 정보가 있어야 하거나 원래 청구서에 정확하게 표시되지 않은 값을 수정해야 하는 경우 차변전표를 발행해야 할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:405 msgid "" @@ -24723,26 +24903,28 @@ msgid "" " is only to declare the amount that you want to add to the original invoice " "for the same or fewer products." msgstr "" +"원래의 청구서에 있던 품목만 차변전표에 포함될 수 있습니다. 품목의 단가나 수량은 변경할 수 있지만 차변전표에 품목을 추가하는 것은 " +"**불가**합니다. 이 문서의 목적은 원래의 청구서에 있던 품목 수량 이하로 추가 금액을 신고하는 것입니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:411 msgid ":ref:`Issue a debit note <accounting/issue-debit-note>`" -msgstr "" +msgstr ":ref:`차변전표 발행 <accounting/issue-debit-note>`" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:414 msgid "Invoice cancellation" -msgstr "" +msgstr "청구서 취소" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:416 msgid "" "It is possible to cancel an electronic invoice that was validated by the " "government." -msgstr "" +msgstr "정부로부터 승인을 받은 전자 청구서는 취소할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:419 msgid "" "Check whether the electronic invoice is still within the cancellation " "deadline, which may vary according to the legislation of each state." -msgstr "" +msgstr "전자 청구서의 취소 기한이 지나지 않았는지 확인하며, 취소 기한은 각 주의 법률에 따라 다를 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:422 msgid "" @@ -24751,20 +24933,22 @@ msgid "" "send this cancellation reason to the customer via email, activate the " ":guilabel:`E-mail` checkbox." msgstr "" +"Odoo에서 :guilabel:`취소 요청`을 클릭하여 팝업이 나타나면 취소 :guilabel:`사유`를 추가하면 됩니다. 이 취소 " +"사유를 고객에게 이메일을 전송하려면 :guilabel:`이메일` 확인란에 표시합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Invoice cancellation reason in Odoo." -msgstr "" +msgstr "Odoo의 청구서 취소 사유" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:430 msgid "Correction letter" -msgstr "" +msgstr "정정요청서" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 msgid "" "A correction letter can be created and linked to an electronic invoice that " "was validated by the government." -msgstr "" +msgstr "정정요청서를 작성하여 정부에서 승인한 전자 청구서에 연결할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:435 msgid "" @@ -24773,14 +24957,16 @@ msgid "" "this correction reason to a customer via email, activate the " ":guilabel:`E-mail` checkbox." msgstr "" +"이 작업은 Odoo에서 :guilabel:`정정요청서`를 클릭하여 팝업이 나타나면 정정 :guilabel:`사유`를 추가하면 됩니다. " +"정정 사유를 고객에게 이메일로 전송하려면 :guilabel:`이메일` 확인란에 표시합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Correction letter reason in Odoo." -msgstr "" +msgstr "Odoo의 정정요청서 사유" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:443 msgid "Invalidate invoice number range" -msgstr "" +msgstr "청구서 번호 넘버링 취소" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:445 msgid "" @@ -24792,20 +24978,24 @@ msgid "" "Number` and :guilabel:`End Number` of the range that should be canceled, and" " enter an invalidation :guilabel:`Reason`." msgstr "" +"판매 전표를 채번하는 넘버링을 현재 사용하지 않고 있으며 **동시에** 향후에도 사용하지 않을 계획인 경우 정부에서 취소할 수 있습니다." +" 이렇게 하려면 전표로 이동하여 :menuselection:`⚙️ (톱니바퀴) 아이콘 --> 넘버링 취소 (BR)`를 클릭합니다. " +":guilabel:`넘버링 취소 (BR)` 마법사에서 취소할 범위의 :guilabel:`시작 번호` 및 :guilabel:`끝 번호`를 " +"추가하고 취소 :guilabel:`사유`를 입력합니다. ." #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Number range invalidation selection in Odoo." -msgstr "" +msgstr "Odoo에서 넘버링 취소 선택" #: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 msgid "Number range invalidation wizard in Odoo." -msgstr "" +msgstr "Odoo의 넘버링 취소 마법사" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:459 msgid "" "The log of the canceled numbers along with the XML file are recorded in the " "chatter of the journal." -msgstr "" +msgstr "취소된 번호의 로그는 XML 파일과 함께 전표에 있는 메시지창에 기록됩니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:465 msgid "" @@ -24814,33 +25004,36 @@ msgid "" "with the same Brazilian specific information that is recorded on the " ":ref:`customer invoices <brazil/electronic-documents>`." msgstr "" +"공급업체 청구서 측면에서는, Odoo에 청구서를 인코딩할 수 있으며 공급업체로부터 청구서를 받을 때 :ref:`고객 청구서 " +"<brazil/electronic-documents>`에 기록된 것과 동일한 브라질의 특정 정보를 전체 비즈니스 정보와 함께 추가할 수 " +"있습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:469 msgid "These Brazilian specific fields are:" -msgstr "" +msgstr "브라질과 관련된 특정 필드는 다음과 같습니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:471 msgid "" ":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)." -msgstr "" +msgstr ":guilabel:`결제 방법: 브라질` (청구서 결제 방법)" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:472 msgid ":guilabel:`Document Type` used by your vendor." -msgstr "" +msgstr ":guilabel:`문서 유형`은 공급업체에서 사용하는 유형을 의미합니다." #: ../../content/applications/finance/fiscal_localizations/brazil.rst:473 msgid ":guilabel:`Document Number` (the invoice number from your supplier)." -msgstr "" +msgstr ":guilabel:`문서 번호` (공급업체의 청구서 번호)" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:474 msgid "" ":guilabel:`Freight Model` (how goods are planned to be transported - " "domestic)." -msgstr "" +msgstr ":guilabel:`운송 모델` (품목 운송 계획 방식 - 국내)" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:475 msgid ":guilabel:`Transporter Brazil` (who is doing the transportation)." -msgstr "" +msgstr ":guilabel:`브라질 운송업체` (운송 담당 업체)" #: ../../content/applications/finance/fiscal_localizations/chile.rst:3 msgid "Chile" @@ -24852,32 +25045,38 @@ msgid "" "localization, and search the playlist for tutorials to discover practical " "workflows while using Odoo in Chile." msgstr "" +"아래에 있는 두 개의 웨비나 동영상을 통해 현지화에 대한 일반적인 내용을 확인해 보시고, 시청 목록에서 튜토리얼을 검색하여 칠레에서 " +"실무에 Odoo를 사용할 때의 작업 흐름에 대해 알아보세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:9 msgid "`Webinar: intro and demo <https://youtu.be/BHnByZiyYcM>`_." -msgstr "" +msgstr "`웨비나: 소개 및 데모 <https://youtu.be/BHnByZiyYcM>`_." #: ../../content/applications/finance/fiscal_localizations/chile.rst:10 msgid "`Webinar: delivery guide <https://youtu.be/X7i4PftnEdU>`_." -msgstr "" +msgstr "`웨비나: 전달 가이드 <https://youtu.be/X7i4PftnEdU>`_." #: ../../content/applications/finance/fiscal_localizations/chile.rst:11 msgid "" "`Playlist of tutorials " "<https://youtube.com/playlist?list=PL1-aSABtP6AB6UY7VUFnVgeYOaz33fb4P>`_." msgstr "" +"`튜토리얼 재생 목록 " +"<https://youtube.com/playlist?list=PL1-aSABtP6AB6UY7VUFnVgeYOaz33fb4P>`_." #: ../../content/applications/finance/fiscal_localizations/chile.rst:15 msgid "" "`Chilean localization app tour " "<https://www.youtube.com/watch?v=3qYkgbmBYHw>`_" -msgstr "" +msgstr "`칠레 현지화 앱 둘러보기 <https://www.youtube.com/watch?v=3qYkgbmBYHw>`_" #: ../../content/applications/finance/fiscal_localizations/chile.rst:16 msgid "" "`Chilean localization smart tutorial <https://www.odoo.com/slides/smart-" "tutorial-localizacion-de-chile-131>`_" msgstr "" +"`칠레 현지화 스마트 튜토리얼 <https://www.odoo.com/slides/smart-tutorial-localizacion-" +"de-chile-131>`_" #: ../../content/applications/finance/fiscal_localizations/chile.rst:22 msgid "Modules" @@ -24887,11 +25086,11 @@ msgstr "모듈" msgid "" ":ref:`Install <general/install>` the following modules to utilize all the " "features of the Chilean localization." -msgstr "" +msgstr "다음 모듈을 :ref:`설치 <general/install>`하면 칠레 현지화의 기능을 모두 사용할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:33 msgid ":guilabel:`Chile - Accounting`" -msgstr "" +msgstr ":guilabel:`칠레 - 회계`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:34 msgid "`l10n_cl`" @@ -24903,10 +25102,12 @@ msgid "" "Chile under the :abbr:`SII (Servicio de Impuestos Internos)` regulations and" " guidelines." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 규정 및 지침에 따라 칠레에서 회사를 운영하기 위해 " +"필요한 최소한의 회계 기능을 추가합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:37 msgid ":guilabel:`Chile - Accounting Reports`" -msgstr "" +msgstr ":guilabel:`칠레 - 회계 보고서`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:38 msgid "`l10n_cl_reports`" @@ -24915,11 +25116,11 @@ msgstr "`l10n_cl_reports`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:39 msgid "" "Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." -msgstr "" +msgstr "*Propuesta F29* 및 *Balance Tributario (8개 컬럼)* 보고서를 추가합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:40 msgid ":guilabel:`Chile - E-invoicing`" -msgstr "" +msgstr ":guilabel:`칠레 - 전자 청구서`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:41 msgid "`l10n_cl_edi`" @@ -24931,10 +25132,12 @@ msgid "" "electronic invoices online based on the :abbr:`SII (Servicio de Impuestos " "Internos)` regulations." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 규정에 따라 온라인으로 전자 청구서를 생성하고 수신하기 " +"위한 기술 및 기능 요구 사항이 모두 포함되어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:44 msgid ":guilabel:`Chile - Electronic Receipt`" -msgstr "" +msgstr ":guilabel:`칠레 - 전자 영수증`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:45 msgid "`l10n_cl_boletas`" @@ -24946,10 +25149,12 @@ msgid "" "electronic invoices digitally based on the :abbr:`SII (Servicio de Impuestos" " Internos)` regulations." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 규정에 따라 디지털 방식으로 전자 청구서를 생성하고 " +"수신하기 위한 기술 및 기능 요구 사항이 모두 포함되어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:48 msgid ":guilabel:`Electronic Exports of Goods for Chile`" -msgstr "" +msgstr ":guilabel:`칠레에 대한 전자 제품 수출`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:49 msgid "`l10n_cl_edi_exports`" @@ -24961,10 +25166,12 @@ msgid "" "invoices for exporting goods based on the :abbr:`SII (Servicio de Impuestos " "Internos)` and customs regulations." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 및 관세 규정에 따라 품목 수출용 전자 청구서를 생성하기" +" 위한 기술 및 기능적 요구 사항이 들어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:52 msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" -msgstr "" +msgstr ":guilabel:`칠레 - 전자 청구서 발행 가이드`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:53 msgid "`l10n_cl_edi_stock`" @@ -24976,18 +25183,20 @@ msgid "" "guides via web service based on the :abbr:`SII (Servicio de Impuestos " "Internos)` regulations." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 규정에 따라 웹 서비스를 통해 발행 가이드를 생성하기 " +"위한 모든 기술 및 기능 요구 사항이 들어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:58 msgid "" "Odoo automatically installs the appropriate package for the company " "according to the country selected at the creation of the database." -msgstr "" +msgstr "Odoo는 데이터베이스를 생성할 때 선택한 국가에 따라 회사에 적합한 패키지를 자동으로 설치합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:60 msgid "" "The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* " "application." -msgstr "" +msgstr "*칠레 - 전자 청구서 발행 가이드* 모듈은 *재고 관리* 애플리케이션에 따라 달라집니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:63 msgid "" @@ -24996,109 +25205,119 @@ msgid "" "<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" " certification process." msgstr "" +"회사에서 이미 `SII Sistema de Facturación de Mercado " +"<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" +" 인증 프로세스를 완료한 경우에만 모든 기능을 사용할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:70 msgid "" "Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure " "the following company information is up-to-date and correctly filled in:" msgstr "" +":menuselection:`설정 --> 회사: 정보 업데이트`로 이동하여 다음의 회사 정보가 최신 상태로 정확하게 입력되었는지 " +"확인합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:73 msgid ":guilabel:`Company Name`" -msgstr "" +msgstr ":guilabel:`회사명`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:74 msgid ":guilabel:`Address`:" -msgstr "" +msgstr ":guilabel:`주소`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:78 msgid ":guilabel:`State`" -msgstr "" +msgstr ":guilabel:`지역`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:82 msgid "" ":guilabel:`Tax ID`: enter the identification number for the selected " ":ref:`Taxpayer Type <chile/fiscal-info>`." msgstr "" +":guilabel:`세금 ID`: 선택한 :ref:`납세자 유형 <chile/fiscal-info>`에 대한 식별 번호를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:84 msgid ":guilabel:`Activity Names`: select up to four activity codes." -msgstr "" +msgstr ":guilabel:`활동 제목`: 최대 4개의 활동 코드를 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:85 msgid "" ":guilabel:`Company Activity Description`: enter a short description of the " "company's activity." -msgstr "" +msgstr ":guilabel:`회사 활동 설명`: 회사 활동에 대한 설명을 간단히 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:90 msgid "" "Next, navigate to :menuselection:`Accounting --> Configuration --> Settings " "--> Chilean Localization` and follow the instructions to configure the:" msgstr "" +"다음으로 :menuselection:`계정 --> 환경 설정 --> 설정 --> 칠레 현지화`로 이동하여 지침에 따라 다음과 같이 " +"설정합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:93 msgid ":ref:`Fiscal information <chile/fiscal-info>`" -msgstr "" +msgstr ":ref:`재정 정보 <chile/fiscal-info>`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:94 msgid ":ref:`Electronic invoice data <chile/electronic-invoice>`" -msgstr "" +msgstr ":ref:`전자 청구서 데이터 <chile/electronic-invoice>`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:95 msgid ":ref:`DTE incoming email server <chile/dte-email>`" -msgstr "" +msgstr ":ref:`DTE 수신 이메일 서버 <chile/dte-email>`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:96 msgid ":ref:`Signature certificates <chile/certificate>`" -msgstr "" +msgstr ":ref:`서명 인증서 <chile/certificate>`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:101 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 msgid "Fiscal information" -msgstr "" +msgstr "재정 정보" #: ../../content/applications/finance/fiscal_localizations/chile.rst:103 msgid "Configure the following :guilabel:`Tax payer information`:" -msgstr "" +msgstr "다음 :guilabel:`납세자 정보`를 설정합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:105 msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" -msgstr "" +msgstr ":guilabel:`납세자 유형`에 적용될 납세자 유형을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:107 msgid "" ":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to " "customers" -msgstr "" +msgstr ":guilabel:`부가가치세 적용 (1번 카테고리)`: 고객에게 세금을 부과하는 청구서용" #: ../../content/applications/finance/fiscal_localizations/chile.rst:108 msgid "" ":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees" " receipt (Boleta)" -msgstr "" +msgstr ":guilabel:`수수료 영수증 발급자 (2번 카테고리)`: 수수료 영수증을 발행하는 공급업체용 (Boleta)" #: ../../content/applications/finance/fiscal_localizations/chile.rst:109 msgid ":guilabel:`End consumer`: only issues receipts" -msgstr "" +msgstr ":guilabel:`최종 소비자`: 영수증만 발행" #: ../../content/applications/finance/fiscal_localizations/chile.rst:110 msgid ":guilabel:`Foreigner`" -msgstr "" +msgstr ":guilabel:`외국인`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:112 msgid "" ":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de " "Impuestos Internos)` regional office" msgstr "" +":guilabel:`SII 사무소`: 회사의 :abbr:`SII (Servicio de Impuestos Internos)` 지역 " +"사무소를 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:118 msgid "Electronic invoice data" -msgstr "" +msgstr "전자 청구서 데이터" #: ../../content/applications/finance/fiscal_localizations/chile.rst:120 msgid "Select your :guilabel:`SII Web Services` environment:" -msgstr "" +msgstr ":guilabel:`SII 웹 서비스` 환경을 선택합니다:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:122 msgid "" @@ -25107,10 +25326,13 @@ msgid "" "Internos)`. In this mode, the direct connection flows can be tested, with " "the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`." msgstr "" +"guilabel:`SII - 테스트`: 테스트용 데이터베이스인 경우 :abbr:`SII (Servicio de Impuestos " +"Internos)`의 테스트 :abbr:`CAF (Folio Authorization Code)`를 사용합니다. 이 모드에서는 직접 연결" +" 흐름을 테스트할 수 있으며, :abbr:`SII (Servicio de Impuestos Internos)`로 파일이 전송됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:126 msgid ":guilabel:`SII - Production`: for production databases." -msgstr "" +msgstr ":guilabel:`SII - Production`: 프로덕션 데이터베이스용" #: ../../content/applications/finance/fiscal_localizations/chile.rst:127 msgid "" @@ -25120,26 +25342,30 @@ msgid "" "will not appear in this mode. Every internal validation can be tested in " "demo mode. Avoid selecting this option in a production database." msgstr "" +":guilabel:`SII - 데모 모드`: 데모 모드에서는 파일이 자동으로 생성 및 승인되지만 :abbr:`SII (Servicio " +"de Impuestos Internos)`로 전송되지는 **않습니다**. 이러한 이유로 이 모드에서는 거부 오류 또는 **이의 사항과 " +"함께 승인* 항목이 표시되지 않습니다. 내부 검증은 모두 데모 모드에서 테스트할 수 있습니다. 프로덕션 데이터베이스에서는 이 옵션을 " +"선택하지 마세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:132 msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" -msgstr "" +msgstr "그런 다음 :guilabel:`법적 전자 청구서 데이터`를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:134 msgid ":guilabel:`SII Resolution N°`" -msgstr "" +msgstr ":guilabel:`SII 결의 번호`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:135 msgid ":guilabel:`SII Resolution Date`" -msgstr "" +msgstr ":guilabel:`SII 결의 날짜`" #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Required information for electronic invoice." -msgstr "" +msgstr "전자 청구서에 필요한 정보입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:144 msgid "DTE incoming email server" -msgstr "" +msgstr "DTE 수신 이메일 서버" #: ../../content/applications/finance/fiscal_localizations/chile.rst:146 msgid "" @@ -25150,6 +25376,10 @@ msgid "" "want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos " "Tributarios Electrónicos)` incoming email server." msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`전차 청구서 이메일 " +"수신함`을 지정하여 고객의 청구 및 승인 이메일을 받을 수 있습니다. :abbr:`DTE (Documentos Tributarios " +"Electrónicos)` 수신 이메일 서버로 *전차 청구서 이메일 수신함*을 사용하려면 :menuselection:`:`회계 --> " +"환경 설정 --> 설정 --> 칠레 현지화`에서 이 옵션을 활성화해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:153 msgid "" @@ -25157,28 +25387,32 @@ msgid "" "email server. More information on how to do this can be found in this " "documentation: :doc:`../../general/email_communication/email_servers`" msgstr "" +"SII 문서를 수신하려면 자체 이메일 서버를 설정해야 합니다. 이 작업을 수행하는 방법에 대한 자세한 내용은 다음 문서에서 확인하세요: " +":doc:`../../general/email_communication/email_servers`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:157 msgid "" "Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click " ":guilabel:`New` to add a server and fill in the following fields:" msgstr "" +"시작하려면 :guilabel:`DTE 수신 이메일 환경 설정`을 클릭한 후 :guilabel:`새로 만들기`를 클릭하여 서버를 추가하고 " +"다음 필드를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:160 msgid ":guilabel:`Name`: give the server a name." -msgstr "" +msgstr ":guilabel:`이름`: 서버에 이름을 지정합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:161 msgid ":guilabel:`Server Type`: select the server type used." -msgstr "" +msgstr ":guilabel:`서버 유형`: 사용되는 서버 유형을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:163 msgid ":guilabel:`IMAP Server`" -msgstr "" +msgstr ":guilabel:`IMAP 서버`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:164 msgid ":guilabel:`POP Server`" -msgstr "" +msgstr ":guilabel:`POP 서버`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:165 msgid "" @@ -25186,6 +25420,8 @@ msgid "" " records. The script can be found in the :guilabel:`Configuration` section " "with this option selected." msgstr "" +":guilabel:`로컬 서버`: 로컬 스크립트를 사용하여 이메일을 가져오고 새로 레코드를 만듭니다. 스크립트는 이 옵션이 선택된 " +":guilabel:`환경 설정` 섹션에서 확인할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:167 msgid "" @@ -25193,6 +25429,8 @@ msgid "" "to be configured in the general settings. A direct link to the configuration" " can be found in the :guilabel:`Login Information` section." msgstr "" +":guilabel:`Gmail OAuth 인증`: 일반 설정에서 Gmail API 자격 증명을 설정해야 합니다. 직접 설정할 수 있는 " +"링크는 :guilabel:`로그인 정보` 섹션에서 확인할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:171 msgid "" @@ -25204,36 +25442,41 @@ msgid "" "Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL " "CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*." msgstr "" +":guilabel:`DTE 서버`: 이 옵션을 활성화합니다. 이 옵션을 선택하면 해당 이메일 계정을 공급업체로부터 전자 청구서 수신에 " +"사용하고, 발행된 전자 청구서과 관련하여 :abbr:`SII (Servicio de Impuestos Internos)`로부터 연락을 " +"받기 위해 사용합니다. 이 경우 이 이메일은 :abbr:`SII (Servicio de Impuestos Internos)` 사이트의 " +"*ACTUALIZACION DE DATOS DEL CONTRIBUYENTE*, *Mail Contacto SII* 및 *Mail " +"Contacto Empresas* 섹션에 신고한 이메일 두 개와 모두 일치해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:178 msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" -msgstr "" +msgstr ":guilabel:`서버 및 로그인` 탭 (IMAP 및 POP 서버용):" #: ../../content/applications/finance/fiscal_localizations/chile.rst:180 msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." -msgstr "" +msgstr ":guilabel:`서버명`: 서버의 호스트 이름이나 IP를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:181 msgid ":guilabel:`Port`: enter the server port." -msgstr "" +msgstr ":guilabel:`포트`: 서버 포트를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:182 msgid "" ":guilabel:`SSL/TLS`: enable this option if connections are encrypted using " "the SSL/TLS protocol." -msgstr "" +msgstr ":guilabel:`SSL/TLS`: 연결이 SSL/TLS 프로토콜로여 암호화되어 있는 경우 이 옵션을 활성화합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:183 msgid ":guilabel:`Username`: enter the server login username." -msgstr "" +msgstr ":guilabel:`사용자 이름`: 서버 로그인용 사용자 이름을 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:184 msgid ":guilabel:`Password`: enter the server login password." -msgstr "" +msgstr ":guilabel:`비밀번호`: 서버 로그인 비밀번호를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Incoming email server configuration for Chilean DTE." -msgstr "" +msgstr "칠레 DTE에 대한 수신용 이메일 서버의 환경 설정" #: ../../content/applications/finance/fiscal_localizations/chile.rst:191 msgid "" @@ -25241,6 +25484,8 @@ msgid "" " to vendor bills that are not required to be processed in Odoo from your " "inbox." msgstr "" +"실시간으로 전환하기 전에, Odoo에서 처리할 필요가 없는 공급업체 청구서 및 모든 관련 이메일은 받은 편지함에서 보관하거나 제거하는 " +"것이 좋습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:197 #: ../../content/applications/finance/fiscal_localizations/peru.rst:219 @@ -25254,16 +25499,19 @@ msgid "" "Signature Certificates` under the :guilabel:`Signature Certificates` " "section. Then, click :guilabel:`New` to configure the certificate:" msgstr "" +"전자 청구서 서명을 생성하려면 '.pfx' 형식의 디지털 인증서가 필요합니다. 추가하려면 :guilabel:`인증서 서명` 섹션 아래에 " +"있는 :guilabel:`인증서 서명 환경 설정`을 클릭합니다. 그런 다음 :guilabel:`새로 만들기`를 클릭하여 인증서에 대한 " +"환경 설정을 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:203 msgid "" ":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select " "the `.pfx` file." -msgstr "" +msgstr ":guilabel:`인증서 키`: :guilabel:`파일 업로드`를 클릭한 후 `.pfx` 파일을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:204 msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." -msgstr "" +msgstr ":guilabel:`인증서 비밀번호`: 파일 비밀번호를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:205 msgid "" @@ -25271,6 +25519,8 @@ msgid "" "field might not be automatically populated. In that case, enter the " "certificate's legal representative :abbr:`RUT (Rol Único Tributario)`." msgstr "" +":guilabel:`제목 일련 번호`: 인증서 형식에 따라 필드가 자동으로 입력되지 않을 수 있습니다. 이 경우 인증서의 법적 대리 " +"항목인 :abbr:`RUT (Rol Único Tributario)`를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:208 msgid "" @@ -25278,16 +25528,18 @@ msgid "" "certificate for a specific user. Leave the field empty to share it with all " "billing users." msgstr "" +":guilabel:`인증서 소유자`: 특정 사용자에 대하여 인증서를 제한해야 하는 경우 하나를 선택합니다. 모든 청구서 사용자와 " +"공유하려면 필드를 비워 둡니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Digital certificate configuration." -msgstr "" +msgstr "디지털 인증서에 대한 환경 설정" #: ../../content/applications/finance/fiscal_localizations/chile.rst:216 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 #: ../../content/applications/finance/fiscal_localizations/peru.rst:230 msgid "Multicurrency" -msgstr "" +msgstr "다중 통화" #: ../../content/applications/finance/fiscal_localizations/chile.rst:218 msgid "" @@ -25297,11 +25549,14 @@ msgid "" "an :guilabel:`Interval` for when the rate is automatically updated, or to " "select another :guilabel:`Service`." msgstr "" +"공식 환율은 `칠레 mindicador.cl <https://mindicador.cl>`_에서 제공되고 있습니다. " +":menuselection:`회계 --> 환경 설정 --> 설정 --> 통화: 자동 환율`로 이동하여 환율의 자동 업데이트 " +":guilabel:`주기`를 설정하거나 다른 :guilabel:`서비스`를 선택합니다.." #: ../../content/applications/finance/fiscal_localizations/chile.rst:226 #: ../../content/applications/finance/fiscal_localizations/france.rst:306 msgid "Partner information" -msgstr "" +msgstr "파트너 정보" #: ../../content/applications/finance/fiscal_localizations/chile.rst:228 msgid "" @@ -25310,58 +25565,63 @@ msgid "" ":menuselection:`Contacts` app to do so and fill in the following fields on a" " new or existing contact form." msgstr "" +"파트너 연락처에 대한 환경 설정은 :abbr:`SII (Servicio de Impuestos Internos)` 전자 청구서 전송에 " +"있어서도 필수 사항입니다. 설정하려면 :menuselection:`연락처` 앱을 열고 새 연락처 양식이나 기존 양식에 다음 내용을 " +"입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:233 #: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 msgid ":guilabel:`Email`" -msgstr "" +msgstr ":guilabel:`이메일`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:234 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 msgid ":guilabel:`Identification Number`" -msgstr "" +msgstr ":guilabel:`식별 번호`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:235 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 msgid ":guilabel:`Taxpayer Type`" -msgstr "" +msgstr ":guilabel:`납세자 유형`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:236 msgid ":guilabel:`Activity Description`" -msgstr "" +msgstr ":guilabel:`활동 설명`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:238 msgid "In the :guilabel:`Electronic Invoicing` tab:" -msgstr "" +msgstr ":guilabel:`전자 청구서` 탭에서 진행합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:240 msgid "" ":guilabel:`DTE Email`: enter the sender's email address for the partner." -msgstr "" +msgstr ":guilabel:`DTE 이메일`: 파트너의 발신 이메일 주소를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:241 msgid "" ":guilabel:`Delivery Guide Price`: select which price the delivery guide " "displays, if any." -msgstr "" +msgstr ":guilabel:`배송 안내 가격`: 배송 안내에 표시할 가격이 있는 경우 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:244 msgid "" "The :guilabel:`DTE Email` is the email used for sending electronic documents" " and must be set in the contact that will be part of an electronic document." msgstr "" +":guilabel:`DTE 이메일`은 전자 문서 전송에 사용하는 이메일이며 전자 문서에 있는 연락처에 설정되어 있어야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Chilean electronic invoice data for partners." -msgstr "" +msgstr "파트너용 칠레 전자 청구서 데이터입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:254 msgid "" "Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos " "Internos)`-defined document types." msgstr "" +"회계 문서는 :abbr:`SII (Servicio de Impuestos Internos)`에서 지정한 문서 유형 카테고리로 분류됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:257 msgid "" @@ -25369,59 +25629,61 @@ msgid "" "localization module, and can be managed by navigating to " ":menuselection:`Accounting --> Configuration --> Document Types`." msgstr "" +"문서 유형은 현지화 모듈을 설치하면 자동으로 생성되며 :menuselection:`회계 --> 환경 설정 --> 문서 유형`으로 이동하여" +" 관리할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Chilean fiscal document types list." -msgstr "" +msgstr "칠레 회계 문서 유형 목록" #: ../../content/applications/finance/fiscal_localizations/chile.rst:265 msgid "" "Several document types are inactive by default but can be activated by " "toggling the :guilabel:`Active` option." -msgstr "" +msgstr "몇 가지 문서 유형은 기본값이 비활성화이지만 :guilabel:`활성화`로 토글을 전환하여 활성화할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:271 msgid "The document type on each transaction is determined by:" -msgstr "" +msgstr "각 거래별 문서 유형은 다음에 따라 결정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:273 msgid "" "The journal related to the invoice, identifying if the journal uses " "documents." -msgstr "" +msgstr "청구서과 관련된 전표로, 전표에 문서가 있는지 여부를 식별합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:274 msgid "" "The condition applied based on the type of issuer and recipient (e.g., the " "buyer or vendor's fiscal regime)." -msgstr "" +msgstr "발행인 및 수령인 유형 (예: 구매자 또는 공급업체의 회계 제도)에 따라 적용되는 조건입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:280 msgid "" "*Sales journals* in Odoo usually represent a business unit or location." -msgstr "" +msgstr "Odoo의 *판매 전표*에는 일반적으로 사업부 또는 위치가 표시되어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:283 msgid "Ventas Santiago." -msgstr "" +msgstr "Ventas Santiago." #: ../../content/applications/finance/fiscal_localizations/chile.rst:284 msgid "Ventas Valparaiso." -msgstr "" +msgstr "Ventas Valparaiso." #: ../../content/applications/finance/fiscal_localizations/chile.rst:286 msgid "" "For retail stores it is common to have one journal per :abbr:`POS (Point of " "Sale)`." -msgstr "" +msgstr "소매점의 경우 :abbr:`POS (Point of Sale)`별로 전표를 사용하는 것이 일반적입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:289 msgid "Cashier 1." -msgstr "" +msgstr "캐셔 1." #: ../../content/applications/finance/fiscal_localizations/chile.rst:290 msgid "Cashier 2." -msgstr "" +msgstr "캐셔 2." #: ../../content/applications/finance/fiscal_localizations/chile.rst:292 msgid "" @@ -25430,18 +25692,20 @@ msgid "" "accounting transactions that are not related to vendor bills. This " "configuration can easily be set by using the following model." msgstr "" +"*구매* 거래는 단일 전표로 관리할 수 있지만 때로는 회사에서 공급업체 청구서와 관련되지 않은 일부 회계 거래를 처리하기 위해 전표를 두" +" 개 이상사용하는 경우도 있습니다. 다음 모델을 사용하여 쉽게 설정할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:297 msgid "Tax payments to the government." -msgstr "" +msgstr "정부에 세금 납부" #: ../../content/applications/finance/fiscal_localizations/chile.rst:298 msgid "Employees payments." -msgstr "" +msgstr "직원 급여" #: ../../content/applications/finance/fiscal_localizations/chile.rst:301 msgid "Create a sales journal" -msgstr "" +msgstr "판매 전표 만들기" #: ../../content/applications/finance/fiscal_localizations/chile.rst:303 msgid "" @@ -25449,12 +25713,14 @@ msgid "" "Configuration --> Journals`. Then, click the :guilabel:`New` button, and " "fill in the following required information:" msgstr "" +"판매 전표를 생성하려면 :menuselection:`회계 --> 환경 설정 --> 전표`로 이동합니다. 그런 다음 " +":guilabel:`새로 만들기` 버튼을 클릭한 후 다음의 필수 정보를 입력합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:306 msgid "" ":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for " "customer invoice journals." -msgstr "" +msgstr ":guilabel:`유형`: 고객 청구서 전표에 있는 드롭다운 메뉴에서 :guilabel:`판매`를 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:307 msgid "" @@ -25464,6 +25730,9 @@ msgid "" "system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` " "portal *Facturación MiPyme*, you can use the option :guilabel:`Manual`." msgstr "" +":guilabel:`POS 유형`: 판매 전표를 전자 문서에 사용하는 경우 반드시 :guilabel:`온라인` 항목을 선택해야 합니다. " +"이렇게 하지 않고 이전 시스템에서 가져온 청구서에 전표를 사용하거나 :abbr:`SII (Servicio de Impuestos " +"Internos)` *Facturación MiPyme* 포털을 사용하는 경우 :guilabel:`수기` 옵션을 사용할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:311 msgid "" @@ -25472,6 +25741,8 @@ msgid "" "can be related to the different sets of document types available in Chile. " "By default, all the sales journals created will use documents." msgstr "" +":guilabel:`문서 사용`: 전표에서 문서 유형을 사용할 경우 이 필드를 선택합니다. 이 필드는 칠레에서 사용할 수 있는 다양한 " +"문서 유형 세트와 관련된 매입 및 판매 전표에만 적용됩니다. 기본적으로, 모든 판매 전표 생성에는 문서가 사용됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:315 msgid "" @@ -25480,10 +25751,13 @@ msgid "" ":guilabel:`Accounting Information` section. Configuring these fields is " "required for one of the debit notes :ref:`use cases <chile/use-cases>`." msgstr "" +"다음으로, :guilabel:`전표 항목` 탭의 :guilabel:`회계 정보` 섹션에서 :guilabel:`기본 수익 계정` 및 " +":guilabel:`대변전표 전용 순번`을 정의합니다. 차변전표 :ref:`사용 사례 <chile/use-cases>` 중에서 해당 " +"필드를 설정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:322 msgid "CAF" -msgstr "" +msgstr "CAF" #: ../../content/applications/finance/fiscal_localizations/chile.rst:324 msgid "" @@ -25493,6 +25767,9 @@ msgid "" "issuer with the folios/sequences authorized for the electronic invoice " "documents." msgstr "" +"전자적으로 발행되는 각 문서 유형에는 *Folio 인증 코드* (CAF: Folio Authorization Code)가 있어야 합니다." +" :abbr:`CAF (Folio Authorization Code)`는 :abbr:`SII (Servicio de Impuestos " +"Internos)`에서 전자 청구서 문서에 대해 승인된 Folio/연번과 함께 발급자에게 제공하는 파일입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:329 msgid "" @@ -25502,6 +25779,10 @@ msgid "" "you only need one active :abbr:`CAF (Folio Authorization Code)` per document" " type, and it will be applied to all journals." msgstr "" +"회사에서 여러 항목의 Folio를 요청하여 다른 Folio 범위에 연결된 :abbr:`CAF (Folio Authorization " +"Codes)`를 여러 개 확인할 수 있습니다. 이러한 :abbr:`CAF (Folio Authorization Code)`는 전체 " +"전표에서 공유되므로 문서 유형당 활성화되어 있는 :abbr:`CAF (Folio Authorization Code)` 하나만 있으면 모든" +" 전표에 적용됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:334 msgid "" @@ -25509,6 +25790,8 @@ msgid "" "<https://palena.sii.cl/dte/mn_timbraje.html>`_ to check the details on how " "to acquire the :abbr:`CAF (Folio Authorization Code)` files." msgstr "" +":abbr:`CAF (Folio Authorization Code)` 파일을 받을 수 있는 방법에 대한 자세한 내용은 `SII 문서 " +"<https://palena.sii.cl/dte/mn_timbraje.html>`_를 참조합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:338 msgid "" @@ -25517,10 +25800,13 @@ msgid "" "(certification mode). Make sure you have the correct :abbr:`CAF (Folio " "Authorization Code)` set depending on your environment." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)`에 필요한 :abbr:`CAF (Folio " +"Authorization Code)`는 프로덕션 및 테스트 (인증 모드)에 따라 다릅니다. 환경에 따라 :abbr:`CAF (Folio " +"Authorization Code)`가 올바르게 설정되어 있는지 확인합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:343 msgid "Upload CAF files" -msgstr "" +msgstr "CAF 파일 업로드" #: ../../content/applications/finance/fiscal_localizations/chile.rst:345 msgid "" @@ -25532,6 +25818,11 @@ msgid "" "upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the " ":guilabel:`Upload your file` button and then click :guilabel:`Save`." msgstr "" +":abbr:`CAF (Folio Authorization Code)` 파일을 :abbr:`SII (Servicio de Impuestos" +" Internos)` 포털에서 받은 후에는 :menuselection:`회계 --> 환경 설정: 찰레 SII --> CAF`로 이동하여 " +"데이터베이스에 업로드해야 합니다. 그 다음 :guilabel:`새로 만들기`를 클릭하여 환경 설정을 시작합니다. :abbr:`CAF " +"(Folio Authorization Code)` 양식에서 :guilabel:`파일 업로드` 버튼을 클릭하여 :abbr:`CAF " +"(Folio Authorization Code)` 파일을 업로드한 다음 :guilabel:`저장`을 클릭합니다. ." #: ../../content/applications/finance/fiscal_localizations/chile.rst:352 msgid "" @@ -25539,6 +25830,8 @@ msgid "" "when a transaction is used for this document type, the invoice number takes " "the first folio in the sequence." msgstr "" +"업로드되면 상태가 :guilabel:`사용 중`으로 변경됩니다. 이 때 이 문서 유형에 대한 작업이 있을 경우, 청구서 번호는 첫 번째 " +"순서에 있는 Folio를 사용하게 됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:356 msgid "" @@ -25547,22 +25840,24 @@ msgid "" "previous system, the next valid folio has to be set when the first " "transaction is created." msgstr "" +"문서 유형은 :abbr:`CAF (Folio Authorization Code)` 파일을 업로드하기 전에 활성화되어 있어야 합니다. 이전" +" 시스템에서 일부 Folio가 사용된 적이 있는 경우 첫 번째 작업이 생성될 때 다음 유효한 Folio를 설정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:363 msgid "" "The chart of accounts is installed by default as part of the data set " "included in the localization module. The accounts are mapped automatically " "in:" -msgstr "" +msgstr "계정과목표는 현지화 모듈에 포함된 데이터 세트의 일부로 기본 설치됩니다. 계정은 다음에 자동으로 매핑됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:367 msgid "Default Account Payable" -msgstr "" +msgstr "기본 미지급금 계정" #: ../../content/applications/finance/fiscal_localizations/chile.rst:368 #: ../../content/applications/finance/fiscal_localizations/peru.rst:75 msgid "Default Account Receivable" -msgstr "" +msgstr "기본 미수금 계정" #: ../../content/applications/finance/fiscal_localizations/chile.rst:369 msgid "Transfer Accounts" @@ -25578,18 +25873,20 @@ msgid "" "their related financial account and configuration. These taxes can be " "managed from :menuselection:`Accounting --> Configuration --> Taxes`." msgstr "" +"현지화 모듈의 일부로, 관련된 금융 계정 및 설정과 함께 세금이 자동으로 생성됩니다. 이와 같은 세금은 :menuselection:`회계" +" --> 환경 설정 --> 세금`에서 관리할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:382 msgid "Chile has several tax types, the most common ones are:" -msgstr "" +msgstr "칠레의 세금에는 여러 가지 종류가 있으며, 가장 일반적인 세금 유형은 다음과 같습니다:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:384 msgid "**VAT**: the regular VAT can have several rates." -msgstr "" +msgstr "**VAT**: 일반 부가가치세에는 여러 가지 세율이 적용될 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:385 msgid "**ILA**: the tax for alcoholic drinks." -msgstr "" +msgstr "**ILA**: 주류에 대한 세금입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:388 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 @@ -25599,7 +25896,7 @@ msgstr ":doc:`../accounting/taxes`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:394 msgid "Electronic invoice workflow" -msgstr "" +msgstr "전자 청구서 작업 흐름" #: ../../content/applications/finance/fiscal_localizations/chile.rst:396 msgid "" @@ -25608,14 +25905,16 @@ msgid "" "explains how information is shared to the :abbr:`SII (Servicio de Impuestos " "Internos)`, customers, and vendors." msgstr "" +"칠레 현지화에서는 전자 청구서 작업 흐름에 고객 청구서 발행 및 공급업체 청구서 수신 작업이 포함되어 있습니다. 다음 다이어그램은 정보가" +" :abbr:`SII (Servicio de Impuestos Internos)`, 고객 및 공급업체와 공유되는 방식을 설명합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Diagram with Electronic invoice transactions." -msgstr "" +msgstr "전자 청구서 거래에 대한 다이어그램" #: ../../content/applications/finance/fiscal_localizations/chile.rst:405 msgid "Customer invoice emission" -msgstr "" +msgstr "고객 청구서 발행" #: ../../content/applications/finance/fiscal_localizations/chile.rst:407 msgid "" @@ -25625,10 +25924,13 @@ msgid "" "document type can be changed manually if needed on the invoice by navigating" " to :menuselection:`Accounting --> Customers --> Invoices`." msgstr "" +"파트너 및 전표를 생성하고 환경 설정을 완료한 후에는 표준 방식으로 청구서가 생성됩니다. 칠레의 경우 차이점 중 하나는 납세자를 기준으로" +" 자동 선택되는 문서 유형입니다. 필요한 경우 :menuselection:`회계 --> 고객 --> 청구서`로 이동하여 청구서에서 문서 " +"유형을 직접 변경할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Customer invoice document type selection." -msgstr "" +msgstr "고객 청구서 문서 유형 선택" #: ../../content/applications/finance/fiscal_localizations/chile.rst:417 msgid "" @@ -25636,34 +25938,39 @@ msgid "" " with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` " "rejects the document validation." msgstr "" +":guilabel:`문서 유형 33` 전자 청구서에는 세금이 포함된 항목이 반드시 하나 이상 있어야 합니다. 그렇지 않으면 " +":abbr:`SII (Servicio de Impuestos Internos)`가 문서 승인이 거부됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:423 #: ../../content/applications/finance/fiscal_localizations/chile.rst:875 msgid "Validation and DTE status" -msgstr "" +msgstr "승인 및 DTE 상태" #: ../../content/applications/finance/fiscal_localizations/chile.rst:425 msgid "" "Once all invoice information is filled, either manually or automatically " "when generated from a sales order, validate the invoice. After the invoice " "is posted:" -msgstr "" +msgstr "판매주문서에서 생성될 당시 직접 혹은 자동으로 청구서 정보가 모두 입력되었으면, 청구서를 승인합니다. 청구서가 게시된 후:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:428 msgid "" "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file is created " "automatically and recorded in the chatter." msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` 파일이 자동으로 생성되어 메시지창에 기록됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:430 msgid "" "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio " "de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio de " +"Impuestos Internos)` 상태는 :guilabel:`보류 중`으로 설정되어 전송됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "DTE XML File displayed in chatter." -msgstr "" +msgstr "메시지창에 표시되는 DTE XML 파일" #: ../../content/applications/finance/fiscal_localizations/chile.rst:437 msgid "" @@ -25673,10 +25980,14 @@ msgid "" "needed immediately, you can do it manually as well by following the " ":abbr:`DTE (Documentos Tributarios Electrónicos)` status workflow:" msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` 상태는 Odoo에서 매일 밤 실행되는 예약 " +"작업으로 자동으로 업데이트되며, :abbr:`SII (Servicio de Impuestos Internos)`의 응답이 즉시 필요한 " +"경우에는.:abbr:`DTE (Documentos Tributarios Electrónicos)` 상태 작업 흐름에 따라 직접 수행할 " +"수도 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Transition of DTE status flow." -msgstr "" +msgstr "DTE 상태 흐름 전환" #: ../../content/applications/finance/fiscal_localizations/chile.rst:446 msgid "" @@ -25688,6 +25999,11 @@ msgid "" "via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for" " Status`." msgstr "" +"첫 번째 단계는 :abbr:`DTE (Documentos Tributarios Electrónicos)`를 :abbr:`SII " +"(Servicio de Impuestos Internos)`로 전송하는 것입니다. :guilabel:`Enviar Ahora` 버튼을 " +"클릭하여 직접 전송할 수 있습니다. 그러면 청구서에 대한 :guilabel:`SII 택 번호`가 생성됩니다. 이 번호는 " +":abbr:`SII (Servicio de Impuestos Internos)`에서 이메일을 통해 전송한 세부 정보를 확인하는 데 " +"사용합니다. 그러면 :guilabel:`DTE 상태`가 :guilabel:`상태 문의`로 업데이트됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:451 msgid "" @@ -25697,10 +26013,13 @@ msgid "" ":guilabel:`Accepted`, :guilabel:`Accepted With Objection` or " ":guilabel:`Rejected`." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 응답이 수신되면 Odoo에서 :guilabel:`DTE " +"상태`가 업데이트됩니다. 직접 수행하려면 :guilabel:`SII에서 확인` 버튼을 클릭합니다. 결과는 :guilabel:`수락 " +"완료`, :guilabel:`이의 사항과 함께 수락` 또는 :guilabel:`거부됨` 중 하나가 됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "Identification transaction for invoice and Status update." -msgstr "" +msgstr "청구서 및 상태 업데이트를 식별하기 위한 작업" #: ../../content/applications/finance/fiscal_localizations/chile.rst:461 msgid "" @@ -25708,22 +26027,28 @@ msgid "" "Internos)` before acceptance or rejection. It's recommended to **NOT** " "continuously click :guilabel:`Verify in SII` for smooth processing." msgstr "" +":abbr:`SII (Serviciqo de Impuestos Internos)`에는 수락 또는 거부 전의 중간 상태가 있습니다. " +"원활하기 처리하기 위해서는 계속해서 :guilabel:`SII 확인`을 계속해서 클릭하지 **않는** 것이 좋습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "Electronic invoice data statuses." -msgstr "" +msgstr "전자 청구서 데이터 상태" #: ../../content/applications/finance/fiscal_localizations/chile.rst:469 msgid "" "The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can" " take on one of these values:" msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)`으로부터의 최종 응답은 다음 값 중 하나가 될 수 " +"있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:472 msgid "" ":guilabel:`Accepted`: indicates the invoice information is correct, our " "document is now fiscally valid and it's automatically sent to the customer." msgstr "" +":guilabel:`수락 완료`: 청구서 정보가 정확하다는 의미로, 이제 문서가 재정적으로 유효하며 자동으로 고객에게 전송되었음을 " +"나타냅니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:474 msgid "" @@ -25731,6 +26056,8 @@ msgid "" "correct, but a minor issue was identified, nevertheless the document is now " "fiscally valid and it's automatically sent to the customer." msgstr "" +":guilabel:`이의 사항과 함께 승인`: 청구서 정보가 정확하다는 의미로, 사소한 문제가 있기는 하지만 문서가 이제 재정적으로 " +"유효하며 자동으로 고객에게 전송되었음을 나타냅니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:477 msgid "" @@ -25740,32 +26067,37 @@ msgid "" "in Odoo, the details are also retrieved in the chatter once the email server" " is processed." msgstr "" +":guilabel:`거부됨`: 청구서 정보가 올바르지 않아 수정해야 함을 나타냅니다. 자세한 내용은 :abbr:`SII (Servicio" +" de Impuestos Internos)`에 등록한 이메일로 전송됩니다. Odoo에서 올바르게 환경 설정이 된 경우, 이메일 서버가 " +"처리되면 세부 정보도 메시지창에서 검색할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:482 msgid "If the invoice is rejected please follow these steps:" -msgstr "" +msgstr "청구서가 거부된 경우 다음 단계를 따르세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:484 msgid "Change the document to :guilabel:`Draft`." -msgstr "" +msgstr "문서를 :guilabel:`초안`으로 변경합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:485 msgid "" "Make the required corrections based on the message received from the " ":abbr:`SII (Servicio de Impuestos Internos)` in the chatter." msgstr "" +"메시지창에서 :abbr:`SII (Servicio de Impuestos Internos)`으로부터 받은 메시지에 따라 필요한 내용을 " +"수정합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:487 msgid "Post the invoice again." -msgstr "" +msgstr "청구서를 다시 발행합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "Message when an invoice is rejected." -msgstr "" +msgstr "청구서가 거부된 경우의 메시지입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:494 msgid "Crossed references" -msgstr "" +msgstr "교차 참조" #: ../../content/applications/finance/fiscal_localizations/chile.rst:496 msgid "" @@ -25776,17 +26108,20 @@ msgid "" " well. In the case of the credit and debit notes, they are set automatically" " by Odoo." msgstr "" +"다른 회계 문서에서 작업 결과 청구서가 생성되는 경우에는, 반드시 원본 문서에 대한 정보가 :guilabel:`상호 참조` 탭에 " +"등록되어야 합니다. 보통 이 탭은 대변 또는 차변전표 작업에 사용하지만 경우에 따라 고객 청구서에도 사용할 수 있습니다. 대변 및 " +"차변전표의 경우 Odoo에서 자동으로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Crossed referenced document(s)." -msgstr "" +msgstr "교차 참조 문서" #: ../../content/applications/finance/fiscal_localizations/chile.rst:508 #: ../../content/applications/finance/fiscal_localizations/india.rst:133 #: ../../content/applications/finance/fiscal_localizations/india.rst:271 #: ../../content/applications/finance/fiscal_localizations/peru.rst-1 msgid "Invoice PDF report" -msgstr "" +msgstr "청구서 PDF 보고서" #: ../../content/applications/finance/fiscal_localizations/chile.rst:510 msgid "" @@ -25794,10 +26129,12 @@ msgid "" "Impuestos Internos)` and the PDF is printed, it includes the fiscal elements" " that indicate that the document is fiscally valid." msgstr "" +"청구서를 승인하여 :abbr:`SII (Servicio de Impuestos Internos)`에 의해 검증되고 PDF로 인쇄되면 " +"문서가 재정적으로 유효함을 나타내는 재정 요소가 포함되게 됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "SII Validation fiscal elements." -msgstr "" +msgstr "SII 승인 재정 요소" #: ../../content/applications/finance/fiscal_localizations/chile.rst:519 msgid "" @@ -25805,40 +26142,43 @@ msgid "" "`pdf417gen <https://pypi.org/project/pdf417gen/>`_ library. Use the " "following command to install it: :command:`pip install pdf417gen`." msgstr "" +"Odoo SH 또는 온프레미스에서 호스팅하는 경우, `pdf417gen " +"<https://pypi.org/project/pdf417gen/>`_ 라이브러리를 수동으로 설치해야 합니다. 다음 명령어를 사용하여 " +"설치합니다: :command:`pip install pdf417gen`." #: ../../content/applications/finance/fiscal_localizations/chile.rst:524 msgid "Commercial validation" -msgstr "" +msgstr "상업용 승인" #: ../../content/applications/finance/fiscal_localizations/chile.rst:526 msgid "Once the invoice has been sent to the customer:" -msgstr "" +msgstr "청구서가 고객에게 전송되면 다음과 같이 진행합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:528 msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." -msgstr "" +msgstr ":guilabel:`DTE 파트너 상태`가 :guilabel:`전송 완료`로 변경됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:529 msgid "The customer must send a reception confirmation email." -msgstr "" +msgstr "고객은 반드시 수신 확인 이메일을 전송해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:530 msgid "" "Subsequently, if commercial terms and invoice data are correct, an " "acceptance confirmation is sent; otherwise, a claim is sent." -msgstr "" +msgstr "그 후에, 상업적 조건과 청구서 데이터가 정확하면 수락 확인이 전송됩니다. 그렇지 않은 경우 클레임이 전송됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:532 msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." -msgstr "" +msgstr ":guilabel:`DTE 승인 상태` 필드가 자동으로 업데이트됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Message with the commercial acceptance from the customer." -msgstr "" +msgstr "고객으로부터 상업용 승인을 받은 메시지입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:539 msgid "Processed for claimed invoices" -msgstr "" +msgstr "클레임을 받은 청구서 처리" #: ../../content/applications/finance/fiscal_localizations/chile.rst:541 msgid "" @@ -25848,15 +26188,18 @@ msgid "" "cancel the invoice or correct it. Please refer to the :ref:`chile/credit-" "notes` section for more details." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)`에서 청구서 승인이 완료된 경우에는, **Odoo에서 " +"취소할 수 없습니다**. 고객으로부터 클레임이 발생한 경우, 올바른 진행 방법은 대변전표를 사용하여 청구서를 취소하거나 수정하는 " +"것입니다. 자세한 내용은 :ref:`칠레/대변전표` 섹션을 참조합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Invoice Commercial status updated to claimed." -msgstr "" +msgstr "청구서의 상업용 상태가 클레임 상태로 업데이트되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:551 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 msgid "Common errors" -msgstr "" +msgstr "일반적인 오류" #: ../../content/applications/finance/fiscal_localizations/chile.rst:553 msgid "" @@ -25864,30 +26207,32 @@ msgid "" "de Impuestos Internos)`, but these are some of the common errors you might " "have and how to solve them:" msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` 거부에는 여러 가지 이유가 있으나, 다음과 같이 " +"일반적으로 발생하는 오류 및 해결 방법이 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "**Error:** `RECHAZO- DTE Sin Comuna Origen`" -msgstr "" +msgstr "**오류:** `RECHAZO- DTE Sin Comuna Origen`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Hint:** make sure the company address is properly filled including the " "state and city." -msgstr "" +msgstr "**도움말:** 지역과 도로명을 포함하여 회사 주소가 제대로 입력되었는지 확인합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "**Error:** `en Monto - IVA debe declararse`" -msgstr "" +msgstr "**오류:**`en Monto - IVA debe declararse`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Hint:** the invoice lines should include one VAT tax, make sure you add " "one on each invoice line." -msgstr "" +msgstr "**도움말:** 청구서 내역에는 부가가치세 한 항목이 포함되어야 있어야 하며, 각 청구서 내역에 하나씩 추가해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "**Error:** `Rut No Autorizado a Firmar`" -msgstr "" +msgstr "**오류:** `Rut No Autorizado a Firmar`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" @@ -25896,34 +26241,43 @@ msgid "" "Tributario)` is correct and is valid in the :abbr:`SII (Servicio de " "Impuestos Internos)` to invoice electronically." msgstr "" +"**도움말:** 입력한 :abbr:`RUT (Rol Único Tributario)`는 전자 청구서를 발행하는 것이 허용되지 않으므로 " +"회사 :abbr:`RUT (Rol Único Tributario)`가 정확하고 :abbr:`SII (Servicio de " +"Impuestos Internos)`에서 유효한지 확인하여 전자 청구서를 발행해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Error:** `Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : " "(Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses`" msgstr "" +"**오류:** `Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : " +"(Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Hint:** try to add a new CAF related to this document as the one you're " "using is expired." -msgstr "" +msgstr "**도움말:** 사용 중인 CAF가 만료되었으므로 이 문서와 관련된 새로운 CAF를 추가하세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Error:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element " "is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`" msgstr "" +"**오류:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element is " +"not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Hint:** Make sure the field :guilabel:`Document Type` and :guilabel:`VAT` " "are set in the customer and in the main company." msgstr "" +"**도움말:** :guilabel:`문서 유형` 및 :guilabel:`부가가치세` 필드가 고객과 주요 회사에 설정되어 있는지 " +"확인합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "**Error:** `Usuario sin permiso de envio.`" -msgstr "" +msgstr "**오류:** `Usuario sin permiso deevio.`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" @@ -25939,28 +26293,35 @@ msgid "" "Tributarios Electrónicos)` files to the :abbr:`SII (Servicio de Impuestos " "Internos)`." msgstr "" +"**도움말:** 이 오류는 귀하의 회사가 `인증 프로세스 " +"<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" +" in the :abbr:`SII (Servicio de Impuestos Internos)` - Sistema de " +"Facturación de Mercado 를 통과하지 못했다는 것을 나타냅니다. 이러한 경우, 인증이 Odoo 서비스에 포함되는 것은 " +"아니나 몇 가지 대안을 드릴 수 있도록 계정 관리자나 고객 지원팀에 문의하시기 바랍니다. 이미 인증 프로세스를 통과한 경우에 이 오류는," +" 인증서 소유자가 아닌 다른 사용자가 :abbr:`DTE (Documentos Tributarios Electrónicos)` 파일을 " +":abbr:`SII (Servicio de Impuestos Internos)로 파일을 보내려고 할 때 나타납니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "**Error:** `CARATULA`" -msgstr "" +msgstr "**오류:** `CARATULA` " #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "" "**Hint:** there are just five reasons why this error could show up and all " "of them are related to the *Caratula* section of the XML:" -msgstr "" +msgstr "**도움말:** 이 오류가 나타나는 이유로는 다섯 가지가 있으며 모두 XML의 *Caratula* 섹션과 관련이 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:585 msgid "" "The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or " "missing." -msgstr "" +msgstr "회사의 :abbr:`RUT (Rol Único Tributario)` 번호가 올바르지 않거나 누락되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:586 msgid "" "The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect" " or missing." -msgstr "" +msgstr "인증서 소유자 :abbr:`RUT (Rol Único Tributario)` 번호가 올바르지 않거나 누락되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:587 msgid "" @@ -25968,14 +26329,16 @@ msgid "" "Tributario)` number (this should be correct by default) is incorrect or " "missing." msgstr "" +":abbr:`SII (Servicio de Impuestos Internos)` :abbr:`RUT(Rol Único " +"Tributario)` 번호 (기본적으로 정확해야 함)가 잘못되었거나 누락되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:589 msgid "The resolution date is incorrect or missing." -msgstr "" +msgstr "결의 날짜가 잘못되었거나 누락되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:590 msgid "The resolution number is incorrect or missing." -msgstr "" +msgstr "결의 번호가 올바르지 않거나 누락되었습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:597 msgid "" @@ -25987,10 +26350,15 @@ msgid "" "<chile/caf-documentation>` for more information on the process to load the " ":abbr:`CAF (Folio Authorization Code)` on each document type." msgstr "" +"승인된 청구서를 취소하거나 수정해야 하는 경우에는 대변전표를 생성해야 합니다. 대변전표에는 :abbr:`CAF (Folio " +"Authorization Code)` 파일이 있어야 하며, 이 파일은 :abbr:`SII (Servicio de Impuestos " +"Internos)`에서 :guilabel:`문서 유형` :guilabel:`61`로 식별됩니다. 각 문서 유형에 :abbr:`CAF " +"(Folio Authorization Code)`를 불러오는 프로세스에 대한 자세한 내용은 :ref:`CAF 섹션 <chile/caf-" +"documentation>`을 참조합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Creation of CAF for Credit notes." -msgstr "" +msgstr "대변전표용 CAF 생성" #: ../../content/applications/finance/fiscal_localizations/chile.rst:609 #: ../../content/applications/finance/fiscal_localizations/chile.rst:665 @@ -25999,7 +26367,7 @@ msgstr "사용 사례" #: ../../content/applications/finance/fiscal_localizations/chile.rst:612 msgid "Cancel referenced document" -msgstr "" +msgstr "참조 문서 취소" #: ../../content/applications/finance/fiscal_localizations/chile.rst:614 msgid "" @@ -26010,14 +26378,18 @@ msgid "" " Internos)` reference code is automatically set to :guilabel:`Anula " "Documento de referencia`." msgstr "" +"청구서를 취소하거나 승인을 취소해야 하는 경우 :menuselection:`회계 --> 고객 --> 청구서`로 이동하여 원하는 청구서를 " +"선택합니다. 그런 다음 :guilabel:`대변전표 추가` 버튼을 사용하여 :guilabel:`전액 환불`를 선택합니다. 이 경우 " +":abbr:`SII (Servicio de Impuestos Internos)` 참조 코드는 자동으로 :guilabel:`Anula " +"Documento de referencia`로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Credit note canceling the referenced document." -msgstr "" +msgstr "참조된 문서가 취소되는 대변전표" #: ../../content/applications/finance/fiscal_localizations/chile.rst:624 msgid "Correct referenced document" -msgstr "" +msgstr "정확한 참조 문서" #: ../../content/applications/finance/fiscal_localizations/chile.rst:626 msgid "" @@ -26028,30 +26400,33 @@ msgid "" " Reference Code` field is automatically set to :guilabel:`Corrects " "Referenced Document Text`." msgstr "" +"청구서 정보를 수정해야 하는 경우, 예를 들어 원본 청구서의 도로명 이름이 잘못된 경우에는, :guilabel:`대변전표 추가` 버튼을 " +"사용하여 :guilabel:`일부 환불`을 선택한 다음 :guilabel:`텍스트 수정만` 옵션을 선택합니다. 이 경우 " +":guilabel:`SII 참조 코드` 필드는 자동으로 :guilabel:`참조된 문서 텍스트 수정`으로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Credit note correcting referenced document text." -msgstr "" +msgstr "참조된 문서 텍스트를 수정하는 대변전표" #: ../../content/applications/finance/fiscal_localizations/chile.rst:635 msgid "" "Odoo creates a credit note with the corrected text in an invoice and " ":guilabel:`Price` `0.00`." -msgstr "" +msgstr "Odoo는 청구서에서 수정된 텍스트와 :guilabel:`가격`으로 `0.00`을 사용하여 대변전표를 생성합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Credit note with the corrected value on the invoice lines." -msgstr "" +msgstr "청구서 내역 값을 수정하는 대변전표입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:642 msgid "" "Make sure to define the :guilabel:`Default Credit Account` in the sales " "journal specifically for this use case." -msgstr "" +msgstr "이 사용 사례에 맞도록 특별히 판매 전표에 :guilabel:`기본 차변 계정`을 지정해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:646 msgid "Corrects referenced document amount" -msgstr "" +msgstr "참조 문서 금액을 수정합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:648 msgid "" @@ -26060,17 +26435,20 @@ msgid "" ":guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el" " monto del Documento de Referencia`." msgstr "" +"금액을 수정해야 하는 경우에는 :guilabel:`대변전표 추가` 버튼을 사용하여 :guilabel:`일부 환불`을 선택합니다. 이 경우" +" :guilabel:`SII 참조 코드`는 자동으로 :guilabel:`Corrige el monto del Documento de " +"Referencia`로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "" "Credit note for partial refund to correct amounts, using the SII reference " "code 3." -msgstr "" +msgstr "SII 참조 코드 3을 사용하여 정확한 금액으로 일부 환불을 하기 위한 대변전표" #: ../../content/applications/finance/fiscal_localizations/chile.rst:657 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Debit notes" -msgstr "" +msgstr "차변전표" #: ../../content/applications/finance/fiscal_localizations/chile.rst:659 msgid "" @@ -26078,10 +26456,12 @@ msgid "" "created using the :guilabel:`Add Debit Note` button, with two main use " "cases." msgstr "" +"칠레 현지화에서는 :guilabel:`차변전표 추가` 버튼을 사용하여 대변전표 외에도 차변전표를 생성할 수 있으며 주요 사용 사례로는 두" +" 가지가 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:668 msgid "Add debt on invoices" -msgstr "" +msgstr "청구서에 차변전표 추가하기" #: ../../content/applications/finance/fiscal_localizations/chile.rst:670 msgid "" @@ -26089,29 +26469,31 @@ msgid "" " invoice. To do so, select option :guilabel:`3. Corrige el monto del " "Documento de Referencia` for the :guilabel:`Reference Code SII` field." msgstr "" +"차변전표는 주로 기존의 청구서 값을 높이기 위해 사용합니다. 그렇게 하려면 :guilabel:`참조 코드 SII` 필드에 대하여 " +":guilabel:`3. Corrige el monto del Documento de Referencia`를 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Debit note correcting referenced document amount." -msgstr "" +msgstr "참조 문서 금액을 수정하는 차변전표" #: ../../content/applications/finance/fiscal_localizations/chile.rst:678 msgid "" "In this case Odoo automatically includes the :guilabel:`Source Invoice` in " "the :guilabel:`Cross Reference` tab." -msgstr "" +msgstr "이 경우 Odoo에서는 :guilabel:`원본 청구서`가 :guilabel:`상호 참조` 탭에 자동으로 들어가 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Automatic reference to invoice in a debit note." -msgstr "" +msgstr "차변전표의 청구서에 대한 자동 참조" #: ../../content/applications/finance/fiscal_localizations/chile.rst:686 msgid "" "You can only add debit notes to an invoice already accepted by the SII." -msgstr "" +msgstr "SII에서 이미 승인한 청구서에만 차변전표를 추가할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:689 msgid "Cancel credit notes" -msgstr "" +msgstr "대변전표 취소" #: ../../content/applications/finance/fiscal_localizations/chile.rst:691 msgid "" @@ -26120,10 +26502,13 @@ msgid "" "Anula Documentos de referencia` option for the :guilabel:`Reference Code " "SII` field." msgstr "" +"칠레에서는 차변전표를 사용하여 유효한 대변전표를 취소할 수 있습니다. 이렇게 하려면 :guilabel:`차변전표 추가` 버튼을 클릭하고 " +":guilabel:`참조 코드 SII` 필드에 대해 :guilabel:`1: Anula Documentos de Referencia` " +"옵션을 선택합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Debit note to cancel the referenced document (credit note)." -msgstr "" +msgstr "참조 문서를 취소하는 차변전표 (대변전표)" #: ../../content/applications/finance/fiscal_localizations/chile.rst:702 msgid "" @@ -26131,47 +26516,52 @@ msgid "" "server to match the one you have registered in the :abbr:`SII (Servicio de " "Impuestos Internos)` in order to:" msgstr "" +"칠레 현지화의 일부로 수신 이메일 서버를 :abbr:`SII (Servicio de Impuestos Internos)`에 등록한 서버에" +" 맞도록 설정하여 다음과 같이 진행할 수 있습니다" #: ../../content/applications/finance/fiscal_localizations/chile.rst:705 msgid "" "Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios " "Electrónicos)` and create the vendor bill based on this information." msgstr "" +"공급업체 청구서 :abbr:`DTE (Documentos Tributarios Electrónicos)`를 자동 수신하고 이 정보를 " +"기반으로 공급업체 청구서를 생성합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:707 msgid "Automatically send the reception acknowledgement to your vendor." -msgstr "" +msgstr "자동으로 공급업체에 수신 확인을 전송합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:708 msgid "Accept or claim the document and send this status to your vendor." -msgstr "" +msgstr "문서를 수락하거나 청구한 후 이 상태를 공급업체로 전송합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:711 msgid "Reception" -msgstr "" +msgstr "수신하기" #: ../../content/applications/finance/fiscal_localizations/chile.rst:713 msgid "" "As soon as the vendor email with the attached :abbr:`DTE (Documentos " "Tributarios Electrónicos)` is received:" msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)`가 첨부된 공급업체 이메일 수신 즉시:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:716 msgid "The vendor bill maps all the information included in the XML." -msgstr "" +msgstr "공급업체 청구서는 XML에 포함되어 있는 모든 정보를 매핑합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:717 msgid "An email is sent to the vendor with the reception acknowledgement." -msgstr "" +msgstr "공급업체에 수신 확인 이메일을 전송합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:718 msgid "" "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." -msgstr "" +msgstr ":guilabel:`DTE 상태`는 :guilabel:`Acuse de Recibido Enviado`로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:721 msgid "Acceptation" -msgstr "" +msgstr "수락" #: ../../content/applications/finance/fiscal_localizations/chile.rst:723 msgid "" @@ -26180,10 +26570,13 @@ msgid "" " this is done, the :guilabel:`DTE Acceptation Status` changes to " ":guilabel:`Accepted` and an email of acceptance is sent to the vendor." msgstr "" +"공급업체 청구서에 있는 비즈니스 정보가 모두 정확하면 :guilabel:`Aceptar Documento` 버튼을 사용하여 문서를 수락할" +" 수 있습니다. 이 작업이 완료되면 :guilabel:`DTE 수락 상태`가 :guilabel:`수락 완료`로 변경되고 수락 이메일이 " +"공급업체에 전송됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Button for accepting vendor bills." -msgstr "" +msgstr "공급업체 청구서를 수락하는 버튼입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:732 msgid "Claim" @@ -26197,12 +26590,17 @@ msgid "" " Status` changes to :guilabel:`Claim` and a rejection email is sent to the " "vendor." msgstr "" +"상업적인 문제가 있거나 공급업체 청구서의 정보가 정확하지 않은 경우, :guilabel:`클레임` 버튼을 사용하여 승인하기 전에 문서에 " +"대한 클레임을 할 수 있습니다. 이 작업이 완료되면 :guilabel:`DTE 수락 상태`가 :guilabel:`클레임`으로 변경되고 " +"거절하는 이메일이 공급업체에 전송됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "" "Claim button in vendor bills to inform the vendor all the document is commercially\n" "rejected." msgstr "" +"모든 문서가 상업 용도로 거부되었음을 공급업체에 알리는 공급업체 청구서의 클레임\n" +"버튼" #: ../../content/applications/finance/fiscal_localizations/chile.rst:744 msgid "" @@ -26211,11 +26609,13 @@ msgid "" " claimed documents should be canceled as they won't be valid for your " "accounting records." msgstr "" +"공급업체 청구서에 대해 클레임을 하면 상태가 :guilabel:`초안`에서 :guilabel:`취소`로 자동 변경됩니다. 클레임한 문서는" +" 모두 회계 기록에 유효하지 않게 되므로 취소하는 것이 좋습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:749 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 msgid "Delivery guide" -msgstr "" +msgstr "배송 가이드" #: ../../content/applications/finance/fiscal_localizations/chile.rst:751 msgid "" @@ -26224,6 +26624,8 @@ msgid "" ":guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery " "Guide`." msgstr "" +":guilabel:`배송 가이드` 모듈을 설치하려면 :menuselection:`앱`으로 이동하여 `Chile (l10n_cl)`을 " +"검색합니다. 그런 다음 :guilabel:`칠레 - 전자 청구서 배송 가이드` 모듈에서 :guilabel:`설치`를 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:756 msgid "" @@ -26232,6 +26634,8 @@ msgid "" "dependency automatically when the :guilabel:`Delivery Guide` module is " "installed." msgstr "" +":guilabel:`칠레 - 전자 청구서 배송 가이드`는 :guilabel:`칠레 - Facturación Electrónica`에 " +"종속되어 있습니다. Odoo는 :guilabel:`배송 가이드` 모듈이 설치될 때 자동으로 종속된 항목을 설치합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:760 msgid "" @@ -26239,6 +26643,8 @@ msgid "" "(Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos " "Internos)` and the stamp in PDF reports for deliveries." msgstr "" +"*배송 가이드* 모듈에는 :abbr:`DTE (Documentos Tributarios Electrónicos)`를 :abbr:`SII " +"(Servicio de Impuestos Internos)`로 전송하는 기능과 배송용 PDF 보고서 스탬프가 포함되어 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:764 msgid "" @@ -26249,28 +26655,32 @@ msgid "" "<chile/caf-documentation>` to check the details on how to acquire the " ":abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." msgstr "" +":ref:`전자 청구서 <chile/electronic-invoice>`에 대한 환경 설정이 모두 완료되면 (예: 유효한 회사 인증서 " +"업로드, 마스터 데이터 설정 등) 배송 가이드에 자체 :abbr:`CAF(Folio Authorization Code)`가 있어야 " +"합니다. 전자 배송 가이드용 :abbr:`CAF(폴리오 인증 코드)`를 받는 방법에 대한 자세한 내용은 :ref:`CAF 문서 " +"<chile/caf-documentation>`을 참조하시기 바랍니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:770 msgid "" "Verify the following important information in the :guilabel:`Price for the " "Delivery Guide` configuration:" -msgstr "" +msgstr ":guilabel:`배송 가이드 가격`의 환경 설정 메뉴에서 다음과 같은 중요 정보를 확인합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:773 msgid "" ":guilabel:`From Sales Order`: delivery guide takes the product price from " "the sales order and shows it on the document." -msgstr "" +msgstr ":guilabel:`판매주문서에서`: 배송 가이드는 판매주문서에서 품목 가격을 가져와서 문서에 표시합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:775 msgid "" ":guilabel:`From Product Template`: Odoo takes the price configured in the " "product template and shows it on the document." -msgstr "" +msgstr ":guilabel:`품목 서식에서`: Odoo는 품목 서식에 설정되어 있는 가격을 가져와서 문서에 표시합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:777 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." -msgstr "" +msgstr ":guilabel:`가격 표시 없음`: 배송 가이드에 가격이 표시되지 않습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:779 msgid "" @@ -26278,33 +26688,35 @@ msgid "" "and they can represent sales, sampling, consignment, internal transfers, and" " basically any product move." msgstr "" +"전자 배송 가이드는 재고를 한 장소에서 다른 장소로 이동하기 위해 사용하며 판매, 샘플링, 위탁, 내부 이전과 함께 기본적으로 모든 품목" +" 이동을 표시할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:783 msgid "Delivery guide from a sales process" -msgstr "" +msgstr "판매 프로세스에서의 배송 가이드" #: ../../content/applications/finance/fiscal_localizations/chile.rst:786 msgid "" "A delivery guide should **not** be longer than one page or contain more than" " 60 product lines." -msgstr "" +msgstr "배송 가이드에서 품목 내역이 한 페이지를 초과하거나 60개를 초과해서는 **안 됩니다**." #: ../../content/applications/finance/fiscal_localizations/chile.rst:788 msgid "" "When a sales order is created and confirmed, a delivery order is generated. " "After validating the delivery order, the option to create a delivery guide " "is activated." -msgstr "" +msgstr "판매주문서를 생성하고 확정되면 배송주문서가 생성됩니다. 배송주문서를 승인하면 배송 가이드를 생성하는 옵션이 활성화됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Create Delivery Guide button on a sales process." -msgstr "" +msgstr "판매 프로세스에서 배송 가이드 버튼을 생성합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:796 msgid "" "When clicking on :guilabel:`Create Delivery Guide` for the first time, a " "warning message pops up, stating the following:" -msgstr "" +msgstr ":guilabel:`배송 가이드 만들기`를 처음으로 클릭하면, 다음과 같은 경고 메시지가 나타납니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:799 msgid "" @@ -26312,10 +26724,13 @@ msgid "" "establezca el primer número dentro del campo número para la guía de " "despacho`" msgstr "" +"`No se encontró una secuencia para la guía de despacho. Por favor, " +"establezca el primer número dentro del campo número para la guía de " +"despacho`" #: ../../content/applications/finance/fiscal_localizations/chile.rst:0 msgid "First Delivery Guide number warning message." -msgstr "" +msgstr "첫 배송 가이드의 번호에 대한 경고 메시지입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:806 msgid "" @@ -26326,26 +26741,32 @@ msgid "" "correctly generated, Odoo takes the next available number in the :abbr:`CAF " "(Folio Authorization Code)` file to generate the following delivery guide." msgstr "" +"이 경고 메시지는 Odoo에서 배송 가이드를 생성할 다음 연번을 사용자가 지정해야 한다는 내용이며 (예: 다음 순서로 사용할 수 있는 " +":abbr:`CAF (Folio Authorization Code)` 번호) 배송 가이드를 처음으로 생성한 경우에만 안내하는 " +"메시지입니다. 첫 번째 문서가 정확히 생성되었다면, Odoo는 :abbr:`CAF (Folio Authorization Code)` " +"파일에서 다음 순서로 사용할 수 있는 배송 가이드 번호를 가져옵니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:812 msgid "After the delivery guide is created:" -msgstr "" +msgstr "배송 가이드가 생성된 후에는:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:814 msgid "" "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " "Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` 파일 (전자 세금 문서)이 자동으로 생성되어 " +":guilabel:`메시지창`에 추가됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:816 #: ../../content/applications/finance/fiscal_localizations/chile.rst:886 msgid "" "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." -msgstr "" +msgstr ":guilabel:`DTE SII Status`는 :guilabel:`발송 대기 중`으로 설정됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Chatter notes of Delivery Guide creation." -msgstr "" +msgstr "배송 가이드 생성에 대한 메시지창 메모" #: ../../content/applications/finance/fiscal_localizations/chile.rst:822 msgid "" @@ -26354,16 +26775,19 @@ msgid "" "(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" " to SII` button." msgstr "" +":guilabel:`DTE 상태`는 매일 밤 실행되는 예약 작업을 통해 Odoo에서 자동으로 업데이트됩니다. :abbr:`SII " +"(Servicio de Impuestos Internos)`에서 즉시 응답을 받으려면 :guilabel:`지금 SII로 보내기` 버튼을 " +"누르세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:826 msgid "" "Once the delivery guide is sent, it may then be printed by clicking on the " ":guilabel:`Print Delivery Guide` button." -msgstr "" +msgstr "배송 가이드가 전송된 후에는, :guilabel:`배송 가이드 인쇄` 버튼을 클릭하여 인쇄할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Printing Delivery Guide PDF." -msgstr "" +msgstr "배송 가이드 PDF 인쇄" #: ../../content/applications/finance/fiscal_localizations/chile.rst:833 msgid "" @@ -26372,10 +26796,13 @@ msgid "" "remember to manually add the :guilabel:`pdf417gen` library mentioned in the " ":ref:`Invoice PDF report section <chile/electronic-invoice-pdf-report>`)." msgstr "" +"배송 가이드에는 인쇄를 할 때 해당 문서가 회계상 유효한 문서임을 나타내는 회계 요소가 있습니다 (*Odoo SH* 또는 " +"*온프레미스*에서 호스팅되는 경우 :ref:`청구서 PDF 보고 섹션 <chile/electronic-invoice-pdf-" +"report>에 있는 :guilabel:`pdf417gen` 라이브러리를 수동으로 추가하시기 바랍니다)." #: ../../content/applications/finance/fiscal_localizations/chile.rst:839 msgid "Electronic receipt" -msgstr "" +msgstr "전자 영수증" #: ../../content/applications/finance/fiscal_localizations/chile.rst:841 msgid "" @@ -26383,6 +26810,8 @@ msgid "" ":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " ":guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." msgstr "" +":guilabel:`전자 영수증` 모듈을 설치하려면 :menuselection:`앱`으로 이동하여 `Chile (l10n_cl)`을 " +"검색합니다. 그런 다음 :guilabel:`칠레 - 전자 영수증` 모듈에서 :guilabel:`설치`를 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:846 msgid "" @@ -26391,6 +26820,8 @@ msgid "" "dependency automatically when the :guilabel:`E-invoicing Delivery Guide` " "module is installed." msgstr "" +":guilabel:`칠레 - 전자 영수증`은 :guilabel:`칠레 - Facturación Electrónica`에 종속된 " +"항목입니다. Odoo는 :guilabel:`전자 청구서 배송 가이드` 모듈이 설치되면 자동으로 종속 항목이 설치됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:850 msgid "" @@ -26401,6 +26832,10 @@ msgid "" "documentation <chile/caf-documentation>` to check the details on how to " "acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" +":ref:`전자 청구서 <chile/electronic-invoice>`에 대해 환경 설정이 모두 완료되면 (예: 유효한 회사 인증서 " +"업로드, 마스터 데이터 설정 등) 전자 영수증에 자체 :abbr:`CAF (Folio Authorization Code)`가 있어야 " +"합니다. 전자 영수증용 :abbr:`CAF (Folio Authorization Code)`를 받는 방법에 대한 자세한 내용은 " +":ref:`CAF 문서 <chile/caf-documentation>`를 참조하시기 바랍니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:856 msgid "" @@ -26411,10 +26846,14 @@ msgid "" "This partner can be used for electronic receipts or a new record may be " "created for the same purpose." msgstr "" +"전자 영수증은 전자 청구서를 필요로 하지 않는 고객이 있는 경우 유용합니다. 기본값으로, 데이터베이스에는 일반 :abbr:`RUT " +"(Rol Único Tributario)` `66666666-6` 및 납세자 유형이 :guilabel:`최종 소비자`인 " +":guilabel:`최종 익명 소비자`라는 파트너를 두고 있습니다. 이 파트너를 전자 영수증에 사용하거나 같은 목적으로 새로 기록을 " +"생성할 수 있습니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Electronic Receipt module." -msgstr "" +msgstr "전자 영수증 모듈" #: ../../content/applications/finance/fiscal_localizations/chile.rst:865 msgid "" @@ -26425,10 +26864,13 @@ msgid "" "but the type of document :guilabel:`(39) Electronic Receipt` should be " "selected in the invoice form:" msgstr "" +"전자 영수증은 일반 :abbr:`RUT (Rol Único Tributario)`를 사용하여 최종 소비자에게 사용되도록 해야 하지만, " +"특정 파트너 대상으로도 사용할 수 있습니다. 파트너 및 전표를 생성 및 설정하여 전자 영수증을 전자 청구서와 같이 표준 방식으로 생성하되" +" 청구서 양식에서 문서 유형 :guilabel:` (39) 전자 영수증`을 선택해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Document type 39 for Electronic Receipts." -msgstr "" +msgstr "전자 영수증의 경우 문서 유형 39입니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:877 msgid "" @@ -26439,16 +26881,21 @@ msgid "" "correctly, make sure to edit the :guilabel:`Document Type` and change to " ":guilabel:`Electronic Receipt`." msgstr "" +"전자 영수증 정보를 모두 입력했으면 수동 (또는 자동)으로 판매주문서에서 영수증을 검증합니다. 기본적으로 :guilabel:`문서 " +"유형`으로는 :guilabel:`전자 청구서`가 선택되지만, 영수증을 정확히 확인하려면 :guilabel:`문서 유형`을 편집하고 " +":guilabel:`전자 영수증`으로 변경해야 합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:882 msgid "After the receipt is posted:" -msgstr "" +msgstr "영수증 발행 후:" #: ../../content/applications/finance/fiscal_localizations/chile.rst:884 msgid "" "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " "Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" +":abbr:`DTE (Documentos Tributarios Electrónicos)` 파일 (전자 세금 문서)이 자동으로 생성되어 " +":guilabel:`메시지창`에 추가됩니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst-1 msgid "Electronic Receipts STE creation status." @@ -26461,6 +26908,9 @@ msgid "" "(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" " to SII` button." msgstr "" +":guilabel:`DTE 상태`는 매일 밤 시간대에 실행되는 예약 작업을 통해 Odoo에서 자동으로 업데이트됩니다. :abbr:`SII" +" (Servicio de Impuestos Internos)`에서 즉시 응답을 받으려면 :guilabel:`지금 SII로 보내기` 버튼을" +" 누르세요." #: ../../content/applications/finance/fiscal_localizations/chile.rst:896 msgid "" @@ -26471,7 +26921,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:900 msgid "Electronic export of goods" -msgstr "" +msgstr "전자 품목 출고" #: ../../content/applications/finance/fiscal_localizations/chile.rst:902 msgid "" @@ -26480,6 +26930,8 @@ msgid "" ":guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for" " Chile`." msgstr "" +":guilabel:`전자 품목 출고` 모듈을 설치하려면 :menuselection:`앱`으로 이동하여 `Chile (l10n_cl)`을 " +"검색합니다. 그런 다음 :guilabel:`칠레 - 전자 품목 출고` 모듈에서 :guilabel:`설치`를 클릭합니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:907 msgid "" @@ -26496,6 +26948,10 @@ msgid "" "documentation <chile/caf-documentation>` to check the details on how to " "acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" +":ref:`전자 청구서 <chile/electronic-invoice>`에 대해 환경 설정이 모두 완료되면 (예: 유효한 회사 인증서 " +"업로드, 마스터 데이터 설정 등) 전자 출고 항목에 자체 :abbr:`CAF (Folio Authorization Code)`가 있어야 " +"합니다. 전자 영수증용 :abbr:`CAF (Folio Authorization Code)`를 받는 방법에 대한 자세한 내용은 " +":ref:`CAF 문서 <chile/caf-documentation>`를 참조하시기 바랍니다." #: ../../content/applications/finance/fiscal_localizations/chile.rst:916 msgid "" @@ -38311,12 +38767,6 @@ msgid "" "platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "" diff --git a/locale/ko/LC_MESSAGES/inventory_and_mrp.po b/locale/ko/LC_MESSAGES/inventory_and_mrp.po index 14073f705..36cab6083 100644 --- a/locale/ko/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/ko/LC_MESSAGES/inventory_and_mrp.po @@ -7,8 +7,8 @@ # Martin Trigaux, 2023 # JH CHOI <hwangtog@gmail.com>, 2023 # Wil Odoo, 2024 -# Daye Jeong, 2024 # Sarah Park, 2024 +# Daye Jeong, 2024 # #, fuzzy msgid "" @@ -17,7 +17,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Sarah Park, 2024\n" +"Last-Translator: Daye Jeong, 2024\n" "Language-Team: Korean (https://app.transifex.com/odoo/teams/41243/ko/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17658,7 +17658,7 @@ msgstr "유지보수 세부 정보 추가" msgid "" "The :guilabel:`Maintenance` tab includes information that can be useful to " "maintenance teams:" -msgstr "" +msgstr ":guilabel:`유지보수` 탭에는 유지관리 팀에 도움이 될 수 있는 정보가 포함되어 있습니다:" #: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 msgid "" @@ -17670,17 +17670,17 @@ msgstr ":guilabel:`예방 유지보수 빈도`: 장비 고장을 방지하기 msgid "" ":guilabel:`Maintenance Duration`: the amount of time required to fix the " "equipment when it fails" -msgstr "" +msgstr ":guilabel:`유지보수 기간`: 장비 고장 시 고치는 데 필요한 시간입니다." #: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:72 msgid "" ":guilabel:`Expected Mean Time Between Failure`: the average amount of time " "that the equipment is expected to operate before failing" -msgstr "" +msgstr ":guilabel:`예상 평균 고장 간격`: 장비가 고장 나기 전에 작동할 것으로 예상되는 평균 시간입니다." #: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 msgid "The maintenance tab for the new piece of equipment." -msgstr "" +msgstr "새 장비에 대한 유지 관리 탭입니다." #: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:80 msgid "" @@ -17689,6 +17689,9 @@ msgid "" " Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated " "automatically based on maintenance requests if any exist." msgstr "" +":guilabel:`유지보수` 탭에는 :guilabel:`평균 장애 간격`, :guilabel:`예상 다음 장애`, " +":guilabel:`최근 장애`, :guilabel:`평균 복구 시간` 섹션도 포함되어 있습니다. 이러한 값은 유지 관리 요청이 있는 " +"경우 유지 관리 요청에 따라 자동으로 계산됩니다." #: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:86 msgid "" @@ -17696,6 +17699,7 @@ msgid "" " the equipment and select :guilabel:`Maintenance` in the top right corner of" " the form." msgstr "" +"장비에 대한 유지보수 요청을 확인하려면 해당 장비 페이지로 이동하여 양식의 오른쪽 상단에서 :guilabel:`유지보수`를 선택하세요." #: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 msgid "Manufacturing" @@ -17708,6 +17712,8 @@ msgid "" " shop floor to control work orders in real-time and allow workers to trigger" " maintenance operations, feedback loops, quality issues, etc." msgstr "" +"**Odoo 제조 관리**는 제조업체가 제조 주문을 예약, 계획 및 처리할 수 있도록 지원합니다. 작업 센터 제어판을 통해 작업 현장에 " +"태블릿을 배치하여 작업 주문을 실시간으로 제어하고 작업자가 유지보수 작업, 피드백 루프, 품질 문제 등을 트리거할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 msgid "`Odoo Tutorials: MRP <https://www.odoo.com/slides/mrp-29>`_" @@ -17737,6 +17743,8 @@ msgid "" "It can also include various operations and the individual step guidelines " "needed to complete a production process." msgstr "" +"*자재명세서*(또는 *BoM*)는 완제품을 생산하거나 납품하는 데 필요한 각 구성품의 수량을 명시한 문서입니다. 또한 생산 공정을 " +"완료하는 데 필요한 다양한 작업과 상세한 단계별 지침이 포함될 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:11 msgid "" @@ -17744,12 +17752,14 @@ msgid "" "linked to each product, so even product variants can have their own tailored" " :abbr:`BoMs (Bills of Materials)`." msgstr "" +"Odoo 제조 관리에서는 각 품목에 여러 개의 :abbr:`BoM (자재명세서)`를 연결할 수 있으므로 품목 세부사항도 자체 맞춤형 " +":abbr:`BoM (자재명세서)`를 가질 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:14 msgid "" "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the " "manufacturing process and save time." -msgstr "" +msgstr ":abbr:`BoM (자재명세서)`을 올바르게 설정하면 제조 공정을 최적화하고 시간을 절약할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 msgid "Set up a bill of materials (BoM)" @@ -17761,6 +17771,8 @@ msgid "" " or instructions, only components. In this case, the production is solely " "managed using *Manufacturing Orders*." msgstr "" +"가장 간단한 :abbr:`BoM (자재명세서)` 설정에는 작업이나 지침 없이 구성 요소만 포함됩니다. 이 경우 생산은 전적으로 *제조 " +"주문*을 사용하여 관리됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:23 msgid "" @@ -17769,12 +17781,16 @@ msgid "" "of Materials`. Then, click :guilabel:`Create`. Next, specify the " ":guilabel:`Product`." msgstr "" +":guilabel:`제조 관리` 모듈에서 :abbr:`BoM (자재명세서)`을 생성하려면 :menuselection:`품목 --> " +"자재명세서`로 이동합니다. 그런 다음 :guilabel:`생성`을 클릭합니다. 다음으로 :guilabel:`품목`을 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:28 msgid "" "A :abbr:`BoM (Bill of Materials)` can also be created directly from the " "product form, in which case the :guilabel:`Product` field is pre-filled." msgstr "" +"품목 양식에서 직접 :abbr:`BoM (자재명세서)`을 생성할 수도 있으며, 이 경우 :guilabel:`품목` 필드가 미리 채워져 " +"있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:31 msgid "" @@ -17799,13 +17815,14 @@ msgstr "자재명세서 설정." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 msgid "Specify a bill of materials (BoM) for a product variant" -msgstr "" +msgstr "품목 세부사항에 대한 자재 명세서 (BoM)를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:45 msgid "" ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product " "Variants*, with two setup options available to choose from." msgstr "" +":abbr:`BoM (자재명세서)`는 특정 *품목 세부사항*에도 할당할 수 있으며, 두 가지 설정 옵션 중에서 선택할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:49 msgid "" @@ -17813,6 +17830,7 @@ msgid "" "the product's variant attributes must already be configured on the product " "form." msgstr "" +"품목 세부사항에 :abbr:`BoM (자재명세서)`을 할당하려면 미리 품목 양식에 제품의 세부사항 속성이 구성되어 있어야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:52 msgid "" @@ -17823,6 +17841,10 @@ msgid "" "specify which variant each component applies to using the :guilabel:`Apply " "on Variants` column." msgstr "" +"첫 번째 방법은 세부사항 품목당 하나의 :abbr:`BoM (자재명세서)`을 새로 생성하고 :guilabel:`품목 세부사항`을 지정하여" +" 세부 품목당 하나의 :abbr:`BoM (자재명세서)`을 생성하는 것입니다. 두 번째 방법은 모든 부품을 포함하는 하나의 마스터 " +":abbr:`BoM (자재명세서)`을 생성하고 :guilabel:`세부선택사항 적용` 열을 사용하여 각 부품이 적용되는 세부사항 품목을 " +"지정하는 것입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 msgid "Product Variants in the Bill of Materials." @@ -17875,7 +17897,7 @@ msgstr "기존 작업 복사 기능." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 msgid "Add by-products to a bill of materials (BoM)" -msgstr "" +msgstr "자재명세서 (BoM)에 부산물 추가하기" #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 msgid "" @@ -17893,6 +17915,8 @@ msgid "" ":guilabel:`By-Products` feature in :menuselection:`Manufacturing --> " "Configuration --> Settings --> Operations`." msgstr "" +"부산물을 :abbr:`BoM (자재명세서)`에 추가하려면 먼저 :menuselection:`제조 관리 --> 설정 -->환경설정 --> " +"작업`에서 :guilabel:`부산물` 기능을 활성화합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:94 msgid "" @@ -17944,10 +17968,12 @@ msgid "" ":guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This " "tells Odoo the product can be manufactured." msgstr "" +"품목 페이지에서 :guilabel:`재고 관리` 탭으로 이동한 다음 :guilabel:`경로` 섹션에서 :guilabel:`제조` " +"확인란을 사용하도록 설정합니다. 이렇게 하면 Odoo에 제품을 제조할 수 있음을 알립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 msgid "The Manufacturing route on the Inventory tab of a product page." -msgstr "" +msgstr "품목 페이지의 재고 관리 탭에 있는 제조 경로입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:28 msgid "Configure a bill of materials (BoM)" @@ -17959,6 +17985,8 @@ msgid "" "manufactured. A |BOM| is a list of the components and operations required to" " manufacture a product." msgstr "" +"다음으로, Odoo가 품목 제조 방법을 알 수 있도록 품목에 대한 |BOM|을 구성해야 합니다. BOM은 제품을 제조하는 데 필요한 " +"부품과 작업의 목록입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:33 msgid "" @@ -17974,7 +18002,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 msgid "The Bill of Materials smart button on a product page." -msgstr "" +msgstr "품목 페이지의 자재 명세서 스마트 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:41 msgid "" @@ -17982,6 +18010,8 @@ msgid "" " In the :guilabel:`Quantity` field, specify the number of units that the BoM" " produces." msgstr "" +"|BOM|에서 :guilabel:`품목` 필드에 제품이 자동으로 채워집니다. :guilabel:`수량` 필드에 BoM이 생산하는 단위 " +"수를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:44 msgid "" @@ -17997,7 +18027,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 msgid "The Components tab on a bill of materials." -msgstr "" +msgstr "자재명세서의 부품 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:53 msgid "" @@ -18021,10 +18051,13 @@ msgid "" "Configuration --> Settings`, then enable the :guilabel:`Work Orders` " "checkbox." msgstr "" +":guilabel:`작업 주문` 설정이 활성화된 경우에만 :guilabel:`작업 주문` 탭이 표시됩니다. 이렇게 하려면 " +":menuselection:`제조 관리 --> 설정 --> 환경설정`으로 이동한 다음 :guilabel:`작업 주문` 확인란을 " +"선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 msgid "The Operations tab on a bill of materials." -msgstr "" +msgstr "자재명세서의 작업 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:70 msgid "" @@ -18059,6 +18092,7 @@ msgid "" "To use, manufacture, and sell kits, both the :guilabel:`Manufacturing` and " ":guilabel:`Inventory` apps need to be installed." msgstr "" +"키트를 사용, 제조 및 판매하려면 :guilabel:`제조 관리` 및 :guilabel:`재고 관리` 앱이 모두 설치되어 있어야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:14 msgid "Create the kit as a product" @@ -18068,13 +18102,15 @@ msgstr "키트를 제품으로 생성" msgid "" "To use a kit as a sellable product, or simply as a component organization " "tool, the kit should first be created as a product." -msgstr "" +msgstr "키트를 판매 가능한 제품으로 사용하거나 단순히 부품을 정리하는 도구로 사용하려면 먼저 키트를 상품으로 생성해야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:19 msgid "" "To create a kit product, go to :menuselection:`Inventory app --> Products " "--> Products`, and click :guilabel:`Create`." msgstr "" +"키트 제품을 생성하려면 :menuselection:`재고 관리 앱 --> 품목 --> 품목`으로 이동한 다음 :guilabel:`생성`을" +" 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22 msgid "" @@ -18116,6 +18152,8 @@ msgid "" ":menuselection:`Inventory app --> Products --> Products`. These components " "require no specific configuration." msgstr "" +"키트의 구성 요소도 :menuselection:`재고 관리 앱 --> 품목 --> 품목`을 통해 제품으로 설정해야 합니다. 이러한 구성 " +"요소는 특정 구성이 필요하지 않습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41 msgid "Set up the kit BoM" @@ -18125,7 +18163,7 @@ msgstr "자재명세서 키트 설정" msgid "" "After fully configuring the kit product and its components, a new :abbr:`BoM" " (bill of materials)` can be created for the kit product." -msgstr "" +msgstr "키트 제품 및 구성 요소를 완전히 구성한 후 키트 제품에 대한 새 :abbr:`BoM (자재명세서)`을 생성할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46 msgid "" @@ -18153,7 +18191,7 @@ msgstr "" msgid "" "Once ready, click :guilabel:`Save` to save the newly-created :abbr:`BoM " "(bill of materials)`." -msgstr "" +msgstr "준비가 완료되면 :guilabel:`저장`을 클릭하여 새로 생성된 :abbr:`BoM (자재명세서)`을 저장합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 msgid "Kit selection on the bill of materials." @@ -18229,7 +18267,7 @@ msgstr "준비가 완료되면 :guilabel:`저장`을 클릭하여 변경 사항 #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 msgid "Kit as a component in a multilevel bill of materials." -msgstr "" +msgstr "키트를 다중 단계 자재명세서의 구성 요소로 사용합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:95 msgid "Structure & cost" @@ -18247,7 +18285,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 msgid "Expanded kit in the Structure and Cost report." -msgstr "" +msgstr "구조 및 비용 보고서의 확장 키트." #: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:105 msgid "" @@ -18378,7 +18416,7 @@ msgstr "" msgid "" "The Create Backorder button on the \"You produced less than initial demand\"" " pop-up window." -msgstr "" +msgstr "\"초기 수요보다 적게 생산했습니다\" 팝업 창의 이월 주문 생성 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:54 msgid "" @@ -18415,7 +18453,7 @@ msgstr "태블릿 보기에서 이월 주문 생성" msgid "" "Backorders for manufacturing orders can also be created from the work order " "tablet view." -msgstr "" +msgstr "작업 주문 태블릿 보기에서 제조 주문에 대한 이월 주문을 생성할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:72 msgid "" @@ -18433,7 +18471,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:0 msgid "The Work Orders setting on the Manufacturing settings page." -msgstr "" +msgstr "제조 관리 설정 페이지의 작업지시서 설정입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82 msgid "" @@ -18459,13 +18497,13 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 msgid "The tablet view button for a work order on a manufacturing order." -msgstr "" +msgstr "제조 주문의 작업 주문에 대한 태블릿 보기 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:97 msgid "" "Once in tablet view, enter the quantity being manufactured immediately in " "the :guilabel:`Units` field at the top left of the tablet view." -msgstr "" +msgstr "태블릿 보기에서 왼쪽 상단에 있는 :guilabel:`단위` 필드에 제조 중인 수량을 직접 입력합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 msgid "The Units field in the tablet view." @@ -18497,7 +18535,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 msgid "" "The Mark As Done And Close MO button in the tablet view of a work order." -msgstr "" +msgstr "작업 주문의 태블릿 보기에서 완료로 표시하고 MO 닫기 버튼." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:118 msgid "" @@ -18551,7 +18589,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 msgid "The Record Production button on a work order." -msgstr "" +msgstr "작업 주문의 생산 기록 버튼." #: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:144 msgid "" @@ -18714,7 +18752,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:0 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:0 msgid "The Manufacture radio input field on a warehouse configuration page." -msgstr "" +msgstr "창고 구성 페이지의 제조 관리 라디오 입력 필드입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:31 #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:30 @@ -18828,7 +18866,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 msgid "The Start button for an operation on a manufacturing order." -msgstr "" +msgstr "제조 주문에 대한 작업 시작 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:74 #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:99 @@ -18843,7 +18881,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 msgid "The Done button for an operation on a manufacturing order." -msgstr "" +msgstr "제조 주문에 대한 작업의 완료 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:81 #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:106 @@ -18972,13 +19010,13 @@ msgstr "재고 관리 앱 설정에서 '품목 세부사항'을 선택합니다. #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 msgid "Create custom product attributes" -msgstr "" +msgstr "사용자 지정 제품 속성 생성" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:27 msgid "" "Once the product variants feature is activated, create and edit product " "attributes on the :guilabel:`Attributes` page." -msgstr "" +msgstr "품목 세부사항 기능이 활성화되면 :guilabel:`속성` 페이지에서 제품 속성을 생성하고 편집할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:30 msgid "" @@ -19028,17 +19066,17 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:0 msgid "Product variant attribute configuration screen." -msgstr "" +msgstr "품목 세부사항 속성 설정 화면." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:54 msgid "" "Once all desired :guilabel:`Values` have been added, click :guilabel:`Save` " "to save the new attribute." -msgstr "" +msgstr "원하는 :guilabel:`값`을 모두 추가했으면 :guilabel:`저장`을 클릭하여 새 속성을 저장합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:58 msgid "Add product variants on the product form" -msgstr "" +msgstr "품목 양식에 품목 세부사항 추가" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:60 msgid "" @@ -19072,11 +19110,11 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:72 msgid "Once finished, click :guilabel:`Save` to save changes." -msgstr "" +msgstr "완료되면 :guilabel:`저장`을 클릭하여 변경 사항을 저장합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 msgid "Product form variants tab with values and attributes." -msgstr "" +msgstr "값 및 속성이 있는 품목 세부사항 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:79 msgid "" @@ -19145,7 +19183,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 msgid "\"Apply on Variants\" option on the additional options menu." -msgstr "" +msgstr "추가 옵션 메뉴의 \"품목 세부사항에 적용\" 옵션을 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:110 msgid "" @@ -19188,7 +19226,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:129 msgid "Sell and manufacture variants of BoM products" -msgstr "" +msgstr "BoM 품목의 세부사항 품목 판매 및 제조" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:131 msgid "" @@ -19196,16 +19234,18 @@ msgid "" " to order, navigate to :menuselection:`Sales app --> Create` to create a new" " quotation." msgstr "" +"주문할 :abbr:`BoM (자재명세서)`의 세부사항 품목을 판매 및 제조하려면 :menuselection:`판매 앱 --> 생성`으로 " +"이동하여 새 견적을 생성합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:135 msgid "Sell variant of BoM product" -msgstr "" +msgstr "BoM 품목의 세부사항 품목 판매" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:137 msgid "" "Once on the blank :guilabel:`Quotation` form, click the drop-down next to " "the :guilabel:`Customer` field to add a customer." -msgstr "" +msgstr "빈 :guilabel:`견적` 양식에서 :guilabel:`고객` 필드 옆의 드롭다운을 클릭하여 고객을 추가합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:140 msgid "" @@ -19225,10 +19265,12 @@ msgid "" ":guilabel:`+` or :guilabel:`-` icons next to the `1` to change the quantity " "to sell and manufacture, if desired." msgstr "" +"팝업 창에서 원하는 속성 옵션을 클릭하여 제조할 제품의 올바른 이형 상품을 구성합니다. 그런 다음 `1` 옆의 녹색 " +":guilabel:`+` 또는 :guilabel:`-` 아이콘을 클릭하여 원하는 경우 판매 및 제조할 수량을 변경합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 msgid "Configure a product pop-up for choosing variant attributes." -msgstr "" +msgstr "품목 세부사항을 선택하기 위한 제품 팝업을 구성합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:152 msgid "" @@ -19237,10 +19279,12 @@ msgid "" "available optional products will appear, if they have been created " "previously." msgstr "" +"모든 사양을 선택했으면 :guilabel:`추가`를 클릭합니다. 그러면 팝업이 두 번째 :guilabel:`설정` 팝업으로 전환되어 " +"이전에 생성한 경우 사용 가능한 모든 옵션 제품을 표시합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:156 msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." -msgstr "" +msgstr "준비가 완료되면 :guilabel:`확인`을 클릭하여 팝업을 닫습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:158 msgid "" @@ -19248,10 +19292,12 @@ msgid "" ":guilabel:`Confirm` at the top of the :guilabel:`Quotation` form to create " "and confirm a new sales order (SO)." msgstr "" +"그런 다음 :guilabel:`저장`을 클릭하여 모든 변경 사항을 저장하고 :guilabel:`견적` 양식 상단의 " +":guilabel:`확인`을 클릭하여 새 판매주문서 (SO)를 생성 및 확인합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:162 msgid "Manufacture variant of BoM product" -msgstr "" +msgstr "BoM 품목의 세부사항 제조" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:164 msgid "" @@ -19260,6 +19306,8 @@ msgid "" "the :guilabel:`Manufacturing` smart button to open the " ":guilabel:`Manufacturing Order` form." msgstr "" +":abbr:`SO (판매주문서)`가 확인되면 :abbr:`SO (판매주문서)` 양식 상단에 :guilabel:`제조` 스마트 버튼이 " +"나타납니다. :guilabel:`제조` 스마트 버튼을 클릭하면 :guilabel:`제조 주문` 양식이 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:168 msgid "" @@ -19268,34 +19316,38 @@ msgid "" " different components will be listed. To see any mandatory or optional " ":guilabel:`Operation` steps, click the :guilabel:`Work Orders` tab." msgstr "" +"이 양식의 :guilabel:`부품` 탭에서 선택한 세부사항 품목의 관련 부품을 찾을 수 있습니다. 나열된 구성 요소는 선택한 품목 " +"세부사항에 따라 달라집니다. 필수 또는 선택 사항인 :guilabel:`작업` 단계를 보려면 :guilabel:`작업 주문` 탭으로 " +"이동합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:172 msgid "" "To enter the tablet view work order screen, click the :guilabel:`tablet " "icon` to the right of the row for the desired operation to be completed." msgstr "" +"태블릿 보기 작업 주문 화면으로 들어가려면 원하는 작업의 행 오른쪽에 있는 :guilabel:`태블릿 아이콘`을 클릭하여 완료합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:175 msgid "" "From the tablet view, click :guilabel:`Mark as Done` as the operation " "progresses to complete the operation steps." -msgstr "" +msgstr "태블릿 보기에서 작업이 진행되면 :guilabel:`완료로 표시`를 클릭하여 작업 단계를 완료합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:178 msgid "" "Alternatively, click the :guilabel:`Mark as Done` button at the top of the " "manufacturing order form to complete the order." -msgstr "" +msgstr "또는 제조 주문 양식 상단의 :guilabel:`완료로 표시` 버튼을 클릭하여 주문을 완료할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 msgid "Manufacturing order for variant of BoM product." -msgstr "" +msgstr "BoM 품목의 세부사항 품목에 대한 제조 주문." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:185 msgid "" "Then, navigate back to the :abbr:`SO (sales order)` via the breadcrumbs at " "the top of the page." -msgstr "" +msgstr "그런 다음 페이지 상단의 이동 경로를 사용하여 :abbr:`SO (판매주문서)`로 돌아옵니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:187 msgid "" @@ -19304,6 +19356,8 @@ msgid "" ":guilabel:`Delivery Order` form, click :guilabel:`Validate`, then click " ":guilabel:`Apply` to deliver the product." msgstr "" +"이제 제품이 제조되었으므로 :guilabel:`배송` 스마트 버튼을 클릭하여 고객에게 제품을 배송합니다. :guilabel:`배송 주문`" +" 양식에서 :guilabel:`승인`을 클릭한 다음 :guilabel:`적용`을 클릭하여 배송 프로세스를 완료합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:191 msgid "" @@ -19312,6 +19366,9 @@ msgid "" ":guilabel:`Create Invoice` followed by :guilabel:`Create Invoice` again to " "invoice the customer for the order." msgstr "" +"판매를 완료하려면 페이지 상단의 :guilabel:`사이트 이동 경로`를 통해 :abbr:`SO (판매주문서)`로 다시 돌아갑니다. 그런" +" 다음 :guilabel:`청구서 생성`을 클릭하고 :guilabel:`청구서 생성`을 다시 한번 클릭하여 고객에게 주문에 대한 청구서를" +" 발행합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:3 msgid "Scrap during manufacturing" @@ -19323,6 +19380,8 @@ msgid "" " or finished products may arise. This can be necessary if a component or " "product is damaged, or unusable for any other reason." msgstr "" +"제조 과정에서 제조 부품이나 완제품을 폐기해야 하는 경우가 발생할 수 있습니다. 이는 부품 또는 제품을 사용할 수 없게 만드는 손상, " +"결함 또는 기타 이유로 인해 발생할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:9 msgid "" @@ -19332,6 +19391,8 @@ msgid "" " a designation in Odoo that is used to track items that are no longer in " "physical inventory." msgstr "" +"기본적으로 부품 또는 완제품이 폐기되면 실제 재고에서 제거되어 *가상 위치/폐기물*이라는 가상 위치로 재배치됩니다. 가상 위치는 물리적 " +"공간을 나타내는 것이 아니라 실제 재고에서 제거된 품목을 추적하는 데 사용되는 Odoo 내의 공간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:14 msgid "" @@ -19340,6 +19401,8 @@ msgid "" " scrapped during a manufacturing order depends on the stage of the " "manufacturing process." msgstr "" +"Odoo *제조 관리*에서는 제조 주문 내에서 부품과 완제품을 모두 직접 폐기할 수 있습니다. 제조 주문 중 특정 유형의 품목을 폐기할 " +"수 있는 기능은 제조 공정 단계에 따라 다릅니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:23 msgid "" @@ -19349,6 +19412,9 @@ msgid "" "all virtual locations. From the list, select the :guilabel:`Virtual " "Locations/Scrap` location." msgstr "" +"폐기된 각 항목의 총 수량을 확인하려면 :menuselection:`재고관리 --> 환경설정 --> 위치`로 이동합니다. " +":guilabel:`검색...` 표시줄에서 :guilabel:`내부` 필터를 제거한 다음 :guilabel:`가상 위치/폐기` 위치를 " +"클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:29 msgid "Scrap manufacturing components" @@ -19362,6 +19428,9 @@ msgid "" " new manufacturing order is created, select a product from the " ":guilabel:`Product` drop-down menu, then click :guilabel:`Confirm`." msgstr "" +"제조 프로세스 중에 부품을 폐기하려면 먼저 :menuselection:`제조 관리 --> 제조 주문`으로 이동합니다. 그런 다음 기존 " +"제조 주문을 선택하거나 :guilabel:`생성`을 클릭하여 새 주문을 설정합니다. 새 주문을 생성하는 경우 :guilabel:`품목` " +"드롭다운 메뉴에서 제품을 선택한 다음 :guilabel:`확인`을 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:36 msgid "" @@ -19369,6 +19438,8 @@ msgid "" "appears at the top of the page. Click the button and a :guilabel:`Scrap` " "pop-up window appears." msgstr "" +"제조 주문이 확인되면 페이지 상단에 :guilabel:`폐기` 버튼이 표시됩니다. 이 버튼을 클릭하면 :guilabel:`폐기` 팝업 " +"창이 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 msgid "The scrap button on a manufacturing order." @@ -19381,6 +19452,8 @@ msgid "" " in the :guilabel:`Quantity` field. Finally, click :guilabel:`Done` to scrap" " the component." msgstr "" +":guilabel:`폐기` 팝업 창의 :guilabel:`품목` 드롭다운 메뉴에서 폐기할 부품을 선택합니다. :guilabel:`수량` " +"필드에 수량을 입력한 다음 :guilabel:`완료`를 클릭하여 부품을 폐기합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 msgid "The Scrap pop-up window." @@ -19393,6 +19466,8 @@ msgid "" "product itself. This is because Odoo recognizes that the finished product " "cannot be scrapped before it has been manufactured." msgstr "" +"제조 주문에서 :guilabel:`완료로 표시`를 클릭하기 전에는 완제품의 부품만 폐기할 수 있으며, 완제품 자체는 폐기할 수 " +"**없습니다**. 이는 Odoo가 제품이 완전히 제조되기 전에는 폐기할 수 없음을 인식하기 때문입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:56 msgid "" @@ -19401,6 +19476,8 @@ msgid "" "count for the component that was scrapped updates to reflect both the " "scrapped quantity and the quantity consumed during manufacturing." msgstr "" +"부품을 폐기한 후 폐기한 부품의 필요한 수량을 사용하여 제조 프로세스를 진행합니다. 폐기된 구성품의 재고 수량은 폐기된 수량과 제조 " +"과정에서 소비된 수량을 모두 반영하도록 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:61 msgid "" @@ -19409,6 +19486,8 @@ msgid "" "total quantity of table legs consumed will be six: four units used to " "manufacture the table plus two units scrapped." msgstr "" +"테이블을 제조하는 데 테이블 다리 4개가 필요하고 그 과정에서 테이블 다리 2개가 폐기되는 경우 소비된 테이블 다리의 총 수량은 6개가 " +"됩니다. 여기에는 테이블 제조에 사용된 4개의 유닛과 폐기된 2개의 유닛이 포함됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:66 msgid "Scrap components from tablet view" @@ -19420,10 +19499,12 @@ msgid "" "so, select the :guilabel:`Work Orders` tab on a manufacturing order, then " "click the :guilabel:`📱 (tablet view)` icon for a work order." msgstr "" +"제조 태블릿 보기에서 바로 구성품을 폐기할 수도 있습니다. 이렇게 하려면 제조 주문으로 이동하여 :guilabel:`작업 주문` 탭을 " +"선택합니다. 거기에서 특정 작업 주문에 대한 :guilabel:`📱 (태블릿 보기)` 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 msgid "The tablet view icon for a work order." -msgstr "" +msgstr "작업 주문의 태블릿 보기 아이콘입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:76 msgid "" @@ -19432,11 +19513,13 @@ msgid "" ":guilabel:`Menu` pop-up window. The :guilabel:`Scrap` pop-up window then " "appears." msgstr "" +"태블릿 보기에서 화면 왼쪽 상단에 있는 :guilabel:`☰(메뉴)` 버튼을 클릭합니다. 표시되는 :guilabel:`메뉴` 팝업 " +"창에서 :guilabel:`폐기` 옵션을 선택합니다. 그러면 :guilabel:`폐기` 팝업 창이 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 msgid "" "The Scrap button on the Menu pop-up window of the manufacturing tablet view." -msgstr "" +msgstr "제조 태블릿 보기의 메뉴 팝업 창에 있는 폐기 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:84 msgid "" @@ -19444,6 +19527,8 @@ msgid "" "enter the quantity being scrapped in the :guilabel:`Quantity` field. Click " ":guilabel:`Done` to scrap the component." msgstr "" +"마지막으로 :guilabel:`품목` 드롭다운 메뉴에서 폐기할 부품을 선택하고 :guilabel:`수량` 필드에 폐기할 수량을 " +"입력합니다. :guilabel:`완료`를 클릭하면 폐기 프로세스가 완료됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:88 msgid "Scrap finished products" @@ -19456,6 +19541,8 @@ msgid "" "click the :guilabel:`Scrap` button to make the :guilabel:`Scrap` pop-up " "window appear." msgstr "" +"Odoo에서는 주문이 완료되면 제조 주문에서 완제품을 폐기할 수도 있습니다. :guilabel:`완료로 표시`를 클릭한 후 " +":guilabel:`폐기` 버튼을 클릭하면 :guilabel:`폐기` 팝업 창이 나타납니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:94 msgid "" @@ -19465,13 +19552,16 @@ msgid "" "product and enter the quantity to be scrapped in the :guilabel:`Quantity` " "field. Click :guilabel:`Done` to scrap the finished product." msgstr "" +"완제품을 제작하기 위해 부품을 소비한 후에는 해당 부품이 더 이상 :guilabel:`품목` 드롭다운 메뉴에 표시되지 않습니다. 대신 " +"완제품이 옵션으로 사용됩니다. 완제품을 선택하고 :guilabel:`수량` 필드에 폐기할 수량을 입력합니다. 그런 다음 " +":guilabel:`완료`를 클릭하여 완제품에 대한 폐기 프로세스를 완료합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:99 msgid "" "The on-hand stock count for the product that was scrapped will update to " "reflect both the scrapped quantity and the quantity produced during " "manufacturing." -msgstr "" +msgstr "폐기된 제품의 재고 수량은 폐기된 수량과 제조 중에 생산된 수량을 모두 반영하도록 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:103 msgid "" @@ -19479,6 +19569,7 @@ msgid "" "after manufacturing was completed, then the on-hand inventory of the chair " "will increase by three: five units manufactured minus two units scrapped." msgstr "" +"의자 5개를 제조했지만 제조 완료 후 2개를 폐기한 경우, 의자의 보유 재고는 제조된 5개에서 폐기된 2개를 뺀 3개로 증가합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:3 msgid "Split and merge manufacturing orders" @@ -19492,6 +19583,9 @@ msgid "" "units into two or more orders, or to merge two or more orders into a single " "order." msgstr "" +"Odoo *제조 관리*에서는 품목의 단일 단위 또는 동일한 품목의 여러 단위에 대한 제조 주문을 생성할 수 있습니다. 경우에 따라 원래 " +"여러 단위에 대한 제조 주문을 두 개 이상의 개별 주문으로 분할해야 하는 경우가 발생할 수 있습니다. 반대로 두 개 이상의 주문을 하나의" +" 제조 주문으로 병합해야 할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:11 msgid "" @@ -19500,6 +19594,8 @@ msgid "" "a result, it is only possible to merge manufacturing orders when every order" " contains the same product being manufactured with the same BoM." msgstr "" +"제조 주문은 하나의 제품 단위 또는 동일한 제품의 여러 단위로 구성될 수 있으며, 모두 동일한 자재명세서 (BoM)를 사용합니다. 따라서" +" 제조 주문의 병합은 각 주문이 동일한 제품을 동일한 BoM으로 제조하는 경우에만 가능합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:17 msgid "Split manufacturing orders" @@ -19513,16 +19609,20 @@ msgid "" ":guilabel:`New` button, the manufacturing order's reference number appears " "with a :guilabel:`⚙️ (settings)` button next to it." msgstr "" +"제조 주문을 여러 주문으로 분할하려면 먼저 :menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동한 다음 제조 " +"주문을 선택합니다. 페이지 상단의 :guilabel:`신규` 버튼 옆에 제조 주문의 참조 번호와 함께 :guilabel:`⚙️ (설정)`" +" 버튼이 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:24 msgid "" "Click the :guilabel:`⚙️ (settings)` button to open the general settings for " "the manufacturing order, then select :guilabel:`Split`." msgstr "" +":guilabel:`⚙️ (설정)` 버튼을 클릭하여 제조 주문에 대한 일반 설정에 액세스한 다음 :guilabel:`분할`을 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 msgid "The Settings and Split buttons on a manufacturing order." -msgstr "" +msgstr "제조 주문의 설정 및 분할 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:31 msgid "" @@ -19542,7 +19642,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 msgid "The Split production pop-up window for a manufacturing order." -msgstr "" +msgstr "제조 주문에 대한 생산 분할 팝업 창입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:42 msgid "" @@ -19551,6 +19651,8 @@ msgid "" "field. The reference numbers for the new manufacturing orders are the " "reference number for the original order with *-###* tags added to the end." msgstr "" +":guilabel:`분할`을 선택하면 원래 제조 주문이 :guilabel:`분할 #` 필드에 표시된 지정된 주문 수로 분할됩니다. 새 " +"제조 주문의 참조 번호는 원래 주문의 참조 번호에서 파생되며, 끝에 *-###* 태그가 추가됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:48 msgid "" @@ -19558,6 +19660,8 @@ msgid "" "reference numbers for the new orders are *WH/MO/00012-001*, " "*WH/MO/00012-002*, and *WH/MO/00012-003*." msgstr "" +"제조 주문 *WH/MO/00012*는 세 개의 개별 주문으로 나뉩니다. 새 주문의 참조 번호는 *WH/MO/00012-001*, " +"*WH/MO/00012-002* 및 *WH/MO/00012-003*입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:52 msgid "Merge manufacturing orders" @@ -19570,12 +19674,14 @@ msgid "" " Orders`. Select the manufacturing orders that will be merged by activating " "the checkbox to the left of the name of each order." msgstr "" +"두 개 이상의 제조 주문을 하나의 주문으로 병합하려면 :menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 " +"이동합니다. 각 주문 이름 왼쪽에 있는 확인란을 활성화하여 병합할 제조 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 msgid "" "Select manufacturing orders that will be merged by clicking the checkbox for" " each." -msgstr "" +msgstr "각 확인란을 클릭하여 병합할 제조 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:62 msgid "" @@ -19583,10 +19689,12 @@ msgid "" ":guilabel:`Actions` button at the top of the page, then select " ":guilabel:`Merge` from the drop-down menu." msgstr "" +"모든 제조 주문을 선택했으면 페이지 상단의 :guilabel:`작업` 버튼을 클릭한 다음 드롭다운 메뉴에서 :guilabel:`병합`을 " +"선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 msgid "The Actions and Merge buttons on the Manufacturing Orders page." -msgstr "" +msgstr "제조 주문 페이지의 작업 및 병합 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:69 msgid "" @@ -19594,6 +19702,7 @@ msgid "" "reference number for the new manufacturing order is the next sequential " "number that has *not* already been assigned to an order." msgstr "" +"선택한 제조 주문이 하나의 단일 주문으로 병합됩니다. 이 새 제조 주문의 참조 번호는 주문에 아직 할당되지 않은 다음 일련 번호입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:73 msgid "" @@ -19602,13 +19711,16 @@ msgid "" " single order. The reference number for the manufacturing order created by " "the merger is *WH/MO/00013*." msgstr "" +"가장 최근에 제조 주문에 사용된 참조 번호는 *WH/MO/00012*입니다. 그 후 두 개의 제조 주문인 *WH/MO/00008* 및 " +"*WH/MO/00009*가 단일 주문으로 통합되었습니다. 이 병합의 결과로 새로 생성된 제조 주문의 참조 번호는 " +"*WH/MO/00013*입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:77 msgid "" "In the :guilabel:`Source` field for the manufacturing order created by the " "merger, the reference numbers of the manufacturing orders that were merged " "are listed." -msgstr "" +msgstr "병합으로 인해 생성된 제조 주문의 :guilabel:`원본` 필드에는 병합된 제조 주문의 참조 번호가 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:81 msgid "" @@ -19616,6 +19728,8 @@ msgid "" "*WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* " "and *WH/MO/00010*." msgstr "" +"제조 주문 *WH/MO/00009*와 *WH/MO/00010*이 병합되어 *WH/MO/00011*이 생성됩니다. WH/MO/00011*의" +" :guilabel:`원본` 필드에는 *WH/MO/00009*와 *WH/MO/00010*가 모두 나열됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 msgid "Manage semi-finished products" @@ -19631,6 +19745,9 @@ msgid "" "referred to as a *multilevel BoM*, where the main *top-level product* and " "its subassemblies are distinguished." msgstr "" +"*반제품*은 *하위 부품*이라고도 하며, 다른 제품의 자재명세서 (BoM)에서 구성품으로 사용되는 제조 제품입니다. 반제품은 복잡한 " +":abbr:`BoM (자재명세서)`을 단순화하거나 제조 공정을 더 잘 표현하기 위해 사용됩니다. 반제품이 포함된 :abbr:`BoM " +"(자재명세서)`을 *다중 단계 BoM*이라고 하며, 여기서 주요 *최상위 제품*과 그 하위 부품이 구분됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:12 msgid "Configure semi-finished products" @@ -19643,6 +19760,8 @@ msgid "" "step is to create the semi-finished products and their :abbr:`BoMs (Bills of" " Materials)`." msgstr "" +"다중 단계 :abbr:`BoM (자재명세서)`을 설정하려면 최상위 제품과 반제품을 모두 구성해야 합니다. 따라서 초기 단계에서는 반제품을" +" 각각의 :abbr:`BoM (자재명세서)`와 함께 생성하는 것이 포함됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:19 msgid ":doc:`bill_configuration`" @@ -19650,7 +19769,7 @@ msgstr ":doc:`bill_configuration`" #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 msgid "A bill of materials for a semi-finished product." -msgstr "" +msgstr "반제품에 대한 자재명세서입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:26 msgid "Create the top-level bill of materials (BoM)" @@ -19663,6 +19782,9 @@ msgid "" ":guilabel:`Create` the top-level product. Configure the product's " "specifications as desired, and be sure to :guilabel:`Save`." msgstr "" +"반제품이 완전히 구성되면 :menuselection:`제조 관리 --> 품목 --> 품목`으로 이동합니다. 그런 다음 " +":guilabel:`생성`을 클릭하여 최상위 제품을 선택합니다. 원하는 대로 제품의 사양을 구성한 후 :guilabel:`저장`을 " +"클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:32 msgid "" @@ -19672,12 +19794,15 @@ msgid "" "simply add the semi-finished products to this :abbr:`BoM (Bill of " "Materials)`, along with any other necessary components." msgstr "" +"최상위 제품을 설정한 후 제품 양식에서 :guilabel:`자재명세서` 스마트 버튼을 선택합니다. 다음으로 :guilabel:`생성`을 " +"선택하여 최상위 제품에 대한 :abbr:`BoM(자재명세서)`을 생성합니다. 여기에서 반제품을 이 :abbr:`BoM (자재명세서)`에 " +"추가하고 기타 필요한 부품을 추가합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 msgid "" "A bill of materials for a top-level product, containing a subassembly " "component." -msgstr "" +msgstr "하위 부품을 포함하는 최상위 품목에 대한 자재명세서입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:42 msgid "Manage production planning" @@ -19687,7 +19812,7 @@ msgstr "생산 계획 관리" msgid "" "There are several methods to manage manufacturing order automation for " "products with multilevel :abbr:`BoMs (Bills of Materials)`." -msgstr "" +msgstr "다중 단계로 구성된 제품의 제조 주문 자동화를 관리하는 방법에는 여러 가지가 있습니다 :abbr:`BoM (자재명세서)`." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:48 msgid "" @@ -19696,13 +19821,15 @@ msgid "" "components or bundle sellable products, using :doc:`Kits <kit_shipping>` is " "the more appropriate option." msgstr "" +"반제품은 특히 다중 단계 BoM으로 제조 가능한 제품을 처리하는 데 사용됩니다. 단순히 부품을 정리하거나 판매 가능한 제품을 번들로 묶기" +" 위해 BoM을 만드는 경우에는 :doc:`키트 <kit_shipping>`을 활용하는 것이 더 적합합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:52 msgid "" "To automatically trigger manufacturing orders for semi-finished products " "after confirming a manufacturing order for the main product, there are two " "options:" -msgstr "" +msgstr "주요 제품에 대한 제조 주문을 확인한 후 반제품에 대한 제조 주문을 자동으로 트리거하려면 두 가지 옵션이 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:55 msgid "" @@ -19710,6 +19837,7 @@ msgid "" "products and set both the minimum and maximum desired stock quantities to " "`0`." msgstr "" +"**옵션 1 (권장):** 반제품에 대한 *재주문 규칙*을 생성하고 최소 및 최대 희망 재고 수량을 모두 `0`으로 설정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:59 msgid ":doc:`../../purchase/products/reordering`" @@ -19721,6 +19849,8 @@ msgid "" ":guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the " "semi-finished product's product form." msgstr "" +"**옵션 2:** 반제품 품목 양식의 :guilabel:`재고` 탭 아래에서 :guilabel:`주문 시 보충 (MTO)` 및 " +":guilabel:`제조` 경로를 활성화합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:64 msgid "" @@ -19731,12 +19861,15 @@ msgid "" "finished and top-level products, exclusively reserving quantities for the " "confirmed top-level manufacturing order." msgstr "" +"옵션 1은 옵션 2에 비해 더 많은 유연성을 제공하므로 권장됩니다. 재주문 규칙은 수요와 보충을 직접 연결하지 않으므로 필요한 경우 " +"재고를 예약 해제하고 다른 주문으로 전환할 수 있습니다. 반면 주문 시 보충 (MTO) 경로는 반제품과 최상위 제품 사이에 고유한 링크를" +" 설정하여 확정된 최상위 제조 주문에 대해서만 수량을 예약합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:70 msgid "" "Regardless of the method chosen, semi-finished products must be fully " "manufactured before manufacturing can begin on the top-level product." -msgstr "" +msgstr "선택한 방법에 관계없이 반제품은 최상위 제품에서 제조를 시작하기 전에 완전히 제조되어야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 msgid "A manufacturing order for a top-level product." @@ -19750,15 +19883,15 @@ msgstr "제조 하청" msgid "" "Outsourcing a portion or all of your company’s manufacturing needs is not " "easy. To make it work correctly, you have to:" -msgstr "" +msgstr "회사 제조 요구 사항의 일부 또는 전부를 아웃소싱하는 것은 쉽지 않습니다. 제대로 작동하려면 다음과 같은 조건이 필요합니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:8 msgid "Manage the inventory of raw materials at your subcontractor" -msgstr "" +msgstr "하청업체의 원자재 재고 관리" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:9 msgid "Ship raw material to your subcontractors, at the right time" -msgstr "" +msgstr "원자재를 적시에 하청업체에 배송하세요." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:10 msgid "Control incoming goods quality" @@ -19772,24 +19905,26 @@ msgstr "하청업체 청구서 관리" msgid "" "Here is an example of subcontracting the manufacturing of “C”, which is " "produced out of raw materials “A” and “B”." -msgstr "" +msgstr "다음은 원재료 “A”와 “B”로 생산되는 “C”의 제조를 하도급하는 예시입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:20 msgid "" "With its MRP subcontracting feature, Odoo helps you handle this flow easily." -msgstr "" +msgstr "Odoo는 MRP 하도급 기능을 통해 이러한 작업을 쉽게 처리할 수 있도록 도와줍니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:25 msgid "" "To use the subcontracting feature, go to :menuselection:`Manufacturing --> " "Configuration --> Settings` and tick the box *Subcontracting*." msgstr "" +"하도급 기능을 사용하려면 :menuselection:`제조 관리 --> 설정 --> 환경설정`으로 이동하여 *하도급* 확인란을 " +"선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:32 msgid "" "To define if a product must be subcontracted, use a *Bill of Materials " "(BoM)* of type *Subcontracting*." -msgstr "" +msgstr "하도급을 위한 제품을 지정하려면 유형이 *하도급*으로 설정된 *자재명세서 (BoM)*를 사용합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:35 msgid "" @@ -19799,12 +19934,15 @@ msgid "" "might want to register all the components, even the ones that are sourced " "directly from the subcontractor." msgstr "" +"새 *BoM*을 생성하려면 :menuselection:`제조 관리 --> 품목 --> 자재명세서`로 이동하여 생성을 선택합니다. 그런 " +"다음 하청업체가 제품을 제조하는 데 필요한 부품을 나열합니다. 원가 계산을 위해 하청업체에서 직접 조달한 부품을 포함하여 모든 구성 " +"요소를 등록하는 것이 좋습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:41 msgid "" "Once you have set the *BoM Type* to *Subcontracting*, specify one or several" " subcontractors." -msgstr "" +msgstr "BoM 유형*을 *하청*으로 지정한 후 하나 이상의 하청업체를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:49 msgid "Basic Subcontracting Flow" @@ -19817,6 +19955,8 @@ msgid "" "new purchase order. Be sure to send the PO to a vendor that is defined as a " "subcontractor on the *BoM* of these products." msgstr "" +"하청업체에 필요한 제품 수량을 알려주려면 구매주문서 (PO)를 생성하여 하청업체에 발송하세요. 이렇게 하려면 *구매* 앱으로 이동하여 새" +" 구매주문서를 생성합니다. 해당 제품의 *BoM*에 하청업체로 지정된 공급업체로 PO가 전송되었는지 확인합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:60 msgid "" @@ -19824,22 +19964,24 @@ msgid "" "products are received, validate the receipt (2), with the actual quantity " "received. As a result, Odoo does the following things for you:" msgstr "" +"*PO*가 승인되면 (1) 보류 중인 입고 내역이 생성됩니다. 제품이 수령되면 실제 수령한 수량으로 입고 내역을 승인합니다 (2). " +"그러면 Odoo가 다음과 같은 작업을 수행합니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:64 msgid "" "Consumes the respective components at the subcontractor’s location, based on" " the *BoM* and your input (3);" -msgstr "" +msgstr "*BoM* 및 사용자 입력 (3)에 따라 하청업체의 위치에서 각 구성 요소를 소비합니다;" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:66 msgid "Produces the finished goods at the subcontractor’s location (4);" -msgstr "" +msgstr "하청업체의 위치에서 완제품을 생산합니다 (4);" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:68 msgid "" "Moves products from that subcontractor’s location to YourCompany via the " "validated receipt (5)." -msgstr "" +msgstr "확인된 입고 내역을 통해 해당 하청업체의 위치에서 귀사로 제품을 이동합니다 (5)." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:73 msgid "" @@ -19848,6 +19990,8 @@ msgid "" "subcontractor does not bill a fixed price per item, but rather the time and " "materials used." msgstr "" +"*PO*는 선택 사항입니다. 올바른 하청업체와 함께 입고를 수동으로 생성하는 경우에도 Odoo가 모든 작업을 수행합니다. 이는 하청업체가" +" 품목당 고정 가격을 청구하지 않고 사용한 시간과 자재를 청구하는 경우에 유용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:79 msgid "Inventory Valuation" @@ -19855,7 +19999,7 @@ msgstr "재고 자산 평가" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:81 msgid "The cost of the manufactured product “C” is defined as:" -msgstr "" +msgstr "제조 제품 “C”의 비용은 다음과 같이 정의됩니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:83 msgid "**C = A + B + s**" @@ -19867,11 +20011,11 @@ msgstr "동반 :" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:87 msgid "**A**: Cost of raw materials coming from YourCompany;" -msgstr "" +msgstr "**A**: 귀사에서 발생하는 원자재 비용;" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 msgid "**B**: Cost of raw materials sourced directly from the" -msgstr "" +msgstr "**B**: 직접 조달한 원자재 비용" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 msgid "subcontractor;" @@ -19888,6 +20032,8 @@ msgid "" "stock. This is managed by making the *Subcontracting Location* an *Internal " "Location*." msgstr "" +"원재료를 하청업체(**A**)로 보내도 해당 부품은 여전히 재고의 일부로 평가되므로 재고 평가에 영향을 미치지 않습니다. 이는 *하도급 " +"위치*를 *내부 위치*로 설정하여 관리합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:99 msgid "" @@ -19896,12 +20042,15 @@ msgid "" "product cost has to be: **A + B + s**, how much the product is valued in the" " accounting." msgstr "" +"그런 다음 제품 C 양식에 설정된 공급업체 가격은 부품 및 서비스 시간에 대해 하청업체에 지불해야 하는 금액이어야 합니다: **B + " +"s**. 제품 원가는 다음과 같아야 합니다: **A + B + s**, 즉 회계에서 제품의 가치를 평가하는 금액이 얼마인지 알아야 " +"합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:104 msgid "" "Finally, the subcontractor bill then matches the purchase order, with the " "proposed price coming from the finished products C." -msgstr "" +msgstr "마지막으로 하청업체 청구서는 완제품 C에서 제안된 가격을 반영하여 발주서와 일치하게 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:108 msgid "" @@ -19909,13 +20058,15 @@ msgid "" " location is not needed, simply include the cost of **B** in the " "subcontractor’s price **s** and remove the products *B* from the *BoM*." msgstr "" +"하청업에서 원자재 **B**의 보충을 관리할 필요가 없는 경우, **B**의 비용을 하청업체의 가격 **S**에 포함시키고 *B* 제품을" +" *BoM*에서 제외하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 msgid "" "In case the received products from the subcontractor contain tracked " "components, their serial or lot numbers need to be specified during the " "receipt." -msgstr "" +msgstr "하청업체로부터 수령한 제품에 추적된 부품이 포함되어 있는 경우, 수령 시 일련번호 또는 로트 번호를 지정해야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:120 msgid "" @@ -19924,12 +20075,14 @@ msgid "" "serial/lot numbers of the components. If the finished product is also " "tracked, its serial/lot number can be registered here too." msgstr "" +"이 경우 하청 제품을 수령하면 *부품 기록* 버튼이 나타납니다. 이 버튼을 클릭하면 대화 상자가 열리고 구성품의 일련/로트 번호가 " +"기록됩니다. 완제품도 추적되는 경우 일련/로트 번호도 여기에 등록할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:129 msgid "" "For audit purposes, it is possible to check the lot numbers recorded on a " "receipt by using the icon on the right of the finished products:" -msgstr "" +msgstr "감사 목적으로 완제품 오른쪽에 있는 아이콘을 사용하여 입고에 기록된 로트 번호를 확인할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:136 msgid "" @@ -19939,6 +20092,8 @@ msgid "" "or less component consumption at your subcontracting location, when " "receiving your final product." msgstr "" +"또한 추적되지 않는 제품에 대한 하청 BOM에서 유연한 소비를 선택한 경우 각 이동 라인에 '부품 기록' 옵션도 선택적으로 표시됩니다. " +"이를 통해 최종 제품을 수령할 때 하청 위치에서 더 많거나 적은 부품 소비를 등록할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:145 msgid "" @@ -19946,6 +20101,7 @@ msgid "" "either be executed by selecting the 'Set Quantities' Option or via the move " "line hamburger menus." msgstr "" +"보시다시피, 이러한 추적되지 않는 제품의 수령은 '수량 설정' 옵션을 선택하거나 이동 항목의 햄버거 메뉴를 사용하여 완료할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:149 msgid "Automate Replenishment of Subcontractors" @@ -19960,6 +20116,9 @@ msgid "" "trigger is the inital PO to the subcontractor, which creates a need at the " "subcontracting location, for raw material." msgstr "" +"최종 제품 구매 시 하청업체에 원자재 공급을 자동화하는 방법에는 두 가지가 있습니다. 선택하는 방법은 자재가 창고를 통과할지 여부에 따라" +" 달라집니다. 이 두 가지 방법은 모두 풀 스타일 메커니즘으로 간주되며, 하청업체에 대한 초기 구매 주문에 의해 트리거되어 하청업체에서 " +"원자재에 대한 수요를 생성합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:158 msgid "" @@ -19968,6 +20127,8 @@ msgid "" "shown below. If this is a component that you buy from a vendor, the buy " "route should also be activated." msgstr "" +"자체 창고에서 하청업체에 원자재를 공급하는 경우 아래와 같이 '주문 시 하청업체 재공급' 경로를 활성화해야 합니다. 공급업체에서 부품을 " +"구매하는 경우 구매 경로도 활성화해야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:169 msgid "" @@ -19988,7 +20149,7 @@ msgstr "" msgid "" "Note that the buy route is not selected in this case, as the dropship route " "is a buy route already." -msgstr "" +msgstr "이 경우에는 직배송 경로가 이미 구매 경로이므로 구매 경로가 선택되지 않습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:185 msgid "" @@ -19997,10 +20158,12 @@ msgid "" ":menuselection:`Inventory --> Configuration --> Settings --> Storage " "locations`." msgstr "" +"마지막으로, 하청 위치에서 이러한 원자재의 재고를 추적하려면 :menuselection:`재고 관리 --> 설정 --> 환경설정 --> " +"보관 위치`에서 *다중 위치*를 활성화해야 합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:189 msgid "From the location form, you are then able to access the Current Stock." -msgstr "" +msgstr "위치 양식에서 현재 재고에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:198 msgid "Manual Replenishment" @@ -20008,7 +20171,7 @@ msgstr "수동 보충" #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:200 msgid "You can also choose to replenish your subcontractors manually." -msgstr "" +msgstr "하청업체를 수동으로 보충하도록 선택할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:202 msgid "" @@ -20017,6 +20180,8 @@ msgid "" "*Inventory* Module, and create a picking, specifying to which subcontractor " "you are delivering to." msgstr "" +"원하는 시간에 하청업체에 부품을 보내려면 *재고 관리* 모듈에서 '하청업체 재공급' 작업 유형을 선택합니다. 피킹을 생성하고 납품할 " +"하청업체를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:210 msgid "" @@ -20024,6 +20189,7 @@ msgid "" "subcontractor by creating a dropship type PO, with your subcontractor set as" " the delivery address." msgstr "" +"또는 하청업체를 배송 주소로 설정한 직배송 유형 PO를 생성하여 공급업체에 하청업체의 재공급을 수동으로 요청할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:3 msgid "Three-step manufacturing" @@ -20037,6 +20203,8 @@ msgid "" "products transfer, and updates inventory counts based on the number of " "components removed, and finished products created." msgstr "" +"Odoo *제조 관리*를 통해 사용자는 1단계, 2단계 또는 3단계로 제품을 제조할 수 있습니다. 3단계 제조의 경우, Odoo는 부품 " +"이송, 제조 주문 (MO), 완제품 보관 이송을 생성합니다. 또한 사용된 부품과 생산된 완제품을 반영하여 재고 수량을 업데이트합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:41 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:42 @@ -20045,16 +20213,18 @@ msgid "" ":guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field " "auto-populates with the associated Bill of Materials (BoM)." msgstr "" +"새 |MO|에서 :guilabel:`품목` 드롭다운 메뉴를 열고 생산할 제품을 선택합니다. 그러면 :guilabel:`자재명세서` 필드가" +" 관련 자재명세서 (BoM)로 자동으로 채워집니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:53 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:54 msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." -msgstr "" +msgstr "마지막으로 :guilabel:`확인`을 클릭하여 |MO|를 확인합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:56 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:57 msgid "Process pick components transfer" -msgstr "" +msgstr "부품 피킹 전송 프로세스" #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:58 msgid "" @@ -20064,6 +20234,9 @@ msgid "" "*WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store " "finished products transfer)." msgstr "" +"3단계 |MO|를 확인하면 페이지 상단에 :guilabel:`이송` 스마트 버튼이 표시됩니다. 이 버튼을 클릭하면 |MO|에 대한 " +":guilabel:`이송` 페이지로 이동합니다. 이 페이지에는 두 개의 이송이 표시됩니다: *WH/PC/XXXXX* (부품 피킹 이송)와" +" *WH/SFP/XXXXX* (완제품 보관 이송)입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:63 msgid "" @@ -20072,6 +20245,8 @@ msgid "" "locations where they are stored to the location where they are used to " "manufacture the product." msgstr "" +":guilabel:`WH/PC/XXXXX`를 선택하여 |MO|에 대한 부품 피킹 이송을 엽니다. 이 이송은 부품이 보관된 위치에서 제품 " +"제조에 사용되는 위치로 부품의 이동을 추적하는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:67 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:64 @@ -20082,18 +20257,21 @@ msgid "" "appears. Doing so marks the transfer as :guilabel:`Done`, and updates " "inventory counts to reflect the quantity of components transferred." msgstr "" +"보관 위치에서 부품을 이동한 후에는 이송 상단에서 :guilabel:`승인`을 선택합니다. 그런 다음 이어지는 :guilabel:`즉시 " +"이송` 팝업 창에서 :guilabel:`적용`을 클릭합니다. 이 작업은 이송을 :guilabel:`완료`로 표시하고 제조를 위해 전송된 " +"부품의 수량을 반영하도록 재고 수량을 업데이트합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:72 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:69 msgid "" "Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` " "breadcrumb at the top of the page." -msgstr "" +msgstr "마지막으로 페이지 상단의 :guilabel:`WH/MO/XXXXX` 이동 경로를 클릭하여 |MO|로 돌아갑니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 msgid "The manufacturing order bread crumb on a pick components transfer." -msgstr "" +msgstr "부품 피킹 이송에 대한 제조 관리 사이트 이동 경로." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:88 msgid "" @@ -20101,14 +20279,16 @@ msgid "" ":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " "then select a manufacturing order." msgstr "" +"|MO| 자체에서 작업 주문을 완료하려면 먼저 :menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동한 다음 " +"제조 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 msgid "The Start button for a work order on a manufacturing order." -msgstr "" +msgstr "제조 주문에 대한 작업 주문의 시작 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 msgid "The Done button for an work order on a manufacturing order." -msgstr "" +msgstr "제조 주문의 작업 주문에 대한 완료 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:130 #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:126 @@ -20119,6 +20299,9 @@ msgid "" " to mark the |MO| as :guilabel:`Done`, and register the manufactured " "product(s) into inventory." msgstr "" +"|MO|의 마지막 작업 주문에 도달하면 태블릿 보기에 :guilabel:`완료로 표시하고 MO 닫기` 버튼과 함께 " +":guilabel:`완료로 표시` 버튼이 나타납니다. guilabel:`완료로 표시하고 MO 닫기`를 클릭하여 |MO|을 " +"guilabel:`완료`로 표시하고 제조된 제품을 재고에 기록합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:135 msgid "" @@ -20127,6 +20310,8 @@ msgid "" "closed at a later time by clicking the :guilabel:`Produce All` button on the" " |MO|." msgstr "" +"|MO|을 열어둔 상태에서 최종 작업 지시를 완료하려면 :guilabel:`완료로 표시`를 클릭할 수 있습니다. 이 시나리오에서는 나중에" +" 주문에서 :guilabel:`모두 생산` 버튼을 클릭하여 |MO|을 닫을 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:140 msgid "Process finished product transfer" @@ -20141,6 +20326,9 @@ msgid "" "from the location where they were manufactured to the location where they " "are stored." msgstr "" +"|MO|를 완료한 후 주문 상단의 :guilabel:`이송` 버튼을 클릭하여 주문의 :guilabel:`이송` 페이지로 돌아갑니다. " +"거기에서 :guilabel:`WH/SFP/XXXXX`를 선택하여 완제품 보관 이송에 액세스합니다. 이 이송은 제조 위치에서 보관 위치로 " +"완제품의 이동을 추적하는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:147 msgid "" @@ -20150,6 +20338,9 @@ msgid "" "appears. Doing so marks the transfer as :guilabel:`Done`, and updates " "inventory counts to reflect the quantity of finished products transferred." msgstr "" +"보관 위치에서 완제품을 이동한 후에는 이송 상단에서 :guilabel:`승인`을 선택합니다. 그런 다음 이어지는 :guilabel:`즉시" +" 이송` 팝업 창에서 :guilabel:`적용`을 클릭합니다. 이 작업은 이송을 :guilabel:`완료`로 표시하고 제조를 위해 전송된" +" 부품의 수량을 반영하도록 재고 수량을 업데이트합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:3 msgid "Two-step manufacturing" @@ -20164,6 +20355,9 @@ msgid "" "Inventory counts still update based on the number of products manufactured, " "but the act of transferring them to and from inventory is not tracked." msgstr "" +"Odoo *제조*를 사용하면 1단계, 2단계 또는 3단계를 사용하여 제품을 제조할 수 있습니다. 2단계 제조를 사용하는 경우 Odoo는 " +"제조 주문 (MO)과 부품 피킹 이송을 생성하지만 완제품을 재고로 이동하기 위한 이송은 생성하지 않습니다. 재고 수는 여전히 제조된 제품" +" 수에 따라 업데이트되지만 재고에서 재고로 이동하는 실제 추적은 기록되지 않습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:59 msgid "" @@ -20173,6 +20367,8 @@ msgid "" "components from the locations where they are stored to the location where " "they are used to manufacture the product." msgstr "" +"2단계 |MO|를 확인하면 페이지 상단에 :guilabel:`이송` 스마트 버튼이 표시됩니다. 이 버튼을 클릭하면 |MO|와 관련된 부품" +" 피킹 이송이 열립니다. 이 이송은 부품이 보관된 위치에서 제품 제조에 사용되는 위치로 부품의 이동을 추적하는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:88 msgid "" @@ -20182,14 +20378,17 @@ msgid "" "starts a timer that keeps track of how long the work order takes to " "complete." msgstr "" +"|MO| 페이지에서 :guilabel:`작업 지시` 탭을 선택합니다. 완료가 필요한 첫 번째 작업 주문에서 작업이 시작되면 해당 특정 " +"작업 주문에 대한 :guilabel:`시작` 버튼을 클릭합니다. 그러면 Odoo *제조*가 타이머를 시작하여 작업 지시를 완료하는 데 " +"걸리는 시간을 모니터링합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 msgid "The Start button for an work order on a manufacturing order." -msgstr "" +msgstr "제조 주문에 대한 작업 주문의 시작 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 msgid "The Done button for a work order on a manufacturing order." -msgstr "" +msgstr "제조 주문의 작업 주문에 대한 완료 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:109 msgid "" @@ -20197,6 +20396,8 @@ msgid "" "navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" " Orders`, and then select an |MO|." msgstr "" +"태블릿 보기를 사용하여 |MO|에 대한 작업 주문을 완료하려면 먼저 :menuselection:`제조 관리 --> 작업 --> 제조 " +"주문`으로 이동한 다음 |MO|를 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:112 msgid "" @@ -20204,6 +20405,8 @@ msgid "" " (tablet)` button on the line of the first work order to be processed. This " "opens the tablet view." msgstr "" +"다음으로 :guilabel:`작업 지시` 탭을 클릭한 다음 처리할 첫 번째 작업 지시 항목에서 :guilabel:`📱 (태블릿)` 버튼을" +" 선택합니다. 그러면 태블릿 보기가 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:131 msgid "" @@ -20212,6 +20415,8 @@ msgid "" "closed at a later time by clicking the :guilabel:`Produce All` button on the" " order." msgstr "" +"|제조 주문|을 열어둔 상태에서 최종 작업을 완료하려면 :guilabel:`완료로 표시`를 클릭할 수 있습니다. 이 경우 나중에 주문에서" +" :guilabel:`모두 생산` 버튼을 클릭하여 |제조 주문|을 닫을 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 msgid "Use the Master Production Schedule" @@ -20221,19 +20426,21 @@ msgstr "주 생산 계획 사용" msgid "" "The Master Production Schedule (MPS) is a valuable tool to plan your " "production based on your demand forecast." -msgstr "" +msgstr "마스터 생산 일정(MPS)은 수요 예측에 따라 생산을 계획하는 데 유용한 도구로 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 msgid "" "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` " "and activate the Master Production Schedule feature before hitting save." msgstr "" +":menuselection:`제조 관리 앱 --> 설정 --> 환경설정`으로 이동하여 마스터 생산 일정(MPS) 기능을 활성화한 다음 " +"변경 사항을 저장합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 msgid "" "In the MPS settings, you can define the time range of your MPS " "(month/week/day) and the number of periods you want to display at all times." -msgstr "" +msgstr "MPS 설정에서 시간 범위(월/주/일)와 연속으로 표시할 기간 수를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 msgid "" @@ -20242,6 +20449,8 @@ msgid "" " stock you want to have on hand at the end of the period) and the minimum " "and maximum quantities that must or can be replenished in each period." msgstr "" +":menuselection:`계획 --> 마스터 생산 일정`으로 이동한 다음 *제품 추가*를 선택합니다. 여기에서 안전 재고 목표 (기간" +" 종료 시 보유하려는 재고)와 각 기간에 보충할 최소 및 최대 수량을 설정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 msgid "" @@ -20268,6 +20477,8 @@ msgid "" "forecast for a finished product will impact the indirect demand for its " "components." msgstr "" +"다음 단계는 *예상 수요* 행에서 선택한 기간의 수요 예측을 진행하는 것입니다. 언제든지 이 예측 수요를 확정된 판매량을 포함한 실제 " +"수요와 비교할 수 있습니다. 완제품에 대한 예측 수요는 해당 부품에 대한 간접 수요에 영향을 미칩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 msgid "" @@ -20277,6 +20488,8 @@ msgid "" "manufacturing lead time) are then displayed in green. You can now launch the" " replenishment by clicking on the replenish button." msgstr "" +"예상 수요가 설정되면 시스템에서 다양한 기간 동안 보충할 수량을 자동으로 계산합니다. 리드 타임 (공급업체 리드 타임 또는 제조 리드 " +"타임)에 따라 제안된 보충 수량이 녹색으로 표시됩니다. 그런 다음 보충 버튼을 클릭하여 보충 프로세스를 시작할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 msgid "" @@ -20284,6 +20497,8 @@ msgid "" "requests for quotations or manufacturing orders will be created. You can " "easily access those by clicking on the *Actual Replenishment* cell." msgstr "" +"제품 구성 방식 (구매 대 제조)에 따라 견적 또는 제조 주문 요청이 생성됩니다. *실제 보충* 셀을 클릭하면 쉽게 액세스할 수 " +"있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 msgid "" @@ -20292,6 +20507,8 @@ msgid "" "back to the automatically computed value given by Odoo, simply click the " "cross." msgstr "" +"*권장 보충* 수량을 수동으로 수정하면 셀 왼쪽에 작은 엑스자 표시가 나타납니다. Odoo에자동으로 계산된 값으로 되돌리려면 엑스자를 " +"클릭하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 msgid "Cells color signification" @@ -20301,7 +20518,7 @@ msgstr "셀 색상 표시" msgid "" "The cells, which are part of the *Suggested Replenishment* line, can take " "different colors depending on the situation:" -msgstr "" +msgstr "*권장 보충* 항목 내의 셀은 상황에 따라 다양한 색상을 표시할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 msgid "" @@ -20309,30 +20526,32 @@ msgid "" "expected safety stock considering the demand forecast and the indirect " "demand forecast." msgstr "" +"**녹색**: 이 색상은 수요 예측과 간접 수요 예측을 고려하여 예상 안전 재고 수준을 달성하기 위해 보충해야 하는 제품 수량을 " +"나타냅니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 msgid "" "**Grey**: replenishment order has already been generated, and its quantity " "still matches current data." -msgstr "" +msgstr "**회색**: 보충 주문이 이미 생성되었으며 해당 수량은 여전히 현재 데이터와 일치합니다" #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 msgid "" "**Red**: replenishment order has already been generated, and its quantity " "was too high considering current data." -msgstr "" +msgstr "**빨간색**: 보충 주문이 이미 생성되었지만 현재 데이터를 고려할 때 수량이 너무 많습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 msgid "" "**Orange**: replenishment order has already been generated, and its quantity" " was too low considering current data." -msgstr "" +msgstr "**주황색**: 보충 주문이 이미 생성되었으며 현재 데이터를 고려할 때 수량이 너무 적습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 msgid "" "The *Forecasted stock* line can also contain red cells, which means the " "stock will be negative during the period in question." -msgstr "" +msgstr "*예상 재고* 라인에는 해당 기간 동안 재고가 마이너스가 될 것임을 나타내는 빨간색 셀도 포함될 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 msgid "What if I have underestimated the demand?" @@ -20344,6 +20563,7 @@ msgid "" "replenish. The cell will become orange, and you’ll be able to launch a new " "replenishment." msgstr "" +"여전히 수요 예측을 늘릴 수 있으며, 이는 보충할 수량에 영향을 미칩니다. 셀이 주황색으로 바뀌고 새 보충을 시작할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 msgid "What if I have overestimated the demand?" @@ -20355,16 +20575,18 @@ msgid "" " that you’ve ordered more than planned. If you’re still able to do it, you " "can cancel some RFQ or MO manually." msgstr "" +"수요 예측을 줄일 수 있습니다. 셀이 빨간색으로 표시되어 계획보다 더 많이 주문했음을 알려줍니다. 여전히 주문할 수 있는 경우 일부 " +"RFQ 또는 MO를 수동으로 취소할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 msgid "What if I wrongly added a product to the MPS?" -msgstr "" +msgstr "MPS에 제품을 잘못 추가한 경우에는 어떻게 하나요?" #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 msgid "" "You can easily remove a product from the MPS by clicking the small bin on " "the right of its name." -msgstr "" +msgstr "제품 이름 오른쪽에 있는 작은 휴지통을 클릭하면 MPS에서 제품을 쉽게 제거할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:3 msgid "Manage work orders using work centers" @@ -20380,6 +20602,9 @@ msgid "" ":guilabel:`Manufacturing` module by selecting :menuselection:`Operations -->" " Work Orders`." msgstr "" +"Odoo 제조 관리를 사용하면 지정된 작업 센터에서 작업 주문을 수행합니다. 제품에 대한 제조 주문을 생성하면 제품의 자재명세서 " +"(BoM)의 :guilabel:`작업` 탭에 나열된 모든 관련 작업 주문도 자동으로 생성되어 지정된 작업 센터에 할당됩니다. 이러한 " +"작업지시서를 관리하려면 :guilabel:`제조` 모듈로 이동하여 :menuselection:`작업 --> 작업 지시서`를 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 msgid "" @@ -20389,6 +20614,9 @@ msgid "" "to :guilabel:`Work Orders`. Work centers can then be created and managed by " "selecting :menuselection:`Configuration --> Work Centers`." msgstr "" +"작업센터를 사용하려면 먼저 :guilabel:`작업 지시` 기능을 활성화해야 합니다. 이렇게 하려면 :guilabel:`제조` 모듈로 " +"이동하여 :menuselection:`설정 --> 환경설정`을 선택한 다음 :guilabel:`작업 주문` 옆의 확인란을 활성화합니다. " +"그런 다음 :menuselection:`설정 --> 작업센터`를 선택하여 작업센터를 생성하고 관리할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 msgid "Create a work center" @@ -20400,37 +20628,39 @@ msgid "" ":menuselection:`Configuration --> Work Centers --> Create`. The work center " "form can then be filled out as follows:" msgstr "" +":guilabel:`제조` 모듈 내에서 :menuselection:`설정 --> 작업 센터 --> 생성`을 선택합니다. 그러면 다음과 " +"같이 작업 센터 양식을 작성할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 msgid "" ":guilabel:`Work Center Name`: give the work center a concise name that " "describes the type of operations it will be used for" -msgstr "" +msgstr ":guilabel:`작업장 이름`: 작업장에 사용할 작업 유형을 설명하는 간결한 이름을 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 msgid "" ":guilabel:`Alternative Workcenters`: specify an alternative work center for " "operations to be carried out at if the main work center is not available" -msgstr "" +msgstr ":guilabel:`대체 작업장`: 주 작업장을 사용할 수 없는 경우 작업을 수행할 대체 작업장을 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:26 msgid ":guilabel:`Code`: assign the work center a reference code" -msgstr "" +msgstr ":guilabel:`코드`: 작업장에 참조 코드를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:27 msgid "" ":guilabel:`Working Hours`: define the number of hours that the work center " "can be in use each week" -msgstr "" +msgstr ":guilabel:`근무 시간`: 작업장이 주당 운영되는 시간을 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:28 msgid "" ":guilabel:`Company`: select the company that the work center belongs to" -msgstr "" +msgstr ":guilabel:`회사`: 작업장이 속한 회사를 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "An example of a fully configured work center form." -msgstr "" +msgstr "완전히 구성된 작업장 양식의 예입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 msgid "Set standards for work center productivity" @@ -20440,7 +20670,7 @@ msgstr "작업장 생산성을 위한 표준 설정" msgid "" "The :guilabel:`General Information` tab on the work center form allows for " "productivity goals to be assigned to a work center:" -msgstr "" +msgstr "작업장 양식의 :guilabel:`일반 정보` 탭을 통해 작업장에 생산성 목표를 할당할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 msgid "" @@ -20449,43 +20679,45 @@ msgid "" "one hour and the efficiency is set to 200%, the work order will take 30 " "minutes" msgstr "" +":guilabel:`시간 효율성`: 작업장에서 작업 주문의 예상 소요 시간을 계산하는 데 사용됩니다. 예를 들어, 작업 주문이 일반적으로" +" 1시간이 걸리고 효율성이 200%로 설정된 경우 작업 주문은 30분이 걸립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 msgid "" ":guilabel:`Capacity`: the number of operations that can be performed at the " "work center simultaneously" -msgstr "" +msgstr ":guilabel:`생산 능력`: 작업장에서 동시에 수행할 수 있는 작업 수입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" -msgstr "" +msgstr ":guilabel:`설비종합효율 대상`: 작업장의 목표 설비종합효율을 설정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 msgid "" ":guilabel:`Time before prod.`: setup time required before work can commence" -msgstr "" +msgstr ":guilabel:`생산 전 시간.`: 생산을 시작하기 전에 필요한 설정 시간을 나타냅니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 msgid "" ":guilabel:`Time after prod.`: breakdown or cleanup time required after work " "is finished" -msgstr "" +msgstr ":guilabel:`생산 후 시간.`: 작업 완료 후 필요한 고장 또는 정리 시간" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 msgid "" ":guilabel:`Cost per hour`: the cost of operating the work center for one " "hour" -msgstr "" +msgstr ":guilabel:`시간당 비용`: 1시간 동안 작업장을 운영하는 데 드는 비용입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 msgid "" ":guilabel:`Analytic Account`: the account where the cost of the work center " "should be recorded" -msgstr "" +msgstr ":guilabel:`분석 계정`: 작업장의 비용을 기록하는 계정입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "The general information tab of the work center form." -msgstr "" +msgstr "작업장 양식의 일반 정보 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 msgid "Assign equipment to a work center" @@ -20497,48 +20729,51 @@ msgid "" "equipment to be assigned to a work center. The following information will be" " displayed for each piece of equipment added:" msgstr "" +":guilabel:`장비` 탭을 사용하여 특정 장비를 작업장에 할당할 수 있습니다. 추가된 각 장비에는 다음 정보가 표시됩니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" -msgstr "" +msgstr ":guilabel:`장비 이름`: 장비의 이름입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 msgid "" ":guilabel:`Technician`: the technician responsible for servicing the " "equipment" -msgstr "" +msgstr ":guilabel:`기술자`: 장비 서비스를 담당하는 기술자입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" -msgstr "" +msgstr ":guilabel:`장비 카테고리`: 장비가 속한 카테고리입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 msgid "" ":guilabel:`MTBF`: mean time between failures; the average time that the " "piece of equipment will operate before failing" -msgstr "" +msgstr ":guilabel:`MTBF`: 평균 고장 간격; 장비가 고장 나기 전까지 작동하는 평균 시간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 msgid "" ":guilabel:`MTTR`: mean time to recovery; the average time it takes for the " "equipment to become fully operational again" -msgstr "" +msgstr ":guilabel:`MTTR`: 평균 복구 시간; 장비가 다시 완전히 작동하는 데 걸리는 평균 시간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 msgid "" ":guilabel:`Est. Next Failure`: an estimate of when the next equipment " "failure will occur" -msgstr "" +msgstr ":guilabel:`예상 다음 장애`: 다음 장비 장애가 발생할 예상 시점입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "The equipment tab of the work center form." -msgstr "" +msgstr "작업장 양식의 장비 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 msgid "" ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are " "all calculated automatically based on past failure data, if any exists." msgstr "" +":guilabel:`MTBF`, :guilabel:`MTTR` 및 :guilabel:`예상 다음 장애`는 모두 과거 장애 데이터가 있는 " +"경우 이를 기반으로 자동으로 계산됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 msgid "Integrate IoT devices" @@ -20549,10 +20784,11 @@ msgid "" "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT " "(Internet of Things)` devices with a work center:" msgstr "" +":guilabel:`IoT 트리거` 탭을 사용하면 :abbr:`IoT (사물 인터넷)` 장치를 작업장과 쉽게 통합할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" -msgstr "" +msgstr ":guilabel:`장치`: 트리거할 IoT 장치를 지정합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 msgid ":guilabel:`Key`: the security key for the device" @@ -20564,7 +20800,7 @@ msgstr ":guilabel:`작업`: 트리거된 IoT 장치 동작" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "The IoT Triggers tab of the work center form." -msgstr "" +msgstr "작업장 양식의 IoT 트리거 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 msgid "Use case: configure an alternative work center" @@ -20577,6 +20813,8 @@ msgid "" "to specify an alternative work center where surplus work orders should be " "carried out." msgstr "" +"작업장이 정원을 초과하면 추가 작업 주문을 받을 수 없습니다. 이러한 경우 작업장이 사용 가능해질 때까지 기다리는 대신 대체 작업 센터를" +" 지정하여 잉여 작업 주문을 처리할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 msgid "" @@ -20586,6 +20824,8 @@ msgid "" "Navigate to the main work center and include the new work center in the " ":guilabel:`Alternative Workcenters` selection field." msgstr "" +"먼저 새 작업장을 생성합니다. 기본 작업장과 동일한 장비로 :guilabel:`장비` 탭을 구성하여 두 위치에서 유사한 작업을 수행할 수" +" 있도록 합니다. 그런 다음 기본 작업장으로 이동하여 새 작업장을 :guilabel:`대체 작업장` 선택 필드에 포함시킵니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 msgid "" @@ -20595,17 +20835,19 @@ msgid "" "manufacturing order, click the :guilabel:`Plan` button that appears at the " "top left of the form." msgstr "" +"이제 작업 중 하나에 주 작업장이 지정된 새 제조 주문을 생성합니다. 주 작업 센터는 :guilabel:`작업 주문` 탭에서 이 작업에 " +"대해 미리 선택되어 있습니다. 제조 주문이 확인되면 양식의 왼쪽 상단에서 :guilabel:`계획` 버튼을 찾아 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "" "Click the plan button to automatically select an available work center." -msgstr "" +msgstr "계획 버튼을 클릭하면 사용 가능한 작업장이 자동으로 선택됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 msgid "" "If the main work center is at capacity, the work center selected for the " "operation will be automatically changed to the alternative work center." -msgstr "" +msgstr "주 작업장의 수용 인원이 초과되면 작업에 지정된 작업장이 자동으로 대체 작업장으로 전환됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 msgid "The alternative work center is automatically selected." @@ -20622,28 +20864,30 @@ msgid "" "center. A variety of metrics showing work center performance can be viewed " "at the top right of the form:" msgstr "" +"개별 작업장의 성과를 보려면 :menuselection:`설정 --> 작업장`으로 이동한 다음 원하는 작업장을 클릭합니다. 양식의 오른쪽" +" 상단에 작업장의 성과를 나타내는 다양한 메트릭이 표시됩니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 msgid "" ":guilabel:`OEE`: overall effective efficiency, the percentage of time that " "the work center has been fully productive" -msgstr "" +msgstr ":guilabel:`OEE`: 작업장이 완전히 생산성을 발휘한 시간의 백분율을 나타내는 전체 장비 효율성입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" -msgstr "" +msgstr ":guilabel:`손실`: 작업 중단으로 인해 손실된 시간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 msgid "" ":guilabel:`Load`: the amount of time it will take to complete the current " "workload" -msgstr "" +msgstr ":guilabel:`로드`: 현재 작업량을 완료하는 데 걸리는 시간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 msgid "" ":guilabel:`Performance`: the real duration of work time, shown as a " "percentage of the expected duration" -msgstr "" +msgstr ":guilabel:`성과`: 예상 기간의 백분율로 표시되는 실제 작업 시간입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 msgid "Make work centers unavailable using Time Off" @@ -20656,6 +20900,8 @@ msgid "" "reason, work orders begin to pile up at the work center until it is " "operational again." msgstr "" +"Odoo에서는 지정된 위치에서 제조 작업을 실행하기 위해 *작업장*을 활용합니다. 그러나 어떤 이유로든 작업장을 사용할 수 없게 되면 " +"다시 운영될 때까지 작업장에 작업 주문이 쌓이기 시작합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 msgid "" @@ -20666,6 +20912,9 @@ msgid "" "manufacturing operations can continue until the impacted work center is " "available again." msgstr "" +"따라서 Odoo에서 작업장을 사용 불가로 표시하여 시스템에서 새 작업 주문을 대체 운영 작업장으로 리디렉션할 수 있도록 설정해야 합니다." +" Odoo *휴가* 앱을 활용하면 지정된 기간 동안 작업장을 사용할 수 없는 상태로 지정할 수 있습니다. 이렇게 하면 영향을 받는 " +"작업장이 다시 온라인 상태가 될 때까지 제조 작업을 원활하게 지속할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 msgid "" @@ -20675,6 +20924,8 @@ msgid "" " smart button to appear on each work center's :guilabel:`Working Hours` pop-" "up window." msgstr "" +"작업장을 사용 불가능으로 표시하기 전에 Odoo 플랫폼을 올바르게 구성해야 합니다. 먼저 :ref:`개발자 모드 <developer-" +"mode>`를 활성화하여 각 작업장의 :guilabel:`근무 시간` 팝업 창에서 :guilabel:`휴가` 스마트 버튼을 표시합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 msgid "" @@ -20682,6 +20933,8 @@ msgid "" "the bottom of the page, and clicking :guilabel:`Activate the developer mode`" " under the :guilabel:`Developer Tools` heading." msgstr "" +"개발자 모드를 활성화하려면 :menuselection:`설정`으로 이동하여 페이지 하단으로 스크롤한 다음 :guilabel:`개발자 " +"도구` 섹션 아래에서 :guilabel:`개발자 모드 활성화`를 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The \"Activate the developer mode\" button." @@ -20696,6 +20949,9 @@ msgid "" "should be the only one that appears on the page. Click the green " ":guilabel:`Install` button on the card to install the app." msgstr "" +"다음으로 *휴가* 앱을 설치합니다. 이 앱은 직원과 작업장을 포함한 Odoo 내의 모든 리소스에 타임오프를 할당하는 데 사용됩니다. " +":menuselection:`앱`으로 이동한 다음 :guilabel:`검색...` 표시줄에 `휴가`를 입력합니다. " +":guilabel:`휴가` 모듈의 카드가 나타나면, 카드의 녹색 :guilabel:`설치` 버튼을 클릭하여 앱을 설치합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The Time Off module installation card." @@ -20709,12 +20965,15 @@ msgid "" " no second work center is configured, Odoo cannot route work orders away " "from the unavailable work center and they will pile up in its queue." msgstr "" +"마지막 단계는 작업장을 올바르게 구성하는 것입니다. 이 워크플로우의 경우 사용 불가능하게 설정된 작업장과 다른 작업장이 수락할 수 없는 " +"작업 주문을 수신하는 두 번째 작업장까지 최소한 두 개 있어야 합니다. 두 번째 작업장이 구성되어 있지 않으면 Odoo는 사용 불가능한 " +"작업장으로부터 작업 주문을 라우팅할 수 없으며 해당 작업장의 대기열에 작업 주문이 쌓이게 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 msgid "" "To create a work center, navigate to :menuselection:`Manufacturing --> " "Configuration --> Work Centers --> Create`." -msgstr "" +msgstr "작업장을 만들려면 :menuselection:`제조 관리 --> 설정 --> 작업장 --> 생성`으로 이동합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 msgid "" @@ -20722,10 +20981,12 @@ msgid "" ":guilabel:`Equipment` tab. This ensures that operations carried out at one " "work center can also be performed at the other." msgstr "" +"두 작업장의 :guilabel:`장비` 탭에 동일한 장비가 나열되어 있는지 확인합니다. 이렇게 하면 한 작업장에서 수행한 작업을 다른 " +"작업장에서도 수행할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The equipment tab on a work center form." -msgstr "" +msgstr "작업장 양식의 장비 탭입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 msgid "" @@ -20734,10 +20995,12 @@ msgid "" "knows to send work orders to the second work center when the first is " "unavailable for any reason." msgstr "" +"사용할 수 없게 될 작업장의 경우, :guilabel:`대체 작업장` 드롭다운 메뉴에서 두 번째 작업장을 선택합니다. 이제 Odoo는 첫" +" 번째 작업장을 어떤 이유로든 사용할 수 없을 때 두 번째 작업장으로 작업 지시를 보내는 것을 알고 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "A work center form configured with an alternative work center." -msgstr "" +msgstr "대체 작업장으로 구성된 작업장 양식입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 msgid "Add time off for a work center" @@ -20752,10 +21015,13 @@ msgid "" ":guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` " "drop-down menu." msgstr "" +"설정이 완료되면 이제 사용할 수 없는 작업장에 대해 휴가를 예약할 수 있습니다. :menuselection:`제조 관리 --> 설정 " +"--> 작업장`으로 이동하여 해당 작업장을 선택합니다. :guilabel:`편집`을 클릭한 다음 :guilabel:`근무 시간` 드롭다운" +" 메뉴 옆에 있는 :guilabel:`↗ (외부 링크)` 버튼을 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The Working Hours \"External link\" button on the work center form." -msgstr "" +msgstr "작업장 양식의 근무 시간 '외부 링크' 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 msgid "" @@ -20765,10 +21031,13 @@ msgid "" ":guilabel:`Time Off` button in the top right of the pop-up. Click it to be " "taken to the :guilabel:`Resource Time Off` page." msgstr "" +":guilabel:근무 시간`이라는 팝업이 나타납니다. 여기에는 작업장의 표준 근무 시간과 기타 다양한 세부 정보가 나열됩니다. 개발자 " +"모드가 활성화되었으므로 팝업의 오른쪽 상단에 :guilabel:`휴가` 버튼이 있습니다. 이를 클릭하면 :guilabel:`자원 휴가` " +"페이지로 이동합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The Time Off button on the Working Hours pop-up." -msgstr "" +msgstr "근무 시간 팝업의 휴가 버튼입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 msgid "" @@ -20780,6 +21049,10 @@ msgid "" "unavailable. Click :guilabel:`Save` and the time off for the work center is " "logged in Odoo." msgstr "" +"이 페이지에서 :guilabel:`생성` 버튼을 클릭하여 새 휴가 항목을 설정합니다. 표시되는 양식에서 작업장의 폐쇄 " +":guilabel:`사유` (예: 유지보수 또는 수리)를 지정하고, 해당 작업장을 :guilabel:`자원`으로 선택한 다음 작업장을 " +"사용할 수 없는 기간의 :guilabel:`시작일`과 :guilabel:`종료일`을 정의합니다. 마지막으로 :guilabel:`저장`을 " +"클릭하면 작업장의 휴무가 Odoo에 기록됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The \"Resource Time Off\" form." @@ -20795,6 +21068,8 @@ msgid "" " to it can be automatically routed to an alternative work center using the " ":guilabel:`Plan` button." msgstr "" +"작업장의 지정된 휴가 기간이 시작되면 해당 작업장에 할당된 모든 새 작업지시는 :guilabel:`계획` 버튼을 사용하여 대체 작업장으로" +" 자동 라우팅할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 msgid "" @@ -20804,6 +21079,9 @@ msgid "" "unavailable work center for one of its operations. Click :guilabel:`Confirm`" " to confirm the work order." msgstr "" +"시작하려면 :menuselection:`작업 --> 제조 주문 --> 생성`으로 이동하여 새 제조 주문을 생성합니다. 제조 주문 양식에서" +" 사용 불가능으로 표시된 작업장의 작업을 포함하는 :guilabel:`품목`을 선택합니다. 완료되면 :guilabel:`확인`을 클릭하여" +" 작업 주문을 확인합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 msgid "" @@ -20812,6 +21090,8 @@ msgid "" "Center` column. There is also a green :guilabel:`Plan` button on the top " "left of the page." msgstr "" +"확인된 작업 주문에서 :guilabel:`작업 주문` 탭으로 이동합니다. 여기에서 사용 불가능으로 표시된 작업장이 기본적으로 " +":guilabel:`작업장` 열에 지정되어 있습니다. 페이지 왼쪽 상단에는 녹색 :guilabel:`계획` 버튼이 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "The Plan button on a manufacturing order." @@ -20822,12 +21102,13 @@ msgid "" "Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work " "Orders` tab is automatically changed to the alternative work center." msgstr "" +":guilabel:`계획` 버튼을 클릭하면 :guilabel:`작업 주문` 탭 아래에 나열된 작업장이 대체 작업장으로 자동 변경됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 msgid "" "The selected work center updates automatically after clicking the Plan " "button." -msgstr "" +msgstr "계획 버튼을 클릭하면 선택한 작업장이 자동으로 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 msgid "" @@ -20836,6 +21117,9 @@ msgid "" "the :guilabel:`Plan` button does not route work orders to an alternative " "work center unless the first one is at capacity." msgstr "" +"사용할 수 없는 작업장의 휴가 기간이 끝나면 Odoo는 해당 작업장을 다시 사용할 수 있음을 인식합니다. 이후에는 " +":guilabel:`계획` 버튼을 클릭해도 첫 번째 작업장의 정원이 가득 차 있지 않는 한 작업 주문이 대체 작업장으로 자동 라우팅되지 " +"않습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:3 msgid "Work order dependencies" @@ -20850,6 +21134,9 @@ msgid "" " of Materials (BoM) to be *blocked* by other operations that should occur " "first." msgstr "" +"특정 제품을 제조할 때 다른 작업을 시작하기 전에 특정 작업을 먼저 완료해야 하는 경우가 있습니다. 작업이 올바른 순서로 실행되도록 하기" +" 위해 Odoo *제조 관리*는 *작업 주문 종속성* 설정을 제공합니다. 이 기능을 활성화하면 자재명세서 (BoM)의 작업을 먼저 " +"수행해야 하는 다른 작업에 의해 *차단*할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:15 msgid "" @@ -20858,6 +21145,8 @@ msgid "" "--> Settings`. Then, enable the :guilabel:`Work Orders` setting, if it is " "not already active." msgstr "" +"*작업 주문 종속성* 설정은 기본적으로 활성화되어 있지 않습니다. 활성화하려면 먼저 :menuselection:`제조 관리 --> 설정 " +"--> 환경설정`으로 이동합니다. 그런 다음 :guilabel:`작업 주문` 설정을 활성화합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:19 msgid "" @@ -20865,6 +21154,8 @@ msgid "" "Order Dependencies` setting appears below it. Enable :guilabel:`Work Order " "Dependencies`, then click :guilabel:`Save` to confirm the changes." msgstr "" +":guilabel:`작업 주문` 설정을 활성화하면 그 아래에 :guilabel:`작업 주문 종속성` 설정이 표시됩니다. " +":guilabel:`작업 주문 종속성` 설정도 켠 다음 :guilabel:`저장`을 클릭하여 수정 사항을 확인합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:24 msgid "Add dependencies to BoM" @@ -20877,6 +21168,8 @@ msgid "" "Materials`, then select a |BOM|, or create a new one by clicking " ":guilabel:`New`." msgstr "" +"작업 주문 종속성은 제품의 |BOM|에 구성됩니다. 설정하려면 :menuselection:`제조 관리 --> 품목 --> 자재명세서`로 " +"이동한 다음 |BOM|을 선택하거나 :guilabel:`신규`를 클릭하여 새로 생성합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:32 msgid "" @@ -20884,6 +21177,8 @@ msgid "" "documentation on :ref:`creating a bill of materials " "<manufacturing/management/bill-configuration>`." msgstr "" +"새 |BOM|을 올바르게 구성하는 방법에 대한 자세한 가이드는 :ref:`자재명세서 생성 " +"<manufacturing/management/bill-configuration>`.`에 대한 문서를 참조하세요." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:35 msgid "" @@ -20892,10 +21187,12 @@ msgid "" ":guilabel:`Blocked By` option available in the settings of the " ":guilabel:`Operations` tab." msgstr "" +"|BOM|에서 :guilabel:`기타` 탭으로 이동한 다음 :guilabel:`작업 종속성` 확인란을 활성화합니다. 이렇게 하면 " +":guilabel:`작업` 탭의 설정에서 새로운 :guilabel:`차단 대상` 옵션을 사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "The Operation Dependencies checkbox on the Miscellaneous tab of a BoM." -msgstr "" +msgstr "BoM의 기타 탭에 있는 작업 종속성 확인란입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:43 msgid "" @@ -20904,10 +21201,13 @@ msgid "" ":guilabel:`Blocked By` checkbox. This makes a :guilabel:`Blocked By` field " "appear for each operation on the :guilabel:`Operations` tab." msgstr "" +"다음으로 :guilabel:`작업` 탭으로 이동합니다. 탭의 오른쪽 상단에서 :guilabel:`설정` 버튼을 클릭한 다음 " +":guilabel:`차단 기준` 확인란을 활성화합니다. 이렇게 하면 :guilabel:`작업` 탭의 각 작업에 대해 " +":guilabel:`차단 기준` 필드가 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "The settings for the Operations tab on a BoM." -msgstr "" +msgstr "BoM의 운영 탭에 대한 설정입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:51 msgid "" @@ -20917,14 +21217,17 @@ msgid "" "pop-up window, select the blocking operation that must be completed *before*" " the operation that is blocked." msgstr "" +"다른 작업에 의해 차단되어야 하는 작업에 해당하는 줄에서 :guilabel:`차단 대상` 필드를 클릭합니다. 이 작업을 수행하면 " +":guilabel:`열기: 작업` 팝업 창이 열립니다. 이 창의 드롭다운 메뉴에서 :guilabel:`차단 대상`을 선택합니다. 이는 " +"현재 구성 중인 작업을 진행하기 *전에* 선택한 작업을 완료해야 한다는 의미입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "The Blocked By drop-down field for an operation on a BoM." -msgstr "" +msgstr "차단 대상 드롭다운 필드에는 BoM에 대한 작업이 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:60 msgid "Finally, save the |BOM| by clicking :guilabel:`Save`." -msgstr "" +msgstr "마지막으로 :guilabel:`저장`을 클릭하여 |BOM|을 저장합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:63 msgid "Plan work orders using dependencies" @@ -20938,6 +21241,8 @@ msgid "" " by navigating to :menuselection:`Manufacturing --> Operations --> " "Manufacturing Orders`." msgstr "" +"작업 주문 종속성이 |BOM|에 설정되면, Odoo *제조 관리*는 이러한 종속성을 기반으로 작업 주문의 일정을 효과적으로 계획할 수 " +"있습니다. 제조 주문에 대한 작업 주문을 계획하려면 :menuselection:`제조 --> 작업 --> 제조 주문`으로 이동합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:70 msgid "" @@ -20947,6 +21252,9 @@ msgid "" "|BOM| configured with work order dependencies from the :guilabel:`Bill of " "Material` drop-down field, then click :guilabel:`Confirm`." msgstr "" +"다음으로, |BOM|에 작업 주문 종속성이 설정된 제품에 대한 제조 주문을 선택하거나 :guilabel:`신규`를 클릭하여 새 제조 " +"주문을 생성합니다. 새 제조 주문을 생성하는 경우 :guilabel:`자재 명세서` 드롭다운 필드에서 작업 주문 종속성으로 구성된 " +"|BOM|을 선택한 다음 :guilabel:`확인`을 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:75 msgid "" @@ -20955,6 +21263,8 @@ msgid "" "are *not* blocked by a different work order display a `Ready` tag in the " ":guilabel:`Status` section." msgstr "" +"제조 주문을 확인한 후 :guilabel:`작업 주문` 탭으로 이동하여 해당 주문을 처리하는 데 필요한 작업 주문을 확인합니다. 다른 " +"작업 주문에 의해 차단되지 *않는* 모든 작업 주문은 :guilabel:`상태` 섹션에 `준비` 태그가 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:79 msgid "" @@ -20962,10 +21272,12 @@ msgid "" "for another WO` tag instead. Once the blocking work order(s) are completed, " "the tag updates to `Ready`." msgstr "" +"하나 이상의 작업 주문에 의해 차단된 작업 주문은 대신 `다른 WO 대기 중` 태그가 표시됩니다. 차단된 작업 주문이 완료되면 태그가 " +"`준비`로 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "The status tags for work orders on a manufacturing order." -msgstr "" +msgstr "제조 주문의 작업 주문에 대한 상태 태그입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:86 msgid "" @@ -20977,11 +21289,14 @@ msgid "" "specified in the :guilabel:`Expected Duration` field of the work order that " "precedes it." msgstr "" +"제조 주문의 작업 주문을 예약하려면 페이지 상단의 :guilabel:`계획` 버튼을 클릭합니다. 이 작업은 예약된 시작 날짜와 시간으로 " +":guilabel:`작업 주문` 탭의 각 작업 주문에 대한 :guilabel:`예약된 시작 날짜` 필드를 채웁니다. 작업 주문이 차단된 " +"경우에는 이전 작업 주문의 :guilabel:`예상 기간` 필드에 지정된 기간 이후에 시작하도록 예약됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "" "The Scheduled Start Date field for work orders on a manufacturing order." -msgstr "" +msgstr "제조 주문의 작업 주문에 대한 예약된 시작 날짜 필드입니다" #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:97 msgid "" @@ -20989,6 +21304,8 @@ msgid "" "two operations: Cut and Assemble. Each operation has an expected duration of" " 60 minutes, and the Assemble operation is blocked by the Cut operation." msgstr "" +"제품 A에 대해 두 가지 작업이 포함된 제조 주문이 생성됩니다: 절단 및 조립. 두 작업 모두 각각 60분이 소요될 것으로 예상되며, " +"조립 작업은 절단 작업의 완료 여부에 따라 차단됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:101 msgid "" @@ -20997,6 +21314,8 @@ msgid "" "operation has an expected duration of 60 minutes, the Assemble operation is " "scheduled to begin at 2:30 pm." msgstr "" +"오후 1시 30분에 제조 주문에 대한 :guilabel:`계획` 버튼을 클릭하면 절단 작업이 바로 시작되도록 예약되어 있습니다. 절단 " +"작업의 예상 소요 시간은 60분이므로 조립 작업은 오후 2시 30분에 시작되도록 예약되어 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:106 msgid "Planning by workcenter" @@ -21009,6 +21328,8 @@ msgid "" ":menuselection:`Manufacturing --> Planning --> Planning by Workcenter`. This" " page shows a timeline of all the work orders scheduled for each operation." msgstr "" +"작업 주문 계획을 시각화하려면 :guilabel:`제조 관리 --> 계획 --> 작업장별 계획`에 있는 :guilabel:`작업 주문 " +"계획` 페이지로 이동합니다. 여기에는 각 작업에 대해 예약된 모든 작업 주문의 타임라인이 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:112 msgid "" @@ -21017,11 +21338,13 @@ msgid "" " it. In addition, an arrow connects the two work orders, leading from the " "blocking operation to the blocked operation." msgstr "" +"한 작업 주문이 다른 작업 주문의 완료로 인해 차단된 경우, 차단된 작업 오더는 이를 차단하는 작업 오더 다음에 시작하도록 예약된 것으로" +" 표시됩니다. 또한 화살표가 두 작업 주문을 연결하여 차단 작업에서 차단된 작업으로의 종속성을 나타냅니다." #: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 msgid "" "The arrow connecting a blocked work order to the work order blocking it." -msgstr "" +msgstr "차단된 작업 주문과 이를 차단하는 작업 주문을 연결하는 화살표입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 msgid "Shop Floor" @@ -21038,6 +21361,8 @@ msgid "" " (MOs) and work orders. It also allows manufacturing employees to track the " "amount of time spent working on manufacturing and work orders." msgstr "" +"*작업 현장* 모듈은 *제조 관리* 앱의 동반 모듈입니다. *작업 현장*은 제조 주문(MO) 및 작업 지시서를 관리할 수 있는 시각적 " +"인터페이스를 제공하여 제조 담당자가 이러한 작업에 소요된 시간을 추적할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:13 msgid "" @@ -21047,12 +21372,16 @@ msgid "" ":guilabel:`Search...` bar, and then click :guilabel:`Install` on the " ":guilabel:`Manufacturing` app card." msgstr "" +"*작업 현장* 모듈은 *제조 관리* 앱과 함께 설치됩니다. 단독으로는 설치할 수 없습니다. *제조 관리* 앱을 설치하려면 " +":menuselection:`앱`으로 이동하여 :guilabel:`검색...`바에서 `제조`를 검색한 다음 :guilabel:`제조 " +"관리` 앱 카드에서 :guilabel:`설치`를 클릭합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:19 msgid "" "The *Shop Floor* module replaces the tablet view functionality of the " "*Manufacturing* app, and is only available in Odoo versions 16.4 and later." msgstr "" +"*작업 현장* 모듈은 *제조 관리* 앱의 태블릿 보기 기능을 대체하며, Odoo 16.4 버전 이상에서만 사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:22 msgid "" @@ -21060,12 +21389,15 @@ msgid "" ":menuselection:`Settings` and scroll down to the :guilabel:`About` section " "at the bottom of the page. The version number is displayed there." msgstr "" +"Odoo 데이터베이스의 버전 번호를 확인하려면 :menuselection:`설정`으로 이동한 다음 페이지 하단의 " +":guilabel:`정보` 섹션까지 아래로 스크롤합니다. 여기에 버전 번호가 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:26 msgid "" "To switch to a newer version of Odoo, see the documentation on " ":ref:`upgrading a database <administration/upgrade>`." msgstr "" +"최신 버전의 Odoo로 전환하려면 :ref:`데이터베이스 <administration/upgrade>`에 대한 문서를 참조하세요." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:30 msgid "Navigation" @@ -21075,13 +21407,13 @@ msgstr "탐색" msgid "" "*Shop Floor* is broken down into three main views, which can be selected " "from the navigation bar at the top of the module:" -msgstr "" +msgstr "*작업 현장*은 모듈 상단의 탐색 모음에서 선택할 수 있는 세 가지 기본 보기로 분류됩니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:35 msgid "" "The :guilabel:`All` page serves as the main dashboard for the module, and " "displays information cards for |MOs|." -msgstr "" +msgstr ":guilabel:`전체` 페이지는 모듈의 기본 대시보드 역할을 하며 |MO|에 대한 정보 카드를 표시합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:37 msgid "" @@ -21091,6 +21423,9 @@ msgid "" "navigation bar, selecting or deselecting them on the pop-up window that " "appears, and then clicking :guilabel:`Confirm`." msgstr "" +"각 작업장의 전용 페이지에는 해당 작업장에 배정된 작업 주문에 대한 정보 카드가 표시됩니다. 이러한 페이지는 탐색 표시줄에서 " +":guilabel:`+(더하기)` 버튼을 클릭하고 표시되는 팝업 창에서 선택하거나 선택 취소한 다음 :guilabel:`확인`을 클릭하여" +" 켜거나 끌 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:41 msgid "" @@ -21100,6 +21435,8 @@ msgid "" " the active employee, this page functions the same as the pages for each " "work center." msgstr "" +":guilabel:`내` 페이지에는 모듈 왼쪽의 조작자 패널에서 현재 프로필이 활성화되어 있는 직원에게 할당된 모든 작업 주문에 대한 " +"정보 카드가 표시됩니다. 이 페이지는 각 작업장의 페이지와 마찬가지로 활성 직원의 작업에 맞는 세부정보와 기능을 제공합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:47 msgid "" @@ -21108,6 +21445,8 @@ msgid "" "the top of the module. This search filter remains active while switching " "between the different module views." msgstr "" +"다른 주문이 표시되지 않도록 |MO| 또는 작업 주문을 분리하려면 모듈 상단의 :guilabel:`검색...` 표시줄에서 |MO|의 참조" +" 번호를 입력하기만 하면 됩니다. 이 검색 필터는 모듈 내의 다른 보기 사이를 이동할 때에도 계속 적용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:51 msgid "" @@ -21117,12 +21456,15 @@ msgid "" " which view is selected. It can be toggled on or off by clicking the " ":guilabel:`sidebar` button at the extreme left of the navigation bar." msgstr "" +"모듈 왼쪽에는 운영자 패널이 있습니다. 이 패널에는 현재 *작업 현장*에 로그인한 모든 직원이 표시되며, 신규 직원도 로그인할 수 " +"있습니다. 운영자 패널은 현재 사용 중인 보기에 관계없이 모듈 전체에서 계속 액세스할 수 있습니다. 탐색 모음 맨 왼쪽에 있는 " +":guilabel:`사이드바` 버튼을 클릭하여 운영자 패널을 표시하거나 숨길 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 msgid "" "The \"sidebar\" button, which is used to toggle the operator panel on or " "off." -msgstr "" +msgstr "\"사이드바\" 버튼은 운영자 패널을 켜거나 끄는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:61 msgid "All page" @@ -21134,6 +21476,8 @@ msgid "" "|MO| that is *ready to start*. An |MO| is considered ready to start once it " "has been confirmed, and all required components are available." msgstr "" +"기본적으로 :guilabel:`전체` 페이지에는 *시작할 준비*가 된 모든 |MO|에 대한 정보 카드가 표시됩니다. |MO|가 확인되면 " +"준비 완료로 분류되며 필요한 모든 부품에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:67 msgid "" @@ -21141,6 +21485,8 @@ msgid "" ":guilabel:`x` button on the :guilabel:`Ready to Start` filter to remove it " "from the :guilabel:`Search...` bar." msgstr "" +"준비 상태와 관계없이 확인된 모든 |MO|를 보려면 :guilabel:`검색...` 표시줄에서 :guilabel:`시작 준비` 필터 옆의" +" :guilabel:`x` 버튼을 클릭하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:71 msgid "MO information card" @@ -21152,6 +21498,8 @@ msgid "" "relevant details of the associated |MO|, and also provides employees with " "options for processing the |MO|." msgstr "" +":guilabel:`전체` 페이지의 |MO|에 대한 정보 카드에는 관련 |MO|의 모든 관련 세부 정보가 표시되며 직원에게 |MO|를 " +"처리하기 위한 다양한 옵션이 제공됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:76 msgid "" @@ -21162,6 +21510,9 @@ msgid "" " an |MO| have been completed and the |MO| is ready to close, the status " "updates to :guilabel:`To Close`." msgstr "" +"|MO| 카드의 헤더에는 |MO| 번호, 생산 중인 제품 및 수량, |MO|의 상태가 표시됩니다. 아직 |MO| 작업이 시작되지 않은 " +"경우 상태는 :guilabel:`확정`으로 표시됩니다. 작업이 진행되면 상태는 :guilabel:`진행 중`으로 변경됩니다. |MO|와 " +"관련된 모든 작업 지시가 완료되고 |MO|를 종료할 준비가 되었다면 상태는 :guilabel:`종료 예정`으로 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:82 msgid "" @@ -21171,6 +21522,9 @@ msgid "" "title of the work order. The current work order is indicated by a button " "that opens the page for the work center to which the order is assigned." msgstr "" +"|MO| 카드의 메인 섹션에는 완료된 각 작업 주문에 대한 항목이 표시되고, 아직 완료되지 않은 현재 작업 주문이 그 뒤에 표시됩니다. " +"완료된 작업 주문은 작업 주문 제목 오른쪽에 녹색 확인 표시가 되어 있습니다. 현재 작업 주문은 사용자가 할당된 작업장의 페이지를 열 수" +" 있는 버튼으로 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:87 msgid "" @@ -21180,6 +21534,9 @@ msgid "" ":guilabel:`Register Production` line, enter a value in the :guilabel:`Units`" " field of the resulting pop-up window, then click :guilabel:`Validate`." msgstr "" +"현재 작업 주문 아래에는 생산된 제품 단위 수를 기록하는 데 사용되는 :guilabel:`생산 등록`이라는 제목의 섹션이 있습니다. 생산" +" 단위 수를 수동으로 입력하려면 :guilabel:`생산 등록` 항목을 클릭하고 이어지는 팝업 창 내의 :guilabel:`단위` 필드에" +" 원하는 값을 입력한 다음 :guilabel:`승인`을 클릭하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:92 msgid "" @@ -21189,6 +21546,8 @@ msgid "" "10 units of a dining table, clicking the :guilabel:`10 units` button records" " that 10 units were produced." msgstr "" +"줄 오른쪽에 있는 :guilabel:`#단위` 버튼을 클릭하면 |MO|가 처음에 생성된 단위 수를 생산된 단위 수로 자동 등록합니다. " +"예를 들어 식탁 10개를 위해 |MO|가 생성된 경우 :guilabel:`10개` 버튼을 클릭하면 10개가 생산된 것으로 기록됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:97 msgid "" @@ -21199,6 +21558,9 @@ msgid "" "Clicking :guilabel:`Quality Checks` opens a pop-up window, from which any " "required quality checks can be completed." msgstr "" +"|MO| 카드 하단에는 :guilabel:`생산 마감` 버튼이 있습니다. 이 버튼은 제작이 완료되면 |MO|를 마무리하고 닫는 데 " +"사용됩니다. 그러나 개별 작업 지시뿐만 아니라 전체 |MO|에 대한 전반적인 품질 검사가 필요한 경우, :guilabel:`품질 검사` " +"버튼이 대신 표시됩니다. :guilabel:`품질 검사`를 클릭하면 필요한 품질 검사를 완료할 수 있는 팝업 창이 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:103 msgid "" @@ -21207,41 +21569,46 @@ msgid "" ":guilabel:`Undo` causes the |MO| to remain open. Once the |MO| card " "disappears completely, the work order is closed." msgstr "" +":guilabel:`생산 마감`을 클릭하면 |MO| 카드가 사라지기 시작하고 하단에 :guilabel:`실행 취소` 버튼이 나타납니다. " +":guilabel:`실행 취소`를 클릭하면 |MO|가 계속 열려 있습니다. |MO| 카드가 완전히 사라지면 작업 주문이 성공적으로 " +"종료됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:107 msgid "" "On the right side of the footer is an :guilabel:`⋮ (options)` button, which " "opens a pop-up window with additional options for the |MO|:" msgstr "" +"하단 오른쪽에는 :guilabel:`⋮ (옵션)` 버튼이 있습니다. 이 버튼을 클릭하면 |MO|에 대한 추가 옵션이 있는 팝업 창이 " +"열립니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:110 #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:171 msgid "" ":guilabel:`Scrap` is used to send components to a scrap location when they " "are found to be defective." -msgstr "" +msgstr ":guilabel:`폐기`는 결함이 발견되면 부품을 폐기 위치로 보내는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:112 msgid "" ":guilabel:`Add Work Order` is used to add an additional work order to the " "|MO|." -msgstr "" +msgstr ":guilabel:`작업 지시 추가`는 |MO|에 작업 지시를 추가하는 데 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:113 #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:173 msgid "" ":guilabel:`Add Component` is used to add an additional component to the " "|MO|." -msgstr "" +msgstr ":guilabel:`부품 추가`는 |MO|에 추가 부품을 포함할 때 사용됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:114 msgid ":guilabel:`Open Backend MO` opens the |MO| in the Manufacturing app." -msgstr "" +msgstr ":guilabel:`백엔드 제조 주문 열기`는 제조 앱에서 |MO|를 엽니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 msgid "" "An information card for an MO on the \"All\" page of the Shop Floor module." -msgstr "" +msgstr "작업 현장 모듈의 \"전체\" 페이지에 있는 MO에 대한 정보 카드입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:121 msgid "Work center pages" @@ -21254,6 +21621,8 @@ msgid "" "considered ready to start once the |MO| it is a part of is ready to start, " "and any preceding work orders have been completed." msgstr "" +"작업장 페이지에는 기본적으로 *시작 준비* 완료로 간주되는 각 작업 주문에 할당된 정보 카드가 표시됩니다. 작업 주문은 관련된 |MO|가" +" 시작할 준비가 되고 모든 선행 작업 주문이 완료되면 준비된 것으로 간주됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:127 msgid "" @@ -21261,6 +21630,8 @@ msgid "" "readiness, click the :guilabel:`x` button on the :guilabel:`Ready to Start` " "filter to remove it from the :guilabel:`Search...` bar." msgstr "" +"준비 상태에 관계없이 작업장에 할당된 모든 확인된 작업 주문을 보려면 :guilabel:`검색...` 표시줄에서 :guilabel:`시작" +" 준비` 필터 옆의 :guilabel:`x` 버튼을 클릭하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:132 msgid "Work order information card" @@ -21272,6 +21643,8 @@ msgid "" "relevant details of the associated work order, and also provides employees " "with options for processing the work order." msgstr "" +"작업장 페이지에 표시되는 작업 주문 정보 카드에는 연결된 작업 주문의 모든 관련 세부 정보가 표시되며 직원에게 작업 지시 처리를 위한 " +"다양한 옵션이 제공됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:137 msgid "" @@ -21294,6 +21667,9 @@ msgid "" " Alternatively, clicking the checkbox on the right side of each line " "automatically marks the step as completed." msgstr "" +"작업 지시 카드의 기본 섹션에는 작업 지시를 완료하는 데 필요한 각 단계에 대한 항목이 표시됩니다. 이러한 단계는 해당 항목을 선택한 " +"다음 이어지는 팝업 창의 지시를 따르면 완료할 수 있습니다. 또는 각 항목의 오른쪽에 있는 확인란을 선택하면 해당 단계가 자동으로 완료된" +" 것으로 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:147 msgid "" @@ -21303,6 +21679,9 @@ msgid "" ":guilabel:`Register Production` line on a work order card also completes the" " step for the associated |MO| card." msgstr "" +"작업지시서의 마지막 단계 아래에는 :guilabel:`생산 등록`이라고 표시된 섹션이 있으며, 이는 |MO| 카드의 " +":guilabel:`생산 등록` 기능과 유사하게 작동합니다. 작업 주문 카드의 :guilabel:`생산 등록` 항목을 통해 생산된 유닛의" +" 수량을 기록하면 해당 |MO| 카드의 단계도 완료됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:152 msgid "" @@ -21313,6 +21692,9 @@ msgid "" " quality check must be completed from the |MO| card before the |MO| can be " "closed." msgstr "" +"|MO| 내에서 마지막 작업 주문을 처리할 때 작업 주문 카드 하단에 :guilabel:`생산 종료` 버튼이 표시됩니다. 해당 작업 " +"주문에 대한 품질 검사가 필요하지 않은 경우, :guilabel:`생산 종료`를 클릭하면 작업 주문과 연결된 |MO|가 모두 종료됩니다." +" 품질 검사가 필요한 경우 |MO| 카드에서 품질 검사를 완료해야 |MO|를 닫을 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:158 msgid "" @@ -21322,6 +21704,9 @@ msgid "" "causes the next work order to appear on the page for the work center it is " "assigned to." msgstr "" +"|MO| 내에서 완료해야 할 작업 주문이 더 있는 경우, :guilabel:`완료로 표시` 버튼이 대신 나타납니다. " +":guilabel:`완료로 표시`를 클릭하면 현재 작업 주문이 완료된 것으로 표시되고 해당 작업장의 페이지에 다음 작업 주문이 " +"표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:163 msgid "" @@ -21331,34 +21716,40 @@ msgid "" "open. Once the work order card disappears completely, the work order is " "marked as :guilabel:`Finished` on the |MO|." msgstr "" +":guilabel:`생산 종료` 또는 :guilabel:`완료로 표시`를 클릭하면 작업 주문 카드가 사라지기 시작하고 하단에 " +":guilabel:`실행 취소` 버튼이 표시됩니다. :guilabel:`실행 취소`를 클릭하면 작업 주문이 계속 열려 있습니다. 작업 " +"주문 카드가 완전히 사라지면 작업 주문은 |MO|에 :guilabel:`완료`로 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:168 msgid "" "On the right side of the footer is an :guilabel:`⋮ (options)` button, which " "opens a pop-up window with additional options for the work order:" msgstr "" +"하단 오른쪽에는 :guilabel:`⋮ (옵션)` 버튼이 있습니다. 이 버튼을 클릭하면 작업 주문에 대한 추가 옵션이 있는 팝업 창이 " +"열립니다:" #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:174 msgid "" ":guilabel:`Move to work center` is used to transfer the work order to a " "different work center." -msgstr "" +msgstr ":guilabel:`작업장으로 이동`을 사용하면 작업 주문을 다른 작업장으로 전송할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:175 msgid "" ":guilabel:`Suggest a Worksheet improvement` allows the user to propose a " "change to the work order's instructions or steps." -msgstr "" +msgstr ":guilabel:`작업표 개선 제안`을 사용하면 사용자가 작업 주문의 지침 또는 단계에 대한 변경을 제안할 수 있습니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:177 msgid "" ":guilabel:`Create a Quality Alert` opens a quality alert form that can be " "filled out to alert a quality team about a potential issue." msgstr "" +":guilabel:`품질 알림 생성`을 클릭하면 품질 팀에 잠재적인 문제에 대한 세부 정보를 제공할 수 있는 품질 알림 양식이 열립니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 msgid "An information card for a work order in the Shop Floor module." -msgstr "" +msgstr "작업 현장 모듈의 작업 주문에 대한 정보 카드입니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:185 msgid "Operator panel" @@ -21370,6 +21761,8 @@ msgid "" " *Shop Floor* module. The panel shows the name and profile picture of every " "employee that is currently signed in across all instances of the database." msgstr "" +"운영자 패널은 *작업 현장* 모듈에 로그인한 직원을 관리하는 데 사용됩니다. 이 패널에는 데이터베이스의 모든 인스턴스에서 현재 로그인한 " +"모든 직원의 이름과 프로필 사진이 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:191 msgid "" @@ -21377,6 +21770,8 @@ msgid "" "name to activate their profile. Profiles that are not active appear with " "their names and profile pictures greyed-out." msgstr "" +"특정 직원으로서 *작업 현장* 모듈에 참여하려면 해당 직원의 이름을 클릭하여 프로필을 활성화하기만 하면 됩니다. 비활성화된 프로필은 " +"이름과 프로필 사진이 회색으로 표시됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:194 msgid "" @@ -21386,6 +21781,9 @@ msgid "" "their name, along with a timer showing how long they've been working on each" " order." msgstr "" +"작업자 패널에서 직원을 선택하면 해당 작업 주문의 제목을 클릭하여 작업 주문에 대한 작업을 시작할 수 있습니다. 직원이 현재 하나 이상의" +" 작업 주문에 참여하고 있는 경우에는 작업 주문의 제목이 이름 아래에 표시됩니다. 또한 타이머가 각 작업 지시에 대해 작업 중인 기간을 " +"표시합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:199 msgid "" @@ -21393,18 +21791,21 @@ msgid "" "Operator` button at the bottom of the panel. Then, select an employee from " "the :guilabel:`Select Employee` pop-up window." msgstr "" +"새 직원을 상담원 패널에 포함하려면 패널 하단에 있는 :guilabel:`+ 상담원 추가` 버튼을 클릭합니다. 그런 다음 " +":guilabel:`직원 선택` 팝업창에서 직원을 선택합니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:202 msgid "" "To remove an employee from the operator panel, simply click the " ":guilabel:`x` button next to their name in the panel." msgstr "" +"운영자 패널에서 직원을 제거하려면 패널에서 해당 직원의 이름 옆에 있는 :guilabel:`x` 버튼을 클릭하기만 하면 됩니다." #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 msgid "" "The operator panel of the Shop Floor module, showing three employees signed " "in." -msgstr "" +msgstr "로그인한 세 명의 직원이 표시된 작업 현장 모듈의 운영자 패널입니다." #: ../../content/applications/inventory_and_mrp/plm.rst:8 msgid "Product lifecycle management" @@ -21417,11 +21818,13 @@ msgid "" "development, design, manufacturing, marketing, and post-launch support " "stages." msgstr "" +"Odoo *제품 수명 주기 관리*(*PLM*)는 컨셉 개발, 디자인, 제조, 마케팅, 출시 후 지원 등 다양한 단계에서 제품의 테스트, " +"협업 및 반복을 위한 체계적인 방법론을 제공합니다." #: ../../content/applications/inventory_and_mrp/plm.rst:14 msgid "" "With approvals, key stakeholders can review changes before implementation." -msgstr "" +msgstr "승인을 받으면 주요 이해관계자가 시행 전에 변경 사항을 검토할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes.rst:3 msgid "Change management" @@ -21438,6 +21841,9 @@ msgid "" " separates |ECOs| into a project in Gantt view, ensuring collaborators and " "stakeholders **only** view and assist with relevant |BOM| improvements." msgstr "" +"*ECO 유형*은 제품 및 자재명세서 (BoM)의 변경 사항을 구성하고 모니터링하기 위한 *설계 변경 주문*(ECO)을 위해 지정됩니다." +" 각 |ECO| 유형은 간트 보기 내에서 |ECO|를 별개의 프로젝트로 분류하여 협업자와 이해관계자가 관련 |ECO| 개선 사항**만**" +" 보고 지원할 수 있도록 합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:17 msgid "" @@ -21447,6 +21853,9 @@ msgid "" "the 'New Product Introduction' and 'Product Improvement' projects, avoiding " "unrelated supplier change or firmware update |ECOs|." msgstr "" +"예를 들어, 반도체 제조업체는 '신제품 도입', '제품 개선', '부품 변경', '펌웨어 업데이트' 유형의 |ECO|를 사용할 수 " +"있습니다. 이렇게 하면 설계자와 엔지니어는 '신제품 도입' 및 '제품 개선' 프로젝트 내에서 |ECO|에 집중할 수 있으므로 관련 없는 " +"공급업체 변경이나 펌웨어 업데이트 |ECO|를 피할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:23 msgid "Create ECO type" @@ -21457,18 +21866,21 @@ msgid "" "To access and manage ECO types, navigate to :menuselection:`PLM app --> " "Configuration --> ECO Types`." msgstr "" +"ECO 유형에 액세스하고 관리하려면 :menuselection:`제품 수명주기 관리 앱 --> 환경설정 --> ECO 유형`으로 " +"이동합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:28 msgid "" "Create a new ECO type by clicking :guilabel:`New`. On the new :guilabel:`ECO" " Types` form, fill in the following information:" msgstr "" +":guilabel:`신규`를 클릭하여 새 ECO 유형을 만듭니다. 새 :guilabel:`ECO 유형` 양식에 다음 정보를 입력합니다:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:31 msgid "" ":guilabel:`Name`: the name of the |ECO| type, which will organize all of the" " |ECOs| of this *type* in a project." -msgstr "" +msgstr ":guilabel:`이름`: 이 *유형*의 모든 |ECO|를 프로젝트에 정리하는 |ECO| 유형의 이름입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:33 msgid "" @@ -21476,6 +21888,8 @@ msgid "" "to this email address automatically generate |ECOs| in the left-most stage " "of this |ECO| type." msgstr "" +":guilabel:`이메일 별칭`: 이 값을 입력하면 이 주소로 전송되는 이메일은 이 |ECO| 유형의 초기 단계에서 자동으로 " +"|ECO|를 생성합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:37 msgid "" @@ -21484,6 +21898,9 @@ msgid "" "generates |ECOs| in the `Formulation change` project sent to the email " "address, `pawlish-change@pawlished-glam.odoo.com`." msgstr "" +"`공식 변경` |ECO| 유형은 단일 프로젝트에서 관련 |ECO|를 정리하고 추적하는 데 사용됩니다. :guilabel:`이메일 별칭` " +"필드를 설정하면 `pawlish-change@pawlished-glam.odoo.com`으로 이메일이 전송될 때 `공식 변경` " +"프로젝트에서 자동으로 |ECO|를 생성합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 msgid "Example of an ECO type." @@ -21499,12 +21916,15 @@ msgid "" ":menuselection:`PLM app --> Configuration --> ECO Types` page. There, click " "on the desired |ECO| type from the list." msgstr "" +"기존 |ECO| 유형의 이름과 이메일 별칭을 조정하려면 :menuselection:`PLM 앱 --> 설정 --> ECO 유형` 페이지로" +" 이동합니다. 목록에서 원하는 |ECO| 유형을 선택하고 필요한 내용을 수정합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:51 msgid "" "On the form for each |ECO| type, proceed to edit the :guilabel:`Name` and " ":guilabel:`Email Alias` fields." msgstr "" +"각 |ECO| 유형에 대한 양식에서 :guilabel:`이름` 및 :guilabel:`이메일 별칭` 필드를 편집할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:57 msgid "Stages" @@ -21516,6 +21936,8 @@ msgid "" "identify the progress of the |ECO| before the changes are ready to be " "applied. (e.g. 'Feedback', 'In Progress', 'Approved', 'Complete')" msgstr "" +"|ECO| 유형 프로젝트 내에서 *단계*는 변경 사항을 검토하고 적용을 준비하면서 |ECO| 의 진행 상황을 추적하는 마일스톤 역할을 " +"합니다. (예: '피드백', '진행 중', '승인됨', '완료')" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:63 msgid "" @@ -21525,6 +21947,9 @@ msgid "" "enforcing at least one review of suggested changes before they're applied on" " a production |BOM|." msgstr "" +"또한 각 단계에 필수 승인자를 지정하여 지정된 승인자가 |ECO|를 검토하고 승인할 때까지 생산 |BOM|의 수정이 진행될 수 없도록 할" +" 수 있습니다. 이 관행은 제안된 변경 사항을 구현하기 전에 최소 한 번 이상 검토하도록 의무화하여 생산 |BOM|에서 발생하는 오류를 " +"방지하는 데 도움이 됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:68 msgid "" @@ -21533,6 +21958,8 @@ msgid "" "|ECOs| that have been either canceled or approved for use as the next " "production |BOM|." msgstr "" +"최적의 프로세스를 위해 필수 승인자가 있는 *확인* 단계를 하나 이상 유지하고, 승인 또는 취소된 |ECO|를 다음 생산 |BOM|에 " +"저장하기 위한 *마감* 단계를 하나 이상 유지하세요." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:73 msgid "Create stage" @@ -21543,6 +21970,8 @@ msgid "" "To add a stage, go to the :menuselection:`PLM` app and select the intended " "project for an |ECO| type from the :guilabel:`PLM Overview` dashboard." msgstr "" +"단계를 추가하려면 :menuselection:`PLM` 앱으로 이동한 다음 :guilabel:`PLM 현황` 대시보드에서 원하는 " +"프로젝트의 |ECO| 유형을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:78 msgid "" @@ -21551,6 +21980,9 @@ msgid "" "box to fill in the name of the stage. After filling it in, click the " ":guilabel:`Add` button to finish adding the stage." msgstr "" +"그런 다음 |ECO| 유형에 대한 :guilabel:`설계 변경 주문` 프로젝트 파이프라인에서 :guilabel:`+ 단계` 버튼을 " +"클릭합니다. 이 작업을 수행하면 단계의 이름을 입력할 수 있는 텍스트 상자가 나타납니다. 입력 후 :guilabel:`추가` 버튼을 " +"클릭하여 단계 추가를 완료합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:83 msgid "" @@ -21558,10 +21990,12 @@ msgid "" " the `New` stage. Adding another stage helps the product manager track " "unassigned tasks." msgstr "" +"신규 `할당됨` 단계는 할당된 |ECO|를 `신규` 단계에서 할당 대기 중인 |ECO|와 구분합니다. 다른 단계를 추가하면 제품 관리자가" +" 할당되지 않은 작업을 추적하는 데 도움이 됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 msgid "Create a new stage in a project for an ECO type." -msgstr "" +msgstr "프로젝트에서 ECO 유형에 대한 새 단계를 만듭니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:91 msgid "Verification stage" @@ -21572,6 +22006,7 @@ msgid "" "Click an ECO type from :menuselection:`PLM app --> Overview` to open a " "kanban view of |ECOs| of this type." msgstr "" +":menuselection:`PLM 앱 --> 현황`에서 에코 유형을 클릭하면 해당 유형의 |ECO|에 대한 칸반 보기가 열립니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:96 msgid "" @@ -21579,12 +22014,14 @@ msgid "" " the :guilabel:`⚙️ (gear)` icon. Then, click :guilabel:`Edit` to open a pop-" "up window." msgstr "" +"인증 단계를 설정하려면 원하는 단계 위로 마우스를 가져가서 :guilabel:`⚙️ (기어)` 아이콘을 선택합니다. 그런 다음 " +":guilabel:`수정`을 클릭하여 팝업 창을 엽니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:99 msgid "" "Configure the verification stage in the edit stage pop-up window, by " "checking the box for :guilabel:`Allow to apply changes`." -msgstr "" +msgstr "변경 단계 팝업 창에서 :guilabel:'변경 사항 적용 허용' 확인란을 선택하여 확인 단계를 구성합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:102 msgid "" @@ -21592,12 +22029,14 @@ msgid "" ":guilabel:`Add a line`, and specifying the :guilabel:`Role` of the reviewer," " their :guilabel:`User`, and :guilabel:`Approval Type`." msgstr "" +"다음으로 :guilabel:`결재권자` 섹션에서 :guilabel:`항목 추가`를 클릭하고 결재권자의 :guilabel:`역할`, " +":guilabel:`사용자` 및 :guilabel:`승인 유형`을 지정합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:106 msgid "" "Make sure at least one approver is configured with the :guilabel:`Approval " "Type`: :guilabel:`Is required to approve`." -msgstr "" +msgstr "최소 한 명 이상의 승인자가 :guilabel:`승인 유형`: :guilabel:`승인 필요`로 구성되어 있는지 확인합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:109 msgid "" @@ -21605,6 +22044,8 @@ msgid "" " stage specified in the pop-up window. Once finished, click :guilabel:`Save " "& Close`." msgstr "" +"지정된 승인자는 팝업 창에서 지정한 단계로 |ECO|가 이동하면 자동으로 알림을 받게 됩니다. 구성을 완료한 후 :guilabel:`저장" +" 후 닫기`를 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:113 msgid "" @@ -21613,6 +22054,8 @@ msgid "" "selecting :guilabel:`Edit`. Doing so opens the :guilabel:`Edit: Validated` " "pop-up window." msgstr "" +"`신제품 도입` |ECO| 유형에서 `승인됨` 검증 단계는 :guilabel:`⚙️ (기어)` 아이콘을 클릭하고 " +":guilabel:`편집`을 선택하면 설정됩니다. 이 작업을 수행하면 :guilabel:`편집: 검증됨` 팝업 창이 열립니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:117 msgid "" @@ -21620,16 +22063,18 @@ msgid "" "this user can proceed to the next stage, and have the changes applied on the" " production |BOM|." msgstr "" +"`엔지니어링 관리자`를 승인자로 포함하면 이 사용자가 승인한 |ECO|만 다음 단계로 진행할 수 있으며 변경 사항을 프로덕션 |ECO|에" +" 적용하도록 할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:120 msgid "" "Additionally, check the :guilabel:`Allow to apply changes` option to ensure " "proper behavior." -msgstr "" +msgstr "또한 :guilabel:`변경 사항 적용 허용` 옵션을 확인하여 올바른 동작이 이루어지는지 확인합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 msgid "Show \"Allow to apply changes\" option is checked." -msgstr "" +msgstr "\"변경 사항 적용 허용\" 옵션이 선택되어 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:127 msgid "Closing stage" @@ -21642,6 +22087,9 @@ msgid "" "(gear)` icon that appears in the top-right corner. Then, click " ":guilabel:`Edit` from the drop-down menu." msgstr "" +":guilabel:`편집: [단계]` 팝업창을 열어 종료 단계를 구성합니다. 이렇게 하려면 원하는 단계 위로 마우스를 가져가 오른쪽 " +"상단에 표시되는 :guilabel:`⚙️ (기어)` 아이콘을 클릭합니다. 그런 다음 드롭다운 메뉴에서 :guilabel:`편집`을 " +"클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:133 msgid "" @@ -21649,6 +22097,8 @@ msgid "" ":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes` and " ":guilabel:`Final Stage`." msgstr "" +":guilabel:`편집: [단계]` 팝업 창에서 :guilabel:`칸반 보기 접힘`, :guilabel:`변경 사항 적용 허용` 및 " +":guilabel:`최종 단계`의 확인란을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:137 msgid "" @@ -21656,6 +22106,8 @@ msgid "" ":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes`, and " ":guilabel:`Final Stage` options" msgstr "" +"마감 단계인 `유효`는 :guilabel:`칸반 보기 접힘`, :guilabel:`변경 사항 적용 허용`, :guilabel:`최종 " +"단계` 옵션을 체크하여 설정합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst-1 msgid "Show configurations of the closing stage." @@ -21671,6 +22123,8 @@ msgid "" " change versions made to products, and :ref:`bills of materials " "<manufacturing/management/bill-configuration>`." msgstr "" +"설계 변경 주문*(*ECO*)을 사용하여 제품 및 :ref:`자재명세서 <manufacturing/management/bill-" +"configuration>`에 대한 변경 사항을 모니터링, 시행 및 되돌리세요." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:15 msgid "Engineering change orders can be created:" @@ -21684,13 +22138,13 @@ msgstr ":ref:`ECO 유형에서 직접 <plm/eco/create-eco>`." msgid "" "by an operator in the :ref:`tablet view <plm/eco/tablet-view>` of an " "operation." -msgstr "" +msgstr "작업의 :ref:`태블릿 보기 <plm/eco/tablet-view>`에서 연산자가 지정할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:19 msgid "" "automatically from feedback submitted to the :ref:`ECO type's email alias " "<plm/eco/eco-type>`." -msgstr "" +msgstr ":ref:`ECO 유형의 이메일 별칭 <plm/eco/eco-type>`으로 제출된 피드백에서 자동으로 생성됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:24 msgid "Create ECO" @@ -21703,6 +22157,8 @@ msgid "" "On the :guilabel:`Engineering Change Orders` page, click the :guilabel:`New`" " button in the top-left corner." msgstr "" +"새 |ECO|를 생성하려면 먼저 *PLM* 앱으로 이동합니다. 그런 다음 적절한 |ECO| 유형 카드를 선택하여 변경 진행 상황을 " +"추적합니다. :guilabel:`설계 변경 주문` 페이지에서 왼쪽 상단에 있는 :guilabel:'신규' 버튼을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:31 msgid "" @@ -21712,26 +22168,30 @@ msgid "" "introductions, targeted product line updates, or regulatory compliance " "fulfillment." msgstr "" +"변경 주문을 분류하고 정리하기 위해 새로운 :ref:`ECO 유형 <plm/eco/eco-type>`을 생성하는 방법을 알아보세요. " +"이렇게 하면 신제품 출시, 대상 제품군 업데이트, 규정 준수 이행 등 직원들이 자신의 담당 업무와 관련된 <ECO>만 볼 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:36 msgid "On the |ECO| form, fill in the following fields accordingly:" -msgstr "" +msgstr "|ECO| 양식에서 다음 필드를 적절하게 입력합니다:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:38 msgid ":guilabel:`Description` is a brief summary of the improvement." -msgstr "" +msgstr ":guilabel:`설명`은 개선 사항에 대한 간략한 요약입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:39 msgid "" ":guilabel:`Type`: specifies the |ECO| type project for organizing the " "|ECOs|." -msgstr "" +msgstr ":guilabel:`유형`: |ECO|를 구성하기 위한 |ECO| 유형 프로젝트를 지정합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:40 msgid "" ":guilabel:`Apply on` determines if the |ECO| changes the :guilabel:`Bill of " "Materials` or the :guilabel:`Product Only`." msgstr "" +":guilabel:`적용` 설정에 따라 |ECO|가 :guilabel:`자재명세서`를 변경할지 아니면 :guilabel:`품목 전용`을 " +"변경할지 결정됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:42 msgid ":guilabel:`Product` indicates the product being improved." @@ -21744,6 +22204,8 @@ msgid "" "multiple |BOMs| exist, select the intended radio options from the drop-down " "menu." msgstr "" +":guilabel:`BOM`은 변경된 |BOM|을 지정하고 :guilabel:`품목` 필드에 기존 |BOM|이 있는 제품의 경우 자동으로" +" 채워집니다. 여러 개의 BOM이 있는 경우 드롭다운 메뉴에서 원하는 옵션을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:46 msgid "" @@ -21751,12 +22213,14 @@ msgid "" " change applies to products in a specific company, or leave blank if the " "change applies to all companies." msgstr "" +":guilabel:`회사` 필드는 여러 회사 데이터베이스에서 사용됩니다. 변경 사항이 특정 회사의 제품에 적용되는지 여부를 지정하거나 " +"모든 회사에 적용되는 변경 사항인 경우 비워 둡니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:48 msgid "" ":guilabel:`Responsible` represents the assignee in charge of this |ECO|. " "(Optional)" -msgstr "" +msgstr ":guilabel:`담당자`는 이 |ECO|를 관리하도록 지정된 책임자를 나타냅니다. (선택 사항)" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:49 msgid "" @@ -21765,6 +22229,8 @@ msgid "" "|BOM| as soon as an authorized user :ref:`applies the changes " "<plm/eco/apply-changes>`." msgstr "" +":guilabel:`유효`는 |ECO|가 적용되는 시점을 결정합니다. :guilabel:`가능한 한 빨리`를 선택하면 권한이 부여된 " +"사용자가 :ref:` 변경 사항 <plm/eco/apply-changes>`를 적용하면 즉시 생산 |BOM|에 |ECO|가 적용됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:53 msgid "" @@ -21772,6 +22238,8 @@ msgid "" "date, leaves a date that makes it easier to track the version history of the" " |BOM|, and the specific date |BOMs|, used for production." msgstr "" +"반면에 :guilabel:`일시`를 선택하고 특정 날짜를 지정하면 |BOM|의 버전 기록과 생산에 사용된 특정 날짜 |BOM|을 더 잘 " +"추적할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:56 msgid "" @@ -21779,12 +22247,14 @@ msgid "" " Create a new tag by typing the name in the field and selecting " ":guilabel:`Create` from the drop-down menu. (Optional)" msgstr "" +"우선순위 지정 및 정리를 위해 :guilabel:`태그`는 |ECO|에 할당됩니다. 필드에 이름을 입력하고 드롭다운 메뉴에서 " +":guilabel:`생성`을 선택하여 새 태그를 만들 수 있습니다. (선택 사항)" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:59 msgid "" "After filling out the |ECO| form, click the :guilabel:`Start Revision` " "button to begin implementing the changes." -msgstr "" +msgstr "|ECO| 양식을 작성한 후 :guilabel:`수정 시작` 버튼을 클릭하면 변경 사항 적용이 시작됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:62 msgid "By pressing :guilabel:`Start Revision`, three actions occur:" @@ -21794,7 +22264,7 @@ msgstr ":guilabel:`변경 시작`을 누르면 세 가지 작업이 실행됩니 msgid "" "The :guilabel:`Documents` smart button appears, storing relevant files of " "the |BOM|." -msgstr "" +msgstr ":guilabel:`문서` 스마트 버튼이 나타나며 |BOM|의 관련 파일을 저장합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:65 msgid "" @@ -21803,12 +22273,14 @@ msgid "" "number (e.g., `V2`, `V3`, ...) is also assigned to keep track of all |BOM| " "versions." msgstr "" +"이제 생산 |BOM|의 사본이 모든 |BOM| 버전을 추적할 수 있도록 새로 표시된 |ECO|의 :guilabel:`수정` 스마트 버튼에" +" 저장되며, 사용 가능한 다음 버전 번호(예: `V2`, `V3`, ...)가 함께 지정됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:68 msgid "" "The stages of the |ECO| :guilabel:`Type` are displayed in the top-right " "corner of the |ECO|." -msgstr "" +msgstr "|ECO| :guilabel:`유형`의 단계는 |ECO|의 오른쪽 상단에 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:71 msgid "" @@ -21817,12 +22289,14 @@ msgid "" ":guilabel:`Apply on` field, and the :guilabel:`Start Revision` button has " "been pressed." msgstr "" +":guilabel:`수정` 스마트 버튼은 :guilabel:`자재명세서` 라디오 버튼이 :guilabel:`적용` 필드에서 선택되어 있고" +" :guilabel:`수정 시작` 버튼을 누른 **경우에만** 사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 msgid "" "ECO with overview of stages in the top-right corner, and *Revision* smart " "button." -msgstr "" +msgstr "오른쪽 상단 모서리에 단계가 표시되고 *수정* 스마트 버튼이 있는 ECO." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:80 msgid "Change components" @@ -21835,6 +22309,9 @@ msgid "" "distinguishes the non-production version of the |BOM| from the current " "version, by flagging the test |BOM| with a large :guilabel:`Archived` tag." msgstr "" +"|BOM|의 구성품을 조정하려면 |ECO|에서 :guilabel:`수정` 스마트 버튼을 선택하여 업데이트된 버전의 |BOM|으로 " +"이동합니다. Odoo는 눈에 잘 띄는 :guilabel:`아카이브됨` 태그로 테스트 |BOM을 표시하여 비프로덕션 버전의 |BOM|과 " +"현재 버전을 명확하게 구분합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:87 msgid "" @@ -21843,6 +22320,9 @@ msgid "" "the :guilabel:`Revision` smart button. Doing so opens the archived |BOM|, " "marked with a large red :guilabel:`Archived` flag." msgstr "" +"제품 `[D_0045 스툴]`과 관련된 |ECO|에 대한 :guilabel:`수정 시작` 버튼을 클릭한 후에는 :guilabel:`수정`" +" 스마트 버튼을 선택하여 제품의 |BOM|을 조정합니다. 이 작업을 수행하면 보관된 |BOM|이 열리며, 눈에 잘 띄는 빨간색 " +":guilabel:`보관됨` 플래그가 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "Show the archived Bill of Materials." @@ -21855,18 +22335,21 @@ msgid "" "components, adding new components using the :guilabel:`Add a line` button, " "and removing components with the :guilabel:`🗑️ (trash)` icon." msgstr "" +"새 |BOM|의 :guilabel:`부품` 탭에서 부품 목록을 조정할 수 있습니다. 여기에는 기존 구성품의 :guilabel:`수량`을 " +"변경하고, :guilabel:`항목 추가` 버튼을 사용하여 새 부품을 추가하고, :guilabel:`🗑️ (휴지통)` 아이콘으로 부품을 " +"제거하는 작업이 포함됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:102 msgid "" "In version two of the |BOM| for a keyboard, the component quantities are " "reduced, and an additional component, `Stabilizers`, is added." -msgstr "" +msgstr "키보드용 |BOM|의 두 번째 버전에서는 부품의 수량이 감소하고 새로운 부품인 `스테빌라이저`가 추가되었습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "" "Make changes to components by going to the new BoM with the *Revision* smart" " button." -msgstr "" +msgstr "*수정* 스마트 버튼으로 새 BoM으로 이동하여 부품을 변경할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:110 #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:153 @@ -21880,6 +22363,8 @@ msgid "" "form, a new :guilabel:`BoM Changes` tab displays the differences between the" " current |BOM| and the new version." msgstr "" +"변경을 완료했으면 왼쪽 상단의 이동 경로에서 `ECO00X`를 클릭하여 |ECO|로 돌아갑니다. |ECO| 양식에 새로운 " +":guilabel:`BOM 변경사항` 탭이 표시되며, 이 탭에는 현재 |BOM|과 업데이트된 버전 간의 차이가 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:116 msgid "" @@ -21887,6 +22372,8 @@ msgid "" "in the production |BOM|. Black text represents updates shared by both " "|BOMs|, while red text indicates components removed in the revised |BOM|." msgstr "" +"파란색 텍스트는 현재 생산 |BOM|에 없는 새 부품이 업데이트된 |BOM|에 추가되었음을 나타냅니다. 검은색 텍스트는 두 |BOM| " +"간에 공유되는 변경 사항을 나타내며, 빨간색 텍스트는 업데이트된 |BOM|에서 제거된 부품을 나타냅니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:120 msgid "" @@ -21894,16 +22381,18 @@ msgid "" "affect the |BOM| currently used in production. That is, until the " ":ref:`changes are applied <plm/eco/apply-changes>`." msgstr "" +"변경 사항 및 테스트는 수정된 |BOM|에 포함되며 :ref:`변경 사항 적용<plm/eco/apply-changes>`까지 현재 생산에" +" 사용되는 |BOM|에 영향을 미치지 **않습니다**." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:124 msgid "" "View the summary of the differences between the current and revised keyboard" " |BOMs| in the :guilabel:`BoM Changes` tab of the |ECO|." -msgstr "" +msgstr "현재 키보드와 수정된 키보드의 차이점 요약은 |ECO|의 :guilabel:`BoM 변경 사항` 탭에서 확인할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "View summary of component changes in the *BoM Changes* tab." -msgstr "" +msgstr "*BoM 변경 사항* 탭에서 부품 변경 사항 요약을 확인합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:132 msgid "Change operations" @@ -21914,6 +22403,8 @@ msgid "" "To modify the operations in a |BOM|, click the :guilabel:`Revision` smart " "button on an |ECO| to access the archived, new version of the |BOM|." msgstr "" +"|BOM|의 작업을 조정하려면 |ECO|에서 :guilabel:`수정` 스마트 버튼을 선택하여 보관된 새 버전의 |BOM|에 " +"액세스합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:137 msgid "" @@ -21921,6 +22412,8 @@ msgid "" "and edit |BOM| operations. To make changes, select each operation, which " "opens the corresponding :guilabel:`Open: Operations` pop-up window." msgstr "" +"업데이트된 |BOM| 버전에서는 :guilabel:`작업` 탭으로 이동하여 |BOM| 작업을 검토하고 수정합니다. 변경을 시작하려면 각 " +"작업을 클릭하여 해당 :guilabel:`열기: 작업` 팝업 창을 엽니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:142 msgid "" @@ -21928,30 +22421,35 @@ msgid "" "navigate to :menuselection:`Manufacturing app --> Configuration --> " "Settings`, and check the :guilabel:`Work Orders` box." msgstr "" +":guilabel:`작업` 탭은 기본적으로 *활성화되어 있지 않습니다*. 사용하려면 먼저 :menuselection:`제조 관리 --> " +"설정 --> 환경설정`으로 이동하여 :guilabel:`작업 주문` 확인란을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:146 msgid "" "Make changes to any of the fields in the :guilabel:`Open: Operations` pop-up" " window, then click :guilabel:`Save` once completed." -msgstr "" +msgstr ":guilabel:`열기: 작업` 팝업 창에서 필드를 변경한 다음 완료되면 :guilabel:`저장`을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:149 msgid "" "Create new operations by clicking the :guilabel:`Add a line` button, and " "remove new operations by clicking the :guilabel:`Archive Operation` button." msgstr "" +":guilabel:`항목 추가` 버튼을 사용하여 새 작업을 생성하고 :guilabel:`작업 보관` 버튼으로 원하지 않는 작업을 " +"제거합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:155 msgid "" "Once the changes are complete, navigate back to the |ECO|, by clicking " "`ECO00X` in the breadcrumbs located in the top-left corner." -msgstr "" +msgstr "변경이 완료되면 왼쪽 상단에 있는 사이트 이동 경로를 누르고 'ECO00X'를 클릭하여 |ECO|로 다시 이동합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:158 msgid "" "On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the " "differences between the current production |BOM| and the new version." msgstr "" +"|ECO| 양식에 새로운 :guilabel:`작업 변경` 탭이 표시되어 현재 생산 |BOM|과 업데이트된 버전 간의 차이점을 보여줍니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:161 msgid "" @@ -21960,6 +22458,8 @@ msgid "" "both |BOMs|, while red text indicates operations removed in the revised " "|BOM|." msgstr "" +"파란색 텍스트는 수정된 |BOM|에 추가된 새 작업 중 생산 |BOM|에 아직 반영되지 않는 작업을 나타냅니다. 검은색 텍스트는 두 " +"|BOM| 간에 공유되는 변경 사항을 나타내며, 빨간색 텍스트는 업데이트된 |BOM|에서 제거된 작업을 나타냅니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:165 msgid "" @@ -21967,22 +22467,24 @@ msgid "" " production. That is, until the :ref:`changes are applied <plm/eco/apply-" "changes>`." msgstr "" +"|ECO| 내의 |BOM|에 대한 변경 사항은 :ref:`변경 사항 적용<plm/eco/apply-changes>`까지 현재 생산에 " +"사용되는 |BOM|에는 영향을 미치지 **않습니다.**" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:168 msgid "" "In the :guilabel:`Operation Changes` tab, each row of details, beneath the " "columns in the table, reflect the following information:" -msgstr "" +msgstr "guilabel:`작업 변경` 탭 내에서 표의 열 아래에 있는 각 세부 정보 행은 다음 정보를 나타냅니다:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:171 msgid ":guilabel:`Operation`: Name of the operation that was modified." -msgstr "" +msgstr ":guilabel:`작업`: 수정된 작업의 이름입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:172 msgid "" ":guilabel:`Step`: specifies the quality control point, visible when the " "operation includes detailed instructions." -msgstr "" +msgstr ":guilabel:`단계`: 작업에 자세한 지침이 포함된 경우 표시되는 품질 관리 지점을 나타냅니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:176 msgid "" @@ -21991,24 +22493,28 @@ msgid "" "Operations` pop-up window, look for the :guilabel:`Instructions` smart " "button displayed at the top." msgstr "" +"지침을 보려면 |BOM|의 :guilabel:`작업` 탭에서 작업 줄 항목을 클릭합니다. :guilabel:`열기: 작업` 팝업 창에서 " +"상단에 있는 :guilabel:`지침` 스마트 버튼을 찾습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:181 msgid "" "The `Assembly` :guilabel:`Operation` includes `10` detailed " ":guilabel:`Instructions` to complete it." -msgstr "" +msgstr "`조립 생산` :guilabel:`작업`에는 완료를 위한 `10`개의 세부 :guilabel:`지침`이 포함되어 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "" "Show *Instructions* smart button to check whether an operation has additional\n" "instructions." msgstr "" +"*지침* 스마트 버튼을 표시하여 작업에 추가 지침이 포함되어 있는지 \n" +"확인합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:189 msgid "" ":guilabel:`Step Type` details the type of quality control for further " "instructions in the operation." -msgstr "" +msgstr ":guilabel:`단계 유형`은 작업의 추가 지침에 대한 품질 관리 유형을 자세히 설명합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:191 msgid "" @@ -22016,12 +22522,14 @@ msgid "" "revised |BOM| differs from the production |BOM|. Operation change types can " "be :guilabel:`Add`, :guilabel:`Remove`, or :guilabel:`Update`." msgstr "" +":guilabel:`유형`은 수정된 |BOM|이 생산 |BOM|과 어떻게 다른지를 나타내는 컬러 텍스트에 해당합니다. 작업 변경 유형은 " +":guilabel:`추가`, :guilabel:`제거` 또는 :guilabel:`업데이트`가 될 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:194 msgid "" ":guilabel:`Work Center` specifies the work center at which the operation is " "performed." -msgstr "" +msgstr ":guilabel:`작업 센터`는 작업이 수행되는 작업 센터를 나타냅니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:195 msgid "" @@ -22029,12 +22537,14 @@ msgid "" ":guilabel:`Default Duration` field in the :guilabel:`Open: Operations` pop-" "up window, which specifies the expected time for completing the operation." msgstr "" +":guilabel:`수동 기간 변경`은 :guilabel:`열기`의 :guilabel:`기본 기간` 필드에 대한 변경 사항을 나타냅니다:" +" `작업` 팝업 창에서 작업을 완료하는 데 필요한 예상 시간을 정의합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:200 msgid "" "The :guilabel:`Operation Changes` tab compares the production |BOM| with the" " revised |BOM| in the |ECO|." -msgstr "" +msgstr ":guilabel:`작업 변경` 탭은 현재 생산 |BOM|과 |ECO|의 업데이트된 |BOM|을 비교합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:203 msgid "" @@ -22043,24 +22553,30 @@ msgid "" "expected duration of the operation is `20.00` minutes, as specified by the " ":guilabel:`Manual Duration Change`." msgstr "" +"업데이트된 |BOM|에는 :guilabel:`작업장`의 `조립 생산 라인 1`에 새로운 `조립 생산` :guilabel:`작업`이 " +"추가됩니다. 예상 작업 시간은 `수동 기간 변경`에 표시된 대로 `20.00`분입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:207 msgid "" "To supplement the `Assembly` operation, two quality control point " "instructions are added:" -msgstr "" +msgstr "`조립 생산` 작업을 보완하기 위해 두 개의 품질 관리 포인트 지침이 추가되었습니다:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:209 msgid "" "The first is the :guilabel:`Step` `QCP00039`, a :guilabel:`Step Type` to " ":guilabel:`Register Production` of components." msgstr "" +"첫 번째 :guilabel:`단계`는 부품의 :guilabel:`생산 등록`을 나타내는 :guilabel:`단계 유형`인 " +"`QCP00039`입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:211 msgid "" "The second :guilabel:`Step` is `QCP00034`, an `Instructions` :guilabel:`Step" " Type` that provides additional assembly details." msgstr "" +"두 번째 :guilabel:`단계`는 추가 조립 생산 세부 정보를 제공하는 `지침` :guilabel:`단계 유형`인 " +"`QCP00034`입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "Show *Operation Changes* tab in an |ECO|." @@ -22076,6 +22592,8 @@ msgid "" "<plm/eco/stage-config>`, which are stages that require approval before the " "revised changes can be applied to the production |BOM|." msgstr "" +"변경 사항을 확인한 후, 수정된 변경 사항을 생산 |BOM|에 적용하기 전에 승인이 필요한 단계인 |ECO|를 :ref:`승인 단계 " +"<plm/eco/stage-config>`로 이동합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:227 msgid "" @@ -22084,6 +22602,8 @@ msgid "" "to a closing stage. The changes are applied, which archives the original " "production |BOM|, and the revised |BOM| becomes the new production |BOM|." msgstr "" +"승인자가 변경 사항을 승인하면 :guilabel:`변경 사항 적용` 버튼이 활성화됩니다. 이 버튼을 클릭하면 |ECO|가 자동으로 종료 " +"단계로 전환됩니다. 그런 다음 변경사항이 적용되면 원래 생산 |BOM|이 보관되고 수정된 |BOM|이 새 생산 |BOM| 버전이 됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:232 msgid "Verify changes" @@ -22095,11 +22615,13 @@ msgid "" "Changes` button was just pressed, return to the revised |BOM| by clicking " "the :guilabel:`Revision` smart button." msgstr "" +"변경 사항이 적용되었는지 확인하려면 :guilabel:`변경 사항 적용` 버튼을 클릭한 |ECO|에서 :guilabel:`수정` 스마트 " +"버튼을 클릭하여 수정된 |BOM|으로 돌아갑니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:237 msgid "" "On the revised |BOM|, the large red :guilabel:`Archived` flag is removed." -msgstr "" +msgstr "수정된 |BOM|에서는 빨간색의 큰 :guilabel:`보관됨` 플래그가 제거됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:239 msgid "" @@ -22107,6 +22629,8 @@ msgid "" ":menuselection:`Manufacturing app --> Products --> Products` and select the " "product." msgstr "" +"변경 사항을 추가로 확인하려면 :menuselection:`제조 관리 앱 --> 품목 --> 품목`으로 이동하여 생산 |BOM|을 " +"확인하고 품목을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:242 msgid "" @@ -22116,6 +22640,9 @@ msgid "" "version number shown on the :guilabel:`Revision` smart button of the latest " "|ECO|." msgstr "" +"그런 다음 제품 양식에서 :guilabel:`자재명세서` 스마트 버튼을 클릭하고 목록에서 |BOM|을 선택합니다. |BOM|의 " +":guilabel:`기타` 탭에서 최신 |ECO|의 :guilabel:`수정` 스마트 버튼에 표시된 버전과 일치하도록 " +"guilabel:`버전` 필드가 업데이트됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:248 msgid "" @@ -22125,10 +22652,13 @@ msgid "" "has been updated to `2`, matching the `V2` that appears in the " ":guilabel:`Revision` smart button of the |ECO|." msgstr "" +":ref:`키보드 <plm/eco/example-keyboard>`에 대한 |ECO|의 변경 사항을 적용한 후, 현재 키보드 |ECO| " +"버전을 :guilabel:`기타` 탭에서 확인합니다. 여기서 :guilabel:`버전` 번호가 `2`로 수정된 것을 확인할 수 있으며, " +"이는 `ECO`의 :guilabel:`수정` 스마트 버튼에 표시된 `V2`와 일치합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "View current *BOM* version in the Miscellaneous tab." -msgstr "" +msgstr "기타 탭에서 현재 *BOM* 버전 보기." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:260 msgid "Create ECO from tablet view" @@ -22138,7 +22668,7 @@ msgstr "태블릿 보기에서 ECO 생성하기" msgid "" "Operators can directly suggest clearer operation instructions, while " "performing manufacturing orders (MOs) in the *Manufacturing* app." -msgstr "" +msgstr "운영자는 *제조 관리* 앱에서 제조주문 (MO)을 수행하면서 보다 명확한 작업 지침을 직접 제안할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:265 msgid "" @@ -22148,6 +22678,9 @@ msgid "" ":guilabel:`Work Orders` tab. Then, click the :guilabel:`📱 (mobile phone)` " "icon for the desired work order to open the *tablet view* of the operation." msgstr "" +"이 방법을 사용하여 |ECO|을 생성하려면 먼저 :menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동합니다. " +"그런 다음 작업하려는 :abbr:`MO(제조 주문)`을 선택하고 :guilabel:`작업 주문` 탭으로 이동합니다. 거기에서 관련 작업 " +"주문의 :guilabel:`📱(휴대폰)` 아이콘을 클릭하면 *태블릿 보기*에서 작업이 열립니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:271 msgid "" @@ -22155,10 +22688,12 @@ msgid "" "(Manufacturing Orders)` with a :guilabel:`Confirmed` or :guilabel:`In " "Progress` status." msgstr "" +":guilabel:`📱 (휴대폰)` 아이콘은 :guilabel:`확인` 또는 :guilabel:`진행 중` 상태의 :abbr:`MOs " +"(제조 주문)`에서**만**사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 msgid "Find the tablet icon for each operation, second from the far right." -msgstr "" +msgstr "각 작업에 대한 태블릿 아이콘 (맨 오른쪽에서 두 번째 아이콘)을 찾습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:278 msgid "" @@ -22167,18 +22702,21 @@ msgid "" "the :guilabel:`Menu` of action items for a :abbr:`MO (Manufacturing Order)`." " Then, click the :guilabel:`Add a step` button." msgstr "" +"그런 다음 작업의 태블릿 보기에서 :guilabel:`☰(가로줄 3개)` 아이콘을 선택하여 지시 단계를 포함시킵니다. 이 작업은 " +":abbr:`MO (제조주문)`에 대한 옵션의 :guilabel:`메뉴`를 표시합니다. 거기에서 :guilabel:`단계 추가` 버튼을 " +"클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 msgid "" "Open the *Add a Step* pop-up by clicking the three horizontal lines icon in " "tablet view." -msgstr "" +msgstr "태블릿 보기에서 가로줄 3개가 있는 아이콘을 선택하여 *단계 추가* 팝업을 엽니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:286 msgid "" "Clicking the button reveals an :guilabel:`Add a step` pop-up window, where " "the proposed changes are submitted." -msgstr "" +msgstr "버튼을 클릭하면 제안된 변경 사항을 제출할 수 있는 :guilabel:`단계 추가` 팝업 창이 나타납니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:289 msgid "" @@ -22187,6 +22725,9 @@ msgid "" "greater detail. Optionally, add an image to the :guilabel:`Document` field. " "Once completed, finish by clicking the :guilabel:`Propose Change` button." msgstr "" +":guilabel:`제목` 필드에 단계에 대한 간단한 설명을 입력합니다. 그런 다음 :guilabel:`지침` 텍스트 필드에 단계에 대한" +" 자세한 지침을 입력합니다. 원하는 경우 :guilabel:`문서` 필드에 이미지를 첨부할 수 있습니다. 완료했으면 " +":guilabel:`변경 제안` 버튼을 클릭하여 제출합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:295 msgid "" @@ -22194,28 +22735,30 @@ msgid "" "the :guilabel:`Add a Step` pop-up window. Doing so creates an instructional " "quality control point that will be reviewed in the following section." msgstr "" +"깨진 구성 요소에 대한 추가 점검을 제안하려면 :guilabel:`단계 추가` 팝업 창에 필요한 정보를 입력합니다. 이렇게 하면 다음 " +"섹션에서 검토할 교육용 품질 관리 지점이 생성됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "" "Fill out the *Add a Step* form to suggest an additional quality control " "point." -msgstr "" +msgstr "추가 품질 관리 지점을 제안하려면 *단계 추가* 양식을 작성하세요." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:303 msgid "" "Based on the inputs from the :guilabel:`Add a Step` pop-up window, an |ECO| " "is created with the following information:" -msgstr "" +msgstr ":guilabel:`단계 추가` 팝업 창에 입력된 정보를 바탕으로 다음 세부 정보가 포함된 |ECO|가 생성됩니다:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:306 msgid "" ":guilabel:`Description` is the name of the operation, followed by the " ":abbr:`MO (Manufacturing Order)` number for reference." -msgstr "" +msgstr ":guilabel:`설명`은 작업의 이름과 참조를 위한 :abbr:`MO (제조 주문)` 번호를 제공합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:308 msgid "The |ECO| :guilabel:`Type` is automatically assigned to `BOM Changes`." -msgstr "" +msgstr "|ECO| :guilabel:`유형`은 `BOM 변경`에 자동으로 할당됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:309 msgid "" @@ -22223,10 +22766,12 @@ msgid "" "automatically populated, based on the |BOM| used in the :abbr:`MO " "(Manufacturing Order)`." msgstr "" +":guilabel:`품목` 및 :guilabel:`BOM` 필드는 :abbr:`MO (제조주문)`에 사용된 |BOM|을 기준으로 자동으로" +" 채워집니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:311 msgid ":guilabel:`Responsible` is the operator who submitted the feedback." -msgstr "" +msgstr ":guilabel:`담당자`는 피드백을 제출한 운영자입니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:314 msgid "View ECO" @@ -22239,6 +22784,8 @@ msgid "" "Engineering Changes` button represents the amount of operational changes " "created from the tablet view." msgstr "" +"제안된 변경 사항을 검토하려면 :menuselection:`PLM 앱 --> 현황`으로 이동합니다. `BOM 업데이트` |ECO| 유형 " +"카드에서 :guilabel:`X 엔지니어링 변경` 버튼은 태블릿 보기에서 생성된 작업 변경의 수를 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:320 msgid "" @@ -22246,6 +22793,8 @@ msgid "" "view of the |ECO| type. To view the suggestion, select an |ECO| in the `New`" " stage." msgstr "" +":guilabel:`X 엔지니어링 변경` 버튼을 클릭하여 |ECO| 유형의 칸반 보기를 엽니다. 제안을 보려면 `신규` 단계에서 " +"|ECO|를 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:323 msgid "" @@ -22254,6 +22803,8 @@ msgid "" "button to navigate to the revised |BOM| and look into the proposed changes " "in greater detail." msgstr "" +"|ECO|의 :guilabel:`작업 변경` 탭에서 제안된 수정 사항의 요약을 검토합니다. :guilabel:`수정` 스마트 버튼을 " +"클릭하여 업데이트된 |BOM|으로 이동하고 제안된 변경 사항을 더 자세히 살펴봅니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:328 msgid "" @@ -22262,6 +22813,8 @@ msgid "" " the :abbr:`MO (Manufacturing Order)` `WH/MO/00010` for the product, " "`Keyboard`." msgstr "" +"한 작업자가 `키보드` 제품에 대해 `스위치 조립` 작업을 실행하는 동안 `abbr:`MO (제조 주문)` `WH/MO/00010` " +"단계를 추가하여 고장난 부품을 추가로 검사할 것을 제안했습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:332 msgid "" @@ -22269,6 +22822,8 @@ msgid "" "ECO type found in :menuselection:`PLM app --> Overview`. By default, |ECOs| " "created from tablet view are set to spawn in the `New` stage." msgstr "" +"그런 다음 생성된 |ECO|는 :menuselection:`PLM 앱 --> 현황`에서 `BOM 변경` ECO 유형으로 이동하여 액세스할" +" 수 있습니다. 태블릿 보기에서 생성된 |ECO|는 초기에는 기본적으로 `신규` 단계에 배치됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:336 msgid "" @@ -22276,10 +22831,12 @@ msgid "" "suggestion, allowing the employee revising the |BOM| to seek further " "clarification from the person who proposed the changes." msgstr "" +"제안을 한 작업자에게 :guilabel:`담당자` 필드가 지정되어 |BOM|을 수정하는 직원이 변경을 제안한 개인에게 추가 설명을 요청할" +" 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "Find the new ECO in the \"BOM Changes\" ECO type, in the *New* stage." -msgstr "" +msgstr "*신규* 단계의 \"BOM 변경\" ECO 유형에서 새로 생성된 ECO를 찾습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:344 msgid "" @@ -22289,10 +22846,13 @@ msgid "" "titled `New Step Suggestion:`, followed by the user-entered title. Click the" " line item to view the suggested changes." msgstr "" +"수정된 |BOM|으로 이동하여 :guilabel:`작업` 탭에 액세스합니다. 거기에서 :guilabel:`☰(가로줄 3개)` 아이콘을 " +"선택하면 작업 :guilabel:`단계` 목록이 표시됩니다. 이 단계 중 `새 단계 제안:`이라는 제목의 최신 지침이 사용자가 제공한 " +"제목과 함께 표시됩니다. 이 항목을 클릭하면 제안된 변경 사항을 검토할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 msgid "\"Show Instructions\" icon in the *Operations* tab of a BoM." -msgstr "" +msgstr "BoM의 *작업* 탭에서 \"지침 표시\" 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:353 msgid "" @@ -22300,12 +22860,14 @@ msgid "" "control-points>` form, ensure the following form fields are accurately " "filled out to give detailed instructions for operators:" msgstr "" +":ref:`품질 관리점<quality/quality_management/quality-control-points>`에 대한 양식에서 다음" +" 필드를 정확하게 작성하여 작업자를 위한 자세한 지침을 제공하세요:" #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:356 msgid "" ":guilabel:`Title`: rename to give a concise description of the new " "instruction." -msgstr "" +msgstr ":guilabel:`제목`: 새 지침에 대한 간결한 설명을 제공하려면 이 필드의 이름을 바꿉니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:357 msgid "" @@ -22314,6 +22876,8 @@ msgid "" "this :guilabel:`Operation` *only*, or a particular :guilabel:`Quantity` of " "the product." msgstr "" +":guilabel:`제어 기준`: 드롭다운 메뉴를 사용하여 이 지침이 전체 :guilabel:`품목`에 광범위하게 적용되는지, 이 " +":guilabel:`작업`*에만* 적용되는지, 아니면 제품의 특정 :guilabel:`수량`에 적용되는지 지정할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:360 msgid "" @@ -22324,6 +22888,10 @@ msgid "" "or other :ref:`quality check options <quality/quality_management/quality-" "control-points>`." msgstr "" +":guilabel:`유형`: 품질 관리점의 유형을 분류합니다. 드롭다운 메뉴에서 :guilabel:`지시`를 선택하여 작업자에게 자세한 " +"지침을 제공합니다. 작업자의 의견을 수집하려면 :guilabel:`사진 찍기`, :guilabel:`소모된 재료 등록`, " +":guilabel:`라벨 인쇄` 또는 기타 관련 :ref:`품질 점검 옵션 " +"<quality/quality_management/quality-control-points>` 등의 옵션을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:367 msgid "" @@ -22337,6 +22905,8 @@ msgid "" ":guilabel:`Steps` list using the breadcrumbs. Finally, drag the last quality" " control line item to its intended order of instructions." msgstr "" +"품질 관리점이 구성되면 사이트 이동 경로를 사용하여 :guilabel:`단계` 목록으로 돌아갑니다. 그런 다음 마지막 품질 관리 항목을 " +"지시 사항 순서에서 원하는 위치로 드래그합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:373 msgid "" @@ -22344,12 +22914,13 @@ msgid "" "and dragging its \"6 dots\" icon to move it from the bottom to the second " "position." msgstr "" +"\"점 6개\" 아이콘을 클릭하고 목록의 아래쪽에서 두 번째 위치로 이동하여 `손상된 스위치 확인` 지침을 드래그하고 순서를 변경합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 msgid "" "Drag and reorder instructions by selecting the \"6 dots\" icon on the far " "left." -msgstr "" +msgstr "맨 왼쪽의 \"점 6개\" 아이콘을 선택하여 지침을 드래그하고 순서를 변경합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:3 msgid "Version control" @@ -22362,6 +22933,9 @@ msgid "" "details, and past product design files while keeping the past details out of" " the production |BOM|." msgstr "" +"Odoo의 *제품 수명 주기 (PLM)*를 활용하여 과거 버전의 자재명세서 (BoM)를 효과적으로 관리하세요. 이 시스템을 사용하면 이전" +" 조립 지침, 부품 사양 및 이전 제품 설계 파일을 저장하는 동시에 이러한 과거 세부 정보를 현재 생산 |BOM|에서 제외할 수 " +"있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:14 msgid "" @@ -22369,6 +22943,8 @@ msgid "" "*PLM* to trace which |BOM| version was active on specific dates for recalls " "or customer complaints." msgstr "" +"필요에 따라 이전 |BOM| 버전으로 쉽게 되돌릴 수 있습니다. 또한 *PLM*을 활용하면 특정 날짜에 어떤 |BOM| 버전이 유효했는지" +" 정확하게 추적하여 리콜을 효율적으로 처리하거나 고객 불만을 처리할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:17 msgid "" @@ -22376,6 +22952,7 @@ msgid "" "organized testing and improvements without disrupting normal manufacturing " "operations." msgstr "" +"모든 |BOM| 버전은 정상적인 제조 운영을 방해하지 않고 체계적인 테스트와 개선을 위해 *설계 변경 주문*(ECO)에 저장됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:21 msgid ":ref:`Engineering change order <plm/eco>`" @@ -22393,16 +22970,19 @@ msgid "" ":guilabel:`Miscellaneous` tab, where the currently live :guilabel:`Version` " "of the |BOM| is displayed." msgstr "" +"생산에 사용되는 현재 버전의 |BOM|을 보려면 :menuselection:`PLM 앱 --> 마스터 데이터 --> BOM`으로 이동한 " +"다음 목록에서 원하는 |BOM|을 선택합니다. 그런 다음 :guilabel:`기타` 탭으로 전환하면 현재 |BOM|의 " +":guilabel:`버전`이 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:32 msgid "" "|BOMs| can also be accessed from :menuselection:`Manufacturing app --> " "Products --> Bill of Materials`." -msgstr "" +msgstr ":menuselection:`제조 앱 --> 품목 --> 자재명세서`에서도 |BOM|에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 msgid "Show the current version BOM in the Misc tab." -msgstr "" +msgstr "기타 탭에서 현재 버전 BOM을 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:40 msgid "Version history" @@ -22414,6 +22994,8 @@ msgid "" "navigating to :menuselection:`Manufacturing app --> Products --> Bills of " "Materials` and click the desired |BOM|." msgstr "" +"모든 과거, 현재 및 향후 버전의 |BOM|을 관리하려면 :menuselection:`제조 관리 앱 --> 품목 --> 자재명세서`로 " +"이동하여 원하는 |BOM|을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:45 msgid "" @@ -22421,16 +23003,18 @@ msgid "" "list view by selecting the :guilabel:`≣ (four horizontal lines)` icon on the" " top right corner." msgstr "" +"|BOM| 페이지에서 :guilabel:`ECO` 스마트 버튼을 클릭한 다음 오른쪽 상단의 :guilabel:`≣ (가로줄 4개)` " +"아이콘을 선택하여 목록 보기로 전환합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:49 msgid "" "The :guilabel:`ECO` smart button is visible on the |BOM| **only** if the " "*PLM* app is installed." -msgstr "" +msgstr ":guilabel:`ECO` 스마트 버튼은 *PLM* 앱이 설치된 경우 |BOM| **에만** 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 msgid "Show ECO smart button on a BoM." -msgstr "" +msgstr "BoM에 ECO 스마트 버튼 표시." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:55 msgid "" @@ -22438,6 +23022,8 @@ msgid "" "top, and click the :guilabel:`▼ (down arrow)` icon on the right to access a " "drop-down menu of :guilabel:`Filters`." msgstr "" +"제품에 대한 |ECO| 목록에서 상단의 검색창으로 이동하여 오른쪽의 :guilabel:`▼ (아래쪽 화살표)` 아이콘을 클릭하면 " +":guilabel:`필터`의 드롭다운 메뉴에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:58 msgid "" @@ -22445,16 +23031,18 @@ msgid "" " |BOM|, the :guilabel:`Responsible` user who applied the change, and the " ":guilabel:`Effective Date` of the |BOM|." msgstr "" +"다음으로 :guilabel:`완료` |ECO|로 필터링하여 |BOM|의 수정 내역, 변경 사항을 적용한 :guilabel:`담당자` " +"사용자, |BOM|의 :guilabel:`적용 날짜`를 확인합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:62 msgid "" "Click each |ECO| to view the past components, operations, and design files " "associated with the |BOM|." -msgstr "" +msgstr "각 |ECO|를 클릭하면 |BOM|에 연결된 구성품, 작업 및 디자인 파일의 과거 기록에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 msgid "Display ECO revision history for a BoM for a product." -msgstr "" +msgstr "제품의 BoM에 대한 ECO 변경 내역을 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:70 msgid "" @@ -22462,6 +23050,8 @@ msgid "" "date of the |ECO| is automatically set to :guilabel:`As soon as possible` " "and no dates are recorded in the revision history of the |BOM|." msgstr "" +":guilabel:`유효 날짜` 필드가 비어 있으면 |ECO|의 :guilabel:`유효` 날짜가 :guilabel:`가능한 한 빨리`로" +" 설정되어 있으며 |BOM|의 수정 내역에 특정 날짜가 기록되지 않았음을 의미합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 msgid "List of BOM effective dates." @@ -22473,6 +23063,8 @@ msgid "" "chatter, and hovering over the time the |ECO| was moved to the :ref:`closing" " stage <plm/eco/stage-config>`." msgstr "" +"채팅 섹션으로 이동한 다음 |ECO|가 :ref:`마감 단계 <plm/eco/stage-config>`로 이동한 시간을 나타내는 " +"타임스탬프 위로 마우스를 가져가면 |BOM|이 언제 라이브가 되었는지 확인할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:83 msgid "Design files" @@ -22482,7 +23074,7 @@ msgstr "디자인 파일" msgid "" "Attach computer-aided design (CAD) files, PDFs, images, or other design " "material to the |BOM| itself." -msgstr "" +msgstr "컴퓨터 지원 설계(CAD) 파일, PDF, 이미지 또는 기타 디자인 자료를 |BOM| 자체에 첨부합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:88 msgid "" @@ -22490,6 +23082,8 @@ msgid "" "Materials`, and select the desired |BOM|. On the |BOM|, navigate to the " "*chatter*, and click the :guilabel:`📎 (paperclip)` icon." msgstr "" +"이렇게 하려면 :menuselection:`PLM 앱 --> 마스터 데이터 --> 자재명세서`로 이동하여 원하는 |BOM|을 선택합니다." +" |BOM|에서 *대화 상자*로 이동하여 :guilabel:`📎 (종이 클립)` 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:92 msgid "" @@ -22497,10 +23091,12 @@ msgid "" "section. To add more design files, select the :guilabel:`Attach files` " "button." msgstr "" +"|BOM|과 관련된 파일은 :guilabel:`파일` 섹션에 표시됩니다. 디자인 파일을 더 추가하려면 :guilabel:`파일 첨부` " +"버튼을 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 msgid "Show paperclip icon in the chatter to attach files to a BoM." -msgstr "" +msgstr "채팅창에 클립 아이콘을 표시하여 BoM에 파일을 첨부할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:100 msgid "Manage design files in an ECO" @@ -22513,6 +23109,8 @@ msgid "" "Archived files are removed from the |BOM|, but are still accessible in the " "|ECO|." msgstr "" +"|ECO| 내에서 파일을 추가, 편집, 삭제할 수 있습니다. |ECO|가 승인되고 적용되면 새 파일은 자동으로 생산 |BOM|에 " +"연결됩니다. 보관된 파일은 |BOM|에서 제거되지만 |ECO|에서는 계속 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:106 msgid "" @@ -22521,6 +23119,8 @@ msgid "" "open the :guilabel:`Attachments` page by clicking the :guilabel:`Documents` " "smart button." msgstr "" +"|ECO| 내에서 설계 파일을 관리하려면 :menuselection:`PLM 앱 --> 변경`으로 이동하여 원하는 |ECO|를 " +"선택합니다. 그런 다음 :guilabel:`문서` 스마트 버튼을 클릭하여 :guilabel:`첨부파일` 페이지를 엽니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:110 msgid "" @@ -22530,6 +23130,10 @@ msgid "" "contained within the |ECO|, and will only apply to the production |BOM| once" " the :ref:`changes are applied <plm/eco/apply-changes>`." msgstr "" +"각 첨부 파일 위로 마우스를 가져가면 :guilabel:`︙(세로 점 3개)` 아이콘이 표시됩니다. 여기에서 파일을 " +":guilabel:`수정`, :guilabel:`제거` 또는 :guilabel:`다운로드`하도록 선택할 수 있습니다. 이러한 파일에 대한" +" 모든 수정 사항은 |ECO|에 포함되며 :ref:`변경 사항 적용 <plm/eco/apply-changes>` 후에만 생산 |BOM|에" +" 적용됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:116 msgid "" @@ -22537,10 +23141,12 @@ msgid "" "`100% keyboard` |BOM|. To replace the keyboard PDF, begin by selecting the " ":guilabel:`Documents` smart button." msgstr "" +"`60% 키보드 만들기` |ECO|에서 설계 파일은 원본 `100% 키보드` |BOM|에서 상속됩니다. 키보드 PDF를 대체하려면 " +":guilabel:`문서` 스마트 버튼을 클릭하여 시작하세요." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 msgid "Show *Documents* smart button from an active ECO." -msgstr "" +msgstr "활성 ECO에서 *문서* 스마트 버튼 표시." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:123 msgid "" @@ -22548,18 +23154,24 @@ msgid "" "manual.pdf` design file, and click the :guilabel:`︙ (three vertical dots)` " "icon. Then, click the :guilabel:`Remove` option to archive the file." msgstr "" +":guilabel:`첨부파일` 페이지에서 `100% 키보드 매뉴얼.pdf` 설계 파일 위로 마우스를 가져가서 " +":guilabel:`︙(세로점 3개)` 아이콘을 선택합니다. 거기에서 :guilabel:`제거` 옵션을 선택하여 파일을 보관합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:127 msgid "" "Next, on the same :guilabel:`Attachments` page, click the :guilabel:`Upload`" " button to upload the new design file, named `60% keyboard manual`." msgstr "" +"그런 다음 같은 :guilabel:`첨부파일` 페이지에서 :guilabel:`업로드` 버튼을 클릭하여 `60% 키보드 매뉴얼`이라는 " +"이름의 새 디자인 파일을 추가합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 msgid "" "View of *Attachments* page from the *Documents* smart button. Displays one archived and\n" "one newly added attachment." msgstr "" +"*문서* 스마트 버튼에서 액세스한 *첨부파일* 페이지를 표시합니다. 보관된 첨부파일 1개와\n" +"새로 추가된 첨부파일 1개가 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:136 msgid "" @@ -22567,6 +23179,8 @@ msgid "" "in the previous |ECO|, or as an archived file in the latest |ECO|, where the" " archival occurred." msgstr "" +"보관된 파일은 **영구적으로 삭제**되지 않으며, 보관된 파일은 이전 |ECO|에서 계속 액세스하거나 보관이 발생한 최신 |ECO|에서 " +"보관된 파일로 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:140 msgid "Apply rebase" @@ -22576,7 +23190,7 @@ msgstr "리베이스 적용" msgid "" "Odoo simplifies merge conflict resolution for concurrent |ECOs| on the same " "product." -msgstr "" +msgstr "Odoo는 동일한 제품에 영향을 미치는 동시 |ECO|로 인해 발생할 수 있는 병합 충돌 해결을 간소화합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:144 msgid "" @@ -22585,12 +23199,14 @@ msgid "" " production |BOMs| are displayed in the :guilabel:`Previous Eco Bom Changes`" " tab, visible only in this scenario." msgstr "" +"생산 |BOM|이 이전 버전을 수정하는 다른 |ECO|와 동시에 업데이트될 때 충돌이 발생할 수 있습니다. 새 버전과 이전 버전 사이의 " +"이러한 불일치는 :guilabel:`이전 Eco Bom 변경` 탭에 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:148 msgid "" "To resolve conflicts and retain |ECO| changes, click the :guilabel:`Apply " "Rebase` button." -msgstr "" +msgstr "충돌을 해결하고 |ECO| 변경 사항을 유지하려면 :guilabel:`리베이스 적용` 버튼을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:151 msgid "" @@ -22599,10 +23215,12 @@ msgid "" " and the changes are applied. This means the current |BOM| version has " "become `6`." msgstr "" +"현재 |BOM| 버전이 `5`인 경우, `ECO0011`과 `ECO0012`라는 두 개의 |ECO|가 생성됩니다. `ECO0011`에서는" +" `스페이스 스태빌라이저`라는 새로운 부품이 추가되어 변경된 내용이 적용됩니다. 따라서 현재 버전의 |BOM|은 `6`으로 전환됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 msgid "Apply changes to an ECO to update the production BOM." -msgstr "" +msgstr "ECO에 변경 사항을 적용하여 생산 BOM을 업데이트합니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:159 msgid "" @@ -22610,6 +23228,8 @@ msgid "" ":guilabel:`Previous Eco Bom Changes` tab, the |BOM| is missing the `Space " "stabilizer`." msgstr "" +"이는 `ECO0012`가 예전 |BOM|을 수정하고 있음을 나타냅니다. guilabel:`이전 Eco Bom 변경` 탭에 표시된 것처럼," +" |BOM|에는 `스페이스 스태빌라이저`가 포함되어 있지 않습니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:162 msgid "" @@ -22618,12 +23238,14 @@ msgid "" "previous |ECO| changes, without affecting the changes already made to " "`ECO0012`." msgstr "" +"`ECO0011`의 수정 사항을 유지하면서 `ECO0012`의 변경 사항을 통합하려면 :guilabel:`리베이스 적용` 버튼을 " +"선택합니다. 이렇게 하면 `ECO0012`에 이미 적용된 변경 사항이 영향 받지 않고 이전 |ECO| 조정 사항이 통합됩니다." #: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 msgid "" "Click the *Apply Rebase* button to update the BOM to match the production " "BOM." -msgstr "" +msgstr "*리베이스 적용* 버튼을 클릭하여 생산 BOM과 일치하도록 BOM을 업데이트합니다." #: ../../content/applications/inventory_and_mrp/plm/management.rst:3 msgid "Project management" @@ -22641,6 +23263,9 @@ msgid "" "Approvals ensure reviews by team members, which prevents mistakes and " "premature actions." msgstr "" +"현재 검토 중인 :ref:`설계 변경 주문 <PLM/ECO>` (ECO) 단계에 승인자를 지정하여 이해관계자 및 관리자에게 자동으로 " +"알림을 보냅니다. 변경 사항은 지정된 승인자가 승인한 후에만 적용됩니다. 이 승인 프로세스는 팀원의 철저한 검토를 보장하여 오류와 성급한" +" 조치를 최소화합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:16 msgid ":ref:`Stage configuration <plm/eco/stage-config>`" @@ -22655,6 +23280,8 @@ msgid "" "To add an approver, first go to the :menuselection:`PLM app`, and click on " "the project card of an ECO type to open the Gantt view of the |ECOs|." msgstr "" +"승인자를 지정하려면 먼저 :menuselection:`PLM 앱`에 액세스한 다음 ECO 유형에 해당하는 프로젝트 카드를 선택하여 " +"|ECO|의 간트 보기를 엽니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:24 msgid "" @@ -22662,6 +23289,8 @@ msgid "" "stage, and select the :guilabel:`⚙️ (gear)` icon. Then, click " ":guilabel:`Edit` to open a pop-up window." msgstr "" +":guilabel:`설계 변경 주문` 페이지에서 원하는 단계 위로 마우스를 가져간 다음 :guilabel:`⚙️(기어)` 아이콘을 " +"선택합니다. 그런 다음 :guilabel:`편집`을 클릭하여 팝업 창을 엽니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:28 msgid "" @@ -22670,12 +23299,14 @@ msgid "" "where |ECOs| are applied, and the :abbr:`BoM (Bill of Materials)` version is" " updated." msgstr "" +"승인자는 어느 단계에나 추가할 수 있지만 |ECO|가 적용되고 :abbr:`BoM (자재명세서)` 버전이 업데이트되는 *마감* 단계 " +"이전에 오는 *승인* 단계에 지정하는 것이 좋습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:32 msgid "" "See the documentation about :ref:`stage types <plm/eco/stage-config>` for " "more information." -msgstr "" +msgstr "자세한 내용은 :ref:`단계 유형 <plm/eco/stage-config>`에 대한 문서를 참조하세요." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:36 msgid "" @@ -22685,6 +23316,9 @@ msgid "" "Manager`, `Quality Team`, etc.), and select the relevant :guilabel:`User` " "from the drop-down menu." msgstr "" +":guilabel:`편집` 단계 팝업 창에서 :guilabel:`승인` 아래에 있는 :guilabel:`항목 추가` 버튼을 클릭합니다. " +"그런 다음 :guilabel:`역할` 아래에 승인자의 직위 또는 직책을 입력하고 (예: `엔지니어링 매니저`, `품질관리 팀` 등), " +"드롭다운 메뉴에서 적절한 :guilabel:`사용자`를 선택합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:41 msgid "" @@ -22692,12 +23326,15 @@ msgid "" "approve`, :guilabel:`Approves, but the approval is optional`, or " ":guilabel:`Comments only`." msgstr "" +"다음으로 :guilabel:`승인 유형`을 :guilabel:`승인 필요`, :guilabel:`승인, 승인 여부는 선택사항` 또는 " +":guilabel:`댓글만`으로 설정합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:45 msgid "" "Assign the `CTO`, \"Mitchell Admin,\" as a required approver for |ECOs| in " "the `Validated` stage in the `New Product Introduction` ECO type." msgstr "" +"`신제품 도입` ECO 유형의 `승인` 단계에서 \"Mitchell 관리자\"인 `CTO`를 |ECO|에 대한 필수 승인자로 지정합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:48 msgid "" @@ -22706,12 +23343,15 @@ msgid "" ":guilabel:`Approves, but the approval is optional` and :guilabel:`Comments " "only`, respectively." msgstr "" +"품질 및 마케팅 팀의 :guilabel:`승인 유형`이 각각 :guilabel:`승인, 승인 여부는 선택사항`과 " +":guilabel:`댓글만`으로 설정되어 있으므로 |ECO|에 변경 사항을 적용하는 데 품질 및 마케팅 팀의 승인은 필요하지 " +"**않습니다.**" #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 msgid "" "Set an approver that \"Is required to approve\" ECOs in the \"Validated\" " "stage." -msgstr "" +msgstr "\"승인\" 단계에서 승인자를 \"승인 필요\"로 설정합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:57 msgid "Manage approvals" @@ -22723,10 +23363,12 @@ msgid "" ":menuselection:`PLM app`, and looking at the card for an ECO type, which " "shows the count of open tasks assigned to them." msgstr "" +"승인자는 :menuselection:`PLM 앱`으로 이동하여 자신에게 할당된 미결 작업의 수를 표시하는 ECO 유형의 카드를 확인하고 " +"할 일 승인을 쉽게 추적할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:62 msgid "Here's what each button on an ECO project card does:" -msgstr "" +msgstr "ECO 프로젝트 카드의 각 버튼은 다음과 같은 기능을 수행합니다:" #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:64 msgid "" @@ -22734,6 +23376,8 @@ msgid "" " |ECOs| of this ECO type. Clicking the button opens the Gantt view of the " ":guilabel:`Engineering Change Orders` page." msgstr "" +":guilabel:`# 엔지니어링 변경` 버튼은 이 ECO 유형의 진행 중인 |ECO| 개수를 표시합니다. 버튼을 클릭하면 " +":guilabel:`엔지니어링 변경 주문` 페이지의 간트 보기가 열립니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:66 msgid "" @@ -22741,6 +23385,8 @@ msgid "" "accept or reject. Clicking on this button displays |ECOs| pending approval " "or rejected (marked with the red :guilabel:`Blocked` state)." msgstr "" +":guilabel:`내 승인`에는 승인자가 수락하거나 거부해야 하는 |ECO|의 수를 나타냅니다. 이 버튼을 클릭하면 승인 대기 중이거나" +" 거부된 |ECO|가 표시됩니다. (빨간색 :guilabel:`차단됨` 상태로 표시)" #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:69 msgid "" @@ -22748,6 +23394,8 @@ msgid "" "approval or rejected by any approver. Clicking it reveals these pending " "|ECOs|." msgstr "" +":guilabel:`모든 유효성 검사` 버튼은 승인을 대기 중이거나 승인자가 거부한 |ECO|의 수를 나타냅니다. 이 버튼을 클릭하면 " +"보류 중인 |ECO| 목록이 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:71 msgid "" @@ -22755,6 +23403,8 @@ msgid "" "apply changes. Clicking on the button displays all the |ECOs| to approve, " "and apply changes to, in the verification stage." msgstr "" +":guilabel:`적용 대상` 버튼은 사용자가 변경 사항을 적용해야 하는 |ECO|의 수를 나타냅니다. 이 버튼을 클릭하면 확인 " +"단계에서 승인하고 변경 사항을 적용할 모든 |ECO|가 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:75 msgid "" @@ -22762,12 +23412,14 @@ msgid "" "approved, and the user just needs to click on the |ECO| to enter the form " "view, and click the :guilabel:`Apply Changes` button." msgstr "" +"녹색 :guilabel:`완료` 단계로 표시된 |ECO|는 이미 승인된 상태이며, 사용자는 해당 |ECO|를 클릭하여 양식 보기로 들어간" +" 다음 :guilabel:`변경사항 적용` 버튼을 클릭하기만 하면 됩니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 msgid "" "Display count of validations to-do and buttons to open filtered list of " "ECOs." -msgstr "" +msgstr "승인된 할 일의 수를 표시하고 필터링된 ECO 목록을 여는 버튼을 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:84 msgid "Approve ECOs" @@ -22779,6 +23431,8 @@ msgid "" "assigned approver, to see the :guilabel:`Approve`, :guilabel:`Reject`, and " ":guilabel:`Apply Changes` buttons." msgstr "" +"지정된 승인자로 로그인한 상태에서 확인 단계의 |ECO|로 이동하여 :guilabel:`승인`, :guilabel:`거부` 및 " +":guilabel:`변경사항 적용` 버튼을 찾습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:89 msgid "" @@ -22786,6 +23440,8 @@ msgid "" "(Bill of Materials)`, click :guilabel:`Approve`, and then :guilabel:`Apply " "Changes`." msgstr "" +"|ECO|를 승인하고 변경 사항을 생산 :abbr:`BoM (자재명세서)`에 적용하려면 :guilabel:`승인`을 클릭한 다음 " +":guilabel:`변경 사항 적용`을 클릭합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:92 msgid "" @@ -22793,6 +23449,8 @@ msgid "" ":guilabel:`Approve` button was clicked first. Additionally, the chatter logs" " the history of the clicked buttons." msgstr "" +":guilabel:`변경사항 적용` 버튼은 :guilabel:`승인` 버튼을 먼저 클릭한 경우에**만** 작동합니다. 클릭한 버튼의 " +"이력도 대화 로그에 기록됩니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:96 msgid "" @@ -22802,6 +23460,9 @@ msgid "" ":guilabel:`Apply Changes` button **will work** without requiring the " ":guilabel:`Approve` button to be clicked first." msgstr "" +":guilabel:`승인 유형`이 :guilabel:`승인 필요`로 설정되어 있지 않은 경우 :guilabel:`변경 사항 적용` " +"버튼으로 수정을 적용하기 전에 관련 사용자의 승인이 필요하지 않습니다. 따라서 :guilabel:`변경사항 적용` 버튼을 먼저 클릭하지 " +"않아도 :guilabel:`승인` 버튼이 **작동**합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:102 msgid "Automated activities" @@ -22814,6 +23475,8 @@ msgid "" "receive a notification in their activities inbox, accessible through the " ":guilabel:`🕘 (clock)` icon at the top of the page." msgstr "" +"|ECO|가 확인 단계로 이동하면 지정된 승인자가 |ECO|를 검토할 수 있도록 계획된 활동이 자동으로 만들어집니다. 승인자는 활동 받은" +" 편지함으로 알림을 받게 되며, 페이지 상단의 :guilabel:`🕘(시계)` 아이콘을 통해 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:108 msgid "" @@ -22822,6 +23485,9 @@ msgid "" ":guilabel:`Today`, and :guilabel:`Future`. Clicking on each of these buttons" " shows a filtered Gantt view of the respective |ECOs|." msgstr "" +"할 일 작업 목록에서 :guilabel:`ECO (엔지니어링 변경 주문)` 알림에는 :guilabel:`지연`, " +":guilabel:`오늘` 및 :guilabel:`예정`으로 표시된 활동의 수가 보여집니다. 이러한 각 버튼을 클릭하면 각각의 " +"|ECO|에 대한 필터링된 간트 보기가 표시됩니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:113 msgid "" @@ -22829,10 +23495,12 @@ msgid "" "icon, with `5` |ECOs| pending approval :guilabel:`Today`. Currently, there " "are `0` :guilabel:`Late` or :guilabel:`Future` |ECOs|." msgstr "" +"예약된 활동은 :guilabel:`🕘 (시계)` 아이콘에 숫자로 표시되며, `5`개의 |ECO|가 :guilabel:`오늘` 승인되기를 " +"기다리고 있습니다. 현재 :guilabel:`지연` 또는 :guilabel:`예정`으로 표시된 |ECO|는 `0`개 입니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 msgid "Show scheduled approvals notifications for the user." -msgstr "" +msgstr "사용자에 대한 예약된 승인 알림을 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:121 msgid "" @@ -22842,10 +23510,13 @@ msgid "" ":guilabel:`Created` date, the approver :guilabel:`Assigned to` it, and the " "due date." msgstr "" +"보류 중인 |ECO|를 클릭하면 :guilabel:`ECO 승인`에 대한 *계획된 활동*이 생성되며, 이는 채팅창에 문서화됩니다. " +":guilabel:`i (정보)` 아이콘을 클릭하면 결재의 :guilabel:`생성` 날짜, :guilabel:`지정된` 승인자, 마감일" +" 등의 추가 세부 정보에 액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 msgid "Show additional details of the planned ECO approval." -msgstr "" +msgstr "예정된 ECO 승인에 대한 추가 세부 정보를 표시합니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:130 msgid "Follow-up activities" @@ -22857,6 +23528,8 @@ msgid "" "required modifications before |ECO| approval. To create tasks with " "deadlines, navigate to the rejected |ECO| form, and go to the chatter." msgstr "" +"|ECO|가 거부된 경우, 프로젝트 구성원에게 필요한 수정 작업을 할당하여 |ECO| 승인 전에 수정해야 합니다. 마감일이 있는 작업을 " +"만들려면 거부된 |ECO| 양식으로 이동한 다음 채팅으로 진행하세요." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:136 msgid "" @@ -22864,12 +23537,16 @@ msgid "" "Activities` section of the chatter to close the activity, and open a pop-up " "window for creating tasks." msgstr "" +"채팅의 :guilabel:`계획된 활동` 섹션에서 :guilabel:`완료 표시` 버튼을 선택하여 활동을 닫고 작업을 만들기 위한 팝업 " +"창을 엽니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 msgid "" "Show *Mark Done* window to show *Done & Schedule Next*, *Done*, and *Discard* buttons to\n" "close the planned activity." msgstr "" +"*완료 표시* 창을 표시하여 *완료 및 다음 일정 예약*, *완료* 및 *삭제* 버튼과 같은 옵션을 표시하여\n" +"계획된 활동을 닫습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:144 msgid "" @@ -22880,6 +23557,10 @@ msgid "" "field and the text box. Click the :guilabel:`Schedule` button to close the " "window." msgstr "" +":guilabel:`완료 표시` 창에서 :guilabel:`완료 및 다음 일정 예약`을 클릭하여 새 :guilabel:`활동 예약` 창을" +" 엽니다. 그런 다음 :guilabel:`할당 대상`에서 팀원에게 작업을 할당하고 완료할 :guilabel:`마감일`을 설정합니다. " +":guilabel:`요약` 필드와 텍스트 상자에 작업 세부 정보를 입력합니다. 마지막으로 :guilabel:`스케줄` 버튼을 클릭하여 " +"창을 닫습니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:149 msgid "" @@ -22888,6 +23569,8 @@ msgid "" "returns the |ECO| to the verification stage, a new :guilabel:`ECO Approval` " "task is created for the approver." msgstr "" +"창을 닫은 후, |ECO| 양식에서 |ECO|를 한 단계 뒤로 이동합니다. 이렇게 하면 팀원이 변경을 완료하고 |ECO|를 확인 단계로 " +"되돌리면 승인자에 대한 새 :guilabel:`ECO 승인` 작업이 자동으로 만들어집니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:154 msgid "" @@ -22896,10 +23579,13 @@ msgid "" "to :guilabel:`Accept` the |ECO|. Clicking the :guilabel:`Schedule` button " "creates a planned activity for Laurie due on `08/15/2023`." msgstr "" +"승인자는 |ECO|의 :guilabel:`담당자`인 `Laurie Poiret`에 대한 활동을 생성하여 승인자가 |ECO|를 " +"`guilabel:`수락`하는 데 필요한 변경 사항을 자세히 설명합니다. :guilabel:`스케줄` 버튼을 클릭하면 마감일이 " +"`08/15/2023`인 Laurie에 대한 계획된 활동이 만들어집니다." #: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 msgid "Create a scheduled activity for follow-up changes to a rejected ECO." -msgstr "" +msgstr "거부된 ECO에 대한 후속 변경을 위해 예약된 활동을 만듭니다." #: ../../content/applications/inventory_and_mrp/purchase.rst:8 msgid "Purchase" @@ -22911,6 +23597,8 @@ msgid "" "purchase orders. Learn how to monitor purchase tender, automate " "replenishment, and follow up on your orders." msgstr "" +"구매 계약서, 견적서, 발주서를 추적하는 데 **Odoo 매입** 앱이 도움이 됩니다. 구매 입찰을 감독하고, 보충을 자동화하고, 주문을" +" 효과적으로 모니터링하는 방법을 알아보세요." #: ../../content/applications/inventory_and_mrp/purchase.rst:14 msgid "`Odoo Tutorials: Purchase <https://www.odoo.com/slides/purchase-23>`_" @@ -22932,6 +23620,9 @@ msgid "" "your business is dependent on particular vendors, and the data can help you " "negotiate discounts on prices." msgstr "" +"회사에서 정기적으로 제품을 구매하는 경우 성과를 모니터링하고 분석해야 할 이유는 많습니다. 수집된 인사이트는 향후 주문을 더 잘 예측하고" +" 계획하는 데 도움이 될 수 있습니다. 예를 들어, 특정 공급업체에 대한 의존도를 평가하여 데이터를 활용하여 가격 할인을 협상할 수 " +"있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:11 msgid "Generate customized reports" @@ -22945,6 +23636,8 @@ msgid "" "presenting the untaxed amount of your purchase orders per day, and below it," " key metrics and a pivot table." msgstr "" +"구매 분석에 액세스하려면 *보고*로 이동하세요. 보고 대시보드에 액세스하기만 하면 실제 실적에 대한 간략한 개요를 확인할 수 있습니다. " +"기본 보기에는 일일 구매 주문의 비과세 금액을 나타내는 꺾은선형 차트와 함께 주요 지표 및 피벗 테이블이 아래에 표시됩니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 msgid "Reporting dashboard in Odoo Purchase" @@ -22954,11 +23647,11 @@ msgstr "Odoo 구매 대시보드 보고" msgid "" "While the data initially presented is useful, there are several tools and " "features you can use to get even more insights on your purchases." -msgstr "" +msgstr "제공되는 초기 데이터도 유용하지만, 구매 인사이트를 더 깊이 파고들 수 있는 다양한 도구와 기능을 사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:26 msgid "Use filters to select the data you need" -msgstr "" +msgstr "필터를 사용하여 필요한 데이터 선택" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:28 msgid "" @@ -22968,6 +23661,9 @@ msgid "" "the chart, key metrics, and pivot table with the data. The pre-configured " "filters are:" msgstr "" +"Odoo는 *필터*를 클릭하여 활용하고 조합할 수 있는 다양한 기본 필터를 제공합니다. 하나 이상의 필터를 선택하면 Odoo는 선택한 " +"기준 중 하나 이상을 충족하는 모든 주문을 검색하여 차트, 주요 지표 및 피벗 테이블을 관련 데이터로 채웁니다. 사전 설정된 필터에는 " +"다음이 포함됩니다:" #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:33 msgid "All *Requests for Quotation*" @@ -22981,25 +23677,26 @@ msgstr "취소된 주문을 제외한 모든 *구매 주문 *" msgid "" "*Confirmation Date Last Year* includes all orders that were confirmed the " "previous year, canceled purchase orders included" -msgstr "" +msgstr "*전년도 확정일*에는 취소된 구매 주문을 포함하여 전년도에 확정된 모든 주문이 포함됩니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:40 msgid "" "*Order Date* includes all orders - request for quotations and purchases " "orders (canceled ones included) - depending on their date of creation" -msgstr "" +msgstr "*주문 날짜*에는 생성 날짜를 기준으로 견적 요청 및 구매 주문 (취소된 주문 포함)을 포함한 모든 주문이 포함됩니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:43 msgid "" "*Confirmation Date* includes all confirmed orders, canceled ones included, " "depending on their date of confirmation" -msgstr "" +msgstr "*확정일*에는 확정일을 기준으로 취소된 주문을 포함한 모든 확정 주문이 포함됩니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:47 msgid "" "When you have to select a period, you can use multiple years, and, with at " "least one year selected, multiple quarters and the three most recent months." msgstr "" +"기간을 선택할 때 여러 연도를 선택할 수 있으며, 최소 1년을 선택한 경우 여러 분기 및 가장 최근 3개월을 선택할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 msgid "" @@ -23007,6 +23704,8 @@ msgid "" " feature appears next to *Filters*. It enables you to compare the period you" " filtered with the previous one." msgstr "" +"*주문 날짜* 또는 *확정 날짜* 필터를 사용하는 경우 *비교* 기능이 *필터* 옆에 나타납니다. 이를 통해 필터링한 기간을 이전 기간과" +" 비교할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 msgid "Reporting filters in Odoo Purchase" @@ -23044,6 +23743,9 @@ msgid "" "customized search filter can then be accessed by clicking on *Favorites* or " "can even be set as the default filter when you open the reporting dashboard." msgstr "" +"사용자 지정 필터를 반복해서 다시 만들 필요가 없도록 하려면 :menuselection:`즐겨찾기 --> 현재 검색 저장 --> " +"저장`으로 이동하여 사용자 지정 필터를 저장하세요. 그런 다음 *즐겨찾기*를 클릭하여 사용자 지정 검색 필터에 액세스하거나 보고 " +"대시보드를 열 때 기본 필터로 설정할 수도 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:80 msgid "Measure exactly what you need" @@ -23057,6 +23759,9 @@ msgid "" "both views. You can access each view separately by clicking on the icons at " "the top right of the dashboard." msgstr "" +"측정 항목을 선택하기 전에 그래프 보기를 사용할지 피벗 보기를 사용할지 결정해야 합니다. 기본적으로 대시보드에는 두 보기가 모두 " +"표시되지만 선택한 측정값이 두 보기에 동시에 적용되지는 않습니다. 대시보드의 오른쪽 상단에 있는 아이콘을 클릭하여 각 보기에 개별적으로 " +"액세스할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 msgid "Switch reporting view in Odoo Purchase" @@ -23073,6 +23778,9 @@ msgid "" "but you can only use one at a time. However, you can group the measure using" " one or several of the 19 *Groups*." msgstr "" +"클릭 한 번으로 막대형, 선형 또는 파이의 세 가지 차트 유형 중에서 선택하여 기본 그래프를 변형할 수 있습니다. 14가지 측정값을 " +"사용할 수 있지만 한 번에 하나의 측정값만 사용할 수 있습니다. 그러나 사용 가능한 19개의 *그룹* 중 하나 또는 여러 개를 사용하여 " +"측정값을 그룹화할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 msgid "Reporting graph view in Odoo Purchase" @@ -23086,6 +23794,9 @@ msgid "" "bar chart. For pie charts, the more groups you select, the more slices are " "displayed." msgstr "" +"막대형 차트 및 꺾은선형 차트에서는 선택한 측정값이 Y축이 되고, 처음 선택한 그룹이 X축을 만드는 데 사용됩니다. 그룹을 더 추가하면 " +"선 (꺾은선형 차트)이 추가되거나 막대형 차트가 누적 막대형 차트로 변환됩니다. 원형 차트의 경우 그룹을 더 많이 선택하면 더 많은 " +"슬라이스가 표시됩니다." #: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:108 msgid "Explore your data" @@ -23114,7 +23825,7 @@ msgstr "Odoo 구매에서 피벗 테이블 보기" msgid "" "You can insert your pivot table's data directly in the Spreadsheet app or " "export it as an Excel file." -msgstr "" +msgstr "피벗 테이블의 데이터를 스프레드시트 앱에 직접 삽입하거나 Excel 파일로 내보낼 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals.rst:5 msgid "Manage deals" @@ -23122,7 +23833,7 @@ msgstr "거래 관리" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:3 msgid "Use blanket orders to create purchase agreements with vendors" -msgstr "" +msgstr "포괄 주문을 사용하여 공급업체와 구매 계약서 작성하기" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:5 msgid "" @@ -23131,6 +23842,8 @@ msgid "" "Using blanket orders are useful when products are always purchased from the " "same vendor, but in different quantities at different times." msgstr "" +"포괄 주문은 회사와 공급업체 간의 장기 계약으로, 미리 정해진 가격으로 반복적으로 제품을 배송할 수 있도록 보장합니다. 특히 동일한 " +"공급업체로부터 지속적으로 제품을 구매하지만 시기마다 다른 수량을 구매할 때 유용합니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:9 msgid "" @@ -23138,6 +23851,8 @@ msgid "" " also save money, since they can be advantageous when negotiating bulk " "pricing with vendors." msgstr "" +"일괄 주문은 주문 프로세스를 간소화하여 시간을 절약할 뿐만 아니라 공급업체와 대량 가격 협상을 할 때 유리하여 전반적인 비용 효율성에 " +"기여합니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:13 msgid ":doc:`calls_for_tenders`" @@ -23156,10 +23871,13 @@ msgid "" "Agreements`. Doing so will enable the ability to create blanket orders, as " "well as alternative requests for quotation (RFQs)." msgstr "" +"포괄 주문을 설정하려면 먼저 *구매* 앱의 설정에서 *구매 계약* 기능을 활성화합니다. :menuselection:`구매 --> 설정 " +"--> 환경설정`으로 이동한 다음 :guilabel:`주문` 섹션 아래에서 :guilabel:`구매 계약` 옆의 확인란을 선택합니다. 이" +" 작업을 수행하면 포괄 주문 및 대체 견적 요청 (RFQ)을 생성할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 msgid "Purchase Agreements enabled in the Purshase app settings." -msgstr "" +msgstr "매입 앱 설정에서 구매 계약을 사용하도록 설정합니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:28 msgid "" @@ -23167,6 +23885,8 @@ msgid "" "blanket orders`, and click :guilabel:`New`. This creates (and navigates to) " "a new blanket order form." msgstr "" +"포괄 주문을 생성하려면 :menuselection:`구매 --> 주문 --> 포괄 주문`으로 이동한 다음 :guilabel:`생성` 또는" +" :guilabel:`신규`를 클릭합니다. 이 작업을 수행하면 새 양식이 열리고 묶음 주문을 생성합니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:31 msgid "" @@ -23174,6 +23894,7 @@ msgid "" "configured, so there are pre-determined rules that the recurring long-term " "agreement must follow:" msgstr "" +"이 새로운 포괄 주문 양식에서 다양한 필드와 설정을 구성하여 반복 장기 계약이 따라야 하는 미리 정해진 규칙을 설정할 수 있습니다:" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:34 msgid "" @@ -23181,6 +23902,8 @@ msgid "" "blanket order. By default, this is the user who created the agreement; the " "user can be changed directly from the drop-down menu next to this field." msgstr "" +":guilabel:`구매 담당자`: 이 특정 포괄 주문에 할당된 사용자입니다. 기본적으로 계약을 생성한 사용자이지만, 이 필드 옆의 " +"드롭다운 메뉴에서 직접 사용자를 변경할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:37 msgid "" @@ -23188,6 +23911,8 @@ msgid "" "order is classified as. In Odoo, blanket orders are the only official " "purchase agreement." msgstr "" +":guilabel:`계약 유형`: 이 포괄 주문이 분류된 구매 계약의 유형을 나타냅니다. Odoo에서는 포괄 주문이 유일한 공식 구매 " +"계약 유형입니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:39 msgid "" @@ -23195,6 +23920,8 @@ msgid "" "once or on a recurring basis. The vendor can be selected directly from the " "drop-down menu next to this field." msgstr "" +":guilabel:`공급업체`: 단일 구매 또는 반복 구매에 대해 이 계약이 묶여 있는 공급업체를 나타냅니다. 공급업체는 이 필드 옆의 " +"드롭다운 메뉴에서 직접 선택할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:41 msgid "" @@ -23202,6 +23929,8 @@ msgid "" " exchange. If multiple currencies have been activated in the database, the " "currency can be changed from the drop-down menu next to this field." msgstr "" +":guilabel:`통화`: 이 거래에 사용하기로 합의한 통화입니다. 데이터베이스에서 여러 통화가 활성화된 경우 이 필드 옆의 드롭다운 " +"메뉴에서 통화를 변경할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:44 msgid "" @@ -23209,6 +23938,8 @@ msgid "" "will be set to expire on (if desired). If this blanket order should not " "expire, leave this field blank." msgstr "" +":guilabel:`계약 마감일`: 해당되는 경우 구매 계약이 만료되는 날짜를 나타냅니다. 포괄 주문에 만료일이 없어야 하는 경우 이 " +"필드를 비워둘 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:46 msgid "" @@ -23217,6 +23948,8 @@ msgid "" "form. If a new quotation is created, this value will automatically populate " "the *Order Deadline* field on the :abbr:`RFQ (Request for Quotation)`." msgstr "" +":guilabel:`주문 날짜`: 포괄 주문 양식에서 직접 새 견적을 생성하는 경우 이 포괄 주문이 예정된 날짜를 나타냅니다. 새 견적이" +" 생성되면 이 값은 :abbr:`견적요청서 (RFQ)`의 *주문 마감일* 필드에 자동으로 채워집니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:50 msgid "" @@ -23226,6 +23959,8 @@ msgid "" "created, this value will automatically populate the *Expected Arrival* field" " on the :abbr:`RFQ (Request for Quotation)`." msgstr "" +":guilabel:`배송 날짜`: 이 필드는 포괄 주문 양식에서 직접 생성된 :abbr:`견적 요청서 (RFQ)`에 포함된 제품의 예상 " +"배송 날짜를 나타냅니다. 새 견적이 생성되면 이 값은 :abbr:`견적 요청서 (RFQ)`의 *예정 도착* 필드에 자동으로 채워집니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:54 msgid "" @@ -23302,6 +24037,8 @@ msgid "" "purchase agreeement can be changed next to the :guilabel:`Lines` and " ":guilabel:`Quantities` fields." msgstr "" +":guilabel:`새 견적에 대한 데이터` 섹션에서 이 구매 계약을 사용하는 새 견적에 제품 라인 및 수량이 채워지는 방식을 조정할 수" +" 있습니다. 이는 :guilabel:`항목` 및 :guilabel:`수량` 필드 옆에서 변경할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 msgid "Purchase Agreement type edit screen for blanket orders." @@ -23484,6 +24221,11 @@ msgid "" " used to determine where, when, and for what price this product could be " "replenished." msgstr "" +"일괄 주문이 확인되면 :abbr:`BO (일괄 주문)`에 나열된 제품에 대한 새 공급업체 라인이 :guilabel:`구매` 탭 아래에 " +"추가됩니다. 이 기능은 특히 :doc:`자동 보충 <../../purchase/products/reordering>`에서 일괄 주문의 " +"유용성을 향상시킵니다. 공급업체 라인에는 참조 역할을 하는 :guilabel:`공급업체`, :guilabel:`가격`, " +":guilabel:`계약`과 같은 중요한 세부 정보가 포함됩니다. 이 정보는 제품을 언제, 어디서, 어떤 가격으로 보충할 수 있는지 " +"결정하는 데 중요한 역할을 합니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 msgid "Product form with replenishment agreement linked to blanket order." @@ -23537,6 +24279,10 @@ msgid "" ":abbr:`RFQs (Requests for Quotation)`, as well as the ability to create " "*blanket orders*." msgstr "" +"견적서에서 바로 대체 :abbr:`견적요청서(RFQ)`를 생성하려면 먼저 *매입* 앱의 설정에서 *구매 계약* 기능을 활성화해야 합니다." +" 이렇게 하려면 :menuselection:`매입 --> 설정 --> 환경설정`으로 이동한 다음 :guilabel:`주문` 섹션에서 " +":guilabel:`구매 계약` 옆의 확인란을 클릭합니다. 이렇게 하면 대체 :abbr:`견적요청서(RFQ)`를 생성할 수 있을 뿐만 " +"아니라 *포괄 주문*을 생성하는 옵션도 사용할 수 있습니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 msgid "Purchase Agreements enabled in the Purchase app settings." @@ -23817,6 +24563,9 @@ msgid "" "purchase order form in which that product was included, its ordered quantity" " is changed to **0**, as well." msgstr "" +"주문 항목 비교 페이지에서 품목을 제거하려면 해당 품목 행의 맨 오른쪽 끝에 있는 :guilabel:`지우기`를 클릭합니다. 이 작업을 " +"수행하면 페이지에서 해당 제품이 사용 가능한 옵션에서 제거되고 제품의 :guilabel:`합계` 가격이 **0**로 재설정됩니다. 동시에" +" 해당 제품이 포함된 구매 주문 양식의 주문 수량도 **0**로 조정됩니다." #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:212 msgid "" @@ -25068,6 +25817,10 @@ msgid "" "navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " "Process` button on an operation card, and selecting an order." msgstr "" +"주문에 대해 *지침* 품질 검사를 수행하려면 확인이 필요한 제조 주문 또는 재고 주문(입고, 배송, 반품 등)을 선택합니다. " +":menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동하여 원하는 주문을 선택하면 제조 주문에 액세스할 수 " +"있습니다. 재고 주문의 경우 :menuselection:`재고 관리`로 이동하여 작업 카드의 :guilabel:`# 진행 대기` 버튼을 " +"클릭한 다음 해당 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:42 msgid "" @@ -25169,6 +25922,9 @@ msgid "" "the recorded measurement must be within a certain *tolerance* of a *norm* " "value." msgstr "" +"Odoo의 *품질 관리* 모듈 내에서 *측정* 검사는 새로운 품질 검사 또는 품질 관리 지점(QCP)을 구성할 때 사용할 수 있는 품질 " +"검사 유형 중 하나입니다. 이러한 *측정* 검사는 사용자에게 제품의 특정 측정을 수행하고 이러한 측정값을 Odoo에 입력하라는 메시지를 " +"표시합니다. 품질 검사를 성공적으로 통과하려면 기록된 측정값이 지정된 *표준* 값의 사전 정의된 *오차* 범위 내에 있어야 합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:14 msgid "Create a Measure quality check" @@ -25339,6 +26095,10 @@ msgid "" ":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " "an operation card, and selecting an order." msgstr "" +"주문에 대한 *측정* 품질 검사를 처리하려면 확인이 필요한 제조 주문 또는 재고 주문(입고, 배송, 반품 등)을 선택합니다. 제조 주문은" +" :menuselection:`제조 관리 --> 작업 --> 제조 주문'`으로 이동한 후 주문을 클릭하여 선택할 수 있습니다. 재고 " +"주문의 경우 :menuselection:`재고 관리`로 이동하여 작업 카드의 :guilabel:`# 진행 대기` 버튼을 클릭한 다음 해당" +" 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:101 #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:96 @@ -25444,6 +26204,10 @@ msgid "" " view for that work order by selecting the :guilabel:`Work Orders` tab, and " "then clicking the :guilabel:`📱 (tablet)` button on the order's line." msgstr "" +"작업 주문에 대해 생성된 *측정* 품질 검사는 태블릿 보기에서 처리해야 합니다. 이렇게 하려면 먼저 :menuselection:`제조 " +"관리 --> 작업 --> 제조 주문`으로 이동합니다. 그런 다음 품질 검사가 필요한 작업 주문이 포함된 제조 주문을 선택합니다. 해당 " +"작업 주문의 태블릿 보기에 액세스하려면 :guilabel:`작업 주문` 탭으로 이동하여 주문 줄에 있는 :guilabel:`📱 " +"(태블릿)` 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:157 msgid "" @@ -25608,6 +26372,10 @@ msgid "" ":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " "an operation card, and selecting an order." msgstr "" +"주문에 대해 *합격-불합격* 품질 검사를 수행하려면 확인이 필요한 제조 주문 또는 재고 주문(입고, 배송, 반품 등)을 선택합니다. " +":menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동하여 원하는 주문을 선택하면 제조 주문에 액세스할 수 " +"있습니다. 재고 주문의 경우 :menuselection:`재고 관리`로 이동하여 작업 카드의 :guilabel:`# 진행 대기` 버튼을 " +"클릭한 다음 해당 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:87 msgid "" @@ -25660,6 +26428,10 @@ msgid "" " :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " "button on the order's line." msgstr "" +"작업 주문에 대해 설정된 *합격-불합격* 품질 검사의 경우 태블릿 보기에서 처리를 수행해야 합니다. 이렇게 하려면 먼저 " +":menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동합니다. 그런 다음 품질 검사가 필요한 작업 주문이 포함된" +" 제조 주문을 선택합니다. 해당 작업 주문의 태블릿 보기에 액세스하려면 :guilabel:`작업 주문` 탭으로 이동하여 주문 줄에 있는 " +":guilabel:`📱 (태블릿)` 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:119 msgid "" @@ -25670,6 +26442,9 @@ msgid "" "top-right of the screen. If the criteria is not met, click the " ":guilabel:`Fail` button." msgstr "" +"태블릿 보기가 열린 상태에서 화면 왼쪽에 나열된 단계를 *합격 - 불합격* 품질 검사 단계에 도달할 때까지 진행합니다. 품질 검사 단계에" +" 도달하면 화면 상단에 표시되는 지침을 따릅니다. 검사 기준을 충족하면 화면 오른쪽 상단에 있는 :guilabel:`합격` 버튼을 " +"클릭합니다. 기준을 충족하지 못하면 :guilabel:`실패` 버튼을 클릭합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 msgid "A Pass - Fail check for a manufacturing work order." @@ -25809,6 +26584,10 @@ msgid "" "navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " "Process` button on an operation card, and selecting an order." msgstr "" +"주문에 대한 *사진 촬영* 품질 검사를 처리하려면 확인이 필요한 제조 주문 또는 재고 주문(입고, 배송, 반품 등)을 선택합니다. 제조 " +"주문은 :menuselection:`제조 관리 --> 작업 --> 제조 주문'`으로 이동한 후 주문을 클릭하여 선택할 수 있습니다. 재고" +" 주문의 경우 :menuselection:`재고 관리`로 이동하여 작업 카드의 :guilabel:`# 진행 대기` 버튼을 클릭한 다음 " +"해당 주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:100 msgid "" @@ -25862,6 +26641,10 @@ msgid "" " :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " "button on the order's line." msgstr "" +"작업 주문에 대해 생성된 *사진 촬영* 품질 검사는 태블릿 보기에서 처리해야 합니다. 이렇게 하려면 먼저 " +":menuselection:`제조 관리 --> 작업 --> 제조 주문`으로 이동합니다. 그런 다음 품질 검사가 필요한 작업 주문이 포함된" +" 제조 주문을 선택합니다. 해당 작업 주문의 태블릿 보기에 액세스하려면 :guilabel:`작업 주문` 탭으로 이동하여 주문 줄에 있는 " +":guilabel:`📱 (태블릿)` 아이콘을 클릭합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 msgid "" @@ -26124,6 +26907,8 @@ msgid "" " :ref:`quality control points <quality/quality_management/quality-control-" "points>`." msgstr "" +"품질 관리 지점 (QCP)을 사용하면 일정한 간격으로 품질 검사를 자동으로 생성할 수 있습니다. QCP에 의해 품질 검사가 생성되면 제조" +" 또는 재고 주문에 표시되어 담당 직원에게 주문 처리 중에 완료하도록 경고합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:18 msgid "" @@ -26302,6 +27087,10 @@ msgid "" ":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " "an operation card, and selecting an order." msgstr "" +"주문에 대한 품질 검사를 처리하려면 확인이 필요한 제조 주문 또는 재고 주문 (입고, 배송, 반품 등)을 선택합니다. 제조 주문은 " +":menuselection:`제조 관리 --> 작업 --> 제조 주문'`으로 이동한 후 주문을 클릭하여 선택할 수 있습니다. 재고 주문의" +" 경우 :menuselection:`재고 관리`로 이동하여 작업 카드의 :guilabel:`# 진행 대기` 버튼을 클릭한 다음 해당 " +"주문을 선택합니다." #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:108 msgid "" diff --git a/locale/ko/LC_MESSAGES/marketing.po b/locale/ko/LC_MESSAGES/marketing.po index ec489498b..94bfe507f 100644 --- a/locale/ko/LC_MESSAGES/marketing.po +++ b/locale/ko/LC_MESSAGES/marketing.po @@ -4548,7 +4548,7 @@ msgid "" "records`." msgstr "" "이렇게 하려면 :menuselection:`SMS 마케팅 앱 --> 환경 설정 --> 블랙리스트에 등록된 전화번호`로 이동한 다음 " -":guilabel:`즐겨찾기` 드롭다운 메뉴 (검색 창 아래)를 선택하고 :guilabel:`가져오기 기록`을 클릭합니다." +":guilabel:`즐겨찾기` 드롭다운 메뉴 (검색 창 아래)를 선택하고 :guilabel:`기록 가져오기`를 클릭합니다." #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 msgid "View of how to import a blacklist in Odoo SMS Marketing." diff --git a/locale/ko/LC_MESSAGES/sales.po b/locale/ko/LC_MESSAGES/sales.po index dca4fe00e..262010894 100644 --- a/locale/ko/LC_MESSAGES/sales.po +++ b/locale/ko/LC_MESSAGES/sales.po @@ -4457,6 +4457,10 @@ msgid "" "click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " "printer." msgstr "" +":guilabel:`인증` 섹션에서 :guilabel:`인증서 목록`을 클릭한 후 :guilabel:`만들기`를 클릭하여 새로운 **자체" +" 서명 인증서**를 생성하세요. :guilabel:`일반 이름`은 자동으로 채워지게 됩니다. 입력되지 않는 경우 프린터 IP 주소 번호를" +" 입력합니다. :guilabel:`유효 기간` 필드에 인증서 유효 기간을 선택하고 :guilabel:`만들기` 및 " +":guilabel:`초기화`를 클릭하거나 프린터를 수동으로 다시 시작합니다." #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 @@ -4466,11 +4470,13 @@ msgid "" "**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " "Certificate` section." msgstr "" +"자체 서명된 인증서가 생성됩니다. 페이지를 새로고침하고 :guilabel:`보안` 섹션에서 :guilabel:`SSL/TLS`를 클릭하여" +" :guilabel:`서버 인증서` 섹션에서 **자체 서명된 인증서**가 올바르게 선택되어 있는지 확인합니다" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 msgid "Export a self-signed certificate" -msgstr "" +msgstr "자체 서명된 인증서 내보내기" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 @@ -4481,6 +4487,9 @@ msgid "" "Then, force the connection as explained in the **Generate a self-signed " "certificate tab**." msgstr "" +"내보내기 프로세스는 :abbr:`OS (운영 체제)`와 브라우저에 따라 크게 다릅니다. 먼저 IP 주소 (예: " +"`https://192.168.1.25`)로 이동하여 웹 브라우저에서 ePOS 프린터 설정에 액세스합니다. 그런 다음 **자체 서명 " +"인증서 생성 탭**에 설명된 대로 수기로 연결합니다." #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 @@ -4822,6 +4831,8 @@ msgid "" "`the name of your browser or operating system` in your preferred search " "engine." msgstr "" +"언급되지 않은 운영 체제 또는 웹 브라우저에서 SSL 인증서를 내보내야 하는 경우 기본 검색 엔진에서 `SSL 인증서 내보내기` + " +"`브라우저 또는 운영 체제 이름`을 검색합니다." #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 msgid "" @@ -4829,10 +4840,12 @@ msgid "" "search for `import SSL certificate root authority` + `the name of your " "browser or operating system` in your preferred search engine." msgstr "" +"마찬가지로, 언급되지 않은 OS 또는 브라우저에서 SSL 인증서를 가져오려면 사용하는 검색 엔진에서 'SSL 인증서 루트 기관 가져오기'" +" + '브라우저 또는 운영 체제 이름'을 검색합니다." #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 msgid "Check if the certificate was imported correctly" -msgstr "" +msgstr "인증서를 올바르게 가져왔는지 확인하기" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 msgid "" @@ -4842,6 +4855,9 @@ msgid "" "longer see a warning page, and the address bar should display a padlock " "icon, indicating that the connection is secure." msgstr "" +"프린터 연결이 안전한지 확인하려면 HTTPS를 사용하여 IP 주소에 연결합니다. 예를 들어 브라우저에서 " +"`https://192.168.1.25` 로 이동합니다. SSL 인증서가 올바르게 적용된 경우에는 더 이상 경고 페이지가 표시되지 않으며" +" 주소 표시줄에 연결이 안전하다는 것을 나타내는 자물쇠 아이콘이 표시됩니다." #: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 msgid "Secure connection (HTTPS)" @@ -17630,7 +17646,7 @@ msgstr "" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Quotation templates page in the Odoo Sales application." -msgstr "" +msgstr "Odoo 판매 애플리케이션에 있는 견적서 서식 페이지" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:47 msgid "" @@ -17638,16 +17654,18 @@ msgid "" "located in the upper-left corner. Doing so reveals a blank quotation " "template form that can be customized in a number of ways." msgstr "" +"새로운 견적서 서식을 생성하려면, 왼쪽 상단에 있는 :guilabel:`새로 만들기` 버튼을 클릭합니다. 그러면 다양한 방식으로 " +"커스터마이징할 수 있도록 내용이 비어있는 견적서 서식 양식이 표시됩니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "Create a new quotation template on Odoo Sales." -msgstr "" +msgstr "Odoo 판매에서 새로운 견적서 서식 만들기" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 msgid "" "Start by entering a name for the template in the :guilabel:`Quotation " "Template` field." -msgstr "" +msgstr ":guilabel:`견적서 서식` 필드에 서식 이름을 입력하는 것으로 시작합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 msgid "" @@ -17655,6 +17673,8 @@ msgid "" "the quotation template will remain valid for, or leave the field on the " "default `0` to keep the template valid indefinitely." msgstr "" +"그 다음, :guilabel:`견적 유효 기간` 필드에 견적서 서식의 유효 기간을 지정하거나, 기본값인 '0'으로 두어 유효 기간을 " +"제한하지 않습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 msgid "" @@ -17662,6 +17682,8 @@ msgid "" "reveal a drop-down menu. From the drop-down menu, select a pre-configured " "email template to be sent to customers upon confirmation of an order." msgstr "" +"다음으로 :guilabel:`확인 메일` 필드에서 빈 필드를 클릭하여 드롭다운 메뉴를 표시합니다. 드롭다운 메뉴에서, 고객이 주문을 하면" +" 전송할 수 있도록 미리 설정되어 있는 이메일 서식을 선택합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 msgid "" @@ -17670,12 +17692,14 @@ msgid "" "and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from" " the drop-down menu that appears." msgstr "" +":guilabel:`확인 메일` 필드에서 직접이메일 서식을 새로 생성하려면, 해당 필드에 새 이메일 서식의 이름을 입력한 후 드롭다운 " +"메뉴가 나타나면 :guilabel:`만들기` 또는 :guilabel:`만들기 및 편집...' 중 하나를 선택합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 msgid "" "Selecting :guilabel:`Create` creates the email template, which can be edited" " later." -msgstr "" +msgstr ":guilabel:`만들기`를 선택하면 이메일 서식이 생성되며 나중에 편집할 수 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 msgid "" @@ -17683,24 +17707,27 @@ msgid "" ":guilabel:`Create Confirmation Mail` pop-up window appears, in which the " "email template can be customized and configured right away." msgstr "" +":guilabel:`만들기 및 편집...`을 선택하면 이메일 서식이 생성되고, :guilabel:`확인 메일 만들기` 팝업 창이 나타나 " +"이메일 서식을 즉시 커스터마이징 및 설정할 수 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 msgid "" "Create confirmation mail pop-up window from the quotation template form in " "Odoo Sales." -msgstr "" +msgstr "Odoo 판매의 견적서 서식 양식에서 확인 메일 팝업 창을 생성합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 msgid "" "When all modifications are complete, click :guilabel:`Save \\& Close` to " "save the email template and return to the quotation form." -msgstr "" +msgstr "편집을 모두 완료했으면 :guilabel:`저장하고 닫기`를 클릭하여 이메일 서식을 저장하고 견적 양식으로 돌아갑니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 msgid "" "If working in a multi-company environment, use the :guilabel:`Company` field" " to designate to which company this quotation template applies." msgstr "" +"여러 개의 회사가 있는 환경에서 작업하는 경우 :guilabel:`회사` 필드에서 이 견적서 서식을 적용할 회사를 지정합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:85 msgid "" @@ -17709,6 +17736,8 @@ msgid "" "journal is set in this field, the sales journal with the lowest sequence is " "used." msgstr "" +":guilabel:`청구서 발행 전표` 필드에 전표가 설정되어 있으면 판매주문서에서 이 서식을 사용할 경우 모두 지정된 전표에서 청구서를" +" 발행합니다. 이 필드에 설정된 전표가 없는 경우 순서가 가장 낮은 판매 전표를 사용합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 msgid "" @@ -17717,12 +17746,15 @@ msgid "" "app --> Configuration --> Settings`), those options are available on " "quotation template forms." msgstr "" +":guilabel:`온라인 서명` 및/또는 :guilabel:`온라인 결제` 기능이 :guilabel:`설정` " +"(:menuselection:`판매 앱 --> 환경 설정 --> 설정`)에서 활성화되어 있으면 이러한 선택 사항을 견적서 서식 양식에서 " +"사용할 수 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 msgid "" "Check the box beside :guilabel:`Online Signature` to request an online " "signature from the customer to confirm an order." -msgstr "" +msgstr "주문 확정을 위해 고객에게 온라인 서명을 요청하려면 :guilabel:`온라인 서명` 옆에 있는 확인란을 선택합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 msgid "" @@ -17731,6 +17763,8 @@ msgid "" "checked, a new percentage field appears, in which a specific percentage of " "payment can be entered." msgstr "" +"주문 확정을 위해 고객에게 온라인 결제를 요청하려면 :guilabel:`온라인 결제` 옆에 있는 확인란을 선택합니다. " +":guilabel:`온라인 결제`를 선택하면 새로 백분율 필드가 표시되어 특정 결제 비율을 입력할 수 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 msgid "" @@ -17738,6 +17772,8 @@ msgid "" "can be enabled simultaneously, in which case the customer must provide " "**both** a signature **and** a payment to confirm an order." msgstr "" +":guilabel:`온라인 서명`과 :guilabel:`온라인 결제` 두 가지 선택 항목을 동시에 활성화할 수 있으며, 이 경우 고객이 " +"주문을 확정하려면 반드시 서명 **및** 결제를 **모두** 완료해야 합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 msgid "" @@ -17745,6 +17781,8 @@ msgid "" "configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`," " etc.) to designate how often this quotation template should occur." msgstr "" +":guilabel:`정기 결제` 필드에서, 미리 설정된 다양한 기간 (예: :guilabel:`월별`, :guilabel:`분기별` " +"등)을 선택하여 견적서 서식을 발행할 빈도를 지정합니다. ." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:109 msgid "" @@ -17752,10 +17790,12 @@ msgid "" " For more information, check out the documentation on " ":doc:`../../subscriptions/plans`." msgstr "" +":guilabel:`정기 결제` 필드는 **오로지** 구독 요금제에만 적용됩니다. 자세한 내용은 " +":doc:`../../subscriptions/plans` 문서를 참조하시기 바랍니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:113 msgid "Lines tab" -msgstr "" +msgstr "내역 탭" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 msgid "" @@ -17765,6 +17805,9 @@ msgid "" "further explained with discretionary information (such as warranty details, " "terms, etc.) by clicking :guilabel:`Add a note`." msgstr "" +":guilabel:`행` 탭에서는 :guilabel:`품목 추가`를 클릭하면 견적서 서식에 품목을 추가할 수 있으며, " +":guilabel:`영역 추가`를 클릭하여 체계적으로 구성합니다 (영역 헤더를 끌어다 놓습니다). 또한 특정 정보 (보증 세부 사항이나 " +"이용약관 등)를 추가로 기재하려면 :guilabel:`메모 추가`를 클릭하면 됩니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 msgid "" @@ -17772,6 +17815,8 @@ msgid "" " the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a " "blank field in the :guilabel:`Product` column." msgstr "" +"견적서 서식에 품목을 추가하려면 견적서 서식 양식의 :guilabel:`내역` 탭에서 :guilabel:`품목 추가`를 클릭합니다. " +"그러면 :guilabel:`품목` 열에 빈 필드가 나타납니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:123 msgid "" @@ -17779,6 +17824,8 @@ msgid "" "appear. Select the desired product from the drop-down menu to add it to the " "quotation template." msgstr "" +"클릭하면 데이터베이스에 있는 기존 품목이 있는 드롭다운 메뉴가 나타납니다. 드롭다운 메뉴에서 원하는 품목을 선택하여 견적서 서식에 " +"추가합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 msgid "" @@ -17787,18 +17834,20 @@ msgid "" "drop-down menu. Products can also be found by clicking :guilabel:`Search " "More...` from the drop-down menu." msgstr "" +"원하는 품목을 쉽게 찾을 수 없는 경우 :guilabel:`품목` 필드에 원하는 품목 이름을 입력하면 드롭다운 메뉴에 선택 사항이 " +"나타납니다. 드롭다운 메뉴에서 :guilabel:`추가 검색...`을 클릭하여 품목을 검색할 수도 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132 msgid "" "When a product is added to a quotation template, the default " ":guilabel:`Quantity` is `1`, but that can be edited at any time." -msgstr "" +msgstr "품목이 견적서 서식에 추가될 경우 기본 :guilabel:`수량`은 `1`이지만 언제든지 수정할 수 있습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135 msgid "" "Then, drag-and-drop the product to the desired position, via the " ":guilabel:`six squares` icon, located to the left of each line item." -msgstr "" +msgstr "그런 다음 각 항목 왼쪽에 있는 :guilabel:`6개의 사각형` 아이콘을 통해 품목을 원하는 위치로 끌어다 놓습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 msgid "" @@ -17808,12 +17857,16 @@ msgid "" "section can be typed. When the name has been entered, click away to secure " "the section name." msgstr "" +"판매주문서의 내용을 체계화할 수 있는 제목 역할을 하도록 *섹션*을 추가하려면, :guilabel:`내역` 탭에서 " +":guilabel:`섹션 추가`를 클릭합니다. 클릭하면 원하는 섹션 이름을 입력할 수 있는 빈 필드가 나타납니다. 이름을 입력한 후 " +"클릭하여 섹션 이름을 확정합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143 msgid "" "Then, drag-and-drop the section name to the desired position, via the " ":guilabel:`six squares` icon, located to the left of each line item." msgstr "" +"그런 다음 각 항목 왼쪽에 있는 :guilabel:`6개의 사각형` 아이콘을 통해 섹션 이름을 원하는 위치로 끌어다 놓습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146 msgid "" @@ -17822,12 +17875,14 @@ msgid "" "clicked, a blank field appears, in which the desired note can be typed. When" " the note has been entered, click away to secure the note." msgstr "" +"견적서에 고객을 위한 텍스트로 표시될 메모를 추가하려면, :guilabel:`내역` 탭에서 :guilabel:`메모 추가`를 클릭합니다." +" 클릭하면 원하는 메모를 입력할 수 있는 빈 필드가 나타납니다. 메모를 입력한 후 외부 영역을 클릭하 메모를 저장합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 msgid "" "Then, drag-and-drop the note to the desired position, via the :guilabel:`six" " squares` icon." -msgstr "" +msgstr "그런 다음 :guilabel:`6개의 사각형` 아이콘을 통해 메모을 원하는 위치로 끌어다 놓습니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152 msgid "" @@ -17835,10 +17890,12 @@ msgid "" "and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right " "side of the line." msgstr "" +":guilabel:`내역` 탭 (품목, 섹션 및/또는 메모)에서 내역에 있는 항목을 삭제하려면 내역 맨 오른쪽에 있는 " +":guilabel:`🗑️ (휴지통)` 아이콘을 클릭합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 msgid "Optional Products tab" -msgstr "" +msgstr "선택 품목 탭" #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158 msgid "" @@ -17847,6 +17904,8 @@ msgid "" "useful and related products to customers, which may result in an increased " "sale." msgstr "" +"*선택 품목*을 사용하는 것은 주력 품목과 함께 다른 제품들을 교차 판매하는 마케팅 전략입니다. 고객과 관련이 있는 유용한 품목을 " +"제안하여 매출을 증대시키는 것을 목표로 합니다." #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 msgid "" @@ -18074,7 +18133,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions.rst:60 msgid "Automatic payments" -msgstr "" +msgstr "자동 결제" #: ../../content/applications/sales/subscriptions.rst:62 msgid "" @@ -18083,6 +18142,8 @@ msgid "" " To do so, go to the :guilabel:`Other Info` tab of the quotation and check " "the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field." msgstr "" +"견적서 확정 전에 고객에게 자동 결제 방법을 설정하여 첫 구독 요금을 선불로 납부하도록 요청할 수 있습니다. 그렇게 하려면 견적서의 " +":guilabel:`기타 정보` 탭으로 이동하여 :guilabel:`온라인 확인` 필드에서 :guilabel:`결제` 옵션을 선택합니다." #: ../../content/applications/sales/subscriptions.rst:67 msgid "" @@ -18090,6 +18151,8 @@ msgid "" "pre-pay to start the subscription. This means that the payment is not " "automatic and that the customer must pay each invoice manually." msgstr "" +":guilabel:`결제` 항목에 표시하지 않으면, 고객이 구독을 시작하기 위해 선불로 결제할 필요가 없습니다. 즉, 결제가 자동으로 " +"진행되지 않으며 고객이 청구서별로 직접 결제해야 합니다." #: ../../content/applications/sales/subscriptions.rst:72 msgid "" @@ -18099,10 +18162,14 @@ msgid "" "<payment_providers/features/tokenization>`. This ensures that the customer " "is automatically charged at each new period." msgstr "" +"선불로 결제해야 온라인 확정이 되는 경우, 고객은 :ref:`토큰화 기능 " +"<payment_providers/supported_providers>`을 지원하는 :ref:`결제대행업체자 " +"<payment_providers/supported_providers>`만 선택할 수 있습니다. 이렇게 하면 새로운 기간마다 고객에게 " +"자동으로 요금이 청구됩니다." #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:3 msgid "Automatic alerts" -msgstr "" +msgstr "자동 알림" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:5 msgid "" @@ -18111,6 +18178,8 @@ msgid "" "not want to go through the list of all your subscribers to check how things " "are going. This is what the *Automatic Alerts* feature is for." msgstr "" +"이제 구독 중이기 때문에, 고객에게 최신 정보를 제공해 주고 싶습니다. 일부라도 자동화가 되어 있다면 진행 상황을 확인하기 위해 전체 " +"구독자 목록을 일일이 살펴보지 않아도 될 것입니다. 이것이 바로 *자동 알림* 기능입니다." #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:9 msgid "" @@ -18120,6 +18189,8 @@ msgid "" "probably want to schedule a call with them to understand the reasons for " "their dissatisfaction." msgstr "" +"예를 들어, 고객이 잡지를 구독할 경우 환영과 감사의 마음을 전하기 위해 이메일을 전송합니다. 또는 고객 만족도가 50% 미만으로 " +"떨어지는 경우에는 고객과 통화 일정을 잡아 만족하지 못하는 이유를 파악하도록 합니다." #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:14 msgid "" @@ -18129,10 +18200,13 @@ msgid "" "satisfaction surveys so customers can evaluate your services? All of that is" " now possible." msgstr "" +"**Odoo 구독**을 사용하면 자동 이메일을 설정하고, 영업 담당자용 \"통화\" 작업을 생성하여 고객의 불만족 상황에 대해 파악할 수" +" 있도록 합니다. 마지막으로, 자동으로 설문을 발송하여 고객 만족도 설문조사를 진행해 보는 것은 어떨까요? 이제 그 모든 것이 " +"가능합니다." #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:20 msgid "Create a new automatic alert" -msgstr "" +msgstr "새 자동 알림 만들기" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:22 msgid "" @@ -18141,10 +18215,12 @@ msgid "" "subscription. To do so, go to :menuselection:`Subscriptions --> " "Configuration --> Alerts`, and create a new alert." msgstr "" +"다음 예시는 구독 한 달 후 고객에게 만족도 설문조사를 이메일로 보내도록 새 자동 알림을 만드는 방법입니다. 이렇게 하려면 " +":menuselection:`구독 --> 환경 설정 --> 알림`으로 이동하여 새 알림을 생성합니다." #: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 msgid "New automatic alert in Odoo Subscriptions" -msgstr "" +msgstr "Odoo 구독의 새로운 자동 알림" #: ../../content/applications/sales/subscriptions/automatic_alerts.rst:30 msgid "" @@ -18271,6 +18347,8 @@ msgid "" "companies come up with dubious methods to reduce the probability of this " "happening." msgstr "" +"언제든 고객을 잃는다는 것은 곤란한 일이며, 특히 많은 공을 들여서 품목/서비스를 사용하도록 한 경우라면 더욱 그럴 것입니다. 그러나 " +"이런 일이 발생할 확률을 줄이기 위해 많은 회사에서는 제시하고 있는 방법은 그다지 믿을만하지 않습니다." #: ../../content/applications/sales/subscriptions/closing.rst:14 msgid "" @@ -18310,6 +18388,9 @@ msgid "" "customer*. Once enabled, this option gives your customers the right to close" " their own subscriptions." msgstr "" +":menuselection:`구독 --> 환경 설정 --> 구독 서식`으로 이동합니다. 여기에서 새로운 *구독 서식*을 생성하거나 기존 " +"서식을 편집할 수 있습니다. 서식을 편집할 때 청구서 발행 탭 아래에 있는 *고객이 해지 가능* 옵션을 활성화할 수 있습니다. 이 옵션을" +" 활성화하면 고객이 본인 구독을 해지할 수 있는 권한을 갖게 됩니다." #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "Configuration to close your subscription with Odoo Subscriptions" @@ -18352,14 +18433,17 @@ msgid "" "subscription is now *Closed* and that the close reason is mentioned on the " "subscription." msgstr "" +"*닫기* 스마트 버튼을 이용하여 해지 사유를 입력해야 합니다. 예를 들어 \"구독 요금이 너무 비싸서\", \"구독으로 요구 사항이 " +"충족하지 않아서\", \"구독 기간이 종료되어서\" 등이 있습니다. 종료 사유를 확인하면 구독 상태가 즉시 *해지됨*으로 표시되고 구독에" +" 해지 사유가 표시됩니다." #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "What happens when you close your subscription with Odoo Subscriptions?" -msgstr "" +msgstr "Odoo 구독에서 구독을 해지하면 어떻게 되나요?" #: ../../content/applications/sales/subscriptions/closing.rst:72 msgid "Customer view" -msgstr "" +msgstr "고객 화면" #: ../../content/applications/sales/subscriptions/closing.rst:74 msgid "" @@ -18370,6 +18454,8 @@ msgid "" "his/her subscription whenever he/she wants to, due to the *Close " "Subscription* button." msgstr "" +"앞서 *관리자 화면* 부분에서 설명한 바와 같이, 구독 양식에서 *고객 미리보기* 버튼으로 구독을 관리할 때 고객에게 표시되는 내용을 " +"화면에서 확인할 수도 있습니다. 이 예에서 고객은 *구독 해지* 버튼을 통해 원할 때 언제든지 구독을 해지할 수 있습니다." #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" @@ -18397,6 +18483,8 @@ msgid "" "chatter with the new stage, the end date, the close reason, and the closing " "text added by the customer." msgstr "" +"취소 확정을 하면 고객은 본인의 포털로 리디렉션됩니다. 관리자에게 변경 사항이 통보됩니다. 이제, 구독 상태는 *해지됨*으로 변경되고 " +"새로운 단계, 해지 날짜, 해지 사유 및 고객이 추가한 종료 텍스트가 포함된 메모가 메시지창에 표시됩니다." #: ../../content/applications/sales/subscriptions/closing.rst-1 msgid "" @@ -18429,6 +18517,9 @@ msgid "" "*yearly* recurrence periods configured, then only the monthly price appears " "on the eCommerce page for that product by default." msgstr "" +"그러나 기본적으로 이커머스에 있는 품목 페이지에는 품목 양식의 :guilabel:`시간 기준 요금` 탭에 있는 항목 중 가장 정기 경제 " +"기간이 짧은 항목만 표시됩니다. 예를 들어 구독 제품에 *월간* 및 *연간* 정기 결제 품목이 설정되어 있는 경우에는, 기본적으로 해당 " +"품목의 이커머스 페이지에는 월간 가격만 표시됩니다." #: ../../content/applications/sales/subscriptions/ecommerce.rst:12 msgid "" @@ -18476,12 +18567,17 @@ msgid "" ":guilabel:`Create`. These value names appear as selectable options on the " "product page of the eCommerce shop." msgstr "" +"다음으로, 품목 양식의 :guilabel:`시간 기준 요금` 탭에 구성된 정기 결제 기간에 해당하는 :guilabel:`값`을 " +"생성합니다. 정기 결제 기간의 이름을 입력한 후 :guilabel:`만들기`를 클릭합니다. 값의 이름은 이커머스 상점의 품목 페이지에서 " +"선택 항목으로 표시됩니다." #: ../../content/applications/sales/subscriptions/ecommerce.rst-1 msgid "" "Recurrence periods configured as product variants in the \"Attributes & Variants\" tab of\n" "the product form." msgstr "" +"품목 양식의 '속성 및 세부 옵션' 탭에서 품목 세부 옵션으로 구성된 정기 결제\n" +"기간입니다." #: ../../content/applications/sales/subscriptions/ecommerce.rst:40 msgid "" @@ -18490,6 +18586,8 @@ msgid "" " :guilabel:`Time-based pricing` tab. Assign the product variants to their " "corresponding recurrence periods and prices." msgstr "" +"수기로 저장하려면 페이지 상단의 :guilabel:`☁️ (클라우드)` 아이콘을 클릭합니다. 저장하고 나면 :guilabel:`품목 세부" +" 옵션` 열이 :guilabel:`시간 기준 요금` 탭에 표시됩니다. 품목 세부 옵션을 해당하는 정기 결제 기간 및 가격에 할당합니다." #: ../../content/applications/sales/subscriptions/ecommerce.rst-1 msgid "Product variants on the \"Time-based pricing\" tab of the product form." @@ -18556,6 +18654,8 @@ msgid "" "the quotation expires, starting from the day the quotation is sent to the " "customer. Leave this field at zero for the quotation to never expire." msgstr "" +":guilabel:`다음 이후 견적서 만료`: 견적서가 고객에게 전송된 날부터 시작하여 견적이 만료되기까지의 일 수를 입력합니다. 견적서" +" 만료 기간이 없게 하려면 이 필드를 0으로 둡니다." #: ../../content/applications/sales/subscriptions/plans.rst:28 msgid "" @@ -18565,6 +18665,9 @@ msgid "" "Enable both to leave the choice to the customer. Enable neither to only " "confirm the quotation in the backend." msgstr "" +":guilabel:`온라인 확인`: :guilabel:`서명` 또는 :guilabel:`결제` 옆의 확인란을 선택하면, 고객이 견적서에 " +"서명하거나 비용을 지불하여 구독 주문을 확인할 수 있도록 합니다. 고객에게 선택하도록 하려면 두 가지 모두 활성화합니다. 백엔드에서만 " +"견적서를 확인하게 하려면 두 항목 모두 활성화하지 않습니다." #: ../../content/applications/sales/subscriptions/plans.rst:32 msgid "" @@ -18573,6 +18676,9 @@ msgid "" "confirmation email that is automatically sent to the customer after the " "quotation is confirmed. Leave this field blank to send nothing." msgstr "" +":guilabel:`확인 메일`: 견적서 확정된 후 고객에게 자동으로 전송되는 확인 이메일에 대한 :doc:`이메일 서식 " +"</applications/general/email_communication/email_template>`을 선택합니다. 필드를 비워둘 " +"경우 전송되는 항목이 없습니다." #: ../../content/applications/sales/subscriptions/plans.rst:37 msgid "" @@ -19319,11 +19425,11 @@ msgstr "" #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "Detailed MRR report in Odoo Subscriptions" -msgstr "" +msgstr "Odoo 구독의 MRR 세부 보고서 " #: ../../content/applications/sales/subscriptions/reports.rst:108 msgid "Salesperson dashboard report" -msgstr "" +msgstr "영업 담당자 현황판 보고서" #: ../../content/applications/sales/subscriptions/reports.rst:110 msgid "" @@ -19333,15 +19439,18 @@ msgid "" "Recurring Invoices* for each of your salespeople. You can choose the period " "you want to apply and the salesperson you want to analyze." msgstr "" +":menuselection:`구독 --> 보고 --> 영업 담당자 현황판`으로 이동합니다. 이 페이지에서는 각 영업 담당자별 *월간 정기" +" 결제*, *비정기 결제 수익*, *구독 수정* 및 *비반복 청구서*에 대한 요약을 제공합니다. 적용 대상 기간과 분석할 영업 담당자를 " +"선택할 수 있습니다." #: ../../content/applications/sales/subscriptions/reports.rst-1 msgid "Salesperson dashboard report in Odoo Subscriptions" -msgstr "" +msgstr "Odoo 구독의 영업 담당자 현황판 보고서" #: ../../content/applications/sales/subscriptions/upselling.rst:3 #: ../../content/applications/sales/subscriptions/upselling.rst:44 msgid "Upsell subscriptions" -msgstr "" +msgstr "구독 상향 판매" #: ../../content/applications/sales/subscriptions/upselling.rst:5 msgid "" @@ -19351,14 +19460,17 @@ msgid "" "need. That's where the opportunity to upsell a subscription can come into " "play." msgstr "" +"구독은 반복적으로 기간을 두지 않고 진행됩니다. 시간이 지남에 따라 고객은 구독 내용을 변경하고자 할 수도 있습니다. 이에 따라 어떤 " +"요구 사항에도 맞출 수 있도록 가격을 조정하거나 수량을 변경할 수 있는 기능이 필수입니다. 바로 여기에서 구독을 상향 판매할 수 있는 " +"기회가 생기게 됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst:9 msgid "Upselling may prove beneficial to the following customer types:" -msgstr "" +msgstr "Odoo 구독의 영업 담당자 현황판 보고서" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "*Loyal Customers*" -msgstr "" +msgstr "*충성 고객*" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "" @@ -19366,10 +19478,12 @@ msgid "" "have established a pattern of paying for products/services, there's more " "confidence behind the attempt to sell them a more expensive product/service." msgstr "" +"이미 회사/브랜드를 신뢰하고 있는 고객이며, 품목/서비스에 대한 결제 패턴이 확정되어 있기 때문에, 좀 더 자신감 있게 좀 더 가격이 " +"높은 품목/서비스를 판매하도록 시도해 볼 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "*New Customers*" -msgstr "" +msgstr "*신규 고객*" #: ../../content/applications/sales/subscriptions/upselling.rst:0 msgid "" @@ -19377,12 +19491,14 @@ msgid "" " tactic must be employed to entice them to purchase a more expensive " "product/service." msgstr "" +"회사/브랜드에 익숙하지 않은 신규 고객의 경우, 좀 더 가격이 높은 품목/서비스를 구매하도록 유도하기 위해서는 새로우면서도 관심을 끌 수" +" 있는 전략을 사용해야 합니다." #: ../../content/applications/sales/subscriptions/upselling.rst:19 msgid "" "In these instances, discounts can be useful. Typically, subscriptions end " "after a certain period of time." -msgstr "" +msgstr "이러한 경우에는 할인 혜택을 주는 것이 유용할 수 있습니다. 보통 구독은 일정 기간이 지나면 종료됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst:22 msgid "" @@ -19392,16 +19508,19 @@ msgid "" "increase customer retention, as they'll grow more comfortable and " "trustworthy over time." msgstr "" +"따라서 이렇게 가격대가 더 높은 품목/서비스를 신규 고객에게 할인된 가격으로 제공하면 판매로 이어질 수 있으며 동시에 .고객과 " +"회사/브랜드 사이에 강한 신뢰감을 형성할 수 있습니다 결과적으로 시간이 지남에 따라 고객이 더욱 편안하게 느끼고 신뢰할 수 있게 되므로 " +"고객 유지율을 높일 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:28 msgid "Discount configuration" -msgstr "" +msgstr "할인 설정" #: ../../content/applications/sales/subscriptions/upselling.rst:30 msgid "" "In order to have the ability to upsell a subscription to a new customer, " "with the aid of a discount, the *Discounts* feature **must** be activated." -msgstr "" +msgstr "할인을 통해 신규 고객에게 구독을 상향 판매하려면, *할인* 기능이 **반드시** 활성화되어 있어야 합니다." #: ../../content/applications/sales/subscriptions/upselling.rst:33 msgid "" @@ -19410,22 +19529,26 @@ msgid "" "and tick the checkbox beside :guilabel:`Discounts`. Then, click " ":guilabel:`Save`." msgstr "" +"*할인* 기능을 활성화하려면 :menuselection:`판매 앱 --> 환경 설정 --> 설정`으로 이동하여 :guilabel:`가격`" +" 섹션으로 스크롤을 이동한 다음 :guilabel:`할인` 옆의 확인란을 선택합니다. 그런 다음 :guilabel:`저장`을 클릭합니다." #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "Activation of the discount option in Odoo Sales." -msgstr "" +msgstr "Odoo 판매에서 할인 항목을 활성화합니다." #: ../../content/applications/sales/subscriptions/upselling.rst:41 msgid "" "With that feature activated, the ability to grant discounts on sales order " "lines." -msgstr "" +msgstr "해당 기능이 활성화되면 판매주문서 내용에 대해 할인을 적용할 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:46 msgid "" "Before upselling a subscription, check out our documentation on how to " ":doc:`Create a quotation <../subscriptions>` using subscription products." msgstr "" +"구독을 상향 판매하기 전에 구독 품목을 사용하여 :doc:`견적서 만들기 <../subscriptions>`를 하는 방법에 대한 문서를 " +"확인해 보세요." #: ../../content/applications/sales/subscriptions/upselling.rst:49 msgid "" @@ -19433,12 +19556,13 @@ msgid "" "sales order, and a new subscription is created in the Odoo *Subscriptions* " "application." msgstr "" +"구독 견적서를 승인하게 되면 이는 공식적인 판매주문서가 되는 것이며, Odoo *구독* 애플리케이션에서 새로운 구독 항목이 생성됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst:53 msgid "" "The subscription sales order **must** be invoiced *before* an upsell can " "occur." -msgstr "" +msgstr "구독 판매주문서는 **반드시** 상향 판매가 발생하기 *전에* 청구서를 발행해야 합니다." #: ../../content/applications/sales/subscriptions/upselling.rst:55 msgid "" @@ -19446,10 +19570,12 @@ msgid "" "*Subscriptions* application, the ability to upsell that subscription is " "available, via the :guilabel:`Upsell` button at the top of the sales order." msgstr "" +"*판매* 또는 *구독* 애플리케이션에서 구독 판매주문서를 열면, 판매주문서 상단에 있는 :guilabel:`상향 판매` 버튼으로 해당 " +"구독을 상향 판매할 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "Upsell button for subscription sales orders with Odoo Subscriptions." -msgstr "" +msgstr "Odoo 구독에서 구독 판매주문서에 대한 상향 판매 버튼" #: ../../content/applications/sales/subscriptions/upselling.rst:63 msgid "" @@ -19457,6 +19583,8 @@ msgid "" " with an :guilabel:`Upsell` status banner in the upper-right corner. The " "initial subscription product is already in the :guilabel:`Order Lines` tab." msgstr "" +":guilabel:`상향 판매` 버튼을 클릭하면 새로운 견적서 양식이 오른쪽 상단의 :guilabel:`상향 판매` 상태 배너와 함께 " +"나타납니다. 초기 구독 제품은 이미 :guilabel:`주문서 내역` 탭에 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:67 msgid "" @@ -19464,6 +19592,8 @@ msgid "" "discounted, according to the prorated period of time, located beneath the " "initial subscription product in the :guilabel:`Order Lines` tab." msgstr "" +"또한 :guilabel:`주문서 내역` 탭의 초기 구독 제품 아래에는 정기 결제 품목이 기간에 따라 비례하여 할인된다는 사실을 사용자에게" +" 상기시키도록 주의 사항이 표시됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst:71 msgid "" @@ -19471,12 +19601,14 @@ msgid "" ":guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and " "selecting the desired subscription product." msgstr "" +"이 신규 상향 판매 견적서 양식에 :guilabel:`품목 추가`를 클릭하고 원하는 구독 품목을 선택하여 :guilabel:`주문서 " +"내역` 탭에 새 구독 품목을 추가합니다." #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "" "Adding products to your subscription via the upsell option in Odoo " "Subscriptions" -msgstr "" +msgstr "Odoo 구독의 상향 판매 옵션을 통해 구독에 품목 추가하기" #: ../../content/applications/sales/subscriptions/upselling.rst:78 msgid "" @@ -19484,6 +19616,7 @@ msgid "" "sent to the customer for approval by clicking the :guilabel:`Send by Email` " "button." msgstr "" +"원하는 상향 판매 구독 품목이 추가되면 :guilabel:`이메일로 보내기` 버튼을 클릭하면 고객에게 보내어 승인을 받을 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:82 msgid "" @@ -19491,12 +19624,14 @@ msgid "" "added to the initial subscription. Quotation prices are then prorated to the" " remaining time of the current invoicing period." msgstr "" +"고객이 견적서를 확인하면 상향 판매 품목이 초기 구독에 추가됩니다. 그런 다음 견적서에 있는 가격은 현재 청구서 발행 기간의 남은 시간에" +" 비례하여 계산됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst:87 msgid "" "Before sending the new quotation to the customer, the unit price, taxes, and" " even discount can be applied." -msgstr "" +msgstr "고객에게 새 견적서를 보내기 전에 단가, 세금, 할인까지 적용할 수 있습니다." #: ../../content/applications/sales/subscriptions/upselling.rst:90 msgid "" @@ -19505,6 +19640,8 @@ msgid "" "History` smart button appears, displaying how many sales orders are attached" " to this initial subscription order." msgstr "" +"고객이 승인하게 되면, 견적서에서 :guilabel:`확인` 버튼을 클릭하여 판매주문서로 변환합니다. 클릭하면 :guilabel:`판매 " +"이력` 스마트 버튼이 표시되어 초기 구독 주문서에 첨부된 판매주문서의 숫자를 표시합니다." #: ../../content/applications/sales/subscriptions/upselling.rst:94 msgid "" @@ -19512,9 +19649,11 @@ msgid "" "separate page containing a list of the related sales orders, clearly " "showcasing their individual :guilabel:`Subscription Status`." msgstr "" +":guilabel:`판매 이력` 스마트 버튼을 클릭하면 Odoo에 관련 판매주문서 목록이 별도의 페이지로 나타나서 개별 " +":guilabel:`구독 상태`가 명확하게 표시됩니다." #: ../../content/applications/sales/subscriptions/upselling.rst-1 msgid "" "The related sales order viewable from the Sales History smart button in Odoo" " Subscriptions." -msgstr "" +msgstr "Odoo 구독의 판매 이력 스마트 버튼에서 볼 수 있는 관련된 판매주문서입니다." diff --git a/locale/nl/LC_MESSAGES/administration.po b/locale/nl/LC_MESSAGES/administration.po index 94a479d2a..9fefc4f51 100644 --- a/locale/nl/LC_MESSAGES/administration.po +++ b/locale/nl/LC_MESSAGES/administration.po @@ -11,6 +11,7 @@ # Jolien De Paepe, 2023 # Gunther Clauwaert <gclauwae@hotmail.com>, 2023 # Erwin van der Ploeg <erwin@odooexperts.nl>, 2024 +# Larissa Manderfeld, 2024 # #, fuzzy msgid "" @@ -19,7 +20,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:55+0000\n" -"Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2024\n" +"Last-Translator: Larissa Manderfeld, 2024\n" "Language-Team: Dutch (https://app.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -5171,7 +5172,7 @@ msgstr "" #: ../../content/administration/odoo_sh/getting_started/settings.rst:123 #: ../../content/administration/odoo_sh/getting_started/settings.rst:127 msgid "|green|" -msgstr "|groen|" +msgstr "|green|" #: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:93 @@ -5329,7 +5330,7 @@ msgstr "Legenda" #: ../../content/administration/maintain/supported_versions.rst:109 msgid "|green| Supported version" -msgstr "|groen| Ondersteunde versies" +msgstr "|green| Ondersteunde versies" #: ../../content/administration/maintain/supported_versions.rst:111 msgid "|red| End-of-support" diff --git a/locale/pt_BR/LC_MESSAGES/inventory_and_mrp.po b/locale/pt_BR/LC_MESSAGES/inventory_and_mrp.po index 2bcb3f527..602cc0322 100644 --- a/locale/pt_BR/LC_MESSAGES/inventory_and_mrp.po +++ b/locale/pt_BR/LC_MESSAGES/inventory_and_mrp.po @@ -1756,7 +1756,7 @@ msgid "" "the associated receipt in the *Barcode* app." msgstr "" "Depois de fazer um :abbr:`PO (pedido de compra)` para cinquenta maçãs, " -"navegue até o recibo associado no aplicativo *Código de barras*." +"navegue até o recebimento associado no aplicativo *Código de barras*." #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:121 msgid "" @@ -1909,8 +1909,8 @@ msgid "" "peaches by scanning the barcode containing the |GTIN| and quantity of " "peaches in kilograms." msgstr "" -"No recibo do aplicativo *Código de barras*, receba um pedido de `52,1 kg` de" -" pêssegos, digitalizando o código de barras que contém o |GTIN| e a " +"No reccebimento do aplicativo *Código de barras*, receba um pedido de `52,1 " +"kg` de pêssegos, digitalizando o código de barras que contém o |GTIN| e a " "quantidade de pêssegos em quilogramas." #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:197 @@ -3175,9 +3175,9 @@ msgid "" msgstr "" "Os recursos de leitura de código de barras podem economizar muito tempo " "despendido com a alternância entre o teclado, o mouse e o leitor. A " -"atribuição adequada de códigos de barras a produtos, locais de coleta etc. " -"permite que você trabalhe com mais eficiência, controlando o software quase " -"que exclusivamente com o leitor de código de barras." +"atribuição adequada de códigos de barras a produtos, locais de separação " +"etc. permite que você trabalhe com mais eficiência, controlando o software " +"quase que exclusivamente com o leitor de código de barras." #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:16 msgid "" @@ -4101,9 +4101,9 @@ msgid "" "page by clicking on it. A :guilabel:`Scrap` button appears at the top of the" " page. Click it to open the :guilabel:`Scrap` pop-up window." msgstr "" -"Em seguida, abra uma ordem de entrega, um recibo ou uma transferência na " -"página correspondente clicando nela. Um botão :guilabel:`Sucata` é exibido " -"na parte superior da página. Clique nele para abrir a janela pop-up " +"Em seguida, abra um pedido de entrega, um recebimento ou uma transferência " +"na página correspondente clicando nela. Um botão :guilabel:`Sucata` é " +"exibido na parte superior da página. Clique nele para abrir a janela pop-up " ":guilabel:`Sucata`." #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 @@ -4879,7 +4879,7 @@ msgstr "" "(PO), clique no botão inteligente :guilabel:`Recebimentos` no canto superior" " direito do PO. O Odoo converte automaticamente a unidade de medida da " "compra na unidade de medida de vendas/inventário do produto, de modo que a " -"coluna :guilabel:`Demanda` do recibo de entrega mostra a quantidade " +"coluna :guilabel:`Demanda` do recebimento da entrega mostra a quantidade " "convertida." #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:85 @@ -5561,8 +5561,8 @@ msgid "" "#`; and more." msgstr "" "Um botão inteligente :guilabel:`Rastreabilidade` aparecerá após a validação " -"do recibo. Clique no botão inteligente :guilabel:`Rastreabilidade` para ver " -"o :guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " +"do recebimento. Clique no botão inteligente :guilabel:`Rastreabilidade` para" +" ver o :guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " "documento :guilabel:`Referência`; o :guilabel:`Produto` que está sendo " "rastreado; o :guilabel:`Nº de série/lote`; e mais." @@ -5723,9 +5723,9 @@ msgid "" "process all :guilabel:`Done` quantities, and deliver the products to the " "customer." msgstr "" -"No formulário de recibo do depósito, clique em :guilabel:`Validar` e, em " -"seguida, em :guilabel:`Aplicar` na janela pop-up que o acompanha, para " -"processar automaticamente todas as quantidades :guilabel:`Concluído` e " +"No formulário de recebimento do armazém, clique em :guilabel:`Validar` e, em" +" seguida, em :guilabel:`Aplicar` na janela pop-up que o acompanha, para " +"processar automaticamente todas as quantidades :guilabel:`concluídas` e " "entregar os produtos ao cliente." #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:215 @@ -6257,8 +6257,8 @@ msgid "" " assigned, and more." msgstr "" "Um botão inteligente :guilabel:`Rastreabilidade` aparece após a validação do" -" recibo. Clique no botão inteligente :guilabel:`Rastreabilidade` para ver o " -":guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " +" recebimento. Clique no botão inteligente :guilabel:`Rastreabilidade` para " +"ver o :guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " "documento :guilabel:`Referência`; o :guilabel:`Produto` que está sendo " "rastreado; o :guilabel:`Nº de série/lote` atribuído e mais." @@ -6420,8 +6420,8 @@ msgid "" " receipt from the previous purchase order, if the product quantities shared " "the same lot number." msgstr "" -"O :guilabel:`Relatório de rastreabilidade` também pode incluir um recibo " -":guilabel:`Referência` do pedido de compra anterior, se as quantidades do " +"O :guilabel:`Relatório de rastreabilidade` também pode incluir um recibo de " +":guilabel:`referência` do pedido de compra anterior, se as quantidades do " "produto compartilharem o mesmo número de lote." #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 @@ -7037,8 +7037,8 @@ msgid "" "#`, and more." msgstr "" "Um botão inteligente :guilabel:`Rastreabilidade` aparece após a validação do" -" recibo. Clique no botão inteligente :guilabel:`Rastreabilidade` para ver o " -":guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " +" recebimento. Clique no botão inteligente :guilabel:`Rastreabilidade` para " +"ver o :guilabel:`Relatório de rastreabilidade` atualizado, que inclui: um " "documento :guilabel:`Referência`; o :guilabel:`Produto` que está sendo " "rastreado; o :guilabel:`Nº de série/lote` e mais." @@ -7055,7 +7055,7 @@ msgstr "" "Quando todas as quantidades de produtos tiverem recebido um número de série," " clique em :guilabel:`Confirmar` para fechar a janela pop-up e clique em " ":guilabel:`Validar`. Um botão inteligente :guilabel:`Rastreabilidade` " -"aparecerá após a validação do recibo. Clique no botão inteligente " +"aparecerá após a validação do recebimento. Clique no botão inteligente " ":guilabel:`Ratreabilidade` para ver o :guilabel:`Relatório de " "rastreabilidade` atualizado, que inclui: um documento de " ":guilabel:`referência`, o :guilabel:`produto` que está sendo rastreado, o " @@ -7550,9 +7550,9 @@ msgid "" msgstr "" "Depois que a :abbr:`SDC (solicitação de cotação) ` é confirmada, ela se " "torna um pedido de compra e um recebimento do envio direto é criado e " -"vinculado a ele. O recibo pode ser visualizado clicando no botão inteligente" -" :guilabel:`Recebimento` no canto superior direito do formulário de pedido " -"de compra." +"vinculado a ele. O recebimento pode ser visualizado clicando no botão " +"inteligente :guilabel:`Recebimento` no canto superior direito do formulário " +"de pedido de compra." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 msgid "" @@ -7570,10 +7570,11 @@ msgid "" ":guilabel:`Validate` button at the top left of the dropship receipt to " "confirm the delivered quantity." msgstr "" -"O recibo de dropship listará o fornecedor na seção :guilabel:`Receber de` e " -"o cliente na seção :guilabel:`Local de destino`. Após a entrega do produto " -"ao cliente, clique no botão :guilabel:`Validar` no canto superior esquerdo " -"do recebimento do envio direto para confirmar a quantidade entregue." +"O recebimento do envio direto listará o fornecedor na seção " +":guilabel:`Receber de` e o cliente na seção :guilabel:`Local de destino`. " +"Após a entrega do produto ao cliente, clique no botão :guilabel:`Validar` no" +" canto superior esquerdo do recebimento do envio direto para confirmar a " +"quantidade entregue." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 msgid "Validate the dropship receipt after delivery." @@ -8873,6 +8874,8 @@ msgid "" "Visualization of the determination of planned MO date manufacturing lead " "times." msgstr "" +"Visualização da determinação dos prazos de entrega de fabricação com a data " +"de MO planejada." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:247 msgid "Manufacturing lead time" @@ -8884,6 +8887,9 @@ msgid "" "navigating to :menuselection:`Manufacturing app --> Products --> Products`, " "and select the desired product." msgstr "" +"Configure o prazo de entrega de fabricação diretamente no formulário do " +"produto, navegando até o :menuselection:`app Fabricação --> Produtos --> " +"Produtos` e selecione o produto desejado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 msgid "" @@ -8891,17 +8897,24 @@ msgid "" "needed to the manufacture the product in the :guilabel:`Manufacturing Lead " "Time` field." msgstr "" +"Na guia :guilabel:`Inventário` do produto, especifique os dias de calendário" +" necessários para a fabricação do produto no campo :guilabel:`Prazo de " +"entrega de fabricação`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 msgid "" "Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly " "in the :guilabel:`Inventory` tab of the product." msgstr "" +"Especifique um :guilabel:`prazo de entrega de fabricação` de 14 dias para um" +" produto diretamente na aba :guilabel:`Inventário` do produto." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 msgid "" "View of the manufacturing lead time configuration from the product form." msgstr "" +"Visualização da configuração do prazo de entrega de fabricação no formulário" +" do produto." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 msgid "" @@ -8909,6 +8922,9 @@ msgid "" "*expected delivery date*, indicated in the :guilabel:`Scheduled Date` field " "of the :abbr:`DO (Delivery Order)`." msgstr "" +"Estabeleça um prazo :abbr:`ordem de produção`, com base na *data de entrega " +"prevista*, indicada no campo :guilabel:`data programada` do :abbr:`pedido de" +" entrega`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 msgid "" @@ -8917,12 +8933,17 @@ msgid "" " calculated as the *expected delivery date* subtracted by the manufacturing " "lead time." msgstr "" +"O prazo final da :abbr:`ordem de produção`, que é o campo :guilabel:`data " +"programada` na :abbr:`ordem de produção)`, é calculado como a *data de " +"entrega prevista* subtraída pelo prazo de entrega de fabricação." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 msgid "" "This ensures the manufacturing process begins on time, in order to meet the " "delivery date." msgstr "" +"Isso garante que o processo de fabricação comece a tempo, a fim de cumprir a" +" data de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 msgid "" @@ -8931,16 +8952,22 @@ msgid "" " (:dfn:`the number of operations that can be performed at the work center " "simultaneously`)." msgstr "" +"No entanto, é importante observar que os prazos de entrega são baseados em " +"dias corridos. Os tempos de espera **não** consideram fins de semana, " +"feriados ou *capacidade do centro de trabalho* (:dfn:`o número de operações " +"que podem ser realizadas no centro de trabalho simultaneamente`)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 msgid ":ref:`Manufacturing planning <manufacturing/management/use_mps>`" -msgstr "" +msgstr ":ref:`Planejamento de fabricação <manufacturing/management/use_mps>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 msgid "" ":ref:`Configure automatic MO scheduling with reordering rules " "<inventory/management/reordering_rules>`" msgstr "" +":ref:`Configurar agendamento automático de ordens de produção com regras de " +"reposição <inventory/management/reordering_rules>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 msgid "" @@ -8949,10 +8976,14 @@ msgid "" "date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment " "date is August 1st." msgstr "" +"A data de envio programada de um produto no :abbr:`pedido de entrega` é 15 " +"de agosto. O produto requer 14 dias para ser fabricado. Portanto, a data " +"final para iniciar a :abbr:`ordem de produção)` para cumprir o prazo do " +"compromisso é 1º de agosto." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 msgid "Manufacturing security lead time" -msgstr "" +msgstr "Tempo de margem de segurança da fabricação" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 msgid "" @@ -8961,6 +8992,10 @@ msgid "" " :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead " "Time`, and click the checkbox to enable the feature." msgstr "" +"*O lead time de segurança de fabricação* é definido globalmente para a " +"empresa no :menuselection:`app Fabricação --> Configuração --> Definições`. " +"Sob o título :guilabel:`Planejamento`, localize a caixa :guilabel:`Margem de" +" segurança` e clique na caixa de seleção para ativar o recurso." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 msgid "" @@ -9222,9 +9257,8 @@ msgid "" "delivery order associated with the sales order." msgstr "" "Um botão inteligente :guilabel:`Entrega` aparece no canto superior direito " -"do formulário de cotação. Ao clicar nele, são exibidos o pedido de " -"separação, o pedido de embalagem e o pedido de entrega associados ao pedido " -"de venda." +"do formulário de cotação. Ao clicar nele, são exibidos a ordem de separação," +" a ordem de embalagem e o pedido de entrega associados ao pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 msgid "" @@ -9244,8 +9278,8 @@ msgid "" "order is confirmed. To view these transfers, go to " ":menuselection:`Inventory --> Operations --> Transfers`." msgstr "" -"Os pedidos de coleta, embalagem e entrega serão criados assim que o pedido " -"de vendas for confirmado. Para visualizar essas transferências, vá para " +"As ordens de separação, embalagem e entrega serão criadas assim que o pedido" +" de vendas for confirmado. Para visualizar essas transferências, vá para " ":menuselection:`Inventário --> Operações --> Transferências`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 @@ -9253,6 +9287,8 @@ msgid "" "Ready status for the pick operation while the packing and delivery operations are waiting\n" "another operation." msgstr "" +"Status de prontidão da operação de separação enquanto as operações de embalagem e entrega estão aguardando\n" +"outra operação." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:73 msgid "" @@ -9263,6 +9299,12 @@ msgid "" "completed. The status of the delivery order will only change to " ":guilabel:`Ready` when the packing has been marked :guilabel:`Done`." msgstr "" +"O status de separação será :guilabel:`Pronto`, pois o produto deve ser " +"retirado do estoque antes de ser embalado. O status da ordem de embalagem e " +"da ordem de entrega será :guilabel:`Aguardando outra operação`, pois a " +"embalagem e a entrega não podem ocorrer até que a separação seja concluída. " +"O status do pedido de entrega só será alterado para :guilabel:`Pronto` " +"quando a embalagem for marcada como :guilabel:`concluída`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:79 msgid "" @@ -9270,10 +9312,14 @@ msgid "" ":guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart " "button in the :guilabel:`Pick` kanban card." msgstr "" +"O recebimento também pode ser encontrado no aplicativo *Inventário*. No " +"painel :guilabel:`Visão geral`, clique no botão inteligente :guilabel:`1 a " +"processar` no cartão kanban :guilabel:`Separação`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 msgid "The pick order can be seen in the Inventory Kanban view." msgstr "" +"A ordem de separação pode ser vista na visualização Kanban do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 msgid "" @@ -9284,15 +9330,21 @@ msgid "" "products which have been previously picked are automatically reserved on the" " packing order." msgstr "" +"Clique na separação para processar. Se o produto estiver em estoque, o Odoo " +"reservará o produto automaticamente. Clique em :guilabel:`Validar` para " +"marcar a separação como concluída e completar a transferência para a " +":guilabel:`zona de embalagem`. Em seguida, a ordem de embalagem estará " +"pronta. Como os documentos estão vinculados, os produtos que foram separados" +" anteriormente serão automaticamente reservados na ordem de embalagem." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "Validate the picking by clicking Validate." -msgstr "" +msgstr "Valide a separação clicando em Validar." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 msgid "Process a packing" -msgstr "" +msgstr "Processar uma embalagem" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 msgid "" @@ -9301,22 +9353,31 @@ msgid "" ":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " "button in the :guilabel:`Pack` kanban card." msgstr "" +"A ordem de embalagem estará pronta para ser processada assim que a separação" +" for concluída e poderá ser encontrada no painel da :guilabel:`Visão geral` " +"do aplicativo :guilabel:`Inventário`. Clique no botão inteligente " +":guilabel:`1 a processar` no cartão kanban :guilabel:`Embalagem`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 msgid "The packing order can be seen in the Inventory kanban view." msgstr "" +"A ordem de embalagem pode ser vista na visualização Kanban do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 msgid "" "Click on the packing order associated with the sales order, then click on " ":guilabel:`Validate` to complete the packing." msgstr "" +"Clique na ordem de embalagem associada ao pedido de venda e, em seguida, " +"clique em :guilabel:`Validar` para concluir a embalagem." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 msgid "" "Click Validate on the packing order to transfer the product from the packing zone to the\n" "output location." msgstr "" +"Clique em Validar na ordem de embalagem para transferir o produto da zona de embalagem para o local de \n" +"saída." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 msgid "" @@ -9324,10 +9385,13 @@ msgid "" ":guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` " "location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" +"Depois que a ordem de embalagem é validada, o produto deixa o local " +":guilabel:`WH/Packing Zone` e vai para o local :guilabel:`WH/Output`. Em " +"seguida, o status do documento será alterado para :guilabel:`Concluído`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 msgid "Process a delivery" -msgstr "" +msgstr "Processar uma entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:121 msgid "" @@ -9336,16 +9400,24 @@ msgid "" ":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " "button in the :guilabel:`Delivery Orders` kanban card." msgstr "" +"O pedido de entrega estará pronto para ser processado assim que a embalagem " +"for concluída e poderá ser encontrado no painel :guilabel:`Visão geral` do " +"aplicativo :guilabel:`Inventário`. Clique no botão inteligente :guilabel:`1 " +"a processar` no cartão kanban :guilabel:`Pedidos de entrega`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 msgid "The delivery order can be seen in the Delivery Orders Kanban view." msgstr "" +"A ordem de entrega pode ser vista no modo de visualização Kanban de ordens " +"de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:129 msgid "" "Click on the delivery order associated with the sales order, then click on " ":guilabel:`Validate` to complete the move." msgstr "" +"Clique no pedido de entrega associado ao pedido de vendas e, em seguida, " +"clique em :guilabel:`Validar` para concluir a mudança." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 @@ -9353,6 +9425,8 @@ msgid "" "Click Validate on the delivery order to transfer the product from the output location to\n" "the customer location." msgstr "" +"Clique em Validar na ordem de entrega para transferir o produto do local de saída para\n" +"o local do cliente." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:137 msgid "" @@ -9361,10 +9435,13 @@ msgid "" ":guilabel:`Partners/Customers` location. Then, the status of the document " "will change to :guilabel:`Done`." msgstr "" +"Quando a ordem de entrega é validada, o produto sai do local " +":guilabel:`WH/Output` e vai para o local :guilabel:`Partners/Customers`. Em " +"seguida, o status do documento será alterado para :guilabel:`Concluído`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 msgid "Process receipts and deliveries in one step" -msgstr "" +msgstr "Processar recebimentos e entregas em uma etapa" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 msgid "" @@ -9373,6 +9450,10 @@ msgid "" "stock to the customer; the default setting for warehouses in Odoo is one " "step receipts and deliveries." msgstr "" +"Por padrão, as remessas recebidas são configuradas para entrarem direto no " +"estoque, e as remessas enviadas são configuradas para serem entregues " +"diretamente do estoque para o cliente; a configuração padrão para armazéns " +"no Odoo é de recebimentos e entregas em uma etapa." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 msgid "" @@ -9380,22 +9461,28 @@ msgid "" "steps. For example, products can be received in one step, but shipped in " "three steps." msgstr "" +"As remessas enviadas e recebidas não precisam ser configuradas com as mesmas" +" etapas. Por exemplo, os produtos podem ser recebidos em uma etapa, mas " +"enviados em três etapas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 msgid "" "In the following example, one step will be used for both receipts and " "deliveries." msgstr "" +"No exemplo a seguir, será usada uma etapa para recebimentos e entregas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 msgid "Configure the warehouse" -msgstr "" +msgstr "Configurar o armazém" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 msgid "" "If another receiving or shipping configuration is set on the warehouse, they" " can easily be set back to the one step setting." msgstr "" +"Se outra configuração de recebimento ou remessa for definida no armazém, é " +"fácil voltar para a configuração de uma etapa." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:23 msgid "" @@ -9406,12 +9493,20 @@ msgid "" ":guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 " "step)` for :guilabel:`Outgoing Shipments`." msgstr "" +"Comece navegando até :menuselection:`Inventário --> Configuração --> " +"Armazéns` e clique no armazém desejado para editá-lo. Em seguida, na aba " +":guilabel:`Configuração do armazén`, na seção :guilabel:`Envios`, selecione " +":guilabel:`Receber mercadorias diretamente (1 etapa)` para " +":guilabel:`Remessas recebidas` e/ou :guilabel:`Entregar mercadorias " +"diretamente (1 etapa)` para :guilabel:`Remessas enviadas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 msgid "" "Set incoming and outgoing shipment options to receive and deliver in one " "step." msgstr "" +"Defina opções de remessa recebidas e enviadas para receber e entregar em uma" +" única etapa." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:34 msgid "Receive goods directly (1 step)" @@ -9421,7 +9516,7 @@ msgstr "Receber mercadorias diretamente (1 etapa)" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 msgid "Create a purchase order" -msgstr "" +msgstr "Criar um pedido de compra" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 @@ -9432,6 +9527,12 @@ msgid "" ":guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` " "to finalize the quote as a new purchase order." msgstr "" +"No painel principal do aplicativo :menuselection:`Compras`, comece fazendo " +"uma nova cotação clicando em :guilabel:`Novo`. Em seguida, selecione (ou " +"crie) um :guilabel:`fornecedor` no campo suspenso, adicione um " +":guilabel:`produto` armazenável às linhas do pedido e clique em " +":guilabel:`Confirmar pedidp` para finalizar a cotação como um novo pedido de" +" compra." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:98 @@ -9440,10 +9541,14 @@ msgid "" "the :abbr:`PO (purchase order)` form — click it to reveal the associated " "receipt for the purchase order." msgstr "" +"Um botão inteligente :guilabel:`Recebimento` aparecerá no canto superior " +"direito do formulário do :abbr:`pedido de compra` - clique nele para revelar" +" o recebimento associado ao pedido de compra." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 msgid "Receipt smart button appears on the confirmed purchase order." msgstr "" +"O botão inteligente do recebimento aparece no pedido de compra confirmado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 @@ -9452,26 +9557,32 @@ msgid "" "application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " "to Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" +"Os recibos de pedidos de compra também podem ser encontrados no aplicativo " +":menuselection:`Inventário`. No painel :guilabel:`Visão geral`, clique no " +"botão inteligente :guilabel:`Nº a processar` no cartão kanban " +":guilabel:`Recebimentos`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "Receipt kanban card's 1 to Process smart button." -msgstr "" +msgstr "Botão inteligente do cartão Kanban de recebimento de 1 a processar." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 msgid "Process the receipt" -msgstr "" +msgstr "Processar o recebimento" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 msgid "" "When viewing the receipt (associated with the purchase order above), click " ":guilabel:`Validate` to then complete the receipt." msgstr "" +"Ao visualizar o recebimento (associado ao pedido de compra acima), clique em" +" :guilabel:`Validar` para concluir o recebimento." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 msgid "Validate the purchase order via the Validate smart button." -msgstr "" +msgstr "Valide o pedido de compra pelo botão inteligente Validar." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 msgid "" @@ -9480,12 +9591,18 @@ msgid "" "enables the :guilabel:`Detailed Operations` screen to pop-up. This allows " "the location(s) to be specified for the received product(s)." msgstr "" +"Se o :guilabel:`Locais de armazenamento` estiver ativado, clicar no ícone de" +" detalhes :guilabel:`≣ (lista)` ao lado do ícone de exclusão :guilabel:`🗑️ " +"(lixeira)` permite que a tela :guilabel:`Operações detalhadas` seja exibida." +" Isso permite que os locais sejam especificados para os produtos recebidos" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "" "Select the Storage Location for the products being received in the Detailed Operations\n" "pop-up." msgstr "" +"Selecione o local de armazenamento para os produtos que estão sendo recebidos na janela pop-up\n" +"Operações detalhadas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:80 msgid "" @@ -9495,6 +9612,11 @@ msgid "" "of the document will change to :guilabel:`Done`, thus completing the " "reception process in one step." msgstr "" +"Depois que o recebimento é validado, o produto deixa o :guilabel:`Local do " +"fornecedor` e entra no :guilabel:`WH/Stock Location`. Quando chegar a esse " +"local, ele estará disponível para fabricação, vendas, etc. Em seguida, o " +"status do documento será alterado para :guilabel:`Concluído`, concluindo " +"assim o processo de recebimento em uma única etapa." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:88 msgid "Deliver goods directly (1 step)" @@ -9508,6 +9630,12 @@ msgid "" ":guilabel:`Product` that is in stock to the order lines, and click " ":guilabel:`Confirm` to finalize the quotation as a sales order." msgstr "" +"Comece navegando até o painel principal do aplicativo " +":menuselection:`Vendas` e crie uma nova cotação clicando em " +":guilabel:`Novo`. Em seguida, selecione (ou crie) um :guilabel:`cliente` no " +"campo suspenso, adicione um :guilabel:`produto` armazenável que esteja em " +"estoque às linhas do pedido e clique em :guilabel:`Confirmar` para finalizar" +" a cotação como um pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 msgid "" @@ -9515,10 +9643,15 @@ msgid "" "the :abbr:`SO (Sales Order)` form — click it to reveal the associated " "delivery order for the sales order." msgstr "" +"Um botão inteligente :guilabel:`Entrega` aparecerá no canto superior direito" +" do formulário do :abbr:`Pedido de venda (SO)` - clique nele para revelar o " +"pedido de entrega associado ao pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 msgid "The Delivery smart button appears after the sales order is confirmed." msgstr "" +"O botão inteligente Entrega é exibido depois que o pedido de venda é " +"confirmado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:109 msgid "" @@ -9526,25 +9659,32 @@ msgid "" "application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " "to Process` smart button in the :guilabel:`Delivery Orders` kanban card." msgstr "" +"Os pedidos de entrega também podem ser encontrados no aplicativo " +":menuselection:`Inventário`. No painel :guilabel:`Visão geral`, clique no " +"botão inteligente :guilabel:`Nº a processar` no cartão kanban " +":guilabel:`Pedidos de entrega`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 msgid "Delivery Orders kanban card's 1 to Process smart button." msgstr "" +"Botão inteligente do cartão Kanban de pedidos de entrega com 1 a processar." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 msgid "Process the delivery" -msgstr "" +msgstr "Processar a entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 msgid "" "When viewing the delivery order (associated with the sales order above), " "click :guilabel:`Validate` to then complete the delivery." msgstr "" +"Ao visualizar o pedido de entrega (associado ao pedido de venda acima), " +"clique em :guilabel:`Validar` para concluir a entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 msgid "Validate the delivery order." -msgstr "" +msgstr "Valide o pedido de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:127 msgid "" @@ -9553,10 +9693,14 @@ msgid "" " location`. Then, the status of the document will change to " ":guilabel:`Done`, thus completing delivery in one step." msgstr "" +"Depois que a ordem de separação é validada, o produto sai do local " +":guilabel:`WH/Stock` e vai para o local :guilabel:`Partners/Customers`. Em " +"seguida, o status do documento será alterado para :guilabel:`Concluído`, " +"concluindo assim a entrega em uma etapa." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 msgid "Process receipts and deliveries in two steps" -msgstr "" +msgstr "Processar recebimentos e entregas em duas etapas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:7 msgid "" @@ -9566,6 +9710,13 @@ msgid "" "receipts work best when various storage locations are being used, such as " "locked or secured areas, freezers and refrigerators, or various shelves." msgstr "" +"Dependendo dos processos comerciais de uma empresa, podem ser necessárias " +"várias etapas antes de receber ou enviar produtos. No processo de " +"recebimento em duas etapas, os produtos são recebidos em uma área de entrada" +" e, em seguida, transferidos para o estoque. Os recebimentos em duas etapas " +"funcionam melhor quando vários locais de armazenamento estão sendo usados, " +"como áreas trancadas ou seguras, freezers e refrigeradores ou várias " +"prateleiras." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 msgid "" @@ -9574,6 +9725,10 @@ msgid "" "products are not available for further processing until they are transferred" " into stock." msgstr "" +"Os produtos podem ser classificados de acordo com o local onde serão " +"armazenados, e os funcionários podem estocar todos os produtos que vão para " +"um local específico. Os produtos não estão disponíveis para processamento " +"posterior até que sejam transferidos para o estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:16 msgid "" @@ -9581,6 +9736,9 @@ msgid "" " are picked from the warehouse according to their removal strategy, and " "brought to an output location before being shipped." msgstr "" +"No processo de entrega em duas etapas, os produtos que fazem parte de um " +"pedido de entrega são separados no armazém de acordo com sua estratégia de " +"remoção e levados a um local de saída antes de serem enviados." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 msgid "" @@ -9590,6 +9748,11 @@ msgid "" "being picked need to be selected based on their receipt date or expiration " "date." msgstr "" +"Uma situação em que isso seria útil é quando se usa uma estratégia de " +"remoção :abbr:`PEPS (primeiro a entrar, primeiro a sair)`, :abbr:`UEPS " +"(último a entrar, primeiro a sair)` ou :abbr:`PVPS (primeiro a vencer, " +"primeiro a sair)`, em que os produtos que estão sendo separados precisam ser" +" selecionados com base na data de recebimento ou na data de validade." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 msgid "" @@ -9600,10 +9763,17 @@ msgid "" "products can be received in two steps, but shipped in one step. In the " "following example, two steps will be used for both receipts and deliveries." msgstr "" +"O Odoo é configurado por padrão para :ref:`receber e entregar mercadorias em" +" uma etapa <inventory/receipts_delivery_one_step>`, portanto, as " +"configurações precisam ser alteradas para utilizar recebimentos e entregas " +"em duas etapas. As remessas recebidas e enviadas não precisam ser definidas " +"para ter as mesmas etapas. Por exemplo, os produtos podem ser recebidos em " +"duas etapas, mas enviados em uma etapa. No exemplo a seguir, serão usadas " +"duas etapas para os recebimentos e as entregas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 msgid "Configure multi-step routes" -msgstr "" +msgstr "Configurar rotas em várias etapas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 msgid "" @@ -9612,12 +9782,18 @@ msgid "" ":guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` " "the changes." msgstr "" +"Primeiro, certifique-se de que a opção :guilabel:`Rotas de várias etapas` " +"esteja habilitada em :menuselection:`Inventário --> Configuração --> " +"Definições`, sob o título :guilabel:`Armazém`. Depois de ativar a " +"configuração, :guilabel:`salve` as alterações." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 msgid "" "Activating the :guilabel:`Multi-Step Routes` setting will also activate the " ":guilabel:`Storage Locations` feature." msgstr "" +"A ativação da configuração :guilabel:`Rotas com várias etapas` também " +"ativará o recurso :guilabel:`Locais de armazenamento`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 msgid "" @@ -9625,6 +9801,9 @@ msgid "" "deliveries. Go to :menuselection:`Inventory --> Configuration --> " "Warehouses`, and click on the warehouse to change the warehouse settings." msgstr "" +"Em seguida, o depósito precisa ser configurado para recebimentos e entregas " +"em duas etapas. Vá para :menuselection:`Inventário --> Configuração --> " +"Armazém` e clique no depósito para alterar as configurações do depósito." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 msgid "" @@ -9632,12 +9811,18 @@ msgid "" " :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and " "then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." msgstr "" +"Em seguida, selecione :guilabel:`Receber mercadorias na entrada e depois " +"estocar (2 etapas)` para :guilabel:`Remessas recebidas`, e :guilabel:`Enviar" +" mercadorias na saída e depois entregar (2 etapas)` para :guilabel:`Remessas" +" enviadas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "" "Set incoming and outgoing shipment options to receive and deliver in two " "steps." msgstr "" +"Definir opções de remessa de entrada e saída para receber e entregar em duas" +" etapas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 msgid "" @@ -9649,10 +9834,17 @@ msgid "" "form, update the :guilabel:`Location Name`, and make any other changes (if " "necessary)." msgstr "" +"A ativação de recebimentos e entregas em duas etapas criará novos locais de " +"*entrada* e *saída* que, por padrão, são rotulados como :guilabel:`WH/Input`" +" e :guilabel:`WH/Output`, respectivamente, no painel :guilabel:`Locais`. " +"Para renomear esses locais, vá para :menuselection:`Configuração --> Locais`" +" e selecione o :guilabel:`local` a ser alterado. No formulário de local, " +"atualize o :guilabel:`nome do local` e faça qualquer outra alteração (se " +"necessário)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 msgid "Process a receipt in two steps (input + stock)" -msgstr "" +msgstr "Processar um recebimento em duas etapas (entrada + estoque)" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 msgid "" @@ -9663,6 +9855,12 @@ msgid "" "warehouse from the drop-down selection that includes the `Receipts` label at" " the end of the name." msgstr "" +"Para empresas com vários armazéns que têm configurações de etapas " +"diferentes, o campo :guilabel:`Entregar para` no formulário :abbr:`pedido de" +" compra (PO)` pode precisar ser especificado como o *local de entrada* " +"correto conectado ao armazém de duas etapas, o que pode ser feito " +"selecionando o armazém na lista suspensa que inclui o rótulo `Recebimentos` " +"no final do nome." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 msgid "" @@ -9670,15 +9868,22 @@ msgid "" "smart button will appear in the top of the :abbr:`PO (Purchase Order)` form " "— click it to reveal the associated receipt." msgstr "" +"Após confirmar o :abbr:`pedido de compra (PO)`, um botão inteligente " +":guilabel:`Recebimento` aparecerá na parte superior do formulário do " +":abbr:`PO` - clique nele para revelar o recebimento associado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "After confirming a purchase order, a Receipt smart button will appear." msgstr "" +"Depois de confirmar um pedido de compra, um botão inteligente de recebimento" +" será exibido." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 msgid "One receipt ready to process in the Inventory Overview kanban view." msgstr "" +"Um recebimento pronto para ser processado na visão kanban da Visão geral do " +"Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 msgid "" @@ -9690,6 +9895,13 @@ msgid "" "only change to :guilabel:`Ready` once the receipt has been marked as " ":guilabel:`Done`." msgstr "" +"O recebimento e a transferência interna serão criados assim que o pedido de " +"compra for confirmado. O status do recebimento será :guilabel:`Pronto`, pois" +" ele deve ser processado primeiro. O status da transferência interna será " +":guilabel:`Aguardando outra operação`, pois a transferência não pode ser " +"feita até que o recebimento seja concluído. O status da transferência " +"interna só será alterado para :guilabel:`Pronto` quando o recebimento for " +"marcado como :guilabel:`concluído`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 msgid "" @@ -9697,16 +9909,21 @@ msgid "" "click :guilabel:`Validate` to complete the receipt and move the product to " "the :guilabel:`Input Location`." msgstr "" +"Clique no :guilabel:`recebimento` associado ao pedido de compra e, em " +"seguida, clique em :guilabel:`Validar` para concluir o recebimento e mover o" +" produto para o :guilabel:`Local de entrada`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "" "Validate the receipt by clicking Validate, then the product will be transferred to the\n" "WH/Input location." msgstr "" +"Valide o recebimento clicando em Validar e, em seguida, o produto será transferido para o local \n" +"WH/Input." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 msgid "Process the internal transfer" -msgstr "" +msgstr "Processar a transferência interna" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 msgid "" @@ -9716,6 +9933,11 @@ msgid "" "dashboard, click the :guilabel:`# To Process` smart button in the " ":guilabel:`Internal Transfers` kanban card." msgstr "" +"Quando o produto estiver no :guilabel:`Local de entrada`, a transferência " +"interna estará pronta para mover o produto para o estoque. Navegue até o " +"aplicativo :menuselection:`Inventário` e, no painel :guilabel:`Visão geral " +"do inventário`, clique no botão inteligente :guilabel:`Nº a processar` no " +"cartão kanban :guilabel:`Transferências internas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 @@ -9723,6 +9945,8 @@ msgid "" "One Internal Transfer ready to process in the Inventory Overview kanban " "view." msgstr "" +"Uma transferência interna pronta para ser processada na visão kanban da " +"Visão geral do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 msgid "" @@ -9731,14 +9955,19 @@ msgid "" "stock. Once the transfer is validated, the product enters the stock and is " "available for customer deliveries or manufacturing orders." msgstr "" +"Clique na :guilabel:`transferência` associada ao pedido de compra e, em " +"seguida, clique em :guilabel:`Validar` para concluir o recebimento e mover o" +" produto para o estoque. Depois que a transferência for validada, o produto " +"entrará no estoque e estará disponível para entregas ao cliente ou ordens de" +" produção." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "Validate the internal transfer to move the item to stock." -msgstr "" +msgstr "Valide a transferência interna para mover o item para o estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 msgid "Process a delivery order in two steps (pick + ship)" -msgstr "" +msgstr "Processar um pedido de entrega em duas etapas (separação + envio)" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 msgid "" @@ -9746,6 +9975,10 @@ msgid "" ":guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable " ":guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." msgstr "" +"No aplicativo :menuselection:`Vendas`, crie uma nova cotação clicando em " +":guilabel:`Novo`. Selecione (ou crie) um :guilabel:`cliente`, adicione um " +":guilabel:`produto` armazenável às linhas do pedido e clique em " +":guilabel:`Confirmar`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 msgid "" @@ -9754,12 +9987,18 @@ msgid "" "Click the :guilabel:`Delivery` smart button to reveal the associated " "receipt." msgstr "" +"Depois de confirmar o :abbr:`pedido de venda (SO)`, um botão inteligente " +":guilabel:`Entrega` aparecerá na parte superior, acima do formulário " +":abbr:`SO`. Clique no botão inteligente :guilabel:`Entrega` para revelar o " +"recebimento associado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "" "After confirming the sales order, the Delivery smart button appears showing two items\n" "associated with it." msgstr "" +"Depois de confirmar o pedido de venda, o botão inteligente Entrega é " +"exibido, mostrando dois itens associados a ele." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 msgid "" @@ -9767,14 +10006,19 @@ msgid "" "application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " "To Process` smart button in the :guilabel:`Pick` kanban card." msgstr "" +"Os recebimentos de pedidos de vendas também podem ser encontrados no " +"aplicativo :menuselection:`Inventário`. No painel :guilabel:`Overview`, " +"clique no botão inteligente :guilabel:`Nº a processar` no cartão Kanban " +":guilabel:`Separação`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 msgid "The pick order can be seen in the Inventory kanban view." msgstr "" +"A ordem de separação pode ser vista na visualização do Kanban do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 msgid "Process the picking" -msgstr "" +msgstr "Processar a separação" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 msgid "" @@ -9783,6 +10027,10 @@ msgid "" "reveal the :guilabel:`Transfers` dashboard, which lists both the picking and" " the delivery orders." msgstr "" +"A ordem de separação e entrega será criada assim que o pedido de venda for " +"confirmado. Quando o botão inteligente :guilabel:`Entrega` for exibido, " +"clique nele para abrir o painel :guilabel:`Transferências`, que lista as " +"ordens de separação e entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 msgid "" @@ -9793,12 +10041,20 @@ msgid "" "order will only change to :guilabel:`Ready` once the picking has been marked" " as :guilabel:`Done`." msgstr "" +"O status da separação será :guilabel:`Pronta`, pois o produto deve ser " +"retirado do estoque antes de ser enviado. O status da ordem de entrega será " +":guilabel:`Aguardando outra operação`, pois a entrega não poderá ser feita " +"até que o picking seja concluído. O status do pedido de entrega só será " +"alterado para :guilabel:`Pronto` quando a separação for marcada como " +":guilabel:`concluída`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "" "Ready status for the pick operation while the delivery operation is Waiting Another\n" "Operation." msgstr "" +"Status \"Pronto\" da operação de separação, enquanto a operação de entrega está Aguardando outra\n" +"operação." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 msgid "" @@ -9809,6 +10065,12 @@ msgid "" " the products which have been previously picked are automatically reserved " "on the delivery order." msgstr "" +"Clique na ordem de entrega da separação para começar a processá-la. Se o " +"produto estiver em estoque, o Odoo reservará automaticamente o produto. " +"Clique em :guilabel:`Validar` para marcar a separação como " +":guilabel:`concluída`, então a ordem entrega estará pronta para ser " +"processada. Como os documentos estão vinculados, os produtos que foram " +"retirados anteriormente são automaticamente reservados na ordem de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 msgid "" @@ -9818,6 +10080,11 @@ msgid "" "Process` smart button in the :guilabel:`Delivery Orders` kanban card to " "begin." msgstr "" +"A ordem de entrega estará pronta para ser processada assim que a separação " +"for concluída e poderá ser encontrado no aplicativo " +":menuselection:`Inventário`, no painel :guilabel:`Visão geral de " +"inventário`. Clique no botão inteligente :guilabel:`Nº a processar` no " +"cartão kanban :guilabel:`Ordens de entrega` para começar." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 msgid "" @@ -9826,16 +10093,24 @@ msgid "" " and choosing the delivery order on the :guilabel:`Transfers` page (which " "should now be marked as :guilabel:`Ready`)." msgstr "" +"A ordem de entrega associada ao :abbr:`pedido de venda (SO)` também pode ser" +" acessada rapidamente clicando no botão inteligente :guilabel:`Entrega` " +"novamente e escolhendo a ordem de entrega na página " +":guilabel:`Transferências` (que agora deve estar marcada como " +":guilabel:`Pronto`)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 msgid "The delivery order can be seen in the Inventory Kanban view." msgstr "" +"A ordem de entrega pode ser vista na visualização Kanban do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 msgid "" "Click on the delivery order associated with the :abbr:`SO (Sales Order)`, " "then click on :guilabel:`Validate` to complete the move." msgstr "" +"Clique na ordem de entrega associada ao :abbr:`pedido de venda` e, em " +"seguida, clique em :guilabel:`Validar` para concluir a transferência." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 msgid "" @@ -9844,10 +10119,14 @@ msgid "" "moves to the :guilabel:`Partners/Customers` location. Then, the status of " "the document will change to :guilabel:`Done`." msgstr "" +"Depois que a ordem de entrega é validada, o produto deixa o local " +":guilabel:`WH/Output` no painel :guilabel:`Transferências` e vai para o " +"local :guilabel:`Partners/Customers`. Em seguida, o status do documento será" +" alterado para :guilabel:`Concluído`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 msgid "Process receipts in three steps" -msgstr "" +msgstr "Processar os recebimentos em três etapas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:7 msgid "" @@ -9855,6 +10134,9 @@ msgid "" " suppliers. To accomplish this, Odoo has a three-step process for receiving " "goods." msgstr "" +"Algumas empresas exigem um processo de controle de qualidade antes de " +"receber mercadorias dos fornecedores. Para isso, o Odoo tem um processo de " +"três etapas para o recebimento de mercadorias." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:10 msgid "" @@ -9864,6 +10146,11 @@ msgid "" "available for further processing until they are transferred out of the " "quality area and into stock." msgstr "" +"No processo de recebimento em três etapas, os produtos são recebidos em uma " +"área de entrada e, em seguida, transferidos para uma área de qualidade para " +"inspeção. Os produtos que passam no controle de qualidade são transferidos " +"para o estoque. Os produtos não estão disponíveis para processamento " +"adicional até que sejam transferidos da área de qualidade para o estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:18 msgid "" @@ -9874,11 +10161,20 @@ msgid "" " Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes`" " will also activate *Storage Locations*." msgstr "" +"O Odoo é configurado por padrão para :ref:`receber e entregar mercadorias em" +" uma etapa <inventory/receipts_delivery_one_step>`, portanto, as " +"configurações precisam ser alteradas para utilizar recebimentos em três " +"etapas. Primeiro, certifique-se de que a opção *Rotas de várias etapas* " +"esteja ativada em :menuselection:`Inventário --> Configuração --> Definições" +" --> Armazém`. Observe que a ativação de :guilabel:`Rotas de várias etapas` " +"também ativará *Locais de armazenamento*." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "" "Activate multi-step routes and storage locations in Inventory settings." msgstr "" +"Ativar rotas de várias etapas e locais de armazenamento nas configurações do" +" Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 msgid "" @@ -9887,6 +10183,10 @@ msgid "" " and select the desired warehouse to be edited. Doing so reveals the detail " "form for that specific warehouse." msgstr "" +"Em seguida, o armazém precisa ser configurado para recebimentos em três " +"etapas. Para fazer isso, vá para o :menuselection:`app Inventário --> " +"Configuração --> Armazéns` e selecione o lugar desejado para editar. Isso " +"abre o formulário detalhado para esse armazém específico." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 msgid "" @@ -9894,10 +10194,13 @@ msgid "" "goods in input, then quality and then stock (3 steps)` for " ":guilabel:`Incoming Shipments`." msgstr "" +"Na página do formulário de detalhes do :guilabel:`Armazém`, selecione " +":guilabel:`Receber mercadorias na entrada, depois verificar qualidade e " +"então estocar (3 passos)` para :guilabel:`Remessas recebidas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "Set incoming shipment option to receive in three steps." -msgstr "" +msgstr "Definir a opção de remessa recebidas para receber em três etapas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 msgid "" @@ -9907,10 +10210,15 @@ msgid "" "Configuration --> Locations`, then click on the desired location to change " "(or update) the name." msgstr "" +"A ativação de recebimentos e entregas em três etapas cria dois novos locais " +"internos: *Entrada* (WH/Input) e *Controle de qualidade* (WH/Quality " +"Control). Para renomear esses locais, acesse :menuselection:`app Inventário " +"--> Configuração --> Locais` e, em seguida, clique no local desejado para " +"alterar (ou atualizar) o nome." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 msgid "Receive in three steps (input + quality + stock)" -msgstr "" +msgstr "Receber em três etapas (entrada + qualidade + estoque)" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 msgid "" @@ -9920,6 +10228,11 @@ msgid "" ":guilabel:`Vendor`, add a storable :guilabel:`Product`, and click " ":guilabel:`Confirm Order`." msgstr "" +"Para criar uma nova :abbr:`SDC (Solicitação de cotação)`, navegue até o " +":menuselection:`app Compras --> Novo`, que revela uma página de formulário " +"da :abbr:`SDC` em branco. Nessa página, selecione um :guilabel:`fornecedor`," +" adicione um :guilabel:`produto` armazenável e clique em " +":guilabel:`Confirmar pedido`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 msgid "" @@ -9927,10 +10240,13 @@ msgid "" "receipt will be associated with the purchase order. Clicking on the " ":guilabel:`Receipt` smart button will show the receipt order." msgstr "" +"Um botão inteligente :guilabel:`Recebimento` aparecerá no canto superior " +"direito, e o recebimento será associado ao pedido de compra. Ao clicar no " +"botão inteligente :guilabel:`Recebimento`, o pedido de recibo será exibido." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "Process a receipt" -msgstr "" +msgstr "Processar um recebimento" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 msgid "" @@ -9939,12 +10255,19 @@ msgid "" "confirmed. To view these transfers, go to :menuselection:`Inventory --> " "Operations --> Transfers`." msgstr "" +"Um recebimento e duas transferências internas (uma transferência para a " +"qualidade e uma transferência subsequente para o estoque) serão criados " +"assim que o pedido de compra for confirmado. Para visualizar essas " +"transferências, vá para :menuselection:`Inventário --> Operações --> " +"Transferências`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "" "The status of the three receipt transfers will show which operation is ready and which ones\n" "are waiting another operation." msgstr "" +"O status das três transferências de recebimentos mostrará qual operação está" +" pronta e quais estão aguardando outra operação." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 msgid "" @@ -9954,6 +10277,12 @@ msgid "" ":guilabel:`Waiting Another Operation`, since the transfers cannot be " "processed until the linked step before each transfer is completed." msgstr "" +"O status do recebimento que transfere o produto para o local de entrada será" +" :guilabel:`Pronto`, pois o recibo deve ser processado antes que qualquer " +"outra operação possa ocorrer. O status das duas transferências internas será" +" :guilabel:`Aguardando outra operação`, pois as transferências não podem ser" +" processadas até que a etapa vinculada antes de cada transferência seja " +"concluída." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 msgid "" @@ -9963,6 +10292,11 @@ msgid "" ":guilabel:`Ready` only after the transfer to quality has been marked " ":guilabel:`Done`." msgstr "" +"O status da primeira transferência interna para *qualidade* só mudará para " +":guilabel:`Pronto` quando o recebimento tiver sido marcado como " +":guilabel:`concluído`. O status da segunda transferência interna para o " +"*estoque* será marcado como :guilabel:`Pronto` somente depois que a " +"transferência para a qualidade for marcada como :guilabel:`concluída`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 msgid "" @@ -9970,10 +10304,16 @@ msgid "" " In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` " "smart button in the :guilabel:`Receipts` kanban card." msgstr "" +"O recebimento também pode ser encontrado no aplicativo " +":menuselection:`Inventário`. No painel :guilabel:`Visão geral`, clique no " +"botão inteligente :guilabel:`1 a processar` no cartão kanban " +":guilabel:`Recebimentos`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "One Receipt ready to process in the Inventory Overview kanban view." msgstr "" +"Um recebimento pronto para ser processado na visão kanban da Visão geral do " +"Inventário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 msgid "" @@ -9981,16 +10321,21 @@ msgid "" ":guilabel:`Validate` to complete the receipt and move the product to the " ":guilabel:`Input Location`." msgstr "" +"Clique no recebimento associado ao pedido de compra e, em seguida, clique em" +" :guilabel:`Validar` para concluir o recebimento e mover o produto para o " +":guilabel:`Local de entrada`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "" "Validate the receipt by clicking Validate, and the product will be transferred to the\n" "WH/Quality location." msgstr "" +"Valide o recebimento clicando em Validar e, em seguida, o produto será transferido para o local \n" +"WH/Quality." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Process a transfer to Quality Control" -msgstr "" +msgstr "Processar uma transferência para controle de qualidade" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 msgid "" @@ -10000,6 +10345,11 @@ msgid "" ":guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` " "kanban card." msgstr "" +"Quando o produto estiver no :guilabel:`Local de entrada`, a transferência " +"interna estará pronta para mover o produto para o :guilabel:`controle de " +"qualidade`. No painel de :guilabel:`Visão geral` do " +":menuselection:`Inventário`, clique no botão inteligente :guilabel:`1 a " +"processar` no cartão kanban :guilabel:`Transferências internas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 msgid "" @@ -10009,16 +10359,23 @@ msgid "" "the product is ready for the quality inspection, but is not available for " "manufacturing or delivery orders." msgstr "" +"Clique na :guilabel:`transferência` associada ao pedido de compra e, em " +"seguida, clique em :guilabel:`Validar` para concluir a transferência e mover" +" o produto para o local de :guilabel:`controle de qualidade`. Depois que a " +"transferência for validada, o produto estará pronto para o controle de " +"qualidade, mas não estará disponível para ordens de produção ou entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 msgid "" "Validate the internal transfer to move the item to the Quality Control " "location." msgstr "" +"Valide a transferência interna para mover o item para o local do controle de" +" qualidade." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 msgid "Process a transfer to stock" -msgstr "" +msgstr "Processar uma transferência para o estoque" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 msgid "" @@ -10027,6 +10384,11 @@ msgid "" ":guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process`" " smart button in the :guilabel:`Internal Transfers` Kanban card." msgstr "" +"Quando o produto estiver no local do :guilabel:`controle de qualidade`, a " +"transferência interna final estará pronta para mover o produto para o " +":guilabel:`estoque`. No painel de visão geral do :guilabel:`Inventário`, " +"clique no botão inteligente :guilabel:`1 a processar` no cartão Kanban " +":guilabel:`Transaferências internas`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 msgid "" @@ -10035,10 +10397,15 @@ msgid "" "product to stock. Once the transfer is validated, the product enters the " "stock and is available for customer deliveries or manufacturing orders." msgstr "" +"Clique na :guilabel:`transferência` final associada ao pedido de compra e, " +"em seguida, clique em :guilabel:`Validar` para concluir a transferência e " +"mover o produto para o estoque. Depois que a transferência for validada, o " +"produto entrará no estoque e estará disponível para entregas ao cliente ou " +"ordens de produção." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 msgid "Incoming shipments and delivery orders" -msgstr "" +msgstr "Remessas recebidas e ordens de entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 msgid "" @@ -10050,22 +10417,36 @@ msgid "" "settings can be configured for receipts and deliveries; they do not have to " "be configured to have the same number of steps." msgstr "" +"Há várias maneiras de lidar com a forma como um armazém recebe " +"(recebimentos) e envia (entregas) produtos. Dependendo de vários fatores, " +"como o tipo de produtos estocados e vendidos, o tamanho do armazém e a " +"quantidade de recebimentos e ordens de entrega confirmados diariamente, a " +"maneira como os produtos são tratados ao entrar e sair do armazém pode " +"variar muito. Diferentes configurações podem ser definidas para recebimentos" +" e entregas; não é preciso configurar para que tenham o mesmo número de " +"etapas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 msgid "" "`Using Routes (eLearning Tutorial) <https://www.odoo.com/slides/slide/using-" "routes-1018>`_" msgstr "" +"`Como usar rotas (Tutorial de e-Learning) " +"<https://www.odoo.com/slides/slide/using-routes-1018>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:13 msgid "" "`Push & Pull Rules (eLearning Tutorial) " "<https://www.odoo.com/slides/slide/push-pull-rules-1024>`_" msgstr "" +"`Regras Push e Pull (Tutorial de eLearning) " +"<https://www.odoo.com/slides/slide/push-pull-rules-1024>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 msgid "Choosing the right inventory flow to handle receipts and deliveries" msgstr "" +"Como escolher o fluxo de estoque correto para lidar com recebimentos e " +"entregas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:19 msgid "" @@ -10078,16 +10459,26 @@ msgid "" "performing quality checks on received products, or using special packaging " "on shipped products." msgstr "" +"Por padrão, o Odoo lida com envio e recebimento de três maneiras diferentes:" +" em uma, duas ou três etapas. A configuração mais simples é a de uma etapa, " +"que é a padrão. Cada etapa adicional necessária em um armazém, seja para o " +"processo de recebimento ou de envio, acrescentará uma camada adicional de " +"operações a serem executadas antes que um produto seja recebido ou enviado. " +"Essas configurações dependem inteiramente dos requisitos dos produtos " +"armazenados, como a realização de verificações de qualidade nos produtos " +"recebidos ou o uso de embalagens especiais nos produtos enviados." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:27 msgid "One-step flow" -msgstr "" +msgstr "Fluxo de uma etapa" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 msgid "" "The receiving and shipping rules for a one-step configuration are as " "follows:" msgstr "" +"As regras de recebimento e envio da configuração em uma etapa são as " +"seguintes:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 msgid "" @@ -10095,12 +10486,18 @@ msgid "" "between receipt and stock occur, such as a transfer to a quality control " "location." msgstr "" +"**Recebimento**: Receber produtos diretamente no estoque. Não ocorrem etapas" +" intermediárias entre o recebimento e o estoque, como uma transferência para" +" um local de controle de qualidade." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:33 msgid "" "**Shipping**: Ship products directly from stock. No intermediate steps " "between stock and shipping occur, such as a transfer to a packing location." msgstr "" +"**Envio**: Enviar produtos diretamente do estoque. Não há etapas " +"intermediárias entre o estoque e o envio, como transferência para um local " +"de embalagem." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:35 msgid "" @@ -10108,36 +10505,46 @@ msgid "" ":abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First " "Out)` removal strategies." msgstr "" +"Só pode ser usado se não estiver usando as estratégias de remoção " +":abbr:`PEPS (primeiro a entrar, primeiro a sair)`, :abbr:`UEPS (último a " +"entrar, primeiro a sair)` ou :abbr:`PVPS (primeiro a vencer, primeiro a " +"sair)`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:37 msgid "Receipts and/or deliveries are handled quickly." -msgstr "" +msgstr "Os recebimentos e/ou as entregas são processados rapidamente." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:38 msgid "" "Recommended for small warehouses with low stock levels, and for non-" "perishable items." msgstr "" +"Recomendado para pequenos armazéns com baixos níveis de estoque e para itens" +" não perecíveis." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 msgid "Items are received or shipped directly into/from stock." -msgstr "" +msgstr "Os itens são recebidos ou enviados diretamente no ou do estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:42 msgid "" ":ref:`Process receipts and deliveries in one step " "<inventory/receipts_delivery_one_step>`" msgstr "" +":ref:`Processar recebimentos e entregas em uma etapa " +"<inventory/receipts_delivery_one_step>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 msgid "Two-step flow" -msgstr "" +msgstr "Fluxo de duas etapas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 msgid "" "The receiving and shipping rules for a two-step configuration are as " "follows:" msgstr "" +"As regras de recebimento e envio da configuração em duas etapas são as " +"seguintes:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 msgid "" @@ -10146,6 +10553,10 @@ msgid "" "such as various shelves, freezers, and locked areas, before being stocked in" " the warehouse." msgstr "" +"**Entrada + estoque**: Trazer produtos para um local de entrada *antes* de " +"movê-los para o estoque. Os produtos podem ser organizados por diferentes " +"locais de armazenamento interno, como várias prateleiras, freezers e áreas " +"restritas, antes de serem estocados no armazém." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:52 msgid "" @@ -10153,6 +10564,9 @@ msgid "" "Packages can be organized by different carriers or shipping docks before " "being shipped." msgstr "" +"**Separação + envio**: Levar os produtos para um local de saída antes do " +"envio. Os pacotes podem ser organizados por diferentes transportadoras ou " +"plataformas de expedição antes de serem enviados." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 msgid "" @@ -10160,12 +10574,18 @@ msgid "" "with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`" " or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" +"Requisito mínimo para usar números de série ou lote para rastrear produtos " +"com uma estratégia de remoção :abbr:`PEPS (primeiro a entrar, primeiro a " +"sair)`, :abbr:`UEPS (último a entrar, primeiro a sair)` ou :abbr:`PVPS " +"(primeiro a vencer, primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 msgid "" "Recommended for larger warehouses with high stock levels, or when stocking " "large items (such as mattresses, large furniture, heavy machinery, etc.)." msgstr "" +"Recomendado para armazéns maiores com altos níveis de estoque ou ao estocar " +"itens grandes (como colchões, móveis grandes, maquinário pesado etc.)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 @@ -10173,22 +10593,28 @@ msgid "" "Products received will not be available for manufacturing, shipping, etc., " "until they are transferred into stock." msgstr "" +"Os produtos recebidos não estarão disponíveis para fabricação, envio, etc., " +"até que sejam transferidos para o estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 msgid "" ":ref:`Process receipts and deliveries in two steps " "<inventory/receipts_delivery_two_steps>`" msgstr "" +":ref:`Processar recebimentos e entregas em duas etapas " +"<inventory/receipts_delivery_two_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 msgid "Three-step flow" -msgstr "" +msgstr "Fluxo de três etapas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:68 msgid "" "The receiving and shipping rules for a three-step configuration are as " "follows:" msgstr "" +"As regras de recebimento e envio da configuração em três etapas são as " +"seguintes:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:70 msgid "" @@ -10196,6 +10622,9 @@ msgid "" "transfer them to a quality control area, and move the ones that pass " "inspection into stock." msgstr "" +"**Entrada + qualidade + estoque**: Receber produtos no local de entrada, " +"transferi-los para uma área de controle de qualidade e mover os que passam " +"pela inspeção para o estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:72 msgid "" @@ -10203,6 +10632,9 @@ msgid "" "pack them in a dedicated packing area, and bring them to an output location " "for shipping." msgstr "" +"**Separação + embalagem + envio**: Separar os produtos de acordo com sua " +"estratégia de remoção, embalá-los em uma área de embalagem dedicada e levá-" +"los a um local de saída para envio." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 msgid "" @@ -10210,34 +10642,44 @@ msgid "" ":abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or " ":abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" +"Pode ser usado ao rastrear produtos por números de série ou lote ao usar uma" +" estratégia de remoção :abbr:`PEPS (primeiro a entrar, primeiro a sair)`, " +":abbr:`UEPS (último a entrar, primeiro a sair)` ou :abbr:`PVPS (primeiro a " +"vencer, primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:77 msgid "Recommended for very large warehouses with very high stock levels." msgstr "" +"Recomendado para armazéns muito grandes com níveis de estoque muito altos." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 msgid "" "Required for any warehouse needing to perform quality control inspections " "before receiving items into stock." msgstr "" +"Necessário em qualquer armazém que precise realizar inspeções de controle de" +" qualidade antes de receber itens no estoque." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 msgid "" ":ref:`Process receipts in three steps <inventory/receipts_three_steps>`" msgstr "" +":ref:`Processar recebimentos em três etapas " +"<inventory/receipts_three_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:85 msgid "" ":ref:`Process deliveries in three steps <inventory/delivery_three_steps>`" msgstr "" +":ref:`Processar entregas em três etapas <inventory/receipts_three_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 msgid "Setup and configuration" -msgstr "" +msgstr "Preparação e configuração" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 msgid "Delivery methods" -msgstr "" +msgstr "Métodos de entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:5 msgid "" @@ -10245,6 +10687,9 @@ msgid "" "calculating the cost of shipping on sales orders and e-commerce shopping " "carts." msgstr "" +"Quando ativada no Odoo, a configuração *Métodos de entrega* adiciona a opção" +" de calcular o custo de frete em pedidos de vendas e carrinhos de compras do" +" e-Commerce." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:8 msgid "" @@ -10252,17 +10697,24 @@ msgid "" "<inventory/shipping/third_party>`, shipping prices are calculated based on " "the carrier's pricing and packaging information." msgstr "" +"Quando integrado a uma :ref:`transportadora terceirizada " +"<inventory/shipping/third_party>`, os preços de remessa são calculados com " +"base nas informações de preço e embalagem da transportadora." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:12 msgid "" ":ref:`Third-party shipping carrier setup <inventory/shipping/third_party>`" msgstr "" +":ref:`Configuração de transportadora terceirizada " +"<inventory/shipping/third_party>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:13 msgid "" "`Odoo Tutorials: Delivery Prices " "<https://www.odoo.com/slides/slide/delivery-prices-613?fullscreen=1>`_" msgstr "" +"`Tutoriais do Odoo: Preços de entrega " +"<https://www.odoo.com/slides/slide/delivery-prices-613?fullscreen=1>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:19 msgid "" @@ -10270,6 +10722,9 @@ msgid "" "module must be installed. To do so, navigate to the :menuselection:`Apps` " "application from the main Odoo dashboard." msgstr "" +"Para calcular o frete em pedidos de vendas e e-Commerce, o módulo *Custos de" +" entrega* deve ser instalado. Para fazer isso, navegue até o aplicativo " +":menuselection:`Aplicativos` no painel principal do Odoo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:22 msgid "" @@ -10277,20 +10732,25 @@ msgid "" "the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` " "module, click :guilabel:`Activate` to install it." msgstr "" +"Em seguida, remova o filtro :guilabel:`Aplicativos` e digite `Custos de " +"entrega` na barra :guilabel:`Pesquisar…`. Depois de localizar o módulo " +":guilabel:`Custos de entrega`, clique em :guilabel:`Ativar` para instalá-lo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 msgid "Install the *Delivery Costs* module." -msgstr "" +msgstr "Instale o módulo *Custos de entrega*." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 msgid "Add shipping method" -msgstr "" +msgstr "Adicionar método de envio" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 msgid "" "To configure delivery methods, go to :menuselection:`Inventory app --> " "Configuration --> Shipping Methods`." msgstr "" +"Para configurar os métodos de entrega, vá para :menuselection:`app " +"Inventário --> Configuração --> Métodos de envio`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:36 msgid "" @@ -10298,22 +10758,30 @@ msgid "" ":guilabel:`Configuration` drop-down menu, verify whether the feature is " "enabled by following these steps:" msgstr "" +"Se a opção :guilabel:`Métodos de envio` não estiver disponível no menu " +"suspenso :guilabel:`Configuração`, verifique se o recurso está ativado " +"seguindo estas etapas:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:39 msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" +"Vá para o :menuselection:`app Inventário --> Configuração --> Definições`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:40 msgid "" "Scroll to the :guilabel:`Shipping` section and enable the " ":guilabel:`Delivery Methods` feature by checking the corresponding checkbox." msgstr "" +"Role até a seção :guilabel:`Envio` e ative o recurso :guilabel:`Métodos de " +"entrega` marcando a caixa de seleção correspondente." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 msgid "" "Enable the *Delivery Methods* feature by checking the box in Configuration >" " Settings." msgstr "" +"Ative o recurso *Métodos de entrega* marcando a caixa em Configuração > " +"Definições." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:47 msgid "" @@ -10321,12 +10789,17 @@ msgid "" ":guilabel:`New`. Doing so opens a form to provide details about the shipping" " provider, including:" msgstr "" +"Na página :guilabel:`Métodos de envio`, adicione um método clicando em " +":guilabel:`Novo`. Isso abre um formulário para fornecer detalhes sobre o " +"provedor de envio, incluindo:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:50 msgid "" ":guilabel:`Shipping Method` (*Required field*): the name of the delivery " "method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." msgstr "" +":guilabel:`Método de envio` (*Campo obrigatório*): o nome do método de " +"entrega (ex.: `frete de taxa fixa`, `entrega no mesmo dia`, etc.)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:52 msgid "" @@ -10336,6 +10809,11 @@ msgid "" "carrier is properly installed and select the provider from the drop-down " "menu." msgstr "" +":guilabel:`Fornecedor` (*Campo obrigatório*): escolha o serviço de entrega, " +"como Fedex, se estiver usando uma :ref:`transportadora terceirizada " +"<inventory/shipping/third_party>`. Verifique se a integração com a " +"transportadora está instalada corretamente e selecione o provedor no menu " +"suspenso." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:56 msgid "" @@ -10345,6 +10823,10 @@ msgid "" "<inventory/shipping/pickup>` options, refer to their respective sections " "below." msgstr "" +"Para obter mais detalhes sobre a configuração de métodos de envio " +"personalizados, como as opções :ref:`preço fixo <inventory/shipping/fixed>`," +" :ref:`baseado em regras <inventory/shipping/rules>` ou :ref:`retirada na " +"loja <inventory/shipping/pickup>`, consulte as respectivas seções abaixo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 msgid "" @@ -10352,6 +10834,9 @@ msgid "" "Select the applicable website from the drop-down menu, or leave it blank to " "apply the method to all web pages." msgstr "" +":guilabel:`Site`: configura métodos de envio para uma página de e-Commerce. " +"Selecione o site aplicável no menu suspenso ou deixe em branco para aplicar " +"o método a todas as páginas da web." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 msgid "" @@ -10359,6 +10844,9 @@ msgid "" "company, select it from the drop-down menu. Leave the field blank to apply " "the method to all companies." msgstr "" +":guilabel:`Companhia`: se o método de envio for aplicável a uma empresa " +"específica, selecione-a no menu suspenso. Deixe o campo em branco para " +"aplicar o método a todas as empresas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:63 msgid "" @@ -10366,18 +10854,25 @@ msgid "" ":ref:`sales order line <inventory/shipping/sales-order>` as the delivery " "charge." msgstr "" +":guilabel:`Produto de entrega` (*Campo obrigatório*): produto listado na " +":ref:`linha do pedido de venda <inventory/shipping/sales-order>` como a taxa" +" de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:65 msgid "" ":guilabel:`Free if order amount is above`: checking this box enables free " "shipping if the customer spends above the specified amount." msgstr "" +":guilabel:`Grátis se o valor do pedido estiver acima`: marcar essa caixa " +"ativa o frete grátis se o cliente gastar mais do que o valor especificado." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 msgid "" "For examples on how to configure specific shipping methods, refer to the " "sections below." msgstr "" +"Para obter exemplos sobre como configurar métodos de envio específicos, " +"consulte as seções abaixo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:73 msgid "Fixed price" @@ -10392,6 +10887,12 @@ msgid "" "option makes the :guilabel:`Fixed Price` field become available, which is " "where the fixed rate shipping amount is defined." msgstr "" +"Para configurar um preço de envio que seja o mesmo para todos os pedidos, vá" +" para :menuselection:`app Inventário --> Configuração --> Métodos de envio`." +" Em seguida, clique em :guilabel:`Novo` e, no formulário de método de envio," +" defina o :guilabel:`provedor` para a opção :guilabel:`Preço fixo`. A " +"seleção dessa opção faz com que o campo :guilabel:`Preço fixo` fique " +"disponível, que é onde o valor da taxa fixa de envio é definido." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:81 msgid "" @@ -10399,40 +10900,46 @@ msgid "" "amount, check the box :guilabel:`Free if order amount is above` and fill in " "the amount." msgstr "" +"Para ativar o frete grátis se o valor do pedido exceder um valor " +"especificado, marque a caixa :guilabel:`Grátis se o valor do pedido estiver " +"acima` e preencha o valor." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:85 msgid "" "To set up `$20` flat-rate shipping that becomes free if the customer spends " "over `$100`, fill in the following fields:" msgstr "" +"Para configurar o frete de taxa fixa de `US$ 20` que se torna gratuito se o " +"cliente gastar mais de `US$ 100`, preencha os seguintes campos:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" -msgstr "" +msgstr ":guilabel:`Método de entrega`: `Frete de taxa fixa`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:89 msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" -msgstr "" +msgstr ":guilabel:`Provedor`: :guilabel:`Preço fixo`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:90 msgid ":guilabel:`Fixed Price`: `$20.00`" -msgstr "" +msgstr ":guilabel:`Preço fixo`: `US$ 20.00`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 msgid ":guilabel:`Free if order amount is above`: `$100.00`" msgstr "" +":guilabel:`Grátis se o valor do pedido estiver acima de`: `US$ 100.00`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" -msgstr "" +msgstr ":guilabel:`Produto de entrega`: `[FRETE] Fixo`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 msgid "Example of filling out a shipping method." -msgstr "" +msgstr "Exemplo de preenchimento de um método de envio." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:101 msgid "Based on rules" -msgstr "" +msgstr "Baseado em regras" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:103 msgid "" @@ -10441,10 +10948,14 @@ msgid "" "Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional " "margin` to include additional shipping costs." msgstr "" +"Para calcular o preço do frete com base nas regras de preços, defina o campo" +" :guilabel:`Provedor` para a opção :guilabel:`Baseado em regras`. " +"Opcionalmente, ajuste :guilabel:`Margem na taxa` e :guilabel:`Margem " +"adicional` para incluir custos adicionais de frete." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:108 msgid "Create pricing rules" -msgstr "" +msgstr "Criar regras de preços" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:110 msgid "" @@ -10454,12 +10965,19 @@ msgid "" "quantity is compared to a defined amount to calculate the " ":guilabel:`Delivery Cost`." msgstr "" +"Navegue até a aba :guilabel:`Preço` e clique em :guilabel:`Adicionar uma " +"linha`. Isso abre a janela :guilabel:`Criar regras de preço`, onde a " +":guilabel:`condição` relacionada ao peso, volume, preço ou quantidade do " +"produto é comparada a um valor definido para calcular o :guilabel:`Custo de " +"entrega`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:115 msgid "" "Once finished, click either :guilabel:`Save & New` to add another rule, or " ":guilabel:`Save & Close`." msgstr "" +"Quando terminar, clique em :guilabel:`Salvar e Novo` para adicionar outra " +"regra ou em :guilabel:`Salvar e Fechar`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 msgid "" @@ -10467,11 +10985,16 @@ msgid "" "set the :guilabel:`Condition` to `Quantity <= 5.00`, and the " ":guilabel:`Delivery Cost` to `$20`." msgstr "" +"Para cobrar dos clientes US$ 20 de frete para pedidos com cinco ou menos " +"produtos, defina a :guilabel:`Condição` como `Quantidade <= 5.00` e o " +":guilabel:`Custo de entrega` como `US$ 20`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 msgid "" "Display window to add a pricing rule. Set a condition and delivery cost." msgstr "" +"Janela de exibição para adicionar uma regra de preços. Defina uma condição e" +" um custo de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:125 msgid "" @@ -10481,10 +11004,15 @@ msgid "" "and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations " "apply." msgstr "" +"Para restringir o envio para destinos específicos no site de e-Commerce, no " +"formulário de método de envio, navegue até a aba :guilabel:`Disponibilidade " +"do destino` e defina os :guilabel:`países`, :guilabel:`estados` e " +":guilabel:`códigos postais`. Deixe esses campos vazios se todos os locais se" +" aplicarem." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:130 msgid "Calculate delivery cost" -msgstr "" +msgstr "Calcular o custo de entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:132 msgid "" @@ -10492,35 +11020,44 @@ msgid "" "satisfies the :guilabel:`Condition`, plus any extra charges from the " ":guilabel:`Margin on rate` and :guilabel:`Additional margin`." msgstr "" +"O custo de envio é o :guilabel:`Custo de entrega` especificado na regra que " +"satisfaz a :guilabel:`condição`, mais os encargos extras da " +":guilabel:`Margem na taxa` e :guilabel:`Margem adicional`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:136 msgid "" "Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" "\n" msgstr "" +"Total = Custo de entrega da regra + (Margem sobre a taxa \\vezes Custo de entrega da regra) + Margem adicional\n" +"\n" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:140 msgid "With the two following rules set up:" -msgstr "" +msgstr "Com as duas regras a seguir configuradas:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:142 msgid "If the order contains five or fewer products, shipping is $20" -msgstr "" +msgstr "Se o pedido contiver cinco ou menos produtos, o frete será de US$ 20" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 msgid "If the order contains more than five products, shipping is $50." -msgstr "" +msgstr "Se o pedido contiver mais de cinco produtos, o frete será de US$ 50." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 msgid "" ":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is " "`$9.00`." msgstr "" +":guilabel:`Margem sobre a taxa` é `10%` e :guilabel:`Margem adicional` é " +"`$9,00`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 msgid "" "Show example of \"Based on rules\" shipping method with margins configured." msgstr "" +"Exibir exemplo de método de envio \"Baseado em regras\" com margens " +"configuradas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:151 msgid "" @@ -10528,6 +11065,9 @@ msgid "" "9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * " "50) + 9)." msgstr "" +"Quando a primeira regra é aplicada, o custo de entrega é de US$ 31 (20 + " +"(0,1 * 20) + 9). Quando a segunda regra é aplicada, o custo de entrega é de " +"US$ 64 (50 + (0,1 * 50) + 9)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:157 msgid "Pickup in store" @@ -10539,6 +11079,9 @@ msgid "" ":guilabel:`Provider` field and specify the pickup location in " ":guilabel:`Warehouse`." msgstr "" +"Para configurar a retirada na loja, selecione :guilabel:`Retirada na loja` " +"no campo :guilabel:`Prestador` e especifique o local de retirada em " +":guilabel:`Armazém`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 msgid "" @@ -10549,10 +11092,16 @@ msgid "" ":guilabel:`Invoicing Policy` field to decide whether the added shipping " "charge on the sales order is the precise cost from the shipping carrier." msgstr "" +"Para faturar o cliente pelo custo de envio para o local de retirada, escolha" +" a opção :guilabel:`Obter taxa e criar remessa` no campo :guilabel:`Nível de" +" integração`. Em seguida, escolha as opções :guilabel:`Custo estimado` ou " +":guilabel:`Custo real` no campo :guilabel:`Política de faturamento` para " +"decidir se a taxa de envio adicionada no pedido de venda é o custo exato da " +"transportadora." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:169 msgid ":ref:`Invoice cost of shipping <inventory/shipping/invoice>`" -msgstr "" +msgstr ":ref:`Custo de envio na fatura <inventory/shipping/invoice>`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:174 msgid "Add shipping" @@ -10565,6 +11114,10 @@ msgid "" "desired sales order by going to :menuselection:`Sales app --> Orders --> " "Orders`." msgstr "" +"Os métodos de envio podem ser adicionados aos pedidos de vendas na forma de " +"produtos de entrega, que aparecem como itens de linha individuais. Primeiro," +" navegue até o pedido de vendas desejado acessando :menuselection:`app " +"Vendas --> Pedidos --> Pedidos`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:180 msgid "" @@ -10572,6 +11125,9 @@ msgid "" "the :guilabel:`Add a shipping method` pop-up window. Then, choose a " ":guilabel:`Shipping Method` from the list." msgstr "" +"No pedido de venda, clique no botão :guilabel:`Adicionar envio`, que abre a " +"janela pop-up :guilabel:`Adicionar um método de envio`. Em seguida, escolha " +"um :guilabel:`Método de envio` na lista." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 msgid "" @@ -10580,32 +11136,42 @@ msgid "" "Edit the field to specify the exact weight, and then click :guilabel:`Add` " "to add the shipping method." msgstr "" +"O :guilabel:`Peso total do pedido` é pré-preenchido com base nos pesos dos " +"produtos (que são definidos na guia :guilabel:`Inventário` para cada " +"formulário de produto). Edite o campo para especificar o peso exato e, em " +"seguida, clique em :guilabel:`Adicionar` para adicionar o método de envio." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:188 msgid "" "The amount defined in :guilabel:`Total Order Weight` overwrites the total " "product weights defined on the product form." msgstr "" +"O valor definido em :guilabel:`Peso total da ordem` substitui os pesos " +"totais do produto definidos no formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 msgid "" "The shipping cost is added to the *sales order line* as the " ":guilabel:`Delivery Product` detailed on the shipping method form." msgstr "" +"O custo de envio é adicionado à linha do *pedido de venda* como o " +":guilabel:`Produto de entrega` detalhado no formulário do método de envio." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:195 msgid "" "`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is " "added to sales order `S00088`." msgstr "" +"`Entrega de móveis`, um produto de entrega com uma taxa fixa de `US$ 200`, é" +" adicionado ao pedido de vendas `S00088`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 msgid "Show delivery order on the sales order line." -msgstr "" +msgstr "Mostrar a ordem de entrega na linha do pedido de vendas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:203 msgid "Delivery order" -msgstr "" +msgstr "Ordem de entrega" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:205 msgid "" @@ -10614,10 +11180,14 @@ msgid "" "on the delivery itself, go to the :guilabel:`Additional Info` tab and modify" " the :guilabel:`Carrier` field." msgstr "" +"O método de envio adicionado ao pedido de vendas está vinculado aos detalhes" +" da transportadora no pedido de entrega. Para adicionar ou alterar o método " +"de entrega na própria entrega, vá para a aba :guilabel:`Informações " +"adicionais` e modifique o campo :guilabel:`Transportadora`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 msgid "Shipping carrier information on the delivery form." -msgstr "" +msgstr "Informações da transportadora no formulário de entrega." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 msgid "How to get DHL credentials for integration with Odoo?" @@ -10671,7 +11241,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 msgid "Set up Sendcloud shipping services in Odoo" -msgstr "" +msgstr "Configurar os serviços de envio da Sendcloud no Odoo" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 msgid "" @@ -10679,20 +11249,27 @@ msgid "" "of European shipping carriers with Odoo. Once integrated, users can select " "shipping carriers on inventory operations in their Odoo database." msgstr "" +"O Sendcloud é um agregador de serviços de remessa que facilita a integração " +"de transportadoras européias com o Odoo. Uma vez integrados, os usuários " +"podem selecionar as transportadoras nas operações de inventário em sua base " +"de dados Odoo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:10 msgid "" "`Sendcloud integration documentation <https://support.sendcloud.com/hc/en-" "us/articles /360059470491-Odoo-integration>`_" msgstr "" +"`Documentação de integração do Sendcloud " +"<https://support.sendcloud.com/hc/en-us/articles /360059470491-Odoo-" +"integration>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:14 msgid "Setup in Sendcloud" -msgstr "" +msgstr "Configuração no Sendcloud" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:17 msgid "Create an account and activate carriers" -msgstr "" +msgstr "Crie uma conta e ative as operadoras" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:19 msgid "" @@ -10700,6 +11277,10 @@ msgid "" " configure the account and generate the connector credentials. Log in with " "the Sendcloud account, or create a new one if needed." msgstr "" +"Para começar, acesse a `Plataforma da Sendcloud " +"<https://www.sendcloud.com>`_ para configurar a conta e gerar as credenciais" +" do conector. Faça login com a conta Sendcloud ou crie uma nova conta, se " +"necessário." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:24 msgid "" @@ -10709,6 +11290,10 @@ msgid "" "(or deactivate) the shipping carriers that will be used in the Odoo " "database." msgstr "" +"Para a criação de uma nova conta, a Sendcloud solicitará um número de " +":abbr:`CNPJ` ou :abbr:`VAT/EORI` (identificação fiscal). Depois de concluir " +"a configuração da conta, ative (ou desative) as transportadoras que serão " +"usadas na base de dados do Odoo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:30 msgid "" @@ -10717,10 +11302,14 @@ msgid "" "rules or individual custom carrier contacts, a paid plan of Sendcloud is " "required." msgstr "" +"A integração do Sendcloud no Odoo funciona nos planos gratuitos do Sendcloud" +" *apenas* se uma conta bancária estiver vinculada, pois o Sendcloud não " +"envia gratuitamente. Para usar regras de envio ou contatos personalizados de" +" transportadoras individuais, é necessário um plano pago do Sendcloud." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 msgid "Warehouse configuration" -msgstr "" +msgstr "Configuração do armazém" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 msgid "" @@ -10728,10 +11317,13 @@ msgid "" " --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse" " address`." msgstr "" +"Uma vez conectado à conta Sendcloud, navegue até :menuselection:`Definições " +"--> Envio --> Endereços` e preencha o campo para :guilabel:`endereço do " +"armazém`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 msgid "Adding addresses in the Sendcloud settings." -msgstr "" +msgstr "Adicionar endereços nas configurações do Sendcloud." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:44 msgid "" @@ -10740,52 +11332,59 @@ msgid "" "called :guilabel:`Address Name (optional)`. The Odoo warehouse name should " "be entered here, and the characters should be exactly the same." msgstr "" +"Para permitir que a Sendcloud processe também as devoluções, é necessário um" +" :guilabel:`Endereço de devolução`. Na seção :guilabel:`Diversos`, há um " +"campo chamado :guilabel:`Nome do endereço (opcional)`. O nome do armazém do " +"Odoo deve ser inserido aqui, e os caracteres devem ser exatamente os mesmos." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid "**SendClould configuration**" -msgstr "" +msgstr "**Configuração do SendClould**" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Miscellaneous`" -msgstr "" +msgstr ":guilabel:`Diversos`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Address Name (optional)`: `Warehouse #1`" -msgstr "" +msgstr ":guilabel:`Nome do endereço (opcional)`: `Warehouse #1`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Brand`: `Default`" -msgstr "" +msgstr ":guilabel:`Marca`: `Padrão`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid "**Odoo warehouse configuration**" -msgstr "" +msgstr "**Configuração do armazém do Odoo**" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Warehouse`: `Warehouse #1`" -msgstr "" +msgstr ":guilabel:`Armazém`: `Warehouse #1`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Short Name`: `WH`" -msgstr "" +msgstr ":guilabel:`Abreviação`: `WH`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Company`: `My company (San Francisco)`" -msgstr "" +msgstr ":guilabel:`Empresa`: `Minha empresa (San Francisco)`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Address`: `My Company (San Francisco)`" -msgstr "" +msgstr ":guilabel:`Endereço`: `Minha empresa (San Francisco)`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:61 msgid "" "Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo" " configuration and the Sendcloud configuration, are the exact same." msgstr "" +"Observe como as entradas para o campo :guilabel:`Warehouse`, tanto para a " +"configuração do Odoo quanto para a configuração da Sendcloud, são exatamente" +" as mesmas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:65 msgid "Generate Sendcloud credentials" -msgstr "" +msgstr "Gerar credenciais do Sendcloud" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 msgid "" @@ -10793,6 +11392,9 @@ msgid "" "Integrations` in the menu on the right. Next, search for :guilabel:`Odoo " "Native`. Then, click on :guilabel:`Connect`." msgstr "" +"Na conta Sendcloud, navegue até :menuselection:`Definições --> Integrações` " +"no menu à direita. Em seguida, procure por :guilabel:`Odoo Native`. Em " +"seguida, clique em :guilabel:`Conectar`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:70 msgid "" @@ -10803,6 +11405,12 @@ msgid "" "CompanyName`, with the user's company name replacing `CompanyName` (e.g. " "`Odoo StealthyWood`)." msgstr "" +"Depois de clicar em :guilabel:`Conectar`, a página redireciona para a página" +" de configurações :guilabel:`API do Sendcloud`, onde as :guilabel:`Chaves " +"secretas e públicas` são produzidas. A próxima etapa é nomear a " +":guilabel:`Integração`. A convenção de nomenclatura é a seguinte: `Odoo " +"NomeDaEmpresa`, com o nome da empresa do usuário substituindo " +"`NomedaEmpresa` (por exemplo, `Odoo StealthyWood`)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:75 msgid "" @@ -10810,10 +11418,14 @@ msgid "" "shipping services for this integration. After saving, the :guilabel:`Public " "and Secret Keys` are generated." msgstr "" +"Em seguida, marque a caixa ao lado de :guilabel:`pontos de serviço` e " +"selecione os serviços de remessa para essa integração. Depois de salvar, as " +":guilabel:`chaves públicas e secretas` são geradas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 msgid "Configuring the Sendcloud integration and receiving the credentials." msgstr "" +"Configuração da integração do Sendcloud e recebimento das credenciais." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 msgid "Setup in Odoo" @@ -10821,7 +11433,7 @@ msgstr "Configuração no Odoo" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:86 msgid "Install the Sendcloud shipping module" -msgstr "" +msgstr "Instale o módulo de envio da Sendcloud" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:88 msgid "" @@ -10829,14 +11441,18 @@ msgid "" " the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, " "search for the :guilabel:`Sendcloud Shipping` integration, and install it." msgstr "" +"Depois que a conta Sendcloud estiver definida e configurada, é hora de " +"configurar a base de dados do Odoo. Para começar, acesse o módulo " +":guilabel:`Aplicativos` do Odoo, procure a integração :guilabel:`Envio por " +"Sendcloud` e instale-a." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 msgid "Sendcloud Shipping module in the Odoo Apps module." -msgstr "" +msgstr "Módulo de envio Sendcloud no módulo Odoo Aplicativos." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 msgid "Sendcloud shipping connector configuration" -msgstr "" +msgstr "Configuração do conector de envio Sendcloud" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 msgid "" @@ -10845,6 +11461,10 @@ msgid "" ":guilabel:`Sendcloud Connector` setting is found under the " ":guilabel:`Shipping Connectors` section." msgstr "" +"Depois de instalado, ative o módulo :guilabel:`Envio por Sendcloud` em " +":menuselection:`Inventário --> Configuração --> Definições`. A configuração " +"do :guilabel:`Conector Sendcloud` é encontrada na seção " +":guilabel:`Conectores de envio`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:103 msgid "" @@ -10852,6 +11472,9 @@ msgid "" ":guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once" " on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." msgstr "" +"Depois de ativar o :guilabel:`Conector do Sendcloud`, clique no link " +":guilabel:`Métodos de envio do Sendcloud` abaixo do conector listado. Uma " +"vez na página :guilabel:`Métodos de envio`, clique em :guilabel:`Criar`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:108 msgid "" @@ -10859,50 +11482,65 @@ msgid "" ":menuselection:`Inventory --> Configuration --> Delivery --> Shipping " "Methods`." msgstr "" +"Também é possível acessar os :guilabel:`Métodos de envio` em " +":menuselection:`Inventário --> Configuração --> Entrega --> Métodos de " +"envio`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:111 msgid "" "Fill out the following fields in the :guilabel:`New Shipping Method` form:" msgstr "" +"Preencha os seguintes campos no formulário :guilabel:`Novo método de envio`:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:113 msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." -msgstr "" +msgstr ":guilabel:`Método de envio`: tipo `Sendcloud DPD`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:114 msgid "" ":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." msgstr "" +":guilabel:`Provedor`: selecione :guilabel:`Sendcloud` no menu suspenso." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:115 msgid "" ":guilabel:`Delivery Product`: set the product that was configured for this " "shipping method or create a new product." msgstr "" +":guilabel:`Produto de entrega`: define o produto que foi configurado para " +"esse método de envio ou cria um novo produto." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:117 msgid "" "In the :guilabel:`SendCloud Configuration` tab, enter the " ":guilabel:`Sendcloud Public Key`." msgstr "" +"Na aba :guilabel:`Configuração do SendCloud`, digite a :guilabel:`Chave " +"pública do Sendcloud`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:118 msgid "" "In the :guilabel:`SendCloud Configuration` tab, enter the " ":guilabel:`Sendcloud Secret Key`." msgstr "" +"Na aba :guilabel:`Configuração do SendCloud`, digite a :guilabel:`Chave " +"secreta do Sendcloud`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:119 msgid "" "Manually :guilabel:`Save` the form by clicking the cloud icon next to the " ":guilabel:`Shipping Methods / New` breadcrumbs." msgstr "" +"Manualmente :guilabel:`salve` o formulário clicando no ícone de nuvem ao " +"lado da trilha de navegação :guilabel:`Métodos de envio/Novo`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:122 msgid "" "After configuring and saving the form, follow these steps to load the " "shipping products:" msgstr "" +"Depois de configurar e salvar o formulário, siga estas etapas para carregar " +"os produtos de remessa:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 msgid "" @@ -10910,40 +11548,45 @@ msgid "" "Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping " "products` link." msgstr "" +"Na aba :guilabel:`COnfiguração do SendCloud` do formulário :guilabel:`Novo " +"método de envio`, clique no link :guilabel:`Carregar seus produtos de " +"remessa do SendCloud`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 msgid "" "Select the shipping products the company would like to use for deliveries " "and returns." msgstr "" +"Selecione os produtos de remessa que a empresa gostaria de usar para " +"entregas e devoluções." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 msgid "Click :guilabel:`Select`." -msgstr "" +msgstr "Clique em :guilabel:`Selecionar`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 msgid "Sample Sendcloud shipping products configured in Odoo:" -msgstr "" +msgstr "Exemplo de produtos de remessa da Sendcloud configurados no Odoo:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`DELIVERY`" -msgstr "" +msgstr ":guilabel:`ENTREGA`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Shipping Product`: `DPD Home 0-31.5kg`" -msgstr "" +msgstr ":guilabel:`Produto a ser enviado`: `DPD Home 0-31,5kg`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Carrier`: `DPD`" -msgstr "" +msgstr ":guilabel:`Transportadora`: `DPD`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Minimum Weight`: `0.00`" -msgstr "" +msgstr ":guilabel:`Peso mínimo`: `0,00`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Maximum Weight`: `31.50`" -msgstr "" +msgstr ":guilabel:`Peso máximo`: `31,50`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:138 msgid "" @@ -10954,34 +11597,40 @@ msgid "" "`Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` " "`Sweden` `Switzerland`" msgstr "" +":guilabel:`Países`: `Áustria` `Bélgica` `Bósnia` `Herzegovina` `Bulgária` " +"`Croácia` `República Tcheca` `Dinamarca` `Estônia` `Finlândia` `França` " +"`Alemanha` `Grécia` `Hungria` `Islândia` `Irlanda` `Itália` Letônia` " +"`Liechtenstein` `Lituânia` `Luxemburgo` `Mônaco` `Países Baixos` `Noruega` " +"`Polônia` `Portugal` `Romênia` `Sérvia` `Eslováquia` `Eslovênia` `Espanha` " +"`Suécia`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`RETURN`" -msgstr "" +msgstr ":guilabel:`DEVOLUÇÃO`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Return Shipping Product`: `DPD Return 0-20kg`" -msgstr "" +msgstr ":guilabel:`Produto de remessa da devolução`: `DPD Devolução 0-20kg`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Return Carrier`: `DPD`" -msgstr "" +msgstr ":guilabel:`Transportadora da devolução`: `DPD`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Return Minimum Weight`: `0.00`" -msgstr "" +msgstr ":guilabel:`Peso mínimo da devolução`: `0,00`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Return Maximum Weight`: `20.00`" -msgstr "" +msgstr ":guilabel:`Peso máximo da devolução`: `20,00`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 msgid ":guilabel:`Return Countries`: `Belgium` `Netherlands`" -msgstr "" +msgstr ":guilabel:`Países de devolução`: `Bélgica` `Países Baixos`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 msgid "Example of shipping products configured in Odoo." -msgstr "" +msgstr "Exemplo de produtos de remessa configurados no Odoo." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:156 msgid "" @@ -10990,6 +11639,10 @@ msgid "" "Sendcloud account will be charged, unless the associated package is canceled" " within 24 hours of creation." msgstr "" +"A Sendcloud não fornece chaves de teste quando uma empresa testa o envio de " +"um pacote no Odoo. Isso significa que, se um pacote for criado, a conta " +"configurada do Sendcloud será cobrada, a menos que o pacote associado seja " +"cancelado dentro de 24 horas após a criação." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:160 msgid "" @@ -10999,10 +11652,16 @@ msgid "" "creation — this occurs automatically. The test and production environment " "settings can be toggled back and forth from the :guilabel:`Smart Buttons`." msgstr "" +"O Odoo tem uma camada integrada de proteção contra cobranças indesejadas ao " +"usar ambientes de teste. Em um ambiente de teste, se um for usado método de " +"envio para criar etiquetas, essas etiquetas serão imediatamente canceladas " +"após a criação - isso ocorre automaticamente. As configurações de ambiente " +"de teste e de produção podem ser alternadas no :guilabel:`botões " +"inteligentes`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:166 msgid "Generate a label with Sendcloud" -msgstr "" +msgstr "Gerar uma etiqueta com o Sendcloud" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:168 msgid "" @@ -11011,31 +11670,40 @@ msgid "" "documents are automatically generated in the chatter, which include the " "following:" msgstr "" +"Ao criar uma cotação no Odoo, adicione a remessa e um :guilabel:`Produto de " +"remessa do Sendcloud`. Em seguida, :guilabel:`valide` a entrega. Os " +"documentos da etiqueta de envio são gerados automaticamente no chatter, que " +"incluem o seguinte:" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:172 msgid ":guilabel:`Shipping label(s)` depending on the number of packages." -msgstr "" +msgstr ":guilabel:`Etiqueta(s) de remessa`, dependendo do número de pacotes." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 msgid "" ":guilabel:`Return label(s)` if the Sendcloud connector is configured for " "returns." msgstr "" +":guilabel:`Etiqueta(s) de devolução `, se o conector Sendcloud estiver " +"configurado para devoluçĩes." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:174 msgid "" ":guilabel:`Customs document(s)` should the destination country require them." msgstr "" +":guilabel:`Documento(s) alfandegário(s)`, caso o país de destino exija." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:176 msgid "Additionally, the tracking number is now available." -msgstr "" +msgstr "Além disso, o número de rastreamento fica disponível." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:179 msgid "" "When return labels are created, Sendcloud will automatically charge the " "configured Sendcloud account." msgstr "" +"Quando as etiquetas de devolução forem criadas, a Sendcloud cobrará " +"automaticamente a conta Sendcloud configurada." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 msgid "FAQ" @@ -11043,7 +11711,7 @@ msgstr "FAQ" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 msgid "Shipment is too heavy" -msgstr "" +msgstr "Remessas muito pesadas" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:188 msgid "" @@ -11052,6 +11720,10 @@ msgid "" "to be put in different :guilabel:`Packages` to :guilabel:`Validate` the " "transfer and generate labels." msgstr "" +"Se a remessa for muito pesada para o serviço Sendcloud configurado, o peso " +"será dividido para simular vários pacotes. Os produtos precisarão ser " +"colocados em diferentes :guilabel:`pacotes` para :guilabel:`validar` a " +"transferência e gerar etiquetas." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:192 msgid "" @@ -11060,10 +11732,14 @@ msgid "" "not apply to the shipping price calculation on the calculation on the sales " "order." msgstr "" +"Também é possível configurar :guilabel:`regras` na Sendcloud para usar " +"outros métodos de envio quando o peso for muito grande. No entanto, observe " +"que essas regras não se aplicarão ao cálculo do preço de envio no cálculo do" +" pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 msgid "When using a personal carrier contract" -msgstr "" +msgstr "Ao usar um contrato de transportadora pessoal" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:199 msgid "" @@ -11071,10 +11747,13 @@ msgid "" " accurately reflected when creating a quotation in Odoo, then the pricing " "information needs to be updated in Sendcloud." msgstr "" +"Ao usar um contrato de transportadora pessoal na Sendcloud, se o preço não " +"for refletido com precisão ao criar uma cotação no Odoo, as informações de " +"preço precisarão ser atualizadas no Sendcloud." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:203 msgid "Measuring volumetric weight" -msgstr "" +msgstr "Medição de peso volumétrico" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:205 msgid "" @@ -11083,12 +11762,18 @@ msgid "" "(:dfn:`Volumetric weight is the volume that a package occupies when in " "transit. In other words it is the physical size of a package`)." msgstr "" +"Muitas transportadoras têm várias medidas de peso. Há o peso real dos " +"produtos no pacote e há o *peso volumétrico* (:dfn:`Peso volumétrico é o " +"volume que um pacote ocupa quando está em trânsito. Em outras palavras, é o " +"tamanho físico de um pacote`)." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:210 msgid "" "Check to see if selected carrier(s) already have defined formulas to compute" " the volumetric weight." msgstr "" +"Verifique se as transportadoras selecionadas já têm fórmulas definidas para " +"calcular o peso volumétrico." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:214 msgid "" @@ -11096,10 +11781,13 @@ msgid "" "<https://support.sendcloud.com/ hc/en-us/articles/360059644051-How-to-" "calculate-automate-parcel-volumetric-weight>`_" msgstr "" +"`Sendcloud: Como calcular r automatizar o peso volumétrico do pacote " +"<https://support.sendcloud.com/ hc/en-us/articles/360059644051-How-to-" +"calculate-automate-parcel-volumetric-weight>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:219 msgid "Unable to calculate shipping rate" -msgstr "" +msgstr "Não foi possível calcular a taxa de frete" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 msgid "" @@ -11109,6 +11797,11 @@ msgid "" " The country of origin (warehouse address) should also be supported by the " "carrier." msgstr "" +"Primeiro, verifique se o produto que está sendo enviado tem um peso " +"compatível com o método de envio selecionado. Se isso estiver definido, " +"verifique se o país de destino (do endereço do cliente) é compatível com a " +"transportadora. O país de origem (endereço do armazém) também deve ser " +"aceito pela transportadora." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:3 msgid "How to integrate a third party shipper?" @@ -11265,6 +11958,9 @@ msgid "" "automatically be added to the invoice. For more information, please read the" " document :doc:`../advanced_operations_shipping/invoicing`." msgstr "" +"Caso contrário, o preço real (calculado quando a entrega for validada) será " +"automaticamente adicionado à fatura. Para obter mais informações, leia o " +"documento :doc:`../advanced_operations_shipping/invoicing`." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 msgid "Delivery" @@ -11299,11 +11995,11 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:160 msgid ":doc:`../advanced_operations_shipping/invoicing`" -msgstr "" +msgstr ":doc:`../advanced_operations_shipping/invoicing`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:161 msgid ":doc:`../advanced_operations_shipping/labels`" -msgstr "" +msgstr ":doc:`../advanced_operations_shipping/labels`" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:3 msgid "How to get UPS credentials for integration with Odoo?" @@ -11330,6 +12026,9 @@ msgid "" "An Access Key is a 16 character alphanumeric code that allows access to the " "UPS Developer Kit API Development and Production servers." msgstr "" +"Uma chave de acesso é um código alfanumérico de 16 caracteres que permite o " +"acesso aos servidores de desenvolvimento e produção da API do UPS Developer " +"Kit." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:17 msgid "Create a UPS Account" @@ -11392,6 +12091,8 @@ msgid "" "Log in to the `UPS.com website <http://www.ups.com/>`_) using your UPS.com " "User ID and Password." msgstr "" +"Faça login no site `UPS.com <http://www.ups.com/>`_) usando sua ID de " +"usuário e senha do UPS.com." #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:41 msgid "Click the **My UPS** tab." @@ -11440,6 +12141,8 @@ msgid "" "Go to the `UPS Developer Kit web page " "<https://www.ups.com/upsdeveloperkit?loc=en_US>`_" msgstr "" +"Acesse a página web do `UPS Developer Kit " +"<https://www.ups.com/upsdeveloperkit?loc=en_US>`_" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:61 msgid "Log into UPS.com with your user ID and password" @@ -11468,17 +12171,20 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 msgid "Warehouses and storage" -msgstr "" +msgstr "Armazéns e armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:3 msgid "Batch picking" -msgstr "" +msgstr "Separação em lote" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:7 msgid "" "*Batch picking* enables a single picker to handle multiple orders at once, " "reducing the time needed to navigate to the same location in a warehouse." msgstr "" +"A *separação em lote* permite que um único selecionador lide com vários " +"pedidos de uma só vez, reduzindo o tempo necessário para navegar até o mesmo" +" local em um depósito." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:10 msgid "" @@ -11486,11 +12192,17 @@ msgid "" "list. After the picking, the batch is taken to an output location, where the" " products are sorted into their respective delivery packages." msgstr "" +"Ao fazer a separação em lotes, os pedidos são agrupados e consolidados em " +"uma lista de separação. Após a separação, o lote é levado para um local de " +"saída, onde os produtos são classificados em seus respectivos pacotes de " +"entrega." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 msgid "" ":ref:`Use Barcode app for pickings <inventory/management/barcode_picking>`" msgstr "" +":ref:`Usar o aplicativo de código de barras para separações " +"<inventory/management/barcode_picking>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 msgid "" @@ -11499,6 +12211,11 @@ msgid "" "often. Storing high-demand items in easily accessible locations can increase" " the number of orders that are fulfilled efficiently." msgstr "" +"Como os pedidos *devem* ser organizados no local de saída após serem " +"separados, esse método de coleta é adequado para empresas com poucos " +"produtos que são solicitados com frequência. O armazenamento de itens de " +"alta demanda em locais de fácil acesso pode aumentar o número de pedidos que" +" são atendidos com eficiência." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:24 msgid "" @@ -11506,10 +12223,14 @@ msgid "" ":menuselection:`Inventory app --> Configuration --> Settings`. Under the " ":guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." msgstr "" +"Para ativar a opção de coleta em lote, comece acessando :menuselection:`app " +"Inventário --> Configuração --> Definições`. Na seção :guilabel:`Operações`," +" marque a caixa :guilabel:`Transferências em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." msgstr "" +"Ative as *transferências em lote* em Inventário > Configuração > Definições." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:32 msgid "" @@ -11518,6 +12239,11 @@ msgid "" "under the :guilabel:`Warehouse` heading must also be checked on this " "settings page. When finished, click :guilabel:`Save`." msgstr "" +"Como o picking em lote é um método para otimizar a operação de *separação* " +"no Odoo, as opções :guilabel:`Locais de armazenamento` e :guilabel:`Rotas de" +" várias etapas` sob o título :guilabel:`Armazém` também devem ser " +"verificadas nessa página de configurações. Quando terminar, clique em " +":guilabel:`Salvar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 @@ -11525,6 +12251,8 @@ msgid "" "Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration" " > Settings." msgstr "" +"Habilite *Locais de armazenamento* e *Rotas de várias etapas* em Inventário " +"> Configuração > Definições." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:40 msgid "" @@ -11532,6 +12260,9 @@ msgid "" " settings page, which is accessible from :menuselection:`Inventory app --> " "Configuration --> Warehouses`." msgstr "" +"Por fim, ative o recurso de separação do armazém, navegando até a página de " +"configurações do armazém, que pode ser acessada em :menuselection:`app " +"Inventário --> Configuração --> Armazéns`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:43 msgid "" @@ -11540,24 +12271,29 @@ msgid "" ":guilabel:`Send goods in output and then deliver (2 steps)` or " ":guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." msgstr "" +"A partir daí, selecione o depósito desejado na lista. Em seguida, entre as " +"opções disponíveis de :guilabel:`Remessas enviadas`, selecione " +":guilabel:`Enviar mercadorias na saída e depois entregar (2 etapas)` ou " +":guilabel:`Embalar mercadorias, enviar mercadorias na saída e depois " +"entregar (3 etapas)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:48 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:131 msgid ":ref:`Delivery in two steps <inventory/receipts_delivery_two_steps>`" -msgstr "" +msgstr ":ref:`Entrega em duas etapas <inventory/receipts_delivery_two_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:49 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:132 msgid ":ref:`Delivery in three steps <inventory/delivery_three_steps>`" -msgstr "" +msgstr ":ref:`Entrega em três etapas <inventory/delivery_three_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 msgid "Set up 2-step or 3-step outgoing shipments." -msgstr "" +msgstr "Configure remessas enviadas em 2 ou 3 etapas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:56 msgid "Create batch transfers" -msgstr "" +msgstr "Criar transferências em lote" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:58 msgid "" @@ -11565,22 +12301,32 @@ msgid "" "app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` " "button to begin creating a batch transfer." msgstr "" +"Crie manualmente transferências em lote diretamente da página " +":menuselection:`app Inventário --> Operações --> Transferências em lote`. " +"Clique no botão :guilabel:`Novo` para começar a criar uma transferência em " +"lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:61 msgid "On the batch transfer form, fill the following fields out accordingly:" msgstr "" +"No formulário de transferência de lote, preencha os seguintes campos " +"adequadamente:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:63 msgid "" ":guilabel:`Responsible`: employee assigned to the picking. Leave this field " "blank if *any* worker can fulfill this picking." msgstr "" +":guilabel:`Responsável`: funcionário designado para a separação. Deixe esse " +"campo em branco se *qualquer* funcionário puder realizar essa separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:65 msgid "" ":guilabel:`Operation Type`: from the drop-down menu, select the operation " "type under which the picking is categorized." msgstr "" +":guilabel:`Tipo de operação`: no menu suspenso, selecione o tipo de operação" +" sob o qual a separação está categorizado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:67 msgid "" @@ -11588,28 +12334,38 @@ msgid "" ":guilabel:`Responsible` person should complete the transfer to the output " "location." msgstr "" +":guilabel:`Data agendada`: especifica a data até a qual a pessoa " +":guilabel:`Responsável` deve concluir a transferência para o local de saída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:70 msgid "" "Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to " "open the :guilabel:`Add: Transfers` window." msgstr "" +"Em seguida, na lista :guilabel:`Transferências`, clique em " +":guilabel:`Adicionar uma linha` para abrir a janela :guilabel:`Adicionar: " +"Transferências`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:73 msgid "" "If the :guilabel:`Operation Type` field was filled, the list will filter " "transfer records matching the selected :guilabel:`Operation Type`." msgstr "" +"Se o campo :guilabel:`Tipo de operação` tiver sido preenchido, a lista " +"filtrará os registros de transferência que correspondem ao :guilabel:`Tipo " +"de operação` selecionado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:76 msgid "Click the :guilabel:`New` button to create a new transfer." -msgstr "" +msgstr "Clique no botão :guilabel:`Novo` para criar uma nova transferência." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:78 msgid "" "Once the transfer records are selected, click :guilabel:`Confirm` to confirm" " the batch picking." msgstr "" +"Depois que os registros de transferência forem selecionados, clique em " +":guilabel:`Confirmar` para confirmar a separação em lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:81 msgid "" @@ -11617,10 +12373,13 @@ msgid "" " for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` " "is set to `August 11`." msgstr "" +"Nova transferência em lote atribuída ao :guilabel:`Responsável`, `Joel " +"Willis`, para o :guilabel:`tipo de operação` `Separação`. A :guilabel:`data " +"agendada` está definida como `11 de agosto`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 msgid "View of *Batch Transfers* form." -msgstr "" +msgstr "Visualização do formulário *Transferências em lote*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:88 msgid "" @@ -11628,6 +12387,10 @@ msgid "" ":guilabel:`Add:Transfers` window, displaying only pickings. This is because " "the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." msgstr "" +"Ao clicar no botão :guilabel:`Adicionar uma linha`, é aberta a janela " +":guilabel:`Adicionar:Transferências`, exibindo apenas separações. Isso " +"ocorre porque o :guilabel:`Tipo de operação` foi definido como `Separação` " +"no formulário de transferência em lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:92 msgid "" @@ -11635,14 +12398,18 @@ msgid "" "`WH/PICK/00002`, to include them in the new transfer. Then, click the " ":guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." msgstr "" +"Clique na caixa de seleção à esquerda das transferências, `WH/PICK/00001` e " +"`WH/PICK/00002`, para incluí-las na nova transferência. Em seguida, clique " +"no botão :guilabel:`Selecionar` para fechar a janela " +":guilabel:`Adicionar:Transferências`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 msgid "Select multiple transfers from the *Add:Transfers* window." -msgstr "" +msgstr "Selecione várias transferências na janela *Adicionar:Transferências*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:101 msgid "Add batch from transfers list" -msgstr "" +msgstr "Adicionar lote da lista de transferências" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:103 msgid "" @@ -11651,12 +12418,18 @@ msgid "" ":menuselection:`Inventory app --> Operations` drop-down menu, and select any" " of the :guilabel:`Transfers` to open a filtered list of transfers." msgstr "" +"Outro método de criar transferências em lote está disponível usando a opção " +":guilabel:`Adicionar ao lote` em uma lista. Navegue até o menu suspenso " +":menuselection:`app Inventário --> Operações` e selecione qualquer uma das " +":guilabel:`Transferências` para abrir uma lista filtrada de transferências." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 msgid "" "Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" "Manufacturings, Batch Transfers, Dropships." msgstr "" +"Mostrar todos os tipos de transferência em um menu suspenso: Recibos, Entregas, Transferências internas, \n" +"Fabricações, Transferências em lote, Envios diretos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:112 msgid "" @@ -11665,11 +12438,15 @@ msgid "" "(gear)` button, and click :guilabel:`Add to batch` from the resulting drop-" "down menu." msgstr "" +"Na lista de transferências, marque a caixa de seleção à esquerda das " +"transferências selecionadas para adicionar em um lote. Em seguida, navegue " +"até o botão :guilabel:`Ações ⚙️ (engrenagem)` e clique em " +":guilabel:`Adicionar ao lote` no menu suspenso resultante." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Use *Add to batch* button, from the *Action* button's list." -msgstr "" +msgstr "Usar o botão *Adicionar ao lote* na lista do botão *Ação*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:120 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:151 @@ -11677,36 +12454,45 @@ msgid "" "Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the " "employee :guilabel:`Responsible` for the picking can be assigned." msgstr "" +"Isso abre uma janela pop-up :guilabel:`Adicionar ao lote`, na qual o " +"funcionário :guilabel:`Responsável` pela separação pode ser atribuído." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:123 msgid "" "Choose from the two radio options to add to :guilabel:`an existing batch " "transfer` or create :guilabel:`a new batch transfer`." msgstr "" +"Escolha entre as duas opções para adicionar a :guilabel:`uma transferência " +"em lote existente` ou criar :guilabel:`uma nova transferência em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:126 msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." msgstr "" +"Para começar com um rascunho, marque a caixa de seleção " +":guilabel:`Rascunho`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:128 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:160 msgid "Conclude the process by clicking :guilabel:`Confirm`." -msgstr "" +msgstr "Conclua o processo clicando em :guilabel:`Confirmar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 msgid "Show *Add to batch* window to create a batch transfer." msgstr "" +"Mostrar a janela *Adicionar ao lote* para criar uma transferência em lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:135 msgid "Process batch transfer" -msgstr "" +msgstr "Processar transferência em lote" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:137 msgid "" "Handle batch transfers in the :menuselection:`Inventory app --> Operations " "--> Batch Transfers` page." msgstr "" +"Lidar com transferências em lote na página :menuselection:`app Inventário " +"--> Operações --> Transferências em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:140 msgid "" @@ -11715,6 +12501,11 @@ msgid "" " the :guilabel:`Detailed Operations` tab. Finally, select " ":guilabel:`Validate` to complete the picking." msgstr "" +"A partir daí, selecione a transferência em questão na lista. Em seguida, no " +"formulário de transferência de lote, insira as quantidades " +":guilabel:`concluídas` para cada produto, na aba :guilabel:`Operações " +"detalhadas`. Por fim, selecione :guilabel:`Validar` para concluir a " +"separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:145 msgid "" @@ -11723,6 +12514,10 @@ msgid "" "button is highlighted instead, that means there are items in the batch that " "are currently *not* available in-stock." msgstr "" +"Certifique-se de que a transferência do lote esteja concluída quando o botão" +" :guilabel:`Validar` estiver destacado em roxo. Se, em vez disso, o botão " +":guilabel:`Verificar disponibilidade` estiver destacado, isso significa que " +"há itens no lote que, no momento, *não* estão disponíveis em estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:152 msgid "" @@ -11732,18 +12527,28 @@ msgid "" "column matches the value in the :guilabel:`Reserved` column. However, `0.00`" " quantities have been picked for the other product, `Cable Management Box`." msgstr "" +"Em uma transferência de lote envolvendo produtos de separações, " +"`WH/PICK/00001` e `WH/PICK/00002`, a aba :guilabel:`Operações detalhadas` " +"mostra que o produto, `Armário com portas`, foi retirado do armazém porque a" +" coluna :guilabel:`Concluído` corresponde ao valor na coluna " +":guilabel:`Reservado`. No entanto, quantidades de `0,00` foram retiradas " +"para o outro produto, `Caixa organizadora de cabos`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 msgid "" "Show batch transfer of products from two pickings in the *Detailed " "Operations* tab." msgstr "" +"Mostrar a transferência em lote de produtos de duas separações na aba " +"*Operações detalhadas*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:161 msgid "" "Only in-stock products are visible in the :guilabel:`Detailed Operations` " "tab." msgstr "" +"Somente os produtos em estoque são visíveis na aba :guilabel:`Operações " +"detalhadas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:163 msgid "" @@ -11753,6 +12558,12 @@ msgid "" " fulfill the order. Lastly, the :guilabel:`Done` column specifies the " "products that have been picked, and are ready for the next step." msgstr "" +"Para visualizar a lista completa de produtos, vá para a aba " +":guilabel:`Operações`. Nessa lista, a coluna :guilabel:`Demanda` indica a " +"quantidade necessária para o pedido. A coluna :guilabel:`Reservado` mostra o" +" estoque disponível para atender ao pedido. Por fim, a coluna " +":guilabel:`Concluído` especifica os produtos que foram separados e estão " +"prontos para a próxima etapa." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:169 msgid "" @@ -11761,16 +12572,22 @@ msgid "" ":guilabel:`Operations` tab because there are no :guilabel:`Reserved` " "quantities in-stock to fulfill the batch picking." msgstr "" +"O produto `Desk Pad`, do mesmo lote que o :ref:`exemplo acima " +"<inventory/management/batch-transfers-example>`, só está visível na aba " +":guilabel:`Operações` porque não há quantidades :guilabel:`reservadas` em " +"estoque para atender à separação do lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:173 msgid "" "Click the :guilabel:`Check Availability` button to search the stock again " "for available products." msgstr "" +"Clique no botão :guilabel:`Verificar disponibilidade` para pesquisar " +"novamente os produtos disponíveis no estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 msgid "Show unavailable reserved quantities in the *Operations* tab." -msgstr "" +msgstr "Mostrar quantidades reservadas indisponíveis na aba *Operações*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:180 msgid "Create backorder" @@ -11781,42 +12598,55 @@ msgid "" "On the batch transfer form, if the :guilabel:`Done` quantity of the product " "is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." msgstr "" +"No formulário de transferência de lote, se a quantidade " +":guilabel:`concluída` do produto for *menor* do que a quantidade " +":guilabel:`reservada`, uma janela pop-up será exibida." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:185 msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." msgstr "" +"Essa janela pop-up oferece a opção: :guilabel:`Criar pedido em espera?`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:187 msgid "" "Clicking the :guilabel:`Create Backorder` button automatically creates a new" " batch transfer, containing the remaining products." msgstr "" +"Clicar no botão :guilabel:`Criar pedido em espera` cria automaticamente uma " +"nova transferência de lote, contendo os produtos restantes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:190 msgid "" "Click :guilabel:`No Backorder` to finish the picking *without* creating " "another batch picking." msgstr "" +"Clique em :guilabel:`Sem pedido em espera` para concluir a separação *sem* " +"criar outra separação em lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:192 msgid "" "Click :guilabel:`Discard` to cancel the validation, and return to the batch " "transfer form." msgstr "" +"Clique em :guilabel:`Descartar` para cancelar a validação e retornar ao " +"formulário de transferência em lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 msgid "Show the *Create Backorder* pop-up." -msgstr "" +msgstr "Mostrar o pop-up *Criar pedido em espera*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:201 msgid "Process batch transfer: Barcode app" -msgstr "" +msgstr "Processar transferência de lotes: app Código de barras" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:203 msgid "" "Created batch transfers are also listed in the :menuselection:`Barcode` app," " accessible by selecting the :guilabel:`Batch Transfers` button." msgstr "" +"As transferências em lote criadas também são listadas no aplicativo " +":menuselection:`Código de barras`, que pode ser acessado selecionando o " +"botão :guilabel:`Transferências em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:206 msgid "" @@ -11824,10 +12654,15 @@ msgid "" "Transfers` page. On that page, click on the desired batch transfer to open " "the detailed list of products for the picking." msgstr "" +"Por padrão, as separações de lotes confirmadas aparecem na página " +":guilabel:`Transferências em lote`. Nessa página, clique na transferência em" +" lote em questão para abrir a lista detalhada de produtos para a separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 msgid "Show list of to-do batch transfers in *Barcode* app." msgstr "" +"Mostrar lista de transferências em lote de tarefas no aplicativo *Código de " +"barras*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:213 msgid "" @@ -11837,12 +12672,19 @@ msgid "" "the :guilabel:`✏️ (pencil)` icon, and enter the required quantities for the " "picking." msgstr "" +"Na transferência de lote escolhida, siga as instruções na parte superior da " +"página, com fundo preto. Comece digitalizando o código de barras do produto " +"para registrar um único produto para separação. Para registrar várias " +"quantidades, clique no ícone :guilabel:`✏️ (lápis)` e insira as quantidades " +"necessárias para a separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:219 msgid "" "Products from the same order are labeled with the same color on the left. " "Completed pickings are highlighted in green." msgstr "" +"Os produtos do mesmo pedido são rotulados com a mesma cor à esquerda. As " +"coletas concluídas são destacadas em verde." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:223 msgid "" @@ -11850,6 +12692,10 @@ msgid "" "and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate " "that the last two product pickings are complete." msgstr "" +"Em uma transferência de lote para 2 `Armários com portas`, 3 `Blocos " +"acústicos` e 4 `Escrivaninhas para quatro pessoas`, as `3/3` e `4/4` " +":guilabel:`unidades` indicam que as duas últimas coletas de produtos estão " +"completas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:227 msgid "" @@ -11858,26 +12704,38 @@ msgid "" "to `Scan a serial number` to record the unique serial number for " ":ref:`product tracking <inventory/serial_numbers/configure>`." msgstr "" +"1/2 unidades do `Gabinete com portas` já foram retiradas e, após a leitura " +"do código de barras do produto para o segundo armário, o Odoo solicita que o" +" usuário faça a leitura de um número de série para registrar o número de " +"série exclusivo para o :ref:`rastreamento de produtos " +"<inventory/serial_numbers/configure>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 msgid "Display products to be picked in barcode view." msgstr "" +"Exibir produtos a serem separados na visualização do código de barras." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:235 msgid "" "Once all the products have been picked, click on :guilabel:`Validate` to " "mark the batch transfer as :guilabel:`Done`." msgstr "" +"Depois que todos os produtos tiverem sido retirados, clique em " +":guilabel:`Validar` para marcar a transferência de lote como " +":guilabel:`Concluída`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:3 msgid "Closest location removal" -msgstr "" +msgstr "Remoção no local mais próximo" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:5 msgid "" "For the *Closest Location* removal strategy, products are picked based on " "the alphanumeric order of storage location titles." msgstr "" +"Para a estratégia de remoção *Local mais próximo*, os produtos são " +"selecionados com base na ordem alfanumérica dos títulos dos locais de " +"armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:8 msgid "" @@ -11885,27 +12743,34 @@ msgid "" " journey to a farther shelf when the product is also available at a closer " "location." msgstr "" +"O objetivo dessa estratégia é evitar que o funcionário do armazém faça uma " +"longa viagem até uma prateleira mais distante, quando o produto também está " +"disponível em um local mais próximo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:12 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:13 msgid ":doc:`About removal strategies <removal>`" -msgstr "" +msgstr ":doc:`Sobre estratégias de remoção <removal>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:16 msgid "" "To understand *location sequence* in the closest removal strategy, consider " "the following example:" msgstr "" +"Para entender a *sequência de localização* na estratégia de remoção mais " +"próxima, considere o seguinte exemplo:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:19 msgid "" "A product is stored in the following locations: `Shelf A/Pallet`, `Shelf " "A/Rack 1`, and `Shelf A/Rack 2`." msgstr "" +"Um produto é armazenado nos seguintes locais: `Estante A/Palete`, `Estante " +"A/Rack 1` e `Estante A/Rack 2`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 msgid "Show a mockup of real storage location in a warehouse." -msgstr "" +msgstr "Mostrar uma maquete de um local de armazenamento real em um armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:26 msgid "" @@ -11914,6 +12779,11 @@ msgid "" "`Rack 2`. The storage locations were strategically named in alphabetic " "order, based on ease of access." msgstr "" +"O sublocal, `Palete`, fica no nível do solo. Os produtos armazenados aqui " +"são mais fáceis de coletar, em comparação com a necessidade de uma " +"empilhadeira para alcançar o `Rack 1` e o `Rack 2`. Os locais de " +"armazenamento foram estrategicamente nomeados em ordem alfabética, com base " +"na facilidade de acesso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:31 msgid "" @@ -11921,15 +12791,20 @@ msgid "" ":guilabel:`Multi-Step Routes` settings **must** be enabled in " ":menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" +"Para usar essa estratégia de remoção, as configurações :guilabel:`Locais de " +"armazenamento` e :guilabel:`Rotas de várias etapas` **devem** estar ativadas" +" em :menuselection:`app Inventário --> Configuração --> Definições`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:35 msgid "" ":ref:`Set up removal strategy <inventory/warehouses_storage/removal-config>`" msgstr "" +":ref:`Configurar estratégia de remoção " +"<inventory/warehouses_storage/removal-config>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:40 msgid "Location names" -msgstr "" +msgstr "Nomes de locais" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:42 msgid "" @@ -11938,6 +12813,11 @@ msgid "" " an existing location, or click :guilabel:`New` to create a new one, and " "then enter the desired name in the :guilabel:`Location Name` field." msgstr "" +"Para configurar os nomes dos locais, comece navegando até " +":menuselection:`app Inventário --> Configuração --> Locais`. Em seguida, " +"selecione um local existente ou clique em :guilabel:`Novo` para criar um " +"novo e, em seguida, digite o nome desejado no campo :guilabel:`Nome do " +"local`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:46 msgid "" @@ -11945,18 +12825,25 @@ msgid "" " to the output or packing location, set the removal strategy on the " ":ref:`parent location <inventory/location-hierarchy>`." msgstr "" +"Depois que os locais forem nomeados em ordem alfabética, com base em sua " +"proximidade com o local de saída ou de embalagem, defina a estratégia de " +"remoção no :ref:`local principal <inventory/location-hierarchy>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:50 msgid "" "To do that, in the :guilabel:`Locations` list, select the parent location of" " the alphabetically named storage locations." msgstr "" +"Para fazer isso, na lista :guilabel:`Locais`, selecione o local superior dos" +" locais de armazenamento nomeados em ordem alfabética." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:53 msgid "" "Doing so opens the form for the parent location. In the :guilabel:`Removal " "Strategy` field, select :guilabel:`Closest Location`." msgstr "" +"Isso abre o formulário para o local superior. No campo :guilabel:`Estratégia" +" de remoção`, selecione :guilabel:`Local mais próximo`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:57 msgid "" @@ -11965,12 +12852,19 @@ msgid "" "shipment. The popular product, `iPhone charger` is stored in three " "locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." msgstr "" +"Em um armazém, o local de armazenamento `WH/Stock/Shelf 1` está localizado " +"mais próximo da área de embalagem, onde os produtos retirados das " +"prateleiras são embalados para envio. O produto popular, \"carregador de " +"iPhone\", é armazenado em três locais: \"WH/Stock/Shelf 1\", " +"\"WH/Stock/Shelf 2\" e \"WH/Stock/Shelf 3\"." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:62 msgid "" "To use closest location, set the removal strategy on the parent location, " "'WH/Stock'." msgstr "" +"Para usar o local mais próximo, defina a estratégia de remoção no local " +"superior, 'WH/Stock'." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:65 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:69 @@ -11985,21 +12879,29 @@ msgid "" "following example, featuring the popular product, `iPhone charger`, which is" " stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." msgstr "" +"Para ver como a estratégia de remoção do local mais próximo funciona, " +"considere o exemplo a seguir, que apresenta o produto popular, `carregador " +"de iPhone`, armazenado em `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2` e " +"`WH/Stock/Shelf 3`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:71 msgid "" "Fifteen, five, and thirty units are in stock at each respective location." msgstr "" +"Quinze, cinco e trinta unidades estão em estoque em cada respectivo local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:74 msgid "" "To check the on-hand stock at each storage location, navigate to the product" " form, and click the :guilabel:`On Hand` smart button." msgstr "" +"Para verificar o estoque disponível em cada local de armazenamento, navegue " +"até o formulário do produto e clique no botão inteligente :guilabel:`Em " +"mãos`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:0 msgid "Show on-hand stock at all locations." -msgstr "" +msgstr "Mostrar o estoque disponível em todos os locais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:81 msgid "" @@ -12007,6 +12909,9 @@ msgid "" "units of the `iPhone charger` by navigating to the :menuselection:`Sales " "app` and creating a new quotation." msgstr "" +"Crie um :ref:`ordem de entrega <inventory/delivery/one-step>` para dezoito " +"unidades do `carregador de iPhone` navegando até o :menuselection:`app " +"Vendas` e criando uma nova cotação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:84 msgid "" @@ -12014,6 +12919,9 @@ msgid "" "order that reserves items stored at the closest location, using the removal " "strategy." msgstr "" +"Depois de adicionar os produtos, clicar em :guilabel:`Confirmar` cria uma " +"ordem de entrega que reserva os itens armazenados no local mais próximo, " +"usando a estratégia de remoção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:87 msgid "" @@ -12022,6 +12930,10 @@ msgid "" "opens the :guilabel:`Open: Stock move` pop-up window that displays how the " "reserved items were picked, according to the removal strategy." msgstr "" +"Para obter mais detalhes sobre *onde* as unidades foram retiradas, selecione" +" o ícone :guilabel:`⦙≣`, localizado na extrema direita. Isso abre a janela " +"pop-up :guilabel:`Abrir: Movimentação de estoque` que exibe como os itens " +"reservados foram retirados, de acordo com a estratégia de remoção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:91 msgid "" @@ -12031,20 +12943,29 @@ msgid "" "`WH/Stock/Shelf 1`, are picked first. The remaining three units are then " "selected from the second closest location, `WH/Stock/Shelf 2`." msgstr "" +"Na janela pop-up :guilabel:`Abrir: Movimentação de estoque`, o campo " +":guilabel:`Separar em` exibe onde as quantidades para atender à " +":guilabel:`demanda` são retiradas. Todas as quinze unidades armazenadas no " +"local mais próximo, `WH/Stock/Shelf 1`, são retiradas primeiro. As três " +"unidades restantes são então selecionadas no segundo local mais próximo, " +"`WH/Stock/Shelf 2`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 msgid "Display *Pick From* quantities for the order for iPhone chargers." msgstr "" +"Exibir quantidades *Separar em* para o pedido de carregadores de iPhone." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 msgid "Cluster picking" -msgstr "" +msgstr "Separação em cluster" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:10 msgid "" "Cluster picking is an advanced order fulfillment approach derived from " ":ref:`batch picking <inventory/misc/batch_picking>`." msgstr "" +"A separação em cluster é uma abordagem avançada de atendimento de pedidos " +"derivada da :ref:`separação em lote <inventory/misc/batch_picking>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:13 msgid "" @@ -12053,6 +12974,10 @@ msgid "" "each storage location, and places the products directly in the package of " "the associated order." msgstr "" +"Nessa estratégia, os selecionadores carregam um carrinho com vários pacotes," +" cada um designado para um *pedido de venda* (SO) específico. Em seguida, o " +"selecionador viaja para cada local de armazenamento e coloca os produtos " +"diretamente na embalagem do pedido associado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:17 msgid "" @@ -12060,6 +12985,10 @@ msgid "" "volumes, and relatively few unique products, since the method eliminates the" " need for sorting products into packages for customers after picking." msgstr "" +"Esse método é mais eficiente para empresas de médio porte, com altos volumes" +" de pedidos e relativamente poucos produtos exclusivos, uma vez que o método" +" elimina a necessidade de classificar os produtos em pacotes para os " +"clientes após a separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:21 msgid "" @@ -12067,29 +12996,37 @@ msgid "" "orders cannot be prioritized, and optimized batches must be manually created" " beforehand. As a result, the picking process can lead to bottlenecks." msgstr "" +"No entanto, a separação em cluster tem algumas desvantagens. Por exemplo, os" +" pedidos urgentes não podem ser priorizados e os lotes otimizados devem ser " +"criados manualmente com antecedência. Como resultado, o processo de " +"separação pode levar a congestionamentos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:28 msgid "|SO| 1 calls for one apple and orange" -msgstr "" +msgstr "O |SO| 1 pede uma maçã e uma laranja" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:29 msgid "|SO| 2 calls for one apple and banana" -msgstr "" +msgstr "O |SO| item 2 pede uma maçã e uma banana" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:30 msgid "|SO| 3 calls for one apple, orange, and banana" -msgstr "" +msgstr "O |SO| 3 pede uma maçã, uma laranja e uma banana" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:32 msgid "" "Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." msgstr "" +"As maçãs são armazenadas na Prateleira A, as laranjas na Prateleira B e as " +"bananas na Prateleira C." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:34 msgid "" "To pick products for three orders at once, the cart is loaded with three " "empty packages." msgstr "" +"Para separar produtos para três pedidos de uma vez, o carrinho é carregado " +"com três embalagens vazias." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:36 msgid "" @@ -12098,6 +13035,11 @@ msgid "" "for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and " "loads packages for |SO| 2 and |SO| 3 with a banana, each." msgstr "" +"Começando na Prateleira A, o separador coloca maçãs em cada pacote. Em " +"seguida, vai até a Prateleira B e coloca laranjas nos pacotes designados " +"para o |SO| 1 e o |SO| 3. Finalmente, o separador empurra o carrinho até a " +"Prateleira C e carrega os pacotes para o |SO| 2 e o |SO| 3, cada qual com " +"uma banana." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:40 msgid "" @@ -12105,10 +13047,14 @@ msgid "" "the output location, where the packages are sealed and prepared for " "shipment." msgstr "" +"Com os pacotes de todos os três |SOs| embalados, o separador empurra o " +"carrinho para o local de saída, onde os pacotes são selados e preparados " +"para o envio." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Show example of fulfilling sales orders 2 and 3 at once." msgstr "" +"Mostrar exemplo de atendimento dos pedidos de vendas 2 e 3 de uma só vez." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:50 msgid "" @@ -12117,10 +13063,15 @@ msgid "" "heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` " "options." msgstr "" +"Para ativar a separação em clusters, comece navegando até o " +":menuselection:`app Inventário --> Configuração --> Definições`. Sob o " +"título :guilabel:`Operações`, ative as opções :guilabel:`Pacotes` e " +":guilabel:`Trasnferências em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 msgid "Activate *Packages* and *Batch Transfers* features in the settings." msgstr "" +"Ative os recursos *Pacotes* e *Transferências em lote* nas configurações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:58 msgid "" @@ -12129,6 +13080,10 @@ msgid "" "under the :guilabel:`Warehouse` heading, must also be checked on this " "settings page." msgstr "" +"Como a separação em lote é usada para otimizar a operação de *separação* no " +"Odoo, as opções :guilabel:`Locais de armazenamento` e :guilabel:`Rotas com " +"várias etapas`, sob o título :guilabel:`Armazém`, também devem ser " +"selecionadas na página de configurações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:62 msgid "" @@ -12136,14 +13091,17 @@ msgid "" "can be picked from, while *multi-step routes* enable the picking operation " "itself." msgstr "" +"Os *locais de armazenamento* permitem que os produtos sejam armazenados em " +"locais específicos dos quais podem ser retirados, enquanto as *rotas com " +"várias etapas* permitem a operação de separação em si." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:65 msgid "When finished, click :guilabel:`Save`." -msgstr "" +msgstr "Quando terminar, clique em :guilabel:`Salvar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:74 msgid "Packages setup" -msgstr "" +msgstr "Configuração de pacotes" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:76 msgid "" @@ -12151,6 +13109,9 @@ msgid "" ":menuselection:`Inventory app --> Products --> Packages`, and click the " ":guilabel:`New` button to create a new package." msgstr "" +"Depois que o recurso :guilabel:`Pacotes` for ativado, navegue até o " +":menuselection:`app Inventário --> Produtos --> Pacotes` e clique no botão " +":guilabel:`Novo` para criar um novo pacote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:79 msgid "" @@ -12158,6 +13119,10 @@ msgid "" "with the next available `PACK` number in the system. :guilabel:`Pack Date` " "is automatically set to the creation date of the form." msgstr "" +"No formulário de novo pacote, a :guilabel:`referência do pacote` é pré-" +"preenchida com o próximo número de `PACK` disponível no sistema. A " +":guilabel:`Data de embalagem` é automaticamente definida como a data de " +"criação do formulário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:83 msgid "" @@ -12167,11 +13132,17 @@ msgid "" "simply used as a method of grouping products from the same |SO| together " "before they are moved to the intended shipping box at the output location." msgstr "" +"No campo :guilabel:`Uso da embalagem`, a opção :guilabel:`Caixa descartável`" +" deverá ser selecionada se a embalagem for usada para remessa. Como " +"alternativa, a opção :guilabel:`Caixa reutilizável` deve ser selecionada se " +"a embalagem for usada simplesmente como um método de agrupar produtos do " +"mesmo |SO| antes de serem movidos para a caixa de remessa em questão no " +"local de saída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 msgid ":ref:`Packages <inventory/management/packages>`" -msgstr "" +msgstr ":ref:`Pacotes <inventory/management/packages>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:92 msgid "" @@ -12180,14 +13151,18 @@ msgid "" "their intended shipping boxes, so :guilabel:`Package Use` is set to " ":guilabel:`Disposable Box`." msgstr "" +"Um pacote destinado à separação em cluster é denominado `CLUSTER-PACK-3` " +"para facilitar a identificação. Nesse fluxo de trabalho, os produtos são " +"embalados diretamente usando suas caixas de remessa, portanto :guilabel:`Uso" +" do pacote` é definido como :guilabel:`Caixa descartável`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Create new package form." -msgstr "" +msgstr "Criar um novo formulário de pacote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:101 msgid "Create cluster batch" -msgstr "" +msgstr "Criar lote de cluster" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:103 msgid "" @@ -12197,12 +13172,19 @@ msgid "" " button becomes visible. Displayed inside the icon is a number representing " "the amount of steps in the outgoing shipment process." msgstr "" +"Para ver como a separação em cluster funciona no Odoo, navegue até o " +"aplicativo :menuselection:`Vendas` e crie |SOs| que serão atendidos juntos " +"no mesmo lote. Depois de confirmar um |SO|, o botão inteligente " +":guilabel:`Entrega` fica visível. Dentro do ícone, é exibido um número que " +"representa a quantidade de etapas no processo de envio." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:109 msgid "" "Begin by creating three |SOS| for the apples, oranges, and bananas, as shown" " in the :ref:`example above <inventory/misc/cluster_picking/example>`." msgstr "" +"Comece criando três |SOs| para as maçãs, laranjas e bananas, conforme " +"mostrado no :ref:`exemplo acima <inventory/misc/cluster_picking/example>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:112 msgid "" @@ -12210,10 +13192,13 @@ msgid "" "the number `2`, indicating there are two operations to complete: `Pick` and " "`Delivery`." msgstr "" +"Depois de confirmar o |SO|, o botão inteligente :guilabel:`Entrega` exibe o " +"número `2`, indicando que há duas operações a serem concluídas: `Separação` " +"e `Entrega`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Example sales order for an apple, orange, and banana." -msgstr "" +msgstr "Exemplo de pedido de venda de uma maçã, laranja e banana." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:119 msgid "" @@ -12222,6 +13207,10 @@ msgid "" ":guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first " "operation in the delivery flow)." msgstr "" +"Com os |SOs| criados, os pedidos agora devem ser agrupados em lotes. Para " +"fazer isso, navegue até o painel *Inventário* e selecione o cartão de tipo " +"de operação, :guilabel:`Ordens de entrega` ou :guilabel:`Separação` (o que " +"for a primeira operação no fluxo de entrega)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:123 msgid "" @@ -12229,16 +13218,21 @@ msgid "" ":guilabel:`Ready` status, indicating that all the products in the |SO| are " "in stock." msgstr "" +"Isso exibe uma lista filtrada de operações de saída com o status " +":guilabel:`Pronto`, indicando que todos os produtos no |SO| estão em " +"estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:127 msgid "" "Cluster pick batches can be created for outgoing shipments in one, two, or " "three steps." msgstr "" +"Os lotes de separação em cluster podem ser criados para remessas enviadas em" +" uma, duas ou três etapas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:130 msgid ":ref:`Delivery in one step <inventory/receipts_delivery_one_step>`" -msgstr "" +msgstr ":ref:`Entrega em uma etapa <inventory/receipts_delivery_one_step>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:134 msgid "" @@ -12247,6 +13241,10 @@ msgid "" ":guilabel:`⚙️ Actions (gear)` button, and select the :guilabel:`Add to " "batch` option from the resulting drop-down menu." msgstr "" +"Clique na caixa de seleção à esquerda da operação de saída correspondente " +"para adicioná-la ao lote. Com as escolhas desejadas selecionadas, clique no " +"botão :guilabel:`⚙️ Ações (engrenagem)` e selecione a opção " +":guilabel:`Adicionar ao lote` no menu suspenso resultante." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:139 msgid "" @@ -12254,18 +13252,24 @@ msgid "" "<inventory/misc/cluster_picking/example>`, in a warehouse configured with " "two-step outgoing shipments, the following pick operations are selected:" msgstr "" +"Para criar um lote de cluster, conforme mostrado no :ref:`exemplo acima " +"<inventory/misc/cluster_picking/example>`, em um armazém configurado com " +"remessas enviadas em duas etapas, as seguintes operações de serparação são " +"selecionadas:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:143 msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." -msgstr "" +msgstr "`WH/PICK/00007`: vinculado ao |SO| 88 para uma maçã e uma laranja." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:144 msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." -msgstr "" +msgstr "`WH/PICK/00008`: vinculado ao |SO| 89 para uma maçã e uma banana." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:145 msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." msgstr "" +"`WH/PICK/00009`: vinculado ao |SO| 90 para uma maçã, uma laranja e uma " +"banana." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:154 msgid "" @@ -12273,34 +13277,45 @@ msgid "" "to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch " "transfer`." msgstr "" +"Escolha uma das duas opções no campo :guilabel:`Adicionar a` para: adicionar" +" a :guilabel:`uma transferência em lote existente` ou criar :guilabel:`uma " +"nova transferência em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:157 msgid "" "To create draft batch pickings to be confirmed at a later date, select the " ":guilabel:`Draft` checkbox." msgstr "" +"Para criar separações em lote provisórias, a serem confirmadas em uma data " +"posterior, marque a caixa de seleção :guilabel:`Rascunho`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:167 msgid "Process batches" -msgstr "" +msgstr "Processar lotes" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:169 msgid "" "To process batches, navigate to :menuselection:`Inventory app --> Operations" " --> Batch Transfers`. Click on a batch to select it." msgstr "" +"Para processar lotes, navegue até :menuselection:`app Inventário --> " +"Operações --> Transferências em lote`. Clique em um lote para selecioná-lo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:172 msgid "" "In the :guilabel:`Detailed Operations` tab, products that are to be picked " "are grouped by location." msgstr "" +"Na aba :guilabel:`Operações detalhadas`, os produtos que devem ser separados" +" são agrupados por local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:174 msgid "" "Under the :guilabel:`Source Package` or :guilabel:`Destination Package` " "field, enter the package used for the picking." msgstr "" +"No campo :guilabel:`Pacote de origem` ou :guilabel:`Pacote de destino`, " +"digite o pacote usado para a separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:178 msgid "" @@ -12309,12 +13324,20 @@ msgid "" "package>`. This means the products are temporarily placed in a container " "during picking, before getting transferred to their final shipping box." msgstr "" +"Use o campo :guilabel:`Pacote de origem` quando o pacote de separação " +"estiver configurado como *reutilizável* no formulário :ref:`pacote " +"<inventory/misc/create-package>`. Isso significa que os produtos são " +"temporariamente colocados em um contêiner durante a separação, antes de " +"serem transferidos para a caixa de envio final." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:182 msgid "" "Alternatively, use the :guilabel:`Destination Package` field when the " "product is directly placed in its *disposable* shipping box during picking." msgstr "" +"Como alternativa, use o campo :guilabel:`Pacote de destino` quando o produto" +" for colocado diretamente em sua caixa de remessa *descartável* durante a " +"separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:186 msgid "" @@ -12322,6 +13345,9 @@ msgid "" "bananas :ref:`example <inventory/misc/cluster_picking/example>` by assigning" " each picking to a dedicated package." msgstr "" +"Processe o lote de cluster para os três pedidos de maçãs, laranjas e bananas" +" :ref:`exemplo <inventory/misc/cluster_picking/example>` atribuindo cada " +"separação a um pacote dedicado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:189 msgid "" @@ -12329,20 +13355,25 @@ msgid "" " all three pickings to one of the three disposable packages, `CLUSTER-" "PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." msgstr "" +"No local de armazenamento de maçãs, `WH/Stock/Shelf A`, atribua as maçãs de " +"todas as três separações a uma das três embalagens descartáveis, `CLUSTER-" +"PACK-1`, `CLUSTER-PACK-2` ou `CLUSTER-PACK-3`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:192 msgid "" "Record this in Odoo using the :guilabel:`Destination Package` field in the " ":guilabel:`Detailed Operations` tab." msgstr "" +"Registre isso no Odoo usando o campo :guilabel:`Pacote de destino` na aba " +":guilabel:`Operações detalhadas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Example of processing cluster pickings in *Inventory*." -msgstr "" +msgstr "Exemplo de processamento de separações em cluster em *Inventário*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:200 msgid "In Barcode" -msgstr "" +msgstr "No app Código de barras" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:202 msgid "" @@ -12350,6 +13381,9 @@ msgid "" ":guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, " "select the desired batch." msgstr "" +"Para processar as separações em cluster diretamente do aplicativo *Código de" +" barras*, selecione o botão :guilabel:`Transferências em lote` no painel do " +"*Código de barras*. Em seguida, selecione o lote desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:205 msgid "" @@ -12357,6 +13391,9 @@ msgid "" "location, and each line is color-coded to associate products in the same " "picking together." msgstr "" +"Na tela de transferência de lote, os produtos na separação são agrupados por" +" localização, e cada linha é codificada por cores para associar produtos da " +"mesma separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:208 msgid "" @@ -12364,11 +13401,16 @@ msgid "" "the storage location of the first product. Then, scan the barcode for the " "product and package to process the transfer." msgstr "" +"Em seguida, siga o prompt para :guilabel:`Escanear o local de destino` com o" +" código de barras para o local de armazenamento do primeiro produto. Em " +"seguida, leia o código de barras do produto e da embalagem para processar a " +"transferência." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:211 msgid "" "Repeat this for all products, and click the :guilabel:`Validate` button." msgstr "" +"Repita isso para todos os produtos e clique no botão :guilabel:`Validar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:214 msgid "" @@ -12377,16 +13419,22 @@ msgid "" "(gear)` icon at the top of the package form, and select the " ":guilabel:`Print` option." msgstr "" +"Para localizar o código de barras do pacote, navegue até :menuselection:`app" +" Inventário --> Produtos --> Pacotes`, selecione o pacote desejado, clique " +"no ícone :guilabel:`⚙️ (engrenagem)` na parte superior do formulário do " +"pacote e selecione a opção :guilabel:`Imprimir`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:218 msgid "" "Next, select one of the three print options to generate the package barcode " "from the :guilabel:`Package Reference` field." msgstr "" +"Em seguida, selecione uma das três opções de impressão para gerar o código " +"de barras do pacote a partir do campo :guilabel:`Referência do pacote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Display where the package barcode can be generated." -msgstr "" +msgstr "Exibir onde o código de barras do pacote pode ser gerado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:226 msgid "" @@ -12395,22 +13443,30 @@ msgid "" "<barcode/setup/location>`. Doing so highlights all the pickings that need " "products from this particular location." msgstr "" +"Comece a processar a separação em cluster indo para o primeiro local de " +"armazenamento, \"Prateleira A\", e lendo o código de barras de " +"\"ref:`local\" <barcode/setup/location>`. Isso destaca todos as separações " +"que precisam de produtos desse local específico." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:230 msgid "" "Scan the barcode for the apple, which highlights the picking (labeled in " "red) for the product `Apple`, for the picking, `WH/PICK/00007`." msgstr "" +"Leia o código de barras da maçã, que destaca a separação (marcada em " +"vermelho) do produto `Maçã` para a separação `WH/PICK/00007`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:233 msgid "" "Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in " "the designated package." msgstr "" +"Em seguida, leia o código de barras da embalagem `CLUSTER-PACK-1` e coloque " +"o produto no pacote designado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 msgid "Example of cluster batch from the *Barcode* app." -msgstr "" +msgstr "Exemplo de lote de cluster do aplicativo *Código de barras*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:240 msgid "" @@ -12418,10 +13474,14 @@ msgid "" "suggests the specified package by displaying the name *in italics* under the" " product name, ensuring pickers place products into the correct boxes." msgstr "" +"Depois de criar uma transferência em lote e atribuir um pacote a uma " +"separação, o Odoo sugere o pacote especificado exibindo o nome *em itálico* " +"sob o nome do produto, garantindo que os selecionadores coloquem os produtos" +" nas caixas corretas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:3 msgid "Organize a cross-dock in a warehouse" -msgstr "" +msgstr "Organizar uma distribuição integrada em um armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:5 msgid "" @@ -12430,6 +13490,10 @@ msgid "" " unloaded in a *Cross-Dock* area in order to reorganize products and load " "another truck." msgstr "" +"A distribuição integrada (Cross-Dock) é o processo de envio de produtos " +"recebidos diretamente aos clientes, sem que eles entrem no estoque. Os " +"caminhões são simplesmente descarregados em uma área de *Distribuição " +"integrada* para reorganizar os produtos e carregar em outro caminhão." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:13 msgid "" @@ -12437,16 +13501,22 @@ msgid "" " is cross-docking and is it for me? <https://www.odoo.com/blog/business-" "hacks-1/post/what-is-cross-docking-and-is-it-for-me-270>`_" msgstr "" +"Para obter mais informações sobre como organizar seu armazém, leia nosso " +"blog: `O que é distribuição integrada e será que devo utilizá-la? " +"<https://www.odoo.com/blog/business-hacks-1/post/what-is-cross-docking-and-" +"is-it-for-me-270>`_" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:20 msgid "" "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and" " activate the *Multi-Step Routes*." msgstr "" +"No aplicativo *Inventárop*, abra :menuselection:`Configuração --> " +"Definições` e ative as *Rotas com várias etapas*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:27 msgid "Doing so will also enable the *Storage Locations* feature." -msgstr "" +msgstr "Isso também ativará o recurso *Locais de armazenamento*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:29 msgid "" @@ -12454,16 +13524,23 @@ msgid "" "with 2 steps. To adapt the configuration, go to :menuselection:`Inventory " "--> Configuration --> Warehouses` and edit your warehouse." msgstr "" +"Agora, as remessas *recebidas* e *enviadas* devem ser configuradas para " +"funcionar com duas etapas. Para adaptar a configuração, vá para " +":menuselection:`Inventário --> Configuração --> Armazéns` e edite seu " +"armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:36 msgid "" "This modification will lead to the creation of a *Cross-Docking* route that " "can be found in :menuselection:`Inventory --> Configuration --> Routes`." msgstr "" +"Essa modificação levará à criação de uma rota *Distribuição integrada* que " +"pode ser encontrada em :menuselection:`Inventário --> Configuração --> " +"Rotas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:43 msgid "Configure products with Cross-Dock Route" -msgstr "" +msgstr "Configurar produtos com rota de distribuição integrada" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:45 msgid "" @@ -12472,6 +13549,10 @@ msgid "" "purchase tab, specify the vendor to who you buy the product and set a price " "for it." msgstr "" +"Crie o produto que usa a *rota de distribuição integrada* e, em seguida, na " +"aba Inventário, selecione as rotas *Comprar* e *Distribuição integrada*. " +"Agora, na aba Compra, especifique o fornecedor do qual você compra o produto" +" e defina um preço." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:55 msgid "" @@ -12483,6 +13564,13 @@ msgid "" "your *Customer Location. Both are in state *Waiting Another Operation* " "because we still need to order the product to our supplier." msgstr "" +"Feito isso, crie um pedido de venda do produto e confirme-o. O Odoo criará " +"automaticamente duas transferências que serão vinculadas ao pedido de venda." +" A primeira é a transferência do *Local de entrada* para o *Local de saída*," +" correspondente à movimentação do produto na área *Distribuição integrada*. " +"A segunda é a ordem de entrega do *Local de saída* para o *Local do " +"cliente*. Ambos estão no status *Aguardando outra operação* porque ainda " +"precisamos fazer o pedido do produto ao nosso fornecedor." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:68 msgid "" @@ -12490,6 +13578,9 @@ msgid "" "has been automatically triggered by the system. Validate it and receive the " "products in the *Input Location*." msgstr "" +"Agora, vá para o aplicativo *Compras*. Lá, você encontrará o pedido de " +"compra que foi acionado automaticamente pelo sistema. Valide-o e receba os " +"produtos no *Local de entrada*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:77 msgid "" @@ -12497,15 +13588,20 @@ msgid "" "your initial sale order and validate the internal transfer from *Input* to " "*Output*." msgstr "" +"Quando os produtos forem recebidos do fornecedor, você poderá voltar ao seu " +"pedido de venda inicial e validar a transferência interna de *Entrada* para " +"*Saída*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:86 msgid "" "The delivery order is now ready to be processed and can be validated too." msgstr "" +"O pedido de entrega agora está pronto para ser processado e também pode ser " +"validado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:3 msgid "Cycle counts" -msgstr "" +msgstr "Contagens de ciclos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:5 msgid "" @@ -12514,6 +13610,10 @@ msgid "" " scheduled date for the next inventory count is set for the 31st of December" " of the current year." msgstr "" +"Para a maioria das empresas, o estoque do armazém só precisa ser contado uma" +" vez por ano. É por isso que, por padrão, depois de fazer um *ajuste de " +"estoque* no Odoo, a data programada para a próxima contagem de estoque é " +"definida para o dia 31 de dezembro do ano atual." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:9 msgid "" @@ -12523,16 +13623,25 @@ msgid "" "their inventory more often in certain *locations*, to ensure that their " "physical inventory counts match their inventory records." msgstr "" +"Entretanto, para algumas empresas, é fundamental ter uma contagem de estoque" +" precisa o tempo todo. Essas empresas usam *contagens cíclicas* para manter " +"precisos os níveis críticos de estoque. A contagem cíclica é um método pelo " +"qual as empresas contam seu inventário com mais frequência em determinados " +"*locais*, para garantir que as contagens do inventário físico correspondam " +"aos registros de inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:15 msgid "Activate storage locations" -msgstr "" +msgstr "Ativar locais de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:17 msgid "" "In Odoo, cycle counts are location-based. Therefore, the *storage locations*" " feature needs to be enabled before performing a cycle count." msgstr "" +"No Odoo, as contagens de ciclos são baseadas em locais. Portanto, o recurso " +"*locais de armazenamento* precisa ser ativado antes de realizar uma contagem" +" de ciclos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:20 msgid "" @@ -12541,20 +13650,30 @@ msgid "" "section. Then, click the checkbox next to :guilabel:`Storage Locations`. " "Click :guilabel:`Save` to save all changes." msgstr "" +"Para ativar esse recurso, navegue até o :menuselection:`app Inventário --> " +"Configuração --> Definições` e role para baixo até a seção " +":guilabel:`Armazém`. Em seguida, clique na caixa de seleção ao lado de " +":guilabel:`Locais de armazenamento`. Clique em :guilabel:`Salvar` para " +"gravar todas as alterações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 msgid "Enabled storage locations setting in inventory settings." msgstr "" +"Configuração de locais de armazenamento habilitada nas definições do app " +"Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:29 msgid "Change inventory count frequency by location" -msgstr "" +msgstr "Alterar a frequência de contagem de inventário por local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:31 msgid "" "Now that the storage locations setting is enabled, the inventory count " "frequency can be changed for specific locations created in the warehouse." msgstr "" +"Agora que a configuração de locais de armazenamento está ativada, a " +"frequência de contagem do inventário pode ser alterada para locais " +"específicos criados no armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:34 msgid "" @@ -12562,6 +13681,9 @@ msgid "" "Configuration --> Locations`. This reveals a :guilabel:`Locations` page " "containing every location currently created and listed in the warehouse." msgstr "" +"Para visualizar e editar locais, navegue até :menuselection:`app Inventário " +"--> Configuração --> Locais`. Isso abre uma página :guilabel:`Locais` que " +"contém todos os locais atualmente criados e listados no armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:38 msgid "" @@ -12569,6 +13691,9 @@ msgid "" "configuration page for that location. Click :guilabel:`Edit` to edit the " "location settings." msgstr "" +"Nessa página, clique em um local para abrir a página de definições e " +"configuração desse local. Clique em :guilabel:`Editar` para editar as " +"configurações do local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:41 msgid "" @@ -12577,16 +13702,22 @@ msgid "" " this location has not been edited previously). In this field, change the " "value to whichever number of days is desired." msgstr "" +"Na seção :guilabel:`Inventário ciclíco`, localize o campo " +":guilabel:`Frenquência de inventário (dias)`, que deve ser definido como `0`" +" (se esse local não tiver sido editado anteriormente). Nesse campo, altere o" +" valor para o número de dias desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 msgid "Location frequency setting on location." -msgstr "" +msgstr "Definição da frequência de localização no local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:50 msgid "" "A location that needs an inventory count every 30 days should have the " ":guilabel:`Inventory Frequency (Days)` value set to `30`." msgstr "" +"Um local que precisa de uma contagem de inventário a cada 30 dias deve ter o" +" valor :guilabel:`Frequência de inventário (dias)` definido como `30`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:53 msgid "" @@ -12596,10 +13727,15 @@ msgid "" "set, based on the value entered into the :guilabel:`Inventory Frequency " "(Days)` field." msgstr "" +"Depois que a frequência tiver sido alterada para o número de dias desejado, " +"clique em :guilabel:`Salvar` para gravar as alterações. Agora, quando um " +"ajuste de inventário for aplicado a esse local, a próxima data de contagem " +"programada será definida automaticamente, com base no valor inserido no " +"campo :guilabel:`Frequência de inventário (dias)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 msgid "Count inventory by location" -msgstr "" +msgstr "Contagem de inventário por local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 msgid "" @@ -12608,6 +13744,11 @@ msgid "" "This reveals an :guilabel:`Inventory Adjustments` page containing all " "products currently in stock, with each product listed on its own line." msgstr "" +"Para realizar uma contagem de ciclos em um local específico do armazém, " +"navegue até :menuselection:`app Inventário --> Operações --> Ajustes de " +"inventário`. Isso revela uma página :guilabel:`Ajustes de inventário` que " +"contém todos os produtos atualmente em estoque, com cada produto listado em " +"sua própria linha." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 msgid "" @@ -12615,10 +13756,14 @@ msgid "" " the top of the page, under the :guilabel:`Search...` bar), can be used to " "select specific locations and perform inventory counts." msgstr "" +"Nessa página, os botões :guilabel:`Filtros` e :guilabel:`Agrupar por` (na " +"parte superior da página, sob a barra :guilabel:`Pesquisar…`) podem ser " +"usados para selecionar locais específicos e realizar contagens de " +"inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 msgid "Inventory adjustments page." -msgstr "" +msgstr "Página de ajustes de inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 msgid "" @@ -12626,6 +13771,10 @@ msgid "" "click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to " "reveal a new drop-down menu to the right." msgstr "" +"Para selecionar um local específico e visualizar todos os produtos nesse " +"local, clique em :guilabel:`Agrupar por` e, em seguida, clique em " +":guilabel:`Adicionar grupo personalizado` para exibir um novo menu suspenso " +"à direita." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 msgid "" @@ -12634,6 +13783,10 @@ msgid "" "location in the warehouse that has products in stock, and a cycle count can " "be performed for all products in that location." msgstr "" +"Clique em :guilabel:`Local` no menu suspenso e, em seguida, clique em " +":guilabel:`Aplicar`. A página agora exibe menus suspensos condensados de " +"cada local no armazém que tem produtos em estoque, e uma contagem de ciclo " +"pode ser executada para todos os produtos nesse local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 msgid "" @@ -12643,6 +13796,11 @@ msgid "" "Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right." " Click this menu to reveal three drop-downs." msgstr "" +"Em grandes armazéns com vários locais e um grande volume de produtos, pode " +"ser mais fácil pesquisar o local específico desejado. Para fazer isso, na " +"página :guilabel:`Ajustes de inventário`, clique em :guilabel:`Filtros`. Em " +"seguida, clique em :guilabel:`Adicionar filtro personalizado` para exibir um" +" novo menu à direita. Clique nesse menu para exibir três menus suspensos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 msgid "" @@ -12651,14 +13809,18 @@ msgid "" "the third field, type in the name of the location that is being searched " "for. Click :guilabel:`Apply` for that location to appear on the page." msgstr "" +"Para o primeiro campo, clique e selecione :guilabel:`Local` no menu " +"suspenso. Para o segundo campo, deixe o valor :guilabel:`contém` como está. " +"No terceiro campo, digite o nome do local que está sendo pesquisado. Clique " +"em :guilabel:`Aplicar` para que esse local apareça na página." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 msgid "Applied filters and group by on inventory adjustments page." -msgstr "" +msgstr "Agrupamento e filtros aplicados e na página de ajustes de inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 msgid "Change full inventory count frequency" -msgstr "" +msgstr "Alterar a frequência de contagem de inventário completo" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 msgid "" @@ -12666,6 +13828,9 @@ msgid "" "for full inventory counts of everything in-stock in the warehouse can also " "be manually changed to push the date up sooner than the date listed." msgstr "" +"Embora as contagens de ciclo sejam normalmente realizadas por local, a data " +"agendada para as contagens completas de tudo o que está em estoque no " +"armaźem também pode ser antecipada manualmente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 msgid "" @@ -12675,16 +13840,23 @@ msgid "" "field, which includes a drop-down that is set to `31` :guilabel:`December` " "by default." msgstr "" +"Para modificar a data agendada padrão, vá para :menuselection:`app " +"Inventário --> Configuração --> Definições`. Em seguida, na seção " +":guilabel:`Operações`, localize o campo de configuração :guilabel:`Dia e mês" +" do inventário anual`, que inclui um menu suspenso definido como `31` de " +":guilabel:`dezembro` por padrão." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 msgid "Frequency field in inventory app settings." -msgstr "" +msgstr "Campo de frequência nas configurações do aplicativo de inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 msgid "" "To change the day, click the `31`, and change it to a day within the range " "`1-31`, depending on the desired month of the year." msgstr "" +"Para alterar o dia, clique em `31` e altere-o para um dia dentro do " +"intervalo `1-31`, dependendo do mês do ano desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 @@ -12692,34 +13864,40 @@ msgid "" "Then, to change the month, click :guilabel:`December` to reveal the drop-" "down menu, and select the desired month." msgstr "" +"Em seguida, para alterar o mês, clique em :guilabel:`dezembro` para exibir o" +" menu suspenso e selecione o mês desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 msgid "" "Once all changes have been made, click :guilabel:`Save` to save all changes." msgstr "" +"Depois que todas as alterações tiverem sido feitas, clique em " +":guilabel:`Salvar` para gravar todas as alterações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 msgid ":doc:`../inventory_management/count_products`" -msgstr "" +msgstr ":doc:`../inventory_management/count_products`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:3 msgid "FEFO removal" -msgstr "" +msgstr "Remoção PVPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:5 msgid "" "The *First Expired, First Out* (FEFO) removal strategy targets products for " "removal based on their assigned removal dates." msgstr "" +"A estratégia de remoção *Primeiro a vencer, primeiro a sair* (PVPS) visa à " +"remoção de produtos com base em suas datas de remoção atribuídas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:9 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:9 msgid ":doc:`Other removal strategies <removal>`" -msgstr "" +msgstr ":doc:`Outras estratégias de remoção <removal>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:14 msgid "Removal date" -msgstr "" +msgstr "Data de remoção" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:16 msgid "" @@ -12727,6 +13905,9 @@ msgid "" "which is set as a certain number of days before the product's *expiration " "date*." msgstr "" +"Os produtos **devem** ser removidos do estoque antes de sua *data de " +"remoção*, que é definida como um determinado número de dias antes da *data " +"de expiração* do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:19 msgid "" @@ -12735,12 +13916,19 @@ msgid "" "ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` " "or :guilabel:`By Unique Serial Number`." msgstr "" +"O usuário define esse número de dias navegando até a guia " +":guilabel:`Inventário` do formulário do produto. Na seção " +":guilabel:`Rastreabilidade`, verifique se o campo :guilabel:`Rastreamento` " +"está definido como :guilabel:`Por lotes` ou :guilabel:`Por número de série " +"exclusivo`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:23 msgid "" "Next, select the :guilabel:`Expiration Date` option, which makes the " ":guilabel:`Removal Date` field (and other date fields) appear." msgstr "" +"Em seguida, selecione a opção :guilabel:`Data de expiração`, que faz com que" +" o campo :guilabel:`Data de remoção` (e outros campos de data) seja exibido." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:27 msgid "" @@ -12748,6 +13936,9 @@ msgid "" "features **must** be enabled in :menuselection:`Inventory app --> " "Configuration --> Settings` to track expiration dates." msgstr "" +"Os recursos :guilabel:`Números de série e lotes` e :guilabel:`Datas de " +"expiração` **devem** ser ativados em :menuselection:`app Inventário --> " +"Configuração --> Definições` para rastrear as datas de vencimento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:31 msgid "" @@ -12755,36 +13946,47 @@ msgid "" "product was received to the number of days specified in the " ":guilabel:`Expiration Date` field of the product form." msgstr "" +"A data de validade de um produto é determinada pela adição da data em que o " +"produto foi recebido ao número de dias especificado no campo :guilabel:`Data" +" de validade` do formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:34 msgid "" "The removal date takes this expiration date, and subtracts the number of " "days specified in the :guilabel:`Removal Date` field of the product form." msgstr "" +"A data de remoção considera essa data de expiração e subtrai o número de " +"dias especificado no campo :guilabel:`Data de remoção` do formulário do " +"produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:38 msgid "" ":doc:`Expiration dates " "<../../product_management/product_tracking/expiration_dates>`" msgstr "" +":doc:`Datas de expiração " +"<../../product_management/product_tracking/expiration_dates>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:41 msgid "" "In the :guilabel:`Inventory` tab of the product, `Egg`, the following " ":guilabel:`Dates` are set by the user:" msgstr "" +"Na guia :guilabel:`Inventário` do produto, `Ovo`, as seguintes " +":guilabel:`Datas` são definidas pelo usuário:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:44 msgid ":guilabel:`Expiration Date`: `30` days after receipt" -msgstr "" +msgstr ":guilabel:`Data de expiração`: `30` dias após o recebimento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:45 msgid ":guilabel:`Removal Date`: `15` days before expiration date" -msgstr "" +msgstr ":guilabel:`Data de remoção`: `15` dias antes da data de expiração" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 msgid "Display expiration and removal dates set on the product form." msgstr "" +"Exibir datas de validade e remoção definidas no formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:51 msgid "" @@ -12792,12 +13994,17 @@ msgid "" "expiration date of the Eggs is **January 31st** (Jan 1st + 30). By " "extension, the removal date is **January 16th** (Jan 31 - 15)." msgstr "" +"Uma remessa de ovos chega ao armazém em 1º de janeiro. Portanto, a data de " +"vencimento dos ovos é **31 de janeiro** (1º de janeiro + 30). Por extensão, " +"a data de remoção é **16 de janeiro** (31 de janeiro - 15)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:57 msgid "" "To view the expiration dates of items in stock, navigate to the product " "form, and click the :guilabel:`On Hand` smart button." msgstr "" +"Para visualizar as datas de expiração dos itens em estoque, navegue até o " +"formulário do produto e clique no botão inteligente :guilabel:`Em mãos`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:60 msgid "" @@ -12805,18 +14012,26 @@ msgid "" "select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal " "Date`." msgstr "" +"Em seguida, clique no ícone de opções adicionais, localizado na extrema " +"direita, e selecione as colunas: :guilabel:`Data de expiração` e " +":guilabel:`Data de remoção`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 msgid "" "Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" "smart button from the product form." msgstr "" +"Mostrar as datas de expiração do modelo de ajustes de estoque acessado pelo botão *Em mãos*\n" +"smart do formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:71 msgid "" "Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures " "that products with the nearest removal date are picked first." msgstr "" +"O uso da estratégia de remoção :abbr:`PVPS (Primeiro a vencer, primeiro a " +"sair)` garante que os produtos com a data de remoção mais próxima sejam " +"retirados primeiro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:74 msgid "" @@ -12824,6 +14039,9 @@ msgid "" "example below about the product, `Carton of eggs`, which is a box containing" " twelve eggs." msgstr "" +"Para entender como essa estratégia de remoção funciona, considere o exemplo " +"a seguir sobre o produto `Caixa de ovos`, que é uma caixa contendo doze " +"ovos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:77 msgid "" @@ -12831,6 +14049,9 @@ msgid "" ":guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First" " Out (FEFO)`." msgstr "" +"O produto é rastreado :guilabel:`Por lotes` e a definição de " +":guilabel:`Forçar estratégia de remoção` da categoria do produto é " +":guilabel:`Primeiro a vencer, primeiro a sair (PVPS)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:81 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:59 @@ -12839,42 +14060,48 @@ msgid "" ":ref:`Set up force removal strategy <inventory/warehouses_storage/removal-" "config>`" msgstr "" +":ref:`Configurar estratégia de remoção forçada " +"<inventory/warehouses_storage/removal-config>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:82 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:60 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:25 msgid ":ref:`Enable lots tracking <inventory/warehouses_storage/lots-setup>`" msgstr "" +":ref:`Habilitar rastreamento de lotes <inventory/warehouses_storage/lots-" +"setup>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:83 msgid "" "`Odoo Tutorials: Perishable Products " "<https://www.odoo.com/slides/slide/5324/share>`_" msgstr "" +"`Tutoriais do Odoo: Produtos perecíveis " +"<https://www.odoo.com/slides/slide/5324/share>`_" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:90 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:69 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:35 msgid "LOT1" -msgstr "" +msgstr "LOTE1" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:91 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:70 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:36 msgid "LOT2" -msgstr "" +msgstr "LOTE2" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:92 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:71 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:37 msgid "LOT3" -msgstr "" +msgstr "LOTE3" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:93 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:72 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:38 msgid "On-hand stock" -msgstr "" +msgstr "Estoque em mãos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:94 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:73 @@ -12897,37 +14124,39 @@ msgstr "Data de expiração" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:98 msgid "April 4" -msgstr "" +msgstr "4 de abril" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:99 msgid "April 10" -msgstr "" +msgstr "10 de abril" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:100 msgid "April 15" -msgstr "" +msgstr "15 de abril" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:101 msgid ":ref:`Removal date <inventory/warehouses_storage/exp-date>`" -msgstr "" +msgstr ":ref:`Data de remoção <inventory/warehouses_storage/exp-date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:102 msgid "February 26" -msgstr "" +msgstr "26 de fevereiro" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:103 msgid "March 4" -msgstr "" +msgstr "4 de março" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:104 msgid "March 9" -msgstr "" +msgstr "9 de março" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:106 msgid "" "To see the removal strategy in action, go to the :menuselection:`Sales app` " "and create a new quotation." msgstr "" +"Para ver a estratégia de remoção em ação, acesse o :menuselection:`app " +"Vendas` e crie uma nova cotação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:109 msgid "" @@ -12935,6 +14164,10 @@ msgid "" "29th, and the lot numbers with the soonest expiration dates are reserved, " "using the :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" +"Clicar em :guilabel:`Confirmar` cria uma ordem de entrega para hoje, 29 de " +"dezembro, e os números de lote com as datas de vencimento mais próximas são " +"reservados, usando a estratégia de remoção :abbr:`PVPS (Primeiro a vencer, " +"primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:113 msgid "" @@ -12943,6 +14176,10 @@ msgid "" ":guilabel:`Operations` tab of the delivery order. Doing so opens the " ":guilabel:`Open: Stock move` pop-up window." msgstr "" +"Para visualizar as coletas detalhadas, clique no ícone :guilabel:`⦙≣ " +"(lista)`, localizado na extremidade direita da linha de produtos Caixa de " +"ovos, na aba :guilabel:`Operações` da ordem de entrega. Isso abre a janela " +"pop-up :guilabel:`Abrir: Movimentação de estoque`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:117 msgid "" @@ -12950,6 +14187,9 @@ msgid "" " field displays where the quantities to fulfill the :guilabel:`Demand` are " "picked from." msgstr "" +"Na janela pop-up :guilabel:`Abrir: Movimentação de estoque`, o campo " +":guilabel:`Separar em` exibe de onde são retiradas as quantidades para " +"atender à :guilabel:`demanda`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:120 msgid "" @@ -12958,14 +14198,19 @@ msgid "" "the removal date of February 26th, are picked. The remaining Carton is " "selected from `LOT2`, which has a removal date of March 4th." msgstr "" +"Como o pedido exigia seis caixas de ovos, usando a estratégia de remoção " +":abbr:`PVPS (Primeiro a vencer, primeiro a sair)`, todas as cinco caixas do " +"`LOTE1`, com data de remoção de 26 de fevereiro, são selecionadas. A caixa " +"restante é selecionada da `LOTE2`, que tem data de remoção em 4 de março." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 msgid "The stock moves window that shows the lots to be removed using FEFO." msgstr "" +"Janela de movimentação de estoque que mostra os lotes a remover por PVPS." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:3 msgid "FIFO removal" -msgstr "" +msgstr "Remoção PEPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:5 msgid "" @@ -12975,10 +14220,15 @@ msgid "" ":abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock " "retention of specific styles." msgstr "" +"A estratégia de remoção *Primeiro a entrar, primeiro a sair* (PEPS) " +"seleciona os produtos com as primeiras datas de chegada. Esse método é útil " +"para empresas que vendem produtos com ciclos de demanda curtos, como roupas," +" por exemplo. Ao usar :abbr:`PEPS`, as empresas podem evitar a retenção " +"prolongada de estoque de estilos específicos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:11 msgid ":doc:`Other removal methods <removal>`" -msgstr "" +msgstr ":doc:`Outros métodos de remoção <removal>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:14 msgid "" @@ -12988,20 +14238,27 @@ msgid "" "have been in stock the longest. So, products received on August 1st are " "selected first for picking." msgstr "" +"Várias quantidades do produto `Camiseta`, rastreadas por números de lote, " +"chegam em 1º e 25 de agosto. Para um pedido feito em 1º de setembro, a " +"estratégia de remoção :abbr:`PEPS (Primeiro a entrar, primeiro a sair) ` " +"prioriza os lotes que estão em estoque há mais tempo. Portanto, os produtos " +"recebidos em 1º de agosto são selecionados primeiro para a retirada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 msgid "Illustration of FIFO selecting the oldest products in stock." -msgstr "" +msgstr "Ilustração de PEPS selecionando os produtos mais antigos em estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:24 msgid "" ":ref:`Lot/serial number setup details <inventory/warehouses_storage/lots-" "setup>`" msgstr "" +":ref:`Detalhes de configuração do número de série/lote " +"<inventory/warehouses_storage/lots-setup>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:29 msgid "Arrival date" -msgstr "" +msgstr "Data de chegada" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:31 msgid "" @@ -13009,6 +14266,9 @@ msgid "" "navigate to :menuselection:`Inventory app --> Products --> Lots/Serial " "Numbers`." msgstr "" +"Para ver o lote do produto ou o número de série que chegou primeiro ao " +"estoque, navegue até :menuselection:`app Inventário --> Produtos --> Números" +" de série/lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:34 msgid "" @@ -13017,40 +14277,57 @@ msgid "" "numbers that are in stock. The :guilabel:`Created On` field shows the " "lot/serial number creation date, which is, essentially, the arrival date." msgstr "" +"Em seguida, selecione o ícone :guilabel:`▶️ (seta apontando para a direita) " +"` à esquerda de uma linha de produto para exibir uma lista dos lotes ou " +"números de série do produto que estão em estoque. O campo :guilabel:`Criado " +"em` mostra a data de criação do número de série/lote, que é, essencialmente," +" a data de chegada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:39 msgid "" "Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on" " December 29th, as displayed in the :guilabel:`Created On` field." msgstr "" +"O número de série `00000000500` do produto, `Gabinete com portas`, chegou em" +" 29 de dezembro, conforme exibido no campo :guilabel:`Criado em`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 msgid "Display arrival date of a lot for an item." -msgstr "" +msgstr "Exibir a data de chegada de um lote para um item." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:49 msgid "" "To understand how :abbr:`FIFO (First In, First Out)` rotates products out, " "consider the following example, focusing on three lots of white shirts." msgstr "" +"Para entender como o :abbr:`PEPS (Primeiro a entrar, primeiro a sair)` faz o" +" rodízio de produtos, considere o exemplo a seguir, com foco em três lotes " +"de camisas brancas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:52 msgid "" "The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In," " First Out)` is set as the :guilabel:`Force Removal Strategy`." msgstr "" +"As camisas são da categoria *Tudo/Roupas*, onde :abbr:`PEPS (Primeiro a " +"entrar, primeiro a sair)` é definido para :guilabel:`Forçar estratégia de " +"separação de estoque`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:55 msgid "" "The white shirts are tracked :guilabel:`By Lots` in the " ":guilabel:`Inventory` tab of the product form." msgstr "" +"As camisas brancas são rastreadas :guilabel:`Por lotes` na aba " +":guilabel:`Inventário` do formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:62 msgid "" "The following table represents the on-hand stock and lot number details of " "white shirts." msgstr "" +"A tabela a seguir representa o estoque disponível e os detalhes do número do" +" lote de camisas brancas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:74 msgid "3" @@ -13059,19 +14336,19 @@ msgstr "3" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:76 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:42 msgid ":ref:`Created on <inventory/warehouses_storage/arrival_date>`" -msgstr "" +msgstr ":ref:`Criado em <inventory/warehouses_storage/arrival_date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:77 msgid "March 1" -msgstr "" +msgstr "1º de março" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:78 msgid "April 1" -msgstr "" +msgstr "1º de abril" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:79 msgid "May 1" -msgstr "" +msgstr "1º de maio" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:81 msgid "" @@ -13079,6 +14356,9 @@ msgid "" "<inventory/delivery/one-step>` for six white shirts by navigating to the " ":menuselection:`Sales app` and creating a new quotation." msgstr "" +"Para ver a estratégia de remoção em ação, crie um :ref:`ordem de entrega " +"<inventory/delivery/one-step>` para seis camisas brancas navegando até o " +":menuselection:`app Vendas` e criando uma nova cotação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:84 msgid "" @@ -13086,6 +14366,9 @@ msgid "" " the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO " "(First In, First Out)` removal strategy." msgstr "" +"Após clicar em :guilabel:`Confirmar` no pedido de venda, um pedido de " +"entrega com os números de lote mais antigos para camisas é reservado, usando" +" a estratégia de remoção :abbr:`PEPS (Primeiro a entrar, primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:87 msgid "" @@ -13094,6 +14377,10 @@ msgid "" ":guilabel:`Operations` tab of the delivery order. Doing so opens the " ":guilabel:`Open: Stock move` pop-up window." msgstr "" +"Para visualizar as separações em detalhes, clique no ícone :guilabel:`⦙≣ " +"(lista)`, localizado na extremidade direita da linha de produtos da camisa " +"branca na aba :guilabel:`Operações` da ordem de entrega. Isso abre a janela " +"pop-up :guilabel:`Abrir: Movimentação de estoque`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:91 msgid "" @@ -13102,14 +14389,19 @@ msgid "" "picked from. Since the order demanded six shirts, all five shirts from " "`LOT1`, and one shirt from `LOT2`, are selected." msgstr "" +"Na janela pop-up :guilabel:`Abrir: Movimentação de estoque`, o campo " +":guilabel:`Separar em` exibe de onde são retiradas as quantidades para " +"atender à :guilabel:`demanda`. Como o pedido exigia seis camisas, todas as " +"cinco camisas do `LOTE1` e uma camisa do `LOTE2` são selecionadas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst-1 msgid "Two lots being reserved for a sales order with the FIFO strategy." msgstr "" +"Dois lotes sendo reservados para um pedido de vendas com a estratégia peps." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:3 msgid "Least packages removal" -msgstr "" +msgstr "Remoção em menos pacotes" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:5 msgid "" @@ -13117,12 +14409,17 @@ msgid "" "fewest number of packages, which is ideal for maintaining organized stock " "without needing to open multiple boxes." msgstr "" +"A estratégia de remoção *Menos pacotes* atende a um pedido abrindo o menor " +"número de pacotes, o que é ideal para manter o estoque organizado sem a " +"necessidade de abrir várias caixas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:10 msgid "" "`Odoo Tutorials: Least Packages " "<https://www.odoo.com/slides/slide/5477/share>`_" msgstr "" +"Tutoriais do Odoo: Menos pacotes " +"<https://www.odoo.com/slides/slide/5477/share>`_" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:12 msgid "" @@ -13130,6 +14427,9 @@ msgid "" "example, featuring a warehouse that stores packages of flour in bulk " "packages of `100 kg`." msgstr "" +"Para entender como a estratégia de remoção funciona, considere o exemplo a " +"seguir, que apresenta um armazém com pacotes de farinha em embalagens a " +"granel de `100 kg`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:15 msgid "" @@ -13137,18 +14437,25 @@ msgid "" "least packages removal strategy is used to pick from a single, opened " "package." msgstr "" +"Para minimizar a umidade e/ou evitar que as pragas entrem nas embalagens " +"abertas, a estratégia de remoção de menos pacotes é usada para retirar de " +"uma única embalagem aberta." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:21 msgid "" "A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some " "orders. There are other packages of `100 kg` in stock." msgstr "" +"Um pacote de 100 kg de farinha foi reduzido para 54 kg após o atendimento de" +" alguns pedidos. Há outros pacotes de `100 kg` em estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:24 msgid "" "When an order for `14 kg` of flour is placed, the package of `54 kg` is " "selected." msgstr "" +"Quando um pedido de `14 kg` de farinha é feito, o pacote de `54 kg` é " +"selecionado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:25 msgid "" @@ -13156,18 +14463,26 @@ msgid "" "kg` package is used to fulfill the order. While this temporarily results in " "two open packages, these open packages are prioritized in the next picking." msgstr "" +"Quando é feito um pedido de *mais* de 54 kg de farinha é feito, um pacote " +"fechado de 100 kg é usado para atender ao pedido. Embora isso resulte " +"temporariamente em dois pacotes abertos, esses pacotes abertos são " +"priorizados na próxima separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:32 msgid "" "Using the least package removal strategy, the fewest number of packages is " "used to fulfill an order." msgstr "" +"Com a estratégia de remoção de menos pacotes, o menor número de pacotes é " +"usado para atender a um pedido." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:35 msgid "" "The :ref:`Packages feature <inventory/warehouses_storage/pack-setup>` " "**must** be enabled to use this strategy." msgstr "" +"O recurso :ref:`Pacotes <inventory/warehouses_storage/pack-setup>` **deve** " +"estar ativado para usar essa estratégia." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:38 msgid "" @@ -13177,22 +14492,32 @@ msgid "" "remaining package containing `54 kg`. The product category's " ":guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." msgstr "" +"Considere o exemplo a seguir, que apresenta o produto `Farinha`. O campo " +":guilabel:`Unidades de medida` do produto, localizado no formulário do " +"produto, está definido como `kg`. O produto é armazenado em pacotes de `100 " +"kg`, com um pacote restante contendo `54 kg`. O campo :guilabel:`Forçar " +"estratégia de remoção` da categoria do produto está definido como " +":guilabel:`Menos pacotes`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:44 msgid "" ":ref:`Set removal strategy on product category " "<inventory/warehouses_storage/removal-config>`" msgstr "" +":ref:`Definir estratégia de remoção na categoria de produto " +"<inventory/warehouses_storage/removal-config>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:47 msgid "" "To check the product's on-hand stock, navigate to the product form, and " "click the :guilabel:`On Hand` smart button." msgstr "" +"Para verificar o estoque disponível do produto, navegue até o formulário do " +"produto e clique no botão inteligente :guilabel:`Em mãos`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:0 msgid "Show on-hand stock in each package." -msgstr "" +msgstr "Mostrar o estoque disponível em cada pacote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:54 msgid "" @@ -13201,12 +14526,18 @@ msgid "" " new quotation. After clicking :guilabel:`Confirm`, the delivery order is " "created." msgstr "" +"Crie uma :ref:`ordem de entrega <inventory/delivery/one-step>` para oitenta " +"quilos de farinha, acessando o :menuselection:`app Vendas` e criando uma " +"nova cotação. Depois de clicar em :guilabel:`Confirmar`, a ordem de entrega " +"é criada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:58 msgid "" "On the delivery order, the :guilabel:`Quantity` field displays the amount " "automatically picked, according to the removal strategy." msgstr "" +"Na ordem de entrega, o campo :guilabel:`Quantidade` exibe a quantidade " +"automaticamente retirada, de acordo com a estratégia de remoção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:61 msgid "" @@ -13215,6 +14546,11 @@ msgid "" "opens the :guilabel:`Open: Stock move` pop-up window, displaying how the " "reserved items were picked, according to the removal strategy." msgstr "" +"Para obter mais detalhes sobre de *onde* as unidades foram retiradas, " +"selecione o ícone :guilabel:`⦙≣ (lista)`, localizado na extremidade direita." +" Isso abre a janela pop-up :guilabel:`Abrir: Movimentação de estoque`, " +"exibindo como os itens reservados foram retirados, de acordo com a " +"estratégia de remoção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:65 msgid "" @@ -13224,20 +14560,28 @@ msgid "" "quantity in the opened package of `54 kg`, an unopened package of `100 kg` " "is selected." msgstr "" +"Na janela pop-up :guilabel:`Abrir: Movimentação de estoque`, o campo " +":guilabel:`Separar em` exibe onde as quantidades para atender à " +":guilabel:`demanda` são separadas. Como o pedido exigia oitenta quilos, o " +"que excede a quantidade no pacote aberto de 54 kg, um pacote fechado de 100 " +"kg é selecionado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst-1 msgid "Show which package was picked in the *Pick From* field." -msgstr "" +msgstr "Mostrar qual pacote foi escolhido no campo *Separar em*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:3 msgid "LIFO removal" -msgstr "" +msgstr "Remoção de UEPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:5 msgid "" "The *Last In, First Out* (LIFO) removal strategy picks the **newest** " "products on-hand, based on the date they entered a warehouse's stock." msgstr "" +"A estratégia de remoção *Último a entrar, primeiro a sair* (UEPS) escolhe os" +" produtos **mais novos** disponíveis, com base na data em que eles entraram " +"no estoque de um depósito." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:8 msgid "" @@ -13246,6 +14590,10 @@ msgid "" "has most recently entered the stock (the **last** lot/serial number that " "entered the warehouse's inventory)." msgstr "" +"Toda vez que um pedido é feito para produtos que usam a estratégia " +":abbr:`UEPS `, uma transferência é criada para o número de série/lote que " +"entrou mais recentemente no estoque (o **último** número de lote/série que " +"entrou no inventário do armazém)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:16 msgid "" @@ -13253,6 +14601,9 @@ msgid "" " banned, since it can potentially result in old, expired, or obsolete " "products being delivered to customers." msgstr "" +"Em muitos países, a estratégia de remoção :abbr:`UEPS` é proibida, pois pode" +" resultar em produtos antigos, vencidos ou obsoletos sendo entregues aos " +"clientes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:19 msgid "" @@ -13261,28 +14612,36 @@ msgid "" "form. The :guilabel:`Force Removal Strategy` for the cinder block's product " "category is set to :guilabel:`Last In, First Out (LIFO)`." msgstr "" +"Considere o exemplo a seguir, com o produto `Bloco de concreto`, que é " +"rastreado :guilabel:`Por lotes` na aba :guilabel:`Inventário` do formulário " +"do produto. A definição de :guilabel:`Forçar estratégia de remoção` para a " +"categoria de produto do bloco de concreto é definida como :guilabel:`Último " +"a entrar, primeiro a sair (UEPS)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:26 msgid ":ref:`Check arrival date <inventory/warehouses_storage/arrival_date>`" msgstr "" +":ref:`Verificar data de chegada <inventory/warehouses_storage/arrival_date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:28 msgid "" "The following table represents the cinder blocks in stock, and their various" " lot number details." msgstr "" +"A tabela a seguir representa os blocos de concreto em estoque e seus vários " +"detalhes de número de lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:43 msgid "June 1" -msgstr "" +msgstr "1º de junho" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:44 msgid "June 3" -msgstr "" +msgstr "3 de junho" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:45 msgid "June 6" -msgstr "" +msgstr "6 de junho" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:47 msgid "" @@ -13290,6 +14649,9 @@ msgid "" "<inventory/delivery/one-step>` for seven cinder blocks by navigating to the " ":menuselection:`Sales app` and creating a new quotation." msgstr "" +"Para ver a estratégia de remoção em ação, crie uma :ref:`ordem de entrega " +"<inventory/delivery/one-step>` para sete blocos de concreto navegando até o " +":menuselection:`app Vendas` e criando uma nova cotação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:51 msgid "" @@ -13297,6 +14659,9 @@ msgid "" "reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First " "Out)` removal strategy." msgstr "" +":guilabel:`Confirme` o pedido de vendas para criar uma ordem de entrega. Ao " +"fazer isso, os números de lote mais recentes são reservados usando a " +"estratégia de remoção :abbr:`UEPS (Último a entrar, primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:54 msgid "" @@ -13305,6 +14670,10 @@ msgid "" ":guilabel:`Operations` tab of the delivery order. Doing so opens the " ":guilabel:`Open: Stock move` pop-up window." msgstr "" +"Para visualizar as separações em detalhes, clique no ícone :guilabel:`⦙≣ " +"(lista)`, localizado na extremidade direita da linha de produtos de bloco de" +" concreto na aba :guilabel:`Operações` da ordem de entrega. Isso abre a " +"janela pop-up :guilabel:`Abrir: Movimentação de estoque`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:58 msgid "" @@ -13314,15 +14683,22 @@ msgid "" " blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First " "Out)` removal strategy." msgstr "" +"Na janela pop-up :guilabel:`Abrir: Movimentação de estoque`, o campo " +":guilabel:`Separar em` exibe de onde são retiradas as quantidades para " +"atender à :guilabel:`demanda`. Como o pedido exigia sete blocos de concreto," +" os blocos de concreto mais novos do `LOTE3` são selecionados, usando a " +"estratégia de remoção :abbr:`UEPS (Último a entrar, primeiro a sair)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst-1 msgid "" "The detailed operations shows which lots are being selected for the picking." msgstr "" +"As operações detalhadas mostram quais lotes estão sendo selecionados para a " +"separação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 msgid "Consignment: buy and sell stock without owning it" -msgstr "" +msgstr "Consignação: comprar e vender produtos sem possuí-los" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:5 msgid "" @@ -13332,6 +14708,11 @@ msgid "" "warehouse, without having to buy those items up-front. This is called " "*consignment*." msgstr "" +"Na maioria das vezes, os produtos armazenados no armazém de uma empresa são " +"comprados de fornecedores ou fabricados internamente. Entretanto, os " +"fornecedores às vezes permitem que as empresas armazenem e vendam produtos " +"no armazém a empresa, sem precisar comprar esses itens antecipadamente. Isso" +" é chamado de *consignação*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:10 msgid "" @@ -13341,10 +14722,15 @@ msgid "" "efforts. Consignees can even charge a fee for the convenience of storing " "products they don't actually own." msgstr "" +"A consignação é um método útil para que os fornecedores lancem novos " +"produtos e entreguem facilmente a seus clientes. Também é uma ótima maneira " +"de a empresa que armazena os produtos (o consignatário) receber algo em " +"troca por seus esforços. Os consignatários podem até cobrar uma taxa pela " +"conveniência de armazenar produtos que, na verdade, não possuem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:16 msgid "Enable the consignment setting" -msgstr "" +msgstr "Ativar a configuração de consignação" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:18 msgid "" @@ -13354,14 +14740,19 @@ msgid "" " check the box next to :guilabel:`Consignment`, and then click " ":guilabel:`Save` to finish." msgstr "" +"Para receber, armazenar e vender estoque em consignação, o recurso precisa " +"ser ativado nas configurações. Para fazer isso, vá para " +":menuselection:`Inventário --> Configuração --> Definições` e, na seção " +":guilabel:`Rastreabilidade`, marque a caixa ao lado de " +":guilabel:`Consignação` e clique em :guilabel:`Salvar` para concluir." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 msgid "Enabled Consignment setting in Inventory configuration." -msgstr "" +msgstr "Configuração de consignação ativada na configuração do inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:28 msgid "Receive (and store) consignment stock" -msgstr "" +msgstr "Receber (e armazenar) estoque em consignação" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:30 msgid "" @@ -13369,6 +14760,10 @@ msgid "" " a warehouse. From the main :menuselection:`Inventory` dashboard, click into" " the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." msgstr "" +"Com o recurso ativado no Odoo, o estoque em consignação agora pode ser " +"recebido em um armazém. No painel principal :menuselection:`Inventário`, " +"clique na seção :guilabel:`Recebimentos`. Em seguida, clique em " +":guilabel:`Criar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:35 msgid "" @@ -13377,12 +14772,20 @@ msgid "" "orders involved in receiving consignment stock. So, *every* receipt of " "consignment stock will start by creating manual receipts." msgstr "" +"O estoque em consignação não é de fato comprado do fornecedor; ele é " +"simplesmente recebido e armazenado. Por esse motivo, não há cotações ou " +"pedidos de compra envolvidos no recebimento do estoque em consignação. " +"Portanto, *todos* os recebimentos de estoque em consignação começarão com a " +"criação de recebimentos manuais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:39 msgid "" "Choose a vendor to enter in the :guilabel:`Receive From` field, and then " "choose the same vendor to enter in the :guilabel:`Assign Owner` field." msgstr "" +"Escolha um fornecedor para inserir no campo :guilabel:`Receber de` e, em " +"seguida, escolha o mesmo fornecedor no campo :guilabel:`Atribuir " +"proprietário`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:43 msgid "" @@ -13390,6 +14793,9 @@ msgid "" "vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields " "must match." msgstr "" +"Como os produtos recebidos do fornecedor serão de propriedade do mesmo " +"fornecedor, os campos :guilabel:`Receber de` e :guilabel:`Atribuir " +"proprietário` devem corresponder." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:46 msgid "" @@ -13400,14 +14806,22 @@ msgid "" "changed, as well. Once all the consignment stock has been received, " ":guilabel:`Validate` the receipt." msgstr "" +"Depois que os campos relacionados ao fornecedor estiverem definidos, insira " +"os produtos nas linhas :guilabel:`Produto` e defina as quantidades a serem " +"recebidas no armazém na coluna :guilabel:`Concluído`. Se o recurso " +":guilabel:`Unidades de medida` estiver ativado, a :abbr:`UM (unidade de " +"medida)` também poderá ser alterada. Quando todo o estoque em consignação " +"tiver sido recebido, :guilabel:`valide` o recebimento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 msgid "Matching vendor fields in consignment Receipt creation." msgstr "" +"Correspondência dos campos do fornecedor na criação do recebimento de " +"consignação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:56 msgid "Sell and deliver consignment stock" -msgstr "" +msgstr "Vender e entregar estoque em consignação" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:58 msgid "" @@ -13415,6 +14829,9 @@ msgid "" "the same as any other in-stock product that has the :guilabel:`Can Be Sold` " "option enabled on the product form." msgstr "" +"Depois que o estoque em consignação for recebido no armazém, ele poderá ser " +"vendido da mesma forma que qualquer outro produto em estoque que tenha a " +"opção :guilabel:`Pode ser vendido` ativada no formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:61 msgid "" @@ -13422,12 +14839,18 @@ msgid "" "from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, " "choose a customer to enter into the :guilabel:`Customer` field." msgstr "" +"Para criar um pedido de vendas, navegue até o aplicativo " +":menuselection:`Vendas` e, na visão geral :guilabel:`Cotações`, clique em " +":guilabel:`Criar`. Em seguida, escolha um cliente para inserir no campo " +":guilabel:`Cliente`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:66 msgid "" "The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` " "that supplied the consignment stock received (and stored) in the warehouse." msgstr "" +"O :guilabel:`cliente` *deve* ser diferente do :guilabel:`fornecedor` que " +"forneceu o estoque em consignação recebido (e armazenado) no armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:69 msgid "" @@ -13436,10 +14859,14 @@ msgid "" "product details on the form. Once the quotation is complete, click " ":guilabel:`Confirm`." msgstr "" +"Adicione o produto em consignação na coluna :guilabel:`Produto` nas linhas " +"do pedido, defina a :guilabel:`Quantidade` e preencha outros detalhes " +"pertinentes do produto no formulário. Quando a cotação estiver concluída, " +"clique em :guilabel:`Confirmar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 msgid "Sales order of consignment stock." -msgstr "" +msgstr "Pedido de vendas de estoque em consignação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:77 msgid "" @@ -13448,10 +14875,14 @@ msgid "" "on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate`" " to validate the delivery." msgstr "" +"Depois que a :abbr:`SDC (solicitação de cotação) ` for confirmada, ela se " +"tornará um pedido de venda. A partir daí, os produtos podem ser entregues " +"clicando no botão inteligente :guilabel:`Entrega` e selecionando " +":guilabel:`Validar` para validar a entrega." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:82 msgid "Traceability and reporting of consignment stock" -msgstr "" +msgstr "Rastreabilidade e relatório de estoque de consignação" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:84 msgid "" @@ -13459,12 +14890,17 @@ msgid "" "by the company storing it in their warehouse, consignment products will " "*still* appear in certain inventory reports." msgstr "" +"Embora o estoque em consignação seja de propriedade do fornecedor que o " +"forneceu, e não da empresa que o armazena, os produtos em consignação " +"*ainda* aparecerão em determinados relatórios de inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:87 msgid "" "To find inventory reports, go to :menuselection:`Inventory --> Reporting`, " "and choose a report to view." msgstr "" +"Para localizar relatórios de inventário, acesse :menuselection:`Inventário " +"--> Relatórios` e escolha um relatório para visualizar." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:91 msgid "" @@ -13472,10 +14908,13 @@ msgid "" "are *not* reflected in the :guilabel:`Stock Valuation` report, and have no " "impact on the consignee's inventory valuation." msgstr "" +"Como o consignatário não possui de fato estoque de consignação, esses " +"produtos *não* são refletidos no relatório de :guilabel:`Valoração de " +"inventário` e não têm impacto na valoração do inventário do consignatário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:96 msgid "Product moves report" -msgstr "" +msgstr "Relatório de movimentação de produtos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:98 msgid "" @@ -13488,6 +14927,15 @@ msgid "" "are available, as well. The consignment stock will originate from " ":guilabel:`Partner Location/Vendors`." msgstr "" +"Para visualizar todas as informações sobre as movimentações de estoque " +"disponíveis, navegue até o painel :guilabel:`Movimentações de produtos` " +"acessando :menuselection:`Inventário --> Relatórios --> Movimentações de " +"produtos`. Para produtos em consignação, as informações nesse relatório são " +"as mesmas de qualquer outro produto: o histórico de suas movimentações de " +"produtos pode ser revisado; os documentos :guilabel:`Quantidade concluída` e" +" :guilabel:`Referência` estão disponíveis, bem como seus :guilabel:`locais`." +" O estoque em consignação será originado de :guilabel:`Local de " +"parceiros/Fornecedores`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:106 msgid "" @@ -13496,20 +14944,26 @@ msgid "" "parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to " "finish." msgstr "" +"Para visualizar as movimentações de um produto em consignação por " +"propriedade, selecione o filtro :guilabel:`Agrupar por`, escolha o parâmetro" +" :guilabel:`Adicionar grupo personalizado` e, em seguida, selecione " +":guilabel:`Do proprietário` e :guilabel:`Aplicar` para concluir." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 msgid "Consignment stock moves history." -msgstr "" +msgstr "O históricode movimentações do estoque em consignação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:115 msgid "" "To see forecasted units of consignment stock, go to " ":menuselection:`Inventory --> Reporting --> Forecasted Inventory`." msgstr "" +"Para ver as unidades previstas de estoque em consignação, vá para " +":menuselection:`Inventário --> Relatórios --> Estoque previsto`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:119 msgid "Stock on hand report" -msgstr "" +msgstr "Relatório de estoque em mãos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:121 msgid "" @@ -13520,14 +14974,20 @@ msgid "" ":guilabel:`Owner` column will be populated with the owner of those products," " or the original vendor who supplied the products in the first place." msgstr "" +"Visualize o painel de controle :guilabel:`Estoque em mãos` navegando até " +":menuselection:`Inventário --> Relatórios --> Relatório de inventário`. " +"Nesse relatório, são exibidos os :guilabel:`Locais` de todo o estoque " +"disponível, além das quantidades por local. Para produtos consumíveis, a " +"coluna :guilabel:`Proprietário` será preenchida com o proprietário desses " +"produtos ou com o fornecedor original que forneceu os produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:3 msgid "Putaway rules" -msgstr "" +msgstr "Regras de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:6 msgid "What is a Putaway Rule?" -msgstr "" +msgstr "O que é uma regra de armazenamento?" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:8 msgid "" @@ -13536,6 +14996,11 @@ msgid "" " uses *Putaway Rules*. Putaway is the process of taking products from the " "received shipments and putting them into the appropriate location." msgstr "" +"Uma boa implementação de armazém garante que os produtos sejam movidos " +"automaticamente para o local de destino apropriado. Para facilitar esse " +"processo, o Odoo usa *Regras de armazenamento*. O armazenamento é o processo" +" de retirar produtos das remessas recebidas e colocá-los no local " +"apropriado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:13 msgid "" @@ -13544,6 +15009,10 @@ msgid "" "because of a potential chemical reaction. That's where putaway rules " "intervene, to avoid storing products wrongly." msgstr "" +"Se, por exemplo, um armazém contiver substâncias voláteis, é importante " +"garantir que determinados produtos não sejam armazenados próximos uns dos " +"outros devido a uma possível reação química. É aí que as regras de " +"armazenamento intervêm, para evitar o armazenamento incorreto de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:20 msgid "" @@ -13552,14 +15021,20 @@ msgid "" "so, the :guilabel:`Storage Locations` feature is also automatically " "activated." msgstr "" +"No aplicativo :guilabel:`Inventário`, vá para :menuselection:`Configuração " +"--> Definições` e ative o recurso :guilabel:`Rotas com várias etapas`. Ao " +"fazer isso, o recurso :guilabel:`Locais de armazenamento` também é ativado " +"automaticamente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 msgid "Activate Multi-Step Routes in Inventory configuration settings." msgstr "" +"Ativar as rotas com várias etapas nas definições de configuração de " +"Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:29 msgid "Setting up a putaway rule" -msgstr "" +msgstr "Configurando uma regra de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:31 msgid "" @@ -13568,44 +15043,50 @@ msgid "" "factors like frequency, size, product category, specific environment needs, " "and so on." msgstr "" +"Em alguns casos, como em uma loja de varejo que armazena frutas e legumes, " +"os produtos devem ser armazenados em locais diferentes, dependendo de vários" +" fatores, como frequência, tamanho, categoria do produto, necessidades " +"específicas do ambiente e assim por diante." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:35 msgid "" "In this example, suppose there is one warehouse location, **WH/Stock**, with" " the following sub-locations:" msgstr "" +"Neste exemplo, suponha que exista um local de armazém, **WH/Stock**, com os " +"seguintes sublocais:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:38 msgid "WH/Stock/Pallets" -msgstr "" +msgstr "WH/Stock/Pallets" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:40 msgid "WH/Stock/Pallets/PAL1" -msgstr "" +msgstr "WH/Stock/Pallets/PAL1" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:41 msgid "WH/Stock/Pallets/PAL2" -msgstr "" +msgstr "WH/Stock/Pallets/PAL2" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:42 msgid "WH/Stock/Pallets/PAL3" -msgstr "" +msgstr "WH/Stock/Pallets/PAL3" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:44 msgid "WH/Stock/Shelf 1" -msgstr "" +msgstr "WH/Stock/Shelf 1" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:46 msgid "WH/Stock/Shelf 2" -msgstr "" +msgstr "WH/Stock/Shelf 2" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:48 msgid "WH/Stock/Shelf 2/Small Refrigerator" -msgstr "" +msgstr "WH/Stock/Shelf 2/Small Refrigerator" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:50 msgid "WH/Stock/Shelf 3" -msgstr "" +msgstr "WH/Stock/Shelf 3" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:52 msgid "" @@ -13615,6 +15096,12 @@ msgid "" "rule that indicated the main location the product will enter before being " "redirected to the right storage location." msgstr "" +"Gerencie esses locais com regras de armazenamento. Para criar uma regra de " +"armazenamento, abra o aplicativo :guilabel:`Inventário` e vá para " +":menuselection:`Configuração --> Regras de armazenamento`. Em seguida, " +"clique em :guilabel:`Criar` e configure uma regra de armazenamento que " +"indique o local principal em que o produto entrará antes de ser " +"redirecionado para o local de armazenamento correto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:58 msgid "" @@ -13622,42 +15109,54 @@ msgid "" "package type (the :guilabel:`Packages` setting must be enabled for that). " "Putaway rules are read sequentially until a match is found." msgstr "" +"As regras de armazenamento podem ser definidas por produto/categoria de " +"produto e/ou tipo de pacote (a configuração :guilabel:`Pacotes` deve estar " +"ativada para isso). As regras de armazenamento são lidas sequencialmente até" +" que uma correspondência seja encontrada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:62 msgid "Take the following example:" -msgstr "" +msgstr "Veja o exemplo a seguir:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:64 msgid "" "If water (category All/drinks) is received, whatever the package, it will be" " redirected to WH/Stock/Shelf 2/Small Refrigerator." msgstr "" +"Se for recebida água (categoria Tudo/bebidas), qualquer que seja a " +"embalagem, ela será redirecionada para WH/Stock/Shelf 2/Small Refrigerator." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:66 msgid "" "If orange juice cans, packaged in boxes, are received, they will be " "redirected to WH/Stock/Shelf 2." msgstr "" +"Se forem recebidas latas de suco de laranja, embaladas em caixas, elas serão" +" redirecionadas para WH/Stock/Shelf 2." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:68 msgid "" "If water or apple juice bottles, packaged in boxes, are received, they will " "be redirected to WH/Stock/Shelf 3." msgstr "" +"Se forem recebidas garrafas de água ou de suco de maçã, embaladas em caixas," +" elas serão redirecionadas para WH/Stock/Shelf 3." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:70 msgid "" "If a pallet of lemonade cans are receieved, it will be redirected to " "WH/Stock/Pallets/PAL1." msgstr "" +"Se um palete de latas de limonada for recebido, ele será redirecionado para " +"WH/Stock/Pallets/PAL1." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 msgid "Some examples of putaway rules." -msgstr "" +msgstr "Alguns exemplos de regras de armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:77 msgid "Using Storage Categories" -msgstr "" +msgstr "Uso de categorias de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:79 msgid "" @@ -13665,6 +15164,10 @@ msgid "" "allow the user to define the quantity of products that can be stored in the " "location and how the location will be selected with putaway rules." msgstr "" +"Uma *Categoria de armazenamento* é um atributo extra de local. As categorias" +" de armazenamento permitem que o usuário defina a quantidade de produtos que" +" podem ser armazenados no local e como o local será selecionado com regras " +"de armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:86 msgid "" @@ -13673,10 +15176,14 @@ msgid "" "so, the :guilabel:`Storage Locations` feature is also automatically " "activated." msgstr "" +"No aplicativo :guilabel:`Inventário`, vá para :menuselection:`Configuração " +"--> Definições` e ative o recurso :guilabel:`Categorias de armazenamento`. " +"Ao fazer isso, o recurso :guilabel:`Locais de armazenamento` também é " +"ativado automaticamente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:91 msgid "Create a Storage Category" -msgstr "" +msgstr "Criar uma categoria de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:93 msgid "" @@ -13686,16 +15193,26 @@ msgid "" ":menuselection:`Configuration --> Storage Categories` to create a new " "storage category." msgstr "" +"Para criar uma categoria de armazenamento, vá para " +":menuselection:`Inventário --> Configuração --> Categorias de armazenamento`" +" e clique em :guilabel:`Criar`. Em seguida, clique em :guilabel:`Salvar` e " +"clique em :guilabel:`Categorias de armazenamento` ou vá para " +":menuselection:`Configuração --> Categorias de armazenamento` para criar uma" +" nova." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 msgid "" "Create Storage Categories inside Odoo Inventory configuration settings." msgstr "" +"Crie categorias de armazenamento dentro das definições de configuração do " +"Odoo Invent.ário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:102 msgid "" "First, click :guilabel:`Create` and type a name for the storage category." msgstr "" +"Primeiro, clique em :guilabel:`Criar` e digite um nome para a categoria de " +"armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 msgid "" @@ -13703,74 +15220,98 @@ msgid "" "package type. The :guilabel:`Allow New Product` field defines when the " "location is considered available to store a product:" msgstr "" +"Em seguida, há opções para limitar a capacidade por peso, por produto ou por" +" tipo de embalagem. O campo :guilabel:`Permitir novo produto` define quando " +"o local é considerado disponível para armazenar um produto:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 msgid "" ":guilabel:`If location is empty`: a product can be added there only if the " "location is empty." msgstr "" +":guilabel:`Se o local está vazio`: um produto só pode ser adicionado ali se " +"o local estiver vazio." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:109 msgid "" ":guilabel:`If products are the same`: a product can be added there only if " "the same product is already there." msgstr "" +":guilabel:`Se os produtos são os mesmos`: um produto só pode ser adicionado " +"ali se o mesmo produto já estiver ali." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:111 msgid "" ":guilabel:`Allow mixed products`: several different products can be stored " "in this location at the same time." msgstr "" +":guilabel:`Permitir produtos mistos`: vários produtos diferentes podem ser " +"armazenados nesse local ao mesmo tempo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:114 msgid "" "Once the storage category settings are saved, the storage category can be " "linked to a location." msgstr "" +"Depois que as configurações da categoria de armazenamento são salvas, a " +"categoria de armazenamento pode ser vinculada a um local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 msgid "" "When a Storage Category is created, it can be linked to a warehouse " "location." msgstr "" +"Quando uma categoria de depósito é criada, ela pode ser vinculada a um local" +" de armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:121 msgid "Storage categories in putaway rules" -msgstr "" +msgstr "Categorias de armazenamento em regras de armazenamento" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:123 msgid "" "To continue the example from above, apply the \"High Frequency Pallets\" on " "the PAL1 and PAL2 locations and rework the putaway rules as follows:" msgstr "" +"Para continuar o exemplo acima, aplique os \"Paletes de alta frequência\" " +"nos locais PAL1 e PAL2 e refaça as regras de armazenamento da seguinte " +"forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:126 msgid "Assume one pallet of lemonade cans is received:" -msgstr "" +msgstr "Suponha que um palete de latas de limonada seja recebido:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 msgid "" "If PAL1 and PAL2 are empty, the pallet will be redirected to " "WH/Stock/Pallets/PAL1." msgstr "" +"Se PAL1 e PAL2 estiverem vazios, o palete será redirecionado para " +"WH/Stock/Pallets/PAL1." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 msgid "" "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." msgstr "" +"Se o PAL1 estiver cheio, o palete será redirecionado para " +"WH/Stock/Pallets/PAL2." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:130 msgid "" "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." msgstr "" +"Se PAL1 e 2 estiverem cheios, o palete será redirecionado para " +"WH/Stock/Pallets." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 msgid "Storage Categories used in a variety of putaway rules." msgstr "" +"Categorias de armazenamento usadas em uma variedade de regras de " +"armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:3 msgid "Removal strategies" -msgstr "" +msgstr "Estratégias de remoção" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:5 msgid "" @@ -13779,6 +15320,10 @@ msgid "" "perishable products, prioritizing the picking of goods with the nearest " "expiration date helps minimize food spoilage." msgstr "" +"Para empresas com armazéns, as *estratégias de remoção* determinam **quais**" +" produtos são retirados e **quando**. Por exemplo, para produtos perecíveis," +" priorizar a retirada de mercadorias com a data de validade mais próxima " +"ajuda a minimizar a deterioração dos alimentos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:9 msgid "" @@ -13787,26 +15332,31 @@ msgid "" "picking order. Leverage these removal strategies to have Odoo automatically " "select how products are selected for orders:" msgstr "" +"As colunas a seguir na tabela abaixo listam as estratégias de remoção " +"disponíveis no Odoo e detalham como as separações são determinados " +"juntamente com a ordem de separação. Aproveite essas estratégias de remoção " +"para que o Odoo selecione automaticamente como os produtos são selecionados " +"para os pedidos:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:18 msgid ":doc:`FIFO <fifo>`" -msgstr "" +msgstr ":doc:`PEPS <fifo>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:19 msgid ":doc:`LIFO <lifo>`" -msgstr "" +msgstr ":doc:`UEPS <lifo>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:20 msgid ":doc:`FEFO <fefo>`" -msgstr "" +msgstr ":doc:`PVPS <fefo>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 msgid ":doc:`Closest Location <closest_location>`" -msgstr "" +msgstr ":doc:`Local mais próximo <closest_location>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:22 msgid ":doc:`Least Packages <least_packages>`" -msgstr "" +msgstr ":doc:`Menos pacotes <least_packages>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:23 msgid "Based on" @@ -13815,63 +15365,71 @@ msgstr "Baseado em" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:24 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:25 msgid ":ref:`Incoming date <inventory/warehouses_storage/arrival_date>`" -msgstr "" +msgstr ":ref:`Data de chegada <inventory/warehouses_storage/arrival_date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:26 msgid ":ref:`Removal date <inventory/warehouses_storage/removal-date>`" -msgstr "" +msgstr ":ref:`Data de remoção <inventory/warehouses_storage/removal-date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:27 msgid ":ref:`Location sequence <inventory/warehouses_storage/sequence>`" -msgstr "" +msgstr ":ref:`Sequência de locais <inventory/warehouses_storage/sequence>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:28 msgid ":ref:`Package quantity <inventory/warehouses_storage/pkg-qty>`" -msgstr "" +msgstr ":ref:`Quantidade do pacote <inventory/warehouses_storage/pkg-qty>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:29 msgid "Selection order" -msgstr "" +msgstr "Ordem de seleção" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:30 msgid "First in" -msgstr "" +msgstr "Primeiro a entrar" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:31 msgid "Last in" -msgstr "" +msgstr "Último a entrar" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:32 msgid ":ref:`First to expire <inventory/warehouses_storage/exp-date>`" -msgstr "" +msgstr ":ref:`Primeiro a vencer <inventory/warehouses_storage/exp-date>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 msgid "" ":ref:`Alphanumeric name of location <inventory/warehouses_storage/location-" "name>`" msgstr "" +":ref:`Nome alfanumérico do local <inventory/warehouses_storage/location-" +"name>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:34 msgid "Quantity closest to fulfilling demand" -msgstr "" +msgstr "Quantidade mais próxima de atender à demanda" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:36 msgid "" "For comprehensive examples for how to use each removal strategy, refer to " "each individual documentation page." msgstr "" +"Para obter exemplos abrangentes de como usar cada estratégia de remoção, " +"consulte as páginas individuais de documentação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:44 msgid "" "Removal strategies are set on either the product category or storage " "location." msgstr "" +"As estratégias de remoção são definidas na categoria do produto ou no local " +"de armazenamento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 msgid "" "Change the Force Removal Strategy for either the Product Categories or " "Locations." msgstr "" +"Alterar a estratégia de remoção forçada nas categorias de produtos ou " +"locais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:50 msgid "" @@ -13880,6 +15438,10 @@ msgid "" "the desired location. On the location form, choose a removal strategy from " "the :guilabel:`Removal Strategy` field's drop-down menu options." msgstr "" +"Configure as estratégias de remoção no local acessando " +":menuselection:`Inventário --> Configuração --> Locais` e selecionando o " +"local desejado. No formulário do local, escolha uma estratégia de remoção " +"nas opções do menu suspenso do campo :guilabel:`Estratégia de remoção`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:55 msgid "" @@ -13887,12 +15449,18 @@ msgid "" "and :guilabel:`Multi-Step Routes` settings **must** be enabled in " ":menuselection:`Inventory --> Configuration --> Settings`." msgstr "" +"Para definir uma estratégia de remoção em um local, as configurações " +":guilabel:`Locais de armazenamento` e :guilabel:`Rotas com várias etapas` " +"**devem** estar ativadas em :menuselection:`Inventário --> Configuração --> " +"Definições`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 msgid "" "These features are **only** necessary when setting the removal strategy on a" " location." msgstr "" +"Esses recursos são **somente** necessários ao definir a estratégia de " +"remoção em um local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:61 msgid "" @@ -13901,6 +15469,11 @@ msgid "" "selecting the intended product category. Next, choose a removal strategy " "from the :guilabel:`Force Removal Strategy` drop-down menu options." msgstr "" +"Configure estratégias de remoção em categorias de produtos acessando " +":menuselection:`Inventário --> Configuração --> Categorias de produtos` e " +"selecionando a categoria de produto desejada. Em seguida, escolha uma " +"estratégia de remoção nas opções do menu suspenso :guilabel:`Forçar " +"estratégia de remoção`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:66 msgid "" @@ -13909,11 +15482,15 @@ msgid "" "Removal Strategy` field set on a :guilabel:`Product Category` form is " "applied as top priority." msgstr "" +"Quando há diferentes estratégias de remoção aplicadas ao local e à categoria" +" de um produto, o valor definido no campo :guilabel:`Forçar estratégia de " +"remoção` definido em um formulário :guilabel:`Categoria de produto` é " +"aplicado como prioridade máxima." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:71 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:91 msgid "Required features" -msgstr "" +msgstr "Recursos necessários" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:73 msgid "" @@ -13923,6 +15500,11 @@ msgid "" "menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal " "Strategy` field." msgstr "" +"Embora algumas estratégias de remoção estejam disponíveis por padrão, alguns" +" recursos adicionais **devem** ser ativados em :menuselection:`Inventário " +"--> Configuração --> Definições` para que a opção de estratégia de remoção " +"apareça no menu suspenso do campo :guilabel:`Forçar estratégia de remoção` " +"ou :guilabel:`Estratégia de remoção`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:78 msgid "" @@ -13930,6 +15512,9 @@ msgid "" "refer to the dedicated sections for the removal strategy for more details on" " requirements and usage." msgstr "" +"Consulte a tabela abaixo para obter um resumo dos recursos necessários. Caso" +" contrário, consulte as seções dedicadas à estratégia de remoção para obter " +"mais detalhes sobre os requisitos e o uso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:86 msgid "FIFO" @@ -13937,11 +15522,11 @@ msgstr "PEPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 msgid "LIFO" -msgstr "" +msgstr "UEPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:88 msgid "FEFO" -msgstr "" +msgstr "PEPS" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:89 msgid "Closest Location" @@ -13958,11 +15543,11 @@ msgstr "Números de lote e série" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:94 msgid "Lots & Serial Numbers, Expiration Date" -msgstr "" +msgstr "Números de série e lotes, Data de expiração" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:95 msgid "Storage Locations, Multi-Step Routes" -msgstr "" +msgstr "Locais de armazenamento, Rotas com várias etapas" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:156 @@ -13972,7 +15557,7 @@ msgstr "Embalagens" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:101 msgid "Lots and serial numbers" -msgstr "" +msgstr "Números de série e lotes" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:103 msgid "" @@ -13982,10 +15567,15 @@ msgid "" " the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots " "& Serial Numbers` to enable the feature." msgstr "" +"Os números de série e lotes diferenciam produtos idênticos e rastreiam " +"informações como datas de chegada ou de expiração. Para ativar esse recurso," +" navegue até :menuselection:`Inventário --> Configuração --> Definições`. " +"Sob o título :guilabel:`Rastreabilidade`, marque a caixa de seleção ao lado " +"de :guilabel:`Números de série e lotes` para ativar o recurso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 msgid "Enable lots and serial numbers." -msgstr "" +msgstr "Habilitar números de série e lotes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 msgid "" @@ -13996,6 +15586,12 @@ msgid "" ":guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial " "Number` or :guilabel:`By Lots` options." msgstr "" +"Em seguida, certifique-se de que o produto em questão seja rastreado por " +"números de série ou lote, navegando até o formulário do produto por meio de " +":guilabel:`Inventário --> Produtos --> Produtos` e selecionando o produto " +"desejado. No formulário do produto, vá para a aba :guilabel:`Inventário` e, " +"no campo :guilabel:`Rastreamento`, selecione as opções :guilabel:`Por número" +" de série exclusivo` ou :guilabel:`Por lotes`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 msgid "" @@ -14003,10 +15599,14 @@ msgid "" "an :doc:`inventory adjustment <../inventory_management/count_products>` or " "during :ref:`product reception <inventory/product_management/receipt-lots>`." msgstr "" +"Depois de ativar os recursos, atribua números de série ou lote aos produtos " +"usando um :doc:`ajuste de inventário " +"<../inventory_management/count_products>` ou durante o :ref:`recebimento de " +"produtos <inventory/product_management/receipt-lots>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 msgid "Locations and routes" -msgstr "" +msgstr "Locais e rotas" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:125 msgid "" @@ -14015,6 +15615,11 @@ msgid "" "features are specifically required for the closest location removal strategy" " since it is only applied at the location level." msgstr "" +"**Locais de armazenamento** e **rotas com várias etapas** são recursos " +"necessários para definir **todos** os tipos de estratégias de remoção em um " +"local. No entanto, esses recursos são especificamente necessários para a " +"estratégia de remoção do local mais próximo, pois ela só é aplicada no nível" +" do local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 msgid "" @@ -14023,10 +15628,14 @@ msgid "" " the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` " "features." msgstr "" +"Para ativar esses recursos, navegue até :menuselection:`Inventário --> " +"Configuração --> Definições`. Sob o título :guilabel:`Armazém`, ative os " +"recursos :guilabel:`Locais de armazenamento` e :guilabel:`Rotas com várias " +"etapas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 msgid "Enable the locations and route features." -msgstr "" +msgstr "Ativar os recursos de localização e rota." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 msgid "" @@ -14034,6 +15643,10 @@ msgid "" "before dates, removal dates, and alert dates on a lot or serial number by " "navigating to :menuselection:`Inventory --> Configuration --> Settings`." msgstr "" +"Ative o recurso **data de vencimento** para rastrear datas de vencimento, " +"datas de validade, datas de remoção e datas de alerta em um lote ou número " +"de série, navegando até :menuselection:`Inventário --> Configuração --> " +"Definições`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 msgid "" @@ -14041,42 +15654,53 @@ msgid "" "Serial Numbers` feature is selected, and then select the check box for " ":guilabel:`Expiration Dates` to enable the feature." msgstr "" +"No cabeçalho :guilabel:`Rastreabilidade`, verifique se o recurso " +":guilabel:`Números de série e lotes` está selecionado e, em seguida, marque " +"a caixa de seleção :guilabel:`Datas de expiração` para ativar o recurso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 msgid "Enable expiration dates feature for FEFO." -msgstr "" +msgstr "Ativar o recurso de datas de expiração para PVPS." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:158 msgid "" "The *packages* feature is used to group products together and is required " "for the least packages removal strategy." msgstr "" +"O recurso *Pacotes* é usado para agrupar produtos e é necessário para a " +"estratégia de remoção de menos pacotes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:161 msgid "" "Navigate to :menuselection:`Inventory --> Configuration --> Settings` and " "select the check box for the :guilabel:`Packages` feature." msgstr "" +"Navegue até :menuselection:`Inventário --> Configuração --> Definições` e " +"marque a caixa de seleção do recurso :guilabel:`Pacotes`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 msgid "Enable the packages feature." -msgstr "" +msgstr "Habilitar o recurso de pacotes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:170 msgid "" ":doc:`2-step delivery " "<../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" msgstr "" +":doc:`Entrega em duas etapas " +"<.../.../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:171 msgid "" ":doc:`3-step delivery " "<../../shipping_receiving/daily_operations/delivery_three_steps>`" msgstr "" +":doc:`Entrega em três etapas " +"<.../.../shipping_receiving/daily_operations/delivery_three_steps>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 msgid "Sell stock from multiple warehouses using virtual locations" -msgstr "" +msgstr "Venda de estoque de vários armazéns usando locais virtuais" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:5 msgid "" @@ -14084,6 +15708,9 @@ msgid "" "smaller companies, bigger companies might need to keep stock in, or sell " "from, multiple warehouses in multiple locations." msgstr "" +"Embora manter o estoque e vender o inventário de um único armazém possa " +"funcionar para empresas menores, as empresas maiores podem precisar manter o" +" estoque ou vender de vários armazéns em vários locais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:9 msgid "" @@ -14092,6 +15719,10 @@ msgid "" " warehouses to satisfy sales demands can be done by using *virtual " "locations*." msgstr "" +"No Odoo, às vezes os produtos incluídos em um único pedido de vendas podem " +"ter estoque em dois (ou mais) armazéns. No Odoo, a extração de produtos de " +"vários armazém para atender às demandas de vendas pode ser feita usando " +"*locais virtuais*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:14 msgid "" @@ -14100,6 +15731,10 @@ msgid "" " Routes` features will need to be enabled in the :menuselection:`Settings` " "app." msgstr "" +"Para criar locais virtuais em armazéns e prosseguir para as etapas a seguir," +" os recursos :guilabel:`Locais de armazenamento` e :guilabel:`Rotas com " +"várias etapas` precisarão ser ativados no aplicativo " +":menuselection:`Definições`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:18 msgid "" @@ -14108,10 +15743,15 @@ msgid "" "next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. " "Then, :guilabel:`Save` the changes to finish." msgstr "" +"Para fazer isso, vá para :menuselection:`Inventário --> Configuração --> " +"Definições`, role para baixo até a seção :guilabel:`Armazém` e clique nas " +"caixas de seleção ao lado de :guilabel:`Locais de armazenamento` e " +":guilabel:`Rotas com várias etapas`. Em seguida, :guilabel:`salve` as " +"alterações para concluir." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:23 msgid "Create and configure a virtual parent location" -msgstr "" +msgstr "Criar e configurar um local primário virtual" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:25 msgid "" @@ -14119,6 +15759,9 @@ msgid "" " created. This new warehouse will act as a *virtual* warehouse, and will be " "the *parent* location of other physical warehouses." msgstr "" +"Antes de criar qualquer local de estoque virtual, será necessário criar um " +"novo armazém. Esse novo armazém atuará como um armazém *virtual* e será o " +"local *primário* de outros armazéns físicos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:31 msgid "" @@ -14128,6 +15771,11 @@ msgid "" "on-hand. In this case, stock from these two (or more) warehouses could be " "used to fulfill a single sales order." msgstr "" +"Os armazéns virtuais são ótimos para empresas com vários armazéns físicos. " +"Isso ocorre porque pode ocorrer uma situação em que um armazém fique sem " +"estoque de um determinado produto, mas outro ainda tenha estoque disponível." +" Nesse caso, o estoque desses dois (ou mais) armazém poderia ser usado para " +"atender a um único pedido de vendas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:36 msgid "" @@ -14135,11 +15783,14 @@ msgid "" "stored in a company's physical warehouses, and is used (for traceability " "purposes) to create a hierarchy of locations in Odoo." msgstr "" +"O armazém \"virtual\" atua como um agregador único de todo o estoque " +"armazenado nos armazéns físicos de uma empresa e é usado (para fins de " +"rastreabilidade) para criar uma hierarquia de locais no Odoo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:41 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:58 msgid "Create a new warehouse" -msgstr "" +msgstr "Criar um novo armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:43 msgid "" @@ -14149,6 +15800,11 @@ msgid "" "warehouse details can be changed under the :guilabel:`Warehouse " "Configuration` tab." msgstr "" +"Para criar um novo armazém, vá para :menuselection:`Inventário --> " +"Configuração --> Armazéns` e clique em :guilabel:`Criar`. Ali, o " +":guilabel:`nome` e :guilabel:`nome abreviado` do armazém podem ser " +"alterados, e outros detalhes do armazém podem ser alterados na aba " +":guilabel:`Configuração do armazém`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:48 msgid "" @@ -14160,30 +15816,44 @@ msgid "" "depend on the warehouse's procurement process, and might differ for " "individual products or product categories." msgstr "" +"Sob o título :guilabel:`Remessas`, defina o número de etapas usadas para " +"processar :guilabel:`remessas recebidas` e :guilabel:`remessas enviadas` " +"selecionando entre os botões :guilabel:`1 etapa`, :guilabel:`2 etapas` e " +":guilabel:`3 etapas`. A opção desejada para :guilabel:`remessas recebidas` e" +" :guilabel:`remessas enviadas` dependerá do processo de aquisição do armazém" +" e poderá ser diferente para produtos individuais ou categorias de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:55 msgid "" ":doc:`How to choose the right flow to handle receipts and deliveries? " "</applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries>`" msgstr "" +":doc:`Como escolher o fluxo certo para recebimentos e entregas? " +"</applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:58 msgid "" "Under the :guilabel:`Resupply` heading, configure the method(s) for how the " "warehouse resupplies its inventory:" msgstr "" +"Sob o título :guilabel:`Repor`, configure os métodos como o armazém " +"reabastece seu inventário:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:61 msgid "" ":guilabel:`Resupply Subcontractors`: resupply subcontractors with components" " from this warehouse." msgstr "" +":guilabel:`Reposição de subcontratação`: repõe as subcontratações com " +"componentes desse armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:62 msgid "" ":guilabel:`Manufacture to Resupply`: when products are manufactured, they " "can be manufactured in this warehouse." msgstr "" +":guilabel:`Fabricar para repor`: os produtos fabricados podem ser feitos " +"nesse armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:64 msgid "" @@ -14192,18 +15862,26 @@ msgid "" "first and then produce, unload the components from the stock to input " "location first, and then transfer it to the production location." msgstr "" +":guilabel:`Fabricar`: para produzir imediatamente, mova os componentes " +"diretamente para o local de produção e inicie o processo de fabricação; para" +" separar primeiro e depois produzir, descarregue os componentes do estoque " +"no local de entrada primeiro e depois transfira-os para o local de produção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:68 msgid "" ":guilabel:`Buy to Resupply`: when products are bought, they can be delivered" " to this warehouse." msgstr "" +":guilabel:`Comprar para repor`: quando os produtos são comprados, eles podem" +" ser entregues a esse depósito." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:69 msgid "" ":guilabel:`Resupply From`: automatically create routes to resupply this " "warehouse from another chosen warehouse" msgstr "" +":guilabel:`Repor de`: cria automaticamente rotas para reabastecer esse " +"armazém a partir de outro armazém escolhido" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:73 msgid "" @@ -14211,10 +15889,14 @@ msgid "" "form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse" " is configured, virtual *Locations* can be created." msgstr "" +"*Rotas* podem ser definidas e configuradas diretamente no formulário do " +":guilabel:`armazém`, clicando no botão inteligente :guilabel:`Rotas`. Depois" +" que o armazém estiver configurado, os *Locais* virtuais poderão ser " +"criados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 msgid "The edit screen for creating a new warehouse." -msgstr "" +msgstr "A tela de edição para criar um novo armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:81 msgid "" @@ -14222,34 +15904,37 @@ msgid "" "*child* location warehouses, there need to be two warehouses configured with" " physical stock locations." msgstr "" +"Para aplicar esse armazém virtual como o local *primário* de dois armazéns " +"de local *secundário*, é necessário que haja dois armazéns configurados com " +"locais de estoque físicos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid "**Parent Warehouse**" -msgstr "" +msgstr "**Armazém primário**" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" -msgstr "" +msgstr ":guilabel:`Armazém`: `Armazém virtual`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Location`: `VWH`" -msgstr "" +msgstr ":guilabel:`Local`: `VWH`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid "**Child Warehouses**" -msgstr "" +msgstr "**Armazéns secundários**" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" -msgstr "" +msgstr ":guilabel:`Armazéns`: `Armazém A` e `Armazém B`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" -msgstr "" +msgstr ":guilabel:`Locais`: `WHA/Stock` e `WHB/Stock`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:95 msgid "Create a virtual parent location" -msgstr "" +msgstr "Criar um local virtual primário" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:98 msgid "" @@ -14257,6 +15942,9 @@ msgid "" "there need to be at least **two** warehouses acting as *child locations* of " "the *virtual parent location* warehouse." msgstr "" +"Para obter estoque de vários armazéns para atender a um pedido de vendas, é " +"necessário que haja pelo menos **dois** armazéns atuando como *locais " +"secundários* do armazém *local virtual primário*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:101 msgid "" @@ -14266,6 +15954,11 @@ msgid "" " created. Click into the *Stock* :guilabel:`Location` for the virtual " "warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." msgstr "" +"Para criar e editar *locais*, vá para :menuselection:`Inventário --> " +"Configuração --> Locais`. Todos os :guilabel:`locais` estão listados ali, " +"incluindo o :guilabel:`local` de *estoque* do armazém virtual que foi " +"criado. Clique no :guilabel:`local` de estoque do armazém virtual que foi " +"criado anteriormente (:dfn:`Nome do armazém/Stock`)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:106 msgid "" @@ -14273,6 +15966,9 @@ msgid "" ":guilabel:`Location Type` from :guilabel:`Internal Location` to " ":guilabel:`View`. :guilabel:`Save` the changes." msgstr "" +"Em seguida, na seção :guilabel:`Informações adicionais`, altere o " +":guilabel:`tipo de local` de :guilabel:`Local interno` para " +":guilabel:`Visualização`. :guilabel:`Salve` as alterações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:109 msgid "" @@ -14280,20 +15976,25 @@ msgid "" "used to create a hierarchical structure for a warehouse and aggregate its " "*child locations*." msgstr "" +"Isso identifica esse :guilabel:`local` como um *local virtual*, que é usado " +"para criar uma estrutura hierárquica para um armazém e agregar seus *locais " +"secundários*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:113 msgid "" "Products can *not* be stored in a :guilabel:`View` :guilabel:`Location " "Type`." msgstr "" +"Os produtos *não* podem ser armazenados em uma :guilabel:`tipo de local` de " +":guilabel:`Visualização`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 msgid "Warehouse location types in location creation screen." -msgstr "" +msgstr "Tipos de local de armazém na tela de criação de local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:120 msgid "Configure physical warehouse locations" -msgstr "" +msgstr "Configurar locais de armazéns físicos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:122 msgid "" @@ -14302,6 +16003,10 @@ msgid "" "first physical warehouse :guilabel:`Location` that was previously created to" " be a *child location*, and click :guilabel:`Edit`." msgstr "" +"Volte para a visão geral de :guilabel:`Locais` (pela trilha de navegação) e " +"remova todos os filtros na :guilabel:`barra de pesquisa`. Em seguida, clique" +" no primeiro :guilabel:`local` de armazém físico que foi criado " +"anteriormente para ser um *local secundário* e clique em :guilabel:`Editar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:126 msgid "" @@ -14310,6 +16015,11 @@ msgid "" ":guilabel:`Locations` overview, and repeat this step for the second physical" " warehouse stock location. Be sure to :guilabel:`Save` changes again." msgstr "" +"Em :guilabel:`Local primário`, selecione o armazém virtual no menu suspenso " +"e :guilabel:`salve` as alterações. Em seguida, navegue de volta para a visão" +" geral de :guilabel:`Locais` e repita essa etapa para o segundo local de " +"estoque do armazém físico. Não se esqueça de :guilabel:`salvar` as " +"alterações novamente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:130 msgid "" @@ -14319,10 +16029,15 @@ msgid "" "(provided they are both tied to the same virtual warehouse *parent " "location*)." msgstr "" +"Ambos os locais agora são *locais secundários* do *local primário* do " +"armazém virtual. Isso permite que o estoque seja retirado de vários locais " +"para atender a um único pedido de venda, se não houver estoque suficiente em" +" um único local (desde que ambos estejam vinculados ao mesmo *local " +"primário* de armazém virtual)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:136 msgid "Example flow: Sell a product from a virtual warehouse" -msgstr "" +msgstr "Exemplo de fluxo: Venda de um produto de um armazém virtual" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:139 msgid "" @@ -14331,6 +16046,10 @@ msgid "" "warehouses configured - with at least **one** product with quantity on-hand " "in each warehouse, respectively." msgstr "" +"Para vender produtos de vários armazéns usando um local *principal* virtual " +"nesse fluxo, deve haver pelo menos **dois** produtos e pelo menos **dois** " +"armazéns configurados - com pelo menos **um** produto com quantidade " +"disponível em cada armazém, respectivamente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:143 msgid "" @@ -14340,6 +16059,11 @@ msgid "" "quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a " "product` to add the two products stored in the two warehouses." msgstr "" +"Para criar uma nova solicitação de cotação (SDC), navegue até o aplicativo " +":menuselection:`Vendas` e clique em :guilabel:`Criar` na visão geral " +":guilabel:`Cotações`. Preencha as informações sobre a nova cotação " +"adicionando um :guilabel:`cliente` e clique em :guilabel:`Adicionar um " +"produto` para adicionar os dois produtos armazenados nos dois armazéns." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:148 msgid "" @@ -14349,6 +16073,11 @@ msgid "" "warehouse has been changed, click :guilabel:`Confirm` to convert the " "quotation into a sales order." msgstr "" +"Em seguida, clique na aba :guilabel:`Outras informações` no formulário de " +"pedido de venda. Na seção :guilabel:`Entrega`, altere o valor do campo " +":guilabel:`Armazém` listado para o armazém virtual que foi criado " +"anteriormente. Depois que o armazém tiver sido alterado, clique em " +":guilabel:`Confirmar` para converter a cotação em um pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:153 msgid "" @@ -14358,6 +16087,11 @@ msgid "" ":guilabel:`Warehouse` field value from the sales order. Both should list the" " virtual warehouse location." msgstr "" +"Agora que a cotação foi confirmada como um pedido de venda, clique no botão " +"inteligente :guilabel:`Entrega`. No formulário de entrega do armazém, " +"confirme se o valor de :guilabel:`Local de origem` corresponde ao valor do " +"campo :guilabel:`Armazém` do pedido de venda. Ambos devem listar o local do " +"armazém virtual." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:159 msgid "" @@ -14366,6 +16100,10 @@ msgid "" "order form *must* match in order for the products included in the sales " "order to be pulled from different warehouses." msgstr "" +"O :guilabel:`Local de origem` no formulário de entrega do armazém e o " +":guilabel:`Armazém` na aba :guilabel:`Outras informações` no formulário de " +"pedido de venda *devem* coincidir para que os produtos incluídos no pedido " +"de venda sejam retirados de armazéns diferentes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:163 msgid "" @@ -14373,12 +16111,17 @@ msgid "" " field on the warehouse delivery form, then click :guilabel:`Edit`, make the" " change, and click :guilabel:`Save`." msgstr "" +"Se o armazém virtual não for o valor no campo :guilabel:`Local de origem` no" +" formulário de entrega do depósito, clique em :guilabel:`Editar`, faça a " +"alteração e clique em :guilabel:`Salvar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:166 msgid "" "If the virtual warehouse is not the value in the :guilabel:`Warehouse` field" " on the sales order, then a new quotation may need to be generated." msgstr "" +"Se o armazém virtual não for o valor no campo :guilabel:`Armazém` do pedido " +"de venda, talvez seja necessário gerar uma nova cotação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:168 msgid "" @@ -14387,10 +16130,15 @@ msgid "" " correctly, in which case, review the documentation above again to make sure" " all settings/configuration were done properly." msgstr "" +"Se o campo :guilabel:`Armazém` estiver ausente no formulário de pedido de " +"venda, o armazém virtual (e seus armazéns secundários) pode não ter sido " +"configurado corretamente. Nesse caso, revise a documentação acima novamente " +"para ter certeza de que todas as definições/configurações foram feitas " +"corretamente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 msgid "Delivery order with matching source and child locations." -msgstr "" +msgstr "Ordem de entrega com locais de origem e secundários correspondentes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:176 msgid "" @@ -14399,6 +16147,10 @@ msgid "" ":guilabel:`From` column for each product matches to the *child locations* " "that are tied to the virtual *parent location*." msgstr "" +"Por fim, no formulário de entrega do armazém, na aba :guilabel:`Operações " +"detalhadas`, confirme se os valores de *Locais* na coluna :guilabel:`De` " +"para cada produto correspondem aos *locais secundários* que estão vinculados" +" ao *local virtual primário*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:181 msgid "" @@ -14407,6 +16159,10 @@ msgid "" "*Location* information. If needed, it can be changed from here (granted " "there is quantity on hand for the product in that location)." msgstr "" +"Para ver de quais *Locais* os produtos estão vindo nos menus suspensos, " +"clique no ícone :guilabel:`link interno (seta)` para expandir as informações" +" de *local*. Se necessário, elas podem ser alteradas ali (desde que haja " +"quantidade disponível de produto nesse local)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:185 msgid "" @@ -14415,6 +16171,11 @@ msgid "" " order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to " "invoice for the sales order." msgstr "" +"Depois que tudo estiver configurado corretamente, clique em " +":guilabel:`Validar` e, em seguida, em :guilabel:`Aplicar` para validar a " +"entrega. Em seguida, volte para o formulário de pedido de vendas (pelas " +"trilhas de navegação) e clique em :guilabel:`Criar fatura` para faturar o " +"pedido de vendas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:190 msgid "" @@ -14423,14 +16184,18 @@ msgid "" "from the drop-down menu next to :guilabel:`Default Warehouse` on their " "employee form." msgstr "" +"Para usar um local virtual *primário* como o armazém padrão de pedidos de " +"vendas, cada vendedor pode ter o armazém virtual atribuído a ele no menu " +"suspenso ao lado de :guilabel:`Armazém padrão` em seu formulário de " +"funcionário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 msgid "Default warehouse location on employee form." -msgstr "" +msgstr "Localização padrão do armazém no formulário do funcionário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:3 msgid "Units of measure, packages, and packagings" -msgstr "" +msgstr "Unidades de medida, pacotes e embalagens" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:5 msgid "" @@ -14439,6 +16204,11 @@ msgid "" " are all available to streamline inventory flows, allowing for a variety of " "configurations for products as they enter and leave the warehouse." msgstr "" +"No Odoo, há várias maneiras de especificar a quantidade de produtos que " +"estão sendo comprados, estocados e vendidos. *Unidades de medida, pacotes e " +"embalagens estão disponíveis para otimizar os fluxos de estoque, permitindo " +"uma variedade de configurações para os produtos à medida que entram e saem " +"do armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:12 msgid "Units of measure" @@ -14451,6 +16221,10 @@ msgid "" "time, or size. Different :abbr:`UoMs (Units of Measure)` for weight, for " "example, can be kilos, pounds, ounces, grams, and so on." msgstr "" +"Uma *unidade de medida (UM)* refere-se a qualquer um dos diferentes padrões " +"usados para medir e manipular uma quantidade quantificável de produtos, como" +" unidades, peso, tempo ou tamanho. Exemplos de diferentes :abbr:`UMs` para " +"peso são quilos, libras, onças, gramas e assim por diante." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:18 msgid "" @@ -14458,10 +16232,14 @@ msgid "" "specifying different :abbr:`UoMs (Units of Measure)` for both buying and " "selling products." msgstr "" +"No Odoo, o gerenciamento de estoque e as compras de fornecedores são " +"simplificados com a especificação de diferentes :abbr:`UMs` para compra e " +"venda de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 msgid "Specify unit of measure for selling a product vs purchasing." msgstr "" +"Especificar a unidade de medida para a venda versus a compra de um produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:25 msgid "" @@ -14470,24 +16248,32 @@ msgid "" "automatically converts the different units in the product's purchase/sales " "orders and the corresponding delivery orders/receipts." msgstr "" +"Quando um produto tem uma :guilabel:`unidade de medida` padrão e uma " +":guilabel:`unidade de medida de compra` definidas no formulário do produto, " +"o Odoo converte automaticamente as diferentes unidades nos pedidos de " +"compra/venda do produto e nos recebimentos/ordens de entrega " +"correspondentes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:29 msgid "" "The only condition is that all of the units have to be in the *same " "category* (unit, weight, volume, length, etc.)." msgstr "" +"A única condição é que todas as unidades devem estar na *mesma categoria* " +"(unidade, peso, volume, comprimento etc.)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:33 msgid "On the product form for `Rope`, the following fields are set as:" msgstr "" +"No formulário do produto `Corda`, os campos a seguir são definidos como:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:35 msgid ":guilabel:`Unit of Measure` in `ft` (feet), and" -msgstr "" +msgstr ":guilabel:`Unidade de medida` em `ft` (pés), e" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:36 msgid ":guilabel:`Purchase Unit of Measure` in `cm` (centimeters)." -msgstr "" +msgstr ":guilabel:`Unidade de medida de compra` em `cm` (centímetros)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:38 msgid "" @@ -14495,10 +16281,13 @@ msgid "" "to represent the quantity on the :abbr:`PO (Purchase Order)`, which is also " "in centimeters." msgstr "" +"Como o fornecedor vende corda em `cm`, a :guilabel:`UM` de compra é usada " +"para representar a quantidade no :abbr:`PO (pedido de compra)`, que também " +"está em centímetros." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Display purchase order for the product, rope, in centimeters." -msgstr "" +msgstr "Exibir o pedido de compra do produto, corda, em centímetros." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:45 msgid "" @@ -14509,6 +16298,12 @@ msgid "" ":guilabel:`Validate` button, the quantity in :guilabel:`Done` is " "automatically adjusted to match the :guilabel:`Demand` column." msgstr "" +"Depois de confirmar o :abbr:`PO`, a quantidade do produto (encontrada na " +"coluna :guilabel:`Demanda`, agora visível) é convertida da :abbr:`UM` da " +"compra para a :guilabel:`Unidade de medida` padrão. Em seguida, quando o " +"produto é recebido, clicando no botão :guilabel:`Validar`, a quantidade em " +":guilabel:`Concluído` é automaticamente ajustada para corresponder à coluna " +":guilabel:`Demanda`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:52 msgid "" @@ -14516,16 +16311,23 @@ msgid "" " `500 cm` that was requested on the purchase order, to `16.40 ft` to match " "the internal/stock :guilabel:`Unit of Measure` value." msgstr "" +"No *recebimento* de `Corda`, a quantidade é automaticamente convertida de " +"`500 cm`, que foi encomendada no pedido de compra, para `16,40 pés` para " +"corresponder ao valor de :guilabel:`unidade de medida` interno/do estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Rope quantity is converted from cm to ft during warehouse reception." msgstr "" +"A quantidade de corda é convertida de cm para pés durante o recebimento no " +"armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:61 msgid "" ":ref:`Use Different Units of Measure " "<inventory/management/products/units_of_measure>`" msgstr "" +":ref:`Usar unidades de medidas diferentes " +"<inventory/management/products/units_of_measure>`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:68 msgid "" @@ -14534,6 +16336,10 @@ msgid "" "Packages can be a reusable or disposable (shipping) box, and are **not** " "specific to a product." msgstr "" +"Os pacotes são um contêiner físico com um ou vários produtos de uma " +"separação, normalmente usado para entregas ou transferências internas. Os " +"pacotes podem ser caixas (de remessa) reutilizáveis ou descartáveis e " +"**não** são específicos de um produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:72 msgid "" @@ -14542,6 +16348,11 @@ msgid "" "containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are " "used to ship the products out to customers." msgstr "" +"As caixas reutilizáveis guardam temporariamente os produtos durante uma " +"separação para serem levados para uma área de embalagem ou de expedição. As " +"caixas descartáveis são os contêineres de remessa reais (por exemplo, caixas" +" de papelão, envelopes, etc.). Elas são usadas para enviar os produtos aos " +"clientes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:76 msgid "" @@ -14551,6 +16362,10 @@ msgid "" " into two separate packages, each containing 10 boxes of pencils and 2 boxes" " of erasers." msgstr "" +"Itens em um pedido de vendas (SO) podem ser separados em diferentes pacotes " +"para acomodar os produtos. Por exemplo, um :abbr:`SO` que tenha 20 caixas de" +" lápis e 4 caixas de borrachas pode ser separado em dois pacotes distintos, " +"cada um contendo 10 caixas de lápis e 2 caixas de borrachas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:82 msgid "" @@ -14558,6 +16373,8 @@ msgid "" "as many packages that are needed to accommodate the :abbr:`SO (Sales " "Order)`." msgstr "" +"Os produtos *não* precisam ser divididos igualmente. Os produtos podem ser " +"divididos em quantos pacotes forem necessários para acomodar o :abbr:`SO`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:85 msgid "" @@ -14565,6 +16382,9 @@ msgid "" "there is a full history for each product, including which package each item " "is shipped out in." msgstr "" +"No Odoo, a quantidade de produtos em cada pacote precisa ser registrada para" +" que haja um histórico completo de cada produto, incluindo em qual pacote " +"cada item é enviado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:88 msgid "" @@ -14573,6 +16393,10 @@ msgid "" "--> Operations`. Click the :guilabel:`Packages` check box, and then " ":guilabel:`Save` to activate the feature." msgstr "" +"Para usar esse método, certifique-se de que a opção :guilabel:`Pacotes` " +"esteja ativada, navegando até o :menuselection:`app Inventário --> " +"Configuração --> Definições --> Operações`. Clique na caixa de seleção " +":guilabel:`Pacotes` e, em seguida, :guilabel:`salve` para ativar o recurso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:92 msgid "" @@ -14580,10 +16404,14 @@ msgid "" ":guilabel:`≣ (Detailed Operations)` icon to the right of each product in the" " :guilabel:`Operations` tab." msgstr "" +"Em uma ordem de entrega, atribua o pacote a ser usado clicando no ícone " +":guilabel:`≣ (Operações detalhadas)` à direita de cada produto na aba " +":guilabel:`Operações`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 msgid "Find detailed operations icon to the right on the product line." msgstr "" +"Encontre o ícone de operações detalhadas à direita na linha de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:99 msgid "" @@ -14592,6 +16420,10 @@ msgid "" ":guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed " "above the customizable product line." msgstr "" +"Clicar no ícone :guilabel:`≣ (Operações Detalhadas)` de um produto revela " +"uma janela pop-up. Nessa janela, o nome do :guilabel:`produto`, a " +":guilabel:`demanda` e a :guilabel:`quantidade concluída` são claramente " +"exibidos acima da linha personalizável do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:103 msgid "" @@ -14600,6 +16432,9 @@ msgid "" "Package`, which represents what package(s) the product(s) will be packaged " "into." msgstr "" +"Aqui, o local do armazém de onde o produto está vindo pode ser modificado, " +"bem como o :guilabel:`pacote de origem` e :guilabel:`pacote de destino`, que" +" representam em quais pacotes os produtos serão embalados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:107 msgid "" @@ -14607,10 +16442,14 @@ msgid "" "the desired amount in the :guilabel:`Done` field to specify the amount of " "products that will go into the :guilabel:`Destination Package`." msgstr "" +"Clique em :guilabel:`Adicionar uma linha` para incluir cada pacote adicional" +" usado. Insira a quantidade desejada no campo :guilabel:`Concluído` para " +"especificar a quantidade de produtos que irão para o :guilabel:`Pacote de " +"destino`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:112 msgid "Multiple packages in a single delivery" -msgstr "" +msgstr "Vários pacotes em uma única entrega" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:114 msgid "" @@ -14620,6 +16459,12 @@ msgid "" "This opens the :guilabel:`Detailed Operations` window with an editable table" " to specify which products are intended for which package." msgstr "" +"Embora uma :abbr:`DO (ordem de entrega)` seja normalmente associada a um " +"único pacote, os pedidos podem ser divididos clicando no ícone :guilabel:`≣ " +"(operações detalhadas)` ao lado dos produtos em uma linha do :abbr:`SO " +"(pedido de venda)`. Isso abre a janela :guilabel:`Operações detalhadas` com " +"uma tabela editável para especificar quais produtos se destinam a qual " +"pacote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:120 msgid "" @@ -14630,6 +16475,12 @@ msgid "" ":guilabel:`Detailed Operations` window that is used to detail how products, " "like the 20 `Box of Pencils`, are packaged." msgstr "" +"Para embalar 10 caixas de lápis e 2 caixas de borrachas do mesmo :abbr:`SO`," +" comece navegando até a :abbr:`DO`. Em seguida, selecione o ícone " +":guilabel:`≣ (quatro linhas horizontais)` à direita do produto, `Caixa de " +"lápis`. Clicar no ícone abre a janela :guilabel:`Operações detalhadas` que é" +" usada para detalhar como os produtos, como as 20 `Caixa de lápis`, são " +"embalados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:126 msgid "" @@ -14641,12 +16492,21 @@ msgid "" ":guilabel:`Add a line` to assign the remaining products in another package, " "`PACK0000007`." msgstr "" +"Digite `10` no campo :guilabel:`Concluído` para empacotar 10 produtos no " +":guilabel:`pacote de desntino`. Para especificar o pacote de destino, digite" +" o nome de um pacote existente (como `PACK0000006`) no campo " +":guilabel:`Pacote de destino`. Se não existir, o Odoo exibirá o botão " +":guilabel:`Criar` para criar um novo pacote. Clique em :guilabel:`Adicionar " +"uma linha` para atribuir os produtos restantes a outro pacote, " +"`PACK0000007`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "" "Detailed operations pop-up where the amount of product going in a pack can " "be specified." msgstr "" +"Pop-up de operações detalhadas onde a quantidade de produto que vai em um " +"pacote pode ser especificada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:136 msgid "" @@ -14654,16 +16514,23 @@ msgid "" "Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and " "`PACK0000007` each." msgstr "" +"Selecione :guilabel:`Operações detalhadas` na linha de produtos `Caixa de " +"borrachas` e, da mesma forma, defina 2 produtos como :guilabel:`Concluídos` " +"em `PACK0000006` e `PACK0000007`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Put in pack button to match the done amount matches the demand." msgstr "" +"Botão \"Colocar no pacote\" para que a quantidade realizada corresponda à " +"demanda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:143 msgid "" "Once all the products for each line have been entered, click " ":guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." msgstr "" +"Depois que todos os produtos de cada linha tiverem sido inseridos, clique em" +" :guilabel:`Confirmar` para retornar à :abbr:`DO (ordem de entrega)`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:146 msgid "" @@ -14672,6 +16539,10 @@ msgid "" "matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button" " to complete the delivery order." msgstr "" +"A quantidade :guilabel:`concluída` na :abbr:`ordem de entrega` é atualizada " +"à medida que são selecionados produtos para cada pacote. Quando a quantidade" +" :guilabel:`concluída` corresponder à quantidade a :guilabel:`demanda`, " +"clique no botão :guilabel:`Validar` para concluir a ordem de entrega." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:151 msgid "" @@ -14680,6 +16551,10 @@ msgid "" " to rename the package, or modify its contents, is available in the " ":guilabel:`Detailed Operations` pop-up." msgstr "" +"O botão :guilabel:`Colocar no pacote` tem o objetivo de empacotar " +"rapidamente todos os produtos da :abbr:`ordem de entrega` em um novo pacote." +" A opção de renomear o pacote ou modificar seu conteúdo está disponível no " +"pop-up :guilabel:`Operações detalhadas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:155 msgid "" @@ -14687,6 +16562,9 @@ msgid "" "of the delivery order reveals a separate page, showing all the packages used" " in that :abbr:`DO (Delivery Order)`." msgstr "" +"Clicar no botão inteligente :guilabel:`pacotes` no canto superior direito da" +" ordem de entrega abre uma página separada, mostrando todos os pacotes " +"usados nessa :abbr:`DO`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:159 msgid "Packagings" @@ -14699,6 +16577,10 @@ msgid "" "cannot be reusable, and each specific packaging must be defined on the " "individual product form." msgstr "" +"A *embalagem* é específica do produto e refere-se a um contêiner descartável" +" que contém várias unidades de um produto específico. Ao contrário dos " +"pacotes, as embalagens não podem ser reutilizáveis, e cada embalagem " +"específica deve ser definida no formulário de produto individual." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:165 msgid "" @@ -14707,10 +16589,15 @@ msgid "" "`12`, and `36` can packaging configured on the individual product since " "packagings are product specific, not generic." msgstr "" +"Por exemplo, diferentes embalagens para latas de refrigerante podem ser " +"configuradas como um pacote de 6, um pacote de 12 ou uma caixa de 36. Cada " +"sabor de refrigerante precisaria de uma embalagem de lata de `6`, `12` e " +"`36` configurada no produto individual, já que as embalagens são específicas" +" do produto, não genéricas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:170 msgid "Set up packagings" -msgstr "" +msgstr "Configurar embalagens" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:172 msgid "" @@ -14720,12 +16607,19 @@ msgid "" "check the box next to :guilabel:`Product Packagings`, and click " ":guilabel:`Save`." msgstr "" +"Para usar embalagens, certifique-se de que o recurso :guilabel:`Embalagens " +"de produtos` esteja ativado. Para fazer isso, navegue até " +":menuselection:`app Inventário --> Configuração --> Definições`. Em seguida," +" sob o título :guilabel:`Produtos`, marque a caixa ao lado de " +":guilabel:`Embalagens de produtos` e clique em :guilabel:`Salvar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:177 msgid "" "In Odoo, product packagings are used on sales/purchase orders and inventory " "transfers." msgstr "" +"No Odoo, as embalagens de produtos são usadas em pedidos de vendas/compras e" +" transferências de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:179 msgid "" @@ -14733,6 +16627,9 @@ msgid "" "Products --> Products` and click on the desired product, then click " ":guilabel:`Edit` on the product page." msgstr "" +"Em seguida, para criar embalagens, navegue até :menuselection:`app " +"Inventário --> Produtos --> Produtos` e clique no produto desejado, depois " +"clique em :guilabel:`Editar` na página do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:182 msgid "" @@ -14741,16 +16638,22 @@ msgid "" "pop-up window appears, in which the following information for each packaging" " should be entered:" msgstr "" +"Na aba :guilabel:`Inventário`, role para baixo até a seção " +":guilabel:`Embalagem` e clique em :guilabel:`Adicionar uma linha`. Em " +"seguida, é exibida uma janela pop-up, na qual as seguintes informações de " +"cada embalagem devem ser inseridas:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:186 msgid "" ":guilabel:`Packaging`: name of packaging that appears on sales/purchase " "orders as a packaging option for the product" msgstr "" +":guilabel:`Embalagem`: nome da embalagem que aparece nos pedidos de " +"compra/venda como uma opção de embalagem para o produto" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:188 msgid ":guilabel:`Contained quantity`: amount of product in the packaging" -msgstr "" +msgstr ":guilabel:`Quantidade contida`: quantidade de produto na embalagem" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:189 msgid "" @@ -14758,6 +16661,10 @@ msgid "" "<barcode/operations/intro>` to trace the packaging of a product during stock" " moves or pickings. Leave blank if not in use" msgstr "" +":guilabel:`Código de barras`: identificador usado com o :ref:`app Código de " +"barras <barcode/operations/intro>` para rastrear a embalagem de um produto " +"durante movimentações de estoque ou separações. Deixe em branco se não " +"estiver em uso" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:191 msgid "" @@ -14765,6 +16672,9 @@ msgid "" "selected company. Leave blank to make the packaging available across all " "companies." msgstr "" +":guilabel:`Empresa`: indica que a embalagem está disponível apenas na " +"empresa selecionada. Deixe em branco para que a embalagem esteja disponível " +"em todas as empresas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:195 msgid "" @@ -14773,10 +16683,14 @@ msgid "" "quantity` to `6` in the pop-up window that appears after clicking on " ":guilabel:`Add a line`." msgstr "" +"Crie um tipo de embalagem para 6 latas do produto, `Refrigerante de uva`, " +"nomeando a :guilabel:`Embalagem` como `1/2 fardo` e definindo a " +":guilabel:`quantidade contida` como `6` na janela pop-up que aparece depois " +"de clicar em :guilabel:`Adicionar uma linhda`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Create 6-pack case for product." -msgstr "" +msgstr "Criar \"1/2 fardo\" com 6 unidades para o produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:203 msgid "" @@ -14785,22 +16699,30 @@ msgid "" "detail form, or :guilabel:`Save & New` to save the packaging and create " "another one in a fresh pop-up window." msgstr "" +"Quando todas as informações necessárias tiverem sido inseridas, clique em " +":guilabel:`Salvar e Fechar` para salvar a embalagem e retornar ao formulário" +" de detalhes do produto, ou em :guilabel:`Salvar e Novo` para salvar a " +"embalagem e criar outra em uma nova janela pop-up." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:208 msgid "" "View all product packagings in the :guilabel:`Inventory` tab of the product " "form." msgstr "" +"Visualize todas as embalagens de produtos na aba :guilabel:`Inventário` do " +"formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "" "Show packaging and contained quantities, specified on the product page form in the\n" "Inventory tab." msgstr "" +"Mostrar embalagem e quantidades contidas, especificadas no formulário da página do produto na aba \n" +"Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:216 msgid "View all packagings" -msgstr "" +msgstr "Exibir todas as embalagens" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:218 msgid "" @@ -14810,6 +16732,11 @@ msgid "" "list of all packagings that have been created for all products. Create new " "packagings by clicking :guilabel:`Create`." msgstr "" +"Para visualizar todas as embalagens que foram criadas, vá para " +":menuselection:`app Inventário --> Configuração --> Embalagens de produtos`." +" Isso abre a página :guilabel:`Embalagens de produtos` com uma lista " +"completa de todas as embalagens que foram criadas para todos os produtos. " +"Crie novos pacotes clicando em :guilabel:`Criar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:224 msgid "" @@ -14818,14 +16745,18 @@ msgid "" "product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 " "products, or a `Case` of 32 products." msgstr "" +"Dois produtos de refrigerante, `Refrigerante de uva` e `Coca-cola Zero`, têm" +" três tipos de embalagens configuradas. Na página :guilabel:`Embalagens de " +"produtos`, cada produto pode ser vendido como um `1/2 fardo` que contém 6 " +"produtos, `Fardo` de 12 produtos ou uma `Caixa` de 32 produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "List of different packagings for products." -msgstr "" +msgstr "Lista de embalagens diferentes para produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:233 msgid "Apply packagings" -msgstr "" +msgstr "Aplicar embalagens" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:235 msgid "" @@ -14834,16 +16765,20 @@ msgid "" "displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` " "field." msgstr "" +"Ao criar um pedido de venda no aplicativo :menuselection:`Vendas`, " +"especifique as embalagens que devem ser usadas para os produtos. A embalagem" +" escolhida é exibida no :abbr:`SO` no campo :guilabel:`Pacote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:240 msgid "" "18 cans of the product, `Grape Soda`, is packed using three 6-pack " "packagings." msgstr "" +"18 latas do produto `Refrigerante de uva` são embaladas em três 1/2 fardos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Assign packagings on the Sales Order Line." -msgstr "" +msgstr "Atribuir embalagens na linha de pedidos de vendas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:247 msgid "" @@ -14852,10 +16787,14 @@ msgid "" "scanning the packaging barcode automatically adds the number of units in the" " packaging to the internal count of the product." msgstr "" +"A embalagem pode ser usada em conjunto com o Odoo :ref:`Código de barras " +"<inventory/barcode/software>`. Ao receber produtos de fornecedores, a " +"leitura do código de barras da embalagem adiciona automaticamente o número " +"de unidades na embalagem à contagem interna do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 msgid "Process wave transfers" -msgstr "" +msgstr "Processar transferências em ondas" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:5 msgid "" @@ -14864,24 +16803,38 @@ msgid "" "pick orders in a warehouse, and depending on the situation, one method may " "be a better fit than the other." msgstr "" +"Enquanto uma transferência em lote é um grupo de várias separações, uma " +"**transferência em onda** contém apenas algumas partes de diferentes " +"separações. Ambos os métodos são usados para selecionar pedidos em um " +"armazém e, dependendo da situação, um método pode ser mais adequado do que o" +" outro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:9 msgid "" "To handle orders of a specific product category, or fetch products that are " "at the same location, wave transfers are the ideal method." msgstr "" +"Para lidar com pedidos de uma categoria de produto específica ou buscar " +"produtos que estão no mesmo local, as transferências em ondas são o método " +"ideal." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:12 msgid "" "In Odoo, wave transfers are actually batch transfers with an extra step: " "transfers are split before being grouped in a batch." msgstr "" +"No Odoo, as transferências em ondas são, na verdade, transferências em lote " +"com uma etapa extra: as transferências são divididas antes de serem " +"agrupadas em um lote." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:18 msgid "" "Before a wave transfer can be created, the :guilabel:`Batch Transfers` and " ":guilabel:`Wave Transfers` options must be activated." msgstr "" +"Antes que uma transferência em onda possa ser criada, as opções " +":guilabel:`Transferências em lote` e :guilabel:`Transferências em onda` " +"devem ser ativadas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:21 msgid "" @@ -14890,21 +16843,29 @@ msgid "" ":guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the " "settings." msgstr "" +"Primeiro, vá para :menuselection:`Inventário --> Configuração --> " +"Definições`. Na seção :guilabel:`Operações`, ative :guilabel:`Transferências" +" em lote` e :guilabel:`Transferências em onda`. Em seguida, clique em " +":guilabel:`Salvar` para aplicar as configurações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 msgid "" "View of Odoo Inventory app settings to enable the wave transfers option." msgstr "" +"Visualização das configurações do aplicativo Odoo Inventário para ativar a " +"opção de transferências em onda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:30 msgid "Add products to a wave" -msgstr "" +msgstr "Adicionar produtos a uma transferência em onda" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:32 msgid "" "Now that the settings are activated, start a wave transfer by adding " "products to a wave." msgstr "" +"Com as definições ativadas, inicie uma transferência em onda adicionando " +"produtos a uma onda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:34 msgid "" @@ -14915,30 +16876,41 @@ msgid "" "icon in the corner of the operation type's card) and click " ":guilabel:`Operations`." msgstr "" +"As transferências em onda só podem conter linhas de produtos de " +"transferências do mesmo tipo de operação. Para visualizar todas as " +"transferências e linhas de produtos em uma operação específica, primeiro " +"acesse o painel :guilabel:`Inventário` e localize o cartão do tipo de " +"operação desejado. Em seguida, abra o menu de opções (o ícone de três pontos" +" no canto do cartão do tipo de operação) e clique em :guilabel:`Operações`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 msgid "How to get an operation type's list of operations." -msgstr "" +msgstr "Como obter a lista de operações de um tipo de operação." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:43 msgid "" "On the operations page, select the product lines you want to add in a new or" " existing wave. Then, click :guilabel:`Add to Wave`." msgstr "" +"Na página de operações, selecione as linhas de produtos que deseja adicionar" +" em uma onda nova ou existente. Em seguida, clique em :guilabel:`Adicionar à" +" onda`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 msgid "Select lines to add to the wave." -msgstr "" +msgstr "Selecione as linhas a serem adicionadas à onda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:51 msgid "" "Use the :guilabel:`Filters` in the search bar to group lines with the same " "product, location, carrier, etc..." msgstr "" +"Use os :guilabel:`filtros` na barra de pesquisa para agrupar linhas com o " +"mesmo produto, local, transportadora, etc." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:54 msgid "After that, a pop-up box appears." -msgstr "" +msgstr "Depois disso, é exibida uma caixa pop-up." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:56 msgid "" @@ -14946,6 +16918,9 @@ msgid "" ":guilabel:`an existing wave transfer` option and select the existing wave " "transfer from the drop-down menu." msgstr "" +"Para adicionar as linhas selecionadas a uma transferência deem onda " +"existente, selecione a opção :guilabel:`uma transferência em onda existente`" +" e selecione-a no menu suspenso." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:59 msgid "" @@ -14954,10 +16929,16 @@ msgid "" "optional :guilabel:`Responsible` field. Once the desired options are " "selected, click :guilabel:`Confirm` to add the product lines to a wave." msgstr "" +"Para criar uma nova transferência em onda, selecione a opção :guilabel:`uma " +"nova transferência em onda`. Se estiver criando uma nova transferência em " +"onda, também é possível definir um funcionário no campo opcional " +":guilabel:`Responsável`. Depois que as opções desejadas forem selecionadas, " +"clique em :guilabel:`Confirmar` para adicionar as linhas de produtos a uma " +"onda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:64 msgid "View wave transfers" -msgstr "" +msgstr "Visualizar transferências em ondas" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:66 msgid "" @@ -14966,14 +16947,19 @@ msgid "" " can also be viewed in the :guilabel:`Barcode` app by going to " ":menuselection:`Barcode --> Batch Transfers`." msgstr "" +"Para visualizar todas as transferências em ondas e seus status, vá para " +":menuselection:`Inventário --> Operações --> Transferências em onda`. As " +"transferências em ondas também podem ser visualizadas no aplicativo " +":guilabel:`Código de barras`, acessando :menuselection:`Código de barras -->" +" Transferências em lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:5 msgid "Inventory management" -msgstr "" +msgstr "Gerenciamento de estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:3 msgid "Inventory adjustments" -msgstr "" +msgstr "Ajustes de estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:7 msgid "" @@ -14984,20 +16970,29 @@ msgid "" "be made to reconcile the differences, and ensure that the recorded counts in" " the database match the actual counts in the warehouse." msgstr "" +"Em qualquer sistema de gerenciamento de armazém, as contagens de inventário " +"registradas no banco de dados às vezes podem não corresponder às contagens " +"reais no armazém. A discrepância entre as duas contagens pode ser causada " +"por danos, erros humanos, roubo ou outros fatores. Dessa forma, devem ser " +"feitos ajustes no inventário para reconciliar as diferenças e garantir que " +"as contagens registradas no banco de dados correspondam às contagens reais " +"no armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:14 msgid "Inventory Adjustments page" -msgstr "" +msgstr "Página de ajustes de estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:16 msgid "" "To view the *Inventory Adjustments* page, navigate to " ":menuselection:`Inventory app --> Operations --> Inventory Adjustments`." msgstr "" +"Para visualizar a página *Ajustes de estoque*, navegue até " +":menuselection:`app Inventário --> Operações --> Ajustes de estoque`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "In stock products listed on the Inventory adjustments page." -msgstr "" +msgstr "Produtos em estoque listados na página de ajustes de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:23 msgid "" @@ -15005,18 +17000,25 @@ msgid "" "currently in stock are listed, with each product line containing the " "following information:" msgstr "" +"Na página :guilabel:`Ajustes de estoque`, todos os produtos que estão " +"atualmente em estoque são listados, com cada linha de produto contendo as " +"seguintes informações:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 msgid "" ":guilabel:`Location`: the specific location in the warehouse where a product" " is stored." msgstr "" +":guilabel:`Local`: o local específico no armazém onde um produto está " +"armazenado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:27 msgid "" ":guilabel:`Product`: the product whose quantity is listed on the inventory " "adjustment line." msgstr "" +":guilabel:`Produto`: o produto cuja quantidade está listada na linha de " +"ajuste de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:28 msgid "" @@ -15024,6 +17026,9 @@ msgid "" "specific product listed. It can contain letters, numbers, or a combination " "of both." msgstr "" +":guilabel:`Número de série/lote`: o identificador de rastreamento atribuído " +"ao produto específico listado, que pode conter letras, números ou uma " +"combinação de ambos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:32 msgid "" @@ -15032,12 +17037,19 @@ msgid "" "identified product is displayed on its own product line with its own " "lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." msgstr "" +"Se um produto específico tiver uma quantidade de mais de `1,00` em estoque e" +" mais de um número de série (ou de lote) atribuído a ele, cada produto " +"identificado exclusivamente será exibido em sua própria linha de produtos " +"com seu próprio número de série/lote, exibido na coluna :guilabel:`Número de" +" série/lote`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:37 msgid "" ":guilabel:`On Hand Quantity`: the quantity of the product currently recorded" " in the database." msgstr "" +":guilabel:`Quantidade em mãos`: a quantidade do produto atualmente " +"registrada na base de dados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:38 msgid "" @@ -15046,6 +17058,9 @@ msgid "" ":guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is " ":guilabel:`Units`." msgstr "" +":guilabel:`UM`: a *unidade de medida* na qual o produto é medido. A menos " +"que especificado de outra forma (como em :guilabel:`libras` ou " +":guilabel:`onças`), a :abbr:`UM` padrão é :guilabel:`unidades`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:41 msgid "" @@ -15053,6 +17068,10 @@ msgid "" "count. This field is left blank by default, but can be changed, depending on" " if it matches the :guilabel:`On Hand Quantity` or not." msgstr "" +":guilabel:`Quantidade contada`: a quantidade real contada durante uma " +"contagem de estoque. Esse campo é deixado em branco por padrão, mas pode ser" +" alterado, dependendo se ele corresponde à :guilabel:`quantidade em mãos` ou" +" não." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:44 msgid "" @@ -15061,6 +17080,9 @@ msgid "" "made. The difference is automatically calculated after every inventory " "adjustment." msgstr "" +":guilabel:`Diferença`: a diferença entre a :guilabel:`quantidade em mãos` e " +"a :guilabel:`quantidade contada`, depois que um ajuste de estoque é feito. A" +" diferença é calculada automaticamente após cada ajuste de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 msgid "" @@ -15068,6 +17090,9 @@ msgid "" " otherwise specified, this date will default to the 31st of December of the " "current year." msgstr "" +":guilabel:`Data agendada`: a data em que a contagem deve ser feita. Se não " +"for especificado de outra forma, essa data terá como padrão o dia 31 de " +"dezembro do ano atual." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 msgid "" @@ -15075,6 +17100,9 @@ msgid "" " either be the person physically counting the inventory, or applying the " "count in the database." msgstr "" +":guilabel:`Usuário`: a pessoa atribuída à contagem na base de dados. Pode " +"ser a pessoa que está contando fisicamente o inventário ou aplicando a " +"contagem na base de dados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:51 msgid "" @@ -15083,6 +17111,10 @@ msgid "" ":guilabel:`Rental`), the default *Product Category* is set to " ":guilabel:`All`." msgstr "" +":guilabel:`Categoria de produtos`: a categoria atribuída internamente a um " +"produto específico. A menos que especificado de outra forma (ou seja, como " +":guilabel:`Consumível` ou :guilabel:`Locação`), a *Categoria de produto* " +"padrão é definida como :guilabel:`Todos`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:54 msgid "" @@ -15091,12 +17123,18 @@ msgid "" "purchase orders, or manufacturing orders that might change the available " "quantity once fulfilled." msgstr "" +":guilabel:`Quantidade disponível`: a quantidade de um produto específico que" +" está disponível no momento, com base em pedidos de vendas pendentes/não " +"concluídos, pedidos de compra ou ordens de produção que possam alterar a " +"quantidade disponível depois de atendidos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 msgid "" ":guilabel:`Accounting Date`: the date on which the adjustments will be " "accounted in the Odoo *Accounting* app." msgstr "" +":guilabel:`Data contábil`: a data em que os ajustes serão contabilizados no " +"aplicativo Odoo *Financeiro*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:59 msgid "" @@ -15104,6 +17142,9 @@ msgid "" "are being made on. The company is listed in the top right corner of the " "database, next to the user currently logged in." msgstr "" +":guilabel:`Empresa`: a empresa em cujo base de dados esses ajustes de " +"inventário estão sendo feitos. A empresa é listada no canto superior direito" +" da base de dados, ao lado do usuário atualmente conectado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:63 msgid "" @@ -15112,10 +17153,14 @@ msgid "" "the form's top row, and select any desired column to reveal by clicking the " "checkbox next to that option." msgstr "" +"Algumas colunas ficam ocultas por padrão. Para revelar essas colunas, clique" +" no botão :guilabel:`opções adicionais` (ícone de três pontos) na " +"extremidade direita da linha superior do formulário e selecione a coluna " +"desejada a ser revelada clicando na caixa de seleção ao lado dessa opção." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 msgid "Create an inventory adjustment" -msgstr "" +msgstr "Criar um ajuste de estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:70 msgid "" @@ -15123,6 +17168,9 @@ msgid "" "Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank " "inventory adjustment line at the bottom of the page." msgstr "" +"Para criar um novo ajuste de estoque na página :menuselection:`Ajustes de " +"estoque`, clique em :guilabel:`Criar`. Isso cria uma nova linha de ajuste de" +" estoque em branco na parte inferior da página." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:74 msgid "" @@ -15132,12 +17180,19 @@ msgid "" "number can also be chosen from the drop-down menu under the " ":guilabel:`Lot/Serial Number` column." msgstr "" +"Nessa linha de ajuste de estoque em branco, clique no menu suspenso na " +"coluna :guilabel:`Produto` e selecione um produto. Se o produto selecionado " +"for rastreado por números de série/lote, o número em questão também poderá " +"ser escolhido no menu suspenso da coluna :guilabel:`Número de lote/série`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:79 msgid "" "Next, set the value in the :guilabel:`Counted Quantity` column to the " "quantity counted for that product during the inventory adjustment process." msgstr "" +"Em seguida, defina o valor na coluna :guilabel:`Quantidade contada` como a " +"quantidade contada para esse produto durante o processo de ajuste de " +"estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:83 msgid "" @@ -15146,6 +17201,11 @@ msgid "" "is recorded in the product's inventory adjustment history, so it should be " "set to reflect the actual quantity counted." msgstr "" +"A :guilabel:`quantidade contada` para novos ajustes de estoque é definida " +"como `0.00` por padrão. Uma movimentação de estoque com `0.00` de " +":guilabel:`quantidade concluída` é registrada no histórico de ajustes de " +"estoque do produto, portanto, deve ser definida para refletir a quantidade " +"real contada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:87 msgid "" @@ -15156,6 +17216,12 @@ msgid "" "selecting a responsible :guilabel:`User` assigns a user to the specific " "inventory adjustment (for traceability purposes)." msgstr "" +"À direita da coluna :guilabel:`Quantidade contada`, a :guilabel:`data " +"agendada` e o :guilabel:`usuário` também podem ser alterados por seus " +"respectivos menus suspensos. A alteração da :guilabel:`data agendada` altera" +" a data em que o ajuste de estoque deve ser processado e a seleção de um " +":guilabel:`usuário` responsável atribui um usuário ao ajuste de estoque " +"específico (para fins de rastreabilidade)." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:93 msgid "" @@ -15163,6 +17229,9 @@ msgid "" "away from the line. Doing so saves the adjustment, and moves the line to the" " top of the page." msgstr "" +"Quando todas as alterações tiverem sido feitas na nova linha de ajuste de " +"estoque, clique fora da linha. Isso salva o ajuste e move a linha para o " +"topo da página." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:96 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:158 @@ -15174,10 +17243,16 @@ msgid "" " quantities match, and haven't been changed at all, no value appears in the " ":guilabel:`Difference` column." msgstr "" +"Se a :guilabel:`quantidade contada` for maior que a :guilabel:`quantidade em" +" mãos`, o valor na coluna :guilabel:`Diferença` será **verde**. Se a " +":guilabel:`quantidade contada` for menor que a :guilabel:`quantidade em " +"mãos`, o valor na coluna :guilabel:`Diferença` estará em **vermelho**. Se as" +" quantidades forem iguais e não tiverem sido alteradas, nenhum valor " +"aparecerá na coluna :guilabel:`Diferença`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "Difference column on inventory adjustments page." -msgstr "" +msgstr "Coluna de diferença na página de ajustes de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:106 msgid "" @@ -15185,6 +17260,9 @@ msgid "" "yet applied. This means that the quantity on hand before the adjustment has " "not yet been updated to match the new, real counted quantity." msgstr "" +"Nesse estágio, a contagem (:dfn:`ajuste de estoque`) é registrada, mas ainda" +" não aplicada. Isso significa que a quantidade disponível antes do ajuste " +"ainda não foi atualizada para corresponder à nova quantidade real contada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:110 msgid "" @@ -15195,6 +17273,13 @@ msgid "" "an :guilabel:`Apply` button. Clicking this button instead causes an " ":guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." msgstr "" +"Há duas maneiras de aplicar o novo ajuste de estoque. A primeira maneira é " +"clicar no botão :guilabel:`Aplicar` na linha na extremidade direita da " +"página. A segunda maneira é clicar na caixa de seleção na extremidade " +"esquerda da linha. Isso revela novas opções de botões na parte superior da " +"página, uma das quais é um botão :guilabel:`Aplicar`. Clicar nesse botão faz" +" com que uma janela pop-up :guilabel:`Motivo/Referência do ajuste de " +"estoque` seja exibida." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:116 msgid "" @@ -15203,20 +17288,28 @@ msgid "" "Reason` field is pre-populated with the date the adjustment is being made " "on, but can be changed to reflect whatever reference or reason is desired." msgstr "" +"Nesse menu pop-up, uma referência ou motivo pode ser atribuído ao ajuste de " +"estoque. Por padrão, o campo :guilabel:`Motivo/Referência do estoque` é " +"preenchido previamente com a data em que o ajuste está sendo feito, mas pode" +" ser alterado para refletir a referência ou motivo desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:120 msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." msgstr "" +"Quando estiver pronto, clique em :guilabel:`Aplicar` para aplicar o ajuste " +"de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "" "Apply all option applies the inventory adjustment once a reason is " "specified." msgstr "" +"A opção Aplicar tudo aplica o ajuste de estoque quando um motivo é " +"especificado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 msgid "Count products" -msgstr "" +msgstr "Contar produtos" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 msgid "" @@ -15225,6 +17318,10 @@ msgid "" "Adjustments` to update the :guilabel:`Counted Quantity` column for each " "product line." msgstr "" +"A contagem de produtos é uma atividade recorrente em um armazém. Quando a " +"contagem estiver concluída, vá para o :menuselection:`app Inventário --> " +"Operações --> Ajustes de estoque` para atualizar a coluna " +":guilabel:`Quantidade contada` em cada linha de produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:133 msgid "" @@ -15233,6 +17330,11 @@ msgid "" "If the recorded value and the counted value do match, click the " ":guilabel:`Set` button (target icon) at the far right of the product line." msgstr "" +"Em cada linha de produto, identifique se o valor da coluna " +":guilabel:`Quantidade em mãos` registrado na base de dados corresponde ao " +"valor recém-contado. Se o valor registrado e o valor contado corresponderem," +" clique no botão :guilabel:`Definir` (ícone de alvo) na extremidade direita " +"da linha de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:137 msgid "" @@ -15242,10 +17344,15 @@ msgid "" "inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the " "product's inventory adjustment history." msgstr "" +"Isso copia o valor da coluna :guilabel:`Quantidade em mãos` para a coluna " +":guilabel:`Quantidade contada` e define o valor da coluna " +":guilabel:`Diferença` como `0.00`. Na sequência, uma vez aplicada, uma " +"movimentação de estoque com a coluna :guilabel:`Quantidade concluída` `0.00`" +" é registrada no histórico de ajuste de estoque do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "Zero count inventory adjustment move." -msgstr "" +msgstr "Movimento de ajuste de estoque de contagem zero." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:146 msgid "" @@ -15254,6 +17361,10 @@ msgid "" "clicking the :guilabel:`Set` button, record the real value in the field in " "the :guilabel:`Counted Quantity` column." msgstr "" +"Se o valor recém-contado de um determinado produto **não** corresponder ao " +"valor de :guilabel:`Quantidade em mãos` registrado na base de dados, em vez " +"de clicar no botão :guilabel:`Definir`, registre o valor real no campo da " +"coluna :guilabel:`Quantidade contada`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:150 msgid "" @@ -15262,6 +17373,10 @@ msgid "" "changed. This automatically assigns a :guilabel:`Counted Quantity` of " "`0.00`." msgstr "" +"Para fazer isso, clique no campo da coluna :guilabel:`Quantidade contada` na" +" linha de ajuste de estoque específica do produto cuja contagem está sendo " +"alterada. Isso atribui automaticamente uma :guilabel:`Quantidade contada` de" +" `0.00`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:154 msgid "" @@ -15270,6 +17385,9 @@ msgid "" "adjustment, and automatically adjusts the value in the " ":guilabel:`Difference` column." msgstr "" +"Para alterar esse valor, digite um novo valor que corresponda ao valor real " +"recém-contado. Em seguida, clique fora da linha. Isso salva o ajuste e " +"ajusta automaticamente o valor na coluna :guilabel:`Diferenã`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:164 msgid "" @@ -15277,12 +17395,17 @@ msgid "" ":guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is " "recorded in the product's inventory adjustment history." msgstr "" +"Posteriormente, uma vez aplicado, uma movimentação com a diferença entre a " +":guilabel:`Quantidade em mãos` e a :guilabel:`Quantidade contada` é " +"registrada no histórico de ajuste de estoque do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "" "Inventory Adjustments History dashboard detailing a list of prior product " "moves." msgstr "" +"Painel de histórico de ajustes de estoque detalhando uma lista de " +"movimentações anteriores dos produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:172 msgid "" @@ -15293,10 +17416,16 @@ msgid "" "extra precaution, Odoo asks for confirmation before applying the inventory " "adjustment." msgstr "" +"Às vezes, uma contagem é feita mas não pode ser aplicada na base de dados " +"imediatamente. No período entre a contagem real e a aplicação do ajuste de " +"estoque, podem ocorrer movimentações de produtos. Nesse caso, a quantidade " +"disponível na base de dados pode mudar e não ser mais consistente com a " +"quantidade contada. Como precaução extra, o Odoo pede confirmação antes de " +"aplicar o ajuste de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 msgid "Change inventory count frequency" -msgstr "" +msgstr "Alterar a frequência da contagem de inventário" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 msgid "" @@ -15305,6 +17434,10 @@ msgid "" "companies, it is crucial that they have an accurate inventory count at all " "times. In such cases, the default scheduled date can be modified." msgstr "" +"Por padrão, a *data programada* para ajustes de inventário é sempre agendada" +" para o dia 31 de dezembro do ano atual. No entanto, para algumas empresas, " +"é fundamental ter uma contagem de estoque precisa em todos os momentos. " +"Nesses casos, a data padrão pode ser modificada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:185 msgid "" @@ -15313,28 +17446,39 @@ msgid "" "section, locate the :guilabel:`Annual Inventory Day and Month` setting, " "which includes a drop-down menu that is set to `31 December` by default." msgstr "" +"Para modificar a data agendada padrão, vá para :menuselection:`app " +"Inventário --> Configuração --> Definições`. Em seguida, na seção " +":guilabel:`Operações`, localize a configuração :guilabel:`Dia e mês do " +"inventário anual`, que inclui um menu suspenso definido como `31 de " +"dezembro` por padrão." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "" "Adjust the next inventory count date with the Annual Inventory Day and Month" " setting." msgstr "" +"Ajustar a data da próxima contagem de inventário com a configuração Dia e " +"mês do inventário anual." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:193 msgid "" "To change the day, click the :guilabel:`31`, and change it to a day within " "the range `1-31`, depending on the desired month of the year." msgstr "" +"Para alterar o dia, clique no :guilabel:`31` e altere-o para um dia dentro " +"do intervalo `1-31`, dependendo do mês do ano desejado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:199 msgid "" "Once all desired changes have been made, click :guilabel:`Save` to save all " "changes." msgstr "" +"Quando todas as alterações tiverem sido feitas, clique em :guilabel:`Salvar`" +" para salvar todas as alterações." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 msgid "Plan big inventory counts" -msgstr "" +msgstr "Planejar grandes contagens de estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 msgid "" @@ -15342,12 +17486,17 @@ msgid "" "in stock, first navigate to :menuselection:`Inventory app --> Operations -->" " Inventory Adjustments`." msgstr "" +"Para planejar grandes contagens de inventário, como uma contagem completa de" +" tudo o que está atualmente em estoque, primeiro navegue até " +":menuselection:`app Inventário --> Operações --> Ajustes de inventário`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:207 msgid "" "Then, select the desired products to be counted by clicking the checkbox on " "the far left of each product line." msgstr "" +"Em seguida, selecione os produtos a contar clicando na caixa de seleção na " +"extremidade esquerda de cada linha de produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:211 msgid "" @@ -15355,10 +17504,14 @@ msgid "" "checkbox at the very top of the table, in the header row next to the " ":guilabel:`Location` label. This selects **all** product lines." msgstr "" +"Para solicitar uma contagem de **todos** os produtos atualmente em estoque, " +"clique na caixa de seleção na parte superior da tabela, na linha de " +"cabeçalho ao lado do rótulo :guilabel:`Local`. Isso seleciona **todas** as " +"linhas de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 msgid "Request a count popup on inventory adjustments page." -msgstr "" +msgstr "Pop-up de solicitação de contagem na página de ajustes de estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:219 msgid "" @@ -15367,20 +17520,26 @@ msgid "" "Count` pop-up window to appear. From this pop-up, fill in the following " "information:" msgstr "" +"Quando todos os produtos desejados tiverem sido selecionados, clique no " +"botão :guilabel:`Solicitar contagem` na parte superior da página. Isso faz " +"com que uma janela pop-up :guilabel:`Solicitar contagem` seja exibida. Nessa" +" janela pop-up, preencha as seguintes informações:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 msgid ":guilabel:`Inventory Date`: the planned date of the count." -msgstr "" +msgstr ":guilabel:`Data do inventário`: a data planejada da contagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 msgid ":guilabel:`User`: the user responsible for the count." -msgstr "" +msgstr ":guilabel:`Usuário`: o usuário responsável pela contagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 msgid "" ":guilabel:`Accounting Date`: the date at which the inventory adjustment will" " be accounted." msgstr "" +":guilabel:`Data contábil`: a data em que o ajuste de estoque será " +"contabilizado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 msgid "" @@ -15389,25 +17548,36 @@ msgid "" "product line with the current value recorded in the database, select " ":guilabel:`Set Current Value`." msgstr "" +":guilabel:`Contagem`: para deixar a quantidade disponível em brnaco nas " +"linha de produto em branco, selecione :guilabel:`Deixar em branco`. Para " +"preencher previamente a quantidade disponível de cada linha de produto com o" +" valor atual registrado na base de dados, selecione :guilabel:`Definir valor" +" atual`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:230 msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." msgstr "" +"Por fim, quando estiver pronto, clique em :guilabel:`Confirmar` para " +"solicitar a contagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:233 msgid "" "In the Odoo *Barcode* app, users can only view inventory counts that are " "assigned to **them**, and are scheduled for **today** or **earlier**." msgstr "" +"No aplicativo *Código de barras* do Odoo, os usuários só podem visualizar as" +" contagens de inventário atribuídas a **eles** e programadas para **hoje** " +"ou **anteriormente**." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:237 msgid "" ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" msgstr "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 msgid "Create a second warehouse" -msgstr "" +msgstr "Criar um segundo armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 msgid "" @@ -15415,6 +17585,9 @@ msgid "" "Odoo, it is possible to set up multiple warehouses and transfer stored items" " between them." msgstr "" +"Um *armazém* é um edifício ou espaço físico onde os itens são armazenados. " +"No Odoo, é possível configurar vários armazéns e transferir itens " +"armazenados entre eles." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:8 msgid "" @@ -15423,16 +17596,22 @@ msgid "" " select :menuselection:`Configuration --> Warehouses`, then click " ":guilabel:`Create` and configure the form as follows:" msgstr "" +"Por padrão, a plataforma Odoo tem um armazém que já está configurado, com o " +"endereço definido como o endereço da empresa. Para criar um segundo, " +"selecione :menuselection:`Configuração --> Armazéns`, depois clique em " +":guilabel:`Criar` e configure o formulário da seguinte forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:12 msgid ":guilabel:`Warehouse`: the full name of the warehouse" -msgstr "" +msgstr ":guilabel:`Armazém`: o nome completo do armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 msgid "" ":guilabel:`Short Name`: the abbreviated code by which the warehouse is " "referred to; the short name for the default warehouse in Odoo is **WH**" msgstr "" +":guilabel:`Nome abreviado`: o código abreviado pelo qual o armazém é " +"referido; o nome abreviado padrão de armazéns no Odoo é **WH**" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 msgid "" @@ -15440,10 +17619,13 @@ msgid "" " the company that owns the Odoo database or the company of a customer or " "vendor" msgstr "" +":guilabel:`Empresa`: a empresa proprietária do armazém; isso pode ser " +"definido como a empresa proprietária da base de dados do Odoo ou a empresa " +"de um cliente ou fornecedor" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:17 msgid ":guilabel:`Address`: the address where the warehouse is located" -msgstr "" +msgstr ":guilabel:`Endereço`: o endereço onde o armazém está localizado" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:20 msgid "" @@ -15452,46 +17634,63 @@ msgid "" " :guilabel:`Warehouse` heading. For more information about routes and how " "they work in Odoo, see :ref:`Using Routes and Pull/Push Rules <use-routes>`." msgstr "" +"As opções abaixo só aparecerão se a caixa de seleção :guilabel:`Rotas com " +"várias etapas` estiver ativada em :menuselection:`Configuração --> " +"Definições` sob o título :guilabel:`Armazém`. Para obter mais informações " +"sobre rotas e como elas funcionam no Odoo, consulte :ref:`Como usar rotas e " +"regras de pull/push <use-routes>`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 msgid "" ":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and" " outgoing shipments should follow" msgstr "" +":guilabel:`Remessas recebidas/enviadas`: selecione as rotas que as remessas " +"recebidas/enviadas devem seguir" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:27 msgid "" ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied " "from this warehouse" msgstr "" +":guilabel:`Reposição de subcontratação`: permite que subcontratações sejam " +"repostas a partir desse armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:28 msgid "" ":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in " "this warehouse" msgstr "" +":guilabel:`Fabricar para repor`: permite que os itens sejam fabricados nesse" +" armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:29 msgid "" ":guilabel:`Manufacture`: select the route that should be followed when " "manufacturing goods inside the warehouse" msgstr "" +":guilabel:`Fabricar`: selecione a rota que deve ser seguida ao fabricar " +"mercadorias dentro do armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:31 msgid "" ":guilabel:`Buy to Resupply`: check the box to allow for purchased products " "to be delivered to the warehouse" msgstr "" +":guilabel:`Comprar para repor`: marque a caixa para permitir que os produtos" +" comprados sejam entregues no armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:33 msgid "" ":guilabel:`Resupply From`: select warehouses that can be used to resupply " "the warehouse being created" msgstr "" +":guilabel:`Repor de `: selecione os aramazéns que podem ser usados para " +"reabastecer o armazém que está sendo criado" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 msgid "A filled out form for creating a new warehouse." -msgstr "" +msgstr "Um formulário preenchido para a criação de um novo armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:41 msgid "" @@ -15501,16 +17700,23 @@ msgid "" " --> Settings` and click the checkbox under the :guilabel:`Warehouse` " "heading." msgstr "" +"A criação de um segundo armazém ativará automaticamente a configuração " +"*Locais de armazenamento*, que permite o rastreamento da localização dos " +"produtos em um depósito. Para alternar essa configuração, navegue até " +":menuselection:`Configuração --> Definições` e clique na caixa de seleção " +"sob o título :guilabel:`Armazém`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:46 msgid "" "After filling out the form, click :guilabel:`Save` and the new warehouse " "will be created." msgstr "" +"Depois de preencher o formulário, clique em :guilabel:`Salvar` e o novo " +"armazém será criado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 msgid "Add inventory to a new warehouse" -msgstr "" +msgstr "Adicionar inventário a um novo armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:51 msgid "" @@ -15521,12 +17727,20 @@ msgid "" " Inventory Adjustments`, and then click :guilabel:`Create`. The inventory " "adjustment form can then be filled out as follows:" msgstr "" +"Se for criado um novo armazém com inventário existente, as contagens de " +"estoque deverão ser adicionadas ao Odoo para que o estoque listado na base " +"de dados do Odoo reflita o que está no armazém físico. Para adicionar o " +"inventário a um novo armazém, navegue até :menuselection:`Inventário --> " +"Operações --> Inventário Ajustes` e clique em :guilabel:`Criar`. O " +"formulário de ajuste de estoque pode ser preenchido da seguinte forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:57 msgid "" ":guilabel:`Inventory Reference`: the name or code that the inventory " "adjustment can be referred to by" msgstr "" +":guilabel:`Referência do inventário`: o nome ou código pelo qual o ajuste de" +" estoque pode ser referenciado" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 msgid "" @@ -15534,12 +17748,18 @@ msgid "" "include the new warehouse and any locations within it that inventory will be" " added to" msgstr "" +":guilabel:`Locais`: os locais onde o inventário está armazenado; inclua o " +"novo armazém e qualquer local dentro dele aos quais o inventário será " +"adicionado" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:61 msgid "" ":guilabel:`Products`: include all products that will be added to inventory " "or leave blank to select any product during the next step" msgstr "" +":guilabel:`Produtos`: inclua todos os produtos que serão adicionados ao " +"inventário ou deixe em branco para selecionar qualquer produto durante a " +"próxima etapa" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:63 msgid "" @@ -15547,18 +17767,25 @@ msgid "" "zero; does not affect inventory adjustments for new warehouses since they " "have no existing inventory" msgstr "" +":guilabel:`Incluir produtos esgotados`: inclui produtos com quantidade zero;" +" não afeta os ajustes de estoque para novos armazéns, pois eles não têm " +"estoque existente" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:65 msgid "" ":guilabel:`Accounting Date`: the date used by accounting teams for " "bookkeeping related to the inventory" msgstr "" +":guilabel:`Data contábil`: a data usada pelas equipes de contabilidade para " +"a escrituração relacionada ao inventário" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:67 msgid "" ":guilabel:`Company`: the company that owns the inventory; can be set as the " "user's company or as a customer or vendor" msgstr "" +":guilabel:`Empresa`: a empresa proprietária do inventário; pode ser definida" +" como a empresa do usuário ou como um cliente ou fornecedor" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:69 msgid "" @@ -15567,10 +17794,14 @@ msgid "" "affect inventory adjustments for new warehouses since they have no existing " "inventory" msgstr "" +":guilabel:`Quantidades contadas`: escolha se as quantidades contadas dos " +"produtos que estão sendo adicionados devem ter como padrão o estoque " +"disponível ou zero; não afeta os ajustes de inventário para novos armazéns, " +"pois eles não têm estoque existente" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 msgid "A filled out form for an inventory adjustment." -msgstr "" +msgstr "Um formulário de ajuste de estoque preenchido." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:77 msgid "" @@ -15579,10 +17810,16 @@ msgid "" "adjustment. Add a new product by clicking on :guilabel:`Create` and then " "fill out the product line as follows:" msgstr "" +"Depois que o formulário estiver configurado corretamente, clique em " +":guilabel:`Começar inventário` para ir para a próxima página, onde os " +"produtos podem ser adicionados ao ajuste do inventário. Adicione um novo " +"produto clicando em :guilabel:`Criar` e, em seguida, preencha a linha do " +"produto da seguinte forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:81 msgid ":guilabel:`Product`: the product being added to inventory" msgstr "" +":guilabel:`Produto`: o produto que está sendo adicionado ao inventário" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 msgid "" @@ -15590,12 +17827,17 @@ msgid "" "the new warehouse; this can be set as the overall warehouse or a location " "within the warehouse" msgstr "" +":guilabel:`Local`: o local onde o produto está atualmente armazenado no novo" +" armazém; isso pode ser definido como o armazém emgeral ou um local dentro " +"dele" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:84 msgid "" ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the " "serial number used to identify it" msgstr "" +":guilabel:`Número de série/lote`: o lote ao qual o produto pertence ou o " +"número de série usado para identificá-lo" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:86 msgid "" @@ -15603,12 +17845,16 @@ msgid "" "location for which inventory is being adjusted; this should be zero for a " "new location or warehouse" msgstr "" +":guilabel:`Em mãos`: a quantidade total do produto armazenado no local cujo " +"estoque está sendo ajustado; deve ser zero para um novo local ou armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:88 msgid "" ":guilabel:`Counted`: the amount of the product that is being added to " "inventory" msgstr "" +":guilabel:`Contado`: a quantidade do produto que está sendo adicionada ao " +"estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:89 msgid "" @@ -15616,14 +17862,18 @@ msgid "" "values; this will automatically update to reflect the value entered in the " ":guilabel:`Counted` column" msgstr "" +":guilabel:`Diferença`: a diferença entre os valores de *Em mãos* e " +"*Contado*; isso será atualizado automaticamente para refletir o valor " +"inserido na coluna :guilabel:`Contado`" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 msgid ":guilabel:`UoM`: the unit of measure used for counting the product" -msgstr "" +msgstr ":guilabel:`UM`: a unidade de medida usada para contar o produto" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 msgid "Include a line for each product being added to inventory." msgstr "" +"Inclua uma linha para cada produto que está sendo adicionado ao estoque." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 msgid "" @@ -15633,10 +17883,15 @@ msgid "" " :guilabel:`Counted` column and the products added will appear in the " "inventory of the new warehouse." msgstr "" +"Depois de adicionar todos os produtos já armazenados no novo armazém, clique" +" em :guilabel:`Validar inventário` para concluir o ajuste de estoque. Os " +"valores na coluna :guilabel:`Em mãos` serão atualizados para refletir os " +"valores na coluna :guilabel:`Contado` e os produtos adicionados aparecerão " +"no inventário do novo armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 msgid "Resupply from another warehouse" -msgstr "" +msgstr "Repor de outro armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:5 msgid "" @@ -15646,6 +17901,11 @@ msgid "" "ordered to the central warehouse. Odoo allows the user to easily set which " "warehouse(s) can resupply another warehouse." msgstr "" +"Um caso de uso comum para vários armazéns é ter um armazém central que " +"reabasteça várias lojas e, nesse caso, cada loja é considerada um armazém " +"local. Quando uma loja deseja repor um produto, o produto é solicitado ao " +"armazém central. O Odoo permite que o usuário defina facilmente quais " +"armazéns podem reabastecer outro armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:13 msgid "" @@ -15653,16 +17913,22 @@ msgid "" "--> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-" "Step Routes`. Then, click :guilabel:`Save` to apply the setting." msgstr "" +"Para reabastecer a partir de outro depósito, primeiro vá para " +":menuselection:`Inventário --> Configuração --> Definições --> Armazém` e " +"ative :guilabel:`Rotas com várias etapas`. Em seguida, clique em " +":guilabel:`Salvar` para aplicar a configuração." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "Enable Multi-Step Routes in Inventory settings." -msgstr "" +msgstr "Habilitar rotas com várias etapas nas configurações do Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:21 msgid "" "View all the configured warehouses by going to :menuselection:`Inventory -->" " Configuration --> Warehouses`." msgstr "" +"Visualize todos os depósitos configurados acessando " +":menuselection:`Inventário --> Configuração --> Armazéns`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:24 msgid "" @@ -15670,6 +17936,9 @@ msgid "" "warehouse a name and a :guilabel:`Short Name`. Finally, click " ":guilabel:`Save` to finish creating the warehouse." msgstr "" +"Crie um novo armazém clicando em :guilabel:`Criar`. Em seguida, dê ao " +"armazém um nome e um :guilabel:`nome abreviado`. Por fim, clique em " +":guilabel:`Salvar` para concluir a criação do armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:27 msgid "" @@ -15682,14 +17951,21 @@ msgid "" ":guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can " "resupply this warehouse." msgstr "" +"Depois disso, volte à página :guilabel:`Armazém` e abra o armazém que será " +"reabastecido pelo outro. Em seguida, clique em :guilabel:`Editar`. Na aba " +":guilabel:`Configuração do armazém`, localize o campo :guilabel:`Repor de` e" +" marque a caixa ao lado do nome do segundo armazém. Se o armaźem puder ser " +"reabastecido por mais de um armazém, certifique-se de marcar as caixas deles" +" também. Por fim, clique em :guilabel:`Salvar` para aplicar a configuração. " +"Agora, o Odoo sabe quais armazéns podem reabastecer este." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "Supply one warehouse with another in the Warehouse Configuration tab." -msgstr "" +msgstr "Reabastecer um armazém com outro na aba Configuração do armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:39 msgid "Set route on a product" -msgstr "" +msgstr "Definir rotas em um produto" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:41 msgid "" @@ -15700,11 +17976,20 @@ msgid "" " with a reordering rule or the make to order (MTO) route to replenish stock " "by moving the product from one warehouse to another." msgstr "" +"Depois de configurar de quais armazéns a reposição deve ser feita, uma nova " +"rota fica disponível em todos os formulários de produtos. A nova rota " +"aparece como :guilabel:`Repor produto de [nome do armazém]` na aba " +":guilabel:`Inventário` em um formulário de produto. Use a rota " +":guilabel:`Repor produto de [nome do armazém]` com uma regra de reposição ou" +" a rota Reposição sob demanda (MTO) para reabastecer o estoque, movendo o " +"produto de um armazém para outro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "" "Route setting which enables a product to resupplied from a second warehouse." msgstr "" +"Configuração de rota que permite que um produto seja reposto de um segundo " +"armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:51 msgid "" @@ -15716,6 +18001,13 @@ msgid "" " The product move from the second warehouse to the main warehouse is fully " "tracked in Odoo." msgstr "" +"Quando a regra de reposição de um produto é acionada e o produto tem a rota " +":guilabel:`Repor produto de [nome do armazém]` definida, o Odoo cria " +"automaticamente duas separações. Uma separação é uma *ordem de entrega* do " +"segundo armazém, que contém todos os produtos necessários, e a segunda " +"separação é um *recebimento* com os mesmos produtos para o armazém " +"principal. A movimentação do produto do segundo armazém para o armazém " +"principal é totalmente rastreada no Odoo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:57 msgid "" @@ -15723,20 +18015,25 @@ msgid "" "Document` is the product's reordering rule. The location between the " "delivery order and the receipt is a transit location." msgstr "" +"Nos registros de separação/transferência criados pelo Odoo, o " +":guilabel:`Documento de origem` é a regra de reposição do produto. O local " +"entre a ordem de entrega e o recibo é um local de trânsito." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "" "A reordering rule automatically creates two receipts for stock between " "warehouses." msgstr "" +"Uma regra de reposição cria automaticamente dois recebimentos para o estoque" +" entre armazéns." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "A warehouse order for resupplying one warehouse's stock with another." -msgstr "" +msgstr "Um pedido de armazém para repor o estoque de um armazém com outro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 msgid "A receipt for stock received to one warehouse from another." -msgstr "" +msgstr "Um recebimento de estoque de um armazém para outro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 msgid "Locations" @@ -15747,6 +18044,8 @@ msgid "" "A *location* is a specific space within a warehouse. This can be a shelf, " "room, aisle, etc. There are three types of locations in Odoo:" msgstr "" +"Um *local* é um espaço específico em um armazém. Pode ser uma prateleira, " +"uma sala, um corredor, etc. Há três tipos de locais no Odoo:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 msgid "" @@ -15755,12 +18054,18 @@ msgid "" "shelf, or an area where operations take place, like loading and unloading " "bays." msgstr "" +"*Locais físicos* são espaços dentro de um armazém de propriedade da empresa " +"do usuário. Podem ser uma área onde os itens são armazenados, como um " +"corredor ou uma prateleira, ou uma área onde as operações ocorrem, como " +"baias de carga e descarga." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 msgid "" "*Partner locations* are the same as physical locations except that they " "exist within the warehouse of a customer or vendor." msgstr "" +"*Os locais de parceiros* são iguais aos locais físicos, exceto pelo fato de " +"existirem no armazém de um cliente ou fornecedor." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:13 msgid "" @@ -15769,6 +18074,10 @@ msgid "" "not yet entered inventory, like products that are on the way to a warehouse," " or items that are no longer in inventory due to loss or other factors." msgstr "" +"*Locais virtuais* são locais que não existem fisicamente, mas onde os itens " +"que não estão no estoque podem ser colocados. Podem ser itens que ainda não " +"entraram no estoque, como produtos que estão a caminho de um armazém, ou " +"itens que não estão mais no estoque devido a perdas ou outros fatores." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:19 msgid "" @@ -15777,10 +18086,15 @@ msgid "" "--> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable " "the :guilabel:`Storage Locations` checkbox." msgstr "" +"Para usar os locais, a configuração :guilabel:`Locais de armazenamento` deve" +" ser ativada. Para fazer isso, navegue até :menuselection:`Inventário --> " +"Configuração --> Definições`, role para baixo até o título " +":guilabel:`Armazém` e ative a caixa de seleção :guilabel:`Locais de " +"armazenamento`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 msgid "Create a new location inside a warehouse" -msgstr "" +msgstr "Criar um novo local em um armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 msgid "" @@ -15788,45 +18102,59 @@ msgid "" ":menuselection:`Configuration --> Locations --> Create`. The new location " "form can then be configured as follows:" msgstr "" +"A partir do aplicativo :menuselection:`Inventário`, selecione " +":menuselection:`Configuração --> Locais --> Criar`. O novo formulário de " +"local pode então ser configurado da seguinte forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:29 msgid "" ":guilabel:`Location Name`: the name that will be used to reference the " "location" msgstr "" +":guilabel:`Nome do local`: o nome que será usado para referenciar o local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:30 msgid "" ":guilabel:`Parent Location`: the location or warehouse that the new location" " exists within" msgstr "" +":guilabel:`Local primário`: o local ou armazém no qual o novo local existe" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 msgid "" ":guilabel:`Location Type`: choose the category that the location belongs to" msgstr "" +":guilabel:`Tipo de local`: escolha a categoria à qual o local pertence" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 msgid "" ":guilabel:`Company`: the company that owns the warehouse that the location " "is inside of" msgstr "" +":guilabel:`Empresa`: a empresa proprietária do armazém no qual o local está " +"localizado" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 msgid "" ":guilabel:`Is a Scrap Location?`: check this box to allow for " "scrapped/damaged goods to be stored in this location" msgstr "" +":guilabel:`É um local de sucata?`: marque essa caixa para permitir que " +"mercadorias sucateadas/danificadas sejam armazenadas nesse local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 msgid "" ":guilabel:`Is a Return Location?`: check this box to allow products to be " "returned to this location" msgstr "" +":guilabel:`É um local de devolução?`: marque essa caixa para permitir que os" +" produtos sejam devolvidos a esse local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 msgid ":guilabel:`Barcode`: the barcode number assigned to the location" msgstr "" +":guilabel:`Código de barras`: o número do código de barras atribuído ao " +"local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 msgid "" @@ -15834,14 +18162,17 @@ msgid "" "<../advanced_operations_warehouse/removal>` for how items should be taken " "from inventory" msgstr "" +":guilabel:`Estratégia de remoção`: a :doc:`estratégia " +"<.../advanced_operations_warehouse/removal>` de como os itens devem ser " +"retirados do estoque" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst-1 msgid "The form for creating a new location." -msgstr "" +msgstr "Formulário para criar um novo local." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 msgid "Create location hierarchies" -msgstr "" +msgstr "Criar hierarquias de local" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 msgid "" @@ -15851,6 +18182,10 @@ msgid "" "within it, allowing for the creation of a virtually infinite hierarchical " "structure." msgstr "" +"A configuração *Local primário* no formulário de novo local permite que um " +"local exista em um armazém ou em outro local. Cada local pode servir como um" +" local primário, e cada local primário pode ter vários locais dentro dele, " +"permitindo a criação de uma estrutura hierárquica praticamente infinita." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 msgid "" @@ -15858,6 +18193,9 @@ msgid "" "aisle, which is located within a room, which is located within the overall " "warehouse." msgstr "" +"A hierarquia de local pode ser organizada de modo que uma prateleira esteja " +"localizada em um corredor, que está localizado em uma sala, que está " +"localizada no armazém geral." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 msgid "" @@ -15866,10 +18204,14 @@ msgid "" "as the parent of the shelf. This can be adapted to a hierarchy of any " "magnitude." msgstr "" +"Para criar a hierarquia de local no exemplo acima, defina o armazém como o " +"local primário da sala, a sala como o o primário do corredor e o corredor " +"como o primário da prateleira. Isso pode ser adaptado a uma hierarquia de " +"qualquer magnitude." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 msgid "Routes and Pull/Push Rules" -msgstr "" +msgstr "Rotas e regras Pull/Push" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 msgid "" @@ -15877,6 +18219,9 @@ msgid "" "should be purchased/manufactured, delivered to distribution centers, and " "made available to the retail channel." msgstr "" +"Na gestão de estoques, a estratégia da cadeia de suprimentos determina " +"quando os produtos devem ser comprados/fabricados, entregues aos centros de " +"distribuição e disponibilizados ao canal de varejo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:11 msgid "" @@ -15885,10 +18230,14 @@ msgid "" "configured, the Inventory app can automatically generate transfers following" " the configured push/pull rules." msgstr "" +"No Odoo, a estratégia da cadeia de suprimentos de um produto pode ser " +"configurada usando *Rotas*, que apresentam *Regras de push e pull*. Quando " +"tudo estiver configurado corretamente, o aplicativo Inventário poderá gerar " +"transferências automaticamente seguindo as regras push/pull configuradas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:16 msgid "Inside the warehouse" -msgstr "" +msgstr "Dentro do armazém" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:18 msgid "" @@ -15897,10 +18246,16 @@ msgid "" "products go through all these locations. As the products move through the " "locations, each location triggers the products' specified route and rules." msgstr "" +"Em um armazém genérico, há docas de recebimento, uma área de controle de " +"qualidade, locais de armazenamento, áreas de separação e embalagem e docas " +"de expedição. Todos os produtos passam por todos esses locais. À medida que " +"os produtos passam pelos locais, cada local aciona a rota e as regras " +"especificadas para os produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a generic warehouse with stock and quality control area." msgstr "" +"Vista de um armazém genérico com estoque e área de controle de qualidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:27 msgid "" @@ -15911,10 +18266,17 @@ msgid "" " the manufacturing process), while others are directly stored in their " "respective locations." msgstr "" +"Neste exemplo, caminhões de fornecedores descarregam paletes de produtos " +"encomendados nas docas de recebimento. Em seguida, os operadores escaneiam " +"os produtos na área de recebimento. Dependendo da rota e das regras do " +"produto, alguns desses produtos são enviados para uma área de controle de " +"qualidade (por exemplo, produtos que são componentes usados no processo de " +"fabricação), enquanto outros são armazenados diretamente em seus respectivos" +" locais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a generic push to rule when receiving products." -msgstr "" +msgstr "Visualização de uma regra de envio genérica ao receber produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 msgid "" @@ -15925,20 +18287,30 @@ msgid "" " and conveyors bring them close to the shipping docks, ready to be delivered" " to customers." msgstr "" +"Aqui está um exemplo de uma rota de atendimento. Pela manhã, os itens são " +"coletados para todos os pedidos que precisam ser preparados durante o dia. " +"Esses itens são retirados dos locais de armazenamento e movidos para a área " +"de separação, perto de onde os pedidos são embalados. Em seguida, os pedidos" +" são embalados em suas respectivas caixas e as esteiras transportadoras os " +"levam para perto das docas de expedição, prontos para serem entregues aos " +"clientes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a generic pull from rule when preparing deliveries." -msgstr "" +msgstr "Visualização de um pull genérico da regra ao preparar entregas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:47 msgid "Pull rules" -msgstr "" +msgstr "Regras de pull" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:49 msgid "" "With *Pull Rules*, a demand for some products triggers procurements, while " "*Push Rules* are triggered by products arriving in a specific location." msgstr "" +"Com as *regras de pull*, a demanda por alguns produtos aciona as aquisições," +" enquanto as *regras de push* são acionadas pela chegada de produtos em um " +"local específico." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:52 msgid "" @@ -15947,6 +18319,10 @@ msgid "" "triggered by a need, Odoo looks for a pull rule defined on the *Customer " "Location*." msgstr "" +"As regras de pull são usadas para atender a um pedido de vendas. O Odoo gera" +" uma demanda no *Local do cliente* para cada produto no pedido. Como as " +"regras pull são acionadas por demanda, o Odoo procura por uma regra de pull " +"definida no *Local do cliente*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:56 msgid "" @@ -15954,6 +18330,9 @@ msgid "" "the *Shipping Area* to the *Customer Location* is found, and a transfer " "between the two locations is created." msgstr "" +"Nesse caso, uma regra de pull de \"ordem de entrega\" que transfere produtos" +" da *Área de expedição* para o *Local do cliente* é encontrada, e uma " +"transferência entre os dois locais é criada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:59 msgid "" @@ -15963,6 +18342,11 @@ msgid "" "triggered until a transfer between the *Stock* and the *Picking Area* is " "created." msgstr "" +"Em seguida, o Odoo encontra outra regra de pull que tenta atender à " +"necessidade da *Área de expedição*: a regra de \"embalagem\" que transfere " +"produtos da *Área de embalagem* para a *Área de expedição*. Por fim, outras " +"regras de pull são acionadas até que uma transferência entre o *Estoque* e a" +" *Área de separação* seja criada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:65 msgid "" @@ -15972,10 +18356,15 @@ msgid "" "transfers in the opposite order: first the picking, then the packing, and " "finally the delivery order." msgstr "" +"Todas essas transferências de produtos são geradas automaticamente pelo Odoo" +" com base nas regras de pull, começando do final (o local do cliente) e indo" +" para trás (o armazém de estoque). Durante o trabalho, o operador processa " +"essas transferências na ordem oposta: primeiro a separação, depois a " +"embalagem e, por fim, a ordem de entrega." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:71 msgid "Push rules" -msgstr "" +msgstr "Regras de push" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:73 msgid "" @@ -15984,6 +18373,11 @@ msgid "" "products arrive in a specific location. Push rules basically say: \"when a " "product arrives at a specific location, move it to another location.\"" msgstr "" +"Por outro lado, as *regras de push* são muito mais fáceis de entender. Em " +"vez de gerar documentos com base nas necessidades, elas são acionadas em " +"tempo real quando os produtos chegam em um local específico. As regras de " +"push basicamente dizem: \"quando um produto chegar em um local específico, " +"mova-o para outro local.\"" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:77 msgid "" @@ -15992,6 +18386,10 @@ msgid "" "applied to different products, the user can assign different storage " "locations for different products." msgstr "" +"Um exemplo de regra de psuh seria: quando um produto chegar na *Área de " +"recebimento*, mova-o para o *Local de armazenamento*. Como diferentes regras" +" de envio podem ser aplicadas a diferentes produtos, o usuário pode atribuir" +" diferentes locais de armazenamento para diferentes produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:81 msgid "" @@ -15999,12 +18397,17 @@ msgid "" " the *Quality Control Area*. Then, once the quality check is done, move them" " to their *Storage Location*." msgstr "" +"Outra regra de envio poderia ser: quando os produtos chegarem a um local, " +"mova-os para a *Área de controle de qualidade*. Depois, quando a verificação" +" de qualidade for concluída, mova-os para o *Local de armazenamento*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:85 msgid "" "Push rules can only be triggered if there are no pull rules that have " "already generated the product transfers." msgstr "" +"As regras de push só podem ser acionadas se não houver regras de pull que já" +" tenham gerado as transferências de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:89 msgid "" @@ -16014,36 +18417,48 @@ msgid "" "grouped in one transfer, whereas the packing operation respects the grouping" " per customer order." msgstr "" +"Conjuntos de regras de push/pull como essas são chamados de *Rotas*. O " +"agrupamento na regra decide se os produtos serão agrupados na mesma " +"transferência ou não. Por exemplo, durante a operação de separação, todos os" +" pedidos e seus produtos são agrupados em uma única transferência, enquanto " +"a operação de embalagem respeita o agrupamento por pedido do cliente." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:97 msgid "Use routes and rules" -msgstr "" +msgstr "Usar rotas e regras" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:99 msgid "" "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you " "manage advanced route configurations such as:" msgstr "" +"Como as *Rotas* são uma coleção de *Regras de push e pull*, o Odoo o ajuda a" +" gerenciar configurações avançadas de rotas, como:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 msgid "Manage product manufacturing chains." -msgstr "" +msgstr "Gerenciar cadeias de fabricação de produtos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 msgid "Manage default locations per product." -msgstr "" +msgstr "Gerenciar locais padrão por produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:104 msgid "" "Define routes within the stock warehouse according to business needs, such " "as quality control, after-sales services, or supplier returns." msgstr "" +"Definir rotas dentro do armazém de estoque de acordo com as necessidades " +"comerciais, como controle de qualidade, serviços pós-venda ou devoluções de " +"fornecedores." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:106 msgid "" "Help rental management by generating automated return moves for rented " "products." msgstr "" +"Auxiliar no gerenciamento de locações gerando movimentações de devolução " +"automatizadas para produtos alugados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:108 msgid "" @@ -16052,26 +18467,34 @@ msgid "" "the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` " "feature and click :guilabel:`Save`." msgstr "" +"Para configurar uma rota para um produto, primeiro, abra o aplicativo " +":guilabel:`Inventário` e vá para :menuselection:`Configuração --> " +"Definições`. Em seguida, na seção :guilabel:`Armazém`, ative o recurso " +":guilabel:`Rotas com várias etapas` e clique em :guilabel:`Salvar`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "Activate the Multi-Step Routes feature in Odoo Inventory." -msgstr "" +msgstr "Ativar o recurso Rotas com várias etapas no Odoo Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:117 msgid "" "The :guilabel:`Storage Locations` feature is automatically activated with " "the :guilabel:`Multi-Step Routes` feature." msgstr "" +"O recurso :guilabel:`Locais de armazenamento` é ativado automaticamente com " +"o recurso :guilabel:`Rotas com várias etapas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:120 msgid "" "Once this first step is completed, the user can use pre-configured routes " "that come with Odoo, or they can create custom routes." msgstr "" +"Uma vez concluída essa primeira etapa, o usuário pode usar rotas pré-" +"configuradas que vêm com o Odoo ou pode criar rotas personalizadas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:124 msgid "Pre-configured routes" -msgstr "" +msgstr "Rotas pré-configuradas" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:126 msgid "" @@ -16081,10 +18504,15 @@ msgid "" "pre-configured routes for :guilabel:`Incoming Shipments` and " ":guilabel:`Outgoing Shipments`." msgstr "" +"Para acessar as rotas pré-configuradas do Odoo, vá para " +":menuselection:`Inventário --> Configuração --> Armazéns`. Em seguida, abra " +"um formulário de armazém. Na aba :guilabel:`Configuração do armazém`, o " +"usuário pode visualizar as rotas pré-configuradas do armazém para " +":guilabel:`Remessas recebidas` e :guilabel:`Remessas enviadas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "A preconfigured warehouse in Odoo Inventory." -msgstr "" +msgstr "Um armnazém pré-configurado no Odoo Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:135 msgid "" @@ -16094,10 +18522,16 @@ msgid "" " set, head to :menuselection:`Inventory --> Configuration --> Routes` to see" " the specific routes that Odoo generated." msgstr "" +"Algumas rotas mais avançadas, como separar-embalar-enviar, também estão " +"disponíveis. O usuário pode selecionar a rota que melhor atenda às suas " +"necessidades comerciais. Depois que as rotas :guilabel:`Remessas recebidas` " +"e :guilabel:`Remessas enviadas` forem definidas, vá para " +":menuselection:`Inventário --> Configuração --> Rotas` para ver as rotas " +"específicas que o Odoo gerou." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of all the preconfigured routes Odoo offers." -msgstr "" +msgstr "Visualização de todas as rotas pré-configuradas que o Odoo oferece." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:144 msgid "" @@ -16108,11 +18542,19 @@ msgid "" "environments; for example, a user can have a company and warehouse in " "Country A and a second company and warehouse in Country B." msgstr "" +"Na página :guilabel:`Rotas`, clique em uma rota para abrir o formulário de " +"rota. No formulário de rota, o usuário pode ver em quais locais a rota é " +":guilabel:`Aplicável`. O usuário também pode definir a rota para ser " +"aplicada somente em uma :guilabel:`empresa` específica. Isso é útil para " +"ambientes com várias empresas; por exemplo, um usuário pode ter uma empresa " +"e um armazém no País A e uma segunda empresa e um armazém no País B." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "View of a route example applicable on product categories and warehouses." msgstr "" +"Visualização de um exemplo de rota aplicável a categorias de produtos e " +"armazéns." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:154 msgid "" @@ -16121,10 +18563,14 @@ msgid "" ":guilabel:`Action`, a :guilabel:`Source Location`, and a " ":guilabel:`Destination Location`." msgstr "" +"Na parte inferior do formulário de rota, o usuário pode visualizar as " +":guilabel:`regras` específicas para a rota. Cada :guilabel:`regra` tem uma " +":guilabel:`ação`, um :guilabel:`local de origem` e um :guilabel:`local de " +"destino`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "An example of rules with push & pull actions in Odoo Inventory." -msgstr "" +msgstr "Um exemplo de regras com ações push e pull no Odoo Inventário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:163 msgid "Custom Routes" @@ -16137,10 +18583,14 @@ msgid "" "this route can be selected. A route can be applicable on a combination of " "places." msgstr "" +"Para criar uma rota personalizada, vá para :menuselection:`Inventário --> " +"Configuração --> Rotas` e clique em :guilabel:`Criar`. Em seguida, escolha " +"os locais onde essa rota pode ser selecionada. Uma rota pode ser aplicável " +"em uma combinação de locais." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a pick-pack-ship route." -msgstr "" +msgstr "Visualização de uma rota separar-embalar-enviar." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:173 msgid "" @@ -16148,6 +18598,9 @@ msgid "" "useful ones and adapt each route accordingly. Then, configure the " ":guilabel:`Rules` of the route." msgstr "" +"Cada local tem um comportamento diferente, portanto, é importante marcar " +"apenas os úteis e adaptar cada rota de acordo. Em seguida, configure as " +":guilabel:`regras` da rota." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:176 msgid "" @@ -16157,6 +18610,12 @@ msgid "" "select the product category and open the form. Next, click :guilabel:`Edit` " "and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." msgstr "" +"Se a rota for aplicável em uma categoria de produto, a rota ainda precisará " +"ser definida manualmente no formulário de categoria de produto, acessando " +":menuselection:`Inventário --> Configuração --> Categorias de produtos`. Em " +"seguida, selecione a categoria de produto e abra o formulário. Em seguida, " +"clique em :guilabel:`Editar` e, na seção :guilabel:`Logística`, defina a " +"seção :guilabel:`Rotas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:181 msgid "" @@ -16165,10 +18624,14 @@ msgid "" "helpful if the business uses the dropshipping process for all the products " "from the same category." msgstr "" +"Ao aplicar a rota em uma categoria de produto, todas as regras configuradas " +"na rota são aplicadas a **todos** os produtos da categoria. Isso pode ser " +"útil se a empresa usar o processo de envio direto para todos os produtos da " +"mesma categoria." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a route applied to the \"all\" product category." -msgstr "" +msgstr "Visualização de uma rota aplicada à categoria de produtos \"todos\"." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:189 msgid "" @@ -16177,11 +18640,16 @@ msgid "" "warehouse that meet the conditions of the route's rules will then follow " "that route." msgstr "" +"O mesmo comportamento se aplica aos armazéns. Se a rota puder ser aplicada a" +" :guilabel:`Armazéns`, todas as transferências que ocorrerem dentro do " +"armazém escolhido e que atenderem às condições das regras da rota seguirão " +"essa rota." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "View of the warehouse drop-down menu when selecting applicable on warehouse." msgstr "" +"Visualização do menu suspenso do armazém ao selecionar aplicável no armazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:197 msgid "" @@ -16189,6 +18657,9 @@ msgid "" "less the opposite. The route must be manually chosen when creating a " "quotation. This is useful if some products go through different routes." msgstr "" +"Se a rota for aplicável em :guilabel:`Linhas do pedido de venda`, é mais ou " +"menos o contrário. A rota deve ser escolhida manualmente ao criar uma " +"cotação. Isso é útil se alguns produtos passarem por rotas diferentes." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:201 msgid "" @@ -16196,10 +18667,15 @@ msgid "" "quotation/sales order. Then, the route can be chosen on each line of the " "quotation/sales order." msgstr "" +"Lembre-se de alternar a visibilidade da coluna :guilabel:`Rota` na " +"cotação/pedido de venda. Em seguida, a rota pode ser escolhida em cada linha" +" da cotação/pedido de venda." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of the menu allowing to add new lines to sales orders." msgstr "" +"Visualização do menu que permite adicionar novas linhas aos pedidos de " +"vendas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:208 msgid "" @@ -16207,6 +18683,9 @@ msgid "" "or less like the product categories: once selected, the route must be " "manually set on the product form." msgstr "" +"Por fim, há rotas que podem ser aplicadas a produtos. Elas funcionam mais ou" +" menos como as categorias de produtos: uma vez selecionada, a rota deve ser " +"definida manualmente no formulário do produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:211 msgid "" @@ -16215,14 +18694,19 @@ msgid "" ":guilabel:`Inventory` tab and under the :guilabel:`Operations` section, " "select the :guilabel:`Routes`." msgstr "" +"Para definir uma rota em um produto, vá para :menuselection:`Inventário --> " +"Produtos --> Produtos` e selecione o produto desejado. Em seguida, vá para a" +" aba :guilabel:`Inventário` e, na seção :guilabel:`Operações`, selecione a " +"seção :guilabel:`Rotas`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of a product form, where the route must be selected." msgstr "" +"Visualização de um formulário de produto, onde a rota deve ser selecionada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:220 msgid "Rules must be set on the route in order for the route to work." -msgstr "" +msgstr "As regras devem ser definidas na rota para que ela funcione." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:223 msgid "Rules" @@ -16235,10 +18719,15 @@ msgid "" " route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` " "section, click on :guilabel:`Add a line`." msgstr "" +"As regras são definidas no formulário de rota. Primeiro, vá para " +":menuselection:`Inventário --> Configuração --> Rotas` e abra o formulário " +"de rota em questão. Em seguida, clique em :guilabel:`Editar` e, na seção " +":guilabel:`Regras`, clique em :guilabel:`Adicionar uma linha`." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of the rules menu, where it is possible to add new rules." msgstr "" +"Visualização do menu de regras, onde é possível adicionar novas regras." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:233 msgid "" @@ -16246,6 +18735,9 @@ msgid "" "*Pull* rules, others are also available. Each rule has an " ":guilabel:`Action`:" msgstr "" +"As regras disponíveis acionam várias ações. Se o Odoo oferece regras de " +"*push* e *pull*, outras também estão disponíveis. Cada regra tem uma " +":guilabel:`ação`:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:236 msgid "" @@ -16255,6 +18747,11 @@ msgid "" "appears in the destination location, Odoo generates a picking to fulfill " "this need." msgstr "" +":guilabel:`Pull de`: essa regra é acionada por uma necessidade do produto em" +" um local específico. A demanda pode vir de um pedido de vendas que está " +"sendo validado ou de uma ordem de produção que requer um componente " +"específico. Quando a necessidade aparece no local de destino, o Odoo gera " +"uma separação para atender a essa necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:240 msgid "" @@ -16263,6 +18760,10 @@ msgid "" "the source location, Odoo generates a picking to move those products to the " "destination location." msgstr "" +":guilabel:`Push para`: essa regra é acionada pela chegada de alguns produtos" +" no local de origem definido. No caso de o usuário mover produtos para o " +"local de origem, o Odoo gera uma separação para mover esses produtos para o " +"local de destino." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:243 msgid "" @@ -16273,30 +18774,45 @@ msgid "" "is triggered to fulfill it. Once the second need is fulfilled, the products " "are pushed to the destination location and all the needs are fulfilled." msgstr "" +":guilabel:`Pull e Push`: essa regra permite a geração de separações nas duas" +" situações explicadas acima. Isso significa que, quando os produtos são " +"necessários em um local específico, é criada uma transferência do local " +"anterior para atender a essa necessidade. Isso cria uma necessidade no local" +" anterior e uma regra é acionada para atendê-la. Quando a segunda " +"necessidade é atendida, os produtos são transferidos para o local de destino" +" e todas as necessidades são atendidas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:248 msgid "" ":guilabel:`Buy`: when products are needed at the destination location, a " "request for quotation is created to fulfill the need." msgstr "" +":guilabel:`Comprar`: quando os produtos são necessários no local de destino," +" uma solicitação de cotação é criada para atender à necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:250 msgid "" ":guilabel:`Manufacture`: when products are needed in the source location, a " "manufacturing order is created to fulfill the need." msgstr "" +":guilabel:`Fabricar`: quando os produtos são necessários no local de origem," +" uma ordem de produção é criada para atender à necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" "zone." msgstr "" +"Visão geral de uma regra \"Pull de\" que cria uma transferência entre o " +"estoque e a zona de embalagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:258 msgid "" "The :guilabel:`Operation Type` must also be defined on the rule. This " "defines which kind of picking is created from the rule." msgstr "" +"O :guilabel:`Tipo de operação` também deve ser definido na regra. Isso " +"define que tipo de separação é criado a partir da regra." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:261 msgid "" @@ -16304,18 +18820,27 @@ msgid "" ":guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The " ":guilabel:`Supply Method` defines what happens at the source location:" msgstr "" +"Se a :guilabel:`ação` da regra for definida como :guilabel:`Pull de` ou " +":guilabel:`Pull e Push`, um :guilabel:`método de abastecimento` deverá ser " +"definido. O :guilabel:`método de abastecimento` define o que acontece no " +"local de origem:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:265 msgid "" ":guilabel:`Take From Stock`: the products are taken from the available stock" " of the source location." msgstr "" +":guilabel:`Retirar do estoque`: os produtos são retirados do estoque " +"disponível do local de origem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:267 msgid "" ":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to " "bring the products to the source location. The available stock is ignored." msgstr "" +":guilabel:`Acionar outra regra`: o sistema tenta encontrar uma regra de " +"estoque para levar os produtos ao local de origem. O estoque disponível é " +"ignorado." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:269 msgid "" @@ -16324,6 +18849,10 @@ msgid "" " is no stock available, the system tries to find a rule to bring the " "products to the source location." msgstr "" +":guilabel:`Retirar do estoque, se indisponível acionar outra regra`: os " +"produtos são retirados do estoque disponível do local de origem. Se não " +"houver estoque disponível, o sistema tentará encontrar uma regra para levar " +"os produtos ao local de origem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 msgid "" @@ -16331,22 +18860,30 @@ msgid "" "the chain's pickings is rescheduled. In case you decide to **Propagate " "Rescheduling**, the next move is also to be rescheduled." msgstr "" +"Na seção *Agendamento*, é possível determinar como o Odoo se comporta quando" +" uma das separações da cadeia é reagendada. Caso você decida **propagar o " +"reagendamento**, a próxima movimentação também será reagendada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:277 msgid "" "If you prefer having the choice to reschedule the next move, you can decide " "to receive an alert in the form of a *next activity*." msgstr "" +"Se preferir ter a opção de reagendar a próxima ação, você pode optar por " +"receber um alerta na forma de uma *próxima atividade*." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 msgid "Sample full route flow" -msgstr "" +msgstr "Exemplo de fluxo de rota completo" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:283 msgid "" "In this example, let's use a custom *Pick - Pack - Ship* route to try a full" " flow with an advanced custom route." msgstr "" +"Neste exemplo, vamos usar uma rota personalizada *Separar - Embalar - " +"Enviar* para experimentar um fluxo completo com uma rota personalizada " +"avançada." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:286 msgid "" @@ -16354,6 +18891,9 @@ msgid "" " three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply " "Methods` for each rule are the following:" msgstr "" +"Primeiro, uma rápida olhada nas regras da rota e em seus métodos de " +"fornecimento. Há três regras, todas :guilabel:`Pull de`. Os " +":guilabel:`métodos dee abastecimento` de cada regra são os seguintes:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:289 msgid "" @@ -16362,6 +18902,10 @@ msgid "" ":guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from " ":guilabel:`WH/Stock` to fulfill the need." msgstr "" +":guilabel:`Retirar do estoque`: Quando produtos são necessários na " +":guilabel:`WH/Packing Zone`, *separações* (transferências internas da " +":guilabel:`WH/Stock` para a :guilabel:`WH/Packing Zone`) são criadas no " +":guilabel:`WH/Stock` para atender à necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:292 msgid "" @@ -16370,6 +18914,10 @@ msgid "" ":guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from " ":guilabel:`WH/Packing Zone` to fulfill the need." msgstr "" +":guilabel:`Acionar outra regra`: Quando produtos são necessários em " +":guilabel:`WH/Output`, *embalagens* (transferências internas de " +":guilabel:`WH/Packing Zone` para :guilabel:`WH/Output`) são criadas a partir" +" de :guilabel:`WH/Packing Zone` para atender à necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 msgid "" @@ -16377,20 +18925,28 @@ msgid "" ":guilabel:`Partner Locations/Customers`, *delivery orders* are created from " ":guilabel:`WH/Output` to fulfill the need." msgstr "" +":guilabel:`Acionar outra regra`: Quando produtos são necessários em " +":guilabel:`Locais de parceiros/clientes`, *ordens de entrega* são criadas a " +"partir de :guilabel:`WH/Output` para atender à necessidade." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "Overview of all the transfers created by the pick - pack - ship route." msgstr "" +"Visão geral de todas as transferências criadas pela rota separar - embarar -" +" enviar." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 msgid "" "This means that, when a customer orders products that have a *pick - pack - " "ship* route set on it, a delivery order is created to fulfill the order." msgstr "" +"Isso significa que, quando um cliente faz um pedido de produtos que têm uma " +"rota *separar - embalar - enviar* definida, um pedido de entrega é criado " +"para atender ao pedido." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of the operations created by a pull from transfer." -msgstr "" +msgstr "Visualização das operações criadas por uma transferência \"pull de\"." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 msgid "" @@ -16398,23 +18954,33 @@ msgid "" "status is not the same. The status will be :guilabel:`Waiting Another " "Operation` if the previous transfer in the list is not done yet." msgstr "" +"Se o documento de origem de várias transferências for o mesmo pedido de " +"vendas, o status não será o mesmo. O status será :guilabel:`Aguardando outra" +" operação` se a transferência anterior na lista ainda não tiver sido " +"concluída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "View of the transfers' various statuses at the beginning of the process." msgstr "" +"Visualização dos vários status das transferências no início do processo." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:319 msgid "" "To prepare the delivery order, packed products are needed at the output " "area, so an internal transfer is requested from the packing zone." msgstr "" +"Para preparar a ordem de entrega, é necessário que os produtos embalados " +"estejam na área de saída, portanto, uma transferência interna é solicitada " +"da zona de embalagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "View of the detailed operations for a transfer between the packing and " "output zones." msgstr "" +"Visualização das operações detalhadas de uma transferência entre as zonas de" +" embalagem e saída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:326 msgid "" @@ -16422,12 +18988,17 @@ msgid "" "internal transfer is requested to the stock and employees can gather the " "required products from the warehouse." msgstr "" +"Obviamente, a zona de embalagem precisa de produtos prontos para serem " +"embalados. Portanto, uma transferência interna é solicitada para o estoque e" +" os funcionários podem coletar os produtos necessários no amazém." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "" "View of the detailed operations for a transfer between the stock and packing" " zones." msgstr "" +"Visualização das operações detalhadas de uma transferência entre as zonas de" +" estoque e de embalagem." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:333 msgid "" @@ -16438,20 +19009,28 @@ msgid "" "everything is ready to be processed so the customer can get the ordered " "items." msgstr "" +"Conforme explicado na introdução da documentação, a última etapa do processo" +" (para essa rota, a ordem de entrega) é a primeira a ser acionada, o que " +"aciona outras regras até chegarmos à primeira etapa do processo (aqui, a " +"transferência interna do estoque para a área de embalagem). Agora, tudo está" +" pronto para ser processado para que o cliente possa receber os itens " +"solicitados." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:338 msgid "" "In this example, the product is delivered to the customer when all the rules" " have been triggered and the transfers are done." msgstr "" +"Nesse exemplo, o produto é entregue ao cliente quando todas as regras são " +"acionadas e as transferências são feitas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 msgid "View of the transfers' statuses when the route is completed." -msgstr "" +msgstr "Visualização dos status das transferências quando a rota é concluída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:3 msgid "Transfer products between warehouses using replenishment" -msgstr "" +msgstr "Transferir produtos entre armazéns por reposição" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:5 msgid "" @@ -16462,10 +19041,16 @@ msgid "" "and after the transfer. This document will detail the method for conducting " "an inter-warehouse transfer using replenishment." msgstr "" +"Para empresas que usam vários armazéns, muitas vezes é necessário transferir" +" itens entre eles. Isso é chamado de *transferência entre armazéns*. O " +"*Inventário* do Odoo lida com o processo administrativo de transferências " +"entre armazéns para garantir que as contagens de estoque permaneçam precisas" +" durante e após a transferência. Este documento detalhará o método para " +"realizar uma transferência entre armazéns por reposição." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:12 msgid "Configure warehouses for inter-warehouse replenishment" -msgstr "" +msgstr "Configurar armazéns para reposição entre armazéns" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:14 msgid "" @@ -16475,6 +19060,12 @@ msgid "" "additional configuration options when creating a second warehouse that are " "needed for inter-warehouse replenishment." msgstr "" +"Primeiro, verifique se a configuração :guilabel:`Rotas com várias etapas` " +"está ativada navegando até :menuselection:`Inventário --> Configuração --> " +"Definições` e, em seguida, marque a caixa de seleção na aba " +":guilabel:`Armazém`. Isso fornecerá opções de configuração adicionais ao " +"criar um segundo armazém que são necessárias para a reposição entre " +"armazéns." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:19 msgid "" @@ -16485,18 +19076,29 @@ msgid "" "be transferred to from the :guilabel:`Warehouses` page and then click " ":guilabel:`Edit` to change its settings. Configure the warehouse as follows:" msgstr "" +"Por padrão, o Odoo vem com um armazém principal já configurado. Se um " +"armazém adicional ainda não tiver sido criado, faça-o agora no módulo " +":guilabel:`Inventário` selecionando :menuselection:`Configuração --> " +"Armazéns --> Criar`. Caso contrário, selecione o armazém para os produtos " +"serão transferidos na página :guilabel:`Armazéns` e, em seguida, clique em " +":guilabel:`Editar` para alterar suas configurações. Configure o armazémn da " +"seguinte forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:25 msgid "" ":guilabel:`Warehouse`: choose a name that is not already being used for " "another warehouse (e.g. `Alternative Warehouse`)" msgstr "" +":guilabel:`Armazém`: escolha um nome que ainda não esteja sendo usado para " +"outro armazém (por exemplo, `Armazém alternativo`)" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:27 msgid "" ":guilabel:`Short Name`: choose a short name by which the warehouse will be " "identified (e.g. `ALT_WH`)" msgstr "" +":guilabel:`Nome abreviado`: escolha um nome abreviado pelo qual o armazém " +"será identificado (por exemplo, `ALT_WH`)" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:30 msgid "" @@ -16505,12 +19107,18 @@ msgid "" "Click :guilabel:`Edit` and then check the box next to the warehouse that " "will be used to resupply the warehouse that is currently being configured." msgstr "" +"Clique em :guilabel:`Salvar` e o novo armazém será criado. Além disso, um " +"novo campo :guilabel:`Repor de` aparecerá no formulário do armazém. Clique " +"em :guilabel:`Editar` e, em seguida, marque a caixa ao lado do armazeḿ que " +"será usado para reabastecer o armazém que está sendo configurado no momento." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 msgid "" "A warehouse settings form configured to allow resupplying between " "warehouses." msgstr "" +"Um formulário de configurações de armazém configurado para permitir o " +"reabastecimento entre armazéns." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:39 msgid "" @@ -16519,10 +19127,13 @@ msgid "" "warehouse that products are transferred to (incoming) will be titled \"San " "Francisco 2\"." msgstr "" +"Para fins desta demonstração, o armazém do qual os produtos são transferidos" +" (saída) será intitulado \"San Francisco\" e o armazém para o qual os " +"produtos são transferidos (entrada) será intitulado \"San Francisco 2\"." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:44 msgid "Configure products for inter-warehouse replenishment" -msgstr "" +msgstr "Configurar produtos para reposição entre armazéns" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:46 msgid "" @@ -16531,6 +19142,10 @@ msgid "" "Products --> Products` and select an existing product or :guilabel:`Create` " "a new one, if necessary." msgstr "" +"Os produtos também devem ser configurados corretamente para que possam ser " +"transferidos entre armazéns. Navegue até :menuselection:`Inventário --> " +"Produtos --> Produtos` e selecione um produto existente ou :guilabel:`crie` " +"um novo, se necessário." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:50 msgid "" @@ -16539,14 +19154,19 @@ msgid "" "warehouse receiving the transferred products and *Y* being the warehouse " "that products are transferred from." msgstr "" +"Em seguida, no formulário do produto, vá para a aba :guilabel:`Inventário` e" +" ative a caixa de seleção para :guilabel:`X: Repor produtos de Y`, sendo *X*" +" o depósito que recebe os produtos transferidos e *Y* o armazém do qual os " +"produtos são transferidos." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 msgid "Enable the checkbox to resupply one warehouse from another." msgstr "" +"Ativar a caixa de seleção para reabastecer um armazém a partir de outro." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:59 msgid "Replenish one warehouse from another" -msgstr "" +msgstr "Reabastecer um armazém a partir de outro" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:61 msgid "" @@ -16555,22 +19175,31 @@ msgid "" " be replenished. Click the :guilabel:`Replenish` button on the top left of " "the product page and fill out the pop-up form as follows:" msgstr "" +"A partir do módulo :menuselection:`Inventário`, selecione " +":menuselection:`Produtos --> Produtos` e, em seguida, escolha o produto que " +"será reposto. Clique no botão :guilabel:`Reposição` no canto superior " +"esquerdo da página do produto e preencha o formulário pop-up da seguinte " +"forma:" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:65 msgid "" ":guilabel:`Quantity`: the number of units that will be sent to the warehouse" " being replenished" msgstr "" +":guilabel:`Quantidade`: o número de unidades que serão enviadas para o " +"armazém que está sendo reabastecido" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:66 msgid "" ":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to " "take place" msgstr "" +":guilabel:`Data programada`: a data em que o reabastecimento está programado" +" para ocorrer" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:67 msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" -msgstr "" +msgstr ":guilabel:`Armazém`: o armazém que será reabastecido" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:68 msgid "" @@ -16578,10 +19207,13 @@ msgid "" "being the warehouse to be replenished and *Y* being the warehouse that the " "product will be transferred from" msgstr "" +":guilabel:`Rotas preferidas`: selecione `X: Repor produtos de Y`, com *X* " +"sendo o armazém a ser reabastecido e *Y* sendo o armazém do qual o produto " +"será transferido" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 msgid "The form for replenishing a product." -msgstr "" +msgstr "O formulário para reposição de um produto." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:75 msgid "" @@ -16592,10 +19224,16 @@ msgid "" "between one and three steps. This document will detail how to process one-" "step deliveries and receipts." msgstr "" +"Clique em :guilabel:`Confirmar` e uma ordem de entrega será criada para o " +"armazém de saída, juntamente com um recebimento para o armazém que receberá " +"o produto. Dependendo das definições de configuração dos armazéns de entrada" +" e de saída, o processamento das ordens de entrega e dos recebimentos " +"exigirá de uma a três etapas. Este documento detalhará como processar " +"entregas e recebimentos em uma etapa." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:82 msgid "Process the delivery order" -msgstr "" +msgstr "Processar a ordem de entrega" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:84 msgid "" @@ -16609,10 +19247,19 @@ msgid "" " been dispatched, click the :guilabel:`Validate` button to register the " "quantities shipped." msgstr "" +"A primeira etapa de um pedido de reposição é o processamento da entrega do " +"armazém do qual o produto está sendo transferido. No painel de controle " +":menuselection:`Inventário`, selecione o botão :guilabel:`X a processar` no " +"cartão :guilabel:`Ordens de entrega` do armazém de saída e, em seguida, a " +"ordem de entrega criada para a reposição. Na página da ordem de entrega, " +"clique no botão :guilabel:`Verificar disponibilidade` no canto superior " +"esquerdo para reservar a quantidade do produto a ser transferido. Quando a " +"entrega tiver sido despachada, clique no botão :guilabel:`Validar` para " +"registrar as quantidades enviadas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 msgid "The delivery orders card for the outgoing warehouse." -msgstr "" +msgstr "O cartão de ordens de entrega do armazém de saída." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 msgid "" @@ -16624,6 +19271,13 @@ msgid "" ":guilabel:`Validate` button in the top left of the page to register the " "quantities received." msgstr "" +"Quando as mercadorias chegarem ao armazém de entrada, o recebimento criado " +"para esse armazém também deverá ser processado. Retorne ao painel de " +"controle :menuselection:`Inventário` e selecione o botão :guilabel:`X a " +"processar` no cartão :guilabel:`Recebimentos` para o armazém de entrada e, " +"em seguida, o recebimento criado para a reposição. Na página do recebimento," +" clique no botão :guilabel:`Validar` no canto superior esquerdo da página " +"para registrar as quantidades recebidas." #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:109 msgid "" diff --git a/locale/th/LC_MESSAGES/administration.po b/locale/th/LC_MESSAGES/administration.po new file mode 100644 index 000000000..6c914291a --- /dev/null +++ b/locale/th/LC_MESSAGES/administration.po @@ -0,0 +1,9907 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wichanon Jamwutthipreecha, 2024 +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:55+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/administration.rst:8 +msgid "Install and Maintain" +msgstr "ติดตั้งและซ่อมบำรุง" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" +"คู่มือเหล่านี้ให้คำแนะนำเกี่ยวกับวิธีการติดตั้ง บำรุงรักษา " +"และอัปเกรดฐานข้อมูล Odoo" + +#: ../../content/administration.rst:13 +msgid "" +":doc:`History of Versions <administration/maintain/supported_versions>`" +msgstr "" +":doc:`ประวัติของเวอร์ชัน <administration/maintain/supported_versions>`" + +#: ../../content/administration/install.rst:5 +msgid "Install" +msgstr "ติดตั้ง" + +#: ../../content/administration/install.rst:7 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" +"มีหลายวิธีในการติดตั้ง Odoo หรือไม่ติดตั้งเลย " +"ขึ้นอยู่กับกรณีการใช้งานที่ต้องการ" + +#: ../../content/administration/install.rst:10 +msgid "" +":doc:`Online <install/online>` is the easiest way to use Odoo in production " +"or to try it." +msgstr "" +":doc:`ออนไลน์ <install/online>` เป็นวิธีที่ง่ายที่สุดในการใช้ Odoo " +"ในการผลิตหรือลองใช้" + +#: ../../content/administration/install.rst:12 +msgid "" +":doc:`Packaged installers <install/packages>` are suitable for testing Odoo " +"and developing modules. They can be used for long-term production with " +"additional deployment and maintenance work." +msgstr "" +":doc:`ตัวติดตั้งแบบแพ็คเกจ <install/packages>` เหมาะสำหรับการทดสอบ Odoo " +"และการพัฒนาโมดูล " +"สามารถใช้สำหรับการผลิตในระยะยาวโดยมีการปรับใช้และบำรุงรักษาเพิ่มเติม" + +#: ../../content/administration/install.rst:16 +msgid "" +":doc:`Source install <install/source>` provides greater flexibility, as it " +"allows, for example, running multiple Odoo versions on the same system. It " +"is adequate to develop modules and can be used as a base for production " +"deployment." +msgstr "" +":doc:`การติดตั้งซอร์ส <install/source>` ให้ความยืดหยุ่นที่มากกว่า " +"เนื่องจากช่วยให้สามารถใช้งาน Odoo หลายเวอร์ชันบนระบบเดียวกันได้ " +"เพียงพอที่จะพัฒนาโมดูลและสามารถใช้เป็นฐานสำหรับการใช้งานจริงได้" + +#: ../../content/administration/install.rst:20 +msgid "" +"A `Docker <https://hub.docker.com/_/odoo/>`_ base image is available for " +"development or deployment." +msgstr "" +"รูปภาพพื้นฐาน `Docker <https://hub.docker.com/_/odoo/>`_ " +"พร้อมสำหรับการพัฒนาหรือการปรับใช้" + +#: ../../content/administration/install.rst:26 +msgid "Editions" +msgstr "ฉบับ" + +#: ../../content/administration/install.rst:28 +msgid "There are two different editions." +msgstr "มีสองรุ่นที่แตกต่างกัน" + +#: ../../content/administration/install.rst:30 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"<https://github.com/odoo/odoo/blob/master/LICENSE>`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" +"**Odoo Community** เป็นซอฟต์แวร์เวอร์ชันโอเพ่นซอร์สฟรี " +"ซึ่งได้รับอนุญาตภายใต้ `GNU LGPLv3 " +"<https://github.com/odoo/odoo/blob/master/LICENSE>`_ เป็นแกนหลักที่ใช้สร้าง " +"Odoo สำหรับองค์กร" + +#: ../../content/administration/install.rst:34 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing <https://www.odoo.com/pricing-plan>`_ starts from one app " +"free." +msgstr "" +"**Odoo Enterprise** เป็นเวอร์ชันซอร์สที่ใช้ร่วมกันของซอฟต์แวร์ " +"ซึ่งให้การเข้าถึงฟังก์ชันการทำงานเพิ่มเติม รวมถึงการสนับสนุนการทำงาน " +"การอัปเกรด และการโฮสต์ `การกำหนดราคา <https://www.odoo.com/pricing-plan>`_ " +"เริ่มต้นจากแอปเดียวฟรี" + +#: ../../content/administration/install.rst:39 +msgid "" +":doc:`Switch from Community to Enterprise <maintain/enterprise>` at any time" +" (except for the source install)." +msgstr "" +":doc:`เปลี่ยนจากคอมมูนิตี้เป็นองค์กร <maintain/enterprise>` ได้ตลอดเวลา " +"(ยกเว้นการติดตั้งต้นทาง)" + +#: ../../content/administration/install/cdn.rst:3 +msgid "Set up a content delivery network (CDN)" +msgstr "ตั้งค่าเครือข่ายการจัดส่งเนื้อหา (CDN)" + +#: ../../content/administration/install/cdn.rst:8 +msgid "Deploying with KeyCDN" +msgstr "การปรับใช้ด้วย KeyCDN" + +#: ../../content/administration/install/cdn.rst:10 +msgid "" +"A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, " +"is a geographically distributed network of servers that provides high speed " +"internet content. The :abbr:`CDN (Content Delivery Network)` provides quick," +" high-quality content delivery for content-heavy websites." +msgstr "" +"A :abbr:`CDN (Content Delivery Network)` หรือ *เครือข่ายการกระจายเนื้อหา* " +"เป็นเครือข่ายเซิร์ฟเวอร์ที่กระจายตามพื้นที่ทางภูมิศาสตร์ซึ่งให้บริการเนื้อหาอินเทอร์เน็ตความเร็วสูง" +" :abbr:`CDN (เครือข่ายการจัดส่งเนื้อหา)` " +"ให้การจัดส่งเนื้อหาที่รวดเร็วและมีคุณภาพสูงสำหรับเว็บไซต์ที่มีเนื้อหาจำนวนมาก" + +#: ../../content/administration/install/cdn.rst:14 +msgid "" +"This document will guide you through the setup of a KeyCDN_ account with an " +"Odoo powered website." +msgstr "" +"เอกสารนี้จะแนะนำคุณตลอดการตั้งค่าบัญชี KeyCDN_ ด้วยเว็บไซต์ที่สนับสนุนโดย " +"Odoo" + +#: ../../content/administration/install/cdn.rst:17 +msgid "Create a pull zone in the KeyCDN dashboard" +msgstr "สร้างโซนดึงในแดชบอร์ด KeyCDN" + +#: ../../content/administration/install/cdn.rst:19 +msgid "" +"On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` " +"menu item on the left. On the form, give a value to the :guilabel:`Zone " +"Name`, which will appear as part of the :abbr:`CDN (Content Delivery " +"Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the " +":guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the " +":guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, " +"under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this " +"address should be the full Odoo database :abbr:`URL (Uniform Resource " +"Locator)`." +msgstr "" +"บนแดชบอร์ด KeyCDN ให้เริ่มต้นด้วยการนำทางไปยังรายการเมนู " +":menuselection:`โซน` ทางด้านซ้าย ในแบบฟอร์ม ให้ระบุค่าให้กับ " +":guilabel:`ชื่อโซน` ซึ่งจะปรากฏเป็นส่วนหนึ่งของ :abbr:`CDN (Content Delivery" +" Network)`'s :abbr:`URL (Uniform Resource Locator)` จากนั้น ตั้งค่า " +":guilabel:`สถานะโซน` เป็น :guilabel:`ใช้งานอยู่` เพื่อใช้งานโซน สำหรับ " +":guilabel:`ประเภทโซน` ให้ตั้งค่าเป็น :guilabel:`ดึง` และสุดท้ายภายใต้ " +":guilabel:`ตั้งค่าการดึง` ให้ป้อน :guilabel:`URL ต้นทาง`— ที่อยู่นี้ควรเป็น " +"ฐานข้อมูล Odoo แบบเต็ม :abbr:`URL (Uniform Resource Locator)`" + +#: ../../content/administration/install/cdn.rst:28 +msgid "" +"Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* " +"subdomain prefix with the actual name of the database. A custom :abbr:`URL " +"(Uniform Resource Locator)` can be used, as well, in place of the Odoo " +"subdomain that was provided to the database." +msgstr "" +"ใช้ ``https://yourdatabase.odoo.com`` และแทนที่คำนำหน้าโดเมนย่อย " +"*yourdatabase* ด้วยชื่อจริงของฐานข้อมูล :abbr:`URL (Uniform Resource " +"Locator)` ที่กำหนดเองสามารถใช้ได้เช่นกัน แทนที่โดเมนย่อย Odoo " +"ที่มอบให้กับฐานข้อมูล" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN's Zone configuration page." +msgstr "หน้าการกำหนดค่าโซนของ KeyCDN" + +#: ../../content/administration/install/cdn.rst:36 +msgid "" +"Under the :guilabel:`General Settings` heading below the zone form, click " +"the :guilabel:`Show all settings` button to expand the zone options. This " +"should be the last option on the page. After expanding the " +":guilabel:`General Settings` ensure that the :guilabel:`CORS` option is " +":guilabel:`enabled`." +msgstr "" +"ใต้หัวข้อ :guilabel:`การตั้งค่าทั่วไป` ใต้แบบฟอร์มโซน ให้คลิกปุ่ม " +":guilabel:`แสดงการตั้งค่าทั้งหมด` เพื่อขยายตัวเลือกโซน " +"นี่ควรเป็นตัวเลือกสุดท้ายบนหน้า หลังจากขยาย :guilabel:`การตั้งค่าทั่วไป` " +"ตรวจสอบให้แน่ใจว่าตัวเลือก :guilabel:`CORS` เป็น :guilabel:`เปิดใช้งาน`" + +#: ../../content/administration/install/cdn.rst:41 +msgid "" +"Next, scroll to the bottom of the zone configuration page and " +":guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be" +" deployed. This can take about 10 minutes." +msgstr "" +"จากนั้น เลื่อนไปที่ด้านล่างของหน้าการกำหนดค่าโซนและ :guilabel:`บันทึก` " +"การเปลี่ยนแปลง KeyCDN จะระบุว่าโซนใหม่จะถูกปรับใช้ " +"การดำเนินการนี้อาจใช้เวลาประมาณ 10 นาที" + +#: ../../content/administration/install/cdn.rst-1 +msgid "KeyCDN deploying the new Zone." +msgstr "KeyCDN ปรับใช้โซนใหม่" + +#: ../../content/administration/install/cdn.rst:49 +msgid "" +"A new :guilabel:`Zone URL` has been generated for your Zone, in this example" +" it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each " +"database." +msgstr "" +"มีการสร้าง :guilabel:`Zone URL` ใหม่สำหรับโซนของคุณ ในตัวอย่างนี้คือ " +"``pulltest-xxxxx.kxcdn.com`` ค่านี้จะแตกต่างกันไปในแต่ละฐานข้อมูล" + +#: ../../content/administration/install/cdn.rst:52 +msgid "" +"Copy this :guilabel:`Zone URL` to a text editor for later, as it will be " +"used in the next steps." +msgstr "" +"คัดลอกสิ่งนี้ :guilabel:`URL โซน` ไปยังโปรแกรมแก้ไขข้อความเพื่อใช้ในภายหลัง " +"เนื่องจากจะถูกใช้ในขั้นตอนถัดไป" + +#: ../../content/administration/install/cdn.rst:55 +msgid "Configure the Odoo instance with the new zone" +msgstr "กำหนดค่าอินสแตนซ์ Odoo ด้วยโซนใหม่" + +#: ../../content/administration/install/cdn.rst:57 +msgid "" +"In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and" +" then activate the :guilabel:`Content Delivery Network (CDN)` setting and " +"copy/paste the :guilabel:`Zone URL` value from the earlier step into the " +":guilabel:`CDN Base URL` field. This field is only visible and configurable " +"when :doc:`Developer Mode <../../applications/general/developer_mode>` is " +"activated." +msgstr "" +"ในแอป Odoo :guilabel:`เว็บไซต์` ให้ไปที่ :menuselection:`การตั้งค่า` " +"จากนั้นเปิดใช้งานการตั้งค่า :guilabel:`Content Delivery Network (CDN)` " +"และคัดลอก/วางค่า :guilabel:`URL โซน` จาก ขั้นตอนก่อนหน้าในฟิลด์ " +":guilabel:`URL ฐาน CDN` ฟิลด์นี้จะมองเห็นและกำหนดค่าได้เฉพาะเมื่อ " +":doc:`โหมดนักพัฒนา <../../applications/general/developer_mode>` " +"ถูกเปิดใช้งาน" + +#: ../../content/administration/install/cdn.rst:63 +msgid "" +"Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN" +" Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." +msgstr "" +"ตรวจสอบให้แน่ใจว่ามี *เครื่องหมายทับ* (`//`) สองเครื่องหมายข้างหน้า " +":guilabel:`URL ฐาน CDN` และเครื่องหมายทับข้างหน้าหนึ่งเครื่องหมาย (`/`) หลัง" +" :guilabel:`URL ฐาน CDN`" + +#: ../../content/administration/install/cdn.rst:66 +msgid ":guilabel:`Save` the settings when complete." +msgstr ":guilabel:`บันทึก` การตั้งค่าเมื่อเสร็จสิ้น" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Activate the CDN setting in Odoo." +msgstr "เปิดใช้งานการตั้งค่า CDN ใน Odoo" + +#: ../../content/administration/install/cdn.rst:72 +msgid "" +"Now the website is using the CDN for the resources matching the " +":guilabel:`CDN filters` regular expressions." +msgstr "" +"ขณะนี้เว็บไซต์กำลังใช้ CDN สำหรับทรัพยากรที่ตรงกับนิพจน์ทั่วไป " +":guilabel:`ตัวกรอง CDN`" + +#: ../../content/administration/install/cdn.rst:75 +msgid "" +"In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` " +"integration is evidenced as working properly by checking the :abbr:`URL " +"(Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen" +" by using your web browser's :guilabel:`Inspect` feature on the Odoo " +"website. Look for it's record by searching within the :guilabel:`Network` " +"tab inside of devtools." +msgstr "" +"ใน HTML ของเว็บไซต์ Odoo การผสานรวม :abbr:`CDN (เครือข่ายการจัดส่งเนื้อหา)` " +"ได้รับการพิสูจน์แล้วว่าทำงานได้อย่างถูกต้องโดยการตรวจสอบ :abbr:`URL " +"(ตัวระบุทรัพยากรแบบเดียวกัน)` ของรูปภาพ คุณสามารถดูค่า *URL ฐาน CDN* " +"ได้โดยใช้ฟีเจอร์ :guilabel:`ตรวจสอบ` ของเว็บเบราว์เซอร์บนเว็บไซต์ Odoo " +"ค้นหาบันทึกโดยค้นหาภายในแท็บ :guilabel:`เครือข่าย` ภายใน devtools" + +#: ../../content/administration/install/cdn.rst-1 +msgid "" +"The CDN Base URL can be seen using the inspect function on the Odoo website." +msgstr "สามารถดู URL ฐาน CDN ได้โดยใช้ฟังก์ชันตรวจสอบบนเว็บไซต์ Odoo" + +#: ../../content/administration/install/cdn.rst:85 +msgid "" +"Prevent security issues by activating cross-origin resource sharing (CORS)" +msgstr "" +"ป้องกันปัญหาด้านความปลอดภัยด้วยการเปิดใช้งานการแบ่งปันทรัพยากรข้ามต้นทาง " +"(CORS)" + +#: ../../content/administration/install/cdn.rst:87 +msgid "" +"A security restriction in some browsers (such as Mozilla Firefox and Google " +"Chrome) prevents a remotely linked CSS file to fetch relative resources on " +"this same external server." +msgstr "" +"ข้อจำกัดด้านความปลอดภัยในเบราว์เซอร์บางตัว (เช่น Mozilla Firefox และ Google " +"Chrome) ป้องกันไม่ให้ไฟล์ CSS " +"ที่เชื่อมโยงจากระยะไกลดึงทรัพยากรที่เกี่ยวข้องบนเซิร์ฟเวอร์ภายนอกเดียวกันนี้" + +#: ../../content/administration/install/cdn.rst:90 +msgid "" +"If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in " +"the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard " +"Odoo website will be the lack of *Font Awesome* icons because the font file " +"declared in the *Font Awesome* CSS won't be loaded from the remote server." +msgstr "" +"หากไม่ได้เปิดใช้งานตัวเลือก :abbr:`CORS (Cross-Origin Resource Sharing)` ใน " +":guilabel:`โซน CDN` ปัญหาที่เกิดขึ้นที่ชัดเจนยิ่งขึ้นบนเว็บไซต์ Odoo " +"มาตรฐานก็คือการไม่มีไอคอน *ฟ้อนต์ที่ยอดเยี่ยม* เนื่องจากไฟล์ฟอนต์ที่ประกาศใน" +" *ฟ้อนต์ที่ยอดเยี่ยม* CSS จะไม่ถูกโหลดจากเซิร์ฟเวอร์ระยะไกล" + +#: ../../content/administration/install/cdn.rst:95 +msgid "" +"When these cross-origin resource issues occur, a security error message " +"similar to the output below will appear in the web browser's developer " +"console:" +msgstr "" +"เมื่อเกิดปัญหาทรัพยากรข้ามต้นทาง " +"ข้อความแสดงข้อผิดพลาดด้านความปลอดภัยที่คล้ายกับผลลัพธ์ด้านล่างจะปรากฏในคอนโซลนักพัฒนาซอฟต์แวร์ของเว็บเบราว์เซอร์:" + +#: ../../content/administration/install/cdn.rst:98 +msgid "" +"``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from " +"loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-" +"Allow-Origin' header is present on the requested resource. Origin " +"'http://yourdatabase.odoo.com' is therefore not allowed access.``" +msgstr "" +"``แบบอักษรจากแหล่งกำเนิด 'http://pulltest-xxxxx.kxcdn.com' " +"ถูกบล็อกไม่ให้โหลด /shop:1 โดยนโยบายการแบ่งปันทรัพยากรข้ามแหล่งกำเนิด: " +"ไม่มีส่วนหัว 'Access-Control-Allow-Origin' บน ทรัพยากรที่ร้องขอ ที่มา " +"'http://yourdatabase.odoo.com' จึงไม่ได้รับอนุญาตให้เข้าถึง``" + +#: ../../content/administration/install/cdn.rst-1 +msgid "Error message populated in the browser console." +msgstr "มีข้อความแสดงข้อผิดพลาดอยู่ในคอนโซลของเบราว์เซอร์" + +#: ../../content/administration/install/cdn.rst:106 +msgid "" +"Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the " +":abbr:`CDN (Content Delivery Network)` settings fixes this issue." +msgstr "" +"การเปิดใช้งานตัวเลือก :abbr:`CORS (Cross-Origin Resource Sharing)` " +"ในการตั้งค่า :abbr:`CDN (Content Delivery Network)` จะช่วยแก้ไขปัญหานี้ได้" + +#: ../../content/administration/install/deploy.rst:3 +msgid "System configuration" +msgstr "การกำหนดค่าระบบ" + +#: ../../content/administration/install/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../install>`, and is " +"not generally necessary for a development systems that is not exposed on the" +" internet." +msgstr "" +"เอกสารนี้อธิบายขั้นตอนพื้นฐานในการตั้งค่า Odoo " +"ในการใช้งานจริงหรือบนเซิร์ฟเวอร์ที่เชื่อมต่อกับอินเทอร์เน็ต มันเป็นไปตาม " +":doc:`การติดตั้ง <../install>` " +"และโดยทั่วไปแล้วไม่จำเป็นสำหรับระบบการพัฒนาที่ไม่ได้เปิดเผยบนอินเทอร์เน็ต" + +#: ../../content/administration/install/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" +"หากคุณกำลังตั้งค่าเซิร์ฟเวอร์สาธารณะ โปรดตรวจสอบคำแนะนำ :ref:`security` " +"ของเรา!" + +#: ../../content/administration/install/deploy.rst:15 +msgid "dbfilter" +msgstr "dbfilter" + +#: ../../content/administration/install/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" +"Odoo เป็นระบบที่มีผู้เช่าหลายราย: ระบบ Odoo " +"เดียวอาจทำงานและให้บริการอินสแตนซ์ฐานข้อมูลจำนวนหนึ่งได้ " +"นอกจากนี้ยังสามารถปรับแต่งได้สูงด้วยการปรับแต่ง (เริ่มจากโมดูลที่กำลังโหลด) " +"ขึ้นอยู่กับ \"ฐานข้อมูลปัจจุบัน\"" + +#: ../../content/administration/install/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" +"นี่ไม่ใช่ปัญหาเมื่อทำงานกับแบ็กเอนด์ (เว็บไคลเอ็นต์) " +"ในฐานะผู้ใช้บริษัทที่เข้าสู่ระบบ: สามารถเลือกฐานข้อมูลได้เมื่อเข้าสู่ระบบ " +"และโหลดการปรับแต่งในภายหลัง" + +#: ../../content/administration/install/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" +"อย่างไรก็ตาม ปัญหาสำหรับผู้ใช้ที่ไม่ได้เข้าสู่ระบบ (พอร์ทัล เว็บไซต์) " +"ซึ่งไม่ได้ผูกไว้กับฐานข้อมูล: Odoo " +"จำเป็นต้องทราบว่าควรใช้ฐานข้อมูลใดในการโหลดหน้าเว็บไซต์หรือดำเนินการ " +"หากไม่ได้ใช้การเช่าหลายรายการซึ่งไม่เป็นปัญหา จะมีเพียงฐานข้อมูลเดียวให้ใช้ " +"แต่หากมีหลายฐานข้อมูลที่เข้าถึงได้ Odoo " +"จำเป็นต้องมีกฎเพื่อทราบว่าควรใช้ฐานข้อมูลใด" + +#: ../../content/administration/install/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter <odoo-bin --db-filter>`:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" +"นั่นคือหนึ่งในวัตถุประสงค์ของ :option:`--db-filter <odoo-bin --db-filter>`: " +"ระบุว่าควรเลือกฐานข้อมูลตามชื่อโฮสต์ (โดเมน) ที่ถูกร้องขออย่างไร ค่านี้คือ " +"`นิพจน์ทั่วไป`_ ซึ่งอาจรวมถึงชื่อโฮสต์ที่แทรกแบบไดนามิก (`` %h``) " +"หรือโดเมนย่อยแรก (``%d``) ที่ใช้เข้าถึงระบบ" + +#: ../../content/administration/install/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" +"สำหรับเซิร์ฟเวอร์ที่โฮสต์ฐานข้อมูลหลายฐานข้อมูลในการใช้งานจริง " +"โดยเฉพาะอย่างยิ่งหากใช้ ``เว็บไซต์`` จะต้องตั้งค่า dbfilter **จำเป็น** " +"ไม่เช่นนั้นฟีเจอร์บางอย่างจะทำงานไม่ถูกต้อง" + +#: ../../content/administration/install/deploy.rst:42 +msgid "Configuration samples" +msgstr "ตัวอย่างการกำหนดค่า" + +#: ../../content/administration/install/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "แสดงเฉพาะฐานข้อมูลที่มีชื่อขึ้นต้นด้วย 'mycompany'" + +#: ../../content/administration/install/deploy.rst:46 +#: ../../content/administration/install/deploy.rst:58 +#: ../../content/administration/install/deploy.rst:153 +#: ../../content/administration/install/deploy.rst:280 +msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:" +msgstr "ในเซ็ท :ref:`ไฟล์การกำหนดค่า <reference/cmdline/config_file>`:" + +#: ../../content/administration/install/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" +"แสดงเฉพาะฐานข้อมูลที่ตรงกับโดเมนย่อยแรกที่อยู่หลัง ``www``: ตัวอย่างเช่น " +"ฐานข้อมูล \"mycompany\" จะแสดงขึ้นหากคำขอขาเข้าถูกส่งไปยัง " +"``www.mycompany.com`` หรือ ``mycompany.co.uk`` แต่ไม่ใช่สำหรับ " +"``www2.mycompany.com`` หรือ ``helpdesk.mycompany.com``" + +#: ../../content/administration/install/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter <odoo-bin --db-filter>` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" +"การตั้งค่า :option:`--db-filter <odoo-bin --db-filter>` " +"ที่เหมาะสมเป็นส่วนสำคัญในการรักษาความปลอดภัยการปรับใช้ของคุณ " +"เมื่อทำงานอย่างถูกต้องและจับคู่ฐานข้อมูลเดียวต่อชื่อโฮสต์ " +"ขอแนะนำอย่างยิ่งให้บล็อกการเข้าถึงหน้าจอตัวจัดการฐานข้อมูล " +"และใช้พารามิเตอร์เริ่มต้น ``--no-database-list`` " +"เพื่อป้องกันการแสดงรายการฐานข้อมูลของคุณ " +"และบล็อกการเข้าถึงหน้าจอการจัดการฐานข้อมูล ดูเพิ่มเติมเกี่ยวกับความปลอดภัย_" + +#: ../../content/administration/install/deploy.rst:76 +#: ../../content/administration/install/source.rst:193 +msgid "PostgreSQL" +msgstr "PostgreSQL" + +#: ../../content/administration/install/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" +"ตามค่าเริ่มต้น PostgreSQL อนุญาตการเชื่อมต่อผ่านซ็อกเก็ต UNIX " +"และการเชื่อมต่อแบบย้อนกลับเท่านั้น (จาก \"localhost\" " +"ซึ่งเป็นเครื่องเดียวกับที่ติดตั้งเซิร์ฟเวอร์ PostgreSQL)" + +#: ../../content/administration/install/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" +"ซ็อกเก็ต UNIX นั้นใช้ได้ถ้าคุณต้องการให้ Odoo และ PostgreSQL " +"ดำเนินการบนเครื่องเดียวกัน และเป็นค่าเริ่มต้นเมื่อไม่ได้ระบุโฮสต์ไว้ " +"แต่ถ้าคุณต้องการให้ Odoo และ PostgreSQL ดำเนินการบนเครื่องที่แตกต่างกัน " +"[#different-machines]_ จะต้อง `ฟังอินเทอร์เฟซเครือข่าย`_ [#remote-socket]_ " +"อย่างใดอย่างหนึ่ง:" + +#: ../../content/administration/install/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" +"ยอมรับเฉพาะการเชื่อมต่อแบบย้อนกลับและ `ใช้ช่องทางการเชื่อมต่อ SSH`_ " +"ระหว่างเครื่องที่ Odoo รันกับเครื่องที่ PostgreSQL รัน จากนั้นกำหนดค่า Odoo " +"ให้เชื่อมต่อกับจุดสิ้นสุดของช่องทางการเชื่อมต่อ" + +#: ../../content/administration/install/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" +"ยอมรับการเชื่อมต่อกับเครื่องที่ติดตั้ง Odoo ซึ่งอาจผ่าน ssl (ดูรายละเอียดใน " +"`การตั้งค่าการเชื่อมต่อ PostgreSQL`_) จากนั้นกำหนดค่า Odoo " +"ให้เชื่อมต่อผ่านเครือข่าย" + +#: ../../content/administration/install/deploy.rst:95 +#: ../../content/administration/install/deploy.rst:145 +#: ../../content/administration/install/deploy.rst:235 +#: ../../content/administration/install/deploy.rst:275 +msgid "Configuration sample" +msgstr "ตัวอย่างการกำหนดค่า" + +#: ../../content/administration/install/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "อนุญาตการเชื่อมต่อ TCP บน localhost" + +#: ../../content/administration/install/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "อนุญาตการเชื่อมต่อ TCP จากเครือข่าย 192.168.1.x" + +#: ../../content/administration/install/deploy.rst:100 +msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:" +msgstr "" +"ในเซ็ท ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf``:" + +#: ../../content/administration/install/deploy.rst:108 +msgid "" +"in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:" +msgstr "" +"ในเซ็ท ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf``:" + +#: ../../content/administration/install/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "กำลังกำหนดค่า Odoo" + +#: ../../content/administration/install/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"<reference/cmdline/server/database>` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" +"เมื่อเริ่มใช้งาน Odoo จะเชื่อมต่อกับ postgres ในเครื่องผ่านซ็อกเก็ต UNIX " +"ผ่านพอร์ต 5432 ซึ่งสามารถแทนที่ได้โดยใช้ :ref:`ตัวเลือกฐานข้อมูล " +"<reference/cmdline/server/database>` เมื่อการปรับใช้ Postgres " +"ของคุณไม่ใช่ในเครื่องและ/หรือ ไม่ได้ใช้ค่าเริ่มต้นการติดตั้ง" + +#: ../../content/administration/install/deploy.rst:126 +msgid "" +"The :doc:`packaged installers <packages>` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" +":doc:`ตัวติดตั้งแบบแพ็คเกจ <packages> ` จะสร้างผู้ใช้ใหม่โดยอัตโนมัติ " +"(``odoo``) และตั้งค่าให้เป็นผู้ใช้ฐานข้อมูล" + +#: ../../content/administration/install/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" +"หน้าจอการจัดการฐานข้อมูลได้รับการปกป้องโดยการตั้งค่า ``admin_passwd`` " +"การตั้งค่านี้สามารถตั้งค่าได้โดยใช้ไฟล์การกำหนดค่าเท่านั้น " +"และจะถูกตรวจสอบก่อนดำเนินการแก้ไขฐานข้อมูล " +"ควรตั้งค่าเป็นค่าที่สร้างขึ้นแบบสุ่มเพื่อให้แน่ใจว่าบุคคลที่สามไม่สามารถใช้อินเทอร์เฟซนี้ได้" + +#: ../../content/administration/install/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"<reference/cmdline/server/database>`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" +"การดำเนินการฐานข้อมูลทั้งหมดใช้ :ref:`ตัวเลือกฐานข้อมูล " +"<reference/cmdline/server/database>` รวมถึงหน้าจอการจัดการฐานข้อมูล " +"เพื่อให้หน้าจอการจัดการฐานข้อมูลทำงานได้ ผู้ใช้ PostgreSQL จะต้องมีสิทธิ์ " +"``createdb``" + +#: ../../content/administration/install/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" +"ผู้ใช้สามารถทิ้งฐานข้อมูลของตนเองได้ตลอดเวลา " +"เพื่อให้หน้าจอการจัดการฐานข้อมูลไม่ทำงานโดยสมบูรณ์ ผู้ใช้ PostgreSQL " +"จะต้องถูกสร้างขึ้นด้วย ``no-createdb`` และฐานข้อมูลจะต้องเป็นของผู้ใช้ " +"PostgreSQL อื่น" + +#: ../../content/administration/install/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "ผู้ใช้ PostgreSQL *ต้องไม่* เป็นผู้ใช้ระดับสูง" + +#: ../../content/administration/install/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "เชื่อมต่อกับเซิร์ฟเวอร์ PostgreSQL บน 192.168.1.2" + +#: ../../content/administration/install/deploy.rst:148 +msgid "port 5432" +msgstr "พอร์ต 5432" + +#: ../../content/administration/install/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "โดยใช้บัญชีผู้ใช้ 'odoo'" + +#: ../../content/administration/install/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "โดยมี 'pwd' เป็นรหัสผ่าน" + +#: ../../content/administration/install/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "กรองเฉพาะ db ที่มีชื่อขึ้นต้นด้วย 'mycompany'" + +#: ../../content/administration/install/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "SSL ระหว่าง Odoo และ PostgreSQL" + +#: ../../content/administration/install/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" +"ตั้งแต่ Odoo 11.0 คุณสามารถบังคับใช้การเชื่อมต่อ SSL ระหว่าง Odoo และ " +"PostgreSQL ได้ ใน Odoo db_sslmode ควบคุมความปลอดภัย ssl " +"ของการเชื่อมต่อด้วยค่าที่เลือกจาก 'ปิดการใช้งาน', 'อนุญาต', 'ต้องการ', " +"'ต้องการ', 'ตรวจสอบ-ca' หรือ 'ตรวจสอบเต็ม'" + +#: ../../content/administration/install/deploy.rst:175 +msgid "" +"`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_" +msgstr "" +"`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_" + +#: ../../content/administration/install/deploy.rst:180 +msgid "Builtin server" +msgstr "เซิร์ฟเวอร์ในตัว" + +#: ../../content/administration/install/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" +"Odoo มีเซิร์ฟเวอร์ HTTP, cron และไลฟ์แชทในตัว " +"โดยใช้มัลติเธรดหรือการประมวลผลหลายตัว" + +#: ../../content/administration/install/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" +"เซิร์ฟเวอร์ **แบบมัลติเธรด** " +"เป็นเซิร์ฟเวอร์ที่เรียบง่ายกว่าซึ่งส่วนใหญ่ใช้สำหรับการพัฒนา การสาธิต " +"และความเข้ากันได้กับระบบปฏิบัติการต่างๆ (รวมถึง Windows) " +"เธรดใหม่จะถูกสร้างขึ้นสำหรับทุกคำขอ HTTP ใหม่ " +"แม้แต่สำหรับการเชื่อมต่อที่มีอายุการใช้งานยาวนาน เช่น websocket เธรด cron " +"daemonic พิเศษก็ถูกสร้างขึ้นเช่นกัน เนื่องจากข้อจำกัดของ Python (GIL) " +"จึงไม่สามารถใช้ฮาร์ดแวร์ให้เกิดประโยชน์สูงสุดได้" + +#: ../../content/administration/install/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers <odoo-bin --workers>` " +"option out or setting it to ``0``." +msgstr "" +"เซิร์ฟเวอร์แบบมัลติเธรดเป็นเซิร์ฟเวอร์เริ่มต้นสำหรับคอนเทนเนอร์นักเทียบท่าด้วย" +" มันถูกเลือกโดยปล่อยตัวเลือก :option:`--workers <odoo-bin --workers>` " +"ออกหรือตั้งค่าเป็น ``0``" + +#: ../../content/administration/install/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" +"เซิร์ฟเวอร์ **การประมวลผลหลายตัว** " +"เป็นเซิร์ฟเวอร์เต็มรูปแบบที่ใช้สำหรับการผลิตเป็นหลัก " +"จะไม่รับผิดชอบต่อข้อจำกัด Python (GIL) เดียวกันในการใช้ทรัพยากร " +"และด้วยเหตุนี้จึงใช้ฮาร์ดแวร์ให้เกิดประโยชน์สูงสุด " +"กลุ่มคนทำงานถูกสร้างขึ้นเมื่อเริ่มต้นเซิร์ฟเวอร์ ระบบปฏิบัติการจะจัดคิวคำขอ " +"HTTP ใหม่จนกว่าจะมีคนทำงานพร้อมที่จะประมวลผล ผู้ปฏิบัติงาน HTTP " +"ที่ขับเคลื่อนด้วยเหตุการณ์พิเศษสำหรับไลฟ์แชทนั้นถูกสร้างขึ้นบนพอร์ตอื่น " +"คนทำงาน cron พิเศษก็เกิดขึ้นเช่นกัน " +"เก็บเกี่ยวกระบวนการที่กำหนดค่าได้จะตรวจสอบการใช้ทรัพยากรและสามารถหยุด/รีสตาร์ทผู้ปฏิบัติงานที่ไม่สำเร็จได้" + +#: ../../content/administration/install/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers <odoo-bin --workers>` option to a non-null integer." +msgstr "" +"เซิร์ฟเวอร์ที่มีการประมวลผลหลายตัวเลือกใช้ มันถูกเลือกโดยการตั้งค่าตัวเลือก " +":option:`--workers <odoo-bin --workers>` เป็นจำนวนเต็มที่ไม่ใช่ค่าว่าง" + +#: ../../content/administration/install/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" +"เนื่องจากได้รับการปรับแต่งอย่างมากสำหรับเซิร์ฟเวอร์ Linux " +"เซิร์ฟเวอร์ที่มีการประมวลผลหลายรายการจึงไม่พร้อมใช้งานบน Windows" + +#: ../../content/administration/install/deploy.rst:209 +msgid "Worker number calculation" +msgstr "การคำนวณจำนวนคนงาน" + +#: ../../content/administration/install/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "หลักทั่วไป : (#CPU * 2) + 1" + +#: ../../content/administration/install/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "คนทำงาน Cron ต้องการ CPU" + +#: ../../content/administration/install/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "คนงาน 1 คน ~= 6 ผู้ใช้พร้อมกัน" + +#: ../../content/administration/install/deploy.rst:216 +msgid "memory size calculation" +msgstr "การคำนวณขนาดหน่วยความจำ" + +#: ../../content/administration/install/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" +"เราถือว่าคำขอ 20% เป็นคำขอจำนวนมาก ในขณะที่ 80% เป็นคำขอที่เรียบง่ายกว่า" + +#: ../../content/administration/install/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" +"ซึ่งทำงานหนัก เมื่อฟิลด์ที่คำนวณทั้งหมดได้รับการออกแบบมาอย่างดี คำขอ SQL " +"จะได้รับการออกแบบมาอย่างดี ... คาดว่าจะใช้ RAM ประมาณ 1GB" + +#: ../../content/administration/install/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" +"ในสถานการณ์เดียวกัน ส่วนของงานที่เบากว่านั้นคาดว่าจะใช้ RAM ประมาณ 150MB" + +#: ../../content/administration/install/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" +"RAM ที่ต้องการ = #worker * ( (light_worker_ratio * " +"light_worker_ram_estimation) + (heavy_worker_ratio * " +"heavy_worker_ram_estimation) )" + +#: ../../content/administration/install/deploy.rst:225 +#: ../../content/administration/install/deploy.rst:412 +msgid "LiveChat" +msgstr "ไลฟ์แชท" + +#: ../../content/administration/install/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port <odoo-bin --gevent-port>`. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode <odoo-bin" +" --proxy-mode>` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" +"ในการประมวลผลหลายรายการ " +"พนักงานไลฟ์แชทโดยเฉพาะจะเริ่มทำงานโดยอัตโนมัติและรับฟัง :option:`--gevent-" +"port <odoo-bin --gevent-port>` ตามค่าเริ่มต้น คำขอ HTTP " +"จะเข้าถึงผู้ปฏิบัติงาน HTTP ปกติต่อไป แทนที่จะเป็นไลฟ์แชท " +"คุณต้องปรับใช้พร็อกซีหน้า Odoo " +"และเปลี่ยนเส้นทางคำขอขาเข้าที่มีเส้นทางขึ้นต้นด้วย ``/websocket/`` " +"ไปยังพนักงานไลฟ์แชท คุณต้องเริ่ม Odoo ใน :option:`--proxy-mode <odoo-bin " +"--proxy-mode>` ดังนั้นจึงใช้ส่วนหัวของไคลเอ็นต์จริง (เช่น ชื่อโฮสต์ สคีม และ" +" IP) แทนส่วนหัวของพร็อกซี" + +#: ../../content/administration/install/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "เซิร์ฟเวอร์ที่มี 4 CPU, 8 เธรด" + +#: ../../content/administration/install/deploy.rst:238 +msgid "60 concurrent users" +msgstr "ผู้ใช้พร้อมกัน 60 คน" + +#: ../../content/administration/install/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "ผู้ใช้ 60 ราย / 6 = 10 <- จำนวนคนงานที่ต้องการตามทฤษฎี" + +#: ../../content/administration/install/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "(4 * 2) + 1 = 9 <- จำนวนคนงานสูงสุดตามทฤษฎี" + +#: ../../content/administration/install/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" +"เราจะใช้คนงาน 8 คน + 1 คนสำหรับ cron นอกจากนี้เรายังใช้ระบบตรวจสอบ " +"เพื่อวัดโหลด cpu และตรวจสอบว่าอยู่ระหว่าง 7 ถึง 7.5 หรือไม่" + +#: ../../content/administration/install/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +msgstr "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM สำหรับ Odoo" + +#: ../../content/administration/install/deploy.rst:245 +msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:" +msgstr "ใน :ref:`the configuration file <reference/cmdline/config_file>`:" + +#: ../../content/administration/install/deploy.rst:261 +msgid "HTTPS" +msgstr "HTTPS" + +#: ../../content/administration/install/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" +"ไม่ว่าจะเข้าถึงผ่านเว็บไซต์/เว็บไคลเอ็นต์ หรือบริการเว็บ Odoo " +"จะส่งข้อมูลการตรวจสอบสิทธิ์ในรูปแบบข้อความธรรมดา ซึ่งหมายความว่าการติดตั้ง " +"Odoo อย่างปลอดภัยต้องใช้ HTTPS\\ [#switching]_ การยกเลิก SSL " +"สามารถทำได้ผ่านพร็อกซีการยกเลิก SSL ใดก็ได้ แต่ต้องมีการตั้งค่าต่อไปนี้:" + +#: ../../content/administration/install/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" +"เปิดใช้งาน Odoo :option:`โหมดพร็อกซี <odoo-bin --proxy-mode>` " +"ควรเปิดใช้งานเฉพาะเมื่อ Odoo อยู่หลังพร็อกซีย้อนกลับ" + +#: ../../content/administration/install/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "ตั้งค่าพร็อกซีการยกเลิก SSL (`ตัวอย่างการยกเลิก Nginx`_)" + +#: ../../content/administration/install/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "ตั้งค่าพร็อกซีเอง (`ตัวอย่างพร็อกซี Nginx`_)" + +#: ../../content/administration/install/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" +"พร็อกซีการยกเลิก SSL " +"ของคุณควรเปลี่ยนเส้นทางการเชื่อมต่อที่ไม่ปลอดภัยไปยังพอร์ตที่ปลอดภัยโดยอัตโนมัติ" + +#: ../../content/administration/install/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "เปลี่ยนเส้นทางคำขอ http ไปยัง https" + +#: ../../content/administration/install/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "คำขอพร็อกซีสำหรับ odoo" + +#: ../../content/administration/install/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "ในเซ็ท ``/etc/nginx/sites-enabled/odoo.conf``:" + +#: ../../content/administration/install/deploy.rst:361 +msgid "HTTPS Hardening" +msgstr "การทำให้ HTTPS แข็งแกร่งขึ้น" + +#: ../../content/administration/install/deploy.rst:363 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" +"เพิ่มส่วนหัว `Strict-Transport-Security` ให้กับคำขอทั้งหมด " +"เพื่อป้องกันไม่ให้เบราว์เซอร์ส่งคำขอ HTTP ธรรมดาไปยังโดเมนนี้ " +"คุณจะต้องรักษาบริการ HTTPS " +"ที่ใช้งานได้โดยมีใบรับรองที่ถูกต้องบนโดเมนนี้ตลอดเวลา " +"ไม่เช่นนั้นผู้ใช้ของคุณจะเห็นการแจ้งเตือนด้านความปลอดภัยหรือไม่สามารถเข้าถึงได้เลย" + +#: ../../content/administration/install/deploy.rst:369 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" +"บังคับใช้การเชื่อมต่อ HTTPS ในช่วงหนึ่งปีสำหรับผู้เยี่ยมชมทุกคนใน NGINX " +"ด้วยบรรทัด:" + +#: ../../content/administration/install/deploy.rst:375 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" +"สามารถกำหนดการกำหนดค่าเพิ่มเติมสำหรับคุกกี้ `session_id` ได้ " +"คุณสามารถเพิ่มแฟล็ก 'ปลอดภัย' เพื่อให้แน่ใจว่าจะไม่ส่งผ่าน HTTP และ " +"'SameSite=Lax' เพื่อป้องกัน `CSRF`_ ที่ได้รับการรับรองความถูกต้อง" + +#: ../../content/administration/install/deploy.rst:386 +msgid "Odoo as a WSGI Application" +msgstr "Odoo เป็นแอปพลิเคชัน WSGI" + +#: ../../content/administration/install/deploy.rst:388 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" +"นอกจากนี้ยังสามารถติดตั้ง Odoo เป็นแอปพลิเคชัน WSGI_ มาตรฐานได้อีกด้วย Odoo " +"จัดเตรียมฐานสำหรับสคริปต์ตัวเรียกใช้งาน WSGI เป็น ``odoo-wsgi.example.py`` " +"ควรปรับแต่งสคริปต์นั้น (อาจหลังจากคัดลอกจากไดเร็กทอรีการตั้งค่า) " +"เพื่อตั้งค่าการกำหนดค่าโดยตรงใน :mod:`odoo.tools.config` อย่างถูกต้อง " +"แทนที่จะใช้บรรทัดคำสั่งหรือไฟล์การกำหนดค่า" + +#: ../../content/administration/install/deploy.rst:394 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" +"อย่างไรก็ตาม เซิร์ฟเวอร์ WSGI จะเปิดเผยเฉพาะตำแหน่งข้อมูล HTTP " +"หลักสำหรับเว็บไคลเอ็นต์ เว็บไซต์ และ API บริการเว็บเท่านั้น เนื่องจาก Odoo " +"ไม่ได้ควบคุมการสร้างคนทำงานอีกต่อไป จึงไม่สามารถตั้งค่าคนทำงาน cron " +"หรือไลฟ์แชทได้" + +#: ../../content/administration/install/deploy.rst:399 +msgid "Cron Workers" +msgstr "คนงาน Cron" + +#: ../../content/administration/install/deploy.rst:401 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http <odoo-bin " +"--no-http>` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" +"จำเป็นต้องเริ่มต้นเซิร์ฟเวอร์ Odoo ในตัวตัวใดตัวหนึ่งถัดจากเซิร์ฟเวอร์ WSGI " +"เพื่อประมวลผลงาน cron เซิร์ฟเวอร์นั้นจะต้องได้รับการกำหนดค่าให้ประมวลผลเฉพาะ" +" crons ไม่ใช่คำขอ HTTP โดยใช้ตัวเลือก :option:`--no-http <odoo-bin --no-" +"http>` ตัวเลือก cli หรือการตั้งค่าไฟล์การกำหนดค่า ``http_enable = False``" + +#: ../../content/administration/install/deploy.rst:406 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 <odoo-bin " +"--workers>` and :option:`--max-cron-threads=n <odoo-bin --max-cron-threads>`" +" cli options." +msgstr "" +"บนระบบที่คล้ายกับ Linux " +"ขอแนะนำให้ใช้เซิร์ฟเวอร์ที่มีการประมวลผลหลายตัวบนเซิร์ฟเวอร์แบบมัลติเธรด " +"เพื่อให้ได้รับประโยชน์จากการใช้ฮาร์ดแวร์ที่ดีขึ้นและความเสถียรที่เพิ่มขึ้น " +"กล่าวคือ การใช้ :option:`--workers=-1 <odoo-bin -- คนงาน>` และ " +":option:`--max-cron-threads=n <odoo-bin --max-cron-threads>` ตัวเลือก cli" + +#: ../../content/administration/install/deploy.rst:414 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" +"จำเป็นต้องใช้เซิร์ฟเวอร์ WSGI ที่เข้ากันได้กับ gevent " +"เพื่อการทำงานที่ถูกต้องของฟีเจอร์ไลฟ์แชท " +"เซิร์ฟเวอร์นั้นควรจะสามารถรองรับการเชื่อมต่อที่มีอายุการใช้งานยาวนานพร้อมกันจำนวนมากได้" +" แต่ไม่ต้องการพลังการประมวลผลมากนัก คำขอทั้งหมดที่เส้นทางเริ่มต้นด้วย " +"``/websocket/`` ควรถูกส่งไปยังเซิร์ฟเวอร์นั้น ควรใช้เซิร์ฟเวอร์ WSGI ปกติ " +"(ตามเธรด/ตามกระบวนการ) สำหรับคำขออื่นทั้งหมด" + +#: ../../content/administration/install/deploy.rst:420 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http <odoo-bin --no-http>` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port <odoo-bin " +"--http-port>` (multi-threading server) or on the :option:`--gevent-port " +"<odoo-bin --gevent-port>` (multi-processing server)." +msgstr "" +"เซิร์ฟเวอร์ Odoo cron ยังสามารถใช้เพื่อให้บริการตามคำขอไลฟ์แชทได้ " +"เพียงวางตัวเลือก cli :option:`--no-http <odoo-bin --no-http>` จากเซิร์ฟเวอร์" +" cron และตรวจสอบให้แน่ใจว่าคำขอที่มีเส้นทางขึ้นต้นด้วย ``/websocket/`` " +"ถูกส่งไปยังเซิร์ฟเวอร์นี้โดยตรง บน :option:`--http-port <odoo-bin --http-" +"port>` (เซิร์ฟเวอร์แบบมัลติเธรด) หรือบน :option:`--gevent-port <odoo-bin " +"--gevent-port >` (เซิร์ฟเวอร์ที่มีการประมวลผลหลายตัว)" + +#: ../../content/administration/install/deploy.rst:429 +msgid "Serving static files and attachments" +msgstr "ให้บริการไฟล์ static และไฟล์แนบ" + +#: ../../content/administration/install/deploy.rst:431 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" +"เพื่อความสะดวกในการพัฒนา Odoo จะให้บริการไฟล์ static " +"และไฟล์แนบทั้งหมดในโมดูลโดยตรง อาจไม่เหมาะเมื่อพูดถึงประสิทธิภาพ " +"และโดยทั่วไปไฟล์แบบ static ควรให้บริการโดยเซิร์ฟเวอร์ HTTP แบบ static" + +#: ../../content/administration/install/deploy.rst:436 +msgid "Serving static files" +msgstr "ให้บริการไฟล์ static" + +#: ../../content/administration/install/deploy.rst:438 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" +"ไฟล์ static ของ Odoo จะอยู่ในโฟลเดอร์ :file:`static/` ของแต่ละโมดูล " +"ดังนั้นไฟล์คงที่จึงสามารถให้บริการได้โดยการสกัดกั้นคำขอทั้งหมดที่ส่งไปยัง " +":samp:`/{MODULE}/static/{FILE}` และค้นหาโมดูลที่ถูกต้อง (และไฟล์) " +"ในพาธแอดออนต่างๆ" + +#: ../../content/administration/install/deploy.rst:442 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" +"ขอแนะนำให้ตั้งค่าส่วนหัว ``Content-Security-Policy: default-src 'none''`` " +"บนรูปภาพทั้งหมดที่ส่งโดยเว็บเซิร์ฟเวอร์ " +"ซึ่งไม่จำเป็นอย่างยิ่งเนื่องจากผู้ใช้ไม่สามารถแก้ไข/แทรกเนื้อหาภายในโฟลเดอร์" +" :file:`static/` ของโมดูล และรูปภาพที่มีอยู่ถือเป็นที่สิ้นสุด " +"(ไม่ได้ดึงทรัพยากรใหม่ด้วยตนเอง) อย่างไรก็ตาม ถือเป็นแนวปฏิบัติที่ดี" + +#: ../../content/administration/install/deploy.rst:447 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" +"เมื่อใช้การกำหนดค่า NGINX (https) ข้างต้น ควรเพิ่มบล็อก ``แผนที่`` และ " +"``สถานที่`` ต่อไปนี้เพื่อให้บริการไฟล์คงที่ผ่าน NGINX" + +#: ../../content/administration/install/deploy.rst:474 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path <odoo-bin " +"--addons-path>`." +msgstr "" +"คำสั่ง ``root`` และ ``try_files`` ที่แท้จริงนั้นขึ้นอยู่กับการติดตั้งของคุณ " +"โดยเฉพาะใน :option:`--addons-path <odoo-bin --addons-path>`" + +#: ../../content/administration/install/deploy.rst:481 +msgid "Debian package" +msgstr "แพ็คเกจ Debian" + +#: ../../content/administration/install/deploy.rst:483 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path <odoo-bin --addons-path>` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" +"สมมติว่า Odoo ได้รับการติดตั้งผ่าน **แพ็คเกจ debian** " +"สำหรับคอมมูนิตี้และองค์กร และ :option:`--addons-path <odoo-bin --addons-" +"path>` คือ ``'/usr/lib/ python3/dist-packages/odoo/addons''``" + +#: ../../content/administration/install/deploy.rst:487 +#: ../../content/administration/install/deploy.rst:501 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "``root`` และ ``try_files`` ควรเป็น:" + +#: ../../content/administration/install/deploy.rst:494 +msgid "Git sources" +msgstr "แหล่งที่มาของ Git" + +#: ../../content/administration/install/deploy.rst:496 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path <odoo-bin --addons-path>` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" +"สมมติว่า Odoo ได้รับการติดตั้งผ่าน **แหล่งที่มา** ซึ่งทั้งที่เก็บคอมไพล์ " +"คอมมูนิตี้และองค์กร ได้รับการโคลนใน :file:`/opt/odoo/community` และ " +":file:`/opt/odoo/enterprise` ตามลำดับ และ :option:`--addons-path <odoo-bin " +"--addons-path>` คือ " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo " +"/enterprise''``." + +#: ../../content/administration/install/deploy.rst:509 +msgid "Serving attachments" +msgstr "ให้บริการไฟล์แนบ" + +#: ../../content/administration/install/deploy.rst:511 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" +"ไฟล์แนบคือไฟล์ที่จัดเก็บไว้ในที่เก็บไฟล์ ซึ่ง Odoo ควบคุมการเข้าถึง " +"ไม่สามารถเข้าถึงได้โดยตรงผ่านทางเว็บเซิร์ฟเวอร์แบบ static " +"เนื่องจากการเข้าถึงไฟล์เหล่านี้จำเป็นต้องมีการค้นหาหลายครั้งในฐานข้อมูลเพื่อพิจารณาว่าไฟล์ถูกจัดเก็บไว้ที่ใด" +" และผู้ใช้ปัจจุบันสามารถเข้าถึงไฟล์เหล่านั้นได้หรือไม่" + +#: ../../content/administration/install/deploy.rst:516 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or " +"`X-Accel " +"<https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile <odoo-bin " +"--x-sendfile>` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" +"อย่างไรก็ตาม เมื่อไฟล์ถูกพบและยืนยันสิทธิ์การเข้าถึงโดย Odoo แล้ว " +"เป็นความคิดที่ดีที่จะให้บริการไฟล์โดยใช้เว็บเซิร์ฟเวอร์แบบ static แทน Odoo " +"เพื่อให้ Odoo มอบหมายการให้บริการไฟล์ไปยังเว็บเซิร์ฟเวอร์แบบคงที่ " +"`X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) หรือ `X-Accel " +"<https://www.nginx.com/ resources/wiki/start/topics/examples/x-accel/>`_ " +"(nginx) จะต้องเปิดใช้งานและกำหนดค่าบนเว็บเซิร์ฟเวอร์แบบ static " +"เมื่อตั้งค่าแล้ว ให้เริ่ม Odoo ด้วย :option:`--x-sendfile <odoo-bin " +"--x-sendfile>` แฟล็ก CLI (แฟล็กเฉพาะนี้ใช้สำหรับทั้ง X-Sendfile และ X-Accel)" + +#: ../../content/administration/install/deploy.rst:526 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" +"ส่วนขยาย X-Sendfile สำหรับ apache (และเว็บเซิร์ฟเวอร์ที่เข้ากันได้) " +"ไม่ต้องการการกำหนดค่าเพิ่มเติมใดๆ" + +#: ../../content/administration/install/deploy.rst:528 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" +"ส่วนขยาย X-Accel สำหรับ NGINX **ไม่** " +"จำเป็นต้องมีการกำหนดค่าเพิ่มเติมต่อไปนี้:" + +#: ../../content/administration/install/deploy.rst:537 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" +"ในกรณีที่คุณไม่ทราบว่าเส้นทางไปยังที่เก็บไฟล์ของคุณคืออะไร ให้เริ่ม Odoo " +"ด้วยตัวเลือก :option:`--x-sendfile <odoo-bin --x-sendfile>` และไปที่ " +"``/web/filestore `` URL โดยตรงผ่าน Odoo (อย่านำทางไปยัง URL ผ่าน NGINX) " +"ซึ่งจะบันทึกคำเตือน ข้อความประกอบด้วยการกำหนดค่าที่คุณต้องการ" + +#: ../../content/administration/install/deploy.rst:546 +msgid "Security" +msgstr "ความปลอดภัย" + +#: ../../content/administration/install/deploy.rst:548 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" +"สำหรับผู้เริ่มต้น " +"โปรดทราบว่าการรักษาความปลอดภัยของระบบข้อมูลนั้นเป็นกระบวนการที่ต่อเนื่อง " +"ไม่ใช่การดำเนินการเพียงครั้งเดียว " +"คุณมีความปลอดภัยเท่าจุดอ่อนที่สุดในสภาพแวดล้อมของคุณเท่านั้น" + +#: ../../content/administration/install/deploy.rst:552 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" +"ดังนั้น " +"โปรดอย่าถือว่าส่วนนี้เป็นรายการมาตรการขั้นสูงสุดที่จะป้องกันปัญหาด้านความปลอดภัยทั้งหมด" +" " +"มีจุดมุ่งหมายเพียงเพื่อสรุปสิ่งสำคัญแรกที่คุณควรรวมไว้ในแผนปฏิบัติการด้านความปลอดภัยของคุณ" +" " +"ส่วนที่เหลือจะมาจากแนวทางปฏิบัติด้านความปลอดภัยที่ดีที่สุดสำหรับระบบปฏิบัติการและการเผยแพร่ของคุณ" +" แนวทางปฏิบัติที่ดีที่สุดในแง่ของผู้ใช้ รหัสผ่าน " +"และการจัดการการควบคุมการเข้าถึง และอื่นๆ" + +#: ../../content/administration/install/deploy.rst:558 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" +"เมื่อปรับใช้เซิร์ฟเวอร์ที่เชื่อมต่อกับอินเทอร์เน็ต " +"โปรดพิจารณาหัวข้อที่เกี่ยวข้องกับความปลอดภัยต่อไปนี้:" + +#: ../../content/administration/install/deploy.rst:561 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" +"ตั้งรหัสผ่านผู้ดูแลระบบระดับสูงที่รัดกุมเสมอ " +"และจำกัดการเข้าถึงหน้าการจัดการฐานข้อมูลทันทีที่ตั้งค่าระบบ โปรดดู " +":ref:`db_manager_security`" + +#: ../../content/administration/install/deploy.rst:564 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" +"เลือกการเข้าสู่ระบบที่ไม่ซ้ำกันและรหัสผ่านที่รัดกุมสำหรับบัญชีผู้ดูแลระบบทั้งหมดในทุกฐานข้อมูล" +" อย่าใช้ 'ผู้ดูแลระบบ' เป็นการเข้าสู่ระบบ " +"อย่าใช้การล็อกอินเหล่านั้นสำหรับการดำเนินงานในแต่ละวัน " +"เพียงเพื่อการควบคุม/จัดการการติดตั้งเท่านั้น *ห้าม* ใช้รหัสผ่านเริ่มต้นใดๆ " +"เช่น ผู้ดูแลระบบ/ผู้ดูแลระบบ แม้แต่กับฐานข้อมูลการทดสอบ/ชั่วคราวก็ตาม" + +#: ../../content/administration/install/deploy.rst:569 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" +"**อย่า** ติดตั้งข้อมูลสาธิตบนเซิร์ฟเวอร์ที่เชื่อมต่อกับอินเทอร์เน็ต " +"ฐานข้อมูลที่มีข้อมูลสาธิตประกอบด้วยการเข้าสู่ระบบและรหัสผ่านเริ่มต้นที่สามารถใช้เพื่อเข้าสู่ระบบของคุณและก่อให้เกิดปัญหาร้ายแรง" +" แม้แต่ในระบบชั่วคราว/การพัฒนา" + +#: ../../content/administration/install/deploy.rst:573 +msgid "" +"Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-" +"filter>`) to restrict the visibility of your databases according to the " +"hostname. See :ref:`db_filter`. You may also use :option:`-d <odoo-bin -d>` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" +"ใช้ตัวกรองฐานข้อมูลที่เหมาะสม ( :option:`--db-filter <odoo-bin --db-" +"filter>`) เพื่อจำกัดการมองเห็นฐานข้อมูลของคุณตามชื่อโฮสต์ โปรดดู " +":ref:`db_filter` คุณยังอาจใช้ :option:`-d <odoo-bin -d>` " +"เพื่อจัดทำรายการฐานข้อมูลที่มีอยู่ (คั่นด้วยเครื่องหมายจุลภาค) " +"ของคุณเองเพื่อกรอง แทนที่จะปล่อยให้ระบบดึงข้อมูลทั้งหมดจากแบ็กเอนด์ฐานข้อมูล" + +#: ../../content/administration/install/deploy.rst:580 +msgid "" +"Once your ``db_name`` and ``db_filter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list <odoo-bin --no-database-list>` command-line " +"option)" +msgstr "" +"เมื่อ ``db_name`` และ ``db_filter`` ได้รับการกำหนดค่าแล้ว " +"และตรงกับฐานข้อมูลเดียวต่อชื่อโฮสต์ คุณควรตั้งค่าตัวเลือกการกำหนดค่า " +"``list_db`` เป็น ``False`` เพื่อป้องกันการแสดงรายการฐานข้อมูลทั้งหมด " +"และเพื่อบล็อก เข้าถึงหน้าจอการจัดการฐานข้อมูล (ซึ่งแสดงเป็น :option:`--no-" +"database-list <odoo-bin --no-database-list>` ตัวเลือกบรรทัดคำสั่ง)" + +#: ../../content/administration/install/deploy.rst:586 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --db_user>`) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" +"ตรวจสอบให้แน่ใจว่าผู้ใช้ PostgreSQL (:option:`--db_user <odoo-bin " +"--db_user>`) เป็น *ไม่ใช่* ผู้ใช้ระดับสูง " +"และฐานข้อมูลของคุณเป็นของผู้ใช้รายอื่น ตัวอย่างเช่น ผู้ใช้ขั้นสูง " +"``postgres`` อาจเป็นเจ้าของได้ หากคุณใช้ ``db_user`` " +"ที่ไม่มีสิทธิพิเศษโดยเฉพาะ ดูเพิ่มเติมที่ :ref:`setup/deploy/odoo`" + +#: ../../content/administration/install/deploy.rst:591 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" +"อัปเดตการติดตั้งอยู่เสมอโดยการติดตั้งบิวด์ล่าสุดเป็นประจำ ไม่ว่าจะผ่าน " +"GitHub หรือโดยการดาวน์โหลดเวอร์ชันล่าสุดจาก " +"https://www.odoo.com/page/download หรือ http://nightly.odoo.com" + +#: ../../content/administration/install/deploy.rst:595 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" +"กำหนดค่าเซิร์ฟเวอร์ของคุณในโหมดหลายกระบวนการด้วยขีดจำกัดที่เหมาะสมซึ่งตรงกับการใช้งานทั่วไปของคุณ" +" (หน่วยความจำ/CPU/หมดเวลา) ดูเพิ่มเติม :ref:`builtin_server`" + +#: ../../content/administration/install/deploy.rst:598 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode <odoo-bin --proxy-mode>` option. See also " +":ref:`https_proxy`." +msgstr "" +"เรียกใช้ Odoo ด้านหลังเว็บเซิร์ฟเวอร์ที่ให้การยกเลิก HTTPS ด้วยใบรับรอง SSL " +"ที่ถูกต้อง เพื่อป้องกันการดักฟังการสื่อสารข้อความที่ชัดเจน ใบรับรอง SSL " +"มีราคาถูกและมีตัวเลือกฟรีมากมาย กำหนดค่าเว็บพร็อกซีเพื่อจำกัดขนาดของคำขอ " +"ตั้งค่าการหมดเวลาที่เหมาะสม จากนั้นเปิดใช้งานตัวเลือก :option:`proxy mode " +"<odoo-bin --proxy-mode>` ดูเพิ่มเติม :ref:`https_proxy`" + +#: ../../content/administration/install/deploy.rst:605 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" +"หากคุณต้องการอนุญาตให้เข้าถึง SSH ระยะไกลไปยังเซิร์ฟเวอร์ของคุณ " +"ตรวจสอบให้แน่ใจว่าได้ตั้งรหัสผ่านที่รัดกุมสำหรับบัญชี **ทั้งหมด** ไม่ใช่แค่ " +"`root` " +"ขอแนะนำอย่างยิ่งให้ปิดการใช้งานการตรวจสอบสิทธิ์โดยใช้รหัสผ่านโดยสิ้นเชิง " +"และอนุญาตเฉพาะการตรวจสอบสิทธิ์กุญแจสาธารณะเท่านั้น นอกจากนี้ " +"ให้พิจารณาจำกัดการเข้าถึงผ่าน VPN โดยอนุญาตเฉพาะ IP " +"ที่เชื่อถือได้ในไฟร์วอลล์ และ/หรือใช้งานระบบตรวจจับแบบ brute-force เช่น " +"`fail2ban` หรือเทียบเท่า" + +#: ../../content/administration/install/deploy.rst:611 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" +"พิจารณาติดตั้งการจำกัดอัตราที่เหมาะสมบนพร็อกซีหรือไฟร์วอลล์ของคุณ " +"เพื่อป้องกันการโจมตีแบบ brute-force และการโจมตีแบบปฏิเสธบริการ ดูเพิ่มเติม " +":ref:`login_brute_force` สำหรับมาตรการเฉพาะ" + +#: ../../content/administration/install/deploy.rst:615 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" +"ผู้ให้บริการเครือข่ายหลายรายจัดให้มีการบรรเทาการโจมตีแบบ Distributed Denial " +"of Service (DDOS) โดยอัตโนมัติ แต่มักเป็นบริการเสริม " +"ดังนั้นคุณควรปรึกษากับผู้ให้บริการเครือข่ายเหล่านั้น" + +#: ../../content/administration/install/deploy.rst:619 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" +"เมื่อใดก็ตามที่เป็นไปได้ " +"ให้โฮสต์อินสแตนซ์การสาธิต/การทดสอบ/การแสดงแบบสาธารณะของคุณบนเครื่องที่แตกต่างจากเครื่องที่ใช้งานจริง" +" และใช้มาตรการรักษาความปลอดภัยเช่นเดียวกับการผลิต" + +#: ../../content/administration/install/deploy.rst:623 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"<http://0pointer.net/blog/ip-accounting-and-access-lists-with-" +"systemd.html>`_ may also be useful to implement per-process network access " +"control." +msgstr "" +"หากเซิร์ฟเวอร์ Odoo " +"แบบสาธารณะของคุณสามารถเข้าถึงทรัพยากรเครือข่ายภายในหรือบริการที่ละเอียดอ่อน " +"(เช่น ผ่าน VLAN ส่วนตัว) ให้ใช้กฎไฟร์วอลล์ที่เหมาะสม " +"เพื่อปกป้องทรัพยากรภายในเหล่านั้น สิ่งนี้จะช่วยให้แน่ใจว่าเซิร์ฟเวอร์ Odoo " +"จะไม่ถูกใช้โดยไม่ได้ตั้งใจ (หรือเป็นผลมาจากการกระทำของผู้ใช้ที่เป็นอันตราย) " +"เพื่อเข้าถึงหรือรบกวนทรัพยากรภายในเหล่านั้น โดยทั่วไปสามารถทำได้โดยใช้กฎ " +"DENY เริ่มต้นขาออกบนไฟร์วอลล์ " +"จากนั้นให้อนุญาตเฉพาะการเข้าถึงทรัพยากรภายในที่เซิร์ฟเวอร์ Odoo " +"ต้องการเข้าถึงอย่างชัดเจนเท่านั้น `การควบคุมการเข้าถึงการรับส่งข้อมูล " +"Systemd IP <http://0pointer.net/blog/ip-accounting-and-access-lists-with-" +"systemd.html>`_ " +"อาจมีประโยชน์ในการใช้การควบคุมการเข้าถึงเครือข่ายต่อกระบวนการ" + +#: ../../content/administration/install/deploy.rst:634 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" +"หากเซิร์ฟเวอร์ Odoo แบบสาธารณะของคุณอยู่ด้านหลังไฟร์วอลล์แอปพลิเคชันบนเว็บ, " +"โหลดบาลานเซอร์, บริการป้องกัน DDoS ที่โปร่งใส (เช่น CloudFlare) " +"หรืออุปกรณ์ระดับเครือข่ายที่คล้ายกัน คุณอาจต้องการหลีกเลี่ยงการเข้าถึงระบบ " +"Odoo โดยตรง โดยทั่วไป การเก็บที่อยู่ IP ปลายทางของเซิร์ฟเวอร์ Odoo " +"ของคุณไว้เป็นความลับนั้นเป็นเรื่องยาก ตัวอย่างเช่น " +"อาจปรากฏในบันทึกของเว็บเซิร์ฟเวอร์เมื่อสืบค้นระบบสาธารณะ " +"หรือในส่วนหัวของอีเมลที่โพสต์จาก Odoo ในสถานการณ์เช่นนี้ " +"คุณอาจต้องการกำหนดค่าไฟร์วอลล์ของคุณเพื่อไม่ให้เข้าถึงจุดสิ้นสุดแบบสาธารณะ " +"ยกเว้นจากที่อยู่ IP เฉพาะของ WAF, โหลดบาลานเซอร์ หรือบริการพร็อกซีของคุณ " +"ผู้ให้บริการเช่น CloudFlare มักจะรักษารายการสาธารณะของช่วงที่อยู่ IP " +"ของตนเพื่อจุดประสงค์นี้" + +#: ../../content/administration/install/deploy.rst:645 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" +"หากคุณโฮสต์ลูกค้าหลายราย " +"ให้แยกข้อมูลและไฟล์ของลูกค้าออกจากกันโดยใช้คอนเทนเนอร์หรือเทคนิค " +"\"การกักขัง\" ที่เหมาะสม" + +#: ../../content/administration/install/deploy.rst:648 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" +"ตั้งค่าการสำรองข้อมูลรายวันของฐานข้อมูลและข้อมูลพื้นที่จัดเก็บไฟล์ของคุณ " +"และคัดลอกไปยังเซิร์ฟเวอร์การเก็บถาวรระยะไกลที่ไม่สามารถเข้าถึงได้จากเซิร์ฟเวอร์เอง" + +#: ../../content/administration/install/deploy.rst:651 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" +"ขอแนะนำอย่างยิ่งให้ปรับใช้ Odoo บน Linux บน Windows " +"หากคุณเลือกที่จะปรับใช้บนแพลตฟอร์ม Windows " +"ควรดำเนินการตรวจสอบการรักษาความปลอดภัยอย่างเข้มงวดของเซิร์ฟเวอร์และอยู่นอกเหนือขอบเขตของคู่มือนี้" + +#: ../../content/administration/install/deploy.rst:659 +msgid "Blocking Brute Force Attacks" +msgstr "การปิดกั้นการโจมตีแบบ Brute Force" + +#: ../../content/administration/install/deploy.rst:661 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" +"สำหรับการปรับใช้ผ่านอินเทอร์เน็ต การโจมตีแบบ bruteforce " +"ต่อรหัสผ่านผู้ใช้เป็นเรื่องปกติมาก " +"และภัยคุกคามนี้ไม่ควรละเลยสำหรับเซิร์ฟเวอร์ Odoo ทั้งนี้ Odoo " +"ปล่อยรายการบันทึกทุกครั้งที่พยายามเข้าสู่ระบบ และรายงานผลลัพธ์: " +"สำเร็จหรือไม่สำเร็จ พร้อมทั้งการเข้าสู่ระบบเป้าหมายและ IP ต้นทาง" + +#: ../../content/administration/install/deploy.rst:665 +msgid "The log entries will have the following form." +msgstr "รายการบันทึกจะมีแบบฟอร์มดังต่อไปนี้" + +#: ../../content/administration/install/deploy.rst:667 +msgid "Failed login::" +msgstr "เข้าสู่ระบบไม่สำเร็จ::" + +#: ../../content/administration/install/deploy.rst:671 +msgid "Successful login::" +msgstr "เข้าสู่ระบบสำเร็จ::" + +#: ../../content/administration/install/deploy.rst:676 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" +"บันทึกเหล่านี้สามารถวิเคราะห์ได้อย่างง่ายดายด้วยระบบป้องกันการบุกรุก เช่น " +"`fail2ban`" + +#: ../../content/administration/install/deploy.rst:678 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" +"ตัวอย่างเช่น ข้อกำหนดตัวกรอง failed2ban " +"ต่อไปนี้ควรตรงกับการเข้าสู่ระบบที่ไม่สำเร็จ::" + +#: ../../content/administration/install/deploy.rst:685 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "สามารถใช้กับคำจำกัดความของคุกเพื่อป้องกัน IP ที่ถูกโจมตีบน HTTP(S)" + +#: ../../content/administration/install/deploy.rst:687 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" +"ต่อไปนี้คือลักษณะที่ปรากฏสำหรับการบล็อก IP เป็นเวลา 15 นาที " +"เมื่อตรวจพบการพยายามเข้าสู่ระบบที่ไม่สำเร็จเกินกว่า 10 ครั้งจาก IP " +"เดียวกันภายใน 1 นาที::" + +#: ../../content/administration/install/deploy.rst:701 +msgid "Database Manager Security" +msgstr "ความปลอดภัยของผู้จัดการฐานข้อมูล" + +#: ../../content/administration/install/deploy.rst:703 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr ":ref:`setup/deploy/odoo` กล่าวถึง ``admin_passwd`` ในการผ่าน" + +#: ../../content/administration/install/deploy.rst:705 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" +"การตั้งค่านี้ใช้กับหน้าจอการจัดการฐานข้อมูลทั้งหมด (เพื่อสร้าง ลบ ดัมพ์ " +"หรือกู้คืนฐานข้อมูล)" + +#: ../../content/administration/install/deploy.rst:708 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" +"หากหน้าจอการจัดการต้องไม่สามารถเข้าถึงได้เลย " +"คุณควรตั้งค่าตัวเลือกการกำหนดค่า ``list_db`` เป็น ``False`` " +"เพื่อบล็อกการเข้าถึงการเลือกฐานข้อมูลและหน้าจอการจัดการทั้งหมด" + +#: ../../content/administration/install/deploy.rst:714 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" +"ขอแนะนำอย่างยิ่งให้ปิดการใช้งานตัวจัดการฐานข้อมูลสำหรับระบบที่เชื่อมต่อกับอินเทอร์เน็ต!" +" มีไว้เพื่อเป็นเครื่องมือในการพัฒนา/สาธิต " +"เพื่อให้ง่ายต่อการสร้างและจัดการฐานข้อมูลอย่างรวดเร็ว " +"ไม่ได้ออกแบบมาเพื่อใช้ในการผลิต " +"และอาจเปิดเผยฟีเจอร์ที่เป็นอันตรายแก่ผู้โจมตีด้วยซ้ำ " +"นอกจากนี้ยังไม่ได้ออกแบบมาเพื่อจัดการกับฐานข้อมูลขนาดใหญ่ " +"และอาจทำให้เกิดขีดจำกัดของหน่วยความจำ" + +#: ../../content/administration/install/deploy.rst:720 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" +"ในระบบที่ใช้งานจริง ผู้ดูแลระบบควรดำเนินการจัดการฐานข้อมูลเสมอ " +"รวมถึงการจัดเตรียมฐานข้อมูลใหม่และการสำรองข้อมูลอัตโนมัติ" + +#: ../../content/administration/install/deploy.rst:723 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``db_filter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" +"ตรวจสอบให้แน่ใจว่าได้ตั้งค่าพารามิเตอร์ ``db_name`` ที่เหมาะสม " +"(และเป็นทางเลือก ``db_filter`` ด้วย) " +"เพื่อให้ระบบสามารถระบุฐานข้อมูลเป้าหมายสำหรับแต่ละคำขอ " +"ไม่เช่นนั้นผู้ใช้จะถูกบล็อกเนื่องจากจะไม่ได้รับอนุญาตให้เลือก " +"ฐานข้อมูลนั้นเอง" + +#: ../../content/administration/install/deploy.rst:728 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" +"หากต้องเข้าถึงหน้าจอการจัดการได้จากชุดเครื่องที่เลือกเท่านั้น " +"ให้ใช้ฟีเจอร์ของพร็อกซีเซิร์ฟเวอร์เพื่อบล็อกการเข้าถึงทุกเส้นทางที่ขึ้นต้นด้วย" +" ``/web/database`` ยกเว้น (อาจจะ) ``/web/database/selector`` " +"ซึ่งแสดงหน้าจอการเลือกฐานข้อมูล" + +#: ../../content/administration/install/deploy.rst:732 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" +"หากควรปล่อยให้หน้าจอการจัดการฐานข้อมูลสามารถเข้าถึงได้ การตั้งค่า " +"``admin_passwd`` จะต้องเปลี่ยนจากค่าเริ่มต้น ``admin``: " +"รหัสผ่านนี้จะถูกตรวจสอบก่อนที่จะอนุญาตการดำเนินการแก้ไขฐานข้อมูล" + +#: ../../content/administration/install/deploy.rst:736 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "ควรเก็บไว้อย่างปลอดภัย และควรสร้างขึ้นแบบสุ่ม เช่น" + +#: ../../content/administration/install/deploy.rst:742 +msgid "which will generate a 32 characters pseudorandom printable string." +msgstr "ซึ่งจะสร้างสตริงที่สามารถพิมพ์แบบสุ่มเทียมได้ 32 ตัวอักษร" + +#: ../../content/administration/install/deploy.rst:745 +msgid "Supported Browsers" +msgstr "เบราว์เซอร์ที่รองรับ" + +#: ../../content/administration/install/deploy.rst:747 +msgid "" +"Odoo supports all the major desktop and mobile browsers available on the " +"market, as long as they are supported by their publishers." +msgstr "" +"Odoo รองรับเบราว์เซอร์เดสก์ท็อปและมือถือหลักทั้งหมดที่มีอยู่ในตลาด " +"เท่าที่ได้รับการสนับสนุนจากผู้เผยแพร่" + +#: ../../content/administration/install/deploy.rst:750 +msgid "Here are the supported browsers:" +msgstr "นี่คือเบราว์เซอร์ที่รองรับ:" + +#: ../../content/administration/install/deploy.rst:752 +msgid "Google Chrome" +msgstr "Google Chrome" + +#: ../../content/administration/install/deploy.rst:753 +msgid "Mozilla Firefox" +msgstr "Mozilla Firefox" + +#: ../../content/administration/install/deploy.rst:754 +msgid "Microsoft Edge" +msgstr "Microsoft Edge" + +#: ../../content/administration/install/deploy.rst:755 +msgid "Apple Safari" +msgstr "Apple Safari" + +#: ../../content/administration/install/deploy.rst:757 +msgid "" +"Please make sure your browser is up-to-date and still supported by its " +"publisher before filing a bug report." +msgstr "" +"โปรดตรวจสอบให้แน่ใจว่าเบราว์เซอร์ของคุณเป็นเวอร์ชันล่าสุดและยังคงได้รับการสนับสนุนโดยผู้เผยแพร่ก่อนที่จะยื่นรายงานข้อบกพร่อง" + +#: ../../content/administration/install/deploy.rst:762 +msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." +msgstr "ตั้งแต่ Odoo 13.0 จึงรองรับ ES6 ดังนั้นการสนับสนุน IE จึงถูกยกเลิก" + +#: ../../content/administration/install/deploy.rst:765 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" +"เพื่อให้การติดตั้ง Odoo หลายรายการใช้ฐานข้อมูล PostgreSQL เดียวกัน " +"หรือเพื่อจัดหาทรัพยากรการประมวลผลเพิ่มเติมให้กับซอฟต์แวร์ทั้งสอง" + +#: ../../content/administration/install/deploy.rst:768 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" +"ในทางเทคนิคแล้ว เครื่องมืออย่าง socat_ สามารถใช้กับซ็อกเก็ตพร็อกซี UNIX " +"ข้ามเครือข่ายได้ แต่ส่วนใหญ่ใช้สำหรับซอฟต์แวร์ที่สามารถใช้ได้ผ่านซ็อกเก็ต " +"UNIX เท่านั้น" + +#: ../../content/administration/install/deploy.rst:772 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" +"หรือสามารถเข้าถึงได้ผ่านเครือข่ายสวิตช์แพ็กเก็ตภายในเท่านั้น " +"แต่ต้องใช้สวิตช์ที่ปลอดภัย การป้องกันการปลอมแปลง ARP และขัดขวางการใช้ WiFi " +"แม้แต่บนเครือข่ายสวิตช์แพ็กเก็ตที่ปลอดภัย ขอแนะนำให้ปรับใช้ผ่าน HTTPS " +"และค่าใช้จ่ายที่เป็นไปได้จะลดลง เนื่องจากใบรับรอง \"ที่ลงนามด้วยตนเอง\" " +"จะปรับใช้ในสภาพแวดล้อมที่มีการควบคุมได้ง่ายกว่าบนอินเทอร์เน็ต" + +#: ../../content/administration/install/email_gateway.rst:3 +msgid "Email gateway" +msgstr "เกตเวย์อีเมล" + +#: ../../content/administration/install/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" +"เกตเวย์อีเมลของ Odoo ช่วยให้คุณสามารถแทรกอีเมลที่ได้รับทั้งหมดลงใน Odoo " +"ได้โดยตรง" + +#: ../../content/administration/install/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" +"มีหลักการตรงไปตรงมา: เซิร์ฟเวอร์ SMTP ของคุณรันสคริปต์ \"mailgate\" " +"สำหรับอีเมลขาเข้าใหม่ทุกฉบับ" + +#: ../../content/administration/install/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" +"สคริปต์จะดูแลการเชื่อมต่อกับฐานข้อมูล Odoo ของคุณผ่าน XML-RPC " +"และส่งอีเมลผ่านฟีเจอร์ `MailThread.message_process()`" + +#: ../../content/administration/install/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "ข้อกำหนดเบื้องต้น" + +#: ../../content/administration/install/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "ผู้ดูแลระบบเข้าถึงฐานข้อมูล Odoo" + +#: ../../content/administration/install/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "เมลเซิร์ฟเวอร์ของคุณเอง เช่น Postfix หรือ Exim" + +#: ../../content/administration/install/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "ความรู้ทางเทคนิคเกี่ยวกับวิธีกำหนดค่าเซิร์ฟเวอร์อีเมล" + +#: ../../content/administration/install/email_gateway.rst:21 +msgid "For Postfix" +msgstr "สำหรับ Postfix" + +#: ../../content/administration/install/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "ในการกำหนดค่านามแฝงของคุณ (:file:`/etc/aliases`):" + +#: ../../content/administration/install/email_gateway.rst:30 +#: ../../content/administration/install/email_gateway.rst:45 +msgid "Resources" +msgstr "แหล่งข้อมูล" + +#: ../../content/administration/install/email_gateway.rst:32 +msgid "`Postfix <http://www.postfix.org/documentation.html>`_" +msgstr "`Postfix <http://www.postfix.org/documentation.html>`_" + +#: ../../content/administration/install/email_gateway.rst:33 +msgid "`Postfix aliases <http://www.postfix.org/aliases.5.html>`_" +msgstr "`Postfix aliases <http://www.postfix.org/aliases.5.html>`_" + +#: ../../content/administration/install/email_gateway.rst:34 +msgid "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_" +msgstr "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_" + +#: ../../content/administration/install/email_gateway.rst:38 +msgid "For Exim" +msgstr "สำหรับ Exim" + +#: ../../content/administration/install/email_gateway.rst:47 +msgid "`Exim <https://www.exim.org/docs.html>`_" +msgstr "`Exim <https://www.exim.org/docs.html>`_" + +#: ../../content/administration/install/email_gateway.rst:50 +msgid "" +"If you don't have access/manage your email server, use :ref:`inbound " +"messages <email_communication/inbound_messages>`." +msgstr "" +"หากคุณไม่มีสิทธิ์เข้าถึง/จัดการเซิร์ฟเวอร์อีเมลของคุณ ให้ใช้ " +":ref:`ข้อความขาเข้า <email_communication/inbound_messages>`" + +#: ../../content/administration/install/geo_ip.rst:3 +msgid "Geo IP" +msgstr "Geo IP" + +#: ../../content/administration/install/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "เอกสารนี้ใช้กับฐานข้อมูลภายในองค์กรเท่านั้น" + +#: ../../content/administration/install/geo_ip.rst:9 +msgid "Installation" +msgstr "การติดตั้ง" + +#: ../../content/administration/install/geo_ip.rst:11 +msgid "" +"Download both the GeoLite2 City and Country `databases " +"<https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with " +"two files called :file:`GeoLite2-City.mmdb` and " +":file:`GeoLite2-Country.mmdb`." +msgstr "" +"ดาวน์โหลดทั้ง `ฐานข้อมูล GeoLite2 เมืองและประเทศ " +"<https://dev.maxmind.com/geoip/geoip2/geolite2/>`_ คุณควรจะมีสองไฟล์ชื่อ " +":file:`GeoLite2-City.mmdb` และ :file:`GeoLite2-Country.mmdb`" + +#: ../../content/administration/install/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "ย้ายไฟล์ไปยังโฟลเดอร์ :file:`/usr/share/GeoIP/`" + +#: ../../content/administration/install/geo_ip.rst:22 +msgid "Restart the server" +msgstr "รีสตาร์ทเซิร์ฟเวอร์" + +#: ../../content/administration/install/geo_ip.rst:25 +msgid "" +"If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`," +" use the :option:`--geoip-city-db <odoo-bin --geoip-city-db>` and " +":option:`--geoip-country-db <odoo-bin --geoip-country-db>` options of the " +"Odoo command line interface. These options take the absolute path to the " +"GeoIP database file and use it as the GeoIP database. For example:" +msgstr "" +"หากคุณไม่ต้องการค้นหาฐานข้อมูล geoip ใน :file:`/usr/share/GeoIP/` ให้ใช้ " +":option:`--geoip-city-db <odoo-bin --geoip-city-db> ` และ :option:`--geoip-" +"country-db <odoo-bin --geoip-country-db>` ตัวเลือกของอินเทอร์เฟซบรรทัดคำสั่ง" +" Odoo ตัวเลือกเหล่านี้ใช้เส้นทางที่แน่นอนไปยังไฟล์ฐานข้อมูล GeoIP " +"และใช้เป็นฐานข้อมูล GeoIP ตัวอย่างเช่น:" + +#: ../../content/administration/install/geo_ip.rst:36 +msgid ":doc:`CLI documentation </developer/reference/cli>`." +msgstr ":doc:`เอกสารของ CLI </developer/reference/cli>`." + +#: ../../content/administration/install/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "ทดสอบตำแหน่งทางภูมิศาสตร์ GeoIP ในเว็บไซต์ Odoo ของคุณ" + +#: ../../content/administration/install/geo_ip.rst:41 +msgid "" +"Edit a web page to include some geo-ip information such as the country name " +"of the current request IP address. To do so:" +msgstr "" +"แก้ไขหน้าเว็บเพื่อรวมข้อมูลทางภูมิศาสตร์บางส่วน เช่น ชื่อประเทศของที่อยู่ IP" +" คำขอปัจจุบัน โดยทำดังนี้:" + +#: ../../content/administration/install/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "ไปที่เว็บไซต์ของคุณ เปิดหน้าเว็บที่คุณต้องการทดสอบ ``GeoIP``" + +#: ../../content/administration/install/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "เลือก :menuselection:`ปรับแต่ง --> ตัวแก้ไข HTML/CSS/JS`" + +#: ../../content/administration/install/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "เพิ่มส่วนต่อไปนี้ของ XML ในหน้า:" + +#: ../../content/administration/install/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "บันทึกและรีเฟรชเพจ" + +#: ../../content/administration/install/geo_ip.rst:54 +msgid "" +"Geo-ip is working if you read your country name displayed in bold in the " +"middle of the page." +msgstr "" +"Geo-ip ใช้งานได้หากคุณอ่านชื่อประเทศของคุณที่แสดงเป็นตัวหนาตรงกลางหน้า" + +#: ../../content/administration/install/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" +"ในกรณีที่คุณอ่านว่า \"**geoip ไม่สำเร็จ**\" " +"แสดงว่าการระบุตำแหน่งทางภูมิศาสตร์ที่ไม่สำเร็จ สาเหตุที่พบบ่อยคือ:" + +#: ../../content/administration/install/geo_ip.rst:58 +msgid "" +"The browsing IP address is the localhost (``127.0.0.1``) or a local area " +"network one. If you don't know, you can access your website using mobile " +"data." +msgstr "" +"ที่อยู่ IP ของการเรียกดูคือ localhost (`` 127.0.0.1``) หรือเครือข่ายท้องถิ่น" +" หากคุณไม่ทราบ คุณสามารถเข้าถึงเว็บไซต์ของคุณโดยใช้ข้อมูลมือถือ" + +#: ../../content/administration/install/geo_ip.rst:60 +msgid "" +"You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't " +"start Odoo with the proxy-mode enabled. See :option:`proxy mode <odoo-bin " +"--proxy-mode>`." +msgstr "" +"คุณกำลังใช้ Reverse-proxy (apache, nginx) หน้า Odoo แต่ไม่ได้เริ่ม Odoo " +"โดยเปิดใช้งานโหมดพร็อกซี โปรดดู :option:`โหมดพร็อกซี <odoo-bin --proxy-" +"mode>`" + +#: ../../content/administration/install/geo_ip.rst:62 +msgid "" +"The GeoIP database is corrupt, missing or unaccessible. In such case a " +"warning was logged in the server logs." +msgstr "" +"ฐานข้อมูล GeoIP เสียหาย สูญหาย หรือไม่สามารถเข้าถึงได้ ในกรณีเช่นนี้ " +"คำเตือนจะถูกบันทึกไว้ในบันทึกของเซิร์ฟเวอร์" + +#: ../../content/administration/install/online.rst:3 +msgid "Online" +msgstr "ออนไลน์" + +#: ../../content/administration/install/online.rst:5 +msgid "" +"Online instances are accessed using any web browser and do not require a " +"local installation." +msgstr "" +"อินสแตนซ์ออนไลน์เข้าถึงได้โดยใช้เว็บเบราว์เซอร์ใดก็ได้ " +"และไม่จำเป็นต้องติดตั้งในเครื่อง" + +#: ../../content/administration/install/online.rst:8 +msgid "Demo" +msgstr "สาธิต" + +#: ../../content/administration/install/online.rst:10 +msgid "" +"To quickly try out Odoo, shared `demo <https://demo.odoo.com>`_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" +"หากต้องการลองใช้ Odoo อย่างรวดเร็ว อินสแตนซ์ `demo <https://demo.odoo.com>`_" +" ที่แชร์ก็พร้อมใช้งาน ไม่จำเป็นต้องลงทะเบียน " +"แต่แต่ละอินสแตนซ์ใช้งานได้เพียงไม่กี่ชั่วโมงเท่านั้น" + +#: ../../content/administration/install/online.rst:14 +#: ../../content/administration/maintain/domain_names.rst:166 +#: ../../content/administration/maintain/domain_names.rst:236 +#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:90 +#: ../../content/administration/upgrade.rst:307 +msgid "Odoo Online" +msgstr "Odoo Online" + +#: ../../content/administration/install/online.rst:16 +msgid "" +"`Odoo Online <https://www.odoo.com/trial>`_ provides private instances which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" +"`Odoo Online <https://www.odoo.com/trial>`_ " +"มอบอินสแตนซ์ส่วนตัวที่ได้รับการจัดการและโฮสต์โดย Odoo อย่างสมบูรณ์ " +"สามารถใช้สำหรับการผลิตในระยะยาวหรือทดสอบ Odoo อย่างละเอียด " +"รวมถึงการปรับแต่งที่ไม่ต้องใช้โค้ด" + +#: ../../content/administration/install/online.rst:21 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "Odoo Online เข้ากันไม่ได้กับโมดูลแบบกำหนดเองหรือ Odoo App Store" + +#: ../../content/administration/install/packages.rst:3 +msgid "Packaged installers" +msgstr "ตัวติดตั้งแบบแพ็คเกจ" + +#: ../../content/administration/install/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" +"Odoo มีตัวติดตั้งแบบแพ็คเกจสำหรับการกระจาย Linux ที่ใช้ Debian (Debian, " +"Ubuntu และอื่นๆ), การกระจาย Linux บน RPM (Fedora, CentOS, RHEL และอื่นๆ) และ" +" Windows สำหรับฉบับคอมมูนิตี้และองค์กร" + +#: ../../content/administration/install/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"<https://nightly.odoo.com>`_." +msgstr "" +"แพ็คเกจ Nightly **คอมมูนิตี้** อย่างเป็นทางการ " +"พร้อมข้อกำหนดการพึ่งพาที่เกี่ยวข้องทั้งหมดมีอยู่ใน `เซิร์ฟเวอร์ Nightly " +"<https://nightly.odoo.com>`_" + +#: ../../content/administration/install/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "แพ็คเกจ Nightly อาจติดตามข้อมูลได้ยาก" + +#: ../../content/administration/install/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page <https://www.odoo.com/page/download>`_." +msgstr "" +"สามารถดาวน์โหลดแพ็คเกจ **คอมมูนิตี้** และ **องค์กร** อย่างเป็นทางการได้จาก " +"`หน้าดาวน์โหลด Odoo <https://www.odoo.com/page/download>`_" + +#: ../../content/administration/install/packages.rst:19 +msgid "" +"It is required to be logged in as a paying customer or partner to download " +"the Enterprise packages." +msgstr "" +"จำเป็นต้องเข้าสู่ระบบในฐานะลูกค้าหรือพาร์ทเนอร์แบบชำระเงินเพื่อดาวน์โหลดแพ็คเกจองค์กร" + +#: ../../content/administration/install/packages.rst:25 +#: ../../content/administration/install/source.rst:52 +#: ../../content/administration/install/source.rst:129 +#: ../../content/administration/install/source.rst:152 +#: ../../content/administration/install/source.rst:174 +#: ../../content/administration/install/source.rst:199 +#: ../../content/administration/install/source.rst:228 +#: ../../content/administration/install/source.rst:271 +#: ../../content/administration/install/source.rst:384 +#: ../../content/administration/install/source.rst:446 +msgid "Linux" +msgstr "Linux" + +#: ../../content/administration/install/packages.rst:28 +#: ../../content/administration/install/source.rst:116 +msgid "Prepare" +msgstr "เตรียมพร้อม" + +#: ../../content/administration/install/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL <https://www.postgresql.org/>`_ server to run " +"properly." +msgstr "" +"Odoo ต้องการเซิร์ฟเวอร์ `PostgreSQL <https://www.postgresql.org/>`_ " +"เพื่อให้ทำงานได้อย่างถูกต้อง" + +#: ../../content/administration/install/packages.rst:34 +#: ../../content/administration/install/packages.rst:70 +#: ../../content/administration/install/packages.rst:100 +#: ../../content/administration/install/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "Debian/Ubuntu" + +#: ../../content/administration/install/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" +"การกำหนดค่าเริ่มต้นสำหรับแพ็คเกจ Odoo 'deb' คือการใช้เซิร์ฟเวอร์ PostgreSQL " +"บนโฮสต์เดียวกันกับอินสแตนซ์ Odoo " +"ดำเนินการคำสั่งต่อไปนี้เพื่อติดตั้งเซิร์ฟเวอร์ PostgreSQL:" + +#: ../../content/administration/install/packages.rst:44 +#: ../../content/administration/install/packages.rst:80 +#: ../../content/administration/install/packages.rst:132 +msgid "Fedora" +msgstr "Fedora" + +#: ../../content/administration/install/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" +"ตรวจสอบให้แน่ใจว่าคำสั่ง `sudo` พร้อมใช้งานและได้รับการกำหนดค่าอย่างดี " +"จากนั้นจึงดำเนินการคำสั่งต่อไปนี้เพื่อติดตั้งเซิร์ฟเวอร์ PostgreSQL:" + +#: ../../content/administration/install/packages.rst:57 +#: ../../content/administration/install/source.rst:416 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"<https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"<https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the " +"various versions." +msgstr "" +"`wkhtmltopdf` ไม่ได้ติดตั้งผ่าน **pip** และต้องติดตั้งด้วยตนเองใน `เวอร์ชัน " +"0.12.6 <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ " +"เพื่อรองรับส่วนหัวและส่วนท้าย ตรวจสอบ `wkhtmltopdf wiki " +"<https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ " +"เพื่อดูรายละเอียดเพิ่มเติมเกี่ยวกับเวอร์ชันต่างๆ" + +#: ../../content/administration/install/packages.rst:63 +msgid "Repository" +msgstr "พื้นที่เก็บข้อมูล" + +#: ../../content/administration/install/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" +"Odoo S.A. จัดเตรียมพื้นที่เก็บข้อมูลที่สามารถใช้เพื่อติดตั้งรุ่น " +"**คอมมูนิตี้** โดยการรันคำสั่งต่อไปนี้:" + +#: ../../content/administration/install/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" +"ใช้คำสั่ง `apt-get upgrade` ตามปกติเพื่อให้การติดตั้งเป็นปัจจุบันอยู่เสมอ" + +#: ../../content/administration/install/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "ขณะนี้ไม่มีพื้นที่เก็บข้อมูล nightly สำหรับรุ่นสำหรับองค์กร" + +#: ../../content/administration/install/packages.rst:93 +msgid "Distribution package" +msgstr "แพ็คเกจการจำหน่าย" + +#: ../../content/administration/install/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"<https://www.odoo.com/page/download>`_." +msgstr "" +"แทนที่จะใช้พื้นที่เก็บข้อมูล คุณสามารถดาวน์โหลดแพ็คเกจสำหรับทั้งรุ่น " +"**คอมมูนิตี้** และ **องค์กร** ได้จาก `หน้าดาวน์โหลด Odoo " +"<https://www.odoo.com/page/download>`_" + +#: ../../content/administration/install/packages.rst:103 +msgid "" +"Odoo 17 'deb' package currently supports `Debian Buster " +"<https://www.debian.org/releases/buster/>`_ and `Ubuntu 18.04 " +"<https://releases.ubuntu.com/18.04>`_ or above." +msgstr "" +"ปัจจุบันแพ็คเกจ Odoo 17 'deb' รองรับ `Debian Buster " +"<https://www.debian.org/releases/buster/>`_ และ `Ubuntu 18.04 " +"<https://releases.ubuntu.com/18.04>`_ หรือสูงกว่า" + +#: ../../content/administration/install/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" +"เมื่อดาวน์โหลดแล้ว ให้รันคำสั่งต่อไปนี้ **ในฐานะรูท** เพื่อติดตั้ง Odoo " +"เป็นบริการ สร้างผู้ใช้ PostgreSQL ที่จำเป็น " +"และเริ่มต้นเซิร์ฟเวอร์โดยอัตโนมัติ:" + +#: ../../content/administration/install/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" +"แพ็คเกจ `python3-xlwt` Debian ซึ่งจำเป็นในการส่งออกเป็นรูปแบบ XLS " +"ไม่มีอยู่ใน Debian Buster หรือ Ubuntu 18.04 หากจำเป็น " +"ให้ติดตั้งด้วยตนเองโดยทำดังนี้:" + +#: ../../content/administration/install/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" +"แพ็คเกจ Python `num2words` ซึ่งจำเป็นสำหรับการแสดงผลจำนวนข้อความ ไม่มีอยู่ใน" +" Debian Buster หรือ Ubuntu 18.04 ซึ่งอาจทำให้เกิดปัญหากับโมดูล `l10n_mx_edi`" +" หากจำเป็น ให้ติดตั้งด้วยตนเองโดยทำดังนี้:" + +#: ../../content/administration/install/packages.rst:135 +msgid "Odoo 17 'rpm' package supports Fedora 36." +msgstr "แพ็คเกจ Odoo 17 'rpm' รองรับ Fedora 36" + +#: ../../content/administration/install/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" +"เมื่อดาวน์โหลดแล้ว สามารถติดตั้งแพ็คเกจได้โดยใช้ตัวจัดการแพ็คเกจ 'dnf':" + +#: ../../content/administration/install/packages.rst:148 +#: ../../content/administration/install/source.rst:70 +#: ../../content/administration/install/source.rst:133 +#: ../../content/administration/install/source.rst:158 +#: ../../content/administration/install/source.rst:180 +#: ../../content/administration/install/source.rst:208 +#: ../../content/administration/install/source.rst:239 +#: ../../content/administration/install/source.rst:324 +#: ../../content/administration/install/source.rst:393 +#: ../../content/administration/install/source.rst:456 +msgid "Windows" +msgstr "Windows" + +#: ../../content/administration/install/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" +"แพ็คเกจ Windows " +"มีไว้เพื่อความสะดวกในการทดสอบหรือเรียกใช้อินสแตนซ์ภายในเครื่องแบบผู้ใช้คนเดียว" +" " +"แต่การปรับใช้งานจริงไม่ได้รับการสนับสนุนเนื่องจากข้อจำกัดและความเสี่ยงหลายประการที่เกี่ยวข้องกับการปรับใช้" +" Odoo บนแพลตฟอร์ม Windows" + +#: ../../content/administration/install/packages.rst:155 +msgid "" +"Download the installer from the `nightly server <https://nightly.odoo.com>`_" +" (Community only) or the Windows installer from the `Odoo download page " +"<https://www.odoo.com/page/download>`_ (any edition." +msgstr "" +"ดาวน์โหลดตัวติดตั้งจาก `เซิร์ฟเวอร์ nightly <https://nightly.odoo.com>`_ " +"(คอมมูนิตี้เท่านั้น) หรือตัวติดตั้ง Windows จาก `หน้าดาวน์โหลด Odoo " +"<https://www.odoo.com/page/download> `_ (ฉบับใดก็ได้" + +#: ../../content/administration/install/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "ดำเนินการไฟล์ที่ดาวน์โหลด" + +#: ../../content/administration/install/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" +"บน Windows 8 และใหม่กว่า คำเตือนชื่อ *Windows protected your PC* " +"อาจแสดงขึ้นมา คลิก **ข้อมูลเพิ่มเติม** จากนั้น **เรียกใช้ต่อไป** " +"เพื่อดำเนินการต่อ" + +#: ../../content/administration/install/packages.rst:164 +msgid "" +"Accept the `UAC <https://en.wikipedia.org/wiki/User_Account_Control>`_ " +"prompt." +msgstr "" +"ยอมรับข้อความแจ้ง `UAC " +"<https://en.wikipedia.org/wiki/User_Account_Control>`_" + +#: ../../content/administration/install/packages.rst:165 +msgid "Go through the installation steps." +msgstr "ทำตามขั้นตอนการติดตั้ง" + +#: ../../content/administration/install/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "Odoo เปิดใช้งานโดยอัตโนมัติเมื่อสิ้นสุดการติดตั้ง" + +#: ../../content/administration/install/source.rst:3 +msgid "Source" +msgstr "แหล่งที่มา" + +#: ../../content/administration/install/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" +"'การติดตั้ง' แหล่งที่มาไม่ได้เกี่ยวกับการติดตั้ง Odoo " +"แต่เป็นการเรียกใช้โดยตรงจากแหล่งที่มาแทน" + +#: ../../content/administration/install/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" +"การใช้แหล่งที่มาของ Odoo จะสะดวกกว่าสำหรับนักพัฒนาโมดูล " +"เนื่องจากเข้าถึงได้ง่ายกว่าการใช้ตัวติดตั้งแบบแพ็คเกจ" + +#: ../../content/administration/install/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters <reference/cmdline>` without " +"needing to edit a configuration file." +msgstr "" +"ทำให้การเริ่มและการหยุด Odoo " +"มีความยืดหยุ่นและชัดเจนมากกว่าบริการที่ตั้งค่าโดยตัวติดตั้งแบบแพ็คเกจ " +"นอกจากนี้ยังอนุญาตให้แทนที่การตั้งค่าโดยใช้ :ref:`พารามิเตอร์บรรทัดคำสั่ง " +"<reference/cmdline>` โดยไม่จำเป็นต้องแก้ไขไฟล์การกำหนดค่า" + +#: ../../content/administration/install/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" +"สุดท้ายนี้ ช่วยให้สามารถควบคุมการตั้งค่าของระบบได้ดียิ่งขึ้น " +"และช่วยให้สามารถเก็บ (และเรียกใช้) Odoo " +"หลายเวอร์ชันไว้เคียงข้างกันได้ง่ายขึ้น" + +#: ../../content/administration/install/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/install/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/install/source.rst:24 +msgid "Archive" +msgstr "เก็บถาวร" + +#: ../../content/administration/install/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/install/source.rst:28 +#: ../../content/administration/install/source.rst:34 +msgid "`Odoo download page <https://www.odoo.com/page/download>`_" +msgstr "" + +#: ../../content/administration/install/source.rst:29 +msgid "`GitHub Community repository <https://github.com/odoo/odoo>`_" +msgstr "" + +#: ../../content/administration/install/source.rst:30 +msgid "`Nightly server <https://nightly.odoo.com>`_" +msgstr "" + +#: ../../content/administration/install/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/install/source.rst:35 +msgid "`GitHub Enterprise repository <https://github.com/odoo/enterprise>`_" +msgstr "" + +#: ../../content/administration/install/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/install/source.rst:43 +msgid "" +"It is required to have `Git <https://git-scm.com/>`_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/install/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"</developer/tutorials/getting_started>`." +msgstr "" + +#: ../../content/administration/install/source.rst:56 +#: ../../content/administration/install/source.rst:74 +#: ../../content/administration/install/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/install/source.rst:63 +#: ../../content/administration/install/source.rst:81 +#: ../../content/administration/install/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/install/source.rst:88 +#: ../../content/administration/install/source.rst:141 +#: ../../content/administration/install/source.rst:164 +#: ../../content/administration/install/source.rst:186 +#: ../../content/administration/install/source.rst:213 +#: ../../content/administration/install/source.rst:253 +#: ../../content/administration/install/source.rst:347 +#: ../../content/administration/install/source.rst:405 +#: ../../content/administration/install/source.rst:467 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/install/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/install/source.rst:119 +msgid "Python" +msgstr "Python" + +#: ../../content/administration/install/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/install/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/install/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/install/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"<https://www.python.org/downloads/windows/>`_ and install it." +msgstr "" + +#: ../../content/administration/install/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/install/source.rst:143 +msgid "" +"Use a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts " +"<https://www.macports.org>`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/install/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.7 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/install/source.rst:170 +msgid "" +"Verify that `pip <https://pip.pypa.io>`_ is also installed for this version." +msgstr "" + +#: ../../content/administration/install/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/install/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/install/source.rst:210 +msgid "" +"`Download PostgreSQL <https://www.postgresql.org/download/windows>`_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/install/source.rst:215 +msgid "" +"Use `Postgres.app <https://postgresapp.com>`_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/install/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions <https://postgresapp.com/documentation/cli-tools.html>`_." +msgstr "" + +#: ../../content/administration/install/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/install/source.rst:236 +#: ../../content/administration/install/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/install/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\<version>\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/install/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/install/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/install/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/install/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/install/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/install/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/install/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/install/source.rst:267 +msgid "Dependencies" +msgstr "การขึ้นต่อกัน" + +#: ../../content/administration/install/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/install/source.rst:280 +msgid "" +"For Debian-based systems, the packages are listed in the `debian/control " +"<https://github.com/odoo/odoo/blob/17.0/debian/control>`_ file of the Odoo " +"sources." +msgstr "" + +#: ../../content/administration/install/source.rst:283 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/install/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/install/source.rst:292 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/install/source.rst:295 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/install/source.rst:301 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:305 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/install/source.rst:312 +#: ../../content/administration/install/source.rst:334 +#: ../../content/administration/install/source.rst:353 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv <https://pypi.org/project/virtualenv/>`_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/install/source.rst:316 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/install/source.rst:326 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio <https://visualstudio.microsoft.com/downloads/>`_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/install/source.rst:330 +#: ../../content/administration/install/source.rst:349 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:338 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/install/source.rst:357 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/install/source.rst:367 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)." +msgstr "" + +#: ../../content/administration/install/source.rst:370 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/install/source.rst:376 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/install/source.rst:379 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/install/source.rst:386 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/install/source.rst:387 +#: ../../content/administration/install/source.rst:396 +#: ../../content/administration/install/source.rst:409 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/install/source.rst:395 +msgid "Download and install `nodejs <https://nodejs.org/en/download>`_." +msgstr "" + +#: ../../content/administration/install/source.rst:402 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/install/source.rst:407 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"<https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)." +msgstr "" + +#: ../../content/administration/install/source.rst:424 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/install/source.rst:426 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/install/source.rst:429 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"<reference/cmdline/server>` or a :ref:`configuration file " +"<reference/cmdline/config>`." +msgstr "" + +#: ../../content/administration/install/source.rst:433 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/install/source.rst:437 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/install/source.rst:439 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/install/source.rst:440 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/install/source.rst:442 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/install/source.rst:453 +#: ../../content/administration/install/source.rst:474 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/source.rst:463 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/install/source.rst:477 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/install/source.rst:482 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users/manage_users>`." +msgstr "" + +#: ../../content/administration/install/source.rst:483 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user <odoo-bin -r>` CLI argument." +msgstr "" + +#: ../../content/administration/install/source.rst:487 +msgid "" +":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`" +msgstr "" + +#: ../../content/administration/maintain.rst:5 +msgid "Maintain" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:3 +msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:5 +msgid "" +"Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order " +"to send and receive secure emails from a custom domain, all that is required" +" is to configure a few settings on the Azure platform and on the back end of" +" the Odoo database. This configuration works with either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:11 +msgid "" +"`Microsoft Learn: Register an application with the Microsoft identity " +"platform <https://learn.microsoft.com/azure/active-" +"directory/develop/quickstart-register-app>`_" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:15 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/outlook`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:19 +msgid "Setup in Microsoft Azure Portal" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:22 +msgid "Create a new application" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:24 +msgid "" +"To get started, go to `Microsoft's Azure Portal " +"<https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook " +"Office 365` account if there is one, otherwise log in with the personal " +":guilabel:`Microsoft account`. A user with administrative access to the " +"Azure Settings will need to connect and perform the following configuration." +" Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID`" +" (formally *Azure Active Directory*)." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:30 +msgid "" +"Now, click on :guilabel:`Add (+)`, located in the top menu, and then select " +":guilabel:`App registration`. On the :guilabel:`Register an application` " +"screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. " +"Under the :guilabel:`Supported account types` section select " +":guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID " +"directory - Multitenant) and personal Microsoft accounts (e.g. Skype, " +"Xbox)`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:36 +msgid "" +"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " +"platform, and then input `https://<odoo base url>/microsoft_outlook/confirm`" +" in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at " +"which your Odoo instance can be reached in the URL field." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:41 +msgid "" +"*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the " +"database's subdomain, assuming it's hosted on Odoo.com" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:44 +msgid "" +"After the URL has been added to the field, :guilabel:`Register` the " +"application so it is created." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:47 +msgid "API permissions" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:49 +msgid "" +"The :guilabel:`API permissions` should be set next. Odoo will need specific " +"API permissions to be able to read (IMAP) and send (SMTP) emails in the " +"Microsoft 365 setup. First, click the :guilabel:`API permissions` link, " +"located in the left menu bar. Next, click on the :guilabel:`(+) Add a " +"Permission` button and select :guilabel:`Microsoft Graph` under " +":guilabel:`Commonly Used Microsoft APIs`. After, select the " +":guilabel:`Delegated Permissions` option." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:55 +msgid "" +"In the search bar, search for the following :guilabel:`Deregulated " +"permissions` and click :guilabel:`Add permissions` for each one:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:58 +msgid ":guilabel:`SMTP.Send`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:59 +msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:62 +msgid "The :guilabel:`User.Read` permission will be added by default." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"API permissions needed for Odoo integration are listed under the Microsoft " +"Graph." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:69 +msgid "Assign users and groups" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:71 +msgid "" +"After adding the API permissions, navigate back to the :guilabel:`Overview` " +"of the :guilabel:`Application` in the top of the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:74 +msgid "" +"Now, add users to this application. Under the :guilabel:`Essentials` " +"overview table, click on the link labeled :guilabel:`Managed Application in " +"Local Directory`, or the last option on the bottom right-hand side of the " +"table." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "" +"Add users/groups by clicking the Managed application in local directory link for the\n" +"created application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:83 +msgid "" +"In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click " +"on :guilabel:`(+) Add User/Group`. Depending on the account, either a " +":guilabel:`Group` and a :guilabel:`User` can be added, or only " +":guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` " +"to be added." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:88 +msgid "" +"Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None " +"Selected` and add the users or group of users that will be sending emails " +"from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the " +"users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to " +"the application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:94 +msgid "Create credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:96 +msgid "" +"Now that the Microsoft Azure app is set up, credentials need to be created " +"for the Odoo setup. These include the :guilabel:`Client ID` and " +":guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied" +" from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or" +" :guilabel:`Application ID` is located under the :guilabel:`Display Name` in" +" the :guilabel:`Essentials` overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Application/Client ID located in the Overview of the app." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:106 +msgid "" +"Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this" +" value, click on :guilabel:`Certificates & Secrets` in the left sidebar " +"menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do" +" this, click on the :guilabel:`(+) New Client Secret` button." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:110 +msgid "" +"A window on the right will populate with a button labeled :guilabel:`Add a " +"client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or " +"something recognizable, and then set the :guilabel:`expiration date`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:115 +msgid "" +"A new :guilabel:`Client Secret` will need to be produced and configured if " +"the first one expires. In this event, there could be an interruption of " +"service, so the expiration date should be noted and set to the furthest " +"possible date." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:119 +msgid "" +"Next, click on :guilabel:`Add` when these two values are entered. A " +":guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. " +"It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret " +"Value` into a notepad as it will become encrypted after leaving this page. " +"The :guilabel:`Secret ID` is not needed." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Client Secret Value or Value in the app's credentials." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:128 +msgid "" +"After these steps, the following items should be ready to be set up in Odoo:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:130 +msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:131 +msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:133 +msgid "" +"This completes the setup on the :guilabel:`Microsoft Azure Portal` side." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:136 +#: ../../content/administration/maintain/google_oauth.rst:111 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:139 +msgid "Enter Microsoft Outlook credentials" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:141 +msgid "" +"First, open the Odoo database and navigate to the :guilabel:`Apps` module. " +"Then, remove the :guilabel:`Apps` filter from the search bar and type in " +"`Outlook`. After that, install the module called :guilabel:`Microsoft " +"Outlook`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:145 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` is checked. This populates a new option for" +" :guilabel:`Outlook Credentials`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:149 +msgid ":guilabel:`Save` the progress." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:151 +msgid "" +"Then, copy and paste the :guilabel:`Client ID` (Application ID) and " +":guilabel:`Client Secret (Client Secret Value)` into the respective fields " +"and :guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Outlook Credentials in Odoo General Settings." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:159 +#: ../../content/administration/maintain/google_oauth.rst:127 +msgid "Configure outgoing email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:161 +msgid "" +"On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email " +"Servers` setting, click the :guilabel:`Outgoing Email Servers` link to " +"configure the Microsoft account." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:164 +msgid "" +"Then, create a new email server and check the box for :guilabel:`Outlook`. " +"Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft " +"Outlook email :guilabel:`Username`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:167 +msgid "" +"If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain " +"or email address <email_communication/default>`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:170 +msgid "Then, click on :guilabel:`Connect your Outlook account`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:172 +msgid "" +"A new window from Microsoft opens to complete the :guilabel:`authorization " +"process`. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Permission page to grant access between newly created app and Odoo." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:179 +msgid "" +"Then, allow Odoo to access the Microsoft account by clicking on " +":guilabel:`Yes`. After this, the page will navigate back to the newly " +"configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration " +"automatically loads the :guilabel:`token` in Odoo, and a tag stating " +":guilabel:`Outlook Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Valid Outlook Token indicator." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:188 +msgid "" +"Finally, click :guilabel:`Test Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Microsoft" +" Outlook using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:194 +msgid "Configuration with a single outgoing mail server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:196 +msgid "" +"Configuring a single outgoing server is the simplest configuration available" +" for Microsoft Azure and it doesn't require extensive access rights for the " +"users in the database." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:199 +msgid "" +"A generic email address would be used to send emails for all users within " +"the database. For example it could be structured with a `notifications` " +"alias (`notifications@example.com`) or `contact` alias " +"(`contact@example.com`). This address must be set as the :guilabel:`FROM " +"Filtering` on the server. This address must also match the " +"`{mail.default.from}@{mail.catchall.domain}` key combination in the system " +"parameters." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:206 +#: ../../content/administration/maintain/azure_oauth.rst:247 +msgid "" +"For more information on the from filter visit: " +":ref:`email_communication/default`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:209 +#: ../../content/administration/maintain/azure_oauth.rst:254 +msgid "" +"The :guilabel:`System Parameters` can be accessed by activating " +":ref:`developer-mode` in the :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:212 +msgid "" +"When using this configuration, every email that is sent from the database " +"will use the address of the configured `notification` mailbox. However it " +"should be noted that the name of the sender will appear but their email " +"address will change:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst-1 +msgid "Name from real sender with static email." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:221 +msgid "Single outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:223 +msgid "" +"Outgoing mail server **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:224 +msgid "" +"Outgoing mail server :guilabel:`FROM Filtering` = " +"`notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:225 +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "`mail.catchall.domain` in system parameters = `example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:226 +#: ../../content/administration/maintain/azure_oauth.rst:280 +msgid "`mail.default.from` in system parameters = `notifications`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:229 +msgid "User-specific (multiple user) configuration" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:231 +msgid "" +"In addition to a generic email server, individual email servers can be set " +"up for users in a database. These email addresses must be set as the " +":guilabel:`FROM Filtering` on each individual server for this configuration " +"to work." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:235 +msgid "" +"This configuration is the more difficult of the two Microsoft Azure " +"configurations, in that it requires all users configured with email servers " +"to have access rights to settings in order to establish a connection to the " +"email server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:240 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "ตั้งค่า" + +#: ../../content/administration/maintain/azure_oauth.rst:242 +msgid "" +"Each user should have a separate email server set up. The :guilabel:`FROM " +"Filtering` should be set so that only the user's email is sent from that " +"server. In other words, only a user with an email address that matches the " +"set :guilabel:`FROM Filtering` is able to use this server." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:249 +msgid "" +"A :ref:`fallback server <azure_oauth/notifications>` must be setup to allow " +"for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering`" +" for this server should have the value of the " +"`{mail.default.from}@{mail.catchall.domain}`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:258 +msgid "" +"The configuration for this transactional email server can work alongside an " +"outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the " +"mass-mailing email server can remain empty, but it's require to be added in " +"the settings of the *Email Marketing* application." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:263 +msgid "" +"For more information on setting the mass-mailing email server visit " +":ref:`email_communication/mass_mails`." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:267 +msgid "Multiple user outgoing mail server configuration:" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "User #1 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:270 +msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:271 +msgid "" +"Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "User #2 mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:273 +msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:274 +msgid "" +"Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "Notifications mailbox" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:276 +msgid "" +"Outgoing mail server #3 **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:277 +msgid "" +"Outgoing mail server #3 :guilabel:`FROM Filtering` = " +"`notifications@example.com`" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:279 +msgid "System Parameters" +msgstr "พารามิเตอร์ของระบบ" + +#: ../../content/administration/maintain/azure_oauth.rst:283 +msgid "Configure incoming email server" +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:285 +msgid "" +"The incoming account should be configured in a similar way to the outgoing " +"email account. Navigate to the :guilabel:`Incoming Mail Servers` in the " +":guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check" +" or Select the button next to :guilabel:`Outlook Oauth Authentication` and " +"enter the :guilabel:`Microsoft Outlook username`. Click on " +":guilabel:`Connect your Outlook account`. Odoo will state: " +":guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the " +"account. The account should be ready to receive email to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/azure_oauth.rst:293 +msgid ":doc:`../../applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:3 +#: ../../content/administration/maintain/odoo_online.rst:70 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:5 +msgid "" +"A **domain name** works as an address for your website. It makes the " +"Internet much more accessible as it allows users to type a meaningful web " +"address, such as ``www.odoo.com``, rather than its server's IP address with " +"a series of numbers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:9 +msgid "" +"You can use a custom domain name to access your Odoo database and websites:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:11 +msgid "" +"By :ref:`registering a free domain name with Odoo <domain-name/odoo-" +"register>` (for Odoo Online databases)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:13 +msgid "" +"By :ref:`configuring a custom domain that you already own <domain-" +"name/existing>`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:16 +msgid "" +"Odoo Online and Odoo.sh databases, including their websites, use by default " +"a subdomain of ``odoo.com`` for both the URL and the emails (e.g., " +"``https://example.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:20 +msgid "" +"Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:25 +msgid "" +"`Odoo Tutorials: Register a Free Domain Name " +"<https://www.odoo.com/slides/slide/register-a-free-domain-name-1663>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:27 +msgid "" +"`Odoo Quick Tips: Get a free domain name! " +"<https://www.youtube.com/watch?v=eAfgeNOHLP4>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:32 +msgid "About domain names" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:34 +msgid "" +"Having a **good domain name** is as important to your branding as the name " +"of your business or organization as it is the first thing your visitors will" +" notice. We recommend you keep them *simple, short, easy to remember and " +"spell*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:38 +msgid "" +"A **subdomain** is a domain that is a part of another domain. It often " +"refers to the additional part that comes before the main domain name. " +"Traditionally, most websites use the ``www.`` subdomain, but any string of " +"letters can be used as well. You can use subdomains to direct your visitors " +"to other websites than your main website or to specific pages (e.g., " +"``experience.odoo.com`` points to a specific page.)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:44 +msgid "" +"All domain names are referenced in the **Domain Name System**, or **DNS**, " +"which works as a giant directory for the Internet. There are many DNS " +"servers, so any modification to the DNS can take up to 72 hours to propagate" +" worldwide on all servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:51 +msgid "Indexing of domain names by search engines" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:53 +msgid "" +"Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots " +"that explore and analyze the web`) to index all websites and their related " +"domain names. These crawlers discover new URLs thanks to links on known web " +"pages. As a result, search engines should index domain names automatically " +"after a while, as long as their URLs are mentioned elsewhere on the " +"Internet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:58 +msgid "" +"Improving the appearance and positioning of web pages on search engines is a" +" practice named \"Search Engine Optimization\" (SEO)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:62 +msgid "" +"Adding relevant content, optimizing metadata, and building high-quality " +"backlinks can all help improve a website's search engine visibility." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:65 +msgid "" +"Some search engines provide tools for web admins, such as `Google Search " +"Console <https://search.google.com/search-console>`_ and `Bing Webmaster " +"Tools <https://www.bing.com/webmasters>`_, to help you analyze and improve " +"your page ranking. To use these services, you must prove that you are the " +"owner of your domain name. One way to verify the ownership of your domain " +"name is by adding a DNS record. You can do this for :ref:`domain names " +"registered with Odoo <domain-name/odoo-manage>` and for domain names managed" +" by other providers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:74 +msgid ":doc:`/applications/websites/website/pages/seo`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:75 +msgid "" +"`Google Search Console Help - Verify your site ownership " +"<https://support.google.com/webmasters/answer/9008080>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:76 +msgid "" +"`Bing Webmaster Tools - Add and Verify site " +"<https://www.bing.com/webmasters/help/add-and-verify-site-12184f8b>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:81 +msgid "Register a free domain name with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:83 +msgid "" +"You can register a domain name for your Odoo Online database directly from " +"Odoo Website or your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:87 +msgid "" +"Your domain name is **free for one year** if you register it with Odoo!" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:88 +msgid "" +"The domain name is registered with `Gandi <https://www.gandi.net/>`_, the " +"domain name registrar." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:90 +msgid "" +"You are the owner of the domain name and can use it for other purposes." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:91 +msgid "Odoo manages payment and technical support for you." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:92 +msgid "" +"This offer doesn't include any mailbox. However, you can :ref:`configure " +"your MX records <domain-name/odoo-manage>` to use your own email server or " +"solution such as Google Workspace." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:95 +msgid "" +"To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, " +"open your `database manager <https://www.odoo.com/my/databases>`_, click on " +"the :guilabel:`settings` button next to your database, then on " +":guilabel:`Domain names`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Clicking on Domain Names from an Odoo website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:103 +msgid "" +"Search for the domain name of your choice to check its availability, then " +"select the one you want to register for your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "" +"The search of the domain name example.com shows which associated domains are" +" available." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:110 +msgid "" +"Next, fill in the form with your information to become the domain name " +"owner." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:112 +msgid "" +"Your domain name is directly linked to your database, but you still have to " +":ref:`map your domain name with your website <domain-name/website-map>`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:116 +msgid "" +"Free domain names are also available for free Odoo Online databases (if you " +"installed one app only, for example). In this case, Odoo reviews your " +"request and your website to avoid abuse. This process can take several days " +"due to the success of the offer." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:119 +msgid "This is not available for Odoo.sh databases yet." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:124 +msgid "Manage your domain name registered with Odoo" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:126 +msgid "" +"To manage the DNS records of your domain name registered with Odoo or to " +"visualize the contacts associated with it, open your `database manager " +"<https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` " +"button next to your database, on :guilabel:`Domain names`, and then on " +":guilabel:`Contacts` or :guilabel:`DNS`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Management of the domain names linked to an Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:136 +msgid "" +"Please `submit a support ticket <https://www.odoo.com/help>`_ if you need " +"further assistance to manage your domain name." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:142 +msgid "Configure your existing domain name" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:144 +msgid "" +"If you already own a domain name, you can use it to point to your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:146 +msgid "" +"To avoid any issue with the :ref:`SSL certificate validation <domain-" +"name/ssl>`, we highly recommend that you proceed with the following actions " +"in this order:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:149 +msgid "" +":ref:`Add a CNAME record <domain-name/cname>` on your domain name's DNS " +"zone." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:150 +msgid "" +":ref:`Map your domain name with your Odoo database <domain-name/db-map>`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:151 +msgid "" +":ref:`Map your domain name with your Odoo website <domain-name/website-" +"map>`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:156 +msgid "Add a CNAME record" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:158 +msgid "" +"A **CNAME record** is a type of DNS record that points to the domain of " +"another website rather than directly to an IP address." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:161 +msgid "" +"You need a CNAME record that points to your Odoo database. The requirements " +"are detailed in your database manager." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:168 +msgid "" +"The target address is the current address of your database, as defined at " +"its creation (e.g., ``example.odoo.com``)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:171 +#: ../../content/administration/maintain/domain_names.rst:250 +#: ../../content/administration/maintain/supported_versions.rst:30 +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:173 +msgid "" +"Your project's main address is defined in :menuselection:`Settings --> " +"Project Name`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:175 +msgid "" +"If you want to target a specific branch (production, staging or " +"development), go to :menuselection:`Branches --> select your branch --> " +"Settings --> Custom domains`, and click on :guilabel:`How to set up my " +"domain?`. A message indicates which address your CNAME record should target." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:180 +#: ../../content/administration/maintain/domain_names.rst:222 +msgid "Open your domain name's manager dashboard." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:181 +msgid "" +"Open the **DNS zone** management page for the domain name you want to " +"configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:182 +msgid "Create a **CNAME record** pointing to the address of your database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:184 +msgid "" +"While Odoo suggests creating a CNAME record for your ``www.`` subdomain " +"(``www.example.com``), you can of course use any domain name of your choice," +" with any subdomain (e.g., ``anything.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:189 +msgid "" +"You own the domain name ``example.com``, and you have an Odoo Online " +"database at the address ``example.odoo.com``. You want to access your Odoo " +"database primarily with the domain ``www.example.com`` but also with the " +":ref:`naked domain <domain-name/naked-domain>` ``example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:194 +msgid "" +"To do so, you create a CNAME record for the ``www`` subdomain, with " +"``example.odoo.com`` as the target. The DNS zone manager generates the " +"following rule and adds it to your DNS zone: ``www IN CNAME " +"example.odoo.com.``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:198 +msgid "" +"You also create a redirection from ``example.com`` to ``wwww.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:200 +msgid "Your new DNS records are propagated to all DNS servers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:203 +msgid "Here are some specific guidelines to create a CNAME record:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:205 +msgid "`GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:206 +msgid "" +"`Namecheap " +"<https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-" +"to-create-a-cname-record-for-your-domain>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:207 +msgid "" +"`OVH " +"<https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/#add-" +"a-new-dns-record>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:208 +msgid "" +"`CloudFlare <https://support.cloudflare.com/hc/en-" +"us/articles/360019093151>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:209 +msgid "" +"`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:214 +msgid "Naked domain" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:216 +msgid "" +"A **naked domain** is a domain name that doesn't have any subdomain at the " +"beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:219 +msgid "" +"You may want your naked domain to redirect to your website as some visitors " +"may not type the full domain name to access your website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:223 +msgid "" +"Create a **redirection** from the naked domain (``example.com``) to your " +"main domain name (``www.example.com``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:227 +msgid "" +"Depending on your domain name registrar, this redirection may be already " +"pre-configured." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:232 +msgid "Map your domain name with your Odoo database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:238 +msgid "" +"Open your `database manager <https://www.odoo.com/my/databases>`_, click on " +"the :guilabel:`settings` button next to your database, on :guilabel:`Domain " +"names`, and then on :guilabel:`Use my own domain` at the bottom of the right" +" column." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:242 +msgid "" +"Type the domain name you want to add to this database, then click on " +":guilabel:`Verify` to check if the CNAME record is correctly configured. " +"Once done, click on :guilabel:`I confirm, it's done`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "" +"Verification of the CNAME records of a domain name before mapping it with a " +"database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:252 +msgid "" +"Go to :menuselection:`Branches --> select your branch --> Settings --> " +"Custom domains`, type the domain name you want to add to this database, then" +" click on :guilabel:`Add domain`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:0 +msgid "Mapping a domain name with an Odoo.sh branch" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:260 +msgid "" +":ref:`Odoo.sh branches: settings tab <odoosh-gettingstarted-branches-tabs-" +"settings>`" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:263 +msgid "" +"Make sure to :ref:`add a CNAME record <domain-name/cname>` to your domain " +"name's DNS **before** mapping your domain name with your Odoo database." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:266 +msgid "" +"Failing to do so may impede the validation of the :ref:`SSL certificate " +"<domain-name/ssl>` and would result in a *certificate name mismatch* error. " +"This is often displayed by web browsers as a warning such as *\"Your " +"connection is not private\"*." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:270 +msgid "" +"If this is the case and you have added the domain name to your database's " +"settings less than five days ago, wait 24 hours as the validation may still " +"happen. Otherwise, please `submit a support ticket " +"<https://www.odoo.com/help>`_ including screenshots of your CNAME records." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:277 +msgid "SSL encryption (HTTPS protocol)" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:279 +msgid "" +"**SSL encryption** is an encryption-based Internet security protocol. It " +"allows your visitors to navigate your website through a secure connection, " +"which appears as an ``https://`` protocol at the beginning of your web " +"address, rather than a non-secure ``http://`` protocol." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:283 +msgid "" +"Odoo generates a separate SSL certificate for each domain :ref:`mapped in " +"the database manager <domain-name/db-map>`, using integration with `Let's " +"Encrypt Certificate Authority and ACME protocol " +"<https://letsencrypt.org/how-it-works/>`_." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:288 +msgid "The certificate generation may take up to 24h." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:289 +msgid "" +"Several attempts to validate your certificate are made during the five days " +"following the moment you add your domain name in your database's settings." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:291 +msgid "" +"If you already use another service, you can keep using it or simply change " +"for Odoo." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:296 +msgid "Web base URL of a database" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:299 +msgid "" +"If you have Odoo Website, you can disregard this part and directly :ref:`map" +" your domain name with your website <domain-name/website-map>`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:302 +msgid "" +"The **web base URL** of a database, or **root URL** affects your main " +"website address and all the links sent to your customers (e.g., quotations, " +"portal links, etc.)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:305 +msgid "" +"To configure it, access your Odoo database with your custom address, then " +"log in as an administrator of your database (any user in the *Settings* " +"group) from the login screen." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:309 +msgid "" +"Connecting to your database with the original Odoo subdomain address (e.g., " +"``example.odoo.com`` also updates the web base URL of your database. See " +"below to prevent these automatic updates." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:312 +msgid "" +"Alternatively, you can do it manually. To do so, activate the " +":ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings " +"--> Technical --> System Parameters`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:315 +msgid "" +"Find the key called ``web.base.url`` (or create it if it does not exist) and" +" enter the full address of your website as value, such as " +"``https://www.example.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:319 +msgid "" +"The URL must include the protocol ``https://`` (or ``http://``) and must not" +" end with a slash (``/``)." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:322 +msgid "" +"To prevent the automatic update of the web base URL when an administrator " +"logs in the database, you can create the following System Parameter:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:325 +msgid "key: ``web.base.url.freeze``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:326 +msgid "value: ``True``" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:331 +msgid "Map your domain name with your website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:333 +msgid "" +"Mapping your domain name to your website isn't the same as mapping it with " +"your database:" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:335 +msgid "" +"It defines your domain name as the main one for your website, helping search" +" engines to index your website properly." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:337 +msgid "" +"It defines your domain name as the base URL for your database, including the" +" portal links sent by email to your customers." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:339 +msgid "" +"If you have multiple websites, it maps your domain name with the appropriate" +" website." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:341 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings --> Website " +"Info`. If you have multiple websites, select the one you want to configure." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:344 +msgid "" +"In the :guilabel:`Domain` field, fill in the web address of your website " +"(e.g., ``https://www.example.com``) and click on :guilabel:`Save`." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst-1 +msgid "Configuring https://www.example.com as the Domain of the website" +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:352 +msgid "" +"Mapping your domain name with your Odoo website prevents Google from " +"indexing both your custom domain name ``www.example.com`` and your original " +"odoo database address ``example.odoo.com``." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:355 +msgid "" +"If both addresses are already indexed, it may take some time before Google " +"removes the indexation of the second address. You may also try using the " +"`Google Search Console <https://search.google.com/search-console>`_ to fix " +"this." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:360 +msgid "" +"If you have multiple websites and companies on your database, make sure that" +" you select the right :guilabel:`Company` in the website settings, next to " +"the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as" +" the :ref:`base URL <domain-name/web-base-url>` according to the company in " +"use." +msgstr "" + +#: ../../content/administration/maintain/domain_names.rst:366 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:12 +#: ../../content/administration/maintain/enterprise.rst:31 +#: ../../content/administration/maintain/enterprise.rst:63 +#: ../../content/administration/maintain/enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:17 +#: ../../content/administration/maintain/enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../install/source`)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/maintain/enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:3 +msgid "Connect Gmail to Odoo using Google OAuth" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:5 +msgid "" +"Odoo is compatible with Google's OAuth for Gmail. In order to send secure " +"emails from a custom domain, all that is required is to configure a few " +"settings on Google's *Workspace* platform, as well as on the back end of the" +" Odoo database. This configuration works by using either a personal email " +"address or an address created by a custom domain." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:11 +msgid "" +"For more information, visit `Google's documentation " +"<https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:15 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:19 +msgid "Setup in Google" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:22 +msgid "Create a new project" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:24 +msgid "" +"To get started, go to the `Google API Console " +"<https://console.developers.google.com>`_. Log in with your *Google " +"Workspace* account if you have one, otherwise log in with your personal " +"Gmail account (this should match the email address you want to configure in " +"Odoo)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:28 +msgid "" +"After that, click on :guilabel:`Create Project`, located on the far right of" +" the :guilabel:`OAuth consent screen`. If a project has already been created" +" in this account, then the :guilabel:`New Project` option will be located on" +" the top right under the :guilabel:`Select a project` drop-down menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:33 +msgid "" +"On the :menuselection:`New Project` screen, rename the :guilabel:`Project " +"name` to `Odoo` and browse for the :guilabel:`Location`. Set the " +":guilabel:`Location` as the *Google Workspace organization*. If you are " +"using a personal Gmail account, then leave the :guilabel:`Location` as " +":guilabel:`No Organization`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Project Name and Location for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:42 +msgid "Click on :guilabel:`Create` to finish this step." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:45 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:47 +msgid "" +"If the page doesn't redirect to the :menuselection:`User Type` options, " +"click on :guilabel:`OAuth consent screen` in the left menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:50 +msgid "" +"Under :guilabel:`User Type` options, select the appropriate :guilabel:`User " +"Type`, and then click on :guilabel:`Create` again, which will finally " +"navigate to the :menuselection:`Edit app registration` page." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:55 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:59 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:63 +msgid "Edit app registration" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:65 +msgid "Next we will configure the app registration of the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:67 +msgid "" +"On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App " +"information` section, enter `Odoo` in the :guilabel:`App name` field. Select" +" the organization's email address under the :guilabel:`User support` email " +"field." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:71 +msgid "" +"Next, under :menuselection:`App Domain --> Authorized domains`, click on " +":guilabel:`Add Domain` and enter `odoo.com`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:74 +msgid "" +"After that, under the :guilabel:`Developer contact information` section, " +"enter the organization's email address. Google uses this email address to " +"notify the organization about any changes to your project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:78 +msgid "" +"Next, click on the :guilabel:`Save and Continue` button. Then, skip the " +":menuselection:`Scopes` page by scrolling to the bottom and clicking on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:81 +msgid "" +"If continuing in testing mode (External), add the email addresses being " +"configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:85 +msgid "" +"Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to " +"finish setting up the project." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:89 +msgid "Create Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:91 +msgid "" +"Now that the project is set up, credentials should be created, which " +"includes the *Client ID* and *Client Secret*. First, click on " +":guilabel:`Credentials` in the left sidebar menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:94 +msgid "" +"Then, click on :guilabel:`Create Credentials` in the top menu and select " +":guilabel:`OAuth client ID` from the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:97 +msgid "" +"Under :guilabel:`Application Type`, select :guilabel:`Web Application` from " +"the dropdown menu." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:98 +msgid "In the :guilabel:`Name` field, enter `Odoo`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:99 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` label, click the button " +":guilabel:`ADD URI`, and then input " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1`" +" field. Be sure to replace the *yourdbname* part of the URL with the actual " +"Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:102 +msgid "" +"Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID`" +" and :guilabel:`Client Secret`. Finally, copy each generated value for later" +" use when configuring in Odoo, and then navigate to the Odoo database." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Client ID and Client Secret for Google OAuth." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:114 +msgid "Enter Google Credentials" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:116 +msgid "" +"First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove " +"the :guilabel:`Apps` filter from the search bar and type in `Google`. " +"Install the module called :guilabel:`Google Gmail`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:120 +msgid "" +"Next, navigate to :menuselection:`Settings --> General Settings`, and under " +"the :guilabel:`Discuss` section, ensure that the checkbox for " +":guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is " +"checked. This populates a new option for :guilabel:`Gmail Credentials` or " +":guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values " +"into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and " +":guilabel:`Save` the settings." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:129 +msgid "" +"To configure the external Gmail account, return to the top of the " +":guilabel:`Custom Email Servers` setting and then click the " +":guilabel:`Outgoing Email Servers` link." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Configure Outgoing Email Servers in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:136 +msgid "" +"Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email " +"server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the " +"email :guilabel:`Username` (if required)." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:139 +msgid "" +"Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` " +"(under the :guilabel:`Authenticate with` or :guilabel:`Connection` section)." +" Finally, click on :guilabel:`Connect your Gmail Account`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:143 +msgid "" +"A new window labeled :guilabel:`Google` opens to complete the authorization " +"process. Select the appropriate email address that is being configured in " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:146 +msgid "" +"If the email address is a personal account, then an extra step pops up, so " +"click :guilabel:`Continue` to allow the verification and connect the Gmail " +"account to Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:149 +msgid "" +"Then, allow Odoo to access the Google account by clicking on " +":guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates " +"back to the newly configured outgoing email server in Odoo. The " +"configuration automatically loads the token in Odoo, and a tag stating " +":guilabel:`Gmail Token Valid` appears in green." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:158 +msgid "" +"Finally, :guilabel:`Test the Connection`. A confirmation message should " +"appear. The Odoo database can now send safe, secure emails through Google " +"using OAuth authentication." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:162 +msgid "Google OAuth FAQ" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:165 +msgid "Production VS Testing Publishing Status" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:167 +msgid "" +"Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` " +"(instead of :guilabel:`Testing`) will display the following warning message:" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "OAuth is Limited to 100 Sensitive Scope Logins." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:174 +msgid "" +"To correct this warning, navigate to the `Google API Platform " +"<https://console.cloud.google.com/apis/credentials/consent>`_. If the " +":guilabel:`Publishing status` is :guilabel:`In Production`, click " +":guilabel:`Back to Testing` to correct the issue." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:179 +msgid "No Test Users Added" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:181 +msgid "" +"If no test users are added to the OAuth consent screen, then a 403 access " +"denied error will populate." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "403 Access Denied Error." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:188 +msgid "" +"To correct this error, return to the :guilabel:`OAuth consent screen` under " +":guilabel:`APIs & Services` and add test user(s) to the app. Add the email " +"that you are configuring in Odoo." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:192 +msgid "Gmail Module not updated" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:194 +msgid "" +"If the *Google Gmail* module in Odoo has not been updated to the latest " +"version, then a :guilabel:`Forbidden` error message populates." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "" +"Forbidden you don't have the permission to access the requested resource." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:201 +msgid "" +"To correct this error, go to the :menuselection:`Apps` module and clear out " +"the search terms. Then, search for `Gmail` or `Google` and upgrade the " +":guilabel:`Google Gmail` module. Finally, click on the three dots on the " +"upper right of the module and select :guilabel:`Upgrade`." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:206 +msgid "Application Type" +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:208 +msgid "" +"When creating the credentials (OAuth *Client ID* and *Client Secret*), if " +":guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an" +" :guilabel:`Authorization Error` appears." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst-1 +msgid "Error 400 Redirect URI Mismatch." +msgstr "" + +#: ../../content/administration/maintain/google_oauth.rst:215 +msgid "" +"To correct this error, delete the credentials already created and create new" +" credentials, selecting :guilabel:`Web Application` for the " +":guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect " +"URIs`, click :guilabel:`ADD URI` and type: " +"`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure " +"to replace *yourdbname* in the URL with the Odoo database name." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:3 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:5 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:9 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:12 +#: ../../content/administration/maintain/hosting_changes.rst:80 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:15 +#: ../../content/administration/maintain/hosting_changes.rst:83 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:16 +msgid "" +"The database's current version must be :doc:`supported " +"<supported_versions>`." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:18 +msgid "Create a :ref:`duplicate <duplicate_premise>` of the database." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:19 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:20 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:21 +msgid "" +"`Submit a support ticket <https://www.odoo.com/help>`_ including the " +"following:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:23 +#: ../../content/administration/maintain/hosting_changes.rst:88 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:24 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:25 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:27 +#: ../../content/administration/maintain/hosting_changes.rst:95 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:31 +#: ../../content/administration/maintain/hosting_changes.rst:99 +msgid "" +"If you have time constraints, `submit a support ticket " +"<https://www.odoo.com/help>`_ as soon as possible to schedule the transfer." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:35 +#: ../../content/administration/maintain/hosting_changes.rst:67 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:37 +#: ../../content/administration/maintain/hosting_changes.rst:73 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"<odoo_sh_import_your_database>` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:41 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:44 +msgid "" +"Odoo Online's :ref:`intermediary versions <supported_versions>` cannot be " +"hosted on-premise as that type of hosting does not support those versions. " +"Therefore, if the database to transfer is running an intermediary version, " +"it must be upgraded first to the next :ref:`major version " +"<supported_versions>`, waiting for its release if necessary." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:50 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:54 +msgid "" +"Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo " +"Online database manager <https://www.odoo.com/my/databases/>`_ to display " +"its version number." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:58 +#: ../../content/administration/maintain/hosting_changes.rst:108 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:60 +#: ../../content/administration/maintain/hosting_changes.rst:69 +msgid "" +"Sign in to `the Odoo Online database manager " +"<https://www.odoo.com/my/databases/>`_ and click the gear icon " +"(:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. " +"If the download fails due to the file being too large, `contact Odoo support" +" <https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:64 +#: ../../content/administration/maintain/hosting_changes.rst:111 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:77 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:85 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:86 +msgid "" +"`Create a support ticket <https://www.odoo.com/help>`_ including the " +"following:" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:89 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:90 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:91 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:92 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:93 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:101 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:102 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:103 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:105 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/maintain/hosting_changes.rst:110 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"<odoo_sh_branches_backups>`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:3 +msgid "Mailjet API" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:5 +msgid "" +"Odoo is compatible with Mailjet's :abbr:`API (Application Programming " +"Interface)` for mass mailing. Set up a dedicated mass mailing server through" +" Mailjet by configuring settings in the Mailjet account and the Odoo " +"database. In some circumstances, settings need to be configured on the " +"custom domain's :abbr:`DNS (Domain Name System)` settings as well." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:11 +msgid "Set up in Mailjet" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:14 +msgid "Create API credentials" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:16 +msgid "" +"To get started, sign in to the `Mailjet Account Information " +"<https://app.mailjet.com/account>`_ page. Next, navigate to the " +":guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND " +"API Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "" +"SMTP and Send API Settings link in the Senders & Domains section of Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:24 +msgid "" +"Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration " +"settings onto a notepad. They can be found under the " +":guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail " +"Transfer Protocol)` configuration settings include the server address, the " +"security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS " +"(Transport Layer Security)`), and the port number. The settings are needed " +"to configure Mailjet in Odoo, which is covered in the :ref:`last section " +"<maintain/mailjet-api/odoo-setup>`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:32 +msgid "" +"`Mailjet: How can I configure my SMTP parameters? " +"<https://documentation.mailjet.com/hc/articles/360043229473>`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:36 +msgid "" +"Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See " +"reference here <email_servers/restriction>`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "SMTP configuration from Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:43 +msgid "" +"Next, click on the button labeled :guilabel:`Retrieve your API credentials` " +"to retrieve the Mailjet API credentials." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:46 +msgid "" +"Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key" +" to a notepad, as this serves as the :guilabel:`Username` in the Odoo " +"configuration. Next, click on the :guilabel:`Generate Secret Key` button to " +"generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this " +"serves as the :guilabel:`Password` in the Odoo configuration." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:52 +msgid "Add verified sender address(es)" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:54 +msgid "" +"The next step is to add a sender address or a domain to the Mailjet account " +"settings so that the email address or domain is approved to send emails " +"using Mailjet's servers. First, navigate to the `Mailjet Account Information" +" <https://app.mailjet.com/account>`_ page. Next, click on the :guilabel:`Add" +" a Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Add a sender domain or address in the Mailjet interface." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:63 +msgid "" +"Determine if a sender's email address or the entire domain needs to be added" +" to the Mailjet settings. It may be easier to configure the domain as a " +"whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the " +":ref:`Add a domain <maintain/mailjet-api/add-domain>` section for steps on " +"adding the domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:69 +msgid "" +"Either all email addresses of the Odoo database users who are sending emails" +" using Mailjet's servers need to be configured or the domain(s) of the " +"users' email addresses can be configured." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:72 +msgid "" +"By default, the email address originally set up in the Mailjet account is " +"added as a trusted sender. To add another email address, click on the button" +" labeled :guilabel:`Add a sender address`. Then, add the email address that " +"is configured to send from the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:76 +msgid "" +"At minimum the following email addresses should be set up in the provider " +"and verified in Mailjet:" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:78 +msgid "notifications\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:79 +msgid "bounce\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:80 +msgid "catchall\\@yourdomain.com" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:83 +msgid "" +"Replace `yourdomain` with the custom domain for the Odoo database. If there " +"isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:86 +msgid "" +"After that, fill out the :guilabel:`Email Information` form, making sure to " +"select the appropriate email type: transactional email or mass emails. After" +" completing the form, an activation email is sent to the email address and " +"the trusted sender can be activated." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:90 +msgid "" +"It is recommended to set up the :abbr:`SPF (Sender Policy " +"Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, and Conformance)` settings on the " +"domain of the sender." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:95 +#: ../../content/administration/maintain/mailjet_api.rst:162 +msgid "" +"`Mailjet's SPF/DKIM/DMARC documentation " +"<https://documentation.mailjet.com/hc/articles/ 360042412734-Authenticating-" +"Domains-with-SPF-DKIM>`_" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:99 +msgid "" +"If the database is not using a custom domain, then in order to verify the " +"sender's address, a temporary alias (of the three email addresses mentioned " +"above) should be set up in Odoo CRM to create a lead. Then, the database is " +"able to receive the verification email and verify the accounts." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:107 +msgid "Add a domain" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:109 +msgid "" +"By adding an entire domain to the Mailjet account, all the sender addresses " +"related to that domain are automatically validated for sending emails using " +"Mailjet servers. First, navigate to the `Mailjet Account Information " +"<https://app.mailjet.com/account>`_ page. Next, click on :guilabel:`Add a " +"Sender Domain or Address` link under the :guilabel:`Senders & Domains` " +"section. Then, click on :guilabel:`Add domain` to add the custom domain." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:116 +msgid "" +"The domain needs to be added to the Mailjet account and then validated " +"through the :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:119 +msgid "" +"After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and " +"click :guilabel:`Continue`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:122 +msgid "" +"After adding the domain, a validation page will populate. Unless the Odoo " +"database is on-premise (in which case, choose :guilabel:`Option 1`), choose " +":guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information " +"to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name " +"System)` provider to complete validation." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "The TXT record information to input on the domain's DNS." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:132 +msgid "Setup in the domain's DNS" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:134 +msgid "" +"After getting the TXT record information from the Mailjet account, add a TXT" +" record to the domain's :abbr:`DNS (Domain Name System)`. This process " +"varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult " +"the provider for specific configuration processes. The TXT record " +"information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste " +"these into the corresponding fields in the TXT record." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:141 +msgid "Return to Mailjet account information" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:143 +msgid "" +"After adding the TXT record to the domain's :abbr:`DNS (Domain Name " +"System)`, navigate back to the Mailjet account. Then, navigate to " +":menuselection:`Account Information --> Add a Sender Domain or Address`, " +"click the gear icon next to :guilabel:`Domain`, and select " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:147 +msgid "" +"This action can also be done by going to the `Sender domains & addresses " +"<https://app.mailjet.com/ account/sender>`_ page on the Mailjet account " +"information and clicking on :guilabel:`Manage`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:150 +msgid "" +"Next, click :guilabel:`Check Now` to validate the TXT record that was added " +"on the domain. A success screen will appear if the domain is configured " +"correctly." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Check DNS record in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:157 +msgid "" +"After successfully setting up the domain, there is an option to " +":guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates " +":abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified " +"Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Authenticate the domain with SPF/DKIM records in Mailjet." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:172 +msgid "Set up in Odoo" +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:174 +msgid "" +"To complete the setup, navigate to the Odoo database and go to the " +":guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the " +":menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, " +"create a new outgoing server configuration by clicking on the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:179 +msgid "" +"Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or " +"465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet " +"account. They can also be found `here " +"<https://app.mailjet.com/account/setup>`_. It is recommended to use " +":abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` " +"even though Mailjet may not require it." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:184 +msgid "" +"For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the " +":guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from " +"the Mailjet account to the notepad earlier. These settings can be found on " +":menuselection:`Mailjet --> Account Settings --> SMTP and SEND API " +"Settings`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:189 +msgid "" +"Then, if the Mailjet server is used for mass emailing, set the " +":guilabel:`Priority` value higher than that of any transactional email " +"server(s). Finally, save the settings and :guilabel:`Test the Connection`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst-1 +msgid "Odoo outgoing email server settings." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:198 +msgid "" +"In order for the notifications feature to work using Mailjet, there are " +"three settings that need to be set in Odoo." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:201 +msgid "" +"The :guilabel:`From Filter` needs to be set on the server configuration. It " +"is recommended to set it as a domain and not a full email address. It should" +" match the domain in the two proceeding steps. More information can be " +"referenced :ref:`here <email_communication/from_filter>`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:205 +msgid "" +"The :guilabel:`mail.default.from` system parameter must have the value " +"`notifications\\@yourdomain.com`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:207 +msgid "" +"The :guilabel:`mail.default.from_filter` system parameter must have the " +"value `yourdomain.com`. Replace `yourdomain` with the custom domain for the " +"Odoo database. If there isn't one, then use the " +":guilabel:`mail.catchall.domain` system parameter." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:211 +msgid "" +"For more information see :ref:`Using a default email address " +"<email_communication/default>`." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:213 +msgid "" +"The :guilabel:`System Parameters` can be accessed by activating " +":doc:`../../applications/general/developer_mode` in the " +":menuselection:`Settings --> Technical --> Parameters --> System Parameters`" +" menu." +msgstr "" + +#: ../../content/administration/maintain/mailjet_api.rst:217 +msgid "" +"Once the setup is complete, the Odoo database is ready to use the Mailjet " +"email server for mass mailing or transactional emails!" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:3 +msgid "Odoo Online database management" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:5 +msgid "" +"To manage a database, go to the `database manager " +"<https://www.odoo.com/my/databases>`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:8 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:15 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:16 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:17 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:18 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:19 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:20 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:21 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:22 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:23 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:28 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:77 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "อัพเกรด" + +#: ../../content/administration/maintain/odoo_online.rst:30 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:33 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation <upgrade/request-test-database>`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:39 +msgid "Duplicate" +msgstr "คัดลอก" + +#: ../../content/administration/maintain/odoo_online.rst:41 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:45 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:47 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:52 +msgid "Rename" +msgstr "ตั้งชื่อใหม่" + +#: ../../content/administration/maintain/odoo_online.rst:54 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:59 +msgid "Download" +msgstr "ดาวน์โหลด" + +#: ../../content/administration/maintain/odoo_online.rst:61 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:64 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"<https://www.odoo.com/cloud-sla>`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:72 +msgid "" +"Use a custom :doc:`domain name <domain_names>` to access the database via " +"another URL." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:75 +msgid "" +"You can :ref:`register a domain name for free <domain-name/odoo-register>`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:80 +msgid "Tags" +msgstr "แท็ก" + +#: ../../content/administration/maintain/odoo_online.rst:82 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:85 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:90 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "ลบ" + +#: ../../content/administration/maintain/odoo_online.rst:92 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:95 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:98 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:105 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:106 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:107 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"<https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:113 +msgid "Contact us" +msgstr "ติดต่อเรา" + +#: ../../content/administration/maintain/odoo_online.rst:115 +msgid "" +"Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:121 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:123 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:129 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:132 +msgid ":doc:`/applications/general/users/manage_users`" +msgstr "" + +#: ../../content/administration/maintain/odoo_online.rst:133 +msgid ":doc:`/applications/general/users/odoo_account`" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:3 +msgid "On-premise database management" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:6 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:8 +msgid "" +"To register your database, you just need to enter your Subscription Code in " +"the banner in the App Switcher. Make sure you do not add extra spaces before" +" or after your subscription code. If the registration is successful, it will" +" turn green and will provide you with the Expiration Date of your freshly-" +"registered database. You can check this Expiration Date in the About menu " +"(Odoo 9) or in the Settings Dashboard (Odoo 10)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:16 +msgid "Registration Error Message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:18 +msgid "" +"If you are unable to register your database, you will likely encounter this " +"message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"Something went wrong while registering your database, you can try again or contact Odoo\n" +"Help" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:27 +#: ../../content/administration/maintain/on_premise.rst:100 +#: ../../content/administration/maintain/on_premise.rst:127 +msgid "Solutions" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:29 +msgid "Do you have a valid Enterprise subscription?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:31 +msgid "" +"Check if your subscription details get the tag \"In Progress\" on your `Odoo" +" Account <https://accounts.odoo.com/my/subscription>`__ or with your Account" +" Manager" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:35 +msgid "Have you already linked a database with your subscription reference?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:37 +msgid "" +"You can link only one database per subscription. (Need a test or a " +"development database? `Find a partner <https://www.odoo.com/partners>`__)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:41 +msgid "" +"You can unlink the old database yourself on your `Odoo Contract " +"<https://accounts.odoo.com/my/subscription>`__ with the button \"Unlink " +"database\"" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:47 +msgid "" +"A confirmation message will appear; make sure this is the correct database " +"as it will be deactivated shortly:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:53 +msgid "Do you have the updated version of Odoo 9?" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:55 +#: ../../content/administration/maintain/on_premise.rst:159 +msgid "" +"From July 2016 onward, Odoo 9 now automatically change the uuid of a " +"duplicated database; a manual operation is no longer required." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:58 +msgid "" +"If it's not the case, you may have multiple databases sharing the same UUID." +" Please check on your `Odoo Contract " +"<https://accounts.odoo.com/my/subscription>`__, a short message will appear " +"specifying which database is problematic:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:66 +msgid "" +"In this case, you need to change the UUID on your test databases to solve " +"this issue. You will find more information about this in :ref:`this section " +"<duplicate_premise>`." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:69 +msgid "" +"For your information, we identify database with UUID. Therefore, each " +"database should have a distinct UUID to ensure that registration and " +"invoicing proceed effortlessly for your and for us." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:73 +msgid "Check your network and firewall settings" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:75 +msgid "" +"The Update notification must be able to reach Odoo's subscription validation" +" servers. In other words, make sure that the Odoo server is able to open " +"outgoing connections towards:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:79 +msgid "services.odoo.com on port 443 (or 80)" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:80 +msgid "services.openerp.com on port 443 (or 80) for older deployments" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:82 +msgid "" +"Once you activated your database, you must keep these ports open, as the " +"Update notification runs once a week." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:86 +msgid "Error message due to too many users" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:88 +msgid "" +"If you have more users in your local database than provisionned in your Odoo" +" Enterprise subscription, you may encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "" +"This database will expire in X days, you have more users than your " +"subscription allows" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:96 +msgid "" +"When the message appears you have 30 days before the expiration. The " +"countdown is updated everyday." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:102 +msgid "" +"**Add more users** on your subscription: follow the link and Validate the " +"upsell quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:104 +msgid "" +"**Deactivate users** as explained in this `documentation " +"<documentation.html#deactivating-users>`_ and **Reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:107 +msgid "" +"Once your database has the correct number of users, the expiration message " +"will disappear automatically after a few days, when the next verification " +"occurs. We understand that it can be a bit frightening to see the countdown," +" so you can :ref:`force an Update Notification <force_ping>` to make the " +"message disappear right away." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:114 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:116 +msgid "" +"If your database reaches its expiration date before your renew your " +"subscription, you will encounter this message:" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst-1 +msgid "This database has expired." +msgstr "ฐานข้อมูลนี้หมดอายุแล้ว" + +#: ../../content/administration/maintain/on_premise.rst:123 +msgid "" +"This **blocking** message appears after a non-blocking message that lasts 30" +" days. If you fail to take action before the end of the countdown, the " +"database is expired." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:131 +msgid "" +"Renew your subscription: follow the link and renew your subscription - note " +"that" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:130 +msgid "" +"if you wish to pay by Wire Transfer, your subscription will effectively be " +"renewed only when the payment arrives, which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:133 +msgid "Contact our `Support <https://www.odoo.com/help>`__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:135 +msgid "" +"None of those solutions worked for you? Please contact our `Support " +"<https://www.odoo.com/help>`__" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:143 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:145 +msgid "" +"You can duplicate your database by accessing the database manager on your " +"server (<odoo-server>/web/database/manager). In this page, you can easily " +"duplicate your database (among other things)." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:152 +msgid "" +"When you duplicate a local database, it is **strongly** advised to change " +"the duplicated database's uuid (Unniversally Unique Identifier), since this " +"uuid is how your database identifies itself with our servers. Having two " +"databases with the same uuid could result in invoicing problems or " +"registration problems down the line." +msgstr "" + +#: ../../content/administration/maintain/on_premise.rst:162 +msgid "" +"The database uuid is currently accessible from the menu " +":menuselection:`Settings --> Technical --> System Parameters`, we advise you" +" to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix " +"command ``uuidgen`` to generate a new uuid. You can then simply replace it " +"like any other record by clicking on it and using the edit button." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online <odoo_online>` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` " +"them regularly." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:34 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:35 +#: ../../content/administration/maintain/supported_versions.rst:36 +#: ../../content/administration/maintain/supported_versions.rst:37 +#: ../../content/administration/maintain/supported_versions.rst:41 +#: ../../content/administration/maintain/supported_versions.rst:65 +#: ../../content/administration/maintain/supported_versions.rst:66 +#: ../../content/administration/maintain/supported_versions.rst:67 +#: ../../content/administration/maintain/supported_versions.rst:83 +#: ../../content/administration/maintain/supported_versions.rst:84 +#: ../../content/administration/maintain/supported_versions.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 +msgid "|green|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:38 +#: ../../content/administration/maintain/supported_versions.rst:93 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:39 +msgid "November 2026 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:40 +msgid "Odoo saas~16.4" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:42 +#: ../../content/administration/maintain/supported_versions.rst:43 +#: ../../content/administration/maintain/supported_versions.rst:48 +#: ../../content/administration/maintain/supported_versions.rst:49 +#: ../../content/administration/maintain/supported_versions.rst:54 +#: ../../content/administration/maintain/supported_versions.rst:55 +#: ../../content/administration/maintain/supported_versions.rst:60 +#: ../../content/administration/maintain/supported_versions.rst:61 +#: ../../content/administration/maintain/supported_versions.rst:72 +#: ../../content/administration/maintain/supported_versions.rst:73 +#: ../../content/administration/maintain/supported_versions.rst:78 +#: ../../content/administration/maintain/supported_versions.rst:79 +msgid "N/A" +msgstr "ไม่ระบุ" + +#: ../../content/administration/maintain/supported_versions.rst:44 +msgid "August 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:46 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:47 +#: ../../content/administration/maintain/supported_versions.rst:53 +#: ../../content/administration/maintain/supported_versions.rst:59 +#: ../../content/administration/maintain/supported_versions.rst:71 +#: ../../content/administration/maintain/supported_versions.rst:77 +#: ../../content/administration/maintain/supported_versions.rst:89 +#: ../../content/administration/maintain/supported_versions.rst:90 +#: ../../content/administration/maintain/supported_versions.rst:91 +#: ../../content/administration/maintain/supported_versions.rst:95 +#: ../../content/administration/maintain/supported_versions.rst:96 +#: ../../content/administration/maintain/supported_versions.rst:97 +#: ../../content/administration/maintain/supported_versions.rst:101 +#: ../../content/administration/maintain/supported_versions.rst:102 +#: ../../content/administration/maintain/supported_versions.rst:103 +msgid "|red|" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:50 +msgid "June 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:52 +msgid "Odoo saas~16.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:56 +msgid "March 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:58 +msgid "Odoo saas~16.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:62 +msgid "February 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:64 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:68 +#: ../../content/administration/maintain/supported_versions.rst:99 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:69 +msgid "November 2025 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:70 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:74 +msgid "March 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:75 +msgid "January 2023" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:76 +msgid "Odoo saas~15.1" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:80 +msgid "February 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:81 +msgid "July 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:82 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:86 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:87 +msgid "November 2024 (planned)" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:88 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:92 +msgid "October 2020" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:94 +msgid "**Odoo 13.0**" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:98 +msgid "October 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:100 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:104 +msgid "Before 2019" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:105 +msgid "Before 2022" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:107 +msgid "Legend" +msgstr "Legend" + +#: ../../content/administration/maintain/supported_versions.rst:109 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:111 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:113 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/maintain/supported_versions.rst:116 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version <https://upgrade.odoo.com/>`_." +msgstr "" + +#: ../../content/administration/maintain/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/maintain/update.rst:9 +msgid "Introduction" +msgstr "แนะนำ" + +#: ../../content/administration/maintain/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/maintain/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/maintain/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/maintain/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"<https://upgrade.odoo.com>`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" +"หมายถึงการดำเนินการประมวลผลข้อมูลที่ซับซ้อนซึ่งโครงสร้างและเนื้อหาของฐานข้อมูลของคุณได้รับการแก้ไขอย่างถาวรเพื่อให้เข้ากันได้กับ" +" Odoo รุ่นใหม่ การดำเนินการนี้ไม่สามารถย้อนกลับได้ " +"และโดยปกติแล้วจะดำเนินการผ่าน `บริการอัปเกรดฐานข้อมูล " +"<https://upgrade.odoo.com>`_ ของ Odoo เมื่อคุณตัดสินใจเปลี่ยนไปใช้ Odoo " +"รุ่นใหม่กว่า ในอดีต ขั้นตอนนี้เรียกอีกอย่างว่า \"การโยกย้าย\" " +"เนื่องจากเกี่ยวข้องกับการย้ายข้อมูลไปมาภายในฐานข้อมูล " +"แม้ว่าฐานข้อมูลอาจไปอยู่ที่ตำแหน่งจริงเดียวกันหลังจากการอัปเกรดก็ตาม" + +#: ../../content/administration/maintain/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"<https://upgrade.odoo.com>`_ instead." +msgstr "" + +#: ../../content/administration/maintain/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/maintain/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/maintain/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../install>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/maintain/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/maintain/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/maintain/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/maintain/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/maintain/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/maintain/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/maintain/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"<security>` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/maintain/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/maintain/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/maintain/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/maintain/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" +"หากคุณติดตั้ง Odoo ด้วยแพ็คเกจการติดตั้งที่ดาวน์โหลดบนเว็บไซต์ของเรา " +"(วิธีที่แนะนำ) การอัปเดตก็ทำได้ง่ายมาก " +"สิ่งที่คุณต้องทำคือดาวน์โหลดแพ็คเกจการติดตั้งที่สอดคล้องกับระบบของคุณ " +"(ดูขั้นตอนที่ 1) และติดตั้งบนเซิร์ฟเวอร์ของคุณ " +"อัปเดตทุกวันและรวมการแก้ไขความปลอดภัยล่าสุด โดยปกติแล้ว " +"คุณสามารถดับเบิลคลิกที่แพ็คเกจเพื่อติดตั้งทับการติดตั้งปัจจุบันได้ " +"หลังจากติดตั้งแพ็คเกจแล้ว อย่าลืมเริ่มการบริการของ Odoo " +"ใหม่หรือรีบูตเซิร์ฟเวอร์ของคุณ เพียงเท่านี้คุณก็พร้อมแล้ว" + +#: ../../content/administration/maintain/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/maintain/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/maintain/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/maintain/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/maintain/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/maintain/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/maintain/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/maintain/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/maintain/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"<https://hub.docker.com/_/odoo/>`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "ขั้นสูง" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "ภาพรวม" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"<https://pip.pypa.io/en/stable/reference/pip_install/#requirement-" +"specifiers>`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo <https://github.com/odoo/odoo/blob/17.0/requirements.txt>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"<https://help.ubuntu.com/community/LinuxFilesystemTreeOverview#Main_directories>`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"<https://www.postgresql.org/docs/current/static/sql-begin.html>`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"</developer/reference/cli>`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb <https://docs.python.org/3/library/pdb.html>`_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb <https://pypi.org/project/pudb/>`_ or `ipdb " +"<https://pypi.org/project/ipdb/>`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "หรือ" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"<https://stackoverflow.com/a/1077421/3332416>`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:170 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"<odoosh-gettingstarted-settings-submodules>`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git <odoosh-advanced-submodules-" +"withgit>`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "แทนที่" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*<git@yourprovider.com>:<username/repository.git>* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "*<branch>* by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "*<path>* by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +"<remote> by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +"<branch> by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation <https://git-" +"scm.com/book/en/v2/Git-Tools-Submodules>`_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes <https://git-scm.com/book/en/v2/Git-Tools-" +"Submodules#_pulling_in_upstream_changes_from_the_submodule_remote>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "เริ่มเลย" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "สาขา" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "ขั้นตอน" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +msgid "Production" +msgstr "การผลิต" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"</developer/reference/cli>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Development" +msgstr "การพัฒนา" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings <odoosh-gettingstarted-settings-modules-installation>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings <odoosh-" +"gettingstarted-branches-tabs-settings>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "แท็บ" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +msgid "History" +msgstr "ประวัติ" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +msgid "Mails" +msgstr "อีเมล" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "ผู้แก้ไข" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +msgid "Logs" +msgstr "บันทึก" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:109 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us <https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" +"หากคุณรวมคอมมิตที่เปลี่ยนโค้ดบางส่วนโดยไม่มีการแก้ไขที่กล่าวมาข้างต้น " +"Odoo.sh จะไม่มีการสำรองข้อมูล " +"เนื่องจากทั้งคอนเทนเนอร์และฐานข้อมูลไม่ได้รับการแก้ไข " +"ดังนั้นแพลตฟอร์มจึงถือว่าสิ่งนี้ปลอดภัยเพียงพอ เพื่อเป็นการป้องกันไว้ก่อน " +"คุณสามารถสำรองข้อมูลด้วยตนเองก่อนที่จะทำการเปลี่ยนแปลงครั้งใหญ่ในแหล่งที่มาที่ใช้งานจริงของคุณ" +" ในกรณีที่มีสิ่งผิดปกติเกิดขึ้น " +"(การสำรองข้อมูลด้วยตนเองเหล่านี้จะสามารถใช้งานได้ประมาณหนึ่งสัปดาห์) " +"เพื่อหลีกเลี่ยงการละเมิด เราจำกัดการสำรองข้อมูลด้วยตนเองไว้ที่ 5 ครั้งต่อวัน" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view <odoosh-" +"gettingstarted-builds>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:117 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:124 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage <stage_production>`). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" +"สำหรับสาขาการพัฒนาและการจัดเตรียม " +"คุณสามารถเปลี่ยนพฤติกรรมของสาขาเมื่อได้รับคอมมิตใหม่ ตามค่าเริ่มต้น " +"สาขาการพัฒนาจะสร้างบิลด์ใหม่และสาขาการจัดเตรียมจะอัปเดตบิลด์ก่อนหน้า (ดู " +":ref:`ขั้นตอนการผลิต <stage_production>`) " +"สิ่งนี้มีประโยชน์อย่างยิ่งหากฟีเจอร์ที่คุณกำลังทำงานอยู่จำเป็นต้องมีการตั้งค่าหรือการกำหนดค่าเฉพาะ" +" เพื่อหลีกเลี่ยงการตั้งค่าด้วยตนเองอีกครั้งในทุกคอมมิต " +"หากคุณเลือกบิลด์ใหม่สำหรับสาขาการจัดเตรียม " +"มันจะสร้างสำเนาใหม่จากบิลด์ที่ใช้งานจริงทุกครั้งที่มีการส่งคอมมิต " +"สาขาที่เปลี่ยนกลับจากการจัดเตรียมเป็นการพัฒนาจะถูกตั้งค่าเป็น 'ไม่ทำอะไรเลย'" +" โดยอัตโนมัติ" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules <odoosh-advanced-submodules>` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"<developer/reference/testing/selection>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *<name>.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"<https://support.google.com/webmasters/answer/7451184?hl=en>`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"<https://letsencrypt.org/about/>`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF " +"<email_communication/spf_compliant>` and :ref:`DKIM " +"<email_communication/dkim_compliant>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ``<URL>``, ``<PATH>``, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "ผสาน" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key <https://help.github.com/en/github/authenticating-" +"to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-" +"agent#generating-a-new-ssh-key>`_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"<https://help.github.com/en/github/authenticating-to-github/adding-a-new-" +"ssh-key-to-your-github-account>`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "การเชื่อมต่อ" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights <odoosh-gettingstarted-" +"settings-collaborators>` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules <odoosh-" +"advanced-submodules>` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository *<URL>* as a submodule under the " +"path *<PATH>* in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise " +"<https://github.com/odoo/enterprise>`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "ฟีเจอร์" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view <odoosh-gettingstarted-branches-tabs>`: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"<https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version </administration/maintain/supported_versions>` of " +"Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules <odoosh-advanced-submodules>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch <odoosh-" +"gettingstarted-branches-stages>`, or :ref:`merge it into your production " +"branch <odoosh-gettingstarted-branches-mergingbranches>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" <db_manager_security>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"<https://accounts.odoo.com/my/databases/manage>`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode <developer-mode>` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "ลงทะเบียนสมัครสมาชิก" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../maintain/on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh <odoosh-" +"gettingstarted-create>`, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../install/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"<first_module/my_module.zip>` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "ด้วยตนเอง" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/getting_started` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes <odoosh-gettingstarted-online-editor-push>` of the :ref:`Online " +"Editor <odoosh-gettingstarted-online-editor>` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode <developer-mode>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases <odoosh-gettingstarted-firstmodule-" +"productiondata-install>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "หลังจาก" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "เพิ่ม" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "กับ" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"<https://www.odoo.sh/faq#install_dependencies>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"<https://pypi.python.org/pypi/Unidecode>`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "ก่อนหน้า" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"<https://jupyterlab.readthedocs.io/en/stable/user/notebook.html>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"<odoosh-gettingstarted-branches-tabs>`, :ref:`the builds dropdown menu " +"<odoosh-gettingstarted-builds-dropdown-menu>` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo <https://github.com/odoo/odoo>`_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise <https://github.com/odoo/enterprise>`_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes <https://github.com/odoo/design-" +"themes>`_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:<branch>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +"<branch> must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" <https://help.github.com/articles/creating-a-personal-access-token-for-the-" +"command-line/>`_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" +"ไม่ได้ใช้รีโมต SSH Github เนื่องจากคีย์ส่วนตัว SSH " +"ของคุณไม่ได้โฮสต์อยู่ในคอนเทนเนอร์บิลด์ของคุณ " +"(สำหรับข้อกังวลด้านความปลอดภัยที่ชัดเจน) หรือส่งต่อผ่านตัวแทน SSH " +"(เมื่อคุณเข้าถึงตัวแก้ไขนี้ผ่านเว็บเบราว์เซอร์) " +"ดังนั้นคุณจึงไม่สามารถรับรองความถูกต้องของตัวเองกับ Github ใช้ SSH " +"คุณต้องใช้ HTTPS ระยะไกลของที่เก็บ Github ของคุณเพื่อพุชการเปลี่ยนแปลงของคุณ" +" ซึ่งจะถูกเพิ่มชื่อโดยอัตโนมัติเป็น *https* ในรีโมท Git ของคุณ " +"คุณจะได้รับแจ้งให้ป้อนชื่อผู้ใช้และรหัสผ่าน Github ของคุณ " +"หากคุณเปิดใช้งานการตรวจสอบสิทธิ์แบบสองปัจจัยบน Github คุณสามารถสร้าง " +"`โทเค็นการเข้าถึงส่วนบุคคล <https://help.github.com/articles/creating-a-" +"personal-access-token-for-the-command-line/ >`_ และใช้เป็นรหัสผ่าน " +"การให้สิทธิ์ `` repo`` ก็ถือว่าเพียงพอ" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"<odoosh-gettingstarted-branches-tabs-settings>`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"<https://ipython.readthedocs.io/en/stable/interactive/tutorial.html>`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"<https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-" +"display>`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"<https://pandas.pydata.org/pandas-docs/stable/tutorials.html>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"<https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-" +"display>`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas <https://pandas.pydata.org/pandas-" +"docs/stable/tutorials.html>`_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "ผู้ทำงานร่วมกัน" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are two levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid "Admin: has access to all features of Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:39 +msgid "" +"User: does not have access to the project settings nor to the production and" +" staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:41 +msgid "" +"The user group is meant for developers who can make modifications in your " +"code but are not allowed to access the production data. Users of this group " +"cannot connect to the production and staging databases using the *1-click " +"connect* feature, but they can of course use their regular account on these " +"databases if they have one, using their regular credentials." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:46 +msgid "" +"In addition, they cannot use the webshell nor have access to the server " +"logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "User" +msgstr "ผู้ใช้" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Admin" +msgstr "แอดมิน" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:97 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +msgid "Production & Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +msgid "|green|\\*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:120 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "สถานะ" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +msgid "\\* Only in staging branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:145 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:147 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:152 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to connect to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:155 +msgid "" +"In addition, visitors have access to the logs, shell and mails of your " +"development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:157 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:162 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:164 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab <odoosh-gettingstarted-branches-tabs-settings>`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:172 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules <odoosh-advanced-submodules>` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:183 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:188 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:190 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:192 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:193 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:196 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:198 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:200 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:202 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:203 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:204 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:205 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:208 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:210 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:215 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:217 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:219 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:222 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"<https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:225 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:231 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:239 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"<https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:245 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:247 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:254 +msgid "Activation" +msgstr "การเปิดใช้งาน" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:256 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/upgrade.rst:7 +msgid "" +"An upgrade is the process of moving your database from an older version to a" +" newer :doc:`supported version <maintain/supported_versions>` (e.g., Odoo " +"14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes " +"with new and improved features, bug fixes, and security patches." +msgstr "" + +#: ../../content/administration/upgrade.rst:15 +msgid "" +"The Rolling Release process allows Odoo Online customers to upgrade their " +"database directly from a message prompt sent to the database administrator " +"as soon as a new version is released. The invitation to upgrade is only sent" +" if no issues are detected during the automatic tests." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:22 +msgid "" +"It is strongly recommended to manually :ref:`test the upgrade first " +"<upgrade/test_your_db>`. Clicking :guilabel:`I want to test first` redirects" +" to `the database manager <https://www.odoo.com/my/databases/>`_, where it " +"is possible to request an upgraded test database and check it for any " +"discrepancies." +msgstr "" + +#: ../../content/administration/upgrade.rst:27 +msgid "" +"It is **not** recommended to click :guilabel:`Upgrade Now` without testing " +"first, as it immediately triggers the live production database upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:30 +msgid "" +"If the Rolling Release process detects an issue with the upgrade, it will be" +" deactivated until the issue is resolved." +msgstr "" + +#: ../../content/administration/upgrade.rst:33 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:35 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:36 +msgid "" +":doc:`Switching editions <maintain/enterprise>` (e.g., from Community to " +"Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +":doc:`Changing hosting type </administration/maintain/hosting_changes>` " +"(e.g., from on-premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:39 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:42 +msgid "" +"If your database contains custom modules, it cannot be upgraded until a " +"version of your custom modules is available for the target version of Odoo. " +"For customers maintaining their own custom modules, we recommend to " +"parallelize the process by :ref:`requesting an upgraded database " +"<upgrade/request-test-database>` while also :doc:`upgrading the source code " +"of your custom modules </developer/howtos/upgrade_custom_db>`." +msgstr "" + +#: ../../content/administration/upgrade.rst:50 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database <upgrade/request-test-database>`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "" +"If applicable, upgrade the source code of your custom module to be " +"compatible with the new version of Odoo (see " +":doc:`/developer/howtos/upgrade_custom_db`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database <upgrade/test_your_db>`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "" +"Report any issue encountered during the testing to Odoo via the `support " +"page <https://odoo.com/help?stage=migration>`__." +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +msgid "" +"Once all issues are resolved and you are confident that the upgraded " +"database can be used as your main database without any issues, plan the " +"upgrade of your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:67 +msgid "" +"Request the upgrade for the production database, rendering it unavailable " +"for the time it takes to complete the process (see :ref:`upgrading the " +"production database <upgrade/upgrade-prod>`)." +msgstr "" + +#: ../../content/administration/upgrade.rst:70 +msgid "" +"Report any issue encountered during the upgrade to Odoo via the `support " +"page <https://odoo.com/help?stage=post_upgrade>`__." +msgstr "" + +#: ../../content/administration/upgrade.rst:76 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:78 +msgid "" +"The `Upgrade page <https://upgrade.odoo.com/>`_ is the main platform for " +"requesting an upgraded database. However, depending on the hosting type, you" +" can upgrade from the command line (on-premise), the `Odoo Online database " +"manager <https://odoo.com/my/databases>`_, or your `Odoo.sh project " +"<https://odoo.sh/project>`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +msgid "" +"The Upgrade platform follows the same `Privacy Policy " +"<https://www.odoo.com/privacy>`_ as the other Odoo.com services. Visit the " +"`General Data Protection Regulation page <https://www.odoo.com/gdpr>`_ to " +"learn more about how Odoo handles your data and privacy." +msgstr "" + +#: ../../content/administration/upgrade.rst:92 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"<https://odoo.com/my/databases>`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "" +"The database manager displays all databases associated with the user's " +"account. Databases not on the most recent version of Odoo display an arrow " +"in a circle icon next to their name, indicating that they can be upgraded." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:102 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:104 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:105 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:106 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:112 +msgid "" +"The :guilabel:`Upgrade in progress` tag is displayed next to the database " +"name until completion. Once the process succeeds, an email containing a link" +" to the upgraded test database is sent to the address provided. The database" +" can also be accessed from the database manager by clicking the dropdown " +"arrow before the database name." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:122 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:127 +msgid "" +"The **latest production daily automatic backup** is then sent to the " +"`upgrade platform <https://upgrade.odoo.com>`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:130 +msgid "" +"Once the upgrade platform is done upgrading the backup and uploading it on " +"the branch, it is put in a **special mode**: each time a **commit is " +"pushed** on the branch, a **restore operation** of the upgraded backup and " +"an **update of all the custom modules** occur. This allows you to test your " +"custom modules on a pristine copy of the upgraded database. The log file of " +"the upgrade process can be found in your newly upgraded staging build by " +"going to :file:`~/logs/upgrade.log`." +msgstr "" +"เมื่อแพลตฟอร์มอัปเกรดเสร็จสิ้น อัปเกรดการสำรองข้อมูลและอัปโหลดบนสาขา " +"แพลตฟอร์มจะเข้าสู่ **โหมดพิเศษ**: แต่ละครั้งที่มี **การคอมมิทถูกผลัก** " +"บนสาขา **การดำเนินการกู้คืน** ของ การสำรองข้อมูลที่อัปเกรดแล้วและ " +"**การอัปเดตของโมดูลที่กำหนดเองทั้งหมด** จะเกิดขึ้น " +"สิ่งนี้ทำให้คุณสามารถทดสอบโมดูลที่คุณกำหนดเองบนสำเนาฐานข้อมูลที่อัปเกรดแล้ว " +"ไฟล์บันทึกของกระบวนการอัปเกรดสามารถพบได้ในการสร้างขั้นตอนที่อัปเกรดใหม่ของคุณโดยไปที่" +" :file:`~/logs/upgrade.log`" + +#: ../../content/administration/upgrade.rst:138 +msgid "" +"In databases where custom modules are installed, their source code must be " +"up-to-date with the target version of Odoo before the upgrade can be " +"performed. If there are none, the \"update on commit\" mode is skipped, the " +"upgraded database is built as soon as it is transferred from the upgrade " +"platform, and the upgrade mode is exited." +msgstr "" + +#: ../../content/administration/upgrade.rst:143 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:145 +#: ../../content/administration/upgrade.rst:341 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/upgrade.rst:147 +msgid "" +"The standard upgrade process can be initiated by entering the following " +"command line on the machine where the database is hosted:" +msgstr "" + +#: ../../content/administration/upgrade.rst:154 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:160 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"<https://upgrade.odoo.com/>`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:164 +msgid "" +"In databases where custom modules are installed, their source code must be " +"up-to-date with the target version of Odoo before the upgrade can be " +"performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for" +" more information." +msgstr "" + +#: ../../content/administration/upgrade.rst:169 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:170 +msgid "" +"For storage reasons, the database's copy is submitted without a filestore to" +" the upgrade server. Therefore, the upgraded database does not contain the " +"production filestore." +msgstr "" + +#: ../../content/administration/upgrade.rst:172 +msgid "" +"Before restoring the upgraded database, its filestore must be merged with " +"the production filestore to be able to perform tests in the same conditions " +"as it would be in the new version." +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:177 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"A `filestore` folder containing files extracted from in-database records " +"into attachments (if there are any) and new standard Odoo files from the " +"targeted Odoo version (e.g., new images, icons, payment provider's logos, " +"etc.). This is the folder that should be merged with the production " +"filestore in order to get the full upgraded filestore." +msgstr "" + +#: ../../content/administration/upgrade.rst:185 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:190 +msgid "" +"When an upgrade request is completed, an upgrade report is attached to the " +"successful upgrade email, and it becomes available in the Discuss app for " +"users who are part of the \"Administration / Settings\" group. This report " +"provides important information about the changes introduced by the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:198 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:200 +msgid "" +"It is essential to spend some time testing the upgraded test database to " +"ensure that you are not stuck in your day-to-day activities by a change in " +"views, behavior, or an error message once the upgrade goes live." +msgstr "" + +#: ../../content/administration/upgrade.rst:205 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:208 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:209 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +msgid "" +"Bank synchronization is disabled. Should you want to test the " +"synchronization, contact your bank synchronization provider to get sandbox " +"credentials." +msgstr "" + +#: ../../content/administration/upgrade.rst:214 +msgid "" +"Testing as many of your business flows as possible is strongly recommended " +"to ensure they are working correctly and to get more familiar with the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:217 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:219 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:222 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:223 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:224 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:226 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:227 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:228 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:229 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:233 +msgid "" +"Checking a random product in your product catalog and comparing its test and" +" production data to verify everything is the same (product category, selling" +" price, cost price, vendor, accounts, routes, etc.)." +msgstr "" + +#: ../../content/administration/upgrade.rst:236 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:237 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:238 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:243 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:244 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:246 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:247 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:249 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:251 +msgid "" +"Making an online order (Website apps) from the product selection in your " +"shop until the checkout process and checking if everything behaves as in " +"your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:256 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo via the `support page " +"<https://odoo.com/help?stage=migration>`__ by selecting the option related " +"to testing the upgrade. In any case, it is essential to report any problem " +"encountered during the testing to fix it before upgrading your production " +"database." +msgstr "" + +#: ../../content/administration/upgrade.rst:261 +msgid "" +"You might encounter significant differences with standard views, features, " +"fields, and models during testing. Those changes cannot be reverted on a " +"case-by-case basis. However, if a change introduced by a new version breaks " +"a customization, it is the responsibility of the maintainer of your custom " +"module to make it compatible with the new version of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:267 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:270 +msgid "" +"Workflows between different apps (online sales with eCommerce, converting a " +"lead all the way to a sales order, delivery of products, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:273 +msgid "Automated actions" +msgstr "การดำเนินการอัตโนมัติ" + +#: ../../content/administration/upgrade.rst:274 +msgid "" +"Server actions in the action menu on form views, as well as by selecting " +"multiple records on list views" +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +msgid "" +"Once the :ref:`tests <upgrade/test_your_db>` are completed and you are " +"confident that the upgraded database can be used as your main database " +"without any issues, it is time to plan the go-live day. It can be planned in" +" coordination with Odoo's upgrade support analysts, reachable via the " +"`support page <https://odoo.com/help>`__." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"Your production database will be unavailable during its upgrade. Therefore, " +"we recommend planning the upgrade at a time when the use of the database is " +"minimal." +msgstr "" + +#: ../../content/administration/upgrade.rst:290 +msgid "" +"As the standard upgrade scripts and your database are constantly evolving, " +"it is also recommended to frequently request another upgraded test database " +"to ensure that the upgrade process is still successful, especially if it " +"takes a long time to finish. **Fully rehearsing the upgrade process the day " +"before upgrading the production database is also recommended.**" +msgstr "" + +#: ../../content/administration/upgrade.rst:296 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:298 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:299 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:300 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:309 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"<upgrade/request-test-database>`, except for the purpose option, which must " +"be set to :guilabel:`Production` instead of :guilabel:`Test`." +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +msgid "" +"Once the upgrade is requested, the database will be unavailable until the " +"upgrade is finished. Once the process is completed, it is impossible to " +"revert to the previous version." +msgstr "" + +#: ../../content/administration/upgrade.rst:320 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"<upgrade/request-test-database>` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:326 +msgid "" +"The process is **triggered as soon as a new commit is made** on the branch. " +"This allows the upgrade process to be synchronized with the deployment of " +"the custom modules' upgraded source code. If there are no custom modules, " +"the upgrade process is triggered immediately." +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The database is unavailable throughout the process. If anything goes wrong, " +"the platform automatically reverts the upgrade, as it would be for a regular" +" update. In case of success, a backup of the database before the upgrade is " +"created." +msgstr "" + +#: ../../content/administration/upgrade.rst:336 +msgid "" +"The update of your custom modules must be successful to complete the entire " +"upgrade process. Make sure the status of your staging upgrade is " +":guilabel:`successful` before trying it in production. More information on " +"how to upgrade your custom modules can be found on " +":doc:`/developer/howtos/upgrade_custom_db`." +msgstr "" + +#: ../../content/administration/upgrade.rst:343 +msgid "" +"The command to upgrade a database to production is similar to the one of " +"upgrading a test database except for the argument `test`, which must be " +"replaced by `production`:" +msgstr "" + +#: ../../content/administration/upgrade.rst:350 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"<https://upgrade.odoo.com/>`_. Once the database is uploaded, any " +"modification to your production database will **not** be present on your " +"upgraded database. This is why we recommend not using it during the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:357 +msgid "" +"When requesting an upgraded database for production purposes, the copy is " +"submitted without a filestore. Therefore, the upgraded database filestore " +"must be merged with the production filestore before deploying the new " +"version." +msgstr "" + +#: ../../content/administration/upgrade.rst:361 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo via the `support page " +"<https://odoo.com/help?stage=post_upgrade>`__ by selecting the option " +"related to the upgrade in production." +msgstr "" + +#: ../../content/administration/upgrade.rst:369 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:371 +msgid "" +"With Odoo Enterprise, upgrading a database to the most recent version of " +"Odoo is **free**, including any support required to rectify potential " +"discrepancies in the upgraded database." +msgstr "" + +#: ../../content/administration/upgrade.rst:374 +msgid "" +"Information about the upgrade services included in the Enterprise Licence is" +" available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. " +"However, this section clarifies what upgrade services you can expect." +msgstr "" + +#: ../../content/administration/upgrade.rst:379 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:381 +msgid "" +"Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or " +"self-hosted (On-Premise) can benefit from upgrade services at all times for:" +msgstr "" + +#: ../../content/administration/upgrade.rst:384 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:385 +msgid "" +"the upgrade of all **customizations created with the Studio app**, as long " +"as Studio is still installed and the respective subscription is still " +"active; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:387 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:390 +msgid "" +"Upgrade services are limited to the technical conversion and adaptation of a" +" database (standard modules and data) to make it compatible with the version" +" targeted by the upgrade." +msgstr "" + +#: ../../content/administration/upgrade.rst:394 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:396 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:398 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "" +"the upgrade of **custom modules created in-house or by third parties**, " +"including Odoo partners;" +msgstr "" + +#: ../../content/administration/upgrade.rst:400 +msgid "" +"lines of **code added to standard modules**, i.e., customizations created " +"outside the Studio app, code entered manually, and :ref:`automated actions " +"using Python code <studio/automated-actions/action>`; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:403 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:406 +msgid ":doc:`Odoo.sh documentation <odoo_sh>`" +msgstr "" + +#: ../../content/administration/upgrade.rst:407 +msgid ":doc:`Supported Odoo versions <maintain/supported_versions>`" +msgstr "" diff --git a/locale/th/LC_MESSAGES/applications.po b/locale/th/LC_MESSAGES/applications.po new file mode 100644 index 000000000..5dc3c5b9c --- /dev/null +++ b/locale/th/LC_MESSAGES/applications.po @@ -0,0 +1,26 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-11-08 08:46+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications.rst:9 +msgid "User Docs" +msgstr "" + +#: ../../content/applications.rst:11 +msgid "Discover our user guides and configuration tutorials per application." +msgstr "" diff --git a/locale/th/LC_MESSAGES/finance.po b/locale/th/LC_MESSAGES/finance.po new file mode 100644 index 000000000..e05b52f63 --- /dev/null +++ b/locale/th/LC_MESSAGES/finance.po @@ -0,0 +1,39545 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Odoo Thaidev <odoothaidev@gmail.com>, 2024 +# Martin Trigaux, 2024 +# Khwunchai Jaengsawang <khwunchai.j@ku.th>, 2024 +# Wichanon Jamwutthipreecha, 2024 +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/finance.rst:5 +msgid "Finance" +msgstr "การเงิน" + +#: ../../content/applications/finance/accounting.rst:5 +msgid "Accounting and Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:7 +msgid "" +"**Odoo Invoicing** is a standalone invoicing app to create invoices, send " +"them to your customers, and manage payments." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:10 +msgid "" +"**Odoo Accounting** is a full featured accounting app. Accountant " +"productivity is at the core of its development with features such as AI-" +"powered invoice recognition, synchronization with your bank accounts, smart " +"matching suggestions, etc." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:15 +msgid "" +"`Odoo Tutorials: Accounting <https://www.odoo.com/slides/accounting-19>`_" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:56 +msgid "Double-entry bookkeeping" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:58 +msgid "" +"Odoo automatically creates all the underlying journal entries for all " +"accounting transactions (e.g., customer invoices, vendor bills, point-of-" +"sales orders, expenses, inventory valuations, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:61 +msgid "" +"Odoo uses the double-entry bookkeeping system, whereby every entry needs a " +"corresponding and opposite counterpart in a different account, with one " +"account debited and the other credited. It ensures that all transactions are" +" recorded accurately and consistently and that the accounts always balance." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:67 +#: ../../content/applications/finance/accounting.rst:222 +msgid ":doc:`Accounting Cheat Sheet <accounting/get_started/cheat_sheet>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:70 +msgid "Accrual and cash basis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:72 +msgid "" +"Both accrual and cash basis accounting are supported in Odoo. This allows " +"reporting income and expense either when the transaction occurs (accrual " +"basis) or when the payment is made or received (cash basis)." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:77 +msgid ":doc:`Cash basis <accounting/taxes/cash_basis>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:80 +msgid "Multi-company" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:82 +msgid "" +"Several companies can be managed within the same database. Each company has " +"its :doc:`chart of accounts <accounting/get_started/chart_of_accounts>`, " +"which is also useful to generate consolidation reports. Users can access " +"several companies but can only work on a single company's accounting at a " +"time." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:88 +msgid "Multi-currency environment" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:90 +msgid "" +"A :doc:`multi-currency <accounting/get_started/multi_currency>` environment " +"with an automated exchange rate to ease international transactions is " +"available in Odoo. Every transaction is recorded in the company's default " +"currency; for transactions occurring in another currency, Odoo stores both " +"the value in the company's currency and the transactions' currency value. " +"Odoo generates currency gains and losses after reconciling the journal " +"items." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:97 +msgid "" +":doc:`Manage a bank in a foreign currency " +"<accounting/bank/foreign_currency>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:100 +msgid "Branch management" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:102 +msgid "" +"Multiple branches can be managed thanks to multi-company hierarchies. This " +"allows to post journal entries on each branch as well as setting up a common" +" lock date managed by the main company." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:106 +msgid "International standards" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:108 +msgid "" +"Odoo Accounting supports more than 70 countries. It provides the central " +"standards and mechanisms common to all nations, and thanks to country-" +"specific modules, local requirements are fulfilled. Fiscal positions exist " +"to address regional specificities like the chart of accounts, taxes, or any " +"other requirements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:114 +msgid ":doc:`Fiscal localization packages <fiscal_localizations>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:117 +msgid "Accounts receivable and payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:119 +msgid "" +"By default, there is a single account for the account receivable entries and" +" one for the account payable entries. As transactions are linked to your " +"**contacts**, you can run a report per customer, vendor, or supplier." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:123 +msgid "" +"The **Partner Ledger** report displays the balance of your customers and " +"suppliers. It is available by going to :menuselection:`Accounting --> " +"Reporting --> Partner Ledger`." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:127 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:77 +#: ../../content/applications/finance/accounting/reporting.rst:5 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:77 +msgid "Reporting" +msgstr "การรายงาน" + +#: ../../content/applications/finance/accounting.rst:129 +msgid "" +"The following financial :doc:`reports <accounting/reporting>` are available " +"and updated in real-time:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:133 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:28 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1157 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 +msgid "Financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:135 +msgid "Statement" +msgstr "รายการเดินบัญชีธนาคาร" + +#: ../../content/applications/finance/accounting.rst:135 +#: ../../content/applications/finance/accounting/customer_invoices.rst:216 +msgid "Balance sheet" +msgstr "งบดุล" + +#: ../../content/applications/finance/accounting.rst:137 +#: ../../content/applications/finance/accounting/customer_invoices.rst:206 +msgid "Profit and loss" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:139 +msgid "Cash flow statement" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:141 +#: ../../content/applications/finance/accounting.rst:180 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:77 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:38 +msgid "Tax report" +msgstr "รายงานภาษี" + +#: ../../content/applications/finance/accounting.rst:143 +msgid "ES sales list" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:145 +msgid "Audit" +msgstr "ตรวจสอบบัญชี" + +#: ../../content/applications/finance/accounting.rst:145 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1076 +msgid "General ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:147 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1038 +msgid "Trial balance" +msgstr "งบทดลอง" + +#: ../../content/applications/finance/accounting.rst:149 +msgid "Journal report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:151 +msgid "Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:153 +msgid "Check register" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:155 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:138 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:138 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:325 +msgid "Partner" +msgstr "พาร์ทเนอร์" + +#: ../../content/applications/finance/accounting.rst:155 +msgid "Partner ledger" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:157 +msgid "Aged receivable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:159 +msgid "Aged payable" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:161 +msgid "Management" +msgstr "การจัดการ" + +#: ../../content/applications/finance/accounting.rst:161 +msgid "Invoice analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:163 +msgid "Unrealized currency gains/losses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:165 +msgid "Depreciation schedule" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:167 +msgid "Disallowed expenses" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:169 +msgid "Budget analysis" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:171 +msgid "Product margins" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:173 +msgid "1099 report" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:177 +msgid "" +":doc:`Create and customize reports <accounting/reporting/customize>` with " +"Odoo's report engine." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:182 +msgid "" +"Odoo computes all accounting transactions for the specific tax period and " +"uses these totals to calculate the tax obligation." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:186 +msgid "" +"Once the tax report has been generated for a period, Odoo locks it and " +"prevents the creation of new journal entries involving VAT. Any correction " +"to customer invoices or vendor bills has to be recorded in the next period." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:191 +msgid "" +"Depending on the country's localization, an XML version of the tax report " +"can be generated to be uploaded to the VAT platform of the relevant taxation" +" authority." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:195 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:5 +msgid "Bank synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:197 +msgid "" +"The bank synchronization system directly connects with your bank institution" +" to automatically import all transactions into your database. It gives an " +"overview of your cash flow without logging into an online banking system or " +"waiting for paper bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:202 +msgid ":doc:`Bank synchronization <accounting/bank/bank_synchronization>`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:205 +msgid "Inventory valuation" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:207 +msgid "" +"Both periodic (manual) and perpetual (automated) inventory valuations are " +"supported in Odoo. The available methods are standard price, average price, " +":abbr:`LIFO (Last-In, First-Out)` and :abbr:`FIFO (First-In, First-Out).`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:212 +msgid "" +":doc:`../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config`" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:215 +msgid "Retained earnings" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:217 +msgid "" +"Retained earnings are the portion of income retained by a business. Odoo " +"calculates current year earnings in real-time, so no year-end journal or " +"rollover is required. The profit and loss balance is automatically reported " +"on the balance sheet report." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:227 +msgid "Fiduciaries" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:229 +msgid "" +"The :guilabel:`Accounting Firms` mode can be activated by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Firms mode`. When enabled:" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:232 +msgid "The document's sequence becomes editable on all documents;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:233 +msgid "" +"The :guilabel:`Total (tax incl.)` field appears to speed up and control the " +"encoding by automating line creation with the right account and tax;" +msgstr "" + +#: ../../content/applications/finance/accounting.rst:235 +msgid "" +":guilabel:`Invoice Date` and :guilabel:`Bill Date` are pre-filled when " +"encoding a transaction." +msgstr "" + +#: ../../content/applications/finance/accounting.rst:236 +msgid "" +"A :guilabel:`Quick encoding` option is available for customer invoices and " +"vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:5 +msgid "Bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:7 +msgid "" +"You can manage as many bank or cash accounts as needed on your database. " +"Configuring them well allows you to have all your banking data up-to-date " +"and ready for :doc:`reconciliation <bank/reconciliation>` with your journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:11 +msgid "" +"In Odoo Accounting, each bank account has a dedicated journal set to post " +"all entries in a dedicated account. Both the journal and the account are " +"automatically created and configured whenever you add a bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:16 +msgid "Cash journals and accounts must be configured manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:18 +msgid "" +"Bank journals are displayed by default on the :guilabel:`Accounting " +"Dashboard` in the form of cards which include action buttons." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "" +"Bank journals are displayed on the Accounting Dashboard and contain action " +"buttons" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:27 +msgid "Manage your bank and cash accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:30 +msgid "Connect your bank for automatic synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:32 +msgid "" +"To connect your bank account to your database, go to " +":menuselection:`Accounting --> Configuration --> Banks: Add a Bank Account`," +" select your bank in the list, click on :guilabel:`Connect`, and follow the " +"instructions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:37 +#: ../../content/applications/finance/accounting/bank.rst:135 +#: ../../content/applications/finance/accounting/get_started.rst:188 +msgid ":doc:`bank/bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:40 +msgid "Create a bank account" +msgstr "สร้างบัญชีธนาคาร" + +#: ../../content/applications/finance/accounting/bank.rst:42 +msgid "" +"If your banking institution is not available in Odoo, or if you don't want " +"to connect your bank account to your database, you can configure your bank " +"account manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:45 +msgid "" +"To manually add a bank account, go to :menuselection:`Accounting --> " +"Configuration --> Banks: Add a Bank Account`, click on :guilabel:`Create it`" +" (at the bottom right), and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:49 +msgid "" +"Odoo automatically detects the bank account type (e.g., IBAN) and enables " +"some features accordingly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:51 +msgid "" +"A default bank journal is available and can be used to configure your bank " +"account by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Bank`. Open it and edit the different fields to " +"match your bank account information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:56 +msgid "Create a cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:58 +msgid "" +"To create a new cash journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`, click on :guilabel:`Create` and " +"select :guilabel:`Cash` in the :guilabel:`Type` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:61 +msgid "" +"For more information on the accounting information fields, read the " +":ref:`bank_accounts/configuration` section of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:65 +msgid "" +"A default cash journal is available and can be used straight away. You can " +"review it by going to :menuselection:`Accounting --> Configuration --> " +"Accounting: Journals --> Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:69 +msgid "Edit an existing bank or cash journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:71 +msgid "" +"To edit an existing bank journal, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals` and select the journal you want to " +"modify." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:77 +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:28 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:24 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:22 +#: ../../content/applications/finance/accounting/bank/cash_register.rst:9 +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:16 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:69 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:27 +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:14 +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:13 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:29 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:63 +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:21 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:46 +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:12 +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:15 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:36 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:15 +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:11 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:20 +#: ../../content/applications/finance/accounting/payments/follow_up.rst:14 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:12 +#: ../../content/applications/finance/accounting/payments/online.rst:21 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:10 +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:45 +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:10 +#: ../../content/applications/finance/accounting/reporting/budget.rst:11 +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:11 +#: ../../content/applications/finance/accounting/taxes.rst:51 +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:60 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:14 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:17 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:20 +#: ../../content/applications/finance/accounting/taxes/retention.rst:11 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:18 +#: ../../content/applications/finance/documents.rst:16 +#: ../../content/applications/finance/fiscal_localizations.rst:21 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:8 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:329 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:424 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:878 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:6 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:45 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:570 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:58 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:8 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:40 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:653 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:769 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:909 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:29 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:6 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:6 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:42 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:6 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:6 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:6 +#: ../../content/applications/finance/payment_providers.rst:276 +#: ../../content/applications/finance/payment_providers/adyen.rst:17 +#: ../../content/applications/finance/payment_providers/alipay.rst:12 +#: ../../content/applications/finance/payment_providers/authorize.rst:9 +#: ../../content/applications/finance/payment_providers/authorize.rst:60 +#: ../../content/applications/finance/payment_providers/demo.rst:9 +#: ../../content/applications/finance/payment_providers/mollie.rst:8 +#: ../../content/applications/finance/payment_providers/paypal.rst:101 +#: ../../content/applications/finance/payment_providers/sips.rst:9 +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:30 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/finance/accounting/bank.rst:79 +msgid "" +"You can edit the accounting information and bank account number according to" +" your needs." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Manually configure your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:85 +#: ../../content/applications/finance/accounting/bank.rst:109 +msgid ":doc:`get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:86 +#: ../../content/applications/finance/accounting/bank.rst:136 +msgid ":doc:`bank/transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:91 +msgid "Suspense account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:93 +msgid "" +"Bank statement transactions are posted on the :guilabel:`Suspense Account` " +"until the final reconciliation allows finding the right account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:97 +msgid "Profit and loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:99 +msgid "" +"The :guilabel:`Profit Account` is used to register a profit when the ending " +"balance of a cash register differs from what the system computes, while the " +":guilabel:`Loss Account` is used to register a loss when the ending balance " +"of a cash register differs from what the system computes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:104 +msgid "Currency" +msgstr "สกุลเงิน" + +#: ../../content/applications/finance/accounting/bank.rst:106 +msgid "You can edit the currency used to enter the statements." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:112 +msgid "Account number" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:114 +msgid "" +"If you need to **edit your bank account details**, click on the external " +"link arrow next to your :guilabel:`Account Number`. On the new page, click " +"on the external link arrow next to your :guilabel:`Bank` and update your " +"bank information accordingly. These details are used when registering " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Edit your bank information" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:123 +msgid "Bank feeds" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:125 +msgid "" +":guilabel:`Bank Feeds` defines how the bank statements are registered. Three" +" options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:127 +msgid "" +":guilabel:`Undefined yet`, which should be selected when you don’t know yet " +"if you will synchronize your bank account with your database or not." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:129 +msgid "" +":guilabel:`Import (CAMT, CODA, CSV, OFX, QIF)`, which should be selected if " +"you want to import your bank statement using a different format." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:131 +msgid "" +":guilabel:`Automated Bank Synchronization`, which should be selected if your" +" bank is synchronized with your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:141 +msgid "Outstanding accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:143 +msgid "" +"By default, payments are registered through transitory accounts named " +"**outstanding accounts**, before being recorded in your bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:146 +msgid "" +"An **outstanding payments account** is where outgoing payments are posted " +"until they are linked with a withdrawal from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:148 +msgid "" +"An **outstanding receipts account** is where incoming payments are posted " +"until they are linked with a deposit from your bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:151 +msgid "" +"These accounts should be of :ref:`type <chart-of-account/type>` " +":guilabel:`Current Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:154 +msgid "" +"The movement from an outstanding account to a bank account is done " +"automatically when you reconcile the bank account with a bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:158 +msgid "Default accounts configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:160 +msgid "" +"The outstanding accounts are defined by default. If necessary, you can " +"update them by going to :menuselection:`Accounting --> Configuration --> " +"Settings --> Default Accounts` and update your :guilabel:`Outstanding " +"Receipts Account` and :guilabel:`Outstanding Payments Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:165 +msgid "Bank and cash journals configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:167 +msgid "" +"You can also set specific outstanding accounts for any journal with the " +":ref:`type <chart-of-account/type>` :guilabel:`Bank` or :guilabel:`Cash`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:170 +msgid "" +"From your :guilabel:`Accounting Dashboard`, click on the menu selection ⋮ of" +" the journal you want to configure, and click on :guilabel:`Configuration`, " +"then open the :guilabel:`Incoming/Outgoing Payments` tab. To display the " +"outstanding accounts column, click on the toggle button and check the " +":guilabel:`Outstanding Receipts/Payments accounts`, then update the account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst-1 +msgid "Select the toggle button and click on outstanding Accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:180 +msgid "" +"If you do not specify an outstanding payments account or an outstanding " +"receipts account for a specific journal, Odoo uses the default outstanding " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank.rst:182 +msgid "" +"If your main bank account is added as an outstanding receipts account or " +"outstanding payments account, when a payment is registered, the invoice or " +"bill's status is directly set to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:7 +msgid "" +"Odoo can synchronize directly with your bank institution to get all bank " +"statements imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:10 +msgid "" +"To check if your bank is compatible with Odoo, go to `Odoo Accounting " +"Features <https://www.odoo.com/page/accounting-features>`_, and click on " +":guilabel:`See list of supported institutions`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:14 +msgid "Odoo supports more than 25,000 institutions around the world." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:16 +msgid "To connect to the banks, Odoo uses multiple web-services:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:18 +msgid "**Plaid**: United States of America and Canada" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:19 +msgid "**Yodlee**: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:20 +msgid ":doc:`Salt Edge <bank_synchronization/saltedge>`: Worldwide" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:21 +msgid ":doc:`Ponto <bank_synchronization/ponto>`: Europe" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:22 +msgid "" +":doc:`Enable Banking <bank_synchronization/enablebanking>`: Scandinavian " +"countries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:25 +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:18 +msgid ":doc:`transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:31 +msgid "On-Premise users" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:33 +msgid "" +"To be able to use this service, you need to have a valid Odoo Enterprise " +"subscription. So make sure that your database is registered with your Odoo " +"Enterprise contract. We also use a proxy between your database and the third" +" party provider so, in case of a connection error, please check that you " +"don't have a firewall or a proxy blocking the following address:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:39 +msgid "https://production.odoofin.com/" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:42 +msgid "First synchronization" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:44 +msgid "" +"You can start synchronization either by going to the Accounting app and " +":menuselection:`Accounting Dashboard --> Configuration --> Banks: Add a Bank" +" Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:47 +msgid "" +"Now you can search for your bank institution. Select it and follow the steps" +" to synchronize with it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:50 +msgid "" +"If you have any issues during your first synchronization, please verify that" +" your web browser doesn't block pop-ups and that your ad-blocker is " +"disabled." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:54 +msgid "" +"When setting up the bank statement synchronization, Odoo automatically " +"starts recording the accounting transactions from the last transaction’s " +"date +1 day (if the last transaction day is 31/12/2022, the recording starts" +" on 01/01/2023). If the journal contains no transaction, Odoo retrieves " +"transactions as far back as possible. You can limit how far back Odoo " +"retrieves transactions by opening the Accounting app, going to " +":menuselection:`Accounting --> Lock Dates`, and setting a date in the " +":guilabel:`Journal Entries Lock Date` field." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:61 +msgid "" +"You must provide a phone number during your first synchronization to secure " +"your account. We ask for such information because we don't want your data " +"falling into the wrong hands. Therefore, if we detect suspicious activities " +"on your account, we block all requests coming from your account, and you " +"need to reactivate it using that phone number." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:66 +msgid "" +"The third-party provider may request more information in order to connect " +"with your bank institution. This information is not stored on Odoo's " +"servers." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:69 +msgid "" +"By default, transactions fetched from an online source are grouped inside " +"the same statement, and one bank statement is created per month. You can " +"change the bank statement creation periodicity in your journal settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:73 +msgid "" +"You can find all your synchronizations by going to " +":menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:77 +msgid "Synchronize manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:79 +msgid "" +"After your first synchronization, the created journals are synchronized by " +"default every 12 hours. If you wish, you can synchronize manually by " +"clicking on the :guilabel:`Synchronize Now` button on the dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:83 +msgid "" +"Or you can go to :menuselection:`Accounting Dashboard --> Configuration --> " +"Accounting: Online Synchronization`, select your institution and then click " +"on the :guilabel:`fetch transactions` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:88 +msgid "" +"Some institutions do not allow transactions to be fetched automatically. For" +" such institutions, during the automatic synchronization of the account, you" +" receive an error message asking you to disable the automatic " +"synchronization. This message can be found in the chatter of your online " +"synchronizations. In this case, make sure to perform manual " +"synchronizations." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:94 +msgid "Issues" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:97 +msgid "Synchronization in error" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:99 +msgid "" +"To report a connection error to the `Odoo support " +"<https://www.odoo.com/help>`_, go to :menuselection:`Accounting Dashboard-->" +" Configuration --> Accounting: Online Synchronization`, select the " +"connection that failed, and copy the error description and the reference." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:104 +msgid "Synchronization disconnected" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:106 +msgid "" +"If your connection with the proxy is disconnected, you can reconnect with " +"the proxy using the :guilabel:`Fetch Account` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:110 +msgid "" +"If you are unable to reconnect using the :guilabel:`Reconnect` button, " +"please contact the `support <https://www.odoo.com/help>`_ directly with your" +" client id or the reference of the error listed in the chatter." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:117 +msgid "Migration process for users having installed Odoo before December 2020" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:119 +msgid "" +"If you are on-premise, please first make sure that your source is up-to-date" +" with the latest version of Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:122 +msgid "" +"Users who have created a database before December 2020 need to install the " +"new module manually to use the new functionalities." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:125 +msgid "" +"To do so, go to :menuselection:`Apps --> Update Apps List`, remove the " +"default filter in the search bar and type `account_online_synchronization`. " +"You can then click on :guilabel:`Install`. Finally, make sure all your users" +" refresh their Odoo page by pressing CTRL+F5." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:131 +msgid "" +"All previous synchronizations are disconnected during the installation and " +"won't work anymore." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:132 +msgid "" +"You can find them directly in the synchronization menu " +"(:menuselection:`Accounting Dashboard --> Configuration --> Accounting: " +"Online Synchronization`). It is not possible to resynchronize these " +"connections; you have to make new ones." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:136 +msgid "" +"Do not uninstall `account_online_sync`, which is the previous module for " +"online synchronization. The new one overrides it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:138 +msgid "" +"By default, `account_online_synchronization` is installed automatically with" +" Accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:141 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:95 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:81 +msgid "FAQ" +msgstr "คำถามที่พบบ่อย" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:144 +msgid "The synchronization is not working in real-time. Is that normal?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:146 +msgid "" +"The process is not intended to work in real-time as third party providers " +"synchronize your accounts at different intervals. To force the " +"synchronization and fetch the statements, go to your :guilabel:`Accounting " +"Dashboard`, and click on the :guilabel:`Synchronize Now` button. You can " +"also synchronize and fetch transactions through :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`. Some " +"providers only allow one refresh per day, so it is possible that clicking on" +" :guilabel:`Synchronize Now` does not get your latest transactions if you " +"already performed such action earlier in the day." +msgstr "" +"ขั้นตอนนี้ไม่สามารถทำงานแบบเรียลไทม์ได้ " +"เนื่องจากผู้ให้บริการบุคคลที่สามซิงค์บัญชีของคุณในช่วงเวลาที่ต่างกัน " +"หากต้องการบังคับการซิงโครไนซ์และดึงข้อมูลใบแจ้งยอด ให้ไปที่ " +":guilabel:`แดชบอร์ดระบบบัญชี` ของคุณ และคลิกที่ปุ่ม " +":guilabel:`ซิงโครไนซ์ทันที` คุณยังสามารถซิงโครไนซ์และดึงธุรกรรมผ่าน " +":menuselection:`แดชบอร์ดระบบบัญชี --> การกำหนดค่า --> ระบบบัญชี: " +"การซิงโครไนซ์ออนไลน์` ผู้ให้บริการบางรายอนุญาตให้รีเฟรชเพียงครั้งเดียวต่อวัน" +" ดังนั้นจึงเป็นไปได้ที่การคลิก :guilabel:`ซิงโครไนซ์ทันที` " +"จะไม่ได้รับธุรกรรมล่าสุดของคุณ " +"หากคุณได้ดำเนินการดังกล่าวก่อนหน้านี้ในวันนั้น" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:154 +msgid "" +"A transaction can be visible on your bank account but not be fetched if it " +"has the status :guilabel:`Pending`. Only transactions with the " +":guilabel:`Posted` status will be retrieved. If the transaction is not " +"**Posted** yet, you will have to wait until the status changes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:159 +msgid "Is the Online Bank Synchronization feature included in my contract?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:161 +msgid "" +"**Community Version**: No, this feature is not included in the Community " +"Version." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:162 +msgid "" +"**Online Version**: Yes, even if you benefit from the One App Free contract." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:163 +msgid "" +"**Enterprise Version**: Yes, if you have a valid enterprise contract linked " +"to your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:166 +msgid "Some banks have a status \"Beta.\" What does this mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:168 +msgid "" +"This means that banking institutions are not yet fully supported by our " +"Third Party Provider. Bugs or other problems may arise. Odoo does not " +"support technical problems that occur with banks in the Beta phase, but the " +"user may still choose to connect. Connecting with these banks contributes to" +" the development process since the Provider will have real data and feedback" +" from the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:174 +msgid "Why do my transactions only synchronize when I refresh manually?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:176 +msgid "" +"Some banks have additional security measures and require extra steps, such " +"as an SMS/email authentication code or another type of MFA. Because of this," +" the integrator cannot pull transactions until the security code is " +"provided." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:181 +msgid "Not all of my past transactions are in Odoo, why?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:183 +msgid "" +"For some institutions, transactions can only be fetched up to 3 months in " +"the past." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:186 +msgid "Why don't I see any transactions?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:188 +msgid "" +"During your first synchronization, you selected the bank accounts you " +"decided to synchronize with Odoo. If you didn't synchronize any of your " +"accounts, you can go to :menuselection:`Accounting Dashboard --> " +"Configuration --> Accounting: Online Synchronization` to click on the " +":guilabel:`Fetch Account` button on the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:193 +msgid "There may also be no new transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:195 +msgid "" +"If your bank account is properly linked to a journal and posted transactions" +" are not visible in your database, please `submit a support ticket " +"<https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:199 +msgid "How can I update my bank credentials?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:201 +msgid "" +"You can update your credentials by going to :menuselection:`Accounting " +"Dashboard --> Configuration --> Accounting: Online Synchronization`,open the" +" connection you want to update your credentials and click on the " +":guilabel:`Update Credentials` button." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:3 +msgid "Enable Banking" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:5 +msgid "" +"**Enable Banking** is a third-party provider aggregating banking information" +" from bank accounts all in one place. It offers non-intrusive connectivity " +"to ASPSPs' official APIs across Europe without storing data." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst-1 +msgid "Enable Banking logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:13 +msgid "" +"**Odoo** synchronizes directly with banks to get access to all bank " +"transactions and automatically import them into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:17 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:20 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:18 +msgid ":doc:`../bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:18 +msgid "`Enable Banking website <https://enablebanking.com/>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:24 +msgid "Link bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:26 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:28 +msgid "Select your bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:29 +msgid "" +"Make sure you give your consent to share your account information with Odoo " +"by clicking :guilabel:`Continue authentication`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:0 +msgid "Enable Banking authentication page" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/enablebanking.rst:36 +msgid "Finally, you are redirected to your bank's login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:3 +msgid "Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:5 +msgid "" +"**Ponto** is a service that allows companies and professionals to aggregate " +"their accounts in one place and directly see all their transactions within " +"one app. It is a third-party solution that is continuously expanding the " +"number of bank institutions that can be synchronized with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst-1 +msgid "Logo of the Ponto brand" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:13 +msgid "" +"**Odoo** can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:16 +msgid "" +"Ponto is a paid third-party provider that can handle the synchronization " +"between your bank accounts and Odoo. `Its pricing is 4€/month per " +"account/integration <https://myponto.com/en#pricing>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:21 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:19 +msgid ":doc:`../transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:27 +msgid "Link your bank accounts with Ponto" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:29 +msgid "Go to `Ponto's website (https://myponto.com) <https://myponto.com>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:30 +msgid "Create an account if you don't have one yet." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:31 +msgid "Once you are logged in, create an *organization*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Fill out the form to add an organization in Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Go to :menuselection:`Accounts --> Live`, and click on *Add account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "You might have to add your **Billing Information** first." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:39 +msgid "" +"Select your country, your bank institutions, give your consent to Ponto, and" +" follow the steps on-screen to link your bank account with your Ponto " +"account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Add bank accounts to your Ponto account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:46 +msgid "" +"Make sure to add all bank accounts you want to synchronize with your Odoo " +"database before moving on to the next steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:50 +msgid "Link your Ponto account with your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:52 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:53 +msgid "" +"Search your institution, make sure to select the right institution. By " +"selecting the institution, you can verify that the third party provider is " +"Ponto." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:55 +msgid "Click on *Connect* and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:56 +msgid "" +"At some point, you will have to authorize the accounts you want to access in" +" Odoo. Please select **all the accounts** you want to synchronize. Even the " +"ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:0 +msgid "Selection of the accounts you wish to synchronize with Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:64 +msgid "Finish the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:67 +msgid "" +"You have to authorize all the accounts you want to access in Odoo, but Odoo " +"will filter the accounts based on the institution you selected in the second" +" step." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:71 +msgid "Update your synchronization credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:73 +msgid "" +"You might have to update your Ponto credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:75 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:87 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to fetch the other " +"accounts. Click on *Fetch Accounts* button to start the flow." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:79 +msgid "" +"During the update, select **all the accounts** you want to synchronize, even" +" the ones coming from other banking institutions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:83 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:69 +msgid "Fetch new accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:85 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:71 +msgid "You might want to add new online accounts to your connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:91 +msgid "" +"Don't forget to keep authorization for existing accounts (for all " +"institutions that you have synchronized with Ponto)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:98 +msgid "After my synchronization, no account appears" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:100 +msgid "" +"You selected an institution from the list and did not authorize any accounts" +" from this institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:103 +msgid "I have an error about that my authorization has expired" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:105 +msgid "" +"Every **3 months** (90 days) you must re-authorize the connection between " +"your bank account and Ponto. This must be done from the `Ponto website " +"<https://myponto.com>`_. If you do not do this, the synchronization will " +"stop for these accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:110 +msgid "I have some errors with my beta institution" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:112 +msgid "" +"Ponto provides institutions in *beta*, these institutions are not directly " +"supported by Odoo and we advise you to contact Ponto directly." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/ponto.rst:116 +msgid "" +"Using an institution in beta is beneficial for Ponto, it allows them to have" +" real feedback on the connection with the institution." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:3 +msgid "Salt Edge" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:5 +msgid "" +"**Salt Edge** is a third-party provider that aggregates banking information " +"from your bank accounts. It supports ~5000 institutions in more than 50 " +"countries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst-1 +msgid "Salt Edge Logo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:14 +msgid "" +"Odoo can synchronize directly with your bank to get all bank statements " +"imported automatically into your database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:25 +msgid "Link your bank accounts with Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:27 +msgid "" +"Start synchronization by clicking on :menuselection:`Accounting --> " +"Configuration --> Add a Bank Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:29 +msgid "" +"Select the institution you want to synchronize. You can see if Salt Edge is " +"the third party provider of the institution by selecting it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:31 +msgid "" +"After giving your phone number, you are asked for an email address. This " +"email address is used to create your Salt Edge account. Please make sure you" +" enter a valid email address, as otherwise, you will not be able to access " +"your Salt Edge account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "" +"Email address to provide to Salt Edge for the creation of your account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:40 +msgid "" +"After entering your email address, you are redirected to Salt Edge to " +"continue the synchronization process." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge Login page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:47 +msgid "Make sure you give your consent by checking the consent checkbox." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:0 +msgid "Salt Edge give consent page." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:53 +msgid "Complete the synchronization by following the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:57 +msgid "Update your credentials" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:59 +msgid "" +"You might have to update your Salt Edge credentials or modify the " +"synchronization settings." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:61 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution you want to update credentials. " +"Click on the *Update Credentials* button to start the flow and follow the " +"steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:65 +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:77 +msgid "" +"Don't forget to check the consent checkbox. Otherwise, Odoo may not be able " +"to access your information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:73 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Online " +"Synchronization` and select the institution to fetch the new accounts. Click" +" on the *Fetch Accounts* button to start the flow and follow the steps." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:84 +msgid "I have an error when I try to delete my synchronization within Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:86 +msgid "" +"Odoo can't permanently delete the connection you have created with the " +"banking institution. However, it can revoke the consent you gave so that " +"Odoo won't be able to access your account anymore. The error you are seeing " +"is probably a message telling you that the consent was revoked, but the " +"record could not be deleted as it still exists within Salt edge. If you want" +" to remove the connection completely, please connect to your `Salt Edge " +"account <https://www.saltedge.com/dashboard>`_ and manually delete your " +"synchronization. Once this is done, you can go back to Odoo to delete the " +"record." +msgstr "" +"Odoo ไม่สามารถลบการเชื่อมต่อที่คุณสร้างกับสถาบันการเงินได้อย่างถาวร " +"แต่สามารถเพิกถอนความยินยอมที่คุณให้ไว้ได้ เพื่อที่ Odoo " +"จะไม่สามารถเข้าถึงบัญชีของคุณได้อีกต่อไป " +"ข้อผิดพลาดที่คุณเห็นอาจเป็นข้อความที่บอกคุณว่าความยินยอมได้ถูกเพิกถอนแล้ว " +"แต่บันทึกไม่สามารถลบได้เนื่องจากยังคงมีอยู่ใน Salt Edge " +"หากคุณต้องการลบการเชื่อมต่อโดยสมบูรณ์ โปรดเชื่อมต่อกับ `บัญชี Salt Edge " +"ของคุณ <https://www.saltedge.com/dashboard>`_ " +"และลบการซิงโครไนซ์ของคุณด้วยตนเอง เมื่อเสร็จแล้ว คุณสามารถกลับไปที่ Odoo " +"เพื่อลบบันทึกได้" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:95 +msgid "I have an error saying that I have already synchronized this account" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:97 +msgid "" +"You have probably already synchronized your bank account with Salt Edge, " +"please check on your `dashboard <https://www.saltedge.com/dashboard>`_ that " +"you don't already have a connection with the same credentials." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:101 +msgid "" +"In case you already have a synchronization with the same credentials present" +" on your Salt Edge dashboard and this synchronization has not been created " +"with Odoo, please delete it and create it from your Odoo database." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/bank_synchronization/saltedge.rst:105 +msgid "" +"In case you already have a connection with the same credentials present on " +"your Salt Edge dashboard and this synchronization was created with Odoo, you" +" will normally be able to find it by going to :menuselection:`Accounting -->" +" Configuration --> Online Synchronization`. Please make sure to do an " +"*Update Credentials* to reactivate the connection." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:3 +msgid "Cash register" +msgstr "เครื่องบันทึกเงินสด" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:5 +msgid "" +"The cash register is a journal to register receivings and payments " +"transactions. It calculates the total money in and out, computing the total " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:14 +msgid "" +"Configure the Cash journal in :menuselection:`Accounting --> Configuration " +"--> Journals`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:17 +msgid "" +"In the tab Journal Entries, the Default Debit and Credit Account can be " +"configured as well as the currency of the journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:21 +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:34 +msgid "Usage" +msgstr "การใช้งาน" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:24 +msgid "How to register cash payments?" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:26 +msgid "" +"To register a cash payment specific to another customer, you should follow " +"these steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:29 +msgid "" +"Go to :menuselection:`Accounting --> Dashboard --> Cash --> Register " +"Transactions`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:32 +msgid "Fill in the start and ending balance" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:34 +msgid "" +"Register the transactions, specifying the customers linked to the " +"transaction" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:37 +msgid "Put money in" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:39 +msgid "" +"Put money in is used to placed your cash manually before starting your " +"transactions. From the Register Transactions window, go to " +":menuselection:`More --> Put money in`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:47 +msgid "Take money out" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:49 +msgid "" +"Take money out is used to collect/get yor your cash manually after ending " +"all your transactions. From the Register Transaction windows, go to " +":menuselection:`More --> Take money out`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/cash_register.rst:56 +msgid "" +"The transactions will be added to the current cash payment registration." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:3 +msgid "Manage a bank account in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:5 +msgid "" +"In Odoo, every transaction is recorded in the default currency of the " +"company, and reports are all based on that default currency. When you have a" +" bank account in a foreign currency, for every transaction, Odoo stores two " +"values:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:9 +msgid "The debit/credit in the currency of the *company*;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:10 +msgid "The debit/credit in the currency of the *bank account*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:12 +msgid "" +"Currency rates are updated automatically using the web services of a banking" +" institution. By default, Odoo uses the European Central Bank's web services" +" but other options are available." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:19 +msgid "Activate multi-currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:21 +msgid "" +"To work with multiple currencies, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and tick :guilabel:`Multi-" +"Currencies`. Under :guilabel:`Post Exchange difference entries in:`, provide" +" a :guilabel:`Journal`, a :guilabel:`Gain Account`, a :guilabel:`Loss " +"Account`, and then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:27 +msgid "Configure currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:29 +msgid "" +"Once Odoo is configured to support multiple currencies, they are all created" +" by default, but not necessarily active. To activate the new currencies, " +"click on :guilabel:`Activate Other Currencies` under the :guilabel:`Multi-" +"Currencies` setting or go to :menuselection:`Accounting --> Configuration " +"--> Accounting: Currencies`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:34 +msgid "" +"When the currencies are activated, you can choose to **automate** the " +"currency rate update, or leave it on **manual**. To configure the rate " +"update, go back to :menuselection:`Accounting --> Configuration --> Settings" +" --> Currencies`, check :guilabel:`Automatic Currency Rates`, set " +":guilabel:`Interval` to your desired frequency, and then click on " +":guilabel:`Save`. You also have the option to choose the :guilabel:`Service`" +" you wish to obtain currency rates from." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:40 +msgid "" +"Click on the Update now button (:guilabel:`🗘`) besides the :guilabel:`Next " +"Run` field to update the currency rates manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:44 +msgid "Create a new bank account" +msgstr "สร้างบัญชีธนาคารใหม่" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:46 +msgid "" +"In the accounting application, go to :menuselection:`Accounting --> " +"Configuration --> Journals` and create a new one. Enter a :guilabel:`Journal" +" Name` and set the :guilabel:`Type` to `Bank`. In the :guilabel:`Journal " +"Entries` tab, enter a **short code**, a **currency**, and then finally click" +" on the :guilabel:`Bank Account` field to create a new account. In the pop-" +"up window of the account creation, enter a name, a code (ex.: 550007), set " +"its type to `Bank and Cash`, set a currency type, and save. When you are " +"back on the **journal**, click on the :guilabel:`Account Number` field, and " +"in the pop-up window, fill out the :guilabel:`Account Number`, " +":guilabel:`Bank` of your account, and save." +msgstr "" +"ในแอปพลิเคชันระบบบัญชี ไปที่ :เมนูการเลือก:`ระบบบัญชี --> การกำหนดค่า --> " +"สมุดรายวัน` และสร้างรายการใหม่ ป้อน :guilabel:`ชื่อสมุดรายวัน` และตั้งค่า " +":guilabel:`ประเภท` เป็น `ธนาคาร` ในแท็บ :guilabel:`รายการสมุดรายวัน` ให้ป้อน" +" **รหัสสั้น** **สกุลเงิน** จากนั้นคลิกที่ช่อง :guilabel:`บัญชีธนาคาร` " +"เพื่อสร้างบัญชีใหม่ ในหน้าต่างป๊อปอัปของการสร้างบัญชี ให้ป้อนชื่อ รหัส (เช่น" +" 550007) ตั้งค่าประเภทเป็น `ธนาคารและเงินสด` กำหนดประเภทสกุลเงิน และบันทึก " +"เมื่อคุณกลับมาที่ **สมุดรายวัน** ให้คลิกที่ช่อง :guilabel:`หมายเลขบัญชี` " +"และในหน้าต่างป๊อปอัป ให้กรอก :guilabel:`หมายเลขบัญชี`, :guilabel:`ธนาคาร` " +"ของบัญชีของคุณและบันทึก" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Example of a created bank journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:59 +msgid "" +"Upon creation of the journal, Odoo automatically links the bank account to " +"the journal. It can be found under :menuselection:`Accounting --> " +"Configuration --> Accounting: Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:63 +msgid "Vendor bill in a foreign currency" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:65 +msgid "" +"To pay a bill in a foreign currency, simply select the currency next to the " +":guilabel:`Journal` field and register the payment. Odoo automatically " +"creates and posts the foreign **exchange gain or loss** as a new journal " +"entry." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "How to set a bill currency." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:74 +msgid "" +"Note that you can pay a foreign bill with another currency. In that case, " +"Odoo automatically converts between the two currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:78 +msgid "Unrealized Currency Gains/Losses Report" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:80 +msgid "" +"This report gives an overview of all unrealized amounts in a foreign " +"currency on your balance sheet, and allows you to adjust an entry or " +"manually set an exchange rate. To access this report, go to " +":menuselection:`Reporting --> Management: Unrealized Currency Gains/Losses`." +" From here, you have access to all open entries in your **balance sheet**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "View of the Unrealized Gains/Losses journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:89 +msgid "" +"If you wish to use a different currency rate than the one set in " +":menuselection:`Accounting --> Configuration --> Settings --> Currencies`, " +"click the :guilabel:`Exchange Rates` button and change the rate of the " +"foreign currencies in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Menu to manually change exchange rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:97 +msgid "" +"When manually changing **exchange rates**, a yellow banner appears allowing " +"you to reset back to Odoo's rate. To do so, simply click on :guilabel:`Reset" +" to Odoo's Rate`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Banner to reset back to Odoo's rates." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:104 +msgid "" +"In order to update your **balance sheet** with the amount of the " +":guilabel:`adjustment` column, click on the :guilabel:`Adjustment Entry` " +"button. In the pop-up window, select a :guilabel:`Journal`, " +":guilabel:`Expense Account` and :guilabel:`Income Account` to calculate and " +"process the **unrealized gains and losses**." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:109 +msgid "" +"You can set the date of the report in the :guilabel:`Date` field. Odoo " +"automatically reverses the booking entry to the date set in " +":guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst:112 +msgid "" +"Once posted, the :guilabel:`adjustment` column should indicate `0.00`, " +"meaning all **unrealized gains/losses** have been adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/foreign_currency.rst-1 +msgid "Unrealized Currency Gains/Losses report once adjusted." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:3 +#: ../../content/applications/finance/accounting/payments/batch.rst:52 +msgid "Bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:5 +msgid "" +"**Bank reconciliation** is the process of matching your :doc:`bank " +"transactions <transactions>` with your business records, such as " +":doc:`customer invoices <../customer_invoices>`, :doc:`vendor bills " +"<../vendor_bills>`, and :doc:`payments <../payments>`. Not only is this " +"compulsory for most businesses, but it also offers several benefits, such as" +" reduced risk of errors in financial reports, detection of fraudulent " +"activities, and improved cash flow management." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:11 +msgid "" +"Thanks to the bank :doc:`reconciliation models <reconciliation_models>`, " +"Odoo pre-selects the matching entries automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:15 +msgid "" +"`Odoo Tutorials: Bank reconciliation " +"<https://www.odoo.com/slides/slide/bank-reconciliation-2724>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:17 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:128 +msgid ":doc:`bank_synchronization`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:21 +msgid "Bank reconciliation view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:23 +msgid "" +"To access a bank journal's **reconciliation view**, go to your " +":guilabel:`Accounting Dashboard` and either:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:26 +msgid "" +"click the journal name (e.g., :guilabel:`Bank`) to display all transactions," +" including those previously reconciled or" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:28 +msgid "" +"click the :guilabel:`Reconcile items` button to display all transactions " +"Odoo pre-selected for reconciliation. You can remove the :guilabel:`Not " +"Matched` filter from the search bar to include previously reconciled " +"transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst-1 +msgid "Reaching the bank reconciliation tool from your accounting dashboard" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:35 +msgid "" +"The bank reconciliation view is structured into three distinct sections: " +"transactions, counterpart entries, and resulting entry." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst-1 +msgid "The user interface of the reconciliation view of a bank journal." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:43 +#: ../../content/applications/finance/accounting/bank/transactions.rst:3 +msgid "Transactions" +msgstr "ธุรกรรม" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:42 +msgid "" +"The transactions section on the left shows all bank transactions, with the " +"newest displayed first. Click a transaction to select it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:50 +msgid "Counterpart entries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:46 +msgid "" +"The counterpart entries section on the bottom right displays the options to " +"match the selected bank transaction. Multiple tabs are available, including " +":ref:`reconciliation/existing-entries`, :ref:`reconciliation/batch-" +"payments`, :ref:`reconciliation/manual-operations`, and :guilabel:`Discuss`," +" which contains the chatter for the selected bank transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:56 +msgid "Resulting entry" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:53 +msgid "" +"The resulting entry section on the top right displays the selected bank " +"transaction matched with the counterpart entries and includes any remaining " +"debits or credits. In this section, you can validate the reconciliation or " +"mark it as :guilabel:`To Check`. Any :ref:`reconciliation model buttons " +"<reconciliation_models_button>` are also available in the resulting entry " +"section." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:59 +msgid "Reconcile transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:61 +msgid "" +"Transactions can be matched automatically with the use of " +":doc:`reconciliation models <reconciliation_models>`, or they can be matched" +" with :ref:`existing entries <reconciliation/existing-entries>`, :ref:`batch" +" payments <reconciliation/batch-payments>`, :ref:`manual operations " +"<reconciliation/manual-operations>`, and :ref:`reconciliation model buttons " +"<reconciliation_models_button>`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:67 +msgid "Select a transaction among unmatched bank transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:68 +msgid "" +"Define the counterpart. There are several options for defining a " +"counterpart, including :ref:`matching existing entries " +"<reconciliation/existing-entries>`, :ref:`manual operations " +"<reconciliation/manual-operations>`, :ref:`batch payments " +"<reconciliation/batch-payments>`, and :ref:`reconciliation model buttons " +"<reconciliation_models_button>`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:72 +msgid "" +"If the resulting entry is not fully balanced, balance it by adding another " +"existing counterpart entry or writing it off with a :ref:`manual operation " +"<reconciliation/manual-operations>`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:74 +msgid "" +"Click the :guilabel:`Validate` button to confirm the reconciliation and move" +" to the next transaction." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:78 +msgid "" +"If you are not sure how to reconcile a particular transaction and would like" +" to deal with it later, use the :guilabel:`To Check` button instead. All " +"transactions marked as :guilabel:`To Check` can be displayed using the " +":guilabel:`To Check` filter." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:83 +msgid "" +"Bank transactions are posted on the **journal's suspense account** until " +"reconciliation. At this point, reconciliation modifies the transaction " +"journal entry by replacing the bank suspense account with the corresponding " +"receivable, payable, or outstanding account." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:90 +msgid "Match existing entries" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:92 +msgid "" +"This tab contains matching entries Odoo automatically pre-selects according " +"to the reconciliation models. The entry order is based on " +":ref:`reconciliation models <reconciliation_models_suggestion>`, with " +"suggested entries appearing first." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:97 +msgid "" +"The search bar within the :guilabel:`Match Existing Entries` tab allows you " +"to search for specific journal items." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:103 +msgid "Batch payments" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:105 +msgid "" +"`Batch payments <payments/batch-payments>`_ allow you to group different " +"payments to ease reconciliation. Use the :guilabel:`Batch Payments` tab to " +"find batch payments for customers and vendors. Similarly to the " +":guilabel:`Match Existing Entries` tab, the :guilabel:`Batch Payments` tab " +"has a search bar that allows you to search for specific batch payments." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:113 +msgid "Manual operations" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:115 +msgid "" +"If there is not an existing entry to match the selected transaction, you may" +" instead wish to reconcile the transaction manually by choosing the correct " +"account and amount. Then, complete any of the relevant optional fields." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:120 +msgid "" +"You can use the :guilabel:`fully paid` option to reconcile a payment, even " +"in cases where only a partial payment is received. A new line appears in the" +" resulting entry section to reflect the open balance registered on the " +"Account Receivable by default. You can choose another account by clicking on" +" the new line in the resulting entry section and selecting the " +":guilabel:`Account` to record the open balance." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:127 +msgid "" +"Lines are silently reconciled unless a write-off entry is required, which " +"launches a reconciliation wizard." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:0 +msgid "Click on fully paid to manually set an invoice as entirely paid." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:135 +msgid "Reconciliation model buttons" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation.rst:137 +msgid "" +"Use a :ref:`reconciliation model button <reconciliation_models_button>` for " +"manual operations that are frequently used. These custom buttons allow you " +"to quickly reconcile bank transactions manually and can also be used in " +"combination with existing entries." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:3 +msgid "Reconciliation Models" +msgstr "แบบการกระทบยอด" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:5 +msgid "" +"Once the bank statements are correctly imported, it is essential to " +"*reconcile* the records properly and ensure all *Journal Entries* are " +"balanced and in agreement. To ease and speed up the reconciliation process, " +"you can configure **Reconciliation Models**, which are particularly useful " +"with recurrent entries such as bank fees." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:10 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:67 +msgid "Todo" +msgstr "ที่จะทำ" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:10 +msgid "" +"Add a link to the Reconciliation process in the paragraph above, once the " +"doc will have been updated." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:14 +msgid "" +"Reconciliation Models are also useful to handle *Cash Discounts*. Please " +"refer to :doc:`this documentation <../customer_invoices/cash_discounts>` for" +" more information." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:21 +msgid "Types of Reconciliation Models" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:23 +msgid "There are three types of Reconciliation Models:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:25 +msgid ":ref:`Write-off Button <reconciliation_models_button>`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:26 +msgid "" +":ref:`Suggestion of counterpart values <reconciliation_models_suggestion>`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:27 +msgid ":ref:`Match existing invoices/bills <reconciliation_models_match>`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:32 +msgid "Manually create a write-off on clicked button" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:34 +msgid "" +"When you are reconciling an entry with an *Open Balance*, you can use the " +"buttons available under the *Manual Operations* tab to pre-fill all the " +"values automatically, before validating the reconciliation. Each button is a" +" different Reconciliation Model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model with a write-off button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:45 +msgid "Suggest counterpart values" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:47 +msgid "" +"This type of Reconciliation Model suggests immediately counterpart values " +"that only need to be validated. This automation is based on a set of rules " +"defined in the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model that suggests counterpart values in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:57 +msgid "Match existing invoices/bills" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:59 +msgid "" +"This type of Reconciliation Model automatically selects the right Customer " +"Invoice or Vendor Bill that matches the payment. All that is left to do is " +"to validate the entry. This automation is based on a set of rules defined in" +" the reconciliation model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Example of a Reconciliation Model that matches existing invoices and bills automatically\n" +"in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:71 +msgid "" +"To manage or create new **Reconciliation Models**, go to " +":menuselection:`Accounting --> Reconciliation --> Reconciliation Models`. " +"Alternatively, you can also open this menu from the Accounting Overview, by " +"going to your Bank Journal card, clicking on the three little dots, and then" +" on *Reconciliation Models*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Open the Reconciliation Model menu from the overview dashboard in Odoo " +"Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:81 +msgid "" +"The first entry, named *Invoices Matching Rule*, is the one responsible for " +"the current matching of invoices and bills. Therefore, it is advised to " +"leave it at the top of the list and not to delete it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:85 +msgid "" +"Open the model you want to modify, or click on *Create* to create a new one," +" then fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:88 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:43 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:56 +msgid "Type" +msgstr "ประเภท" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:90 +msgid "" +"See :ref:`above <reconciliation_models_types>` for an explanation about the " +"different types of Reconciliation Models." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:94 +msgid "" +"If the *Documents* application is installed on your database, an additional " +"**Activity type** field appears when *To check* is ticked. Selecting the " +"value *Reconciliation request* implies that, whenever you use this model, a " +"*Request Document* window pops up to request a document from a user." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:100 +msgid "Conditions on Bank Statement Line" +msgstr "บรรทัดรายการเดินบัญชีธนาคาร" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:102 +msgid "" +"Define here all the conditions that are required for a Reconciliation Model " +"to be applied." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:105 +msgid "" +"If a record matches with several Reconciliation Models, the first one in the" +" *sequence* of models will be applied. The sequence is simply the order of " +"the models in the *list view*. They can be rearranged by dragging-and-" +"dropping the handle next to the name." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "" +"Conditions for the Reconciliation Model to be applied in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:114 +msgid "Counterpart Values" +msgstr "บัญชีคู่" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:116 +msgid "" +"This section comprises the values that are applied by the Reconciliation " +"Model." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:118 +msgid "" +"If the value to reconcile needs to be written-off in two separate accounts, " +"click on *Add a second line*." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst-1 +msgid "Counterparts values of a Reconciliation Model in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:127 +msgid ":doc:`reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:129 +msgid ":doc:`../customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:5 +msgid "" +"Importing transactions from your bank statements allows keeping track of " +"bank account transactions and reconciling them with the ones recorded in " +"your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:8 +msgid "" +":doc:`Bank synchronization <bank_synchronization>` automates the process. " +"However, if you do not want to use it or if your bank is not yet supported, " +"other options exist:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:11 +msgid "" +":ref:`Import bank transactions <transactions/import>` delivered by your " +"bank;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:12 +msgid ":ref:`Register bank transactions <transactions/register>` manually." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:15 +msgid "" +":ref:`Grouping transactions by statement <transactions/statements>` is " +"optional." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:20 +msgid "Import transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:22 +msgid "Odoo supports multiple file formats to import transactions:" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:24 +msgid "SEPA recommended Cash Management format (CAMT.053);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:25 +msgid "Comma-separated values (.CSV);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:26 +msgid "Open Financial Exchange (.OFX);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:27 +msgid "Quicken Interchange Format (.QIF);" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:28 +msgid "Belgium: Coded Statement of Account (.CODA)." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:30 +msgid "" +"To import a file, go to the :guilabel:`Accounting Dashboard`, and in the " +":guilabel:`Bank` journal, click on :guilabel:`Import Transactions`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst-1 +msgid "Import bank transactions from the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:36 +msgid "Next, select the file and upload it." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:38 +msgid "" +"After setting the necessary formatting options and mapping the file columns " +"with their related Odoo fields, you can run a :guilabel:`Test` and " +":guilabel:`Import` your bank transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:42 +msgid ":doc:`/applications/general/export_import_data`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:47 +msgid "Register bank transactions manually" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:49 +msgid "" +"You can also record your bank transactions manually. To do so, go to " +":guilabel:`Accounting Dashboard`, click on the :guilabel:`Bank` journal, and" +" then on :guilabel:`New`. Make sure to fill out the :guilabel:`Partner` and " +":guilabel:`Label` fields to ease the reconciliation process." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:56 +msgid "Statements" +msgstr "งบการเงิน" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:58 +msgid "" +"A **bank statement** is a document provided by a bank or financial " +"institution that lists the transactions that have occurred in a particular " +"bank account over a specified period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:61 +msgid "" +"In Odoo Accounting, it is optional to group transactions by their related " +"statement, but depending on your business flow, you may want to record them " +"for control purposes." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:65 +msgid "" +"If you want to compare the ending balances of your bank statements with the " +"ending balances of your financial records, *don't forget to create an " +"opening transaction* to record the bank account balance as of the date you " +"begin synchronizing or importing transactions. This is necessary to ensure " +"the accuracy of your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:70 +msgid "" +"To access a list of statements, go to your :guilabel:`Accounting Dashboard`," +" click on the vertical ellipsis (:guilabel:`⋮`) button next to the bank or " +"cash journal you want to check, then on :guilabel:`Statements`" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:75 +msgid "Statement creation from the kanban view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:77 +msgid "" +"Open the bank reconciliation view by clicking on the name of the bank " +"journal, and identify the transaction corresponding to the last transaction " +"of your bank statement. Click on the :guilabel:`STATEMENT` button when " +"hovering on the upper separator line." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst-1 +msgid "" +"A \"STATEMENT\" button is visible when hovering on the line separating two " +"transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:84 +msgid "" +"Fill out the statement's details and save. The newly created statement " +"includes the previous transactions following the last statement." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:88 +msgid "Statement creation from the list view" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:90 +msgid "" +"Open the list of transactions by clicking on the name of the bank journal " +"and switching to the list view. Select all the transactions corresponding to" +" the bank statement, and, in the :guilabel:`Statement` column, select an " +"existing statement or create a new one by typing its reference, clicking on " +":guilabel:`Create and edit...`, filling out the statement's details, and " +"saving." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:5 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:352 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:346 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 +msgid "Customer invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:8 +msgid "From Customer Invoice to Payments Collection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:10 +msgid "" +"Odoo supports multiple invoicing and payment workflows, so you can choose " +"and use the ones that match your business needs. Whether you want to accept " +"a single payment for a single invoice, or process a payment spanning " +"multiple invoices and taking discounts for early payments, you can do so " +"efficiently and accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:17 +msgid "From Draft Invoice to Profit and Loss" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:19 +msgid "" +"If we pick up at the end of a typical 'order to cash' scenario, after the " +"goods have been shipped, you will: issue an invoice; receive payment; " +"deposit that payment at the bank; make sure the Customer Invoice is closed; " +"follow up if Customers are late; and finally present your Income on the " +"Profit and Loss report and show the decrease in Assets on the Balance Sheet " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:26 +msgid "" +"Invoicing in most countries occurs when a contractual obligation is met. If " +"you ship a box to a customer, you have met the terms of the contract and can" +" bill them. If your supplier sends you a shipment, they have met the terms " +"of that contract and can bill you. Therefore, the terms of the contract is " +"fulfilled when the box moves to or from the truck. At this point, Odoo " +"supports the creation of what is called a Draft Invoice by Warehouse staff." +msgstr "" +"การออกใบแจ้งหนี้ในประเทศส่วนใหญ่เกิดขึ้นเมื่อปฏิบัติตามข้อผูกพันตามสัญญา " +"หากคุณจัดส่งกล่องให้กับลูกค้า " +"แสดงว่าคุณปฏิบัติตามเงื่อนไขของสัญญาและสามารถเรียกเก็บเงินจากลูกค้าได้ " +"หากซัพพลายเออร์ของคุณส่งพัสดุถึงคุณ " +"แสดงว่าซัพพลายเออร์ได้ปฏิบัติตามเงื่อนไขของสัญญาและสามารถเรียกเก็บเงินจากคุณได้" +" ดังนั้นเงื่อนไขของสัญญาจึงจะสมบูรณ์เมื่อกล่องเคลื่อนเข้าหรือออกจากรถบรรทุก " +"ณ จุดนี้ Odoo " +"สนับสนุนการสร้างสิ่งที่เรียกว่าร่างใบแจ้งหนี้โดยเจ้าหน้าที่คลังสินค้า" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:35 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:284 +msgid "Invoice creation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:37 +msgid "" +"Draft invoices can be manually generated from other documents such as Sales " +"Orders, Purchase Orders,etc. Although you can create a draft invoice " +"directly if you would like." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:41 +msgid "" +"An invoice must be provided to the customer with the necessary information " +"in order for them to pay for the goods and services ordered and delivered. " +"It must also include other information needed to pay the invoice in a timely" +" and precise manner." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:47 +msgid "Draft invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:49 +msgid "" +"The system generates invoice which are initially set to the Draft state. " +"While these invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:52 +msgid "" +"remain unvalidated, they have no accounting impact within the system. There " +"is nothing to stop users from creating their own draft invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:55 +msgid "Let's create a customer invoice with following information:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:57 +msgid "Customer: Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:58 +msgid "Product: iMac" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:59 +msgid "Quantity: 1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:60 +msgid "Unit Price: 100" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:61 +msgid "Taxes: Tax 15%" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:67 +msgid "The document is composed of three parts:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:69 +msgid "the top of the invoice, with customer information," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:70 +msgid "the main body of the invoice, with detailed invoice lines," +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:71 +msgid "the bottom of the page, with detail about the taxes, and the totals." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:74 +msgid "Open or Pro-forma invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:76 +msgid "" +"An invoice will usually include the quantity and the price of goods and/or " +"services, the date, any parties involved, the unique invoice number, and any" +" tax information." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:80 +msgid "" +"\"Validate\" the invoice when you are ready to approve it. The invoice then " +"moves from the Draft state to the Open state." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:83 +msgid "" +"When you have validated an invoice, Odoo gives it a unique number from a " +"defined, and modifiable, sequence." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:88 +msgid "" +"Accounting entries corresponding to this invoice are automatically generated" +" when you validate the invoice. You can see the details by clicking on the " +"entry in the Journal Entry field in the \"Other Info\" tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:96 +msgid "Send the invoice to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:98 +msgid "" +"After validating the customer invoice, you can directly send it to the " +"customer via the 'Send by email' functionality." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:103 +msgid "" +"A typical journal entry generated from a validated invoice will look like as" +" follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:56 +msgid "**Account**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Partner**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +msgid "**Due date**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:40 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Debit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:82 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:99 +msgid "**Credit**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:58 +msgid "Accounts Receivable" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "Agrolait" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +msgid "01/07/2015" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +msgid "115" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/taxes.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:167 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:180 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:366 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:376 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:73 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:246 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:121 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:116 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:51 +msgid "Taxes" +msgstr "ภาษี" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "15" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:142 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:146 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:150 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:154 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:158 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:162 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "Sales" +msgstr "การขาย" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +#: ../../content/applications/finance/accounting/taxes.rst:112 +msgid "100" +msgstr "100" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:117 +msgid "Payment" +msgstr "การชำระเงิน" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:119 +msgid "" +"In Odoo, an invoice is considered to be paid when the associated accounting " +"entry has been reconciled with the payment entries. If there has not been a " +"reconciliation, the invoice will remain in the Open state until you have " +"entered the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:124 +msgid "" +"A typical journal entry generated from a payment will look like as follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:67 +msgid "Bank" +msgstr "ธนาคาร" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:136 +msgid "Receive a partial payment through the bank statement" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:138 +msgid "" +"You can manually enter your bank statements in Odoo, or you can import them " +"in from a csv file or from several other predefined formats according to " +"your accounting localisation." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:142 +msgid "" +"Create a bank statement from the accounting dashboard with the related " +"journal and enter an amount of $100 ." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:148 +msgid "Reconcile" +msgstr "กระทบยอด" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:150 +msgid "Now let's reconcile!" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:154 +msgid "" +"You can now go through every transaction and reconcile them or you can mass " +"reconcile with instructions at the bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:156 +msgid "" +"After reconciling the items in the sheet, the related invoice will now " +"display \"You have outstanding payments for this customer. You can reconcile" +" them to pay this invoice. \"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:164 +msgid "" +"Apply the payment. Below, you can see that the payment has been added to the" +" invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:170 +msgid "Payment Followup" +msgstr "ติดตามการชำระเงิน" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:172 +msgid "" +"There's a growing trend of customers paying bills later and later. " +"Therefore, collectors must make every effort to collect money and collect it" +" faster." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:176 +msgid "" +"Odoo will help you define your follow-up strategy. To remind customers to " +"pay their outstanding invoices, you can define different actions depending " +"on how severely overdue the customer is. These actions are bundled into " +"follow-up levels that are triggered when the due date of an invoice has " +"passed a certain number of days. If there are other overdue invoices for the" +" same customer, the actions of the most overdue invoice will be executed." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:184 +msgid "" +"By going to the customer record and diving into the \"Overdue Payments\" you" +" will see the follow-up message and all overdue invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:194 +msgid "Customer aging report:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:196 +msgid "" +"The customer aging report will be an additional key tool for the collector " +"to understand the customer credit issues, and to prioritize their work." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:200 +msgid "" +"Use the aging report to determine which customers are overdue and begin your" +" collection efforts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:208 +msgid "" +"The Profit and Loss statement displays your revenue and expense details. " +"Ultimately, this gives you a clear image of your Net Profit and Loss. It is " +"sometimes referred to as the \"Income Statement\" or \"Statement of Revenues" +" and Expenses.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:218 +msgid "" +"The balance sheet summarizes your company's liabilities, assets and equity " +"at a specific moment in time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices.rst:225 +msgid "" +"For example, if you manage your inventory using the perpetual accounting " +"method, you should expect a decrease in account \"Current Assets\" once the " +"material has been shipped to the customer." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:3 +msgid "Cash discounts and tax reduction" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:5 +msgid "" +"**Cash discounts** are reductions in the amount a customer must pay for " +"goods or services offered as an incentive for paying their invoice promptly." +" These discounts are typically a percentage of the total invoice amount and " +"are applied if the customer pays within a specified time. Cash discounts can" +" help a company maintain a steady cash flow." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:11 +msgid "" +"You issue a €100 invoice on the 1st of January. The full payment is due " +"within 30 days, and you also offer a 2% discount if your customer pays you " +"within seven days." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:14 +msgid "" +"The customer can pay €98 up to the 8th of January. After that date, they " +"would have to pay €100 by the 31st of January." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:17 +msgid "" +"A :ref:`tax reduction <cash-discounts/tax-reductions>` can also be applied " +"depending on the country or region." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:21 +msgid ":doc:`payment_terms`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:22 +#: ../../content/applications/finance/accounting/payments/batch.rst:67 +msgid ":doc:`../payments`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:29 +msgid "" +"To grant cash discounts to customers, you must first verify the :ref:`gain " +"and loss accounts <cash-discounts/gain-loss-accounts>`. Then, configure " +":ref:`payment terms <cash-discounts/payment-terms>` and add a cash discount " +"by checking the :guilabel:`Early Discount` checkbox and filling in the " +"discount percentage, discount days, and :ref:`tax reduction <cash-" +"discounts/tax-reductions>` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:38 +msgid "Cash discount gain/loss accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:40 +msgid "" +"With a cash discount, the amount you earn depends on whether the customer " +"benefits from the cash discount or not. This inevitably leads to gains and " +"losses, which are recorded on default accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:43 +msgid "" +"To modify these accounts, go to :menuselection:`Accounting --> Configuration" +" --> Settings`, and, in the :guilabel:`Default Accounts` section, select the" +" accounts you want to use for the :guilabel:`Cash Discount Gain account` and" +" :guilabel:`Cash Discount Loss account`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:50 +msgid "Payment terms" +msgstr "เงื่อนไขการชําระเงิน" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:52 +msgid "" +"Cash discounts are defined on :doc:`payment terms <payment_terms>`. " +"Configure them to your liking by going to :menuselection:`Accounting --> " +"Configuration --> Payment Terms`, and make sure to fill out the discount " +"percentage, discount days, and :ref:`tax reduction <cash-discounts/tax-" +"reductions>` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"Configuration of payment terms named \"2/7 Net 30\". The field \"Description on Invoices\"\n" +"reads: \"Payment terms: 30 Days, 2% Early Payment Discount under 7 days\"." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:64 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:66 +msgid "" +"Depending on the country or region, the base amount used to compute the tax " +"can vary, which can lead to a **tax reduction**. Since tax reductions are " +"set on individual payment terms, each term can use a specific tax reduction." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:70 +msgid "" +"To configure how the tax reduction is applied, go to a payment term with the" +" :guilabel:`Early Discount` checkbox enabled, and select one of the three " +"following options:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:75 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:94 +msgid "Always (upon invoice)" +msgstr "เสมอ (ตามใบแจ้งหนี้)" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:74 +msgid "" +"The tax is always reduced. The base amount used to compute the tax is the " +"discounted amount, whether the customer benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:80 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:109 +msgid "On early payment" +msgstr "ในการชำระเงินก่อนกำหนด" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:78 +msgid "" +"The tax is reduced only if the customer pays early. The base amount used to " +"compute the tax is the same as the sale: if the customer benefits from the " +"reduction, then the tax is reduced. This means that, depending on the " +"customer, the tax amount can vary after the invoice is issued." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:84 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:124 +msgid "Never" +msgstr "ไม่เคย" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:83 +msgid "" +"The tax is never reduced. The base amount used to compute the tax is the " +"full amount, whether the customer benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:88 +msgid "" +"You issue a €100 invoice (tax-excluded) on the 1st of January, with a 21% " +"tax rate. The full payment is due within 30 days, and you also offer a 2% " +"discount if your customer pays you within seven days." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:99 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:114 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:129 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +msgid "Due date" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:100 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:115 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:130 +msgid "Total amount due" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:101 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:116 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:131 +msgid "Computation" +msgstr "การคำนวณ" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:102 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:117 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:132 +msgid "8th of January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:103 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:118 +msgid "€118.58" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:104 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:119 +msgid "€98 + (21% of €98)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:120 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:135 +msgid "31st of January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:106 +msgid "€120.58" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:107 +msgid "€100 + (21% of €98)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:121 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:136 +msgid "€121.00" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:122 +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:137 +msgid "€100 + (21% of €100)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:133 +msgid "€119.00" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:134 +msgid "€98 + (21% of €100)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:140 +msgid "" +":ref:`Tax grids <tax-returns/tax-grids>`, which are used for the tax report," +" are correctly computed according to the :ref:`type of tax reduction <cash-" +"discounts/tax-reductions>` you configured." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:143 +msgid "" +"The **type of cash discount tax reduction** may be correctly pre-configured," +" depending on your :ref:`fiscal localization package " +"<fiscal_localizations/packages>`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:149 +msgid "Apply a cash discount to a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:151 +msgid "" +"On a customer invoice, apply a cash discount by selecting the :ref:`payment " +"terms you created <cash-discounts/payment-terms>`. Odoo automatically " +"computes the correct amounts, tax amounts, due dates, and accounting " +"records." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:155 +msgid "" +"Under the :guilabel:`Journal Items` tab, you can display the discount " +"details by clicking on the \"toggle\" button and adding the " +":guilabel:`Discount Date` and :guilabel:`Discount Amount` columns." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"An invoice of €100.00 with \"2/7 Net 30\" selected as payment terms. The \"Journal Items\" tab\n" +"is open, and the \"Discount Date\" and \"Discount Amount\" columns are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:162 +msgid "" +"The discount amount and due date are also displayed on the generated invoice" +" report sent to the customer if the :guilabel:`Show installment dates` " +"option is checked on the payment terms." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst-1 +msgid "" +"An invoice of €100.00 with the following text added to the terms and conditions: \"30\n" +"Days, 2% Early Payment Discount under 7 days. 118.58 € due if paid before 01/08/2023.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:170 +msgid "Payment reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:172 +msgid "" +"When you record a :doc:`payment <../payments>` or :doc:`reconcile your bank " +"transactions <../bank/reconciliation>`, Odoo takes the customer payment's " +"date into account to determine if the customer can benefit from the cash " +"discount or not." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_discounts.rst:177 +msgid "" +"If your customer pays the discount amount *after* the discount date, you can" +" always decide to mark the invoice as fully paid with a write-off or as " +"partially paid." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "การปัดเศษเงินสด" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and enable " +"*Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:22 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Cash Roundings`, and " +"click on *Create*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:25 +msgid "" +"Define here your *Rounding Precision*, *Rounding Strategy*, and *Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:28 +msgid "Odoo supports two **rounding strategies**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:30 +msgid "" +"**Add a rounding line**: a *rounding* line is added on the invoice. You have" +" to define which account records the cash roundings." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:33 +msgid "**Modify tax amount**: the rounding is applied in the taxes section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:36 +msgid "Apply roundings" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/cash_rounding.rst:38 +msgid "" +"When editing a draft invoice, open the *Other Info* tab, go to the " +"*Accounting Information* section, and select the appropriate *Cash Rounding " +"Method*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:3 +msgid "Credit notes and refunds" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:5 +msgid "" +"A **credit/debit note**, or **credit/debit memo**, is a document issued to a" +" customer that notifies them that they have been *credited/debited* a " +"certain amount." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:8 +msgid "Several use cases can lead to a credit note, such as:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:10 +msgid "a mistake in the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:11 +msgid "a return of the goods, or a rejection of the services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:12 +msgid "the goods delivered are damaged" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:14 +msgid "" +"Debit notes are less common but are most frequently used to track debts owed" +" by customers or to vendors because of modifications to confirmed customer " +"invoices or vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:18 +msgid "" +"Issuing a credit/debit note is the only legal way to cancel, refund, or " +"modify a validated invoice. Do not forget to **register the payment** " +"afterward if you need to send money back to your customer and/or validate " +"the :doc:`return </applications/sales/sales/products_prices/returns>` if a " +"storable product is returned." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:27 +msgid "Issue a credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:29 +msgid "" +"You can create a credit note from scratch by going to " +":menuselection:`Accounting --> Customers --> Credit Notes`, and by clicking " +"on :guilabel:`Create`. Filling out a credit note form works the same way as " +"an invoice form." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:33 +msgid "" +"However, most of the time, credit notes are generated directly from the " +"related invoices. To do so, go to :menuselection:`Accounting --> Customers " +"--> Invoices`, open the related **customer invoice**, and click on " +":guilabel:`Credit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:37 +msgid "You can choose between three options:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:39 +msgid ":guilabel:`Partial Refund`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:40 +msgid ":guilabel:`Full Refund`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:41 +msgid ":guilabel:`Full refund and new draft invoice`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:44 +msgid "" +"A credit note sequence starts with `R` and is followed by the number of the " +"related document (e.g., RINV/2019/0004 is related to the invoice " +"INV/2019/0004)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:48 +msgid "Partial refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:50 +msgid "" +"When selecting the :guilabel:`Partial Refund` option, Odoo creates a draft " +"credit note already prefilled with all the necessary information from the " +"original invoice. This is the option to choose if you wish to do a partial " +"refund or if you want to modify any detail of the credit note." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:55 +msgid "This is the only option for invoices marked as *in payment* or *paid*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:58 +msgid "Full refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:60 +msgid "" +"When selecting the :guilabel:`Full Refund` option, Odoo creates a credit " +"note, automatically validates it, and reconciles it with the related " +"invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst-1 +msgid "Full refund credit note." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:66 +msgid "" +"This is the option to choose for a full refund or to **cancel** a " +"*validated* invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:69 +msgid "Full refund and new draft invoice" +msgstr "การคืนเงินเต็มจํานวนและใบแจ้งหนี้ฉบับร่างใหม่" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:71 +msgid "" +"When selecting the :guilabel:`Full refund and new draft invoice` option, " +"Odoo creates a credit note, automatically validates it, reconciles it with " +"the related invoice, and opens a new draft invoice prefilled with the same " +"details from the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:75 +msgid "This is the option to **modify** the content of a *validated* invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:80 +msgid "Issue a debit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:82 +msgid "" +"You can create a debit note from scratch by going to " +":menuselection:`Accounting --> Customers --> Invoices` or by clicking on the" +" related invoice you wish to issue a debit note for. On the invoice form " +"view, click :guilabel:`Cog icon (⚙) --> Debit Note`, fill in the " +"information, and click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:88 +msgid "Record a vendor refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:90 +msgid "**Vendor refunds** are recorded the same way as credit notes:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:92 +msgid "" +"You can either create a credit note from scratch by going to " +":menuselection:`Accounting --> Vendors --> Refund`, and by clicking on " +":guilabel:`Create`; or by opening the related **vendor bill**, and clicking " +"on :guilabel:`Credit Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:97 +msgid "Record a debit note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:99 +msgid "" +"**Debit notes** from vendors are recorded in a similar way to how they are " +"issued to customers:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:101 +msgid "" +"Go to :menuselection:`Accounting --> Vendors --> Bills`, open the related " +"bill you wish to record a debit note for, and click :guilabel:`Cog icon (⚙) " +"--> Debit Note`. Fill in the information, and click :guilabel:`Create Debit " +"Note`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:106 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:111 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:135 +#: ../../content/applications/finance/accounting/payments/checks.rst:84 +msgid "Journal entries" +msgstr "รายการสมุดรายวัน" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:108 +msgid "" +"Issuing a credit/debit note from an invoice/bill creates a **reverse entry**" +" that zeroes out the journal items generated by the original invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:113 +msgid "The journal invoice of an entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:0 +msgid "Invoice journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:118 +msgid "" +"And here is the credit note’s journal entry generated to reverse the " +"original invoice above:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/credit_notes.rst:0 +msgid "Credit note journal entry reverses the invoice journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:3 +msgid "Delivery and invoice addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:5 +msgid "" +"Companies often have multiple locations, and it is common that a customer " +"invoice should be sent to one address and the delivery should be sent to " +"another. Odoo's **Customer Addresses** feature is designed to handle this " +"scenario by making it easy to specify which address to use for each case." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:10 +msgid ":doc:`overview`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:15 +msgid "" +"To specify a sales order's invoice and delivery addresses, first go to " +":menuselection:`Accounting --> Configuration --> Settings`. In the " +":guilabel:`Customer Invoices` section, enable :guilabel:`Customer Addresses`" +" and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:19 +msgid "" +"On quotations and sales orders, there are now fields for :guilabel:`Invoice " +"Address` and :guilabel:`Delivery Address`. If the customer has an invoice or" +" delivery address listed on their contact record, the corresponding field " +"will use that address by default, but any contact's address can be used " +"instead." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:25 +msgid "Invoice and deliver to different addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:27 +msgid "" +"Delivery orders and their delivery slip reports use the address set as the " +":guilabel:`Delivery Address` on the sales order. By default, invoice reports" +" show both the shipping address and the invoice address to assure the " +"customer that the delivery is going to the correct location." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:31 +msgid "" +"Emails also go to different addresses. The quotation and sales order are " +"sent to the main contact's email, as usual, but the invoice is sent to the " +"email of the address set as the :guilabel:`Invoice Address` on the sales " +"order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 +msgid "" +"Reports, such as the delivery slip and invoice report, can be " +":doc:`customized using Studio " +"</applications/productivity/studio/pdf_reports>`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:38 +msgid "" +"If :doc:`Send by Post <snailmail>` is checked when you click :guilabel:`Send" +" & Print`, the invoice will be mailed to the invoice address." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:3 +msgid "Deferred revenues" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:5 +msgid "" +"**Deferred revenues**, or **unearned revenues**, are invoices addressed to " +"customers for goods yet to be delivered or services yet to be rendered." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:8 +msgid "" +"The company cannot report them on the current **profit and loss statement**," +" or *income statement*, since the goods and services will be effectively " +"delivered/rendered in the future." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:11 +msgid "" +"These future revenues must be deferred on the company's balance sheet among " +"the current liabilities until they can be **recognized**, at once or over a " +"defined period, on the profit and loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:15 +msgid "" +"For example, let's say a business sells a software license of $1200 for 1 " +"year. They immediately invoice it to the customer but can't consider it " +"earned yet, as the future months of licensing have not yet been delivered. " +"Therefore, they post this new revenue in a deferred revenue account and " +"recognize it on a monthly basis. Each month, for the next 12 months, $100 " +"will be recognized as revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:21 +msgid "" +"Odoo Accounting handles deferred revenues by spreading them in multiple " +"entries that are posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:25 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:25 +msgid "" +"The server checks once a day if an entry must be posted. It might then take " +"up to 24 hours before you see a change from :guilabel:`Draft` to " +":guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:31 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:31 +msgid "" +"Make sure the default settings are correctly configured for your business. " +"To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"The following options are available:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:34 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:34 +msgid "Journal" +msgstr "สมุดรายวัน" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:35 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:35 +msgid "The deferral entries are posted in this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:36 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:36 +msgid "Deferred Expense Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:37 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:37 +msgid "" +"Expenses are deferred on this Current Asset account until they are " +"recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:38 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:38 +msgid "Deferred Revenue Account" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:39 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:39 +msgid "" +"Revenues are deferred on this Current Liability account until they are " +"recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:43 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:43 +msgid "Generate Entries" +msgstr "สร้างรายการ" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:41 +msgid "" +"By default, Odoo :ref:`automatically generates " +"<customer_invoices/deferred/generate_on_validation>` the deferral entries " +"when you post a customer invoice. However, you can also choose to " +":ref:`generate them manually <customer_invoices/deferred/generate_manually>`" +" by selecting the :guilabel:`Manually & Grouped` option instead." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:48 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:48 +msgid "Amount Computation" +msgstr "การคำนวณจำนวนเงิน" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:46 +msgid "" +"Suppose an invoice of $1200 must be deferred over 12 months. The " +":guilabel:`Equal per month` computation accounts for $100 each month, while " +"the :guilabel:`Based on days` computation accounts for different amounts " +"depending on the number of days in each month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:53 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:53 +msgid "Generate deferral entries on validation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:56 +msgid "" +"Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are " +"visible in the :guilabel:`Invoice Lines` tab. In most cases, the " +":guilabel:`Start Date` should be in the same month as the :guilabel:`Invoice" +" Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 +msgid "" +"For each line of the invoice that should be deferred, specify the start and " +"end dates of the deferral period." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:63 +msgid "" +"If the :guilabel:`Generate Entries` field in the **Settings** is set to " +":guilabel:`On invoice/bill validation`, Odoo automatically generates the " +"deferral entries when the invoice is validated. Click the " +":guilabel:`Deferred Entries` smart button to see them." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:67 +msgid "" +"One entry, dated on the same day as the invoice, moves the invoice amounts " +"from the income account to the deferred account. The other entries are " +"deferral entries which, month after month, move the invoice amounts from the" +" deferred account to the income account to recognize the revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:72 +msgid "" +"You can defer a January invoice of $1200 over 12 months by specifying a " +"start date of 01/01/2023 and an end date of 12/31/2023. At the end of " +"August, $800 is recognized as an income, whereas $400 remains on the " +"deferred account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:79 +msgid "" +"The deferred revenue report computes an overview of the necessary deferral " +"entries for each account. To access it, go to :menuselection:`Accounting -->" +" Reporting --> Deferred Revenue`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:82 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:82 +msgid "" +"To view the journal items of each account, click on the account name and " +"then :guilabel:`Journal Items`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst-1 +msgid "Deferred revenue report" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:89 +msgid "" +"Only invoices whose accounting date is before the end of the period of the " +"report are taken into account." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:95 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:95 +msgid "Generate grouped deferral entries manually" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:97 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 +msgid "" +"If you have a lot of deferred revenues and wish to reduce the number of " +"journal entries created, you can generate deferral entries manually. To do " +"so, set the :guilabel:`Generate Entries` field in the **Settings** to " +":guilabel:`Manually & Grouped`. Odoo then aggregates the deferred amounts in" +" a single entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:102 +msgid "" +"At the end of each month, go to :menuselection:`Accounting --> Reporting -->" +" Deferred Revenue` and click the :guilabel:`Generate Entries` button. This " +"generates two deferral entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:105 +msgid "" +"One dated at the end of the month which aggregates, for each account, all " +"the deferred amounts of that month. This means that a part of the deferred " +"revenue is recognized at the end of that period." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:108 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:108 +msgid "" +"The reversal of this created entry, dated on the following day (i.e., the " +"first day of the next month) to cancel the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:112 +msgid "There are two invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:114 +msgid "Invoice A: $1200 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 +msgid "Invoice B: $600 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "In January" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:118 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:119 +msgid "" +"At the end of January, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:121 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:122 +msgid "Entry 1 dated on the 31st January:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:123 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:140 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:156 +msgid "" +"Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both" +" invoices)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:124 +msgid "" +"Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of invoice A " +"and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +msgid "" +"Line 3: Deferred account 1800 - 150 = **1650** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:128 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:129 +msgid "Entry 2 dated on the 1st February, the reversal of the previous entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:130 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:131 +msgid "Line 1: Expense account **1800**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:131 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:132 +msgid "Line 2: Deferred account **-150**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 +msgid "Line 3: Expense account **-1650**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "In February" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:135 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:136 +msgid "" +"At the end of February, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:138 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:139 +msgid "Entry 1 dated on the 28th February:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:141 +msgid "" +"Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of invoice A " +"and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:143 +msgid "" +"Line 3: Deferred account 1800 - 300 = **1500** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:145 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:146 +msgid "Entry 2 dated on the 1st March, the reversal of the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "From March to October" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:148 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:149 +msgid "The same computation is done for each month until October." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "In November" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:151 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:152 +msgid "" +"At the end of November, after clicking the :guilabel:`Generate Entries` " +"button, there are the following entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:154 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:155 +msgid "Entry 1 dated on the 30th November:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 +msgid "" +"Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of invoice " +"A and invoice B)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:159 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:159 +msgid "" +"Line 3: Deferred account 1800 - 1650 = **150** (amount that has yet to be " +"deferred later on)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:162 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:162 +msgid "Entry 2 dated on the 1st December, the reversal of the previous entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:166 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:166 +msgid "In December" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:165 +msgid "" +"There is no need to generate entries in December. Indeed, if we do the " +"computation for December, we have an amount of 0 to be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "In total" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:169 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:169 +msgid "If we aggregate everything, we would have:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:171 +msgid "invoice A and invoice B" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 +msgid "" +"two entries (one for the deferral and one for the reversal) for each month " +"from January to November" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:175 +msgid "" +"Therefore, at the end of December, invoices A and B are fully recognized as " +"income only once in spite of all the created entries thanks to the reversal " +"mechanism." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:3 +msgid "Electronic invoicing (:abbr:`EDI (electronic data interchange)`)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:5 +msgid "" +"EDI, or electronic data interchange, is the inter-company communication of " +"business documents, such as purchase orders and invoices, in a standard " +"format. Sending documents according to an EDI standard ensures that the " +"machine receiving the message can interpret the information correctly. " +"Various EDI file formats exist and are available depending on your company's" +" country." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:10 +msgid "" +"EDI feature enables automating the administration between companies and " +"might also be required by some governments for fiscal control or to " +"facilitate the administration." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:13 +msgid "" +"Electronic invoicing of your documents such as customer invoices, credit " +"notes or vendor bills is one of the application of EDI." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:16 +msgid "Odoo supports, among others, the following formats." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:21 +msgid "Format Name" +msgstr "ชื่อรูปแบบ" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:22 +msgid "Applicability" +msgstr "การบังคับใช้" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:23 +msgid "Factur-X (CII)" +msgstr "Factur-X (CII)" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:24 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:26 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:28 +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:50 +msgid "All customers" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:25 +msgid "Peppol BIS Billing 3.0" +msgstr "Peppol BIS Billing 3.0" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:27 +msgid "XRechnung (UBL)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:29 +msgid "Fattura PA (IT)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:30 +msgid "Italian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:31 +msgid "CFDI (4.0)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:32 +msgid "Mexican companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:33 +msgid "Peru UBL 2.1" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:34 +msgid "Peruvian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:35 +msgid "SII IVA Llevanza de libros registro (ES)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:36 +msgid "Spanish companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:37 +msgid "UBL 2.1 (Columbia)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:38 +msgid "Colombian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:39 +msgid "Egyptian Tax Authority" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:40 +msgid "Egyptian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:41 +msgid "E-Invoice (IN)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:42 +msgid "Indian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:43 +msgid "NLCIUS (Netherlands)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:44 +msgid "Dutch companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:45 +msgid "EHF 3.0" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:46 +msgid "Norwegian companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:47 +msgid "SG BIS Billing 3.0" +msgstr "SG BIS Billing 3.0" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:48 +msgid "Singaporean companies" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:49 +msgid "A-NZ BIS Billing 3.0" +msgstr "A-NZ BIS Billing 3.0" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:53 +msgid "" +"The **Factur-X (CII)** format enables validation checks on the invoice and " +"generates PDF/A-3 compliant files." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:55 +msgid "" +"Every PDF generated by Odoo includes an integrated **Factur-X** XML file." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:182 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:123 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:38 +msgid ":doc:`../../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:65 +msgid "" +"By default, the format available in the :ref:`send window " +"<e-invoicing/generation>` depends on your customer's country." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:68 +msgid "" +"You can define a specific e-invoicing format for each customer. To do so, go" +" to :menuselection:`Accounting --> Customers --> Customers`, open the " +"customer form, go to the :guilabel:`Accounting` tab and select the " +"appropriate format." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Select an EDI format for a specific customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:76 +msgid "National electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:78 +msgid "" +"Depending on your company's country (e.g., :doc:`Italy " +"<../../fiscal_localizations/italy>`, :doc:`Spain " +"<../../fiscal_localizations/spain>`, :doc:`Mexico " +"<../../fiscal_localizations/mexico>`, etc.), you may be required to issue " +"e-invoicing documents in a specific format for all your invoices. In this " +"case, you can define a default e-invoicing format for your sales journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:84 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open your sales journal, go to the :guilabel:`Advanced Settings` tab, and " +"enable the formats you need for this journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:90 +msgid "E-invoices generation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:92 +msgid "" +"From a confirmed invoice, click :guilabel:`Send & Print` to open the send " +"window. Check the e-invoicing option to generate and attach the e-invoice " +"file." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "" +"The Peppol option is checked and an e-invoicing XML file is attached to the " +"email." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:99 +msgid "Peppol" +msgstr "Peppol" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:101 +msgid "" +"The `Peppol <https://peppol.org/about/>`_ network ensures the exchange of " +"documents and information between enterprises and governmental authorities. " +"It is primarily used for electronic invoicing, and its access points " +"(connectors to the Peppol network) allow enterprises to exchange electronic " +"documents." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:106 +msgid "" +"Odoo is an **access point** and an :abbr:`SMP (Service Metadata Publisher)`," +" enabling electronic invoicing transactions without the need to send " +"invoices and bills by email or post." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:109 +msgid "" +"If not done yet, :ref:`install <general/install>` the :guilabel:`Peppol` " +"module (`account_peppol`)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:112 +msgid "Peppol registration is **free** and available in Odoo Community" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:113 +msgid "" +"You can send **Customer Invoices** and **Credit Notes** and receive **Vendor" +" Bills** and **Refunds** via Peppol." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:115 +msgid "" +"You can send in one of the following supported document formats: **BIS " +"Billing 3.0, XRechnung CIUS, NLCIUS**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "" +"The following **countries** are eligible for **Peppol registration in " +"Odoo**:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "" +"Andorra, Albania, Austria, Bosnia and Herzegovina, Belgium, Bulgaria, " +"Switzerland, Cyprus, Czech Republic, Germany, Denmark, Estonia, Spain, " +"Finland, France, United Kingdom, Greece, Croatia, Hungary, Ireland, Iceland," +" Italy, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Montenegro, " +"North Macedonia, Malta, Netherlands, Norway, Poland, Portugal, Romania, " +"Serbia, Sweden, Slovenia, Slovakia, San Marino, Turkey, Holy See (Vatican " +"City State)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:125 +msgid "Registration" +msgstr "การลงทะเบียน" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:127 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. If you do " +"not have the Peppol module installed, first tick the :guilabel:`Enable " +"PEPPOL` checkbox and then **manually save**." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Peppol module installation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:134 +msgid "Fill in the following information:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:136 +msgid "" +":guilabel:`Peppol EAS`. This is the Peppol Electronic Address Scheme and " +"usually depends on your company's country. Odoo often prefills this with the" +" most commonly used EAS code in your country. For example, the preferred EAS" +" code for most companies in Belgium is 0208." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:139 +msgid "" +":guilabel:`Peppol Endpoint`. This is usually a Company Registry number or a " +"VAT number." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:140 +msgid "" +":guilabel:`Phone Number`, including the country code (e.g., `+32` in " +"Belgium)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:141 +msgid ":guilabel:`Primary contact email`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:144 +msgid "" +"`Peppol EAS - European Commision <https://ec.europa.eu/digital-building-" +"blocks/wikis/display/DIGITAL/Code+lists/>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:145 +msgid "" +"`Peppol Endpoint - OpenPeppol eDEC Code Lists " +"<https://docs.peppol.eu/edelivery/codelists/>`_ (open the \"Participant " +"Identifier Schemes\" as HTML page)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:148 +msgid "" +"If you are migrating from another access point, insert the " +":guilabel:`Migration key` from the previous provider." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Configuration for peppol" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:154 +msgid "" +"Finally, click :guilabel:`Validate registration`. If you want to explore or " +"demo Peppol, you can choose to register in :guilabel:`Demo` mode. Otherwise," +" select :guilabel:`Live`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol demo mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:161 +msgid "" +"When testing Peppol, the system parameter `account_peppol.edi.mode` can be " +"changed to `test`. Then, a radio button appears with the option to register " +"on the test server." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode parameter" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:0 +msgid "Peppol test mode selection" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:170 +msgid "" +"Now, you can request a verification code to be sent to you by clicking " +":guilabel:`Verify phone number`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "phone validation request verification" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:176 +msgid "" +"A text message containing a code is sent to the phone number provided to " +"finalize the verification process." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "phone validation" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:182 +msgid "" +"Once you enter the code and click :guilabel:`Confirm`, you can see that your" +" registration is pending activation. From this point onwards, the default " +"journal for receiving Vendor Bills can be set." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "pending application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:188 +msgid "It should be automatically activated within a day." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:191 +msgid "" +"It is also possible to manually trigger the cron that checks the " +"registration status by going to :menuselection:`Settings --> Technical --> " +"Scheduled Actions --> PEPPOL\\: update participant status`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:195 +msgid "" +"Your application status should be updated soon after you are registered on " +"the Peppol network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "active application" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:200 +msgid "" +"All invoices and vendor bills can now be sent directly using the Peppol " +"network." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:203 +msgid "Contact verification" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:205 +msgid "" +"Before sending an invoice to a contact using the Peppol network, it is " +"necessary to verify that they are also registered as a Peppol participant." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:208 +msgid "" +"To do so, go to :menuselection:`Accounting --> Customers --> Customers` and " +"open the customer's form. Then go to :menuselection:`Accounting tab --> " +"Electronic Invoicing`, select the correct format, and make sure their " +":guilabel:`Peppol EAS code` and the :guilabel:`Endpoint` are filled in. " +"Then, click :guilabel:`Verify`. If the contact exists on the network, their " +"Peppol endpoint validity is set to Valid." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "verify contact registration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:218 +msgid "" +"While Odoo prefills both the EAS code and the Endpoint number based on the " +"information available for a contact, it is better to confirm these details " +"directly with the contact." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:221 +msgid "" +"It is possible to verify the Peppol participant status of several customers " +"at once. To do so, go to :menuselection:`Accounting --> Customers --> " +"Customers` and switch to the list view. Select the customers you want to " +"verify and then click :menuselection:`Actions --> Verify Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:226 +msgid "Send invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:228 +msgid "" +"Once ready to send an invoice via the Peppol network, simply click " +":guilabel:`Send & Print` on the invoice form. To queue multiple invoices, " +"select them in the list view and click :menuselection:`Actions --> Send & " +"Print`; they will be sent in a batch later on. Both :guilabel:`BIS Billing " +"3.0` and :guilabel:`Send via PEPPOL` checkboxes need to be ticked." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Send peppol invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:236 +msgid "" +"Posted invoices that can be sent via Peppol are marked as :guilabel:`Peppol " +"Ready`. To display them, use the :guilabel:`Peppol Ready` filter or access " +"the Accounting dashboard and click :guilabel:`Peppol ready invoices` on the " +"corresponding sales journal." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Filter Peppol ready invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:243 +msgid "" +"Once the invoices are sent via Peppol, the status is changed to " +":guilabel:`Processing`. The status is changed to `Done` after they have been" +" successfully delivered to the contact's Access Point." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Peppol message status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:251 +msgid "" +"By default, the Peppol status column is hidden on the Invoices list view. " +"You can choose to have it displayed by selecting it from the optional " +"columns, accessible from the top right corner of the Invoices list view." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:255 +msgid "" +"A cron runs regularly to check the status of these invoices. It is possible " +"to check the status before the cron runs by clicking :guilabel:`Fetch Peppol" +" invoice status` in the corresponding sales journal on the Accounting " +"dashboard." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Fetch invoice Peppol status" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:263 +msgid "Receive vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:265 +msgid "" +"Once a day, a cron checks whether any new documents have been sent to you " +"via the Peppol network. These documents are imported, and the corresponding " +"vendor bills are created automatically as drafts." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "peppol receive bills" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:272 +msgid "" +"If you want to retrieve incoming Peppol documents before the cron runs, you " +"can do so from the Accounting dashboard on the main Peppol purchase journal " +"that you set up in the settings. Just click :guilabel:`Fetch from Peppol`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst-1 +msgid "Fetch bills from Peppol" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:3 +msgid "EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:5 +msgid "" +"European Payments Council quick response codes, or **EPC QR codes**, are " +"two-dimensional barcodes that customers can scan with their **mobile banking" +" applications** to initiate a **SEPA credit transfer (SCT)** and pay their " +"invoices instantly." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:9 +msgid "" +"In addition to bringing ease of use and speed, it greatly reduces typing " +"errors that would potentially make for payment issues." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:13 +msgid "" +"This feature is only available for companies in several European countries " +"such as Austria, Belgium, Finland, Germany, and the Netherlands." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:17 +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:126 +msgid ":doc:`../bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:18 +msgid "" +"`Odoo Academy: QR Code on Invoices for European Customers " +"<https://www.odoo.com/r/VuU>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:23 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and " +"activate the :guilabel:`QR Codes` feature in the :guilabel:`Customer " +"Payments` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:27 +msgid "Configure your bank account's journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:29 +msgid "" +"Make sure that your :guilabel:`Bank Account` is correctly configured in Odoo" +" with your IBAN and BIC." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:31 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open your bank journal, then fill out the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Bank Account Number` column." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "Bank account number column in the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:39 +msgid "Issue invoices with EPC QR codes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:41 +msgid "" +"EPC QR codes are added automatically to your invoices. Customers whose bank " +"supports making payments via EPC QR codes will be able to scan the code and " +"pay the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:44 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> Invoices`, and create a " +"new invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:46 +msgid "" +"Before posting it, open the :guilabel:`Other Info` tab. Odoo automatically " +"fills out the :guilabel:`Recipient Bank` field with your IBAN." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:50 +msgid "" +"In the :guilabel:`Other Info` tab, the account indicated in the " +":guilabel:`Recipient Bank` field is used to receive your customer's payment." +" Odoo automatically populates this field with your IBAN by default and uses " +"it to generate the EPC QR code." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:54 +msgid "" +"When the invoice is printed or previewed, the QR code is included at the " +"bottom." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst-1 +msgid "QR code on a customer invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/epc_qr_code.rst:60 +msgid "" +"If you want to issue an invoice without an EPC QR code, remove the IBAN " +"indicated in the :guilabel:`Recipient Bank` field, under the " +":guilabel:`Other Info` tab of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:3 +msgid "Incoterms" +msgstr "Incoterms" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:5 +msgid "" +":abbr:`Incoterms (International Commercial Terms)` are standardized trade " +"terms used in international transactions to define the rights and " +"responsibilities of buyers and sellers. They establish the obligations " +"related to the delivery of goods, the transfer of risks, and the " +"distribution of costs between the parties involved. Incoterms specify " +"important details, such as the point at which the risk and costs transfer " +"from the seller to the buyer, the responsibility for transportation, " +"insurance, customs clearance, and other relevant aspects of the transaction." +msgstr "" +":abbr:`Incoterms (ข้อกำหนดทางการค้าระหว่างประเทศ)` " +"เป็นข้อกำหนดทางการค้ามาตรฐานที่ใช้ในธุรกรรมระหว่างประเทศเพื่อกำหนดสิทธิ์และความรับผิดชอบของผู้ซื้อและผู้ขาย" +" พวกเขากำหนดภาระผูกพันที่เกี่ยวข้องกับการจัดส่งสินค้า การโอนความเสี่ยง " +"และการกระจายต้นทุนระหว่างฝ่ายต่างๆ ที่เกี่ยวข้อง Incoterm " +"ระบุรายละเอียดที่สำคัญ เช่น " +"จุดที่ความเสี่ยงและต้นทุนโอนจากผู้ขายไปยังผู้ซื้อ ความรับผิดชอบในการขนส่ง " +"การประกันภัย พิธีการศุลกากร และประเด็นอื่นที่เกี่ยวข้องของธุรกรรม" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:13 +msgid "By default, all 11 Incoterms are available in Odoo:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:15 +msgid "**EXW**: Ex works" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:16 +msgid "**FCA**: Free carrier" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:17 +msgid "**FAS**: Free alongside ship" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:18 +msgid "**FOB**: Free on board" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:19 +msgid "**CFR**: Cost and freight" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:20 +msgid "**CIF**: Cost, insurance and freight" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:21 +msgid "**CPT**: Carriage paid to" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:22 +msgid "**CIP**: Carriage and insurance paid to" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:23 +msgid "**DPU**: Delivered at place unloaded" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:24 +msgid "**DAP**: Delivered at place" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:25 +msgid "**DDP**: Delivered duty paid" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:28 +msgid ":doc:`../reporting/intrastat`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:29 +msgid ":doc:`../customer_invoices`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:30 +msgid ":doc:`../vendor_bills`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:35 +msgid "Define an Incoterm" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:37 +msgid "" +"To define an Incoterm manually, create an invoice or bill, click the " +":guilabel:`Other Info` tab, and select the :guilabel:`Incoterm`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:41 +msgid "Incoterm location" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:43 +msgid "" +"A location relevant to the chosen Incoterm can be added to the invoice or " +"bill under :guilabel:`Other Info` in the :guilabel:`Incoterm Location` " +"field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:47 +msgid "" +"If the chosen Incoterm code is `CIF` (Cost, Insurance, Freight), the " +"associated location might be the destination port where the goods will be " +"delivered." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:53 +msgid "Default Incoterm configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/incoterms.rst:55 +msgid "" +"You can set a default Incoterm rule to **automatically** populate the " +"Incoterm field on all newly created invoices and bills. Under " +":menuselection:`Accounting/Invoicing --> Configuration --> Settings`, scroll" +" down to the :guilabel:`Customer Invoices` section, and select an Incoterm " +"in the :guilabel:`Default Incoterm` field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:3 +msgid "Invoicing processes" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:5 +msgid "" +"Depending on your business and the application you use, there are different " +"ways to automate the customer invoice creation in Odoo. Usually, draft " +"invoices are created by the system (with information coming from other " +"documents like sales order or contracts) and accountant just have to " +"validate draft invoices and send the invoices in batch (by regular mail or " +"email)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:12 +msgid "" +"Depending on your business, you may opt for one of the following way to " +"create draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:19 +msgid "Sales Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:21 +msgid "" +"In most companies, salespeople create quotations that become sales order " +"once they are validated. Then, draft invoices are created based on the sales" +" order. You have different options like:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:25 +msgid "" +"Invoice manually: use a button on the sale order to trigger the draft " +"invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:28 +msgid "" +"Invoice before delivery: invoice the full order before triggering the " +"delivery order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:31 +msgid "Invoice based on delivery order: see next section" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:33 +msgid "" +"Invoice before delivery is usually used by the eCommerce application when " +"the customer pays at the order and we deliver afterwards. (pre-paid)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:37 +msgid "" +"For most other use cases, it's recommended to invoice manually. It allows " +"the salesperson to trigger the invoice on demand with options: invoice the " +"whole order, invoice a percentage (advance), invoice some lines, invoice a " +"fixed advance." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:42 +msgid "This process is good for both services and physical products." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:45 +msgid ":doc:`/applications/sales/sales/invoicing/proforma`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:48 +msgid "Sales Order ‣ Delivery Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:50 +msgid "" +"Retailers and eCommerce usually invoice based on delivery orders, instead of" +" sales order. This approach is suitable for businesses where the quantities " +"you deliver may differs from the ordered quantities: foods (invoice based on" +" actual Kg)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:55 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:61 +msgid ":doc:`/applications/sales/sales/invoicing/invoicing_policy`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:64 +msgid "eCommerce Order ‣ Invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:66 +msgid "" +"An eCommerce order will also trigger the creation of the order when it is " +"fully paid. If you allow paying orders by check or wire transfer, Odoo only " +"creates an order and the invoice will be triggered once the payment is " +"received." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:72 +msgid "Contracts" +msgstr "สัญญา" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:75 +msgid "Regular Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:77 +msgid "" +"If you use contracts, you can trigger invoice based on time and material " +"spent, expenses or fixed lines of services/products. Every month, the " +"salesperson will trigger invoice based on activities on the contract." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:81 +msgid "Activities can be:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:83 +msgid "" +"fixed products/services, coming from a sale order linked to this contract" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:84 +msgid "materials purchased (that you will re-invoice)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:85 +msgid "time and material based on timesheets or purchases (subcontracting)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:86 +msgid "" +"expenses like travel and accommodation that you re-invoice to the customer" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:88 +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 "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:94 +msgid ":doc:`/applications/sales/sales/invoicing/time_materials`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:95 +msgid ":doc:`/applications/sales/sales/invoicing/expense`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:96 +msgid ":doc:`/applications/sales/sales/invoicing/milestone`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:99 +msgid "Recurring Contracts ‣ Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:101 +msgid "" +"For subscriptions, an invoice is triggered periodically, automatically. The " +"frequency of the invoicing and the services/products invoiced are defined on" +" the contract." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:106 +msgid ":doc:`/applications/sales/subscriptions`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:109 +msgid "Others" +msgstr "อื่นๆ " + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:112 +msgid "Creating an invoice manually" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:114 +msgid "" +"Users can also create invoices manually without using contracts or a sales " +"order. It's a recommended approach if you do not need to manage the sales " +"process (quotations), or the delivery of the products or services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:119 +msgid "" +"Even if you generate the invoice from a sales order, you may need to create " +"invoices manually in exceptional use cases:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:122 +msgid "if you need to create a refund" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:124 +msgid "If you need to give a discount" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:126 +msgid "if you need to change an invoice created from a sales order" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:128 +msgid "if you need to invoice something not related to your core business" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:131 +msgid "Specific modules" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:133 +msgid "Some specific modules are also able to generate draft invoices:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:135 +msgid "**membership**: invoice your members every year" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:137 +msgid "**repairs**: invoice your after-sale services" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:140 +msgid "Resequencing of the invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:142 +msgid "" +"It remains possible to resequence the invoices but with some restrictions:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:144 +msgid "The feature does not work when entries are previous to a lock date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:145 +msgid "" +"The feature does not work if the sequence is inconsistent with the month of " +"the entry." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:146 +msgid "It does not work if the sequence leads to a duplicate." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:147 +msgid "The order of the invoice remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:148 +msgid "" +"It is useful for people who use a numbering from another software and who " +"want to continue the current year without starting over from the beginning." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:152 +msgid "Invoice digitization with optical character recognition (OCR)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:154 +msgid "" +"**Invoice digitization** is the process of automatically encoding " +"traditional paper invoices into invoices forms in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:157 +msgid "" +"Odoo uses OCR and artificial intelligence technologies to recognize the " +"content of the documents. Vendor bills and customer invoices forms are " +"automatically created and populated based on scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/overview.rst:162 +msgid "" +":doc:`/applications/finance/accounting/vendor_bills/invoice_digitization`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:3 +msgid "Payment terms and installment plans" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:5 +msgid "" +"**Payment terms** specify all the conditions of a sale's payment to help " +"ensure customers pay their invoices correctly and on time." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:8 +msgid "" +"Payment terms are generally defined on documents such as sales orders, " +"customer invoices, and vendor bills. Payment terms cover:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:11 +msgid "The due date(s)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:12 +msgid "Early payment discounts" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:13 +msgid "Any other conditions on the payment" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:15 +msgid "" +"An **installment plan** allows the customers to pay an invoice in parts, " +"with the amounts and payment dates defined beforehand by the seller." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:19 +msgid "Immediate Payment" +msgstr "ชำระทันที" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:20 +msgid "The full payment is due on the day of the invoice's issuance." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:21 +msgid "15 Days (or Net 15)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:22 +msgid "The full payment is due 15 days after the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:23 +msgid "21 MFI" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:24 +msgid "" +"The full payment is due by the 21st of the month following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:26 +msgid "30% Advance End of Following Month" +msgstr "ล่วงหน้า 30% เสร็จสิ้นเดือนถัดไป" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:26 +msgid "" +"30% is due on the day of the invoice's issuance. The remaining balance is " +"due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:29 +msgid "2% 10, Net 30 EOM" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:29 +msgid "" +"A 2% :doc:`cash discount <cash_discounts>` if the payment is received within" +" ten days. Otherwise, the full payment is due at the end of the month " +"following the invoice date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:33 +msgid "" +"Payment terms are not to be confused with :doc:`down payment invoices " +"</applications/sales/sales/invoicing/down_payment>`. If, for a specific " +"order, you issue multiple invoices to your customer, that is neither a " +"payment term nor an installment plan but an invoicing policy." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:37 +msgid "" +"This page is about the *payment terms* feature, not :doc:`terms & conditions" +" <terms_conditions>`, which can be used to declare contractual obligations " +"regarding content use, return policies, and other policies surrounding the " +"sale of goods and services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:42 +msgid "" +"`Odoo Tutorials: payment terms <https://www.odoo.com/slides/slide/payment-" +"terms-1679>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:43 +msgid ":doc:`cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:48 +msgid "To create new payment terms, follow these steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:50 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Payment Terms` and " +"click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:52 +msgid "" +"Enter a name in the :guilabel:`Payment Terms` field. This field is the name " +"displayed both internally and on sales orders." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:54 +msgid "" +"Tick the :guilabel:`Early Discount` checkbox and fill out the discount " +"percentage, discount days, and :ref:`tax reduction <cash-discounts/tax-" +"reductions>` fields to add a :doc:`cash discount <cash_discounts>`, if " +"desired." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:57 +msgid "" +"In the :guilabel:`Due Terms` section, add a set of rules (terms) to define " +"what needs to be paid and by which due date(s). Defining terms automatically" +" calculates the payments' due date(s). This is particularly helpful for " +"managing **installment plans** (:dfn:`payment terms with multiple terms`)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:62 +msgid "" +"To add a term, click on :guilabel:`Add a line`, define the discount's value " +"and type in the :guilabel:`Due` fields, then fill out the :guilabel:`After` " +"fields to determine the due date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:64 +msgid "" +"Enter the text to be displayed on the document (sales order, invoice, etc.) " +"in the gray textbox in the :guilabel:`Preview` column." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:66 +msgid "" +"Tick the :guilabel:`Show installment dates` checkbox to display a breakdown " +"of each payment and its due date on the invoice report, if desired." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:70 +msgid "" +"To instead specify a number of days *before the end of the month*, use a " +"negative value in the :guilabel:`After` field." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:73 +msgid "" +"To test that your payment terms are configured correctly, enter an invoice " +"date on the :guilabel:`Example` line to generate the payments that would be " +"due and their due dates using these payment terms." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:78 +msgid "Terms are computed in the order of their due dates." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:81 +msgid "" +"In the following example, 30% is due on the day of issuance, and the " +"remaining 70% is due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:0 +msgid "" +"Example of Payment Terms. The first line is the 30% due immediately. The second line is\n" +"the remaining 70% due at the end of the following month." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:89 +msgid "Using payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:91 +msgid "" +"Payment terms can be defined using the :guilabel:`Payment Terms` field on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:93 +msgid "" +"**Contacts:** To automatically set default payment terms on a contact's new " +"sales orders, invoices, and bills. This can be modified in the contact form," +" under the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:96 +msgid "" +"**Quotations/Sales Orders:** To set specific payment terms automatically on " +"all invoices generated from a quotation or sales order." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:99 +msgid "" +"Payment terms can be defined using the :guilabel:`Due Date` field, with the " +":guilabel:`Terms` drop-down list on:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:102 +msgid "**Customer invoices:** To set specific payment terms on an invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:103 +msgid "**Vendor bills:** To set specific payment terms on a bill." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:106 +msgid "" +"Setting payment terms on a vendor bill is mostly useful for managing vendor " +"terms with multiple installments or cash discounts. Otherwise, manually " +"setting the **due date** is enough. If payment terms are already defined, " +"empty the field to select a date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:113 +msgid "" +"Invoices with specific payment terms generate different *journal entries*, " +"with one *journal item* for every computed *due date*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:116 +msgid "" +"This makes for easier :doc:`follow-ups " +"</applications/finance/accounting/payments/follow_up>` and " +":doc:`reconciliation </applications/finance/accounting/bank/reconciliation>`" +" since Odoo takes each due date into account, rather than just the balance " +"due date. It also helps to get an accurate :ref:`aged receivable report " +"<customer-invoices/aging-report>`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst-1 +msgid "" +"The amount debited to the account receivable is split into two journal items with\n" +"distinct due dates" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:126 +msgid "" +"In this example, an invoice of $1000 has been issued with the following " +"payment terms: *30% is due on the day of issuance, and the remaining 70% is " +"due at the end of the following month.*" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Account" +msgstr "บัญชี" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit" +msgstr "เดบิต" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:130 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit" +msgstr "เครดิต" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "Account Receivable" +msgstr "ลูกหนี้" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +msgid "February 21" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:132 +msgid "300" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +msgid "March 31" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:134 +msgid "700" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:136 +msgid "Product Sales" +msgstr "การขายสินค้า" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:136 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "1000" +msgstr "1000" + +#: ../../content/applications/finance/accounting/customer_invoices/payment_terms.rst:139 +msgid "" +"The $1000 debited to the account receivable is split into two distinct " +"journal items. Both of them have their own due date." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:5 +msgid "Snailmail" +msgstr "Snailmail" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:7 +msgid "" +"Sending direct mail can be an effective strategy for grabbing people's " +"attention, especially when their email inboxes are overflowing. With Odoo, " +"you have the ability to send invoices and follow-up reports through postal " +"mail worldwide, all from within your database." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:14 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" +" invoices` section to activate :guilabel:`Snailmail`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:17 +msgid "" +"To make it a by-default feature, select :guilabel:`Send by Post` in the " +":guilabel:`Default Sending Options` section." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst-1 +msgid "Under settings enable the snailmail feature in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:25 +msgid "Send invoices by post" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:27 +msgid "" +"Open your invoice, click on :guilabel:`Send & Print` and select " +":guilabel:`Send by Post`. Make sure your customer’s address is set " +"correctly, including the country, before sending the letter." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:31 +msgid "" +"Your document must respect the following rules to pass the validation before" +" being sent:" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:33 +msgid "" +"Margins must be **5 mm** on all sides. As Odoo forces the outer margins by " +"filling them with white before sending the snailmail, it can results in the " +"user's custom being cut off if it protrudes into the margins. To check the " +"margins, activate the :ref:`developer mode <developer-mode>`, go to " +":menuselection:`General Settings --> Technical --> Reporting section: Paper " +"Format`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:38 +msgid "" +"A square of **15mm by 15mm** on the bottom left corner has to stay clear." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:39 +msgid "" +"The postage area has to stay clear (click :download:`here " +"<snailmail/snailmail-template.pdf>` to get more info about the area)." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:41 +msgid "" +"Pingen (Odoo Snailmail service provider) scans the area to process the " +"address, so if something gets written outside the area, it is not counted as" +" part of the address." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:45 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:84 +msgid "Pricing" +msgstr "กำหนดราคา" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:47 +msgid "" +"Snailmail is an :doc:`/applications/general/in_app_purchase` service that " +"requires prepaid stamps (=credits) to work. Sending one document consumes " +"one stamp." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:50 +msgid "" +"To buy stamps, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Customer invoices: Snailmail`, click on :guilabel:`Buy " +"credits`, or go to :menuselection:`Settings --> In-App Purchases: Odoo IAP`," +" and click on :guilabel:`View my Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:94 +msgid "" +"If you are on Odoo Online and have the Enterprise version, you benefit from " +"free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:57 +msgid "" +"Click `here <https://iap.odoo.com/privacy#header_4>`_ to know about our " +"*Privacy Policy*." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:3 +msgid "Default terms and conditions (T&C)" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:5 +msgid "" +"Specifying terms and conditions is essential to establish important " +"contractual points, such as return and refunds, warranty, and after-sale " +"services." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:8 +msgid "" +"You can add default terms and conditions at the bottom of all customer " +"invoices, sales orders, and quotations, either as text or a link to a web " +"page." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:12 +msgid "" +"`Odoo Tutorial: Terms & Conditions <https://www.odoo.com/slides/slide/terms-" +"conditions-1680>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:17 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Customer Invoices`, enable :guilabel:`Default Terms & " +"Conditions`. By default, the :guilabel:`Add a Note` option is selected, and " +"the terms and conditions are displayed at the bottom of the document. Enter " +"the terms and conditions in the text box below." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst-1 +msgid "Example of terms and conditions as a note" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:26 +msgid "" +"You can also add a PDF version of your terms and conditions as an attachment" +" when sending the document via email. Edit the email templates if you want " +"to include them by default." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:29 +msgid "" +"Alternatively, to display the terms and conditions on a web page, select the" +" :guilabel:`Add a link to a Web Page` option and click :guilabel:`Save`. " +"Click :guilabel:`Update Terms`, edit the content, and click " +":guilabel:`Save`. The link to that page is then added as a note in your " +"document." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:34 +msgid "" +"You can edit the layout and content of the page using the :doc:`Website " +"</applications/websites/website>` app. If the Website app is activated, the " +":guilabel:`Edit in Website Builder` option then replaces :guilabel:`Update " +"Terms`." +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst-1 +msgid "Example of terms and conditions as a web page" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:5 +msgid "Get started" +msgstr "เริ่มเลย" + +#: ../../content/applications/finance/accounting/get_started.rst:7 +msgid "" +"When you first open your Odoo Accounting app, the *Accounting Overview* page" +" welcomes you with a step-by-step onboarding banner, a wizard that helps you" +" get started. This onboarding banner is displayed until you choose to close " +"it." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:11 +msgid "" +"The settings visible in the onboarding banner can still be modified later by" +" going to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:15 +msgid "" +"Odoo Accounting automatically installs the appropriate **Fiscal Localization" +" Package** for your company, according to the country selected at the " +"creation of the database. This way, the right accounts, reports, and taxes " +"are ready-to-go. :ref:`Click here <fiscal_localizations/packages>` for more " +"information about Fiscal Localization Packages." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:21 +msgid "Accounting onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:23 +msgid "" +"The step-by-step Accounting onboarding banner is composed of four steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:28 +msgid ":ref:`accounting-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:29 +msgid ":ref:`accounting-setup-bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:30 +msgid ":ref:`accounting-setup-periods`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:31 +msgid ":ref:`accounting-setup-chart`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:36 +#: ../../content/applications/finance/accounting/get_started.rst:137 +msgid "Company Data" +msgstr "ข้อมูลบริษัท" + +#: ../../content/applications/finance/accounting/get_started.rst:38 +msgid "" +"This menu allows you to add your company’s details such as the name, " +"address, logo, website, phone number, email address, and Tax ID, or VAT " +"number. These details are then displayed on your documents, such as on " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Add your company's details in Odoo Accounting and Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:46 +msgid "" +"You can also change these settings by going to :menuselection:`Settings --> " +"General Settings --> Settings --> Companies` and clicking on **Update " +"Info**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:52 +msgid "Bank Account" +msgstr "บัญชีธนาคาร" + +#: ../../content/applications/finance/accounting/get_started.rst:54 +msgid "" +"Connect your bank account to your database and have your bank statements " +"synced automatically. To do so, find your bank in the list, click on " +"*Connect*, and follow the instructions on-screen." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:58 +msgid "" +":doc:`Click here <bank/bank_synchronization>` for more information about " +"this feature." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:60 +msgid "" +"If your Bank Institution can’t be synchronized automatically, or if you " +"prefer not to sync it with your database, you may also configure your bank " +"account manually by clicking on *Create it*, and filling out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:64 +msgid "**Name**: the bank account's name, as displayed on Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:65 +msgid "**Account Number**: your bank account number (IBAN in Europe)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:66 +msgid "" +"**Bank**: click on *Create and Edit* to configure the bank's details. Add " +"the bank institution's name and its Identifier Code (BIC or SWIFT)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:68 +msgid "" +"**Code**: this code is your Journal's *Short Code*, as displayed on Odoo. By" +" default, Odoo creates a new Journal with this Short Code." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:70 +msgid "" +"**Journal**: This field is displayed if you have an existing Bank Journal " +"that is not linked yet to a bank account. If so, then select the *Journal* " +"you want to use to record the financial transactions linked to this bank " +"account or create a new one by clicking on *Create and Edit*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:75 +msgid "" +"You can add as many bank accounts as needed with this tool by going to " +":menuselection:`Accounting --> Configuration`, and clicking on *Add a Bank " +"Account*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:77 +msgid ":doc:`Click here <bank>` for more information about Bank Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:83 +msgid "Accounting Periods" +msgstr "รอบระยะเวลาบัญชี" + +#: ../../content/applications/finance/accounting/get_started.rst:85 +msgid "" +"Define here your **Fiscal Years**’ opening and closing dates, which are used" +" to generate reports automatically, and your **Tax Return Periodicity**, " +"along with a reminder to never miss a tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:89 +msgid "" +"By default, the opening date is set on the 1st of January and the closing " +"date on the 31st of December, as this is the most common use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:93 +msgid "" +"You can also change these settings by going to :menuselection:`Accounting " +"--> Configuration --> Settings --> Fiscal Periods` and updating the values." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:99 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:45 +msgid "Chart of Accounts" +msgstr "ผังบัญชี" + +#: ../../content/applications/finance/accounting/get_started.rst:101 +msgid "" +"With this menu, you can add accounts to your **Chart of Accounts** and " +"indicate their initial opening balances." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:104 +msgid "" +"Basic settings are displayed on this page to help you review your Chart of " +"Accounts. To access all the settings of an account, click on the *double " +"arrow button* at the end of the line." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "" +"Setup of the Chart of Accounts and their opening balances in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:111 +msgid "" +":doc:`Click here <get_started/chart_of_accounts>` for more information on " +"how to configure your Chart of Accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:115 +msgid "Invoicing onboarding banner" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:117 +msgid "" +"There is another step-by-step onboarding banner that helps you take " +"advantage of your Odoo Invoicing and Accounting apps. The *Invoicing " +"onboarding banner* is the one that welcomes you if you use the Invoicing app" +" rather than the Accounting app." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:121 +msgid "" +"If you have Odoo Accounting installed on your database, you can reach it by " +"going to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:124 +msgid "The Invoicing onboarding banner is composed of four main steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Step-by-step onboarding banner in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:129 +msgid ":ref:`invoicing-setup-company`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:130 +msgid ":ref:`invoicing-setup-layout`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:131 +msgid ":ref:`invoicing-setup-payment`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:132 +msgid ":ref:`invoicing-setup-sample`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:139 +msgid "" +"This form is the same as :ref:`the one presented in the Accounting " +"onboarding banner <accounting-setup-company>`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:145 +msgid "Invoice Layout" +msgstr "โครงร่างใบแจ้งหนี้" + +#: ../../content/applications/finance/accounting/get_started.rst:147 +msgid "" +"With this tool, you can design the appearance of your documents by selecting" +" which layout template, paper format, colors, font, and logo you want to " +"use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:150 +msgid "" +"You can also add your *Company Tagline* and the content of the documents’ " +"*footer*. Note that Odoo automatically adds the company's phone number, " +"email, website URL, and Tax ID (or VAT number) to the footer, according to " +"the values you previously configured in the :ref:`Company Data <accounting-" +"setup-company>`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst-1 +msgid "Document layout configuration in Odoo Invoicing" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:159 +msgid "" +"Add your **bank account number** and a link to your **General Terms & " +"Condition** in the footer. This way, your contacts can find the full content" +" of your GT&C online without having to print them on the invoices you issue." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:164 +msgid "" +"These settings can also be modified by going to :menuselection:`Settings -->" +" General Settings`, under the *Business Documents* section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:170 +msgid "Payment Method" +msgstr "วิธีการชำระเงิน" + +#: ../../content/applications/finance/accounting/get_started.rst:172 +msgid "" +"This menu helps you configure the payment methods with which your customers " +"can pay you." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:175 +msgid "" +"Configuring a *Payment Provider* with this tool also activates the *Invoice " +"Online Payment* option automatically. With this, users can directly pay " +"online, from their Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:181 +msgid "Sample Invoice" +msgstr "ตัวอย่างใบแจ้งหนี้" + +#: ../../content/applications/finance/accounting/get_started.rst:183 +msgid "" +"Send yourself a sample invoice by email to make sure everything is correctly" +" configured." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:186 +msgid ":doc:`bank`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:187 +msgid ":doc:`get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:189 +msgid ":doc:`../fiscal_localizations`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started.rst:190 +msgid "" +"`Odoo Tutorials: Accounting and Invoicing - Getting started [video] " +"<https://www.odoo.com/slides/slide/getting-started-1692>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:3 +msgid "Average price on returned goods" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:8 +msgid "" +"*Average cost valuation* (AVCO) is an inventory valuation method that " +"evaluates cost based on the total cost of goods bought or produced during a " +"period, divided by the total number of items on-hand. Inventory valuation is" +" used to:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:12 +msgid "reflect the value of a company's assets;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:13 +msgid "keep track of the amount of unsold goods;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:14 +msgid "account for monetary value in goods that have yet to generate profit;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:15 +msgid "report on flow of goods throughout the quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:17 +msgid "" +"Because |AVCO| uses the weighted average to evaluate the cost, it is a good " +"fit for companies that sell only a few different products in large " +"quantities. In Odoo, this costing analysis is *automatically updated* each " +"time products are received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:21 +msgid "" +"Thus, when shipments are returned to their supplier, Odoo automatically " +"generates accounting entries to reflect the change in inventory valuation. " +"However, Odoo does **not** automatically update the |AVCO| calculation, " +"because :ref:`this can potentially create inconsistencies with inventory " +"valuation <inventory/avg_price/leaving_inventory>`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:27 +msgid "" +"This document addresses a specific use case for theoretical purposes. " +"Navigate :ref:`here <inventory/management/inventory_valuation_config>` for " +"instructions on how to set up and use |AVCO| in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:32 +msgid "" +":ref:`Using inventory valuation <inventory/reporting/using_inventory_val>`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:33 +msgid "" +":ref:`Other inventory valuation methods " +"<inventory/inventory_valuation_config/costing_methods>`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:38 +msgid "" +"To use average cost inventory valuation on a product, navigate to " +":menuselection:`Inventory --> Configuration --> Product Categories` and " +"select the category that will be using |AVCO|. On the product category page," +" set :guilabel:`Costing Method` to `Average Cost (AVCO)` and " +":guilabel:`Inventory Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:44 +msgid "" +":ref:`Inventory valuation configuration " +"<inventory/management/inventory_valuation_config>`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:47 +msgid "Using average cost valuation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:49 +msgid "" +"The average cost method adjusts the inventory valuation when products are " +"received in the warehouse. This section explains how it works, but if the " +"explanation is unnecessary, skip to the :ref:`return to supplier use case " +"<inventory/avg_cost/return>` section." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:56 +msgid "Formula" +msgstr "สูตร" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:58 +msgid "" +"When new products arrive, the new average cost for each product is " +"recomputed using the formula:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:60 +msgid "" +"Avg~Cost = \\frac{(Old~Qty \\times Old~Avg~Cost) + (Incoming~Qty \\times Purchase~Price)}{Final~Qty}\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:63 +msgid "**Old Qty**: product count in stock before receiving the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:64 +msgid "" +"**Old Avg Cost**: calculated average cost for a single product from the " +"previous inventory valuation;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:66 +msgid "**Incoming Qty**: count of products arriving in the new shipment;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:67 +msgid "" +"**Purchase Price**: estimated price of products at the reception of products" +" (since vendor bills may arrive later). The amount includes not only the " +"price for the products, but also added costs, such as shipping, taxes, and " +":ref:`landed costs <inventory/reporting/landed_costs>`. At reception of the " +"vendor bill, this price is adjusted;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:71 +msgid "**Final Qty**: quantity of on-hand stock after the stock move." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:76 +msgid "" +"When products leave the warehouse, the average cost **does not** change. " +"Read about why the average cost valuation is **not** adjusted :ref:`here " +"<inventory/avg_price/leaving_inventory>`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:82 +msgid "Compute average cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:84 +msgid "" +"To understand how the average cost of a product changes with each shipment, " +"consider the following table of warehouse operations and stock moves. Each " +"is a different example of how the average cost valuation is affected." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Operation" +msgstr "ปฏิบัติการ" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +msgid "Incoming Value" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Inventory Value" +msgstr "มูลค่าสินค้าคงคลัง" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Qty On Hand" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:89 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "0" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "Receive 8 tables at $10/unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +msgid "8 * $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "$80" +msgstr "$80" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "8" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:93 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "$10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "Receive 4 tables at $16/unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +msgid "4 * $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +msgid "$144" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "12" +msgstr "12" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:95 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "Deliver 10 tables" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +msgid "-10 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "$24" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:103 +msgid "" +"Ensure comprehension of the above computations by reviewing the \"Receive 8 " +"tables at $10/unit\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:106 +msgid "Initially, the product stock is 0, so all values are $0." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:108 +msgid "" +"In the first warehouse operation, `8` tables are received at `$10` each. The" +" average cost is calculated using the :ref:`formula " +"<inventory/avg_cost/formula>`:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:111 +msgid "" +"Avg~Cost = \\frac{0 + 8 \\times $10}{8} = \\frac{$80}{8} = $10\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:114 +msgid "" +"Since the *incoming quantity* of tables is `8` and the *purchase price* for " +"each is `$10`," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:115 +msgid "The inventory value in the numerator is evaluated to `$80`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:116 +msgid "`$80` is divided by the total amount of tables to store, `8`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:117 +msgid "`$10` is the average cost of a single table from the first shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:119 +msgid "" +"To verify this in Odoo, in the *Purchase* app, order `8` quantities of a new" +" product, `Table`, with no previous stock moves, for `$10` each." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:122 +msgid "" +"In the table's :guilabel:`Product Category` field in the :guilabel:`General " +"Information` tab of the product form, click the :guilabel:`➡️ (arrow)` icon," +" to open an :guilabel:`External Link` to edit the product category. Set the " +":guilabel:`Costing Method` to `Average Cost (AVCO)` and :guilabel:`Inventory" +" Valuation` to `Automated`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:127 +msgid "" +"Then, return to the purchase order. Click :guilabel:`Confirm Order`, and " +"click :guilabel:`Receive Products` to confirm receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:130 +msgid "" +"Next, check the inventory valuation record generated by the product " +"reception by navigating to :menuselection:`Inventory --> Reporting --> " +"Inventory Valuation`. Select the drop-down for `Table`, and view the " +":guilabel:`Total Value` column for the *valuation layer* (:dfn:`inventory " +"valuation at a specific point in time = on-hand quantity * unit price`). The" +" 8 tables in-stock are worth $80." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show inventory valuation of 8 tables in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:141 +msgid "" +"When the product category's :guilabel:`Costing Method` is set to " +":guilabel:`AVCO`, then the average cost of a product is also displayed on " +"the :guilabel:`Cost` field, under the :guilabel:`General Information` tab, " +"on the product page itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:146 +msgid "Product delivery (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:148 +msgid "" +"For outgoing shipments, :ref:`outbound products have no effect on the " +"average cost valuation <inventory/avg_cost/definite_rule>`. Although the " +"average cost valuation is not recalculated, the inventory value still " +"decreases because the product is removed from stock and delivered to the " +"customer location." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:154 +msgid "" +"To demonstrate that the average cost valuation is not recalculated, examine " +"the \"Deliver 10 tables\" example." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:157 +msgid "" +"Avg~Cost = \\frac{12 \\times $12 + (-10) \\times $12}{12-10} = \\frac{24}{2} = $12\n" +"\n" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:160 +msgid "" +"Because 10 tables are being sent out to customers, the *incoming quantity* " +"is `-10`. The previous average cost (`$12`) is used in lieu of a vendor's " +"*purchase price*;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:162 +msgid "The *incoming inventory value* is `-10 * $12 = -$120`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:163 +msgid "" +"The old *inventory value* (`$144`) is added to the *incoming inventory " +"value* (`-$120`), so `$144 + -$120 = $24`;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:165 +msgid "" +"Only `2` tables remain after shipping out `10` tables from `12`. So the " +"current *inventory value* (`$24`) is divided by the on-hand quantity (`2`);" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:167 +msgid "" +"`$24 / 2 = $12`, which is the same average cost as the previous operation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:169 +msgid "" +"To verify this in Odoo, sell `10` tables in the *Sales* app, validate the " +"delivery, and then review the inventory valuation record by going to in " +":menuselection:`Inventory --> Reporting --> Inventory Valuation`. In the " +"topmost valuation layer, delivering `10` tables reduces the product's value " +"by `-$120`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:174 +msgid "" +"**Note**: What is not represented in this stock valuation record is the " +"revenue made from this sale, so this decrease is not a loss to the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Show how deliveries decrease inventory valuation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:184 +msgid "Return items to supplier (use case)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:186 +msgid "" +"Because the price paid to suppliers can differ from the price the product is" +" valued at with the |AVCO| method, Odoo handles returned items in a specific" +" way." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:189 +msgid "" +"Products are returned to suppliers at the original purchase price, but;" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:190 +msgid "The internal cost valuation remains unchanged." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:192 +msgid "" +"The above :ref:`example table <inventory/avg_cost/math_table>` is updated as" +" follows:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:195 +msgid "Qty*Avg Cost" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "Return 1 table bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +msgid "-1 * $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:202 +msgid "" +"In other words, returns to vendors are perceived by Odoo as another form of " +"a product exiting the warehouse. To Odoo, because the table is valued at $12" +" per unit, the inventory value is reduced by `$12` when the product is " +"returned; the initial purchase price of `$10` is unrelated to the table's " +"average cost." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:208 +msgid "" +"To return a single table that was purchased for `$10`, navigate to the " +"receipt in the *Inventory* app for the :ref:`8 tables purchased in Exercise " +"1 <inventory/avg_cost/ex-1>` by going to the :guilabel:`Inventory Overview`," +" clicking on :guilabel:`Receipts`, and selecting the desired receipt." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:213 +msgid "" +"Then, click :guilabel:`Return` on the validated delivery order, and modify " +"the quantity to `1` in the reverse transfer window. This creates an outgoing" +" shipment for the table. Select :guilabel:`Validate` to confirm the outgoing" +" shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:217 +msgid "" +"Return to :menuselection:`Inventory --> Reporting --> Inventory Valuation` " +"to see how the outgoing shipment decreases the inventory value by $12." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:0 +msgid "Inventory valuation for return." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:227 +msgid "Eliminate stock valuation errors in outgoing products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:229 +msgid "" +"Inconsistencies can occur in a company's inventory when the average cost " +"valuation is recalculated on outgoing shipments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:232 +msgid "" +"To demonstrate this error, the table below displays a scenario in which 1 " +"table is shipped to a customer and another is returned to a supplier at the " +"purchased price." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:236 +msgid "Qty*Price" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "Ship 1 product to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +msgid "-1 \\* $12" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "Return 1 product initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "-1 \\* $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$2**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 +msgid "**0**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:245 +msgid "" +"In the final operation above, the final inventory valuation for the table is" +" `$2` even though there are `0` tables left in stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:248 +msgid "Correct method" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:250 +msgid "" +"Use the average cost to value the return. This does not mean the company " +"gets $12 back for a $10 purchase; the item returned for $10 is valued " +"internally at $12. The inventory value change represents a product worth $12" +" no longer being accounted for in company assets." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:255 +msgid "Anglo-Saxon accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:257 +msgid "" +"In addition to using |AVCO|, companies that use **Anglo-Saxon accounting** " +"also keep a holding account that tracks the amount to be paid to vendors. " +"Once a vendor delivers an order, **inventory value** increases based on the " +"vendor price of the products that have entered the stock. The holding " +"account (called **stock input**) is credited and only reconciled once the " +"vendor bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:263 +msgid "" +":ref:`Anglo-Saxon vs. Continental " +"<inventory/inventory_valuation_config/accounting>`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:265 +msgid "" +"The table below reflects journal entries and accounts. The *stock input* " +"account stores the money intended to pay vendors when the vendor bill has " +"not yet been received. To balance accounts when returning products that have" +" a price difference between the price the product is **valued at** and the " +"price it was bought for, a *price difference* account is created." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Stock Input" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:273 +msgid "Price Diff" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "Receive 8 tables at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:277 +msgid "($80)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 +msgid "Receive vendor bill $80" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "Receive 4 tables at $16" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 +msgid "($64)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 +msgid "Receive vendor bill $64" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 +msgid "Deliver 10 tables to customer" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "Return 1 table initially bought at $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$10**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 +msgid "**$12**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "Receive vendor refund $10" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +msgid "$2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:293 +msgid "Product reception" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:296 +msgid "Summary" +msgstr "สรุป" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:298 +msgid "" +"At product reception, Odoo ensures companies can pay for goods that were " +"purchased by preemptively moving an amount matching the price of received " +"goods into the :doc:`liability account " +"</applications/finance/accounting/get_started/cheat_sheet>`, **Stock " +"Input**. Then, once the bill has been received, the amount in the holding " +"account is transferred to *Accounts Payable*. Transfers into this account " +"means the bill has been paid. **Stock Input** is reconciled once the vendor " +"bill is received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:305 +msgid "" +"Inventory valuation is a method of calculating how much each in-stock " +"product is worth internally. Since there is a difference between the price " +"the product is **valuated at** and the price the product was actually " +"**purchased for**, the **Inventory Valuation** account is unrelated to the " +"crediting and debiting operations of the **Stock Input** account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:310 +msgid "To conceptualize all this, follow the breakdown below." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:313 +msgid "Accounts balanced at received products" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:315 +msgid "" +"In this example, a company starts with zero units of a product, `table`, in " +"stock. Then, 8 tables are received from the vendor:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:318 +msgid "" +"The **Stock Input** account stores `$80` of credit owed to the vendor. The " +"amount in this account is unrelated to the inventory value." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:320 +msgid "" +"`$80` worth of tables came **in** (**debit** the *Inventory Value* account " +"`$80`), and" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:321 +msgid "" +"`$80` must be paid **out** for received goods (**credit** the *Stock Input* " +"account `$80`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:324 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:367 +msgid "In Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:326 +msgid "" +"Odoo generates an accounting journal entry when shipments that use |AVCO| " +"costing method are received. Configure a :guilabel:`Price Difference " +"Account` by selecting the :guilabel:`➡️ (arrow)` icon next to the " +":guilabel:`Product Category` field on the product page." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:330 +msgid "" +"Under :guilabel:`Account Properties`, create a new :guilabel:`Price " +"Difference Account` by typing in the name of the account and clicking " +":guilabel:`Create and Edit`. Then set the account :guilabel:`Type` as " +"`Expenses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Create price difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:338 +msgid "" +"Then, receive the shipment in the *Purchase* app or *Inventory* app, and " +"navigate to the :menuselection:`Accounting app --> Accounting --> Journal " +"Entries`. In the list, find the :guilabel:`Reference` that matches the " +"warehouse reception operation for the relevant product." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show accounting entry of 8 tables from the list." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:346 +msgid "" +"Click on the line for 8 tables. This accounting journal entry shows that " +"when the 8 tables were received, the `Stock Valuation` account increased by " +"`$80`. Conversely, the **Stock Input** account (set as `Stock Interim " +"(Received)` account by default) is credited `$80`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Debit stock valuation and credit stock input 80 dollars." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:355 +msgid "Accounts balanced at received vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:357 +msgid "" +"In this example, a company starts with zero units of a product, table, in " +"stock. Then, 8 tables are received from the vendor. When the bill is " +"received from vendor for 8 tables:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:360 +msgid "" +"Use `$80` in the **Stock Input** account to pay the bill. This cancels out " +"and the account now holds `$0`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:362 +msgid "Debit **Stock Input** `$80` (to reconcile this account)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:363 +msgid "" +"Credit **Accounts payable** `$80`. This account stores the amount the " +"company owes others, so accountants use the amount to write checks to " +"vendors." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:369 +msgid "" +"Once the vendor requests payment, navigate to the :menuselection:`Purchase " +"app --> Orders --> Purchase` and select the :abbr:`PO (Purchase Order)` for " +"8 tables. Inside the :abbr:`PO (Purchase Order)`, select :guilabel:`Create " +"Bill`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:373 +msgid "" +"Switch to the :guilabel:`Journal Items` tab to view how `$80` is transferred" +" from the holding account, `Stock Interim (Received)` to `Accounts Payable`." +" :guilabel:`Confirm` the bill to record the payment to the vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show bill linked to the purchase order for 8 tables." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:382 +msgid "On product delivery" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:384 +msgid "" +"In the :ref:`above example table <inventory/avg_price/price-table>`, when 10" +" products are delivered to a customer, the **Stock Input** account is " +"untouched because there are no new products coming in. To put it simply:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:388 +msgid "" +"**Inventory valuation** is credited `$120`. Subtracting from inventory " +"valuation represents `$120` worth of products exiting the company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:390 +msgid "Debit **Accounts Receivable** to record revenue from the sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Show journal items linked to sale order." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:398 +msgid "" +"In the accounting journal entry invoicing a customer for 10 tables, the " +"accounts **Product Sales**, **Tax Received**, and **Accounts Receivable** " +"all pertain to the sale of the product. **Accounts Receivable** is the " +"account where the customer payment will be received." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:402 +msgid "" +"Anglo-Saxon accounting recognizes the cost of goods sold (COGS) once the " +"sale is made. So, up until the product is sold, scrapped, or returned, costs" +" of keeping the product in stock are not accounted for. The **Expense** " +"account is debited `$120` to log the costs of storing 10 tables during this " +"period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:408 +msgid "On product return" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:410 +msgid "" +"In the :ref:`above example table <inventory/avg_price/price-table>`, when " +"returning 1 product to a vendor purchased at `$10`, a company expects `$10` " +"in the **Accounts Payable** account from the vendor. However, **Stock " +"Input** account must be debited `$12` because the average cost is `$12` at " +"the time of the return. The missing `$2` is accounted for in the " +":guilabel:`Price Difference Account`, which is set up in the product's " +":guilabel:`Product Category`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:417 +msgid "" +"Behavior of *price difference accounts* varies from localization. In this " +"case, the account is intended to store differences between vendor price and " +"*automated* inventory valuation methods." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:420 +msgid "Summary:" +msgstr "สรุป" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:422 +msgid "" +"Debit **Stock Input** account `$10` to move the table from stock to stock " +"input. This move is to indicate that the table is to be processed for an " +"outgoing shipment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:424 +msgid "" +"Debit **Stock Input** an additional `$2` to account for the **Price " +"Difference**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:425 +msgid "" +"Credit **Stock Valuation** `$12` because the item is leaving the stock." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "2 dollar difference expensed in Price Difference account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:431 +msgid "Once the vendor's refund is received," +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:433 +msgid "" +"Credit **Stock Input** account `$10` to reconcile the price of the table." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:434 +msgid "" +"Debit **Accounts Payable** `$10` to have the accountants collect and " +"register the payment in their journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst-1 +msgid "Return to get 10 dollars back." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:3 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:79 +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:17 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:146 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:361 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:65 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:38 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:41 +msgid "Chart of accounts" +msgstr "ผังบัญชี" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:5 +msgid "" +"The **chart of accounts (COA)** is the list of all the accounts used to " +"record financial transactions in the general ledger of an organization. The " +"chart of accounts can be found under :menuselection:`Accounting --> " +"Configuration --> Chart of Accounts`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:9 +msgid "" +"When browsing your chart of accounts, you can sort the accounts by " +":guilabel:`Code`, :guilabel:`Account Name`, or :guilabel:`Type`, but other " +"options are available in the drop-down menu" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Drop-down toggle button" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Group the accounts by type in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:19 +msgid "Configuration of an account" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:21 +msgid "" +"The country you select during the creation of your database (or additional " +"company in your database) determines which :doc:`fiscal localization package" +" <../../fiscal_localizations>` is installed by default. This package " +"includes a standard chart of accounts already configured according to the " +"country's regulations. You can use it directly or set it according to your " +"company's needs." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:26 +msgid "" +"To create a new account, go to :menuselection:`Accounting --> Configuration " +"--> Chart of Accounts`, click :guilabel:`Create`, and fill in (at the " +"minimum) the required fields (:guilabel:`Code, Account Name, Type`)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:31 +msgid "" +"It is not possible to modify the **fiscal localization** of a company once a" +" journal entry has been posted." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:35 +msgid "Code and name" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:37 +msgid "" +"Each account is identified by its :guilabel:`Code` and :guilabel:`Name`, " +"which also indicate the account's purpose." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:45 +msgid "" +"Correctly configuring the **account type** is critical as it serves multiple" +" purposes:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:47 +msgid "Information on the account's purpose and behavior" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:48 +msgid "Generate country-specific legal and financial reports" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:49 +msgid "Set the rules to close a fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:50 +msgid "Generate opening entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:52 +msgid "" +"To configure an account type, open the :guilabel:`Type` field's drop-down " +"selector and select the corresponding type from the following list:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Report" +msgstr "รายงาน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Category" +msgstr "หมวดหมู่" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 +msgid "Account Types" +msgstr "ประเภทบัญชี" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/reporting.rst:36 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:23 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 +msgid "Balance Sheet" +msgstr "งบดุล" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:96 +msgid "Assets" +msgstr "สินทรัพย์" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:58 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:59 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:62 +msgid "Receivable" +msgstr "ลูกหนี้" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:60 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:71 +msgid "Bank and Cash" +msgstr "ธนาคารและเงินสด" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:62 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:77 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:83 +msgid "Current Assets" +msgstr "สินทรัพย์หมุนเวียน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:64 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:86 +msgid "Non-current Assets" +msgstr "สินทรัพย์ไม่หมุนเวียน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:66 +msgid "Prepayments" +msgstr "ชำระเงินล่วงหน้า" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:68 +msgid "Fixed Assets" +msgstr "สินทรัพย์ถาวร" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +msgid "Liabilities" +msgstr "หนี้สิน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:70 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:65 +msgid "Payable" +msgstr "เจ้าหนี้" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:72 +msgid "Credit Card" +msgstr "บัตรเครดิต" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:74 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:89 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:92 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:95 +msgid "Current Liabilities" +msgstr "หนี้สินหมุนเวียน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:76 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:98 +msgid "Non-current Liabilities" +msgstr "หนี้สินไม่หมุนเวียน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 +msgid "Equity" +msgstr "ส่วนของเจ้าของ" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:80 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:101 +msgid "Current Year Earnings" +msgstr "กำไรสะสม" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:24 +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:20 +msgid "Profit & Loss" +msgstr "กำไร & ขาดทุน" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 +msgid "Income" +msgstr "รายได้" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:84 +msgid "Other Income" +msgstr "รายได้อื่นๆ" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 +msgid "Expense" +msgstr "รายจ่าย" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:88 +msgid "Depreciation" +msgstr "ค่าเสื่อมสภาพ" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:90 +msgid "Cost of Revenue" +msgstr "ต้นทุนสินค้า" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +msgid "Other" +msgstr "อื่น ๆ" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 +msgid "Off-Balance Sheet" +msgstr "รายการนอกงบดุล" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:98 +msgid "" +"Some **account types** can **automate** the creation of :ref:`asset <assets-" +"automation>` entries. To **automate** entries, click :guilabel:`View` on an " +"account line and go to the :guilabel:`Automation` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:102 +msgid "You have three choices for the :guilabel:`Automation` tab:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:104 +msgid ":guilabel:`No`: this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:105 +msgid "" +":guilabel:`Create in draft`: whenever a transaction is posted on the " +"account, a draft entry is created but not validated. You must first fill out" +" the corresponding form." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:107 +msgid "" +":guilabel:`Create and validate`: you must also select a :guilabel:`Deferred " +"Expense Model`. Whenever a transaction is posted on the account, an entry is" +" created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:111 +#: ../../content/applications/finance/accounting/taxes.rst:14 +msgid "Default taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:113 +msgid "" +"In the :guilabel:`View` menu of an account, select a **default tax** to be " +"applied when this account is chosen for a product sale or purchase." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:117 +#: ../../content/applications/finance/documents.rst:52 +#: ../../content/applications/finance/sign.rst:236 +msgid "Tags" +msgstr "แท็ก" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:119 +msgid "" +"Some accounting reports require **tags** to be set on the relevant accounts." +" To add a tag, under :guilabel:`View`, click the :guilabel:`Tags` field and " +"select an existing tag or :guilabel:`Create` a new one." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:124 +msgid "Account groups" +msgstr "กลุ่ม" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:126 +msgid "" +"**Account groups** are useful to list multiple accounts as *sub-accounts* of" +" a bigger account and thus consolidate reports such as the **Trial " +"Balance**. By default, groups are handled automatically based on the code of" +" the group. For example, a new account `131200` is going to be part of the " +"group `131000`. You can attribute a specific group to an account in the " +":guilabel:`Group` field under :guilabel:`View`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:133 +msgid "Create account groups manually" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:136 +msgid "" +"Regular users should not need to create account groups manually. The " +"following section is only intended for rare and advanced use cases." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:139 +msgid "" +"To create a new account group, activate :ref:`developer mode <developer-" +"mode>` and head to :menuselection:`Accounting --> Configuration --> Account " +"Groups`. Here, create a new group and enter the :guilabel:`name, code " +"prefix, and company` to which that group account should be available. Note " +"that you must enter the same code prefix in both :guilabel:`From` and " +":guilabel:`to` fields." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account groups creation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:147 +msgid "" +"To display your **Trial Balance** report with your account groups, go to " +":menuselection:`Accounting --> Reporting --> Trial Balance`, then open the " +":guilabel:`Options` menu and select :guilabel:`Hierarchy and Subtotals`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Account Groups in the Trial Balance in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:155 +msgid "Allow reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:157 +msgid "" +"Some accounts, such as accounts made to record the transactions of a payment" +" method, can be used for the reconciliation of journal entries." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:160 +msgid "" +"For example, an invoice paid with a credit card can be marked as " +":guilabel:`paid` if reconciled with its payment. Therefore, the account used" +" to record credit card payments needs to be configured as **allowing " +"reconciliation**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:164 +msgid "" +"To do so, check the :guilabel:`Allow Reconciliation` box in the account's " +"settings, and :guilabel:`Save`; or enable the button from the chart of " +"accounts view." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst-1 +msgid "Allow reconciliation for accounts in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:171 +msgid "Deprecated" +msgstr "เลิกใช้งานแล้ว" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:173 +msgid "" +"It is not possible to delete an account once a transaction has been recorded" +" on it. You can make them unusable by using the **Deprecated** feature: " +"check the :guilabel:`Deprecated` box in the account's settings, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:178 +msgid ":doc:`cheat_sheet`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:179 +msgid ":doc:`../vendor_bills/assets`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:180 +msgid ":doc:`../vendor_bills/deferred_expenses`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:181 +msgid ":doc:`../customer_invoices/deferred_revenues`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:183 +msgid "" +"`Odoo Tutorials: Chart of accounts <https://www.odoo.com/slides/slide/chart-" +"of-accounts-1630>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:184 +msgid "" +"`Odoo Tutorials: Update your chart of accounts " +"<https://www.odoo.com/slides/slide/update-your-chart-of-accounts-1658>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:7 +msgid "Accounting cheat sheet" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:13 +msgid "" +"The **Balance Sheet** is a snapshot of the company's finances at a specific " +"date (as opposed to the Profit and Loss, which is an analysis over a " +"period)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:18 +msgid "" +"**Assets** represent the company's wealth and the goods it owns. Fixed " +"assets include buildings and offices, while current assets include bank " +"accounts and cash. The money owed by a client is an asset. An employee is " +"not an asset." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:24 +msgid "" +"**Liabilities** are obligations from past events that the company will have " +"to pay in the future (utility bills, debts, unpaid suppliers). Liabilities " +"could also be defined as a source of financing which is provided to the " +"company, also called *leverage*." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:30 +msgid "" +"**Equity** is the amount of the funds contributed by the owners of the " +"company (founders or shareholders) plus previously retained earnings (or " +"losses). Each year, net profits (or losses) may be reported as retained " +"earnings or distributed to the shareholders (as a dividend)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:34 +msgid "" +"What is owned (an asset) has been financed through debts to reimburse " +"(liabilities) or equity (profits, capital)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "A difference is made between **assets** and **expenses**:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:38 +msgid "" +"An **asset** is a resource with economic value that an individual, " +"corporation, or country owns or controls with the expectation that it will " +"provide a future benefit. Assets are reported on a company's balance sheet. " +"They are bought or created to increase a firm's value or benefit its " +"operations." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:42 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:48 +msgid "" +"The **profit and loss** (P&L) report shows the company's performance over a " +"specific period of time, usually a quarter or a fiscal year." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:53 +msgid "" +"The **revenue** refers to the money earned by the company by selling goods " +"and/or services." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:57 +msgid "" +"The **cost of goods sold** (COGS, or also known as \"Cost of Sale\") refers " +"to the sale of goods' costs (e.g., the cost of the materials and labor used " +"to create the goods)." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:62 +msgid "" +"The **Gross profit** equals the revenues from sales minus the cost of goods " +"sold." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:66 +msgid "" +"**Operating expenses** (OPEX) include administration, sales and R&D " +"salaries, rent and utilities, miscellaneous costs, insurances, and anything " +"beyond the costs of products sold or the cost of sale." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:76 +msgid "Assets = Liabilities + Equity" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:81 +msgid "" +"The **chart of accounts** lists all the company's accounts: both Balance " +"sheet accounts and P&L accounts. Every transaction is recorded by debiting " +"and crediting multiple accounts in a journal entry. In a way, a chart of " +"accounts is like a company's DNA!" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:85 +msgid "" +"Every account listed in the chart of accounts belongs to a specific " +"category. In Odoo, each account has a unique code and belongs to one of " +"these categories:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:92 +msgid "**Equity and subordinated debts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:89 +msgid "" +"**Equity** is the amount of money invested by a company's shareholders to " +"finance the company's activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:91 +msgid "" +"**Subordinated debts** are the amount of money lent by a third party to a " +"company to finance its activities. In the event of the dissolution of a " +"company, these third parties are reimbursed before the shareholders." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:94 +msgid "" +"**Fixed assets** are tangible (i.e., physical) items or properties that a " +"company purchases and uses to produce its goods and services. Fixed assets " +"are long-term assets. This means the assets have a useful life of more than " +"one year. They also include properties, plants, and equipments (also known " +"as \"PP&E\") and are recorded on the balance sheet with that classification." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "**Current assets and liabilities**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:99 +msgid "" +"The **current assets** account is a balance sheet line item listed under the" +" Assets section, which accounts for all company-owned assets that can be " +"converted to cash within one year. Current assets include cash, cash " +"equivalents, accounts receivable, stock inventory, marketable securities, " +"prepaid liabilities, and other liquid assets." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:103 +msgid "" +"**Current liabilities** are a company's short-term financial obligations due" +" within one year. An example of a current liability is money owed to " +"suppliers in the form of accounts payable." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "**Bank and cash accounts**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:106 +msgid "" +"A **bank account** is a financial account maintained by a bank or other " +"financial institution in which the financial transactions between the bank " +"and a customer are recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:108 +msgid "" +"A **cash account**, or cash book, may refer to a ledger in which all cash " +"transactions are recorded. The cash account includes both the cash receipts " +"and the cash payment journals." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:115 +msgid "**Expenses and income**" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:111 +msgid "" +"An **expense** is the costs of operations a company bears to generate " +"revenues. It is simply defined as the cost one is required to spend on " +"obtaining something. Common expenses include supplier payments, employee " +"wages, factory leases, and equipment depreciation." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:114 +msgid "" +"The term \"**income**\" generally refers to the amount of money, property, " +"and other transfers of value received over a set period of time in exchange " +"for services or products." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:118 +msgid "Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:122 +msgid "" +"\\*: Customer Refund and Customer Payment boxes cannot be simultaneously " +"selected as they are contradictory." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:126 +msgid "Balance = Debit - Credit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:137 +msgid "" +"Every financial document of the company (e.g., an invoice, a bank statement," +" a pay slip, a capital increase contract) is recorded as a journal entry, " +"impacting several accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:140 +msgid "" +"For a journal entry to be balanced, the sum of all its debits must be equal " +"to the sum of all its credits." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:145 +msgid "" +"examples of accounting entries for various transactions. (see entries.js)" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:150 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:234 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +msgid "Reconciliation" +msgstr "การกระทบยอด" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:152 +msgid "" +":doc:`Reconciliation <../../accounting/bank/reconciliation>` is the process " +"of linking journal items of a specific account and matching credits and " +"debits." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:155 +msgid "" +"Its primary purpose is to link payments to their related invoices to mark " +"them as paid. This is done by doing a reconciliation on the accounts " +"receivable account and/or the accounts payable account." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:158 +msgid "Reconciliation is performed automatically by the system when:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:160 +msgid "the payment is registered directly on the invoice" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:161 +msgid "" +"the links between the payments and the invoices are detected at the bank " +"matching process" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:0 +msgid "Customer Statement Example" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 +msgid "Invoice 1" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +msgid "Partial payment 1/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:174 +msgid "70" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +msgid "Invoice 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:176 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +msgid "65" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "Partial payment 2/2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:178 +msgid "30" +msgstr "30" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:180 +msgid "Payment 2" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 +msgid "Invoice 3" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:182 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 +msgid "50" +msgstr "50" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:186 +msgid "Total to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 +#: ../../content/applications/finance/accounting/reporting.rst:149 +msgid "Bank Reconciliation" +msgstr "การกระทบยอดธนาคาร" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:192 +msgid "" +"Bank reconciliation is the matching of bank statement lines (provided by " +"your bank) with transactions recorded internally (payments to suppliers or " +"from customers). For each line in a bank statement, it can be:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:196 +msgid "" +"**matched with a previously recorded payment**: a payment is registered when" +" a check is received from a customer, then matched when checking the bank " +"statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:198 +msgid "" +"**recorded as a new payment**: the payment's journal entry is created and " +"reconciled with the related invoice when processing the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:200 +msgid "" +"**recorded as another transaction**: bank transfer, direct charge, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:202 +msgid "" +"Odoo should automatically reconcile most transactions; only a few should " +"need manual review. When the bank reconciliation process is finished, the " +"balance on the bank account in Odoo should match the bank statement's " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:209 +msgid "Checks Handling" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:211 +msgid "" +"There are two approaches to managing checks and internal wire transfers:" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:213 +msgid "Two journal entries and a reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:214 +msgid "One journal entry and a bank reconciliation" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:218 +msgid "" +"The first journal entry is created by registering the payment on the " +"invoice. The second one is created when registering the bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 +msgid "Invoice ABC" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +msgid "Undeposited funds" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:236 +msgid "Check 0123" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:243 +msgid "" +"A journal entry is created by registering the payment on the invoice. When " +"reconciling the bank statement, the statement line is linked to the existing" +" journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:250 +msgid "Bank Statement" +msgstr "ใบแจ้งยอดจากธนาคาร" + +#: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 +msgid "Statement XYZ" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:3 +msgid "Multi-currency system" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:5 +msgid "" +"Odoo allows you to issue invoices, receive bills, and record transactions in" +" currencies other than the main currency configured for your company. You " +"can also set up bank accounts in other currencies and run reports on your " +"foreign currency activities." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:10 +msgid ":doc:`../bank/foreign_currency`" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:20 +msgid "Main currency" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:22 +msgid "" +"The **main currency** is defined by default according to the company's " +"country. You can change it by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies` and changing the currency in the " +":guilabel:`Main Currency` setting." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:29 +msgid "Enable foreign currencies" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:31 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Currencies`, and " +"enable the currencies you wish to use by toggling the :guilabel:`Active` " +"button." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Enable the currencies you wish to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:41 +msgid "Currency rates" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:44 +msgid "Manual update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:46 +msgid "" +"To manually create and set a currency rate, go to :menuselection:`Accounting" +" --> Configuration --> Currencies`, click on the currency you wish to change" +" the rate of, and under the :guilabel:`Rates` tab, click :guilabel:`Add a " +"line` to create a new rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Create or modify the currency rate." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:55 +msgid "Automatic update" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:57 +msgid "" +"When you activate a second currency for the first time, :guilabel:`Automatic" +" Currency Rates` appears under :menuselection:`Accounting Dashboard --> " +"Configuration --> Settings --> Currencies`. By default, you have to click on" +" the **Update now** button (:guilabel:`🗘`) to update the rates." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:61 +msgid "" +"Odoo can update the rates at regular intervals. To do so, change the " +":guilabel:`Interval` from :guilabel:`Manually` to :guilabel:`Daily`, " +":guilabel:`Weekly`, or :guilabel:`Monthly`. You can also select the web " +"service from which you want to retrieve the latest currency rates by " +"clicking on the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:69 +msgid "Exchange difference entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:71 +msgid "" +"Odoo automatically records exchange differences entries on dedicated " +"accounts, in a dedicated journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:74 +msgid "" +"You can define which journal and accounts to use to **post exchange " +"difference entries** by going to :menuselection:`Accounting --> " +"Configuration --> Settings --> Default Accounts` and editing the " +":guilabel:`Journal`, :guilabel:`Gain Account`, and :guilabel:`Loss Account`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:79 +msgid "" +"If you receive a payment for a customer invoice one month after it was " +"issued, the exchange rate has likely changed since. Therefore, this " +"fluctuation implies some profit or loss due to the exchange difference, " +"which Odoo automatically records in the default **Exchange Difference** " +"journal." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:89 +msgid "" +"Each account can have a set currency. By doing so, all moves relevant to the" +" account are forced to have that account's currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:92 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Charts of " +"Accounts` and select a currency in the field :guilabel:`Account Currency`. " +"If left empty, all active currencies are handled instead of just one." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:252 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:159 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:278 +#: ../../content/applications/finance/fiscal_localizations/france.rst:194 +#: ../../content/applications/finance/fiscal_localizations/india.rst:101 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:299 +msgid "Journals" +msgstr "สมุดรายวัน" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:101 +msgid "" +"If a currency is set on a **journal**, that journal only handles " +"transactions in that currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:103 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the journal you want to edit, and select a currency in the field " +":guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency for the journal to handle." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:113 +msgid "Multi-currency accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:118 +msgid "Invoices, bills, and other documents" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:120 +msgid "" +"For all documents, you can select the currency and journal to use for the " +"transaction on the document itself." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:130 +#: ../../content/applications/finance/accounting/payments/checks.rst:58 +msgid "Payment registration" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:132 +msgid "" +"To register a payment in a currency other than your company's main currency," +" click on the :guilabel:`Register Payment` payment button of your document " +"and, in the pop-up window, select a **currency** in the :guilabel:`Amount` " +"field." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Select the currency and journal to use before registering the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:143 +msgid "Bank transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:145 +msgid "" +"When creating or importing bank transactions, the amount is in the company's" +" main currency. To input a **foreign currency**, select a currency in the " +":guilabel:`Foreign Currency`. Once selected, enter the :guilabel:`Amount` in" +" your main currency for it to automatically get converted in the foreign " +"currency in the :guilabel:`Amount in Currency field`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "The extra fields related to foreign currencies." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:154 +msgid "" +"When reconciling, Odoo displays both the foreign currency amount and the " +"equivalent amount in your company's main currency." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:160 +msgid "Exchange rate journal entries" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst:162 +msgid "" +"To see **exchange difference journal entries**, go to " +":menuselection:`Accounting Dashboard --> Accounting --> Journals: " +"Miscellaneous`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/multi_currency.rst-1 +msgid "Exchange rate journal entry." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:3 +msgid "VAT units" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:6 +msgid "This is only applicable to multi-company environments." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:8 +msgid "" +"A **VAT unit** is a group of VAT-taxable enterprises that are legally " +"independent of each other but are closely linked financially, " +"organizationally, and economically and therefore considered the same VAT-" +"taxable enterprise. **VAT units** are not mandatory, but if created, " +"constituent companies of the unit must belong to the same **country**, use " +"the same **currency**, and one company must be designated as the " +"**representative** company of the **VAT unit**. **VAT units** receive a " +"specific **tax ID** intended only for **tax returns**. **Constituent** " +"companies keep their **tax ID** used for **commercial purposes**." +msgstr "" +"**หน่วย VAT** คือกลุ่มขององค์กรที่ต้องเสียภาษี VAT " +"ที่มีความเป็นอิสระทางกฎหมายจากกัน " +"แต่มีความเชื่อมโยงกันอย่างใกล้ชิดทางการเงิน องค์กร และทางเศรษฐกิจ " +"ดังนั้นจึงถือว่าเป็นองค์กรที่ต้องเสีย VAT เดียวกัน **หน่วยภาษีมูลค่าเพิ่ม** " +"ไม่ใช่ข้อบังคับ แต่หากสร้างขึ้น " +"บริษัทที่เป็นส่วนประกอบของหน่วยดังกล่าวจะต้องอยู่ใน **ประเทศ** เดียวกัน ใช้ " +"**สกุลเงิน** เดียวกัน และบริษัทหนึ่งแห่งจะต้องถูกกำหนดให้เป็น **ตัวแทน ** " +"บริษัทของ **หน่วยภาษีมูลค่าเพิ่ม** **หน่วย VAT** จะได้รับ " +"**หมายเลขประจำตัวผู้เสียภาษี** เฉพาะสำหรับ **การคืนภาษี** เท่านั้น " +"**บริษัทที่เป็นส่วนประกอบ** เก็บ **หมายเลขประจำตัวผู้เสียภาษี** ไว้เพื่อ " +"**วัตถุประสงค์ทางการค้า**" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:17 +msgid "" +"Enterprise **A** owes €300.000,00 of VAT taxes and enterprise **B** can " +"recover €280.000,00 of VAT taxes. They form up as a **VAT unit** so that the" +" two amounts balance out and must conjointly only pay €20.000,00 of VAT " +"taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:24 +msgid "" +"To configure a **VAT unit**, go to :menuselection:`Settings --> General " +"Settings`, scroll down to the :guilabel:`Companies` section, and click " +":guilabel:`Manage Companies`. Select the company to serve the " +"**representative** role, and in the :guilabel:`General Information` tab, " +"fill in the mandatory fields for the .XML export when exporting the **tax " +"report**: :guilabel:`Company Name`, :guilabel:`Address`, :guilabel:`VAT`, " +":guilabel:`Currency`, :guilabel:`Phone`, and :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "General information tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:35 +msgid "" +"Then, click on the :guilabel:`VAT Units` tab, :guilabel:`Add a line`, and " +"either select an existing **VAT unit**, or create a new one. Enter a " +"**name** for the unit, :guilabel:`Country` of the constituent companies and " +"tax report, the :guilabel:`Companies`, the :guilabel:`Main Company` that " +"serves the **representative** role, and the :guilabel:`Tax ID` of the **VAT " +"unit**." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT units tab" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:45 +msgid "Fiscal position" +msgstr "สถานะทางการเงิน" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:47 +msgid "" +"As transactions between constituents of the same **VAT unit** are not " +"subject to VAT, it is possible to create a :doc:`tax mapping (fiscal " +"position) <../taxes/fiscal_positions>` to avoid the application of VAT on " +"inter-constituent transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:51 +msgid "" +"Be sure a constituent company has been selected before, then go to " +":menuselection:`Accounting --> Configuration --> Fiscal Positions`, and " +":guilabel:`Create` a new **fiscal position**. Click the :guilabel:`Tax " +"Mapping` tab, select the :guilabel:`Tax on Product` usually applied for " +"**non-constituent** transactions, and in :guilabel:`Tax to Apply`, select " +"the 0% tax to apply for **constituent** transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:57 +msgid "" +"Do the same for the :guilabel:`Account Mapping` tab if required, and repeat " +"this process for **each** constituent company on your database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:61 +msgid "" +"Depending on your :doc:`localization package " +"</applications/finance/fiscal_localizations>`, taxes may vary from the " +"screenshot displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:0 +msgid "Tax mapping of fiscal position for VAT unit" +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:68 +msgid "" +"Then, assign the fiscal position by opening the **Contacts** app. Search for" +" a **constituent** company, and open the contact's **card**. Click the " +":guilabel:`Sales & Purchase` tab, and in the :guilabel:`Fiscal Position` " +"field, input the **fiscal position** created for the **VAT unit**. Repeat " +"the process for each **constituent** company card form, on each company " +"database." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:74 +msgid ":doc:`../taxes/fiscal_positions`." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst:79 +msgid "" +"The **representative** company can access the aggregated tax report of the " +"**VAT unit** by going to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, and selecting the **VAT unit** in :guilabel:`Tax Unit`. This report" +" contains the aggregated transactions of all **constituents** and the .XML " +"export contains the name and VAT number of the **main** company." +msgstr "" + +#: ../../content/applications/finance/accounting/get_started/vat_units.rst-1 +msgid "VAT unit tax report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:5 +msgid "Payments" +msgstr "การชำระเงิน" + +#: ../../content/applications/finance/accounting/payments.rst:7 +msgid "" +"In Odoo, payments can either be automatically linked to an invoice or bill " +"or be stand-alone records for use at a later date:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:10 +msgid "" +"If a payment is **linked to an invoice or bill**, it reduces/settles the " +"amount due of the invoice. You can have multiple payments related to the " +"same invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:13 +msgid "" +"If a payment is **not linked to an invoice or bill**, the customer has an " +"outstanding credit with your company, or your company has an outstanding " +"debit with a vendor. You can use those outstanding amounts to reduce/settle " +"unpaid invoices/bills." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:18 +msgid ":doc:`Internal transfers <payments/internal_transfers>`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:19 +msgid ":doc:`bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:20 +msgid "" +"`Odoo Tutorials: Bank Configuration <https://www.odoo.com/slides/slide/bank-" +"configuration-1880>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:24 +msgid "Registering payment from an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:26 +msgid "" +"When clicking :guilabel:`Register payment` in a customer invoice or vendor " +"bill, it generates a new journal entry and changes the amount due according " +"to the payment amount. The counterpart is reflected in an :ref:`outstanding " +"<bank/outstanding-accounts>` **receipts** or **payments** account. At this " +"point, the customer invoice or vendor bill is marked as :guilabel:`In " +"payment`. Then, when the outstanding account is reconciled with a bank " +"statement line, the invoice or vendor bill changes to the :guilabel:`Paid` " +"status." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:33 +msgid "" +"The information icon near the payment line displays more information about " +"the payment. You can access additional information, such as the related " +"journal, by clicking :guilabel:`View`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "See detailed information of a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:40 +msgid "" +"The customer invoice or vendor bill must be in the :guilabel:`Posted` status" +" to register the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:42 +msgid "" +"If you unreconcile a payment, it still appears in your books but is no " +"longer linked to the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:44 +msgid "" +"If you (un)reconcile a payment in a different currency, a journal entry is " +"automatically created to post the currency exchange gains/losses (reversal) " +"amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:46 +msgid "" +"If you (un)reconcile a payment and an invoice having cash basis taxes, a " +"journal entry is automatically created to post the cash basis tax (reversal)" +" amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:50 +msgid "" +"If your main bank account is set as an :ref:`outstanding account " +"<bank/outstanding-accounts>`, and the payment is registered in Odoo (not " +"through a related bank statement), invoices and bills are directly " +"registered as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:55 +msgid "Registering payments not tied to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:57 +msgid "" +"When a new payment is registered via :menuselection:`Customers / Vendors -->" +" Payments` menu, it is not directly linked to an invoice or bill. Instead, " +"the account receivable or the account payable is matched with the " +"**outstanding account** until it is manually matched with its related " +"invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:63 +msgid "Matching invoices and bills with payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:65 +msgid "" +"A blue banner appears when you validate a new invoice/bill and an " +"**outstanding payment** exists for this specific customer or vendor. It can " +"easily be matched from the invoice or bill by clicking :guilabel:`ADD` under" +" :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:72 +msgid "" +"The invoice or bill is now marked as :guilabel:`In payment` until it is " +"reconciled with its corresponding bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:78 +msgid "Batch payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:80 +msgid "" +"Batch payments allow you to group different payments to ease " +":doc:`reconciliation <bank/reconciliation>`. They are also useful when you " +"deposit :doc:`checks <payments/checks>` to the bank or for :doc:`SEPA " +"payments <payments/pay_sepa>`. To do so, go to :menuselection:`Accounting " +"--> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors " +"--> Batch Payments`. In the list view of payments, you can select and group " +"several payments in a batch by clicking :menuselection:`Action --> Create " +"Batch Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:88 +msgid ":doc:`payments/batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:89 +msgid ":doc:`payments/batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:94 +msgid "Payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:96 +msgid "" +"The :guilabel:`Payments matching` tool opens all unreconciled customer " +"invoices or vendor bills and allows you to process them individually, " +"matching all payments and invoices in one place. You can reach this tool " +"from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor" +" Bills`, click the drop-down menu button (:guilabel:`⋮`), and select " +":guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> " +"Accounting --> Reconciliation`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Payments matching menu in the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:106 +msgid "" +"During the :doc:`reconciliation <bank/reconciliation>`, if the sum of the " +"debits and credits does not match, there is a remaining balance. This either" +" needs to be reconciled at a later date or needs to be written off directly." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:111 +msgid "Batch payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:113 +msgid "" +"You can use the **batch reconciliation feature** to reconcile several " +"outstanding payments or invoices simultaneously for a specific customer or " +"vendor. Go to your **Accounting Dashboard** and open your **bank journal**. " +"In the **bank reconciliation** view, select a **transaction**, and click the" +" :guilabel:`Batch Payments` tab. From here, you can reconcile your " +":doc:`batch payments <payments/batch>` with your outstanding payments or " +"invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "The batch payment reconcile option." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:123 +msgid "Registering a partial payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:125 +msgid "" +"To register a **partial payment**, click :guilabel:`Register payment` from " +"the related invoice or bill, and enter the amount received or paid. Upon " +"entering the amount, a prompt appears to decide whether to :guilabel:`Keep " +"open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select " +":guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or " +"bill is now marked as :guilabel:`Partial`. Select :guilabel:`Mark as fully " +"paid` if you wish to settle the invoice or bill with a difference in the " +"amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst-1 +msgid "Partial payment of an invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:136 +msgid "Reconciling payments with bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:138 +msgid "" +"Once a payment has been registered, the status of the invoice or bill is " +":guilabel:`In payment`. The next step is :doc:`reconciling " +"<bank/reconciliation>` it with the related bank statement line to have the " +"transaction finalized and the invoice or bill marked as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:3 +msgid "Batch payments by bank deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:5 +msgid "" +"A **batch deposit** is a convenient way to group customer payments and " +"deposit them into your bank account. The feature lets you list multiple " +"payments and generate a detailed deposit slip with a batch reference. This " +"reference can be used when reconciling to match bank statement lines with " +"transactions in the batch deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:13 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Customer" +" Payments` and tick :guilabel:`Batch Payments` to activate the feature." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:17 +msgid "Deposit multiple payments in batch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:20 +msgid "Register payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:22 +msgid "" +"Before performing a batch deposit, it is necessary to register each " +"transaction's payment. To do so, open the corresponding customer invoice and" +" click :guilabel:`Register Payment`. In the pop-up window, select the " +":guilabel:`Journal` linked to your bank account and :guilabel:`Batch " +"Deposit` as the :guilabel:`Payment Method`, and click :guilabel:`Create " +"Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Registering a customer payment as part of a batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:31 +msgid "Add payments to a batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:33 +msgid "" +"To add payments to a batch deposit, go to :menuselection:`Accounting --> " +"Customers --> Batch Payments`, and click :guilabel:`New`. Next, select the " +":guilabel:`Bank` and choose :guilabel:`Batch Deposit` as the " +":guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Filling out a new inbound batch payment form" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:40 +msgid "" +"Click :guilabel:`Add a line`. In the pop-up window, tick all payments to " +"include in the batch deposit, then click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Selecting all payments to include in the batch deposit" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:46 +msgid "Once done, click :guilabel:`Validate` to finalize the batch deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:49 +msgid "" +"Click :guilabel:`Print` to download a PDF file to include with the deposit " +"slip." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:54 +msgid "" +"Once the bank transactions are on your database, you can reconcile bank " +"statement lines with the batch payment. To do so, go to the " +":guilabel:`Accounting Dashboard` and click :guilabel:`Reconcile Items` on " +"the related bank account. Go to the :guilabel:`Batch Payments` tab to select" +" a specific batch and click :guilabel:`Validate` to finalize the process." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst-1 +msgid "Reconciling the batch payment with all its transactions" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:63 +msgid "" +"If a specific payment could not be processed by the bank or is missing, " +"remove the related payment before reconciling." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch.rst:68 +msgid ":doc:`batch_sdd`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:3 +msgid "Batch payments: SEPA Direct Debit (SDD)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.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 " +"euros. With **SEPA Direct Debit** (SDD), your customers can sign a mandate " +"that authorizes you to collect future payments from their bank accounts. " +"This is particularly useful for recurring payments based on a subscription." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:10 +msgid "" +"You can record customer mandates in Odoo, and generate `.xml` files " +"containing pending payments made with an SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"SDD is supported by all SEPA countries, which includes the 27 member states " +"of the European Union as well as additional countries." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:0 +msgid "" +"`List of all SEPA countries " +"<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-" +"sepa-scheme-countries>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:22 +msgid "" +"Go to :menuselection:`Accounting app --> Configuration --> Settings`, " +"activate :guilabel:`SEPA Direct Debit (SDD)`, and click on :guilabel:`Save`." +" Enter your company's :guilabel:`Creditor Identifier`. This number is " +"provided by your bank institution, or the authority responsible for " +"delivering them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Add a SEPA Creditor Identifier to Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:32 +msgid "SEPA Direct Debit Mandates" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:35 +msgid "Create a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:37 +msgid "" +"The :abbr:`SDD (sepa direct debit)` Mandate is the document that your " +"customers sign to authorize you to collect money directly from their bank " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:40 +msgid "" +"To create a new mandate, go to :menuselection:`Accounting app --> Customers " +"--> Direct Debit Mandates`, on :guilabel:`Create`, and fill out the form. " +"Export the PDF file by clicking on :guilabel:`Print`. It is then up to your " +"customer to sign this document. Once done, upload the signed file and click " +"on :guilabel:`Validate` to start running the mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:46 +msgid "" +"Make sure that the **IBAN bank accounts details** are correctly recorded on " +"the debtor’s contact form, under the :guilabel:`Accounting` tab, and in your" +" own :doc:`Bank Account <../bank>` settings." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:50 +msgid "SEPA Direct Debit as a payment method" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:52 +msgid "" +"SDD can be used as a payment method both on your **eCommerce** or on the " +"**Customer Portal** by activating SDD as a **Payment Provider**. With this " +"method, your customers can create their mandates. To ensure the validity of " +"the information given by the customer, they will have to confirm each " +"mandate with one successful bank transfer of the expected amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:57 +msgid "" +"To do so, go to :menuselection:`Accounting app --> Configuration --> Payment" +" Providers`, click on :guilabel:`SEPA Direct Debit`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:61 +msgid "" +"Make sure to change the :guilabel:`State` field to :guilabel:`Enabled` and " +"set the provider as \"Published\" so that it is available for your " +"customers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:64 +msgid "" +"Customers using SDD as payment method get prompted to add their IBAN, email " +"address, and to sign their SEPA Direct Debit mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:68 +msgid "Add link to future **Payment Provider** documentation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:71 +msgid "Close or revoke a mandate" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:73 +msgid "" +"Direct debit mandates are closed automatically after their :guilabel:`End " +"Date`. If this field is left blank, the mandate keeps being **Active** until" +" it is **Closed** or **Revoked**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:76 +msgid "" +"Clicking on :guilabel:`Close` updates the mandate’s end day to the current " +"day. This means that invoices issued after the present day will not be " +"processed with an SDD payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:79 +msgid "" +"Clicking on :guilabel:`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 are still included in " +"the next SDD `.xml` file." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:84 +msgid "" +"Once a mandate has been :guilabel:`closed` or :guilabel:`revoked`, it cannot" +" be reactivated." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:87 +msgid "Get paid with SEPA Direct Debit batch payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:92 +msgid "" +"You can register SDD payments for invoices issued to customers who have an " +"active SDD mandate." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:94 +msgid "" +"To do so, open the invoice, click on :guilabel:`Register Payment`, and " +"choose :guilabel:`SEPA Direct Debit` as payment method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:98 +msgid "Generate SEPA Direct Debit `.XML` files to submit payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:100 +msgid "" +"`.xml` files with all SDD payment instructions can be uploaded to your " +"online banking interface to process all payments at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:104 +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 <https://www.europeanpaymentscouncil.eu/document-" +"library/implementation-guidelines/sepa-credit-transfer-customer-psp-" +"implementation>`_, which ensures compatibility with the banks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:109 +msgid "" +"To generate your `.xml` file of multiple pending SDD payments, you can " +"create a batch payment. To do so, go to :menuselection:`Accounting app --> " +"Customers --> Payments`, select the needed payments, then click on " +":guilabel:`Action`, and finally :guilabel:`Create a batch Payment`. Once you" +" click on :guilabel:`Validate`, the `.xml` file is directly available for " +"download." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst-1 +msgid "Generate an .XML file for your SDD payments in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:118 +msgid "" +"Finally, upload this file to your online banking interface to process the " +"payments." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:121 +msgid "" +"You can retrieve all the generated SDD `.xml` files by going to " +":menuselection:`Accounting app --> Customers --> Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:125 +msgid ":doc:`batch`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:127 +msgid "" +"`List of all SEPA countries " +"<https://www.europeanpaymentscouncil.eu/document-library/other/epc-list-" +"sepa-scheme-countries>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/batch_sdd.rst:129 +msgid "" +"`Sepa guidelines <https://www.europeanpaymentscouncil.eu/document-" +"library/implementation-guidelines/sepa-credit-transfer-inter-psp-" +"implementation-guidelines>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:3 +msgid "Checks" +msgstr "ตรวจสอบ" + +#: ../../content/applications/finance/accounting/payments/checks.rst:5 +msgid "" +"There are two ways to handle payments received by checks in Odoo, either by " +"using :ref:`outstanding accounts <checks/outstanding-account>` or by " +":ref:`bypassing the reconciliation process <checks/reconciliation-bypass>`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:9 +msgid "" +"**Using outstanding accounts is recommended**, as your bank account balance " +"stays accurate by taking into account checks yet to be cashed." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:13 +msgid "" +"Both methods produce the same data in your accounting at the end of the " +"process. But if you have checks that have not been cashed in, the " +"**Outstanding Account** method reports these checks in the **Outstanding " +"Receipts** account. However, funds appear in your bank account whether or " +"not they are reconciled, as the bank value is reflected at the moment of the" +" bank statement." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:20 +msgid ":ref:`Outstanding accounts <bank/outstanding-accounts>`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:21 +msgid ":ref:`Bank reconciliation <accounting/reconciliation>`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:26 +msgid "Method 1: Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:28 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` by check on the invoice. Then, when your bank " +"account is credited with the check's amount, you reconcile the payment and " +"statement to move the amount from the **Outstanding Receipt** account to the" +" **Bank** account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:33 +msgid "" +"You can create a new payment method named *Checks* if you would like to " +"identify such payments quickly. To do so, go to :menuselection:`Accounting " +"--> Configuration --> Journals --> Bank`, click the :guilabel:`Incoming " +"Payments` tab, and :guilabel:`Add a line`. As :guilabel:`Payment Method`, " +"select :guilabel:`Manual`, and enter `Checks` as name." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:41 +msgid "Method 2: Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:43 +msgid "" +"When you receive a check, you :doc:`record a payment " +"<../bank/reconciliation>` on the related invoice. The amount is then moved " +"from the **Account Receivable** to the **Bank** account, bypassing the " +"reconciliation and creating only **one journal entry**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:47 +msgid "" +"To do so, you *must* follow the following setup. Go to " +":menuselection:`Accounting --> Configuration --> Journals --> Bank`. Click " +"the :guilabel:`Incoming Payments` tab and then :guilabel:`Add a line`, " +"select :guilabel:`Manual` as :guilabel:`Payment Method`, and enter `Checks` " +"as :guilabel:`Name`. Click the toggle menu button, tick " +":guilabel:`Outstanding Receipts accounts`, and in the :guilabel:`Outstanding" +" Receipts accounts` column, and set the :guilabel:`Bank` account for the " +"**Checks** payment method." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Bypass the Outstanding Receipts account using the Bank account." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:61 +msgid "By default, there are two ways to register payments made by check:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:63 +msgid "**Manual**: for single checks;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:64 +msgid "**Batch**: for multiple checks at once." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:66 +msgid "" +"This documentation focuses on **single-check** payments. For **batch " +"deposits**, see :doc:`the batch payments documentation <batch>`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:69 +msgid "" +"Once you receive a customer check, go to the related invoice " +"(:menuselection:`Accounting --> Customer --> Invoices)`, and click " +":guilabel:`Register Payment`. Fill in the payment information:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:72 +msgid ":guilabel:`Journal: Bank`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:73 +msgid "" +":guilabel:`Payment method`: :guilabel:`Manual` (or **Checks** if you have " +"created a specific payment method);" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:75 +msgid ":guilabel:`Memo`: enter the check number;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:76 +msgid "Click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst-1 +msgid "Check payment info" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:81 +msgid "" +"The generated journal entries are different depending on the payment " +"registration method chosen." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:87 +msgid "Outstanding account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:89 +msgid "" +"The invoice is marked as :guilabel:`In Payment` as soon as you record the " +"payment. This operation produces the following **journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:93 +#: ../../content/applications/finance/accounting/payments/checks.rst:104 +#: ../../content/applications/finance/accounting/payments/checks.rst:123 +msgid "Statement Match" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:95 +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:108 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +#: ../../content/applications/finance/accounting/payments/checks.rst:127 +msgid "100.00" +msgstr "100.00" + +#: ../../content/applications/finance/accounting/payments/checks.rst:97 +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:76 +msgid "Outstanding Receipts" +msgstr "รายรับคงค้าง" + +#: ../../content/applications/finance/accounting/payments/checks.rst:100 +msgid "" +"Then, once you receive the bank statements, match this statement with the " +"check of the **Outstanding Receipts** account. This produces the following " +"**journal entry**:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:106 +#: ../../content/applications/finance/accounting/payments/checks.rst:125 +msgid "X" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:111 +msgid "" +"If you use this approach to manage received checks, you get the list of " +"checks that have not been cashed in the **Outstanding Receipt** account " +"(accessible, for example, from the general ledger)." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:115 +msgid "Reconciliation bypass" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:117 +msgid "" +"The invoice is marked as :guilabel:`Paid` as soon as you record the check." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/checks.rst:119 +msgid "" +"With this approach, you bypass the use of **outstanding accounts**, " +"effectively getting only one journal entry in your books and bypassing the " +"reconciliation:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:3 +msgid "Follow-up on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:5 +msgid "" +"A follow-up message can be sent to customers when a payment is overdue. Odoo" +" helps you identify late payments and allows you to schedule and send the " +"appropriate reminders using **follow-up actions** that automatically trigger" +" one or more actions according to the number of overdue days. You can send " +"your follow-ups via different means, such as email, post, or SMS." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:11 +msgid "" +"`Odoo Tutorials: Payment Follow-up " +"<https://www.odoo.com/slides/slide/payment-follow-up-1682>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:16 +msgid "" +"To configure a :guilabel:`Follow-Up Action`, go to " +":menuselection:`Accounting --> Configuration --> Follow-up Levels`, and " +"select or create (a) new follow-up level(s). Several follow-up actions are " +"available by default under the :guilabel:`Notification` tab, and the " +"**name** as well as the **number of days** can be changed. The follow-up " +":guilabel:`Actions` available are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:21 +msgid ":guilabel:`Send Email`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:22 +msgid ":ref:`Send a Letter <customer_invoices/snailmail>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:23 +msgid ":ref:`Send an SMS message <pricing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:25 +msgid "" +"You can use a pre-filled template for your messages by selecting a " +":guilabel:`Content Template`. To change the template used, hover over the " +"field and click the :guilabel:`-->`. If enabled, SMS messages have a " +"specific :guilabel:`Sms Template` field." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:29 +msgid "" +"It is possible to automatically send a reminder by enabling the " +":guilabel:`Automatic` option, and attaching the *open* invoice(s) by " +"enabling :guilabel:`Attach Invoices`, within a specific follow-up action." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:33 +msgid "" +"By clicking on the :guilabel:`Activity` tab, scheduling activities (tasks) " +"is possible. That way, an activity is automatically scheduled when the " +"follow-up is triggered. To do so, enable :guilabel:`Schedule Activity`, and " +"select a :guilabel:`Responsible` person for the task. Choose an " +":guilabel:`Activity Type`, and enter a :guilabel:`Summary` on how to handle " +"the activity, if desired." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:40 +msgid "" +"Set a negative number of days to send a reminder before the actual due date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:43 +msgid "Follow-up reports" +msgstr "รายงานการติดตามผล" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:45 +msgid "" +"Overdue invoices you need to follow up on are available in " +":menuselection:`Accounting --> Customers --> Follow-up Reports`. By default," +" Odoo filters by :guilabel:`Overdue Invoices`, but you can also filter by " +":guilabel:`In need of action` in the :guilabel:`Filters` menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:49 +msgid "" +"When selecting an invoice, you can see all of the customer's unpaid invoices" +" (overdue or not), with the due dates of late invoices appearing in red. You" +" can exclude invoices from a reminder by clicking :guilabel:`Exclude from " +"Follow-ups`. You can set either :guilabel:`Automatic` or :guilabel:`Manual` " +"reminders as well as a :guilabel:`Responsible` person for that customer." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:54 +msgid "" +"To send reminders, click on :guilabel:`Follow up`, and select the action(s) " +"you want to perform from:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:57 +msgid ":guilabel:`Print`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:58 +msgid ":guilabel:`Email`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:59 +msgid ":guilabel:`Sms`;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:60 +msgid ":guilabel:`By post`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:62 +msgid "" +"You can :guilabel:`Attach Invoices` and change the content templates from " +"this view. When done, click :guilabel:`Send` or :guilabel:`Send & Print`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:66 +msgid "" +"The contact information on the invoice or the contact form is used to send " +"the reminder." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:67 +msgid "" +"When the reminder is sent, it is documented in the chatter of the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:68 +msgid "" +"If it is not the right time for a reminder, you can specify the " +":guilabel:`Next Reminder` date. You will get the next report according to " +"the next reminder date set." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:72 +msgid "" +"Reconcile all bank statements right before launching the follow-up process " +"to avoid sending a reminder to a customer that has already paid." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:76 +msgid "Debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:78 +msgid "" +"To know whether a customer usually pays late or not, you can set a trust " +"level by marking them as :guilabel:`Good Debtor`, :guilabel:`Normal Debtor`," +" or :guilabel:`Bad Debtor` on their follow-up report. To do so, click on the" +" bullet next to the customer's name and select a trust level." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst-1 +msgid "Set debtor's trust level" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:86 +msgid "Send reminders in batches" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:88 +msgid "" +"You can send reminder emails in batches from the :guilabel:`Follow-up " +"Reports` page. To do so, select all the reports you would like to process, " +"click on the :guilabel:`Action` gear icon, and select :guilabel:`Process " +"follow-ups`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:93 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:94 +msgid ":doc:`../../../marketing/sms_marketing/pricing/pricing_and_faq`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/follow_up.rst:95 +msgid ":doc:`../customer_invoices/snailmail`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:3 +msgid "Forecast future bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:5 +msgid "" +"In Odoo, you can manage payments by setting automatic **Payments Terms** and" +" **follow-ups**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:8 +msgid "Configuration: payment terms" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:10 +msgid "" +"In order to track vendor conditions, we use **Payment Terms** in Odoo. They " +"allow keeping track of due dates on invoices. Examples of **Payment Terms** " +"are:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:13 +msgid "50% within 30 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:14 +msgid "50% within 45 days" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:16 +msgid "" +"To create them, go to :menuselection:`Accounting --> Configuration --> " +"Invoicing: Payment Terms` and click on :guilabel:`Create` to add new terms " +"or click existing ones to modify them." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:20 +msgid "" +"`Odoo Tutorials: Payment Terms <https://www.odoo.com/slides/slide/payment-" +"terms-1679?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:23 +msgid "" +"Once **Payment Terms** are defined, you can assign them to your vendor by " +"default. To do so, go to :menuselection:`Vendors --> Vendors`, select a " +"vendor, click the :guilabel:`Sales & Purchase` tab, and select a specific " +"**Payment Term**. This way, every time you purchase from this vendor, Odoo " +"automatically proposes the chosen Payment Term." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:29 +msgid "" +"If you do not set a specific Payment Term on a vendor, you can still set one" +" on the vendor bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:32 +msgid "Forecast bills to pay with the aged payable report" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:34 +msgid "" +"To track amounts to be paid to the vendors, use the **Aged Payable** report." +" To access it, go to :menuselection:`Accounting --> Reporting --> Partner " +"Reports: Aged Payable`. This report gives you a summary per vendor of the " +"amounts to pay, compared to their due date (the due date being computed on " +"each bill using the terms). This report tells you how much you will have to " +"pay within the following months." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:41 +msgid "Select bills to pay" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:43 +msgid "" +"You can get a list of all your vendor bills by going to " +":menuselection:`Vendors --> Bills`. To view only the bills that you need to " +"pay, click :menuselection:`Filters --> Bills to Pay`. To view only overdue " +"payments, select the :guilabel:`Overdue` filter instead." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/forecast.rst:47 +msgid "" +"You can also group bills by their due date by clicking :menuselection:`Group" +" By --> Due Date` and selecting a time period." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:3 +msgid "Internal transfers" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:5 +msgid "" +"Internal money transfers can be handled in Odoo. At least two bank accounts " +"are needed to make internal transfers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:9 +msgid ":doc:`How to add an additional bank account <../bank>`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:14 +msgid "" +"An internal transfer account is automatically created on your database based" +" on your company's localization and depending on your country’s legislation." +" To modify the default :guilabel:`Internal transfer account`, go to " +":menuselection:`Accounting --> Configuration --> Settings` and scroll down " +"to the :guilabel:`Default Accounts` section." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:20 +msgid "Register an internal transfer from one bank to another" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:22 +msgid "" +"If you want to transfer money from one bank to another, access the " +"Accounting Dashboard, click the drop-down selection button (:guilabel:`⋮`) " +"on the bank from which you want to make the transfer, then click " +":guilabel:`Payments`. Select or create a payment, tick the " +":guilabel:`Internal Transfer` checkbox, and select a :guilabel:`Destination " +"Journal` before you :guilabel:`Confirm` the internal transfer." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:28 +msgid "" +"The money is now booked in the transfer account and another payment is " +"automatically created in the destination journal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:33 +msgid "Bank journal (Bank A)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:42 +msgid "Outstanding Payments account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:44 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:60 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:45 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:62 +msgid "**Internal transfer account**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:46 +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:64 +msgid "**$1,000**" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:49 +msgid "Bank journal (Bank B)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:59 +msgid "Outstanding Receipts account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:66 +msgid "" +"There is **one outstanding payment** and **one outstanding receipt** pending" +" in your two bank account journals because the bank statement confirming the" +" sending and receiving of the money has not been booked yet." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 +msgid "" +"Once this is done, you can book and reconcile your bank statement lines as " +"usual." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/internal_transfers.rst:73 +msgid ":doc:`../bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:5 +msgid "Online payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:11 +msgid "" +"To make it more convenient for your customers to pay the invoices you issue," +" you can activate the **Invoice Online Payment** feature, which adds a *Pay " +"Now* button on their **Customer Portal**. This allows your customers to see " +"their invoices online and pay directly with their favorite payment method, " +"making the payment process much easier." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Payment provider choice after having clicked on \"Pay Now\"" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:23 +msgid "" +"Make sure your :ref:`Payment Providers are correctly configured " +"<payment_providers/configuration>`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:26 +msgid "" +"By default, \":doc:`Wire Transfer " +"</applications/finance/payment_providers/wire_transfer>`\" is the only " +"Payment Provider activated, but you still have to fill out the payment " +"details." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:29 +msgid "" +"To activate the Invoice Online Payment, go to :menuselection:`Accounting -->" +" Configuration --> Settings --> Customer Payments`, enable **Invoice Online " +"Payment**, and click on *Save*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:33 +msgid "Customer Portal" +msgstr "พอร์ทัลลูกค้า" + +#: ../../content/applications/finance/accounting/payments/online.rst:35 +msgid "" +"After issuing the invoice, click on *Send & Print* and send the invoice by " +"email to the customer. They will receive an email with a link that redirects" +" them to the invoice on their **Customer Portal**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "Email with a link to view the invoice online on the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:42 +msgid "" +"They can choose which Payment Provider to use by clicking on *Pay Now*." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst-1 +msgid "\"Pay now\" button on an invoice in the Customer Portal." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online.rst:49 +msgid ":doc:`/applications/finance/payment_providers`" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:3 +msgid "Install the patch to disable online invoice payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:5 +msgid "" +"Following recent changes in Odoo 16, you might be warned that disabling the " +":guilabel:`Invoice Online Payment` setting will uninstall modules. If you " +"want to disable the feature without uninstalling modules, follow the steps " +"below to install the module **Payment - Account / Invoice Online Payment " +"Patch**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:0 +msgid "" +"If your Odoo database is created after the module **Payment - Account / " +"Invoice Online Payment Patch** was released, you don't have anything to do." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:0 +msgid "" +"To check if the module is already installed, go to :guilabel:`Apps`, remove " +"the `Apps` filter, and search for `account_payment`. If the module **Payment" +" - Account / Invoice Online Payment Patch** is present and marked as " +"installed, your Odoo database is already up-to-date and you are able to " +"disable the feature without side-effect." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:19 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:21 +msgid "" +"The possibility to disable the :guilabel:`Invoice Online Payment` setting " +"without side-effect is made available through a new Odoo module; to be able " +"to install it, you must make sure that your Odoo source code is up-to-date." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:25 +msgid "" +"If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-" +"date and you can proceed to the next step." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:28 +msgid "" +"If you use Odoo with an on-premise setup or through a partner, you must " +"update your installation as detailed in :doc:`this documentation page " +"</administration/maintain/update>`, or by contacting your integrating " +"partner." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:33 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:35 +msgid "" +"New modules must be *discovered* by your Odoo instance to be available in " +"the **Apps** menu." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:37 +msgid "" +"To do so, activate the :ref:`developer mode <developer-mode>`, and go to " +":menuselection:`Apps --> Update Apps List`. A wizard will ask for " +"confirmation." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:41 +msgid "Install the module Invoice Online Payment Patch" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:44 +msgid "" +"You should never install new modules in your production database without " +"first testing them in a duplicate or staging environment. For Odoo.com " +"customers, a duplicate database can be created from the database management " +"page. For Odoo.sh users, you should use a staging or duplicate database. For" +" on-premise users, you should use a staging environment---contact your " +"integrating partner for more information regarding how to test a new module " +"in your particular setup." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:50 +msgid "" +"The module should now be available in your :guilabel:`Apps` menu. Remove the" +" ``Apps`` filter and search for ``account_payment``; the module " +":guilabel:`Payment - Account / Invoice Online Payment Patch` should be " +"available for installation. If you cannot find the module after having " +"updated the list of available modules, it means your Odoo source code is not" +" up-to-date; refer to step one of this page." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:56 +msgid "" +"Once the module is installed, disabling the feature will work as intended " +"and will not ask you to uninstall installed applications or modules." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:3 +msgid "Pay by checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:5 +msgid "" +"Once you decide to pay a supplier bill, you can select to pay by check. You " +"can then print all the payments registered by check. Finally, the bank " +"reconciliation process will match the checks you sent to suppliers with " +"actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:13 +msgid "Activate checks payment methods" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:15 +msgid "" +"To activate the checks payment method, go to :menuselection:`Accounting --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Vendor " +"Payments` section. There, you can activate the payment method as well as set" +" up the :guilabel:`Check Layout`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:20 +msgid "" +"Once the :guilabel:`Checks` setting is activated, the **Checks** payment " +"method is automatically set up in the :guilabel:`Outgoing Payments` tabs of " +"**bank** journals." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:22 +msgid "" +"Some countries require specific modules to print checks; such modules may be" +" installed by default. For instance, the :guilabel:`U.S. Checks Layout` " +"module is required to print U.S. checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:27 +msgid "Compatible check stationery for printing checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:30 +msgid "United States" +msgstr "สหรัฐอเมริกา" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:32 +msgid "For the United States, Odoo supports by default the check formats of:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 +msgid "" +"**Quickbooks & Quicken**: check on top, stubs in the middle and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 +msgid "**Peachtree**: check in the middle, stubs on top and bottom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:36 +msgid "**ADP**: check in the bottom, and stubs on the top." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:39 +msgid "Pay a supplier bill with a check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:41 +msgid "Paying a supplier with a check is done in three steps:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 +msgid "registering a payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 +msgid "printing checks in batch for all registered payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:45 +msgid "reconciling bank statements" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:48 +msgid "Register a payment by check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:50 +msgid "" +"To register a payment, open any supplier bill from the menu " +":menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is " +"validated, you can register a payment. Set the :guilabel:`Payment Method` to" +" :guilabel:`Checks` and validate the payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:56 +msgid "Print checks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:58 +msgid "" +"On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, " +"you can see the number of checks registered. By clicking on " +":guilabel:`Checks to print` you have got the possibility to print the " +"reconciled checks." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:62 +msgid "" +"To print all checks in batch, select all payments from the list view and " +"click on :guilabel:`Print`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:3 +msgid "Pay with SEPA" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:5 +msgid "" +"SEPA, the Single Euro Payments Area, is a payment-integration initiative of " +"the European Union to simplify bank transfers denominated in euros. SEPA " +"allows you to send payment orders to your bank to automate bank wire " +"transfers." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:9 +msgid "SEPA is supported by the banks of the 27 EU member states, as well as:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:11 +msgid "EFTA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:13 +msgid "Iceland;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:14 +msgid "Liechtenstein;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:15 +msgid "Norway;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:16 +msgid "Switzerland." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:18 +msgid "Non-EEA SEPA countries:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:20 +msgid "Andorra;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:21 +msgid "Monaco;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:22 +msgid "San Marino;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:23 +msgid "United Kingdom;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:24 +msgid "Vatican City State." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:26 +msgid "Non-EEA territories:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:28 +msgid "Saint-Pierre-et-Miquelon;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:29 +msgid "Guernsey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:30 +msgid "Jersey;" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:31 +msgid "Isle of Man." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:33 +msgid "" +"When paying a bill in Odoo, you can select SEPA mandates as a payment " +"option. At the day's end, you can generate the SEPA file containing all bank" +" wire transfers and send it to the bank." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:36 +msgid "" +"By default, the file follows the SEPA Credit Transfer **'pain.001.001.03'** " +"specifications. This is a well-defined standard among banks. However, for " +"Swiss and German companies, other formats are used " +"**'pain.001.001.03.ch.02'** for Switzerland and **'pain.001.003.03'** for " +"Germany." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:40 +msgid "" +"Once the payments are processed by your bank, you can directly import the " +"account statement in Odoo. The bank reconciliation process will seamlessly " +"match the SEPA orders you sent to your bank with actual bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:48 +msgid "Activate SEPA Credit Transfer (SCT)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:50 +msgid "" +"To pay suppliers with SEPA, you must activate the **SEPA Credit Transfer** " +"setting. To do so, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Vendor Payments: SEPA Credit Transfer (SCT)`. By activating the" +" setting and filling out your company data, you will be able to use the SCT " +"option when paying your vendor." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:56 +msgid "" +"According to the localization package installed, the **SEPA Direct Debit** " +"and **SEPA Credit Transfer** modules may be installed by default. If not, " +"they need to be :ref:`installed <general/install>`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:60 +msgid "Activate SEPA payment methods on banks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:62 +msgid "" +"From the accounting dashboard, click on the drop-down menu (:guilabel:`⋮`) " +"on your bank journal and select :guilabel:`Configuration`. Click the " +":guilabel:`Outgoing Payments` tab, and, if not already present, add " +":guilabel:`SEPA Credit Transfer` under :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:66 +msgid "" +"Make sure to specify the IBAN account number (domestic account numbers do " +"not work with SEPA) and the BIC (bank identifier code) in the " +":guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:70 +msgid "Registering payments" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:72 +msgid "" +"You can register and vendor payments made with SEPA. To do so, go to " +":menuselection:`Accounting --> Vendors --> Payments`. When creating your " +"payment, select :guilabel:`SEPA Credit Transfer` as the :guilabel:`Payment " +"Method`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:76 +msgid "" +"The first time you pay a vendor with SEPA, you have to fill in the " +":guilabel:`Recipient Bank Account` field with the bank name, IBAN, and BIC " +"(Bank Identifier Code). Odoo automatically verifies if the IBAN format is " +"respected." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:80 +msgid "" +"For future payments to this vendor, Odoo will automatically suggest you the " +"bank account, but it remains possible to select a new one." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_sepa.rst:83 +msgid "" +"Once your payment is registered, do not forget to confirm it. You can also " +"pay vendor bills from the bill directly using the :guilabel:`Register " +"Payment` button at the top of a vendor bill. The form is the same, but the " +"payment is directly linked to the bill and will be automatically reconciled " +"with it." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:3 +msgid "Trusted accounts (send money)" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:5 +msgid "" +"To protect users from sending money to scammers, vendor bank account numbers" +" must be marked as trusted before you can use them to make an outgoing " +"payment." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:8 +msgid "" +"To do so, open the vendor bank account and click on the :guilabel:`Send " +"Money` toggle switch button." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst-1 +msgid "" +"Example of a vendor bank account with the \"Send Money\" toggle button " +"switched to \"trusted.\"" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:15 +msgid "All accounts are initially marked as untrusted." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:18 +msgid "Phishing attacks" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:20 +msgid "" +"A **phishing attack** is an online scam designed to trick individuals or " +"companies into giving away sensitive information or money by sending out " +"fraudulent communication. Fraudsters pretend to be legitimate companies and " +"may use partial information to give credibility to their requests." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:24 +msgid "" +"There are several types of phishing attacks, including **invoice fraud**. In" +" this case, the fraudster pretends to be a genuine supplier following up on " +"unpaid bills or sending a new invoice, but with different payment " +"information than usual and with fake contact details." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:28 +msgid "" +"To protect yourself from these types of phishing attacks, remain vigilant " +"when you receive unexpected invoices or payment requests." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:32 +msgid "" +"In case of doubt, **we recommend contacting the vendor by phone**. Make sure" +" to call an official phone number by searching yourself, as the URLs, email " +"addresses, and phone numbers written in the communication you received may " +"be fake." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:37 +msgid "Elements to check" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:39 +msgid "" +"There are several elements you can check by yourself when you receive an " +"outgoing payment request to a new account:" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:46 +msgid "Communication style" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:43 +msgid "" +"Fraudulent emails and invoices often use a different communication style, " +"such as **different wording**, and may include **spelling and grammatical " +"mistakes**. Examine and **compare** them with previous ones that you know to" +" be authentic (e.g., payment instructions, language, company logo, etc.).*" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:50 +msgid "Urgency" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:49 +msgid "" +"Invoice frauds often use **urgent or threatening language** and change the " +"**payment deadline**. Check if you really received a late payment reminder " +"previously." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:53 +msgid "Type of account" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:53 +msgid "" +"A company is unlikely to replace a bank account with a **money transfer " +"service**." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:60 +msgid "Email and links domain names" +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:56 +msgid "" +"Double-check the **email address domain** (`example@domain.com`). However, " +"be wary that fraudsters can make their email addresses look genuine or even " +"hack email addresses from your vendor's employees or even someone within " +"your own organization." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/trusted_accounts.rst:60 +msgid "" +"Hover over the links in your email and check that the URLs they redirect to " +"are genuine. Your internet browser usually displays the link's target at the" +" bottom left of the window." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:8 +msgid "Main reports available" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:10 +msgid "" +"Besides the reports created specifically in each localisation module, a few " +"very useful **generic** and **dynamic reports** are available for all " +"countries :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:14 +msgid "**Balance Sheet**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:15 +msgid "**Profit and Loss**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:16 +msgid "**Executive Summary**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:17 +msgid "**General Ledger**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:18 +msgid "**Aged Payable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:19 +msgid "**Aged Receivable**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:20 +msgid "**Cash Flow Statement**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:21 +msgid "**Tax Report**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:22 +msgid "**Bank Reconciliation**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:24 +msgid "" +"You can annotate every reports to print them and report to your adviser. " +"Export to xls to manage extra analysis. Drill down in the reports to see " +"more details (payments, invoices, journal items, etc.)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:28 +msgid "" +"You can also compare values with another period. Choose how many periods you" +" want to compare the chosen time period with. You can choose up to 12 " +"periods back from the date of the report if you don't want to use the " +"default **Previous 1 Period** option." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:38 +msgid "" +"The **Balance Sheet** shows a snapshot of the assets, liabilities and equity" +" of your organisation as at a particular date." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:44 +msgid "Profit and Loss" +msgstr "กำไรขาดทุน" + +#: ../../content/applications/finance/accounting/reporting.rst:46 +msgid "" +"The **Profit and Loss** report (or **Income Statement**) shows your " +"organisation's net income, by deducting expenses from revenue for the report" +" period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:53 +msgid "Executive Summary" +msgstr "ข้อมูลสรุป" + +#: ../../content/applications/finance/accounting/reporting.rst:55 +msgid "" +"The **Executive Summary** allows for a quick look at all the important " +"figures you need to run your company." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:58 +msgid "" +"In very basic terms, this is what each of the items in this section is " +"reporting :" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "**Performance:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:64 +msgid "**Gross profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:63 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales (things like labour, materials, etc)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:70 +msgid "**Net profit margin:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:67 +msgid "" +"The contribution each individual sale made by your business less any direct " +"costs needed to make those sales, as well as any fixed overheads your " +"company has (things like rent, electricity, taxes you need to pay as a " +"result of those sales)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "**Return on investment (p.a.):**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:73 +msgid "" +"The ratio of net profit made, to the amount of assets the company used to " +"make those profits." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:93 +msgid "**Position:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:77 +msgid "**Average debtor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:77 +msgid "" +"The average number of days it takes your customers to pay you (fully), " +"across all your customer invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:80 +msgid "**Average creditor days:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:80 +msgid "" +"The average number of days it takes you to pay your suppliers (fully) across" +" all your bills." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:85 +msgid "**Short term cash forecast:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:83 +msgid "" +"How much cash is expected in or out of your organisation in the next month " +"i.e. balance of your **Sales account** for the month less the balance of " +"your **Purchases account** for the month." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:93 +msgid "**Current assets to liabilities:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:88 +msgid "" +"Also referred to as **current ratio**, this is the ratio of current assets " +"(assets that could be turned into cash within a year) to the current " +"liabilities (liabilities which will be due in the next year). This is " +"typically used as as a measure of a company's ability to service its debt." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:98 +msgid "General Ledger" +msgstr "บัญชีแยกประเภททั่วไป" + +#: ../../content/applications/finance/accounting/reporting.rst:100 +msgid "" +"The **General Ledger Report** shows all transactions from all accounts for a" +" chosen date range. The initial summary report shows the totals for each " +"account and from there you can view a detailed transaction report or any " +"exceptions. This report is useful for checking every transaction that " +"occurred during a certain period of time." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:111 +msgid "Aged Payable" +msgstr "อายุบัญชีเจ้าหนี้" + +#: ../../content/applications/finance/accounting/reporting.rst:113 +msgid "" +"Run the **Aged Payable Details** report to display information on individual" +" bills, credit notes and overpayments owed by you, and how long these have " +"gone unpaid." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:122 +msgid "Aged Receivable" +msgstr "อายุบัญชีลูกหนี้" + +#: ../../content/applications/finance/accounting/reporting.rst:124 +msgid "" +"The **Aged Receivables** report shows the sales invoices that were awaiting " +"payment during a selected month and several months prior." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:130 +msgid "Cash Flow Statement" +msgstr "งบกระแสเงินสด" + +#: ../../content/applications/finance/accounting/reporting.rst:132 +msgid "" +"The **Cash Flow Statement** shows how changes in balance sheet accounts and " +"income affect cash and cash equivalents, and breaks the analysis down to " +"operating, investing and financing activities." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:141 +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:101 +msgid "Tax Report" +msgstr "รายงานภาษี" + +#: ../../content/applications/finance/accounting/reporting.rst:143 +msgid "" +"This report allows you to see the **net** and **tax amounts** for all the " +"taxes grouped by type (sale/purchase)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:3 +msgid "Analytic accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:5 +msgid "" +"Analytic accounting helps you track costs and revenues, as well as analyze " +"the profitability of a project or service. When creating your journal " +"entries, the analytic widget allows the distribution of costs in one or more" +" analytic accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:12 +msgid "" +"Enable the :guilabel:`Analytic Accounting` feature by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Analytics`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:16 +msgid "Analytic accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:18 +msgid "The analytic accounts give an overview of your costs and revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:20 +msgid "" +"Access your existing analytic accounts by going to " +":menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Accounts`. To create a new analytic account, click :guilabel:`New`," +" and fill in the required information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:24 +msgid ":guilabel:`Analytic Account`: add the name of your analytic account;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:25 +msgid ":guilabel:`Customer`: select the customer related to your project;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:26 +msgid "" +":guilabel:`Reference`: add a reference to make it easier to find the account" +" when you are on your bill;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:28 +msgid "" +":guilabel:`Plan`: add an :ref:`analytic plan " +"<analytic_accounting/analytic_plans>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:29 +msgid "" +":guilabel:`Company`: if you are managing multiple companies, select the " +"company for which the analytic account will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:31 +msgid ":guilabel:`Currency`: select the currency of the analytic account;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:33 +msgid "Then, fill in your :doc:`budget <budget>` information." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:38 +msgid "Analytic plans" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:40 +msgid "" +"The analytic plans allow you to analyze your accounting. For example, to " +"track costs and revenues by project or department." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:43 +msgid "" +"You can access the analytic plans by going to :menuselection:`Accounting -->" +" Configuration --> Analytic Accounting: Analytic Plans`. Click " +":guilabel:`New` to create a new plan." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst-1 +msgid "create an analytic plan" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:50 +msgid "The following information must be completed:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:52 +msgid "" +":guilabel:`Parent`: link your plan to another :guilabel:`Analytic Plan` to " +"build a hierarchy between your plans;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:54 +msgid "" +":guilabel:`Default Applicability`: decide how your plan behaves in the " +"widget when creating a new journal entry:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:57 +msgid "" +":guilabel:`Optional`: if selected, it is not mandatory to add the analytic " +"plan in the widget;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:58 +msgid "" +":guilabel:`Mandatory`: if selected, an orange bullet is visible in the " +"widget next to the plan until the analytic distribution is done (the bullet " +"then turns to green); it is not possible to confirm the entry if no analytic" +" account is selected;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:61 +msgid "" +":guilabel:`Unavailable`: if selected, the plan is not available in the " +"widget." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:63 +msgid "" +":guilabel:`Color`: select the color of the tag related to this specific " +"plan;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:64 +msgid ":guilabel:`Company`: add the company to which the plan applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:66 +msgid "" +"You can also fine-tune your plans' applicability by filling in the " +":guilabel:`Applicability` tab:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:68 +msgid "" +":guilabel:`Domain`: choose to which accounting document your plan applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:69 +msgid "" +":guilabel:`Financial Accounts Prefix`: select the prefix of the account(s) " +"to which this plan should be applied;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:71 +msgid "" +":guilabel:`Product Category`: decide to which product category the plan " +"applies;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:73 +msgid "" +":guilabel:`Applicability`: decide how your plan behaves in the widget when " +"creating a new journal" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:73 +msgid "" +"entry. The applicability you set here always overrides the default " +"applicability." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:75 +msgid "Two smart buttons are available in the top-right corner:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:77 +msgid "" +":guilabel:`Subplans`: can be created to have a more complex analytic " +"structure. Click the :guilabel:`Subplans` smart button, and then " +":guilabel:`New` to add a subplan;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:79 +msgid "" +":guilabel:`Analytic Accounts`: to reach the analytic accounts related to the" +" plan." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:82 +msgid "" +"The analytic widget is prefilled based on the applicability, and the " +":ref:`Analytic Distribution Models <analytic_distribution_models>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:84 +msgid "Each analytic plan must have at least one analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:87 +msgid "Analytic distribution" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:89 +msgid "" +"Add a plan in the :guilabel:`Analytic` column when creating an invoice or " +"bill. This field is mandatory only if you previously linked your analytic " +"plan to at least one analytic account. After adding the plan, a **widget** " +"opens where you can fill in the different information. You can add **tags** " +"to reflect the related analytic accounts and decide how to split the costs " +"between the accounts by modifying the percentage." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst-1 +msgid "create a distribution template" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:102 +msgid "Analytic distribution models" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:104 +msgid "" +"The analytic distribution models automatically apply a specific distribution" +" based on defined criteria." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:107 +msgid "" +"To create a new analytic distribution model, go to " +":menuselection:`Accounting --> Configuration --> Analytic Distribution " +"Models`, click :guilabel:`New` and set the conditions your model has to meet" +" to automatically apply:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:111 +msgid "" +":guilabel:`Accounts Prefix`: this analytic distribution will apply to all " +"financial accounts sharing the prefix specified;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:113 +msgid "" +":guilabel:`Partner`: select a partner for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:114 +msgid "" +":guilabel:`Partner Category`: this field is not visible by default: add it " +"by clicking on the columns selection button, and tick the :guilabel:`Partner" +" Category` box. Add the partner category for which the analytic distribution" +" will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:117 +msgid "" +":guilabel:`Product`: select a product for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:118 +msgid "" +":guilabel:`Product Category`: this field is not visible by default: add it " +"by clicking on the columns selection button, and tick the :guilabel:`Product" +" Category` box. Select a product category for which the analytic " +"distribution will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:121 +msgid "" +":guilabel:`Analytic`: add the analytic accounts and their distribution;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:122 +msgid "" +":guilabel:`Company`: select a company for which the analytic distribution " +"will be used;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:123 +msgid "" +":guilabel:`Analytic Distribution`: if the above conditions are met, the " +":guilabel:`Analytic plan` defined in this field as well as the distribution " +"to be applied between the different analytic accounts is selected " +"automatically on the entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:128 +msgid "" +"To **mass edit** several entries simultaneously, go to " +":menuselection:`Accounting --> Accounting --> Journal items`, and select the" +" ones that need to be updated. Add the required distribution in the " +":guilabel:`Analytic Distribution` column, and click on the :guilabel:`floppy" +" disk` icon to save. The analytic distribution template pops up, and you can" +" save it for later use." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:3 +msgid "Financial budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:5 +msgid "" +"Managing budgets is an essential part of running a business. Budgets help " +"people become more intentional with how money is spent and direct people to " +"organize and prioritize their work to meet financial goals. They allow the " +"planning of a desired financial outcome and then measure the actual " +"performance against the plan. Odoo manages budgets using both **general** " +"and **analytic accounts**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:13 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Analytics section`, and enable :guilabel:`Budget Management`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:17 +msgid "Budgetary positions" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:19 +msgid "" +"Budgetary positions are lists of accounts for which you want to keep budgets" +" (typically expense or income accounts)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:22 +msgid "" +"To define budgetary positions, go to :menuselection:`Accounting --> " +"Configuration --> Management: Budgetary Positions` and :guilabel:`New`. Add " +"a :guilabel:`Name` to your budgetary position and select the " +":guilabel:`Company` it applies to. Click :guilabel:`Add a line` to add one " +"or more accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:28 +msgid "" +"Each budgetary position can have any number of accounts from the chart of " +"accounts, though it must have at least one." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:32 +msgid "Use case" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:34 +msgid "Let’s illustrate this with an example." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:36 +msgid "" +"We just started a project with *Smith & Co*, and we would like to budget the" +" income and expenses of that project. We plan on having a revenue of 1000, " +"and we don’t want to spend more than 700." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:39 +msgid "" +"First, we need to define what accounts relate to our project’s expenses. Go " +"to :menuselection:`Accounting --> Configuration --> Management: Budgetary " +"positions`, and click :guilabel:`New` to add a position. Add the accounts " +"wherein expenses will be booked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:47 +msgid "" +"Let's repeat the steps to create a budgetary position that reflects the " +"revenue." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "display the Smith and Co revenue" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:54 +msgid "Analytical accounts" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:56 +msgid "" +"Odoo needs to know which costs or expenses are relevant to a specified " +"budget, as the above general accounts may be used for different projects. Go" +" to :menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Accounts` and click :guilabel:`New` to add a new **Analytic " +"Account** called *Smith & Co*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:61 +msgid "" +"The :guilabel:`Plan` field has to be completed. Plans group multiple " +"analytic accounts; they distribute costs and benefits to analyze business " +"performance. **Analytic Plans** can be created or configured by going to " +":menuselection:`Accounting --> Configuration --> Analytic Accounting: " +"Analytic Plans`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:66 +msgid "" +"When creating a new customer invoice and/or vendor bill, you have to refer " +"to this analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "add analytic accounts in a new invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:73 +msgid "Define the budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:75 +msgid "" +"Let’s set our targets. We specified that we expect to gain 1000 with this " +"project, and we would like not to spend more than 700. Go to " +":menuselection:`Accounting --> Management: Budgets` and click " +":guilabel:`New` to create a new budget for *Smith & Co* project." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:79 +msgid "" +"First, fill in your :guilabel:`Budget Name`. Then, select the " +":guilabel:`Period` wherein the budget is applicable. Next, add the " +":guilabel:`Budgetary Position` you want to track, define the related " +":guilabel:`Analytic Account`, and add the :guilabel:`Planned Amount`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst-1 +msgid "budget lines display" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:88 +msgid "" +"When recording a planned amount related to expenses, the amount must be " +"negative." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:91 +msgid "Check your budget" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:93 +msgid "" +"Go to :menuselection:`Accounting --> Management: Budgets` and find the " +"*Smith & Co* Project to see how it evolves according to the expenses or " +"income for the related analytic account." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:96 +msgid "" +"The :guilabel:`Practical Amount` evolves when a new journal entry related to" +" your analytic account and an account from your budgetary position is " +"created." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/budget.rst:99 +msgid "" +"The :guilabel:`Theoretical Amount` represents the amount of money you " +"theoretically could have spent or should have received based on the date. " +"For example, suppose your budget is 1200 for 12 months (January to " +"December), and today is 31 of January. In that case, the theoretical amount " +"will be 100 since this is the actual amount that could have been made." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:3 +msgid "Custom reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:5 +msgid "" +"Odoo comes with a powerful and easy-to-use reporting framework. The engine " +"allows you to create new reports, such as **tax reports**, or **balance " +"sheets** and **income statements** with **specific groupings** and " +"**layouts**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:10 +msgid "" +"Activate the :ref:`developer mode <developer-mode>` to access the accounting" +" report creation interface." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:13 +msgid "" +"To create a new report, go to :menuselection:`Accounting --> Configuration " +"--> Management: Accounting Reports`. From here, you can either create a " +":ref:`root report <customize-reports/root>` or a :ref:`variant <customize-" +"reports/variants>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Accounting reports engine." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:24 +msgid "Root reports" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:26 +msgid "" +"Root reports can be regarded as generic, neutral accounting reports. They " +"serve as models on which local accounting versions are built. If a report " +"has no root report, it is considered to be a root report itself." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:31 +msgid "" +"A tax report for Belgium and the US would both use the same generic version " +"as a base and adapt it for their domestic regulations." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:34 +msgid "" +"When creating a new root report, you need to create a **menu item** for it. " +"To do so, open the report and then, on that same report, click on " +":menuselection:`Action --> Create Menu Item`. Refresh the page; the report " +"is now available under :menuselection:`Accounting --> Reporting`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:39 +msgid "" +"Cases that require creating a new root report are rare, such as when a " +"country's tax authorities require a new and specific type of report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Create Menu Item button." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:49 +msgid "Variants" +msgstr "ตัวแปร" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:51 +msgid "" +"Variants are country-specific versions of root reports and, therefore, " +"always refer to a root report. To create a variant, select a generic (root) " +"report in the :guilabel:`Root Report` field when creating a new report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:55 +msgid "" +"When a root report is opened from one of the accounting app's main menus, " +"all its variants are displayed in the variant selector in the top right " +"corner of the view." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:59 +msgid "" +"In the following image, :guilabel:`VAT Report (BE)` is the variant of the " +"root :guilabel:`Generic Tax report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "Report variant selection." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:67 +msgid "Lines" +msgstr "รายการ" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:69 +msgid "" +"After having created a report (either root or variant), you need to fill it " +"with lines. You can either create a new one by clicking on :guilabel:`Add a " +"line`, or modify an existing line by clicking on it. All lines *require* a " +":guilabel:`Name`, and can have an optional additional :guilabel:`Code` (of " +"your choice) if you wish to use their value in formulas." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Engine lines options." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:79 +msgid "Expressions" +msgstr "ตัวสั่งงาน" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:81 +msgid "" +"Each line can contain one or multiple **expressions**. Expressions can be " +"seen as **sub-variables** needed by a report line. To create an expression, " +"click on :guilabel:`Add a line` *within* a line report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:85 +msgid "" +"When creating an expression, you must attribute a :guilabel:`label` used to " +"refer to that expression. Therefore, it has to be **unique** among the " +"expressions of each line. Both a :guilabel:`Computation Engine` and a " +":guilabel:`Formula` must also be indicated. The **engine** defines how your " +"**formula(s)** and **subformula(s)** are interpreted. It is possible to mix " +"expressions using different computation engines under the same line if you " +"need to." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:92 +msgid "Depending on the engine, :guilabel:`subformulas` may also be required." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:95 +msgid "'Odoo Domain' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:97 +msgid "" +"With this engine, a formula is interpreted as an :ref:`Odoo domain " +"<reference/orm/domains>` targeting `account.move.line` objects." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:100 +msgid "" +"The subformula allows you to define how the move lines matching the domain " +"are used to compute the value of the expression:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:104 +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 +msgid "`sum`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:104 +msgid "The result is the sum of all the balances of the matched move lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:108 +msgid "`sum_if_pos`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:107 +msgid "" +"The result is the sum of all the balances of the matched move lines if this " +"amount is positive. Otherwise, it is `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:112 +msgid "`sum_if_neg`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:111 +msgid "" +"The result is the sum of all the balances of the matched move lines if this " +"amount is negative. Otherwise, it is `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:117 +msgid "`count_rows`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:115 +msgid "" +"The result is the number of sub-lines of this expression. If the parent line" +" has a group-by value, this will correspond to the number of distinct " +"grouping keys in the matched move lines. Otherwise, it will be the number of" +" matched move lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:119 +msgid "" +"You can also put a `-` sign at the beginning of the subformula to " +"**reverse** the sign of the result." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Expression line within a line report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:127 +msgid "'Tax Tags' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:129 +msgid "" +"A formula made for this engine consists of a name used to match tax tags. If" +" such tags do not exist when creating the expression, they will be created." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:132 +msgid "" +"When evaluating the expression, the expression computation can roughly be " +"expressed as: **(amount of the move lines with** `+` **tag)** `-` **(amount " +"of the move lines with** `-` **tag)**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:136 +msgid "" +"If the formula is `tag_name`, the engine matches tax tags `+tag_name` and " +"`-tag_name`, creating them if necessary. To exemplify further: two tags are " +"matched by the formula. If the formula is `A`, it will require (and create, " +"if needed) tags `+A` and `-A`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:141 +msgid "'Aggregate Other Formulas' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:143 +msgid "" +"Use this engine when you need to perform arithmetic operations on the " +"amounts obtained for other expressions. Formulas here are composed of " +"references to expressions separated by one of the four basic arithmetic " +"operators (addition `+`, subtraction `-`, division `/`, and multiplication " +"`*`). To refer to an expression, type in its parent line's **code** followed" +" by a period `.` and the expression's **label** (ex. **code.label**)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:149 +msgid "**Subformulas** can be one of the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:153 +msgid "`if_above(CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:152 +msgid "" +"The value of the arithmetic expression will be returned only if it is " +"greater than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:157 +msgid "`if_below(CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:156 +msgid "" +"The value of the arithmetic expression will be returned only if it is lower " +"than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:161 +msgid "`if_between(CUR1(amount1), CUR2(amount2))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:160 +msgid "" +"The value of the arithmetic expression will be returned only if it is " +"strictly between the provided bounds. Otherwise, it will be brought back to " +"the closest bound." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:166 +msgid "`if_other_expr_above(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:164 +msgid "" +"The value of the arithmetic expression will be returned only if the value of" +" the expression denoted by the provided line code and expression label is " +"greater than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:171 +msgid "`if_other_expr_below(LINE_CODE.EXPRESSION_LABEL, CUR(amount))`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:169 +msgid "" +"The value of the arithmetic expression will be returned only if the value of" +" the expression denoted by the provided line code and expression label is " +"lower than the provided bound. Otherwise, the result will be `0`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:173 +msgid "" +"`CUR` is the currency code in capital letters, and `amount` is the amount of" +" the bound expressed in that currency." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:176 +msgid "" +"You can also use the `cross_report` subformula to match an expression found " +"in another report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:179 +msgid "'Prefix of Account Codes' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:181 +msgid "" +"This engine is used to match amounts made on accounts using the prefixes of " +"these accounts' codes as variables in an arithmetic expression." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "Arithmetic expressions can also be a single prefix, such as here." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21 + 10 - 5`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula adds the balances of the move lines made on accounts whose " +"codes start with `21` and `10`, and subtracts the balance of the ones on " +"accounts with the prefix `5`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:193 +msgid "It is also possible to ignore a selection of sub-prefixes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21 + 10\\\\(101, 102) - 5\\\\(57)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula works the same way as the previous example but ignores the " +"prefixes `101`, `102`, and `57`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:200 +msgid "" +"You can apply 'sub-filtering' on **credits and debits** using the `C` and " +"`D` suffixes. In this case, an account will only be considered if its prefix" +" matches, *and* if the total balance of the move lines made on this account " +"is **credit/debit**." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:205 +msgid "" +"Account `210001` has a balance of -42 and account `210002` has a balance of " +"25. The formula `21D` only matches the account `210002`, and hence returns " +"25. `210001` is not matched, as its balance is *credit*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:209 +msgid "Prefix exclusions can be mixed with the `C` and `D` suffixes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21D + 10\\\\(101, 102)C - 5\\\\(57)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula adds the balances of the move lines made on accounts whose code" +" starts with `21` *if* it is debit (`D`) and `10` *if* it is credit (`C`), " +"but ignores prefixes `101`, `102`, and subtracts the balance of the ones on " +"accounts with the prefix `5`, ignoring the prefix `57`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:217 +msgid "" +"To match the letter `C` or `D` in a prefix and not use it as a suffix, use " +"an empty exclusion `()`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`21D\\\\()`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose code starts with `21D`, regardless of " +"their balance sign." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:223 +msgid "" +"In addition to using code prefixes to include accounts, you can also match " +"them with **account tags**. This is especially useful, for example, if your " +"country lacks a standardized chart of accounts, where the same prefix might " +"be used for different purposes across companies." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(25)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose associated tags contain the one with id " +"*25*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:231 +msgid "" +"If the tag you reference is defined in a data file, an xmlid can be used " +"instead of the id." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts whose associated tags include the tag denoted " +"by *my_module.my_tag*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:238 +msgid "" +"You can also use arithmetic expressions with tags, possibly combining them " +"with prefix selections." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag) + tag(42) + 10`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"The balances of accounts tagged as *my_module.my_tag* will be summed with " +"those of accounts linked to the tag with ID *42* and accounts with the code " +"prefix `10`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:245 +msgid "`C` and `D` suffixes can be used in the same way with tags." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)C`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts with the tag *my_module.my_tag* and a credit " +"balance." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:251 +msgid "Prefix exclusion also works with tags." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`tag(my_module.my_tag)\\\\(10)`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "" +"This formula matches accounts with the tag *my_module.my_tag* and a code not" +" starting with `10`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:260 +msgid "'External Value' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:262 +msgid "" +"The 'external value' engine is used to refer to **manual** and **carryover " +"values**. Those values are not stored using `account.move.line`, but with " +"`account.report.external.value`. Each of these objects directly points to " +"the expression it impacts, so very little needs to be done about their " +"selection here." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:267 +msgid "**Formulas** can be one of the following:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:270 +msgid "" +"If the result must be the sum of all the external values in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "`most_recent`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:273 +msgid "" +"If the result must be the value of the latest external value in the period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:275 +msgid "In addition, **subformulas** can be used in two ways:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "`rounding=X`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:278 +msgid "" +"Replacing `X` with a number instructs to round the amount to X decimals." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:282 +msgid "`editable`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:281 +msgid "" +"Indicates this expression can be edited manually, triggering the display of " +"an icon in the report, allowing the user to perform this action." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:285 +msgid "" +"Manual values are created at the `date_to` currently selected in the report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:287 +msgid "Both subformulas can be mixed by separating them with a `;`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "`editable;rounding=2`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:0 +msgid "is a correct subformula mixing both behaviors." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:294 +msgid "'Custom Python Function' engine" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:296 +msgid "" +"This engine is a means for developers to introduce custom computation of " +"expressions on a case-by-case basis. The formula is the name of a **python " +"function** to call, and the subformula is a **key** to fetch in the " +"**dictionary** returned by this function. Use it only if you are making a " +"custom module of your own." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:302 +msgid "Columns" +msgstr "คอลัมน์" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:304 +msgid "" +"Reports can have an **indefinite number** of columns to display. Each column" +" gets its values from the **expressions** declared on the **lines**. The " +"field :guilabel:`expression_label` of the column gives the label of the " +"expressions whose value is displayed. If a line has no **expression** in " +"that field, then nothing is displayed for it in this column. If multiple " +"columns are required, you must use different **expression** labels." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst-1 +msgid "Columns of report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/customize.rst:314 +msgid "" +"When using the **period comparison** feature found under the " +":guilabel:`Options` tab of an accounting report, all columns are repeated in" +" and for each period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:3 +msgid "Data inalterability check report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:5 +msgid "" +"Tax authorities in some countries require companies to **prove their posted " +"accounting entries are inalterable**, meaning that once an entry has been " +"posted, it can no longer be changed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:8 +msgid "" +"To do so, Odoo can use the **SHA-256 algorithm** to create a unique " +"fingerprint for each posted entry. This fingerprint is called a hash. The " +"hash is generated by taking an entry's essential data (the values of the " +"`date`, `journal_id`, `company_id`, `debit`, `credit`, `account_id`, and " +"`partner_id` fields), concatenating it, and inputting it to the SHA-256 hash" +" function, which then outputs a fixed size (256-bit) string of characters. " +"The hash function is deterministic (:dfn:`the same input always creates the " +"same output`): any minor modification to the original data would completely " +"change the resulting hash. Consequently, the SHA-256 algorithm is often " +"used, among others, for data integrity verification purposes." +msgstr "" +"ในการทำเช่นนั้น Odoo สามารถใช้ **อัลกอริธึม SHA-256** " +"เพื่อสร้างลายนิ้วมือที่ไม่ซ้ำกันสำหรับแต่ละรายการที่โพสต์ " +"ลายนิ้วมือนี้เรียกว่าแฮช แฮชถูกสร้างขึ้นโดยการนำข้อมูลสำคัญของรายการ " +"(ค่าของช่อง `date`, `journal_id`, `company_id`, `debit`, `credit`, " +"`account_id` และ `partner_id`) มาต่อกัน และ ป้อนลงในฟังก์ชันแฮช SHA-256 " +"ซึ่งจะส่งออกสตริงตัวอักษรขนาดคงที่ (256 บิต) ฟังก์ชันแฮชถูกกำหนดไว้ " +"(:dfn:`อินพุตเดียวกันจะสร้างเอาต์พุตเดียวกันเสมอ): " +"การแก้ไขข้อมูลต้นฉบับเล็กน้อยจะเปลี่ยนแฮชผลลัพธ์โดยสิ้นเชิง ด้วยเหตุนี้ " +"อัลกอริธึม SHA-256 " +"จึงมักถูกนำมาใช้เพื่อวัตถุประสงค์ในการตรวจสอบความสมบูรณ์ของข้อมูล" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:17 +msgid "" +"In addition, the previous entry's hash is always added to the next entry to " +"form a **hash chain**. This is used to ensure a new entry is not added " +"afterward between two posted entries, as doing so would break the hash " +"chain." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:22 +msgid "" +"Hashes generated by the SHA-256 algorithm are theoretically not unique, as " +"there is a finite number of possible values. However, this number is " +"exceptionally high: 2²⁵⁶, which is a lot bigger than the number of atoms in " +"the known universe. This is why hashes are considered unique in practice." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:30 +msgid "Lock posted entries with hash" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:32 +msgid "" +"To start using the hashing function, go to :menuselection:`Accounting --> " +"Configuration > Journals`. Open the journal for which you want to activate " +"the feature, go to the :guilabel:`Advanced Settings` tab, and enable " +":guilabel:`Lock Posted Entries with Hash`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:37 +msgid "" +"Once you post an entry on a locked journal, you cannot disable the feature " +"anymore, nor edit any posted entry." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:43 +msgid "Report download" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:45 +msgid "" +"To download the data inalterability check report, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Reporting` and" +" click on :guilabel:`Download the Data Inalterability Check Report`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:48 +msgid "" +"The report's first section is an overview of all your journals and their " +"configuration. Under the inalterability check column, you can see whether or" +" not a journal's posted entries are locked with a hash (V) or not (X). The " +"coverage column tells you when a journal's posted entries started being " +"locked." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Configuration report for two journals" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst:57 +msgid "" +"The second section gives you the result of the data consistency check for " +"each hashed journal. You can view the first hashed entry and its " +"corresponding hash and the last hashed entry and its corresponding hash." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/data_inalterability.rst-1 +msgid "Data consistency check report for a journal" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:3 +msgid "Intrastat" +msgstr "อินทราสแทต" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:5 +msgid "" +"Intrastat is the data collection and statistics production system for goods " +"traded among EU member states. It collects data on:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:8 +msgid "" +"Commercial transactions of goods for use, consumption, investment, or resale" +" with ownership transfer;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:10 +msgid "" +"Goods movements without transfer of ownership (e.g., stock relocations or " +"moves of goods before or after outsourced production or processing, and " +"after maintenance or repair);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:12 +msgid "Returns of goods." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:15 +msgid "" +"Although the Intrastat system continues to be used, the term Intrastat is " +"not used in the `latest legislation " +"<http://data.europa.eu/eli/reg/2019/2152/2022-01-01>`_, referring instead to" +" *intra-Union trade in goods statistics*." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:20 +msgid "" +"`Eurostat Statistics Explained - Glossary: Intrastat " +"<https://ec.europa.eu/eurostat/statistics-" +"explained/index.php?title=Glossary:Intrastat>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:26 +msgid "General configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:28 +msgid "" +"Enable the Intrastat report by going to :menuselection:`Accounting --> " +"Configuration --> Settings`. Under the :guilabel:`Customer Invoices` " +"section, tick :guilabel:`Intrastat` and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:35 +msgid "Default transaction codes: invoice and refund" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:37 +msgid "" +"You can set a default :ref:`transaction code <intrastat/transaction-code>` " +"for all newly created invoice and refund transactions. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select a " +":guilabel:`Default invoice transaction code` and/or a :guilabel:`Default " +"refund transaction code` and then :guilabel:`Save`. The code will be set " +"automatically on all respective invoice lines." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:45 +msgid "Region code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:47 +msgid "" +"The region code is **only used by Belgian companies**. Under " +":menuselection:`Accounting --> Configuration --> Settings`, select the " +":guilabel:`Company Intrastat Region` where the company is located and then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:52 +msgid "" +"If your warehouses are located in more than one region, you can define the " +"region code at the level of each warehouse instead. To do so, go to " +":menuselection:`Inventory --> Configuration --> Warehouses`, select a " +"warehouse, set its :guilabel:`Intrastat region`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:0 +msgid "Adding the Intrastat region to a warehouse" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:63 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:65 +msgid "" +"All products must be properly configured to be included in the Intrastat " +"report." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:70 +msgid "Commodity code" +msgstr "รหัสสินค้า" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:72 +msgid "" +"Commodity codes are internationally recognized reference numbers used to " +"classify goods depending on their **nature**. Intrastat uses the `Combined " +"Nomenclature <https://taxation-customs.ec.europa.eu/customs-4/calculation-" +"customs-duties/customs-tariff/combined-nomenclature_en>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:75 +msgid "" +"To add a commodity code, go to :menuselection:`Accounting --> Customers --> " +"Products` and select a product. Under the :guilabel:`Accounting` tab, set " +"the product's :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:79 +msgid "" +"`National Bank of Belgium - Intrastat commodity codes " +"<https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:85 +msgid "Quantity: weight and supplementary unit" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:87 +msgid "" +"Depending on the nature of the goods, it is necessary to specify either the " +"product's weight in kilos (without packaging) or the product's supplementary" +" unit, such as square meter (`m2`), number of items (`p/st`), liter (`l`), " +"or gram (`g`)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:91 +msgid "" +"To add a product's weight or supplementary unit, go to " +":menuselection:`Accounting --> Customers --> Products` and select a product." +" Under the :guilabel:`Accounting` tab, depending on the commodity code set, " +"either fill in the product :guilabel:`Weight` or its " +":guilabel:`Supplementary Units`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:98 +msgid "Country of origin" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:100 +msgid "" +"To add the product's country of origin, go to :menuselection:`Accounting -->" +" Customers --> Products` and select a product. Under the " +":guilabel:`Accounting` tab, set the :guilabel:`Country of Origin`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:106 +msgid "Invoices and bills configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:108 +msgid "" +"Once products are properly configured, several settings must be configured " +"on the invoices and bills you create." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:114 +msgid "Transaction code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:116 +msgid "" +"Transaction codes are used to identify a transaction's nature. :ref:`Default" +" transaction codes <intrastat/default-transaction-codes>` can be set for " +"invoice and refund transactions." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:119 +msgid "" +"To set a transaction code on an invoice line, create an invoice or a bill, " +"click the columns selection button, tick :guilabel:`Intrastat`, and use the " +"newly-added :guilabel:`Intrastat` column to select a transaction code." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst-1 +msgid "Adding the Intrastat column to an invoice or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:128 +msgid "" +"`National Bank of Belgium - Intrastat: Nature of transactions from January " +"2022 " +"<https://www.nbb.be/doc/dd/onegate/data/new_natures_of_transaction_2022_en.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:134 +msgid "Partner country" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:136 +msgid "" +"The partner country represents the vendor's country for bills and the " +"customer's country for invoices. It is automatically filled in using the " +"country set in the contact's :guilabel:`Country` field." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:140 +msgid "" +"To edit the partner country manually, create an invoice or a bill, click the" +" :guilabel:`Other Info` tab, and select the :guilabel:`Intrastat Country`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:146 +msgid "Transport code" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:148 +msgid "" +"The transport code identifies the presumed **mode of transport** used to " +"send the goods (arrival or dispatch)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:151 +msgid "" +"To add the transport code, create an invoice or a bill, go to the " +":guilabel:`Other info` tab, and select the :guilabel:`Intrastat Transport " +"Mode`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:157 +msgid "Value of the goods" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:159 +msgid "" +"The value of a good is the untaxed :guilabel:`Subtotal` (:guilabel:`Price` " +"multiplied by :guilabel:`Quantity`) of an invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:165 +msgid "Partner configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:167 +msgid "" +"Two fields from the partner's contact form are used with Intrastat: " +":guilabel:`VAT` and :guilabel:`Country`. The country can be :ref:`manually " +"set <intrastat/partner-country>` on the invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:172 +msgid "Generate the Intrastat report" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:174 +msgid "" +"Generate the report by going to :menuselection:`Accounting --> Reporting -->" +" Audit Reports: Intrastat Report`. It is automatically computed based on the" +" :ref:`default configuration <intrastat/general-configuration>` and the " +"information found on the :ref:`products <intrastat/product-configuration>`, " +":ref:`invoices and bills <intrastat/invoice-bill-configuration>`, and " +":ref:`partners <intrastat/partner>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:180 +msgid "" +"Export the report as a PDF, XLSX, or XML file to post it to your legal " +"administration." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:182 +msgid "" +"Each report line refers to a single invoice line and contains the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:184 +msgid "Invoice or bill reference number;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:185 +msgid "" +"System, which is a code automatically generated depending on whether the " +"document is an invoice (dispatch) or a bill (arrival);" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:187 +msgid "" +":ref:`Country <intrastat/partner-country>`, which is the vendor's country " +"for arrivals and the customer's country for dispatches;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:189 +msgid ":ref:`Transaction Code <intrastat/transaction-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:190 +msgid "" +"(If your company is located in Belgium) :ref:`Region Code <intrastat/region-" +"code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:191 +msgid ":ref:`Commodity Code <intrastat/commodity-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:192 +msgid ":ref:`Origin Country <intrastat/origin-country>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:193 +msgid ":ref:`Partner VAT <intrastat/partner>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:194 +msgid ":ref:`Transport Code <intrastat/transport-code>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:195 +msgid ":doc:`Incoterm Code <../customer_invoices/incoterms>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:196 +msgid ":ref:`Weight <intrastat/quantity>`;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:197 +msgid ":ref:`Supplementary Units <intrastat/quantity>`; and" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/intrastat.rst:198 +msgid "" +":ref:`Value <intrastat/value>`, which is always expressed in euros even if " +"the original invoice or bill used another currency." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:3 +msgid "Silverfin integration" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:5 +msgid "" +"`Silverfin <https://www.silverfin.com>`_ is a third-party service provider " +"that offers a cloud platform for accountants." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:8 +msgid "" +"Odoo and Silverfin provide an integration to automate the synchronization of" +" data." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:13 +msgid "" +"To configure this integration, you need to input the following data into " +"your Silverfin account:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:15 +msgid "user's email address" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:16 +msgid ":ref:`Odoo API key <silverfin/api-key>`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:17 +msgid "URL of the Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:18 +msgid "name of your Odoo database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:23 +msgid "Odoo API key" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:25 +msgid "" +"You can create Odoo external API keys either :ref:`for a single database " +"<silverfin/api-singledb>` (hosting: Odoo Online, On-premise, and Odoo.sh) or" +" :ref:`for all databases managed by a single user <silverfin/api-" +"multipledb>` (hosting: Odoo Online)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:30 +msgid "" +"These API keys are personal and provide full access to your user account. " +"Store it securely." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:31 +msgid "" +"You can copy the API key only at its creation. It is not possible to " +"retrieve it later." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:32 +msgid "If you need it again, create a new API key (and delete the old one)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:35 +msgid ":doc:`/developer/reference/external_api`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:40 +msgid "Per database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:42 +msgid "" +"To add an API key to a **single** database, connect to the database, enable " +"the :ref:`developer mode <developer-mode>`, click on the user menu, and then" +" :guilabel:`My Profile` / :guilabel:`Preferences`. Under the " +":guilabel:`Account Security` tab, click on :guilabel:`New API Key`, confirm " +"your password, give a descriptive name to your new key, and copy the API " +"key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for a database" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:51 +msgid ":ref:`api/external_api/keys`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:56 +msgid "For all databases (fiduciaries)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:58 +msgid "" +"To add an API key to **all** databases managed by a single user at the same " +"time **(the easiest method for fiduciaries)**, navigate to `Odoo's website " +"<https://www.odoo.com>`_ and sign in with your administrator account. Next," +" open `your account security settings in developer mode " +"<https://www.odoo.com/my/security?debug=1>`_, click on :guilabel:`New API " +"Key`, confirm your password, give a descriptive name to your new key, and " +"copy the new API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst:65 +msgid "" +"Open the `database manager <https://www.odoo.com/my/databases>`_ to view all" +" databases that will be linked to the single API key." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/silverfin.rst-1 +msgid "creation of an Odoo external API key for an Odoo user" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:3 +msgid "Tax carryover" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:5 +msgid "" +"When performing tax reports, the **tax carryover** feature allows carrying " +"amounts from one period to another without creating new entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:8 +msgid "" +"It has been created to meet the legal requirements of specific locations, " +"where amounts must be transferred from period to period (for example, " +"because the total of the line is negative)." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:11 +msgid "" +"The feature is activated by default in countries where it is required, such " +"as Belgium, France, and Italy. There is no specific configuration required." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:14 +msgid "" +"Let’s take an example of a Belgian company that created a credit note of 100" +" for one of their customers. The due tax is 21%." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "Illustration with a credit note" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:21 +msgid "" +"In this case, as per local regulation, grid 81 of the tax report may contain" +" a negative amount. But it must be declared to the government as zero, and " +"the negative amount should be carried over to the next period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:25 +msgid "" +"If we go to :menuselection:`Accounting app --> Reporting --> Tax Report`, a " +"pop-up on line 81 explains that the amount will be carried over in the next " +"period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "" +"pop-up message stating the amount will be carried over to the next period" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst:32 +msgid "" +"At the time of the tax closing period, the tax report shows that the amount " +"was carried over from the previous period. It also indicates the amount that" +" will be carried over to this line in the next period based on the existing " +"transactions and the carryover from the previous period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_carryover.rst-1 +msgid "Illustration of the tax return" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:3 +msgid "Tax return (VAT declaration)" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:5 +msgid "" +"Companies with a registered :abbr:`VAT (Value Added Tax)` number must submit" +" a **tax return** on a monthly or quarterly basis, depending on their " +"turnover and the registration regulation. A tax return - or VAT return - " +"gives the tax authorities information about the taxable transactions made by" +" the company. The **output tax** is charged on the number of goods and " +"services sold by a business, while the **input tax** is the tax added to the" +" price when goods or services are purchased. Based on these values, the " +"company can calculate the tax amount they have to pay or be refunded." +msgstr "" +"บริษัทที่จดทะเบียนหมายเลข :abbr:`VAT (ภาษีมูลค่าเพิ่ม)` จะต้องส่ง " +"**การคืนภาษี** เป็นรายเดือนหรือรายไตรมาส " +"ขึ้นอยู่กับผลประกอบการและกฎระเบียบในการจดทะเบียน " +"การคืนภาษีหรือการคืนภาษีมูลค่าเพิ่มจะให้ข้อมูลเกี่ยวกับธุรกรรมที่ต้องเสียภาษีที่ทำโดยบริษัทแก่หน่วยงานภาษี" +" **ภาษีขาย** จะเรียกเก็บจากจำนวนสินค้าและบริการที่ธุรกิจขาย ในขณะที่ " +"**ภาษีซื้อ** คือภาษีที่เพิ่มเข้าไปในราคาเมื่อมีการซื้อสินค้าหรือบริการ " +"ตามค่าเหล่านี้ บริษัทสามารถคำนวณจำนวนภาษีที่ต้องชำระหรือขอคืนได้" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:14 +msgid "" +"You can find additional information about VAT and its mechanism on this page" +" from the European Commission: `\"What is VAT?\" " +"<https://ec.europa.eu/taxation_customs/business/vat/what-is-vat_en>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:20 +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:32 +msgid "Prerequisites" +msgstr "ข้อกำหนดเบื้องต้น" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:25 +msgid "Tax Return Periodicity" +msgstr "ระยะเวลาการคืนภาษี" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:27 +msgid "" +"The configuration of the **Tax Return Periodicity** allows Odoo to compute " +"your tax return correctly and also to send you a reminder to never miss a " +"tax return deadline." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:30 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"Under the :guilabel:`Tax Return Periodicity`, you can set:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:33 +msgid "" +":guilabel:`Periodicity`: define here whether you submit your tax return on a" +" monthly or quarterly basis;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:35 +msgid "" +":guilabel:`Reminder`: define when Odoo should remind you to submit your tax " +"return;" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:36 +msgid "" +":guilabel:`Journal`: select the journal in which to record the tax return." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure how often tax returns have to be made in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:43 +msgid "" +"This is usually configured during the :doc:`app's initial set up " +"<../get_started>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:48 +msgid "Tax Grids" +msgstr "ตารางภาษี" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:50 +msgid "" +"Odoo generates tax reports based on the :guilabel:`Tax Grids` settings that " +"are configured on your taxes. Therefore, it is crucial to make sure that all" +" recorded transactions use the right taxes. You can see the :guilabel:`Tax " +"Grids` by opening the :guilabel:`Journal Items` tab of any invoice and bill." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "see which tax grids are used to record transactions in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:59 +msgid "" +"To configure your tax grids, go to :menuselection:`Accounting --> " +"Configuration --> Taxes`, and open the tax you want to modify. There, you " +"can edit your tax settings, along with the tax grids that are used to record" +" invoices or credit notes." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Configure taxes and their tax grids in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:68 +msgid "" +"Taxes and reports are usually already pre-configured in Odoo: a :ref:`fiscal" +" localization package <fiscal_localizations/packages>` is installed " +"according to the country you select at the creation of your database." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:75 +msgid "Close a tax period" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:80 +msgid "Tax Lock Date" +msgstr "วันที่ล็อคภาษี" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:82 +msgid "" +"Any new transaction whose accounting date prior to the :guilabel:`Tax Lock " +"Date` has its tax values moved to the next open tax period. This is useful " +"to make sure that no change can be made to a report once its period is " +"closed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:86 +msgid "" +"Therefore, we recommend locking your tax date before working on your " +":guilabel:`Closing Journal Entry`. This way, other users cannot modify or " +"add transactions that would have an impact on the :guilabel:`Closing Journal" +" Entry`, which can help you avoid some tax declaration errors." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:91 +msgid "" +"To check the current :guilabel:`Tax Lock Date`, or to edit it, go to " +":menuselection:`Accounting --> Accounting --> Actions: Lock Dates`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "Lock your tax for a specific period in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:103 +msgid "" +"Once all the transactions involving taxes have been posted for the period " +"you want to report, open your :guilabel:`Tax Report` by going to " +":menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`. " +"Make sure to select the right period you want to declare by using the date " +"filter, this way you can have an overview of your tax report. From this " +"view, you can easily access different formats of your tax report, such as " +"`PDF` and XLSX. These include all the values to report to the tax " +"authorities, along with the amount you have to pay or be refunded." +msgstr "" +"เมื่อธุรกรรมทั้งหมดที่เกี่ยวข้องกับภาษีได้รับการโพสต์ในช่วงเวลาที่คุณต้องการรายงานแล้ว" +" ให้เปิด :guilabel:`รายงานภาษี` ของคุณโดยไปที่ :menuselection:`ระบบบัญชี -->" +" การรายงาน --> รายงานการตรวจสอบ: รายงานภาษี` " +"ตรวจสอบให้แน่ใจว่าได้เลือกช่วงเวลาที่ถูกต้องที่คุณต้องการประกาศโดยใช้ตัวกรองวันที่" +" ซึ่งจะทำให้คุณสามารถดูภาพรวมของรายงานภาษีของคุณได้ จากมุมมองนี้ " +"คุณสามารถเข้าถึงรายงานภาษีรูปแบบต่างๆ ของคุณ เช่น `PDF` และ XLSX " +"ได้อย่างง่ายดาย ซึ่งรวมถึงมูลค่าทั้งหมดที่ต้องรายงานต่อหน่วยงานด้านภาษี " +"พร้อมด้วยจำนวนเงินที่คุณต้องจ่ายหรือได้รับคืน" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst-1 +msgid "download the PDF with your Tax Report in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:115 +msgid "" +"If you forgot to lock your tax date before clicking on :guilabel:`Closing " +"Journal Entry`, then Odoo automatically locks your fiscal period on the same" +" date as the accounting date of your entry. This safety mechanism can " +"prevent some fiscal errors, but it is advised to lock your tax date manually" +" before, as described above." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:121 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:37 +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:117 +#: ../../content/applications/finance/accounting/taxes/retention.rst:42 +msgid ":doc:`../taxes`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/tax_returns.rst:122 +msgid ":doc:`../get_started`" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:3 +msgid "Year-end closing" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:5 +msgid "" +"Year-end closing is vital for maintaining financial accuracy, complying with" +" regulations, making informed decisions, and ensuring transparency in " +"reporting." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:11 +msgid "Fiscal years" +msgstr "ปีงบประมาณ" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:13 +msgid "" +"By default, the fiscal year is set to last 12 months and end on December " +"31st. However, its duration and end date can vary due to cultural, " +"administrative, and economic considerations." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:16 +msgid "" +"To modify these values, go to :menuselection:`Accounting --> Configuration " +"--> Settings`. Under the :guilabel:`Fiscal Periods` section, change the " +":guilabel:`Last Day` field if necessary." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:19 +msgid "" +"If the period lasts *more* than or *less* than 12 months, enable " +":guilabel:`Fiscal Years` and :guilabel:`Save`. Go back to the " +":guilabel:`Fiscal Periods` section and click :guilabel:`➜ Fiscal Years`. " +"From there, click :guilabel:`Create`, give it a :guilabel:`Name`, and both a" +" :guilabel:`Start Date` and :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:25 +msgid "" +"Once the set fiscal period is over, Odoo automatically reverts to the " +"default periodicity, taking into account the value specified in the " +":guilabel:`Last Day` field." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:31 +msgid "Year-end checklist" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:34 +msgid "Before closure" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:36 +msgid "" +"Before closing a fiscal year, ensure first everything is accurate and up-to-" +"date:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:38 +msgid "" +"Make sure all bank accounts are fully :doc:`reconciled " +"<../bank/reconciliation>` up to year-end, and confirm that the ending book " +"balances match the bank statement balances." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:40 +msgid "" +"Verify that all :doc:`customer invoices <../customer_invoices>` have been " +"entered and approved and that there are no draft invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:42 +msgid "" +"Confirm that all :doc:`vendor bills <../vendor_bills>` have been entered " +"and agreed upon." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:43 +msgid "" +"Validate all :doc:`expenses <../../expenses>`, ensuring their accuracy." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:44 +msgid "" +"Corroborate that all :doc:`received payments <../payments>` have been " +"encoded and recorded accurately." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:46 +msgid "Close all :ref:`suspense accounts <bank_accounts/suspense>`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:47 +msgid "" +"Book all :doc:`depreciation <../vendor_bills/assets>` and :doc:`deferred " +"revenue <../customer_invoices/deferred_revenues>` entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:51 +msgid "Closing a fiscal year" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:53 +msgid "Then, to close the fiscal year:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:55 +msgid "" +"Run a :ref:`tax report <reporting/tax-report>`, and verify that all tax " +"information is correct." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:56 +msgid "" +"Reconcile all accounts on the :ref:`balance sheet <reporting/balance-" +"sheet>`:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:58 +msgid "" +"Update the bank balances in Odoo according to the actual balances found on " +"the bank statements." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:59 +msgid "" +"Reconcile all transactions in the cash and bank accounts by running the " +":ref:`aged receivables <reporting/aged-receivable>` and :ref:`aged payables " +"<reporting/aged-payable>` reports." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:61 +msgid "" +"Audit all accounts, being sure to fully understand all transactions and " +"their nature, making sure to include loans and fixed assets." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:63 +msgid "" +"Optionally, run :ref:`payments matching <payments/matching>` to validate any" +" open vendor bills and customer invoices with their payments. While this " +"step is optional, it could assist the year-end closing process if all " +"outstanding payments and invoices are reconciled, potentially finding errors" +" or mistakes in the system." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:68 +msgid "" +"Next, the accountant likely verifies balance sheet items and book entries " +"for:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:70 +msgid "year-end manual adjustments," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:71 +msgid "work in progress," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:72 +msgid "depreciation journal entries," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:73 +msgid "loans," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:74 +msgid "tax adjustments," +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:75 +msgid "etc." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:77 +msgid "" +"If the accountant is going through the year-end audit, they may want to have" +" paper copies of all balance sheet items (such as loans, bank accounts, " +"prepayments, sales tax statements, etc.) to compare these with the balances " +"in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:82 +msgid "" +"During this process, it is good practice to set a :guilabel:`Journal Entries" +" Lock Date` to the last day (inclusive) of the preceding fiscal year by " +"going to :menuselection:`Accounting --> Accounting --> Lock Dates`. This " +"way, the accountant can be confident that nobody changes the transactions " +"while auditing the books. Users from the *accountant* access group can still" +" create and modify entries." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:89 +msgid "Current year's earnings" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:91 +msgid "" +"Odoo uses a unique account type called **current year's earnings** to " +"display the amount difference between the **income** and **expenses** " +"accounts." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:95 +msgid "" +"The chart of accounts can only contain one account of this type. By default," +" it is a 999999 account named :guilabel:`Undistributed Profits/Losses`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:98 +msgid "" +"To allocate the current year's earnings, create a miscellaneous entry to " +"book them to any equity account. Once done, confirm whether or not the " +"current year's earnings in the **balance sheet** is correctly reporting a " +"balance of zero. If that is the case, set an :guilabel:`All Users Lock Date`" +" to the last day of the fiscal year by going to :menuselection:`Accounting " +"--> Accounting --> Lock Dates`." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:105 +msgid "" +"Setting an :guilabel:`All Users Lock Date` is **irreversible** and cannot be" +" removed." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting/year_end.rst:108 +msgid "" +"A specific year-end closing entry is **optional** in order to close out the " +"**profit and loss statement**. The reports are created in real-time, meaning" +" that the profit and loss statement corresponds directly with the year-end " +"date specified in Odoo. Therefore, any time the **income statement** is " +"generated, the beginning date corresponds with the beginning of the **fiscal" +" year** and all account balances should equal zero." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:7 +msgid "" +"There are numerous types of **taxes**, and their application varies greatly," +" depending mostly on your company's localization. To make sure they are " +"recorded with accuracy, Odoo's tax engine supports all kinds of uses and " +"computations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:16 +msgid "" +"**Default taxes** define which taxes are automatically selected when " +"creating a new product. They are also used to prefill the :guilabel:`Taxes` " +"field when adding a new line on an invoice in :ref:`Accounting Firms " +"<fiduciaries>` mode." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "" +"Odoo fills out the Tax field automatically according to the Default Taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:23 +msgid "" +"To change your **default taxes**, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes --> Default Taxes`, select the " +"appropriate taxes for your default sales tax and purchase tax, and click on " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Define which taxes to use by default on Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:31 +msgid "" +"**Default taxes** are automatically set up according to the country selected" +" at the creation of your database, or when you set up a :ref:`fiscal " +"localization package <fiscal_localizations/packages>` for your company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:38 +msgid "Activate sales taxes from the list view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:40 +msgid "" +"As part of your :ref:`fiscal localization package " +"<fiscal_localizations/packages>`, most of your country's sales taxes are " +"already preconfigured on your database. However, only a few taxes are " +"activated by default. To activate taxes relevant to your business, go to " +":menuselection:`Accounting --> Configuration --> Taxes` and enable the " +"toggle button under the :guilabel:`Active` column." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Activate pre-configured taxes in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:53 +msgid "" +"To edit or create a **tax**, go to :menuselection:`Accounting --> " +"Configuration --> Taxes` and open a tax or click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Edition of a tax in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:60 +msgid "Basic options" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:65 +msgid "Tax name" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:67 +msgid "" +"The **tax name** is displayed for backend users in the :guilabel:`Taxes` " +"field in :doc:`sales orders <../../sales/sales>`, :doc:`invoices " +"<customer_invoices>`, product forms, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:73 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:306 +msgid "Tax computation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:75 +msgid "**Group of Taxes**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:77 +msgid "" +"The tax is a combination of multiple sub-taxes. You can add as many taxes as" +" you want, in the order you want them to be applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:81 +msgid "" +"Make sure that the tax sequence is correct, as the order in which they are " +"may impact the taxes' amounts computation, especially if one of the taxes " +":ref:`affects the base of the subsequent ones <taxes/base-subsequent>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:85 +msgid "**Fixed**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:87 +msgid "" +"The tax has a fixed amount in the default currency. The amount remains the " +"same, regardless of the sales price." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:91 +msgid "" +"A product has a sales price of $1000, and we apply a $10 *fixed* tax. We " +"then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Product sales price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Price without tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:92 +msgid "Tax" +msgstr "ภาษี" + +#: ../../content/applications/finance/accounting/taxes.rst:94 +#: ../../content/applications/finance/accounting/taxes.rst:109 +#: ../../content/applications/finance/accounting/taxes.rst:124 +#: ../../content/applications/finance/accounting/taxes.rst:268 +msgid "Total" +msgstr "รวม" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:127 +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "10" +msgstr "10" + +#: ../../content/applications/finance/accounting/taxes.rst:97 +msgid "1,010.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:100 +msgid "**Percentage of price**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:102 +msgid "" +"The *sales price* is the taxable basis: the tax amount is computed by " +"multiplying the sales price by the tax percentage." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:106 +msgid "" +"A product has a sales price of $1000, and we apply a *10% of Price* tax. We " +"then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:112 +msgid "1,100.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:115 +msgid "**Percentage of Price Tax Included**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:117 +msgid "" +"The **total** is the taxable basis: the tax amount is a percentage of the " +"total." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:120 +msgid "" +"A product has a Sales Price of $1000, and we apply a *10% of Price Tax " +"Included* tax. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:127 +msgid "1,111.11" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:130 +msgid "**Python code**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:132 +msgid "" +"A tax defined as **Python code** consists of two snippets of Python code " +"that are executed in a local environment containing data such as the unit " +"price, product or partner. :guilabel:`Python Code` defines the amount of the" +" tax, and :guilabel:`Applicable Code` defines if the tax is to be applied. " +"The formula is found at the bottom of the :guilabel:`Definition` tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:138 +msgid "" +":guilabel:`Python Code`: `result = price_unit * 0.10` :guilabel:`Applicable " +"Code`: `result = true`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:144 +msgid "Active" +msgstr "เปิดใช้งาน" + +#: ../../content/applications/finance/accounting/taxes.rst:146 +msgid "Only **active** taxes can be added to new documents." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:149 +msgid "" +"It is not possible to delete taxes that have already been used. Instead, you" +" can deactivate them to prevent future use." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:153 +msgid "" +"This field can be modified from the :ref:`list view " +"<taxes/list_activation>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:158 +msgid "Tax type" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:160 +msgid "" +"The :guilabel:`Tax Type` determines the tax application, which also " +"restricts where it is displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:162 +msgid "**Sales**: Customer invoices, product customer taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:163 +msgid "**Purchase**: Vendor bills, product vendor taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:164 +msgid "**None**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:167 +msgid "" +"You can use :guilabel:`None` for taxes that you want to include in a " +":ref:`Group of Taxes <taxes/computation>` but that you do not want to list " +"along with other sales or purchase taxes." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:171 +msgid "Tax scope" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:173 +msgid "" +"The :guilabel:`Tax Scope` restricts the use of taxes to a type of product, " +"either **goods** or **services**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:179 +msgid "Definition tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:181 +msgid "" +"Allocate with precision the amount of the taxable basis or percentages of " +"the computed tax to multiple accounts and tax grids." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "Allocate tax amounts to the right accounts and tax grids" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:187 +msgid "**Based On**:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:189 +msgid ":guilabel:`Base`: the price on the invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:190 +msgid ":guilabel:`% of tax`: a percentage of the computed tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:192 +msgid "**Account**: if defined, an additional journal item is recorded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:193 +msgid "" +"**Tax Grids**: used to generate :doc:`tax reports <reporting/tax_returns>` " +"automatically, according to your country's regulations." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:199 +msgid "Advanced options tab" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:204 +msgid "Label on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:206 +msgid "" +"The tax label is displayed on each invoice line in the :guilabel:`Taxes` " +"column. This is visible to *front-end* users on exported invoices, in " +"customer portals, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The label on invoices is displayed on each invoice line" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:215 +msgid "Tax group" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:217 +msgid "" +"Select which **tax group** the tax belongs to. The tax group name is the " +"displayed above the **total** line on exported invoices and in customer " +"portals." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:220 +msgid "" +"Tax groups include different iterations of the same tax. This can be useful " +"when you must record the same tax differently according to :doc:`fiscal " +"positions <taxes/fiscal_positions>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The Tax Group name is different from the Label on Invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:228 +msgid "" +"In the example above, the :guilabel:`0% EU S` tax for intra-community " +"customers in Europe records the amount on specific accounts and tax grids. " +"However, it remains a 0% tax to the customer. This is why the label " +"indicates :guilabel:`0% EU S`, and the tax group name above the " +":guilabel:`Total` line indicates :guilabel:`VAT 0%`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:234 +msgid "" +"Taxes have three different labels, each one having a specific use. Refer to " +"the following table to see where they are displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Name <taxes/name>`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Label on Invoice <taxes/label-invoices>`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:238 +msgid ":ref:`Tax Group <taxes/tax-group>`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Backend" +msgstr "การทำงานเบื้องหลัง" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid ":guilabel:`Taxes` column on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:241 +msgid "Above the :guilabel:`Total` line on exported invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:249 +msgid "Include in analytic cost" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:251 +msgid "" +"With this option activated, the tax amount is assigned to the same " +"**analytic account** as the invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:257 +msgid "Included in price" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:259 +msgid "" +"With this option activated, the total (including the tax) equals the **sales" +" price**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:261 +msgid "`Total = Sales Price = Computed Tax-Excluded price + Tax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:264 +msgid "" +"A product has a sales price of $1000, and we apply a *10% of Price* tax, " +"which is *included in the price*. We then have:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "900.10" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "90.9" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:271 +msgid "1,000.00" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:275 +msgid "" +"If you need to define prices accurately, both tax-included and tax-excluded," +" please refer to the following documentation: :doc:`taxes/B2B_B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:279 +msgid "" +"By default, only the :guilabel:`Tax excluded` column is displayed on " +"invoices. To display the :guilabel:`Tax included` column, click the " +"**dropdown toggle** button and check :guilabel:`Tax incl.`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:288 +msgid "Affect base of subsequent taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:290 +msgid "" +"With this option, the total tax-included becomes the taxable basis for the " +"other taxes applied to the same product." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:293 +msgid "" +"You can configure a new :ref:`group of taxes <taxes/computation>` to include" +" this tax or add it directly to a product line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst-1 +msgid "The eco-tax is taken into the basis of the 21% VAT tax" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:300 +msgid "" +"The order in which you add the taxes on a product line has no effect on how " +"amounts are computed. If you add taxes directly on a product line, only the " +"tax sequence determines the order in which they are applied." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:304 +msgid "" +"To reorder the sequence, go to :menuselection:`Accounting --> Configuration " +"--> Taxes`, and drag and drop the lines with the handles next to the tax " +"names." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:0 +msgid "The taxes' sequence in Odoo determines which tax is applied first" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:311 +msgid ":doc:`taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:312 +msgid ":doc:`taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:313 +msgid ":doc:`taxes/taxcloud`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:314 +msgid ":doc:`reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:3 +msgid "B2B (tax excluded) and B2C (tax included) pricing" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:5 +msgid "" +"When working with consumers, prices are usually expressed with taxes " +"included in the price (e.g., in most eCommerce). But, when you work in a B2B" +" environment, companies usually negotiate prices with taxes excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:9 +msgid "" +"Odoo manages both use cases easily, as long as you register your prices on " +"the product with taxes excluded or included, but not both together. If you " +"manage all your prices with tax included (or excluded) only, you can still " +"easily do sales order with a price having taxes excluded (or included): " +"that's easy." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:15 +msgid "" +"This documentation is only for the specific use case where you need to have " +"two references for the price (tax included or excluded), for the same " +"product. The reason of the complexity is that there is not a symmetrical " +"relationship with prices included and prices excluded, as shown in this use " +"case, in belgium with a tax of 21%:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:21 +msgid "Your eCommerce has a product at **10€ (taxes included)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:23 +msgid "This would do **8.26€ (taxes excluded)** and a **tax of 1.74€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:25 +msgid "" +"But for the same use case, if you register the price without taxes on the " +"product form (8.26€), you get a price with tax included at 9.99€, because:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:29 +msgid "**8.26€ \\* 1.21 = 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:31 +msgid "" +"So, depending on how you register your prices on the product form, you will " +"have different results for the price including taxes and the price excluding" +" taxes:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:35 +msgid "Taxes Excluded: **8.26€ & 10.00€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:37 +msgid "Taxes Included: **8.26€ & 9.99€**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:40 +msgid "" +"If you buy 100 pieces at 10€ taxes included, it gets even more tricky. You " +"will get: **1000€ (taxes included) = 826.45€ (price) + 173.55€ (taxes)** " +"Which is very different from a price per piece at 8.26€ tax excluded." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:45 +msgid "" +"This documentation explains how to handle the very specific use case where " +"you need to handle the two prices (tax excluded and included) on the product" +" form within the same company." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:50 +msgid "" +"In terms of finance, you have no more revenues selling your product at 10€ " +"instead of 9.99€ (for a 21% tax), because your revenue will be exactly the " +"same at 9.99€, only the tax is 0.01€ higher. So, if you run an eCommerce in " +"Belgium, make your customer a favor and set your price at 9.99€ instead of " +"10€. Please note that this does not apply to 20€ or 30€, or other tax rates," +" or a quantity >1. You will also make you a favor since you can manage " +"everything tax excluded, which is less error prone and easier for your " +"salespeople." +msgstr "" +"ในด้านการเงิน คุณไม่มีรายได้จากการขายผลิตภัณฑ์ของคุณที่ €10 อีกต่อไป " +"แทนที่จะเป็น €9.99 (สำหรับภาษี 21%) " +"เนื่องจากรายได้ของคุณจะเท่ากันทุกประการที่ €9.99 " +"มีเพียงภาษีเท่านั้นที่สูงกว่า €0.01 ดังนั้น " +"หากคุณดำเนินธุรกิจอีคอมเมิร์ซในประเทศเบลเยียม " +"ให้เอาใจลูกค้าและตั้งราคาไว้ที่ €9.99 แทนที่จะเป็น €10 " +"โปรดทราบว่าสิ่งนี้ใช้ไม่ได้กับ €20 หรือ €30 หรืออัตราภาษีอื่นๆ หรือปริมาณ >1" +" นอกจากนี้ " +"คุณยังจะช่วยเหลือคุณได้เนื่องจากคุณสามารถจัดการทุกอย่างที่ไม่รวมภาษีได้ " +"ซึ่งเกิดข้อผิดพลาดน้อยกว่าและง่ายกว่าสำหรับพนักงานขายของคุณ" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:63 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:413 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:10 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:27 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:6 +msgid "Introduction" +msgstr "แนะนำ" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:65 +msgid "" +"The best way to avoid this complexity is to choose only one way of managing " +"your prices and stick to it: price without taxes or price with taxes " +"included. Define which one is the default stored on the product form (on the" +" default tax related to the product), and let Odoo compute the other one " +"automatically, based on the pricelist and fiscal position. Negotiate your " +"contracts with customers accordingly. This perfectly works out-of-the-box " +"and you have no specific configuration to do." +msgstr "" +"วิธีที่ดีที่สุดในการหลีกเลี่ยงความซับซ้อนนี้คือการเลือกวิธีจัดการราคาของคุณเพียงวิธีเดียวและยึดถือราคานั้นไว้:" +" ราคาไม่รวมภาษี หรือราคารวมภาษี " +"กำหนดว่ารายการใดเป็นค่าเริ่มต้นที่จัดเก็บไว้ในแบบฟอร์มผลิตภัณฑ์ " +"(ตามภาษีเริ่มต้นที่เกี่ยวข้องกับผลิตภัณฑ์) และปล่อยให้ Odoo " +"คำนวณอีกรายการหนึ่งโดยอัตโนมัติ ตามรายการราคาและสถานะทางการเงิน " +"เจรจาสัญญาของคุณกับลูกค้าตามลำดับ " +"วิธีนี้ใช้งานได้อย่างสมบูรณ์แบบทันทีและคุณไม่มีการกำหนดค่าเฉพาะที่ต้องทำ" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:73 +msgid "" +"If you can not do that and if you really negotiate some prices with tax " +"excluded and, for other customers, others prices with tax included, you " +"must:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:77 +msgid "" +"always store the default price **tax excluded** on the product form, and " +"apply a tax (price excluded on the product form)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:80 +msgid "" +"create a pricelist with prices in **tax included**, for specific customers" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:83 +msgid "" +"create a fiscal position that switches the tax excluded to a tax included" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:86 +msgid "" +"assign both the pricelist and the fiscal position to customers who want to " +"benefit to this pricelist and fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:89 +msgid "For the purpose of this documentation, we will use the above use case:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:91 +msgid "your product default sale price is 8.26€ tax excluded" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:93 +msgid "" +"but we want to sell it at 10€, tax included, in our shops or eCommerce " +"website" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:99 +msgid "eCommerce" +msgstr "อีคอมเมิร์ซ" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:101 +msgid "" +"If you only use B2C or B2B prices on your website, simply select the " +"appropriate setting in the **Website** app settings." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:104 +msgid "" +"If you have both B2B and B2C prices on a single website, please follow these" +" instructions:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:106 +msgid "" +"Activate the :ref:`developer mode <developer-mode>` and go to " +":menuselection:`General Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:108 +msgid "" +"Open either `Technical / Tax display B2B` or `Technical / Tax display B2C`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:109 +msgid "" +"Under the :guilabel:`Users` tab, add the users requiring access to the price" +" type. Add B2C users in the B2C group and B2B users in the B2B group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:113 +msgid "Setting your products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:115 +msgid "" +"Your company must be configured with tax excluded by default. This is " +"usually the default configuration, but you can check your **Default Sale " +"Tax** from the menu :menuselection:`Configuration --> Settings` of the " +"Accounting application." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:123 +msgid "" +"Once done, you can create a **B2C** pricelist. You can activate the " +"pricelist feature per customer from the menu: :menuselection:`Configuration " +"--> Settings` of the Sale application. Choose the option **different prices " +"per customer segment**." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:128 +msgid "" +"Once done, create a B2C pricelist from the menu " +":menuselection:`Configuration --> Pricelists`. It's also good to rename the " +"default pricelist into B2B to avoid confusion." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:132 +msgid "" +"Then, create a product at 8.26€, with a tax of 21% (defined as tax not " +"included in price) and set a price on this product for B2C customers at 10€," +" from the :menuselection:`Sales --> Products` menu of the Sales application:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:141 +msgid "Setting the B2C fiscal position" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:143 +msgid "" +"From the accounting application, create a B2C fiscal position from this " +"menu: :menuselection:`Configuration --> Fiscal Positions`. This fiscal " +"position should map the VAT 21% (tax excluded of price) with a VAT 21% (tax " +"included in price)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:152 +msgid "Test by creating a quotation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:154 +msgid "" +"Create a quotation from the Sale application, using the " +":menuselection:`Sales --> Quotations` menu. You should have the following " +"result: 8.26€ + 1.73€ = 9.99€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:161 +msgid "" +"Then, create a quotation but **change the pricelist to B2C and the fiscal " +"position to B2C** on the quotation, before adding your product. You should " +"have the expected result, which is a total price of 10€ for the customer: " +"8.26€ + 1.74€ = 10.00€." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:169 +msgid "This is the expected behavior for a customer of your shop." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:172 +msgid "Avoid changing every sale order" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:174 +msgid "" +"If you negotiate a contract with a customer, whether you negotiate tax " +"included or tax excluded, you can set the pricelist and the fiscal position " +"on the customer form so that it will be applied automatically at every sale " +"of this customer." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:179 +msgid "" +"The pricelist is in the **Sales & Purchases** tab of the customer form, and " +"the fiscal position is in the accounting tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:182 +msgid "" +"Note that this is error prone: if you set a fiscal position with tax " +"included in prices but use a pricelist that is not included, you might have " +"wrong prices calculated for you. That's why we usually recommend companies " +"to only work with one price reference." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:3 +msgid "Avatax integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:5 +msgid "Avatax is a tax calculation provider that can be integrated in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:10 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:98 +msgid "Credential configuration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:12 +msgid "" +"To integrate Avatax with Odoo, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Taxes` and add your Avatax credentials in the" +" :guilabel:`Avatax` section." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:16 +msgid "" +"If you do not yet have credentials, click on :guilabel:`How to Get " +"Credentials`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Configure Avatax settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:25 +msgid "Tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:27 +msgid "" +"The Avatax integration is available on Sale Orders and Invoices with the " +"included Avatax fiscal position." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:30 +msgid "" +"Before using the integration, specify an :guilabel:`Avatax Category` on the " +"product categories." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Specify Avatax Category on products" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:36 +msgid "" +"Avatax Categories may be overridden or set on individual products as well." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Override product categories as needed" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:45 +msgid "Address validation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:47 +msgid "" +"Manually validate customer addresses by clicking the :guilabel:`Validate " +"address` link in the customer form view." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Validate customer addresses" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:54 +msgid "" +"If preferred, choose to keep the newly validated address or the original " +"address in the wizard that pops up." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst-1 +msgid "Address validation wizard" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:64 +msgid "Tax calculation" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:66 +msgid "" +"Automatically calculate taxes on Odoo quotations and invoices with Avatax by" +" confirming the documents. Alternatively, calculate the taxes manually by " +"clicking the :guilabel:`Compute taxes using Avatax` button while these " +"documents are in draft mode." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:70 +msgid "" +"Use the :guilabel:`Avalara Code` field that's available on customers, " +"quotations, and invoices to cross-reference data in Odoo and Avatax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/avatax.rst:74 +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:39 +msgid ":doc:`fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:3 +msgid "Cash basis taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:5 +msgid "" +"Cash basis taxes are due when the payment is made, as opposed to standard " +"taxes that are due when the invoice is confirmed. Reporting your income and " +"expenses to the government based on the cash basis method is mandatory in " +"some countries and under some conditions." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:10 +msgid "" +"You sell a product in the 1st quarter of your fiscal year, and the payment " +"is received in the 2nd quarter. Based on the cash basis method, the tax you " +"must pay is for the 2nd quarter." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:16 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings` and under " +"the :guilabel:`Taxes` section, enable :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:19 +msgid "" +"Then, define the :guilabel:`Tax Cash Basis Journal`. Click on the external " +"link button next to the journal to update its default properties such as the" +" :guilabel:`Journal Name`, :guilabel:`Type` or :guilabel:`Short Code`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "Select your Tax Cash Basis Journal and click on the external link" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:28 +msgid "" +"By default, the journal entries of the :guilabel:`Cash Basis Taxes` journal " +"are named using the :guilabel:`CABA` short code." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:31 +msgid "" +"Once this is done, go to :menuselection:`Accounting --> Configuration --> " +"Accounting: Taxes` to configure your taxes. You can either " +":guilabel:`Create` a new tax or update an existing one by clicking on it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:35 +msgid "" +"The :guilabel:`Account` column reflects the proper transitional accounts to " +"post taxes until the payment is registered." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the account column with a transitional accounts where taxes go until the payment\n" +"is registered" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:43 +msgid "" +"In the :guilabel:`Advanced Options` tab, decide of the :guilabel:`Tax " +"Exigilibity`. Select :guilabel:`Based on Payment`, so the tax is due when " +"the payment of the invoice is received. You can then also define the " +":guilabel:`Cash Basis Transition Account` where the tax amount is recorded " +"as long as the original invoice has not been reconciled." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst-1 +msgid "" +"Fill in the Cash Basis Transition Account where taxes amounts go until payment\n" +"reconciliation." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:54 +msgid "Impact of cash basis taxes on accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:56 +msgid "" +"To illustrate the impact of cash basis taxes on accounting transactions, " +"let's take an example with the sales of a product that costs 1,000$, with a " +"cash basis tax of 15%." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:63 +msgid "" +"The following entries are created in your accounting, and the tax report is " +"currently empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:66 +msgid "**Customer journal (INV)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:70 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:86 +msgid "Receivable $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:72 +msgid "Income $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:74 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:103 +msgid "Temporary tax account $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:77 +msgid "When the payment is then received, it is registered as below :" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:80 +msgid "**Bank journal (BANK)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:84 +msgid "Bank $1,150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:90 +msgid "" +"Once the payment is registered, you can use the :guilabel:`Cash Basis " +"Entries` smart button on the invoice to access them directly." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:93 +msgid "" +"Finally, upon reconciliation of the invoice with the payment, the below " +"entry is automatically created:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:97 +msgid "**Tax Cash Basis Journal (Caba)**" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:101 +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:105 +msgid "Income account $1,000" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:107 +msgid "Tax Received $150" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:110 +msgid "" +"The journal items :guilabel:`Income account` vs. :guilabel:`Income account` " +"are neutral, but they are needed to ensure correct tax reports in Odoo with " +"accurate base tax amounts." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/cash_basis.rst:113 +msgid "" +"Using a default :guilabel:`Base Tax Received Account` is recommended so your" +" balance is at zero and your income account is not polluted by unnecessary " +"accounting movements. To do so, go to :menuselection:`Configuration --> " +"Settings --> Taxes`, and select a :guilabel:`Base Tax Received Account` " +"under :guilabel:`Cash Basis`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:3 +msgid "EU intra-community distance selling" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:5 +msgid "" +"EU intra-community distance selling involves the cross-border trade of goods" +" and services from vendors registered for VAT purposes to individuals (B2C) " +"located in a European Union member state. The transaction is conducted " +"remotely, typically through online platforms, mail orders, telephone, or " +"other means of communication." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:10 +msgid "" +"EU intra-community distance selling is subject to specific VAT rules and " +"regulations. The vendor must charge VAT per the VAT rate applicable in the " +"buyer's country." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:14 +msgid "" +"This remains applicable even if the vendor is located outside of the " +"European Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:19 +msgid "" +"The **EU Intra-community Distance Selling** feature helps you comply with " +"this regulation by creating and configuring new **fiscal positions** and " +"**taxes** based on your company's country. To enable it, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, tick " +":guilabel:`EU Intra-community Distance Selling`, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "" +"EU intra-community Distance Selling feature in Odoo Accounting settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:28 +msgid "" +"Whenever you add or modify taxes, you can automatically update your fiscal " +"positions. To do so, go to :menuselection:`Accounting/Invoicing --> Settings" +" --> Taxes --> EU Intra-community Distance Selling` and click on the " +":guilabel:`Refresh tax mapping`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:33 +msgid "" +"We highly recommend checking that the proposed mapping is suitable for the " +"products and services you sell before using it." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:42 +msgid "One-Stop Shop (OSS)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:44 +msgid "" +"The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union " +"simplifies VAT collection for **cross-border** sales of goods and services. " +"It primarily applies to business-to-consumer **(B2C)** cases. With the OSS, " +"businesses can register for VAT in their home country and use a single " +"online portal to handle VAT obligations for their sales within the EU. There" +" are **two primary schemes**: the **Union OSS** scheme for cross-border " +"services and the **Import OSS** scheme for goods valued at or below €150." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:876 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 +msgid "Reports" +msgstr "รายงาน" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:54 +msgid "" +"To generate **OSS sales** or **OSS imports** reports and submit them onto " +"the OSS portal, go to :menuselection:`Accounting --> Reporting --> Tax " +"Report`, click :guilabel:`Report: Generic Tax report`, and select either " +":guilabel:`OSS Sales` or :guilabel:`OSS Imports`. Once selected, click on " +":guilabel:`PDF`, :guilabel:`XLSX`, or :guilabel:`XML` in the top-left " +"corner. This generates the currently-opened report in the selected format. " +"Once generated, log into the platform of your competent federal authority to" +" submit it onto the OSS portal." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst-1 +msgid "OSS reports view" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:65 +msgid "" +"`European Commission: OSS | Taxation and Customs Union " +"<https://ec.europa.eu/taxation_customs/business/vat/oss_en>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:3 +msgid "Fiscal positions (tax and account mapping)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:5 +msgid "" +"Default taxes and accounts are set on products and customers to create new " +"transactions on the fly. However, depending on the customers' and providers'" +" localization and business type, using different taxes and accounts for a " +"transaction might be necessary." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:9 +msgid "" +"**Fiscal positions** allow the creation of rules to adapt the taxes and " +"accounts used for a transaction automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:12 +msgid "" +"They can be applied :ref:`automatically <fiscal_positions/automatic>`, " +":ref:`manually <fiscal_positions/manual>`, or :ref:`assigned to a partner " +"<fiscal_positions/partner>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:16 +msgid "" +"Several default fiscal positions are available as part of your :ref:`fiscal " +"localization package <fiscal_localizations/packages>`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:25 +msgid "Tax and account mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:27 +msgid "" +"To edit or create a fiscal position, go to :menuselection:`Accounting --> " +"Configuration --> Fiscal Positions`, and open the entry to modify or click " +"on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:30 +msgid "" +"The mapping of taxes and accounts is based on the default taxes and accounts" +" defined in the product form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:33 +msgid "" +"To map to another tax or account, fill out the right column (:guilabel:`Tax " +"to Apply`/ :guilabel:`Account to Use Instead`)." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position's tax mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position's account mapping" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:44 +msgid "To remove a tax, leave the field :guilabel:`Tax to Apply` empty." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:45 +msgid "" +"To replace a tax with several other taxes, add multiple lines using the same" +" :guilabel:`Tax on Product`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:49 +msgid "" +"The mapping only works with *active* taxes. Therefore, make sure they are " +"active by going to :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:53 +msgid "Application" +msgstr "แอปพลิเคชัน" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:58 +msgid "Automatic application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:60 +msgid "" +"To automatically apply a fiscal position following a set of conditions, go " +"to :menuselection:`Accounting --> Configuration --> Fiscal Positions`, open " +"the fiscal position to modify, and tick :guilabel:`Detect Automatically`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:64 +msgid "From there, several conditions can be activated:" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:66 +msgid "" +":guilabel:`VAT Required`: the customer's VAT number must be present on their" +" contact form." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:67 +msgid "" +":guilabel:`Country Group` and :guilabel:`Country`: the fiscal position is " +"only applied to the selected country or country group." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Example of a fiscal position automatic application settings" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:75 +msgid "" +"If the :doc:`Verify VAT Numbers <vat_verification>` feature is enabled, any " +"fiscal positions with :guilabel:`VAT required` enabled will require Intra-" +"Community valid VAT numbers to apply automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:78 +msgid "" +"Taxes on **eCommerce orders** are automatically updated once the customer " +"has logged in or filled out their billing details." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:82 +msgid "" +"The fiscal positions' **sequence** defines which fiscal position is applied " +"if all conditions set on multiple fiscal positions are met simultaneously." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:85 +msgid "" +"For example, suppose the first fiscal position in a sequence targets " +"*country A* while the second fiscal position targets a *country group* that " +"comprises *country A*. In that case, only the first fiscal position will be " +"applied to customers from *country A*." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:92 +msgid "Manual application" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:94 +msgid "" +"To manually select a fiscal position, open a sales order, invoice, or bill, " +"go to the :guilabel:`Other Info` tab and select the desired " +":guilabel:`Fiscal Position` before adding product lines." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Selection of a fiscal position on a sales order, invoice, or bill" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:105 +msgid "Assign to a partner" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:107 +msgid "" +"To define which fiscal position must be used by default for a specific " +"partner, go to :menuselection:`Accounting --> Customers --> Customers`, " +"select the partner, open the :guilabel:`Sales & Purchase` tab, and select " +"the :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst-1 +msgid "Selection of a fiscal position on a customer" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/fiscal_positions.rst:118 +msgid ":doc:`B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:3 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:28 +msgid "Withholding taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:5 +msgid "" +"A **withholding tax**, also known as retention tax, mandates the payer of a " +"customer invoice to deduct a tax from the payment and remit it to the " +"government. Typically, a tax is included in the subtotal to calculate the " +"total amount paid, while withholding taxes are directly subtracted from the " +"payment." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:13 +msgid "" +"In Odoo, a withholding tax is defined by creating a negative tax. To create " +"one, go to :menuselection:`Accounting --> Configuration --> Taxes` and, in " +"the :guilabel:`Amount` field, enter a negative amount." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "negative tax amount in field" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:20 +msgid "" +"Then, go to the :menuselection:`Advanced Options` tab and create a retention" +" :guilabel:`Tax Group`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "tax group for retention tax." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:26 +msgid "" +"If the retention is a percentage of a regular tax, create a :guilabel:`Tax` " +"with a :guilabel:`Tax Computation` as a :guilabel:`Group of Taxes`. Then, " +"set both the regular tax and the retention one in the :guilabel:`Definition`" +" tab." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:31 +msgid "Retention taxes on invoices" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst:33 +msgid "" +"Once the retention tax has been created, it can be used on customer forms, " +"sales orders, and customer invoices. Several taxes can be applied on a " +"single customer invoice line." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/retention.rst-1 +msgid "invoice lines with taxes" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:3 +msgid "TaxCloud integration" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:6 +msgid "" +"The out-of-the-box Odoo TaxCloud integration has begun its decommissioning. " +"Starting in Odoo 17, new installations are prohibited, and in Odoo 18 the " +"TaxCloud module(s) won't exist at all. Odoo recommends the use of the Avatax" +" platform." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:10 +msgid "" +"If you are hosted on-premise or on Odoo.SH and you wish to use Taxcloud, you" +" can contact them directly `here <https://taxcloud.com/blog/odoo-" +"integration/>`_." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/taxcloud.rst:14 +msgid ":doc:`avatax`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:3 +msgid "VAT numbers verification (VIES)" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:5 +msgid "" +"`VAT Information Exchange System " +"<https://ec.europa.eu/taxation_customs/vies/#/vat-validation>`_, or " +"**VIES**, is a tool provided by the European Commission that allows you to " +"check the validity of VAT numbers for companies registered in the European " +"Union." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:9 +msgid "" +"Odoo's VAT Validation feature uses the VIES to verify your contacts' VAT " +"numbers directly from Odoo's interface." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:13 +msgid "" +"Regardless of whether or not the Verify VAT Numbers feature is enabled, Odoo" +" checks the format of a contact's VAT against the `expected format of VAT " +"numbers <https://en.wikipedia.org/wiki/VAT_identification_number>`_ from " +"that country." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:18 +msgid "VIES VAT number verification" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:20 +msgid "" +"To activate this feature, go to :menuselection:`Accounting --> Configuration" +" --> Settings`. In the :guilabel:`Taxes` section, enable the " +":guilabel:`Verify VAT Numbers` feature, and click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:24 +msgid "" +"Once the :guilabel:`Verify VAT Numbers` feature is enabled, if the contact's" +" :guilabel:`Tax ID` field is populated *and* its country is different from " +"your company's country, Odoo displays an :guilabel:`Intra-Community Valid` " +"checkbox. Odoo tests the VAT number through the VIES and automatically " +"checks or unchecks the :guilabel:`Intra-Community Valid` checkbox depending " +"on the validity of the VAT number." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst-1 +msgid "Intra-community valid checkbox on the contact record" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:34 +msgid "" +"It is possible to manually override the :guilabel:`Intra-Community Valid` " +"field on a contact in case the automatic VIES check is incorrect (for " +"example, if the company was recently created and its VAT is not yet in the " +"VIES). This change is logged in the chatter for transparency." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes/vat_verification.rst:39 +msgid "" +"Odoo can :ref:`automatically apply fiscal positions " +"<fiscal_positions/automatic>`. If the Verify VAT Numbers feature is enabled," +" any fiscal positions with VAT required enabled will require Intra-Community" +" valid VAT numbers to apply automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:5 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:279 +msgid "Vendor bills" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:7 +msgid "" +"In Odoo, we can register vendor bills **manually** or **automatically**, " +"while the **Aged Payable report** provides an overview of all outstanding " +"bills to help us pay the correct amounts on time." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:12 +msgid "" +"Tutorial `Registering a vendor bill " +"<https://www.odoo.com/slides/slide/registering-a-vendor-" +"bill-1683?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:13 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:16 +msgid "Bill creation" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:19 +msgid "Manually" +msgstr "ด้วยตนเอง" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:21 +msgid "" +"Create a vendor bill manually by going to :menuselection:`Accounting --> " +"Vendors --> Bills` and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:25 +msgid "Automatically" +msgstr "โดยอัตโนมัติ" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:27 +msgid "" +"Vendor bills can be automatically created by **sending an email** to an " +":ref:`email alias <invoice-digitization/email-alias>` associated with the " +"purchase journal, or by **uploading a PDF** in :menuselection:`Accounting " +"--> Vendors --> Bills` and then clicking :guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:32 +msgid "Bill completion" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:34 +msgid "" +"Whether the bill is created manually or automatically, make sure the " +"following fields are appropriately completed:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:37 +msgid "" +":guilabel:`Vendor`: Odoo automatically fills some information based on the " +"vendor's registered information, previous purchase orders, or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:39 +msgid "" +":guilabel:`Bill Reference`: add the sales order reference provided by the " +"vendor and is used to do the :ref:`matching <payments/matching>` when you " +"receive the products." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:41 +msgid "" +":guilabel:`Auto-Complete`: select a past bill/purchase order to " +"automatically complete the document. The :guilabel:`Vendor` field should be " +"completed prior to completing this field." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:43 +msgid ":guilabel:`Bill Date`: is the issuance date of the document." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:44 +msgid "" +":guilabel:`Accounting Date`: is the date on which the document is registered" +" in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:45 +msgid "" +":guilabel:`Payment Reference`: when registering the payment, it is " +"automatically indicated in the :guilabel:`Memo` field." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:47 +msgid "" +":guilabel:`Recipient Bank`: to indicate to which account number the payment " +"has to be made." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:48 +msgid ":guilabel:`Due Date` or :guilabel:`Terms` to pay the bill." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:49 +msgid "" +":guilabel:`Journal`: select in which journal the bill should be recorded and" +" the :doc:`Currency <get_started/multi_currency>`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst-1 +msgid "filling the vendor bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:57 +msgid "" +"Bills can be :doc:`digitized <vendor_bills/invoice_digitization>` for " +"automatic completion by clicking :guilabel:`Send for Digitization`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:59 +msgid "" +"If you upload the bill, the PDF document is displayed on the right of the " +"screen, allowing you to easily fill in the bill information." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:63 +msgid "Bill confirmation" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:65 +msgid "" +"Click :guilabel:`Confirm` when the document is completed. The status of your" +" document changes to :guilabel:`Posted` and a journal entry is generated " +"based on the configuration on the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:69 +msgid "" +"Once confirmed, it is no longer possible to update it. Click " +":guilabel:`Reset to draft` if changes are required." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:73 +msgid "Bill Payment" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:75 +msgid "" +"Upon payment of the vendor bill, click on :guilabel:`Register Payment`. A " +"new window pops up." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:77 +msgid "" +"Select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the " +":guilabel:`Amount` you wish to pay (full or partial payment), and the " +":guilabel:`Currency`. Odoo fills the :guilabel:`Memo` field automatically if" +" the :guilabel:`Payment Reference` has been set correctly in the vendor " +"bill. If the field is empty, we recommend you select the vendor invoice " +"number as a reference." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:82 +msgid "" +"Once confirmed, an :guilabel:`In Payment` banner appears on the bill until " +"it is :doc:`reconciled <bank/reconciliation>`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:86 +msgid "Aged payable report" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:88 +msgid "" +"To get an overview of your open vendor bills and their related due dates, " +"you can use the **Aged Payable report**. Go to :menuselection:`Accounting " +"--> Reporting --> Partner Reports: Aged payable`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:92 +msgid "" +"Click on a vendor's name to open up the details of all outstanding bills, " +"the amounts due, the due dates, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:96 +msgid "" +"By clicking the :guilabel:`Save` button, you can export the information " +"available on the screen as a PDF or XLSX file and save it in the folder of " +"your choice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills.rst:98 +msgid "" +"You might receive several bills for the same purchase order if your vendor " +"is in back-order and is sending you invoices as they ship the products, or " +"if your vendor is sending you a partial bill or asking for a deposit." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:3 +msgid "Non-current assets and fixed assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:5 +msgid "" +"**Non-current Assets**, also known as **long-term assets**, are investments " +"that are expected to be realized after one year. They are capitalized rather" +" than being expensed and appear on the company's balance sheet. Depending on" +" their nature, they may undergo **depreciation**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:9 +msgid "" +"**Fixed Assets** are a type of Non-current Assets and include the properties" +" bought for their productive aspects, such as buildings, vehicles, " +"equipment, land, and software." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:12 +msgid "" +"For example, let's say we buy a car for $ 27,000. We plan to amortize it " +"over five years, and we will sell it for $ 7,000 afterward. Using the " +"linear, or straight-line, depreciation method, $ 4,000 are expensed each " +"year as **depreciation expenses**. After five years, the **Accumulated " +"Depreciation** amount reported on the balance sheet equals $ 20,000, leaving" +" us with $ 7,000 of **Not Depreciable Value**, or Salvage value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:18 +msgid "" +"Odoo Accounting handles depreciation by creating all depreciation entries " +"automatically in *draft mode*. They are then posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:21 +msgid "Odoo supports the following **Depreciation Methods**:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:23 +msgid "Straight Line" +msgstr "วิธีเส้นตรง" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:24 +msgid "Declining" +msgstr "การลดลง" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:25 +msgid "Declining Then Straight Line" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:28 +msgid "" +"The server checks once a day if an entry must be posted. It might then take " +"up to 24 hours before you see a change from *draft* to *posted*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:34 +msgid "" +"Such transactions must be posted on an **Assets Account** rather than on the" +" default expense account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:38 +msgid "Configure an Assets Account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:40 +msgid "" +"To configure your account in the **Chart of Accounts**, go to " +":menuselection:`Accounting --> Configuration --> Chart of Accounts`, click " +"on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Configuration of an Assets Account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:48 +msgid "" +"This account's type must be either *Fixed Assets* or *Non-current Assets*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:51 +msgid "Post an expense to the right account" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:54 +msgid "Select the account on a draft bill" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:56 +msgid "" +"On a draft bill, select the right account for all the assets you are buying." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Selection of an Assets Account on a draft bill in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:65 +msgid "Choose a different Expense Account for specific products" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:67 +msgid "" +"Start editing the product, go to the *Accounting* tab, select the right " +"**Expense Account**, and save." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Change of the Assets Account for a product in Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:75 +msgid "" +"It is possible to :ref:`automate the creation of assets entries <assets-" +"automation>` for these products." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:81 +msgid "Change the account of a posted journal item" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:83 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, select the journal item you want to modify, " +"click on the account, and select the right one." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Modification of a posted journal item's account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:92 +msgid "Assets entries" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:97 +msgid "Create a new entry" +msgstr "สร้างรายการใหม่" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:99 +msgid "" +"An **Asset entry** automatically generates all journal entries in *draft " +"mode*. They are then posted one by one at the right time." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:102 +msgid "" +"To create a new entry, go to :menuselection:`Accounting --> Accounting --> " +"Assets`, click on *Create*, and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:105 +msgid "" +"Click on **select related purchases** to link an existing journal item to " +"this new entry. Some fields are then automatically filled out, and the " +"journal item is now listed under the **Related Purchase** tab." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets entry in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:113 +msgid "" +"Once done, you can click on *Compute Depreciation* (next to the *Confirm* " +"button) to generate all the values of the **Depreciation Board**. This board" +" shows you all the entries that Odoo will post to depreciate your asset, and" +" at which date." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Depreciation Board in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:122 +msgid "What does \"Prorata Temporis\" mean?" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:124 +msgid "" +"The **Prorata Temporis** feature is useful to depreciate your assets the " +"most accurately possible." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:126 +msgid "" +"With this feature, the first entry on the Depreciation Board is computed " +"based on the time left between the *Prorata Date* and the *First " +"Depreciation Date* rather than the default amount of time between " +"depreciations." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:130 +msgid "" +"For example, the Depreciation Board above has its first depreciation with an" +" amount of $ 241.10 rather than $ 4,000.00. Consequently, the last entry is " +"also lower and has an amount of $ 3758.90." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:134 +msgid "What are the different Depreciation Methods" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:136 +msgid "" +"The **Straight Line Depreciation Method** divides the initial Depreciable " +"Value by the number of depreciations planned. All depreciation entries have " +"the same amount." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:139 +msgid "" +"The **Declining Depreciation Method** multiplies the Depreciable Value by " +"the **Declining Factor** for each entry. Each depreciation entry has a lower" +" amount than the previous entry. The last depreciation entry doesn't use the" +" declining factor but instead has an amount corresponding to the balance of " +"the depreciable value so that it reaches $0 by the end of the specified " +"duration." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:144 +msgid "" +"The **Declining Then Straight Line Depreciation Method** uses the Declining " +"Method, but with a minimum Depreciation equal to the Straight Line Method. " +"This method ensures a fast depreciation at the beginning, followed by a " +"constant one afterward." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:149 +msgid "Assets from the Purchases Journal" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:151 +msgid "" +"You can create an asset entry from a specific journal item in your " +"**Purchases Journal**." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:153 +msgid "" +"To do so, open your Purchases Journal by going to :menuselection:`Accounting" +" --> Accounting --> Purchases`, and select the journal item you want to " +"record as an asset. Make sure that it is posted in the right account (see: " +":ref:`journal-assets-account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:157 +msgid "" +"Then, click on *Action*, select **Create Asset**, and fill out the form the " +"same way you would do to :ref:`create a new entry <create-assets-entry>`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Create Asset Entry from a journal item in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:165 +msgid "Modification of an Asset" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:167 +msgid "" +"You can modify the values of an asset to increase or decrease its value." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:169 +msgid "" +"To do so, open the asset you want to modify, and click on *Modify " +"Depreciation*. Then, fill out the form with the new depreciation values and " +"click on *Modify*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:172 +msgid "" +"A **decrease in value** posts a new Journal Entry for the **Value Decrease**" +" and modifies all the future *unposted* Journal Entries listed in the " +"Depreciation Board." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:175 +msgid "" +"An **increase in value** requires you to fill out additional fields related " +"to the account movements and creates a new Asset entry with the **Value " +"Increase**. The Gross Increase Asset Entry can be accessed with a Smart " +"Button." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Gross Increase smart button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:184 +msgid "Disposal of Fixed Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:186 +msgid "" +"To **sell** an asset or **dispose** of it implies that it must be removed " +"from the Balance Sheet." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:188 +msgid "" +"To do so, open the asset you want to dispose of, click on *Sell or Dispose*," +" and fill out the form." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Disposal of Assets in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:194 +msgid "" +"Odoo Accounting then generates all the journal entries necessary to dispose " +"of the asset, including the gain or loss on sale, which is based on the " +"difference between the asset's book value at the time of the sale and the " +"amount it is sold for." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:199 +msgid "" +"To record the sale of an asset, you must first post the related Customer " +"Invoice so you can link the sale of the asset with it." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:203 +msgid "Assets Models" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:205 +msgid "" +"You can create **Assets Models** to create your Asset entries faster. It is " +"particularly useful if you recurrently buy the same kind of assets." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:208 +msgid "" +"To create a model, go to :menuselection:`Accounting --> Configuration --> " +"Assets Models`, click on *Create*, and fill out the form the same way you " +"would do to create a new entry." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:212 +msgid "" +"You can also convert a *confirmed Asset entry* into a model by opening it " +"from :menuselection:`Accounting --> Accounting --> Assets` and then, by " +"clicking on the button *Save Model*." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:217 +msgid "Apply an Asset Model to a new entry" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:219 +msgid "" +"When you create a new Asset entry, fill out the **Fixed Asset Account** " +"with the right asset account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:222 +msgid "" +"New buttons with all the models linked to that account appear at the top of " +"the form. Clicking on a model button fills out the form according to that " +"model." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Assets model button in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:232 +msgid "Automate the Assets" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:234 +msgid "" +"When you create or edit an account of which the type is either *Non-current " +"Assets* or *Fixed Assets*, you can configure it to create assets for the " +"expenses that are credited on it automatically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:238 +msgid "You have three choices for the **Automate Assets** field:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:240 +msgid "**No:** this is the default value. Nothing happens." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:241 +msgid "" +"**Create in draft:** whenever a transaction is posted on the account, a " +"draft *Assets entry* is created, but not validated. You must first fill out " +"the form in :menuselection:`Accounting --> Accounting --> Assets`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:244 +msgid "" +"**Create and validate:** you must also select an Asset Model (see: `Assets " +"Models`_). Whenever a transaction is posted on the account, an *Assets " +"entry* is created and immediately validated." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst-1 +msgid "Automate Assets on an account in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:252 +msgid "" +"You can, for example, select this account as the default **Expense Account**" +" of a product to fully automate its purchase. (see: :ref:`product-assets-" +"account`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:256 +msgid ":doc:`../get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:3 +msgid "Deferred expenses" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:5 +msgid "" +"**Deferred expenses** and **prepayments** (also known as **prepaid " +"expenses**) are both costs that have already occurred for products or " +"services yet to be received." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:8 +msgid "" +"Such costs are **assets** for the company that pays them since it already " +"paid for products and services but has either not yet received them or not " +"yet used them. The company cannot report them on the current **profit and " +"loss statement**, or *income statement*, since the payments will be " +"effectively expensed in the future." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:13 +msgid "" +"These future expenses must be deferred on the company's balance sheet until " +"the moment in time they can be **recognized**, at once or over a defined " +"period, on the profit and loss statement." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:16 +msgid "" +"For example, let's say we pay $1200 at once for one year of insurance. We " +"already pay the cost now but haven't used the service yet. Therefore, we " +"post this new expense in a *prepayment account* and decide to recognize it " +"on a monthly basis. Each month, for the next 12 months, $100 will be " +"recognized as an expense." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:21 +msgid "" +"Odoo Accounting handles deferred expenses by spreading them across multiple " +"entries that are posted periodically." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:41 +msgid "" +"By default, Odoo :ref:`automatically generates " +"<vendor_bills/deferred/generate_on_validation>` the deferral entries when " +"you post a vendor bill. However, you can also choose to :ref:`generate them " +"manually <vendor_bills/deferred/generate_manually>` by selecting the " +":guilabel:`Manually & Grouped` option instead." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:46 +msgid "" +"Suppose a bill of $1200 must be deferred over 12 months. The " +":guilabel:`Equal per month` computation recognizes $100 each month, while " +"the :guilabel:`Based on days` computation recognizes different amounts " +"depending on the number of days in each month." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:56 +msgid "" +"Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are " +"visible in the :guilabel:`Invoice Lines` tab. In most cases, the " +":guilabel:`Start Date` should be in the same month as the :guilabel:`Bill " +"Date`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:60 +msgid "" +"For each line of the bill that should be deferred, specify the start and end" +" dates of the deferral period." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 +msgid "" +"If the :guilabel:`Generate Entries` field is set to :guilabel:`On " +"invoice/bill validation`, Odoo automatically generates the deferral entries " +"when the bill is validated. Click on the :guilabel:`Deferred Entries` smart " +"button to see them." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:67 +msgid "" +"One entry, dated on the same day as the bill, moves the bill amounts from " +"the expense account to the deferred account. The other entries are deferral " +"entries which will, month after month, move the bill amounts from the " +"deferred account to the expense account to recognize the expense." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:72 +msgid "" +"You can defer a January bill of $1200 over 12 months by specifying a start " +"date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800" +" is recognized as an expense, whereas $400 remains on the deferred account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:79 +msgid "" +"The deferred expense report computes an overview of the necessary deferral " +"entries for each account. To access it, go to :menuselection:`Accounting -->" +" Reporting --> Deferred Expense`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst-1 +msgid "Deferred expense report" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:89 +msgid "" +"Only bills whose accounting date is before the end of the period of the " +"report are taken into account." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:102 +msgid "" +"At the end of each month, go to the Deferred Expenses report and click the " +":guilabel:`Generate Entries` button. This generates two deferral entries:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:105 +msgid "" +"One dated at the end of the month which aggregates, for each account, all " +"the deferred amounts of that month. This means that at the end of that " +"period, a part of the deferred expense is recognized." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:113 +msgid "There are two bills:" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:115 +msgid "Bill A: $1200 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 +msgid "Bill B: $600 to be deferred from 01/01/2023 to 12/31/2023" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:124 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:141 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 +msgid "" +"Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both" +" bills)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:125 +msgid "" +"Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of bill A and " +"bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:142 +msgid "" +"Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of bill A and " +"bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:158 +msgid "" +"Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of bill A " +"and bill B)" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:165 +msgid "" +"There is no need to generate entries in December. Indeed, if we do the " +"computation for December, we will have an amount of 0 to be deferred." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:171 +msgid "bill A and bill B" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:175 +msgid "" +"Therefore, at the end of December, bills A and B are fully recognized as " +"expense only once in spite of all the created entries thanks to the reversal" +" mechanism." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:3 +msgid "AI-powered document digitization" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:5 +msgid "" +"**Invoice digitization** is the process of converting paper documents into " +"vendor bill and customer invoice forms in your accounting." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:8 +msgid "" +"Odoo uses :abbr:`OCR (optical character recognition)` and artificial " +"intelligence technologies to recognize the content of the documents. Vendor " +"bill and customer invoice forms are automatically created and populated " +"based on the scanned invoices." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:13 +msgid "" +"`Test Odoo's invoice digitization <https://www.odoo.com/app/invoice-" +"automation>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:14 +msgid "" +"`Odoo Tutorials: Invoice Digitization with OCR " +"<https://www.odoo.com/slides/slide/digitize-bills-with-ocr-1712>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:20 +msgid "" +"In :menuselection:`Accounting --> Configuration --> Settings --> " +"Digitization`, check the box :guilabel:`Document Digitization` and choose " +"whether :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` (this " +"includes customer credit notes) should be processed automatically or on " +"demand." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:25 +msgid "" +"If you enable the :guilabel:`Single Invoice Line Per Tax` option, only one " +"line is created per tax in the new bill, regardless of the number of lines " +"on the invoice." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:29 +msgid "Invoice upload" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:32 +msgid "Upload invoices manually" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:34 +msgid "" +"From the :guilabel:`Accounting Dashboard`, click on the :guilabel:`Upload` " +"button of your vendor bills journal. Alternatively, go to " +":menuselection:`Accounting --> Customers --> Invoices` or " +":menuselection:`Accounting --> Vendors --> Bills` and select " +":guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:42 +msgid "Upload invoices using an email alias" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:44 +msgid "" +"You can configure your connected scanner to send scanned documents to an " +"email alias. Emails sent to these aliases are converted into new draft " +"customer invoices or vendor bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:47 +msgid "" +"You can modify the email alias of a journal. To do so, go to the " +":guilabel:`Settings` app. Under :guilabel:`General Settings: Discuss`, " +"enable :guilabel:`Custom Email Servers`, add an :guilabel:`Alias Domain`, " +"and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:51 +msgid "" +"The email alias is now available in the :guilabel:`Advanced Settings` tab of" +" the journal. Emails sent to this address will be converted automatically " +"into new invoices or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:55 +msgid "" +"If you use the :doc:`Documents <../../documents>` app, you can automatically" +" send your scanned invoices to the :guilabel:`Finance` workspace (e.g., " +"`inbox-financial@example.odoo.com`)." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:58 +msgid "" +"The default email aliases `vendor-bills@` and `customer-invoices@` followed " +"by the :guilabel:`Alias Domain` you set are automatically created for the " +":guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` journals, " +"respectively. Emails sent to these addresses are converted automatically " +"into new invoices or bills." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:63 +msgid "" +"To change a default email alias, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`. Select the journal you want to " +"edit, click on the :guilabel:`Advanced Settings` tab, and edit the `Email " +"Alias`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:68 +msgid "Invoice digitization" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:70 +msgid "" +"According to your settings, the document is either processed automatically, " +"or you need to click on :guilabel:`Send for digitization` to do it manually." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:73 +msgid "" +"Once the data is extracted from the PDF, you can correct it if necessary by " +"clicking on the respective tags (available in :guilabel:`Edit` mode) and " +"selecting the proper information instead." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:77 +msgid "Data recognition with AI" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:79 +msgid "" +"It is essential to review and correct (if needed) the information uploaded " +"during digitization. Then, you have to post the document by clicking on " +":guilabel:`Confirm`. In this manner, the AI learns, and the system " +"identifies the correct data for future digitizations." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:86 +msgid "" +"The **invoice digitization** is an In-App Purchase (IAP) service that " +"requires prepaid credits to work. Digitizing one document consumes one " +"credit." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:89 +msgid "" +"To buy credits, go to :menuselection:`Accounting --> Configuration --> " +"Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to " +":menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My " +"Services`." +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:98 +msgid "`Our Privacy Policy <https://iap.odoo.com/privacy#header_6>`_" +msgstr "" + +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:99 +msgid ":doc:`/applications/general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:3 +msgid "Documents" +msgstr "เอกสาร" + +#: ../../content/applications/finance/documents.rst:5 +msgid "" +"**Odoo Documents** allows you to store, view, and manage files within Odoo." +msgstr "" + +#: ../../content/applications/finance/documents.rst:7 +msgid "" +"You can upload any file (max 64MB per file on Odoo Online) and organize them" +" in various workspaces." +msgstr "" + +#: ../../content/applications/finance/documents.rst:10 +msgid "`Odoo Documents: product page <https://www.odoo.com/app/documents>`_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:11 +msgid "" +"`Odoo Tutorials: Documents basics [video] " +"<https://www.odoo.com/slides/slide/documents-basics-674>`_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:13 +msgid "" +"`Odoo Tutorials: Using Documents with your Accounting App [video] " +"<https://www.odoo.com/slides/slide/using-documents-with-your-accounting-" +"app-675?fullscreen=1#>`_" +msgstr "" + +#: ../../content/applications/finance/documents.rst:18 +msgid "" +"By going to :menuselection:`Documents --> Configuration --> Settings`, you " +"can enable the centralization of files attached to a specific area of your " +"activity. For example, by ticking :guilabel:`Human Resources`, your HR " +"documents are automatically available in the HR workspace, while documents " +"related to Payroll are automatically available in the Payroll sub-workspace " +". You can change the default workspace using the dropdown menu and edit its " +"properties by clicking the internal link button (:guilabel:`➔`)." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "" +"Enable the centralization of files attached to a specific area of your " +"activity." +msgstr "" + +#: ../../content/applications/finance/documents.rst:29 +msgid "" +"If you enable the centralization of your accounting files and documents, it " +"is necessary to click on :guilabel:`Journals` and define each journal " +"independently to allow automatic synchronization." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "Enable the centralization of files attached to your accounting." +msgstr "" + +#: ../../content/applications/finance/documents.rst:36 +msgid "" +"If you select a new workspace, existing documents aren't moved. Only newly " +"created documents will be found under the new workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:40 +msgid "Workspaces" +msgstr "พื้นที่ทำงาน" + +#: ../../content/applications/finance/documents.rst:42 +msgid "" +"Workspaces are hierarchical folders having their own set of tags and " +":ref:`actions <documents/workflow-actions>`. Default workspaces exist, but " +"you can create your own by going to :menuselection:`Documents --> " +"Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page," +" fill in the following information:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:47 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:48 +msgid "" +":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select " +"its :guilabel:`Parent Workspace`" +msgstr "" + +#: ../../content/applications/finance/documents.rst:54 +msgid "" +"Tags are used within workspaces to add a level of differentiation between " +"documents. They are organized per category, and filters can be used to sort " +"them." +msgstr "" + +#: ../../content/applications/finance/documents.rst:57 +msgid "" +"Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a " +"line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." +msgstr "" + +#: ../../content/applications/finance/documents.rst:61 +msgid "" +"The tags of a parent workspace apply to the child workspaces automatically;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:62 +msgid "" +"Tags can be created and modified by going to :menuselection:`Configuration " +"--> Tags`;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:63 +msgid "" +"Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` " +"on the left menu." +msgstr "" + +#: ../../content/applications/finance/documents.rst:66 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/finance/documents.rst:68 +msgid "" +"To manage your workspace access rights, go to :menuselection:`Documents --> " +"Configuration --> Workspaces`, open the workspace you want to edit, and go " +"to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` " +"that can view, create, and edit the workspace's documents. You can also add " +":guilabel:`Read Groups` that can only view the workspace's documents." +msgstr "" + +#: ../../content/applications/finance/documents.rst:74 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/india.rst:18 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +msgid "Description" +msgstr "คำอธิบาย" + +#: ../../content/applications/finance/documents.rst:76 +msgid "" +"You can add descriptive information to your workspace by going to " +":menuselection:`Documents --> Configuration --> Workspaces`, opening the " +"workspace you want to describe and going to the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/finance/documents.rst:81 +msgid "" +"Workspaces can also be created and edited by clicking the gear icon " +":guilabel:`⚙` on the left menu." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "Create sub-workspaces from the left menu" +msgstr "" + +#: ../../content/applications/finance/documents.rst:88 +msgid "Documents management" +msgstr "" + +#: ../../content/applications/finance/documents.rst:90 +msgid "" +"When selecting or opening a document, the right panel displays different " +"options. On the top, additional options might be available: " +":guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, " +":guilabel:`Lock` or :guilabel:`Split`. It is also possible to " +":guilabel:`Open chatter` or :guilabel:`Archive` the document." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "right panel options" +msgstr "" + +#: ../../content/applications/finance/documents.rst:99 +msgid "" +"Then, you can modify the name of your file by clicking on " +":guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be " +"assigned. The related :guilabel:`Workspace` can be modified and it is " +"possible to access the related :guilabel:`Journal Entry` or add " +":guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:105 +msgid "" +"The :guilabel:`Contact` is the person related to the document and assigned " +"to it. He can only view the document and not modify it. I.e.: an existing " +"supplier in your database is the contact for their bill." +msgstr "" + +#: ../../content/applications/finance/documents.rst:108 +msgid "" +"The person who creates a document is, by default :guilabel:`Owner` of it and" +" has complete rights to it. It is possible to replace the owner of a " +"document. I.e., an employee must be owner of a document to be able to see it" +" in \"My Profile\"." +msgstr "" + +#: ../../content/applications/finance/documents.rst:112 +msgid "" +"Different :ref:`Actions <documents/workflow-actions>` are available at the " +"bottom of the right panel, depending on the workspace where your document is" +" stored." +msgstr "" + +#: ../../content/applications/finance/documents.rst:116 +msgid "Split PDF documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:118 +msgid "" +"Select the PDF you want to split, and click the scissors icon. A new view " +"displays all the pages of the document." +msgstr "" + +#: ../../content/applications/finance/documents.rst:121 +msgid "" +"By default, each page of the document will be split when clicking " +":guilabel:`Split`. To remove a split between two pages, click on the " +"scissors icon." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "split your documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:128 +msgid "" +"To merge documents from your dashboard, select them and click the scissors " +"icon. Click on the scissors between the two documents and click " +":guilabel:`Split` to merge the documents." +msgstr "" + +#: ../../content/applications/finance/documents.rst:132 +#: ../../content/applications/finance/payment_providers.rst:175 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/finance/documents.rst:134 +msgid "" +"Select a workspace and click the arrow next to the :guilabel:`Upload` button" +" to access additional features:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:138 +msgid "Request" +msgstr "คำร้องขอ" + +#: ../../content/applications/finance/documents.rst:140 +msgid "" +"You can create \"missing documents\" and organize them as documents, to " +"remind users to download them." +msgstr "" + +#: ../../content/applications/finance/documents.rst:142 +msgid "" +"Select the workspace where the file should be stored, click " +":guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document " +"Name`, select the person you need it from in the :guilabel:`Request To` " +"field, fill in the :guilabel:`Due Date In`, confirm the " +":guilabel:`Workspace`, the document should belong to, and add " +":guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click " +":guilabel:`Request`. A placeholder for the missing document is created in " +"the workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:149 +msgid "When your document is available, click the placeholder to upload it." +msgstr "" + +#: ../../content/applications/finance/documents.rst:151 +msgid "" +"You can see all missing documents by going to the **Activity** view and to " +"the :guilabel:`Requested Document` column." +msgstr "" + +#: ../../content/applications/finance/documents.rst:155 +msgid "" +"From the :guilabel:`Activity` view, you can send a **reminder email** to " +"users from whom you are expecting a document. Go to the :guilabel:`Requested" +" Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:159 +msgid "" +"Click on a date to see the details of a specific request. You can update it " +"by clicking on the pen icon, :guilabel:`Preview` the content of the reminder" +" email, or :guilabel:`Send Now` to send a reminder email." +msgstr "" + +#: ../../content/applications/finance/documents.rst:0 +msgid "send a reminder email from the Activity view" +msgstr "" + +#: ../../content/applications/finance/documents.rst:167 +msgid "Add a link" +msgstr "เพิ่มลิงก์" + +#: ../../content/applications/finance/documents.rst:169 +msgid "" +"To add a link to your documents dashboard, click on :guilabel:`Add a Link`, " +"enter the :guilabel:`URL`, and :guilabel:`Name` it." +msgstr "" + +#: ../../content/applications/finance/documents.rst:173 +msgid "Share" +msgstr "แชร์" + +#: ../../content/applications/finance/documents.rst:175 +msgid "" +"You can create a share link to a document or all documents of a workspace. " +"It allows anyone to download the file(s) or upload files to a workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:178 +msgid "" +"To do so, select the workspace or the document and click the arrow next to " +"the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the " +"share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with " +"anyone. :guilabel:`Name` the share link and set a validity date for the URL " +"by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include" +" Sub Folders` box if you also want to share a workspace's sub-folders. To " +"let users upload their own documents, select :guilabel:`Download and " +"Upload`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:186 +msgid "" +"It is possible to only share one or more documents (without their workspace)" +" by selecting them and clicking :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:190 +msgid "New spreadsheet" +msgstr "สเปรดชีตใหม่" + +#: ../../content/applications/finance/documents.rst:192 +msgid "" +"To create a new :doc:`spreadsheet <spreadsheet>`, click :guilabel:`New " +"Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an " +":doc:`existing template <spreadsheet/templates>`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:198 +msgid "Workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:200 +msgid "" +"Workflow actions help manage documents and overall business operations. " +"These are automated actions that can be created and customized for each " +"workspace. With a single click you can, for example, create, move, sign, and" +" add tags to a document, and process bills." +msgstr "" + +#: ../../content/applications/finance/documents.rst:204 +msgid "" +"These workflow actions appear on the right panel when a document meets the " +"set criteria." +msgstr "" + +#: ../../content/applications/finance/documents.rst:207 +msgid "Create workflow actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:209 +msgid "" +"To create workflow actions, go to :menuselection:`Documents --> " +"Configuration --> Actions` and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:213 +msgid "" +"An action applies to all **sub-workspaces** under the :guilabel:`Related " +"Workspace` you selected." +msgstr "" + +#: ../../content/applications/finance/documents.rst:216 +msgid "Set the conditions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:218 +msgid "" +"You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one." +" You can define the :guilabel:`Action Name` and then set the conditions that" +" trigger the appearance of the action button (:guilabel:`▶`) on the right-" +"side panel when selecting a file." +msgstr "" + +#: ../../content/applications/finance/documents.rst:222 +msgid "There are three basic types of conditions you can set:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:224 +msgid "" +":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does " +"not contain` conditions, meaning the files *must have* or *mustn't have* the" +" tags set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:227 +msgid "" +":guilabel:`Contact`: the files must be associated with the contact set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst:229 +msgid "" +":guilabel:`Owner`: the files must be associated with the owner set here." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's basic condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:235 +msgid "" +"If you don't set any conditions, the action button appears for all files " +"inside the selected workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:239 +msgid "Advanced condition type: domain" +msgstr "" + +#: ../../content/applications/finance/documents.rst:242 +msgid "" +"It is recommended to have some knowledge of Odoo development to configure " +"*Domain* filters properly." +msgstr "" + +#: ../../content/applications/finance/documents.rst:245 +msgid "" +"The :ref:`developer mode <developer-mode>` needs to be activated to access " +"the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once " +"done, select the :guilabel:`Domain` condition type and click :guilabel:`Add " +"condition`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:249 +msgid "" +"To create a rule, you typically select a :guilabel:`field`, an " +":guilabel:`operator`, and a :guilabel:`value`. For example, if you want to " +"add a workflow action to all the PDF files inside a workspace, set the " +":guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, " +"and the pdf :guilabel:`value`." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action's domain condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:257 +msgid "" +"Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add" +" conditions and sub-conditions. You can then specify if your rule should " +"match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the " +"rule directly using the :guilabel:`Code editor`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:262 +msgid "Configure the actions" +msgstr "" + +#: ../../content/applications/finance/documents.rst:264 +msgid "" +"Select the :guilabel:`Actions` tab to set up your action. You can " +"simultaneously:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:266 +msgid "" +"**Set Contact**: add a contact to the file, or replace an existing contact " +"with a new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:267 +msgid "" +"**Set Owner**: add an owner to the file, or replace an existing owner with a" +" new one." +msgstr "" + +#: ../../content/applications/finance/documents.rst:268 +msgid "**Move to Workspace**: move the file to any workspace." +msgstr "" + +#: ../../content/applications/finance/documents.rst:269 +msgid "" +"**Create**: create one of the following items attached to the file in your " +"database:" +msgstr "" + +#: ../../content/applications/finance/documents.rst:271 +msgid "" +"**Link to record**: link the document to a record (i.e. link to a vehicle in" +" Fleet);" +msgstr "" + +#: ../../content/applications/finance/documents.rst:272 +msgid "**Product template**: create a product you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:273 +msgid "**Task**: create a Project task you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:274 +msgid "**Signature PDF template**: create a new Sign template to send out;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:275 +msgid "**PDF to sign**: create a PDF to sign;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:276 +msgid "**Applicant**: create a new HR application you can edit directly;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:277 +msgid "" +"**Vendor bill**: create a vendor bill using OCR and AI to scrape information" +" from the file content;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:279 +msgid "" +"**Customer invoice**: create a customer invoice using OCR and AI to scrape " +"information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:281 +msgid "" +"**Vendor credit note**: create a vendor credit note using OCR and AI to " +"scrape information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:283 +msgid "" +"**Credit note**: create a customer credit note using OCR and AI to scrape " +"information from the file;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:285 +msgid "" +"**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous " +"Operations` in Accounting;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:287 +msgid "**Bank Statement**: create a Bank Statement in Finance;" +msgstr "" + +#: ../../content/applications/finance/documents.rst:288 +msgid "" +"**Expense**: create an expense automatically based on a file's content." +msgstr "" + +#: ../../content/applications/finance/documents.rst:290 +msgid "**Set Tags**: add, remove, and replace any number of tags." +msgstr "" + +#: ../../content/applications/finance/documents.rst:291 +msgid "" +"**Activities - Mark all as Done**: mark all activities linked to the file as" +" done." +msgstr "" + +#: ../../content/applications/finance/documents.rst:292 +msgid "" +"**Activities - Schedule Activity**: create a new activity linked to the file" +" as configured in the action. You can choose to set the activity on the " +"document owner." +msgstr "" + +#: ../../content/applications/finance/documents.rst-1 +msgid "Example of a workflow action Odoo Documents" +msgstr "" + +#: ../../content/applications/finance/documents.rst:299 +msgid "Digitize documents with AI and optical character recognition (OCR)" +msgstr "" + +#: ../../content/applications/finance/documents.rst:301 +msgid "" +"Documents available in the Finance workspace can be digitized. Select the " +"document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create " +"Customer Invoice`, or :guilabel:`Create credit note`, and then click " +":guilabel:`Send for Digitization`." +msgstr "" + +#: ../../content/applications/finance/documents.rst:306 +msgid "" +":doc:`AI-powered document digitization " +"<../finance/accounting/vendor_bills/invoice_digitization>`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:5 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:104 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:107 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:110 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:113 +msgid "Expenses" +msgstr "รายจ่าย" + +#: ../../content/applications/finance/expenses.rst:7 +msgid "" +"Odoo **Expenses** streamlines the management of expenses. After an employee " +"submits their expenses in Odoo, the expenses are reviewed by management and " +"accounting teams. Once approved, payments can then be processed and " +"disbursed back to the employee for reimbursement(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:12 +msgid "`Odoo Expenses: product page <https://www.odoo.com/app/expenses>`_" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:15 +msgid "Set expense categories" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:17 +msgid "" +"The first step to track expenses is to configure the different types of " +"expenses for the company (managed as *expense categories* in Odoo). Each " +"category can be as specific or generalized as needed. Go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories` to " +"view the current expensable categories in a default list view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Set expense costs on products." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:26 +msgid "" +"To create a new expense category, click :guilabel:`New`. A product form will" +" appear, with the description field labeled :guilabel:`Product Name`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:30 +msgid "" +"Expense categories are managed like products in Odoo. The expense category " +"form follows the standard product form in Odoo, and the information entered " +"is similar. Expense products will be referred to as expense categories " +"throughout this document since the main menu refers to these as " +":guilabel:`Expense Categories`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:35 +msgid "" +"Only two fields are required, the :guilabel:`Product Name` and the " +":guilabel:`Unit of Measure`. Enter the :guilabel:`Product Name` in the " +"field, and select the :guilabel:`Unit of Measure` from the drop-down menu " +"(most products will be set to :guilabel:`Units`)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:40 +msgid "" +"The *Sales* app is where specification on the units of measure are created " +"and edited (e.g. units, miles, nights, etc.). Go to :menuselection:`Sales " +"app --> Configuration --> Settings` and ensure `Units of Measure` is enabled" +" in the `Product Catalog` section. Click on the :guilabel:`Units of Measure`" +" internal link to :doc:`view, create, and edit the units of measure " +"<../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:50 +msgid "" +"The :guilabel:`Cost` field on the product form is populated with a value of " +"`0.00` by default. When a specific expense should always be reimbursed for a" +" particular price, enter that amount in the :guilabel:`Cost` field. " +"Otherwise, leave the :guilabel:`Cost` set to `0.00`, and employees will " +"report the actual cost when submitting an expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:56 +msgid "" +"The :guilabel:`Cost` field is always visible on the expense category form, " +"but the :guilabel:`Sales Price` field is *only* visible if the " +":guilabel:`Sales Price` is selected under the :guilabel:`Re-Invoice " +"Expenses` section. Otherwise, the :guilabel:`Sales Price` field is hidden." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:62 +msgid "" +"Here are some examples for when to set a specific :guilabel:`Cost` on a " +"product vs. leaving the :guilabel:`Cost` at `0.00`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:65 +msgid "" +"**Meals**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense for a meal, they enter the actual amount of the bill and will be " +"reimbursed for that amount. An expense for a meal costing $95.23 would equal" +" a reimbursement for $95.23." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:68 +msgid "" +"**Mileage**: Set the :guilabel:`Cost` to `0.30`. When an employee logs an " +"expense for \"mileage\", they enter the number of miles driven in the " +":guilabel:`Quantity` field, and are reimbursed 0.30 per mile they entered. " +"An expense for 100 miles would equal a reimbursement for $30.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:72 +msgid "" +"**Monthly Parking**: Set the :guilabel:`Cost` to `75.00`. When an employee " +"logs an expense for \"monthly parking\", the reimbursement would be for " +"$75.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:74 +msgid "" +"**Expenses**: Set the :guilabel:`Cost` to `0.00`. When an employee logs an " +"expense that is not a meal, mileage, or monthly parking, they use the " +"generic :guilabel:`Expenses` product. An expense for a laptop costing " +"$350.00 would be logged as an :guilabel:`Expenses` product, and the " +"reimbursement would be for $350.00." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:79 +msgid "" +"Select an :guilabel:`Expense Account` if using the Odoo *Accounting* app. It" +" is recommended to check with the accounting department to determine the " +"correct account to reference in this field as it will affect reports." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:83 +msgid "" +"Set a tax on each product in the :guilabel:`Vendor Taxes` and " +":guilabel:`Customer Taxes` fields, if applicable. It is considered good " +"practice to use a tax that is configured with :ref:`Tax Included in Price " +"<taxes/included-in-price>`. Taxes will be automatically configured if this " +"is set." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:90 +msgid "Record expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:93 +msgid "Manually create a new expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:95 +msgid "" +"To record a new expense, begin in the main :menuselection:`Expenses` app " +"dashboard, which presents the default :guilabel:`My Expenses` view. This " +"view can also be accessed from :menuselection:`Expenses app --> My Expenses " +"--> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:99 +msgid "" +"First, click :guilabel:`New`, and then fill out the various fields on the " +"form." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:101 +msgid "" +":guilabel:`Description`: Enter a short description for the expense in the " +":guilabel:`Description` field. This should be short and informative, such as" +" `lunch with client` or `hotel for conference`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:104 +msgid "" +":guilabel:`Category`: Select the expense category from the drop-down menu " +"that most closely corresponds to the expense. For example, an airplane " +"ticket would be appropriate for an expense :guilabel:`Category` named " +":guilabel:`Air Travel`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:107 +msgid "" +":guilabel:`Total`: Enter the total amount paid for the expense in one of two" +" ways:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:109 +msgid "" +"If the expense is for one single item/expense, and the category selected was" +" for a single item, enter the cost in the :guilabel:`Total` field (the " +":guilabel:`Quantity` field is hidden)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:111 +msgid "" +"If the expense is for multiples of the same item/expense with a fixed price," +" the :guilabel:`Unit Price` is displayed. Enter the quantity in the " +":guilabel:`Quantity` field, and the total cost is automatically updated with" +" the correct total (the :guilabel:`Unit Price` x the :guilabel:`Quantity` = " +"the total). Be advised, the word \"total\" does not appear, the total cost " +"simply appears below the :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:118 +msgid "" +"For example, in the case of mileage driven, the :guilabel:`Unit Price` is " +"populated as the cost *per mile*. Set the :guilabel:`Quantity` to the " +"*number of miles* driven, and the total is calculated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:122 +msgid "" +":guilabel:`Included Taxes`: If taxes were configured on the expense " +"category, the tax percentage and amount appear automatically after entering " +"either the :guilabel:`Total` or the :guilabel:`Quantity`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:127 +msgid "" +"When a tax is configured on an expense category, the :guilabel:`Included " +"Taxes` value will update in real time as the :guilabel:`Total` or " +":guilabel:`Quantity` is updated." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:130 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee this " +"expense is for." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:131 +msgid "" +":guilabel:`Paid By`: Click the radio button to indicate who paid for the " +"expense and should be reimbursed. If the employee paid for the expense (and " +"should be reimbursed) select :guilabel:`Employee (to reimburse)`. If the " +"company paid directly instead (e.g. if the company credit card was used to " +"pay for the expense) select :guilabel:`Company`. Depending on the expense " +"category selected, this field may not appear." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:136 +msgid "" +":guilabel:`Bill Reference`: If there is any reference text that should be " +"included for the expense, enter it in this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:138 +msgid "" +":guilabel:`Expense Date`: Using the calendar module, enter the date the " +"expense was incurred. Use the :guilabel:`< (left)` and :guilabel:`> (right)`" +" arrows to navigate to the correct month, then click on the specific day to " +"enter the selection." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:141 +msgid "" +":guilabel:`Account`: Select the expense account that this expense should be " +"logged on from the drop-down menu." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:143 +msgid "" +":guilabel:`Customer to Reinvoice`: If the expense is something that should " +"be paid for by a customer, select the :abbr:`SO (Sales Order)` and customer " +"that will be invoiced for this expense from the drop-down menu. All sales " +"orders in the drop-down menu list both the :abbr:`SO (Sales Order)` as well " +"as the company the sales order is written for, but after the expense is " +"saved, the customer name disappears and only the :abbr:`SO (Sales Order)` is" +" visible on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:150 +msgid "" +"A customer wishes to have an on-site meeting for a custom garden (design and" +" installation) and agrees to pay for the expenses associated with it (such " +"as travel, hotel, meals, etc.). All expenses tied to that meeting would " +"indicate the sales order for the custom garden (which also references the " +"customer) as the :guilabel:`Customer to Reinvoice`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:155 +msgid "" +":guilabel:`Analytic Distribution`: Select the account(s) the expense should " +"be written against from the drop-down menu for either :guilabel:`Projects`, " +":guilabel:`Departments`, or both. Multiple accounts can be listed for each " +"category if needed. Adjust the percentage for each analytic account by " +"typing in the percentage value next to the account." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:159 +msgid "" +":guilabel:`Company`: If multiple companies are set up, select the company " +"this expense should be filed for from the drop-down menu. The current " +"company will automatically populate this field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:161 +msgid "" +":guilabel:`Notes...`: If any notes are needed in order to clarify the " +"expense, enter them in the notes field." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "A filled in expense form for a client lunch." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:169 +msgid "Attach a receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:171 +msgid "" +"After the expense is created, the next step is to attach a receipt. Click " +"the :guilabel:`Attach Receipt` button, and a file explorer appears. Navigate" +" to the receipt to be attached, and click :guilabel:`Open`. The new receipt " +"is recorded in the chatter, and the number of receipts will appear next to " +"the :guilabel:`📎 (paperclip)` icon beneath the expense form. More than one " +"receipt can be attached to an individual expense, as needed. The number of " +"receipts attached to the expense will be noted on the paperclip icon." +msgstr "" +"หลังจากสร้างค่าใช้จ่ายแล้ว ขั้นตอนต่อไปคือการแนบใบเสร็จรับเงิน คลิกปุ่ม " +":guilabel:`แนบใบเสร็จ` จากนั้นโปรแกรมสำรวจไฟล์จะปรากฏขึ้น " +"ไปที่ใบเสร็จที่จะแนบ และคลิก :guilabel:`เปิด` " +"ใบเสร็จใหม่จะถูกบันทึกไว้ในการแชท และจำนวนใบเสร็จจะปรากฏถัดจากไอคอน " +":guilabel:`📎 (คลิปหนีบกระดาษ)` ใต้แบบฟอร์มค่าใช้จ่าย " +"สามารถแนบใบเสร็จรับเงินมากกว่าหนึ่งใบเข้ากับค่าใช้จ่ายส่วนบุคคลได้ตามต้องการ" +" จำนวนใบเสร็จที่แนบมากับค่าใช้จ่ายจะระบุไว้ที่ไอคอนคลิปหนีบกระดาษ" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Attach a receipt and it appears in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:183 +msgid "Create new expenses from a scanned receipt" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:185 +msgid "" +"Rather than manually inputting all of the information for an expense, " +"expenses can be created by scanning a PDF receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:188 +msgid "" +"First, in the main :guilabel:`Expenses` app dashboard view (this view can " +"also be accessed from :menuselection:`Expenses app --> My Expenses --> My " +"Expenses`), click :guilabel:`Scan`, and a file explorer pops up. Navigate to" +" the receipt to be uploaded, click on it to select it, and then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Create an expense by scanning a receipt. Click Scan at the top of the Expenses dashboard\n" +"view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:198 +msgid "" +"The receipt is scanned, and a new entry is created with today's date as the " +":guilabel:`Expense Date`, and any other fields it can populate based on the " +"scanned data, such as the total. Click on the new entry to open the " +"individual expense form, and make any changes needed. The scanned receipt " +"appears in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:204 +msgid "Automatically create new expenses from an email" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:206 +msgid "" +"Instead of individually creating each expense in the *Expenses* app, " +"expenses can be automatically created by sending an email to an email alias." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:209 +msgid "" +"To do so, first, an email alias needs to be configured. Go to " +":menuselection:`Expenses app --> Configuration --> Settings`. Ensure " +":guilabel:`Incoming Emails` is enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Create the domain alias by clicking the link." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:217 +msgid "" +"If the domain alias needs to be set up, :guilabel:`Setup your domain alias` " +"will appear beneath the incoming emails check box instead of the email " +"address field. Refer to this documentation for setup instructions and more " +"information: :doc:`/administration/maintain/domain_names`. Once the domain " +"alias is configured, the email address field will be visible beneath the " +"incoming emails section." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:223 +msgid "" +"Next, enter the email address to be used in the email field, and then click " +":guilabel:`Save`. Now that the email address has been entered, emails can be" +" sent to that alias to create new expenses without having to be in the Odoo " +"database." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:227 +msgid "" +"To submit an expense via email, create a new email and enter the product's " +"*internal reference* code (if available) and the amount of the expense in " +"the email subject. Next, attach the receipt to the email. Odoo creates the " +"expense by taking the information in the email subject and combining it with" +" the receipt." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:232 +msgid "" +"To check an expense categories internal reference, go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`. If " +"an internal reference is listed on the expense category, it is listed in the" +" :guilabel:`Internal Reference` column." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Internal reference numbers are listed in the main Expense Categories view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:240 +msgid "" +"To add an internal reference on an expense category, click on the category " +"to open the form. Enter the internal reference in the field. Beneath the " +":guilabel:`Internal Reference` field, this sentence appears: :guilabel:`Use " +"this reference as a subject prefix when submitting by email.`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Internal reference numbers are listed in the main Expense Products view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:249 +msgid "" +"For security purposes, only authenticated employee emails are accepted by " +"Odoo when creating an expense from an email. To confirm an authenticated " +"employee email address, go to the employee card in the " +":menuselection:`Employees` app, and refer to the :guilabel:`Work Email`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:258 +msgid "" +"If submitting an expense via email for a $25.00 meal during a work trip, the" +" email subject would be `FOOD $25.00`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:261 +msgid "Explanation:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:263 +msgid "" +"The :guilabel:`Internal Reference` for the expense category `Meals` is " +"`FOOD`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:264 +msgid "The :guilabel:`Cost` for the expense is `$25.00`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:269 +msgid "Create an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:271 +msgid "" +"When expenses are ready to submit (such as at the end of a business trip, or" +" once a month), an *expense report* needs to be created. Go to the main " +":menuselection:`Expenses` app dashboard, which displays a default " +":guilabel:`My Expenses` view, or go to :menuselection:`Expenses app --> My " +"Expenses --> My Expenses`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:276 +msgid "" +"Expenses are color coded by status. Any expense with a status of " +":guilabel:`To Report` (expenses that still need to be added to an expense " +"report) the text appears in blue. All other statuses (:guilabel:`To Submit`," +" :guilabel:`Submitted`, and :guilabel:`Approved`) the text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:280 +msgid "" +"First, select each individual expense for the report by clicking the check " +"box next to each entry, or quickly select all the expenses in the list by " +"clicking the check box next to :guilabel:`Expense Date`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:284 +msgid "" +"Another way to quickly add all expenses that are not on an expense report is" +" to click :guilabel:`Create Report` without selecting any expenses, and Odoo" +" will select all expenses with a status of :guilabel:`To Submit` that are " +"not already on a report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the expenses to submit, then create the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:293 +msgid "" +"Any expense can be selected from the :guilabel:`My Expenses` list, " +"regardless of status. The :guilabel:`Create Report` button is visible as " +"long as there is a minimum of 1 expense with a status of :guilabel:`To " +"Report` selected. When the :guilabel:`Create Report` button is clicked, only" +" expenses with a status of :guilabel:`To Submit` that are *not* currently on" +" another expense report will appear in the newly created expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:299 +msgid "" +"Once the expenses have been selected, click the :guilabel:`Create Report` " +"button. The new report appears with all the expenses listed in the " +":guilabel:`Expense` tab. If there is a receipt attached to an individual " +"expense, a :guilabel:`📎 (paperclip)` icon appears next to the " +":guilabel:`Customer to Reinvoice` and :guilabel:`Analytic Distribution` " +"columns." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:304 +msgid "" +"When the report is created, the date range for the expenses appears in the " +":guilabel:`Expense Report Summary` field by default. It is recommended to " +"edit this field with a short summary for each report to help keep expenses " +"organized. Enter a short description for the expense report (such as `Client" +" Trip NYC`, or `Repairs for Company Car`) in the :guilabel:`Expense Report " +"Summary` field. Next, select a :guilabel:`Manager` from the drop-down menu " +"to assign a manager to review the report. If needed, the :guilabel:`Journal`" +" can be changed. Use the drop-down menu to select a different " +":guilabel:`Journal`." +msgstr "" +"เมื่อสร้างรายงาน ช่วงวันที่สำหรับค่าใช้จ่ายจะปรากฏในฟิลด์ " +":guilabel:`สรุปรายงานค่าใช้จ่าย` ตามค่าเริ่มต้น " +"ขอแนะนำให้แก้ไขช่องนี้โดยสรุปสั้นๆ " +"สำหรับแต่ละรายงานเพื่อช่วยจัดระเบียบค่าใช้จ่าย ป้อนคำอธิบายสั้นๆ " +"สำหรับรายงานค่าใช้จ่าย (เช่น `การเดินทางของลูกค้าที่ NYC` หรือ " +"`การซ่อมแซมรถยนต์ของบริษัท`) ในช่อง :guilabel:`สรุปรายงานค่าใช้จ่าย` " +"จากนั้นเลือก :guilabel:`ผู้จัดการ` " +"จากเมนูแบบเลื่อนลงเพื่อมอบหมายให้ผู้จัดการตรวจสอบรายงาน หากจำเป็น " +"สามารถเปลี่ยน :guilabel:`สมุดรายวัน` ได้ ใช้เมนูแบบเลื่อนลงเพื่อเลือก " +":guilabel:`สมุดรายวัน` อื่น" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Enter a short description and select a manager for the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:316 +msgid "" +"If some expenses are not on the report that should be, they can still be " +"added. Click :guilabel:`Add a line` at the bottom of the :guilabel:`Expense`" +" tab. A pop up appears with all the available expenses that can be added to " +"the report (with a status of :guilabel:`To Submit`). Click the check box " +"next to each expense to add, then click :guilabel:`Select`. The items now " +"appear on the report that was just created. If a new expense needs to be " +"added that does *not* appear on the list, click :guilabel:`New` to create a " +"new expense and add it to the report." +msgstr "" +"หากค่าใช้จ่ายบางส่วนไม่อยู่ในรายงานที่ควรจะเป็น ก็ยังสามารถเพิ่มได้ คลิก " +":guilabel:`เพิ่มบรรทัด` ที่ด้านล่างของแท็บ :guilabel:`บัญชีรายจ่าย` " +"ป๊อปอัปจะแสดงขึ้นพร้อมกับค่าใช้จ่ายที่มีอยู่ทั้งหมดที่สามารถเพิ่มลงในรายงานได้" +" (โดยมีสถานะเป็น :guilabel:`ส่ง`) " +"คลิกช่องทำเครื่องหมายถัดจากค่าใช้จ่ายแต่ละรายการที่ต้องการเพิ่ม จากนั้นคลิก " +":guilabel:`เลือก` ขณะนี้รายการแสดงในรายงานที่เพิ่งสร้างขึ้น " +"หากจำเป็นต้องเพิ่มค่าใช้จ่ายใหม่ที่ไม่ *ไม่* ปรากฏในรายการ ให้คลิก " +":guilabel:`สร้าง` เพื่อสร้างค่าใช้จ่ายใหม่และเพิ่มลงในรายงาน" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Add more expenses to the report before submitting." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:328 +msgid "Expense reports can be created in one of three places:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:330 +msgid "" +"Go to the main :menuselection:`Expenses` app dashboard (also accessed by " +"going to :menuselection:`Expenses app --> My Expenses --> My Expenses`)" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:332 +msgid "Go to :menuselection:`Expenses app --> My Expenses --> My Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:333 +msgid "Go to :menuselection:`Expenses app --> Expense Reports`" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:335 +msgid "" +"In any of these views, click :guilabel:`New` to create a new expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:340 +msgid "Submit an expense report" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:342 +msgid "" +"When an expense report is completed, the next step is to submit the report " +"to a manager for approval. Reports must be individually submitted, and " +"cannot be submitted in batches. Open the specific report from the list of " +"expense reports (if the report is not already open). To view all expense " +"reports, go to :menuselection:`Expenses app --> My Expenses --> My Reports`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:347 +msgid "" +"If the list is large, grouping the results by status may be helpful since " +"only reports that have a :guilabel:`To Submit` status need to be submitted, " +"reports with an :guilabel:`Approved` or :guilabel:`Submitted` status do not." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:351 +msgid "" +"The :guilabel:`To Submit` expenses are easily identifiable not just from the" +" :guilabel:`To Submit` status, but the text appears in blue, while the other" +" expenses text appears in black." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Submit the report to the manager." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:359 +msgid "" +"The status of each report is shown in the :guilabel:`Status` column on the " +"right. If the :guilabel:`Status` column is not visible, click the " +":guilabel:`Additional Options (two dots)` icon at the end of the row, and " +"enable :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:363 +msgid "" +"Click on a report to open it, then click :guilabel:`Submit To Manager`. " +"After submitting a report, the next step is to wait for the manager to " +"approve it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:367 +msgid "" +"The :ref:`expenses/approve`, :ref:`expenses/post`, and " +":ref:`expenses/reimburse` sections are **only** for users with the " +"*necessary rights*." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:373 +msgid "Approve expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:375 +msgid "" +"In Odoo, not just anyone can approve expense reports— only users with the " +"necessary rights (or permissions) can. This means that a user must have at " +"least *Team Approver* rights for the *Expenses* app. Employees with the " +"necessary rights can review expense reports, approve or reject them, and " +"provide feedback thanks to the integrated communication tool." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:380 +msgid "" +"To see who has rights to approve, go to the main :menuselection:`Settings` " +"app and click on :guilabel:`Manage Users`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:384 +msgid "" +"If the *Settings* app is not available, then certain rights are not set on " +"the account. Check the :guilabel:`Access Rights` tab of a user's card in the" +" :menuselection:`Settings` app. the :guilabel:`Administration` section " +"(bottom right of the :guilabel:`Access Rights` tab) is set to one of three " +"options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:389 +msgid "" +":guilabel:`None (blank)`: The user cannot access the *Settings* app at all." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:390 +msgid "" +":guilabel:`Access Rights`: The user can only view the :guilabel:`User's & " +"Companies` section of the *Settings* app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:392 +msgid "" +":guilabel:`Settings`: The user has access to the entire *Settings* app with " +"no restrictions." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:394 +msgid "" +"Please refer to :doc:`this document " +"</applications/general/users/manage_users>` to learn more about managing " +"users and their access rights." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:397 +msgid "" +"Click on an individual to view their card, which displays the " +":guilabel:`Access Rights` tab in the default view. Scroll down to the " +":guilabel:`Human Resources` section. Under :guilabel:`Expenses`, there are " +"four options:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:401 +msgid "" +":guilabel:`None (blank)`: A blank field means the user has no rights to view" +" or approve expense reports, and can only view their own." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:403 +msgid "" +":guilabel:`Team Approver`: The user can only view and approve expense " +"reports for their own specific team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:405 +msgid "" +":guilabel:`All Approver`: The user can view and approve any expense report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:406 +msgid "" +":guilabel:`Administrator`: The user can view and approve any expense report," +" as well as access the reporting and configuration menus in the *Expenses* " +"app." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:409 +msgid "" +"Users who are able to approve expense reports (typically managers) can " +"easily view all expense reports they have access rights to. Go to " +":menuselection:`Expenses app --> Expense Reports`, and a list appears with " +"all expense reports that have a status of either :guilabel:`To Submit`, " +":guilabel:`Submitted`, :guilabel:`Approved`, :guilabel:`Posted`, or " +":guilabel:`Done`. Expense reports with a status of :guilabel:`Refused` are " +"hidden in the default view." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Reports to validate are found on the Reports to Approve page." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:419 +msgid "" +"When viewing expense reports, there is a panel of filters that can be " +"enabled or disabled on the left side. The three categories that filters can " +"be applied on are :guilabel:`Status`, :guilabel:`Employee`, and " +":guilabel:`Company`. To view only expense reports with a particular status, " +"enable the specific status filter to display the expense reports with only " +"that status. Disable the specific status filter to hide the reports with " +"that status. To view expense reports for a particular employee and/or " +"company, enable the specific employee name filter and/or company filter in " +"the :guilabel:`Employee` and :guilabel:`Company` sections." +msgstr "" +"เมื่อดูรายงานค่าใช้จ่าย " +"จะมีแผงตัวกรองที่สามารถเปิดหรือปิดใช้งานได้ทางด้านซ้าย " +"สามหมวดหมู่ที่สามารถใช้ตัวกรองได้คือ :guilabel:`สถานะ`, " +":guilabel:`ข้อมูลพนักงาน` และ :guilabel:`บริษัท` " +"หากต้องการดูเฉพาะรายงานค่าใช้จ่ายที่มีสถานะเฉพาะ " +"ให้เปิดใช้งานตัวกรองสถานะเฉพาะเพื่อแสดงรายงานค่าใช้จ่ายที่มีเฉพาะสถานะนั้น " +"ปิดใช้งานตัวกรองสถานะเฉพาะเพื่อซ่อนรายงานที่มีสถานะนั้น " +"หากต้องการดูรายงานค่าใช้จ่ายสำหรับพนักงานและ/หรือบริษัทใดโดยเฉพาะ " +"ให้เปิดใช้งานตัวกรองชื่อพนักงานและ/หรือตัวกรองบริษัทในส่วน " +":guilabel:`ข้อมูลพนักงาน` และ :guilabel:`บริษัท`" + +#: ../../content/applications/finance/expenses.rst:427 +msgid "" +"Reports can be approved in two ways (individually or several at once) and " +"refused only one way. To approve multiple expense reports at once, remain in" +" the list view. First, select the reports to approve by clicking the check " +"box next to each report, or click the box next to :guilabel:`Employee` to " +"select all the reports in the list." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:433 +msgid "" +"Only reports with a status of :guilabel:`Submitted` can be approved. It is " +"recommended to only display the submitted reports by adjusting the status " +"filter on the left side by only having the :guilabel:`Submitted` filter " +"enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:437 +msgid "" +"If a report is selected that is unable to be approved, the " +":guilabel:`Approve Report` button **will not appear**, indicating there is a" +" problem with the selected report(s)." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:440 +msgid "Next, click the :guilabel:`Approve Report` button." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Approve multiple reports by clicking the checkboxes next to each report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:446 +msgid "" +"To approve an individual report, click on a report to go to a detailed view " +"of that report. In this view, several options are presented: " +":guilabel:`Approve`, :guilabel:`Report in Next Payslip`, :guilabel:`Refuse`," +" or :guilabel:`Reset to draft`. Click :guilabel:`Approve` to approve the " +"report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:450 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to Refuse Expense` " +"field, and then click :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +#: ../../content/applications/finance/expenses.rst:0 +msgid "Send messages in the chatter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:457 +msgid "" +"Team managers can easily view all the expense reports for their team " +"members. While in the :guilabel:`Expense Reports` view, click the drop-down " +"arrow in the right-side of the search box, and click on :guilabel:`My Team` " +"in the :guilabel:`Filters` section. This presents all the reports for the " +"manager's team." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Select the My Team filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:467 +msgid "" +"If more information is needed, such as a missing receipt, communication is " +"easy from the chatter. In an individual report, simply click :guilabel:`Send" +" message` to open the message text box. Type in a message, tagging the " +"proper person (if needed), and post it to the chatter by clicking " +":guilabel:`Send`. The message is posted in the chatter, and the person " +"tagged will be notified via email of the message, as well as any followers." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:473 +msgid "" +"The only people that can be tagged in a message are *followers*. To see who " +"is a follower, click on the :guilabel:`👤 (person)` icon to display the " +"followers of the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:483 +msgid "Post expenses in accounting" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:485 +msgid "" +"Once an expense report is approved, the next step is to post the report to " +"the accounting journal. To view all expense reports, go to " +":menuselection:`Expenses app --> Expense Reports`. To view only the expense " +"reports that have been approved and need to be posted, adjust the filters on" +" the left side so that only the :guilabel:`Approved` status is enabled." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to post by clicking on expense reports, then reports to post." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:494 +msgid "" +"Just like approvals, expense reports can be posted in two ways (individually" +" or several at once). To post multiple expense reports at once, remain in " +"the list view. First, select the reports to post by clicking the check box " +"next to each report, or click the box next to :guilabel:`Employee` to select" +" all the reports in the list. Next, click :guilabel:`Post Entries`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Post multiple reports at a time from the Expense Reports view, with the " +"Approved filter." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:503 +msgid "" +"To post an individual report, click on a report to go to the detailed view " +"of that report. In this view, several options are presented: :guilabel:`Post" +" Journal Entries`, :guilabel:`Report In Next Payslip`, :guilabel:`Refuse`, " +"or :guilabel:`Reset to Draft`. Click :guilabel:`Post Journal Entries` to " +"post the report." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:508 +msgid "" +"If :guilabel:`Refuse` is clicked, a pop-up window appears. Enter a brief " +"explanation for the refusal in the :guilabel:`Reason to Refuse Expense` " +"field, and then click :guilabel:`Refuse`. Refused reports can be viewed by " +"going to :menuselection:`Expenses app --> Expense Reports`, then adjusting " +"the filters on the left so that only :guilabel:`Refused` is selected. This " +"will only show the refused expense reports." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:515 +msgid "" +"To post expense reports to an accounting journal, the user must have " +"following access rights:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:517 +msgid "Accounting: Accountant or Adviser" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:518 +msgid "Expenses: Manager" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:523 +msgid "Reimburse employees" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:525 +msgid "" +"After an expense report is posted to an accounting journal, the next step is" +" to reimburse the employee. To view all the expense reports to pay, go to " +":menuselection:`Expenses app --> Expense Reports --> Reports To Pay`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"View reports to pay by clicking on expense reports, then reports to pay." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:533 +msgid "" +"Just like approvals and posting, expense reports can be paid in two ways " +"(individually or several at once). To pay multiple expense reports at once, " +"remain in the list view. First, select the reports to pay by clicking the " +"check box next to each report, or click the box next to :guilabel:`Employee`" +" to select all the reports in the list. Next, click :guilabel:`Register " +"Payment`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Post multiple reports by selecting them, clicking the gear, and then post " +"the entries." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:542 +msgid "" +"To pay an individual report, click on a report to go to a detailed view of " +"that report. Click :guilabel:`Register Payment` to pay the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:545 +msgid "" +"A :guilabel:`Register Payment` pop-up appears, and the :guilabel:`Journal`, " +":guilabel:`Payment Method`, and :guilabel:`Payment Date` can be modified, if" +" needed. When the selections are correct, click :guilabel:`Create Payment` " +"to send the payment to the employee." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:549 +msgid "" +"To pay an individual report, click on a report in the list view to go to a " +"detailed view of that report. Click :guilabel:`Register Payment` to pay the " +"employee. A :guilabel:`Register Payment` pop-up appears, but when paying an " +"individual expense report instead of several at once, more options appear in" +" the pop-up. In addition to the :guilabel:`Journal`, :guilabel:`Payment " +"Method`, and :guilabel:`Payment Date` fields, a :guilabel:`Recipient Bank " +"Account`, :guilabel:`Amount`, and :guilabel:`Memo` field appear. Select the " +"employee's bank account from the drop-down menu to directly deposit the " +"payment to their account. When all other selections are correct, click " +":guilabel:`Create Payment` to send the payment to the employee." +msgstr "" +"หากต้องการชำระเงินรายงานแต่ละรายการ " +"ให้คลิกที่รายงานในมุมมองรายการเพื่อไปยังมุมมองโดยละเอียดของรายงานนั้น คลิก " +":guilabel:`ลงทะเบียนการชำระเงิน` เพื่อจ่ายเงินให้กับพนักงาน ป๊อปอัป " +":guilabel:`ลงทะเบียนการชำระเงิน` จะปรากฏขึ้น " +"แต่เมื่อชำระเงินรายงานค่าใช้จ่ายแต่ละรายการแทนที่จะชำระหลายรายการในคราวเดียว" +" ตัวเลือกเพิ่มเติมจะปรากฏขึ้นในป๊อปอัป นอกเหนือจากฟิลด์ " +":guilabel:`สมุดรายวัน`, :guilabel:`วิธีการชำระเงิน` และ " +":guilabel:`วันที่ชำระเงิน` แล้ว ยังมี :guilabel:`บัญชีธนาคารของผู้รับ`, " +":guilabel:`จำนวน` และ :guilabel: ช่อง \"บันทึก\" ปรากฏขึ้น " +"เลือกบัญชีธนาคารของพนักงานจากเมนูแบบเลื่อนลงเพื่อฝากเงินเข้าบัญชีโดยตรง " +"เมื่อการเลือกอื่นๆ ทั้งหมดถูกต้อง คลิก :guilabel:`สร้างการชำระเงิน` " +"เพื่อส่งการชำระเงินให้กับพนักงาน" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"Different options appear when registering an individual expense report versus multiple\n" +"expense reports at once." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:564 +msgid "Re-invoice expenses to customers" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:566 +msgid "" +"If expenses are tracked on customer projects, expenses can be automatically " +"charged back to the customer. This is done by creating an expense, " +"referencing the :abbr:`SO (Sales Order)` the expense should be added to, and" +" then creating the expense report. Next, managers approve the expense " +"report, and the accounting department posts the journal entries. Finally, " +"once the expense report is posted to a journal, the expense(s) appears on " +"the :abbr:`SO (Sales Order)` that was referenced. The sales order can then " +"be invoiced, thus invoicing the customer for the expense." +msgstr "" +"หากมีการติดตามค่าใช้จ่ายในโปรเจ็กต์ของลูกค้า " +"ค่าใช้จ่ายจะถูกเรียกเก็บกลับไปยังลูกค้าโดยอัตโนมัติ " +"ซึ่งทำได้โดยการสร้างค่าใช้จ่ายโดยอ้างอิง :abbr:`SO (ใบสั่งขาย)` " +"ควรเพิ่มค่าใช้จ่ายเข้าไป จากนั้นจึงสร้างรายงานค่าใช้จ่าย ถัดไป " +"ผู้จัดการอนุมัติรายงานค่าใช้จ่าย และแผนกบัญชีจะผ่านรายการสมุดรายวัน " +"สุดท้ายนี้ เมื่อรายงานค่าใช้จ่ายถูกผ่านรายการไปยังสมุดรายวัน " +"ค่าใช้จ่ายจะปรากฏบน :abbr:`SO (ใบสั่งขาย)` ที่ถูกอ้างอิง " +"ใบสั่งขายสามารถออกใบแจ้งหนี้ได้ " +"ดังนั้นการออกใบแจ้งหนี้ให้กับลูกค้าสำหรับค่าใช้จ่าย" + +#: ../../content/applications/finance/expenses.rst:574 +#: ../../content/applications/finance/fiscal_localizations/india.rst:55 +#: ../../content/applications/finance/fiscal_localizations/india.rst:195 +msgid "Setup" +msgstr "ตั้งค่า" + +#: ../../content/applications/finance/expenses.rst:576 +msgid "" +"First, specify the invoicing policy for each expense category. Go to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`. " +"Click on the expense category to open the expense category form. Under the " +":guilabel:`Invoicing` section, click the radio button next to the desired " +"selection for :guilabel:`Re-Invoicing Expenses`. Options are " +":guilabel:`None`, :guilabel:`At cost`, and :guilabel:`Sales price`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:582 +msgid ":guilabel:`Re-Invoicing Expenses`:" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:584 +msgid ":guilabel:`None`: Expense category will not be re-invoiced." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:585 +msgid "" +":guilabel:`At cost`: Expense category will invoice expenses at their real " +"cost." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:586 +msgid "" +":guilabel:`At sales price`: Expense category will invoice the price set on " +"the sale order." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:589 +msgid "Create an expense" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:591 +msgid "" +"First, when :ref:`creating a new expense <expenses/new>`, the correct " +"information needs to be entered in order to re-invoice a customer. Select " +"the *sales order* the expense will appear on in the :guilabel:`Customer to " +"Reinvoice` section, from the drop-down menu. Next, select the " +":guilabel:`Analytic Account` the expense will be posted to. After the " +"expense(s) are created, the expense report needs to be :ref:`created " +"<expenses/report>` and :ref:`submitted <expenses/submit>` as usual." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "Ensure the customer to be invoiced is called out on the expense." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:603 +msgid "" +"Selecting a :guilabel:`Customer to Reinvoice` when creating an expense is " +"critical, since this is what causes the expenses to be automatically " +"invoiced after an expense report is approved." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:606 +msgid "" +"The :guilabel:`Customer to Reinvoice` field can be modified *until an " +"expense report is* **approved**, then the field is no longer able to be " +"modified." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:610 +msgid "Validate and post expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:612 +msgid "" +"Only employees with permissions (typically managers or supervisors) can " +":ref:`approve expenses <expenses/approve>`. Before approving an expense " +"report, ensure the :guilabel:`Analytic Distribution` is set on every expense" +" line of a report. If an :guilabel:`Analytic Distribution` is missing, " +"assign the correct account(s) from the drop-down menu, and then click " +":guilabel:`Approve` or :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:618 +msgid "" +"The accounting department is typically responsible for :ref:`posting journal" +" entries <expenses/post>`. Once an expense report is approved, it can then " +"be posted. The :abbr:`SO (Sales Order)` is **only** updated *after the " +"journal entries are posted*. One the journal entries are posted, the " +"expenses now appear on the referenced :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:624 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/finance/expenses.rst:626 +msgid "" +"Once the :abbr:`SO (Sales Order)` has been updated, it is time to invoice " +"the customer. After the expense report has been approved and the journal " +"entries have been posted, click the :guilabel:`Sales Orders` smart button to" +" open the :abbr:`SO (Sales Order)`. The expenses to be re-invoiced are now " +"on the :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "" +"After the expense report is posted to the journal entry, the sales order can be called up\n" +"by clicking on the sales order number." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:637 +msgid "" +"More than one :abbr:`SO (Sales Order)` can be referenced on an expense " +"report. If more than one :abbr:`SO (Sales Order)` is referenced, the " +":guilabel:`Sales Orders` smart button will list the number of :abbr:`SO " +"(Sales Order)`'s. If multiple :abbr:`SO (Sales Order)`'s are listed, the " +":guilabel:`Sales Orders` smart button opens a list view of all the :abbr:`SO" +" (Sales Order)`'s on the expense report. Click on a :abbr:`SO (Sales Order)`" +" to open the individual :abbr:`SO (Sales Order)`." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:644 +msgid "" +"The expenses are listed in the :abbr:`SO (Sales Order)` :guilabel:`Order " +"Lines` tab." +msgstr "" + +#: ../../content/applications/finance/expenses.rst-1 +msgid "See the expenses listed on the sales order after clicking into it." +msgstr "" + +#: ../../content/applications/finance/expenses.rst:650 +msgid "" +"Next, click :guilabel:`Create Invoice`, and select if the invoice is for a " +":guilabel:`Regular invoice`, a :guilabel:`Down payment (percentage)`, or a " +":guilabel:`Down payment (fixed amount)` by clicking the radio button next to" +" it. Then, click :guilabel:`Create Invoice`. The customer has now been " +"invoiced for the expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:5 +msgid "Fiscal localizations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:10 +msgid "Fiscal localization packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:12 +msgid "" +"**Fiscal Localization Packages** are country-specific modules that install " +"pre-configured taxes, fiscal positions, chart of accounts, and legal " +"statements on your database. Some additional features, such as the " +"configuration of specific certificates, are also added to your Accounting " +"app, following your fiscal administration requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:18 +msgid "" +"Odoo continuously adds new localizations and improves the existing packages." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:23 +msgid "" +"Odoo automatically installs the appropriate package for your company, " +"according to the country selected at the creation of the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:27 +msgid "" +"As long as you haven't posted any entry, you can still select another " +"package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:29 +msgid "" +"To select a fiscal localization package for your company, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Fiscal " +"Localization`, select the appropriate package from the list and save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst-1 +msgid "Select your country's fiscal localization package in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:37 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Use" +msgstr "ใช้" + +#: ../../content/applications/finance/fiscal_localizations.rst:39 +msgid "" +"These packages require you to fine-tune your chart of accounts according to " +"your needs, activate the taxes you use, and configure your country-specific " +"statements and certifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:43 +msgid ":doc:`accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:44 +msgid ":doc:`accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:49 +msgid "List of supported countries" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:51 +msgid "" +"Odoo Accounting can be used in many countries out of the box by installing " +"the appropriate module. Here is a list of all :ref:`fiscal localization " +"package <fiscal_localizations/packages>` that are available on Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:55 +msgid "Algeria - Accounting" +msgstr "ประเทศแอลจีเรีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:56 +msgid ":doc:`Argentina - Accounting <fiscal_localizations/argentina>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:57 +msgid ":doc:`Australian - Accounting <fiscal_localizations/australia>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:58 +msgid ":doc:`Austria - Accounting <fiscal_localizations/austria>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:59 +msgid ":doc:`Belgium - Accounting <fiscal_localizations/belgium>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:60 +msgid "Bolivia - Accounting" +msgstr "ประเทศโบลิเวีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:61 +msgid ":doc:`Brazilian - Accounting <fiscal_localizations/brazil>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:62 +msgid "Canada - Accounting" +msgstr "ประเทศแคนาดา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:63 +msgid ":doc:`Chile - Accounting <fiscal_localizations/chile>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:64 +msgid "China - Accounting" +msgstr "ประเทศจีน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:65 +msgid ":doc:`Colombia - Accounting <fiscal_localizations/colombia>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:66 +msgid "Costa Rica - Accounting" +msgstr "ประเทศคอสตาริกา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:67 +msgid "Croatia - Accounting (RRIF 2012)" +msgstr "ประเทศโครเอเชีย - ระบบบัญชี (RRIF 2012)" + +#: ../../content/applications/finance/fiscal_localizations.rst:68 +msgid "Czech - Accounting" +msgstr "สาธารณรัฐเช็ก - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:69 +msgid "Denmark - Accounting" +msgstr "ประเทศเดนมาร์ก - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:70 +msgid "Dominican Republic - Accounting" +msgstr "สาธารณรัฐโดมินิกัน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:71 +msgid ":doc:`Ecuadorian - Accounting <fiscal_localizations/ecuador>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:72 +msgid ":doc:`Egypt - Accounting <fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:73 +msgid "Ethiopia - Accounting" +msgstr "ประเทศเอธิโอเปีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:74 +msgid "Finnish Localization" +msgstr "การประยุกต์ใช้ของประเทศฟินแลนด์" + +#: ../../content/applications/finance/fiscal_localizations.rst:75 +msgid ":doc:`France - Accounting <fiscal_localizations/france>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:76 +msgid "Generic - Accounting" +msgstr "ทั่วไป - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:77 +msgid ":doc:`Germany <fiscal_localizations/germany>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:79 +msgid "Germany SKR03 - Accounting" +msgstr "ประเทศเยอรมันนี SKR03 - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:80 +msgid "Germany SKR04 - Accounting" +msgstr "ประเทศเยอรมันนี SKR04 - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:82 +msgid "Greece - Accounting" +msgstr "ประเทศกรีซ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:83 +msgid "Guatemala - Accounting" +msgstr "ประเทศกัวเตมาลา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:84 +msgid "Honduras - Accounting" +msgstr "ประเทศฮอนดูรัส - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:85 +msgid ":doc:`Hong Kong - Accounting <fiscal_localizations/hong_kong>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:86 +msgid "Hungarian - Accounting" +msgstr "ประเทศฮังการี - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:87 +msgid ":doc:`Indian - Accounting <fiscal_localizations/india>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:88 +msgid ":doc:`Indonesian - Accounting <fiscal_localizations/indonesia>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:89 +msgid "Ireland - Accounting" +msgstr "ประเทศไอร์แลนด์ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:90 +msgid "Israel - Accounting" +msgstr "ประเทศอิสราเอล - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:91 +msgid ":doc:`Italy - Accounting <fiscal_localizations/italy>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:92 +msgid "Japan - Accounting" +msgstr "ประเทศญี่ปุ่น - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:93 +msgid ":doc:`Kenya - Accounting <fiscal_localizations/kenya>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:94 +msgid "Lithuania - Accounting" +msgstr "ประเทศลิทัวเนีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:95 +msgid ":doc:`Luxembourg - Accounting <fiscal_localizations/luxembourg>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:96 +msgid "Maroc - Accounting" +msgstr "ประเทศโมร็อกโก - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:97 +msgid ":doc:`Mexico - Accounting <fiscal_localizations/mexico>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:98 +msgid "Mongolia - Accounting" +msgstr "ประเทศมองโกเลีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:99 +msgid ":doc:`Netherlands - Accounting <fiscal_localizations/netherlands>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:100 +msgid "New Zealand - Accounting" +msgstr "ประเทศนิวซีแลนด์ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:101 +msgid "Norway - Accounting" +msgstr "ประเทศนอร์เวย์ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:102 +msgid "OHADA - Accounting" +msgstr "OHADA - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:103 +msgid "Pakistan - Accounting" +msgstr "ประเทศปากีสถาน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:104 +msgid "Panama - Accounting" +msgstr "ประเทศปานามา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:105 +msgid ":doc:`Peru - Accounting <fiscal_localizations/peru>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:106 +msgid ":doc:`Philippines - Accounting <fiscal_localizations/philippines>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:107 +msgid "Poland - Accounting" +msgstr "ประเทศโปแลนด์ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:108 +msgid "Portugal - Accounting" +msgstr "ประเทศโปรตุเกส - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:109 +msgid ":doc:`Romania - Accounting <fiscal_localizations/romania>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:110 +msgid ":doc:`Saudi Arabia - Accounting <fiscal_localizations/saudi_arabia>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:111 +msgid ":doc:`Singapore - Accounting <fiscal_localizations/singapore>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:112 +msgid "Slovak - Accounting" +msgstr "ประเทศสโลวาเกีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:113 +msgid "Slovenian - Accounting" +msgstr "ประเทศสโลเวเนีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:114 +msgid "South Africa - Accounting" +msgstr "ประเทศแอฟริกาใต้ - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:115 +msgid ":doc:`Spain - Accounting (PGCE 2008) <fiscal_localizations/spain>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:116 +msgid "Sweden - Accounting" +msgstr "ประเทศสวีแดน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:117 +msgid ":doc:`Switzerland - Accounting <fiscal_localizations/switzerland>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:118 +msgid "Taiwan - Accounting" +msgstr "ประเทศไต้หวัน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:119 +msgid ":doc:`Thailand - Accounting <fiscal_localizations/thailand>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:120 +msgid "Turkey - Accounting" +msgstr "ประเทศตุรกี - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:121 +msgid "" +":doc:`United Arab Emirates - Accounting " +"<fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:122 +msgid ":doc:`UK - Accounting <fiscal_localizations/united_kingdom>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations.rst:123 +msgid "Ukraine - Accounting" +msgstr "ประเทศยูเครน - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:124 +msgid "United States - Accounting" +msgstr "สหรัฐอเมริกา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:125 +msgid "Uruguay - Accounting" +msgstr "ประเทศอุรุกวัย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:126 +msgid "Venezuela - Accounting" +msgstr "ประเทศเวเนซุเอลา - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations.rst:127 +msgid ":doc:`Vietnam - Accounting <fiscal_localizations/vietnam>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:3 +msgid "Argentina" +msgstr "ประเทศอาร์เจนตินา" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:6 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:18 +msgid "Webinars" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:8 +msgid "" +"Below you can find videos with a general description of the localization, " +"and how to configure it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:10 +msgid "" +"`Webinar - Localización de Argentina " +"<https://www.youtube.com/watch?v=_H1HbU-wKVg>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:11 +msgid "" +"`eCommerce - Localización de Argentina " +"<https://www.youtube.com/watch?v=5gUi2WWfRuI>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:14 +msgid "" +"`Smart Tutorial - Localización de Argentina " +"<https://www.odoo.com/slides/smart-tutorial-localizacion-de-argentina-130>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:20 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:24 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:37 +#: ../../content/applications/finance/fiscal_localizations/germany.rst:61 +msgid "Modules installation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:22 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Argentinean localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:29 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:14 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:30 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/india.rst:16 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:16 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:34 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:14 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:71 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:115 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:14 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:15 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:14 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:14 +msgid "Name" +msgstr "ชื่อ" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:30 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:15 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:31 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:34 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:47 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:17 +#: ../../content/applications/finance/fiscal_localizations/india.rst:17 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:17 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:35 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:15 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:72 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:116 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:15 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:15 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:17 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:15 +msgid "Technical name" +msgstr "ชื่อทางเทคนิค" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:32 +msgid ":guilabel:`Argentina - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:33 +msgid "`l10n_ar`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:34 +msgid "" +"Default :ref:`fiscal localization package <fiscal_localizations/packages>`, " +"which represents the minimal configuration to operate in Argentina under the" +" :abbr:`AFIP (Administración Federal de Ingresos Públicos)` regulations and " +"guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:37 +msgid ":guilabel:`Argentinean Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:38 +msgid "`l10n_ar_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:39 +msgid "VAT Book report and VAT summary report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:40 +msgid ":guilabel:`Argentinean Electronic Invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:41 +msgid "`l10n_ar_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:42 +msgid "" +"Includes all technical and functional requirements to generate electronic " +"invoices via web service, based on the AFIP regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:44 +msgid ":guilabel:`Argentinean eCommerce`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:45 +msgid "`l10n_ar_website_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:46 +msgid "" +"(optional) Allows the user to see Identification Type and AFIP " +"Responsibility in the eCommerce checkout form in order to create electronic " +"invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:50 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:37 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:70 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:47 +msgid "Configure your company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:52 +msgid "" +"Once the localization modules are installed, the first step is to set up the" +" company's data. In addition to the basic information, a key field to fill " +"in is the :guilabel:`AFIP Responsibility Type`, which represents the fiscal " +"obligation and structure of the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP Responsibility Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:61 +msgid "Chart of account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:63 +msgid "" +"In Accounting, there are three different :guilabel:`Chart of Accounts` " +"packages to choose from. They are based on a company's AFIP responsibility " +"type, and consider the difference between companies that do not require as " +"many accounts as the companies that have more complex fiscal requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:68 +msgid "Monotributista (227 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:69 +msgid "IVA Exento (290 accounts);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:70 +msgid "Responsable Inscripto (298 Accounts)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select Fiscal Localization Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:77 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:143 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:238 +msgid "Configure master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:80 +msgid "Electronic Invoice Credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:83 +msgid "Environment" +msgstr "สภาพแวดล้อม" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:85 +msgid "" +"The AFIP infrastructure is replicated in two separate environments, " +"**testing** and **production**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:87 +msgid "" +"Testing is provided so that the companies can test their databases until " +"they are ready to move into the **Production** environment. As these two " +"environments are completely isolated from each other, the digital " +"certificates of one instance are not valid in the other one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:91 +msgid "" +"To select a database environment, go to :menuselection:`Accounting --> " +"Settings --> Argentinean Localization` and choose either :guilabel:`Prueba " +"(Testing)` or :guilabel:`Produccion (Production)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Select AFIP database environment: Testing or Production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:99 +msgid "AFIP certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:101 +msgid "" +"The electronic invoice and other AFIP services work with :guilabel:`Web " +"Services (WS)` provided by the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:104 +msgid "" +"In order to enable communication with the AFIP, the first step is to request" +" a :guilabel:`Digital Certificate` if you do not have one already." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:107 +msgid "" +":guilabel:`Generate Certificate Sign Request (Odoo)`. When this option is " +"selected, a file with extension `.csr` (certificate signing request) is " +"generated to be used in the AFIP portal to request the certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Request a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:114 +msgid "" +":guilabel:`Generate Certificate (AFIP)`. Access the AFIP portal and follow " +"the instructions described in `this document " +"<https://drive.google.com/file/d/17OKX2lNWd1bjUt3NxfqcCKBkBh-Xlpo-/ view>`_ " +"to get a certificate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:118 +msgid "" +":guilabel:`Upload Certificate and Private Key (Odoo)`. Once the certificate " +"is generated, upload it to Odoo using the :guilabel:`Pencil` icon next to " +"the field :guilabel:`Certificado` and select the corresponding file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Upload Certificate and Private Key." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:126 +msgid "" +"In case you need to configure the Homologation Certificate, please refer to " +"the AFIP official documentation: `Homologation Certificate " +"<http://www.afip.gob.ar/ws/documentacion/certificados.asp>`_. Furthermore, " +"Odoo allows the user to test electronic invoicing locally without a " +"Homologation Certificate. The following message will be in the chatter when " +"testing locally:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "" +"Invoice validated locally because it is in a testing environment without testing\n" +"certificate/keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:141 +msgid "Identification type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:143 +msgid "" +"As part of the Argentinean localization, document types defined by the AFIP " +"are now available in the **Partner form**. Information is essential for most" +" transactions. There are six :guilabel:`Identification Types` available by " +"default, as well as 32 inactive types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of AR Localization document types in Odoo, as defined by AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:152 +msgid "" +"The complete list of :guilabel:`Identification Types` defined by the AFIP is" +" included in Odoo, but only the common ones are active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:156 +msgid "AFIP responsibility type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:158 +msgid "" +"In Argentina, the document type and corresponding transactions associated " +"with customers and vendors is defined by the AFIP Responsibility type. This " +"field should be defined in the **Partner form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:169 +msgid "" +"As part of the localization module, the taxes are created automatically with" +" their related financial account and configuration, e.g., 73 taxes for " +":guilabel:`Responsable Inscripto`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list of AR Localization taxes with financial amount and configuration in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:177 +msgid "Taxes types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:179 +msgid "Argentina has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:181 +msgid "" +":guilabel:`VAT`: this is the regular VAT and can have various percentages;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:182 +msgid "" +":guilabel:`Perception`: advance payment of a tax that is applied on " +"invoices;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:183 +msgid "" +":guilabel:`Retention`: advance payment of a tax that is applied on payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:186 +msgid "Special taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:188 +msgid "" +"Some Argentinean taxes are not commonly used for all companies, and those " +"less common options are labeled as inactive in Odoo by default. Before " +"creating a new tax, be sure to check if that tax is not already included as " +"inactive." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "" +"A list showing less common Argentinean tax options, which are labeled as inactive in Odoo\n" +"by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:200 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:252 +msgid "Document types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:202 +msgid "" +"In some Latin American countries, like Argentina, some accounting " +"transactions such as invoices and vendor bills are classified by document " +"types defined by the governmental fiscal authorities. In Argentina, the " +"`AFIP <https://www.afip.gob.ar/>`__ is the governmental fiscal authority " +"that defines such transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:207 +msgid "" +"The document type is an essential piece of information that needs to be " +"clearly displayed in printed reports, invoices, and journal entries that " +"list account moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:210 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the document type includes the " +"country in which the document is applicable (this data is created " +"automatically when the localization module is installed)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:214 +msgid "" +"The information required for the :guilabel:`Document Types` is included by " +"default so the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A list of document types in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:222 +msgid "" +"There are several :guilabel:`Document Types` types that are inactive by " +"default, but can be activated as needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:226 +msgid "Letters" +msgstr "จดหมาย" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:228 +msgid "" +"For Argentina, the :guilabel:`Document Types` include a letter that helps " +"indicate the type of transaction or operation. For example, when an invoice " +"is related to a(n):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:231 +msgid "" +":guilabel:`B2B transaction`, a document type :guilabel:`A` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:232 +msgid "" +":guilabel:`B2C transaction`, a document type :guilabel:`B` must be used;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:233 +msgid "" +":guilabel:`Exportation Transaction`, a document type :guilabel:`E` must be " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:235 +msgid "" +"The documents included in the localization already have the proper letter " +"associated with each :guilabel:`Document Type`, so there is no further " +"configuration necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "document types grouped by letters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:243 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 +msgid "Use on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:245 +msgid "" +"The :guilabel:`Document Type` on each transaction will be determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:247 +msgid "" +"The journal entry related to the invoice (if the journal uses documents);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:248 +msgid "" +"The onditions applied based on the type of issuer and receiver (e.g., the " +"type of fiscal regime of the buyer and the type of fiscal regime of the " +"vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:254 +msgid "" +"In the Argentinean localization, the journal can have a different approach " +"depending on its usage and internal type. To configure journals, go to " +":menuselection:`Accounting --> Configuration --> Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:258 +msgid "" +"For sales and purchase journals, it's possible to activate the option " +":guilabel:`Use Documents`, which enables a list of :guilabel:`Document " +"Types` that can be related to the invoices and vendor bills. For more detail" +" on invoices, please refer to the section :ref:`2.3 document types " +"<document-types>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:263 +msgid "" +"If the sales or purchase journals do not have the :guilabel:`Use Documents` " +"option activated, they will not be able to generate fiscal invoices, " +"meaning, their use case will be mostly limited to monitoring account moves " +"related to internal control processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:268 +msgid "AFIP information (also known as AFIP Point of Sale)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:270 +msgid "" +"The :guilabel:`AFIP POS System` is a field only visible for the **Sales** " +"journals and defines the type of AFIP POS that will be used to manage the " +"transactions for which the journal is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:273 +msgid "The AFIP POS defines the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:275 +msgid "the sequences of document types related to the web service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:276 +msgid "the structure and data of the electronic invoice file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "A AFIP POS System field which is available on Sales journals in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:283 +msgid "Web services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:285 +msgid "" +"**Web services** help generate invoices for different purposes. Below are a " +"few options to choose from:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:288 +msgid "" +":guilabel:`wsfev1: Electronic Invoice`: is the most common service, which is" +" used to generate invoices for document types A, B, C, M with no detail per" +" item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:290 +msgid "" +":guilabel:`wsbfev1: Electronic Fiscal Bond`: is for those who invoice " +"capital goods and wish to access the benefit of the Electronic Tax Bonds " +"granted by the Ministry of Economy. For more details go to: `Fiscal Bond " +"<https://www.argentina.gob.ar/acceder-un-bono-por-fabricar-bienes-de-" +"capital>`__;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:294 +msgid "" +":guilabel:`wsfexv1: Electronic Exportation Invoice`: is used to generate " +"invoices for international customers and transactions that involve " +"exportation processes, the document type related is type \"E\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Web Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:302 +msgid "Here are some useful fields to know when working with web services:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:304 +msgid "" +":guilabel:`AFIP POS Number`: is the number configured in the AFIP to " +"identify the operations related to this AFIP POS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:306 +msgid "" +":guilabel:`AFIP POS Address`: is the field related to the commercial address" +" registered for the POS, which is usually the same address as the company. " +"For example, if a company has multiple stores (fiscal locations) then the " +"AFIP will require the company to have one AFIP POS per location. This " +"location will be printed in the invoice report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:310 +msgid "" +":guilabel:`Unified Book`: when the AFIP POS System is Preimpresa, then the " +"document types (applicable to the journal) with the same letter will share " +"the same sequence. For example:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:313 +msgid "Invoice: FA-A 0001-00000002;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:314 +msgid "Credit Note: NC-A 0001-00000003;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:315 +msgid "Debit Note: ND-A 0001-00000004." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:318 +msgid "Sequences" +msgstr "ลำดับ" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:320 +msgid "" +"For the first invoice, Odoo synchronizes with the AFIP automatically and " +"displays the last sequence used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:324 +msgid "" +"When creating :guilabel:`Purchase Journals`, it's possible to define whether" +" they are related to document types or not. In the case where the option to " +"use documents is selected, there would be no need to manually associate the " +"document type sequences, since the document number is provided by the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:391 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:351 +msgid "Usage and testing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:333 +msgid "Invoice" +msgstr "ใบแจ้งหนี้" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:335 +msgid "" +"The information below applies to invoice creation once the partners and " +"journals are created and properly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:339 +msgid "Document type assignation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:341 +msgid "" +"When the partner is selected, the :guilabel:`Document Type` field will be " +"filled in automatically based on the AFIP document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:344 +msgid "" +"**Invoice for a customer IVA Responsable Inscripto, prefix A** is the type " +"of document that shows all the taxes in detail along with the customer's " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for a customer IVA Responsable Inscripto, prefix A." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:350 +msgid "" +"**Invoice for an end customer, prefix B** is the type of document that does " +"not detail the taxes, since the taxes are included in the total amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Invoice for an end customer, prefix B." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:356 +msgid "" +"**Exportation Invoice, prefix E** is the type of document used when " +"exporting goods that shows the incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Exportation Invoice, prefix E" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:362 +msgid "" +"Even though some invoices use the same journal, the prefix and sequence are " +"given by the :guilabel:`Document Type` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:365 +msgid "" +"The most common :guilabel:`Document Type` will be defined automatically for " +"the different combinations of AFIP responsibility type but it can be updated" +" manually by the user before confirming the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:370 +msgid "Electronic invoice elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:372 +msgid "" +"When using electronic invoices, if all the information is correct then the " +"invoice is posted in the standard way unless there is an error that needs to" +" be addressed. When error messages pop up, they indicate both the issue that" +" needs attention along with a proposed solution. If an error persists, the " +"invoice remains in draft until the issue is resolved." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:377 +msgid "" +"Once the invoice is posted, the information related to the AFIP validation " +"and status is displayed in the AFIP tab, including:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:380 +msgid ":guilabel:`AFIP Autorisation`: CAE number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:381 +msgid "" +":guilabel:`Expiration Date`: deadline to deliver the invoice to the " +"customers (normally 10 days after the CAE is generated);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:383 +msgid "" +":guilabel:`Result:` indicates if the invoice has been :guilabel:`Aceptado en" +" AFIP` and/or :guilabel:`Aceptado con Observaciones`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP Status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:391 +msgid "Invoice taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:393 +msgid "" +"Based on the :guilabel:`AFIP Responsibility type`, the VAT tax can apply " +"differently on the PDF report:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:396 +msgid "" +":guilabel:`A. Tax excluded`: in this case the taxed amount needs to be " +"clearly identified in the report. This condition applies when the customer " +"has the following AFIP Responsibility type of **Responsable Inscripto**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax excluded." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:403 +msgid "" +":guilabel:`B. Tax amount included`: this means that the taxed amount is " +"included as part of the product price, subtotal, and totals. This condition " +"applies when the customer has the following AFIP Responsibility types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:407 +msgid "IVA Sujeto Exento;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:408 +msgid "Consumidor Final;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:409 +msgid "Responsable Monotributo;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:410 +msgid "IVA liberado." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:0 +msgid "Tax amount included." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:417 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:646 +msgid "Special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:420 +msgid "Invoices for services" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:422 +msgid "" +"For electronic invoices that include :guilabel:`Services`, the AFIP requires" +" to report the service starting and ending date, this information can be " +"filled in the tab :guilabel:`Other Info`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoices for Services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:429 +msgid "" +"If the dates are not selected manually before the invoice is validated, the " +"values will be filled automatically with the first and last day of the " +"invoice's month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Service Dates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:437 +msgid "Exportation invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:439 +msgid "" +"Invoices related to :guilabel:`Exportation Transactions` require that a " +"journal uses the AFIP POS System **Expo Voucher - Web Service** so that the " +"proper document type(s) can be associated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Exporation journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:446 +msgid "" +"When the customer selected in the invoice is configured with an AFIP " +"responsibility type :guilabel:`Cliente / Proveedor del Exterior` - " +":guilabel:`Ley N° 19.640`, Odoo automatically assigns the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:450 +msgid "Journal related to the exportation Web Service;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:451 +msgid "Exportation document type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:452 +msgid "Fiscal position: Compras/Ventas al exterior;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:453 +msgid "Concepto AFIP: Products / Definitive export of goods;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:454 +msgid "Exempt Taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice fields autofilled in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:461 +msgid "" +"The Exportation Documents require Incoterms to be enabled and configured, " +"which can be found in :menuselection:`Other Info --> Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Export invoice - Incoterm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:469 +msgid "Fiscal bond" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:471 +msgid "" +"The :guilabel:`Electronic Fiscal Bond` is used for those who invoice capital" +" goods and wish to access the benefit of the Electronic Tax Bonds granted by" +" the Ministry of Economy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:474 +msgid "" +"For these transactions, it is important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:476 +msgid "Currency (according to the parameter table) and invoice quotation;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:477 +msgid "Taxes;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:478 +msgid "Zone;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:479 +msgid "Detail each item;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:481 +msgid "Code according to the Common Nomenclator of Mercosur (NCM);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:482 +msgid "Complete description;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:483 +msgid "Unit Net Price;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:484 +msgid "Quantity;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:485 +msgid "Unit of measurement;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:486 +msgid "Bonus;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:487 +msgid "VAT rate." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:490 +msgid "Electronic credit invoice MiPyme (FCE)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:492 +msgid "" +"For SME invoices, there are several document types that are classified as " +"**MiPyME**, which are also known as **Electronic Credit Invoice** (or " +"**FCE** in Spanish). This classification develops a mechanism that improves " +"the financing conditions for small and medium-sized businesses, and allows " +"them to increase their productivity, through the early collection of credits" +" and receivables issued to their clients and/or vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:498 +msgid "" +"For these transactions it's important to consider the following " +"requirements:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:500 +msgid "specific document types (201, 202, 206, etc);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:501 +msgid "the emitter should be eligible by the AFIP to MiPyME transactions;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:502 +msgid "the amount should be bigger than 100,000 ARS;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:503 +msgid "" +"A bank account type CBU must be related to the emisor, otherwise the invoice" +" cannot be validated, having an error message such as the following." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Bank account relation error." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:510 +msgid "" +"To set up the :guilabel:`Transmission Mode`, go to settings and select " +"either :guilabel:`SDC` or :guilabel:`ADC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:517 +msgid "" +"To change the :guilabel:`Transmission Mode` for a specific invoice, go to " +"the :guilabel:`Other Info` tab and change it before confirming." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:521 +msgid "" +"Changing the :guilabel:`Transmission Mode` will not change the mode selected" +" in :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Transmission Mode on Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:528 +msgid "" +"When creating a :guilabel:`Credit/Debit` note related to a FCE document:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:530 +msgid "" +"use the :guilabel:`Credit and Debit Note` buttons, so all the information " +"from the invoice is transferred to the new :guilabel:`Credit and Debit " +"Note`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:532 +msgid "" +"the document letter should be the same as than the originator document " +"(either A or B);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:533 +msgid "" +"the same currency as the source document must be used. When using a " +"secondary currency there is an exchange difference if the currency rate is " +"different between the emission day and the payment date. It is possible to " +"create a credit/debit note to decrease/increase the amount to pay in ARS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Credit & debit notes buttons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:541 +msgid "When creating a :guilabel:`Credit Note` we can have two scenarios:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:543 +msgid "" +"the FCE is rejected so the :guilabel:`Credit Note` should have the field " +":guilabel:`FCE, is Cancellation?` as *True*; or;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:545 +msgid "" +"the :guilabel:`Credit Note`, is created to annulate the FCE document, in " +"this case the field :guilabel:`FCE, is Cancellation?` must be *empty* " +"(false)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "FCE: Es Cancelación?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:553 +msgid "Invoice printed report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:555 +msgid "" +"The :guilabel:`PDF Report` related to electronic invoices that have been " +"validated by the AFIP includes a barcode at the bottom of the format which " +"represents the CAE number. The expiration date is also displayed as it is a " +"legal requirement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Invoice printed report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:564 +msgid "Troubleshooting and auditing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:566 +msgid "" +"For auditing and troubleshooting purposes, it is possible to obtain detailed" +" information of an invoice number that has been previously sent to the AFIP." +" To retrieve this information, activate the :ref:`developer mode <developer-" +"mode>`, then go to the :menuselection:`Accounting` menu and click on the " +"button :guilabel:`Consult Invoice` button in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult invoice in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Details of invoice consulted in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:579 +msgid "" +"It is also possible to retrieve the last number used in AFIP for a specific " +"document type and POS Number as a reference for any possible issues on the " +"sequence synchronization between Odoo and AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Consult the last invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:590 +msgid "" +"Based on the purchase journal selected for the vendor bill, the " +":guilabel:`Document Type` is now a required field. This value is auto-" +"populated based on the AFIP Responsibility type of Issuer and Customer, but " +"the value can be changed if necessary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Changing journal and document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:598 +msgid "" +"The :guilabel:`Document Number` field needs to be registered manually and " +"the format will be validated automatically. However, in case the format is " +"invalid, a user error will be displayed indicating the correct format that " +"is expected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Vendor bill document number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:606 +msgid "" +"The vendor bill number is structured in the same way as the customer " +"invoices, excepted that the document sequence is entered by the user using " +"the following format: *Document Prefix - Letter - Document Number*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:611 +msgid "Validate vendor bill number in AFIP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:613 +msgid "" +"As most companies have internal controls to verify that the vendor bill is " +"related to an AFIP valid document, an automatic validation can be set in " +":menuselection:`Accounting --> Settings --> Argentinean Localization --> " +"Validate document in the AFIP`, considering the following levels:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:617 +msgid "" +":guilabel:`Not available:` the verification is not done (this is the default" +" value);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:618 +msgid "" +":guilabel:`Available:` the verification is done. In case the number is not " +"valid it, only displays a warning but still allows the vendor bill to be " +"posted;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:620 +msgid "" +":guilabel:`Required:` the verification is done and it does not allow the " +"user to post the vendor bill if the document number is not valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify Vendor Bills validity in AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:628 +msgid "Validate vendor bills in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:630 +msgid "" +"With the vendor validation settings enabled, a new button shows up on the " +"vendor bills inside of Odoo, labeled :guilabel:`Verify on AFIP`, which is " +"located next to the :guilabel:`AFIP Authorization code` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Verify on AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:638 +msgid "" +"In case the vendor bill cannot be validated in AFIP, a value of " +":guilabel:`Rejected` will be displayed on the dashboard and the details of " +"the invalidation will be added to the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "AFIP authorization Rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:649 +msgid "Untaxed concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:651 +msgid "" +"There are some transactions that include items that are not a part of the " +"VAT base amount, such as fuel and gasoline invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:654 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and an additional item to register the amount " +"of the exempt concept." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT exempt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:662 +msgid "Perception taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:664 +msgid "" +"The vendor bill will be registered using one item for each product that is " +"part of the VAT base amount, and the perception tax can be added in any of " +"the product lines. As a result, there will be one tax group for the VAT and " +"another for the perception. The perception default value is always " +":guilabel:`0.10`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:669 +msgid "" +"To edit the VAT perception and set the correct amount, you should use the " +":guilabel:`Pencil` icon that is the next to the :guilabel:`Perception` " +"amount. After the VAT perception amount has been set, the invoice can then " +"be validated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Enter the perception amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:678 +msgid "Check management" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:680 +msgid "" +"To install the *Third Party and Deferred/Electronic Checks Management* " +"module, go to :menuselection:`Apps` and search for the module by its " +"technical name `l10n_latam_check` and click the :guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "l10n_latam_check module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:688 +msgid "" +"This module enables the required configuration for journals and payments to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:690 +msgid "Create, manage, and control your different types of checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:691 +msgid "Optimize the management of *own checks* and *third party checks*" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:692 +msgid "" +"Have an easy and effective way to manage expiration dates from your own and " +"third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:694 +msgid "" +"Once all the configurations are made for the Argentinian electronic invoice " +"flow, it is also needed to complete certain configurations for the own " +"checks and the third party checks flows." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:698 +msgid "Own checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:700 +msgid "" +"Configure the bank journal used to create your own checks by going to " +":menuselection:`Accounting --> Configuration --> Journals`, selecting the " +"bank journal, and opening the :guilabel:`Outgoing Payments` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:704 +msgid "" +":guilabel:`Checks` should be available as a :guilabel:`Payment Method`. If " +"not, click :guilabel:`Add a line` and type `Checks` under :guilabel:`Payment" +" Method` to add them" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:706 +msgid "Enable the :guilabel:`Use electronic and deferred checks` setting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:709 +msgid "" +"This last configuration **disables** the printing ability but enables to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:711 +msgid "Enter check numbers manually" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:712 +msgid "Adds a field to allocate the payment date of the check" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Bank journal configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:719 +msgid "Management of own checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:721 +msgid "" +"Own checks can be created directly from the vendor bill. For this process, " +"click on the :guilabel:`Register Payment` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:724 +msgid "" +"On the payment registration modal, select the bank journal from which the " +"payment is to be made and set the :guilabel:`Check Cash-In Date`, and the " +":guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with own check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:732 +msgid "" +"To manage current checks, the :guilabel:`Check Cash-In Date` field must be " +"left blank or filled in with the current date. To manage deferred checks, " +"the :guilabel:`Check Cash-In Date` must be set in the future." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:736 +msgid "" +"To manage your existing own checks, navigate to :menuselection:`Accounting " +"--> Vendors --> Own Checks`. This window shows critical information such as " +"the dates when checks need to be paid, the total quantity of checks, and the" +" total amount paid in checks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Own checks menu location." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:744 +msgid "" +"It is important to note that the list is pre-filtered by checks that are " +"still *not reconciled* with a bank statement - that were not yet debited " +"from the bank - which can be verified with the :guilabel:`Is Matched with a " +"Bank Statement` field. If you want to see all of your own checks, delete the" +" :guilabel:`No Bank Matching` filter by clicking on the :guilabel:`X` " +"symbol." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Own checks menu organization and filtering." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:754 +msgid "Cancel an own check" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:756 +msgid "" +"To cancel an own check created in Odoo, navigate to " +":menuselection:`Accounting --> Vendors --> Own Checks` and select the check " +"to be canceled, then click on the :guilabel:`Void Check` button. This will " +"break the reconciliation with the vendor bills and the bank statements and " +"leave the check in a **canceled** state." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Empty Check button to cancel Own Checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:766 +msgid "Third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:768 +msgid "" +"In order to register payments using third party checks, two specific " +"journals need to be configured. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Journals` and create two " +"new journals:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:772 +msgid "`Third Party Checks`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:773 +msgid "`Rejected Third Party Checks`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:776 +msgid "" +"You can manually create more journals if you have multiple points of sale " +"and need journals for those." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:779 +msgid "" +"To create the *Third Party Checks* journal, click the :guilabel:`New` button" +" and configure the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:782 +msgid "Type `Third Party Checks` as the :guilabel:`Journal Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:783 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:817 +msgid "Select :guilabel:`Cash` as :guilabel:`Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:784 +msgid "" +"In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to " +"`1.1.1.02.010 Cheques de Terceros`, input a :guilabel:`Short Code` of your " +"choice, and select a :guilabel:`Currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Automatically created cash account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:791 +msgid "The available payment methods are listed in the *payments* tabs:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:793 +msgid "" +"For new incoming third party checks, go to :menuselection:`Incoming Payments" +" tab --> Add a line` and select :guilabel:`New Third Party Checks`. This " +"method is used to create *new* third party checks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:796 +msgid "" +"For incoming and outgoing existing third party checks, go to " +":menuselection:`Incoming Payments tab --> Add a line` and select " +":guilabel:`Existing Third Party Checks`. Repeat the same step for the " +":guilabel:`Outgoing Payments` tab. This method is used to receive and/or pay" +" vendor bills using already *existing* checks, as well as for internal " +"transfers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:802 +msgid "" +"You can delete pre-existing payment methods appearing by default when " +"configuring the third party checks journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment methods automatically created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:809 +msgid "" +"The *Rejected Third Party Checks* journal also needs to be created and/or " +"configured. This journal is used to manage rejected third party checks and " +"can be utilized to send checks rejected at the moment of collection or when " +"coming from vendors when rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:813 +msgid "" +"To create the *Rejected Third Party Checks* journal, click the " +":guilabel:`New` button and configure the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:816 +msgid "Type `Rejected Third Party Checks` as the :guilabel:`Journal Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:818 +msgid "" +"In the :guilabel:`Journal Entries` tab, set :guilabel:`Cash Account`: to " +"`1.1.1.01.002 Rejected Third Party Checks`, input a :guilabel:`Short Code` " +"of your choice, and select a :guilabel:`Currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:822 +msgid "Use the same payment methods as the *Third Party Checks* journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:825 +msgid "New third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:827 +msgid "" +"To register a *new* third party check for a customer invoice, click the " +":guilabel:`Register Payment` button. In the pop-up window, you must select " +":guilabel:`Third Party Checks` as journal for the payment registration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:831 +msgid "" +"Select :guilabel:`New Third Party Checks` as :guilabel:`Payment Method`, and" +" fill in the :guilabel:`Check Number`, :guilabel:`Payment Date`, and " +":guilabel:`Check Bank`. Optionally, you can manually add the " +":guilabel:`Check Issuer Vat`, but this is automatically filled by the " +"customer's VAT number related to the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with New Third Party Check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:841 +msgid "Existing third party checks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:843 +msgid "" +"To pay a vendor bill with an *existing* check, click the :guilabel:`Register" +" Payment` button. In the pop-up window, you must select :guilabel:`Third " +"Party Checks` as journal for the payment registration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:847 +msgid "" +"Select :guilabel:`Existing Third Party Checks` as :guilabel:`Payment " +"Method`, and select a check from the :guilabel:`Check` field. The field " +"shows all **available existing checks** to be used as payment for vendor " +"bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Payment pop-up window with Existing Third Party Check options enabled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:855 +msgid "" +"When an **existing third party check** is used, you can review the " +"operations related to it. For example, you can see if a third party check " +"made to pay a customer invoice was later used as an existing third party " +"check to pay a vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:859 +msgid "" +"To do so, either go to :menuselection:`Accounting --> Customers --> Third " +"Party Checks` or :menuselection:`Accounting --> Vendors --> Own Checks` " +"depending on the case, and click on a check. In the :guilabel:`Check Current" +" Journal` field, click on :guilabel:`=> Check Operations` to bring up the " +"check's history and movements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Check Operations menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:868 +msgid "" +"The menu also displays critical information related to these operations, " +"such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:870 +msgid "" +"The :guilabel:`Payment Type`, allowing to classify whether it is a payment " +"*sent* to a vendor or a payment *received* from a customer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:872 +msgid "The :guilabel:`Journal` in which the check is currently registered" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:873 +msgid "" +"The **partner** associated with the operation (either customer or vendor)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:878 +msgid "" +"As part of the localization installation, financial reporting for Argentina " +"was added to the :guilabel:`Accounting` dashboard. Access these reports by " +"navigating to :menuselection:`Accounting --> Reporting --> Argentinean " +"Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Argentinean reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:887 +msgid "VAT reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:890 +msgid "Sales VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:892 +msgid "" +"In this report, all the sales are recorded, which are taken as the basis for" +" the accounting records to determine the VAT (Tax Debit)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:895 +msgid "" +"The :guilabel:`Sales VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Sales VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:903 +msgid "Purchases VAT book" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:905 +msgid "" +"The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file " +":guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` " +"files to upload in the AFIP portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "Purchases VAT book." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:913 +msgid "VAT summary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:915 +msgid "" +"Pivot table designed to check the monthly VAT totals. This report is for " +"internal usage, it is not sent to the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "VAT Summary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:923 +msgid "IIBB - Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:926 +msgid "IIBB - Sales by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:928 +msgid "" +"Pivot table where you can validate the gross income in each jurisdiction. " +"Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Sales by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:936 +msgid "IIBB - Purchases by jurisdiction" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:938 +msgid "" +"Pivot table where you can validate the gross purchases in each jurisdiction." +" Affidavit for the corresponding taxes to pay, therefore it is not sent to " +"the AFIP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst-1 +msgid "IIBB Purchases by jurisdiction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:3 +msgid "Australia" +msgstr "ประเทศออสเตรเลีย" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:14 +msgid "Module Name" +msgstr "ชื่อโมดูล" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:15 +msgid "Module Key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:17 +msgid ":guilabel:`Australia - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:18 +msgid "`l10n_au`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:19 +msgid "" +"Installed by default when the Accounting :guilabel:`Fiscal Localization` " +"package is set to :guilabel:`Australia`. This module also installs the " +":guilabel:`ABA credit transfer` and the :guilabel:`Remittance Advice report`" +" module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:22 +msgid ":guilabel:`Australian Reports - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:23 +msgid "`l10n_au_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:24 +msgid "" +"Includes the :guilabel:`Taxable Payments Annual Reports (TPAR)` and the " +":guilabel:`BAS report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:26 +msgid ":guilabel:`Australia - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:27 +msgid "`l10n_au_hr_payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:28 +msgid "Payroll localisation for Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:29 +msgid ":guilabel:`Australia - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:30 +msgid "`l10n_au_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:31 +msgid "" +"Installs the link between Australian payroll and accounting. The module also" +" installs the modules: :guilabel:`Australian - Accounting`; " +":guilabel:`Australian Reports - Accounting`; and :guilabel:`Australia - " +"Payroll`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:34 +msgid ":guilabel:`Accounting Customer Statements`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:35 +msgid "`l10n_account_customer_statements`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:36 +msgid "" +"Allows the management and sending of monthly customer statements from the " +"partner ledger and the contact form. Also used in New Zealand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:38 +msgid ":guilabel:`Employment Hero Australian Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:39 +msgid "`l10n_au_keypay`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:40 +msgid "" +"Synchronises all pay runs from Employment Hero with Odoo’s journal entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:47 +msgid "" +"The Australian chart of accounts is included in the **Australia - " +"Accounting** module. Go to :menuselection:`Accounting --> Configuration --> " +"Chart of Accounts` to access it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:51 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:27 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:373 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:79 +msgid ":doc:`../accounting/get_started/chart_of_accounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:56 +msgid "Taxes and GST" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:58 +msgid "" +"The default Australian taxes impact the :ref:`BAS Report <australia/bas>`, " +"which can be accessed through :menuselection:`Accounting --> Reporting --> " +"BAS Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:61 +msgid "" +"In Australia, the standard **Goods and Services Tax** (GST) rate is 10%, but" +" different rates and exemptions exist for specific categories of goods and " +"services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Default GST of Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:68 +msgid "Tax Mapping" +msgstr "การวางแผนภาษี" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:70 +msgid "" +"Within the Australian localisation package, tax names encompass the tax rate" +" as an integral part of their naming convention." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:73 +msgid "" +"Despite the high amount of taxes in Odoo, these taxes are pretty similar " +"(mostly 0% and 10%), with different tax grid variations for:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:76 +msgid "Goods" +msgstr "สินค้า" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:77 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:165 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:169 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:173 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:177 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:185 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:189 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:193 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:197 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:201 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:205 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:213 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:217 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:221 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:225 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:229 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:233 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:237 +msgid "Services" +msgstr "บริการ" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:78 +msgid "TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:79 +msgid "TPAR without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:82 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:79 +msgid ":doc:`Taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:84 +msgid "" +"Taxes including a **TPAR** mention impact not only the **BAS** report but " +"also the **TPAR** report. Businesses from certain industries need to report " +"payments made to subcontractors from relevant services during the financial " +"year. Odoo combines the use of taxes and fiscal positions to report these " +"payments on the **TPAR** report. Taxes with the mention **TPAR without ABN**" +" are used to record amounts withheld from subcontractors without an **ABN** " +"for the **ATO**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:91 +msgid ":ref:`TPAR <australia/tpar>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:93 +msgid "Here are the taxes for Australia in Odoo 17." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:99 +msgid "GST Name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:101 +msgid "GST Scope" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:102 +msgid "GST Type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:103 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:139 +msgid "10%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:104 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:164 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:168 +msgid "GST Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:106 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:110 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:114 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:118 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:122 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:126 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:130 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:134 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:138 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:166 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:170 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:174 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:178 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:182 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:186 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:190 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:194 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:198 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:202 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:206 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:210 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:214 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:218 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:222 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:226 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:230 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:234 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:238 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Purchases" +msgstr "รายการที่ซื้อ" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:107 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:143 +msgid "10% INC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:108 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:172 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:176 +msgid "GST Inclusive Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:111 +msgid "10% C" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:112 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:180 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:184 +msgid "Capital Purchases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:115 +msgid "0% C" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:116 +msgid "Zero Rated Purch" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:119 +msgid "100% T EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:120 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:196 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:200 +msgid "Purchase (Taxable Imports) - Tax Paid Separately" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:123 +msgid "10% I" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:124 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:204 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:208 +msgid "Purchases for Input Taxed Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:127 +msgid "10% P" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:128 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:212 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:216 +msgid "Purchases for Private use or not deductible" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:131 +msgid "100% EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:132 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:220 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:224 +msgid "GST Only on Imports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:135 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:159 +msgid "10% Adj" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:136 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:228 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:232 +msgid "Tax Adjustments (Purchases)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:140 +msgid "GST Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:144 +msgid "GST Inclusive Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:147 +msgid "0% EX" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:148 +msgid "Zero Rated (Export) Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:151 +msgid "0% EXEMPT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:152 +msgid "Exempt Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:155 +msgid "0% I" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:156 +msgid "Input Taxed Sales" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:160 +msgid "Tax Adjustments (Sales)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:163 +msgid "10% TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:167 +msgid "10% TPAR NO ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:171 +msgid "10% INC TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:175 +msgid "10% INC TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:179 +msgid "10% C TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:183 +msgid "10% C TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:187 +msgid "0% C TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:188 +msgid "Zero Rated Purch TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:191 +msgid "0% C TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:192 +msgid "Zero Rated Purch TPAR without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:195 +msgid "100% T EX TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:199 +msgid "100% T EX TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:203 +msgid "10% I TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:207 +msgid "100% I TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:211 +msgid "10% P TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:215 +msgid "10% P TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:219 +msgid "100% EX TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:223 +msgid "100% EX TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:227 +msgid "10% Adj TPAR" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:231 +msgid "10% Adj TPAR N ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:235 +msgid "47% WH" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:236 +msgid "Tax Withheld for Partners without ABN" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:243 +msgid "BAS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:245 +msgid "" +"The **Business Activity Statement (BAS)** report is a critical tax reporting" +" requirement for businesses registered for **Goods and Services Tax (GST)** " +"in Australia. The **BAS** is used to report and remit various taxes to the " +"**Australian Taxation Office (ATO)**. With the Odoo **BAS** feature, " +"businesses can report on the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:250 +msgid "Goods and Services Tax (GST)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:251 +msgid "PAYG tax withheld" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "BAS report in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:256 +msgid "" +"The taxes for GST are collected from the **tax grid**, which is pre-" +"configured in the system. The **tax grid** can also be manually set up for " +"any additional special GST. Once the tax for each account is set up, the " +"system automatically slots journal items into the correct tax category. This" +" ensures the **BAS** report is accurate and reflective of the business's " +"financial activities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "GST grids in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:264 +msgid "" +"In addition, the **BAS** report includes the **PAYG** tax withheld " +"components (**W1** to **W5**, then **summary, section 4**). This integration" +" ensures that all payroll-related withholding taxes are accurately captured " +"and reflected within the report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "PAYG Tax Withheld and Summary of BAS report in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:271 +msgid "" +"The module incorporates built-in rules that facilitate the automatic " +"calculation of taxes for types **W1** to **W5**. For a detailed walkthrough " +"and more information on the calculation process for these taxes, please " +"refer to the Payroll app documentation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:276 +msgid ":ref:`Payroll <australia/payroll>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:279 +msgid "Closing the BAS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:281 +msgid "" +"When it is time to file the tax return with the **ATO**, click " +":guilabel:`Closing entry`. The tax return period can be configured in " +":menuselection:`configuration --> Settings --> Tax Return Periodicity`. " +"Also, the start date of the tax return period can be defined through the " +"**period button** (marked by a calendar icon 📅)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:287 +msgid ":doc:`Year-end closing <../accounting/reporting/year_end>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:290 +msgid "" +"Odoo uses the *calendar quarter* rather than the Australian FY quarter, " +"which means **July to September is Q3 in Odoo**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:293 +msgid "" +"Before closing the entry for the first time, the default **GST payable " +"account** and **GST receivable account** need to be set. A notification pops" +" up and redirects the user to tax group configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:297 +msgid "" +"Once the **GST payable** and **GST receivable** accounts are set up, the " +"**BAS** report generates an accurate journal closing entry automatically, " +"which balances out the GST balance with the GST clearing account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "GST accounts for the BAS report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:304 +msgid "" +"The balance between **GST receivable** and **payable** is set against the " +"tax clearing account defined on the tax group. The amount to be paid to or " +"received from the **ATO** can be reconciled against a bank statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "BAS tax payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:312 +msgid "" +"The **BAS** report is not directly submitted to the **ATO**. Odoo helps you " +"automatically compute the necessary values in each section, with the " +"possibility to audit them to better understand the history behind these " +"numbers. Businesses can copy these values and enter them on the `ATO’s " +"portal <https://www.ato.gov.au/newsrooms/small-business-newsroom/lodging-" +"your-next-bas>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:320 +msgid "TPAR report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:322 +msgid "" +"Odoo allows businesses to report payments made to contractors or " +"subcontractors during the financial year. This is done by generating a " +":abbr:`TPAR (Taxable Payments Annual Report)`. If you are unsure your " +"business needs this report, refer to the documentation provided by the `ATO " +"<https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-" +"paying/reports-and-returns/taxable-payments-annual-report>`_. You can find " +"this report in :menuselection:`Accounting --> Reporting --> Taxable Payments" +" Annual Reports (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:331 +msgid "" +"Under :menuselection:`Accounting --> Customers` or " +":menuselection:`Accounting --> Vendors`, select a your contractor and set a " +":guilabel:`Fiscal Position` under the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "TPAR fiscal position" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:337 +msgid "" +"Upon billing a contact with a fiscal position set to :guilabel:`TPAR` or " +":guilabel:`TPAR without ABN`, the report is automatically generated in " +":menuselection:`Accounting --> Reporting --> Taxable Payments Annual Reports" +" (TPAR)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:341 +msgid "" +"The report includes the **ABN**, **Total GST**, **Gross Paid**, and **Tax " +"Withheld** from their **TPAR** subcontractors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:344 +msgid "**Total GST**: the total tax paid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:345 +msgid "" +"**Gross Paid amounts**: shows after registering a payment for those bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:346 +msgid "" +"**Tax Withheld**: shown if the subcontractor is registered with a fiscal " +"position set to :guilabel:`TPAR without ABN`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:349 +msgid "The **TPAR** report can be exported to PDF, XLSX, and TPAR formats." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:354 +msgid "Customer statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:356 +msgid "" +"Customer statements allow customers to see their financial transactions with" +" the company over a certain period, and overdue statement details. These " +"statements can be sent out to customers by email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Customer statement in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:363 +msgid "There are **two** ways for customers to download these statements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:365 +msgid "" +"**From the contact form:** Customer statements are under " +":menuselection:`Customers --> Customers`. Select a customer, click the " +"**gear icon (⚙)**, and then :guilabel:`Print Customer Statements`. This " +"prints out the statement from the beginning of the month to today's date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:370 +msgid "" +"**From the partner ledger:** This option allows for more flexibility in " +"selecting a statement's start and end date. You can access it by going to " +":menuselection:`Accounting --> Reporting --> Partner Ledger`. From here, " +"specify a date range in the **calendar menu (📅)** for the statement, hover " +"over a partner, and click the :guilabel:`Customer Statements` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Customer statement from partner ledger report in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:381 +msgid "Remittance advice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:383 +msgid "" +"A remittance advice is a document used as proof of payment to a business. In" +" Odoo, it can be accessed by going to :menuselection:`Accounting ‣ Vendors ‣" +" Payments`, selecting the payment(s), and clicking :menuselection:`Print -->" +" Payment Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Remittance advice in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:393 +msgid "E-Invoicing via Peppol" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:395 +msgid "" +"Odoo is compliant with Australia's and New Zealand's `PEPPOL requirements " +"<https://peppol.org/learn-more/country-profiles/australia/>`_. You can find " +"and set up **electronic invoicing** settings per partner under " +":menuselection:`Accounting --> Customers` or :menuselection:`Accounting --> " +"Vendors`, select a partner, and click the :guilabel:`Accounting` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Peppol settings from a partner in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:404 +msgid "" +"Validating an invoice or credit note for a partner on the PEPPOL network " +"will download a compliant XML file that can be manually uploaded to your " +"PEPPOL network." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:410 +msgid "ABA files for batch payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:415 +msgid "" +"An ABA file is a digital format developed by the `Australian Bankers' " +"Association <https://www.ausbanking.org.au/>`_. It is designed for business " +"customers to facilitate bulk payment processing by uploading a single file " +"from their business management software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:419 +msgid "" +"The main advantage of using ABA files is to improve payment and matching " +"efficiency. This is achieved by consolidating numerous payments into one " +"file for batch processing, which can be submitted to all Australian banks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:427 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:429 +msgid "" +"To enable **batch payments**, go to :menuselection:`Accounting --> " +"Configuration --> Setting --> Batch Payment` and enable :guilabel:`Allow " +"Batch Payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:433 +msgid "Bank journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:435 +msgid "" +"Then, go to :menuselection:`Accounting --> Configuration --> Journals` and " +"select the :guilabel:`Bank` journal type. In the :guilabel:`Journal Entries`" +" tab, enter the :guilabel:`Account Number` and click :guilabel:`Create and " +"edit`. In the pop-up window, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:440 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:477 +msgid ":guilabel:`Bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:441 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:478 +msgid ":guilabel:`Account Holder Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:442 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:479 +msgid ":guilabel:`BSB`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:443 +msgid ":guilabel:`Account Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Account Number settings for ABA in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:449 +msgid "The :guilabel:`Send Money` field must be **enabled**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:452 +msgid "The :guilabel:`Currency` field is optional." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:454 +msgid "" +"Go back to the :guilabel:`Journal Entries` tab and fill in the following " +"fields related to the ABA:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:456 +msgid ":guilabel:`BSB`: This field is auto-formatted from the bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:457 +msgid "" +":guilabel:`Financial Institution Code`: The official 3-letter abbreviation " +"of the financial institution (e.g., WBC for Westpac)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:459 +msgid "" +":guilabel:`Supplying User Name`: 6-digit number provided by your bank. " +"Contact or check your bank website if you need to know." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:463 +msgid "" +":guilabel:`Include Self-Balancing Transactions`: Selecting this option adds " +"an additional" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:462 +msgid "" +"\"self-balancing\" transaction to the end of the ABA file, which some " +"financial institutions require when generating ABA files. Check with your " +"bank to see if you need this option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:465 +msgid "" +"Then, go to the :guilabel:`Outgoing Payments` tab on the same " +":guilabel:`Bank` type journal. Click :guilabel:`Add a line` and select " +":guilabel:`ABA Credit Transfer` as the **payment method**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:469 +msgid "Partners’ bank accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:471 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> Customers` or " +":menuselection:`Accounting --> Vendors --> Vendors` and select a partner for" +" whom you want to add banking information. Once selected, click the " +":guilabel:`Accounting` tab, and under the :guilabel:`Bank Accounts` section," +" click :guilabel:`Add a line` to fill in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:476 +msgid ":guilabel:`Account Number` of that partner" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:480 +msgid ":guilabel:`Accounter Holder`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:481 +msgid "" +":guilabel:`Send Money` defines the bank account as *trusted*, which is " +"essential for ABA files and must be enabled if to be used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:485 +msgid "Generate an ABA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:487 +msgid "" +"To generate an **ABA** file, :guilabel:`Create` a vendor bill (manually or " +"from a purchase order). :guilabel:`Confirm` the bill and ensure the vendor’s" +" banking information is set up correctly before registering a payment.." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:491 +msgid "" +"Next, click :guilabel:`Register Payment` in the pop-up window: select the " +":guilabel:`Bank` journal, select :guilabel:`ABA Credit Transfer` as " +":guilabel:`Payment Method`, and select the right :guilabel:`Recipient Bank " +"Account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:495 +msgid "" +"Once payments are confirmed, they appear in :menuselection:`Accounting --> " +"Vendors --> Payments`. Tick the box of the payments to be included in the " +"batch, then click :guilabel:`Create Batch`. Verify all information is " +"correct and finally :guilabel:`Validate`. Once validated, the ABA file " +"becomes available in the **chatter** on the right." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:500 +msgid "" +"After uploading it to your bank’s portal, an ABA transaction line will " +"appear in your bank feed at the following bank feed iteration. You will need" +" to reconcile it against the **batch payment** made in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:505 +msgid ":doc:`Batch Payment <../accounting/payments/batch>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:510 +msgid "Buy Now, Pay Later solutions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:512 +msgid "" +"Buy Now, Pay Later solutions are popular payment methods for eShops in " +"Australia. Some of these solutions are available via the `Stripe " +"<https://stripe.com/en-au/payments/payment-methods>`_ and `AsiaPay " +"<https://www.asiapay.com.au/payment.html#option>`_ payment providers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:517 +msgid ":doc:`AsiaPay Payment Provider <../payment_providers/asiapay>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:518 +msgid ":doc:`Stripe Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:521 +msgid "POS terminals for Australia" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:523 +msgid "" +"If you wish to have a direct connection between Odoo and your PoS terminal " +"in Australia, you *must* have a **Stripe** terminal. Odoo supports the " +"**EFTPOS** payment solution in Australia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:527 +msgid "" +"You do not need a Stripe payment terminal to use Odoo as your main PoS " +"system. The only drawback of not using Stripe is that cashiers must manually" +" enter the final payment amount on the terminal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:532 +msgid ":doc:`Stripe Odoo Payment Provider <../payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:533 +msgid "" +":doc:`Stripe Odoo Payment Terminal " +"</applications/sales/point_of_sale/payment_methods/terminals/stripe>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:534 +msgid "`Stripe Dashboard <https://dashboard.stripe.com/dashboard>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:535 +msgid "`Stripe Terminal <https://stripe.com/docs/terminal>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:540 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:150 +msgid "Payroll" +msgstr "เงินเดือน" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:543 +msgid "Odoo is currently not compliant with STP Phase 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:546 +msgid "Create your employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:548 +msgid "" +"To create an **employee form** and fill in mandatory information, go to the " +"**Employees** app and click :guilabel:`Create`. In the :guilabel:`HR " +"Settings` tab, you can input the mandatory information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:552 +msgid "" +":guilabel:`TFN Status`: if the employee provides a TFN, make sure to add it " +"to the “TFN” field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:553 +msgid ":guilabel:`Non-resident`: if the employee is a foreign resident" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:554 +msgid "" +":guilabel:`Tax-free Threshold`: if the employee is below or above the " +"threshold" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:555 +msgid "" +":guilabel:`HELP / STSL`: for all types of study and training support loans " +"(e.g. HELP, VSL, SSL…)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:556 +msgid ":guilabel:`Medicare levy Deduction`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:557 +msgid ":guilabel:`Medicare levy Exemption`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:558 +msgid ":guilabel:`Withholding for Extra Pay`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:559 +msgid "..." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:562 +msgid "Manage Australian contracts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:564 +msgid "" +"Once the employee form has been created, ensure the contract is enabled by " +"clicking the :guilabel:`Contracts` smart button or by going to " +":menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:569 +msgid "" +"Only one contract can be active simultaneously per employee, but an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:572 +msgid "" +"Contractual information related to Australia can be found in the following " +"**three** places:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:574 +msgid "" +"Before assigning a salary amount, pay frequency, and other important details" +" to a contract, defining the **salary structure**, **start date**, and " +"**work entry** source is important. In Australia, a \"Salary Structure\" is " +"employed to specify the tax schedule applicable to that contract, as defined" +" by the Australian Taxation Office (ATO). Most contracts will fall under the" +" following **three structures**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:580 +msgid "" +"**Regular (Schedule 1)**: the great majority of Australian employees will " +"fall in this category; hence, this structure is assigned by default to all " +"contracts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:582 +msgid "" +"**Working holiday makers (Schedule 15)**. When employing working holiday " +"makers (WHMs), other taxes apply. For detailed information on these specific" +" tax implications, refer to the documentation provided by the **ATO**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:585 +msgid "" +"**No TFN**. Choose this structure if the employee hasn’t provided a **TFN** " +"for over **28** days." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Employees form in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:592 +msgid "" +"The structures **Horticulture/Shearing (Schedule 2)** and **Artists and " +"Performers (Schedule 3)** are only partially complete, and proper tests " +"should be performed before using them to pay employees in your production " +"database. Send your feedback to au-feedback@mail.odoo.com." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:596 +msgid "" +"The field :guilabel:`Work Entry Source` is also significant and defines how " +"**working hours** and **days** are accounted for in the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:599 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee’s working schedule, starting from the contract's start " +"date.. For example, let’s assume that an employee works 38 hours a week, and" +" their contract’s begins on January 1st. Today is January 16th, and the user" +" generates a pay run from January 14th to 20th. The working hours on the " +"payslip will be automatically calculated to be 38 hours (5 * 7.36 hours) if " +"no leave is taken." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:604 +msgid "" +":guilabel:`Attendances`: The default working schedule is ignored, and work " +"entries are only generated after clocking in and out of the attendance app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:606 +msgid "" +":guilabel:`Planning`: The default working schedule is ignored, and work " +"entries are generated from planning shifts only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:610 +msgid "" +"Additional configurations are necessary to ensure that Odoo’s payslips " +"automatically compute various **penalty rates** as defined by an **award " +"(overtime rate, public holiday rate, etc)**. To create these configurations," +" create new work-entry types for each penalty rate and then assign a penalty" +" rate in % to each. Once this one-time configuration is done, work entries " +"can be manually imported for each period, and Odoo will separate the pay " +"items and rates on the employee’s payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:618 +msgid "Timesheets do not impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:620 +msgid "" +"The :guilabel:`Salary Information` tab contains a few essential fields " +"impacting the frequency of pay runs and the management of payslip rules in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:623 +msgid "" +":guilabel:`Wage Type`: Select the :guilabel:`Fixed Wage` pay type for full-" +"time and part-time employees. For casual workers and other :guilabel:`Hourly" +" Wage` type. For employees being paid hourly, make sure to define the " +"correct **casual loading**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:626 +msgid "" +":guilabel:`Schedule Pay`: In Australia, only the following pay run " +"frequencies are accepted: **daily, weekly, bi-weekly (or fortnightly), " +"monthly, and quarterly**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:628 +msgid "" +":guilabel:`Wage` (/period): Assign a wage to the contract according to their" +" pay frequency. On payslips, the corresponding annual and hourly rates will " +"be automatically computed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:632 +msgid "" +"For hourly workers, please note that the hourly wage should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:634 +msgid "" +"The :guilabel:`Australia` tab. Most of the fields in this tab are used for " +"**Single Touch Payroll** (or **STP**) reporting, which requires a thorough " +"understanding of several details from an employee’s contract. Review the " +"information on this tab before moving forward with pay runs. This includes " +"the following **four** fields which impact payslip computations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:639 +msgid "" +":guilabel:`Withholding Variation`: use this field in case the employee’s " +"withholding must be varied upward or downward according to their " +"circumstances. E.g., if employee X benefits from a 25% withholding " +"variation, their percentage of tax withheld will vary from whatever amount " +"they were supposed to pay according to their salary structure and situation " +"to a fixed 25%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:643 +msgid "" +":guilabel:`Leave Loading`: if the employee benefits from a regular leave " +"loading, the value set in the field :guilabel:`Leave Loading Rate` (e.g., " +"17.5%) is added to any amount earned when taking annual or long service " +"leaves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:646 +msgid "" +":guilabel:`Salary Sacrifice Superannuation`: any amount added to this field " +"is deducted, per pay frequency, from the employee’s basic salary before the " +"computation of the gross salary. Then, this amount is added to the super " +"guarantee line of their payslip. E.g., if employee Y earns 5,000 AUD per " +"month and sacrifices 300 AUD to superannuation, their gross salary will be " +"4,700 AUD, and 300 AUD will be added on top of their normal super " +"contributions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:651 +msgid "" +":guilabel:`Salary Sacrifice Other`: any amount added to this field is " +"deducted, per pay frequency, from the employee’s basic salary before the " +"computation of the gross salary." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:654 +msgid "" +"Once all important information has been entered, ensure the transition of " +"the contract's status from \"New\" to \"Running\" to facilitate its use in " +"pay runs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "\"Australia\" payroll tab in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:661 +msgid "Assign superannuation accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:663 +msgid "" +"Upon receipt of superannuation details from a new employee, ensure the " +"creation of a new account in :menuselection:`Payroll --> Configuration --> " +"Super Accounts` to link it to the employee. Input the :guilabel:`Super " +"Fund`, :guilabel:`Member Since` date, and :guilabel:`TFN` number of the " +"employee." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:667 +msgid "" +"Suppose the employee uses a superannuation fund that does not exist in the " +"database yet. In that case Odoo creates a new one and centralises basic " +"information about this fund, such as its **ABN**, **address**, type " +"(**APRA** or **SMSF**), **USI**, and **ESA**. Super funds can be created or " +"imported in :menuselection:`Payroll --> Configuration --> Super Funds`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:673 +msgid "Odoo is currently not **SuperStream-compliant**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:676 +msgid "Create pay runs with payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:678 +msgid "" +"Odoo can create pay runs in **two** ways: via **batch** or via " +"**individual** payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:681 +msgid "Create a batch of payslips" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:683 +msgid "" +"When preparing to generate employees’ draft payslips (e.g., at the end of " +"every week, fortnight, or month), navigate to :menuselection:`Payroll --> " +"Payslips --> Batches` and click :guilabel:`New`. Fill in the necessary info," +" click :guilabel:`Generate Payslips`, select the :guilabel:`Salary " +"Structure`, :guilabel:`Department`, :guilabel:`Employees`, and " +":guilabel:`Generate`. This method allows the creation of multiple payslips " +"corresponding to each employee in a single batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:690 +msgid "Give the batch a name. (E.g., `2024 – Weekly W1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:691 +msgid "" +"Choose the pay run's start and end date. (E.g., 01/01/2024 to 07/01/2024)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:692 +msgid "" +"Click on :guilabel:`Generate`. A pop-up window asks to confirm which " +"employees should be included in the batch. By default, all active employees " +"are included. You can leave :guilabel:`Salary Structure` field blank as Odoo" +" automatically selects the structure linked to each employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:696 +msgid "" +"The batch creates as many payslips as there are employees. There is no limit" +" to the number of payslips created in a batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:698 +msgid "" +"Verify important information on each payslip. After payslips from a batch " +"have been generated, there is no need to manually compute payslip lines; " +"Odoo does it for you." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:702 +msgid "Create an individual payslip" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:704 +msgid "" +"In cases where the pay run does not fall into the category of regular " +"payslips, the option exists to create a pay run dedicated to a single " +"employee. Go to :menuselection:`Payroll --> Payslips --> All Payslips` and " +"click :guilabel:`New`. Employ this method when processing **one-time " +"payments** for employees, including **return-to-work** payments (**ATO " +"Schedule 4**), **employment termination** payments (**ATO Schedule 7 and " +"11**), and **commissions and bonuses** (**ATO Schedule 5**). When generating" +" an individual payslip, make sure to proceed with the following steps:" +msgstr "" +"ในกรณีที่การดำเนินการจ่ายเงินไม่อยู่ในหมวดหมู่ของสลิปเงินเดือนปกติ " +"มีตัวเลือกในการสร้างการดำเนินการจ่ายเงินสำหรับพนักงานคนเดียวโดยเฉพาะ ไปที่ " +":menuselection:`บัญชีเงินเดือน --> สลิปเงินเดือน --> สลิปเงินเดือนทั้งหมด` " +"และคลิก :guilabel:`สร้าง` ใช้วิธีนี้เมื่อประมวลผล " +"**การชำระเงินแบบครั้งเดียว** สำหรับพนักงาน รวมถึงการชำระเงิน " +"**การกลับไปทำงาน** (**ATO Schedule 4**), **การเลิกจ้าง** การชำระเงิน (**ATO " +"Schedule 7 และ 11**) และ **ค่าคอมมิชชั่นและโบนัส** (**ATO Schedule 5**) " +"เมื่อสร้างสลิปเงินเดือนแต่ละรายการ โปรดดำเนินการตามขั้นตอนต่อไปนี้:" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:711 +msgid "" +"Select an :guilabel:`Employee`; their :guilabel:`Contract` will be filled " +"out automatically" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:712 +msgid "Add a pay :guilabel:`Period`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:713 +msgid "Select a salary :guilabel:`Structure` (e.g., return-to-work payment)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:714 +msgid "" +"Unlike payslips generated from a batch, the payroll user must click the " +":guilabel:`Compute Sheet` button to generate payslip lines" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "One-time payments in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:721 +msgid "Understand payslip features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:723 +msgid "" +"The same features apply no matter how payslips are created (individually or " +"via batch)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:725 +msgid "" +"Depending on how work entries are created, the :guilabel:`Worked Days & " +"Inputs` table automatically shows the number of days and hours the employee " +"worked during the payslip period next to the corresponding total gross " +"amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:730 +msgid "" +"There is one line per work entry type, meaning **paid** and **unpaid time-" +"off**, in addition to custom **hourly penalty rates** (overtime, public " +"holidays, etc.) which are automatically added to the table." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Worked days and hours in Payroll" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:737 +msgid "" +"In the :guilabel:`Other Inputs` section, You can add entries such as " +"**allowances** and **extra pay** items in the :guilabel:`Other Inputs` " +"section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:740 +msgid "" +"To incorporate various **allowances** into an employee's payslip, create " +"**allowances** in :menuselection:`Payroll --> Configuration --> Other Input " +"Types`. Once created, tick the :guilabel:`Is an Allowance` checkbox for the " +"involved allowances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:745 +msgid "" +"Withholding for allowances is not computed automatically. The payroll user " +"has to use the field :guilabel:`Withholding for allowance` under the other " +"inputs table to manually add the total amount to be withheld across all " +"allowances on that payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:749 +msgid "" +"**Extra pay** items are other inputs added to the **payslip’s gross** and, " +"as a result, to the **withholding amount**. An example lies in regular sales" +" commissions, taxed at the same rate as the regular salary (unlike " +"discretionary bonuses, which fall under the ATO’s Schedule 5 and its " +"corresponding salary structure). To configure such a custom pay item, go to " +":menuselection:`Payroll --> Configuration --> Other Input Types` and create " +"a new entry with the code **EXTRA**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Extra pay item input type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:759 +msgid "" +"In the :guilabel:`Salary Computation` tab, the payroll user can verify " +"whether all the pay rules have been computed correctly as per employee, " +"contract and salary structure. Here are a few guidelines to better " +"understand the data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Salary computation in Odoo Payroll." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:766 +msgid "" +"**Basic salary:** amount from which tax-deductible lines can be subtracted" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:767 +msgid "" +"**Gross salary:** amount subject to the taxes defined by the salary " +"structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:768 +msgid "**Withholding:** tax amount to be paid to the **ATO**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:769 +msgid "**Net salary:** amount to be paid to the employee’s bank account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:770 +msgid "" +"**Superannuation Guarantee:** amount to be provisioned for quarterly " +"payments to the employee’s super account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:772 +msgid "" +"**Allowances & Extra pay items:** these lines will show if other inputs are " +"added to the payslip." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:773 +msgid "" +"**Other lines:** depending on the employee and contract specifics (Medicare," +" child support, salary, sacrifice, etc.)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:776 +msgid "" +"When satisfied with the payslip, click :guilabel:`Create Draft entry` to " +"generate a draft accounting journal entry that the accountant can review. " +"Note that in the case of a payslip batch, this accounting entry will sum up " +"balances from all payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:781 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:783 +msgid "" +"After a batch or a payslip’s journal entry has been posted, the company can " +"pay their employees. The user can choose between **two** different **payment" +" methods**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:786 +msgid "" +"Pay the employee in batch via **ABA** files. This is **only** possible from " +"the **payslip batch** level. Ensure the batch’s journal entry has been " +"posted to generate the **ABA** file. From the batch form view, click " +":guilabel:`Create ABA File` and choose the desired bank journal. The newly " +"generated **ABA** file becomes available for download in the field " +":guilabel:`ABA File`. It is possible to re-generate the ABA file after " +"applying corrections to existing payslips." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:793 +msgid "" +"It is always possible to include an individual payslip into an existing " +"batch in an **ABA** file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:797 +msgid "" +"An ABA file can only be generated if both the company’s bank account and " +"each employee’s bank account have been properly :ref:`configured " +"<australia/aba>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:800 +msgid "" +"From the employee's payslip (:menuselection:`Payroll --> Payslips`), once " +"the payslip's journal entry has been posted, click :guilabel:`Register " +"Payment`. The process is the same as :doc:`paying vendor bills " +"<../accounting/payments>`: select the desired bank journal and payment " +"method, then later reconcile the payment with the corresponding bank " +"statement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:806 +msgid "One-time payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:808 +msgid "" +"Certain payments, such as **Return-to-Work** payments and **Employment " +"Termination Payments** **(ETP)**, are processed only once and require a " +"slightly different approach." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:812 +msgid "Return-to-Work payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:814 +msgid "" +"A **Return-to-Work** payment is a payment made to an employee to resume " +"working. To process one, create an individual payslip, select the employee, " +"and modify its **regular structure** to :guilabel:`Australia: Return to " +"work`. Then, add the **gross amount** of that payment in the " +":guilabel:`Other Inputs` section and compute the payslip. Odoo automatically" +" computes the **PAYG withholding**, the **net amount**, and the **super " +"guarantee** corresponding to that payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Return-to-work payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:824 +msgid "Termination payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:826 +msgid "" +"Before proceeding with the employee’s ETP, make sure that a **Contract End " +"Date** has been set on that employee’s contract so that Odoo can " +"automatically compute the final prorated salary of that employee for the " +"current month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:830 +msgid "" +"First, create the final salary for that employee this month. To do so, " +"create an individual payslip. If the contract end date is set correctly, " +"Odoo will automatically compute the prorated salary up to the final payslip " +"date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Termination payment worked days computation in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:838 +msgid "" +"We recommend creating a batch on the fly for that payslip, in which the ETP " +"is added as a second payslip of that same batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:841 +msgid "" +"Create a second individual payslip and include it in the same batch. Change " +"the salary structure on that payslip to :guilabel:`Australia: Termination " +"Payments`. Before computing the sheet, it is important to provide the " +"payslip with termination details ." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Termination payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:848 +msgid "" +":guilabel:`Genuine` or :guilabel:`Non-Genuine Redundancy`. This choice " +"impacts the amounts and caps defined per **ETP** type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:850 +msgid "" +"**ETP types**: see the full list of termination payment types in " +":guilabel:`Other Input Types` by filtering by `ETP Type is Set`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Payslip other inputs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:856 +msgid "" +"Add the relevant **ETP type** in the :guilabel:`Other Inputs` table of the " +"payslip, then compute the payslip. Odoo computes the **gross ETP**, the " +"**withholding**, the **unused leaves**, and the **net salary** according to " +"the rules defined on the **ETP**, the **employee**, and their **contract**. " +"Once payment for both payslips is ready to be processed, an **ABA** file can" +" be created directly from the batch." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:865 +msgid "Employment Hero Australian Payroll" +msgstr "การจ้างงาน Hero บัญชีเงินเดือนของประเทศออสเตรเลีย" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:867 +msgid "" +"If your business is already up and running with `Employment Hero " +"<https://employmenthero.com/>`_, you can use our connector as an alternative" +" payroll solution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:870 +msgid "" +"The Employment Hero module synchronises payslip accounting entries (e.g., " +"expenses, social charges, liabilities, taxes) automatically from Employment " +"Hero to Odoo. Payroll administration is still done in Employment Hero. We " +"only record the **journal entries** in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:875 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:880 +msgid "" +":ref:`Activate <general/install>` the :guilabel:`Employment Hero Australian " +"Payroll` module (`l10n_au_keypay`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:882 +msgid "" +"Configure the **Employment Hero API** by going to :menuselection:`Accounting" +" --> Configuration --> Settings`. More fields become visible after clicking " +"on :guilabel:`Enable Employment Hero Integration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:890 +msgid "" +"You can find the API Key in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:895 +msgid "" +"The **Payroll URL** is pre-filled with `https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:898 +msgid "Do not change the **pre-filled Payroll URL**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:900 +msgid "" +"You can find the **Business ID** in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:0 +msgid "The Employment Hero \"Business ID\" number is in the URL" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:905 +msgid "You can choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:908 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:910 +msgid "" +"The API syncs the journal entries from Employment Hero to Odoo and leaves " +"them in draft mode. The reference includes the Employment Hero payslip entry" +" ID in brackets for the user to easily retrieve the same record in " +"Employment Hero and Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:917 +msgid "" +"By default, the synchronisation happens once per week. You can fetch the " +"records manually by going to :menuselection:`Accounting --> Configuration " +"--> Settings` and, in the :guilabel:`Enable Employment Hero Integration` " +"option, click on :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:921 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:923 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/australia.rst:928 +msgid "" +"For the API to work, you need to create the same accounts as the default " +"accounts of your Employment Hero business (**same name and same code**) in " +"Odoo. You also need to choose the correct account types in Odoo to generate " +"accurate financial reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:3 +msgid "Austria" +msgstr "ประเทศออสเตรีย" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:8 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Austrian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:17 +msgid ":guilabel:`Austria - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:18 +msgid "`l10n_at`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:19 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:19 +msgid "" +"Default :ref:`fiscal localization package <fiscal_localizations/packages>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:20 +msgid ":guilabel:`Austria - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:21 +msgid "`l10n_at_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:22 +msgid "Adds localized versions of financial reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:23 +msgid ":guilabel:`Austrian SAF-T Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:24 +msgid "`l10n_at_saft`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:25 +msgid "Adds the SAF-T export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:30 +msgid "The following localized reports are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:32 +msgid "" +"Balance sheet according to `§ 224 UGB " +"<https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001702&Artikel=&Paragraf=224&Anlage=&Uebergangsrecht=>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:33 +msgid "" +"Profit and loss according to `§ 231 UGB " +"<https://www.ris.bka.gv.at/NormDokument.wxe?Abfrage=Bundesnormen&Gesetzesnummer=10001702&Artikel=&Paragraf=231&Anlage=&Uebergangsrecht=>`_" +" (Gesamtkostenverfahren)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:36 +msgid ":doc:`Accounting reporting documentation <../accounting/reporting>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:39 +msgid "SAF-T (Standard Audit File for Tax)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:41 +msgid "" +"The Austrian tax office may request a SAF-T. The Austrian SAF-T Export " +"module allows exporting the report in XML format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:47 +msgid "" +"This section explains how to configure the database to ensure all the " +"information required by the SAF-T is available. If anything is missing, a " +"warning message listing which information is needed will be displayed during" +" the export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:52 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:68 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 +msgid "Company information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:54 +msgid "" +"Open the database :guilabel:`Settings`. Under the :guilabel:`Companies` " +"section, click :guilabel:`Update Info` and ensure the following fields are " +"correctly filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:57 +msgid ":guilabel:`Address`, by providing at least the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:59 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:76 +msgid ":guilabel:`Street`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:60 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +msgid ":guilabel:`City`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:61 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:79 +msgid ":guilabel:`ZIP`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:62 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 +msgid ":guilabel:`Country`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:64 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:82 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 +msgid ":guilabel:`Phone`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:65 +msgid ":guilabel:`Company ID` by providing your company's tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:66 +msgid "" +":guilabel:`Tax ID` by providing, if you have one, your :abbr:`UID-Nummer " +"(Umsatzsteueridentifikationsnummer)` (including the country prefix)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:70 +msgid "Contact person" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:72 +msgid "" +"At least one **contact person** must be linked to your company in the " +":guilabel:`Contacts` app, and:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:74 +msgid "Ensure the contact type is set to :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:75 +msgid "Select your company in the :guilabel:`Company name` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:76 +msgid "" +"Provide at least one phone number using the :guilabel:`Phone` or " +":guilabel:`Mobile` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:79 +msgid "Customer and supplier information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:81 +msgid "" +"Using the :guilabel:`Contacts` app, fill in the :guilabel:`Address` of any " +"partner that appears in your invoices, vendor bills, or payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:84 +msgid "" +"For partners that are companies, fill in the VAT number (including the " +"country prefix) in the :guilabel:`Tax ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:88 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +msgid "Accounting settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:90 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Austrian localization` section, fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:93 +msgid ":guilabel:`ÖNACE-Code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:94 +msgid ":guilabel:`Profit Assessment Method`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:97 +msgid "" +"`ÖNACE information on the Austrian Economic Chambers website " +"<https://www.wko.at/service/zahlen-daten-fakten/oenace.html>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:101 +msgid "Chart of accounts mapping" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:103 +msgid "" +"The Austrian SAF-T specifications define a chart of accounts (COA). All " +"relevant accounts for the SAF-T export must be annotated with a fitting " +"account from this COA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:106 +msgid "" +"The needed mapping information is supplied by adding tags to the accounts. " +"For example, adding the `1000` tag to an account maps it (virtually) to the " +"SAF-T COA account with the code `1000`. Any number can be used as long as " +"there is an account in the SAF-T COA with that code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:110 +msgid "" +"The :guilabel:`Austria - Accounting` module adds a tag for each SAF-T COA " +"account. Furthermore, it automatically maps many accounts from the default " +"Austrian COA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:113 +msgid "" +"You can try exporting the SAF-T report to check if there are unmapped " +"accounts (or mapped to multiple SAF-T accounts). A warning will be displayed" +" if there is any issue with your configuration or the mapping. Clicking " +":guilabel:`View Problematic Accounts` lets you view them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:118 +msgid "" +":doc:`Chart of accounts documentation " +"<../accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:121 +msgid "Exporting the SAF-T report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst:123 +msgid "" +"To export the SAF-T report, go to :menuselection:`Accounting --> Reports -->" +" General Ledger`. Click the right side of the :guilabel:`PDF` button and " +"select :guilabel:`SAF-T`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/austria.rst-1 +msgid "The SAF-T button to export the file in XML format" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "ประเทศเบลเยียม" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:10 +msgid "" +"Install the :guilabel:`🇧🇪 Belgium` :ref:`fiscal localization package " +"<fiscal_localizations/packages>` to get all the default accounting features " +"of the Belgian localization, following the :abbr:`IFRS(International " +"Financial Reporting Standards)` rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:19 +msgid "" +"You can reach the :guilabel:`Chart of accounts` by going to " +":menuselection:`Accounting --> Configuration --> Accounting: Chart of " +"Accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:22 +msgid "" +"The Belgian chart of accounts includes pre-configured accounts as described " +"in the :abbr:`PCMN(Plan Comptable Minimum Normalisé)`. To add a new account," +" click :guilabel:`New`. A new line appears. Fill it in, click " +":guilabel:`Save`, and then :guilabel:`Setup` to configure it further." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:34 +msgid "" +"Default Belgian taxes are created automatically when the :guilabel:`Belgium " +"- Accounting` and the :guilabel:`Belgium - Accounting Reports` modules are " +"installed. Each tax impacts the Belgian :guilabel:`Tax Report`, available by" +" going to :menuselection:`Accounting --> Reporting --> Statements Reports: " +"Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:39 +msgid "" +"In Belgium, the standard VAT rate is **21%**, but there are lower rates for " +"some categories of goods and services. An intermediate rate of **12%** is " +"applied on social housing and food served in restaurants, while a reduced " +"rate of **6%** applies to most basic goods, such as food, water supply, " +"books, and medicine. A **0%** rate applies to some exceptional goods and " +"services, such as some daily and weekly publications, as well as recycled " +"goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:48 +msgid "Non-deductible taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:50 +msgid "" +"In Belgium, some taxes are not fully deductible, such as taxes on the " +"maintenance of cars. This means a part of these taxes is considered as an " +"expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:53 +msgid "" +"In Odoo, you can configure non-deductible taxes by creating tax rules for " +"these taxes and linking them to the corresponding accounts. This way, the " +"system automatically calculates the taxes and allocates them to the " +"appropriate accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:57 +msgid "" +"To configure a new non-deductible tax, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Taxes`, and click :guilabel:`New`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:60 +msgid "" +":guilabel:`Add a line` and select :guilabel:`Base` in the :guilabel:`Based " +"On` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:61 +msgid "" +":guilabel:`Add a line`, then select :guilabel:`on tax` in the " +":guilabel:`Based on` column and enter the **non-deductible** percentage in " +"the :guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:63 +msgid "" +"On the :guilabel:`of tax` line, select the :guilabel:`Tax Grid(s)` related " +"to your tax;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:64 +msgid "" +":guilabel:`Add a line` with the **deductible** percentage in the " +":guilabel:`%` column;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:65 +msgid "Set :guilabel:`of tax` in :guilabel:`Based On`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 +msgid "" +"Select :guilabel:`411000 VAT recoverable` as account, and select the related" +" tax grid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:68 +msgid "" +"Once you have created a non-deductible tax, you can apply it to your " +"transactions by selecting the appropriate tax during the encoding of bills " +"and credit notes. The system automatically calculates the tax amount and " +"allocates it to the corresponding accounts based on the tax rules " +"configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:73 +msgid "" +"With the Belgian localization, the **21% car** tax is created by default " +"(50% non-deductible)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Example of not-fully deductible tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:80 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:50 +msgid ":doc:`../accounting/reporting/tax_returns`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:87 +msgid "Here is the list of Belgian-specific reports available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:89 +msgid "Balance sheet;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:90 +msgid "Profit & loss;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:91 +msgid "Tax report;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:92 +msgid "Partner VAT Listing;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:93 +msgid "EC Sales List;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:94 +msgid "Intrastat." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:96 +msgid "" +"You can access Belgian-specific versions of reports by clicking on the " +"**book** icon when on a report and selecting its Belgian version: **(BE)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Belgian version of reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:103 +msgid ":doc:`../accounting/reporting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:108 +msgid "Disallowed expenses report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:110 +msgid "" +"**Disallowed expenses** are expenses that can be deducted from your " +"accounting result but not from your fiscal result." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:113 +msgid "" +"The **disallowed expenses report** is available by going to " +":menuselection:`Accounting --> Reporting --> Management: Disallowed " +"Expenses`. It allows financial results in real-time, and periodic changes. " +"This report is generated based on the **disallowed expenses categories** " +"that you can reach by going to :menuselection:`Accounting --> Configuration " +"--> Management: Disallowed Expenses Categories`. Some categories already " +"exist by default but do not have any rates. Click on :guilabel:`Set Rates` " +"to update a specific category." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:121 +msgid "" +"You can add multiple rates for various dates. In that case, the rate used to" +" calculate the expense depends on the date at which it is calculated, and " +"the rate set for that date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:123 +msgid "" +"If you have the **Fleet** app installed, tick the :guilabel:`Car Category` " +"box when applicable. This makes the vehicle mandatory while booking a vendor" +" bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:126 +msgid "" +"To link a disallowed expenses category with a specific account, go to " +":menuselection:`Accounting --> Configuration --> Acounting: Chart of " +"Accounts`. Find the account you want, and click on :guilabel:`Setup`. Add " +"the :guilabel:`Disallowed Expense category` in the :guilabel:`Disallowed " +"Expenses` field. From now, when an expense is created with this account, the" +" disallowed expense is calculated based on the rate mentioned in the " +":guilabel:`Disallowed Expense category`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:132 +msgid "Let's take an example reflecting **restaurant** and **car expenses**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:137 +msgid "Restaurant expenses" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:139 +msgid "" +"In Belgium, 31% of **restaurant** expenses are non-deductible. Create a new " +"**disallowed expenses category** and set both :guilabel:`Related Account(s)`" +" and :guilabel:`Current Rate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Disallowed expenses categories" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:148 +msgid "Car expenses: vehicle split" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:150 +msgid "" +"In Belgium, the deductible percentage varies from car to car and, therefore," +" should be indicated for each vehicle. To do so, open :menuselection:`Fleet`" +" and select a vehicle. In the :guilabel:`Tax info` tab, go to the " +":guilabel:`Disallowed Expenses Rate` section and click on :guilabel:`Add a " +"line`. Add a :guilabel:`Start Date` and a :guilabel:`%`. The amounts go in " +"the same account for all car expenses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:156 +msgid "" +"When you create a bill for car expenses, you can link each expense to a " +"specific car by filling the :guilabel:`Vehicle` column, so the right " +"percentage is applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:162 +msgid "" +"The :guilabel:`vehicle split` option available in the disallowed expenses " +"report allows you to see the rate and disallowed amount for each car." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:171 +msgid "Fee form 281.50 and form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:176 +msgid "Fee form 281.50" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:178 +msgid "" +"Annually, a **281.50 fee form** must be reported to the fiscal authorities. " +"To do so, the tag `281.50` must be added on the **contact form** of the " +"entities concerned by the **281.50** fee. To add the tag, open " +":menuselection:`Contacts`, select the person or company you want to create a" +" **281.50 fee form** for, and add the `281.50` tag in the :guilabel:`Tags` " +"field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "add the tag 281.50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:187 +msgid "" +"Make sure the **street, zip code, country**, and **VAT number** are also " +"informed on the **Contact form**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:190 +msgid "" +"Then, depending on the nature of the expense, add the corresponding `281.50`" +" tag on the impact accounts. To do so, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Chart of Accounts`, and click on " +":guilabel:`Setup` to add the corresponding `281.50` tag on the impacted " +"accounts, i.e., :guilabel:`281.50 - Commissions`, depending on the nature of" +" the expense." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:198 +msgid "Form 325" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:200 +msgid "" +"You can create a **325 form** by going to :menuselection:`Accounting --> " +"Reporting --> Belgium: Create 325 form`. A new page pops up: select the " +"right options and click :guilabel:`Generate 325 form`. To open an already " +"generated **325 form**, go to :menuselection:`Accounting --> Reporting --> " +"Belgium: Open 325 forms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Add the tag 281-50 on a contact form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:211 +msgid "CODA and SODA statements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:216 +msgid "CODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:218 +msgid "" +"**CODA** is an electronic XML format used to import Belgian bank statements." +" You can download CODA files from your bank and import them directly into " +"Odoo by clicking :guilabel:`Import Statement` from your :guilabel:`Bank` " +"journal on your dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Import CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:226 +msgid ":ref:`Import bank statements files <transactions/import>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:231 +msgid "SODA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:233 +msgid "" +"**SODA** is an electronic XML format used to import accounting entries " +"related to salaries. SODA files can be imported into the journal you use to " +"record salaries by going to your Accounting **dashboard** and clicking " +":guilabel:`Upload` in the related journal card form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:237 +msgid "" +"Once your **SODA** files are imported, the entries are created automatically" +" in your 'salary' journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Import SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:246 +msgid "CodaBox" +msgstr "CodaBox" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:248 +msgid "" +"**CodaBox** is a service that allows Belgian accounting firms accessing " +"their clients' bank information and statements. Odoo provides a way to " +"import such statements automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:252 +msgid "" +"As an accounting firm, you must manage your clients on separate databases " +"and configure them individually to avoid mixing up their data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:258 +msgid "" +"The configuration must be done on each client database. In the following " +"instructions, we will refer to your client's company as *Company* and to " +"your accounting firm as *Accounting Firm*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:262 +msgid "" +"You must first :ref:`Install <general/install>` :guilabel:`CodaBox` and " +":guilabel:`CodaBox Bridge` to start." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:266 +msgid "" +"Make sure the company settings are correctly configured, i.e., the country " +"is set to :guilabel:`Belgium`, the :guilabel:`Tax ID` and " +":guilabel:`Accounting Firm` fields are filled, as well as the :guilabel:`Tax" +" ID` of the accounting firm (unless it is the same as the company's " +":guilabel:`Tax ID`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:272 +msgid "Configure the Journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:276 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:351 +msgid "For CODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:278 +msgid ":doc:`Create a new bank journal <../accounting/bank>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:279 +msgid "Set the right IBAN in the :guilabel:`Account Number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:280 +msgid "" +"Select :guilabel:`CodaBox synchronisation` as the :guilabel:`Bank Feed`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a CODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:286 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:361 +msgid "For SODA files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:288 +msgid "Create a new miscellaneous journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:289 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 +msgid "Select the journal you just created in the SODA journal field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configuration of a SODA journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:299 +msgid "Configure the Connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:301 +msgid "" +"First, you must select which users can access the **CodaBox** connection " +"settings. To do so, go to :menuselection:`Settings --> Users & Companies -->" +" Groups`, and search for the group :guilabel:`Allow to show and modify the " +"CodaBox Connection Settings`. Add the users you want to this group. By " +"default, only the :guilabel:`Administrator` is part of this group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:306 +msgid "" +"Then, to configure the connection itself, go to :menuselection:`Accounting " +"--> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:309 +msgid "" +"The procedure differs depending on whether **CodaBox** is being setup for a " +"first client or an additional one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 +msgid "First connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:316 +msgid "" +"Click on :guilabel:`Connect`, where you are redirected to the **CodaBox** " +"platform, here validate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:318 +msgid "" +"Once redirected back to Odoo, the :guilabel:`Status` should be set to " +":guilabel:`Connected` and a new field :guilabel:`Access Token` should " +"appear." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Configured connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 +msgid "" +"This :guilabel:`Access Token` will be used to create new connections for " +"other clients without having to validate the connection again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:329 +msgid "Following connection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:331 +msgid "Copy the :guilabel:`Access Token` from a previous connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 +msgid "Click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +msgid "" +"The **CodaBox** connection linked to the :guilabel:`Access Token` should " +"still exist, therefore there is no need to validate the connection again. A " +"new and different :guilabel:`Access Token` is generated, and the " +":guilabel:`Status` should be set to :guilabel:`Connected`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:340 +msgid "" +"By having a different :guilabel:`Access Token` for each client, you can " +"easily revoke the access of a client to your CodaBox account without " +"affecting the other clients. One client cannot interfere with another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:345 +msgid "Synchronisation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:347 +msgid "" +"Once the connection is established, Odoo can be synchronized with CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:353 +msgid "" +"CODA files are automatically imported from CodaBox every 12 hours. You do " +"not have to do anything. However, if you wish, it can also be done manually," +" by clicking on :guilabel:`Fetch CODA's` in the Accounting Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch CODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:363 +msgid "" +"SODA files are automatically imported from CodaBox once a day as draft. You " +"do not have to do anything. However, if you wish, it can also be done " +"manually, by clicking on :guilabel:`Fetch SODA's` in the Accounting " +"Dashboard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 +msgid "" +"By default, if an account in the SODA is not mapped to an account in Odoo, " +"the Suspense Account (499000) is used and a note is left in the created " +"journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:0 +msgid "Manually fetch SODA's." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 +msgid "" +"You can access the mapping between the SODA accounts and the Odoo accounts " +"by clicking on the :guilabel:`SODA Mapping` button in " +":menuselection:`Accounting --> Configuration --> Accounting: CodaBox`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:380 +msgid "" +"The connection between Odoo and CodaBox can be revoked by using the " +":guilabel:`Revoke` button in the CodaBox settings, which will revoke the " +"link on Odoo's side only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:384 +msgid "" +"If you have multiple connections, you will still be able to use the Access " +"Token of one of them to easily reconnect Odoo and CodaBox for another " +"client." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:388 +msgid "" +"However, if you have only one (remaining) connection, you will not be able " +"to use its Access Token to create new connections. In that case, you will " +"have to revoke the connection from the CodaBox platform too, and then " +"recreate a new one following the steps in the :ref:`first connection " +"<belgium/codabox-configuration-connection>` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:395 +msgid "Potential issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "CodaBox is not configured. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +msgid "Either the Company VAT of the Accounting Firm VAT is not set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "" +"It seems that the fiduciary VAT number you provided is not valid. Please " +"check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:401 +msgid "" +"Either the Company VAT of the Accounting Firm VAT is in the wrong format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "" +"It seems that the fiduciary VAT number you provided does not exist in " +"CodaBox. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +msgid "" +"The Accounting Firm VAT number you provided is not registered in CodaBox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 +msgid "Error while connecting to the IAP server. Please contact Odoo support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:407 +msgid "" +"It seems that Odoo's IAP server is down or unreachable. Please contact Odoo " +"support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:414 +msgid "" +"It seems that your CodaBox connection is not valid anymore. Please check " +"your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 +msgid "" +"It seems that you have either revoked the access of Odoo to your CodaBox " +"account, or that you have not completed the configuration process. In this " +"case, you must click on the :guilabel:`Revoke connection` button in the " +"settings, and follow again the steps in the :ref:`first connection " +"<belgium/codabox-configuration-connection>` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:423 +msgid "" +"A previous CodaBox registration already exists. Paste the access token from " +"a previous connection here. Odoo will generate a new one, exclusive to this " +"database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:417 +msgid "" +"It seems that you have already your Accounting Firm with Odoo, but that the " +"Access Token is either not filled or wrong. You should follow the steps in " +"the :ref:`following connection <belgium/codabox-configuration-connection>` " +"tab section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 +msgid "" +"If you have lost your Access Token, you have to go on the CodaBox platform, " +"and revoke the access of Odoo to your CodaBox account. Then, you will have " +"to follow the steps in the :ref:`first connection <belgium/codabox-" +"configuration-connection>` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "" +"The provided access token is not valid for this fiduciary. Please check your" +" configuration. If you have lost your access token, please contact Odoo " +"support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:426 +msgid "Same as above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:433 +msgid "" +"It seems that no connection linked to your database/VAT number exists. " +"Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 +msgid "" +"You may obtain this error when revoking or trying to fetch files from " +"CodaBox if the pair (Accounting Firm VAT, Company VAT) is not registered " +"yet. This may happen if you have changed the company VAT after the " +"connection was established for instance. For security reasons, you have to " +"recreate a connection for this company VAT by following the steps in the " +":ref:`first connection <belgium/codabox-configuration-connection>` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:438 +msgid "No files were found. Please check your configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 +msgid "" +"This may occur if the company VAT has changed after the connection was " +"established. In that case, you must click on the :guilabel:`Revoke " +"connection` button in the settings, and recreate the connection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:443 +msgid "" +"It seems you have already created a connection to CodaBox with this " +"fiduciary. To create a new connection, you must first revoke the old one on " +"myCodaBox portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:441 +msgid "" +"You must go on the CodaBox platform, and revoke the access of Odoo to your " +"CodaBox account. Then, you will have to follow the steps in the :ref:`first " +"connection <belgium/codabox-configuration-connection>` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:446 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 +msgid "Electronic invoicing" +msgstr "การออกใบแจ้งหนี้อิเล็กทรอนิกส์" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:448 +msgid "" +"Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing " +"format. To enable it for a customer, go to :menuselection:`Accounting --> " +"Customers --> Customers`, open their contact form, and under the " +":guilabel:`Accounting` tab, select the :guilabel:`Peppol BIS Billing 3.0` " +"format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:453 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:94 +msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 +msgid "Cash discount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:460 +msgid "" +"In Belgium, if an early payment discount is offered on an invoice, the tax " +"is calculated based on the discounted total amount, whether the customer " +"benefits from the discount or not." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 +msgid "" +"To apply the right tax amount and report it correctly in your VAT return, " +"set the tax reduction as :guilabel:`Always (upon invoice)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:467 +msgid ":doc:`../accounting/customer_invoices/cash_discounts`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 +msgid "Fiscal certification: POS restaurant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:474 +msgid "" +"In Belgium, the owner of a cooking business such as a restaurant or food " +"truck is required by law to use a government-certified **Cash Register " +"System** for their receipts. This applies if their yearly earnings " +"(excluding VAT, drinks, and take-away food) exceed 25,000 euros." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 +msgid "" +"This government-certified system entails the use of a :ref:`certified POS " +"system <belgium/certified-pos>`, along with a device called a :ref:`Fiscal " +"Data Module <belgium/fdm>` (or **black box**) and a :ref:`VAT Signing Card " +"<belgium/vat>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:483 +msgid "" +"Do not forget to register as *foodservice industry manager* on the `Federal " +"Public Service Finance registration form " +"<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:489 +msgid "Certified POS system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:491 +msgid "" +"The Odoo POS system is certified for the major versions of databases hosted " +"on **Odoo Online** and **Odoo.sh**. Please refer to the following table to " +"ensure that your POS system is certified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:499 +#: ../../content/applications/finance/payment_providers/stripe.rst:17 +msgid "Odoo Online" +msgstr "Odoo Online" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:500 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:501 +msgid "On-Premise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:502 +msgid "Odoo 16.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:503 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:504 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:511 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:512 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:515 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:516 +msgid "Certified" +msgstr "ได้รับการรับรอง" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:505 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:507 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:508 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:509 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:513 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:517 +msgid "Not certified" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:506 +msgid "Odoo 15.2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:510 +msgid "Odoo 15.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:514 +msgid "Odoo 14.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:520 +msgid ":doc:`/administration/maintain/supported_versions`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:522 +msgid "" +"A `certified POS system " +"<https://www.systemedecaisseenregistreuse.be/systemes-certifies>`_ must " +"adhere to rigorous government regulations, which means it operates " +"differently from a non-certified POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 +msgid "On a certified POS, you cannot:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:528 +msgid "" +"Set up and use the **global discounts** feature (the `pos_discount` module " +"is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:530 +msgid "" +"Set up and use the **loyalty programs** feature (the `pos_loyalty` module is" +" blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 +msgid "" +"Reprint receipts (the `pos_reprint` module is blacklisted and cannot be " +"activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:533 +msgid "Modify prices in order lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 +msgid "Modify or delete order lines in POS orders." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:535 +msgid "Sell products without a valid VAT number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 +msgid "Use a POS that is not connected to an IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:538 +msgid "" +"The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` " +"feature must be activated and set to a :guilabel:`Rounding Precision` of " +"`0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:541 +msgid "" +"Taxes must be set as included in the price. To set it up, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, and from the " +":guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form " +"by clicking the arrow next to the default sales tax field. There, click " +":guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:545 +msgid "" +"At the start of a POS session, users must click :guilabel:`Work in` to clock" +" in. Doing so allows the registration of POS orders. If users are not " +"clocked in, they cannot make POS orders. Likewise, they must click " +":guilabel:`Work Out` to clock out at the end of the session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:550 +msgid "" +"If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you " +"cannot use it again without it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:556 +msgid "Fiscal Data Module (FDM)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:558 +msgid "" +"An FDM, or **black box**, is a government-certified device that works " +"together with the Point of Sale application and saves your POS orders " +"information. Concretely, a **hash** (:dfn:`unique code`) is generated for " +"each POS order and added to its receipt. This allows the government to " +"verify that all revenue is declared." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:564 +msgid "" +"Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 " +"<https://www.systemedecaisseenregistreuse.be/fr/systemes-" +"certifies#FDM%20certifiés>`_ is supported by Odoo. `Contact the manufacturer" +" (GCV BMC) <https://www.boîtenoire.be/contact>`_ to order one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:572 +msgid "" +"Before setting up your database to work with an FDM, ensure you have the " +"following hardware:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:574 +msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 +msgid "an RS-232 serial null modem cable per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:576 +msgid "an RS-232 serial-to-USB adapter per FDM;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:577 +msgid "an :ref:`IoT Box <belgium/iotbox>` (one IoT box per FDM); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:578 +msgid "a receipt printer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:583 +msgid "Black box module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:585 +msgid "" +"As a pre-requisite, :ref:`activate <general/install>` the `Belgian " +"Registered Cash Register` module (technical name: `pos_blackbox_be`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "black box modules for belgian fiscal certification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:591 +msgid "" +"Once the module is activated, add your VAT number to your company " +"information. To set it up, go to :menuselection:`Settings --> Companies --> " +"Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national " +"registration number for every staff member who operates the POS system. To " +"do so, go to the :guilabel:`Employees` app and open an employee form. There," +" go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and " +"fill in the :guilabel:`INSZ or BIS number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "ISNZ or BIS number field on employee form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:601 +msgid "" +"To input your information, click on your avatar, go to :menuselection:`My " +"Profile --> Preference tab`, and enter your INSZ or BIS number in the " +"designated field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:605 +msgid "" +"You must configure the :abbr:`FDM (Fiscal Data Module)` directly in the " +"production database. Utilizing it in a testing environment may result in " +"incorrect data being stored within the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:611 +msgid "IoT Box" +msgstr "กล่อง IoT " + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:613 +msgid "" +"In order to use an :abbr:`FDM (Fiscal Data Module)`, you need a registered " +"IoT Box. To register your IoT box, you must contact us through our `support " +"contact form <https://www.odoo.com/help>`_ and provide the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:617 +msgid "your VAT number;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:618 +msgid "your company's name, address, and legal structure; and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:619 +msgid "the Mac address of your IoT Box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:621 +msgid "" +"Once your IoT box is certified, :doc:`connect " +"<../../productivity/iot/config/connect>` it to your database. To verify that" +" the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the " +":guilabel:`IOT Device` section, which should display the FDM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst-1 +msgid "Hardware status page on a registered IoT Box" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:628 +msgid "" +"Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale" +" --> Configuration --> Point of Sale`, select your POS, scroll down to the " +":guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. " +"Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:633 +msgid "" +"To be able to use an FDM, you must at least connect one :guilabel:`Receipt " +"Printer`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:638 +msgid "VAT signing card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:640 +msgid "" +"When you open a POS session and make your initial transaction, you are " +"prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`." +" The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` " +"upon `registration " +"<https://www.systemedecaisseenregistreuse.be/fr/enregistrement>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:3 +msgid "Brazil" +msgstr "ประเทศบราซิล" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:12 +msgid "" +"With the Brazilian localization, sales taxes can be automatically computed " +"and electronic invoices (NF-e) for goods can be sent using AvaTax (Avalara) " +"through |API| calls. Moreover, taxes for services can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:16 +msgid "" +"For the goods tax computation and electronic invoicing process, you need to " +"configure the :ref:`contacts <brazil/contacts>`, :ref:`company " +"<brazil/company>`, :ref:`products <brazil/products>`, and :ref:`create an " +"account in Avatax <brazil/avatax-account>` need to be configured in the " +"general settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:21 +msgid "" +"For the services taxes, you can create and configure them from Odoo directly" +" without computing them with AvaTax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:24 +msgid "" +"The localization also includes taxes and a chart of accounts template that " +"can be modified if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:30 +msgid "" +"Install the :guilabel:`🇧🇷 Brazil` :ref:`fiscal localization package " +"<fiscal_localizations/packages>` to get all the default accounting features " +"of the Brazilian localization, following the :abbr:`IFRS (International " +"Financial Reporting Standards)` rules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:39 +msgid "" +"To configure your company information, go to the :menuselection:`Contacts` " +"app and search the name given to your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:42 +msgid "" +"Select the :guilabel:`Company` option at the top of the page. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:45 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:245 +msgid ":guilabel:`Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:46 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:246 +msgid "" +":guilabel:`Address` (add :guilabel:`City`, :guilabel:`State`, :guilabel:`Zip" +" Code`, :guilabel:`Country`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:49 +msgid "" +"In the :guilabel:`Street` field, enter the street name, number, and any " +"additional address information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:51 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:250 +msgid "In the :guilabel:`Street 2` field, enter the neighborhood." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:53 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:252 +msgid ":guilabel:`Identification Number` (:guilabel:`CNPJ`, :guilabel:`CPF`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:54 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:253 +msgid ":guilabel:`Tax ID` (associated with the identification type)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:55 +msgid ":guilabel:`IE` (State registration)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:56 +msgid ":guilabel:`IM` (Municipal registration)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:57 +msgid "" +":guilabel:`SUFRAMA code` (Superintendence of the Manaus Free Trade Zone - " +"add if applicable)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:58 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:257 +msgid ":guilabel:`Phone`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:59 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:258 +msgid ":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Company configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:64 +msgid "" +"Configure the :guilabel:`Fiscal Information` within the :guilabel:`Sales and" +" Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:66 +msgid "" +"Add the :guilabel:`Fiscal Position` for :ref:`Avatax Brazil <brazil/fiscal-" +"positions>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:67 +msgid ":guilabel:`Tax Regime` (Federal Tax Regime)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:68 +msgid "" +":guilabel:`ICMS Taxpayer Type` (indicates ICMS regime, Exempt status, or " +"Non-Taxpayer)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:69 +msgid ":guilabel:`Main Activity Sector`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Company fiscal configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:74 +msgid "Finally, upload a company logo and save the contact" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:77 +msgid "" +"If you are a simplified regime, you need to configure the ICMS rate under " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes --> " +"Avatax Brazil`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:83 +msgid "Configure AvaTax integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:85 +msgid "" +"Avalara AvaTax is a tax calculation and electronic invoicing provider that " +"can be integrated in Odoo to automatically compute taxes by taking into " +"account the company, contact (customer), product, and transaction " +"information to retrieve the correct tax to be used and process the e-invoice" +" afterward with the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:90 +msgid "" +"Using this integration requires :doc:`In-App-Purchases (IAPs) " +"<../../general/in_app_purchase>` to compute the taxes and to send the " +"electronic invoices. Whenever you compute taxes, an |API| call is made using" +" credits from your |IAP| credits balance." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 +msgid "Odoo is a certified partner of Avalara Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:100 +msgid "" +"To activate AvaTax in Odoo, you need to create an account. To do so, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and in" +" the :guilabel:`AvaTax Brazil` section, add the administration email address" +" to be used for the AvaTax portal in the :guilabel:`Avatax Portal Email`, " +"and then click on :guilabel:`Create account`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:106 +msgid "" +"When **testing** an :guilabel:`Avatax Portal Email` integration in a testing" +" or sandbox database, use an alternate email address. It is **not** possible" +" to re-use the same email address on the production database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:110 +msgid "" +"After you create the account from Odoo, you need to go to the Avalara Portal" +" to set up your password:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:113 +msgid "" +"Access the `Avalara portal <https://portal.avalarabrasil.com.br/Login>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:114 +msgid "Click on :guilabel:`Meu primeiro acesso`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:115 +msgid "" +"Add the email address you used in Odoo to create the Avalara/Avatax account," +" and then click :guilabel:`Solicitar Senha`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:117 +msgid "" +"You will receive an email with a token and a link to create your password. " +"Click on this link and copy-paste the token to allocate your desired " +"password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:121 +msgid "" +"You can start using AvaTax in Odoo for tax computation **only** without " +"creating a password and accessing the Avalara portal in the Odoo database. " +"However, in order to use the electronic invoice service, you **must** access" +" the AvaTax portal and upload your certificate there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Avatax account configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:129 +msgid "" +"You can transfer |API| credentials. Use this only when you have already " +"created an account in another Odoo instance and wish to reuse it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:133 +msgid "A1 certificate upload" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:135 +msgid "" +"In order to issue electronic invoices, a certificate needs to be uploaded to" +" the `AvaTax portal <https://portal.avalarabrasil.com.br/Login>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:138 +msgid "" +"The certificate will be synchronized with Odoo, as long as the external " +"identifier number in the AvaTax portal matches - without special characters " +"- with the CNPJ number, and the identification number (CNPJ) in Odoo matches" +" with the CNPJ in AvaTax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:148 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"is installed by default as part of the data set included in the localization" +" module. The accounts are mapped automatically in their corresponding taxes," +" and the default account payable and account receivable fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:153 +msgid "" +"The chart of accounts for Brazil is based on the SPED CoA, which gives a " +"baseline of the accounts needed in Brazil." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:250 +msgid "You can add or delete accounts according to the company's needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:161 +msgid "" +"In Brazil, a *series* number is linked to a sequence number range for " +"electronic invoices. The series number can be configured in Odoo on a sales " +"journal from the :guilabel:`Series` field. If more than one series is " +"needed, then a new sales journal will need to be created and a new series " +"number assigned to it for each series needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:166 +msgid "" +"The :guilabel:`Use Documents` field needs to be selected. When issuing " +"electronic and non-electronic invoices, the :guilabel:`Type` field selects " +"the document type used when creating the invoice. The :guilabel:`Type` field" +" will only be displayed if the :guilabel:`Use Documents` field is selected " +"on the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Journal configuration with the Use Documents? field checked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:175 +msgid "" +"When creating the journal, ensure the field :guilabel:`Dedicated Credit Note" +" Sequence` is unchecked, as in Brazil, sequences between invoices, credit " +"notes, and debit notes are shared per series number, which means per " +"journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:182 +msgid "" +"Taxes are automatically created when installing the Brazilian localization. " +"Taxes are already configured, and some of them are used by Avalara when " +"computing taxes on the sales order or invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:185 +msgid "" +"Taxes can be edited, or more taxes can be added. For example, some taxes " +"used for services need to be manually added and configured, as the rate may " +"differ depending on the city where you are offering the service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:190 +msgid "" +"Taxes attached to services are not computed by AvaTax. Only goods taxes are " +"computed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:192 +msgid "" +"When configuring a tax used for a service that is included in the final " +"price (when the tax is not added or subtracted on top of the product price)," +" set the :guilabel:`Tax Computation` to :guilabel:`Percentage of Price Tax " +"Included`, and, on the :guilabel:`Advanced Options` tab, check the " +":guilabel:`Included in Price` option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Tax configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:201 +msgid "" +"Do not delete taxes, as they are used for the AvaTax tax computation. If " +"deleted, Odoo creates them again when used in an |SO| or invoice and " +"computing taxes with AvaTax, but the account used to register the tax needs " +"to be re-configured in the tax's :guilabel:`Definition` tab, under the " +":guilabel:`Distribution for invoices` and :guilabel:`Distribution for " +"refunds` sections." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:207 +msgid ":doc:`Taxes functional documentation <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:212 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:253 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:820 +msgid "Products" +msgstr "สินค้า" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:214 +msgid "" +"To use the AvaTax integration on sale orders and invoices, first specify the" +" following information on the product:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:217 +msgid "" +":guilabel:`CEST Code` (Code for products subject to ICMS tax substitution)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:218 +msgid "" +":guilabel:`Mercosul NCM Code` (Mercosur Common Nomenclature Product Code)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:219 +msgid "" +":guilabel:`Source of Origin` (Indicates the origin of the product, which can" +" be foreign or domestic, among other possible options depending on the " +"specific use case)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 +msgid "" +":guilabel:`SPED Fiscal Product Type` (Fiscal product type according to SPED " +"list table)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:222 +msgid "" +":guilabel:`Purpose of Use` (Specify the intended purpose of use for this " +"product)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Product configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:228 +msgid "" +"Odoo automatically creates three products to be used for transportation " +"costs associated with sales. These are named `Freight`, `Insurance`, and " +"`Other Costs`. They are already configured, if more need to be created, " +"duplicate and use the same configuration (configuration needed: " +":guilabel:`Product Type` `Service`, :guilabel:`Transportation Cost Type` " +"`Insurance`, `Freight`, or `Other Costs`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:265 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:40 +msgid "Contacts" +msgstr "การติดต่อ" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:239 +msgid "" +"Before using the integration, specify the following information on the " +"contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:241 +msgid "General information about the contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:243 +msgid "" +"Select the :guilabel:`Company` option for a contact with a tax ID (CNPJ), or" +" check :guilabel:`Individual` for a contact with a CPF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:249 +msgid "" +"In the :guilabel:`Street` field, enter the street, number, and any extra " +"address information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:254 +msgid ":guilabel:`IE`: state tax identification number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:255 +msgid ":guilabel:`IM`: municipal tax identification number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:256 +msgid ":guilabel:`SUFRAMA code`: SUFRAMA registration number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:264 +msgid "" +"The :guilabel:`CPF`, :guilabel:`IE`, :guilabel:`IM`, and :guilabel:`SUFRAMA " +"code` fields are are hidden until the :guilabel:`Country` is set to " +"`Brazil`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:267 +msgid "" +"Fiscal information about the contact under the :guilabel:`Sales \\& " +"Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:269 +msgid "" +":guilabel:`Fiscal Position`: add the AvaTax fiscal position to automatically" +" compute taxes on sale orders and invoices automatically" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:271 +msgid ":guilabel:`Tax Regime`: federal tax regime" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:272 +msgid "" +":guilabel:`ICMS Taxpayer Type`: taxpayer type determines if the contact is " +"within the ICMS regime, if it is exempt, or if it is a non-taxpayer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:274 +msgid "" +":guilabel:`Main Activity Sector`: list of main activity sectors of the " +"contact" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:0 +msgid "Contact fiscal configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:282 +msgid "Fiscal positions" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:284 +msgid "" +"To compute taxes and send electronic invoices on sale orders and invoices, " +"both the :guilabel:`Detect Automatically` and the :guilabel:`Use AvaTax API`" +" options need to be enabled in the :guilabel:`Fiscal Position`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:288 +msgid "" +"The :guilabel:`Fiscal Position` can be configured on the contact or selected" +" when creating a sales order or an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Fiscal position configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 +msgid "Workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:297 +msgid "" +"This section provides an overview of the actions that trigger `API calls " +"<https://en.wikipedia.org/wiki/API>`_ for tax computation, and how to send " +"an electronic invoice for goods (NF-e) for government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:302 +msgid "" +"Please note that each |API| call incurs a cost. Be mindful of the actions " +"that trigger these calls to manage costs effectively." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:309 +msgid "Tax calculations on quotations and sales orders" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:311 +msgid "" +"Trigger an |API| call to calculate taxes on a quotation or sales order " +"automatically with AvaTax in any of the following ways:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:314 +msgid "**Quotation confirmation**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:315 +msgid "Confirm a quotation into a sales order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:316 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:332 +msgid "**Manual trigger**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:317 +msgid "Click on :guilabel:`Compute Taxes Using Avatax`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:318 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:334 +msgid "**Preview**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:319 +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:335 +msgid "Click on the :guilabel:`Preview` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:320 +msgid "**Email a quotation / sales order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:321 +msgid "Send a quotation or sales order to a customer via email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:324 +msgid "**Online quotation access**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:323 +msgid "" +"When a customer accesses the quotation online (via the portal view), the " +"|API| call is triggered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:327 +msgid "Tax calculations on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:329 +msgid "" +"Trigger an |API| call to calculate taxes on a customer invoice automatically" +" with AvaTax any of the following ways:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:333 +msgid "Click on :guilabel:`Compute Taxes Using AvaTax`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +msgid "**Online invoice access**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:337 +msgid "" +"When a customer accesses the invoice online (via the portal view), the |API|" +" call is triggered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:340 +msgid "" +"The :guilabel:`Fiscal Position` must be set to `Automatic Tax Mapping " +"(Avalara Brazil)` for any of these actions to compute taxes automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:344 +msgid "" +":doc:`Fiscal positions (tax and account mapping) " +"<../accounting/taxes/fiscal_positions>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:92 +msgid "Electronic documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:354 +msgid "" +"To process an electronic invoice for goods (NF-e), the invoice needs to be " +"confirmed and taxes need to be computed by Avalara. Once that step is done, " +"click on the :guilabel:`Send \\& Print` button in the upper left corner, and" +" a pop-up will appear. Then click on :guilabel:`Process e-invoice` and any " +"of the other options - :guilabel:`Download` or :guilabel:`Email`. Finally, " +"click on :guilabel:`Send \\& Print` to process the invoice against the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:360 +msgid "" +"Before sending the electronic invoice for goods (NF-e) some fields need to " +"be filled out on the invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:363 +msgid ":guilabel:`Customer` with all the customer information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:364 +msgid "" +":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:365 +msgid "" +":guilabel:`Fiscal Position` set as the :guilabel:`Automatic Tax Mapping " +"(Avalara Brazil)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:368 +msgid "" +":guilabel:`Document Type` set as :guilabel:`(55) Electronic Invoice (NF-e)`." +" This is the only" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:367 +msgid "" +"electronic document supported at the moment. Non-electronic invoices can be " +"registered, and other document types can be activated if needed" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:370 +msgid "" +"There are some other optional fields that depend on the nature of the " +"transaction. These fields are not required, so no errors will appear from " +"the government if these optional fields are not populated for most cases:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:374 +msgid "" +":guilabel:`Freight Model` determines how the goods are planned to be " +"transported - domestic" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:375 +msgid "" +":guilabel:`Transporter Brazil` determines who is doing the transportation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Invoice information needed to process an electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Process electronic invoice pop-up in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:384 +msgid "" +"All of the fields available on the invoice used to issue an electronic " +"invoice are also available on the sales order, if needed. When creating the " +"first invoice, the field :guilabel:`Document Number` is displayed, allocated" +" as the first number to be used sequentially for subsequent invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:390 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 +msgid "Credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:392 +msgid "" +"If a sales return needs to be registered, then a credit note can be created " +"in Odoo to be sent to the government for validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:396 +msgid ":ref:`Issue a credit note <accounting/issue-credit-note>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:399 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:585 +msgid "Debit Notes" +msgstr "ใบเพิ่มหนี้" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:401 +msgid "" +"If additional information needs to be included, or values need to be " +"corrected that were not accurately provided in the original invoice, a debit" +" note can be issued." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:405 +msgid "" +"Only the products included in the original invoice can be part of the debit " +"note. While changes can be made to the product's unit price or quantity, " +"products **cannot** be added to the debit note. The purpose of this document" +" is only to declare the amount that you want to add to the original invoice " +"for the same or fewer products." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:411 +msgid ":ref:`Issue a debit note <accounting/issue-debit-note>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:414 +msgid "Invoice cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:416 +msgid "" +"It is possible to cancel an electronic invoice that was validated by the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:419 +msgid "" +"Check whether the electronic invoice is still within the cancellation " +"deadline, which may vary according to the legislation of each state." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:422 +msgid "" +"This can be done in Odoo by clicking :guilabel:`Request Cancel` and adding a" +" cancellation :guilabel:`Reason` on the pop-up that appears. If you want to " +"send this cancellation reason to the customer via email, activate the " +":guilabel:`E-mail` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Invoice cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:430 +msgid "Correction letter" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:432 +msgid "" +"A correction letter can be created and linked to an electronic invoice that " +"was validated by the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:435 +msgid "" +"This can be done in Odoo by clicking :guilabel:`Correction Letter` and " +"adding a correction :guilabel:`Reason` on the pop-up that appears. To send " +"this correction reason to a customer via email, activate the " +":guilabel:`E-mail` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Correction letter reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:443 +msgid "Invalidate invoice number range" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:445 +msgid "" +"A range of sequences that are assigned to sales journals can be invalidated " +"with the government if they are not currently used, **and** will not be used" +" in the future. To do so, navigate to the journal, and click the " +":menuselection:`⚙️ (gear) icon --> Invalidate Number Range (BR)`. On the " +":guilabel:`Invalidate Number Range (BR)` wizard, add the :guilabel:`Initial " +"Number` and :guilabel:`End Number` of the range that should be canceled, and" +" enter an invalidation :guilabel:`Reason`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Number range invalidation selection in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst-1 +msgid "Number range invalidation wizard in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:459 +msgid "" +"The log of the canceled numbers along with the XML file are recorded in the " +"chatter of the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:465 +msgid "" +"On the vendor bills side, when receiving an invoice from a supplier, you can" +" encode the bill in Odoo by adding all the commercial information together " +"with the same Brazilian specific information that is recorded on the " +":ref:`customer invoices <brazil/electronic-documents>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:469 +msgid "These Brazilian specific fields are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:471 +msgid "" +":guilabel:`Payment Method: Brazil` (how the invoice is planned to be paid)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:472 +msgid ":guilabel:`Document Type` used by your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:473 +msgid ":guilabel:`Document Number` (the invoice number from your supplier)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:474 +msgid "" +":guilabel:`Freight Model` (how goods are planned to be transported - " +"domestic)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/brazil.rst:475 +msgid ":guilabel:`Transporter Brazil` (who is doing the transportation)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:3 +msgid "Chile" +msgstr "ประเทศชิลี" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:6 +msgid "" +"Watch the two webinar recordings below for a general presentation of the " +"localization, and search the playlist for tutorials to discover practical " +"workflows while using Odoo in Chile." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:9 +msgid "`Webinar: intro and demo <https://youtu.be/BHnByZiyYcM>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:10 +msgid "`Webinar: delivery guide <https://youtu.be/X7i4PftnEdU>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:11 +msgid "" +"`Playlist of tutorials " +"<https://youtube.com/playlist?list=PL1-aSABtP6AB6UY7VUFnVgeYOaz33fb4P>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:15 +msgid "" +"`Chilean localization app tour " +"<https://www.youtube.com/watch?v=3qYkgbmBYHw>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:16 +msgid "" +"`Chilean localization smart tutorial <https://www.odoo.com/slides/smart-" +"tutorial-localizacion-de-chile-131>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:22 +msgid "Modules" +msgstr "โมดูล" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:24 +msgid "" +":ref:`Install <general/install>` the following modules to utilize all the " +"features of the Chilean localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:33 +msgid ":guilabel:`Chile - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:34 +msgid "`l10n_cl`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:35 +msgid "" +"Adds the minimal accounting features required for a company to operate in " +"Chile under the :abbr:`SII (Servicio de Impuestos Internos)` regulations and" +" guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:37 +msgid ":guilabel:`Chile - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:38 +msgid "`l10n_cl_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:39 +msgid "" +"Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:40 +msgid ":guilabel:`Chile - E-invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:41 +msgid "`l10n_cl_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:42 +msgid "" +"Includes all technical and functional requirements to generate and receive " +"electronic invoices online based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:44 +msgid ":guilabel:`Chile - Electronic Receipt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:45 +msgid "`l10n_cl_boletas`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:46 +msgid "" +"Includes all technical and functional requirements to generate and receive " +"electronic invoices digitally based on the :abbr:`SII (Servicio de Impuestos" +" Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:48 +msgid ":guilabel:`Electronic Exports of Goods for Chile`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:49 +msgid "`l10n_cl_edi_exports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:50 +msgid "" +"Includes technical and functional requirements to generate electronic " +"invoices for exporting goods based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` and customs regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:52 +msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:53 +msgid "`l10n_cl_edi_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:54 +msgid "" +"Includes all technical and functional requirements to generate delivery " +"guides via web service based on the :abbr:`SII (Servicio de Impuestos " +"Internos)` regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:58 +msgid "" +"Odoo automatically installs the appropriate package for the company " +"according to the country selected at the creation of the database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:60 +msgid "" +"The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* " +"application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:63 +msgid "" +"All features are only available if the company already completed the `SII " +"Sistema de Facturación de Mercado " +"<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" +" certification process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:70 +msgid "" +"Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure " +"the following company information is up-to-date and correctly filled in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:73 +msgid ":guilabel:`Company Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 +msgid ":guilabel:`Address`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +msgid ":guilabel:`State`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 +msgid "" +":guilabel:`Tax ID`: enter the identification number for the selected " +":ref:`Taxpayer Type <chile/fiscal-info>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 +msgid ":guilabel:`Activity Names`: select up to four activity codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:85 +msgid "" +":guilabel:`Company Activity Description`: enter a short description of the " +"company's activity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:90 +msgid "" +"Next, navigate to :menuselection:`Accounting --> Configuration --> Settings " +"--> Chilean Localization` and follow the instructions to configure the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:93 +msgid ":ref:`Fiscal information <chile/fiscal-info>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 +msgid ":ref:`Electronic invoice data <chile/electronic-invoice>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:95 +msgid ":ref:`DTE incoming email server <chile/dte-email>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:96 +msgid ":ref:`Signature certificates <chile/certificate>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:101 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 +msgid "Fiscal information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:103 +msgid "Configure the following :guilabel:`Tax payer information`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 +msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 +msgid "" +":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to " +"customers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:108 +msgid "" +":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees" +" receipt (Boleta)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 +msgid ":guilabel:`End consumer`: only issues receipts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:110 +msgid ":guilabel:`Foreigner`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 +msgid "" +":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de " +"Impuestos Internos)` regional office" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:118 +msgid "Electronic invoice data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:120 +msgid "Select your :guilabel:`SII Web Services` environment:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 +msgid "" +":guilabel:`SII - Test`: for test databases using test :abbr:`CAFs (Folio " +"Authorization Code)` obtained from the :abbr:`SII (Servicio de Impuestos " +"Internos)`. In this mode, the direct connection flows can be tested, with " +"the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +msgid ":guilabel:`SII - Production`: for production databases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:127 +msgid "" +":guilabel:`SII - Demo Mode`: files are created and accepted automatically in" +" demo mode but are **not** sent to the :abbr:`SII (Servicio de Impuestos " +"Internos)`. For this reason, rejection errors or *Accepted with Objections* " +"will not appear in this mode. Every internal validation can be tested in " +"demo mode. Avoid selecting this option in a production database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:132 +msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:134 +msgid ":guilabel:`SII Resolution N°`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:135 +msgid ":guilabel:`SII Resolution Date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Required information for electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:144 +msgid "DTE incoming email server" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:146 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`Email Box " +"Electronic Invoicing` can be defined to receive your customers' claim and " +"acceptance emails. Enabling this option from :menuselection:`Accounting --> " +"Configuration --> Settings --> Chilean Localization` is necessary if you " +"want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` incoming email server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:153 +msgid "" +"In order to receive your SII documents, it's necessary to set up your own " +"email server. More information on how to do this can be found in this " +"documentation: :doc:`../../general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 +msgid "" +"Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click " +":guilabel:`New` to add a server and fill in the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:160 +msgid ":guilabel:`Name`: give the server a name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +msgid ":guilabel:`Server Type`: select the server type used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:163 +msgid ":guilabel:`IMAP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +msgid ":guilabel:`POP Server`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 +msgid "" +":guilabel:`Local Server`: uses a local script to fetch emails and create new" +" records. The script can be found in the :guilabel:`Configuration` section " +"with this option selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 +msgid "" +":guilabel:`Gmail OAuth Authentication`: requires your Gmail API credentials " +"to be configured in the general settings. A direct link to the configuration" +" can be found in the :guilabel:`Login Information` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 +msgid "" +":guilabel:`DTE Server`: enable this option. By checking this option, this " +"email account will be used to receive the electronic invoices from the " +"suppliers, and communications from the :abbr:`SII (Servicio de Impuestos " +"Internos)` regarding the electronic invoices issued. In this case, this " +"email should match both emails declared on the :abbr:`SII (Servicio de " +"Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL " +"CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:178 +msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:180 +msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:181 +msgid ":guilabel:`Port`: enter the server port." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 +msgid "" +":guilabel:`SSL/TLS`: enable this option if connections are encrypted using " +"the SSL/TLS protocol." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:183 +msgid ":guilabel:`Username`: enter the server login username." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 +msgid ":guilabel:`Password`: enter the server login password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Incoming email server configuration for Chilean DTE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:191 +msgid "" +"Before going live, it is recommended to archive or remove all emails related" +" to vendor bills that are not required to be processed in Odoo from your " +"inbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:197 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:219 +msgid "Certificate" +msgstr "ใบรับรอง" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:199 +msgid "" +"A digital certificate in `.pfx` format is required to generate the " +"electronic invoice signature. To add one, click :guilabel:`Configure " +"Signature Certificates` under the :guilabel:`Signature Certificates` " +"section. Then, click :guilabel:`New` to configure the certificate:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 +msgid "" +":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select " +"the `.pfx` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:204 +msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:205 +msgid "" +":guilabel:`Subject Serial Number`: depending on the certificate format, the " +"field might not be automatically populated. In that case, enter the " +"certificate's legal representative :abbr:`RUT (Rol Único Tributario)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +msgid "" +":guilabel:`Certificate Owner`: select one if you need to restrict the " +"certificate for a specific user. Leave the field empty to share it with all " +"billing users." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Digital certificate configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:216 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:230 +msgid "Multicurrency" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:218 +msgid "" +"The official currency rate is provided by `Chilean mindicador.cl " +"<https://mindicador.cl>`_. Navigate to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies: Automatic Currency Rates` to set " +"an :guilabel:`Interval` for when the rate is automatically updated, or to " +"select another :guilabel:`Service`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 +#: ../../content/applications/finance/fiscal_localizations/france.rst:306 +msgid "Partner information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:228 +msgid "" +"Configuring partner contacts is also required to send :abbr:`SII (Servicio " +"de Impuestos Internos)` electronic invoices. Open the " +":menuselection:`Contacts` app to do so and fill in the following fields on a" +" new or existing contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 +msgid ":guilabel:`Identification Number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:235 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +msgid ":guilabel:`Taxpayer Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 +msgid ":guilabel:`Activity Description`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 +msgid "In the :guilabel:`Electronic Invoicing` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 +msgid "" +":guilabel:`DTE Email`: enter the sender's email address for the partner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:241 +msgid "" +":guilabel:`Delivery Guide Price`: select which price the delivery guide " +"displays, if any." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:244 +msgid "" +"The :guilabel:`DTE Email` is the email used for sending electronic documents" +" and must be set in the contact that will be part of an electronic document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean electronic invoice data for partners." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 +msgid "" +"Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos " +"Internos)`-defined document types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:257 +msgid "" +"Document types are created automatically upon installation of the " +"localization module, and can be managed by navigating to " +":menuselection:`Accounting --> Configuration --> Document Types`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean fiscal document types list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:265 +msgid "" +"Several document types are inactive by default but can be activated by " +"toggling the :guilabel:`Active` option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 +msgid "The document type on each transaction is determined by:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 +msgid "" +"The journal related to the invoice, identifying if the journal uses " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:274 +msgid "" +"The condition applied based on the type of issuer and recipient (e.g., the " +"buyer or vendor's fiscal regime)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:280 +msgid "" +"*Sales journals* in Odoo usually represent a business unit or location." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:283 +msgid "Ventas Santiago." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:284 +msgid "Ventas Valparaiso." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 +msgid "" +"For retail stores it is common to have one journal per :abbr:`POS (Point of " +"Sale)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:289 +msgid "Cashier 1." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 +msgid "Cashier 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 +msgid "" +"The *purchase* transactions can be managed with a single journal, but " +"sometimes companies use more than one journal in order to handle some " +"accounting transactions that are not related to vendor bills. This " +"configuration can easily be set by using the following model." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:297 +msgid "Tax payments to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:298 +msgid "Employees payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:301 +msgid "Create a sales journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:303 +msgid "" +"To create a sales journal, navigate to :menuselection:`Accounting --> " +"Configuration --> Journals`. Then, click the :guilabel:`New` button, and " +"fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:306 +msgid "" +":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for " +"customer invoice journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:307 +msgid "" +":guilabel:`Point of sale type`: if the sales journal will be used for " +"electronic documents, the option :guilabel:`Online` must be selected. " +"Otherwise, if the journal is used for invoices imported from a previous " +"system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` " +"portal *Facturación MiPyme*, you can use the option :guilabel:`Manual`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:311 +msgid "" +":guilabel:`Use Documents`: check this field if the journal will use document" +" types. This field is only applicable to purchase and sales journals that " +"can be related to the different sets of document types available in Chile. " +"By default, all the sales journals created will use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:315 +msgid "" +"Next, from the :guilabel:`Jounal Entries` tab, define the :guilabel:`Default" +" Income Account` and :guilabel:`Dedicated Credit Note Squence` in the " +":guilabel:`Accounting Information` section. Configuring these fields is " +"required for one of the debit notes :ref:`use cases <chile/use-cases>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:322 +msgid "CAF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:324 +msgid "" +"A *folio authorization code* (CAF) is required for each document type that " +"will be issued electronically. The :abbr:`CAF (Folio Authorization Code)` is" +" a file the :abbr:`SII (Servicio de Impuestos Internos)` provides to the " +"issuer with the folios/sequences authorized for the electronic invoice " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:329 +msgid "" +"Your company can request multiple folios and obtain several :abbr:`CAFs " +"(Folio Authorization Codes)` linked to different folio ranges. These " +":abbr:`CAFs (Folio Authorization Code)` are shared within all journals, so " +"you only need one active :abbr:`CAF (Folio Authorization Code)` per document" +" type, and it will be applied to all journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:334 +msgid "" +"Please refer to the `SII documentation " +"<https://palena.sii.cl/dte/mn_timbraje.html>`_ to check the details on how " +"to acquire the :abbr:`CAF (Folio Authorization Code)` files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:338 +msgid "" +"The :abbr:`CAFs (Folio Authorization Code)` required by the :abbr:`SII " +"(Servicio de Impuestos Internos)` are different from production to test " +"(certification mode). Make sure you have the correct :abbr:`CAF (Folio " +"Authorization Code)` set depending on your environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:343 +msgid "Upload CAF files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:345 +msgid "" +"Once the :abbr:`CAF (Folio Authorization Code)` files have been acquired " +"from the :abbr:`SII (Servicio de Impuestos Internos)` portal, they need to " +"be uploaded in the database by navigating to :menuselection:`Accounting --> " +"Configuration: Chilean SII --> CAFs`. Then, click the :guilabel:`New` begin " +"the configuration. On the :abbr:`CAF (Folio Authorization Code)` form, " +"upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the " +":guilabel:`Upload your file` button and then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:352 +msgid "" +"Once uploaded, the status changes to :guilabel:`In Use`. At this moment, " +"when a transaction is used for this document type, the invoice number takes " +"the first folio in the sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:356 +msgid "" +"The document types have to be active before uploading the :abbr:`CAF (Folio " +"Authorization Code)` files. In case some folios have been used in the " +"previous system, the next valid folio has to be set when the first " +"transaction is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:363 +msgid "" +"The chart of accounts is installed by default as part of the data set " +"included in the localization module. The accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:367 +msgid "Default Account Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:75 +msgid "Default Account Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:369 +msgid "Transfer Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 +msgid "Conversion Rate" +msgstr "อัตราการแปลง" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:378 +msgid "" +"As part of the localization module, taxes are created automatically with " +"their related financial account and configuration. These taxes can be " +"managed from :menuselection:`Accounting --> Configuration --> Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:382 +msgid "Chile has several tax types, the most common ones are:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:384 +msgid "**VAT**: the regular VAT can have several rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:385 +msgid "**ILA**: the tax for alcoholic drinks." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:388 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:106 +msgid ":doc:`../accounting/taxes`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:394 +msgid "Electronic invoice workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:396 +msgid "" +"In the Chilean localization, the electronic invoice workflow includes " +"customer invoice issuance and vendor bill reception. The following diagram " +"explains how information is shared to the :abbr:`SII (Servicio de Impuestos " +"Internos)`, customers, and vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Diagram with Electronic invoice transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:405 +msgid "Customer invoice emission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:407 +msgid "" +"After the partners and journals are created and configured, the invoices are" +" created in the standard way. For Chile, one of the differences is the " +"document type that is automatically selected based on the taxpayer. The " +"document type can be changed manually if needed on the invoice by navigating" +" to :menuselection:`Accounting --> Customers --> Invoices`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Customer invoice document type selection." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:417 +msgid "" +":guilabel:`Documents type 33` electronic invoice must have at least one item" +" with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` " +"rejects the document validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:423 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 +msgid "Validation and DTE status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:425 +msgid "" +"Once all invoice information is filled, either manually or automatically " +"when generated from a sales order, validate the invoice. After the invoice " +"is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:428 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file is created " +"automatically and recorded in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio " +"de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "DTE XML File displayed in chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:437 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` status is updated " +"automatically by Odoo with a scheduled action that runs every day at night, " +"if the response from the :abbr:`SII (Servicio de Impuestos Internos)` is " +"needed immediately, you can do it manually as well by following the " +":abbr:`DTE (Documentos Tributarios Electrónicos)` status workflow:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Transition of DTE status flow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:446 +msgid "" +"The first step is to send the :abbr:`DTE (Documentos Tributarios " +"Electrónicos)` to the :abbr:`SII (Servicio de Impuestos Internos)`. This can" +" be sent manually by clicking the :guilabel:`Enviar Ahora` button. This " +"generates a :guilabel:`SII Tack number` for the invoice, which is used to " +"check the details sent by the :abbr:`SII (Servicio de Impuestos Internos)` " +"via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for" +" Status`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:451 +msgid "" +"Once the :abbr:`SII (Servicio de Impuestos Internos)` response is received, " +"Odoo updates the :guilabel:`DTE status`. To do it manually, click on the " +"button :guilabel:`Verify on SII`. The result can either be " +":guilabel:`Accepted`, :guilabel:`Accepted With Objection` or " +":guilabel:`Rejected`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Identification transaction for invoice and Status update." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:461 +msgid "" +"There are intermediate statuses in the :abbr:`SII (Serviciqo de Impuestos " +"Internos)` before acceptance or rejection. It's recommended to **NOT** " +"continuously click :guilabel:`Verify in SII` for smooth processing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Electronic invoice data statuses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:469 +msgid "" +"The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can" +" take on one of these values:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:472 +msgid "" +":guilabel:`Accepted`: indicates the invoice information is correct, our " +"document is now fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 +msgid "" +":guilabel:`Accepted with objections`: indicates the invoice information is " +"correct, but a minor issue was identified, nevertheless the document is now " +"fiscally valid and it's automatically sent to the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:477 +msgid "" +":guilabel:`Rejected`: indicates the invoice information is incorrect and " +"must be corrected. Details are sent to emails you registered in the " +":abbr:`SII (Servicio de Impuestos Internos)`. If it is properly configured " +"in Odoo, the details are also retrieved in the chatter once the email server" +" is processed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:482 +msgid "If the invoice is rejected please follow these steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 +msgid "Change the document to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:485 +msgid "" +"Make the required corrections based on the message received from the " +":abbr:`SII (Servicio de Impuestos Internos)` in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:487 +msgid "Post the invoice again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "Message when an invoice is rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:494 +msgid "Crossed references" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 +msgid "" +"When the invoice is created, as a result of another fiscal document, the " +"information related to the originator document must be registered in the " +":guilabel:`Cross-Reference` tab. This tab is commonly used for credit or " +"debit notes, however, in some cases it can be used for customer invoices, as" +" well. In the case of the credit and debit notes, they are set automatically" +" by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Crossed referenced document(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:508 +#: ../../content/applications/finance/fiscal_localizations/india.rst:133 +#: ../../content/applications/finance/fiscal_localizations/india.rst:271 +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Invoice PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:510 +msgid "" +"Once the invoice is accepted and validated by the :abbr:`SII (Servicio de " +"Impuestos Internos)` and the PDF is printed, it includes the fiscal elements" +" that indicate that the document is fiscally valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "SII Validation fiscal elements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:519 +msgid "" +"If you are hosted in Odoo SH or On-Premise, you should manually install the " +"`pdf417gen <https://pypi.org/project/pdf417gen/>`_ library. Use the " +"following command to install it: :command:`pip install pdf417gen`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 +msgid "Commercial validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +msgid "Once the invoice has been sent to the customer:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:529 +msgid "The customer must send a reception confirmation email." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +msgid "" +"Subsequently, if commercial terms and invoice data are correct, an " +"acceptance confirmation is sent; otherwise, a claim is sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Message with the commercial acceptance from the customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 +msgid "Processed for claimed invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 +msgid "" +"Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos " +"Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for" +" your customer, the correct way to proceed is with a credit note to either " +"cancel the invoice or correct it. Please refer to the :ref:`chile/credit-" +"notes` section for more details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Commercial status updated to claimed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:551 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 +msgid "Common errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 +msgid "" +"There are multiple reasons behind a rejection from the :abbr:`SII (Servicio " +"de Impuestos Internos)`, but these are some of the common errors you might " +"have and how to solve them:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `RECHAZO- DTE Sin Comuna Origen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** make sure the company address is properly filled including the " +"state and city." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `en Monto - IVA debe declararse`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** the invoice lines should include one VAT tax, make sure you add " +"one on each invoice line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Rut No Autorizado a Firmar`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** the :abbr:`RUT (Rol Único Tributario)` entered is not allowed to " +"invoice electronically, make sure the company :abbr:`RUT (Rol Único " +"Tributario)` is correct and is valid in the :abbr:`SII (Servicio de " +"Impuestos Internos)` to invoice electronically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Error:** `Fecha/Número Resolucion Invalido RECHAZO- CAF Vencido : " +"(Firma_DTE[AAAA-MM-DD] - CAF[AAAA-MM-DD]) > 6 meses`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** try to add a new CAF related to this document as the one you're " +"using is expired." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Error:** `Element '{http://www.sii.cl/SiiDte%7DRutReceptor': This element " +"is not expected. Expected is ( {http://www.sii.cl/SiiDte%7DRutEnvia ).`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** Make sure the field :guilabel:`Document Type` and :guilabel:`VAT` " +"are set in the customer and in the main company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `Usuario sin permiso de envio.`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** this error indicates that most likely, your company has not passed" +" the `Certification process " +"<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" +" in the :abbr:`SII (Servicio de Impuestos Internos)` - Sistema de " +"Facturación de Mercado. If this is the case, please contact your Account " +"Manager or Customer Support as this certification is not part of the Odoo " +"services, but we can give you some alternatives. If you already passed the " +"certification process, this error appears when a user different from the " +"owner of the certificate is trying to send :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` files to the :abbr:`SII (Servicio de Impuestos " +"Internos)`." +msgstr "" +"**คำแนะนำ:** ข้อผิดพลาดนี้บ่งชี้ว่าเป็นไปได้มากว่าบริษัทของคุณยังไม่ผ่าน " +"`กระบวนการรับรอง " +"<https://www.sii.cl/factura_electronica/factura_mercado/proceso_certificacion.htm>`_" +" ใน :abbr:`SII (Servicio de Impuestos Internos)` - ระบบ Facturación de " +"Mercado หากเป็นกรณีนี้ โปรดติดต่อผู้จัดการบัญชีหรือฝ่ายสนับสนุนลูกค้าของคุณ " +"เนื่องจากการรับรองนี้ไม่ได้เป็นส่วนหนึ่งของบริการ Odoo " +"แต่เราสามารถให้ทางเลือกอื่นแก่คุณได้ หากคุณผ่านขั้นตอนการรับรองแล้ว " +"ข้อผิดพลาดนี้จะปรากฏขึ้นเมื่อผู้ใช้ที่ไม่ใช่เจ้าของใบรับรองพยายามส่งไฟล์ " +":abbr:`DTE (Documentos Tributarios Electrónicos)` ไปยัง :abbr:`SII (Servicio" +" de Impuestos Internos) `." + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "**Error:** `CARATULA`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "" +"**Hint:** there are just five reasons why this error could show up and all " +"of them are related to the *Caratula* section of the XML:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 +msgid "" +"The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or " +"missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:586 +msgid "" +"The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect" +" or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 +msgid "" +"The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol Único " +"Tributario)` number (this should be correct by default) is incorrect or " +"missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +msgid "The resolution date is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:590 +msgid "The resolution number is incorrect or missing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 +msgid "" +"When a cancellation or correction is needed over a validated invoice, a " +"credit note must be generated. It is important to consider that a :abbr:`CAF" +" (Folio Authorization Code)` file is required for the credit note, which is " +"identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII " +"(Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section " +"<chile/caf-documentation>` for more information on the process to load the " +":abbr:`CAF (Folio Authorization Code)` on each document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Creation of CAF for Credit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:609 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:665 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 +msgid "Cancel referenced document" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 +msgid "" +"In case you need to cancel or invalidate an invoice, navigate to " +":menuselection:`Accounting --> Customers --> Invoices` and select the " +"desired invoice. Then, use the button :guilabel:`Add Credit Note` and select" +" :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos" +" Internos)` reference code is automatically set to :guilabel:`Anula " +"Documento de referencia`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note canceling the referenced document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 +msgid "Correct referenced document" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 +msgid "" +"If a correction in the invoice information is required, for example the " +"street name on the original invoice is wrong, then use the button " +":guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select " +"the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII" +" Reference Code` field is automatically set to :guilabel:`Corrects " +"Referenced Document Text`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note correcting referenced document text." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:635 +msgid "" +"Odoo creates a credit note with the corrected text in an invoice and " +":guilabel:`Price` `0.00`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Credit note with the corrected value on the invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:642 +msgid "" +"Make sure to define the :guilabel:`Default Credit Account` in the sales " +"journal specifically for this use case." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 +msgid "Corrects referenced document amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 +msgid "" +"When a correction on the amounts is required, use the button :guilabel:`Add " +"Credit note` and select :guilabel:`Partial Refund`. In this case the " +":guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el" +" monto del Documento de Referencia`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Credit note for partial refund to correct amounts, using the SII reference " +"code 3." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 +msgid "Debit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 +msgid "" +"In Chilean localization, debit notes, in addition to credit notes, can be " +"created using the :guilabel:`Add Debit Note` button, with two main use " +"cases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 +msgid "Add debt on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 +msgid "" +"The primary use case for debit notes is to increase the value of an existing" +" invoice. To do so, select option :guilabel:`3. Corrige el monto del " +"Documento de Referencia` for the :guilabel:`Reference Code SII` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Debit note correcting referenced document amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:678 +msgid "" +"In this case Odoo automatically includes the :guilabel:`Source Invoice` in " +"the :guilabel:`Cross Reference` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Automatic reference to invoice in a debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:686 +msgid "" +"You can only add debit notes to an invoice already accepted by the SII." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 +msgid "Cancel credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 +msgid "" +"In Chile, debits notes are used to cancel a valid credit note. To do this, " +"click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: " +"Anula Documentos de referencia` option for the :guilabel:`Reference Code " +"SII` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Debit note to cancel the referenced document (credit note)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 +msgid "" +"As part of the Chilean localization, you can configure your incoming email " +"server to match the one you have registered in the :abbr:`SII (Servicio de " +"Impuestos Internos)` in order to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 +msgid "" +"Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios " +"Electrónicos)` and create the vendor bill based on this information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 +msgid "Automatically send the reception acknowledgement to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:708 +msgid "Accept or claim the document and send this status to your vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 +msgid "Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 +msgid "" +"As soon as the vendor email with the attached :abbr:`DTE (Documentos " +"Tributarios Electrónicos)` is received:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 +msgid "The vendor bill maps all the information included in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:717 +msgid "An email is sent to the vendor with the reception acknowledgement." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +msgid "" +"The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 +msgid "Acceptation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 +msgid "" +"If all the commercial information is correct on your vendor bill, then you " +"can accept the document using the :guilabel:`Aceptar Documento` button. Once" +" this is done, the :guilabel:`DTE Acceptation Status` changes to " +":guilabel:`Accepted` and an email of acceptance is sent to the vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Button for accepting vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 +msgid "Claim" +msgstr "เรียกร้อง" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:734 +msgid "" +"In case there is a commercial issue or the information is not correct on " +"your vendor bill, you can claim the document before validating it, using the" +" :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation" +" Status` changes to :guilabel:`Claim` and a rejection email is sent to the " +"vendor." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "" +"Claim button in vendor bills to inform the vendor all the document is commercially\n" +"rejected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:744 +msgid "" +"If you claim a vendor bill, the status changes from :guilabel:`Draft` to " +":guilabel:`Cancel` automatically. Considering this as best practice, all the" +" claimed documents should be canceled as they won't be valid for your " +"accounting records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 +msgid "Delivery guide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +msgid "" +"To install the :guilabel:`Delivery Guide` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery " +"Guide`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 +msgid "" +":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with " +":guilabel:`Chile - Facturación Electrónica`. Odoo will install the " +"dependency automatically when the :guilabel:`Delivery Guide` module is " +"installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:760 +msgid "" +"The *Delivery Guide* module includes the ability to send the :abbr:`DTE " +"(Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos " +"Internos)` and the stamp in PDF reports for deliveries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"<chile/electronic-invoice>` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), delivery guides need their own :abbr:`CAFs " +"(Folio Authorization Code)`. Please refer to the :ref:`CAF documentation " +"<chile/caf-documentation>` to check the details on how to acquire the " +":abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 +msgid "" +"Verify the following important information in the :guilabel:`Price for the " +"Delivery Guide` configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 +msgid "" +":guilabel:`From Sales Order`: delivery guide takes the product price from " +"the sales order and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +msgid "" +":guilabel:`From Product Template`: Odoo takes the price configured in the " +"product template and shows it on the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 +msgid ":guilabel:`No show price`: no price is shown in the delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +msgid "" +"Electronic delivery guides are used to move stock from one place to another " +"and they can represent sales, sampling, consignment, internal transfers, and" +" basically any product move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 +msgid "Delivery guide from a sales process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 +msgid "" +"A delivery guide should **not** be longer than one page or contain more than" +" 60 product lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +msgid "" +"When a sales order is created and confirmed, a delivery order is generated. " +"After validating the delivery order, the option to create a delivery guide " +"is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Create Delivery Guide button on a sales process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 +msgid "" +"When clicking on :guilabel:`Create Delivery Guide` for the first time, a " +"warning message pops up, stating the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:799 +msgid "" +"`No se encontró una secuencia para la guía de despacho. Por favor, " +"establezca el primer número dentro del campo número para la guía de " +"despacho`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:0 +msgid "First Delivery Guide number warning message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 +msgid "" +"This warning message means the user needs to indicate the next sequence " +"number Odoo has to take to generate the delivery guide (e.g. next available " +":abbr:`CAF (Folio Authorization Code)` number), and only happens the first " +"time a delivery guide is created in Odoo. After the first document has been " +"correctly generated, Odoo takes the next available number in the :abbr:`CAF " +"(Folio Authorization Code)` file to generate the following delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 +msgid "After the delivery guide is created:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:814 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " +"Document) is automatically created and added to the :guilabel:`chatter`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 +msgid "" +"The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chatter notes of Delivery Guide creation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 +msgid "" +"The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled" +" action that runs every night. To get a response from the :abbr:`SII " +"(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" +" to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +msgid "" +"Once the delivery guide is sent, it may then be printed by clicking on the " +":guilabel:`Print Delivery Guide` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Printing Delivery Guide PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:833 +msgid "" +"Delivery guide will have fiscal elements that indicate that the document is " +"fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* " +"remember to manually add the :guilabel:`pdf417gen` library mentioned in the " +":ref:`Invoice PDF report section <chile/electronic-invoice-pdf-report>`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 +msgid "Electronic receipt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 +msgid "" +"To install the :guilabel:`Electronic Receipt` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:846 +msgid "" +":guilabel:`Chile - Electronic Receipt` has a dependency with " +":guilabel:`Chile - Facturación Electrónica`. Odoo will install the " +"dependency automatically when the :guilabel:`E-invoicing Delivery Guide` " +"module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:850 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"<chile/electronic-invoice>` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), electronic receipts need their own " +":abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF " +"documentation <chile/caf-documentation>` to check the details on how to " +"acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:856 +msgid "" +"Electronic receipts are useful when clients do not need an electronic " +"invoice. By default, there is a partner in the database called " +":guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol Único " +"Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. " +"This partner can be used for electronic receipts or a new record may be " +"created for the same purpose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Electronic Receipt module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 +msgid "" +"Although electronic receipts should be used for final consumers with a " +"generic :abbr:`RUT (Rol Único Tributario)`, it can also be used for specific" +" partners. After the partners and journals are created and configured, the " +"electronic receipts are created in the standard way as electronic invoice, " +"but the type of document :guilabel:`(39) Electronic Receipt` should be " +"selected in the invoice form:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Document type 39 for Electronic Receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +msgid "" +"When all of the electronic receipt information is filled, manually (or " +"automatically) proceed to validate the receipt from the sales order. By " +"default, :guilabel:`Electronic Invoice` is selected as the " +":guilabel:`Document Type`, however in order to validate the receipt " +"correctly, make sure to edit the :guilabel:`Document Type` and change to " +":guilabel:`Electronic Receipt`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 +msgid "After the receipt is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 +msgid "" +"The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax " +"Document) is created automatically and added to the :guilabel:`chatter`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Electronic Receipts STE creation status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 +msgid "" +"The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled" +" action that runs every day at night. To get a response from the :abbr:`SII " +"(Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now" +" to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +msgid "" +"Please refer to the :ref:`DTE Workflow <chile/electronic-invoice-" +"validation>` for electronic invoices as the workflow for electronic receipt " +"follows the same process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 +msgid "Electronic export of goods" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 +msgid "" +"To install the :guilabel:`Electronic Exports of Goods` module, go to " +":menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click " +":guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for" +" Chile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:907 +msgid "" +":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency " +"with :guilabel:`Chile - Facturación Electrónica`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:910 +msgid "" +"Once all configurations have been made for :ref:`electronic invoices " +"<chile/electronic-invoice>` (e.g., uploading a valid company certificate, " +"setting up master data, etc.), electronic exports of goods need their own " +":abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF " +"documentation <chile/caf-documentation>` to check the details on how to " +"acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:916 +msgid "" +"Electronic invoices for the export of goods are tax documents that are used " +"not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also " +"used with customs and contain the information required by it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:921 +msgid "Contact configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Taxpayer Type needed for the Electronic Exports of Goods module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 +msgid "Chilean customs" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 +msgid "" +"When creating an electronic exports of goods invoice, these new fields in " +"the :guilabel:`Other Info` tab are required to comply with Chilean " +"regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean customs fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 +msgid "PDF report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 +msgid "" +"Once the invoice is accepted and validated by the :abbr:`SII (Servicio de " +"Impuestos Internos)` and the PDF is printed, it includes the fiscal elements" +" that indicate that the document is fiscally valid and a new section needed " +"for customs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "PDF report section for the Electronic Exports of Goods PDF Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 +msgid "eCommerce electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +msgid "" +"To install the :guilabel:`Chilean eCommerce` module, go to " +":menuselection:`Apps, search for the module by its technical name " +"`l10n_cl_edi_website_sale`, and click the :guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "l10n_cl eCommerce module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:958 +msgid "This module enables the features and configurations to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:960 +msgid "Generate electronic documents from the *eCommerce* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:961 +msgid "Support for required fiscal fields in the *eCommerce* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 +msgid "" +"Effectively let the final client decide the electronic document to be " +"generated for their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 +msgid "" +"Once all of the configurations are made for the Chilean :ref:`electronic " +"invoice <chile/electronic-invoice>` flow, the following configurations are " +"required for the eCommerce flow to be integrated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 +msgid "" +"To configure your website to generate electronic documents during the sale " +"process, go to :menuselection:`Website --> Configuration --> Settings --> " +"Invoicing` and activate the :guilabel:`Automatic Invoice` feature. " +"Activating this feature allows electronic documents to be automatically " +"generated when an online payment is confirmed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Policy and Automatic Invoice configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:978 +msgid "" +"Since an online payment needs to be confirmed for the *automatic invoice* " +"feature to generate the document, a payment provider must be configured for " +"the related website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:982 +msgid "" +"Review the :doc:`../payment_providers` documentation for information on " +"which payment providers are supported in Odoo, and how to configure them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:985 +msgid "" +"It is also recommended to configure your products so they are able to be " +"invoiced when an online payment is confirmed. To do so, go to " +":menuselection:`Website --> eCommerce --> Products` and select the product " +"template of the desired product. Then, set the :guilabel:`Invoicing Policy` " +"to :guilabel:`Ordered quantities`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Invoice Policy configuration in Products." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:995 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1081 +msgid "Invoicing flows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:997 +msgid "" +"Clients from Chile will be able to select if they need an **invoice** or a " +"**ballot** for their purchase with an extra step added during the checkout " +"process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Option for EDI Documents for clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1004 +msgid "" +"If the customer selects the :guilabel:`Electronic Invoice` option, fiscal " +"fields are required to be filled out, including the :guilabel:`Activity " +"Description`, the :guilabel:`Identification Number` and their :guilabel:`DTE" +" Email`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Fiscal fields required for an Invoice to be requested." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1012 +msgid "" +"If the client selects the :guilabel:`Electronic Receipts` option, they will " +"be directed to the next step, and the electronic document will be generated " +"for the *Consumidor Final Anónimo* contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1015 +msgid "" +"Clients from countries other than Chile, will have their electronic receipts" +" automatically generated for them by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 +msgid "" +"If a purchase through eCommerce requires an export, the customer will need " +"to contact your company to generate an electronic export invoice (*document " +"type 110*), which can be done from the *Accounting* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1024 +msgid "Point of Sale electronic invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1026 +msgid "" +"To install the :guilabel:`Chilean Module for Point of Sale`, go to the " +":menuselection:`Apps` application on the main Odoo dashboard, search for the" +" module by its technical name `l10n_cl_edi_pos`, and click the " +":guilabel:`Activate` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "l10n_cl POS EDI module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 +msgid "This module enables the following features and configurations to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1036 +msgid "Generate electronic documents from the *Point of Sale* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1037 +msgid "" +"Support the required fiscal fields for contacts created in the *Point of " +"Sale* application" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1038 +msgid "" +"Effectively lets the final client decide the type of electronic document to " +"be generated for their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1040 +msgid "Print QR or 5-digit codes in tickets to access to electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 +msgid "" +"To configure contacts with the required fiscal information, review the " +":ref:`partner information <chile/partner-information>` section, or directly " +"modify a contact. Navigate to :menuselection:`Point of Sale --> Session --> " +"Customers --> Details`, and edit any of the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1049 +msgid ":guilabel:`Identification Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1050 +msgid ":guilabel:`Tax Payer Type`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1051 +msgid ":guilabel:`Type Giro`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 +msgid ":guilabel:`DTE Email`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 +msgid ":guilabel:`RUT`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Contact with fiscal information created from POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1059 +msgid "" +"To configure the products, navigate to :menuselection:`Point of Sale --> " +"Products --> Products` and select a product record. In the :guilabel:`Sales`" +" tab of the product form, it is necessary to mark the product as " +":guilabel:`Available for POS`, this makes the product available for sale in " +"the *Point of Sale* app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Product with fiscal information created from POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 +msgid "" +"Optionally, the following features are available for configuration in the " +":menuselection:`Point of Sale --> Configuration --> Settings --> Bills & " +"Receipts section`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1071 +msgid "" +":guilabel:`Use QR code on ticket`: this feature enables a QR code to be " +"printed on the user's receipt so they can easily request an invoice after " +"their purchase" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 +msgid "" +":guilabel:`Generate a code on ticket`: this feature enables a 5-digit code " +"to be generated on the receipt, allowing the user to request an invoice " +"through the customer portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Configuration to generate QR or 5 digit codes on tickets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 +msgid "" +"The following sections cover the invoicing flows for the *Point of Sale* " +"application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 +msgid "Electronic receipts: anonymous end user" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1088 +msgid "" +"When making a purchase as an anonymous user that does not request an " +"electronic invoice, Odoo automatically selects :guilabel:`Consumidor Final " +"Anónimo` as the contact for the order and generates the electronic receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Automatic contact selection of an anonymous end consumer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 +msgid "" +"If the client requests a credit note due to a return of their purchase, the " +"credit note should be made using the *Accounting* app. See the :doc:`credit " +"notes and refunds <../accounting/customer_invoices/credit_notes>` " +"documentation for detailed instructions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 +msgid "Electronic receipts: specific customer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1104 +msgid "" +"When specific user makes a purchase that does not request an electronic " +"invoice, Odoo automatically selects the contact for the order as the " +":guilabel:`Consumidor Final Anónimo`, and allows you to select or create the" +" required customer contact with their fiscal information for the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of contact for the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1113 +msgid "" +"If the client requests a credit note because of a return of this type of " +"purchase, the credit note and return process can be managed directly from " +"the :abbr:`POS (Point of Sale)` session." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 +msgid "Electronic invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1119 +msgid "" +"When clients request an electronic invoice, it is possible to select or " +"create the required contact with their fiscal information. When the payment " +"is being made, select the option :guilabel:`Invoice` to generate the " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of invoice option at payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1128 +msgid "" +"For both the electronic receipts and invoices, if the product is not " +"affected by taxes, Odoo detects this and generates the correct type of " +"document for tax-exempt sales." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 +msgid "Returns" +msgstr "ส่งคืน" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1134 +msgid "" +"For electronic receipts (not generated for the *Consumidor Final Anónimo*) " +"and electronic invoices, it is possible to manage the process to return " +"products sold in a :abbr:`POS (Point of Sale)` order by selecting the " +":guilabel:`Refund` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Refund option in the POS application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1142 +msgid "" +"Orders can be searched by the order status or by contact, and be selected " +"for the refund to be based on the client's original order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Selection of order for the refund process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1149 +msgid "" +"When the return payment is validated, Odoo generates the necessary credit " +"note, referencing the original receipt or invoice, partially or fully " +"canceling the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 +msgid "" +"`Smart tutorial - Electronic invoicing for point of sale " +"<https://www.youtube.com/watch?v=B2XuWmtlmno&t=360s>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1160 +msgid "Balance tributario de 8 columnas" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 +msgid "" +"This report presents the accounts in detail (with their respective " +"balances), classifying them according to their origin and determining the " +"level of profit or loss that the business had within the evaluated period of" +" time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 +msgid "" +"You can find this report in :menuselection:`Accounting --> Reporting --> " +"Balance Sheet` and selecting in the :guilabel:`Report` field the option " +":guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Location of the Reporte Balance Tributario de 8 Columnas." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Chilean Fiscal Balance (8 Columns)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1179 +msgid "Propuesta F29" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 +msgid "" +"The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos " +"Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales " +"Books*. This report is integrated by Purchase Register (CR) and the Sales " +"Register (RV). Its purpose is to support the transactions related to VAT, " +"improving its control and declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1186 +msgid "" +"This record is supplied by the electronic tax documents (DTE's) that have " +"been received by the :abbr:`SII (Servicio de Impuestos Internos)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1189 +msgid "" +"You can find this report in :menuselection:`Accounting --> Reporting --> Tax" +" Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta " +"F29 (CL)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Location of the Propuesta F29 (CL) Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1196 +msgid "" +"It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` " +"and the :guilabel:`Proportional Factor for the fiscal year` from the " +":menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1204 +msgid "" +"Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst-1 +msgid "Manual PPM for the Propuesta F29 Report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:3 +msgid "Colombia" +msgstr "ประเทศโคลัมเบีย" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:7 +msgid "" +"Odoo's Colombian localization package provides accounting, fiscal, and legal" +" features for databases in Colombia – such as chart of accounts, taxes, and " +"electronic invoicing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:10 +msgid "" +"In addition, a series of videos on the subject is also available. These " +"videos cover how to start from scratch, set up configurations, complete " +"common workflows, and provide in-depth looks at some specific use cases as " +"well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:15 +msgid "" +"`Smart Tutorial - Colombian Localization <https://www.odoo.com/slides/smart-" +"tutorial-localizacion-de-colombia-132>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:26 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:36 +msgid ":guilabel:`Colombia - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:37 +msgid "`l10n_co`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:38 +msgid "" +"Default :ref:`fiscal localization package <fiscal_localizations/packages>`. " +"This module adds the base accounting features for the Colombian " +"localization: chart of accounts, taxes, withholdings, and identification " +"document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:41 +msgid ":guilabel:`Colombian - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:42 +msgid "`l10n_co_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:43 +msgid "" +"Includes accounting reports for sending certifications to suppliers for " +"withholdings applied." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:44 +msgid ":guilabel:`Electronic invoicing for Colombia with Carvajal`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:45 +msgid "`l10n_co_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:46 +msgid "" +"This module includes the features required for integration with Carvajal, " +"and generates the electronic invoices and support documents related to the " +"vendor bills, based on |DIAN| regulations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:49 +msgid ":guilabel:`Colombian - Point of Sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:50 +msgid "`l10n_co_pos`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:51 +msgid "Includes Point of Sale receipts for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:54 +msgid "" +"When `Colombia` is selected for a company's :guilabel:`Fiscal Localization`," +" Odoo automatically installs certain modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:58 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:60 +msgid "" +"To configure your company information, go to the :menuselection:`Contacts` " +"app, and search for your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:63 +msgid "" +"Alternatively, activate :ref:`developer mode <developer-mode>` and navigate " +"to :menuselection:`General Setting --> Company --> Update Info --> Contact`." +" Then, edit the contact form and configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:67 +msgid ":guilabel:`Company Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:68 +msgid "" +":guilabel:`Address`: Including :guilabel:`City`, :guilabel:`Department` and " +":guilabel:`ZIP` code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:69 +msgid "" +":guilabel:`Identification Number`: Select the :guilabel:`Identification " +"Type` (`NIT`, `Cédula de Ciudadanía`, `Registro Civil`, etc.). When the " +":guilabel:`Identification Type` is `NIT`, the :guilabel:`Identification " +"Number` **must** have the *verification digit* at the end of the ID prefixed" +" by a hyphen (`-`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:74 +msgid "" +"Next, configure the :guilabel:`Fiscal Information` in the :guilabel:`Sales &" +" Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:76 +msgid "" +":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal " +"responsibility for the company (`O-13` Gran Contribuyente, `O-15` " +"Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de " +"tributación simple, `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:79 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:173 +msgid "" +":guilabel:`Gran Contribuyente`: If the company is *Gran Contribuyente* this " +"option should be selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:81 +msgid "" +":guilabel:`Fiscal Regimen`: Select the Tribute Name for the company (`IVA`, " +"`INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:83 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:177 +msgid "" +":guilabel:`Commercial Name`: If the company uses a specific commercial name," +" and it needs to be displayed in the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:87 +msgid "Carjaval credentials configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:89 +msgid "" +"Once the modules are installed, the user credentials **must** be configured," +" in order to connect with Carvajal Web Service. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Settings` and scroll to the" +" :guilabel:`Colombian Electronic Invoicing` section. Then, fill in the " +"required configuration information provided by Carvajal:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:94 +msgid "" +":guilabel:`Username` and :guilabel:`Password`: Username and password " +"(provided by Carvajal) to the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:96 +msgid "" +":guilabel:`Company Registry`: Company's NIT number *without* the " +"verification code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:97 +msgid ":guilabel:`Account ID`: Company's NIT number followed by `_01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:98 +msgid "" +":guilabel:`Colombia Template Code`: Select one of the two available " +"templates (`CGEN03` or `CGNE04`) to be used in the PDF format of the " +"electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:101 +msgid "" +"Enable the :guilabel:`Test mode` checkbox to connect with the Carvajal " +"testing environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:103 +msgid "" +"Once Odoo and Carvajal are fully configured and ready for production, " +"deactivate the :guilabel:`Test mode` checkbox to use the production " +"database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Configure credentials for Carvajal web service in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:111 +msgid "" +":guilabel:`Test mode` must **only** be used on duplicated databases, **not**" +" the production environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:115 +msgid "Report data configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:117 +msgid "" +"Report data can be defined for the fiscal section and bank information of " +"the PDF as part of the configurable information sent in the XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:120 +msgid "" +"Navigate to :menuselection:`Accounting --> Configuration --> Settings`, and " +"scroll to the :guilabel:`Colombian Electronic Invoicing` section, in order " +"to find the :guilabel:`Report Configuration` fields. Here the header " +"information for each report type can be configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:124 +msgid ":guilabel:`Gran Contribuyente`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:125 +msgid ":guilabel:`Tipo de Régimen`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:126 +msgid ":guilabel:`Retenedores de IVA`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:127 +msgid ":guilabel:`Autorretenedores`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:128 +msgid ":guilabel:`Resolución Aplicable`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:129 +msgid ":guilabel:`Actividad Económica`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:130 +msgid ":guilabel:`Bank Information`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:135 +msgid "Master data configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:140 +msgid "" +"Partner contacts can be created in the *Contacts* app. To do so, navigate to" +" :menuselection:`Contacts`, and click the :guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:143 +msgid "" +"Then, name the contact, and using the radio buttons, select the contact " +"type, either :guilabel:`Individual` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:146 +msgid "" +"Complete the full :guilabel:`Address`, including the :guilabel:`City`, " +":guilabel:`State`, and :guilabel:`ZIP` code. Then, complete the " +"identification and fiscal information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:150 +msgid "Identification information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:152 +msgid "" +"Identification types, defined by the |DIAN|, are available on the partner " +"form, as part of the Colombian localization. Colombian partners **must** " +"have their :guilabel:`Identification Number` (VAT) and :guilabel:`Document " +"Type` set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:157 +msgid "" +"When the :guilabel:`Document Type` is `NIT`, the :guilabel:`Identification " +"Number` needs to be configured in Odoo, including the *verification digit at" +" the end of the ID, prefixed by a hyphen (`-`)*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:164 +msgid "" +"The partner's responsibility codes (section 53 in the :abbr:`RUT (Registro " +"único tributario)` document) are included as part of the electronic " +"invoicing module, as it is required by the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:167 +msgid "" +"The required fields can be found under :menuselection:`Partner --> Sales & " +"Purchase Tab --> Fiscal Information section`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:170 +msgid "" +":guilabel:`Obligaciones y Responsabilidades`: Select the fiscal " +"responsibility for the company (`O-13` Gran Contribuyente, `O-15` " +"Autorretenedor, `O-23` Agente de retención IVA, `O-47` Regimen de " +"tributación simple, or `R-99-PN` No Aplica)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:175 +msgid "" +":guilabel:`Fiscal Regimen`: Select the tribute name for the company (`IVA`, " +"`INC`, `IVA e INC`, or `No Aplica`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:183 +msgid "" +"To manage products, navigate to :menuselection:`Accounting --> Customers -->" +" Products`, then click on a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:186 +msgid "" +"When adding general information on the product form, it is required that " +"either the :guilabel:`UNSPSC Category` (:guilabel:`Accounting` tab), or " +":guilabel:`Internal Reference` (:guilabel:`General Information` tab) field " +"is configured. Be sure to :guilabel:`Save` the product once configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:194 +msgid "" +"To create or modify taxes, go to :menuselection:`Accounting --> " +"Configuration --> Taxes`, and select the related tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:197 +msgid "" +"If sales transactions include products with taxes, the :guilabel:`Value " +"Type` field in the :guilabel:`Advanced Options` tab needs to be configured " +"per tax. Retention tax types (:guilabel:`ICA`, :guilabel:`IVA`, " +":guilabel:`Fuente`) are also included. This configuration is used to display" +" taxes correctly in the invoice PDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "The ICA, IVA and Fuente fields in the Advanced Options tab in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:209 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:85 +msgid "Sales journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:211 +msgid "" +"Once the |DIAN| has assigned the official sequence and prefix for the " +"electronic invoice resolution, the sales journals related to the invoice " +"documents **must** be updated in Odoo. To do so, navigate to " +":menuselection:`Accounting --> Configuration --> Journals`, and select an " +"existing sales journal, or create a new one with the :guilabel:`Create` " +"button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:216 +msgid "" +"On the sales journal form, input the :guilabel:`Journal Name`, " +":guilabel:`Type`, and set a unique :guilabel:`Short Code` in the " +":guilabel:`Journals Entries` tab. Then, configure the following data in the " +":guilabel:`Advanced Settings` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:220 +msgid "" +":guilabel:`Electronic invoicing`: Enable :guilabel:`UBL 2.1 (Colombia)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:221 +msgid "" +":guilabel:`Invoicing Resolution`: Resolution number issued by |DIAN| to the " +"company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:222 +msgid ":guilabel:`Resolution Date`: Initial effective date of the resolution." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:223 +msgid "" +":guilabel:`Resolution end date`: End date of the resolution's validity." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:224 +msgid "" +":guilabel:`Range of Numbering (minimum)`: First authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:225 +msgid "" +":guilabel:`Range of Numbering (maximum)`: Last authorized invoice number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:228 +msgid "" +"The sequence and resolution of the journal **must** match the one configured" +" in Carvajal and the |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:232 +msgid "Invoice sequence" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:234 +msgid "" +"The invoice sequence and prefix **must** be correctly configured when the " +"first document is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:237 +msgid "" +"Odoo automatically assigns a prefix and sequence to the following invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:240 +msgid "Purchase journals" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:242 +msgid "" +"Once the |DIAN| has assigned the official sequence and prefix for the " +"*support document* related to vendor bills, the purchase journals related to" +" their supporting documents need to be updated in Odoo. The process is " +"similar to the configuration of the :ref:`sales journals <co-journals>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:249 +msgid "" +"The :doc:`chart of accounts " +"</applications/finance/accounting/get_started/chart_of_accounts>` is " +"installed by default as part of the localization module, the accounts are " +"mapped automatically in taxes, default account payable, and default account " +"receivable. The chart of accounts for Colombia is based on the PUC (Plan " +"Unico de Cuentas)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:257 +msgid "Main workflows" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:262 +msgid "" +"The following is a breakdown of the main workflow for electronic invoices " +"with the Colombian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:265 +msgid "Sender creates an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:266 +msgid "Electronic invoice provider generates the legal XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:267 +msgid "" +"Electronic invoice provider creates the CUFE (Invoice Electronic Code) with " +"the electronic signature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:269 +msgid "Electronic invoice provider sends a notification to |DIAN|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:270 +msgid "|DIAN| validates the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:271 +msgid "|DIAN| accepts or rejects the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:272 +msgid "Electronic invoice provider generates the PDF invoice with a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:273 +msgid "Electronic invoice provider sends invoice to the acquirer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:274 +msgid "" +"Acquirer sends a receipt of acknowledgement, and accepts or rejects the " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:275 +msgid "Sender downloads a :file:`.zip` file with the PDF and XML." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Electronic invoice workflow for Colombian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:287 +msgid "" +"The functional workflow taking place before an invoice validation does " +"**not** alter the main changes introduced with the electronic invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:290 +msgid "" +"Electronic invoices are generated and sent to both the |DIAN| and customer " +"through Carvajal's web service integration. These documents can be created " +"from your sales order or manually generated. To create a new invoice, go to " +":menuselection:`Accounting --> Customers --> Invoices`, and select " +":guilabel:`Create`. On the invoice form configure the following fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:295 +msgid ":guilabel:`Customer`: Customer's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:296 +msgid ":guilabel:`Journal`: Journal used for electronic invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:297 +msgid "" +":guilabel:`Electronic Invoice Type`: Select the type of document. By " +"default, :guilabel:`Factura de Venta` is selected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:299 +msgid "" +":guilabel:`Invoice Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:301 +msgid "When done, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:306 +#: ../../content/applications/finance/fiscal_localizations/india.rst:116 +#: ../../content/applications/finance/fiscal_localizations/india.rst:257 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:389 +msgid "Invoice validation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:308 +msgid "" +"After the invoice confirmation, an XML file is created and sent " +"automatically to Carvajal. The invoice is then processed asynchronously by " +"the E-invoicing service UBL 2.1 (Colombia). The file is also displayed in " +"the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Carvajal XML invoice file in Odoo chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:316 +msgid "" +"The :guilabel:`Electronic Invoice Name` field is now displayed in the " +":guilabel:`EDI Documents` tab, with the name of the XML file. Additionally, " +"the :guilabel:`Electronic Invoice Status` field is displayed with the " +"initial value :guilabel:`To Send`. To process the invoice manually, click on" +" the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:324 +msgid "Reception of legal XML and PDF" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:326 +msgid "" +"The electronic invoice vendor (Carvajal) receives the XML file, and proceeds" +" to validate its structure and information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:329 +msgid "" +"After validating the electronic invoice, proceed to generate a legal XML " +"which includes a digital signature and a unique code (CUFE), a PDF invoice " +"that includes a QR code and the CUFE is also generated. If everything is " +"correct the :guilabel:`Electronic Invoicing` field value changes to " +":guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:334 +msgid "" +"A :file:`.zip` containing the legal electronic invoice (in XML format) and " +"the invoice in (PDF format) is downloaded and displayed in the invoice " +"chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "ZIP file displayed in the invoice chatter in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:341 +msgid "The electronic invoice status changes to :guilabel:`Accepted`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:346 +msgid "" +"The process for credit notes is the same as for invoices. To create a credit" +" note with reference to an invoice, go to :menuselection:`Accounting --> " +"Customers --> Invoices`. On the invoice, click :guilabel:`Add Credit Note`, " +"and complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:350 +msgid ":guilabel:`Credit Method`: Select the type of credit method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:352 +msgid "" +":guilabel:`Partial Refund`: Use this option when it is a partial amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:353 +msgid "" +":guilabel:`Full Refund`: Use this option if the credit note is for the full " +"amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:354 +msgid "" +":guilabel:`Full refund and new draft invoice`: Use this option if the credit" +" note is auto-validated and reconciled with the invoice. The original " +"invoice is duplicated as a new draft." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:358 +msgid ":guilabel:`Reason`: Enter the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:359 +msgid "" +":guilabel:`Reversal Date`: Select if you want a specific date for the credit" +" note or if it is the journal entry date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:361 +msgid "" +":guilabel:`Use Specific Journal`: Select the journal for your credit note or" +" leave it empty if you want to use the same journal as the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:363 +msgid "" +":guilabel:`Refund Date`: If you chose a specific date, select the date for " +"the refund." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:365 +msgid "Once reviewed, click the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:370 +msgid "" +"The process for debit notes is similar to credit notes. To create a debit " +"note with reference to an invoice, go to :menuselection:`Accounting --> " +"Customers --> Invoices`. On the invoice, click the :guilabel:`Add Debit " +"Note` button, and enter the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:374 +msgid ":guilabel:`Reason`: Type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:375 +msgid ":guilabel:`Debit note date`: Select the specific options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:376 +msgid "" +":guilabel:`Copy lines`: Select this option if you need to register a debit " +"note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:378 +msgid "" +":guilabel:`Use Specific Journal`: Select the printer point for your debit " +"note, or leave it empty if you want to use the same journal as the original " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:381 +msgid "When done, click :guilabel:`Create Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:384 +msgid "Support document for vendor bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:386 +msgid "" +"With master data, credentials, and the purchase journal configured for " +"support documents related to vendor bills, you can start using *support " +"documents*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:389 +msgid "" +"Support documents for vendor bills can be created from your purchase order " +"or manually. Go to :menuselection:`Accounting --> Vendors --> Bills` and " +"fill in the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:392 +msgid ":guilabel:`Vendor`: Enter the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:393 +msgid ":guilabel:`Bill Date`: Select the date of the bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:394 +msgid "" +":guilabel:`Journal`: Select the journal for support documents related to the" +" vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:395 +msgid "" +":guilabel:`Invoiced Lines`: Specify the products with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:397 +msgid "" +"Once reviewed, click the :guilabel:`Confirm` button. Upon confirmation, an " +"XML file is created and automatically sent to Carvajal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:405 +msgid "" +"During the XML validation, the most common errors are related to missing " +"master data (*Contact Tax ID*, *Address*, *Products*, *Taxes*). In such " +"cases, error messages are shown in the chatter after updating the electronic" +" invoice status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:409 +msgid "" +"After the master data is corrected, it's possible to reprocess the XML with " +"the new data and send the updated version, using the :guilabel:`Retry` " +"button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "XML validation errors shown in the invoice chatter in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:421 +msgid "Certificado de Retención en ICA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:423 +msgid "" +"This report is a certification to vendors for withholdings made for the " +"Colombian Industry and Commerce (ICA) tax. The report can be found under " +":menuselection:`Accounting --> Reporting --> Colombian Statements --> " +"Certificado de Retención en ICA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en ICA report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:432 +msgid "Certificado de Retención en IVA" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:434 +msgid "" +"This report issues a certificate on the amount withheld from vendors for VAT" +" withholding. The report can be found under :menuselection:`Accounting --> " +"Reporting --> Colombian Statements --> Certificado de Retención en IVA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en IVA report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:443 +msgid "Certificado de Retención en la Fuente" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:445 +msgid "" +"This certificate is issued to partners for the withholding tax that they " +"have made. The report can be found under :menuselection:`Accounting --> " +"Reporting --> Colombian Statements --> Certificado de Retención en Fuente`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/colombia.rst-1 +msgid "Certificado de Retención en Fuente report in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:3 +msgid "Ecuador" +msgstr "ประเทศเอกวาดอร์" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:8 +msgid "" +"With the Ecuadorian localization you can generate electronic documents with " +"its XML, Fiscal folio, with electronic signature and direct connection to " +"tax authority SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:11 +msgid "" +"The supported documents are Invoices, Credit Notes, Debit Notes, Purchase " +"Liquidations and Withholds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:14 +msgid "" +"The localization also Includes automations to easily predict the withholding" +" tax to be applied to each purchase invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:18 +msgid "" +"`App Tour - Localización de Ecuador " +"<https://www.youtube.com/watch?v=BQOXVSDeeK8>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:19 +msgid "" +"`Smart Tutorial - Localización de Ecuador " +"<https://www.odoo.com/slides/smart-tutorial-localizacion-de-ecuador-170>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:22 +#: ../../content/applications/finance/spreadsheet.rst:26 +msgid "Glossary" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:24 +msgid "Here are some terms that are essential on the Ecuadorian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:26 +msgid "" +"**SRI**: meaning *Servicio de Rentas Internas*, the government organization " +"that enforces pay of taxes in Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:28 +msgid "" +"**EDI**: stands for *Electronic Data Interchange*, which refers to the " +"sending of Electronics Documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:30 +msgid "" +"**RIMPE**: stands for *Regimen Simplificado para Emprendedores y Negocios*, " +"the type of taxpayer qualified for SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:39 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Ecuadorian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:49 +msgid ":guilabel:`Ecuadorian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:50 +msgid "`l10n_ec`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:51 +msgid "" +"The default :doc:`fiscal localization package <../fiscal_localizations>`, " +"adds accounting characteristics for the Ecuadorian localization, which " +"represent the minimum configuration required for a company to operate in " +"Ecuador according to the guidelines set by the :abbr:`SRI (servicio de " +"rentas internas)`. The module's installation automatically loads: Chart of " +"Accounts, taxes, documents types, tax support types. Additionally, the " +"generation of forms 103 and 104 are automatic." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:57 +msgid ":guilabel:`Ecuadorian Accounting EDI`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:58 +msgid "`l10n_ec_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:59 +msgid "" +"Includes all the technical and functional requirements to generate and " +"validate :doc:`Electronics Documents " +"<../accounting/customer_invoices/electronic_invoicing>`, based on the " +"Technical documentation published by the SRI. The authorized documents are: " +"Invoices, Credit Notes, Debit Notes, Withholdings and Purchase liquidations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:66 +msgid "" +"When you install a database from scratch selecting `Ecuador` as the country," +" Odoo automatically installs the base module :guilabel:`Ecuadorian - " +"Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:72 +msgid "" +"To configure your company information, go to the :guilabel:`Contacts` app " +"and search the name given to your company or activate :ref:`developer mode " +"<developer-mode>` and go to :menuselection:`Company --> Contact` and then " +"edit the contact to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:76 +msgid "Check the :guilabel:`Company` option on top" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:79 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:85 +msgid "Upload company logo and save" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Populate company data for Ecuador in Odoo Contacts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:94 +msgid "" +"To upload your information for electronic documents go to " +":menuselection:`Accounting --> Configuration --> Settings` and search for " +":command:`Ecuadorian Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 +msgid "Configure the next information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 +msgid ":guilabel:`Company legal name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 +msgid "" +":guilabel:`Use production servers`: check the checkbox if your company is " +"going to do electronic documents in the production environment. If you want " +"to use the testing environment for electronic documents then keep the " +"checkbox unchecked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:103 +msgid "" +":guilabel:`Regime`: select if your company is in General Regular or is " +"qualified as RIMPE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:104 +msgid "" +":guilabel:`Forced to keep accounting books`: check the checkbox if your " +"company has this condition." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:106 +msgid ":guilabel:`Default taxes for withholdings`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:107 +msgid "" +":guilabel:`Issue withholds`: check the checkbox if your company is going to " +"do electronic withholds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 +msgid "" +":guilabel:`Withhold consumibles`: put the code of the withholding for when " +"you buy goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:110 +msgid "" +":guilabel:`Withhold services`: put the code of the withholding for when you " +"buy services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 +msgid "" +":guilabel:`Withhold credit card`: put the code of the withholding for when " +"you buy with credit card" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:113 +msgid "" +":guilabel:`Withhold agent number`: put the company withholding agent " +"resolution number, if applicable for your company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:115 +msgid "" +":guilabel:`Electronic Certificate File`: upload electronic certificate and " +"password, then save it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 +msgid "" +":guilabel:`Special tax contributor number`: if your company is qualified as " +"a special taxpayer, fill out this field with it's corresponding tax " +"contributor number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Electronic signature for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:124 +msgid "" +"When configuring the withholdings in the configuration menu, these suggested" +" withholdings are only for domestic suppliers when no withholdings are setup" +" on their *Taxpayer Type*. Moreover, the Credit Card withholding set up is " +"always used when a Credit or Debit Card SRI Payment Metho is used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 +msgid "VAT withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 +msgid "" +"This configuration only applies if you are qualified as a *Withholding " +"Agent* by the SRI, otherwise skip this step. To configure your VAT " +"withholding, go to :menuselection:`Accounting --> Accounting --> " +"Configuration --> Ecuadorian SRI: Taxpayer Type SRI`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:136 +msgid "" +"You must configure the withholding percentage that applies for each type of " +"taxpayer, specify the :guilabel:`Goods VAT Withholding` and the " +":guilabel:`Services VAT Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxpayer Type configuration for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:144 +msgid "" +"In the case that the :guilabel:`Taxpayer Type` is `RIMPE`, also configure " +"the :guilabel:`Profit Withholding` percentage." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:148 +msgid "Printer points" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:150 +msgid "" +"To configure your printer points, go to :menuselection:`Accounting --> " +"Configuration --> Accounting: Journals`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:153 +msgid "" +"Printer points need to be configured for each type of electronic document " +"that you need. For example: Customer Invoice, Credit Notes, and Debit Notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:156 +msgid "" +"For each printer point, you need to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:158 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Sales Documents`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:160 +msgid ":guilabel:`Type`: refers to the type of journal, select `Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:161 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:195 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:222 +msgid "" +":guilabel:`Use Documents?`: this checkbox is automatically checked, leave it" +" checked." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:162 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:196 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:223 +msgid ":guilabel:`Emission Entity`: configure the establishment number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:163 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:197 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:224 +msgid ":guilabel:`Emission Point`: configure the printer point." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:164 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:198 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:225 +msgid "" +":guilabel:`Emission address`: configure the address of the establishment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:165 +msgid "" +":guilabel:`Default income account`: configure the default income account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:166 +msgid "" +":guilabel:`Dedicated Credit Note Sequence`: check the checkbox if *Credit " +"Notes* are to be generated from this printer point - journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:168 +msgid "" +":guilabel:`Short Code`: This is the unique code for the sequence of " +"accounting entries, enter a unique 5-digit code, for example: `VT001`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:171 +msgid "" +"Customer Invoice, Credit Notes and Debit Notes need to use the same journal " +"as the :guilabel:`Emission Point`, and the :guilabel:`Entity Point` should " +"be unique per journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring a printer point for Ecuador electronic document type of Customer" +" Invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 +msgid "" +"In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic " +"Invoicing` checkbox to enable it for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:186 +msgid "Withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:188 +msgid "" +"A Withholding Journal must be defined, go to go to " +":menuselection:`Accounting --> Configuration --> Accounting: Journals` " +"where you need to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:191 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:193 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:220 +msgid "" +":guilabel:`Type`: refers to the type of journal, select `Miscellaneous`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:194 +msgid ":guilabel:`Withhold Type`: Configure Purchase Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:199 +msgid ":guilabel:`Default account`: configure the default income account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:200 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:226 +msgid "" +":guilabel:`Short Code`: This is the unique code for the sequence of " +"accounting entries, enter a unique 5-digit code, for example: `RT001`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring withholding for Ecuador electronic document type of Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:208 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:234 +msgid "" +"In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic " +"Invoicing` checkbox to enable the sending of electronic invoicing for the " +"withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 +msgid "Purchase Liquidations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:214 +msgid "" +"When using Purchase Liquidations, a specific journal must be created, go to " +":menuselection:`Accounting --> Configuration --> Accounting: Journals` and " +"configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:218 +msgid "" +":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point]" +" [Document Type]`, for example: `001-001 Withhold`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:221 +msgid "" +":guilabel:`Purchase Liquidations`: check the checkbox to enable purchase " +"liquidations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "" +"Configuring purchase liquidations for Ecuador electronic document type of " +"Withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"is installed by default as part of the set of data included in the " +"localization module, the accounts are mapped automatically in Taxes, Default" +" Account Payable, Default Account Receivable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:247 +msgid "" +"The chart of accounts for Ecuador is based on the most updated version of " +"Superintendency of Companies, which is grouped in several categories and is " +"compatible with NIIF accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 +msgid "" +"In addition to the basic information in your products, you must add the " +"configuration of the withholding code (tax) that applies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 +msgid "" +"Go to :menuselection:`Accounting --> Vendors: Products` under the tab " +"\"Purchase\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Product for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 +msgid "Configure the next information when you create a contact:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:269 +msgid "" +"Check the :guilabel:`Company` option on top if it is a contact with RUC, or " +"check :guilabel:`Individual` if it is a contact with cedula or passport." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 +msgid "" +":guilabel:`Address`: :guilabel:`Street` is a required field to confirm the " +"Electronic Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:273 +msgid "" +":guilabel:`Identification Number`: select an identification type `RUC`, " +"`Cedula`, or `Passport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:274 +msgid ":guilabel:`Taxpayer Type`: select the contact's SRI Taxpayer Type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Contacts for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:283 +msgid "" +"The :guilabel:`SRI Taxpayer Type` has inside the configuration of which VAT " +"and Profit withholding will apply when you use this contact on Vendor Bill, " +"and then create a withholding from there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 +msgid "Review your taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 +msgid "" +"As part of the localization module, taxes are automatically created with its" +" configuration and related financial accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxes for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:297 +msgid "The following options have been automatically configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:299 +msgid "" +":guilabel:`Tax Support`: to be configured only in the IVA tax, this option " +"is useful when you register purchase withholdings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:301 +msgid "" +":guilabel:`Code ATS`: to be configured only for income tax withholding " +"codes, it is important when you register the withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:303 +msgid "" +":guilabel:`Tax Grids`: configure the codes of 104 form if it is a IVA tax " +"and configure the codes of 103 form if it is a income tax withholding code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:305 +msgid ":guilabel:`Tax Name`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 +msgid "" +"For IVA tax, format the name as: `IVA [percent] (104, [form code] [tax " +"support code] [tax support short name])`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:309 +msgid "" +"For income tax withholding code, format the name as: `Code ATS [Percent of " +"withhold] [withhold name]`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:312 +msgid "" +"Once the Ecuador module is installed, the most common taxes are " +"automatically configured. If you need to create an additional one, you can " +"do so, for which you must base yourself on the configuration of the existing" +" taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Taxes with tax support for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:321 +msgid "Review your Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:323 +msgid "" +"Some accounting transactions like *Customer Invoices* and *Vendor Bills* are" +" classified by document types. These are defined by the government fiscal " +"authorities, in this case by the SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the document type includes the " +"country on which the document is applicable; also the data is created " +"automatically when the localization module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:330 +msgid "" +"The information required for the document types is included by default so " +"the user does not need to fill anything there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Document types for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 +msgid "" +"Once you have configured your database, you can register your documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:343 +msgid "Sales documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:348 +msgid "" +":guilabel:`Customer invoices` are electronic documents that, when validated," +" are sent to SRI. These documents can be created from your sales order or " +"manually. They must contain the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:351 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:395 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:428 +msgid ":guilabel:`Customer`: type the customer's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:352 +msgid "" +":guilabel:`Journal`: select the option that matches the printer point for " +"the customer invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:353 +msgid "" +":guilabel:`Document Type`: type document type in this format `(01) Invoice`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:354 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:474 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:512 +msgid "" +":guilabel:`Payment Method (SRI)`: select how the invoice is going to be " +"paid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:475 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:513 +msgid ":guilabel:`Products`: specify the product with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer invoice for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:362 +msgid "Customer credit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:364 +msgid "" +"The :doc:`Customer credit note " +"<../accounting/customer_invoices/credit_notes>` is an electronic document " +"that, when validated, is sent to SRI. It is necessary to have a validated " +"(posted) invoice in order to register a credit note. On the invoice there is" +" a button named :guilabel:`Credit note`, click on this button to be directed" +" to the :guilabel:`Create credit note` form, then complete the following " +"information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 +msgid ":guilabel:`Credit Method`: select the type of credit method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 +msgid "" +":guilabel:`Partial Refund`: use this option when you need to type the first " +"number of documents and if it is a partial credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:374 +msgid "" +":guilabel:`Full Refund`: use this option if the credit note is for the total" +" invoice and you need the credit note to be auto-validated and reconciled " +"with the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:376 +msgid "" +":guilabel:`Full refund and new draft invoice`: use this option if the credit" +" note is for the total invoice and you need the credit note to be auto-" +"validated and reconciled with the invoice, and auto-create a new draft " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:380 +msgid ":guilabel:`Reason`: type the reason for the credit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 +msgid ":guilabel:`Rollback Date`: select the :guilabel:`specific` options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:382 +msgid ":guilabel:`Reversal Date`: type the date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:383 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:416 +msgid "" +":guilabel:`Use Specific Journal`: select the printer point for your credit " +"note, or leave it empty if you want to use the same journal as the original " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:386 +msgid "Once reviewed, you can click on the :guilabel:`Reverse` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Add Customer Credit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:392 +msgid "" +"When the :guilabel:`Partial Refund` option is used, you can change the " +"amount of the credit note and then validate it. Before validating the credit" +" note, review the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:396 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:429 +msgid "" +":guilabel:`Journal`: select the printer point for the customer Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:397 +msgid "" +":guilabel:`Document Type`: this is the document type `(04) Credit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:398 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 +msgid "" +":guilabel:`Products`: It must specify the product with the correct taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer Credit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:405 +msgid "Customer debit note" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:407 +msgid "" +"The :guilabel:`Customer debit note` is an electronic document that, when " +"validated, is sent to SRI. It is necessary to have a validated (posted) " +"invoice in order to register a debit note. On the invoice there is a button " +"named :guilabel:`Debit Note`, click on this button to be directed to the " +":guilabel:`Create debit note` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:412 +msgid ":guilabel:`Reason`: type the reason for the debit note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:413 +msgid ":guilabel:`Debit note date`: select the :guilabel:`specific` options." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 +msgid "" +":guilabel:`Copy lines`: select this option if you need to register a debit " +"note with the same lines of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:419 +msgid "" +"Once reviewed you can click on the :guilabel:`Create Debit Note` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Add Customer Debit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:425 +msgid "" +"You can change the debit note amount, and then validate it. Before " +"validating the debit note, review the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:430 +msgid "" +":guilabel:`Document Type`: this is the document type `(05) Debit Note`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer Debit Note for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:438 +msgid "Customer withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:440 +msgid "" +"The :guilabel:`Customer withholding` is a non-electronic document for your " +"company, this document is issued by the client in order to apply a " +"withholding to the sale." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:443 +msgid "" +"It is necessary to have a validated (posted) invoice in order to register a " +"customer withholding. On the invoice there is a button named :guilabel:`Add " +"Withhold`, click on this button to be directed to the :guilabel:`Customer " +"withholding` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 +msgid ":guilabel:`Document Number`: type the withholding number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:448 +msgid "" +":guilabel:`Withhold Lines`: select the taxes that the customer is " +"withholding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:450 +msgid "" +"Before validating the withholding, review that the amounts for each tax are " +"the same as the original document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Customer withhold for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:458 +msgid "Purchase Documents" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:461 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:130 +msgid "Vendor bill" +msgstr "บิลผู้ขาย" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:463 +msgid "" +"The :guilabel:`Vendor bill` is a non-electronic document for your company, " +"this document is issued by your vendor when your company generates a " +"purchase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:466 +msgid "" +"The bills can be created from the purchase order or manually, it must " +"contain the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:469 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:506 +msgid ":guilabel:`Vendor`: type the vendor's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:470 +msgid ":guilabel:`Bill Date`: select the date of invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:471 +msgid ":guilabel:`Journal`: it is the journal for vendor bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:472 +msgid ":guilabel:`Document Type`: this is the document type `(01) Invoice`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:473 +msgid ":guilabel:`Document number`: type the document number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchases for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:482 +msgid "" +"When creating the purchase withholding, verify that the bases (base amounts)" +" are correct. If you need to edit the amount of the tax in the " +":guilabel:`Vendor bill`, click the :guilabel:`Edit` button. Otherwise, from " +"the :guilabel:`Journal Items` tab click the :guilabel:`Edit` button and set " +"the adjustment to go where you want." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 +msgid "Purchase liquidation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 +msgid "" +"The :guilabel:`Purchase liquidation` is an electronic document that, when " +"validated, is sent to SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 +msgid "" +"Companies issue this type of electronic document when they purchase, and the" +" vendor does not issue an invoice due to one or more of the following cases:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:495 +msgid "Services were provided by non-residents of Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:496 +msgid "" +"Services provided by foreign companies without residency or establishment in" +" Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:497 +msgid "" +"Purchase of goods or services from natural persons not registered with a " +"RUC, who due to their cultural level or hardiness are not able to issue " +"sales receipts or customer invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:499 +msgid "" +"Reimbursement for the purchase of goods or services to employees in a " +"dependency relationship (full-time employee)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:501 +msgid "" +"Services provided by members of collegiate bodies for the exercise of their " +"function." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:503 +msgid "" +"These types of electronic documents can be created from the " +":guilabel:`Purchase Order` or manually from the :guilabel:`Vendor Bills` " +"form view. It must contain the following data:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 +msgid "" +":guilabel:`Journal`: select the journal for the :guilabel:`Purchase " +"Liquidation` with the correct printer point." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 +msgid "" +":guilabel:`Document Type`: this is the document type `(03) Purchase " +"Liquidation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:510 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:530 +msgid "" +":guilabel:`Document number`: type the document number (sequence), you will " +"only have to do this once, then the sequence will be automatically assigned " +"for the next documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:515 +msgid "" +"Once you review the information you can validate the :guilabel:`Purchase " +"Liquidation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchase liquidation for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:522 +msgid "Purchase withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:524 +msgid "" +"The :guilabel:`Purchase withholding` is an electronic document that, when " +"validated, is sent to SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 +msgid "" +"It is necessary to have an invoice in a validated state in order to register" +" a :guilabel:`Purchase withholding`. On the invoice, there is a button named" +" :guilabel:`Add Withhold`, click on this button to be directed to the " +":guilabel:`Withholding` form, then complete the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 +msgid "" +":guilabel:`Withhold lines`: The taxes appear automatically according to the " +"configuration of products and vendors, you should review if the taxes and " +"tax support are correct, and, if it is not correct, you can edit and select " +"the correct taxes and tax support." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:536 +msgid "" +"Once you review the information you can validate the " +":guilabel:`Withholding`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Purchase withhold for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 +msgid "" +"You can't change the tax support for one that was not included in the " +"configuration of the taxes used on the :guilabel:`Vendor Bill`. To do so, go" +" to the tax applied on the :guilabel:`Vendor Bill` and change the " +":guilabel:`Tax Support` there." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:547 +msgid "" +"A withholding tax can be divided into two or more lines, this will depend on" +" whether two or more withholdings percentages apply." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:551 +msgid "" +"The system suggests a VAT withholding of 30% with tax support 01, you can " +"add your VAT withholding of 70% in a new line with the same tax support, the" +" system will allow you as long as the total of the bases matches the total " +"from the :guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:556 +msgid "Financial Reports" +msgstr "รายงานทางการเงิน" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:558 +msgid "" +"In Ecuador, there are fiscal reports that the company presents to SRI. In " +"Odoo, we have two of the main financial reports used by companies. These are" +" the reports 103 and 104." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:561 +msgid "" +"To get these reports go to the :guilabel:`Accounting` app and select " +":menuselection:`Reporting --> Statements Reports --> Tax Report` and then " +"filter by `Tax Report 103` or `Tax Report 104`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:565 +msgid "Report 103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:567 +msgid "" +"This report contains information of income tax withholdings in a given " +"period, this can be reported monthly or semi-annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:570 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 +msgid "" +"You can see the information needed to report, which includes base and tax " +"amounts, which also includes the tax code within the parenthesis in order to" +" report it to the SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Report 103 form for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:578 +msgid "Report 104" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 +msgid "" +"This report contains information on VAT tax and VAT withholding for a given " +"period, this can be monthly or semi-annually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst-1 +msgid "Report 104 form for Ecuador." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "ประเทศอียิปต์" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:8 +#: ../../content/applications/finance/fiscal_localizations/india.rst:8 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:8 +msgid "Installation" +msgstr "การติดตั้ง" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:10 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Egyptian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:19 +msgid ":guilabel:`Egypt - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:20 +msgid "``l10n_eg``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:21 +#: ../../content/applications/finance/fiscal_localizations/india.rst:21 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:19 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:20 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:19 +msgid "" +"Default :ref:`fiscal localization package <fiscal_localizations/packages>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:22 +msgid ":guilabel:`Egyptian E-invoice Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:23 +msgid "``l10n_eg_edi_eta``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:24 +msgid "" +":ref:`Egyptian Tax Authority (ETA) e-invoicing integration " +"<egypt/e-invoicing>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:29 +msgid "Egyptian e-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:31 +msgid "" +"Odoo is compliant with the **Egyptian Tax Authority (ETA) e-invoicing** " +"requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:34 +msgid "" +"Egyptian e-invoicing is available from Odoo 15.0. If needed, :doc:`upgrade " +"</administration/upgrade>` your database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:38 +msgid "" +"`Video: Egypt E-invoicing <https://www.youtube.com/watch?v=NXuBPLR4pVw>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:39 +msgid ":doc:`/administration/upgrade`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:44 +msgid "Register Odoo on your ETA portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:46 +msgid "" +"You must register your Odoo ERP system on your ETA portal to get your API " +"credentials. You need these codes to :ref:`configure your Odoo Accounting " +"app <egypt/e-invoicing-configuration>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:49 +msgid "" +"Access your company profile on the ETA portal by clicking on :guilabel:`View" +" Taxpayer Profile`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Clicking on \"View Taxpayer Profile\" on an ETA invoicing portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:55 +msgid "" +"Next, go to the :guilabel:`Representatives` section and then click on " +":guilabel:`Register ERP`. Fill out the :guilabel:`ERP Name` (e.g., ``Odoo``)" +" and leave the other fields empty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Filling out of the form to register an ERP system on the ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:62 +msgid "" +"Once successfully registered, the website displays your API credentials:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:64 +msgid "Client ID" +msgstr "ไอดีลูกค้า" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:65 +msgid "Client Secret 1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:66 +msgid "Client Secret 2" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:69 +msgid "" +"ETA should give you a username and a password to access their online portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:70 +msgid "Ask ETA to provide you with preproduction portal access as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:71 +msgid "These codes are confidential and should be stored safely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:76 +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:37 +#: ../../content/applications/finance/payment_providers/asiapay.rst:34 +#: ../../content/applications/finance/payment_providers/buckaroo.rst:27 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:29 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:30 +#: ../../content/applications/finance/payment_providers/razorpay.rst:37 +msgid "Configuration on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:78 +msgid "" +"To connect your Odoo database to your ETA portal account, go to " +":menuselection:`Accounting --> Configuration --> Settings --> ETA " +"E-Invoicing Settings`, and set the :guilabel:`ETA Client ID` and " +":guilabel:`ETA Secret` that you retrieved when you :ref:`registered Odoo on " +"your ETA portal <egypt/e-invoicing-eta-portal>`. Set an invoicing threshold " +"if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Configuration of the ETA E-Invoicing credentials in Odoo Accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:88 +msgid "" +"**Test on your preproduction portal** before starting to issue real invoices" +" on the production ETA portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:90 +msgid "" +"**Credentials** for preproduction and production environments are different." +" Make sure to update them on Odoo when you move from one environment to " +"another." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:92 +msgid "" +"If not done yet, fill out your company details with your company's full " +"address, country, and Tax ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:98 +msgid "ETA codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:100 +msgid "" +"E-invoicing works with a set of codes provided by the ETA. You can use the " +"`ETA documentation <https://sdk.preprod.invoicing.eta.gov.eg/codes/>`_ to " +"code your business attributes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:103 +msgid "" +"Most of these codes are handled automatically by Odoo, provided that your " +":ref:`branches <egypt/e-invoicing-branches>`, :ref:`customers " +"<egypt/e-invoicing-customers>`, and :ref:`products <egypt/e-invoicing-" +"products>` are correctly configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:107 +msgid "Company Information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:109 +msgid "Company Tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Branch ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "If you have only one branch, use ``0`` as the branch code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:112 +msgid "Activity type Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:114 +msgid "Other Information:" +msgstr "ข้อมูลอื่น:" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Product Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Your company's products should be coded and matched with their **GS1** or " +"**EGS** codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "Tax Codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:0 +msgid "" +"Most of the taxes codes are already configured on Odoo in the :guilabel:`ETA" +" Code (Egypt)` field. We advise you to make sure these codes match your " +"company's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:123 +msgid "" +"`Egyptian eInvoicing & eReceipt SDK - Code Tables " +"<https://sdk.preprod.invoicing.eta.gov.eg/codes/>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:130 +msgid "Branches" +msgstr "สาขา" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:132 +msgid "" +"Create a contact and a journal for each branch of your company and configure" +" its ETA settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:134 +msgid "" +"To do so, go to :menuselection:`Accounting --> Configuration --> Journals`, " +"then click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:137 +msgid "" +"Name the journal according to your company's branch and set the " +":guilabel:`Type` as :guilabel:`Sales`. Next, open the " +":menuselection:`Advanced Settings` tab and fill out the :guilabel:`Egyptian " +"ETA settings` section:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:141 +msgid "" +"In the :guilabel:`Branch` field, select the branch's contact or create it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:142 +msgid "Set the :guilabel:`ETA Activity Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:143 +msgid "" +"Set the :guilabel:`ETA Branch ID` (use ``0`` if you have one branch only)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Sales journal configuration of an Egyptian company's branch" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:150 +msgid "" +"The contact selected in the :guilabel:`Branch` field must be set as a " +":guilabel:`Company` (**not** as an :guilabel:`Individual`), and the " +":guilabel:`Address` and :guilabel:`Tax ID` fields must be filled out." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:157 +msgid "Customers" +msgstr "ลูกค้า" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:159 +msgid "" +"Make sure your customers' contact forms are correctly filled out so your " +"e-invoices are valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:161 +msgid "contact type: :guilabel:`Individual`: or :guilabel:`Company`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:162 +msgid ":guilabel:`Country`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:163 +msgid "" +":guilabel:`Tax ID`: Tax ID or Company registry for companies. National ID " +"for individuals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:166 +msgid "" +"You can edit your customers' contact forms by going to " +":menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:174 +msgid "" +"Make sure your products are correctly configured so your e-invoices are " +"valid:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:176 +msgid ":guilabel:`Product Type`: storable products, consumables, or services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:177 +msgid "" +":guilabel:`Unit of Measure`: if you also use Odoo Inventory and have enabled" +" :doc:`Units of Measure " +"<../../inventory_and_mrp/inventory/product_management/product_replenishment/uom>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:179 +msgid ":guilabel:`Barcode`: **GS1** or **EGS** barcode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:180 +msgid "" +":guilabel:`ETA Item code` (under the :menuselection:`Accounting` tab): if " +"the barcode doesn't match your ETA item code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:184 +msgid "" +"You can edit your products by going to :menuselection:`Accounting --> " +"Customers --> Products`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:189 +msgid "USB authentication" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:191 +msgid "" +"Each person who needs to electronically sign invoices needs a specific USB " +"key to authenticate and send invoices to the ETA portal through an ERP." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:195 +msgid "" +"You can contact the :abbr:`ETA (Egyptian Tax Authority)` or `Egypt Trust " +"<https://www.egypttrust.com/>`_ to get these USB keys." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:201 +msgid "Install Odoo as a local proxy on your computer" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:203 +msgid "" +"An Odoo local server works as a bridge between your computer and your Odoo " +"database hosted online." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:205 +msgid "" +"Download the Odoo Community installer from the page " +"https://www.odoo.com/page/download and start the installation on your " +"computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:208 +msgid "Select :guilabel:`Local Proxy Mode` as the type of install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "" +"Selection of \"Local Proxy Mode\" during the installation of Odoo Community." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:215 +msgid "" +"This installation of Odoo only works as a server and does not install any " +"Odoo apps on your computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:218 +msgid "" +"Once the installation is complete, the installer displays your **access " +"token** for the Odoo Local Proxy. Copy the token and save it in a safe place" +" for later use." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:222 +msgid "`Odoo: Download Odoo <https://www.odoo.com/page/download>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:223 +msgid ":doc:`../../../administration/install`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:228 +msgid "Configure the USB key" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:230 +msgid "" +"Once the local proxy server is installed on your computer, you can link it " +"with your Odoo database." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:232 +msgid "" +"Go to :menuselection:`Accounting --> Configurations --> Thumb Drive` and " +"click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:234 +msgid "" +"Input a :guilabel:`Company` name, the :guilabel:`ETA USB Pin` given to you " +"by your USB key provider, and the :guilabel:`Access Token` provided at the " +"end of the :ref:`local proxy installation <egypt/e-invoicing-local-proxy>`, " +"then click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:237 +msgid "Click on :guilabel:`Get certificate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/egypt.rst-1 +msgid "Creating a new thumb drive for the e-invoicing of an egyptian company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:3 +msgid "France" +msgstr "ประเทศฝรั่งเศส" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:8 +msgid "FEC - Fichier des Écritures Comptables" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:10 +msgid "" +"An FEC :dfn:`Fichier des Écritures Comptables` audit file contains all the " +"accounting data and entries recorded in all the accounting journals for a " +"financial year. The entries in the file must be arranged in chronological " +"order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:14 +msgid "" +"Since January 1st, 2014, every French company is required to produce and " +"transmit this file upon request by the tax authorities for audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:18 +msgid "FEC Import" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:20 +msgid "" +"To make the onboarding of new users easier, Odoo Enterprise's French " +":ref:`fiscal localization package <fiscal_localizations/packages>` includes " +"the **FEC Import** feature (module name: ``l10n_fr_fec_import``), which " +"enables the import of existing FEC files from older software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:24 +msgid "" +"To enable this feature, go to :menuselection:`Accounting --> Configuration " +"--> Settings --> Accounting Import`, enable **FEC Import**, and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:27 +msgid "" +"Next, go to :menuselection:`Accounting --> Configuration --> FEC Import`, " +"upload your FEC file, and click on *Import*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Importing FEC files from different year takes no particular action or " +"computation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"Should multiple files contain any \"Reports à Nouveaux\" (RAN) with the " +"starting balance of the year, you might need to cancel those entries in the " +"User Interface. Odoo makes those entries (RAN) useless." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:38 +msgid "File formats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:40 +msgid "" +"FEC files can only be in CSV format, as the XML format is not supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:44 +msgid "" +"The FEC CSV file has a plain text format representing a data table, with the" +" first line being a header and defining the list of fields for each entry, " +"and each following line representing one accounting entry, in no " +"predetermined order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:48 +msgid "" +"Our module expects the files to meet the following technical specifications:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:50 +msgid "**Encoding**: UTF-8, UTF-8-SIG and iso8859_15." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:51 +msgid "**Separator**: any of these: `;` or `|` or `,` or `TAB`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:52 +msgid "" +"**Line terminators**: both CR+LF (`\\\\r\\\\n`) and LF (`\\\\n`) character " +"groups are supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:53 +msgid "**Date format**: `%Y%m%d`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:56 +msgid "Fields description and use" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "#" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Field name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +msgid "Format" +msgstr "รูปแบบ" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "01" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "JournalCode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "Journal Code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +msgid "`journal.code` and `journal.name` if `JournalLib` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Alphanumeric" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "02" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "JournalLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "Journal Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +msgid "`journal.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "03" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "EcritureNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "Numbering specific to each journal sequence number of the entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +msgid "`move.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "04" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "EcritureDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +msgid "Accounting entry Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "`move.date`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Date (yyyyMMdd)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "05" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "CompteNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "Account Number" +msgstr "หมายเลขบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +msgid "`account.code`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "06" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "CompteLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "Account Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +msgid "`account.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "07" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "CompAuxNum" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "Secondary account Number (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +msgid "`partner.ref`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "08" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "CompAuxLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "Secondary account Label (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +msgid "`partner.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "09" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "PieceRef" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "Document Reference" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +msgid "`move.ref` and `move.name` if `EcritureNum` is not provided" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "PieceDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +msgid "Document Date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "11" +msgstr "11" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "EcritureLib" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "Account entry Label" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +msgid "`move_line.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "Debit amount" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +msgid "`move_line.debit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Float" +msgstr "ลอย" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "13" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "Credit amount (Field name \"Crédit\" is not allowed)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +msgid "`move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "14" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "EcritureLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "Accounting entry cross reference (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +msgid "`move_line.fec_matching_number`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "DateLet" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +msgid "Accounting entry date (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "unused" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "16" +msgstr "16" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "ValidDate" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +msgid "Accounting entry validation date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "17" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Montantdevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "Currency amount (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +msgid "`move_line.amount_currency`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "18" +msgstr "18" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Idevise" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "Currency identifier (accepts null)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +msgid "`currency.name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:108 +msgid "" +"These two fields can be found in place of the others in the sence above." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Montant" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "Amount" +msgstr "จำนวน" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +msgid "`move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Sens" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Can be \"C\" for Credit or \"D\" for Debit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "determines `move_line.debit` or `move_line.credit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +msgid "Char" +msgstr "Char" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 +msgid "Implementation details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:121 +msgid "" +"The following accounting entities are imported from the FEC files: " +"**Accounts, Journals, Partners**, and **Moves**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:124 +msgid "" +"Our module determines the encoding, the line-terminator character, and the " +"separator that are used in the file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:127 +msgid "" +"A check is then performed to see if every line has the correct number of " +"fields corresponding to the header." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:130 +msgid "" +"If the check passes, then the file is read in full, kept in memory, and " +"scanned. Accounting entities are imported one type at a time, in the " +"following order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:134 +msgid "Accounts" +msgstr "บัญชี" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:136 +msgid "" +"Every accounting entry is related to an account, which should be determined " +"by the field `CompteNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:140 +msgid "Code matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:142 +msgid "" +"Should a similar account code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:145 +msgid "" +"Accounts in Odoo generally have a number of digits that are default for the " +"fiscal localization. As the FEC module is related to the French " +"localization, the default number of relevant digits is 6." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:148 +msgid "" +"This means that the account codes the trailing zeroes are right-trimmed, and" +" that the comparison between the account codes in the FEC file and the ones " +"already existing in Odoo is performed only on the first six digits of the " +"codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:153 +msgid "" +"The account code `65800000` in the file is matched against an existing " +"`658000` account in Odoo, and that account is used instead of creating a new" +" one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:157 +msgid "Reconcilable flag" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:159 +msgid "" +"An account is technically flagged as *reconcilable* if the first line in " +"which it appears has the `EcritureLet` field filled out, as this flag means " +"that the accounting entry is going to be reconciled with another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:165 +msgid "" +"In case the line somehow has this field not filled out, but the entry still " +"has to be reconciled with a payment that hasn't yet been recorded, this " +"isn't a problem anyway; the account is flagged as reconcilable as soon as " +"the import of the move lines requires it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:170 +msgid "Account type and Templates matching" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:172 +msgid "" +"As the **type** of the account is not specified in the FEC format, **new** " +"accounts are created with the default type *Current Assets* and then, at the" +" end of the import process, they are matched against the installed Chart of " +"Account templates. Also, the *reconcile* flag is also computed this way." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:177 +msgid "" +"The match is done with the left-most digits, starting by using all digits, " +"then 3, then 2." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:54 +msgid "Code" +msgstr "โค้ด" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "Full comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "3-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +msgid "2-digits comparison" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/payment_providers/authorize.rst:83 +msgid "Template" +msgstr "เทมเพลต" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +msgid "`400`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`40100000`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +msgid "`401`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "**Result**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +msgid "Match **found**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 +msgid "" +"The type of the account is then flagged as *payable* and *reconcilable* as " +"per the account template." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:196 +msgid "" +"Journals are also checked against those already existing in Odoo to avoid " +"duplicates, also in the case of multiple FEC files imports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:199 +msgid "" +"Should a similar journal code already be present in the system, the existing" +" one is used instead of creating a new one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:202 +msgid "New journals have their name prefixed by the string ``FEC-``." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:205 +msgid "`ACHATS` -> `FEC-ACHATS`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:207 +msgid "" +"The journals are *not* archived, the user is entitled to handle them as he " +"wishes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:210 +msgid "Journal type determination" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:212 +msgid "" +"The journal type is also not specified in the format (as per the accounts) " +"and therefore it is at first created with the default type `general`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:215 +msgid "" +"At the end of the import process, the type is determined as per these rules " +"regarding related moves and accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`bank`: Moves in these journals always have a line (debit or credit) " +"impacting a liquidity account." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`cash` / `bank` can be interchanged, so `bank` is set everywhere when this " +"condition is met." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`sale`: Moves in these journals mostly have debit lines on receivable " +"accounts and credit lines on tax income accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Sale refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "" +"`purchase`: Moves in these journals mostly have credit lines on payable " +"accounts and debit lines on expense accounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "Purchase refund journal items are debit/credit inverted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:0 +msgid "`general`: for everything else." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:231 +msgid "A minimum of three moves is necessary for journal type identification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:232 +msgid "" +"A threshold of 70% of moves must correspond to a criteria for a journal type" +" to be determined." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:235 +msgid "Suppose we are analyzing the moves that share a certain `journal_id`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +#: ../../content/applications/finance/fiscal_localizations/france.rst:269 +msgid "Moves" +msgstr "การเคลื่อนย้าย" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Count" +msgstr "จำนวน" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +msgid "Percentage" +msgstr "เปอร์เซ็นต์" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +msgid "that have a sale account line and no purchase account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "that have a purchase account line and no sale account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +msgid "25%" +msgstr "25%" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "that have a liquidity account line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "3" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +msgid "**75%**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "**Total**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "4" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +msgid "100%" +msgstr "100%" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 +msgid "" +"The journal `type` would be `bank`, because the bank moves percentage (75%) " +"exceeds the threshold (70%)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:253 +msgid "Partners" +msgstr "พาร์ทเนอร์" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:255 +msgid "Each partner keeps its `Reference` from the field `CompAuxNum`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:259 +msgid "" +"These fields are searchable, in line with former FEC imports on the " +"accounting expert's side for fiscal/audit purposes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:264 +msgid "" +"Users can merge partners with the Data Cleaning App, where Vendors and " +"Customers or similar partner entries may be merged by the user, with " +"assistance from the system that groups them by similar entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:271 +msgid "" +"Entries are immediately posted and reconciled after submission, using the " +"`EcritureLet` field to do the matching between the entries themselves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:274 +msgid "" +"The `EcritureNum` field represents the name of the moves. We noticed that " +"sometimes it may not be filled out. In this case, the field `PieceRef` is " +"used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:278 +msgid "Rounding issues" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:280 +msgid "" +"There is a rounding tolerance with a currency-related precision on debit and" +" credit (i.e., 0.01 for EUR). Under this tolerance, a new line is added to " +"the move, named *Import rounding difference*, targeting the accounts:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:284 +msgid "`658000` Charges diverses de gestion courante, for added debits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:285 +msgid "`758000` Produits divers de gestion courante, for added credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:288 +msgid "Missing move name" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:290 +msgid "" +"Should the `EcritureNum` not be filled out, it may also happen that the " +"`PieceRef` field is also not suited to determine the move name (it may be " +"used as an accounting move line reference) leaving no way to actually find " +"which lines are to be grouped in a single move, and effectively impeding the" +" creation of balanced moves." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:295 +msgid "" +"One last attempt is made, grouping all lines from the same journal and date " +"(`JournalLib`, `EcritureDate`). Should this grouping generate balanced moves" +" (sum(credit) - sum(debit) = 0), then each different combination of journal " +"and date creates a new move." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:300 +msgid "" +"`ACH` + `2021/05/01` --> new move on journal `ACH` with name `20210501`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:302 +msgid "" +"Should this attempt fail, the user is prompted an error message with all the" +" move lines that are supposedly unbalanced." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:308 +msgid "" +"If a line has the partner information specified, the information is copied " +"to the accounting move itself if the targeted Journal is of type *payable* " +"or *receivable*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:312 +msgid "Export" +msgstr "ส่งออก" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:314 +msgid "" +"If you have installed the French :ref:`fiscal localization package " +"<fiscal_localizations/packages>`, you should be able to download the FEC. To" +" do so, go to :menuselection:`Accounting --> Reporting --> France --> FEC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:320 +msgid "" +"If you do not see the submenu **FEC**, go to :menuselection:`Apps`, remove " +"the *Apps* filter, then search for the module named **France-FEC** and make " +"sure it is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:325 +msgid "" +"`Official Technical Specification (fr) " +"<https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000027804775>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:327 +msgid "" +"`Test-Compta-Demat (Official FEC Testing tool) " +"<https://github.com/DGFiP/Test-Compta-Demat>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:331 +msgid "French Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:333 +msgid "" +"If you have installed the French Accounting, you will have access to some " +"accounting reports specific to France:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:336 +msgid "Bilan comptable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:337 +msgid "Compte de résultats" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:338 +msgid "Plan de Taxes France" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:341 +msgid "Get the VAT anti-fraud certification with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:343 +msgid "" +"As of January 1st 2018, a new anti-fraud legislation comes into effect in " +"France and DOM-TOM. This new legislation stipulates certain criteria " +"concerning the inalterability, security, storage and archiving of sales " +"data. These legal requirements are implemented in Odoo, version 9 onward, " +"through a module and a certificate of conformity to download." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:350 +msgid "Is my company required to use anti-fraud software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:352 +msgid "" +"Your company is required to use an anti-fraud cash register software like " +"Odoo (CGI art. 286, I. 3° bis) if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:355 +msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:356 +msgid "Some of your customers are private individuals (B2C)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:358 +msgid "" +"This rule applies to any company size. Auto-entrepreneurs are exempted from " +"VAT and therefore are not affected." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:362 +msgid "Get certified with Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:364 +msgid "Getting compliant with Odoo is very easy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:366 +msgid "" +"Your company is requested by the tax administration to deliver a certificate" +" of conformity testifying that your software complies with the anti-fraud " +"legislation. This certificate is granted by Odoo SA to Odoo Enterprise users" +" `here <https://www.odoo.com/my/contract/french-certification/>`_. If you " +"use Odoo Community, you should :doc:`upgrade to Odoo Enterprise " +"</administration/maintain/enterprise>` or contact your Odoo service " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:373 +msgid "In case of non-conformity, your company risks a fine of €7,500." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:375 +msgid "To get the certification, just follow the following steps:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:377 +msgid "" +"If you use **Odoo Point of Sale**, :ref:`install <general/install>` the " +"**France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 " +"bis)** module by going to :menuselection:`Apps`, removing the *Apps* filter," +" then searching for *l10n_fr_pos_cert*, and installing the module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:381 +msgid "" +"Make sure a country is set on your company, otherwise your entries won’t be " +"encrypted for the inalterability check. To edit your company’s data, go to " +":menuselection:`Settings --> Users & Companies --> Companies`. Select a " +"country from the list; Do not create a new country." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:385 +msgid "" +"Download the mandatory certificate of conformity delivered by Odoo SA `here " +"<https://www.odoo.com/my/contract/french-certification/>`__." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:389 +msgid "" +"To install the module in any system created before December 18th 2017, you " +"should update the modules list. To do so, activate the :ref:`developer mode " +"<developer-mode>`. Then go to the *Apps* menu and press *Update Modules " +"List* in the top-menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:393 +msgid "" +"In case you run Odoo on-premise, you need to update your installation and " +"restart your server beforehand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:395 +msgid "" +"If you have installed the initial version of the anti-fraud module (prior to" +" December 18th 2017), you need to update it. The module's name was *France -" +" Accounting - Certified CGI 286 I-3 bis*. After an update of the modules " +"list, search for the updated module in *Apps*, select it and click " +"*Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is" +" installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:404 +msgid "Anti-fraud features" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:406 +msgid "The anti-fraud module introduces the following features:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:408 +msgid "" +"**Inalterability**: deactivation of all the ways to cancel or modify key " +"data of POS orders, invoices and journal entries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:410 +msgid "**Security**: chaining algorithm to verify the inalterability;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:411 +msgid "" +"**Storage**: automatic sales closings with computation of both period and " +"cumulative totals (daily, monthly, annually)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:415 +msgid "Inalterability" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:417 +msgid "" +"All the possible ways to cancel and modify key data of paid POS orders, " +"confirmed invoices and journal entries are deactivated, if the company is " +"located in France or in any DOM-TOM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:423 +msgid "" +"If you run a multi-companies environment, only the documents of such " +"companies are impacted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:426 +msgid "Security" +msgstr "ความปลอดภัย" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:428 +msgid "" +"To ensure inalterability, every order or journal entry is encrypted upon " +"validation. This number (or hash) is calculated from the key data of the " +"document as well as from the hash of the precedent documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:433 +msgid "" +"The module introduces an interface to test the data inalterability. If any " +"information is modified on a document after its validation, the test will " +"fail. The algorithm recomputes all the hashes and compares them against the " +"initial ones. In case of failure, the system points out the first corrupted " +"document recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:439 +msgid "" +"Users with *Manager* access rights can launch the inalterability check. For " +"POS orders, go to :menuselection:`Point of Sales --> Reporting --> French " +"Statements`. For invoices or journal entries, go to " +":menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:446 +msgid "Storage" +msgstr "อุปกรณ์จัดเก็บ" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:448 +msgid "" +"The system also processes automatic sales closings on a daily, monthly and " +"annual basis. Such closings distinctly compute the sales total of the period" +" as well as the cumulative grand totals from the very first sales entry " +"recorded in the system." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:454 +msgid "" +"Closings can be found in the *French Statements* menu of Point of Sale, " +"Invoicing and Accounting apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:459 +msgid "" +"Closings compute the totals for journal entries of sales journals (Journal " +"Type = Sales)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:461 +msgid "" +"For multi-companies environments, such closings are performed by company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:463 +msgid "" +"POS orders are posted as journal entries at the closing of the POS session. " +"Closing a POS session can be done anytime. To prompt users to do it on a " +"daily basis, the module prevents from resuming a session opened more than 24" +" hours ago. Such a session must be closed before selling again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:469 +msgid "" +"A period’s total is computed from all the journal entries posted after the " +"previous closing of the same type, regardless of their posting date. If you " +"record a new sales transaction for a period already closed, it will be " +"counted in the very next closing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:476 +msgid "" +"For test & audit purposes such closings can be manually generated in the " +":ref:`developer mode <developer-mode>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:478 +msgid "" +"Then go to :menuselection:`Settings --> Technical --> Automation --> " +"Scheduled Actions`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:481 +msgid "Responsibilities" +msgstr "ความรับผิดชอบ" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:483 +msgid "" +"Do not uninstall the module! If you do so, the hashes will be reset and none" +" of your past data will be longer guaranteed as being inalterable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:486 +msgid "" +"Users remain responsible for their Odoo instance and must use it with due " +"diligence. It is not permitted to modify the source code which guarantees " +"the inalterability of data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:490 +msgid "" +"Odoo absolves itself of all and any responsibility in case of changes in the" +" module’s functions caused by 3rd party applications not certified by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:494 +msgid "More Information" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:496 +msgid "" +"You can find more information about this legislation in the following " +"official documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:500 +msgid "" +"`Frequently Asked Questions " +"<https://www.economie.gouv.fr/files/files/directions_services/dgfip/controle_fiscal/actualites_reponses/logiciels_de_caisse.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:502 +msgid "" +"`Official Statement " +"<http://bofip.impots.gouv.fr/bofip/10691-PGP.html?identifiant=BOI-TVA-" +"DECLA-30-10-30-20160803>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:504 +msgid "" +"`Item 88 of Finance Law 2016 " +"<https://www.legifrance.gouv.fr/affichTexteArticle.do?idArticle=JORFARTI000031732968&categorieLien=id&cidTexte=JORFTEXT000031732865>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:3 +msgid "Germany" +msgstr "ประเทศเยอรมันนี" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:6 +msgid "German Chart of Accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:8 +msgid "" +"The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can " +"choose the one you want by going in :menuselection:`Accounting --> " +"Configuration` then choose the package you want in the Fiscal Localization " +"section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:12 +msgid "" +"Be careful, you can only change the accounting package as long as you have " +"not created any accounting entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:16 +msgid "" +"When you create a new Odoo Online database, the SKR03 is installed by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:19 +msgid "German Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:21 +msgid "" +"Here is the list of German-specific reports available on Odoo Enterprise:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:25 +msgid "Tax Report (Umsatzsteuervoranmeldung)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:26 +msgid "Partner VAT Intra" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:29 +msgid "Export from Odoo to Datev" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:31 +msgid "" +"It is possible to export your accounting entries from Odoo to Datev. To be " +"able to use this feature, the german accounting localization needs to be " +"installed on your Odoo Enterprise database. Then you can go in " +":menuselection:`Accounting --> Reporting --> General Ledger` then click on " +"the **Export Datev (csv)** button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:39 +msgid "Point of Sale in Germany: Technical Security System" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:41 +msgid "" +"The **Kassensicherungsverordnung** (The Act on Protection against " +"Manipulation of Digital Records) requires that electronic record-keeping " +"systems - including the :doc:`point of sale " +"</applications/sales/point_of_sale>` systems - must be equipped with a " +"**Technical Security System** (also called **TSS** or **TSE**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:46 +msgid "" +"Odoo offers a service that is compliant with the help of `fiskaly " +"<https://fiskaly.com>`_, a *cloud-based solution*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:50 +msgid "" +"Since this solution is cloud-based, a working internet connection is " +"required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:53 +msgid "" +"The only VAT rates allowed are given by fiskaly. You can check these rates " +"by consulting: `fiskaly DSFinV-K API: VAT Definition " +"<https://developer.fiskaly.com/api/dsfinvk/v0/#tag/VAT-Definition>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:63 +msgid "" +"If your database was created before June 2021, :ref:`upgrade " +"<general/upgrade>` your **Point of Sale** app (`point_of_sale`) and the " +"**Restaurant** module (`pos_restaurant`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:65 +msgid "" +":ref:`Install <general/install>` the **Germany - Certification for Point of " +"Sale** (`l10n_de_pos_cert`) and **Germany - Certification for Point of Sale " +"of type restaurant** (`l10n_de_pos_res_cert`) modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:70 +msgid "" +"If these modules are not listed, :ref:`update the app list " +"<general/install>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Upgrading Odoo Point of Sale from the Apps dashboard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:77 +msgid "Register your company at the financial authority" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:79 +msgid "" +"To register your company, go to :menuselection:`Settings --> General " +"Settings --> Companies --> Update Info`, fill out the following fields and " +"*Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:82 +msgid "**Company name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:83 +msgid "Valid **address**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:84 +msgid "**VAT** number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:85 +msgid "" +"**St.-Nr** (Steuernummer): this number is assigned by the tax office to " +"every taxable natural or legal person. (e.g., `2893081508152`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:87 +msgid "" +"**W-IdNr** (Wirtschafts-Identifikationsnummer): this number is used as a " +"permanent identification number for economically active persons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:90 +msgid "" +"You can then **register your company through fiskaly** by opening the " +"*fiskaly* tab and clicking on the *fiskaly Registration* button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Button to register a company through fiskaly in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:98 +msgid "" +"If you do not see the *fiskaly Registration* button, make sure that you " +"*saved* your company details and are not in *editing mode* anymore." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:101 +msgid "Once the registration has been finalized, new fields appear:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:103 +msgid "" +"**fiskaly organization ID** refers to the ID of your company at the fiskaly " +"side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:104 +msgid "" +"**fiskaly API key** and **secret** are the credentials the system uses to " +"access the services offered by fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "fiskaly keys as displayed on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:112 +msgid "" +"It is possible to request new credentials if there is any issue with the " +"current ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:115 +msgid "Create and link a Technical Security System to your PoS" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Create TSS option from a point of sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:121 +msgid "" +"To use your point of sale in Germany, you first have to create a :abbr:`TSS " +"(Technical Security System)` for it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:124 +msgid "" +"To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of" +" Sale`, open the point of sale you want to edit, then check the box next to " +"**Create TSS** and *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Example of TSS ID and Client ID from fiskaly in Odoo Point of Sale" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:131 +msgid "" +"Once the creation of the TSS is successful, you can find your **TSS ID** and" +" **Client ID** under the *fiskaly API* section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:134 +msgid "**TSS ID** refers to the ID of your TSS at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:135 +msgid "**Client ID** refers to your PoS but at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:138 +msgid "DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Menu to export DSFinV-K" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:144 +msgid "" +"Whenever you close a PoS session, the orders' details are sent to the " +":abbr:`DSFinV-K (Digitale Schnittstelle der Finanzverwaltung für " +"Kassensysteme)` service of fiskaly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:147 +msgid "" +"In case of an audit, you can export the data sent to DSFinV-K by going to " +":menuselection:`Point of Sale --> Orders --> DSFinV-k exports`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:150 +msgid "These fields are mandatory:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:152 +msgid "**Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:153 +msgid "" +"**Start Datetime** (export data with dates larger than or equal to the given" +" start date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:154 +msgid "" +"**End Datetime** (export data with dates smaller than or equal to the given " +"end date)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:156 +msgid "" +"Leave the **Point of Sale** field blank if you want to export the data of " +"all your points of sale. Specify a Point of Sale if you want to export this " +"specific PoS' data only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:159 +msgid "" +"The creation of a DSFinV-K export triggers on export at fiskaly's side." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst-1 +msgid "Pending DSFinV-K export on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:165 +msgid "" +"As you can see, the **State** is *Pending*. This means that the export has " +"been successfully triggered and is being processed. You have to click on " +"*Refresh State* to check if it is ready." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:171 +msgid "German Tax Accounting Standards: Odoo's guide to GoBD Compliance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:173 +msgid "" +"**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung" +" von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum" +" Datenzugriff " +"<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_." +" In short, it is a **guideline for the proper management and storage of " +"books, records, and documents in electronic form, as well as for data " +"access**, that is relevant for the German tax authority, tax declaration, " +"and balance sheet." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:180 +msgid "" +"These principles have been written and published by the Federal Ministry of " +"Finance (BMF) in November 2014. Since January 2015, **they have become the " +"norm** and replace previously accepted practices linked to computer-based " +"accounting. Several changes have been made by the BMF in 2019 and January " +"2020 to specify some of the content and due to the development of digital " +"solutions (cloud hosting, paperless companies, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:187 +msgid "Odoo gives you **the means to be compliant with GoBD**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:190 +msgid "" +"What do you need to know about GoBD when relying on accounting software?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:193 +msgid "" +"If you can, the best way to understand GoBD is to Read the `Official GoBD " +"text " +"<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_." +" It is a bit long but quite readable for non-experts. But in short, here is " +"what to expect:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:197 +msgid "" +"The **GoBD is binding for companies that have to present accounts, which " +"includes SMEs, freelancers, and entrepreneurs, to the financial " +"authorities**. As such, **the taxpayer himself is the sole responsible** for" +" the complete and exhaustive keeping of fiscal-relevant data (above-" +"mentioned financial and related data)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:202 +msgid "" +"Apart from software requirements, the user is required to ensure Internal " +"control systems (*in accordance with sec. 146 of the Fiscal Code*):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:205 +msgid "Access rights control;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:206 +msgid "Segregation of Duties, Functional separating;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:207 +msgid "Entry controls (error notifications, plausibility checks);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:208 +msgid "Reconciliation checks at data entry;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:209 +msgid "Processing controls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:210 +msgid "" +"Measures to prevent intentional or unintentional manipulation of software, " +"data, or documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:212 +msgid "" +"The user must distribute tasks within its organization to the relevant " +"positions (*control*) and verify that the tasks are properly and completely " +"performed (*supervision*). The result of these controls must be recorded " +"(*documentation*), and should errors be found during these controls, " +"appropriate measures to correct the situation should be put into place " +"(*prevention*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:218 +msgid "What about data security?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:220 +msgid "" +"**The taxpayer must secure the system against any data loss due to " +"deletion, removal, or theft of any data**. If the entries are not " +"sufficiently secured, the bookkeeping will be regarded as not in accordance " +"with the GoBD guidelines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:224 +msgid "" +"Once bookings have been finally posted, they can no longer be changed or " +"deleted via the application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:227 +msgid "" +"If Odoo is used in the cloud, regular backups are part of the Odoo Online " +"service. In addition, regular backups can be downloaded and backed up on " +"external systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:231 +msgid "" +"`Odoo Cloud Hosting - Service Level Agreement <https://www.odooo.com/cloud-" +"sla>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:233 +msgid "" +"If the server is operated locally, it is the responsibility of the user to " +"create the necessary backup infrastructure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:237 +msgid "" +"In some cases, data has to be kept for ten years or more, so always have " +"backups saved. It is even more important if you decide to change software " +"provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:241 +msgid "Responsibility of the software editor" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:243 +msgid "" +"Considering GoBD only applies between the taxpayer and the financial " +"authority, **the software editor can by no means be held responsible for the" +" accurate and compliant documentation of financial transactional data of " +"their users**. It can merely provide the necessary tools for the user to " +"respect the software related guidelines described in the GoBD." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:249 +msgid "How can Odoo help you achieve Compliance?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:251 +msgid "" +"The key words, when it comes to GoBD, are: **traceable, verifiable, true, " +"clear, and continuous**. In short, you need to have audit-proof archiving in" +" place and Odoo provides you with the means to achieve all of these " +"objectives:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Traceability and verifiability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Each record in Odoo is stamped with the creator of the document, the " +"creation date, the modification date, and who modified it. In addition, " +"relevant fields are tracked thus it can be seen which value was changed by " +"whom in the chatter of the relevant object." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Completeness**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"All financial data must be recorded in the system, and there can be no gaps." +" Odoo ensures that there is no gap in the numbering of the financial " +"transactions. It is the responsibility of the user to encode all financial " +"data in the system. As most financial data in Odoo is generated " +"automatically, it remains the responsibility of the user to encode all " +"vendor bills and miscellaneous operations completely." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Accuracy**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Odoo ensures with the correct configuration that the correct accounts are " +"used. In addition, the control mechanisms between purchase orders and sales " +"orders and their respective invoices reflect the business reality. It is the" +" responsibility of the user to scan and attach the paper-based vendor bill" +" to the respective record in Odoo. *Odoo Document helps you automate this " +"task*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Timely booking and record-keeping**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"As most financial data in Odoo is generated by the transactional objects " +"(for example, the invoice is booked at confirmation), Odoo ensures out-of-" +"the-box timely record-keeping. It is the responsibility of the user to " +"encode all incoming vendor bills in a timely manner, as well as the " +"miscellaneous operations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Order**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"Financial data stored in Odoo is per definition ordered and can be reordered" +" according to most fields present in the model. A specific ordering is not " +"enforced by the GoBD, but the system must ensure that a given financial " +"transaction can be quickly found by a third-party expert. Odoo ensures this " +"out-of-the-box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "**Inalterability**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:0 +msgid "" +"With the German Odoo localization, Odoo is in standard configured in such a " +"way that the inalterability clause can be adhered to without any further " +"customization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:286 +msgid "Do you need a GoBD-Export?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:288 +msgid "" +"In the case of fiscal control, the fiscal authority can request three levels" +" of access to the accounting system (Z1, Z2, Z3). These levels vary from " +"direct access to the interface to the handover of the financial data on a " +"storage device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:292 +msgid "" +"In case of a handover of the financial data on a storage device, the format " +"is **not** enforced by the GoBD. It can be, for example, in XLS, CSV, XML, " +"Lotus 123, SAP-format, AS/400-format, or else. Odoo supports the CSV and " +"XLS-export of financial data out-of-the-box. The GoBD **recommends** the " +"export in a specific XML-based GoBD-format (see \"Ergänzende Informationen " +"zur Datenntträgerüberlassung\" §3) but it is not binding." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:299 +msgid "What is the role and meaning of the compliance certification?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:301 +msgid "" +"The GoBD clearly states that due to the nature of a state of the art " +"accounting software, their configuration possibilities, changing nature, and" +" various forms of use, **no legally binding certification can be given**, " +"nor can the software be made liable towards a public authority. Third-party " +"certificates can indeed have **an informative value** for customers to make " +"software buying decisions but are by no means legally binding or of any " +"other legal value (A. 12, § 181)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:307 +msgid "" +"A GoBD certificate states nothing more than that if you use the software " +"according to its guidelines, the software will not refrain you from " +"respecting the GoBD. These certifications are very expensive in terms of " +"time and cost, and their value is very relative. Thus we focus our efforts " +"on ensuring GoBD compliance rather than pay for a marketing tool which does " +"not, however, offer our customer any legal certainty." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:314 +msgid "" +"The BMF actually states the following in the `Official GoBD text " +"<https://www.bundesfinanzministerium.de/Content/DE/Downloads/BMF_Schreiben/Weitere_Steuerthemen/Abgabenordnung/2019-11-28-GoBD.pdf>`_:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:317 +msgid "" +"180. Positive attestations on the correctness of the bookkeeping - and thus " +"on the correctness of IT-based bookkeeping systems - are not issued either " +"in the context of a tax field audit or in the context of binding " +"information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:320 +msgid "" +"181. \"Certificates\" or \"attestations\" from third parties can serve as a " +"decision criterion for the company when selecting a software product, but " +"develop from the in margin no. 179 is not binding on the tax authorities." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:325 +msgid "" +"The previous content was `automatically translated from German with Google " +"Translate " +"<https://translate.google.com/?sl=de&tl=en&text=180.%0APositivtestate%20zur%20Ordnungsm%C3%A4%C3%9Figkeit%20der%20Buchf%C3%BChrung%20-%20und%20damit%20zur%20Ordnungsm%C3%A4%C3%9Figkeit%20DV-" +"gest%C3%BCtzter%20Buchf%C3%BChrungssysteme%20-%20werden%20weder%20im%20Rahmen%20einer%20steuerlichen%20Au%C3%9Fenpr%C3%BCfung%20noch%20im%20Rahmen%20einer%20verbindlichen%20Auskunft%20erteilt.%0A%0A181.%0A%E2%80%9EZertifikate%E2%80%9C%20oder%20%E2%80%9ETestate%E2%80%9C%20Dritter%20k%C3%B6nnen%20bei%20der%20Auswahl%20eines%20Softwareproduktes%20dem%20Unternehmen%20als%20Entscheidungskriterium%20dienen%2C%20entfalten%20jedoch%20aus%20den%20in%20Rz.%20179%20genannten%20Gr%C3%BCnden%20gegen%C3%BCber%20der%20Finanzbeh%C3%B6rde%20keine%20Bindungswirkung.%20&op=translate>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:330 +msgid "What happens if you are not compliant?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/germany.rst:332 +msgid "" +"In the event of an infringement, you can expect a fine but also a court " +"order demanding the implementation of specific measures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "เขตปกครองพิเศษฮ่องกง" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:6 +msgid "Add FPS QR codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:8 +msgid "" +":abbr:`FPS (Faster Payment System)` is a payment service platform that " +"allows customers to make instant domestic payments to individuals and " +"merchants in Hong Kong dollars or Renminbi via online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:13 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:12 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:125 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:12 +msgid "Activate QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:15 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:14 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:127 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:14 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the " +":guilabel:`Customer Payments` section, activate the :guilabel:`QR Codes` " +"feature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:19 +msgid "FPS bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:21 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate FPS. Set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:26 +msgid "" +"The account holder's country must be set to Hong Kong on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:27 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:26 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:27 +msgid "" +"You could also include the invoice number in the QR code by checking the " +":guilabel:`Include Reference` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:34 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:33 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:144 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:34 +msgid ":doc:`../accounting/bank`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:37 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:36 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:147 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:37 +msgid "Bank journal configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:39 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:38 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:39 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Journals`, open the " +"bank journal, then fill out the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +msgid "Bank Account's journal configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:46 +msgid "Issue invoices with FPS QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:48 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:47 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:48 +msgid "" +"When creating a new invoice, open the :guilabel:`Other Info` tab and set the" +" :guilabel:`Payment QR-code` option to *EMV Merchant-Presented QR-code*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +msgid "Select EMV Merchant-Presented QR-code option" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:54 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the FPS QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:3 +msgid "India" +msgstr "ประเทศอินเดีย" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:10 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Indian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:19 +msgid ":guilabel:`Indian - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:20 +msgid "`l10n_in`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:22 +msgid ":guilabel:`Indian E-invoicing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:23 +msgid "`l10n_in_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:24 +msgid ":ref:`Indian e-invoicing integration <india/e-invoicing>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:25 +msgid ":guilabel:`Indian E-waybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:26 +msgid "`l10n_in_edi_ewaybill`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:27 +msgid ":ref:`Indian E-way bill integration <india/e-waybill>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:28 +msgid ":guilabel:`Indian - GSTR India eFiling`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:29 +msgid "`l10n_in_reports_gstr`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:30 +msgid ":ref:`Indian GST Return filing <india/gstr>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:31 +msgid ":guilabel:`Indian - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:32 +msgid "`l10n_in_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:33 +msgid ":ref:`Indian tax reports <india/gstr_reports>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:34 +msgid ":guilabel:`Indian - Purchase Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:35 +msgid "`l10n_in_purchase`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:36 +msgid "Indian GST Purchase report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:37 +msgid ":guilabel:`Indian - Sale Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:38 +msgid "`l10n_in_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:39 +msgid "Indian GST Sale report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:40 +msgid ":guilabel:`Indian - Stock Report(GST)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:41 +msgid "`l10n_in_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:42 +msgid "Indian GST Stock report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:50 +msgid "e-Invoice system" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:52 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) e-Invoice " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:60 +msgid "NIC e-Invoice registration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:62 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` e-Invoice" +" portal to get your **API credentials**. You need these credentials to " +":ref:`configure your Odoo Accounting app <india/e-invoicing-configuration>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:66 +msgid "" +"Log in to the `NIC e-Invoice portal <https://einvoice1.gst.gov.in/>`_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:70 +msgid "" +"If you are already registered on the NIC portal, you can use the same login " +"credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Register Odoo ERP system on e-invoice web portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:75 +msgid "" +"From the dashboard, go to :menuselection:`API Registration --> User " +"Credentials --> Create API User`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:77 +msgid "" +"After that, you should receive an :abbr:`OTP (one-time password)` code on " +"your registered mobile number. Enter the OTP code and click " +":guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:79 +msgid "" +"Select :guilabel:`Through GSP` for the API interface, set :guilabel:`Tera " +"Software Limited` as GSP, and type in a :guilabel:`Username` and " +":guilabel:`Password` for your API. Once it is done, click " +":guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit API specific Username and Password" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:89 +#: ../../content/applications/finance/fiscal_localizations/india.rst:228 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:91 +msgid "" +"To enable the e-Invoice service in Odoo, go to :menuselection:`Accounting " +"--> Configuration --> Settings --> Indian Electronic Invoicing`, and enter " +"the :guilabel:`Username` and :guilabel:`Password` previously set for the " +"API." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Setup e-invoice service" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:103 +msgid "" +"To automatically send e-Invoices to the NIC e-Invoice portal, you must first" +" configure your *sales* journal by going to :menuselection:`Accounting --> " +"Configuration --> Journals`, opening your *sales* journal, and in the " +":guilabel:`Advanced Settings` tab, under :guilabel:`Electronic Data " +"Interchange`, enable :guilabel:`E-Invoice (IN)` and save." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:111 +#: ../../content/applications/finance/fiscal_localizations/india.rst:240 +msgid "Workflow" +msgstr "ขั้นตอนการทำงาน" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:118 +msgid "" +"Once an invoice is validated, a confirmation message is displayed at the " +"top. Odoo automatically uploads the JSON-signed file of validated invoices " +"to the NIC e-Invoice portal after some time. If you want to process the " +"invoice immediately, click :guilabel:`Process now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-invoicing confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:126 +#: ../../content/applications/finance/fiscal_localizations/india.rst:266 +msgid "" +"You can find the JSON-signed file in the attached files in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:127 +msgid "" +"You can check the document's :abbr:`EDI (electronic data interchange)` " +"status under the :guilabel:`EDI Document` tab or the :guilabel:`Electronic " +"invoicing` field of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:135 +msgid "" +"Once an invoice is validated and submitted, the invoice PDF report can be " +"printed. The report includes the :abbr:`IRN (Invoice Reference Number)`, " +":guilabel:`Ack. No` (acknowledgment number) and :guilabel:`Ack. Date` " +"(acknowledgment date), and QR code. These certify that the invoice is a " +"valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "IRN and QR code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:146 +msgid "e-Invoice cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:148 +msgid "" +"If you want to cancel an e-Invoice, go to the :guilabel:`Other info` tab of " +"the invoice and fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel" +" remarks` fields. Then, click :guilabel:`Request EDI cancellation`. The " +"status of the :guilabel:`Electronic invoicing` field changes to " +":guilabel:`To Cancel`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:154 +msgid "" +"Doing so cancels both the :ref:`e-Invoice <india/e-invoicing>` and the " +":ref:`E-Way bill <india/e-waybill>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:161 +msgid "" +"If you want to abort the cancellation before processing the invoice, then " +"click :guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:163 +msgid "" +"Once you request to cancel the e-Invoice, Odoo automatically submits the " +"JSON-signed file to the NIC e-Invoice portal. You can click " +":guilabel:`Process now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:170 +msgid "GST e-Invoice verification" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:172 +msgid "" +"After submitting an e-Invoice, you can verify if the invoice is signed from " +"the GST e-Invoice system website itself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:175 +msgid "" +"Download the JSON file from the attached files. It can be found in the " +"chatter of the related invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:177 +msgid "" +"Open the `NIC e-Invoice portal <https://einvoice1.gst.gov.in/>`_ and go to " +":menuselection:`Search --> Verify Signed Invoice`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:179 +msgid "Select the JSON file and submit it;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "select the JSON file for verify invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:184 +msgid "If the file is signed, a confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "verified e-invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:192 +msgid "E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:197 +msgid "" +"Odoo is compliant with the **Indian Goods and Services Tax (GST) E-waybill " +"system** requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:202 +msgid "API registration on NIC E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:204 +msgid "" +"You must register on the :abbr:`NIC (National Informatics Centre)` E-Way " +"bill portal to create your **API credentials**. You need these credentials " +"to :ref:`configure your Odoo Accounting app <india/e-waybill-" +"configuration>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:208 +msgid "" +"Log in to the `NIC E-Way bill portal <https://ewaybillgst.gov.in/>`_ by " +"clicking :guilabel:`Login` and entering your :guilabel:`Username` and " +":guilabel:`Password`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:210 +msgid "From your dashboard, go to :menuselection:`Registration --> For GSP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:211 +msgid "" +"Click :guilabel:`Send OTP`. Once you have received the code on your " +"registered mobile number, enter it and click :guilabel:`Verify OTP`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:213 +msgid "" +"Check if :guilabel:`Tera Software Limited` is already on the registered " +"GSP/ERP list. If so, use the username and password used to log in to the NIC" +" portal. Otherwise, follow the next steps;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "E-Way bill list of registered GSP/ERP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:219 +msgid "" +"Select :guilabel:`Add/New`, select :guilabel:`Tera Software Limited` as your" +" GSP Name, create a :guilabel:`Username` and a :guilabel:`Password` for your" +" API, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Submit GSP API registration details" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:230 +msgid "" +"To set up the E-Way bill service, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Indian Electronic WayBill --> Setup E-Way " +"bill`, and enter your :guilabel:`Username` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill setup odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:245 +msgid "Send an E-Way bill" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:247 +msgid "" +"You can manually send an E-Way bill by clicking :guilabel:`Send E-Way bill`." +" To send the E-Way bill automatically when an invoice or a bill is " +"confirmed, enable :guilabel:`E-Way bill (IN)` in your :ref:`Sales or " +"Purchase journal <india/e-invoicing-journals>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Send E-waybill button on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:259 +msgid "" +"Once an invoice has been issued and sent via :guilabel:`Send E-Way bill`, a " +"confirmation message is displayed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Indian e-Way bill confirmation message" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:267 +msgid "" +"Odoo automatically uploads the JSON-signed file to the government portal " +"after some time. Click :guilabel:`Process now` if you want to process the " +"invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:273 +msgid "" +"You can print the invoice PDF report once you have submitted the E-Way bill." +" The report includes the **E-Way bill number** and the **E-Way bill validity" +" date**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "E-way bill acknowledgment number and date" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:282 +msgid "E-Way bill cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:284 +msgid "" +"If you want to cancel an E-Way bill, go to the :guilabel:`E-Way bill` tab of" +" the related invoice and fill out the :guilabel:`Cancel reason` and " +":guilabel:`Cancel remarks` fields. Then, click :guilabel:`Request EDI " +"Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:289 +msgid "" +"Doing so cancels both the :ref:`e-Invoice <india/e-invoicing>` (if " +"applicable) and the :ref:`E-Way bill <india/e-waybill>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst-1 +msgid "Cancel reason and remarks" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:296 +msgid "" +"If you want to abort the cancellation before processing the invoice, click " +":guilabel:`Call Off EDI Cancellation`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:298 +msgid "" +"Once you request to cancel the E-Way bill, Odoo automatically submits the " +"JSON-signed file to the government portal. You can click :guilabel:`Process " +"Now` if you want to process the invoice immediately." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:305 +msgid "Indian GST Return filing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:310 +msgid "Enable API access" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:312 +msgid "" +"To file GST Returns in Odoo, you must first enable API access on the GST " +"portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:314 +msgid "" +"Log into the `GST portal <https://services.gst.gov.in/services/login>`_ by " +"entering your :guilabel:`Username` and :guilabel:`Password`, and go to " +":guilabel:`My Profile` on your **profile menu**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Click On the My Profile from profile" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:321 +msgid "" +"Select :guilabel:`Manage API Access`, and click :guilabel:`Yes` to enable " +"API access;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Click Yes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:326 +msgid "" +"Doing so enables a :guilabel:`Duration` drop-down menu. Select the " +":guilabel:`Duration` of your preference, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:332 +msgid "Indian GST Service In Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:334 +msgid "" +"Once you have enabled the :ref:`API access <india/gstr_api>` on the GST " +"portal, you can set up the :guilabel:`Indian GST Service` in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:337 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Indian " +"GST Service` and enter the :guilabel:`GST Username`. Click :guilabel:`Send " +"OTP`, enter the code, and finally, :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "Please enter your GST portal Username as Username" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:347 +msgid "File-in GST Return" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:349 +msgid "" +"When the :guilabel:`Indian GST Service` is configured, you can file your GST" +" return. Go to :menuselection:`Accounting --> Reporting --> India --> GST " +"Return periods` and create a new **GST Return Period** if it does not exist." +" GST Return file-in is done in **three steps** in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:354 +msgid "" +"**Tax Return Periodicity** can be :doc:`configured " +"<../accounting/reporting/tax_returns>` according to the user's needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:361 +msgid "Send GSTR-1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:363 +msgid "" +"The user can verify the :ref:`GSTR-1 <india/gstr-1_report>` report before " +"uploading it to the **GST portal** by clicking :guilabel:`GSTR-1 Report`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:365 +msgid "" +"If the **GSTR-1** report is correct, then click :guilabel:`Push to GSTN` to " +"send it to the **GST portal**. The status of the :guilabel:`GSTR-1` report " +"changes to :guilabel:`Sending`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Sending Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:371 +msgid "" +"After a few seconds, the status of the **GSTR-1** report changes to " +":guilabel:`Waiting for Status`. It means that the **GSTR-1** report has been" +" sent to the :guilabel:`GST Portal` and is being verified on the " +":guilabel:`GST Portal`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Waiting for Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:378 +msgid "" +"Once more, after a few seconds, the status either changes to " +":guilabel:`Sent` or :guilabel:`Error in Invoice`. The status " +":guilabel:`Error in Invoice` indicates that some of the invoices are not " +"correctly filled out to be validated by the **GST portal**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:382 +msgid "" +"If the state of the **GSTR-1** is :guilabel:`Sent`, it means your **GSTR-1**" +" report is ready to be filed on the **GST portal**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Sent" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:388 +msgid "" +"If the state of the **GSTR-1** is :guilabel:`Error in Invoice`, invoices can" +" be checked for errors in the :guilabel:`Log Note`. Once issues have been " +"resolved, the user can click :guilabel:`Push to GSTN` to submit the file " +"again on the **GST portal**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Error in Invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Error in Invoice Log" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:398 +msgid "" +"Click :guilabel:`Mark as Filed` after filing the **GSTR-1** report on the " +"**GST portal**. The status of the report changes to :guilabel:`Filed` in " +"**Odoo**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 in the Filed Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:407 +msgid "Receive GSTR-2B" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:409 +msgid "" +"Users can retrieve the **GSTR-2B Report** from the **GST portal**. This " +"automatically reconciles the **GSTR-2B** report with your Odoo bills;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:412 +msgid "" +"Click :guilabel:`Fetch GSTR-2B Summary` to retrieve the **GSTR-2B** summary." +" After a few seconds, the status of the report changes to :guilabel:`Waiting" +" for Reception`. This means Odoo is trying to receive the **GSTR-2B** report" +" from the **GST portal**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B in Waiting for Reception" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:419 +msgid "" +"Once more, after a few seconds, the status of the **GSTR-2B** changes to the" +" :guilabel:`Being Processed`. It means Odoo is reconciling the **GSTR-2B** " +"report with your Odoo bills;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:425 +msgid "" +"Once it is done, the status of the **GSTR-2B** report changes to either " +":guilabel:`Matched` or :guilabel:`Partially Matched`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:428 +msgid "If the status is :guilabel:`Matched`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Matched" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:433 +msgid "" +"If the status is :guilabel:`Partially Matched`, you can make changes in " +"bills by clicking :guilabel:`View Reconciled Bills`. Once it is done, click " +":guilabel:`re-match`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Partially Matched" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-2B Reconciled Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:445 +#: ../../content/applications/finance/fiscal_localizations/india.rst:490 +msgid "GSTR-3 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:447 +msgid "" +"The :ref:`GSTR-3 <india/gstr-3_report>` report is a monthly summary of " +"**sales** and **purchases**. This return is auto-generated by extracting " +"information from **GSTR-1** and **GSTR-2**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:450 +msgid "" +"Users can compare the **GSTR-3** report with the **GSTR-3** report available" +" on the **GST portal** to verify if they match by clicking :guilabel:`GSTR-3" +" Report`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:453 +msgid "" +"Once the **GSTR-3** report has been verified by the user and the tax amount " +"on the **GST portal** has been paid. Once paid, the report can be **closed**" +" by clicking :guilabel:`Closing Entry`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:459 +msgid "" +"In :guilabel:`Closing Entry`, add the tax amount paid on the **GST portal** " +"using challan, and click :guilabel:`POST` to post the :guilabel:`Closing " +"Entry`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Post Entry" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:465 +msgid "" +"Once posted, the **GSTR-3** report status changes to :guilabel:`Filed`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Filed" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:473 +msgid "Tax reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:478 +msgid "GSTR-1 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:480 +msgid "" +"The :guilabel:`GSTR-1` report is divided into sections. It displays the " +":guilabel:`Base` amount, :abbr:`CGST (Central Goods and Services Tax)`, " +":abbr:`SGST (State Goods and Service Tax)`, :abbr:`IGST (Integrated Goods " +"and Services Tax)`, and :guilabel:`CESS` for each section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-1 Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:492 +msgid "The :guilabel:`GSTR-3` report contains different sections:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:494 +msgid "Details of inward and outward supply subject to a **reverse charge**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:495 +msgid "Eligible :abbr:`ITC (Income Tax Credit)`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:496 +msgid "Values of **exempt**, **Nil-rated**, and **non-GST** inward supply;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:497 +msgid "Details of inter-state supplies made to **unregistered** persons." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 +msgid "GSTR-3 Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:3 +msgid "Indonesia" +msgstr "ประเทศอินโดนีเซีย" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:8 +msgid "E-Faktur Module" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:10 +msgid "" +"The **E-Faktur Module** is installed by default with the Indonesian " +"localization module. It allows one to generate a CSV file for one tax " +"invoice or for a batch of tax invoices to upload to the **Tax Office " +"e-Faktur** application." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:17 +msgid "NPWP/NIK settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Company**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"This information is used in the FAPR line in the effect file format. You " +"need to set a VAT number on the related partner of your Odoo company. If you" +" don't, it won't be possible to create an e-Faktur from an invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "**Your Clients**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:0 +msgid "" +"You need to set the checkbox *ID PKP* to generate e-fakturs for a customer. " +"You can use the VAT field on the customer's contact to set the NPWP needed " +"to generate the e-Faktur file. If your customer does not have an NPWP, just " +"enter the NIK in the same VAT field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:39 +msgid "Generate Tax Invoice Serial Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:41 +msgid "" +"Go to :menuselection:`Accounting --> Customers --> e-Faktur`. In order to be" +" able to export customer invoices as e-Faktur for the Indonesian government," +" you need to put here the ranges of numbers you were assigned by the " +"government. When you validate an invoice, a number will be assigned based on" +" these ranges. Afterwards, you can filter the invoices still to export in " +"the invoices list and click on *Action*, then on *Download e-Faktur*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:46 +msgid "" +"After receiving new serial numbers from the Indonesian Revenue Department, " +"you can create a set of tax invoice serial numbers group through this list " +"view. You only have to specify the Min and Max of each serial numbers' group" +" and Odoo will format the number automatically to a 13-digits number, as " +"requested by the Indonesia Tax Revenue Department." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:50 +msgid "" +"There is a counter to inform you how many unused numbers are left in that " +"group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:58 +msgid "Generate e-faktur csv for a single invoice or a batch invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:60 +msgid "" +"Create an invoice from :menuselection:`Accounting --> Customers --> " +"Invoices`. If the invoice customer's country is Indonesia and the customer " +"is set as *ID PKP*, Odoo will allow you to create an e-Faktur." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:63 +msgid "" +"Set a Kode Transaksi for the e-Faktur. There are constraints related to the " +"Kode transaksi and the type of VAT applied to invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:69 +msgid "" +"Odoo will automatically pick the next available serial number from the " +"e-Faktur number table (see the :ref:`section above " +"<localization_indonesia/tax_invoice_sn>`) and generate the e-faktur number " +"as a concatenation of Kode Transaksi and serial number. You can see this " +"from the invoice form view under the page *Extra Info* in the box " +"*Electronic Tax*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:77 +msgid "" +"Once the invoice is posted, you can generate and download the e-Faktur from " +"the *Action* menu item *Download e-faktur*. The checkbox *CSV created* will " +"be set." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:83 +msgid "" +"You can select multiple invoices in list view and generate a batch e-Faktur " +".csv." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:88 +msgid "Kode Transaksi FP (Transaction Code)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:90 +msgid "" +"The following codes are available when generating an e-Faktur. - 01 Kepada " +"Pihak yang Bukan Pemungut PPN (Customer Biasa) - 02 Kepada Pemungut " +"Bendaharawan (Dinas Kepemerintahan) - 03 Kepada Pemungut Selain Bendaharawan" +" (BUMN) - 04 DPP Nilai Lain (PPN 1%) - 06 Penyerahan Lainnya (Turis Asing) -" +" 07 Penyerahan yang PPN-nya Tidak Dipungut (Kawasan Ekonomi Khusus/ Batam) -" +" 08 Penyerahan yang PPN-nya Dibebaskan (Impor Barang Tertentu) - 09 " +"Penyerahan Aktiva (Pasal 16D UU PPN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:103 +msgid "" +"Correct an invoice that has been posted and downloaded: Replace Invoice " +"feature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:105 +msgid "" +"Cancel the original wrong invoice in Odoo. For instance, we will change the " +"Kode Transakski from 01 to 03 for the INV/2020/0001." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:107 +msgid "" +"Create a new invoice and set the canceled invoice in the *Replace Invoice* " +"field. In this field, we can only select invoices in *Cancel* state from the" +" same customer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:109 +msgid "" +"As you validate, Odoo will automatically use the same e-Faktur serial number" +" as the canceled and replaced invoice replacing the third digit of the " +"original serial number with *1* (as requested to upload a replacement " +"invoice in the e-Faktur app)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:120 +msgid "" +"Correct an invoice that has been posted but not downloaded yet: Reset " +"e-Faktur" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:122 +msgid "Reset the invoice to draft and cancel it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:123 +msgid "Click on the button *Reset e-Faktur* on the invoice form view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/indonesia.rst:124 +msgid "" +"The serial number will be unassigned, and we will be able to reset the " +"invoice to draft, edit it and re-assign a new serial number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:3 +msgid "Italy" +msgstr "ประเทศอิตาลี" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:10 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Italian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:20 +msgid "Italy - Accounting" +msgstr "ประเทศอิตาลี - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:21 +msgid "`l10n_it`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:23 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:26 +msgid "Italy - E-invoicing" +msgstr "ประเทศอิตาลี - ใบแจ้งหนี้อิเล็กทรอนิกส์" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:24 +msgid "`l10n_it_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:25 +msgid "e-invoice implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:27 +msgid "`l10n_it_edi_withholding`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:28 +msgid "e-invoice withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:29 +msgid "Italy - Accounting Reports" +msgstr "ประเทศอิตาลี - รายงานทางบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:30 +msgid "`l10n_it_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:31 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:22 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:25 +msgid "Country-specific reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:32 +msgid "Italy - Stock DDT" +msgstr "ประเทศอิตาลี - สต็อก DDT" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:33 +msgid "`l10n_it_stock_ddt`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:34 +msgid "Transport documents - Documento di Trasporto (DDT)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:43 +msgid "" +"Configuring the company's information ensures your Accounting database is " +"properly set up. To add information, go to :menuselection:`Settings --> " +"General Settings`, and in the :guilabel:`Companies` section, click " +":guilabel:`Update info`. From here, fill out the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:47 +msgid ":guilabel:`Address`: the address of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:48 +msgid ":guilabel:`VAT`: VAT of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:49 +msgid ":guilabel:`Codice Fiscale`: the fiscal code of the company;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:50 +msgid ":guilabel:`Tax System`: the tax system under which the company falls;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Company information to provide" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:57 +msgid "E-invoicing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:59 +msgid "" +"The :abbr:`SdI (Sistema di Interscambio)` is the electronic invoicing system" +" used in Italy. It enables to send and receive electronic invoices to and " +"from customers. The documents must be in XML format and formally validated " +"by the system before being delivered." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:63 +msgid "" +"To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di" +" Interscambio)` service must be notified that the user's files are to be " +"sent to **Odoo** and processed on their behalf. To so, you must set up " +"Odoo's :guilabel:`Codice Destinatario` on the **Agenzia Delle Entrate** " +"portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:68 +msgid "" +"Go to https://ivaservizi.agenziaentrate.gov.it/portale/ and authenticate;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:69 +msgid "Go to section :menuselection:`Fatture e Corrispettivi`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:70 +msgid "" +"Set the user as Legal Party for the VAT number you wish to configure the " +"electronic address;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:71 +msgid "" +"In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> " +"Registrazione dell’indirizzo telematico dove ricevere tutte le fatture " +"elettroniche`, insert Odoo's :guilabel:`Codice Destinatario` `K95IV18`, and " +"confirm." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:76 +msgid "Electronic Data Interchange (EDI)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:78 +msgid "" +"Odoo uses the **FatturaPA** :abbr:`EDI (Electronic Data Interchange)` format" +" for the Italian localization and is enabled on the default journals when " +"installed. When the **file processing authorization** has been set, all " +"**invoices** and **bills** are automatically sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:83 +msgid "" +"You can :ref:`enable electronic invoicing for other sales and purchase " +"journals <e-invoicing/configuration>` than the default ones." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:86 +msgid "" +"You can check the current status of an invoice by the :guilabel:`Electronic " +"invoicing` field. The XML file can be found in the **chatter** of the " +"invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Electronic invoicing status (waiting for confirmation)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:97 +msgid "File processing authorization (Odoo)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:99 +msgid "" +"Since the files are transmitted through Odoo's server before being sent to " +"the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you " +"need to authorize Odoo to process your files from your database. To do so, " +"go to :menuselection:`Accounting --> Configuration --> Settings --> " +"Electronic Document Invoicing`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:104 +msgid "There are **three** modes available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:108 +msgid ":guilabel:`Demo`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:107 +msgid "" +"This mode simulates an environment in which invoices are sent to the " +"government. In this mode, invoices need to be *manually* downloaded as XML " +"files and uploaded to the **Agenzia delle Entrate**'s website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:112 +msgid ":guilabel:`Test (experimental)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:111 +msgid "" +"This mode sends invoices to a non-production (i.e., test) service made " +"available by the **Agenzia delle Entrate**. Saving this change directs all " +"companies on the database to use this configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 +msgid ":guilabel:`Official`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 +msgid "" +"This is a production mode that sends your invoices directly to the **Agenzia" +" delle Entrate**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:117 +msgid "" +"Once a mode is selected, you need to accept the **terms and conditions** by " +"ticking :guilabel:`Allow Odoo to process invoices`, and then " +":guilabel:`Save`. You can now record your transactions in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:122 +msgid "" +"Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is " +"**irreversible**. Once in :guilabel:`Official` mode, it is not possible to " +"select :guilabel:`Test (experimental)` or :guilabel:`Demo`, and same for " +":guilabel:`Test (experimental)`. We recommend creating a separate database " +"for testing purposes only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:128 +msgid "" +"When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have " +"a partner using one of the following fake :guilabel:`Codice Destinatario` " +"given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. " +"Any real production :guilabel:`Codice Destinario` of your customers will not" +" be recognized as valid by the test service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italy's electronic document invoicing options" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:138 +msgid "Taxes configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:140 +msgid "" +"Many of the e-invoicing features are implemented using Odoo's tax system. As" +" such, it is very important that taxes are properly configured in order to " +"generate invoices correctly and handle other billing use cases. For example," +" specific configurations are required for the **reverse charge** type of " +"taxes. In case of a **reverse charge** tax, the seller does *not* charge the" +" customer for the VAT but, instead, the customer pays the VAT *themselves* " +"to their government. There are **two** main types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:147 +msgid ":ref:`external reverse charge <italy/external-reverse>`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:148 +msgid ":ref:`internal reverse charge <italy/internal-reverse>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:153 +msgid "External reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:156 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:387 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:212 +msgid "Invoices" +msgstr "การแจ้งหนี้" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:158 +msgid "" +"To make an export invoice, make sure that the invoice lines all use a tax " +"configured for **reverse charge**. The **Italian** localization contains an " +"**example** of a reverse charge tax for export in the EU to be used as " +"reference (`0% EU`, invoice label `00eu`), which can be found under " +":menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt " +"from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has " +"exoneration of tax (Italy)` option ticked, with both the " +":guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." +msgstr "" +"หากต้องการสร้างใบแจ้งหนี้การส่งออก " +"ตรวจสอบให้แน่ใจว่ารายการใบแจ้งหนี้ทั้งหมดใช้ภาษีที่กำหนดค่าสำหรับ " +"**ค่าธรรมเนียมย้อนกลับ** การแปลเป็นภาษาท้องถิ่น **ภาษาอิตาลี** มี " +"**ตัวอย่าง** " +"ของการเรียกเก็บภาษีย้อนกลับสำหรับการส่งออกในสหภาพยุโรปเพื่อใช้เป็นข้อมูลอ้างอิง" +" (`0% EU`, ป้ายกำกับใบแจ้งหนี้ `00eu`) ซึ่งอยู่ใต้ :menuselection " +":`ระบบบัญชี --> การกำหนดค่า --> ภาษี` " +"การส่งออกได้รับการยกเว้นภาษีมูลค่าเพิ่ม ดังนั้นภาษี **ค่าธรรมเนียมย้อนกลับ**" +" จึงต้องมีการทำเครื่องหมายที่ :guilabel:`มีการยกเว้นภาษี (อิตาลี)` " +"โดยทำเครื่องหมายทั้ง :guilabel:`Exoneration` และ " +":guilabel:`การอ้างอิงกฎหมาย` เติมใน." + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "External reverse charge settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:170 +msgid "" +"If you need to use a different kind of :guilabel:`Exoneration`, click " +":menuselection:`Action --> Duplicate` within the tax menu to create a copy " +"of an existing similar tax. Then, select another :guilabel:`Exoneration`, " +"and :guilabel:`Save`. Repeat this process as many times as you need " +"different kind of :guilabel:`Exoneration` taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:176 +msgid "" +"**Rename** your taxes in the :guilabel:`Name` field according to their " +":guilabel:`Exoneration` to differentiate them easily." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:179 +msgid "" +"On your invoice, select the corresponding tax you need in the " +":guilabel:`Taxes` field. You can find the following **additional info** by " +"opening the **XML** file of the issued invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:182 +msgid "" +":guilabel:`SdI address (Codice Destinatario)`: must be filled for both " +"**EU** or **non-EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:183 +msgid "" +":guilabel:`Country Id`: must contain the country of the foreign seller in " +"the two-letter ISO (Alpha-2) code (ex., `IT` for 'Italy');" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:185 +msgid ":guilabel:`CAP`: must be filled with `00000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:186 +msgid "" +":guilabel:`Partita Iva` (**VAT number**): must contain the **VAT** number " +"for **EU businesses** and `OO99999999999` (double 'O' **letter**, not " +"'zero') for **non-EU businesses**. In case of private customers without " +"**VAT** number, use `0000000`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:189 +msgid "" +":guilabel:`Fiscal Code`: for foreign entities without an actual **Codice " +"Fiscale**, any recognizable identifier is valid." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:193 +msgid "Odoo does not support sending user-modified XML files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:195 +msgid "" +"For **invoices**, multiple configurations are technically identified by a " +":guilabel:`Tipo Documento` code:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:198 +msgid "`TD02` - Down payments;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:199 +msgid "`TDO7` - Simplified invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:200 +msgid "`TD08` - Simplified credit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:201 +msgid "`TD09` - Simplified debit note;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:202 +msgid "`TD24` - Deferred invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:206 +msgid "`TD02`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:208 +msgid "Down payments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:210 +msgid "" +"**Down payment** invoices are imported/exported with a different " +":guilabel:`Tipo Documento` code `TDO2` than regular invoices. Upon import of" +" the invoice, it creates a regular vendor bill." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:214 +msgid "Odoo exports moves as `TD02` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:216 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:274 +msgid "Is an invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:217 +msgid "" +"All invoice lines are related to **sales order lines** that have the flag " +"`is_downpayment` set as `True`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:220 +msgid "`TD07`, `TD08`, and `TD09`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:222 +msgid "Simplified invoices, and credit/debit notes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:224 +msgid "" +"Simplified invoices and credit notes can be used to certify **domestic " +"transactions** under **400 EUR** (VAT included). Its status is the same as a" +" regular invoice, but with fewer information requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:228 +msgid "For a **simplified** invoice to be established, it must include:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:230 +msgid "" +":guilabel:`Customer Invoice` reference: **unique** numbering sequence with " +"**no gaps**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:231 +msgid ":guilabel:`Invoice Date`: issue **date** of the invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:232 +msgid "" +":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number," +" name, full address) under :menuselection:`General Settings --> Companies " +"(section)`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:234 +msgid "" +":guilabel:`VAT`: the **buyer**'s VAT/TIN number (on their profile card);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:235 +msgid ":guilabel:`Total`: the total **amount** (VAT included) of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:237 +msgid "" +"In the :abbr:`EDI (Electronic Data Interchange)`, Odoo exports invoices as " +"simplified if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:239 +msgid "It is a **domestic** transaction (i.e., the partner is from Italy);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:240 +msgid "The buyer's data is **insufficient** for a regular invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:241 +msgid "" +"The **required fields** for a regular invoice (address, ZIP code, city, " +"country) are provided;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:243 +msgid "The total amount VAT included is **less** than **400 EUR**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:246 +msgid "" +"The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in " +"the Gazzetta Ufficiale " +"<https://www.gazzettaufficiale.it/eli/id/2019/05/24/19A03271/sg>`_. We " +"advise you to check the current official value." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:250 +msgid "`TD24`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:252 +msgid "Deferred invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:254 +msgid "" +"The **deferred invoice** is an invoice that is **issued at a later time** " +"than the sale of goods or the provision of services. A **deferred invoice** " +"has to be issued at the latest within the **15th day** of the month " +"following the delivery covered by the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:258 +msgid "" +"It usually is a **summary invoice** containing a list of multiple sales of " +"goods or services, carried out in the month. The business is allowed to " +"**group** the sales into **one invoice**, generally issued at the **end of " +"the month** for accounting purposes. Deferred invoices are default for " +"**wholesaler** having recurrent clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:263 +msgid "" +"If the goods are transported by a **carrier**, every delivery has an " +"associated **Documento di Transporto (DDT)**, or **Transport Document**. The" +" deferred invoice **must** indicate the details of all the **DDTs** " +"information for better tracing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:268 +msgid "" +"E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` " +":ref:`module <italy/modules>`. In this case, a dedicated :guilabel:`Tipo " +"Documento` `TD24` is used in the e-invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:272 +msgid "Odoo exports moves as `TD24` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:275 +msgid "" +"Is associated to deliveries whose **DDTs** have a **different** date than " +"the issuance date of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:281 +msgid "" +"Italian companies buying goods or services from EU countries (or services " +"from non-EU countries) must send the information contained within the bill " +"received to the **Agenzia delle Entrate**. This allows you to complete tax-" +"related information on your bill, and to send it. The seller must be set as " +":guilabel:`Cedente/Prestatore`, and the buyer as " +":guilabel:`Cessionario/Committente`. Contained within the **XML** document " +"for the vendor bill, the vendor's credentials show as " +":guilabel:`Cedente/Prestatore`, and your company's credentials as " +":guilabel:`Cessionario/Committente`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:290 +msgid "" +"Self-billing invoices or VAT invoice integrations must be issued and sent to" +" the tax agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:292 +msgid "" +"When inputting taxes in a vendor bill, it is possible to select **reverse " +"charge** taxes. These are automatically activated in the Italian fiscal " +"position. By going to :menuselection:`Accounting --> Configuration --> " +"Taxes`, the `10%` and `22%` :guilabel:`Goods` and :guilabel:`Services` tax " +"scopes are activated and preconfigured with the correct tax grids. These are" +" set up automatically to ensure the correct booking of accounting entries " +"and display of the tax report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:298 +msgid "" +"For **vendor bills**, **three** types of configurations are technically " +"identified by a code called :guilabel:`Tipo Documento`:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:301 +msgid "`TD17` - Buying services from **EU** and **non-EU** countries;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:302 +msgid "`TD18` - Buying **goods** from **EU**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:303 +msgid "" +"`TD19` - Buying **goods** from a **foreign** vendor, but the **goods** are " +"already in **Italy** in a **VAT deposit**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:308 +msgid "`TD17`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:310 +msgid "Buying **services** from **EU** and **non-EU** countries:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:312 +msgid "" +"The foreign *seller* invoices a service with a **VAT-excluded** price, as it" +" is not taxable in Italy. The VAT is paid by the *buyer* in Italy;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:315 +msgid "" +"Within EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:317 +msgid "" +"Non-EU: the *buyer* sends themselves an invoice (i.e., **self-billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:319 +msgid "" +"Odoo exports a transaction as `TD17` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:321 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:335 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:351 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:411 +msgid "Is a vendor bill;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:322 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:336 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:412 +msgid "" +"At least one tax on the invoice lines targets the tax grids :ref:`VJ " +"<italy/grids>`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:323 +msgid "" +"All invoice lines either have :guilabel:`Services` as **products**, or a tax" +" with the :guilabel:`Services` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:326 +msgid "`TD18`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:328 +msgid "Buying **goods** from **EU**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:330 +msgid "" +"Invoices issued within the EU follow a **standard format**, therefore only " +"an integration of the existing invoice is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:333 +msgid "" +"Odoo exports a transaction as `TD18` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:337 +msgid "" +"All invoice lines either have :guilabel:`Consumable` as **products**, or a " +"tax with the :guilabel:`Goods` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:340 +msgid "`TD19`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:342 +msgid "" +"Buying **goods** from a **foreign** vendor, but the **goods** are already in" +" **Italy** in a **VAT deposit**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:345 +msgid "" +"From EU: the *buyer* integrates the invoice received with the **VAT " +"information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:347 +msgid "" +"Non-EU: the *buyer* sends an invoice to *themselves* (i.e., **self-" +"billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:349 +msgid "Odoo exports a move as a `TD19` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:352 +msgid "" +"At least one tax on the invoice lines targets the tax grid :ref:`VJ3 " +"<italy/grids>`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:353 +msgid "" +"All invoice lines either have :guilabel:`Consumable` products, or a tax with" +" :guilabel:`Goods` as tax scope." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:357 +msgid "" +"Odoo does not offer the `Conservazione Sostitutiva " +"<https://www.agid.gov.it/index.php/it/piattaforme/conservazione>`_ " +"requirements. Other providers and **Agenzia delle Entrate** supply free and " +"certified storage to meet the requested conditions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:365 +msgid "Internal reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:368 +msgid "" +"Odoo currently does not support domestic **internal reverse charge** " +"processes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:373 +msgid "'Reverse Charge' tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:375 +msgid "" +"The Italian localization has a specific **tax grid** section for **reverse " +"charge** taxes. These tax grids are identifiable by the :ref:`VJ " +"<italy/grids>` tag, and can be found under :menuselection:`Accounting --> " +"Reporting --> Audit Reports: Tax Report`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst-1 +msgid "Italian reverse charge tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:384 +msgid "San Marino" +msgstr "ประเทศซานมารีโน" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:389 +msgid "" +"San Marino and Italy have special agreements on e-invoicing operations. As " +"such, **invoices** follow the regular **reverse charge** rules. Additional " +"requirements are not enforced by Odoo, however, the user is requested by the" +" **State** to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:393 +msgid "" +"Select a tax with the option :guilabel:`Has exoneration of tax (Italy)` " +"ticked, and the :guilabel:`Exoneration` set to `N3.3`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:395 +msgid "" +"Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice " +"Destinatario` `2R4GT08`. The invoice is then routed by a dedicated office in" +" San Marino to the correct business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:399 +msgid "Bills" +msgstr "ใบเรียกเก็บเงิน" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:401 +msgid "" +"When a **paper bill** is received from San Marino, any Italian company " +"**must** submit that invoice to the **Agenzia delle Entrate** by indicating " +"the e-invoice's :guilabel:`Tipo Documento` field with the special value " +"`TD28`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:407 +msgid "`TD28`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:409 +msgid "Odoo exports a move as `TD28` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:413 +msgid "The **country** of the partner is **San Marino**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:416 +msgid "Pubblica amministrazione (B2G)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:419 +msgid "" +"Odoo does **not** send invoices directly to the government as they need to " +"be signed. If we see that the codice destinatario is 6 digits, then it is " +"not sent to the PA automatically, but you can download the XML, sign it with" +" an external program and send it through the portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:424 +msgid "Digital qualified signature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:426 +msgid "" +"For invoices and bills intended to the **Pubblica Amministrazione (B2G)**, a" +" **Digital Qualified Signature** is required for all files sent through the " +":abbr:`SdI (Sistema di Interscambio)`. The **XML** file must be certified " +"using a certificate that is either:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:430 +msgid "a **smart card**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:431 +msgid "a **USB token**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:432 +msgid "a **Hardware Security Module (HSM)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:435 +msgid "CIG, CUP, DatiOrdineAcquisto" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:437 +msgid "" +"To ensure the effective traceability of payments by public administrations, " +"electronic invoices issued to the public administrations must contain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:440 +msgid "" +"The :abbr:`CIG (Codice Identificativo Gara)`, except in cases of exclusion " +"from traceability obligations provided by law n. 136 of August 13, 2010;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:442 +msgid "" +"The :abbr:`CUP (Codice Unico di Progetto)`, in case of invoices related to " +"public works." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:444 +msgid "" +"If the **XML** file requires it, the **Agenzia Delle Entrate** can *only* " +"proceed payments of electronic invoices when the **XML** file contains a " +":abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di " +"Progetto)`. For each electronic invoice, it is **necessary** to indicate the" +" :abbr:`CUU (Codice Univoco Ufficio)`, which represents the unique " +"identifier code that allows the :abbr:`SdI (Sistema di Interscambio)` to " +"correctly deliver the electronic invoice to the recipient office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:452 +msgid "" +"The :abbr:`Codice Unico di Progetto)` and the :abbr:`CIG (Codice " +"Identificativo Gara)` must be included in one of the **2.1.2** " +"(DatiOrdineAcquisto), **2.1.3** (Dati Contratto), **2.1.4** " +"(DatiConvenzione), **2.1.5** (Date Ricezione), or **2.1.6** (Dati Fatture " +"Collegate) information blocks. These correspond to the elements named " +":guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice " +"**XML** file, whose table can be found on the government `website " +"<http://www.fatturapa.gov.it/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:458 +msgid "" +"The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic " +"invoice corresponding to the element **1.1.4** " +"(:guilabel:`CodiceDestinario`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:3 +msgid "Kenya" +msgstr "ประเทศเคนยา" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:10 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Kenyan localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:19 +msgid ":guilabel:`Kenyan - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:20 +msgid "`l10n_ke`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:21 +msgid "" +"Installing this module grants you access to the list of accounts used in the" +" local GAAP and the list of common taxes (VAT, etc.)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:23 +msgid ":guilabel:`Kenyan - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:24 +msgid "`l10n_ke_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:25 +msgid "" +"Installing this module grants you access to improved accounting reports for " +"Kenya, such as Profit and Loss and Balance Sheets." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:28 +msgid "" +"You also have to install the **Kenya Tremol Device EDI Integration** package" +" to be able to report your taxes to the **Kenya Revenue Authority (KRA)** " +"using the Tremol G03 Control Unit:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:37 +msgid ":guilabel:`Kenya Tremol Device EDI Integration`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:38 +msgid "`l10n_ke_edi_tremol`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:39 +msgid "" +"Installing this module integrates with the Kenyan G03 Tremol control unit " +"device to report taxes to KRA through TIMS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "The three modules for the Kenya Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:47 +msgid "Kenyan TIMS integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:49 +msgid "" +"The Kenya Revenue Authority (KRA) has decided to go digital for tax " +"collection through the **Tax Invoice Management System (TIMS)**. As of " +"December 1st, 2022, all VAT-registered persons should comply with TIMS. The " +"goal is to reduce VAT fraud, increase tax revenue, and increase VAT " +"compliance through standardization, validation, and transmission of invoices" +" to KRA on a real-time or near real-time basis." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:55 +msgid "" +"All VAT-registered taxpayers should use a **compliant tax register**. Odoo " +"decided to develop the integration of the **Tremol G03 Control Unit (type " +"C)**, which can be run locally through USB. This device validates invoices " +"to ensure financial documents meet the new regulations and send the " +"validated tax invoices directly to KRA. Installing a proxy server that " +"provides a gateway between users and the internet is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:62 +msgid "Installing the proxy server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:64 +msgid "" +"Go to `odoo.com/download <https://www.odoo.com/page/download>`_, fill out " +"the required information and click :guilabel:`Download`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Install the Proxy Server on a Windows device" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:71 +msgid "" +"Once it is loaded on your computer, a wizard opens. You have to read and " +"agree with the terms of the agreement. On the next page, select the " +":guilabel:`type of install: Odoo IoT`. Then, click :guilabel:`Next` and " +":guilabel:`Install`. Once completed, click :guilabel:`Next`. Check the " +":guilabel:`Start Odoo` box to be redirected to Odoo automatically, and then " +"click :guilabel:`Finish`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 +msgid "" +"A new page opens, confirming your :doc:`IoT Box " +"<../../productivity/iot/config/connect>` is up and running. Connect your " +"physical device **Tremol G03 Control Unit (type C)** to your laptop via USB." +" In the :guilabel:`IoT Device` section, check that your Tremol G03 Control " +"Unit (type C) appears, confirming the connection between the device and your" +" computer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst-1 +msgid "Your IoT box is up and running" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:86 +msgid "" +"If the device is not detected, try to plug it in again or click on the " +":guilabel:`Restart` button in the top right corner." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 +msgid "" +":doc:`Connect an IoT box to your database " +"<../../productivity/iot/config/connect>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 +msgid "Sending the data to KRA using the Tremol G03 Control Unit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:95 +msgid "" +"As a pre-requisite, check out that the :ref:`Kenyan Accounting modules " +"<localization/kenya/configuration>` are installed on your database. Then, go" +" to :menuselection:`Accounting --> Configuration --> Settings --> Kenya TIMS" +" Integration section`, and check that the :guilabel:`control Unit Proxy " +"Address` matches the address of the IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:100 +msgid "" +"To send data to KRA, create a new invoice by going to " +":menuselection:`Accounting Dashboard --> Customer Invoice card` and clicking" +" :guilabel:`New Invoice`. Upon confirmation of a new invoice, the " +":guilabel:`Send invoice to Fiscal Device` button appears. Clicking on it " +"sends the invoice details to the device and from the device to the " +"government. The :guilabel:`CU Invoice Number` field is now completed in your" +" invoice, confirming the information has been sent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:106 +msgid "" +"The :guilabel:`Tremol G03 Fiscal Device` tab contains fields that are " +"automatically completed once the invoice is sent to the government:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:109 +msgid "" +":guilabel:`CU QR Code`: Url from the KRA portal which reflects a QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:110 +msgid "" +":guilabel:`CU Serial Number`: reflects the serial number of the device." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:111 +msgid "" +":guilabel:`CU Signing Date and Time`: The date and time when the invoice has" +" been sent to KRA." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:113 +msgid "" +"If you click on :guilabel:`Send and Print`, a .pdf of the invoice is " +"generated. The :guilabel:`Kenyan Fiscal Device Info` is mentioned on the " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:117 +msgid "" +"To verify KRA has received the invoice information, take the :guilabel:`CU " +"Invoice Number` and enter it in the :guilabel:`Invoice Number Checker` " +"section on `Kenya Revenue Authority website <https://itax.kra.go.ke/KRA-" +"Portal>`_. Click :guilabel:`Validate` and find the invoice details." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:3 +msgid "Luxembourg" +msgstr "ประเทศลักเซมเบิร์ก" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:8 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Luxembourgish localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:17 +msgid ":guilabel:`Luxembourg - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:18 +msgid "`l10n_lu`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:20 +msgid ":guilabel:`Luxembourg - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:21 +msgid "`l10n_lu_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:23 +msgid ":guilabel:`Luxembourg - Annual VAT Report`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:24 +msgid "`l10n_lu_reports_annual_vat`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"The three modules for the Luxembourgish Fiscal Localization Package on Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:32 +msgid "" +"Installing the module :guilabel:`Luxembourg - Accounting Reports` installs " +"all three modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:36 +msgid "Standard Chart of Accounts - PCN 2020" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:38 +msgid "" +"Odoo's :ref:`fiscal localization package <fiscal_localizations/packages>` " +"for Luxembourg includes the current **Standard Chart of Accounts (PCN " +"2020)**, effective since January 2020." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:42 +msgid "eCDF tax return" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:44 +msgid "" +"Tax returns in Luxembourg require a specific XML file to upload on the eCDF." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:46 +msgid "" +"To download it, go to :menuselection:`Accounting --> Report --> Audit " +"Reports --> Tax Report`, and click on :guilabel:`Export eCDF declaration`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:51 +msgid "" +"`Platform for electronic gathering of financial data (eCDF) " +"<http://www.ecdf.lu>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:54 +msgid "Annual tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:56 +msgid "" +"You can generate an XML file to electronically file your annual tax report " +"with the tax office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:58 +msgid "" +"To do so, go to :menuselection:`Accounting --> Report --> Luxembourg --> " +"Annual Tax Report`, click on :guilabel:`Create`, then define the annual " +"period in the :guilabel:`Year` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:61 +msgid "" +"The **simplified annual declaration** is automatically generated. You can " +"manually add values in all the fields to get a **complete annual " +"declaration**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "" +"Odoo Accounting (Luxembourg localization) generates an annual tax " +"declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:68 +msgid "" +"To help you complete it, you can use the information provided on the " +":guilabel:`Tax Report`. To do so, go to :menuselection:`Accounting --> " +"Report --> Audit Reports --> Tax Report`, then click on the :guilabel:`Tax " +"Report` dropdown menu and select the type of report you want to display." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst-1 +msgid "Dropdown menu to select the type of Tax Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:76 +msgid "Finally, click on :guilabel:`Export XML` to download the XML file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:79 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Annual VAT Report` " +"to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:82 +msgid "FAIA (SAF-T)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:84 +msgid "" +"**FAIA (Fichier d’Audit Informatisé AED)** is a standardized and structured " +"file that facilitates the exchange of information between the taxpayers' " +"accounting system and the tax office. It is the Luxembourgish version of the" +" OECD-recommended SAF-T (Standard Audit File for Tax)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:88 +msgid "" +"Odoo can generate an XML file that contains all the content of an accounting" +" period according to the rules imposed by the Luxembourg tax authorities on " +"digital audit files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:92 +msgid "" +"This feature requires the module :guilabel:`Luxembourg - Accounting Reports`" +" to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:95 +msgid "Export FAIA file" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:97 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Audit Reports --> " +"General Ledger`, then click on :guilabel:`FAIA`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:3 +msgid "Mexico" +msgstr "ประเทศเม็กซิโก" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:20 +msgid "" +"A video on the Mexican localization is also available. This video covers how" +" to implement this localization from scratch, including how to set up the " +"configurations, how to complete common workflows, and provides an in-depth " +"look at several specific use cases, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:24 +msgid "" +"`Video webinar of a complete demo " +"<https://www.youtube.com/watch?v=5cdogjm0GCI>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:29 +msgid "" +"The Odoo Mexican localization modules allow for the signing of electronic " +"invoices, according to the specifications of the |SAT| for `version 4.0 of " +"the CFDI <http://omawww.sat.gob.mx/ " +"tramitesyservicios/Paginas/documentos/Anexo_20_Guia_de_llenado_CFDI.pdf>`_, " +"a legal requirement, as of January 1, 2022. These modules also add relevant " +"accounting reports (such as: the |DIOT|, enables foreign trade, and the " +"creation of delivery guides)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:36 +msgid "" +"In order to electronically sign any documents in Odoo, ensure the *Sign* " +"application is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:43 +msgid "Requirements" +msgstr "ข้อกำหนด" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:45 +msgid "" +"It is necessary to meet the following requirements before configuring the " +"Mexican localization modules in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:50 +msgid "Be registered in the |SAT|, with a valid |RFC|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:51 +msgid "" +"Have a `Certificate of Digital Seal <https://www.gob.mx/sat/acciones-y-" +"programas/ certificado-de-sello-digital>`_ (CSD)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:53 +msgid "" +"Choose a PAC (Proveedor Autorizado de Certificación / Authorized " +"Certification Provider). Currently, Odoo works with the following |PAC|\\s: " +"`Solución Factible <https://solucionfactible.com/>`_, `Quadrum (formerly " +"Finkok) <https://cfdiquadrum.com.mx/>`_ and `SW Sapien - Smarter Web " +"<https://sw.com.mx/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:57 +msgid "" +"Have knowledge and experience with billing, sales, and accounting in Odoo. " +"This documentation **only** contains the necessary information needed to use" +" Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:61 +msgid "Installing modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:63 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Mexican localization. The :doc:`Accounting <../accounting>` " +"and *Contacts* modules are required to be installed for this configuration:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:74 +msgid ":guilabel:`Mexico - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:75 +msgid "`l10n_mx`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:76 +msgid "" +"The default :doc:`fiscal localization package <../fiscal_localizations>`, " +"adds accounting characteristics for the Mexican localization, such as: the " +"most common taxes and the chart of accounts – based on `the SAT account " +"grouping code " +"<https://www.gob.mx/cms/uploads/attachment/file/151586/codigo_agrupador.pdf>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:80 +msgid ":guilabel:`EDI for Mexico`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:81 +msgid "`l10n_mx_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:82 +msgid "" +"Includes all the technical and functional requirements to generate and " +"validate :doc:`Electronics Documents " +"<../accounting/customer_invoices/electronic_invoicing>` — based on the " +"technical documentation published by the |SAT|. This allows you to send " +"invoices (with or without addedums) and payment complements to the " +"government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:86 +msgid ":guilabel:`EDI v4.0 for Mexico`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:87 +msgid "`l10n_mx_edi_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:88 +msgid "" +"Necessary to create XML documents with the correct specifications of the " +"CFDI 4.0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:89 +msgid ":guilabel:`Odoo Mexican Localization Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:90 +msgid "`l10n_mx_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:91 +msgid "" +"Adapts reports for Mexico's Electronic Accounting: Chart of Accounts, Trial " +"Balance, and |DIOT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:93 +msgid ":guilabel:`Mexico - Localization Reports for Closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:94 +msgid "`l10n_mx_reports_closing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:95 +msgid "" +"Necessary to create the Closing Entry (Also known as the *month 13th move*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:96 +msgid ":guilabel:`Odoo Mexican XML Polizas Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:97 +msgid "`l10n_mx_xml_polizas`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:98 +msgid "" +"Allows the export of XML files of Journal Entries for a compulsory audit." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:99 +msgid ":guilabel:`Odoo Mexican XML Polizas Export Edi bridge`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:100 +msgid "`l10n_mx_xml_polizas_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:101 +msgid "Complements the module `l10n_mx_xml_polizas`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:104 +msgid "" +"When installing a database from scratch and selecting :guilabel:`Mexico` as " +"the country, Odoo automatically installs the following modules: " +":guilabel:`Mexico - Accounting`, :guilabel:`EDI for Mexico`, and " +":guilabel:`EDI v4.0 for Mexico`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:108 +msgid "" +"The following modules are optional. It's recommended to install them *only* " +"if meeting a specific requirement. Make sure that they are needed for the " +"business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:118 +msgid ":guilabel:`EDI for Mexico (Advanced Features)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:119 +msgid "`l10n_mx_edi_extended`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:120 +msgid "" +"Adds the external trade complement to invoices: A legal requirement for " +"selling products to foreign countries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:122 +msgid ":guilabel:`EDI v4.0 for Mexico (COMEX)`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:123 +msgid "`l10n_mx_edi_extended_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:124 +msgid "Adapts the module `l10n_mx_edi_extended` for CFDI 4.0." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:125 +msgid ":guilabel:`Mexico - Electronic Delivery Guide`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:126 +msgid "`l10n_mx_edi_stock`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:127 +msgid "" +"Lets you create a *Carta Porte*: A bill of lading that proves to the " +"government you are sending goods between A & B with a signed electronic " +"document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:129 +msgid ":guilabel:`Electronic Delivery Guide for Mexico CFDI 4.0`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:130 +msgid "`l10n_mx_edi_stock_40`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:131 +msgid "Adapts the module `l10n_mx_edi_stock` for CFDI 4.0" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:132 +msgid ":guilabel:`Odoo Mexico Localization for Stock/Landing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:133 +msgid "`l10n_mx_edi_landing`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:134 +msgid "" +"Allows managing customs numbers related to landed costs in electronic " +"documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:139 +msgid "" +"After installing the correct modules, the next step is to verify that your " +"company is configured with the correct data. To do so, go to " +":menuselection:`Settings --> General Settings --> Companies`, and select " +":guilabel:`Update Info` under your company name." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:143 +msgid "" +"Enter the full :guilabel:`Address` in the resulting form, including: " +":guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| " +"(:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:146 +msgid "" +"According to the requirements of the CFDI 4.0, the name of the main company " +"contact **must** coincide with your business name registered in the |SAT|, " +"without the legal entity abbreviation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Main company contact requirements for a correct invoicing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:154 +msgid "" +"From a legal point of view, a Mexican company **must** use the local " +"currency (MXN). Therefore, Odoo does not provide features to manage an " +"alternative configuration. If you want to manage another currency, let MXN " +"be the default currency and use a :doc:`pricelist " +"<../../sales/sales/products_prices/prices/pricing>`, instead." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:159 +msgid "" +"Next, go to :menuselection:`Settings --> Accounting --> Electronic Invoicing" +" (MX) --> Fiscal Regime`, then select the regime that applies to your " +"company from the drop-down list, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Fiscal regime configuration in the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:168 +msgid "" +"If you want to test the Mexican localization, the company can be configured " +"with a real address within Mexico (including all fields), and add " +"`EKU9003173C9` as the :guilabel:`VAT` and `ESCUELA KEMPER URGATE` as the " +":guilabel:`Company Name`. For the :guilabel:`Fiscal Regime`, use " +":guilabel:`General de Ley Personas Morales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:176 +msgid "" +"To create a contact that can be invoiced, go to :menuselection:`Contacts -->" +" Create`. Then, enter the contact name, full :guilabel:`Address` including: " +":guilabel:`ZIP` code, :guilabel:`State`, :guilabel:`Country`, and |RFC| " +"(:guilabel:`VAT` number)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:181 +msgid "" +"As with your own company, all of your contacts needs to have their correct " +"business name registered in the |SAT|. This also applies to the " +":guilabel:`Fiscal Regime`, which needs to be added in the :guilabel:`MX EDI`" +" tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:188 +msgid "" +"Some additional configurations for factor type and tax objects need to be " +"added to the sales taxes in order to properly sign invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:192 +msgid "Factor type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:194 +msgid "" +"The *Factor Type* field is pre-loaded in the default taxes. If new taxes are" +" created, you need to make sure to configure this field. To do so, go to " +":menuselection:`Accounting --> Configuration --> Taxes`, then enable the " +":guilabel:`Factor Type` field in the :guilabel:`Advanced Options` tab for " +"all records, with the :guilabel:`Tax Type` set as :guilabel:`Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Factor Type Sales tax type configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:204 +msgid "" +"Mexico manages two different kinds of 0% VAT to accommodate two scenarios:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:206 +msgid "*0% VAT* set the :guilabel:`Factor Type` as :guilabel:`Tasa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:207 +msgid "*VAT Exempt* set the :guilabel:`Factor Type` as :guilabel:`Exento`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:210 +msgid "Tax object" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:212 +msgid "" +"One requirement of the CFDI 4.0 is that the resulting XML file needs (or " +"does not need) to break down the taxes of the operation. There are three " +"different possible values that are added in the XML file:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:216 +msgid "" +"`01`: Not subject to tax - this value is added automatically if your invoice" +" line doesn't contain any taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:218 +msgid "" +"`02`: Subject to tax - this is the default configuration of any invoice line" +" that contains taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:219 +msgid "" +"`03`: Subject to tax and not forced to break down - this value can be " +"triggered on-demand for certain customers to replace the value 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:222 +msgid "" +"To use the `03` value, navigate to :menuselection:`Contacts --> your " +"customer's invoice --> MX EDI tab`, and activate the :guilabel:`No Tax " +"Breakdown` checkbox." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "No Tax Breakdown option on the MX EDI tab of the customer's invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:230 +msgid "" +"The :guilabel:`No Tax Breakdown` value applies **only** to specific fiscal " +"regimes and/or taxes. Consult your accountant first to see if it is needed " +"for your business before making any modification." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:235 +msgid "Other tax configurations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:237 +msgid "" +"When registering a payment, Odoo will carry out the movement of taxes from " +"the *Cash Basis Transition Account* to the account set in the " +":guilabel:`Definition` tab. For such movement, a tax base account will be " +"used: (`Base Imponible de Impuestos en Base a Flujo de Efectivo`) in the " +"journal entry when reclassifying taxes. **Do not delete this account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:242 +msgid "" +"If you create a new tax in :menuselection:`Accounting --> Configuration --> " +"Taxes`, you need to add the correct :guilabel:`Tax Grids` for it (`IVA`, " +"`ISR` or `IEPS`). Odoo **only** supports these three groups of taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Tax accounts available for Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 +msgid "" +"To configure products, go to :menuselection:`Accounting --> Customers --> " +"Products`, then select a product to configure, or :guilabel:`Create` a new " +"one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product" +" Category` field, select the category that represents the product. The " +"process can be done manually, or through :doc:`a bulk import " +"<../../general/export_import_data>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:259 +msgid "" +"All products need to have an |SAT| code associated with them in order to " +"prevent validation errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:266 +msgid "PAC credentials" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:268 +msgid "" +"After you have processed your `Private Key (CSD) " +"<https://www.sat.gob.mx/aplicacion/16660/genera-y-descarga-tus-archivos-a-" +"traves-de-la-aplicacion- certifica>`_ with the |SAT|, you **must** register " +"directly with the :ref:`PAC <mx-requirements>` of your choice before you " +"start creating invoices from Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:273 +msgid "" +"Once you've created your account with any of these providers, go to " +":menuselection:`Settings --> Accounting --> Electronic Invoicing (MX)`. " +"Under the :guilabel:`MX PAC` section, enter the name of your |PAC| with your" +" credentials (:guilabel:`PAC username` and :guilabel:`PAC password`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Configuring PAC credentials from the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:282 +msgid "" +"If you do not have credentials, but want to test the electronic invoicing, " +"you can activate the :guilabel:`MX PAC test environment` checkbox, and " +"select :guilabel:`Solucion Factible` as the |PAC|. You do not need to add a " +"username or password for a test environment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:287 +msgid ".cer and .key certificates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:289 +msgid "" +"The `digital certificates of the company " +"<https://www.gob.mx/tramites/ficha/certificado-de-sello-digital/SAT139>`_ " +"must be uploaded within the :guilabel:`MX Certificates` section. To do so, " +"navigate to :menuselection:`Settings --> Accounting --> Electronic Invoicing" +" (MX)`. Under the :guilabel:`MX Certificates` section, select :guilabel:`Add" +" a line`, and a window will open. Click :guilabel:`Create`, and from there, " +"upload your digital :guilabel:`Certificate` (:file:`.cer` file), your " +":guilabel:`Certificate Key` (:file:`.key` file), and your " +":guilabel:`Certificate Password`. To finish, click on :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Certificate and key upload inputs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:303 +msgid "" +"If you still do not have one of the contracted |PAC|\\s and you want to test" +" electronic invoicing, you can use the following |SAT| test certificates:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:306 +msgid ":download:`Certificate <mexico/certificate.cer>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:307 +msgid ":download:`Certificate Key <mexico/certificate.key>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:308 +msgid "**Password**: ``12345678a``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:316 +msgid "" +"The invoicing process in Odoo is based on `Annex 20 " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_ version" +" 4.0 of electronic invoicing of the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:323 +msgid "" +"To start invoicing from Odoo, a customer invoice must be created using the " +":doc:`standard invoicing flow <../accounting/customer_invoices>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:326 +msgid "" +"While the document is in draft mode, changes can be made to it (the correct " +":guilabel:`Payment Way` or :guilabel:`Usage` that the customer might require" +" can be added, for example.)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:329 +msgid "" +"After you :guilabel:`Confirm` the customer invoice, a blue message appears " +"stating: :guilabel:`The invoice will be processed asynchronously by the " +"following E-invoicing service: CFDI (4.0)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:332 +msgid "" +"Pressing the :guilabel:`Process Now` button sends the document to the " +"government so it can be signed. After receiving the signed document back " +"from the government, the :guilabel:`Fiscal Folio` field appears on the " +"document, and the XML file is attached in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:337 +msgid "" +"If you click :guilabel:`Retry` in the :guilabel:`SAT status` field on the " +"invoice, you can confirm if the XML file is valid in the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:340 +msgid "" +"If you are in a testing environment, you will always receive the message " +":guilabel:`Not Found`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:342 +msgid "" +"To send the signed invoice to your client by mail, you can send both the XML" +" and PDF files together, directly from Odoo, by clicking the :guilabel:`Send" +" & Print` button. You can also download the PDF file to your computer, by " +"clicking the :guilabel:`Print` button, and selecting the desired print " +"option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:350 +msgid "" +"While an invoice is a document type \"I\" (Ingreso), a credit note is a " +"document type \"E\" (Egreso)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:352 +msgid "" +"The only addition to the :doc:`standard flow for credit notes " +"<../accounting/customer_invoices/credit_notes>` is that, as a requirement of" +" the |SAT|, there has to be a relation between a credit note and an invoice " +"through the fiscal folio." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:356 +msgid "" +"Because of this requirement, the field :guilabel:`CFDI Origin` adds this " +"relation with a `01|`, followed by the fiscal folio of the original invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example CFDI Origin number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:364 +msgid "" +"For the :guilabel:`CFDI Origin` field to be automatically added, use the " +":guilabel:`Add Credit Note` button from the invoice, instead of creating it " +"manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:368 +msgid "Payment complements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:371 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:373 +msgid "" +"One addition of the Mexican localization is the :guilabel:`Payment Policy` " +"field . `According to the SAT documentation " +"<https://www.sat.gob.mx/consultas/92764/comprobante-de-recepcion-de-" +"pagos>`_, there may be 2 types of payments:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:377 +msgid "`PUE` (Pago en una Sola Exhibición/Payment in a Single Exhibition)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:378 +msgid "" +"`PPD` (Pago en Parcialidades o Diferido/Payment in Installements or " +"Deferred)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:381 +msgid "" +":doc:`../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:383 +msgid "" +"The difference lies in the *Due Date* or *Payment Terms* of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:385 +msgid "" +"To configure |PUE| invoices, navigatge to :menuselection:`Accounting --> " +"Customers --> Invoices`, and either select an invoice :guilabel:`Due Date` " +"within the same month, or choose a payment term that does not imply changing" +" the due month (immediate payment, 15 days, 21 days, all falling within the " +"current month)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example of an invoice with the PUE requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:395 +msgid "" +"Some :guilabel:`Payment Terms` are already installed by default, and can be " +"managed from :menuselection:`Accounting --> Configuration --> Payment " +"Terms`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:398 +msgid "" +"To configure |PPD| invoices, navigate to :menuselection:`Accounting --> " +"Customers --> Invoices`, and select an invoice with a :guilabel:`Due Date` " +"after the first day of the following month. This also applies if your " +":guilabel:`Payment Term` is due in the following month." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Example of an invoice with the PPD requirements." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:407 +msgid "" +"Because the |PPD| policy implies that an invoice is not going to get paid at" +" the moment, the correct :guilabel:`Payment Way` for the |PPD| invoices is " +":guilabel:`99 - Por Definir` (To define)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:412 +msgid "Payment flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:414 +msgid "" +"In both cases, the payment process in Odoo :doc:`is the same " +"<../accounting/customer_invoices>`, the main difference being payments " +"related to |PPD| invoices trigger the creation of a document type \"P\" " +"(Pago)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:418 +msgid "" +"If a payment is related to a |PUE| invoice, it can be registered with the " +"wizard, and be associated with the corresponding invoice. To do so, navigate" +" to :menuselection:`Accounting --> Customers --> Invoices`, and select an " +"invoice. Then, click the :guilabel:`Register Payment` button. The invoice " +"status changes to :guilabel:`In Payment`, since the payment is effectively " +"validated when it is bank reconciled." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:425 +msgid ":doc:`../accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:427 +msgid "" +"While this process is the same for PPD invoices, the addition of the " +"creating an :doc:`electronic document " +"<../accounting/customer_invoices/electronic_invoicing>` means some " +"additional requirements are needed to correctly send the document to the " +"|SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:431 +msgid "" +"From an invoice, you need to confirm the specific :guilabel:`Payment Way` " +"where you received the payment. Because of this, the :guilabel:`Payment Way`" +" field **cannot** be set as `99 - Por Definir (To Define)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:435 +msgid "" +"If you are going to add a bank account number in the :guilabel:`Accounting` " +"tab of a customer's contact card, it must have a valid account number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:439 +msgid "" +"The exact configurations are in the `Anexo 20 of the SAT " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_. " +"Usually, the :guilabel:`Bank Account` needs to be 10 or 18 digits for " +"transfers, 16 for credit or debit cards." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:443 +msgid "" +"If a payment is related to a signed invoice with the :guilabel:`Payment " +"Policy` `PPD`, Odoo generates the corresponding payment complement " +"automatically, once you click :guilabel:`Process Now`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI (4.0) E-invoicing service process payment now message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:452 +msgid "" +"A payment in MXN **cannot** be used to pay multiple invoices in USD. " +"Instead, the payment should be separated into multiple payments, using the " +":guilabel:`Register Payment` button on the corresponding invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:457 +msgid "Invoice cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:459 +msgid "" +"It is possible to cancel the EDI documents sent to the |SAT|. According to " +"the `Reforma Fiscal 2022 <https://www.sat.gob.mx/consultas/91447/nuevo-" +"esquema-de-cancelacion>`_, since January 1st, 2022, there are two " +"requirements for this:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:463 +msgid "" +"With all cancellation requests, you **must** specify a *cancellation " +"reason*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:464 +msgid "" +"After 24 hours have passed since the creation of the invoice, the client " +"**must** be asked to accept the cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:467 +msgid "" +"There are four different cancellation reasons. In Odoo, you can cancel " +"invoices with the reasons *01 Invoices sent with errors with a relation*, " +"and *02 Invoices sent with errors without a relation*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:470 +msgid "" +"The following sections break down the process of canceling invoices for each" +" cancellation reason in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:474 +msgid "" +"Odoo has certain limitations to canceling invoices in the |SAT|: The reasons" +" 03 and 04 (*Operation did not take place* and *Nominative transactions " +"related to a global invoice*, respectively) are not currently supported by " +"Odoo. For this, you need to cancel the invoice directly in the |SAT|, and " +"press :guilabel:`Retry` in the :guilabel:`SAT Status field`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:480 +msgid "01 - invoices sent with errors with a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:482 +msgid "" +"This cancellation reason must be used when a new invoice needs to substitute" +" the original one, due to an error in any field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:485 +msgid "" +"Begin by navigating to :menuselection:`Accounting --> Customers --> " +"Invoices`, and select the old invoice. Copy the :guilabel:`Fiscal Folio` " +"from the old invoice. Then, navigate to the new invoice, and in the " +":guilabel:`CFDI Origin` field, add the value `04|` and paste the " +":guilabel:`Fiscal Folio` of the old invoice after the value. Finally, sign " +"the new document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:490 +msgid "" +"Next, navigate back to the old invoice, and notice the " +":guilabel:`Substituted By` field is now available. Click the " +":guilabel:`Request EDI Cancellation` button on the old invoice, and then " +"click :guilabel:`Process Now` in the blue section that appears. The invoice " +"status changes to :guilabel:`Canceled`, and a confirmation is logged in the " +"chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:495 +msgid "" +"Now, the invoice should be canceled in the |SAT| as well. You can confirm " +"this was done correctly, by pressing :guilabel:`Retry` in the |SAT| status " +"field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:498 +msgid "" +"If the document was canceled more than 24 hours after its creation, you may " +"need to ask the client to accept the cancellation in their “Buzón " +"Tributario” directly from the `SAT website <https://www.sat.gob.mx/home>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:503 +msgid "" +"The `04|` is only a code that helps Odoo to perform this process. It has no " +"relation to the method 04 reason for cancellation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Old invoice with CFDI Origin." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "" +"Invoice with the Substituted By field referencing the CFDI Origin invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:515 +msgid "02 - invoices sent with errors without a relation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:517 +msgid "" +"This cancellation reason has to be used when an invoice was sent with an " +"error in any field, and does not need to be replaced by another one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:520 +msgid "" +"For this case, navigate to :menuselection:`Accounting --> Customers --> " +"Invoices`, and select the old invoice. From here, the only requirement is to" +" click the :guilabel:`Request EDI Cancellation` button, and then click the " +":guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:524 +msgid "" +"Because the field :guilabel:`Substituted By` does not appear when using this" +" cancellation reason, the |SAT| should automatically detect that the " +"cancellation reason is 02." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:528 +msgid "Payment cancellations" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:530 +msgid "" +"It is also possible to cancel *Payment Complements*. For this, go to the " +"payment, via :menuselection:`Accounting --> Customers --> Payments`, and " +"select :guilabel:`Request EDI Cancellation`. As with invoices, a blue button" +" will appear. Click :guilabel:`Process now`, and the document will be sent " +"to the |SAT|. After a few seconds, you can click :guilabel:`Retry` to " +"confirm the current |SAT| status." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:536 +msgid "Finally, the payment status is moved to :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:539 +msgid "" +"Just like invoices, when you create a new *Payment Complement*, you can add " +"the relation of the original document, by adding a `04|` plus the fiscal " +"folio in the :guilabel:`CFDI Origin` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:543 +msgid "Invoicing special use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:546 +msgid "CFDI to public" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:548 +msgid "" +"If the customer you are selling goods or services to does not require an " +"invoice, a *CFDI to Public* has to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:551 +msgid "" +"If you use the :guilabel:`Customer` name `PUBLICO EN GENERAL`, an error will" +" be triggered. This is a main change in the CFDI 4.0 that requires invoices " +"with that specific name to need additional fields, which Odoo does not " +"currently support. So, for a *CFDI to Public* to be created, you need to add" +" any name to your customer that is **not** `PUBLICO EN GENERAL`. (For " +"example: `CLIENTE FINAL`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:556 +msgid "" +"In addition to this, it is required that the :guilabel:`ZIP` code of your " +"company is added, the generic |RFC| is set as `XAXX010101000`, and the " +":guilabel:`Fiscal Regime` of your customer must be set as: `Sin obligaciones" +" fiscales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "CFDI to Public Customer field configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:567 +msgid "" +"The main currency in Mexico is MXN. While this is mandatory for all Mexican " +"companies, it is possible to send and receive invoices (and payments) in " +"different currencies. To enable the use of :doc:`multicurrency " +"<../accounting/get_started/multi_currency>`, navigate to the " +":menuselection:`Accounting --> Settings --> Currencies`, and set " +":guilabel:`Mexican Bank` as the :guilabel:`Service` in the " +":guilabel:`Automatic Currency Rates` section. Then, set the " +":guilabel:`Interval` field to the frequency you wish to update the exchange " +"rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:574 +msgid "" +"This way, the XML file of the document will have the correct exchange rate, " +"and the total amount, in both the foreign currency and in MXN." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:577 +msgid "" +"It is highly recommended to use :doc:`a bank account for each currency " +"<../accounting/bank/foreign_currency>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:581 +msgid "" +"The only currencies that automatically update their exchange rate daily are:" +" USD, EUR, GBP, and JPY." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Multi-currency configuration in the Accounting settings." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:589 +msgid "Down payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:591 +msgid "" +"There can be cases where you receive a payment in advance from a customer " +"that needs to be applied to an invoice later. In order to do this in Odoo, " +"it is required to properly link invoices to each other with the " +":guilabel:`CFDI Origin` field. To do so, it is necessary to have the " +":doc:`Sales <../../sales>` app installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:597 +msgid "" +"`The official documentation for registration of down payments in Mexico " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/documentos/Caso_uso_Anticipo.pdf>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:600 +msgid "" +"First, navigate to the :menuselection:`Sales` app to create a product " +"`Anticipo` and configure it. The :guilabel:`Product Type` must be " +":guilabel:`Service`, and use the :guilabel:`UNSPSC Category` must be: " +"`84111506 Servicios de facturación`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:604 +msgid "" +"Then, go to :menuselection:`Sales --> Settings --> Invoicing --> Down " +"Payments`, and add the *Anticipo* product as the default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:607 +msgid "" +"Create a sales order with the total amount, and create a down payment " +"(either using a percentage or fixed amount). Then, sign the document, and " +":guilabel:`Register the Payment`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:610 +msgid "" +"When the time comes for the customer to get the final invoice, create it " +"again from the same sales order. In the :guilabel:`Create Invoices` wizard, " +"select :guilabel:`Regular Invoice`, and uncheck :guilabel:`Deduct down " +"payments`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:614 +msgid "" +"Then, copy the :guilabel:`Fiscal Folio` from the first invoice, and paste it" +" into the :guilabel:`CDFI Origin` of the second invoice, adding the prefix " +"`07|` before the value. Then, sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:618 +msgid "" +"After this, create a credit note for the first invoice. Copy the " +":guilabel:`Fiscal Folio` from the second invoice, and paste it in the " +":guilabel:`CFDI Origin` of the credit note, adding the prefix `07|`. Then, " +"sign the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:622 +msgid "" +"With this, all electronic documents are linked to each other. The final step" +" is to fully pay the new invoice. At the bottom of the new invoice, you can " +"find the credit note in the :guilabel:`Outstanding credits` - add it as " +"payment. Finally, register the remaining amount with the :guilabel:`Register" +" Payment` wizard." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:628 +msgid "External trade" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:630 +msgid "" +"The external trade is a complement to a regular invoice that adds certain " +"values in both the XML and PDF, to invoices with a foreign customer " +"according to `SAT regulations " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/complemento_comercio_exterior.htm>`_," +" such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:634 +msgid "The specific address of the receiver and the sender" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:635 +msgid "" +"The addition of a :guilabel:`Tariff Fraction` that identifies the type of " +"product" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:636 +msgid "" +"The correct :guilabel:`Incoterm` (International Commercial Terms), among " +"others (*certificate of origin* and *special units of measure*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:639 +msgid "" +"This allows the correct identification of exporters and importers, in " +"addition to expanding the description of the merchandise sold." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:642 +msgid "" +"Since January 1, 2018, external trade is a requirement for taxpayers, who " +"carry export operations of type A1. While the current CFDI is 4.0, the " +"external trade is currently on version 1.1" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:645 +msgid "" +"In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended` " +"and :guilabel:`l10n_mx_edi_extended_40` have to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:649 +msgid "" +"Before installing, make sure your business needs to use this feature. " +"Consult your accountant first, if needed, before installing any modules." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:658 +msgid "" +"To configure your company contact for external trade, navigate to " +":menuselection:`Accounting --> Customers --> Customers`, and select your " +":guilabel:`Company`. While the CFDI 4.0 requirements ask you to add a valid " +":guilabel:`ZIP` code in your contact, the external trade complement adds the" +" requirement that your :guilabel:`City` and the :guilabel:`State` must also " +"be valid. All three fields must coincide with the `Official SAT Catalog " +"<sat-catalog_>`_, or you will receive an error." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:665 +msgid "" +"Add the :guilabel:`City` and :guilabel:`State` in the company's *contact*, " +"not in the company itself. You can find your company's contact in " +":menuselection:`Accounting --> Customers --> Customers`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:669 +msgid "" +"The fields :guilabel:`Locality` and :guilabel:`Colony Code` are optional and" +" can be added in the company directly in :menuselection:`Settings --> " +"General Settings --> Companies`. These two fields have to coincide with the " +"data in the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Optional external trade company fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:677 +msgid "" +"To configure the contact data for a foreign receiving client, navigate to " +":menuselection:`Accounting --> Customers --> Customers`, and select the " +"foreign client's contact. The contact must have the following fields " +"completed to avoid errors:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:681 +msgid "" +"The entire company :guilabel:`Address`, including a valid :guilabel:`ZIP` " +"code and the foreign :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:683 +msgid "" +"The format of the foreign :guilabel:`VAT` (tax identification number, for " +"example: Colombia `123456789-1`)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:685 +msgid "" +"In the :guilabel:`MX EDI` tab, you need to address if the customer receives " +"goods for a period of time temporarily (:guilabel:`Temporary`) or " +"permanently (:guilabel:`Definitive`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:689 +msgid "" +"If the new contact was created by duplicating another existing contact from " +"Mexico, make sure to delete any carried over information from the " +":guilabel:`Fiscal Regime` field. In addition, do not enable the " +":guilabel:`No Tax Breakdown` option. Selecting this option hides mandatory " +"fields that are required for external trade contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Required external trade customer fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:699 +msgid "" +"In the resulting XML and PDF files, the :guilabel:`VAT` is automatically " +"replaced by the generic VAT for abroad transactions: `XEXX010101000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:705 +msgid "" +"All products involved with external trade have four fields that are " +"required, two of them exclusive to external trade." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:708 +msgid "" +"The :guilabel:`Internal Reference` of the product is in the " +":guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:709 +msgid "The :guilabel:`Weight` of the product must be more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:710 +msgid "" +"The `correct <https://www.ventanillaunica.gob.mx/vucem/Clasificador.html>`_" +" :guilabel:`Tariff Fraction` of the product in the :guilabel:`Accounting` " +"tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:712 +msgid "" +"The :guilabel:`UMT Aduana` corresponds to the :guilabel:`Tariff Fraction`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Required external trade product fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:719 +msgid "" +"If the UoM code of the :guilabel:`Tariff Fraction` is `01`, the correct " +":guilabel:`UMT Aduana` is `kg`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:721 +msgid "" +"If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct " +":guilabel:`UMT Aduana` is `Units`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 +msgid "Invoicing flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:727 +msgid "" +"Before creating an invoice, it is important to take into account that " +"external trade invoices require to convert the amounts of your product into " +"USD. Therefore, :doc:`multicurrency " +"<../accounting/get_started/multi_currency>` **must** be enabled and *USD* " +"**must** be activated in the :guilabel:`Currencies` section. The correct " +":guilabel:`Service` to run is :guilabel:`Mexican Bank`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:733 +msgid "" +"Then, with the correct exchange rate set up in :menuselection:`Accounting " +"--> Settings --> Currency`, the only fields left are :guilabel:`Incoterm` " +"and the optional :guilabel:`Certificate Source` in the :guilabel:`Other " +"Info` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "External trade Other Info tab of a product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:741 +msgid "" +"Finally, sign the invoice with the same process as a regular invoice, and " +"click the :guilabel:`Process Now` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:747 +msgid "" +"A `Carta Porte <https://www.sat.gob.mx/consultas/68823/complemento-carta-" +"porte->`_ is a bill of lading: a document that states the type, quantity, " +"and destination of goods being carried." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:750 +msgid "" +"On December 1st, 2021, version 2.0 of this CFDI was implemented for all " +"transportation providers, intermediaries, and owners of goods. Odoo is able " +"to generate a document type \"T\" (Traslado), which, unlike other documents," +" is created in a delivery order instead of an invoice or payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:754 +msgid "" +"Odoo can create XML and PDF files with (or without) ground transport, and " +"can process materials that are treated as *Dangerous Hazards*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:757 +msgid "" +"In order to use this feature, the modules :guilabel:`l10n_mx_edi_extended`, " +":guilabel:`l10n_mx_edi_extended_40`, :guilabel:`l10n_mx_edi_stock` and " +":guilabel:`l10n_mx_edi_stock_40` have to be installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:761 +msgid "" +"In addition to this, it is necessary to have the :doc:`Inventory " +"<../../inventory_and_mrp/inventory>` and :doc:`Sales <../../sales/sales>` " +"apps installed, as well." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:765 +msgid "" +"Odoo does not support Carta Porte type document type \"I\" (Ingreso), air, " +"or marine transport. Consult your accountant first if this feature is needed" +" before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:771 +msgid "Odoo manages two different types of CFDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:773 +msgid "" +"**No Federal Highways**: Is used when the *Distance to Destination* is `less" +" than 30 KM " +"<http://omawww.sat.gob.mx/cartaporte/Paginas/documentos/PreguntasFrecuentes_Autotransporte.pdf>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:775 +msgid "" +"**Federal Transport**: Is used when the *Distance to Destination* exceeds 30" +" KM." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:777 +msgid "" +"Other than the standard requirements of regular invoicing (The |RFC| of the " +"customer, the UNSPSC code, etc.), if you are using *No Federal Highways*, no" +" external configuration is needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:780 +msgid "" +"For *Federal Transport*, several configurations have to be added to " +"contacts, vehicle setups, and products. Those configurations are added to " +"the XML and PDF files." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:784 +msgid "Contacts and vehicles" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:786 +msgid "" +"Like the external trade feature, the :guilabel:`Address` in both the company" +" and the final customer must be complete. The :guilabel:`ZIP` code, " +":guilabel:`City`, and :guilabel:`State` must coincide with the `Official SAT" +" Catalog for Carta Porte <sat-catalog_>_`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:791 +msgid "The field, :guilabel:`Locality`, is optional for both addresses." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide contact configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:798 +msgid "" +"The origin address used for the delivery guide is set in " +":menuselection:`Inventory --> Configuration --> Warehouses Management --> " +"Warehouses`. While this is set as the company address by default, you can " +"change it according to your correct warehouse address." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:802 +msgid "" +"Another addition to this feature is the :guilabel:`Vehicle Setups` menu " +"found in :menuselection:`Inventory --> Settings --> Mexico`. This menu lets " +"you add all the information related to the vehicle used for the delivery " +"order." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:806 +msgid "All fields are mandatory to create a correct delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:809 +msgid "" +"The fields, :guilabel:`Vehicle Plate Number` and :guilabel:`Number Plate`, " +"must contain between 5 to 7 characters." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:812 +msgid "" +"In the :guilabel:`Intermediaries` section, you must add the operator of the " +"vehicle. The only mandatory fields for this contact are the :guilabel:`VAT` " +"and :guilabel:`Operator Licence`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide vehicle configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:822 +msgid "" +"Similar to regular invoicing, all products must have a :guilabel:`UNSPSC " +"category`. In addition to this, there are two extra configurations for " +"products involved in delivery guides:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:825 +msgid "" +"The :guilabel:`Product Type` must be set as :guilabel:`Storable Product` for" +" stock movements to be created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:827 +msgid "" +"In the :guilabel:`Inventory` tab, the field :guilabel:`Weight` should have " +"more than `0`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:830 +msgid "" +"Creating a delivery guide of a product with the value `0` will trigger an " +"error. As the :guilabel:`Weight` has been already stored in the delivery " +"order, it is needed to return the products, and create the delivery order " +"(and delivery guide) again with the correct amounts." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide product configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:839 +msgid "Sales and inventory flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:841 +msgid "" +"To create a delivery guide, first, you need to create and confirm a sales " +"order from :menuselection:`Sales --> Sales Order`. This generates a " +":guilabel:`Delivery` smart button. Click it, and :guilabel:`Validate` the " +"transfer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:845 +msgid "" +"After the status is set to :guilabel:`Done`, you can edit the transfer, and " +"select the :guilabel:`Transport Type` (either :guilabel:`No Federal " +"Highways` or :guilabel:`Federal Transport`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:849 +msgid "" +"If your delivery guide has the type :guilabel:`No Federal Highways`, you can" +" save the transfer, and then click :guilabel:`Generate Delivery Guide`. The " +"resulting XML can be found in the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:853 +msgid "" +"Other than the :guilabel:`UNSPSC` in all products, delivery guides that use " +":guilabel:`No Federal Highways` do not require any special configuration to " +"be sent to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:856 +msgid "" +"If your delivery guide has the type, :guilabel:`Federal Transport`, the tab " +":guilabel:`MX EDI` appears. There, enter a value in :guilabel:`Distance to " +"Destination (KM)` bigger than `0`, and select the :guilabel:`Vehicle Setup` " +"used for this delivery." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide MX EDI tab configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:865 +msgid "Dangerous hazards" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:867 +msgid "" +"Certain values in the :guilabel:`UNSPSC Category` are considered in the " +"`official SAT catalog " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/complemento_carta_porte.htm>`_" +" as *dangerous hazards*. These categories need additional considerations " +"when creating a delivery guide with :guilabel:`Federal Transport`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:872 +msgid "" +"First, select your product from :menuselection:`Inventory --> Products --> " +"Products`. Then, in the :guilabel:`Accounting` tab, the fields " +":guilabel:`Hazardous Material Designation Code (MX)` and " +":guilabel:`Hazardous Packaging (MX)` must be filled with the correct code " +"from the |SAT| catalog." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery guide hazardous material product required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:880 +msgid "" +"In :menuselection:`Inventory --> Settings --> Mexico --> Vehicle Setup`, the" +" data from the :guilabel:`Environment Insurer` and :guilabel:`Environment " +"Insurance Policy` has to be filed, as well. After this, continue with the " +"regular process to create a delivery guide." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Delivery Guide environment insurer required fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:889 +msgid "Customs numbers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:891 +msgid "" +"A *customs declaration* (Pedimento Aduanero) is a fiscal document that " +"certifies that all contributions to the fiscal entity (the |SAT|) has been " +"paid for, including the import/export of goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:895 +msgid "" +"According to the `Annex 20 " +"<http://omawww.sat.gob.mx/tramitesyservicios/Paginas/anexo_20.htm>`_ of CFDI" +" 4.0, in documents where the invoiced goods come from a first-hand import " +"operation, the field, :guilabel:`Customs Number`, needs to be added to all " +"lines of products involved with the operation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:899 +msgid "" +"To do so, the module :guilabel:`l10n_mx_edi_landing` must be installed, in " +"addition to the :doc:`Inventory <../../inventory_and_mrp/inventory>`, " +":doc:`Purchase <../../inventory_and_mrp/purchase>` and :doc:`Sales " +"<../../sales/sales>` apps." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:904 +msgid "" +"Do not confuse this feature with external trade. The customs numbers are " +"directly related to importing goods, while the external trade complement is " +"related to exporting. Consult your accountant first if this feature is " +"needed before doing any modifications." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:911 +msgid "" +"In order to track the correct customs number for a specific invoice, Odoo " +"uses :doc:`landed costs " +"<../../inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs>`." +" Go to :menuselection:`Inventory --> Configuration --> Settings --> " +"Valuation`. Make sure that :guilabel:`Landed Costs` is activated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:916 +msgid "" +"Begin by creating a *service*-type product called, `Pedimento`. In the " +":guilabel:`Purchase` tab, activate :guilabel:`Is a Landed Cost`, and select " +"a :guilabel:`Default Split Method`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:919 +msgid "" +"Then, configure the *storable products* that hold the customs numbers. To do" +" so, create the storable products, and make sure the :guilabel:`Product " +"Category` has the following configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:922 +msgid "" +":guilabel:`Costing Method`: Either :guilabel:`FIFO` or :guilabel:`AVCO`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:923 +msgid ":guilabel:`Inventory Valuation`: :guilabel:`Automated`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:924 +msgid ":guilabel:`Stock Valuation Account`: :guilabel:`115.01.01 Inventario`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:925 +msgid ":guilabel:`Stock Journal`: :guilabel:`Inventory Valuation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:926 +msgid "" +":guilabel:`Stock Input Account`: :guilabel:`115.05.01 Mercancías en " +"tránsito`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:927 +msgid "" +":guilabel:`Stock Output Account`: :guilabel:`115.05.01 Mercancías en " +"tránsito`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Storable products general configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Storable product category configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:938 +msgid "Purchase and sales flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:940 +msgid "" +"After you configure your product, follow the standard :doc:`purchase flow " +"<../../inventory_and_mrp/purchase>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:943 +msgid "" +"Create a purchase order from :menuselection:`Purchase --> Orders --> " +"Purchase Order`. Then, confirm the order to display a :guilabel:`Receipt` " +"smart button. Click on the :guilabel:`Receipt` smart button to " +":guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:947 +msgid "" +"Go to :menuselection:`Inventory --> Operations --> Landed Costs`, and create" +" a new record. Add the transfer that you just created, and both: the product" +" `Pedimento` and :guilabel:`Customs number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:950 +msgid "" +"Optionally, you can add a cost amount. After this, validate the landed cost." +" Once :guilabel:`Posted`, all products related to that receipt have the " +"customs number assigned." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:954 +msgid "" +"You can only add the *Pedimentos* number **once**, so be careful when " +"associating the correct number with the transfer(s)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Customs number on a landed costs Inventory record." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:961 +msgid "" +"Now, create a sales order, and confirm it. This should trigger a " +":guilabel:`Delivery` smart button. Validate it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:964 +msgid "" +"Finally, create an invoice from the sales order, and confirm it. The invoice" +" line related to your product has a customs number in it. This number should" +" match the customs number added in the *Landed Costs* record you created " +"earlier." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Customs number on confirmed sales order product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:973 +msgid "Electronic accounting" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:975 +msgid "" +"For Mexico, `Electronic Accounting " +"<https://www.sat.gob.mx/aplicacion/42150/envia-tu-contabilidad-" +"electronica>`_ refers to the obligation to keep accounting records and " +"entries through electronic means, and to enter accounting information on a " +"monthly basis, through the |SAT| website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:980 +msgid "It consists of three main XML files:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:982 +msgid "" +"The updated list of the chart of accounts that you are currently using." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:983 +msgid "" +"A monthly trial balance, plus a closing entry report, also known as: *Trial " +"Balance Month 13*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:984 +msgid "" +"Either optional, or for a compulsory audit, an export of the journal entries" +" in your general ledger." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:987 +msgid "" +"The resulting XML files follow the requirements of the `Anexo Técnico de " +"Contabilidad Electrónica 1.3 " +"<https://www.gob.mx/cms/uploads/attachment/file/151135/Anexo24_05012015.pdf>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:990 +msgid "" +"In addition to this, you can generate the `DIOT " +"<https://www.sat.gob.mx/declaracion/74295/presenta-tu-declaracion-" +"informativa-de-operaciones-con- terceros-(diot)->`_: A report of vendor's " +"journal entries that involve IVA taxes that can be exported in a " +":file:`.txt` file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:995 +msgid "" +"In order to use these reports, the modules :guilabel:`l10n_mx_reports`, " +":guilabel:`l10n_mx_reports_closing`, :guilabel:`l10n_mx_xml_polizas` and " +":guilabel:`l10n_mx_xml_polizas_edi` have to be installed, as well as the " +":doc:`Accounting <../accounting/get_started>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1000 +msgid "" +"You can find the *Chart of accounts*, *Trial Balance Month 13*, and *DIOT* " +"reports in :menuselection:`Accounting --> Reporting --> Mexico`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1004 +msgid "" +"The specific characteristics and obligations of the reports that you send " +"might change according to your fiscal regime. Always contact your accountant" +" before sending any documents to the government." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1013 +msgid "" +"The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` " +"in México follows a specific pattern based on |SAT|'s' `Código agrupador de " +"cuentas " +"<http://omawww.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/codigo_agrupador.pdf>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1017 +msgid "" +"You can create any account, as long as it respects |SAT|'s encoding group: " +"the pattern is `NNN.YY.ZZ` or `NNN.YY.ZZZ`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1021 +msgid "Some examples are `102.01.99` or `401.01.001`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1023 +msgid "" +"When a new account is created in :menuselection:`Accounting --> " +"Configuration --> Chart of Accounts`, with the |SAT| encoding group pattern," +" the correct grouping code appears in :guilabel:`Tags`, and your account " +"appears in the *COA* report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1027 +msgid "" +"Once you create all your accounts, make sure the correct :guilabel:`Tags` " +"are added." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1030 +msgid "" +"You cannot use any pattern that ends a section with a 0 (such as " +"`100.01.01`, `301.00.003` or `604.77.00`). This triggers errors in the " +"report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1033 +msgid "" +"Once everything is set up, you can go to :menuselection:`Accounting --> " +"Reporting --> Mexico --> COA`, and click the :guilabel:`SAT (XML)` button to" +" generate an XML file containing all of your accounts, which will be ready " +"to upload to the |SAT| website." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1040 +msgid "" +"The trial balance reports the initial balance, credit, and total balance of " +"your accounts, provided that you added their correct :ref:`encoding group " +"<l10n_mx/chart-of-accounts>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1043 +msgid "" +"This report can be generated monthly, and a corresponding XML file is " +"created, if you go to :menuselection:`Accounting --> Reporting --> Mexico " +"--> Trial Balance`, and click the :guilabel:`SAT (XML)` button. Select the " +"month you want to download beforehand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial balance report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1052 +msgid "Odoo does not generate the *Balanza de Comprobación Complementaria*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1054 +msgid "" +"An additional report is the *Month 13*: a closing balance sheet that shows " +"any adjustments or movements made in the accounting to close the year." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1057 +msgid "" +"To generate this XML document, navigate to :menuselection:`Accounting --> " +"Accounting --> Miscellaneous --> Journal Entries`, and create a new " +"document. Here, add all amounts to modify, and balance the debit and/or " +"credit of each one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1061 +msgid "" +"After this is done, click :guilabel:`Mark as Closing Entry`, and the report " +"found in :menuselection:`Accounting --> Reporting --> Mexico --> Trial " +"Balance Month 13`, contains the total amount of the year, plus all the " +"additions of the journal entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1065 +msgid "" +"The XML file is generated by pressing the :guilabel:`SAT (XML)` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial Balance Month 13 setup." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "Trial Balance Month 13 report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1078 +msgid "" +"By law, all transactions in Mexico must be recorded digitally. Since Odoo " +"automatically creates all the underlying journal entries of your invoicing " +"and payments, you can export your journal entries to comply with |SAT|'s " +"audits and/or tax refunds." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1083 +msgid "" +"You can filter by period, or by journal, according to your current needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1085 +msgid "" +"To create the XML, go to :menuselection:`Accounting --> Reporting --> Audit " +"Reports --> General Ledger`, and click :guilabel:`XML (Polizas)`. Here, you " +"can select between four types of :guilabel:`Export` types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1089 +msgid ":guilabel:`Tax audit`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1090 +msgid ":guilabel:`Audit certification`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1091 +msgid ":guilabel:`Return of goods`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1092 +msgid ":guilabel:`Compensation`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1094 +msgid "" +"For :guilabel:`Tax audit`, or :guilabel:`Audit certification`, you need to " +"write the :guilabel:`Order Number` provided by the |SAT|. For " +":guilabel:`Return of goods`, or :guilabel:`Compensation`, you need to write " +"your :guilabel:`Process Number`, also provided by the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1100 +msgid "" +"If you want to see this report without sending it, use `ABC6987654/99` for " +":guilabel:`Order Number` and `AB123451234512` for :guilabel:`Process " +"Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1104 +msgid "DIOT report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1106 +msgid "" +"The DIOT (Declaración Informativa de Operaciones con Terceros / *Informative" +" Declaration of Operations with Third Parties*) is an additional obligation " +"with the |SAT|, where the current status of creditable and non-creditable " +"payments, withholdings, and refunds of VAT from your vendor bills, are " +"provided to the |SAT|." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1111 +msgid "" +"Unlike other reports, the |DIOT| is uploaded to a software provided by the " +"|SAT| that contains the A-29 form. In Odoo, you can download the records of " +"your transactions as a :file:`.txt` file that can be uploaded to the form, " +"avoiding direct capture of this data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1115 +msgid "" +"The transactions file contains the total amount of your payments registered " +"in vendor bills, broken down into the corresponding types of IVA. The " +":guilabel:`VAT` and :guilabel:`Country` is mandatory for all vendors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1119 +msgid "" +"To get the |DIOT| report, go to :menuselection:`Accounting --> Reports --> " +"Mexico --> Transactions with third parties [DIOT]`. Select the month that " +"suits you, and click :guilabel:`DIOT (TXT)` to download the :file:`.txt` " +"file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "A Vendor Bill that is In Payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst-1 +msgid "DIOT (TXT) download button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:1132 +msgid "" +"You need to fill the field, :guilabel:`L10N Mx Type of Operation`, in the " +":guilabel:`Accounting` tab of each one of your vendors to prevent validation" +" errors. Make sure that your foreign customers have their country set up for" +" :guilabel:`L10N Mx Nationality` to appear automatically." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:0 +msgid "DIOT information on a vendor contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:3 +msgid "Netherlands" +msgstr "ประเทศเนเธอร์แลนด์" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:6 +msgid "XAF Export" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:8 +msgid "" +"With the Dutch accounting localization installed, you will be able to export" +" all your accounting entries in XAF format. For this, you have to go in " +":menuselection:`Accounting --> Reporting --> General Ledger`, you define the" +" entries you want to export using the filters (period, journals, ...) and " +"then you click on the button **EXPORT (XAF)**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:15 +msgid "Dutch Accounting Reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:17 +msgid "" +"If you install the Dutch accounting localization, you will have access to " +"some reports that are specific to the Netherlands such as :" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:21 +msgid "Tax Report (Aangifte omzetbelasting)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/netherlands.rst:22 +msgid "Intrastat Report (ICP)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:3 +msgid "Peru" +msgstr "ประเทศเปรู" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:8 +msgid "" +"The Peruvian localization has been improved and extended, in this version " +"the next modules are available:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:11 +msgid "" +"**l10n_pe**: Adds accounting features for the Peruvian localization, which " +"represent the minimal configuration required for a company to operate in " +"Peru and under the SUNAT regulations and guidelines. The main elements " +"included in this module are: Chart of account, taxes, document types." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:16 +msgid "" +"**l10n_pe_edi**: includes all technical and functional requirements to " +"generate and validate Electronic Invoice, based on the SUNAT specification " +"to create and process valid electronic documents, for more technical detail " +"you can access the `SUNAT EDI specifications " +"<https://cpe.sunat.gob.pe/node/88/>`_, that keeps track of new changes and " +"updates. The features of this module are based on the resolutions published " +"on the `SUNAT Legislation " +"<https://www.sunat.gob.pe/legislacion/general/index.html/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:25 +msgid "`App Tour - Localización de Peru <https://youtu.be/Ic3mGovkf8Y>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:26 +msgid "" +"`Smart Tutorial - Localización de Peru <https://www.odoo.com/slides/smart-" +"tutorial-localizacion-de-peru-133>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:32 +msgid "Install the Peruvian localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:34 +msgid "" +"Go to *Apps* and search for Peru, then click Install in the module Peru EDI." +" This module has a dependency with *Peru - Accounting*. In case this last " +"one is not installed, Odoo installs it automatically within EDI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "The \"Module\" filter is set on \"Peru\"" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:43 +msgid "" +"When you install a database from scratch selecting Peru as country, Odoo " +"automatically installs the base module: Peru - Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:49 +msgid "" +"In addition to the basic information in the Company, we need to set Peru as " +"the Country, this is essential for the Electronic Invoice to work properly. " +"The field **Address Type Code** represents the establishment code assigned " +"by the SUNAT when companies register their RUC (Unique Contributor " +"Registration):" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Company data for Peru including RUC and Address type code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:60 +msgid "" +"In case the Address type code is unknown, you can set it as the default " +"value: 0000. Be aware that if an incorrect value is entered, the Electronic " +"invoice validation might have errors." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:64 +msgid "The NIF should be set following the RUC format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:68 +msgid "Chart of Account" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:70 +msgid "" +"The chart of accounts is installed by default as part of the set of data " +"included in the localization module, the accounts are mapped automatically " +"in:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:74 +msgid "Default Account Payable." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:77 +msgid "" +"The chart of accounts for Peru is based on the most updated version of the " +":abbr:`PCGE (Plan Contable General Empresarial)`, which is grouped in " +"several categories and is compatible with NIIF accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:82 +msgid "Accounting Settings" +msgstr "การตั้งค่าการบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:84 +msgid "" +"Once the modules are installed and the basic information of your company is " +"set, you need to configure the elements required for Electronic Invoice. For" +" this, go to :menuselection:`Accounting --> Settings --> Peruvian " +"Localization`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:89 +msgid "Basic Concepts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:91 +msgid "Here are some terms that are essential on the Peruvian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:93 +msgid "" +"**EDI**: Electronic Data Interchange, which in this refers to the Electronic" +" Invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:94 +msgid "" +"**SUNAT**: is the organization that enforces customs and taxation in Peru." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:95 +msgid "" +"**OSE**: Electronic Service Operator, `OSE SUNAT's definition " +"<https://cpe.sunat.gob.pe/aliados/ose#:~:text=El%20Operador%20de%20Servicios%20Electr%C3%B3nicos%20(OSE)%20es%20qui%C3%A9n%20se%20encarga,otro%20documento%20que%20se%20emita>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:97 +msgid "**CDR**: Receipt certificate (Constancia de Recepción)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:98 +msgid "" +"**SOL Credentials**: Sunat Operaciones en Línea. User and password are " +"provided by the SUNAT and grant access to Online Operations systems." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:103 +msgid "Signature Provider" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:105 +msgid "" +"As part of the requirements for Electronic Invoice in Peru, your company " +"needs to select a Signature Provider that will take care of the document " +"signing process and manage the SUNAT validation response. Odoo offers three " +"options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:109 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:116 +msgid "IAP (Odoo In-App Purchase)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:110 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:174 +msgid "Digiflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:111 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:190 +msgid "SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:113 +msgid "" +"Please refer to the sections below to check the details and considerations " +"for each option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:118 +msgid "" +"This is the default and the suggested option, considering the digital " +"ceritificate is included as part of the service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "IAP option as signature providers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:126 +msgid "What is the IAP?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:128 +msgid "" +"This is a signature service offered directly by Odoo, the service takes care" +" of the next process:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:130 +msgid "" +"Provides the Electronic invoice Certificate, so you do not need to acquire " +"one by yourself." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:131 +msgid "Send the document to the OSE, in this case, Digiflow." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:132 +msgid "Receive the OSE validation and CDR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:135 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:137 +msgid "" +"The service requires Credits in order to process your electronic documents. " +"Odoo provides 1000 credits for free in new databases. After these credits " +"are consumed, you need to buy a Credit Package." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "Credits" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:142 +msgid "EUR" +msgstr "EUR" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:144 +msgid "22" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "5000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:146 +msgid "110" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:148 +msgid "10,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:148 +msgid "220" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:150 +msgid "20,000" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:150 +msgid "440" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:153 +msgid "The credits are consumed per each document that is sent to the OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:156 +msgid "" +"If you have a validation error and the document needs to be sent one more " +"time, one additional credit will be charged. Therefore, it is paramount that" +" you verify all information is correct before sending your document to the " +"OSE." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:161 +msgid "What do you need to do?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:163 +msgid "" +"In Odoo, once your enterprise contract is activated and you start working in" +" Production, you need to buy credits once the first 1000 are consumed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:165 +msgid "" +"As Digiflow is the OSE used in the IAP, you need to affiliate it as the " +"official OSE for your company on the SUNAT website. This is a simple " +"process. For more information, please check `OSE Affiliation guide " +"<https://drive.google.com/file/d/1BkrMTZIiJyi5XI0lGMi3rbMzHddOL1pa/view?usp=sharing>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:169 +msgid "" +"Register Digiflow as the authorized PSE, please check `PSE Affiliation guide" +" " +"<https://drive.google.com/file/d/1QZoqWvtQERpS0pqp6LcKmw7EBlm9EroU/view?usp=sharing>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:176 +msgid "" +"This option can be used as an alternative, instead of using the IAP services" +" you can send your document validation directly to Digiflow. In this case " +"you need to consider:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:179 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:196 +msgid "" +"Buy your own digital Certificate: For more detail regarding the official " +"vendor list, and the process to acquire it, please refer to `SUNAT Digital " +"Ceritifcates " +"<https://cpe.sunat.gob.pe/informacion_general/certificados_digitales/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:182 +msgid "" +"Sign a service agreement directly with `Digiflow " +"<https://www.digiflow.pe/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:183 +msgid "Provide your SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:192 +msgid "" +"In case your company wants to sign directly with the SUNAT, it is possible " +"to select this option in your configuration. In this case you need to " +"consider: - Get the SUNAT Certification process accepted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:200 +msgid "Provide you SOL credentials." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:203 +msgid "" +"When using direct connection with the SUNAT, the SOL User must be set with " +"the Company RUT + User Id. Example: ``20121888549JOHNSMITH``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:207 +msgid "Testing environment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:209 +msgid "" +"Odoo provides a testing environment that can be activated before your " +"company goes into production." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:211 +msgid "" +"When using the testing environment and the IAP signature, you don’t need to " +"buy testing credits for your transactions as all of them are validated by " +"default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:215 +msgid "" +"By default the databases are set to work on production, make sure to enable " +"the testing mode if needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:221 +msgid "" +"In case you don’t use Odoo IAP, in order to generate the electronic invoice " +"signature, a digital certificate with the extension ``.pfx`` is required. " +"Proceed to this section and load your file and password." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "EDI Certificate wizard" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:232 +msgid "" +"The official currency exchange rate in Peru is provided by the Bank of Peru." +" Odoo can connect directly to its services and get the currency rate either " +"automatically or manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Bank of Peru is displayed in Multicurrency Service option" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:239 +msgid "" +"Please refer to the next section in our documentation for more information " +"about :doc:`multicurrencies <../accounting/get_started/multi_currency>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:243 +msgid "Configure Master data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:248 +msgid "" +"As part of the localization module the taxes are created automatically with " +"their related financial account and electronic invoice configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "List of default taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:256 +msgid "EDI Configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:258 +msgid "" +"As part of the taxes configuration, there are three new fields required for " +"electronic invoice, the taxes created by default have this data included, " +"but in case you create new taxes make sure you fill in the fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Taxes EDI data for Peru" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:268 +msgid "Fiscal Positions" +msgstr "ฐานะทางการเงิน" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:270 +msgid "" +"There are two main fiscal positions included by default when you install the" +" Peruvian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:272 +msgid "" +"**Extranjero - Exportación**: Set this fiscal position on customers for " +"Exportation transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:274 +msgid "**Local Peru**: Set this fiscal position on local customers." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:277 +msgid "Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:279 +msgid "" +"In some Latin American countries, including Peru, some accounting " +"transactions like invoices and vendor bills are classified by document " +"types, defined by the government fiscal authorities, in this case by the " +"SUNAT." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:283 +msgid "" +"Each document type can have a unique sequence per journal where it is " +"assigned. As part of the localization, the Document Type includes the " +"country on which the document is applicable;the data is created " +"automatically when the localization module is installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:287 +msgid "" +"The information required for the document types is included by default so " +"the user does not need to fill anything on this view:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Document Type list" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:295 +msgid "" +"Currently the documents supported on customer invoices are: Invoice, Boleta," +" Debit Note and Credit Note." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:301 +msgid "" +"When creating Sales Journals, the following information must be filled, in " +"addition to the standard fields on the Journals:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:305 +msgid "Use Documents" +msgstr "ใช้งานเอกสาร" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:307 +msgid "" +"This field is used to define if the journal uses Document Types. It is only " +"applicable to Purchase and Sales journals, which are the ones that can be " +"related to the different set of document types available in Peru. By " +"default, all the sales journals created use documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:312 +msgid "Electronic Data Interchange" +msgstr "การแลกเปลี่ยนข้อมูลทางอิเล็กทรอนิกส์" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:314 +msgid "" +"This section indicates which EDI workflow is used in the invoice, for Peru " +"we must select “Peru UBL 2.1”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Journal EDI field" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:322 +msgid "" +"By default, the value Factur-X (FR) is always displayed, make sure you can " +"uncheck it manually." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:328 +msgid "Identification Type and VAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:330 +msgid "" +"As part of the Peruvian localization, the identification types defined by " +"the SUNAT are now available on the Partner form, this information is " +"essential for most transactions either on the sender company and in the " +"customer, make sure you fill in this information in your records." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Partner identification type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:340 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:109 +msgid "Product" +msgstr "สินค้า" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:342 +msgid "" +"Additional to the basic information in your products, for the Peruvian " +"localization, the UNSPC Code on the product is a required value to be " +"configured." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "UNSPC Code on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:354 +msgid "Customer invoice" +msgstr "ใบแจ้งหนี้ของลูกค้า" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:357 +msgid "EDI Elements" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:359 +msgid "" +"Once you have configured your master data, the invoices can be created from " +"your sales order or manually. Additional to the basic invoice information " +"described on :doc:`our page about the invoicing process " +"<../accounting/customer_invoices/overview>`, there are a couple of fields " +"required as part of the Peru EDI:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:364 +msgid "" +"**Document type**: The default value is “Factura Electronica” but you can " +"manually change the document type if needed and select Boleta for example." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice document type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:371 +msgid "" +"**Operation type**: This value is required for Electronic Invoice and " +"indicates the transaction type, the default value is “Internal Sale” but " +"another value can be selected manually when needed, for example Export of " +"Goods." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Invoice operation type field on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:379 +msgid "" +"**EDI Affectation Reason**: In the invoice lines, additional to the Tax " +"there is a field “EDI Affectation Reason” that determines the tax scope " +"based on the SUNAT list that is displayed. All the taxes loaded by default " +"are associated with a default EDI affection reason, if needed you can " +"manually select another one when creating the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Tax affectation reason in invoice line" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:391 +msgid "" +"Once you check all the information in your invoice is correct, you can " +"proceed to validate it. This action registers the account move and triggers " +"the Electronic invoice workflow to send it to the OSE and the SUNAT. The " +"following message is displayed at the top of the invoice:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Sending of EDI Invoice in blue" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:399 +msgid "" +"Asynchronous means that the document is not sent automatically after the " +"invoice has been posted." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:402 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:496 +msgid "Electronic Invoice Status" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:404 +msgid "" +"**To be Sent**: Indicates the document is ready to be sent to the OSE, this " +"can be done either automatically by Odoo with a *cron* that runs every hour," +" or the user can send it immediately by clicking on the button “Sent now”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Send EDI manually" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:412 +msgid "" +"**Sent**: Indicates the document was sent to the OSE and was successfully " +"validated. As part of the validation a ZIP file is downloaded and a message " +"is logged in the chatter indicating the correct Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Message on chatter when the invoice is valid" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:420 +msgid "" +"In case there is a validation error the Electronic Invoice status remains in" +" “To be sent” so the corrections can be made and the invoice can be sent " +"again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:424 +msgid "" +"One credit is consumed each time that you send a document for validation, in" +" this sense if an error is detected on an invoice and you send it one more " +"time, two credits are consumed in total." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:429 +msgid "Common Errors" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:431 +msgid "" +"There are multiple reasons behind a rejection from the OSE or the SUNAT, " +"when this happens Odoo sends a message at the top of the invoice indicating " +"the error details and in the most common cases a hint to fix the issue." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:435 +msgid "If a validation error is received, you have two options:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:437 +msgid "" +"In case the error is related to master data on the partner, customer or " +"taxes, you can simply apply the change on the record (example customer " +"identification type) and once it is done click on the Retry button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:440 +msgid "" +"If the error is related to some data recorded on the invoice directly " +"(Operation type, missing data on the invoice lines), the correct solution is" +" to reset the invoice to Draft, apply the changes, and then send the invoice" +" again to the SUNAT for another validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "List of common errors on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:449 +msgid "" +"For more detail please refert to `Common errors in SUNAT " +"<https://www.nubefact.com/codigos-error-sunat/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:453 +msgid "Invoice PDF Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:455 +msgid "" +"After the invoice is accepted and validated by the SUNAT, the invoice PDF " +"report can be printed. The report includes a QR code, indicating the invoice" +" is a valid fiscal document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:463 +msgid "IAP Credits" +msgstr "IAP เครดิต" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:465 +msgid "" +"Odoo’s Electronic IAP offers 1000 credits for free, after these credits are " +"consumed in your production database, your company must buy new credits in " +"order to process your transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:468 +msgid "" +"Once you run out of credits a red label is displayed at the top of the " +"invoice indicating that additional credits are required, you can easily buy " +"them by accessing the link provided in the message." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Buying credits in the IAP" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:476 +msgid "" +"In the IAP service includes packages with different pricing based on the " +"number of credits. The price list in the IAP is always displayed in EUR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:480 +msgid "Special Use cases" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:483 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:519 +msgid "Cancellation process" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:485 +msgid "" +"Some scenarios require an invoice cancellation, for example, when an invoice" +" was created by mistake. If the invoice was already sent and validated by " +"the SUNAT, the correct way to proceed is by clicking on the button Request " +"Cancellation:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Request invoice cancellation button" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:493 +msgid "In order to cancel an invoice, please provide a cancellation Reason." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:498 +msgid "" +"**To Cancel**: Indicates the cancellation request is ready to be sent to " +"the OSE, this can be done either automatically by Odoo with a *cron* that " +"runs every hour, or the user can send it immediately by clicking on the " +"button “Send now”. Once it is sent, a cancellation ticket is created, as a " +"result the next message and CDR File are logged in the chatter:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Cancellation CDR sent by the SUNAT" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:507 +msgid "" +"**Cancelled**: Indicates the cancellation request was sent to the OSE and " +"was successfully validated. As part of the validation a ZIP file is " +"downloaded and a message is logged in the chatter indicating the correct " +"Government validation." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "nvoice after cancellation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:516 +msgid "One credit is consumed on each cancellation request." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:521 +msgid "" +"When creating exportation invoices, take into account the next " +"considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:523 +msgid "The Identification type on your customer must be Foreign ID." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:524 +msgid "Operation type in your invoice must be an Exportation one." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:525 +msgid "The taxes included in the invoice lines should be EXP taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Exportation invoices main data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:532 +msgid "Advance Payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:534 +msgid "Create the advance payment Invoice and apply its related payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:535 +msgid "Create the final invoice without considering the advance payment." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:536 +msgid "" +"Create a credit note for the Final invoice with the advance payment amount." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:537 +msgid "Reconcile the Credit note with the final invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:538 +msgid "" +"The remaining balance on the final invoice should be paid with a regular " +"payment transaction." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:541 +msgid "Detraction Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:543 +msgid "" +"When creating invoices that is subject to Detractions, take into account the" +" next considerations:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:545 +msgid "" +"All the products included in the invoice must have these fields configured:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction fields on products" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:551 +msgid "Operation type in your invoice must be ``1001``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:0 +msgid "Detraction code on invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:558 +msgid "Credit Notes" +msgstr "ใบลดหนี้" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:560 +msgid "" +"When a correction or refund is needed over a validated invoice, a credit " +"note must be generated, for this just click on the button “Add Credit Note”," +" a part of the Peruvian localization you need to prove a Credit Reason " +"selecting one of the options in the list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Add Credit Note from invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:569 +msgid "" +"When creating your first credit Note, select the Credit Method: Partial " +"Refund, this allows you to define the credit note sequence." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:572 +msgid "By default the Credit Note is set in the document type:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst-1 +msgid "Credit Note document type" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:578 +msgid "" +"To finish the workflow please follow the instructions on :doc:`our page " +"about Credit Notes <../accounting/customer_invoices/credit_notes>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:582 +msgid "" +"The EDI workflow for the Credit notes works in the same way as the invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:587 +msgid "" +"As part of the Peruvian localization, besides creating credit notes from an " +"existing document you can also create debit Notes. For this just use the " +"button “Add Debit Note”." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/peru.rst:590 +msgid "By default the Debit Note is set in the document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:3 +msgid "Philippines" +msgstr "ประเทศฟิลิปปินส์" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:8 +msgid "" +":ref:`Install <general/install>` the :guilabel:`🇵🇭 Philippines` :ref:`fiscal" +" localization package <fiscal_localizations/packages>` to get all the " +"default accounting features of the Philippine localization, such as a chart " +"of accounts, taxes, and the BIR 2307 report. These provide a base template " +"to get started with using Philippine accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:14 +msgid "" +"When creating a new database and `Philippines` is selected as a country, the" +" fiscal localization module **Philippines - Accounting** is automatically " +"installed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:16 +msgid "" +"If installing the module in an existing company, the **chart of accounts** " +"and **taxes** will *not* be replaced if there are already posted journal " +"entries." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:18 +msgid "" +"The BIR 2307 report is installed, but the withholding taxes may need to be " +"manually created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:21 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:28 +msgid "Chart of accounts and taxes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:23 +msgid "" +"A minimum configuration default chart of accounts is installed, and the " +"following types of taxes are installed and also linked to the relevant " +"account:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:26 +msgid "VAT 12%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:27 +msgid "VAT Exempt" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:30 +msgid "" +"For the withholding taxes, there is an additional :guilabel:`Philippines " +"ATC` field under the :guilabel:`Philippines` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Philippines ATC code field set on taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:36 +msgid "" +"Taxes' ATC codes are used for the BIR 2307 report. If a tax is created " +"manually, its ATC code must be added." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:42 +msgid "" +"When a company or an individual (not belonging to a company) contact is " +"located in the Philippines, fill in the :guilabel:`Tax ID` field with their " +"`Taxpayer Identification Number (TIN)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:45 +msgid "" +"For individuals not belonging to a company, identify them by using the " +"following additional fields:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:47 +msgid ":guilabel:`First Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:48 +msgid ":guilabel:`Middle Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:49 +msgid ":guilabel:`Last Name`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Individual type contact with First, Middle, and Last Name fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:55 +msgid "" +"For both :guilabel:`Company` and :guilabel:`Individual`, the TIN should " +"follow the `NNN-NNN-NNN-NNNNN` format. The branch code should follow the " +"last digits of the TIN, or else it can be left as `00000`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:60 +msgid "BIR 2307 report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:62 +msgid "" +"**BIR 2307** report data, also known as *Certificate of Creditable Tax " +"Withheld at Source*, can be generated for purchase orders and vendor " +"payments with the applicable withholding taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:65 +msgid "" +"To generate a BIR 2307 report, select one or multiple vendor bills from the " +"list view, and click :menuselection:`Action --> Download BIR 2307 XLS`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Multiple vendor bills selected with action to \"Download BIR 2307 XLS\"." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:71 +msgid "The same action can be performed on a vendor bill from the form view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:73 +msgid "" +"A pop-up appears to review the selection, then click on " +":guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst-1 +msgid "Pop up menu to generate BIR 2307 XLS file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:78 +msgid "" +"This generates the `Form_2307.xls` file that lists all the vendor bill lines" +" with the applicable withholding tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:81 +msgid "" +"The same process above can also be done for a *single* vendor :doc:`payment " +"<../accounting/payments>` if they were linked to one or more :doc:`vendor " +"bills <../accounting/payments>` with applied withholding taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:86 +msgid "" +"If there is no withholding tax applied, then the XLS file will not generate " +"records for those vendor bill lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:88 +msgid "" +"When grouping payments for multiple bills, Odoo splits the payments based on" +" the contact. From a payment, clicking :menuselection:`Action --> Download " +"BIR 2307 XLS`, generates a report that only includes vendor bills related to" +" that contact." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:93 +msgid "" +"Odoo cannot generate the BIR 2307 PDF report or DAT files directly. The " +"generated `Form_2307.xls` file can be exported to an *external* tool to " +"convert it to BIR DAT or PDF format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:3 +msgid "Romania" +msgstr "ประเทศโรมาเนีย" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:8 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Romanian localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:17 +msgid ":guilabel:`Romania - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:18 +msgid "`l10n_ro`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:20 +msgid ":guilabel:`Romanian SAF-T Export`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:21 +msgid "`l10n_ro_saft`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:22 +msgid "Module to generate the **D.406 declaration** in the SAF-T format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "Modules for the Romanian localization" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:28 +msgid "D.406 declaration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:30 +msgid "" +"Starting January 1, 2023, companies registered for tax purposes in Romania " +"must report their accounting data to the Romanian Tax Agency monthly or " +"quarterly in the D.406 declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:33 +msgid "" +"Odoo provides all you need to export the data of this declaration in the " +"SAF-T XML format, which you can validate and sign using the software " +"provided by the Romanian Tax Agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:37 +msgid "" +"Currently, Odoo only supports the generation of the monthly/quarterly D.406 " +"declaration (containing journal entries, invoices, vendor bills, and " +"payments). The yearly declaration (including assets) and the on-demand " +"declaration (including inventory) are not yet supported." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:45 +msgid "Company" +msgstr "บริษัท" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:47 +msgid "" +"Under :guilabel:`Settings --> General Settings`, in the **Companies** " +"section, click :guilabel:`Update Info` and fill in the company's " +":guilabel:`Country`, :guilabel:`City`, and :guilabel:`Telephone Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:50 +msgid "" +"Provide your company's :abbr:`CUI (Codul Unic de Inregistrare)` number or " +":abbr:`CIF (*Codul de identificare fiscală*)` number (for foreign companies)" +" in the :guilabel:`Company ID` field, without the `RO` prefix (e.g., " +"`18547290`)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:53 +msgid "" +"If your company is **registered** for VAT in Romania, fill in the " +":guilabel:`Tax ID` field number, including the `RO` prefix (e.g., " +"`RO18547290`). If the company is **not** registered for VAT in Romania, you " +"**must not** fill in the :guilabel:`Tax ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:56 +msgid "" +"Open the **Contacts** app and search for your company. Open your company's " +"profile, and in the :guilabel:`Accounting` tab, click :guilabel:`Add a line`" +" and add your **bank account number** if not informed already. Make sure the" +" profile is set as :guilabel:`Company` above the **name**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:60 +msgid "" +"You must have at least one **contact person** linked to your company in the " +"**Contacts** app. If no **contact person** is linked, create a new one by " +"clicking :guilabel:`New`, set it as :guilabel:`Individual`, and select your " +"company in the :guilabel:`Company name` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:67 +msgid "" +"To generate a file receivable by the Romanian Tax Agency, the chart of " +"accounts must not deviate from an official chart of accounts, such as:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:70 +msgid "" +"the chart of accounts for commercial companies (*PlanConturiBalSocCom*), " +"which is installed by default when creating a company with the Romanian " +"localization or;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:72 +msgid "" +"the chart of accounts for companies following `IFRS " +"<https://www.ifrs.org/>`_ (*PlanConturiIFRS*)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:74 +msgid "" +"Under :guilabel:`Settings --> Accounting`, in the **Romanian localization** " +"section, set the :guilabel:`Tax Accounting Basis` to reflect the accounting " +"regulations and Chart of Accounts used by the company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:82 +msgid "Customer and supplier" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:84 +msgid "" +"Fill in the :guilabel:`Country`, :guilabel:`City`, and :guilabel:`Zip Code` " +"of each partner that appears in your invoices, vendor bills, or payments " +"through the **Contacts** app." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:87 +msgid "" +"For partners that are companies, you must fill in the VAT number (including " +"the country prefix) in the :guilabel:`Tax ID` field. If the partner is a " +"company based in Romania, you may instead fill in the CUI number (without " +"the 'RO' prefix) in the :guilabel:`Company ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:94 +msgid "" +"You must indicate the :guilabel:`Romanian SAF-T Tax Type` (3-digit number) " +"and :guilabel:`Romanian SAF-T Tax Code` (6-digit number) on each of the " +"taxes you use. This is already done for the taxes that exist by default in " +"Odoo. To do so, go to :menuselection:`Accounting --> Configuration --> " +"Taxes`, select the tax you wish to modify, click the :guilabel:`Advanced " +"Options` tab, and fill in the **tax type** and **tax code** fields." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:101 +msgid "" +"The **tax type** and **tax code** are codes defined by the Romanian Tax " +"Agency for the **D.406 declaration**. These can be found in the Excel " +"spreadsheet published as guidance for completing the declaration, which you " +"can find on the `website of the Romanian Tax Agency " +"<https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:111 +msgid "" +"For some types of goods transactions, the :guilabel:`Intrastat Code` (Cod " +"NC) must be configured on the product, as it is required by Romanian law:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:114 +msgid "import / export transactions;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:115 +msgid "" +"acquisitions / supplies of food products subjected to reduced VAT rate;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:116 +msgid "intra-community movements subjected to intrastat reporting;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:117 +msgid "" +"acquisitions / supplies subjected to local reversed VAT charge (depending on" +" Cod NC); and" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:118 +msgid "" +"transactions with excisable products for which excise duties are determined " +"based on the Cod NC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:120 +msgid "" +"If the Intrastat Code is not specified on a non-service product, the default" +" code '0' will be used." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:122 +msgid "" +"To configure the :guilabel:`Intrastat Codes`, go to " +":menuselection:`Accounting --> Customers --> Products`, select a product, " +"and in the :guilabel:`Accounting` tab, set a :guilabel:`Commodity Code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:127 +msgid ":doc:`../accounting/reporting/intrastat`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:132 +msgid "" +"You must check the :guilabel:`Is self-invoice (RO)?` checkbox in the " +":guilabel:`Other Info` tab for any vendor bill that is a self-invoice (i.e. " +"a vendor bill that you issued yourself in the absence of an invoice document" +" received from a supplier)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:137 +msgid "Generating the declaration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:140 +msgid "Exporting your data" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:142 +msgid "" +"To export the XML for the D.406 declaration, go to " +":menuselection:`Accounting --> Reports --> General Ledger` and click on " +":guilabel:`SAF-T`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "Click on the 'SAF-T' button to export the D.406 XML declaration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:149 +msgid "" +"You can then validate and sign the XML file using the Romanian Tax Agency's " +"validation software, *DUKIntegrator*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:153 +msgid "Signing the report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:155 +msgid "" +"Download and install the *DUKIntegrator* validation software found on the " +"`website of the Romanian Tax Agency " +"<https://www.anaf.ro/anaf/internet/ANAF/despre_anaf/strategii_anaf/proiecte_digitalizare/saf_t/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:158 +msgid "" +"Once you have generated the XML, open 'DUKIntegrator' and select the file " +"you have just generated." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:160 +msgid "" +"Click on :guilabel:`Validare + creare PDF` to create an **unsigned** PDF " +"containing your report, or :guilabel:`Validare + creare PDF semnat` to " +"create a **signed** PDF containing your report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst-1 +msgid "The DUKIntegrator validation software." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/romania.rst:167 +msgid "" +"If the *DUKIntegrator* validator detects errors or inconsistencies in your " +"data, it generates a file that explains the errors. In this case, you need " +"to correct those inconsistencies in your data before you can submit the " +"report to the Romanian Tax Agency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:3 +msgid "Saudi Arabia" +msgstr "ประเทศซาอุดิอาระเบีย" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:8 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the Saudi Arabian localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:18 +msgid "Saudi Arabia - Accounting" +msgstr "ประเทศซาอุดิอาระเบีย - ระบบบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:19 +msgid "`l10n_sa`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:21 +msgid "Saudi Arabia - E-invoicing" +msgstr "ประเทศซาอุดิอาระเบีย - ใบแจ้งหนี้อิเล็กทรอนิกส์" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:22 +msgid "`l10n_sa_edi`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:23 +msgid "ZATCA e-invoices implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:24 +msgid "Saudi Arabia - Point of Sale" +msgstr "ประเทศซาอุดิอาระเบีย - ระบบขายหน้าร้าน" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:25 +msgid "`l10n_sa_pos`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:26 +msgid "Point of Sale compliance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:29 +msgid "ZATCA e-invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:31 +msgid "" +"The ZATCA e-invoicing system is designed to streamline and digitize the " +"invoicing process for businesses operating in Saudi Arabia." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:35 +msgid "" +"`ZATCA e-invoicing page " +"<https://zatca.gov.sa/en/E-Invoicing/Pages/default.aspx>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:40 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Companies`, click " +":guilabel:`Update info`, and ensure the following company information is " +"complete and up-to-date." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:43 +msgid "The full :guilabel:`Company Name`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:44 +msgid "" +"All relevant :guilabel:`Address` fields, including the :guilabel:`Building " +"Number` and :guilabel:`Plot Identification` (four digits each)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:46 +msgid "" +"Select an enterprise :guilabel:`Identification Scheme`. It is recommended to" +" use the :guilabel:`Commercial Registration Number`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:48 +msgid "" +"Enter the :guilabel:`Identification Number` for the selected " +":guilabel:`Identification Scheme`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:49 +msgid "The :guilabel:`VAT` number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:50 +msgid "Ensure the :guilabel:`Currency` is set to :guilabel:`SAR`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:53 +msgid "" +"It is also necessary to fill out similar information for partner companies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:56 +msgid "Simulation mode" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:59 +msgid "" +"It is strongly recommended to thoroughly test all invoicing workflows using " +"the Fatoora **simulation** portal first, as **any** invoice submitted to the" +" regular Fatoora portal will be accounted for, which could lead to fines and" +" penalties." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:64 +msgid "Fatoora simulation portal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:66 +msgid "" +"Log in on the `Fatoora portal <https://fatoora.zatca.gov.sa/>`_ using the " +"company's ZATCA credentials. Then, click the :guilabel:`Fatoora Simulation " +"Portal` button to switch to the simulation portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:71 +msgid "" +"`ZACTA Fatoora portal user manual version 3 (May 2023) " +"<https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/Fatoora_Portal_User_Manual_English.pdf>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:76 +msgid "ZATCA API integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:78 +msgid "" +"On Odoo, go to :menuselection:`Accounting --> Configuration --> Settings`. " +"Under :guilabel:`ZATCA API Integration`, select the :guilabel:`Simulation " +"(Pre-Production)` :guilabel:`API mode` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:87 +msgid "" +"Each sales journal on Odoo needs to be configured. To do so, go to " +":menuselection:`Accounting --> Configuration --> Journals`, open any sales " +"journal (e.g., Customer Invoices), and go to the :guilabel:`ZATCA` tab. Once" +" there, enter any :guilabel:`Serial Number` to identify the journal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:92 +msgid "" +"The same serial number can be used for all of the company's sales journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:94 +msgid "" +"Next, click :guilabel:`Onboard Journal`. In the dialog box, providing an " +":abbr:`OTP (one-time password)` code is required. To retrieve it, open the " +"`Fatoora simulation portal <https://fatoora.zatca.gov.sa/>`_, click " +":guilabel:`Onboard New Solution Unit/Device`, choose the number of OTP codes" +" to generate (one per journal to configure), and click :guilabel:`Generate " +"OTP Code`. Copy an OTP code, it into the dialog box on Odoo, and click " +":guilabel:`Request`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:101 +msgid "OTP codes expire after one hour." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:104 +msgid "" +"If any issue occurs during onboarding, click :guilabel:`Regenerate CSR` to " +"start again." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:107 +msgid "Testing" +msgstr "ทดสอบ" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:109 +msgid "" +"When confirming an invoice, there is now an option to process the invoice, " +"sending it directly the Fatoora simulation portal. Odoo displays the " +"portal's response after each submission. Only rejected invoices can be reset" +" to draft and edited on Odoo. Furthermore, at the end of each day, Odoo " +"sends all unprocessed invoices to the portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:115 +msgid "" +"Testing all invoicing workflows, preferably with real invoices and for a " +"reasonable amount of time, is recommended." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:117 +msgid "" +"Compare the invoices received statistics page on the Fatoora simulation " +"portal with the list of invoices on Odoo to ensure both align." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:123 +msgid "" +"When using a **0% tax** in a customer invoice, it is necessary to specify " +"the reason behind such a rate. To configure taxes, go to " +":menuselection:`Accounting --> Configuration --> Settings --> Taxes`, and " +"open the tax to edit. Under the :guilabel:`Advanced Options`, select an " +":guilabel:`Exemption Reason Code` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:128 +msgid "" +"When using **retention** or **withholding an amount** in a customer invoice," +" the tax used to retain the amount needs to be specified." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:132 +msgid "Production mode" +msgstr "โหมดการผลิต" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:134 +msgid "" +"When ready for production, change the :ref:`API mode <saudi-arabia/api-" +"mode>` to :guilabel:`Production` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:138 +msgid "" +"Setting the :guilabel:`API mode` to :guilabel:`Production` is " +"**irreversible**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:140 +msgid "" +"The sales journals initially linked to the simulation portal now needs to be" +" linked to the regular portal. To do so, :ref:`onboard the journals <saudi-" +"arabia/journals>` again, ensuring to use the regular `Fatoora portal " +"<https://fatoora.zatca.gov.sa/>`_ this time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:3 +msgid "Singapore" +msgstr "ประเทศสิงคโปร์" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:6 +msgid "Add PayNow QR codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:8 +msgid "" +"PayNow is a payment service platform that allows customers to make instant " +"domestic payments to individuals and merchants in Singapore dollars via " +"online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst-1 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:18 +msgid "PayNow bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:20 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate PayNow. Set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:25 +msgid "" +"The account holder's country must be set to Singapore on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:45 +msgid "Issue invoices with PayNow QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:53 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the PayNow QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:3 +msgid "Spain" +msgstr "ประเทศสเปน" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:6 +msgid "Spanish chart of accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:8 +msgid "Several Spanish charts of accounts are available by default in Odoo:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:10 +msgid "PGCE PYMEs 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:11 +msgid "PGCE Completo 2008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:12 +msgid "PGCE Entitades" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:14 +msgid "" +"To choose the one you want, go to :menuselection:`Accounting --> " +"Configuration --> Settings`, then select a package in the :guilabel:`Fiscal " +"localization` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:18 +msgid "" +"When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed" +" by default." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:21 +msgid "" +"You can only change the accounting package as long as you have not created " +"any accounting entry." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:24 +msgid "Spanish accounting reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:26 +msgid "" +"If the Spanish accounting localization is installed, you have access to " +"accounting reports specific to Spain:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:30 +msgid "Tax Report (Modelo 111)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:31 +msgid "Tax Report (Modelo 115)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:32 +msgid "Tax Report (Modelo 303)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:33 +msgid "Tax Report (Modelo 347)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:34 +msgid "Tax Report (Modelo 349)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:35 +msgid "Tax Report (Modelo 390)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:3 +msgid "Switzerland" +msgstr "ประเทศสวิตเซอร์แลนด์" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:6 +msgid "ISR (In-payment Slip with Reference number)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:8 +msgid "" +"The ISRs are payment slips used in Switzerland. You can print them directly " +"from Odoo. On the customer invoices, there is a new button called *Print " +"ISR*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:16 +msgid "" +"The button *Print ISR* only appears there is well a bank account defined on " +"the invoice. You can use CH6309000000250097798 as bank account number and " +"010391391 as CHF ISR reference." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:23 +msgid "Then you open a pdf with the ISR." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:28 +msgid "" +"There exists two layouts for ISR: one with, and one without the bank " +"coordinates. To choose which one to use, there is an option to print the " +"bank information on the ISR. To activate it, go in " +":menuselection:`Accounting --> Configuration --> Settings --> Customer " +"Invoices` and enable **Print bank on ISR**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:38 +msgid "ISR reference on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:40 +msgid "" +"To ease the reconciliation process, you can add your ISR reference as " +"**Payment Reference** on your invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:43 +msgid "" +"To do so, you need to configure the Journal you usually use to issue " +"invoices. Go to :menuselection:`Accounting --> Configuration --> Journals`, " +"open the Journal you want to modify (By default, the Journal is named " +"*Customer Invoices*), click en *Edit*, and open the *Advanced Settings* tab." +" In the **Communication Standard** field, select *Switzerland*, and click on" +" *Save*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst-1 +msgid "" +"Configure your Journal to display your ISR as payment reference on your " +"invoices in Odoo" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:53 +msgid "Currency Rate Live Update" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:55 +msgid "" +"You can update automatically your currencies rates based on the Federal Tax " +"Administration from Switzerland. For this, go in :menuselection:`Accounting " +"--> Settings`, activate the multi-currencies setting and choose the service " +"you want." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:64 +msgid "Updated VAT for January 2018" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:66 +msgid "" +"Starting from the 1st January 2018, new reduced VAT rates will be applied in" +" Switzerland. The normal 8.0% rate will switch to 7.7% and the specific rate" +" for the hotel sector will switch from 3.8% to 3.7%." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:71 +msgid "" +"How to update your taxes in Odoo Enterprise (Odoo Online or On-premise)?" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:73 +msgid "" +"If you have the V11.1 version, all the work is already been done, you don't " +"have to do anything." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:76 +msgid "" +"If you have started on an earlier version, you first have to update the " +"module \"Switzerland - Accounting Reports\". For this, you go in " +":menuselection:`Apps --> remove the filter \"Apps\" --> search for " +"\"Switzerland - Accounting Reports\" --> open the module --> click on " +"\"upgrade\"`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:83 +msgid "" +"Once it has been done, you can work on creating new taxes for the updated " +"rates." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:87 +msgid "" +"**Do not suppress or modify the existing taxes** (8.0% and 3.8%). You want " +"to keep them since you may have to use both rates for a short period of " +"time. Instead, remember to archive them once you have encoded all your 2017 " +"transactions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:92 +msgid "The creation of such taxes should be done in the following manner:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:94 +msgid "" +"**Purchase taxes**: copy the origin tax, change its name, label on invoice, " +"rate and tax group (effective from v10 only)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:97 +msgid "" +"**Sale taxes**: copy the origin tax, change its name, label on invoice, rate" +" and tax group (effective from v10 only). Since the vat report now shows the" +" details for old and new rates, you should also set the tags accordingly to" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:102 +msgid "" +"For 7.7% taxes: Switzerland VAT Form: grid 302 base, Switzerland VAT Form: " +"grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:105 +msgid "" +"For 3.7% taxes: Switzerland VAT Form: grid 342 base, Switzerland VAT Form: " +"grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:108 +msgid "" +"You'll find below, as examples, the correct configuration for all taxes " +"included in Odoo by default" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Name**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Rate**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Label on Invoice**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Group (effective from V10)**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tax Scope**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:112 +msgid "**Tag**" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "TVA 7.7% sur achat B&S (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +msgid "7.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA 7.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "Switzerland VAT Form: grid 400" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "TVA 7.7% sur achat B&S (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 +msgid "7.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "TVA 7.7% sur invest. et autres ch. (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +msgid "7.7% invest." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "Switzerland VAT Form: grid 405" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "TVA 7.7% sur invest. et autres ch. (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 +msgid "7.7% invest. Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "TVA 3.7% sur achat B&S (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +msgid "3.7% achat" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:122 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA 3.7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "TVA 3.7% sur achat B&S (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:124 +msgid "3.7% achat Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "TVA 3.7% sur invest. et autres ch. (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 +msgid "3.7% invest" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "TVA 3.7% sur invest. et autres ch. (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 +msgid "3.7% invest Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +msgid "TVA due a 7.7% (TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "" +"Switzerland VAT Form: grid 302 base, Switzerland VAT Form: grid 302 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "TVA due à 7.7% (Incl. TN)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 +msgid "7.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +msgid "TVA due à 3.7% (TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "" +"Switzerland VAT Form: grid 342 base, Switzerland VAT Form: grid 342 tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "TVA due a 3.7% (Incl. TS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 +msgid "3.7% Incl." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:139 +msgid "" +"If you have questions or remarks, please contact our support using " +"odoo.com/help." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:143 +msgid "" +"Don't forget to update your fiscal positions. If you have a version 11.1 (or" +" higher), there is nothing to do. Otherwise, you will also have to update " +"your fiscal positions accordingly." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:3 +msgid "Thailand" +msgstr "ประเทศไทย" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:8 +msgid "" +":ref:`Install <general/install>` the :guilabel:`🇹🇭 Thailand` localization " +"package to get all the features of the Thai localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:17 +msgid ":guilabel:`Thailand - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:18 +msgid "`l10n_th`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:20 +msgid ":guilabel:`Thailand - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:21 +msgid "`l10n_th_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:22 +msgid "Country-specific accounting reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Thailand localization modules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:30 +msgid "" +"Odoo's fiscal localization package for Thailand includes the following " +"taxes:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:32 +msgid "VAT 7%" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:33 +msgid "VAT-exempted" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:34 +msgid "Withholding tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:35 +msgid "Withholding income tax" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:40 +msgid "" +"Odoo allows users to generate Excel files to submit their VAT to the " +"**Revenue Department** of Thailand." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:44 +msgid "Sales and purchase tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:46 +msgid "" +"To generate a sales and purchase tax report, go to " +":menuselection:`Accounting --> Reporting --> Tax Report`. Select a specific " +"time or time range on the tax report, and click :guilabel:`VAT-202-01 " +"(xlsx)` for purchase tax and :guilabel:`VAT-202-02 (xlsx)` for sales tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Thai purchase and sales taxes reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:54 +msgid "Withholding PND tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:56 +msgid "" +"PND report data displays the summarized amounts of the applicable " +"**withholding corporate income tax returns (domestic)** from vendor bills " +"under the :guilabel:`PND53 (TH)` and :guilabel:`PND3 (TH)` tax reports. It " +"is installed by default with the Thai localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PND tax reports" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:64 +msgid "" +"Withholding corporate income tax returns (domestic) is the tax used in case " +"the company has withheld the tax from “**Personal (PND3)**” or “**Corporate " +"(PND53)**” services provided such as rental, hiring, transportation, " +"insurance, management fee, consulting, etc." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:68 +msgid "" +"The PND tax report allows users to generate a CSV file for bills to upload " +"on the `RDprep for Thailand e-Filling application " +"<https://efiling.rd.go.th/rd-cms/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:71 +msgid "" +"To generate a PND CSV file, go to :menuselection:`Accounting --> Reporting " +"--> Tax Report`, select a specific time or time range on the tax report, and" +" click :guilabel:`PND3` or :guilabel:`PND53`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:74 +msgid "" +"This generates the :file:`Tax Report PND3.csv` and :file:`Tax Report " +"PND53.csv` files that lists all the vendor bill lines with the applicable " +"withholding tax." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PND3 and PND53 CSV files" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:81 +msgid "" +"Odoo cannot generate the PND or PDF report or **withholding tax " +"certificate** directly. The generated :file:`Tax Report PND3.csv` and " +":file:`Tax Report PND53.csv` files must be exported to an external tool to " +"convert them into a **withholding PND** report or a **PDF** file." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:86 +msgid "Tax invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:88 +msgid "" +"The **tax invoice PDF** report can be generated from Odoo through the " +"**Invoicing** module. Users have the option to print PDF reports for normal" +" invoices and tax invoices. To print out **tax invoices**, users can click " +"on :guilabel:`Print Invoices` in Odoo. Regular invoices can be printed as " +"**commercial invoices** by clicking on :menuselection:`Cog button (⚙️) --> " +"Print --> Commercial Invoice`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Commercial invoice printing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:98 +msgid "Headquarter/Branch number settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:100 +msgid "" +"You can inform a company's **Headquarters** and **Branch number** in the " +"**Contacts** app. Once in the app, open the **contact form** of the company " +"and under the :guilabel:`Sales & Purchase` tab:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:103 +msgid "" +"If the contact is identified as a branch, input the **Branch number** in the" +" :guilabel:`Company ID` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:105 +msgid "" +"If the contact is a **Headquarters**, leave the :guilabel:`Company ID` field" +" **blank**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "Company Headquarter/Branch number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:111 +msgid "" +"This information is used in the **tax invoice** PDF report and PND **tax " +"report** export." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:114 +msgid "PromptPay QR code on invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:116 +msgid "" +"The **PromptPay QR code** is a QR code that can be added to invoices to " +"allow customers to pay their bills using the PromptPay-supported bank mobile" +" application. The QR code is generated based on the **invoice amount** and " +"one of the following **merchant information**:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:120 +msgid "Ewallet ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:121 +msgid "Merchant Tax ID" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:122 +msgid "Mobile Number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:131 +msgid "PromptPay QR bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:133 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate PromptPay QR. Set the" +" :guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the chosen type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:138 +msgid "" +"The :guilabel:`Include Reference` checkbox doesn't work for PromptPay QR " +"codes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst-1 +msgid "PromptPay bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:149 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Journals`, open the " +"bank journal, then fill in the :guilabel:`Account Number` and " +":guilabel:`Bank` under the :guilabel:`Journal Entries` tab." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:156 +msgid "Issue invoices with PromptPay QR code" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:158 +msgid "" +"When creating a new invoice, open the :guilabel:`Other Info` tab and set the" +" :guilabel:`Payment QR-code` option to :guilabel:`EMV Merchant-Presented QR-" +"code`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:164 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the PromptPay QR code." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "สหรัฐอาหรับเอมิเรตส์" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:10 +msgid "" +":ref:`Install <general/install>` the following modules to get all the " +"features of the **United Arab Emirates** localization:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:19 +msgid ":guilabel:`United Arab Emirates - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:20 +msgid "``l10n_ae``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:21 +msgid "" +"Default :doc:`fiscal localization package " +"</applications/finance/fiscal_localizations>`. Includes all accounts, taxes," +" and reports." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`U.A.E. - Payroll`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:24 +msgid "``l10n_ae_hr_payroll``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`U.A.E. - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:27 +msgid "``l10n_ae_hr_payroll_account``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:29 +msgid ":guilabel:`United Arab Emirates - Point of Sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:30 +msgid "``l10n_ae_pos``" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:31 +msgid "Includes the UAE-compliant POS receipt." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the modules to install." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:40 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Chart of Accounts` to" +" view all default accounts available for the UAE localization package. You " +"can filter by :guilabel:`Code` using the numbers on the far left or by " +"clicking on :menuselection:`Group By --> Account Type`. You can " +":guilabel:`Enable`/:guilabel:`Disable` reconciliation or **configure** " +"specific accounts according to your needs." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:47 +msgid "" +"Always keep at least one **receivable account** and one **payable account** " +"active." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:48 +msgid "" +"It is also advised to **keep the accounts below active**, as they are used " +"either as transitory accounts by Odoo or are specific to the **UAE " +"localization package**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:55 +msgid "Account Name" +msgstr "ชื่อบัญชี" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:57 +msgid "102011" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:60 +msgid "102012" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:61 +msgid "Accounts Receivable (POS)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:63 +msgid "201002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:64 +msgid "Payables" +msgstr "เจ้าหนี้" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:66 +msgid "101004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:69 +msgid "105001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:70 +msgid "Cash" +msgstr "เงินสด" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:72 +msgid "100001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:73 +msgid "Liquidity Transfer" +msgstr "โอนย้ายภายใน" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:75 +msgid "101002" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:78 +msgid "101003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:79 +msgid "Outstanding Payments" +msgstr "การชำระเงินคงค้าง" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:81 +msgid "104041" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:82 +msgid "VAT Input" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:84 +msgid "100103" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:85 +msgid "VAT Receivable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:87 +msgid "101001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:88 +msgid "Bank Suspense Account" +msgstr "บัญชีพักของธนาคาร" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:90 +msgid "201017" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:91 +msgid "VAT Output" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:93 +msgid "202001" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:94 +msgid "End of Service Provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:96 +msgid "202003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:97 +msgid "VAT Payable" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:99 +msgid "999999" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:100 +msgid "Undistributed Profits/Losses" +msgstr "กำไร/ขาดทุนที่ยังไม่ได้สรุป" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:102 +msgid "400003" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:103 +msgid "Basic Salary" +msgstr "เงินเดือนขั้นพื้นฐาน" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:105 +msgid "400004" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:106 +msgid "Housing Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:108 +msgid "400005" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:109 +msgid "Transportation Allowance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:111 +msgid "400008" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:112 +msgid "End of Service Indemnity" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:118 +msgid "" +"To access your taxes, go to :menuselection:`Accounting --> Configuration -->" +" Taxes`. Activate/deactivate, or :doc:`configure " +"</applications/finance/accounting/taxes/>` the taxes relevant to your " +"business by clicking on them. Remember to only set tax accounts on the " +"**5%** tax group, as other groups do not need closing. To do so, enable the " +":doc:`developer mode <../../general/developer_mode>` and go to " +":menuselection:`Configuration --> Tax Groups`. Then, set a :guilabel:`Tax " +"current account (payable)`, :guilabel:`Tax current account (receivable)`, " +"and an :guilabel:`Advance Tax payment account` for the **5%** group." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:127 +msgid "The :abbr:`RCM (Reverse Charge Mechanism)` is supported by Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Preview of the UAE localization package's taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:134 +msgid "Currency exchange rates" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:136 +msgid "" +"To update the currency exchange rates, go to :menuselection:`Accounting --> " +"Configuration --> Settings --> Currencies`. Click on the update button " +"(:guilabel:`🗘`) found next to the :guilabel:`Next Run` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:140 +msgid "" +"To launch the update automatically at set intervals, change the " +":guilabel:`Interval` from :guilabel:`Manually` to the desired frequency." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:144 +msgid "" +"By default, the UAE Central Bank exchange rates web service is used. Several" +" other providers are available under the :guilabel:`Service` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:152 +msgid "" +"The :guilabel:`UAE - Payroll` module creates the necessary **salary rules** " +"in the Payroll app in compliance with the UAE rules and regulations. The " +"salary rules are linked to the corresponding accounts in the **chart of " +"accounts**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "The UAE Employee Payroll Structure." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:161 +msgid "Salary rules" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:163 +msgid "" +"To apply these rules to an employee's contract, go to " +":menuselection:`Payroll --> Contracts --> Contracts` and select the " +"employee's contract. In the :guilabel:`Salary Structure Type` field, select " +":guilabel:`UAE Employee`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst-1 +msgid "Select the Salary Structure Type to apply to the contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:171 +msgid "" +"Under the :guilabel:`Salary Information` tab, you can find details such as " +"the:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:173 +msgid ":guilabel:`Wage`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:174 +msgid ":guilabel:`Housing Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:175 +msgid ":guilabel:`Transportation Allowance`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:176 +msgid ":guilabel:`Other Allowances`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:177 +msgid "" +":guilabel:`Number of Days`: used to calculate the :ref:`end of service " +"provision <uae-end-of-service-provision>`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:181 +msgid "" +"**Leave deductions** are calculated using a salary rule linked to the " +"**unpaid leave** time-off type;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:183 +msgid "" +"Any other deductions or reimbursements are made *manually* using other " +"inputs;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:184 +msgid "" +"**Overtimes** are added *manually* by going to :menuselection:`Work Entries " +"--> Work Entries`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:185 +msgid "" +"**Salary attachments** are generated by going to :menuselection:`Contracts " +"--> Salary Attachments`. Then, :guilabel:`Create` an attachment and select " +"the :guilabel:`Employee` and the :guilabel:`Type (Attachment of Salary, " +"Assignment of Salary, Child Support)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:190 +msgid "" +"To prevent a rule from appearing on a paycheck, go to " +":menuselection:`Payroll --> Configuration --> Rules`. Click on " +":guilabel:`UAE Employee Payroll Structure`, select the rule to hide, and " +"uncheck :guilabel:`Appears on Payslip`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:197 +msgid "End of service provision" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:199 +msgid "" +"The provision is defined as the total monthly allowance *divided* by 30 and " +"then *multiplied* by the number of days set in the field :guilabel:`Number " +"of days` at the bottom of a contract's form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:202 +msgid "" +"The provision is then calculated via a salary rule associated with two " +"accounts: the **End Of Service Indemnity (Expense account)** and the **End " +"of Service Provision (Non-current Liabilities account)**. The latter is used" +" to pay off the **end of service amount** by settling it with the **payables" +" account**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:208 +msgid "" +"The end of service amount is calculated based on the gross salary and the " +"start and end dates of the employee’s contract." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:214 +msgid "" +"The UAE localization package allows the generation of invoices in English, " +"Arabic, or both. The localization also includes a line to display the **VAT " +"amount** per line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:3 +msgid "United Kingdom" +msgstr "สหราชอาณาจักร" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:8 +msgid "" +":ref:`Install <general/install>` the :guilabel:`UK - Accounting` and the " +":guilabel:`UK - Accounting Reports` modules to get all the features of the " +"UK localization." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:17 +msgid ":guilabel:`UK - Accounting`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:18 +msgid "`l10n_uk`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:19 +msgid "CT600-ready chart of accounts" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:20 +msgid "VAT100-ready tax structure" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:21 +msgid "Infologic UK counties listing" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:22 +msgid ":guilabel:`UK - Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:23 +msgid "`l10n_uk_reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:24 +msgid "Accounting reports for the UK" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:25 +msgid "Allows sending the tax report via the MTD-VAT API to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst-1 +msgid "Odoo uk packages" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:32 +msgid "Only UK-based companies can submit reports to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:33 +msgid "" +"Installing the module :guilabel:`UK - Accounting Reports` installs all two " +"modules at once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:36 +msgid "" +"`HM Revenue & Customs <https://www.gov.uk/government/organisations/hm-" +"revenue-customs/>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:37 +msgid "" +"`Overview of Making Tax Digital " +"<https://www.gov.uk/government/publications/making-tax-digital/overview-of-" +"making-tax-digital/>`_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:43 +msgid "" +"The UK chart of accounts is included in the :guilabel:`UK - Accounting` " +"module. Go to :menuselection:`Accounting --> Configuration --> Accounting: " +"Chart of Accounts` to access it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:46 +msgid "" +"Setup your :abbr:`CoA (chart of accounts)` by going to " +":menuselection:`Accounting --> Configuration --> Settings --> Accounting " +"Import section` and choose to :guilabel:`Review Manually` or " +":guilabel:`Import (recommended)` your initial balances." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:53 +msgid "" +"As part of the localization module, UK taxes are created automatically with " +"their related financial accounts and configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:56 +msgid "" +"Go to :menuselection:`Accounting --> Configuration --> Settings --> Taxes` " +"to update the :guilabel:`Default Taxes`, the :guilabel:`Tax Return " +"Periodicity` or to :guilabel:`Configure your tax accounts`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:60 +msgid "" +"To edit existing taxes or to :guilabel:`Create` a new tax, go to " +":menuselection:`Accounting --> Configuration --> Accounting: Taxes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:64 +msgid ":doc:`taxes <../accounting/taxes>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:65 +msgid "" +"Tutorial: `Tax report and return <https://www.odoo.com/slides/slide/tax-" +"report-and-return-1719?fullscreen=1>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:69 +msgid "Making Tax Digital (MTD)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:71 +msgid "" +"In the UK, all VAT-registered businesses have to follow the MTD rules by " +"using software to submit their VAT returns." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:74 +msgid "" +"The **UK - Accounting Reports** module enables you to comply with the `HM " +"Revenue & Customs <https://www.gov.uk/government/organisations/hm-revenue-" +"customs/>`_ requirements regarding `Making Tax Digital " +"<https://www.gov.uk/government/publications/making-tax-digital/overview-of-" +"making-tax-digital/>`_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:80 +msgid "" +"If your periodic submission is more than three months late, it is no longer " +"possible to submit it through Odoo, as Odoo only retrieves open bonds from " +"the last three months. Your submission has to be done manually by contacting" +" HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:87 +msgid "Register your company to HMRC before the first submission" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:89 +msgid "" +"Go to :menuselection:`Accounting --> Reporting --> Tax report` and click on " +":guilabel:`Connect to HMRC`. Enter your company information on the HMRC " +"platform. You only need to do it once." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 +msgid "Periodic submission to HMRC" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:99 +msgid "" +"Import your obligations HMRC, filter on the period you want to submit, and " +"send your tax report by clicking :guilabel:`Send to HMRC`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:103 +msgid "Periodic submission to HMRC for multi-company" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:105 +msgid "" +"Only one company and one user can connect to HMRC simultaneously. If several" +" UK-based companies are on the same database, the user who submits the HMRC " +"report must follow these instructions before each submission:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:109 +msgid "Log into the company for which the submission has to be done." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:110 +msgid "" +"Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, " +"click :guilabel:`Manage Users`. Select the user who is connected to HMRC." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:112 +msgid "" +"Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset " +"Authentication Credentials` or :guilabel:`Remove Authentication Credentials`" +" button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:114 +msgid "" +"You can now :ref:`register your company to HMRC <uk_localization/hmrc-" +"registration>` and submit the tax report for this company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 +msgid "Repeat the steps for other companies' HMRC submissions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:119 +msgid "" +"During this process, the :guilabel:`Connect to HMRC` button no longer " +"appears for other UK-based companies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:3 +msgid "Vietnam" +msgstr "ประเทศเวียดนาม" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:6 +msgid "Add Vietnamese QR banking codes to invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:8 +msgid "" +"Vietnamese QR banking is a payment service platform that allows customers to" +" make instant domestic payments to individuals and merchants in Vietnamese " +"dong via online and mobile banking." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst-1 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:18 +msgid "Vietnamese QR banking bank account configuration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:20 +msgid "" +"Go to :menuselection:`Contacts --> Configuration --> Bank Accounts` and " +"select the bank account for which you want to activate Vietnamese QR " +"banking. Set the :guilabel:`Bank Identifier Code` on the bank. Then set the " +":guilabel:`Proxy Type` and fill in the :guilabel:`Proxy Value` field " +"depending on the type you chose." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:26 +msgid "" +"The account holder's country must be set to Vietnam on its contact form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:46 +msgid "Issue invoices with Vietnamese QR banking QR codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:54 +msgid "" +"Ensure that the :guilabel:`Recipient Bank` is the one you configured, as " +"Odoo uses this field to generate the Vietnamese QR banking QR code." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:5 +msgid "Payment providers (credit cards, online payments)" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:27 +msgid "" +"Odoo embeds several **payment providers** that allow your customers to pay " +"on their *Customer Portals* or your *eCommerce website*. They can pay sales " +"orders, invoices, or subscriptions with recurring payments with their " +"favorite payment methods such as **Credit Cards**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:31 +msgid "" +"Offering several payment methods increases the chances of getting paid in " +"time, or even immediately, as you make it more convenient for your customers" +" to pay with the payment method they prefer and trust." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "" +"Pay online in the customer portal and select which payment provider to use." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:40 +msgid "" +"Odoo apps delegate the handling of sensitive information to the certified " +"payment provider so that you don't ever have to worry about PCI compliance." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:43 +msgid "" +"This means that no sensitive information (such as credit card numbers) is " +"stored on Odoo servers or Odoo databases hosted elsewhere. Instead, Odoo " +"apps use a unique reference number to the data stored safely in the payment " +"providers' systems." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:50 +msgid "Supported payment providers" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:52 +msgid "" +"From an accounting perspective, we can distinguish two types of payment " +"providers: the payment providers that are third-party services and require " +"you to follow another accounting workflow, and the payments that go directly" +" on the bank account and follow the usual reconciliation workflow." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:59 +msgid "Online payment providers" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:67 +msgid "Payment flow from" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:68 +msgid ":ref:`Tokenization <payment_providers/features/tokenization>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:69 +msgid ":ref:`Manual capture <payment_providers/features/manual_capture>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:70 +msgid ":ref:`Refunds <payment_providers/features/refund>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:71 +msgid ":ref:`Express checkout <payment_providers/features/express_checkout>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:72 +msgid ":doc:`Adyen <payment_providers/adyen>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:73 +#: ../../content/applications/finance/payment_providers.rst:91 +#: ../../content/applications/finance/payment_providers.rst:127 +#: ../../content/applications/finance/payment_providers.rst:139 +msgid "Odoo" +msgstr "Odoo" + +#: ../../content/applications/finance/payment_providers.rst:74 +#: ../../content/applications/finance/payment_providers.rst:92 +#: ../../content/applications/finance/payment_providers.rst:104 +#: ../../content/applications/finance/payment_providers.rst:128 +#: ../../content/applications/finance/payment_providers.rst:140 +#: ../../content/applications/finance/payment_providers.rst:143 +msgid "|V|" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:75 +#: ../../content/applications/finance/payment_providers.rst:76 +#: ../../content/applications/finance/payment_providers.rst:130 +#: ../../content/applications/finance/payment_providers.rst:142 +msgid "Full and partial" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:78 +msgid "" +":doc:`Amazon Payment Services <payment_providers/amazon_payment_services>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:79 +#: ../../content/applications/finance/payment_providers.rst:85 +#: ../../content/applications/finance/payment_providers.rst:97 +#: ../../content/applications/finance/payment_providers.rst:103 +#: ../../content/applications/finance/payment_providers.rst:109 +#: ../../content/applications/finance/payment_providers.rst:115 +#: ../../content/applications/finance/payment_providers.rst:121 +#: ../../content/applications/finance/payment_providers.rst:133 +msgid "The provider website" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:84 +msgid ":doc:`AsiaPay <payment_providers/asiapay>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:90 +msgid ":doc:`Authorize.Net <payment_providers/authorize>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:93 +#: ../../content/applications/finance/payment_providers.rst:94 +#: ../../content/applications/finance/payment_providers.rst:129 +#: ../../content/applications/finance/payment_providers.rst:141 +msgid "Full only" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:96 +msgid ":doc:`Buckaroo <payment_providers/buckaroo>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:102 +msgid ":doc:`Flutterwave <payment_providers/flutterwave>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:108 +msgid ":doc:`Mercado Pago <payment_providers/mercado_pago>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:114 +msgid ":doc:`Mollie <payment_providers/mollie>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:120 +msgid ":doc:`PayPal <payment_providers/paypal>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:126 +msgid ":doc:`Razorpay <payment_providers/razorpay>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:132 +msgid ":doc:`SIPS <payment_providers/sips>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:138 +msgid ":doc:`Stripe <payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:148 +msgid "" +"Some of these online payment providers can also be added as :doc:`bank " +"accounts <../finance/accounting/bank>`, but this is **not** the same process" +" as adding them as payment providers. Payment providers allow customers to " +"pay online, and bank accounts are added and configured on your Accounting " +"app to do a bank reconciliation, which is an accounting control process." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:155 +msgid "" +"In addition to the regular payment providers that integrate with an API such" +" as Stripe, PayPal, or Adyen, Odoo bundles the :doc:`Demo payment provider " +"<payment_providers/demo>`. This payment provider allows you to make demo " +"payments to test business flows involving online payments. No credentials " +"are required as the demo payments are fake." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:163 +msgid "Bank payments" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid ":doc:`Wire Transfer <payment_providers/wire_transfer>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid "" +"When selected, Odoo displays your payment information with a payment " +"reference. You have to approve the payment manually once you have received " +"it on your bank account." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid ":doc:`SEPA Direct Debit <../finance/accounting/payments/batch_sdd>`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:0 +msgid "" +"Your customers can make a bank transfer to register a SEPA Direct Debit " +"mandate and get their bank account charged directly." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:177 +msgid "" +"Some payment providers support additional features for the payment flow. " +"Refer to the :ref:`table above <payment_providers/online_providers>` to " +"check if your payment provider supports these features." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:184 +msgid "Tokenization" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:186 +msgid "" +"If your payment provider supports this feature, customers can choose to save" +" their card for later. A **payment token** is created in Odoo and can be " +"used as a payment method for subsequent payments without having to enter the" +" card details again. This is particularly useful for the eCommerce " +"conversion rate and for subscriptions that use recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:191 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Allow Saving Payment " +"Methods` checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:195 +msgid "" +"You remain fully PCI-compliant when you enable this feature because Odoo " +"does not store the card details directly. Instead, it creates a payment " +"token that only holds a reference to the card details stored on the payment " +"provider's server." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:202 +msgid "Manual capture" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:204 +msgid "" +"If your payment provider supports this feature, you can authorize and " +"capture payments in two steps instead of one. When you authorize a payment, " +"the funds are reserved on the customer's payment method but they are not " +"immediately charged. The charge is only made when you manually capture the " +"payment later on. You can also void the authorization to release the " +"reserved funds; this is equivalent to a regular cancellation. Capturing " +"payments manually can prove itself useful in many situations:" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:211 +msgid "" +"Receive the payment confirmation and wait until the order is shipped to " +"capture the payment." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:212 +msgid "" +"Review and verify that orders are legitimate before the payment is completed" +" and the fulfillment process starts." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:214 +msgid "" +"Avoid potentially high processing fees for cancelled payments: payment " +"providers will not charge you for voiding an authorization." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:216 +msgid "" +"Hold a security deposit to return later, minus any deductions (e.g., after a" +" damage)." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:218 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Capture Amount Manually`" +" checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:221 +msgid "" +"To capture the payment after it was authorized, go to the related sales " +"order or invoice and click on the :guilabel:`CAPTURE TRANSACTION` button. To" +" release the funds, click on the :guilabel:`VOID TRANSACTION` button." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:225 +msgid "" +"If your provider supports partial capture, you can select to capture only a " +"**partial amount** of the full amount. The **remaining (uncaptured) amount**" +" can either be voided or partially captured again later." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:230 +msgid "" +"Some payment providers support capturing only part of the authorized amount." +" The remaining amount can then be either captured or voided. These providers" +" have the value **Full and partial** in the :ref:`table above " +"<payment_providers/online_providers>`. The providers that only support " +"capturing or voiding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:234 +msgid "" +"The funds are likely not reserved forever. After a certain time, they may be" +" automatically released back to the customer's payment method. Refer to your" +" payment provider's documentation for the exact reservation duration." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:237 +msgid "" +"Odoo does not support this feature for all payment providers but some allow " +"the manual capture from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:243 +msgid "Refunds" +msgstr "การคืนเงิน" + +#: ../../content/applications/finance/payment_providers.rst:245 +msgid "" +"If your payment provider supports this feature, you can refund payments " +"directly from Odoo. It does not need to be enabled first. To refund a " +"customer payment, navigate to it and click on the :guilabel:`REFUND` button." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:250 +msgid "" +"Some payment providers support refunding only part of the amount. The " +"remaining amount can then optionally be refunded too. These providers have " +"the value **Full and partial** in the :ref:`table above " +"<payment_providers/online_providers>`. The providers that only support " +"refunding the full amount have the value **Full only**." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:254 +msgid "" +"Odoo does not support this feature for all payment providers but some allow " +"to refund payments from their website interface." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:260 +msgid "Express checkout" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:262 +msgid "" +"If your payment provider supports this feature, customers can use the " +"**Google Pay** and **Apple Pay** buttons to pay their eCommerce orders in " +"one click without filling the contact form. Using one of those buttons, " +"customers go straight from the cart to the confirmation page, stopping by " +"the payment form of Google or Apple to validate the payment." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:267 +msgid "" +"Enable this feature by navigating to the :guilabel:`Configuration` tab from " +"your payment provider and by ticking the :guilabel:`Allow Express Checkout` " +"checkbox." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:271 +msgid "" +"All prices shown in the express checkout payment form are always taxes " +"included." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:279 +msgid "" +"Each provider has its specific configuration flow, depending on :ref:`which " +"feature is available <payment_providers/online_providers>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:285 +msgid "Add a new payment provider" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:287 +msgid "" +"To add a new payment provider and make it available to your customers, go to" +" :menuselection:`Accounting --> Configuration --> Payment Providers`, look " +"for your payment provider, install the related module, and activate it. To " +"do so, open the payment provider and change its state from *Disabled* to " +"*Enabled*." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "" +"Click on install, then on activate to make the payment provider available on" +" Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:297 +msgid "" +"We recommend using the *Test Mode* on a duplicated database or a test " +"database. The Test Mode is meant to be used with your test/sandbox " +"credentials, but Odoo generates Sales Orders and Invoices as usual. It isn't" +" always possible to cancel an invoice, and this could create some issues " +"with your invoices numbering if you were to test your payment providers on " +"your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:305 +#: ../../content/applications/finance/payment_providers/adyen.rst:25 +#: ../../content/applications/finance/payment_providers/alipay.rst:18 +#: ../../content/applications/finance/payment_providers/authorize.rst:15 +#: ../../content/applications/finance/payment_providers/mollie.rst:14 +#: ../../content/applications/finance/payment_providers/sips.rst:15 +msgid "Credentials tab" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:307 +msgid "" +"If not done yet, go to the online payment provider website, create an " +"account, and make sure to have the credentials required for third-party use." +" Odoo requires these credentials to communicate with the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:311 +msgid "" +"The form in this section is specific to the payment provider you are " +"configuring. Please refer to the related documentation for more information." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:317 +#: ../../content/applications/finance/payment_providers/authorize.rst:38 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:319 +msgid "" +"You can change the payment provider's front-end appearance by modifying its " +"name under the **Displayed as** field, and the supported credit card icons " +"displayed under the **Supported Payment Methods** field." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:326 +msgid "Currencies" +msgstr "สกุลเงิน" + +#: ../../content/applications/finance/payment_providers.rst:328 +msgid "" +"All payment providers have a different list of available currencies. They " +"are preconfigured and available in the :guilabel:`Configuration` tab. They " +"serve as a first filter during payment operations, i.e. the payment provider" +" is not displayed as available for payment if the currency is not in the " +"supported list." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:334 +msgid "" +"As there might be errors, updates, and unknowns in the lists of available " +"currencies, it is possible to add or remove currencies." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:337 +msgid "" +"If the list of supported currencies is empty, it either means the list is " +"too long to be displayed, or Odoo does not have information on that payment " +"provider. The payment provider remains available, even though it is possible" +" the payment will be refused at a later stage should the currency not be " +"supported. This field is required if the user needs to select a currency " +"when setting up their payment provider account." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:346 +msgid "Countries" +msgstr "ประเทศ" + +#: ../../content/applications/finance/payment_providers.rst:348 +msgid "" +"Restrict the use of the payment provider to a selection of countries. Leave " +"this field blank to make the payment provider available in all countries." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:352 +msgid "Maximum Amount" +msgstr "จำนวนสูงสุด" + +#: ../../content/applications/finance/payment_providers.rst:354 +msgid "" +"Restrict the maximum amount that can be paid with the selected provider. " +"Leave this field to `0.00` to make the payment provider available regardless" +" of the payment amount." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:358 +msgid "" +"This feature is not intended to work on pages which allow the customer to " +"update the payment amount. For example, the **Donation** snippet of the " +"Website app, and the **Checkout** page of the **eCommerce** app when paid " +"delivery methods are enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:365 +msgid "Payment journal" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:367 +msgid "" +"The **Payment journal** selected for your payment provider must be a *Bank* " +"journal." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:372 +msgid "Publish on the website" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:374 +msgid "" +"By default, payment providers are *unpublished*, which means that only " +"internal users can see them on the website. Your customers cannot make " +"payments through an unpublished provider but they can still manage " +":dfn:`(delete and assign to a subscription)` their already existing tokens " +"linked to such an provider. This conveniently allows you to test an provider" +" while preventing making payments and registering new tokens." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:380 +msgid "" +"Click on the :guilabel:`Publish` button located in the top right corner of " +"the provider's form to publish it on the website and make it available to " +"your customers. Click on the :guilabel:`Unpublish` button to unpublish it." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:385 +msgid "" +"Payment providers are automatically published and unpublished when you " +"respectively change their state to `enabled` and `test`." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:391 +msgid "Accounting perspective" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:393 +msgid "" +"The **Bank Payments** that go directly to one of your bank accounts follow " +"their usual reconciliation workflows. However, payments recorded with " +"**Online Payment Providers** require you to consider how you want to record " +"your payments' journal entries. We recommend you to ask your accountant for " +"advice." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:398 +msgid "" +"You need to select a *Payment Journal* on your provider configuration to " +"record the payments, on a **Outstanding Account**. The Journal's **type** " +"must be *Bank Journal*." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:401 +msgid "" +"You can use a single journal for many payment methods. And for each payment " +"method, you can either:" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:403 +msgid "" +"Define an **Accounting Account** to separate these payments from another " +"payment method." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:404 +msgid "" +"Leave blank to fallback on the default account, which you can see or change " +"in the settings." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst-1 +msgid "A bank journal in the \"Incoming Payments Tab\"." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:410 +msgid "" +"You can have the same bank account for the whole company, or for some " +"journals only, or a single payment method... What best suit your needs." +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:414 +msgid ":doc:`payment_providers/wire_transfer`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:415 +msgid ":doc:`payment_providers/adyen`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:416 +msgid ":doc:`payment_providers/alipay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:417 +msgid ":doc:`payment_providers/authorize`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:418 +msgid ":doc:`payment_providers/asiapay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:419 +msgid ":doc:`payment_providers/buckaroo`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:420 +msgid ":doc:`payment_providers/demo`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:421 +msgid ":doc:`payment_providers/mercado_pago`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:422 +msgid ":doc:`payment_providers/mollie`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:423 +msgid ":doc:`payment_providers/ogone`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:424 +msgid ":doc:`payment_providers/paypal`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:425 +msgid ":doc:`payment_providers/razorpay`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:426 +msgid ":doc:`payment_providers/sips`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:427 +msgid ":doc:`payment_providers/stripe`" +msgstr "" + +#: ../../content/applications/finance/payment_providers.rst:428 +msgid ":doc:`../websites/ecommerce/checkout_payment_shipping/payments`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:3 +msgid "Adyen" +msgstr "Adyen" + +#: ../../content/applications/finance/payment_providers/adyen.rst:5 +msgid "" +"`Adyen <https://www.adyen.com/>`_ is a Dutch company that offers several " +"online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:9 +#: ../../content/applications/finance/payment_providers/adyen.rst:20 +#: ../../content/applications/finance/payment_providers/alipay.rst:15 +#: ../../content/applications/finance/payment_providers/authorize.rst:12 +#: ../../content/applications/finance/payment_providers/demo.rst:12 +#: ../../content/applications/finance/payment_providers/mollie.rst:11 +#: ../../content/applications/finance/payment_providers/ogone.rst:9 +#: ../../content/applications/finance/payment_providers/paypal.rst:86 +#: ../../content/applications/finance/payment_providers/sips.rst:12 +#: ../../content/applications/finance/payment_providers/stripe.rst:12 +msgid ":ref:`payment_providers/add_new`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:10 +#: ../../content/applications/finance/payment_providers/adyen.rst:163 +#: ../../content/applications/finance/payment_providers/alipay.rst:39 +#: ../../content/applications/finance/payment_providers/asiapay.rst:50 +#: ../../content/applications/finance/payment_providers/authorize.rst:51 +#: ../../content/applications/finance/payment_providers/buckaroo.rst:37 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:44 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:39 +#: ../../content/applications/finance/payment_providers/mollie.rst:31 +#: ../../content/applications/finance/payment_providers/paypal.rst:121 +#: ../../content/applications/finance/payment_providers/razorpay.rst:54 +#: ../../content/applications/finance/payment_providers/sips.rst:32 +#: ../../content/applications/finance/payment_providers/stripe.rst:133 +msgid ":doc:`../payment_providers`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:13 +msgid "" +"Adyen works only with customers processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1.000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:22 +msgid "" +"First, reach Adyen support to enable :guilabel:`multiple partial capture` " +"for you." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:27 +msgid "" +"Odoo needs your **API Credentials** to connect with your Adyen account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:29 +msgid "" +"**Merchant Account**: The code of the merchant account to use with Adyen." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:30 +msgid "" +":ref:`API Key <adyen/api_and_client_keys>`: The API key of the webservice " +"user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:31 +msgid "" +":ref:`Client Key <adyen/api_and_client_keys>`: The client key of the " +"webservice user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:32 +msgid ":ref:`HMAC Key <adyen/hmac_key>`: The HMAC key of the webhook." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:33 +msgid "" +":ref:`Checkout API URL <adyen/urls>`: The base URL for the Checkout API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:34 +msgid "" +":ref:`Recurring API URL <adyen/urls>`: The base URL for the Recurring API " +"endpoints." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:36 +msgid "" +"You can copy your credentials from your Adyen account, and paste them in the" +" related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:40 +msgid "" +"If you are trying Adyen as a test, with an Adyen *test account*, head to " +":menuselection:`Accounting --> Configuration --> Payment Providers`. There, " +"click on :guilabel:`Adyen`, enable :guilabel:`Test Mode` and enter your " +"credentials in the :guilabel:`Credentials` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:48 +msgid "API Key and Client Key" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:50 +msgid "" +"In order to retrieve the API Key and the Client Key, log into your Adyen " +"account, go to :menuselection:`Developers --> API Credentials`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:53 +msgid "If you already have an API user, open it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:54 +msgid "If you don't have an API user yet, click on **Create new credential**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:56 +msgid "" +"Go to :menuselection:`Server settings --> Authentification` and copy or " +"generate your **API Key**. Be careful to copy your API key as you'll not be " +"allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:60 +msgid "" +"Now, head to :menuselection:`Client settings --> Authentification` and cody " +"or generate your **Client Key**. This is also the place where you can " +":ref:`allow payments to be made from your website <adyen/allowed_origins>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:67 +msgid "HMAC key" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:69 +msgid "" +"In order to retrieve the HMAC Key, you'll need to configure a `Standard " +"Notification` webhook. For this, log into your Adyen account then go to " +":menuselection:`Developers --> Webhooks --> Add webhook --> Add Standard " +"notification`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Configure a webhook." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:77 +msgid "" +"There, in :menuselection:`General --> Server configuration --> URL`, enter " +"your server address followed by `/payment/adyen/notification`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Enter the notification URL." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:84 +msgid "" +"Then enter :menuselection:`Security --> HMAC Key --> Generate`. Be careful " +"to copy the key as you will not be allowed to do it later without generating" +" a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Generate a HMAC key and save it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:91 +msgid "You have to save the webhook to finalize its creation." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:96 +msgid "API URLs" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:98 +msgid "" +"All Adyen API URLs include a customer area-specific prefix generated by " +"Adyen. To configure the URLs, proceed as follows:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:101 +msgid "" +"Log into your Adyen account, then go to :menuselection:`Developers --> API " +"URLs`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:102 +msgid "" +"Copy the :guilabel:`Prefix` for your live Customer area (i.e., **data " +"center**) and save it for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:0 +msgid "Copy the prefix for the Adyen APIs" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:108 +msgid "" +"In Odoo, :ref:`navigate to the payment provider Adyen " +"<payment_providers/add_new>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:109 +msgid "" +"In the :guilabel:`Checkout API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-checkout-live.adyenpayments.com/checkout`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:112 +msgid "" +"In the :guilabel:`Recurring API URL` field, enter the following URL and " +"replace `yourprefix` with the prefix you previously saved: " +"`https://yourprefix-pal-live.adyenpayments.com/pal/servlet/Recurring`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:117 +msgid "" +"If you are trying Adyen as a test, you can use the following URLs instead:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:119 +msgid ":guilabel:`Checkout API URL`: `https://checkout-test.adyen.com`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:120 +msgid "" +":guilabel:`Recurring API URL`: `https://pal-" +"test.adyen.com/pal/servlet/Recurring`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:123 +msgid "Adyen Account" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:128 +msgid "Allow payments from a specific origin" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:130 +msgid "" +"To allow payment originated from your website, follow the steps in " +":ref:`adyen/api_and_client_keys` to navigate to your API user and go to " +":menuselection:`Add allowed origins`, then add the URLs from where payments " +"will be made (the URLs of the servers hosting your Odoo instances)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Allows payments originated from a specific domain." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:139 +#: ../../content/applications/finance/payment_providers/authorize.rst:41 +msgid "Place a hold on a card" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:141 +msgid "" +"Adyen allows you to capture an amount manually instead of having an " +"immediate capture." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:143 +msgid "" +"To set it up, enable the **Capture Amount Manually** option on Odoo, as " +"explained in the :ref:`payment providers documentation " +"<payment_providers/features/manual_capture>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:146 +msgid "" +"Then, open your Adyen Merchant Account, go to :menuselection:`Account --> " +"Settings`, and set the **Capture Delay** to **manual**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst-1 +msgid "Capture Delay settings in Adyen" +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:154 +msgid "" +"If you configure Odoo to capture amounts manually, make sure to set the " +"**Capture Delay** to **manual** on Adyen. Otherwise, the transaction will be" +" blocked in the authorized state in Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/adyen.rst:159 +msgid "" +"After **7 days**, if the transaction has not been captured yet, the customer" +" has the right to **revoke** it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:3 +msgid "Alipay" +msgstr "Alipay" + +#: ../../content/applications/finance/payment_providers/alipay.rst:5 +msgid "" +"`Alipay <https://www.alipay.com/>`_ is an online payments platform " +"established in China by Alibaba Group." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:9 +msgid "" +"The provider Alipay is deprecated. It is recommended to use :doc:`asiapay` " +"instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:20 +msgid "" +"Odoo needs your **API Credentials** to connect with your Alipay account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:22 +msgid "" +"**Account**: Depending on where you are situated - `Express Checkout` if " +"your are a Chinese Merchant. - `Cross-border` if you are not." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:25 +msgid "" +"**Alipay Seller Email**: Your public Alipay partner email (for express " +"checkout only)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:26 +msgid "" +"**Merchant Partner ID**: The public partner ID solely used to identify the " +"account with Alipay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:27 +msgid "**MD5 Signature Key**: The signature key." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:29 +msgid "" +"You can copy your credentials from your Alipay account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:32 +msgid "" +"To retrieve them, log into your Alipay account, they are on the front page." +msgstr "" + +#: ../../content/applications/finance/payment_providers/alipay.rst:35 +msgid "" +"If you are trying Alipay as a test, in the *sandbox*, change the **State** " +"to *Test Mode*. We recommend doing this on a test Odoo database, rather than" +" on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:3 +msgid "Amazon Payment Services" +msgstr "บริการชำระเงินของ Amazon" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:5 +msgid "" +"`Amazon Payment Services <https://paymentservices.amazon.com/>`_ or APS is " +"an online payment provider established in Dubai offering several online " +"payment options." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:11 +msgid "Configuration on APS Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:13 +msgid "" +"Log into your `Amazon Payment Services Dashboard " +"<https://fort.payfort.com/>`_ and go to :menuselection:`Integration Settings" +" --> Security Settings`. Generate the :guilabel:`Access Code` if none has " +"been generated yet. Copy the values of the :guilabel:`Merchant Identifier`, " +":guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and :guilabel:`SHA " +"Response Phrase` fields, and save them for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:18 +msgid "" +"Enter your Odoo database URL in the :guilabel:`Origin URL`, for example: " +"`https://yourcompany.odoo.com/`. Then, click on :guilabel:`Save Changes`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:20 +msgid "" +"Navigate to :menuselection:`Integration Settings --> Technical Settings` and" +" click on :guilabel:`Redirection`. Make sure :guilabel:`Status` is set to " +"`Active` and select your preferred payment methods underneath in " +":guilabel:`Payment Options`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "" +"Set :guilabel:`Send Response Parameters` to :guilabel:`Yes` and enter your " +"database URL followed by `/payment/aps/return` in the :guilabel:`Redirection" +" URL`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "For example `https://yourcompany.odoo.com/payment/aps/return`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "" +"Enter your database URL followed by `/payment/aps/webhook` in the " +":guilabel:`Direct Transaction Feedback` and :guilabel:`Notification URL` " +"fields." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "For example `https://yourcompany.odoo.com/payment/aps/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:0 +msgid "Click on :guilabel:`Save Changes`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:30 +msgid "" +"Under :menuselection:`Integration Settings --> Payment Page Template` you " +"can customize the look and feel of the Amazon Payment Services payment page " +"(where customers fill out their credit card details during payment)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:39 +msgid "" +":ref:`Navigate to the payment provider Amazon Payment Services " +"<payment_providers/add_new>`, change its state to :guilabel:`Enabled`, and " +"make sure it is :guilabel:`Published`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:41 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Merchant " +"Identifier`, :guilabel:`Access Code`, :guilabel:`SHA Request Phrase` and " +":guilabel:`SHA Response Phrase` with the values you saved at the step " +":ref:`payment_providers/aps/configure-dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:44 +#: ../../content/applications/finance/payment_providers/asiapay.rst:47 +#: ../../content/applications/finance/payment_providers/flutterwave.rst:36 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 +#: ../../content/applications/finance/payment_providers/razorpay.rst:44 +msgid "Configure the rest of the options to your liking." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:3 +msgid "AsiaPay" +msgstr "AsiaPay" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:5 +msgid "" +"`AsiaPay <https://www.asiapay.com/>`_ is an online payments provider " +"established in Hong Kong and covering several Asian countries and payment " +"methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:11 +msgid "Configuration on AsiaPay Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:13 +msgid "" +"Log into AsiaPay Dashboard according to the account provided by AsiaPay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:15 +msgid "" +"`PayDollar <https://www.paydollar.com/b2c2/eng/merchant/index.jsp>`_: For " +"markets in HK, CN, MO, TW, SG, MY, IN, VN, NZ and AU" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:17 +msgid "" +"`PesoPay <https://www.pesopay.com/b2c2/eng/merchant/index.jsp>`_: For market" +" in PH" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:18 +msgid "" +"`SiamPay <https://www.siampay.com/b2c2/eng/merchant/index.jsp>`_: For market" +" in TH" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:19 +msgid "" +"`BimoPay <https://www.bimopay.com/b2c2/eng/merchant/index.jsp>`_: For market" +" in ID" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:21 +msgid "" +"Go to :menuselection:`Profile --> Account Information`. Copy the values of " +"the :guilabel:`Currency` and :guilabel:`Secure Hash` fields and save them " +"for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Go to :menuselection:`Profile --> Payment Account Settings` and enable the " +"option :guilabel:`Return Value Link (Datefeed)`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Enter your Odoo database URL followed by `/payment/asiapay/webhook` in the " +":guilabel:`Return Value Link (Datefeed)` text field. For example: " +"`https://yourcompany.odoo.com/payment/asiapay/webhook`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"Click on :guilabel:`Test` to check if the webhook is working correctly." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:29 +msgid "Click on :guilabel:`Update` to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:36 +msgid "" +":ref:`Navigate to the payment provider AsiaPay <payment_providers/add_new>` " +"and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"In the :guilabel:`Credentials` tab, choose the :guilabel:`Brand` of your " +"Asiapay account. Then fill in the :guilabel:`Merchant ID` and " +":guilabel:`Secure Hash Secret`, and the :guilabel:`Currency` in the " +":guilabel:`Configuration` tab with the values you saved at the step " +":ref:`payment_providers/asiapay/configure_dashboard`;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/asiapay.rst:0 +msgid "" +"By default, the payment provider AsiaPay is configured to verify the secret " +"hash with the hash function `SHA1`. If a different function is :ref:`set on " +"your account <payment_providers/asiapay/configure_dashboard>`, activate the " +":ref:`developer mode <developer-mode>` and set the same value to the field " +":guilabel:`Secure Hash Function` in the :guilabel:`Credentials` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:3 +msgid "Authorize.Net" +msgstr "Authorize.Net" + +#: ../../content/applications/finance/payment_providers/authorize.rst:5 +msgid "" +"`Authorize.Net <https://www.authorize.net>`_ is a United States-based online" +" payment solution provider, allowing businesses to accept **credit cards**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:17 +msgid "" +"Odoo needs your **API Credentials & Keys** to connect with your " +"Authorize.Net account, which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:20 +msgid "" +"**API Login ID**: The ID solely used to identify the account with " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:21 +msgid "**API Transaction Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:22 +msgid "**API Signature Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:23 +msgid "**API Client Key**" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:25 +msgid "" +"To retrieve them, log into your Authorize.Net account, go to " +":menuselection:`Account --> Settings --> Security Settings --> API " +"Credentials & Keys`, generate your **Transaction Key** and **Signature " +"Key**, and paste them on the related fields in Odoo. Then, click on " +"**Generate Client Key**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:31 +msgid "" +"To test Authorize.Net with a *sandbox* account, change the :guilabel:`State`" +" to :guilabel:`Test Mode`. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:34 +msgid "" +"If you use the :guilabel:`Test Mode` with a regular account, it results in " +"the following error: *The merchant login ID or password is invalid or the " +"account is inactive*." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:43 +msgid "" +"With Authorize.Net, you can enable the :ref:`manual capture " +"<payment_providers/features/manual_capture>`. If enabled, the funds are " +"reserved for 30 days on the customer's card, but not charged yet." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:48 +msgid "" +"After **30 days**, the transaction is **voided automatically** by " +"Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:54 +msgid "ACH payments (USA only)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:56 +msgid "" +":abbr:`ACH (automated clearing house)` is an electronic funds transfer " +"system used between bank accounts in the United States." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:62 +msgid "" +"To give customers the possibility to pay using ACH, `sign up for " +"Authorize.Net eCheck's service " +"<https://www.authorize.net/payments/echeck.html>`_. Once eCheck is " +"activated, duplicate the previously configured Authorize.Net payment " +"provider on Odoo by going to :menuselection:`Accounting --> Configuration " +"--> Payment Providers --> Authorize.net`. Then, click the cog icon " +"(:guilabel:`⛭`) and select :guilabel:`Duplicate`. Change the provider's name" +" to differentiate both versions (e.g., `Authorize.net - Banks`)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:69 +msgid "" +"Open the :guilabel:`Configuration` tab, set the :guilabel:`Allow Payments " +"From` field to :guilabel:`Bank Account (USA only)`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:72 +msgid "" +"When ready, change the provider's :guilabel:`State` to :guilabel:`Enabled` " +"for a regular account or :guilabel:`Test Mode` for a sandbox account." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:76 +msgid "Import an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:79 +msgid "Export from Authorize.Net" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:85 +msgid "" +"`Download the Excel import template " +"<https://docs.google.com/spreadsheets/d/1CMVtBWLLVIrUpYA92paw-" +"cL7-WdKLbaa/edit?usp=share_link&ouid=105295722917050444558&rtpof=true&sd=true>`_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:87 +msgid "To export a statement:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:89 +msgid "Log in to Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:90 +msgid "" +"Go to :menuselection:`Account --> Statements --> eCheck.Net Settlement " +"Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:91 +msgid "" +"Define an export range using an *opening* and *closing* batch settlement. " +"All transactions within the two batch settlements will be exported to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:93 +msgid "" +"Select all transactions within the desired range, copy them, and paste them " +"into the :guilabel:`Report 1 Download` sheet of the :ref:`Excel import " +"template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst-1 +msgid "Selecting Authorize.Net transactions to import" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst-1 +msgid "Settlement batch of an Authorize.Net statement" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:106 +msgid "" +"In this case, the first batch (01/01/2021) of the year belongs to the " +"settlement of 12/31/2020, so the **opening** settlement is from 12/31/2020." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:109 +msgid "Once the data is in the :guilabel:`Report 1 Download` sheet:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:111 +msgid "Go to the :guilabel:`Transaction Search` tab on Authorize.Net." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:112 +msgid "" +"Under the :guilabel:`Settlement Date` section, select the previously used " +"range of batch settlement dates in the :guilabel:`From:` and :guilabel:`To:`" +" fields and click :guilabel:`Search`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:114 +msgid "When the list has been generated, click :guilabel:`Download to File`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:115 +msgid "" +"In the pop-up window, select :guilabel:`Expanded Fields with CAVV " +"Response/Comma Separated`, enable :guilabel:`Include Column Headings`, and " +"click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:117 +msgid "" +"Open the text file, select :guilabel:`All`, copy the data, and paste it into" +" the :guilabel:`Report 2 Download` sheet of the :ref:`Excel import template " +"<authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:119 +msgid "" +"Transit lines are automatically filled in and updated in the " +":guilabel:`transit for report 1` and :guilabel:`transit for report 2` sheets" +" of the :ref:`Excel import template <authorize-import-template>`. Make sure " +"all entries are present, and **if not**, copy the formula from previously " +"filled-in lines of the :guilabel:`transit for report 1` or :guilabel:`2` " +"sheets and paste it into the empty lines." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:126 +msgid "" +"To get the correct closing balance, **do not remove** any line from the " +"Excel sheets." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:129 +msgid "Import into Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:131 +msgid "To import the data into Odoo:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:133 +msgid "Open the :ref:`Excel import template <authorize-import-template>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:134 +msgid "" +"Copy the data from the :guilabel:`transit for report 2` sheet and use *paste" +" special* to only paste the values in the :guilabel:`Odoo Import to CSV` " +"sheet." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:136 +msgid "" +"Look for *blue* cells in the :guilabel:`Odoo Import to CSV` sheet. These are" +" chargeback entries without any reference number. As they cannot be imported" +" as such, go to :menuselection:`Authorize.Net --> Account --> Statements -->" +" eCheck.Net Settlement Statement`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:139 +msgid "Look for :guilabel:`Charge Transaction/Chargeback`, and click it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:140 +msgid "" +"Copy the invoice description, paste it into the :guilabel:`Label` cell of " +"the :guilabel:`Odoo Import to CSV` sheet, and add `Chargeback /` before the " +"description." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:142 +msgid "" +"If there are multiple invoices, add a line into the :ref:`Excel import " +"template <authorize-import-template>` for each invoice and copy/paste the " +"description into each respective :guilabel:`Label` line." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:147 +msgid "" +"For **combined chargeback/returns** in the payouts, create a new line in the" +" :ref:`Excel import template <authorize-import-template>` for each invoice." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:0 +msgid "Chargeback description" +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:155 +msgid "" +"Next, delete *zero transaction* and *void transaction* line items, and " +"change the format of the :guilabel:`Amount` column in the :guilabel:`Odoo " +"Import to CSV` sheet to *Number*." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:157 +msgid "" +"Go back to :menuselection:`eCheck.Net Settlement Statement --> Search for a " +"Transaction` and search again for the previously used batch settlements " +"dates." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:159 +msgid "" +"Verify that the batch settlement dates on eCheck.Net match the related " +"payments' dates found in the :guilabel:`Date` column of the :guilabel:`Odoo " +"Import to CSV`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:161 +msgid "" +"If it does not match, replace the date with the one from eCheck.Net. Sort " +"the column by *date*, and make sure the format is `MM/DD/YYYY`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:163 +msgid "" +"Copy the data - column headings included - from the :guilabel:`Odoo Import " +"to CSV` sheet, paste it into a new Excel file, and save it using the CSV " +"format." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:165 +msgid "" +"Open the Accounting app, go to :menuselection:`Configuration --> Journals`, " +"tick the :guilabel:`Authorize.Net` box, and click :menuselection:`Favorites " +"--> Import records --> Load file`. Select the CSV file and upload it into " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/authorize.rst:170 +msgid "" +"List of `eCheck.Net return codes " +"<https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001293>`_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:3 +msgid "Buckaroo" +msgstr "Buckaroo" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:5 +msgid "" +"`Buckaroo <https://www.buckaroo.eu/>`_ is a Dutch-based company that offers " +"several online payment possibilities." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:11 +msgid "Configuration on Buckaroo Plaza" +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:13 +msgid "" +"Log into `Buckaroo Plaza <https://plaza.buckaroo.nl>`_, go to " +":menuselection:`My Buckaroo --> Websites` and select the :guilabel:`Push " +"settings` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:15 +msgid "" +"Tick the :guilabel:`Enable Push Response` check box in the " +":guilabel:`Delayed and Push responses` section." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:17 +msgid "" +"Enter the URL of your Odoo database, followed by `/payment/buckaroo/webhook`" +" in both the :guilabel:`Push URI Success/Pending` and :guilabel:`Push URI " +"Failure` text fields. For example: " +"`https://yourcompany.odoo.com/payment/buckaroo/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:20 +msgid "Leave the other fields as they are and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:21 +msgid "" +"In the :guilabel:`General` tab, copy the website :guilabel:`Key` (i.e., the " +"key used to uniquely identify your website with Buckaroo) and save it for " +"later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:23 +msgid "" +"Go to :menuselection:`Configuration --> Security --> Secret key`, enter or " +":guilabel:`Generate` a :guilabel:`Secret key` and click :guilabel:`Save`. " +"Save the key for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:29 +msgid "" +":ref:`Navigate to the payment provider Buckaroo <payment_providers/add_new>`" +" and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:31 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Website Key` and " +":guilabel:`Secret Key` fields with the values you saved at the step " +":ref:`payment_providers/buckaroo/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/buckaroo.rst:34 +msgid "Configure the options in the other tabs to your liking." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:3 +msgid "Demo" +msgstr "สาธิต" + +#: ../../content/applications/finance/payment_providers/demo.rst:5 +msgid "" +"Odoo's **Demo Payment Provider** allows you to test business flows involving" +" online transactions without requiring real banking credentials." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:15 +msgid "Switch the state to :guilabel:`Test Mode`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:18 +msgid "Payment outcome" +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:20 +msgid "" +"Upon checkout or when paying a bill online, you can choose the payment " +"outcome when using the demo payment provider. To do so, click on the " +":guilabel:`Payment Status` drop-down menu and select the desired outcome." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst-1 +msgid "Payment status outcomes." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:29 +msgid "Transaction state" +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst:31 +msgid "" +"If you selected :guilabel:`Pending` as **payment outcome**, you can change " +"the state of the transaction straight from its form view. To access a " +"transaction's form view, activate the :ref:`developer mode <developer-" +"mode>`, and go to :menuselection:`Accounting / Website --> Configuration -->" +" Payment Transactions`. Then, change the status of a transaction by clicking" +" on the state bar (:guilabel:`Draft, Pending, Authorized, Confirmed, " +"Canceled, Error`)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/demo.rst-1 +msgid "Transaction's status bar." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:3 +msgid "Flutterwave" +msgstr "Flutterwave" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:5 +msgid "" +"`Flutterwave <https://flutterwave.com/>`_ is an online payments provider " +"established in Nigeria and covering several African countries and payment " +"methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:11 +msgid "Configuration on Flutterwave Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:13 +msgid "" +"Log into `Flutterwave Dashboard <https://dashboard.flutterwave.com/>`_ and " +"go to :menuselection:`Settings --> API`. Copy the values of the " +":guilabel:`Public Key` and :guilabel:`Secret Key` fields and save them for " +"later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:0 +msgid "" +"Go to :menuselection:`Settings --> Webhooks` and enter your Odoo database " +"URL followed by `/payment/flutterwave/webhook` in the :guilabel:`URL` text " +"field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:0 +msgid "" +"For example: `https://yourcompany.odoo.com/payment/flutterwave/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:19 +msgid "" +"Fill the :guilabel:`Secret hash` with a password that you generate and save " +"its value for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:20 +msgid "Make sure *all* the remaining checkboxes are ticked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:21 +msgid "Click on **Save** to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst-1 +msgid "Flutterwave settings" +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:31 +msgid "" +":ref:`Navigate to the payment provider Flutterwave " +"<payment_providers/add_new>` and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:33 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Public Key`, " +":guilabel:`Secret Key`, and :guilabel:`Webhook Secret` with the values you " +"saved at the step :ref:`payment_providers/flutterwave/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/flutterwave.rst:39 +msgid "" +"If you choose to allow saving payment methods, it is recommended to only " +"enable card payments from Flutterwave dashboard, as only cards can be saved " +"as payment tokens. To do so, go to your Flutterwave Dashboard and then to " +":menuselection:`Settings --> Account Settings`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:3 +msgid "Mercado Pago" +msgstr "Mercado Pago" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:5 +msgid "" +"`Mercado Pago <https://www.mercadopago.com/>`_ is an online payment provider" +" covering several countries, currencies and payment methods in Latin " +"America." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:11 +msgid "Configuration on Mercado Pago Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:13 +msgid "" +"Log into the `Mercado Pago Dashboard " +"<https://www.mercadopago.com.mx/developers/panel>`_ and select your " +"application or create a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:15 +msgid "" +"Select :guilabel:`Credenciales de producción` in the left part of the " +"application page, then select the industry, optionally enter your domain, " +"and click :guilabel:`Activar credenciales de producción`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:18 +msgid "Copy the :guilabel:`Access token` and save it for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:21 +msgid "" +"If you are trying Mercado Pago as a test, select :guilabel:`Credienciales de" +" prueba` in the left part of the application page, then copy the test " +":guilabel:`Access token`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst-1 +msgid "Production and testing credentials in Mercado Pago." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:32 +msgid "" +":ref:`Navigate to the payment provider Mercado Pago " +"<payment_providers/add_new>` and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:34 +msgid "" +"In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` " +"with the value you saved at the " +":ref:`payment_providers/mercado_pago/configure_dashboard` step." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:40 +msgid "" +"`Mercado Pago Odoo webinar <https://www.youtube.com/watch?v=CX8vPHMb1ic>`_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:3 +msgid "Mollie" +msgstr "Mollie" + +#: ../../content/applications/finance/payment_providers/mollie.rst:5 +msgid "" +"`Mollie <https://www.mollie.com/>`_ is an online payments platform " +"established in the Netherlands." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:16 +msgid "" +"Odoo needs your **API Credentials** to connect with your Mollie account, " +"which comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:18 +msgid "" +"**API Key**: The test or live API Key depending on the configuration of the " +"provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:20 +msgid "" +"You can copy your credentials from your Mollie account, and paste them in " +"the related fields under the **Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:23 +msgid "" +"To retrieve your API key, log into your Mollie account, go to " +":menuselection:`Developers --> API keys`, and copy your Test or Live **API " +"Key**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mollie.rst:27 +msgid "" +"If you are trying Mollie as a test, with the Test API key, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:3 +msgid "Ogone" +msgstr "Ogone" + +#: ../../content/applications/finance/payment_providers/ogone.rst:5 +msgid "" +"`Ogone <https://www.ingenico.com/>`_, also known as **Ingenico Payment " +"Services** is a France-based company that provides the technology involved " +"in secure electronic transactions." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:10 +msgid "" +"`Ogone's documentation <https://epayments-support.ingenico.com/get-" +"started/>`_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:13 +msgid "" +"The provider Ogone is deprecated. It is recommended to use :doc:`stripe` " +"instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:16 +msgid "Settings in Ogone" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:19 +msgid "Create an API user" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:21 +msgid "" +"Log into your Ogone account and head to the :guilabel:`Configuration` tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:23 +msgid "" +"You need to create an **API user** to be used in the creation of " +"transactions from Odoo. While you can use your main account to do so, using " +"an **API user** ensures that if the credentials used in Odoo are leaked, no " +"access to your Ogone configuration is possible. Additionally, passwords for " +"**API users** do not need to be updated regularly, unlike normal users." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:28 +msgid "" +"To create an **API user**, go to :menuselection:`Configuration --> Users` " +"and click on :guilabel:`New User`. The following fields must be configured:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:33 +msgid ":guilabel:`UserID`: you can choose anything you want." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:34 +msgid "" +":guilabel:`User's Name, E-mail and Timezone`: you can enter the information " +"you want." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:35 +msgid ":guilabel:`Profile`: should be set to :guilabel:`Admin`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:36 +msgid ":guilabel:`Special user for API`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:38 +msgid "" +"After the creation of the user, you are required to generate a password. " +"Save the password and **UserID**, as they will be required later on during " +"the setup." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:42 +msgid "" +"If you already have an user set up, make sure it is activated without any " +"error. If not, simply click the :guilabel:`Activate(Errors)` button to reset" +" the user." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:46 +msgid "Set up Ogone for Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:48 +msgid "" +"Ogone must now be configured to accept payments from Odoo. Head to " +":menuselection:`Configuration --> Technical Information --> Global Security " +"Parameters`, select :guilabel:`SHA-512` as :guilabel:`Hash Algorithm` and " +":guilabel:`UTF-8` as :guilabel:`character encoding`. Then, go to the " +":guilabel:`Data and Origin verification` tab of the same page and leave the " +"URL field of the :guilabel:`e-Commerce and Alias Gateway` section blank." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:55 +msgid "" +"If you need to use another algorithm, such as `sha-1` or `sha-256`, within " +"Odoo, activate the :ref:`developer mode <developer-mode>` and go to the " +"**Payment Providers** page in :menuselection:`Accounting --> Configuration " +"--> Payment Providers`. Click on :guilabel:`Ogone`, and in the " +":guilabel:`Credentials` tab, select the algorithm you wish to use in the " +":guilabel:`Hash function` field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:61 +msgid "" +"You are now required to generate **SHA-IN** passphrases. **SHA-IN** and " +"**SHA-OUT** passphrases are used to digitally sign the transaction requests " +"and responses between Odoo and Ogone. By using these secret passphrases and " +"the `sha-1` algorithm, both systems can ensure that the information they " +"receive from the other was not altered or tampered with." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:66 +msgid "" +"Enter the same **SHA-IN** passphrase in both :guilabel:`Checks for " +"e-Commerce & Alias Gateway` and :guilabel:`Checks for DirectLink and Batch " +"(Automatic)`. You can leave the IP address field blank." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:69 +msgid "" +"Your **SHA-IN** and **SHA-OUT** passphrases should be different, and between" +" 16 and 32 characters long. Make sure to use the same **SHA-IN** and **SHA-" +"OUT** passphrases throughout the entire Ogone configuration, as Odoo only " +"allows a single **SHA-IN** and single **SHA-OUT** passphrase." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:73 +msgid "" +"In order to retrieve the **SHA-OUT** key, log into your Ogone account, go to" +" :menuselection:`Configuration --> Technical Information --> Transaction " +"feedback --> All transaction submission modes`, and get or generate your " +"**API Key** and **Client Key**. Be careful to copy your API key as you’ll " +"not be allowed to get it later without generating a new one." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:78 +msgid "" +"When done, head to :menuselection:`Configuration --> Technical Information " +"--> Transaction Feedback` and check the following options:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:81 +msgid "" +"The :guilabel:`URL` fields for :guilabel:`HTTP redirection in the browser` " +"can be left empty, as Odoo will specify these URLs for every transaction " +"request." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:83 +msgid "" +":guilabel:`I would like to receive transaction feedback parameters on the " +"redirection URLs`: should be checked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:85 +msgid "" +":guilabel:`Direct HTTP server-to-server request`: should to be set to " +"`Online but switch to a deferred request when the online request fails`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:87 +msgid "" +"Both **URL** fields should contain the same following URL, with `<example>` " +"replaced by your database: `https://<example>/payment/ogone/return`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:90 +msgid "" +":guilabel:`Dynamic eCommerce Parameters` should contain the following " +"values: `ALIAS`, `AMOUNT`, `CARDNO`, `CN`, `CURRENCY`, `IP`, `NCERROR` " +"`ORDERID`, `PAYID`, `PM`, `STATUS`, `TRXDATE`. Other parameters can be " +"included (if you have another integration with Ogone that requires them), " +"but are not advised." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:94 +msgid "" +"In the :guilabel:`All transaction submission modes` section, fill out **SHA-" +"OUT** passphrase and disable `HTTP request for status change`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:97 +msgid "" +"To allow your customers to save their credit card credentials for future " +"use, head to :menuselection:`Configuration --> Alias --> My alias " +"information`. From this tab, you can configure how the user can have its " +"card details saved, for how long the information is saved, if a checkbox to " +"save the card information should be displayed, etc." +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:103 +#: ../../content/applications/finance/payment_providers/paypal.rst:83 +msgid "Settings in Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/ogone.rst:105 +msgid "" +"To set up Ogone in Odoo, head to :menuselection:`Accounting --> " +"Configuration --> Payment Providers` and open the Ogone provider. In the " +":guilabel:`Credentials` tab, enter the **PSPID** of your Ogone account, and " +"fill out the other fields as configured in your :ref:`Ogone portal " +"<ogone/ogone>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:3 +msgid "PayPal" +msgstr "PayPal" + +#: ../../content/applications/finance/payment_providers/paypal.rst:5 +msgid "" +"`Paypal <https://www.paypal.com/>`_ is an American online payment provider " +"available worldwide, and one of the few that does not charge a subscription " +"fee." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:9 +msgid "" +"While PayPal is available in `over 200 countries/regions " +"<https://www.paypal.com/webapps/mpp/country-worldwide>`_, only `a selection " +"of currencies are supported " +"<https://developer.paypal.com/docs/reports/reference/paypal-supported-" +"currencies>`_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:14 +msgid "Settings in PayPal" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:16 +msgid "" +"To access your PayPal account settings, log into PayPal, open the " +":guilabel:`Account Settings`, and open the :guilabel:`Website payments` " +"menu." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst-1 +msgid "PayPal account menu" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:24 +msgid "" +"Note that for PayPal to work **in Odoo**, the options :ref:`Auto Return " +"<paypal/auto-return>` and :ref:`PDT <paypal/pdt>` **must** be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:30 +msgid "Auto Return" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:32 +msgid "" +"The **Auto Return** feature automatically redirects customers to Odoo once " +"the payment is processed." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:34 +msgid "" +"From :guilabel:`Website payments`, go to :menuselection:`Website preferences" +" --> Update --> Auto return for website payments --> Auto return` and select" +" :guilabel:`On`. Enter the address of your Odoo database (e.g., " +"`https://yourcompany.odoo.com`) in the :guilabel:`Return URL` field, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:40 +msgid "" +"Any URL does the job. Odoo only needs the setting to be enabled since it " +"uses another URL." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:45 +msgid "Payment Data Transfer (PDT)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:47 +msgid "" +":abbr:`PDT (Payment Data Transfer)` allows to receive payment confirmations," +" displays the payment status to the customers, and verifies the authenticity" +" of the payments. From :menuselection:`Website preferences --> Update`, " +"scroll down to :guilabel:`Payment data transfer` and select :guilabel:`On`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:52 +msgid "" +"PayPal displays your **PDT Identity Token** as soon as :ref:`Auto return " +"<paypal/auto-return>` and :ref:`Payment Data Transfer (PDT) <paypal/pdt>` " +"are enabled. If you need the **PDT Identity Token**, disable and re-enable " +":guilabel:`Payment data transfer` to display the token again." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:57 +msgid "PayPal Account Optional" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:59 +msgid "" +"We advise not to prompt customers to log in with a PayPal account upon " +"payment. It is better and more accessible for customers to pay with a " +"debit/credit card. To disable that prompt, go to :menuselection:`Account " +"Settings --> Website payments --> Update` and select :guilabel:`On` for " +":guilabel:`PayPal account optional`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:65 +msgid "Payment Messages Format" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:67 +msgid "" +"If you use accented characters (or anything other than primary Latin " +"characters) for customer names or addresses, then you **must** configure the" +" encoding format of the payment request sent by Odoo to PayPal. If you do " +"not, some transactions fail without notice." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:71 +msgid "" +"To do so, go to `your production account <https://www.paypal.com/cgi-" +"bin/customerprofileweb ?cmd=_profile-language-encoding>`_. Then, click " +":guilabel:`More Options` and set the two default encoding formats as " +":guilabel:`UTF-8`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:76 +msgid "" +"For Encrypted Website Payments & EWP_SETTINGS error, please check the " +"`Paypal documentation <https://developer.paypal.com/docs/online/>`_." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:78 +msgid "" +"Configure your :ref:`Paypal Sandbox account <paypal/testing>`, then follow " +"this `link <https://sandbox.paypal.com/cgi-" +"bin/customerprofileweb?cmd=_profile-language-encoding>`_ to configure the " +"encoding format in a test environment." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:88 +msgid "" +"Odoo needs your **API Credentials** to connect with your PayPal account. To " +"do so, go to :menuselection:`Accounting --> Configuration --> Payment " +"Providers` and :guilabel:`Activate` PayPal. Then, enter your PayPal account " +"credentials in the :guilabel:`Credentials` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:92 +msgid ":guilabel:`Email`: the login email address in Paypal;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:93 +msgid "" +":guilabel:`PDT Identity Token`: the key used to verify the authenticity of " +"transactions." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:98 +msgid "Test environment" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:103 +msgid "" +"Thanks to PayPal sandbox accounts, you can test the entire payment flow in " +"Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:105 +msgid "" +"Log into the `Paypal Developer Site <https://developer.paypal.com/>`_ using " +"your PayPal credentials, which creates two sandbox accounts:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:108 +msgid "" +"A business account (to use as merchants, e.g., " +"`pp.merch01-facilitator@example.com " +"<mailto:pp.merch01-facilitator@example.com>`_);" +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:110 +msgid "" +"A default personal account (to use as shoppers, e.g., " +"`pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`_)." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:113 +msgid "" +"Log into PayPal sandbox using the merchant account and follow the same " +"configuration instructions. Enter your sandbox credentials in Odoo " +"(:menuselection:`Accounting --> Configuration --> Payment Providers --> " +"PayPal` in the :guilabel:`Credentials` tab, and make sure the status is set " +"on :guilabel:`Test Mode`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/paypal.rst:118 +msgid "Run a test transaction from Odoo using the sandbox personal account." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:3 +msgid "Razorpay" +msgstr "Razorpay" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:5 +msgid "" +"`Razorpay <https://razorpay.com/>`_ is an online payments provider " +"established in India and covering more than 100 payment methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:11 +msgid "Configuration on Razorpay Dashboard" +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:13 +msgid "" +"Log into `Razorpay Dashboard <https://dashboard.razorpay.com/>`_ and go to " +":menuselection:`Settings --> API Keys`. Generate the new keys and copy the " +"values of the :guilabel:`Key Id` and :guilabel:`Secret Key` fields and save " +"them for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:0 +msgid "" +"Go to :menuselection:`Settings --> Webhooks`, click on :guilabel:`Create New" +" Webhook`, and enter your Odoo database URL followed by " +"`/payment/razorpay/webhook` in the :guilabel:`Webhook URL` text field." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:0 +msgid "For example: `https://example.odoo.com/payment/razorpay/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:20 +msgid "" +"Fill the :guilabel:`Secret` field with a password of your choice and save it" +" for later." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:21 +msgid "" +"Make sure the :guilabel:`payment.authorized`, :guilabel:`payment.captured`, " +":guilabel:`payment.failed`, :guilabel:`refund.failed` and " +":guilabel:`refund.processed` checkboxes are ticked." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:24 +msgid "Click on :guilabel:`Create Webhook` to finalize the configuration." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:29 +msgid "" +"The :guilabel:`Recurring payments` feature must be activated if you want to " +"make recurring payments. Send a request to the `Razorpay Support team " +"<https://razorpay.com/support/#request>`_ to enable recurring payments." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:39 +msgid "" +":ref:`Navigate to the payment provider Razorpay <payment_providers/add_new>`" +" and change its state to :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:41 +msgid "" +"In the :guilabel:`Credentials` tab, fill the :guilabel:`Key Id`, " +":guilabel:`Key Secret`, and :guilabel:`Webhook Secret` with the values you " +"saved at the step :ref:`payment_providers/razorpay/configure_dashboard`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:47 +msgid "If you configure Odoo to capture amounts manually:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:49 +msgid "" +"Be aware that the **manual voiding** of a transaction is not supported by " +"Razorpay." +msgstr "" + +#: ../../content/applications/finance/payment_providers/razorpay.rst:50 +msgid "" +"After **five days**, if the transaction hasn't been captured yet, it'll " +"automatically be **voided**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:3 +msgid "SIPS" +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:5 +msgid "" +"`SIPS <https://sips.worldline.com/>`_ is an online payments solution from " +"the multinational Worldline." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:17 +msgid "" +"Odoo needs your **API Credentials** to connect with your SIPS account, which" +" comprise:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:19 +msgid "" +"**Merchant ID**: The ID solely used to identify the merchant account with " +"SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:20 +msgid "**Secret Key**: The key to sign the merchant account with SIPS." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:21 +msgid "**Secret Key Version**: The version of the key, pre-filled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:22 +msgid "**Interface Version**: Pre-filled, don't change it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:24 +msgid "" +"You can copy your credentials from your SIPS environment info documentation," +" in the section **PROD**, and paste them in the related fields under the " +"**Credentials** tab." +msgstr "" + +#: ../../content/applications/finance/payment_providers/sips.rst:28 +msgid "" +"If you are trying SIPS as a test, with the *TEST* credentials, change the " +"**State** to *Test Mode*. We recommend doing this on a test Odoo database, " +"rather than on your main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:3 +msgid "Stripe" +msgstr "Stripe" + +#: ../../content/applications/finance/payment_providers/stripe.rst:5 +msgid "" +"`Stripe <https://stripe.com/>`_ is a United States-based online payment " +"solution provider, allowing businesses to accept **credit cards** and other " +"payment methods." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:9 +msgid "Link your Stripe Account with Odoo" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:14 +msgid "The method to acquire your credentials depends on your hosting type:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:19 +#: ../../content/applications/finance/payment_providers/stripe.rst:35 +msgid "" +"Go to the **eCommerce** or the **Sales** app and click on the *Activate " +"Stripe* or the *Set payments* button on the onboarding banner." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:21 +#: ../../content/applications/finance/payment_providers/stripe.rst:37 +msgid "Fill in the requested information and submit the form." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:22 +#: ../../content/applications/finance/payment_providers/stripe.rst:38 +msgid "Confirm your email address when Stripe sends you a confirmation email." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:23 +msgid "" +"At the end of the process, you are redirected to Odoo. If you submitted all " +"the requested information, you are all set and your payment provider is " +"enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:25 +msgid "Your can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:28 +msgid "" +"To use your own API keys, :ref:`activate the Developer mode <developer-" +"mode>` and :ref:`enable Stripe manually <payment_providers/add_new>`. You " +"can then :ref:`Fill in your credentials <stripe/api_keys>`, :ref:`generate a" +" webhook <stripe/webhook>` and enable the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:33 +msgid "Odoo.sh or On-premise" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:39 +msgid "" +"At the end of the process, you are redirected to the payment provider " +"**Stripe** on Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:40 +msgid ":ref:`Fill in your credentials <stripe/api_keys>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:41 +msgid ":ref:`Generate a webhook <stripe/webhook>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:42 +msgid "Enable the payment provider." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:43 +msgid "" +"You are all set and can continue to :ref:`stripe/local-payment-methods`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:46 +msgid "" +"To connect your Stripe account after the onboarding is already completed, go" +" to :menuselection:`Accounting --> Configuration --> Payment Providers --> " +"Stripe` and click on the *Connect Stripe* button." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:51 +msgid "" +"If you are testing Stripe (in **test mode**), change the **State** to *Test " +"Mode*. We recommend doing this on a test Odoo database rather than on your " +"main database." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:57 +msgid "Fill in your credentials" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:59 +msgid "" +"In case your **API Credentials** are required to connect with your Stripe " +"account, these are the credentials that must be completed:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:62 +msgid "" +":ref:`Publishable Key <stripe/api_keys>`: The key solely used to identify " +"the account with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:63 +msgid "" +":ref:`Secret Key <stripe/api_keys>`: The key to sign the merchant account " +"with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:64 +msgid "" +":ref:`Webhook Signing Secret <stripe/webhook>`: When you enable your webhook" +" on your Stripe account, this signing secret must be set to authenticate the" +" messages sent from Stripe to Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:67 +msgid "" +"To retrieve the publishable and secret keys, follow this `link to your API " +"keys <https://dashboard.stripe.com/account/apikeys>`_, or log into your " +"Stripe dashboard and go to :menuselection:`Developers --> API Keys --> " +"Standard Keys`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:74 +msgid "Generate a webhook" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:76 +msgid "" +"In case your **Webhook Signing Secret** is required to connect with your " +"Stripe account, you can create a webhook either automatically or manually." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:80 +msgid "Create the webhook automatically" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:82 +msgid "" +"Make sure your :ref:`Publishable and Secret keys <stripe/api_keys>` are " +"filled in, then click on the *Generate your Webhook* button." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:85 +msgid "Create the webhook manually" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:87 +msgid "" +"Visit the `webhooks page on Stripe " +"<https://dashboard.stripe.com/webhooks>`_, or log into your Stripe dashboard" +" and go to :menuselection:`Developers --> Webhooks`. Then, click on **Add " +"endpoint** in your **Hosted endpoints** and insert the following data into " +"the pop-up form:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "In the **Endpoint URL**, enter your Odoo database's URL followed by" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "`/payment/stripe/webhook`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:0 +msgid "For example: `https://yourcompany.odoo.com/payment/stripe/webhook`" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:94 +msgid "" +"At the end of the form, you can **Select events** to listen to. Click on it " +"and, in the **Checkout** section, select **checkout.session.completed**." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:98 +msgid "" +"It is possible to select other events, but they are currently not processed " +"by Odoo." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:100 +msgid "" +"When you click on **Add endpoint**, your Webhook is configured. You can then" +" click on **reveal** to display your signing secret." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:106 +msgid "Enable local payment methods" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:108 +msgid "" +"Local payment methods are payment methods that are only available for " +"certain merchants and customers countries and currencies." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:111 +msgid "Odoo supports the following local payment methods:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:113 +msgid "Bancontact" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:114 +msgid "EPS" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:115 +msgid "giropay" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:116 +msgid "iDEAL" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:117 +msgid "Przelewy24 (P24)" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:119 +msgid "" +"To enable some of these local payment methods with Stripe, list them as " +"supported payment icons. To do so, go to :menuselection:`Payment Providers " +"--> Stripe --> Configuration` and add the desired payment methods in the " +"**Supported Payment Icons** field. If the desired payment method is already " +"listed, you do not have anything to do." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst-1 +msgid "Select and add icons of the payment methods you want to enable" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:128 +msgid "" +"If a payment method record does not exist in the database and its related " +"local payment method is listed above, it is considered enabled with Stripe." +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:130 +msgid "" +"If a local payment method is not listed above, it is not supported and " +"cannot be enabled." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:3 +msgid "Wire transfers" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:5 +msgid "" +"The **Wire transfer** payment method allows you to provide payment " +"instructions to your customers, such as the bank details and communication. " +"They are displayed:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:8 +msgid "" +"at the end of the checkout process, once the customer has selected " +":guilabel:`Wire transfer` as a payment method and clicked the :guilabel:`Pay" +" now` button:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:0 +msgid "Payment instructions at checkout" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:14 +msgid "on the customer portal:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:0 +msgid "Payment instructions on the customer portal" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:20 +msgid "" +"While this method is very accessible and requires minimal setup, it is very " +"inefficient process-wise. We recommend setting up a :doc:`payment provider " +"<../payment_providers>` instead." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:22 +msgid "" +"Online orders remain in the :guilabel:`Quotation sent` (i.e., unpaid order) " +"stage until you receive the payment and :guilabel:`Confirm` the order." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:26 +msgid "" +"**Wire transfer** can be used as a template for other payment methods that " +"are processed manually, such as checks, by renaming or duplicating it." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:32 +msgid "" +"To configure **Wire Transfer**, go to :menuselection:`Accounting / Website " +"--> Configuration --> Payment Providers`, and open the :guilabel:`Wire " +"Transfer` card. Then, in the :guilabel:`Configuration` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:36 +msgid "Select the :guilabel:`Communication` to be used;" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:38 +msgid ":guilabel:`Based on Document Reference`: sales order or invoice number" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:39 +msgid ":guilabel:`Based on Customer ID`: customer identifier" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:41 +msgid "" +"Tick the :guilabel:`Enable QR codes` check box to activate :doc:`QR code " +"payments <../accounting/customer_invoices/epc_qr_code>`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:44 +msgid "Define the payment instructions in the :guilabel:`Messages` tab:" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst-1 +msgid "Define payment instructions" +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:49 +msgid "" +"If you have already defined :doc:`a bank account <../accounting/bank>`, the " +"account number will be automatically added to the default message generated " +"by Odoo. You can also add it afterwards and update the message by clicking " +":guilabel:`Reload pending message`." +msgstr "" + +#: ../../content/applications/finance/payment_providers/wire_transfer.rst:54 +msgid ":ref:`payment_providers/journal`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:3 +msgid "Sign" +msgstr "เพิ่ม" + +#: ../../content/applications/finance/sign.rst:5 +msgid "" +"**Odoo Sign** allows you to send, sign, and approve documents online, using " +"electronic signatures." +msgstr "" + +#: ../../content/applications/finance/sign.rst:7 +msgid "" +"An **electronic signature** shows a person's agreement to the content of a " +"document. Just like a handwritten signature, the electronic one represents a" +" legal bounding by the terms of the signed document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:11 +msgid "" +"With Sign, you can upload any PDF file and add fields to it. These fields " +"can be automatically filled in with the user's details present in your " +"database." +msgstr "" + +#: ../../content/applications/finance/sign.rst:15 +msgid "`Odoo Sign: product page <https://www.odoo.com/app/sign>`_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:16 +msgid "`Odoo Tutorials: Sign [video] <https://www.odoo.com/slides/sign-61>`_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:19 +msgid "Validity of electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:21 +msgid "" +"Documents signed via the Sign app are valid electronic signatures in the " +"European Union and the United States of America. They also meet the " +"requirements for electronic signatures in most countries. The legal validity" +" of electronic signatures generated by Odoo depends on your country's " +"legislation. Companies doing business abroad should also consider other " +"countries' electronic signature laws." +msgstr "" + +#: ../../content/applications/finance/sign.rst:28 +msgid "European Union" +msgstr "สหภาพยุโรป" + +#: ../../content/applications/finance/sign.rst:30 +msgid "" +"The `eIDAS regulation <http://data.europa.eu/eli/reg/2014/910/oj>`_ " +"establishes the framework for electronic signatures in the `27 member states" +" of the European Union <https://europa.eu/european-union/about-" +"eu/countries_en>`_. It distinguishes three types of electronic signatures:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:35 +msgid "Simple electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:36 +msgid "Advanced electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:37 +msgid "Qualified electronic signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:39 +msgid "" +"Odoo generates the first type, **simple electronic signatures**; these " +"signatures are legally valid in the EU, as stated in the eIDAS regulation." +msgstr "" + +#: ../../content/applications/finance/sign.rst:42 +msgid "" +"Electronic signatures may not be automatically recognized as valid. You may " +"need to bring supporting evidence of a signature's validity. While the Sign " +"app provides a simple electronic signature, some supporting evidence is " +"automatically collected during the signature process, such as:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:47 +msgid "Email and SMS validation (if enabled)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:48 +msgid "" +"Strong identity proof through itsme® (available in Belgium and the " +"Netherlands)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:49 +msgid "" +"Timestamped, IP and geographically traceable access logs to the documents " +"and their associated signatures" +msgstr "" + +#: ../../content/applications/finance/sign.rst:51 +msgid "" +"Document traceability and inalterability (any alteration made to a signed " +"document is detected by Odoo with the use of cryptographic proofs)" +msgstr "" + +#: ../../content/applications/finance/sign.rst:55 +msgid "United States of America" +msgstr "สหรัฐอเมริกา" + +#: ../../content/applications/finance/sign.rst:57 +msgid "" +"The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) " +"<https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the " +"interstate and international levels, and the `UETA (Uniform Electronic " +"Transactions Act) <https://www.uniformlaws.org/committees/community-" +"home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_," +" at the state level, provide the legal framework for electronic signatures. " +"Note that `Illinois " +"<https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York " +"<https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not " +"adopted the UETA, but similar acts instead." +msgstr "" + +#: ../../content/applications/finance/sign.rst:66 +msgid "" +"Overall, to be recognized as valid, electronic signatures have to meet five " +"criteria:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:68 +msgid "" +"The signer must show a clear **intent to sign**. For example, using a mouse " +"to draw a signature can show intent. The signer must also have the option to" +" opt out of the electronic document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:70 +msgid "" +"The signer must first express or imply their **consent to conduct business " +"electronically**." +msgstr "" + +#: ../../content/applications/finance/sign.rst:71 +msgid "" +"**The signature must be clearly attributed**. In Odoo, metadata, such as the" +" signer's IP address, is added to the signature, which can be used as " +"supporting evidence." +msgstr "" + +#: ../../content/applications/finance/sign.rst:73 +msgid "" +"**The signature must be associated with the signed document**, for example, " +"by keeping a record detailing how the signature was captured." +msgstr "" + +#: ../../content/applications/finance/sign.rst:75 +msgid "" +"Electronically signed documents need to be **retained and stored** by all " +"parties involved; for example, by providing the signer either a fully-" +"executed copy or the possibility to download a copy." +msgstr "" + +#: ../../content/applications/finance/sign.rst:80 +msgid "" +"The above information has no legal value; it is only provided for general " +"informational purposes. As laws governing electronic signatures rapidly " +"evolve, we cannot guarantee that all information is up-to-date. We advise " +"contacting a local attorney for legal advice regarding electronic signature " +"compliance and validity." +msgstr "" + +#: ../../content/applications/finance/sign.rst:86 +msgid "Send a document to sign" +msgstr "" + +#: ../../content/applications/finance/sign.rst:89 +msgid "One-time signature" +msgstr "" + +#: ../../content/applications/finance/sign.rst:91 +msgid "" +"You can click :guilabel:`Upload a PDF to sign` from your dashboard for a " +"one-time signature. Select your document, open it, and drag and drop the " +"required :ref:`fields <sign/fields>` in your document. You can modify the " +":ref:`role <sign/role>` assigned to a field by clicking on it and selecting " +"the one you want." +msgstr "" + +#: ../../content/applications/finance/sign.rst:96 +msgid "" +"When ready, click :guilabel:`Send`, and fill in the required fields. Once " +"sent, your document remains available. Go to :menuselection:`Documents --> " +"All Documents` to see your document and the status of the signatures." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Signature status" +msgstr "" + +#: ../../content/applications/finance/sign.rst:104 +msgid "Validity dates and reminders" +msgstr "" + +#: ../../content/applications/finance/sign.rst:106 +msgid "" +"You can set **validity dates** on limited-duration agreement documents or " +"send **automatic email reminders** to obtain signatures on time. From your " +"dashboard, click :guilabel:`Send` on your document. On the new page, go to " +"the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and " +":guilabel:`Reminder` fields." +msgstr "" + +#: ../../content/applications/finance/sign.rst:112 +#: ../../content/applications/finance/spreadsheet/templates.rst:3 +msgid "Templates" +msgstr "เทมเพลต" + +#: ../../content/applications/finance/sign.rst:114 +msgid "" +"You can create document templates when you have to send the same document " +"several times. From your dashboard, click :guilabel:`Upload a PDF template`." +" Select the document and add the required :ref:`fields <sign/fields>`. You " +"can modify the :ref:`role <sign/role>` of a field by clicking on it and " +"selecting the one you want." +msgstr "" + +#: ../../content/applications/finance/sign.rst:119 +msgid "" +"Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your " +"template, define a :guilabel:`Signed Document Workspace`, add " +":guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will " +"be available in the signature confirmation message received after the " +"signature, or define :guilabel:`Authorized Users` if you want to restrict " +"the use of your template to specific authorized users or groups." +msgstr "" + +#: ../../content/applications/finance/sign.rst:125 +msgid "" +"Your templates are visible by default on your dashboard. You can click " +":guilabel:`Send` to quickly send a document template to a signer or " +":guilabel:`Sign Now` if you are ready to sign your document immediately." +msgstr "" + +#: ../../content/applications/finance/sign.rst:130 +msgid "" +"You can **create a template from a document that was previously sent**. To " +"do so, go to :menuselection:`Documents --> All Documents`. On the document " +"you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), " +"then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) " +"again, then :guilabel:`Restore`. Your document now appears on your dashboard" +" next to your other templates." +msgstr "" + +#: ../../content/applications/finance/sign.rst:139 +msgid "Roles" +msgstr "บทบาท" + +#: ../../content/applications/finance/sign.rst:141 +msgid "" +"Each field in a Sign document is related to a role corresponding to a " +"specific person. When a document is being signed, the person assigned to the" +" role must fill in their assigned fields and sign it." +msgstr "" + +#: ../../content/applications/finance/sign.rst:145 +msgid "" +"Roles are available by going to :menuselection:`Sign --> Configuration --> " +"Roles`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:147 +msgid "" +"It is possible to update existing roles or to create new roles by clicking " +"on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra " +"Authentication Step` to confirm the identity of the signing person, and if " +"the document can be reassigned to another contact, select :guilabel:`Change " +"Authorized` for the role. A :guilabel:`Color` can also be chosen for the " +"role. This color can help understand which roles are responsible for which " +"field when configuring a template." +msgstr "" + +#: ../../content/applications/finance/sign.rst:155 +msgid "Secured identification" +msgstr "" + +#: ../../content/applications/finance/sign.rst:157 +msgid "" +"As the owner of a document, you may request an :guilabel:`Extra " +"Authentication Step` through :ref:`SMS verification <sign/sms>` or via " +":ref:`Itsme® <sign/itsme>` (available in Belgium and the Netherlands). Both " +"authentication options require :ref:`credits <iap/buying_credits>`. If you " +"do not have any credits left, the authentication steps will be skipped." +msgstr "" + +#: ../../content/applications/finance/sign.rst:163 +msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:164 +msgid "" +":doc:`SMS pricing and FAQ " +"<../marketing/sms_marketing/pricing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/finance/sign.rst:169 +msgid "SMS verification" +msgstr "" + +#: ../../content/applications/finance/sign.rst:171 +msgid "" +"Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the " +":guilabel:`Extra Authentication Step` column for the role, and select " +":guilabel:`Unique Code Via SMS`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:175 +msgid "" +"Before being able to send SMS Text Messages, you need to register your phone" +" number. To do so, go to :menuselection:`Sign --> Configuration --> " +"Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by" +" SMS`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:179 +msgid "" +"Go to the document to sign, add the field for which the SMS verification is " +"required, for example, the :guilabel:`Signature` field, and click " +":guilabel:`Send`. On the new page, select the :guilabel:`customer` and click" +" :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:183 +msgid "" +"The person signing the document fills in the :guilabel:`Signature` field, " +"then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed " +"Document`. A :guilabel:`Final Validation` page pops up where to add their " +"phone number. One-time codes are sent by SMS." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Add a hash to your document" +msgstr "" + +#: ../../content/applications/finance/sign.rst:191 +msgid "This feature is enabled by default." +msgstr "" + +#: ../../content/applications/finance/sign.rst:192 +msgid "" +"As soon as the :guilabel:`Extra Authentication Step` applies to a role, this" +" validation step is requested for any field assigned to this role." +msgstr "" + +#: ../../content/applications/finance/sign.rst:198 +msgid "Itsme®" +msgstr "" + +#: ../../content/applications/finance/sign.rst:200 +msgid "" +"Itsme® authentication can be used to allow signatories to provide their " +"identity using itsme®. This feature is only available in **Belgium** and the" +" **Netherlands**." +msgstr "" + +#: ../../content/applications/finance/sign.rst:203 +msgid "" +"The feature can be enabled in :guilabel:`Sign Settings` and applies " +"automatically to the :guilabel:`Customer (identified with itsme®)` role. To " +"enable it for other roles, go to :menuselection:`Sign --> Configuration --> " +"Roles`. Click in the :guilabel:`Extra Authentication Step` column for the " +"role, and select :guilabel:`Via itsme®`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:208 +msgid "" +"Go to the document that needs to be signed and add the :guilabel:`Signature`" +" field. Switch to any role configured to use the feature, and click " +":guilabel:`Validate` and :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "select customer identified with itsme®" +msgstr "" + +#: ../../content/applications/finance/sign.rst:214 +msgid "" +"Upon signing the document, the signer completes the :guilabel:`Signature` " +"field and proceeds by clicking on :guilabel:`Validate & Send Completed " +"Document`, triggering a :guilabel:`Final verification` page where " +"authentication via itsme® is required." +msgstr "" + +#: ../../content/applications/finance/sign.rst:219 +msgid "Signatory hash" +msgstr "" + +#: ../../content/applications/finance/sign.rst:221 +msgid "" +"Each time someone signs a document, a **hash** - a unique digital signature " +"of the operation - is generated to ensure traceability, integrity, and " +"inalterability. This process guarantees that any changes made after a " +"signature is affixed can be easily detected, maintaining the document's " +"authenticity and security throughout its lifecycle." +msgstr "" + +#: ../../content/applications/finance/sign.rst:226 +msgid "" +"A visual security frame displaying the beginning of the hash is added to the" +" signatures. Internal users can hide or show it by turning the " +":guilabel:`Frame` option on or off when signing the document." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Adding the visual security frame to a signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:238 +msgid "" +"Tags can be used to categorize and organize documents, allowing users to " +"quickly search for and filter documents based on specific criteria." +msgstr "" + +#: ../../content/applications/finance/sign.rst:241 +msgid "" +"You can manage tags by going to :menuselection:`Configuration --> Tags`. To " +"create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag" +" Name` and select a :guilabel:`Color Index` for your tag." +msgstr "" + +#: ../../content/applications/finance/sign.rst:245 +msgid "" +"To apply a tag to a document, use the dropdown list available in your " +"document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:248 +msgid "" +"You can modify the tags of a signed document by going to " +":menuselection:`Documents --> All Documents`, clicking the vertical ellipsis" +" (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying " +"your :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:253 +msgid "Sign order" +msgstr "" + +#: ../../content/applications/finance/sign.rst:255 +msgid "" +"When a document needs to be signed by different parties, the signing order " +"lets you control the order in which your recipients receive it for " +"signature." +msgstr "" + +#: ../../content/applications/finance/sign.rst:258 +msgid "" +"After uploading a PDF with at least two signature fields with two different " +"roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing " +"Order` button and search for the signer's name or email information to add " +"them. You can decide on the signing order by typing **1** or **2** in the " +"first column." +msgstr "" + +#: ../../content/applications/finance/sign.rst:263 +msgid "" +"Each recipient receives the signature request notification only once the " +"previous recipient has completed their action." +msgstr "" + +#: ../../content/applications/finance/sign.rst:267 +msgid "" +"`Odoo Quick Tips: Sign order [video] " +"<https://www.youtube.com/watch?v=2KUq7RPt1cU/>`_" +msgstr "" + +#: ../../content/applications/finance/sign.rst:272 +msgid "Field types" +msgstr "" + +#: ../../content/applications/finance/sign.rst:274 +msgid "" +"Fields are used in a document to indicate what information must be completed" +" by the signers. You can add fields to your document simply by dragging and " +"dropping them for the left column into your document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:278 +msgid "" +"Various field types can be used to sign documents (placeholder, " +"autocompletion, etc.). By configuring your own field types, also known as " +"signature item types, the signing process can be even faster for your " +"customers, partners, and employees." +msgstr "" + +#: ../../content/applications/finance/sign.rst:282 +msgid "" +"To create and edit field types, go to :menuselection:`Sign --> Configuration" +" --> Settings --> Edit field types`." +msgstr "" + +#: ../../content/applications/finance/sign.rst:285 +msgid "" +"You can select an existing field by clicking on it, or you can " +":guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, " +"select a :guilabel:`Field Type`:" +msgstr "" + +#: ../../content/applications/finance/sign.rst:288 +msgid "" +":guilabel:`Signature`: users are asked to enter their signature either by " +"drawing it, generating an automatic one based on their name, or uploading a " +"local file (usually an image). Each subsequent :guilabel:`Signature` field " +"type then reuses the data entered in the first field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:291 +msgid "" +":guilabel:`Initial`: users are asked to enter their initials, in a similar " +"way to the :guilabel:`Signature` field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:293 +msgid ":guilabel:`Text`: users enter text on a single line." +msgstr "" + +#: ../../content/applications/finance/sign.rst:294 +msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." +msgstr "" + +#: ../../content/applications/finance/sign.rst:295 +msgid "" +":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or " +"consent)." +msgstr "" + +#: ../../content/applications/finance/sign.rst:296 +msgid "" +":guilabel:`Selection`: users choose a single option from a variety of " +"options." +msgstr "" + +#: ../../content/applications/finance/sign.rst:298 +msgid "" +"The :guilabel:`Auto-fill Partner Field` setting is used to automatically " +"fill in a field during the signature process. It uses the value of one of " +"the fields on the contact (`res.partner`) model of the person signing the " +"document. To do so, enter the contact model field's technical name." +msgstr "" + +#: ../../content/applications/finance/sign.rst:303 +msgid "" +"To know the technical name of a field, enable developer mode and hover your " +"mouse on the question mark next to the field." +msgstr "" + +#: ../../content/applications/finance/sign.rst:307 +msgid "" +"Auto-completed values are suggestions and can be modified as required by the" +" person signing the document." +msgstr "" + +#: ../../content/applications/finance/sign.rst:310 +msgid "" +"The size of the fields can also be changed by editing the :guilabel:`Default" +" Width` and :guilabel:`Default Height`. Both sizes are defined as a " +"percentage of the full page expressed as a decimal, with 1 equalling the " +"full page's width or height. By default, the width of new fields you create " +"is set to 15% (0.150) of a full page's width, while their height is set to " +"1.5% (0.015) of a full page's height." +msgstr "" + +#: ../../content/applications/finance/sign.rst:316 +msgid "" +"Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-" +"hand side of the user's screen during the signing process to help them " +"understand what the step entails (e.g., \"Sign here\" or “Fill in your " +"birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed" +" inside the field before it is completed." +msgstr "" + +#: ../../content/applications/finance/sign.rst-1 +msgid "Tip and placeholder example in Odoo Sign" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:6 +msgid "Spreadsheet" +msgstr "สเปรดชีต" + +#: ../../content/applications/finance/spreadsheet.rst:14 +msgid "" +"Spreadsheet lets you organize, analyze, and visualize your data in tabular " +"form. Among others, you can:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:17 +msgid "" +":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) " +"<spreadsheet/insert>`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:18 +msgid "" +":doc:`Use default templates or create new ones <spreadsheet/templates>`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:19 +msgid "Format data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:20 +msgid "Use formulas and functions." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:21 +msgid "Sort and filter data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:28 +msgid "" +"Some of Spreadsheet's main :abbr:`UI (user interface)` elements are " +"highlighted and defined below." +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst-1 +msgid "Spreadsheet main UI elements" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:34 +msgid "Menu bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:35 +msgid "Top bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:36 +msgid "Formula bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:37 +msgid "Filters button" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:38 +msgid "Row header" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:39 +msgid "Column header" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:40 +msgid "Cell menu" +msgstr "" + +#: ../../content/applications/finance/spreadsheet.rst:41 +msgid "Bottom bar" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:3 +msgid "Link Odoo data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:5 +msgid "" +"You can insert and link several elements from your database in your " +"spreadsheets, namely:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:7 +msgid "pivots," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:8 +msgid "graphs," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:9 +msgid "lists, and" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:10 +msgid "links to menus (i.e., a clickable link to a view of a specific model)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:12 +msgid "" +"Before inserting :ref:`pivots <reporting/views/pivot>`, :ref:`graphs " +"<reporting/views/graph>`, or lists, ensure they are tailored to your needs, " +"as some elements are more quickly - or only - configurable in their " +"respective view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:16 +msgid "" +"To insert pivots and graphs, click :guilabel:`Insert in spreadsheet` from " +"any pivot or graph view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:17 +msgid "" +"To insert lists, click :menuselection:`Favorites --> Insert list in " +"spreadsheet` from any list view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:19 +msgid "" +"To insert links to menus, click :menuselection:`Favorites --> Link menu in " +"spreadsheet` from any view." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:22 +msgid "" +"In the pop-up box, either create a new spreadsheet by selecting " +":guilabel:`Blank spreadsheet` or insert it in an existing one by selecting " +"it and clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst-1 +msgid "Inserting a pivot in a spreadsheet" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:30 +msgid "" +"By default, new spreadsheets are saved under the :guilabel:`Spreadsheet` " +"workspace of the Documents app." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:36 +msgid "Updating data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:38 +msgid "" +"Once inserted in a spreadsheet, your data is kept up-to-date, reflecting any" +" changes made to your database. Reopening the spreadsheet reloads the linked" +" data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:42 +msgid "" +"To update pivots and lists data without reopening a spreadsheet, go to the " +"menu bar and click :menuselection:`Data --> Refresh all data`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:46 +msgid "Pivot data" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:48 +msgid "" +"Using :guilabel:`Refresh all data` only updates existing pivot cells. If new" +" cells need to be added, go to the menu bar and click :menuselection:`Data " +"--> Re-insert pivot` to fully update the pivot. Alternatively, click " +":guilabel:`Insert pivot`, select the pivot, and tick :guilabel:`Display " +"missing cells only` to preview first the missing data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:0 +msgid "Displaying missing cells in a pivot" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/insert.rst:57 +msgid "" +"To change which records are :ref:`used by the pivot <search/preconfigured-" +"filters>`, right-click on a pivot cell, select :guilabel:`See pivot " +"properties`, and click :guilabel:`Edit domain`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:5 +msgid "" +"Spreadsheet templates allow you to quickly create spreadsheets without " +"starting from scratch." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:7 +msgid "" +"Several pre-built templates are available when creating a new spreadsheet " +"from the **Documents** app, such as:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:10 +msgid ":ref:`budget reports <templates/budget-reports>`," +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:11 +msgid ":ref:`pipeline revenue reports <templates/pipeline-reports>`, or" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:12 +msgid ":ref:`sales commission report <templates/sales-commission>`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "View of all the default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:17 +msgid "" +"You can also :ref:`save any spreadsheet as a template <templates/save>` and " +":ref:`manage and edit existing templates <templates/manage>`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:21 +msgid "Default templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:26 +msgid "Accounting: budget reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:28 +msgid "" +"Budget reports compare a company's actual spending with its budget over a " +"defined period. Two templates are available: one uses quarterly intervals " +"(:guilabel:`Budget Report (Quarterly)`), while the other uses monthly " +"intervals (:guilabel:`Budget Report (Monthly)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a budget report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:35 +msgid "" +"The cells under the :guilabel:`Actuals` column are automatically filled in " +"with the amount of money made and spent over the corresponding period (month" +" or quarter). The data is taken from posted journal items under :ref:`income" +" and expense accounts <chart-of-account/type>`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:40 +msgid "" +"Journal items under the :guilabel:`Other Income` account type are not " +"considered when collecting data." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:43 +msgid "" +"To analyze your budget's performance, fill the cells under the " +":guilabel:`Budget` column with how much money you expect to make " +"(:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the " +"related period and per account. Then, the performance (:guilabel:`Perf.`) " +"column compares :guilabel:`Actuals` data to their corresponding budget, " +"expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:48 +msgid "" +"Lastly, the :guilabel:`Net Profit` row represents the total " +":guilabel:`Income` minus the total :guilabel:`Expenses` for the " +":guilabel:`Actuals` and :guilabel:`Budget` columns." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:54 +msgid "CRM: pipeline revenue reports" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:56 +msgid "" +"Two pipeline revenue reports are available. The :guilabel:`Pipeline Revenue " +"Report (Monthly)` is dedicated to one-time revenue (:abbr:`NRR (non-" +"recurring revenue)`), while the :guilabel:`MRR/NRR Pipeline Revenue Report " +"(Monthly)` covers recurring and non-recurring revenue (:abbr:`MRR (monthly " +"recurring revenue)`)." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:62 +msgid "" +"Enable :guilabel:`Recurring Revenues` by going to :menuselection:`CRM --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a pipeline revenue report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:68 +msgid "" +"The cells under the :guilabel:`Actuals` column are automatically filled in " +"with the amount of monthly revenue from **won** opportunities." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:71 +msgid "" +"To compute the revenue performance, fill in the monthly revenue targets." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:73 +msgid "" +"For the :guilabel:`Revenue by Team` sheet, fill in the cells under the " +":guilabel:`Target` columns for each sales team." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:75 +msgid "" +"For the :guilabel:`Revenue by Salesperson` sheet, open the " +":guilabel:`Targets` sheet and fill in the cells next to each salesperson. " +"Use the :guilabel:`Monthly Factor` table below to adapt the main targets " +"depending on the month of the year." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:79 +msgid "" +"Then, the performance (:guilabel:`Perf.`) column compares " +":guilabel:`Actuals` data to their related budget, expressed as a percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:82 +msgid "" +"Lastly, the :guilabel:`Forecasted` column gathers the monthly revenue of " +"leads multiplied by their :guilabel:`Probability` percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:86 +msgid "For actuals and forecasts:" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:88 +msgid "" +"The :guilabel:`Expected Closing` date found on leads is used to assign them " +"to a month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:89 +msgid "" +"The recurring monthly revenue is used even if the recurring plan's number of" +" months is set to a different value than 1 month. For example, a yearly " +"plan's revenue is divided by 12 months." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:95 +msgid "Sales: sales commission" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:97 +msgid "" +"This report presents the monthly commission earned or due to each " +"salesperson." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst-1 +msgid "Extract of a sales commission report" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:102 +msgid "" +"The :guilabel:`Rate` column is pre-filled with the percentage rate from the " +":guilabel:`Rates` tab, which can be customized for each product category " +"according to the company's policy. Adjusting the rate for a specific product" +" category automatically updates the commission amount for that category." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:106 +msgid "" +"The :guilabel:`Invoiced` column shows the total amount of untaxed invoices " +"grouped by salesperson and month." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:109 +msgid "" +"Lastly, the :guilabel:`Comm.` column is computed by multiplying the invoiced" +" amount with the rate percentage." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:115 +msgid "Save a spreadsheet as a template" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:117 +msgid "" +"Any spreadsheet can be saved as a template. From the menu bar, click " +":menuselection:`File --> Save as template`. Modify the default " +":guilabel:`Template Name` if necessary and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:122 +msgid "Templates are available to all users on the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:127 +msgid "Manage and edit templates" +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:129 +msgid "" +"Manage templates by going to :menuselection:`Documents --> Configuration -->" +" Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter " +"<search/preconfigured-filters>` to view all templates in the database." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:133 +msgid "" +"To edit an existing template, click `✎ Edit` next to the desired template. " +"Modifications are automatically saved." +msgstr "" + +#: ../../content/applications/finance/spreadsheet/templates.rst:137 +msgid "" +"Use the download button under the :guilabel:`Data` column to export a " +"template in JSON format. The file can be imported into another database." +msgstr "" diff --git a/locale/th/LC_MESSAGES/general.po b/locale/th/LC_MESSAGES/general.po new file mode 100644 index 000000000..c522c64b2 --- /dev/null +++ b/locale/th/LC_MESSAGES/general.po @@ -0,0 +1,6148 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/general.rst:3 +msgid "Miscellaneous" +msgstr "เบ็ดเตล็ด" + +#: ../../content/applications/general/apps_modules.rst:3 +msgid "Apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:5 +msgid "" +"You can :ref:`install <general/install>`, :ref:`upgrade <general/upgrade>` " +"and :ref:`uninstall <general/uninstall>` all apps and modules from the " +":menuselection:`Apps` dashboard." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:8 +msgid "" +"By default, an *Apps* filter is applied. If you want to search for modules, " +"click on *Filters* and select *Extra*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst-1 +msgid "Add \"Extra\" filter in Odoo Apps" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:16 +msgid "" +"Odoo is *not a smartphone*, and its apps shouldn't be installed or " +"uninstalled carelessly. Apply caution when adding or removing apps and " +"modules on your database since this may impact your subscription costs." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Installing or uninstalling apps and managing users is up to you.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"As the administrator of your database, you are responsible for its usage, as" +" you know best how your organization works." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Odoo apps have dependencies.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"Installing some apps and features with dependencies may also install " +"additional apps and modules that are technically required, even if you won't" +" actively use them." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "**Test app installation/removal on a duplicate of your database.**" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:0 +msgid "" +"This way, you can know what app dependencies may be required or what data " +"may be erased." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:32 +msgid "Install apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:34 +msgid "" +"Go to :menuselection:`Apps`, and click on the *Install* button of the app " +"you want to install." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:37 +msgid "" +"If the module you are looking for is not listed, you can **update the app " +"list**." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:39 +msgid "" +"To do so, activate the :ref:`developer mode <developer-mode>`, then go to " +":menuselection:`Apps --> Update Apps List` and click on *Update*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:45 +msgid "Upgrade apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:47 +msgid "" +"On some occasions, new improvements or app features are added to " +":doc:`supported versions of Odoo " +"</administration/maintain/supported_versions>`. To be able to use them, you " +"must **upgrade** your app." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:51 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to upgrade, then on *Upgrade*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:57 +msgid "Uninstall apps and modules" +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:59 +msgid "" +"Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you " +"want to uninstall, then on *Uninstall*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:65 +msgid "" +"Some apps have dependencies, meaning that one app requires another. " +"Therefore, uninstalling one app may uninstall multiple apps and modules. " +"Odoo warns you which dependent apps and modules are affected by it." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:72 +msgid "To complete the uninstallation, click on *Confirm*." +msgstr "" + +#: ../../content/applications/general/apps_modules.rst:75 +msgid "" +"Uninstalling an app also uninstalls all its dependencies and permanently " +"erases their data." +msgstr "" + +#: ../../content/applications/general/auth.rst:5 +#: ../../content/applications/general/auth/azure.rst:79 +msgid "Authentication" +msgstr "การรับรองความถูกต้อง" + +#: ../../content/applications/general/auth/2fa.rst:3 +msgid "Two-factor Authentication" +msgstr "การรับรองความถูกต้องแบบ Two-factor" + +#: ../../content/applications/general/auth/2fa.rst:5 +msgid "" +"Two-factor authentication (\"2FA\") is a good way to improve the security of" +" an account, to make it less likely that an other person will manage to log " +"in instead of you." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:9 +msgid "" +"Practically, it means storing a secret inside an *authenticator* (usually " +"your cell phone) and exchanging a code from the authenticator when you try " +"to log in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:13 +msgid "" +"This means an attacker needs *both* to have guessed (or found) your password" +" and to access (or steal) your authenticator, a more difficult proposition " +"than either one or the other." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:18 +msgid "Requirements" +msgstr "ข้อกำหนด" + +#: ../../content/applications/general/auth/2fa.rst:20 +msgid "" +"These lists are just examples, they are not endorsements of any specific " +"software." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:23 +msgid "" +"If you don't already have one, you will need to choose an authenticator." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:26 +msgid "" +"Phone-based authenticators are the easiest and most common so we will assume" +" you'll pick and install one on your phone, examples include `Authy " +"<https://authy.com/>`_, `FreeOTP <https://freeotp.github.io/>`_, `Google " +"Authenticator <https://support.google.com/accounts/answer/1066447?hl=en>`_, " +"`LastPass Authenticator <https://lastpass.com/auth/>`_, `Microsoft " +"Authenticator <https://www.microsoft.com/en-" +"gb/account/authenticator?cmp=h66ftb_42hbak>`_, ...; password managers also " +"commonly include :abbr:`2FA (two-factor authentication)` support e.g. " +"`1Password <https://support.1password.com/one-time-passwords/>`_, `Bitwarden" +" <https://bitwarden.com/help/article/authenticator-keys/>`_, ..." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:39 +msgid "" +"For the sake of demonstration we will be using Google Authenticator (not " +"because it is any good but because it is quite common)." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:43 +msgid "Setting up two-factor authentication" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:45 +msgid "" +"Once you have your authenticator of choice, go to the Odoo instance you want" +" to setup :abbr:`2FA (two-factor authentication)`, then open " +":guilabel:`Preferences` (or :guilabel:`My Profile`):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:52 +msgid "" +"Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable " +"two-factor authentication` button:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:58 +msgid "" +"Because this is a security-sensitive action, you will need to input your " +"password:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:64 +msgid "After which you will see this screen with a barcode:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:69 +msgid "" +"In most applications, you can simply *scan the barcode* via the " +"authenticator of your choice, the authenticator will then take care of all " +"the setup:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:78 +msgid "" +"If you can not scan the screen (e.g. because you are doing this set-up on " +"the same phone as the authenticator application), you can click the provided" +" link, or copy the secret to manually set-up your authenticator:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:89 +msgid "" +"Once this is done, the authenticator should display a *verification code* " +"with some useful identifying information (e.g. the domain and login for " +"which the code is):" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:96 +msgid "" +"You can now input the code into the :guilabel:`Verification Code` field, " +"then click the :guilabel:`Enable two-factor authentication` button." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:100 +msgid "" +"Congratulation, your account is now protected by two-factor authentication!" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:107 +msgid "Logging in" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:109 +msgid "You should now :guilabel:`Log out` to follow along." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:111 +msgid "" +"On the login page, input the username and password of the account for which " +"you set up :abbr:`2FA (two-factor authentication)`, rather than immediately " +"enter Odoo you will now get a second log-in screen:" +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:118 +msgid "" +"Get your authenticator, input the code it provides for the domain and " +"account, validate, and you're now in." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:121 +msgid "" +"And that's it. From now on, unless you disable :abbr:`2FA (two-factor " +"authentication)` you will have a two-step log-in process rather than the old" +" one-step process." +msgstr "" + +#: ../../content/applications/general/auth/2fa.rst:125 +msgid "" +"Don't lose your authenticator, if you do, you will need an *Odoo " +"Administrator* to disable :abbr:`2FA (two-factor authentication)` on the " +"account." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:3 +msgid "Microsoft Azure sign-in authentication" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:5 +msgid "" +"The Microsoft Azure OAuth sign-in authentication is a useful function that " +"allows Odoo users to sign in to their database with their Microsoft Azure " +"account." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:8 +msgid "" +"This is particularly helpful if the organization uses Azure Workspace, and " +"wants employees within the organization to connect to Odoo using their " +"Microsoft Accounts." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:12 +msgid "" +"Databases hosted on Odoo.com should not use OAuth login for the owner or " +"administrator of the database as it would unlink the database from their " +"Odoo.com account. If OAuth is set up for that user, the database will no " +"longer be able to be duplicated, renamed, or otherwise managed from the " +"Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:19 +msgid ":doc:`../../productivity/calendar/outlook`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:20 +#: ../../content/applications/general/email_communication/email_servers.rst:67 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:23 +#: ../../content/applications/general/auth/google.rst:24 +#: ../../content/applications/general/voip/axivox.rst:16 +#: ../../content/applications/general/voip/onsip.rst:17 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/general/auth/azure.rst:25 +msgid "" +"Integrating the Microsoft sign-in function requires configuration on " +"Microsoft and Odoo." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:28 +msgid "Odoo System Parameter" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:30 +msgid "" +"First activate the :ref:`developer mode <developer-mode>`, and then go to " +":menuselection:`Settings --> Technical --> System Parameters`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:33 +msgid "" +"Click :guilabel:`Create` and on the new/blank form that appears, add the " +"following system parameter `auth_oauth.authorization_header` to the " +":guilabel:`Key` field, and set the :guilabel:`Value` to `1`. Then click " +":guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:38 +msgid "Microsoft Azure dashboard" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:41 +msgid "Create a new application" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:43 +msgid "" +"Now that the system parameters in Odoo have been set up, it's time to create" +" a corresponding application inside of Microsoft Azure. To get started " +"creating the new application, go to `Microsoft's Azure Portal " +"<https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook " +"Office 365` account if there is one, otherwise, log in with a personal " +":guilabel:`Microsoft account`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:50 +msgid "" +"A user with administrative access to the *Azure Settings* must connect and " +"perform the following configuration steps below." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:53 +msgid "" +"Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` " +"(formally *Azure Active Directory*). The location of this link is usually in" +" the center of the page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:56 +msgid "" +"Now, click on the :guilabel:`Add (+)` icon, located in the top menu, and " +"then select :guilabel:`App registration` from the drop-down menu. On the " +":guilabel:`Register an application` screen, rename the :guilabel:`Name` " +"field to `Odoo Login OAuth` or a similarly recognizable title. Under the " +":guilabel:`Supported account types` section select the option for " +":guilabel:`Accounts in this organizational directory only (Default Directory" +" only - Single tenant)`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:63 +msgid "" +"The :guilabel:`Supported account types` can vary by Microsoft account type " +"and end use of the OAuth. For example: Is the login meant for internal users" +" within one organization or is it meant for customer portal access? The " +"above configuration is used for internal users in an organization." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:68 +msgid "" +"Choose :guilabel:`Personal Microsoft accounts only` if the target audience " +"is meant for portal users. Choose :guilabel:`Accounts in this organizational" +" directory only (Default Directory only - Single tenant)` if the target " +"audience is company users." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:72 +msgid "" +"Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the " +"platform, and then input `https://<odoo base url>/auth_oauth/signin` in the " +":guilabel:`URL` field. The Odoo base :abbr:`URL (Uniform Resource Locator)` " +"is the canonical domain at which your Odoo instance can be reached (e.g. " +"*mydatabase.odoo.com* if you are hosted on Odoo.com) in the :guilabel:`URL` " +"field. Then, click :guilabel:`Register`, and the application is created." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:81 +msgid "" +"Edit the new app's authentication by clicking on the " +":guilabel:`Authentication` menu item in the left menu after being redirected" +" to the application's settings from the previous step." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:84 +msgid "" +"Next, the type of *tokens* needed for the OAuth authentication will be " +"chosen. These are not currency tokens but rather authentication tokens that " +"are passed between Microsoft and Odoo. Therefore, there is no cost for these" +" tokens; they are used merely for authentication purposes between two " +":abbr:`APIs (application programming interfaces)`. Select the tokens that " +"should be issued by the authorization endpoint by scrolling down the screen " +"and check the boxes labeled: :guilabel:`Access tokens (used for implicit " +"flows)` and :guilabel:`ID tokens (used for implicit and hybrid flows)`." +msgstr "" +"ถัดไป ประเภทของ *โทเค็น* ที่จำเป็นสำหรับการตรวจสอบสิทธิ์ OAuth จะถูกเลือก " +"สิ่งเหล่านี้ไม่ใช่โทเค็นสกุลเงิน " +"แต่เป็นโทเค็นการรับรองความถูกต้องที่ส่งผ่านระหว่าง Microsoft และ Odoo " +"ดังนั้นจึงไม่มีค่าใช้จ่ายสำหรับโทเค็นเหล่านี้ " +"ใช้เพื่อวัตถุประสงค์ในการตรวจสอบความถูกต้องระหว่างสอง :abbr:`API " +"(อินเทอร์เฟซการเขียนโปรแกรมแอปพลิเคชัน)` เท่านั้น " +"เลือกโทเค็นที่ควรออกโดยจุดสิ้นสุดการให้สิทธิ์โดยเลื่อนหน้าจอลงและทำเครื่องหมายในช่องที่มีป้ายกำกับ:" +" :guilabel:`โทเค็นการเข้าถึง (ใช้สำหรับการดำเนินการทางอ้อม)` และ " +":guilabel:`โทเค็น ID (ใช้สำหรับการดำเนินการทางอ้อมและไฮบริด) `." + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Authentication settings and endpoint tokens." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:96 +msgid "Click :guilabel:`Save` to ensure these settings are saved." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:99 +msgid "Gather credentials" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:101 +msgid "" +"With the application created and authenticated in the Microsoft Azure " +"console, credentials will be gathered next. To do so, click on the " +":guilabel:`Overview` menu item in the left-hand column. Select and copy the " +":guilabel:`Application (client) ID` in the window that appears. Paste this " +"credential to a clipboard / notepad, as this credential will be used in the " +"Odoo configuration later." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:106 +msgid "" +"After finishing this step, click on :guilabel:`Endpoints` on the top menu " +"and click the *copy icon* next to :guilabel:`OAuth 2.0 authorization " +"endpoint (v2)` field. Paste this value in the clipboard / notepad." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:115 +msgid "Odoo setup" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:117 +msgid "" +"Finally, the last step in the Microsoft Azure OAuth configuration is to " +"configure some settings in Odoo. Navigate to :menuselection:`Settings --> " +"Integrations --> OAuth Authentication` and check the box to activate the " +"OAuth login feature. Click :guilabel:`Save` to ensure the progress is saved." +" Then, sign in to the database once the login screen loads." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:122 +msgid "" +"Once again, navigate to :menuselection:`Settings --> Integrations --> OAuth " +"Authentication` and click on :guilabel:`OAuth Providers`. Now, select " +":guilabel:`New` in the upper-left corner and name the provider `Azure`." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:126 +msgid "" +"Paste the :guilabel:`Application (client) ID` from the previous section into" +" the :guilabel:`Client ID` field. After completing this, paste the new " +":guilabel:`OAuth 2.0 authorization endpoint (v2)` value into the " +":guilabel:`Authorization URL` field." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:130 +msgid "" +"For the :guilabel:`UserInfo URL` field, paste the following :abbr:`URL " +"(Uniform Resource Locator)`: `https://graph.microsoft.com/oidc/userinfo`" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:133 +msgid "" +"In the :guilabel:`Scope` field, paste the following value: `openid profile " +"email`. Next, the Windows logo can be used as the CSS class on the login " +"screen by entering the following value: `fa fa-fw fa-windows`, in the " +":guilabel:`CSS class` field." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:137 +msgid "" +"Check the box next to the :guilabel:`Allowed` field to enable the OAuth " +"provider. Finally, add `Microsoft Azure` to the :guilabel:`Login button " +"label` field. This text will appear next to the Windows logo on the login " +"page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Odoo provider setup in the Settings application." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:145 +msgid "" +":guilabel:`Save` the changes to complete the OAuth authentication setup in " +"Odoo." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:148 +msgid "User experience flows" +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:150 +msgid "" +"For a user to log in to Odoo using Microsoft Azure, the user must be on the " +":menuselection:`Odoo password reset page`. This is the only way that Odoo is" +" able to link the Microsoft Azure account and allow the user to log in." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:155 +msgid "" +"Existing users must :ref:`reset their password <users/reset-password>` to " +"access the :menuselection:`Odoo password reset page`. New Odoo users must " +"click the new user invitation link that was sent via email, then click on " +":guilabel:`Microsoft Azure`. Users should not set a new password." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:160 +msgid "" +"To sign in to Odoo for the first time using the Microsoft Azure OAuth " +"provider, navigate to the :menuselection:`Odoo password reset page` (using " +"the new user invitation link). A password reset page should appear. Then, " +"click on the option labeled :guilabel:`Microsoft Azure`. The page will " +"redirect to the Microsoft login page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Microsoft Outlook login page." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:169 +msgid "" +"Enter the :guilabel:`Microsoft Email Address` and click :guilabel:`Next`. " +"Follow the process to sign in to the account. Should :abbr:`2FA (Two Factor " +"Authentication)` be turned on, then an extra step may be required." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "Enter Microsoft login credentials." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst:177 +msgid "" +"Finally, after logging in to the account, the page will redirect to a " +"permissions page where the user will be prompted to :guilabel:`Accept` the " +"conditions that the Odoo application will access their Microsoft " +"information." +msgstr "" + +#: ../../content/applications/general/auth/azure.rst-1 +msgid "" +"Accept Microsoft conditions for permission access to your account " +"information." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:3 +msgid "Google Sign-In Authentication" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:5 +msgid "" +"The *Google Sign-In Authentication* is a useful function that allows Odoo " +"users to sign in to their database with their Google account." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:8 +msgid "" +"This is particularly helpful if the organization uses Google Workspace, and " +"wants employees within the organization to connect to Odoo using their " +"Google Accounts." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:12 +msgid "" +"Databases hosted on Odoo.com should not use Oauth login for the owner or " +"administrator of the database as it would unlink the database from their " +"Odoo.com account. If Oauth is set up for that user, the database will no " +"longer be able to be duplicated, renamed or otherwise managed from the " +"Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:18 +msgid ":doc:`/applications/productivity/calendar/google`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:19 +#: ../../content/applications/general/email_communication/email_servers.rst:66 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:26 +msgid "" +"The integration of the Google sign-in function requires configuration both " +"on Google *and* Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:31 +msgid "Google API Dashboard" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:33 +msgid "" +"Go to the `Google API Dashboard <https://console.developers.google.com/>`_." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:34 +msgid "" +"Make sure the right project is opened. If there isn't a project yet, click " +"on :guilabel:`Create Project`, fill out the project name and other details " +"of the company, and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the details of a new project." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:43 +msgid "Choose the name of the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:48 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:50 +msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Google OAuth consent selection menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:56 +msgid "" +"Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and" +" click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Choice of a user type in OAuth consent." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:64 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:68 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:71 +msgid "" +"Fill out the required details and domain info, then click on :guilabel:`Save" +" and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:72 +msgid "" +"On the :menuselection:`Scopes` page, leave all fields as is, and click on " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:74 +msgid "" +"Next, if continuing in testing mode (*External*), add the email addresses " +"being configured under the :guilabel:`Test users` step by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:77 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:82 +msgid "Credentials" +msgstr "ข้อมูลประจำตัว" + +#: ../../content/applications/general/auth/google.rst:84 +msgid "On the left side menu, click on :menuselection:`Credentials`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Credentials button menu." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:90 +msgid "" +"Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client " +"ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "OAuth client id selection." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:96 +msgid "" +"Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now," +" configure the allowed pages on which Odoo will be redirected." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:99 +msgid "" +"In order to achieve this, in the :guilabel:`Authorized redirect URIs` field," +" enter the database's domain immediately followed by `/auth_oauth/signin`. " +"For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:103 +msgid "" +"Now that the *OAuth client* has been created, a screen will appear with the " +":guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the " +":guilabel:`Client ID` for later, as it will be necessary for the " +"configuration in Odoo, which will be covered in the following steps." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:110 +msgid "Google Authentication on Odoo" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:115 +msgid "Retrieve the Client ID" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:117 +msgid "" +"Once the previous steps are complete, two keys are generated on the Google " +"API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the" +" :guilabel:`Client ID`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst-1 +msgid "Google OAuth Client ID generated." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:127 +msgid "Odoo activation" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:129 +msgid "" +"Go to :menuselection:`Odoo General Settings --> Integrations` and activate " +":guilabel:`OAuth Authentication`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:133 +msgid "Odoo may prompt the user to log-in again after this step." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:135 +msgid "" +"Go back to :menuselection:`General Settings --> Integrations --> OAuth " +"Authentication`, activate the selection and :guilabel:`Save`. Next, return " +"to :menuselection:`General Settings --> Integrations --> Google " +"Authentication` and activate the selection. Then fill out the " +":guilabel:`Client ID` with the key from the Google API Dashboard, and " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Filling out the client id in Odoo settings." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:145 +msgid "" +"Google OAuth2 configuration can also be accessed by clicking on " +":guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` " +"heading in :menuselection:`Integrations`." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:151 +msgid "Log in to Odoo with Google" +msgstr "" + +#: ../../content/applications/general/auth/google.rst:153 +msgid "" +"To link the Google account to the Odoo profile, click on :guilabel:`Log in " +"with Google` when first logging into Odoo." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:0 +msgid "Reset password screen with \"Log in with Google\" button." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:161 +msgid "" +"Existing users must :ref:`reset their password <users/reset-password>` to " +"access the :menuselection:`Reset Password` page, while new users can " +"directly click on :guilabel:`Log in with Google`, instead of choosing a new " +"password." +msgstr "" + +#: ../../content/applications/general/auth/google.rst:166 +msgid "" +"`Google Cloud Platform Console Help - Setting up OAuth 2.0 " +"<https://support.google.com/cloud/answer/6158849>`_" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:3 +msgid "Sign in with LDAP" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:5 +msgid "Install the LDAP module in General Settings." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:7 +msgid "Click on **Create** in Setup your LDAP Server." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:15 +msgid "Choose the company about to use the LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:20 +msgid "" +"In **Server Information**, enter the IP address of your server and the port " +"it listens to." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:22 +msgid "Tick **User TLS** if your server is compatible." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:27 +msgid "" +"In **Login Information**, enter ID and password of the account used to query" +" the server. If left empty, the server will be queried anonymously." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:32 +msgid "" +"In **Process Parameter**, enter the domain name of your LDAP server in LDAP " +"nomenclature (e.g. ``dc=example,dc=com``)." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:34 +msgid "In **LDAP filter**, enter ``uid=%s``" +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:39 +msgid "" +"In **User Information**, tick *Create User* if you want Odoo to create a " +"User profile the first time someone log in with LDAP." +msgstr "" + +#: ../../content/applications/general/auth/ldap.rst:41 +msgid "" +"In **Template User**, indicate a template for the new profiles created. If " +"left blanked, the admin profile will be used as template." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:5 +msgid "Developer Mode (debug mode)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:7 +msgid "" +"The developer mode (or debug mode) unlocks access to extra and advanced " +"tools in Odoo. There are several ways to activate the developer mode: " +"through the :ref:`settings <general/developer_mode/settings>`, the " +":ref:`browser extension <general/developer_mode/browser-extension>`, through" +" the :ref:`command palette <general/developer_mode/command-palette>` or the" +" :ref:`URL <general/developer_mode/url>`." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:17 +msgid "Activate through the Settings" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:19 +msgid "" +"The debug mode can be activated in the Odoo database settings. Go to " +":menuselection:`Settings --> General Settings --> Developer Tools` and click" +" on :guilabel:`Activate the developer mode`. At least one application needs " +"to be installed for the :guilabel:`Developer Tools` section to appear in the" +" :guilabel:`Settings` module." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of the debug options under settings in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:29 +msgid "" +":guilabel:`Activate the developer mode (with assets)` is used by developers;" +" :guilabel:`Activate the developer mode (with tests assets)` is used by " +"developers and testers." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:32 +msgid "" +"Once activated, the :guilabel:`Deactivate the developer mode` option becomes" +" available." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:37 +msgid "Activate through the browser extension" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:39 +msgid "" +"Within a web browser, navigate to the browser settings and extensions and " +"search for the `Odoo Debug` extension. Once the extension is installed, a " +"new icon will be shown on the browser's toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:43 +msgid "" +"For the *Odoo Debug* extension, a single click enables a normal version of " +"the mode, while a double click enables it with assets. To deactivate it, use" +" a single click." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "View of Odoo's debug icon in a Google Chrome toolbar." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:53 +msgid "Activate through the command palette" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:55 +msgid "" +"In Odoo, the command palette tool has a command to activate the debug mode. " +"First, open the command palette tool with the keyboard shortcut `ctrl+k` and" +" then type `debug`. A command will show up to activate the debug mode." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Command palette with debug command." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:68 +msgid "Activate through the URL" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:70 +msgid "" +"The debug mode can also be activated by adding an extra query string to the " +"database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To" +" deactivate the debug mode, change the value to `?debug=0` instead." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a URL with the debug mode command added." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:79 +msgid "" +"Additional modes are available for developers: `?debug=assets` enables the " +":ref:`assets mode <frontend/framework/assets_debug_mode>`, and " +"`?debug=tests` enables the :ref:`tests mode " +"<frontend/framework/tests_debug_mode>`." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:86 +msgid "Locate the developer mode tools" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:88 +msgid "" +"Once developer mode is activated, the developer mode tools can be accessed " +"from the :guilabel:`Open Developer Tools` button, the bug icon located in " +"the header of the Odoo database." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst-1 +msgid "Overview of a console page and the debug icon being shown in Odoo." +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:95 +msgid "" +"This menu contains additional tools that are useful to understand or edit " +"technical data, such as the views or actions of a page. On a page that has " +"filters, actions, and view options, the developer mode tools contain some " +"useful menu items such as:" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:99 +msgid ":guilabel:`Edit Action`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:100 +msgid ":guilabel:`Manage Filters`" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:101 +msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)" +msgstr "" + +#: ../../content/applications/general/developer_mode.rst:102 +msgid "See the :guilabel:`Fields View Get`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:3 +msgid "Digest Emails" +msgstr "อีเมลสรุป" + +#: ../../content/applications/general/digest_emails.rst:5 +msgid "" +"**Digest Emails** are periodic snapshots sent to your organization via email" +" that include high-level information about how your business is performing." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:8 +msgid "" +"Navigate to Digest Emails by going to :menuselection:`Settings --> General " +"Settings --> Statistics`, then activate the **Digest Emails** feature and " +"click on save." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Digest Emails section inside General Settings." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:15 +msgid "You can control a variety of settings for your Digest Emails, such as:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:17 +msgid "which KPIs are shared in the Digest" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:18 +msgid "how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:19 +msgid "who in your organization receives Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:20 +msgid "creating custom Digest Email templates" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:21 +msgid "adding additional KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:24 +msgid "" +"By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* " +"serves as the primary template, which includes all KPI measurements across " +"your Odoo database and is sent daily to administrators." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:31 +msgid "Customize *Your Odoo Periodic Digest*" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:33 +msgid "" +"To customize the default Digest Email (*Your Odoo Periodic Digest*), go to " +":menuselection:`Settings --> General Settings --> Statistics --> Digest " +"Email`, select *Your Odoo Periodic Digest* and click on the *external link* " +"next to the dropdown selection." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:37 +msgid "" +"A popup window appears and presents a variety of editable settings, which " +"include:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:39 +msgid "**Digest Title** - what you want your Digest Email to be called" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:40 +msgid "" +"**Periodicity** - control the regimen in how often Digest Emails are sent" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:41 +msgid "" +"**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:42 +msgid "**Recipients** - add/remove users who receive your Digest Emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:43 +msgid "**Custom** - add your own KPIs (Studio required)" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst-1 +msgid "Customize default Digest Email settings and custom KPIs." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:52 +msgid "Custom digest emails" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:54 +msgid "To do so, click on **Configure Digest Emails** and then **Create**." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:56 +msgid "" +"From there, give your Digest Email a title, specify periodicity, and choose " +"your desired KPIs and recipients fields as needed." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:59 +msgid "" +"After you click **Save**, your new custom Digest Email is available as a " +"selection in the **General Settings** dropdown menu." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:65 +msgid "Custom KPIs with Studio" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:67 +msgid "" +"For either *Your Odoo Periodic Digest* or your own custom Digest Email, you " +"can add your own KPIs by using Odoo Studio." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:70 +msgid "" +"To begin, click the **Toggle Studio** icon or click the **Recipients** tab " +"and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit " +"the template or add additional fields." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:73 +msgid "" +"In order to create additional fields, you must create two fields on the " +"digest object:" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:75 +msgid "" +"create a boolean field called `kpi_myfield` and display it in the KPIs tab" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:76 +msgid "" +"create a computed field called `kpi_myfield_value` that computes your " +"customized KPI" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:77 +msgid "select your KPI(s) in the KPIs tab." +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:80 +msgid "Computed values reference table" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "LABEL" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:83 +msgid "VALUE" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "Connected Users" +msgstr "ผู้ใช้ที่เชื่อมต่อ" + +#: ../../content/applications/general/digest_emails.rst:85 +msgid "`kpi_res_users_connected_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "Messages Sent" +msgstr "ส่งข้อความแล้ว" + +#: ../../content/applications/general/digest_emails.rst:87 +msgid "`kpi_mail_message_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "New Leads" +msgstr "ลูกค้าเป้าหมายใหม่" + +#: ../../content/applications/general/digest_emails.rst:89 +msgid "`kpi_crm_lead_created_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "Opportunities Won" +msgstr "โอกาสสำเร็จแล้ว" + +#: ../../content/applications/general/digest_emails.rst:91 +msgid "`kpi_crm_opportunities_won_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "Open Tasks" +msgstr "งานที่เปิดอยู่" + +#: ../../content/applications/general/digest_emails.rst:93 +msgid "`kpi_project_task_opened_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "Tickets Closed" +msgstr "ทิกเก็ตที่ปิดแล้ว" + +#: ../../content/applications/general/digest_emails.rst:95 +msgid "`kpi_helpdesk_tickets_closed_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "% of Happiness" +msgstr "% แห่งความสุข" + +#: ../../content/applications/general/digest_emails.rst:97 +msgid "`kpi_livechat_rating_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "Conversations handled" +msgstr "การสนทนาได้รับการจัดการแล้ว" + +#: ../../content/applications/general/digest_emails.rst:99 +msgid "`kpi_livechat_conversations_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "Time to answer (sec)" +msgstr "เวลาในการตอบ (วินาที)" + +#: ../../content/applications/general/digest_emails.rst:101 +msgid "`kpi_livechat_response_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "All Sales" +msgstr "ขายทั้งหมด" + +#: ../../content/applications/general/digest_emails.rst:103 +msgid "`kpi_all_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "eCommerce Sales" +msgstr "การขายอีคอมเมิร์ซ" + +#: ../../content/applications/general/digest_emails.rst:105 +msgid "`kpi_website_sale_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "Revenue" +msgstr "รายได้" + +#: ../../content/applications/general/digest_emails.rst:107 +msgid "`kpi_account_total_revenue_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "Bank & Cash Moves" +msgstr "การย้ายธนาคารและเงินสด" + +#: ../../content/applications/general/digest_emails.rst:109 +msgid "`kpi_account_bank_cash_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "POS Sales" +msgstr "การขายของระบบขายหน้าร้าน" + +#: ../../content/applications/general/digest_emails.rst:111 +msgid "`kpi_pos_total_value`" +msgstr "" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "New Employees" +msgstr "พนักงานใหม่" + +#: ../../content/applications/general/digest_emails.rst:113 +msgid "`kpi_hr_recruitment_new_colleagues_value`" +msgstr "" + +#: ../../content/applications/general/email_communication.rst:5 +msgid "Email Communication" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:3 +msgid "Configure DNS records to send emails in Odoo" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:6 +msgid "SPAM labels overview" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:8 +msgid "" +"Sometimes, emails from Odoo are misclassified by the different email " +"providers and end up in spam folders. At the moment, some settings are out " +"of Odoo's control, notably the way the different email providers classify " +"Odoo's emails according to their own restriction policy and/or limitations." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:12 +msgid "" +"It is standard in Odoo that emails are received from ``\"name of the " +"author\" <notifications@mycompany.odoo.com>``. In other words this can be " +"translated to: ``\"name of the author\" " +"<{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands " +"for `ir.config.parameters`, which are the System Parameters. Deliverability " +"is greatly improved with the :ref:`notifications configuration " +"<email_servers/notifications>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:18 +msgid "" +"In order for servers to accept emails from Odoo on a more regular basis, one" +" of the solutions is for customers to create rules within their own mailbox." +" A filter can be added to the email inbox so that when email is received " +"from Odoo (`notifications@mycompany.odoo.com`) it is moved to the inbox. It " +"is also possible to add the Odoo database domain onto a safe senders list or" +" whitelist on the receiving domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:24 +msgid "" +"If an Odoo email server appears on a blacklist, notify Odoo via a `new help " +"ticket <https://www.odoo.com/help>`_ and the support team will work to get " +"the servers removed from the blacklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:28 +msgid "" +"Should the Odoo database be using a custom domain for sending emails from " +"Odoo there are three records that should be implemented on the custom " +"domain's DNS to ensure deliverability of email. This includes setting " +"records for :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys " +"Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)`. Ultimately though, it is up to the discretion of" +" the final receiving mailbox." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:38 +msgid "Be SPF compliant" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:40 +msgid "" +"The Sender Policy Framework (SPF) protocol allows the owner of a domain name" +" to specify which servers are allowed to send emails from that domain. When " +"a server receives an incoming email, it checks whether the IP address of the" +" sending server is on the list of allowed IPs according to the sender's " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:46 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` verification is performed on the " +"domain mentioned in the `Return-Path` field of the email. In the case of an " +"email sent by Odoo, this domain corresponds to the value of the " +"`mail.catchall.domain` key in the database system parameters." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:50 +msgid "" +"The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a " +"TXT record. The way to create or modify a TXT record depends on the provider" +" hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In " +"order for the verification to work properly, each domain can only have one " +":abbr:`SPF (Sender Policy Framework)` record." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:55 +msgid "" +"If the domain name does not yet have a :abbr:`SPF (Sender Policy Framework)`" +" record, create one using the following input: `v=spf1 include:_spf.odoo.com" +" ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:58 +msgid "" +"If the domain name already has a :abbr:`SPF (Sender Policy Framework)` " +"record, the record must be updated (and do not create a new one)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:63 +msgid "" +"If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add " +"`include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com " +"include:_spf.google.com ~all`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:66 +msgid "" +"Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a " +"free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:72 +msgid "Enable DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:74 +msgid "" +"The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails " +"with a digital signature." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:77 +msgid "" +"When sending an email, the Odoo server includes a unique :abbr:`DKIM " +"(DomainKeys Identified Mail)` signature in the headers. The recipient's " +"server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified " +"Mail)` record in the database's domain name. If the signature and the key " +"contained in the record match, this guarantees that the message is authentic" +" and has not been altered during transport." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:83 +msgid "" +"To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME " +"(Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the" +" domain name:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:86 +msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:89 +msgid "" +"If the domain name is `mycompany.com`, make sure to create a subdomain " +"`odoo._domainkey.mycompany.com` whose canonical name is " +"`odoo._domainkey.odoo.com.`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:92 +msgid "" +"The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends " +"on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the " +"domain name. The most common providers are :ref:`listed below " +"<email_communication/SPFDKIM_common_providers>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:96 +msgid "" +"Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with " +"a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector " +"is asked, enter `odoo`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:100 +msgid "Check the DMARC policy" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:102 +msgid "" +"The Domain-based Message Authentication, Reporting, & Conformance (DMARC) " +"record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and " +":abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the" +" :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name tell the destination server what to do" +" with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)`" +" and/or :abbr:`DKIM (DomainKeys Identified Mail)` check." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:110 +msgid "DMARC: TXT record" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:112 +msgid "`v=DMARC1; p=none;`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:114 +msgid "" +"There are three :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` policies:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:117 +msgid "`p=none`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:118 +#: ../../content/applications/general/email_communication/email_domain.rst:171 +msgid "`p=quarantine`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:119 +msgid "`p=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:121 +msgid "" +"`p=quarantine` and `p=reject` instruct the server that receives an email to " +"quarantine that email or ignore it if the :abbr:`SPF (Sender Policy " +"Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:125 +msgid "" +"If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, " +"Reporting, & Conformance)` and has defined one of these policies, the domain" +" must be :abbr:`SPF (Sender Policy Framework)` compliant or enable " +":abbr:`DKIM (DomainKeys Identified Mail)`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:130 +msgid "" +"Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-" +"based Message Authentication, Reporting, & Conformance)` policy set to " +"`p=reject`. Odoo strongly advises against using an *@yahoo.com* or " +"*@aol.com* address for the database users. These emails will never reach " +"their recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:135 +msgid "" +"`p=none` is used for the domain owner to receive reports about entities " +"using their domain. It should not impact the deliverability if the " +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` check fails." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:139 +msgid "" +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` records are comprised of tags in the form of :abbr:`DNS " +"(Domain Name System)` records. These tags/parameters allow for reporting, " +"such as :abbr:`RUA (Reporting URI of aggregate reports)` and :abbr:`RUF " +"(Reporting URI for forensic reports)`, along with more precise specification" +" like :abbr:`PCT (Percentage of messages subjected to filtering)`, :abbr:`P " +"(Policy for organizational domain)`, :abbr:`SP (Policy for subdomains of the" +" OD)` :abbr:`ADKIM (Alignment mode for DKIM)` & :abbr:`ASPF (Alignment mode " +"for SPF)`. For best practice, the the :abbr:`DMARC (Domain-based Message " +"Authentication, Reporting, & Conformance)` policy should not start out being" +" too restrictive." +msgstr "" +":abbr:`บันทึก DMARC (การตรวจสอบข้อความตามโดเมน การรายงาน และความสอดคล้อง)` " +"ประกอบด้วยแท็กในรูปแบบของบันทึก :abbr:`DNS (Domain Name System)` " +"แท็ก/พารามิเตอร์เหล่านี้อนุญาตให้มีการรายงาน เช่น :abbr:`RUA (URI " +"การรายงานของรายงานรวม)` และ :abbr:`RUF (URI " +"การรายงานสำหรับรายงานทางนิติวิทยาศาสตร์)` พร้อมด้วยข้อกำหนดที่แม่นยำยิ่งขึ้น" +" เช่น :abbr:`PCT ( เปอร์เซ็นต์ของข้อความที่ต้องกรอง)`, :abbr:`P " +"(นโยบายสำหรับโดเมนองค์กร)`, :abbr:`SP (นโยบายสำหรับโดเมนย่อยของ OD)` " +":abbr:`ADKIM (โหมดการจัดตำแหน่งสำหรับ DKIM)` & : abbr:`ASPF " +"(โหมดการจัดตำแหน่งสำหรับ SPF)`. สำหรับแนวทางปฏิบัติที่ดีที่สุด นโยบาย " +":abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` ไม่ควรเริ่มต้นด้วยการเข้มงวดเกินไป" + +#: ../../content/applications/general/email_communication/email_domain.rst:148 +msgid "The following chart displays available tags:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:154 +msgid "Tag Name" +msgstr "ชื่อแท็ก" + +#: ../../content/applications/general/email_communication/email_domain.rst:155 +msgid "Purpose" +msgstr "เสนอ" + +#: ../../content/applications/general/email_communication/email_domain.rst:156 +msgid "Example" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:157 +msgid "v" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:158 +msgid "Protocol version" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:159 +msgid "`v=DMARC1`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:160 +msgid "pct" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:161 +msgid "Percentage of messages subjected to filtering" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:162 +msgid "`pct=20`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:163 +msgid "ruf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:164 +msgid "Reporting URI for forensic reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:165 +msgid "`ruf=mailto:authfail@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:166 +msgid "rua" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:167 +msgid "Reporting URI of aggregate reports" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:168 +msgid "`rua=mailto:aggrep@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:169 +msgid "p" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:170 +msgid "Policy for organizational domain" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:172 +msgid "sp" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:173 +msgid "Policy for subdomains of the OD" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:174 +msgid "`sp=reject`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:175 +msgid "adkim" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:176 +msgid "Alignment mode for DKIM" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:177 +msgid "`adkim=s`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:178 +msgid "aspf" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:179 +msgid "Alignment mode for SPF" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:180 +msgid "`aspf=r`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:182 +msgid "" +"Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & " +"Conformance)` record of a domain name with a tool like `MXToolbox DMARC " +"<https://mxtoolbox.com/DMARC.aspx>`_." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:186 +msgid "" +"`DMARC.org is another great resource to learn about DMARC records. " +"<https://dmarc.org/overview/>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:192 +msgid "SPF, DKIM & DMARC documentation of common providers" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:194 +msgid "" +"`OVH DNS " +"<https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:195 +msgid "" +"`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:196 +msgid "" +"`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:197 +msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:198 +msgid "" +"`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:199 +msgid "" +"`NameCheap " +"<https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-" +"do-i-add- txtspfdkimdmarc-records-for-my-domain/>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:201 +msgid "" +"`CloudFlare DNS <https://support.cloudflare.com/hc/en-" +"us/articles/360019093151>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:202 +msgid "" +"`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:203 +msgid "" +"`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-" +"portal>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:205 +msgid "" +"To fully test the configuration, use the `Mail-Tester <https://www.mail-" +"tester.com/>`_ tool, which gives a full overview of the content and " +"configuration in one sent email. Mail-Tester can also be used to configure " +"records for other, lesser-known providers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_domain.rst:210 +msgid "" +"`Using Mail-Tester to set SPF Records for specific carriers " +"<https://www.mail-tester.com/spf/>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:3 +msgid "Send and receive emails in Odoo with an email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:6 +msgid "Odoo Online or Odoo.sh users" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:8 +msgid "" +"Since **Odoo sets up its own mail servers for the database**, outgoing and " +"incoming emails already work out-of-the-box. So for **Odoo Online** and " +"**Odoo.sh** customers, nothing needs to be configured!" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:12 +msgid "" +"Unless an external mail server is required to send large batches of mass " +"emails, simply use the standard online Odoo database normally since it has " +"already been pre-configured to send email." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:16 +msgid "" +"The Odoo server is subject to a daily email limit to prevent abuse. The " +"default limit is 200 emails sent per day for databases with an " +"**Enterprise** subscription. This limit can be increased under certain " +"conditions. See the :doc:`FAQ <faq>` or contact support for more " +"information." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:22 +msgid "Scope of this documentation" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:24 +msgid "" +"This document is **mainly dedicated to Odoo on-premise databases** who don't" +" benefit from an out-of-the-box solution to send and receive emails in Odoo," +" unlike `Odoo Online <https://www.odoo. com/trial>`_ and `Odoo.sh " +"<https://www.odoo.sh>`_. Incoming and outgoing servers must be configured " +"for on-premise databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:29 +msgid "" +"The following sections below contain information on how to integrate an " +"external email server with Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:33 +msgid "" +"If no one in the company is employed to manage email servers, Odoo Online " +"and Odoo.sh are strongly recommended. In these Odoo hosting types email " +"sending and receiving works instantly and is monitored by professionals. " +"Nevertheless, a company can use their own email server if they want to " +"manage the email server's reputation themselves. For more information see " +":doc:`Configure DNS records to send emails in Odoo <email_domain>`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:42 +msgid "Default notifications system" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:44 +msgid "" +"Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, " +"etc.) have a discussion thread, called *chatter*." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:47 +msgid "" +"When a database user posts a message in the chatter, this message is sent by" +" email to the followers of the document as a notification (except to the " +"sender). If a follower replies to the message, the reply updates the " +"chatter, and Odoo relays another reply to the followers as a notification. " +"Messages sent back to the chatter from users or external users will appear " +"in the chatter from their respective email, or as the name listed in their " +"*Contacts* record." +msgstr "" +"เมื่อผู้ใช้ฐานข้อมูลโพสต์ข้อความในการแชท " +"ข้อความนี้จะถูกส่งทางอีเมลไปยังผู้ติดตามเอกสารเพื่อเป็นการแจ้งเตือน " +"(ยกเว้นถึงผู้ส่ง) หากผู้ติดตามตอบกลับข้อความ การตอบกลับจะอัปเดตการสนทนา และ " +"Odoo จะถ่ายทอดการตอบกลับอีกครั้งไปยังผู้ติดตามเป็นการแจ้งเตือน " +"ข้อความที่ส่งกลับไปยังแชทจากผู้ใช้หรือผู้ใช้ภายนอกจะปรากฏในการแชทจากอีเมลที่เกี่ยวข้อง" +" หรือเป็นชื่อที่แสดงอยู่ในบันทึก *ผู้ติดต่อ*" + +#: ../../content/applications/general/email_communication/email_servers.rst:53 +msgid "" +"These notifications are sent using a default from address. For more " +"information see :ref:`Use a default email address " +"<email_communication/default>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:57 +msgid "Manage outbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:59 +msgid "" +"As a system admin, go to :menuselection:`Settings --> General Settings --> " +"Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. " +"Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers`" +" and click :guilabel:`Create` to create a new outgoing mail server record in" +" Odoo. Reference the SMTP data of the external email server. Once all the " +"information has been filled out, click :guilabel:`Test Connection`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:70 +msgid "" +"Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, " +":abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based " +"Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS " +"(Domain Name System)` will improve deliverability. For more information see " +":doc:`email_domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:78 +msgid "Port restriction" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:80 +msgid "" +"Note that port 25 is blocked for security reasons on the Odoo Online and " +"Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:86 +msgid "Use a default \"From\" email address" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:88 +msgid "" +"Sometimes, an email's \"From\" (outgoing) address can belong to a different " +"domain, and that can be a problem." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:91 +msgid "" +"For example, if a customer with the email address " +"`mary\\@customer.example.com` responds to a message, Odoo will try to " +"redistribute that same email to the other subscribers in the thread. " +"However, if the domain `customer.example.com` forbids that kind of usage for" +" security, the email that Odoo is trying to redistribute would get rejected " +"by some recipients' email servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:96 +msgid "" +"To avoid that problem, Odoo sends all emails using a \"From\" address from " +"the same authorized domain." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:99 +msgid "" +"Access the :guilabel:`System Parameters` by activating :ref:`developer mode " +"<developer-mode>` and going to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:102 +msgid "" +"To force the email address from which emails are sent, a combination of the " +"following keys needs to be set in the system parameters of the database:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:105 +msgid "" +"`mail.default.from`: accepts the local part or a complete email address as " +"value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:106 +msgid "" +"`mail.default.from_filter`: accepts a domain name or a full email address as" +" value" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:109 +msgid "" +"The `mail.default.from_filter` works only for `odoo-bin` configurations or " +"the default Odoo email server, otherwise this parameter can be set using the" +" `from_filter` field on `ir.mail_server`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:112 +msgid "" +"The field can be a domain name or an entire email address, or it can remain " +"empty. If the sender's email address does not match this set filter, then " +"the email will be encapsulated using a combination of the two system " +"parameters: `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:117 +msgid "" +"In the following example, the from email address is replaced with the " +"combination of the the two system parameters (`mail.default.from` and " +"`mail.catchall.domain`). This is the default\\ notifications configuration " +"in Odoo: ``“Admin” <admin@example.com>`` => ``“Admin” " +"<notifications@mycompany.com>``." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:122 +msgid "" +"In other words if the email address of the author does not match " +"`mail.default.from_filter`, the email address is replaced by " +"`mail.default.from` (if it contains a full email address) or a combination " +"of `mail.default.from` and `mail.catchall.domain`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:126 +msgid "" +"If the `from_filter` contains a full email address, and if the " +"`mail.default.from` is the same as this address, then all of the email " +"addresses that are different from `mail.default.from` will be encapsulated " +"in `mail.default.from`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:133 +msgid "Utilizing the \"From\" filter on an outgoing email server" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:135 +msgid "" +"The :guilabel:`FROM Filtering` field allows for the use of a specific " +"outgoing email server depending on the :guilabel:`From` email address or " +"domain that Odoo is sending on behalf of. This setting can be used to " +"improve the deliverability or sending success rate of emails sent from the " +"database. Setting the :guilabel:`FROM Filtering` field can also be used to " +"send from different domains in a multi-company environment. Access this " +"field in Odoo by navigating to :menuselection:`Settings --> Discuss --> " +"Custom Mail Servers --> Outgoing Mail Servers --> New`." +msgstr "" +"ช่อง :guilabel:`การกรอง จาก` อนุญาตให้ใช้เซิร์ฟเวอร์อีเมลขาออกเฉพาะได้ " +"ขึ้นอยู่กับที่อยู่อีเมลหรือโดเมน :guilabel:`จาก` ที่ Odoo ส่งในนามของ " +"การตั้งค่านี้สามารถใช้เพื่อปรับปรุงความสามารถในการส่งหรืออัตราความสำเร็จในการส่งอีเมลที่ส่งจากฐานข้อมูล" +" การตั้งค่าช่อง :guilabel:`การกรอง จาก` " +"ยังสามารถใช้เพื่อส่งจากโดเมนที่แตกต่างกันในสภาพแวดล้อมที่มีหลายบริษัทได้ " +"เข้าถึงฟิลด์นี้ใน Odoo โดยไปที่ :menuselection:`การตั้งค่า --> แชท --> " +"เมลเซิร์ฟเวอร์แบบกำหนดเอง --> เซิร์ฟเวอร์เมลขาออก --> สร้าง`" + +#: ../../content/applications/general/email_communication/email_servers.rst-1 +msgid "Outgoing email server settings and the FROM filter settings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:146 +msgid "" +"When an email is sent from Odoo while the :guilabel:`FROM Filtering` field " +"is set, an email server is chosen in the following sequence:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:149 +msgid "" +"First, Odoo searches for an email server that has the same :guilabel:`FROM " +"Filtering` value as the :guilabel:`From` value (email address) defined in " +"the outgoing email. For example, if the :guilabel:`From` value (email " +"address) is `test\\@example.com`, only the email servers that have the " +":guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:153 +msgid "" +"However, if no email servers are found that use the :guilabel:`From` value, " +"then Odoo searches for an email server that has the same *domain* as the " +":guilabel:`From` value (email address) defined in the outgoing email. For " +"example, if the :guilabel:`From` email address is `test\\@example.com`, only" +" the email servers that have the :guilabel:`FROM Filtering` value equal to " +"`example.com` are returned." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:159 +msgid "" +"If no email servers are found after checking for the domain, then Odoo " +"returns all email servers that do not have any :guilabel:`FROM Filtering` " +"value(s) set." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:162 +msgid "" +"Should this query return no results, then Odoo performs a search for an " +"email server using the system parameter: `mail.default.from`. First, the " +"email address listed attempts to match an email server, and then the domain " +"attempts to find a match. If no email server is found, Odoo returns the " +"first outgoing email server (sorted by priority)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:168 +msgid "" +"If several email servers are found, then Odoo uses the first one according " +"to its priority. For example, if there are two email servers, one with a " +"priority of `10` and the other with a priority of `20`, then the email " +"server with a priority of `10` is used first." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:175 +msgid "Set up different dedicated servers for transactional and mass emails" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:177 +msgid "" +"In Odoo a separate email server can be used for transactional emails and " +"mass mailings. Example: Use Postmark or SendinBlue for transactional emails," +" and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet " +"</administration/maintain/mailjet_api>` for mass mailings." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:182 +msgid "" +"A default outgoing email server is already configured. Do not create an " +"alternative one unless a specific external outgoing email server is needed " +"for technical reasons." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:185 +msgid "" +"To do this, first activate the :ref:`developer mode <developer-mode>`, and " +"then go to :menuselection:`Settings --> Technical --> Outgoing` email " +"servers. There, create two outgoing email server settings; one for the " +"transactional emails and one for the mass mailing server. Make sure to give " +"priority to the transactional server over the mass mailing server by " +"providing a lower priority number for the transactional email server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:191 +msgid "" +"Now, go to :menuselection:`Email Marketing --> Settings` and enable " +":guilabel:`Dedicated Server`. Choose the appropriate email server. With " +"these settings, Odoo uses the server with the lower priority for " +"transactional emails, and the server here selected for mass mails. Note that" +" in this case, the domain's Sender Policy Framework (SPF) records must be " +"set to include both transactional and mass mail servers." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:198 +msgid ":doc:`email_domain`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:203 +msgid "Manage inbound messages" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:205 +msgid "Odoo relies on generic email aliases to fetch incoming messages." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:207 +msgid "" +"**Reply messages** of messages sent from Odoo are routed to their original " +"discussion thread (and to the inbox of all its followers) by the alias of " +"the model if there is any or by the catchall alias (**catchall@**). Replies " +"to messages of models that don't have a custom alias will use the catchall " +"alias (`catchall@mycompany.odoo.com`). The catchall address, however, does " +"not have another action attached to it like other aliases might, it is only " +"used to collect replies." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:212 +msgid "" +"**Bounced messages** are used as a Return-Path. One example this is " +"especially useful for is in `Odoo Email Marketing " +"<https://www.odoo.com/page/email-marketing>`__. In this case bounces are " +"opt-out based on if the email bounced too many times (5) in the last month " +"and the bounces are separated by one week. This is done to avoid " +"blacklisting someone because of a mail server error. If these circumstances " +"are met then the email is considered invalid and is blacklisted. A log note " +"is added on the contact under :guilabel:`Blacklisted Email Addresses` on the" +" :guilabel:`Email Marketing Configuration Menu`." +msgstr "" +"**ข้อความที่ถูกตีกลับ** ถูกใช้เป็นเส้นทางการกลับ " +"ตัวอย่างหนึ่งที่เป็นประโยชน์อย่างยิ่งคือใน `การตลาดผ่านอีเมล Odoo " +"<https://www.odoo.com/page/email-marketing>`__ ในกรณีนี้ " +"การตีกลับจะถูกเลือกไม่ใช้โดยขึ้นอยู่กับว่าอีเมลตีกลับหลายครั้งเกินไป (5) " +"ในเดือนที่ผ่านมาและการตีกลับแยกจากกันหนึ่งสัปดาห์ " +"การทำเช่นนี้เพื่อหลีกเลี่ยงการขึ้นบัญชีแบล็คลิสต์ใครบางคนเนื่องจากข้อผิดพลาดของเซิร์ฟเวอร์เมล" +" หากเป็นไปตามสถานการณ์เหล่านี้ " +"อีเมลจะถือว่าไม่ถูกต้องและอยู่ในบัญชีแบล็คลิสต์ " +"บันทึกบันทึกจะถูกเพิ่มลงในผู้ติดต่อภายใต้ " +":guilabel:`ที่อยู่อีเมลที่อยู่ในบัญชีแบล็คลิสต์` บน " +":guilabel:`เมนูการกำหนดค่าการตลาดผ่านอีเมล`" + +#: ../../content/applications/general/email_communication/email_servers.rst:220 +msgid "" +"Messages that bounce in the chatter (outside of Email Marketing) will " +"populate a red envelope indicating the failed delivery. This can be helpful " +"to know that a Sales Order or an Invoice did not reach its final " +"destination." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:223 +msgid "" +"**Original messages**: several business objects have their own alias to " +"create new records in Odoo from incoming emails:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:226 +msgid "" +"Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM " +"<https://www.odoo.com/page/ crm>`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:228 +msgid "" +"Support channel (to create *Tickets* in `Odoo Helpdesk " +"<https://www.odoo.com/page/helpdesk>`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:229 +msgid "" +"Projects (to create new *Tasks* in `Odoo Project <https://www.odoo.com/page " +"/project-management>`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:231 +msgid "" +"Job positions (to create *Applicants* in `Odoo Recruitment " +"<https://www.odoo.com/page /recruitment>`_)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:234 +msgid "" +"Depending on the mail server, there might be several methods to fetch " +"emails. The easiest and most recommended method is to manage one email " +"address per Odoo alias in the mail server." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:237 +msgid "" +"Create the corresponding email addresses in the mail server (**catchall@**, " +"**bounce@**, **sales@**, etc.)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:239 +msgid "" +"Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> " +"General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will " +"change the catchall's domain for the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:242 +msgid "" +"If the database's hosting type is Odoo on-premise, create an " +":guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new " +"incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail " +"Servers --> Incoming Mail Servers --> New` Fill out the form according to " +"the email provider's settings. Leave the :guilabel:`Actions to Perform on " +"Incoming Mails` field blank. Once all the information has been filled out, " +"click on :guilabel:`TEST & CONFIRM`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:0 +msgid "Incoming mail server configuration on Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:252 +msgid "" +"If the database's hosting type is Odoo Online or Odoo.sh, redirecting or " +"forwarding incoming messages to Odoo's domain name instead of the external " +"email server is recommended. That way, incoming messages can be received " +"without delay. Redirections for all email addresses should be set to Odoo's " +"domain name in the email server (e.g. `catchall\\@mydomain.ext` to " +"`catchall\\@mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:258 +msgid "" +"All the aliases are customizable in Odoo. Object aliases can be edited from " +"their respective configuration view by navigating to " +":menuselection:`Settings --> Technical Menu --> Email --> Aliases`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:262 +msgid "" +"To edit catchall and bounce aliases, first activate the :ref:`developer mode" +" <developer-mode>`. Then, go to :menuselection:`Settings --> Technical --> " +"Parameters --> System Parameters` to customize the aliases " +"(`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should" +" be completed prior to the database going live. If a customer replies after " +"a change is made then the system will not recognize the old alias and the " +"reply won't be received." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:268 +msgid "" +"By default, inbound messages are fetched every 5 minutes for on-premise " +"databases." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:271 +msgid "" +"This value can be changed in :ref:`developer mode <developer-mode>`. Go to " +":menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`" +" and look for :guilabel:`Mail: Fetchmail Service`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:276 +msgid "System parameters that prevent feedback loops" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:278 +msgid "" +"There are two system parameters that help prevent email loops from occurring" +" in Odoo. These parameters were introduced in Odoo 16 to prevent aliases " +"from creating too many records and to prevent feedback loops on the catchall" +" reply-to email address. They are present in database but not in the *System" +" Parameters*. To override the following defaults they need to be added in." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:283 +msgid "The two system parameters are as follows:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:285 +msgid "`mail.incoming.limit.period` (60 minutes by default)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:286 +msgid "`mail.incoming.limit.alias` (5 by default)" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:288 +msgid "" +"Add these fields in Odoo by first enabling :ref:`developer mode <developer-" +"mode>`, and then navigating to :menuselection:`Settings --> Technical Menu " +"--> Parameters --> System Parameters`. Change the value of these parameters," +" as needed." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:292 +msgid "" +"When an email is received in the Odoo database on the catchall email address" +" or on any alias, Odoo looks at the mail received for the given period of " +"time defined in the system parameter `mail.incoming.limit.period`. If the " +"received email was sent to an alias then Odoo will reference the " +"`mail.incoming.limit.alias` system parameter and determine the value as the " +"number of records this alias is allowed to create in the given period of " +"time (value of `mail.incoming.limit.period`)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:298 +msgid "" +"In addition, when email is received to the catchall email address, Odoo will" +" reference the emails received to the database during the set period of time" +" (as stated by the value in the system parameter: " +"`mail.incoming.limit.period`). Odoo will then determine whether any of the " +"emails received match that of the email(s) being received during the " +"specified time-frame, and will prevent a feedback loop from occurring if a " +"duplicate email is detected." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:3 +msgid "Email templates" +msgstr "เทมเพลตอีเมล" + +#: ../../content/applications/general/email_communication/email_template.rst:5 +msgid "" +"Email templates are saved emails that are used repeatedly to send emails " +"from the database. They allow users to send quality communications, without " +"having to compose the same text repeatedly." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:8 +msgid "" +"Creating different templates that are tailored to specific situations lets " +"users choose the right message for the right audience. This increases the " +"quality of the message and the overall engagement rate with the customer." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:13 +msgid "" +"Email templates in Odoo use QWeb or XML, which allows for editing emails in " +"their final rendering, making customizations more robust, without having to " +"edit any code whatsoever. This means that Odoo can use a Graphical User " +"Interface (GUI) to edit emails, which edits the backend code. When the " +"received email is read by the end user's program, different formatting and " +"graphics will appear in the final form of it." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:19 +msgid "" +"Access email templates in :ref:`developer mode <developer-mode>` by " +"navigating to :menuselection:`Settings app --> Technical menu --> Email --> " +"Email Templates`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:23 +msgid "Editing email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:25 +msgid "" +"The *powerbox* feature can be used when working with email templates. This " +"feature provides the ability to directly edit the formatting and text in an " +"email template, as well as the ability to add links, buttons, appointment " +"options, or images." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:29 +msgid "" +"Additionally, the XML/HTML code of the email template can be edited " +"directly, via the :guilabel:`</>` icon. Dynamic placeholders (referencing " +"fields within Odoo) are also available for use in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:34 +msgid "Powerbox" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:36 +msgid "" +"The *powerbox* feature is an enriched text editor with various formatting, " +"layout, and text options. It can also be used to add XML/HTML features in an" +" email template. The powerbox feature is activated by typing a forward slash" +" `/` in the body of the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:40 +msgid "" +"When a forward slash `/` is typed in the body of an email template, a drop-" +"down menu appears with the following options:" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:43 +msgid ":guilabel:`Structure`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:45 +msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:46 +msgid ":guilabel:`Numbered list`: Create a list with numbering." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:47 +msgid ":guilabel:`Checklist`: Track tasks with a checklist." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:48 +msgid ":guilabel:`Table`: Insert a table." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:49 +msgid ":guilabel:`Separator`: Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:50 +msgid ":guilabel:`Quote`: Add a blockquote section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:51 +msgid ":guilabel:`Code`: Add a code section." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:52 +msgid ":guilabel:`2 columns`: Convert into two columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:53 +msgid ":guilabel:`3 columns`: Convert into three columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:54 +msgid ":guilabel:`4 columns`: Convert into four columns." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:56 +msgid ":guilabel:`Format`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:58 +msgid ":guilabel:`Heading 1`: Big section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:59 +msgid ":guilabel:`Heading 2`: Medium section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:60 +msgid ":guilabel:`Heading 3`: Small section heading." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:61 +msgid ":guilabel:`Switch direction`: Switch the text's direction." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:62 +msgid ":guilabel:`Text`: Paragraph block." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:64 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:66 +msgid ":guilabel:`Image`: Insert an image." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:67 +msgid ":guilabel:`Article`: Link an article." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:69 +msgid ":guilabel:`Navigation`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:71 +msgid ":guilabel:`Link`: Add a link." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:72 +msgid ":guilabel:`Button`: Add a button." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:73 +msgid ":guilabel:`Appointment`: Add a specific appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:74 +msgid ":guilabel:`Calendar`: Schedule an appointment." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:76 +msgid ":guilabel:`Widgets`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:78 +msgid ":guilabel:`3 Stars`: Insert a rating over three stars." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:79 +msgid ":guilabel:`5 Stars`: Insert a rating over five stars." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:81 +msgid ":guilabel:`Basic Blocks`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:83 +msgid ":guilabel:`Signature`: Insert your signature." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:85 +msgid ":guilabel:`Marketing Tools`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:87 +msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:90 +msgid "" +"To use any of these options, click on the desired feature from the powerbox " +"drop-down menu. To format existing text with a text-related option (e.g. " +":guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the " +"text, then type in the activator key (forward slash) `/`, and select the " +"desired option from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:0 +msgid "Powerbox feature in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:100 +msgid "" +":ref:`Using dynamic placeholders <email_template/dynamic-placeholders>`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:103 +msgid "XML/HTML code editor" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:105 +msgid "" +"To access the XML/HTML editor for an email template, first enter " +":ref:`developer mode <developer-mode>`. Then, click the :guilabel:`</>` icon" +" in the upper-right corner of the template, and proceed to edit the " +"XML/HTML. To return to the standard text editor, click the :guilabel:`</>` " +"icon again." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "HTML editor in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:115 +msgid "" +"The XML/HTML editor should be accessed with caution as this is the backend " +"code of the template. Editing the code can cause the email template to break" +" immediately or when upgrading the database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:122 +msgid "Dynamic placeholders" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:124 +msgid "" +"*Dynamic placeholders* reference certain fields within the Odoo database to " +"produce unique data in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:128 +msgid "" +"Many companies like to customize their emails with a personalized piece of " +"customer information to grab attention. This can be accomplished in Odoo by " +"referencing a field within a model by inserting a dynamic placeholder. For " +"example, a customer's name can be referenced in the email from the " +":guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic" +" placeholder for this field is: `{{ object.partner_id }}`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:134 +msgid "" +"Dynamic placeholders are encoded to display fields from within the database." +" Dynamic placeholders can be used in the :guilabel:`Body` " +"(:guilabel:`Content` Tab) of the email template. They can also be used in " +"the fields present in the :guilabel:`Email Configuration` tab, the " +":guilabel:`Subject` of the email, and the :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:139 +msgid "" +"To use the dynamic placeholders in the :guilabel:`Body` of an email open the" +" **powerbox** feature by typing in `/` into the body of the email template " +"under the :guilabel:`Content` tab. Scroll to the bottom of the options list," +" to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic " +"Placeholder`. Then select the dynamic placeholder from a list of available " +"options and follow the prompts to configure it with the desired " +"corresponding Odoo field. Each dynamic placeholder will vary in " +"configuration." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Using dynamic placeholders in an email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:151 +msgid "" +"Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and " +":guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it " +"as a combination to the field that is being created." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:155 +msgid "" +"To search the available fields, simply type in the front-end name (on user-" +"interface) of the field in the search. This will find a result from all of " +"the available fields for the model that the email template is created for." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:160 +msgid "Customizing email templates are out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:163 +msgid "Rich text editor" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:165 +msgid "" +"A rich text editor toolbar can be accessed by highlighting text in the email" +" template. This can be used to change the heading, font size/style, color, " +"add a list type, or a link." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Rich text editor in the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:173 +msgid "Resetting email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:175 +msgid "" +"Should the email template not work because the code has been altered it can " +"be reset to restore it back to the out-of-box default template. Simply click" +" on the :guilabel:`Reset Template` button in the upper left-hand of the " +"screen and the template will be reset." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Resetting the email template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:184 +msgid "Default reply on email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:186 +msgid "" +"Under the :guilabel:`Email Configuration` tab on an email template, there is" +" a :guilabel:`Reply To` field. In this field, add email addresses to which " +"replies are redirected when sending emails en masse using this template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:191 +msgid "" +"Add multiple email addresses by adding a comma `,` between the addresses or " +"dynamic placeholders." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Reply-to field on template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:198 +msgid "" +"The :guilabel:`Reply To` field is **only** used for mass mailing (sending " +"emails in bulk). Bulk emails can be sent in almost every Odoo application " +"that has a list view option." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:201 +msgid "" +"To send mass mails, while in :guilabel:`list` view, check the boxes next to " +"the desired records where the emails are to be sent, click the " +":guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and" +" select the desired email option from the :guilabel:`Action` drop-down menu." +" Email options can vary by the particular list view and application." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:206 +msgid "" +"If it is possible to send an email, a mail composer pop-up window appears, " +"with values that can be defined and customized. This option will be " +"available on the :guilabel:`Action` button on pages where emails can be sent" +" in bulk---for example, on the :guilabel:`Customers` page of the CRM app. " +"This action occurs throughout the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Email composer in mass mailing mode with reply-to highlighted." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:216 +msgid "Transactional emails and corresponding URLs" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:218 +msgid "" +"In Odoo, multiple events can trigger the sending of automated emails. These " +"emails are known as *transactional emails*, and sometimes contain links " +"redirecting to the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:221 +msgid "" +"By default, links generated by the database use the dynamic `web.base.url` " +"key defined in the system parameters. For more information about this, see " +":ref:`system parameters <domain-name/web-base-url>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:225 +msgid "" +"If the *Website* application is not installed, the `web.base.url` key will " +"always be the default parameter used to generate all the links." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:229 +msgid "" +"The `web.base.url` key can only have a single value, meaning that, in a " +"multi-website or multi-company database environment, even if there is a " +"specific domain name for each website, the links generated to share a " +"document (or the links within a transactional email) may remain the same, " +"regardless of which website/company is related to the sending of the " +"email/document." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:235 +msgid "" +"If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is" +" equal to `https://www.mycompany.com` and there are two separate companies " +"in Odoo with different website URLs: `https://www.mycompany2.com` and " +"`https://www.mycompany1.com`, the links created by Odoo to share a document," +" or send a transactional email, come from the domain: " +"`https://www.mycompany.com`, regardless of which company sends the document " +"or email." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:241 +msgid "" +"This is not always the case, as some Odoo applications (*eCommerce*, for " +"example) have a link established in the database with the *Website* " +"application. In that case, if a specific domain is defined for the website, " +"the URL generated in the email template uses the domain defined on the " +"corresponding website of the company." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:247 +msgid "" +"When a customer makes a purchase on an Odoo *eCommerce* website, the order " +"has an established link with that website. As a result, the links in the " +"confirmation email sent to the customer use the domain name for that " +"specific website." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:252 +msgid "" +"A document shared using the *Documents* application will **always** use the " +"`web.base.url` key, as the document shared is not associated with any " +"particular website. This means that the URL will always be the same (the " +"`web.base.url` key value), no matter what company it's shared from. This is " +"a known limitation." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:257 +msgid "" +"For more information about how to configure domains, check out the " +":doc:`domain name documentation </administration/maintain/domain_names>`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:261 +msgid "Updating translations within email templates" +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:263 +msgid "" +"In Odoo, email templates are automatically translated for all users in the " +"database for all of the languages installed. Changing the translations " +"shouldn't be necessary. However, if for a specific reason, some of the " +"translations need to be changed, it can be done." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:268 +msgid "" +"Like any modification in the code, if translation changes are not done " +"correctly (for example, modifications leading to bad syntax), it can break " +"the template, and as a result, the template will appear blank." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:272 +msgid "" +"In order to edit translations, first enter :ref:`developer mode <developer-" +"mode>`. Then, on the email template, click on the :guilabel:`Edit` button, " +"and then click on the language button, represented by the initials of the " +"language currently being used (e.g. :guilabel:`EN` for English)." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Edit the language of a template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:281 +msgid "" +"If there aren't multiple languages installed and activated in the database, " +"or if the user does not have administration access rights, the language " +"button will not appear." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:284 +msgid "" +"A pop-up window with the different languages installed on the database " +"appears. From this pop-up, editing of translations is possible. When the " +"desired changes have been made, click the :guilabel:`Save` button to save " +"the changes." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst-1 +msgid "Translation of the body of the Appointment Booked template." +msgstr "" + +#: ../../content/applications/general/email_communication/email_template.rst:293 +msgid "" +"When editing the translations, the default language set in the database " +"appears in **bold**." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:3 +msgid "Email issues" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:5 +msgid "" +"This document contains an explanation of the most recurring emailing issues " +"in Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:8 +msgid "Outgoing emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:13 +msgid "Email is not sent" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:15 +msgid "" +"The first indicator showing that an email has not been sent is the presence " +"of a red :guilabel:`✉️ (envelope)` icon, next to the date and time of the " +"message, located in the chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Red envelope icon displayed in chatter." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:22 +msgid "" +"Unsent emails also appear in the Odoo email queue. In :ref:`developer mode " +"<developer-mode>`, the email queue can be accessed by going to " +":menuselection:`Settings app --> Technical menu --> Email --> Emails`. " +"Unsent emails appear in turquoise, while sent emails appear in grey." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:27 +msgid "Common error messages" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:32 +msgid "Daily limit reached" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Warning in Odoo upon email limit reached." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:38 +msgid "" +"Each email service provider has its own email sending limits. The limits may" +" be daily, hourly, or sometimes, per minute. This is the same for Odoo, " +"which limits a customer's sending to prevent Odoo's email servers from being" +" blacklisted." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:42 +msgid "Here are the default limits for new databases:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:44 +msgid "" +"**200 emails per day** for Odoo Online and Odoo.sh databases with an active " +"subscription." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:45 +msgid "**20 emails per day** for one-app free databases." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:46 +msgid "**50 emails per day** for trial databases." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:47 +msgid "" +"In the case of migration, the daily limit might be reset to 50 emails per " +"day." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:49 +msgid "If the daily limit is reached:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:51 +msgid "" +"Contact the Odoo support team, who may increase the daily limit depending on" +" the following factors:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:54 +msgid "How many users are in the database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:55 +msgid "Which apps are installed?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:56 +msgid "" +"The bounce rate: the percentage of email addresses that did not receive " +"emails because they were returned by a mail server on its way to the final " +"recipient." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:59 +msgid "" +"Use an external outgoing email server to be independent of Odoo's mail limit" +" (refer to the corresponding :doc:`email documentation " +"</applications/general/email_communication/email_servers>`)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:62 +msgid "" +"Wait until 11 PM (UTC) for the daily limit to reset, and retry sending the " +"email. In :ref:`developer mode <developer-mode>`, go to " +":menuselection:`Settings app --> Technical menu --> Email --> Emails`, then " +"click the :guilabel:`Retry` button next to an unsent email." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:67 +msgid "" +"The daily email limit is comprehensive to the database. By default, any " +"internal message, notification, logged note, etc. counts as an email in the " +"daily limit if it notifies someone via email. This can be mitigated by " +"receiving :ref:`notifications in Odoo " +"<discuss_app/notification_preferences>`, instead of emails." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:73 +msgid "SMTP error" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:75 +msgid "" +"Simple Mail Transport Protocol (SMTP) error messages explain why an email " +"wasn't transmitted successfully. :abbr:`SMTP (Simple Mail Transport " +"Protocol)` is a protocol to describe the email structure, and transmits data" +" from messages over the Internet. The error messages generated by email " +"services are helpful tools to diagnose and troubleshoot email problems." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:81 +msgid "" +"This is an example of a 554 SMTP permanent delivery error: `554: delivery " +"error: Sorry, your message to ------@yahoo.com cannot be delivered. This " +"mailbox is disabled (554.30). - mta4471.mail.bf1.yahoo.com --- Below this " +"line is a copy of the message.`" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:85 +msgid "" +"The debug menu can be used to investigate SMTP sending issues from a " +"database. To access the menu, :ref:`developer mode <developer-mode>` must be" +" activated. Once activated, navigate to the :menuselection:`Debug Menu` in " +"the top right of the menu bar (the :guilabel:`🐞 (bug)` icon), " +":menuselection:`Debug Menu --> Manage Messages`" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:90 +msgid "" +"The :guilabel:`Manage Messages` menu opens a list of all the messages sent " +"in a particular record. Within each message there is information on sending," +" including the type, and subtype, of the message." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:94 +msgid "" +"Other information includes to whom the message was sent, and whether Odoo " +"received a bounce-back message from an email server." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Manage messages menu option on the debug menu." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:102 +msgid "" +"A user must be on a view in Odoo that has a chatter in order for the " +":guilabel:`Manage Messages` menu option to appear." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:106 +msgid "No error populated" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:108 +msgid "" +"Odoo is not always capable of providing information for the reason it " +"failed. The different email providers implement a personalized policy of " +"bounced emails, and it is not always possible for Odoo to interpret it " +"correctly." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:112 +msgid "" +"If this is a recurring problem with the same client, or the same domain, do " +"not hesitate to contact `Odoo Support <https://www.odoo.com/help>`_ for help" +" in finding a reason." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:116 +msgid "" +"One of the most common reasons for an email failing to send with no error " +"message is related to :ref:`SPF <email_communication/spf_compliant>` and/or " +":ref:`DKIM <email_communication/DKIM_compliant>` configuration. Also, check " +"to make sure the `mail.bounce.alias` is defined in the *system parameters*. " +"Access system parameters in :ref:`developer mode <developer-mode>` by " +"navigating to :menuselection:`Settings app --> Technical menu --> Parameters" +" --> System Parameters`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:124 +msgid "Email is sent late" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:126 +msgid "" +"Email campaigns send at a scheduled time, using a delay pre-programed in the" +" database. Odoo uses a delayed task to send emails that are considered \"not" +" urgent\" (newsletter formats, such as: mass mailing, marketing automation, " +"and events). The system utility **cron** can be used to schedule programs to" +" run automatically at predetermined intervals. Odoo uses that policy in " +"order to avoid cluttering the mail servers and, instead, prioritizes " +"individual communication. This **cron** is called :guilabel:`Mail: Email " +"Queue Manager`, and can be accessed in :ref:`developer mode <developer-" +"mode>` by going to :menuselection:`Settings app --> Technical menu --> " +"Automation --> Scheduled Actions`." +msgstr "" +"แคมเปญอีเมลส่งตามเวลาที่กำหนด " +"โดยใช้การหน่วงเวลาที่ตั้งโปรแกรมไว้ล่วงหน้าในฐานข้อมูล Odoo " +"ใช้งานล่าช้าในการส่งอีเมลที่ถือว่า \"ไม่เร่งด่วน\" (รูปแบบจดหมายข่าว เช่น " +"การส่งจดหมายกลุ่ม ระบบการตลาดอัตโนมัติ และกิจกรรมต่างๆ) " +"สามารถใช้ยูทิลิตี้ระบบ **cron** " +"เพื่อกำหนดเวลาโปรแกรมให้ทำงานโดยอัตโนมัติตามช่วงเวลาที่กำหนดไว้ Odoo " +"ใช้นโยบายนั้นเพื่อหลีกเลี่ยงไม่ให้เมลเซิร์ฟเวอร์เกะกะ " +"และให้ความสำคัญกับการสื่อสารแต่ละรายการแทน **cron** นี้เรียกว่า " +":guilabel:`จดหมาย: ตัวจัดการคิวอีเมล` และสามารถเข้าถึงได้ใน " +":ref:`โหมดนักพัฒนาซอฟต์แวร์ ` โดยไปที่ :menuselection:`แอปการตั้งค่า --> " +"เมนูทางเทคนิค --> ระบบอัตโนมัติ - -> การดำเนินการตามกำหนดการ `" + +#: ../../content/applications/general/email_communication/faq.rst-1 +msgid "Email scheduled to be sent later." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:140 +msgid "" +"What is a **cron**? A cron is an action that Odoo runs in the background to " +"execute particular code to complete a task." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:144 +msgid "" +"By default, the *Mass Mailing cron* runs every 60 minutes. This can be " +"changed to no less than 5 minutes. However, running the action every 5 " +"minutes would bog down the Odoo database (stress the system), so this is not" +" recommended. To edit the mass mailing cron, select the scheduled action " +":guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary " +"adjustments." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:149 +msgid "" +"Emails that are considered urgent (communication from one person to another," +" such as sales orders, invoices, purchase orders, etc.) are sent " +"immediately." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:153 +msgid "Incoming emails" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:155 +msgid "" +"When there is an issue with incoming emails, there might not be an " +"indication, per se, in Odoo. It is the sending email client, who tries to " +"contact a database, that will get a bounce-back message (most of the time a " +":guilabel:`550: mailbox unavailable` error message)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:160 +msgid "Email is not received" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:162 +msgid "" +"The steps that should be taken depend on the Odoo platform where the " +"database is hosted." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:164 +msgid "" +"**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:166 +msgid "" +"Logs are a stored collection of all the tasks completed in a database. They " +"are a text-only representation, complete with timestamps of every action " +"taken on the Odoo database. This can be helpful to track emails leaving the " +"database. Failure to send can also be seen by logs that indicate that the " +"message tried to send repeatedly. Logs will show every action to the email " +"servers from the database." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:172 +msgid "" +"The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh " +"dashboard) of an Odoo.sh database contains a list of files containing the " +"logs of the database. The log files are created everyday at 5:00 AM (UTC)." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:177 +msgid "" +"The two most recent days (today and yesterday) are not compressed, while the" +" older ones are, in order to save space. The naming of the files for today " +"and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:181 +msgid "" +"For the following days, they are named with their dates, and then " +"compressed. Use the command :command:`grep` and :command:`zgrep` (for the " +"compressed ones) to search through the files." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:185 +msgid "" +"For more information on logs and how to access them via the Odoo.sh " +"dashboard, see :ref:`this administration documentation <odoosh/logs>`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:188 +msgid "" +"For more information on accessing logs via the command line visit :ref:`this" +" developer documentation <reference/cmdline/server/logging>`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:191 +msgid "" +"**Odoo Online** users won't have access to the logs. However `Odoo Support " +"<https://www.odoo.com/help>`_ can be contacted if there is a recurring issue" +" with the same client or domain." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:196 +msgid "Get help from Odoo support" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:198 +msgid "" +"In order to get helped efficiently, please provide as much information as " +"possible. Here is a list of what can be helpful when reaching out to the " +"Odoo Support team about an issue:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:201 +msgid "" +"Send a copy of the email headers. The `.EML` file (or **headers**) of the " +"email is the file format containing all the technical information required " +"for an investigation. The documentation from the email provider might " +"explain how to access the EML file/header files. Once the headers of the " +"email are obtained, adding it into the Odoo Support ticket is the most " +"efficient way for the Odoo Support team to investigate." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:208 +msgid "" +"`Gmail documentation on headers " +"<https://support.google.com/mail/answer/29436>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:209 +msgid "" +"`Outlook documentation on headers <https://support.microsoft.com/en-" +"us/office/view-internet-message-headers-in-outlook-" +"cd039382-dc6e-4264-ac74-c048563d212c#tab=Web>`_" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:212 +msgid "" +"Explain the exact flow that is being followed to normally receive those " +"emails in Odoo. Here are examples of questions whose answers can be useful:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:215 +msgid "Is this a notification message from a reply being received in Odoo?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:216 +msgid "Is this a message being sent from the Odoo database?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:217 +msgid "" +"Is there an incoming email server being used, or is the email somehow being " +"redirected?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:218 +msgid "Is there an example of an email that has been correctly forwarded?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:220 +msgid "Provide answers to the following questions:" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:222 +msgid "" +"Is it a generic issue, or is it specific to a use case? If specific to a use" +" case, which one exactly?" +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:224 +msgid "" +"Is it working as expected? In case the email is sent using Odoo, the bounce " +"email should reach the Odoo database, and display the :ref:`red envelope " +"<red_envelop>`." +msgstr "" + +#: ../../content/applications/general/email_communication/faq.rst:228 +msgid "" +"The bounce system parameter needs to be set in the technical settings in " +"order for the database to correctly receive bounce messages. To access this " +"setting, go to :menuselection:`Settings app --> Technical menu --> " +"Parameters --> System Parameters`. Then select the parameter name " +":guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't " +"already set." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:8 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:10 +msgid "" +"When working with a database, it sometimes is necessary to export your data " +"in a distinct file. Doing so can help to do reporting over your activities " +"(even if Odoo offers a precise and easy reporting tool with each available " +"application)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:14 +msgid "" +"With Odoo, you can export the values from any field in any record. To do so," +" activate the list view on the items that need to be exported, click on " +"*Action*, and, then, on *Export*." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "view of the different things to enable/click to export data" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:22 +msgid "" +"Pretty simple, this action still comes with some specificities. In fact, " +"when clicking on *Export*, a pop-up window appears with several options for " +"the data to export:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst-1 +msgid "" +"overview of all the options to take into account when exporting data in Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:30 +msgid "" +"With the *I want to update data* option ticked, the system only shows the " +"fields which can be imported. This is very helpful in case you want to " +"update existing records. Basically, this works like a filter. Leaving the " +"box unticked gives way more field options because it shows all the fields, " +"not just the ones which can be imported." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:36 +msgid "" +"When exporting, you can choose between two formats: .csv and .xls. With " +".csv, items are separated with a comma, while .xls holds information about " +"all the worksheets in a file, including both content and formatting." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:39 +msgid "" +"Those are the items you may want to export. Use the arrows to display more " +"sub-field options. Of course, you can use the search bar to find specific " +"fields more easily. To use the search option more efficiently, display all " +"the fields by clicking on all the arrows!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:44 +msgid "The + button is there to add fields to the \"to export\" list." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:45 +msgid "" +"The \"handles\" next to the selected fields allow you to move the fields up " +"and down to change the order in which they must be displayed in the exported" +" file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:48 +msgid "The trashcan is there if you need to remove fields." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:49 +msgid "" +"For recurring reports, it might be interesting to save export presets. " +"Select all the needed ones and click on the template bar. There, click on " +"*New template* and give a name to yours. The next time you need to export " +"the same list, simply select the related template." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:56 +msgid "" +"It’s good to keep the field’s external identifier in mind. For example, " +"*Related Company* is equal to *parent_id*. Doing so helps export only what " +"you would like to import next." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:63 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:66 +msgid "How to start" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:68 +msgid "" +"You can import data on any Odoo's business object using either Excel (.xlsx)" +" or CSV (.csv) formats: contacts, products, bank statements, journal entries" +" and even orders!" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:72 +msgid "" +"Open the view of the object you want to populate and click on " +":menuselection:`Favorites --> Import records`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:78 +msgid "" +"There you are provided with templates you can easily populate with your own " +"data. Such templates can be imported in one click; The data mapping is " +"already done." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:83 +msgid "How to adapt the template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:85 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:86 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:87 +#: ../../content/applications/general/export_import_data.rst:376 +msgid "" +"Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:92 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field in Odoo. Don't worry! You can map new " +"columns manually when you test the import. Search the list for the " +"corresponding field." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:100 +msgid "" +"Then, use this field's label in your file in order to make it work straight " +"on the very next time." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:104 +msgid "How to import from another application" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:106 +msgid "" +"In order to re-create relationships between different records, you should " +"use the unique identifier from the original application and map it to the " +"**ID** (External ID) column in Odoo. When you import another record that " +"links to the first one, use **XXX/ID** (XXX/External ID) to the original " +"unique identifier. You can also find this record using its name but you will" +" be stuck if at least 2 records have the same name." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:114 +msgid "" +"The **ID** will also be used to update the original import if you need to " +"re-import modified data later, it's thus good practice to specify it " +"whenever possible." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:120 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:122 +msgid "" +"Odoo tries to find with some heuristic, based on the first ten lines of the " +"files, the type of field for each column inside your file. For example if " +"you have a column only containing numbers, only the fields that are of type " +"*Integer* will be displayed for you to choose from. While this behavior " +"might be good and easy for most cases, it is also possible that it goes " +"wrong or that you want to map your column to a field that is not proposed by" +" default." +msgstr "" +"Odoo " +"พยายามค้นหาประเภทของฟิลด์สำหรับแต่ละคอลัมน์ในไฟล์ของคุณโดยอิงจากสิบบรรทัดแรกของไฟล์" +" ตัวอย่างเช่น หากคุณมีคอลัมน์ที่มีเฉพาะตัวเลข เฉพาะฟิลด์ที่เป็นประเภท " +"*จำนวนเต็ม* เท่านั้นที่จะแสดงให้คุณเลือก " +"แม้ว่าลักษณะการทำงานนี้อาจดีและง่ายสำหรับกรณีส่วนใหญ่ " +"แต่ก็อาจเป็นไปได้ว่าพฤติกรรมนี้อาจผิดพลาดหรือคุณต้องการแมปคอลัมน์ของคุณกับฟิลด์ที่ไม่ได้เสนอตามค่าเริ่มต้น" + +#: ../../content/applications/general/export_import_data.rst:131 +msgid "" +"If that happens, you just have to check the ** Show fields of relation " +"fields (advanced)** option, you will then be able to choose from the " +"complete list of fields for each column." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:139 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:141 +msgid "" +"Odoo can automatically detect if a column is a date, and it will try to " +"guess the date format from a set of most commonly used date formats. While " +"this process can work for many date formats, some date formats will not be " +"recognized. This can cause confusion due to day-month inversions; it is " +"difficult to guess which part of a date format is the day and which part is " +"the month in a date such as '01-03-2016'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:147 +msgid "" +"To view which date format Odoo has found from your file you can check the " +"**Date Format** that is shown when clicking on **Options** under the file " +"selector. If this format is incorrect you can change it to your liking using" +" the *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:152 +msgid "" +"If you are importing an excel (.xls, .xlsx) file, you can use date cells to " +"store dates as the display of dates in excel is different from the way it is" +" stored. That way you will be sure that the date format is correct in Odoo " +"whatever your locale date format is." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:157 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:159 +msgid "" +"Yes, we fully support numbers with parenthesis to represent negative sign as" +" well as numbers with currency sign attached to them. Odoo also " +"automatically detect which thousand/decimal separator you use (you can " +"change those under **options**). If you use a currency symbol that is not " +"known to Odoo, it might not be recognized as a number though and it will " +"crash." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:164 +msgid "" +"Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:166 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:167 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:168 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:169 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:170 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:171 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:172 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:174 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:176 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:177 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:180 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:182 +msgid "" +"By default the Import preview is set on commas as field separators and " +"quotation marks as text delimiters. If your csv file does not have these " +"settings, you can modify the File Format Options (displayed under the Browse" +" CSV file bar after you select your file)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:186 +msgid "" +"Note that if your CSV file has a tabulation as separator, Odoo will not " +"detect the separations. You will need to change the file format options in " +"your spreadsheet application. See the following question." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:191 +msgid "" +"How can I change the CSV file format options when saving in my spreadsheet " +"application?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:193 +msgid "" +"If you edit and save CSV files in spreadsheet applications, your computer's " +"regional settings will be applied for the separator and delimiter. We " +"suggest you use OpenOffice or LibreOffice Calc as they will allow you to " +"modify all three options (in :menuselection:`'Save As' dialog box --> Check " +"the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:198 +msgid "" +"Microsoft Excel will allow you to modify only the encoding when saving (in " +":menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> " +"Encoding tab`)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:202 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:204 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When you" +" want to import such fields, Odoo will have to recreate links between the " +"different records. To help you import such fields, Odoo provides three " +"mechanisms. You must use one and only one mechanism per field you want to " +"import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:209 +msgid "" +"For example, to reference the country of a contact, Odoo proposes you 3 " +"different fields to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:211 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:212 +msgid "" +"Country/Database ID: the unique Odoo ID for a record, defined by the ID " +"postgresql column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:213 +msgid "" +"Country/External ID: the ID of this record referenced in another application" +" (or the .XML file that imported it)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:216 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:218 +msgid "Country: Belgium" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:219 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:220 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:222 +msgid "" +"According to your need, you should use one of these 3 ways to reference " +"records in relations. Here is when you should use one or the other, " +"according to your need:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:225 +msgid "" +"Use Country: This is the easiest way when your data come from CSV files that" +" have been created manually." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:227 +msgid "" +"Use Country/Database ID: You should rarely use this notation. It's mostly " +"used by developers as it's main advantage is to never have conflicts (you " +"may have several records with the same name, but they always have a unique " +"Database ID)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:230 +msgid "" +"Use Country/External ID: Use External ID when you import data from a third " +"party application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:232 +msgid "" +"When you use External IDs, you can import CSV files with the \"External ID\"" +" column to define the External ID of each record you import. Then, you will " +"be able to make a reference to that record with columns like " +"\"Field/External ID\". The following two CSV files give you an example for " +"Products and their Categories." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:237 +msgid "" +":download:`CSV file for categories " +"<export_import_data/External_id_3rd_party_application_product_categories.csv>`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:240 +msgid "" +":download:`CSV file for Products " +"<export_import_data/External_id_3rd_party_application_products.csv>`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:244 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:246 +msgid "" +"If for example you have two product categories with the child name " +"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other " +"Products/Sellable\"), your validation is halted but you may still import " +"your data. However, we recommend you do not import the data because they " +"will all be linked to the first 'Sellable' category found in the Product " +"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of " +"the duplicates' values or your product category hierarchy." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:252 +msgid "" +"However if you do not wish to change your configuration of product " +"categories, we recommend you use make use of the external ID for this field " +"'Category'." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:256 +msgid "" +"How can I import a many2many relationship field (e.g. a customer that has " +"multiple tags)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:258 +msgid "" +"The tags should be separated by a comma without any spacing. For example, if" +" you want your customer to be linked to both tags 'Manufacturer' and " +"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column" +" of your CSV file." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:262 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"<export_import_data/m2m_customers_tags.csv>`" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:266 +msgid "" +"How can I import a one2many relationship (e.g. several Order Lines of a " +"Sales Order)?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:268 +msgid "" +"If you want to import sales order having several order lines; for each order" +" line, you need to reserve a specific row in the CSV file. The first order " +"line will be imported on the same row as the information relative to order. " +"Any additional lines will need an additional row that does not have any " +"information in the fields relative to the order. As an example, here is " +"``purchase.order_functional_error_line_cant_adpat.CSV`` file of some " +"quotations you can import, based on demo data." +msgstr "" +"หากคุณต้องการนำเข้าใบสั่งขายที่มีรายการใบสั่งหลายรายการ " +"สำหรับแต่ละบรรทัดคำสั่งซื้อ คุณจะต้องจองแถวที่ต้องการในไฟล์ CSV " +"บรรทัดคำสั่งซื้อแรกจะถูกนำเข้าในแถวเดียวกันกับข้อมูลที่สัมพันธ์กับคำสั่งซื้อ" +" บรรทัดเพิ่มเติม จะต้องมีแถวเพิ่มเติมที่ไม่มีข้อมูลใดๆ " +"ในฟิลด์ที่เกี่ยวข้องกับคำสั่งซื้อ ตามตัวอย่าง นี่คือไฟล์ " +"``purchase.order_function_error_line_cant_adpat.CSV`` " +"ของใบเสนอราคาบางรายการที่คุณสามารถนำเข้าได้ โดยอิงตามข้อมูลสาธิต" + +#: ../../content/applications/general/export_import_data.rst:275 +msgid "" +":download:`File for some Quotations " +"<export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:277 +msgid "" +"The following CSV file shows how to import purchase orders with their " +"respective purchase order lines:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:280 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"<export_import_data/o2m_purchase_order_lines.csv>`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:282 +msgid "" +"The following CSV file shows how to import customers and their respective " +"contacts:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:284 +msgid "" +":download:`Customers and their respective contacts " +"<export_import_data/o2m_customers_contacts.csv>`." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:287 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:289 +msgid "" +"If you import a file that contains one of the column \"External ID\" or " +"\"Database ID\", records that have already been imported will be modified " +"instead of being created. This is very useful as it allows you to import " +"several times the same CSV file while having made some changes in between " +"two imports. Odoo will take care of creating or modifying each record " +"depending if it's new or not." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:294 +msgid "" +"This feature allows you to use the Import/Export tool of Odoo to modify a " +"batch of records in your favorite spreadsheet application." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:298 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:300 +msgid "" +"If you do not set all fields in your CSV file, Odoo will assign the default " +"value for every non defined fields. But if you set fields with empty values " +"in your CSV file, Odoo will set the EMPTY value in the field, instead of " +"assigning the default value." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:305 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:307 +msgid "" +"If you need to import data from different tables, you will have to recreate " +"relations between records belonging to different tables. (e.g. if you import" +" companies and persons, you will have to recreate the link between each " +"person and the company they work for)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:311 +msgid "" +"To manage relations between tables, you can use the \"External ID\" " +"facilities of Odoo. The \"External ID\" of a record is the unique identifier" +" of this record in another application. This \"External ID\" must be unique " +"across all the records of all objects, so it's a good practice to prefix " +"this \"External ID\" with the name of the application or table. (like " +"'company_1', 'person_1' instead of '1')" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:317 +msgid "" +"As an example, suppose you have a SQL database with two tables you want to " +"import: companies and persons. Each person belong to one company, so you " +"will have to recreate the link between a person and the company he work for." +" (If you want to test this example, here is a :download:`dump of such a " +"PostgreSQL database <export_import_data/database_import_test.sql>`)" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:322 +msgid "" +"We will first export all companies and their \"External ID\". In PSQL, write" +" the following command:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:328 +msgid "This SQL command will create the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:337 +msgid "" +"To create the CSV file for persons, linked to companies, we will use the " +"following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:343 +msgid "It will produce the following CSV file:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:353 +msgid "" +"As you can see in this file, Fabien and Laurence are working for the Bigees " +"company (company_1) and Eric is working for the Organi company. The relation" +" between persons and companies is done using the External ID of the " +"companies. We had to prefix the \"External ID\" by the name of the table to " +"avoid a conflict of ID between persons and companies (person_1 and company_1" +" who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:359 +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 "" + +#: ../../content/applications/general/export_import_data.rst:364 +msgid "How to adapt an import template" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:366 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). You can open them with " +"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, " +"etc.)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:372 +msgid "How to customize the file" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:374 +msgid "" +"Remove columns you don't need. We advise to not remove the *ID* one (see why" +" here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:381 +msgid "" +"When you add a new column, Odoo might not be able to map it automatically if" +" its label doesn't fit any field of the system. If so, find the " +"corresponding field using the search." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:388 +msgid "" +"Then, use the label you found in your import template in order to make it " +"work straight away the very next time you try to import." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:392 +msgid "Why an “ID” column" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:394 +msgid "" +"The **ID** (External ID) is an unique identifier for the line item. Feel " +"free to use the one of your previous software to ease the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:397 +msgid "" +"Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:399 +msgid "" +"Update imports: you can import the same file several times without creating " +"duplicates;" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:400 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:403 +msgid "How to import relation fields" +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:405 +msgid "" +"An Odoo object is always related to many other objects (e.g. a product is " +"linked to product categories, attributes, vendors, etc.). To import those " +"relations you need to import the records of the related object first from " +"their own list menu." +msgstr "" + +#: ../../content/applications/general/export_import_data.rst:409 +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 "" + +#: ../../content/applications/general/in_app_purchase.rst:3 +msgid "In-App Purchase (IAP)" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:5 +msgid "" +"In-App Purchases (IAP) gives access to additional services through Odoo. For" +" instance, it allows you to send SMS Text Messages or to send Invoices by " +"post directly from your database." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:11 +msgid "Buying Credits" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:13 +msgid "" +"Each IAP Service relies on prepaid credits to work and has its own pricing. " +"To consult your current balance or to recharge your account, go to " +":menuselection:`Settings --> Odoo IAP --> View my Services`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:21 +msgid "" +"If you are on Odoo Online and have the Enterprise version, you benefit from " +"free credits to test our IAP features." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:25 +msgid "IAP accounts" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:27 +msgid "" +"Credits to use IAP services are stored on IAP accounts, which are specific " +"to each service. By default, IAP accounts are common to all companies, but " +"can be restricted to specific ones. Activate the :ref:`developer mode " +"<developer-mode>`, then go to :menuselection:`Technical Settings --> IAP " +"Account`." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:36 +msgid "" +"An IAP account can be disabled by appending `+disabled` to its token. " +"Reverting this change will re-enable the account." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:40 +msgid "IAP Portal" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:42 +msgid "" +"The IAP Portal is a platform regrouping your IAP Services. It is accessible " +"from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From " +"there, you can view your current balance, recharge your credits and set a " +"reminder when your balance falls below a threshold." +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:50 +msgid "Get notified when credits are low" +msgstr "" + +#: ../../content/applications/general/in_app_purchase.rst:52 +msgid "" +"To be notified when it’s time to recharge your credits, you can go to your " +"IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my " +"Services`, unfold a service and check the Receive threshold warning option. " +"Then, you can provide a minimum amount of credits and email addresses. Now, " +"every time that the limit is reached, an automatic reminder will be sent by " +"email!" +msgstr "" + +#: ../../content/applications/general/reporting.rst:3 +msgid "Reporting" +msgstr "การรายงาน" + +#: ../../content/applications/general/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/general/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/general/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:22 +msgid "" +"The :ref:`graph view <reporting/using-graph>` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/general/reporting.rst-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:35 +msgid "" +"The :ref:`pivot view <reporting/using-pivot>` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/general/reporting.rst-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered <search>`. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/general/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"<studio/fields/simple-fields/integer>`, :ref:`decimal <studio/fields/simple-" +"fields/decimal>`, :ref:`monetary <studio/fields/simple-fields/monetary>`) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/general/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped <search/group>` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/general/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/general/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/general/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/general/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/general/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/general/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/general/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/general/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/general/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/general/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/general/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/general/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:169 +#: ../../content/applications/general/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/general/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/general/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/general/search.rst:3 +msgid "Search and filter records" +msgstr "" + +#: ../../content/applications/general/search.rst:5 +msgid "" +"Odoo uses filters to include only the most relevant records depending on the" +" purpose of the view you are on. However, you can edit the default filter or" +" search for specific values." +msgstr "" + +#: ../../content/applications/general/search.rst:11 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/general/search.rst:13 +msgid "" +"You can modify the default selection of records by clicking " +":guilabel:`Filters` and selecting one or several **preconfigured filters**." +msgstr "" + +#: ../../content/applications/general/search.rst:17 +msgid "" +"On the Sales Analysis report, only records at the sales order stage are " +"selected by default. However, you could *also* include records at the " +"quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could " +"*only* include records from a specific year, for example *2022*, by " +"selecting :menuselection:`Order Date --> 2022`." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:27 +msgid "" +"If you select preconfigured filters from the same group (i.e., that are " +"*not* separated by an horizontal line), the records can match *any* " +"condition to be included. However, if you select filters from different " +"groups, the records have to match *all* condition to be included." +msgstr "" + +#: ../../content/applications/general/search.rst:34 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/general/search.rst:36 +msgid "" +"You can create custom filters using most fields present on the model by " +"clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, " +"an operator, a value, and clicking :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/search.rst:41 +msgid "" +"You could *only* include records from a single salesperson on the Sales " +"Analysis report, for example *Mitchell Admin*, by selecting " +":guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the " +"operator, and typing `Mitchell Admin` as the value." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Using a custom filter on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:50 +msgid "" +"If the records should *only* match one of several conditions, click " +":guilabel:`Add a condition` before applying a custom filter. If the records " +"should match *all* conditions, add new custom filters instead." +msgstr "" + +#: ../../content/applications/general/search.rst:57 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/general/search.rst:59 +msgid "" +"You can use the search field to quickly look for specific values and add " +"them as a filter. Either type the full value you are searching for and " +"select the desired field, or type a part of the value, click the dropdown " +"button (:guilabel:`⏵`) before the chosen field, and select the exact value " +"you are looking for." +msgstr "" + +#: ../../content/applications/general/search.rst:65 +msgid "" +"Instead of adding a custom filter to select records where *Mitchell Admin* " +"is the salesperson on the Sales Analysis report, you could search for " +"`Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search" +" Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:75 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a custom filter. If you enter a partial value and directly select the" +" desired field, *all* records containing the characters you typed for the " +"selected field will be included." +msgstr "" + +#: ../../content/applications/general/search.rst:82 +msgid "Group records" +msgstr "" + +#: ../../content/applications/general/search.rst:84 +msgid "" +"You can click :guilabel:`Group By` below the search field to cluster records" +" together according to one of the **preconfigured groups**." +msgstr "" + +#: ../../content/applications/general/search.rst:88 +msgid "" +"You could group the records by salesperson on the Sales Analysis report by " +"clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No " +"records are filtered out." +msgstr "" + +#: ../../content/applications/general/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/general/search.rst:95 +msgid "" +"You can **customize groups** by using a wide selection of fields present on " +"the model. To do so, click :menuselection:`Group By --> Add Custom Group`, " +"select a field, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/search.rst:99 +msgid "" +"You can use several groups at the same time. The first group you select is " +"the main cluster, the next one you add further divides the main group's " +"categories, and so on." +msgstr "" + +#: ../../content/applications/general/users.rst:5 +msgid "Users and companies" +msgstr "" + +#: ../../content/applications/general/users.rst:7 +msgid "" +"Odoo defines a *user* as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:3 +msgid "Access Rights" +msgstr "สิทธิ์การเข้าใช้งาน" + +#: ../../content/applications/general/users/access_rights.rst:5 +msgid "" +"Activate the :ref:`developer mode <developer-mode>`, then go to " +":menuselection:`Settings --> Users & Companies --> Groups`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:9 +msgid "Groups" +msgstr "กลุ่ม" + +#: ../../content/applications/general/users/access_rights.rst:14 +msgid "" +"When choosing the groups the user can have access under :ref:`Access Rights " +"<users/add-individual>`, details of the rules and inheritances of that group" +" are not shown, so this is when the menu *Groups* comes along. *Groups* are " +"created to define rules to models within an application." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:16 +msgid "" +"Under *Users*, have a list of the current ones. The ones with administrative" +" rights are shown in black." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab users in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:22 +msgid "" +"*Inherited* means that users added to this application group are " +"automatically added to the following ones. In the example below, users who " +"have access to the group *Administrator* of *Sales* also have access to " +"*Website/Restricted Editor* and *Sales/User: All Documents*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab inherited in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:32 +msgid "" +"Remember to always test the settings being changed in order to ensure that " +"they are being applied to the needed and right users." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:35 +msgid "" +"The *Menus* tab is where you define which menus (models) the user can have " +"access to." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab menus in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:42 +msgid "" +"*Access Rights* rules are the first level of rights. The field is composed " +"of the object name, which is the technical name given to a model. For each " +"model, enable the following options as appropriate:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:45 +msgid "*Read*: the values of that object can be only seen by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:46 +msgid "*Write*: the values of that object can be edited by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:47 +msgid "*Create*: values for that object can be created by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:48 +msgid "*Delete*: the values of that object can be deleted by the user." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab access rights in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:55 +msgid "" +"As a second layer of editing and visibility rules, *Record Rules* can be " +"formed. They overwrite, or refine, the *Access Rights*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:58 +msgid "" +"A record rule is written using a *Domain*. Domains are conditions used to " +"filter or searching data. Therefore, a domain expression is a list of " +"conditions. For each rule, choose among the following options: *Read*, " +"*Write*, *Create* and *Delete* values." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst-1 +msgid "View of a group’s form emphasizing the tab record rules in Odoo" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:65 +msgid "" +"Making changes in access rights can have a big impact on the database. For " +"this reason, we recommend you to contact your Odoo Business Analyst or our " +"Support Team, unless you have knowledge about Domains in Odoo." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:3 +msgid "Companies" +msgstr "บริษัท" + +#: ../../content/applications/general/users/companies.rst:5 +msgid "" +"A centralized management environment allows you to select multiple companies" +" simultaneously and set their specific warehouses, customers, equipment, and" +" contacts. It provides you the ability to generate reports of aggregated " +"figures without switching interfaces, which facilitates daily tasks and the " +"overall management process." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:13 +msgid "Manage companies and records" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:15 +msgid "" +"Go to :menuselection:`Settings --> Manage Companies` and fill in the form " +"with your company’s information. If a *Parent Company* is selected, records " +"are shared between the two companies (as long as both environments are " +"active)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "Overview of a new company's form in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:24 +msgid "" +"Activate the :ref:`developer mode <developer-mode>` to choose a *Favicon* " +"for each of your companies, and easily identify them by the browser tabs. " +"Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and " +"ICO are extensions accepted." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:0 +msgid "" +"View of a web browser and the favicon for a specific company chosen in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:33 +msgid "" +"Switch between or select multiple companies by enabling their selection " +"boxes to activate them. The grayed company is the one which environment is " +"in use. To switch environments, click on the company’s name. In the example " +"below, the user has access to three companies, two are activated, and the " +"environment in use is of *JS Store US*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of the companies menu through the main dashboard in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:42 +msgid "" +"Data such as Products, Contacts, and Equipment can be shared or set to be " +"shown for a specific company only. To do so, on their forms, choose between:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:45 +msgid "*A blank field*: the record is shared within all companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:46 +msgid "" +"*Adding a company*: the record is visible to users logged in to that " +"specific company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of a product's form emphasizing the company field in Odoo Sales" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:53 +msgid "Employees' access" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:55 +msgid "" +"Once companies are created, manage your employees' :doc:`Access Rights " +"<access_rights>` for *Multi Companies*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of an user form emphasizing the multi companies field under the access rights tabs\n" +"in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:64 +msgid "" +"If a user has multiple companies *activated* on his database, and he is " +"**editing** a record, the editing happens on the record's related company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:67 +msgid "" +"Example: if editing a sale order issued under JS Store US while working on " +"the JS Store Belgium environment, the changes are applied under JS Store US " +"(the company from which the sale order was issued)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:68 +msgid "When **creating** a record, the company taken into account is:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:70 +msgid "The current company (the one active) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:71 +msgid "No company is set (on products and contacts’ forms for example) or," +msgstr "" + +#: ../../content/applications/general/users/companies.rst:72 +msgid "" +"The company set is the one linked to the document (the same as if a record " +"is being edited)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:75 +msgid "Documents’ format" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:77 +msgid "" +"To set documents' formats according to each company, *activate* and *select*" +" the respective one and, under *Settings*, click on *Configure Document " +"Layout*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the document layout field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:85 +msgid "Inter-Company Transactions" +msgstr "ธุรกรรมระหว่าง บริษัท" + +#: ../../content/applications/general/users/companies.rst:87 +msgid "" +"First, make sure each one of your companies is properly set in relation to:" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:89 +msgid "" +":doc:`Chart of Accounts " +"<../../finance/accounting/get_started/chart_of_accounts>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:90 +msgid ":doc:`Taxes <../../finance/accounting/taxes>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:91 +msgid "" +":doc:`Fiscal Positions <../../finance/accounting/taxes/fiscal_positions>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:92 +msgid ":doc:`Journals <../../finance/accounting/bank>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:93 +msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:94 +msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:96 +msgid "" +"Now, activate the *Inter-Company Transactions* option under *Settings*. With" +" the respective company *activated* and *selected*, choose if you would like" +" operations between companies to be synchronized at an invoice/bills level " +"or at a sales/purchase orders level." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the settings page emphasizing the inter company transaction field in" +" Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:104 +msgid "" +"**Synchronize invoice/bills**: generates a bill/invoice when a company " +"confirms a bill/invoice for the selected company." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:107 +msgid "" +"*Example:* an invoice posted on JS Store Belgium, for JS Store US, " +"automatically creates a vendor bill on the JS Store US, from the JS Store " +"Belgium." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:114 +msgid "" +"**Synchronize sales/purchase order**: generates a drafted purchase/sales " +"order using the selected company warehouse when a sales/purchase order is " +"confirmed for the selected company. If instead of a drafted purchase/sales " +"order you rather have it validated, enable *Automatic Validation*." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:118 +msgid "" +"*Example:* when a sale order for JS Store US is confirmed on JS Store " +"Belgium, a purchase order on JS Store Belgium is automatically created (and " +"confirmed if the *Automatic Validation* feature was enabled)." +msgstr "" + +#: ../../content/applications/general/users/companies.rst-1 +msgid "" +"View of the purchase created on JS Store US from JS Store Belgium in Odoo" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:127 +msgid "" +"Products have to be configured as *Can be sold* and must be shared between " +"the companies." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:130 +msgid "" +"Remember to test all workflows as an user other than the administrator." +msgstr "" + +#: ../../content/applications/general/users/companies.rst:133 +msgid ":doc:`Multi-company Guidelines </developer/howtos/company>`" +msgstr "" + +#: ../../content/applications/general/users/companies.rst:134 +msgid ":doc:`../../finance/accounting/get_started/multi_currency`" +msgstr "" + +#: ../../content/applications/general/users/language.rst:3 +msgid "Change language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:5 +msgid "" +"Odoo provides you with the option to manage Odoo in different languages, and" +" each user can use Odoo in his own language ." +msgstr "" + +#: ../../content/applications/general/users/language.rst:9 +msgid "Load your desired language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:11 +msgid "" +"The first thing to do is to load your desired language on your Odoo " +"instance." +msgstr "" + +#: ../../content/applications/general/users/language.rst:14 +msgid "" +"From the general dashboard click on the **Settings** app; on the top left of" +" the page select :menuselection:`Translations --> Load a Translation`, " +"select a language to install and click on **LOAD.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:23 +msgid "" +"If you check the \"Websites to translate\" checkbox you will have the option" +" to change the navigation language on your website." +msgstr "" + +#: ../../content/applications/general/users/language.rst:27 +msgid "Change your language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:29 +msgid "" +"You can change the language to the installed language by going to the drop-" +"down menu at the top right side of the screen, choose **Preferences**." +msgstr "" + +#: ../../content/applications/general/users/language.rst:36 +msgid "" +"Then change the Language setting to your installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:42 +msgid "Open a new menu to view the changes." +msgstr "" + +#: ../../content/applications/general/users/language.rst:45 +msgid "Change another user's language" +msgstr "" + +#: ../../content/applications/general/users/language.rst:47 +msgid "" +"Odoo also gives you the possibility for each user to choose his preferred " +"language." +msgstr "" + +#: ../../content/applications/general/users/language.rst:50 +msgid "" +"To change the language for a different user, choose :menuselection:`Users " +"--> Users` from the Settings app. Here you have a list of all users and you " +"can choose the user who you'd like to change the language for. Select the " +"user and click on **Edit** in the top left corner. Under Preferences you can" +" change the Language to any previously installed language and click " +"**SAVE.**" +msgstr "" + +#: ../../content/applications/general/users/language.rst:61 +msgid ":doc:`../../websites/website/configuration/translate`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:3 +msgid "Manage users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:5 +msgid "" +"Odoo defines a **user** as someone who has access to a database to perform " +"daily tasks. You can add as many users as you need and, in order to restrict" +" the type of information each user can access, rules can be applied. Users " +"and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:10 +msgid ":doc:`language`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:11 +msgid ":doc:`access_rights`" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:16 +msgid "Add individual users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:18 +msgid "" +"Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of the settings page emphasizing the manage users field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:27 +msgid "" +"Fill in the form with the needed information. Under the tab :doc:`Access " +"Rights <access_rights>` choose the group within each application the user " +"can have access to." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:28 +msgid "" +"The list of applications shown is based on the applications installed on the" +" database." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the access rights tab in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:34 +msgid "" +"When you are done editing the page and have *Saved* it, an invitation email " +"is automatically sent to the user. The user must click on it to accept the " +"invitation and create a login." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form with a notification that the invitation email has been" +" sent in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:42 +msgid "" +"Remember that subscription prices follow the number of users. Refer to our " +"`pricing page <https://www.odoo.com/pricing>`_ for more information." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:46 +msgid "" +"With the :ref:`developer mode <developer-mode>` activated, *User Types* can " +"be selected." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "" +"View of a user’s form in developer mode emphasizing the user type field in " +"Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:53 +msgid "" +"The *Portal* and *Public* options do not allow you to choose access rights. " +"Members have specific ones (such as record rules and restricted menus) and " +"usually do not belong to the usual Odoo groups." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:60 +msgid "Deactivate users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:62 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, open the " +"user you want to deactivate, click on *Action*, and then on *Archive*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:66 +msgid "**Never** deactivate the main user (*admin*)." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:71 +msgid "Passwords management" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:76 +msgid "Reset passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:81 +msgid "Enable password resets from login page" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:83 +msgid "It is possible to enable password resets directly from the login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:85 +msgid "" +"To do so, go to :menuselection:`Settings --> Permissions`, activate " +"**Password Reset** and *Save*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Enabling Password Reset in Odoo Settings" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:94 +msgid "Send reset instructions to users" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:96 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, select the " +"user out of the list and click on *Send Password Reset Instructions* on its " +"user form. An email is automatically sent to them." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:101 +msgid "" +"The *Send Password Reset Instructions* button only appears if the Odoo " +"invitation email has already been confirmed by the user." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:104 +msgid "" +"This email contains all the instructions needed to reset the password, along" +" with a link redirecting the user to an Odoo login page." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Example of an email with a password reset link for an Odoo account" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:114 +msgid "Change users’ passwords" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:116 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users` and select " +"a user to access its form. Click on the *Action* button and select *Change " +"Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "Change another user's password on Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:123 +msgid "Enter a new password and confirm by clicking on *Change Password*." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:126 +msgid "" +"This operation only modifies the password of the users locally and does not " +"affect their odoo.com account. If you want to change the odoo.com password, " +"you can :ref:`send the password reset instructions <users/reset-password-" +"email>`." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:130 +msgid "" +"Click on *Change Password* one more time. You are then redirected to an Odoo" +" login page where you can reaccess your database using your new password." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:136 +msgid "Multi Companies" +msgstr "หลายบริษัท" + +#: ../../content/applications/general/users/manage_users.rst:138 +msgid "" +"The *Multi Companies* field allows you to set to which of the multiple " +"companies database you hold the user can have access." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:142 +msgid "" +"Note that if not handled correctly, it may be the source of a lot of " +"inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is" +" required. For technical explanations refer to :doc:`this " +"</developer/howtos/company>` documentation." +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst-1 +msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgstr "" + +#: ../../content/applications/general/users/manage_users.rst:152 +msgid ":doc:`companies`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:3 +msgid "Odoo.com account changes" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:5 +msgid "" +"This documentation is dedicated to edits made to an Odoo.com account. The " +"following processes describe how to delete an Odoo.com account, and how to " +"change the password on an Odoo.com account." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:9 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:11 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:15 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"<https://www.odoo.com/my/home>`_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:20 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:23 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:30 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:34 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:36 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:41 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:47 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"<https://www.odoo.com/help>`_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:51 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:55 +#: ../../content/applications/general/users/portal.rst:143 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:57 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:62 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:65 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:71 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:74 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:76 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:77 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:78 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:3 +msgid "Portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:7 +msgid "" +"Portal access is given to users who need the ability to view certain " +"documents or information within an Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:10 +msgid "" +"Some common use cases for providing portal access include allowing customers" +" to read/view any or all of the following in Odoo:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:13 +msgid "leads/opportunities" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:14 +msgid "quotations/sales orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:15 +msgid "purchase orders" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:16 +msgid "invoices & bills" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:17 +msgid "projects" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:18 +msgid "tasks" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:19 +msgid "timesheets" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:20 +msgid "tickets" +msgstr "ทิกเก็ต" + +#: ../../content/applications/general/users/portal.rst:21 +msgid "signatures" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:22 +msgid "subscriptions" +msgstr "การสมัครสมาชิก" + +#: ../../content/applications/general/users/portal.rst:25 +msgid "" +"Portal users only have read/view access, and will not be able to edit any " +"documents in the database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:29 +msgid "Provide portal access to customers" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:31 +msgid "" +"From the main Odoo dashboard, select the :guilabel:`Contacts` application. " +"If the contact is not yet created in the database, click on the " +":guilabel:`Create` button, enter the details of the contact, and then click " +":guilabel:`Save`. Otherwise, choose an existing contact, and then click on " +"the :guilabel:`Action` drop-down menu located at the top-center of the " +"interface." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "Use the Contacts application to give portal access to users." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:40 +msgid "" +"Then select :guilabel:`Grant portal access`. A pop-up window appears, " +"listing three fields:" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:42 +msgid "" +":guilabel:`Contact`: the recorded name of the contact in the Odoo database" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:43 +msgid "" +":guilabel:`Email`: the contact's email address that they will use to log " +"into the portal" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:44 +msgid ":guilabel:`In Portal`: whether or not the user has portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:46 +msgid "" +"To grant portal access, first enter the contact's :guilabel:`Email` they " +"will use to log into the portal. Then, check the box under the :guilabel:`In" +" Portal` column. Optionally, add text to the invitation message the contact " +"will receive. Then click :guilabel:`Apply` to finish." +msgstr "" + +#: ../../content/applications/general/users/portal.rst-1 +msgid "" +"An email address and corresponding checkbox for the contact need to be filled in before\n" +"sending a portal invitation." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:55 +msgid "" +"An email will be sent to the specified email address, indicating that the " +"contact is now a portal user for that Odoo database." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:59 +msgid "" +"To grant portal access to multiple users at once, navigate to a company " +"contact, then click :menuselection:`Action --> Grant portal access` to view " +"a list of all of the company's related contacts. Check the box under the " +":guilabel:`In Portal` column for all the contacts that need portal access, " +"then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:65 +msgid "" +"At any time, portal access can be revoked by navigating to the contact, " +"clicking :menuselection:`Action --> Grant portal access`, and then " +"unselecting the checkbox under the :guilabel:`In Portal` column and clicking" +" :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:72 +msgid "Change portal username" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:74 +msgid "" +"There may be times when a portal user wants to change their user login. This" +" can be done by any user in the database with administrator access rights. " +"The following process outlines the necessary steps to change the portal user" +" login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:79 +msgid "" +":doc:`See the documentation on setting access rights " +"</applications/general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:82 +msgid "" +"First, navigate to :menuselection:`Settings app --> Users`. Then, under " +":guilabel:`Filters`, select :guilabel:`Portal Users`, or select " +":guilabel:`Add Custom Filter` and set the following configuration " +":guilabel:`Groups` > :guilabel:`contains` > `portal`. After making this " +"selection, search for (and open) the portal user that needs to be edited." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:87 +msgid "" +"Next, click :guilabel:`Edit` (if necessary), click into the :guilabel:`Email" +" Address` field, and proceed to make any necessary changes to this field. " +"The :guilabel:`Email Address` field is used to log into the Odoo portal." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:92 +msgid "" +"Changing the :guilabel:`Email Address` (or login) only changes the " +"*username* on the customer's portal login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:95 +msgid "" +"In order to change the contact email, this change needs to take place on the" +" contact template in the *Contacts* app. Alternatively, the customer can " +"change their email directly from the portal, but the login **cannot** be " +"changed. :ref:`See change customer info <portal/custinfo>`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:100 +msgid "Customer portal changes" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:102 +msgid "" +"There may be times when the customer would like to make changes to their " +"contact information, password/security, or payment information attached to " +"the portal account. This can be performed by the customer from their portal." +" The following process is how a customer can change their contact " +"information." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:110 +msgid "Change customer info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:112 +msgid "" +"First enter the username and password (login) into the database login page " +"to access the portal user account. A portal dashboard will appear upon " +"successfully logging in. Portal documents from the various installed Odoo " +"applications will appear with the number count of each." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:117 +msgid ":ref:`Portal access documentation <portal/main>`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:119 +msgid "" +"Next, navigate to the upper-right corner of the portal, and click the " +":guilabel:`Edit` button, next to the :guilabel:`Details` section. Then, " +"change the pertinent information, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:124 +msgid "Change password" +msgstr "เปลี่ยนรหัสผ่าน" + +#: ../../content/applications/general/users/portal.rst:126 +#: ../../content/applications/general/users/portal.rst:145 +#: ../../content/applications/general/users/portal.rst:162 +msgid "" +"First enter the username and password (login) into the database login page " +"to access the portal user account. A portal dashboard will appear upon " +"successfully logging in." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:129 +msgid "" +"If the customer would like to change their password for portal access, click" +" on the :guilabel:`Edit Security Settings` link, below the " +":guilabel:`Account Security` section. Then, make the necessary changes, by " +"typing in the current :guilabel:`Password`, :guilabel:`New Password`, and " +"verify the new password. Lastly, click on :guilabel:`Change Password` to " +"complete the password change." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:135 +msgid "" +"If a customer would like to change the login, as documented above, contact " +"the Odoo database point-of-contact. :ref:`See above documentation on " +"changing the portal username <portal/login>`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:139 +msgid "" +"Passwords for portal users and Odoo.com users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:148 +msgid "" +"If the customer would like to turn on two-factor authentication (2FA) for " +"portal access, click on the :guilabel:`Edit Security Settings` link, below " +"the :guilabel:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:151 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Confirm the current portal password in the " +":guilabel:`Password` field. Then, click on :guilabel:`Confirm Password`. " +"Next, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-" +"factor authentication)` app (Google Authenticator, Authy, etc.), by scanning" +" the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:157 +msgid "" +"Finally, click :guilabel:`Enable two-factor authentication` to complete the " +"setup." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:160 +msgid "Change payment info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:165 +msgid "" +"If the customer would like to manage payment options, navigate to the " +":guilabel:`Manage payment methods` in the menu on the right. Then, add the " +"new payment information, and select :guilabel:`Add new card`." +msgstr "" + +#: ../../content/applications/general/voip.rst:5 +msgid "VoIP (Voice over Internet Protocol)" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:3 +msgid "Configure your VoIP Asterisk server for Odoo" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:6 +msgid "Installing Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:9 +msgid "Dependencies" +msgstr "การขึ้นต่อกัน" + +#: ../../content/applications/general/voip/asterisk.rst:11 +msgid "" +"Before installing Asterisk you need to install the following dependencies:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:13 +msgid "wget" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:14 +msgid "gcc" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:15 +msgid "g++" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:16 +msgid "ncurses-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:17 +msgid "libxml2-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:18 +msgid "sqlite-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:19 +msgid "libsrtp-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:20 +msgid "libuuid-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:21 +msgid "openssl-devel" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:22 +msgid "pkg-config" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:24 +msgid "In order to install libsrtp, follow the instructions below:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:35 +msgid "" +"You also need to install PJSIP, you can download the source `here " +"<http://www.pjsip.org/download.htm>`_. Once the source directory is " +"extracted:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:38 +msgid "**Change to the pjproject source directory:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:44 +msgid "**run:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:50 +msgid "**Build and install pjproject:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:58 +msgid "**Update shared library links:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:64 +msgid "**Verify that pjproject is installed:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:70 +msgid "**The result should be:**" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:87 +msgid "Asterisk" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:89 +msgid "" +"In order to install Asterisk 13.7.0, you can download the source directly " +"`there <http://downloads.asterisk.org/pub/telephony/asterisk/old-" +"releases/asterisk-13.7.0.tar.gz>`_." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:92 +msgid "Extract Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:98 +msgid "Enter the Asterisk directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:104 +msgid "Run the Asterisk configure script:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:110 +msgid "Run the Asterisk menuselect tool:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:116 +msgid "" +"In the menuselect, go to the resources option and ensure that res_srtp is " +"enabled. If there are 3 x’s next to res_srtp, there is a problem with the " +"srtp library and you must reinstall it. Save the configuration (press x). " +"You should also see stars in front of the res_pjsip lines." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:120 +msgid "Compile and install Asterisk:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:126 +msgid "" +"If you need the sample configs you can run 'make samples' to install the " +"sample configs. If you need to install the Asterisk startup script you can " +"run 'make config'." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:130 +msgid "DTLS Certificates" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:132 +msgid "After you need to setup the DTLS certificates." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:138 +msgid "Enter the Asterisk scripts directory:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:144 +msgid "" +"Create the DTLS certificates (replace pbx.mycompany.com with your ip address" +" or dns name, replace My Super Company with your company name):" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:152 +msgid "Configure Asterisk server" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:154 +msgid "" +"For WebRTC, a lot of the settings that are needed MUST be in the peer " +"settings. The global settings do not flow down into the peer settings very " +"well. By default, Asterisk config files are located in /etc/asterisk/. Start" +" by editing http.conf and make sure that the following lines are " +"uncommented:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:166 +msgid "" +"Next, edit sip.conf. The WebRTC peer requires encryption, avpf, and " +"icesupport to be enabled. In most cases, directmedia should be disabled. " +"Also under the WebRTC client, the transport needs to be listed as ‘ws’ to " +"allow websocket connections. All of these config lines should be under the " +"peer itself; setting these config lines globally might not work:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:197 +msgid "" +"In the sip.conf and rtp.conf files you also need to add or uncomment the " +"lines:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:204 +msgid "Lastly, set up extensions.conf:" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:213 +msgid "Configure Odoo VOIP" +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:215 +msgid "In Odoo, the configuration should be done in the user's preferences." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:221 +msgid "" +"The SIP Login/Browser's Extension is the number you configured previously in" +" the sip.conf file (in our example: 1060)." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:224 +msgid "The SIP Password is the secret you chose in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:226 +msgid "" +"The extension of your office's phone is not a required field but it is used " +"if you want to transfer your call from Odoo to an external phone also " +"configured in the sip.conf file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:230 +msgid "" +"The configuration should also be done in the General Settings under the " +"\"Integrations\" section." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:235 +msgid "" +"The PBX Server IP should be the same as the IP you define in the http.conf " +"file." +msgstr "" + +#: ../../content/applications/general/voip/asterisk.rst:237 +msgid "" +"The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to" +" be the same as the IP defined previously and \"XXXX\" needs to be the port " +"defined in the http.conf file." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:3 +msgid "Use VoIP services in Odoo with Axivox" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:6 +#: ../../content/applications/general/voip/onsip.rst:6 +msgid "Introduction" +msgstr "แนะนำ" + +#: ../../content/applications/general/voip/axivox.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with `Axivox " +"<https://www.axivox.com/>`_. In that case, an :doc:`Asterisk server " +"<asterisk>` is not necessary as the infrastructure is hosted and managed by " +"Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:12 +msgid "" +"To use this service, `contact Axivox <https://www.axivox.com/contact/>`_ to " +"open an account. Before doing so, verify that Axivox covers your area and " +"the areas you wish to call." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:18 +msgid "Go to :menuselection:`Apps` and install the **VoIP Module**." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "VoIP module installation on an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:24 +msgid "" +"Go to :menuselection:`Settings --> General Settings --> Integrations`, and " +"fill out the **Asterisk (VoIP)** field:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:27 +msgid "" +"**PBX Server IP**: set the domain created by Axivox for your account (e.g., " +"*yourcompany.axivox.com*)" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:29 +msgid "**WebSocket**: type in ``wss://pabx.axivox.com:3443``" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:30 +msgid "**VoIP Environment**: set as *Production*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox as VoIP provider in an Odoo database" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:37 +msgid "Configure the VOIP user in the Odoo's user" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:39 +msgid "" +"Go to :menuselection:`Settings --> Users & Companies --> Users`, then open " +"the user's form you want to configure. Under the **Preferences** tab, fill " +"out the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:42 +msgid "**SIP Login / Browser's Extension**: the Axivox *username*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:43 +msgid "**SIP Password**: the Axivox *SIP Password*" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Integration of Axivox user in the Odoo user preference" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:50 +msgid "" +"You can find all this information by logging in at " +"https://manage.axivox.com/, selecting the user you want to configure, and " +"referring to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "SIP credentials in the Axivox manager" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:58 +msgid "Phone Calls" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:60 +msgid "" +"You can make phone calls by clicking on the phone icon in the navigation " +"bar." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:62 +msgid "" +"You can also receive phone calls. Odoo rings and displays a notification." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:65 +msgid "Your number is the one provided by Axivox." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst-1 +msgid "Incoming VoIP call in Odoo" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:72 +msgid "" +"If you see a *Missing Parameter* message in the **Odoo softphone**, refresh " +"your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:80 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g., +16506913277 (where +1 is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/axivox.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:3 +msgid "Use VoIP services in Odoo with OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:8 +msgid "" +"Odoo VoIP can be set up to work together with OnSIP (www.onsip.com). In that" +" case, the installation and setup of an Asterisk server is not necessary as " +"the whole infrastructure is hosted and managed by OnSIP." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:12 +msgid "" +"You will need to open an account with OnSIP to use this service. Before " +"doing so, make sure that your area and the areas you wish to call are " +"covered by the service. After opening an OnSIP account, follow the " +"configuration procedure below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:19 +msgid "Go to Apps and install the module **VoIP OnSIP**." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:24 +msgid "" +"Go to Settings/General Settings. In the section Integrations/Asterisk " +"(VoIP), fill in the 3 fields:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:26 +msgid "" +"**OnSIP Domain** is the domain you chose when creating an account on " +"www.onsip.com. If you don't know it, log in to https://admin.onsip.com/ and " +"you will see it in the top right corner of the screen." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:29 +msgid "**WebSocket** should contain wss://edge.sip.onsip.com" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:30 +msgid "**Mode** should be Production" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:35 +msgid "" +"Go to **Settings/Users**. In the form view of each VoIP user, in the " +"Preferences tab, fill in the section **PBX Configuration**:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:38 +msgid "**SIP Login / Browser's Extension**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:39 +msgid "**OnSIP authorization User**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:40 +msgid "**SIP Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:41 +msgid "**Handset Extension**: the OnSIP 'Extension'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:43 +msgid "" +"You can find all this information by logging in at " +"https://admin.onsip.com/users, then select the user you want to configure " +"and refer to the fields as pictured below." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:49 +msgid "" +"You can now make phone calls by clicking the phone icon in the top right " +"corner of Odoo (make sure you are logged in as a user properly configured in" +" Odoo and in OnSIP)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:53 +msgid "" +"If you see a *Missing Parameters* message in the Odoo softphone, make sure " +"to refresh your Odoo window and try again." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:60 +msgid "" +"If you see an *Incorrect Number* message in the Odoo softphone, make sure to" +" use the international format, leading with the plus (+) sign followed by " +"the international country code. E.g.: `+16506913277` (where `+1` is the " +"international prefix for the United States)." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:67 +msgid "" +"You can now also receive phone calls. Your number is the one provided by " +"OnSIP. Odoo will ring and display a notification." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:74 +msgid "OnSIP on Your Cell Phone" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:76 +msgid "" +"In order to make and receive phone calls when you are not in front of your " +"computer, you can use a softphone app on your cell phone in parallel of Odoo" +" VoIP. This is useful for on-the-go calls, but also to make sure to hear " +"incoming calls, or simply for convenience. Any SIP softphone will work." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:80 +msgid "" +"On Android and iOS, OnSIP has been successfully tested with `Grandstream " +"Wave <https://play.google.com/store/apps/details?id=com.grandstream.ucm>`_. " +"When creating an account, select OnSIP in the list of carriers. You will " +"then have to configure it as follows:" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:84 +msgid "**Account name**: OnSIP" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:85 +msgid "**SIP Server**: the OnSIP 'Domain'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:86 +msgid "**SIP User ID**: the OnSIP 'Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:87 +msgid "**SIP Authentication ID**: the OnSIP 'Auth Username'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:88 +msgid "**Password**: the OnSIP 'SIP Password'" +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:90 +msgid "" +"Aside from initiating calls from Grandstream Wave on your phone, you can " +"also initiate calls by clicking phone numbers in your browser on your PC. " +"This will make Grandstream Wave ring and route the call via your phone to " +"the other party. This approach is useful to avoid wasting time dialing phone" +" numbers. In order to do so, you will need the Chrome extension `OnSIP Call " +"Assistant <https://chrome.google.com/webstore/detail/onsip-call-" +"assistant/pceelmncccldedfkcgjkpemakjbapnpg>`_." +msgstr "" + +#: ../../content/applications/general/voip/onsip.rst:97 +msgid "" +"The downside of using a softphone on your cell phone is that your calls will" +" not be logged in Odoo, as the softphone acts as an independent, separate " +"app." +msgstr "" diff --git a/locale/th/LC_MESSAGES/index.po b/locale/th/LC_MESSAGES/index.po new file mode 100644 index 000000000..043448b0d --- /dev/null +++ b/locale/th/LC_MESSAGES/index.po @@ -0,0 +1,22 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2023-11-08 08:46+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/index.rst:5 +msgid "Odoo Documentation" +msgstr "" diff --git a/locale/th/LC_MESSAGES/inventory_and_mrp.po b/locale/th/LC_MESSAGES/inventory_and_mrp.po new file mode 100644 index 000000000..662e6faad --- /dev/null +++ b/locale/th/LC_MESSAGES/inventory_and_mrp.po @@ -0,0 +1,23736 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wichanon Jamwutthipreecha, 2024 +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/inventory_and_mrp.rst:5 +msgid "Inventory & MRP" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:8 +msgid "Barcode" +msgstr "บาร์โค้ด" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:10 +msgid "" +"**Odoo Barcode** allows users to assign barcodes to individual products and " +"product categories, and track inventory movements using those barcodes. By " +"connecting a barcode scanner, certain inventory processes can be triggered " +"by scanning barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode.rst:15 +msgid "" +"`Odoo Tutorials: Barcode Basics <https://www.odoo.com/slides/slide/barcode-" +"basics-692>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:5 +msgid "Daily operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:3 +msgid "Apply inventory adjustments with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:5 +msgid "" +"In a warehouse, the recorded inventory counts in the database might not " +"always match the actual, real inventory counts. In such cases, inventory " +"adjustments can be made to reconcile the differences, and ensure that the " +"recorded counts in the database match the actual counts in the warehouse. In" +" Odoo, the *Barcode* app can be used to make these adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:10 +msgid "" +"These adjustments can be done in real time using an Odoo-compatible barcode " +"scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:14 +msgid "" +"For a list of Odoo-compatible barcode mobile scanners, and other hardware " +"for the *Inventory* and *Barcode* apps, refer to the `Odoo Inventory • " +"Hardware page <https://www.odoo.com/app/inventory-hardware>`_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:19 +msgid "" +":doc:`../../inventory/warehouses_storage/inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:22 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:15 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:13 +msgid "Enable Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:24 +msgid "" +"To use the *Barcode* app to create and apply inventory adjustments, it " +"**must** be installed by enabling the feature from the settings of the " +"*Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:27 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click " +"the checkbox next to the :guilabel:`Barcode Scanner` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:31 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:24 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:22 +msgid "" +"Once the checkbox is ticked, click :guilabel:`Save` at the top of the page " +"to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:33 +msgid "" +"After saving, a new drop-down menu appears under the :guilabel:`Barcode " +"Scanner` option, labeled :guilabel:`Barcode Nomenclature`, where either " +":guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can" +" be selected. Each nomenclature option determines how scanners interpret " +"barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:38 +msgid "" +"There is also a :guilabel:`Configure Product Barcodes` internal link arrow, " +"along with a set of :guilabel:`Print` buttons for printing barcode commands " +"and a barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Enabled Barcode feature in Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:46 +msgid "" +"For more information on setting up and configuring the :guilabel:`Barcode` " +"app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and" +" :doc:`Activate the Barcodes in Odoo <../setup/software>` docs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:51 +msgid "Perform an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:53 +msgid "" +"Begin by navigating to the :menuselection:`Barcode app --> Barcode Scanning`" +" dashboard, where different options will be displayed, including " +":guilabel:`Operations`, :guilabel:`Inventory Adjustments`, and " +":guilabel:`Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:57 +msgid "" +"To create and apply inventory adjustments, click on the :guilabel:`Inventory" +" Adjustments` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:60 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:123 +msgid "" +"Doing so navigates to the *Barcode Inventory Client Action* page, labeled as" +" :guilabel:`Inventory Adjustment` in the top header section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Barcode app start screen with scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:67 +msgid "" +"To begin the adjustment, first scan the *source location*, which is the " +"current location in the warehouse of the product whose count should be " +"adjusted. Then, scan the product barcode(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:70 +msgid "" +"The barcode of a specific product can be scanned multiple times to increase " +"the quantity of that product in the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:74 +msgid "" +"If the warehouse *multi-location* feature is **not** enabled in the " +"database, a source location does not need to be scanned. Instead, simply " +"scan the product barcode to start the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:78 +msgid "" +"Alternatively, the quantity can be changed by clicking the :guilabel:`✏️ " +"(pencil)` icon on the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:81 +msgid "" +"Doing so opens a separate window with a keypad. Edit the number in the " +":guilabel:`Quantity` line to change the quantity. Additionally, the " +":guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract " +"quantity of the product, and the number keys can be used to add quantity, as" +" well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:86 +msgid "" +"In the below inventory adjustment, the source location `WH/Stock/Shelf/2` " +"was scanned, assigning the location. Then, the barcode for the product " +"`[FURN_7888] Desk Stand with Screen` was scanned 3 times, increasing the " +"units in the adjustment. Additional products can be added to this adjustment" +" by scanning the barcodes for those specific products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Barcode Inventory Client Action page with inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:95 +msgid "" +"To complete the inventory adjustment, click the green :guilabel:`✅ Apply` " +"button with the check mark at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:98 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:150 +msgid "" +"Once applied, Odoo navigates back to the :guilabel:`Barcode Scanning` " +"screen. A small green banner appears in the top right corner, confirming " +"validation of the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:180 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:103 +msgid "" +"Odoo's *Barcode* application provides demo data with barcodes to explore the" +" features of the app. These can be used for testing purposes, and can be " +"printed from the home screen of the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:106 +msgid "" +"To access this demo data, navigate to the :menuselection:`Barcode app` and " +"click :guilabel:`stock barcodes sheet` and :guilabel:`commands for " +"Inventory` (bolded and highlighted in blue) in the information pop-up window" +" above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Demo data prompt pop-up on Barcode app main screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:115 +msgid "Manually add products to inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:117 +msgid "" +"When the barcodes for the location or product are not available, Odoo " +"*Barcode* can still be used to perform inventory adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:120 +msgid "" +"To do this, navigate to the :menuselection:`Barcode app --> Barcode Scanning" +" --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:126 +msgid "" +"To manually add products to this adjustment, click the white :guilabel:`➕ " +"Add Product` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:129 +msgid "" +"This navigates to a new, blank page where the desired product, quantity, and" +" source location must be chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Keypad to add products on Barcode Inventory Client Action page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:136 +msgid "" +"First, click the :guilabel:`Product` line, and choose the product whose " +"stock count should be adjusted. Then, manually enter the quantity of that " +"product, either by changing the `1` in the :guilabel:`Quantity` line, or by " +"clicking the :guilabel:`+1` and :guilabel:`-1` buttons to add or subtract " +"quantity of the product. The number pad can be used to add quantity, as " +"well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:141 +msgid "" +"Below the number pad is the :guilabel:`location` line, which should read " +"`WH/Stock` by default. Click this line to reveal a drop-down menu of " +"locations to choose from, and choose the :guilabel:`source location` for " +"this inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:145 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:147 +msgid "" +"To apply the inventory adjustment, click the green :guilabel:`✅ Apply` " +"button with the check mark, at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:8 +msgid "Overview" +msgstr "ภาพรวม" + +#: ../../content/applications/inventory_and_mrp/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 sale which sells products in" +" bulk, in which 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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:13 +msgid "Create a Barcode Nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:15 +msgid "" +"Odoo supports Barcode Nomenclatures, which determine the mapping and " +"interpretation of the encoded information. You can configure your barcode " +"nomenclature being in :ref:`developer mode <developer-mode>`. To do so, go " +"to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:20 +msgid "" +"You can create a barcode nomenclature from there, and then add a line to " +"create your first rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:26 +msgid "" +"The first step is to specify the **rule name**, for example Weight Barcode " +"with 3 Decimals. You then have to specify the type for barcode nomenclature," +" in our case it will be Weighted Product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:33 +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" +" simply to identify the product in question. The “N” define a number and the" +" “D” define the decimals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:40 +msgid "" +"The encoding allows to specify the barcode encoding on which the rule should" +" be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:44 +msgid "" +"You can define different rules and order their priority thanks to the " +"sequence. The first rule which matches the scanned barcode will be applied." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:49 +msgid "Configure your Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:51 +msgid "The barcode of the product should start by “21”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:52 +msgid "" +"The 5 “dots” are the other numbers of your product barcode, allowing to " +"identify the product;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:53 +msgid "" +"The barcode should contain 0’s where you did defined D’s or N’s. In our case" +" we need to set 5 zeros because we configured “21…..{NNDDD}”;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:54 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:59 +msgid "" +"In case you weight 1,5 Kg of pasta, the balance will print you the following" +" barcode 2112345015002. If you scan this barcode in your POS or when " +"receiving products in your barcode application, Odoo will automatically " +"create a new line for the Pasta product for a quantity of 1.5 Kg. For the " +"point of sale, a price depending on the quantity will also be computed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:70 +msgid "Rule Types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:72 +msgid "" +"**Priced Product**: allows you to identify the product and specify its " +"price, used in POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:73 +msgid "" +"**Discounted Product**: allows you to create one barcode per applied " +"discount. You can then scan your product in the POS and then scan the " +"discount barcode, discount will be applied on the normal price of the " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:74 +msgid "" +"**Weighted Product**: allows you to identify the product and specify its " +"weight, used in both POS (in which the price is computed based on the " +"weight) and in inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:75 +msgid "" +"**Client**: allows you to identify the customer, for example used with " +"loyalty program." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:76 +msgid "**Cashier**: allows you to identify the cashier when entering the POS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:77 +msgid "" +"**Location**: allows you to identify the location on a transfer when multi-" +"location is activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:78 +msgid "" +"**Package**: allows you to identify packages on a transfer when packages are" +" activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:79 +msgid "" +"**Credit Card**: doesn’t need manual modification, exists for data from the " +"Mercury module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:80 +msgid "" +"**Unit Product**: allows you to identify a product for both POS and " +"transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:83 +msgid "" +"When the barcode pattern contains .*, it means that it can contain any " +"number of characters, those characters being any number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:3 +msgid "GS1 barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:12 +msgid "" +"`GS1 nomenclature <https://www.gs1us.org/>`_ consolidates various product " +"and supply chain data into a single barcode. Odoo takes in `unique Global " +"Trade Item Numbers <https://www.gs1.org/standards/get-barcodes>`_ (GTIN), " +"purchased by businesses, to enable global shipping, sales, and eCommerce " +"product listing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:17 +msgid "" +"Configure GS1 nomenclature to scan barcodes of sealed boxes and identify " +"essential product information, such as |GTIN|, lot number, quantity " +"information, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:21 +msgid "" +"|GTINs| are unique product identification that **must** be `purchased from " +"GS1 <https://www.gs1.org/standards/get-barcodes>`_ to use GS1 barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:25 +msgid "" +"`All GS1 barcodes <https://www.gs1.org/standards/barcodes/application-" +"identifiers>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:26 +msgid "" +":ref:`Odoo's default GS1 rules <barcode/operations/default-gs1-nomenclature-" +"list>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:27 +msgid "" +":ref:`Why's my barcode not working? <barcode/operations/troubleshooting>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:34 +msgid "" +"To use GS1 nomenclature, navigate to the :menuselection:`Inventory app --> " +"Configuration --> Settings`. Then under the :guilabel:`Barcode` section, " +"check the :guilabel:`Barcode Scanner` box. Next, select " +":menuselection:`Barcode Nomenclature --> Default GS1 Nomenclature` from the " +"default barcode nomenclature options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst-1 +msgid "" +"Choose GS1 from dropdown and click the external link to see the list of GS1 " +"rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:43 +msgid "" +"The list of GS1 *rules* and *barcode patterns* Odoo supports by default is " +"accessible by clicking the :guilabel:`➡️ (arrow)` icon to the right of the " +":guilabel:`Barcode Nomenclature` selection." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:46 +msgid "" +"In the :guilabel:`Open: Nomenclature` pop-up table, view and edit the GS1 " +":guilabel:`Rule Names` available in Odoo. The table contains all the " +"information that can be condensed with a GS1 barcode, along with the " +"corresponding :guilabel:`Barcode Pattern`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:51 +msgid "" +"After setting GS1 as the barcode nomenclature, the :menuselection:`Barcode " +"Nomenclatures` settings can also be accessed by a hidden menu that's " +"discoverable after enabling :ref:`developer mode <developer-mode>`. Once " +"enabled, navigate to the :menuselection:`Inventory app --> Configuration -->" +" Barcode Nomenclatures` menu and finally, select :guilabel:`Default GS1 " +"Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:60 +msgid "Use GS1 barcodes in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:62 +msgid "" +"For product identification using GS1 barcodes in Odoo, businesses obtain a " +"`unique GTIN <https://www.gs1.org/standards/get-barcodes>`_ as an " +"internationally distinct product identifier purchased from GS1. This |GTIN| " +"is combined with specific product details following GS1's designated " +"*barcode pattern*. The barcode pattern's arrangement of numbers and letters " +"must adhere to GS1 conventions for accurate interpretation by global systems" +" along the supply chain." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:68 +msgid "" +"Every barcode starts with a 2-4 digit `application identifier " +"<https://www.gs1.org/standards/barcodes/application-identifiers>`_ (A.I.). " +"This required prefix universally indicates what kind of information the " +"barcode contains. Odoo follows GS1 rules for identifying information, as " +"detailed in the :ref:`default GS1 rules list <barcode/operations/default-" +"gs1-nomenclature-list>`. Including the relevant |AI| from the list enables " +"Odoo to correctly interpret GS1 barcodes. While most barcode patterns have a" +" fixed length requirement, certain ones, such as lots and serial numbers, " +"have flexible length." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:77 +msgid "" +"For flexible-length barcode patterns not placed at the end of the GS1 " +"barcode, use the FNC1 separator (`\\\\x1D`) to end the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:80 +msgid "" +"Example: The barcode pattern for lot numbers is 20 characters long. Instead " +"of creating a 20-character lot number barcode, like `LOT00000000000000001`, " +"use the FNC1 separator to make it shorter: `LOT001\\x1D`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:84 +msgid "" +"Refer to the :ref:`GS1 nomenclature list <barcode/operations/default-" +"gs1-nomenclature-list>` to see a comprehensive list of all barcode patterns " +"and rules to follow. Otherwise, refer to :ref:`this GS1 usage doc " +"<barcode/operations/gs1_usage>` for specific examples of combining |GTIN| to" +" product information and configuring the workflow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:90 +msgid ":ref:`Lots workflow <barcode/operations/gs1-lots>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:91 +msgid ":ref:`Non-unit quantities workflow <barcode/operations/quantity-ex>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:98 +msgid "" +"GS1 rules are a specific format of information contained in the barcode, " +"beginning with an |AI| and containing a defined length of characters. " +"Scanning GS1 barcodes from the :ref:`default GS1 list " +"<barcode/operations/default-gs1-nomenclature-list>` auto-fills corresponding" +" data in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:103 +msgid "" +"Adding GS1 barcode rules in Odoo ensures accurate interpretation of unique, " +"non-standard GS1 formats." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:106 +msgid "" +"To do so, begin by turning on :ref:`developer mode <developer-mode>` and " +"navigating to the :guilabel:`Barcode Nomenclatures` list in " +":menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. " +"Then, select the :guilabel:`Default GS1 Nomenclature` list item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:110 +msgid "" +"On the :guilabel:`Default GS1 Nomenclature` page, select :guilabel:`Add a " +"line` at the bottom of the table, which opens a window to create a new rule." +" The :guilabel:`Rule Name` field is used internally to identify what the " +"barcode represents. The barcode :guilabel:`Types` are different " +"classifications of information that can be understood by the system (e.g. " +"product, quantity, best before date, package, coupon). The " +":guilabel:`Sequence` represents the priority of the rule; this means the " +"smaller the value, the higher the rule appears on the table. Odoo follows " +"the sequential order of this table and will use the first rule it matches " +"based on the sequence. The :guilabel:`Barcode Pattern` is how the sequence " +"of letters or numbers is recognized by the system to contain information " +"about the product." +msgstr "" +"ในหน้า :guilabel:`Default GS1 Nomenclature` ให้เลือก :guilabel:`Add a line` " +"ที่ด้านล่างของตาราง ซึ่งจะเปิดหน้าต่างเพื่อสร้างกฎใหม่ ช่อง :guilabel:`Rule " +"Name` ถูกใช้เป็นการภายในเพื่อระบุว่าบาร์โค้ดหมายถึงอะไร บาร์โค้ด " +":guilabel:`Types` " +"คือการจำแนกประเภทข้อมูลที่แตกต่างกันซึ่งระบบสามารถเข้าใจได้ (เช่น ผลิตภัณฑ์ " +"ปริมาณ วันหมดอายุ บรรจุภัณฑ์ คูปอง) :guilabel:`Sequence` " +"แสดงถึงลำดับความสำคัญของกฎ ซึ่งหมายความว่ายิ่งค่าน้อยลง " +"กฎก็จะยิ่งปรากฏบนตารางมากขึ้นเท่านั้น Odoo ตามลำดับของตารางนี้ " +"และจะใช้กฎแรกที่ตรงกันตามลำดับ :guilabel:`รูปแบบบาร์โค้ด` " +"คือวิธีที่ระบบรับรู้ลำดับของตัวอักษรหรือตัวเลขเพื่อให้มีข้อมูลเกี่ยวกับผลิตภัณฑ์" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:120 +msgid "" +"After filling in the information, click the :guilabel:`Save & New` button to" +" make another rule or click :guilabel:`Save & Close` to save and return to " +"the table of rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:126 +msgid "Barcode troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:128 +msgid "" +"Since GS1 barcodes are challenging to work with, here are some checks to try" +" when the barcodes are not working as expected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:131 +msgid "" +"Ensure that the :guilabel:`Barcode Nomenclature` setting is set as " +":menuselection:`Default GS1 Nomenclature`. Jump to the :ref:`nomenclature " +"setup section <barcode/operations/set-up-barcode-nomenclature>` for more " +"details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:134 +msgid "" +"Ensure that the fields scanned in the barcode are enabled in Odoo. For " +"example, to scan a barcode containing lots and serial numbers, make sure the" +" :guilabel:`Lots & Serial Numbers` feature is enabled in :ref:`Odoo's " +"settings <barcode/operations/lot-setup>` and :ref:`on the product " +"<barcode/operations/lot-setup-on-product>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:138 +msgid "" +"Omit punctuation such as parentheses `()` or brackets `[]` between the " +":abbr:`A.I. (Application Identifier)` and the barcode sequence. These are " +"typically used in examples for ease of reading and should **not** be " +"included in the final barcode. For more details on building GS1 barcodes, go" +" to :ref:`this section <barcode/operations/create-GS1-barcode>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:142 +msgid "" +"When a single barcode contains multiple encoded fields, Odoo requires all " +"rules to be listed in the barcode nomenclature for Odoo to read the barcode." +" :ref:`This section <barcode/operations/create-new-rules>` details how to " +"add new rules in the barcode nomenclature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:146 +msgid "" +"Test barcodes containing multiple encoded fields, piece by piece, to figure " +"out which field is causing the issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:150 +msgid "" +"When testing a barcode containing the |GTIN|, lot number, and quantity, " +"start by scanning the |GTIN| alone. Then, test the |GTIN| with the lot " +"number, and finally, try scanning the whole barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:154 +msgid "" +"After diagnosing the encoded field is unknown, :ref:`add new rules " +"<barcode/operations/create-new-rules>` to Odoo's default list to recognize " +"GS1 barcodes with unique specifications." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:159 +msgid "" +"While the new field will be read, the information won't link to an existing " +"field in Odoo without developer customizations. However, adding new rules is" +" necessary to ensure the rest of the fields in the barcode are interpreted " +"correctly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:166 +msgid "GS1 nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:168 +msgid "" +"The table below contains Odoo's default list of GS1 rules. Barcode patterns " +"are written in regular expressions. Only the first three rules require a " +"`check digit <https://www.gs1.org/services/check-digit-calculator>`_ as the " +"final character." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Rule Name" +msgstr "ชื่อกฎ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" +msgstr "ประเภท" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Barcode Pattern" +msgstr "รูปแบบบาร์โค้ด" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "GS1 Content Type" +msgstr "ประเภทเนื้อหา GS1" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Odoo field" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Serial Shipping Container Code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package" +msgstr "แพ็คเกจ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "(00)(\\\\d{18})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "Numeric identifier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "Global Trade Item Number (GTIN)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Unit Product" +msgstr "หน่วยสินค้า" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "(01)(\\\\d{14})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid ":guilabel:`Barcode` field on product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "GTIN of contained trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "(02)(\\\\d{14})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Packaging" +msgstr "บรรจุภัณฑ์" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "Ship to / Deliver to global location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Destination location" +msgstr "ตำแหน่งปลายทาง" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 +msgid "(410)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Ship / Deliver for forward" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "(413)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 +msgid "Source location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "I.D. of a physical location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 +msgid "Location" +msgstr "สถานที่" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +msgid "(414)(\\\\d{13})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "Batch or lot number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Lot" +msgstr "ล็อต" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Alpha-numeric name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Serial number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "(21) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Packaging Date" +msgstr "วันที่บรรจุภัณฑ์" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "(13)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Date" +msgstr "วันที่" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:197 +msgid "Pack date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before Date" +msgstr "ดีที่สุดก่อนวันที่" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "(15)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:200 +msgid "Best before date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration date (YYMMDD)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiration Date" +msgstr "วันหมดอายุ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "(17)(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:203 +msgid "Expiry date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "Variable count of items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "Quantity" +msgstr "ปริมาณ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +msgid "(30)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Measure" +msgstr "ตัวชี้วัด" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:206 +msgid "UoM: Units" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Count of trade items" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "(37)(\\\\d{0,8})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:208 +msgid "Qty in units for containers (AI 02)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Net weight: kilograms (kg)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "(310[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:211 +msgid "Qty in kg" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Length in meters (m)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "(311[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:213 +msgid "Qty in m" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Net volume: liters (L)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "(315[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:215 +msgid "Qty in L" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Net volume: cubic meters (m\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "(316[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:217 +msgid "Qty in m\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Length in inches (in)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "(321[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:219 +msgid "Qty in inches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Net weight/volume: ounces (oz)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "(357[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:221 +msgid "Qty in oz" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Net volume: cubic feet (ft\\ :sup:`3`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "(365[0-5])(\\\\d{6})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:223 +msgid "Qty in ft\\ :sup:`3`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Packaging Type" +msgstr "ประเภทบรรจุภัณฑ์" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:225 +msgid "Package type" +msgstr "ประเภทแพ็คเกจ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:3 +msgid "GS1 barcode usage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:10 +msgid "" +"GS1 barcodes provide a standardized format that barcode scanners can " +"interpret. They encode information in a :ref:`specific structure recognized " +"globally <barcode/operations/gs1>`, allowing scanners to understand and " +"process supply chain data consistently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:14 +msgid "" +"Odoo *Barcode* interprets and prints GS1 barcodes, automating product " +"identification and tracking in warehouse operations such as receiving, " +"picking, and shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:17 +msgid "" +"The following sections contain examples of how Odoo uses GS1 barcodes " +"provided by the business to identify common warehouse items and automate " +"certain warehouse workflows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:21 +msgid "" +"Odoo **does not** create GS1 barcodes. Businesses must purchase a unique " +"Global Trade Item Number (GTIN) from GS1. Then, they can combine their " +"existing GS1 barcodes with product and supply chain information (also " +"provided by GS1) to create barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:26 +msgid "`Purchase GTINs <https://www.gs1.org/standards/get-barcodes>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:27 +msgid ":ref:`GS1 nomenclature <barcode/operations/gs1>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:32 +msgid "Configure barcodes for product, quantity, and lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:34 +msgid "" +"To build a GS1 barcode that contains information about a product, its " +"quantities, and the lot number, the following barcode patterns and " +"Application Identifiers (A.I.) are used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Name" +msgstr "ชื่อ" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "A.I." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Field in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +msgid "Product" +msgstr "สินค้า" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:135 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:203 +msgid "01" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:139 +msgid "30" +msgstr "30" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:43 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid ":guilabel:`Units` field on transfer form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "Lot Number" +msgstr "หมายเลขล็อต" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:41 +msgid "10" +msgstr "10" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +msgid ":guilabel:`Lot` on Detailed Operations pop-up" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:52 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:39 +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:54 +msgid "" +"First, :ref:`enable product tracking using lots " +"<inventory/management/track_products_by_lots>` by navigating to " +":menuselection:`Inventory app --> Configuration --> Settings`, and checking " +"the box for :guilabel:`Lots & Serial Numbers` under the " +":guilabel:`Traceability` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:58 +msgid "" +"Then, set up the product barcode by navigating to the intended product form " +"in :menuselection:`Inventory app --> Products --> Products` and selecting " +"the product. On the product form, click :guilabel:`Edit`. Then, in the " +":guilabel:`General Information` tab, fill in the :guilabel:`Barcode` field " +"with the unique 14-digit `Global Trade Item Number (GTIN) " +"<https://www.gs1.org/standards/get-barcodes>`_, which is a universally " +"recognized identifying number that is provided by GS1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:66 +msgid "" +"On the product form, omit the |AI| `01` for |GTIN| product barcode pattern, " +"as it is only used to encode multiple barcodes into a single barcode that " +"contains detailed information about the package contents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:72 +msgid "" +"To record the GS1 barcode for the product, `Fuji Apple`, enter the 14-digit " +"|GTIN| `20611628936004` in the :guilabel:`Barcode` field on the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "Enter 14-digit GTIN into the Barcode field on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:80 +msgid "" +"To view a list of *all* products and their corresponding barcodes in the " +"Odoo database, navigate to :menuselection:`Inventory app --> Configuration " +"--> Settings`. Under the :guilabel:`Barcode` heading, click on the " +":guilabel:`Configure Product Barcodes` button under the :guilabel:`Barcode " +"Scanner` section. Enter the 14-digit |GTIN| into the :guilabel:`Barcode` " +"column, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "View the Product Barcodes page from inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:92 +msgid "" +"After activating tracking by lots and serial numbers from the settings page," +" specify that this feature is to be applied on each product by navigating to" +" the :guilabel:`Inventory` tab on the product form. Under " +":guilabel:`Tracking`, choose the :guilabel:`By Lots` radio button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst-1 +msgid "" +"Enable product tracking by lots in the \"Inventory\" tab of the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:176 +msgid "Scan barcode on receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:103 +msgid "" +"To ensure accurate lot interpretation in Odoo on product barcodes scanned " +"during a receipt operation, navigate to the :menuselection:`Barcode` app to " +"manage the :ref:`receipt picking process <barcode/operations/scan-received-" +"products>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:107 +msgid "" +"From the :guilabel:`Barcode Scanning` dashboard, click the " +":guilabel:`Operations` button, then the :guilabel:`Receipts` button to view " +"the list of vendor receipts to process. Receipts generated from :abbr:`POs " +"(Purchase Orders)` are listed, but new receipt operations can also be " +"created directly through the :menuselection:`Barcode` app using the " +":guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:112 +msgid "" +"On the list of receipts, click on the warehouse operation (`WH/IN`) and scan" +" product barcodes and lot numbers with a barcode scanner. The scanned " +"product then appears on the list. Use the :guilabel:`✏️ (pencil)` button to " +"open a window and manually enter quantities for specific lot numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:118 +msgid "" +"After placing a :abbr:`PO (Purchase Order)` for fifty apples, navigate to " +"the associated receipt in the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:121 +msgid "" +"Scan the barcode containing the |GTIN|, quantity, and lot number. For " +"testing with a barcode scanner, below is an example barcode for the fifty " +"Fuji apples in Lot 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:129 +msgid "50 Fuji apples in Lot0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:131 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:199 +msgid "2D Matrix" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "" +"2D matrix of GS1 barcode of 50 fuji apples with an assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:134 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:202 +msgid "|AI| (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:136 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:204 +msgid "GS1 Barcode (product)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:137 +msgid "20611628936004" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:138 +msgid "|AI| (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:140 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:208 +msgid "GS1 Barcode (quantity)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:141 +msgid "00000050" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:142 +msgid "|AI| (lot)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:144 +msgid "GS1 Barcode (lot #)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:145 +msgid "LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:146 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:210 +msgid "Full GS1 barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:147 +msgid "0120611628936004 3000000050 10LOT0002" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:149 +msgid "" +":ref:`If the configuration is correct <barcode/operations/troubleshooting>`," +" `50/50` :guilabel:`Units` processed will be displayed and the " +":guilabel:`Validate` button turns green. Click the :guilabel:`Validate` " +"button to complete the reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "" +"Scan the barcode for a product on the reception picking page in the " +"*Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:160 +msgid "Configure barcode for product and non-unit quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:162 +msgid "" +"To build a GS1 barcode that contains products measured in a non-unit " +"quantity, like kilograms, for example, the following barcode patterns are " +"used:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "Quantity in kilograms" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:171 +msgid "310[0-5]" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:178 +msgid "" +"To confirm that quantities are correctly interpreted in Odoo, place an order" +" in the *Purchase* app using the appropriate unit of measure " +"(:guilabel:`UoM`) for the quantity of products to be purchased." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:183 +msgid "" +":ref:`Simplify vendor unit conversions with UoMs <inventory/management/uom-" +"example>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:185 +msgid "" +"After the order is placed, navigate to the :menuselection:`Barcode` app to " +":ref:`receive the vendor shipment <barcode/operations/scan-received-" +"products>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:189 +msgid "" +"On the receipt in the *Barcode* app, receive an order for `52.1 kg` of " +"peaches by scanning the barcode containing the |GTIN| and quantity of " +"peaches in kilograms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:197 +msgid "52.1 kg of Peaches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "2D matrix of GS1 barcode of 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:205 +msgid "00614141000012" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:206 +msgid "|AI| (kg, 1 decimal point)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:207 +msgid "3101" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:209 +msgid "000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:211 +msgid "0100614141000012 3101000521" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:213 +msgid "" +":ref:`If the configuration is correct <barcode/operations/troubleshooting>`," +" `52.1 / 52.1` :guilabel:`kg` will be displayed and the :guilabel:`Validate`" +" button turns green. Finally, press :guilabel:`Validate` to complete the " +"validation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:0 +msgid "Scan barcode screen for a reception operation in the Barcode app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:222 +msgid "Verify product moves" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:224 +msgid "" +"For additional verification, the quantities of received products are also " +"recorded on the :guilabel:`Product Moves` report, accessible by navigating " +"to :menuselection:`Inventory app --> Reporting --> Product Moves`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:228 +msgid "" +"The items on the :guilabel:`Product Moves` report are grouped by product by " +"default. To confirm the received quantities, click on a product line to open" +" its collapsible drop-down menu, which displays a list of *stock move lines*" +" for the product. The latest stock move matches the warehouse reception " +"reference number (e.g. `WH/IN/00013`) and quantity processed in the barcode " +"scan, demonstrating that the records processed in the *Barcode* app were " +"properly stored in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst-1 +msgid "Reception stock move record for 52.1 kg of peaches." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:3 +msgid "Process receipts and deliveries with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:7 +msgid "" +"The *Barcode* app can be used to process receipts, deliveries, and other " +"types of operations in real time using a barcode scanner or the Odoo mobile " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:10 +msgid "" +"This makes it possible to process operations on the warehouse floor when " +"they happen, instead of having to wait to validate transfers from a " +"computer. Processing operations this way can help to properly attribute " +"barcodes to the appropriate products, pickings, locations, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:17 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:15 +msgid "" +"To use the *Barcode* app to process transfers, it must be installed by " +"enabling the feature from the settings of the *Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:20 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:18 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click " +"the checkbox next to the :guilabel:`Barcode Scanner` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:26 +msgid "" +"Once the page has refreshed, new options will be displayed under the " +":guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with " +"a corresponding drop-down menu), where either :guilabel:`Default " +"Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:30 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:29 +msgid "" +"There is also a :guilabel:`Configure Product Barcodes` internal link arrow, " +"and a set of :guilabel:`Print` buttons for printing barcode commands and a " +"barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:37 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:36 +msgid "" +"For more on setting up and configuring the :guilabel:`Barcode` app, refer to" +" the :doc:`Set up your barcode scanner <../setup/hardware>` and " +":doc:`Activate the Barcodes in Odoo <../setup/software>` documentation " +"pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:44 +msgid "Scan barcodes for receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:46 +msgid "" +"To process warehouse receipts for incoming products, there first needs to be" +" a purchase order (PO) created, and a receipt operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:49 +msgid "" +"To create a :abbr:`PO (purchase order)`, navigate to the " +":menuselection:`Purchase app --> Create` to create a new request for " +"quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:52 +msgid "" +"From the blank :abbr:`RFQ (request for quotation)` form, click the drop-down" +" menu next to the :guilabel:`Vendor` field to add a vendor. Then, on the " +":guilabel:`Product` line under the :guilabel:`Products` tab, click " +":guilabel:`Add a product`, and select the desired product(s) to add to the " +"quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:57 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form, then click " +":guilabel:`Confirm Order` to confirm the :abbr:`RFQ (request for quotation)`" +" to a :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Completed purchase order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:64 +msgid "" +"To process and scan barcodes for warehouse receipts, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:66 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented. To process receipts, click" +" on the :guilabel:`Operations` button at the bottom of the screen. This " +"navigates to an :menuselection:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:74 +msgid "" +"From this page, locate the :guilabel:`Receipts` card, and click the " +":guilabel:`# To Process` button to view all outstanding receipts. Then, " +"select the desired receipt operation to process. This navigates to the " +"barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:79 +msgid "" +"If *only* using a barcode scanner or the Odoo mobile app, the barcodes for " +"each transfer of a corresponding operation type can be scanned to be " +"processed easily. Once scanned, the products that are part of an existing " +"transfer can be scanned, and new products can be added to the transfer, as " +"well. Once all products have been scanned, validate the transfer to proceed " +"with the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:85 +msgid "" +"From this screen, an overview of all receipts to process within that " +"transfer (**WH/IN/000XX**) is shown. At the bottom of the screen, there are " +"options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if " +"products need to be added to the operation, or if the whole operation should" +" be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Overview of receipts in transfer to scan." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:94 +msgid "" +"To process and scan each product individually, choose a specific product " +"line. The :guilabel:`+#` button (in this case, :guilabel:`+10`) can be " +"clicked to indicate receipt of that product, or the :guilabel:`pencil` icon " +"can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:98 +msgid "" +"From this screen, the product that's being received is listed. Under the " +"product name, the :guilabel:`Quantity` line can be edited. Either change the" +" `0` in the line to the desired quantity, or click the :guilabel:`/# Units` " +"button (in this case, :guilabel:`/10 Units`) to automatically fill the " +"quantity ordered from the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:104 +msgid "" +"In the reception operation `WH/IN/00019`, `10 Units` of the `Barcode " +"Product` is expected to be received. `[BARCODE_PROD]` is the " +":guilabel:`Internal Reference` set on the product form. Scan the barcode of " +"the `Barcode Product` to receive one unit. Afterwards, click the " +":guilabel:`pencil` icon to manually enter the received quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Product line editor for individual transfer in Barcode app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:113 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:179 +msgid "" +"Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked " +"to add or subtract quantity of the product, and the :guilabel:`number keys` " +"can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:116 +msgid "" +"Below the :guilabel:`number keys` is the :guilabel:`location` line, which " +"reads `WH/Stock` by default, unless another *location* is listed on the " +"product itself. Click this line to reveal a drop-down menu of additional " +"locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:120 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:158 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:211 +msgid "" +"Once ready, click :guilabel:`Confirm` to confirm the changes made to the " +"product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:122 +msgid "" +"Then, from the overview page with all receipts to process within that " +"transfer (**WH/IN/000XX**), click the :guilabel:`+#` button on the product " +"line for the products being received, and click :guilabel:`Validate`. The " +"receipt has now been processed, and the :guilabel:`Barcode app` can be " +"closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Overview of receipts in transfer to validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:132 +msgid "Scan barcodes for delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:134 +msgid "" +"To process warehouse deliveries for outgoing products, there first needs to " +"be a sales order (SO) created, and a delivery operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:137 +msgid "" +"To create a :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales " +"app --> Create` to create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:140 +msgid "" +"From the blank quotation form, click the drop-down menu next to the " +":guilabel:`Customer` field to add a customer. Then, on the " +":guilabel:`Product` line under the :guilabel:`Order Lines` tab, click " +":guilabel:`Add a product`, and select the desired product(s) to add to the " +"quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:144 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form, and click " +":guilabel:`Confirm Order` to confirm the quotation to a :abbr:`SO (sales " +"order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Completed sales order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:151 +msgid "" +"To process and scan barcodes for warehouse deliveries, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:153 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented. To process deliveries, " +"click on the :guilabel:`Operations` button at the bottom of the screen. This" +" navigates to an :guilabel:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:157 +msgid "" +"From this page, locate the :guilabel:`Delivery Orders` card, and click the " +":guilabel:`# To Process` button to view all outstanding deliveries. Then, " +"select the desired delivery order to process. This navigates to the barcode " +"transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Operations overview page in Barcode app dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:165 +msgid "" +"From this screen, an overview of all deliveries to process within that " +"transfer (**WH/OUT/000XX**) is shown. At the bottom of the screen, there are" +" options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if" +" products need to be added to the operation, or if the whole operation " +"should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:170 +msgid "" +"To process and scan each product individually, choose a specific product " +"line. The :guilabel:`+1` button can be clicked to indicate delivery of that " +"product, or the :guilabel:`pencil icon` can be clicked to open a new screen " +"to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:174 +msgid "" +"From this screen, the product that's being delivered is listed. Under the " +"product name, the :guilabel:`Quantity` line can be edited. Either change the" +" `0` in the line to the desired quantity, or click the :guilabel:`/# Units` " +"button (in this case, :guilabel:`/10 Units`) to automatically fill the " +"quantity ordered from the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:182 +msgid "" +"Below the :guilabel:`number keys` is the :guilabel:`location` line, which " +"reads `WH/Stock` by default, unless another location is listed on the " +"product itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:185 +msgid "" +"This is the location that the product is being pulled from for delivery. " +"Click this line to reveal a drop-down menu of additional locations to choose" +" from (if this product is stored in multiple locations in the warehouse)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:190 +msgid "" +"For warehouses that have multiple different storage locations, putaway " +"rules, and removal strategies, additional steps can be added for various " +"operation types, while using the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:196 +msgid "" +"Then, from the overview page with all receipts to process within that " +"transfer (**WH/OUT/000XX**), click the :guilabel:`+#` button on the product " +"line for the products being received, and click :guilabel:`Validate`. The " +"delivery has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst-1 +msgid "Overview of deliveries in transfer to validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:3 +msgid "Create and process transfers with barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:5 +msgid "" +"The *Barcode* app can be used to process internal transfers for all types of" +" products, including transfers for products tracked using lots or serial " +"numbers. Transfers can be created from scratch in real time using an Odoo-" +"compatible barcode scanner or the Odoo mobile app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:9 +msgid "" +"For a list of Odoo-compatible barcode mobile scanners, and other hardware " +"for the *Inventory* app, refer to the `Odoo Inventory • Hardware page " +"<https://www.odoo.com/app/inventory-hardware>`_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:24 +msgid "" +"When the page has refreshed, new options are displayed under the " +":guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with " +"a corresponding drop-down menu), where either :guilabel:`Default " +"Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. The " +"nomenclature selected changes how scanners interpret barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:41 +msgid "Scan barcodes for internal transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:43 +msgid "" +"To create and process internal transfers for products in a warehouse, the " +":guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features " +"**must** be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:46 +msgid "" +"To do so, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`. Then, scroll down to the :guilabel:`Warehouse` section, and click" +" the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-" +"Step Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:50 +msgid "Then, click :guilabel:`Save` at the top of the page to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:53 +msgid "Create an internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:55 +msgid "" +"To process existing internal transfers, there first needs to be an internal " +"transfer created, and an operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:58 +msgid "" +"To create an internal transfer, navigate to the :menuselection:`Inventory " +"app`. From the :guilabel:`Inventory Overview` dashboard, locate the " +":guilabel:`Internal Transfers` card, and click on the :guilabel:`0 To " +"Process` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:62 +msgid "" +"Then, click :guilabel:`Create` in the top left of the resulting page. This " +"navigates to a new :guilabel:`Internal Transfer` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:65 +msgid "" +"On this blank form, the :guilabel:`Operation Type` is automatically listed " +"as :guilabel:`Internal Transfers`. Under that field, the :guilabel:`Source " +"Location` and :guilabel:`Destination Location` are set as " +":guilabel:`WH/Stock` by default, but can be changed to whichever locations " +"the products are being moved from, and moved to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "" +"Blank internal transfer form with source location and destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:74 +msgid "" +"Once the desired locations have been selected, products can be added to the " +"transfer. On the :guilabel:`Product` line under the :guilabel:`Products` " +"tab, click :guilabel:`Add a product`, and select the desired product(s) to " +"add to the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:78 +msgid "" +"Once ready, click :guilabel:`Save` at the top of the form to save the new " +"internal transfer. Once saved, click the :guilabel:`Detailed Operations` " +"icon (four lines, at the far right of the :guilabel:`Product` line) to open " +"the :guilabel:`Detailed Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Internal transfer detailed operations pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:86 +msgid "From the pop-up, click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:88 +msgid "" +"Then, in the :guilabel:`To` column, change the location from " +":guilabel:`WH/Stock` to a different location, where the products should be " +"moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:91 +msgid "" +"Next, in the :guilabel:`Done` column, change the quantity to the desired " +"quantity to transfer. Once ready, click :guilabel:`Confirm` to close out the" +" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:95 +msgid "Scan barcodes for internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:97 +msgid "" +"To process and scan barcodes for internal transfers, navigate to the " +":menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:99 +msgid "" +"Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` " +"screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:102 +msgid "" +"To process internal transfers, click on the :guilabel:`Operations` button at" +" the bottom of the screen. This navigates to an :menuselection:`Operations` " +"overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:109 +msgid "" +"From this page, locate the :guilabel:`Internal Transfers` card, and click " +"the :guilabel:`# To Process` button to view all outstanding internal " +"transfers. Then, select the desired operation to process. This navigates to " +"the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:114 +msgid "" +"When using the *Barcode* app without the *Inventory* app (**only** if using " +"a barcode scanner or the Odoo mobile app), the barcodes for each transfer of" +" a corresponding operation type can be scanned to be processed easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:118 +msgid "" +"Once scanned, the products that are part of an existing transfer can be " +"scanned, and new products can be added to the transfer, as well. Once all " +"products have been scanned, validate the transfer to proceed with the stock " +"moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:122 +msgid "" +"From this screen, an overview of all products to process within that " +"specific internal transfer (**WH/INT/000XX**) is shown. At the bottom of the" +" screen, there are options to :guilabel:`Add Product` or " +":guilabel:`Validate`, depending on if products need to be added to the " +"operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:131 +msgid "" +"Then, scan the barcode of the product to process the internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:133 +msgid "" +"Or, to process and scan each product individually, choose a specific product" +" line. The :guilabel:`+ 1` button can be clicked to add additional quantity " +"of that product to the transfer, or the :guilabel:`pencil icon` can be " +"clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:137 +msgid "" +"In the product's pop-up window, the product and the units to process is " +"displayed with a number pad. Under the product name, the " +":guilabel:`Quantity` line can be edited. Change the number in the line to " +"the quantity listed to be transferred on the internal transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:142 +msgid "" +"In the internal transfer operation `WH/INT/000XX`, `50 Units` of the " +"`Transfer Product` is moved from `WH/Stock` to `WH/Stock/Shelf 1`. " +"`[TRANSFER_PROD]` is the :guilabel:`Internal Reference` set on the product " +"form. Scan the barcode of the `Transfer Product` to receive one unit. " +"Afterwards, click the :guilabel:`pencil icon` to manually enter the " +"transferred quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:151 +msgid "" +"Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked " +"to add or subtract quantity of the product, and the number keys can be used " +"to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:154 +msgid "" +"Below the number keys are the two :guilabel:`location` lines, which read " +"whichever locations were previously specified on the internal transfer form," +" in this case `WH/Stock` and `WH/Stock/Shelf 1`. Click these lines to reveal" +" a drop-down menu of additional locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:160 +msgid "" +"Then, from the overview page with all products to process within that " +"transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The receipt has now" +" been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:165 +msgid "" +"The *Barcode* app can also be used to scan products in internal transfers " +"containing unique lot numbers and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:168 +msgid "" +"From the barcode transfer screen, scan the barcode of a lot or serial " +"number, and Odoo automatically increases the quantity of the product to the " +"quantity recorded in the database. If the same lot or serial number is " +"shared between different products, scan the product barcode first, then the " +"barcode of the lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:174 +msgid "Create a transfer from scratch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:176 +msgid "" +"In addition to processing and scanning barcodes for existing, previously-" +"created internal transfers, the *Barcode* app can also be used to create " +"transfers from scratch, simply by scanning a printed operation type barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:182 +msgid "" +"Odoo's *Barcode* application provides demo data with barcodes to explore the" +" features of the app. These can be used for testing purposes, and can be " +"printed from the home screen of the app. To access this demo data, navigate " +"to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes " +"sheet` (bolded and highlighted in blue) in the information pop-up above the " +"scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:191 +msgid "" +"To do this, first navigate to the :menuselection:`Barcode app`. Once inside " +"the *Barcode* app, a :guilabel:`Barcode Scanning` screen displaying " +"different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:194 +msgid "" +"From this screen, when using a USB or bluetooth barcode scanner, directly " +"scan the product barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:196 +msgid "" +"When using a smartphone as the barcode scanner, click the :guilabel:`Tap to " +"Scan` button (next to the camera icon, at the center of the screen). This " +"opens a :guilabel:`Barcode Scanner` pop-up screen that enables the camera of" +" the device being used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:200 +msgid "" +"Face the camera toward the printed operation type barcode to scan it. Doing " +"so processes the barcode, and navigates to a barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:203 +msgid "" +"From this screen, an overview of all products to process within that " +"specific internal transfer (**WH/INT/000XX**) is shown. Since this is a new " +"transfer created from scratch, however, there should not be any products " +"listed on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:207 +msgid "" +"To add products, scan the product barcode. If the barcode is not available, " +"manually enter the product into the system by clicking the :guilabel:`Add " +"Product` button at the bottom of the screen, and add the products and " +"product quantities that should be transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst-1 +msgid "Blank product editor in scratch internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:217 +msgid "" +"Then, from the overview page with all products to process within that " +"transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The internal " +"transfer has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup.rst:5 +msgid "Setup" +msgstr "ตั้งค่า" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:3 +msgid "Set up your barcode scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:7 +msgid "" +"Follow this guide to choose and set up a barcode scanner compatible with " +"Odoo's *Inventory* and *Barcode* apps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:14 +msgid "An image of an example barcode scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:17 +msgid "Scanner types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:19 +msgid "" +"Before setting up a barcode scanner, it is important to determine which " +"scanner type best meets the needs of the business. There are three main " +"types, each with their own benefits and use cases:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:22 +msgid "" +"**USB scanners** are connected to a computer, and are suitable for " +"businesses that scan products at a fixed location, like at the checkout in a" +" grocery store. Ensure the chosen USB scanner is compatible with the " +"keyboard layout of the computer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:26 +msgid "" +"**Bluetooth scanners** pair with a smartphone or tablet, making them an " +"ideal cost-effective and portable barcode scanner option. In this scenario, " +"Odoo is installed on the smartphone, allowing warehouse operators to handle " +"operations, and check stock directly through their mobile devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:30 +msgid "" +"**Mobile computer scanners** are mobile devices with a built-in barcode " +"scanner. First, ensure the device can run the Odoo mobile app properly. " +"Recent models that use Android OS with the Google Chrome browser, or Windows" +" OS with Microsoft Edge, should work. However, testing is crucial due to the" +" variety of available models and configurations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:36 +msgid "" +"`Compatible hardware with Odoo Inventory " +"<https://www.odoo.com/app/inventory-hardware>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:41 +msgid "" +"When setting up the barcode scanner, make sure the following configurations " +"are correct so the scanner can properly interpret barcodes with Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:45 +msgid "Keyboard layout" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:47 +msgid "" +"When using a USB barcode scanner, match its keyboard layout with the " +"operating system's layout for proper interpretation of characters. " +"Generally, the scanning mode should be set to accept a USB keyboard (HID), " +"with the language set based on the keyboard that is in use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:51 +msgid "" +"To configure the keyboard layout for a **Zebra** scanner, scan the keyboard " +"wedge barcode for the desired language in the scanner's user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "Example of a user manual for keyboard layout." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:57 +msgid "" +"Examples of keyboard language settings in the Zebra scanner user manual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:60 +msgid "Automatic carriage return" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:62 +msgid "" +"Odoo has a default 100-millisecond delay between scans to prevent accidental" +" double scanning. To synchronize with the barcode scanner, set it to include" +" a *carriage return* (:dfn:`character like the \"Enter\" key on a keyboard`)" +" after each scan. Odoo interprets the carriage return as the end of the " +"barcode input; so Odoo accepts the scan, and waits for the next one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:67 +msgid "" +"Typically, on the scanner, a carriage return is included by default. Ensure " +"it is set by scanning a specific barcode in the user manual, like `CR suffix" +" ON` or `Apply Enter for suffix`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:71 +msgid "Zebra scanner" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:73 +msgid "" +"When using Zebra scanners, ensure the following keystroke configurations are" +" set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:75 +msgid "" +"Begin on the Zebra scanner's home screen, and select the " +":guilabel:`DataWedge` app (the icon for the app is a light blue barcode). On" +" the :guilabel:`DataWedge Profiles` page, select the profile option to " +"access the Zebra scanner's settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:79 +msgid "" +"Scroll down to the :guilabel:`Keyboard Output` option, and ensure the " +":guilabel:`Enable/disable keystroke output` option is :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst-1 +msgid "Show keystroke option in the Zebra scanner's DataWedge app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:86 +msgid "" +"Now, go back to the :guilabel:`Profile` options page, and select " +":guilabel:`Key event options`. Here, ensure the :guilabel:`Send Characters " +"as Events` option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:3 +msgid "Activate the Barcodes in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:7 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:16 +msgid "" +"To use this feature, you first need to activate the *Barcode* functionality " +"via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you " +"have ticked the feature, you can hit save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:24 +msgid "Set Product Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:26 +msgid "" +"You can easily assign barcodes to your different products via the " +"*Inventory* app. To do so, go to :menuselection:`Settings --> Configure " +"Products Barcodes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:32 +msgid "" +"Then, you have the possibility to assign barcodes to your products directly " +"at creation on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:42 +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 "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:49 +msgid "Set Locations Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:51 +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 --> " +"Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:62 +msgid "" +"You can easily print the barcode you allocate to the locations via the " +"*Print* menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:66 +msgid "Barcode Formats" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:68 +msgid "" +"Most retail products use EAN-13 barcodes, also known as GTIN (Global Trade " +"Identification Numbers). GTIN are used by companies to uniquely identify " +"their products and services. While GTIN and UPC are often used synonymously," +" GTIN refers to the number a barcode represents, while UPC refers to the " +"barcode itself. More information about GTIN can be found on the GS1 website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:73 +msgid "" +"In order to create GTIN for items, a company must have a GS1 Company Prefix." +" This prefix is the number that will appear at the beginning of each GTIN, " +"and will identify the company as the owner of the barcode any the products " +"it appears on. To learn more about GS1 Company Prefixes, or purchase a " +"license for a prefix, visit the GS1 Company Prefix page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:78 +msgid "" +"Odoo users are able to use GTIN barcodes to identify their products. " +"However, since Odoo supports any numeric string as a barcode, it is also " +"possible to define a custom barcode for internal use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:8 +msgid "Inventory" +msgstr "คลังสินค้า" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:10 +msgid "" +"Odoo *Inventory* is both an inventory application and a warehouse management" +" system. The app allows users to easily manage lead times, automate " +"replenishment, configure advanced routes, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory.rst:14 +msgid "" +"`Odoo Tutorials: Inventory <https://www.odoo.com/slides/inventory-24>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management.rst:5 +msgid "Product management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment.rst:5 +msgid "Product replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:3 +msgid "Replenish on order (MTO)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:9 +msgid "" +"*Replenish on order*, also known as *MTO* (make to order), is a " +"replenishment strategy that creates a draft order for a product every time a" +" sales order is created for it. For products that are purchased from a " +"vendor, a request for quotation (RFQ) is created, while a sales order for a " +"product manufactured in-house triggers the creation of a manufacturing " +"order. The creation of a |RFQ| or manufacturing order occurs every time a " +"sales order is created, regardless of the current stock level of the product" +" being ordered." +msgstr "" +"*เติมสินค้าตามคำสั่งซื้อ* หรือที่เรียกว่า *MTO* (สั่งทำ) " +"เป็นกลยุทธ์การเติมสินค้าที่สร้างใบสั่งที่ร่างสำหรับผลิตภัณฑ์ทุกครั้งที่สร้างใบสั่งขาย" +" สำหรับผลิตภัณฑ์ที่ซื้อจากผู้ขาย จะมีการสร้างคำขอใบเสนอราคา (RFQ) " +"ในขณะที่ใบสั่งขายสำหรับผลิตภัณฑ์ที่ผลิตภายในบริษัทจะเริ่มต้นการสร้างใบสั่งผลิต" +" การสร้าง |RFQ| หรือใบสั่งผลิตเกิดขึ้นทุกครั้งที่มีการสร้างใบสั่งขาย " +"โดยไม่คำนึงถึงระดับสต็อกปัจจุบันของผลิตภัณฑ์ที่สั่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:17 +msgid "Unarchive the Replenish on Order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:19 +msgid "" +"By default, Odoo sets the |MTO| route as *archived*. This is because |MTO| " +"is a somewhat niche workflow that is only used by certain companies. " +"However, it is easy to unarchive the route in just a few simple steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:23 +msgid "" +"To do so, begin by navigating to :menuselection:`Inventory --> Configuration" +" --> Routes`. On the :guilabel:`Routes` page, click the :guilabel:`Filters` " +"button and select the :guilabel:`Archived` option. This shows all routes " +"that are currently archived." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The archived filter on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:31 +msgid "" +"Enable the checkbox next to :guilabel:`Replenish on Order (MTO)`, then click" +" the :guilabel:`Action` button to reveal a drop-down menu. From the drop-" +"down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The unarchive action on the Routes page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:38 +msgid "" +"Finally, remove the :guilabel:`Archived` filter from the " +":guilabel:`Search...` bar. The :guilabel:`Routes` page will now show all " +"available routes, including :guilabel:`Replenish on Order (MTO)`, which is " +"now selectable on the inventory tab of each product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "The MTO route appears on the Routes page after unarchiving it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:47 +msgid "Configure a product to use the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:49 +msgid "" +"With the |MTO| route unarchived, products can now be properly configured to " +"use replenish on order. To do so, begin by going to " +":menuselection:`Inventory --> Products --> Products`, then select an " +"existing product, or click :guilabel:`Create` to configure a new one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:53 +msgid "" +"On the product page, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Replenish on Order (MTO)` route in the :guilabel:`Routes` " +"section, along with one other route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:57 +msgid "" +"The :guilabel:`Replenish on Order (MTO)` route **does not** work unless " +"another route is selected as well. This is because Odoo needs to know how to" +" replenish the product when an order is placed for it (buy it, manufacture " +"it, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "Select the MTO route and a second route on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:65 +msgid "" +"If the product is purchased from a vendor to fulfill sales orders, enable " +"the :guilabel:`Can be Purchased` checkbox under the product name. Doing so " +"makes the :guilabel:`Purchase` tab appear alongside the other settings tabs " +"below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:69 +msgid "" +"Select the :guilabel:`Purchase` tab and specify a :guilabel:`Vendor` and the" +" :guilabel:`Price` they sell the product for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst-1 +msgid "Enable \"Can be Purchased\" and specify a vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:76 +msgid "" +"If the product is manufactured, make sure that it has a bill of materials " +"(BOM) configured for it. To do so, click the :guilabel:`Bill of Materials` " +"smart button at the top of the screen, then click :guilabel:`Create` on the " +":guilabel:`Bill of Materials` page to configure a new |BOM| for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:81 +msgid "" +"On the blank |BOM| form, add the components used to manufacture the product " +"on the :guilabel:`Components` tab, along with the operations required for " +"the manufacturing workflow on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:85 +msgid "Finally, click :guilabel:`Save` to save the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:88 +msgid "Fulfill a sales order using the MTO route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:90 +msgid "" +"After configuring a product to use the |MTO| route, a replenishment order is" +" created for it every time a sales order including the product is confirmed." +" The type of order created depends on the second route selected in addition " +"to |MTO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:94 +msgid "" +"For example, if *Buy* was the second route selected, then a purchase order " +"is created upon confirmation of a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:98 +msgid "" +"When the |MTO| route is enabled for a product, a replenishment order is " +"always created upon confirmation of a sales order. This is the case even if " +"there is enough stock of the product on-hand to fulfill the sales order, " +"without buying or manufacturing additional units of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:102 +msgid "" +"While the |MTO| route can be used in unison with a variety of other routes, " +"the *Buy* route is used as the example for this workflow. Begin by " +"navigating to the :menuselection:`Sales` app, then click :guilabel:`Create`," +" which opens a blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:106 +msgid "" +"On the blank quotation form, add a :guilabel:`Customer`, then click " +":guilabel:`Add a product` under the :guilabel:`Order Lines` tab, and enter a" +" product that has been configured to use the *MTO* and *Buy* routes. Click " +":guilabel:`Confirm` and the quotation is turned into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:110 +msgid "" +"A :guilabel:`Purchase` smart button now appears in the top-right corner of " +"the sales order. Clicking it opens the |RFQ| associated with the sales " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:113 +msgid "" +"Click :guilabel:`Confirm Order` to confirm the |RFQ|, and turn it into a " +"purchase order. A green :guilabel:`Receive Products` button now appears at " +"the top of the purchase order. Once the products are received, click " +":guilabel:`Receive Products` to register them into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:117 +msgid "" +"Return to the sales order by clicking the :guilabel:`SO` breadcrumb, or by " +"navigating to :menuselection:`Sales --> Orders --> Orders`, and selecting " +"the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/mto.rst:120 +msgid "" +"Finally, click the :guilabel:`Delivery` smart button in the top-right of the" +" order to be taken to the delivery order. Once the products have been " +"shipped to the customer, click :guilabel:`Validate` to confirm the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:3 +msgid "Reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:7 +msgid "" +"Reordering rules are used to keep forecasted stock levels above a certain " +"threshold without exceeding a specified upper limit. This is accomplished by" +" specifying a minimum quantity that stock should not fall below and a " +"maximum quantity that stock should not exceed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:11 +msgid "" +"Reordering rules can be configured for each product based on the route used " +"to replenish it. If a product uses the *Buy* route, then a Request for " +"Quotation (RFQ) is created when the reordering rule is triggered. If a " +"product uses the *Manufacture* route, then a Manufacturing Order (MO) is " +"created instead. This is the case regardless of the selected replenishment " +"route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:17 +msgid "Configure products for reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:19 +msgid "" +"In order to use reordering rules for a product, it must first be correctly " +"configured. Begin by navigating to :guilabel:`Inventory --> Products --> " +"Products`, then select an existing product, or create a new one by clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:23 +msgid "" +"First, on the :guilabel:`General Information` tab, make sure that the " +":guilabel:`Product Type` is set to :guilabel:`Storable Product`. This is " +"necessary because Odoo only tracks stock quantities for storable products, " +"and this number is used to trigger reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Set the Product Type as Storable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:31 +msgid "" +"Next, click on the :guilabel:`Inventory` tab and select one or more routes " +"from the :guilabel:`Routes` section. Doing so tells Odoo which route to use " +"to replenish the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Select one or more routes on the Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:38 +msgid "" +"If the product is reordered using the :guilabel:`Buy` route, confirm that " +"the :guilabel:`Can be Purchased` checkbox is enabled under the product name." +" This makes the :guilabel:`Purchase` tab appear. Click on the " +":guilabel:`Purchase` tab, and specify at least one vendor, and the price " +"that they sell the product for, so that Odoo knows which company the product" +" should be purchased from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Specify a vendor and price on the Purchase tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:47 +msgid "" +"If the product is replenished using the :guilabel:`Manufacture` route, it " +"needs to have at least one Bill of Materials (BoM) associated with it. This " +"is necessary because Odoo only creates manufacturing orders for products " +"with a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:51 +msgid "" +"If a :abbr:`BoM (Bill of Materials)` does not already exist for the product," +" select the :guilabel:`Bill of Materials` smart button at the top of the " +"product form, then click :guilabel:`Create` to configure a new :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "The Bill of Materials smart button on a product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:60 +msgid "Create new reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:62 +msgid "" +"To create a new reordering rule, navigate to :menuselection:`Inventory --> " +"Configuration --> Reordering Rules`, then click :guilabel:`Create`, and fill" +" out the new line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:65 +msgid ":guilabel:`Product`: The product that is replenished by the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:66 +msgid ":guilabel:`Location`: The location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:67 +msgid "" +":guilabel:`Min Quantity`: The minimum quantity that can be forecasted " +"without the rule being triggered. When forecasted stock falls below this " +"number, a replenishment order for the product is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:70 +msgid "" +":guilabel:`Max Quantity`: The maximum quantity that stock is replenished up " +"to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:71 +msgid "" +":guilabel:`Multiple Quantity`: Specify if the product should be replenished " +"in batches of a certain quantity (e.g., a product could be replenished in " +"batches of 20)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:73 +msgid "" +":guilabel:`UoM`: The unit of measure used for reordering the product. This " +"value can simply be `Units` or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "The form for creating a new reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:81 +msgid "" +"Reordering rules can also be created from each product form. To do so, " +"navigate to :menuselection:`Inventory --> Products --> Products`, then " +"select a product. Click on :menuselection:`Reordering Rules --> Create`, " +"then fill out the new line as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:85 +msgid "" +"Once a reordering rule has been created for a product, if its forecasted " +"quantity is below the rule's minimum quantity when the scheduler runs, a " +"replenishment order for the product is automatically generated. By default, " +"the scheduler runs once each day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:90 +msgid "" +"To manually trigger a reordering rule before the scheduler runs, select " +":menuselection:`Inventory --> Operations --> Run Scheduler`. Then, select " +"the green :guilabel:`Run Scheduler` button on the pop-up that appears. Be " +"aware that this also triggers any other scheduled actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:94 +msgid "" +"If the :guilabel:`Buy` route is selected, then an :abbr:`RFQ (Request for " +"Quotation)` is generated. To view and manage :abbr:`RFQs (Requests for " +"Quotation)`, navigate to :menuselection:`Purchase --> Orders --> Requests " +"for Quotation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:98 +msgid "" +"If the :guilabel:`Manufacture` route is selected, then an :abbr:`MO " +"(Manufacturing Order)` is generated. To view and manage :abbr:`MOs " +"(Manufacturing Orders)`, navigate to :menuselection:`Manufacturing --> " +"Operations --> Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:103 +msgid "Set a preferred route for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:105 +msgid "" +"Odoo allows for multiple routes to be selected under the " +":guilabel:`Inventory` tab on each product form. For instance, it is possible" +" to select both :guilabel:`Buy` and :guilabel:`Manufacture`, thus enabling " +"the functionality of both routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:109 +msgid "" +"Odoo also enables users to set a preferred route for a product's reordering " +"rule. This is the route that the rule defaults to if multiple are selected. " +"To select a preferred route, begin by navigating to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:113 +msgid "" +"By default, the :guilabel:`Preferred Route` column is hidden on the " +":guilabel:`Reordering Rules` page. Enable it by selecting the :guilabel:`⋮ " +"(three-dot)` option button on the right side of the page and checking the " +":guilabel:`Preferred Route` checkbox. Doing so reveals the " +":guilabel:`Preferred Route` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:118 +msgid "" +"Click inside of the column on the row of a reordering rule and a drop-down " +"menu shows all available routes for that rule. Select one to set it as the " +"preferred route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst-1 +msgid "Select a preferred route from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:126 +msgid "" +"If multiple routes are enabled for a product but no preferred route is set " +"for its reordering rule, the product is reordered using the selected route " +"that is listed first on the :guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:3 +msgid "Scrap inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:5 +msgid "" +"In some cases, a product in inventory may be damaged or found to be " +"defective. If it is not possible to repair or return the product, Odoo " +"*Inventory* allows users to scrap it, ensuring that usable inventory counts " +"remain accurate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:19 +msgid "" +"Scrap orders can be viewed by navigating to :menuselection:`Inventory --> " +"Operations --> Scrap`. Each scrap order shows the date and time the order " +"was created, along with the product and quantity that was scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:14 +msgid "" +"To view the total quantity of each item scrapped, navigate to " +":menuselection:`Inventory --> Configuration --> Locations`. Remove the " +":guilabel:`Internal` filter from the :guilabel:`Search...` bar to display " +"virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:19 +msgid "" +"By default, scrapping a product removes it from physical inventory, and " +"places it in a virtual location titled *Virtual Locations/Scrap*. A virtual " +"location is **not** a physical space, but rather a designation in Odoo that " +"is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:30 +msgid "Learn more" +msgstr "เรียนรู้เพิ่มเติม" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:25 +msgid "" +"For more information about virtual locations, see the documentation about " +"the different types of :ref:`locations <inventory/management/difference-" +"warehouse-location>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:29 +msgid "Scrap from stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:31 +msgid "" +"To scrap a product located in inventory, begin by navigating to " +":menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap" +" Orders` page, click :guilabel:`Create` to configure a new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:35 +msgid "" +"On the scrap order, select the product being scrapped from the " +":guilabel:`Product` drop-down menu, then enter the quantity in the " +":guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the " +"location where the product is stored, and the :guilabel:`Scrap Location` " +"defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be " +"changed by selecting a different location from their respective drop-down " +"menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "A new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:45 +msgid "" +"Finally, click :guilabel:`Validate` to scrap the product. The on-hand " +"inventory count for the scrapped product updates to subtract the scrapped " +"quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:49 +msgid "Scrap from a receipt, transfer, or delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:51 +msgid "" +"It is also possible to scrap products during the receipt, transfer, and " +"delivery operations. This can be necessary if any products are found to be " +"defective when receiving them into inventory, transferring them from one " +"location to another, or preparing them for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:55 +msgid "" +"To scrap a product during the receipt, transfer, or delivery operations, " +"begin by navigating to the :menuselection:`Inventory` app. On the " +":guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the" +" :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or " +":guilabel:`Delivery Orders` card, depending on the type of operation the " +"product is being scrapped from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:61 +msgid "" +"For the :guilabel:`Internal Transfers` card to appear on the " +":menuselection:`Overview` page of the :menuselection:`Inventory` app, the " +":guilabel:`Storage Locations` setting must be enabled. To do so, navigate to" +" :menuselection:`Configuration --> Settings`, then enable the checkbox next " +"to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:66 +msgid "" +"Alternatively, a list of all delivery orders, receipts, and transfers can be" +" viewed by navigating to :menuselection:`Inventory --> Operations --> " +"Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:69 +msgid "" +"Next, open a delivery order, receipt, or transfer from the corresponding " +"page by clicking on it. A :guilabel:`Scrap` button appears at the top of the" +" page. Click it to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "The scrap pop-up in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:78 +msgid "" +"The :guilabel:`Scrap` button will only appear on a receipt that has been " +"validated. This is because Odoo only allows products to be scrapped once " +"they have been entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:81 +msgid "" +"On the :guilabel:`Scrap` pop-up window, select the product being scrapped " +"from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the" +" :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:84 +msgid "" +"The :guilabel:`Source Location` defaults to the location where the product " +"is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual" +" Locations/Scrap`, but either of these can be changed by selecting a " +"different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:88 +msgid "" +"Finally, click :guilabel:`Done` to scrap the product. After doing so, the " +":guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart " +"button appears in the top right of the page. Click it to view all of the " +"scrap orders created from that operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst-1 +msgid "The Scraps smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:3 +msgid "Selecting a replenishment strategy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:10 +msgid "" +"In Odoo, there are two strategies for automatically replenishing inventory: " +"*reordering rules* and the *make to order (MTO)* route. Although these " +"strategies differ slightly, they both have similar consequences: triggering " +"the automatic creation of a |PO| or |MO|. The choice of which strategy to " +"use depends on the business's manufacturing and delivery processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:6 +msgid "Terminology" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:19 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:56 +msgid "Replenishment report and reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:21 +msgid "" +"The replenishment report is a list of all products that have a negative " +"forecast quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:23 +msgid "" +"*Reordering rules* are used to ensure there's always a minimum amount of a " +"product in-stock, in order to manufacture products and/or fulfill sales " +"orders. When the stock level of a product reaches its minimum, Odoo " +"automatically generates a purchase order with the quantity needed to reach " +"the maximum stock level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:28 +msgid "" +"Reordering rules can be created and managed in the replenishment report, or " +"from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:33 +msgid "Make to order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:35 +msgid "" +"*Make to order (MTO)* is a procurement route that creates a draft purchase " +"order (or manufacturing order) each time a sales order is confirmed, " +"**regardless of the current stock level**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:38 +msgid "" +"Unlike products replenished using reordering rules, Odoo automatically links" +" the sales order to the |PO| or |MO| generated by the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:41 +msgid "" +"Another difference between reordering rules and |MTO| is, with |MTO|, Odoo " +"generates a draft |PO| or |MO| immediately after the |SO| is confirmed. With" +" reordering rules, Odoo generates a draft |PO| or |MO| when the product's " +"forecasted stock falls below the set minimum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:45 +msgid "" +"In addition, Odoo automatically adds quantities to the |PO| or |MO| as the " +"forecast changes, so long as the |PO| or |MO| is not confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:48 +msgid "" +"The |MTO| route is the best replenishment strategy for products that are " +"customized, and/or for products that have no stock kept on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:58 +msgid "" +"To access the replenishment report, go to :menuselection:`Inventory app --> " +"Operations --> Replenishment.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:61 +msgid "" +"By default, the replenishment report dashboard shows every product that " +"needs to be manually reordered. If there is no specific rule for a product, " +"Odoo assumes the :guilabel:`Min Quantity` and :guilabel:`Max Quantity` stock" +" are both `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:66 +msgid "" +"For products that don't have a set reordering rule, Odoo calculates the " +"forecast based on confirmed sales orders, deliveries, and receipts. For " +"products that have a set reordering rule, Odoo calculates the forecast " +"normally, but also takes into account the purchase/manufacturing lead time " +"and security lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:72 +msgid "" +"Before creating a new reordering rule, make sure the product has a *vendor* " +"or a *bill of materials* configured on the product form. To check this, go " +"to :menuselection:`Inventory app --> Products --> Products`, and select the " +"product to open its product form. The vendor, if configured, is listed in " +"the :guilabel:`Purchase` tab, and the bill on materials, if configured, is " +"found in the :guilabel:`Bill of Materials` smart button at the top of the " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:78 +msgid "" +"The :guilabel:`Product Type`, located in the :guilabel:`General Information`" +" tab on the product form, **must** be set to :guilabel:`Storable Product`. " +"By definition, a consumable product does not have its inventory levels " +"tracked, so Odoo cannot account for a consumable product in the " +"replenishment report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Replenishment report listing all items needing to be purchased to meet " +"current needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:87 +msgid "" +"To create a new reordering rule from the replenishment report, go to " +":menuselection:`Inventory app --> Operations --> Replenishment`, click " +":guilabel:`Create`, and select the desired product from the drop-down menu " +"in the :guilabel:`Product` column. If necessary, a :guilabel:`Min Quantity` " +"and a :guilabel:`Max Quantity` can be configured in the corresponding " +"columns on the :guilabel:`Replenishment` report page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:93 +msgid "" +"To create a new reordering rule from the product form, go to " +":menuselection:`Inventory app --> Products --> Products`, and select a " +"product to open its product form. Click the :guilabel:`Reordering Rules` " +"smart button, click :guilabel:`Create`, and fill out the fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:98 +msgid "Replenishment report fields" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:100 +msgid "" +"The following fields are on the :guilabel:`Replenishment` report. If any of " +"these fields are not visible, click the :guilabel:`⋮ (additional options)` " +"icon on the far right side of the report, then click the checkbox next to a " +"field to make it visible." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:104 +msgid ":guilabel:`Product`: the product that requires a replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:105 +msgid "" +":guilabel:`Location`: the specific location where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:106 +msgid ":guilabel:`Warehouse`: the warehouse where the product is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:107 +msgid ":guilabel:`On Hand`: the amount of product currently available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:108 +msgid "" +":guilabel:`Forecast`: the amount of product available after all current " +"orders (sales, manufacturing, purchase, etc.) are taken into account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:110 +msgid "" +":guilabel:`Preferred Route`: how the product is procured, either " +":guilabel:`Buy`, :guilabel:`Manufactured`, :guilabel:`Dropship`, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:112 +msgid ":guilabel:`Vendor`: the company from which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:113 +msgid "" +":guilabel:`Bill of Materials`: the bill of materials for the product (if one" +" is configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:114 +msgid "" +":guilabel:`Trigger`: how the replenishment is created, either " +":guilabel:`Auto` (automatically, once the :guilabel:`On Hand` quantity goes " +"below the :guilabel:`Min Quantity`) or :guilabel:`Manual` (only when the " +"replenishment is requested)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:117 +msgid "" +":guilabel:`Procurement Group`: the reference number for how the product is " +"being acquired, such as a sales order, purchase order, or manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:119 +msgid "" +":guilabel:`Min Quantity`: the minimum amount of product that should be " +"available. When inventory levels goes below this number, the replenishment " +"is triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:121 +msgid "" +":guilabel:`Max Quantity`: the amount of product that should be available " +"after replenishing the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:123 +msgid "" +":guilabel:`Multiple Quantity`: if the product should be ordered in specific " +"quantities, enter the number that should be ordered. For example, if the " +":guilabel:`Multiple Quantity` is set to `5`, and only 3 are needed, 5 " +"products are replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:126 +msgid "" +":guilabel:`To Order`: the amount of product that is currently needed, and " +"will be ordered, if the :guilabel:`Order Once` or :guilabel:`Automate " +"Orders` button is clicked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:128 +msgid ":guilabel:`UoM`: the unit of measure used to acquire the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:129 +msgid ":guilabel:`Company`: the company for which the product is acquired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:131 +msgid "" +"By default, the quantity in the :guilabel:`To Order` field is the quantity " +"required to reach the set :guilabel:`Max Quantity`. However, the " +":guilabel:`To Order` quantity can be adjusted by clicking on the field and " +"changing the value. To replenish a product manually, click :guilabel:`Order " +"Once`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:135 +msgid "" +"To automate a replenishment from the :guilabel:`Replenishment` page, click " +":guilabel:`Automate Orders` on the right-side of the line, represented by a " +":guilabel:`🔄 (circular arrow)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:138 +msgid "" +"When this button is clicked, Odoo will automatically generate a draft " +"|PO|/|MO| every time the forecasted stock level falls below the set " +":guilabel:`Min Quantity` of the reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:141 +msgid "" +"On the :guilabel:`Replenishment` page, a reordering rule or manual " +"replenishment can be temporarily deactivated for a given period, by clicking" +" the :guilabel:`🔕 (snooze)` icon on the far-right of the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Snooze options to turn off notifications for reordering for a period of " +"time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:149 +msgid "" +"A |PO| or |MO| created by a manual replenishment has a " +":guilabel:`Replenishment Report` as the source document. A |PO| or |MO| " +"created by an automated reordering rule has the |SO| reference number(s) " +"that triggered the rule as the source document." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "" +"Quote request list shows which quotes are directly from the replenishment " +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:158 +msgid "Make to order (MTO) route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:160 +msgid "" +"Since the |MTO| route is recommended for customized products, the route is " +"hidden by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:169 +msgid "To activate the |MTO| route in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:163 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:164 +msgid "" +"Activate the :guilabel:`Multi-Step Routes` setting, located under the " +":guilabel:`Warehouse` section, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:166 +msgid "" +"Then, go to :menuselection:`Inventory app --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:167 +msgid "" +"Click on :menuselection:`Filters --> Archived` to show archived routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:168 +msgid "" +"Select the checkbox next to :guilabel:`Replenish on Order (MTO)`, and click " +"on :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:172 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting also activates " +":guilabel:`Storage Locations`. If these features aren't applicable to the " +"warehouse, disable these settings after unarchiving the |MTO| route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:176 +msgid "" +"To set a product's procurement route to |MTO|, go to " +":menuselection:`Inventory app --> Products --> Products`, and click on the " +"desired product to open its product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:179 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and in the :guilabel:`Routes` " +"section of options, select :guilabel:`Replenish on Order (MTO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:182 +msgid "" +"For products purchased directly from a vendor, make sure the :guilabel:`Buy`" +" route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a vendor is configured in the :guilabel:`Purchase` " +"tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:186 +msgid "" +"For products manufactured in-house, make sure the :guilabel:`Manufacture` " +"route is selected, in addition to the :guilabel:`Replenish on Order (MTO)` " +"route. Also, make sure a bill of materials is configured for the product, " +"which is accessible via the :guilabel:`Bill of Materials` smart button on " +"the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:192 +msgid "" +"The |MTO| route cannot be selected alone. |MTO| **only** works if the " +":guilabel:`Manufacture` or :guilabel:`Buy` route is also selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst-1 +msgid "Replenish on Order selected on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:3 +msgid "Use different units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:7 +msgid "" +"In some cases, handling products in different units of measure is necessary." +" For example, a business can buy products from a country that uses the " +"metric system, and then sell those products in a country that uses the " +"imperial system, so the business needs to convert the units. Another case " +"for unit conversion is when a business buys products in a big pack from a " +"supplier and then sells those products in individual units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:13 +msgid "Odoo can be set up to use different units of measure for one product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:18 +msgid "" +"To use different units of measure in Odoo, first go to " +":menuselection:`Inventory --> Configuration --> Settings --> Products` and " +"activate the :guilabel:`Units of Measure` setting. Then, click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "Enable Units of Measure in the Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:27 +msgid "Units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:29 +msgid "" +"After enabling the units of measure setting, view the default units of " +"measure categories in :menuselection:`Inventory --> Configuration --> Units " +"of Measures --> UoM Categories`. The category is important for unit " +"conversion, Odoo can only convert a product's units from one unit to another" +" only if both units belong to the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "Set units of measure categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:38 +msgid "" +"Each units of measure category has a reference unit. The reference unit is " +"highlighted in blue in the :guilabel:`Uom` column of the :guilabel:`Units of" +" Measure Categories` page. Odoo uses the reference unit as a base for any " +"new units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:42 +msgid "" +"To create a new unit, first select the correct category. For example, to " +"sell a product in a box of six units, click on the :guilabel:`Unit` category" +" line. Next, click :guilabel:`Edit`. After that, click :guilabel:`Add a " +"line`. Then, in the :guilabel:`Unit of Measure` field, title the new unit " +"`Box of 6`. In the :guilabel:`Type` field, select :guilabel:`Bigger than the" +" reference Unit of Measure`. In the :guilabel:`Ratio` field, enter `6.00000`" +" since a box of six is six times bigger than the reference unit (`1.00000`)." +" Finally, click :guilabel:`Save`." +msgstr "" +"หากต้องการสร้างหน่วยใหม่ ให้เลือกหมวดหมู่ที่ถูกต้องก่อน ตัวอย่างเช่น " +"หากต้องการขายผลิตภัณฑ์ในกล่องหกหน่วย ให้คลิกที่บรรทัดหมวดหมู่ " +":guilabel:`หน่วย` จากนั้นคลิก :guilabel:`แก้ไข` หลังจากนั้น คลิก " +":guilabel:`เพิ่มบรรทัด` จากนั้น ในฟิลด์ :guilabel:`หน่วยวัด` " +"ให้ตั้งชื่อหน่วยใหม่ว่า `กล่อง 6 หน่วย` ในฟิลด์ :guilabel:`ประเภท` ให้เลือก " +":guilabel:`ใหญ่กว่าหน่วยวัดอ้างอิง` ในช่อง :guilabel:`อัตรา` ให้ป้อน " +"`6.00000` เนื่องจากช่องที่มี 6 ช่องมีขนาดใหญ่กว่าหน่วยอ้างอิงถึง 6 เท่า " +"(`1.00000`) สุดท้าย คลิก :guilabel:`บันทึก`" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:49 +msgid "Click on the :guilabel:`Unit` category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:51 +msgid "" +"Click :guilabel:`Add a line`. As an example, we will create a Box of 6 units" +" that we will use for the Egg product. The box of 6 is 6 times bigger than " +"the reference unit of measure for the category which is “Units” here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst-1 +msgid "" +"Convert products from one unit to another as long as they belong to the same" +" category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:60 +msgid "Specify a product's units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:62 +msgid "" +"To set units of measure on a product, first go to :menuselection:`Inventory " +"--> Products --> Products` and click on a product to open its settings. " +"Then, click on :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:65 +msgid "" +"In the :guilabel:`General Information` tab, edit the :guilabel:`Unit of " +"Measure` field to specify the unit of measure that the product is sold in. " +"The specified unit will also be the unit used to keep track of the product's" +" inventory and internal transfers. Edit the :guilabel:`Purchase UoM` field " +"to specify the unit of measure that the product is purchased in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:71 +msgid "Unit conversion" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:74 +msgid "Buy products in the Purchase UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:76 +msgid "" +"When creating a new request for quotation (RFQ) in the Purchase app, Odoo " +"automatically uses the product's specified purchase unit of measure. " +"However, if needed, the :guilabel:`UoM` can be manually edited on the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:80 +msgid "" +"After the RFQ is confirmed into a purchase order (PO), click on the " +":guilabel:`Receipt` smart button at the top right corner of the PO. Odoo " +"automatically converts the purchase unit of measure into the product's " +"sales/inventory unit of measure, so the :guilabel:`Demand` column of the " +"delivery receipt shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:85 +msgid "" +"For example, if the product's purchase UoM is `Box of 6` and its " +"sales/inventory unit of measure is `Units`, the PO shows the quantity in " +"boxes of six, and the delivery receipt shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:90 +msgid "Replenishment" +msgstr "การเติมสินค้า" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:92 +msgid "" +"A request for quotation for a product can also be generated directly from " +"the product form using the :guilabel:`Replenish` button. After clicking " +":guilabel:`Replenish`, a replenish assistant box pops up. The purchase unit " +"of measure can be manually edited here if needed. Then, click " +":guilabel:`Confirm` to create the RFQ." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:97 +msgid "" +"Next, click the :guilabel:`Units Forecasted` smart button on the product " +"form and scroll down to :menuselection:`Forecasted Inventory --> Requests " +"for quotation`. Click on the RFQ reference number to open the draft RFQ. The" +" purchase UoM can also be edited here if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:102 +msgid "Sell in a different UoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:104 +msgid "" +"When creating a new quotation in the Sales app, Odoo automatically uses the " +"product's specified unit of measure. However, if needed, the :guilabel:`UoM`" +" can be manually edited on the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:107 +msgid "" +"After the quotation is sent to the customer and confirmed into a sales order" +" (SO), click on the :guilabel:`Delivery` smart button at the top right " +"corner of the SO. Odoo automatically converts the unit of measure into the " +"product's inventory unit of measure, so the :guilabel:`Demand` column of the" +" delivery shows the converted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:112 +msgid "" +"For example, if the product's UoM on the SO was changed to `Box of 6`, but " +"its inventory unit of measure is `Units`, the SO shows the quantity in boxes" +" of six, and the delivery shows the quantity in units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking.rst:5 +msgid "Product tracking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 +msgid "Difference between lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:5 +msgid "" +"*Lots* and *serial numbers* are the two ways to identify and track products " +"in Odoo. While there are similarities between the two traceability methods, " +"there are also notable differences that affect receipts, deliveries, and " +"inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:9 +msgid "" +"A *lot* usually indicates a specific batch of an item that was received, is " +"currently stored, or was shipped from a warehouse. However, it can also " +"pertain to a batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:13 +msgid "" +"A *serial number* is a unique identifier assigned incrementally (or " +"sequentially) to an item or product, used to distinguish it from other items" +" or products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:17 +msgid ":doc:`lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 +msgid "Enable lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:23 +msgid "" +"To track products using lots and serial numbers, the *Lots & Serial Numbers*" +" feature must be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:26 +msgid "" +"To do that, go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Traceability` section, and click " +"the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " +":guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled lots and serial numbers feature in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:35 +msgid "When to use lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:37 +msgid "" +"Lots are useful for products that are manufactured or received in large " +"quantities, such as clothes or food. Lots and can be used to trace a product" +" back to a group, which is especially useful when managing product recalls " +"or expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "Created lot with quantity of products in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 +msgid "" +"Manufacturers assign lot numbers to groups of products that have common " +"properties; this can lead to multiple goods sharing the same lot number. " +"This helps identify a number of products in a single group, and allows for " +"end-to-end traceability of these products through each step in their life " +"cycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:52 +msgid "When to use serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:54 +msgid "" +"The goal of assigning serial numbers to individual products is to make sure " +"every item's history is identifiable when it travels through the supply " +"chain. This can be especially useful for manufacturers that provide after-" +"sales services related to products they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "List of serial numbers for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:63 +msgid "" +"Serial numbers can contain many different types of characters: numbers, " +"letters, typographical symbols, or a mixture of all three types." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 +msgid "Traceability" +msgstr "การติดตามย้อนกลับ" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 +msgid "" +"Manufacturers and companies can refer to traceability reports to see the " +"entire life cycle of a product. These reports include vital information, " +"like where it came from (and when), where it was stored, and to whom it was " +"sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:73 +msgid "" +"To see the full traceability of a product, or group products by lots and/or " +"serial numbers, go to :menuselection:`Inventory app --> Products --> " +"Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` " +"dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:77 +msgid "" +"From here, products with lots or serial numbers assigned to them are listed " +"by default. They can also be expanded to show what lots or serial numbers " +"have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:80 +msgid "" +"To group by lots or serial numbers, first remove any default filters from " +"the search bar in the upper-right corner. Then, click :guilabel:`Group By`, " +"and select :guilabel:`Add Custom Group`, which reveals a mini drop-down " +"menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, " +"and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:85 +msgid "" +"Doing so reveals all existing lots and serial numbers, and each can be " +"expanded to show all product quantities with that assigned number. For " +"unique serial numbers that are *not* reused, there should *only* be one " +"product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst-1 +msgid "Reporting page with drop-down lists of lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:94 +msgid "" +"For additional information regarding an individual lot number or serial " +"number, click the line item for the lot or serial number to reveal that " +"specific number's :guilabel:`Lot` or :guilabel:`Serial Number` form. From " +"this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart" +" buttons to see all stock on-hand using that serial number. Any operations " +"made using that lot or serial number can be found here, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 +msgid "Expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:7 +msgid "" +"In Odoo, *expiration dates* can be used to manage and track the lifecycles " +"of perishable products, from purchase to sale. Using expiration dates " +"reduces product loss due to unexpected expiry, and helps to avoid sending " +"expired products to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:11 +msgid "" +"In Odoo, only products that are tracked using *lots* and *serial numbers* " +"can be assigned expiration information. Once a lot or serial number has been" +" assigned, an expiration date can be set. This is especially helpful for " +"companies (such as food manufacturers) that consistently, or exclusively, " +"buy and sell perishable products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:17 +msgid ":doc:`../product_tracking/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:18 +msgid ":doc:`../product_tracking/serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:21 +msgid "Enable expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:23 +msgid "" +"To enable the use of *expiration dates*, go to :menuselection:`Inventory app" +" --> Configuration --> Settings`, and scroll down to the " +":guilabel:`Traceability` section. Then, click the checkbox to enable the " +":guilabel:`Lots & Serial Numbers` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:27 +msgid "" +"Once that feature is activated, a new option will appear to enable " +":guilabel:`Expiration Dates`. Click that checkbox to enable the feature, and" +" be sure to :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Enabled lots and serial numbers and expiration dates settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:35 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` feature is activated, additional " +"features appear to :guilabel:`Display Lots & Serial Numbers on Delivery " +"Slips`; to :guilabel:`Display Lots & Serial Numbers on Invoices`; and to " +":guilabel:`Display Expiration Dates on Delivery Slips`. Activating these " +"features helps with end-to-end traceability, making it easier to manage " +"product recalls, identify \"bad\" batches of products, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:42 +msgid "Configure expiration dates on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:44 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` and :guilabel:`Expiration Dates` " +"features have been enabled in the settings of the *Inventory* app, " +"expiration information can be configured on individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:48 +msgid "" +"To do so, go to :menuselection:`Inventory app --> Products --> Products`, " +"and select a product to edit. Selecting a product reveals the product form " +"for that particular item. Once on the product form, click :guilabel:`Edit` " +"in the upper-left corner to make changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:53 +msgid "" +"To be tracked using lots or serial numbers, or to configure expiration " +"information, products *must* have their :guilabel:`Product Type` set as " +":guilabel:`Storable Product` under the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:57 +msgid "" +"Then, click the :guilabel:`Inventory` tab, and scroll down to the " +":guilabel:`Traceability` section. From here, make sure that either " +":guilabel:`By Unique Serial Number` or :guilabel:`By Lots` is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:61 +msgid "" +"Once it is, a new :guilabel:`Expiration Date` checkbox appears that must " +"also be clicked. When both are enabled, a new :guilabel:`Dates` field " +"appears to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:65 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed in order " +"to assign lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:70 +msgid "" +"For processing large quantities of products on receipts or deliveries, it is" +" recommended to track using lots, so multiple products can be traced back to" +" the same lot, if any issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Expiration dates configuration on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:77 +msgid "" +"Under the :guilabel:`Dates` field, there are four categories of expiration " +"information to configure for the product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:80 +msgid "" +":guilabel:`Expiration Time`: the number of days after receiving products " +"(either from a vendor or in stock after production) in which goods may " +"become dangerous and should not be used or consumed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:82 +msgid "" +":guilabel:`Best Before Time`: the number of days before the expiration date " +"in which the goods start deteriorating, **without** necessarily being " +"dangerous yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:84 +msgid "" +":guilabel:`Removal Time`: the number of days before the expiration date in " +"which the goods should be removed from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:86 +msgid "" +":guilabel:`Alert Time`: the number of days before the expiration date in " +"which an alert should be raised on goods in a particular lot or containing a" +" particular serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:90 +msgid "" +"The values entered into these fields automatically compute the expiration " +"date for goods entered into stock, whether purchased from a vendor or " +"manufactured in-house." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:93 +msgid "" +"Once all the expiration information has been configured, click " +":guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:96 +msgid "" +"If the :guilabel:`Dates` field is not populated with any values for " +"expiration information, dates (and lots) can be manually assigned upon " +"receipts and deliveries in and out of the warehouse. Even when assigned, " +"they can still be overwritten and changed manually if needed, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:101 +msgid "Set expiration dates on receipts with lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:103 +msgid "" +"Generating expiration dates for **incoming** goods can be done directly from" +" the purchase order. To create a purchase order, go to the " +":menuselection:`Purchase` app and click :guilabel:`Create` to create a new " +"request for quotation (RFQ)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:107 +msgid "" +"Then, fill out the information by adding a :guilabel:`Vendor`, and add " +"products to the :guilabel:`Product` lines by clicking :guilabel:`Add a " +"product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:110 +msgid "" +"Choose the desired quantity to order by changing the number in the " +":guilabel:`Quantity` column, and click :guilabel:`Confirm Order`. This " +"converts the :abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:114 +msgid "" +"Click the :guilabel:`Receipt` smart button at the top of the purchase order " +"to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:118 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities causes a :guilabel:`User Error` popup to appear. " +"The popup requires entry of a lot or serial number for the ordered products." +" The :abbr:`RFQ (request for quotation)` cannot be validated without an " +"assigned lot or serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:0 +msgid "User error popup when validating an order with no lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:127 +msgid "" +"From here, click the :guilabel:`Additional Options` menu (hamburger) icon " +"located on the far-right of the product line. When clicked, a " +":guilabel:`Detailed Operations` pop-up will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:130 +msgid "" +"In this pop-up, click :guilabel:`Add a line`, and assign a lot or serial " +"number under the :guilabel:`Lot/Serial Number Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:133 +msgid "" +"An expiration date automatically populates, based on the configuration on " +"the product form (if previously configured)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:137 +msgid "" +"If the :guilabel:`Dates` field on the product form has not been configured, " +"this date can be manually entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:140 +msgid "" +"After the expiration date has been established, mark the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Finally, " +"click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "" +"Detailed operations popup showing expiration dates for ordered products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:147 +msgid "" +"A :guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document; the :guilabel:`Product` being traced; the :guilabel:`Lot/Serial " +"#`; and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:153 +msgid "Set expiration dates on manufactured products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:155 +msgid "" +"Expiration dates can also be generated for products manufactured in-house. " +"To assign expiration dates to manufactured products, a manufacturing order " +"(MO) needs to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:158 +msgid "" +"To create a :abbr:`MO (manufacturing order)`, go to " +":menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, " +"and click :guilabel:`Create`. Choose a product to manufacture from the " +":guilabel:`Product` field drop-down menu, then select the " +":guilabel:`Quantity` to produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Manufacturing order for product with expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:167 +msgid "" +"To manufacture a product, there must be materials to consume in the lines in" +" the :guilabel:`Product` column. This can be achieved either by creating a " +":guilabel:`Bill of Material` for the :guilabel:`Product`, or manually adding" +" materials to consume by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:172 +msgid "Once ready, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:174 +msgid "" +"Next to :guilabel:`Lot/Serial Number`, either select an existing lot number " +"from the drop-down menu, or click the green :guilabel:`+` sign to " +"automatically assign a new lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:177 +msgid "" +"Then, select a number of units for the :guilabel:`Quantity` field, and click" +" :guilabel:`Mark as Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:180 +msgid "" +"Click on the :guilabel:`External Link` icon in the assigned " +":guilabel:`Lot/Serial Number` field. A pop-up appears, revealing a detail " +"form for that specific number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:183 +msgid "" +"On that pop-up, under the :guilabel:`Dates` tab, all expiration information " +"that was previously configured for the product is displayed. That same " +"information is also available on the detail form for that specific product, " +"or by going to :menuselection:`Inventory app --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Dates tab with expiration information for specific lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:193 +msgid "Sell products with expiration dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:195 +msgid "" +"Selling perishable products with expiration dates is done the same as any " +"other type of product. The first step in selling perishable products is to " +"create a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:198 +msgid "" +"To do that, go to :menuselection:`Sales app --> Create` to create a new " +"quotation, and fill out the information on the sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:201 +msgid "" +"Add a :guilabel:`Customer`, click :guilabel:`Add a product` to add the " +"desired products to the :guilabel:`Product` lines, and set a " +":guilabel:`Quantity` for the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:204 +msgid "" +"Then, click the :guilabel:`Other Info` tab. Under the :guilabel:`Delivery` " +"section, change the :guilabel:`Delivery Date` to a date after the expected " +"date, and click the :guilabel:`green checkmark` icon to confirm the date. " +"Finally, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:208 +msgid "" +"Next, click the :guilabel:`Delivery` smart button at the top of the sales " +"order to see the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:211 +msgid "" +"On the warehouse receipt form, click :guilabel:`Validate`, and then " +":guilabel:`Apply` in the accompanying pop-up window, to automatically " +"process all :guilabel:`Done` quantities, and deliver the products to the " +"customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:215 +msgid "" +"If the products are delivered before the :guilabel:`Alert Date` set on the " +"product form, then no alerts will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:219 +msgid "" +"To sell perishable products with expiration dates, the :guilabel:`Removal " +"Strategy` for the :guilabel:`Location` the products are stored in must be " +"set to :abbr:`FEFO (First Expiry, First Out)`. If there is not enough stock " +"of perishable products in one lot, Odoo will automatically take the " +"remaining quantity required from a second lot with the next-soonest " +"expiration date. Removal strategies can also be set on :guilabel:`Product " +"Categories`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:226 +msgid ":doc:`../../warehouses_storage/advanced_operations_warehouse/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:229 +msgid "View expiration dates for lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:231 +msgid "" +"To view (and/or group) all products with expiration dates by lot number, go " +"to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:234 +msgid "" +"Once there, remove any default search filters from the :guilabel:`Search...`" +" bar. Then, click :guilabel:`Group By`, choose :guilabel:`Add Custom Group`," +" and select the :guilabel:`Expiration Date` parameter from the drop-down " +"menu. Finally, click :guilabel:`Apply` to apply the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:238 +msgid "" +"Doing so breaks down all perishable products, their expiration dates, and " +"the assigned lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Group by expiration dates on lots and serial numbers page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:245 +msgid "Expiration alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:247 +msgid "" +"To see expiration alerts, go to :menuselection:`Inventory app --> Products " +"--> Lots/Serial Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:249 +msgid "" +"Then, click into a :guilabel:`Lot/Serial Number` with perishable products. " +"Doing so reveals the serial number detail form. On the serial number detail " +"form, click the :guilabel:`Dates` tab to see all expiration information " +"related to the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:253 +msgid "" +"To edit the form, click :guilabel:`Edit` in the upper-left corner of the " +"form, then change the :guilabel:`Expiration Date` to today's date (or " +"earlier), and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:257 +msgid "" +"After saving, the lot number form displays a red :guilabel:`Expiration " +"Alert` at the top of the form to indicate that the products in this lot are " +"either expired or expiring soon. From here, click back to the " +":guilabel:`Lots/Serial Numbers` page (via the breadcrumbs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:261 +msgid "" +"To see the new expiration alert, or any expiration alerts for products that " +"are expired (or will expire soon), remove all of the search filters from the" +" :guilabel:`Search...` bar on the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:265 +msgid "" +"Then, click :guilabel:`Filters`, and choose :guilabel:`Expiration Alerts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst-1 +msgid "Expiration alert for product past the expiration date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:3 +msgid "Use lots to manage groups of products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:5 +msgid "" +"*Lots* are one of the two ways to identify and track products in Odoo. A lot" +" usually indicates a specific batch of an item that was received, is " +"currently stored, or was shipped from a warehouse, but can also pertain to a" +" batch of products manufactured in-house, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:9 +msgid "" +"Manufacturers assign lot numbers to groups of products that have common " +"properties; this can lead to multiple goods sharing the same lot number. " +"This helps to identify a number of products in a single group, and allows " +"for end-to-end traceability of these products through each step in their " +"lifecycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:14 +msgid "" +"Lots are useful for products that are manufactured or received in large " +"quantities (such as clothes or food), and can be used to trace a product " +"back to a group. This is especially useful when managing product recalls or " +"expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 +msgid "" +"To track products using lots, the *Lots & Serial Numbers* feature must be " +"enabled. Go to the :menuselection:`Inventory app --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Traceability` section, and click " +"the box next to :guilabel:`Lots & Serial Numbers`. Then, click the " +":guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 +msgid "Track products by lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:38 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be configured to be tracked using lots. To do " +"this, go to the :menuselection:`Inventory app --> Products --> Products`, " +"and choose a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:42 +msgid "" +"Once on the product form, click :guilabel:`Edit` to make changes to the " +"form. Then, click the :guilabel:`Inventory` tab. In the " +":guilabel:`Traceability` section, click :guilabel:`By Lots`. Then, click " +":guilabel:`Save` to save changes. Existing or new lot numbers can now be " +"assigned to newly-received or manufactured batches of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:48 +msgid "" +"If a product has stock on-hand prior to activating tracking by lots or " +"serial numbers, an inventory adjustment might need to be performed to assign" +" lot numbers to the existing stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled tracking by lots feature on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:56 +msgid "Create new lots for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:58 +msgid "" +"New lots can be created for products already in stock with no assigned lot " +"number. To do this, go to the :menuselection:`Inventory app --> Products -->" +" Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a " +"separate page where a new :guilabel:`Lot/Serial Number` is generated " +"automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:64 +msgid "" +"While Odoo automatically generates a new :guilabel:`Lot/Serial Number` to " +"follow the most recent number, it can be edited and changed to any desired " +"number, by clicking the line under the :guilabel:`Lot/Serial Number` field, " +"and changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:68 +msgid "" +"Once the new :guilabel:`Lot/Serial Number` is generated, click the blank " +"field next to :guilabel:`Product` to reveal a drop-down menu. From this " +"menu, select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:72 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and assign this specific lot or serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:77 +msgid "" +"A detailed description of this specific lot or serial number can also be " +"added in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:81 +msgid "" +"When all desired configurations are complete, click the :guilabel:`Save` " +"button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "New lot number creation form with assigned product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:86 +msgid "" +"After a new lot number has been created, saved, and assigned to the desired " +"product, navigate back to the product form in the :menuselection:`Inventory`" +" app, by going to :menuselection:`Products --> Products`, and selecting the " +"product to which this newly-created lot number was just assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:90 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new lot number. When additional quantity of this " +"product is received or manufactured, this new lot number can be selected and" +" assigned to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:95 +msgid "Manage lots for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:97 +msgid "" +"Lot numbers can be assigned for both **incoming** and **outgoing** goods. " +"For incoming goods, lot numbers are assigned directly on the purchase order " +"form. For outgoing goods, lot numbers are assigned directly on the sales " +"order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:104 +msgid "Manage lots on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:106 +msgid "" +"Assigning lot numbers to **incoming** goods can be done directly from the " +"purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:108 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to :menuselection:`Purchase app " +"--> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:111 +msgid "" +"On this :abbr:`RFQ (request for quotation)`, fill out the necessary " +"information by adding a :guilabel:`Vendor`, and adding the desired products " +"to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product` " +"(under the :guilabel:`Products` tab)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:115 +msgid "" +"Choose the desired quantity of the product to order by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:118 +msgid "" +"Once the :abbr:`RFQ (request for quotation)` has been filled out, click " +":guilabel:`Confirm Order`. When the :abbr:`RFQ (request for quotation)` is " +"confirmed, it becomes a :guilabel:`Purchase Order`, and a " +":guilabel:`Receipt` smart button appears. Click the :guilabel:`Receipt` " +"smart button to be taken to the warehouse receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:124 +msgid "" +"Clicking :guilabel:`Validate` before assigning a lot number to the ordered " +"product quantities will result in a :guilabel:`User Error` pop-up. The pop-" +"up requires entry of a lot or serial number for the ordered products. The " +":abbr:`RFQ (request for quotation)` **cannot** be validated without a lot " +"number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Add lot/serial number user error popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:133 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +":guilabel:`hamburger (four horizontal lines)` icon, located to the right of " +"the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:137 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a lot number, under the :guilabel:`Lot/Serial Number Name` " +"column, located at the bottom of the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:140 +msgid "" +"There are two ways to assign lot numbers: **manually** and **copy/paste**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:142 +msgid "" +"**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the" +" location the products will be stored in under the :guilabel:`To` column. " +"Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` " +"quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "Assign lot number detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:151 +msgid "" +"If quantities should be processed in multiple locations and lots, click " +":guilabel:`Add a line` and type a new :guilabel:`Lot Number Name` for " +"additional quantities. Repeat until the :guilabel:`Quantity Done` matches " +"the :guilabel:`Demand`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:155 +msgid "" +"**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with " +"all of the lot numbers received from the supplier (or manually chosen to " +"assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial" +" Number Name` column. Odoo will automatically create the necessary number of" +" lines based on the amount of numbers pasted in the column. From here, the " +":guilabel:`To` locations and :guilabel:`Done` quantities can be manually " +"entered in each of the lot number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:0 +msgid "List of lot numbers copied on excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:165 +msgid "" +"Once all product quantities have been assigned a lot number, click " +":guilabel:`Confirm` to close the pop-up. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:168 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`" +" assigned, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:174 +msgid "Manage lots on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:176 +msgid "" +"Assigning lot numbers to **outgoing** goods can be done directly from the " +"sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:178 +msgid "" +"To create an :abbr:`SO (sales order)`, go to the :menuselection:`Sales app " +"--> Create`. Doing so reveals a new, blank quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:181 +msgid "" +"On this blank quotation form, fill out the necessary information by adding a" +" :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines " +"(in the :guilabel:`Order Lines` tab) by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:221 +msgid "" +"Then, choose the desired quantity to sell by changing the number in the " +":guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:187 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, it becomes an " +":abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 +msgid "" +"Click the :guilabel:`Delivery` smart button to view the warehouse receipt " +"form for that specific :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:230 +msgid "" +"From here, click the :guilabel:`Additional Options` menu, represented by a " +"`hamburger` icon (four horizontal lines, located to the right of the " +":guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). " +"Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:198 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with the full :guilabel:`Reserved` quantity taken from that specific lot (if" +" there is enough stock in that particular lot)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:202 +msgid "" +"If there is insufficient stock in that lot, or if partial quantities of the " +":guilabel:`Demand` should be taken from multiple lots, change the quantity " +"in the :guilabel:`Done` column to only include that specific part of the " +"total quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:207 +msgid "" +"The lot automatically chosen for delivery orders varies, depending on the " +"selected removal strategy (:abbr:`FIFO (First In, First Out)`, :abbr:`LIFO " +"(Last In, First Out)`, or :abbr:`FEFO (First Expiry, First Out)`). It will " +"also depend on the quantity ordered, and if there is enough quantity in one " +"lot to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:213 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:215 +msgid "" +"Then, click :guilabel:`Add a line`, select an additional (different) " +":guilabel:`Lot/Serial Number`, apply the rest of the :guilabel:`Done` " +"quantities, and click :guilabel:`Confirm` to close the pop-up. Lastly, click" +" the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Detailed operations popup for source lot number on sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:223 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:228 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order, if the product quantities shared " +"the same lot number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:232 +msgid "Manage lots for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:234 +msgid "" +"In Odoo, the creation of new lots is only allowed upon **receiving** " +"products from a purchase order, by default. **Existing** lot numbers cannot " +"be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:237 +msgid "" +"For sales orders, the opposite is true: new lot numbers cannot be created on" +" the delivery order, only existing lot numbers can be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:240 +msgid "" +"To change the ability to use new (or existing) lot numbers on any operation " +"type, go to the :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:244 +msgid "" +"For :guilabel:`Receipts`, found on the :menuselection:`Operations Types` " +"page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be " +"enabled, by clicking :guilabel:`Edit`, and then clicking the checkbox beside" +" the :guilabel:`Use Existing Lots/Serial Numbers` option (in the " +":guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button" +" to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:249 +msgid "" +"For :guilabel:`Delivery Orders`, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by clicking :guilabel:`Edit`, and clicking " +"the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option. " +"Be sure to click the :guilabel:`Save` button to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Enabled traceability setting on operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:258 +msgid "" +"For inter-warehouse transfers involving products tracked by lots, it can be " +"useful to enable the :guilabel:`Use Existing Lots/Serial Numbers` option for" +" warehouse receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:262 +msgid "Lots traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:264 +msgid "" +"Manufacturers and companies can refer to traceability reports to see the " +"entire lifecycle of a product: where (and when) it came from, where it was " +"stored, and who (and when) it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:267 +msgid "" +"To see the full traceability of a product, or group by lots, go to the " +":menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :menuselection:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:271 +msgid "" +"From here, products with lot numbers assigned to them will be listed by " +"default, and can be expanded to show the lot numbers those products have " +"assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:274 +msgid "" +"To group by lots (or serial numbers), begin by removing any filters in the " +"search bar. Then, click the :guilabel:`Group By` drop-down, select " +":guilabel:`Add Custom Group`, and select :guilabel:`Lot/Serial Number` from " +"the drop-down menu. Then, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:278 +msgid "" +"Doing so displays all existing lots and serial numbers, and can be expanded " +"to show all quantities of products with that assigned number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst-1 +msgid "Lots and serial numbers traceability report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:286 +msgid ":doc:`differences`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:3 +msgid "Use serial numbers to track products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:5 +msgid "" +"*Serial numbers* are one of the two ways to identify and track products in " +"Odoo. A serial number is a unique identifier assigned incrementally (or " +"sequentially) to an item or product, used to distinguish it from other items" +" and products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:9 +msgid "" +"Serial numbers can consist of many different types of characters: they can " +"be strictly numerical, they can contain letters and other typographical " +"symbols, or they can be a mix of all of the above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:12 +msgid "" +"The goal of assigning serial numbers to individual products is to make sure " +"that every item's history is identifiable when it travels through the supply" +" chain. This can be especially useful for manufacturers that provide after-" +"sales services to products that they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:17 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 +msgid "" +"To track products using serial numbers, the :guilabel:`Lots & Serial " +"Numbers` feature must be enabled. To enable this, go to " +":menuselection:`Inventory app --> Configuration --> Settings`, scroll down " +"to the :guilabel:`Traceability` section, and click the box next to " +":guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` " +"button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled lots and serial numbers setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:34 +msgid "Configure serial number tracking on products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:36 +msgid "" +"Once the :guilabel:`Lots & Serial Numbers` setting has been activated, " +"individual products can now be tracked using serial numbers. To configure " +"this, go to :menuselection:`Inventory app --> Products --> Products`, and " +"choose a desired product to track." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:40 +msgid "" +"Once on the product form, click :guilabel:`Edit`, and click the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:42 +msgid "" +"Once on the product form, click :guilabel:`Edit`, navigate to the " +":guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` " +"section. Then, select the :guilabel:`By Unique Serial Number` option, and " +"click :guilabel:`Save` to save the changes. Existing or new serial numbers " +"can now be selected and assigned to newly-received or manufactured batches " +"of this product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled serial number tracking on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:52 +msgid "" +"If a product doesn't have a serial number assigned to it, a user error pop-" +"up window will appear. The error message states that the product(s) in stock" +" have no lot/serial number. However, a lot/serial number can be assigned to " +"the product by making an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:57 +msgid "Create new serial numbers for products already in stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:59 +msgid "" +"New serial numbers can be created for products already in stock with no " +"assigned serial number. To do this, go to :menuselection:`Inventory --> " +"Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so " +"reveals a blank lots/serial numbers form. On this form, a new " +":guilabel:`Lot/Serial Number` is generated automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:65 +msgid "" +"While Odoo automatically generates a new lot/serial number to follow the " +"most recent number, it can be edited and changed to any desired number, by " +"clicking the line under the :guilabel:`Lot/Serial Number` field, and " +"changing the generated number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:69 +msgid "" +"Once the :guilabel:`Lot/Serial Number` is generated, click the blank field " +"next to :guilabel:`Product` to reveal a drop-down menu. From this menu, " +"select the product to which this new number will be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:73 +msgid "" +"This form also provides the option to adjust the :guilabel:`Quantity`, to " +"assign a unique :guilabel:`Internal Reference` number (for traceability " +"purposes), and to assign this specific lot/serial number configuration to a " +"specific website in the :guilabel:`Website` field (if working in a multi-" +"website environment)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:78 +msgid "" +"A detailed description of this specific lot/serial number can also be added " +"in the :guilabel:`Description` tab below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "New serial number created for existing product stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:87 +msgid "" +"After a new serial number has been created, assigned to the desired product," +" and saved, navigate back to the product form, by going to " +":menuselection:`Products --> Products`, and selecting the product that this " +"newly-created serial number was just assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:91 +msgid "" +"On that product's detail form, click the :guilabel:`Lot/Serial Numbers` " +"smart button to view the new serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:95 +msgid "Manage serial numbers for shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:97 +msgid "" +"Serial numbers can be assigned for both **incoming** and **outgoing** goods." +" For incoming goods, serial numbers are assigned directly on the purchase " +"order form. For outgoing goods, serial numbers are assigned directly on the " +"sales order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:102 +msgid "Manage serial numbers on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:104 +msgid "" +"Assigning serial numbers to **incoming** goods can be done directly from the" +" purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:106 +msgid "" +"To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase " +"app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:109 +msgid "" +"On this :abbr:`RFQ (request for quotation)` form, fill out the necessary " +"information, by adding a :guilabel:`Vendor`, and by adding the desired " +"products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a " +"product`, under the :guilabel:`Products` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:113 +msgid "" +"Choose the desired quantity of the product to order, by changing the number " +"in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:116 +msgid "" +"When the necessary configurations are complete, click :guilabel:`Confirm " +"Order`. This will convert the :abbr:`RFQ (request for quotation)` to a " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:119 +msgid "" +"Then, click the :guilabel:`Receipt` smart button to be taken to the " +"warehouse receipt form page for that specific :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:123 +msgid "" +"Clicking :guilabel:`Validate` before assigning a serial number to the " +"ordered product quantities will cause a :guilabel:`User Error` pop-up to " +"appear. The pop-up requires entry of a lot or serial number for the ordered " +"products. The :abbr:`RFQ (request for quotation)` **cannot** be validated " +"without a serial number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "User error popup prompting serial number entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:136 +msgid "" +"In this pop-up, configure a number of different fields, including the " +"assignation of a serial number (or serial numbers) under the " +":guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-" +"up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:140 +msgid "" +"There are three ways to do this: manually assigning serial numbers, " +"automatically assigning serial numbers, and copy/pasting serial numbers from" +" a spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:144 +msgid "Assign serial numbers manually" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:146 +msgid "" +"To assign serial numbers manually, click :guilabel:`Add a line` from the " +":guilabel:`Detailed Operations` pop-up, and first choose the location where " +"the product will be stored under the :guilabel:`To` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:150 +msgid "" +"Then, type a new :guilabel:`Serial Number Name`, and set the " +":guilabel:`Done` quantity in the appropriate columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:153 +msgid "" +"Repeat this process for the quantity of products shown in the " +":guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field " +"displays the correct (matching) number of products processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:157 +msgid "Assign serial numbers automatically" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:159 +msgid "" +"If a large quantity of products need individual serial numbers assigned to " +"them, Odoo can automatically generate and assign serial numbers to each of " +"the individual products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:162 +msgid "" +"To accomplish this, start with the :guilabel:`First SN` field in the " +":guilabel:`Detailed Operations` pop-up window, and type the first serial " +"number in the desired order to be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:165 +msgid "" +"Then, in the :guilabel:`Number of SN` field, type the total number of items " +"that need newly-generated unique serial numbers assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:168 +msgid "" +"Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate " +"with new serial numbers matching the ordered quantity of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Automatic serial number assignment in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:176 +msgid "Copy/paste serial numbers from a spreadsheet" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:178 +msgid "" +"To copy and paste serial numbers from an existing spreadsheet, first " +"populate a spreadsheet with all of the serial numbers received from the " +"supplier (or manually chosen upon receipt). Then, copy and paste them in the" +" :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create " +"the necessary number of lines based on the amount of numbers pasted in the " +"column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:183 +msgid "" +"From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can " +"be manually entered in each of the serial number lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "List of serial numbers copied in Excel spreadsheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:191 +msgid "" +"For purchase orders that include large quantities of products to receive, " +"the best method of serial number assignment is to automatically assign " +"serial numbers using the :guilabel:`Assign Serial Numbers` button located on" +" the :abbr:`PO (purchase order)`. This prevents any serial numbers from " +"being reused or duplicated, and improves traceability reporting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:196 +msgid "" +"Once all product quantities have been assigned a serial number, click the " +":guilabel:`Confirm` button to close the pop-up. Then, click " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:199 +msgid "" +"A :guilabel:`Traceability` smart button appears upon validating the receipt." +" Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 +msgid "" +"Once all product quantities have been assigned a serial number, click " +":guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A " +":guilabel:`Traceability` smart button will appear upon validating the " +"receipt. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial " +"#`, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:211 +msgid "Manage serial numbers on delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:213 +msgid "" +"Assigning serial numbers to **outgoing** goods can be done directly from the" +" sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:215 +msgid "" +"To create an :abbr:`SO (sales order)`, navigate to the " +":menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing " +"so reveals a new, blank quotation form. On this blank quotation form, fill " +"out the necessary information, by adding a :guilabel:`Customer`, and adding " +"products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` " +"tab), by clicking :guilabel:`Add a product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:223 +msgid "" +"Once the quotation has been filled out, click the :guilabel:`Confirm` button" +" to confirm the quotation. When the quotation is confirmed, the quotation " +"becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button" +" appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:234 +msgid "" +"In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, " +"with each product of the total :guilabel:`Reserved` quantity listed with " +"their unique serial numbers (most likely listed in sequential order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:238 +msgid "" +"To manually change a product's serial number, click the drop-down menu under" +" :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial " +"number. Then, mark the :guilabel:`Done` quantities, and click " +":guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:242 +msgid "" +"Finally, click the :guilabel:`Validate` button to deliver the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Serial numbers listed in detailed operations popup." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:248 +msgid "" +"Upon validating the delivery order, a :guilabel:`Traceability` smart button " +"appears. Click the :guilabel:`Traceability` smart button to see the updated " +":guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` " +"document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and " +"the :guilabel:`Lot/Serial #` assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:253 +msgid "" +"The :guilabel:`Traceability Report` can also include a :guilabel:`Reference`" +" receipt from the previous purchase order (PO), if any of the product " +"quantities shared a serial number assigned during receipt of that specific " +":abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:258 +msgid "Manage serial numbers for different operations types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:260 +msgid "" +"By default in Odoo, the creation of new serial numbers is only allowed upon " +"**receiving** products from a purchase order. **Existing** serial numbers " +"cannot be used. For sales orders, the opposite is true: new serial numbers " +"cannot be created on the delivery order, only existing serial numbers can be" +" used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:265 +msgid "" +"To change the ability to use new (or existing) serial numbers on any " +"operation type, go to :menuselection:`Inventory app --> Configuration --> " +"Operations Types`, and select the desired :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:269 +msgid "" +"For the :guilabel:`Receipts` operation type, found on the " +":guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the " +":guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then " +"clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial " +"Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the" +" :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:275 +msgid "" +"For the :guilabel:`Delivery Orders` operation type, located on the " +":guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial " +"Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` " +"from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and " +"clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` " +"option (in the :guilabel:`Traceability` section). Be sure to click " +":guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Enabled traceability setting in operations type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:286 +msgid "Serial number traceability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:288 +msgid "" +"Manufacturers and companies can refer to the traceability reports to see the" +" entire lifecycle of a product: where it came from (and when), where it was " +"stored, and who it went to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:291 +msgid "" +"To see the full traceability of a product, or group by serial numbers, go to" +" :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing " +"so reveals the :guilabel:`Lots/Serial Numbers` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:295 +msgid "" +"From here, products with serial numbers assigned to them will be listed by " +"default, and can be expanded to show what serial numbers have been " +"specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:298 +msgid "" +"To group by serial numbers (or lots), first remove any default filters from " +"the search bar in the upper-right corner. Then, click :guilabel:`Group By`, " +"and select :guilabel:`Add Custom Group`, which reveals a mini drop-down " +"menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, " +"and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:303 +msgid "" +"Doing so reveals all existing serial numbers and lots, and can be expanded " +"to show all quantities of products with that assigned number. For unique " +"serial numbers that are not reused, there should be just one product per " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst-1 +msgid "Serial numbers reporting page with drop-down lists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:312 +msgid "" +"For additional information regarding an individual serial number (or lot " +"number), click the line item for the serial number to reveal that specific " +"serial number's :guilabel:`Serial Number` form. From this form, click the " +":guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all " +"stock on-hand using that serial number, and any operations made using that " +"serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 +msgid "Shipping and receiving" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse.rst:5 +msgid "Advanced operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:3 +msgid "How to cancel a shipping request to a shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo will be linked with the transportation company tracking system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:12 +msgid "" +"It will allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:15 +msgid "You can easily cancel the request made to the carrier system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:18 +msgid "How to cancel a shipping request?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:20 +msgid "" +"If the delivery order is not **Validated**, then the request hasn't been " +"made. You can choose to cancel the delivery or to change the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:24 +msgid "" +"If you have clicked on **Validate**, the request has been made and you " +"should have received the tracking number and the label. You can still cancel" +" the request. Simply click on the **Cancel** button next to the **Carrier " +"Tracking Ref**:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:32 +msgid "You will now see that the shipment has been cancelled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:37 +msgid "You can now change the carrier if you wish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:40 +msgid "How to send a shipping request after cancelling one?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:42 +msgid "" +"After cancelling the shipping request, you can change the carrier you want " +"to use. Confirm it by clicking on the **Send to shipper** button. You will " +"get a new tracking number and a new label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:115 +msgid ":doc:`invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:116 +msgid ":doc:`multipack`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:3 +msgid "Use dropshipping to ship directly from suppliers to customers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:5 +msgid "" +"Dropshipping is an order fulfillment strategy that allows sellers to have " +"items shipped directly from suppliers to customers. Normally, a seller " +"purchases a product from a supplier, stores it in their inventory, and ships" +" it to the end customer once an order is placed. With dropshipping, the " +"supplier is responsible for storing and shipping the item. This benefits the" +" seller by reducing inventory costs, including the price of operating " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:12 +msgid "Configure products to be dropshipped" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:14 +msgid "" +"To use dropshipping as a fulfillment strategy, navigate to the " +":menuselection:`Purchase` app and select :menuselection:`Configuration --> " +"Settings`. Under the :guilabel:`Logistics` heading, click the " +":guilabel:`Dropshipping` checkbox, and :guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:18 +msgid "" +"Next, go to the :menuselection:`Sales` app, click :menuselection:`Products " +"--> Products` and choose an existing product or select :guilabel:`Create` to" +" configure a new one. On the :guilabel:`Product` page, make sure that the " +":guilabel:`Can be Sold` and :guilabel:`Can be Purchased` checkboxes are " +"enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"Enable the \"Can be Sold\" and \"Can be Purchased\" checkboxes on the " +"product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:27 +msgid "" +"Click on the :guilabel:`Purchase` tab and specify a vendor and the price " +"that they sell the product for. Multiple vendors can be added, but the " +"vendor at the top of the list will be the one automatically selected for " +"purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "The product form with a vendor specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:35 +msgid "" +"Finally, select the :guilabel:`Inventory` tab and enable the " +":guilabel:`Dropship` checkbox in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "Enable the Dropship option in the product inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:43 +msgid "Fulfill orders using dropshipping" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:45 +msgid "" +"When a customer completes an online purchase for a dropshipped product, a " +"sales order will be automatically created with an associated request for " +"quotation (:abbr:`RFQ (Request for Quotation)`) for the supplier. Sales " +"orders can be viewed in the :menuselection:`Sales` app by selecting " +":menuselection:`Orders --> Orders`. Click the :guilabel:`Purchase` smart " +"button at the top right of a sales order to view the associated :abbr:`RFQ " +"(Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:52 +msgid "" +"Dropship sales orders can also be created manually through the " +":menuselection:`Sales` app by selecting :menuselection:`Orders --> Orders " +"--> Create` and adding a product configured for dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"A dropship sales order with the Purchase smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:60 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` is confirmed, it becomes a " +"purchase order and a dropship receipt is created and linked to it. The " +"receipt can be viewed by clicking the :guilabel:`Receipt` smart button in " +"the top right corner of the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"A dropship purchase order with the Receipt smart button in the top right " +"corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:68 +msgid "" +"The dropship receipt will list the supplier in the :guilabel:`Receive From` " +"section and the customer in the :guilabel:`Destination Location` section. " +"Upon delivery of the product to the customer, click on the " +":guilabel:`Validate` button at the top left of the dropship receipt to " +"confirm the delivered quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "Validate the dropship receipt after delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst:77 +msgid "" +"To view all dropship orders, simply navigate to the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard and click the teal" +" :guilabel:`# TO PROCESS` button on the :guilabel:`Dropship` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/dropshipping.rst-1 +msgid "" +"Click the green button on the Dropship card to view all dropship orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:3 +msgid "How to invoice the shipping cost to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 +msgid "There are two ways to invoice the shipping costs:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:12 +msgid "Agree with the customer over a cost and seal it down in the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:15 +msgid "Invoice the real cost of the shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:20 +msgid "" +"To configure the price of your delivery methods, go to the **Inventory** " +"app, click on :menuselection:`Configuration --> Delivery --> Delivery " +"Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:23 +msgid "" +"You can manually set a price for the shipping: It can be fixed or based on " +"rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:26 +msgid "" +"Or you can use the transportation company computation system by " +":doc:`integrating a third-party shipper " +"<../setup_configuration/third_party_shipper>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 +msgid "How to invoice the shipping costs to the customer?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:33 +msgid "Invoice the price set on the sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 +msgid "" +"On your sale order, choose the carrier that will be used. Click on " +"**Delivery Method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 +msgid "" +"The price is computed when you **save** the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:44 +msgid "" +"To invoice the price of the delivery charge on the sale order, click on " +"**Set price**, it will add a line with the name of the delivery method as a " +"product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 +msgid "" +"When you create the invoice, it will take the price set on the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:55 +msgid "Invoice the real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:63 +msgid "" +"The price is computed when you **save** the sale order. Confirm the sale " +"order and proceed to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:66 +msgid "" +"The real shipping cost is computed when the delivery order is validated, you" +" can see the real cost in the chatter of the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:72 +msgid "" +"Go back to the sale order, the real cost is now added to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:78 +msgid "" +"When you create the invoice, it will take the price computed by the carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 +msgid "" +"If you split the delivery and make several ones, each delivery order will " +"add a line to the sale order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:89 +msgid ":doc:`../setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:90 +msgid ":doc:`labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:3 +msgid "Change shipping label size" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:8 +msgid "" +"In Odoo, there are a variety of different types of shipping labels that can " +"be selected for delivery orders. Depending on the types of shipping packages" +" used, different label sizes may be more appropriate, and can be configured " +"to fit the package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:15 +msgid "" +"In the :menuselection:`Inventory` module, go to " +":menuselection:`Configuration --> Delivery --> Shipping Methods.` Click on a" +" delivery method to choose it. For the following example, *FedEx " +"International* will be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Different shipping methods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:23 +msgid "" +"In the :guilabel:`Configuration` tab, under :guilabel:`Label Type`, choose " +"one of the label types available. The availability varies depending on the " +"carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Select a label type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:30 +msgid "" +"When a sales order with the corresponding shipping company is confirmed and " +"a delivery order is validated, the shipping label will be automatically " +"created as a PDF and appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 +msgid "Create a sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:37 +msgid "" +"In the :menuselection:`Sales` application, click :guilabel:`Create` and " +"select an international customer. Click :guilabel:`Add A Product` and select" +" an item. Click :guilabel:`Add Shipping`, select a shipping method, then " +"click :guilabel:`Get Rate`, and finally, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Add a shipping method and rate to a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:45 +msgid "" +"Once the quotation is confirmed by clicking :guilabel:`Confirm`, a " +":guilabel:`Delivery` smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Delivery order smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:52 +msgid "" +"Once the delivery order is validated by clicking :guilabel:`Validate` in the" +" delivery order, the shipping documents appear in the :guilabel:`Chatter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Shipping PDF documents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:60 +msgid "Example labels" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:62 +msgid "" +"The default :guilabel:`Label Type` is :guilabel:`Paper Letter`. An example " +"of a FedEx letter sized label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Full page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:69 +msgid "For comparison, an example of a FedEx bottom-half label is:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst-1 +msgid "Half page letter size FedEx shipping label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 +msgid "How to print shipping labels?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 +msgid "" +"Odoo can handle various delivery methods, including third party shippers " +"linked with the transportation company tracking system. It allows you to " +"manage the transport company, the real prices and the destination. And " +"finally, you will be able to print the shipping labels directly from Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 +msgid "Install the shipper company connector module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:20 +msgid "" +"In the **Inventory** module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:28 +msgid "Then click on **Apply**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:35 +msgid "Configure the delivery method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:37 +msgid "" +"To configure your delivery methods, go to the **Inventory** module, click on" +" :menuselection:`Configuration --> Delivery Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:41 +msgid "" +"In the **Pricing** tab, the name of the provider means that the delivery " +"will be handled and computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:44 +msgid "The configuration of the shipper is split into two columns :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:46 +msgid "" +"The first one is linked to **your account** (develop key, password,...). For" +" more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 +msgid "" +"The second column varies according to the **provider**. You can choose the " +"packaging type, the service type, the weight unit..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:67 +msgid "Uncheck **Test Mode** when you are done with the testings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:79 +msgid "Company configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:81 +msgid "" +"In order to compute the right price, the provider needs your company " +"information. Be sure your address and phone number are correctly encoded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:64 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:88 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:94 +msgid "" +"The shipper companies need the weight of your product, otherwise the price " +"computation cannot be done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:73 +msgid "" +"Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open " +"the products you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:80 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to do" +" the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:87 +msgid "" +"The delivery order created from the sale order will take the shipping " +"information from it, but you can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:137 +msgid "" +"If you create a delivery transfer from the inventory module, you can add the" +" third party shipper in the additional info tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:96 +msgid "" +"Click on **Validate** to receive the tracking number and **the label(s)**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:153 +msgid "" +"The label to stick on your package is available in the history underneath :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:104 +msgid "Click on it to open the document and print it :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:110 +msgid "" +"If you are doing multi-packages shippings, most of the time, there will be " +"one label per package. Each label will appear in the delivery history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 +msgid "Multi-package shipments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:5 +msgid "" +"In some cases, a delivery order with multiple items may need to be shipped " +"in more than one package. This may be necessary if the items are too large " +"to ship in a single package, or if certain items cannot be packaged " +"together. Shipping a single delivery order in multiple packages provides " +"flexibility for how each item is packaged, without the need to create " +"multiple delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:13 +msgid "" +"In order to split a delivery order across multiple packages, the *Packages* " +"setting must be enabled. To do so, navigate to :menuselection:`Inventory -->" +" Configuration --> Settings`, then enable the checkbox next to " +":guilabel:`Packages`. Click :guilabel:`Save` to confirm the change." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Packages setting on the Inventory app settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:24 +msgid "Ship items in multiple packages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:26 +msgid "" +"To split items in the same delivery order across multiple packages, begin by" +" navigating to :menuselection:`Inventory --> Delivery Orders`, then select a" +" delivery order that has multiple items, a multiple quantity of the same " +"item, or both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:30 +msgid "" +"On the :guilabel:`Operations` tab, select the :guilabel:`⁞≣ (menu)` icon in " +"the line of the product that will be shipped in the first package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The menu icon for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:37 +msgid "" +"This makes a :guilabel:`Detailed Operations` pop-up window appear. In the " +"table at the bottom of the pop-up window, the :guilabel:`Reserved` column " +"shows the total quantity of the product included in the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:41 +msgid "" +"If the full quantity will be shipped in the first package, enter the number " +"from the :guilabel:`Done` column in the :guilabel:`Reserved` column. If less" +" than the full quantity will be shipped in the first package, enter a " +"smaller number than the one that appears in the :guilabel:`Reserved` column." +" Click :guilabel:`Confirm` to confirm the :guilabel:`Done` quantities and " +"close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Detailed Operations pop-up for a product in a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:51 +msgid "" +"Repeat the same steps for every item quantity that is included in the first " +"package. Then, click :guilabel:`Put In Pack` to create a package with all of" +" the selected items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Put In Pack button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:58 +msgid "" +"For the next package, follow the same steps as detailed above, marking the " +"quantity of each item to be included in the package as :guilabel:`Done` " +"before clicking :guilabel:`Put In Pack` on the delivery order. Continue " +"doing so until the full quantity of all items are added to a package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:62 +msgid "" +"Finally, after all of the packages have been shipped, click " +":guilabel:`Validate` to confirm that the delivery order has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:66 +msgid "" +"After one or more packages are created, a :guilabel:`Packages` smart button " +"appears in the top-right corner of the delivery order. Click the " +":guilabel:`Packages` smart button to go to the :guilabel:`Packages` page for" +" the delivery order, where each package can be selected to view all of the " +"items included in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:0 +msgid "The Packages smart button on a delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:76 +msgid "Create a backorder for items to be shipped later" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:78 +msgid "" +"If some items will be shipped at a later date than others, there is no need " +"to put them in a package until they are ready to be shipped. Instead, create" +" a backorder for the items being shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:81 +msgid "" +"Begin by shipping the items that will be shipped immediately. If they will " +"be shipped in multiple packages, follow the :ref:`steps above " +"<inventory/shipping/multiple-packages>` to package them as required. If they" +" will be shipped in a single package, simply mark in the :guilabel:`Done` " +"column the quantity of each item being shipped, but **do not** click the " +":guilabel:`Put In Pack` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:86 +msgid "" +"After all quantities being shipped immediately are marked as " +":guilabel:`Done`, click the :guilabel:`Validate` button, and a " +":guilabel:`Create Backorder?` pop-up window appears. Then, click the " +":guilabel:`Create Backorder` button. Doing so confirms the items being " +"shipped immediately and creates a new delivery order for the items that will" +" be shipped later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Create Backorder? pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:95 +msgid "" +"The backorder delivery order will be listed in the chatter of the original " +"delivery order in a message that reads :guilabel:`The backorder WH/OUT/XXXXX" +" has been created.`. Click on :guilabel:`WH/OUT/XXXXX` in the message to " +"view the backorder delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "" +"The backorder delivery order listed in the chatter of the original delivery " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:103 +msgid "" +"The backorder delivery order can also be accessed by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# Back Orders` button on" +" the :guilabel:`Delivery Orders` card, and selecting the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst-1 +msgid "The Back Orders button on the Delivery Orders card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:111 +msgid "" +"Once the remaining items are ready to be shipped, navigate to the backorder " +"delivery order. The items can be shipped in a single package by clicking " +":guilabel:`Validate` and selecting :guilabel:`Apply` on the " +":guilabel:`Immediate Transfer?` pop-up window that appears, or shipped in " +"multiple packages by following the steps detailed in the section above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:116 +msgid "" +"It is also possible to ship out some of the items while creating another " +"backorder for the rest. To do so, simply follow the same steps used to " +"create the first backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:3 +msgid "Scheduled delivery dates" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:5 +msgid "" +"Accurately forecasting delivery dates is vital for fulfilling customer " +"expectations. In Odoo, the *Inventory* app allows for comprehensive lead " +"time configuration, allowing coordination and planning of manufacturing " +"orders, deliveries, and receptions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:10 +msgid "Lead time types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:12 +msgid "" +"Different lead times for different operations can impact various stages of " +"the order fulfillment process. Here's a summary of the types of lead times " +"in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "Show graphic of all lead times working together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:19 +msgid "" +":ref:`Customer lead time <inventory/management/customer-lt>`: The default " +"time frame for fulfilling customer orders. The customer lead time is the " +"number of days from the date the sales order (SO) is confirmed to the date " +"the products are shipped from the warehouse. This is also known as *delivery" +" lead time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:24 +msgid "" +":ref:`Sales security lead time <inventory/management/sales-security-lt>`: " +"moves the *scheduled delivery date* forward by a specified number of days. " +"This serves as a buffer to allow the team ample time to prepare the outgoing" +" shipment earlier, considering the possibility of delays in the fulfillment " +"process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:29 +msgid "" +":ref:`Purchase lead time <inventory/management/purchase-lt>`: the number of " +"days from the confirmation of a purchase order (PO) to the receipt of " +"products. It provides insight on the time it takes for products to arrive at" +" the warehouse, facilitating effective scheduling and planning of supplier " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:34 +msgid "" +":ref:`Purchase security lead time <inventory/management/purchase-security-" +"lt>`: advances the order deadline on a :abbr:`PO (Purchase Order)` by a " +"specified number of days. This proactive approach of placing orders earlier " +"mitigates the risk of vendor or shipping delays. Thus, for products that are" +" set to replenish to order, the need appears on the *Replenishment report* " +"earlier, according to the specified number of days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:40 +msgid "" +":ref:`Manufacturing lead time <inventory/management/manuf-lt>`: the number " +"of days needed to complete a manufacturing order (MO) from the date of " +"confirmation. This lead time includes weekends (non-working hours in Odoo), " +"and is used to forecast an approximate production date for a finished good." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:45 +msgid "" +":ref:`Manufacturing security lead time <inventory/management/manuf-security-" +"lt>`: moves the scheduled date of the :abbr:`MO (Manufacturing Order)` " +"forward by a specified number of days. When used in conjunction with " +":ref:`replenish to order <inventory/management/products/strategies>`, the " +"security lead time makes the need appear earlier on the replenishment " +"report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:53 +msgid "Sales lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:55 +msgid "" +"Customer lead times and sales security lead times can be configured to " +"automatically compute an *expected delivery date* on a :abbr:`SO (Sales " +"Order)`. The expected delivery date ensures a realistic *delivery dates* " +"setting for shipments from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:59 +msgid "" +"Odoo issues a warning message if the set delivery date is earlier than the " +"expected date, as it may not be feasible to fulfill the order by that time, " +"which would impact other warehouse operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:63 +msgid "" +"A :abbr:`SO (Sales Order)` containing a `Coconut-scented candle` is " +"confirmed on July 11th. The product has a customer lead time of 14 days, and" +" the business uses a sales security lead time of 1 day. Based on the lead " +"time inputs, Odoo suggests a delivery date in 15 days, on July 26th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Set *Delivery Date* in a sales order. Enables delivery lead times feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:71 +msgid "" +"The following sections demonstrate how to automatically compute expected " +"delivery dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:74 +msgid "Customer lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:76 +msgid "" +"Set the customer lead time on each product form, by navigating to the " +"products page. To do so, go to :menuselection:`Sales app --> Products --> " +"Products`. From there, select the desired product, and switch to the " +":guilabel:`Inventory` tab. Then, under the :guilabel:`Customer Lead Time` " +"field, fill in the number of calendar days required to fulfill the delivery " +"order from start to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:82 +msgid "" +"Set a 14-day customer lead time for the `Coconut-scented candle` by " +"navigating to its product form. Then, in the :guilabel:`Inventory` tab, type" +" `14.00` days into the :guilabel:`Customer Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Set *Customer Lead Time* on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:93 +msgid "Sales security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:95 +msgid "" +"*Sales security lead time* is set globally for the business in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:98 +msgid "" +"On the configuration page, under the :guilabel:`Advanced Scheduling` " +"heading, locate the box for :guilabel:`Security Lead Time for Sales`, and " +"click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:101 +msgid "" +"Next, enter the desired number of calendar days. This security lead time is " +"a buffer notifying the team to prepare for outgoing shipments earlier than " +"the scheduled date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:105 +msgid "" +"Setting the :guilabel:`Security Lead Time for Sales` to `1.00` day, pushes " +"the :guilabel:`Scheduled Date` of a delivery order (DO) forward by one day. " +"In that case, if a product is initially scheduled for delivery on April 6th," +" but with a one-day security lead time, the new scheduled date for the " +"delivery order would be April 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"View of the security lead time for sales configuration from the sales " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:115 +msgid "Deliver several products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:117 +msgid "" +"For orders that include multiple products with different lead times, the " +"lead times can be configured directly from the quotation itself. On a " +"quotation, click the :guilabel:`Other Info` tab, and set the " +":guilabel:`Shipping Policy` to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:121 +msgid "" +":guilabel:`As soon as possible` to deliver products as soon as they are " +"ready. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` is " +"determined by adding today's date to the shortest lead time among the " +"products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:125 +msgid "" +":guilabel:`When all products are ready` to wait to fulfill the entire order " +"at once. The :guilabel:`Scheduled Date` of the :abbr:`DO (Delivery Order)` " +"is determined by adding today's date to the longest lead time among the " +"products in the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "Show *Shipping Policy* field in the *Other Info* tab of a quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:134 +msgid "" +"In a quotation containing 2 products, `Yoga mat` and `Resistance band,` the " +"products have a lead time of 8 days and 5 days, respectively. Today's date " +"is April 2nd." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:137 +msgid "" +"When the :guilabel:`Shipping Policy` is set to :guilabel:`As soon as " +"possible`, the scheduled delivery date is 5 days from today: April 7th. On " +"the other hand, selecting :guilabel:`When all products are ready` configures" +" the scheduled date to be 8 days from today: April 10th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:144 +msgid "Purchase lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:146 +msgid "" +"Automatically determining the dates on which to place orders from suppliers " +"can help simplify the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:149 +msgid "" +"Odoo calculates the supplier shipment *receipt date*, and :abbr:`PO " +"(Purchase Order)` deadline, based on the required date the product is needed" +" in the warehouse. By working backwards from the receipt date, vendor lead " +"times and purchase security lead times are taken into account, in order to " +"determine the :abbr:`PO (Purchase Order)` deadline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:154 +msgid "" +"This deadline is the date by which the order should be confirmed, in order " +"to ensure timely arrival by the expected receipt date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Visualization of PO deadline and receipt date used with vendor lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:162 +msgid "" +":ref:`PO scheduling with reordering rules " +"<inventory/management/reordering_rules>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:165 +msgid "Vendor lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:167 +msgid "" +"To set a vendor lead time for orders arriving in the warehouse from a vendor" +" location, begin by navigating to a product form through " +":menuselection:`Purchase app --> Products --> Products`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:170 +msgid "" +"Next, select the desired product, and switch to the :guilabel:`Purchase` " +"tab. In the editable vendor pricelist, click the :guilabel:`Add a line` " +"button to add vendor details, such as the :guilabel:`Vendor` name, " +":guilabel:`Price` offered for the product, and lastly, the " +":guilabel:`Delivery Lead Time`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:176 +msgid "" +"Multiple vendors and lead times can be added to the vendor pricelist. The " +"default vendor and lead time selected will be the entry at the top of the " +"list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:180 +msgid "" +"On the vendor pricelist of the product form, the :guilabel:`Delivery Lead " +"Time` for the selected vendor is set to `10 days.`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Add delivery lead times to vendor pricelist on a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:187 +msgid "" +"By setting the vendor lead time, the expected arrival date of the item is " +"automatically determined as the date of the :abbr:`PO (Purchase Order)` " +"confirmation, plus the vendor lead time. This ensures that warehouse " +"employees are notified, if the products do **not** arrive within the " +"expected timeframe." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:193 +msgid "" +"On a :abbr:`PO (Purchase Order)` confirmed on July 11th, for a product " +"configured with a 10-day vendor lead time, Odoo automatically sets the " +":guilabel:`Receipt Date` to July 21st. The receipt date also appears as the " +":guilabel:`Scheduled Date` on the warehouse receipt form, accessible from " +"the :guilabel:`Receipt` smart button, located on the :guilabel:`PO (Purchase" +" Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "Show expected *Receipt Date* of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Show expected *Scheduled Date* of arrival of the product from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:209 +msgid "Purchase security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:211 +msgid "" +"*Purchase security lead time* is set globally for the business in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:214 +msgid "" +"On the configuration page, under the :guilabel:`Advanced Scheduling` " +"heading, locate the box for :guilabel:`Security Lead Time for Purchase`, and" +" click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:217 +msgid "" +"Next, enter the desired number of calendar days. By configuring the security" +" lead time, a buffer is set to account for potential delays in supplier " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:221 +msgid "" +"Setting the :guilabel:`Security Lead Time for Purchase` to `2.00` days, " +"pushes the :guilabel:`Scheduled Date` of receipt back by one day. In that " +"case, if a product is initially scheduled to arrive on April 6th, with a " +"two-day security lead time, the new scheduled date for the receipt would be " +"April 8th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"Set security lead time for purchase from the Inventory > Configuration > " +"Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:233 +msgid "Manufacturing lead times" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:235 +msgid "" +"Lead times can help simplify the procurement process for consumable " +"materials and components used in manufactured products with bills of " +"materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:238 +msgid "" +"The :abbr:`MO (Manufacturing Order)` deadline, which is the deadline to " +"begin the manufacturing process to complete the product by the scheduled " +"delivery date, can be determined by configuring the manufacturing lead times" +" and manufacturing security lead times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Visualization of the determination of planned MO date manufacturing lead " +"times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:247 +msgid "Manufacturing lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:249 +msgid "" +"Configure the manufacturing lead time directly on the product form, by " +"navigating to :menuselection:`Manufacturing app --> Products --> Products`, " +"and select the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:252 +msgid "" +"In the :guilabel:`Inventory` tab of the product, specify the calendar days " +"needed to the manufacture the product in the :guilabel:`Manufacturing Lead " +"Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:256 +msgid "" +"Specify a 14-day :guilabel:`Manufacturing Lead Time` for a product directly " +"in the :guilabel:`Inventory` tab of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:0 +msgid "" +"View of the manufacturing lead time configuration from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:263 +msgid "" +"Establish a :abbr:`MO (Manufacturing Order)` deadline, based on the " +"*expected delivery date*, indicated in the :guilabel:`Scheduled Date` field " +"of the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:266 +msgid "" +"The :abbr:`MO (Manufacturing Order)` deadline, which is the " +":guilabel:`Scheduled Date` field on the :abbr:`MO (Manufacturing Order)`, is" +" calculated as the *expected delivery date* subtracted by the manufacturing " +"lead time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:270 +msgid "" +"This ensures the manufacturing process begins on time, in order to meet the " +"delivery date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:272 +msgid "" +"However, it's important to note that lead times are based on calendar days. " +"Lead times do **not** consider weekends, holidays, or *work center capacity*" +" (:dfn:`the number of operations that can be performed at the work center " +"simultaneously`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:277 +msgid ":ref:`Manufacturing planning <manufacturing/management/use_mps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:278 +msgid "" +":ref:`Configure automatic MO scheduling with reordering rules " +"<inventory/management/reordering_rules>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:282 +msgid "" +"A product's scheduled shipment date on the :abbr:`DO (Delivery Order)` is " +"August 15th. The product requires 14 days to manufacture. So, the latest " +"date to start the :abbr:`MO (Manufacturing Order)` to meet the commitment " +"date is August 1st." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:289 +msgid "Manufacturing security lead time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:291 +msgid "" +"*Manufacturing security lead time* is set globally for the business in " +":menuselection:`Manufacturing app --> Configuration --> Settings`. Under the" +" :guilabel:`Planning` heading, locate the box for :guilabel:`Security Lead " +"Time`, and click the checkbox to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:295 +msgid "" +"Next, enter the desired number of calendar days. By configuring the security" +" lead time, a buffer is set to account for potential delays in the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"View of the security lead time for manufacturing from the manufacturing app " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:303 +msgid "" +"A product has a scheduled shipment date on the :abbr:`DO (Delivery Order)` " +"set for August 15th. The manufacturing lead time is 7 days, and " +"manufacturing security lead time is 3 days. So, the :guilabel:`Scheduled " +"Date` on the :abbr:`MO (Manufacturing Order)` reflects the latest date to " +"begin the manufacturing order. In this example, the planned date on the " +":abbr:`MO (Manufacturing Order)` is August 5th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:310 +msgid "Global example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:312 +msgid "" +"See the following example to understand how all the lead times work together" +" to ensure timely order fulfillment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:315 +msgid "**Sales security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:316 +msgid "**Manufacturing security lead time**: 2 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:317 +msgid "**Manufacturing lead time**: 3 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:318 +msgid "**Purchase security lead time**: 1 day" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:319 +msgid "**Vendor lead time**: 4 days" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:321 +msgid "" +"The customer places an order for a manufactured product on September 1st, " +"and the scheduled delivery date from the warehouse is on September 20th. " +"Odoo uses lead times and automated reordering rules to schedule the " +"necessary operations, based on the outgoing shipment delivery date, " +"September 20th:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst-1 +msgid "" +"Show timeline of how lead times work together to schedule warehouse " +"operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:329 +msgid "**September 1st**: Sales order created, confirmed by salesperson." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:331 +msgid "" +"**September 9th**: Deadline to order components to ensure they arrive in " +"time when manufacturing begins (4-day supplier lead time)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:334 +msgid "" +"**September 13th**: Scheduled date of receipt for components. Initially, it " +"was set to 9/14, but the 1-day purchase security lead time pushed the date " +"earlier by 1 day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:337 +msgid "" +"**September 14th**: Deadline to begin manufacturing. Calculated by " +"subtracting the manufacturing lead time of 3 days, and the manufacturing " +"security lead time of 2 days, from the expected delivery date of September " +"19th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:341 +msgid "" +"**September 19th**: :guilabel:`Scheduled Date` on the delivery order form " +"indicates the updated expected delivery date, which was originally set as " +"September 20th. But the sales security lead time pushed the date forward by " +"a day." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/scheduled_dates.rst:345 +msgid "" +"Odoo's replenishment planning maps a business' order fulfillment process, " +"setting pre-determined deadlines and raw material order dates, including " +"buffer days for potential delays. This ensures products are delivered on " +"time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:3 +msgid "Process deliveries in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:7 +msgid "" +"Some companies process large amounts of deliveries every day, many of which " +"include multiple products or require special packaging. To make this " +"efficient, a packing step is needed before shipping out products. For this, " +"Odoo has a three step process for delivering goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:11 +msgid "" +"In the default three-step delivery process, products that are part of a " +"delivery order are picked in the warehouse according to their removal " +"strategy, and brought to a packing zone. After the items have been packed " +"into the different shipments in the packing zone, they are brought to an " +"output location before being shipped. These steps can be modified if they do" +" not fit the needs of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:20 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" <inventory/receipts_delivery_one_step>`, so the settings need to be changed" +" in order to utilize three step deliveries. First, make sure the *Multi-Step" +" Routes* option is enabled in :menuselection:`Inventory --> Configuration " +"--> Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step " +"Routes` will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:30 +msgid "" +"Next, the warehouse needs to be configured for three step deliveries. To do " +"this, go to :menuselection:`Inventory app --> Configuration --> Warehouses`," +" and click on the :guilabel:`warehouse` to edit. Then, select " +":guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for " +":guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "Set outgoing shipment option to deliver in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:39 +msgid "" +"Activating three-step receipts and deliveries creates two new internal " +"locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To " +"rename these locations, go to :menuselection:`Inventory app --> " +"Configuration --> Locations`, click on the :guilabel:`Location` to change, " +"and update the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 +msgid "Deliver in three steps (pick + pack + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:50 +msgid "" +"To create a new quote, navigate to :menuselection:`Sales app --> Create`, " +"which reveals a blank quotation form. On the blank quotation form, select a " +":guilabel:`Customer`, add a storable :guilabel:`Product`, and click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:54 +msgid "" +"A :guilabel:`Delivery` smart button appears in the top right of the " +"quotation form. Clicking it shows the picking order, packing order, and the " +"delivery order associated with the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing three items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:63 +msgid "Process a picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:65 +msgid "" +"The picking, packing, and delivery orders will be created once the sales " +"order is confirmed. To view these transfers, go to " +":menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"Ready status for the pick operation while the packing and delivery operations are waiting\n" +"another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:73 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be packed. The status of the packing " +"order and delivery order will both be :guilabel:`Waiting Another Operation`," +" since the packing and delivery cannot happen until the picking is " +"completed. The status of the delivery order will only change to " +":guilabel:`Ready` when the packing has been marked :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:79 +msgid "" +"The receipt can also be found in the *Inventory* application. In the " +":guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The pick order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 +msgid "" +"Click on the picking to process. If the product is in stock, Odoo will " +"automatically reserve the product. Click :guilabel:`Validate` to mark the " +"picking as done, and complete the transfer to the :guilabel:`Packing Zone`. " +"Then the packing order will be ready. Since the documents are linked, the " +"products which have been previously picked are automatically reserved on the" +" packing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "Validate the picking by clicking Validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 +msgid "Process a packing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 +msgid "" +"The packing order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Pack` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The packing order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 +msgid "" +"Click on the packing order associated with the sales order, then click on " +":guilabel:`Validate` to complete the packing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "" +"Click Validate on the packing order to transfer the product from the packing zone to the\n" +"output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 +msgid "" +"Once the packing order is validated, the product leaves the " +":guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` " +"location. Then, the status of the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 +msgid "Process a delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:121 +msgid "" +"The delivery order will be ready to be processed once the packing is " +"completed, and can be found in the :menuselection:`Inventory` application " +":guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart " +"button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +msgid "The delivery order can be seen in the Delivery Orders Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:129 +msgid "" +"Click on the delivery order associated with the sales order, then click on " +":guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Click Validate on the delivery order to transfer the product from the output location to\n" +"the customer location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:137 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location and moves to the " +":guilabel:`Partners/Customers` location. Then, the status of the document " +"will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:3 +msgid "Process receipts and deliveries in one step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:7 +msgid "" +"By default, incoming shipments are configured to be received directly into " +"stock, and outgoing shipments are configured to be delivered directly from " +"stock to the customer; the default setting for warehouses in Odoo is one " +"step receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:12 +msgid "" +"Incoming and outgoing shipments do not need to be configured with the same " +"steps. For example, products can be received in one step, but shipped in " +"three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:15 +msgid "" +"In the following example, one step will be used for both receipts and " +"deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:18 +msgid "Configure the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:20 +msgid "" +"If another receiving or shipping configuration is set on the warehouse, they" +" can easily be set back to the one step setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:23 +msgid "" +"Begin by navigating to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, and click on the desired warehouse to edit. Next, on the " +":guilabel:`Warehouse Configuration` tab, under the :guilabel:`Shipments` " +"section, select :guilabel:`Receive goods directly (1 step)` for " +":guilabel:`Incoming Shipments` and/or :guilabel:`Deliver goods directly (1 " +"step)` for :guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in one " +"step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:34 +msgid "Receive goods directly (1 step)" +msgstr "รับสินค้าโดยตรง (1 ขั้นตอน)" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 +msgid "Create a purchase order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:71 +msgid "" +"On the main :menuselection:`Purchase` application dashboard, start by making" +" a new quote by clicking :guilabel:`New`. Then, select (or create) a " +":guilabel:`Vendor` from the drop-down field, add a storable " +":guilabel:`Product` to the order lines, and click :guilabel:`Confirm Order` " +"to finalize the quote as a new purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:98 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top-right corner of " +"the :abbr:`PO (purchase order)` form — click it to reveal the associated " +"receipt for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Receipt smart button appears on the confirmed purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 +msgid "" +"Purchase order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "Receipt kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 +msgid "Process the receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 +msgid "" +"When viewing the receipt (associated with the purchase order above), click " +":guilabel:`Validate` to then complete the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Validate the purchase order via the Validate smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:71 +msgid "" +"If :guilabel:`Storage Locations` are activated, clicking the :guilabel:`≣ " +"(bullet list)` details icon next to the :guilabel:`🗑️ (trash)` delete icon " +"enables the :guilabel:`Detailed Operations` screen to pop-up. This allows " +"the location(s) to be specified for the received product(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "" +"Select the Storage Location for the products being received in the Detailed Operations\n" +"pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:80 +msgid "" +"Once the receipt is validated, the product leaves the :guilabel:`Supplier " +"Location` and enters the :guilabel:`WH/Stock Location`. Once it arrives " +"here, it will be available for manufacturing, sales, etc. Then, the status " +"of the document will change to :guilabel:`Done`, thus completing the " +"reception process in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:88 +msgid "Deliver goods directly (1 step)" +msgstr "ส่งสินค้าโดยตรง (1 ขั้นตอน)" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 +msgid "" +"Start my navigating to the main :menuselection:`Sales` app dashboard, and " +"make a new quote by clicking :guilabel:`New`. Then select (or create) a " +":guilabel:`Customer` from the drop-down field, add a storable " +":guilabel:`Product` that is in stock to the order lines, and click " +":guilabel:`Confirm` to finalize the quotation as a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:101 +msgid "" +"A :guilabel:`Delivery` smart button will appear in the top-right corner of " +"the :abbr:`SO (Sales Order)` form — click it to reveal the associated " +"delivery order for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "The Delivery smart button appears after the sales order is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:109 +msgid "" +"Delivery orders can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"to Process` smart button in the :guilabel:`Delivery Orders` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:0 +msgid "Delivery Orders kanban card's 1 to Process smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 +msgid "Process the delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 +msgid "" +"When viewing the delivery order (associated with the sales order above), " +"click :guilabel:`Validate` to then complete the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst-1 +msgid "Validate the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:127 +msgid "" +"Once the picking order is validated, the product leaves the " +":guilabel:`WH/Stock location` and moves to the :guilabel:`Partners/Customers" +" location`. Then, the status of the document will change to " +":guilabel:`Done`, thus completing delivery in one step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:3 +msgid "Process receipts and deliveries in two steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:7 +msgid "" +"Depending on a company's business processes, multiple steps may be needed " +"before receiving or shipping products. In the two-step receipt process, " +"products are received in an input area, then transferred to stock. Two-step " +"receipts work best when various storage locations are being used, such as " +"locked or secured areas, freezers and refrigerators, or various shelves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:12 +msgid "" +"Products can be sorted according to where they are going to be stored, and " +"employees can stock all the products going to a specific location. The " +"products are not available for further processing until they are transferred" +" into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:16 +msgid "" +"In the two-step delivery process, products that are part of a delivery order" +" are picked from the warehouse according to their removal strategy, and " +"brought to an output location before being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:20 +msgid "" +"One situation where this would be useful is when using either a :abbr:`FIFO " +"(First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO " +"(First Expired, First Out)` removal strategy, where the products that are " +"being picked need to be selected based on their receipt date or expiration " +"date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:25 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" <inventory/receipts_delivery_one_step>`, so the settings need to be changed" +" in order to utilize two-step receipts and deliveries. Incoming and outgoing" +" shipments do not need to be set to have the same steps. For example, " +"products can be received in two steps, but shipped in one step. In the " +"following example, two steps will be used for both receipts and deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:32 +msgid "Configure multi-step routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:34 +msgid "" +"First, make sure the :guilabel:`Multi-Step Routes` option is enabled in " +":menuselection:`Inventory --> Configuration --> Settings`, under the " +":guilabel:`Warehouse` heading. After enabling the setting, :guilabel:`Save` " +"the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:39 +msgid "" +"Activating the :guilabel:`Multi-Step Routes` setting will also activate the " +":guilabel:`Storage Locations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:46 +msgid "" +"Next, the warehouse needs to be configured for two-step receipts and " +"deliveries. Go to :menuselection:`Inventory --> Configuration --> " +"Warehouses`, and click on the warehouse to change the warehouse settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:50 +msgid "" +"Then, select :guilabel:`Receive goods in input and then stock (2 steps)` for" +" :guilabel:`Incoming Shipments`, and :guilabel:`Send goods in output and " +"then deliver (2 steps)` for :guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Set incoming and outgoing shipment options to receive and deliver in two " +"steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:59 +msgid "" +"Activating two-step receipts and deliveries will create new *input* and " +"*output* locations, which by default, are labeled :guilabel:`WH/Input` and " +":guilabel:`WH/Output`, respectively, on the :guilabel:`Locations` dashboard." +" To rename these locations, go to :menuselection:`Configuration --> " +"Locations`, and select the :guilabel:`Location` to change. On the location " +"form, update the :guilabel:`Location Name`, and make any other changes (if " +"necessary)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:66 +msgid "Process a receipt in two steps (input + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:77 +msgid "" +"For businesses with multiple warehouses that have different step " +"configurations, the :guilabel:`Deliver To` field on the :abbr:`PO (Purchase " +"Order)` form may need to be specified as the correct *input location* " +"connected to the two-step warehouse, which can be done by selecting the " +"warehouse from the drop-down selection that includes the `Receipts` label at" +" the end of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 +msgid "" +"After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` " +"smart button will appear in the top of the :abbr:`PO (Purchase Order)` form " +"— click it to reveal the associated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "After confirming a purchase order, a Receipt smart button will appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 +msgid "One receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 +msgid "" +"The receipt and internal transfer will be created once the purchase order is" +" confirmed. The status of the receipt will be :guilabel:`Ready`, since the " +"receipt must be processed first. The status of the internal transfer will be" +" :guilabel:`Waiting Another Operation`, since the transfer cannot happen " +"until the receipt is completed. The status of the internal transfer will " +"only change to :guilabel:`Ready` once the receipt has been marked as " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 +msgid "" +"Click on the :guilabel:`Receipt` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"the :guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, then the product will be transferred to the\n" +"WH/Input location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 +msgid "Process the internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product into stock. Navigate to the " +":menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` " +"dashboard, click the :guilabel:`# To Process` smart button in the " +":guilabel:`Internal Transfers` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"One Internal Transfer ready to process in the Inventory Overview kanban " +"view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the receipt and move the product to " +"stock. Once the transfer is validated, the product enters the stock and is " +"available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "Validate the internal transfer to move the item to stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 +msgid "Process a delivery order in two steps (pick + ship)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 +msgid "" +"In the :menuselection:`Sales` application, create a new quote by clicking " +":guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable " +":guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 +msgid "" +"After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart " +"button will appear in the top, above the :abbr:`SO (Sales Order)` form. " +"Click the :guilabel:`Delivery` smart button to reveal the associated " +"receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"After confirming the sales order, the Delivery smart button appears showing two items\n" +"associated with it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 +msgid "" +"Sales order receipts can also be found in the :menuselection:`Inventory` " +"application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# " +"To Process` smart button in the :guilabel:`Pick` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 +msgid "The pick order can be seen in the Inventory kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 +msgid "Process the picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 +msgid "" +"The picking and delivery order will be created once the sales order is " +"confirmed. When the :guilabel:`Delivery` smart button appears, click it to " +"reveal the :guilabel:`Transfers` dashboard, which lists both the picking and" +" the delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 +msgid "" +"The status of the picking will be :guilabel:`Ready`, since the product must " +"be picked from stock before it can be shipped. The status of the delivery " +"order will be :guilabel:`Waiting Another Operation`, since the delivery " +"cannot happen until the picking is completed. The status of the delivery " +"order will only change to :guilabel:`Ready` once the picking has been marked" +" as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "" +"Ready status for the pick operation while the delivery operation is Waiting Another\n" +"Operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 +msgid "" +"Click on the picking delivery order to begin processing it. If the product " +"is in stock, Odoo will automatically reserve the product. Click " +":guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the " +"delivery order will be ready for processing. Since the documents are linked," +" the products which have been previously picked are automatically reserved " +"on the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 +msgid "" +"The delivery order will be ready to be processed once the picking is " +"completed, and can be found in the :menuselection:`Inventory` application, " +"on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To " +"Process` smart button in the :guilabel:`Delivery Orders` kanban card to " +"begin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 +msgid "" +"The delivery order associated with the :abbr:`SO (Sales Order)` can also be " +"quickly accessed by clicking on the :guilabel:`Delivery` smart button again," +" and choosing the delivery order on the :guilabel:`Transfers` page (which " +"should now be marked as :guilabel:`Ready`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst-1 +msgid "The delivery order can be seen in the Inventory Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 +msgid "" +"Click on the delivery order associated with the :abbr:`SO (Sales Order)`, " +"then click on :guilabel:`Validate` to complete the move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 +msgid "" +"Once the delivery order is validated, the product leaves the " +":guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and " +"moves to the :guilabel:`Partners/Customers` location. Then, the status of " +"the document will change to :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 +msgid "Process receipts in three steps" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:7 +msgid "" +"Some companies require a quality control process before receiving goods from" +" suppliers. To accomplish this, Odoo has a three-step process for receiving " +"goods." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:10 +msgid "" +"In the three-step receipt process, products are received in an input area, " +"then transferred to a quality area for inspection. Products that pass the " +"quality inspection are then transferred into stock. The products are not " +"available for further processing until they are transferred out of the " +"quality area and into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:18 +msgid "" +"Odoo is configured by default to :ref:`receive and deliver goods in one step" +" <inventory/receipts_delivery_one_step>`, so the settings need to be changed" +" in order to utilize three-step receipts. First, make sure the *Multi-Step " +"Routes* option is enabled in :menuselection:`Inventory --> Configuration -->" +" Settings --> Warehouse`. Note that activating :guilabel:`Multi-Step Routes`" +" will also activate *Storage Locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Activate multi-step routes and storage locations in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 +msgid "" +"Next, the warehouse needs to be configured for three-step receipts. To do " +"that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`," +" and select the desired warehouse to be edited. Doing so reveals the detail " +"form for that specific warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 +msgid "" +"On that :guilabel:`Warehouse` detail form page, select :guilabel:`Receive " +"goods in input, then quality and then stock (3 steps)` for " +":guilabel:`Incoming Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "Set incoming shipment option to receive in three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 +msgid "" +"Activating three-step receipts and deliveries creates two new internal " +"locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). " +"To rename these locations, go to :menuselection:`Inventory app --> " +"Configuration --> Locations`, then click on the desired location to change " +"(or update) the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 +msgid "Receive in three steps (input + quality + stock)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 +msgid "" +"To create a new :abbr:`RfQ (Request for Quotation)`, navigate to " +":menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ " +"(Request for Quotation)` form page. On this page, select a " +":guilabel:`Vendor`, add a storable :guilabel:`Product`, and click " +":guilabel:`Confirm Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 +msgid "" +"A :guilabel:`Receipt` smart button will appear in the top right, and the " +"receipt will be associated with the purchase order. Clicking on the " +":guilabel:`Receipt` smart button will show the receipt order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 +msgid "Process a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 +msgid "" +"One receipt and two internal transfers (one transfer to quality, and a " +"subsequent transfer to stock) will be created once the purchase order is " +"confirmed. To view these transfers, go to :menuselection:`Inventory --> " +"Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"The status of the three receipt transfers will show which operation is ready and which ones\n" +"are waiting another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 +msgid "" +"The status of the receipt transferring the product to the input location " +"will be :guilabel:`Ready`, since the receipt must be processed before any " +"other operation can occur. The status of the two internal transfers will be " +":guilabel:`Waiting Another Operation`, since the transfers cannot be " +"processed until the linked step before each transfer is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 +msgid "" +"The status of the first internal transfer to *quality* will only change to " +":guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The " +"status for the second internal transfer to *stock* will be marked " +":guilabel:`Ready` only after the transfer to quality has been marked " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 +msgid "" +"The receipt can also be found in the :menuselection:`Inventory` application." +" In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` " +"smart button in the :guilabel:`Receipts` kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "One Receipt ready to process in the Inventory Overview kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 +msgid "" +"Click on the receipt associated with the purchase order, then click " +":guilabel:`Validate` to complete the receipt and move the product to the " +":guilabel:`Input Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Validate the receipt by clicking Validate, and the product will be transferred to the\n" +"WH/Quality location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 +msgid "Process a transfer to Quality Control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 +msgid "" +"Once the product is in the :guilabel:`Input Location`, the internal transfer" +" is ready to move the product to :guilabel:`Quality Control`. In the " +":menuselection:`Inventory` :guilabel:`Overview` dashboard, click the " +":guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` " +"kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 +msgid "" +"Click on the :guilabel:`Transfer` associated with the purchase order, then " +"click :guilabel:`Validate` to complete the transfer and move the product to " +"the :guilabel:`Quality Control` location. Once the transfer is validated, " +"the product is ready for the quality inspection, but is not available for " +"manufacturing or delivery orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst-1 +msgid "" +"Validate the internal transfer to move the item to the Quality Control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 +msgid "Process a transfer to stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 +msgid "" +"Once the product is in the :guilabel:`Quality Control` location, the final " +"internal transfer is ready to move the product to :guilabel:`Stock`. In the " +":guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process`" +" smart button in the :guilabel:`Internal Transfers` Kanban card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 +msgid "" +"Click on the final :guilabel:`Transfer` associated with the purchase order, " +"then click :guilabel:`Validate` to complete the transfer and move the " +"product to stock. Once the transfer is validated, the product enters the " +"stock and is available for customer deliveries or manufacturing orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 +msgid "Incoming shipments and delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 +msgid "" +"There are several ways to handle how a warehouse receives products " +"(receipts) and ships products (deliveries). Depending on several factors, " +"such as the type of products stocked and sold, warehouse size, and the " +"amount of daily confirmed receipts and delivery orders, the way products are" +" handled when coming in and out of the warehouse can vary a lot. Different " +"settings can be configured for receipts and deliveries; they do not have to " +"be configured to have the same number of steps." +msgstr "" +"มีหลายวิธีในการจัดการวิธีที่คลังสินค้าได้รับสินค้า (ใบรับ) และจัดส่งสินค้า " +"(การส่งมอบ) ขึ้นอยู่กับปัจจัยหลายประการ เช่น " +"ประเภทของผลิตภัณฑ์ที่จัดเก็บและขาย ขนาดคลังสินค้า " +"และจำนวนใบเสร็จรับเงินที่ยืนยันรายวันและใบสั่งจัดส่ง " +"วิธีจัดการผลิตภัณฑ์เมื่อเข้าและออกจากคลังสินค้าอาจแตกต่างกันมาก " +"สามารถกำหนดการตั้งค่าต่างๆ สำหรับการรับและการส่งมอบได้ " +"ไม่จำเป็นต้องกำหนดค่าให้มีจำนวนขั้นตอนเท่ากัน" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 +msgid "" +"`Using Routes (eLearning Tutorial) <https://www.odoo.com/slides/slide/using-" +"routes-1018>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:13 +msgid "" +"`Push & Pull Rules (eLearning Tutorial) " +"<https://www.odoo.com/slides/slide/push-pull-rules-1024>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 +msgid "Choosing the right inventory flow to handle receipts and deliveries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:19 +msgid "" +"By default, Odoo handles shipping and receiving in three different ways: in " +"one, two, or three steps. The simplest configuration is one step, which is " +"the default. Each additional step required for a warehouse for either the " +"receiving or shipping process will add an additional layer of operations to " +"perform before a product is either received or shipped. These configurations" +" depend entirely on the requirements for the products stored, such as " +"performing quality checks on received products, or using special packaging " +"on shipped products." +msgstr "" +"ตามค่าเริ่มต้น Odoo จัดการการจัดส่งและรับในสามวิธีที่แตกต่างกัน: ในหนึ่ง สอง" +" หรือสามขั้นตอน การกำหนดค่าที่ง่ายที่สุดคือขั้นตอนเดียวซึ่งเป็นค่าเริ่มต้น " +"แต่ละขั้นตอนเพิ่มเติมที่จำเป็นสำหรับคลังสินค้าสำหรับกระบวนการรับหรือจัดส่งจะเพิ่มชั้นของการดำเนินงานเพิ่มเติมที่จะดำเนินการก่อนที่จะได้รับหรือจัดส่งผลิตภัณฑ์" +" การกำหนดค่าเหล่านี้ขึ้นอยู่กับข้อกำหนดทั้งหมดสำหรับผลิตภัณฑ์ที่จัดเก็บ เช่น" +" การดำเนินการตรวจสอบคุณภาพของผลิตภัณฑ์ที่ได้รับ " +"หรือการใช้บรรจุภัณฑ์พิเศษกับผลิตภัณฑ์ที่จัดส่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:27 +msgid "One-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 +msgid "" +"The receiving and shipping rules for a one-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 +msgid "" +"**Receipt**: Receive products directly into stock. No intermediate steps " +"between receipt and stock occur, such as a transfer to a quality control " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:33 +msgid "" +"**Shipping**: Ship products directly from stock. No intermediate steps " +"between stock and shipping occur, such as a transfer to a packing location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:35 +msgid "" +"Can only be used if not using :abbr:`FIFO (First In, First Out)`, " +":abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First " +"Out)` removal strategies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:37 +msgid "Receipts and/or deliveries are handled quickly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:38 +msgid "" +"Recommended for small warehouses with low stock levels, and for non-" +"perishable items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 +msgid "Items are received or shipped directly into/from stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:42 +msgid "" +":ref:`Process receipts and deliveries in one step " +"<inventory/receipts_delivery_one_step>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 +msgid "Two-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 +msgid "" +"The receiving and shipping rules for a two-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 +msgid "" +"**Input + stock**: Bring products to an input location *before* moving into " +"stock. Products can be organized by different internal storage locations, " +"such as various shelves, freezers, and locked areas, before being stocked in" +" the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:52 +msgid "" +"**Pick + ship**: Bring products to an output location before shipping. " +"Packages can be organized by different carriers or shipping docks before " +"being shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 +msgid "" +"Minimum requirement to use lot numbers or serial numbers to track products " +"with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`" +" or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 +msgid "" +"Recommended for larger warehouses with high stock levels, or when stocking " +"large items (such as mattresses, large furniture, heavy machinery, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 +msgid "" +"Products received will not be available for manufacturing, shipping, etc., " +"until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 +msgid "" +":ref:`Process receipts and deliveries in two steps " +"<inventory/receipts_delivery_two_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 +msgid "Three-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:68 +msgid "" +"The receiving and shipping rules for a three-step configuration are as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:70 +msgid "" +"**Input + quality + stock**: Receive products at the input location, " +"transfer them to a quality control area, and move the ones that pass " +"inspection into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:72 +msgid "" +"**Pick + pack + ship**: Pick products according to their removal strategy, " +"pack them in a dedicated packing area, and bring them to an output location " +"for shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 +msgid "" +"Can be used when tracking products by lot or serial numbers when using a " +":abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or " +":abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:77 +msgid "Recommended for very large warehouses with very high stock levels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 +msgid "" +"Required for any warehouse needing to perform quality control inspections " +"before receiving items into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 +msgid "" +":ref:`Process receipts in three steps <inventory/receipts_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:85 +msgid "" +":ref:`Process deliveries in three steps <inventory/delivery_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 +msgid "Setup and configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:3 +msgid "Delivery methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:5 +msgid "" +"When activated in Odoo, the *Delivery Methods* setting adds the option of " +"calculating the cost of shipping on sales orders and e-commerce shopping " +"carts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:8 +msgid "" +"When integrated with a :ref:`third-party carrier " +"<inventory/shipping/third_party>`, shipping prices are calculated based on " +"the carrier's pricing and packaging information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:12 +msgid "" +":ref:`Third-party shipping carrier setup <inventory/shipping/third_party>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:13 +msgid "" +"`Odoo Tutorials: Delivery Prices " +"<https://www.odoo.com/slides/slide/delivery-prices-613?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:19 +msgid "" +"To calculate shipping on sales orders and e-commerce, the *Delivery Costs* " +"module must be installed. To do so, navigate to the :menuselection:`Apps` " +"application from the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:22 +msgid "" +"Then, remove the :guilabel:`Apps` filter, and type in `Delivery Costs` in " +"the :guilabel:`Search...` bar. After finding the :guilabel:`Delivery Costs` " +"module, click :guilabel:`Activate` to install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "Install the *Delivery Costs* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 +msgid "Add shipping method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 +msgid "" +"To configure delivery methods, go to :menuselection:`Inventory app --> " +"Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:36 +msgid "" +"If the :guilabel:`Shipping Methods` option is not available from the " +":guilabel:`Configuration` drop-down menu, verify whether the feature is " +"enabled by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:39 +msgid "Go to :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:40 +msgid "" +"Scroll to the :guilabel:`Shipping` section and enable the " +":guilabel:`Delivery Methods` feature by checking the corresponding checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "" +"Enable the *Delivery Methods* feature by checking the box in Configuration >" +" Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:47 +msgid "" +"On the :guilabel:`Shipping Methods` page, add a method by clicking " +":guilabel:`New`. Doing so opens a form to provide details about the shipping" +" provider, including:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:50 +msgid "" +":guilabel:`Shipping Method` (*Required field*): the name of the delivery " +"method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:52 +msgid "" +":guilabel:`Provider` (*Required field*): choose the delivery service, like " +"Fedex, if using a :ref:`third-party carrier " +"<inventory/shipping/third_party>`. Ensure the integration with the shipping " +"carrier is properly installed and select the provider from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:56 +msgid "" +"For more details on configuring custom shipping methods, such as :ref:`fixed" +" price <inventory/shipping/fixed>`, :ref:`based on rules " +"<inventory/shipping/rules>`, or :ref:`pickup in store " +"<inventory/shipping/pickup>` options, refer to their respective sections " +"below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 +msgid "" +":guilabel:`Website`: configure shipping methods for an e-commerce page. " +"Select the applicable website from the drop-down menu, or leave it blank to " +"apply the method to all web pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 +msgid "" +":guilabel:`Company`: if the shipping method should apply to a specific " +"company, select it from the drop-down menu. Leave the field blank to apply " +"the method to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:63 +msgid "" +":guilabel:`Delivery Product` (*Required field*): the product listed on the " +":ref:`sales order line <inventory/shipping/sales-order>` as the delivery " +"charge." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:65 +msgid "" +":guilabel:`Free if order amount is above`: checking this box enables free " +"shipping if the customer spends above the specified amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 +msgid "" +"For examples on how to configure specific shipping methods, refer to the " +"sections below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:73 +msgid "Fixed price" +msgstr "ราคาคงที่" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:75 +msgid "" +"To configure a shipping price that is the same for all orders, go to " +":menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then," +" click :guilabel:`New`, and on the shipping method form, set the " +":guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this " +"option makes the :guilabel:`Fixed Price` field become available, which is " +"where the fixed rate shipping amount is defined." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:81 +msgid "" +"To enable free shipping if the amount of the order exceeds a specified " +"amount, check the box :guilabel:`Free if order amount is above` and fill in " +"the amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:85 +msgid "" +"To set up `$20` flat-rate shipping that becomes free if the customer spends " +"over `$100`, fill in the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 +msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:89 +msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:90 +msgid ":guilabel:`Fixed Price`: `$20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 +msgid ":guilabel:`Free if order amount is above`: `$100.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 +msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Example of filling out a shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:101 +msgid "Based on rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:103 +msgid "" +"To calculate the price of shipping based on pricing rules, set the " +":guilabel:`Provider` field to the :guilabel:`Based on Rules` option. " +"Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional " +"margin` to include additional shipping costs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:108 +msgid "Create pricing rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:110 +msgid "" +"Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. " +"Doing so opens the :guilabel:`Create Pricing Rules` window, where the " +":guilabel:`Condition` related to the product weight, volume, price, or " +"quantity is compared to a defined amount to calculate the " +":guilabel:`Delivery Cost`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:115 +msgid "" +"Once finished, click either :guilabel:`Save & New` to add another rule, or " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 +msgid "" +"To charge customers $20 in shipping for orders with five or fewer products, " +"set the :guilabel:`Condition` to `Quantity <= 5.00`, and the " +":guilabel:`Delivery Cost` to `$20`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "" +"Display window to add a pricing rule. Set a condition and delivery cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:125 +msgid "" +"To restrict shipping to specific destinations on the eCommerce website, in " +"the shipping method form, navigate to the :guilabel:`Destination " +"Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, " +"and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations " +"apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:130 +msgid "Calculate delivery cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:132 +msgid "" +"Shipping cost is the :guilabel:`Delivery cost` specified in the rule that " +"satisfies the :guilabel:`Condition`, plus any extra charges from the " +":guilabel:`Margin on rate` and :guilabel:`Additional margin`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:136 +msgid "" +"Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" +"\n" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:140 +msgid "With the two following rules set up:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:142 +msgid "If the order contains five or fewer products, shipping is $20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 +msgid "If the order contains more than five products, shipping is $50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 +msgid "" +":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is " +"`$9.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "" +"Show example of \"Based on rules\" shipping method with margins configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:151 +msgid "" +"When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + " +"9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * " +"50) + 9)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:157 +msgid "Pickup in store" +msgstr "รับสินค้าที่ร้านค้า" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:159 +msgid "" +"To configure in-store pickup, select :guilabel:`Pickup in store` in the " +":guilabel:`Provider` field and specify the pickup location in " +":guilabel:`Warehouse`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 +msgid "" +"To invoice the customer for the shipping cost to the pickup location, choose" +" the :guilabel:`Get Rate and Create Shipment` option in the " +":guilabel:`Integration Level` field. Then, pick either the " +":guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the " +":guilabel:`Invoicing Policy` field to decide whether the added shipping " +"charge on the sales order is the precise cost from the shipping carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:169 +msgid ":ref:`Invoice cost of shipping <inventory/shipping/invoice>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:174 +msgid "Add shipping" +msgstr "เพิ่มการจัดส่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:176 +msgid "" +"Shipping methods can be added to sales orders in the form of delivery " +"products, which appear as individual line items. First, navigate to the " +"desired sales order by going to :menuselection:`Sales app --> Orders --> " +"Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:180 +msgid "" +"On the sales order, click the :guilabel:`Add shipping` button, which opens " +"the :guilabel:`Add a shipping method` pop-up window. Then, choose a " +":guilabel:`Shipping Method` from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 +msgid "" +"The :guilabel:`Total Order Weight` is pre-filled based on product weights " +"(that are defined in the :guilabel:`Inventory` tab for each product form). " +"Edit the field to specify the exact weight, and then click :guilabel:`Add` " +"to add the shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:188 +msgid "" +"The amount defined in :guilabel:`Total Order Weight` overwrites the total " +"product weights defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 +msgid "" +"The shipping cost is added to the *sales order line* as the " +":guilabel:`Delivery Product` detailed on the shipping method form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:195 +msgid "" +"`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is " +"added to sales order `S00088`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:0 +msgid "Show delivery order on the sales order line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:203 +msgid "Delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:205 +msgid "" +"The shipping method added to the sales order is linked to the shipping " +"carrier details on the delivery order. To add or change the delivery method " +"on the delivery itself, go to the :guilabel:`Additional Info` tab and modify" +" the :guilabel:`Carrier` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst-1 +msgid "Shipping carrier information on the delivery form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3 +msgid "How to get DHL credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:5 +msgid "In order to use the Odoo DHL API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:7 +msgid "A DHL.com SiteID" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:9 +msgid "A DHL Password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:11 +msgid "A DHL Account Number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:15 +msgid "" +"Getting SiteID and password for countries other than United States (UK and " +"Rest of the world)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:17 +msgid "" +"You should contact DHL account manager and request integration for XML " +"Express API. The presales should provide you live credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:20 +msgid "Getting SiteID and Password for United States" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:22 +msgid "" +"You need to write to xmlrequests@dhl.com along with your full Account " +"details like account number, region, address, etc. to get API Access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:3 +msgid "Set up Sendcloud shipping services in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:5 +msgid "" +"Sendcloud is a shipping service aggregator that facilitates the integration " +"of European shipping carriers with Odoo. Once integrated, users can select " +"shipping carriers on inventory operations in their Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:10 +msgid "" +"`Sendcloud integration documentation <https://support.sendcloud.com/hc/en-" +"us/articles /360059470491-Odoo-integration>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:14 +msgid "Setup in Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:17 +msgid "Create an account and activate carriers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:19 +msgid "" +"To get started, go to `Sendcloud's platform <https://www.sendcloud.com>`_ to" +" configure the account and generate the connector credentials. Log in with " +"the Sendcloud account, or create a new one if needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:24 +msgid "" +"For new account creation, Sendcloud will ask for a :abbr:`VAT (Value-Added " +"Tax Identification)` number or :abbr:`EORI (Economic Operators' Registration" +" and Identification)` number. After completing the account setup, activate " +"(or deactivate) the shipping carriers that will be used in the Odoo " +"database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:30 +msgid "" +"Odoo integration of Sendcloud works on free Sendcloud plans *only* if a bank" +" account is linked, since Sendcloud won't ship for free. To use shipping " +"rules or individual custom carrier contacts, a paid plan of Sendcloud is " +"required." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 +msgid "Warehouse configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:37 +msgid "" +"Once logged into the Sendcloud account, navigate to :menuselection:`Settings" +" --> Shipping --> Addresses`, and fill in the field for :guilabel:`Warehouse" +" address`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Adding addresses in the Sendcloud settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:44 +msgid "" +"To allow Sendcloud to process returns as well, a :guilabel:`Return Address` " +"is required. Under the :guilabel:`Miscellaneous section`, there is a field " +"called :guilabel:`Address Name (optional)`. The Odoo warehouse name should " +"be entered here, and the characters should be exactly the same." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**SendClould configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Miscellaneous`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address Name (optional)`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Brand`: `Default`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid "**Odoo warehouse configuration**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Warehouse`: `Warehouse #1`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Short Name`: `WH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Company`: `My company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Address`: `My Company (San Francisco)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:61 +msgid "" +"Notice how the inputs for the :guilabel:`Warehouse` field, for both the Odoo" +" configuration and the Sendcloud configuration, are the exact same." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:65 +msgid "Generate Sendcloud credentials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:67 +msgid "" +"In the Sendcloud account, navigate to :menuselection:`Settings --> " +"Integrations` in the menu on the right. Next, search for :guilabel:`Odoo " +"Native`. Then, click on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:70 +msgid "" +"After clicking on :guilabel:`Connect`, the page redirects to the " +":guilabel:`Sendcloud API` settings page, where the :guilabel:`Public and " +"Secret Keys` are produced. The next step is to name the " +":guilabel:`Integration`. The naming convention is as follows: `Odoo " +"CompanyName`, with the user's company name replacing `CompanyName` (e.g. " +"`Odoo StealthyWood`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:75 +msgid "" +"Then, check the box next to :guilabel:`Service Points` and select the " +"shipping services for this integration. After saving, the :guilabel:`Public " +"and Secret Keys` are generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Configuring the Sendcloud integration and receiving the credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:86 +msgid "Install the Sendcloud shipping module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:88 +msgid "" +"After the Sendcloud account is set up and configured, it's time to configure" +" the Odoo database. To get started, go to Odoo's :guilabel:`Apps` module, " +"search for the :guilabel:`Sendcloud Shipping` integration, and install it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Sendcloud Shipping module in the Odoo Apps module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:97 +msgid "Sendcloud shipping connector configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:99 +msgid "" +"Once installed, activate the :guilabel:`Sendcloud Shipping` module in " +":menuselection:`Inventory --> Configuration --> Settings`. The " +":guilabel:`Sendcloud Connector` setting is found under the " +":guilabel:`Shipping Connectors` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:103 +msgid "" +"After activating the :guilabel:`Sendcloud Connector`, click on the " +":guilabel:`Sendcloud Shipping Methods` link below the listed connector. Once" +" on the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:108 +msgid "" +":guilabel:`Shipping Methods` can also be accessed by going to " +":menuselection:`Inventory --> Configuration --> Delivery --> Shipping " +"Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:111 +msgid "" +"Fill out the following fields in the :guilabel:`New Shipping Method` form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:113 +msgid ":guilabel:`Shipping Method`: type `Sendcloud DPD`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:114 +msgid "" +":guilabel:`Provider`: select :guilabel:`Sendcloud` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:115 +msgid "" +":guilabel:`Delivery Product`: set the product that was configured for this " +"shipping method or create a new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:117 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab, enter the " +":guilabel:`Sendcloud Public Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:118 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab, enter the " +":guilabel:`Sendcloud Secret Key`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:119 +msgid "" +"Manually :guilabel:`Save` the form by clicking the cloud icon next to the " +":guilabel:`Shipping Methods / New` breadcrumbs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:122 +msgid "" +"After configuring and saving the form, follow these steps to load the " +"shipping products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:124 +msgid "" +"In the :guilabel:`SendCloud Configuration` tab of the :guilabel:`New " +"Shipping Method` form, click on the :guilabel:`Load your SendCloud shipping " +"products` link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:126 +msgid "" +"Select the shipping products the company would like to use for deliveries " +"and returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:127 +msgid "Click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:130 +msgid "Sample Sendcloud shipping products configured in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`DELIVERY`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Shipping Product`: `DPD Home 0-31.5kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Maximum Weight`: `31.50`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:138 +msgid "" +":guilabel:`Countries`: `Austria` `Belgium` `Bosnia` `Herzegovina` `Bulgaria`" +" `Croatia` `Czech` `Republic` `Denmark` `Estonia` `Finland` `France` " +"`Germany` `Greece` `Hungary` `Iceland` `Ireland` `Italy` `Latvia` " +"`Liechtenstein` `Lithuania` `Luxembourg` `Monaco` `Netherlands` `Norway` " +"`Poland` `Portugal` `Romania` `Serbia` `Slovakia` `Slovenia` `Spain` " +"`Sweden` `Switzerland`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`RETURN`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Shipping Product`: `DPD Return 0-20kg`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Carrier`: `DPD`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Minimum Weight`: `0.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Maximum Weight`: `20.00`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:0 +msgid ":guilabel:`Return Countries`: `Belgium` `Netherlands`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst-1 +msgid "Example of shipping products configured in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:156 +msgid "" +"Sendcloud does not provide test keys when a company tests the sending of a " +"package in Odoo. This means if a package is created, the configured " +"Sendcloud account will be charged, unless the associated package is canceled" +" within 24 hours of creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:160 +msgid "" +"Odoo has a built-in layer of protection against unwanted charges when using " +"test environments. Within a test environment, if a shipping method is used " +"to create labels, then those labels are immediately canceled after the " +"creation — this occurs automatically. The test and production environment " +"settings can be toggled back and forth from the :guilabel:`Smart Buttons`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:166 +msgid "Generate a label with Sendcloud" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:168 +msgid "" +"When creating a quotation in Odoo, add shipping and a :guilabel:`Sendcloud " +"shipping product`. Then, :guilabel:`Validate` the delivery. Shipping label " +"documents are automatically generated in the chatter, which include the " +"following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:172 +msgid ":guilabel:`Shipping label(s)` depending on the number of packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:173 +msgid "" +":guilabel:`Return label(s)` if the Sendcloud connector is configured for " +"returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:174 +msgid "" +":guilabel:`Customs document(s)` should the destination country require them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:176 +msgid "Additionally, the tracking number is now available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:179 +msgid "" +"When return labels are created, Sendcloud will automatically charge the " +"configured Sendcloud account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:183 +msgid "FAQ" +msgstr "คำถามที่พบบ่อย" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:186 +msgid "Shipment is too heavy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:188 +msgid "" +"If the shipment is too heavy for the Sendcloud service that is configured, " +"then the weight is split to simulate multiple packages. Products will need " +"to be put in different :guilabel:`Packages` to :guilabel:`Validate` the " +"transfer and generate labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:192 +msgid "" +":guilabel:`Rules` can also be set up in Sendcloud to use other shipping " +"methods when the weight is too heavy. However, note that these rules will " +"not apply to the shipping price calculation on the calculation on the sales " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:197 +msgid "When using a personal carrier contract" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:199 +msgid "" +"When using a personal carrier contract in Sendcloud, if the the price is not" +" accurately reflected when creating a quotation in Odoo, then the pricing " +"information needs to be updated in Sendcloud." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:203 +msgid "Measuring volumetric weight" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:205 +msgid "" +"Many carriers have several measures for weight. There is the actual weight " +"of the products in the parcel, and there is the *volumetric weight* " +"(:dfn:`Volumetric weight is the volume that a package occupies when in " +"transit. In other words it is the physical size of a package`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:210 +msgid "" +"Check to see if selected carrier(s) already have defined formulas to compute" +" the volumetric weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:214 +msgid "" +"`Sendcloud: How to calculate & automate parcel volumetric weight " +"<https://support.sendcloud.com/ hc/en-us/articles/360059644051-How-to-" +"calculate-automate-parcel-volumetric-weight>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:219 +msgid "Unable to calculate shipping rate" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 +msgid "" +"First, verify that product being shipped has a weight that is supported by " +"the selected shipping method. If this is set, then verify that the " +"destination country (from the customer address) is supported by the carrier." +" The country of origin (warehouse address) should also be supported by the " +"carrier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:3 +msgid "How to integrate a third party shipper?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 +msgid "" +"Odoo can handle various delivery methods, including third party shippers. " +"Odoo can be linked with the transportation company tracking system. It will " +"allow you to manage the transport company, the real prices and the " +"destination." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 +msgid "" +"In the inventory module, click on :menuselection:`Configuration --> " +"Settings`. Under **Shipping Connectors**, flag the transportation companies " +"you want to integrate :" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:31 +msgid "" +"If you want to integrate delivery methods in your e-commerce, you'll have to" +" install the **eCommerce Delivery** module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:40 +msgid "" +"The delivery methods for the chosen shippers have been automatically " +"created. Most of the time, there will be **2** delivery methods for the same" +" provider: one for **international** shipping and the other for **domestic**" +" shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:45 +msgid "" +"You can create other methods with the same provider with other " +"configuration, for example the **Packaging Type**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:48 +msgid "" +"You can change the **Name** of the delivery method. This is the name that " +"will appear on your ecommerce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:51 +msgid "Flag **Shipping enabled** when you are ready to use it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 +msgid "" +"In the pricing tab, the name of the provider chosen under the **Price " +"computation** means that the pricing will be computed by the shipper system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:59 +msgid "The configuration of the shipper is split into two columns:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:61 +msgid "" +"The first one is linked to **your account** (developer key, password,...). " +"For more information, please refer to the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:69 +msgid "" +"Finally you can limit the delivery method to a few destinations. You can " +"limit it to some countries, states or even zip codes. This feature limits " +"the list of countries on your e-commerce. It is useful for the domestic " +"providers. For example, USPS US only delivers from the United States to the " +"United States." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:97 +msgid "" +"Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products" +" you want to ship and set a weight on it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:104 +msgid "" +"The weight on the product form is expressed in kilograms. Don't forget to " +"make the conversion if you are used to the imperial measurement system." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:109 +msgid "Sale process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:112 +msgid "Sale order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:117 +msgid "" +"You can now choose the carrier on your sale order. Click on **Delivery " +"method** to choose the right one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:120 +msgid "" +"The price is computed when you save the sale order or when you click on " +"**Set price**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 +msgid "" +"If you want to invoice the price of the delivery charge on the sale order, " +"click on **Set price**, it will add a line with the name of the delivery " +"method as a product. It may vary from the real price." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:127 +msgid "" +"Otherwise, the real price (computed when the delivery is validated) will " +"automatically be added to the invoice. For more information, please read the" +" document :doc:`../advanced_operations_shipping/invoicing`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 +msgid "Delivery" +msgstr "การจัดส่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:134 +msgid "" +"The delivery created from the sale order will take the shipping information " +"from it. You can change the carrier if you want to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:143 +msgid "" +"The weight is computed based on the products weights. The shipping cost will" +" be computed once the transfer is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 +msgid "" +"Click on **Validate** to receive the tracking number. The **Carrier Tracking" +" ref** field will automatically be filled. Click on the **Tracking** button " +"to check your delivery on the provider website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:160 +msgid ":doc:`../advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:161 +msgid ":doc:`../advanced_operations_shipping/labels`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:3 +msgid "How to get UPS credentials for integration with Odoo?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:5 +msgid "In order to use the Odoo UPS API, you will need:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:7 +msgid "A UPS.com user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:9 +msgid "A UPS account number" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:11 +msgid "An Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:13 +msgid "" +"An Access Key is a 16 character alphanumeric code that allows access to the " +"UPS Developer Kit API Development and Production servers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:17 +msgid "Create a UPS Account" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:19 +msgid "" +"Note that only customers located in the US can open a UPS account online. If" +" you are located outside the US, you will need to contact UPS Customer " +"Service in order to to open an account." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:23 +msgid "" +"You can read additional information about opening a UPS account on the their" +" website, on the page, `How to Open a UPS Account Online " +"<https://www.ups.com/content/us/en/resources/sri/openaccountonline.html?srch_pos=2&srch_phr=open+ups+account>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:27 +msgid "" +"If you don't already have a UPS account, you can create one along with your " +"online profile by following these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:30 +msgid "" +"1. Access the UPS.com web site at `www.ups.com <http://www.ups.com/>`__, and" +" click the **New User** link at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:34 +msgid "" +"2. Click the **Register for MyUPS** button, and follow the prompts to " +"complete the registration process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:37 +msgid "" +"If you already have a UPS account, you can add it to your online profile as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:39 +msgid "" +"Log in to the `UPS.com website <http://www.ups.com/>`_) using your UPS.com " +"User ID and Password." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:41 +msgid "Click the **My UPS** tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:43 +msgid "Click the **Account Summary** link." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:45 +msgid "" +"4. Click the **Add an Existing UPS Account** link in the **UPS Account " +"Details** section of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:48 +msgid "" +"5. In the **Add New Account** screen, enter the **UPS Account Number**, " +"**Account Name**, and **Postal Code** fields. The country defaults to United" +" States.q" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:52 +msgid "Click the **Next** button to continue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:55 +msgid "Get an Access Key" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:57 +msgid "" +"After you have added your UPS account number to your user profile you can " +"request an Access Key from UPS using the steps below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:60 +msgid "" +"Go to the `UPS Developer Kit web page " +"<https://www.ups.com/upsdeveloperkit?loc=en_US>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:61 +msgid "Log into UPS.com with your user ID and password" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:62 +msgid "Click on the link **Request an access key**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:63 +msgid "Verify your contact information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:64 +msgid "Click the **Request Access Key** button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:66 +msgid "" +"The **Access Key** will be provided to you on the web page, and an email " +"with the Access Key will be sent to the email address of the primary " +"contact." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 +msgid "Warehouses and storage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:3 +msgid "Batch picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:7 +msgid "" +"*Batch picking* enables a single picker to handle multiple orders at once, " +"reducing the time needed to navigate to the same location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:10 +msgid "" +"When picking in batches, orders are grouped and consolidated into a picking " +"list. After the picking, the batch is taken to an output location, where the" +" products are sorted into their respective delivery packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:15 +msgid "" +":ref:`Use Barcode app for pickings <inventory/management/barcode_picking>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:17 +msgid "" +"Since orders *must* be sorted at the output location after being picked, " +"this picking method suits businesses with a few products that are ordered " +"often. Storing high-demand items in easily accessible locations can increase" +" the number of orders that are fulfilled efficiently." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:24 +msgid "" +"To activate the batch picking option, begin by going to " +":menuselection:`Inventory app --> Configuration --> Settings`. Under the " +":guilabel:`Operations` section, check the :guilabel:`Batch Transfers` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Enable the *Batch Transfers* in Inventory > Configuration > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:32 +msgid "" +"Since batch picking is a method to optimize the *pick* operation in Odoo, " +"the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options " +"under the :guilabel:`Warehouse` heading must also be checked on this " +"settings page. When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "" +"Enable *Storage Locations* and *Multi-Step Routes* Inventory > Configuration" +" > Settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:40 +msgid "" +"Lastly, enable the warehouse picking feature, by navigating to the warehouse" +" settings page, which is accessible from :menuselection:`Inventory app --> " +"Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:43 +msgid "" +"From here, select the desired warehouse from the list. Then, from the radio " +"options available for :guilabel:`Outgoing Shipments`, select either the " +":guilabel:`Send goods in output and then deliver (2 steps)` or " +":guilabel:`Pack goods, send goods in output and then deliver (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:131 +msgid ":ref:`Delivery in two steps <inventory/receipts_delivery_two_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:132 +msgid ":ref:`Delivery in three steps <inventory/delivery_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Set up 2-step or 3-step outgoing shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:56 +msgid "Create batch transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:58 +msgid "" +"Manually create batch transfers directly from the :menuselection:`Inventory " +"app --> Operations --> Batch Transfers` page. Click the :guilabel:`New` " +"button to begin creating a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:61 +msgid "On the batch transfer form, fill the following fields out accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:63 +msgid "" +":guilabel:`Responsible`: employee assigned to the picking. Leave this field " +"blank if *any* worker can fulfill this picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:65 +msgid "" +":guilabel:`Operation Type`: from the drop-down menu, select the operation " +"type under which the picking is categorized." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:67 +msgid "" +":guilabel:`Scheduled Date`: specifies the date by which the " +":guilabel:`Responsible` person should complete the transfer to the output " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:70 +msgid "" +"Next, in the :guilabel:`Transfers` list, click :guilabel:`Add a line` to " +"open the :guilabel:`Add: Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:73 +msgid "" +"If the :guilabel:`Operation Type` field was filled, the list will filter " +"transfer records matching the selected :guilabel:`Operation Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:76 +msgid "Click the :guilabel:`New` button to create a new transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:78 +msgid "" +"Once the transfer records are selected, click :guilabel:`Confirm` to confirm" +" the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:81 +msgid "" +"A new batch transfer assigned to the :guilabel:`Responsible`, `Joel Willis`," +" for the `Pick` :guilabel:`Operation Type`. The :guilabel:`Scheduled Date` " +"is set to `August 11`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "View of *Batch Transfers* form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:88 +msgid "" +"Clicking the :guilabel:`Add a line` button opens the " +":guilabel:`Add:Transfers` window, displaying only pickings. This is because " +"the :guilabel:`Operation Type` was set to `Pick` on the batch transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:92 +msgid "" +"Click the checkbox to the left of the transfers, `WH/PICK/00001` and " +"`WH/PICK/00002`, to include them in the new transfer. Then, click the " +":guilabel:`Select` button to close the :guilabel:`Add:Transfers` window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Select multiple transfers from the *Add:Transfers* window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:101 +msgid "Add batch from transfers list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:103 +msgid "" +"Another method of creating batch transfers is available using the " +":guilabel:`Add to batch` option in a list. Navigate to the " +":menuselection:`Inventory app --> Operations` drop-down menu, and select any" +" of the :guilabel:`Transfers` to open a filtered list of transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "" +"Show all transfer types in a drop-down menu: Receipts, Deliveries, Internal Transfers,\n" +"Manufacturings, Batch Transfers, Dropships." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:112 +msgid "" +"On the transfers list, select the checkbox to the left of the selected " +"transfers to add in a batch. Next, navigate to the :guilabel:`Actions ⚙️ " +"(gear)` button, and click :guilabel:`Add to batch` from the resulting drop-" +"down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Use *Add to batch* button, from the *Action* button's list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:151 +msgid "" +"Doing so opens an :guilabel:`Add to batch` pop-up window, wherein the " +"employee :guilabel:`Responsible` for the picking can be assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:123 +msgid "" +"Choose from the two radio options to add to :guilabel:`an existing batch " +"transfer` or create :guilabel:`a new batch transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:126 +msgid "To begin with a draft, select the :guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:128 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:160 +msgid "Conclude the process by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "Show *Add to batch* window to create a batch transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:135 +msgid "Process batch transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:137 +msgid "" +"Handle batch transfers in the :menuselection:`Inventory app --> Operations " +"--> Batch Transfers` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:140 +msgid "" +"From here, select the intended transfer from the list. Then, on the batch " +"transfer form, input the :guilabel:`Done` quantities for each product, under" +" the :guilabel:`Detailed Operations` tab. Finally, select " +":guilabel:`Validate` to complete the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:145 +msgid "" +"Be certain the batch transfer is complete when the :guilabel:`Validate` " +"button is highlighted in purple. If the :guilabel:`Check Availability` " +"button is highlighted instead, that means there are items in the batch that " +"are currently *not* available in-stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:152 +msgid "" +"In a batch transfer involving products from pickings, `WH/PICK/00001` and " +"`WH/PICK/00002`, the :guilabel:`Detailed Operations` tab shows that the " +"product, `Cabinet with Doors`, has been picked because the :guilabel:`Done` " +"column matches the value in the :guilabel:`Reserved` column. However, `0.00`" +" quantities have been picked for the other product, `Cable Management Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "" +"Show batch transfer of products from two pickings in the *Detailed " +"Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:161 +msgid "" +"Only in-stock products are visible in the :guilabel:`Detailed Operations` " +"tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:163 +msgid "" +"To view the complete product list, switch to the :guilabel:`Operations` tab." +" On this list, the :guilabel:`Demand` column indicates the required quantity" +" for the order. The :guilabel:`Reserved` column shows the available stock to" +" fulfill the order. Lastly, the :guilabel:`Done` column specifies the " +"products that have been picked, and are ready for the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:169 +msgid "" +"The product, `Desk Pad`, from the same batch as the :ref:`example above " +"<inventory/management/batch-transfers-example>`, is only visible in the " +":guilabel:`Operations` tab because there are no :guilabel:`Reserved` " +"quantities in-stock to fulfill the batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:173 +msgid "" +"Click the :guilabel:`Check Availability` button to search the stock again " +"for available products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Show unavailable reserved quantities in the *Operations* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:180 +msgid "Create backorder" +msgstr "สร้างคำสั่งล่วงหน้า" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:182 +msgid "" +"On the batch transfer form, if the :guilabel:`Done` quantity of the product " +"is *less* than the :guilabel:`Reserved` quantity, a pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:185 +msgid "This pop-up window provides the option: :guilabel:`Create Backorder?`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:187 +msgid "" +"Clicking the :guilabel:`Create Backorder` button automatically creates a new" +" batch transfer, containing the remaining products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:190 +msgid "" +"Click :guilabel:`No Backorder` to finish the picking *without* creating " +"another batch picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:192 +msgid "" +"Click :guilabel:`Discard` to cancel the validation, and return to the batch " +"transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Show the *Create Backorder* pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:201 +msgid "Process batch transfer: Barcode app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:203 +msgid "" +"Created batch transfers are also listed in the :menuselection:`Barcode` app," +" accessible by selecting the :guilabel:`Batch Transfers` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:206 +msgid "" +"By default, confirmed batch pickings appear on the :guilabel:`Batch " +"Transfers` page. On that page, click on the desired batch transfer to open " +"the detailed list of products for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst-1 +msgid "Show list of to-do batch transfers in *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:213 +msgid "" +"For the chosen batch transfer, follow the instructions at the top of the " +"page in the black background. Begin by scanning the product's barcode to " +"record a single product for picking. To record multiple quantities, click " +"the :guilabel:`✏️ (pencil)` icon, and enter the required quantities for the " +"picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:219 +msgid "" +"Products from the same order are labeled with the same color on the left. " +"Completed pickings are highlighted in green." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:223 +msgid "" +"In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, " +"and 4 `Four Person Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate " +"that the last two product pickings are complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:227 +msgid "" +"`1/2` units of the `Cabinet with Doors` has already been picked, and after " +"scanning the product barcode for the second cabinet, Odoo prompts the user " +"to `Scan a serial number` to record the unique serial number for " +":ref:`product tracking <inventory/serial_numbers/configure>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 +msgid "Display products to be picked in barcode view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:235 +msgid "" +"Once all the products have been picked, click on :guilabel:`Validate` to " +"mark the batch transfer as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:3 +msgid "Closest location removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:5 +msgid "" +"For the *Closest Location* removal strategy, products are picked based on " +"the alphanumeric order of storage location titles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:8 +msgid "" +"The goal of this strategy is to save the warehouse worker from taking a long" +" journey to a farther shelf when the product is also available at a closer " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:13 +msgid ":doc:`About removal strategies <removal>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:16 +msgid "" +"To understand *location sequence* in the closest removal strategy, consider " +"the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:19 +msgid "" +"A product is stored in the following locations: `Shelf A/Pallet`, `Shelf " +"A/Rack 1`, and `Shelf A/Rack 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 +msgid "Show a mockup of real storage location in a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:26 +msgid "" +"The sublocation, `Pallet`, is on the ground level. Products stored here are " +"easier to retrieve, compared to requiring a forklift to reach `Rack 1` and " +"`Rack 2`. The storage locations were strategically named in alphabetic " +"order, based on ease of access." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:31 +msgid "" +"To use this removal strategy, the :guilabel:`Storage Locations` and " +":guilabel:`Multi-Step Routes` settings **must** be enabled in " +":menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:35 +msgid "" +":ref:`Set up removal strategy <inventory/warehouses_storage/removal-config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:40 +msgid "Location names" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:42 +msgid "" +"To configure location names, begin by navigating to " +":menuselection:`Inventory app --> Configuration --> Locations`. Then, select" +" an existing location, or click :guilabel:`New` to create a new one, and " +"then enter the desired name in the :guilabel:`Location Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:46 +msgid "" +"Once the locations are named in alphabetical order, based on their proximity" +" to the output or packing location, set the removal strategy on the " +":ref:`parent location <inventory/location-hierarchy>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:50 +msgid "" +"To do that, in the :guilabel:`Locations` list, select the parent location of" +" the alphabetically named storage locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:53 +msgid "" +"Doing so opens the form for the parent location. In the :guilabel:`Removal " +"Strategy` field, select :guilabel:`Closest Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:57 +msgid "" +"In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest " +"to the packing area, where products retrieved from shelves are packed for " +"shipment. The popular product, `iPhone charger` is stored in three " +"locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:62 +msgid "" +"To use closest location, set the removal strategy on the parent location, " +"'WH/Stock'." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:30 +msgid "Workflow" +msgstr "ขั้นตอนการทำงาน" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:67 +msgid "" +"To see how the closest location removal strategy works, consider the " +"following example, featuring the popular product, `iPhone charger`, which is" +" stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:71 +msgid "" +"Fifteen, five, and thirty units are in stock at each respective location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:74 +msgid "" +"To check the on-hand stock at each storage location, navigate to the product" +" form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:0 +msgid "Show on-hand stock at all locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:81 +msgid "" +"Create a :ref:`delivery order <inventory/delivery/one-step>` for eighteen " +"units of the `iPhone charger` by navigating to the :menuselection:`Sales " +"app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:84 +msgid "" +"After adding the products, clicking :guilabel:`Confirm` creates a delivery " +"order that reserves items stored at the closest location, using the removal " +"strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:87 +msgid "" +"For more details about *where* the units were picked, select the " +":guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so " +"opens the :guilabel:`Open: Stock move` pop-up window that displays how the " +"reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst:91 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked. All fifteen of the units stored at the closest location, " +"`WH/Stock/Shelf 1`, are picked first. The remaining three units are then " +"selected from the second closest location, `WH/Stock/Shelf 2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/closest_location.rst-1 +msgid "Display *Pick From* quantities for the order for iPhone chargers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:3 +msgid "Cluster picking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:10 +msgid "" +"Cluster picking is an advanced order fulfillment approach derived from " +":ref:`batch picking <inventory/misc/batch_picking>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:13 +msgid "" +"In this strategy, pickers load a cart with multiple packages, each " +"designated for a specific *sales order* (SO). Then, the picker travels to " +"each storage location, and places the products directly in the package of " +"the associated order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:17 +msgid "" +"This method is most efficient for medium-sized companies, with high order " +"volumes, and relatively few unique products, since the method eliminates the" +" need for sorting products into packages for customers after picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:21 +msgid "" +"However, cluster picking does have some disadvantages. For instance, urgent " +"orders cannot be prioritized, and optimized batches must be manually created" +" beforehand. As a result, the picking process can lead to bottlenecks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:28 +msgid "|SO| 1 calls for one apple and orange" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:29 +msgid "|SO| 2 calls for one apple and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:30 +msgid "|SO| 3 calls for one apple, orange, and banana" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:32 +msgid "" +"Apples are stored in Shelf A, oranges in Shelf B, and bananas in Shelf C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:34 +msgid "" +"To pick products for three orders at once, the cart is loaded with three " +"empty packages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:36 +msgid "" +"Starting at Shelf A, the picker places apples into each package. Next, the " +"picker navigates to Shelf B, and places oranges in the packages designated " +"for |SO| 1 and |SO| 3. Finally, the picker pushes the cart to Shelf C, and " +"loads packages for |SO| 2 and |SO| 3 with a banana, each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:40 +msgid "" +"With the packages for all three |SOS| packed, the picker pushes the cart to " +"the output location, where the packages are sealed and prepared for " +"shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Show example of fulfilling sales orders 2 and 3 at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:50 +msgid "" +"To enable cluster picking, begin by navigating to :menuselection:`Inventory " +"app --> Configuration --> Settings`. Under the :guilabel:`Operations` " +"heading, activate the :guilabel:`Packages` and :guilabel:`Batch Transfers` " +"options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst-1 +msgid "Activate *Packages* and *Batch Transfers* features in the settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:58 +msgid "" +"Since batch picking is used to optimize the *pick* operation in Odoo, the " +":guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` options, " +"under the :guilabel:`Warehouse` heading, must also be checked on this " +"settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:62 +msgid "" +"*Storage locations* allow products to be stored in specific locations they " +"can be picked from, while *multi-step routes* enable the picking operation " +"itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:65 +msgid "When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:74 +msgid "Packages setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:76 +msgid "" +"After the :guilabel:`Packages` feature is enabled, navigate to " +":menuselection:`Inventory app --> Products --> Packages`, and click the " +":guilabel:`New` button to create a new package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:79 +msgid "" +"On the new package form, the :guilabel:`Package Reference` is pre-filled " +"with the next available `PACK` number in the system. :guilabel:`Pack Date` " +"is automatically set to the creation date of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:83 +msgid "" +"For the :guilabel:`Package Use` field, the :guilabel:`Disposable Box` option" +" should be selected if the package is used for a shipping. Alternatively, " +"the :guilabel:`Reusable Box` option should be selected if the package is " +"simply used as a method of grouping products from the same |SO| together " +"before they are moved to the intended shipping box at the output location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:169 +msgid ":ref:`Packages <inventory/management/packages>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:92 +msgid "" +"A package intended for cluster picking is named `CLUSTER-PACK-3` for easy " +"identification. For this workflow, the products are directly packed using " +"their intended shipping boxes, so :guilabel:`Package Use` is set to " +":guilabel:`Disposable Box`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Create new package form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:101 +msgid "Create cluster batch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:103 +msgid "" +"To see how cluster picking works in Odoo, navigate to the " +":menuselection:`Sales` app, and create |SOS| that will be fulfilled together" +" in the same batch. After confirming an |SO|, the :guilabel:`Delivery` smart" +" button becomes visible. Displayed inside the icon is a number representing " +"the amount of steps in the outgoing shipment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:109 +msgid "" +"Begin by creating three |SOS| for the apples, oranges, and bananas, as shown" +" in the :ref:`example above <inventory/misc/cluster_picking/example>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:112 +msgid "" +"After confirming the |SO|, the :guilabel:`Delivery` smart button displays " +"the number `2`, indicating there are two operations to complete: `Pick` and " +"`Delivery`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example sales order for an apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:119 +msgid "" +"With the |SOS| created, orders now must be grouped into batches. To do so, " +"navigate to the *Inventory* dashboard and select the operation type card, " +":guilabel:`Delivery Orders` or :guilabel:`Pick` (whichever is the first " +"operation in the delivery flow)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:123 +msgid "" +"Doing so displays a filtered list of outgoing operations with the " +":guilabel:`Ready` status, indicating that all the products in the |SO| are " +"in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:127 +msgid "" +"Cluster pick batches can be created for outgoing shipments in one, two, or " +"three steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:130 +msgid ":ref:`Delivery in one step <inventory/receipts_delivery_one_step>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:134 +msgid "" +"Click the checkbox to the left of the corresponding outgoing operation to " +"add them to the batch. With the desired pickings selected, click the " +":guilabel:`⚙️ Actions (gear)` button, and select the :guilabel:`Add to " +"batch` option from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:139 +msgid "" +"To create a cluster batch, as shown in the :ref:`example above " +"<inventory/misc/cluster_picking/example>`, in a warehouse configured with " +"two-step outgoing shipments, the following pick operations are selected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:143 +msgid "`WH/PICK/00007`: linked to |SO| 88 for one apple and orange." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:144 +msgid "`WH/PICK/00008`: linked to |SO| 89 for one apple and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:145 +msgid "`WH/PICK/00009`: linked to |SO| 90 for one apple, orange, and banana." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:154 +msgid "" +"Choose from the two options in the :guilabel:`Add to` field to either: add " +"to :guilabel:`an existing batch transfer`, or create :guilabel:`a new batch " +"transfer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:157 +msgid "" +"To create draft batch pickings to be confirmed at a later date, select the " +":guilabel:`Draft` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:167 +msgid "Process batches" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:169 +msgid "" +"To process batches, navigate to :menuselection:`Inventory app --> Operations" +" --> Batch Transfers`. Click on a batch to select it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:172 +msgid "" +"In the :guilabel:`Detailed Operations` tab, products that are to be picked " +"are grouped by location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:174 +msgid "" +"Under the :guilabel:`Source Package` or :guilabel:`Destination Package` " +"field, enter the package used for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:178 +msgid "" +"Use the :guilabel:`Source Package` field when the picking package is " +"configured as *reusable* on the :ref:`package form <inventory/misc/create-" +"package>`. This means the products are temporarily placed in a container " +"during picking, before getting transferred to their final shipping box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:182 +msgid "" +"Alternatively, use the :guilabel:`Destination Package` field when the " +"product is directly placed in its *disposable* shipping box during picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:186 +msgid "" +"Process the cluster batch for the three orders of apples, oranges, and " +"bananas :ref:`example <inventory/misc/cluster_picking/example>` by assigning" +" each picking to a dedicated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:189 +msgid "" +"At the storage location for apples, `WH/Stock/Shelf A`, assign the apples in" +" all three pickings to one of the three disposable packages, `CLUSTER-" +"PACK-1`, `CLUSTER-PACK-2`, or `CLUSTER-PACK-3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:192 +msgid "" +"Record this in Odoo using the :guilabel:`Destination Package` field in the " +":guilabel:`Detailed Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of processing cluster pickings in *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:200 +msgid "In Barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:202 +msgid "" +"To process cluster pickings directly from the *Barcode* app, select the " +":guilabel:`Batch Transfers` button from the *Barcode* dashboard. Then, " +"select the desired batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:205 +msgid "" +"On the batch transfer screen, the products in the picking are grouped by " +"location, and each line is color-coded to associate products in the same " +"picking together." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:208 +msgid "" +"Then, follow the prompt to :guilabel:`Scan the source location` barcode for " +"the storage location of the first product. Then, scan the barcode for the " +"product and package to process the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:211 +msgid "" +"Repeat this for all products, and click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:214 +msgid "" +"To find the package barcode, navigate to :menuselection:`Inventory app --> " +"Products --> Packages`, select the desired package, click the :guilabel:`⚙️ " +"(gear)` icon at the top of the package form, and select the " +":guilabel:`Print` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:218 +msgid "" +"Next, select one of the three print options to generate the package barcode " +"from the :guilabel:`Package Reference` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Display where the package barcode can be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:226 +msgid "" +"Begin processing the cluster picking by going to the first storage location," +" `Shelf A`, and scanning the :ref:`location barcode " +"<barcode/setup/location>`. Doing so highlights all the pickings that need " +"products from this particular location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:230 +msgid "" +"Scan the barcode for the apple, which highlights the picking (labeled in " +"red) for the product `Apple`, for the picking, `WH/PICK/00007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:233 +msgid "" +"Then, scan the `CLUSTER-PACK-1` package barcode, and place the product in " +"the designated package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:0 +msgid "Example of cluster batch from the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:240 +msgid "" +"After creating a batch transfer and assigning a package to a picking, Odoo " +"suggests the specified package by displaying the name *in italics* under the" +" product name, ensuring pickers place products into the correct boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:3 +msgid "Organize a cross-dock in a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:5 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:13 +msgid "" +"For more information on how to organize your warehouse, read our blog: `What" +" is cross-docking and is it for me? <https://www.odoo.com/blog/business-" +"hacks-1/post/what-is-cross-docking-and-is-it-for-me-270>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:20 +msgid "" +"In the *Inventory* app, open :menuselection:`Configuration --> Settings` and" +" activate the *Multi-Step Routes*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:27 +msgid "Doing so will also enable the *Storage Locations* feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:29 +msgid "" +"Now, both *Incoming* and *Outgoing* shipments should be configured to work " +"with 2 steps. To adapt the configuration, go to :menuselection:`Inventory " +"--> Configuration --> Warehouses` and edit your warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:36 +msgid "" +"This modification will lead to the creation of a *Cross-Docking* route that " +"can be found in :menuselection:`Inventory --> Configuration --> Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:43 +msgid "Configure products with Cross-Dock Route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:45 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:55 +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 "" +"เมื่อเสร็จแล้ว ให้สร้างใบสั่งขายสำหรับผลิตภัณฑ์และยืนยัน Odoo " +"จะสร้างการโอนสองครั้งโดยอัตโนมัติซึ่งจะเชื่อมโยงกับใบสั่งขาย " +"อย่างแรกคือการถ่ายโอนจาก *ตำแหน่งอินพุต* ไปยัง *ตำแหน่งเอาต์พุต* " +"ซึ่งสอดคล้องกับการเคลื่อนย้ายผลิตภัณฑ์ในพื้นที่ *ศูนย์กระจายสินค้า* " +"รายการที่สองคือคำสั่งจัดส่งจาก *สถานที่ส่งออก* ไปยัง *สถานที่ลูกค้าของคุณ " +"ทั้งสองรายการอยู่ในสถานะ *กำลังรอการดำเนินการอื่น* " +"เนื่องจากเรายังจำเป็นต้องสั่งผลิตภัณฑ์ไปยังซัพพลายเออร์ของเรา" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:68 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:77 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:86 +msgid "" +"The delivery order is now ready to be processed and can be validated too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:5 +msgid "" +"For most companies, warehouse stock only needs to be counted once a year. " +"This is why, by default, after making an *inventory adjustment* in Odoo, the" +" scheduled date for the next inventory count is set for the 31st of December" +" of the current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:9 +msgid "" +"However, for some businesses, it's crucial to have an accurate inventory " +"count at all times. These companies use *cycle counts* to keep critical " +"stock levels accurate. Cycle counting is a method by which companies count " +"their inventory more often in certain *locations*, to ensure that their " +"physical inventory counts match their inventory records." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:15 +msgid "Activate storage locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:17 +msgid "" +"In Odoo, cycle counts are location-based. Therefore, the *storage locations*" +" feature needs to be enabled before performing a cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:20 +msgid "" +"To enable this feature, navigate to :menuselection:`Inventory app --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` " +"section. Then, click the checkbox next to :guilabel:`Storage Locations`. " +"Click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Enabled storage locations setting in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:29 +msgid "Change inventory count frequency by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:31 +msgid "" +"Now that the storage locations setting is enabled, the inventory count " +"frequency can be changed for specific locations created in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:34 +msgid "" +"To view and edit locations, navigate to :menuselection:`Inventory app --> " +"Configuration --> Locations`. This reveals a :guilabel:`Locations` page " +"containing every location currently created and listed in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:38 +msgid "" +"From this page, click into a location to reveal the settings and " +"configuration page for that location. Click :guilabel:`Edit` to edit the " +"location settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:41 +msgid "" +"Under the :guilabel:`Cyclic Inventory` section, locate the " +":guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if" +" this location has not been edited previously). In this field, change the " +"value to whichever number of days is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Location frequency setting on location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:50 +msgid "" +"A location that needs an inventory count every 30 days should have the " +":guilabel:`Inventory Frequency (Days)` value set to `30`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:53 +msgid "" +"Once the frequency has been changed to the desired number of days, click " +":guilabel:`Save` to save changes. Now, once an inventory adjustment is " +"applied to this location, the next scheduled count date is automatically " +"set, based on the value entered into the :guilabel:`Inventory Frequency " +"(Days)` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 +msgid "" +"To perform a cycle count for a specific location in the warehouse, navigate " +"to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. " +"This reveals an :guilabel:`Inventory Adjustments` page containing all " +"products currently in stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 +msgid "" +"From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at" +" the top of the page, under the :guilabel:`Search...` bar), can be used to " +"select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 +msgid "" +"To select a specific location and view all products within that location, " +"click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to " +"reveal a new drop-down menu to the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 +msgid "" +"Click :guilabel:`Location` from the drop-down menu, then click " +":guilabel:`Apply`. The page now displays condensed drop-down menus of each " +"location in the warehouse that has products in stock, and a cycle count can " +"be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 +msgid "" +"In large warehouses with multiple locations and a high volume of products, " +"it might be easier to search for the specific location desired. To do this, " +"from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. " +"Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right." +" Click this menu to reveal three drop-downs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 +msgid "" +"For the first field, click and select :guilabel:`Location` from the drop-" +"down. For the second field, leave the :guilabel:`contains` value as is. For " +"the third field, type in the name of the location that is being searched " +"for. Click :guilabel:`Apply` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Applied filters and group by on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 +msgid "" +"While cycle counts are typically performed per location, the scheduled date " +"for full inventory counts of everything in-stock in the warehouse can also " +"be manually changed to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 +msgid "" +"To modify the default scheduled date, go to :menuselection:`Inventory app " +"--> Configuration --> Settings`. Then, in the :guilabel:`Operations` " +"section, locate the :guilabel:`Annual Inventory Day and Month` setting " +"field, which includes a drop-down that is set to `31` :guilabel:`December` " +"by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 +msgid "" +"To change the day, click the `31`, and change it to a day within the range " +"`1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 +msgid "" +"Then, to change the month, click :guilabel:`December` to reveal the drop-" +"down menu, and select the desired month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 +msgid "" +"Once all changes have been made, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 +msgid ":doc:`../inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:3 +msgid "FEFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:5 +msgid "" +"The *First Expired, First Out* (FEFO) removal strategy targets products for " +"removal based on their assigned removal dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:9 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:9 +msgid ":doc:`Other removal strategies <removal>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:14 +msgid "Removal date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:16 +msgid "" +"Products **must** be removed from inventory before their *removal date*, " +"which is set as a certain number of days before the product's *expiration " +"date*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:19 +msgid "" +"The user sets this number of days by navigating to the product form's " +":guilabel:`Inventory` tab. Under the :guilabel:`Traceability` section, " +"ensure the :guilabel:`Tracking` field is set to either :guilabel:`By Lots` " +"or :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:23 +msgid "" +"Next, select the :guilabel:`Expiration Date` option, which makes the " +":guilabel:`Removal Date` field (and other date fields) appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:27 +msgid "" +"The :guilabel:`Lots and Serial Numbers` and :guilabel:`Expiration Dates` " +"features **must** be enabled in :menuselection:`Inventory app --> " +"Configuration --> Settings` to track expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:31 +msgid "" +"The expiration date of a product is determined by adding the date the " +"product was received to the number of days specified in the " +":guilabel:`Expiration Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:34 +msgid "" +"The removal date takes this expiration date, and subtracts the number of " +"days specified in the :guilabel:`Removal Date` field of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:38 +msgid "" +":doc:`Expiration dates " +"<../../product_management/product_tracking/expiration_dates>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:41 +msgid "" +"In the :guilabel:`Inventory` tab of the product, `Egg`, the following " +":guilabel:`Dates` are set by the user:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:44 +msgid ":guilabel:`Expiration Date`: `30` days after receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:45 +msgid ":guilabel:`Removal Date`: `15` days before expiration date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "Display expiration and removal dates set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:51 +msgid "" +"A shipment of Eggs arrive at the warehouse on January 1st. So, the " +"expiration date of the Eggs is **January 31st** (Jan 1st + 30). By " +"extension, the removal date is **January 16th** (Jan 31 - 15)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:57 +msgid "" +"To view the expiration dates of items in stock, navigate to the product " +"form, and click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:60 +msgid "" +"Next, click the additional options icon, located on the far-right, and " +"select the columns: :guilabel:`Expiration Date` and :guilabel:`Removal " +"Date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "" +"Show expiration dates from the inventory adjustments model accessed from the *On Hand*\n" +"smart button from the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:71 +msgid "" +"Using the :abbr:`FEFO (First Expired, First Out)` removal strategy ensures " +"that products with the nearest removal date are picked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:74 +msgid "" +"To understand how this removal strategy works, consider the following " +"example below about the product, `Carton of eggs`, which is a box containing" +" twelve eggs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:77 +msgid "" +"The product is tracked :guilabel:`By Lots`, and the product category's " +":guilabel:`Force Removal Strategy` is set to :guilabel:`First Expired, First" +" Out (FEFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:24 +msgid "" +":ref:`Set up force removal strategy <inventory/warehouses_storage/removal-" +"config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:25 +msgid ":ref:`Enable lots tracking <inventory/warehouses_storage/lots-setup>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:83 +msgid "" +"`Odoo Tutorials: Perishable Products " +"<https://www.odoo.com/slides/slide/5324/share>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:35 +msgid "LOT1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:36 +msgid "LOT2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:37 +msgid "LOT3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:38 +msgid "On-hand stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:73 +msgid "5" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:75 +msgid "2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:96 +msgid "1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:140 +msgid "Expiration date" +msgstr "วันที่หมดอายุ" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:98 +msgid "April 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:99 +msgid "April 10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:100 +msgid "April 15" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:101 +msgid ":ref:`Removal date <inventory/warehouses_storage/exp-date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:102 +msgid "February 26" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:103 +msgid "March 4" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:104 +msgid "March 9" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:106 +msgid "" +"To see the removal strategy in action, go to the :menuselection:`Sales app` " +"and create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:109 +msgid "" +"Clicking :guilabel:`Confirm` creates a delivery order for today, December " +"29th, and the lot numbers with the soonest expiration dates are reserved, " +"using the :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:113 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the Carton of egg's product line, in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:117 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst:120 +msgid "" +"Since the order demanded six Cartons of eggs, using the :abbr:`FEFO (First " +"Expired, First Out)` removal strategy, all five Cartons from `LOT1`, with " +"the removal date of February 26th, are picked. The remaining Carton is " +"selected from `LOT2`, which has a removal date of March 4th." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fefo.rst-1 +msgid "The stock moves window that shows the lots to be removed using FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:3 +msgid "FIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:5 +msgid "" +"The *First In, First Out* (FIFO) removal strategy selects products with the " +"earliest arrival dates. This method is useful for companies selling products" +" that have short demand cycles, like clothes, for example. By using " +":abbr:`FIFO (First In, First Out)`, companies can prevent prolonged stock " +"retention of specific styles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:11 +msgid ":doc:`Other removal methods <removal>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:14 +msgid "" +"Various quantities of the product, `T-shirt`, tracked by lot numbers, arrive" +" on August 1st and August 25th. For an order made on September 1st, the " +":abbr:`FIFO (First In, First Out)` removal strategy prioritizes lots that " +"have been in stock the longest. So, products received on August 1st are " +"selected first for picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Illustration of FIFO selecting the oldest products in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:24 +msgid "" +":ref:`Lot/serial number setup details <inventory/warehouses_storage/lots-" +"setup>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:29 +msgid "Arrival date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:31 +msgid "" +"To see the product lot or serial number that arrived in inventory first, " +"navigate to :menuselection:`Inventory app --> Products --> Lots/Serial " +"Numbers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:34 +msgid "" +"Then, select the :guilabel:`▶️ (right-pointing arrow)` icon on the left of a" +" product line, in order to reveal a list of the product's lots or serial " +"numbers that are in stock. The :guilabel:`Created On` field shows the " +"lot/serial number creation date, which is, essentially, the arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:39 +msgid "" +"Serial number `00000000500` of the product, `Cabinet with Doors`, arrived on" +" December 29th, as displayed in the :guilabel:`Created On` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:0 +msgid "Display arrival date of a lot for an item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:49 +msgid "" +"To understand how :abbr:`FIFO (First In, First Out)` rotates products out, " +"consider the following example, focusing on three lots of white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:52 +msgid "" +"The shirts are from the *All/Clothes* category, where :abbr:`FIFO (First In," +" First Out)` is set as the :guilabel:`Force Removal Strategy`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:55 +msgid "" +"The white shirts are tracked :guilabel:`By Lots` in the " +":guilabel:`Inventory` tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:62 +msgid "" +"The following table represents the on-hand stock and lot number details of " +"white shirts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:74 +msgid "3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:42 +msgid ":ref:`Created on <inventory/warehouses_storage/arrival_date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:77 +msgid "March 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:78 +msgid "April 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:79 +msgid "May 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:81 +msgid "" +"To see the removal strategy in action, create a :ref:`delivery order " +"<inventory/delivery/one-step>` for six white shirts by navigating to the " +":menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:84 +msgid "" +"After clicking :guilabel:`Confirm` on the sales order, a delivery order with" +" the oldest lot numbers for shirts are reserved, using the :abbr:`FIFO " +"(First In, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:87 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the white shirt's product line in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst:91 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from. Since the order demanded six shirts, all five shirts from " +"`LOT1`, and one shirt from `LOT2`, are selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/fifo.rst-1 +msgid "Two lots being reserved for a sales order with the FIFO strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:3 +msgid "Least packages removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:5 +msgid "" +"The *Least Packages* removal strategy fulfills an order by opening the " +"fewest number of packages, which is ideal for maintaining organized stock " +"without needing to open multiple boxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:10 +msgid "" +"`Odoo Tutorials: Least Packages " +"<https://www.odoo.com/slides/slide/5477/share>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:12 +msgid "" +"To understand how the removal strategy works, consider the following " +"example, featuring a warehouse that stores packages of flour in bulk " +"packages of `100 kg`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:15 +msgid "" +"To minimize moisture, and/or prevent pests from entering open packages, the " +"least packages removal strategy is used to pick from a single, opened " +"package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:21 +msgid "" +"A package of `100 kg` of flour is depleted to `54 kg` after fulfilling some " +"orders. There are other packages of `100 kg` in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:24 +msgid "" +"When an order for `14 kg` of flour is placed, the package of `54 kg` is " +"selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:25 +msgid "" +"When an order for *more* than `54 kg` of flour is placed, an unopened `100 " +"kg` package is used to fulfill the order. While this temporarily results in " +"two open packages, these open packages are prioritized in the next picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:32 +msgid "" +"Using the least package removal strategy, the fewest number of packages is " +"used to fulfill an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:35 +msgid "" +"The :ref:`Packages feature <inventory/warehouses_storage/pack-setup>` " +"**must** be enabled to use this strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:38 +msgid "" +"Consider the following example, featuring the product, `Flour`. The " +"product's :guilabel:`Units of Measure` field, located on the product form, " +"is set to `kg`. The product is stored in packages of `100 kg`, with one " +"remaining package containing `54 kg`. The product category's " +":guilabel:`Force Removal Strategy` is set to :guilabel:`Least Packages`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:44 +msgid "" +":ref:`Set removal strategy on product category " +"<inventory/warehouses_storage/removal-config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:47 +msgid "" +"To check the product's on-hand stock, navigate to the product form, and " +"click the :guilabel:`On Hand` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:0 +msgid "Show on-hand stock in each package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:54 +msgid "" +"Create a :ref:`delivery order <inventory/delivery/one-step>` for eighty " +"kilograms of flour by going to the :menuselection:`Sales app` and creating a" +" new quotation. After clicking :guilabel:`Confirm`, the delivery order is " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:58 +msgid "" +"On the delivery order, the :guilabel:`Quantity` field displays the amount " +"automatically picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:61 +msgid "" +"For more details about *where* the units were picked, select the " +":guilabel:`⦙≣ (bulleted list)` icon, located on the far-right. Doing so " +"opens the :guilabel:`Open: Stock move` pop-up window, displaying how the " +"reserved items were picked, according to the removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst:65 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked. Since the order demanded eighty kilograms, which exceeds the " +"quantity in the opened package of `54 kg`, an unopened package of `100 kg` " +"is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/least_packages.rst-1 +msgid "Show which package was picked in the *Pick From* field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:3 +msgid "LIFO removal" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:5 +msgid "" +"The *Last In, First Out* (LIFO) removal strategy picks the **newest** " +"products on-hand, based on the date they entered a warehouse's stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:8 +msgid "" +"Every time an order is placed for products using the :abbr:`LIFO (Last In, " +"First Out)` strategy, a transfer is created for the lot/serial number that " +"has most recently entered the stock (the **last** lot/serial number that " +"entered the warehouse's inventory)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:16 +msgid "" +"In many countries, the :abbr:`LIFO (Last In, First Out)` removal strategy is" +" banned, since it can potentially result in old, expired, or obsolete " +"products being delivered to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:19 +msgid "" +"Consider the following example, with the product, `Cinder Block`, which is " +"tracked :guilabel:`By Lots` in the :guilabel:`Inventory` tab of the product " +"form. The :guilabel:`Force Removal Strategy` for the cinder block's product " +"category is set to :guilabel:`Last In, First Out (LIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:26 +msgid ":ref:`Check arrival date <inventory/warehouses_storage/arrival_date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:28 +msgid "" +"The following table represents the cinder blocks in stock, and their various" +" lot number details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:43 +msgid "June 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:44 +msgid "June 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:45 +msgid "June 6" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:47 +msgid "" +"To see the removal strategy in action, create a :ref:`delivery order " +"<inventory/delivery/one-step>` for seven cinder blocks by navigating to the " +":menuselection:`Sales app` and creating a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:51 +msgid "" +":guilabel:`Confirm` the sales order to create a delivery order. Doing so " +"reserves the newest lot numbers are using the :abbr:`LIFO (Last In, First " +"Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:54 +msgid "" +"To view the detailed pickings, click the :guilabel:`⦙≣ (bulleted list)` " +"icon, located on the far-right of the cinder block's product line in the " +":guilabel:`Operations` tab of the delivery order. Doing so opens the " +":guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst:58 +msgid "" +"In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from`" +" field displays where the quantities to fulfill the :guilabel:`Demand` are " +"picked from. Since the order demanded seven cinder blocks, the newest cinder" +" blocks from `LOT3` are selected, using the :abbr:`LIFO (Last In, First " +"Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/lifo.rst-1 +msgid "" +"The detailed operations shows which lots are being selected for the picking." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 +msgid "Consignment: buy and sell stock without owning it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:5 +msgid "" +"Most of the time, products stored in a company's warehouse are either " +"purchased from suppliers, or are manufactured in-house. However, suppliers " +"will sometimes let companies store and sell products in the company's " +"warehouse, without having to buy those items up-front. This is called " +"*consignment*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:10 +msgid "" +"Consignment is a useful method for suppliers to launch new products, and " +"easily deliver to their customers. It's also a great way for the company " +"storing the products (the consignee) to earn something back for their " +"efforts. Consignees can even charge a fee for the convenience of storing " +"products they don't actually own." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:16 +msgid "Enable the consignment setting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:18 +msgid "" +"To receive, store, and sell consignment stock, the feature needs to be " +"enabled in the settings. To do this, go to :menuselection:`Inventory --> " +"Configuration --> Settings`, and under the :guilabel:`Traceability` section," +" check the box next to :guilabel:`Consignment`, and then click " +":guilabel:`Save` to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Enabled Consignment setting in Inventory configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:28 +msgid "Receive (and store) consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:30 +msgid "" +"With the feature enabled in Odoo, consignment stock can now be received into" +" a warehouse. From the main :menuselection:`Inventory` dashboard, click into" +" the :guilabel:`Receipts` section. Then, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:35 +msgid "" +"Consignment stock is not actually purchased from the vendor; it is simply " +"received and stored. Because of this, there are no quotations or purchase " +"orders involved in receiving consignment stock. So, *every* receipt of " +"consignment stock will start by creating manual receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:39 +msgid "" +"Choose a vendor to enter in the :guilabel:`Receive From` field, and then " +"choose the same vendor to enter in the :guilabel:`Assign Owner` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:43 +msgid "" +"Since the products received from the vendor will be owned by the same " +"vendor, the :guilabel:`Receive From` and :guilabel:`Assign Owner` fields " +"must match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:46 +msgid "" +"Once the vendor-related fields are set, enter products into the " +":guilabel:`Product` lines, and set the quantities to be received into the " +"warehouse under the :guilabel:`Done` column. If the :guilabel:`Units of " +"Measure` feature is enabled, the :abbr:`UoM (Units of Measure)` can be " +"changed, as well. Once all the consignment stock has been received, " +":guilabel:`Validate` the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Matching vendor fields in consignment Receipt creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:56 +msgid "Sell and deliver consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:58 +msgid "" +"Once consignment stock has been received into the warehouse, it can be sold " +"the same as any other in-stock product that has the :guilabel:`Can Be Sold` " +"option enabled on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:61 +msgid "" +"To create a sales order, navigate to the :menuselection:`Sales` app, and " +"from the :guilabel:`Quotations` overview, click :guilabel:`Create`. Next, " +"choose a customer to enter into the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:66 +msgid "" +"The :guilabel:`Customer` *must* be different from the :guilabel:`Vendor` " +"that supplied the consignment stock received (and stored) in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:69 +msgid "" +"Add the consignment product under the :guilabel:`Product` column in the " +"order lines, set the :guilabel:`Quantity`, and fill out any other pertinent " +"product details on the form. Once the quotation is complete, click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Sales order of consignment stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:77 +msgid "" +"Once the :abbr:`RFQ (Request for Quotation)` has been confirmed, it will " +"become a sales order. From here, the products can be delivered by clicking " +"on the :guilabel:`Delivery` smart button, and selecting :guilabel:`Validate`" +" to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:82 +msgid "Traceability and reporting of consignment stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:84 +msgid "" +"Although consignment stock is owned by the vendor who supplied it, and not " +"by the company storing it in their warehouse, consignment products will " +"*still* appear in certain inventory reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:87 +msgid "" +"To find inventory reports, go to :menuselection:`Inventory --> Reporting`, " +"and choose a report to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:91 +msgid "" +"Since the consignee does not actually own consigment stock, these products " +"are *not* reflected in the :guilabel:`Stock Valuation` report, and have no " +"impact on the consignee's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:96 +msgid "Product moves report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:98 +msgid "" +"To view all information about on-hand stock moves, navigate to the the " +":guilabel:`Product Moves` dashboard by going to :menuselection:`Inventory " +"--> Reporting --> Product Moves`. For consignment products, the information " +"in this report is the same as any other product: the history of its product " +"moves can be reviewed; the :guilabel:`Quantity Done` and " +":guilabel:`Reference` document are available; and its :guilabel:`Locations` " +"are available, as well. The consignment stock will originate from " +":guilabel:`Partner Location/Vendors`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:106 +msgid "" +"To view a consignment product's moves by ownership, select the " +":guilabel:`Group By` filter, choose the :guilabel:`Add Custom Group` " +"parameter, and then select :guilabel:`From Owner`, and :guilabel:`Apply` to " +"finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst-1 +msgid "Consignment stock moves history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:115 +msgid "" +"To see forecasted units of consignment stock, go to " +":menuselection:`Inventory --> Reporting --> Forecasted Inventory`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:119 +msgid "Stock on hand report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:121 +msgid "" +"View the :guilabel:`Stock On Hand` dashboard by navigating to " +":menuselection:`Inventory --> Reporting --> Inventory Report`. From this " +"report, the :guilabel:`Locations` of all stock on-hand are displayed, in " +"addition to the quantities per location. For consigment products, the " +":guilabel:`Owner` column will be populated with the owner of those products," +" or the original vendor who supplied the products in the first place." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:3 +msgid "Putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:6 +msgid "What is a Putaway Rule?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:8 +msgid "" +"A good warehouse implementation makes sure that products automatically move " +"to their appropriate destination location. To make that process easier, Odoo" +" uses *Putaway Rules*. Putaway is the process of taking products from the " +"received shipments and putting them into the appropriate location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:13 +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:20 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Activate Multi-Step Routes in Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:29 +msgid "Setting up a putaway rule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:31 +msgid "" +"In some cases, like for a retail shop storing fruits and vegetables, " +"products should be stored in different locations depending on several " +"factors like frequency, size, product category, specific environment needs, " +"and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:35 +msgid "" +"In this example, suppose there is one warehouse location, **WH/Stock**, with" +" the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:38 +msgid "WH/Stock/Pallets" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:40 +msgid "WH/Stock/Pallets/PAL1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:41 +msgid "WH/Stock/Pallets/PAL2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:42 +msgid "WH/Stock/Pallets/PAL3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:44 +msgid "WH/Stock/Shelf 1" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:46 +msgid "WH/Stock/Shelf 2" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:48 +msgid "WH/Stock/Shelf 2/Small Refrigerator" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:50 +msgid "WH/Stock/Shelf 3" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:52 +msgid "" +"Manage those locations with putaway rules. To create a putaway rule, open " +"the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> " +"Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway " +"rule that indicated the main location the product will enter before being " +"redirected to the right storage location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:58 +msgid "" +"The putaway rules can be defined either per product/product category and/or " +"package type (the :guilabel:`Packages` setting must be enabled for that). " +"Putaway rules are read sequentially until a match is found." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:62 +msgid "Take the following example:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:64 +msgid "" +"If water (category All/drinks) is received, whatever the package, it will be" +" redirected to WH/Stock/Shelf 2/Small Refrigerator." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:66 +msgid "" +"If orange juice cans, packaged in boxes, are received, they will be " +"redirected to WH/Stock/Shelf 2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:68 +msgid "" +"If water or apple juice bottles, packaged in boxes, are received, they will " +"be redirected to WH/Stock/Shelf 3." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:70 +msgid "" +"If a pallet of lemonade cans are receieved, it will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Some examples of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:77 +msgid "Using Storage Categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:79 +msgid "" +"A *Storage Category* is an extra location attribute. Storage categories " +"allow the user to define the quantity of products that can be stored in the " +"location and how the location will be selected with putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:86 +msgid "" +"In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> " +"Settings` and activate the :guilabel:`Storage Categories` feature. By doing " +"so, the :guilabel:`Storage Locations` feature is also automatically " +"activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:91 +msgid "Create a Storage Category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:93 +msgid "" +"To create a storage category, go to :menuselection:`Inventory --> " +"Configuration --> Storage Categories` and click :guilabel:`Create`. Then, " +"click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to " +":menuselection:`Configuration --> Storage Categories` to create a new " +"storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "" +"Create Storage Categories inside Odoo Inventory configuration settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:102 +msgid "" +"First, click :guilabel:`Create` and type a name for the storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 +msgid "" +"Then, there are options to limit the capacity by weight, by product, or by " +"package type. The :guilabel:`Allow New Product` field defines when the " +"location is considered available to store a product:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 +msgid "" +":guilabel:`If location is empty`: a product can be added there only if the " +"location is empty." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:109 +msgid "" +":guilabel:`If products are the same`: a product can be added there only if " +"the same product is already there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:111 +msgid "" +":guilabel:`Allow mixed products`: several different products can be stored " +"in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:114 +msgid "" +"Once the storage category settings are saved, the storage category can be " +"linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "" +"When a Storage Category is created, it can be linked to a warehouse " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:121 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:123 +msgid "" +"To continue the example from above, apply the \"High Frequency Pallets\" on " +"the PAL1 and PAL2 locations and rework the putaway rules as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:126 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 +msgid "" +"If PAL1 and PAL2 are empty, the pallet will be redirected to " +"WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 +msgid "" +"If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:130 +msgid "" +"If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst-1 +msgid "Storage Categories used in a variety of putaway rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:3 +msgid "Removal strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:5 +msgid "" +"For companies with warehouses, *removal strategies* determine **which** " +"products are taken from the warehouse, and **when**. For example, for " +"perishable products, prioritizing the picking of goods with the nearest " +"expiration date helps minimize food spoilage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:9 +msgid "" +"The following columns in the table below list the removal strategies " +"available in Odoo, and detail how pickings are determined along with the " +"picking order. Leverage these removal strategies to have Odoo automatically " +"select how products are selected for orders:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:18 +msgid ":doc:`FIFO <fifo>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:19 +msgid ":doc:`LIFO <lifo>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:20 +msgid ":doc:`FEFO <fefo>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:21 +msgid ":doc:`Closest Location <closest_location>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:22 +msgid ":doc:`Least Packages <least_packages>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:23 +msgid "Based on" +msgstr "อิงตาม" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:24 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:25 +msgid ":ref:`Incoming date <inventory/warehouses_storage/arrival_date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:26 +msgid ":ref:`Removal date <inventory/warehouses_storage/removal-date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:27 +msgid ":ref:`Location sequence <inventory/warehouses_storage/sequence>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:28 +msgid ":ref:`Package quantity <inventory/warehouses_storage/pkg-qty>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:29 +msgid "Selection order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:30 +msgid "First in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:31 +msgid "Last in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:32 +msgid ":ref:`First to expire <inventory/warehouses_storage/exp-date>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:33 +msgid "" +":ref:`Alphanumeric name of location <inventory/warehouses_storage/location-" +"name>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:34 +msgid "Quantity closest to fulfilling demand" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:36 +msgid "" +"For comprehensive examples for how to use each removal strategy, refer to " +"each individual documentation page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:44 +msgid "" +"Removal strategies are set on either the product category or storage " +"location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "" +"Change the Force Removal Strategy for either the Product Categories or " +"Locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:50 +msgid "" +"Configure removal strategies on the location by going to " +":menuselection:`Inventory --> Configuration --> Locations`, and selecting " +"the desired location. On the location form, choose a removal strategy from " +"the :guilabel:`Removal Strategy` field's drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:55 +msgid "" +"To set a removal strategy on a location, the :guilabel:`Storage Locations` " +"and :guilabel:`Multi-Step Routes` settings **must** be enabled in " +":menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:59 +msgid "" +"These features are **only** necessary when setting the removal strategy on a" +" location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:61 +msgid "" +"Configure removal strategies on product categories by going to " +":menuselection:`Inventory --> Configuration --> Product Categories` and " +"selecting the intended product category. Next, choose a removal strategy " +"from the :guilabel:`Force Removal Strategy` drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:66 +msgid "" +"When there are different removal strategies applied on both the location and" +" product category for a product, the value set on the :guilabel:`Force " +"Removal Strategy` field set on a :guilabel:`Product Category` form is " +"applied as top priority." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:91 +msgid "Required features" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:73 +msgid "" +"While some removal strategies are available by default, some additional " +"features **must** be enabled in :menuselection:`Inventory --> Configuration " +"--> Settings` for the removal strategy option to appear in the drop-down " +"menu of the :guilabel:`Force Removal Strategy` or :guilabel:`Removal " +"Strategy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:78 +msgid "" +"Refer to the table below for a summary of required features. Otherwise, " +"refer to the dedicated sections for the removal strategy for more details on" +" requirements and usage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:86 +msgid "FIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:87 +msgid "LIFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:88 +msgid "FEFO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:89 +msgid "Closest Location" +msgstr "ตำแหน่งที่ใกล้ที่สุด" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:90 +msgid "Least Packages" +msgstr "แพ็คเกจน้อยที่สุด" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:93 +msgid "Lots & Serial Numbers" +msgstr "ล็อตและหมายเลขซีเรียล" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:94 +msgid "Lots & Serial Numbers, Expiration Date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:95 +msgid "Storage Locations, Multi-Step Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 +msgid "Packages" +msgstr "แพ็คเกจ" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:101 +msgid "Lots and serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:103 +msgid "" +"Lots and serial numbers differentiate identical products and track " +"information like arrival or expiration dates. To enable this feature, " +"navigate to :menuselection:`Inventory --> Configuration --> Settings`. Under" +" the :guilabel:`Traceability` heading, check the box beside :guilabel:`Lots " +"& Serial Numbers` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:112 +msgid "" +"Next, ensure the intended product is tracked by lots or serial numbers by " +"navigating to the product form through :menuselection:`Inventory --> " +"Products --> Products`, and selecting the desired product. On the product " +"form, switch to the :guilabel:`Inventory` tab, and under the " +":guilabel:`Tracking` field, select either the :guilabel:`By Unique Serial " +"Number` or :guilabel:`By Lots` options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:118 +msgid "" +"After enabling the features, assign lot or serial numbers to products using " +"an :doc:`inventory adjustment <../inventory_management/count_products>` or " +"during :ref:`product reception <inventory/product_management/receipt-lots>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:123 +msgid "Locations and routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:125 +msgid "" +"**Storage locations** and **multi-step routes** are necessary features for " +"setting **all** types of removal strategies on a location. However, these " +"features are specifically required for the closest location removal strategy" +" since it is only applied at the location level." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:129 +msgid "" +"To activate these features, navigate to :menuselection:`Inventory --> " +"Configuration --> Settings`. Under the :guilabel:`Warehouse` heading, enable" +" the :guilabel:`Storage Location` and :guilabel:`Multi-Step Routes` " +"features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable the locations and route features." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:142 +msgid "" +"Enable the **expiration date** feature to track expiration dates, best " +"before dates, removal dates, and alert dates on a lot or serial number by " +"navigating to :menuselection:`Inventory --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:146 +msgid "" +"Under the :guilabel:`Traceability` heading, ensure the :guilabel:`Lots & " +"Serial Numbers` feature is selected, and then select the check box for " +":guilabel:`Expiration Dates` to enable the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable expiration dates feature for FEFO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:158 +msgid "" +"The *packages* feature is used to group products together and is required " +"for the least packages removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:161 +msgid "" +"Navigate to :menuselection:`Inventory --> Configuration --> Settings` and " +"select the check box for the :guilabel:`Packages` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst-1 +msgid "Enable the packages feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:170 +msgid "" +":doc:`2-step delivery " +"<../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/removal.rst:171 +msgid "" +":doc:`3-step delivery " +"<../../shipping_receiving/daily_operations/delivery_three_steps>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:3 +msgid "Sell stock from multiple warehouses using virtual locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:5 +msgid "" +"While keeping stock and selling inventory from one warehouse might work for " +"smaller companies, bigger companies might need to keep stock in, or sell " +"from, multiple warehouses in multiple locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:9 +msgid "" +"In Odoo, sometimes products included in a single sales order might take " +"stock from two (or more) warehouses. In Odoo, pulling products from multiple" +" warehouses to satisfy sales demands can be done by using *virtual " +"locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:14 +msgid "" +"In order to create virtual locations in warehouses and proceed to the " +"following steps, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step" +" Routes` features will need to be enabled in the :menuselection:`Settings` " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:18 +msgid "" +"To do so, go to :menuselection:`Inventory --> Configuration --> Settings`, " +"scroll down to the :guilabel:`Warehouse` section, and click the checkboxes " +"next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`. " +"Then, :guilabel:`Save` the changes to finish." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:23 +msgid "Create and configure a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:25 +msgid "" +"Before creating any virtual stock locations, a new warehouse will need to be" +" created. This new warehouse will act as a *virtual* warehouse, and will be " +"the *parent* location of other physical warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:31 +msgid "" +"Virtual warehouses are great for companies with multiple physical " +"warehouses. This is because a situation might arise when one warehouse runs " +"out of stock of a particular product, but another warehouse still has stock " +"on-hand. In this case, stock from these two (or more) warehouses could be " +"used to fulfill a single sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:36 +msgid "" +"The \"virtual\" warehouse acts as a single aggregator of all the inventory " +"stored in a company's physical warehouses, and is used (for traceability " +"purposes) to create a hierarchy of locations in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:58 +msgid "Create a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:43 +msgid "" +"To create a new warehouse, go to :menuselection:`Inventory --> Configuration" +" --> Warehouses`, and click :guilabel:`Create`. From here, the warehouse " +":guilabel:`Name` and :guilabel:`Short Name` can be changed, and other " +"warehouse details can be changed under the :guilabel:`Warehouse " +"Configuration` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:48 +msgid "" +"Under the :guilabel:`Shipments` heading, set the number of steps used to " +"process :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` by" +" selecting between the :guilabel:`1 step`, :guilabel:`2 steps`, and " +":guilabel:`3 steps` radio buttons. The desired option for " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` will " +"depend on the warehouse's procurement process, and might differ for " +"individual products or product categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:55 +msgid "" +":doc:`How to choose the right flow to handle receipts and deliveries? " +"</applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:58 +msgid "" +"Under the :guilabel:`Resupply` heading, configure the method(s) for how the " +"warehouse resupplies its inventory:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:61 +msgid "" +":guilabel:`Resupply Subcontractors`: resupply subcontractors with components" +" from this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:62 +msgid "" +":guilabel:`Manufacture to Resupply`: when products are manufactured, they " +"can be manufactured in this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:64 +msgid "" +":guilabel:`Manufacture`: to produce right away, move the components to the " +"production location directly and start the manufacturing process; to pick " +"first and then produce, unload the components from the stock to input " +"location first, and then transfer it to the production location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:68 +msgid "" +":guilabel:`Buy to Resupply`: when products are bought, they can be delivered" +" to this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:69 +msgid "" +":guilabel:`Resupply From`: automatically create routes to resupply this " +"warehouse from another chosen warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:73 +msgid "" +"*Routes* can be set and configured directly from the :guilabel:`Warehouse` " +"form, by clicking on the :guilabel:`Routes` smart button. Once the warehouse" +" is configured, virtual *Locations* can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "The edit screen for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:81 +msgid "" +"In order to apply this virtual warehouse as the *parent* location of two " +"*child* location warehouses, there need to be two warehouses configured with" +" physical stock locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid "**Parent Warehouse**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouse`: `Virtual Warehouse`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Location`: `VWH`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid "**Child Warehouses**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Warehouses`: `Warehouse A` and `Warehouse B`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:0 +msgid ":guilabel:`Locations`: `WHA/Stock` and `WHB/Stock`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:95 +msgid "Create a virtual parent location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:98 +msgid "" +"In order to take stock from multiple warehouses to fulfill a sales order, " +"there need to be at least **two** warehouses acting as *child locations* of " +"the *virtual parent location* warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:101 +msgid "" +"To create and edit *Locations*, go to :menuselection:`Inventory --> " +"Configuration --> Locations`. All :guilabel:`Locations` are listed here, " +"including the *Stock* :guilabel:`Location` of the virtual warehouse that was" +" created. Click into the *Stock* :guilabel:`Location` for the virtual " +"warehouse that was previously created (:dfn:`Warehouse Name/Stock`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:106 +msgid "" +"Then, under the :guilabel:`Additional Information` section, change the " +":guilabel:`Location Type` from :guilabel:`Internal Location` to " +":guilabel:`View`. :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:109 +msgid "" +"This identifies this :guilabel:`Location` as a *virtual location*, which is " +"used to create a hierarchical structure for a warehouse and aggregate its " +"*child locations*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:113 +msgid "" +"Products can *not* be stored in a :guilabel:`View` :guilabel:`Location " +"Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Warehouse location types in location creation screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:120 +msgid "Configure physical warehouse locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:122 +msgid "" +"Navigate back to the :guilabel:`Locations` overview (via the breadcrumbs), " +"and remove any filters in the :guilabel:`Search Bar`. Then, click into the " +"first physical warehouse :guilabel:`Location` that was previously created to" +" be a *child location*, and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:126 +msgid "" +"Under :guilabel:`Parent Location`, select the virtual warehouse from the " +"drop-down menu, and :guilabel:`Save` changes. Then, navigate back to the " +":guilabel:`Locations` overview, and repeat this step for the second physical" +" warehouse stock location. Be sure to :guilabel:`Save` changes again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:130 +msgid "" +"Both locations are now *child locations* of the virtual warehouse *parent " +"location*. This allows stock to be taken from multiple locations to fulfill " +"a single sales order, if there is not enough stock in any one location " +"(provided they are both tied to the same virtual warehouse *parent " +"location*)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:136 +msgid "Example flow: Sell a product from a virtual warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:139 +msgid "" +"To sell products from multiple warehouses using a virtual *parent* location " +"in this flow, there must be at least **two** products and at least **two** " +"warehouses configured - with at least **one** product with quantity on-hand " +"in each warehouse, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:143 +msgid "" +"To create a new request for quotation, or RFQ, navigate to the " +":menuselection:`Sales` app, and click :guilabel:`Create` from the " +":guilabel:`Quotations` overview. Fill out the information on the new " +"quotation by adding a :guilabel:`Customer`, and click :guilabel:`Add a " +"product` to add the two products stored in the two warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:148 +msgid "" +"Then, click the :guilabel:`Other Info` tab on the sales order form. Under " +"the :guilabel:`Delivery` section, change the :guilabel:`Warehouse` field " +"value listed to the virtual warehouse that was previously created. Once the " +"warehouse has been changed, click :guilabel:`Confirm` to convert the " +"quotation into a sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:153 +msgid "" +"Now that the quotation has been confirmed as a sales order, click the " +":guilabel:`Delivery` smart button. From the warehouse delivery form, confirm" +" that the :guilabel:`Source Location` value matches the " +":guilabel:`Warehouse` field value from the sales order. Both should list the" +" virtual warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:159 +msgid "" +"The :guilabel:`Source Location` on the warehouse delivery form and the " +":guilabel:`Warehouse` under the :guilabel:`Other Info` tab on the sales " +"order form *must* match in order for the products included in the sales " +"order to be pulled from different warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:163 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Source Location`" +" field on the warehouse delivery form, then click :guilabel:`Edit`, make the" +" change, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:166 +msgid "" +"If the virtual warehouse is not the value in the :guilabel:`Warehouse` field" +" on the sales order, then a new quotation may need to be generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:168 +msgid "" +"If the :guilabel:`Warehouse` field is missing on the sales order form, then " +"the virtual warehouse (and its children warehouses) may not have been set up" +" correctly, in which case, review the documentation above again to make sure" +" all settings/configuration were done properly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Delivery order with matching source and child locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:176 +msgid "" +"Finally, on the warehouse delivery form, under the :guilabel:`Detailed " +"Operations` tab, confirm that the *Locations* values under the " +":guilabel:`From` column for each product matches to the *child locations* " +"that are tied to the virtual *parent location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:181 +msgid "" +"To view which *Locations* the products are coming from on the drop-down " +"menus, click the :guilabel:`internal link (arrow)` icon to expand the " +"*Location* information. If needed, it can be changed from here (granted " +"there is quantity on hand for the product in that location)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:185 +msgid "" +"Once everything has been properly set, click :guilabel:`Validate` and then " +":guilabel:`Apply` to validate the delivery. Then, navigate back to the sales" +" order form (via the breadcrumbs), and click :guilabel:`Create Invoice` to " +"invoice for the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:190 +msgid "" +"To use a virtual *parent* location as the default warehouse for sales " +"orders, each salesperson can have the virtual warehouse assigned to them " +"from the drop-down menu next to :guilabel:`Default Warehouse` on their " +"employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst-1 +msgid "Default warehouse location on employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:3 +msgid "Units of measure, packages, and packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:5 +msgid "" +"In Odoo, there are a variety of ways to specify the amount of products being" +" bought, stocked, and sold. *Units of measure*, *packages*, and *packagings*" +" are all available to streamline inventory flows, allowing for a variety of " +"configurations for products as they enter and leave the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:12 +msgid "Units of measure" +msgstr "หน่วยวัด" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:14 +msgid "" +"A *unit of measure (UoM)* refers to any of the different standards used to " +"measure and handle a quantifiable amount of products, such a units, weight, " +"time, or size. Different :abbr:`UoMs (Units of Measure)` for weight, for " +"example, can be kilos, pounds, ounces, grams, and so on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:18 +msgid "" +"In Odoo, stock management and purchasing from suppliers are streamlined by " +"specifying different :abbr:`UoMs (Units of Measure)` for both buying and " +"selling products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 +msgid "Specify unit of measure for selling a product vs purchasing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:25 +msgid "" +"Once a product has a default :guilabel:`Unit of Measure` and " +":guilabel:`Purchase Unit of Measure` set on the product form, Odoo " +"automatically converts the different units in the product's purchase/sales " +"orders and the corresponding delivery orders/receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:29 +msgid "" +"The only condition is that all of the units have to be in the *same " +"category* (unit, weight, volume, length, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:33 +msgid "On the product form for `Rope`, the following fields are set as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:35 +msgid ":guilabel:`Unit of Measure` in `ft` (feet), and" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:36 +msgid ":guilabel:`Purchase Unit of Measure` in `cm` (centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:38 +msgid "" +"Because the vendor sells rope in `cm`, the purchase :guilabel:`UoM` is used " +"to represent the quantity on the :abbr:`PO (Purchase Order)`, which is also " +"in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Display purchase order for the product, rope, in centimeters." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:45 +msgid "" +"After confirming the :abbr:`PO (Purchase Order)`, the quantity of product " +"(found under the now visible :guilabel:`Demand` column) is converted from " +"the purchase :abbr:`UoM (Unit of Measure)` to the :guilabel:`Unit of " +"Measure`. Then, when the product is received by clicking the " +":guilabel:`Validate` button, the quantity in :guilabel:`Done` is " +"automatically adjusted to match the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:52 +msgid "" +"On the *receipt* for `Rope`, the quantities are automatically converted from" +" `500 cm` that was requested on the purchase order, to `16.40 ft` to match " +"the internal/stock :guilabel:`Unit of Measure` value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Rope quantity is converted from cm to ft during warehouse reception." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:61 +msgid "" +":ref:`Use Different Units of Measure " +"<inventory/management/products/units_of_measure>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:68 +msgid "" +"Packages are a physical container that holds one or several products from a " +"picking, typically used for outgoing deliveries or internal transfers. " +"Packages can be a reusable or disposable (shipping) box, and are **not** " +"specific to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:72 +msgid "" +"Reusable boxes temporarily hold products during a picking to be brought to " +"either a packing or shipping area. Disposable boxes are the actual shipping " +"containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are " +"used to ship the products out to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:76 +msgid "" +"Multiple items in a sales order (SO) can be separated into different " +"packages to accommodate the products. For example, an :abbr:`SO (Sales " +"Order)` that has 20 boxes of pencils and 4 boxes of erasers can be separated" +" into two separate packages, each containing 10 boxes of pencils and 2 boxes" +" of erasers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:82 +msgid "" +"Products do *not* have to be divided equally. Products can be divided into " +"as many packages that are needed to accommodate the :abbr:`SO (Sales " +"Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:85 +msgid "" +"In Odoo, the quantity of products in each package needs to be recorded, so " +"there is a full history for each product, including which package each item " +"is shipped out in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:88 +msgid "" +"To use this method, ensure the :guilabel:`Packages` option is enabled, by " +"navigating to :menuselection:`Inventory app --> Configuration --> Settings " +"--> Operations`. Click the :guilabel:`Packages` check box, and then " +":guilabel:`Save` to activate the feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:92 +msgid "" +"On a delivery order, assign which package to use by clicking on the " +":guilabel:`≣ (Detailed Operations)` icon to the right of each product in the" +" :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst-1 +msgid "Find detailed operations icon to the right on the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:99 +msgid "" +"Clicking the :guilabel:`≣ (Detailed Operations)` icon of a product reveals a" +" pop-up window. In this window, the :guilabel:`Product` name, " +":guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed " +"above the customizable product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:103 +msgid "" +"Here, the warehouse location the product is coming from can be modified, in " +"addition to the :guilabel:`Source Package` and :guilabel:`Destination " +"Package`, which represents what package(s) the product(s) will be packaged " +"into." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:107 +msgid "" +"Click :guilabel:`Add a line` to include each additional package used. Enter " +"the desired amount in the :guilabel:`Done` field to specify the amount of " +"products that will go into the :guilabel:`Destination Package`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:112 +msgid "Multiple packages in a single delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:114 +msgid "" +"Although a :abbr:`DO (Delivery Order)` is typically associated with a single" +" package, orders can be split by clicking the :guilabel:`≣ (Detailed " +"Operations)` icon next to the products on an :abbr:`SO (Sales Order)` line. " +"This opens the :guilabel:`Detailed Operations` window with an editable table" +" to specify which products are intended for which package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:120 +msgid "" +"To package 10 boxes of pencils with 2 boxes of erasers from the same " +":abbr:`SO (Sales Order)`, begin by navigating to the :abbr:`DO (Delivery " +"Order)`. Then, select the :guilabel:`≣ (four horizontal lines)` icon to the " +"right of the product, `Box of Pencils`. Clicking the icon opens the " +":guilabel:`Detailed Operations` window that is used to detail how products, " +"like the 20 `Box of Pencils`, are packaged." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:126 +msgid "" +"Type in `10` under the :guilabel:`Done` field to package 10 products into " +"the :guilabel:`Destination Package`. To specify the destination package, " +"type the name of an existing package (such as `PACK0000006`) under the " +"field, :guilabel:`Destination Package`. If the package does not exist, Odoo " +"displays the :guilabel:`Create` button to create a new package. Click " +":guilabel:`Add a line` to assign the remaining products in another package, " +"`PACK0000007`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "" +"Detailed operations pop-up where the amount of product going in a pack can " +"be specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:136 +msgid "" +"Select :guilabel:`Detailed Operations` on the product line for `Box of " +"Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and " +"`PACK0000007` each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Put in pack button to match the done amount matches the demand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:143 +msgid "" +"Once all the products for each line have been entered, click " +":guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:146 +msgid "" +"The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as " +"products are selected for each package. When the :guilabel:`Done` amount " +"matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button" +" to complete the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:151 +msgid "" +"The :guilabel:`Put In Pack` button is intended to quickly package all " +"products in the :abbr:`DO (Delivery Order)` into one new package. The option" +" to rename the package, or modify its contents, is available in the " +":guilabel:`Detailed Operations` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:155 +msgid "" +"Clicking on the :guilabel:`Packages` smart button in the upper-right corner " +"of the delivery order reveals a separate page, showing all the packages used" +" in that :abbr:`DO (Delivery Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:159 +msgid "Packagings" +msgstr "บรรจุภัณฑ์" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:161 +msgid "" +"*Packaging* is product specific, and refers to a disposable container that " +"holds several units of a specific product. Unlike packages, packagings " +"cannot be reusable, and each specific packaging must be defined on the " +"individual product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:165 +msgid "" +"For example, different packages for cans of soda can be configured as a " +"6-pack, a 12-pack, or a case of 36. Each flavor of soda would need a `6`, " +"`12`, and `36` can packaging configured on the individual product since " +"packagings are product specific, not generic." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:170 +msgid "Set up packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:172 +msgid "" +"To use packagings, ensure the :guilabel:`Product Packagings` feature is " +"enabled. To do that, navigate to :menuselection:`Inventory app --> " +"Configuration --> Settings`. Then, under the :guilabel:`Products` heading, " +"check the box next to :guilabel:`Product Packagings`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:177 +msgid "" +"In Odoo, product packagings are used on sales/purchase orders and inventory " +"transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:179 +msgid "" +"Next, to create packagings, navigate to :menuselection:`Inventory app --> " +"Products --> Products` and click on the desired product, then click " +":guilabel:`Edit` on the product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:182 +msgid "" +"Under the :guilabel:`Inventory` tab, scroll down to the " +":guilabel:`Packaging` section, and click :guilabel:`Add a line`. Then, a " +"pop-up window appears, in which the following information for each packaging" +" should be entered:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:186 +msgid "" +":guilabel:`Packaging`: name of packaging that appears on sales/purchase " +"orders as a packaging option for the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:188 +msgid ":guilabel:`Contained quantity`: amount of product in the packaging" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:189 +msgid "" +":guilabel:`Barcode`: identifier used with the :ref:`Barcode app " +"<barcode/operations/intro>` to trace the packaging of a product during stock" +" moves or pickings. Leave blank if not in use" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:191 +msgid "" +":guilabel:`Company`: indicates the packaging is only available at the " +"selected company. Leave blank to make the packaging available across all " +"companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:195 +msgid "" +"Create a packaging type for 6 cans of the product, `Grape Soda`, by naming " +"the :guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained " +"quantity` to `6` in the pop-up window that appears after clicking on " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Create 6-pack case for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:203 +msgid "" +"When all the necessary information has been entered, either click " +":guilabel:`Save & Close` to save the packaging and return to the product " +"detail form, or :guilabel:`Save & New` to save the packaging and create " +"another one in a fresh pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:208 +msgid "" +"View all product packagings in the :guilabel:`Inventory` tab of the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "" +"Show packaging and contained quantities, specified on the product page form in the\n" +"Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:216 +msgid "View all packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:218 +msgid "" +"To view all packagings that have been created, go to " +":menuselection:`Inventory app --> Configuration --> Product Packagings`. " +"Doing so reveals the :guilabel:`Product Packagings` page with a complete " +"list of all packagings that have been created for all products. Create new " +"packagings by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:224 +msgid "" +"Two soda products, `Grape Soda` and `Diet Coke`, have three types of " +"packaging configured. On the :guilabel:`Product Packagings` page, each " +"product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 " +"products, or a `Case` of 32 products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "List of different packagings for products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:233 +msgid "Apply packagings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:235 +msgid "" +"When creating a sales order in the :menuselection:`Sales` app, specify the " +"packagings that should be used for the product(s). The chosen packaging is " +"displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` " +"field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:240 +msgid "" +"18 cans of the product, `Grape Soda`, is packed using three 6-pack " +"packagings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 +msgid "Assign packagings on the Sales Order Line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:247 +msgid "" +"Packaging can be used in conjunction with Odoo :ref:`Barcode " +"<inventory/barcode/software>`. When receiving products from suppliers, " +"scanning the packaging barcode automatically adds the number of units in the" +" packaging to the internal count of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 +msgid "Process wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:5 +msgid "" +"While a batch transfer is a group of several pickings, a **wave transfer** " +"only contains some parts of different pickings. Both methods are used to " +"pick orders in a warehouse, and depending on the situation, one method may " +"be a better fit than the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:9 +msgid "" +"To handle orders of a specific product category, or fetch products that are " +"at the same location, wave transfers are the ideal method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:12 +msgid "" +"In Odoo, wave transfers are actually batch transfers with an extra step: " +"transfers are split before being grouped in a batch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:18 +msgid "" +"Before a wave transfer can be created, the :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers` options must be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:21 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings`. In " +"the :guilabel:`Operations` section, enable :guilabel:`Batch Transfers` and " +":guilabel:`Wave Transfers`. Then, click :guilabel:`Save` to apply the " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "" +"View of Odoo Inventory app settings to enable the wave transfers option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:30 +msgid "Add products to a wave" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:32 +msgid "" +"Now that the settings are activated, start a wave transfer by adding " +"products to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:34 +msgid "" +"Wave transfers can only contain product lines from transfers of the same " +"operation type. To view all the transfers and product lines in a specific " +"operation, first go to the :guilabel:`Inventory` dashboard and locate the " +"desired operation type's card. Then, open the options menu (the three dots " +"icon in the corner of the operation type's card) and click " +":guilabel:`Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "How to get an operation type's list of operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:43 +msgid "" +"On the operations page, select the product lines you want to add in a new or" +" existing wave. Then, click :guilabel:`Add to Wave`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst-1 +msgid "Select lines to add to the wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:51 +msgid "" +"Use the :guilabel:`Filters` in the search bar to group lines with the same " +"product, location, carrier, etc..." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:54 +msgid "After that, a pop-up box appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:56 +msgid "" +"To add the selected lines to an existing wave transfer, select the " +":guilabel:`an existing wave transfer` option and select the existing wave " +"transfer from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:59 +msgid "" +"To create a new wave transfer, select the :guilabel:`a new wave transfer` " +"option. If creating a new wave transfer, an employee can also be set in the " +"optional :guilabel:`Responsible` field. Once the desired options are " +"selected, click :guilabel:`Confirm` to add the product lines to a wave." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:64 +msgid "View wave transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:66 +msgid "" +"To view all wave transfers and their statuses, go to " +":menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers" +" can also be viewed in the :guilabel:`Barcode` app by going to " +":menuselection:`Barcode --> Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:5 +msgid "Inventory management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:3 +msgid "Inventory adjustments" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:7 +msgid "" +"In any warehouse management system, the recorded inventory counts in the " +"database might not always match the actual inventory counts in the " +"warehouse. The discrepancy between the two counts can be due to damages, " +"human errors, theft, or other factors. As such, inventory adjustments must " +"be made to reconcile the differences, and ensure that the recorded counts in" +" the database match the actual counts in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:14 +msgid "Inventory Adjustments page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:16 +msgid "" +"To view the *Inventory Adjustments* page, navigate to " +":menuselection:`Inventory app --> Operations --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "In stock products listed on the Inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:23 +msgid "" +"On the :guilabel:`Inventory Adjustments` page, all products that are " +"currently in stock are listed, with each product line containing the " +"following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 +msgid "" +":guilabel:`Location`: the specific location in the warehouse where a product" +" is stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:27 +msgid "" +":guilabel:`Product`: the product whose quantity is listed on the inventory " +"adjustment line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:28 +msgid "" +":guilabel:`Lot/Serial Number`: the tracking identifier assigned to the " +"specific product listed. It can contain letters, numbers, or a combination " +"of both." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:32 +msgid "" +"If a specific product has a quantity of more than `1.00` in stock, and more " +"than one serial number (or lot number) assigned to it, each uniquely-" +"identified product is displayed on its own product line with its own " +"lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:37 +msgid "" +":guilabel:`On Hand Quantity`: the quantity of the product currently recorded" +" in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:38 +msgid "" +":guilabel:`UoM`: the *unit of measure* in which the product is measured. " +"Unless otherwise specified (i.e., in :guilabel:`Pounds` or " +":guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is " +":guilabel:`Units`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:41 +msgid "" +":guilabel:`Counted Quantity`: the real quantity counted during an inventory " +"count. This field is left blank by default, but can be changed, depending on" +" if it matches the :guilabel:`On Hand Quantity` or not." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:44 +msgid "" +":guilabel:`Difference`: the difference between the :guilabel:`On Hand " +"Quantity` and :guilabel:`Counted Quantity`, once an inventory adjustment is " +"made. The difference is automatically calculated after every inventory " +"adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 +msgid "" +":guilabel:`Scheduled Date`: the date at which a count should be made. If not" +" otherwise specified, this date will default to the 31st of December of the " +"current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 +msgid "" +":guilabel:`User`: the person assigned to the count in the database. This can" +" either be the person physically counting the inventory, or applying the " +"count in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:51 +msgid "" +":guilabel:`Product Category`: the category assigned internally to a specific" +" product. Unless otherwise specified (i.e., as :guilabel:`Consumable` or " +":guilabel:`Rental`), the default *Product Category* is set to " +":guilabel:`All`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:54 +msgid "" +":guilabel:`Available Quantity`: the quantity of a specific product that is " +"currently available, based on any outstanding/uncompleted sales orders, " +"purchase orders, or manufacturing orders that might change the available " +"quantity once fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 +msgid "" +":guilabel:`Accounting Date`: the date on which the adjustments will be " +"accounted in the Odoo *Accounting* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:59 +msgid "" +":guilabel:`Company`: the company whose database these inventory adjustments " +"are being made on. The company is listed in the top right corner of the " +"database, next to the user currently logged in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:63 +msgid "" +"Some columns are hidden by default. To reveal these columns, click the " +":guilabel:`additional options` button (three dots icon) to the far right of " +"the form's top row, and select any desired column to reveal by clicking the " +"checkbox next to that option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 +msgid "Create an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:70 +msgid "" +"To create a new inventory adjustment from the :menuselection:`Inventory " +"Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank " +"inventory adjustment line at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:74 +msgid "" +"On this blank inventory adjustment line, click the drop-down menu under the " +":guilabel:`Product` column, and select a product. If the selected product is" +" tracked using either lots or serial numbers, the desired lot or serial " +"number can also be chosen from the drop-down menu under the " +":guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:79 +msgid "" +"Next, set the value in the :guilabel:`Counted Quantity` column to the " +"quantity counted for that product during the inventory adjustment process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:83 +msgid "" +"The :guilabel:`Counted Quantity` for new inventory adjustments is set to " +"`0.00` by default. An inventory move with `0.00` :guilabel:`Quantity Done` " +"is recorded in the product's inventory adjustment history, so it should be " +"set to reflect the actual quantity counted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:87 +msgid "" +"To the right of the :guilabel:`Counted Quantity` column, the " +":guilabel:`Scheduled Date` and :guilabel:`User` can also be changed via " +"their respective drop-down menus. Changing the :guilabel:`Scheduled Date` " +"changes the date that the inventory adjustment should be processed on, and " +"selecting a responsible :guilabel:`User` assigns a user to the specific " +"inventory adjustment (for traceability purposes)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:93 +msgid "" +"Once all changes have been made to the new inventory adjustment line, click " +"away from the line. Doing so saves the adjustment, and moves the line to the" +" top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:158 +msgid "" +"If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand " +"Quantity`, the value in the :guilabel:`Difference` column is **green**. If " +"the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand " +"Quantity`, the value in the :guilabel:`Difference` column is **red**. If the" +" quantities match, and haven't been changed at all, no value appears in the " +":guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Difference column on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:106 +msgid "" +"At this stage, the count (:dfn:`inventory adjustment`) is recorded, but not " +"yet applied. This means that the quantity on hand before the adjustment has " +"not yet been updated to match the new, real counted quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:110 +msgid "" +"There are two ways to apply the new inventory adjustment. The first way is " +"to click the :guilabel:`Apply` button on the line at the far right of the " +"page. The second way is to click the checkbox on the far left of the line. " +"Doing so reveals new button options at the top of the page, one of which is " +"an :guilabel:`Apply` button. Clicking this button instead causes an " +":guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:116 +msgid "" +"From this pop-up menu, a reference or reason can be assigned to the " +"inventory adjustment. By default, the :guilabel:`Inventory Reference / " +"Reason` field is pre-populated with the date the adjustment is being made " +"on, but can be changed to reflect whatever reference or reason is desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:120 +msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Apply all option applies the inventory adjustment once a reason is " +"specified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 +msgid "Count products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 +msgid "" +"Counting products is a recurring activity in a warehouse. Once a count is " +"complete, go to :menuselection:`Inventory app --> Operations --> Inventory " +"Adjustments` to update the :guilabel:`Counted Quantity` column for each " +"product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:133 +msgid "" +"On each product line, identify whether the value in the :guilabel:`On Hand " +"Quantity` column recorded in the database matches the newly-counted value. " +"If the recorded value and the counted value do match, click the " +":guilabel:`Set` button (target icon) at the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:137 +msgid "" +"Doing so copies the value from the :guilabel:`On Hand Quantity` column over " +"to the :guilabel:`Counted Quantity` column, and sets the value of the " +":guilabel:`Difference` column to `0.00`. Subsequently, once applied, an " +"inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the " +"product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Zero count inventory adjustment move." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:146 +msgid "" +"If the newly-counted value for a given product does **not** match the value " +"in the :guilabel:`On Hand Quantity` recorded in the database, instead of " +"clicking the :guilabel:`Set` button, record the real value in the field in " +"the :guilabel:`Counted Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:150 +msgid "" +"To do so, click the field in the :guilabel:`Counted Quantity` column on the " +"specific inventory adjustment line for the product whose count is being " +"changed. This automatically assigns a :guilabel:`Counted Quantity` of " +"`0.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:154 +msgid "" +"To change this value, type in a new value that matches the real, newly-" +"counted value. Then, click away from the line. Doing so saves the " +"adjustment, and automatically adjusts the value in the " +":guilabel:`Difference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:164 +msgid "" +"Subsequently, once applied, a move with the difference between the " +":guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is " +"recorded in the product's inventory adjustment history." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Inventory Adjustments History dashboard detailing a list of prior product " +"moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:172 +msgid "" +"Sometimes a count occurs, but cannot be applied in the database right away. " +"In the time between the actual count and applying the inventory adjustment, " +"product moves can occur. In that case, the on-hand quantity in the database " +"can change and no longer be consistent with the counted quantity. As an " +"extra precaution, Odoo asks for confirmation before applying the inventory " +"adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 +msgid "Change inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 +msgid "" +"By default, the *scheduled date* for inventory adjustments are always " +"scheduled for the 31st of December of the current year. However, for some " +"companies, it is crucial that they have an accurate inventory count at all " +"times. In such cases, the default scheduled date can be modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:185 +msgid "" +"To modify the default scheduled date, go to :menuselection:`Inventory app " +"--> Configuration --> Settings`. Then, in the :guilabel:`Operations` " +"section, locate the :guilabel:`Annual Inventory Day and Month` setting, " +"which includes a drop-down menu that is set to `31 December` by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "" +"Adjust the next inventory count date with the Annual Inventory Day and Month" +" setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:193 +msgid "" +"To change the day, click the :guilabel:`31`, and change it to a day within " +"the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:199 +msgid "" +"Once all desired changes have been made, click :guilabel:`Save` to save all " +"changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 +msgid "Plan big inventory counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 +msgid "" +"To plan big inventory counts, such as a full count of everything currently " +"in stock, first navigate to :menuselection:`Inventory app --> Operations -->" +" Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:207 +msgid "" +"Then, select the desired products to be counted by clicking the checkbox on " +"the far left of each product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:211 +msgid "" +"To request a count of **all** products currently in stock, click the " +"checkbox at the very top of the table, in the header row next to the " +":guilabel:`Location` label. This selects **all** product lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst-1 +msgid "Request a count popup on inventory adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:219 +msgid "" +"Once all desired products have been selected, click the :guilabel:`Request a" +" Count` button at the top of the page. This causes a :guilabel:`Request a " +"Count` pop-up window to appear. From this pop-up, fill in the following " +"information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 +msgid ":guilabel:`Inventory Date`: the planned date of the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +msgid ":guilabel:`User`: the user responsible for the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 +msgid "" +":guilabel:`Accounting Date`: the date at which the inventory adjustment will" +" be accounted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 +msgid "" +":guilabel:`Count`: to leave the on-hand quantity of each product line blank," +" select :guilabel:`Leave Empty`. To prefill the on-hand quantity of each " +"product line with the current value recorded in the database, select " +":guilabel:`Set Current Value`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:230 +msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:233 +msgid "" +"In the Odoo *Barcode* app, users can only view inventory counts that are " +"assigned to **them**, and are scheduled for **today** or **earlier**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:237 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 +msgid "Create a second warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 +msgid "" +"A *warehouse* is a physical building or space where items are stored. In " +"Odoo, it is possible to set up multiple warehouses and transfer stored items" +" between them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:8 +msgid "" +"By default, the Odoo platform has one warehouse that is already configured, " +"with the address set as the company's address. To create a second warehouse," +" select :menuselection:`Configuration --> Warehouses`, then click " +":guilabel:`Create` and configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:12 +msgid ":guilabel:`Warehouse`: the full name of the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 +msgid "" +":guilabel:`Short Name`: the abbreviated code by which the warehouse is " +"referred to; the short name for the default warehouse in Odoo is **WH**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 +msgid "" +":guilabel:`Company`: the company that owns the warehouse; this can be set as" +" the company that owns the Odoo database or the company of a customer or " +"vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:17 +msgid ":guilabel:`Address`: the address where the warehouse is located" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:20 +msgid "" +"The options below will only appear if the :guilabel:`Multi-Step Routes` " +"checkbox is enabled in :menuselection:`Configuration --> Settings` under the" +" :guilabel:`Warehouse` heading. For more information about routes and how " +"they work in Odoo, see :ref:`Using Routes and Pull/Push Rules <use-routes>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 +msgid "" +":guilabel:`Incoming/Outgoing Shipments`: select the routes that incoming and" +" outgoing shipments should follow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:27 +msgid "" +":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied " +"from this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:28 +msgid "" +":guilabel:`Manufacture to Resupply`: allow for items to be manufactured in " +"this warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:29 +msgid "" +":guilabel:`Manufacture`: select the route that should be followed when " +"manufacturing goods inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:31 +msgid "" +":guilabel:`Buy to Resupply`: check the box to allow for purchased products " +"to be delivered to the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:33 +msgid "" +":guilabel:`Resupply From`: select warehouses that can be used to resupply " +"the warehouse being created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "A filled out form for creating a new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:41 +msgid "" +"Creating a second warehouse will automatically enable the *Storage " +"Locations* setting, which allows location tracking of products within a " +"warehouse. To toggle this setting, navigate to :menuselection:`Configuration" +" --> Settings` and click the checkbox under the :guilabel:`Warehouse` " +"heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:46 +msgid "" +"After filling out the form, click :guilabel:`Save` and the new warehouse " +"will be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 +msgid "Add inventory to a new warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:51 +msgid "" +"If a new warehouse is created that has existing inventory in it, the " +"inventory counts should be added to Odoo so that the stock listed in the " +"Odoo database reflects what is in the physical warehouse. To add inventory " +"to a new warehouse, navigate to :menuselection:`Inventory --> Operations -->" +" Inventory Adjustments`, and then click :guilabel:`Create`. The inventory " +"adjustment form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:57 +msgid "" +":guilabel:`Inventory Reference`: the name or code that the inventory " +"adjustment can be referred to by" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 +msgid "" +":guilabel:`Locations`: the location(s) where the inventory is stored; " +"include the new warehouse and any locations within it that inventory will be" +" added to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:61 +msgid "" +":guilabel:`Products`: include all products that will be added to inventory " +"or leave blank to select any product during the next step" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:63 +msgid "" +":guilabel:`Include Exhausted Products`: include products with a quantity of " +"zero; does not affect inventory adjustments for new warehouses since they " +"have no existing inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:65 +msgid "" +":guilabel:`Accounting Date`: the date used by accounting teams for " +"bookkeeping related to the inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:67 +msgid "" +":guilabel:`Company`: the company that owns the inventory; can be set as the " +"user's company or as a customer or vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:69 +msgid "" +":guilabel:`Counted Quantities`: choose whether the counted quantities for " +"products being added should default to stock on hand or zero; does not " +"affect inventory adjustments for new warehouses since they have no existing " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "A filled out form for an inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:77 +msgid "" +"Once the form is properly configured, click on :guilabel:`Start Inventory` " +"to be taken to the next page where products can be added to the inventory " +"adjustment. Add a new product by clicking on :guilabel:`Create` and then " +"fill out the product line as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:81 +msgid ":guilabel:`Product`: the product being added to inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 +msgid "" +":guilabel:`Location`: the location where the product is currently stored in " +"the new warehouse; this can be set as the overall warehouse or a location " +"within the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:84 +msgid "" +":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the " +"serial number used to identify it" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:86 +msgid "" +":guilabel:`On Hand`: the total quantity of the product stored in the " +"location for which inventory is being adjusted; this should be zero for a " +"new location or warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:88 +msgid "" +":guilabel:`Counted`: the amount of the product that is being added to " +"inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:89 +msgid "" +":guilabel:`Difference`: the difference between the *On Hand* and *Counted* " +"values; this will automatically update to reflect the value entered in the " +":guilabel:`Counted` column" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 +msgid ":guilabel:`UoM`: the unit of measure used for counting the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst-1 +msgid "Include a line for each product being added to inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 +msgid "" +"After adding all the products already stored in the new warehouse, click " +":guilabel:`Validate Inventory` to complete the inventory adjustment. The " +"values in the :guilabel:`On Hand` column will update to reflect those in the" +" :guilabel:`Counted` column and the products added will appear in the " +"inventory of the new warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 +msgid "Resupply from another warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:5 +msgid "" +"A common use case for multiple warehouses is to have one central warehouse " +"that resupplies multiple shops, and in this case, each shop is considered a " +"local warehouse. When a shop wants to replenish a product, the product is " +"ordered to the central warehouse. Odoo allows the user to easily set which " +"warehouse(s) can resupply another warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:13 +msgid "" +"To resupply from another warehouse, first go to :menuselection:`Inventory " +"--> Configuration --> Settings --> Warehouse` and activate :guilabel:`Multi-" +"Step Routes`. Then, click :guilabel:`Save` to apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "Enable Multi-Step Routes in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:21 +msgid "" +"View all the configured warehouses by going to :menuselection:`Inventory -->" +" Configuration --> Warehouses`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:24 +msgid "" +"Create a new warehouse by clicking :guilabel:`Create`. Then, give the " +"warehouse a name and a :guilabel:`Short Name`. Finally, click " +":guilabel:`Save` to finish creating the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:27 +msgid "" +"After that, go back to the :guilabel:`Warehouses` page and open the " +"warehouse that will be resupplied by the second warehouse. Then, click " +":guilabel:`Edit`. In the :guilabel:`Warehouse Configuration` tab, locate the" +" :guilabel:`Resupply From` field, and check the box next to the second " +"warehouse's name. If the warehouse can be resupplied by more than one " +"warehouse, make sure to check those warehouses' boxes too. Finally, click " +":guilabel:`Save` to apply the setting. Now, Odoo knows which warehouses can " +"resupply this warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "Supply one warehouse with another in the Warehouse Configuration tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:39 +msgid "Set route on a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:41 +msgid "" +"After configuring which warehouse(s) to resupply from, a new route is now " +"available on all product forms. The new route appears as :guilabel:`Supply " +"Product from [Warehouse Name]` under the :guilabel:`Inventory` tab on a " +"product form. Use the :guilabel:`Supply Product from [Warehouse Name]` route" +" with a reordering rule or the make to order (MTO) route to replenish stock " +"by moving the product from one warehouse to another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "" +"Route setting which enables a product to resupplied from a second warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:51 +msgid "" +"When a product's reordering rule is triggered and the product has the " +":guilabel:`Supply Product from [Warehouse Name]` route set, Odoo " +"automatically creates two pickings. One picking is a *delivery order* from " +"the second warehouse, which contains all the necessary products, and the " +"second picking is a *receipt* with the same products for the main warehouse." +" The product move from the second warehouse to the main warehouse is fully " +"tracked in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:57 +msgid "" +"On the picking/transfer records created by Odoo, the :guilabel:`Source " +"Document` is the product's reordering rule. The location between the " +"delivery order and the receipt is a transit location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "" +"A reordering rule automatically creates two receipts for stock between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "A warehouse order for resupplying one warehouse's stock with another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst-1 +msgid "A receipt for stock received to one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 +msgid "Locations" +msgstr "ตำแหน่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:5 +msgid "" +"A *location* is a specific space within a warehouse. This can be a shelf, " +"room, aisle, etc. There are three types of locations in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 +msgid "" +"*Physical locations* are spaces within a warehouse owned by the user's " +"company. These can be a an area where items are stored like an aisle or " +"shelf, or an area where operations take place, like loading and unloading " +"bays." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 +msgid "" +"*Partner locations* are the same as physical locations except that they " +"exist within the warehouse of a customer or vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:13 +msgid "" +"*Virtual locations* are locations that do not exist physically, but where " +"items that are not in inventory can be placed. These can be items that have " +"not yet entered inventory, like products that are on the way to a warehouse," +" or items that are no longer in inventory due to loss or other factors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:19 +msgid "" +"In order to use locations, the :guilabel:`Storage Locations` setting must be" +" enabled. To do so, navigate to :menuselection:`Inventory --> Configuration " +"--> Settings`, scroll down to the :guilabel:`Warehouse` heading, and enable " +"the :guilabel:`Storage Locations` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:24 +msgid "Create a new location inside a warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 +msgid "" +"Starting from the :menuselection:`Inventory` app, select " +":menuselection:`Configuration --> Locations --> Create`. The new location " +"form can then be configured as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:29 +msgid "" +":guilabel:`Location Name`: the name that will be used to reference the " +"location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:30 +msgid "" +":guilabel:`Parent Location`: the location or warehouse that the new location" +" exists within" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 +msgid "" +":guilabel:`Location Type`: choose the category that the location belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 +msgid "" +":guilabel:`Company`: the company that owns the warehouse that the location " +"is inside of" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 +msgid "" +":guilabel:`Is a Scrap Location?`: check this box to allow for " +"scrapped/damaged goods to be stored in this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 +msgid "" +":guilabel:`Is a Return Location?`: check this box to allow products to be " +"returned to this location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 +msgid ":guilabel:`Barcode`: the barcode number assigned to the location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:38 +msgid "" +":guilabel:`Removal Strategy`: the :doc:`strategy " +"<../advanced_operations_warehouse/removal>` for how items should be taken " +"from inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst-1 +msgid "The form for creating a new location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:48 +msgid "Create location hierarchies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 +msgid "" +"The *Parent Location* setting on the new location form allows for a location" +" to exist within a warehouse or another location. Every location can serve " +"as a parent location, and every parent location can have multiple locations " +"within it, allowing for the creation of a virtually infinite hierarchical " +"structure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:56 +msgid "" +"Location hierarchy could be organized so that a shelf is located within an " +"aisle, which is located within a room, which is located within the overall " +"warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 +msgid "" +"To create the location hierarchy in the example above, set the warehouse as " +"the parent of the room, the room as the parent of the aisle, and the aisle " +"as the parent of the shelf. This can be adapted to a hierarchy of any " +"magnitude." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 +msgid "Routes and Pull/Push Rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 +msgid "" +"In inventory management, the supply chain strategy determines when products " +"should be purchased/manufactured, delivered to distribution centers, and " +"made available to the retail channel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:11 +msgid "" +"In Odoo, a product's supply chain strategy can be configured using *Routes*," +" which feature *Pull and Push Rules*. Once everything is properly " +"configured, the Inventory app can automatically generate transfers following" +" the configured push/pull rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:16 +msgid "Inside the warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:18 +msgid "" +"In a generic warehouse, there are receiving docks, a quality control area, " +"storage locations, picking and packing areas, and shipping docks. All " +"products go through all these locations. As the products move through the " +"locations, each location triggers the products' specified route and rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic warehouse with stock and quality control area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:27 +msgid "" +"In this example, vendor trucks unload pallets of ordered products at the " +"receiving docks. Operators then scan the products in the receiving area. " +"Depending on the product's route and rules, some of these products are sent " +"to a quality control area (for example, products that are components used in" +" the manufacturing process), while others are directly stored in their " +"respective locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic push to rule when receiving products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 +msgid "" +"Here is an example of a fulfillment route. In the morning, items are picked " +"for all the orders that need to be prepared during the day. These items are " +"picked from storage locations and moved to the picking area, close to where " +"the orders are packed. Then, the orders are packed in their respective boxes" +" and conveyors bring them close to the shipping docks, ready to be delivered" +" to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a generic pull from rule when preparing deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:47 +msgid "Pull rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:49 +msgid "" +"With *Pull Rules*, a demand for some products triggers procurements, while " +"*Push Rules* are triggered by products arriving in a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:52 +msgid "" +"Pull Rules are used to fulfill a sales order. Odoo generates a need at the " +"*Customer Location* for each product in the order. Because pull rules are " +"triggered by a need, Odoo looks for a pull rule defined on the *Customer " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:56 +msgid "" +"In this case, a \"delivery order\" pull rule that transfers products from " +"the *Shipping Area* to the *Customer Location* is found, and a transfer " +"between the two locations is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:59 +msgid "" +"Then, Odoo finds another pull rule that tries to fulfill the need for the " +"*Shipping Area*: the \"packing\" rule that transfers products from the " +"*Packing Area* to the *Shipping Area*. Finally, other pull rules are " +"triggered until a transfer between the *Stock* and the *Picking Area* is " +"created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:65 +msgid "" +"All these product transfers are automatically generated by Odoo based on the" +" pull rules, starting from the end (the customer location) and going " +"backward (the stock warehouse). While working, the operator processes these " +"transfers in the opposite order: first the picking, then the packing, and " +"finally the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:71 +msgid "Push rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:73 +msgid "" +"On the other hand, *Push Rules* are much easier to understand. Instead of " +"generating documents based on needs, they are triggered in real time when " +"products arrive in a specific location. Push rules basically say: \"when a " +"product arrives at a specific location, move it to another location.\"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:77 +msgid "" +"An example of a push rule would be: when a product arrives in the *Receipt " +"Area*, move it to the *Storage Location*. As different push rules can be " +"applied to different products, the user can assign different storage " +"locations for different products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:81 +msgid "" +"Another push rule could be: when products arrive at a location, move them to" +" the *Quality Control Area*. Then, once the quality check is done, move them" +" to their *Storage Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:85 +msgid "" +"Push rules can only be triggered if there are no pull rules that have " +"already generated the product transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:89 +msgid "" +"Sets of push/pull rules like those are called *Routes*. The grouping on the " +"rule decides if products are grouped in the same transfer or not. For " +"example, during the picking operation, all orders and their products are " +"grouped in one transfer, whereas the packing operation respects the grouping" +" per customer order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:97 +msgid "Use routes and rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:99 +msgid "" +"Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you " +"manage advanced route configurations such as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 +msgid "Manage product manufacturing chains." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 +msgid "Manage default locations per product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:104 +msgid "" +"Define routes within the stock warehouse according to business needs, such " +"as quality control, after-sales services, or supplier returns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:106 +msgid "" +"Help rental management by generating automated return moves for rented " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:108 +msgid "" +"To configure a route for a product, first, open the :guilabel:`Inventory` " +"application and go to :menuselection:`Configuration --> Settings`. Then, in " +"the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` " +"feature and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "Activate the Multi-Step Routes feature in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:117 +msgid "" +"The :guilabel:`Storage Locations` feature is automatically activated with " +"the :guilabel:`Multi-Step Routes` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:120 +msgid "" +"Once this first step is completed, the user can use pre-configured routes " +"that come with Odoo, or they can create custom routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:124 +msgid "Pre-configured routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:126 +msgid "" +"To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> " +"Configuration --> Warehouses`. Then, open a warehouse form. In the " +":guilabel:`Warehouse Configuration` tab, the user can view the warehouse's " +"pre-configured routes for :guilabel:`Incoming Shipments` and " +":guilabel:`Outgoing Shipments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "A preconfigured warehouse in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:135 +msgid "" +"Some more advanced routes, such as pick-pack-ship, are also available. The " +"user can select the route that best fits their business needs. Once the " +":guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are" +" set, head to :menuselection:`Inventory --> Configuration --> Routes` to see" +" the specific routes that Odoo generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of all the preconfigured routes Odoo offers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:144 +msgid "" +"On the :guilabel:`Routes` page, click on a route to open the route form. In " +"the route form, the user can view which places the route is " +":guilabel:`Applicable On`. The user can also set the route to only apply on " +"a specific :guilabel:`Company`. This is useful for multi-company " +"environments; for example, a user can have a company and warehouse in " +"Country A and a second company and warehouse in Country B." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of a route example applicable on product categories and warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:154 +msgid "" +"At the bottom of the route form, the user can view the specific " +":guilabel:`Rules` for the route. Each :guilabel:`Rule` has an " +":guilabel:`Action`, a :guilabel:`Source Location`, and a " +":guilabel:`Destination Location`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "An example of rules with push & pull actions in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:163 +msgid "Custom Routes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:165 +msgid "" +"To create a custom route, go to :menuselection:`Inventory --> Configuration " +"--> Routes`, and click on :guilabel:`Create`. Next, choose the places where " +"this route can be selected. A route can be applicable on a combination of " +"places." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a pick-pack-ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:173 +msgid "" +"Each place has a different behavior, so it is important to tick only the " +"useful ones and adapt each route accordingly. Then, configure the " +":guilabel:`Rules` of the route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:176 +msgid "" +"If the route is applicable on a product category, the route still needs to " +"be manually set on the product category form by going to " +":menuselection:`Inventory --> Configuration --> Product Categories`. Then, " +"select the product category and open the form. Next, click :guilabel:`Edit` " +"and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:181 +msgid "" +"When applying the route on a product category, all the rules configured in " +"the route are applied to **every** product in the category. This can be " +"helpful if the business uses the dropshipping process for all the products " +"from the same category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a route applied to the \"all\" product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:189 +msgid "" +"The same behavior applies to the warehouses. If the route can apply to " +":guilabel:`Warehouses`, all the transfers occurring inside the chosen " +"warehouse that meet the conditions of the route's rules will then follow " +"that route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the warehouse drop-down menu when selecting applicable on warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:197 +msgid "" +"If the route is applicable on :guilabel:`Sales Order Lines`, it is more or " +"less the opposite. The route must be manually chosen when creating a " +"quotation. This is useful if some products go through different routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:201 +msgid "" +"Remember to toggle the visibility of the :guilabel:`Route` column on the " +"quotation/sales order. Then, the route can be chosen on each line of the " +"quotation/sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the menu allowing to add new lines to sales orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:208 +msgid "" +"Finally, there are routes that can be applied to products. Those work more " +"or less like the product categories: once selected, the route must be " +"manually set on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:211 +msgid "" +"To set a route on a product, go to :menuselection:`Inventory --> Products " +"--> Products` and select the desired product. Then, go to the " +":guilabel:`Inventory` tab and under the :guilabel:`Operations` section, " +"select the :guilabel:`Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of a product form, where the route must be selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:220 +msgid "Rules must be set on the route in order for the route to work." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:223 +msgid "Rules" +msgstr "กฏ" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:225 +msgid "" +"The rules are defined on the route form. First, go to " +":menuselection:`Inventory --> Configuration --> Routes` and open the desired" +" route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` " +"section, click on :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the rules menu, where it is possible to add new rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:233 +msgid "" +"The available rules trigger various actions. If Odoo offers *Push* and " +"*Pull* rules, others are also available. Each rule has an " +":guilabel:`Action`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:236 +msgid "" +":guilabel:`Pull From`: this rule is triggered by a need for the product in a" +" specific location. The need can come from a sales order being validated or " +"from a manufacturing order requiring a specific component. When the need " +"appears in the destination location, Odoo generates a picking to fulfill " +"this need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:240 +msgid "" +":guilabel:`Push To`: this rule is triggered by the arrival of some products " +"in the defined source location. In the case of the user moving products to " +"the source location, Odoo generates a picking to move those products to the " +"destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:243 +msgid "" +":guilabel:`Pull & Push`: this rule allows the generation of pickings in the " +"two situations explained above. This means that when products are required " +"at a specific location, a transfer is created from the previous location to " +"fulfill that need. This creates a need in the previous location and a rule " +"is triggered to fulfill it. Once the second need is fulfilled, the products " +"are pushed to the destination location and all the needs are fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:248 +msgid "" +":guilabel:`Buy`: when products are needed at the destination location, a " +"request for quotation is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:250 +msgid "" +":guilabel:`Manufacture`: when products are needed in the source location, a " +"manufacturing order is created to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"Overview of a \"Pull From\" rule that creates a transfer between the stock and the packing\n" +"zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:258 +msgid "" +"The :guilabel:`Operation Type` must also be defined on the rule. This " +"defines which kind of picking is created from the rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:261 +msgid "" +"If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or " +":guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The " +":guilabel:`Supply Method` defines what happens at the source location:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:265 +msgid "" +":guilabel:`Take From Stock`: the products are taken from the available stock" +" of the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:267 +msgid "" +":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to " +"bring the products to the source location. The available stock is ignored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:269 +msgid "" +":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the " +"products are taken from the available stock of the source location. If there" +" is no stock available, the system tries to find a rule to bring the " +"products to the source location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 +msgid "" +"In the *Scheduling* section, you can determine how Odoo behaves when one of " +"the chain's pickings is rescheduled. In case you decide to **Propagate " +"Rescheduling**, the next move is also to be rescheduled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:277 +msgid "" +"If you prefer having the choice to reschedule the next move, you can decide " +"to receive an alert in the form of a *next activity*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 +msgid "Sample full route flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:283 +msgid "" +"In this example, let's use a custom *Pick - Pack - Ship* route to try a full" +" flow with an advanced custom route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:286 +msgid "" +"First, a quick look at the route's rules and their supply methods. There are" +" three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply " +"Methods` for each rule are the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:289 +msgid "" +":guilabel:`Take From Stock`: When products are needed in the " +":guilabel:`WH/Packing Zone`, *picks* (internal transfers from " +":guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from " +":guilabel:`WH/Stock` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:292 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`WH/Output`, *packs* (internal transfers from " +":guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from " +":guilabel:`WH/Packing Zone` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 +msgid "" +":guilabel:`Trigger Another Rule`: When products are needed in " +":guilabel:`Partner Locations/Customers`, *delivery orders* are created from " +":guilabel:`WH/Output` to fulfill the need." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "Overview of all the transfers created by the pick - pack - ship route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 +msgid "" +"This means that, when a customer orders products that have a *pick - pack - " +"ship* route set on it, a delivery order is created to fulfill the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the operations created by a pull from transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 +msgid "" +"If the source document for multiple tranfers is the same sales order, the " +"status is not the same. The status will be :guilabel:`Waiting Another " +"Operation` if the previous transfer in the list is not done yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the transfers' various statuses at the beginning of the process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:319 +msgid "" +"To prepare the delivery order, packed products are needed at the output " +"area, so an internal transfer is requested from the packing zone." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the packing and " +"output zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:326 +msgid "" +"Obviously, the packing zone needs products ready to be packed. So, an " +"internal transfer is requested to the stock and employees can gather the " +"required products from the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "" +"View of the detailed operations for a transfer between the stock and packing" +" zones." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:333 +msgid "" +"As explained in the introduction of the documentation, the last step in the " +"process (for this route, the delivery order) is the first to be triggered, " +"which then triggers other rules until we reach the first step in the process" +" (here, the internal transfer from the stock to the packing area). Now, " +"everything is ready to be processed so the customer can get the ordered " +"items." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:338 +msgid "" +"In this example, the product is delivered to the customer when all the rules" +" have been triggered and the transfers are done." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst-1 +msgid "View of the transfers' statuses when the route is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:3 +msgid "Transfer products between warehouses using replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:5 +msgid "" +"For companies that use multiple warehouses, it is often necessary to " +"transfer items between them. This is referred to as an *inter-warehouse " +"transfer*. Odoo *Inventory* handles the administrative process of inter-" +"warehouse transfers to ensure that inventory counts remain accurate during " +"and after the transfer. This document will detail the method for conducting " +"an inter-warehouse transfer using replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:12 +msgid "Configure warehouses for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:14 +msgid "" +"First, ensure the :guilabel:`Multi-Step Routes` setting is enabled by " +"navigating to :menuselection:`Inventory --> Configuration --> Settings`, and" +" then check the box under the :guilabel:`Warehouse` tab. This will provide " +"additional configuration options when creating a second warehouse that are " +"needed for inter-warehouse replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:19 +msgid "" +"By default, Odoo comes with a main warehouse already configured. If an " +"additional warehouse has not already been created, do so now from the " +":guilabel:`Inventory` module by selecting :menuselection:`Configuration --> " +"Warehouses --> Create`. Otherwise, select the warehouse that products will " +"be transferred to from the :guilabel:`Warehouses` page and then click " +":guilabel:`Edit` to change its settings. Configure the warehouse as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:25 +msgid "" +":guilabel:`Warehouse`: choose a name that is not already being used for " +"another warehouse (e.g. `Alternative Warehouse`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:27 +msgid "" +":guilabel:`Short Name`: choose a short name by which the warehouse will be " +"identified (e.g. `ALT_WH`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:30 +msgid "" +"Click :guilabel:`Save` and the new warehouse will be created. In addition, a" +" new :guilabel:`Resupply From` field will appear on the warehouse's form. " +"Click :guilabel:`Edit` and then check the box next to the warehouse that " +"will be used to resupply the warehouse that is currently being configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "" +"A warehouse settings form configured to allow resupplying between " +"warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:39 +msgid "" +"For the purposes of this demonstration, the warehouse that products are " +"transferred from (outgoing) will be titled \"San Francisco\", and the " +"warehouse that products are transferred to (incoming) will be titled \"San " +"Francisco 2\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:44 +msgid "Configure products for inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:46 +msgid "" +"Products must also be configured properly in order for them to be " +"transferred between warehouses. Navigate to :menuselection:`Inventory --> " +"Products --> Products` and select an existing product or :guilabel:`Create` " +"a new one, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:50 +msgid "" +"Then, on the product form, go to the :guilabel:`Inventory` tab and enable " +"the checkbox for :guilabel:`X: Supply Product from Y`, with *X* being the " +"warehouse receiving the transferred products and *Y* being the warehouse " +"that products are transferred from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "Enable the checkbox to resupply one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:59 +msgid "Replenish one warehouse from another" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:61 +msgid "" +"Starting in the :menuselection:`Inventory` module, select " +":menuselection:`Products --> Products` and then choose the product that will" +" be replenished. Click the :guilabel:`Replenish` button on the top left of " +"the product page and fill out the pop-up form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:65 +msgid "" +":guilabel:`Quantity`: the number of units that will be sent to the warehouse" +" being replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:66 +msgid "" +":guilabel:`Scheduled Date`: the date that the replenishment is scheduled to " +"take place" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:67 +msgid ":guilabel:`Warehouse`: the warehouse that will be replenished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:68 +msgid "" +":guilabel:`Preferred Routes`: select `X: Supply Product from Y`, with *X* " +"being the warehouse to be replenished and *Y* being the warehouse that the " +"product will be transferred from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "The form for replenishing a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:75 +msgid "" +"Click :guilabel:`Confirm` and a delivery order will be created for the " +"outgoing warehouse along with a receipt for the warehouse that will receive " +"the product. Depending on the configuration settings for the outgoing and " +"incoming warehouses, processing delivery orders and receipts will require " +"between one and three steps. This document will detail how to process one-" +"step deliveries and receipts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:82 +msgid "Process the delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:84 +msgid "" +"The first stage of a replenishment order is processing the delivery from the" +" warehouse that the product is being transferred from. On the " +":menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` " +"button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, " +"then the delivery order created for the replenishment. On the delivery order" +" page, click the :guilabel:`Check Availability` button in the top left to " +"reserve the quantity of the product to be transferred. Once the delivery has" +" been dispatched, click the :guilabel:`Validate` button to register the " +"quantities shipped." +msgstr "" +"ขั้นแรกของใบสั่งการเติมสินค้าคือการประมวลผลการจัดส่งจากคลังสินค้าที่มีการโอนย้ายผลิตภัณฑ์มา" +" บนแดชบอร์ด :menuselection:`สินค้าคงคลัง` ให้เลือกปุ่ม :guilabel:`X " +"เพื่อดำเนินการ` บนการ์ด :guilabel:`คำสั่งการจัดส่ง` สำหรับคลังสินค้าขาออก " +"จากนั้นจึงสร้างใบสั่งจัดส่งสำหรับการเติมสินค้า ในหน้าใบสั่งจัดส่ง " +"ให้คลิกปุ่ม :guilabel:`ตรวจสอบความพร้อมจำหน่าย` " +"ที่ด้านซ้ายบนเพื่อจองจำนวนสินค้าที่จะโอน เมื่อจัดส่งแล้ว ให้คลิกปุ่ม " +":guilabel:`ตรวจสอบ` เพื่อลงทะเบียนปริมาณที่จัดส่ง" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "The delivery orders card for the outgoing warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:99 +msgid "" +"Once the goods arrive at the incoming warehouse, the receipt created for " +"that warehouse must be processed as well. Return to the " +":menuselection:`Inventory` dashboard and select the :guilabel:`X to Process`" +" button on the :guilabel:`Receipts` card for the incoming warehouse, then " +"the receipt created for the replenishment. On the receipt page, click the " +":guilabel:`Validate` button in the top left of the page to register the " +"quantities received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:109 +msgid "" +"After processing the receipt, the products transferred will now appear in " +"the inventory of the incoming warehouse. The stock numbers for both " +"warehouses can be viewed by returning to the product page and selecting the " +":guilabel:`X Units On Hand` button at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:114 +msgid "Automate inter-warehouse replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:116 +msgid "" +"Using reordering rules, it is possible to automate the process of " +"replenishing one warehouse from another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:119 +msgid "" +"To get started, navigate to :menuselection:`Inventory --> Products --> " +"Products`, and then choose the product that will be replenished. From the " +"product page, select the :guilabel:`Reordering Rules` smart button at the " +"top of the form, and then on the next page, click :guilabel:`Create` to " +"configure the form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:124 +msgid "" +":guilabel:`Location`: the location that the reordering rule will replenish " +"when triggered, in this case, the incoming warehouse" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:126 +msgid "" +":guilabel:`Min Quantity`: when the quantity on hand at the incoming " +"warehouse falls below this number, the reordering rule will be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:128 +msgid "" +":guilabel:`Max Quantity`: when the reordering rule is triggered, the product" +" will be replenished at the incoming warehouse up to this quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:130 +msgid "" +":guilabel:`Multiple Quantity`: specify if the product should be replenished " +"in batches of a certain quantity; for example, a product could be " +"replenished in batches of 20" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:132 +msgid "" +":guilabel:`UoM`: the unit of measure used for reordering the product; this " +"value can simply be `Units`, or a specific unit of measurement for weight, " +"length, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst-1 +msgid "A fully configured reordering rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:139 +msgid "" +"Finish by clicking :guilabel:`Save` and the reordering rule will be created." +" Now, when the scheduler runs automatically each day, a transfer will be " +"created for each reordering rule that has been triggered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:144 +msgid "" +"To manually trigger reordering rules, start from the " +":menuselection:`Inventory` module and select :menuselection:`Operation --> " +"Run Scheduler`, then click the green :guilabel:`Run Scheduler` button in the" +" pop-up that appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:148 +msgid "" +"After the scheduler runs, a delivery order and receipt will be created for " +"the outgoing and incoming warehouses, respectively. Both the delivery order " +"and receipt should be processed using the same method as detailed above." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:3 +msgid "Manage Warehouses and Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:9 +msgid "Warehouse" +msgstr "โกดังสินค้า" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:11 +msgid "" +"In Odoo, a **Warehouse** is the actual building/place in which a company's " +"items are stocked. Multiple warehouses can be set up in Odoo and the user " +"can create moves between warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:19 +msgid "" +"A **Location** is a specific space within the warehouse. It can be a " +"sublocation of the warehouse (a shelf, a floor, an aisle, and so on). " +"Therefore, a location is part of one warehouse only and it is not possible " +"to link one location to multiple warehouses. In Odoo, as many locations can " +"be configured as needed under one warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:24 +msgid "There are three types of locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:26 +msgid "" +"The **Physical Locations** are internal locations that are part of the " +"warehouses that the company owns. They can be the loading and unloading " +"areas of the warehouse, a shelf, a department, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:30 +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 they are not owned by the user's company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:34 +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 recording lost products (**Inventory " +"Loss**), or accounting for products that are on their way to the warehouse " +"(**Procurements**)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:39 +msgid "" +"In Odoo, locations are structured hierarchically. Locations can be " +"structured as a tree, dependent on a parent-child relationship. This gives " +"more detailed levels of analysis of the stock operations and the " +"organization of the warehouses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 +msgid "" +"To activate locations, go to :menuselection:`Configuration --> Settings` and" +" enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Enable the storage location feature in Odoo Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:54 +msgid "" +"To manage several routes within the warehouses, also enable " +":guilabel:`Multi-Step Routes` and check " +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:60 +msgid "" +"To create a warehouse, go to :menuselection:`Configuration --> Warehouse " +"Management --> Warehouses` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:63 +msgid "" +"Then, fill out a :guilabel:`Warehouse Name` and a :guilabel:`Short Name`. " +"The short name is five characters maximum." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Short name field of a warehouse on Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:71 +msgid "" +"The :guilabel:`Short Name` appears on transfer orders and other warehouse " +"documents. Odoo recommends using an understandable one like \"WH/[first " +"letters of location]\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:74 +msgid "" +"Now, go back to the :guilabel:`Inventory` dashboard. There, new operations " +"related to the newly created warehouse have been automatically generated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "" +"Inventory app dashboard displaying new transfer types for the recently " +"created warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:82 +msgid "" +"Adding a second warehouse will automatically activate the " +":guilabel:`Locations` setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:85 +msgid "Create a new location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:87 +msgid "" +"To create a location, go to :menuselection:`Configuration --> Warehouse " +"Management --> Locations` and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:90 +msgid "" +"Then, fill out a :guilabel:`Location Name` and a :guilabel:`Parent Location`" +" and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst-1 +msgid "Create a new warehouse location in Odoo Inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 +msgid "Inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:3 +msgid "Integrating additional costs to products (landed costs)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:7 +msgid "" +"The landed cost feature in Odoo allows the user to include additional costs " +"(shipment, insurance, customs duties, etc.) into the cost of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:13 +msgid "" +"First, go to :menuselection:`Inventory --> Configuration --> Settings --> " +"Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also " +"gives the option to set a :guilabel:`Default Journal` in which the landed " +"costs accounting entries will be recorded." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Activate the landed cost feature in Inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:22 +msgid "Add costs to products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:25 +msgid "Receive the vendor bill" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:27 +msgid "" +"After a vendor fulfills a purchase order and sends a bill, click " +":guilabel:`Create Bill` on the purchase order to create a vendor bill in " +"Odoo. If the vendor bill includes landed costs, such as custom duties, tick " +"the box in the :guilabel:`Landed Costs` column on the vendor bill invoice " +"line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Enable Landed Costs option on vendor bill line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:35 +msgid "" +"For charges that are always landed costs, create a landed cost product in " +"Odoo. That way, the landed cost product can be quickly added to the vendor " +"bill as an invoice line instead of manually entering the landed cost " +"information every time a vendor bill comes in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:39 +msgid "" +"First, create a new product in :menuselection:`Inventory --> Products --> " +"Products --> Create`. Next, name the landed cost product. Then, set the " +":guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must " +"always be a service product type. After that, go to the :guilabel:`Purchase`" +" tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click " +":guilabel:`Save` to finish creating the landed cost product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:45 +msgid "" +"If this product is always a landed cost, you can also define it on the " +"product and avoid having to tick the box on each vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Option to define a product as a landed cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:52 +msgid "" +"Once the landed cost is added to the vendor bill (either by checking the " +":guilabel:`Landed Cost` option on the invoice line or adding a landed cost " +"product to the bill), click the :guilabel:`Create Landed Costs` button at " +"the top of the bill. Odoo automatically creates a landed cost record with " +"the set landed cost pre-filled in the :guilabel:`Additional Costs` product " +"lines. From here, decide which picking the additional costs apply to by " +"clicking :guilabel:`Edit` and selecting the picking reference number from " +"the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." +msgstr "" +"เมื่อเพิ่มต้นทุนที่ดินลงในใบเรียกเก็บเงินของผู้ขาย " +"(โดยทำเครื่องหมายที่ตัวเลือก :guilabel:`ต้นทุนแฝง` ในบรรทัดใบแจ้งหนี้ " +"หรือเพิ่มผลิตภัณฑ์ต้นทุนที่ดินลงในใบเรียกเก็บเงิน) ให้คลิกปุ่ม " +":guilabel:`สร้างต้นทุนแฝง` ที่ ด้านบนของใบเรียกเก็บเงิน Odoo " +"จะสร้างบันทึกต้นทุนแฝงโดยอัตโนมัติโดยกรอกต้นทุนแฝงที่กำหนดไว้ล่วงหน้าในกลุ่มผลิตภัณฑ์" +" :guilabel:`ค่าใช้จ่ายเพิ่มเติม` จากที่นี่ " +"ตัดสินใจว่าจะใช้ค่าใช้จ่ายเพิ่มเติมในการเลือกใดโดยคลิก :guilabel:`แก้ไข` " +"และเลือกหมายเลขอ้างอิงในการเลือกจากเมนูแบบเลื่อนลง :guilabel:`โอนย้าย` " +"สุดท้าย คลิก :guilabel:`บันทึก`" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "" +"Use a warehouse transfer to cover a landed cost in the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:64 +msgid "" +"After setting the picking, click :guilabel:`Compute` on the landed cost " +"record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the " +"impact of the landed costs. Finally, click :guilabel:`Validate` to post the " +"landed cost entry to the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:68 +msgid "" +"The user can access the journal entry that has been created by the landed " +"cost by clicking on the :guilabel:`Journal Entry`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:72 +msgid "" +"The product that the landed cost is applied to must have a product category " +"set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average " +"Costing)` method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst-1 +msgid "Landed cost journal entry" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 +msgid "" +"Landed cost records can also be directly created in " +":menuselection:`Inventory --> Operations --> Landed Costs`, it is not " +"necessary to create a landed cost record from the vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:3 +msgid "Inventory valuation configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:7 +msgid "" +"All of a company's stock on-hand contributes to the valuation of its " +"inventory. That value should be reflected in the company's accounting " +"records to accurately show the value of the company and all of its assets." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:11 +msgid "" +"By default, Odoo uses a periodic inventory valuation (also known as manual " +"inventory valuation). This method implies that the accounting team posts " +"journal entries based on the physical inventory of the company, and that " +"warehouse employees take the time to count the stock. In Odoo, this method " +"is reflected inside each product category, where the :guilabel:`Costing " +"Method` field will be set to `Standard Price` by default, and the " +":guilabel:`Inventory Valuation` field will be set to `Manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst-1 +msgid "" +"The Inventory Valuation fields are located on the Product Categories form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:22 +msgid "" +"Alternatively, automated inventory valuation is an integrated valuation " +"method that updates the inventory value in real-time by creating journal " +"entries whenever there are stock moves initiated between locations in a " +"company's inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:27 +msgid "" +"Automated inventory valuation is a method recommended for expert " +"accountants, given the extra steps involved in journal entry configuration. " +"Even after the initial setup, the method will need to be periodically " +"checked to ensure accuracy, and adjustments may be needed on an ongoing " +"basis depending on the needs and priorities of the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:35 +msgid "Types of accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:37 +msgid "" +"Accounting entries will depend on the accounting mode: *Continental* or " +"*Anglo-Saxon*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 +msgid "" +"Verify the accounting mode by activating the :ref:`developer-mode` and " +"navigating to :menuselection:`Accounting --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:43 +msgid "" +"In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported " +"when products are sold or delivered. This means that the cost of a good is " +"only recorded as an expense when a customer is invoiced for a product. " +"*Interim Stock Accounts* are used for the input and output accounts, and are" +" both *Asset Accounts* in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:48 +msgid "" +"In *Continental* accounting, the cost of a good is reported as soon as a " +"product is received into stock. Additionally, a single *Expense* account is " +"used for both input and output accounts in the balance sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:55 +msgid "Costing methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:57 +msgid "" +"Below are the three costing methods that can be used in Odoo for inventory " +"valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 +msgid "" +"**Standard Price**: is the default costing method in Odoo. The cost of the " +"product is manually defined on the product form, and this cost is used to " +"compute the valuation. Even if the purchase price on a purchase order " +"differs, the valuation will still use the cost defined on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:63 +msgid "" +"**Average Cost (AVCO)**: calculates the valuation of a product based on the " +"average cost of that product, divided by the total number of available stock" +" on-hand. With this costing method, inventory valuation is *dynamic*, and " +"constantly adjusts based on the purchase price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 +msgid "" +"**First In First Out (FIFO)**: tracks the costs of incoming and outgoing " +"items in real-time and uses the real price of the products to change the " +"valuation. The oldest purchase price is used as the cost for the next good " +"sold until an entire lot of that product is sold. When the next inventory " +"lot moves up in the queue, an updated product cost is used based on the " +"valuation of that specific lot. This method is arguably the most accurate " +"inventory valuation method for a variety of reasons, however, it's highly " +"sensitive to input data and human error." +msgstr "" +"**เข้าก่อนออกก่อน (FIFO)**: ติดตามต้นทุนของสินค้าเข้าและออกแบบเรียลไทม์ " +"และใช้ราคาจริงของผลิตภัณฑ์เพื่อเปลี่ยนแปลงการประเมินราคา " +"ราคาซื้อที่เก่าที่สุดจะถูกใช้เป็นต้นทุนสำหรับสินค้าที่ขายถัดไปจนกว่าจะขายผลิตภัณฑ์นั้นหมดทั้งล็อต" +" เมื่อล็อตสินค้าคงคลังถัดไปเลื่อนขึ้นในคิว " +"ต้นทุนผลิตภัณฑ์ที่อัปเดตจะถูกใช้ตามการประเมินมูลค่าของล็อตเฉพาะนั้น " +"วิธีการนี้ถือเป็นวิธีการประเมินมูลค่าสินค้าคงคลังที่แม่นยำที่สุดด้วยเหตุผลหลายด้าน" +" วิธีการนี้มีความอ่อนไหวสูงต่อการป้อนข้อมูลและข้อผิดพลาดจากมนุษย์" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:74 +msgid "" +"Changing the costing method greatly impacts inventory valuation. It's highly" +" recommended to consult an accountant first before making any adjustments " +"here." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 +msgid "Configure automated inventory valuation in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:80 +msgid "" +"Make changes to inventory valuation options by navigating to " +":menuselection:`Inventory --> Configuration --> Product Categories`, and " +"choose the category/categories where the automated valuation method should " +"apply." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:85 +msgid "" +"It is possible to use different valuation settings for different product " +"categories." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:87 +msgid "" +"Under the :guilabel:`Inventory Valuation` heading are two labels: " +":guilabel:`Costing Method` and :guilabel:`Inventory Valuation`. Pick the " +"desired :guilabel:`Costing Method` using the drop-down menu (e.g. " +":guilabel:`Standard`, :guilabel:`Average Cost (AVCO)`, or :guilabel:`First " +"In First Out (FIFO)`) and switch the :guilabel:`Inventory Valuation` to " +":guilabel:`Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:93 +msgid "" +":ref:`Using the inventory " +"valuation<inventory/reporting/using_inventory_val>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +msgid "" +"When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing " +"Method`, changing the numerical value in the :guilabel:`Cost` field for " +"products in the respective product category creates a new record in the " +"*Inventory Valuation* report to adjust the value of the product. The " +":guilabel:`Cost` amount will then automatically update based on the average " +"purchase price both of inventory on hand and the costs accumulated from " +"validated purchase orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 +msgid "" +"When the :guilabel:`Costing Method` is changed, products already in stock " +"that were using the :guilabel:`Standard` costing method **do not** change " +"value; rather, the existing units keep their value, and any product moves " +"from then on affect the average cost, and the cost of the product will " +"change. If the value in the :guilabel:`Cost` field on a product form is " +"changed manually, Odoo will generate a corresponding record in the " +"*Inventory Valuation* report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 +msgid "" +"On the same screen, the :guilabel:`Account Stock Properties` fields will " +"appear, as they are now required fields given the change to automated " +"inventory valuation. These accounts are defined as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:112 +msgid "" +":guilabel:`Stock Valuation Account`: when automated inventory valuation is " +"enabled on a product, this account will hold the current value of the " +"products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 +msgid "" +":guilabel:`Stock Input Account`: counterpart journal items for all incoming " +"stock moves will be posted in this account, unless there is a specific " +"valuation account set on the source location. This is the default value for " +"all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:118 +msgid "" +":guilabel:`Stock Output Account`: counterpart journal items for all outgoing" +" stock moves will be posted in this account, unless there is a specific " +"valuation account set on the destination location. This is the default value" +" for all products in a given category, and can also be set directly on each " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:124 +msgid "Access reporting data generated by inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:126 +msgid "" +"To start, go to :menuselection:`Accounting --> Reporting --> Balance Sheet`." +" At the top of the dashboard, change the :guilabel:`As of` field value to " +":guilabel:`Today`, and adjust the filtering :guilabel:`Options` to " +":guilabel:`Unfold All` in order to see all of the latest data displayed, all" +" at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +msgid "" +"Under the parent :guilabel:`Current Assets` line item, look for the nested " +":guilabel:`Stock Valuation Account` line item, where the total valuation of " +"all of the inventory on hand is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:135 +msgid "" +"Access more specific information with the :guilabel:`Stock Valuation " +"Account` drop-down menu, by selecting either the :guilabel:`General Ledger` " +"to see an itemized view of all of the journal entries, or by selecting " +":guilabel:`Journal Items` to review all of the individualized journal " +"entries that were submitted to the account. As well, annotations to the " +":guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, " +"filling in the text box, and clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst-1 +msgid "See the full inventory valuation breakdown in Odoo Accounting app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:3 +msgid "Using inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:7 +msgid "" +"*Inventory valuation* is a quintessential accounting procedure that " +"calculates the value of on-hand stock. Once determined, the inventory " +"valuation amount is then incorporated into a company's overall value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:11 +msgid "" +"In Odoo, this process can be conducted manually— by warehouse employees " +"physically counting the products— or automatically through the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:15 +msgid "Automatic inventory valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:17 +msgid "" +"To use Odoo to automatically generate a trail of inventory valuation " +"entries, first navigate to the :menuselection:`Product Categories` list by " +"going to :menuselection:`Inventory app --> Configuration --> Product " +"Categories` and select the desired product category. On the form, set the " +":guilabel:`Inventory Valuation` as :guilabel:`Automated` and the " +":guilabel:`Costing Method` to any of the three options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:24 +msgid "" +":ref:`Set up inventory valuation " +"<inventory/management/inventory_valuation_config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:26 +msgid "" +"In order to understand how moving products in and out of stock affects the " +"company's overall value, consider the following product and stock moves " +"scenario below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:30 +msgid "Receive a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:32 +msgid "" +"To track the value of incoming products, such as a simple *table*, configure" +" the product category on the the product itself. To get there, navigate to " +":menuselection:`Inventory app --> Products --> Products` and click the " +"desired product. On the product form, click the :guilabel:`➡️ (right arrow)`" +" icon beside the :guilabel:`Product Category` field, which opens an internal" +" link to edit the product category. Next, set the :guilabel:`Costing Method`" +" as :guilabel:`First In First Out (FIFO)` and :guilabel:`Inventory " +"Valuation` as :guilabel:`Automated`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:40 +msgid "" +"Alternatively access the :guilabel:`Product Categories` dashboard by " +"navigating to :menuselection:`Inventory app --> Configuration --> Product " +"Categories` and select the desired product category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:44 +msgid "" +"Next, assume 10 tables are purchased at a price of $10.00, each. The " +":abbr:`PO (Purchase Order)` for those tables will show the subtotal of the " +"purchase as $100, plus any additional costs or taxes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Purchase order with 10 tables products valued at $10.00 each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:51 +msgid "" +"After selecting :guilabel:`Validate` on the :abbr:`PO (Purchase Order)`, the" +" :guilabel:`Valuation` smart button is enabled. Clicking on this button " +"displays a report showing how the inventory valuation for the table was " +"affected by this purchase." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:56 +msgid "" +":ref:`Developer mode <developer-mode>` **must** be turned on to see the " +":guilabel:`Valuation` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:60 +msgid "" +"The :doc:`consignment " +"</applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock>`" +" feature allows ownership to items in stock. Thus, products owned by other " +"companies are not accounted for in the host company's inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "See Valuation smart button on a receipt, with Developer mode enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:68 +msgid "" +"For a comprehensive dashboard that includes the inventory valuation of all " +"product shipments, inventory adjustments, and warehouse operations, refer to" +" the :ref:`stock valuation report <inventory/management/reporting/valuation-" +"report>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:73 +msgid "Deliver a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:75 +msgid "" +"In the same logic, when a table is shipped to a customer and leaves the " +"warehouse, the stock valuation decreases. The :guilabel:`Valuation` smart " +"button on the :abbr:`DO (Delivery Order)`, likewise, displays the stock " +"valuation record as it does on a :abbr:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Decreased stock valuation after a product is shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:86 +msgid "Inventory valuation report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:88 +msgid "" +"To view the current value of all products in the warehouse, first turn on " +":ref:`Developer mode <developer-mode>` and navigate to " +":menuselection:`Inventory app --> Reporting --> Valuation`. The " +":guilabel:`Stock Valuation` dashboard displays detailed records of products " +"with the :guilabel:`Date`, :guilabel:`Quantity`, :guilabel:`Unit Value`, and" +" :guilabel:`Total Value` of the inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:95 +msgid "" +":ref:`Developer mode <developer-mode>` **must** be enabled to see the " +":guilabel:`Valuation` option under :guilabel:`Reporting`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Inventory valuation report showing multiple products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:102 +msgid "" +"The :guilabel:`Valuation At Date` button, located in the top-left corner of " +"the :guilabel:`Stock Valuation` page, reveals a pop-up window. In this pop-" +"up, the inventory valuation of products available during a prior specified " +"date can be seen and selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:107 +msgid "" +"View a detailed record of a product's inventory value, stock move, and on-" +"hand stock by selecting the teal :guilabel:`➡️ (right arrow)` button to the " +"right of the :guilabel:`Reference` column value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:112 +msgid "Update product unit price" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:114 +msgid "" +"For any company: lead times, supply chain failures, and other risk factors " +"can contribute to invisible costs. Although Odoo attempts to accurately " +"represent the stock value, *manual valuation* serves as an additional tool " +"to update the unit price of products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:119 +msgid "" +"Manual valuation is intended for products that can be purchased and received" +" for a cost greater than 0, or have product categories set with " +":guilabel:`Costing Method` set as either :guilabel:`Average Cost (AVCO)` or " +":guilabel:`First In First Out (FIFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "Add manual valuation of stock value to a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:127 +msgid "" +"Create manual valuation entries on the :guilabel:`Stock Valuation` dashboard" +" by first navigating to :menuselection:`Inventory app --> Reporting --> " +"Valuation`. Next, to enable the *product revaluation* feature, select " +":menuselection:`Group by --> Product` to organize all the records by " +"product. Click on the gray :guilabel:`▶️ (drop-down triangle)` icon to " +"reveal stock valuation line items below, as well as a teal :guilabel:`➕ " +"(plus)` button on the right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:133 +msgid "" +"Click the teal :guilabel:`+ (plus)` button to open up the :guilabel:`Product" +" Revaluation` form. Here, the inventory valuation for a product can be " +"recalculated, by increasing or decreasing the unit price of each product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:138 +msgid "" +"The :guilabel:`▶️ (drop-down triangle)` and :guilabel:`➕ (plus)` buttons are" +" only visible after grouping entries by product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst-1 +msgid "" +"Product revaluation form adding a value of $1.00 with the reason being " +"inflation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:146 +msgid "Inventory valuation journal entries" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:148 +msgid "" +"In Odoo, automatic inventory valuation records are also recorded in the " +":menuselection:`Accounting app --> Accounting --> Journal Entries` " +"dashboard. On this comprehensive list of accounting entries, inventory " +"valuation records are identified by checking values in the " +":guilabel:`Journal` column, or looking for the :guilabel:`Reference` column " +"value which matches the warehouse operation reference (e.g. `WH/IN/00014` " +"for receipts)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:154 +msgid "" +"Clicking on an inventory valuation journal entry opens a *double-entry " +"accounting* record. These records are generated by Odoo to track the change " +"of value in inventory valuation as products are moved in and out of the " +"warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:159 +msgid "" +"To view the inventory valuation of 10 *tables*, costing $10.00 each, upon " +"reception from the vendor, go to the :menuselection:`Journal Entries` page " +"found in :menuselection:`Accounting app --> Accounting --> Journal Entries`." +" Here, click the journal line where the :guilabel:`Reference` column value " +"matches the reference on the receipt, `WH/IN/00014`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Stock valuation page depicting the products within a shipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:168 +msgid "" +"`Stock interim` is a holding account for money intended to pay vendors for " +"the product. The `stock valuation` account stores the value of all on-hand " +"stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:0 +msgid "Accounting entry for the inventory valuation of 10 tables." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/using_inventory_valuation.rst:176 +msgid "" +"`Odoo Tutorial: Inventory Valuation " +"<https://www.odoo.com/slides/slide/2795/share>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:8 +msgid "Maintenance" +msgstr "บำรุงรักษา" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:10 +msgid "" +"**Odoo Maintenance** helps extend the effectiveness of equipment by keeping " +"track of maintenance requirements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance.rst:14 +msgid "" +"`Odoo Tutorials: Managing Equipment Maintenance " +"<https://www.odoo.com/slides/slide/managing-equipment-maintenance-709>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management.rst:5 +msgid "Equipment management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:3 +msgid "Add new equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:7 +msgid "" +"In Odoo, *equipment* refers to any item that is used in everyday operations," +" including the manufacturing of products. This can mean a piece of machinery" +" on a production line, a tool that is used in different locations, or a " +"computer in an office space. Equipment registered in Odoo can be owned by " +"the company that uses the Odoo database, or by a third party, such as a " +"vendor in the case of equipment rentals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:13 +msgid "" +"Using Odoo *Maintenance*, it is possible to track individual pieces of " +"equipment, along with information about their maintenance requirements. To " +"add a new piece of equipment, navigate to the :guilabel:`Maintenance` " +"module, select :menuselection:`Equipments --> Machines & Tools --> Create`, " +"and configure the equipment as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:18 +msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:19 +msgid "" +":guilabel:`Equipment Category`: the category that the equipment belongs to; " +"for example, computers, machinery, tools, etc.; new categories can be " +"created by navigating to :menuselection:`Configuration --> Equipment " +"Categories` and clicking :guilabel:`Create`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:22 +msgid "" +":guilabel:`Company`: the company that owns the equipment; again, this can be" +" the company that uses the Odoo database, or a third-party company" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:24 +msgid "" +":guilabel:`Used By`: specify if the equipment is used by a specific " +"employee, department, or both; select :guilabel:`Other` to specify both an " +"employee and a department" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:26 +msgid "" +":guilabel:`Maintenance Team`: the team responsible for servicing the " +"equipment; new teams can be created by navigating to " +":menuselection:`Configuration --> Maintenance Teams` and selecting " +":guilabel:`Create`; the members of each team can also be assigned from this " +"page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:29 +msgid "" +":guilabel:`Technician`: the person responsible for servicing the equipment; " +"this can be used to assign a specific individual in the event that no " +"maintenance team is assigned or when a specific member of the assigned team " +"should always be responsible for the equipment; any person added to Odoo as " +"a user can be assigned as a technician" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:33 +msgid "" +":guilabel:`Used in location`: the location where the equipment is used; this" +" is a simple text field that can be used to specify locations that are not " +"work centers, like an office, for example" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:36 +msgid "" +":guilabel:`Work Center`: if the equipment is used at a work center, specify " +"it here; equipment can also be assigned to a work center by navigating to " +":menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a " +"work center or creating a new one using the :guilabel:`Create` button, and " +"clicking the :guilabel:`Equipment` tab on the work center form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "An example of a fully configured new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:46 +msgid "Include additional product information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:48 +msgid "" +"The :guilabel:`Product Information` tab at the bottom of the form can be " +"used to provide further details about the piece of equipment:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:51 +msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:52 +msgid "" +":guilabel:`Vendor Reference`: the reference code assigned to the vendor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:53 +msgid ":guilabel:`Model`: the specific model of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:54 +msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:55 +msgid "" +":guilabel:`Effective Date`: the date that the equipment became available for" +" use; this is used to calculate the :abbr:`MTBF (Mean Time Between " +"Failures)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:57 +msgid ":guilabel:`Cost`: the amount the equipment was purchased for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:58 +msgid "" +":guilabel:`Warranty Expiration Date`: the date on which the equipment's " +"warranty will expire" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "The product information tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:65 +msgid "Add maintenance details" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:67 +msgid "" +"The :guilabel:`Maintenance` tab includes information that can be useful to " +"maintenance teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 +msgid "" +":guilabel:`Preventive Maintenance Frequency`: specifies how often " +"maintenance should be performed to prevent equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:71 +msgid "" +":guilabel:`Maintenance Duration`: the amount of time required to fix the " +"equipment when it fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:72 +msgid "" +":guilabel:`Expected Mean Time Between Failure`: the average amount of time " +"that the equipment is expected to operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst-1 +msgid "The maintenance tab for the new piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:80 +msgid "" +"The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean " +"Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest" +" Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated " +"automatically based on maintenance requests if any exist." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:86 +msgid "" +"To see the maintenance requests for a piece of equipment, go to the page for" +" the equipment and select :guilabel:`Maintenance` in the top right corner of" +" the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 +msgid "Manufacturing" +msgstr "การผลิต" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:10 +msgid "" +"**Odoo Manufacturing** helps manufacturers schedule, plan, and process " +"manufacturing orders. With the work center control panel, put tablets on the" +" shop floor to control work orders in real-time and allow workers to trigger" +" maintenance operations, feedback loops, quality issues, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 +msgid "`Odoo Tutorials: MRP <https://www.odoo.com/slides/mrp-29>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 +msgid "" +"`Odoo Tutorials: Barcode Scanner <https://www.odoo.com/slides/barcode-30>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:17 +msgid ":doc:`IoT Boxes (MES) </applications/productivity/iot>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 +msgid "Manufacturing workflows" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 +msgid "Bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:7 +msgid "" +"A *bill of materials* (or *BoM* for short) is a document that defines the " +"quantity of each component required to make or deliver a finished product. " +"It can also include various operations and the individual step guidelines " +"needed to complete a production process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:11 +msgid "" +"In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be " +"linked to each product, so even product variants can have their own tailored" +" :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:14 +msgid "" +"Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the " +"manufacturing process and save time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 +msgid "Set up a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:20 +msgid "" +"The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations" +" or instructions, only components. In this case, the production is solely " +"managed using *Manufacturing Orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:23 +msgid "" +"To create a :abbr:`BoM (Bill of Materials)` from the " +":guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills " +"of Materials`. Then, click :guilabel:`Create`. Next, specify the " +":guilabel:`Product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:28 +msgid "" +"A :abbr:`BoM (Bill of Materials)` can also be created directly from the " +"product form, in which case the :guilabel:`Product` field is pre-filled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:31 +msgid "" +"For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type`" +" to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line`" +" to specify the various components that make up the production of the final " +"product and their respective quantities. New components can be created " +"quickly through the :abbr:`BoM (Bill of Materials)`, or can be created " +"beforehand in :menuselection:`Manufacturing --> Products --> Products --> " +"Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Set up a Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 +msgid "Specify a bill of materials (BoM) for a product variant" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:45 +msgid "" +":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product " +"Variants*, with two setup options available to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:49 +msgid "" +"In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, " +"the product's variant attributes must already be configured on the product " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:52 +msgid "" +"The first method is to create one :abbr:`BoM (Bill of Materials)` per " +"variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the" +" :guilabel:`Product Variant`. The second method is to create one master " +":abbr:`BoM (Bill of Materials)` that contains all of the components, and " +"specify which variant each component applies to using the :guilabel:`Apply " +"on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Product Variants in the Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 +msgid "Set up operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:64 +msgid "" +"Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify" +" instructions for production and register time spent on an operation. To use" +" this feature, first enable the :guilabel:`Work Orders` feature in " +":menuselection:`Manufacturing --> Configuration --> Settings --> " +"Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:69 +msgid "" +"Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the " +":guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new " +"operation. In the :guilabel:`Create Operations` box, give the operation a " +"name, specify the :guilabel:`Work Center` and duration settings. Like " +"components, Odoo gives the option to specify a product variant in the " +":guilabel:`Apply on Variants` field so the operation only applies to that " +"variant. Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:76 +msgid "" +"Each operation is unique, as it is always exclusively linked to one " +":abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a" +" new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing " +"Operations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst-1 +msgid "Copy Existing Operations feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 +msgid "Add by-products to a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 +msgid "" +"A *By-Product* is a residual product that is created during production in " +"addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike " +"the primary product, there can be more than one by-product on a :abbr:`BoM " +"(Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:91 +msgid "" +"To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the " +":guilabel:`By-Products` feature in :menuselection:`Manufacturing --> " +"Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:94 +msgid "" +"Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill " +"of Materials)` by clicking on the :guilabel:`Operations` tab and clicking " +":guilabel:`Add a line`. Then, name the by-product and indicate the " +":guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM " +"(Bill of Materials)` has configured operations, specify exactly which " +"operation the by-product is produced from in the :guilabel:`Produced in " +"Operation` field. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:3 +msgid "Manufacturing product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:8 +msgid "" +"In order to manufacture a product in Odoo *Manufacturing*, the product must " +"be properly configured. Doing so consists of enabling the *Manufacturing* " +"route and configuring a bill of materials (BoM) for the product. Once these " +"steps are completed, the product is selectable when creating a new " +"manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:14 +msgid "Activate the Manufacture route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:16 +msgid "" +"The Manufacture route is activated for each product on its own product page." +" To do so, begin by navigating to :menuselection:`Manufacturing --> Products" +" --> Products`. Then, select an existing product, or create a new one by " +"clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:20 +msgid "" +"On the product page, select the :guilabel:`Inventory` tab, then enable the " +":guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This " +"tells Odoo the product can be manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Manufacturing route on the Inventory tab of a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:28 +msgid "Configure a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:30 +msgid "" +"Next, a |BOM| must be configured for the product so Odoo knows how it is " +"manufactured. A |BOM| is a list of the components and operations required to" +" manufacture a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:33 +msgid "" +"To create a |BOM| for a specific product, navigate to " +":menuselection:`Manufacturing --> Products --> Products`, then select the " +"product. On the product page, click the :guilabel:`Bill of Materials` smart " +"button at the top of the page, then select :guilabel:`New` to configure a " +"new |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Bill of Materials smart button on a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:41 +msgid "" +"On the |BOM|, the :guilabel:`Product` field auto-populates with the product." +" In the :guilabel:`Quantity` field, specify the number of units that the BoM" +" produces." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:44 +msgid "" +"Add a component to the |BOM| by selecting the :guilabel:`Components` tab and" +" clicking :guilabel:`Add a line`. Select a component from the " +":guilabel:`Component` drop-down menu, then enter the quantity in the " +":guilabel:`Quantity` field. Continue adding components on new lines until " +"all components have been added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Components tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:53 +msgid "" +"Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` " +"and a :guilabel:`Create Operations` pop-up window appears. In the " +":guilabel:`Operation` field, specify the name of the operation being added " +"(e.g. Assemble, Cut, etc.). Select the work center where the operation will " +"be carried out from the :guilabel:`Work Center` drop-down menu. Finally, " +"click :guilabel:`Save & Close` to finish adding operations, or " +":guilabel:`Save & New` to add more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:60 +msgid "" +"The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` " +"setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> " +"Configuration --> Settings`, then enable the :guilabel:`Work Orders` " +"checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst-1 +msgid "The Operations tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:70 +msgid "" +"The section above provides instructions for creating a basic |BOM| that " +"allows a product to be manufactured in Odoo. However, it is by no means an " +"exhaustive summary of all the options available when configuring a |BOM|. " +"For more information about bills of materials, see the documentation on how " +"to :ref:`create a bill of materials <manufacturing/management/bill-" +"configuration>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 +msgid "Use kits" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5 +msgid "" +"In Odoo, a *kit* is a type of bill of materials (BoM) that can be " +"manufactured and sold. Kits are sets of unassembled components sold to " +"customers. They may be sold as standalone products, but are also useful " +"tools for managing more complex bills of materials (BoMs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10 +msgid "" +"To use, manufacture, and sell kits, both the :guilabel:`Manufacturing` and " +":guilabel:`Inventory` apps need to be installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:14 +msgid "Create the kit as a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16 +msgid "" +"To use a kit as a sellable product, or simply as a component organization " +"tool, the kit should first be created as a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:19 +msgid "" +"To create a kit product, go to :menuselection:`Inventory app --> Products " +"--> Products`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22 +msgid "" +"Then, assign a name to the new kit product. Next, under the " +":guilabel:`General Information` tab, set the :guilabel:`Product Type` to " +":guilabel:`Consumable`. Kit products work best as consumables, because the " +"stock on-hand for kits is typically not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:27 +msgid "" +"Although kits should almost always be set to :guilabel:`Consumable`, " +"companies using **Anglo-Saxon** accounting might need to create kits as a " +":guilabel:`Storable Product`. This is because when processing invoices for " +"kits, the Cost of Goods Sold (COGS) will be posted in accounting journals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:32 +msgid "" +"Unlike storable products, the :guilabel:`Routes` designation under the " +":guilabel:`Inventory` tab does not matter for kits, since Odoo uses the " +"routes of the kit's individual components for replenishment purposes. All " +"other parameters for the kit product may be modified according to " +"preference. Once ready, click :guilabel:`Save` to save the new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:37 +msgid "" +"The kit's components must also be configured as products via " +":menuselection:`Inventory app --> Products --> Products`. These components " +"require no specific configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41 +msgid "Set up the kit BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:43 +msgid "" +"After fully configuring the kit product and its components, a new :abbr:`BoM" +" (bill of materials)` can be created for the kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46 +msgid "" +"To do so, go to :menuselection:`Manufacturing app --> Products --> Bills of " +"Materials`, and click :guilabel:`Create`. Next to the :guilabel:`Product` " +"field, click the drop-down menu to reveal a list of products, and select the" +" previously configured kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:50 +msgid "" +"Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Kit` option." +" Finally, under the :guilabel:`Components` tab, click :guilabel:`Add a " +"line`, and add each desired component, and specify their quantities under " +"the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:54 +msgid "" +"Once ready, click :guilabel:`Save` to save the newly-created :abbr:`BoM " +"(bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit selection on the bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60 +msgid "" +"If the kit is solely being used as a sellable product, then only components " +"need to be added under the :guilabel:`Components` tab, and configuring " +"manufacturing operations is not necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:64 +msgid "" +"When a kit is sold as a product, it appears as a single line item on the " +"quotation and sales order. However, on delivery orders, each component of " +"the kit is listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68 +msgid "Use kits to manage complex BoMs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:70 +msgid "" +"Kits are also used to manage multi-level :abbr:`BoMs (bills of materials)`. " +"These are products that contain **other** :abbr:`BoM (bill of materials)` " +"products as components, and therefore require *nested* :abbr:`BoMs (bills of" +" materials)`. Incorporating pre-configured kits into multi-level :abbr:`BoMs" +" (bills of materials)` allows for cleaner organization of bundled products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:75 +msgid "" +"To configure this type of :abbr:`BoM (bill of materials)` with a kit as a " +"component, go to :menuselection:`Manufacturing app --> Products --> Bills of" +" Materials`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:79 +msgid "" +"Next to the :guilabel:`Product` field, click the drop-down menu to reveal a " +"list of products, and select the desired :abbr:`BoM (bill of materials)` " +"product. Then, for the :guilabel:`BoM Type` field, select the " +":guilabel:`Manufacture this product` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:83 +msgid "" +"Under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and " +"select a kit as the component. Adding the kit as a component eliminates the " +"need to add the kit's components individually. Any :guilabel:`BoM Type` can " +"be used for the higher-level product's :abbr:`BoM (bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:88 +msgid "Once ready, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Kit as a component in a multilevel bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:95 +msgid "Structure & cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:97 +msgid "" +"To access a comprehensive overview of the multi-level :abbr:`BoM's (bill of " +"material's)` components, click on the :guilabel:`Structure & Cost` smart " +"button. Sublevel :abbr:`BoMs (bills of materials)` can be expanded and " +"viewed from this report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst-1 +msgid "Expanded kit in the Structure and Cost report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:105 +msgid "" +"When creating a manufacturing order for a product with a multi-level " +":abbr:`BoM (bill of materials)`, the kit product automatically expands to " +"show all components. Any operations in the kit's :abbr:`BoM (bill of " +"materials)` are also added to the list of work orders on the manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:111 +msgid "" +"Kits are primarily used to bundle components together for organization or " +"sale. To manage multi-level products that require manufactured sub-" +"components, refer to :doc:`this documentation <sub_assemblies>` on sub-" +"assemblies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:3 +msgid "Manufacturing backorders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:5 +msgid "" +"In some cases, the full quantity of a manufacturing order cannot be produced" +" immediately. When this happens, Odoo *Manufacturing* allows for the " +"manufacturing of partial quantities of the order and creates a *backorder* " +"for the remaining amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:9 +msgid "" +"In the *Manufacturing* app, creating a backorder splits the original " +"manufacturing order into two orders. The reference tag for each order is the" +" tag used for the original order, followed by a hyphen and then an " +"additional number to indicate that it's a backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:14 +msgid "" +"A company creates a manufacturing order with the reference tag " +"*WH/MO/00175*, for 10 units of *Product X*. After starting work on the " +"manufacturing order, the employee working the production line realizes there" +" are only enough components in stock to produce five units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:18 +msgid "" +"Instead of waiting for additional stock of the components, they manufacture " +"five units and create a backorder for the remaining five. This splits the " +"manufacturing order into two separate orders: *WH/MO/00175-001* and " +"*WH/MO/00175-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:22 +msgid "" +"Order *001* contains the five units that have been manufactured, and is " +"immediately marked as :guilabel:`Done`. Order *002* contains the five units " +"that still need to be manufactured and is marked as :guilabel:`In Progress`." +" Once the remaining components are available, the employee returns to order " +"*002* and manufactures the remaining units before closing the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:28 +msgid "Create a manufacturing backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:30 +msgid "" +"To create a backorder for part of a manufacturing order, begin by navigating" +" to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order with a quantity of two or more or create one by" +" clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:34 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:86 +msgid "" +"If a new manufacturing order is created, select a product from the " +":guilabel:`Product` drop-down menu and enter a quantity of two or more in " +"the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm " +"the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:38 +msgid "" +"After manufacturing the quantity that is being produced immediately, enter " +"that number in the :guilabel:`Quantity` field at the top of the " +"manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The quantity field on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:45 +msgid "" +"Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than " +"initial demand` pop-up window appears, from which a backorder can be " +"created. Click :guilabel:`Create Backorder` to split the manufacturing order" +" into two separate orders, with the reference tags *WH/MO/XXXXX-001* and " +"*WH/MO/XXXXX-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "" +"The Create Backorder button on the \"You produced less than initial demand\"" +" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:54 +msgid "" +"Order *001* contains the items that have been manufactured, and is closed " +"immediately. Order *002* is the backorder that contains the items that have " +"yet to be manufactured, and remains open, to be completed at a later date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:58 +msgid "" +"Once the remaining units can be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select the backorder manufacturing order. If all of the remaining units" +" are manufactured immediately, simply click :guilabel:`Validate` to close " +"the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:63 +msgid "" +"If only some of the remaining units are manufactured immediately, create " +"another backorder for the remainder by following the steps detailed in this " +"section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:67 +msgid "Create a backorder from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:69 +msgid "" +"Backorders for manufacturing orders can also be created from the work order " +"tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:72 +msgid "" +"In order to use tablet view, the *Work Orders* setting must be enabled. To " +"enable it, navigate to :menuselection:`Manufacturing --> Configuration --> " +"Settings`. On the :guilabel:`Settings` page, enable the checkbox next to " +":guilabel:`Work Orders`, then click :guilabel:`Save` to save the change. " +"This makes the :guilabel:`Work Orders` tab appear on manufacturing orders, " +"from which the tablet view can be opened." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:0 +msgid "The Work Orders setting on the Manufacturing settings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82 +msgid "" +"To create a backorder from the tablet view, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order with a quantity of two or more or create one by" +" clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:90 +msgid "" +"After confirming the manufacturing order, select the :guilabel:`Work Orders`" +" tab and click the :guilabel:`📱 (tablet view)` button located on the line of" +" the first work order to enter the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The tablet view button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:97 +msgid "" +"Once in tablet view, enter the quantity being manufactured immediately in " +"the :guilabel:`Units` field at the top left of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The Units field in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:104 +msgid "" +"The steps for the rest of the workflow depend on whether the manufacturing " +"order being processed requires the completion of a single work order or " +"multiple work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:108 +msgid "Single work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:110 +msgid "" +"If the manufacturing order only requires the completion of a single work " +"order, complete the work order, then click :guilabel:`Mark As Done And Close" +" MO`. The manufacturing order is closed and a backorder for the units that " +"still need to be manufactured is created automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "" +"The Mark As Done And Close MO button in the tablet view of a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:118 +msgid "" +"Once the remaining units are ready to be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select the backorder manufacturing order, which is titled using the " +"reference tag of the original backorder with *002* added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:122 +msgid "" +"On the backorder manufacturing order, select the :guilabel:`Work Orders` tab" +" and click the :guilabel:`📱 (tablet view)` button located on the line of the" +" work order to open the tablet view. If all of the units in the backorder " +"will be completed immediately, simply click :guilabel:`Mark As Done And " +"Close MO` after completing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:127 +msgid "" +"If only some of the remaining units will be manufactured immediately, enter " +"the number in the :guilabel:`Units` field at the top left of the tablet " +"view, then click :guilabel:`Mark As Done And Close MO` to create another " +"backorder for the remaining units. The new backorder can be processed using " +"the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:133 +msgid "Multiple work orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:135 +msgid "" +"If the manufacturing order requires the completion of multiple work orders, " +"complete the first work order, and then click :guilabel:`Record Production`." +" This splits the manufacturing order into two separate orders, titled " +"*WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*, with *XXXXX* being the number of " +"the original order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst-1 +msgid "The Record Production button on a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:144 +msgid "" +"The tablet view defaults to showing the first work order for the *002* " +"manufacturing order. Since this manufacturing order will not be completed " +"immediately, back out of tablet view by clicking the :guilabel:`⬅️ (back)` " +"button twice. Doing so will take you to the *001* order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:148 +msgid "" +"To finish the *001* order, select the :guilabel:`Work Orders` tab and click " +"the :guilabel:`tablet view` button located on the line of the next work " +"order. Finally, complete the remaining work orders, then click " +":guilabel:`Mark As Done And Close MO` to close the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:152 +msgid "" +"Once the remaining units are ready to be manufactured, navigate to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select the *002* order. Select the :guilabel:`Work Orders` tab and click " +"the :guilabel:`tablet view` button located on the line of the first work " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:157 +msgid "" +"If all of the units in the backorder will be completed immediately, simply " +"click :guilabel:`Mark As Done And Close MO` after completing all of the work" +" orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:160 +msgid "" +"If only some of the remaining units will be manufactured immediately, enter " +"the number in the :guilabel:`Units` field at the top left of the tablet " +"view, then click :guilabel:`Record Production` to create an additional " +"backorder for the remaining units, with *003* at the end of its reference " +"tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:165 +msgid "" +"The *002* backorder and *003* backorder can be completed by following the " +"steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:169 +msgid "" +"It is also possible to create a backorder in the middle of a manufacturing " +"order, when some but not all of the work orders have already been completed." +" Doing so marks the completed work order(s) as :guilabel:`Finished` on the " +"backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:174 +msgid "" +"A manufacturing order for four chairs requires the completion of two work " +"orders: *Paint* and *Assemble*. While the paint step can be completed " +"immediately for all four chairs, there are only enough screws to assemble " +"two of them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:178 +msgid "" +"As a result, the employee responsible for producing the chairs begins by " +"painting all four, and marking the *Paint* work order as " +":guilabel:`Finished` for all of them. Then, they move on to the *Assemble* " +"work order. They assemble two of the four chairs, enter that number in the " +":guilabel:`Units` field of the tablet view, and click :guilabel:`Record " +"Production`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:183 +msgid "" +"A backorder manufacturing order is created for the remaining two chairs. On " +"the backorder, the *Paint* work order is already marked as " +":guilabel:`Finished`, and only the *Assemble* work order is left to be " +"completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:187 +msgid "" +"Once more screws are available, the manufacturing employee assembles the " +"remaining chairs and clicks :guilabel:`Mark As Done And Close MO` to " +"complete the *Assemble* work order and close the backorder manufacturing " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:3 +msgid "One-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using one-step manufacturing, Odoo creates a " +"manufacturing order (MO), but does not generate transfers for the movement " +"of components out of inventory or finished products into stock. Inventory " +"counts still update based on the number of components used and products " +"manufactured, but the act of transferring them to and from inventory is not " +"tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:16 +msgid "" +"The number of steps used in manufacturing is set at the warehouse level, " +"allowing for each warehouse to use a different number of steps. To change " +"the number of steps used for a specific warehouse, begin by navigating to " +":menuselection:`Inventory --> Configuration --> Warehouses`, and then select" +" a warehouse from the :guilabel:`Warehouses` screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:20 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:21 +msgid "" +"On the :guilabel:`Warehouse Configuration` tab, find the " +":guilabel:`Manufacture` radio input field, and select one of the three " +"options: :guilabel:`Manufacture (1 step)`, :guilabel:`Pick components and " +"then manufacture (2 steps)`, or :guilabel:`Pick components, manufacture and " +"then store products (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:0 +msgid "The Manufacture radio input field on a warehouse configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:31 +msgid "" +"Products must be properly configured before they can be manufactured in " +"Odoo. For details on how to do so, see the documentation on how to " +":ref:`configure a product for manufacturing " +"<manufacturing/management/configure-manufacturing-product>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:36 +msgid "Create manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:38 +msgid "" +"To manufacture a product in Odoo *Manufacturing*, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:42 +msgid "" +"On the new |MO|, select the product to be produced from the " +":guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field " +"auto-populates with the associated bill of materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:45 +msgid "" +"If a product has more than one |BOM| configured for it, the specific |BOM| " +"can be selected in the :guilabel:`Bill of Material` field, and the " +":guilabel:`Product` field auto-populates with the associated product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:49 +msgid "" +"After a |BOM| has been selected, the :guilabel:`Components` and " +":guilabel:`Work Orders` tabs auto-populate with the components and " +"operations specified on the |BOM|. If additional components or operations " +"are required for the |MO| being configured, add them to the " +":guilabel:`Components` and :guilabel:`Work Orders` tabs by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:55 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:80 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:77 +msgid "Process manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:79 +msgid "" +"An |MO| is processed by completing all of the work orders listed under its " +":guilabel:`Work Orders` tab. This can be done on the |MO| itself, or from " +"the work order tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:83 +msgid "Basic workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:85 +msgid "" +"To complete work orders from the |MO| itself, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:91 +msgid "" +"On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins " +"on the first work order that needs to be completed, click the " +":guilabel:`Start` button for that work order. Odoo *Manufacturing* then " +"starts a timer that keeps track of how long the work order takes to " +"complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +msgid "The Start button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:74 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:96 +msgid "" +"When the work order is completed, click the :guilabel:`Done` button for that" +" work order. Repeat the same process for each work order listed on the " +":guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst-1 +msgid "The Done button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:81 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:103 +msgid "" +"After completing all of the work orders, click :guilabel:`Produce All` at " +"the top of the screen to mark the |MO| as :guilabel:`Done`, and register the" +" manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:107 +msgid "Tablet view workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:112 +msgid "" +"To complete the work orders for an |MO| using the tablet view, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:91 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:116 +msgid "" +"Next, click on the :guilabel:`Work Orders` tab, and then select the " +":guilabel:`📱 (tablet)` button on the line of the first work order to be " +"processed. This opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:98 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:119 +msgid "" +"After opening the tablet view, Odoo *Manufacturing* automatically starts a " +"timer that keeps track of how long the work order takes to complete. After " +"completing the work order, click the :guilabel:`Mark as Done` button in the " +"top-right corner of the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:102 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:123 +msgid "" +"Clicking :guilabel:`Mark as Done` while there is at least one more work " +"order left to complete opens a page that lists the next work order. Click on" +" that work order to open it in the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:105 +msgid "" +"Once the final work order for the |MO| has been reached, a :guilabel:`Mark " +"as Done and Close MO` button appears on the tablet view in addition to the " +":guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO`" +" to mark the |MO| as :guilabel:`Done` and register the manufactured " +"product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:110 +msgid "" +"It is also possible to complete the final operation while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed later by clicking the :guilabel:`Produce All` button on the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 +msgid "Managing BoMs for product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 +msgid "" +"Odoo allows one bill of materials (BoM) to be used for multiple variants of " +"the same product. Having a consolidated :abbr:`BoM (bill of materials)` for " +"a product with variants saves time by preventing the need to manage multiple" +" :abbr:`BoMs (bills of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 +msgid "Activate product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 +msgid "" +"To activate the product variants feature, navigate to " +":menuselection:`Inventory app --> Configuration --> Settings`, and scroll " +"down to the :guilabel:`Products` section. Then, click the checkbox to enable" +" the :guilabel:`Variants` option. After that, click :guilabel:`Save` to " +"apply the setting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:17 +msgid "" +"For more information on configuring product variants, refer to the " +":doc:`product variants " +"<../../../sales/sales/products_prices/products/variants>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Selecting \"Variants\" from Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 +msgid "Create custom product attributes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:27 +msgid "" +"Once the product variants feature is activated, create and edit product " +"attributes on the :guilabel:`Attributes` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:30 +msgid "" +"The :guilabel:`Attributes` page is accessible either from " +":menuselection:`Inventory app --> Configuration --> Settings` by clicking " +"the :guilabel:`Attributes` button, or by clicking :menuselection:`Inventory " +"app --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:34 +msgid "" +"Once on the :guilabel:`Attributes` page, either click into an existing " +"attribute, or click :guilabel:`Create` to create a new one. Clicking " +":guilabel:`Create` reveals a new, blank form for customizing an attribute. " +"For an existing attribute, click :guilabel:`Edit` on its form to make " +"changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +msgid "" +"Assign an :guilabel:`Attribute Name`, and choose a category from the " +":guilabel:`Category` field's drop-down menu. Then, select the desired " +"options next to the :guilabel:`Display Type` and :guilabel:`Variants " +"Creation Mode` fields. Once the desired options are selected, click " +":guilabel:`Add a line` under the :guilabel:`Attribute Values` tab to add a " +"new value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:45 +msgid "" +"Included on the :guilabel:`Value` row is a :guilabel:`Is custom value` " +"checkbox. If selected, this value will be recognized as a custom value, " +"which allows customers to type special customization requests upon ordering " +"a custom variant of a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:0 +msgid "Product variant attribute configuration screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:54 +msgid "" +"Once all desired :guilabel:`Values` have been added, click :guilabel:`Save` " +"to save the new attribute." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:58 +msgid "Add product variants on the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:60 +msgid "" +"Created attributes can be applied on specific variants for particular " +"products. To add product variants to a product, navigate to the product form" +" by going to :menuselection:`Inventory app --> Products --> Products`. To " +"make changes to the product, click :guilabel:`Edit`. Then, click the " +":guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:65 +msgid "" +"Under the :guilabel:`Attribute` header, click :guilabel:`Add a line` to add " +"a new attribute, and select one to add from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:68 +msgid "" +"Then, under the :guilabel:`Values` header, click the drop-down menu to " +"choose from the list of existing values. Click on each desired value to add " +"them, and repeat this process for any additional attributes that should be " +"added to the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:72 +msgid "Once finished, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Product form variants tab with values and attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:79 +msgid "" +":abbr:`BoM (bill of materials)` products with multiple variants that are " +"manufactured in-house should either have a **0,0 reordering rule** set up, " +"or have their replenishment routes set to *Replenish on Order (MTO)*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:84 +msgid "Apply BoM components to product variants" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:86 +msgid "" +"Next, create a new :abbr:`BoM (bill of materials)`. Or, edit an existing " +"one, by going to :menuselection:`Manufacturing app --> Products --> Bills of" +" Materials`. Then, click :guilabel:`Create` to open a new :guilabel:`Bills " +"of Materials` form to configure from scratch." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:90 +msgid "" +"Add a product to the :abbr:`BoM (bill of materials)` by clicking the drop-" +"down menu in the :guilabel:`Product` field and selecting the desired " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:93 +msgid "" +"Then, add components by clicking :guilabel:`Add a line` under the " +":guilabel:`Component` section of the :guilabel:`Components` tab, and " +"choosing the desired components from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:96 +msgid "" +"Choose the desired values in the :guilabel:`Quantity` and :guilabel:`Product" +" Unit of Measure` columns. Then, choose the desired values in the " +":guilabel:`Apply on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:100 +msgid "" +"The :guilabel:`Apply on Variants` option to assign components to specific " +"product variants on the :abbr:`BoM (bill of materials)` is available once " +"the :guilabel:`Variants` setting is activated from the " +":menuselection:`Inventory` application. If the :guilabel:`Apply on Variants`" +" field is not immediately visible, activate it from the additional options " +"menu (three-dots icon, to the right of the header row)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "\"Apply on Variants\" option on the additional options menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:110 +msgid "" +"Each component can be assigned to multiple variants. Components with no " +"variants specified are used in every variant of the product. The same " +"principle applies when configuring operations and by-products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:114 +msgid "" +"When defining variant :abbr:`BoMs (bills of material)` by component " +"assignment, the :guilabel:`Product Variant` field in the main section of the" +" :abbr:`BoM (bill of materials)` should be left blank. This field is *only* " +"used when creating a :abbr:`BoM (bill of materials)` specifically for one " +"product variant." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:119 +msgid "" +"When all desired configurations have been made to the :abbr:`BoM (bill of " +"materials)`, click :guilabel:`Save` at the top of the form to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:123 +msgid "" +"For components that only apply for specific variants, choose which " +"operations the components should be consumed in. If the :guilabel:`Consumed " +"in Operation` column is *not* immediately visible, activate it from the " +"additional options menu (three-dots icon, to the right of the header row)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:129 +msgid "Sell and manufacture variants of BoM products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:131 +msgid "" +"To sell and manufacture variants of :abbr:`BoM (bill of materials)` products" +" to order, navigate to :menuselection:`Sales app --> Create` to create a new" +" quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:135 +msgid "Sell variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:137 +msgid "" +"Once on the blank :guilabel:`Quotation` form, click the drop-down next to " +"the :guilabel:`Customer` field to add a customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:140 +msgid "" +"Then, under the :guilabel:`Order Lines` tab, click :guilabel:`Add a " +"product`, and select the previously-created :abbr:`BoM (bill of materials)` " +"product with variants from the drop-down menu. Doing so reveals a " +":guilabel:`Configure a product` pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:144 +msgid "" +"From the pop-up window, click the desired attribute options to configure the" +" correct variant of the product to manufacture. Then, click the green " +":guilabel:`+` or :guilabel:`-` icons next to the `1` to change the quantity " +"to sell and manufacture, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Configure a product pop-up for choosing variant attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:152 +msgid "" +"Once all the specifications have been chosen, click :guilabel:`Add`. This " +"will change the pop-up to a second :guilabel:`Configure` pop-up, where " +"available optional products will appear, if they have been created " +"previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:156 +msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:158 +msgid "" +"Then, click :guilabel:`Save` to save all changes, and click " +":guilabel:`Confirm` at the top of the :guilabel:`Quotation` form to create " +"and confirm a new sales order (SO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:162 +msgid "Manufacture variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:164 +msgid "" +"Once the :abbr:`SO (sales order)` is confirmed, a :guilabel:`Manufacturing` " +"smart button appears at the top of the :abbr:`SO (sales order)` form. Click " +"the :guilabel:`Manufacturing` smart button to open the " +":guilabel:`Manufacturing Order` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:168 +msgid "" +"On this form, under the :guilabel:`Components` tab, the appropriate " +"components for the chosen variant are listed. And, depending on the variant," +" different components will be listed. To see any mandatory or optional " +":guilabel:`Operation` steps, click the :guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:172 +msgid "" +"To enter the tablet view work order screen, click the :guilabel:`tablet " +"icon` to the right of the row for the desired operation to be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:175 +msgid "" +"From the tablet view, click :guilabel:`Mark as Done` as the operation " +"progresses to complete the operation steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:178 +msgid "" +"Alternatively, click the :guilabel:`Mark as Done` button at the top of the " +"manufacturing order form to complete the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst-1 +msgid "Manufacturing order for variant of BoM product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:185 +msgid "" +"Then, navigate back to the :abbr:`SO (sales order)` via the breadcrumbs at " +"the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:187 +msgid "" +"Now that the product has been manufactured, click the :guilabel:`Delivery` " +"smart button to deliver the product to the customer. From the " +":guilabel:`Delivery Order` form, click :guilabel:`Validate`, then click " +":guilabel:`Apply` to deliver the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:191 +msgid "" +"To finish the sale, click back to the :abbr:`SO (sales order)` via the " +":guilabel:`breadcrumbs` at the top of the page again. Then, click " +":guilabel:`Create Invoice` followed by :guilabel:`Create Invoice` again to " +"invoice the customer for the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:3 +msgid "Scrap during manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:5 +msgid "" +"During the manufacturing process, the need to scrap manufacturing components" +" or finished products may arise. This can be necessary if a component or " +"product is damaged, or unusable for any other reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:9 +msgid "" +"By default, scrapping a component or finished product removes it from " +"physical inventory and places it in a virtual location titled *Virtual " +"Locations/Scrap*. A virtual location is **not** a physical space, but rather" +" a designation in Odoo that is used to track items that are no longer in " +"physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:14 +msgid "" +"Odoo *Manufacturing* allows for both components and finished products to be " +"scrapped within a manufacturing order. The specific type of item that can be" +" scrapped during a manufacturing order depends on the stage of the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:23 +msgid "" +"To view the total quantity of each item scrapped, navigate to " +":menuselection:`Inventory --> Configuration --> Locations`, then remove the " +":guilabel:`Internal` filter from the :guilabel:`Search...` bar to display " +"all virtual locations. From the list, select the :guilabel:`Virtual " +"Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:29 +msgid "Scrap manufacturing components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:31 +msgid "" +"To scrap components during the manufacturing process, begin by navigating to" +" :menuselection:`Manufacturing --> Manufacturing Orders`, then select a " +"manufacturing order or click :guilabel:`Create` to configure a new one. If a" +" new manufacturing order is created, select a product from the " +":guilabel:`Product` drop-down menu, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:36 +msgid "" +"Once the manufacturing order has been confirmed, a :guilabel:`Scrap` button " +"appears at the top of the page. Click the button and a :guilabel:`Scrap` " +"pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The scrap button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:43 +msgid "" +"From the :guilabel:`Product` drop-down menu on the :guilabel:`Scrap` pop-up " +"window, select the component that is being scrapped, then enter the quantity" +" in the :guilabel:`Quantity` field. Finally, click :guilabel:`Done` to scrap" +" the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The Scrap pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:52 +msgid "" +"Before clicking :guilabel:`Mark As Done` on a manufacturing order, only the " +"components of the finished product can be scrapped, **not** the finished " +"product itself. This is because Odoo recognizes that the finished product " +"cannot be scrapped before it has been manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:56 +msgid "" +"After scrapping a component, continue the manufacturing process using the " +"required quantity of the component that was scrapped. The on-hand stock " +"count for the component that was scrapped updates to reflect both the " +"scrapped quantity and the quantity consumed during manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:61 +msgid "" +"If the manufacturing of a table requires four units of a table leg, and two " +"units of the table leg were scrapped during the manufacturing process, the " +"total quantity of table legs consumed will be six: four units used to " +"manufacture the table plus two units scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:66 +msgid "Scrap components from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:68 +msgid "" +"Components can also be scrapped from the manufacturing tablet view. To do " +"so, select the :guilabel:`Work Orders` tab on a manufacturing order, then " +"click the :guilabel:`📱 (tablet view)` icon for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "The tablet view icon for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:76 +msgid "" +"With tablet view open, click the :guilabel:`☰ (menu)` button at the top left" +" of the screen, then select the :guilabel:`Scrap` button on the " +":guilabel:`Menu` pop-up window. The :guilabel:`Scrap` pop-up window then " +"appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst-1 +msgid "" +"The Scrap button on the Menu pop-up window of the manufacturing tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:84 +msgid "" +"Finally, select a component from the :guilabel:`Product` drop-down menu and " +"enter the quantity being scrapped in the :guilabel:`Quantity` field. Click " +":guilabel:`Done` to scrap the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:88 +msgid "Scrap finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:90 +msgid "" +"Odoo also allows for finished products to be scrapped from a manufacturing " +"order once the order is completed. After clicking :guilabel:`Mark as Done`, " +"click the :guilabel:`Scrap` button to make the :guilabel:`Scrap` pop-up " +"window appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:94 +msgid "" +"Since the components have been consumed to create the finished product, they" +" will no longer appear in the :guilabel:`Product` drop-down menu. Instead, " +"the finished product will be available as an option. Select the finished " +"product and enter the quantity to be scrapped in the :guilabel:`Quantity` " +"field. Click :guilabel:`Done` to scrap the finished product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:99 +msgid "" +"The on-hand stock count for the product that was scrapped will update to " +"reflect both the scrapped quantity and the quantity produced during " +"manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:103 +msgid "" +"If five units of a chair were manufactured, but two units were scrapped " +"after manufacturing was completed, then the on-hand inventory of the chair " +"will increase by three: five units manufactured minus two units scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:3 +msgid "Split and merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:5 +msgid "" +"In Odoo *Manufacturing*, it is possible to create manufacturing orders for a" +" single unit of an item, or multiple units of the same item. In some cases, " +"it may be necessary to split a manufacturing order that contains multiple " +"units into two or more orders, or to merge two or more orders into a single " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:11 +msgid "" +"A manufacturing order can only contain one unit of a product, or multiple " +"units of a single product that all use the same Bill of Materials (BoM). As " +"a result, it is only possible to merge manufacturing orders when every order" +" contains the same product being manufactured with the same BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:17 +msgid "Split manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:19 +msgid "" +"To split a manufacturing order into multiple orders, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select a manufacturing order. At the top of the page, next to the " +":guilabel:`New` button, the manufacturing order's reference number appears " +"with a :guilabel:`⚙️ (settings)` button next to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:24 +msgid "" +"Click the :guilabel:`⚙️ (settings)` button to open the general settings for " +"the manufacturing order, then select :guilabel:`Split`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Settings and Split buttons on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:31 +msgid "" +"After selecting :guilabel:`Split`, a :guilabel:`Split production` pop-up " +"window appears. In the :guilabel:`Split #` field, enter the number of " +"manufacturing orders that the original order should be split into, then " +"click outside of the field. A table appears below, with a line for each new " +"manufacturing order that will be created by the split. In the " +":guilabel:`Quantity To Produce` column, enter the number of units that will " +"be assigned to each new manufacturing order. Finally, click " +":guilabel:`Split` to split the manufacturing order." +msgstr "" +"หลังจากเลือก :guilabel:`แยก` หน้าต่างป๊อปอัป :guilabel:`แยกการผลิต` " +"จะแสดงขึ้น ในช่อง :guilabel:`แยก #` " +"ให้ป้อนจำนวนใบสั่งผลิตที่ควรแยกใบสั่งเดิม จากนั้นคลิกด้านนอกช่อง " +"ตารางแสดงด้านล่าง " +"พร้อมด้วยรายการสำหรับใบสั่งผลิตใหม่แต่ละรายการที่จะถูกสร้างขึ้นโดยการแยก " +"ในคอลัมน์ :guilabel:`ปริมาณที่จะผลิต` " +"ให้ป้อนจำนวนหน่วยที่จะกำหนดให้กับใบสั่งผลิตใหม่แต่ละรายการ สุดท้าย คลิก " +":guilabel:`แยก` เพื่อแยกใบสั่งผลิต" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Split production pop-up window for a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:42 +msgid "" +"After clicking :guilabel:`Split`, the original manufacturing order is split " +"into the number of orders that was specified in the :guilabel:`Split #` " +"field. The reference numbers for the new manufacturing orders are the " +"reference number for the original order with *-###* tags added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:48 +msgid "" +"Manufacturing order *WH/MO/00012* is split into three separate orders. The " +"reference numbers for the new orders are *WH/MO/00012-001*, " +"*WH/MO/00012-002*, and *WH/MO/00012-003*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:52 +msgid "Merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:54 +msgid "" +"To merge two or more manufacturing orders into a single order, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`. Select the manufacturing orders that will be merged by activating " +"the checkbox to the left of the name of each order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "" +"Select manufacturing orders that will be merged by clicking the checkbox for" +" each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:62 +msgid "" +"Once all manufacturing orders have been selected, click the " +":guilabel:`Actions` button at the top of the page, then select " +":guilabel:`Merge` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst-1 +msgid "The Actions and Merge buttons on the Manufacturing Orders page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:69 +msgid "" +"The selected manufacturing orders are merged into a single order. The " +"reference number for the new manufacturing order is the next sequential " +"number that has *not* already been assigned to an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:73 +msgid "" +"The last reference number used for a manufacturing order was *WH/MO/00012*. " +"Two manufacturing orders, *WH/MO/00008* and *WH/MO/00009*, are merged into a" +" single order. The reference number for the manufacturing order created by " +"the merger is *WH/MO/00013*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:77 +msgid "" +"In the :guilabel:`Source` field for the manufacturing order created by the " +"merger, the reference numbers of the manufacturing orders that were merged " +"are listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:81 +msgid "" +"Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create " +"*WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* " +"and *WH/MO/00010*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 +msgid "Manage semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:5 +msgid "" +"A *semi-finished product*, also known as a *subassembly*, is a manufactured " +"product that is used as a component in another product's bill of materials " +"(BoM). Semi-finished products are used to simplify complex :abbr:`BoMs " +"(Bills of Materials)` or to more accurately represent a manufacturing flow. " +"A :abbr:`BoM (Bill of Materials)` that contains semi-finished products is " +"referred to as a *multilevel BoM*, where the main *top-level product* and " +"its subassemblies are distinguished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:12 +msgid "Configure semi-finished products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:14 +msgid "" +"To set up a multilevel :abbr:`BoM (Bill of Materials)`, the top-level " +"product and semi-finished products must be configured. Therefore, the first " +"step is to create the semi-finished products and their :abbr:`BoMs (Bills of" +" Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:19 +msgid ":doc:`bill_configuration`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A bill of materials for a semi-finished product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:26 +msgid "Create the top-level bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:28 +msgid "" +"After the semi-finished products are fully configured, navigate to " +":menuselection:`Manufacturing --> Products --> Products`. Then, " +":guilabel:`Create` the top-level product. Configure the product's " +"specifications as desired, and be sure to :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:32 +msgid "" +"Once the top-level product is configured, click the :guilabel:`Bill of " +"Materials` smart button on the product form, then click :guilabel:`Create` " +"to make a :abbr:`BoM (Bill of Materials)` for the top-level product. Then, " +"simply add the semi-finished products to this :abbr:`BoM (Bill of " +"Materials)`, along with any other necessary components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "" +"A bill of materials for a top-level product, containing a subassembly " +"component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:42 +msgid "Manage production planning" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:44 +msgid "" +"There are several methods to manage manufacturing order automation for " +"products with multilevel :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:48 +msgid "" +"Semi-finished products are specifically used to manage manufacturable " +"products with multilevel BoMs. If a BoM is being created simply to organize " +"components or bundle sellable products, using :doc:`Kits <kit_shipping>` is " +"the more appropriate option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:52 +msgid "" +"To automatically trigger manufacturing orders for semi-finished products " +"after confirming a manufacturing order for the main product, there are two " +"options:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:55 +msgid "" +"**Option 1 (recommended):** Create *Reordering Rules* for the semi-finished " +"products and set both the minimum and maximum desired stock quantities to " +"`0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:59 +msgid ":doc:`../../purchase/products/reordering`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:61 +msgid "" +"**Option 2:** Activate the :guilabel:`Replenish on Order (MTO)` and " +":guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the " +"semi-finished product's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:64 +msgid "" +"Option 1 is more flexible than Option 2 and is therefore recommended. " +"Reordering rules do not directly link demand to replenishment, and therefore" +" allow stocks to be unreserved and redirected to other orders, if necessary." +" The Replenish on Order (MTO) route creates a unique link between the semi-" +"finished and top-level products, exclusively reserving quantities for the " +"confirmed top-level manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:70 +msgid "" +"Regardless of the method chosen, semi-finished products must be fully " +"manufactured before manufacturing can begin on the top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst-1 +msgid "A manufacturing order for a top-level product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:3 +msgid "Subcontract your Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:5 +msgid "" +"Outsourcing a portion or all of your company’s manufacturing needs is not " +"easy. To make it work correctly, you have to:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:8 +msgid "Manage the inventory of raw materials at your subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:9 +msgid "Ship raw material to your subcontractors, at the right time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:10 +msgid "Control incoming goods quality" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:11 +msgid "Control subcontractors bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:13 +msgid "" +"Here is an example of subcontracting the manufacturing of “C”, which is " +"produced out of raw materials “A” and “B”." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:20 +msgid "" +"With its MRP subcontracting feature, Odoo helps you handle this flow easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:25 +msgid "" +"To use the subcontracting feature, go to :menuselection:`Manufacturing --> " +"Configuration --> Settings` and tick the box *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:32 +msgid "" +"To define if a product must be subcontracted, use a *Bill of Materials " +"(BoM)* of type *Subcontracting*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:35 +msgid "" +"To create a new *BoM*, go to :menuselection:`Manufacturing --> Products --> " +"Bill of Materials` and hit create. Then, list the components your " +"subcontractor needs to manufacture the product. For costing purposes, you " +"might want to register all the components, even the ones that are sourced " +"directly from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:41 +msgid "" +"Once you have set the *BoM Type* to *Subcontracting*, specify one or several" +" subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:49 +msgid "Basic Subcontracting Flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:51 +msgid "" +"To let your subcontractor know how many products you need, create and send " +"them purchase orders (PO). To do so, go to the *Purchase* app and create a " +"new purchase order. Be sure to send the PO to a vendor that is defined as a " +"subcontractor on the *BoM* of these products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:60 +msgid "" +"Once the *PO* is validated (1), a pending receipt is created. When the " +"products are received, validate the receipt (2), with the actual quantity " +"received. As a result, Odoo does the following things for you:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:64 +msgid "" +"Consumes the respective components at the subcontractor’s location, based on" +" the *BoM* and your input (3);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:66 +msgid "Produces the finished goods at the subcontractor’s location (4);" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:68 +msgid "" +"Moves products from that subcontractor’s location to YourCompany via the " +"validated receipt (5)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:73 +msgid "" +"The *PO* is optional. If you create a receipt manually, with the right " +"subcontractor, Odoo still performs all the moves. This can be useful if the " +"subcontractor does not bill a fixed price per item, but rather the time and " +"materials used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:79 +msgid "Inventory Valuation" +msgstr "การประเมินมูลค่าสินค้าคงคลัง" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:81 +msgid "The cost of the manufactured product “C” is defined as:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:83 +msgid "**C = A + B + s**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:85 +msgid "With:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:87 +msgid "**A**: Cost of raw materials coming from YourCompany;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "**B**: Cost of raw materials sourced directly from the" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 +msgid "subcontractor;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:92 +msgid "**s**: Cost of the subcontracted service." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:94 +msgid "" +"Sending raw materials to your subcontractors (**A**) does not impact the " +"inventory valuation, as the components are still valued as part of your " +"stock. This is managed by making the *Subcontracting Location* an *Internal " +"Location*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:99 +msgid "" +"Then, the vendor price set on the product C form has to be what has to be " +"paid to the subcontractor for his parts and service time: **B + s**. The " +"product cost has to be: **A + B + s**, how much the product is valued in the" +" accounting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:104 +msgid "" +"Finally, the subcontractor bill then matches the purchase order, with the " +"proposed price coming from the finished products C." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:108 +msgid "" +"If managing the replenishment of raw materials **B** at your subcontractor’s" +" location is not needed, simply include the cost of **B** in the " +"subcontractor’s price **s** and remove the products *B* from the *BoM*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 +msgid "" +"In case the received products from the subcontractor contain tracked " +"components, their serial or lot numbers need to be specified during the " +"receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:120 +msgid "" +"In that case, on the receipt of the subcontracted product, a *Record " +"Components* button appears. Click on it to open a dialog box and record the " +"serial/lot numbers of the components. If the finished product is also " +"tracked, its serial/lot number can be registered here too." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:129 +msgid "" +"For audit purposes, it is possible to check the lot numbers recorded on a " +"receipt by using the icon on the right of the finished products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:136 +msgid "" +"Also note that in case flexible consumption has been selected on the " +"subcontracted BOM for a non-tracked product, the record components option " +"will also appear optionally on each move line, if you want to register more " +"or less component consumption at your subcontracting location, when " +"receiving your final product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:145 +msgid "" +"As you can see, the reception of both of these non-tracked products can " +"either be executed by selecting the 'Set Quantities' Option or via the move " +"line hamburger menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:149 +msgid "Automate Replenishment of Subcontractors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:151 +msgid "" +"There are two ways to automate the supply of raw materials to your " +"subcontractors when purchasing the final product. The chosen method depends " +"on whether or not you want the materials to transit through your warehouse. " +"Both of these methods are described as pull style mechanisms as their " +"trigger is the inital PO to the subcontractor, which creates a need at the " +"subcontracting location, for raw material." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:158 +msgid "" +"If you are supplying your subcontractor with raw material from your own " +"warehouse, you must activate the 'Resupply Subcontractor on Order' route as " +"shown below. If this is a component that you buy from a vendor, the buy " +"route should also be activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:169 +msgid "" +"Now, if you want your vendor to resupply your subcontractor directly, you " +"must choose the 'Dropship Subcontractor on Order' option instead. In order " +"for this option to be active on the product form, you must first activate " +"the dropship option from :menuselection:`Purchase --> Configuration --> " +"Settings --> Dropshipping`. Once the PO to the subcontractor is validated, " +"this route will create a dropship RFQ from your vendor to that " +"subcontractor. You then just need to review and validate it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:182 +msgid "" +"Note that the buy route is not selected in this case, as the dropship route " +"is a buy route already." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:185 +msgid "" +"Finally, if you want to track the stock of these raw materials at your " +"subcontracting location(s), then you must activate *Multi-locations* in " +":menuselection:`Inventory --> Configuration --> Settings --> Storage " +"locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:189 +msgid "From the location form, you are then able to access the Current Stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:198 +msgid "Manual Replenishment" +msgstr "การเติมสินค้าด้วยตนเอง" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:200 +msgid "You can also choose to replenish your subcontractors manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:202 +msgid "" +"If you want to send components to your subcontractor at your own " +"convenience, select the 'Resupply Subcontractor' Operation Type from the " +"*Inventory* Module, and create a picking, specifying to which subcontractor " +"you are delivering to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:210 +msgid "" +"Alternatively, you can also manually ask your vendor to resupply your " +"subcontractor by creating a dropship type PO, with your subcontractor set as" +" the delivery address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:3 +msgid "Three-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using three-step manufacturing, Odoo creates a pick " +"components transfer, a manufacturing order (MO), and a store finished " +"products transfer, and updates inventory counts based on the number of " +"components removed, and finished products created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:42 +msgid "" +"On the new |MO|, select the product to be produced from the " +":guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field " +"auto-populates with the associated Bill of Materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:53 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:54 +msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:57 +msgid "Process pick components transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:58 +msgid "" +"After confirming a three-step |MO|, a :guilabel:`Transfers` smart button " +"appears at the top of the page. Click it to be taken to the " +":guilabel:`Transfers` page for the |MO|. The page lists two transfers: " +"*WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store " +"finished products transfer)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:63 +msgid "" +"Select :guilabel:`WH/PC/XXXXX` to open the pick components transfer for the " +"|MO|. This transfer is used to track the movement of components from the " +"locations where they are stored to the location where they are used to " +"manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:64 +msgid "" +"After transferring the components out of their storage location, click " +":guilabel:`Validate` at the top of the transfer, followed by " +":guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that " +"appears. Doing so marks the transfer as :guilabel:`Done`, and updates " +"inventory counts to reflect the quantity of components transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:69 +msgid "" +"Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` " +"breadcrumb at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The manufacturing order bread crumb on a pick components transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:88 +msgid "" +"To complete work orders from the |MO| itself, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +msgid "The Start button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst-1 +msgid "The Done button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:130 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:126 +msgid "" +"Once the final work order for the |MO| has been reached, a :guilabel:`Mark " +"as Done and Close MO` button appears on the tablet view in addition to the " +":guilabel:`Mark as Done` button. Click :guilabel:`Mark as Done and Close MO`" +" to mark the |MO| as :guilabel:`Done`, and register the manufactured " +"product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:135 +msgid "" +"It is also possible to complete the final work order while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed at a later time by clicking the :guilabel:`Produce All` button on the" +" |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:140 +msgid "Process finished product transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:142 +msgid "" +"After completing the |MO|, return to the order's :guilabel:`Transfers` page " +"by clicking the :guilabel:`Transfers` button at the top of the order. This " +"time, select :guilabel:`WH/SFP/XXXXX` to open the store finished products " +"transfer. This transfer is used to track the movement of finished products " +"from the location where they were manufactured to the location where they " +"are stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:147 +msgid "" +"After transferring the finished products to their storage location, click " +":guilabel:`Validate` at the top of the transfer, followed by " +":guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that " +"appears. Doing so marks the transfer as :guilabel:`Done`, and updates " +"inventory counts to reflect the quantity of finished products transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:3 +msgid "Two-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:9 +msgid "" +"Odoo *Manufacturing* allows users to manufacture products using one, two, or" +" three steps. When using two-step manufacturing, Odoo creates a " +"manufacturing order (MO) and a pick components transfer, but does not " +"generate a transfer for the movement of finished products into stock. " +"Inventory counts still update based on the number of products manufactured, " +"but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:59 +msgid "" +"After confirming a two-step |MO|, a :guilabel:`Transfers` smart button " +"appears at the top of the page. Click it to open the pick components " +"transfer for the |MO|. This transfer is used to track the movement of " +"components from the locations where they are stored to the location where " +"they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:88 +msgid "" +"On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins " +"on the first work order that needs to be completed, click the " +":guilabel:`Start` button for that operation. Odoo *Manufacturing* then " +"starts a timer that keeps track of how long the work order takes to " +"complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The Start button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst-1 +msgid "The Done button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:109 +msgid "" +"To complete the work orders for an |MO| using the tablet view, begin by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:112 +msgid "" +"Next, click on the :guilabel:`Work Orders` tab, then select the :guilabel:`📱" +" (tablet)` button on the line of the first work order to be processed. This " +"opens the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:131 +msgid "" +"It is also possible to complete the final operation while keeping the |MO| " +"open, by clicking :guilabel:`Mark as Done`. In this case, the |MO| can be " +"closed at a later time by clicking the :guilabel:`Produce All` button on the" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 +msgid "Use the Master Production Schedule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:7 +msgid "" +"The Master Production Schedule (MPS) is a valuable tool to plan your " +"production based on your demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 +msgid "" +"Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` " +"and activate the Master Production Schedule feature before hitting save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 +msgid "" +"In the MPS settings, you can define the time range of your MPS " +"(month/week/day) and the number of periods you want to display at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 +msgid "" +"Now, go to :menuselection:`Planning --> Master Production Schedule` and " +"click on *add a product*. You can now define your safety stock target (= the" +" stock you want to have on hand at the end of the period) and the minimum " +"and maximum quantities that must or can be replenished in each period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 +msgid "" +"In the MPS view, you can decide which information you would like to display " +"by clicking on *rows*. For instance, the *Actual demand* will show you which" +" quantity of products has already been ordered for the period, or *Available" +" to Promise*, what can still be sold during that same period (what you plan " +"to replenish - what is already sold during the period). You can also decide " +"to hide rows if you like." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 +msgid "Estimate your demand and launch replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:40 +msgid "" +"The next step is to estimate the demand for the chosen period. This is done " +"in the *Forecasted Demand* Row. You can easily, at any time, compare the " +"demand forecast with the actual demand (= confirmed sales). The demand " +"forecast for a finished product will impact the indirect demand for its " +"components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 +msgid "" +"Once the forecasted demand has been set, the quantity to replenish for the " +"different periods will automatically be computed. The replenishments you are" +" supposed to launch based on your lead times (vendor lead time or " +"manufacturing lead time) are then displayed in green. You can now launch the" +" replenishment by clicking on the replenish button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 +msgid "" +"Depending on the configuration of the product (buy vs. manufacture), " +"requests for quotations or manufacturing orders will be created. You can " +"easily access those by clicking on the *Actual Replenishment* cell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 +msgid "" +"In case you manually edit the *Suggested Replenishment* quantity, a small " +"cross will appear on the left hand side of the cell. In case you want to go " +"back to the automatically computed value given by Odoo, simply click the " +"cross." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 +msgid "Cells color signification" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:69 +msgid "" +"The cells, which are part of the *Suggested Replenishment* line, can take " +"different colors depending on the situation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 +msgid "" +"**Grey**: replenishment order has already been generated, and its quantity " +"still matches current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 +msgid "" +"**Red**: replenishment order has already been generated, and its quantity " +"was too high considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 +msgid "" +"**Orange**: replenishment order has already been generated, and its quantity" +" was too low considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 +msgid "" +"The *Forecasted stock* line can also contain red cells, which means the " +"stock will be negative during the period in question." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 +msgid "What if I have underestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:86 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 +msgid "What if I have overestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:93 +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 "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 +msgid "What if I wrongly added a product to the MPS?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 +msgid "" +"You can easily remove a product from the MPS by clicking the small bin on " +"the right of its name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:3 +msgid "Manage work orders using work centers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:5 +msgid "" +"Odoo Manufacturing allows for work orders to be carried out at specific work" +" centers. When a manufacturing order is created for a product, any work " +"orders listed in the :guilabel:`Operations` tab of the product bill of " +"materials (BoM) will be automatically created as well and assigned to the " +"specified work center. Work orders can be managed in the " +":guilabel:`Manufacturing` module by selecting :menuselection:`Operations -->" +" Work Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 +msgid "" +"In order to use work centers, the :guilabel:`Work Orders` feature must first" +" be enabled. To do so, go to the :guilabel:`Manufacturing` module, select " +":menuselection:`Configuration --> Settings`, and activate the checkbox next " +"to :guilabel:`Work Orders`. Work centers can then be created and managed by " +"selecting :menuselection:`Configuration --> Work Centers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 +msgid "Create a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:19 +msgid "" +"Within the :guilabel:`Manufacturing` module, select " +":menuselection:`Configuration --> Work Centers --> Create`. The work center " +"form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 +msgid "" +":guilabel:`Work Center Name`: give the work center a concise name that " +"describes the type of operations it will be used for" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 +msgid "" +":guilabel:`Alternative Workcenters`: specify an alternative work center for " +"operations to be carried out at if the main work center is not available" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:26 +msgid ":guilabel:`Code`: assign the work center a reference code" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:27 +msgid "" +":guilabel:`Working Hours`: define the number of hours that the work center " +"can be in use each week" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:28 +msgid "" +":guilabel:`Company`: select the company that the work center belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "An example of a fully configured work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 +msgid "Set standards for work center productivity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:39 +msgid "" +"The :guilabel:`General Information` tab on the work center form allows for " +"productivity goals to be assigned to a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 +msgid "" +":guilabel:`Time Efficiency`: used to calculate the expected duration of a " +"work order at the work center; for example, if a work order normally takes " +"one hour and the efficiency is set to 200%, the work order will take 30 " +"minutes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 +msgid "" +":guilabel:`Capacity`: the number of operations that can be performed at the " +"work center simultaneously" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +msgid "" +":guilabel:`Time before prod.`: setup time required before work can commence" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +msgid "" +":guilabel:`Time after prod.`: breakdown or cleanup time required after work " +"is finished" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 +msgid "" +":guilabel:`Cost per hour`: the cost of operating the work center for one " +"hour" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 +msgid "" +":guilabel:`Analytic Account`: the account where the cost of the work center " +"should be recorded" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The general information tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 +msgid "Assign equipment to a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:60 +msgid "" +"Using the :guilabel:`Equipment` tab, it is possible for specific pieces of " +"equipment to be assigned to a work center. The following information will be" +" displayed for each piece of equipment added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +msgid "" +":guilabel:`Technician`: the technician responsible for servicing the " +"equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 +msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 +msgid "" +":guilabel:`MTBF`: mean time between failures; the average time that the " +"piece of equipment will operate before failing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 +msgid "" +":guilabel:`MTTR`: mean time to recovery; the average time it takes for the " +"equipment to become fully operational again" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 +msgid "" +":guilabel:`Est. Next Failure`: an estimate of when the next equipment " +"failure will occur" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The equipment tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 +msgid "" +":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are " +"all calculated automatically based on past failure data, if any exists." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 +msgid "Integrate IoT devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 +msgid "" +"The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT " +"(Internet of Things)` devices with a work center:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +msgid ":guilabel:`Device`: specifies the IoT device to be triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 +msgid ":guilabel:`Key`: the security key for the device" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:90 +msgid ":guilabel:`Action`: the IoT device action triggered" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The IoT Triggers tab of the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 +msgid "Use case: configure an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 +msgid "" +"When a work center is at capacity, it cannot accept any new work orders. " +"Instead of waiting for the work center to become available, it is possible " +"to specify an alternative work center where surplus work orders should be " +"carried out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 +msgid "" +"Begin by creating a new work center. Configure the :guilabel:`Equipment` tab" +" so that it has all of the same equipment as the main work center. This will" +" ensure that the same tasks can be carried out at both work centers. " +"Navigate to the main work center and include the new work center in the " +":guilabel:`Alternative Workcenters` selection field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 +msgid "" +"Now, create a new manufacturing order that uses the main work center for one" +" of its operations. The main work center will automatically be selected for " +"the operation in the :guilabel:`Work Orders` tab. After confirming the " +"manufacturing order, click the :guilabel:`Plan` button that appears at the " +"top left of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "" +"Click the plan button to automatically select an available work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 +msgid "" +"If the main work center is at capacity, the work center selected for the " +"operation will be automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst-1 +msgid "The alternative work center is automatically selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 +msgid "Monitor work center performance" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 +msgid "" +"Performance for an individual work center can be viewed by selecting " +":menuselection:`Configuration --> Work Centers`, and clicking on a work " +"center. A variety of metrics showing work center performance can be viewed " +"at the top right of the form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +msgid "" +":guilabel:`OEE`: overall effective efficiency, the percentage of time that " +"the work center has been fully productive" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 +msgid "" +":guilabel:`Load`: the amount of time it will take to complete the current " +"workload" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 +msgid "" +":guilabel:`Performance`: the real duration of work time, shown as a " +"percentage of the expected duration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 +msgid "Make work centers unavailable using Time Off" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5 +msgid "" +"In Odoo, *work centers* are used to carry out manufacturing operations at " +"specific locations. However, if a work center cannot be used for some " +"reason, work orders begin to pile up at the work center until it is " +"operational again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 +msgid "" +"As a result, it is necessary to make the work center unavailable in Odoo so " +"that the platform routes new work orders to alternative work centers that " +"are operational. Using Odoo *Time Off*, it is possible to designate a work " +"center as being unavailable for a set period of time. Doing so ensures that " +"manufacturing operations can continue until the impacted work center is " +"available again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 +msgid "" +"Before a work center can be designated as unavailable, the Odoo platform " +"must be properly configured. First, it is necessary to enable " +":ref:`developer mode <developer-mode>`. This allows the :guilabel:`Time Off`" +" smart button to appear on each work center's :guilabel:`Working Hours` pop-" +"up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 +msgid "" +"Enable developer mode by going to :menuselection:`Settings`, scrolling to " +"the bottom of the page, and clicking :guilabel:`Activate the developer mode`" +" under the :guilabel:`Developer Tools` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Activate the developer mode\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29 +msgid "" +"Next, install the *Time Off* app. This is the app used for assigning time " +"off to all resources within Odoo, including employees and work centers. " +"Navigate to :menuselection:`Apps`, then type `Time Off` in the " +":guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module " +"should be the only one that appears on the page. Click the green " +":guilabel:`Install` button on the card to install the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off module installation card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39 +msgid "" +"The last step is to properly configure work centers. For this workflow, it " +"is necessary to have at least two work centers: one that is made unavailable" +" and a second that receives the work orders that the other cannot accept. If" +" no second work center is configured, Odoo cannot route work orders away " +"from the unavailable work center and they will pile up in its queue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 +msgid "" +"To create a work center, navigate to :menuselection:`Manufacturing --> " +"Configuration --> Work Centers --> Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 +msgid "" +"Make sure that both work centers have the same equipment listed under the " +":guilabel:`Equipment` tab. This ensures that operations carried out at one " +"work center can also be performed at the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The equipment tab on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 +msgid "" +"For the work center that will be made unavailable, select the second work " +"center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo " +"knows to send work orders to the second work center when the first is " +"unavailable for any reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "A work center form configured with an alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 +msgid "Add time off for a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65 +msgid "" +"With configuration completed, time off can now be assigned to the work " +"center that will be made unavailable. Begin by navigating to " +":menuselection:`Manufacturing --> Configuration --> Work Centers` and " +"selecting the affected work center. Click :guilabel:`Edit`, and then the " +":guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` " +"drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Working Hours \"External link\" button on the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 +msgid "" +"A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard " +"working hours for the work center are listed here, along with various other " +"details about it. Since developer mode was enabled, there is a " +":guilabel:`Time Off` button in the top right of the pop-up. Click it to be " +"taken to the :guilabel:`Resource Time Off` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Time Off button on the Working Hours pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 +msgid "" +"On this page, click :guilabel:`Create` to configure a new time-off entry. On" +" the time-off form, note the :guilabel:`Reason` for the work center closure " +"(broken, maintenance, etc.), select the affected work center as the " +":guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End" +" Date` to specify the period during which the work center will be " +"unavailable. Click :guilabel:`Save` and the time off for the work center is " +"logged in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The \"Resource Time Off\" form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94 +msgid "Route orders to an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96 +msgid "" +"Once a work center is within its specified time-off period, work orders sent" +" to it can be automatically routed to an alternative work center using the " +":guilabel:`Plan` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 +msgid "" +"Begin by creating a new manufacturing order by selecting " +":menuselection:`Operations --> Manufacturing Orders --> Create`. On the " +"manufacturing order form, specify a :guilabel:`Product` that uses the " +"unavailable work center for one of its operations. Click :guilabel:`Confirm`" +" to confirm the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 +msgid "" +"On the confirmed work order, select the :guilabel:`Work Orders` tab. By " +"default, the unavailable work center is specified in the :guilabel:`Work " +"Center` column. There is also a green :guilabel:`Plan` button on the top " +"left of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "The Plan button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112 +msgid "" +"Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work " +"Orders` tab is automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst-1 +msgid "" +"The selected work center updates automatically after clicking the Plan " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 +msgid "" +"Once the time-off period for the unavailable work center ends, Odoo " +"recognizes that the work center is available again. At this point, clicking " +"the :guilabel:`Plan` button does not route work orders to an alternative " +"work center unless the first one is at capacity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:3 +msgid "Work order dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:7 +msgid "" +"When manufacturing certain products, specific operations may need to be " +"completed before others can begin. In order to ensure operations are carried" +" out in the correct order, Odoo *Manufacturing* features a *work order " +"dependencies* setting. Enabling this setting allows for operations on a Bill" +" of Materials (BoM) to be *blocked* by other operations that should occur " +"first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:15 +msgid "" +"The *work order dependencies* setting is not enabled by default. To enable " +"it, begin by navigating to :menuselection:`Manufacturing --> Configuration " +"--> Settings`. Then, enable the :guilabel:`Work Orders` setting, if it is " +"not already active." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:19 +msgid "" +"After enabling the :guilabel:`Work Orders` setting, the :guilabel:`Work " +"Order Dependencies` setting appears below it. Enable :guilabel:`Work Order " +"Dependencies`, then click :guilabel:`Save` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:24 +msgid "Add dependencies to BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:26 +msgid "" +"Work order dependencies are configured on a product's |BOM|. To do so, " +"navigate to :menuselection:`Manufacturing --> Products --> Bills of " +"Materials`, then select a |BOM|, or create a new one by clicking " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:32 +msgid "" +"For a complete guide on how to properly configure a new |BOM|, see the " +"documentation on :ref:`creating a bill of materials " +"<manufacturing/management/bill-configuration>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:35 +msgid "" +"On the |BOM|, click on the :guilabel:`Miscellaneous` tab, then enable the " +":guilabel:`Operation Dependencies` checkbox. This makes a new " +":guilabel:`Blocked By` option available in the settings of the " +":guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The Operation Dependencies checkbox on the Miscellaneous tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:43 +msgid "" +"Next, click on the :guilabel:`Operations` tab. On the top-right of the tab, " +"click on the tab's :guilabel:`settings` button, then enable the " +":guilabel:`Blocked By` checkbox. This makes a :guilabel:`Blocked By` field " +"appear for each operation on the :guilabel:`Operations` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The settings for the Operations tab on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:51 +msgid "" +"In the line of the operation that should be blocked by another operation, " +"click the :guilabel:`Blocked By` field, and an :guilabel:`Open: Operations` " +"pop-up window appears. In the :guilabel:`Blocked By` drop-down field on the " +"pop-up window, select the blocking operation that must be completed *before*" +" the operation that is blocked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The Blocked By drop-down field for an operation on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:60 +msgid "Finally, save the |BOM| by clicking :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:63 +msgid "Plan work orders using dependencies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:65 +msgid "" +"Once work order dependencies have been configured on a |BOM|, Odoo " +"*Manufacturing* is able to plan when work orders are scheduled, based on " +"their dependencies. To plan the work orders for a manufacturing order, begin" +" by navigating to :menuselection:`Manufacturing --> Operations --> " +"Manufacturing Orders`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:70 +msgid "" +"Next, select a manufacturing order for a product with work order " +"dependencies set on its |BOM|, or create a new manufacturing order by " +"clicking :guilabel:`New`. If a new manufacturing order is created, select a " +"|BOM| configured with work order dependencies from the :guilabel:`Bill of " +"Material` drop-down field, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:75 +msgid "" +"After confirming the manufacturing order, select the :guilabel:`Work Orders`" +" tab to view the work orders required to complete it. Any work orders that " +"are *not* blocked by a different work order display a `Ready` tag in the " +":guilabel:`Status` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:79 +msgid "" +"Work orders that are blocked by one or more work orders display a `Waiting " +"for another WO` tag instead. Once the blocking work order(s) are completed, " +"the tag updates to `Ready`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "The status tags for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:86 +msgid "" +"To schedule the manufacturing order's work orders, click the " +":guilabel:`Plan` button at the top of the page. After doing so, the " +":guilabel:`Scheduled Start Date` field for each work order on the " +":guilabel:`Work Orders` tab auto-fills with the scheduled start date and " +"time. A blocked work order is scheduled at the end of the time period " +"specified in the :guilabel:`Expected Duration` field of the work order that " +"precedes it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "" +"The Scheduled Start Date field for work orders on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:97 +msgid "" +"A manufacturing order is created for Product A. The manufacturing order has " +"two operations: Cut and Assemble. Each operation has an expected duration of" +" 60 minutes, and the Assemble operation is blocked by the Cut operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:101 +msgid "" +"The :guilabel:`Plan` button for the manufacturing order is clicked at 1:30 " +"pm, and the Cut operation is scheduled to begin immediately. Since the Cut " +"operation has an expected duration of 60 minutes, the Assemble operation is " +"scheduled to begin at 2:30 pm." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:106 +msgid "Planning by workcenter" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:108 +msgid "" +"To see a visual representation of how work orders are planned, navigate to " +"the :guilabel:`Work Orders Planning` page by going to " +":menuselection:`Manufacturing --> Planning --> Planning by Workcenter`. This" +" page shows a timeline of all the work orders scheduled for each operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:112 +msgid "" +"If one work order is blocked by the completion of another, the work order " +"that is blocked is shown as scheduled to start after the work order blocking" +" it. In addition, an arrow connects the two work orders, leading from the " +"blocking operation to the blocked operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst-1 +msgid "" +"The arrow connecting a blocked work order to the work order blocking it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 +msgid "Shop Floor" +msgstr "พื้นที่ผลิต" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:3 +msgid "Shop Floor overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:9 +msgid "" +"The *Shop Floor* module is a companion module to the *Manufacturing* app. " +"*Shop Floor* provides a visual interface for processing manufacturing orders" +" (MOs) and work orders. It also allows manufacturing employees to track the " +"amount of time spent working on manufacturing and work orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:13 +msgid "" +"The *Shop Floor* module is installed alongside the *Manufacturing* app. It " +"cannot be installed by itself. To install the *Manufacturing* app, navigate " +"to :menuselection:`Apps`, search for `manufacturing` in the " +":guilabel:`Search...` bar, and then click :guilabel:`Install` on the " +":guilabel:`Manufacturing` app card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:19 +msgid "" +"The *Shop Floor* module replaces the tablet view functionality of the " +"*Manufacturing* app, and is only available in Odoo versions 16.4 and later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:22 +msgid "" +"To check the version number of an Odoo database, navigate to " +":menuselection:`Settings` and scroll down to the :guilabel:`About` section " +"at the bottom of the page. The version number is displayed there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:26 +msgid "" +"To switch to a newer version of Odoo, see the documentation on " +":ref:`upgrading a database <administration/upgrade>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:30 +msgid "Navigation" +msgstr "การนำทาง" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:32 +msgid "" +"*Shop Floor* is broken down into three main views, which can be selected " +"from the navigation bar at the top of the module:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:35 +msgid "" +"The :guilabel:`All` page serves as the main dashboard for the module, and " +"displays information cards for |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:37 +msgid "" +"Each work center also has a dedicated page, which shows information cards " +"for work orders assigned to that work center. Work center pages can be " +"toggled on or off by clicking the :guilabel:`+ (plus)` button in the " +"navigation bar, selecting or deselecting them on the pop-up window that " +"appears, and then clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:41 +msgid "" +"The :guilabel:`My` page shows information cards for all work orders assigned" +" to the employee whose profile is currently active in the operator panel on " +"the left side of the module. Other than only showing work orders assigned to" +" the active employee, this page functions the same as the pages for each " +"work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:47 +msgid "" +"To isolate an |MO| or work order, so that no other orders appear, simply " +"search the reference number of the |MO| in the :guilabel:`Search...` bar at " +"the top of the module. This search filter remains active while switching " +"between the different module views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:51 +msgid "" +"On the left side of the module is the operator panel, which shows all of the" +" employees currently signed in to *Shop Floor*, and allows new employees to " +"sign in. The operator panel is always available in the module, regardless of" +" which view is selected. It can be toggled on or off by clicking the " +":guilabel:`sidebar` button at the extreme left of the navigation bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"The \"sidebar\" button, which is used to toggle the operator panel on or " +"off." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:61 +msgid "All page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:63 +msgid "" +"By default, the :guilabel:`All` page shows an information card for every " +"|MO| that is *ready to start*. An |MO| is considered ready to start once it " +"has been confirmed, and all required components are available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:67 +msgid "" +"To view every confirmed |MO| regardless of readiness, click the " +":guilabel:`x` button on the :guilabel:`Ready to Start` filter to remove it " +"from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:71 +msgid "MO information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:73 +msgid "" +"An |MO| information card on the :guilabel:`All` page shows all of the " +"relevant details of the associated |MO|, and also provides employees with " +"options for processing the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:76 +msgid "" +"The header for an |MO| card shows the |MO| number, the product and number of" +" units being produced, and the status of the |MO|. If work has not yet begun" +" on the |MO|, the status appears as :guilabel:`Confirmed`. Once work has " +"begun, the status updates to :guilabel:`In Progress`. If all work orders for" +" an |MO| have been completed and the |MO| is ready to close, the status " +"updates to :guilabel:`To Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:82 +msgid "" +"The main body of an |MO| card shows a line for each completed work order, if" +" any, followed by the current work order that needs to be completed. " +"Completed work orders are indicated by a green check mark to the right of " +"title of the work order. The current work order is indicated by a button " +"that opens the page for the work center to which the order is assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:87 +msgid "" +"Below the current work order is a line titled :guilabel:`Register " +"Production`, which is used to record the number of product units produced. " +"To manually enter the number of units produced, click on the " +":guilabel:`Register Production` line, enter a value in the :guilabel:`Units`" +" field of the resulting pop-up window, then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:92 +msgid "" +"Alternatively, click the :guilabel:`# Units` button on the right side of the" +" line, which automatically records the number of units the |MO| was created " +"for as the number of units produced. For example, if an |MO| is created for " +"10 units of a dining table, clicking the :guilabel:`10 units` button records" +" that 10 units were produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:97 +msgid "" +"The footer of the |MO| card displays a :guilabel:`Close Production` button. " +"This is used to close the |MO| once production is completed. However, if " +"there are any quality checks required for the |MO| as a whole (not the work " +"orders within it), a :guilabel:`Quality Checks` button appears instead. " +"Clicking :guilabel:`Quality Checks` opens a pop-up window, from which any " +"required quality checks can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:103 +msgid "" +"After clicking :guilabel:`Close Production`, the |MO| card begins to fade " +"away, and an :guilabel:`Undo` button appears on the footer. Clicking " +":guilabel:`Undo` causes the |MO| to remain open. Once the |MO| card " +"disappears completely, the work order is closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:107 +msgid "" +"On the right side of the footer is an :guilabel:`⋮ (options)` button, which " +"opens a pop-up window with additional options for the |MO|:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:171 +msgid "" +":guilabel:`Scrap` is used to send components to a scrap location when they " +"are found to be defective." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:112 +msgid "" +":guilabel:`Add Work Order` is used to add an additional work order to the " +"|MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:173 +msgid "" +":guilabel:`Add Component` is used to add an additional component to the " +"|MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:114 +msgid ":guilabel:`Open Backend MO` opens the |MO| in the Manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"An information card for an MO on the \"All\" page of the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:121 +msgid "Work center pages" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:123 +msgid "" +"By default, the page for each work center shows an information card for " +"every work order assigned to it that is *ready to start*. A work order is " +"considered ready to start once the |MO| it is a part of is ready to start, " +"and any preceding work orders have been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:127 +msgid "" +"To view every confirmed work order assigned to a work center regardless of " +"readiness, click the :guilabel:`x` button on the :guilabel:`Ready to Start` " +"filter to remove it from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:132 +msgid "Work order information card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:134 +msgid "" +"A work order information card on a work center's page shows all of the " +"relevant details of the associated work order, and also provides employees " +"with options for processing the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:137 +msgid "" +"The header for a work order card shows the reference number of the |MO| that" +" the work order is a part of, the product and number of units being " +"produced, and the status of the work order. If work has not yet begun on the" +" work order, the status appears as :guilabel:`To Do`. Once work has begun, " +"the status updates to display a timer showing the total time the work order " +"has been worked on." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:142 +msgid "" +"The main body of a work order card shows a line for each step required to " +"complete the work order. Work order steps can be completed by clicking on " +"the line, then following the instructions on the pop-up window that appears." +" Alternatively, clicking the checkbox on the right side of each line " +"automatically marks the step as completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:147 +msgid "" +"Below the final step of the work order is a line titled :guilabel:`Register " +"Production`, which functions the same as the :guilabel:`Register Production`" +" line on an |MO| card. Registering the number of units produced using the " +":guilabel:`Register Production` line on a work order card also completes the" +" step for the associated |MO| card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:152 +msgid "" +"If the work order being processed is the final work order for the |MO|, a " +":guilabel:`Close Production` button appears on the footer of the work order " +"card. Clicking :guilabel:`Close Production` closes both the work order and " +"the |MO|, unless a quality check is required for the |MO|. In this case, the" +" quality check must be completed from the |MO| card before the |MO| can be " +"closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:158 +msgid "" +"Alternatively, if the |MO| requires the completion of additional work " +"orders, a :guilabel:`Mark as Done` button appears instead. Clicking " +":guilabel:`Mark as Done` marks the current work order as completed, and " +"causes the next work order to appear on the page for the work center it is " +"assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:163 +msgid "" +"After clicking :guilabel:`Close Production` or :guilabel:`Mark as Done`, the" +" work order card begins to fade away, and an :guilabel:`Undo` button appears" +" on the footer. Clicking :guilabel:`Undo` causes the work order to remain " +"open. Once the work order card disappears completely, the work order is " +"marked as :guilabel:`Finished` on the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:168 +msgid "" +"On the right side of the footer is an :guilabel:`⋮ (options)` button, which " +"opens a pop-up window with additional options for the work order:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:174 +msgid "" +":guilabel:`Move to work center` is used to transfer the work order to a " +"different work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:175 +msgid "" +":guilabel:`Suggest a Worksheet improvement` allows the user to propose a " +"change to the work order's instructions or steps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:177 +msgid "" +":guilabel:`Create a Quality Alert` opens a quality alert form that can be " +"filled out to alert a quality team about a potential issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "An information card for a work order in the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:185 +msgid "Operator panel" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:187 +msgid "" +"The operator panel is used to manage the employees that are signed in to the" +" *Shop Floor* module. The panel shows the name and profile picture of every " +"employee that is currently signed in across all instances of the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:191 +msgid "" +"To interact with *Shop Floor* as a specific employee, click the employee's " +"name to activate their profile. Profiles that are not active appear with " +"their names and profile pictures greyed-out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:194 +msgid "" +"When an employee is selected in the operator panel, they can begin working " +"on a work order by clicking the work order's heading. If an employee is " +"working on one or more work orders, the work order title(s) appear under " +"their name, along with a timer showing how long they've been working on each" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:199 +msgid "" +"To add a new employee to the operator panel, click the :guilabel:`+ Add " +"Operator` button at the bottom of the panel. Then, select an employee from " +"the :guilabel:`Select Employee` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:202 +msgid "" +"To remove an employee from the operator panel, simply click the " +":guilabel:`x` button next to their name in the panel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst-1 +msgid "" +"The operator panel of the Shop Floor module, showing three employees signed " +"in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:8 +msgid "Product lifecycle management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:10 +msgid "" +"Odoo *Product Lifecycle Management* (*PLM*) offers a systematic approach for" +" testing, collaboration, and iteration of products across concept " +"development, design, manufacturing, marketing, and post-launch support " +"stages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm.rst:14 +msgid "" +"With approvals, key stakeholders can review changes before implementation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes.rst:3 +msgid "Change management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:10 +msgid "ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:12 +msgid "" +"An *ECO type* is assigned to *engineering change orders* (ECOs) to organize " +"and track changes to products and bills of materials (BoMs). Each |ECO| type" +" separates |ECOs| into a project in Gantt view, ensuring collaborators and " +"stakeholders **only** view and assist with relevant |BOM| improvements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:17 +msgid "" +"For example, an electronic chip manufacturer might use 'New Product " +"Introduction', 'Product Improvement', 'Component Change', and 'Firmware " +"Update' |ECO| types. Then, designers and engineers can focus on |ECOs| in " +"the 'New Product Introduction' and 'Product Improvement' projects, avoiding " +"unrelated supplier change or firmware update |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:23 +msgid "Create ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:25 +msgid "" +"To access and manage ECO types, navigate to :menuselection:`PLM app --> " +"Configuration --> ECO Types`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:28 +msgid "" +"Create a new ECO type by clicking :guilabel:`New`. On the new :guilabel:`ECO" +" Types` form, fill in the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:31 +msgid "" +":guilabel:`Name`: the name of the |ECO| type, which will organize all of the" +" |ECOs| of this *type* in a project." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:33 +msgid "" +":guilabel:`Email Alias`: if this optional field is filled, emails submitted " +"to this email address automatically generate |ECOs| in the left-most stage " +"of this |ECO| type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:37 +msgid "" +"The `Formulation change` |ECO| type is used to organize and track related " +"|ECOs| in a single project. Configuring the :guilabel:`Email Alias` field " +"generates |ECOs| in the `Formulation change` project sent to the email " +"address, `pawlish-change@pawlished-glam.odoo.com`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Example of an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:46 +msgid "Edit ECO type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:48 +msgid "" +"Modify existing |ECO| type names and email aliases by navigating to the " +":menuselection:`PLM app --> Configuration --> ECO Types` page. There, click " +"on the desired |ECO| type from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:51 +msgid "" +"On the form for each |ECO| type, proceed to edit the :guilabel:`Name` and " +":guilabel:`Email Alias` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:57 +msgid "Stages" +msgstr "ขั้นตอน" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:59 +msgid "" +"Within an |ECO| type project, *stages* are like milestones and are used to " +"identify the progress of the |ECO| before the changes are ready to be " +"applied. (e.g. 'Feedback', 'In Progress', 'Approved', 'Complete')" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:63 +msgid "" +"Additionally, required approvers can be added to each stage, ensuring that " +"changes to the production |BOM| cannot proceed until the approver reviews " +"and approves the |ECO|. Doing so prevents errors on the production |BOM| by " +"enforcing at least one review of suggested changes before they're applied on" +" a production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:68 +msgid "" +"For best practice, there should be at least one *verification* stage, which " +"is a stage with a required approver, and one *closing* stage, which stores " +"|ECOs| that have been either canceled or approved for use as the next " +"production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:73 +msgid "Create stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:75 +msgid "" +"To add a stage, go to the :menuselection:`PLM` app and select the intended " +"project for an |ECO| type from the :guilabel:`PLM Overview` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:78 +msgid "" +"Then, on the :guilabel:`Engineering Change Orders` project pipeline for the " +"|ECO| type, click the :guilabel:`+ Stage` button. Doing so reveals a text " +"box to fill in the name of the stage. After filling it in, click the " +":guilabel:`Add` button to finish adding the stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:83 +msgid "" +"A new `Assigned` stage separates assigned |ECOs| from the unassigned ones in" +" the `New` stage. Adding another stage helps the product manager track " +"unassigned tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Create a new stage in a project for an ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:91 +msgid "Verification stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:93 +msgid "" +"Click an ECO type from :menuselection:`PLM app --> Overview` to open a " +"kanban view of |ECOs| of this type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:96 +msgid "" +"To configure a verification stage, hover over the intended stage, and select" +" the :guilabel:`⚙️ (gear)` icon. Then, click :guilabel:`Edit` to open a pop-" +"up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:99 +msgid "" +"Configure the verification stage in the edit stage pop-up window, by " +"checking the box for :guilabel:`Allow to apply changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:102 +msgid "" +"Then, add an approver in the :guilabel:`Approvers` section, by clicking " +":guilabel:`Add a line`, and specifying the :guilabel:`Role` of the reviewer," +" their :guilabel:`User`, and :guilabel:`Approval Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:106 +msgid "" +"Make sure at least one approver is configured with the :guilabel:`Approval " +"Type`: :guilabel:`Is required to approve`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:109 +msgid "" +"The approver listed is automatically notified when |ECOs| are dropped in the" +" stage specified in the pop-up window. Once finished, click :guilabel:`Save " +"& Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:113 +msgid "" +"In the |ECO| type `New Product Introduction`, the verification stage " +"`Validated` is configured by clicking the :guilabel:`⚙️ (gear)` icon, and " +"selecting :guilabel:`Edit`. Doing so opens the :guilabel:`Edit: Validated` " +"pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:117 +msgid "" +"By adding the `Engineering manager` as an approver, only |ECOs| approved by " +"this user can proceed to the next stage, and have the changes applied on the" +" production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:120 +msgid "" +"Additionally, check the :guilabel:`Allow to apply changes` option to ensure " +"proper behavior." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:0 +msgid "Show \"Allow to apply changes\" option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:127 +msgid "Closing stage" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:129 +msgid "" +"Configure a closing stage by opening the :guilabel:`Edit: [stage]` pop-up " +"window. To do so, hover over the intended stage and click the :guilabel:`⚙️ " +"(gear)` icon that appears in the top-right corner. Then, click " +":guilabel:`Edit` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:133 +msgid "" +"On the :guilabel:`Edit: [stage]` pop-up window, select the check boxes for " +":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes` and " +":guilabel:`Final Stage`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst:137 +msgid "" +"The closing stage, `Effective` is configured by checking the " +":guilabel:`Folded in kanban view`, :guilabel:`Allow to apply changes`, and " +":guilabel:`Final Stage` options" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst-1 +msgid "Show configurations of the closing stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:3 +msgid "Engineering change orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:12 +msgid "" +"Utilize *engineering change orders* (*ECOs*) to track, implement, and revert" +" change versions made to products, and :ref:`bills of materials " +"<manufacturing/management/bill-configuration>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:15 +msgid "Engineering change orders can be created:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:17 +msgid ":ref:`directly in the ECO type <plm/eco/create-eco>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:18 +msgid "" +"by an operator in the :ref:`tablet view <plm/eco/tablet-view>` of an " +"operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:19 +msgid "" +"automatically from feedback submitted to the :ref:`ECO type's email alias " +"<plm/eco/eco-type>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:24 +msgid "Create ECO" +msgstr "สร้าง ECO" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:26 +msgid "" +"To create a new |ECO|, begin by navigating to the *PLM* app. Then, select " +"the |ECO| type card that will be used to track the progress of the change. " +"On the :guilabel:`Engineering Change Orders` page, click the :guilabel:`New`" +" button in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:31 +msgid "" +"Learn how to create new :ref:`ECO types <plm/eco/eco-type>` to categorize " +"and organize change orders. Doing so ensures employees only view the |ECOs| " +"related to their responsibilities, whether it involves new product " +"introductions, targeted product line updates, or regulatory compliance " +"fulfillment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:36 +msgid "On the |ECO| form, fill in the following fields accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:38 +msgid ":guilabel:`Description` is a brief summary of the improvement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:39 +msgid "" +":guilabel:`Type`: specifies the |ECO| type project for organizing the " +"|ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:40 +msgid "" +":guilabel:`Apply on` determines if the |ECO| changes the :guilabel:`Bill of " +"Materials` or the :guilabel:`Product Only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:42 +msgid ":guilabel:`Product` indicates the product being improved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:43 +msgid "" +":guilabel:`Bill of Materials` specifies the changed |BOM|. It auto-populates" +" if the product in :guilabel:`Product` field has an existing |BOM|. If " +"multiple |BOMs| exist, select the intended radio options from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:46 +msgid "" +":guilabel:`Company` field is used in multi-company databases. Specify if the" +" change applies to products in a specific company, or leave blank if the " +"change applies to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:48 +msgid "" +":guilabel:`Responsible` represents the assignee in charge of this |ECO|. " +"(Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:49 +msgid "" +":guilabel:`Effective` specifies when the |ECO| becomes live. Choosing " +":guilabel:`As soon as possible` means the |ECO| applies to the production " +"|BOM| as soon as an authorized user :ref:`applies the changes " +"<plm/eco/apply-changes>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:53 +msgid "" +"On the other hand, choosing :guilabel:`At Date`, and setting a specific " +"date, leaves a date that makes it easier to track the version history of the" +" |BOM|, and the specific date |BOMs|, used for production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:56 +msgid "" +":guilabel:`Tags` are assigned to |ECOs| for prioritization and organization." +" Create a new tag by typing the name in the field and selecting " +":guilabel:`Create` from the drop-down menu. (Optional)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:59 +msgid "" +"After filling out the |ECO| form, click the :guilabel:`Start Revision` " +"button to begin implementing the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:62 +msgid "By pressing :guilabel:`Start Revision`, three actions occur:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:64 +msgid "" +"The :guilabel:`Documents` smart button appears, storing relevant files of " +"the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:65 +msgid "" +"A copy of the production |BOM| is stored in the newly-appeared " +":guilabel:`Revision` smart button of the |ECO|. The next available version " +"number (e.g., `V2`, `V3`, ...) is also assigned to keep track of all |BOM| " +"versions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:68 +msgid "" +"The stages of the |ECO| :guilabel:`Type` are displayed in the top-right " +"corner of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:71 +msgid "" +"The :guilabel:`Revision` smart button is available **only** when the " +":guilabel:`Bill of Materials` radio button is selected in the " +":guilabel:`Apply on` field, and the :guilabel:`Start Revision` button has " +"been pressed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "" +"ECO with overview of stages in the top-right corner, and *Revision* smart " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:80 +msgid "Change components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:82 +msgid "" +"To modify the components in a |BOM|, click the :guilabel:`Revision` smart " +"button on an |ECO| to access the new version of the |BOM|. Odoo " +"distinguishes the non-production version of the |BOM| from the current " +"version, by flagging the test |BOM| with a large :guilabel:`Archived` tag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:87 +msgid "" +"After clicking the :guilabel:`Start Revision` button for an |ECO| for the " +"product, `[D_0045 Stool]`, make changes to the product's |BOM| by clicking " +"the :guilabel:`Revision` smart button. Doing so opens the archived |BOM|, " +"marked with a large red :guilabel:`Archived` flag." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show the archived Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:95 +msgid "" +"On the new |BOM|, in the :guilabel:`Components` tab, proceed to modify the " +"components list, by changing the :guilabel:`Quantity` of existing " +"components, adding new components using the :guilabel:`Add a line` button, " +"and removing components with the :guilabel:`🗑️ (trash)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:102 +msgid "" +"In version two of the |BOM| for a keyboard, the component quantities are " +"reduced, and an additional component, `Stabilizers`, is added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Make changes to components by going to the new BoM with the *Revision* smart" +" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:110 +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:153 +msgid "Compare changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:112 +msgid "" +"Once the changes are complete, navigate back to the |ECO|, by clicking " +"`ECO00X` in the breadcrumbs located in the top-left corner. On the |ECO| " +"form, a new :guilabel:`BoM Changes` tab displays the differences between the" +" current |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:116 +msgid "" +"Blue text indicates new components added to the revised |BOM| that are not " +"in the production |BOM|. Black text represents updates shared by both " +"|BOMs|, while red text indicates components removed in the revised |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:120 +msgid "" +"Changes and tests are encapsulated in the revised |BOM|, and do **not** " +"affect the |BOM| currently used in production. That is, until the " +":ref:`changes are applied <plm/eco/apply-changes>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:124 +msgid "" +"View the summary of the differences between the current and revised keyboard" +" |BOMs| in the :guilabel:`BoM Changes` tab of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View summary of component changes in the *BoM Changes* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:132 +msgid "Change operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:134 +msgid "" +"To modify the operations in a |BOM|, click the :guilabel:`Revision` smart " +"button on an |ECO| to access the archived, new version of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:137 +msgid "" +"In the new |BOM| version, switch to the :guilabel:`Operations` tab to view " +"and edit |BOM| operations. To make changes, select each operation, which " +"opens the corresponding :guilabel:`Open: Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:142 +msgid "" +"The :guilabel:`Operations` tab is *not* available by default. To enable it, " +"navigate to :menuselection:`Manufacturing app --> Configuration --> " +"Settings`, and check the :guilabel:`Work Orders` box." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:146 +msgid "" +"Make changes to any of the fields in the :guilabel:`Open: Operations` pop-up" +" window, then click :guilabel:`Save` once completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:149 +msgid "" +"Create new operations by clicking the :guilabel:`Add a line` button, and " +"remove new operations by clicking the :guilabel:`Archive Operation` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:155 +msgid "" +"Once the changes are complete, navigate back to the |ECO|, by clicking " +"`ECO00X` in the breadcrumbs located in the top-left corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:158 +msgid "" +"On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the " +"differences between the current production |BOM| and the new version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:161 +msgid "" +"Blue text indicates new operations added to the revised |BOM| that do not " +"yet exist in the production |BOM|. Black text represents updates shared by " +"both |BOMs|, while red text indicates operations removed in the revised " +"|BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:165 +msgid "" +"Modifications to the |BOM| in an |ECO| will **not** affect the |BOM| used in" +" production. That is, until the :ref:`changes are applied <plm/eco/apply-" +"changes>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:168 +msgid "" +"In the :guilabel:`Operation Changes` tab, each row of details, beneath the " +"columns in the table, reflect the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:171 +msgid ":guilabel:`Operation`: Name of the operation that was modified." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:172 +msgid "" +":guilabel:`Step`: specifies the quality control point, visible when the " +"operation includes detailed instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:176 +msgid "" +"To check for instructions, click the operation line item in the " +":guilabel:`Operations` tab of a |BOM|. Then, in the :guilabel:`Open: " +"Operations` pop-up window, look for the :guilabel:`Instructions` smart " +"button displayed at the top." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:181 +msgid "" +"The `Assembly` :guilabel:`Operation` includes `10` detailed " +":guilabel:`Instructions` to complete it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Show *Instructions* smart button to check whether an operation has additional\n" +"instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:189 +msgid "" +":guilabel:`Step Type` details the type of quality control for further " +"instructions in the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:191 +msgid "" +":guilabel:`Type` corresponds with the colored text to specify how the " +"revised |BOM| differs from the production |BOM|. Operation change types can " +"be :guilabel:`Add`, :guilabel:`Remove`, or :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:194 +msgid "" +":guilabel:`Work Center` specifies the work center at which the operation is " +"performed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:195 +msgid "" +":guilabel:`Manual Duration Change` refers to the change in the " +":guilabel:`Default Duration` field in the :guilabel:`Open: Operations` pop-" +"up window, which specifies the expected time for completing the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:200 +msgid "" +"The :guilabel:`Operation Changes` tab compares the production |BOM| with the" +" revised |BOM| in the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:203 +msgid "" +"In the revised |BOM|, a new `Assembly` :guilabel:`Operation` at the " +":guilabel:`Work Center` `Assembly Line 1` is added. In addition, the " +"expected duration of the operation is `20.00` minutes, as specified by the " +":guilabel:`Manual Duration Change`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:207 +msgid "" +"To supplement the `Assembly` operation, two quality control point " +"instructions are added:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:209 +msgid "" +"The first is the :guilabel:`Step` `QCP00039`, a :guilabel:`Step Type` to " +":guilabel:`Register Production` of components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:211 +msgid "" +"The second :guilabel:`Step` is `QCP00034`, an `Instructions` :guilabel:`Step" +" Type` that provides additional assembly details." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Show *Operation Changes* tab in an |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:221 +msgid "Apply changes" +msgstr "ใช้การเปลี่ยนแปลง" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:223 +msgid "" +"After verifying the changes, move the |ECO| to a :ref:`verification stage " +"<plm/eco/stage-config>`, which are stages that require approval before the " +"revised changes can be applied to the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:227 +msgid "" +"Once the approvers accept the changes, the :guilabel:`Apply Changes` button " +"becomes available. Click this button, and the |ECO| is automatically moved " +"to a closing stage. The changes are applied, which archives the original " +"production |BOM|, and the revised |BOM| becomes the new production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:232 +msgid "Verify changes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:234 +msgid "" +"To ensure the changes are live, from the |ECO| where the :guilabel:`Apply " +"Changes` button was just pressed, return to the revised |BOM| by clicking " +"the :guilabel:`Revision` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:237 +msgid "" +"On the revised |BOM|, the large red :guilabel:`Archived` flag is removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:239 +msgid "" +"To further verify the changes, check the production |BOM| by going to " +":menuselection:`Manufacturing app --> Products --> Products` and select the " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:242 +msgid "" +"Then, on the product form, click the :guilabel:`Bill of Materials` smart " +"button, and select the |BOM| from the list. In the :guilabel:`Miscellaneous`" +" tab of the |BOM|, the :guilabel:`Version` field is updated to match the " +"version number shown on the :guilabel:`Revision` smart button of the latest " +"|ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:248 +msgid "" +"After applying the changes of the |ECO| for the :ref:`keyboard " +"<plm/eco/example-keyboard>`, view the version of the current keyboard |BOM| " +"in the :guilabel:`Miscellaneous` tab. Here, the :guilabel:`Version` number " +"has been updated to `2`, matching the `V2` that appears in the " +":guilabel:`Revision` smart button of the |ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "View current *BOM* version in the Miscellaneous tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:260 +msgid "Create ECO from tablet view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:262 +msgid "" +"Operators can directly suggest clearer operation instructions, while " +"performing manufacturing orders (MOs) in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:265 +msgid "" +"To create |ECOs| in this manner, begin by navigating to " +":menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. " +"Then, select the desired :abbr:`MO (Manufacturing Order)` and switch to the " +":guilabel:`Work Orders` tab. Then, click the :guilabel:`📱 (mobile phone)` " +"icon for the desired work order to open the *tablet view* of the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:271 +msgid "" +"The :guilabel:`📱 (mobile phone)` icon is **only** available for :abbr:`MOs " +"(Manufacturing Orders)` with a :guilabel:`Confirmed` or :guilabel:`In " +"Progress` status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "Find the tablet icon for each operation, second from the far right." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:278 +msgid "" +"Next, add an instructional step, by clicking the :guilabel:`☰ (three " +"horizontal lines)` icon in the tablet view of an operation. Doing so opens " +"the :guilabel:`Menu` of action items for a :abbr:`MO (Manufacturing Order)`." +" Then, click the :guilabel:`Add a step` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "" +"Open the *Add a Step* pop-up by clicking the three horizontal lines icon in " +"tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:286 +msgid "" +"Clicking the button reveals an :guilabel:`Add a step` pop-up window, where " +"the proposed changes are submitted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:289 +msgid "" +"In the :guilabel:`Title` field, enter a short step description. Next, in the" +" :guilabel:`Instruction` text field, type the instructions of the step in " +"greater detail. Optionally, add an image to the :guilabel:`Document` field. " +"Once completed, finish by clicking the :guilabel:`Propose Change` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:295 +msgid "" +"To propose an additional check for broken components, enter the details in " +"the :guilabel:`Add a Step` pop-up window. Doing so creates an instructional " +"quality control point that will be reviewed in the following section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Fill out the *Add a Step* form to suggest an additional quality control " +"point." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:303 +msgid "" +"Based on the inputs from the :guilabel:`Add a Step` pop-up window, an |ECO| " +"is created with the following information:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:306 +msgid "" +":guilabel:`Description` is the name of the operation, followed by the " +":abbr:`MO (Manufacturing Order)` number for reference." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:308 +msgid "The |ECO| :guilabel:`Type` is automatically assigned to `BOM Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:309 +msgid "" +":guilabel:`Product` and :guilabel:`Bill of Materials` fields are " +"automatically populated, based on the |BOM| used in the :abbr:`MO " +"(Manufacturing Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:311 +msgid ":guilabel:`Responsible` is the operator who submitted the feedback." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:314 +msgid "View ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:316 +msgid "" +"To review the proposed changes, navigate to the :menuselection:`PLM app --> " +"Overview`. In the `BOM Updates` |ECO| type card, the :guilabel:`X " +"Engineering Changes` button represents the amount of operational changes " +"created from the tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:320 +msgid "" +"Click on the :guilabel:`X Engineering Changes` button to open the kanban " +"view of the |ECO| type. To view the suggestion, select an |ECO| in the `New`" +" stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:323 +msgid "" +"On the |ECO|, view a summary of the proposed changes in the " +":guilabel:`Operation Changes` tab. Click the :guilabel:`Revision` smart " +"button to navigate to the revised |BOM| and look into the proposed changes " +"in greater detail." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:328 +msgid "" +"An operator suggested another check for broken components by adding a step " +"from the tablet view, while performing the `Assemble switches` operation for" +" the :abbr:`MO (Manufacturing Order)` `WH/MO/00010` for the product, " +"`Keyboard`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:332 +msgid "" +"Then, this created |ECO| can be viewed by navigating to the `BOM Changes` " +"ECO type found in :menuselection:`PLM app --> Overview`. By default, |ECOs| " +"created from tablet view are set to spawn in the `New` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:336 +msgid "" +"The :guilabel:`Responsible` field is assigned to the operator who made the " +"suggestion, allowing the employee revising the |BOM| to seek further " +"clarification from the person who proposed the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "Find the new ECO in the \"BOM Changes\" ECO type, in the *New* stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:344 +msgid "" +"On the revised |BOM|, switch to the :guilabel:`Operations` tab, and select " +"the :guilabel:`☰ (three horizontal lines)` icon. Doing so opens a list of " +":guilabel:`Steps` to perform the operation, with the newest instruction " +"titled `New Step Suggestion:`, followed by the user-entered title. Click the" +" line item to view the suggested changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst-1 +msgid "\"Show Instructions\" icon in the *Operations* tab of a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:353 +msgid "" +"On the :ref:`quality control point <quality/quality_management/quality-" +"control-points>` form, ensure the following form fields are accurately " +"filled out to give detailed instructions for operators:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:356 +msgid "" +":guilabel:`Title`: rename to give a concise description of the new " +"instruction." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:357 +msgid "" +":guilabel:`Control per`: using the drop-down menu, determine whether this " +"instruction applies broadly for the :guilabel:`Product`, specifically for " +"this :guilabel:`Operation` *only*, or a particular :guilabel:`Quantity` of " +"the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:360 +msgid "" +":guilabel:`Type`: categorizes the control point type. From the drop-down " +"menu, select :guilabel:`Instructions` to detail an instruction for the " +"worker. To receive input from the workers, select the :guilabel:`Take a " +"Picture`, :guilabel:`Register Consumed Materials`, :guilabel:`Print Label`, " +"or other :ref:`quality check options <quality/quality_management/quality-" +"control-points>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:367 +msgid "" +":ref:`Configure quality control points <quality/quality_management/quality-" +"control-points>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:369 +msgid "" +"Once the quality control point is configured, return to the " +":guilabel:`Steps` list using the breadcrumbs. Finally, drag the last quality" +" control line item to its intended order of instructions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:373 +msgid "" +"Drag and reorder the `Check for broken switches` instruction, by clicking " +"and dragging its \"6 dots\" icon to move it from the bottom to the second " +"position." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst:0 +msgid "" +"Drag and reorder instructions by selecting the \"6 dots\" icon on the far " +"left." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:3 +msgid "Version control" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:10 +msgid "" +"Use Odoo's *Product Lifecycle Management (PLM)* to manage previous versions " +"of bills of materials (BoMs). Store former assembly instructions, component " +"details, and past product design files while keeping the past details out of" +" the production |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:14 +msgid "" +"Easily revert to previous |BOM| versions, when needed. Additionally, use " +"*PLM* to trace which |BOM| version was active on specific dates for recalls " +"or customer complaints." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:17 +msgid "" +"Every |BOM| version is stored in an *engineering change order* (ECO) for " +"organized testing and improvements without disrupting normal manufacturing " +"operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:21 +msgid ":ref:`Engineering change order <plm/eco>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:24 +msgid "Current BoM version" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:26 +msgid "" +"To see the current version of the |BOM| used in production, go to " +":menuselection:`PLM app --> Master Data --> Bill of Materials`, and select " +"the desired |BOM| from the list. Then, switch to the " +":guilabel:`Miscellaneous` tab, where the currently live :guilabel:`Version` " +"of the |BOM| is displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:32 +msgid "" +"|BOMs| can also be accessed from :menuselection:`Manufacturing app --> " +"Products --> Bill of Materials`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show the current version BOM in the Misc tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:40 +msgid "Version history" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:42 +msgid "" +"To manage all former, current, and future versions of a |BOM|, begin by " +"navigating to :menuselection:`Manufacturing app --> Products --> Bills of " +"Materials` and click the desired |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:45 +msgid "" +"From the |BOM| page, click the :guilabel:`ECO` smart button, and switch to " +"list view by selecting the :guilabel:`≣ (four horizontal lines)` icon on the" +" top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:49 +msgid "" +"The :guilabel:`ECO` smart button is visible on the |BOM| **only** if the " +"*PLM* app is installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show ECO smart button on a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:55 +msgid "" +"In the list of |ECOs| for the product, navigate to the search bar at the " +"top, and click the :guilabel:`▼ (down arrow)` icon on the right to access a " +"drop-down menu of :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:58 +msgid "" +"Next, filter by :guilabel:`Done` |ECOs| to view: the revision history of the" +" |BOM|, the :guilabel:`Responsible` user who applied the change, and the " +":guilabel:`Effective Date` of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:62 +msgid "" +"Click each |ECO| to view the past components, operations, and design files " +"associated with the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Display ECO revision history for a BoM for a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:70 +msgid "" +"If the :guilabel:`Effective Date` field is empty, the :guilabel:`Effective` " +"date of the |ECO| is automatically set to :guilabel:`As soon as possible` " +"and no dates are recorded in the revision history of the |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "List of BOM effective dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:79 +msgid "" +"A workaround for checking when the |BOM| went live is by navigating to the " +"chatter, and hovering over the time the |ECO| was moved to the :ref:`closing" +" stage <plm/eco/stage-config>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:83 +msgid "Design files" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:85 +msgid "" +"Attach computer-aided design (CAD) files, PDFs, images, or other design " +"material to the |BOM| itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:88 +msgid "" +"To do so, navigate to :menuselection:`PLM app --> Master Data --> Bill of " +"Materials`, and select the desired |BOM|. On the |BOM|, navigate to the " +"*chatter*, and click the :guilabel:`📎 (paperclip)` icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:92 +msgid "" +"The files associated with the |BOM| are displayed in the :guilabel:`Files` " +"section. To add more design files, select the :guilabel:`Attach files` " +"button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst-1 +msgid "Show paperclip icon in the chatter to attach files to a BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:100 +msgid "Manage design files in an ECO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:102 +msgid "" +"Add, modify, and remove files in an |ECO|. Once the |ECO| is approved and " +"applied, the new files are automatically linked to the production |BOM|. " +"Archived files are removed from the |BOM|, but are still accessible in the " +"|ECO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:106 +msgid "" +"To manage the design files in the |ECO|, begin by navigating to " +":menuselection:`PLM app --> Changes` and choose the desired |ECO|. Next, " +"open the :guilabel:`Attachments` page by clicking the :guilabel:`Documents` " +"smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:110 +msgid "" +"Hover over each attachment to reveal the :guilabel:`︙ (three vertical dots)`" +" icon. From there, choose whether to :guilabel:`Edit`, :guilabel:`Remove`, " +"or :guilabel:`Download` the file. Any changes made to these files are " +"contained within the |ECO|, and will only apply to the production |BOM| once" +" the :ref:`changes are applied <plm/eco/apply-changes>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:116 +msgid "" +"In the `Create 60% keyboard` |ECO|, the design files are from the original " +"`100% keyboard` |BOM|. To replace the keyboard PDF, begin by selecting the " +":guilabel:`Documents` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Show *Documents* smart button from an active ECO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:123 +msgid "" +"On the :guilabel:`Attachments` page, hover over the `100% keyboard " +"manual.pdf` design file, and click the :guilabel:`︙ (three vertical dots)` " +"icon. Then, click the :guilabel:`Remove` option to archive the file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:127 +msgid "" +"Next, on the same :guilabel:`Attachments` page, click the :guilabel:`Upload`" +" button to upload the new design file, named `60% keyboard manual`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "" +"View of *Attachments* page from the *Documents* smart button. Displays one archived and\n" +"one newly added attachment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:136 +msgid "" +"Archived files are **not** permanently deleted — they can still be accessed " +"in the previous |ECO|, or as an archived file in the latest |ECO|, where the" +" archival occurred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:140 +msgid "Apply rebase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:142 +msgid "" +"Odoo simplifies merge conflict resolution for concurrent |ECOs| on the same " +"product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:144 +msgid "" +"Conflicts can occur when the production |BOM| is updated while other |ECOs| " +"are modifying the previous version. Differences between the new and previous" +" production |BOMs| are displayed in the :guilabel:`Previous Eco Bom Changes`" +" tab, visible only in this scenario." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:148 +msgid "" +"To resolve conflicts and retain |ECO| changes, click the :guilabel:`Apply " +"Rebase` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:151 +msgid "" +"Two |ECOs|, `ECO0011` and `ECO0012`, are created when the current |BOM| " +"version is `5`. In `ECO0011`, a new component, `Space stabilizer`, is added," +" and the changes are applied. This means the current |BOM| version has " +"become `6`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "Apply changes to an ECO to update the production BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:159 +msgid "" +"This means `ECO0012` is modifying an outdated |BOM|. As shown in the " +":guilabel:`Previous Eco Bom Changes` tab, the |BOM| is missing the `Space " +"stabilizer`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:162 +msgid "" +"To ensure the changes applied by `ECO0011` are kept when the changes occur " +"in `ECO0012`, click the :guilabel:`Apply Rebase` button to apply the " +"previous |ECO| changes, without affecting the changes already made to " +"`ECO0012`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/manage_changes/version_control.rst:0 +msgid "" +"Click the *Apply Rebase* button to update the BOM to match the production " +"BOM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management.rst:3 +msgid "Project management" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:3 +msgid "Approvals" +msgstr "การอนุมัติ" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:10 +msgid "" +"Notify stakeholders and managers automatically by assigning approvers to " +"stages of :ref:`engineering change orders <plm/eco>` (ECOs) under review. " +"Changes can only be applied after the assigned approver accepts them. " +"Approvals ensure reviews by team members, which prevents mistakes and " +"premature actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:16 +msgid ":ref:`Stage configuration <plm/eco/stage-config>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:19 +msgid "Add approver" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:21 +msgid "" +"To add an approver, first go to the :menuselection:`PLM app`, and click on " +"the project card of an ECO type to open the Gantt view of the |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:24 +msgid "" +"On the :guilabel:`Engineering Change Orders` page, hover over the intended " +"stage, and select the :guilabel:`⚙️ (gear)` icon. Then, click " +":guilabel:`Edit` to open a pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:28 +msgid "" +"Approvers can be added to any stage, but it's strongly recommended to assign" +" them to the *verification* stage, which comes before the *closing* stage, " +"where |ECOs| are applied, and the :abbr:`BoM (Bill of Materials)` version is" +" updated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:32 +msgid "" +"See the documentation about :ref:`stage types <plm/eco/stage-config>` for " +"more information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:36 +msgid "" +"In the :guilabel:`Edit` stage pop-up window, click the :guilabel:`Add a " +"line` button, located under :guilabel:`Approvals`. Then, type in the " +"approver's position (or title) under :guilabel:`Role` (e.g. `Engineering " +"Manager`, `Quality Team`, etc.), and select the relevant :guilabel:`User` " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:41 +msgid "" +"Next, set the :guilabel:`Approval Type` to :guilabel:`Is required to " +"approve`, :guilabel:`Approves, but the approval is optional`, or " +":guilabel:`Comments only`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:45 +msgid "" +"Assign the `CTO`, \"Mitchell Admin,\" as a required approver for |ECOs| in " +"the `Validated` stage in the `New Product Introduction` ECO type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:48 +msgid "" +"Approvals from the quality and marketing teams are **not** required to apply" +" changes to the |ECO| because their :guilabel:`Approval Type` is set to " +":guilabel:`Approves, but the approval is optional` and :guilabel:`Comments " +"only`, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "" +"Set an approver that \"Is required to approve\" ECOs in the \"Validated\" " +"stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:57 +msgid "Manage approvals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:59 +msgid "" +"Approvers can easily track their to-do approvals by navigating to the " +":menuselection:`PLM app`, and looking at the card for an ECO type, which " +"shows the count of open tasks assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:62 +msgid "Here's what each button on an ECO project card does:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:64 +msgid "" +"The :guilabel:`# Engineering Changes` button displays a count of in-progress" +" |ECOs| of this ECO type. Clicking the button opens the Gantt view of the " +":guilabel:`Engineering Change Orders` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:66 +msgid "" +":guilabel:`My Validations` displays a count of |ECOs| the approver must " +"accept or reject. Clicking on this button displays |ECOs| pending approval " +"or rejected (marked with the red :guilabel:`Blocked` state)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:69 +msgid "" +"The :guilabel:`All Validations` button shows the count of |ECOs| awaiting " +"approval or rejected by any approver. Clicking it reveals these pending " +"|ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:71 +msgid "" +":guilabel:`To Apply` displays a count of |ECOs| to which the user needs to " +"apply changes. Clicking on the button displays all the |ECOs| to approve, " +"and apply changes to, in the verification stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:75 +msgid "" +"|ECOs| marked with the green :guilabel:`Done` stage have already been " +"approved, and the user just needs to click on the |ECO| to enter the form " +"view, and click the :guilabel:`Apply Changes` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "" +"Display count of validations to-do and buttons to open filtered list of " +"ECOs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:84 +msgid "Approve ECOs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:86 +msgid "" +"Navigate to an |ECO| in a verification stage, while logged in as the " +"assigned approver, to see the :guilabel:`Approve`, :guilabel:`Reject`, and " +":guilabel:`Apply Changes` buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:89 +msgid "" +"To approve the |ECO|, and apply the changes onto the production :abbr:`BoM " +"(Bill of Materials)`, click :guilabel:`Approve`, and then :guilabel:`Apply " +"Changes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:92 +msgid "" +"Note that the :guilabel:`Apply Changes` button will **not** work unless the " +":guilabel:`Approve` button was clicked first. Additionally, the chatter logs" +" the history of the clicked buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:96 +msgid "" +"When the :guilabel:`Approval Type` is **not** set to :guilabel:`Is required " +"to approve`, approval from the associated user is not needed before applying" +" changes with the :guilabel:`Apply Changes` button. Thus, the " +":guilabel:`Apply Changes` button **will work** without requiring the " +":guilabel:`Approve` button to be clicked first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:102 +msgid "Automated activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:104 +msgid "" +"When an |ECO| is moved to a verification stage, a planned activity is " +"automatically created for assigned approvers to review the |ECO|. Approvers " +"receive a notification in their activities inbox, accessible through the " +":guilabel:`🕘 (clock)` icon at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:108 +msgid "" +"In the to-do task list, the :guilabel:`Engineering Change Order (ECO)` " +"notification displays the number of activities marked :guilabel:`Late`, " +":guilabel:`Today`, and :guilabel:`Future`. Clicking on each of these buttons" +" shows a filtered Gantt view of the respective |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:113 +msgid "" +"Scheduled activities are shown as a number on the :guilabel:`🕘 (clock)` " +"icon, with `5` |ECOs| pending approval :guilabel:`Today`. Currently, there " +"are `0` :guilabel:`Late` or :guilabel:`Future` |ECOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Show scheduled approvals notifications for the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:121 +msgid "" +"By clicking a pending |ECO|, a *planned activity* for :guilabel:`ECO " +"Approval` is recorded in the chatter. Click on the :guilabel:`i (Info)` icon" +" to view additional information, including the approval's " +":guilabel:`Created` date, the approver :guilabel:`Assigned to` it, and the " +"due date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "Show additional details of the planned ECO approval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:130 +msgid "Follow-up activities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:132 +msgid "" +"When |ECOs| are rejected, tasks need to be assigned to project members for " +"required modifications before |ECO| approval. To create tasks with " +"deadlines, navigate to the rejected |ECO| form, and go to the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:136 +msgid "" +"Select the :guilabel:`Mark Done` button in the :guilabel:`Planned " +"Activities` section of the chatter to close the activity, and open a pop-up " +"window for creating tasks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst-1 +msgid "" +"Show *Mark Done* window to show *Done & Schedule Next*, *Done*, and *Discard* buttons to\n" +"close the planned activity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:144 +msgid "" +"In the :guilabel:`Mark Done` window, click :guilabel:`Done & Schedule Next` " +"to open a new :guilabel:`Schedule an Activity` window. Next, set the " +":guilabel:`Assigned to` team member and the :guilabel:`Due Date` for " +"completing the changes. Provide task details in the :guilabel:`Summary` " +"field and the text box. Click the :guilabel:`Schedule` button to close the " +"window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:149 +msgid "" +"After closing the window, on the |ECO| form, move the |ECO| back one stage. " +"Doing so ensures that when the team member completes the changes, and " +"returns the |ECO| to the verification stage, a new :guilabel:`ECO Approval` " +"task is created for the approver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:154 +msgid "" +"The approver creates an activity for the :guilabel:`Responsible` of the " +"|ECO|, `Laurie Poiret`, that details the changes required for the approver " +"to :guilabel:`Accept` the |ECO|. Clicking the :guilabel:`Schedule` button " +"creates a planned activity for Laurie due on `08/15/2023`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/plm/management/approvals.rst:0 +msgid "Create a scheduled activity for follow-up changes to a rejected ECO." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:8 +msgid "Purchase" +msgstr "สั่งซื้อ" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:10 +msgid "" +"**Odoo Purchase** helps keep track of purchase agreements, quotations, and " +"purchase orders. Learn how to monitor purchase tender, automate " +"replenishment, and follow up on your orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase.rst:14 +msgid "`Odoo Tutorials: Purchase <https://www.odoo.com/slides/purchase-23>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced.rst:5 +msgid "Advanced" +msgstr "ระดับสูง" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:3 +msgid "Analyze the performance of your purchases" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:5 +msgid "" +"If your company regularly purchases products, you have several reasons to " +"track and analyze your performance. The insights gathered can help you to " +"better forecast and plan your future orders. For example, you can assess if " +"your business is dependent on particular vendors, and the data can help you " +"negotiate discounts on prices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:11 +msgid "Generate customized reports" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:13 +msgid "" +"Go to *Reporting* to access the purchase analysis. Simply by accessing the " +"reporting dashboard, you can get a quick overview of your actual " +"performance. By default, the reporting dashboard displays a line chart " +"presenting the untaxed amount of your purchase orders per day, and below it," +" key metrics and a pivot table." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting dashboard in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:22 +msgid "" +"While the data initially presented is useful, there are several tools and " +"features you can use to get even more insights on your purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:26 +msgid "Use filters to select the data you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:28 +msgid "" +"Odoo offers several default filters you can use and combine by clicking on " +"*Filters*. When you select one or several filters, Odoo looks for all the " +"orders that match at least one of the filters you have chosen and populates " +"the chart, key metrics, and pivot table with the data. The pre-configured " +"filters are:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:33 +msgid "All *Requests for Quotation*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:35 +msgid "All *Purchase Orders*, except canceled ones" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:37 +msgid "" +"*Confirmation Date Last Year* includes all orders that were confirmed the " +"previous year, canceled purchase orders included" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:40 +msgid "" +"*Order Date* includes all orders - request for quotations and purchases " +"orders (canceled ones included) - depending on their date of creation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:43 +msgid "" +"*Confirmation Date* includes all confirmed orders, canceled ones included, " +"depending on their date of confirmation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:47 +msgid "" +"When you have to select a period, you can use multiple years, and, with at " +"least one year selected, multiple quarters and the three most recent months." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:51 +msgid "" +"If you use the *Order Date* or *Confirmation Date* filters, the *Comparison*" +" feature appears next to *Filters*. It enables you to compare the period you" +" filtered with the previous one." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting filters in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:59 +msgid "Add custom filters" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:61 +msgid "" +"Thanks to the 31 filtering options to choose from, the possibilities of your" +" customizing your dataset are almost limitless. Go to " +":menuselection:`Filters --> Add Custom Filter`, specify the condition the " +"filtering option should meet (e.g. *is equal to*, *contains*, etc.), and " +"click on *Apply*. If you want to select orders matching several conditions " +"simultaneously (*and* operator), repeat the process to add another custom " +"filter. If you want to use the *or* operator, don't click on *Apply*, and " +"click on *Add a condition* instead. Once you have added all the desired " +"filtering options, click on *Apply*." +msgstr "" +"ด้วยตัวเลือกการกรองที่มีตัวกรองถึง 31 แบบให้เลือก " +"ความเป็นไปได้ในการปรับแต่งชุดข้อมูลของคุณจึงแทบจะไร้ขีดจำกัด ไปที่ " +":menuselection:`ตัวกรอง --> เพิ่มตัวกรองแบบกำหนดเอง` " +"ระบุเงื่อนไขที่ตัวเลือกการกรองควรเป็นไปตาม (เช่น *เท่ากับ*, *มี* และอื่นๆ) " +"และคลิกที่ *นำไปใช้* " +"หากคุณต้องการเลือกคำสั่งซื้อที่ตรงกับเงื่อนไขหลายข้อพร้อมกัน (*และ* " +"โอเปอเรเตอร์) ให้ทำซ้ำขั้นตอนนี้เพื่อเพิ่มตัวกรองที่กำหนดเองอื่น " +"หากคุณต้องการใช้โอเปอเรเตอร์ *หรือ* อย่าคลิก *นำไปใช้* และคลิก " +"*เพิ่มเงื่อนไข* แทน เมื่อคุณเพิ่มตัวเลือกการกรองที่ต้องการทั้งหมดแล้ว " +"ให้คลิก *นำไปใช้*" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Custom reporting filter in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:74 +msgid "" +"To avoid having to recreate custom filters every time, save them by clicking" +" on :menuselection:`Favorites --> Save current search --> Save`. The " +"customized search filter can then be accessed by clicking on *Favorites* or " +"can even be set as the default filter when you open the reporting dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:80 +msgid "Measure exactly what you need" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:82 +msgid "" +"Before selecting what you want to measure, you need to decide whether you " +"prefer using the graph view or the pivot view. By default, the dashboard " +"presents both views. However, the measures you select won't be applied to " +"both views. You can access each view separately by clicking on the icons at " +"the top right of the dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Switch reporting view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:92 +msgid "Visualize your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:94 +msgid "" +"You can transform the main graph in just a click by selecting one of the " +"three charts: bar, line or pie. Fourteen different measures are available, " +"but you can only use one at a time. However, you can group the measure using" +" one or several of the 19 *Groups*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Reporting graph view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:102 +msgid "" +"For bar and line charts, the selected measure is your y-axis, and the first " +"group you select is used to create the x-axis. Adding more group adds " +"additional lines (line chart) or transforms your bar chart into a stacked " +"bar chart. For pie charts, the more groups you select, the more slices are " +"displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:108 +msgid "Explore your data" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:110 +msgid "" +"The pivot table view enables you to explore your data in great detail. " +"Unlike the graph view, the pivot table enables you to add several measures " +"at the same time. By clicking on *Measures* or on the **+** sign in the " +"*Total* column, you can add as many as you want, each assigned to a new " +"column. By clicking on the **+** sign in the *Total* row, you can add " +"*Groups*. If you click on a group's **+** sign, you can add a sub-group, and" +" so on." +msgstr "" +"มุมมองตารางสรุปทำให้คุณสามารถสำรวจข้อมูลของคุณได้อย่างละเอียด " +"ตารางสรุปทำให้คุณสามารถเพิ่มการวัดหลายอย่างพร้อมกันได้ ซึ่งต่างจากมุมมองกราฟ" +" เมื่อคลิกที่ *การวัด* หรือเครื่องหมาย **+** ในคอลัมน์ *รวม* " +"คุณสามารถเพิ่มได้มากเท่าที่คุณต้องการ " +"โดยแต่ละรายการจะถูกกำหนดให้กับคอลัมน์ใหม่ เมื่อคลิกที่เครื่องหมาย **+** " +"ในแถว *รวม* คุณจะสามารถเพิ่ม *กลุ่ม* ได้ หากคุณคลิกที่เครื่องหมาย **+** " +"ของกลุ่ม คุณจะสามารถเพิ่มกลุ่มย่อยได้ และอื่นๆ" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst-1 +msgid "Pivot table view in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/advanced/analyze.rst:121 +msgid "" +"You can insert your pivot table's data directly in the Spreadsheet app or " +"export it as an Excel file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals.rst:5 +msgid "Manage deals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:3 +msgid "Use blanket orders to create purchase agreements with vendors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:5 +msgid "" +"Blanket orders are long-term purchase agreements between a company and a " +"vendor to deliver products on a recurring basis with predetermined pricing. " +"Using blanket orders are useful when products are always purchased from the " +"same vendor, but in different quantities at different times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:9 +msgid "" +"By simplifying the ordering process, blanket orders not only save time, they" +" also save money, since they can be advantageous when negotiating bulk " +"pricing with vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:13 +msgid ":doc:`calls_for_tenders`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:16 +msgid "Create a new blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:18 +msgid "" +"To create blanket orders, the *Purchase Agreements* feature first needs to " +"be enabled in the settings of the *Purchase* app. To do this, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and under the " +":guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase " +"Agreements`. Doing so will enable the ability to create blanket orders, as " +"well as alternative requests for quotation (RFQs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Purchase Agreements enabled in the Purshase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:28 +msgid "" +"To create a blanket order, go to :menuselection:`Purchase --> Orders --> " +"blanket orders`, and click :guilabel:`New`. This creates (and navigates to) " +"a new blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:31 +msgid "" +"From this new blanket order form, different fields and settings can be " +"configured, so there are pre-determined rules that the recurring long-term " +"agreement must follow:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:34 +msgid "" +":guilabel:`Purchase Representative`: is the user assigned to this specific " +"blanket order. By default, this is the user who created the agreement; the " +"user can be changed directly from the drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:37 +msgid "" +":guilabel:`Agreement Type`: is the type of purchase agreement this blanket " +"order is classified as. In Odoo, blanket orders are the only official " +"purchase agreement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:39 +msgid "" +":guilabel:`Vendor`: is the supplier to whom this agreement is tied, either " +"once or on a recurring basis. The vendor can be selected directly from the " +"drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:41 +msgid "" +":guilabel:`Currency`: is the agreed-upon currency that will be used for this" +" exchange. If multiple currencies have been activated in the database, the " +"currency can be changed from the drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:44 +msgid "" +":guilabel:`Agreement Deadline`: is the date that this purchase agreement " +"will be set to expire on (if desired). If this blanket order should not " +"expire, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:46 +msgid "" +":guilabel:`Ordering Date`: is the date that this blanket order should be " +"placed on if a new quotation is created directly from the blanket order " +"form. If a new quotation is created, this value will automatically populate " +"the *Order Deadline* field on the :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:50 +msgid "" +":guilabel:`Delivery Date`: is the expected delivery date that the products " +"included in an :abbr:`RFQ (Request for Quotation)` created directly from the" +" blanket order form will be expected to arrive. If a new quotation is " +"created, this value will automatically populate the *Expected Arrival* field" +" on the :abbr:`RFQ (Request for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:54 +msgid "" +":guilabel:`Source Document`: is the source purchase order (PO) that this " +"blanket order will be tied to. If this blanket order should not be tied to " +"any existing :abbr:`POs (Purchase Orders)`, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:57 +msgid "" +":guilabel:`Company`: is the company assigned to this specific blanket order." +" By default, this is the company that the user creating the blanket order is" +" listed under. If the database is not a multi-company database, this field " +"can not be changed, and will default to the only company listed in the " +"database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New blanket order purchase agreement with added products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:66 +msgid "" +"Once all relevant fields have been filled out, click :guilabel:`Add a line` " +"to add products under the :guilabel:`Product` column. Then, change the " +"quantity of each product in the :guilabel:`Quantity` column (if desired), " +"and set a price in the :guilabel:`Unit Price` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:71 +msgid "" +"When adding products to a new blanket order, the pre-existing prices of " +"products will not be added automatically to the product lines. The prices " +"must be manually assigned by changing the value in the :guilabel:`Unit " +"Price` column to an agreed-upon price with the listed vendor. Otherwise, the" +" price will remain **0**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:76 +msgid "" +"To view and change the default purchase agreement settings for blanket " +"orders directly from the blanket order form, click the :guilabel:`internal " +"link (arrow icon)` next to the :guilabel:`Agreement Type` field where " +":guilabel:`Blanket Order` is listed. This navigates to the blanket order " +"settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:81 +msgid "" +"From here, the settings for blanket orders can be edited. Under the " +":guilabel:`Agreement Type` section, the name of the :guilabel:`Agreement " +"Type` can be changed (if desired), and the :guilabel:`Agreement Selection " +"Type` can be changed, as well. There are two options that can be activated " +"for the type of selection:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:86 +msgid "" +":guilabel:`Select only one RFQ (exclusive)`: when a purchase order is " +"confirmed, the remaining purchase orders will be canceled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:88 +msgid "" +":guilabel:`Select multiple RFQ (non-exclusive)`: when a purchase order is " +"confirmed, remaining purchase orders will ***not** be canceled. Instead, " +"multiple purchase orders are allowed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:91 +msgid "" +"Under the :guilabel:`Data For New Quotations` section, the settings for how " +"product lines and quantities will be populated on new quotations using this " +"purchase agreeement can be changed next to the :guilabel:`Lines` and " +":guilabel:`Quantities` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Purchase Agreement type edit screen for blanket orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:99 +msgid "There are two options that can be activated for :guilabel:`Lines`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:101 +msgid "" +":guilabel:`Use lines of agreement`: when creating a new quotation, the " +"product lines will pre-populate with the same products listed on the blanket" +" order, if said blanket order is chosen on the new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:104 +msgid "" +":guilabel:`Do not create RfQ lines automatically`: when creating a new " +"quotation and selecting an existing blanket order, the settings will carry " +"over to the new quotation, but the product lines will not populate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:108 +msgid "" +"And, there are two options that can be activated for :guilabel:`Quantities`:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:110 +msgid "" +":guilabel:`Use quantities of agreement`: when creating a new quotation, the " +"product quantities listed on the blanket order will pre-populate on the " +"product lines, if said blanket order is chosen on the new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:113 +msgid "" +":guilabel:`Set quantities manually`: when creating a new quotation and " +"selecting an existing blanket order, the product lines will pre-populate, " +"but all quantities will be set to **0**. The quantities will need to be " +"manually set by the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:117 +msgid "" +"Once the desired changes have been made (if any), click :guilabel:`New` (via" +" the breadcrumbs, at the top of the page) to navigate back to the blanket " +"order form, and click :guilabel:`Confirm` to save this new purchase " +"agreement. Once confirmed, the blanket order changes from *Draft* to " +"*Ongoing*, meaning this agreement can be selected and used when creating new" +" :abbr:`RFQs (Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:124 +msgid "" +"After creating and confirming a blanket order, products, quantities, and " +"prices can still be edited, added, and removed from the purchase agreement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:128 +msgid "" +"Create a new :abbr:`RFQ (Request for Quotation)` from the blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:130 +msgid "" +"After confirming a blanket order, new quotations can be created directly " +"from the blanket order form that will use the rules set on the form and pre-" +"populate the new quotation with the correct information. Additionally, this " +"new quotation will be automatically linked to this blanket order form via " +"the :guilabel:`RFQs/Orders` smart button at the top right of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:135 +msgid "" +"To create a new quotation from the blanket order form, click :guilabel:`New " +"Quotation`. This creates (and navigates to) a new :abbr:`RFQ (Request for " +"Quotation)`, that is pre-populated with the correct information, depending " +"on the settings configured on the blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:139 +msgid "" +"From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send" +" by Email` to compose and send an email to the listed vendor; click " +":guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once" +" ready, click :guilabel:`Confirm Order` to confirm the purchase order (PO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New quotation with copied products and rules from blanket order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:147 +msgid "" +"Once the :abbr:`PO (Purchase Order)` has been confirmed, click back to the " +"blanket order form (via the breadcrumbs, at the top of the page). From the " +"blanket order form, there is now one :abbr:`RFQ (Request for Quotation)` " +"listed in the :guilabel:`RFQs/Orders` smart button at the top right of the " +"form. Click the :guilabel:`RFQs/Orders` smart button to see the purchase " +"order that was just created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "RFQs and Orders smart button from blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:157 +msgid "Create a new blanket order from an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:159 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:49 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:148 +msgid "" +"To create a new :abbr:`RFQ (Request for Quotation)`, navigate to the " +":menuselection:`Purchase` app, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:162 +msgid "" +"Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a" +" vendor from the drop-down menu next to the :guilabel:`Vendor` field, and " +"click :guilabel:`Add a product` to select a product from the drop-down menu " +"in the :guilabel:`Product` column. Then, set the desired purchase quantity " +"in the :guilabel:`Quantity` column, and change the purchase price in the " +":guilabel:`Unit Price` column, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:168 +msgid "" +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item. Repeat these steps to" +" add as many additional options as desired, including the :guilabel:`UoM` " +"(Units of Measure) to purchase the products in, and the :guilabel:`Expected " +"Arrival` date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:173 +msgid "" +"Before confirming the new quotation and creating a purchase order, click the" +" drop-down menu next to the :guilabel:`Blanket Order` field, and type a new " +"name for the new blanket order. This creates a brand new purchase agreement," +" and saves the information entered in the fields of the purchase order form," +" as well as the product information entered on the product lines." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:178 +msgid "" +"From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send" +" by Email` to compose and send an email to the listed vendor; click " +":guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once" +" ready, click :guilabel:`Confirm Order` to confirm the :abbr:`PO (purchase " +"order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "New blanket order created directly from quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:188 +msgid "" +"To see the newly-created blanket order purchase agreement, go to " +":menuselection:`Orders --> Blanket Orders`, and click into the new blanket " +"order. From here, settings and rules can be changed, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:193 +msgid "Blanket orders and replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:195 +msgid "" +"Once a blanket order is confirmed, a new vendor line is added under the " +":guilabel:`Purchase` tab of of the products included in the :abbr:`BO " +"(Blanket Order)`. This makes blanket orders useful with :doc:`automated " +"replenishment <../../purchase/products/reordering>`, because information " +"about the :guilabel:`Vendor`, :guilabel:`Price`, and the " +":guilabel:`Agreement` are referenced on the vendor line. This information is" +" used to determine where, when, and for what price this product could be " +"replenished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst-1 +msgid "Product form with replenishment agreement linked to blanket order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:3 +msgid "Create alternative requests for quotation for multiple vendors" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:5 +msgid "" +"Sometimes, companies might want to request offers from multiple vendors at " +"the same time, by inviting those vendors to submit offers for similar goods " +"or services all at once. This helps companies to select the cheapest (and " +"fastest) vendors, depending on their specific business needs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:9 +msgid "" +"In Odoo, this can be done by adding alternative requests for quotation " +"(RFQs) for different vendors. Once a response is received from each vendor, " +"the product lines from each :abbr:`RFQ (Request for Quotation)` can be " +"compared, and a decision can be made for which products to purchase from " +"which vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:14 +msgid "" +"Sometimes referred to as a *call for tender*, this process is primarily used" +" by organizations in the public sector, who are legally bound to use it when" +" making a purchase. However, private companies can also use alternative " +":abbr:`RFQs (Requests for Quotation)` to spend money efficiently, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:20 +msgid ":doc:`blanket_orders`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:23 +msgid "Configure purchase agreement settings" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:25 +msgid "" +"To create alternative :abbr:`RFQs (Requests for Quotation)` directly from a " +"quotation, the *Purchase Agreements* feature first needs to be enabled in " +"the settings of the *Purchase* app. To do this, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and under the " +":guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase " +"Agreements`. Doing so will enable the ability to create alternative " +":abbr:`RFQs (Requests for Quotation)`, as well as the ability to create " +"*blanket orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Purchase Agreements enabled in the Purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:37 +msgid "" +"To save time on a *call for tender*, custom vendors, prices, and delivery " +"lead times can be set in the :guilabel:`Purchase` tab on a product form. To " +"do so, navigate to :menuselection:`Purchase --> Products --> Products`, and " +"select a product to edit. From the product form, click the " +":guilabel:`Purchase tab`, then click :guilabel:`Add a line`. From the drop-" +"down menu, choose a vendor to set under the :guilabel:`Vendor` column, and " +"set a :guilabel:`Price` and :guilabel:`Delivery Lead Time` if desired. " +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item." +msgstr "" +"เพื่อประหยัดเวลาในการ *เรียกประกวดราคา* คุณสามารถตั้งค่าผู้ขายที่กำหนดเอง " +"ราคา และเวลารอสินค้าในการจัดส่งได้ใน :guilabel:`แท็บซื้อ` " +"บนแบบฟอร์มผลิตภัณฑ์ โดยไปที่ :menuselection:`การจัดซื้อ --> ผลิตภัณฑ์ --> " +"ผลิตภัณฑ์` และเลือกผลิตภัณฑ์ที่จะแก้ไข จากแบบฟอร์มผลิตภัณฑ์ คลิก " +":guilabel:`แท็บซื้อ` จากนั้นคลิก :guilabel:`เพิ่มบรรทัด` จากเมนูแบบเลื่อนลง " +"ให้เลือกผู้ขายที่จะตั้งค่าภายใต้คอลัมน์ :guilabel:`ผู้จำหน่าย` และตั้งค่า " +":guilabel:`ราคา` และ :guilabel:`ระยะเวลาในการจัดส่ง` หากต้องการ การคลิกไอคอน" +" :guilabel:`ตัวเลือกเพิ่มเติม (สองจุด)` " +"จะทำให้มีตัวเลือกการมองเห็นเพิ่มเติมเพื่อเพิ่มลงในรายการโฆษณา" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:47 +msgid "Create an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:52 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:151 +msgid "" +"Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a" +" vendor from the drop-down next to the :guilabel:`Vendor` field, and click " +":guilabel:`Add a product` to select a product from the drop-down menu in the" +" :guilabel:`Product` column. Then, set the desired purchase quantity in the " +":guilabel:`Quantity` column, and change the purchase price in the " +":guilabel:`Unit Price` column, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:58 +msgid "" +"Clicking the :guilabel:`additional options (two-dots)` icon provides " +"additional visibility options to add to the line item. Repeat these steps to" +" add as many options as desired, including the :guilabel:`UoM` (Units of " +"Measure) to purchase the products in, and the :guilabel:`Expected Arrival` " +"date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:63 +msgid "" +"Once ready, click :guilabel:`Send by Email`. This causes a " +":guilabel:`Compose Email` pop-up window to appear, wherein the message to " +"the vendor can be customized. Once ready, click :guilabel:`Send`. This turns" +" the :abbr:`RFQ (Request for Quotation)` into a purchase order (PO), and " +"sends an email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Compose and send quotation email pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:73 +msgid "" +"Sending emails to each vendor can be useful when creating alternative " +":abbr:`RFQs (Requests for Quotation)`, because vendors can confirm if their " +"past prices still hold today, which can help companies choose the best " +"offers for them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:78 +msgid "Create alternatives to an :abbr:`RFQ (Request for Quotation)`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:80 +msgid "" +"Once a :abbr:`PO (Purchase Order)` is created and sent by email to a vendor," +" alternative :abbr:`RFQs (Requests for Quotation)` can be created and sent " +"to additional, alternate vendors to compare prices, delivery times, and " +"other factors to make a decision from which vendors to order which products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:85 +msgid "" +"To create alternative :abbr:`RFQs (Requests for Quotation)`, click the " +":guilabel:`Alternatives` tab from the purchase order form, then click " +":guilabel:`Create Alternative`. When clicked, a :guilabel:`Create " +"alternative` pop-up window appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Calls for tenders pop-up to create alternative quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:93 +msgid "" +"From this window, select a new/different vendor from the drop-down menu next" +" to the :guilabel:`Vendor` field to assign this alternative quotation to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:96 +msgid "" +"Next to this, there is a :guilabel:`Copy Products` checkbox that is selected" +" by default. When selected, the product quantities of the original :abbr:`PO" +" (Purchase Order)` are copied to the alternative. For this first alternative" +" quotation, leave the checkbox checked. Once finished, click " +":guilabel:`Create Alternative`. This creates (and navigates to) a new " +":abbr:`PO (Purchase Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:101 +msgid "" +"Since the :guilabel:`Create Alternative` checkbox was left checked, this new" +" purchase order form is already populated with the same products, " +"quantities, and other details as the previous, original :abbr:`PO (Purchase " +"Order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:106 +msgid "" +"When the :guilabel:`Copy Products` checkbox is selected while creating an " +"alternative quotation, additional products do not need to be added on the " +"purchase order form unless desired. However, if a chosen vendor is listed in" +" the :guilabel:`Vendor` column under the :guilabel:`Purchase` tab on a " +"product form included in the purchase order, the values set on the product " +"form carry over to the :abbr:`PO (Purchase Order)`, and have to be changed " +"manually, if desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:112 +msgid "" +"Once ready, create a second alternative quotation by clicking the " +":guilabel:`Alternatives` tab, and once again, click :guilabel:`Create " +"Alternative`. This causes the :guilabel:`Create alternative` pop-up window " +"to appear again. This time, choose a different vendor from the drop-down " +"menu next to :guilabel:`Vendor`, and this time, *uncheck* the " +":guilabel:`Copy Products` checkbox. Then, click :guilabel:`Create " +"Alternative`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:119 +msgid "" +"If an alternative quotation needs to be removed from the " +":guilabel:`Alternatives` tab, they can be individually removed by clicking " +"on the :guilabel:`Remove (X)` icon at the end of their row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:122 +msgid "" +"This creates a third, new purchase order. But, since the product quantities " +"of the original :abbr:`PO (Purchase Order)` were *not* copied over, the " +"product lines are empty, and new products need to be added by clicking " +":guilabel:`Add a product`, and selecting the desired products from the drop-" +"down menu. Once the desired number of products are added, click " +":guilabel:`Send by Email`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Blank alternative quotation with alternatives in breadcrumbs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:131 +msgid "" +"This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the" +" message to the vendor can be customized. Once ready, click :guilabel:`Send`" +" to send an email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:135 +msgid "" +"From this newest purchase order form, click the :guilabel:`Alternatives` " +"tab. Under this tab, all three purchase orders can be seen in the " +":guilabel:`Reference` column. Additionally, the vendors are listed under the" +" :guilabel:`Vendor` column, and the order :guilabel:`Total` and " +":guilabel:`Status` of the orders are in the rows, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:141 +msgid "Link a new :abbr:`RFQ (Request for Quotation)` to existing quotations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:143 +msgid "" +"Creating alternative quotations directly from a purchase order form under " +"the :guilabel:`Alternatives` tab is the easiest way to create and link " +"quotations. However, separate :abbr:`RFQs (Requests for Quotation)` can also" +" be linked *after* the fact, even if they are created completely separately " +"at first." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:157 +msgid "" +"Once ready, click :guilabel:`Send by Email`. This causes a " +":guilabel:`Compose Email` pop-up window to appear, wherein the message to " +"the vendor can be customized. Once ready, click :guilabel:`Send` to send an " +"email to the vendor listed on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:161 +msgid "" +"Then, click the :guilabel:`Alternatives` tab once more. Since this new " +":abbr:`PO (Purchase Order)` was created separately, there are no other " +"orders linked yet. To link this order with the alternatives created " +"previously, click :guilabel:`Link to Existing RfQ` on the first line in the " +":guilabel:`Vendor` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "pop-up to link new quotation to existing RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:170 +msgid "" +"This causes an :guilabel:`Add: Alternative POs` pop-up window to appear. " +"Select the three purchase orders created previously, and click " +":guilabel:`Select`. All of these orders are now copied to this :abbr:`PO " +"(Purchase Order)` under the :guilabel:`Alternatives` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:175 +msgid "" +"If a large number of purchase orders are being processed and the previous " +":abbr:`POs (Purchase Orders)` can't be located, try clicking " +":menuselection:`Group By --> Vendor` under the search bar at the top of the " +"pop-up window to group by the vendors selected on the previous orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:181 +msgid "Compare product lines" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:183 +msgid "" +"When there are multiple :abbr:`RFQs (Requests for Quotation)` linked as " +"alternatives, they can be compared side-by-side in order to determine which " +"vendors offer the best deals on which products. To compare each quotation, " +"go to the :menuselection:`Purchase` app, and select one of the quotations " +"created previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:188 +msgid "" +"Then, click the :guilabel:`Alternatives` tab to see all the linked " +":abbr:`RFQs (Requests for Quotation)`. Next, under the :guilabel:`Create " +"Alternative` tab, click :guilabel:`Compare Product Lines`. This navigates to" +" a Compare Order Lines page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Compare Product Lines page for alternative RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:196 +msgid "" +"The Compare Order Lines page, by default, groups by :guilabel:`Product`. " +"Each product included in any of the :abbr:`RFQs (Requests for Quotation)` is" +" displayed in its own drop-down, along with all of the :abbr:`PO (Purchase " +"Order)` numbers in the :guilabel:`Reference` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:200 +msgid "" +"Additional columns on this page include the :guilabel:`Vendor` from which " +"products were ordered, the :guilabel:`Status` of the quotation (i.e., RFQ, " +"RFQ Sent); the :guilabel:`Quantity` of products ordered from each vendor; " +"the :guilabel:`Unit Price` per product and :guilabel:`Total` price of the " +"order, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:206 +msgid "" +"To remove product lines from the Compare Order Lines page, click " +":guilabel:`Clear` at the far right end of that product line's row. This " +"removes this product as a chooseable option from the page, and changes the " +":guilabel:`Total` price of that product on the page to **0**. On the " +"purchase order form in which that product was included, its ordered quantity" +" is changed to **0**, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:212 +msgid "" +"Once the best offers have been identified, at the end of each row, " +"individual products can be selected by clicking :guilabel:`Choose`. Once all" +" the desired products have been chosen, click :guilabel:`Requests for " +"Quotation` (in the breadcrumbs, at the top of the page) to navigate back to " +"an overview of all :abbr:`RFQs (Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:218 +msgid "Cancel (or keep) alternatives" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:220 +msgid "" +"Now that the desired products have been chosen, based on which vendors " +"provided the best offer, the other :abbr:`RFQs (Requests for Quotation)` " +"(from which no products were chosen) can be canceled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:223 +msgid "" +"Under the :guilabel:`Total` column, at the far right of each row, the orders" +" from which no products were chosen have automatically had their total cost " +"set to **0**. Although they haven't been canceled yet, this means that they " +"can ultimately be canceled without repercussions, *after* the desired " +"purchase orders have been confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Canceled quotations in the Purchase app overview." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:232 +msgid "" +"To confirm a quotation that contains the chosen product quantities, click " +"into one. Then, click :guilabel:`Confirm Order`. This causes an " +":guilabel:`Alternative Warning` pop-up window to appear. From there, either " +":guilabel:`Cancel Alternatives` or :guilabel:`Keep Alternatives` can be " +"clicked. If this :abbr:`PO (Purchase Order)` should *not* be confirmed, " +"click :guilabel:`Cancel`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:237 +msgid "" +":guilabel:`Cancel Alternatives` automatically cancels the alternative " +"purchase orders. :guilabel:`Keep Alternatives` keeps the alternative " +"purchase orders open, so they can still be accessed if any additional " +"product quantities need to be ordered. Once all products are ordered, " +":guilabel:`Cancel Alternatives` can be selected from whichever :abbr:`PO " +"(Purchase Order)` is open." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:242 +msgid "" +"To view a detailed form of one of the :abbr:`RFQs (Requests for Quotation)` " +"listed, click the line item for that quotation. This causes an " +":guilabel:`Open: Alternative POs` pop-up window to appear, from which all " +"details of that particular quotation can be viewed. Click :guilabel:`Close` " +"when finished." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst-1 +msgid "Keep or cancel pop-up for alternative RFQs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:251 +msgid "" +"From the :guilabel:`Alternative Warning` pop-up window, click " +":guilabel:`Keep Alternatives` to keep all alternative quotations open for " +"now. Then, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at " +"the top of the page) to navigate back to an overview of all :abbr:`RFQs " +"(Requests for Quotation)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:256 +msgid "" +"Click into the remaining quotation(s) that contain products that need to be " +"ordered, and click :guilabel:`Confirm Order`. This causes the " +":guilabel:`Alternative Warning` pop-up window to appear again. This time, " +"click :guilabel:`Cancel Alternatives` to cancel all other alternative " +":abbr:`RFQs` linked with this quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:261 +msgid "" +"Finally, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at " +"the top of the page) to navigate back to an overview of all :abbr:`RFQs " +"(Requests for Quotation)`. The canceled orders can be seen greyed out and " +"listed with a :guilabel:`Cancelled` status under the :guilabel:`Status` " +"column at the far right of their rows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:266 +msgid "" +"Now that all product quantities have been ordered, the purchase process can " +"be followed, and continued to completion, until the products are received " +"into the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:15 +msgid "Bill control policies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:5 +msgid "" +"In Odoo, the *bill control* policy determines the quantities billed by " +"vendors on every purchase order, for ordered or received quantities. The " +"policy selected in the settings will act as the default value and will be " +"applied to any new product created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:12 +msgid "" +"To view the default bill control policy and make changes, go to " +":menuselection:`Purchase --> Configuration --> Settings`, and scroll down to" +" the :guilabel:`Invoicing` section. Here, there are the two :guilabel:`Bill " +"Control` policy options: :guilabel:`Ordered quantities` and " +":guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "" +"The policy selected will be the default for any new product created. The " +"definition of each policy is as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:20 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +msgid "" +":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase " +"order is confirmed. The products and quantities in the purchase order are " +"used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:22 +msgid "" +":guilabel:`Received quantities`: a bill is created only *after* part of the " +"total order has been received. The products and quantities *received* are " +"used to generate a draft bill. An error message will appear if creation of a" +" vendor bill is attempted without receiving anything." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Bill control policy draft bill error message." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:31 +msgid "" +"If one or two products need a different control policy, the default bill " +"control setting can be overridden by going to the :guilabel:`Purchase` tab " +"in a product's template and modifying its :guilabel:`Control Policy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36 +msgid "Example flow: Ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:38 +msgid "" +"To complete an example workflow using the *ordered quantities* bill control " +"policy, first go to :menuselection:`Purchase --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Invoicing` section, and select " +":guilabel:`Ordered quantities`. Then, :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:42 +msgid "" +"In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for " +"Quotation)`. Fill out the information on the quotation form, add products to" +" the invoice lines, and click :guilabel:`Confirm Order`. Then, click " +":guilabel:`Create Bill`. Since the policy is set to *ordered quantities*, " +"the draft bill can be confirmed as soon as it is created, without any " +"products actually being received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:48 +msgid "Example flow: Received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:50 +msgid "" +"To complete an example workflow using the *received quantities* bill control" +" policy, first go to :menuselection:`Purchase --> Configuration --> " +"Settings`, scroll down to the :guilabel:`Invoicing` section, and select " +":guilabel:`Received quantities`. Then, :guilabel:`Save` changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:54 +msgid "" +"In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for " +"Quotation)`. Fill out the information on the quotation form, add products to" +" the invoice lines, and click :guilabel:`Confirm Order`. Then, click on the " +":guilabel:`Receipt smart button`. Set the quantities in the :guilabel:`Done`" +" column to match the quantities in the :guilabel:`Demand` column, and " +":guilabel:`Validate` the changes. Then, in the purchase order, click " +":guilabel:`Create Bill` and :guilabel:`Confirm`. Since the policy is set to " +"*received quantities*, the draft bill can be confirmed *only* when at least " +"some of the quantities are received." +msgstr "" +"ในแอป :guilabel:`การจัดซื้อ` ให้สร้าง :abbr:`RFQ (Request for Quotation)` " +"ใหม่ กรอกข้อมูลในแบบฟอร์มใบเสนอราคา เพิ่มผลิตภัณฑ์ลงในบรรทัดใบแจ้งหนี้ " +"และคลิก :guilabel:`ยืนยันคำสั่งซื้อ` จากนั้นคลิกที่ปุ่ม " +":guilabel:`ปุ่มรับใบเสร็จอัจฉริยะ` ตั้งค่าปริมาณในคอลัมน์ " +":guilabel:`เสร็จสิ้น` เพื่อให้ตรงกับปริมาณในคอลัมน์ :guilabel:`ความต้องการ` " +"และ :guilabel:`ตรวจสอบ` การเปลี่ยนแปลง จากนั้น ในใบสั่งซื้อ คลิก " +":guilabel:`สร้างบิล` และ :guilabel:`ยืนยัน` เนื่องจากนโยบายถูกตั้งค่าเป็น " +"*ปริมาณที่ได้รับ* จึงสามารถยืนยันร่างบิลได้ *เฉพาะ* " +"เมื่อได้รับปริมาณบางส่วนเป็นอย่างน้อย" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:63 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 +msgid "3-way matching" +msgstr "การจับคู่ 3 ทาง" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:65 +msgid "" +"Activating :guilabel:`3-way matching` ensures that vendor bills are only " +"paid once some or all of the products included in the purchase order have " +"actually been received. To activate it, go to :menuselection:`Purchase --> " +"Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` " +"section. Then, click :guilabel:`3-way matching: purchases, receptions, and " +"bills`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:72 +msgid "" +"3-way matching is *only* intended to work when the bill control policy is " +"set to *received quantities*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:76 +msgid "Pay vendor bills with 3-way matching" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:78 +msgid "" +"When :guilabel:`3-way matching` is activated, vendor bills will display the " +":guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When " +"a new vendor bill is created, the field will be set to :guilabel:`Yes`, " +"since a bill can't be created until at least some of the products included " +"in a purchase order have been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Draft bill should be paid field status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:88 +msgid "" +"If the total quantity of products from a purchase order has not been " +"received, Odoo only includes the products that *have* been received in the " +"draft vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:91 +msgid "" +"Draft bills can be edited to increase the billed quantity, change the price " +"of the products in the bill, and add additional products to the bill. If " +"this is done, the :guilabel:`Should Be Paid` field status will be set to " +":guilabel:`Exception`. This means that Odoo notices the discrepancy, but " +"doesn't block the changes or display an error message, since there might be " +"a valid reason for making changes to the draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:97 +msgid "" +"Once payment has been registered for a vendor bill and displays the green " +":guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status will be" +" set to :guilabel:`No`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:101 +msgid "" +"The :guilabel:`Should Be Paid` status on bills is set automatically by Odoo." +" However, the status can be changed manually by clicking the field's drop-" +"down menu inside the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:106 +msgid "View a purchase order's billing status" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:108 +msgid "" +"When a purchase order is confirmed, its :guilabel:`Billing Status` can be " +"viewed under the :guilabel:`Other Information` tab on the purchase order " +"form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst-1 +msgid "Purchase order billing status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:115 +msgid "" +"Below is a list of the different statuses that a :guilabel:`Billing Status` " +"could appear as and when they are displayed, depending on the bill control " +"policy used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 +msgid ":guilabel:`Billing Status`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 +msgid "**Conditions**" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 +msgid "*On received quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 +msgid "*On ordered quantities*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid ":guilabel:`Nothing to Bill`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid "PO confirmed; no products received" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +msgid "*Not applicable*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid ":guilabel:`Waiting Bills`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid "All/some products received; bill not created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid "PO confirmed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid ":guilabel:`Fully Billed`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid "All/some products received; draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +msgid "Draft bill created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3 +msgid "Manage vendor bills" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:7 +msgid "" +"A *vendor bill* is an invoice received for products and/or services that a " +"company purchases from a vendor. Vendor bills record payables as they arrive" +" from vendors, and can include amounts owed for the goods and/or services " +"purchased, sales taxes, freight and delivery charges, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:11 +msgid "" +"In Odoo, a vendor bill can be created at different points in the purchasing " +"process, depending on the *bill control* policy chosen in the *Purchase* app" +" settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:17 +msgid "" +"To view and edit the default bill control policy and make changes to it, go " +"to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll " +"down to the :guilabel:`Invoicing` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:21 +msgid "" +"Here, there are two :guilabel:`Bill Control` policy options: " +":guilabel:`Ordered quantities` and :guilabel:`Received quantities`. After a " +"policy is selected, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Bill control policies in purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 +msgid "" +":guilabel:`Received quantities`: a bill is only created **after** part of " +"the total order has been received. The products and quantities **received** " +"are used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:37 +msgid "" +"If a product needs a different control policy, the default bill control " +"policy can be overridden by going to the :guilabel:`Purchase` tab in a " +"product's template, and modifying its :guilabel:`Control Policy` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Control policy field on product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:48 +msgid "" +"*3-way matching* ensures vendor bills are only paid once some (or all) of " +"the products included in the purchase order have actually been received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:51 +msgid "" +"To activate it, go to :menuselection:`Purchase app --> Configuration --> " +"Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, check" +" the box next to :guilabel:`3-way matching: purchases, receptions, and " +"bills`, and click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:56 +msgid "" +":guilabel:`3-way matching` is **only** intended to work with the " +":guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Activated three-way matching feature in purchase settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:64 +msgid "Create and manage vendor bills on receipts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:66 +msgid "" +"When products are received into a company's warehouse, receipts are created." +" Once the company processes the received quantities, they can choose to " +"create a vendor bill directly from the warehouse receipt form. Depending on " +"the bill control policy chosen in the settings, vendor bill creation is " +"completed at different steps of the procurement process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:72 +msgid "With the bill control policy set to ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:74 +msgid "" +"To create and manage vendor bills on receipts using the *ordered quantities*" +" bill control policy, first go to :menuselection:`Purchase app --> " +"Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Ordered quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:79 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new request for quotation (RFQ). Doing so reveals a blank " +":abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:82 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:144 +msgid "" +"On the blank detail form, add a vendor to the :abbr:`RFQ (request for " +"quotation)` in the :guilabel:`Vendor` field, and add products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:86 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:148 +msgid "" +"Then, confirm the :abbr:`RFQ (request for quotation)` by clicking the " +":guilabel:`Confirm Order` button above the detail form. Doing so turns the " +":abbr:`RFQ (request for quotation)` into a purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:90 +msgid "" +"Then, click the :guilabel:`Create Bill` button to create a vendor bill for " +"the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:92 +msgid "" +"Clicking the :guilabel:`Create Bill` button reveals the :guilabel:`Draft " +"Bill` page for the purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:95 +msgid "" +"On the :guilabel:`Draft Bill`, click the :guilabel:`Edit` button to modify " +"the bill, and add a bill date in the :guilabel:`Bill Date` field. If needed," +" add additional products to the :guilabel:`Product` lines by clicking " +":guilabel:`Add a line` in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:99 +msgid "" +"Next, confirm the bill by clicking the :guilabel:`Confirm` button on the " +":guilabel:`Draft Bill` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:103 +msgid "" +"Since the bill control policy is set to *ordered quantities*, the draft bill" +" can be confirmed as soon as it is created, before any products have been " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:106 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:179 +msgid "" +"On the new :guilabel:`Vendor Bill`, add a :guilabel:`Bill Reference` number," +" which can be used to match the bill with additional documents (such as the " +":abbr:`PO (purchase order)`). Then, click :menuselection:`Confirm --> " +"Register Payment`. Doing so causes a pop-up to appear, wherein a payment " +":guilabel:`Journal` can be chosen; a :guilabel:`Payment Method` selected; " +"and a :guilabel:`Recipient Bank Account` can be selected from a drop-down " +"menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:112 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the " +":guilabel:`Vendor Bill`. Doing so causes a green :guilabel:`In Payment` " +"banner to display on the :abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Vendor bill form for ordered quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:122 +msgid "" +"Each vendor bill provides the option to either :guilabel:`Add Credit Note` " +"or :guilabel:`Add Debit Note`. A *credit note* is typically issued when a " +"vendor or supplier of goods get some quantity of products back from the " +"customer to whom they were sold, while *debit notes* are reserved for goods " +"returned from the customer/buyer to the vendor or supplier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:128 +msgid "With the bill control policy set to received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:131 +msgid "" +"If the creation of a vendor bill is attempted without receiving any " +"quantities of a product (while using the *received quantities* bill control " +"policy), an error message appears, and settings must be changed before " +"proceeding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:135 +msgid "" +"To create and manage vendor bills on receipts using the *received " +"quantities* bill control policy, first go to :menuselection:`Purchase app " +"--> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` " +"section, and select :guilabel:`Received quantities` under :guilabel:`Bill " +"Control`. Then, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:140 +msgid "" +"Next, go to the :menuselection:`Purchase` app, and click :guilabel:`Create` " +"to create a new :abbr:`RFQ (request for quotation)`. Doing so reveals a " +"blank :abbr:`RFQ (request for quotation)` detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:152 +msgid "" +"Finally, click the :guilabel:`Create Bill` button to create a bill for the " +"purchase order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:155 +msgid "" +"Clicking :guilabel:`Create Bill` before any products have been received will" +" cause a :guilabel:`User Error` pop-up to appear. The :guilabel:`Purchase " +"Order` requires the receipt of at least partial quantity of the items " +"included on the order to create a vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "User error pop-up for received quantities control policy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:163 +msgid "" +"Next, click the :guilabel:`Receipt` smart button to view the warehouse " +"receipt form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:165 +msgid "" +"On the warehouse receipt form, click :menuselection:`Validate --> Apply` to " +"mark the :guilabel:`Done` quantities. Then, navigate back to the " +":menuselection:`Purchase Order` (via the breadcrumbs), and click the " +":guilabel:`Create Bill` button on the purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:169 +msgid "" +"Doing so reveals the :guilabel:`Draft Bill` for the purchase order. On the " +":guilabel:`Draft Bill`, click the :guilabel:`Edit` button, and add a " +":guilabel:`Bill Date`. If needed, add additional products to the " +":guilabel:`Product` lines by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:173 +msgid "" +"Next, click the :guilabel:`Confirm` button to confirm the :guilabel:`Draft " +"Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:176 +msgid "" +"Since the bill control policy is set to *received quantities*, the draft " +"bill can **only** be confirmed when at least some of the quantities are " +"received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:185 +msgid "" +"Additionally, the bill :guilabel:`Amount`, :guilabel:`Payment Date`, and " +":guilabel:`Memo` (:dfn:`Reference Number`) can be changed from this pop-up. " +"Once ready, click :guilabel:`Create Payment` to finish creating the vendor " +"bill. Doing so causes a green **In Payment** banner to display on the " +":abbr:`RFQ (request for quotation)` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:191 +msgid "Create and manage vendor bills in Accounting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:193 +msgid "" +"Vendor bills can also be created directly from the *Accounting* app, " +"**without** having to create a purchase order first. To do this, go to " +":menuselection:`Accounting app --> Vendors --> Bills`, and click " +":guilabel:`Create`. Doing so reveals a blank vendor bill detail form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:197 +msgid "" +"On this blank vendor bill detail form, add a vendor in the " +":guilabel:`Vendor` field, and add products to the :guilabel:`Product` lines " +"(under the :guilabel:`Invoice Lines` tab), by clicking :guilabel:`Add a " +"line`. Then, add a bill date in the :guilabel:`Bill Date` field, and any " +"other necessary information. Finally, click :guilabel:`Confirm` to confirm " +"the bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:202 +msgid "" +"From here, click the :guilabel:`Journal Items` tab to view (or change) the " +":guilabel:`Account` journals that were populated based on the configuration " +"on the corresponding :guilabel:`Vendor` and :guilabel:`Product` forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:206 +msgid "" +"Then, click :guilabel:`Add Credit Note` or :guilabel:`Add Debit Note` to add" +" credit or debit notes to the bill. Or, add a :guilabel:`Bill Reference` " +"number (while in :guilabel:`Edit` mode)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:209 +msgid "" +"Then, when ready, click :menuselection:`Register Payment --> Create Payment`" +" to complete the :guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:213 +msgid "" +"To tie the draft bill to an existing purchase order, click the drop-down " +"menu next to :guilabel:`Auto-Complete`, and select a :abbr:`PO (purchase " +"order)` from the menu. The bill will auto-populate with the information from" +" the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:0 +msgid "Auto-complete drop-down list on draft vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:222 +msgid "Batch billing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:224 +msgid "" +"Vendor bills can be processed and managed in batches in the *Accounting* " +"app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:226 +msgid "" +"To do this, go to :menuselection:`Accounting app --> Vendors --> Bills`. " +"Then, click the :guilabel:`checkbox` at the top left of the page, beside the" +" :guilabel:`Number` column, under the :guilabel:`Create` button. This " +"selects all existing vendor bills with a :guilabel:`Posted` or " +":guilabel:`Draft` :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:231 +msgid "" +"From here, click the :guilabel:`Action` gear icon to export, delete, or send" +" & print the bills; click the :guilabel:`Print` icon to print the invoices " +"or bills; or click :guilabel:`Register Payment` to create and process " +"payments for multiple vendor bills at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:235 +msgid "" +"When :guilabel:`Register Payment` is selected, a pop-up appears. In this " +"pop-up window, select the appropriate journal in the :guilabel:`Journal` " +"field, choose a payment date in the :guilabel:`Payment Date` field, and " +"choose a :guilabel:`Payment Method`. There is also the option to " +":guilabel:`Group Payments` on this pop-up, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:240 +msgid "" +"When ready, click the :guilabel:`Create Payment` button, which creates a " +"list of journal entries on a separate page. This list of journal entries are" +" all tied to their appropriate vendor bills." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst-1 +msgid "Batch billing register payment pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:248 +msgid "" +"The :guilabel:`Register Payment` option for vendor bills in batches will " +"only work for journal entries whose :guilabel:`Status` is set to " +":guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:252 +msgid "" +":doc:`/applications/inventory_and_mrp/purchase/manage_deals/control_bills`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products.rst:5 +msgid "Products" +msgstr "สินค้า" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:3 +msgid "Configure reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:5 +msgid "" +"For certain products, it is necessary to ensure that there is always a " +"minimum amount available on hand at any given time. By adding a reordering " +"rule to a product, it is possible to automate the reordering process so that" +" a purchase order is automatically created whenever the amount on hand falls" +" below a set threshold." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:11 +msgid "The *Inventory* module must be installed to use reordering rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:14 +msgid "Configure products for reordering" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:16 +msgid "" +"Products must be configured in a specific way before a reordering rule can " +"be added to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:18 +msgid "" +"Starting from the :menuselection:`Inventory`, " +":menuselection:`Manufacturing`, :menuselection:`Purchase`, or " +":menuselection:`Sales` module, navigate to :menuselection:`Products --> " +"Products` and then click :guilabel:`Create` to make a new product. " +"Alternatively, find a product that already exists in the database and click " +"into it's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:23 +msgid "" +"Next, on the product form, enable reordering by checking the :guilabel:`Can " +"be Purchased` option underneathe the :guilabel:`Product Name` field. " +"Finally, set the :guilabel:`Product Type` to `Storable Product` under the " +":guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure a product for reordering in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:32 +msgid "Add a reordering rule to a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:34 +msgid "" +"After properly configuring a product, a reordering rule can be added to it " +"by selecting the now visible :guilabel:`Reordering Rules` tab at the top of " +"that product's form, and then clicking :guilabel:`Create` on the " +":guilabel:`Reordering Rules` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Access reordering rules for a product from the product page in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:42 +msgid "" +"Once created, the reordering rule can be configured to generate purchase " +"orders automatically by defining the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:45 +msgid "" +":guilabel:`Location` specifies where the ordered quantities should be stored" +" once they are received and entered into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:47 +msgid "" +":guilabel:`Min Quantity` sets the lower threshold for the reordering rule " +"while :guilabel:`Max Quantity` sets the upper threshold. If the stock on " +"hand falls below the minimum quantity, a new purchase order will be created " +"to replenish it up to the maximum quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:52 +msgid "" +"If :guilabel:`Min Quantity` is set to `5` and :guilabel:`Max Quantity` is " +"set to `25` and the stock on hand falls to four, a purchase order will be " +"created for 21 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:55 +msgid "" +":guilabel:`Multiple Quantity` can be configured so that products are only " +"ordered in batches of a certain quantity. Depending on the number entered, " +"this can result in the creation of a purchase order that would put the " +"resulting stock on hand above what is specified in the :guilabel:`Max " +"Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:61 +msgid "" +"If :guilabel:`Max Quantity` is set to `100` but :guilabel:`Multiple " +"Quantity` is set to order the product in batches of `200`, a purchase order " +"will be created for 200 units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:65 +msgid "" +":guilabel:`UoM` specifies the unit of measurement by which the quantity will" +" be ordered. For discrete products, this should be set to `Units`. However, " +"it can also be set to units of measurement like `Volume` or `Weight` for " +"non-discrete products like water or bricks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst-1 +msgid "Configure the reordering rule in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:74 +msgid "Manually trigger reordering rules using the scheduler" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:76 +msgid "" +"Reordering rules will be automatically triggered by the scheduler, which " +"runs once a day by default. To trigger reordering rules manually, navigate " +"to :menuselection:`Inventory --> Operations --> Run Scheduler`. On the pop-" +"up window, confirm the manual action by clicking :guilabel:`Run Scheduler`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:82 +msgid "" +"Manually triggering reordering rules will also trigger any other scheduled " +"actions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:85 +msgid "Manage reordering rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:87 +msgid "" +"To manage the reordering rules for a single product, navigate to that " +"product page's form and select the :guilabel:`Reordering Rules` tab at the " +"top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/reordering.rst:90 +msgid "" +"To manage all reordering rules for every product, go to " +":menuselection:`Inventory --> Configuration --> Reordering Rules`. From this" +" dashboard, typical bulk actions in Odoo can be performed such as exporting " +"data or archiving rules that are no longer needed. As well, the " +":guilabel:`Filters`, :guilabel:`Group By` or triple-dotted menu on the form " +"are available to search for and/or organize the reordering rules as desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:3 +msgid "Purchase in different units of measure than sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:5 +msgid "" +"When you purchase a product, it may happen that your vendor uses a different" +" unit of measure than you do when you sell it. This can cause confusion " +"between sales and purchase representatives. It is also time-consuming to " +"convert measures manually every time. With Odoo, you can configure your " +"product once and let Odoo handle the conversion." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:10 +msgid "Consider the following examples:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:12 +msgid "" +"You purchase orange juice from an American vendor, and they use **gallons**." +" However, your customers are European and use **liters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:15 +msgid "" +"You buy curtains from a vendor in the form of **rolls** and you sell pieces " +"of the rolls to your customers using **square meters**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:19 +msgid "Enable units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:21 +msgid "" +"Open your Sales app and go to :menuselection:`Configuration --> Settings`. " +"Under Product Catalog, enable *Units of Measure*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Enable the units of measure option in Odoo Sales" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:29 +msgid "Specify sales and purchase units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:32 +msgid "Standard units of measure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:34 +msgid "" +"A variety of units of measure are available by default in your database. " +"Each belongs to one of the five pre-configured units of measure categories: " +"*Length / Distance*, *Unit*, *Volume*, *Weight* and *Working Time*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:39 +msgid "" +"You can create your new units of measure and units of measure categories " +"(see next section)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:41 +msgid "" +"To specify different units of measures for sales and purchases, open the " +"Purchase app and go to :menuselection:`Products --> Products`. Create a " +"product or select an existing one. Under the product's *General Information*" +" tab, first select the *Unit of Measure* to be used for sales (as well as " +"for other apps such as inventory). Then, select the *Purchase Unit of " +"Measure* to be used for purchases." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:47 +msgid "" +"Back to the first example, if you purchase orange juice from your vendor in " +"**gallons** and sell it to your customers in **liters**, first select *L* " +"(liters) as the *Unit of Measure*, and *gal (US)* (gallons) as the *Purchase" +" Unit of Measure*, then click on *Save*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Configure a product's units of measure in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:56 +msgid "Create new units of measure and units of measure categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:58 +msgid "" +"Sometimes you need to create your own units and categories, either because " +"the measure is not pre-configured in Odoo or because the units do not relate" +" with each other (e.g. kilos and centimeters)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:62 +msgid "" +"If you take the second example where you buy curtains from a vendor in the " +"form of **rolls** and you sell pieces of the rolls using **square meters**, " +"you need to create a new *Units of Measure Category* in order to relate both" +" units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:66 +msgid "" +"To do so, go to :menuselection:`Configuration --> Units of Measure " +"Categories`. Click on *Create* and name the category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new units of measure category in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:73 +msgid "" +"The next step is to create the two units of measures. To do so, go to " +":menuselection:`Configuration --> Units of Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:76 +msgid "" +"First, create the unit of measure used as the reference point for converting" +" to other units of measure inside the category by clicking on *Create*. Name" +" the unit and select the units of measure category you just created. For the" +" *Type*, select *Reference Unit of Measure for this category type*. Enter " +"the *Rounding Precision* you would like to use. The quantity computed by " +"Odoo is always a multiple of this value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:82 +msgid "" +"In the example, as you cannot purchase less than 1 roll and won't use " +"fractions of a roll as a unit of measure, you can enter 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a new reference unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:89 +msgid "" +"If you use a *Rounding Precision* inferior to 0.01, a warning message might " +"appear stating that it is higher than the *Decimal Accuracy* and that it " +"might cause inconsistencies. If you wish to use a *Rounding Precision* lower" +" than 0.01, first activate the :ref:`developer mode <developer-mode>`, then " +"go to :menuselection:`Settings --> Technical --> Database Structure --> " +"Decimal Accuracy`, select *Product Unit of Measure* and edit *Digits* " +"accordingly. For example, if you want to use a rounding precision of " +"0.00001, set *Digits* to 5." +msgstr "" +"หากคุณใช้ *ความแม่นยำในการปัดเศษ* ที่ต่ำกว่า 0.01 " +"ข้อความเตือนอาจปรากฏขึ้นโดยระบุว่ามีค่าสูงกว่า *ความแม่นยำของทศนิยม* " +"และอาจทำให้เกิดความไม่สอดคล้องกัน หากคุณต้องการใช้ *ความแม่นยำในการปัดเศษ* " +"ต่ำกว่า 0.01 ให้เปิดใช้งาน :ref:`โหมดนักพัฒนาซอฟต์แวร์ ` ก่อน จากนั้นไปที่ " +":menuselection:`การตั้งค่า --> เทคนิค --> โครงสร้างฐานข้อมูล --> " +"ความแม่นยำทศนิยม` เลือก *หน่วยวัดผลิตภัณฑ์* และแก้ไข *ตัวเลข* ตามลำดับ " +"ตัวอย่างเช่น หากคุณต้องการใช้ความแม่นยำในการปัดเศษที่ 0.00001 ให้ตั้งค่า " +"*ตัวเลข* เป็น 5" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:96 +msgid "" +"Next, create a second unit of measure, name it, and select the same units of" +" measure category as your reference unit. As *Type*, select *Smaller* or " +"*Bigger than the reference Unit of Measure*, depending on your situation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:100 +msgid "" +"As the curtain roll equals to 100 square meters, you should select " +"*Smaller*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:102 +msgid "" +"Next, you need to enter the *Ratio* between your reference unit and the " +"second one. If the second unit is smaller, the *Ratio* should be greater " +"than 1. If the second unit is larger, the ratio should be smaller than 1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:106 +msgid "For your curtain roll, the ratio should be set to 100." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Create a second unit of measure in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst:112 +msgid "" +"You can now configure your product just as you would using Odoo's standard " +"units of measure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/products/uom.rst-1 +msgid "Set a product's units of measure using your own units in Odoo Purchase" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality.rst:8 +msgid "Quality" +msgstr "คุณภาพ" + +#: ../../content/applications/inventory_and_mrp/quality.rst:10 +msgid "" +"**Odoo Quality** helps ensure product quality throughout manufacturing " +"processes and inventory movements. Conduct quality checks, automate quality " +"inspection frequency, and create quality alerts when issues arise." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality.rst:15 +msgid "" +"`Odoo Tutorials: Managing Quality Checks " +"<https://www.odoo.com/slides/slide/managing-quality-checks-708>`_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types.rst:5 +msgid "Quality check types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:3 +msgid "Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:7 +msgid "" +"In Odoo *Quality*, an *Instructions* check is one of the quality check types" +" that can be selected when creating a new quality check or quality control " +"point (QCP). *Instructions* checks consist of a text entry field that allows" +" the creator to provide instructions for how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:11 +msgid "" +"For a full overview of how to configure a quality check or a |QCP|, see the " +"documentation on :ref:`quality checks <quality/quality_management/quality-" +"checks>` and :ref:`quality control points " +"<quality/quality_management/quality-control-points>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:16 +msgid "Process an Instructions quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:18 +msgid "" +"There are multiple ways that *Instructions* quality checks can be processed." +" If a quality check is assigned to a specific manufacturing, inventory, or " +"work order, the check can be processed on the order itself. Alternatively, a" +" check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:23 +msgid "Process from the quality check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:25 +msgid "" +"To process an *Instructions* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:29 +msgid "" +"If the product passes the check, click the :guilabel:`Pass` button above the" +" quality check form. If the product does not pass the check, click the " +":guilabel:`Fail` button, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:33 +msgid "Process quality check on an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:35 +msgid "" +"To process an *Instructions* quality check on an order, select a " +"manufacturing order or inventory order (receipt, delivery, return, etc.) for" +" which a check is required. Manufacturing orders can be selected by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and clicking on an order. Inventory orders can be selected by " +"navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " +"Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:42 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears above the order. Click the button " +"to open the :guilabel:`Quality Check` pop-up window, from which any quality " +"checks created for the order can be processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst-1 +msgid "The Quality Check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:50 +msgid "" +"To complete an *Instructions* quality check, follow the instructions " +"detailed in the :guilabel:`Quality Check` pop-up window. Finally, click " +":guilabel:`Validate` to confirm that the check has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:54 +msgid "" +"If an issue or defect is found during the quality check, a quality alert may" +" need to be created to notify a quality team. To do so, click the " +":guilabel:`Quality Alert` button that appears at the top of the " +"manufacturing or inventory order after the check is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:58 +msgid "" +"Clicking :guilabel:`Quality Alert` opens a quality alert form on a new page." +" For a complete guide on how to fill out quality alert forms, view the " +"documentation on :ref:`quality alerts <quality/quality_management/quality-" +"alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:63 +msgid "Process work order quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:65 +msgid "" +"When configuring a |QCP| that is triggered by a manufacturing order, a " +"specific work order can also be specified in the :guilabel:`Work Order " +"Operation` field on the |QCP| form. If a work order is specified, an " +"*Instructions* quality check is created for that specific work order, rather" +" than the manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:70 +msgid "" +"Quality checks configured for work orders must be completed from the tablet " +"view. To do so, begin by navigating to :menuselection:`Manufacturing --> " +"Operations --> Manufacturing Orders`. Select a manufacturing order that " +"includes a work order for which a quality check is required. Open the tablet" +" view for that work order by clicking the :guilabel:`📱 (tablet)` button on " +"the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:75 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Instructions* quality check step is reached. Upon reaching" +" the check, the instructions for how to complete it will appear at the top " +"of the screen. Follow the instructions, then click :guilabel:`Next` to move " +"on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst-1 +msgid "An Instructions check for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:84 +msgid "" +"If an issue or defect is found during the quality check, a quality alert may" +" need to be created to notify a quality team. To do so, click the " +":guilabel:`☰ (menu)` button in the tablet view, and then select " +":guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:88 +msgid "" +"Clicking :guilabel:`Quality Alert` opens a :guilabel:`Quality Alerts` pop-up" +" window, from which a quality alert can be created. For a complete guide to " +"quality alert creation, view the documentation on :ref:`quality alerts " +"<quality/quality_management/quality-alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:3 +msgid "Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Measure* check is one of the quality check types that " +"can be selected when creating a new quality check or quality control point " +"(QCP). *Measure* checks prompt users to measure a certain aspect of a " +"product and record the measurement in Odoo. For the quality check to pass, " +"the recorded measurement must be within a certain *tolerance* of a *norm* " +"value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:14 +msgid "Create a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:16 +msgid "" +"There are two distinct ways that *Measure* quality checks can be created. A " +"single check can be manually created. Alternatively, a |QCP| can be " +"configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:20 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Measure* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"<quality/quality_management/quality-checks>` and :ref:`quality control " +"points <quality/quality_management/quality-control-points>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:27 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:26 +msgid "Quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:29 +msgid "" +"To create a single *Measure* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:32 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` " +"quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:34 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:33 +msgid "" +"In the :guilabel:`Team` drop-down field, select the quality team responsible" +" for managing the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:35 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:35 +msgid "" +"In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, " +"enter instructions for how the picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A quality check form configured for a Measure quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:43 +msgid "Quality control point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:45 +msgid "" +"To create a |QCP| that generates *Measure* quality checks automatically, " +"navigate to :menuselection:`Quality --> Quality Control --> Control Points`," +" and click :guilabel:`New`. Fill out the new |QCP| form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:49 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Measure` " +"quality check type. Doing so causes two new fields to appear: " +":guilabel:`Norm` and :guilabel:`Tolerance`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:52 +msgid "" +"Use the first text-entry field of the :guilabel:`Norm` field to record the " +"ideal measurement that the product should conform to. Use the second text-" +"entry field to specify the unit of measurement that should be used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:55 +msgid "" +"The :guilabel:`Tolerance` field features two sub-fields: :guilabel:`from` " +"and :guilabel:`to`. Use the :guilabel:`from` field to specify the minimum " +"acceptable measurement, and the :guilabel:`to` field to specify the maximum " +"acceptable measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:59 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:51 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:54 +msgid "" +"In the :guilabel:`Team` drop-down field, select the quality team responsible" +" for managing the checks created by the |QCP|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:61 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how the " +"measurement should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A QCP form configured to create Measure quality checks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:69 +msgid "Process a Measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:71 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:63 +msgid "" +"Once created, there are multiple ways that *Measure* quality checks can be " +"processed. If a quality check is assigned to a specific inventory, " +"manufacturing, or work order, the check can be processed on the order " +"itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:76 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:68 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:71 +msgid "From the check's page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:78 +msgid "" +"To process a *Measure* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to take the measurement." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:82 +msgid "" +"After taking the measurement, record the value in the :guilabel:`Measure` " +"field on the quality check form. To manually pass or fail the check, click " +":guilabel:`Pass` or :guilabel:`Fail` at the top-left corner of the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:86 +msgid "" +"Alternatively, if the quality check is assigned to a |QCP| for which *norm* " +"and *tolerance* values have been specified, click :guilabel:`Measure` at the" +" top-left corner of the check instead. Doing so automatically marks the " +"check as *Passed* if the recorded value is within the specified *tolerance*," +" or *Failed* if the value is outside of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:92 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:78 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:87 +msgid "On an order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:94 +msgid "" +"To process a *Measure* quality check on an order, select a manufacturing " +"order or inventory order (receipt, delivery, return, etc.), for which a " +"check is required. Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:101 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:96 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears at the top of the page. Click the " +"button to open the :guilabel:`Quality Check` pop-up window, which shows all " +"of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:105 +msgid "" +"To process a *Measure* quality check, measure the product as instructed, " +"then enter the value in the :guilabel:`Measure` field on the pop-up window. " +"Finally, click :guilabel:`Validate` to register the recorded value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "" +"A Measure quality check pop-up window on a manufacturing or inventory order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:113 +msgid "" +"If the value entered is within the range specified in the " +":guilabel:`Tolerance` section of the |QCP|, the quality check passes and the" +" pop-up window closes. The rest of the manufacturing or inventory order can " +"then be processed as usual." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:117 +msgid "" +"However, if the value entered is outside of the specified range, a new pop-" +"up window appears, titled :guilabel:`Quality Check Failed`. The body of the " +"pop-up shows a warning message that states, :guilabel:`You measured # units " +"and it should be between # units and # units.`, as well as the instructions " +"entered in the :guilabel:`Message If Failure` tab of the |QCP|. At the " +"bottom of the pop-up, two buttons appear: :guilabel:`Correct Measure` and " +":guilabel:`Confirm Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "The \"Quality Check Failed\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:127 +msgid "" +"If the measurement was not entered correctly and should be changed, select " +":guilabel:`Correct Measure`. Doing so re-opens the :guilabel:`Quality Check`" +" pop-up window. Enter the corrected measurement in the :guilabel:`Measure` " +"field, and then click :guilabel:`Validate` to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:132 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:185 +msgid "" +"If the measurement was entered correctly, click :guilabel:`Confirm Measure` " +"instead, and the quality check fails. Follow any instructions that were " +"listed on the :guilabel:`Quality Check Failed` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:136 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert " +"form on a new page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:140 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:193 +msgid "" +"For a complete guide on how to fill out the quality alert form, view the " +"documentation on :ref:`quality alerts <quality/quality_management/quality-" +"alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:144 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:106 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:120 +msgid "On a work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:146 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Measure* quality " +"check is created for that specific work order, rather than the manufacturing" +" order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:151 +msgid "" +"*Measure* quality checks created for work orders must be processed from the " +"tablet view. To do so, begin by navigating to :menuselection:`Manufacturing " +"--> Operations --> Manufacturing Orders`. Select a manufacturing order that " +"includes a work order for which a quality check is required. Open the tablet" +" view for that work order by selecting the :guilabel:`Work Orders` tab, and " +"then clicking the :guilabel:`📱 (tablet)` button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:157 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Measure* quality check step is reached. Upon reaching the " +"check, the instructions for how to take the measurement appear at the top of" +" the screen. Enter the measured value in the :guilabel:`Measure` field above" +" the instructions, and then click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst-1 +msgid "A Measure quality check in the Manufacturing tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:166 +msgid "" +"If the measurement entered is within the range specified in the " +":guilabel:`Tolerance` section of the |QCP|, the quality check passes and the" +" tablet view moves on to the next step of the work order. However, if the " +"measurement entered is outside of the specified range, a pop-up window " +"appears, titled :guilabel:`Quality Check Failed`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:171 +msgid "" +"The body of the :guilabel:`Quality Check Failed` pop-up window shows a " +"warning message that states, :guilabel:`You measured # units and it should " +"be between # units and # units.`, as well as the instructions entered in the" +" :guilabel:`Message If Failure` tab of the |QCP|. At the bottom of the pop-" +"up, two buttons appear: :guilabel:`Correct Measure` and :guilabel:`Confirm " +"Measure`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:180 +msgid "" +"If the measurement was not entered correctly, and should be changed, select " +":guilabel:`Correct Measure`. Doing so opens a new pop-up window, titled " +":guilabel:`Quality Check`. Enter the corrected measurement in the " +":guilabel:`Measure` field, then click :guilabel:`Validate` to complete the " +"check, and move on to the next step of the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/measure_check.rst:189 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(three horizontal lines)` button, and selecting :guilabel:`Quality Alert` " +"from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up" +" window appears, from which a quality alert can be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:3 +msgid "Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Pass - Fail* check is one of the quality check types " +"that can be selected when creating a new quality check or quality control " +"point (QCP). *Pass - Fail* checks consist of a text field that allows the " +"creator to specify a certain criteria that a product must meet to pass the " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:14 +msgid "Create a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:16 +msgid "" +"There are two distinct ways that *Pass - Fail* quality checks can be " +"created. A single check can be manually created. Alternatively, a |QCP| can " +"be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:20 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Pass - Fail* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"<quality/quality_management/quality-checks>` and :ref:`quality control " +"points <quality/quality_management/quality-control-points>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:29 +msgid "" +"To create a single *Pass - Fail* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:33 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:50 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Pass - Fail` " +"quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:36 +msgid "" +"In the :guilabel:`Instructions` text field of the :guilabel:`Notes` tab, " +"enter instructions for how to complete the quality check and the criteria " +"that must be met for the check to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "A quality check form configured for a Pass - Fail quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:44 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:43 +msgid "Quality Control Point (QCP)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:46 +msgid "" +"To create a |QCP| that generates *Pass - Fail* quality checks automatically," +" begin by navigating to :menuselection:`Quality --> Quality Control --> " +"Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:53 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how to " +"complete the quality check and the criteria that must be met for the check " +"to pass." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "" +"A Quality Control Point (QCP) form configured to create a Pass - Fail " +"quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:61 +msgid "Process a Pass - Fail quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:70 +msgid "" +"To process a *Measure* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and select a quality check. Follow the :guilabel:`Instructions` for" +" how to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:74 +msgid "" +"If the criteria for the check is met, click the :guilabel:`Pass` button at " +"the top-left corner of the page. If the criteria is not met, click the " +":guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:80 +msgid "" +"To process a *Pass - Fail* quality check on an order, select a manufacturing" +" order or inventory order (receipt, delivery, return, etc.), for which a " +"check is required. Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:87 +msgid "" +"On the selected manufacturing or inventory order, a purple " +":guilabel:`Quality Checks` button appears at the top of the order. Click the" +" button to open the :guilabel:`Quality Check` pop-up window, which shows all" +" of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:91 +msgid "" +"To process a *Pass - Fail* quality check, follow the instructions shown on " +"the :guilabel:`Quality Check` pop-up window. If the criteria for the check " +"is met, click the :guilabel:`Pass` button at the bottom of the window. If " +"the criteria is not met, click the :guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "" +"A Pass - Fail quality check pop-up window on a manufacturing or inventory " +"order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:99 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check fails. Clicking :guilabel:`Quality Alert` opens a quality alert " +"form on a new page. For a complete guide on how to fill out quality alert " +"forms, view the documentation on :ref:`quality alerts " +"<quality/quality_management/quality-alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:108 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Pass - Fail* " +"quality check is created for that specific work order, rather than the " +"manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:113 +msgid "" +"*Pass - Fail* quality checks configured for work orders must be processed " +"from the tablet view. To do so, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order that includes a work order for which a quality " +"check is required. Open the tablet view for that work order by selecting the" +" :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " +"button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:119 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Pass - Fail* quality check step is reached. Upon reaching " +"the check, follow the instructions that appear at the top of the screen. If " +"the criteria for the check is met, click the :guilabel:`Pass` button at the " +"top-right of the screen. If the criteria is not met, click the " +":guilabel:`Fail` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst-1 +msgid "A Pass - Fail check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:128 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(menu)` button in the tablet view, and selecting :guilabel:`Quality Alert` " +"from the :guilabel:`Menu` pop-up window. A :guilabel:`Quality Alerts` pop-up" +" window appears, from which a quality alert can be created. For a complete " +"guide on how to fill out quality alert forms, view the documentation on " +":ref:`quality alerts <quality/quality_management/quality-alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:3 +msgid "Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:8 +msgid "" +"In Odoo *Quality*, a *Take a Picture* check is one of the quality check " +"types that can be selected when creating a new quality check or quality " +"control point (QCP). *Take a Picture* checks require a picture to be " +"attached to the check, which can then be reviewed by a quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:13 +msgid "Create a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:15 +msgid "" +"There are two distinct ways that *Take a Picture* quality checks can be " +"created. A single check can be manually created. Alternatively, a |QCP| can " +"be configured that automatically creates checks at a predetermined interval." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:19 +msgid "" +"This documentation only details the configuration options that are unique to" +" *Take a Picture* quality checks and |QCPs|. For a full overview of all the " +"configuration options available when creating a single check or a |QCP|, see" +" the documentation on :ref:`quality checks " +"<quality/quality_management/quality-checks>` and :ref:`quality control " +"points <quality/quality_management/quality-checks>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:28 +msgid "" +"To create a single *Take a Picture* quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. Fill out the new quality check form as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:32 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:49 +msgid "" +"In the :guilabel:`Type` drop-down field, select the :guilabel:`Take a " +"Picture` quality check type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A quality check form configured for a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:45 +msgid "" +"To create a |QCP| that will generate *Take a Picture* quality checks " +"automatically, navigate to :menuselection:`Quality --> Quality Control --> " +"Control Points`, and click :guilabel:`New`. Fill out the new |QCP| form as " +"follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:50 +msgid "" +"If the *Maintenance* app is installed, a :guilabel:`Device` field appears " +"after selecting the *Take a Picture* check type. Use this field to specify a" +" device that should be used to take quality check pictures. For information " +"about managing devices in the *Maintenance* app, see the documentation on " +":ref:`adding new equipment " +"<maintenance/equipment_management/add_new_equipment>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:56 +msgid "" +"In the :guilabel:`Instructions` text field, enter instructions for how the " +"picture should be taken." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "" +"A Quality Control Point (QCP) form configured to create a Take a Picture " +"quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:64 +msgid "Process a Take a Picture quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:66 +msgid "" +"Once created, there are multiple ways that *Take a Picture* quality checks " +"can be processed. If a quality check is assigned to a specific inventory, " +"manufacturing, or work order, the check can be processed on the order " +"itself. Alternatively, a check can be processed from the check's page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:73 +msgid "" +"To process a *Take a Picture* quality check from the check's page, begin by " +"navigating to :menuselection:`Quality --> Quality Control --> Quality " +"Checks`, and then select a quality check. Follow the " +":guilabel:`Instructions` for how to take the picture." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:77 +msgid "" +"After taking the picture, make sure it is stored on the device being used to" +" process the quality check (computer, tablet, etc.). Then, click the " +":guilabel:`✏️ (pencil)` button in the :guilabel:`Picture` section to open " +"the device's file manager. In the file manager, navigate to the picture, " +"select it, and click :guilabel:`Open` to attach it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "The edit button (pencil) on a Take a Picture quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:89 +msgid "" +"To process a *Take a Picture* quality check on an order, select a " +"manufacturing order or inventory order (receipt, delivery, return, etc.), " +"for which a check is required. Manufacturing orders can be selected by " +"navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing" +" Orders`, and clicking on an order. Inventory orders can be selected by " +"navigating to :menuselection:`Inventory`, clicking the :guilabel:`# To " +"Process` button on an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:100 +msgid "" +"Follow the instructions detailing how to take the picture, which are shown " +"on the :guilabel:`Quality Check` pop-up window. After taking the picture, " +"make sure it is stored on the device being used to process the quality check" +" (computer, tablet, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:104 +msgid "" +"Then, click the :guilabel:`Take a Picture` button in the :guilabel:`Picture`" +" section to open the device's file manager. In the file manager, navigate to" +" the picture, select it, and click :guilabel:`Open` to attach it. Finally, " +"click :guilabel:`Validate` on the :guilabel:`Quality Check` pop-up window to" +" complete the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "" +"A Take a Picture quality check pop-up window on a manufacturing or inventory" +" order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:113 +msgid "" +"If a quality alert must be created, click the :guilabel:`Quality Alert` " +"button that appears at the top of the manufacturing or inventory order after" +" the check is validated. Clicking :guilabel:`Quality Alert` opens a quality " +"alert form on a new page. For a complete guide on how to fill out quality " +"alert forms, view the documentation on :ref:`quality alerts " +"<quality/quality_management/quality-alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:122 +msgid "" +"When configuring a |QCP| that is triggered during manufacturing, a specific " +"work order can also be specified in the :guilabel:`Work Order Operation` " +"field on the |QCP| form. If a work order is specified, a *Take a Picture* " +"quality check is created for that specific work order, rather than the " +"manufacturing order as a whole." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:127 +msgid "" +"*Take a Picture* quality checks created for work orders must be completed " +"from the tablet view. To do so, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. " +"Select a manufacturing order that includes a work order for which a quality " +"check is required. Open the tablet view for that work order by selecting the" +" :guilabel:`Work Orders` tab, and then clicking the :guilabel:`📱 (tablet)` " +"button on the order's line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the *Take a Picture* quality check step is reached. Upon " +"reaching the check, follow the instructions for how to take the picture, " +"which appear at the top of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:137 +msgid "" +"After taking the picture, make sure it is stored on the device being used to" +" process the work order (computer, tablet, etc.). Then, click the " +":guilabel:`Take a Picture` button to open the device's file manager. In the " +"file manager, navigate to the picture, select it, and click :guilabel:`Open`" +" to attach it. Finally, click :guilabel:`Validate` to complete the quality " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A Take a Picture check for a manufacturing work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:146 +msgid "" +"If a quality alert must be created, do so by clicking the :guilabel:`☰ " +"(three horizontal lines)` button in the tablet view, and selecting " +":guilabel:`Quality Alert` from the :guilabel:`Menu` pop-up window. A " +":guilabel:`Quality Alerts` pop-up window appears, from which a quality alert" +" can be created. For a complete guide on how to fill out quality alert " +"forms, view the documentation on :ref:`quality alerts " +"<quality/quality_management/quality-alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:153 +msgid "Review a picture attached to a check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:155 +msgid "" +"After a picture has been attached to a check, it can then be reviewed by " +"quality team members or other users. To do so, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and select " +"a quality check to review." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:159 +msgid "" +"The attached picture appears in the :guilabel:`Picture` section of the " +"quality check form. After reviewing the picture, click the :guilabel:`Pass` " +"button if the check passes, or the :guilabel:`Fail` button if the check " +"fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst-1 +msgid "A Take a Picture check with a picture attached." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management.rst:5 +msgid "Quality control basics" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:3 +msgid "Create quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:7 +msgid "" +"Configuring quality control points is a great way to ensure that quality " +"checks are performed at routine stages during specific operations. However, " +"quality issues can often appear outside of these scheduled checks. Using " +"Odoo *Quality*, users can create quality alerts for issues that are not " +"detected by automated processes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:13 +msgid ":doc:`Add quality control points <quality_control_points>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:16 +msgid "Find and fill out the quality alerts form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:18 +msgid "" +"In some situations, it is necessary to manually create quality alerts within" +" the *Quality* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:21 +msgid "" +"A helpdesk user who is notified of a product defect by a customer ticket can" +" create an alert that brings the issue to the attention of the relevant " +"quality team." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:24 +msgid "" +"To create a new quality alert, start from the :menuselection:`Quality` " +"module and select :menuselection:`Quality Control --> Quality Alerts --> " +"Create`. The quality alert form can then be filled out as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:28 +msgid "" +":guilabel:`Title`: choose a concise, yet descriptive title for the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:29 +msgid "" +":guilabel:`Product`: the product about which the quality alert is being " +"created" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:30 +msgid "" +":guilabel:`Product Variant`: the specific variant of the product that has " +"the quality issue, if applicable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:32 +msgid ":guilabel:`Lot`: the lot number assigned to the product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:33 +msgid "" +":guilabel:`Work Center`: the work center where the quality issue originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:34 +msgid "" +":guilabel:`Picking`: the picking operation during which the quality issue " +"originated" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:35 +msgid "" +":guilabel:`Team`: the quality team that will be notified by the quality " +"alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:36 +msgid "" +":guilabel:`Responsible`: the individual responsible for managing the quality" +" alert" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:37 +msgid "" +":guilabel:`Tags`: classify the quality alert based on user-created tags" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:38 +msgid ":guilabel:`Root Cause`: the cause of the quality issue, if known" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:39 +msgid "" +":guilabel:`Priority`: assign a priority between one and three stars to " +"ensure more urgent issues are prioritized" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:42 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:42 +msgid "" +"The tabs at the bottom of the form can be used to provide additional " +"information to quality teams:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:44 +msgid "" +":guilabel:`Description`: provide additional details about the quality issue" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:45 +msgid "" +":guilabel:`Corrective Actions`: the method for fixing affected products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:46 +msgid "" +":guilabel:`Preventive Actions`: procedures for preventing the issue from " +"occurring in the future" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:48 +msgid "" +":guilabel:`Miscellaneous`: the product vendor (if applicable), the company " +"that produces the product, and the date assigned" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst-1 +msgid "An example of a completed quality alert form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:56 +msgid "Add quality alerts during the manufacturing process" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:58 +msgid "" +"Odoo enables manufacturing employees to create quality alerts within a work " +"order without accessing the *Quality* module. From the work order tablet " +"view, click the :guilabel:` ☰ ` hamburger menu icon in the top left corner " +"and select :guilabel:`Quality Alert`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst-1 +msgid "Access the work order menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:66 +msgid "" +"The quality alert form can then be filled out as detailed in the previous " +"section. After saving the form, a new alert will appear on the " +":guilabel:`Quality Alerts` dashboard that can be found through the " +":menuselection:`Quality --> Quality Control` menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:71 +msgid "Manage existing quality alerts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:73 +msgid "" +"By default, quality alerts are organized in a kanban board view. The stages " +"of the kanban board are fully configurable and alerts can be moved from one " +"stage to the next by dragging and dropping or from within each alert. " +"Additional options are available for viewing alerts, including graph, " +"calendar, and pivot table views." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_alerts.rst:79 +msgid "" +"Filter alerts based on diverse criteria like date assigned or date closed. " +"Alerts can also be grouped by quality team, root cause, or other parameters " +"found under the :guilabel:`Filters` button menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:3 +msgid "Quality checks" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:8 +msgid "" +"Quality checks are manual inspections conducted by employees, and are used " +"to ensure the quality of products. In Odoo, a quality check can be conducted" +" for a single product, or multiple products within the same inventory " +"operation or manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:12 +msgid "" +"Using a Quality Control Point (QCP), it is possible to create quality checks" +" automatically at regular intervals. When quality checks are created by a " +"|QCP|, they appear on a manufacturing or inventory order, where the employee" +" processing the order will be prompted to complete them. For a full " +"explanation of how to create and configure a |QCP|, see the documentation on" +" :ref:`quality control points <quality/quality_management/quality-control-" +"points>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:18 +msgid "" +"While quality checks are most commonly created automatically by a |QCP|, it " +"is also possible to manually create a single quality check. Creating a check" +" manually is useful when an employee wants to schedule a quality check that " +"will only occur once, or register a quality check that they conduct " +"unprompted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:24 +msgid "Manual quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:26 +msgid "" +"To manually create a single quality check, navigate to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, and click " +":guilabel:`New`. On the quality check form, begin by selecting an option " +"from the :guilabel:`Control per` drop-down menu:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:30 +msgid "" +":guilabel:`Operation` requests a check for an entire operation (ex. delivery" +" order) and all products within it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:32 +msgid "" +":guilabel:`Product` requests a check for every unit of a product that is " +"part of an operation (ex. every unit of a product within a delivery order)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:34 +msgid "" +":guilabel:`Quantity` requests a check for every quantity of a product that " +"is part of an operation (ex. one check for five units of a product within a " +"delivery order). Selecting :guilabel:`Quantity` also causes a " +":guilabel:`Lot/Serial` drop-down field to appear, from which can be selected" +" a specific lot or serial number that the quality check should be conducted " +"for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:39 +msgid "" +"Next, select an inventory operation from the :guilabel:`Picking` drop-down " +"menu or a manufacturing order from the :guilabel:`Production Order` drop-" +"down menu. This is necessary because Odoo needs to know for which operation " +"the quality check is being conducted." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:43 +msgid "" +"If the quality check should be assigned to a specific |QCP|, select it from " +"the :guilabel:`Control Point` drop-down menu. This is useful if the quality " +"check is being created manually, but should still be recognized as belonging" +" to a specific |QCP|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:47 +msgid "Select a quality check type from the :guilabel:`Type` drop-down field:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:49 +msgid "" +":guilabel:`Instructions` provides specific instructions for how to conduct " +"the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:50 +msgid "" +":guilabel:`Take a Picture` requires a picture to be attached to the check " +"before the check can be completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:52 +msgid "" +":guilabel:`Pass - Fail` is used when the product being checked must meet a " +"certain criteria to pass the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:54 +msgid "" +"Selecting :guilabel:`Measure` causes a :guilabel:`Measure` input field to " +"appear, in which a measurement must be entered before the check can be " +"completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:56 +msgid "" +"Selecting :guilabel:`Worksheet` causes a :guilabel:`Quality Template` drop-" +"down field to appear. Use it to select a quality worksheet that must be " +"filled out to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:59 +msgid "" +"In the :guilabel:`Team` field, select the quality team that is responsible " +"for the quality check. In the :guilabel:`Company` field, select the company " +"that owns the product being inspected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:62 +msgid "" +"On the :guilabel:`Notes` tab at the bottom of the form, enter any relevant " +"instructions in the :guilabel:`Instructions` text entry box (ex. 'Attach a " +"picture of the product'). In the :guilabel:`Notes` text entry box, enter any" +" relevant information about the quality check (who created it, why it was " +"created, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:67 +msgid "" +"Finally, if the check is being processed immediately, click the " +":guilabel:`Pass` button at the top left of the screen if the check passes, " +"or the :guilabel:`Fail` button if the check fails." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "A quality check form filled out for a Pass - Fail check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:75 +msgid "Process quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:77 +msgid "" +"Quality checks can be processed directly on the quality check's page, or " +"from a manufacturing or inventory order for which a check is required. " +"Alternatively, if a quality check is created for a specific work order " +"operation, the check is processed in the tablet view for the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:82 +msgid "" +"It is not possible to manually create a single quality check that is " +"assigned to a specific work order operation. Quality checks for work order " +"operations can only be created by a |QCP|. See the documentation on " +":ref:`Quality Control Points <quality/quality_management/quality-control-" +"points>` for information about how to configure a |QCP| that will create " +"quality checks for a specific work order operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:89 +msgid "Quality check page" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:91 +msgid "" +"To process a quality check from the check's page, begin by navigating to " +":menuselection:`Quality --> Quality Control --> Quality Checks`, then select" +" the check to process. Follow the instructions for how to complete the " +"check, listed in the :guilabel:`Instructions` field of the :guilabel:`Notes`" +" tab at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:96 +msgid "" +"If the quality check passes, click the :guilabel:`Pass` button at the top of" +" the page. If the check fails, click the :guilabel:`Fail` button, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:100 +msgid "Quality check on order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:102 +msgid "" +"To process a quality check on an order, select a manufacturing or inventory " +"order (receipt, delivery, return, etc.), for which a check is required. " +"Manufacturing orders can be selected by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and " +"clicking on an order. Inventory orders can be selected by navigating to " +":menuselection:`Inventory`, clicking the :guilabel:`# To Process` button on " +"an operation card, and selecting an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:108 +msgid "" +"On the selected inventory or manufacturing order, a purple " +":guilabel:`Quality Checks` button appears at the top of the order. Click the" +" button to open the :guilabel:`Quality Check` pop-up window, which shows all" +" of the quality checks required for that order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:112 +msgid "" +"Follow the instructions that appear on the :guilabel:`Quality Check` pop-up " +"window. If a Pass - Fail check is being processed, complete the check by " +"clicking :guilabel:`Pass` or :guilabel:`Fail` at the bottom of the pop-up " +"window. For all other quality check types, a :guilabel:`Validate` button " +"appears instead. Click it to complete the check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "The \"Quality Check\" pop-up window on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:122 +msgid "Quality check on work order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:124 +msgid "" +"To process a quality check for a work order, begin by navigating to " +":menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then" +" select a manufacturing order. Select the :guilabel:`Work Orders` tab, then " +"click the :guilabel:`📱 (tablet)` tablet view button for the work order that " +"requires the quality check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 +msgid "" +"With tablet view open, complete the steps listed on the left side of the " +"screen until the quality check step is reached, then follow the instructions" +" at the top of the screen. If a Pass - Fail check is being processed, " +"complete the check by clicking :guilabel:`Pass` or :guilabel:`Fail` at the " +"top of the screen. For all other quality check types, a :guilabel:`Next` " +"button appears instead. Click it to complete the check and move on to the " +"next step of the work order." +msgstr "" +"เมื่อเปิดมุมมองแท็บเล็ต " +"ให้ทำตามขั้นตอนที่แสดงทางด้านซ้ายของหน้าจอจนกว่าจะถึงขั้นตอนการตรวจสอบคุณภาพ" +" จากนั้นทำตามคำแนะนำที่ด้านบนของหน้าจอ หากกำลังดำเนินการตรวจสอบ ผ่าน - " +"ไม่ผ่าน ให้ตรวจสอบให้เสร็จสิ้นโดยคลิก :guilabel:`ผ่าน` หรือ " +":guilabel:`ไม่ผ่าน` ที่ด้านบนของหน้าจอ สำหรับการตรวจสอบคุณภาพประเภทอื่นๆ " +"ทั้งหมด ปุ่ม :guilabel:`ถัดไป` จะปรากฏขึ้นแทน " +"คลิกเพื่อดำเนินการตรวจสอบให้เสร็จสิ้น และไปยังขั้นตอนถัดไปของใบสั่งงาน" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst-1 +msgid "A quality check for a work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:3 +msgid "Add quality controls" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:7 +msgid "" +"Use Odoo *Quality* to control the quality of products before they are " +"registered into stock, during picking operations, and when leaving the " +"warehouse for a delivery order. By creating *quality control points*, " +"manufacturers can set up quality checks that automatically trigger at " +"specific points during production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:13 +msgid "Configure quality control points" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:15 +msgid "" +"To create a new quality control point, go to :menuselection:`Quality Control" +" --> Control Points --> Create`. Then, fill in the following form fields, " +"accordingly:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:18 +msgid "" +":guilabel:`Title`: give the quality control point a simple, but informative " +"title so production floor and quality check teams can understand it easily" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:20 +msgid "" +":guilabel:`Products`: indicate which product(s) should pass through the " +"specific quality control point" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:22 +msgid "" +":guilabel:`Operations`: determine which operations team(s) should perform " +"the quality control check (e.g., `Manufacturing`, `Receipts`, `Delivery " +"Orders`, etc.)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:24 +msgid "" +":guilabel:`Work Order Operation`: for manufacturing operations, use the " +"drop-down menu to indicate which type of work order the quality control " +"point applies to: :guilabel:`Manual Assembly`, :guilabel:`Packing`, " +":guilabel:`Assembly`, :guilabel:`Testing` or :guilabel:`Long time assembly`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:28 +msgid "" +":guilabel:`Company`: add the company that will implement the quality control" +" point. Usually this will be the company that owns the Odoo database. " +"However, a multi-company or vendor profile can be selected, as well, for " +"cases where there are multiple manufacturing or engineering locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:31 +msgid "" +":guilabel:`Control Type`: using the drop-down menu, choose from " +":guilabel:`All Operations`, :guilabel:`Randomly` or :guilabel:`Periodically`" +" to determine how often the control point should executed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:34 +msgid "" +":guilabel:`Type`: using the drop-down menu, choose the control point type: " +":guilabel:`Instructions`, :guilabel:`Take a Picture`, :guilabel:`Pass - " +"Fail`, or :guilabel:`Measure`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:37 +msgid "" +":guilabel:`Team`: decide which quality team should receive the results of " +"the quality control point check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:39 +msgid "" +":guilabel:`Responsible`: add a point person to manage the status and " +"evolution of the quality control point over time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:44 +msgid ":guilabel:`Instructions`: describe the quality check to be performed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:45 +msgid "" +":guilabel:`Message If Failure`: detail what should be done if the check " +"fails" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:46 +msgid ":guilabel:`Notes`: use to include any additional information" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst-1 +msgid "" +"An example of a completed quality control point form for a Pass-Fail test." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:52 +msgid "" +"Once a control point has been configured, a quality check will be " +"automatically created and assigned when the specified operation or work " +"order has been reached. Quality checks can be managed by selecting " +":menuselection:`Quality Control --> Quality Checks`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:57 +msgid "" +"To see all of the quality checks created by a control point, go to " +":menuselection:`Quality Control --> Control Points`, select a control point," +" and click :guilabel:`Quality Checks` in the top right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:62 +msgid "Use case: configure a measure quality check" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:64 +msgid "" +"To ensure that a product meets specific measurement requirements, select " +":guilabel:`Measure` from the :guilabel:`Type` drop-down menu. Selecting the " +":guilabel:`Measure` quality check type reveals three new fields: " +":guilabel:`Device`, :guilabel:`Norm`, and :guilabel:`Tolerance`. These " +"fields can be configured so that only products within a certain tolerance " +"will pass the check:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:69 +msgid "" +":guilabel:`Device`: select the measuring device that should be used to take " +"the measurement (e.g., measuring tape)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:71 +msgid "" +":guilabel:`Norm`: specify the desired measurement that the product should " +"conform to and the unit of measurement that should be used" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:73 +msgid "" +":guilabel:`Tolerance`: select the range that a measurement can be within " +"while still passing the check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to`" +" 60.5 mm)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst-1 +msgid "" +"An example of a quality control point form configured for a measure quality " +"check." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:80 +msgid "" +"When the quality control points form is complete, click :guilabel:`Save`. " +"Now, this measurement-based test will trigger for products that were " +"specified on the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:83 +msgid "" +"When production of the specified product reaches the operation that requires" +" a measure quality check, the manufacturing employee responsible will be " +"prompted to record and validate the measured value in the tablet view. For " +"products that measure within the values indicated in the " +":guilabel:`Tolerance` fields, the test will pass. However, for products that" +" measure outside of those values, the test will fail. In that case, the " +"worker who performed the check would create a quality alert from the tablet " +"view. That quality alert can then be addressed by the quality management " +"team." +msgstr "" +"เมื่อการผลิตผลิตภัณฑ์ที่ระบุถึงการดำเนินการที่ต้องมีการตรวจสอบคุณภาพการวัด " +"พนักงานฝ่ายผลิตที่รับผิดชอบจะได้รับแจ้งให้บันทึกและตรวจสอบความถูกต้องของค่าที่วัดได้ในมุมมองแท็บเล็ต" +" สำหรับผลิตภัณฑ์ที่วัดภายในค่าที่ระบุในช่อง :guilabel:`พิกัดความเผื่อ` " +"การทดสอบจะผ่าน อย่างไรก็ตาม สำหรับผลิตภัณฑ์ที่วัดผลนอกค่าเหล่านั้น " +"การทดสอบจะล้มเหลว ในกรณีนั้น " +"ผู้ปฏิบัติงานที่ดำเนินการตรวจสอบจะสร้างการแจ้งเตือนคุณภาพจากมุมมองแท็บเล็ต " +"การแจ้งเตือนด้านคุณภาพนั้นสามารถแก้ไขได้โดยทีมผู้บริหารคุณภาพ" diff --git a/locale/th/LC_MESSAGES/marketing.po b/locale/th/LC_MESSAGES/marketing.po new file mode 100644 index 000000000..195f484dd --- /dev/null +++ b/locale/th/LC_MESSAGES/marketing.po @@ -0,0 +1,6527 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Chatcha Mee, 2024 +# Rasareeyar Lappiam, 2024 +# Wil Odoo, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Wil Odoo, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/marketing.rst:5 +msgid "Marketing" +msgstr "การตลาด" + +#: ../../content/applications/marketing/email_marketing.rst:6 +msgid "Email marketing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:8 +msgid "" +"Emails are an effective, fully-customizable form of communication that are " +"able to reach any target audience - large or small. The success of an email " +"is easily measurable, especially when a creative call-to-action is involved." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:12 +msgid "" +"Odoo *Email Marketing* provides professional-grade email design tools, " +"templates, and features, designed to simplify the otherwise complex process " +"required to create engaging emails, build successful campaigns, and track " +"their overall effectiveness in a single application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:17 +#: ../../content/applications/marketing/email_marketing.rst:219 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74 +msgid ":doc:`/applications/marketing/email_marketing/mailing_lists`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:18 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:136 +msgid ":doc:`/applications/marketing/email_marketing/unsubscriptions`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:21 +msgid "Email marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:23 +msgid "" +"To get started, click on the :menuselection:`Email Marketing` app icon, " +"located on the main Odoo dashboard, which leads to the main :guilabel:`Email" +" Marketing` dashboard (in the default kanban view)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:27 +msgid "" +"To see all the mailings in the database, remove the default :guilabel:`My " +"Mailings` filter from the search bar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the main dashboard of the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:35 +msgid "" +"In the search bar, by default, the filter: :guilabel:`My Mailings` is " +"present. That means the only information being seen (at that time) on the " +":guilabel:`Email Marketing` dashboard are emails that the current user has " +"created, sent, or is responsible for." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:39 +msgid "" +"This filter can be removed by clicking the :guilabel:`X` next to " +":guilabel:`My Mailings` in the search bar. Doing so, reveals all the " +"information for every email in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:43 +msgid "Default kanban view and stages" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:45 +msgid "" +"The four kanban columns each represent the various stages of emails that " +"have been built or sent within the *Email Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:48 +msgid "" +"The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, " +":guilabel:`Sending`, :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:50 +msgid ":guilabel:`Draft`: means the email is still being written/created." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:51 +msgid "" +":guilabel:`In Queue`: means the email is scheduled, and sent at a later " +"date." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:52 +msgid "" +":guilabel:`Sending`: means the email is currently being sent to its " +"recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:53 +msgid "" +":guilabel:`Sent`: means the email has already been sent to its recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:55 +msgid "" +"In each stage, there are drag-and-drop cards representing the email " +"campaigns that have been created, and the stage they are in represents the " +"current status of that mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:58 +msgid "" +"Each mailing block on the :guilabel:`Email Marketing` dashboard provides key" +" information related to that specific email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:61 +msgid "" +"When the cursor hovers over the upper-right corner of an email campaign " +"card, three vertical dots (:guilabel:`⋮`) appear. When clicked, a mini drop-" +"down menu reveals the option to color-code the email :guilabel:`Delete` the " +"email altogether, or :guilabel:`Archive` the message for potential future " +"use." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the three-dot drop-down menu on the Odoo Email Marketing dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:70 +msgid "" +"In the upper-right corner of the main :guilabel:`Email Marketing` dashboard," +" there are other view options to choose from: :guilabel:`List` and " +":guilabel:`Graph`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:74 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 +msgid "List view" +msgstr "ดูล่าสุด" + +#: ../../content/applications/marketing/email_marketing.rst:76 +msgid "" +"The :guilabel:`List` view (represented by the :guilabel:`☰ (three vertical " +"lines)` icon) provides the same key information, but in a classic list " +"format." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "How the List view appears in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:84 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:86 +msgid "" +"The :guilabel:`Graph` view (represented by the :guilabel:`📊 (bar graph)` " +"icon) provides the same key information, but in a variety of customizable " +"graph (and chart) layouts." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "How the Graph view appears in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:93 +msgid "" +"In the upper-left corner, there is a :guilabel:`Measures` menu, providing " +"even more filter options to further customize the graph views." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:96 +msgid "" +"Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage`, " +":guilabel:`Color Index`, and :guilabel:`Count` (which is selected, by " +"default)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:100 +msgid "Filters, Group By, and Favorites search options" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:102 +msgid "" +"Regardless of the view chosen for the :guilabel:`Email Marketing` dashboard," +" the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` " +"options are always available." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:105 +msgid "" +"These options provide various ways to specify and organize the information " +"seen on the :guilabel:`Email Marketing` dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:110 +msgid "Filters" +msgstr "ตัวกรอง" + +#: ../../content/applications/marketing/email_marketing.rst:112 +msgid "" +"This drop-down menu provides different ways to filter email campaigns on the" +" dashboard. The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`," +" :guilabel:`Archived`, and :guilabel:`Add Custom Filter`. If :guilabel:`Add " +"Custom Filter` is selected, Odoo reveals an additional drop-down menu, with " +"three customizable fields to fill in, in order to retrieve results that fit " +"more specific criteria." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of filters drop-down menu options on the Odoo Email Marketing " +"dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:121 +msgid "Group By" +msgstr "กลุ่มโดย" + +#: ../../content/applications/marketing/email_marketing.rst:123 +msgid "" +"This drop-down menu provides additional ways to organize the data on the " +"dashboard by grouping them in specific ways. Using this drop-down menu, the " +"data can be grouped by the messages' :guilabel:`Status`, or who it was " +":guilabel:`Sent By`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:127 +msgid "" +"There is also the option to group the data by :guilabel:`Sent Period`, which" +" has its own sub-menu of options to choose from. The :guilabel:`Sent Period`" +" options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, " +":guilabel:`Week`, and :guilabel:`Day`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:131 +msgid "" +"If none of the above :guilabel:`Group By` options deliver the desired " +"results, click :guilabel:`Add Custom Group` at the bottom of the drop-down " +"menu. Doing so reveals a new field, wherein custom criteria can be selected " +"and applied, thus delivering any grouping of data that may be desired." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of the Group By drop-down menu on the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:139 +msgid "Favorites" +msgstr "รายการโปรด" + +#: ../../content/applications/marketing/email_marketing.rst:141 +msgid "" +"This drop-down menu provides different ways to incorporate past search " +"filters and other record-related options to customize the dashboard. The " +"options are: :guilabel:`Save current search`, :guilabel:`Import records`, " +":guilabel:`Add to my dashboard`, and :guilabel:`Add to Google Spreadsheet`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "" +"View of the Favorites drop-down menu on the Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:150 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/applications/marketing/email_marketing.rst:152 +msgid "" +"To view (and modify) the *Email Marketing* settings, navigate to " +":menuselection:`Email Marketing application --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the Settings page in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:159 +msgid "" +"On this :guilabel:`Settings` page, there are three features available. The " +"features are: :guilabel:`Mailing Campaigns`, :guilabel:`Blacklist Option " +"when Unsubscribing`, and :guilabel:`Dedicated Server`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:163 +msgid "" +":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:164 +msgid "" +":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to " +"blacklist themselves from future mailings during the unsubscribing process." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:166 +msgid "" +":guilabel:`Dedicated Server`: provides the option to utilize a separate, " +"dedicated server for mailings. When enabled, Odoo reveals a new field (and " +"link), in which the specific server configurations must be entered, in order" +" for it to connect properly to Odoo." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:171 +msgid "Create an email" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:173 +msgid "" +"To create an email, open the :menuselection:`Email Marketing` application, " +"and click the :guilabel:`Create` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:176 +msgid "Clicking :guilabel:`Create` reveals a blank email detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of a blank email detail form in Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:182 +msgid "" +"First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is " +"visible in the recipients' inbox, allowing them to get quickly see what the " +"message is about." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:186 +msgid "" +"The :guilabel:`Subject` field is mandatory. An email can not be sent without" +" a :guilabel:`Subject`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:190 +msgid "" +"The :guilabel:`☺ (smiley face)` icon at the end of the :guilabel:`Subject` " +"field (and :guilabel:`Preview Text` field) represents emojis. Click that " +":guilabel:`☺ (smiley face)` icon to reveal a menu of emojis that can be used" +" in either field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:194 +msgid "" +"Next, there is the option to enter some :guilabel:`Preview Text`. This text " +"is a catchy preview sentence that encourages recipients to open the message." +" In most inboxes, this is displayed next to the subject." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:199 +msgid "" +"Keep the :guilabel:`Preview Text` empty to show the first characters of the " +"email content, instead." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:203 +msgid "Recipients" +msgstr "ผู้รับ" + +#: ../../content/applications/marketing/email_marketing.rst:205 +msgid "" +"After that, it's time to choose the recipients of this email, which can be " +"completed in the :guilabel:`Recipients` field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of recipients drop-down menu in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:212 +msgid "" +"The default option is :guilabel:`Mailing List`. If :guilabel:`Mailing List` " +"option is selected, a specific :guilabel:`Mailing List` needs to be chosen " +"from the adjacent :guilabel:`Select mailing lists` field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:216 +msgid "" +"Then, Odoo will only send this email to contacts on that specific mailing " +"list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:221 +msgid "" +"When the :guilabel:`Recipients` field is clicked, a drop-down menu of other " +"options is revealed. Each option provides different ways Odoo can create a " +"target audience for the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:224 +msgid "" +"Those options (excluding the default :guilabel:`Mailing List`) provide the " +"option to create a more specified recipient filter, in an equation-like " +"format." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:227 +msgid "The :guilabel:`Recipients` field options are as follows:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:229 +msgid "" +":guilabel:`Applicant`: filter focuses on specific job applicants in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:230 +msgid "" +":guilabel:`Contact`: filter focuses on specific contacts in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:231 +msgid "" +":guilabel:`Event Registration`: filter focuses on people in the database who" +" purchased event registrations." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:233 +msgid "" +":guilabel:`Event Track`: filter focuses on people in the database who hosted" +" a specific talk (track) at an event." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:235 +msgid "" +":guilabel:`Lead/Opportunity`: filter focuses on leads or opportunities in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:236 +msgid "" +":guilabel:`Mailing Contact`: filter focuses on specific mailing contacts in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:237 +msgid "" +":guilabel:`Sales Order`: filter focuses on a specific sales orders in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:239 +msgid "" +"If the specified recipient fields don't automatically reveal themselves, " +"simply click the :guilabel:`Add Filter` button beneath the " +":guilabel:`Recipients` field, and Odoo reveals the necessary equation fields" +" to further drill down the target recipients for this mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:244 +msgid "Add a recipient filter" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:246 +msgid "" +"To add a more specified recipient filter, select any recipient option (other" +" than :guilabel:`Mailing List`), and clicking :guilabel:`Add Filter`, if " +"needed, to reveal three fields, formatted like an equation." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:250 +msgid "" +"To reveal the sub-menu options, click each field, and make the desired " +"selections, until the preferred configuration has been achieved. The number " +"of :guilabel:`Records` that match the rule(s) are indicated to the right of " +"the :guilabel:`Recipients` field, in green." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of how recipient filters can be customized in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:259 +#: ../../content/applications/marketing/events/event_essentials.rst:191 +msgid "" +"Some sub-menu options in the first rule field allow for a second choice to " +"provide even more specificity." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:262 +msgid "" +"To the right of each rule, are :guilabel:`× (Delete node)`, :guilabel:`＋ " +"(Add node)`, and :guilabel:`⋯ (Add branch)` icons." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:265 +msgid "" +"The :guilabel:`× (Delete node)` icon deletes a specific node (line) of the " +"rule. The :guilabel:`＋ (Add node)` icon adds a node (line) to the rule. And," +" the :guilabel:`⋯ (Add branch)` icon adds a branch to the node. A branch " +"means two additional, indented sub-nodes are added to the rule, providing " +"even more specificity to the line above it." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:271 +msgid "Mail body tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:273 +msgid "" +"At the bottom of the email form are two tabs: :guilabel:`Mail Body` and " +":guilabel:`Settings`. Let's focus on :guilabel:`Mail Body` tab first." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:276 +msgid "" +"In the :guilabel:`Mail Body` tab, there are a number of pre-configured " +"message templates to choose from. Select the desired template, and modify " +"every element of its design details with Odoo's drag-and-drop building " +"blocks, located on the right sidebar. Each building block provides unique " +"features and professional design elements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the building blocks used to create mailings in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:286 +msgid "" +"To build an email from scratch, select the :guilabel:`Plain Text` template, " +"and Odoo provides a blank email canvas, which can be customized in a number " +"of ways - either by using the front-end rich text editor that accepts slash " +"(:guilabel:`/`) commands, or with the XML code editor when :ref:`Developer " +"Mode (debug mode) <developer-mode>` is engaged, and the :guilabel:`</>` icon" +" is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:293 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:295 +msgid "" +"To the right of the :guilabel:`Mail Body` tab is the :guilabel:`Settings` " +"tab." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:298 +msgid "" +"The options available in the :guilabel:`Settings` tab will be different, " +"depending on if the :guilabel:`Mailing Campaigns` feature is activated in " +"the :guilabel:`Settings` page of the :menuselection:`Email Marketing` " +"application (:menuselection:`Email Marketing --> Configuration --> " +"Settings`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:303 +msgid "" +"Without the :guilabel:`Mailing Campaigns` feature activated, the " +":guilabel:`Settings` tab on the email detail form looks like this:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of settings tab in Odoo Email Marketing app, without settings " +"activated." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:310 +msgid "" +":guilabel:`Responsible`: choose an employee (in the database) to be " +"responsible for this particular email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:312 +msgid "" +":guilabel:`Send From`: designate an email alias that'll display as the " +"sender of this particular email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:314 +msgid "" +":guilabel:`Reply To`: designate an email alias to whom all the replies to " +"this particular email will be sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:316 +msgid "" +":guilabel:`Attachments`: if any specific documents are required (or helpful)" +" for this event invite, they can be sent along with this email, by clicking " +":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:320 +msgid "" +"When the :guilabel:`Mailing Campaigns` feature *is* activated, additional " +":guilabel:`Marketing` options appear in the :guilabel:`Settings` tab, which " +"look like this:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of settings tab in Odoo Email Marketing when settings are activated." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:327 +msgid "" +"The additional features are: :guilabel:`Mailing Campaign`, :guilabel:`Allow " +"A/B Testing`, and :guilabel:`A/B Testing percentage`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:331 +msgid "Mailing campaigns" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:333 +msgid "" +"The :guilabel:`Mailing Campaign` field provides the option to add this " +"particular email to a previously-made email campaign in the database. Click " +"the empty field to reveal a drop-down menu containing all previously-made " +"mailing campaigns in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of a mailing campaign drop-down menu in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:341 +msgid "" +"If the desired campaign isn't available in the initial drop-down menu, " +"select :guilabel:`Search More` to reveal a complete list of all mailing " +"campaigns in the database. Or, type the name of the desired mailing campaign" +" in the :guilabel:`Mailing Campaign` field, until Odoo reveals the desired " +"campaign in the drop-down menu. Then, select the desired campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:347 +msgid "Create new mailing campaign (from Settings tab)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:349 +msgid "" +"To create a new campaign from this :guilabel:`Mailing Campaign` field, start" +" typing the name of this new campaign, and select :guilabel:`Create " +"[Campaign Name]` or :guilabel:`Create and Edit...`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:352 +msgid "" +"Click :guilabel:`Create` to add this new mailing campaign to the database, " +"and modify its settings in the future. And click :guilabel:`Create and " +"Edit...` to add this new mailing campaign to the database, and Odoo reveals " +"a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "" +"View of the email mailing campaign pop-up window in Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:360 +msgid "" +"Here, the new mailing campaign can be further customized. Adjust the " +":guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add " +":guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:363 +msgid "" +"The top row of the :guilabel:`Create: Mailing Campaign` pop-up window is " +"filled with analytical smart buttons. Each of which displays various metrics" +" related to the campaign. When clicked, Odoo reveals a separate, more " +"detailed page with even more in-depth statistics." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:367 +msgid "" +"The option to instantly a new communication from this pop-up window is " +"available in the upper-left corner. The adjustable status bar is located in " +"the upper-right." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:370 +msgid "" +"When all modifications are ready to be finalized, click :guilabel:`Save`. To" +" delete the entire campaign, click :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:374 +msgid "Create new mailing campaign (from Campaigns page)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:376 +msgid "" +"When the :guilabel:`Mailing Campaigns` feature is activated, a new " +":guilabel:`Campaigns` option appears in the header of the *Email Marketing* " +"application. Campaigns can also be created on this :guilabel:`Campaigns` " +"page in the *Email Marketing* app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:380 +msgid "" +"To do that, navigate to :menuselection:`Email Marketing app --> Campaigns " +"--> Create`. When that's clicked, a pop-up window appears, in which the " +":guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can" +" be added directly on the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst-1 +msgid "View of the campaign pop-up window in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:388 +msgid "" +"Click :guilabel:`Add` to add the campaign to the database, and freely edit " +"it later on. Or, click :guilabel:`Edit` and Odoo reveals the campaign " +"template form on a separate page, providing the opportunity to further edit " +"the campaign, send communications related to the campaign, and analyze " +"various metrics related to the campaign, via the smart buttons at the top of" +" the form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:394 +msgid "A/B testing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:396 +msgid "" +"Back in the :guilabel:`Settings` tab of the mailing, if the :guilabel:`Allow" +" A/B Testing` box is checked, recipients are only be mailed to once. This " +"allows different mailings to be sent to randomly selected recipients. This " +"tests the overall effectiveness of the mailing, and eliminates the need for " +"duplicate messages." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:401 +msgid "" +"The :guilabel:`A/B Testing percentage` field represents the percentage of " +"contacts in the database that this message will be mailed to, as a part of " +"the :guilabel:`A/B Testing`. Enter a number between `1-100`. The recipients " +"are randomly chosen." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:406 +msgid "Send, schedule, or test" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:408 +msgid "" +"After finalizing the mailing, Odoo provides the following options in the " +"upper-left corner of the email template page. Those options are: " +":guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:412 +msgid "" +"While in :guilabel:`Edit` mode, there are also buttons to :guilabel:`Save` " +"or :guilabel:`Discard` the mailing, as well." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:415 +msgid "" +":guilabel:`Send` - Click to have Odoo send the email to the desired " +"recipients. When Odoo has sent the mailing, the status changes to *Sent*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:417 +msgid "" +":guilabel:`Schedule` - Click to reveal a pop-up window, in which a future " +"date-time is chosen. Odoo sends the mailing to the desired recipients at " +"that specified date-time. When a date-time is chosen, the status of the " +"mailing changes to *In Queue*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:420 +msgid "" +":guilabel:`Test` - Click to reveal a pop-up window, in which Odoo allows a " +"sample email to be sent for testing purposes. Enter the desired recipient's " +"email address in the :guilabel:`Recipients` field, and click :guilabel:`Send" +" Sample Mail`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:423 +msgid "" +":guilabel:`Save` - Click to save the mailing as a draft, which can be edited" +" (and sent) at a later date. When clicked, the status of the mailing stays " +"as :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:425 +msgid "" +":guilabel:`Discard` - Click to discard any changes that have been made since" +" the last save." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:428 +msgid "" +"When :guilabel:`Save` or :guilabel:`Discard` is selected (while in " +":guilabel:`Edit` mode), those options are replaced with an :guilabel:`Edit` " +"button and a :guilabel:`Create` button. Click :guilabel:`Edit` to re-enter " +":guilabel:`Edit` mode. Click :guilabel:`Create` to start creating a new " +"mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:434 +msgid "" +"By default, there's a daily limit applied for **all emails** sent throughout" +" *all* applications. So, if there are remaining emails to be sent after a " +"limit has been reached, those mailings *will not* be sent automatically the " +"next day. The sending needs to be forced, by opening the email and clicking " +":guilabel:`Retry`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3 +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:15 +msgid "Mailing lists" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:5 +msgid "" +"Mailing lists are important for a number of reasons. Mailing lists can " +"provide valuable leads for sales teams, communicate with focus groups " +"participants, contact consumers directly for useful feedback, and more." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:10 +msgid "Create mailing lists" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:12 +msgid "" +"To create a mailing list in the *Email Marketing* application, navigate to " +":menuselection:`Mailing lists --> Mailing lists --> Create`. Clicking " +":guilabel:`Create` reveals a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the mailing list pop-up in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:19 +msgid "" +"In the pop-up, name the mailing list and designate if the mailing list " +"should be public with the :guilabel:`Is Public` checkbox." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:22 +msgid "" +"The :guilabel:`Is Public` option allows the mailing list to be accessible by" +" recipients in the unsubscription page, making it possible for them to " +"update their subscription preferences." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:25 +msgid "" +"After those options have been configured, click :guilabel:`Create` to create" +" the mailing list, which Odoo automatically adds to the :guilabel:`Mailing " +"Lists` page." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:29 +msgid "Add contacts to a mailing list" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:31 +msgid "" +"After a mailing list has been created (and added to the :guilabel:`Mailing " +"Lists` dashboard), click on the desired mailing list to add contacts to the " +"list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:34 +msgid "" +"Clicking the desired mailing list reveals a separate :guilabel:`Mailing List" +" Contacts` page, in which contacts can be added to this specific list by " +"clicking :guilabel:`Create`, and adding contact information directly on a " +"separate contact detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:38 +msgid "" +"Or, while in the :menuselection:`Email Marketing` application, navigate to " +":menuselection:`Mailing Lists --> Mailing List Contacts`. Doing so reveals a" +" separate page with all the mailing list contacts in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:42 +msgid "" +"From here, click :guilabel:`Create`, and add a contact with the same " +"previous steps. Or, click the :guilabel:`Import` icon (to the right of the " +":guilabel:`Create` button) to import contacts into the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:46 +msgid "" +"Once contacts are in the database, click into the desired contact's detail " +"form, and add the preferred mailing list in the :guilabel:`Mailing List` tab" +" (at the bottom of the contact detail form), by clicking :guilabel:`Add a " +"line`, and selecting the desired mailing list. Multiple mailing lists can be" +" added to a single contact's detail form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of a contact detail form with mailing list tab in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:56 +msgid "Create new mailing list from contact detail form" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:58 +msgid "" +"To create a mailing list from a contact detail form, click :guilabel:`Add a " +"line`, and type in the name of a new mailing list in the empty field that " +"appears. Then, select either :guilabel:`Create` or :guilabel:`Create and " +"Edit...`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the new mailing list drop-down on contact form in Odoo Email " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:66 +msgid "" +"The :guilabel:`Create` option quickly creates the mailing list to the " +"contact detail form, and the list can be configured at a later date. The " +":guilabel:`Create and Edit...` option creates the mailing list, and reveals " +"a pop-up window, in which the new mailing list can be configured right away." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "" +"View of the create and edit mailing list pop-up in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:76 +msgid "Link a mailing list to website (Newsletter blocks)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:78 +msgid "" +"When a mailing list is created in the database, Odoo provides the option to " +"directly link the mailing list on the Odoo-built website (created via Odoo's" +" :guilabel:`Website` application)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:81 +msgid "" +"To link a mailing list to a website, navigate to the front-end of the " +"website, and enter :guilabel:`Edit` mode by clicking :guilabel:`Edit` in the" +" upper-right corner. When clicked, Odoo reveals a right-sidebar, filled with" +" drag-and-drop *Building Blocks* that are packed with various features, " +"options, and design elements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:86 +msgid "" +"Then, to add a *subscription field* for a specific mailing list onto a " +"website, drag-and-drop any of the :guilabel:`Newsletter` options " +"(:guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup`, or " +":guilabel:`Newsletter`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:91 +msgid "" +"To quickly locate the :guilabel:`Newsletter` building block options (while " +"in :guilabel:`Edit` mode on the front-end of the website), type `Newsletter`" +" into the search bar, located in the right sidebar, under the " +":guilabel:`Blocks` tab, and Odoo reveals the three different " +":guilabel:`Newsletter` block options." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "" +"View of how to quickly search for Newsletter blocks in the Odoo Website " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:100 +msgid "" +"When a :guilabel:`Newsletter` block is dragged onto the body of the website," +" Odoo reveals a pop-up window, in which the desired mailing list is selected" +" from a drop-down menu (and linked) to this block on the website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1 +msgid "View of the add mailing list subscription pop-up on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:108 +msgid "" +":guilabel:`Newsletter Block` - Adds a block onto the webpage, providing " +"visitors with the option to add their email address to this mailing list, " +"and subscribe to future communications." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:111 +msgid "Here's an example of a :guilabel:`Newsletter Block`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a sample newsletter block in the Odoo Website application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:116 +msgid "" +":guilabel:`Newsletter Popup` - Tells Odoo to reveal a subscription pop-up " +"window to occur at a certain part of the webpage. When the visitor scrolls " +"to this predetermined point, a pop-up subscription window appears, asking " +"for their email address to subscribe to the mailing list. The pop-up window " +"can be edited further to fit any business needs." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:121 +msgid "Here's an example of a :guilabel:`Newsletter Popup`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a sample newsletter pop-up sample on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:126 +msgid "" +":guilabel:`Newsletter` - Provides visitors with a simple field to add their " +"email address to the mailing list, and subscribe to future mailings in the " +"footer (or anywhere else on the page)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:129 +msgid "Here's an example of a :guilabel:`Newsletter` dynamic block." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 +msgid "View of a Newsletter dynamic block on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:135 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:73 +msgid ":doc:`/applications/marketing/email_marketing`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:3 +msgid "Manage unsubscriptions (Blacklist)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:5 +msgid "" +"Providing recipients with the power to unsubscribe from mailing lists is not" +" only a smart business practice, it's often a legal requirement. By allowing" +" recipients to unsubscribe from a mailing list establishes a sense of trust " +"with an audience, and helps companies appear genuine (and not spammy)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:10 +msgid "Enable the Blacklist feature" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:12 +msgid "" +"First, the *Blacklist* feature must be enabled. To do that, navigate to " +":menuselection:`Email Marketing app --> Configuration --> Settings`, enable " +"to :guilabel:`Blacklist Options when Unsubscribing`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "" +"View of the blacklist feature in the Settings page of the Odoo Email " +"Marketing app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20 +msgid "" +"With that feature activated, an *Unsubscribe* link appears in mailings. If a" +" recipient clicks that link, Odoo reveals a :guilabel:`Unsubscriptions` " +"page, where they can directly manage their subscriptions." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:25 +msgid "" +"With a test mailing, clicking the :guilabel:`Unsubscribe` link reveals an " +"error page (*error 403 - Access Denied*). To make sure the link is working " +"properly, create the mailing, and only send it to a personal email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:30 +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102 +msgid "Blacklist" +msgstr "บัญชีดำ" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:32 +msgid "" +"In addition to having the option to *Unsubscribe* from specific mailing " +"lists, the recipient can also *Blacklist* themselves, meaning they will not " +"receive *any* more emails." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:36 +msgid "" +"The mailing list has to be configured as *Public* in order to be visible for" +" users." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:38 +msgid "" +"To view a complete collection of blacklisted email addresses, navigate to " +":menuselection:`Email Marketing app --> Configuration --> Blacklisted Email " +"Addresses`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "View of the blacklisted email addresses page in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:45 +msgid "" +"When a blacklisted record is selected from this page, Odoo reveals a " +"separate page with that blacklisted recipient's contact information." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "View of a blacklisted contact detail form in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:52 +msgid "" +"In the :guilabel:`Chatter` of this page, there's a time-stamped message, " +"informing the user when that recipient blacklisted themselves (via a " +":guilabel:`Mail Blacklist created` log note)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56 +msgid "Unblacklist contacts" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:58 +msgid "" +"To *Unblacklist* contacts, click the :guilabel:`Unblacklist` button in the " +"upper-left corner to remove the contact from the blacklist, allowing them to" +" receive mailings once again." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61 +msgid "" +"When :guilabel:`Unblacklist` is clicked, a pop-up appears. In this pop-up, " +"the specific email address is listed, and there's a :guilabel:`Reason` " +"field, in which a reason can be entered, explaining why this particular " +"contact was removed from the blacklist." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1 +msgid "" +"View of the unblacklist pop-up window in the Odoo Email Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:69 +msgid "" +"After filling in the fields, click :guilabel:`Confirm` to officially remove " +"that particular contact from the blacklist." +msgstr "" + +#: ../../content/applications/marketing/events.rst:5 +msgid "Events" +msgstr "อีเวนต์" + +#: ../../content/applications/marketing/events.rst:8 +msgid "`Odoo Tutorials: Events <https://www.odoo.com/slides/surveys-63>`_" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:3 +msgid "Event essentials" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:5 +msgid "" +"Odoo Events provides event coordinators with an arsenal of planning, " +"communications, and reporting tools to create immersive and engaging " +"experiences for customers. Namely, staff can create and publish events on " +"their website, sell tickets online, scan tickets with Odoo barcode, send out" +" automated emails, and generate rich reporting data once the event accepts " +"registrations." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:11 +msgid "Kanban concepts and organization" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:13 +msgid "" +"To get started, click on the :guilabel:`Events` application on the home " +"dashboard, which then leads to the kanban view populated with a variety of " +"pipeline stages. Key information is listed on each event card, such as the " +"date/time of the event, along with the number of expected (and confirmed) " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:18 +msgid "" +"To create a new stage, click :guilabel:`Add a Column` and provide a " +"befitting title to reflect the purpose of that stage." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:21 +msgid "" +"To reorganize the stages, just drag-and-drop them until they are in the " +"correct order. Stages can also be “folded” in the kanban for a cleaner " +"presentation, via the :guilabel:`Settings` menu to the right of each stage's" +" title, which is represented by a gear icon." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:26 +msgid "" +"The gear icon, by default, is hidden and will appear next to the " +":guilabel:`+` icon when moused over." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:29 +msgid "When clicked, a drop-down menu of settings will appear." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "Overview of events setting with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:36 +msgid "Create a new event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:38 +msgid "" +"To create an event, click :guilabel:`Create` from the Events dashboard. Odoo" +" will then direct the page to a blank event template form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:41 +msgid "" +"From the event form, fill out the necessary fields, either by choosing from " +"existing data in the Odoo database or by creating and editing new field " +"data. Key information to enter for the event includes:" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:45 +msgid ":guilabel:`Event Name`: give the event a title." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:46 +msgid "" +":guilabel:`Date`: includes the start and end dates/times for the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:47 +msgid "" +":guilabel:`Timezone`: covers the timezone for when the event is taking " +"place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:48 +msgid "" +":guilabel:`Template`: choose from a pre-built event template or build a " +"custom one and connect it here." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:50 +msgid "" +":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. " +"`tradeshow`). Tags help better organize event cards in the kanban and are " +"useful when using search filters during reporting periods." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:53 +msgid "" +":guilabel:`Organizer`: detail the organizer(s) for the event. This field is " +"usually the company that owns the Odoo database, or a vendor." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:55 +msgid "" +":guilabel:`Responsible`: name the point person who is responsible for " +"organizing the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:56 +msgid "" +":guilabel:`Website`: indicate which Odoo website(s) the event event should " +"be published to." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:57 +msgid "" +":guilabel:`Venue`: list the venue details here if it's a new record, or " +"choose from an existing location." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:59 +msgid "" +":guilabel:`Limit Registrations`: when enabled, this setting caps the " +"attendee registrations to a specified amount" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:61 +msgid "" +":guilabel:`Autoconfirmation`: when enabled, this setting skips the " +"confirmation request that gets sent by email to event registrants, and " +"automatically confirms their registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:64 +msgid "" +"Once the fields in the event form are set, move on to the " +":guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the " +":guilabel:`Questions` tab if registrations should require additional " +"information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:69 +msgid "Add and sell event tickets" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:71 +msgid "" +"Under the :guilabel:`Tickets` tab, add line items for each type of ticket " +"the event plans to offer. Here, determine the ticket price, start/end dates " +"for registrations, as well as the maximum number of tickets that can be " +"sold." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:75 +msgid "" +"If selling tickets isn't necessary for the event, a simple " +":guilabel:`Registration` button will be displayed on the event's page by " +"default." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the ticket tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:83 +msgid "Send automated emails, text, and social posts to event attendees" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:85 +msgid "" +"Under the :guilabel:`Communication` tab, configure personalized email, SMS, " +"or social post messages to keep in touch with event attendees. For each " +"communication, click :guilabel:`Add a line` in the :guilabel:`Communication`" +" tab form, and then choose (or create) a communications template using the " +"drop-down menu under the :guilabel:`Template` column." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:90 +msgid "" +"Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how " +"often the communication should be sent; use these time fields to specify the" +" frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " +":guilabel:`Months` communications should be sent. There is also the option " +"to send communications `Immediately` after a specified :guilabel:`Trigger` " +"is activated." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:96 +msgid "" +"In the last column, determine the :guilabel:`Trigger` which controls how and" +" when the communication is sent. For this action, choose between: " +":guilabel:`Before the event`, :guilabel:`After each registration`, or " +":guilabel:`After the event`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the communication tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:105 +msgid "Attach a questionnaire to event registrations" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:107 +msgid "" +"Implementing a questionnaire during event sign up is an effective way to " +"gauge the wants, needs, and interests of the event's attendees ahead of " +"time. Questionnaires also act as informative analytics tools for reporting " +"periods before (or after) events take place." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:111 +msgid "" +"To create a questionnaire, from the :guilabel:`Events` application, navigate" +" to :menuselection:`Configuration --> Settings` and then enable the " +":guilabel:`Questions` setting." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:114 +msgid "" +"With the setting enabled, questions and answers can now be added (and " +"recorded) under the the :guilabel:`Questions` tab back on the event form. " +"For each question, specify if it should only be asked once with the " +":guilabel:`Ask once per order` checkbox, or if the question requires a " +":guilabel:`Mandatory Answer`, which will make the question required for " +"registration." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:120 +msgid "" +"If the :guilabel:`Once per order` checkbox is enabled, then a single " +"registration for 3 event attendees will show the questionnaire only once." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:123 +msgid "" +"There are two :guilabel:`Question Types` to choose from: " +":guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` " +"type, allows attendees to select an answer from pre-configured options, " +"which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text " +"Input` type allows attendees to write in their own answer to the question in" +" a text box." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of an event form, open the questions tab, and add a question." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:133 +msgid "Log internal notes or add ticket instructions" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:135 +msgid "" +"In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` " +"and/or :guilabel:`Ticket instructions`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:138 +msgid "" +"Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, " +"contact information, etc.) for event staff to reference. In the " +":guilabel:`Ticket instructions` field, helpful information for staff and " +"attendees can be shared (like, directions to the venue, opening/closing " +"times, etc.)" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:144 +msgid "" +"Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket " +"instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These " +"options provide various formatting options to ensure vital internal " +"information is organized for event staff to review." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "View of the Notes tab in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:153 +msgid "Invite attendees to the event" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:155 +msgid "" +"To invite people to an event, click the :guilabel:`Invite` button located in" +" the top left corner of the event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:158 +msgid "" +"Inside the invite template form, are options to sent email or SMS invites. " +"Each message can be fully customized, and recipients can be added." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:161 +msgid "" +"Adding a :guilabel:`Subject` line for the invite message is required, but " +"the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text`" +" is a catchy preview sentence meant to encourage recipients to open the " +"email." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:166 +msgid "" +"In most cases, the :guilabel:`Preview Text` is displayed next to the " +"subject. Keep this field empty to ensure the first characters of the email " +"content appear, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:170 +msgid "Select invitees and configure recipient filters" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:172 +msgid "" +"In the middle of the invitation form, find and click the " +":guilabel:`Recipients` field, to reveal a drop-down menu of recipient " +"options. These choices represent where Odoo will find the desired " +"recipients' information." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:176 +msgid "" +"Once an option from this menu is selected (e.g. :guilabel:`Applicant`, " +":guilabel:`Contact`, :guilabel:`Event Registration`, " +":guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all " +"recipients who match that initial rule. Additional rules can be added to " +"narrow down the target recipients, by clicking :guilabel:`Add Filter`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the add filter button beneath the recipients field in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:185 +msgid "" +"Clicking :guilabel:`Add Filter` reveals three fields, formatted like an " +"equation. To reveal the sub-menu options, click each field, and make the " +"desired selections, until the preferred configuration has been acheived. The" +" number of :guilabel:`Records` that match the rule(s) are indicated to the " +"right of the :guilabel:`Recipients` field, in green." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:194 +msgid "" +"To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and " +":guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line)" +" of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, " +"the :guilabel:`...` icon adds a branch to the node. A branch means two " +"additional, indented sub-nodes are added to the rule, providing even more " +"specificity to the line above it." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:201 +msgid "Build a custom event invite" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:203 +msgid "" +"In the :guilabel:`Mail Body` tab, there are a number of pre-configured " +"message templates to choose from. Select the desired template, and modify " +"every element of its design details with Odoo's drag-and-drop web builder, " +"located on the right sidebar." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of the drag and drop building blocks used to customize event invite " +"emails." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:212 +msgid "" +"To build an email event invite from scratch, select the :guilabel:`Plain " +"Text` template, and Odoo will provide a blank email canvas, which can be " +"customized either by using the frontend rich text editor that accepts slash " +"(`/`) commands, or the XML code editor when :ref:`developer mode <developer-" +"mode>` is engaged and the :guilabel:`</>` icon is pressed." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:218 +msgid "" +"The :guilabel:`Mail Body` tab (and template options), are only available if " +"the event invite :guilabel:`Mailing Type` is designated as an " +":guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a " +":guilabel:`SMS Content` tab (consisting of a blank text space), is " +"available, instead." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:224 +msgid "Modify event invite settings" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:226 +msgid "" +"The options under the :guilabel:`Settings` tab are different, depending on " +"the specified :guilabel:`Mailing Type`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:229 +msgid "" +"If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`," +" an employee can be designated as the :guilabel:`Responsible`, meaning that " +"person is the one responsible for this particular invite message. " +":guilabel:`Send From` and :guilabel:`Reply To` email aliases can be " +"designated here, as well." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:234 +msgid "" +"Also, if any specific documents are required (or helpful) for this event " +"invite, they can be sent along with this email, by clicking " +":guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:238 +msgid "" +"If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a" +" :guilabel:`Responsible` can be designated, and the option to " +":guilabel:`Include an opt-out link` is available." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:242 +msgid "Send event invitations to recipients" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:244 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are " +"three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, " +"and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:247 +msgid "" +"The :guilabel:`Send` option sends the invite right away. The " +":guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time" +" can be selected for the email to be sent. The :guilabel:`Test` option " +"reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email " +"addresses can be entered for Odoo to send them the current version of the " +"mailing for review before officially sending it out to prospective event " +"attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:253 +msgid "" +"If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four " +"options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, " +":guilabel:`Schedule`, and :guilabel:`Test`." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:256 +msgid "" +"The :guilabel:`Put in Queue` option schedules an SMS message to all " +"recipients (that match the designated rules, if any) in the near future. " +"Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. " +"When confirmed, a blue banner appears on the event invite template form, " +"indicating that the SMS will be sent later that day." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:262 +msgid "" +"The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options" +" all function the same way for both :guilabel:`Mailing Type` options." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:266 +msgid "Publish events" +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:268 +msgid "" +"Until an event is published, it will remain hidden from public view on the " +"website and registering for it will not be possible. To publish an event, " +"navigate to it either from the backend of Odoo through the " +":guilabel:`Events` application, or access the hidden event page through the " +"frontend as either a priveliged user or administrator." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:273 +msgid "" +"If navigating from the backend, go to the event form, and click the " +":guilabel:`Go to Website` smart button to reach the event page on the " +"website (on the frontend). If starting from the frontend , simply navigate " +"to the event page that needs to be published." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst:277 +msgid "" +"No matter the route, an event page can only be published from the frontend. " +"In the upper right corner of the event page on the website, toggle the " +"switch from the red :guilabel:`Unpublished` status to the green " +":guilabel:`Published` status. Doing so instantly makes the event page " +"accessible to the public on the website." +msgstr "" + +#: ../../content/applications/marketing/events/event_essentials.rst-1 +msgid "" +"View of a website page and the option to publish the event in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:3 +msgid "Sell tickets" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:5 +msgid "" +"Create custom ticket tiers (with various price points) for potential " +"attendees to choose from, directly on the event template form, under the " +":guilabel:`Tickets` tab. Odoo simplifies the ticket-purchasing process by " +"providing plenty of payment method options." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:10 +#: ../../content/applications/marketing/events/track_manage_talks.rst:9 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/marketing/events/sell_tickets.rst:12 +msgid "" +"First, in order to enable the creation (and selling of) event tickets, go to" +" :menuselection:`Configuration --> Settings`, then enable the " +":guilabel:`Tickets` and :guilabel:`Online Ticketing` features." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:16 +msgid "" +"The :guilabel:`Tickets` feature allows tickets to be sold for an event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:18 +msgid "" +"The :guilabel:`Online Tickets` feature allows for the sale of tickets to " +"occur through the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:21 +msgid "" +"If these options are *not* enabled, a default :guilabel:`Register` button " +"will be available for free registrations." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of the settings page for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:29 +msgid "Sell tickets through sales orders" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:31 +msgid "" +"In the :guilabel:`Sales` application, choose a previously-created Event " +"Registration (as if it were a product), and add it as a product line. Upon " +"adding the registration, a pop-up appears, which allows for the selection of" +" a specific event (and ticket tier). That specific event ticket is then " +"attached to the sales order." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of a sales order and option to choose the specific event in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:40 +msgid "" +"Events with tickets sold online or through sales orders have a " +":guilabel:`Sales Smart Button` shortcut, located at the top of the event " +"template form (in the :guilabel:`Events` application)." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:43 +msgid "" +"Clicking the :guilabel:`Sales Smart Button` reveals a page with all the " +"sales orders related to that event." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of an event's form and the sales smart button in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "" +"View of an event form highlighting the column product under the tickets tab in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:56 +msgid "Sell tickets through the website" +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:58 +msgid "" +"With tickets purchased through the website, the process is similar to " +"creating a :guilabel:`Sales Order` with a specific :guilabel:`Registration` " +"product. Here, tickets are added to a virtual cart, and the transaction can " +"be completed as usual - utilizing any of the pre-configured payment methods " +"options that have been set up on the website." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst:63 +msgid "" +"The completed purchase is automatically produced in a :guilabel:`Sales " +"Order`, which can be easily accessed in the back end of the database." +msgstr "" + +#: ../../content/applications/marketing/events/sell_tickets.rst-1 +msgid "View of website transaction for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +msgid "Track and manage talks" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:5 +msgid "" +"With Odoo Events, it's possible to provide attendees with the power to " +"propose presenters to speak at events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:11 +msgid "" +"First, go to :menuselection:`Events --> Configuration --> Settings` and " +"enable :guilabel:`Schedule & Tracks`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:14 +msgid "" +"When that feature is enabled, two more options become available: *Live " +"Broadcast* and *Event Gamification*." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:17 +msgid "" +":guilabel:`Live Broadcast` allows for the airing of tracks online through a " +"YouTube integration." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:19 +msgid "" +":guilabel:`Event Gamification` allows for the sharing of a quiz with your " +"attendees, once a track (talk) is over." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:23 +msgid "" +":guilabel:`Event Gamification` isn't necessary for tracks to appear on the " +"event page on the website, but it can enhance the engagement and overall " +"enjoyablity of the event for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:27 +msgid "Talks, talk proposals, and agenda" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:29 +msgid "" +"Once those two features are enabled, the following links are automatically " +"added to the sub-header menu, located on the event page on the website: " +":guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any " +"attendee can freely access these menu items and their corresponding content." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:33 +msgid "" +"The :guilabel:`Talks` link takes the attendee to a page full of all the " +"talks for that event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:35 +msgid "" +"The :guilabel:`Talks Proposals` link takes the attendee to a form page, " +"where they can propose talks for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:38 +msgid "" +"The :guilabel:`Agenda` link takes the attendee to a page with all the talks " +"for the event, but in a calendar/time-slot format." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the published website and the talks, talk proposals, and agenda in " +"Odoo Events" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:46 +msgid "Manage talk proposals" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:48 +msgid "" +"When attendees fill out and submit a talk proposal form on the website, a " +"new :guilabel:`Proposal` is instantly created in the back end for the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:52 +msgid "" +"All talks (Proposals, Confirmed, Announced, etc.) are accessible via the " +":guilabel:`Tracks` smart button on the event form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of the talks' proposals page emphasizing the column proposal in Odoo " +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:59 +msgid "" +"If a proposal is accepted, move the :guilabel:`Event Track` to the " +"appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to " +"that particular event's template form, and click the :guilabel:`Go to " +"Website` smart button to reach that specific talk's page on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:63 +msgid "" +"In the upper right corner, toggle the switch from :guilabel:`Unpublished` to" +" :guilabel:`Published`, and the talk is instantly accessible on the website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:67 +msgid "Without publishing a talk, attendees will never be able to access it." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "View of the website page to publish a proposed talk for Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:74 +msgid "Attendees list and attendance" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:76 +msgid "" +"Once attendees have registered for a specific event, they are added to the " +":guilabel:`Attendee List` for that event, which is accessible via the " +":guilabel:`Attendees` smart button on the event template form, or " +":menuselection:`Reporting --> Attendees` and sorted by event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:81 +msgid "" +"When an attendee arrives at the event, they will be marked as attending " +"(:guilabel:`Confirmed Attendance`), and the status of that attendee will " +"change to :guilabel:`Attended.`" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Overview of events with the kanban view in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:88 +msgid "" +"When analyzing an :guilabel:`Attendees list`, Odoo provides different ways " +"to view the information. Each view option presents the same information, but" +" in a slightly different layout. To change the view, click on the icons in " +"the upper right hand of the screen." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "Various view options on the attendees list page." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:96 +msgid "" +"In the :guilabel:`Kanban` view, it can be confirmed whether the attendees " +"have already paid or remain unpaid." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:99 +msgid "" +"The :guilabel:`List` view provides information in a more traditional list " +"formation." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:101 +msgid "" +"The :guilabel:`Calendar` view provides a clear schedule visualization of " +"which attendees are arriving on specific dates of the event." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:104 +msgid "" +"The :guilabel:`Graph` view provides graphical representations of that " +"event's attendees, along with numerous filters and customizable measures for" +" deeper analysis." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:107 +msgid "" +"The :guilabel:`Cohort` view lays out attendee data to better analyze the " +"number of registration dates." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:111 +msgid "" +"Tickets sold through sales orders validate attendees as soon as the " +"quotation is confirmed." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:114 +msgid "Manage registrations" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:116 +msgid "" +"Upon selecting an attendee, Odoo reveals that specific attendee's detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:118 +msgid "" +"From here, event badges can be sent manually, by selecting :guilabel:`Send " +"By Email`. The :guilabel:`Attendee` can also be marked as " +":guilabel:`Attended`, or the registration can be canceled altogether via the" +" :guilabel:`Cancel Registration` button." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "" +"View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" +"Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:128 +msgid "Lead Generation Rules" +msgstr "กฎการสร้างลูกค้าเป้าหมาย" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:130 +msgid "With Odoo, leads can be generated from events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:132 +msgid "" +"To create and configure a :guilabel:`Lead Generation Rule` related to " +"events, navigate to :menuselection:`Events app --> Configuration --> Lead " +"Generation`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:135 +msgid "" +"On the :guilabel:`Lead Generation Rule` page, every configured " +":guilabel:`Lead Generation Rule` can be found, along with pertinent data " +"related to those rules." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule page looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:142 +msgid "" +"To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, " +"and fill out the :guilabel:`Lead Generation Rule` form." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst-1 +msgid "How the Lead Generation Rule template looks in Odoo Events." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:149 +msgid "" +"After naming the rule, configure *how* the lead should be created (either " +":guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should " +"be created, (when :guilabel:`Attendees are created`, when " +":guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` " +"the event)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:154 +msgid "" +"In the :guilabel:`For any of these Events` section, there are fields to " +"attach this rule to any specific event categories, company, and/or event. To" +" add even more specificity to the rule, a domain filter rule can be " +"configured to ensure the rule only applies to a specific target audience of " +"attendees (found in the :guilabel:`If the Attendees meet these Conditions` " +"section)." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:159 +msgid "" +"Lastly, in the :guilabel:`Lead Default Values` section, designate a " +":guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` " +"(and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:8 +msgid "Marketing Automation" +msgstr "การตลาดอัตโนมัติ" + +#: ../../content/applications/marketing/marketing_automation.rst:11 +#: ../../content/applications/marketing/sms_marketing.rst:11 +#: ../../content/applications/marketing/social_marketing.rst:11 +msgid "" +"`Odoo Tutorials: Marketing <https://www.odoo.com/slides/marketing-27>`_" +msgstr "`Odoo Tutorials: การตลาด <https://www.odoo.com/slides/marketing-27>`_" + +#: ../../content/applications/marketing/marketing_automation/advanced.rst:5 +msgid "Advanced" +msgstr "ระดับสูง" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3 +msgid "Campaign metrics" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5 +msgid "" +"*Campaign metrics* are detailed statistics and analytics within a marketing " +"campaign, measuring its success and effectiveness. Triggered marketing " +"activities populate relevant activity blocks with real-time metrics, in the " +"campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10 +msgid "Activity analytics" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:12 +msgid "" +"In the :guilabel:`Workflow` section of a campaign detail form in the " +"*Marketing Automation* app, where the various campaign activities are " +"located, a collection of useful data can be found on every individual " +"activity block, like number of communications :guilabel:`Sent`, percentage " +"of messages that have been :guilabel:`Clicked`, and more." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"An activity block in the workflow section with useful analytical data in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:21 +msgid "" +"To the left of the activity block, the configured :doc:`trigger time " +"<../getting_started/workflow_activities>` is displayed as a duration (either" +" :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or " +":guilabel:`Months`) if it corresponds to period after the workflow begins." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27 +msgid "" +"If the trigger time is dependent on another activity or triggering action " +"(e.g. :guilabel:`Mail: Replied`, etc.) the time is displayed, along with the" +" necessary action for that activity to be activated (e.g. `Replied after 2 " +"Hours`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "" +"Time trigger display when dependent on another activity in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:35 +msgid "" +"In the activity block, an icon represents each activity type. An " +":guilabel:`✉️ (envelope)` icon means the activity is an email. Three tiny, " +"interlocking :guilabel:`⚙️ (gear)` icons means the activity is an internal " +"action. And, a small, basic :guilabel:`📱 (mobile)` icon means the activity " +"is an SMS." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41 +msgid "" +"The activity type name is also displayed in smaller font below the activity " +"title." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:43 +msgid "" +"Beside the activity icon, at the top of the activity block, is the title of " +"the activity. To the right of the activity title, there are :guilabel:`Edit`" +" and :guilabel:`Delete` buttons." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:46 +msgid "" +"Click :guilabel:`Edit` to open the :guilabel:`Open: Activities` pop-up form " +"for that specific activity, in which that activity can be modified. Click " +"the :guilabel:`Delete` button to completely delete that specific activity " +"from the workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:51 +msgid "" +":doc:`/applications/marketing/marketing_automation/getting_started/workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54 +msgid "Activity graph tab" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:56 +msgid "" +"In every activity block, the :guilabel:`Graph (pie chart icon)` tab is open " +"by default, displaying related metrics as a simple line graph. The success " +"metrics are represented in `green` and the rejected metrics are represented " +"in `red`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:60 +msgid "" +"Numerical representations of both :guilabel:`Success` and " +":guilabel:`Rejected` activities are shown to the right of the line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64 +msgid "" +"Hovering over any point in the line graph of the activity block reveals a " +"notated breakdown of data for that specific date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "" +"Hovering over any point in line graph reveals notated breakdown of data in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71 +msgid "" +"Beneath the graph in the activity block, for *Email* or *SMS* activity " +"types, a line of accessible data figures provide a bird's eye view of the " +"campaign activity, including: :guilabel:`Sent` (numerical), " +":guilabel:`Clicked` (percentage), :guilabel:`Replied` (percentage), and " +":guilabel:`Bounced` (percentage)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:77 +msgid "" +"Clicking any of those stats on the :guilabel:`DETAILS` line, beneath the " +"line graph, reveals a separate page containing every specific record for " +"that particular data point." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:81 +msgid "Activity filter tab" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:83 +msgid "" +"Next to the :guilabel:`Graph` tab on the activity block, there's the option " +"to open a :guilabel:`Filter` tab (represented by a :guilabel:`filter/funnel`" +" icon)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "" +"What a campaign activity filter tab looks like in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:90 +msgid "" +"Clicking the :guilabel:`Filter` tab on an activity block, reveals what the " +"specific filters are for that particular campaign activity, and how many " +"records in the database match that specific criteria." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:95 +msgid "" +"Clicking the :guilabel:`records` link beneath the displayed filter reveals a" +" separate pop-up window containing a list of all the records that match that" +" specific campaign activity rule(s)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:99 +msgid "Link tracker" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:101 +msgid "" +"Odoo tracks all URLs used in marketing campaigns. To access and analyze " +"those URLs, navigate to :menuselection:`Marketing Automation app --> " +"Reporting --> Link Tracker`. Doing so reveals a :guilabel:`Link Statistics` " +"page, wherein all campaign-related URLs can be analyzed." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:109 +msgid "" +"The default view on the :guilabel:`Link Statistics` page is the " +":guilabel:`Bar Chart` view, but there are different view options available " +"in the upper-left corner. There is the option to view the statistics as a " +":guilabel:`Line Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:113 +msgid "" +"Beside that, there is also the option to view the statistics as " +":guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or " +":guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:116 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Number of " +"Clicks` or total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:121 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:153 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:180 +msgid "" +"Also, in the upper-right corner of the :guilabel:`Link Statistics` page, to " +"the far-right of the search bar, there are additional view options to choose" +" from: the default :guilabel:`Graph` view, the :guilabel:`Pivot` table view," +" and the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:126 +msgid "Traces" +msgstr "ติดตาม" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:128 +msgid "" +"Odoo tracks all activities used in every marketing campaign. The data " +"related to these activities can be accessed and analyzed in the " +":guilabel:`Traces` page, which can be found by navigating to " +":menuselection:`Marketing Automation app --> Reporting --> Traces`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "The Traces page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:136 +msgid "" +"The default view on the :guilabel:`Traces` page is the :guilabel:`Bar Chart`" +" view, but there are different view options available in the upper-left " +"corner. There is the option to view the statistics as a :guilabel:`Line " +"Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:140 +msgid "" +"At the top of the graph, there's a color key, informing the user which " +"activities have been :guilabel:`Processed`, :guilabel:`Scheduled`, and " +":guilabel:`Rejected`. There's also an outline indicator to inform users of " +"the :guilabel:`Sum` of certain activities, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:144 +msgid "" +"Beside the various view option in the upper-left corner of the " +":guilabel:`Traces` page, there is also the option to view the statistics as " +":guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or " +":guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:148 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Document ID` or " +"total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:158 +msgid "Participants" +msgstr "ผู้มีส่วนร่วม" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:160 +msgid "" +"Odoo tracks all participants related to every marketing campaign. The data " +"related to these participants can be accessed and analyzed in the " +":guilabel:`Participants` page, which can be found by navigating to " +":menuselection:`Marketing Automation app --> Reporting --> Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst-1 +msgid "The Participants page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:168 +msgid "" +"The default view on the :guilabel:`Participants` page is the :guilabel:`Pie " +"Chart` view, but there are different view options available in the upper-" +"left corner. There is the option to view the statistics as a :guilabel:`Line" +" Chart` or :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:172 +msgid "" +"At the top of the graph, there's a color key that describes the type of " +"participants found in the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:175 +msgid "" +"To the far-left of the view options, there is the :guilabel:`Measures` drop-" +"down menu. When clicked, the options to view the :guilabel:`Record ID` or " +"total :guilabel:`Count` are available. And, to the right of the " +":guilabel:`Measures` drop-down menu, there's the ability to add any data to " +"a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started.rst:5 +msgid "Getting Started" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3 +msgid "Marketing automation campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5 +msgid "" +"The Odoo *Marketing Automation* app automates a variety of marketing tasks " +"by combining specific rules and filters to generate timed actions. Instead " +"of manually having to build each stage of a campaign (like a series of timed" +" massmails), the *Marketing Automation* app allows marketers to build the " +"entire campaign, and all of its stages, in one place---on one dashboard." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11 +msgid "Campaign configuration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13 +msgid "" +"To create a new automated marketing campaign, navigate to " +":menuselection:`Marketing Automation app --> New` to reveal a blank campaign" +" form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"A blank marketing automation campaign form in Odoo Marketing Automation " +"application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:20 +msgid "" +"After entering a name for the marketing campaign, configure the target " +"audience in the remaining fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23 +msgid "" +"A target audience can be configured by entering specific criteria for Odoo " +"to use when determining to whom this marketing automation campaign should be" +" sent." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26 +msgid "" +"In the :guilabel:`Target` field, use the drop-down menu to choose which " +"model the target audience filters should be based on (e.g. " +":guilabel:`Contact`, :guilabel:`Lead/Opportunity`, :guilabel:`Sales Order`, " +"etc.)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:30 +msgid "" +"Select :guilabel:`Search More...` from the drop-down menu to reveal a " +":guilabel:`Search: Target` pop-up window containing all of the available " +"targeting options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:33 +msgid "" +"Once a :guilabel:`Target` is selected, there's a :guilabel:`Unicity based " +"on` field. This field is used to avoid duplicates based on the model chosen " +"in the :guilabel:`Target` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:37 +msgid "" +"If :guilabel:`Customers` is chosen as the :guilabel:`Target`, select " +":guilabel:`Email` in the :guilabel:`Unicity based on` field so Odoo only " +"processes one record for each customer email address." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:41 +msgid "" +"Select :guilabel:`Search More...` from the :guilabel:`Unicity based on` " +"drop-down menu to reveal all available options in a pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:44 +msgid "" +"Last on the campaign form is the :guilabel:`Filter` field. This is where " +"more specific targeting options can be layered into the campaign to further " +"narrow the number and type of recipients that receive the marketing " +"automation material." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:48 +msgid "" +"If left alone, the :guilabel:`Filter` field reads: :guilabel:`Match all " +"records`. That means Odoo uses the :guilabel:`Target` and :guilabel:`Unicity" +" based on` fields to determine who the recipients will be. The number of " +"recipients is represented beneath as :guilabel:`record(s)`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:53 +msgid "Campaign filter rules" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:55 +msgid "" +"To add a more specific filter to a marketing automation campaign, click the " +":guilabel:`Add condition` button in the :guilabel:`Filter` field. Doing so " +"reveals a series of other configurable filter rule fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59 +msgid "" +"In the rule fields, customizable equations can be configured for Odoo to use" +" when filtering who to include or exclude in this specific marketing " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"How the filter rule equation fields look in Odoo Marketing Automation " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:67 +msgid "" +":guilabel:`Records` refer to contacts in the system that fit the specified " +"criteria for a campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:70 +msgid "" +"Also, once :guilabel:`Add condition` is clicked, the ability to " +":guilabel:`Save as Favorite Filter` becomes available on the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:73 +msgid "" +"There is also the option to match records with :guilabel:`all` or " +":guilabel:`any` of the rules configured in the :guilabel:`Filter` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:76 +msgid "" +"To choose either of those options, click :guilabel:`all` from the middle of " +"the sentence \":guilabel:`Match records with all of the following rules`\" " +"to reveal a drop-down menu with those options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"Match records with all or any of the rules in Filter field for marketing " +"campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:84 +msgid "" +"When the first field of the rule equation is clicked, a nested drop-down " +"menu of options appears on the screen where specific criteria is chosen " +"based on needs of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:87 +msgid "" +"The remaining fields on the rule equation further define the criteria, which" +" is used to determine which records in the database to include or exclude in" +" the execution of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:90 +msgid "" +"To add another rule, either click the :guilabel:`➕ (plus sign)` icon to the " +"right of the filtering rule, or click :guilabel:`New Rule` beneath the rule " +"equation fields. When either are clicked, a new series of rule fields " +"appears." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:94 +msgid "" +"To add a branch of multiple rules at the same time, click the " +":guilabel:`branch` icon, located to the right of the :guilabel:`➕ (plus " +"sign)` icon. When clicked, two additional sub-rule equation fields appear " +"beneath the initial rule." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst-1 +msgid "" +"Sample of how the rule branches look in the filter section of a marketing " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:102 +msgid "" +"There is also the option to have the filter apply to :guilabel:`any` or " +":guilabel:`all` of the configured branch rules." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:105 +msgid "" +"For further information on marketing automation campaign filter " +"configuration, refer to :doc:`this documentation page <target_audience>`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:109 +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:153 +msgid ":doc:`workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:110 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:266 +msgid ":doc:`testing_running`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3 +msgid "Target an audience" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5 +msgid "" +"Delivering marketing campaigns to the right audience is paramount when " +"trying to grow a business. The Odoo *Marketing Automation* application helps" +" marketers to do just that by providing detailed filtering tools, which can " +"be as simple (or as complex) as necessary, to reach the right customers at " +"the right time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11 +msgid "Configure target filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13 +msgid "" +"When configuring the target filters on a marketing campaign, there are some " +"options that have an :guilabel:`> (arrow)` icon beside them. The " +":guilabel:`> (arrow)` icon signifies that the particular filter has more " +"refined parameters within it that can be customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "The drop-down filter menu in the Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:21 +msgid "" +"Filters can be extended by adding *branches* and *nodes*. A *node* adds " +"another filtering parameter to a group of targeting conditions (e.g. a new " +"line), and a *branch* creates a narrowly refined cluster of parameters, " +"allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` " +"statements." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26 +msgid "Every time a new branch is created, there are two options:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:28 +msgid "" +"Either the records can match :guilabel:`ALL` criteria for the upcoming rules" +" (creating an AND statement where *all* criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:30 +msgid "" +"Or, the records can match :guilabel:`ANY` criteria for the upcoming rules " +"(creating an OR statement where *only one* of the criteria must match)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:33 +msgid "" +"To change between these two options, simply click the drop-down arrow icon " +"in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:36 +msgid "" +"To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add " +"another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node" +" or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:45 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:47 +msgid "" +"The following scenarios outline different combinations of filters a " +"marketing campaign might commonly use." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:51 +msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:53 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, search for " +":guilabel:`Lead/Opportunity`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:57 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, " +"click on the default :guilabel:`ID` filter option in the first portion of " +"the filter equation. Doing so reveals a drop-down menu full of filter " +"options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:62 +msgid "" +"Keep the second portion of the filter equation on the default :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:64 +msgid "" +"Next, change the third (and final) portion of the filter equation from " +":guilabel:`Lead` to :guilabel:`Opportunity`. The number of " +":guilabel:`Records` that fit this specific filter equation changes as the " +"equation is customized." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:68 +msgid "" +"Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` " +"icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:71 +msgid "" +"With \"new\" opportunities being the target of this filter, the second node " +"will focus on *only* locating opportunities that are in the :guilabel:`New` " +"stage of the pipeline. To do that, select the default :guilabel:`ID` from " +"the first portion of the second filter equation, and scroll down (or search " +"for) :guilabel:`Stage` from the field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:76 +msgid "" +"Once again, leave the second portion of the filter equation on :guilabel:`🟰 " +"(equal sign)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:78 +msgid "" +"Lastly, highlight the default value in the third (and final) portion of the " +"second filter equation, and type in `New`. With that in place, Odoo only " +"targets opportunities that are in the \"New\" stage of the pipeline." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "" +"A standard scenario using filters in the Odoo Marketing Automation app." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:87 +msgid "" +"Scenario #2: Narrow down target to event attendees who purchased a specific " +"ticket" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:89 +msgid "" +"While in *Edit mode* on a campaign template form (by clicking the " +":guilabel:`Edit` button), select the :guilabel:`Target` field, and click " +":guilabel:`Search More` from the drop-down menu. Then, scroll down (or " +"search for) :guilabel:`Event`, and select it." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:93 +msgid "" +"Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on" +" the default :guilabel:`ID` filter option in the first portion of the filter" +" equation. Doing so reveals a drop-down menu full of filter options. From " +"this drop-down, scroll down (or search for) :guilabel:`Event`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:98 +msgid "" +"Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of " +"the filter equation. This reveals a drop-down menu. From this drop-down " +"menu, select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:101 +msgid "" +"In the third (and final) empty portion of the filter equation, type in the " +"name of the event(s) that Odoo should consider for this campaign filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:104 +msgid "" +"Then, add another node to this filter by clicking the :guilabel:`➕ (plus " +"sign)` icon to the right of the equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:107 +msgid "" +"The second node will focus on targeting this campaign to attendees who " +"purchase a specific type of ticket to the aforementioned event(s) mentioned " +"in the first filter equation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:110 +msgid "" +"To do that, select the default :guilabel:`ID` from the first portion of the " +"second filter equation, and scroll down (or search for) :guilabel:`Event " +"Ticket` from the field drop-down menu. Then, in that same drop-down menu, " +"select :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:114 +msgid "" +"Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second " +"portion of the filter equation, and select :guilabel:`contains`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:117 +msgid "" +"Lastly, in the third (and final) portion of the second filter equation, " +"which is blank, type in the name of the ticket type that should be used for " +"the filter. In this case, :guilabel:`Standard` is the name of the event " +"ticket type for this sample filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst-1 +msgid "An event ticket filter in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3 +msgid "Testing/running campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 +msgid "" +"The Odoo *Marketing Automation* app allows users to test marketing campaigns" +" (and mailings) before officially running them to check for errors and " +"correct any mistakes before it reaches its target audience." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:10 +msgid "Test campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:12 +msgid "" +"To test a marketing campaign, open the :menuselection:`Marketing Automation " +"app`, and select the desired campaign to test, which reveals the campaign's " +"detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 +msgid "" +"On the campaign detail form, make sure the campaign already has activities " +"configured in the workflow (or build a campaign by following the directions " +"on :doc:`this documentation " +"</applications/marketing/marketing_automation/getting_started/workflow_activities>`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:20 +msgid "" +"Testing marketing automation campaigns is meant to be performed in the " +"production version of the database. Duplicate (or trial) databases have " +"limited email sending capabilities." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:23 +msgid "" +"To start a test, click the :guilabel:`Launch a Test` button at the top of " +"the campaign form, to the right of the :guilabel:`Start` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Launch a test button on a campaign detail form in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:30 +msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Launch a test pop-up window that appears in Odoo Markting Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:36 +msgid "" +"In the :guilabel:`Launch a test` pop-up window, click the :guilabel:`Pick or" +" create a/an Contact to generate a Test Participant` field to reveal a drop-" +"down menu of contacts. From this drop-down menu, select an existing contact " +"(or create a new one) to run the test on." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:41 +msgid "" +"Only one contact can be selected from the :guilabel:`Launch a test` pop-up " +"window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:43 +msgid "" +"To create a new contact directly from the :guilabel:`Launch a test` pop-up " +"window, start typing the name of the new contact in the blank field, and " +"click :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Typing in a new contact directly from the launch a test pop-up window in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "" +"Doing so reveals a blank :guilabel:`Create Record` pop-up form, in which the" +" necessary contact information (:guilabel:`Email`, :guilabel:`Mobile`, etc.)" +" *must* be entered, in order for the test to work. When the necessary " +"information is entered, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"A blank contact form from a launch test pop-up window in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:58 +msgid "" +"When all the necessary fields have been entered, click :guilabel:`Save & " +"Close` to return to the :guilabel:`Launch a test` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:61 +msgid "" +"Once a contact is selected, click :guilabel:`Launch` to reveal the campaign " +"test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Test screen in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:67 +msgid "" +"On the campaign test page, the name of the :guilabel:`Record` being tested " +"is visible, along with the precise time this test workflow was started in " +"the :guilabel:`Workflow Started On` field. Beneath that, in the " +":guilabel:`Workflow` section is the first activity (or activities) in the " +"workflow that's being tested." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:72 +msgid "" +"To start a test, click the :guilabel:`Run` button, represented by a " +":guilabel:`▶️ (play button)` icon beside the first activity in the workflow." +" When clicked, the page reloads, and Odoo shows the various results (and " +"analytics) connected to that specific activity as they occur, in real-time." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:77 +msgid "" +"If a child activity is scheduled beneath a parent activity, that child " +"activity will be revealed slightly indented in the workflow, once that " +"parent activity has been run, via the :guilabel:`▶️ (play button)` icon." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "Workflow test progress in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:85 +msgid "" +"Once all the workflow activities are completed, the test ends, and the " +"status bar (in the upper-right corner) moves to the :guilabel:`Completed` " +"stage." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:88 +msgid "" +"To stop a test before all the workflow activities are completed, click the " +":guilabel:`Stop` button in the upper-left corner of the campaign test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:92 +msgid "Run campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:94 +msgid "" +"To run a campaign, navigate to :menuselection:`Marketing Automation app`, " +"and select the desired campaign to run." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:97 +msgid "" +"On the campaign detail form, with all the desired activities ready in the " +":guilabel:`Workflow` section, click :guilabel:`Start` in the upper-left " +"corner to officially run the campaign to the configured target audience " +"specified on the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:101 +msgid "" +"Clicking :guilabel:`Start` launches the campaign, and the status bar of the " +"campaign switches to :guilabel:`Running`, which is located in the upper-" +"right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The status of a marketing campaign changing to running in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:109 +msgid "" +"If some participants are already running on a campaign, and was stopped for " +"any reason, clicking the :guilabel:`Start` button again prompts a pop-up " +"warning. This warning advises the user to click an :guilabel:`Update` button" +" to apply any modifications made to the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The workflow has been modified warning pop-up window of a marketing campaign" +" form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:117 +msgid "" +"Be aware that participants that had already gone through an entire campaign " +"in its original state **can** be reintroduced into the newly-modified " +"campaign, and new traces could be created for them." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:121 +msgid "" +"Then, as the mailings and actions are triggered in the :guilabel:`Workflow`," +" the various stats and data related to each activity appear in each activity" +" block. There is also a series of stat-related smart buttons that appear at " +"the top of the campaign detail form, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:125 +msgid "" +"These analytical smart buttons will *also* populate with real-time data as " +"the campaign progresses: :guilabel:`Templates`, :guilabel:`Clicks`, " +":guilabel:`Tests`, :guilabel:`Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The row of smart buttons that appear in a currently running marketing " +"campaign in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:133 +msgid "Stop campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:135 +msgid "" +"To stop a campaign that's currently running, navigate to the " +":menuselection:`Marketing Automation app`, and select the desired campaign " +"to stop. On the campaign detail form, click the :guilabel:`Stop` button in " +"the upper-left corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"The stop button on a typical campaign detail form in Odoo Marketing " +"Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:143 +msgid "" +"When clicked, the campaign is officially stopped, and the status changes to " +":guilabel:`Stopped` in the upper-right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst-1 +msgid "" +"Marketing campaign's stopped status on a campaign detail form in Odoo " +"Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:151 +msgid ":doc:`first_campaign`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:152 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:188 +msgid ":doc:`target_audience`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 +msgid "Campaign workflow activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 +msgid "" +"When creating a marketing campaign in the *Marketing Automation* app, users " +"can plan marketing activities that can be triggered when certain actions or " +"inactions occur. These can be activities such as, automated emails, SMS, or " +"internal server actions." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10 +msgid "Add workflow activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:12 +msgid "" +"To add workflow activities to a marketing campaign, navigate to the bottom " +"of a pre-existing or new campaign detail form, beneath the target audience " +"configuration fields, and click :guilabel:`Add new activity`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:16 +msgid "" +"Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up " +"window is a blank activity template, where specific parameters can be set " +"for that particular activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A workflow activity template pop-up window in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 +msgid "" +"First, enter a name for the activity in the :guilabel:`Activity Name` field." +" Then, proceed to configure the following options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:26 +msgid "" +"Once ready, either click: :guilabel:`Save & Close` to save the activity and " +"close the pop-up form, :guilabel:`Save & New` to save the activity and " +"instantly create an additional activity on a fresh :guilabel:`Create " +"Activities` pop-up form, or :guilabel:`Discard` to delete the activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:31 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:33 +msgid "" +"Then, select the :guilabel:`Activity Type`. Choose between " +":guilabel:`Email`, :guilabel:`Server Action` (an internal action within the " +"database), or :guilabel:`SMS`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 +msgid "" +"The field below the :guilabel:`Activity Type` changes, depending on the " +"chosen :guilabel:`Activity Type`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 +msgid "Email activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 +msgid "" +"If :guilabel:`Email` is the :guilabel:`Activity Type`, the option to choose " +"a premade/pre-configured :guilabel:`Mail Template` becomes available. A mail" +" template can also be created on-the-fly, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:46 +msgid "" +"To create a new template directly from the :guilabel:`Mail Template` field, " +"start typing the title of the new template into the blank field beside " +":guilabel:`Mail Template`, and select :guilabel:`Create and edit...` to " +"reveal a :guilabel:`Create Marketing Template` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create and edit email drop-down option on create activities pop-up " +"window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:54 +msgid "" +"In that pop-up window, proceed to create and configure the new email " +"template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create marketing template email pop-up window in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 +msgid "Server action activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:63 +msgid "" +"If :guilabel:`Server Action` is the :guilabel:`Activity Type`, the option to" +" choose a specific :guilabel:`Server Action` (e.g. Message for sales person," +" Create Leads on Website clicks, etc.) becomes available." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:67 +msgid "" +"The option to create a new server action directly from the :guilabel:`Server" +" Action` is also available. To do that, type in the name of the new action, " +"then click :guilabel:`Create and Edit...` from the drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create and edit option in the server action field on campaign detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 +msgid "" +"Or, as an alternative, click the empty :guilabel:`Server Action` field to " +"reveal a drop-down menu, and select :guilabel:`Search More...` to reveal a " +":guilabel:`Search: Server Action` pop-up window, containing all the pre-" +"configured server action options to choose from." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79 +msgid "" +"To create a new server action from this pop-up window, and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The new button found on a server action pop-up in Odoo marketing automation " +"application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:85 +msgid "" +"Either option reveals a blank :guilabel:`Create Server Action` pop-up, " +"wherein a custom server action can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "SMS activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:91 +msgid "" +"If :guilabel:`SMS` is the :guilabel:`Activity Type`, the option to choose a " +"premade/pre-configured :guilabel:`SMS Template` becomes available. A SMS " +"template can also be created on-the-fly directly from this field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:95 +msgid "" +"To create a new template directly from the :guilabel:`SMS Template` field, " +"start typing the title of the new template into the blank field beside " +":guilabel:`SMS Template`, and select :guilabel:`Create and edit...` from the" +" drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:103 +msgid "" +"Doing so reveals a :guilabel:`Create Marketing Template` pop-up window. In " +"that pop-up window, proceed to create and configure the new SMS template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The create marketing template pop-up window to create a SMS template on-the-" +"fly." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:111 +msgid "Trigger" +msgstr "เปิดใช้งาน" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:113 +msgid "" +"The :guilabel:`Trigger` field on the :guilabel:`Create Activities` pop-up " +"form allows users to choose when the designated workflow activity should be " +"triggered." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:116 +msgid "" +"Start by selecting a number in the top field. In the next " +":guilabel:`Trigger` field, designate if it should be :guilabel:`Hours`, " +":guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, click the " +"final field, where it reads :guilabel:`beginning of the workflow` be default" +" to reveal a a drop-down menu of other trigger options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A list of the trigger options available on the workflow activities pop-up " +"form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:125 +msgid "The trigger options are as follows:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:127 +msgid "" +":guilabel:`beginning of the workflow`: the activity will be triggered at the" +" previously-configured time after the beginning of the entire workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:129 +msgid "" +":guilabel:`another activity`: the activity will be triggered at the " +"previously-configured time after another specific activity in the workflow." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:131 +msgid "" +":guilabel:`Mail:opened`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been opened by the " +"recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:133 +msgid "" +":guilabel:`Mail:not opened`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"opened by the recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:135 +msgid "" +":guilabel:`Mail: replied`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been replied to by the " +"recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:137 +msgid "" +":guilabel:`Mail: not replied`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"replied to by the recipient." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:139 +msgid "" +":guilabel:`Mail: clicked`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been clicked by the " +"recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:141 +msgid "" +":guilabel:`Mail: not clicked`: the activity will be triggered at the " +"previously-configured time if the sent mail in the workflow has not been " +"clicked by the recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:143 +msgid "" +":guilabel:`Mail: bounced`: the activity will be triggered at the previously-" +"configured time if the sent mail in the workflow has been bounced back for " +"any reason." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:145 +msgid "" +":guilabel:`SMS: clicked`: the activity will be triggered at the previously-" +"configured time if the sent SMS in the workflow has been clicked by the " +"recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:147 +msgid "" +":guilabel:`SMS: not clicked`: the activity will be triggered at the " +"previously-configured time if the sent SMS in the workflow has not been " +"clicked by the recipient, after it's been opened." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:149 +msgid "" +":guilabel:`SMS: bounced`: the activity will be triggered at the previously-" +"configured time if the sent SMS in the workflow has been bounced back for " +"any reason." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:153 +msgid "Expiry duration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:155 +msgid "" +"Next, on the :guilabel:`Create Activities` pop-up form is the " +":guilabel:`Expiry Duration` option." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:157 +msgid "" +"The :guilabel:`Expiry Duration` checkbox provides the option to configure " +"the activity to stop the actions after a specific amount of time (after the " +"scheduled date)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:160 +msgid "" +"When selected, a :guilabel:`Cancel after` field appears, in which the number" +" of :guilabel:`Hours, Days, Weeks, or Months` can be configured for the " +"actions to cease after the initial date." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"A list of the expiry duration options available on the workflow activities " +"pop-up form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:168 +msgid "Activity and applied filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:170 +msgid "" +"Moving down into the :guilabel:`Domain` section of the :guilabel:`Create " +"Activities` pop-up form, there is the :guilabel:`Activity Filter` and " +":guilabel:`Applied Filter` fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:173 +msgid "" +"The :guilabel:`Activity Filter` field provides the option to configure a " +"recipient filter domain that applies to this activity *and* its child " +"activities. In works in the same fashion as a typical target audience " +"filter." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:177 +msgid "" +"To add an activity filter, click :guilabel:`Add condition` in the " +":guilabel:`Activity Filter` field and proceed to configure a custom activity" +" filter equation rule(s)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"How to add an activity filter to a workflow activity in Odoo Marketing " +"Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:184 +msgid "" +"This option is not a required field. If left alone, the activity applies to " +"all records related to the target audience of the overall campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:190 +msgid "" +"The :guilabel:`Applied Filter` field is non-configurable. It's simply a " +"summary of when the activity will be performed, *only* if it satisfies the " +"specified domain (e.g. the rules configured in the :guilabel:`Activity " +"Filter` field)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:195 +msgid "" +"After the activity's settings are fully configured, click :guilabel:`Save & " +"Close` to save the activity and return to the marketing automation campaign " +"form, :guilabel:`Save & New` to save the activity and immediately create " +"another one in a fresh :guilabel:`Create Activities` pop-up window, or " +":guilabel:`Discard` to delete the activity and return to the marketing " +"automation campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:202 +msgid "Workflow activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:204 +msgid "" +"Once an activity is created and saved, it appears as an activity card in the" +" :guilabel:`Workflow` section, located at the bottom of the marketing " +"automation campaign form. The analytics related to each activity is " +"displayed as a line graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "Typical workflow activity in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:212 +msgid "" +"The configured :guilabel:`Trigger` time for that activity can be found to " +"the left of the :guilabel:`Workflow Activity` card in the " +":guilabel:`Workflow` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:215 +msgid "" +"Once the activity has been triggered, a figure representing the number of " +":guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to " +"the right of the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:219 +msgid "" +"If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`" +" or :guilabel:`SMS`, there are more in-depth analytics beneath the activity " +"graph data, detailing how many messages have been :guilabel:`Sent`, and what" +" percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, " +"or :guilabel:`Bounced`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:225 +msgid "Child activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:227 +msgid "" +"There is also the option to add a *child activity* by clicking " +":guilabel:`Add child activity`, located at the bottom of each activity block" +" in the :guilabel:`Workflow` section of a marketing campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:231 +msgid "" +"Child activities are sub-activities that are connected to and triggered by " +"the activity above it, which is known as its *parent activity*. A child " +"activity is easy to recognize, as its slightly indented beneath its parent " +"activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "A typical child activity indented beneath its parent activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:239 +msgid "" +"Odoo provides a number of triggering options to launch a child activity - " +"all of which depend on the trigger configurations related to its parent " +"activity. Under the desired parent activity, hover over :guilabel:`Add child" +" activity`, to reveal a menu of child activity trigger options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst-1 +msgid "" +"The various child activity trigger options in the workflow section of a " +"campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:247 +msgid "Select any of the following child activity triggers:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:249 +msgid ":guilabel:`Add Another Activity`: instantly adds another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:250 +msgid "" +":guilabel:`Opened`: the next activity will be triggered if the recipient " +"opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:251 +msgid "" +":guilabel:`Not Opened`: the next activity will be triggered if the recipient" +" does not open the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:253 +msgid "" +":guilabel:`Replied`: the next activity will be triggered if the recipient " +"replies to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:254 +msgid "" +":guilabel:`Not Replied`: the next activity will be triggered if the " +"recipient does not reply to the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:256 +msgid "" +":guilabel:`Clicked`: the next activity will be triggered if the recipient " +"clicks on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:258 +msgid "" +":guilabel:`Not Clicked`: the next activity will be triggered if the " +"recipient does not click on a link included in the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:260 +msgid "" +":guilabel:`Bounced`: the next activity will be triggered if the mailing is " +"bounced (not sent)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:262 +msgid "" +"Once a trigger is selected, the user can configure the child activity the " +"same way they would for a regular workflow activity." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing.rst:8 +msgid "SMS Marketing" +msgstr "การตลาดผ่าน SMS" + +#: ../../content/applications/marketing/sms_marketing/essentials.rst:5 +#: ../../content/applications/marketing/social_marketing/essentials.rst:5 +msgid "Essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:3 +msgid "Mailing lists and blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:5 +msgid "" +"Creating or importing mailing lists in Odoo is very useful when curating " +"content to specific groups of people that already share similar demographics" +" or interests. Mailing lists are also a great way to get started if a " +"company is migrating from another system, and already has a established " +"audience." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:10 +msgid "" +"Moreover, providing an audience with the option to 'unsubscribe' from " +"mailings, helps businesses maintain good customer relations, by giving " +"recipients the power to control what they are (and aren't) sent." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:17 +msgid "" +"In the :guilabel:`SMS Marketing` app, there's an option on the header menu " +"called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with " +"options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:21 +msgid "" +"Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of" +" all mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the main SMS mailing list page on the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:28 +msgid "" +"To edit any existing list, select the desired list from the " +":guilabel:`Mailing Lists` page, and proceed to modify it in a number of " +"ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:31 +msgid "" +"To create a new mailing list, click :guilabel:`Create` in the upper left " +"corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank " +"mailing list template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list pop-up window in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:38 +msgid "" +"First, choose a name for the :guilabel:`Mailing List`, and activate the " +"option :guilabel:`Is Public`, to make the mailing list accessible to " +"recipients on the :guilabel:`Subscription Management page`. Doing so allows " +"users to update their subscription preferences at any time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:43 +msgid "" +"Checking the :guilabel:`Is Public` box is not required, but is recommended " +"to maintain good customer relations." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:46 +msgid "" +"When those fields are filled in, click :guilabel:`Create` to finalize the " +"form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing " +"list that was just created will be accessible." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:49 +msgid "" +"To edit or customize the mailing list further, select the mailing list from " +"the main :guilabel:`Mailing Lists` page to reveal the mailing list detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:52 +msgid "" +"Along the top of the mailing list detail form, there are various analytical " +"smart buttons displaying statistics for different metrics related to the " +"mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:56 +msgid "" +"To review or edit any of those elements, click the desired smart button to " +"reveal a separate page with in-depth data associated with the mailing list." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:59 +msgid "" +"To make changes to the mailing list itself, click the :guilabel:`Edit` " +"button in the upper-left corner of the mailing list detail form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of the mailing list template form in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:67 +msgid "" +"Don't forget to hit the :guilabel:`Save` button once changes have been made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:70 +msgid "Mailing lists contacts" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:72 +msgid "" +"Access contacts information from one or more mailing lists navigate to " +":menuselection:`Mailing Lists --> Mailing List Contacts` to reveal a " +"dashboard with with all the contacts associated with one or more of the " +"configured mailing lists in the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "" +"View of the mailing lists contact page in the Odoo SMS Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:81 +msgid "" +"By default, Odoo reveals the :guilabel:`Mailing List Contacts` page with the" +" :guilabel:`Exclude Blacklisted Phone` filter in the search bar. Therefore " +"only showing contact information for recipients who still want to receive " +"communications and mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:86 +msgid "Communication history in the Chatter" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:88 +msgid "" +"An accessible record of every sent mailing(s) is kept on each recipient's " +"*chatter* section, located beneath a recipient's contact form (in the " +"*Contacts* application)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:91 +msgid "" +"Database users can reference the chatter to easily keep track of " +"communications, and see a history of interactions with contacts and " +"prospects." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:94 +msgid "" +"For example, sales representatives can use the chatter to quickly find out " +"which :abbr:`SMS (Short Message Service)` mailing promotions a certain " +"customer has received (or not received)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of what the chatter looks like in the Odoo Contacts app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:104 +msgid "" +"Odoo *SMS Marketing* has a :guilabel:`Blacklist` feature that provides " +"recipients with the power to add their phone number to a list of people who " +"no longer want to receieve communications or mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:108 +msgid "" +"This is also known as the unsubscribe process: customers will automatically " +"be added onto a *blacklist*, if they click :guilabel:`Unsubscribe`, via " +"their :guilabel:`Subscription Management` page. Customers can also be added " +"manually to the blacklist, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:112 +msgid "" +"To see a complete collection of blacklisted numbers, navigate to the " +":menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone " +"Numbers` to reveal a dashboard containing every blacklisted phone number in " +"the database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "SMS Blacklist menu in the application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:120 +msgid "" +"To manually add a number to a blacklist, click the :guilabel:`Create` button" +" in the upper-left corner of the dashboard and enter the phone number on the" +" next page's form. There's also a checkbox to indicate whether that " +"particular phone numnber is :guilabel:`Active` (or not)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:128 +msgid "" +"Once the form is completed, click :guilabel:`Save` to add it to the " +":guilabel:`Blacklisted Phone Numbers` list. To remove any number from the " +"blacklist, select the desired number on the dashboard, and then, on the " +"phone number's form, click :guilabel:`Unblacklist`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:133 +msgid "Importing blacklists" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:135 +msgid "" +"During a software/platform migration, it is possible to import an already " +"existing blacklist of contacts. This would include customers, who have " +"already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` " +"mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:139 +msgid "" +"To do that, navigate to :menuselection:`SMS Marketing app --> Configuration " +"--> Blacklisted Phone Numbers`, and then select the :guilabel:`Favorites` " +"drop-down menu (beneath the search bar), and click :guilabel:`Import " +"records`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst-1 +msgid "View of how to import a blacklist in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:3 +msgid "SMS campaign settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` campaigns with Odoo *SMS " +"Marketing* isn't just an effective advertisement strategy, it's also a great" +" way to remind people about upcoming events, issued invoices, and so much " +"more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:9 +msgid "" +"But, before :abbr:`SMS (Short Message Service)` campaigns can be created " +"(and sent), a few specific settings and features must be enabled first." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:13 +msgid "SMS campaign setting" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:15 +msgid "" +"To enable :abbr:`SMS (Short Message Service)` campaigns in Odoo, make sure " +"the *Mailing Campaigns* feature is activated by going to " +":menuselection:`Email Marketing --> Configuration --> Settings`, and then " +"enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of the mailing campaigns setting in Odoo." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:24 +msgid "" +"Activating the *Mailing Campaigns* feature in the *General Settings* also " +"enables the *A/B Test* feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:27 +msgid "" +"Once the setting is enabled, navigate back to the :menuselection:`SMS " +"Marketing` app, and notice the :guilabel:`Campaigns` header menu is now " +"available for use. Similarly, the :guilabel:`A/B Test` tab is now also " +"available on every :abbr:`SMS (Short Message Service)` template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:32 +msgid "A/B tests" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:34 +msgid "" +":guilabel:`A/B Tests` allows any :abbr:`SMS (Short Message Service)` " +"mailings to be tested against other versions within the same campaign, in " +"order to compare which version is the most successful in producing " +"engagement and/or conversion outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:38 +msgid "" +"On an :abbr:`SMS (Short Message Service)` template form, under the " +":guilabel:`A/B Tests` tab, initially, there's only a single checkbox " +"labeled: :guilabel:`Allow A/B Testing.`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:41 +msgid "When clicked, a series of other options appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The A/B Test tab is located on an Odoo SMS Marketing app campaign form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:47 +msgid "" +"In the first field, enter a desired percentage of recipients to conduct the " +"A/B Test on." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:49 +msgid "" +"Beneath the percentage field is the :guilabel:`Winner Selection` field. This" +" is what Odoo will use to determine the successful result of an A/B Test. In" +" other words, this tells Odoo how to pick a winning A/B test." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:53 +msgid "" +"The following sections are available: :guilabel:`Manual`, :guilabel:`Highest" +" Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or " +":guilabel:`Revenues`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:56 +msgid "" +"Finally, the :guilabel:`Send Final On` field is listed. This represents the " +"date-time that Odoo uses as a deadline to determine the winning mailing " +"variation. Then, Odoo sends that winning mailing variation to the remaining " +"recipients, who weren't involved in the test, at that prior date and time." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:62 +msgid "" +"Quickly create different versions of the mailing to add to the A/B Test by " +"clicking the :guilabel:`Create an Alternate Version` button." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:66 +msgid "" +"Remember, the winning mailing variation is based on the criteria selected in" +" the :guilabel:`Winner Selection` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:70 +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:15 +msgid "Campaigns page" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:72 +msgid "" +"To create, edit, or analyze any campaign, click :menuselection:`Campaigns` " +"in the header menu of the :guilabel:`SMS Marketing` app. On the " +":guilabel:`Campaigns` page, each campaign displays various information " +"related to the mailings associated with that campaign (e.g. number of " +"emails, social posts, SMSs, and push notifications)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, " +"separated by stage." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:82 +msgid "Campaign templates" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:84 +msgid "" +"Click :guilabel:`Create` to create a new campaign, and Odoo reveals a blank " +"campaign template form to fill out. Alternatively, select any previously-" +"made campaign in order to duplicate, review, or edit its campaign template " +"form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "View of an SMS campaign template in Odoo SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:92 +msgid "" +"With each campaign, the options to :guilabel:`Send New Mailing`, " +":guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push " +"Notifications` are available above the template form." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:96 +msgid "" +"Whenever one of those communication options is added to the campaign, Odoo " +"will create a new corresponding tab on the template form, where those types " +"of messages can be reviewed or edited, along with various data sets related " +"to each specific mailing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:100 +msgid "" +"At the top of the template, there are various analytical smart buttons. When" +" clicked, Odoo reveals in-depth metrics related to that specific topic (e.g." +" :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate " +"page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:104 +msgid "" +"Beneath the smart buttons, are fields for :guilabel:`Campaign Name` and " +":guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be" +" added, as well (if necessary)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:108 +msgid "Sending SMSs through the Contacts app" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:110 +msgid "" +"Sending :abbr:`SMS (Short Message Service)` mailings directly through a " +"contact's form is available by default." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:113 +msgid "" +"In order to send an :abbr:`SMS (Short Message Service)` in this fashion, " +"navigate to the :menuselection:`Contacts` app, select the desired contact in" +" the database, and click on the :guilabel:`SMS` icon on the contact form " +"(next to the :guilabel:`Phone Number` field)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS icon is located on an individual's contact form in Odoo Contacts." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:121 +msgid "" +"To send a message to multiple contacts at once, navigate to the main " +":menuselection:`Contacts` app main dashboard, choose the :guilabel:`List " +"View`, and select all the desired contacts to whom the message should be " +"sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select a number of contacts, click action, and select send multiple SMSs." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:130 +msgid "Set up SMS templates for future use" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:132 +msgid "" +"In order to set up :guilabel:`SMS Templates` for future use, activate " +":ref:`developer mode <developer-mode>`, by navigating to the main Odoo " +"dashboard that is full of apps, and select the :menuselection:`Settings " +"app`. Then, scroll down to the :guilabel:`Developer Tools` section, and " +"click :guilabel:`Activate the Developer Mode`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:137 +msgid "" +"Once *developer mode* is activated, the main Odoo dashboard appears once " +"more, with a now-visible bug icon, which is located at the top-right corner " +"of the dashboard; this bug icon indicates that developer mode is currently " +"active." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:141 +msgid "" +"Next return to the :menuselection:`Settings app` and, in the now-visible " +"header menus at the top, choose :menuselection:`Technical --> SMS Templates`" +" to begin setting up :abbr:`SMS (Short Message Service)` templates for " +"future marketing campaigns." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"Select the SMS Template option in the Technical dropdown on the Settings " +"app." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:149 +msgid "" +"Inside of the :guilabel:`SMS Templates` dashboard, Odoo reveals an entire " +"page of :abbr:`SMS (Short Message Service)` templates. The default " +":guilabel:`List` view showcases each template's name, and to which " +"recipients it applies." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst:153 +msgid "" +"On this page, :abbr:`SMS (Short Message Service)` templates can be edited or" +" created from scratch." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_campaign_settings.rst-1 +msgid "" +"The SMS Templates page in Odoo is available after enabling developer mode in the General\n" +"Settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:3 +msgid "SMS essentials" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:5 +msgid "" +"Utilizing :abbr:`SMS (Short Message Service)` outreach in communication " +"strategies can help companies expand their market reach, especially in some " +"countries, where emails might not be very common, or even used at all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:9 +msgid "" +"Odoo's *SMS Marketing* application can also help boost conversion rates " +"around valuable actions, such as event registrations, free trials, " +"purchases, etc., since text and mobile-based marketing channels typically " +"yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through" +" rate)` outcomes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:15 +msgid "SMS marketing dashboard" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:17 +msgid "" +"When the application is opened, Odoo displays the main :guilabel:`SMS " +"Marketing` dashboard, which showcases the various SMS mailings that have " +"been created, along with pertinent information and data related to that " +"specific message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:21 +msgid "" +"The :guilabel:`Kanban` view is the default Odoo uses when the application is" +" opened, which provides an organized display of the SMS mailings that have " +"been created, and what their current status is at the moment." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:26 +msgid "" +"An :abbr:`SMS (Short Message Service)` mailing can have one of the following" +" statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or " +":guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:29 +msgid "" +"In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, " +"there are a few different view options to choose from. Each one provides a " +"unique take on the same SMS information." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:32 +msgid "" +"The :guilabel:`List` view provides the same useful data related to SMS " +"mailings, but in a more traditional list layout." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:35 +msgid "" +"The :guilabel:`Calendar` view provides a simple calendar, making it easy to " +"see when SMS mailings are going to be sent (or have been sent). If a future " +"date is clicked, Odoo reveals a blank SMS template that, when completed, " +"will be scheduled to be sent on that specific future date." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:39 +msgid "" +"Lastly, the :guilabel:`Graph` view visualizes that same SMS-related data in " +"series of graphs and charts. Odoo also provides various ways to sort and " +"group the data for more detailed analysis." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:43 +msgid "Create SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:45 +msgid "" +"To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` " +"dashboard, and Odoo reveals a blank SMS template form, which can be " +"configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Creating an SMS marketing template." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:52 +msgid "" +"First, give the mailing a :guilabel:`Subject`, which describes what the " +"mailing is about." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:54 +msgid "" +"Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS " +"(Short Message Service)` will be sent. By default, Odoo has " +":guilabel:`Mailing List` selected. If this is the desired " +":guilabel:`Recipients` field option, specify which mailing list Odoo should " +"send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select " +"Mailing List` field." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:60 +msgid "" +"To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> " +"Mailing List`. There, Odoo displays all previously created mailing lists, " +"along with various types of data related to that specific list (e.g. number " +"of contacts, mailings, recipients, etc.)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 +msgid "" +"To learn more about mailing lists and contacts, check out " +":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "View of the mailing list page in the SMS marketing application." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 +msgid "" +"To reveal all the possible options in the :guilabel:`Recipients` field, " +"click the field to see all the choices Odoo makes available." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 +msgid "" +"When another field (other than :guilabel:`Mailing List`) is selected, the " +"option to specify that chosen field even further becomes available — either " +"with a default recipient filter equation that appears automatically (which " +"can be customized to fit any business need), or, if no default recipient " +"filter equation is present, an :guilabel:`Add Filter` button will appear." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79 +msgid "" +"Clicking the :guilabel:`Add Filter` button, reveals fully customizable " +"domain rule fields, which can be configured similar to an equation. You can " +"create multiple recipient rules, if necessary." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82 +msgid "" +"Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to " +"recipients who fit into whatever criteria is configured in those fields. " +"Multiple rules can be added." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86 +msgid "" +"If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo " +"database (vendors, customers, etc.) will receive the :abbr:`SMS (Short " +"Message Service)`, by default — unless more specific recipient rules are " +"entered." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90 +msgid "" +"For instance, the message below will only be sent to contacts in the " +"database that are located in the United States (e.g. `Country` > `Country " +"Name` equals `United States`), and they haven't blacklisted themselves from " +"any mailings (e.g. `Blacklist` > `is` > `not set`)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:0 +msgid "Contact recipients on SMS marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99 +msgid "Writing SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101 +msgid "" +"Enter the content of the :abbr:`SMS (Short Message Service)` in the text " +"field, found in the :guilabel:`SMS Content` tab. Links and emojis can also " +"be included. Beneath the text field, Odoo displays how many characters are " +"used in the message, along with how many :abbr:`SMS (Short Message Service)`" +" mailings it will take to deliver the complete message." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107 +msgid "" +"To check the price of sending an :abbr:`SMS (Short Message Service)` for a " +"country, click on the :guilabel:`Information` icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS price check icon." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115 +msgid "" +"Credits must be purchased from Odoo in order to take advantage of the *SMS " +"Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be " +"sent without credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119 +msgid "`Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing>`_" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122 +msgid "Track links used in SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124 +msgid "" +"When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo " +"automatically generates link trackers to gather analytical data and metrics " +"related to those specific links, which can be found by going to " +":menuselection:`Configuration --> Link Tracker`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Link Tracker page." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:133 +msgid "Adjust SMS settings" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:135 +msgid "" +"Under the :guilabel:`Settings` tab of the SMS template, there is an option " +"to :guilabel:`Include opt-out link`. If activated, the recipient is able to " +"unsubscribe from the mailing list, thus avoiding all future mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:139 +msgid "" +"An employee can be designated as the :guilabel:`Responsible` in the " +":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "SMS Settings tab." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:147 +msgid "Send SMS messages" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:149 +msgid "" +"Once a mailing is created, choose when Odoo should deliver the message from " +"the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:151 +msgid "" +":guilabel:`Send`: sends the message immediately. Consider using this option " +"if the recipient list is highly refined, or in cases that involve fast " +"approaching deadlines, such as a \"flash sale.\"" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:153 +msgid "" +":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. " +"This is typically the best option for mailings related to a specific event. " +"Such a method can also be used to promote a limited-time offer, or to help " +"plan a company's content strategy in advance." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:156 +msgid "" +":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be " +"sent to one or multiple numbers for test purposes. Remember to use a comma " +"between phone numbers if multiple numbers are used as recipients." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:161 +msgid "Visualize reports" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:163 +msgid "" +"On the :guilabel:`Reporting` page (accessible via the " +":menuselection:`Reporting` option in the header menu), there are options to " +"apply different combinations of :guilabel:`Filters` and :guilabel:`Measures`" +" to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, " +":guilabel:`List`, and :guilabel:`Cohort` views.)" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:168 +msgid "" +"Each :guilabel:`Reporting` metric view option allows for more extensive " +"performance analysis of :abbr:`SMS (Short Message Service)` mailings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:171 +msgid "" +"For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short " +"Message Service)` data is visualized as different graphs and charts, which " +"can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop " +"down menu)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst-1 +msgid "Reporting page in SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:180 +msgid ":doc:`sms_campaign_settings`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:181 +msgid ":doc:`mailing_lists_blacklists`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing.rst:5 +msgid "Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:5 +msgid "SMS Pricing and FAQ" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:8 +msgid "What do I need to send SMSs?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:10 +msgid "" +"SMS Text Messaging is an In-App Purchase (IAP) service that *requires " +"prepaid credits* to work." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:13 +msgid "How many types of SMSs are there?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:15 +msgid "There are 2 types: GSM7 and UNICODE." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:17 +msgid "" +"**GSM7** is the standard format, with a limit of 160 characters per message," +" that includes the following characters:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "GSM7 characters available in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:24 +msgid "" +"**UNICODE** is the format applied if a special character, that *is not* in " +"the GSM7 list, is used. Limit per SMS: 70 characters." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:28 +msgid "" +"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above" +" these limits, the content is divided into a multi-part message* and the " +"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, " +"in real-time, the system displays the number of SMS mailings the message " +"represents." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34 +msgid "How much does it cost to send an SMS?" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:36 +msgid "" +"The price of an SMS depends on the destination and the length (number of " +"characters) of the message. To see the **price per country, please " +"consult**: `Odoo SMS - FAQ <https://iap-" +"services.odoo.com/iap/sms/pricing#sms_faq_01>`_." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:40 +msgid "" +"The number of SMSs a message represents will always be available in the " +"database." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "" +"Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:47 +msgid "How to buy credits" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49 +msgid "Go to :menuselection:`Settings --> Buy Credits`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Buying credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:55 +msgid "Or go to :menuselection:`Settings --> View my Services`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst-1 +msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:62 +msgid "" +"If Odoo Online (Saas) is being used, along with the Enterprise version, free" +" trial credits are available to test the feature." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:66 +msgid "More common questions" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Is there an expiration time for my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, credits do not expire." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +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 "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only if that phone number supports SMS (e.g. SIP phones)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I receive an invoice to buy my credits?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can the recipient answer me?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "No, it is not possible to reply to the SMS." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send multiple SMSs at once, but I don't have enough " +"credits to send them all?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Multiple SMS communications at once at are counted as a single transaction, " +"so no SMSs will be sent until there are enough credits to send them all." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Do I have a history of the sent SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"A history of sent SMSs, along with all pertinent information related to its " +"sent contacts (and the message itself), can be found in the :guilabel:`Sent`" +" column of the main :guilabel:`SMS Marketing` dashboard (while in " +":guilabel:`Kanban` view)." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:91 +msgid "" +"For more detailed information, select a desired SMS from the main dashboard " +"(in :guilabel:`Kanban` view), and click on either link in the blue banner " +"above the SMS detail form to learn more." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I send as many SMSs I want at once?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Yes, if you have enough credits." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**If an SMS is sent to a number that doesn't exist in the list of " +"recipients, will credits be lost?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"No, not if the phone number is incorrectly formatted (e.g. too many digits)." +" However, if the SMS is sent to the wrong person (or to a fake number), the " +"credit for that SMS will be lost." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**What happens if I send my SMS to a paying number (e.g.: a contest to win a" +" ticket for a festival)?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"The SMS will not be delivered to that kind of number, so no charges will be " +"made." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"**Can I identify the numbers that do not exist when I send several SMSs?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "Only the ones that have an invalid format." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**How does the GDPR regulation affect this service?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "**Can I use my own SMS provider?**" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:0 +msgid "" +"Yes, but it is not possible out-of-the-box. Odoo experts can help customize " +"a database to allow for the use of a personal SMS provider. Please check our" +" success packs `here <https://www.odoo.com/pricing-packs>`_." +msgstr "" + +#: ../../content/applications/marketing/social_marketing.rst:8 +msgid "Social Marketing" +msgstr "การตลาดโซเชียล" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:3 +msgid "Social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:5 +msgid "" +"Social marketing campaigns help companies connect directly with the " +"marketplace. These campaigns are helpful when introducing a new product to " +"customers, explaining the value of a product or service, or when advertising" +" an upcoming event or product release." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:9 +msgid "" +"The most effective social marketing campaigns typically involve multiple " +"channels to maximize content distribution, and Odoo's *Social Marketing* " +"application acts as a singular control center to monitor, plan, post, track," +" and analyze all of the various content and content channels within a single" +" dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:17 +msgid "" +"To access a complete overview of all social marketing campaigns, open the " +":menuselection:`Social Marketing` application, and click " +":menuselection:`Campaigns` from the header menu. Doing so reveals a separate" +" page with every campaign in a default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the campaigns page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:25 +msgid "" +"Each *stage* in the kanban view can be edited, by clicking the " +":guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located" +" to the right of the stage title." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:29 +msgid "" +"The **gear icon** *only* appears when the cursor hovers to the left of the " +"**+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals " +"the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:37 +msgid "" +"Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage " +"column can be restored by clicking the folded version of it on the main " +":guilabel:`Campaigns` dashboard in the default kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:41 +msgid "" +"Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name " +"and the sequence of the stage can be modified. If changes are made, be sure " +"to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:44 +msgid "Clicking :guilabel:`Delete` removes the stage entirely." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:47 +msgid "" +"To add a new stage to the pipeline, side-scroll to the right on the " +":guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in " +"the desired information, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:52 +msgid "" +"The same social marketing campaign information on the :guilabel:`Campaigns` " +"dashboard can also be viewed as a list, by selecting the :guilabel:`List` " +"option, located under the search bar, in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:57 +msgid "Create social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:59 +msgid "" +"First, open the :menuselection:`Social Marketing` application, and select " +":guilabel:`Campaigns` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:62 +msgid "" +"On the :guilabel:`Campaigns` dashboard, a new campaign can be created by " +"clicking the quick add :guilabel:`+ (plus sign)` located in the top-right " +"corner of each stage in the pipeline, visible in the kanban view. Campaigns " +"can also be created by clicking :guilabel:`Create` in the upper-left corner " +"of the :guilabel:`Campaigns` dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:67 +msgid "" +"Both options reveal a new campaign detail window directly on the " +":guilabel:`Campaigns` dashboard when clicked." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of the quick add option for campaigns in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:74 +msgid "" +"Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and " +":guilabel:`Tags` can be entered. When all modifications are complete, click " +":guilabel:`Add` to add the campaign to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:78 +msgid "Edit social marketing campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:80 +msgid "" +"In order to edit a campaign in greater detail, and create/send various forms" +" of communications related to it, the template page for that campaign must " +"be accessed and modified, accordingly. There are multiple ways to access a " +"template page for a campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:84 +msgid "" +"After entering the pertinent information in the :guilabel:`Quick Add` " +"campaign drop-down, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:86 +msgid "" +"Simply select the desired campaign from the :guilabel:`Campaigns` dashboard " +"in list or kanban view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:88 +msgid "" +"On the :guilabel:`Campaigns` dashboard in the kanban view, select the " +":guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and " +"select :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:91 +msgid "" +"Any of the above routes will reveal the *Campaign Template* page for that " +"specific campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:94 +msgid "Social marketing campaign templates" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:96 +msgid "" +"On a *Campaign Template* page, numerous elements can be customized/modified," +" and various forms of communications can be created, modified, and sent or " +"scheduled. Below is a sample of a completed campaign template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst-1 +msgid "View of a sample campaign template page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:105 +msgid "" +"In order for the :guilabel:`Send New Mailing` option to appear on campaign " +"templates, make sure the *Mailing Campaigns* feature is enabled in the " +"*Email Marketing* app. To do that, navigate to :menuselection:`Email " +"Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing " +"Campaigns`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:111 +msgid "" +"In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS " +"Marketing* application must be installed on the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:115 +msgid "Add content and communications to campaigns" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:117 +msgid "" +"If the proper settings and applications are installed (as instructed above)," +" there are four forms of communication/content options that can be added to " +"campaigns. Each of these options are displayed as buttons in the upper-left " +"corner of the campaign template page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:121 +msgid "" +":guilabel:`Send New Mailing`: reveals a blank email template on a separate " +"page, in which the message can be fully customized in a variety of ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:123 +msgid "" +":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in " +"which a SMS communication can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:125 +msgid "" +":guilabel:`Send Social Post`: reveals a blank social post template on a " +"separate page, in which a post can be created, and applied to social media " +"accounts that are already connected to the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:128 +msgid "" +":guilabel:`Push Notification`: reveals a similar blank social post template " +"on a separate page, however, the :guilabel:`Push Notification` options are " +"already pre-selected in the :guilabel:`Post on` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:132 +msgid "" +"Whichever form of communication is created, once it's completed, Odoo " +"returns to the :guilabel:`Campaign Template` page, showcasing that new " +"content in its corresponding tab (e.g. :guilabel:`Mailings`, " +":guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push " +"Notifications`)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:137 +msgid "" +"As content and communications are added to a campaign, tabs for those " +"specific mediums appear, along with a variety of analytical smart buttons " +"(e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, " +"etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:141 +msgid "" +"These smart buttons, located at the top of the template, display different " +"metrics related to the campaign, and its various communications and content." +" Clicking any smart button reveals a separate page dedicated to that " +"particular element of the campaign, allowing for quicker, more organized " +"analysis." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:147 +msgid "" +"The Odoo *Social Marketing* app is integrated with other Odoo applications, " +"such as *Sales*, *Invoicing*, *CRM*, and *Website*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:151 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_essentials`" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:3 +msgid "Social marketing essentials" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 +msgid "" +"Odoo's *Social Marketing* application helps content marketers create and " +"schedule posts, manage various social media accounts, analyze content " +"effectiveness, and engage directly with social media followers in one, " +"centralized location." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 +msgid "Social media accounts" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 +msgid "" +"In order to create social posts and analyze content with Odoo *Social " +"Marketing*, social media accounts **must** be added as a *stream* on the " +"application's main dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 +msgid "" +"Be aware that personal profiles **cannot** be added as a stream. The main " +"use of Odoo *Social Marketing* is to manage and analyze business accounts on" +" social media platforms." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:20 +msgid "" +"Odoo *Social Marketing* has some limitations in regards to social media " +"accounts. For example, Odoo **cannot** handle a large quantity of various " +"pages (e.g. ~40 pages) under the same company. The same limitations are " +"present in a multi-company environment because of how the API is " +"constructed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:26 +msgid "" +"In multi-company environments, if every company doesn't activate a page at " +"once, it will result in a permission error." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 +msgid "" +"For example, if Company 1 is the only company selected from the main Odoo " +"dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those" +" pages will be accesible on the *Social Marketing* dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:33 +msgid "" +"However, if on that same database, the user adds Company 2 from the company " +"drop-down menu in the header, and attempts to add those same streams, it " +"results in a permission error." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"View of the permission error that appears when incorrectly attempting to add" +" stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:41 +msgid "Social media streams" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:43 +msgid "" +"To add a social media business account as a stream, navigate to " +":menuselection:`Social Marketing app` and select the :guilabel:`Add A " +"Stream` button located in the upper-left corner. Doing so reveals an " +":guilabel:`Add a Stream` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the pop-up window that appears when Add a Stream is selected in " +"Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:51 +msgid "" +"In the :guilabel:`Add a Stream` pop-up window, choose to :guilabel:`Link a " +"new account` for a business from any of the following popular social media " +"platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, " +":guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:55 +msgid "" +"After clicking the desired social media outlet from the :guilabel:`Add a " +"Stream` pop-up window, Odoo navigates directly to that specific social media" +" outlet's authorization page, where permission must be granted, in order for" +" Odoo to add that particular social media account as a stream to the *Social" +" Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample of a populated social marketing dashboard with social media streams " +"and content." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +msgid "" +"Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on " +"the main :guilabel:`Social Marketing` dashboard, and a new column, with that" +" account's posts, is added. Accounts/streams can be added at any time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:69 +msgid "" +"A :guilabel:`Facebook` page can be added as long as the :guilabel:`Facebook`" +" account that grants permission is the administrator for the page. It should" +" also be noted that different pages can be added for different streams." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:74 +msgid "" +":guilabel:`Instagram` accounts are added through a :guilabel:`Facebook` " +"login because it uses the same API. This means, an :guilabel:`Instagram` " +"account needs to be linked to a :guilabel:`Facebook` account in order for it" +" to show up as a stream in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:79 +msgid "Posts" +msgstr "โพสต์" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 +msgid "" +"Clicking on a post from a social media stream reveals a pop-up window, " +"showcasing the content of that specific post, along with all the engagement " +"data related to it (e.g. likes, comments, etc.)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample of a social media post's pop-up window in Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:88 +msgid "" +"If desired, the user can leave a new comment of the post from the post's " +"pop-up window, by typing one in the :guilabel:`Write a comment...` field, " +"and clicking :guilabel:`Enter` to post that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:93 +msgid "Create leads from comments" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:95 +msgid "" +"Odoo *Social Marketing* also provides the ability to create leads directly " +"from social media comments." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:98 +msgid "" +"To create a lead from a comment left on a social media post, click on the " +"desired post from the dashboard to reveal that post's specific pop-up " +"window. Then, scroll to the desired comment, and click the :guilabel:`three " +"vertical dots` icon to the right of that comment." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:102 +msgid "" +"Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"The drop-down menu beside a comment revealing the option to create a lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:108 +msgid "" +"Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a " +":guilabel:`Conver Post to Lead` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"The convert post to lead pop-up window that appears in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:115 +msgid "" +"In this pop-up window, select to either: :guilabel:`Create a new customer`, " +":guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a " +"customer`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:119 +msgid "" +"If :guilabel:`Link to an existing customer` is selected, a new " +":guilabel:`Customer` field appears beneath those options, wherein a customer" +" can be chosen to be linked to this lead." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 +msgid "" +"Once the desired selection has been made, click the :guilabel:`Convert` " +"button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. " +"Doing so reveals a fresh lead detail form, where the necessary information " +"can be entered and processed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New lead detail form generated from a social media comment in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:131 +msgid "Insights" +msgstr "ข้อมูลเชิงลึก" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:133 +msgid "" +"When a social media account stream is added to the *Social Marketing* " +"dashboard, each stream also displays and links that specific social media " +"platform's KPIs (if the platform has them)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:136 +msgid "" +"To get redirected to the statistics and metrics related to any social media " +"account's KPIs, click on the :guilabel:`Insights` link, located at the top " +"of each stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Visual of how the Insights link appears on the dashboard of the Social " +"Marketing app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 +msgid "" +"In a multi-company environment, if not *all* pages are selected, de-" +"authentication happens." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:146 +msgid "" +"For example, if the companies have 3 *Facebook* pages, but only grant access" +" to 1, and try to grant access to another at a later date, they will be de-" +"authenticated, and access to the initial page's insights/analytics will be " +"lost." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:150 +msgid "" +"So, be sure to add *all* pages for *all* companies in a multi-company " +"environment to avoid this issue. If a page gets de-autenticated, simply " +"remove the stream, and re-establish it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:154 +msgid "Create and post social media content" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:156 +msgid "" +"Odoo *Social Marketing* offers the ability to create and post content for " +"social media accounts directly through the application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:159 +msgid "" +"To create content for social media accounts, navigated to the " +":menuselection:`Social Marketing app`, and click :guilabel:`New Post` " +"located in the upper-right corner of the *Social Marketing* dashboard." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New Post button on the main dashboard of the Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:167 +msgid "" +"Or, navigate to :menuselection:`Social Marketing app --> Posts` and click " +"the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"New button on the Social Posts page in the Odoo Social Marketing " +"application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:174 +msgid "" +"Either route reveals a blank social media post detail form that can be " +"customized and configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "Blank social media post detail page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 +msgid "Post detail form" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:184 +msgid "" +"The social media post detail form in Odoo *Social Marketing* has many " +"different configurable options available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:188 +msgid "Company" +msgstr "บริษัท" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:190 +msgid "" +"If working in a multi-company environment, the first field in the " +":guilabel:`Your Post` section of the social media post detail form is " +":guilabel:`Company`. In this field, select the company that should be " +"connected to this specific social media post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:195 +msgid "Post on" +msgstr "โพสต์บน" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 +msgid "" +"If working in a single-company environment, the first field in the " +":guilabel:`Your Post` section of the social media post detail form is " +":guilabel:`Post on`. In this field, determine which social media outlets " +"(streams) this post is intended to be posted on, and/or which website's " +"visitors this post should be sent to, via push notification, by checking the" +" box beside the desired option(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 +msgid "" +"Odoo automatically provides every available social media account that's been" +" linked to the database as an option in this section. If a social media " +"account hasn't been added as a stream to the *Social Marketing* application," +" it will **not** appear as an option on the post template." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 +msgid "" +"Multiple social media outlets (streams) and websites can be selected in the " +":guilabel:`Post on` field. At least **one** option in the :guilabel:`Post " +"on` field *must* be selected." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:210 +msgid "" +"In order for the :guilabel:`Push Notification` option to appear on the " +"social media post detail form in Odoo *Social Marketing*, make sure the " +"*Enable Web Push Notifications* feature is enabled in the *Website* app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:214 +msgid "" +"To do that, navigate to :menuselection:`Website app --> Configuration --> " +"Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the " +"corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:219 +msgid "Message" +msgstr "ข้อความ" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:221 +msgid "" +"Next, there's the :guilabel:`Message` field. This is where the main content " +"of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:223 +msgid "" +"In the :guilabel:`Message` field, type in the desired message for the social" +" post. After typing, click away from the :guilabel:`Message` field to reveal" +" visual samples of how the post will look on all the previously selected " +"social media accounts (and/or websites, as push notifications)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Sample social media post with visual samples of how it will appear on social" +" media outlets." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:232 +msgid "" +"Emojis can also be added directly to the text in the :guilabel:`Message` " +"field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line " +"of the :guilabel:`Message` field to the far right. Clicking this icon " +"reveals a drop-down menu containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +msgid "" +"If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a " +"character counter appears beneath the :guilabel:`Message` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:241 +msgid "Attach Images" +msgstr "แนบรูปภาพ" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:243 +msgid "" +"If images are to be used in the post, click the :guilabel:`Attach Images` " +"button, in the :guilabel:`Attach Images` field, located beneath the " +":guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In " +"this pop-up window, select the desired image from the hard drive, and upload" +" it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:248 +msgid "" +"After successfully uploading and attaching the desired image, Odoo reveals a" +" new preview of the social media post, complete with the newly-added image, " +"on the right side of the detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Visualized samples of post with newly-attached images in Odoo Social " +"Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 +msgid "Campaign" +msgstr "แคมเปญ" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:258 +msgid "" +"Next, there is the :guilabel:`Campaign` field. This non-required field " +"provides the options to attach this post to a specific marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:261 +msgid "" +"To add this post to a pre-existing campaign, click the empty " +":guilabel:`Campaign` field to reveal a drop-down menu, containing all the " +"existing campaigns in the database. Select the desired campaign from this " +"drop-down menu to add this post to that campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 +msgid "" +"To create a new campaign directly from the social media post detail form, " +"start typing the name of the new campaign in the blank :guilabel:`Campaign` " +"field, and select either :guilabel:`Create` or :guilabel:`Create and " +"edit...`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Drop-down menu options of Create or Create and edit in the Campaign field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:273 +msgid "" +"Clicking :guilabel:`Create` creates the campaign, which can be " +"edited/customized later." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +msgid "" +"Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a " +":guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign " +"Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly " +"configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Create campaign pop-up window that appears on a social media post detail " +"form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 +msgid "" +"When all the desired settings have been entered, click :guilabel:`Save & " +"Close` to save the campaign and return to the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:287 +msgid "When" +msgstr "เมื่อ" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:289 +msgid "" +"Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to " +"have Odoo publish the post immediately, or :guilabel:`Schedule later` to " +"have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:293 +msgid "" +"If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` " +"field appears. Clicking the empty field reveals a pop-up calendar, in which " +"a future date and time can be designated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Schedule date pop-up window that appears on social media post detail form in" +" Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 +msgid "" +"After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo" +" will promptly publish the post at that specific date and time on the pre-" +"detemined social media account(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:304 +msgid "" +"If scheduling a post, the :guilabel:`Post` button at the top of the social " +"media post detail form changes to :guilabel:`Schedule`. Be sure to click " +":guilabel:`Schedule` after completing the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 +msgid "" +"Doing so, locks in that specific date/time for Odoo to send the post, and it" +" changes the status of the post to :guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +msgid "Push Notification Options" +msgstr "ตัวเลือกการแจ้งเตือนแบบพุช" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 +msgid "" +"If one (or multiple) :guilabel:`[Push Notification]` options are chosen in " +"the :guilabel:`Post on` field, a specific :guilabel:`Push Notification " +"Options` section appears at the bottom of the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "Push notification options section on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 +msgid "It should be noted that *none* of these fields are required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:324 +msgid "" +"The first field in this section is :guilabel:`Notification Title`. In this " +"field, there is the option to add a custom title to the push notification " +"that will be sent." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +msgid "" +"To designate a specific page on the website that should trigger this push " +"notification, enter that page's URL in the :guilabel:`Target URL` field. " +"Then, once a visitor reaches that specific page, Odoo will display the push " +"notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:331 +msgid "" +"Below that field is the option to add a custom :guilabel:`Icon Image` to the" +" push notification. This is an icon that appears beside the push " +"notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:334 +msgid "" +"To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering " +"over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up " +"window, in which the desired icon image can be located on the hard drive, " +"and subsequently uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:338 +msgid "" +"Once that's complete, Odoo automatically updates the visual preview of how " +"the icon appears on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:342 +msgid "" +"Next, if the post is scheduled to be posted later, there is the option to " +"ensure the post is sent in the visitor's timezone, by enabling the " +":guilabel:`Local Time` option. If enabled, Odoo will send it at the " +"appropriate, pre-determined time, taking the visitor's location into " +"consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"The Local Time option in the Push Notification Options section of features." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:351 +msgid "" +"Then, there is the :guilabel:`Match all records` field. This field provides " +"the ability to target a specific group of recipients in the database, based " +"on certain criteria, and can be applied to match :guilabel:`all` or " +":guilabel:`any` of the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:355 +msgid "" +"To utilize this field, click the :guilabel:`+ Add condition` button, which " +"reveals an equation-like rule field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:358 +msgid "" +"In this equation-like rule field, specifiy the specific criteria Odoo should" +" take into account when sending this post to a particular target audience." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"Push notification conditions set up to match a specific amount of records in" +" the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:365 +msgid "" +"To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the " +"far-right of the rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:367 +msgid "" +"To add a branch (series of additional rules based on the previous rule, to " +"further specify a target audience), click the unique :guilabel:`branch " +"icon`, located to the right of the :guilabel:`➕ (plus sign) icon`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:371 +msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:373 +msgid "" +"The size of the specified target audience of recipients is represented by " +"the number of :guilabel:`Records` displayed beneath the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:377 +msgid "Posts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:379 +msgid "" +"To see a complete overview of posts, go to Odoo :menuselection:`Social " +"Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every " +"post that has been created and posted with Odoo can be seen and accessed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:383 +msgid "" +"There are four different view options for the :guilabel:`Social Posts` page " +"data: *kanban*, *calendar*, *list*, and *pivot*." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:386 +msgid "" +"The view options are located in the upper right corner of the " +":guilabel:`Posts` page, beneath the search bar." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:393 +msgid "" +"By default, Odoo displays the posts in a kanban view. The information on " +"this page can be sorted even further, via the left sidebar, where all " +"connected social accounts and posts can be quickly seen, accessed, and " +"analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:397 +msgid "" +"The kanban view is represented by an :guilabel:`inverted bar graph icon` in " +"the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "" +"Kanban view of the posts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 +msgid "Calendar view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:406 +msgid "" +"The calendar view option displays a visual representation of posts in a " +"calendar format of when posts were published, or are scheduled to be " +"published. This option provides a clear overview of any planned day, week, " +"or month, and Odoo displays all drafted, scheduled, and published posts." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:411 +msgid "" +"Clicking on a date reveals a blank social media post detail form, in which a" +" social media post can be created, and Odoo will post it on that specific " +"date/time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:414 +msgid "" +"The calendar view is represented by a :guilabel:`calendar icon` in the " +"upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "Example of the calendar view in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:422 +msgid "" +"The list view option is similar to the kanban option, but instead of " +"individual blocks, all post information is displayed in a clear, list " +"layout. Each line of the list displays the :guilabel:`Social Accounts`, " +":guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:426 +msgid "" +"There is also a helpful left sidebar that organizes all posts by " +":guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as " +"well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:429 +msgid "" +"The list view is represented by four vertical lines in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the list option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:435 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:437 +msgid "" +"The pivot view option provides a fully customizable grid table, where " +"different measures of data can be added and analyzed." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "View of the pivot option on the posts page in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:444 +msgid "" +"The pivot view option provides numerous analytical options, allowing for in-" +"depth, detailed analysis of various posts and metrics." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:447 +msgid "" +"Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot " +"table to reveal more metric options to add to the grid." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:450 +msgid "" +"While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is " +"available, located to the right of the :guilabel:`Measures` drop-down menu, " +"in the upper-left corner of the :guilabel:`Social Posts` page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:454 +msgid "" +"Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to" +" the pivot view." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:456 +msgid "From left to right, those options are:" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:458 +msgid "" +":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid " +"table." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:459 +msgid "" +":guilabel:`Expand All`, which expands each line in the grid, revealing more " +"detailed information related to it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:461 +msgid "" +":guilabel:`Download`, which, when clicked, instantly downloads the pivot " +"table as a spreadsheet." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:465 +msgid "Visitors" +msgstr "ผู้เยี่ยมชม" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:467 +msgid "" +"To see a complete overview of all the people who have visited the website(s)" +" connected to the database, navigate to :menuselection:`Social Marketing app" +" --> Visitors`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "View of the Visitors page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:474 +msgid "" +"Here, Odoo provides a detailed layout of all the visitors' pertinent " +"information in a default kanban view. If visitors already have contact " +"information in the database, the option to send them an :guilabel:`Email` " +"and/or an :guilabel:`SMS` is available." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:478 +msgid "" +"This same visitor data can also be viewed as a list or a graph. Those view " +"options are located in the upper-right corner of the :guilabel:`Visitors` " +"page." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:482 +msgid "Social media page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:484 +msgid "" +"Another way to quickly link social media accounts to Odoo *Social Marketing*" +" can be done on the :guilabel:`Social Media` page. To access the " +":guilabel:`Social Media` page, navigate to :menuselection:`Social Marketing " +"app --> Configuration --> Social Media`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:488 +msgid "" +"On the :guilabel:`Social Media` page there is a collection of all social " +"media options, each complete with a :guilabel:`Link account` button: " +":guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, " +":guilabel:`Twitter`, :guilabel:`YouTube`, and :guilabel:`Push " +"Notifications`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social media page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:497 +msgid "Social accounts page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:499 +msgid "" +"To see a list of all social accounts and websites linked to the database, go" +" to :menuselection:`Social Marketing app --> Configuration --> Social " +"Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, " +"the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, " +"who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it " +"is associated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst-1 +msgid "" +"View of the social accounts page in the Odoo Social Marketing application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:509 +msgid "" +"To edit/modify any of the social accounts on this page, simply select the " +"desired account from the list on this page, and proceed to make any " +"adjustments necessary." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:513 +msgid "Social streams page" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:515 +msgid "" +"To view a separate page with all the social media streams that have been " +"added to the main *Social Marketing* dashboard, navigate to " +":menuselection:`Social Marketing app --> Configuration --> Social Streams`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:523 +msgid "" +"Here, the social stream information is organized in a list with the " +":guilabel:`Social Media`, the :guilabel:`Title` of the stream, the " +":guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`," +" etc.), who it was :guilabel:`Created by`, and the :guilabel:`Company` to " +"which it is associated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:528 +msgid "" +"To modify any stream's information, simply click the desired stream from the" +" list, and proceed to make any necessary adjustments." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:532 +msgid "" +":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:5 +msgid "Surveys" +msgstr "แบบสอบถาม" + +#: ../../content/applications/marketing/surveys.rst:8 +msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:3 +msgid "Survey essentials" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:5 +msgid "" +"Companies often use surveys to collect valuable information from their " +"customers and employees, which in turn, allows them to make more informed " +"business decisions." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:8 +msgid "" +"In Odoo, surveys are used to collect customer feedback, evaluate the success" +" of a recent event, measure the satisfaction of customers (or employees), " +"and gain more insight into shifting market sentiments." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:13 +msgid "Getting started" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:15 +msgid "" +"To begin, open the :guilabel:`Surveys` application and click " +":guilabel:`Create`. Odoo then redirects the page to a blank survey template " +"form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:18 +msgid "" +"On the survey form, add a :guilabel:`Survey Title` and then add a cover " +"image to the survey by hovering over the photo icon and clicking on the " +":guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose " +"an image from the local files." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:22 +msgid "" +"Below the :guilabel:`Survey Title` are various tabs in which the survey " +"questions and format can be created and customized. These tabs are labeled " +"as follows:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:25 +msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:26 +msgid "" +":guilabel:`Description`: contextual information to aid in understanding the " +"survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:27 +msgid "" +":guilabel:`Options`: choices for survey respondents to answer the questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "Various tabs that can be found on the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:34 +msgid "Questions tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:36 +msgid "" +"Add questions and sections to the survey in the :guilabel:`Questions` tab. A" +" section divides the survey into parts in order to visually group similar " +"questions together. To make a section, click :guilabel:`Add a section` and " +"type in a section name. Then, add questions or drag and drop questions into " +"the divided sections." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:41 +msgid "" +"Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and" +" Questions` pop-up to create and customize the survey question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst-1 +msgid "The survey question pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:49 +msgid "Create questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:51 +msgid "" +"In the :guilabel:`Create Sections and Questions` pop-up, type the question " +"in the :guilabel:`Question` field. Then, choose the :guilabel:`Question " +"Type`. A preview of how the question type looks is shown in the preview " +"window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:55 +msgid "Choose from the following :guilabel:`Question Types`:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:57 +msgid ":guilabel:`Multiple Lines Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:58 +msgid ":guilabel:`Single Line Text Box`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:59 +msgid ":guilabel:`Numerical Value`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:60 +msgid ":guilabel:`Date`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:61 +msgid ":guilabel:`Datetime`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:62 +msgid ":guilabel:`Multiple choice: only one answer`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:63 +msgid ":guilabel:`Multiple choice: multiple answers allowed`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:64 +msgid ":guilabel:`Matrix`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:67 +msgid "" +"Different features appear in the :guilabel:`Answers` and :guilabel:`Options`" +" tabs, depending on the :guilabel:`Question Type` chosen. However, the " +":guilabel:`Description` tab always remains the same, regardless of what " +"question is chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:72 +msgid "Create sections and questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:74 +msgid "" +"Once a :guilabel:`Question Type` has been selected, there are three possible" +" tabs where information can be customized for the question. These include " +"the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and " +":guilabel:`Options` tabs." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:78 +msgid "" +"Each tab offers a variety of different features depending on what " +":guilabel:`Question Type` was chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:81 +msgid "" +"For example, in the :guilabel:`Options` tab, the following options may " +"appear:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:83 +msgid ":guilabel:`Mandatory Answer`: the question must be answered." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:84 +msgid "" +":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or " +"multiple choices can be selected per row." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:86 +msgid ":guilabel:`Number of columns`: select how many columns are displayed." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:87 +msgid ":guilabel:`Images on answers`: allow images on the answer options." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:88 +msgid "" +":guilabel:`Conditional Display`: determine if the question is displayed " +"based on the participant's answer to a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:90 +msgid "" +":guilabel:`Show Comments Field`: allow the participant to type a comment in " +"a text box." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:91 +msgid "" +":guilabel:`Question Time Limit`: for live session surveys, set a time limit " +"for the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:94 +msgid "Conditional Display" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:96 +msgid "" +":guilabel:`Conditional Display` means the question is only displayed if the " +"specified conditional answer has been selected in a previous question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:99 +msgid "" +"When the box next to :guilabel:`Conditional Display` is selected, the " +":guilabel:`Triggering Question` field appears. Select a question from the " +"survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:102 +msgid "" +"Then, a :guilabel:`Triggering Answer` field appears. Here, select which " +"answer will trigger this :guilabel:`Conditional Display` question." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:106 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:108 +msgid "" +"Back on the main survey template form, under the :guilabel:`Options` tab, " +"there are different sections of settings that can be modified." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:111 +msgid "The sections include:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:113 +msgid "" +":guilabel:`Questions`: focuses on the overall presentation of the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:114 +msgid ":guilabel:`Scoring`: decides how the survey is scored" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:115 +msgid ":guilabel:`Candidates`: manages access to the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:116 +msgid "" +":guilabel:`Live Session`: enables the survey into a real-time group " +"activity." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:119 +msgid "Questions" +msgstr "คำถาม" + +#: ../../content/applications/marketing/surveys/create.rst:121 +msgid "" +"First, select the :guilabel:`Layout` of the survey. The following options " +"can be chosen:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:123 +msgid ":guilabel:`One page with all the questions`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:124 +msgid ":guilabel:`One page per section`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:125 +msgid ":guilabel:`One page per question`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:127 +msgid "" +"If either the :guilabel:`One page per section` or :guilabel:`One page per " +"question` options are chosen, then the :guilabel:`Back Button` option " +"appears. If selected, the :guilabel:`Back Button` option allows the " +"participant to go back to a question during the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:131 +msgid "" +"Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` " +"setting, which indicates how the participant's progress during the survey is" +" displayed. It is shown as either a :guilabel:`Percentage` or a " +":guilabel:`Number`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:135 +msgid "" +"Next, there is an option available to add a :guilabel:`Survey Time Limit`. " +"To implement this option, simply check the box, and enter the amount of time" +" (in minutes) participants have to complete the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:139 +msgid "" +"After the :guilabel:`Survey Time Limit` option is a section labeled " +":guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per " +"section`, in other words, the number of random questions can be configured " +"by section. This mode is ignored in a live session." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:144 +#: ../../content/applications/marketing/surveys/scoring.rst:56 +msgid ":doc:`time_random`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:147 +msgid "Scoring" +msgstr "การให้คะแนน" + +#: ../../content/applications/marketing/surveys/create.rst:149 +msgid "" +"The following options are available when deciding how a :guilabel:`Scoring` " +"method:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:151 +msgid ":guilabel:`No scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:152 +msgid ":guilabel:`Scoring with answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:153 +msgid ":guilabel:`Scoring without answers at the end`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:155 +msgid "" +"If either the :guilabel:`Scoring with answers at the end` or " +":guilabel:`Scoring without answers at the end` options are selected, a " +":guilabel:`Success %` field appears. Set the percentage of correct answers " +"needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:159 +msgid "" +"Next, there is the option to make the survey a certification. To do so, " +"check the box next to the option labeled :guilabel:`Is a Certification`, and" +" two additional fields appear. Select a color theme in the " +":guilabel:`Certification Template` field and then choose an :guilabel:`Email" +" Template`. When a participant passes the certification with the required " +"score, an email from Odoo will automatically be sent to that person using " +"the selected email template." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:165 +msgid "" +"If the :guilabel:`Give Badge` feature is enabled and the " +":guilabel:`Certification Badge` is set, the survey participant also receives" +" a badge upon passing the certification." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:169 +#: ../../content/applications/marketing/surveys/time_random.rst:48 +msgid ":doc:`scoring`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:172 +msgid "Candidates" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:174 +msgid "" +"To determine access to the survey, the :guilabel:`Access Mode` has two " +"options to choose between: :guilabel:`Anyone with the link` and " +":guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:177 +msgid "" +"Below the :guilabel:`Appraisal Managers Only` checkbox is the " +":guilabel:`Login Required` option to require a login to participate in the " +"survey. If this option is activated, an :guilabel:`Attempts Limit` field " +"also populates, in which the number of survey attempts is defined for the " +"participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:182 +msgid "Live Session" +msgstr "ไลฟ์เซสชัน" + +#: ../../content/applications/marketing/surveys/create.rst:184 +msgid "" +"The :guilabel:`Live Session` section is dedicated to users who are " +"conducting surveys in real-time, wherein they directly engage with and " +"collect answers from a live audience." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:187 +msgid "" +"Customize the :guilabel:`Session Code` here; this code is needed for " +"participants to access the live session survey. Reward participants for " +"quick answers by selecting the checkbox labeled :guilabel:`Reward quick " +"answers`. By checking it, attendees will get more points if they answer " +"quickly." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:193 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:195 +msgid "" +"Back on the main survey template page is the :guilabel:`Description` tab, " +"where a custom description of the survey can be added. This is displayed " +"beneath the title on the survey's homepage, which is on the front end of the" +" website made through the Odoo :guilabel:`Website` app." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:200 +msgid "Test and share the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:202 +msgid "" +"Once the survey is created and saved, run a test to check for possible " +"errors before finally sending it out to the participants by clicking " +":guilabel:`Test` in the upper left corner of the survey template page." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:206 +msgid "" +"When activated, Odoo redirects the page to a test version of the survey on " +"the front end of the website. This page displays how the survey will look to" +" participants. Proceed to run through the survey, like a normal participant," +" to check for errors." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:210 +msgid "" +"To return to the survey template form in the backend, simply click the " +":guilabel:`This is a test survey. Edit Survey` link in the blue banner along" +" the top of the page. Once Odoo redirects the page to the survey template in" +" the backend, make any further changes, as needed, before officially sending" +" the survey out to participants." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:215 +msgid "" +"When the survey is ready to be shared with the audience, click the " +":guilabel:`Start Survey` button in the upper-left corner of the survey " +"template form. Then, click :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:218 +msgid "" +"In the pop-up window, add the survey recipients in the " +":guilabel:`Recipients` field (for existing contacts in the Odoo database) or" +" the :guilabel:`Additional emails` field (for contacts that do not want to " +"be listed in the Odoo database). Finally, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:222 +msgid "" +"As answers are received, check them by clicking the :guilabel:`Answers` " +"smart button on the survey template form, or the :guilabel:`See Results` " +"button in the upper left corner. To end the survey, click the " +":guilabel:`Close` button on the survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:3 +msgid "Scoring surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:5 +msgid "" +"To measure a survey participant's performance, knowledge, or overall " +"satisfaction, Odoo ascribes points to survey answers. At the end of the " +"survey, these points are summed up, resulting in the participant's final " +"score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:9 +msgid "" +"To add points to questions, open the :guilabel:`Surveys` application, choose" +" the desired survey form, and then click on the :guilabel:`Options` tab. " +"Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring " +"with answers at the end` or :guilabel:`Scoring without answers at the end`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:14 +msgid "" +":guilabel:`Scoring with answers at the end` shows the survey participant " +"their answers after completing the survey, and displays which questions they" +" got right or wrong. On questions where there was an incorrect answer, the " +"correct answer will be highlighted." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:18 +msgid "" +":guilabel:`Scoring without answers at the end` does not show the survey " +"participant their answer choices after completing the survey, only their " +"final score." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:21 +msgid "" +"To indicate correct answers, click on the :guilabel:`Questions tab` and " +"choose a question. In the question form, check the :guilabel:`Is a correct " +"answer` box for the choice that is the correct answer and attach a score " +"value." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:25 +msgid "" +"Back on the :guilabel:`Options` tab of the survey, set the " +":guilabel:`Success %`. The percentage entered determines what percentage of " +"correct answers is needed to pass the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:28 +msgid "" +"Further on the :guilabel:`Options` tab of the survey, survey administrators " +"can also choose to make the survey a certification. A certification " +"indicates that the survey asks questions to test the participants' knowledge" +" level on a subject." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:32 +msgid "" +"When enabling the :guilabel:`Is a certification` option, choose a " +":guilabel:`Certification email template`. The certification will " +"automatically be emailed using this email template to users who pass the " +"survey with a final score that is greater than or equal to the set " +":guilabel:`Success %`." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:36 +msgid "" +"In the :guilabel:`Candidates` section, participants can be required to log " +"in to take the survey. If the :guilabel:`Login Required` setting is enabled," +" two new options appear: the :guilabel:`Attempts Limit` checkbox, which " +"limits the number of times a participant can attempt the survey, and the " +"option to :guilabel:`Give Badge`, located beneath the " +":guilabel:`Certification` options in the :guilabel:`Scoring` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "" +"Setting the Required Score (percentage), login required, and certification " +"template." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst:46 +msgid "" +"Badges are displayed on the eLearning portion of a given user's portal, and " +"are a way to set milestones and reward participants for passing surveys or " +"gaining points. Besides the awardee, website visitors who access the " +":guilabel:`Courses` page will also be able to see the granted badges." +msgstr "" + +#: ../../content/applications/marketing/surveys/scoring.rst-1 +msgid "Example of how a badge looks on the eLearning portion of the website." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:3 +msgid "Timed and randomized questions" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:5 +msgid "" +"When creating a survey in Odoo, there are options to set a time limit on the" +" survey and randomize the questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:9 +msgid "Time limit" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:11 +msgid "" +"During a timed survey, participants must finish the survey within a " +"specified period of time. A common use case for implementing a time limit is" +" that it greatly reduces the chance of participants looking up responses via" +" external resources (e.g. web search), and reduces the survey to a \"closed " +"book\" testing environment." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:16 +msgid "" +"Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` " +"tab of the survey form, under the :guilabel:`Questions` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Time limit field in the options tab of a survey template form." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:23 +msgid "" +"When the :guilabel:`Survey Time Limit` option is checked, a timer will be " +"displayed on every page of the survey, letting participants keep track of " +"the time remaining while the survey is active." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:27 +msgid "" +"Participants that do not submit their survey by the preconfigured time limit" +" will *not* have their answers saved." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:31 +msgid "Randomized selection" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:33 +msgid "" +"When a survey is randomized, Odoo shuffles the questions and reveals them in" +" a random order every time a participant begins the questionnaire. Using " +"randomization as a survey method discourages participants from looking at " +"each other's responses, and helps control for individual testing." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:37 +msgid "" +"To randomize a survey, click the :guilabel:`Options` tab on the survey form." +" In the :guilabel:`Questions` section, select :guilabel:`Randomized per " +"section` for the :guilabel:`Selection` field. After enabling, navigate to " +"the :guilabel:`Questions` tab and look in the :guilabel:`Random questions " +"count` column. From there, determine how many questions (per section) Odoo " +"should select and display during the shuffling of questions." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst-1 +msgid "Randomized question count in the questions tab of a survey." +msgstr "" diff --git a/locale/th/LC_MESSAGES/productivity.po b/locale/th/LC_MESSAGES/productivity.po new file mode 100644 index 000000000..16e99064e --- /dev/null +++ b/locale/th/LC_MESSAGES/productivity.po @@ -0,0 +1,10210 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wichanon Jamwutthipreecha, 2024 +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/productivity.rst:5 +msgid "Productivity" +msgstr "ผลิตผล" + +#: ../../content/applications/productivity/calendar.rst:5 +#: ../../content/applications/productivity/studio/views.rst:201 +msgid "Calendar" +msgstr "ปฏิทิน" + +#: ../../content/applications/productivity/calendar/google.rst:3 +msgid "Synchronize Google calendar with Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:5 +msgid "" +"Synchronize Google Calendar with Odoo to see and manage meetings from both " +"platforms (updates go in both directions). This integration helps organize " +"schedules, so a meeting is never missed." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:9 +msgid ":doc:`/applications/general/auth/google`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:10 +msgid ":doc:`/administration/maintain/google_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:13 +msgid "Setup in Google" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:16 +msgid "Select (or create) a project" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:18 +msgid "" +"Create a new Google API project and enable the Google Calendar API. First, " +"go to the `Google API Console <https://console.developers.google.com>`_ and " +"log into the Google account." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:22 +msgid "" +"If this is the first time visiting this page, Google will prompt the user to" +" enter a country and agree to the Terms of Service. Select a country from " +"the drop-down list and agree to the :abbr:`ToS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:26 +msgid "" +"Next, click :guilabel:`Select a project` and select (or create) an API " +"project to configure OAuth in, and store credentials. Click :guilabel:`New " +"Project`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Create a new API project to store credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:34 +msgid "" +"Give the API Project a clear name, like \"Odoo Sync\", so it can be easily " +"identified." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:37 +msgid "Enable Google calendar API" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:39 +msgid "" +"Now, click on :guilabel:`Enabled APIs and Services` in the left menu. Select" +" :guilabel:`Enabled APIs and Services` again if the :guilabel:`Search bar` " +"doesn't appear." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable APIs and Services on the API Project." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:46 +msgid "" +"After that, search for `Google Calendar API` using the search bar and select" +" :guilabel:`Google Calendar API` from the search results. Click " +":guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Enable the Google Calendar API." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:54 +msgid "OAuth consent screen" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:56 +msgid "" +"Now that the API project has been created, OAuth should be configured. To do" +" that, click on :guilabel:`OAuth consent` in the left menu and then select " +"the :guilabel:`User Type`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:60 +msgid "" +"*Personal* Gmail Accounts are only allowed to be **External** User Type, " +"which means Google may require an approval, or for *Scopes* to be added on. " +"However, using a *Google WorkSpace* account allows for **Internal** User " +"Type to be used." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:64 +msgid "" +"Note, as well, that while the API connection is in the *External* testing " +"mode, then no approval is necessary from Google. User limits in this testing" +" mode is set to 100 users." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:67 +msgid "" +"In the second step, :guilabel:`OAuth Consent Screen`, type `Odoo` in the " +":guilabel:`App name` field, select the email address for the :guilabel:`User" +" support email` field, and type the email address for the " +":guilabel:`Developer contact information` section. Then, click " +":guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:72 +msgid "" +"Skip the third step, :menuselection:`Scopes`, by clicking :guilabel:`Save " +"and Continue`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:74 +msgid "" +"Next, if continuing in testing mode (External), add the email addresses " +"being configured under the :guilabel:`Test users` step, by clicking on " +":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " +"summary of the app registration appears." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:78 +msgid "" +"Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:80 +msgid "" +"Now, the OAuth consent has been configured, and it's time to create " +"credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:83 +msgid "Create credentials" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:85 +msgid "" +"The *Client ID* and the *Client Secret* are both needed to connect Google " +"Calendar to Odoo. This is the last step in the Google console. Begin by " +"clicking :guilabel:`Credentials` in the left menu. Then, click " +":guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, " +"Google will open a guide to create credentials." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:90 +msgid "" +"Under :menuselection:`Create OAuth Client ID`, select :guilabel:`Website " +"application` for the :guilabel:`Application Type` field, and type `My Odoo " +"Database` for the :guilabel:`Name`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:93 +msgid "" +"Under the :guilabel:`Authorized JavaScript Origins` section, click " +":guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform " +"Resource Locator)` address." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:95 +msgid "" +"Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ " +"Add URI` and type the company's Odoo :abbr:`URL (Uniform Resource Locator)` " +"address followed by `/google_account/authentication`. Finally, click " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Add the authorized JavaScript origins and the authorized redirect URIs." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:103 +msgid "" +"A :guilabel:`Client ID` and :guilabel:`Client Secret` will appear, copy " +"these to a notepad." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:106 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:108 +msgid "" +"Once the *Client ID* and the *Client Secret* are located, open the Odoo " +"database and go to :menuselection:`Settings --> General Settings --> " +"Integrations --> Google Calendar`. Check the box next to :guilabel:`Google " +"Calendar`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "The Google Calendar checkbox in General Settings." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:116 +msgid "" +"Next, copy and paste the *Client ID* and the *Client Secret* from the Google" +" Calendar API credentials page into their respective fields below the " +":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:121 +msgid "Sync calendar in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:123 +msgid "" +"Finally, open the :menuselection:`Calendar` app in Odoo and click on the " +":guilabel:`Google` sync button to sync Google Calendar with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "" +"Click the Google sync button in Odoo Calendar to sync Google Calendar with " +"Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:131 +msgid "" +"When syncing Google Calendar with Odoo for the first time, the page will " +"redirect to the Google Account. From there, select the :guilabel:`Email " +"Account` that should have access, then select :guilabel:`Continue` (should " +"the app be unverifed), and finally select :guilabel:`Continue` (to give " +"permission for the transfer of data)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst-1 +msgid "Give Odoo permission to access Google Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:140 +msgid "Now, Odoo Calendar is successfully synced with Google Calendar!" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:143 +msgid "" +"Odoo highly recommends testing the Google calendar synchronization on a test" +" database and a test email address (that is not used for any other purpose) " +"before attempting to sync the desired Google Calendar with the user's " +"production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:147 +msgid "Once a user synchronizes their Google calendar with the Odoo calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:149 +msgid "" +"Creating an event in Odoo causes Google to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:150 +msgid "" +"Deleting an event in Odoo causes Google to send a cancellation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:151 +msgid "" +"Adding a contact to an event causes Google to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:152 +msgid "" +"Removing a contact from an event causes Google to send a cancellation to all" +" event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:154 +msgid "" +"Events can be created in Google Calendar without sending a notification by " +"selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:3 +msgid "Outlook Calendar synchronization" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:5 +msgid "" +"Synchronizing a user's Outlook Calendar with Odoo is useful for keeping " +"track of their tasks and appointments across all related applications." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:9 +msgid ":doc:`/applications/general/auth/azure`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:10 +msgid ":doc:`/administration/maintain/azure_oauth`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:13 +msgid "Register the application with Microsoft Azure" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:15 +msgid "" +"To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account" +" is needed. Creating an account is free for users who have never tried or " +"paid for Azure. For more information, `click here " +"<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:19 +msgid "" +"Refer to `Microsoft's documentation <https://docs.microsoft.com/en-" +"us/azure/active-directory/ develop/quickstart-create-new-tenant>`_ on how to" +" set up an Microsoft Entra ID (formally called *Microsoft Azure Active " +"Directory (Azure AD)*), which is a representation of an organization to " +"manage and register apps." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:24 +msgid "" +"Then, `Register an Application <https://docs.microsoft.com/en-" +"us/azure/active-directory/develop/ quickstart-register-app>`_, choosing the " +"appropriate :guilabel:`Supported account type`. Users who wish to connect " +"their Outlook calendar to Odoo should select the :guilabel:`Accounts in any " +"organizational directory (Any Microsoft Entra ID directory - Multitenant) " +"and personal Microsoft accounts (e.g. Skype, Xbox)` option for " +":guilabel:`Supported account types`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:30 +msgid "" +"When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and " +"copy the Odoo database URI (URL) followed by " +"`/microsoft_account/authentication`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:34 +msgid "" +"Enter `https://www.companyname.odoo.com/microsoft_account/authentication` " +"for the :guilabel:`Redirect URI`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "" +"The \"Supported account type\" and \"Redirect URI\" settings in the " +"Microsoft Entra ID portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:41 +msgid "" +"For more information on the restrictions and limitations of URIs, `check " +"this page <https://docs. microsoft.com/en-us/azure/active-" +"directory/develop/reply-url>`_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:44 +msgid "" +"Regarding the application credentials, the user *must* add a client secret, " +"which allows Odoo to authenticate itself, requiring no interaction from the " +"user's side. :guilabel:`Certificates` are optional." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:48 +msgid "" +"To do add a client secret, click :guilabel:`Add a certificate or secret` and" +" then click :guilabel:`New client secret`. Next, type a " +":guilabel:`Description` and select when the client secret " +":guilabel:`Expires`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:52 +msgid "" +"Since resetting the synchronization can be tricky, Odoo recommends setting " +"the maximum allowed expiration date for the client secret (24 months), so " +"there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to " +"generate the client secret (:guilabel:`Secret ID`)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:57 +msgid "Configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:59 +msgid "" +"In the Odoo database, go to :menuselection:`Settings --> General Settings " +"--> Integrations` and activate the :guilabel:`Outlook Calendar` setting." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook Calendar\" setting activated in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:66 +msgid "" +"From the Microsoft Azure portal, under the :guilabel:`Overview` section of " +"the application, copy the :guilabel:`Application (Client) ID`, and paste it " +"into the :guilabel:`Client ID` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client ID\" in the Microsoft Azure portal." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:73 +msgid "" +"In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` " +"section, copy the :guilabel:`Client Secret Value` and paste it into the " +":guilabel:`Client Secret` field in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:80 +msgid "" +"Finally, on the Odoo :menuselection:`Settings --> General Settings` page, " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:85 +msgid "Sync with Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:89 +msgid "" +"Odoo highly recommends testing the Outlook calendar synchronization on a " +"test database and a test email address (that is not used for any other " +"purpose) before attempting to sync the desired Outlook Calendar with the " +"user's production database." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:93 +msgid "" +"If the user has any past, present, or future events on their Odoo calendar " +"before syncing their Outlook calendar, Outlook will treat the events pulled " +"from Odoo's calendar during the sync as new events, causing an email " +"notification to be sent from Outlook to all the event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:97 +msgid "" +"To avoid unwanted emails being sent to all past, present, and future event " +"attendees, the user must add the events from the Odoo calendar to the " +"Outlook calendar before the first ever sync, delete the events from Odoo, " +"and then start the sync." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:101 +msgid "" +"Even after synchronizing the Odoo Calendar with the Outlook calendar, " +"Outlook will still send a notification to all event participants every time " +"an event is edited (created, deleted, unarchived, or event date/time " +"changed), with no exceptions. This is a limitation that cannot be fixed from" +" Odoo's side." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:106 +msgid "" +"In summary, once a user synchronizes their Outlook calendar with the Odoo " +"calendar:" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:108 +msgid "" +"Creating an event in Odoo causes Outlook to send an invitation to all event " +"attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:109 +msgid "" +"Deleting an event in Odoo causes Outlook to send a cancellation to all event" +" attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:110 +msgid "" +"Unarchiving an event in Odoo causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:111 +msgid "" +"Archiving an event in Odoo causes Outlook to send a cancellation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:112 +msgid "" +"Adding a contact to an event causes Outlook to send an invitation to all " +"event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:113 +msgid "" +"Removing a contact from an event causes Outlook to send a cancellation to " +"all event attendees." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:116 +msgid "Sync Odoo Calendar and Outlook" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:118 +msgid "" +"In the Odoo database, go to the :guilabel:`Calendar` module and click the " +":guilabel:`Outlook` sync button. The page will redirect to a Microsoft login" +" page, and the user is asked to log in to their account, if they are not " +"already, and grant the required permissions." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst-1 +msgid "The \"Outlook\" sync button in Odoo Calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:126 +msgid "" +"The synchronization is a two-way process, meaning that events are reconciled" +" in both accounts (Outlook and Odoo)." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:130 +msgid "" +"All users that want to use the synchronization simply need to :ref:`sync " +"their calendar with Outlook <outlook/sync>`. The configuration of " +"Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' " +"Client IDs and Client Secrets are unique, and represent an organization that" +" helps the user to manage a specific instance of Microsoft cloud services " +"for their internal and external users." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:137 +msgid ":doc:`../mail_plugins/outlook`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:138 +msgid ":doc:`google`" +msgstr "" + +#: ../../content/applications/productivity/discuss.rst:8 +msgid "Discuss" +msgstr "การสนทนา" + +#: ../../content/applications/productivity/discuss/advanced.rst:5 +msgid "Advanced" +msgstr "ระดับสูง" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:3 +msgid "Configure ICE servers with Twilio" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:5 +msgid "" +"Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and " +"video calls. If one of the call attendees is behind a symmetric NAT, you " +"need to configure an ICE server to establish a connection to the call " +"attendee. To set up an ICE server, first, create a Twilio account for video " +"calls, and then, connect that Twilio account to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:11 +msgid "Create a Twilio account" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13 +msgid "" +"First, go to `Twilio <https://www.twilio.com>`_ and click :guilabel:`Sign " +"up` to create a new Twilio account. Next, enter your name and email address," +" create a password, and accept Twilio's terms of service. Then, click " +":guilabel:`Start your free trial`. Verify your email address with Twilio, as" +" per their instructions." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 +msgid "" +"Next, enter your phone number into Twilio. Then, Twilio will send you an SMS" +" text message containing a verification code. Enter the verification code " +"into Twilio to verify your phone number." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:22 +msgid "" +"After that, Twilio redirects to a welcome page. Use the following list to " +"answer Twilio's questions:" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:25 +msgid "" +"For :guilabel:`Which Twilio product are you here to use?`, select " +":guilabel:`Video`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:26 +msgid "" +"For :guilabel:`What do you plan to build with Twilio?`, select " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:27 +msgid "" +"For :guilabel:`How do you want to build with Twilio?`, select " +":guilabel:`With no code at all`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:28 +msgid "" +"For :guilabel:`What is your goal today?`, select :guilabel:`3rd party " +"integrations`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The Twilio welcome page." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34 +msgid "" +"If necessary, change the billing country. Finally, click :guilabel:`Get " +"Started with Twilio`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:37 +msgid "Locate the Twilio Account SID and Auth Token" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:39 +msgid "" +"To locate the Account SID and Auth Token, go to the Twilio account " +"dashboard. Then, click :guilabel:`Develop` on the sidebar. In the " +":guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the" +" :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "" +"The Twilio Account SID and Auth Token can be found uner the Account Info " +"section." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49 +msgid "Connect Twilio to Odoo" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:51 +msgid "" +"Open the Odoo database and go to :menuselection:`Settings --> General " +"Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE " +"servers` and enter the Twilio account's :guilabel:`Account SID` and " +":guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these " +"changes." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61 +msgid "Define a list of custom ICE servers" +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:63 +msgid "" +"This step is not required for the Twilio configuration. However, if Twilio " +"is not configured or is not working at any given moment, Odoo will fall back" +" on the custom ICE servers list. The user must define the list of custom ICE" +" servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:67 +msgid "" +"In :menuselection:`Settings --> General Settings --> Discuss`, click the " +":guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE Servers\" button in Odoo General Settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74 +msgid "" +"Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define " +"your own list of ICE servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst-1 +msgid "The \"ICE servers\" page in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:82 +msgid "" +"For on-premise instances of Odoo, the package `python3-gevent` is necessary " +"for the Discuss module to run calls/video calls on Ubuntu (Linux) servers." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview.rst:5 +msgid "Overview" +msgstr "ภาพรวม" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:3 +msgid "Get started with Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:5 +msgid "" +"Odoo *Discuss* is an internal communication app that allows users to connect" +" through messages, notes, and file sharing, either through a persistent chat" +" window that works across applications, or through the dedicated *Discuss* " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:12 +msgid "Choose notifications preference" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:14 +msgid "" +"Access user-specific preferences for the *Discuss* app by navigating to " +":menuselection:`Settings app --> Users --> User --> Preferences tab`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the Preferences tab for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:21 +msgid "" +"By default, the :guilabel:`Notification` field is set as :guilabel:`Handle " +"by Emails`. With this setting enabled, a notification email will be sent by " +"Odoo every time a message is sent from the chatter, a note is sent with an " +"`@` mention (from chatter), or a notification is sent for a record that the " +"user follows. Something that triggers a notification is changing of the " +"stage (if an email\\ is configured to be sent, for example if the task is " +"set to :guilabel:`Done`)." +msgstr "" +"ตามค่าเริ่มต้น ฟิลด์ :guilabel:`การแจ้งเตือน` จะถูกตั้งค่าเป็น " +":guilabel:`จัดการทางอีเมล` เมื่อเปิดใช้งานการตั้งค่านี้ Odoo " +"จะส่งอีเมลแจ้งเตือนทุกครั้งที่มีการส่งข้อความจากแชท " +"มีการส่งบันทึกพร้อมการกล่าวถึง `@` (จากแชท) " +"หรือส่งการแจ้งเตือนสำหรับบันทึกที่ผู้ใช้ติดตาม " +"สิ่งที่ทำให้เกิดการแจ้งเตือนกำลังเปลี่ยนแปลงขั้นตอน " +"(หากมีการกำหนดค่าอีเมลให้ส่ง เช่น หากงานตั้งค่าเป็น :guilabel:`เสร็จสิ้น`)" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:27 +msgid "" +"By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in" +" the *Discuss* app's *inbox*. Messages can have the following actions taken " +"on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or " +"reply to the message by clicking on :guilabel:`Reply`. Additional actions " +"may include starring the message by clicking :guilabel:`Marked as Todo`, or " +"pinning the message by selecting :guilabel:`Pin` or even mark the message as" +" unread by selecting :guilabel:`Marked as unread`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of an inbox message and its action options in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:38 +msgid "" +"Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the " +":guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the " +"message to :guilabel:`History`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of messages marked as todo in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:46 +msgid "Start chatting" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:48 +msgid "" +"The first time a user logs in to their account, OdooBot sends a message " +"asking for permission to send desktop notifications for chats. If accepted, " +"the user will receive push notifications on their desktop for the messages " +"they receive, regardless of where the user is in Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of the messages under the messaging menu emphasizing the request for push\n" +"notifications for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:58 +msgid "" +"To stop receiving desktop notifications, reset the notifications settings of" +" the browser." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:60 +msgid "" +"To start a chat, go to the :menuselection:`Discuss` app and click on the " +":guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or " +":guilabel:`Channels` in the left menu of the dashboard." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "" +"View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n" +"Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:69 +msgid "" +"A company can also easily create :doc:`public and private channels " +"</applications/productivity/discuss/overview/team_communication>`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:73 +msgid "Mentions in the chat and on the chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:75 +msgid "" +"To mention a user within a chat or the chatter, type `@user-name`; to refer " +"to a channel, type `#channel-name`. The user mentioned will be notified in " +"their *inbox* or through an email, depending on their communication " +"settings." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of a couple of chat window messages for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:84 +msgid "" +"When a user is mentioned, the search list (list of names) suggests values " +"first based on the task's followers, and secondly on employees. If the " +"record being searched does not match with either a follower or employee, the" +" scope of the search becomes all partners." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:89 +msgid "User status" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:91 +msgid "" +"It is helpful to see what colleagues are up to and how quickly they can " +"respond to messages by checking their *status*. The status is shown on the " +"left side of a contact's name on the :guilabel:`Discuss` sidebar, on the " +"*messaging menu* and when listed in the *chatter*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:95 +msgid "Green = online" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:96 +msgid "Orange = away" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 +msgid "White = offline" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 +msgid "Airplane = out of the office" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst-1 +msgid "View of the contacts' status for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:106 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:107 +msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 +msgid "Activities" +msgstr "กิจกรรม" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 +msgid "" +"*Activities* are follow-up tasks tied to a record in an Odoo database. " +"Activities can be scheduled on any page of the database that contains a " +"chatter thread, kanban view, list view, or activities view of an " +"application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 +msgid "" +"One way that activities are created is by clicking the :guilabel:`Schedule " +"Activity` button, located at the top of the *chatter* on any record. On the " +"pop-up window that appears, select an :guilabel:`Activity Type` from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 +msgid "" +"Enter a title for the activity in the :guilabel:`Summary` field, located in " +"the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 +msgid "" +"To assign the activity to a different user, select a name from the " +":guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the " +"activity is automatically assigned." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 +msgid "" +"Lastly, feel free to add any additional information in the optional " +":guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 +msgid "" +"The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up " +"window auto-populates based on the configuration settings for the selected " +":guilabel:`Activity Type`. However, this date can be changed by selecting a " +"day on the calendar in the :guilabel:`Due Date` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 +msgid "" +":guilabel:`Schedule`: adds the activity to the chatter under " +":guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 +msgid "" +":guilabel:`Mark as Done`: adds the details of the activity to the chatter " +"under :guilabel:`Today`. The activity is not scheduled, it is automatically " +"marked as completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 +msgid "" +":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` " +"marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 +msgid "" +"Depending on the activity type, the :guilabel:`Schedule` button may be " +"replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` " +"button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 +msgid "" +"Scheduled activities are added to the chatter for the record under " +":guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57 +msgid "" +"Activities can also be scheduled from the kanban, list, or activities view " +"of an application." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 +msgid "" +"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 " +"(clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill " +"out the pop-up form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 +msgid "List view" +msgstr "ดูล่าสุด" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72 +msgid "" +"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 " +"(clock)` icon, then :guilabel:`Schedule An Activity`. If the record already " +"has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 " +"(phone)` or an :guilabel:`✉️ (envelope)` icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 +msgid "Activity view" +msgstr "มุมมองกิจกรรม" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82 +msgid "" +"To open the activity view for an application, select the :guilabel:`🕘 " +"(clock)` icon from the menu bar anywhere in the database. Select any " +"application from the drop-down menu, and click the :guilabel:`🕘 (clock)` " +"icon for the desired app." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Activity menu drop down with focus on where to open activity view for CRM." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90 +msgid "" +"Select a record on which to schedule an activity. Move across the row to " +"find the desired activity type, then click the :guilabel:`＋ (plus sign)`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98 +msgid "" +"Activity colors, and their relation to an activity's due date, is consistent" +" throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 +msgid "" +"Activities that appear in **green** indicate a due date sometime in the " +"future." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 +msgid "**Yellow** indicates that the activity's due date is today." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 +msgid "" +"**Red** indicates that the activity is overdue and the due date has passed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 +msgid "" +"For example, if an activity is created for a phone call, and the due date " +"passes, the activity appears with a red phone in list view, and a red clock " +"on the kanban view." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 +msgid "View scheduled activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 +msgid "" +"To view scheduled activities, open either the :menuselection:`Sales app` or " +":menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located " +"to the far-right side of the other view options." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114 +msgid "" +"Doing so opens the activities menu, showcasing all the scheduled activities " +"for the user, by default. To show all activities for every user, remove the " +":guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118 +msgid "" +"To view a consolidated list of activities separated by the application where" +" they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on" +" the header menu to see the activities for that specific application in a " +"drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122 +msgid "" +"The possibility to :guilabel:`Add new note` and :guilabel:`Request a " +"Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘" +" (clock)` icon on the header menu is clicked." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of CRM leads page emphasizing the activities menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 +msgid "Configure activity types" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 +msgid "" +"To configure the types of activities in the database, go to " +":menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "View of the settings page emphasizing the menu activity types." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 +msgid "" +"To edit an existing activity type, select it from the list, then click " +":guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 +msgid "" +"At the top of a blank activity type form, start by choosing a " +":guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 +#: ../../content/applications/productivity/studio/automated_actions.rst:134 +msgid "Action" +msgstr "การดำเนินการ" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157 +msgid "" +"The *Action* field specifies the intent of the activity. Some actions " +"trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160 +msgid "" +"If :guilabel:`Upload Document` is selected, a link to upload a document is " +"added directly to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162 +msgid "" +"If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users " +"have the option to open their calendar to schedule a time for this activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 +msgid "" +"If :guilabel:`Request Signature` is selected, a link is added to the planned" +" activity in the chatter that opens a signature request pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 +msgid "" +"The actions available to select on an activity type vary, depending on the " +"applications currently installed in the database." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 +msgid "Default user" +msgstr "ผู้ใช้เริ่มต้น" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174 +msgid "" +"To automatically assign this activity to a specific user when this activity " +"type is scheduled, choose a name from the :guilabel:`Default User` drop-down" +" menu. If this field is left blank, the activity is assigned to the user who" +" creates the activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181 +msgid "" +"To include notes whenever this activity type is created, enter them into the" +" :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192 +msgid "" +"To automatically suggest, or trigger, a new activity after an activity has " +"been marked complete, the :guilabel:`Chaining Type` must be set." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198 +msgid "" +"In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next " +"Activity`. Upon doing so, the field underneath changes to: " +":guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to " +"select any activities to recommend as follow-up tasks to this activity type." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230 +msgid "" +"In the :guilabel:`Schedule` field, choose a default deadline for these " +"activities. To do so, configure a desired number of :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur " +":guilabel:`after completion date` or :guilabel:`after previous activity " +"deadline`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 +msgid "" +"This :guilabel:`Schedule` field information can be altered before the " +"activity is scheduled." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "Schedule activity popup with emphasis on recommended activities." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 +msgid "" +"If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest " +"Next Activity`, and has activities listed in the :guilabel:`Suggest` field, " +"users are presented with recommendations for activities as next steps." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 +msgid "" +"Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` " +"immediately launches the next activity once the previous one is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226 +msgid "" +"If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining " +"Type` field, the field beneath changes to: :guilabel:`Trigger`. From the " +":guilabel:`Trigger` field drop-down menu, select the activity that should be" +" launched once this activity is completed." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 +msgid "" +"Schedule new activity popup with emphasis on Done and launch next button." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244 +msgid "" +"When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger" +" Next Activity`, marking the activity as `Done` immediately launches the " +"next activity listed in the :guilabel:`Trigger` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249 +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:113 +msgid ":doc:`get_started`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 +msgid ":doc:`team_communication`" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 +msgid "Use channels for team communication" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:5 +msgid "" +"Use channels in the Odoo *Discuss* app to organize discussions between " +"individual teams, departments, projects, or any other group that requires " +"regular communication. With channels, employees can communicate inside " +"dedicated spaces within the Odoo database around specific topics, updates, " +"and latest developments having to do with the organization." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:11 +msgid "Public and private channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:13 +msgid "" +"A *Public* channel can be seen by everyone, while a *Private* one is only " +"visible to users invited to it. To create a new channel, navigate to the " +":menuselection:`Discuss` app, and then click on the :guilabel:`➕ (plus)` " +"icon next to the :guilabel:`Channels` heading in the left-side menu. After " +"typing the name of the channel, two selectable options will appear: The " +"first is a channel with a hashtag (`#`) to indicate that it is a public " +"channel; the second option is a channel with a lock icon (`🔒`) next to it, " +"to indicate that it is a private channel. Select the channel type that best " +"fits the communication needs." +msgstr "" +"ทุกคนสามารถดูช่อง *สาธารณะ* ได้ ในขณะที่ช่อง *ส่วนตัว* " +"จะปรากฏแก่ผู้ใช้ที่ได้รับเชิญเท่านั้น หากต้องการสร้างช่องใหม่ ให้ไปที่แอป " +":menuselection:`แชท` จากนั้นคลิกที่ไอคอน :guilabel:`➕ (บวก)` ถัดจากหัวข้อ " +":guilabel:`ช่อง` ในเมนูด้านซ้าย หลังจากพิมพ์ชื่อช่องแล้ว " +"ตัวเลือกที่เลือกได้สองรายการจะแสดงขึ้น: ช่องแรกคือช่องที่มีแฮชแท็ก (`#`) " +"เพื่อระบุว่าเป็นช่องสาธารณะ ตัวเลือกที่สองคือช่องที่มีไอคอนล็อค (`🔒`) " +"อยู่ข้างๆ เพื่อระบุว่าเป็นช่องส่วนตัว " +"เลือกประเภทช่องสัญญาณที่เหมาะกับความต้องการด้านการสื่อสารมากที่สุด" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of discuss's sidebar and a channel being created in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:26 +msgid "" +"A public channel is best used when many employees need to access information" +" (such as company announcements), whereas a private channel could be used " +"whenever information should be limited to specific groups (such as a " +"specific department)." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:31 +msgid "Configuration options" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:33 +msgid "" +"The channel's :guilabel:`Group Name`, :guilabel:`Description`, and " +":guilabel:`Privacy` settings can be modified by clicking on the channel's " +"settings, represented by a :guilabel:`⚙️ (gear)` icon in the left sidebar " +"menu, next to the channel's name." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel's settings form in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:42 +msgid "Privacy and Members tabs" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:44 +msgid "" +"Changing :guilabel:`Who can follow the group's activities?` controls which " +"groups can have access to the channel." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:48 +msgid "" +"Allowing :guilabel:`Everyone` to follow a private channel lets other users " +"view and join it, as they would a public one." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:51 +msgid "" +"When choosing :guilabel:`Invited people only`, specify in the " +":guilabel:`Members` tab which members should be invited. Inviting members " +"can also be done from the *Discuss* app's main dashboard, by selecting the " +"channel, clicking the *add user* icon in the top-right corner of the " +"dashboard, and finally clicking :guilabel:`Invite to Channel` once all the " +"users have been added." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of Discuss' option to invite members in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:60 +msgid "" +"When the :guilabel:`Selected group of users` option is selected, it reveals " +"the ability to add an :guilabel:`Authorized Group`, along with the options " +"to :guilabel:`Auto Subscribe Groups` and :guilabel:`Auto Subscribe " +"Departments`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:64 +msgid "" +"The option to :guilabel:`Auto Subscribe Groups` automatically adds users of " +"that particular user group as followers. In other words, while " +":guilabel:`Authorized Groups` limits which users can access the channel, " +":guilabel:`Auto Subscribe Groups` automatically adds users as members as " +"long as they are part of a specific user group. The same is true for " +":guilabel:`Auto Subscribe Departments`." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:70 +msgid "Quick search bar" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:72 +msgid "" +"Once at least 20 channels, direct messages, or live chat conversations (if " +"*Live Chat* module is installed on the database) are pinned in the sidebar, " +"a :guilabel:`Quick search…` bar is displayed. This feature is a convenient " +"way to filter conversations and quickly find relevant communications." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"View of the Discuss' sidebar emphasizing the quick search bar in Odoo " +"Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:81 +msgid "Finding channels" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:83 +msgid "" +"Click on the settings :guilabel:`⚙️ (gear)` icon, located in the left " +"sidebar, to the right of the :guilabel:`CHANNELS` collapsible menu item. " +"Doing so will lead to a mosaic view containing all the public channels " +"available. Users can join or leave channels on this screen by clicking the " +":guilabel:`JOIN` or :guilabel:`LEAVE` buttons that appear in the channel " +"boxes." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:88 +msgid "" +"There is also the ability to apply filtering criteria and save them for " +"later use. The :guilabel:`Search...` function accepts wildcards by using the" +" underscore character [ `_` ], and specific searches can be saved by using " +"the :menuselection:`Favorites --> Save Current Search` drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "View of a channel being searched through filters in Odoo Discuss" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:98 +msgid "Linking channel in chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:100 +msgid "" +"Channels can be linked in the chatter (log note) of a record in Odoo. To do " +"so, simply type: `#` and the channel name. Click or press enter on the " +"*channel* name. Upon logging the note a link to the channel will appear. " +"After clicking on the link a chat window with the channel conversation will " +"pop up in the lower right corner of the screen." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:105 +msgid "" +"Users are able to contribute to this group channel (either public or member " +"based) by typing messages in window and pressing *enter*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 +msgid "" +"Channel linked in chatter with the channel open on the lower right quadrant." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/team_communication.rst:114 +msgid ":doc:`plan_activities`" +msgstr "" + +#: ../../content/applications/productivity/iot.rst:8 +msgid "Internet of Things (IoT)" +msgstr "Internet of Things (IoT)" + +#: ../../content/applications/productivity/iot.rst:17 +msgid "" +"The Open Platform Communications (OPC) Unified Architecture (UA) protocol is" +" now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open" +" Platform Communications)` :abbr:`UA (United Architecture)` is an open " +"standard that specifies information exchange for industrial communication on" +" devices, between machines and between systems. This includes communication " +"between information technology and operational technology. :abbr:`OPC (Open " +"Platform Communications)` :abbr:`UA (United Architecture)` can be used with " +"any software platform, on a wide variety of devices, and deployed securely. " +"The :abbr:`IoT (Internet of Things)` box has entered the world of the " +"Industry 4.0 standard and can be utilized in a wide variety of industries, " +"and for things like building automation, packaging, utilities, etc." +msgstr "" +"ขณะนี้โปรโตคอล Open Platform Communications (OPC) Unified Architecture (UA) " +"ได้รับการสนับสนุนโดยกล่อง :abbr:`IoT (Internet of Things)` :abbr:`OPC (Open " +"Platform Communications)` :abbr:`UA (United Architecture)` " +"เป็นมาตรฐานเปิดที่ระบุการแลกเปลี่ยนข้อมูลสำหรับการสื่อสารทางอุตสาหกรรมบนอุปกรณ์" +" ระหว่างเครื่องจักร และระหว่างระบบ " +"ซึ่งรวมถึงการสื่อสารระหว่างเทคโนโลยีสารสนเทศและเทคโนโลยีการดำเนินงาน " +":abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` " +"สามารถใช้กับแพลตฟอร์มซอฟต์แวร์ใดก็ได้ บนอุปกรณ์ที่หลากหลาย " +"และปรับใช้อย่างปลอดภัย กล่อง :abbr:`IoT (Internet of Things)` " +"ได้เข้าสู่โลกของมาตรฐานอุตสาหกรรม 4.0 " +"และสามารถนำมาใช้ในอุตสาหกรรมที่หลากหลาย และสำหรับสิ่งต่างๆ เช่น " +"ระบบอัตโนมัติในอาคาร บรรจุภัณฑ์ สาธารณูปโภค และอื่นๆ" + +#: ../../content/applications/productivity/iot/config.rst:5 +#: ../../content/applications/productivity/mail_plugins/outlook.rst:10 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/productivity/iot/config/connect.rst:3 +msgid "Connect an IoT box to Odoo" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:5 +msgid "" +"An Internet of Things (IoT) box is a micro-computer device that allows for " +"the connection of input and output devices to an Odoo database. An " +":abbr:`IoT (Internet of Things)` box subscription is required in order to " +"use the :abbr:`IoT (Internet of Things)` box with a secured connection. A " +"computer is also required to set up the :abbr:`IoT (Internet of Things)` " +"box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:11 +msgid "`IoT Box FAQ <https://www.odoo.com/app/iot-faq>`_" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:13 +msgid "" +"Begin the :abbr:`IoT (Internet of Things)` configuration process by " +":ref:`installing the IoT app <general/install>` on the Odoo database through" +" the :menuselection:`Apps` application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The Internet of Things (IoT) app on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:20 +msgid "" +"Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app " +"--> IoT Boxes`, and then click on the :guilabel:`Connect` button located in " +"the upper-left corner of the :menuselection:`IoT Boxes` dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connecting an IoT box to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:28 +msgid "" +"There are two recommended ways to connect the :abbr:`IoT (Internet of " +"Things)` box to the database once the *IoT app* is installed. Follow the " +"steps in either of the next two sections to connect the :abbr:`IoT (Internet" +" of Things)` box via :ref:`wired ethernet connection <iot_connect/ethernet>`" +" or via :ref:`WiFi <iot_connect/wifi>`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Connection steps for a wired connection or WiFi connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:38 +msgid "" +"The disk image that the :abbr:`IoT (Internet of Things)` box SD card is " +"formatted with is unique to the version of the Odoo database that the " +":abbr:`IoT (Internet of Things)` box is running on. Ensure that the " +":abbr:`IoT (Internet of Things)` box is :doc:`flashed <flash_sdcard>` with " +"the most up-to-date disk image." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:46 +msgid "Ethernet connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:48 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via an ethernet cable to the Odoo database (by way of the ethernet " +"port; RJ-45)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:51 +msgid "" +"First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box" +" (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, " +"an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of " +"Things)` box into a power source." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:55 +msgid "" +"Immediately after the unit powers on and boots up, read the *pairing code* " +"from the screen or from the printout of a receipt printer connected to the " +":abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:59 +msgid "" +"By default, the :abbr:`IoT (Internet of Things)` box will display the " +"*pairing code* for a maximum of 5 minutes after the unit boots up. After 5 " +"minutes, the *pairing code* will disappear for security purposes and the " +":abbr:`IoT (Internet of Things)` box will need to be rebooted manually by " +"unplugging the unit from the power source for ten seconds and re-plugging it" +" back in." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:65 +msgid "" +"If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then " +"the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)`" +" box homepage by clicking on the :guilabel:`POS Display` button. For " +"instructions on how to access the :abbr:`IoT (Internet of Things)` box " +"homepage visit :ref:`iot_connect/token`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:70 +msgid "" +"On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and " +"then click on the :guilabel:`Connect` button located in the upper-left " +"corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing " +"code* in the :guilabel:`Pairing Code` field and click on the " +":guilabel:`Pair` button. The database will now link to the :abbr:`IoT " +"(Internet of Things)` box and it will appear on the :menuselection:`IoT " +"Boxes` page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:81 +msgid "" +"The following is the process to connect the :abbr:`IoT (Internet of Things)`" +" box via a WiFi connection to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:84 +msgid "" +"First, ensure there is no ethernet cable plugged into the :abbr:`IoT " +"(Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT" +" (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, " +"etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:88 +msgid "" +"After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box " +"into to a power source. On the computer, navigate to :menuselection:`IoT app" +" --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in" +" the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then" +" copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as " +"this will later be used to link the Odoo database to the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:94 +msgid "" +"Back on the computer, navigate to the available WiFi networks and connect to" +" the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network " +"dispersed by the :abbr:`IoT (Internet of Things)` box will start with " +"`IoTBox-xxxxxxxxxx`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:102 +msgid "" +"Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser " +"will automatically redirect to the :menuselection:`Configure Iot Box` " +"wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the " +"previously copied *token* into the :guilabel:`Server Token` field, and then " +"click on :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:112 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't " +"start, then see the documentation on :ref:`connecting with a token " +"<iot_connect/token>`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:115 +msgid "" +"Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box " +"will connect with (enter the password if there is one) and click on " +":guilabel:`Connect`. Wait a few seconds and the browser will redirect to the" +" :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be " +"manually re-connected back to the original WiFi connection, if this does not" +" happen automatically." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:124 +msgid "" +"After completing each step, the :abbr:`IoT (Internet of Things)` box should " +"appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo" +" database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:132 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted " +"upon successfully connecting via WiFi for the box to appear in the *IoT app*" +" on the Odoo database. To do so, simply unplug the device and plug it back " +"into the power source after ten seconds." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:141 +msgid "" +"A manual connection of the :abbr:`IoT (Internet of Things)` box to the " +":abbr:`IoT (Internet of Things)` app can be made using the *token*, from a " +"computer. The *token* can be found by navigating to :menuselection:`IoT app " +"--> IoT Boxes` and clicking on :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:145 +msgid "" +"Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an " +"IoT Box` page that appears, click :guilabel:`Copy` to the right of the " +":guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet " +"of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:149 +msgid "" +"Access the :abbr:`IoT (Internet of Things)` box homepage by entering the " +":abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of " +"Things)` box into a browser window from a computer on the same network as " +"the :abbr:`IoT (Internet of Things)` box (preferably by ethernet " +"connection)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:154 +msgid "" +"The :abbr:`IP (Internet Protocol)` address can be accessed by the router " +"admin console that the :abbr:`IoT (Internet of Things)` box is connected to," +" or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` " +"box. A receipt will print out with the :abbr:`IoT (Internet of Things)` " +"box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:159 +msgid "" +"On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* " +"under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. " +"Then, paste the *token* into the :guilabel:`Server Token` field and click " +":guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link" +" to the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/productivity/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 +msgid "Flashing the SD card" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 +msgid "" +"In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD " +"Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT " +"(Internet of Things)` image update. This means that the Odoo :abbr:`IoT " +"(Internet of Things)` box software may need to be updated." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 +msgid "" +"Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to " +":menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP " +"address` of the :abbr:`IoT (Internet of Things)` box. Then click on " +":guilabel:`Update` (next to the version number)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 +msgid "" +"If a new version of the :abbr:`IoT (Internet of Things)` Box image is " +"available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the " +"bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT" +" (Internet of Things)` box will then flash itself to the new version. All of" +" the previous configurations will be saved." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 +msgid "" +"This process can take more than 30 minutes. Do not turn off or unplug the " +":abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent" +" state. This means that the :abbr:`IoT (Internet of Things)` box will need " +"to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "IoT box software upgrade in the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 +msgid "" +"A computer with a micro SD card reader/adapter is required in order to re-" +"flash the micro SD card." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 +msgid "" +"Navigate to Balena's website and download `Etcher " +"<https://www.balena.io/>`_. It's a free and open-source utility used for " +"burning image files onto drives. Click to `download " +"<https://www.balena.io/etcher#download-etcher>`_. Install and launch the " +"program on the computer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 +msgid "" +"Then download the version-specific :abbr:`IoT (Internet of Things)` image " +"from `nightly <http://nightly.odoo.com/master/iotbox/>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 +msgid "" +"The following are image versions on the `nightly " +"<http://nightly.odoo.com/master/iotbox/>`_ website with their corresponding " +"Odoo database version:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 +msgid "" +"The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 +msgid "" +"After this step is complete, insert the :abbr:`IoT (Internet of Things)` " +"box's micro SD card into the computer or reader. Open *Etcher* and select " +":guilabel:`Flash from file`, then find and select the image just downloaded " +"and extracted. Next, select the drive the image should be burned to. Lastly," +" click on :guilabel:`Flash` and wait for the process to finish." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 +msgid "" +"An alternative software for flashing the micro SD card is *Raspberry Pi " +"Imager*. Download the *Raspberry Pi* software `here " +"<https://www.raspberrypi.com/software/>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 +msgid "HTTPS certificate (IoT)" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 +msgid "What is HTTPS?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 +msgid "" +"*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of " +"*Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to " +"send data back and forth between a web browser and a website. :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` is encrypted in order to increase the " +"security of data transfer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption " +"protocol to encrypt communications. The protocol is called *Transport Layer " +"Security* (TLS), although formerly it was known as *Secure Sockets Layer* " +"(SSL)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 +msgid "" +":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the " +"transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure " +"Sockets Layer)` certificates, which verify that a particular provider is who" +" they say they are." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 +msgid "" +"In this documentation and throughout Odoo the term \"HTTPS certificate\" " +"will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` " +"certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 +msgid "Why is it needed?" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 +msgid "" +"In order to communicate with certain network devices (in particular for " +"payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol " +"Secure)` certificate isn't valid, some devices won't be able to interact " +"with the :abbr:`IoT (Internet of Things)` Box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 +msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 +msgid "" +"The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate is automatic." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 +msgid "" +"The :abbr:`IoT (Internet of Things)` Box will send a specific request to " +"`<https://www.odoo.com>`_ which will send back the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of " +"Things)` box and database are eligible." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 +msgid "Internet of Things (IoT) eligibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 +msgid "" +"The database should be a **production** instance. The database instance " +"should not be a copy, a duplicate, a staging, or a development environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 +msgid "The Odoo subscription must:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 +msgid "Have an :guilabel:`IoT Box Subscription` line." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 +msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 +msgid "" +"If the subscription is linked to a `<https://www.odoo.com>`_ portal user " +"check the information on the portal subscription page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 +msgid "" +"In this case, both subscriptions are considered \"in progress\" as the " +":guilabel:`Filter By\\: In Progress` was used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 +msgid "" +"If the subscription is in question, contact the database's Account Manager " +"or Partner regarding the matter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 +msgid "" +"Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate " +"errors" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 +msgid "" +"If anything goes wrong during the process of the \"HTTPS certificate\" " +"generation or reception, a specific error will code be given on the " +":abbr:`IoT (Internet of Things)` box home page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 +msgid "" +"Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for " +"the presence of the \"HTTPS certificate\" and will attempt its generation if" +" it is missing. As such, if there is an error on the :abbr:`IoT (Internet of" +" Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home " +"page to see if the error disappears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 +msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:132 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:149 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:166 +msgid "Reason:" +msgstr "เหตุผล:" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:87 +msgid "" +"The configuration regarding the server is missing. In other words, the Odoo " +"instance is not connected with the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:114 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:137 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:159 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 +msgid "Solution:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 +msgid "Ensure that the server is configured." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 +#: ../../content/applications/productivity/iot/config/windows_iot.rst:99 +msgid ":doc:`/applications/productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 +msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 +msgid "" +"An unhandled error happened when trying to read the existing :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 +msgid "" +"Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate file is readable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 +msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 +msgid "" +"The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is " +"missing." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 +msgid "" +"Ensure that both values are configured as intended. To modify them, go to " +"the :abbr:`IoT (Internet of Things)` box home page, and navigate to " +":guilabel:`Credential`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 +msgid "" +"An unexpected error happened when the :abbr:`IoT (Internet of Things)` box " +"tried to reach `<https://www.odoo.com>`_. The causes are likely due to the " +"network infrastructure/configuration:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 +msgid "" +"The :abbr:`IoT (Internet of Things)` box does not have access to internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 +msgid "" +"The network does not allow the :abbr:`IoT (Internet of Things)` box to " +"communicate with `<https://www.odoo.com>`_. This may be due to network " +"devices preventing the communication (firewalls, etc.) or the network " +"configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 +msgid "" +"More information regarding the error that occurred can be found in the full " +"request exception details, which are in the :abbr:`IoT (Internet of Things)`" +" box logs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure and goes beyond Odoo " +"support's service scope." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:140 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:143 +msgid "" +"The IoT-box was able to reach `<https://www.odoo.com>`_ but received an " +"unusual `HTTP response (status codes) <https://developer.mozilla.org/en-" +"US/docs/Web/HTTP/Status>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:147 +msgid "" +"This error code will also give the HTTP response status codes. For example, " +"if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the" +" page returned a 404 error, which is the \"Page Not Found\" code." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:152 +msgid "" +"Check if `<https://www.odoo.com>`_ is down using a web browser, as it's " +"possible that it is down due to maintenance." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:155 +msgid "" +"If `<https://www.odoo.com>`_ is down due to maintenance, unfortunately there" +" is nothing that can be done but instead wait for it to recover." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:157 +msgid "" +"If `<https://www.odoo.com>`_ is not down due to maintenance, open a `support" +" ticket <https://www.odoo.com/help>`_ on the matter. Ensure that the 3 " +"digits status code next to the code error is included in the support ticket." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:162 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:165 +msgid "" +"The :abbr:`IoT (Internet of Things)` box was able to reach " +"`<https://www.odoo.com>`_ but it refused to deliver the :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:169 +msgid "" +"Ensure that the :abbr:`IoT (Internet of Things)` box and database are " +"eligible for a certificate: :ref:`Internet of Things (IoT) eligibility " +"<iot/iot-eligibility>`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:173 +msgid "How to ensure that the HTTPS certificate is correct" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:175 +msgid "" +"If the certificate has been applied successfully, a new :abbr:`HTTPS " +"(Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)`" +" for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` " +"will appear on the Odoo database, inside of the :menuselection:`IoT` " +"application on that specific device's form." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:184 +msgid "" +"When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a" +" secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will " +"be established." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 +msgid "Example of valid SSL certificate details on the browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 +msgid "" +"Padlock in Chrome on Windows 10 attesting the fact that the connection is " +"secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:194 +msgid "" +"The IoT-box homepage will now display an `OK` status next to `HTTPS " +"certificate`. The drop-down menu icon, when clicked, will reveal information" +" regarding the certificate." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 +msgid "IoT box homepage with HTTPS certificate OK status." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:202 +msgid "Domain Name System (DNS) issue" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:204 +msgid "" +"If the :abbr:`IoT (Internet of Things)` box can be accessed from its " +":abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: " +"`.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely " +"running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it " +"will give an error code mentioning :abbr:`DNS (Domain Name System)` (like " +"`DNS_PROBE_FINISHED_NXDOMAIN`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:209 +msgid "" +"These :abbr:`DNS (Domain Name System)` issues may appear as the following in" +" different browsers:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:213 +msgid "Chrome" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:219 +msgid "DNS issue on Chrome browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:222 +msgid "Firefox" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:228 +msgid "DNS issue on Firefox browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:230 +msgid "Edge" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:236 +msgid "DNS issue on Edge browser on Windows 10." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:240 +msgid "Domain Name System (DNS) issue solution" +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:242 +msgid "" +"Should the router allow the :abbr:`DNS (Domain Name System)` to be manually " +"changed, change the DNS to use `Google DNS " +"<https://developers.google.com/speed/public-dns>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:244 +msgid "" +"If your router doesn't allow for this, then a change will need to be made on" +" the :abbr:`DNS (Domain Name System)` settings of each of the devices using " +"`Google DNS <https://developers.google.com/speed/public-dns>`_. This will " +"need to occur on **every** device that plans to interact with the :abbr:`IoT" +" (Internet of Things)` box (e.g. computer, tablet or phone). The individual " +"device configuration processes can be found on the website of the device's " +"manufacturer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:252 +msgid "" +"Other :abbr:`IoT (Internet of Things)` devices such as payment terminals " +"likely won't need their :abbr:`DNS (Domain Name System)` settings changed as" +" they are already configured with custom :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:257 +msgid "" +"Consult with your system or network administrator should this issue arise. " +"This error code depends on the network infrastructure, and it goes beyond " +"Odoo support's service scope." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:3 +msgid "Use an IoT box with a PoS" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:6 +msgid "Prerequisites" +msgstr "ข้อกำหนดเบื้องต้น" + +#: ../../content/applications/productivity/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:11 +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:12 +msgid "" +"Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* " +"applications installed." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:13 +msgid "" +"A local network set up with :abbr:`DHCP (Dynamic Host Configuration " +"Protocol)` (this is the default setting)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:15 +msgid "" +"An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already " +"built in)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:16 +msgid "" +"Any of the supported hardware (receipt printer, barcode scanner, cash " +"drawer, payment terminal, scale, customer display, etc.). The list of " +"supported hardware can be found on the `POS Hardware page " +"<https://www.odoo.com/page/point-of-sale-hardware>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:21 +msgid "Setup" +msgstr "ตั้งค่า" + +#: ../../content/applications/productivity/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:27 +msgid "" +"To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to" +" connect an :abbr:`IoT (Internet of Things)` box to the database. To do " +"this, follow these instructions: :doc:`Connect an Internet of Things (IoT) " +"box to the Odoo database <connect>`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:31 +msgid "" +"Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)`" +" box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:37 +msgid "Device Name" +msgstr "ชื่ออุปกรณ์" + +#: ../../content/applications/productivity/iot/config/pos.rst:38 +msgid "Instructions" +msgstr "คำแนะนำ" + +#: ../../content/applications/productivity/iot/config/pos.rst:39 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "เครื่องพิมพ์" + +#: ../../content/applications/productivity/iot/config/pos.rst:40 +msgid "" +"Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` " +"port or to the network, and power it on. Refer to " +":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:43 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:391 +msgid "Cash drawer" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:44 +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:45 +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:359 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:46 +msgid "" +"In order for the barcode scanner to be compatible it must end barcodes with " +"an `ENTER` character (keycode 28). This is most likely the default " +"configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:48 +msgid "Scale" +msgstr "เครื่องชั่ง" + +#: ../../content/applications/productivity/iot/config/pos.rst:49 +msgid "" +"Connect the scale and power it on. Refer to " +":doc:`/applications/productivity/iot/devices/scale`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:51 +msgid "Customer display" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:52 +msgid "" +"Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the " +":abbr:`PoS (Point of Sale)` order. Refer to " +":doc:`/applications/productivity/iot/devices/screen`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:54 +msgid "Payment terminal" +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:55 +msgid "" +"The connection process depends on the terminal. Refer to the :doc:`payment " +"terminals documentation " +"</applications/sales/point_of_sale/payment_methods>`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:58 +msgid "" +"Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to " +"the :menuselection:`PoS` application. To do this, go to " +":menuselection:`Point of Sale --> Configuration --> PoS`, tick the " +":guilabel:`IoT Box` option, and select the devices to be used in this " +":abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst-1 +msgid "Configuring the connected devices in the POS application." +msgstr "" + +#: ../../content/applications/productivity/iot/config/pos.rst:67 +msgid "" +"Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be " +"launched." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 +#: ../../content/applications/productivity/iot/config/windows_iot.rst:105 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 +msgid "IoT box connection" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 +msgid "Unable to locate the pairing code to connect the IoT box" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 +msgid "" +"The pairing code should be printed on receipt printers connected to the " +":abbr:`IoT (Internet of Things)` box and should also be displayed on " +"connected monitors." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 +msgid "The pairing code doesn't show under the following circumstances:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo " +"database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 +msgid "" +"The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 +msgid "" +"The code is only valid for 5 minutes after the :abbr:`IoT (Internet of " +"Things)` box has started. It's automatically removed from connected displays" +" when this time has expired." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 +msgid "" +"The version of the :abbr:`IoT (Internet of Things)` box image is too old. If" +" the :abbr:`IoT (Internet of Things)` box image is from an earlier version, " +"then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be" +" re-flashed to update the image (see :doc:`Flashing the SD Card " +"<flash_sdcard>`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 +msgid "" +"If none of the cases listed above correct the issue, then make sure that the" +" :abbr:`IoT (Internet of Things)` box has correctly started, by checking " +"that a fixed green LED is showing next to the power port." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it's not showing in the database" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 +msgid "" +"When an :abbr:`IoT (Internet of Things)` box connects to a database, it may " +"restart. If so, it can take up to five minutes before appearing in the " +"database. If the :abbr:`IoT (Internet of Things)` box is still not showing " +"after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box " +"can reach the database and that the server doesn't use a multi-database " +"environment." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 +msgid "" +"To access the database from the :abbr:`IoT (Internet of Things)` box, open a" +" browser and type in the database address." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 +msgid "" +"Make sure that the :abbr:`IoT (Internet of Things)` box and the computer " +"running the browser are located on the same network, as the :abbr:`IoT " +"(Internet of Things)` box cannot be reached from outside the local network." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate doesn't generate" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 +msgid "" +"In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " +"certificate, an IoT box subscription is required for the :abbr:`IoT " +"(Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` " +"box prior to configuring an :abbr:`IoT (Internet of Things)` subscription " +"for the database and :abbr:`IoT (Internet of Things)` box with the Account " +"Manager will result in an unsecured connection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 +msgid "" +"In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating correctly. In this " +"case, deactivate the firewall until the certificate is successfully " +"generated. It should also be noted that certain devices, such as a router " +"that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext " +"Transfer Protocol Secure)` certificate from generating." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) <https_certificate_iot>`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 +msgid "" +"If a printer doesn't show up in the devices list, go to the :abbr:`IoT " +"(Internet of Things)` box homepage and make sure that it is listed under " +":guilabel:`Printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 +msgid "" +"If the printer is not present on the :abbr:`IoT (Internet of Things)` box " +"homepage, click :guilabel:`Printers Server`, go to the " +":guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the " +"printer is not present in the list, it's likely not connected properly." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 +msgid "" +"For most printers, the correct driver should be automatically detected and " +"selected. However, in some cases, the automatic detection mechanism might " +"not be enough, and if no driver is found, the printer might print random " +"characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 +msgid "" +"The solution is to manually select the corresponding driver. On the " +":abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers " +"Server`, go to the :guilabel:`Printers` tab and select the printer in the " +"list. In the :guilabel:`Administration` dropdown, click on :guilabel:`Modify" +" Printer`. Follow the steps and select the *make* and *model* corresponding " +"to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 +msgid "" +"Epson and Star receipt printers and Zebra label printers do not need a " +"driver to work. Make sure that no driver is selected for those printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 +msgid "Epson configuration special case" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 +msgid "" +"Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of " +"Sale)` using the `GS v 0` command. However, the following Epson printer " +"models do not support this command:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 +msgid "TM-U220" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 +msgid "TM-U230" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 +msgid "TM-P60" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 +msgid "TMP-P60II" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:113 +msgid "" +"Bypass this issue by configuring the printer to use the `ESC *` command " +"instead." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:116 +msgid "Process to force ESC * command" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:119 +msgid "Epson printer compatibility" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 +msgid "" +"The first step is to check whether the printer is incompatible with `GS v 0`" +" command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:125 +msgid "" +"`Epson GS v 0 documentation <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php? content_id=94>`_ for `GS v 0` " +"compatible printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 +msgid "" +"`Epson ESC * documentation <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php ?content_id=88>`_ for `ESC *` " +"compatible printers." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:130 +msgid "" +"If the printer is not compatible with the `ESC *` command then the following" +" process is not possible. Should the printer be compatible to use the `ESC " +"*` command to print, follow this process to configure the printer with the " +":abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 +msgid "IoT box configuration for ESC *" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:137 +msgid "" +"To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` " +"command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by" +" navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the " +":guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of " +"Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:142 +msgid "**Choosing the printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:144 +msgid "" +"Now click on the :guilabel:`Printers server` button. This will redirect the " +"browser to the *CUPS* page. Next, go to :menuselection:`Administration --> " +"Printers --> Add Printer`, choose the printer that should be modified, and " +"then click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 +msgid "" +"If the name of the printer is still uncertain, take the following steps:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:151 +msgid "Take note of the listed printers on the *CUPS* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 +msgid "Turn the printer off and refresh the page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:153 +msgid "" +"Now compare the difference with the first list to see which printer " +"disappeared." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 +msgid "Turn the printer back on and refresh the page again." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:155 +msgid "Double-check the list again to see if the printer re-appears." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:156 +msgid "" +"The printer that disappeared and reappears again on the listed printers is " +"the name of the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:160 +msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:162 +msgid "**CUPS naming convention**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:164 +msgid "" +"`CUPS` will prompt the admin for three pieces of information: the " +":guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The " +"last two pieces of information do not need to be specific, however, the " +":guilabel:`Name` should follow a particular convention to work with the `ESC" +" *` command." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:169 +msgid "" +"The :guilabel:`Name` should match this convention: " +"`<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:172 +msgid "A breakdown of the naming convention:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:174 +msgid "" +"`printer_name`: This is the printer name. It can be any character as long as" +" it does not contain `_`, `/`, `#`, or ` ` (space character)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:176 +msgid "" +"`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC " +"*`)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 +msgid "`param_1`: This stands for the specific parameter:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:179 +msgid "" +"`SCALE<X>`: Scale of the picture (with the same aspect ratio). `X` should be" +" an integer describing the scale percentage that should be used." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:183 +msgid "" +"`100` is the original size, `50` is half the size, `200` is twice the size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:185 +msgid "" +"`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not" +" specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:186 +msgid "" +"`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if" +" not specified)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:189 +msgid "" +"*Density* parameters might need to be configured in a particular way " +"depending on the printer model." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:193 +msgid "" +"Visit `Epson's ESC * documentation <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_ and click on the " +"printer model printer in the table above to see if the printer should set " +"these parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:198 +msgid "The following are examples of proper and improper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:200 +msgid "Proper name formatting:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:202 +msgid "`EPSONTMm30II__IMC__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 +msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:205 +msgid "" +"Improper name formatting (this will not prevent printing, but the result " +"might not have the expected printed output):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:208 +msgid "`EPSON TMm 30II` -> The name can't have spaces." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 +msgid "" +"`EPSONTMm30II` -> The name itself is correct, but it won't use `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:210 +msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 +msgid "" +"`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing" +" parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:212 +msgid "" +"`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale " +"value." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:214 +msgid "**Finish adding a printer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:216 +msgid "" +"After setting the name of the printer with the appropriate naming " +"convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value" +" to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to " +":guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:220 +msgid "" +"After completing these steps, click :guilabel:`Add Printer`. If everything " +"was done correctly, the page should redirect to the *Banners* page." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:223 +msgid "" +"At this point the printer should have been created, now the :abbr:`IoT " +"(Internet of Things)` box just needs to detect it and then sync to Odoo's " +"server (this could take a few minutes)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:226 +msgid "**Adding the printer to Odoo PoS**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:228 +msgid "" +"Once the printer is visible on the Odoo database, don't forget to choose it " +"in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet " +"of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> " +"Connected Devices --> IoT Box --> Receipt Printer --> Save`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:234 +msgid "" +"If the printer was set up incorrectly (it is still printing random text or " +"the printed receipt is too big or small), then it cannot be modified via the" +" printer name with *CUPS*. Instead, the above process can be repeated to set" +" up another printer from scratch to create one with modified parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:239 +msgid "**Example setup of the Epson TM-U220B printer using ESC**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:244 +msgid "" +"The following is an example of the troubleshooting process for a TM-U220B " +"printer model using the `ESC *` command. The receipt pictured below is an " +"example of a receipt that is printing correctly due to proper formatting (in" +" theory):" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Properly formatted receipt picture from a demo database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:252 +msgid "" +"Trying to print this receipt right-away prior to the proper formatting will " +"not work as the TM-U220B printer model does not support `GS v 0`. Instead " +"random characters will print:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Printer paper with seemingly random characters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:259 +msgid "" +"To properly configure formatting for the Epson TM-U220B printer model take " +"the following steps." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:261 +msgid "" +"After consulting Epson's website for compatibility for both of the commands:" +" `GS v 0 <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=94>`_ and `ESC * " +"<https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_, it can be seen that " +"indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with " +"`ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson compatibility evaluation from Epson website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:270 +msgid "" +"When adding the printer, *CUPS* will ask which printer should be added:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Administration menu, add printer selection." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:276 +msgid "" +"In this case, the printer is connected via :abbr:`USB (Universal Serial " +"Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. " +"Instead it is likely part of the :guilabel:`Unknown` selection under " +":guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB " +"(Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box " +"and refreshing the page, the :guilabel:`Unknown` printer disappears. By " +"plugging it back in, the printer reappears, so it can be said that this is " +"the printer in question." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:283 +msgid "" +"For the naming convention, since it will need to print using the `ESC *` " +"command, it is imperative to add `__IMC`. Reference the printer model on " +"`Epson's ESC * site <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_ to find out more about" +" the *density* parameters." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturer's website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:292 +msgid "" +"For this particular model, TM-U220, `m` should be equal to 0 or 1. While " +"referencing the :guilabel:`Description` below the pink box in the above " +"picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, " +"the `m` value can NOT be 32 or 33 (otherwise there will be random characters" +" printed)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:297 +msgid "" +"The table includes the numeric values: 32 and 33, they both occur if the " +":guilabel:`Number of bits for vertical data` is set to 24. This means that " +"is a *High Vertical Density*. In the case of configuring the Epson TM-U220, " +"the *Low Vertical Density* will need to be forced, as this printer model " +"does not support *High Vertical Density* for this command `ESC *`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:302 +msgid "" +"To add a *Low Vertical Density*, add the `LDV` parameter to the naming " +"convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:308 +msgid "" +"Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value " +"to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to " +":guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturers website." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:315 +msgid "" +"However when trying to print with the naming convention: " +"`EpsonTMU220B__IMC_LDV__`, it will print the receipt, but it will be too big" +" and outside the margin. To resolve this, add a new printer (and naming " +"convention) with the `SCALE<X>` parameter to adapt to our receipt size." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:319 +msgid "Here are some examples:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:324 +msgid "Printer Naming Convention" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:325 +msgid "`EpsonTMU220B__IMC_LDV__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:326 +msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:327 +msgid "`EpsonTMU220B__IMC_LDV_LDH__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:328 +msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt example format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 +msgid "" +"Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:346 +msgid "The Zebra printer doesn't print anything" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:348 +msgid "" +"Zebra printers are quite sensitive to the format of the Zebra Programming " +"Language (ZPL) code that is printed. If nothing comes out of the printer or " +"blank labels are printed, try changing the format of the report that is sent" +" to the printer by accessing :menuselection:`Settings --> Technical --> User" +" Interface --> Views` in :ref:`developer mode <developer-mode>` and look for" +" the corresponding template." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:355 +msgid "" +"Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming " +"Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-" +"a-zpl-file-using-the-Generic-Text-Printer>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:362 +msgid "The characters read by the barcode scanner don't match the barcode" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:364 +msgid "" +"By default, most barcode scanners are configured in the US QWERTY format. If" +" the barcode scanner uses a different layout, go to the form view of the " +"device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select " +"the correct format." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:369 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:371 +msgid "" +"Make sure that the correct device is selected in the :menuselection:`Point " +"of Sale` configuration and that the barcode is configured to send an `ENTER`" +" character (keycode 28) at the end of every barcode. To do so, navigate to " +":menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> " +"Edit`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:377 +msgid "The barcode scanner is detected as a keyboard" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:380 +msgid "" +"Some barcode scanners do not advertise themselves as barcode scanners but as" +" a USB keyboard instead, and will not be recognized by the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:383 +msgid "" +"The device type can be manually changed by going to its form view " +"(:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the" +" :guilabel:`Is scanner` option." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 +msgid "Modifying the form view of the barcode scanner." +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:394 +msgid "The cash drawer does not open" +msgstr "" + +#: ../../content/applications/productivity/iot/config/troubleshooting.rst:396 +msgid "" +"The cash drawer should be connected to the printer and the :guilabel:`Cash " +"drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` " +"configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu " +"on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer " +"checkbox`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:3 +msgid "Connect Windows IoT Odoo" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:5 +msgid "" +"A Virtual IoT box is a computer program that needs to be downloaded and " +"installed on a Windows computer. This requires a Windows operating system " +"with an Odoo 16 or later database." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:8 +msgid "" +"The Windows virtual :abbr:`IoT (Internet of Things)` box works the same way " +"as a physical :abbr:`IoT (Internet of Things)` box, with the ability to run " +"most of the same devices. All :abbr:`POS (Point of Sale)` devices work with " +"it, such as a scale or printer. Payment terminals will also work, but it " +"should be noted that :abbr:`MRP (Material Requirement Planning)` devices are" +" not compatible. *These include cameras or measurement tools.*" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:15 +msgid "Pre-requisites" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:17 +msgid "" +"The following items will be needed to complete the Windows :abbr:`IoT " +"(Internet of Things)` installation." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:20 +msgid "Odoo 16 database or any version above." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:21 +msgid "" +":abbr:`IoT (Internet of Things)` compatible devices (except those mentioned " +"above). Refer to: `Odoo's compatible IoT devices " +"<https://www.odoo.com/app/iot-hardware>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:23 +msgid "Device drivers for Windows." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:26 +msgid "" +"Odoo recommends using an updated, recent version of Windows (Windows 10/11) " +"as some older operating systems can cause the Windows virtual :abbr:`IoT " +"(Internet of Things)` to not work." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:29 +msgid "Windows computer (laptop, desktop, or server)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:30 +msgid "" +"Odoo :abbr:`IoT (Internet of Things)` subscription. Refer to: :ref:`iot/iot-" +"eligibility`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:33 +msgid "Connect the Windows virtual Iot box to an Odoo database" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:35 +msgid "" +"The Windows virtual IoT box is simple to setup in just a few easy steps. " +"Follow this process when installing the Windows virtual IoT software for the" +" first time." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:39 +msgid "Download and initial installation" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:41 +msgid "" +"To begin the installation, navigate to the Odoo 16 or higher installation " +"package for Enterprise or Community - Windows edition at `Odoo's download " +"page <https://odoo.com/download>`_. Next, install and setup the Odoo " +":file:`.exe` file. After the instructions screen, click :guilabel:`Next` to " +"start the installation and agree to the :abbr:`TOS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:46 +msgid "" +"During the next step of the installation, select :guilabel:`Odoo IoT` from " +"the :guilabel:`Select the type of install` dropdown." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:50 +msgid "For reference, the following should be installed:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:52 +msgid "**Odoo server**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:53 +msgid "**Odoo IoT**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:54 +msgid "**Nginx WebServer**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:55 +msgid "**Ghostscript interpreter**" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:57 +msgid "" +"Ensure there is enough space on the computer for the installation and click " +":guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:60 +msgid "Setting the destination and completing the installation" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:62 +msgid "" +"To complete the installation, select the :guilabel:`Destination Folder` and " +"click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:66 +msgid "" +"Choosing ``C:\\odoo`` as the install location will allow for the Nginx " +"server to start. If the folder doesn't exist, then create it. Otherwise the " +"installation files will be spread throughout the hard drive." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:71 +msgid "" +"Odoo's Windows virtual IoT software shouldn't be installed inside any of the" +" Window's User's directories. Doing so won't allow for Nginx to initialize." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:74 +msgid "" +"The installation may take a few minutes. When complete, click " +":guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:76 +msgid "" +"Ensure that the :guilabel:`Start Odoo` box is checked and click " +":guilabel:`Finish`. After installation, the Odoo server will run and " +"automatically open `http://localhost:8069` on your web browser. The webpage " +"should display the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:81 +msgid "" +"A restart of the Windows IoT program may be necessary should the web browser" +" not display anything. :ref:`iot/restart_windows_iot`" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:85 +msgid "Connecting devices" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:87 +msgid "" +"Next, connect the :abbr:`IoT (Internet of Things)` devices to the Windows " +"computer. Windows should automatically detect the device because the driver " +"is pre-installed on the computer. If not, search for and install the Windows" +" driver for the device." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:91 +msgid "" +"Following connecting devices to the computer, refresh the :abbr:`IoT " +"(Internet of Things)` box homepage and verify the device is seen. If not, " +"reload the handlers through the :abbr:`IoT (Internet of Things)` box " +"homepage." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:95 +msgid "" +"Finally, connect Windows :abbr:`IoT (Internet of Things)` to a database " +"using existing instructions (manually using the Token)." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:101 +msgid "" +"Now the installation is complete, the devices connected to :abbr:`IoT " +"(Internet of Things)` can be used to complete processes/actions." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:110 +msgid "Restart Windows IoT box" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:112 +msgid "" +"In some instances a manual restart of the physical :abbr:`IoT (Internet of " +"Things)` box can resolve the issue of an :abbr:`IoT (Internet of Things)` " +"box not showing up on the database. For the Windows virtual :abbr:`IoT " +"(Internet of Things)` box a manual restart of the Odoo server can resolve " +"database connection issues." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:117 +msgid "To restart the virtual Windows IoT server:" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:119 +msgid "Type `Services` into the Windows :guilabel:`Search Bar`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:120 +msgid "" +"Select the :menuselection:`Services` App and scroll down to the " +":guilabel:`Odoo` service." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:121 +msgid "" +"Right click on :guilabel:`Odoo` and select :guilabel:`Start` or " +":guilabel:`Restart`. This action will manually restart the Odoo IoT server." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:125 +msgid "Firewalls" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:127 +msgid "" +"Firewalls keep devices safe and secure. Sometimes they can block connections" +" that should be made though. The Windows virtual :abbr:`IoT (Internet of " +"Things)` box software may not be reachable to the :abbr:`LAN (Local Area " +"Network)` due to a firewall preventing the connection. Consult your local IT" +" support team to make exceptions (network discovery) in the :abbr:`OS " +"(Operating System)` or firewall program. Windows has their own firewall as " +"do other virus protection programs." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:134 +msgid "" +"A client might encounter a time when they are able to reach the homepage of " +"the :abbr:`IoT (Internet of Things)` box, yet they cannot access it from " +"another computer/mobile device/tablet on the same network." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:139 +msgid "Making an exception on Windows Defender" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:141 +msgid "" +"It's possible to allow other devices to access the Windows virtual " +":abbr:`IoT (Internet of Things)` box while keeping the firewall on. This is " +"done by creating a rule on *Windows Defender* and allowing communication " +"through port `8069`. The following process describes the steps to take in " +"order to make this exception." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:147 +msgid "Create a rule in Windows Defender" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:149 +msgid "" +"First, open the *Windows Firewall* by navigating to the " +":menuselection:`Start Menu` and typing in `Firewall`. Then, open the " +":menuselection:`Windows Defender Firewall` program. In the left-hand menu, " +"navigate to :guilabel:`Advanced Settings`." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:153 +msgid "" +"Once :guilabel:`Advanced Settings` have been selected, click " +":guilabel:`Inbound Rules` in the left-hand menu. Then, in the right-hand " +"menu column (under :guilabel:`Inbound Rules`), click on :guilabel:`New Rule`" +" to create a new rule." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:158 +msgid "Configure new rule" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:160 +msgid "" +"On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then " +"click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page " +"leave the rule application to :guilabel:`TCP`. Then, select " +":guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the " +"text box, type in `8069`. Finally click :guilabel:`Next` to continue to the " +"next step." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:165 +msgid "" +"On the :menuselection:`Actions` page, select :guilabel:`Allow the " +"connection` and click :guilabel:`Next`. The following page on the " +":menuselection:`Rule Configuration` wizard is the :guilabel:`Profile` page. " +"On this page, select whichever connection type applies to the network the " +"Windows machine is operating on. Ideally, select :guilabel:`Private` only " +"connections. The *Private* connection type is the most secure connection " +"while allowing the selected port to communicate. Click :guilabel:`Next` to " +"continue." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:172 +msgid "" +"Finally, assign a new, unique name to the rule. For example, this name can " +"be `Odoo`. Optionally, add a brief description in the " +":guilabel:`Description` field. Click :guilabel:`Finish` to complete the " +":guilabel:`Rule Configuration` wizard. Now, the new rule is active and " +"devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` " +"box." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:178 +msgid "Uninstalling Windows IoT" +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:180 +msgid "" +"Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is " +"done through the Windows program manager. Using any Windows version, search " +"for `program`. Then, select :guilabel:`Add or Remove Programs` located in " +"the control panel. Search for `Odoo` and click the :guilabel:`three dot " +"menu` to uninstall." +msgstr "" + +#: ../../content/applications/productivity/iot/config/windows_iot.rst:185 +msgid "" +"Confirm the un-installation and follow the steps to uninstall through the " +"Odoo uninstall guide." +msgstr "" + +#: ../../content/applications/productivity/iot/devices.rst:5 +msgid "Devices" +msgstr "อุปกรณ์" + +#: ../../content/applications/productivity/iot/devices/camera.rst:3 +msgid "Connect a camera" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:5 +msgid "" +"A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an" +" Odoo database in just a few steps. Once a camera is connected to an " +":abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing " +"process, or it can be linked to a quality control point/quality check. Doing" +" so allows for the taking of pictures when a chosen quality control " +"point/check has been reached, or when a specific key is pressed during " +"manufacturing." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:12 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 +#: ../../content/applications/productivity/iot/devices/printer.rst:11 +#: ../../content/applications/productivity/iot/devices/scale.rst:10 +#: ../../content/applications/productivity/iot/devices/screen.rst:18 +msgid "Connection" +msgstr "การเชื่อมต่อ" + +#: ../../content/applications/productivity/iot/devices/camera.rst:14 +msgid "" +"To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply " +"connect the two via cable. This is usually done with a :abbr:`USB (Universal" +" Serial Bus)` cable of some sort." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:17 +msgid "" +"If the camera is `supported <https://www.odoo.com/page/iot-hardware>`_, " +"there is no need to set up anything, as it'll be detected as soon as it's " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Camera recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:25 +msgid "Link camera to quality control point in manufacturing process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:27 +msgid "" +"In the :menuselection:`Quality app`, a device can be set up on a " +":guilabel:`Quality Control Point`. To do that, navigate to the " +":menuselection:`Quality app --> Quality Control --> Control Points` and open" +" the desired :guilabel:`Control Point` that'll be linked to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:31 +msgid "" +"On the control point form, edit the control point by selecting the " +":guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the " +"drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein " +"the attached *device* can be selected. :guilabel:`Save` the changes, if " +"required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Setting up the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:40 +msgid "" +"The camera is now useable with the selected quality control point. When the " +"quality control point is reached during the manufacturing process, the " +"database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:48 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`. From here, select the device. There is" +" a :guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:53 +msgid "" +"On a quality check form, the :guilabel:`Type` of check can also be specified" +" to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> " +"Quality Control --> Quality Checks --> New` to create a new quality check " +"from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:58 +#: ../../content/applications/productivity/iot/devices/printer.rst:70 +msgid "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:59 +#: ../../content/applications/productivity/iot/devices/printer.rst:71 +msgid "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:64 +msgid "" +"To link a camera to an action, it first needs to be configured on a work " +"center. Navigate to :menuselection:`Manufacturing app --> Configuration --> " +"Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a " +"camera will be used to reveal that specific work center's detail form. From " +"here, add the device in the :guilabel:`IoT Triggers` tab, in the " +":guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:70 +msgid "" +"Now, the camera device can be linked to the :guilabel:`Action` column drop-" +"down option labeled :guilabel:`Take a Picture`. A key can also be added to " +"trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:74 +msgid "" +"The first trigger listed is chosen first. The order of triggers matters, and" +" they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:78 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/camera.rst:82 +#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92 +#: ../../content/applications/productivity/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:3 +msgid "Connect a footswitch" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:5 +msgid "" +"When working in a manufacturing environment, it's always better for an " +"operator to have both hands available at all times. Odoo's :abbr:`IoT " +"(Internet of Things)` box makes this possible when using a footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 +msgid "" +"In fact, with a footswitch, the operator is able to go from one screen to " +"another, and perform actions using their foot. This can be configured in " +"just a few steps on the work center in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 +msgid "" +"To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect" +" the two devices via cable. More often than not, this is done with a " +":abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 +msgid "" +"If the footswitch is a `supported device <https://www.odoo.com/page/iot-" +"hardware>`_, there is no need to take further action, since it'll be " +"automatically detected when connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 +msgid "" +"To link a footswitch to an action, it first needs to be configured on a work" +" center. Navigate to :menuselection:`Manufacturing app --> Configuration -->" +" Work Centers`. From here, go to the desired :guilabel:`Work Center` in " +"which the footswitch will be used, and add the device in the :guilabel:`IoT " +"Triggers` tab, under the :guilabel:`Device` column, by selecting " +":guilabel:`Add a Line`. Doing so means the footswitch can be linked to an " +"option in the :guilabel:`Action` column drop-down, and optionally, a key can" +" be added to trigger it. An example of an :guilabel:`Action` in the " +"*Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as " +"Done` buttons on a manufacturing work order." +msgstr "" +"หากต้องการเชื่อมโยงสวิตช์เท้าเหยียบกับการดำเนินการ " +"จะต้องกำหนดค่าบนศูนย์งานก่อน ไปที่ :menuselection:`แอประบบการผลิต --> " +"การกำหนดค่า --> ศูนย์งาน` จากที่นี่ ไปที่ :guilabel:`ศูนย์งาน` " +"ที่ต้องการซึ่งจะใช้สวิตช์เท้าเหยียบและเพิ่มอุปกรณ์ในแท็บ :guilabel:`เริ่มต้น" +" IoT` ใต้คอลัมน์ :guilabel:`อุปกรณ์` โดยเลือก : guillabel:`เพิ่มบรรทัด`. " +"การทำเช่นนี้หมายความว่าสามารถลิงก์ฟุตสวิตช์กับตัวเลือกในคอลัมน์แบบเลื่อนลง " +":guilabel:`ดำเนินการ` และอาจเพิ่มคีย์เพื่อทริกเกอร์ก็ได้ ตัวอย่างของ " +":guilabel:`ดำเนินการ` ใน *แอประบบการผลิต* อาจเป็นปุ่ม :guilabel:`ตรวจสอบ` " +"หรือ :guilabel:`ทำเครื่องหมายว่าเสร็จสิ้น` ในใบสั่งงานการผลิต" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 +msgid "" +"It should be noted that the first listed trigger is chosen first. So, the " +"order matters, and these triggers can be dragged into any order. In the " +"picture above, using the footswitch automatically skips the part of the " +"process that's currently being worked on." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the footswitch." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 +msgid "Connect a measurement tool" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7 +msgid "" +"With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect " +"measurement tools to the Odoo database for use in the *Quality app* on a " +"quality control point/quality check, or for use in a work center during the " +"manufacturing process." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11 +msgid "" +"Find the list of supported devices here: `Supported devices " +"<https://www.odoo.com/page/iot-hardware>`_." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 +msgid "Connect with universal serial bus (USB)" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17 +msgid "" +"To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the " +":abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of " +"Things)` box, and the device appears in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool recognized on the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 +msgid "Connect with bluetooth" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28 +msgid "" +"Activate the Bluetooth functionality on the device (see the device manual " +"for further explanation), and the :abbr:`IoT (Internet of Things)` box " +"automatically connects to the device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 +msgid "" +"Link a measurement tool to a quality control point in the manufacturing " +"process" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, navigate to :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the measurement" +" tool should be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a" +" field called :guilabel:`Device`, where the attached device can be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 +msgid "" +"Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. " +":guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50 +msgid "" +"At this point, the measurement tool is linked to the chosen quality control " +"point. The value, which usually needs to be changed manually, is " +"automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58 +#: ../../content/applications/productivity/iot/devices/printer.rst:60 +msgid "" +"Quality control points can also be accessed by navigating to " +":menuselection:`IoT App --> Devices`, then select the device. There is a " +":guilabel:`Quality Control Points` tab, where they can be added with the " +"device." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Measure`. Access a new quality check detail page, by" +" navigating to :menuselection:`Quality app --> Quality Control --> Quality " +"Checks --> New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68 +msgid "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69 +msgid "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74 +msgid "" +"To link a measurement tool to an action, it first needs to be configured on " +"a work center. To do that, navigate to :menuselection:`Manufacturing app -->" +" Configuration --> Work Centers`. Then, select the desired work center in " +"which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78 +msgid "" +"On the work center page, add the device in the :guilabel:`IoT Triggers` tab," +" under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. " +"Then, the measurement tool can be linked to the :guilabel:`Action` drop-down" +" menu option labeled :guilabel:`Take Measure`. A key can be added to trigger" +" the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84 +msgid "" +"It should be noted that the first listed trigger is chosen first. The order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the measurement tool." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:3 +msgid "Connect a printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:5 +msgid "" +"Printer installation can be done in a few easy steps. The printer can be " +"used to print receipts, labels, orders, or even reports from the different " +"Odoo apps. In addition, printer actions can be assigned as an *action on a " +"trigger* during the manufacturing process, or added onto a quality control " +"point or a quality check." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:13 +msgid "" +"The :abbr:`IoT (Internet of Things)` box supports printers connected through" +" :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. " +"`Supported printers <https://www.odoo.com/page/iot-hardware>`__ are detected" +" automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer as it would appear in the IoT app devices list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:23 +msgid "" +"The printer can take up to two minutes to appear in the *IoT app* devices " +"list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:26 +msgid "Link printer" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:29 +msgid "Link printer to work orders" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:31 +msgid "" +"*Work Orders* can be linked to printers, via a quality control point, to " +"print labels for manufactured products." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:34 +msgid "" +"In the *Quality app*, a device can be set up on a quality control point. To " +"do that, go to the :menuselection:`Quality app --> Quality Control --> " +"Control Points`, and open the desired control point to which the printer " +"will be linked." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:39 +msgid "" +"A *Manufacturing Operation* and *Work Order Operation* need to be attached " +"to a quality control point before the :guilabel:`Type` field allows for the " +":guilabel:`Print Label` option to be selected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:43 +msgid "" +"From here, edit the control point, by selecting the :guilabel:`Type` field, " +"and selecting :guilabel:`Print Label` from the drop-down menu of options. " +"Doing so reveals a field called :guilabel:`Device`, where the attached " +"*device* can be selected. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "This is the quality control point setup." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:52 +msgid "" +"The printer can now be used with the selected quality control point. When " +"the quality control point is reached during the manufacturing process, the " +"database presents the option to print labels for a specific product." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:65 +msgid "" +"On a quality check detail form, the :guilabel:`Type` of check can also be " +"specified to :guilabel:`Print Label`. To create new quality checks, navigate" +" to :menuselection:`Quality app --> Quality Control --> Quality Checks --> " +"New`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:76 +msgid "" +"To link a printer to an action, it first needs to be configured on a work " +"center. To do that, navigate to :menuselection:`Manufacturing app --> " +"Configuration --> Work Centers`. From here, select the desired work center " +"in which the printer will be used. Next, add the device in the " +":guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by " +"selecting :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:82 +msgid "" +"Then, the printer can be linked to either of the following options in the " +":guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, " +":guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can " +"also be added to trigger the action." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:87 +msgid "" +"The first listed trigger on the form will be chosen first. So, the order " +"matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:91 +msgid "" +"On the :guilabel:`Work Order` screen, a status graphic indicates whether the" +" database is correctly connected to the printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:98 +msgid "Link printer to reports" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:100 +msgid "" +"It's also possible to link a type of report to a certain printer. In the " +"*IoT app*, go to the :guilabel:`Devices` menu, and select the desired " +"printer that needs to be configured." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:103 +msgid "" +"From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` " +"tab, and select :guilabel:`Add a line`. In the window that appears, check " +"all the types of :guilabel:`Reports` that should be linked to this printer." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst-1 +msgid "The printer devices listed in the IoT Devices menu." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:111 +msgid "" +"Now, each time :guilabel:`Print` is selected in the control panel, instead " +"of downloading a PDF, Odoo sends the report to the selected printer, and " +"automatically prints it." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:115 +msgid "" +":doc:`POS Order Printing " +"<../../../sales/point_of_sale/restaurant/kitchen_printing>`" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/printer.rst:118 +msgid "" +"Reports can also be configured in the :guilabel:`Technical Menu` while in " +":ref:`debug mode <developer-mode>`. To do that, navigate to " +":menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. " +"From here, the individual report can be found in this list, where the " +":guilabel:`IoT Device` can be set on the report." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:3 +msgid "Connect a scale" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:5 +msgid "" +"A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an " +"Odoo database in a few easy steps. After setup, the *Point of Sale* app can " +"be used to weigh products, which is helpful if their prices are calculated " +"based on weight." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:12 +msgid "" +"To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it " +"with a :abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:16 +msgid "" +"In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter " +"may be needed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:18 +msgid "" +"If the scale is `compatible with Odoo IoT Box " +"<https://www.odoo.com/page/iot-hardware>`_, there is no need to set up " +"anything because it will be automatically detected as soon as it is " +"connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "IOT box auto detection." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:25 +msgid "" +"The :abbr:`IoT (Internet of Things)` box may need to be restarted and the " +"scale's drivers may need to be downloaded to the box in some cases. To " +"update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage " +"and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load " +"Drivers`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "View of the IoT box settings and driver list." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:34 +msgid "" +"If loading the drivers still doesn't allow for the scale to function, it may" +" be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of " +"Things)` box. In this case, a different scale will need to be used." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:41 +msgid "" +"To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app " +"--> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT " +"(Internet of Things)` box feature. After this is complete, the scale device " +"can be set." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:45 +msgid "" +"Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then " +"click :guilabel:`Save` to save the changes, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "List of the external tools that can be used with PoS and the IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst:52 +msgid "" +"The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. " +"Now, if a product has a price per weight set, clicking on it on the " +":guilabel:`PoS` screen opens the scale screen, where the cashier can weigh " +"the product and add the correct price to the cart." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/scale.rst-1 +msgid "Electronic Scale dashboard view when no items are being weighed." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:3 +msgid "Connect a screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:5 +msgid "" +"In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a " +"screen display. After being configured, the screen can be used to display a " +"Point of Sale (PoS) order to a client." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:10 +msgid "An example of a PoS (point of sale) order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:12 +msgid "" +"Access the customer display by going to the :abbr:`IoT (Internet of Things)`" +" box homepage and clicking on the :guilabel:`PoS Display` button. To get to " +"the :abbr:`IoT (Internet of Things)` box homepage, navigate to " +":menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet" +" of Things)` box homepage link." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:20 +msgid "" +"The way to connect the screen display to the :abbr:`IoT (Internet of " +"Things)` box differs depending on the model." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:25 +msgid "IoT Box model 4" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:27 +msgid "" +"Connect up to two screens with micro-HDMI cables on the side of the " +":abbr:`IoT (Internet of Things)` box. If two screens are connected, they can" +" display distinct content (see :ref:`Screen Usage <iot/usage_screen>`)." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:31 +msgid "IoT Box model 3" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:33 +msgid "" +"Connect the screen with an HDMI cable on the side of the :abbr:`IoT " +"(Internet of Things)` box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema <iot/connect_schema>`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:39 +msgid "" +"Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` " +"box is switched on. If it is already on, connect the screen(s), and then " +"restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten " +"seconds and plugging it back into its power source." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:44 +msgid "" +"The usage of HDMI/micro-HDMI adapters may cause issues which will result in " +"a blank, black screen on the screen display. Using the specific cable for " +"the display connection is recommended." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:47 +msgid "" +"If the connection was successful, the screen should display the " +":guilabel:`POS Client display` screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The default \"POS Client Display\" screen that appears when a screen display is successfully\n" +"connected to an IoT box." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:55 +msgid "" +"The screen should also appear in the list of :guilabel:`Displays` on the " +":abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display " +"can be seen by accessing :menuselection:`IoT app --> Devices`." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a screen display name shown on the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:64 +msgid "" +"If no screen is detected, a default display named :guilabel:`Distant " +"Display` will be displayed instead. This indicates that there is no hardware" +" screen connected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:0 +msgid "The \"Distant Display\" screen name will be used if no screen is detected." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:74 +msgid "Usage" +msgstr "การใช้งาน" + +#: ../../content/applications/productivity/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:79 +msgid "" +"To use the screen in the *Point of Sale app*, go to :menuselection:`Point of" +" Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of " +"Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT " +"Box` feature." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:83 +msgid "" +"Next, select the screen from the :guilabel:`Customer Display` drop-down " +"menu. Then click :guilabel:`Save`, if required." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:90 +msgid "" +"The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A " +"screen icon will appear in the menu at the top of the screen to indicate the" +" screen's connection status." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "" +"The \"screen\" icon on the Point of Sale display shows the connection status with the\n" +"screen." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:98 +msgid "" +"The screen will automatically show the :abbr:`PoS (Point of Sale)` orders " +"and update when changes are made to the order." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst-1 +msgid "An example of a PoS order on a screen display." +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:106 +msgid "Display a website on the screen" +msgstr "" + +#: ../../content/applications/productivity/iot/devices/screen.rst:108 +msgid "" +"Open the screen form view by accessing :menuselection:`IoT app --> Devices " +"--> Customer Display`. This allows the user to choose a particular website " +"URL to display on the screen using the :guilabel:`Display URL` field." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:7 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:203 +msgid "Knowledge" +msgstr "คลังข้อมูล" + +#: ../../content/applications/productivity/knowledge.rst:9 +msgid "" +"**Odoo Knowledge** is a multipurpose productivity app that allows internal " +"users to enrich their business knowledge base and provide individually or " +"collaboratively gathered information." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:12 +msgid "" +"The pages on which they gather content are called *articles*. They are " +"mainly composed of a title and a body. The latter is an HTML field " +"containing text, images, links to other articles, records from other models," +" templates, etc." +msgstr "" + +#: ../../content/applications/productivity/knowledge.rst:17 +msgid "`Knowledge product page <https://www.odoo.com/app/knowledge>`_" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:3 +msgid "Articles editing" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:6 +msgid "Add and style content" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:8 +msgid "" +"To start adding content, click anywhere on the page. Your cursor is " +"automatically set to write the article's first-level header. Once you are " +"done writing the title, press **enter** on your keyboard to move to the next" +" line." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst-1 +msgid "knowledge's user interface" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:17 +msgid "" +"Click :guilabel:`Untitled` on the left side of the top bar to automatically " +"match your h1 :dfn:`(First-level header)` title and the article's name. To " +"change the name of your article later, you must do it manually. To do so, " +"click the name on the top bar and proceed to the modification." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:23 +msgid "Text editor" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:25 +msgid "To stylize the text using the text editor, select the text to format." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:27 +msgid "Then, you can:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:29 +msgid "" +"Change the style by clicking :guilabel:`Normal`. Doing so opens a dropdown " +"menu with multiple styles to choose from (:guilabel:`Normal, Code, Header 1 " +"→ Header 6, Quote`);" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:31 +msgid "" +"Format the text. Click :guilabel:`B` to put it in bold, :guilabel:`I` to put" +" it in italic, :guilabel:`U` to underline, and :guilabel:`S` to " +"strikethrough;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:33 +msgid "" +"Change the font color by clicking :guilabel:`A` or the background color by " +"clicking the **pencil** icon:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:36 +msgid "" +"To choose from a predefined theme color, click :guilabel:`Theme` and select " +"the desired color." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:37 +msgid "" +"To customize, click :guilabel:`Solid` and define a color using the wheel, by" +" typing its hex code, or its RGBA values." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:39 +msgid "" +"To use a gradient, click :guilabel:`Gradient`, choose a predefined gradient " +"or click :guilabel:`Custom` to create a personalized gradient." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:42 +msgid "" +"To change the text's size, click the **size number** and select the desired " +"size;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:43 +msgid "" +"Click the **lists** icons to turn the paragraph into an unordered list, an " +"ordered list, or a checklist;" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:45 +msgid "Click the **chain** icon to insert or edit an URL link." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:51 +msgid "" +"To format a whole paragraph, type `/` anywhere in the text. Doing so opens " +"the **powerbox**, which allows:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:54 +msgid "Changing a paragraph into lists (unordered, ordered, checklists)." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:55 +msgid "" +"Changing a paragraph into a header (1 → 6), normal text, `code`, or " +"*quotes*." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:58 +msgid "Cover pictures" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:60 +msgid "" +"You can customize your article by adding a cover picture and an icon. Hover " +"above the h1 title and click :guilabel:`Add Cover`. A pop-up window opens to" +" set a cover picture." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:63 +msgid "" +"If your database and your Unsplash account are associated, the cover picture" +" is automatically selected based on the article's name. To modify it, hover " +"over the picture to make the buttons appear, click :guilabel:`Change Cover`," +" and select another image." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:67 +msgid "Retrieve images from different sources:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:69 +msgid "Search the **Unsplash** database." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:70 +msgid "Enter a picture's **URL**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:71 +msgid "**Upload** an image from a computer." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:73 +msgid "" +"To remove the cover, hover over it to make the buttons appear and click " +":guilabel:`Remove Cover`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:76 +msgid "" +"To associate Unsplash with your database, please refer to " +":doc:`../../websites/website/configuration/unsplash`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:78 +msgid "" +"The articles are responsive, and so are the cover pictures. As a result, the" +" images cannot be repositioned manually to fit a particular screen, as they " +"automatically resize depending on the device." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:83 +msgid "Icons" +msgstr "ไอคอน" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:85 +msgid "" +"To add an icon, hover above the h1 title and click :guilabel:`Add Icon`. " +"Doing this sets a random emoji automatically. To change it, click it and " +"select one from the emoji window. To remove it, proceed equally and click " +"the red-circled :guilabel:`x`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:90 +msgid "" +"The emoji is also displayed before the corresponding article in the side " +"panel hierarchic tree." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:91 +msgid "" +"Click the emoji on the side panel to change it without opening the related " +"article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:94 +msgid "Commands" +msgstr "คำสั่ง" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:96 +msgid "" +"To use a command, type `/` and open the **powerbox**. Type the command's " +"name or select from multiple features to insert blocks, images, files, etc. " +"Some of them, such as `/Image` or `/Article` are common to all the apps, but" +" others are inherent to the knowledge app and cannot be found or used in any" +" other application." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:102 +msgid "List of commands" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:104 +msgid "Commands are divided into multiple categories depending on their use." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:107 +msgid "Structure" +msgstr "โครงสร้าง" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:114 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:144 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:164 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:178 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:196 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:210 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:235 +msgid "Command" +msgstr "คำสั่ง" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:115 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:145 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:165 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:179 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:197 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:211 +#: ../../content/applications/productivity/knowledge/articles_editing.rst:236 +msgid "Use" +msgstr "ใช้" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:116 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:117 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:118 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:119 +msgid "Create a list with numbering." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:120 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:121 +msgid "Track tasks with a checklist." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:122 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:123 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:124 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:125 +msgid "Insert an horizontal rule separator." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:126 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:127 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:128 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:129 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:130 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:131 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:132 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:133 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:134 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:135 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:137 +msgid "Format" +msgstr "รูปแบบ" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:146 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:147 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:148 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:149 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:150 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:151 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:154 +#: ../../content/applications/productivity/knowledge/properties.rst:34 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:155 +msgid "Paragraph block." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:157 +msgid "Media" +msgstr "มีเดีย" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:166 +msgid ":guilabel:`Image`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:167 +msgid "Insert an image." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:168 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:169 +msgid "Link an article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:171 +msgid "Navigation" +msgstr "การนำทาง" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:180 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:181 +msgid "Add a link." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:182 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:183 +msgid "Add a button." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:184 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:185 +msgid "Add a specific appointment." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:186 +msgid ":guilabel:`Calendar`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:187 +msgid "Schedule an appointment." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:189 +msgid "Widget" +msgstr "วิดเจ็ต" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:198 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:199 +msgid "Insert a rating over 3 stars." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:200 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:201 +msgid "Insert a rating over 5 stars." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:212 +msgid ":guilabel:`Table of Content`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:213 +msgid "Add a table of content with the article's headings." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:214 +msgid ":guilabel:`Index`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:215 +msgid "Show the first level of nested articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:216 +msgid ":guilabel:`Outline`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:217 +msgid "Show all nested articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:218 +msgid ":guilabel:`Item Kanban`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:219 +msgid "Insert a kanban view of article items." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:220 +msgid ":guilabel:`Item List`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:221 +msgid "Insert a list view of article items." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:222 +msgid ":guilabel:`File`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:223 +msgid "Embed a file that can be downloaded." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:224 +msgid ":guilabel:`Template`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:225 +msgid "" +"Add a template section that can be inserted in messages, terms & conditions," +" or description in other applications." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:228 +msgid "Basic Blocks" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:237 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:238 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:241 +msgid "Content from other apps" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:243 +msgid "" +"Knowledge allows to retrieve content views from other applications. To do " +"so, go to the targeted app and create the desired view. Then, click " +":menuselection:`Favorite --> Insert view in article` and select an article. " +"The view is inserted at the bottom of the selected article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:248 +msgid "" +"To retrieve the view below, we created it by going to :menuselection:`Sales " +"--> Graph icon --> Pie Chart icon` and inserted it by clicking " +":menuselection:`Favorite --> Insert view in article` and selecting the " +"*Sales Playbook* article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:0 +msgid "article view from the Sales app" +msgstr "" + +#: ../../content/applications/productivity/knowledge/articles_editing.rst:257 +msgid "" +"Users who do **not** have access to the view will **not** be able to access " +"it in **Knowledge** even though they have access to the article containing " +"the view." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:3 +msgid "Articles management" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:5 +msgid "" +"Managing articles effectively is key to maximizing the value of your " +"knowledge resources, whether working on a research project, studying for an " +"exam, or building a knowledge database for your business. Knowledge allows " +"you to fully manage your articles, from :ref:`creation <management/create>` " +"to :ref:`removal <management/remove>`, through :ref:`sharing " +"<management/share>` and :ref:`structure <management/structure>`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:11 +msgid "" +"You can find most tools to manage articles by clicking the vertical ellipsis" +" button (:guilabel:`⋮`) at the right side of the top bar. From there, you " +"can move, lock, delete, or duplicate an article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Menu with tools for the management of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:18 +msgid "Creation, sharing, and removal of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:23 +msgid "Creation" +msgstr "การสร้าง" + +#: ../../content/applications/productivity/knowledge/management.rst:25 +msgid "" +"To create articles, click the :guilabel:`+ New` button on the right side of " +"the top bar or the :guilabel:`+` button next to a category or another " +"article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:29 +msgid "" +"Create private articles quickly with the Alt/Option + C keyboard shortcut." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:34 +msgid "Sharing" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:36 +msgid "" +"You can share articles with internal or external users. To do so, open the " +"share menu by clicking :guilabel:`Share` in the top-right menu of articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:40 +msgid "Invite users" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:42 +msgid "" +"To share articles with specific users (internal or external, such as a " +"partner or a customer), click :guilabel:`Invite`. This opens a pop-up window" +" in which you can choose the :guilabel:`Permission` :ref:`(i.e, access " +"rights) <management/categories>` and enter the :guilabel:`Recipients`' name " +"or email." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:47 +msgid "" +"You can also restrict a specific user from accessing the article by " +"selecting :guilabel:`No access` permission." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "pop-up window to invite users to access a Knowledge article" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:54 +msgid "Share online" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:56 +msgid "" +"To share articles **online**, activate the :guilabel:`Share to web` button. " +"Doing so generates a URL link anyone can use to view the article." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:59 +msgid "" +"Additionally, the share menu displays the default permission for internal " +"members along with all the users who have been granted specific permission." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Sharing menu with URL for online sharing and the list of members." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:68 +msgid "Removal" +msgstr "การนำออก" + +#: ../../content/applications/productivity/knowledge/management.rst:70 +msgid "To remove an article, you can either **delete** it or **archive** it." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:72 +msgid "" +"To delete an article, open it and click the vertical ellipsis button " +":menuselection:`(⋮) --> Delete`. The article is moved to the trash for 30 " +"days before being permanently deleted. To restore it, click :guilabel:`Open " +"the Trash`, select the article, and click :guilabel:`Restore`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:76 +msgid "" +"To archive articles, click :guilabel:`Search`, select the article(s), and " +"click :menuselection:`Action --> Archive --> Archive`. Archived articles are" +" hidden from the search menu. To retrieve an archived article, add a custom " +"filter to display them (:menuselection:`Search --> Filters --> Add Custom " +"Filter`, and set :guilabel:`Active` as :guilabel:`is No`). Then, select the " +"article(s) and go to :menuselection:`Action --> Unarchive`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:85 +msgid "Structure of articles" +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:87 +msgid "" +"Articles are organized into a hierarchical structure wherein the article on " +"top is a parent article, and those underneath are called nested articles. " +"This structure allows the grouping of related articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:91 +msgid "" +"To establish this hierarchy, create new articles by clicking the " +":guilabel:`+` button next to the parent-to-be article, or move existing " +"articles by either dragging and dropping them under the parent-to-be or by " +"clicking the vertical ellipsis button (:guilabel:`⋮`), clicking " +":guilabel:`Move To` on the toolbox and selecting the article to use as a " +"parent." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:99 +msgid "Categories" +msgstr "หมวดหมู่" + +#: ../../content/applications/productivity/knowledge/management.rst:101 +msgid "" +"Additionally, articles are divided into four categories that can be found on" +" the left sidebar. These categories give articles default **access rights**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:104 +msgid "" +":guilabel:`Favorites`: You can set any article you can access as a favorite." +" To do so, click the star-shaped icon (:guilabel:`★`) in the top-right menu " +"of articles. Marking articles as **favorites** is user-specific and does not" +" affect other users." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:107 +msgid "" +":guilabel:`Workspace`: Articles displayed in that category are available to " +"all internal users. These users have the right to read, modify or share " +"these articles." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:109 +msgid "" +":guilabel:`Shared`: Articles displayed in that category are those you shared" +" with internal users, external users, or shared with you." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst:111 +msgid "" +":guilabel:`Private`: Articles displayed in that category are only available " +"to you." +msgstr "" + +#: ../../content/applications/productivity/knowledge/management.rst-1 +msgid "Categories displayed in the left sidebar of Odoo Knowledge" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:3 +#: ../../content/applications/productivity/studio/fields.rst:453 +msgid "Properties" +msgstr "คุณสมบัติ" + +#: ../../content/applications/productivity/knowledge/properties.rst:5 +msgid "" +"Properties are fields containing data and that can be added to articles by " +"any user with **write** access. These fields are shared between all the " +"child articles and article items under the same parent." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:10 +msgid "" +"To be able to add properties, an article must be either a **child article** " +"or an **article item**." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:14 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:16 +msgid "" +"Hover above the first-level header to make the buttons appear. Click " +":menuselection:`⚙ Add Properties --> Field Type`, select the type and add a " +"default value if needed. To make the fields appear in **kanban views**, " +"check :guilabel:`View in Kanban` as well. To validate and close the property" +" creation window, click anywhere." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst-1 +msgid "Dropdown of property fields types" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:25 +msgid "The different types assess what the field content can be:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:32 +#: ../../content/applications/productivity/knowledge/properties.rst:58 +msgid "Types" +msgstr "ประเภท" + +#: ../../content/applications/productivity/knowledge/properties.rst:33 +#: ../../content/applications/productivity/knowledge/properties.rst:59 +msgid "Uses" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:35 +msgid "Allows adding any content with no restriction." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:36 +msgid ":guilabel:`Checkbox`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:37 +msgid "Add a checkbox." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:38 +msgid ":guilabel:`Integer`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:39 +msgid "Allows adding integer numbers." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:40 +msgid ":guilabel:`Decimal`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:41 +msgid "Allows adding any number." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:42 +msgid ":guilabel:`Date`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:43 +msgid "Allows selecting a date." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:44 +msgid ":guilabel:`Date & Time`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:45 +msgid "Allows selecting a date and time." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:47 +msgid "Some **field types** need to be configured:" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst-1 +msgid "property configuration form" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:60 +msgid ":guilabel:`Selection`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:61 +msgid "" +"Add a drop-down selection menu with restricted values that have been set at " +"the property creation." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:64 +msgid "" +"To set it up, click :guilabel:`Add a Value` next to the :guilabel:`Values` " +"field. Enter predetermined values and press **enter** to validate; you can " +"enter as many values as needed. Click anywhere to close the property " +"creation window." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:67 +msgid ":guilabel:`Tags`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:68 +msgid "Allows creating and applying as many tags as needed." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:70 +msgid "" +"To set it up, enter your `new_tag` in the :guilabel:`Tags` field, and press " +"**enter** or click :guilabel:`Create \"new_tag\"`. Click anywhere to close " +"the window. Then, add the tags into the property field. To do so, click the " +"property field and choose from the created tags; enter the tags' name and " +"press **enter**; enter a new tag's name and create a new one on the spot." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:75 +msgid ":guilabel:`Many2one`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:76 +msgid "" +"Choose from a list of records that result from a model's domain. You can " +"only select one result." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:79 +#: ../../content/applications/productivity/knowledge/properties.rst:86 +msgid "" +"To set it up, click :guilabel:`Search a Model` in the :guilabel:`Model` " +"field, select the model. Match all records by clicking :guilabel:`## " +"Record(s)`, or filter the results by clicking :guilabel:`+ Add Filter` and " +"show the records by clicking :guilabel:`## Record(s)`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:82 +msgid ":guilabel:`Many2many`" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:83 +msgid "" +"Choose from a list of records that result from a model's domain. You can " +"select as many results as needed." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:91 +msgid "Delete property fields" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:93 +msgid "" +"To remove a property, click the **pencil** icon next to the targeted " +"property, then click :menuselection:`Delete --> Delete`." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:97 +msgid "Once a property field is deleted, you cannot retrieve it." +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:100 +msgid "Hide the property panel" +msgstr "" + +#: ../../content/applications/productivity/knowledge/properties.rst:102 +msgid "" +"To hide the property sidebar panel, click the gear :guilabel:`(⚙)` button." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:5 +msgid "Mail Plugins" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:13 +msgid "" +"Mail Plugins are connectors that bridge your mailbox with your Odoo " +"database. With them, you can interact with your Odoo database directly from " +"your mailbox by:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:16 +msgid "Creating leads and centralizing prospects' emails into the CRM app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:17 +msgid "Generating tasks in any Odoo project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:18 +msgid "Creating tickets in the Helpdesk app." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:19 +msgid "Searching and storing insights on your contacts." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:21 +msgid "" +"Mail Plugins are available for :doc:`Outlook <mail_plugins/outlook>` and " +":doc:`Gmail <mail_plugins/gmail>`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:27 +msgid "Pricing" +msgstr "กำหนดราคา" + +#: ../../content/applications/productivity/mail_plugins.rst:29 +msgid "Mail Plugins are **free** to install and use." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:31 +msgid "" +"However, they can provide **Lead Enrichment**, which is part of a paid " +"service known as **Lead Generation**." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:34 +msgid "" +"Mail plugins allow you to test Lead Enrichment for free, whether you connect" +" the plugins to a database or not. After a while, the plugins ask you to buy" +" :doc:`../general/in_app_purchase` credits if you would like to keep using " +"this service." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:41 +msgid "Lead Generation IAP service" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:43 +msgid "" +"Lead Enrichment uses the *Lead Generation IAP service*. Each request " +"consumes one *Lead Generation credit*." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:46 +msgid "" +"To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment " +"--> Buy credits` and select a package." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:50 +msgid "" +"If you are out of credits, the only information populated when clicking on " +"the suggested company is its website link and logo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:52 +msgid "" +"Check out the `Lead Generation IAP service Privacy Policy " +"<https://iap.odoo.com/privacy#header_3>`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:56 +msgid ":doc:`../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins.rst:57 +msgid "`Odoo Tutorials: Lead Enrichment <https://www.odoo.com/r/p73>`_" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:3 +msgid "Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:5 +msgid "" +"The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users " +"can keep track of all their work between Gmail and Odoo, without losing any " +"information." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:9 +msgid "Odoo Online users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:11 +msgid "" +"For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to " +"configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:15 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:94 +msgid "Install the Gmail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:17 +msgid "" +"First, log in to the Gmail account that the user wishes to connect to Odoo." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:19 +msgid "" +"From the Gmail inbox, click the plus sign icon on the right side panel to " +"get add-ons. If the side panel is not visible, click on the arrow icon at " +"the bottom right corner of the inbox to reveal it." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Plus sign icon on the Gmail inbox side panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:26 +msgid "" +"Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo" +" Inbox Addin`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "Odoo Inbox Addin on Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:32 +msgid "" +"Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google " +"Workspace Marketplace " +"<https://workspace.google.com/marketplace/app/odoo_inbox_addin/873497133275>`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:35 +msgid "" +"Once the plugin is located, click :guilabel:`Install`. Then, click " +":guilabel:`Continue` to start the installation." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:38 +msgid "" +"Next, select which Gmail account the user wishes to connect to Odoo. Then " +"click :guilabel:`Allow` to let Odoo access the Google account. Google will " +"then show a pop-up window confirming that the installation was successful." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:43 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:134 +msgid "Configure the Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:45 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:136 +msgid "" +"The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in " +"order to use the Gmail Plugin. To enable the feature, go to " +":menuselection:`Settings --> General Settings`. Under the " +":guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then" +" click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "The Mail Plugin feature in the Settings." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:55 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:145 +msgid "Configure the Gmail inbox" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:57 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:147 +msgid "" +"In the Gmail inbox, a purple Odoo icon is now visible on the right side " +"panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click" +" on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin" +" window to grant Odoo access to the Gmail inbox." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"The Authorize Access button in the right sidebar of the Odoo plugin panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:65 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:155 +msgid "" +"Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that" +" the user wishes to connect to the Gmail inbox, and log in to the database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:69 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:159 +msgid "" +"Use the general URL for the database, not the URL of a specific page in the " +"database. For example, use `https://mycompany.odoo.com`, not " +"`https://mycompany.odoo.com/web#cids=1&action=menu`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:73 +#: ../../content/applications/productivity/mail_plugins/gmail.rst:163 +msgid "" +"Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The " +"browser will then show a :guilabel:`Success!` message. After that, close the" +" window. The Gmail inbox and Odoo database are now connected." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:78 +msgid "Odoo On-Premise users" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:80 +msgid "" +"For databases hosted on servers other than Odoo Online (or Odoo.sh), follow " +"the steps below to configure the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:84 +msgid "" +"As part of their security guidelines, Google requires add-on creators to " +"provide a list of URLs that can be used in actions and redirections launched" +" by the add-on. This protects users by ensuring, for example, that no add-on" +" redirects users toward a malicious website. (Read more on `Google Apps " +"Script <https://developers.google.com/apps-script/manifest/allowlist-" +"url>`_.)" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:89 +msgid "" +"Since Odoo can only list the `odoo.com` domain and not every on-premise " +"customer's unique server domain, on-premise customers cannot install the " +"Gmail Plugin from the Google Workspace Marketplace." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:96 +msgid "" +"First, access the `GitHub repository <https://github.com/odoo/mail-client-" +"extensions>`_ for the Odoo Mail Plugins. Next, click on the green " +":guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download " +"the Mail Plugin files onto the user's computer." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst-1 +msgid "" +"Download the ZIP file from the Odoo GitHub repository for Mail Plugins." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:104 +msgid "" +"Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-" +"extensions-master --> gmail --> src --> views`, and open the " +":file:`login.ts` file using any text editor software, such as Notepad " +"(Windows), TextEdit (Mac), or Visual Studio Code." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:108 +msgid "" +"Delete the following three lines of text from the :file:`login.ts` file:" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:116 +msgid "" +"This removes the `odoo.com` domain constraint from the Gmail Plugin program." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:118 +msgid "" +"Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master " +"--> gmail`, and open the file called :guilabel:`appsscript.json`. In the " +":guilabel:`urlFetchWhitelist` section, replace all the references to " +"`odoo.com` with the Odoo customer's unique server domain." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:122 +msgid "" +"Then, in the same :guilabel:`gmail` folder, open the file called " +":guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` " +"file to push the Gmail Plugin files as a Google Project." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:126 +msgid "" +"The computer must be able to run Linux commands in order to follow the " +"instructions on the :guilabel:`README.md` file." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/gmail.rst:129 +msgid "" +"After that, share the Google Project with the Gmail account that the user " +"wishes to connect to Odoo. Then, click :guilabel:`Publish` and " +":guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-" +"on` to install the Gmail Plugin." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:3 +msgid "Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:5 +msgid "" +"Outlook allows for third-party applications to connect in order to execute " +"database actions from emails. Odoo has a plugin for Outlook that allows for " +"the creation of an opportunity from the email panel." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:12 +msgid "" +"The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both" +" on Odoo and Outlook." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 +msgid "Enable Mail Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:19 +msgid "" +"First, enable the *Mail Plugin* feature in the database. Go to " +":menuselection:`Settings --> General Settings --> Integrations`, enable " +":guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:25 +msgid "Install the Outlook Plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:27 +msgid "" +"Download (:menuselection:`Save Page As --> Web Page XML only`) the following" +" XML file to upload later: " +"`https://download.odoocdn.com/plugins/outlook/manifest.xml " +"<https://download.odoocdn.com/plugins/outlook/manifest.xml>`_." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:31 +msgid "" +"Next, open the Outlook mailbox, and select any email. After completing this," +" click on the :guilabel:`More actions` button in the upper right-side and " +"select :guilabel:`Get Add-ins`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 +msgid "" +"Following this step, select the :guilabel:`My add-ins` tab on the left-side." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "My add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:44 +msgid "" +"Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ " +"Add a custom add-in`, and then on :guilabel:`Add from file...`" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Custom add-ins in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:51 +msgid "" +"For the next step, attach the `manifest.xml` file downloaded above, and " +"press :guilabel:`OK`. Next, read the warning and click on " +":guilabel:`Install`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Custom add-in installation warning in Outlook" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:61 +msgid "Connect the database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:63 +msgid "" +"Now, Outlook will be connected to the Odoo database. First, open any email " +"in the Outlook mailbox, click on the :guilabel:`More actions` button in the " +"upper right-side, and select :guilabel:`Odoo for Outlook`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Odoo for Outlook add-in button" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:71 +msgid "" +"The right-side panel can now display **Company Insights**. At the bottom, " +"click on :guilabel:`Login`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Logging in the Odoo database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:79 +msgid "" +"Only a limited amount of **Company Insights** (*Lead Enrichment*) requests " +"are available as a trial database. This feature requires :ref:`prepaid " +"credits <mail_plugins/pricing>`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:83 +msgid "" +"If, after a short while, the panel is still empty, it is possible that the " +"browser cookie settings prevented it from loading. Note that these settings " +"also change if the browser is in \"Incognito\" mode." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:87 +msgid "" +"To fix this issue, configure the browser to always allow cookies on Odoo's " +"plugin page." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:89 +msgid "" +"For Google Chrome, change the browser cookie settings by following the guide" +" at: `https://support.google.com/chrome/answer/95647 " +"<https://support.google.com/chrome/answer/95647>`_ and adding " +"`download.odoo.com` to the list of :guilabel:`Sites that can always use " +"cookies`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 +msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Entering the Odoo database URL" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 +msgid "Next, click on :guilabel:`Allow` to open the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "New window pop-up warning" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:108 +msgid "" +"If the user isn't logged into the database, enter the credentials. Click on " +":guilabel:`Allow` to let the Outlook Plugin connect to the database." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Allowing the Outlook Plugin to connect to a database" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 +msgid "Add a shortcut to the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:120 +msgid "" +"By default, the Outlook Plugin can be opened from the *More actions* menu. " +"However, to save time, it's possible to add it next to the other default " +"actions." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:123 +msgid "" +"In the Outlook mailbox, click on :guilabel:`Settings`, then on " +":guilabel:`View all Outlook settings`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Viewing all Outlook settings" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:130 +msgid "" +"Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on " +":guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst-1 +msgid "Odoo for Outlook customized action" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 +msgid "Following this step, open any email; the shortcut should be displayed." +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 +msgid "Using the plugin" +msgstr "" + +#: ../../content/applications/productivity/mail_plugins/outlook.rst:146 +msgid "" +"Now that the plug-in is installed and operational, all that needs to be done" +" to create a lead is to click on the `O` [Odoo icon] or navigate to " +":guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side" +" panel will appear on the right-side, and under :guilabel:`Opportunities` " +"click on :guilabel:`New`. A new window with the created opportunity in the " +"Odoo database will populate." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:6 +msgid "Studio" +msgstr "สตูดิโอ" + +#: ../../content/applications/productivity/studio.rst:17 +msgid "" +"Studio is a toolbox that allows you to customize Odoo without coding " +"knowledge. For example, you can, on any app, add or modify:" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:20 +msgid ":doc:`Fields <studio/fields>`" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:21 +msgid ":doc:`Views <studio/views>`" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:22 +msgid ":doc:`Models <studio/models_modules_apps>`" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:23 +msgid ":doc:`Automated actions <studio/automated_actions>`" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:24 +msgid ":doc:`PDF reports <studio/pdf_reports>`" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:25 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:26 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/productivity/studio.rst:28 +msgid "" +"Or you can :doc:`build an app from scratch <studio/models_modules_apps>`." +msgstr "" + +#: ../../content/applications/productivity/studio.rst:31 +msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:3 +msgid "Automated actions (automations)" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:5 +msgid "" +"Automated actions are used to trigger automatic changes based on user " +"actions (e.g., apply a modification when a field is set to a specific value)" +" or on time conditions (e.g., archive a record 7 days after its last " +"update)." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:9 +msgid "" +"To create an automated action with Studio, go to :guilabel:`Automations` " +"from anywhere within Studio." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:12 +msgid "" +"For every automated action you create, the following elements should be " +"defined: the :ref:`studio/automated-actions/model`, the " +":ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-" +"actions/apply-on`, and the :ref:`studio/automated-actions/action`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an automated action on the Subscription model" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:25 +msgid "Model" +msgstr "โมเดล" + +#: ../../content/applications/productivity/studio/automated_actions.rst:27 +msgid "Select the model where the automated action should be applied." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:30 +msgid "" +"The model you are on when you click on :guilabel:`Automations` is pre-" +"selected by default." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:35 +msgid "Trigger" +msgstr "เปิดใช้งาน" + +#: ../../content/applications/productivity/studio/automated_actions.rst:37 +msgid "" +"Define when the automated action should be applied. Six triggers are " +"available." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:42 +msgid "On Creation" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:44 +msgid "The action is triggered when a record is created and then saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:49 +msgid "On Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:51 +msgid "" +"The action is triggered when a previously saved record is edited and then " +"saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:53 +msgid "" +"Use :guilabel:`Trigger Fields` to specify which fields - and only those - " +"trigger the action on their update." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:55 +msgid "" +"To detect when a record changes from one state to another, define a " +":guilabel:`Before Update Domain` filter, which checks if the condition is " +"satisfied before the record is updated. Then set an :ref:`studio/automated-" +"actions/apply-on` filter, which checks if the condition is met after the " +"record is updated." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:61 +msgid "" +"If you want the automated action to happen when an email address is set on a" +" contact, define the :guilabel:`Before Update Domain` to `Email is not set`," +" and the :guilabel:`Apply on` domain to `Email is set`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of an On Update trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:72 +msgid "On Creation & Update" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:74 +msgid "" +"The action is triggered when a record is created and saved or edited " +"afterward and saved." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:79 +msgid "On Deletion" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:81 +msgid "The action is triggered when a record is deleted." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:84 +msgid "" +"This trigger is rarely used, as archiving records is usually preferred to " +"deletion." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:89 +msgid "Based on Form Modification" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:91 +msgid "" +"The action is triggered when any change is done to a trigger field's value " +"on the :ref:`Form view <studio/views/general/form>`, even before saving the " +"record. This trigger only works on the user interface when a modification is" +" made by a user. If the field is changed through another action and not by " +"the user, the action will not run." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:97 +msgid "" +"This trigger can only be used with the :ref:`Execute Python Code action " +"<studio/automated-actions/action/python-code>`, so development is required." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:103 +msgid "Based on Timed Condition" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:105 +msgid "" +"The action is triggered when a trigger field's date or date & time value is " +"reached." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:107 +msgid "" +"To trigger the action after the :guilabel:`Trigger Date`, add a number of " +"minutes, hours, days, or months under :guilabel:`Delay after trigger date`. " +"To trigger the action before, add a negative number instead." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:112 +msgid "" +"If you want to send a reminder email 30 minutes before the start of a " +"calendar event, select the :guilabel:`Start (Calendar Event)` under " +":guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to" +" **-30** :guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Based on Timed Condition trigger" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:121 +msgid "By default, the scheduler checks for trigger dates every 4 hours." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:126 +msgid "Apply on" +msgstr "ใช้เมื่อ" + +#: ../../content/applications/productivity/studio/automated_actions.rst:128 +msgid "" +"Define on which records of the model the automated action should be applied." +" It works the same way as when you apply filters on a model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:136 +msgid "" +"Determine what the automated action should do (server action). There are " +"eight types of action to choose from." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:142 +msgid "Execute Python Code" +msgstr "รหัส Python" + +#: ../../content/applications/productivity/studio/automated_actions.rst:144 +msgid "" +"The action is used to execute Python code. The available variables are " +"described on the :guilabel:`Python Code` tab, which is also used to write " +"your code, or on the :guilabel:`Help` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:147 +msgid "" +"To allow the action to be run through the website, tick :guilabel:`Available" +" on the Website` and add a :guilabel:`Website Path`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:153 +msgid "Create a new Record" +msgstr "สร้างรายการใหม่" + +#: ../../content/applications/productivity/studio/automated_actions.rst:155 +msgid "The action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:158 +msgid "" +"Selecting a :guilabel:`Target Model` is only required if you want to target " +"another model than the one you are on." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:161 +msgid "" +"To link the record that triggered the creation of the new record, select a " +"field under :guilabel:`Link Field`. For example, you could create a contact " +"automatically when a lead is turned into an opportunity." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:164 +msgid "" +":guilabel:`Data to Write` tab: the tab is used to specify the new record's " +"values. After selecting a :guilabel:`Field`, select its " +":guilabel:`Evaluation Type`:" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:167 +msgid "" +":guilabel:`Value`: used to directly give the field's raw value in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:168 +msgid "" +":guilabel:`Reference`: used to select the record under the " +":guilabel:`Record` column and let Studio add the internal ID in the " +":guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:172 +msgid "" +"If an automated action creates a new task in a project, you can assign it to" +" a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible " +"User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, " +"and the :guilabel:`Record` to a specific user." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create a new Record action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:181 +msgid "" +":guilabel:`Python expression`: used to dynamically define the newly created " +"record’s value for a field using Python code in the :guilabel:`Value` " +"column." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:187 +msgid "Update the Record" +msgstr "อัพเดทรายงาน" + +#: ../../content/applications/productivity/studio/automated_actions.rst:189 +msgid "" +"The action is used to set value(s) for field(s) of any record on the current" +" model." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:192 +msgid "" +"The process to fill in the :guilabel:`Data to Write` tab is the same as " +"described under :ref:`studio/automated-actions/action/new-record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:198 +msgid "Execute several actions" +msgstr "ดำเนินการหลายอย่าง" + +#: ../../content/applications/productivity/studio/automated_actions.rst:200 +msgid "" +"The action is used to trigger multiple actions at the same time. To do so, " +"click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the " +":guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure " +"the action." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:207 +msgid "Send Email" +msgstr "ส่งอีเมล" + +#: ../../content/applications/productivity/studio/automated_actions.rst:209 +msgid "" +"The action is used to send an email to a contact linked to a specific " +"record. To do so, select or create an :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:215 +msgid "Add Followers" +msgstr "เพิ่มผู้ติดตาม" + +#: ../../content/applications/productivity/studio/automated_actions.rst:217 +msgid "The action is used to subscribe existing contacts to the record." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:222 +msgid "Create Next Activity" +msgstr "สร้างกิจกรรมถัดไป" + +#: ../../content/applications/productivity/studio/automated_actions.rst:224 +msgid "" +"The action is used to schedule a new activity linked to the record. Use the " +":guilabel:`Activity` tab to set it up as usual, but instead of the " +":guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. " +"Select :guilabel:`Specific User` and add the user under " +":guilabel:`Responsible` if the activity should always be assigned to the " +"same user. To dynamically target a user linked to the record, select " +":guilabel:`Generic User From Record` instead and change the :guilabel:`User " +"field name` if necessary." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:232 +msgid "" +"After a lead is turned into an opportunity, you want your automated action " +"to set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity " +"User Type` to :guilabel:`Generic User From Record`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:0 +msgid "Example of a Create Next Activity action" +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:243 +msgid "Send SMS Text Message" +msgstr "ส่งข้อความ SMS" + +#: ../../content/applications/productivity/studio/automated_actions.rst:245 +msgid "" +"The action is used to send an SMS to a contact linked to the record. To do " +"so, select or create an :guilabel:`SMS Template`." +msgstr "" + +#: ../../content/applications/productivity/studio/automated_actions.rst:249 +msgid "" +"If you want sent messages to be logged in the Chatter, tick :guilabel:`Log " +"as Note`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:26 +#: ../../content/applications/productivity/studio/fields.rst:325 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:36 +#: ../../content/applications/productivity/studio/fields.rst:220 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:38 +#: ../../content/applications/productivity/studio/fields.rst:71 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"<studio/fields/simple-fields/image>` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:66 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:68 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:82 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:84 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:87 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:89 +#: ../../content/applications/productivity/studio/fields.rst:118 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:91 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view <studio/views/multiple-records/list>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:103 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:105 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:109 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:112 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"<studio/fields/simple-fields/monetary>`. It is recommended to use the later " +"as it offers more functionalities." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:115 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:116 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:120 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:131 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:133 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:136 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:149 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:151 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:153 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:164 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:166 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:168 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:180 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:182 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:185 +msgid "" +":guilabel:`Date`: used to record the time without displaying it on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:186 +msgid "" +":guilabel:`Remaining days`: displays the remaining number of days before the" +" selected date (e.g., *In 5 days*), based on the current date and time." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:198 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:200 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:203 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:204 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:215 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:217 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:222 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:224 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field <studio/fields/simple-" +"fields/priority>`, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:228 +#: ../../content/applications/productivity/studio/fields.rst:352 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:231 +msgid "" +"By default, radio buttons are organized vertically. Tick :guilabel:`display " +"horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:243 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:245 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field <studio/fields/simple-" +"fields/selection>` with the :guilabel:`Priority` widget selected by default " +"and four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"<studio/fields/simple-fields/selection>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:253 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:266 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:268 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:271 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view <studio/views/general/form>`. This has the same effect as" +" using the :ref:`Image field <studio/fields/simple-fields/image>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:274 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view <studio/views/general/form>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:276 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field <studio/fields/simple-" +"fields/sign>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:288 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:290 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view <studio/views/general/form>`. This field type is a " +":ref:`File field <studio/fields/simple-fields/file>` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File <studio/fields/simple-" +"fields/file>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:297 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:303 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:305 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field <studio/fields/simple-fields/file>` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File <studio/fields/simple-" +"fields/file>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:311 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text <studio/fields/simple-fields/text>`, :ref:`Many2One " +"<studio/fields/relational-fields/many2one>`, and :ref:`Related Field " +"<studio/fields/relational-fields/related-field>` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:320 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:322 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:330 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:332 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:336 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:345 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:347 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:348 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:350 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:357 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:359 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:363 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:371 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field <studio/fields/relational-" +"fields/many2one>`. One2Many relations do not exist independently: a reverse-" +"search of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:378 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:380 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:384 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:397 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:399 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"<studio/fields/relational-fields/many2one>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:405 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:413 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:414 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field <studio/fields/relational-fields/tags>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:421 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:423 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field <studio/fields/relational-fields/many2many>` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many <studio/fields/relational-" +"fields/many2many>`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:430 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:441 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:443 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:447 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:455 +msgid "" +":guilabel:`Invisible`: When it is not necessary for users to view a field on" +" the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing " +"the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:460 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:465 +msgid "" +"The :guilabel:`Invisible` attribute also applies to Studio. To view hidden " +"fields inside Studio, click on a view's :guilabel:`View` tab and tick " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:469 +msgid "" +":guilabel:`Required`: If a field should always be completed by the user " +"before being able to proceed, tick :guilabel:`Required`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:471 +msgid "" +":guilabel:`Read only`: If users should not be able to modify a field, tick " +":guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:474 +msgid "" +"You can choose to apply these three properties only for specific records by " +"clicking on :guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:477 +msgid "" +":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:480 +msgid "" +"This is not the same name as used in the PostgreSQL database. To view and " +"change the latter, activate the :ref:`Developer mode <developer-mode>`, and " +"edit the :guilabel:`Technical Name`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:483 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, write a " +"description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip" +" box when hovering with your mouse over the field's label." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:486 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, write it under :guilabel:`Placeholder`. It is displayed in light " +"gray in lieu of the field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:488 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:490 +msgid "" +":guilabel:`Default value`: To add a default value to a field when a record " +"is created, use :guilabel:`Default value`." +msgstr "" + +#: ../../content/applications/productivity/studio/fields.rst:492 +msgid "" +":guilabel:`Limit visibility to groups`: To limit which users can see the " +"field, select a user access group." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view <studio/views/multiple-records/kanban>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "รายละเอียดการติดต่อ" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"<studio/views/general/form>` a :ref:`Many2One field " +"<studio/fields/relational-fields/many2one>` linked to the *Contact* model " +"and two of its :ref:`Related Fields <studio/fields/relational-" +"fields/related-field>`: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"<studio/views/multiple-records/list>`, and the :ref:`Map view " +"<studio/views/multiple-records/map>` is activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "การมอบหมายผู้ใช้" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"<studio/views/general/form>` a :ref:`Many2One field " +"<studio/fields/relational-fields/many2one>` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view <studio/views/multiple-records/list>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "วันที่และปฏิทิน" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"<studio/views/general/form>` a :ref:`Date field <studio/fields/simple-" +"fields/date>` and activates the :ref:`Calendar view " +"<studio/views/timeline/calendar>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "ช่วงวันที่และแกนต์" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"<studio/views/general/form>` two :ref:`Date fields <studio/fields/simple-" +"fields/date>` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view <studio/views/timeline/gantt>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "ขั้นตอนไปป์ไลน์" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"<studio/views/multiple-records/kanban>`, adds several fields such as " +":ref:`Priority <studio/fields/simple-fields/priority>` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"<studio/views/general/form>`. The :guilabel:`Color` field is added to the " +":ref:`List view <studio/views/multiple-records/list>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "แท็ก" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"<studio/fields/relational-fields/tags>`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "รูปภาพ" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"<studio/views/general/form>` an :ref:`Image field <studio/fields/simple-" +"fields/image>`." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "รายการ" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"<studio/views/general/form>` a :ref:`Lines field <studio/fields/relational-" +"fields/lines>` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "โน้ต" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"<studio/views/general/form>` an :ref:`Html field <studio/fields/simple-" +"fields/html>` using the full width of the form." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "ค่าของเงิน" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field <studio/fields/simple-" +"fields/monetary>`. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "บริษัท" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"<studio/fields/relational-fields/many2one>` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "การเรียงลำดับแบบกำหนดเอง" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"<studio/views/multiple-records/list>` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "แชท" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"<studio/views/general/form>` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "กำลังเก็บถาวร" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +":guilabel:`Studio customizations` is added to your database." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:217 +msgid "" +"To export these customizations, go to :menuselection:`Main dashboard --> " +"Studio --> Customizations --> Export` to download a ZIP file containing all " +"customizations." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:220 +msgid "" +"To import and install these customizations in another database, connect to " +"the destination database and go to :menuselection:`Main dashboard --> Studio" +" --> Customizations --> Import`, then upload the exported ZIP file before " +"clicking on the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/productivity/studio/models_modules_apps.rst:225 +msgid "" +"Before importing, make sure the destination database contains the same apps " +"and modules as the source database. Studio does not add the underlying " +"modules as dependencies of the exported module." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can edit existing PDF reports (e.g., orders and quotations)" +" or create new ones." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:8 +msgid "" +"To edit a standard PDF report, it is strongly recommended to **duplicate** " +"it and make changes to the duplicated version, as changes made to standard " +"reports will be overwritten after an Odoo upgrade. To duplicate a report, go" +" to :menuselection:`Studio --> Reports`. Hover the mouse pointer on the top " +"right corner of the report, click the vertical ellipsis icon " +"(:guilabel:`⋮`), and then select :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:20 +msgid "Default layout" +msgstr "เค้าโครงเริ่มต้น" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:22 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings --> Companies: Document Layout --> Configure " +"Document Layout`. Layout settings apply to all reports but only to the " +"current company." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:27 +msgid "" +"Use :guilabel:`Download PDF Preview` to view how the different settings " +"affect the layout of a sample invoice." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:33 +msgid "Layout" +msgstr "เค้าโครง" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:35 +msgid "Four layouts are available." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:39 +msgid "Light" +msgstr "อ่อน" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:44 +msgid "Boxed" +msgstr "กล่อง" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:49 +msgid "Bold" +msgstr "ตัวหนา" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:54 +msgid "Striped" +msgstr "Striped" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:62 +msgid "Font" +msgstr "ฟอนต์" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:64 +msgid "" +"Seven fonts are available. Click on the links below to preview them on " +"`Google Fonts <https://fonts.google.com/>`_." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:67 +msgid "`Lato <https://fonts.google.com/specimen/Lato#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:68 +msgid "`Roboto <https://fonts.google.com/specimen/Roboto#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:69 +msgid "`Open Sans <https://fonts.google.com/specimen/Open+Sans#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:70 +msgid "" +"`Montserrat <https://fonts.google.com/specimen/Montserrat#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:71 +msgid "`Oswald <https://fonts.google.com/specimen/Oswald#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:72 +msgid "`Raleway <https://fonts.google.com/specimen/Raleway#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:73 +msgid "`Tajawal <https://fonts.google.com/specimen/Tajawal#type-tester>`_" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:76 +msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:81 +msgid "Company logo" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:83 +msgid "Upload an image file to add a :guilabel:`Company Logo`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:86 +msgid "" +"This adds the logo to the company’s record on the *Company* model, which you" +" can access by going to :menuselection:`General Settings --> Companies --> " +"Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:92 +msgid "Colors" +msgstr "สี" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:94 +msgid "" +"Change the primary and secondary colors used throughout reports to highlight" +" important elements. The default colors are automatically generated based on" +" the colors of the logo." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:100 +msgid "Layout background" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:102 +msgid "Change the :guilabel:`Layout Background` of the report:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:104 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:105 +msgid "" +":guilabel:`Geometric`: an image featuring geometric shapes is displayed in " +"the background." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:106 +msgid ":guilabel:`Custom`: use a custom background image by uploading one." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:111 +msgid "Company tagline" +msgstr "สโลแกนของบริษัท" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:113 +msgid "" +"The :guilabel:`Company Tagline` is displayed on the header of :ref:`External" +" reports <studio/pdf-reports/header-footer/external>`. You can add multiple " +"lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:119 +msgid "Company details" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:121 +msgid "" +"The :guilabel:`Company Details` are displayed on the header of " +":ref:`External reports <studio/pdf-reports/header-footer/external>`. You can" +" add multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:127 +msgid "Footer" +msgstr "ส่วนท้าย" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:129 +msgid "" +"Use the :guilabel:`Footer` field to put any text in the :ref:`External " +"reports' <studio/pdf-reports/header-footer/external>` footers. You can add " +"multiple lines of text." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:135 +msgid "Paper format" +msgstr "รูปแบบกระดาษ" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:137 +msgid "" +"Use the :guilabel:`Paper format` field to change the paper size of reports. " +"You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US " +"Letter` (21.59 cm x 27.54 cm)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:141 +msgid "" +"You can change the :guilabel:`Paper format` on individual reports. Open the " +"app containing the report, then go to :menuselection:`Studio --> Reports -->" +" Select or Create a report --> Report --> Select a Paper format`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Configuration pop-up window for the default layout of PDF reports" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:151 +msgid "Header and footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:153 +msgid "" +"When creating a new report in Studio, you must choose between one of three " +"styles of reports first. This is solely used to determine what is displayed " +"on the header and footer. To do so, go to the app on which you want to add a" +" new report, click the **Toggle Studio** button, then click " +":guilabel:`Reports`. Click :guilabel:`New` and select :ref:`studio/pdf-" +"reports/header-footer/external`, :ref:`studio/pdf-reports/header-" +"footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:163 +msgid "External" +msgstr "ภายนอก" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:165 +msgid "" +"The header displays the company :ref:`studio/pdf-reports/default-" +"layout/logo` and several values set on the *Company* model: the " +":guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and " +":guilabel:`Website`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:170 +msgid "" +"To change a company's information, go to :menuselection:`Settings --> " +"Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External header" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:175 +msgid "" +"The footer displays the values set on the :ref:`studio/pdf-reports/default-" +"layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and " +":ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page" +" number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "Example of an External footer" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:185 +msgid "Internal" +msgstr "ภายใน" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:187 +msgid "" +"The header displays the user's current date and time, :guilabel:`Company " +"Name`, and page number." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:189 +msgid "There is no footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:194 +msgid "Blank" +msgstr "ว่าง" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:196 +msgid "There is neither a header nor a footer." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:201 +msgid "Add tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:203 +msgid "" +"After opening an existing report or creating a new one, go to the " +":guilabel:`Add` tab to add or edit elements. The elements are organized into" +" four categories: :ref:`studio/pdf-reports/elements/block`, " +":ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-" +"reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:211 +msgid "Block" +msgstr "บล็อก" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:213 +msgid "" +"Block elements start on a new line and occupy the full width of the page." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:216 +msgid "" +"You can set an element's width by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:218 +#: ../../content/applications/productivity/studio/pdf_reports.rst:247 +msgid ":guilabel:`Text`: add any text using small font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:220 +msgid "" +":guilabel:`Title Block`: add any text using larger font size by default." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:222 +msgid "" +":guilabel:`Image`: add an image. You can either upload one from your device," +" add one from an URL, or select one already existing on your database." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:225 +#: ../../content/applications/productivity/studio/pdf_reports.rst:249 +msgid ":guilabel:`Field`: dynamically add a field's value." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:227 +msgid "" +":guilabel:`Field & Label`: to dynamically add a field's value and label." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:229 +msgid "" +":guilabel:`Address Block`: to dynamically add the values, if any, of a " +"contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and " +"*Email*." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of an Address Block" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:238 +msgid "Inline" +msgstr "อินไลน์" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:240 +msgid "" +"Inline elements are used around other elements. They do not start on a new " +"line and the width adapts to length of the content." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:244 +msgid "" +"You can set an element's width and margins by selecting it and going to the " +":guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:254 +msgid "Table" +msgstr "โต๊ะ" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:256 +msgid "Table elements are used together to create a data table." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:258 +msgid "" +":guilabel:`Data table`: create a table and dynamically add a first column " +"displaying the *Name* values of a :ref:`Many2Many <studio/fields/relational-" +"fields/many2many>` or :ref:`One2Many <studio/fields/relational-" +"fields/one2many>` field on your model." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:0 +msgid "Example of a Data table" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:265 +msgid "" +":guilabel:`Field Column`: add a new column to the table displaying the " +"values of a :ref:`Related Field <studio/fields/relational-fields/related-" +"field>` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:269 +msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:271 +msgid "" +":guilabel:`Field in Cell`: add, within an existing table cell, the values of" +" a :ref:`Related Field <studio/fields/relational-fields/related-field>` to " +"the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:275 +msgid "" +":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's " +"value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts " +"are added before the total amount." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:281 +msgid "Column" +msgstr "คอลัมน์" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:283 +msgid "" +"Columns are used to add multiple :ref:`blocks <studio/pdf-" +"reports/elements/block>` elements on the same line." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:286 +msgid ":guilabel:`Two Columns`: add any text in two different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:288 +msgid ":guilabel:`Three Columns`: add any text in three different columns." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:291 +msgid "Report tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:293 +msgid "" +"Several configuration options are available under the :guilabel:`Report` " +"tab." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:295 +msgid "" +":guilabel:`Name`: change the report name. The new name is applied everywhere" +" (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:298 +msgid ":guilabel:`Paper format`: change the paper size of the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:300 +msgid "" +":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` " +"button available on the record." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:303 +msgid "" +":guilabel:`Limit visibility to groups`: limit the availability of the PDF " +"report to specific :doc:`user groups <../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:307 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:309 +msgid "" +"Select an element on the report to access the element's options and edit it." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst-1 +msgid "The Options tab for a text element" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:315 +msgid "" +"You can select and edit multiple elements at the same time by clicking on " +"the different sections or divisions (e.g., `div`, `table`, etc.)." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:318 +msgid "Below are presented some of the most common options:" +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:320 +msgid "" +":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, " +":guilabel:`bottom`, and :guilabel:`left` of the element." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:323 +msgid ":guilabel:`Width`: set the element's maximum width." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:325 +msgid "" +":guilabel:`Visible if`: set under which condition(s) the element should be " +"displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:327 +msgid "" +":guilabel:`Visible for`: set for which :doc:`users groups " +"<../../general/users/access_rights>` the element should be displayed." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:330 +msgid "" +":guilabel:`Remove from View`: remove the element from the report's view." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:332 +msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:334 +msgid "" +":guilabel:`Alignment`: align the element to the left, center, or right of " +"the report." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:336 +msgid ":guilabel:`Font style`: use one of the default font styles." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:338 +msgid ":guilabel:`Colors`: change the font's color and the background color." +msgstr "" + +#: ../../content/applications/productivity/studio/pdf_reports.rst:341 +msgid "" +"You may need to select a section or division above the element you want to " +"edit to see some of the options described above." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:3 +msgid "Views" +msgstr "มุมมอง" + +#: ../../content/applications/productivity/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +"model. One model can have several views, which are simply different ways to " +"show the same data. In Studio, views are organized into four categories: " +":ref:`general <studio/views/general>`, :ref:`multiple records " +"<studio/views/multiple-records>`, :ref:`timeline <studio/views/timeline>`, " +"and :ref:`reporting <studio/views/reporting>`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:12 +msgid "" +"To change the default view of a model, go to :menuselection:`Studio --> " +"Views --> Dropdown menu (⋮) --> Set as Default`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:16 +msgid "" +"You can modify views by using the built-in XML editor. To do so, activate " +":ref:`Developer mode <developer-mode>`, go to the view you want to edit, " +"select the :guilabel:`View` tab and then click on :guilabel:`</> XML`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:21 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard views and inherited views, as those would be reset and " +"would not be kept in case of an update or module upgrade. Always make sure " +"you select the right Studio inherited views. Indeed, when you modify a view " +"in Studio by drag-and-dropping a new field, a specific Studio inherited view" +" and its XPath, the latter which defines which part of the view is modified," +" are automatically generated." +msgstr "" +"หากคุณกำลังแก้ไขมุมมองโดยใช้ตัวแก้ไข XML " +"ให้หลีกเลี่ยงการเปลี่ยนแปลงโดยตรงกับมุมมองมาตรฐานและมุมมองที่สืบทอดมา " +"เนื่องจากการเปลี่ยนแปลงเหล่านั้นจะถูกรีเซ็ตและจะไม่ถูกเก็บไว้ในกรณีของการอัปเดตหรือการอัปเกรดโมดูล" +" ตรวจสอบให้แน่ใจว่าคุณเลือกมุมมองที่สืบทอดมาจากสตูดิโอที่ถูกต้องเสมอ " +"เมื่อคุณแก้ไขมุมมองในสตูดิโอ โดยการลากและวางฟิลด์ใหม่ มุมมองสตูดิโอ " +"ที่สืบทอดมาโดยเฉพาะและ XPath ของสตูดิโอดังกล่าว " +"ซึ่งกำหนดส่วนใดของมุมมองที่ได้รับการแก้ไขจะถูกสร้างขึ้นโดยอัตโนมัติ" + +#: ../../content/applications/productivity/studio/views.rst:31 +msgid "General views" +msgstr "มุมมองทั่วไป" + +#: ../../content/applications/productivity/studio/views.rst:34 +#: ../../content/applications/productivity/studio/views.rst:97 +#: ../../content/applications/productivity/studio/views.rst:195 +#: ../../content/applications/productivity/studio/views.rst:311 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:40 +msgid "Form" +msgstr "ฟอร์ม" + +#: ../../content/applications/productivity/studio/views.rst:42 +msgid "" +"The :guilabel:`Form` view is used when creating and editing records, such as" +" contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:45 +msgid "" +"To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:47 +#: ../../content/applications/productivity/studio/views.rst:132 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:59 +msgid "Activity" +msgstr "กิจกรรม" + +#: ../../content/applications/productivity/studio/views.rst:61 +msgid "" +"The :guilabel:`Activity` view is used to schedule and have an overview of " +"activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:65 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:76 +msgid "Search" +msgstr "ค้นหา" + +#: ../../content/applications/productivity/studio/views.rst:78 +msgid "" +"The :guilabel:`Search` view is added on top of other views to filter, group," +" and search records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:80 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:82 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:94 +msgid "Multiple records views" +msgstr "มุมมองบันทึกหลายรายการ" + +#: ../../content/applications/productivity/studio/views.rst:103 +msgid "Kanban" +msgstr "คัมบัง" + +#: ../../content/applications/productivity/studio/views.rst:105 +msgid "" +"The :guilabel:`Kanban` view is often used to support business flows by " +"moving records across stages or as an alternative way to display records " +"inside *cards*." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:109 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view <studio/views/multiple-" +"records/list>`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:112 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:113 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:115 +msgid "" +"To change the way records are grouped by default, select a new group under " +":guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:127 +msgid "List" +msgstr "รายการ" + +#: ../../content/applications/productivity/studio/views.rst:129 +msgid "" +"The :guilabel:`List` view is used to overview many records at once, look for" +" records, and edit simple records." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:134 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`New record on top` or :guilabel:`New record at the bottom` under " +":guilabel:`Editable`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:138 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"<studio/views/general/form>` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:141 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:142 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:145 +msgid "" +"To add a drag handle icon to reorder records manually, add an :ref:`Integer " +"field <studio/fields/simple-fields/integer>` with the :guilabel:`Handle` " +"widget." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:161 +msgid "Map" +msgstr "แผนที่" + +#: ../../content/applications/productivity/studio/views.rst:163 +msgid "" +"The :guilabel:`Map` view is used to display records on a map. For example, " +"it is used in the Field Service app to plan an itinerary between different " +"tasks." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:167 +msgid "" +"A :ref:`Many2One field <studio/fields/relational-fields/many2one>` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:170 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:172 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:174 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:175 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:187 +msgid "Timeline views" +msgstr "มุมมองไทม์ไลน์" + +#: ../../content/applications/productivity/studio/views.rst:190 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date <studio/fields/simple-fields/date>` or :ref:`Date & Time " +"<studio/fields/simple-fields/date-time>` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:203 +msgid "" +"The :guilabel:`Calendar` view is used to overview and manage records inside " +"a calendar." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:205 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view <studio/views/general/form>`, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:209 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:213 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:217 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:220 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field <studio/fields/simple-fields/checkbox>` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:223 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:227 +msgid "" +"You can also use :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal <studio/fields/simple-" +"fields/decimal>` or :ref:`Integer <studio/fields/simple-fields/integer>` " +"field on the model which specifies the duration of the event. However, if " +"you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not " +"be taken into account." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:242 +msgid "Cohort" +msgstr "หมู่คณะ" + +#: ../../content/applications/productivity/studio/views.rst:244 +msgid "" +"The :guilabel:`Cohort` view is used to examine the life cycle of records " +"over a time period. For example, it is used in the Subscriptions app to view" +" the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:247 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:249 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:251 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:255 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:268 +msgid "Gantt" +msgstr "แกนต์" + +#: ../../content/applications/productivity/studio/views.rst:270 +msgid "" +"The :guilabel:`Gantt` view is used to forecast and examine the overall " +"progress of records. Records are represented by a bar under a time scale." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:273 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:275 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:279 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:282 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:283 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:284 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:286 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:288 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:292 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:294 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:308 +msgid "Reporting views" +msgstr "การรายงานมุมมอง" + +#: ../../content/applications/productivity/studio/views.rst:317 +msgid "Pivot" +msgstr "หมุน" + +#: ../../content/applications/productivity/studio/views.rst:319 +msgid "" +"The :guilabel:`Pivot` view is used to explore and analyze the data contained" +" in records in an interactive manner. It is especially useful to aggregate " +"numeric data, create categories, and drill down the data by expanding and " +"collapsing different levels of data." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:323 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:325 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:327 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:329 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:341 +msgid "Graph" +msgstr "กราฟ" + +#: ../../content/applications/productivity/studio/views.rst:343 +msgid "" +"The :guilabel:`Graph` view is used to showcase data from records in a bar, " +"line, or pie chart." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:345 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:347 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:349 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:351 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:354 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:356 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:368 +msgid "Dashboard" +msgstr "แดชบอร์ด" + +#: ../../content/applications/productivity/studio/views.rst:370 +msgid "" +"The :guilabel:`Dashboard` view is used to display multiple reporting views " +"and key performance indicators. Which elements are displayed on the view " +"depends on the configuration of the other reporting views." +msgstr "" + +#: ../../content/applications/productivity/studio/views.rst:0 +msgid "Sales Analysis Report model's Dashboard view" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:3 +msgid "To-do" +msgstr "To-do" + +#: ../../content/applications/productivity/to_do.rst:5 +msgid "To-do assists you in organizing and managing personal tasks." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:8 +msgid "Creating to-dos" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:10 +msgid "" +"To create a to-do, click :guilabel:`New` or the plus button (:guilabel:`➕`) " +"next to a stage name. Add a title to your to-do, then click :guilabel:`Add` " +"to save it or :guilabel:`Edit` to access more options." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:14 +msgid "" +"If you choose to :guilabel:`Edit` a to-do, you have the option to add " +":guilabel:`Tags`, :guilabel:`Assignees`, or more information using the Odoo " +"Editor." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:18 +msgid "Adding :guilabel:`Assignees` shares the to-do with the users selected." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:19 +msgid "" +"Type `/` in the editor box to structure and format your content. You can " +"also add media, links, and widgets." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:23 +msgid "" +"You can create a new to-do on the fly from anywhere in Odoo by opening the " +"**command palette tool** with the keyboard shortcut ´ctrl+k´ and clicking " +":guilabel:`Add a To-Do`, or by clicking the clock button and then " +":guilabel:`Add a To-Do`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:0 +msgid "Adding a to-do on the fly" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:31 +msgid "Converting to-dos into project tasks" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:33 +msgid "" +"If you use the :doc:`Project app <../services/project>`, you can convert to-" +"dos into project tasks. To do so, open a to-do and click the gear button " +"(:guilabel:`⚙`), then :guilabel:`Convert to Task`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:36 +msgid "" +"Next, select the :guilabel:`Project`, :guilabel:`Assignees`, and " +":guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a" +" project task and appears in the selected project." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Converting a to-do into a task" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:43 +msgid "Managing the to-do pipeline" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:45 +msgid "" +"Your assigned **to-dos** are displayed on the app dashboard. You can drag " +"and drop a to-do to move it from one stage to another." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Example of a to-do pipeline" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:52 +msgid "" +"Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to" +" create a new stage." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:54 +msgid "" +"Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, " +":guilabel:`Edit`, or :guilabel:`Delete` it." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:0 +msgid "Stage settings button" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:61 +msgid "Scheduling activities" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:63 +msgid "" +"To schedule an activity on a to-do, click the clock button on the app " +"dashboard, then the :guilabel:`+ Schedule an activity` button." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Scheduling an activity from the To-do dashboard" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:69 +msgid "To create the activity:" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:71 +msgid "Select an :guilabel:`Activity Type`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:72 +msgid "Select a :guilabel:`Due date`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:73 +msgid "Choose who the activity should be :guilabel:`Assigned to`." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:74 +msgid "" +"Add a brief :guilabel:`Summary` if needed. You can add a more elaborate " +"description in the :guilabel:`Log a note` box." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:77 +msgid "Click :guilabel:`Schedule` to complete the action." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:80 +msgid "" +"The :guilabel:`To Do` activity is *not* a to-do task. Selecting it does not " +"create a to-do task." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:83 +msgid "Viewing to-dos in the Project app" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:85 +msgid "" +"If you use the :doc:`Project app <../services/project>`, your to-dos also " +"appear as private tasks under the :guilabel:`My Tasks` view." +msgstr "" + +#: ../../content/applications/productivity/to_do.rst-1 +msgid "Example of a \"My Tasks\" pipeline in the Project app" +msgstr "" + +#: ../../content/applications/productivity/to_do.rst:92 +msgid "" +"A padlock icon is visible on your private tasks to quickly identify them " +"among your project tasks." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:3 +msgid "WhatsApp" +msgstr "WhatsApp" + +#: ../../content/applications/productivity/whatsapp.rst:5 +msgid "" +"**WhatsApp** is an instant messaging and voice-over-IP app that allows users" +" to send messages, make calls, and share content. Businesses can use " +"`WhatsApp Business <https://developers.facebook.com/products/whatsapp/>`_ to" +" communicate with their customers by text, send documents and provide " +"support." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:10 +msgid "" +"With the **Odoo WhatsApp** app, a company can connect a WhatsApp Business " +"Account (WABA) to an Odoo database, which allows for the following:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:13 +msgid "Receive and reply to WhatsApp messages directly from an Odoo database" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:14 +msgid "Create new templates with dynamic placeholders/variables" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:15 +msgid "Send pre-approved templates that use dynamic variables, such as:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:17 +msgid "Quotations from the Sales app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:18 +msgid "Receipts and invoices from the Point of Sale app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:19 +msgid "Tickets from the Events app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:22 +msgid "" +"`Meta Business: create message templates for the WhatsApp Business account " +"<https://www.facebook.com/business/help/2055875911147364>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:24 +msgid "" +"`Meta Business: connect a phone number to the WhatsApp Business account " +"<https://www.facebook.com/business/help/456220311516626>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:26 +msgid "" +"`Meta Business: change the WhatsApp Business display name " +"<https://www.facebook.com/business/help/378834799515077>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:29 +msgid "" +"WhatsApp is a messaging service operated by Meta, which is the parent " +"company of Facebook. WhatsApp is commonly used as a communication tool in " +"many countries and by many businesses. This documentation will cover the " +"integration of a WhatsApp Business Account with Odoo. The company's Meta " +"account is configured in Odoo via an :abbr:`API (Application Programming " +"Interface)` connection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:35 +msgid "" +"The WhatsApp connector supports two flows: company initiated, and customer " +"initiated. A company can initiate a discussion by sending a template to one " +"or more people. Once the template is sent, the recipient can answer in order" +" to trigger a discussion between the sender and the receiver (a *Discuss* " +"chat window will pop up if the customer answers within 15 days)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:40 +msgid "" +"If the discussion is initiated by the client (e.g. by sending to the " +"company's public WhatsApp number), then Odoo will open a group chat with all" +" operators responsible for this WhatsApp channel." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:44 +msgid "" +"It is recommended to set up multiple WhatsApp accounts for different " +"departments. For example, the help desk team and sales teams can chat on " +"different channels." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:48 +msgid "WhatsApp configuration in a Meta" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:50 +msgid "" +"A WhatsApp integration with Odoo uses a standard :abbr:`API (Application " +"Programming Interface)` connection, and is configured on Meta in the " +"following steps:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:53 +msgid "Create a Meta business account" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:54 +msgid "Create a Meta developer account" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:55 +msgid "Setup an *app* and WhatsApp *product* on Meta's developer console" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:56 +msgid "Test the API connection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:58 +msgid "" +"Once connected, messages are then sent and received through Odoo's *Discuss*" +" application using the WhatsApp :abbr:`API (Application Programming " +"Interface)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:62 +msgid "Meta business account setup" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:64 +msgid "" +"To create a Business account with Meta (owner of Facebook) navigate to: " +"`Facebook Business Manager <https://business.facebook.com/overview>`_. Begin" +" by clicking :guilabel:`Create account` and then enter the business name, " +"the administrator's name, and a work email address. Then click " +":guilabel:`Next`, and a pop-up window will appear prompting to confirm the " +"email address. After confirming, click :guilabel:`Done` to close the window." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:70 +msgid "" +"Next, follow the instructions in the email sent by Facebook to confirm the " +"creation of the business account and to complete the setup process." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:74 +msgid "" +"`Set up a Meta business account " +"<https://www.facebook.com/business/help/1710077379203657?id=180505742745347>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:78 +msgid "" +"If the business account is linked to a personal Facebook account then the " +"administrator must toggle between the personal account to the business " +"account for the remainder of the configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:82 +msgid "" +"To toggle to the business account navigate to the `Facebook Developer " +"Console <https://developers.facebook.com>`_ and click on the *account name* " +"in the upper right corner. Under the :guilabel:`Business Accounts` heading, " +"click on the desired business that the WhatsApp configuration should take " +"place in. This will be the account for which Odoo will send and receive " +"WhatsApp messages." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Toggle between Meta personal and business accounts." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:93 +msgid "" +"In order to create a Meta business account, the user must already have a " +"personal Facebook account that has existed for a minimum of one hour prior " +"to setting up the Facebook Business account. Trying to create the business " +"account prior to this time will result in an error." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:98 +msgid "App creation" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:100 +msgid "" +"On the `Meta for Developers <https://developers.facebook.com>`_ dashboard, " +"sign in with the Meta developer account. If no account is configured yet, " +"link a Facebook account to create a Meta developer account." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:105 +msgid "" +"A Facebook *developer* account is different than a Facebook *business* " +"account. While developer accounts are made up of personal Facebook accounts," +" business accounts are **not** as they represent a business and manage all " +"of the business's assets in Meta, such as apps." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:110 +msgid "" +"`Set up the WhatsApp Business Platform " +"<https://www.facebookblueprint.com/student/collection/409587/path/360218>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:113 +msgid "" +"Click on :guilabel:`My Apps` in the top right corner after successfully " +"signing in to the Meta developer account. This will redirect the " +"administrator to all the apps the developer has configured in this specific " +"developer account. Click on :guilabel:`Create App` to begin the process of " +"configuring a new Meta application." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:119 +msgid "App type" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:121 +msgid "" +"On the :menuselection:`Create an app` page, select :guilabel:`Other` under " +"the section labeled, :guilabel:`Looking for something else?`, and then click" +" :guilabel:`Next` to be directed to another page in order to select the app " +"type. Then, click on the first option listed under the :guilabel:`Select an " +"app type` label, titled :guilabel:`Business`. This selection allows for the " +"creation and management of the WhatsApp :abbr:`API (Application Programming " +"Interface)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:127 +msgid "" +"Now, click :guilabel:`Next` to configure the app, as desired. When the app " +"*type* has been configured, the administrator will move onto the app " +"*details* section." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:131 +msgid "App details" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:133 +msgid "" +"On the :guilabel:`Details` section of the :guilabel:`Create an app` process," +" enter `Odoo` in the field under the :guilabel:`Add an app name` label." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:137 +msgid "" +"The app name can be changed at a later time in the settings, if necessary." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:140 +msgid "" +"Trademarks and branded elements may not be used in this text section. These " +"include the Meta group of companies. Do not include the word: `WhatsApp` or " +"the system will flag this in error." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:143 +msgid "" +"Next, enter the developer email address in the field under the " +":guilabel:`App contact email` label." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:145 +msgid "" +"Lastly, set the :guilabel:`Business Account - Optional` field to the Meta " +"business account profile, using the drop-down menu. To finish, click " +":guilabel:`Create app`. This action will create the app and prompts the " +"*Meta Platform Terms* and *Developer Policies* agreements." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:149 +msgid "" +"To accept the agreements, enter the Facebook password for security purposes," +" and click :guilabel:`Submit` to finalize the app creation. The browser will" +" then direct to the :guilabel:`Meta for Developers` dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:154 +msgid "" +"If the Meta business account is prohibited from advertising, claiming an app" +" won't be allowed. To resolve this issue navigate to " +"`<https://business.facebook.com/business>`_ for assistance." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:157 +msgid "" +"For more information, see `Meta's documentation on advertising restrictions " +"<https://www.facebook.com/business/help/975570072950669>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:161 +msgid "Add a WhatsApp product to the app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:163 +msgid "" +"Now that the basic structure of the app has been created, a product will " +"need to be added to the app. Begin by accessing the Meta app dashboard by " +"navigating to `<https://developers.facebook.com/apps>`_, and clicking on the" +" app that is being configured." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:167 +msgid "" +"On the next page: since WhatsApp will be used, click :guilabel:`Set up` next" +" to the box containing WhatsApp, located towards the bottom of the page." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:171 +msgid "" +"`Meta's WhatsApp developer documentation " +"<https://developers.facebook.com/docs/whatsapp/>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:173 +msgid "" +"The page then directs to the configuration page for the :guilabel:`WhatsApp " +"Business Platform API`. Use the drop-down menu to select the Meta business " +"to be configured for the :guilabel:`Select a Meta Business Account` option, " +"and then click :guilabel:`Continue` to confirm the selection." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:178 +msgid "" +"When :guilabel:`Continue` is clicked, the administrator agrees to Meta's " +"terms and conditions as linked on the :guilabel:`Meta App Dashboard`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:182 +msgid "" +"Once the WhatsApp product is added to the app, Meta will provide a WhatsApp " +"test phone number with 5 test messages." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:186 +msgid "Start using the WhatsApp API" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:188 +msgid "" +"After finishing the previous WhatsApp product wizard, and clicking " +":guilabel:`Continue`, the browser should have directed to the WhatsApp " +":guilabel:`Quickstart` page; this :guilabel:`Quickstart` page is where to " +"begin configuring the WhatsApp API by adding a phone number and then sending" +" an initial test message." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Navigating to the WhatsApp quickstart wizard in Meta for Developer " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:198 +msgid "" +"If the browser isn't on the :guilabel:`Quickstart` page for WhatsApp, " +"navigate to `<https://developers.facebook.com/apps>`_ and click on the app " +"that is being configured, (the app name is `Odoo` if the instructions above " +"were followed)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:202 +msgid "" +"Then, in the menu on the left-hand side of the page, click the :guilabel:`v " +"(menu toggle)` icon next to the :guilabel:`WhatsApp` section heading. A " +"small menu will open, containing the following options:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:206 +msgid ":guilabel:`Quickstart`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:207 +msgid ":guilabel:`API Setup`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:208 +msgid ":guilabel:`Configuration`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:210 +msgid "" +"Click the :guilabel:`Quickstart` option, and then click :guilabel:`Start " +"using the API`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:213 +msgid "API Setup" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:215 +msgid "" +"After clicking on :guilabel:`Start using the API`, the page navigates to the" +" :guilabel:`API Setup`. Now that the test number has been created, a test " +"message can be sent to confirm that WhatsApp is working properly. To begin, " +"navigate to the section on the page labeled :guilabel:`Send and receive " +"messages` and click the drop-down menu next to :guilabel:`To`, under " +":guilabel:`Step 1 Select phone numbers`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:221 +msgid "" +"Now, select the only option available: :guilabel:`Manage phone number list`." +" Follow the steps and add up to five numbers to send the free test messages " +"to. After entering the appropriate country code and phone number, click on " +":guilabel:`Next`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:226 +msgid "" +"Adding a phone number to send to in this step will allow for a successful " +"test to be sent by the terminal. This is critical to ensure the WhatsApp " +":abbr:`API (Application Programming Interface)` is working." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:230 +msgid "" +"A verification code from WhatsApp Business is then sent to the phone number," +" which needs to be input on the next screen to verify ownership of the " +"number. Enter the verification code and click :guilabel:`Next` to verify the" +" number." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:235 +msgid "Send a test message via terminal" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:237 +msgid "" +"Next, send a test message via the terminal. Under the section labeled " +":guilabel:`Step 2 Send messages with the API`, click :guilabel:`Send " +"Message`. A test message will then be sent to the phone number that was set " +"in the previous section." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:241 +msgid "" +"Upon successfully receiving the message to the number, move onto the next " +"section to produce and configure webhooks." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:247 +msgid "WhatsApp configuration in Odoo" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:249 +msgid "" +"The next steps configured in this section are all within the Odoo database. " +"A few different values for a token, phone number, and account IDs all need " +"to be configured in Odoo; these values are necessary in order to create a " +":guilabel:`Callback URL` and :guilabel:`Webhook Verify Token`, which are " +"then used to configure the webhooks (in order to receive messages back into " +"the database)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:254 +msgid "" +"In Odoo, navigate to :menuselection:`WhatsApp app --> Configuration --> " +"WhatsApp Business Accounts`. Then click :guilabel:`New` to configure the " +"WhatsApp business account in Odoo." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:257 +msgid "" +"In another browser tab, navigate to " +":menuselection:`https://developers.facebook.com --> My Apps --> WhatsApp -->" +" API Configuration`, and then copy the following values from the Meta " +"developer console into the corresponding fields in Odoo:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:265 +#: ../../content/applications/productivity/whatsapp.rst:669 +msgid "Name" +msgstr "ชื่อ" + +#: ../../content/applications/productivity/whatsapp.rst:266 +msgid "Meta Console" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:267 +msgid "Odoo Interface" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:268 +msgid "Phone" +msgstr "โทรศัพท์" + +#: ../../content/applications/productivity/whatsapp.rst:269 +msgid ":guilabel:`Phone number ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:270 +msgid ":guilabel:`Phone Number ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:271 +msgid "Token" +msgstr "โทเค็น" + +#: ../../content/applications/productivity/whatsapp.rst:272 +msgid ":guilabel:`Temporary access token`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:273 +msgid ":guilabel:`Access Token`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:274 +msgid "App ID" +msgstr "ไอดีแอป" + +#: ../../content/applications/productivity/whatsapp.rst:275 +#: ../../content/applications/productivity/whatsapp.rst:276 +msgid ":guilabel:`App ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:277 +msgid "Account ID" +msgstr "หมายเลขบัญชี" + +#: ../../content/applications/productivity/whatsapp.rst:278 +msgid ":guilabel:`WhatsApp Business Account ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:279 +msgid ":guilabel:`Account ID`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:281 +msgid "" +"To retrieve the :guilabel:`App Secret`, navigate to the Meta developer " +"console, `<https://developers.facebook.com/apps>`_ and select the app that " +"Odoo is being configured in. Then in the left-side menu, under " +":guilabel:`App settings`, select :guilabel:`Basic`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:285 +msgid "" +"Next, click :guilabel:`Show` next to the field :guilabel:`App secret`, and " +"enter the account password to verify ownership. Copy the :guilabel:`App " +"secret` and then paste that copied value into the :guilabel:`App Secret` " +"field on the Odoo :guilabel:`WhatsApp Business Account` configuration " +"dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:290 +msgid "" +"To complete the setup of the WhatsApp business account in Odoo, click " +":guilabel:`Test Connection`. A successful message in green will populate in " +"the upper-right corner of the dashboard if the configuration is set " +"correctly." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:295 +msgid "Configuring webhooks" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:297 +msgid "" +"To configure the webhooks for WhatsApp in Odoo, navigate to " +"`<https://developers.facebook.com/apps>`_ and select the app that Odoo is " +"being configured in. Next under the :guilabel:`WhatsApp` menu heading on the" +" left side of the screen, click on the :guilabel:`API Setup` menu item. " +"Finally go to the section marked :guilabel:`Step 3: Configure webhooks to " +"receive messages` and click on :guilabel:`Configure webhooks`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:304 +msgid "" +"Another way to configure *Webhooks* is to navigate to " +"`<https://developers.facebook.com/apps>`_ and select the app that Odoo is " +"being configured in. Then select :guilabel:`Webhooks` in the left hand menu." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Manually navigating to the Whatsapp webhooks configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:312 +msgid "" +"On the :menuselection:`Webhook configuration` page, click on " +":guilabel:`Edit`, where both the :guilabel:`Callback URL` and " +":guilabel:`Webhook Verify Token` values from the Odoo will be added." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:316 +msgid "" +"Both the :guilabel:`Callback URL` and :guilabel:`Webhook Verify Token` " +"values were automatically populated after clicking on :guilabel:`Test " +"Connection` in the previous step." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:319 +msgid "" +"In a separate browser window, retrieve the necessary values in Odoo by " +"navigating to :menuselection:`WhatsApp app --> Configuration --> WhatsApp " +"Business Accounts` and select the account that is being configured. Locate " +"the values under the section labeled :guilabel:`Receiving Messages`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:324 +msgid "" +"Copy and paste the :guilabel:`Callback URL` from Odoo into the " +":guilabel:`Callback URL` field in Meta. Similarly, copy and paste the " +":guilabel:`Webhook Verify Token` into the :guilabel:`Verify Token` field on " +"the Meta developer console, as well." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:328 +msgid "" +"Finally, click :guilabel:`Verify and save` to record the values in the Meta " +"developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:331 +msgid "Webhook fields" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:333 +msgid "" +"Now input individual webhook fields into Meta's developer console, under the" +" :guilabel:`Webhook fields` section. Click :guilabel:`Manage` and when the " +"pop-up window appears, check the boxes in the :guilabel:`Subscribe` column " +"for the following *field names*:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:337 +msgid "account_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:338 +msgid "message_template_quality_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:339 +msgid "message_template_status_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:340 +msgid "messages" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:341 +msgid "template_category_update" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:343 +msgid "After making the selections, click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:345 +msgid "" +"The finished :guilabel:`Webhooks` configuration will appear like this in the" +" Meta developer console:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "WhatsApp webhooks set in the Meta developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:352 +msgid "" +"The :guilabel:`Webhook fields` will only appear once the subscription is " +"confirmed using the :guilabel:`Callback URL` and :guilabel:`Webhook Verify " +"Token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:356 +msgid "" +"`Meta's WhatsApp documentation on setting webhooks " +"<https://developers.facebook.com/docs/whatsapp/cloud-api/guides/set-up-" +"webhooks>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:360 +msgid "Add phone number" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:362 +msgid "" +"To configure the phone number to use for WhatsApp in Odoo, navigate back to " +"the Meta developer console (`<https://developers.facebook.com/apps>`_) and " +"again select the app that Odoo is being configured in. Under the " +":guilabel:`WhatsApp` menu heading on the left side of the screen, click on " +"the :guilabel:`API Setup` menu item. From there, go to the section marked: " +":guilabel:`Step 5: Add a phone number`, and click on :guilabel:`Add phone " +"number`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:368 +msgid "" +"In the fields, enter a :guilabel:`Business name` as well as a " +":guilabel:`Business website or profile page`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:372 +msgid "" +"The :guilabel:`Business website or profile page` field can be a social media" +" page's :abbr:`URL (Uniform Resource Locator)`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:375 +msgid "" +"Complete filling out the business information by next selecting the country " +"that the company does business in from the drop-down menu in the " +":guilabel:`Country` section. Add an address if desired, however, this " +"information is optional. After adding the location, click :guilabel:`Next` " +"to continue." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:380 +msgid "" +"The following page contains information for the :guilabel:`WhatsApp Business" +" profile`. Complete the following sections, accordingly:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:383 +msgid ":guilabel:`WhatsApp Business Profile Display Name`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:384 +msgid ":guilabel:`Timezone`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:385 +msgid ":guilabel:`Category`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:386 +msgid ":guilabel:`Business description` (optional)" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:388 +msgid "" +"Once these sections are complete, click :guilabel:`Next`. The page refreshes" +" and then prompts the administrator to :guilabel:`Add a phone number for " +"WhatsApp` in the respective field. Here, enter the phone number to configure" +" in WhatsApp." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:393 +msgid "" +"`Migrate an Existing WhatsApp Number to a Business Account " +"<https://developers.facebook.com/docs/whatsapp/cloud-api/get-" +"started/migrate-existing-whatsapp- number-to-a-business-account>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:397 +msgid "" +"Next, choose a verification method for the phone number. Select either " +":guilabel:`Text message` or :guilabel:`Phone call`, and then click " +":guilabel:`Next` proceed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:400 +msgid "" +"The phone number entered will receive either a text or a phone call by " +"WhatsApp with a code, depending on the verification method chosen. Enter " +"that verification code into the :guilabel:`Verification code` field and " +"click :guilabel:`Next` to finish." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:405 +msgid "" +"If a payment method hasn't been added this will be necessary to proceed. " +"`Visit Meta's documentation on how to add a payment method in Meta's " +"Business Manager " +"<https://www.facebook.com/business/help/915454841921082?id=180505742745347>`_." +" This is part of Meta's fraud detection system, in order to ensure that the " +"account/company are real a payment method is required to proceed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:412 +msgid "" +"`Meta for Developers: Add a Phone Number " +"<https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/add-a-" +"phone-number>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:418 +msgid "Permanent token" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:420 +msgid "" +"After configuration and testing are complete, a permanent token should be " +"created to replace the :guilabel:`Temporary token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:424 +msgid "" +"`Meta for Developers: System User Access Tokens " +"<https://developers.facebook.com/docs/whatsapp/business-management-api/get-" +"started#system-user- access-tokens>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:428 +msgid "" +"Begin by navigating to `<https://business.facebook.com/>`_ and then go to " +":menuselection:`Business settings --> User --> System Users`. Select an " +"existing system user or create a new system user by clicking on " +":guilabel:`Add`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:432 +msgid "" +"Assets now must be added to the system user and then a permanent token can " +"be generated." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:434 +msgid "" +"Click on :guilabel:`Add assets`, and when the pop-up window appears select " +":guilabel:`Apps` under the :guilabel:`Select asset type`. Then, select the " +"Odoo app and toggle the permissions to *On* under the :guilabel:`Full " +"control` option. Set this new permission setting by clicking :guilabel:`Save" +" Changes`, to which a confirmation window will appear, acknowledging the " +"addition of the asset to the system user. Finish by clicking " +":guilabel:`Done`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:440 +msgid "" +"Next, the permanent token will be generated. Click on :guilabel:`Generate " +"new token`, and a pop-up window will appear asking which app this token " +"should be generated for. Select the :guilabel:`App` that this token is for. " +"Then determine the expiration date of either :guilabel:`60 days` or " +":guilabel:`Never`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:445 +msgid "" +"Finally, when Meta asks which permissions should the system user allow, add " +"all of the following permissions:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:448 +msgid "WhatsApp_business_messaging" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:449 +msgid "WhatsApp_business_management" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:451 +msgid "" +"When permissions are set, click :guilabel:`Generate token`. Copy the token " +"value that populates on the screen that follows." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:454 +msgid "" +"With that token value, update the :guilabel:`Access Token` field in the " +"WhatsApp business account in Odoo by navigating to :menuselection:`WhatsApp " +"app --> Configuration --> WhatsApp Business Accounts`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:459 +msgid "Go live with the Meta app" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:461 +msgid "" +"Finally, to launch the app, the Meta app must be set to :guilabel:`Live` in " +"the Meta developer console. Navigate to " +"`<https://developers.facebook.com/apps>`_ and click on the app that is being" +" configured. In the top menu, toggle the :guilabel:`App Mode` field from " +":guilabel:`Development` to :guilabel:`Live`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:467 +msgid "" +"If the app status is not set to *live*, then the database will only be able " +"to contact the test numbers specified in the developer console." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:471 +msgid "" +"A privacy policy URL must be set in order for the app to be set to live. Go " +"to the Meta developer console, `<https://developers.facebook.com/apps>`_ and" +" select the app that Odoo is being configured in. Then, using the menu on " +"the left side of the screen, go to :menuselection:`App Settings --> Basic`. " +"Then, enter the privacy policy hyperlink address under the " +":guilabel:`Privacy Policy URL` field of the form. Click :guilabel:`Save " +"changes` to apply the privacy policy to the app." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:478 +msgid "" +"Once the app has gone live in the Meta developer console, a confirmation " +"email is sent to the administrator." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:484 +msgid "WhatsApp templates" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:486 +msgid "" +"WhatsApp templates are saved messages that are used repeatedly to send " +"messages from the database. They allow users to send quality communications," +" without having to compose the same text repeatedly." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:489 +msgid "" +"Creating different templates that are tailored to specific situations lets " +"users choose the right message for the right audience. This increases the " +"quality of the message and the overall engagement rate with the customer." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:493 +msgid "" +"WhatsApp templates can be created on both the Odoo and Meta consoles. The " +"following process will overview the process for creating templates in Odoo " +"and then afterward in Meta." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:497 +msgid "" +"WhatsApp has an approval process that must be completed before the template " +"can be used. :ref:`productivity/whatsapp/approval`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:503 +msgid "Creating templates in Odoo" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:505 +msgid "" +"To access and create WhatsApp templates, begin by navigating to the " +":menuselection:`WhatsApp app --> Templates` dashboard." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:508 +msgid "" +"At the bottom of an individual template's form, there are three tabs: " +":guilabel:`Body`, :guilabel:`Buttons`, and :guilabel:`Variables`; these " +"three tabs combined create the WhatsApp template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:512 +msgid "" +"The text is entered into the :guilabel:`Body` tab, and dynamic content that " +"is called out in the :guilabel:`Body` tab is specified in the " +":guilabel:`Variables` tab. Every piece of dynamic content (e.g., " +"placeholders) in the message (body) is specifically called out and specified" +" in the :guilabel:`Variables` tab." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:517 +msgid "" +"Templates are prefabricated layouts that allow users to send professional " +"looking messages to customers. These templates are capable of containing " +"dynamic data that will populate in the end message using variables that are " +"set in the template configuration. For example, messages can contain the end" +" user's name, call out specific products, or reference a sales order, to " +"name a few convenient and impactful variables." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:523 +msgid "" +"To create a WhatsApp template, go to the :menuselection:`WhatsApp app --> " +"Templates` dashboard and click :guilabel:`New`. On the form, enter a " +":guilabel:`Name` for the template, and select a :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:528 +msgid "" +"In order to complete this next task, administrator access rights are needed " +"to edit the :guilabel:`Applies to` field. See this :doc:`access rights " +"documentation <../general/users/access_rights>` for more information." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:532 +msgid "" +"In the :guilabel:`Account` drop-down menu, select the *WhatsApp business " +"account* in Odoo that this template should link to. Next, under the " +":guilabel:`Applies to` field select the *model* the server action will apply" +" to for this template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:537 +msgid "" +"These models can also be accessed in :ref:`developer mode <developer-mode>`." +" On a contact form (or similar relevant form in Odoo), navigate to the model" +" that will be referenced, and hover over any field name. A box of backend " +"information will reveal itself with the specific Odoo :guilabel:`Model` name" +" in the backend. Search (using the front-end name) for this model in the " +":guilabel:`Applies to` drop-down menu in the WhatsApp template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:544 +msgid "" +"Often when changing the model or :guilabel:`Applies to` field, the " +":guilabel:`Phone Field` may produce an error The :guilabel:`Phone Field` " +"should always be set to the `Phone` or `Mobile` model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:548 +msgid "" +"To search available fields, type in the front-end name in the " +":guilabel:`Search...` box. This will find a result from all of the " +"available fields for the model (:guilabel:`Applies to`) that the template is" +" created for." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:553 +msgid "" +"In order to find specific fields, multiple levels may need to be navigated " +"in the search results box. Use the :guilabel:`> (right chevron)` and " +":guilabel:`⬅️ (left arrow)` icons to navigate between the menu levels." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "Searching for the phone field in the search bar." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:561 +msgid "" +"Change the :guilabel:`Category` to fit either a :guilabel:`Marketing`, " +":guilabel:`Utility`, or :guilabel:`Authentication` category. In most " +"instances the first two options will be used, unless the user would like to " +"send a password reset or something security related. Set to " +":guilabel:`Marketing` should there be anything promotional being sent and " +"set to :guilabel:`Utility` should there be general transactional messages " +"being sent (i.e., sales order, event ticket, etc)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:568 +msgid "" +"Specifying an incorrect category can cause a flag/rejected status from Meta " +"during the approval process." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:571 +msgid "" +"Add any :guilabel:`Users` that are allowed to use this template. In the " +"right-side column, a :guilabel:`Header type` can be configured along with a " +":guilabel:`Header message`, as well." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:574 +msgid "The available :guilabel:`Header types` are as follows:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:576 +msgid "Text" +msgstr "ข้อความ" + +#: ../../content/applications/productivity/whatsapp.rst:577 +msgid "Image" +msgstr "รูปภาพ" + +#: ../../content/applications/productivity/whatsapp.rst:578 +msgid "Video" +msgstr "วิดีโอ" + +#: ../../content/applications/productivity/whatsapp.rst:579 +msgid "Document" +msgstr "เอกสาร" + +#: ../../content/applications/productivity/whatsapp.rst:580 +msgid "Location (variables need to be set)" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:582 +msgid "" +"Navigate to the :guilabel:`Body` tab to configure the main message of the " +"template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:584 +msgid "" +"When all the necessary changes are made to the template, click on the " +":guilabel:`Submit for approval` button in the upper-left corner. This will " +"cause the status of the template to change to :guilabel:`Pending`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:588 +msgid "" +"The status will remain in :guilabel:`Pending` until a decision has been made" +" by Meta, whereby a confirmation email will then be sent indicating that the" +" template has been approved (or rejected). The templates will then need to " +"be synced from the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:592 +msgid "" +"See this section for more information on :ref:`syncing templates " +"<productivity/whatsapp/sync>`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:595 +msgid "" +"There are pre-configured demo data templates available in Odoo to use or " +"modify. These templates can be used as-is or modified to suit a specific " +"business need." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:598 +msgid "" +"To use these templates, navigate to :menuselection:`WhatsApp app --> " +"Templates` and select a pre-configured template. Click :guilabel:`Submit for" +" Approval` to start the approval process. An email will be sent to the " +"administrator of the Meta account when the template has been approved." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:603 +msgid "Buttons" +msgstr "ปุ่ม" + +#: ../../content/applications/productivity/whatsapp.rst:605 +msgid "" +"Buttons can be added into the message from the :guilabel:`Buttons` tab. " +"Enter the :guilabel:`Type` (either :guilabel:`Visit Website`, " +":guilabel:`Call Number`, or :guilabel:`Quick Reply`), and then specify the " +":guilabel:`Button Text`, :guilabel:`Call Number` or :guilabel:`Website URL` " +"(including :guilabel:`Url Type`), depending on the :guilabel:`Type` of " +"button." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:611 +msgid "" +"Buttons can also be added on the Meta business console. See Meta's WhatsApp " +"template dashboard by navigating to " +"`<https://business.facebook.com/wa/manage/home>`_. Then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:616 +msgid "Using placeholders and variables" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:618 +msgid "" +"Dynamic variables reference certain fields within the Odoo database to " +"produce unique data in the WhatsApp message when using a template. Dynamic " +"variables are encoded to display fields from within the database, " +"referencing fields from within a model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:623 +msgid "" +"Many companies like to customize their WhatsApp messages with a personalized" +" piece of customer information to grab attention. This can be accomplished " +"in Odoo by referencing a field within a model by setting a dynamic variable." +" For example, a customer's name can be referenced in the email from the " +":guilabel:`Customer` field on the :guilabel:`Sales Order` model." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "WhatsApp message with dynamic variables highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:632 +msgid "" +"Dynamic variables can be added in to the :guilabel:`Body` by adding " +":guilabel:`placeholders` in the *text*. To add a placeholder in the *message" +" body* enter the following text `{{1}}`. For the second placeholder enter " +"`{{2}}` and increase incrementally as more placeholders are added to the " +"text." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:637 +msgid "*The following is the text from payment receipt template body:*" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:639 +msgid "Dear {{1}}," +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "Here is your invoice *{{2}}* from *{{3}}* for a total of *{{4}}{{5}}*." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:0 +msgid "To review your invoice or pay online: {{6}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:644 +msgid "Thank you" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:647 +msgid ":ref:`productivity/whatsapp/templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:649 +msgid "" +"These placeholders must be configured on the :guilabel:`Variables` tab of " +"the template before submitting for approval from Meta. To edit the dynamic " +"variables on a template, first change the :guilabel:`Type` to " +":guilabel:`Field of Model`. This allows Odoo to reference a field within a " +"model to produce unique data in the message being sent." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:654 +msgid "" +"Next, edit the :guilabel:`Field` of the dynamic variables. The " +":guilabel:`Applies to` field in the template should be edited prior to " +"ensure the correct model and field are referenced." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:657 +msgid "" +"To search the available fields, type in the front-end name of the field in " +"the search box. This will find a result from all of the available fields for" +" the model (:guilabel:`Applies to`) that the template is created for. There " +"may be multiple levels that need to be configured." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:662 +msgid "" +"The following is an example of the variables set for the above placeholders " +"in the payment receipt noted above:" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:670 +msgid "Sample Value" +msgstr "ค่าตัวอย่าง" + +#: ../../content/applications/productivity/whatsapp.rst:671 +msgid "Type" +msgstr "ประเภท" + +#: ../../content/applications/productivity/whatsapp.rst:672 +msgid "Field" +msgstr "ฟิลด์" + +#: ../../content/applications/productivity/whatsapp.rst:673 +msgid "body - {{1}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:674 +msgid "Azure Interior" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:675 +#: ../../content/applications/productivity/whatsapp.rst:679 +#: ../../content/applications/productivity/whatsapp.rst:683 +#: ../../content/applications/productivity/whatsapp.rst:687 +#: ../../content/applications/productivity/whatsapp.rst:691 +msgid "Field of Model" +msgstr "ฟิลด์ของโมเดล" + +#: ../../content/applications/productivity/whatsapp.rst:676 +msgid "`Partner`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:677 +msgid "body - {{2}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:678 +msgid "INV/2022/00001" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:680 +msgid "`Number`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:681 +msgid "body - {{3}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:682 +msgid "My Company" +msgstr "My Company" + +#: ../../content/applications/productivity/whatsapp.rst:684 +msgid "`Company`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:685 +msgid "body - {{4}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:686 +msgid "$" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:688 +msgid "`Currency > Symbol`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:689 +msgid "body - {{5}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:690 +msgid "4000" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:692 +msgid "`Amount`" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:693 +msgid "body - {{6}}" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:694 +msgid "\\https://.." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:695 +msgid "Portal link" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:699 +msgid "" +"For example, in the :guilabel:`Body` tab, if the following is typed, \"Hello" +" {{1}},\", then `{{1}}` must be set in the :guilabel:`Variables` tab. For " +"this specific case, the message should greet the customer by name, so the " +"`{{1}}` should be configured to populate the `{{1}}` :guilabel:`Field` with " +"the :guilabel:`Customer` name." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:705 +msgid "Customizing WhatsApp templates is out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:710 +msgid "Meta template approval" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:712 +msgid "" +"After updating the dynamic variables on the template, the template needs to " +"be submitted to Meta for approval again. Click :guilabel:`Submit for " +"Approval` to start the approval process. An email will be sent to the " +"administrator of the Meta account when the template has been approved." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:716 +msgid "" +"Following the approval from Meta, sync the templates again in the Odoo " +"database. See this documentation: :ref:`productivity/whatsapp/sync`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:720 +msgid "" +"To see the status to Meta's WhatsApp template dashboard by navigating to " +"`<https://business.facebook.com/wa/manage/home>`_. Then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:727 +msgid "Syncing templates" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:729 +msgid "" +"Templates must be synced on the Odoo database once they are approved by the " +"Meta team. To do so, begin by navigating to :menuselection:`WhatsApp app -->" +" Configuration --> WhatsApp Business Accounts` and select the configuration " +"that should be synced. Under the section marked :menuselection:`Sending " +"messages`, towards the bottom, click on :guilabel:`Sync Templates`. Meta " +"will update the templates that are approved so that they can be utilized " +"with various apps in the database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Syncing Meta WhatsApp templates to the Odoo database, with the 'Sync Templates'\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:741 +msgid "" +"A successful message in green appears in the upper-right corner with the " +"number of templates updated." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:745 +msgid "" +"Templates can also be synced individually from the template itself. Navigate" +" to the :menuselection:`WhatsApp app --> Templates` dashboard and select the" +" template to sync. Then, click on the :guilabel:`Sync Template` button " +"located in the top menu of the template's form." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:750 +msgid "Creating templates in Meta" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:752 +msgid "" +"First, navigate to `Meta's WhatsApp template dashboard " +"<https://business.facebook.com/wa/manage/home>`_, and then go to " +":menuselection:`Account tools --> Message templates`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Account tools highlighted in business manager with the manage templates link" +" highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:760 +msgid "" +"To create a WhatsApp template, click on the blue :guilabel:`Create template`" +" button, and then select the :guilabel:`Category`. The options listed " +"include: :guilabel:`Marketing`, :guilabel:`Utility`, and " +":guilabel:`Authentication`. In most instances the first two options will be " +"used, unless the user would like to send a password reset or something " +"security related." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:765 +msgid "" +"Enter the :guilabel:`Name` of the template and then select the " +":guilabel:`Language` for the template." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:769 +msgid "" +"Multiple languages can be selected by typing the language name(s) and " +"selecting the other languages as needed." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Template configuration options listed, with Marketing, Utility, Name and Language\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:777 +msgid "" +"After making the appropriate selections, click on :guilabel:`Continue` in " +"the upper-right corner. The page redirects to the :guilabel:`Edit template` " +"page. Here the :guilabel:`Header`, :guilabel:`Body`, :guilabel:`Footer` and " +":guilabel:`Buttons` are configured. To the right of the template is a " +"preview of what the template will look like in production." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "Edit the template using a header, body, footer and buttons." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:786 +msgid "" +"When all the necessary changes are made to the template, click on the " +":guilabel:`Submit` button in the upper-right corner. A confirmation window " +"appears to confirm the language— click :guilabel:`Confirm` to approve and " +"then another window appears stating that the template will be submitted to " +"Meta for review and approval." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:791 +msgid "" +"The :guilabel:`Status` of the template will remain in :guilabel:`In review` " +"until a decision has been made by Meta. Once an email confirmation is " +"received approving the template, the templates will need to be synced from " +"within the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:796 +msgid "" +"For more information on configuring templates on the Meta developer console " +"visit `Meta's WhatsApp template documentation " +"<https://developers.facebook.com/docs/whatsapp/business-management-" +"api/message-templates/>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:801 +msgid "Notifications" +msgstr "การแจ้งเตือน" + +#: ../../content/applications/productivity/whatsapp.rst:803 +msgid "" +"Notifications in WhatsApp are handled similar to a message conversation in " +"Odoo. A pop-up window appears with the received conversation from the " +"customer. By default, notifications are set in the WhatsApp business account" +" configuration in Odoo." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:807 +msgid "" +"Notification settings can be adjusted by navigating to " +":menuselection:`WhatsApp app --> Configuration --> WhatsApp Business " +"Accounts`. From there, select the account and scroll down to the " +":menuselection:`Control` section where notifications are handled. Under the " +":guilabel:`Notify users` heading, type in the field which user(s) should be " +"notified for this particular WhatsApp channel." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:813 +msgid "" +"Once a conversation is initiated between a user and a customer, " +"notifications to all the users specified in the WhatsApp business account " +"configuration won't occur. Only notifications to the user(s) in the " +"conversation will occur. Should the user not respond within 15 days, the " +"customer's reply after the 15 days will populate once again to all the users" +" specified in the WhatsApp configuration." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:820 +msgid "Adding users to chat" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:822 +msgid "" +"Users can be added to a WhatsApp chat by expanding the WhatsApp pop-up " +"window. WhatsApp conversations are located in the *Discuss* app. Click on " +"the :guilabel:`👤+ (add user)` icon next to it, and a window appears to " +"invite users to the conversation." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"Adding users to a WhatsApp conversation, with the add user icon highlighted." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:831 +msgid "WhatsApp API FAQ" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:834 +msgid "Verification" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:836 +msgid "" +"As of February 1, 2023, if the Meta app requires advanced level access to " +"permissions, a complete business verification may need to be completed. This" +" includes submitting office business documents to Meta. `See this " +"documentation " +"<https://developers.facebook.com/docs/development/release/business-" +"verification>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:842 +msgid "" +"`Meta's WhatsApp access verification documentation " +"<https://developers.facebook.com/docs/development/release/access-" +"verification/>`_." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:846 +msgid "Template errors" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:848 +msgid "" +"Editing templates can cause tracebacks and errors unless the exact process " +"is followed above, here: (:ref:`productivity/whatsapp/templates`)." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:852 +msgid "Duplicate validation error" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:854 +msgid "" +"When syncing the templates there may be an instance when there are multiple " +"templates with the same name on Meta's business manager and in Odoo. This " +"causes a duplicate validation error. To correct this issue, rename the " +"duplicate template name on Odoo and sync the templates once again by " +"following the steps here: :ref:`productivity/whatsapp/sync`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "User error populated in Odoo when a duplicate template exists." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:864 +msgid "Token errors" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:867 +msgid "User error" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:869 +msgid "" +"Should the temporary token not be replaced with a permanent token a user " +"error will populate in Odoo when testing the connection after sending fails." +" To correct this issues see :ref:`productivity/whatsapp/token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "User error populated in Odoo when token expires." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:878 +msgid "System user error 100" +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:880 +msgid "" +"Should the system user be an :guilabel:`Employee` when setting up the " +"permanent token, a user error 100 will populate." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst:883 +msgid "" +"To correct this error, create an :guilabel:`Admin` system user, following " +"the process outlined here: :ref:`productivity/whatsapp/token`." +msgstr "" + +#: ../../content/applications/productivity/whatsapp.rst-1 +msgid "" +"User error populated in Odoo when an employee token is generated instead of " +"a Admin user." +msgstr "" diff --git a/locale/th/LC_MESSAGES/sales.po b/locale/th/LC_MESSAGES/sales.po new file mode 100644 index 000000000..f0576a986 --- /dev/null +++ b/locale/th/LC_MESSAGES/sales.po @@ -0,0 +1,18728 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/sales.rst:5 +#: ../../content/applications/sales/sales.rst:8 +msgid "Sales" +msgstr "การขาย" + +#: ../../content/applications/sales/crm.rst:8 +msgid "CRM" +msgstr "CRM" + +#: ../../content/applications/sales/crm.rst:10 +msgid "" +"**Odoo CRM** helps you organize your sales activities: track leads, close " +"opportunities and get accurate forecasts. Keep opportunities organized with " +"the pipeline and manage your day-to-day activities with meetings and next " +"activities." +msgstr "" + +#: ../../content/applications/sales/crm.rst:15 +msgid "`Odoo Tutorials: CRM <https://www.odoo.com/slides/crm-16>`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads.rst:5 +msgid "Acquire leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:3 +msgid "Convert leads into opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 +msgid "" +"*Leads* act as qualifying steps before an opportunity is created. This " +"provides additional time before a potential opportunity is assigned to a " +"sales person." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 +#: ../../content/applications/sales/crm/optimize/gamification.rst:11 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 +#: ../../content/applications/sales/point_of_sale/configuration.rst:6 +#: ../../content/applications/sales/point_of_sale/employee_login.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:11 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:52 +#: ../../content/applications/sales/point_of_sale/restaurant.rst:20 +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:34 +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:24 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 +#: ../../content/applications/sales/subscriptions/closing.rst:31 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:11 +msgid "" +"To activate the *Leads* setting, navigate to :menuselection:`CRM app --> " +"Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. " +"Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Leads setting on CRM configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:18 +msgid "" +"Activating this feature adds a new menu, :guilabel:`Leads`, to the header " +"menu bar at the top of the screen." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Leads menu on CRM application." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:25 +msgid "" +"Once the *Leads* setting has been activated, it applies to all sales teams " +"by default. To turn off leads for a specific team, navigate to " +":menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a " +"team from the list to open the record, and uncheck the :guilabel:`Leads` " +"box. Once done, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35 +msgid "Convert a lead into an opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:37 +msgid "" +"To convert a lead into an *opportunity*, navigate to :menuselection:`CRM -->" +" Leads`, and click on a :guilabel:`Lead` from the list to open it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:40 +msgid "" +"In the upper-left corner of the screen, click the :guilabel:`Convert to " +"Opportunity` button, which opens a :guilabel:`Convert to opportunity` pop-up" +" window." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Create opportunity button on a lead record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:47 +msgid "" +"On the :guilabel:`Convert to opportunity` pop-up window, in the " +":guilabel:`Conversion action` field, select the :guilabel:`Convert to " +"opportunity` option." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 +msgid "" +"If a lead, or an opportunity, already exists in the database for this " +"customer, Odoo automatically suggests merging both leads/opportunities. For " +"more information on merging leads and opportunities, see the section on how " +"to :ref:`merge leads <sales/crm/acquire_leads/merge-leads>` below." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:56 +msgid "" +"Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which" +" the opportunity should be assigned." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59 +msgid "" +"If the lead has already been assigned to a salesperson or a team, these " +"fields automatically populate with that information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Create opportunity pop-up." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:66 +msgid "" +"Under the :guilabel:`Customer` heading, choose from the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:68 +msgid "" +":guilabel:`Create a new customer`: Choose this option to use the information" +" in the lead to create a new customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:70 +msgid "" +":guilabel:`Link to an existing customer`: Choose this option, then select a " +"customer from the resulting drop-down menu, to link this opportunity to the " +"existing customer record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:72 +msgid "" +":guilabel:`Do not link to a customer`: Choose this option to convert the " +"lead, but not link it to a new or existing customer." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:75 +msgid "" +"Lastly, when all configurations are complete, click :guilabel:`Create " +"Opportunity`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:80 +msgid "Merge leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:82 +msgid "" +"Odoo automatically detects similar leads and opportunities by comparing the " +"email addresses of the associated contacts. If a similar lead/opportunity is" +" found, a :guilabel:`Similar Lead` smart button appears at the top of the " +"lead/opportunity record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Similar leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:90 +msgid "" +"To compare the details of the similar leads/opportunities, click the " +":guilabel:`Similar Leads` button. This opens a kanban view with only the " +"similar leads/opportunities. Click into each card to view the details for " +"each lead/opportunity, and confirm if they should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 +msgid "" +"When merging, Odoo gives priority to whichever lead/opportunity was created " +"in the system first, merging the information into the first created " +"lead/opportunity. However, if a lead and an opportunity are being merged, " +"the resulting record is referred to as an opportunity, regardless of which " +"record was created first." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:100 +msgid "" +"After confirming that the leads/opportunities should be merged, return to " +"the kanban view using breadcrumbs, or by clicking the :guilabel:`Similar " +"Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to " +"change to list view." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:104 +msgid "" +"Check the box on the left of the page for the leads/opportunities to be " +"merged. Then, click the :guilabel:`Action ⚙️ (gear)` icon at the top of the " +"page, to reveal a drop-down menu. From that drop-down menu, select the " +":guilabel:`Merge` option to merge the selected opportunities (or leads)." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:108 +msgid "" +"When :guilabel:`Merge` is selected from the :guilabel:`Action ⚙️ (gear)` " +"drop-down menu, a :guilabel:`Merge` pop-up window appears. In that pop-up " +"window, decide to :guilabel:`Assign opportunities to` a " +":guilabel:`Salesperson` and/or :guilabel:`Sales Team`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:112 +msgid "" +"Below those fields, the leads/opportunities to merge are listed, along with " +"their related information. To merge those selected leads/opportunities, " +"click :guilabel:`Merge`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:116 +msgid "" +"When merging opportunities, no information is lost. Data from the other " +"opportunity is logged in the chatter, and the information fields, for " +"reference." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst-1 +msgid "Merge option from action menu in list view." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 +msgid "Generate leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:5 +msgid "" +"Two key ways to generate new leads or opportunities for your business are " +"through email aliases and website contact forms. Odoo automatically creates " +"leads in your CRM whenever someone sends a message to a Sales Team email " +"alias or fills out a contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:10 +msgid "Configure email aliases" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:12 +msgid "" +"Each Sales Team can use its own unique email alias to generate " +"leads/opportunities. Any email sent to a Sales Team's email alias will " +"automatically create a lead (if leads are activated in your CRM settings) or" +" an opportunity in the pipeline for that particular team. Configure custom " +"email aliases on the configuration page for each Sales Team by navigating to" +" :menuselection:`CRM --> Configuration --> Sales Teams`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Configuring Sales Teams" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:23 +msgid "Use Contact Forms on your website" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:25 +msgid "" +"By default, your website's *Contact Us* page displays Odoo's ready-to-use " +"Contact Form. Whenever someone submits this form, a lead or an opportunity " +"is generated in your database." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Default Contact Us page" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:32 +msgid "" +"The Contact Form can be activated or deactivated at any time by going to " +":menuselection:`Website --> Go to Website --> Customize --> Contact Form`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form toggle" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:39 +msgid "" +"When the Form is deactivated, the *Contact Us* page simply displays a button" +" to email your company directly. Any email sent this way will generate a " +"lead/opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Us Page using email" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:46 +msgid "" +"Choose which Sales Team or salesperson is automatically assigned to the " +"leads/opportunities created from the Contact Form by going to " +":menuselection:`Website --> Configuration --> Settings --> Communication`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Contact Form settings" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:55 +msgid "Customize Contact Forms" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:57 +msgid "" +"Contact Forms can be customized for the specific information your team " +"needs, using the free *Form Builder* module." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:60 +msgid "" +"The *Form Builder* module is installed automatically when a Form element is " +"added to a web page via the Website Builder. It can also be installed " +"manually from the :guilabel:`Apps` page." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Form Builder building blocks" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:68 +msgid "" +"Forms can be created from scratch to serve a wide variety of purposes. " +"However, Odoo's default *Contact Us* page is designed to fit most users' " +"needs. Start with the default form and modify from there." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:73 +msgid "Edit Contact Form fields" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:75 +msgid "" +"In Edit mode on your website, click on any field to start editing it. The " +"following information can be edited for each field on the Contact Form:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:78 +msgid "" +":guilabel:`Type`: Choose a custom field option or an existing field. " +"Examples include phone, file upload, language, etc." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:80 +msgid "" +":guilabel:`Input Type`: Determine the type of entry customers should input. " +"Available options are text,email, telephone, and URL." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:82 +msgid "" +":guilabel:`Input Placeholder`: Type in an example to guide users how to " +"input information where formatting is important, such as a phone number or " +"email address." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:84 +msgid "" +":guilabel:`Label Name`: Type in the display name to show users what " +"information is needed from them." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:86 +msgid "" +":guilabel:`Label Position`: Choose the way the label is aligned with the " +"rest of the form. The label can be hidden, above the field, to the far left " +"of the field, or right adjusted and closer to the field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:89 +msgid "" +":guilabel:`Required`: Toggle this option for information that you absolutely" +" need entered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:90 +msgid "" +":guilabel:`Hidden`: Toggle this option to hide the field without deleting " +"it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:91 +msgid "" +":guilabel:`Shown on Mobile`: Toggle this option to show the field to users " +"on mobile devices." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst-1 +msgid "Editable field options" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:97 +msgid "" +"By default, when a Form is submitted, it sends you an email with the " +"customer's inputted information. To have it automatically generate a " +"lead/opportunity instead, edit the Form and select :guilabel:`Create an " +"Opportunity` as the Action." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:102 +msgid "" +"If leads are activated in your CRM settings, selecting :guilabel:`Create an " +"Opportunity` generates a lead instead. To learn more about activating leads " +"in the CRM settings, head over to :doc:`convert`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:3 +msgid "Lead mining" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5 +msgid "" +"Lead mining is a feature that allows CRM users to generate new leads " +"directly into their Odoo database. To ensure lead qualification, lead mining" +" output is determined by a variety of filtering criteria, such as the " +"country, the company size, and the industry." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:12 +msgid "" +"To get started, go to :menuselection:`CRM --> Configuration --> Settings` " +"and activate :guilabel:`Lead Mining`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Activate lead mining in Odoo CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:20 +msgid "Generate leads" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22 +msgid "" +"After the :guilabel:`Lead Mining` setting is activated, a new button called " +":guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` " +"pipeline. Lead mining requests are also available through " +":menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through " +":menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate " +"Leads` button is also available." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "The Generate Leads button to use the lead mining feature." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:32 +msgid "" +"Click on the :guilabel:`Generate Leads` button, and a window will appear " +"offering a variety of criteria by which to generate leads." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "" +"The pop-up window with the selection criteria in order to generate leads in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39 +msgid "" +"Choose to generate leads for :guilabel:`Companies` to get company " +"information only, or choose :guilabel:`Companies and their Contacts` to get " +"company information as well as individual employee contact information. When" +" targeting :guilabel:`Companies and their Contacts`, there is an option to " +"filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44 +msgid "Additional filtering options include:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46 +msgid "" +":guilabel:`Size`: filter leads based on the number of employees at the " +"company" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47 +msgid "" +":guilabel:`Countries`: filter leads based on the country (or countries) they" +" are located in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48 +msgid "" +":guilabel:`States`: further filter leads based on the state they are located" +" in, if applicable" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49 +msgid "" +":guilabel:`Industries`: filter leads based on the specific industry they " +"work in" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50 +msgid "" +":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned " +"to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51 +msgid "" +":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads " +"will be assigned to" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52 +msgid "" +":guilabel:`Default Tags`: choose which tags are applied directly to the " +"leads once found" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:55 +msgid "" +"Make sure to be aware of the latest EU regulations when receiving contact " +"information. Get more information about the General Data Protection " +"Regulation on `Odoo GDPR <http://odoo.com/gdpr>`_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 +#: ../../content/applications/sales/rental.rst:88 +msgid "Pricing" +msgstr "กำหนดราคา" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61 +msgid "" +"Lead mining is an *In-App Purchase* feature and each generated lead costs " +"one credit." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63 +msgid "" +"Choosing to generate :guilabel:`Companies and their Contacts` costs one " +"additional credit for each contact generated." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67 +msgid "" +"See here for full pricing information: `Lead Generation by Odoo IAP " +"<https://iap.odoo.com/iap/ in-app-services/167?>`_." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70 +msgid "" +"To buy credits, navigate to :menuselection:`CRM --> Configuration --> " +"Settings`. In the :guilabel:`Lead Generation` section, under the " +":guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits from the lead mining settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78 +msgid "" +"Credits may also be purchased by navigating to the :menuselection:`Settings " +"--> General Settings`. In the :guilabel:`In-App Purchases` section, under " +"the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst-1 +msgid "Buy credits in the Odoo IAP settings." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88 +msgid "" +"Users of Odoo Online (SaaS) Enterprise automatically have free trial credits" +" in their database to test any IAP features." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 +msgid ":doc:`../../../general/in_app_purchase`" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 +msgid "Create and send quotations" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:5 +msgid "" +"Once a qualified lead has been converted into an opportunity, the next step " +"is to create and deliver a quotation. This process can be easily handled " +"through Odoo's *CRM* application." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:9 +msgid "Create a new quotation" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:11 +msgid "" +"To create a new quotation, open the :menuselection:`CRM app`, revealing the " +":guilabel:`Pipeline` page on the main *CRM* dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:14 +msgid "" +"From here, click on any opportunity to open it. Review the existing " +"information and update any fields, if necessary." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:18 +msgid "" +"If a quotation has already been created for this opportunity, it can be " +"found by clicking on the :guilabel:`Quotations` smart button at the top of " +"the top of the form. The number of existing quotations is listed on the " +"smart button, as well." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:22 +msgid "" +"At the top-left of the form, click the :guilabel:`New Quotation` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst-1 +msgid "Qualified lead form with New Quotation button emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:29 +msgid "" +"The :guilabel:`Customer` field is **not** required on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:31 +msgid "" +"However, customer information must be added or linked before a quotation can" +" be sent. If the :guilabel:`Customer` field is left blank on the " +"opportunity, clicking the :guilabel:`New Quotation` button opens a pop-up " +"window with the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:35 +msgid "" +":guilabel:`Create a new customer`: creates a new customer record, using any " +"available information provided on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:37 +msgid "" +":guilabel:`Link to an existing customer`: opens a drop-down field with " +"existing customer names. Select a name to link this new quotation to an " +"existing customer record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:39 +msgid "" +":guilabel:`Do not link to a customer`: the quotation will **not** be linked " +"to a customer, and no changes are made to the customer information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:42 +msgid "" +"Once this button is clicked, a new quotation form appears. Confirm the " +"information in the top half of the form, and update any missing or incorrect" +" fields:" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:45 +msgid "" +":guilabel:`Customer`: the company or contact for whom this quotation was " +"created." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:46 +msgid "" +":guilabel:`Referrer`: if this customer was referred by another customer or " +"contact, select it from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:48 +msgid "" +":guilabel:`Invoice Address`: physical address where the invoice should be " +"sent." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:49 +msgid "" +":guilabel:`Delivery Address`: physical address where any products should be " +"delivered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:50 +msgid "" +":guilabel:`Quotation Template`: if applicable, select a pre-configured " +":doc:`quotation template " +"</applications/sales/sales/send_quotations/quote_template>` from this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:52 +msgid ":guilabel:`Expiration`: date when this quotation is no longer valid." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:53 +msgid "" +":guilabel:`Quotation Date`: creation date of draft/sent orders, confirmation" +" date of confirmed orders. Note that this field is only visible if " +":doc:`Developer mode (debug mode) </applications/general/developer_mode>` is" +" active." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:56 +msgid "" +":guilabel:`Recurring Plan`: if this quotation is for a recurring product or " +"subscription, select the recurring plan configuration to be used." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:58 +msgid ":guilabel:`Pricelist`: select a pricelist to be applied to this order." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:59 +msgid "" +":guilabel:`Payment Terms`: select any applicable payment terms for this " +"quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:66 +msgid "" +"The :guilabel:`Expiration` field automatically populates based on the " +"creation date of the quotation, and the default validity time frame." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:69 +msgid "" +"To update the default validity time frame, navigate to :menuselection:`Sales" +" app --> Configuration --> Settings --> Quotations & Orders` and update the " +":guilabel:`Default Quotation Validity` field. To disable automatic " +"expiration, enter `0` in this field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:73 +msgid "When the desired changes are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:75 +msgid "" +"When using a quotation template, the expiration date is based off of the " +":guilabel:`Quotation Validity` field on the template. To alter the validity " +"date computation on a template, go to :menuselection:`Sales app --> " +"Configuration --> Sales Orders --> Quotation Templates`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:79 +msgid "" +"Then, click on a template to open it, and update the number in the " +":guilabel:`Quotation Validity` field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:83 +msgid "Order lines" +msgstr "รายการคำสั่งซื้อ" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:85 +msgid "" +"After updating the customer, payment, and deadline information on the new " +"quotation, the :guilabel:`Order Lines` tab can be updated with the " +"appropriate product information." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:88 +msgid "" +"To do that, click :guilabel:`Add a product` in the :guilabel:`Order Lines` " +"tab." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:90 +msgid "" +"Next, type the name of an item into the :guilabel:`Product` field to search " +"through the product catalog. Then, select a product from the drop-down menu," +" or create a new one by selecting :guilabel:`Create` or :guilabel:`Create " +"and Edit`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:94 +msgid "" +"After selecting a product, update the :guilabel:`Quantity`, if necessary. " +"Confirm the information in the remaining fields." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:97 +msgid "" +"To remove a line from the quotation, click the :guilabel:`🗑️ (trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:99 +msgid "Repeat the steps above until the quotation is complete." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:102 +msgid "Preview and send quotation" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:104 +msgid "" +"To see a preview of the quotation as the customer will see it, click the " +":guilabel:`Preview` button. Doing so opens a preview in the " +":guilabel:`Customer Portal`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:107 +msgid "" +"After reviewing the customer preview, click :guilabel:`Return to edit mode` " +"to return to the quotation form in the backend." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:110 +msgid "" +"When the quotation is ready to deliver to the customer, click the " +":guilabel:`Send by Email` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:112 +msgid "" +"Doing so opens a pop-up window with a pre-configured email message. " +"Information from the quotation, including the contact information, total " +"cost, and quotation title are be imported from the quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:116 +msgid "A PDF of the quotation is added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:119 +msgid "" +"A pre-loaded template is used to create the email message. To alter the " +"template, click the internal link to the right of the :guilabel:`Load " +"template` field, located at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:123 +msgid "" +"To select a new template, select an option from the :guilabel:`Load " +"template` drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:125 +msgid "" +"Proceed to make any necessary changes to the email, then click " +":guilabel:`Send`. A copy of the message is added to the *Chatter* of the of " +"the record." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:128 +msgid "" +"After a quotation is sent, the originating opportunity's " +":guilabel:`Quotations` smart button updates with a new count. This " +"quotation, and all other quotations can be accessed through this smart " +"button at the top of the opportunity in the *CRM* app." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:132 +msgid "" +"Any quotations attached to the opportunity that are confirmed, and have " +"therefore been converted to sales orders, will be deducted from the number " +"listed on the :guilabel:`Quotations` smart button. Instead, the value of the" +" sales order will appear in the :guilabel:`Orders` smart button located in " +"the same control panel." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:138 +msgid "" +"`Quotation templates " +"</applications/sales/sales/send_quotations/quote_template/>`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:139 +msgid "" +"`Optional products " +"</applications/sales/sales/send_quotations/optional_products/>`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140 +msgid "" +"`Quotation deadlines </applications/sales/sales/send_quotations/deadline/>`_" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143 +msgid "Mark an opportunity won or lost" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:145 +msgid "" +"In order to keep the pipeline up to date and accurate, opportunities need to" +" be identified as *won* or *lost* once a customer has responded to a " +"quotation." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 +msgid "" +"To mark an opportunity as *won* or *lost*, return to the opportunity using " +"the breadcrumbs at the top-left of the quotation form. Or navigate to " +":menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct " +"opportunity to open it." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:152 +msgid "" +"At the top-left of the form, click on either the :guilabel:`Won` or " +":guilabel:`Lost` button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:154 +msgid "" +"If the opportunity is marked *won*, a green :guilabel:`Won` banner is added " +"to the record, and it is moved to the :guilabel:`Won` stage." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:157 +msgid "" +"Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a " +":guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be " +"entered." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:160 +msgid "" +"From the :guilabel:`Lost Reason` drop-down field, choose an existing lost " +"reason. If no applicable reason is available, create a new one by entering " +"it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:165 +msgid "" +"It's best practice to try and use pre-configured :guilabel:`Lost Reason` " +"values as much as possible or to limit the creation of new values only to " +"sales team leads. Using consistent values for this parameter will make " +"pipeline analysis easier and more accurate when filtering for the " +":guilabel:`Lost Reason` parameter." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:170 +msgid "" +"To set up new values for this field, navigate to :menuselection:`CRM --> " +"Configuration --> Lost Reasons`, and click both :guilabel:`New`and " +":guilabel:`Save` for each new entry added to the list." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:174 +msgid "" +"Additional notes and comments can be added in the :guilabel:`Closing Note` " +"field." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:176 +msgid "" +"When all the desired information has been entered in the :guilabel:`Mark " +"Lost` pop-up window, click :guilabel:`Mark as Lost`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 +msgid "" +"Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and " +"Odoo returns to the opportunity form, where a new red :guilabel:`Lost` " +"banner is now present in the upper-right corner of the opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:183 +msgid "" +"Once an opportunity is marked as *lost*, it is no longer considered active, " +"and it is removed from the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:186 +msgid "" +"In order to view a *lost* opportunity from the pipeline, click the " +":guilabel:`down arrow icon` to the right of the search bar, and select " +"either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that" +" appears." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:191 +msgid "" +"While opportunities that have been marked as *lost* are considered " +"*Archived*, be advised that, in order for an opportunity to be included as " +"*lost* in reporting, it **must** be specifically marked as *lost*, not " +"*Archived*." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:196 +msgid "" +"`Manage lost opportunities " +"</applications/sales/crm/pipeline/lost_opportunities>`_" +msgstr "" + +#: ../../content/applications/sales/crm/optimize.rst:5 +msgid "Optimize your Day-to-Day work" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:3 +msgid "How to motivate and reward my salespeople?" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:5 +msgid "" +"Challenging your employees to reach specific targets with goals and rewards " +"is an excellent way to reinforce good habits and improve your salespeople " +"productivity. The Gamification module gives you simple and creative ways to " +"motivate and evaluate your employees with real-time recognition and badges " +"inspired by game mechanics." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:13 +msgid "" +"Install the *Gamification* module, or the *CRM gamification* one, which adds" +" some useful data (goals and challenges) that can be used on *CRM/Sale*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the gamification module being installed in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:21 +msgid "Create a challenge" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:23 +msgid "" +"Now, create your first challenge by going to :menuselection:`Settings --> " +"Gamification Tools --> Challenges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:27 +msgid "" +"As the gamification tool is a one-time technical setup, you need to activate" +" the technical features in order to access the configuration. To do so, go " +"to *Settings* and *Activate the developer mode*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View if the gamification tools menu in Odoo Settings" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:35 +msgid "" +"A challenge is a mission that you send to your sales team. It can include " +"one or several goals, set for a specific period of time. Configure your " +"challenge as follows:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:38 +msgid "Assign the salespeople to be challenged;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:39 +msgid "Assign a responsible;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:40 +msgid "Set up the periodicity along with the start and the end date;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:41 +msgid "Select your goals;" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:42 +msgid "Set up your rewards (badges)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:45 +msgid "" +"Badges are granted when a challenge is finished. This is either at the end " +"of a running period (eg: end of the month for a monthly challenge), at the " +"end date of a challenge (if no periodicity is set), or when the challenge is" +" manually closed." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:49 +msgid "" +"In the example below, 2 employees are being challenged with a *Monthly Sales" +" Target*. The challenge is based on 2 goals: the total amount invoiced and " +"number of new leads generated. At the end of the month, the winner will be " +"granted with a badge." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the challenge form and a challenge being created for Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:58 +msgid "Set up goals" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:60 +msgid "" +"The users can be evaluated using goals and numerical objectives to reach." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:62 +msgid "" +"**Goals** are assigned through *challenges* that evaluate (see image above) " +"and compare members of a team throughout time." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:66 +msgid "" +"You can create a new goal on the fly from a *Challenge* by clicking on *Add " +"new item*, under *Goals*. Select the business object according to your " +"company's needs. Examples: number of new leads, time to qualify a lead, " +"total amount invoiced in a specific week, month or any other time frame " +"based on your management preferences, etc." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "" +"View of the goal definition form and a goal definition being created for " +"Odoo Sales" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:73 +msgid "" +"Goals may include your database setup as well (e.g. set your company data " +"and a timezone, create new users, etc.)." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:77 +msgid "Set up rewards" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:79 +msgid "" +"For non-numerical achievements, **Badges** can be granted to users. From a " +"simple thank you to an exceptional achievement, a badge is an easy way to " +"express gratitude to a user for their good work. To create and grant badges " +"to your employees based on their performance, go to :menuselection:`Settings" +" --> Gamification Tools --> Badges`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst-1 +msgid "View of the badges page in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 +msgid "Enrich your contacts base with Partner Autocomplete" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 +msgid "" +"Partner Autocomplete helps you to enrich your contacts database with " +"corporate data. Select one of the companies suggested in the dropdown, and " +"quickly get all the information you need." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 +msgid "" +"Go to :menuselection:`Settings --> Contacts` and activate the *Partner " +"Autocomplete* feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "View of settings page and the activations of the feature in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:18 +msgid "Enrich your contacts with corporate data" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:22 +msgid "" +"From any module, once you start to create a new contact typing the name of " +"it, the system will suggest a potential match. If you select it, the contact" +" will be populated with corporate data." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:23 +msgid "" +"For example, after typing *Odoo*, you will get the following information:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "Creating a new contact in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst-1 +msgid "" +"View of the information being shown about odoo with the autocomplete option " +"in Odoo" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:33 +msgid "" +"Partner Autocomplete also works if you enter a VAT number instead of a " +"company name." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 +msgid "" +"*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires" +" prepaid credits to be used. Each request will consume one credit." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:41 +msgid "" +"To buy credits, go to :menuselection:`Settings --> Contacts --> Partner " +"Autocomplete or Odoo IAP --> View My Services` and select a package." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:44 +msgid "" +"If you run out of credits, the only information that will be populated when " +"clicking on the suggested company will be the website link and the logo." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46 +msgid "" +"If you are on Odoo Online and you have the Enterprise version, you benefit " +"from free trial credits to test the feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 +msgid "" +"Learn about our *Privacy Policy* `here " +"<https://iap.odoo.com/privacy#header_2>`_." +msgstr "" + +#: ../../content/applications/sales/crm/performance.rst:5 +msgid "Analyze performance" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:3 +msgid "Pipeline Analysis" +msgstr "การวิเคราะห์ไปป์ไลน์" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:5 +msgid "" +"The *CRM* app manages the sales pipeline as leads/opportunities move from " +"stage to stage, origination to sale (**Won**) or archival (**Lost**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:8 +msgid "" +"After organizing the pipeline, use the search options and reports available " +"on the *Pipeline Analysis* page to gain insight into the effectiveness of " +"the pipeline and its users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:11 +msgid "" +"To access the *Pipeline Analysis* page, go to :menuselection:`CRM app --> " +"Reporting --> Pipeline`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"Open the CRM app and click on the Reporting tab along the top, then click " +"Pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:20 +msgid "Navigate the pipeline analysis page" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:22 +msgid "" +"Upon accessing the :guilabel:`Pipeline Analysis` page, a bar graph " +"showcasing the leads from the past year automatically populates. The bars " +"represent the number of leads in each stage of the sales pipeline, color-" +"coded to show the month the lead reached that stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The default state of the Pipeline Analysis page is a graph, with many " +"options to change it." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:30 +msgid "" +"The interactive elements of the :guilabel:`Pipeline Analysis` page " +"manipulate the graph to report different metrics in several views. From " +"left-to-right, top-to-bottom, the elements include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:33 +msgid "" +":guilabel:`Actions`: represented by the :guilabel:`⚙️ (gear)` icon, located " +"next to the :guilabel:`Pipeline Analysis` page title. When clicked, a drop-" +"down menu appears with three options, each with their own sub-menu: " +":guilabel:`Knowledge`, :guilabel:`Dashboard`, :guilabel:`Spreadsheet`. (See " +":ref:`Save and share reports <win_loss/save_reports>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:39 +msgid "" +"The :guilabel:`Knowledge` option is for linking to or inserting the graph in" +" a *Knowledge* app article." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:41 +msgid "" +"The :guilabel:`Dashboard` option is for adding the graph to a dashboard in " +"the *Dashboards* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:42 +msgid "" +"The :guilabel:`Spreadsheet` option is for linking the graph in a spreadsheet" +" in the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:44 +msgid "" +":guilabel:`Search...` bar: shows the filters and groupings currently being " +"applied to the graph. To add new filters/groups, type them into the search " +"bar, or click the :guilabel:`⬇️ (down arrow)` icon, at the end of the bar, " +"to open a drop-down menu of options. (See :ref:`Search Options " +"<win_loss/search>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:49 +msgid "" +"In the upper-right corner, there are view options represented by different " +"icons. (See :ref:`View Options <win_loss/view>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:52 +msgid "" +":guilabel:`Graph` view: displays the data in a bar graph. This is the " +"default view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:53 +msgid "" +":guilabel:`Pivot` view: displays the data in a customizable, categorized " +"metrics table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:54 +msgid "" +":guilabel:`Cohort` view: displays and organizes the data, based on their " +":guilabel:`Created on` and :guilabel:`Closed Date` week (default), day, " +"month, or year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:56 +msgid ":guilabel:`List` view: displays the data in a list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:58 +msgid "" +"Located on the far-left side of the page, beneath the :guilabel:`Pipeline " +"Analysis` page title, there are more configurable filter and view options." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:61 +msgid "" +":guilabel:`Measures`: opens a drop-down menu of different measurement " +"options that can be seen in the graph, pivot, or cohort view. The " +":guilabel:`Measure` drop-down menu is not available in the list view. (See " +":ref:`Measurement Options <win_loss/measure>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:64 +msgid "" +":guilabel:`Insert in Spreadsheet`: opens a pop-up window with options for " +"adding a graph or pivot table to a spreadsheet in the *Documents* app or a " +"dashboard in the *Dashboards* app. This option is not available in the " +"cohort or list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:68 +msgid "With the graph view selected, the following options are available:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:70 +msgid ":guilabel:`Bar Chart`: switches the graph to a bar chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:71 +msgid ":guilabel:`Line Chart`: switches the graph to a line chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:72 +msgid ":guilabel:`Pie Chart`: switches the graph to a pie chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:73 +msgid "" +":guilabel:`Stacked`: when selected, the results of each stage of the graph " +"are stacked on top of each other. When not selected, the results in each " +"stage are shown as individual bars." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:75 +msgid "" +":guilabel:`Descending`: re-orders the stages in the graph in descending " +"order from left-to-right. Click the icon a second time to deselect it. " +"Depending on the search criteria, this option may not be available." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:78 +msgid "" +":guilabel:`Ascending`: re-orders the stages in the graph in ascending order " +"from left-to-right. Click the icon a second time to deselect it. Depending " +"on the search criteria, this option may not be available." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:82 +msgid "With the pivot view selected, the following options are available:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:84 +#: ../../content/applications/sales/crm/performance/win_loss.rst:326 +msgid ":guilabel:`Flip Axis`: flips the X and Y axis for the entire table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:85 +#: ../../content/applications/sales/crm/performance/win_loss.rst:327 +msgid "" +":guilabel:`Expand All`: when additional groupings are selected using the " +":guilabel:`➕ (plus sign)` icons, this button opens those groupings under " +"every row." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:87 +#: ../../content/applications/sales/crm/performance/win_loss.rst:329 +msgid ":guilabel:`Download xlsx`: downloads the table as an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:92 +msgid "Search options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:94 +msgid "" +"The :guilabel:`Pipeline Analysis` page can be customized with various " +"filters and grouping options." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:96 +msgid "" +"To add new search criteria, type the desired criteria into the search bar, " +"or click the :guilabel:`⬇️ (down arrow)` icon, next to the search bar, to " +"open a drop-down menu of all options. See the sections below for more " +"information on what each option does." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"Clicking on the down arrow next to the search bar opens a menu of filters " +"for the analysis." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:106 +msgid "Filters" +msgstr "ตัวกรอง" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:108 +msgid "" +"The :guilabel:`Filters` section allows users to add pre-made and custom " +"filters to the search criteria. Multiple filters can be added to a single " +"search." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:111 +msgid ":guilabel:`My Pipeline`: show leads assigned to the current user." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:112 +msgid "" +":guilabel:`Opportunities`: show leads that have been qualified as " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:113 +msgid "" +":guilabel:`Leads`: show leads that have yet to be qualified as " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:114 +msgid ":guilabel:`Active`: show active leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:115 +msgid ":guilabel:`Inactive`: show inactive leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:116 +msgid ":guilabel:`Won`: show leads that have been marked **Won**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:117 +msgid ":guilabel:`Lost`: show leads that have been marked **Lost**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:118 +msgid "" +":guilabel:`Created On`: show leads that were created during a specific " +"period of time. By default, this is the past year, but it can be adjusted as" +" needed, or removed entirely." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:120 +msgid "" +":guilabel:`Expected Closing`: show leads that are expected to close (marked " +"**Won**) during a specific period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:122 +msgid "" +":guilabel:`Date Closed`: show leads that were closed (marked **Won**) during" +" a specific period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:124 +msgid "" +":guilabel:`Archived`: show leads that have been archived (marked **Lost**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:125 +msgid "" +":guilabel:`Add Custom Filter`: allows the user to create a custom filter " +"with numerous options. (See :ref:`Add Custom Filters and Groups " +"<win_loss/custom_filters>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:129 +msgid "Group By" +msgstr "กลุ่มโดย" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:131 +msgid "" +"The :guilabel:`Group By` section allows users to add pre-made and custom " +"groupings to the search results. Multiple groupings can be added to split " +"results into more manageable chunks." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:135 +msgid "" +"The order that groupings are added affects how the final results are " +"displayed. Try selecting the same combinations in a different order to see " +"what works best for each use case." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:139 +msgid "" +":guilabel:`Salesperson`: groups the results by the Salesperson to whom a " +"lead is assigned." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:140 +msgid "" +":guilabel:`Sales Team`: groups the results by the Sales Team to whom a lead " +"is assigned." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:141 +msgid "" +":guilabel:`City`: groups the results by the city from which a lead " +"originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:142 +msgid "" +":guilabel:`Country`: groups the results by the country from which a lead " +"originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:143 +msgid "" +":guilabel:`Company`: groups the results by the company to which a lead " +"belongs (if multiple companies are activated in the database)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:145 +msgid "" +":guilabel:`Stage`: groups the results by the stages of the sales pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:146 +msgid "" +":guilabel:`Campaign`: groups the results by the marketing campaign from " +"which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:148 +msgid "" +":guilabel:`Medium`: groups the results by the medium (Email, Google Adwords," +" Website, etc.) from which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:150 +msgid "" +":guilabel:`Source`: groups the results by the source (Search engine, Lead " +"Recall, Newsletter, etc.) from which a lead originated." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:152 +msgid "" +":guilabel:`Creation Date`: groups the results by the date a lead was added " +"to the database." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:153 +msgid "" +":guilabel:`Conversion Date`: groups the results by the date a lead was " +"converted to an opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:155 +msgid "" +":guilabel:`Expected Closing`: groups the results by the date a lead is " +"expected to close (marked \"Won\")." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:157 +msgid "" +":guilabel:`Closed Date`: groups the results by the date a lead was " +"closed(marked \"Won\")." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:158 +msgid "" +":guilabel:`Lost Reason`: groups the results by the reason selected when a " +"lead was marked \"Lost.\"" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:160 +msgid "" +":guilabel:`Add Custom Group`: allows the user to create a custom group with " +"numerous options. (See :ref:`Adding Custom Filters and Groups " +"<win_loss/custom_filters>` for more information)" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:164 +msgid "Comparison" +msgstr "การเปรียบเทียบ" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:166 +msgid "" +"The :guilabel:`Comparison` section allows users to add comparisons to the " +"same search criteria over another period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:169 +msgid "" +"This option is only available if the search includes time-based filters, " +"such as :guilabel:`Created On`, :guilabel:`Expected Closing`, or " +":guilabel:`Date Closed`. While multiple time-based filters can be added at " +"once, only one comparison can be selected at a time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:174 +msgid "" +":guilabel:`Previous Period`: adds a comparison to the same search criteria " +"from the previous period." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:176 +msgid "" +":guilabel:`Previous Year`: adds a comparison to the same search criteria " +"from the previous year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:179 +msgid "Favorites" +msgstr "รายการโปรด" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:181 +msgid "" +"The :guilabel:`Favorites` section allows users to save a search for later, " +"so it does not need to be recreated every time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:184 +msgid "" +"Multiple searches can be saved, shared with others, or even set as the " +"default for whenever the :guilabel:`Pipeline Analysis` page is opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:187 +msgid "" +":guilabel:`Save current search`: save the current search criteria for later." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:189 +msgid "" +":guilabel:`Default filter`: when saving a search, check this box to make it " +"the default search filter when the :guilabel:`Pipeline Analysis` page is " +"opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:191 +msgid "" +":guilabel:`Shared`: when saving a search, check this box to make it " +"available to other users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:197 +msgid "Add custom filters and groups" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:199 +msgid "" +"In addition to the pre-made options in the search bar, the " +":guilabel:`Pipeline Analysis` page can also utilize custom filters and " +"groups." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:202 +msgid "" +"Custom filters are complex rules that further customize the search results, " +"while custom groups display the information in a more organized fashion." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:205 +msgid "**To add a custom filter:**" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:207 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " +"icon next to the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:209 +msgid "In the drop-down menu, click :guilabel:`Add Custom Filter`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:210 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window appears with a default rule " +"(:guilabel:`Country is in _____`) comprised of three unique fields. These " +"fields can be edited to make a custom rule, and multiple rules can be added " +"to a single custom filter." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:213 +msgid "" +"To edit a rule, start by clicking the first field (:guilabel:`Country`), and" +" select an option from the drop-down menu. The first field determines the " +"primary subject of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:215 +msgid "" +"Next, click the second field, and select an option from the drop-down menu. " +"The second field determines the relationship of the first and third fields, " +"and is usually an **is** or **is not** statement, but can also be **greater " +"than or less than** statements, and more." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:218 +msgid "" +"Finally, click the third field, and select an option from the drop-down " +"menu. The third field determines the secondary subject of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:220 +msgid "With all three fields selected, the rule is complete." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:222 +msgid "" +"**To add more rules:** click :guilabel:`New Rule` and repeat steps 4-7, as " +"needed." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:223 +msgid "" +"**To delete a rule:** click the :guilabel:`🗑️ (trash)` icon to the right of " +"the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:224 +msgid "" +"**To duplicate an existing rule:** click the :guilabel:`➕ (plus sign)` icon " +"to the right of the rule." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:226 +msgid "" +"**To create more complex rules:** click the :guilabel:`Add branch` icon to " +"the right of the rule. This adds another modifier below the rule for adding " +"an \"all of\" or \"any of\" statement." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The add branch feature allows the creation of more complex all or any " +"statements for rules." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:233 +msgid "" +"Once all rules have been added, click :guilabel:`Add` to add the custom " +"filter to the search criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:236 +msgid "" +"**To remove a custom filter:** click the :guilabel:`✖️ (x)` icon beside the " +"filter in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:239 +msgid "**To add a custom group:**" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:241 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`down arrow` " +"icon next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:243 +msgid "" +"In the drop-down menu that appears, click :guilabel:`Add Custom Group`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:244 +msgid "" +"Scroll through the options in the drop-down menu, and select one or more " +"groups." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:246 +msgid "" +"**To remove a custom group:** click the :guilabel:`✖️ (x)` icon beside the " +"custom group in the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:252 +msgid "Measurement options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:254 +msgid "" +"By default, the :guilabel:`Pipeline Analysis` page measures the total " +":guilabel:`Count` of leads that match the search criteria, but can be " +"changed to measure other items of interest." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:257 +msgid "" +"To change the selected measurement, click the :guilabel:`Measures` button on" +" the top-left of the page, and select one of the following options from the " +"drop-down menu:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:260 +msgid "" +":guilabel:`Days to Assign`: measures the number of days it took a lead to be" +" assigned after creation." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:262 +msgid "" +":guilabel:`Days to Close`: measures the number of days it took a lead to be " +"closed (marked **Won**)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:264 +msgid "" +":guilabel:`Days to Convert`: measures the number of days it took a lead to " +"be converted to an opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:266 +msgid "" +":guilabel:`Exceeded Closing Days`: measures the number of days by which a " +"lead exceeded its Expected Closing date." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:268 +msgid "" +":guilabel:`Expected MRR`: measures the Expected Recurring Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:269 +msgid ":guilabel:`Expected Revenue`: measures the Expected Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:270 +msgid "" +":guilabel:`Prorated MRR`: measures the Prorated Monthly Recurring Revenue of" +" a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:271 +msgid "" +":guilabel:`Prorated Recurring Revenues`: measures the Prorated Recurring " +"Revenues of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:272 +msgid ":guilabel:`Prorated Revenue`: measures the Prorated Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:273 +msgid "" +":guilabel:`Recurring Revenues`: measures the Recurring Revenue of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:274 +msgid "" +":guilabel:`Count`: measures the total amount of leads that match the search " +"criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:279 +msgid "View options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:281 +msgid "" +"After configuring filters, groupings, and measurements, the " +":guilabel:`Pipeline Analysis` page can display the data in a variety of " +"ways. By default, the page uses the graph view, but can be changed to a " +"pivot view, cohort view, or list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:285 +msgid "" +"To change the pipeline to a different view, click one of the four view " +"icons, located in the top-right of the :guilabel:`Pipeline Analysis` page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:290 +msgid "Graph View" +msgstr "มุมมองกราฟ" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:292 +msgid "" +"The graph view is the default selection for the :guilabel:`Pipeline " +"Analysis` page. It displays the analysis as either a: bar chart, line chart," +" or pie chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:295 +msgid "" +"This view option is useful for quickly visualizing and comparing simple " +"relationships, like the :guilabel:`Count` of leads in each stage, or the " +"leads assigned to each :guilabel:`Salesperson`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:299 +msgid "" +"By default, the graph measures the :guilabel:`Count` of leads in each group," +" but this can be changed by clicking the :guilabel:`Measures` button, and " +":ref:`selecting another option <win_loss/measure>` from the resulting drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"The Graph View displays the analysis as a Bar Chart, Line Chart, or Pie " +"Chart." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:308 +msgid "" +"When using a bar chart in this view, consider deselecting the " +":guilabel:`Stacked` option, in order to make the breakdown of results more " +"legible." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:311 +#: ../../content/applications/sales/crm/performance/win_loss.rst:512 +msgid "Pivot View" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:313 +msgid "" +"The pivot view displays the results of the analysis as a table. By default, " +"the table groups the results by the stages of the sales pipeline, and " +"measures :guilabel:`Expected Revenue`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:316 +msgid "" +"The pivot view is useful for analyzing more detailed numbers than the graph " +"view can handle, or for adding the data to a spreadsheet, where custom " +"formulas can be set up, like in an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Pivot View displays the analysis as a table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:324 +msgid "" +"The three icons at the top-left of the page perform the following functions:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:332 +msgid "" +"The :guilabel:`Stage` grouping cannot be removed, but the measurement can be" +" changed by clicking the :guilabel:`Measures` button, and selecting another " +"option." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:335 +msgid "Cohort View" +msgstr "มุมมอง" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:337 +msgid "" +"The cohort view displays the analysis as periods of time (cohorts) that can " +"be set to days, weeks, months, or years. By default, :guilabel:`Week` is " +"selected." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:340 +msgid "" +"This view option is useful specifically for comparing how long it has taken " +"to close leads." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Cohort View displays the analysis as individual weeks of the year." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:346 +msgid "" +"From left-to-right, top-to-bottom, the columns in the chart represent the " +"following:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:348 +msgid "" +":guilabel:`Created On`: rows in this column represent the weeks of the year," +" in which records matching the search criteria exist." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:351 +msgid "" +"When set to :guilabel:`Week`, a row with the label :guilabel:`W52 2023` " +"means the results occurred in: Week 52 of the Year 2023." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:353 +msgid "" +":guilabel:`Measures`: the second column in the chart is the measurement of " +"the results. By default, it is set to :guilabel:`Count`, but can be changed " +"by clicking the :guilabel:`Measures` button, and selecting an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:356 +msgid "" +":guilabel:`Closed Date - By Day/Week/Month/Year`: this column looks at what " +"percentage of the measured results were closed in subsequent " +"days/weeks/months/years." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:358 +msgid "" +":guilabel:`Average`: this row provides the average of all other rows in the " +"column." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:360 +msgid "" +"The cohort view can also be downloaded as an Excel file, by clicking the " +":guilabel:`Download` icon in the top-left of the page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:363 +#: ../../content/applications/sales/crm/performance/win_loss.rst:537 +msgid "List View" +msgstr "รายการมุมมอง" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:365 +msgid "" +"The list view displays a single list of all leads matching the search " +"criteria. Clicking a lead opens the record for closer review. Additional " +"details such as :guilabel:`Country`, :guilabel:`Medium`, and more can be " +"added to the list, by clicking the :guilabel:`Filters` icon in the top-right" +" of the list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:370 +msgid "This view option is useful for reviewing many records at once." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"The List View displays a single list of all records matching the search " +"criteria." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:376 +msgid "" +"Clicking the :guilabel:`⚙️ (gear)` icon opens the Actions drop-down menu, " +"with options for the following:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:379 +msgid "" +":guilabel:`Import records`: opens a page for uploading a spreadsheet of " +"data, as well as a template spreadsheet to easily format that data." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:381 +msgid ":guilabel:`Export All`: downloads the list as an xlsx file for Excel." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:382 +msgid "" +":guilabel:`Knowledge`: inserts a view of, or link to, the list in an article" +" in the *Knowledge* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:384 +msgid "" +":guilabel:`Dashboard`: adds the list to *My Dashboard* in the *Dashboards* " +"app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:385 +msgid "" +":guilabel:`Spreadsheet`: links to, or inserts, the list in a spreadsheet in " +"the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:389 +msgid "" +"On the list view, clicking :guilabel:`New` closes the list, and opens the " +"*New Quotation* page. Clicking :guilabel:`Generate Leads` opens a pop-up " +"window for lead generation. Neither feature is intended to manipulate the " +"list view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:396 +msgid "Create reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:398 +msgid "" +"After understanding how to :ref:`navigate the pipeline analysis page " +"<win_loss/pipeline>`, the :guilabel:`Pipeline Analysis` page can be used to " +"create and share different reports. Between the pre-made options and custom " +"filter and groupings, almost any combination is possible." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:402 +msgid "" +"Once created, reports can be :ref:`saved to favorites, shared with other " +"users, and/or added to dashboards and spreadsheets <win_loss/save_reports>`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:405 +msgid "" +"A few common reports that can be created using the :guilabel:`Pipeline " +"Analysis` page are detailed below." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:411 +msgid "Win/Loss reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:413 +msgid "" +"Win/Loss is a calculation of active or previously active leads in a pipeline" +" that were either marked as **Won** or **Lost** over a specific period of " +"time. By calculating opportunities won over opportunities lost, teams can " +"clarify key performance indicators (KPIs) that are converting leads into " +"sales, such as specific teams or team members, certain marketing mediums or " +"campaigns, and so on." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:419 +msgid "" +"\\begin{equation}\n" +"Win/Loss Ratio = \\frac{Opportunities Won}{Opportunities Lost}\n" +"\\end{equation}\n" +"\n" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:424 +msgid "" +"A win/loss report filters the leads from the past year, whether won or lost," +" and groups the results by their stage in the pipeline. Creating this report" +" requires a custom filter, and grouping the results by :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The search criteria for win/loss reports is Created On, Stage, and Active is" +" in true false." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:432 +msgid "Follow the steps below to create a win/loss report:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:434 +msgid "Navigate to :menuselection:`CRM app --> Reporting --> Pipeline`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:435 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " +"arrow)` icon, next to the search bar, to open a drop-down menu of filters " +"and groupings." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Search menu containing the filters for a basic win/loss report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:442 +msgid "" +"In drop-down menu that appears, under the :guilabel:`Group By` heading, " +"click :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:443 +msgid "" +"Under the :guilabel:`Filters` heading, click :guilabel:`Add Custom Filter` " +"to open another pop-up menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:445 +msgid "" +"In the :guilabel:`Add Custom Filter` pop-up menu, click on the first field " +"in the :guilabel:`Match any of the following rules:` section. By default, " +"this field displays :guilabel:`Country`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:448 +msgid "" +"Clicking that first field reveals a sub-menu with numerous options to choose" +" from. From this sub-menu, locate and select the :guilabel:`Active` option. " +"Doing so automatically populates the remaining fields." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:452 +msgid "" +"The first field reads: :guilabel:`Active`. The second field reads: " +":guilabel:`is`. And lastly, the third field reads: :guilabel:`set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:455 +msgid "In total, the rule reads: :guilabel:`Active is set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:456 +msgid "" +"Click :guilabel:`New Rule`, change the first field to :guilabel:`Active`, " +"and the last field to :guilabel:`not set`. In total, the rule reads " +":guilabel:`Active is not set`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:458 +#: ../../content/applications/sales/crm/performance/win_loss.rst:640 +msgid "Click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"The Add Custom Filter menu showing two rules: (1) Active is set, and (2) " +"Active is not set." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:464 +msgid "" +"The report now displays the total :guilabel:`Count` of leads, whether " +"\"Won\" or \"Lost,\" grouped by their stage in the CRM pipeline. Hover over " +"a section of the report to see the number of leads in that stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst-1 +msgid "" +"A basic win/loss report showing all leads whether won or lost grouped by " +"stage." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:473 +msgid "Customize win/loss reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:475 +msgid "" +"After :ref:`creating a win/loss report <win_loss/win_loss>`, consider using " +"the options below to customize the report for different needs." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:479 +msgid "" +"A sales manager might group wins and losses by salesperson, or sales team, " +"to see who has the best conversion rate. Or, a marketing team might group by" +" sources, or medium, to determine where their advertising has been most " +"successful." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:485 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:487 +msgid "" +"To add more filters and groups, click the :guilabel:`⬇️ (down arrow)` icon, " +"next to the search bar, and select one or more options from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:490 +msgid "Some useful options include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:492 +msgid "" +":guilabel:`Created on`: adjusting this filter to a different period of time," +" such as the last 30 days, or the last quarter, can provide more timely " +"results." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:494 +msgid "" +":guilabel:`Add Custom Filter`: clicking this option, and scrolling through " +"the numerous options in the drop-down menu, opens up additional search " +"criteria, like :guilabel:`Last Stage Update` or :guilabel:`Lost Reason`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:497 +msgid "" +":guilabel:`Add Custom Group > Active`: Clicking :menuselection:`Add Custom " +"Group --> Active` separates the results into **Won** (:guilabel:`true`) or " +"**Lost** (:guilabel:`false`). This shows at what stage leads are being " +"marked **Won** or **Lost**." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:500 +msgid "" +":guilabel:`Multiple Groupings`: add multiple :guilabel:`Group By` selections" +" to split results into more relevant and manageable chunks." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:503 +msgid "" +"Adding :guilabel:`Salesperson` or :guilabel:`Sales Team` breaks up the total" +" count of leads in each :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:505 +msgid "" +"Adding :guilabel:`Medium` or :guilabel:`Source` can reveal what marketing " +"avenues generate more sales." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "The Search menu open and the Won and Lost filters highlighted." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:514 +msgid "" +"By default, pivot view groups win/loss reports by :guilabel:`Stage` and " +"measures :guilabel:`Expected Revenue`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:517 +msgid "To flesh out the table:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:519 +msgid "Click the :guilabel:`⬇️ (down arrow)` next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:520 +msgid "" +"In the pop-up menu, replace the :guilabel:`Stage` grouping with something " +"like :guilabel:`Salesperson` or :guilabel:`Medium`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:522 +msgid "" +"Click the :guilabel:`Measures` button and click :guilabel:`Count` to add the" +" number of leads back into the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:525 +msgid "" +"Other useful measures for pivot view include :guilabel:`Days to Assign` and " +":guilabel:`Days to Close`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "A win/loss report in Pivot View displays the data in table form." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:533 +msgid "" +"In pivot view, the :guilabel:`Insert In Spreadsheet` button may be greyed " +"out due to the report containing :guilabel:`duplicate group bys`. To fix " +"this, replace the :guilabel:`Stage` grouping in the search bar with another " +"option." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:539 +msgid "In list view, a win/loss report displays all leads on a single page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:541 +msgid "" +"To better organize the list, click the :guilabel:`⬇️ (down arrow)` next to " +"the search bar, and add more relevant groupings or re-organize the existing " +"ones. To re-order the nesting, remove all :guilabel:`Group By` options and " +"re-add them in the desired order." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:545 +msgid "To add more columns to the list:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:547 +msgid "Click the :guilabel:`Filters` icon in the top-right of the page." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:548 +msgid "" +"Select options from the resulting drop-down menu. Some useful filters " +"include:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:550 +msgid "**Campaign**: Shows the marketing campaign that originated each lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:551 +msgid "" +"**Medium**: Shows the marketing medium (Banner, Direct, Email, Google " +"Adwords, Phone, Website, etc.) that originated each lead." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:553 +msgid "" +"**Source**: Shows the source of each lead (Newsletter, Lead Recall, Search " +"Engine, etc.)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"A win/loss report in List View displays all leads in an easy-to-read list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:562 +msgid "Save and share reports" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:564 +msgid "" +"After :ref:`creating a report <win_loss/reports>`, the search criteria can " +"be saved, so the report does not need to be created again in the future. " +"Saved searches automatically update their results every time the report is " +"opened." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:568 +msgid "" +"Additionally, reports can be shared with others, or added to " +"spreadsheets/dashboards for greater customization and easier access." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:573 +msgid "Save to Favorites" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:575 +msgid "To save a report for later:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:577 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⬇️ (down " +"arrow)` icon, next to the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:579 +msgid "" +"In the drop-down menu that appears, under the :guilabel:`Favorites` heading," +" click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:581 +msgid "In the next drop-down menu that appears, enter a name for the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:583 +msgid "" +"Checking the :guilabel:`Default filter` box sets this report as the default " +"analysis when the :guilabel:`Pipeline Analysis` page is accessed." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:585 +msgid "" +"Checking the :guilabel:`Shared` box makes this report available to other " +"users." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:587 +msgid "" +"Finally, click :guilabel:`Save`. The report is now saved under the " +":guilabel:`Favorites` heading." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"Under the Favorites heading, click Save current search and save the report " +"for later." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:594 +msgid "Add to a Spreadsheet" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:596 +msgid "" +"Inserting a report into a spreadsheet not only saves a copy of the report, " +"it allows users to add charts and formulas like in an Excel file." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:599 +msgid "To save a report as a spreadsheet:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:601 +msgid "**In Graph or Pivot View**:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:603 +msgid "Click the :guilabel:`Insert in spreadsheet` button." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:604 +msgid "In the pop-up menu that appears, click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:606 +msgid "**In Cohort or List View**:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:608 +msgid "Click the :guilabel:`⚙️ (gear)` icon." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:609 +msgid "" +"In the drop-down menu that appears, hover over :guilabel:`Spreadsheet`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:610 +msgid "" +"In the next drop-down menu, click either :guilabel:`Insert in spreadsheet` " +"or :guilabel:`Link in spreadsheet`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:613 +msgid "Saved reports are viewable in the *Documents* app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"Pivot View reports especially benefit from being inserted in spreadsheets." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:620 +msgid "" +"After modifying a spreadsheet and adding additional formulas, consider then " +"adding the entire spreadsheet to a dashboard. Using this method, the " +"spreadsheet can be added to a public dashboard instead of only :guilabel:`My" +" Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:624 +msgid "Click :menuselection:`File --> Add to dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:625 +msgid "" +"In the pop-up menu that appears, name the spreadsheet and select a " +":guilabel:`Dashboard Section` to house the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:627 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:629 +msgid "Add to a Dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:631 +msgid "" +"Adding a report to a dashboard saves it for later and makes it easy to view " +"alongside the rest of :guilabel:`My Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:634 +msgid "To add a report to :guilabel:`My dashboard`:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:636 +msgid "" +"On the :guilabel:`Pipeline Analysis` page, click the :guilabel:`⚙️ (gear)` " +"icon." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:637 +msgid "In the drop-down menu that appears, hover over :guilabel:`Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:638 +msgid "" +"In the :guilabel:`Add to my dashboard` drop-down menu, enter a name for the " +"report (by default, it is named :guilabel:`Pipeline`)." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:642 +msgid "To view a saved report:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:644 +msgid "" +"Return to the main apps page, and navigate to :menuselection:`Dashboards app" +" --> My Dashboard`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:0 +msgid "" +"To access the saved report, open the Dashboard app and click My Dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:652 +msgid ":doc:`../acquire_leads/convert`" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:653 +msgid ":doc:`../acquire_leads/send_quotes`" +msgstr "" + +#: ../../content/applications/sales/crm/performance/win_loss.rst:654 +msgid ":doc:`../pipeline/lost_opportunities`" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline.rst:5 +msgid "Organize the pipeline" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:3 +msgid "Manage lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 +msgid "" +"Not all opportunities result in successful sales. In order to keep the " +"pipeline up to date, lost opportunities need to be identified. Specifying " +"the reason why an opportunity was lost provides additional insight that can " +"prove useful for future opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 +msgid "Mark a lead as lost" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 +msgid "" +"To mark a lead as lost, open the :menuselection:`CRM` application, and " +"select a lead from the pipeline, by clicking on its corresponding kanban " +"card. Doing so reveals that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 +msgid "" +"Then, click :guilabel:`Lost`, located at the top of the lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "" +"Buttons from the top of an opportunity record with the lost button " +"emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 +msgid "" +"This opens the :guilabel:`Lost Reason` popup. From the drop-down, choose an " +"existing lost reason. If no applicable reason is available, create a new one" +" by entering it into the :guilabel:`Lost Reason` field, and clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 +msgid "" +"Additional notes and comments can be added below the lost reason designated " +"in the :guilabel:`Lost Reason` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 +msgid "" +"When all the desired information has been entered in the :guilabel:`Lost " +"Reason` pop-up window, click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Lost reasons popup with sample reasons." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 +msgid "" +"Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo " +"returns to the lead detail form, where a new red :guilabel:`Lost` banner is " +"now present in the upper-right corner of the lead." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 +msgid "Create/edit lost reasons" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 +msgid "" +"To create a new lost reason, or edit an existing one, navigate to " +":menuselection:`CRM app --> Configuration --> Lost Reasons`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 +msgid "" +"To edit an existing reason, click on the reason that should be modified. " +"When clicked, that reason becomes highlighted. Once highlighted, change the " +"description of the selected lost reason by editing the " +":guilabel:`Description` field. When done, click :guilabel:`Save` in the " +"upper-left corner." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 +msgid "" +"To create a new lost reason, click :guilabel:`Create` in the upper-left " +"corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank " +"line in the :guilabel:`Description` field. Then, proceed to type in the new " +"lost reason in that new line. Once ready, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 +msgid "Retrieve lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 +msgid "" +"To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM " +"app` to the main :guilabel:`Pipeline` dashboard. Then, click the " +":guilabel:`Filters` drop-down menu, located beneath the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Search bar with lost filter emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +msgid "" +"From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` " +"option. Upon selecting :guilabel:`Lost`, only the leads that have been " +"marked as `Lost` appear on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 +msgid "" +"To filter leads by a specific lost reason, select :menuselection:`Filters " +"--> Add Custom Filter`. Doing so reveals another drop-down menu with three " +"fields." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 +msgid "" +"In the top field drop-down menu, select :guilabel:`Lost Reason`. In the " +"second field drop-down menu, select :guilabel:`Contains`. Then, in the third" +" field of the :guilabel:`Add Custom Field` sub menu, type in the specific " +"keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking " +":guilabel:`Apply`, Odoo reveals all the lost leads with a reason that " +"contains that specified keyword(s)." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Search bar with custom filter added for lost reason." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 +msgid "Restore lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 +msgid "" +"To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` " +"dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and" +" select the :guilabel:`Lost` option. Doing so reveals all the lost " +"opportunities on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 +msgid "" +"Then, click on the kanban card of the desired lost opportunity to restore, " +"which opens that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +msgid "" +"From the lost lead's detail form, click :guilabel:`Restore` in the upper-" +"left corner. Doing so removes the red :guilabel:`Lost` banner from the lead " +"form, signifying the lead has been restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Lost opportunity with emphasis on the Restore button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 +msgid "Restore multiple opportunities at once" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 +msgid "" +"To restore multiple opportunities at once, navigate to the main " +":guilabel:`Pipeline` dashboard in the *CRM* app, open the " +":guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 +msgid "" +"Next, select the list view option, which is represented by the three-line " +":guilabel:`☰ (list)` icon in the upper-right corner. Doing so places all the" +" leads from the :guilabel:`Pipeline` page in a list form. With the list form" +" chosen, select the checkbox to the left of each desired opportunity/lead to" +" be restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 +msgid "" +"Once the desired opportunities/leads have been selected, click the " +":guilabel:`⚙️ Action (gear)` drop-down menu at the top of the " +":guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down " +"menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 +msgid "" +"Doing so removes those selected lost opportunities from the " +":guilabel:`Pipeline` page because they no longer fit into the `Lost` filter " +"criteria. To reveal these newly-restored leads, delete the `Lost` filter " +"from the search bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst-1 +msgid "Action button from list view with the Unarchive option emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 +msgid ":doc:`../performance/win_loss`" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 +msgid "Multiple sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:5 +msgid "" +"Use the *Sales Teams* feature to manage several sales teams, departments, or" +" channels, each with their own unique sales processes." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:10 +msgid "Create a new sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:12 +msgid "" +"To create a new sales team, go to :menuselection:`CRM --> Configuration --> " +"Sales Teams`, then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:15 +msgid "" +"On the creation page, set an :guilabel:`Email Alias` to automatically " +"generate a lead/opportunity for this sales team every time a message is sent" +" to that unique email address. Choose whether to accept emails from " +":guilabel:`Everyone`, :guilabel:`Authenticated Partners`, or " +":guilabel:`Followers Only`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:20 +msgid "" +"Set an :guilabel:`Invoicing Target` if this team has specific monthly " +"revenue goals. Set a :guilabel:`Domain` to assign leads/opportunities to " +"this sales team based on specific filters, such as country, language, or " +"campaign." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Create a sales team in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:29 +msgid "Add members to a sales team" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:31 +msgid "" +"To add team members, click :guilabel:`Add` under the :guilabel:`Members` tab" +" when editing the sales team's configuration page. Select a salesperson from" +" the drop-down menu or create new salesperson. Set a maximum number of leads" +" that can be assigned to this salesperson in a 30-day period to ensure that " +"they do not overwork." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Add a salesperson in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:40 +msgid "" +"One person can be added as a team member or :guilabel:`Team Leader` to " +"multiple sales teams, allowing them to access all of the pipelines that they" +" need to." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:44 +msgid "Sales team dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:46 +msgid "" +"To view the sales team dashboard, go to :menuselection:`CRM --> Sales --> " +"Teams`. Odoo users will see any teams that they are a part of as dashboard " +"tiles." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:49 +msgid "" +"Each tile gives an overview of the sales team's open opportunities, " +"quotations, sales orders, and expected revenue, as well as a bar graph of " +"new opportunities per week and an invoicing progress bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "Sales team overview dashboard in Odoo CRM." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:57 +msgid "" +"Click on the three dots in the corner of a tile to open a navigational menu " +"that lets users quickly view documents or reports, create new quotations or " +"opportunities, pick a color for this team, or access the team's " +"configuration page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst-1 +msgid "" +"Click the Three Dot Menu in Odoo CRM dashboard to view documents and create " +"opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:65 +msgid "" +"Click on the :guilabel:`Pipeline` button to go directly to that team's CRM " +"pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads.rst:5 +msgid "Assign and track leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:3 +msgid "Assign leads with predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5 +msgid "" +"The Odoo *CRM* app can automatically assign leads/opportunities to sales " +"teams and salespeople. A standard practice is to assign leads based on the " +"probability of winning each lead. Companies can prioritize the leads that " +"are more likely to result in successful deals by quickly assigning them to " +"the appropriate salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10 +msgid "" +"Odoo automatically calculates the probability of winning each lead using a " +"method called *predictive lead scoring*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:14 +msgid "Predictive lead scoring" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16 +msgid "" +"Predictive lead scoring is a machine-learning model that uses historical " +"data from Odoo *CRM* to score open leads/opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19 +msgid "" +"As a company processes opportunities through the CRM pipeline, Odoo collects" +" data on which opportunities are won and lost. Predictive lead scoring uses " +"this data to predict the probability of winning each new lead or " +"opportunity." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:23 +msgid "" +"The more opportunities that are sent through the CRM pipeline, the more data" +" Odoo collects, resulting in more accurate probabilities." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:26 +msgid "" +"Specifically, Odoo's predictive lead scoring uses the *naive Bayes* " +"probability model:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:28 +msgid "" +"\\begin{equation}\n" +"P(A | B) = \\frac{P(A) \\times P(B | A)}{P(B)}\n" +"\\end{equation}\n" +"\n" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:33 +msgid "" +"The probability of success of each opportunity is displayed on the " +"opportunity form, and it updates automatically as the opportunity progresses" +" through the CRM pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The probability of success displayed on the opportunity form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:40 +msgid "" +"When an opportunity moves to the next stage, its probability of success " +"automatically increases according to the predictive lead scoring algorithm." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:46 +msgid "" +"Predictive lead scoring is always active in Odoo *CRM*. However, the " +"variables used to calculate the probability of success can be customized in " +"the settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:49 +msgid "" +"To customize the variables used by predictive lead scoring, go to " +":menuselection:`CRM --> Configuration --> Settings`. Under " +":guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update " +"Probabilities` button." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53 +msgid "" +"Then, click on the drop-down menu to choose which variables the predictive " +"lead scoring feature will take into account." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The Update Probabilities window in the Predictive Lead Scoring settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60 +msgid "Any number of the following variables can be activated:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62 +msgid "" +":guilabel:`State`: the geographical state from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:63 +msgid "" +":guilabel:`Country`: the geographical country from which the opportunity " +"originates" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64 +msgid "" +":guilabel:`Phone Quality`: whether or not a phone number is listed for the " +"opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65 +msgid "" +":guilabel:`Email Quality`: whether or not an email address is listed for the" +" opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:66 +msgid "" +":guilabel:`Source`: the source of an opportunity (e.g. search engine, social" +" media)" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:67 +msgid ":guilabel:`Language`: the spoken language specified on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68 +msgid ":guilabel:`Tags`: the tags placed on the opportunity" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:71 +msgid "" +"The variables `Stage` and `Team` are always in effect. `Stage` refers to the" +" CRM pipeline stage that an opportunity is in. `Team` refers to the sales " +"team that is assigned to an opportunity. Predictive lead scoring *always* " +"takes into account these two variables, regardless of which optional " +"variables are selected." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76 +msgid "" +"Next, click on the date field next to the option :guilabel:`Consider leads " +"created as of the:` to select the date from which predictive lead scoring " +"will begin its calculations." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79 +msgid "Lastly, click :guilabel:`Confirm` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82 +msgid "Change the probability manually" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84 +msgid "" +"An opportunity's probability of success can be changed manually on the " +"opportunity form. Click on the probability number to edit it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:88 +msgid "" +"Manually changing the probability removes the automatic probability updates " +"for that opportunity. The probability will no longer update automatically as" +" the opportunity moves through each stage of the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92 +msgid "" +"To reactivate automatic probability, click on the gear icon next to the " +"probability percentage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "" +"The gear icon used to reactivate automatic probability on an opportunity " +"form." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:99 +msgid "Assign leads based on probability" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:101 +msgid "" +"Odoo *CRM* can assign leads/opportunities to sales teams and salespeople " +"based on specified rules. Create assignment rules based on the leads' " +"probability of success to prioritize those that are more likely to result in" +" deals." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106 +msgid "Configure rule-based assignment" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108 +msgid "" +"To activate *rule-based assignment*, navigate to :menuselection:`CRM --> " +"Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:111 +msgid "" +"The rule-based assignment feature can be set to run :guilabel:`Manually`, " +"meaning an Odoo user must manually trigger the assignment, or " +":guilabel:`Repeatedly`, meaning Odoo will automatically trigger the " +"assignment according to the chosen time period." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115 +msgid "" +"To set up automatic lead assignment, select :guilabel:`Repeatedly` for the " +":guilabel:`Running` section. Then, customize how often Odoo will trigger the" +" automatic assignment in the :guilabel:`Repeat every` section." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst-1 +msgid "The Rule-Based Assignment setting in CRM settings." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:123 +msgid "" +"If rule-based assignment is set to run :guilabel:`Repeatedly`, the " +"assignment can still be triggered manually using the circular arrow icon in " +"the :guilabel:`Rule-Based Assignment` settings (or using the " +":guilabel:`Assign Leads` button on the sales team configuration page)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128 +msgid "Configure assignment rules" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:130 +msgid "" +"Next, configure the *assignment rules* for each sales team and/or " +"salesperson. These rules determine which leads Odoo assigns to which people." +" To get started, navigate to :menuselection:`CRM --> Configuration --> Sales" +" Teams`, and select a sales team." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:134 +msgid "" +"On the sales team configuration form, under :guilabel:`Assignment Rules`, " +"click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to " +"determine lead assignment for this sales team. The rules can include " +"anything that may be relevant for this company or team, and any number of " +"rules can be added." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139 +msgid "" +"Click :guilabel:`Add Filter` to start creating assignment rules. Click on " +"the :guilabel:`+` sign on the right of the assignment rule to add another " +"line. Click on the :guilabel:`x` symbol to remove the line." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143 +msgid "" +"To create an assignment rule based on an opportunity's probability of " +"success, click on the far left drop-down menu of an assignment rule line, " +"and select :guilabel:`Probability`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146 +msgid "" +"From the middle drop-down menu, select the desired equation symbol—most " +"likely the symbol for *greater than*, *less than*, *greater than or equal " +"to*, or *less than or equal to*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149 +msgid "" +"In the far right space, enter the desired number value of the probability. " +"Finally, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:153 +msgid "" +"To configure an assignment rule such that a sales team receives leads that " +"have a probability of success of 20% or greater, create a :guilabel:`Domain`" +" line that reads: `Probability >= 20`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:0 +msgid "" +"Sales team domain set to probability greater than or equal to twenty " +"percent." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:160 +msgid "" +"Separate assignment rules can also be configured for individual team " +"members. From the sales team configuration page, click on a team member in " +"the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click" +" :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164 +msgid "" +"If automatic lead assignment is configured in the settings, both the sales " +"team and individual team members have the option to :guilabel:`Skip auto " +"assignment`. Check this box to omit a particular sales team or salesperson " +"from being assigned leads automatically by Odoo's rule-based assignment " +"feature. If :guilabel:`Skip auto assignment` is activated, the sales team or" +" salesperson can still be assigned leads manually." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:170 +msgid "" +"To manually assign leads to this sales team, click on the :guilabel:`Assign " +"Leads` button at the top of the sales team configuration page. This will " +"assign any leads that are currently unassigned and match this team's " +"specified domain." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:3 +msgid "Track your prospects visits" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5 +msgid "" +"Tracking your website pages will give you much more information about the " +"interests of your website visitors." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8 +msgid "" +"Every tracked page they visit will be recorded on your lead/opportunity if " +"they use the contact form on your website." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14 +msgid "" +"To use this feature, install the free module *Lead Scoring* under your " +"*Apps* page (only available in Odoo Enterprise)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21 +msgid "Track a webpage" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23 +msgid "" +"Go to any static page you want to track on your website and under the " +"*Promote* tab you will find *Optimize SEO*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29 +msgid "There you will see a *Track Page* checkbox to track this page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35 +msgid "See visited pages in your leads/opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37 +msgid "" +"Now each time a lead is created from the contact form it will keep track of " +"the pages visited by that visitor. You have two ways to see those pages, on " +"the top right corner of your lead/opportunity you can see a *Page Views* " +"button but also further down you will see them in the chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43 +msgid "" +"Both will update if the viewers comes back to your website and visits more " +"pages." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52 +msgid "" +"The feature will not repeat multiple viewings of the same pages in the " +"chatter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55 +msgid "Your customers will no longer be able to keep any secrets from you!" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:6 +msgid "Point of Sale" +msgstr "การขายหน้าร้าน" + +#: ../../content/applications/sales/point_of_sale.rst:8 +msgid "" +"With **Odoo Point of Sale**, run your shops and restaurants easily. The app " +"works on any device with a web browser, even if you are temporarily offline." +" Product moves are automatically registered in your stock, you get real-time" +" statistics, and your data is consolidated across all shops." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:13 +msgid "" +"`Odoo Tutorials: Point of Sale Tutorials <https://www.odoo.com/slides/point-" +"of-sale-28>`_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:14 +msgid ":doc:`IoT Boxes Documentations </applications/productivity/iot>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:19 +msgid "Start a session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:21 +msgid "" +"From the **POS dashboard**, click :guilabel:`New Session`, and at the " +":guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to " +"start a POS session, or click :guilabel:`Continue Selling` if the session is" +" already opened." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:26 +msgid "" +":doc:`Multiple users <point_of_sale/employee_login>` can be logged into the " +"same session at the same time. However, the session can only be opened once " +"on the same browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:32 +msgid "Sell products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:34 +msgid "" +"Click on products to add them to the cart. To change the **quantity**, click" +" :guilabel:`Qty` and enter the number of products using the keypad. To add a" +" **discount** or modify the product **price**, click respectively " +":guilabel:`% Disc` or :guilabel:`Price` and enter the amounts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:38 +msgid "" +"Once an order is completed, proceed to checkout by clicking " +":guilabel:`Payment`. Select the **payment method**, enter the received " +"amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move " +"on to the next customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "POS session interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:46 +msgid "You can use both `,` and `.` on your keyboard as decimal separators." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:47 +msgid "" +"**Cash** is selected by default if you enter the amount without choosing a " +"payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:52 +msgid "Set customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:54 +msgid "" +"Registering your customer is necessary to :doc:`collect their loyalty points" +" and grant them rewards <point_of_sale/pricing/loyalty>`, automatically " +"apply the :doc:`attributed pricelist <point_of_sale/pricing/pricelists>`, or" +" :ref:`generate and print an invoice <receipts-invoices/invoices>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:59 +msgid "" +"You can create customers from an :ref:`open POS session <pos/session-start>`" +" by clicking :menuselection:`Customer --> Create`, and filling in the " +"contact information. You can also create customers from the backend by going" +" to :menuselection:`Point of Sale --> Orders --> Customers` and clicking " +":guilabel:`New`. Then, fill in the information and save." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:64 +msgid "" +"To set a customer during an order, access the list of customers by clicking " +":guilabel:`Customer` on the POS interface. You can also set a customer at " +"the payment screen by clicking :guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:71 +msgid "Customer notes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:73 +msgid "" +"You can add **customer notes** about specific products directly from an open" +" :ref:`POS session <pos/session-start>`. For instance, to provide cleaning " +"and maintenance tips. They can also be used to track a customer's particular" +" request, such as not wanting the product to be assembled for them." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:77 +msgid "" +"To do so, select a product and click :guilabel:`Customer Note` on the pad. " +"Doing so opens a pop-up window in which you can add or modify content for " +"the note." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:81 +msgid "" +"Product notes from an :doc:`imported SO <point_of_sale/shop/sales_order>` " +"are displayed identically in the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer note button and notes (SO and POS session) on products in the cart" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:87 +msgid "" +"Customer notes appear on customers' receipts and invoices similarly to how " +"they appear in the cart, under the related product." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Customer receipt with notes from an SO and from the customer note feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:96 +msgid "Return and refund products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:98 +msgid "To return and refund a product," +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:100 +msgid ":ref:`start a session <pos/session-start>` from the **POS dashboard**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:101 +msgid "click :guilabel:`Refund` and select the corresponding order;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:102 +msgid "select the product and the quantity to refund using the keypad;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:103 +msgid "click :guilabel:`Refund` to go back to the previous screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:104 +msgid "" +"once the order is completed, click :guilabel:`Payment` to proceed to the " +"refund;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:105 +msgid "" +"click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next " +"customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "refund view from a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:111 +msgid "" +"You can filter the **orders list** by :guilabel:`Receipt Number`, " +":guilabel:`Date` or :guilabel:`Customer` using the search bar." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:113 +msgid "" +"You can also refund a product by selecting the returned product from an open" +" session, and setting a negative quantity that equals the number of returned" +" products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by " +"the quantity of returned products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:120 +msgid "Manage the cash register" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:122 +msgid "" +"To add or take out cash from the register, click the **menu icon** in the " +"upper right corner of your screen and :guilabel:`Cash In/Out`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "" +"Dropdown menu to close a POS session, reach the backend, add or take cash out or check\n" +"orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:129 +msgid "" +"Doing so opens a pop-up window on which you can select :guilabel:`Cash In` " +"or :guilabel:`Cash Out`, enter the amount and the reason, and click " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:135 +msgid "Close the POS session" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:137 +msgid "" +"To close your session, click the **menu icon** in the upper right corner of " +"your screen and :guilabel:`Close Session`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:140 +msgid "" +"Doing so opens the :guilabel:`Closing Control` pop-up screen. From this " +"screen, you can retrieve various information:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:143 +msgid "" +"the number of orders made and the total amount made during the session;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:144 +msgid "the expected amounts grouped by payment method." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:146 +msgid "" +"Before closing this window, count your cash using the calculator icon. Doing" +" so opens a pop-up window that computes the total amount in the cash drawer " +"depending on the coins and bills counted and added manually. Then, click " +":guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed" +" amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money " +"Details` are specified in the **Notes** section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst-1 +msgid "How to close a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:155 +msgid "" +"Once you are done controlling the amounts, click :guilabel:`Close Session` " +"to close and go back to the **POS dashboard**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:159 +msgid "" +"To reach the backend without closing the session, click :guilabel:`Backend` " +"on the dropdown menu." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:161 +msgid "To abort, click :guilabel:`Discard` on the pop-up window." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:162 +msgid "" +"Depending on your setup, you might only be allowed to close a session if the" +" expected cash revenue equals the counted cash. To close it anyway, click " +":guilabel:`Ok` on the :guilabel:`Payments Difference` screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:167 +msgid "" +"It is strongly advised to close your POS session at the end of each day." +msgstr "" + +#: ../../content/applications/sales/point_of_sale.rst:168 +msgid "" +"To look at all your previous sessions, go to :menuselection:`Point of Sale " +"--> Orders --> Sessions`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:11 +msgid "Access POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:13 +msgid "" +"To access the general POS settings, go to :menuselection:`Point of Sale --> " +"Configuration --> Settings`. Then, open the dropdown menu in the " +":guilabel:`Point of Sale` field and select the POS to configure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "Dropdown menu to select the POS in the app settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:21 +msgid "" +"These settings are available to users with the :doc:`access rights " +"</applications/general/users/manage_users>` :guilabel:`Administration` set " +"as :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:25 +msgid "" +"You can also configure some settings from the dashboard by clicking the " +"vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a " +"popup window, from which you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:28 +msgid ":doc:`Enable multiple employees to log in. <employee_login>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:29 +msgid "" +":doc:`Connect and set up an IoT box. <../../productivity/iot/config/pos>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:30 +msgid ":doc:`Connect and set up an ePOS printer. <configuration/epos_ssc>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "popup window to access quick settings in POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:36 +msgid "" +"These settings are available to users with the :doc:`access rights " +"</applications/general/users/manage_users>` :guilabel:`Point of Sale` set as" +" :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:41 +msgid "Make products available" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst:43 +msgid "" +"To make products available for sale, go to :menuselection:`Point of Sale -->" +" Products --> Products`, and select a product to open the product form. In " +"the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration.rst-1 +msgid "Making a product available in your POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 +msgid "Self-signed certificate for ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 +msgid "" +"ePOS printers are designed to work seamlessly with Point of Sale systems. " +"Once connected, the two devices automatically share information, enabling " +"the direct printing of tickets from the POS system to the ePOS printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 +msgid "" +"These `Epson ePOS printers <https://c4b.epson-" +"biz.com/modules/community/index.php?content_id=91>`_ are compatible with " +"Odoo:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:15 +msgid "TM-H6000IV-DT (Receipt printer only)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 +msgid "TM-T70II-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 +msgid "TM-T88V-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 +msgid "TM-L90-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 +msgid "TM-T20II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 +msgid "TM-T70-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 +msgid "TM-T82II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 +msgid "TM-T83II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 +msgid "TM-T88V-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 +msgid "TM-U220-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 +msgid "TM-m10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 +msgid "TM-m30" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 +msgid "TM-P20 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 +msgid "TM-P60II (Receipt: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 +msgid "TM-P60II (Peeler: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 +msgid "TM-P80 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 +msgid "" +"To work with Odoo, some models that can be used without an :doc:`IoT box " +"<../../../productivity/iot/config/connect>` may require :doc:`the HTTPS " +"protocol <https>` to establish a secure connection between the browser and " +"the printer. However, trying to reach the printer's IP address using HTTPS " +"leads to a warning page on most web browsers. In that case, you can " +"temporarily :ref:`force the connection <epos_ssc/instructions>`, which " +"allows you to reach the page in HTTPS and use the ePOS printer in Odoo as " +"long as the browser window stays open." +msgstr "" +"หากต้องการทำงานร่วมกับ Odoo บางรุ่นที่สามารถใช้งานได้โดยไม่ต้องใช้ :doc:`IoT" +" box <../../../productivity/iot/config/connect>` อาจต้องใช้ :doc:`โปรโตคอล " +"HTTPS ` เพื่อสร้าง การเชื่อมต่อที่ปลอดภัยระหว่างเบราว์เซอร์และเครื่องพิมพ์ " +"อย่างไรก็ตาม การพยายามเข้าถึงที่อยู่ IP ของเครื่องพิมพ์โดยใช้ HTTPS " +"จะนำไปสู่หน้าคำเตือนบนเว็บเบราว์เซอร์ส่วนใหญ่ ในกรณีนั้น คุณสามารถ " +":ref:`บังคับการเชื่อมต่อ <epos_ssc/instructions>` ชั่วคราว " +"ซึ่งช่วยให้คุณเข้าถึงเพจใน HTTPS และใช้เครื่องพิมพ์ ePOS ใน Odoo " +"หากหน้าต่างเบราว์เซอร์ยังคงเปิดอยู่" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 +msgid "" +"The connection is lost after closing the browser window. Therefore, this " +"method should only be used as a **workaround** or as a pre-requisite for the" +" :ref:`following instructions <epos_ssc/instructions>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 +msgid "Generate, export, and import self-signed certificates" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 +msgid "" +"For a long-term solution, you must generate a **self-signed certificate**. " +"Then, export and import it into your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 +msgid "" +"**Generating** an SSL certificate should only be done **once**. If you " +"create another certificate, devices using the previous one will lose HTTPS " +"access." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +msgid "Windows 10 & Linux OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191 +msgid "Generate a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 +msgid "" +"Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force " +"the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to " +"[IP address] (unsafe)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +msgid "Warning page on Google Chrome, Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203 +msgid "" +"Then, sign in using your printer credentials to access the ePOS printer " +"settings. To sign in, enter `epson` in the :guilabel:`ID` field and your " +"printer serial number in the :guilabel:`Password` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207 +msgid "" +"Click :guilabel:`Certificate List` in the :guilabel:`Authentication` " +"section, and click :guilabel:`create` to generate a new **Self-Signed " +"Certificate**. The :guilabel:`Common Name` should be automatically filled " +"out. If not, fill it in with the printer IP address number. Select the years" +" the certificate will be valid in the :guilabel:`Validity Period` field, " +"click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the " +"printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +msgid "" +"The self-signed certificate is generated. Reload the page and click " +":guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure " +"**Selfsigned Certificate** is correctly selected in the :guilabel:`Server " +"Certificate` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 +msgid "Export a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 +msgid "" +"The export process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser. Start by accessing your ePOS printer settings on your web " +"browser by navigating to its IP address (e.g., `https://192.168.1.25`). " +"Then, force the connection as explained in the **Generate a self-signed " +"certificate tab**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225 +msgid "If you are using **Google Chrome**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 +msgid "" +"click :guilabel:`Not secure` next to the search bar, and " +":guilabel:`Certificate is not valid`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 +msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234 +msgid "" +"add `.crt` at the end of the file name to ensure it has the correct " +"extension;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235 +msgid "" +"select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom " +"of the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 +msgid "save, and the certificate is exported." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 +msgid "" +"Make sure that the certificate ends with the extension `.crt`. Otherwise, " +"some browsers might not see the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243 +msgid "If you are using **Mozilla Firefox**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 +msgid "click the **lock-shaped** icon on the left of the address bar;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246 +msgid "" +"go to :menuselection:`Connection not secure --> More information --> " +"Security tab --> View certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox browser" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252 +msgid "scroll down to the :guilabel:`Miscellaneous` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253 +msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +msgid "Import a self-signed certificate" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 +msgid "" +"The import process is heavily dependent on the :abbr:`OS (Operating System)`" +" and the browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 +msgid "Windows 10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 +msgid "" +"Windows 10 manages certificates, which means that self-signed certificates " +"must be imported from the certification file rather than the browser. To do " +"so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +msgid "" +"open the Windows File Explorer and locate the downloaded certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 +msgid "" +"right-click on the certification file and click :guilabel:`Install " +"Certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +msgid "" +"select where to install the certificate and for whom - either for the " +":guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, " +"click :guilabel:`Next`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +msgid "" +"on the `Certificate Store` screen, tick :guilabel:`Place all certificates in" +" the following store`, click :guilabel:`Browse...`, and select " +":guilabel:`Trusted Root Certification Authorities`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 +msgid "click :guilabel:`Finish`, accept the pop-up security window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 +msgid "restart the computer to make sure that the changes are applied." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 +msgid "Linux" +msgstr "Linux" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +msgid "open Chrome;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 +msgid "" +"go to :menuselection:`Settings --> Privacy and security --> Security --> " +"Manage certificates`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 +msgid "" +"go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select " +"the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +msgid "accept all warnings;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 +msgid "click :guilabel:`ok`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +msgid "restart your browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 +msgid "open Firefox;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 +msgid "" +"go to :menuselection:`Settings --> Privacy & Security --> Security --> View " +"Certificates... --> Import`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 +msgid "select the exported certification file;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +msgid "tick the checkboxes and validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +msgid "Mac OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +msgid "" +"On Mac OS, you can secure the connection for all browsers by following these" +" steps:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +msgid "" +"open Safari and navigate to your printer's IP address. Doing so leads to a " +"warning page;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 +msgid "" +"on the warning page, go to :menuselection:`Show Details --> visit this " +"website --> Visit Website`, validate;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 +msgid "reboot the printer so you can use it with any other browser." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +msgid "" +"To generate and export an SSL certificate and send it to IOS devices, open " +"**Google Chrome** or **Mozilla Firefox**. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Warning page about the connection privacy on Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection to the printer not secure button in Google Chrome" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240 +msgid "" +"Make sure that the certificate ends with the extension `.crt`. Otherwise, " +"some browsers might not find the file during the import process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:0 +msgid "Connection is not secure button in Mozilla Firefox" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 +msgid "Android OS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 +msgid "" +"To import an SSL certificate into an Android device, first create and export" +" it from a computer. Next, transfer the `.crt` file to the device using " +"email, Bluetooth, or USB. Once the file is on the device," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262 +msgid "open the settings and search for `certificate`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263 +msgid "click :guilabel:`Certificate AC` (Install from device storage);" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264 +msgid "select the certificate file to install it on the device." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 +msgid "" +"The specific steps for installing a certificate may vary depending on the " +"version of Android and the device manufacturer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270 +msgid "iOS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 +msgid "" +"To import an SSL certificate into an iOS device, first create and export it " +"from a computer. Then, transfer the `.crt` file to the device using email, " +"Bluetooth, or any file-sharing service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276 +msgid "" +"Downloading this file triggers a warning pop-up window. Click " +":guilabel:`Allow` to download the configuration profile, and close the " +"second pop-up window. Then," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279 +msgid "go to the **Settings App** on the iOS device;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 +msgid "click :guilabel:`Profile Downloaded` under the user's details box;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281 +msgid "locate the downloaded `.crt` file and select it;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 +msgid "click :guilabel:`Install` on the top right of the screen;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283 +msgid "if a passcode is set on the device, enter the passcode;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284 +msgid "" +"click :guilabel:`Install` on the top right of the certificate warning screen" +" and the pop-up window;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286 +msgid "click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290 +msgid "" +"The certificate is installed, but it still needs to be authenticated. To do " +"so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292 +msgid "" +"go to :menuselection:`Settings --> General --> About > Certificate Trust " +"Settings`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293 +msgid "enable the installed certificate using the **slide button**;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294 +msgid "click :guilabel:`Continue` on the pop-up window." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297 +msgid "" +"If you need to export SSL certificates from an operating system or web " +"browser that has not been mentioned, search for `export SSL certificate` + " +"`the name of your browser or operating system` in your preferred search " +"engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 +msgid "" +"Similarly, to import SSL certificates from an unmentioned OS or browser, " +"search for `import SSL certificate root authority` + `the name of your " +"browser or operating system` in your preferred search engine." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 +msgid "Check if the certificate was imported correctly" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 +msgid "" +"To confirm your printer's connection is secure, connect to its IP address " +"using HTTPS. For example, navigate to `https://192.168.1.25` in your " +"browser. If the SSL certificate has been applied correctly, you should no " +"longer see a warning page, and the address bar should display a padlock " +"icon, indicating that the connection is secure." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:3 +msgid "Secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 +msgid "" +"If **Direct Devices** is enabled in a Point of Sale settings (for example, " +"if you use an ePos printer), HTTP becomes the default protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 +msgid "Force your Point of Sale to use a secure connection (HTTPS)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:11 +msgid "" +"Add a new **key** in the **System Parameters** to force your Point of Sale " +"to use a secure connection with the HTTPS protocol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:14 +msgid "" +"To do so, activate the :ref:`developer mode <developer-mode>`, go to " +":menuselection:`Settings --> Technical --> Parameters --> System " +"Parameters`, then create a new parameter, add the following values and click" +" on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:18 +msgid "**Key**: `point_of_sale.enforce_https`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:19 +msgid "**Value**: `True`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 +msgid ":doc:`epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:3 +msgid "Multi-employee management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:5 +msgid "" +"Odoo Point of Sale allows you to manage access to a specific POS by enabling" +" the **Multi Employees per Session** feature. When activated, :ref:`you can " +"select which users can log into the POS <employee_login/use>` and :ref:`keep" +" track of the employees involved in each order <employee_login/analytics>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:15 +msgid "" +":ref:`Access the POS settings <configuration/settings>` and select your POS," +" or click the vertical ellipsis button (:guilabel:`⋮`) on a POS card and " +"click :guilabel:`Edit`. Then, enable :guilabel:`Multi Employees per " +"Session`, and add the allowed employees in the :guilabel:`Allowed Employees`" +" field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "setting to enable multiple cashiers in POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:26 +msgid "Practical application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:28 +msgid "" +"Once the feature is activated, cashiers can log in :ref:`by scanning their " +"badge <employee_login/badge>` or selecting their name from the list of " +"allowed employees to :ref:`open the session <pos/session-start>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "window to open a session when the multiple cashiers feature is enabled" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:35 +msgid "" +"To switch to another user :ref:`from an open session <pos/session-start>`, " +"click the employee name at the top-right of the screen and select the " +"employee to swap with from the list." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "button to switch from one cashier to another." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:41 +msgid "" +"You can also require your employees to enter a pin code every time they log " +"into a POS to prevent them from logging in as someone else. To define the " +"code, go to the **Employees** app, open the employee form, and click the " +":guilabel:`HR settings` tab. Then, enter a pin code of your choice in the " +":guilabel:`PIN Code` field of the :guilabel:`Attendance/Point of Sale` " +"category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst-1 +msgid "setting on the employee form to assign a badge ID and a PIN code." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:52 +msgid "Log in using badges" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:54 +msgid "" +"For your employees to be able to log in by scanning their badge, they must " +"have a badge ID assigned. To do so, go to the **Employees** app, open the " +"employee form, and click the :guilabel:`HR settings` tab. Then, enter the " +"badge ID of your choice in the :guilabel:`Badge ID` field of the " +":guilabel:`Attendance/Point of Sale` category or click :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:59 +msgid "" +"To switch to another user, lock the session by clicking the lock-shaped icon" +" (:guilabel:`🔓`) at the top-right of the screen and scan your badge." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:65 +msgid "Analytics" +msgstr "การวิเคราะห์" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:67 +msgid "" +"Once you close and post the POS session, access the comprehensive report to " +"review all session activities, including who initiated the session and who " +"handled specific orders. To access the session's report, click the vertical " +"ellipsis button (:guilabel:`⋮`) on the POS card and select " +":guilabel:`Sessions` from the :guilabel:`View` section. Then, select a " +"specific session for more detailed information, and click the " +":guilabel:`Orders` button to view a list of all orders placed during that " +"session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/employee_login.rst:74 +msgid "" +"To get an overview of all orders, regardless of the session, click the " +"vertical ellipsis button (:guilabel:`⋮`) on the POS card and select " +":guilabel:`Orders` from the :guilabel:`View` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:5 +msgid "Payment methods" +msgstr "วิธีการชำระเงิน" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:7 +msgid "" +"To add a payment method, you first need to create it. Go to " +":menuselection:`Point of Sale --> Configuration --> Payment Methods --> " +"New`, and set a name. Check :guilabel:`Identify Customer` to allow this " +"payment method *exclusively* for registered customers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:11 +msgid "" +"Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this " +"payment method for cash payments, or :guilabel:`Bank` to use it for card " +"payments." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst-1 +msgid "Creating a new payment method for a POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:18 +msgid "" +"Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a" +" Payment Terminal` field in which you can add your :doc:`payment terminal's " +"information <payment_methods/terminals>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:23 +msgid ":doc:`payment_methods/terminals`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 +msgid "" +"Once the payment method is created, you can select it in your POS settings. " +"To do so, go to the :ref:`POS' settings <configuration/settings>`, click " +":guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` " +"section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:5 +msgid "Payment terminals" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:7 +msgid "" +"Connecting and integrating a payment terminal with your POS system allows " +"you to accept multiple payment options, including credit and debit cards, " +"making the payment process more efficient." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 +msgid "" +"Go to the :doc:`application settings <../configuration>`, scroll down to the" +" :guilabel:`Payment Terminals` section, and tick your terminal's checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst-1 +msgid "checkbox in the settings to enable a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:19 +msgid "Then, follow the corresponding documentation to configure your device:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:21 +msgid ":doc:`Adyen configuration <terminals/adyen>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:22 +msgid ":doc:`Ingenico configuration <terminals/ingenico>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:23 +msgid ":doc:`SIX configuration <terminals/six>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:24 +msgid ":doc:`Stripe configuration <terminals/stripe>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:25 +msgid ":doc:`Vantiv configuration <terminals/vantiv>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:26 +msgid ":doc:`Worldline configuration <terminals/worldline>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 +msgid "" +"Once the terminal is configured, you can :doc:`create the corresponding " +"payment method and add it to the POS <../payment_methods>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3 +msgid "Adyen" +msgstr "Adyen" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:5 +msgid "" +"Connecting an **Adyen payment terminal** allows you to offer a fluid payment" +" flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 +msgid "" +"Adyen works only with businesses processing **more** than **10 million " +"annually** or invoicing a **minimum** of **1,000** transactions **per " +"month**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 +msgid "" +"Start by creating your Adyen account on `Adyen's website " +"<https://www.adyen.com/>`_. Then, board your terminal following the steps " +"described on your terminal's screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 +msgid "" +"`Adyen Docs - Payment terminal quickstart guides " +"<https://docs.adyen.com/point-of-sale/user-manuals>`_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:23 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 +msgid "Configure the payment method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 +msgid "" +"First, go to :menuselection:`Point of Sale --> Configuration --> Settings " +"--> Payment Terminals`, and enable :guilabel:`Adyen`. Then, go to " +":menuselection:`Configuration --> Payment Methods` and create a new payment " +"method. Select :guilabel:`Adyen` in the :guilabel:`Use a Payment Terminal` " +"field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 +msgid "" +"The selected journal **must** be a bank journal for the :guilabel:`Use a " +"payment terminal` field to appear." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 +msgid "" +"Finally, fill the mandatory fields with an :guilabel:`Adyen API key`, and an" +" :guilabel:`Adyen Terminal Identifier`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:38 +msgid "Generate an Adyen API key" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 +msgid "" +"The **Adyen API key** is a key used to authenticate your requests. To " +"generate an API key, go to your **Adyen account**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:43 +msgid "" +"Then, go to :menuselection:`Developers --> API credentials`. Create a new " +"credential or click on an existing one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 +msgid "" +"Click on :guilabel:`Generate an API key` and copy-paste that key onto the " +"Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:49 +msgid "" +"`Adyen Docs - API credentials <https://docs.adyen.com/development-" +"resources/api-credentials#generate-api-key>`_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 +msgid "Locate the Adyen terminal identifier" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 +msgid "" +"The **Adyen Terminal Identifier** is your terminal's serial number, which is" +" used to identify the hardware." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 +msgid "" +"To find this number, go to your **Adyen account**. Then, go to " +":menuselection:`Point of Sale --> Terminals`, select the terminal to link, " +"and copy-paste its serial number onto the Odoo mandatory field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:63 +msgid "Set the Event URLs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 +msgid "" +"For Odoo to know when a payment is made, you must set the terminal **Event " +"URLs**. To do so," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 +msgid "log in to `Adyen's website <https://www.adyen.com/>`_;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 +msgid "" +"go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and" +" select the connected terminal;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:70 +msgid "from the terminal settings, click :guilabel:`Integrations`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:71 +msgid "" +"set the :guilabel:`Switch to decrypted mode to edit this setting` field as " +":guilabel:`Decrypted`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:72 +msgid "" +"click the **pencil icon** button and enter your server address, followed by " +"`/pos_adyen/notification` in the :guilabel:`Event URLs` field; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:74 +msgid "" +"click :guilabel:`Save` at the bottom of the screen to save the changes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:77 +msgid "Add a new payment method" +msgstr "เพิ่มวิธีการชำระเงินใหม่" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 +msgid "" +"To add a new **payment method** to a point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, " +"select the POS and go to :menuselection:`Payments --> Payment Methods`, and " +"add your new method for Adyen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:65 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:86 +msgid "Pay with a payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:86 +msgid "" +"When processing a payment, select :guilabel:`Adyen` as the payment method. " +"Check the amount and click on :guilabel:`Send`. Once the payment is " +"successful, the status changes to :guilabel:`Payment Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +msgid "" +"In case of connection issues between Odoo and the payment terminal, force " +"the payment by clicking on :guilabel:`Force Done`, which allows you to " +"validate the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +msgid "" +"This option is only available after receiving an error message informing you" +" that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:95 +msgid "To cancel the payment request, click on :guilabel:`cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3 +msgid "Ingenico" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:5 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 +msgid "" +"Please note that Ingenico is currently only available for customers in the " +"Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15 +msgid "Connect an IoT Box" +msgstr "เชื่อมต่อกล่อง IoT" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 the :doc:`IoT documentation " +"</applications/productivity/iot/config/connect>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 +msgid "Configure the Lane/5000 for Ingenico BENELUX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 +msgid "" +"Click on the F button of the terminal, then go in the :menuselection:`PoS " +"Menu --> Settings` and enter the settings password." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 +msgid "" +"Now, click on connection 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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 +msgid "" +"First, go in the general settings of the POS app, and activate the Ingenico " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:44 +msgid "" +"Go back in :menuselection:`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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 +msgid "" +"If you want to cancel the payment request, click on cancel. You can still " +"retry to send the payment request." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:67 +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 connection between the terminal and Odoo has issues." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 +msgid "" +"This option will only be available if you received an error message telling " +"you the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:76 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:3 +msgid "SIX" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5 +msgid "" +"Connecting a **SIX payment terminal** allows you to offer a fluid payment " +"flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9 +msgid "" +"Even though Worldline has acquired SIX Payment Services and both companies " +"use Yomani payment terminals, the firmware they run is different. Terminals " +"received from Worldline are, therefore, not compatible with this " +"integration." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17 +msgid "Install the POS IoT Six module" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19 +msgid "" +"To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the " +":guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds " +"the necessary driver and interface to your database to detect Six terminals." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24 +msgid "This module replaces the **POS Six** module." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27 +msgid "Connect an IoT box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 +msgid "" +"Connecting a Six payment terminal to Odoo is requires :doc:`using a " +"Raspberry Pi or virtual (for Windows OS only) IoT box " +"</applications/productivity/iot/config/connect>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 +msgid "Configure the terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35 +msgid "" +"Navigate to your IoT Box homepage, where you can find the :guilabel:`Six " +"payment terminal` field once your database server is connected to the IoT " +"box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field " +"with the ID received from Six, and click :guilabel:`Connect`. Your Six " +"terminal ID should appear in the :guilabel:`Current Terminal Id` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Setting the Six terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43 +msgid "" +"Odoo automatically restarts the IoT box when the Six terminal ID is " +"configured. If your Six terminal is online, it will be automatically " +"detected and connected to the database. Check the IoT box homepage under the" +" :guilabel:`Payments` section to confirm the connection." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Confirming the connection to the Six payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55 +msgid "" +"From your database, go to :menuselection:`Point of Sale --> Configuration " +"--> Payment Methods` to create a new payment method specifically for Six. " +"Click :guilabel:`New`, enter a :guilabel:`Name`, set the :guilabel:`Journal`" +" field as :guilabel:`Bank`, the :guilabel:`Use a Payment Terminal` field as " +":guilabel:`SIX IOT`, and select the corresponding device in the " +":guilabel:`Payment Terminal Device` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Creating a new payment method for the SIX payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:67 +msgid "" +"When processing a payment, select :ref:`your Six payment method " +"<six/configure>` in the :guilabel:`Payment Method` section and click " +":guilabel:`Send`. To cancel the payment request, click :guilabel:`Cancel`. " +"Once the payment is successful, the status switches to :guilabel:`Payment " +"Successful`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst-1 +msgid "Paying with Six" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:76 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 +msgid "" +"Once your payment is processed, the type of card used and the transaction ID" +" appear on the payment record." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:78 +msgid "" +"The language used for error messages is the same as the Six terminal. " +"Configure the terminal to change the language or contact Six." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:80 +msgid "By default, the port used by the Six terminal is `7784`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83 +msgid "" +"If there are connection issues between the payment terminal and Odoo, you " +"can still force the payment validation in Odoo using the :guilabel:`Force " +"Done` button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3 +msgid "Stripe" +msgstr "Stripe" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:9 +msgid "" +":doc:`Use Stripe as payment provider. " +"<../../../../finance/payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:17 +msgid "" +"Activate **Stripe** in the settings by going to :menuselection:`Point of " +"Sale --> Configuration --> Settings --> Payment Terminals` and enabling " +":guilabel:`Stripe`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:20 +msgid "Then, create the payment method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, " +"click :guilabel:`Create`, and complete the :guilabel:`Method` field with " +"your payment method's name;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:24 +msgid "" +"Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use" +" a Payment Terminal` field as :guilabel:`Stripe`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:26 +msgid "" +"Enter your payment terminal serial number in the :guilabel:`Stripe Serial " +"Number` field;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:27 +msgid "" +"Click :guilabel:`Don't forget to complete Stripe connect before using this " +"payment method.`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 +msgid "payment method creation form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 +msgid "" +"Click :guilabel:`Identify Customer` to allow this payment method " +"**exclusively** for identified customers. For any unidentified customers to " +"be able to pay with Stripe, leave the :guilabel:`Identify Customer` field " +"unchecked." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:37 +msgid "" +"The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account`" +" can stay empty to use the default accounts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:39 +msgid "" +"Find your payment terminal serial number under the device or on `Stripe's " +"dashboard <https://dashboard.stripe.com>`_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:43 +msgid "Connect Stripe to Odoo" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:45 +msgid "" +"Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a " +"configuration page. Fill in all the information to create your Stripe " +"account and link it with Odoo. Once the forms are completed, the API keys " +"(:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on" +" **Stripe's** website. To do so, click :guilabel:`Get your Secret and " +"Publishable keys`, click the keys to copy them, and paste them into the " +"corresponding fields in Odoo. Your terminal is ready to be configured in a " +"POS." +msgstr "" +"คลิก :guilabel:`เชื่อมต่อ Stripe` " +"ซึ่งจะนำคุณไปยังหน้าการกำหนดค่าโดยอัตโนมัติ กรอกข้อมูลทั้งหมดเพื่อสร้างบัญชี" +" Stripe ของคุณและเชื่อมโยงกับ Odoo เมื่อกรอกแบบฟอร์มเสร็จแล้ว คีย์ API " +"(:guilabel:`รหัสที่เผยแพร่ได้` และ :guilabel:`รหัสลับ`) " +"สามารถเรียกค้นได้จากเว็บไซต์ **Stripe's** โดยคลิก " +":guilabel:`รับรหัสลับและรหัสที่เผยแพร่ได้` " +"คลิกที่รหัสเพื่อคัดลอกและวางลงในฟิลด์ที่เกี่ยวข้องใน Odoo " +"เครื่องเทอร์มินัลของคุณพร้อมที่จะกำหนดค่าใน POS แล้ว" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst-1 +msgid "stripe connection form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:57 +msgid "" +"When you use **Stripe** exclusively in Point of Sale, you only need the " +"**Secret Key** to use your terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:59 +msgid "" +"When you use Stripe as **payment provider**, the :guilabel:`State` can stay " +"set as :guilabel:`Disabled`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:61 +msgid "" +"For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button " +"does not work. To retrieve the API keys manually, log in to your `Stripe " +"dashboard <https://dashboard.stripe.com>`_, type `API` in the search bar, " +"and click :guilabel:`Developers > API`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:67 +msgid "Configure the payment terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:69 +msgid "" +"Swipe right on your payment terminal, click :guilabel:`Settings`, enter the " +"admin PIN code, validate and select your network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:73 +msgid "The device must be connected to a secured WI-FI network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 +msgid "Your Odoo database and payment terminal must share the same network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:75 +msgid "" +"You must enter the admin PIN code to access your payment terminal settings. " +"By default, this code is `07139`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:79 +msgid "Link the payment method to a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 +msgid "" +"To add a **payment method** to your point of sale, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`. Select the " +"POS, scroll down to the :guilabel:`Payments` section, and add your payment " +"method for **Stripe** in the :guilabel:`Payment Methods` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 +msgid "" +"When processing a payment, select :guilabel:`Stripe` as the payment method. " +"Check the amount and click :guilabel:`Send`. Once the payment is successful," +" the status changes to :guilabel:`Payment Successful`. To cancel the payment" +" request, click :guilabel:`cancel`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:97 +msgid "The terminal must have at least 10% battery level to use it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:98 +msgid "The device does not work for payments under €0.50." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:101 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 +msgid "Payment terminal unavailable in your Stripe account" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:106 +msgid "" +"If the payment terminal is unavailable in your Stripe account, you must add " +"it manually:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 +msgid "" +"Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to" +" :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:110 +msgid "" +"Add a location by clicking the :guilabel:`+ New` button or selecting an " +"already created location;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 +msgid "" +"Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill " +"in the required information." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 +msgid "" +"You must provide a **registration code**. To retrieve that code, swipe right" +" on your device, enter the admin PIN code (by default: `07139`), validate, " +"and click :guilabel:`Generate a registration code`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:3 +msgid "Vantiv" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:9 +msgid "" +"Please note MercuryPay only operates with US and Canadian banks, making this" +" procedure only suitable for North American businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:13 +msgid "" +"Vantiv card readers should be purchased exclusively from Vantiv, as certain " +"Vantiv terminals bought on Amazon do not include the correct encryption " +"needed to be used with an Odoo database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 +msgid "Configure the Payment Method" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:22 +msgid "" +"First, go in the general settings of the POS app, and activate the Vantiv " +"setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:28 +msgid "" +"Back in :menuselection:`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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:36 +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 "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:44 +msgid "Pay with a Payment Terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:46 +msgid "" +"In your PoS interface, at the moment of the payment, select your Vantiv " +"payment method and… that’s all." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 +msgid "Worldline" +msgstr "Worldline" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 +msgid "Please note that Worldline is currently only available in the Benelux." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 +msgid "" +"Connecting a Worldline Payment Terminal to Odoo is a feature that requires " +"an IoT Box. For more information on how to connect one to your database, " +"please refer to the :doc:`IoT documentation " +"</applications/productivity/iot/config/connect>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22 +msgid "Configure the protocol" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 2`. Then, click on :menuselection:`Change --> " +"CTEP (as Protocole ECR) --> OK`. Click on **OK** thrice on the subsequent " +"screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). " +"Finally, press **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:31 +msgid "Set the IP address" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33 +msgid "" +"From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> " +"0 --> 9`. Enter the technician password **\"1235789\"** and click on " +":menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> " +"TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK`" +" (*TCP Configuration client* screen)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:38 +msgid "Finally, set up the hostname and port number." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41 +msgid "Hostname" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44 +msgid "" +"To set up the hostname, enter your IoT box's IP address' sequence numbers " +"and press **OK** at each \".\" until you reach the colon symbol." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 +msgid "Then, press **OK** twice." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "Here's an IP address sequence: `10.30.19.4:8069`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:0 +msgid "" +"On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> " +"19 --> OK --> 4 --> OK --> OK`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:53 +msgid "" +"Your IoT box's IP address is available in your IoT Box application's " +"database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:56 +msgid "Port number" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58 +msgid "" +"On the *Port number* screen, enter **9001** (or **9050** for Windows) and " +"click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> " +"OK`. Click on **Stop** three times; the terminal automatically restarts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:65 +msgid "" +"From the Point of Sale application, go to :menuselection:`Configuration --> " +"Settings --> Payment terminals` and activate the *Worldline* payment " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:71 +msgid "" +"Then, go to :menuselection:`Configuration --> Payment methods` and create a " +"new payment method for *Worldline*. Select the payment terminal *Worldline* " +"and your payment terminal device on your *Payment Method form*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:78 +msgid "Technician password: `1235789`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:79 +msgid "" +"To reach Wordline's technical assistance, call `02 727 61 11` and choose " +"\"merchant\". Your call is automatically transferred to the desired service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 +msgid "" +"Configure the cashier terminal if you have both a customer and a cashier " +"terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:82 +msgid "" +"To avoid blocking the terminal, check the initial configuration beforehand." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83 +msgid "" +"Set a fixed IP to your IoT Box’s router to prevent losing the connexion." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 +msgid "" +"When processing a payment, select *Worldline* as payment method. Check the " +"amount and click on *Send*. Once the payment is successful, the status " +"changes to *Payment Successful*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 +msgid "" +"In case of connexion issues between Odoo and the payment terminal, force the" +" payment by clicking on *Force Done*, which allows you to validate the " +"order. This option is only available after receiving an error message " +"informing you that the connection failed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 +msgid "To cancel the payment request, click on **cancel**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing.rst:5 +msgid "Pricing features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:3 +msgid "Cash rounding" +msgstr "การปัดเศษเงินสด" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:5 +msgid "" +"**Cash rounding** is required when the lowest physical denomination of " +"currency, or the smallest coin, is higher than the minimum unit of account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:9 +msgid "" +"For example, some countries require their companies to round up or down the " +"total amount of an invoice to the nearest five cents, when the payment is " +"made in cash." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:13 +msgid "" +"Each point of sale in Odoo can be configured to apply cash rounding to the " +"totals of its bills or receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:19 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Settings` and " +"enable *Cash Rounding*, then click on *Save*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:25 +msgid "" +"Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, " +"open the point of sale you want to configure, and enable the *Cash Rounding*" +" option." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:29 +msgid "" +"To define the **Rounding Method**, open the drop-down list and click on " +"*Create and Edit...*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:32 +msgid "" +"Define here your *Rounding Precision*, *Profit Account*, and *Loss Account*," +" then save both the Rounding Method and your Point of Sale settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:39 +msgid "" +"All total amounts of this point of sale now add a line to apply the rounding" +" according to your settings." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:46 +msgid "" +"Odoo Point of Sale only supports the :guilabel:`Add a rounding line` " +"rounding strategy." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:3 +msgid "Discount tags (barcode scanner)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:5 +msgid "" +"If you want to sell your products with a discount, for a product getting " +"close to its expiration date for example, you can use discount tags. They " +"allow you to scan discount barcodes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:10 +msgid "To use discount tags you will need to use a barcode scanner." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:13 +msgid "Barcode Nomenclature" +msgstr "การตั้งชื่อบาร์โค้ด" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:15 +msgid "To use discounts tags, we need to learn about barcode nomenclature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:17 +msgid "" +"Let's say you want to have a discount for the product with the following " +"barcode:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:23 +msgid "" +"You can find the *Default Nomenclature* under the settings of your PoS " +"interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:32 +msgid "" +"Let's say you want 50% discount on a product you have to start your barcode " +"with 22 (for the discount barcode nomenclature) and then 50 (for the %) " +"before adding the product barcode. In our example, the barcode would be:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:41 +msgid "Scan the products & tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:43 +msgid "You first have to scan the desired product (in our case, a lemon)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discount_tags.rst:48 +msgid "" +"And then scan the discount tag. The discount will be applied and you can " +"finish the transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:3 +msgid "Discounts" +msgstr "ลดราคา" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:5 +msgid "" +"By offering discounts, you can entice your customers and drastically " +"increase your revenue. It is vital to offer discounts, whether they are " +"time-limited, seasonal or manually given." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:9 +msgid "" +"To manage discounts, Odoo has powerful features that help set up a pricing " +"strategy tailored to every business." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:13 +msgid "Apply manual discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:15 +msgid "" +"If you seldom use discounts, applying manual ones might be the easiest " +"solution for your Point of Sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:18 +msgid "" +"You can either apply a discount on the whole order or on specific products " +"inside an order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:22 +msgid "Apply a discount on a product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:24 +msgid "From your PoS session interface, use the *Disc* button." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount button for manual discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:30 +msgid "" +"Then, you can input a discount over the product that is currently selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:34 +msgid "Apply a global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:36 +msgid "" +"To apply a discount on the whole order, go to :menuselection:`Point of Sales" +" --> Configuration --> Point of Sale` and select your PoS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:39 +msgid "" +"Once on your PoS form, select *Global Discounts*, under the *Pricing* " +"category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the feature to enable for global discount" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:45 +msgid "Now, you have a new *Discount* button appearing on your PoS interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the button to use for global discount via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:51 +msgid "Click on it and enter the wanted discount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the discount offered in the payment summary" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:58 +msgid "" +"On this example, there is a global discount of 50% as well as a specific 50%" +" discount on oranges." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:62 +msgid "Apply time-limited discounts" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:64 +msgid "" +"To activate time-limited discounts, you must activate the *Pricelists* " +"feature. To do so, go to :menuselection:`Point of Sales --> Configuration " +"--> Point of Sale` and open your PoS. Then, enable the pricelist feature." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of the pricelist feature" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:73 +msgid "" +"Once activated, you must choose the pricelists you want to make available in" +" the PoS and define a default one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:77 +msgid "Create a pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:79 +msgid "" +"By default, Odoo has a *Public Pricelist* configured. To create more, go to " +":menuselection:`Point of Sale --> Products --> Pricelists`. Then click on " +"create." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:83 +msgid "" +"When creating a pricelist, you can set several criteria to use a specific " +"price: period, min. quantity, etc. You can also decide to apply that " +"pricelist on specific products or on the whole range." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "View of a time-limited pricelist for two products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:92 +msgid "Using a pricelist with the PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:94 +msgid "" +"On the PoS interface, a new button appears. Use it to select a pricelist." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst-1 +msgid "" +"View of the button to use for time-limited discounts via the pos interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/discounts.rst:101 +msgid "" +"Click on it to instantly update the prices with the selected pricelist. " +"Then, you can finalize the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 +msgid "Flexible taxes (fiscal positions)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:5 +msgid "" +"When running a business, you may need to apply different taxes and record " +"transactions on various accounts based on the location and type of business " +"of your customers and providers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:8 +msgid "" +"The **fiscal positions** feature enables you to establish rules that " +"automatically select the right taxes and accounts used for each transaction." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:12 +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:51 +msgid ":doc:`../../../finance/accounting/taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:13 +msgid ":doc:`../../../finance/accounting/taxes`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:18 +msgid "" +"To enable the feature, go to :menuselection:`Point of Sale --> Configuration" +" --> Settings`, scroll down to the :guilabel:`Accounting` section, and " +"enable :guilabel:`Flexible Taxes`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:21 +msgid "" +"Then, set a default fiscal position that should be applied to all sales in " +"the selected POS in the :guilabel:`Default` field. You can also add more " +"fiscal positions to choose from in the :guilabel:`Allowed` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:28 +msgid "" +"According to the :doc:`fiscal localization package " +"<../../../finance/fiscal_localizations>` activated, several fiscal positions" +" are preconfigured and can be set and used in POS. However, you can also " +":ref:`create new fiscal positions <fiscal_positions/mapping>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:33 +msgid "" +"If you do not set a fiscal position, the tax remains as defined in the " +"**customer taxes** field on the product form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:37 +msgid "Use fiscal positions" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:39 +msgid "" +"Open a :ref:`POS session <pos/session-start>` to use one of the allowed " +"fiscal positions. Then, click the :guilabel:`Tax` button next to the **book-" +"shaped** icon and select a fiscal position from the list. Doing so applies " +"the defined rules automatically to all the products subject to the chosen " +"fiscal position's regulations." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:48 +msgid "" +"If a default fiscal position is set, the tax button displays the name of the" +" fiscal position." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:3 +msgid "Loyalty programs" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:5 +msgid "" +"Encourage your customers to continue to shop at your point of sale with a " +"*Loyalty Program*." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:11 +msgid "" +"To activate the *Loyalty Program* feature, go to :menuselection:`Point of " +"Sale --> Configuration --> Point of sale` and select your PoS interface. " +"Under the Pricing features, select *Loyalty Program*" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:19 +msgid "From there you can create and edit your loyalty programs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:24 +msgid "" +"You can decide what type of program you wish to use, if the reward is a " +"discount or a gift, make it specific to some products or cover your whole " +"range. Apply rules so that it is only valid in specific situation and " +"everything in between." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:30 +msgid "Use the loyalty program in your PoS interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:32 +msgid "" +"When a customer is set, you will now see the points they will get for the " +"transaction and they will accumulate until they are spent. They are spent " +"using the button *Rewards* when they have enough points according to the " +"rules defined in the loyalty program." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:40 +msgid "" +"You can see the price is instantly updated to reflect the pricelist. You can" +" finalize the order in your usual way." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:44 +msgid "" +"If you select a customer with a default pricelist, it will be applied. You " +"can of course change it." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:3 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:38 +#: ../../content/applications/sales/subscriptions/products.rst:108 +msgid "Pricelists" +msgstr "รายการราคา" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:5 +msgid "" +"Pricelists allow you to adjust product prices depending on various criteria " +"automatically. For example, you can set POS-specific prices, create " +"temporary discount periods, reward specific customers, or offer discounts " +"when set quantities are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:14 +msgid "" +"Navigate to the :ref:`general POS app settings <configuration/settings>` and" +" ensure :guilabel:`Flexible Pricelists` are enabled under the " +":guilabel:`Pricing` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:17 +msgid "" +":ref:`Multiple prices per product <pricelists/simple>` is the default " +"pricelist option for setting simple fixed price rules per product. Select " +":ref:`Advanced price rules (discounts, formulas) <pricelists/advanced>` to " +"apply price rules to multiple products at once and to compute prices " +"dynamically using percentage discounts or more complex formulas in addition " +"to setting fixed prices." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Enabling pricelists in the general P0S settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:26 +msgid "" +"The selected pricelist type applies to the entire database, including the " +":doc:`Sales <../../sales/products_prices/prices/pricing>` and " +":ref:`eCommerce <ecommerce/pricelists>` apps." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:33 +msgid "Create pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:35 +msgid "" +"Go to :menuselection:`Point of Sale --> Products --> Pricelists` and click " +":guilabel:`New` or select an existing pricelist. The pricelist setup differs" +" depending on the :ref:`selected pricelist option " +"<pricelists/configuration>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:42 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:234 +msgid "Multiple prices per product" +msgstr "หลายราคาต่อสินค้า" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:44 +msgid "" +"When pricelists are configured to use the :guilabel:`Multiple prices per " +"product` option, it is possible to use multiple fixed prices for different " +"products or their variants depending, if necessary, on one or several " +"conditions. To add a new price rule to a pricelist:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:48 +msgid "" +"Click :guilabel:`Add a line`, and select a **product** and its **variant** " +"if needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:49 +msgid "Add the condition(s):" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:51 +msgid "" +"a product quantity to be reached by using the :guilabel:`Min. Quantity` " +"column;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:52 +msgid "" +"a determined period during which the pricelist is applied by using the " +":guilabel:`Start Date` and :guilabel:`End Date` columns." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:55 +msgid "" +"Add the :guilabel:`Price` to be applied when the conditions are met (if " +"any)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Setup form of a multiple prices pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:63 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:312 +msgid "Advanced price rules" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:65 +msgid "" +"When pricelists are configured to use the :guilabel:`Advanced price rules " +"(discounts, formulas)` option, it is possible to use percentage " +"discounts/mark-ups and formulas in addition to using fixed prices. To add a " +"new price rule to a pricelist, click :guilabel:`Add a line`. In the pop-up " +"windows:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:69 +msgid "Select a :guilabel:`Computation` method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:71 +msgid "" +":guilabel:`Fixed Price` to set a new fixed price (similarly to the " +":guilabel:`Multiple prices per product` option)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:73 +msgid "" +":guilabel:`Discount` to compute a percentage discount (e.g., `10.00` %) or " +"mark-up (e.g., `-10.00` %)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:75 +msgid "" +":guilabel:`Formula` to compute the price according to a formula. It is " +"required to define what the calculation is **based on** (:guilabel:`Sales " +"Price`, :guilabel:`Cost`, or :guilabel:`Other Pricelist`). You can then:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:79 +msgid "Apply a percentage :guilabel:`Discount` or mark-up." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:80 +msgid "" +"Add an :guilabel:`Extra Fee` (e.g., $ `5.00`) or subtract a fixed amount " +"(e.g., $ `-5.00`)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:81 +msgid "" +"Define a :doc:`Rounding Method <cash_rounding>` by forcing the price after " +":guilabel:`Discount` to be a multiple of the value set. The :guilabel:`Extra" +" Fee` is applied afterward." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:86 +msgid "" +"To have the final price end with `.99`, set the :guilabel:`Rounding Method` " +"to `1.00` and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:89 +msgid "" +"Specify the minimum (e.g., $ `20.00` ) and maximum (e.g., $ `50.00` ) profit" +" :guilabel:`Margins` for computations based on :guilabel:`Cost`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:92 +msgid "Select on which product(s) the price rule should be **applied**:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:94 +msgid ":guilabel:`All Products`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:95 +msgid "a :guilabel:`Product Category`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:96 +msgid "a :guilabel:`Product`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:97 +msgid "a :guilabel:`Product Variant`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:99 +msgid "" +"Add conditions, such as a specific quantity to reach for the price to change" +" by using the :guilabel:`Min. Quantity` field or a specific period during " +"which the pricelist should be applied by using the :guilabel:`Validity` " +"fields." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Setup form to configure an advanced pricelist" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:107 +msgid "Select pricelists" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:109 +msgid "" +"Go to the :ref:`specific POS settings <configuration/settings>` and add all " +"the available pricelists in the :guilabel:`Available` field. Then, set its " +"**default pricelist** in the :guilabel:`Default` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:113 +msgid "" +"When you :ref:`open a POS session <pos/session-start>`, click the " +"**pricelists** button, and select the desired pricelist from the list." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst-1 +msgid "Button to select a pricelist on the POS frontend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:120 +msgid "" +"Multiple pricelists must be selected for the **pricelist button** to be " +"displayed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:121 +msgid "" +"If a pricelist is selected on a POS order while its conditions are **not** " +"met, the price will **not** be adjusted." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:125 +msgid "" +"You can also set a pricelist to be selected automatically once a specific " +":ref:`customer is set <pos/customers>`. To do so, go to the customer form " +"and switch to the preferred pricelist in the :guilabel:`Pricelist` field of " +"the :guilabel:`Sales & Purchase` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:130 +msgid ":doc:`../../sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:131 +msgid "" +":ref:`How to use pricelists in an ecommerce environment " +"<ecommerce/pricelists>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:3 +msgid "Receipts and invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:6 +msgid "Receipts" +msgstr "ใบเสร็จ" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:8 +msgid "" +"Set up receipts by going to :menuselection:`Point of Sale --> Configuration " +"--> Point of Sale`, selecting a POS, and scrolling down to the " +":guilabel:`Bills & Receipts` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:11 +msgid "" +"To **customize** the **header** and **footer**, activate :guilabel:`Header &" +" Footer` and fill in both fields with the information to be printed on the " +"receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:14 +msgid "" +"To **print receipts** automatically once the payment is registered, enable " +"the :guilabel:`Automatic Receipt Printing` setting." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "POS receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:21 +msgid ":doc:`restaurant/bill_printing`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24 +msgid "Reprint a receipt" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 +msgid "" +"From the POS interface, click :guilabel:`Orders`, open the dropdown " +"selection menu next to the search bar, and change the default :guilabel:`All" +" active orders` filter to :guilabel:`Paid`. Then, select the corresponding " +"order and click :guilabel:`Print Receipt`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "Print receipt button from the backend" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:34 +msgid "" +"You can filter the list of orders using the search bar. Type in your " +"reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or " +":guilabel:`Customer`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 +msgid "Invoices" +msgstr "การแจ้งหนี้" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 +msgid "" +"Point of Sale allows you to issue and print invoices for :ref:`registered " +"customers <pos/customers>` upon payment and retrieve all past invoiced " +"orders." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 +msgid "" +"An invoice created in a POS creates an entry into the corresponding " +":ref:`accounting journal <cheat_sheet/journals>`, previously :ref:`set up " +"<receipts_invoices/invoice_configuration>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 +msgid "" +"To define what journals will be used for a specific POS, go to the " +":ref:`POS' settings <configuration/settings>` and scroll down to the " +"accounting section. Then, you can determine the accounting journals used by " +"default for orders and invoices in the :guilabel:`Default Journals` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "accounting section in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:63 +msgid "Invoice a customer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 +msgid "" +"Upon processing a payment, click :guilabel:`Invoice` underneath the " +"customer's name to issue an invoice for that order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:68 +msgid "" +"Select the payment method and click :guilabel:`Validate`. The **invoice** is" +" automatically issued and ready to be downloaded and/or printed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 +msgid "" +"To be able to issue an invoice, a :ref:`customer <pos/customers>` must be " +"selected." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75 +msgid "Retrieve invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 +msgid "To retrieve invoices from the **POS dashboard**," +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 +msgid "" +"access all orders made through your POS by going to :menuselection:`Point of" +" Sale --> Orders --> Orders`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 +msgid "" +"to access an order's invoice, open the **order form** by selecting the " +"order, then click :guilabel:`Invoice`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "invoice smart button from an order form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:88 +msgid "" +"**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in " +"the :guilabel:`Status` column." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 +msgid "" +"You can filter the list of orders to invoiced orders by clicking " +":guilabel:`Filters` and :guilabel:`Invoiced`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:94 +msgid "QR codes to generate invoices" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 +msgid "" +"Customers can also request an invoice by scanning the **QR code** printed on" +" their receipt. Upon scanning, they must fill in a form with their billing " +"information and click :guilabel:`Get my invoice`. On the one hand, doing so " +"generates an invoice available for download. On the other hand, the order " +"status goes from :guilabel:`Paid` or :guilabel:`Posted` to " +":guilabel:`Invoiced` in the Odoo backend." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst-1 +msgid "order status change" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:105 +msgid "" +"To use this feature, you have to enable QR codes on receipts by going to " +":menuselection:`Point of Sale --> Configuration --> Settings`. Then, select " +"the POS in the :guilabel:`Point of Sale` field, scroll down to the " +":guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on " +"ticket`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:3 +msgid "Reporting" +msgstr "การรายงาน" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:6 +msgid "View statistics" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:8 +msgid "" +"To access your statistics, go to :menuselection:`Point of Sale --> Reporting" +" --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis " +"(:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/reporting.rst:12 +msgid "" +"These statistics are available in a graph or pivot view that you can filter " +"or group depending on your needs." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:5 +msgid "Restaurant features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:7 +msgid "" +"Managing a restaurant or a bar comes with specific needs. The Point of Sale " +"application provides various features that allow performing all the required" +" tasks in such businesses." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:10 +msgid "Once the POS is set to be used in a restaurant or a bar, you can:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:12 +msgid "" +":doc:`organize your floors and tables to reflect your interior " +"<restaurant/floors_tables>`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:13 +msgid ":ref:`take orders <floors_tables/orders>`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:14 +msgid "" +":doc:`communicate with the kitchen or the bar through the POS " +"<restaurant/kitchen_printing>`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:15 +msgid "" +":doc:`print bills in advance and split them <restaurant/bill_printing>`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:16 +msgid ":doc:`collect tips <restaurant/tips>`; and" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:17 +msgid "" +":doc:`set different taxes for takeaway food <pricing/fiscal_position>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:22 +msgid "" +"To enable the restaurant and bar-specific features, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, select the " +"POS, and activate :guilabel:`Is a Bar/Restaurant`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst:25 +msgid "" +"These features are displayed in the :guilabel:`Restaurant & Bar` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant.rst-1 +msgid "restaurant and bar-specific features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:3 +msgid "Bills" +msgstr "ใบเรียกเก็บเงิน" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:5 +msgid "" +"Typical practices in restaurants or bars are to request the bill before " +"proceeding to payment or splitting it based on the items ordered. Odoo POS " +"provides two features to perform these tasks seamlessly: **Bill Printing** " +"and **Bill Splitting**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:12 +msgid "" +"To activate the features, go to :menuselection:`Point of Sale --> " +"Configuration --> Settings`, select the POS, and activate :guilabel:`Early " +"Receipt Printing` and :guilabel:`Allow Bill Splitting` in the " +":guilabel:`Restaurant & Bar` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst-1 +msgid "" +"activate the bill printing and bill splitting features in the POS settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:21 +msgid "Bill printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:23 +msgid "" +"From an open session, click :menuselection:`Bill --> Print` at any moment to" +" generate and print a bill." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:27 +msgid "" +"The printed bill is **not** final and will be updated to reflect any changes" +" to the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:30 +msgid "Bill splitting" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:32 +msgid "" +"From an open session, click :guilabel:`Split` to select the items to " +"regroup. Once everything is selected, click :guilabel:`Payment` and proceed " +"to checkout for these items. Repeat for each guest." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:36 +msgid "" +"Once you return to the table, the selected items are no longer on order, as " +"they have been paid for." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:38 +msgid "The feature is available as soon as at least two items are ordered." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:41 +msgid ":doc:`floors_tables`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:3 +msgid "Floors and tables management" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:6 +msgid "Add a floor" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:8 +msgid "" +"Once your *Point of Sale* has been configured, select *Table Management* " +"under :menuselection:`Point of Sale --> Configuration --> Point of Sale`. " +"Then, click on *Floors* to create and name your floor and tables." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the table management feature. Way to manage and create floors for a " +"pos" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"Backend view of a restaurant floor. Table name and number of sits for each " +"table" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:21 +msgid "Don’t forget to link your floor to your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:24 +msgid "Add tables" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:26 +msgid "" +"To add tables, you can also open your PoS interface to see your floor(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the floors menu to manage several floors at the same time" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:33 +msgid "" +"Then, click on *Edit Mode* (pencil icon on the upper right corner) to be " +"allowed to create, move, modify tables, etc." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the floor management. Add tables, the number of sits, their name and" +" their shape" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:41 +msgid "" +"To make your table easier to be found, you can rename them, change their " +"shape, size or even color. It is also possible to add the maximum number of " +"sits the table can have." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:48 +msgid "Register your table(s) orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:50 +msgid "" +"To register an order, click on the respective table. By doing so, you are " +"taken to your main interface." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the pos interface to register orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:58 +msgid "Transfer customer(s)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:60 +msgid "" +"If your customers want to move to another table after they already ordered, " +"use the transfer button. This way, the order is also moved to the new table." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:64 +msgid "To do so, select the table your customer is currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the restaurant tables, one having a pending order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:70 +msgid "" +"Now, click on the transfer button and select the table to which you are " +"transferring your customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "" +"View of the pos interface and transfer button. How to transfer customers from one table\n" +"to another" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:79 +msgid "Register an additional order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:81 +msgid "" +"When registering an order, use the + button to simultaneously proceed to " +"another one." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:84 +msgid "" +"Then, you can shift between your orders and process the payment when needed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst-1 +msgid "View of the - button, allowing employees to close/remove an order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:92 +msgid "The - button allows you to remove the order you are currently on." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:3 +msgid "Orders printing" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:5 +msgid "" +"Integrating printers in a restaurant or bar's workflow can enhance " +"communication and collaboration between the front-of-house and back-of-house" +" teams, leading to a more streamlined and efficient service." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:15 +msgid "Enable and create printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:17 +msgid "" +"To enable sending orders to a kitchen or bar printer, go to " +":menuselection:`Point of Sale --> Configuration --> Settings`, scroll down " +"to the :guilabel:`Restaurant & Bar` section, and enable :guilabel:`Kitchen " +"Printers`. Type in a name for the printer in the :guilabel:`Printers` field " +"and click :guilabel:`Create and edit...` to open a setup form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:22 +msgid "" +"To get a list of all the printers already created or to modify an already " +"created printer, click :guilabel:`--> Printers` and select the desired " +"printer to open the setup form." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "settings to enable the kitchen printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:32 +msgid "Setup form" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:34 +msgid "" +"From the :ref:`setup form <kitchen_printing/enable>`, select the " +":guilabel:`Printer Type` according to your installation:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:37 +msgid "" +"If your printer is connected to an IoT box, select :guilabel:`Use a printer " +"connected to the IoT Box` and select the device in the :guilabel:`IoT " +"Device` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:39 +msgid "" +"If you use an Epson printer that does not need an IoT box, select " +":guilabel:`Use an Epson printer` and enter the printer's IP address in the " +":guilabel:`Epson Printer IP Address` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:43 +msgid ":doc:`../../../productivity/iot/config/connect`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 +msgid ":doc:`../../../productivity/iot/devices/printer`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:45 +msgid ":doc:`../configuration/epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:47 +msgid "" +"Set your printer to print specific products based on their POS category. To " +"do so, click :guilabel:`Add a line` in the :guilabel:`Printed Product " +"Categories` field. If you leave this field empty, all products are sent to " +"the printer regardless of their POS category." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "setup form to configure a kitchen printer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:56 +msgid "Print orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:58 +msgid "" +"From an open session, start taking an order and click :guilabel:`Order` to " +"send it to the bar or the kitchen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst-1 +msgid "order button from the POS UI to send orders to a kitchen or a bar" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:66 +msgid "" +"When products can be printed, they appear in green in the cart, and the " +"order button turns green." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:3 +msgid "Tips" +msgstr "เคล็ดลับ" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:5 +msgid "" +"Tipping is customary in multiple countries. Point of Sale allows tipping in " +":ref:`shops <pos/sell>`, :doc:`bars <../restaurant>`, or :doc:`restaurants " +"<../restaurant>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:13 +msgid "" +"To allow tipping in your POS, activate the :guilabel:`Tips` feature in " +":menuselection:`Point of Sale --> Configuration --> Settings`. At the top of" +" the page, select the POS in which you wish to allow **tipping**, scroll " +"down to the :guilabel:`Payment` section and check :guilabel:`Tips`. Once " +"enabled, add a :guilabel:`Tip Product` in the corresponding field, and save." +" The designated product will be used as a reference on customers' receipts." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "enable tips in a POS" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:25 +msgid "Tip products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:27 +msgid "" +"**Tip products** can be created on the spot. To do so, enter a product's " +"name in the :ref:`Tip Product <configuration>` field and click " +":guilabel:`Create` or press **enter**. The product is automatically " +"configured to be used as a tip at the payment screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:31 +msgid "" +"However, if you wish to be able to select the tip product in a POS session, " +"you must activate the **Available in POS** setting. To do so, click " +":guilabel:`Create and edit...` to open the product configuration form. Then," +" go to the :guilabel:`Sales` tab, tick the :guilabel:`Available in POS` " +"checkbox, and click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:37 +msgid "" +"When you create a product to use as a tip, leave the **product type** as " +":guilabel:`Consumable` to avoid unnecessary inventory movements." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:39 +msgid "" +"You can only select one tip product per POS, but you can choose a different " +"one for each." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:42 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:72 +msgid "Tip using an Adyen terminal" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:44 +msgid "" +"If you use an :doc:`Adyen <../payment_methods/terminals/adyen>` payment " +"terminal and wish to enable **tips** using the terminal, check " +":guilabel:`Add tip through payment terminal (Adyen)` below the :ref:`tip " +"settings <configuration>`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:49 +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:79 +msgid "Tip after payment" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:51 +msgid "" +"If you use a POS system in a bar or a restaurant, you can enable " +":guilabel:`Add tip after payment (North America specific)`. Doing so " +"generates a bill to print and complete manually by the customer and the " +"waiter. That bill indicates the tip value the customer chooses to give after" +" the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:56 +msgid "" +"To use this feature, the selected payment method must have a bank journal " +"attributed." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:59 +msgid "Add tips" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:61 +msgid "" +"To add tips to an order, :ref:`access the payment screen <pos/sell>` and " +"click :guilabel:`♥ Tip`. Then, enter the tipping amount, click " +":guilabel:`Confirm` to validate, and process the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "tip popup window" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:67 +msgid "" +"Alternatively, you can select the :ref:`tip product <tip-product>` on the " +"POS interface to add it to the cart. When selected, the product is " +"automatically set as a tip, and its default value equals its **Sales " +"Price**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:74 +msgid "" +"During checkout, select **Adyen** as the payment terminal, and send the " +"payment request to the device by clicking :guilabel:`Send`. The customers " +"are asked to enter the desired tipping amount on the terminal's screen " +"before proceeding to the payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:81 +msgid "" +"At checkout, select a card payment method and click :guilabel:`Close Tab`. " +"Doing so generates a bill to complete by the customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "tipping bill after payment to complete by customers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:87 +msgid "" +"On the following screen, click the percentage (:guilabel:`15%`, " +":guilabel:`20%`, :guilabel:`25%`), :guilabel:`No Tip`, or enter the tipping " +"amount the customer chose to give. Then, click :guilabel:`Settle` to move to" +" the following order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 +msgid "screen to select a tip amount to collect after payment" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop.rst:5 +msgid "Shop features" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:3 +msgid "Barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:5 +msgid "" +"Using a barcode scanner to process point-of-sale orders improves your " +"efficiency in providing quicker customer service. Barcode scanners can be " +"used both to scan products or to log employees into a POS session." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:12 +msgid "" +"To use a barcode scanner, you must enable the feature in the Inventory app. " +"Go to :menuselection:`Inventory --> Configuration --> Settings`, in the " +":guilabel:`Barcode` section, tick :guilabel:`Barcode Scanner` and save." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst-1 +msgid "barcode setting in the Inventory application" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:21 +msgid "" +":doc:`Set up a barcode scanner " +"</applications/inventory_and_mrp/barcode/setup/hardware>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:22 +msgid "" +":doc:`Activate barcode scanners " +"</applications/inventory_and_mrp/barcode/setup/software>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:24 +msgid "" +"Once enabled in **Inventory**, you can use the barcode feature in **Point of" +" Sale** with products that have a barcode number assigned." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:28 +msgid "Assign barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:31 +msgid "To your products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:33 +msgid "" +"To use this feature in POS, your products must have barcodes assigned. To do" +" so, go to :menuselection:`Point of Sale --> Products --> Products` and open" +" a **product form**. Add a barcode number in the :guilabel:`Barcode` field " +"in the :guilabel:`General Information` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:38 +msgid "To your employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:40 +msgid "" +"To add an identification number to an employee, go to the **Employees** app " +"and open an **employee form**. Choose an identification number for your " +"employee and fill in the :guilabel:`PIN Code` field in the :guilabel:`HR " +"Settings` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:45 +msgid "Use barcodes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:48 +msgid "Scan products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:50 +msgid "" +"Scan a product's barcode using a barcode scanner. Doing so adds it directly " +"to the cart. To change the quantity, scan a product as many times as needed," +" or click :guilabel:`Qty` and enter the number of products using the keypad." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:54 +msgid "" +"You can also enter the barcode number manually in the search bar to look for" +" the product. Then, click it to add it to the cart." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:58 +msgid "Log employees" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/barcode.rst:60 +msgid "" +"You can also use a barcode scanner to log your employees. To do so, " +":ref:`restrict access <employee_login/configuration>` to the POS and " +":ref:`use barcodes to log your employees in <employee_login/badge>` your " +"POS." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 +msgid "Sales orders" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:5 +msgid "" +"When working in retail, you might need to order products directly from your " +"Point of sale. Fortunately, Odoo Point of Sale is fully integrated with Odoo" +" Sales, meaning that you can create a sales order and pay for it directly " +"from your point of sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:10 +msgid "Select a sales order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:12 +msgid "" +"From the **Point of Sale** application, open a new session. Then, click on " +":guilabel:`Quotations/Orders` to get the complete list of quotations and " +"sales orders created on the sales application." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "Quotations and sales order button on the Point of Sale interface" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:21 +msgid "" +"To ease finding the right sales order, you can filter that list on the " +"**customer** or on the **order reference**. You can also set the customer " +"before clicking on :guilabel:`Quotations/Orders` to reduce the list to one " +"particular customer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:26 +msgid "Apply a down payment or settle the order" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:28 +msgid "From the list of sales order, select one to make a payment." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst-1 +msgid "list view of sales orders and quotations" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:34 +msgid "You can either:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:36 +msgid "" +"Settle the order **partially**: after clicking on :guilabel:`Apply a down " +"payment`, enter the percentage of down payment you want the customer to pay." +" Then, click on :guilabel:`ok` and proceed with the order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:39 +msgid "" +"Settle the order **completely**: click on :guilabel:`Settle the order` to " +"pay for the total of the sales order." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:43 +msgid "" +"Once you settle a sales order, the applied down payment is automatically " +"deducted from the total amount." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:47 +msgid ":doc:`/applications/sales/sales/invoicing/down_payment`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:3 +msgid "Serial numbers and lots" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:5 +msgid "" +"Working with **serial numbers** and **lots** allows tracking your products' " +"movements. When products are tracked, the system identifies their location " +"based on their last movement." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:8 +msgid "" +"To enable traceability, go to :menuselection:`Point of Sale --> Products -->" +" Products`. Then, select a product and check the :guilabel:`Tracking By " +"Unique Serial Number` or the :guilabel:`Tracking By Lots` box in the " +":guilabel:`Inventory` tab." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Enable traceability settings" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:17 +msgid "Serial numbers and lots importation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:19 +msgid "" +"You can import serial numbers in Point of Sale. To do so, select a **sales " +"order** or a **quotation** containing tracked products. Then, agree to load " +"the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "Pop-up window for serial number import" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:28 +msgid "" +"The imported tracking numbers appear below the tracked products. You can " +"modify them by clicking on the list-view button next to the products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:37 +msgid ":doc:`../shop/sales_order`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:40 +msgid "Serial numbers and lots creation" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:42 +msgid "" +"If a tracked product is available in your POS, adding the product to the " +"cart opens a pop-up window where you can type or scan the product's serial " +"or lot numbers. To add more than one of the same tracked products, click on " +"**enter** to validate and start a new line." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst-1 +msgid "adding new serial and lots numbers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:52 +msgid "" +"Changing a tracked product's quantity using the numpad turns the list-view " +"button red. Click on it to add the missing lot and serial numbers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:54 +msgid "" +":guilabel:`Lot & Serial Number(s)` are :guilabel:`required` on tracked " +"products but not mandatory. Meaning that not attributing some or any does " +"**not** prevent from completing the sale." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:59 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:60 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" +msgstr "" + +#: ../../content/applications/sales/rental.rst:3 +msgid "Rental" +msgstr "เช่า" + +#: ../../content/applications/sales/rental.rst:5 +msgid "" +"The Odoo *Rental* application provides comprehensive solutions to configure " +"and manage rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:7 +msgid "" +"Send quotations, confirm orders, schedule rentals, register products when " +"they are picked up and returned, and invoice customers from this single " +"platform." +msgstr "" + +#: ../../content/applications/sales/rental.rst:11 +msgid "`Odoo Rental: product page <https://www.odoo.com/app/rental>`_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:12 +msgid "`Odoo Tutorials: Rental <https://www.odoo.com/slides/rental-48>`_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:17 +msgid "Dashboard" +msgstr "แดชบอร์ด" + +#: ../../content/applications/sales/rental.rst:19 +msgid "" +"Upon opening the *Rental* application, the :guilabel:`Rental Orders` " +"dashboard is revealed." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Example of the Rental Orders dashboard available in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:25 +msgid "" +"In the default kanban view, all rentals are visible. Each rental card " +"displays the customer name, the price of the rental, the related sales order" +" number, along with the status of the rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:29 +msgid "" +"Rental kanban cards that do **not** display a rental status means those " +"rentals have confirmed quotations, but have not been picked up yet." +msgstr "" + +#: ../../content/applications/sales/rental.rst:32 +msgid "" +"On the left sidebar, the :guilabel:`Rental Status` for each rental can be " +"found. Beneath that, the :guilabel:`Invoice Status` of the rentals is " +"accessible. Clicking any option in the left sidebar filters the displayed " +"rentals on the dashboard." +msgstr "" + +#: ../../content/applications/sales/rental.rst:37 +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:13 +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:10 +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:17 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/applications/sales/rental.rst:39 +msgid "" +"To configure additional rental delay costs, availability of rental items, or" +" minimum time of rental, navigate to :menuselection:`Rental app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "How the Settings page appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:46 +msgid "" +"In the :guilabel:`Rental` section, there are options to configure " +":guilabel:`Default Delay Costs` and :guilabel:`Default Padding Time`. There " +"is also the option to activate :guilabel:`Rental Transfers` and " +":guilabel:`Digital Documents`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:50 +msgid ":guilabel:`Default Delay Costs` are additional costs for late returns." +msgstr "" + +#: ../../content/applications/sales/rental.rst:51 +msgid "" +":guilabel:`Default Padding Time` represents the minimum amount of time " +"between two rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:52 +msgid "" +":guilabel:`Rental Transfers` means stock deliveries and receipts can be used" +" for rental orders." +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "" +":guilabel:`Digital Documents` allows users to upload documents for customers" +" to sign prior to" +msgstr "" + +#: ../../content/applications/sales/rental.rst:54 +msgid "confirming their rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:56 +msgid "" +"In the :guilabel:`Rent Online` section, there are options to configure a " +":guilabel:`Minimal Rental Duration` and designate :guilabel:`Unavailability " +"days`, or days during which pickup and return are not possible." +msgstr "" + +#: ../../content/applications/sales/rental.rst:61 +msgid "Rental products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:63 +msgid "" +"To view all products that can rented in the database, navigate to " +":menuselection:`Rentals app --> Products`. By default, the :guilabel:`Can be" +" Rented` search filter appears in the search bar." +msgstr "" + +#: ../../content/applications/sales/rental.rst:66 +msgid "" +"Each product kanban card displays that product's name, rental price, and " +"product image (if applicable)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:70 +msgid "Rental pricing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:72 +msgid "" +"To adjust the rental pricing on a product, go to the :guilabel:`Products` " +"page in the *Rental* app, then select the desired product or click " +":guilabel:`New` to create a new product from scratch." +msgstr "" + +#: ../../content/applications/sales/rental.rst:75 +msgid "" +"On the product form, ensure the :guilabel:`Can be Rented` checkbox is " +"ticked. Then, open the :guilabel:`Rental prices` tab." +msgstr "" + +#: ../../content/applications/sales/rental.rst:83 +msgid "" +"If creating a rental product outside of the *Rental* app, just ensure the " +":guilabel:`Can be Rented` checkbox is ticked on the product form. By " +"default, this checkbox is ticked whenever a product is created directly in " +"the *Rental* application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:90 +msgid "" +"Under the :guilabel:`Pricing` section of the :guilabel:`Rental prices` tab, " +"designate custom rental prices and rental periods for the product." +msgstr "" + +#: ../../content/applications/sales/rental.rst:93 +msgid "" +"To add pricing for a rental, click :guilabel:`Add a price`. Then, choose a " +"*pricing period* (:dfn:`the unit of duration of the rental`) in the " +":guilabel:`Period` column, or create a new pricing period by typing in the " +"name and clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:97 +msgid "" +"Next, decide whether or not to apply this custom rental price to a specific " +":guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:99 +msgid "" +"Lastly, enter the desired :guilabel:`Price` for that specific " +":guilabel:`Period`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:102 +msgid "" +"There is no limit to how many pricing lines can be added. Multiple pricing " +"options for rental products are typically used to give discounts for " +"customers who agree to longer rental durations." +msgstr "" + +#: ../../content/applications/sales/rental.rst:105 +msgid "" +"To delete any rental pricing option, click the :guilabel:`🗑️ (trash)` icon, " +"and that row is deleted." +msgstr "" + +#: ../../content/applications/sales/rental.rst:109 +msgid "Reservations" +msgstr "การจอง" + +#: ../../content/applications/sales/rental.rst:111 +msgid "" +"Under the :guilabel:`Reservations` section of the :guilabel:`Rental prices` " +"tab, there is the option to configure additional fines for any " +":guilabel:`Extra Hour` or :guilabel:`Extra Day` that the customer takes to " +"return a rental." +msgstr "" + +#: ../../content/applications/sales/rental.rst:115 +msgid "" +"There is also the option to set a :guilabel:`Security Time`, expressed in " +"hours, to make the rental product temporarily unavailable between two rental" +" orders. Such a feature may prove useful if maintenance or cleaning is " +"required between rentals." +msgstr "" + +#: ../../content/applications/sales/rental.rst:120 +msgid "Price computing" +msgstr "" + +#: ../../content/applications/sales/rental.rst:122 +msgid "" +"Odoo always uses two rules to compute the price of a product when a rental " +"order is created:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:124 +msgid "Only one price line is used." +msgstr "" + +#: ../../content/applications/sales/rental.rst:125 +msgid "The cheapest line is selected." +msgstr "" + +#: ../../content/applications/sales/rental.rst:128 +msgid "Consider the following rental pricing configuration for a product:" +msgstr "" + +#: ../../content/applications/sales/rental.rst:130 +msgid "1 day: $100" +msgstr "" + +#: ../../content/applications/sales/rental.rst:131 +msgid "3 days: $250" +msgstr "" + +#: ../../content/applications/sales/rental.rst:132 +msgid "1 week: $500" +msgstr "" + +#: ../../content/applications/sales/rental.rst:134 +msgid "" +"A customer wants to rent this product for eight days. What price will they " +"pay?" +msgstr "" + +#: ../../content/applications/sales/rental.rst:136 +msgid "" +"After an order is created, Odoo selects the second line as this is the " +"cheapest option. The customer has to pay three times '3 days' to cover the " +"rental's eight days, for a total of $750." +msgstr "" + +#: ../../content/applications/sales/rental.rst:142 +msgid "Rental orders" +msgstr "" + +#: ../../content/applications/sales/rental.rst:144 +msgid "" +"To create a rental order in the *Rental* app, navigate to " +":menuselection:`Rental app --> Orders --> Orders`, and click " +":guilabel:`New`. Doing so reveals a blank rental order form to be filled in " +"accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Sample of a filled out rental order available in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:152 +msgid "" +"Start by adding a :guilabel:`Customer`, then configure the desired duration " +"of the rental in the :guilabel:`Rental period` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:155 +msgid "" +"To adjust the rental duration, click the first date in the :guilabel:`Rental" +" period` field, and select the range of dates to represent the rental " +"duration from the pop-up calendar form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"Sample of a rental period calendar pop-up window in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:163 +msgid "" +"Once complete, click :guilabel:`Apply` in the calendar pop-up form. " +"Following that, the pop-up form disappears, and the designated time period " +"of the rental is represented in the :guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst:167 +msgid "" +"Next, add a rental product in the :guilabel:`Order Lines` tab, by clicking " +":guilabel:`Add a product`, and selecting the desired rental product to add " +"to the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst:171 +msgid "" +"If a rental product is added *before* the :guilabel:`Rental period` field " +"has been properly configured, the user can *still* adjust the " +":guilabel:`Rental period` field accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:174 +msgid "" +"Simply select the desired range of dates to represent the duration of the " +"rental, then click :guilabel:`Update Rental Prices` in the " +":guilabel:`Duration` field." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The update rental prices option that appears in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:181 +msgid "" +"Doing so reveals a :guilabel:`Confirmation` pop-up window. If everything is " +"correct, click :guilabel:`Ok`, and Odoo recalculates the rental price " +"accordingly." +msgstr "" + +#: ../../content/applications/sales/rental.rst:184 +msgid "" +"Once all the information has been entered correctly on the rental order " +"form, click the :guilabel:`Send by Email` button to send the quotation to " +"the customer, or click the :guilabel:`Confirm` button to confirm the order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:189 +msgid "Customer signature" +msgstr "" + +#: ../../content/applications/sales/rental.rst:191 +msgid "" +"Upon confirming a rental order, the :guilabel:`Sign Documents` button " +"appears. This gives the ability to request the customer sign a rental " +"agreement, outlining the arrangement between the company and customer, " +"*before* they pick up the rental product(s)." +msgstr "" + +#: ../../content/applications/sales/rental.rst:195 +msgid "" +"Such documents can ensure everything is returned on-time and in its original" +" condition." +msgstr "" + +#: ../../content/applications/sales/rental.rst:198 +msgid "" +"The :guilabel:`Sign Documents` button/option **only** appears if the " +":guilabel:`Digital Documents` feature has been activated in the *Rental* " +"application settings. To do so, navigate to :menuselection:`Rental app --> " +"Configuration --> Settings`, activate :guilabel:`Digital Documents`, and " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:204 +msgid "" +"This feature also requires the :doc:`Sign <../finance/sign>` app. If " +"necessary, Odoo automatically installs it after activating the " +":guilabel:`Digital Documents` setting." +msgstr "" + +#: ../../content/applications/sales/rental.rst:207 +msgid "" +"To request a customer signature on a rental agreement, select a confirmed " +"rental order, and click the :guilabel:`Sign Documents` button to reveal a " +":guilabel:`Sign Documents` pop-up window." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The Sign Documents pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:214 +msgid "" +"From here, select the desired document from the :guilabel:`Document " +"Template` field. Then, click :guilabel:`Sign Document`. Doing so reveals a " +":guilabel:`New Signature Request` pop-up window." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The New Signature Request pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:221 +msgid "" +"Upon confirming the information in the :guilabel:`New Signature Request` " +"pop-up form, click :guilabel:`Sign Now` to initiate the signing process." +msgstr "" + +#: ../../content/applications/sales/rental.rst:224 +msgid "" +"A separate page is then revealed, showcasing the document to be signed, " +"which is accessible to the customer via the customer portal." +msgstr "" + +#: ../../content/applications/sales/rental.rst:227 +msgid "" +"Odoo guides the customer through the signing process with clear, clickable " +"indicators, and allows them to create electronic signatures to quickly " +"complete the form." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The adopt your signature pop-up window that appears in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:234 +msgid "" +"Once the document has been signed and completed, click the " +":guilabel:`Validate & Send Completed Document` button at the bottom of the " +"document." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The validate and send completed document button in the Odoo Rental " +"application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:241 +msgid "" +"Upon clicking the :guilabel:`Validate & Send Completed Document` button, " +"Odoo presents the option to download the signed document for record-keeping " +"purposes, if necessary." +msgstr "" + +#: ../../content/applications/sales/rental.rst:245 +msgid "`Odoo Tutorials: Sign <https://www.odoo.com/slides/sign-61>`_" +msgstr "" + +#: ../../content/applications/sales/rental.rst:250 +msgid "Pickup products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:252 +msgid "" +"When a customer picks up the product(s), navigate to the appropriate rental " +"order, click the :guilabel:`Pickup` button, and then click " +":guilabel:`Validate` in the :guilabel:`Validate a pickup` pop-up form that " +"appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:256 +msgid "" +"Doing so places a :guilabel:`Picked-up` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:259 +msgid "Return products" +msgstr "" + +#: ../../content/applications/sales/rental.rst:261 +msgid "" +"When a customer returns the product(s), navigate to the appropriate rental " +"order, click the :guilabel:`Return` button, and validate the return by " +"clicking :guilabel:`Validate` in the :guilabel:`Validate a return` pop-up " +"form that appears." +msgstr "" + +#: ../../content/applications/sales/rental.rst:265 +msgid "" +"Doing so places a :guilabel:`Returned` status banner on the rental order." +msgstr "" + +#: ../../content/applications/sales/rental.rst:268 +msgid "Print pickup and return receipts" +msgstr "" + +#: ../../content/applications/sales/rental.rst:270 +msgid "" +"Pickup and return receipts can be printed for customers when they pick up " +"and/or return rental products." +msgstr "" + +#: ../../content/applications/sales/rental.rst:273 +msgid "" +"To print pickup and/or return receipts, navigate to the appropriate rental " +"order, click the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/rental.rst-1 +msgid "" +"The pickup and return receipt print option in the Odoo Rental application." +msgstr "" + +#: ../../content/applications/sales/rental.rst:280 +msgid "" +"From this drop-down menu, hover over the :guilabel:`Print` option to reveal " +"a sub-menu. Then select :guilabel:`Pickup and Return Receipt`." +msgstr "" + +#: ../../content/applications/sales/rental.rst:283 +msgid "" +"Odoo generates and downloads a PDF, detailing all information about the " +"current status of the rented item(s)." +msgstr "" + +#: ../../content/applications/sales/sales.rst:10 +msgid "" +"**Odoo Sales** is the application to run your sales process (from quotation " +"to sales order) and deliver and invoice what has been sold." +msgstr "" + +#: ../../content/applications/sales/sales.rst:14 +msgid "" +"`Odoo Tutorials: Sales Tutorials <https://www.odoo.com/slides/sales-17>`_" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector.rst:5 +msgid "Amazon Connector" +msgstr "Amazon Connector" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:3 +msgid "Amazon Connector features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:5 +msgid "" +"The *Amazon Connector* synchronizes orders between Amazon and Odoo, which " +"considerably reduces the amount of time spent manually entering Amazon " +"orders (from the Amazon Seller account) into Odoo. It also allows users to " +"accurately keep track of Amazon sales in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:10 +msgid "Supported features" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:12 +msgid "The Amazon Connector is able to:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:14 +msgid "" +"Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM), and " +"their order items, which include:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:17 +msgid "product name, description, and quantity" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:18 +msgid "shipping costs for the product" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:19 +msgid "gift wrapping charges" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:21 +msgid "" +"Create any missing partner related to an order in Odoo (contact types " +"supported: contact and delivery address)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:24 +msgid "Notify Amazon of confirmed shipment in Odoo (FBM) to get paid." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:26 +msgid "" +"Synchronize (Odoo to Amazon) all available quantities of your products " +"(FBM)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:28 +msgid "Support multiple seller accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:30 +msgid "Support multiple marketplaces per seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:32 +msgid "" +"The following table lists capabilities provided by Odoo when using the " +"Amazon Connector:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Fulfilled By Amazon (FBA)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Fulfilled By Merchant (FBM)" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "**Orders**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize shipped and canceled orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 +msgid "Synchronize unshipped and canceled orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "**Shipping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "" +"Shipping cost is computed by Amazon, and included in the synchronized order." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 +msgid "" +"Shipping cost is computed by Amazon and included in the synchronized orders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "Shipping done by Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:44 +msgid "" +"A delivery order is automatically created in Odoo for each new order. Once " +"it has been processed in Odoo, the status is then synchronized in Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "**Gift Wrapping**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Handled by Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:50 +msgid "" +"Cost is computed by Amazon, and included in the synchronized order. Gift " +"message is added on a line of the order and on the delivery order. Then it " +"is up to the user." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "**Stock Management**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "" +"Managed by Amazon, and synchronized with a virtual location to follow it in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:56 +msgid "Managed in Odoo Inventory app, and synchronized with Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "**Delivery Notifications**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:61 +msgid "Send by Amazon, based on delivery status synchronized from Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +msgid "" +"The Amazon Connector is designed to synchronize the data of sales orders. " +"Other actions, such as downloading monthly fees reports, handling disputes, " +"or issuing refunds, **must** be managed from the *Amazon Seller Central*, as" +" usual." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +msgid "Supported marketplaces" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:75 +msgid "The Amazon Connector supports all the current marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:77 +msgid "" +"If a marketplace is not listed in your Amazon marketplaces, it's possible to" +" :ref:`add a new marketplace <amazon/add-new-marketplace>`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:81 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 +msgid ":doc:`setup`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 +msgid ":doc:`manage`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 +msgid "Amazon order management" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 +msgid "Order synchronization" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 +msgid "" +"Orders are automatically fetched from Amazon, and synchronized in Odoo, at " +"regular intervals." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:10 +msgid "" +"The synchronization is based on the Amazon status: only orders whose status " +"has changed since the last synchronization are fetched from Amazon. This " +"includes changes on either end (Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:13 +msgid "" +"For *FBA* (Fulfilled by Amazon), only *Shipped* and *Canceled* orders are " +"fetched." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 +msgid "" +"For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and " +"*Canceled* orders. For each synchronized order, a sales order and customer " +"are created in Odoo (if the customer is not already registered in the " +"database)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 +msgid "" +"When an order is canceled in Amazon, and was already synchronized in Odoo, " +"the corresponding sales order is automatically canceled in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:24 +msgid "Force synchronization" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26 +msgid "" +"In order to force the synchronization of an order, whose status has **not** " +"changed since the previous synchronization, start by activating the " +":ref:`developer mode <developer-mode>`. This includes changes on either end " +"(Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 +msgid "" +"Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> " +"Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon " +"Accounts`), and modify the date under :menuselection:`Orders Follow-up --> " +"Last Order Sync`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:34 +msgid "" +"Be sure to pick a date that occurs prior to the last status change of the " +"desired order to synchronize and save. This will ensure synchronization " +"occurs correctly." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:39 +msgid "" +"To immediately synchronize the orders of an Amazon account, switch to " +":ref:`developer mode <developer-mode>`, head to the Amazon account in Odoo, " +"and click :guilabel:`Sync Orders`. The same can be done with pickings by " +"clicking :guilabel:`Sync Pickings`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:44 +msgid "Manage deliveries in FBM" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 +msgid "" +"Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a " +"picking is instantly created in the *Inventory* app, along with a sales " +"order and customer record. Then, decide to either ship all the ordered " +"products to the customer at once, or ship products partially using " +"backorders." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:50 +msgid "" +"When a picking related to the order is confirmed, a notification is then " +"sent to Amazon, who, in turn, notifies the customer that the order (or a " +"part of it) is on its way." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 +msgid "" +"Amazon requires users to provide a tracking reference with each delivery. " +"This is needed to assign a carrier." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 +msgid "" +"If the carrier doesn't automatically provide a tracking reference, one must " +"be set manually. This rule applies to all Amazon marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:61 +msgid "" +"If the chosen carrier isn't supported by Odoo, a carrier with the same name " +"can still be created (e.g. create a carrier named `easyship`). The name used" +" is **not** case sensitive, but be mindful to avoid typos. If there are " +"typos, Amazon will **not** recognize them. Next, create a delivery carrier " +"named `Self Delivery` to inform Amazon that the user will make the " +"deliveries. Even with this route, a tracking reference still **must** be " +"entered. Remember, the customer is notified by email about the delivery, and" +" the carrier, along with the tracking reference, are displayed in the email " +"to the customer." +msgstr "" +"หาก Odoo ไม่รองรับผู้ให้บริการที่เลือก " +"จะยังสามารถสร้างผู้ให้บริการที่มีชื่อเดียวกันได้ (เช่น สร้างผู้ให้บริการชื่อ" +" `easyship`) ชื่อที่ใช้ **ไม่** คำนึงถึงตัวพิมพ์เล็กและตัวพิมพ์ใหญ่ " +"แต่โปรดระวังอย่าพิมพ์ผิด หากมีการพิมพ์ผิด Amazon จะ **ไม่** " +"จดจำสิ่งเหล่านั้น จากนั้น สร้างผู้ให้บริการจัดส่งชื่อ 'การจัดส่งด้วยตนเอง' " +"เพื่อแจ้งให้ Amazon ทราบว่าผู้ใช้จะทำการจัดส่ง แม้ว่าจะใช้เส้นทางนี้ " +"แต่ยังคง **ต้อง** ป้อนการอ้างอิงการติดตาม โปรดจำไว้ว่า " +"ลูกค้าจะได้รับแจ้งทางอีเมลเกี่ยวกับการจัดส่ง " +"และผู้ให้บริการขนส่งพร้อมกับข้อมูลอ้างอิงในการติดตามจะแสดงในอีเมลที่ส่งถึงลูกค้า" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:70 +msgid "" +":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75 +msgid "Manage errors when synchronizing deliveries" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:77 +msgid "" +"Sometimes, Amazon can fail to correctly process all the information sent by " +"Odoo. In this case, Odoo sends an email listing all the shipments that " +"failed and the errors Amazon sent with them. In addition, these shipments " +"are flagged with a :guilabel:`Synchronization with Amazon failed` tag." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 +msgid "" +"Usually, the error can be corrected directly in the Amazon backend or in " +"Odoo. If the problem is corrected in Odoo, synchronize the shipment again " +"using the :guilabel:`Retry Amazon Sync` button." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:85 +msgid "" +"It might happen that Odoo receives a notification from Amazon saying that " +"some delivery information was not processed, but without specifying which " +"shipments were affected. In that case, all the shipments in an unknown state" +" will be treated as if they failed to synchronize. Once Odoo receives a " +"notification from Amazon saying that a shipment was processed, its tag will " +"change to :guilabel:`Synchronized with Amazon`. To speed up this process, on" +" your Amazon account, click on :guilabel:`Sync Orders` to manually " +"synchronize these orders, or click on :guilabel:`Recover Order` and enter " +"the relevant Amazon Order Reference." +msgstr "" +"อาจเกิดขึ้นที่ Odoo ได้รับการแจ้งเตือนจาก Amazon " +"ว่าข้อมูลการจัดส่งบางส่วนไม่ได้รับการประมวลผล " +"แต่ไม่ได้ระบุว่าการจัดส่งใดได้รับผลกระทบ ในกรณีดังกล่าว " +"การจัดส่งทั้งหมดในสถานะที่ไม่รู้จักจะได้รับการปฏิบัติเสมือนว่าไม่สามารถซิงโครไนซ์ได้" +" เมื่อ Odoo ได้รับการแจ้งเตือนจาก Amazon ว่ามีการประมวลผลการจัดส่งแล้ว " +"แท็กจะเปลี่ยนเป็น :guilabel:`ซิงโครไนซ์กับ Amazon` " +"เพื่อเร่งการดำเนินการของขั้นตอนนี้ ในบัญชี Amazon ของคุณ ให้คลิกที่ " +":guilabel:`ซิงค์คำสั่งซื้อ` เพื่อซิงโครไนซ์คำสั่งซื้อเหล่านี้ด้วยตนเอง " +"หรือคลิกที่ :guilabel:`กู้คืนคำสั่งซื้อ` และป้อนการอ้างอิงคำสั่งซื้อของ " +"Amazon ที่เกี่ยวข้อง" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:94 +msgid "Follow deliveries in FBA" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +msgid "" +"When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock " +"move is recorded in the *Inventory* app for each sales order item. That way," +" it's saved in the system." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:99 +msgid "" +"Inventory managers can access these stock moves by navigating to " +":menuselection:`Inventory app --> Reporting --> Moves History`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102 +msgid "" +"For FBA orders, the stock move is automatically created in Odoo by the " +"Amazon connector, thanks to the shipping status of Amazon. When sending new " +"products to Amazon, the user should manually create a picking (delivery " +"order) to transfer these products from their warehouse to the Amazon " +"location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:107 +msgid "" +"To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after " +"replenishing stock. An automated replenishment from reordering rules can " +"also be triggered on the Amazon location." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:110 +msgid "" +"The Amazon location is configurable by accessing the Amazon account managed " +"in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales" +" app --> Configuration --> Settings --> Connectors --> Amazon Sync --> " +"Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 +msgid "" +"All accounts of the same company use the same Amazon location, by default. " +"However, it is possible to follow the stock filtered by marketplace." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:117 +msgid "" +"To do that, first remove the marketplace, where the desired stock to follow " +"separately can be found, from the list of synchronized marketplaces, which " +"can be found by navigating to :menuselection:`Sales app --> Configuration " +"--> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:122 +msgid "" +"Next, create another registration for this account, and remove all " +"marketplaces--- **except** the marketplace this is desired to be isolated " +"from the others." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:125 +msgid "" +"Lastly, assign another stock location to the second registration of the " +"account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128 +msgid "Invoice and register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 +msgid "Issue invoices" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133 +msgid "" +"Due to Amazon's policy of not sharing customer email addresses, it is " +"**not** possible to send invoices directly to Amazon customers from Odoo. " +"However, it **is** possible to manually upload the generated invoices from " +"Odoo to the Amazon back-end." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:137 +msgid "" +"Additionally, for B2B clients, it is currently required to manually retrieve" +" VAT numbers from the Amazon back-end **before** creating an invoice in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:141 +msgid "" +"For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: " +"invoices created from Amazon sales orders are **not** synchronized with " +"TaxCloud, since Amazon already includes them in its own tax report to " +"TaxCloud." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:146 +msgid "TaxCloud integration will be decommissioned in Odoo 17+." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 +msgid "Register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151 +msgid "" +"Since customers pay Amazon as an intermediary, creating a dedicated *Bank* " +"journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* " +"intermediary account is recommended." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:154 +msgid "" +"Additionally, as Amazon makes a single monthly payment, selecting all the " +"invoices linked to a single payment is necessary when registering payments." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:157 +msgid "" +"To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon " +"payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment " +"Method`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:160 +msgid "" +"Then, select all the generated payments, and click :menuselection:`Actions " +"--> Create batch payment --> Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:164 +msgid "" +"This same action can be performed with vendor bills from Amazon dedicated to" +" commissions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 +msgid "" +"When the balance is received in the bank account at the end of the month, " +"and the bank statements are recorded, credit the Amazon intermediary account" +" by the amount received." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:170 +msgid "Follow Amazon sales in sales reporting" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 +msgid "" +"On the Amazon account profile in Odoo, a sales team is set under the " +":guilabel:`Order Follow-up` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:175 +msgid "" +"This gives quick access to important metrics related to sales reporting. By " +"default, the Amazon account's sales team is shared between all of the " +"company's accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:178 +msgid "" +"If desired, the sales team on the account can be changed for another, in " +"order to perform a separate reporting for the sales of this account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:182 +msgid "It is also possible to perform reporting on a per-marketplace basis." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 +msgid "" +"First, remove the desired marketplace from the list of synchronized " +"marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:186 +msgid "" +"To access the list of synchronized marketplaces in Odoo, navigate to " +":menuselection:`Sales app --> Configuration --> Settings --> Connectors --> " +"Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:189 +msgid "" +"Then, create another registration for this account, and remove all other " +"marketplaces **except** the one to isolate." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:192 +msgid "" +"Lastly, assign another sales team to one of the two registrations of the " +"account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:195 +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 +msgid ":doc:`features`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:3 +msgid "Amazon Connector configuration" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:5 +msgid "" +"Odoo allows users to register an Amazon seller account in the database, but " +"the user **must** have a paid Amazon Seller account prior to completing the " +"configuration." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:8 +msgid "" +"Set up a paid Seller account on Amazon by first logging into the Amazon " +"platform, and navigating to :menuselection:`Account \\& Lists --> Start a " +"Selling Account` from the drop-down menu located in the header section." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:12 +msgid "" +"Then on the :guilabel:`Sell with Amazon` page, follow the sign-up process " +"and finally proceed to follow the instructions below to register and link " +"that Amazon Seller account in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:16 +msgid "`Sell with Amazon <https://www.amazon.com/b/?node=12766669011>`_" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:19 +msgid "Connect Amazon Seller account to Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:23 +msgid "" +"To connect an Amazon Seller account in Odoo, navigate to " +":menuselection:`Sales app --> Configuration --> Settings --> Connectors " +"section`, activate the :guilabel:`Amazon Sync` feature, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:27 +msgid "" +"Then, return to :menuselection:`Sales app --> Configuration --> Settings -->" +" Connectors section`, and click on the :guilabel:`Amazon Accounts` link " +"under the :guilabel:`Amazon Sync` setting." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "" +"The Amazon Accounts link beneath the Amazon Sync settings in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:34 +msgid "" +"Doing so reveals a separate :guilabel:`Amazon Accounts` page. From here, " +"click :guilabel:`New` to create and link a new Amazon account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:37 +msgid "" +"On the blank :guilabel:`Amazon Account` form page, start by choosing a name " +"for the account (e.g. `American Marketplace`). Then, in the " +":guilabel:`Credentials` tab, select the marketplace on which the seller " +"account was initially created from the :guilabel:`Home Marketplace` drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "A typical Amazon Account form page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:45 +msgid "" +"After saving, the field in the :guilabel:`Credentials` tab is replaced by a " +":guilabel:`Link with Amazon` button." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "" +"A typical Amazon Account form page and Link with Amazon button in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:52 +msgid "" +"Clicking that button redirects to either the Amazon login page, or directly " +"to the required consent page, if the user is already logged in to Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:55 +msgid "On the login page, log in to the desired Amazon seller account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:57 +msgid "" +"On the consent page, confirm that Amazon is allowed to give Odoo access to " +"the account and related data." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:60 +msgid "" +"Upon confirmation, Amazon returns the user to Odoo, and the account has been" +" registered." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:62 +msgid "" +"With the Amazon account successfully registered, the marketplaces available " +"to this specific account are synchronized with Odoo and listed under the " +":guilabel:`Marketplaces` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:65 +msgid "" +"If desired, remove items from the list of synchronized marketplaces to " +"disable synchronization." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:68 +msgid "Amazon orders in Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:70 +msgid "" +"When an Amazon order is synchronized, up to three line items are created on " +"the sales order in Odoo. Each one represents a product sold on Amazon: one " +"for the product that was sold on Amazon Marketplace, one for the shipping " +"charges (if any), and one for the gift wrapping charges (if any)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:76 +msgid "" +"The selection of a database product for a sales order item is done by " +"matching its :guilabel:`Internal Reference` (a customizable product " +"reference idenifier in Odoo, like `FURN001`) with the Amazon *SKU* for " +"marketplace items, the Amazon *Shipping Code* for delivery charges, and the " +"Amazon *Gift Wrapping* code for gift wrapping charges." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:81 +msgid "" +"For marketplace products, pairings are saved as *Amazon Offers*, which are " +"listed under the :guilabel:`Offers` smart button on the account form." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst-1 +msgid "The Amazon Offers smart button on the account form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:88 +msgid "" +"Offers are automatically created when the pairing is established, and " +"they're used for subsequent orders to lookup SKUs. If no offer with a " +"matching SKU is found, :ref:`the internal reference is used instead " +"<amazon/matching>`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:93 +msgid "" +"It's possible to force the pairing of a marketplace item with a specific " +"product, by changing either the product or the SKU of an offer to ensure " +"they match. The offer can be manually created if it was not automatically " +"done yet." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:97 +msgid "" +"This is useful if the internal reference is not used as the SKU, or if the " +"product sells under different conditions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:100 +msgid "" +"If no database product with a matching internal reference is found for a " +"given Amazon SKU or gift wrapping code, then a default database product, " +"*Amazon Sale*, is used. The same is done with the default product *Amazon " +"Shipping* if no database product is found for a given Amazon shipping code." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:105 +msgid "" +"To modify default products, activate the :ref:`developer mode <developer-" +"mode>`, and navigate to :menuselection:`Sales app --> Configuration --> " +"Settings --> Connectors --> Amazon Sync --> Default Products`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:110 +msgid "Product tax configuration" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:112 +msgid "" +"To allow for tax reporting of Amazon sales with Odoo, the taxes applied to " +"the sales order items are those set on the product, or determined by the " +"fiscal position." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:115 +msgid "" +"Make sure to have the correct taxes set on your products in Odoo, or have it" +" done by a fiscal position, to avoid discrepancies in the subtotals between " +"*Amazon Seller Central* and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 +msgid "" +"As Amazon does not necessarily apply the same taxes as those configured in " +"Odoo, it may happen that order totals differ by a few cents between Odoo and" +" *Amazon Seller Central*. Those differences can be resolved with a write-off" +" when reconciling the payments in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:126 +msgid "Add a new marketplace" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:128 +msgid "" +"All marketplaces are supported by the Amazon Connector. To add a new " +"marketplace, proceed as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 +msgid "Activate the :ref:`developer mode <developer-mode>`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:132 +msgid "" +"Go to :menuselection:`Sales app --> Configuration --> Settings --> " +"Connectors --> Amazon Sync --> Amazon Marketplaces`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:134 +msgid "Click :guilabel:`New` to create a new marketplace record." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:135 +msgid "" +"Enter the Marketplace ID in the :guilabel:`API Idenifier` field, and select " +"the :guilabel:`Amazon Region` for your marketplace as described in the " +"`Amazon Documentation for marketplace IDs and regions <https://developer-" +"docs.amazon.com/amazon-shipping/docs/marketplace-ids>`_, and the " +":guilabel:`Seller Central URL` as described in the `Amazon Documentation for" +" seller central URLs <https://developer-docs.amazon.com/amazon-" +"shipping/docs/seller-central-urls>`_." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:140 +msgid "" +"Set the :guilabel:`Name` of the record to `Amazon.<country code>` to easily " +"retrieve it (e.g. `Amazon.se`). The :guilabel:`API Identifier`, the " +":guilabel:`Region` and the :guilabel:`Seller Central URL` fields should " +"respectively hold the *Marketplace ID*, the selected Amazon region, and the " +"*Seller Central URL* values from the Amazon Documentation." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:144 +msgid "" +"Once the marketplace is saved, update the Amazon Account configuration by " +"going to :menuselection:`Sales app --> Configuration --> Settings --> " +"Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/setup.rst:147 +msgid "" +"Select the account on which to use the new marketplace, go to the " +":guilabel:`Marketplaces` tab, and click on :guilabel:`Update available " +"marketplaces`. An animation should confirm the success of the operation. " +"Newly added marketplaces are automatically added to the list of synchronized" +" marketplaces. If the new marketplace is not added to the list, it means " +"that it is either incompatible or unavailable for the seller account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector.rst:5 +msgid "eBay Connector" +msgstr "account_plaid" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:3 +msgid "Linking existing listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:5 +msgid "" +"Once the eBay account is linked existing listings from within the eBay " +"seller account need to be added manually to the Odoo product listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:8 +msgid "" +"The process will be as follows: - Turn off eBay scheduled actions - Add " +"products and link listings - Turn on eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:14 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:28 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:15 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:6 +msgid "To learn more about the eBay connector visit these pages as well:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:32 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:19 +msgid ":doc:`troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:21 +msgid "Turn off eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:23 +msgid "" +"To start linking existing listings in eBay, first turn off the eBay " +"notifications in the scheduled actions in Odoo. The reason for this is so " +"that no orders or eBay data syncs during this process. The " +":guilabel:`Scheduled Actions` can be accessed by first activating " +":ref:`developer mode <developer-mode>`. After doing so, go to " +":menuselection:`Settings --> Technical --> Automation --> Scheduled " +"Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:30 +msgid "" +":doc:`../../../general/developer_mode` must be activated to ensure the " +"technical menu appears for the user." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:33 +msgid "" +"Disabling scheduled actions enables users to sync and validate eBay data " +"before receiving orders. The following are descriptions of scheduled actions" +" that need to be temporarily deactivated:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:36 +msgid "" +":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo" +" (based on :guilabel:`client_order_reference`, or :guilabel:`sales order " +"reference` field). This command also updates existing orders, where changes " +"we made in eBay. New and updated orders are then placed in draft mode. " +"Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:40 +msgid "" +":guilabel:`eBay: synchronize stock`: eBay displays Odoo's stock on hand." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:41 +msgid "" +":guilabel:`eBay: update categories`: eBay will push updated monthly " +"categories (only up to fourth layer; a manual update required for the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:44 +msgid "" +"To toggle off the eBay notification, select the entry from the " +":guilabel:`Scheduled Actions` list. Then, on the page, click the " +":guilabel:`Active` toggle button to turn it off." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:48 +msgid "Sync eBay categories" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:50 +msgid "" +"To ensure that Odoo's eBay products have all the categories available on " +"eBay, the eBay categories should be synced to Odoo next." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:53 +msgid "" +"Navigate to :menuselection:`Settings --> Technical --> Automation --> " +"Scheduled Actions`. Click into the scheduled action labeled: " +":guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`." +" This action will populate the :menuselection:`Sales --> Configuration --> " +"eBay Categories` menu item with all standard eBay product categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:59 +msgid "" +"Odoo only recognizes eBay category paths up to four layers deep. If a " +"product has a listing of more than four, the category field will only " +"populate up to the fourth layer." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:62 +msgid "" +"If product categories beyond four paths are required, users need to manually" +" add those paths. This has historically been done by getting a list of all " +"product categories beyond 4 paths, manually importing them into the Product " +"Category model in Odoo, then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:67 +msgid "" +"Users can import the remaining product categories into the eBay product " +"categories manually using using the :guilabel:`Action` menu and " +":guilabel:`Import` feature." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:71 +msgid "Link eBay listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:73 +msgid "" +"To add eBay listings in Odoo, either manually add products, using a listing " +"ID, or establish an automatic listing link between Odoo and eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:77 +msgid "" +"For more information on listing a product from scratch visit: :ref:`How to " +"list a product? <ebay-connector/listing>`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:81 +msgid "Manual listing link" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:83 +msgid "" +"To add an eBay listing to products in Odoo, begin by going to " +":menuselection:`Sales app --> Products --> Products` and selecting the " +"desired product. Click on :guilabel:`Sell on eBay` (either in the " +":guilabel:`eBay` tab or under the :guilabel:`Product name`). Select " +":guilabel:`Save` if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:87 +msgid "" +"Still the product form, click :guilabel:`link to listing` in the top menu " +"and enter in listing ID from eBay in the pop up (the listing ID is in the " +"eBay product URL)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:91 +msgid "" +"An example URL would be as such: " +"`www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The " +"listing ID is `272222656444` in this case. Once the listing ID has been " +"entered the eBay listing information will sync into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:97 +msgid "Turn on eBay scheduled Actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:99 +msgid "" +"The next step is to turn on the eBay notifications in the scheduled actions " +"in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled " +"Actions` can be accessed by first activating :ref:`developer mode " +"<developer-mode>` and go to :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:104 +msgid "" +"Turning on the following scheduled actions allows users to sync and validate" +" eBay data automatically." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:107 +msgid "" +":guilabel:`eBay: get new orders`: eBay will push all new orders not already " +"in Odoo (based on client_order_reference, or sales order reference field), " +"and will update orders if there has been a change from eBay. Orders will be " +"put in draft mode. Customers will be created if they are not already in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:111 +msgid "" +":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:112 +msgid "" +":guilabel:`eBay: update categories`: eBay will push updated monthly " +"categories (only up to fourth layer, will need to manually update the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:116 +msgid "" +"If an order comes in and the listing from the order is not linked to a " +"product, eBay will create a consumable product.product in its place. These " +"consumables should be altered on the *Sales Order* while in draft state to " +"represent a storable product, and then the user can link to the listing as " +"they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:127 +msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153 +msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:124 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 +msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 +msgid "How to list a product?" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:7 +msgid "" +"In order to list a product on eBay and Odoo there are two methods in Odoo to" +" do so:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:9 +msgid "Make a product in Odoo and list the item eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:11 +msgid "" +"Click :guilabel:`List Item on eBay` in the top menu of the product template." +" The product template can be accessed by navigating to :menuselection:`Sales" +" app --> Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 +msgid "" +"List the item on eBay, then create the product in Odoo, and finally link " +"product to the item on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 +msgid "" +"Click :guilabel:`Link With Existing eBay Listing` in the top menu on the " +"product template.The product template can be accessed by navigating to " +":menuselection:`Sales app --> Product --> Product` and selecting the " +"individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:22 +msgid "" +"If an order comes in and the listing from the order is not linked to a " +"product, eBay will create a consumable product.product in its place. These " +"consumables should be altered on the *sales order* while in draft state to " +"represent a storable product, and then the user can link to the listing as " +"they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:31 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:10 +msgid ":doc:`linking_listings`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 +msgid "Listing without variation" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 +msgid "" +"Access the product template by navigating to :menuselection:`Sales app --> " +"Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:40 +msgid "" +"In order to list a product, select the :guilabel:`Sell on eBay` field on a " +"product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` " +"tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if " +"necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 +msgid "The eBay template form listed in the product template in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:48 +msgid "" +"When the :guilabel:`Use Stock Quantity` field is checked, the quantity set " +"on eBay will be the Odoo *Forecast Quantity* (Odoo *Inventory* app)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:51 +msgid "" +"The :guilabel:`Description Template` allows the administrator to use " +"templates in listings. The default template only use the :guilabel:`eBay " +"Description` field of the product. HTML can be used inside the " +":guilabel:`Description Template` and in the :guilabel:`eBay Description` in " +"Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in " +"the template and description. Simply type a forward slash `/` to reveal a " +"menu with formatting, layout, and text options. To add an image, type " +"`/image`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:58 +msgid "" +"To use images in the listing, another option is to add them as *Attachments*" +" on the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:62 +msgid "" +"For more information on template configuration in Odoo visit: " +":doc:`../../../general/email_communication/email_template`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 +msgid "Listing with variations" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68 +msgid "" +"When the :guilabel:`Sell on eBay` is checked on a product containing " +"variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the " +"eBay form is slightly different. Go to the :guilabel:`Variants` tab to or " +"click :guilabel:`Configure Variants` in the top menu to configure the " +"variant settings. Pricing can be configured for each variation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 +msgid "" +"When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, " +"Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in " +"which the :guilabel:`Fixed Price` can be entered, and the decision to " +":guilabel:`Publish on eBay` can be made for specific variants, along with " +"other options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst-1 +msgid "" +"The fixed price listing type in the eBay tab on a product form in Odoo " +"sales." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:83 +msgid "Product identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85 +msgid "" +"Products identifiers such as EAN, UPC, Brand or MPN are required in most of " +"the eBay categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:88 +msgid "EAN and UPC identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 +msgid "" +"The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` " +"field of the product variant. If the :guilabel:`Barcode` field is empty or " +"is value is not valid, the EAN and UPC values will be set as 'Does not " +"apply' as recommended by eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:94 +msgid "" +"Barcodes can be found on the product template, under the the " +":guilabel:`General Information` tab. Access the product template, first, by " +"navigating to :menuselection:`Sales app --> Products --> Product` and " +"selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:99 +msgid "Listing with item specifics" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 +msgid "" +"In order to add item specifics, one should create a product attribute with a" +" single value in the :guilabel:`Attributes & Variants` tab on the product " +"form. Examples of item specifics include: `MPN` or `Brand`. The Brand and " +"MPN values are working as item specifics and should be defined in the " +":guilabel:`Attributes & Variants` tab on the product form. If these values " +"are not set, 'Does not apply' will be used for the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 +msgid "Process invoices and payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111 +msgid "Posting payment" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113 +msgid "" +"When eBay orders are placed they are always paid for up front, via the eBay " +"site. At no point will users pay for items on eBay through Odoo. Therefore, " +"once orders are synced into Odoo from eBay they are already paid for. Odoo's" +" invoicing and payment functionalities are not utilized. However, invoices " +"need to be created and marked as Paid to “close” the *Sales Order*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 +msgid "" +"Users can opt to mass create and post invoices in batches. To do so, " +"navigate to Quotations in the list view by going to :menuselection:`Sales " +"app --> Orders --> Quotations`. In the upper right corner, select the list " +"view icon. Hover over the icons to reveal the name of each. Then check the " +"boxes on the left that invoices should be made for and go to the " +":guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create " +"Invoices`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:124 +msgid "" +"A pop-up will appear and click on the :guilabel:`Create and view invoice` " +"button. A new screen will populate with the newly created invoices. Next, " +"select all of them by clicking on the box icon next to :guilabel:`Number` in" +" the header row of the list, this will select all the records. Then navigate" +" to the :guilabel:`Action` menu and click :guilabel:`Post entries`. " +"Following this step, a pop-up will appear and click on :guilabel:`Post " +"journal entries`. This will take the invoices out of *draft* and set them to" +" *posted*." +msgstr "" +"ป๊อปอัปจะปรากฏขึ้นและคลิกที่ปุ่ม :guilabel:`สร้างและดูใบแจ้งหนี้` " +"หน้าจอใหม่จะแสดงใบแจ้งหนี้ที่สร้างขึ้นใหม่ " +"จากนั้นเลือกทั้งหมดโดยคลิกที่ไอคอนช่องถัดจาก :guilabel:`หมายเลข` " +"ในแถวส่วนหัวของรายการ ซึ่งจะเป็นการเลือกบันทึกทั้งหมด จากนั้นไปที่เมนู " +":guilabel:`การดำเนินการ` และคลิก :guilabel:`โพสต์รายการ` ทำตามขั้นตอนนี้ " +"ป๊อปอัปจะปรากฏขึ้นและคลิกที่ :guilabel:`โพสต์รายการสมุดรายวัน` " +"การดำเนินการนี้จะนำใบแจ้งหนี้ออกจาก *ฉบับร่าง* และตั้งค่าเป็น *โพสต์แล้ว*" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:132 +msgid "Reconciling payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134 +msgid "" +"Users typically utilize PayPal to receive payment from eBay, and then send " +"lump sums from PayPal into their bank account. To reconcile this income, " +"users can reconcile the one PayPal transfer with all related invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:138 +msgid "" +"First navigate to the :guilabel:`Accounting Dashboard` by going to the " +":menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a" +" new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out " +"the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on " +":guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:143 +msgid "" +"For the :guilabel:`Ending Balance` field, enter the same account that was " +"entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, " +"open the new balance that needs to be reconciled. Under the tab marked: " +":guilabel:`Match Existing Entries` select the entries that are included in " +"this balance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:148 +msgid "" +"After adding all the necessary entries, click :guilabel:`Validate` to " +"complete the reconciliation. To verify the payment, navigate to " +":menuselection:`Customers --> Invoices` and select the desired customer " +"invoice. The *Paid* label should appear under the :guilabel:`Payment Status`" +" column." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:154 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 +msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 +msgid "eBay connector setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 +msgid "Overview" +msgstr "ภาพรวม" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 +msgid "" +"Odoo's eBay connector allows eBay listings to connect with Odoo products. " +"Once connected, :doc:`updates to the listings <linking_listings>` can be " +"made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* " +"are created in Odoo for the user to review and confirm. Once the sales order" +" is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull " +"products out of inventory, and allow the user to create invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 +msgid "eBay - Odoo linked fields" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 +msgid "" +"The following are eBay product details. Each of these eBay fields update " +"corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:27 +msgid "eBay URL" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:28 +msgid "eBay status" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 +msgid "Quantity sold" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:30 +msgid "Start date" +msgstr "วันเริ่มต้น" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:31 +msgid "Title" +msgstr "คำนำหน้าชื่อ" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:32 +msgid "Subtitle" +msgstr "คำบรรยาย" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 +msgid "Item condition" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:34 +msgid "Category" +msgstr "หมวดหมู่" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:35 +msgid "Category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 +msgid "Store category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:37 +msgid "Store category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:38 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:39 +msgid "Seller profiles" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 +msgid "Postal code" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:41 +msgid "Shipping policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 +msgid "Listing type (fixed price or auction)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:44 +msgid "Starting price for Auction" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:45 +msgid "Buy it now price" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 +msgid "Fixed Price amount" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:48 +msgid "Use stock quantity" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:49 +msgid "Quantity on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:50 +msgid "Duration" +msgstr "ระยะเวลา" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 +msgid "Allow best offer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 +msgid "Private listing" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 +msgid "eBay description" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 +msgid "eBay product image" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:55 +msgid "Country" +msgstr "ประเทศ" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 +msgid "eBay terms" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 +msgid "" +"*Variations* group multiple products into one, with variation (or variant) " +"options. Variations can sync to Odoo's attributes and values. Variations " +"will appear in drop down menus near the top of the page when viewing an eBay" +" listing. These are comparable to product variants in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "An example on eBay of the variations that can be added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:68 +msgid "" +"*Item specifics*, located at the bottom of the listing, detail product-" +"specific information. These specifics don't sync with Odoo fields by " +"default; a development is required to link these fields." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Item specifics listed on an eBay product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:75 +msgid "" +"*Sandbox* and *Production* are terms that are used to categorize the eBay " +"environments as either still in development/testing (*Sandbox*) or for use " +"in the real instance of the database with real customer information/dataset " +"(*Production*). It is recommended to start first in the *Sandbox* to test, " +"and then following the processes below, create a *Production* instance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 +msgid "" +"eBay's sandbox environment can be accessed by navigating to `eBay's sandbox " +"portal <https://sandbox.ebay.com/>`_ at `https://sandbox.ebay.com/`. eBay's " +"production environment can be accessed by navigating to `eBay.com portal " +"<https://www.ebay.com/>`_ or `https://www.ebay.com/`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:87 +msgid "" +"The environment selection **must** remain the same for all environment " +"settings on eBay and on Odoo throughout this setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:91 +msgid "eBay actions available on Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:93 +msgid "" +"The following are built-in actions in Odoo that add or update eBay listings:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 +msgid "" +"**List**/ **Link**: generate a new eBay listing with an Odoo product by " +"clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay" +" Listing`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 +msgid "" +":guilabel:`Revise item` button: after making changes to an eBay listing in " +"Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to" +" update the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:99 +msgid "" +"**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` " +"was not selected, a user can relist the item from Odoo. The start date will " +"reset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:101 +msgid "" +":guilabel:`End item's listing` button: end a listing on eBay directly from " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:102 +msgid "" +"**Unlink product listings**: users can unlink a product from the eBay " +"listing; the listing will stay intact on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:106 +msgid "Setup required on Odoo prior to eBay setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:108 +msgid "" +"To link eBay with Odoo, install the eBay module by navigating to the Odoo " +"dashboard and clicking into the :guilabel:`Apps` application. Search the " +"term `eBay` and install the `eBay Connector` module." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 +msgid "The following items must be configured before eBay is set up:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:114 +msgid "" +"In Odoo, create and configure products that are intended to be listed in " +"eBay. eBay does not import new products into Odoo. All products must first " +"be created in Odoo, and then linked to listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 +msgid "" +"Odoo does not allow multiple eBay listings to be linked per product in Odoo." +" If the company sells the same product for multiple listings, follow these " +"instructions:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 +msgid "" +"Set up one *base* product (noted in the :guilabel:`Component` field of the " +":abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull " +"from. This will be a storable product so stock can be kept. Highlighted in " +"green below, this product will be included in the kit on each subsequent " +"“linked” product below." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 +msgid "" +"Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the " +":abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type" +" will be determined by the company's accounting settings, as explained in " +"the Odoo documentation. Highlighted in yellow below, each product should " +"have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base " +"product as a :guilabel:`Component` of the kit. When this linked eBay product" +" is sold, the delivery order created will have the base product listed in " +"lieu of the linked product." +msgstr "" +"ตั้งค่าผลิตภัณฑ์ *ที่เชื่อมโยง* 2 รายการขึ้นไป (ระบุไว้ในฟิลด์ " +":guilabel:`ผลิตภัณฑ์` ของ :abbr:`BoM (Bill of Materials)` " +"หนึ่งรายการสำหรับการลงประกาศใน eBay แต่ละรายการ " +"ประเภทผลิตภัณฑ์จะถูกกำหนดโดยการตั้งค่าการบัญชีของบริษัท " +"ตามที่อธิบายไว้ในเอกสารของ Odoo ไฮไลต์ด้วยสีเหลืองด้านล่าง " +"แต่ละผลิตภัณฑ์ควรมี :guilabel:`ประเภท BoM` เท่ากับ :guilabel:`ชุดผลิตภัณฑ์` " +"และมีผลิตภัณฑ์พื้นฐานเป็น :guilabel:`ส่วนประกอบ` ของชุด " +"เมื่อมีการขายผลิตภัณฑ์ eBay ที่เชื่อมโยงนี้ " +"คำสั่งซื้อการจัดส่งที่สร้างขึ้นจะมีรายการผลิตภัณฑ์พื้นฐานแทนผลิตภัณฑ์ที่เชื่อมโยง" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:0 +msgid "Setting up bill of materials with base product and linked products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:138 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/management/bill_configuration/`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 +msgid "" +"eBay does not automatically create invoices for eBay orders that get pushed " +"into Odoo. Set invoicing policy on eBay products: invoicing policy will " +"dictate when the product can be invoiced. Since most eBay users collect " +"payment before the product is shipped, “invoice on ordered” will allow users" +" to mass create invoices for eBay orders every day." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:144 +msgid "" +"Set the :guilabel:`Outgoing Shipments` route for the warehouse to " +":guilabel:`Deliver goods directly (1 step)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:148 +msgid "" +"When the :guilabel:`Outgoing Shipments` route is set to two or three steps, " +"a known bug occurs: eBay wrongly marks orders as delivered when the pick " +"operation in Odoo is confirmed. The expected behavior is to mark orders as " +"delivered **after** the *delivery order* is confirmed. This mislabeling " +"prevents tracking numbers in eBay from being imported onto the delivery " +"order." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:152 +msgid "" +"If the Accounting/Invoicing apps are installed, practice registering payment" +" and reconciling invoices created from eBay orders with incoming eBay money." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:156 +msgid ":doc:`../../..//finance/accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:158 +msgid "" +"Generate a marketplace account deletion/closure notification token. To " +"begin, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`. Under the :guilabel:`eBay` heading, change the mode to " +":guilabel:`Production`, and input random text values for the " +":guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` " +"button under the :guilabel:`eBay Marketplace Account Deletion/Closure " +"Notifications` section. This token will be used during the setup on eBay for" +" the deletion/closure notifications configuration." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Generate a verification token in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:170 +msgid "Set up on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:173 +msgid "Set up eBay developer account" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:175 +msgid "" +"To start, create an eBay developer account via `eBay's developer portal " +"<https://go.developer.ebay.com/>`_. This site requires a different login and" +" password than the eBay account, though the same email address can be used " +"to register. The verification to create a developer account is around 24 " +"hours." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:181 +msgid "Set up eBay keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:183 +msgid "" +"Once the eBay developer account is created, set up an application on `eBay's" +" developer portal <https://go.developer.ebay.com/>`_. Next, navigate to the " +":guilabel:`Hi [username]` heading at top right of screen, then from the " +"drop-down menu options, click :guilabel:`Application Keysets`. Doing so " +"opens a pop-up that prompts the user to :guilabel:`Enter Application Title` " +"(up to fifty characters), and choose a development environment " +"(:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate " +"first keyset. This application title is not saved until the keyset is " +"generated. Click on :guilabel:`Create a keyset` to generate the keyset." +msgstr "" +"เมื่อสร้างบัญชีนักพัฒนา eBay แล้ว ให้ตั้งค่าแอปพลิเคชันบน " +"`พอร์ทัลนักพัฒนาของ eBay <https://go.developer.ebay.com/>`_ จากนั้น " +"ไปที่ส่วนหัว :guilabel:`สวัสดี [ชื่อผู้ใช้]` ที่มุมขวาบนของหน้าจอ " +"จากนั้นจากตัวเลือกเมนูแบบเลื่อนลง คลิก :guilabel:`ชุดคีย์แอปพลิเคชัน` " +"การทำเช่นนี้จะเปิดป๊อปอัปที่แจ้งให้ผู้ใช้ :guilabel:`ป้อนชื่อแอปพลิเคชัน` " +"(สูงสุดห้าสิบตัวอักษร) และเลือกสภาพแวดล้อมการพัฒนา (:guilabel:`Sandbox` หรือ" +" :guilabel:`การผลิต`) สองฟิลด์นี้สร้างชุดคีย์ชุดแรก " +"ชื่อแอปพลิเคชันนี้จะไม่ถูกบันทึกจนกว่าจะสร้างชุดคีย์ คลิกที่ " +":guilabel:`สร้างชุดคีย์` เพื่อสร้างชุดคีย์" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:192 +msgid "" +"The newly created *production keyset* is disabled by default. Activate it by" +" subscribing to the eBay Marketplace 'account deletion or closure " +"notifications' or by applying to eBay for an exemption. Once enabled, the " +"database can make 5000 calls per day using this keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Disabled keyset present after creating a keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:201 +msgid "Configure account deletion / notification settings (Production)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:203 +msgid "" +"To configure notifications or delete the database on a production " +"environment, navigate to the `eBay developer portal " +"<https://go.developer.ebay.com/>`_. Configure the account " +"deletion/notification settings in eBay by navigating to the `Hi [username]` " +"at top right of screen, then :guilabel:`Application Keysets`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:208 +msgid "" +"Next, click the :guilabel:`marketplace deletion/account closure " +"notification` option under the :guilabel:`Production` keyset column. Enter " +"an email under :guilabel:`Email to notify if marketplace account deletion " +"notification endpoint is down`. Click :guilabel:`Save` to enable the email." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:212 +msgid "" +"Following this action, enter the :guilabel:`Marketplace account deletion " +"notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in" +" Odoo by navigating to :menuselection:`Sales app --> Configuration --> " +"Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure " +"Notifications` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:217 +msgid "" +"Clicking the :guilabel:`Generate Token` button in Odoo below this field " +"creates a verification token for the eBay production environment. In Odoo, " +":guilabel:`Copy` the newly created token and navigate to eBay to fill in the" +" :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the " +":guilabel:`Event Notification Delivery Method`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Configuring account deletion / notification settings in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:226 +msgid "" +"After completing the above fields, click :guilabel:`Send Test Notification` " +"to test the new notifications. Proceed to the next step when the green check" +" mark appears. Revisit the above settings if the test post is not as " +"expected." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:230 +msgid "" +"After configuring notification settings, go back to the " +":menuselection:`Application Keys` page to generate production keysets." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:234 +msgid "Creating the keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:236 +msgid "" +"A successful setup of the notifications enables the ability to create " +"Production Keysets which are needed in the remainder of the Odoo " +"configuration. Navigate back to the :menuselection:`Application Keys` page " +"generate a production keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:240 +msgid "" +"The administrator is prompted to :menuselection:`Confirm the Primary " +"Contact`. Enter or confirm the account owner (the person legally responsible" +" for the eBay API License Agreement). Fill out :guilabel:`First Name`, " +":guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select " +"either the :guilabel:`Individual` or :guilabel:`Business` options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:246 +msgid "" +"The provided email address or phone number does **not** have to match the " +"account's. eBay uses this information to contacting the business or " +"individual in case of issues with user tokens. Additional contacts can be " +"added from the :guilabel:`Profile & Contacts` page on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:250 +msgid "" +"Click on :guilabel:`Continue to Create Keys` to confirm the primary contact." +" The :guilabel:`Application Keys` populates in a new screen and an email is " +"also sent to the developer account. An :guilabel:`App ID (Client ID)`, " +":guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Application keys are populated after creating the app in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:259 +msgid "" +"Copy these values down as they will be input into Odoo later in the process." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:262 +msgid "Create eBay user token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:264 +msgid "" +"Now, create a *user token* in eBay by navigating to the `Hi [username]` at " +"top right of screen, then :guilabel:`User Access Tokens`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "Generate user token s on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:271 +msgid "" +"Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing " +"or :guilabel:`Production` for the live database. Maintain the same selection" +" for all environment settings on both eBay and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:275 +msgid "Next, select the radio button labeled :guilabel:`Auth'n'Auth`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:277 +msgid "" +"Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` " +"to get a user token in the chosen environment. This button varies based on " +"the selection made above for either :guilabel:`Sandbox` or " +":guilabel:`Production`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:281 +msgid "" +"Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal " +"Address`. Complete the required fields, which are :guilabel:`First Name`, " +":guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`," +" and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either " +":guilabel:`Individual` or :guilabel:`Business`. To complete the " +"confirmation, click :guilabel:`Sign into eBay to get a Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:288 +msgid "" +"eBay will contact this individual or business should there be any issues " +"with the application keys. Other contacts can be added on the " +":menuselection:`Profile & Contacts` eBay page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:291 +msgid "" +"The administrator will be redirected to either a sandbox or production sign-" +"in page for eBay. This login is different than the eBay developer's console," +" it is the eBay account where the items will be sold on. This email and/or " +"login can differ from the eBay developer account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:295 +msgid "" +"Enter the :guilabel:`Email` or :guilabel:`Username` for the eBay account and" +" sign into the eBay account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:299 +msgid "" +"Should an additional user be needed for the sandbox simulation, a test user " +"needs to be created. Visit `eBay's Register for Sandbox form " +"<https://developer.ebay.com/sandbox/register>`_. Detailed instructions can " +"be found on eBay's help pages: `Create a test Sandbox user " +"<https://developer.ebay.com/api-docs/static/gs_create-a-test-sandbox-" +"user.html>`_." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:305 +msgid "Grant application access" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:307 +msgid "" +"After signing into the production or sandbox environment, eBay presents the " +"administrator with an *agreement* to grant access to the user's eBay data." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:310 +msgid "" +"Clicking :guilabel:`Agree` allows eBay to link the eBay account with the " +"*application programming interface* (API). This agreement can be changed at " +"any time by visiting eBay's account preferences." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:314 +msgid "" +"eBay has a timed sequence between signing in and agreeing to the terms for " +"the :abbr:`API (Application Programming Interface)` linkage to the account. " +"Once complete a :guilabel:`User Token` will populate on the " +":menuselection:`User Tokens` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:318 +msgid "" +"A :guilabel:`User Token` will populate on the screen. Make sure to copy this" +" token down as it will be used in the next steps along with the " +":guilabel:`Application Keyset`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst-1 +msgid "" +"Generated user token and API explorer link on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:326 +msgid "" +"Signing in to the eBay account is necessary to create to the token. The eBay" +" developer can also revoke the token by clicking on the :guilabel:`Revoke a " +"Token` link." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:330 +msgid "API explorer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:332 +msgid "" +"Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have " +"been created, a test can be executed via the `API Explorer " +"<https://developer.ebay.com/DevZone/build-test/test-tool/default.aspx>`_ to " +"ensure that the :abbr:`API (Application Programming Interface)` is " +"configured correctly. This test will execute a simple search using the " +":abbr:`API (Application Programming Interface)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:338 +msgid "" +"To begin the :abbr:`API (Application Programming Interface)` test, click on " +":guilabel:`Get OAuth Application Token`. This will populate the key into the" +" :guilabel:`Token` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:341 +msgid "" +"A basic search function is set to execute. Click on :guilabel:`Execute` to " +"complete the test. A successful test will respond with a :guilabel:`Call " +"Response` of `200 OK` with a corresponding :guilabel:`Time`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:346 +msgid "Entering credentials into Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:348 +msgid "" +"The previously copied :guilabel:`User Token` and :guilabel:`Application " +"Keyset` are now ready to be entered into the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:351 +msgid "" +"Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> " +"Configuration --> Settings --> eBay`) and paste the following credentials " +"from eBay into the corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:358 +msgid "Platform" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:359 +msgid "Dev Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:360 +msgid "Token" +msgstr "โทเค็น" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:361 +msgid "App Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:362 +msgid "Cert Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:363 +msgid "eBay" +msgstr "eBay" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:364 +msgid "Dev ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:365 +msgid "User Token" +msgstr "โทเค็นผู้ใช้" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:366 +msgid "App ID (Client ID)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:367 +msgid "Cert ID (Client Secret)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:368 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:102 +msgid "Odoo" +msgstr "Odoo" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:369 +msgid "Developer Key" +msgstr "กุญแจของนักพัฒนา" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:370 +msgid "Production/Sandbox Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:371 +msgid "Production/Sandbox App Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:372 +msgid "Production/Sandbox Cert Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:375 +msgid "" +"The :guilabel:`Application Keyset` can be accessed by going to `eBay's " +"developer portal <https://go.developer.ebay.com/>`_ and navigate to the `Hi " +"[username]` at top right of screen, then click on :guilabel:`Application " +"Keysets`. Get to the *User Token* in eBay by navigating to the `Hi " +"[username]` at top right of screen, then :guilabel:`User Access Tokens` and " +"click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also" +" be accessed by clicking on :guilabel:`User Tokens` from the " +":menuselection:`Application Keys` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:382 +msgid "" +"Confirm that the setup is correct by saving the credentials in Odoo. Once " +"the initial setup is complete, a new menu tab in products will appear called" +" `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` " +"documentation on how to list products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:387 +msgid "" +"Sync product categories by clicking :guilabel:`Product Categories`. After " +"syncing, a new menu item, `eBay Category`, appears available for products to" +" be configured with. These eBay categories are imported from the Odoo " +"database and are available when listing an item on eBay through Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:393 +msgid "" +"If Product Categories beyond four paths are required, users will need to " +"manually add those paths. This has historically been done by getting a list " +"of all product categories beyond four paths, manually importing them into " +"the Product Category model in Odoo, and then linking them individually to " +"the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:399 +msgid "Now that the setup is complete, proceed to either:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:401 +msgid ":doc:`Create listings <manage>`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:402 +msgid ":doc:`Link existing listings <linking_listings>`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:3 +msgid "Troubleshooting eBay connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:13 +msgid "Accept account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:15 +msgid "" +"Since September 2021, **eBay requires supporting customer account " +"deletion/closure notifications**. As such, when eBay receives an account " +"request for deletion, all eBay partners must confirm the reception of the " +"request and take further action if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:19 +msgid "" +"Odoo has a notification endpoint to receive those notifications, confirm the" +" reception of the request, and handle the first set of actions to anonymize " +"the account details in *Contacts* and remove the customer's access to the " +"portal." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:24 +msgid "" +"Make sure to correctly :ref:`set up the subscription to the marketplace " +"account deletion notifications <ebay/subscribe-account-deletion-" +"notifications>` as eBay may temporarily disable the related eBay account " +"until the subscription is completed." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:29 +msgid "Verify the installation of Odoo is up to date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:31 +msgid "" +"In order to activate the endpoint, the module *eBay Connector - Account " +"Deletion* must be installed. If the Odoo database was first created after " +"September 2021, the module is installed automatically and the administrator " +"can proceed to the :ref:`next step <ebay/retrieve-endpoint-details>`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:36 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:38 +msgid "" +"The notification endpoint is made available through a new Odoo module; to be" +" able to install it, the administrator must make sure that the Odoo source " +"code is up-to-date." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:41 +msgid "" +"If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is " +"already up-to-date, so proceed to the next step." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 +msgid "" +"If the company uses Odoo with an on-premise setup or through a partner, then" +" the administrator must update the installation as detailed in :doc:`this " +"documentation page </administration/maintain/update>` or by contacting an " +"integrating partner." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:50 +msgid "" +"New modules must be *discovered* by the Odoo instance to be available in the" +" :menuselection:`Apps` menu." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:53 +msgid "" +"To do so, activate the :ref:`developer mode <developer-mode>`, and go to " +":menuselection:`Apps -> Update Apps List`. A wizard will ask for " +"confirmation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:57 +msgid "Install the eBay Connector - Account Deletion update" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:60 +msgid "" +"**Never** install new modules in the production database without testing " +"them in a duplicate or staging environment. For Odoo.com customers, a " +"duplicate database can be created from the database management page. For " +"Odoo.sh users, the administrator should use a staging or duplicate database." +" For on-premise users, the administrator should use a staging environment - " +"contact the integrating partner for more information regarding how to test a" +" new module in a particular setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:67 +msgid "" +"To install the module, go to the :menuselection:`Apps` menu, remove the " +"`Apps` search facet and search for `eBay`. If the module *eBay Connector - " +"Account Deletion* is present and marked as installed, the Odoo database is " +"already up-to-date and the administrator can proceed with the next step. If " +"it is not yet installed, install it now." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:75 +msgid "Retrieve endpoint details from Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:77 +msgid "" +"The endpoint details can be found in :menuselection:`Sales --> Configuration" +" --> Settings --> eBay`. First, input random text values for the " +":guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. " +"Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification " +"Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:89 +msgid "Subscribe to account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:91 +msgid "" +"Navigate to the `eBay developer portal <https://go.developer.ebay.com/>`_. " +"Configure the account deletion/notification settings in eBay by navigating " +"to the `Hi [username]` at the top right of screen, then go to " +":guilabel:`Alerts & Notifications`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:99 +msgid "" +"To subscribe to deletion/closure notifications, eBay needs a few details:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:101 +msgid "" +"An *email address* to send notifications to if the endpoint is unreachable." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:102 +msgid "The *endpoint details*:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:104 +msgid "The URL to Odoo's account deletion notification endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:105 +msgid "A verification token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Dedicated fields to enter the endpoint details" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:112 +msgid "" +"The administrator can edit the last two fields once the email address field " +"is filled out." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:115 +msgid "Verify the connectivity with the endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:117 +msgid "" +"After setting the retrieved endpoint details in eBay's dashboard, consider " +"testing the connectivity with the :guilabel:`Send Test Notification` button." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:120 +msgid "" +"The following confirmation message should be received: \"A test notification" +" was sent successfully!\"" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst-1 +msgid "Button to send test notification" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing.rst:5 +msgid "Invoicing Method" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:3 +msgid "Down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:5 +msgid "" +"A down payment is a partial payment made by the buyer when a sales contract " +"is concluded. This implies both parties' (seller and buyer) full commitment " +"to honor the contract." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:8 +msgid "" +"With a down payment, the buyer pays a portion of the total amount owed while" +" agreeing to pay the remaining amount at a later date. In turn, the seller " +"provides goods or services to the buyer after accepting the down payment, " +"trusting that the remaining amount will be paid later on." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:13 +msgid "Create invoices" +msgstr "สร้างใบแจ้งหนี้" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:15 +msgid "" +"When a sales order is confirmed, the option to create an invoice becomes " +"available, via the :guilabel:`Create Invoice` button, located in the upper-" +"left corner of the sales order form. When clicked, a :guilabel:`Create " +"invoices` pop-up appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "Create invoices pop-up form that appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:24 +msgid "" +"Invoices are automatically created as drafts, so they can be reviewed before" +" validation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:26 +msgid "" +"On the :guilabel:`Create invoices` pop-up, there are 3 options to choose " +"from in the :guilabel:`Create Invoice` field:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:29 +msgid ":guilabel:`Regular invoice`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:30 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:42 +msgid ":guilabel:`Down payment (percentage)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:31 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:43 +msgid ":guilabel:`Down payment (fixed amount)`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:34 +msgid "" +"If :guilabel:`Regular Invoice` is selected, the other fields disappear, as " +"they only pertain to down payment configurations." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:38 +msgid "Initial down payment request" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:40 +msgid "" +"On the :guilabel:`Create invoices` pop-up form, the down payment options " +"are:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:45 +msgid "" +"Once the desired down payment option is selected in the :guilabel:`Create " +"Invoice` field on the pop-up form, designate the desired amount, either as a" +" percentage or a fixed amount, in the :guilabel:`Down Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:49 +msgid "" +"Then, select the appropriate income account for the invoice in the " +":guilabel:`Income Account` field. Next, select a tax amount, if necessary, " +"in the :guilabel:`Customer Taxes` drop-down field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"A create invoices pop-up form with down payment fields filled in with " +"information." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:56 +msgid "" +"Once all fields are filled in with the desired information, click the " +":guilabel:`Create Draft Invoice` button. Upon clicking this button, Odoo " +"reveals the :guilabel:`Customer Invoice Draft`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:59 +msgid "" +"In the :guilabel:`Invoice Lines` tab of the :guilabel:`Customer Invoice " +"Draft`, the down payment that was just configured in the :guilabel:`Create " +"invoices` pop-up form appears as a :guilabel:`Product`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Down payment as a product in the invoice lines tab of a customer invoice " +"draft in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:68 +msgid "" +"When the :guilabel:`Down payment` product in the :guilabel:`Invoice Lines` " +"tab is clicked, Odoo reveals the product form for the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:71 +msgid "" +"By default, the :guilabel:`Product Type` of down payment products generated " +"for invoices are set as :guilabel:`Service`, with the :guilabel:`Invoicing " +"Policy` set to :guilabel:`Prepaid/Fixed Price`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Down payment product form with service product type and invoicing policy " +"field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:79 +msgid "This product can be edited/modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:82 +msgid "" +"If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the " +":guilabel:`Invoicing Policy`, an invoice will **not** be able to be created." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:86 +msgid "Example: request 50% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:89 +msgid "" +"The following example involves a 50% amount down payment on a product " +"(:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the " +":guilabel:`Invoicing Policy`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:0 +msgid "Cabinet with doors product form showcasing various details and fields." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:97 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:260 +#: ../../content/applications/sales/sales/invoicing/expense.rst:226 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:238 +#: ../../content/applications/sales/sales/invoicing/proforma.rst:71 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:166 +msgid ":doc:`invoicing_policy`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 +msgid "" +"First, navigate to :menuselection:`Sales app --> New`, and add a " +":guilabel:`Customer` to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:102 +msgid "" +"Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, " +"and select the :guilabel:`Cabinet with Doors` product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +msgid "" +"When the order is confirmed (via the :guilabel:`Confirm` button), the " +"quotation turns into a sales order. Once this occurs, create and view the " +"invoice by clicking :guilabel:`Create Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Cabinet with doors sales order that's been confirmed in the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +msgid "" +"Next, on the :guilabel:`Create invoices` pop-up window that appears, select " +":guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down " +"Payment Amount` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:116 +msgid "" +"The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are " +"*not* required fields, and they will *not* appear if they've already been " +"preconfigured in previous down payment requests." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:120 +msgid "" +"For more information, check out the documentation on :ref:`customer taxes " +"modification on down payments <sales/invoicing/customer-tax-modification-" +"down-payments>` and :ref:`income account modification on down payments " +"<sales/invoicing/income-account-modification>`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:124 +msgid "" +"Lastly, click :guilabel:`Create Draft Invoice` to create and view the " +"invoice draft." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +msgid "" +"Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which " +"includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice" +" Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:129 +msgid "" +"From there, the invoice can be confirmed and posted by clicking " +":guilabel:`Confirm`. Confirming the invoice changes the status from " +":guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of " +"buttons at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "A sample draft invoice with down payment mentioned in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:137 +msgid "" +"From those buttons, the payment can be registered by clicking " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Showcase of the Register Payment button on a confirmed customer invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:143 +msgid "" +"Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-" +"populated with the necessary information. Confirm the information provided " +"is correct and make any necessary adjustments. When ready, click the " +":guilabel:`Create Payment` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Showcase of the Register Payment pop-up window with create payment button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:151 +msgid "" +"After clicking :guilabel:`Create Payment`, Odoo reveals the customer " +"invoice, now with a green :guilabel:`In Payment` banner in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"Customer Invoice with a green In Payment banner located in the upper-right " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +msgid "" +"Now, when the customer wants to pay the remaining amount of the order, " +"another invoice must be created. To do that, return to the sales order, via " +"the breadcrumb links." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:161 +msgid "" +"Back on the sales order, a new :guilabel:`Down Payments` section is present " +"in the :guilabel:`Order Lines` tab, along with the down payment that was " +"just invoiced and posted." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The down payments section in the order lines tab of a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:168 +msgid "Next, click the :guilabel:`Create Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +msgid "" +"On the :guilabel:`Create invoices` pop-up window that appears, there are two" +" new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "" +"The deduct down payment option on the create invoices pop up in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:177 +msgid "" +"If the remaining amount is ready to be paid, select the :guilabel:`Regular " +"Invoice` option. Odoo will create an invoice for the exact amount needed to " +"complete the total payment, as indicated in the :guilabel:`Amount to " +"invoice` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:181 +msgid "Once ready, click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 +msgid "" +"Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing " +"*all* the invoices for that specific sales order in the :guilabel:`Invoice " +"Lines` tab. Each invoice line item displays all the necessary information " +"related to each invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:187 +msgid "" +"To complete the flow, click :guilabel:`Confirm`, which changes the status of" +" the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:190 +msgid "" +"Once again, the :guilabel:`Register Payment` appears, with all fields auto-" +"populated with the necessary information, including the remaining amount " +"left to be paid on the order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The second register payment pop-up form in Odoo sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:197 +msgid "" +"After confirming that information, click :guilabel:`Create Payment`. Doing " +"so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In" +" Payment` banner in the upper-right corner. Also, both down payments are " +"present in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "The second down payment invoice with in payment banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:205 +msgid "At this point, the flow is now complete." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:208 +msgid "" +"This flow is also possible with the :guilabel:`Fixed amount` down payment " +"option." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:211 +msgid "" +"If a down payment is used with a product that has a :guilabel:`Delivered " +"quantities` invoicing policy, the down payments will **not** be able to be " +"deducted when it comes time to invoice the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:215 +msgid "" +"This is because, due to the invoicing policy, the product(s) would have to " +"be delivered *before* creating the final invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:218 +msgid "" +"If nothing has been delivered, a :guilabel:`Credit Note` is created, which " +"cancels the draft invoice that was created after the down payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:221 +msgid "" +"To utilize the :guilabel:`Credit Note` option, the *Inventory* application " +"must be installed, in order to confirm the delivery. Otherwise, the " +"delivered quantity can be entered manually directly on the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:228 +msgid "Customer taxes modification on down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:230 +msgid "" +"To adjust the income account and customer taxes attached to a down payment, " +"navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> " +"Products --> Products`), search for the `Down Payment` product in the search" +" bar, and select it to reveal the product detail page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:234 +msgid "" +"On the :guilabel:`Down Payment` product page, in the :guilabel:`General " +"Information` tab, the customer taxes can be modified in the " +":guilabel:`Customer Taxes` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst-1 +msgid "How to modify the income account link to down payments." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 +msgid "Income account modification on down payments" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:246 +msgid "" +"To change or adjust the income account attached to the :guilabel:`Down " +"Payment` product page, the *Accounting* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:249 +msgid "" +"With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes " +"available on the product page. That tab will **not** be accessible without " +"the *Accounting* app installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:252 +msgid "" +"In the :guilabel:`Accounting` tab, the income account can be changed in the " +":guilabel:`Income Account` field, located in the :guilabel:`Receivables` " +"section." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:3 +msgid "Reinvoice expenses to customers" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:5 +msgid "" +"While working on a project for a client, employees often have to spend their" +" own money on various expenses related to the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:8 +msgid "" +"For example, an employee may need to use their own money to pay for a hotel," +" while they provide an on-site service for a client. As a company, this " +"expense should be reinvoiced to the customer. With Odoo, these kinds of " +"expenses can quickly be reinvoiced to the customer related to the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:13 +msgid "Expenses application" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:15 +msgid "" +"To be able to reinvoice a customer for an expense, the *Expenses* " +"application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:17 +msgid "" +"To install the *Expenses* application, navigate to :menuselection:`main Odoo" +" dashboard --> Apps`, and click :guilabel:`Install` on the *Expenses* " +"application block. When clicked, Odoo installs the application, refreshes " +"the page, and returns to the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:22 +msgid "Add expenses to sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:24 +msgid "" +"To begin, have a sales order confirmed in the *Sales* app to which a " +"reinvoiced expense can be added. Or, create a new sales order from scratch. " +"To do that, navigate to the :menuselection:`Sales app --> New`. Doing so " +"reveals a blank quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:28 +msgid "" +"Then, add a :guilabel:`Customer`, and add a product to the :guilabel:`Order " +"Lines` tab, by clicking :guilabel:`Add a product`. Next, select a product " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:31 +msgid "Lastly, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"This is how a confirmed sales order looks in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:37 +msgid "With the sales order confirmed, it's time to create an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:39 +msgid "" +"To do that, navigate to the *Expenses* application, by going to " +":menuselection:`main Odoo dashboard --> Expenses`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:42 +msgid "" +"Then, from the *Expenses* dashboard, click :guilabel:`New` to reveal a blank" +" expenses form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A blank expenses form in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:48 +msgid "" +"On the expenses form, add a :guilabel:`Description` to easily reference the " +"expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:50 +msgid "" +"Then, in the :guilabel:`Category` field, select one of the following options" +" from the drop-down menu:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:53 +msgid "" +":guilabel:`Communication`: any form of communication related to a " +"project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:54 +msgid "" +":guilabel:`Others`: expense that doesn't fit into any other categories." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:55 +msgid ":guilabel:`Meals`: any form of meal costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:56 +msgid ":guilabel:`Gifts`: any form of gift costs related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:57 +msgid "" +":guilabel:`Mileage`: any form of mileage (gas) costs related to " +"project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:58 +msgid "" +":guilabel:`Travel \\& Accommodation`: any travel or accommodation costs " +"related to a project/order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:61 +msgid "" +"New expense categories can be created from an expense form, by clicking the " +":guilabel:`Category` field drop-down menu, selecting :guilabel:`View All`, " +"and clicking :guilabel:`New` from the :guilabel:`Search:Category` pop-up " +"window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:0 +msgid "" +"The Search:Category expenses pop-up window from a blank expenses form in " +"Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:69 +msgid "" +"For this sample workflow, which will reinvoice a customer for a brief hotel " +"stay, the :guilabel:`Category` for this example is :guilabel:`[TRANS \\& " +"ACC] Travel \\& Accommodation`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:73 +msgid "" +"The following example requires the *Sales*, *Accounting*, and *Expense* apps" +" to view/modify all the fields mentioned during the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:76 +msgid "" +"Beneath the :guilabel:`Category` field, enter in the amount to be expensed " +"in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:79 +msgid "" +"Next, designate if there are any :guilabel:`Included taxes` in the " +":guilabel:`Total`. If a preconfigured tax amount is selected from the " +":guilabel:`Included taxes` field, Odoo auto-calculates the taxed amount, " +"based on the amount entered in the :guilabel:`Total` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:83 +msgid "" +"Then, choose which :guilabel:`Employee` was responsible for the expense, and" +" choose an option in the :guilabel:`Paid By` field: :guilabel:`Employee (to " +"reimburse)` or :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:86 +msgid "" +"In this case, our employee paid for the hotel with their own money, so the " +":guilabel:`Employee (to reimburse)` option is chosen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:89 +msgid "" +"On the right-hand side of the expenses form, the option to add a " +":guilabel:`Bill Reference` is available. Beneath that, the auto-populated " +":guilabel:`Expense Date` and :guilabel:`Account` fields are available." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:94 +msgid "" +"The :guilabel:`Expense Date` and :guilabel:`Account` field can be modified, " +"if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:96 +msgid "" +"Next, in the :guilabel:`Customer to Reinvoice` field, click the blank field " +"to reveal a drop-down menu. From this drop-down menu, select the appropriate" +" sales order to which this expense should be attached. This field **must** " +"be filled, in order to reinvoice a customer for an expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:100 +msgid "" +"Lastly, the option to modify the :guilabel:`Analytic Distribution` and " +":guilabel:`Company` fields are available. These fields are *not* required to" +" complete a reinvoiced expense to a customer, but are available to modify, " +"if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:104 +msgid "" +"Also, at the bottom of the expense form, there is a :guilabel:`Notes...` " +"section, wherein any notes related to this expense can be added, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A filled out expenses form in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:111 +msgid "" +"At the top of the expense form, there are buttons to :guilabel:`Attach " +"Receipt`, :guilabel:`Create Report`, and :guilabel:`Split Expense`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:114 +msgid "" +"If there is a physical or digital receipt that should be attached to the " +"expense, click :guilabel:`Attach Receipt`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:117 +msgid "" +"If the cost of this expense needs to be split, click :guilabel:`Split " +"Expense`. This feature can be used for a number of reasons (spitting expense" +" with another employee, to accommodate different tax rates, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:121 +msgid "" +"If neither of these options are necessary, click :guilabel:`Create Report` " +"to lock in the expense report that was just configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:124 +msgid "" +"Doing so reveals an :guilabel:`Expense Report Summary` for the new expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "An expense report summary in the Odoo Expenses application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:130 +msgid "" +"Here, once the details related to the expense have been confirmed, click " +":guilabel:`Submit to Manager`. This sends the expense report to the " +"approving manager, who will review the expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:133 +msgid "" +"The manager in charge of reviewing and approving the expense will inspect " +"the details related to the expense, and if there are no issues, they will " +"click the :guilabel:`Approve` button — which *only* appears on the manager's" +" view of the :guilabel:`Expense Report Summary` that's been submitted to the" +" manager by the employee." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"An expense report summary that a manager will approve with an Approve " +"button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:142 +msgid "" +"Once approved, the buttons at the top of the :guilabel:`Expense Report " +"Summary` change once again. At this point, the buttons at the top of the " +":guilabel:`Expense Report Summary` are: :guilabel:`Post Journal Entries`, " +":guilabel:`Report in Next Payslip`, :guilabel:`Refuse`, and :guilabel:`Reset" +" to Draft`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"An expense report summary with post journal entries button at the top of the" +" form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:151 +msgid "" +"When the manager is satisfied with the :guilabel:`Expense Report Summary`, " +"they'll click :guilabel:`Post Journal Entries`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:154 +msgid "" +"Upon clicking :guilabel:`Post Journal Entries`, that button disappears, and " +"the :guilabel:`Analytic Distribution` column in the :guilabel:`Expense` tab " +"is filled with the sales order that was initially configured to the expense " +"in the :guilabel:`Customer to Reinvoice` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:159 +msgid "Reinvoice expense" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:161 +msgid "" +"With those steps completed, it's time to return to the sales order to " +"complete the reinvoice of the expense to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:164 +msgid "" +"To do that, navigate to :menuselection:`main Odoo dashboard --> Sales app`, " +"and select the appropriate sales order that should be reinvoiced for the " +"expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:167 +msgid "" +"On the sales form, the newly-configured expense is now in the " +":guilabel:`Order Lines` tab, with its :guilabel:`Delivered` column filled " +"in, and ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A sales order with the configured expense ready to be invoiced in the Order " +"Lines tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:174 +msgid "" +"After confirming the details of the expense, click :guilabel:`Create " +"Invoice` at the top of the sales order. When clicked, a :guilabel:`Create " +"invoices` pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A create invoices pop-up window that appears when the Create Invoice is " +"clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:181 +msgid "" +"From this pop-up window, leave the :guilabel:`Create Invoice` field on the " +"default :guilabel:`Regular invoice` option, and click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:184 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` showing *only* the " +"expense in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A customer invoice draft with the expense in the Invoice Lines tab of the " +"form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:191 +msgid "" +"If all the information related to the expense is correct, click " +":guilabel:`Confirm` to confirm the invoice. Doing so moves the status of the" +" invoice from :guilabel:`Draft` to :guilabel:`Posted`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:194 +msgid "" +"To send the invoice to the customer, click :guilabel:`Send \\& Print`. Doing" +" so reveals a :guilabel:`Send` pop-up window, with a preconfigured message " +"and PDF invoice in the body of the message. The message can be reviewed and " +"modified, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:198 +msgid "" +"Once ready, click :guilabel:`Send \\& Print` to send the invoice to the " +"customer. When clicked, the pop-up window disappears, and Odoo sends the " +"message/invoice to the customer. Additionally, a PDF of the invoice is " +"automatically downloaded for record-keeping and/or printing purposes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:202 +msgid "" +"Back on the :guilabel:`Customer Invoice`, click the :guilabel:`Register " +"Payment` button when the customer pays for the invoiced expense." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "" +"A customer invoice with the register payment button ready to be clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:209 +msgid "" +"When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment`" +" pop-up window appears. In this pop-up window, the necessary fields are " +"auto-populated with the correct information. After reviewing the " +"information, click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst-1 +msgid "A register payment pop-up window on a customer invoice in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:217 +msgid "" +"Once :guilabel:`Create Payment` is clicked, the pop-up window disappears, " +"and a green :guilabel:`In Payment` banner is in the upper-right corner of " +"the invoice, signifying this invoice is paid for in full. Thus, completing " +"the workflow." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:227 +#: ../../content/applications/sales/sales/invoicing/milestone.rst:236 +msgid ":doc:`time_materials`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/expense.rst:228 +msgid ":doc:`milestone`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:3 +msgid "Invoice based on delivered or ordered quantities" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:5 +msgid "" +"Different business policies might require different options for invoicing:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:7 +msgid "" +"The *Invoice what is ordered* rule is used as the default mode in Odoo " +"*Sales*, which means customers are invoiced once the sales order is " +"confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:9 +msgid "" +"The *Invoice what is delivered* rule invoices customers once the delivery is" +" done. This rule is often used for businesses that sell materials, liquids, " +"or food in large quantities. In these cases, the ordered quantity may differ" +" slightly from the delivered quantity, making it preferable to invoice the " +"quantity actually delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:14 +msgid "" +"Being able to have different invoicing options provides more flexibility." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:17 +msgid "Invoicing policy features" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:19 +msgid "" +"To activate the necessary invoicing policy features, go to " +":menuselection:`Sales app --> Configuration --> Settings`, and under the " +":guilabel:`Invoicing` heading, select an :guilabel:`Invoicing Policy` rule: " +":guilabel:`Invoice what is ordered` or :guilabel:`Invoice what is " +"delivered`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "Choosing an invoicing policy on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:29 +msgid "" +"If the :guilabel:`Invoice what is delivered` rule is chosen, it is **not** " +"possible to activate the :guilabel:`Automatic Invoice` feature, which " +"automatically generates invoices when an online payment is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:34 +msgid "Invoicing policy on product form" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:36 +msgid "" +"On any product page, via the :menuselection:`Sales app --> Products --> " +"Products dashboard`, locate the :guilabel:`Invoicing Policy` option located " +"under the :guilabel:`General Information` tab. It can be changed manually " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to change your invoicing policy on a product form on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:45 +msgid "Impact on sales flow" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:47 +msgid "" +"In Odoo *Sales*, the basic sales flow starts with the creation of a " +"quotation. Then, that quotation is sent to a customer. Next, it needs to be " +"confirmed, which turns the quotation into a sales order. This, in turn, " +"creates an invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:51 +msgid "" +"The following is a breakdown of how invoicing policy rules impact the " +"aforementioned sales flow:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:53 +msgid "" +":guilabel:`Invoice what is ordered`: No impact on the basic sales flow. An " +"invoice is created as soon as a sale is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:55 +msgid "" +":guilabel:`Invoice what is delivered`: Minor impact on sales flow, because " +"the delivered quantity needs to be manually entered on the sales order. Or, " +"the *Inventory* app can be installed and used to confirm the delivered " +"quantity before creating an invoice with the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:60 +msgid "" +"If a user attempts to create an invoice without validating the delivered " +"quantity, the following error message appears: :guilabel:`There is no " +"invoiceable line. If a product has a Delivered quantities invoicing policy, " +"please make sure that a quantity has been delivered.`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:0 +msgid "" +"If Delivered Quantities invoicing policy is chosen, ensure a quantity has " +"been delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:69 +msgid "" +"Once a quotation is confirmed, and the status changes from " +":guilabel:`Quotation sent` to :guilabel:`Sales order`, the delivered and " +"invoiced quantities are available to view, directly from the sales order. " +"This is true for both invoicing policy rule options." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst-1 +msgid "How to see your delivered and invoiced quantities on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:77 +msgid "" +"Odoo automatically adds the quantities to the invoice, both " +":guilabel:`Delivered` and :guilabel:`Invoiced`, even if it's a partial " +"delivery, when the quotation is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:80 +msgid "" +"Finally, there are a few different options to create an invoice: " +":guilabel:`Regular invoice`, :guilabel:`Down payment (percentage)` or " +":guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/invoicing_policy.rst:84 +msgid "" +"Be sure to check out the documentation explaining down payment options to " +"learn more: :doc:`/applications/sales/sales/invoicing/down_payment`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:3 +msgid "Invoice project milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:5 +msgid "" +"Invoicing based on project milestones can be used for expensive or large-" +"scale projects. The series of milestones in a project represent a clear " +"sequence of work that will inevitably result in the completion of a project " +"and/or contract." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:9 +msgid "" +"This method of invoicing ensures the company gets a consistent flow of money" +" throughout the lifetime of the project. Customers can closely monitor every" +" phase of the project's development as it happens, in addition to paying a " +"large bill in several installments, instead of all at once." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:14 +msgid "Create milestone products" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:16 +msgid "" +"In Odoo, each milestone of a project is considered as an individual product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:18 +msgid "" +"To create and/or configure products to work like this, first navigate to " +":menuselection:`Sales app --> Products --> Products`. Then, click on a " +"product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:22 +msgid "" +"The option to invoice based on milestones is only available for certain " +"product types." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:24 +msgid "" +"On the product form, under the :guilabel:`General Information` tab, the " +":guilabel:`Product Type` field *must* be set on any of the following " +"options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event " +"Booth`, or :guilabel:`Course`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The invoicing policy field drop-down menu with options on product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:32 +msgid "" +"With any of those :guilabel:`Product Type` options selected, choose " +":guilabel:`Based on Milestones` from the :guilabel:`Invoicing Policy` drop-" +"down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:39 +msgid "Beneath that is the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:41 +msgid "" +"To ensure workflows are as seamless as possible, it is recommended that an " +"option in the :guilabel:`Create on Order` field is selected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:45 +msgid "" +"Leaving it on the default :guilabel:`Nothing` option won't negatively affect" +" the desired workflow. However, a project *must* then be created directly " +"from a sales order form with that specific product. Once a project is " +"created *then* milestones and tasks can be created and configured." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:50 +msgid "" +"When the :guilabel:`Create on Order` default option of :guilabel:`Nothing` " +"is clicked, a drop-down menu is revealed with the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:53 +msgid "" +":guilabel:`Task`: Odoo creates a task related to this milestone product in " +"the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:55 +msgid "" +":guilabel:`Project \\& Task`: Odoo creates a project and task related to " +"this milestone product in the *Projects* app when this specific product is " +"ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:57 +msgid "" +":guilabel:`Project`: Odoo creates a project related to this milestone " +"product in the *Projects* app when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:60 +msgid "" +"When :guilabel:`Task` is selected, a :guilabel:`Project` field appears. In " +"this field, select to which existing project in the *Projects* app this " +"created task should be connected." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Project field appears when the Task option is selected in Create on " +"Order field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:67 +msgid "" +"When :guilabel:`Project \\& Task` or :guilabel:`Project` is selected, two " +"new fields appear: :guilabel:`Project Template` and :guilabel:`Workspace " +"Template`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Project template and workspace template fields that appear on milestone " +"product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:74 +msgid "" +"The :guilabel:`Project Template` field provides template options to use for " +"the project that will be created when this specific product is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:77 +msgid "" +"The :guilabel:`Workspace Template` field provides template options to use " +"for the workspace (for the *Documents* app, not the *Projects* app) that " +"will be automatically generated for the project when this specific product " +"is ordered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:82 +msgid "" +"For organizational purposes, click the :guilabel:`Sales` tab on the product " +"form, and enter a custom 'Milestone' related descriptor in the " +":guilabel:`Sales Description` field. This information appears in the " +":guilabel:`Description` column on the :guilabel:`Order Lines` tab of the " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:87 +msgid "" +"Or, directly edit/modify the :guilabel:`Description` field on the " +":guilabel:`Order Lines` tab of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:90 +msgid "This is *not* a requirement." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:93 +msgid "Invoice milestones" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:96 +msgid "" +"The following flow features a trio of milestone products that have " +":guilabel:`Service` set as their :guilabel:`Product Type`, and " +":guilabel:`Task` set on their :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:0 +msgid "" +"Product with Service \"Product Type\" and \"Task\" in the Create on Order " +"field on form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:104 +msgid "" +"Those tasks are then attached to a pre-existing :guilabel:`Project`, which, " +"in this case, is titled, :guilabel:`Rebranding Projects`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:107 +msgid "" +"To invoice milestones, create a sales order with the milestone product(s). " +"To do that, go to :menuselection:`Sales app --> New`. Doing so reveals a " +"blank quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:110 +msgid "" +"From this quotation form, add a :guilabel:`Customer`. Then, click " +":guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Next, add the " +"milestone product(s) to the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:113 +msgid "" +"Once the corresponding milestone product(s) have been added, click " +":guilabel:`Confirm` to confirm the order, which turns the quotation into a " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:116 +msgid "" +"When the order is confirmed, new smart buttons appear at the top of the " +"sales order based on what was selected in the :guilabel:`Create on Order` " +"field on the product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:119 +msgid "" +"From the sales order, click the :guilabel:`Milestones` smart button. Doing " +"so reveals a blank :guilabel:`Milestones` page. Click :guilabel:`New` to add" +" milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "Adding milestones to a sales order with milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:126 +msgid "" +"Enter a :guilabel:`Name` for the milestone. Next, apply it to the " +"corresponding :guilabel:`Sales Order Item`. Lastly, assign a " +":guilabel:`Deadline` to the milestone, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:129 +msgid "Repeat that process for all milestone sales order items." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:131 +msgid "" +"Then, return to the sales order, via the breadcrumbs. From the sales order, " +"click the :guilabel:`Tasks` smart button. Doing so reveals a " +":guilabel:`Tasks` page with a task for each sales order item with that " +"option designated in the :guilabel:`Create on Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"Sample tasks page accessed via the smart button from a sales order with " +"milestone products." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:139 +msgid "" +"To manually assign a configured milestone to a task, click the desired task," +" which reveals the task form. On the task form, select the appropriate " +"milestone to which this task should be connected, in the " +":guilabel:`Milestone` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The milestone field on the task form when dealing with milestone products in" +" Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:147 +msgid "Repeat this process for all milestone tasks." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:149 +msgid "" +"With those tasks properly configured, employees log in their progress as " +"they work on the task, in addition to adding any notes related to the task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:152 +msgid "" +"Then, when that task is complete, that means that milestone has been " +"reached. At that point, it is time to invoice that milestone." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:155 +msgid "" +"To invoice a milestone, first return to the sales order — either via the " +"breadcrumb links, or by navigating to :menuselection:`Sales app --> Orders " +"--> Orders` and picking the appropriate sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:159 +msgid "" +"Back on the sales order form, click the :guilabel:`Milestones` smart button," +" and check the box in the :guilabel:`Reached` column for that particular " +"task." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"What it looks like to mark a milestone as reached via the milestone smart " +"button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:166 +msgid "" +"Next, return to the sales order — either by clicking :guilabel:`View Sales " +"Order` on the :guilabel:`Milestones` page, or via the breadcrumb links." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:169 +msgid "" +"Back on the sales order, the line item for the milestone that's been reached" +" has its :guilabel:`Delivered` column filled. That's because the milestone " +"has been reached, and therefore delivered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"A milestone product that's been reached marked as delivered on the sales " +"order in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:177 +msgid "" +"Click :guilabel:`Create Invoice` in the upper-left corner. Doing so reveals " +"a :guilabel:`Create invoices` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The create invoices pop-up window that appears when create invoice button is" +" clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:184 +msgid "" +"On the :guilabel:`Create invoices` pop-up window, leave the " +":guilabel:`Create Invoice` option on the default :guilabel:`Regular Invoice`" +" selection, and click the :guilabel:`Create Draft Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:188 +msgid "" +"Upon clicking :guilabel:`Create Draft Invoice`, Odoo reveals the " +":guilabel:`Customer Invoice Draft`, *only* showing that reached milestone in" +" the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"A customer invoice draft showing only the milestone product that's been " +"reached." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:195 +msgid "" +"From this invoice page, click the :guilabel:`Confirm` button to confirm the " +"invoice. Then, when the customer has paid for this milestone, click " +":guilabel:`Register Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:198 +msgid "" +"When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment`" +" pop-up window appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Register Payment pop-up window that appears when Register Payment is " +"clicked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:204 +msgid "" +"On this pop-up window, confirm the accuracy of the auto-populated fields, " +"then click :guilabel:`Create Payment`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:207 +msgid "" +"When clicked, the pop-up window disappears, and Odoo returns to the invoice " +"for that milestone, which now has a green :guilabel:`In Payment` banner in " +"the upper-right corner. This banner signifies the invoice has been paid." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"An invoice with a milestone product that has been paid with an In Payment " +"banner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:215 +msgid "" +"Then, return to the sales order, via the breadcrumb links. Back on the sales" +" order, in the :guilabel:`Order Lines` tab, the reached milestone that's " +"been invoiced and paid for, now has its :guilabel:`Invoiced` column filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The Invoiced column of a milestone product that's been paid for is filled." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:223 +msgid "" +"There is also a new :guilabel:`Invoices` smart button at the top of the " +"sales order. Clicking that reveals all the invoices that are connected to " +"this sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst-1 +msgid "" +"The invoices smart button that appears at the top of a sales order with " +"milestones." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:230 +msgid "" +"Simply repeat the above process for each milestone as it is worked on, and " +"subsequently, completed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:232 +msgid "" +"Continue that process until the entire project has been completed, each " +"milestone has been invoiced, and the entire order has been paid for in full." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/milestone.rst:237 +msgid ":doc:`proforma`" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:3 +msgid "Pro-forma invoices" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:5 +msgid "" +"A *pro-forma invoice* is an abridged or estimated invoice sent in advance of" +" a delivery of goods. It notes the kind and quantity of goods, their value, " +"and other important information, such as weight and transportation charges." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:9 +msgid "" +"Pro-forma invoices are commonly used as preliminary invoices with a " +"quotation. They are also used during importation for customs purposes. They " +"differ from a normal invoice, in that they are *not* a demand (or request) " +"for payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:16 +msgid "" +"In order to utilize pro-forma invoices, the *Pro-Forma Invoice* feature " +"**must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:18 +msgid "" +"To enable this feature, navigate to :menuselection:`Sales app --> " +"Configuration --> Settings`, and in the :guilabel:`Quotations \\& Orders` " +"section, click the checkbox next to :guilabel:`Pro-Forma Invoice`. Then, " +"click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "The Pro-Forma Invoice feature setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:27 +msgid "Send pro-forma invoice" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:29 +msgid "" +"With the :guilabel:`Pro-Forma Invoice` feature activated, the option to send" +" a pro-forma invoice is now available on any quotation or sales order, via " +"the :guilabel:`Send Pro-Forma Invoice` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The Send Pro-Forma Invoice button on a typical sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:37 +msgid "" +"Pro-forma invoices can **not** be sent for a sales order or quotation if an " +"invoice for a down payment has already been sent, or for a recurring " +"subscription." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:40 +msgid "" +"In either case, the :guilabel:`Send Pro-Froma Invoice` button does **not** " +"appear." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:42 +msgid "" +"However, pro-forma invoices **can** be sent for services, event " +"registrations, courses, and/or new subscriptions. Pro-forma invoices are not" +" limited to physical, consumable, or storable goods." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:45 +msgid "" +"When the :guilabel:`Send Pro-Forma Invoice` button is clicked, a pop-up " +"window appears, from which an email can be sent." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:48 +msgid "" +"In the pop-up window, the :guilabel:`Recipients` field is auto-populated " +"with the customer from the sales order or quotation. The :guilabel:`Subject`" +" field and the body of the email can be modified, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:52 +msgid "" +"The pro-forma invoice is automatically added as an attachment to the email." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:54 +msgid "" +"When ready, click :guilabel:`Send`, and Odoo instantly sends the email, with" +" the attached pro-forma invoice, to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst-1 +msgid "" +"The email pop-up window that appears with pro-forma invoice attached in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:62 +msgid "" +"To preview what the pro-forma invoice looks like, click on the PDF at the " +"bottom of the email pop-up window *before* clicking :guilabel:`Send`. When " +"clicked, the pro-forma invoice is downloaded instantly. Open that PDF to " +"view (and review) the pro-forma invoice." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/proforma.rst:0 +msgid "Sample pro-forma invoice PDF from Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:3 +msgid "Invoicing based on time and materials" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:5 +msgid "" +"Invoicing based on time and/or materials is typically used when accurately " +"estimating the size of a project isn't possible, or when the requirements of" +" a project may change." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:8 +msgid "" +"This is different from a fixed-price contract, when a customer agrees to pay" +" a specified total for the fulfillment of the contract---no matter what " +"needs to be paid to the employees, sub-contractors, vendors, suppliers, and " +"so on." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:12 +msgid "" +"The Odoo *Sales* app can invoice for time and various other expenses (e.g. " +"transport, lodging), as well as purchases needed to fulfill an order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:16 +msgid "App and settings configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:18 +msgid "" +"First, in order to accurately keep track of the progress of a project, the " +"Odoo *Project* and *Accounting* apps **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:21 +msgid "" +"To install the *Project* app, navigate to :menuselection:`Odoo main " +"dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Project` app block, and click :guilabel:`Activate`. The page " +"automatically refreshes and returns to the main Odoo dashboard, where the " +"*Project* app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:26 +msgid "Repeat the same process to install the *Accounting* application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:28 +msgid "" +"After installation, click the :guilabel:`Accounting` app icon from the main " +"Odoo dashboard, and navigate to :menuselection:`Configuration --> Settings`." +" On the :guilabel:`Settings` page, scroll down to the :guilabel:`Analytics` " +"section, and ensure the box next to :guilabel:`Analytic Accounting` is " +"checked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How it looks to activate the Analytic Accounting setting in Odoo Accounting " +"Setting page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:37 +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:43 +msgid "Then, click :guilabel:`Save` to save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:39 +msgid "" +"Then, navigate to :menuselection:`Odoo main dashboard --> Project app --> " +"Configuration --> Settings`. On the :guilabel:`Settings` page, in the " +":guilabel:`Time Management` section, ensure the box beside the " +":guilabel:`Timesheets` feature is checked." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"What the Timesheets feature looks like on the Odoo Project settings page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:52 +msgid "Service product configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:54 +msgid "" +"With the *Timesheets* feature activated in the *Project* app, it is now " +"possible to invoice for time spent on a project, but **only** when the " +"following product configurations have been made." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:58 +msgid "" +"Invoicing for time spent on a project is **only** possible with products " +"that have *Service* set as the *Product Type* on their product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:61 +msgid "" +"To configure a service product, first navigate to :menuselection:`Sales app " +"--> Products --> Products`. On the :guilabel:`Products` page, select the " +"desired service product to be configured, or click :guilabel:`New` to create" +" a new product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:65 +msgid "" +"From the product form, in the :guilabel:`General Information` tab, set the " +":guilabel:`Product Type` to :guilabel:`Service`. Then, open the drop-down " +"menu in the :guilabel:`Invoicing Policy` field, and select :guilabel:`Based " +"on Timesheets`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:69 +msgid "" +"Next, from the :guilabel:`Create on Order` drop-down menu, select " +":guilabel:`Project \\& Task`. That setting indicates that, when a sales " +"order is created with this specific service product, a new project and task " +"is created in the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"The correct settings for Invoicing Policy and Create on Order fields for " +"service product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:78 +msgid "" +"The option :guilabel:`Task` can be chosen instead from the :guilabel:`Create" +" on Order` drop-down menu. If :guilabel:`Task` is chosen, select an existing" +" project that the task will appear in from :guilabel:`Project` field, which " +"only appears if :guilabel:`Task` is chosen in the :guilabel:`Create on " +"Order` field." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:84 +msgid "Add time spent to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:86 +msgid "" +"After properly configuring a service product with the correct *Invoicing " +"Policy* and *Create on Order* options, it is possible to add time spent to a" +" sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:89 +msgid "" +"To see that in action, navigate to :menuselection:`Sales app --> New` to " +"open a blank quotation form. Then, proceed to add a :guilabel:`Customer`, " +"and in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and" +" select the properly :ref:`configured service product " +"<sales/invoicing/configured-service-product>` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:94 +msgid "Next, click :guilabel:`Confirm` to confirm the order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:96 +msgid "" +"After confirming the sales order, two smart buttons appear at the top of the" +" order form: :guilabel:`Projects` and :guilabel:`Tasks`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How the Projects and Tasks smart buttons look on a Sales Order in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:103 +msgid "" +"If the :guilabel:`Projects` smart button is clicked, it reveals the specific" +" project related to this sales order. If the :guilabel:`Tasks` smart button " +"is clicked, it reveals the specific project task related to this sales " +"order. Both are also accessible in the *Project* app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:107 +msgid "" +"In order to add time spent on a sales order, click the :guilabel:`Tasks` " +"smart button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:109 +msgid "" +"On the task form, select the :guilabel:`Timesheets` tab. From the " +":guilabel:`Timesheets` tab, employees can be assigned to work on the " +"project, and the time they spend working on the task can be added by the " +"employees or by the person who created the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:113 +msgid "" +"To add an employee, and the time spent working on the task, click " +":guilabel:`Add a line` in the :guilabel:`Timesheets` tab. Then, select the " +"appropriate :guilabel:`Date` and :guilabel:`Employee`. There is also the " +"option to add a brief description of the work done during this time in the " +":guilabel:`Description` column, but it's not required." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:118 +msgid "" +"Lastly, enter the amount of time worked on the task in the :guilabel:`Hours " +"Spent` column, and click away to complete that line in the " +":guilabel:`Timesheets` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:122 +msgid "" +"The time entered in the :guilabel:`Hours Spent` column is immediately " +"reflected in the :guilabel:`Allocated Time` field (located near the top of " +"the task form) as a percentage, which reflects how much of the total " +"allocated work hours have been done so far." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:126 +msgid "" +"That same information is found as numerical hours in the :guilabel:`Hours " +"Spent` and :guilabel:`Remaining Hours` fields, located at the bottom of the " +":guilabel:`Timesheets` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "" +"How the Timesheets tab appears on a task form in Odoo Sales and Odoo " +"Project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:133 +msgid "" +"Repeat this process for however many employees and hours have been worked on" +" the project." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:136 +msgid "Invoice time spent" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:138 +msgid "" +"Once all the necessary employees and time spent have been added to the " +"project task, return to the sales order to invoice the customer for those " +"hours. To do that, either click the :guilabel:`Sales Order` smart button at " +"the top of the task form, or return to the sales order via the breadcrumb " +"links, located in the upper-left of the screen." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:143 +msgid "" +"Back on the sales order form, the time that was added to the task is " +"reflected in the :guilabel:`Order Lines` tab (in the :guilabel:`Delivered` " +"column) and in the new :guilabel:`Recorded Hours` smart button at the top of" +" the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:147 +msgid "" +"To invoice the customer for time spent on the project, click " +":guilabel:`Create Invoice`, and select :guilabel:`Regular invoice` from the " +":guilabel:`Create invoices` pop-up window. Then, click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:151 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft`, clearly showing all " +"the work that's been done in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:155 +msgid "" +"Pay attention to the :guilabel:`Analytic Distribution` column in the " +":guilabel:`Customer Invoice`, as that information is necessary to ensure " +"other time/material invoicing tasks are completed properly and accurately." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "Invoice draft showing time spent on sales order in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:163 +msgid "" +"Click :guilabel:`Confirm` to confirm the invoice and continue with the " +"invoicing process." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:169 +msgid "Expenses configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:171 +msgid "" +"In order to track and invoice expenses related to a sales order, the Odoo " +"*Expenses* app **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:174 +msgid "" +"To install the *Expenses* app, navigate to :menuselection:`Odoo main " +"dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Expenses` app block, and click :guilabel:`Activate`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:178 +msgid "" +"The page automatically refreshes and returns to the main Odoo dashboard, " +"where the :guilabel:`Expenses` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:184 +msgid "Add expenses to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:186 +msgid "" +"To add an expense to a sales order, first navigate to the " +":menuselection:`Expenses` app. Then, from the main *Expenses* dashboard, " +"click :guilabel:`New`, which reveals a blank expense form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:189 +msgid "" +"On the expense form, add a :guilabel:`Description` of the expense (e.g. " +"`Hotel Stay`, `Plane Ticket`). Next, in the :guilabel:`Category` field, " +"select the appropriate option from the drop-down menu (e.g. " +":guilabel:`Meals`, :guilabel:`Miles`, :guilabel:`Travel \\& Accommodation`)." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:194 +msgid "" +"Expense categories can be added and modified by navigating to " +":menuselection:`Expenses app --> Configuration --> Expense Categories`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:197 +msgid "" +"Then, enter the total amount of the expense in the :guilabel:`Total` field, " +"as well as any :guilabel:`Included Taxes` that may apply. Next, ensure that " +"the correct :guilabel:`Employee` is selected, and designate who paid for the" +" expense in the :guilabel:`Paid By` field: the :guilabel:`Employee (to " +"reimburse)` or the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:202 +msgid "" +"Next, in the :guilabel:`Customer to Reinvoice` field, select the appropriate" +" sales order from the drop-down menu. Then, select that same sales order " +"information from the :guilabel:`Analytic Distribution` field, as well." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:207 +msgid "" +"The :guilabel:`Analytic Distribution` field will **only** have the " +"corresponding sales order as an option if the sales order contains a service" +" product that is billed based on *Timesheets*, *Milestones*, or *Delivered " +"Quantities*." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to properly fill out an expense form that's attached to a sales order in" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:215 +msgid "" +"If there are any receipts that should be uploaded and attached to the " +"expense, click the :guilabel:`Attach Receipt` button, and upload the " +"necessary documents to the expense. This is **not** required, but it may " +"affect whether or not an expense is approved." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:219 +msgid "" +"When all the information has been entered, click :guilabel:`Create Report` " +"to create an expense report detailing all the expense information that was " +"just entered." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "How an Expense Report Summary looks in Odoo Expenses." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:226 +msgid "" +"Then, there's the option to :guilabel:`Submit to Manager` for approval. Once" +" approved, the :guilabel:`Report in Next Payslip` appears." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:229 +msgid "" +"To showcase a complete flow in this example, select :guilabel:`Submit to " +"Manager`. Then, the manager would click :guilabel:`Approve` to approve this " +"expense, and click :guilabel:`Post Journal Entries` to post this expense to " +"the accounting journal." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:234 +msgid "Invoice expenses" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:236 +msgid "" +"To invoice a customer for an :ref:`expense on a sales order " +"<sales/invoicing/add-expenses-sales-order>`, navigate to the related sales " +"order, either from the :menuselection:`Sales` app or from the expense report" +" in the :menuselection:`Expenses` app. From the expense report, click the " +":guilabel:`Sales Orders` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:241 +msgid "" +"If the expense report was linked to the sales order, the newly-configured " +"expense now has its own line in the :guilabel:`Order Lines` tab, and can be " +"invoiced to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"An expense appearing on Order Lines tab of a Sales Order in Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:248 +msgid "" +"To invoice the customer for the expense on the sales order, click " +":guilabel:`Create Invoice`, select :guilabel:`Regular Invoice` from the " +":guilabel:`Create invoices` pop-up window, then click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:252 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` for the expense. Then," +" the invoicing process can be completed as usual." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Sample customer invoice for an expense generated from a sales order in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:260 +msgid "Purchase configuration" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:262 +msgid "" +"In order to invoice a customer for purchases made on a sales order, the " +"*Purchase* application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:265 +msgid "" +"To install the *Purchase* application, navigate to :menuselection:`Odoo main" +" dashboard --> Apps`. Then, on the :guilabel:`Apps` page, locate the " +":guilabel:`Purchase` app block, and click :guilabel:`Activate`. The page " +"automatically refreshes and returns to the main Odoo dashboard, where the " +":guilabel:`Purchase` app is now available to access." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:273 +msgid "Add purchase to sales order" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:275 +msgid "" +"To add a purchase to a sales order, a purchase order must first be created. " +"To create a purchase order, navigate to :menuselection:`Purchase app --> " +"New` to reveal a blank purchase order form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:278 +msgid "" +"First, add a :guilabel:`Vendor` to the purchase order. Then, under the " +":guilabel:`Products` tab, click the :guilabel:`extra column options` drop-" +"down menu, represented by two horizontal lines with dots on them, located to" +" the far-right of the column headers. From that drop-down menu, select " +":guilabel:`Analytic Distribution`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to add analytic distribution column on purchase order form in Odoo " +"Purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:287 +msgid "" +"After adding the :guilabel:`Analytic Distribution` column to the headers on " +"the :guilabel:`Products` tab of the purchase order form, proceed to add the " +"product(s) to the purchase order. To do that, click :guilabel:`Add a " +"product`, and select the desired product from the drop-down menu. Repeat for" +" all the products to add." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:293 +msgid "" +"In order for a purchase to be properly invoiced on a sales order, the " +"product on the purchase order **must** be marked as :guilabel:`Can be " +"Expensed`, have an :guilabel:`Invoicing Policy` set to :guilabel:`Delivered " +"quantities`, and have the :guilabel:`At cost` option selected in the " +":guilabel:`Re-Invoice Expenses` field on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:0 +msgid "" +"Product settings for a purchase order to be invoiced on a sales order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:302 +msgid "" +"Then, select the appropriate :guilabel:`Analytic Distribution` associated " +"with the sales order to which this purchase order is related. To do that, " +"click the empty :guilabel:`Analytic Distribution` field to reveal an " +":guilabel:`Analytic` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:306 +msgid "" +"Then, from the :guilabel:`Departments` drop-down menu, select the analytic " +"distribution associated with the desired sales order to be invoiced for the " +"purchase." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"How to select the Analytic Distribution department from a purchase order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:313 +msgid "" +"Once all the information is entered in the :guilabel:`Products` tab of the " +"purchase order, confirm the order by clicking :guilabel:`Confirm Order`. " +"Then, click :guilabel:`Receive Products` when the products have been " +"received. This creates a receipt form." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:318 +msgid "" +"If any serial/lot numbers must be entered before validating the receipt of " +"products, then on the receipt form, click the :guilabel:`details` icon " +"represented by four horizontal lines located to the far-right of the product" +" line." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:322 +msgid "" +"This reveals a :guilabel:`Detailed Operations` tab, in which the necessary " +":guilabel:`Lot/Serial Number(s)` and :guilabel:`Done` quantity can be added." +" When ready, click :guilabel:`Confirm` to confirm the data." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:326 +msgid "Then, click :guilabel:`Validate` to validate the purchase order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:328 +msgid "" +"Next, return to the purchase order, via the breadcrumb links at the top of " +"the page, and click :guilabel:`Create Bill` to create a vendor bill that can" +" be invoiced to the customer on the attached sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Vendor bill draft for a purchase order to be invoiced to a customer in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:337 +msgid "" +"Make sure to enter a :guilabel:`Bill Date` on the :guilabel:`Vendor Bill " +"Draft` before confirming. If a :guilabel:`Bill Date` is *not* entered, an " +"error window appears, requesting that information to be entered before " +"confirmation can occur." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:341 +msgid "" +"Then, click :guilabel:`Confirm` to confirm the vendor bill, which is then " +"automatically added to the sales order, where it can be invoiced directly to" +" the customer attached to it." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:345 +msgid "Invoice purchase" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:347 +msgid "" +"To invoice a customer for a purchase on a sales order, first :ref:`add the " +"purchase to the sales order <sales/invoicing/add-purchase-to-sales-order>`, " +"then navigate to the desired sales order in the :menuselection:`Sales` app." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:351 +msgid "" +"On the sales order that was attached to the purchase order, the purchased " +"product now has its own product line under the :guilabel:`Order Lines` tab, " +"and it is ready to be invoiced." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Purchase order product on sales order to be invoiced to customer via Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:358 +msgid "" +"To invoice the customer for the purchase, simply click :guilabel:`Create " +"Invoice`, select :guilabel:`Regular Invoice` from the :guilabel:`Create " +"invoices` pop-up window, then click :guilabel:`Create Draft Invoice`." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:362 +msgid "" +"Doing so reveals a :guilabel:`Customer Invoice Draft` with the newly-added " +"purchase order product in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst-1 +msgid "" +"Customer invoice draft with purchase product attached to sales order in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/time_materials.rst:369 +msgid "" +"To complete the invoicing process, click :guilabel:`Confirm` to confirm the " +"invoice, and then click :guilabel:`Register Payment` in the " +":guilabel:`Register Payment` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices.rst:5 +msgid "Products & Prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:3 +msgid "Use eWallets and gift cards" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:5 +msgid "" +"With Odoo, customers can use **eWallets** and **gift cards** for online and " +"in-store shopping." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:7 +msgid "" +"To enable eWallets and gift cards for eCommerce and Point of Sale (PoS), " +"first enable :guilabel:`Discounts, Loyalty & Gift Card` under " +":menuselection:`Sales app --> Configuration --> Settings --> Pricing " +"section`. Once enabled, go to :menuselection:`Sales app --> Products --> " +"Gift cards & eWallet` and :guilabel:`Create` a new eWallet or gift card " +"program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:13 +msgid "eWallets" +msgstr "eWallets" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:15 +msgid "" +"eWallets allow customers to save credits on their online account and use " +"these credits as a payment method when buying items in an online store or a " +"brick-and-mortar store. eWallets can also be used to centralize multiple " +":ref:`gift cards <ewallet_gift/gift-cards>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:19 +msgid "" +"Before creating an eWallet program, it is necessary to create an eWallet " +"**top-up** product. Top-ups are pre-defined digital credit values added to " +"an eWallet in exchange for its equivalent in real currency. These credits " +"can then be used as a payment method in the eCommerce shop or :abbr:`PoS " +"(Point of Sale)`. Top-up values can be of different amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:25 +msgid "" +"A $50 top-up can be bought for $50, and adds that same amount of credits to " +"the eWallet." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:27 +msgid "" +"To create a top-up product, go to :menuselection:`Sales app --> Products -->" +" Products` and :guilabel:`Create` a new product. On the product template, " +"configure the options as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:30 +msgid "" +":guilabel:`Product Name`: enter a name for the top-up product (for example, " +"`$50 Top-Up`)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:31 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:92 +msgid ":guilabel:`Can be Sold`: enabled" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:32 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:93 +msgid ":guilabel:`Product Type`: select :guilabel:`Service`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:33 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:94 +msgid ":guilabel:`Invoicing Policy`: select :guilabel:`Prepaid/Fixed Price`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:34 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:95 +msgid ":guilabel:`Create on Order`: select :guilabel:`Nothing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:35 +msgid ":guilabel:`Sales Price`: enter the amount of the top-up" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:38 +msgid "" +"In order to have eWallet top-ups of different amounts, create multiple top-" +"up products and modify the :guilabel:`Sales Price` accordingly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:41 +msgid "" +"Once the top-up is created, go to :menuselection:`Sales app --> Products -->" +" Gift cards & eWallet` to :guilabel:`Create` an eWallet program. The " +"following configuration options are available:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:44 +msgid ":guilabel:`Program Name`: enter a name for the eWallet program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:45 +msgid ":guilabel:`Program Type`: select :guilabel:`eWallet`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:46 +msgid "" +":guilabel:`eWallet Products`: select the eWallet top-up created earlier. " +"Repeat the process if you created top-ups of different amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:48 +msgid "" +":guilabel:`Email template`: select the email template used for the email " +"sent to the customer. To create a new template, click on the field, select " +":guilabel:`Search More`, and then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:51 +msgid "" +":guilabel:`Currency`: select the currency to use for the eWallet program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:52 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:115 +msgid "" +":guilabel:`Company`: select the company for which the program is valid and " +"available" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:53 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:116 +msgid "" +":guilabel:`Available On`: select the applications on which the program is " +"valid and available" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:54 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:117 +msgid "" +":guilabel:`Website`: select the website on which the program is valid and " +"available. Leave this field empty to include all websites." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:56 +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:119 +msgid "" +":guilabel:`Point of Sale`: select the :abbr:`PoS (Point of Sale)` in which " +"the program is valid and available. Leave this field empty to include all " +":abbr:`PoS (Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "eWallet program configuration page" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:63 +msgid "" +"Once the program is configured, click the :guilabel:`Generate eWallet` " +"button in the upper-left corner to generate eWallets. eWallets can be " +"generated based on :guilabel:`Customers` and/or :guilabel:`Customer Tags`. " +"The quantity is automatically adapted according to the :guilabel:`Customers`" +" and :guilabel:`Customer Tags` selected. Then, set the :guilabel:`eWallet " +"value`. Finally, set the :guilabel:`Valid Until` period if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:69 +msgid "" +"Generated eWallets can be accessed through the :guilabel:`eWallets` smart " +"button in the upper-right corner. From there, :guilabel:`Send` or " +":guilabel:`Share` the eWallets via email or a URL link." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "eWallets send and share buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:76 +msgid "" +"Click on an eWallet to change the :guilabel:`Expiration Date`, " +":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of an " +"eWallet *cannot* be changed, deleted, or duplicated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:82 +msgid "Gift cards" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:84 +msgid "" +"Gift cards can be purchased by customers, and in turn used as a payment " +"method upon checkout at an eCommerce shop or :abbr:`PoS (Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:87 +msgid "" +"Before creating a new gift card program, it is necessary to first create " +"gift cards as products. To do so, go to :menuselection:`Sales app --> " +"Products --> Products` and :guilabel:`Create` a product. On the product " +"template, configure the options as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:91 +msgid ":guilabel:`Product Name`: enter a name for the gift card product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:96 +msgid ":guilabel:`Sales Price`: enter the amount of the gift card" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:99 +msgid "" +"In order to have gift cards of different amounts, create multiple gift card " +"products and modify the :guilabel:`Sales Price` accordingly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:102 +msgid "" +"Once the gift card product is created, go to :menuselection:`Sales app --> " +"Products --> Gift cards & eWallet` to :guilabel:`Create` a gift card " +"program. The following configuration options are available:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:106 +msgid ":guilabel:`Program Name`: enter a name for the gift card program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:107 +msgid ":guilabel:`Program Type`: select :guilabel:`Gift Card`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:108 +msgid "" +":guilabel:`Gift Card Products`: select the gift card product created " +"earlier. Repeat the process if you created gift card products of different " +"amounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:110 +msgid "" +":guilabel:`Email template`: select the default :guilabel:`Gift Card: Gift " +"Card Information` template, or create a new template by clicking on the " +"field, selecting :guilabel:`Search More`, and then clicking " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:113 +msgid ":guilabel:`Print Report`: select :guilabel:`Gift Card`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:114 +msgid "" +":guilabel:`Currency`: select the currency to use for the gift card program" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "Gift card program configuration page" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:126 +msgid "" +"Once the program is configured, click the :guilabel:`Generate Gift Cards` " +"button in the upper-left corner to generate gift cards. Gift cards can be " +"generated either for :guilabel:`Anonymous Customers` or :guilabel:`Selected " +"Customers`. Set the :guilabel:`Quantity to generate` for " +":guilabel:`Anonymous Customers`, or select the :guilabel:`Customers` and/or " +":guilabel:`Customer Tags` for :guilabel:`Selected Customers`. Then, set the " +":guilabel:`Gift Card value`. Finally, set the :guilabel:`Valid Until` period" +" if applicable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:133 +msgid "" +"Generated gift cards can be accessed through the :guilabel:`Gift Cards` " +"smart button in the upper-right corner. From there, :guilabel:`Send` or " +":guilabel:`Share` the gift cards via email or a URL link." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst-1 +msgid "Gift cards send and share buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/ewallets_giftcards.rst:141 +msgid "" +"Click on a gift card to change the :guilabel:`Expiration Date`, " +":guilabel:`Partner`, or :guilabel:`Balance`. The :guilabel:`Code` of a gift " +"card *cannot* be changed, deleted, or duplicated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:3 +msgid "Discount and loyalty programs" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:5 +msgid "" +"The Odoo *Sales*, *eCommerce*, and *Point of Sale* applications allow users " +"to create discount and loyalty programs that customers can use for online " +"and in-store shopping. These programs offer more varied, public, and time-" +"sensitive pricing options than :doc:`pricelists " +"</applications/sales/sales/products_prices/prices/pricing>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:11 +msgid "Configure the settings" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:13 +msgid "" +"To begin using discount and loyalty programs, navigate to " +":menuselection:`Sales --> Configuration --> Settings`. Under the " +":guilabel:`Pricing` heading, activate the :guilabel:`Discounts, Loyalty & " +"Gift Card` setting by checking the box next to the feature. Finally, click " +":guilabel:`Save` to save the changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:19 +msgid "Configure discount and loyalty programs" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:21 +msgid "" +"To create discount and loyalty programs, go to :menuselection:`Sales --> " +"Products --> Discount & Loyalty`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:24 +msgid "" +"If no discount or loyalty programs have been created yet, Odoo provides a " +"choice of templates to help create the first program. Choose one of the " +"template cards, or click :guilabel:`New` to create a new program from " +"scratch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:28 +msgid "" +"Or, if there are already existing programs, select an existing program to " +"edit it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Discount and loyalty program template cards." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:35 +msgid "" +"Templates only appear when no programs have been created, and they disappear" +" once the first program is created." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:38 +msgid "Creating or editing a program opens the program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:40 +msgid "The program form contains the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:42 +msgid "" +":guilabel:`Program Name`: Enter the name of the program. The program name is" +" *not* visible to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:44 +msgid "" +":guilabel:`Program Type`: Select the desired :ref:`program type " +"<sales/pricing_management/program-types>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:46 +msgid ":guilabel:`Currency`: Select the currency used for the program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:47 +msgid "" +":guilabel:`Points Unit`: Enter the name of the points used for the " +":guilabel:`Loyalty Cards` program (e.g. `Loyalty Points`). The points unit " +"name *is* visible to the customer. This field is only available when the " +":guilabel:`Program Type` is set to :guilabel:`Loyalty Cards`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:50 +msgid "" +":guilabel:`Validity`: Select the date until which the program is valid. " +"Leave this field blank for no end date, meaning the program is always valid " +"and does not expire." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:52 +msgid "" +":guilabel:`Limit Usage`: Check this box and enter a number to limit the " +"number of times the program can be used during the :guilabel:`Validity` " +"period." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:54 +msgid "" +":guilabel:`Company`: In the case of multiple companies, choose the company " +"for which the program is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:56 +msgid "" +":guilabel:`Available On`: Select the app(s) on which the program is " +"available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:57 +msgid "" +":guilabel:`Website`: Select the website(s) on which the program is " +"available. Leave this field blank to make it available on all websites." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:59 +msgid "" +":guilabel:`Point of Sale`: Select the point(s) of sale at which the program " +"is available. Leave this field blank to make it available at all :abbr:`PoS " +"(Point of Sale)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Program options on the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:67 +msgid "" +"The options available on the program form vary depending on the " +":ref:`Program Type <sales/pricing_management/program-types>` selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:70 +msgid "" +"All of the existing cards, codes, coupons, etc. that have been generated for" +" the program are accessible through the smart button located in the upper-" +"right corner of the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Program items smart button on the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:80 +msgid "Program types" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:82 +msgid "" +"The different :guilabel:`Program Types` available on the program form are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:84 +msgid "" +":guilabel:`Coupons`: Generate and share single-use coupon codes that grant " +"immediate access to rewards." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:86 +msgid "" +":guilabel:`Next Order Coupons`: Generate and share single-use coupon codes " +"that grant access to rewards on the customer's next order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:88 +msgid "" +":guilabel:`Loyalty Cards`: When making purchases, the customer accumulates " +"points to exchange for rewards on future orders." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:90 +msgid "" +":guilabel:`Promotions`: Set conditional rules for ordering products, which, " +"when fulfilled, grant access to rewards for the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:92 +msgid "" +":guilabel:`Discount Code`: Set codes which, when entered upon checkout, " +"grant discounts to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:94 +msgid "" +":guilabel:`Buy X Get Y`: For every X item bought, the customer is granted 1 " +"credit. After accumulating a specified amount of credits, the customer can " +"trade them in to receive Y item." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:98 +msgid "Conditional rules" +msgstr "กฎแบบมีเงื่อนไข" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:100 +msgid "" +"Next, configure the :guilabel:`Conditional rules` that determine when the " +"program applies to a customer's order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:103 +msgid "" +"In the :guilabel:`Rules & Rewards` tab, click :guilabel:`Add` next to " +":guilabel:`Conditional rules` to add *conditions* to the program. This " +"reveals a :guilabel:`Create Conditional rules` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Rules & Rewards tab of the loyalty program form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:112 +msgid "" +"The options for :guilabel:`Conditional rules` vary depending on the selected" +" :ref:`Program Type <sales/pricing_management/program-types>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:115 +msgid "The following options are available for configuring conditional rules:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:117 +msgid "" +":guilabel:`Discount Code`: Enter a custom code to be used for the " +":guilabel:`Discount Code` program, or use the default one generated by Odoo." +" This field is only available when the :guilabel:`Program Type` is set to " +":guilabel:`Discount Code`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:120 +msgid "" +":guilabel:`Minimum Quantity`: Enter the minimum number of products that must" +" be purchased in order to access the reward. Set the minimum quantity to at " +"least `1` to ensure that the customer must make a purchase in order to " +"access the reward." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:123 +msgid "" +":guilabel:`Minimum Purchase`: Enter the minimum amount (in currency), with " +":guilabel:`tax Included` or :guilabel:`tax Excluded`, that must be spent in " +"order to access the reward. If both a minimum quantity *and* minimum " +"purchase amount are entered, then the customer's order must meet both " +"conditions." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:127 +msgid "" +":guilabel:`Products`: Select the specific product(s) for which the program " +"applies. Leave this field blank to apply it to all products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:129 +msgid "" +":guilabel:`Categories`: Select the category of products for which the " +"program applies. Choose :guilabel:`All` to apply it to all product " +"categories." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:131 +msgid "" +":guilabel:`Product Tag:` Select a tag to apply the program to products with " +"that specific tag." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:132 +msgid "" +":guilabel:`Grant`: Enter the number of points the customer earns " +":guilabel:`per order`, :guilabel:`per currency spent`, or :guilabel:`per " +"unit paid` (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get Y` " +"programs)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "" +"Conditional rules configuration window for a discount or loyalty program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:140 +msgid "" +"Click :guilabel:`Save & Close` to save the rule and close the pop-up window," +" or click :guilabel:`Save & New` to save the rule and immediately create a " +"new one." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:144 +msgid "Rewards" +msgstr "รางวัล" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:146 +msgid "" +"In the :guilabel:`Rules & Rewards` tab of the program form, click " +":guilabel:`Add` next to :guilabel:`Rewards` to add *rewards* to the program." +" This reveals a :guilabel:`Create Rewards` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:151 +msgid "" +"The options for :guilabel:`Rewards` vary depending on the selected " +":ref:`Program Type <sales/pricing_management/program-types>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:154 +msgid "The following options are available for configuring rewards:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:156 +msgid "" +":guilabel:`Reward Type`: Select the reward type among :guilabel:`Free " +"Product`, :guilabel:`Discount`, and :guilabel:`Free Shipping`. The other " +"options for reward configuration depend on the :guilabel:`Reward Type` " +"selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:160 +msgid ":guilabel:`Free Product`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:162 +msgid "" +":guilabel:`Quantity Rewarded`: Select the number of free products rewarded " +"to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:163 +msgid "" +":guilabel:`Product`: Select the product given for free as a reward. Only one" +" product can be selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:165 +msgid "" +":guilabel:`Product Tag`: Select a tag to further specify the free product " +"eligible for the reward." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:168 +msgid ":guilabel:`Discount`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:170 +msgid "" +":guilabel:`Discount`: Enter the discounted amount in either " +":guilabel:`percentage`, :guilabel:`currency per point`, or " +":guilabel:`currency per order`. Then, select whether the discount applies to" +" the entire :guilabel:`Order`, only the :guilabel:`Cheapest Product` on the " +"order, or only :guilabel:`Specific Products`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:174 +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:179 +msgid "" +":guilabel:`Max Discount`: Enter the maximum amount (in currency) that this " +"reward may grant as a discount. Leave this field at `0` for no limit." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:177 +msgid ":guilabel:`Free Shipping`:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:182 +msgid "" +":guilabel:`In exchange of`: Enter the number of points required to exchange " +"for the reward (for the :guilabel:`Loyalty Cards` and :guilabel:`Buy X Get " +"Y` programs)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst:184 +msgid "" +":guilabel:`Description on order`: Enter the description of the reward, which" +" is displayed to the customer upon checkout." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/loyalty_discount.rst-1 +msgid "Rewards configuration window for a discount or loyalty program." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices.rst:5 +msgid "Manage your pricing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:3 +msgid "Foreign currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:5 +msgid "" +"With Odoo, pricelists can be used to manage prices in a number of foreign " +"currencies. Specifically, Odoo has the ability to work with 167 total " +"currencies." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:9 +msgid "" +"In order to use multiple currencies in Odoo *Sales*, the *Accounting* " +"application **must** be installed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:15 +msgid "" +"Once the *Accounting* app has been installed, foreign currencies can be " +"added to the database. Navigate to :menuselection:`Accounting app --> " +"Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, " +"and locate the :guilabel:`Main Currency` setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "" +"How the main currency feature appears on settings page in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:23 +msgid "" +"Odoo automatically sets the main currency as the currency of the country the" +" company is based in." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:25 +msgid "" +"To change the main currency of the company, select the drop-down menu in the" +" :guilabel:`Currency` field, select the desired currency, and be sure to " +":guilabel:`Save` the changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:29 +msgid "" +"To ensure currency rates are updated automatically, enable the *automatic " +"currency rates* feature on the *Accounting* settings page " +"(:menuselection:`Accounting app --> Configuration --> Settings --> " +"Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:37 +msgid "" +"Click the checkbox beside the :guilabel:`Automatic Currency Rates` feature, " +"choose a designated bank to get the currency rates from in the " +":guilabel:`Service` field drop-down menu, and select an :guilabel:`Interval`" +" of time for the updates to take place. Then determine when the date of the " +":guilabel:`Next Run` should be." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:42 +msgid "" +"To instantly update the currency rates, click the :guilabel:`🔁 (circular " +"arrows)` icon, located to the right of the :guilabel:`Next Run` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:45 +msgid "" +"When all configurations are complete, be sure to :guilabel:`Save` all " +"changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:48 +msgid "" +"All payment methods **must** be in the same currency as the sales journal, " +"or the company currency, if the company currency is not set. If it is not " +"the same, a :guilabel:`Validation Error` message appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:53 +msgid "View, edit, and add currencies" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:55 +msgid "" +"To view, edit, and add currencies to the database, making them available on " +"pricelists and on the :guilabel:`Main Currency` drop-down menu, click the " +":guilabel:`Currencies` link, located beneath the :guilabel:`Currency` field " +"on the :menuselection:`Accounting app --> Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:59 +msgid "" +"When the :guilabel:`Currencies` link is clicked, a separate " +":guilabel:`Currencies` page is revealed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How the main currencies page appears in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:65 +msgid "" +"On this page, Odoo provides a master list of 167 global currencies. Each row" +" shows the corresponding :guilabel:`Currency`, :guilabel:`Symbol`, " +":guilabel:`Name`, date of the :guilabel:`Last Update`, and " +":guilabel:`Current Rate` (compared to the default currency of the country in" +" which the company is based)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:70 +msgid "" +"To the far right, there are two columns, which can be toggled on or off:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:72 +msgid "" +":guilabel:`Use on eBay`: this currency can be used with the connected eBay " +"account (if applicable)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:74 +msgid "" +":guilabel:`Active`: this currency is activated, which means it can be added " +"to a pricelist, or used as the main currency of the company, if desired (via" +" :menuselection:`Accounting app --> Configuration --> Settings --> " +"Currencies section`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:79 +msgid "" +"By default, all the :guilabel:`Active` currency options are at the top of " +"the list." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:82 +msgid "" +"It is recommended that *at least* one pricelist is created per " +":guilabel:`Active` currency. See :doc:`./pricing` to learn more about " +"pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:85 +msgid "" +"To toggle options on/off, click the toggle switch in the row for the " +"corresponding column. When *on* the color of the switch is green. When " +"*off*, the color of the switch is grey." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:89 +msgid "Currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:91 +msgid "" +"To edit any currency on the :guilabel:`Currencies` page, click the desired " +"currency to reveal the detail form for that specific currency, and proceed " +"to make any necessary changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:98 +msgid "" +"On the currency detail form, the relevant currency code appears in the " +":guilabel:`Currency` field. Beneath that, the name for the currency is in " +"the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:101 +msgid "" +"Then, toggle the currency's availability with the :guilabel:`Active` toggle:" +" *on* is indicated with a green switch, and *off* is indicated with a grey " +"switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:104 +msgid "" +"On the right of the currency detail form, the appropriate " +":guilabel:`Currency Unit` (e.g. `Dollars`) and :guilabel:`Currency Subunit` " +"(e.g. `Cents`) can be found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:107 +msgid "" +"If the currency is meant to be used for eBay purposes, toggle the " +":guilabel:`Use on eBay` option to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:110 +msgid "" +"Next, under the :guilabel:`Rates` tab, the various conversion rates can be " +"viewed, added, or deleted. Each row shows the :guilabel:`Date` of that " +"specific rate, the :guilabel:`Company` to which it is connected, followed by" +" the :guilabel:`Unit per...` and :guilabel:`...per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:115 +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:166 +msgid "" +"The *...* in each of the last two columns represents the main currency set " +"for the company. For example, if the main currency is set to `USD`, the " +"columns are titled :guilabel:`Unit per USD` and :guilabel:`USD per Unit`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:119 +msgid "" +"To add a new rate, click :guilabel:`Add a line` in the :guilabel:`Rates` " +"tab, and proceed to fill in the necessary information in the aforementioned " +"columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:123 +msgid "Main currency detail form" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:125 +msgid "" +"If the selected currency is the main currency of the company, a blue banner " +"appears at the top of the currency detail form with the message: " +":guilabel:`This is your company's currency.`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a main currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:132 +msgid "" +"All the fields are the same as a typical currency detail form, but there " +"will **not** be a :guilabel:`Rates` tab because all other currency rates are" +" based off the main currency of the company." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:137 +msgid "Create new currency" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:139 +msgid "" +"If a desired currency isn't on the :guilabel:`Currencies` page, click the " +":guilabel:`New` button to open a blank currency template form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:143 +msgid "" +"The same :guilabel:`New` button is located in the upper-right corner of any " +"currency detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "How a blank currency detail form looks in Odoo Accounting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:149 +msgid "" +"On the blank currency detail form, proceed to enter the desired currency " +"code in the :guilabel:`Currency` field. Beneath that, enter the name for the" +" currency in the :guilabel:`Name` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:153 +msgid "" +"Then, toggle the currency's availability with the :guilabel:`Active` toggle " +"switch." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:155 +msgid "" +"On the right of the currency detail form, enter the appropriate " +":guilabel:`Currency Unit` (e.g. `Dollars`) and appropriate " +":guilabel:`Currency Subunit` (e.g. `Cents`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:158 +msgid "" +"If the currency is meant to be used for eBay purposes, toggle the " +":guilabel:`Use on eBay` to the desired activation." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:161 +msgid "" +"Next, under the :guilabel:`Rates` tab, add a new rate by clicking " +":guilabel:`Add a line`. Then, proceed to confirm and adjust the " +":guilabel:`Date`, :guilabel:`Company`, :guilabel:`Unit per...`, and " +":guilabel:`...per Unit` fields to ensure all the auto-populated information " +"is accurate." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:171 +msgid "Currency-specific pricelists" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:173 +msgid "" +"It is recommended that *at least* one pricelist is created per active " +"currency in the database. To create (or assign) a pricelist to a specific " +"currency, start by navigating to :menuselection:`Sales app --> Products --> " +"Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:177 +msgid "" +"From the :guilabel:`Pricelists` page, either select an existing pricelist to" +" edit, or click :guilabel:`New` to create a new pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:180 +msgid "" +"On the pricelist detail form, for either a new or existing pricelist, adjust" +" the :guilabel:`Currency` field as desired." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:184 +msgid ":doc:`./pricing` to learn more about pricelist configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:187 +msgid "Auto-conversion from public price" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:189 +msgid "" +"It should be noted that the public price seen on products is directly " +"related to the main currency the company has set, which is configured by " +"navigating to :menuselection:`Accounting app --> Configuration --> Settings " +"--> Currencies section --> Main Currency --> Currency drop-down menu`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:193 +msgid "" +"The sales price automatically updates if the pricelist is changed to a " +"different pricelist that has a different currency than the company's main " +"currency. The change in price is directly related to the updated conversion " +"rate for that currency." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:198 +msgid "Set product prices" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:200 +msgid "" +"In order to have product prices set in place to avoid any changes in " +"currency rates, start by navigating to :menuselection:`Sales app --> " +"Products --> Products`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:203 +msgid "" +"From the :guilabel:`Products` page, select the desired product to modify. " +"Or, create a new product by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:206 +msgid "" +"Then, on the product detail form, click the :guilabel:`Extra Prices` smart " +"button, located in the upper-left corner. Doing so reveals a separate " +":guilabel:`Price Rules` page, specific to that particular product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst-1 +msgid "" +"How to set product prices based on foreign currency pricelists in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:214 +msgid "" +"Click :guilabel:`New`, and select the desired pricelist from the drop-down " +"menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:217 +msgid "" +"The :guilabel:`Applied On` field is auto-populated with the product, so " +"proceed to enter in the desired figures in the :guilabel:`Min. Quantity` and" +" :guilabel:`Price` fields." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:221 +msgid "" +"The figure in the :guilabel:`Min. Quantity` field means the " +":guilabel:`Price` being set will **only** trigger if at least that amount of" +" product is purchased." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:224 +msgid "" +"If necessary, configure a :guilabel:`Start Date` and :guilabel:`End Date` " +"for the set prices. Leaving those columns blank ensures the set price will " +"remain valid, regardless of the date of sale." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:227 +msgid "" +"If working in a multi-company environment, designate to which company this " +"price rule should be applied in the :guilabel:`Company` field. Leaving that " +"field blank ensures the price rule applies to all companies in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:231 +msgid "" +"With those configurations complete, regardless of any changes/updates in " +"conversion, whenever those designated pricelists are applied to a customer " +"trying to purchase this specific product, these pre-determined set prices " +"appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:236 +msgid ":doc:`./pricing`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:3 +msgid "Pricelists, discounts, and formulas" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:5 +msgid "" +"Odoo *Sales* has a useful pricelist feature that can be tailored to fit any " +"unique pricing strategy." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:7 +msgid "" +"A *pricelist* is a list of prices (or price rules) that Odoo uses to " +"determine the appropriate price for a customer. These pricelists can be set " +"with specific criteria (such as time periods, minimum quantity sold, and " +"more) in order to apply certain prices or discounts." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:11 +msgid "" +"Pricelists suggest certain prices, but they can always be overridden on the " +"sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:14 +msgid "Pricing strategy options" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:16 +msgid "" +"To choose a pricing strategy, first navigate to :menuselection:`Sales app " +"--> Configuration --> Settings`. In the :guilabel:`Pricing` section, click " +"the checkbox next to the :guilabel:`Pricelists` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:20 +msgid "" +"Doing so reveals two additional options beneath it: :guilabel:`Multiple " +"prices per product` and :guilabel:`Advanced price rules (discounts, " +"formulas)`. A link labeled :guilabel:`Pricelists` also appears, which leads " +"to a separate pricelists page, wherein pricelists can be created and/or " +"modified." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:25 +msgid "" +":guilabel:`Multiple prices per product`: provides the option to set several " +"different prices per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:27 +msgid "" +":guilabel:`Advanced price rules (discounts, formulas)`: provides the option " +"to create detailed price rules and apply discounts, margins, and roundings." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelist feature setting looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:34 +msgid "" +"After clicking the checkbox beside the :guilabel:`Pricelists` feature, " +"select one of those two options, then click :guilabel:`Save` to save all " +"changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:40 +msgid "" +"After activating and saving the :guilabel:`Pricelists` feature, the " +":guilabel:`Settings` page reloads and, from here, either select the " +":guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on " +"the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app -->" +" Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:45 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:328 +msgid "" +"Either option reveals the :guilabel:`Pricelists` page, in which pricelists " +"can be created and/or modified at any time." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelists page looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:53 +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:267 +msgid "" +"The :guilabel:`Public Pricelist` is the default pricelist used with Odoo " +"*Sales* and *eCommerce*." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:55 +msgid "" +"From the :guilabel:`Pricelists` page, either select the desired pricelist to" +" edit, or click :guilabel:`New` to create a new pricelist, which reveals a " +"blank pricelist form that can be configured in a number of different ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the pricelist detail form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:63 +msgid "" +"When creating a new pricelist, start by adding a name for the pricelist at " +"the top of the form, in the blank field. Next, select which " +":guilabel:`Currency` should be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:66 +msgid "" +"Then, if working in a multi-company environment, select which company this " +"pricelist should apply to in the :guilabel:`Company` field. If this field is" +" left blank, the pricelist is automatically applied to all companies in the " +"database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:71 +msgid "Price rules tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:73 +msgid "" +"The :guilabel:`Price Rules` tab functionality on a pricelist form varies " +"depending on the :guilabel:`Pricelists` setting chosen: either " +":guilabel:`Multiple prices per product` or :guilabel:`Advanced price rules " +"(discounts, formulas)`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:77 +msgid "" +"However, the :guilabel:`Time-based rules` tab and :guilabel:`Configuration` " +"tab are always the same, regardless of the chosen :guilabel:`Pricelists` " +"setting." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:81 +msgid "Price rules tab (multiple prices per product)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:83 +msgid "" +"With the :guilabel:`Multiple prices per product` setting activated, the " +":guilabel:`Price Rules` tab on pricelist forms provides the option to add " +"specific products, with a specific price, to a pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:87 +msgid "" +"To add a specific product and price to a pricelist form, click the " +":guilabel:`Price Rules` tab, then click :guilabel:`Add a line` in the " +":guilabel:`Products` column. Then, select the desired product for which a " +"specific price should be applied." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:91 +msgid "" +"Next, if necessary, select a product variant under the :guilabel:`Variants` " +"column (e.g. a specific product size, color, etc.). If no variants are " +"selected, then this price will apply to all variants of the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:95 +msgid "" +"If a minimum amount of the product must be purchased in order to apply the " +"specific price, enter the amount under the :guilabel:`Min. Quantity` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:98 +msgid "" +"To configure the price of the product for this specific pricelist, enter the" +" desired amount under the :guilabel:`Price` column. Then, there is the " +"option to add a :guilabel:`Start Date` and :guilabel:`End Date` to the " +"configured product price, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:102 +msgid "" +"To add another product line, click :guilabel:`Add a line` again, and repeat " +"the process. There is no limit to how many products can be added in the " +":guilabel:`Price Rules` tab of a pricelist form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:105 +msgid "" +"For more information, check out the following section: :ref:`Multiple prices" +" per product <sales/multiple-prices-per-product>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:109 +msgid "Price rules tab (advanced price rules)" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:111 +msgid "" +"With the :guilabel:`Advanced price rules (discounts, formulas)` setting " +"activated, the :guilabel:`Price Rules` tab on pricelist forms provides the " +"option to configure detailed price rules based on formulas." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:115 +msgid "" +"Check out the :ref:`Advanced price rules (discounts, formulas) " +"<sales/advanced-price-rules>` section for detailed steps on how to add " +"advanced price rules to a pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:119 +msgid "Time-based rules tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:121 +msgid "" +"Time-based rules are used specifically with :doc:`subscription products " +"</applications/sales/subscriptions/products>`. Be sure to check out the Odoo" +" *Subscriptions* :doc:`documentation </applications/sales/subscriptions>`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:125 +msgid "" +"Under the :guilabel:`Time-based rules` tab, the same functionality of the " +":guilabel:`Price Rules` tab is present, with the only difference being that " +"a repeating time period can be applied in the :guilabel:`Period` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:129 +msgid "" +"After a :guilabel:`Product` and potential :guilabel:`Variant` are selected " +"in the :guilabel:`Time-based rules` tab, select the blank field in the " +":guilabel:`Period` column to reveal a drop-down menu of pre-designated " +"recurrence periods (e.g. `Monthly`, `Quarterly`, `Weekly`, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:133 +msgid "" +"New recurrence periods can also be directly created from this column, by " +"typing in the new name for the :guilabel:`Period` and then selecting " +":guilabel:`Create` to create the time period, which can be edited later. Or," +" select :guilabel:`Create and edit...` to reveal a pop-up form, in which the" +" new recurrence period can be directly configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Custom time period pop-up form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:142 +msgid "" +"From this :guilabel:`Create Period` pop-up form, add a :guilabel:`Name`, " +":guilabel:`Duration`, then a :guilabel:`Unit` (e.g. `Days`, `Weeks`, etc.). " +"When finished, click :guilabel:`Save and Close`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:145 +msgid "" +"Lastly, add the desired price for this time-based rule in the " +":guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:148 +msgid ":doc:`/applications/sales/subscriptions`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:151 +msgid "Configuration tab" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:153 +msgid "" +"Under the :guilabel:`Configuration` tab, there are a few options that can " +"further customize the pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Configuration tab on pricelist detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:160 +msgid "" +"From here, under the :guilabel:`Availability` section, in the " +":guilabel:`Country Groups` field, certain country groups can be added to the" +" pricelist. There is no limit to how many country groups can be added in " +"this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:165 +msgid "" +"If no country is set for a customer, Odoo takes the first pricelist without " +"any country group." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:167 +msgid "" +"Under the :guilabel:`Website` section, there are a few options that can be " +"configured. In the :guilabel:`Website` field, this pricelist can be applied " +"to a specific website, if working in a multi-website environment. If left " +"blank, the pricelist will be applied to all websites in the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:172 +msgid "" +"Click the :guilabel:`Selectable` checkbox to have this pricelist as a " +"selectable option for customers to choose as they shop. If the " +":guilabel:`Selectable` box is left unchecked, customers **cannot** select " +"this pricelist for themselves as they shop." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:176 +msgid "" +"Lastly, there is the option to add an :guilabel:`E-commerce Promotional " +"Code`. To add a code, type in the desired promo code that, when entered " +"during the checkout process, applies the pricelist to the customer, even if " +"the customer does not fall into the previously-specified criteria." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:181 +msgid "Show discount percentage to customers" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:183 +msgid "" +"With Odoo *Sales*, the option to show the public price *and* the computed " +"discount percentage on the product catalog is available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:186 +msgid "" +"To do that, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`, and in the :guilabel:`Pricing` section, click the checkbox next " +"to the :guilabel:`Discounts` feature, and then click :guilabel:`Save` to " +"save all changes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:190 +msgid "" +"After activating the :guilabel:`Discounts` feature, navigate to the " +"pricelists page, either by clicking the :guilabel:`Pricelists` link from the" +" :guilabel:`Settings` page, or by going to :menuselection:`Sales app --> " +"Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:194 +msgid "" +"On the :guilabel:`Pricelists` page, select the desired pricelist to edit. On" +" the pricelist form, click into the :guilabel:`Configuration` tab. In the " +":guilabel:`Configuration` tab, at the bottom, a :guilabel:`Discounts` " +"section is now available." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "" +"What the discount options are on the configuration tab of a pricelist in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:202 +msgid "The options available in this section are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:204 +msgid "" +":guilabel:`Discount included in the price`: shows the customer only the " +"final price with the discount already included." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:206 +msgid "" +":guilabel:`Show public price & discount to the customer`: shows the customer" +" the public price *and* the discount they're earning." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:210 +msgid "Customer pricelist application" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:212 +msgid "" +"While the default pricelist applied to any customer is the :guilabel:`Public" +" Pricelist`, Odoo provides the opportunity to directly apply a different " +"pricelist to customers on their contact form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:215 +msgid "" +"To do that, open the desired customer's contact form, either by navigating " +"to :menuselection:`Sales app --> Orders --> Customers` and selecting the " +"customer from the main :guilabel:`Customers` page, or by clicking on the " +"customer's name on a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "Sample customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:223 +msgid "" +"On the desired customer's contact form, under the :guilabel:`Sales & " +"Purchase` tab, in the :guilabel:`Sales` section, designate what pricelist " +"should be applied to this specific customer from the drop-down menu in the " +":guilabel:`Pricelist` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "The pricelist field in a customer detail form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:236 +msgid "" +"To apply several prices per individual product, select the " +":guilabel:`Multiple prices per product` option, after enabling the " +":guilabel:`Pricelists` feature on the *Sales* app setting page " +"(:menuselection:`Sales app --> Configuration --> Settings`), and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:240 +msgid "" +"Next, apply pricelists to specific products using the product form. Navigate" +" to the :menuselection:`Sales app --> Products --> Products` and select the " +"product for which multiple prices should be applied. Selecting a product " +"from the :guilabel:`Products` page reveals that specific product's product " +"form on a separate page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:245 +msgid "" +"On the product form, click the :guilabel:`Extra Prices` smart button, " +"located at the top of the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the extra prices smart button appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:252 +msgid "" +"Doing so reveals a separate page displaying the :guilabel:`Price Rules` that" +" are specific to that particular product. Here, price rules can be edited or" +" created at any time." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the extra price rules per product page appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:259 +msgid "" +"To create a new price rule for a product from this specific :guilabel:`Price" +" Rules` page, click :guilabel:`New` to add a new, customizable row that has " +"the desired product already populated in the :guilabel:`Applied On` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:263 +msgid "" +"Next, select which :guilabel:`Pricelist` this specific product price rule " +"should apply to, via the drop-down menu in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:270 +msgid "" +"To create a new pricelist from this page, type in the desired name of the " +"new pricelist in the :guilabel:`Pricelist` column, then select " +":guilabel:`Create` from the drop-down menu. All pricelists can be modified " +"at any time, by navigating to :menuselection:`Sales app --> Products --> " +"Pricelists`. Pricelists can also be created on that specific " +":guilabel:`Pricelists` page, as well." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:276 +msgid "" +"After the desired pricelist is added to the row, designate a :guilabel:`Min." +" Quantity` for the price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:280 +msgid "" +"If the :guilabel:`Min. Quantity` column is set to `2`, the new price in the " +":guilabel:`Price` column will be applied to orders of 2 or more products. " +"So, in theory, if a single product costs $100, customers can be encouraged " +"to buy more, if the :guilabel:`Price` is set at $85 per product for a " +":guilabel:`Min. Quantity` of `2` products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:285 +msgid "" +"Next, enter the desired amount in the :guilabel:`Price` column. Then, if " +"needed, enter a :guilabel:`Start Date` and :guilabel:`End Date` for the " +"product's price rule." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:288 +msgid "" +"And lastly, if working in a multi-company environment, select which company " +"this price rule should be applied to in the :guilabel:`Company` field. " +"Leaving this field blank means the price rule applies for all companies in " +"the database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:292 +msgid "" +"Click away from the row to activate Odoo's auto-save capability, meaning " +"that newly-created price rule is now ready to be used." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:295 +msgid "" +"Proceed to add as many unique price rules per product as desired. There is " +"no limit to how many price rules can be added per product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:298 +msgid "" +"With the price rule(s) in place for a specific product, customers who fall " +"into those corresponding pricelists automatically see those new prices " +"applied. The number of price rules applied to a particular product are also " +"displayed in the :guilabel:`Extra Prices` smart button, located on every " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:304 +msgid "" +"When a price rule/pricelist is added to a product via the :guilabel:`Extra " +"Prices` smart button, it is also reflected on the pricelist itself. " +"Similarly, when a price rule for a specific product is added to a pricelist," +" it is also reflected on the product form via the :guilabel:`Extra Prices` " +"smart button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:314 +msgid "" +"The :guilabel:`Advanced price rules (discounts, formulas)` pricelist feature" +" provides the option to set price change rules based on discounts and " +"formulas. These changes can be relative to the product list/catalog price, " +"the product's cost, or another pricelist." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:318 +msgid "" +"To use advanced pricing rules, with discounts and formulas, select the " +":guilabel:`Advanced price rules (discounts, formulas)` option, after " +"enabling the :guilabel:`Pricelists` feature on the *Sales* app setting page " +"(:menuselection:`Sales app --> Configuration --> Settings`), and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:323 +msgid "" +"After activating and saving that :guilabel:`Pricelists` feature, the " +":guilabel:`Settings` page reloads and, from here, either select the " +":guilabel:`Pricelists` link (beneath the :guilabel:`Pricelists` feature on " +"the :guilabel:`Settings` page), or navigate to :menuselection:`Sales app -->" +" Products --> Pricelists`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:331 +msgid "" +"From the :guilabel:`Pricelists` page, select a desired pricelist to modify, " +"or create a new pricelist by clicking the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:334 +msgid "" +"On the pricelist form, under the :guilabel:`Price Rules` tab, click " +":guilabel:`Add a line` to add an advanced price rule. Doing so reveals a " +":guilabel:`Create Pricelist Rules` pop-up form, in which the advanced rule " +"is configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "How the Create Pricelist Rules pop-up form looks in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:343 +msgid "Price computation" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:345 +msgid "" +"On this form, first choose one of the three :guilabel:`Computation` options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:347 +msgid "" +":guilabel:`Fixed Price`: the price computation is based on a fixed price." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:348 +msgid ":guilabel:`Discount`: the price computation is based on a discount." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:349 +msgid ":guilabel:`Formula`: the price computation is based on a formula." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:352 +msgid "" +"Each :guilabel:`Computation` option reveals its own computation-specific " +"fields on the form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:354 +msgid "" +"If :guilabel:`Fixed Price` is selected, enter the desired price in the " +":guilabel:`Fixed Price` field below. If :guilabel:`Discount` is selected, " +"enter the desired discount percentage in the :guilabel:`Discount` field that" +" appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:358 +msgid "" +"If :guilabel:`Formula` is selected, a number of configurable options appear." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst-1 +msgid "The various formula computation options present in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:364 +msgid "" +"To configure the :guilabel:`Formula` computation option, start by selecting " +"an option from the :guilabel:`Based on` field: :guilabel:`Sales Price`, " +":guilabel:`Cost`, or :guilabel:`Other Pricelist`. This determines what the " +"advanced price rule formula will be based on." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:368 +msgid "" +"Next, in the :guilabel:`Discount` field, determine how much of a discount " +"should be applied. It should be noted that a mark-up can be applied by " +"setting a negative discount in this field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:372 +msgid "" +"To formulate a 100% markup (or 2 times the cost of the product), with a $5 " +"minimum margin, set the :guilabel:`Based on` field to :guilabel:`Cost`, the " +":guilabel:`Discount` to `-100`, and the :guilabel:`Margins` to `5`. This is " +"often seen in retail situations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "" +"How it looks to formulate a markup cost with 5 dollar minimum margin in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:380 +msgid "" +"Then, in the :guilabel:`Extra Fee` field, specify a fixed amount to add (or " +"subtract) to the amount calculated with the discount. After that, enter a " +"desired figure in the :guilabel:`Rounding Method` field. The rounding method" +" sets the price so that it is a multiple of the value in the field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:385 +msgid "Rounding is applied *after* the discount and *before* the surcharge." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:388 +msgid "" +"To have prices that end in 9.99, set the :guilabel:`Rounding Method` to `10`" +" and the :guilabel:`Extra Fee` to `-0.01`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:391 +msgid "" +"Lastly, specify the minimum amount of margin over the base price in the " +":guilabel:`Margins` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:393 +msgid "" +"Once all formula-related configurations are complete, Odoo provides an " +"example of the formula in a blue block to the right of the configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:397 +msgid "" +"To apply 20% discounts, with prices rounded up to 9.99, set the " +":guilabel:`Based on` field to :guilabel:`Sales Price`, the " +":guilabel:`Discount` field to `20`, the :guilabel:`Extra Fee` field to " +"`-0.01`, and the :guilabel:`Rounding Method` field to `10`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:0 +msgid "Example of a 20% discount with prices rounded to 9.99 in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:406 +msgid "Conditions" +msgstr "เงื่อนไข" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:408 +msgid "" +"At the bottom of the :guilabel:`Create Pricelist Rules` pop-up form is the " +":guilabel:`Conditions` section." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:411 +msgid "" +"Here, start by selecting one of the options in the :guilabel:`Apply On` " +"field:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:413 +msgid "" +":guilabel:`All Products`: the advanced pricelist rule will be applied to all" +" products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:414 +msgid "" +":guilabel:`Product Category`: the advanced pricelist rule will be applied to" +" a specific category of products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:416 +msgid "" +":guilabel:`Product`: the advanced pricelist rule will be applied to a " +"specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:417 +msgid "" +":guilabel:`Product Variant`: the advanced pricelist rule will be applied to " +"a specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:420 +msgid "" +"If any of those options, apart from :guilabel:`All Products`, are selected, " +"a new option-specific field appears, in which the specific " +":guilabel:`Product Category`, :guilabel:`Product`, or :guilabel:`Product " +"Variant` must be chosen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:424 +msgid "" +"Then, select a minimum quantity to be applied to the advanced pricelist rule" +" in the :guilabel:`Min. Quantity` field. Lastly, select a range of dates for" +" the pricelist item validation in the :guilabel:`Validity` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:428 +msgid "" +"Once all configurations are complete, either click :guilabel:`Save & Close` " +"to save the advanced pricelist rule, or click :guilabel:`Save & New` to " +"immediately create another advanced pricelist rule on a fresh form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:433 +msgid "" +"If a price rule is set for a particular product, and another one for its " +"product category, Odoo takes the rule of the product itself." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:437 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:438 +msgid "" +":doc:`/applications/websites/ecommerce/managing_products/price_management`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products.rst:5 +msgid "Manage your products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:3 +msgid "Import products" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:5 +msgid "" +"Odoo *Sales* provides a template for importing products with categories and " +"variants, which can be opened and edited with any spreadsheet software " +"(Microsoft Excel, OpenOffice, Google Sheets, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:8 +msgid "" +"When this spreadsheet is filled out properly, it can be quickly uploaded to " +"the Odoo database. When uploaded, those products are instantly added, " +"accessible, and editable in the product catalog." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:12 +msgid "Import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:14 +msgid "" +"In order to import products with categories and variants, the *Import " +"Template for Products* **must** be downloaded. Once downloaded, the template" +" can be adjusted and customized, and then uploaded back into the Odoo " +"database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:18 +msgid "" +"To download the necessary import template, navigate to :menuselection:`Sales" +" app --> Products --> Products`. On the :guilabel:`Products` page, click the" +" :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:22 +msgid "" +"From this drop-down menu, select the :guilabel:`Import records` option." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The Import records option selectable from the gear icon on the Products page" +" in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:28 +msgid "" +"Selecting :guilabel:`Import records` reveals a separate page with a link to " +"download the :guilabel:`Import Template for Products`. Click that link to " +"download the template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:35 +msgid "" +"Once the template download is complete, open the spreadsheet file to " +"customize it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:38 +msgid "Customize product import template" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:40 +msgid "" +"When the import template has been downloaded and opened, it's time to modify" +" its contents. However, before any changes are made, there are a few " +"elements to keep in mind during the process:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:43 +msgid "" +"Feel free to remove any columns that aren't deemed necessary. But, it is " +"*strongly* advised that the :guilabel:`Internal Reference` column remains." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:46 +msgid "" +"While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in " +"the :guilabel:`Internal Reference` column for each product can be helpful in" +" many cases. This can even be from previous software spreadsheets to ease " +"the transition into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:50 +msgid "" +"For example, when updating imported products, the same file can be imported " +"several times without creating duplicates, thus enhancing the efficiency and" +" simplicity of imported product management." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:52 +msgid "" +"Do **not** change the labels of columns that are meant to be imported. " +"Otherwise, Odoo won't recognize them, forcing the user to map them on the " +"import screen manually." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:54 +msgid "" +"Feel free to add new columns to the template spreadsheet, if desired. " +"However, to be added, those fields **must** exist in Odoo. If Odoo can't " +"match the column name with a field, it can be matched manually during the " +"import process." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:58 +msgid "" +"During the import process of the completed template, Odoo reveals a page " +"showcasing all the elements of the newly-configured product template " +"spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, " +"and :guilabel:`Comments`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:62 +msgid "" +"To manually match a column name with a field in Odoo, click the " +":guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` " +"that needs a manual adjustment, and select the appropriate field from that " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:0 +msgid "" +"The Odoo Field drop-down menu next to a Field Column that needs to be " +"manually adjusted." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:71 +msgid "Import product template spreadsheet" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:73 +msgid "" +"After customizing the product template spreadsheet, return to the Odoo " +"product import page, where the template download link is found, and click " +"the :guilabel:`Upload File` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The upload file button on the import products template download page in Odoo" +" Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:81 +msgid "" +"Then, a pop-up window appears, in which the completed product template " +"spreadsheet file should be selected and uploaded to Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:84 +msgid "" +"After that, Odoo reveals a page showcasing all the elements of the newly-" +"configured product template spreadsheet, separated by :guilabel:`File " +"Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The import a file page in Odoo Sales after a product template has been " +"uploaded." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:91 +msgid "" +"From here, the :guilabel:`File Column` can be manually assigned to an " +":guilabel:`Odoo Field`, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:94 +msgid "" +"To make sure everything is appropriate, and all the columns and fields are " +"lined up accurately, click the :guilabel:`Test` button in the upper-left " +"corner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:97 +msgid "" +"If everything is lined up and applied correctly, Odoo reveals a blue banner " +"at the top of the page, informing the user that :guilabel:`Everything seems " +"valid`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The everything seems valid message that appears if file columns are entered " +"correctly." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:104 +msgid "" +"If there are any errors, Odoo reveals a red banner at the top of the page, " +"with instructions of where to locate the specific issues, and how to fix " +"them." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The import error message that appears if file columns don't match an Odoo " +"Field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:111 +msgid "" +"Once those errors are fixed, click :guilabel:`Test` again to ensure all " +"necessary issues have been remedied appropriately." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:114 +msgid "" +"If additional product template spreadsheets need to be uploaded, click the " +":guilabel:`Load File` button, select the desired product template " +"spreadsheet, and repeat the process." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:117 +msgid "When everything is ready, click the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:119 +msgid "" +"When clicked, Odoo instantly imports those products, and reveals the main " +":guilabel:`Products` page, with a pop-up message in the upper-right corner. " +"This pop-up message informs the user how many products were successfully " +"imported." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"The pop-up window that appears after a successful product import process in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:127 +msgid "" +"At this point, all the newly-imported products are accessible and editable " +"via the :guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:131 +msgid "Import relation fields, attributes, and variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:133 +msgid "" +"It's important to note that an Odoo object is always related to many other " +"objects. For example, a product is linked to product categories, attributes," +" vendors, and things of this nature. These links/connections are known as " +"relations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:138 +msgid "" +"In order to import product relations, the records of the related object " +"**must** be imported *first* from their own list menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:142 +msgid "Relation fields" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:144 +msgid "" +"On product forms in Odoo, there are a number of fields that can be modified " +"and customized at any time. These fields are found under every tab on a " +"product form. While these fields are easily editable directly on the product" +" form, they can also be modified via a product import." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:148 +msgid "" +"As mentioned, relation fields of this nature can **only** be imported for " +"products if they already exist in the database. For example, if a user " +"attempts to import a product with a *Product Type*, it can only be one of " +"the preconfigured product types existing in the database (e.g. *Storable " +"Product*, *Consumable*, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:153 +msgid "" +"To import information for a relation field on a product import template " +"spreadsheet, add the name of the field as a column name/title on the " +"spreadsheet. Then, on the appropriate product line, add the desired relation" +" field option." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:157 +msgid "" +"When all desired relation field information has been entered, save the " +"spreadsheet, and import it to the database, per the process mentioned above " +"(:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> " +"Import records --> Upload File`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:161 +msgid "" +"Once the spreadsheet with the newly-configured relation field information " +"has been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:164 +msgid "" +"When the newly-changed/modified products, complete with the new relation " +"field information, has been imported and uploaded, that new information can " +"be found on the :guilabel:`Products` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:168 +msgid "Attributes and values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:170 +msgid "" +"Odoo also allows users to import product attributes and values that can be " +"used for products that already exist in the database, and/or with imported " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:173 +msgid "" +"To import attributes and values, a separate spreadsheet or CSV file " +"dedicated to attributes and values **must** be imported and uploaded before " +"they can be used for other products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:176 +msgid "" +"The column names/titles of the attributes and values spreadsheet should be " +"as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, " +":guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "An attributes and values spreadsheet template for imports." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:184 +msgid ":guilabel:`Attribute`: name of the attribute (e.g. `Size`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:185 +msgid "" +":guilabel:`Display Type`: display type used in the product configurator. " +"There are three display type options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:188 +msgid ":guilabel:`Radio`: values displayed as radio buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:189 +msgid ":guilabel:`Selection`: values displayed in a selection list" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:190 +msgid ":guilabel:`Color`: values denoted as a color selection" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:192 +msgid "" +":guilabel:`Variant Creation Mode`: how the variants are created when applied" +" to a product. There are three variant creation mode options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:195 +msgid "" +":guilabel:`Instantly`: all possible variants are created as soon as the " +"attribute, and its values, are added to a product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:197 +msgid "" +":guilabel:`Dynamically`: each variant is created **only** when its " +"corresponding attributes and values are added to a sales order" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:199 +msgid ":guilabel:`Never`: variants are **never** created for the attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:202 +msgid "" +"The :guilabel:`Variants Creation Mode` **cannot** be changed once the " +"attribute is used on at least one product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:205 +msgid "" +":guilabel:`Values/Value`: values pertaining to the corresponding attribute. " +"If there are multiple values for the same attribute, the values need to be " +"in individual lines on the spreadsheet." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:208 +msgid "" +"Once the desired attributes and values have been entered and saved in the " +"spreadsheet, it's time to import and upload it into Odoo. To do that, " +"navigate to :menuselection:`Sales app --> Configuration --> Attributes --> " +"⚙️ (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:212 +msgid "" +"Once the spreadsheet with the newly-configured attributes and values has " +"been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Attributes` page. That's where those newly-added attributes and " +"values can be found and edited, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:216 +msgid "" +"As mentioned previously, when attributes and values have been added to the " +"Odoo database, they can be used for existing or imported products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:220 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 +msgid "Product variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:222 +msgid "" +"When product attributes and values are configured in the database, they can " +"be used on product import spreadsheets to add more information and detail to" +" products being imported." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:225 +msgid "" +"To import products with product attributes and values, the product import " +"template spreadsheet must be configured with specific :guilabel:`Product " +"Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and " +":guilabel:`Name` columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:229 +msgid "" +"There can be other columns, as well, but these columns are **required** in " +"order to properly import products with specific variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst-1 +msgid "" +"Product variants spreadsheet with product attributes and variants for import" +" purposes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:236 +msgid ":guilabel:`Name`: product name" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:237 +msgid ":guilabel:`Product Attributes / Attribute`: name of attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:238 +msgid "" +":guilabel:`Product Attributes / Values`: values pertaining to the " +"corresponding attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:241 +msgid "" +"To import multiple values, separate them by *just* a comma, **not** a comma " +"followed by a space, in the product import template spreadsheet (e.g. " +"`furniture,couch,home`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:244 +msgid "" +"When the desired products and product variants have been entered and saved " +"in the spreadsheet, it's time to import and upload them into Odoo. To do " +"that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️" +" (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:248 +msgid "" +"Once the spreadsheet with the newly-configured products and product variants" +" has been uploaded, click :guilabel:`Import`, and Odoo returns to the " +":guilabel:`Products` page. That's where the newly-added products can be " +"found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:252 +msgid "" +"To view and modify the attributes and variants on any products, select the " +"desired product from the :guilabel:`Products` page, and click the " +":guilabel:`Attributes \\& Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:256 +msgid ":doc:`variants`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 +msgid "Product images with Google Images" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 +msgid "" +"Having appropriate product images in Odoo is useful for a number of reasons." +" However, if a lot of products need images, assigning them can become " +"incredibly time-consuming." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:8 +msgid "" +"Fortunately, by configuring the *Google Custom Search* API within an Odoo " +"database, finding product images for products (based on their barcode) is " +"extremely efficient." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:16 +msgid "" +"In order to utilize *Google Custom Search* within an Odoo database, both the" +" database and the Google API must be properly configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:20 +msgid "" +"Free Google accounts allow users to select up to 100 free images per day. If" +" a higher amount is needed, a billing upgrade is required." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:26 +msgid "Google API dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 +msgid "" +"Go to the `Google Cloud Platform API & Services " +"<https://console.developers.google.com/>`_ page to generate Google Custom " +"Search API credentials. Then, log in with a Google account. Next, agree to " +"their :guilabel:`Terms of Service` by checking the box, and clicking " +":guilabel:`Agree and Continue`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:32 +msgid "" +"From here, select (or create) an API project to store the credentials. Start" +" by giving it a memorable :guilabel:`Project Name`, select a " +":guilabel:`Location` (if any), then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:35 +msgid "" +"With the :guilabel:`Credentials` option selected in the left sidebar, click " +":guilabel:`Create Credentials`, and select :guilabel:`API key` from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "API & Services page on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:42 +msgid "" +"Doing so reveals an :guilabel:`API key created` pop-up window, containing a " +"custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the " +"pop-up window -- it will be used later. Once the key is copied (and saved " +"for later use), click :guilabel:`Close` to remove the pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The API key created pop-up window that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:50 +msgid "On this page, search for `Custom Search API`, and select it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 +msgid "" +"From the :guilabel:`Custom Search API` page, enable the API by clicking " +":guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"\"Custom Search API\" page with Enable button highlighted on Google Cloud " +"Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:65 +msgid "Google Programmable Search dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:67 +msgid "" +"Next, go to `Google Programmable Search Engine " +"<https://programmablesearchengine.google.com/>`_, and click either of the " +":guilabel:`Get started` buttons. Log in with a Google account, if not " +"already logged in." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Google Programmable Search Engine page with the Get Started buttons." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:75 +msgid "" +"On the :guilabel:`Create a new search engine` form, fill out the name of the" +" search engine, along with what the engine should search, and be sure to " +"enable :guilabel:`Image Search` and :guilabel:`SafeSearch`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"Create new search engine form that appears with search engine " +"configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 +msgid "Validate the form by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:84 +msgid "" +"Doing so reveals a new page with the heading: :guilabel:`Your new search " +"engine has been created`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The Your New Search Engine Has Been Created page that appears with copy " +"code." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:91 +msgid "" +"From this page, click :guilabel:`Customize` to open the " +":menuselection:`Overview --> Basic` page. Then, copy the ID in the " +":guilabel:`Search engine ID` field. This ID is needed for the Odoo " +"configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Basic overview page with search engine ID field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 +msgid "" +"In the Odoo database, go to the :menuselection:`Settings app` and scroll to " +"the :guilabel:`Integrations` section. From here, check the box beside " +":guilabel:`Google Images`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Google Images setting in the Odoo Settings app page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:112 +msgid "" +"Next, return to the :menuselection:`Settings app`, and scroll to the " +":guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and " +":guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google " +"Images` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:115 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 +msgid "Product images in Odoo with Google Custom Search API" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:122 +msgid "" +"Adding images to products in Odoo can be done on any product or product " +"variant. This process can be completed in any Odoo application that provides" +" access to product pages (e.g. *Sales* app, *Inventory* app, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:126 +msgid "" +"Below is a step-by-step guide detailing how to utilize the *Google Custom " +"Search API* to assign images to products in Odoo using the Odoo *Sales* " +"application:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:129 +msgid "" +"Navigate to the :guilabel:`Products` page in the *Sales* app " +"(:menuselection:`Sales app --> Products --> Products`). Or, navigate to the " +":guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales " +"app --> Products --> Product Variants`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:132 +msgid "Select the desired product that needs an image." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:135 +msgid "" +"Only products (or product variants) that have a barcode, but **not** an " +"image, are processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:137 +msgid "" +"If a product with one or more variants is selected, each variant that " +"matches the aforementioned criteria is processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:140 +msgid "" +"Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select " +":guilabel:`Get Pictures from Google Images` from the menu that pops up." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The Get Pictures from Google Images option from the Action drop-down menu in" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:147 +msgid "On the pop-up window that appears, click :guilabel:`Get Pictures`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "" +"The pop-up that appears in which the user should click Get Picture in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:153 +msgid "Once clicked, the image(s) will appear incrementally." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:156 +msgid "" +"Only the first 10 images are fetched immediately. If you selected more than " +"10, the rest are fetched as a background job." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:159 +msgid "" +"The background job processes about 100 images in a minute. If the quota " +"authorized by Google (either with a free or a paid plan) is reached, the " +"background job puts itself on hold for 24 hours. Then, it will continue " +"where it stopped the day before." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:164 +msgid "" +"`Create, modify, or close your Google Cloud Billing account " +"<https://cloud.google.com/billing/docs/how-to/manage-billing-account>`_" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 +msgid "" +"Product variants are used to give single products a variety of different " +"characteristics and options for customers to choose from, such as size, " +"style, or color, just to name a few." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:8 +msgid "" +"Products variants can be managed via their individual product template, or " +"by navigating to either the :guilabel:`Product Variants` or " +":guilabel:`Attributes` page. All of these options are located within the " +"Odoo *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 +msgid "" +"An apparel company has the following variant breakdown for one their best-" +"selling t-shirts:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:15 +msgid "Unisex Classic Tee" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:17 +msgid "Color: Blue, Red, White, Black" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:18 +msgid "Size: S, M, L, XL, XXL" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:20 +msgid "" +"Here, the **T-shirt** is the product template, and **T-shirt: Blue, S** is a" +" specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +msgid "" +"**Color** and **Size** are *attributes*, and the corresponding options (like" +" **Blue** and **S**) are *values*." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 +msgid "" +"In this instance, there is a total of twenty different product variants: " +"four **Color** options multiplied by five **Size** options. Each variant has" +" its own inventory count, sales totals, and other similar records in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 +msgid ":doc:`/applications/websites/ecommerce/managing_products/variants`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 +msgid "" +"To use product variants, the *Variants* setting **must** be activated in the" +" Odoo *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 +msgid "" +"To do that, go to :menuselection:`Sales app --> Configuration --> Settings`," +" and locate the :guilabel:`Product Catalog` section at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:42 +msgid "" +"In that section, check the box to enable the :guilabel:`Variants` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Activating product variants on the Settings page of the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:48 +msgid "" +"Then, click :guilabel:`Save` at the top of the :guilabel:`Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:51 +msgid "Attributes" +msgstr "คุณลักษณะ" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:53 +msgid "" +"Before product variants can be set up, attributes **must** be created. To " +"create, manage, and modify attributes, navigate to :menuselection:`Sales app" +" --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:57 +msgid "" +"The order of attributes on the :guilabel:`Attributes` page dictates how they" +" appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` " +"dashboard, and :guilabel:`eCommerce` pages." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:61 +msgid "" +"To create a new attribute from the :guilabel:`Attributes` page, click " +":guilabel:`New`. Doing so reveals a blank attributes form that can be " +"customized and configured in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "A blank attribute creation form in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:68 +msgid "" +"First, create an :guilabel:`Attribute Name`, such as `Color` or `Size`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 +msgid "" +"Next, in the optional :guilabel:`Category` field, select a category from a " +"drop-down menu to group similar attributes under the same section for added " +"specificity and organization." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 +msgid "" +"To view the details related to the attribute category selected, click the " +"internal link :guilabel:`➡️ (arrow)` icon to the far-right of the " +":guilabel:`Category` field. Doing so reveals that attribute category's " +"detail form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"A standard attribute category detail page accessible via its internal link " +"arrow icon." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 +msgid "" +"Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at" +" the top. Followed by :guilabel:`Related Attributes` associated with the " +"category. These attributes can be dragged-and-dropped into a desirable order" +" of priority." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:86 +msgid "" +"Attributes can be directly added to the category, as well, by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:89 +msgid "" +"To create an attribute category directly from this field, start typing the " +"name of the new category, then select either :guilabel:`Create` or " +":guilabel:`Create and edit...` from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:93 +msgid "" +"Clicking :guilabel:`Create` creates the category, which can be modified " +"later. Clicking :guilabel:`Create and edit...` creates the category and " +"reveals a :guilabel:`Create Category` pop-up window, in which the new " +"attribute category can be configured and customized." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 +msgid "" +"Beneath the :guilabel:`Category` field are the :guilabel:`Display Type` " +"options. The :guilabel:`Display Type` determines how this product is shown " +"on the online store, :guilabel:`Point of Sale` dashboard, and " +":guilabel:`Product Configurator`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 +msgid "The :guilabel:`Display Type` options are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:103 +msgid "" +":guilabel:`Radio`: options appear in a bullet-style list on the product page" +" of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104 +msgid "" +":guilabel:`Pills`: options appear as selectable buttons on the product page " +"of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:105 +msgid "" +":guilabel:`Select`: options appear in a drop-down menu on the product page " +"of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 +msgid "" +":guilabel:`Color`: options appear as small, colored squares, which reflect " +"any HTML color codes set, on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "Display Types on Product Configurator on the online store in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:113 +msgid "" +"The :guilabel:`Variants Creation Mode` field informs Odoo when to " +"automatically create a new variant once an attribute is added to a product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:116 +msgid "" +":guilabel:`Instantly`: creates all possible variants as soon as attributes " +"and values are added to a product template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:118 +msgid "" +":guilabel:`Dynamically`: creates variants **only** when corresponding " +"attributes and values are added to a sales order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 +msgid ":guilabel:`Never (option)`: never automatically creates variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123 +msgid "" +"Once added to a product, an attribute's :guilabel:`Variants Creation Mode` " +"cannot be edited." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:125 +msgid "" +"Lastly, the :guilabel:`eCommerce Filter Visibility` field determines whether" +" these attribute options are visible to the customer on the front-end, as " +"they shop on the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 +msgid "" +":guilabel:`Visible`: the attribute values are visible to customers on the " +"front-end." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 +msgid "" +":guilabel:`Hidden`: the attribute values are hidden from customers on the " +"front-end." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:132 +msgid "Attribute values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:134 +msgid "" +"Attribute values should be added to the :guilabel:`Attribute Values` tab. " +"Values can be added to an attribute at any time, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 +msgid "" +"To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute " +"Values` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:139 +msgid "" +"Then, enter the name of the value in the :guilabel:`Value` column. Next, " +"check the box in the :guilabel:`Is custom value` column, if the value is " +"custom (i.e. the customer gets to provide unique specifications that are " +"specific to this particular value)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:144 +msgid "" +"If the :guilabel:`Display Type` - :guilabel:`Color` option is selected, the " +"option to add an HTML color code will appear to the far-right of the value " +"line, to make it easier for salespeople and customers to know exactly what " +"color option they're choosing." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Attribute values tab when add a line is clicked, showing the custom columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 +msgid "" +"To choose a color, click the blank circle in the :guilabel:`Color` column, " +"which reveals an HTML color selector pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"Selecting a color from the HTML color pop-up window that appears on " +"attribute form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:159 +msgid "" +"In this pop-up window, select a specific color by dragging the color slider " +"to a particular hue, and clicking on the color portion directly on the color" +" gradient window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:162 +msgid "" +"Or, choose a specific color by clicking the *dropper* icon, and selecting a " +"desired color that's currently clickable on the screen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166 +msgid "" +"Attributes can also be created directly from the product template by adding " +"a new line and typing the name into the :guilabel:`Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +msgid "" +"Once an attribute is added to a product, that product is listed and " +"accessible, via the attribute's :guilabel:`Related Products` smart button. " +"That button lists every product in the database currently using that " +"attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176 +msgid "" +"Once an attribute is created, use the attribute (and its values) to create a" +" product variant. To do that, go to :menuselection:`Sales app --> Products " +"--> Products`, and select an existing product to view that desired product's" +" form. Or, click :guilabel:`Create` to create a new product, to which a " +"product variant can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181 +msgid "" +"On the product form, click the :guilabel:`Attributes \\& Variants` tab to " +"view, manage, and modify attributes and values for the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "The attributes and values tab on a typical product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 +msgid "" +"To add an attribute to a product, and subsequent attribute values, click " +":guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then," +" choose the desired attribute from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:193 +msgid "" +"Attributes can be created directly from the :guilabel:`Attributes \\& " +"Variants` tab of a product form. To do that, start typing the name of the " +"new attribute in the blank field, and select either :guilabel:`Create` or " +":guilabel:`Create and edit...` from the mini drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:198 +msgid "" +"Clicking :guilabel:`Create` creates the attribute, which can be customized " +"later. Clicking :guilabel:`Create and edit...` creates the attribute, and a " +":guilabel:`Create Attribute` pop-up form appears. In the pop-up form, " +"proceed to modify the attribute in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 +msgid "" +"Once an attribute is selected in the :guilabel:`Attribute` column, proceed " +"to select the specific attribute values to apply to the product, via the " +"drop-down menu available in the :guilabel:`Values` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:207 +msgid "There is no limit to how many values can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:210 +msgid "" +"Similar product variant creation processes are accessible through the " +"Purchase, Inventory, and eCommerce applications." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214 +msgid "Configure variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:216 +msgid "" +"To the far-right of the attribute line is a :guilabel:`Configure` button. " +"When clicked, Odoo reveals a separate page showcasing those specific " +":guilabel:`Product Variant Values`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The Product Variant Values page accessible via the Configure button on a " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 +msgid "" +"Here, the specific :guilabel:`Value` name, :guilabel:`HTML Color Index` (if " +"applicable), and :guilabel:`Value Price Extra` are viewable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:227 +msgid "" +"The :guilabel:`Value Price Extra` represents the increase in the sales price" +" if the attribute is selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230 +msgid "" +"When a value is clicked on the :guilabel:`Product Variant Values` page, Odoo" +" reveals a separate page, detailing that value's related details." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"A Product Variant Values page accessible via the Product Variants Values " +"general page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:237 +msgid "" +"On the specific product variant detail page, the :guilabel:`Value` and " +":guilabel:`Value Price Extra` fields can be found, along with an " +":guilabel:`Exclude for` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:240 +msgid "" +"In the :guilabel:`Exclude for` field, different :guilabel:`Product " +"Templates` and specific :guilabel:`Attribute Values` can be added. When " +"added, this specific attribute value will be excluded from those specific " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:245 +msgid "Variants smart button" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247 +msgid "" +"When a product has attributes and variants configured in its " +":guilabel:`Attributes \\& Variants` tab, a :guilabel:`Variants` smart button" +" appears at the top of the product form. The :guilabel:`Variants` smart " +"button indicates how many variants are currently configured for that " +"specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The variants smart button at the top of the product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:255 +msgid "" +"When the :guilabel:`Variants` smart button is clicked, Odoo reveals a " +"separate page showcasing all the specific product variant combinations " +"configured for that specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst-1 +msgid "" +"The variants page accessible via the variants smart button on the product " +"form in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:263 +msgid "Impact of variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:265 +msgid "" +"In addition to offering more detailed product options to customers, product " +"variants have their own impacts that can be taken advantage of throughout " +"the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:268 +msgid "" +":guilabel:`Barcode`: barcodes are associated with each variant, instead of " +"the product template. Each individual variant can have its own unique " +"barcode/SKU." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270 +msgid "" +":guilabel:`Price`: every product variant has its own public price, which is " +"the sum of the product template price *and* any extra charges for particular" +" attributes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:274 +msgid "" +"A red shirt's sales price is $23 -- because the shirt's template price is " +"$20, plus an additional $3 for the red color variant. Pricelist rules can be" +" configured to apply to the product template, or to the variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:278 +msgid "" +":guilabel:`Inventory`: inventory is counted for each individual product " +"variant. On the product template form, the inventory reflects the sum of all" +" variants, but the actual inventory is computed by individual variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281 +msgid "" +":guilabel:`Picture`: each product variant can have its own specific picture." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:284 +msgid "" +"Changes to the product template automatically apply to every variant of that" +" product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:287 +msgid ":doc:`import`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:3 +msgid "Returns and refunds" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:5 +msgid "" +"The Odoo *Sales* app provides two different ways to process returns. The " +"method used depends on whether or not an invoice has been sent." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:9 +msgid "Before invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:11 +msgid "" +"Returns are completed using *Reverse Transfers* when a customer decides to " +"return a product **before** an invoice has been sent or validated." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:15 +msgid "" +"In order to use *Reverse Transfers*, the *Inventory* app **must** be " +"installed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:17 +msgid "" +"To start a return before invoicing, navigate to the :menuselection:`Sales` " +"app, select the desired sales order, and click on the :guilabel:`Delivery` " +"smart button to open the associated delivery order." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A typical sales order with a highlighted delivery smart button in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:25 +msgid "On the validated delivery order, click :guilabel:`Return`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A validated delivery order with a highlighted Return button in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:31 +msgid "This opens a :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:33 +msgid "" +"By default, the :guilabel:`Quantity` matches the validated quantities from " +"the delivery order. Update the quantities, if necessary. Click on the " +":guilabel:`🗑️ (trash)` icon next to a line item to remove it from the " +"return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The \"Reverse Transfer\" pop-up window, to make a return before invoicing " +"the customer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:41 +msgid "" +"Next, click :guilabel:`Return` to confirm the return. This generates a new " +"warehouse operation for the incoming returned product(s)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Warehouse operation after a return has been confirmed in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:48 +msgid "" +"Upon receiving the return, the warehouse team validates the warehouse " +"operation by clicking :guilabel:`Validate`. Then, on the original sales " +"order, the :guilabel:`Delivered` quantity updates to reflect the difference " +"between the initial validated quantities and the returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"The updated \"Delivered\" quantity on the sales order after the reverse " +"transfer." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:56 +msgid "" +"When an invoice is created, the customer receives an invoice **only** for " +"the products they are keeping, if any." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:60 +msgid "After invoicing" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:62 +msgid "" +"Sometimes, customers return an item after they receive and/or pay for their " +"invoice. In these cases, a return using only *Reverse Transfers* is " +"insufficient since validated, or sent, invoices cannot be changed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:66 +msgid "" +"However, *Reverse Transfers* can be used in conjunction with *Credit Notes* " +"to complete the customer's return." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:69 +msgid "" +"To start a return after invoicing, navigate to the relevant sales order in " +"the :menuselection:`Sales` app." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:72 +msgid "" +"If there is a payment registered on the sales order, the payment details " +"appear in the chatter, and the invoice (accessible through the " +":guilabel:`Invoices` smart button) has a green :guilabel:`In Payment` " +"banner." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Sample of a green in payment banner in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:80 +msgid "" +"From the sales order, click on the :guilabel:`Delivery` smart button to view" +" the validated delivery order. Then, click :guilabel:`Return` to open the " +":guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:83 +msgid "" +"Next, edit the :guilabel:`Product` and/or :guilabel:`Quantity`, as needed " +"for the return. Then, click :guilabel:`Return`. This generates a new " +"warehouse operation for the incoming returned product(s), which is validated" +" by the warehouse team once the return is received by clicking " +":guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:88 +msgid "" +"Then, on the sales order, the :guilabel:`Delivered` quantity updates to " +"reflect the difference between the initial validated quantities and the " +"returned quantities." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:91 +msgid "" +"To process a refund, navigate to the relevant invoice (from the sales order," +" click on the :guilabel:`Invoices` smart button). Then, click the " +":guilabel:`Credit Note` button at the top of the validated invoice." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "" +"A typical customer invoice with a Credit Note button highlighted in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:99 +msgid "Doing so reveals a :guilabel:`Credit Note` pop-up form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst-1 +msgid "Typical credit note pop-up form that appears in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:105 +msgid "" +"Start by entering a :guilabel:`Reason displayed on Credit Note` and a " +"specific :guilabel:`Journal` to process the credit. Then, select a specific " +":guilabel:`Reversal Date`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:108 +msgid "" +"After the information is filled in, click :guilabel:`Reverse` or " +":guilabel:`Reverse and Create Invoice`. Then, edit the draft, if needed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:111 +msgid "Lastly, click :guilabel:`Confirm` to confirm the credit note." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:113 +msgid "" +"When complete, a blue banner reading: :guilabel:`You have outstanding " +"credits for this customer. You can allocate them to mark this invoice as " +"paid.` appears at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/returns.rst:117 +msgid ":doc:`../../../finance/accounting/customer_invoices/credit_notes`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations.rst:5 +msgid "Send Quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:3 +msgid "Quotation deadlines" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:5 +msgid "" +"In the Odoo *Sales* application, it is possible to set deadlines on sales " +"quotations. Doing so encourages customers to act quickly during sales " +"negotiations, for they might fear for missing out on a good deal. As well, " +"deadlines also can also act as protection for a company in case an order has" +" to be fulfilled at a price that is no longer profitable for the business." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:11 +msgid "Quotation expiration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:13 +msgid "" +"In Odoo *Sales*, there's the option to add an expiration date to a " +"quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:15 +msgid "" +"To add an expiration date to a quotation, navigate to :menuselection:`Sales " +"app`, and select a desired quotation, or create a new one by clicking " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:18 +msgid "" +"On the quotation form, click the :guilabel:`Expiration` field to reveal a " +"pop-up calendar. From this pop-up calendar, select the desired month and " +"date as the expiration date for the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "The expiration field on a standard quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:26 +msgid "" +"By clicking the :guilabel:`Preview` button on a quotation, Odoo clearly " +"displays when that specific offer expires." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:0 +msgid "How customers will see deadlines on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:34 +msgid "Quotation template expiration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:36 +msgid "" +"The Odoo *Sales* application also makes it possible to add a deadline " +"expiration date to quotation templates." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:39 +msgid "" +"To add a deadline expiration date to a quotation template, navigate to " +":menuselection:`Sales app --> Configuration --> Quotation Templates`, and " +"either select the desired quotation template to which a deadline should be " +"added, or click :guilabel:`New` to build a new quotation template from " +"scratch." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:43 +msgid "" +"On the quotation template form, add a specific number of days to the " +":guilabel:`Quotation expires after` field, located beneath the quotation " +"template name. The number of days represents how long the quotation will be " +"valid for, before it expires." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst-1 +msgid "" +"The quotation expires after field on a quotation template form in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:51 +msgid "" +"Then, whenever that specific quotation template is used in a quote, an " +"expiration date is automatically calculated, based on the number of days " +"designated above. However, this date can be overwritten before sending the " +"quotation to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/deadline.rst:56 +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:227 +msgid ":doc:`/applications/sales/sales/send_quotations/quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:3 +msgid "Deliveries and invoices to different addresses" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:5 +msgid "" +"People and businesses often use separate addresses for billing (invoicing) " +"and shipping (delivery) purposes. With the Odoo *Sales* app, contacts can " +"have different specified addresses for delivery and invoicing." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:12 +msgid "" +"To properly utilize multiple addresses in Odoo, go to :menuselection:`Sales " +"app --> Configuration --> Settings` and scroll down to the " +":guilabel:`Quotations & Orders` heading. Then, check the box next to " +":guilabel:`Customer Addresses`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Activate the Customer Addresses setting." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:21 +msgid "Contact form configuration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:23 +msgid "" +"To add multiple addresses to a contact, go to :menuselection:`Sales app --> " +"Orders --> Customers`, and clear any default filters from the search bar. " +"Then, click on the desired customer to open their contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:28 +msgid "Contact forms can be accessed in the *Contacts* application, as well." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:30 +msgid "" +"From the contact form, click :guilabel:`Edit`, and then select " +":guilabel:`Add`, which is located under the :guilabel:`Contacts & Addresses`" +" tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which " +"additional addresses can be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:38 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field to reveal a drop-down menu of address-" +"related options." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:41 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:43 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:44 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:45 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:46 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:47 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:49 +msgid "" +"Once an option is selected, proceed to enter the corresponding contact " +"information that should be used for the specified address type." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:56 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address and immediately input another one." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:60 +msgid "Address added to quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:62 +msgid "" +"When a customer is added to a quotation, the :guilabel:`Invoice Address` and" +" :guilabel:`Delivery Address` fields autopopulate with the corresponding " +"addresses specified on the customer's contact form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst-1 +msgid "Invoice and Delivery Addresses autopopulate on a quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:70 +msgid "" +"The :guilabel:`Invoice Address` and :guilabel:`Delivery Address` can also be" +" edited directly from the quotation by clicking the :guilabel:`Edit` button," +" and then clicking the :guilabel:`➡️ (right arrow)` internal link buttons " +"next to each address line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:74 +msgid "" +"These addresses can be updated at any time to ensure accurate invoicing and " +"delivery." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/different_addresses.rst:77 +msgid "" +"If any changes are made on a form in Odoo, include *Contacts* forms, " +"remember to click :guilabel:`Save` to save the changes to the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:3 +msgid "Online payment order confirmation" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:5 +msgid "" +"The Odoo *Sales* application provides customers with the ability to confirm " +"orders, via an online payment, directly on a sales order. Once the sales " +"order is electronically paid for by the customer, the salesperson attached " +"to the sales order is instantly notified that the order is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:10 +msgid "Activate online payments" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:12 +msgid "" +"In order to have customers confirm orders with an online payment, the " +"*Online Payment* setting **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:15 +msgid "" +"To activate the *Online Payment* feature, go to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " +"Orders` heading, check the box next to the :guilabel:`Online Payment` " +"feature, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:23 +msgid "" +"Beneath the :guilabel:`Online Payment` option on the *Sales* " +":guilabel:`Settings` page, there's a :guilabel:`Default Quotation Validity` " +"field. In this field, there's the option to add a specific number of days " +"for quotations to remain valid by default." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:27 +msgid "" +"To enable this feature on a standard quotation, click the checkbox for the " +":guilabel:`Payment` feature option, located in the :guilabel:`Online " +"confirmation` field, on the :guilabel:`Other Info` tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting on a standard quotation in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:35 +msgid "" +"To enable this feature on a quotation template, click the checkbox for the " +":guilabel:`Payment` feature option, located in the :guilabel:`Online " +"confirmation` field of the quotation template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The online payment setting on quotation template forms in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:43 +msgid "Payment providers" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:45 +msgid "" +"After activating the :guilabel:`Online Payment` feature, a link to configure" +" :guilabel:`Payment Providers` appears beneath it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:48 +msgid "" +"Clicking that link reveals a separate :guilabel:`Payment Providers` page, in" +" which a large variety of payment providers can be enabled, customized, and " +"published." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "Payment providers page in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:56 +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:91 +msgid ":doc:`../../../finance/payment_providers`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:59 +msgid "Register a payment" +msgstr "ลงทะเบียนการชําระเงิน" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:61 +msgid "" +"After opening quotations in their customer portal, customers can click " +":guilabel:`Accept \\& Pay` to confirm their order with an online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "The accept and pay button on an online quotation in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:68 +msgid "" +"After clicking :guilabel:`Accept \\& Pay`, customers are presented with " +":guilabel:`Validate Order` pop-up window containing different options for " +"them to make online payments, in the :guilabel:`Pay with` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "" +"How to register a payment on a validate order pop-up window in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:77 +msgid "" +"Odoo will **only** offer payment options on the :guilabel:`Validate Order` " +"pop-up window that have been published and configured on the " +":guilabel:`Payment Providers` page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:80 +msgid "" +"Once the customer selects their desired method of payment, they will click " +"the :guilabel:`Pay` button on the pop-up window to confirm the order. Odoo " +"instantly notifies the assigned salesperson upon order confirmation with an " +"online payment." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst-1 +msgid "" +"Sample of notification that appears in the chatter when an online payment is" +" made." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:89 +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:77 +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:99 +msgid ":doc:`quote_template`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_paid_to_validate.rst:90 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:245 +msgid ":doc:`get_signature_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:3 +msgid "Online signatures for order confirmations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:5 +msgid "" +"The Odoo *Sales* application provides customers with the ability to confirm " +"orders, via an online signature, directly on the sales order. Once the sales" +" order is electronically signed by the customer, the salesperson attached to" +" the sales order is instantly notified that the order is confirmed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:11 +msgid "Activate online signatures" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:13 +msgid "" +"In order to have customers confirm orders with an online signature, the " +"*Online Signature* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:16 +msgid "" +"To activate the *Online Signature* feature, go to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Quotations \\& " +"Orders` heading, and activate the :guilabel:`Online Signature` feature by " +"checking the box beside it." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "" +"The Online Signature feature option in the Settings of the Odoo Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:24 +msgid "Then, click the :guilabel:`Save` button in the top-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:27 +msgid "" +"When making a quotation template, the online signature feature is the " +":guilabel:`Signature` option, located in the :guilabel:`Online confirmation`" +" field of the quotation template form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 +msgid "" +"The Online confirmation signature option found on every quotation template " +"in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:34 +msgid "" +"On standard quotations, the online signature feature is the " +":guilabel:`Signature` option, located under the :guilabel:`Other Info` tab " +"of the quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:0 +msgid "" +"The online signature feature option in the Other Info tab of a quotation " +"form in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:42 +msgid "Order confirmations with online signatures" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:44 +msgid "" +"When clients access quotations online through their customer portal, there's" +" a :guilabel:`Sign \\& Pay` button directly on the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "The Sign and Pay button present on online quotations in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:51 +msgid "" +"When clicked, a :guilabel:`Validate Order` pop-up window appears. In this " +"pop-up window, the :guilabel:`Full Name` field is auto-populated, based on " +"the contact information in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst-1 +msgid "The Validate Order pop-up window for online signatures in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:58 +msgid "" +"Then, customers have the option to enter an online signature with any of the" +" following options: :guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:61 +msgid "" +":guilabel:`Auto` lets Odoo automatically generate an online signature based " +"on the information in the :guilabel:`Full Name` field. :guilabel:`Draw` lets" +" the customer use the cursor to create a custom signature directly on the " +"pop-up window. And :guilabel:`Load` lets the customer upload a previously-" +"created signature file from their computer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:66 +msgid "" +"After the customer has chosen any of the three previously mentioned " +"signature options (:guilabel:`Auto`, :guilabel:`Draw`, or :guilabel:`Load`)," +" they will click the :guilabel:`Accept \\& Sign` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:70 +msgid "" +"When :guilabel:`Accept \\& Sign` is clicked, the various payment method " +"options become available for them to choose from (if the *online payment* " +"option applies to this quotation)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:73 +msgid "" +"Then, when the quotation is paid and confirmed, a delivery order is " +"automatically created (if the Odoo *Inventory* app is installed)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/get_signature_to_validate.rst:78 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:246 +msgid ":doc:`get_paid_to_validate`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:3 +msgid "Optional products" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:5 +msgid "" +"The use of optional products is a marketing strategy that involves the " +"cross-selling of products along with a core product. The aim is to offer " +"useful and related products to customers, which may result in an increased " +"sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:9 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:162 +msgid "" +"For instance, if a customer wants to buy a car, they have the choice to " +"order massaging seats, as well, or ignore the offer and simply buy the car. " +"Presenting the choice to purchase optional products enhances the customer " +"experience." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:14 +msgid "Optional products on quotations" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:16 +msgid "" +"With the Odoo *Sales* application, it is possible to add or modify optional " +"products directly on quotations by navigating to the :guilabel:`Optional " +"Products` tab on a quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "How to add optional products to your quotations on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:23 +msgid "" +"To add an optional product(s) to a quotation, click :guilabel:`Add a " +"product` in the :guilabel:`Optional Products` tab of a quotation. Doing so " +"reveals a blank field in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:27 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:179 +msgid "" +"When clicked, a drop-down menu with products from the database appear. " +"Select the desired product from the drop-down menu to add it as an optional " +"product to the quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:31 +msgid "" +"If the desired product isn't readily visible, type the name of the desired " +"product in the field, and the option appears in the drop-down menu. Then, " +"select that desired product to add it to the quotation." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:36 +msgid "" +"When a product is added, the default :guilabel:`Quantity` is `1`, but that " +"can be edited at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:39 +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:182 +msgid "" +"To delete any line item from the :guilabel:`Optional Products` tab, click " +"the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:42 +msgid "" +"Click the :guilabel:`Preview` button, located in the upper-left corner of " +"the quotation, to reveal a preview of the quotation customers would receive," +" via email, along with the optional products they can potentially add to " +"their order, located in the :guilabel:`Options` section." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst-1 +msgid "Preview your quotations on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:50 +msgid "" +"Customers are able to add different optional products to an order by " +"clicking the :guilabel:`🛒 (shopping cart)` icon, located to the right of the" +" optional product line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:53 +msgid "" +"If a customer selects optional products, these are automatically added to " +"the quotation managed by the salesperson." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:56 +msgid "" +"When the customer adds an optional product(s) to an order, the salesperson " +"is instantly notified about the change, along with any other change the " +"customer makes to an order. This allows salespeople to stay up-to-date with " +"everything related to an order in the backend of the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:62 +msgid "Optional products on quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:65 +msgid "" +"Be sure to review the :doc:`quote_template` documentation to better " +"understand how quotation templates work before reading the following " +"information." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:68 +msgid "" +"For quotation templates, just like a typical quotation form, there is also " +"an :guilabel:`Optional Products` tab, wherein related products or services " +"can be added to a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:71 +msgid "" +"To add optional products to a quotation template, navigate to " +":menuselection:`Sales app --> Configuration --> Quotation Templates`. Then, " +"either select an existing quotation template to edit, or create a new one by" +" clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:75 +msgid "" +"On the quotation template form, click the :guilabel:`Optional Products` tab." +" Under the :guilabel:`Optional Products` tab, click :guilabel:`Add a line`, " +"and select the desired product to add as an optional product to the " +"quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:83 +msgid "" +"The products added in the :guilabel:`Optional Products` tab are present in " +"the quotation, by default, whenever that particular quotation template is " +"used. These products can be removed, and additional products can be added, " +"before the quotation is sent to a customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:88 +msgid "" +"It's best to offer optional products that would encourage a customer to add " +"additional items to their order, or entice them to purchase a more expensive" +" version of their initially selected product." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:92 +msgid "" +"For example, if a customer purchases a wooden chair, some optional products " +"could be: a warranty on that chair and/or a wooden chair with leather seats." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:96 +msgid "" +"There is no limit to how many optional products can be added to a quotation " +"template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:3 +msgid "Product variants on quotations and sales orders" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:5 +msgid "" +"Before getting into detail about how to use product variants on quotations " +"and sales orders, it's recommended to learn about " +":doc:`../products_prices/products/variants` in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:8 +msgid "" +"Once familiarized with the basics surrounding product variants, the " +"following covers how product variants can be added to quotations and sales " +"orders using the *product configurator* or *order grid entry*." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:13 +msgid "" +"It should be noted that the setting is titled, *Variant Grid Entry* on the " +"*Sales* app settings page, and titled, *Order Grid Entry* on product forms. " +"So, be sure to keep that in mind." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:19 +msgid "" +"When working with product variants, Odoo uses the product configurator, by " +"default. To add the variant grid entry option, that feature **must** be " +"enabled in the Odoo *Sales* application. The variant grid entry option " +"provides a pop-up window on the quotation/sales order to simplify the " +"variant selection process." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:24 +msgid "" +"To enable that setting, go to :menuselection:`Sales app --> Configuration " +"--> Settings`, and scroll to the :guilabel:`Product Catalog` section. Then, " +"check the box next to the :guilabel:`Variant Grid Entry` option, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "The variant grid entry setting in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:33 +msgid "" +"Of course, the :guilabel:`Variants` feature **must** also be activated, in " +"order to use product variants on quotations and sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:37 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:39 +msgid "" +"Once the :guilabel:`Variant Grid Entry` setting is enabled, both options " +"(*Product Configurator* and *Order Grid Entry*) become available on every " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:42 +msgid "" +"To configure a product form to use either a product configurator or variant " +"grid entry, start by navigating to :menuselection:`Sales app --> Products " +"--> Products` to view all the products in the database." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:46 +msgid "" +"Then, select the desired product to configure, or click :guilabel:`New`, to " +"create a new product from scratch. Once on the product form, click into the " +":guilabel:`Attributes \\& Variants` tab, where product variants can be " +"viewed, modified, and added." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:50 +msgid "" +"At the bottom of the :guilabel:`Attributes \\& Variants` tab, there is a " +":guilabel:`Sales Variant Selection` section with two options: " +":guilabel:`Product Configurator` and :guilabel:`Order Grid Entry`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:55 +msgid "" +"It should be noted that these options **only** appear if at least two values" +" of an attribute have been added to the record." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"Sales variant selection options on the attributes and variants tab on " +"product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:62 +msgid "" +"These options determine which method is used when adding product variants to" +" quotations or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:65 +msgid "" +"The :guilabel:`Product Configurator` provides a pop-up window that neatly " +"displays all the available product variants for that particular product when" +" it's added to a quotation. However, only one variant can be selected/added " +"at a time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:69 +msgid "" +"The :guilabel:`Order Grid Entry` provides the same information as the " +":guilabel:`Product Configurator` in a table layout, allowing the user to " +"select larger numbers of unique product variants, and add them to a " +"quotation/sales order, in a single view." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:74 +msgid "Product configurator" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:76 +msgid "" +"The product configurator feature appears as a :guilabel:`Configure` pop-up " +"window, as soon as a product with (at least two) variants is added to a " +"quotation or sales order, but **only** if the :guilabel:`Product " +"Configurator` option is selected on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"The product configurator pop-up window that appears on a quotation or sales " +"order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:85 +msgid "" +"This :guilabel:`Configure` pop-up window also appears if the " +":guilabel:`Order Grid Entry` setting is **not** activated, as it is the " +"default option Odoo uses when dealing with product variants on quotations " +"and/or sales orders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:89 +msgid "" +"The :guilabel:`Product Configurator` option lets salespeople choose exactly " +"which product variant to add to the quotation or sales order using a format " +"similar to online shopping." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:93 +msgid "Order grid entry" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:95 +msgid "" +"The order grid entry feature appears as a :guilabel:`Choose Product " +"Variants` pop-up window, as soon as a product with (at least two) variants " +"is added to a quotation or sales order, but **only** if the :guilabel:`Order" +" Grid Entry` option is selected on its product form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"The choose product variants pop-up window that appears on a quotation in " +"Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:103 +msgid "" +"The :guilabel:`Choose Product Variants` pop-up window features all the " +"variant options for that particular product. From this pop-up window, the " +"salesperson can designate how many of each variant they'd like to add to the" +" quotation/sales order at once." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:107 +msgid "" +"When all the desired quantities and variants have been selected, the " +"salesperson simply clicks :guilabel:`Confirm`, and those orders are " +"instantly added to the quotation/sales order in the :guilabel:`Order Lines` " +"tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst-1 +msgid "" +"Populated order lines tab after order grid entry has been chosen to select " +"products." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/orders_and_variants.rst:116 +msgid ":doc:`../products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:3 +msgid "PDF quote builder" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:5 +msgid "" +"The *PDF Quote Builder* in Odoo *Sales* provides the opportunity to send " +"customers a fully customized PDF file for quotes, showcasing the company and" +" products, with various information and design elements, instead of just " +"showing the price and total." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:9 +msgid "" +"The PDF Quote Builder groups header pages, product descriptions, the " +"price(s), and footer pages to create a detailed quote. It can also inject " +"dynamic texts in the PDF to personalize the offer for the customer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:13 +msgid "" +"Having a customized PDF in quotes provides a heightened conclusion to the " +"shopping experience for customers, and adds an elegant level of " +"professionalism to a company." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:17 +msgid "" +"`Odoo Quick Tips - Create a PDF quote [video] " +"<https://www.youtube.com/watch?v=tQNydBZt-VI>`_" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:20 +msgid "" +"It is recommended to edit PDF forms with Adobe software. The form fields on " +"the header and footer PDF templates are necessary to get dynamic values with" +" Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:26 +msgid "" +"In order to add custom PDF files for quotes, the :guilabel:`PDF Quote " +"builder` feature *must* be configured." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:29 +msgid "" +"To do that, navigate to :menuselection:`Sales app --> Configuration --> " +"Settings`. Then, on the :guilabel:`Settings` page, scroll to the " +":guilabel:`Quotations & Orders` section, and locate the :guilabel:`PDF Quote" +" builder` feature." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"The PDF Quote Builder feature located on the Settings page of the Sales " +"application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:37 +msgid "" +"Here, custom :guilabel:`Header pages` and :guilabel:`Footer pages` can be " +"uploaded. To upload either, click the :guilabel:`Upload your file` button, " +"or the :guilabel:`✏️ (pencil)` icon to the right of the desired field, and " +"proceed to locate, select, and upload the desired PDF file." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:42 +msgid "" +"Headers and footers can also be added directly in a quotation template, so " +"it's possible to have different variations per template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:45 +msgid "" +"Clicking the :guilabel:`🗑️ (trash)` icon deletes the current PDF file and " +"replaces the blank field with an :guilabel:`Upload your file` button." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:48 +msgid "" +"Once the desired PDF file(s) are uploaded in the appropriate fields in the " +":guilabel:`PDF Quote builder` section of the *Sales* :guilabel:`Settings` " +"page, be sure to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:51 +msgid "The files uploaded here will be the default PDF used for all quotes." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:54 +msgid "Values set in the PDF Quote Builder settings are company-specific." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:57 +msgid "Dynamic text in PDFs" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:59 +msgid "" +"While creating custom PDFs for quotes, use *dynamic text* for Odoo to auto-" +"fill the PDF content with information related to the quote from the Odoo " +"database, like names, prices, etc." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:62 +msgid "" +"Dynamic text values are form components (text inputs) that can be added in a" +" PDF file, and Odoo automatically fills those values in with information " +"related to the quote." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:66 +msgid "Dynamic text values" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:68 +msgid "" +"Below are common dynamic text values used in custom PDFs, and what they " +"represent:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:70 +msgid ":guilabel:`name`: Sales Order Reference" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:71 +msgid ":guilabel:`partner_id__name`: Customer Name" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:72 +msgid ":guilabel:`user_id__name`: Salesperson Name" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:73 +msgid ":guilabel:`amount_untaxed`: Untaxed Amount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:74 +msgid ":guilabel:`amount_total`: Total Amount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:75 +msgid ":guilabel:`delivery_date`: Delivery Date" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:76 +msgid ":guilabel:`validity_date`: Expiration Date" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:77 +msgid ":guilabel:`client_order_ref`: Customer Reference" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:80 +msgid "" +"Double underscore notation for :guilabel:`partner_id__name` and " +":guilabel:`user_id__name` values are used in place of the typically used `.`" +" symbol because the library currently does not support the `.` symbol." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:84 +msgid "Product-specific dynamic text values are as follows:" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:86 +msgid ":guilabel:`description`: Product Description" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:87 +msgid ":guilabel:`quantity`: Quantity" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:88 +msgid ":guilabel:`uom`: Unit of Measure (UoM)" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:89 +msgid ":guilabel:`price_unit`: Price Unit" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:90 +msgid ":guilabel:`discount`: Discount" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:91 +msgid ":guilabel:`product_sale_price`: Product List Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:92 +msgid ":guilabel:`taxes`: Taxes name joined by a comma (`,`)" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:93 +msgid ":guilabel:`tax_excl_price`: Tax Excluded Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:94 +msgid ":guilabel:`tax_incl_price`: Tax Included Price" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:97 +msgid "" +"When a PDF is built, it's best practice to use common dynamic text values " +"(:guilabel:`name` and :guilabel:`partner_id_name`). When uploaded into the " +"database, Odoo auto-populates those fields with the information from their " +"respective fields." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:101 +msgid "" +"In this case, Odoo would auto-populate the Sales Order Reference in the " +":guilabel:`name` dynamic text field, and the Customer Name in the " +":guilabel:`partner_id_name` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "PDF quote being built using common dynamic placeholders." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:108 +msgid "" +"Once the PDF file(s) are complete, save them to the computer's hard drive, " +"and proceed to upload them to Odoo via :menuselection:`Sales app --> " +"Configuration --> Settings --> PDF Quote builder`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:111 +msgid "" +"Upload the created PDF in the :guilabel:`Header pages` or :guilabel:`Footer " +"pages` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:113 +msgid "Once the upload(s) are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:116 +msgid "Add PDF to product" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:118 +msgid "" +"In Odoo *Sales*, it's also possible to add a custom PDF to a product form. " +"When a PDF is added to a product, and that product is used in a quotation, " +"that PDF is also inserted in the final PDF." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:121 +msgid "" +"To add a custom PDF to a product, start by navigating to " +":menuselection:`Sales app --> Products --> Products`, and select the desired" +" product to which a custom PDF should be added." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:125 +msgid "" +"A document could also be added to a product variant, instead of a product. " +"If there are documents on a product *and* on its variant, **only** the " +"documents in the variant are shown." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:128 +msgid "" +"To add a custom document to a product variant, navigate to " +":menuselection:`Sales app --> Products --> Product Variants`. Select the " +"desired variant, click the :guilabel:`Documents` smart button, and proceed " +"to upload the custom document(s) to the specific product variant." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:132 +msgid "" +"On the product page, click the :guilabel:`Documents` smart button at the top" +" of the page." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "The Documents smart button on a product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:138 +msgid "" +"Doing so reveals a separate :guilabel:`Documents` page for that product, " +"wherein files related to that product can be uploaded. From this page, " +"either click :guilabel:`New` or :guilabel:`Upload`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:141 +msgid "" +"Clicking :guilabel:`Upload` instantly provides the opportunity to upload the" +" desired document. Then, the document can be further configured on the " +"document card, or by clicking the three dots icon in the top right corner of" +" the document card, and then clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:145 +msgid "" +"Clicking :guilabel:`New` reveals a blank documents form, in which the " +"desired PDF can be uploaded via the :guilabel:`Upload your file` button on " +"the form, located in the :guilabel:`File Content` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"A standard document form with various fields for a specific product in Odoo " +"Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:153 +msgid "" +"Various information and configurations related to the uploaded document can " +"be modified here." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:155 +msgid "" +"The first field on the documents form is for the :guilabel:`Name` of the " +"document, and it is grayed-out (not clickable) until a document is uploaded." +" Once a PDF has been uploaded, the :guilabel:`Name` field is auto-populated " +"with the name of the PDF, and it can then be edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:159 +msgid "" +"Prior to uploading a document, there's the option to designate whether the " +"document is a :guilabel:`File` or :guilabel:`URL` from the :guilabel:`Type` " +"drop-down field menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "A standard document form with an uploaded pdf in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:167 +msgid "" +"If a PDF is uploaded, the :guilabel:`Type` field is auto-populated to " +":guilabel:`File`, and it cannot be modified." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:170 +msgid "" +"Then, in the :guilabel:`Sales` section, in the :guilabel:`Visible at` field," +" click the drop-down menu, and select either: :guilabel:`Quotation`, " +":guilabel:`Confirmed order`, or :guilabel:`Inside quote`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:174 +msgid "" +":guilabel:`Quotation`: the document is sent to (and accessible by) customers" +" at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:176 +msgid "" +":guilabel:`Confirmed order`: the document is sent to customers upon the " +"confirmation of an order. This is best for user manuals and other " +"supplemental documents." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:179 +msgid "" +":guilabel:`Inside quote`: the document is included in the PDF of the " +"quotation, between the header pages and the :guilabel:`Pricing` section of " +"the quote." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:183 +msgid "" +"When the :guilabel:`Inside quote` option for the :guilabel:`Visible at` " +"field is chosen, and the custom PDF file, `Sample Builder.pdf` is uploaded, " +"the PDF is visible on the quotation the in the *customer portal* under the " +":guilabel:`Documents` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "" +"Sample of an uploaded pdf with the inside quote option chosen in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:191 +msgid "" +"Lastly, in the :guilabel:`E-Commerce` section, decide whether or not to " +":guilabel:`Show on product page` on the front-end (in the online store)." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:195 +msgid "" +"When the :guilabel:`Show on product page` option is enabled, a link to the " +"uploaded document, `Sample Builder.pdf`, appears on the product's page, " +"located on the frontend in the online store." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:198 +msgid "" +"It appears beneath a :guilabel:`Documents` heading, with a link showcasing " +"the name of the uploaded document." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:0 +msgid "" +"Showing a link to an uploaded document on a product page using Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:206 +msgid "PDF quote" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:208 +msgid "" +"Once a quote with a pre-configured PDF has been confirmed, Odoo provides the" +" option to print the confirmed quote to check for errors, or to keep for " +"records." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:211 +msgid "" +"To print the PDF quote, navigate to the confirmed quote, and click the " +":guilabel:`⚙️ (gear)` icon to reveal a drop-down menu. From this drop-down " +"menu, select :guilabel:`Print`, then select :guilabel:`PDF Quote`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst-1 +msgid "" +"Print pdf quote option on drop-down menu located on confirmed sales order in" +" Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:219 +msgid "" +"Doing so instantly downloads the PDF quote. When opened, the PDF quote, " +"along with the configured product PDF that was set to be visible inside the " +"quote, can be viewed and printed." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/pdf_quote_builder.rst:223 +msgid "" +"Download these :download:`PDF quote builder examples " +"<pdf_quote_builder/pdfquotebuilderexamples.zip>` for added reference." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:3 +msgid "Quotation templates" +msgstr "เทมเพลตใบเสนอราคา" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:5 +msgid "" +"In Odoo *Sales*, salespeople have the ability to create reusable quotation " +"templates for common products or services that the business offers." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:8 +msgid "" +"By using these templates, quotations can be tailored and sent to customers " +"at a much faster pace, without having to create new quotations from scratch " +"every time a sales negotiation occurs." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:16 +msgid "" +"Begin by activating the setting in :menuselection:`Sales app --> " +"Configuration --> Settings`, and scroll to the :guilabel:`Quotations \\& " +"Orders` heading." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:19 +msgid "" +"In that section, check the box beside the :guilabel:`Quotation Templates` " +"option. Doing so reveals a new :guilabel:`Default Template` field, in which " +"a default quotation template can be chosen from a drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "How to enable quotation templates on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:27 +msgid "" +"Also, upon activating the :guilabel:`Quotation Template` feature, an " +"internal :guilabel:`➡️ Quotation Templates` link appears beneath the " +":guilabel:`Default Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:30 +msgid "" +"Clicking that link reveals the :guilabel:`Quotation Templates` page, from " +"which templates can be created, viewed, and edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:33 +msgid "" +"Before leaving the :guilabel:`Settings` page, don't forget to click the " +":guilabel:`Save` button to save all changes made during the session." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:37 +msgid "Create quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:39 +msgid "" +"Click the :guilabel:`Quotation Templates` link on the :guilabel:`Settings` " +"page, or navigate to :menuselection:`Sales app --> Configuration --> " +"Quotation Templates`. Both options reveal the :guilabel:`Quotation " +"Templates` page, where quotation templates can be created, viewed, and " +"edited." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Quotation templates page in the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:47 +msgid "" +"To create a new quotation template, click the :guilabel:`New` button, " +"located in the upper-left corner. Doing so reveals a blank quotation " +"template form that can be customized in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Create a new quotation template on Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:54 +msgid "" +"Start by entering a name for the template in the :guilabel:`Quotation " +"Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:56 +msgid "" +"Then, in the :guilabel:`Quotation Validity` field, designate how many days " +"the quotation template will remain valid for, or leave the field on the " +"default `0` to keep the template valid indefinitely." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:60 +msgid "" +"Next, in the :guilabel:`Confirmation Mail` field, click the blank field to " +"reveal a drop-down menu. From the drop-down menu, select a pre-configured " +"email template to be sent to customers upon confirmation of an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:65 +msgid "" +"To create a new email template directly from the :guilabel:`Confirmation " +"Mail` field, start typing the name of the new email template in the field, " +"and select either: :guilabel:`Create` or :guilabel:`Create and edit...` from" +" the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:69 +msgid "" +"Selecting :guilabel:`Create` creates the email template, which can be edited" +" later." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:71 +msgid "" +"Selecting :guilabel:`Create and edit...` creates the email template, and a " +":guilabel:`Create Confirmation Mail` pop-up window appears, in which the " +"email template can be customized and configured right away." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "" +"Create confirmation mail pop-up window from the quotation template form in " +"Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:79 +msgid "" +"When all modifications are complete, click :guilabel:`Save \\& Close` to " +"save the email template and return to the quotation form." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:82 +msgid "" +"If working in a multi-company environment, use the :guilabel:`Company` field" +" to designate to which company this quotation template applies." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:85 +msgid "" +"If a journal is set in the :guilabel:`Invoicing Journal` field, all sales " +"orders with this template will invoice in that specified journal. If no " +"journal is set in this field, the sales journal with the lowest sequence is " +"used." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:89 +msgid "" +"If the :guilabel:`Online Signature` and/or :guilabel:`Online Payment` " +"features are activated in the :guilabel:`Settings` (:menuselection:`Sales " +"app --> Configuration --> Settings`), those options are available on " +"quotation template forms." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:93 +msgid "" +"Check the box beside :guilabel:`Online Signature` to request an online " +"signature from the customer to confirm an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:96 +msgid "" +"Check the box beside :guilabel:`Online Payment` to request an online payment" +" from the customer to confirm an order. When :guilabel:`Online Payment` is " +"checked, a new percentage field appears, in which a specific percentage of " +"payment can be entered." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:100 +msgid "" +"Both options, :guilabel:`Online Signature` and :guilabel:`Online Payment` " +"can be enabled simultaneously, in which case the customer must provide " +"**both** a signature **and** a payment to confirm an order." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:104 +msgid "" +"In the :guilabel:`Recurring Plan` field, choose from a variety of pre-" +"configured amounts of time (e.g. :guilabel:`Monthly`, :guilabel:`Quarterly`," +" etc.) to designate how often this quotation template should occur." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:109 +msgid "" +"The :guilabel:`Recurring Plan` field **only** applies to subscription plans." +" For more information, check out the documentation on " +":doc:`../../subscriptions/plans`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:113 +msgid "Lines tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:115 +msgid "" +"In the :guilabel:`Lines` tab, products can be added to the quotation " +"template by clicking :guilabel:`Add a product`, organized by clicking " +":guilabel:`Add a section` (and dragging/dropping section headers), and " +"further explained with discretionary information (such as warranty details, " +"terms, etc.) by clicking :guilabel:`Add a note`." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:120 +msgid "" +"To add a product to a quotation template, click :guilabel:`Add a product` in" +" the :guilabel:`Lines` tab of a quotation template form. Doing so reveals a " +"blank field in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:123 +msgid "" +"When clicked, a drop-down menu with existing products in the database " +"appear. Select the desired product from the drop-down menu to add it to the " +"quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:127 +msgid "" +"If the desired product isn't readily visible, type the name of the desired " +"product in the :guilabel:`Product` field, and the option appears in the " +"drop-down menu. Products can also be found by clicking :guilabel:`Search " +"More...` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:132 +msgid "" +"When a product is added to a quotation template, the default " +":guilabel:`Quantity` is `1`, but that can be edited at any time." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:135 +msgid "" +"Then, drag-and-drop the product to the desired position, via the " +":guilabel:`six squares` icon, located to the left of each line item." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:138 +msgid "" +"To add a *section*, which serves as a header to organize the lines of a " +"sales order, click :guilabel:`Add a section` in the :guilabel:`Lines` tab. " +"When clicked, a blank field appears, in which the desired name of the " +"section can be typed. When the name has been entered, click away to secure " +"the section name." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:143 +msgid "" +"Then, drag-and-drop the section name to the desired position, via the " +":guilabel:`six squares` icon, located to the left of each line item." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:146 +msgid "" +"To add a note, which would appear as a piece of text for the customer on the" +" quotation, click :guilabel:`Add a note` in the :guilabel:`Lines` tab. When " +"clicked, a blank field appears, in which the desired note can be typed. When" +" the note has been entered, click away to secure the note." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:150 +msgid "" +"Then, drag-and-drop the note to the desired position, via the :guilabel:`six" +" squares` icon." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:152 +msgid "" +"To delete any line item from the :guilabel:`Lines` tab (product, section, " +"and/or note), click the :guilabel:`🗑️ (trash can)` icon on the far-right " +"side of the line." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:156 +msgid "Optional Products tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:158 +msgid "" +"The use of *optional products* is a marketing strategy that involves the " +"cross-selling of products along with a core product. The aim is to offer " +"useful and related products to customers, which may result in an increased " +"sale." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:166 +msgid "" +"Optional products appear as a section on the bottom of sales orders and " +"eCommerce pages. Customers can immediately add them to their online sales " +"orders themselves, if desired." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Optional products appearing on a typical sales order with Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:173 +msgid "" +"In the :guilabel:`Optional Products` tab, :guilabel:`Add a line` for each " +"cross-selling product related to the original items in the :guilabel:`Lines`" +" tab, if applicable. The products added here ideally complement the original" +" offering as added value for the prospective buyer." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:177 +msgid "" +"Clicking :guilabel:`Add a line` reveals a blank field in the " +":guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:186 +msgid "Optional products are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:189 +msgid "Terms \\& Conditions tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:191 +msgid "" +"The :guilabel:`Terms \\& Conditions` tab provides the opportunity to add " +"terms and conditions to the quotation template. To add terms and conditions," +" simply type (or copy/paste) the desired terms and conditions in this tab." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:196 +msgid ":doc:`../../../finance/accounting/customer_invoices/terms_conditions`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:199 +msgid "" +"Terms and conditions are **not** required to create a quotation template." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:202 +msgid "PDF Quote Builder tab" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:204 +msgid "" +"The :guilabel:`PDF Quote Builder` tab provides options to compose an " +"attractive quotation, with more information and visually-pleasing elements, " +"to highlight products and/or services." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:207 +msgid "" +"To upload customer :guilabel:`Header pages` and :guilabel:`Footer pages`, " +"click the :guilabel:`✏️ (pencil)` icon to the right of the respective pages." +" Click the :guilabel:`🗑️ (trash)` icon to delete an uploaded PDF." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:212 +msgid ":doc:`/applications/sales/sales/send_quotations/pdf_quote_builder`" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:215 +msgid "Use quotation templates" +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:217 +msgid "" +"When creating a quotation (:menuselection:`Sales app --> New`), choose a " +"pre-configured template in the :guilabel:`Quotation Template` field." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Quotation templates field on a standard quotation form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:224 +msgid "" +"To view what the customer will see, click the :guilabel:`Preview` button at " +"the top of the page to see how the quotation template appears on the front-" +"end of the website through Odoo's customer portal." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst-1 +msgid "Customer preview of a quotation template in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:233 +msgid "" +"Quotation template design uses the same methodology and functionality with " +"design building blocks as a typical web page design with Odoo *Website*. Be " +"sure to check out the :doc:`../../../websites/website` documentation to " +"learn more." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:237 +msgid "" +"When all blocks and customizations are complete, click the :guilabel:`Save` " +"button to put those configurations into place." +msgstr "" + +#: ../../content/applications/sales/sales/send_quotations/quote_template.rst:240 +msgid "" +"There is also a blue banner at the top of the quotation template design with" +" a link to quickly return :guilabel:`Back to edit mode`. When clicked, Odoo " +"returns to the quotation form in the back-end of the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:5 +msgid "Subscriptions" +msgstr "การสมัครสมาชิก" + +#: ../../content/applications/sales/subscriptions.rst:7 +msgid "" +"Odoo *Subscriptions* is used to run recurring businesses: :ref:`sell new " +"contracts <subscriptions/quotations>`, :doc:`upsell customers " +"</applications/sales/subscriptions/upselling>`, keep the churn under " +"control, and :doc:`generate reports " +"</applications/sales/subscriptions/reports>` on the main :abbr:`KPIs (Key " +"Performance Indicators)`: :abbr:`MRR (Monthly Recurring Revenue)`, " +":abbr:`ARR (Annual Recurring Revenue)`, retention, churn, etc." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:15 +msgid "" +"`Odoo Tutorials: Subscriptions " +"<https://www.odoo.com/slides/subscription-20>`_" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:16 +msgid ":doc:`/applications/sales/subscriptions/products`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:17 +msgid ":doc:`/applications/sales/subscriptions/ecommerce`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:18 +msgid ":doc:`/applications/sales/subscriptions/plans`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:19 +msgid ":doc:`/applications/sales/subscriptions/upselling`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:20 +msgid ":doc:`/applications/sales/subscriptions/renewals`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:21 +msgid ":doc:`/applications/sales/subscriptions/closing`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:22 +msgid ":doc:`/applications/sales/subscriptions/automatic_alerts`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:23 +msgid ":doc:`/applications/sales/subscriptions/reports`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:28 +msgid "Subscription quotations" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:31 +msgid "Sales orders with a defined recurrence become subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:33 +msgid "" +"To create a new subscription, click on :guilabel:`New` from the " +"*Subscription* or the :doc:`Sales </applications/sales>` app. You can " +"either:" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:36 +msgid "" +"Select a :doc:`subscription plan </applications/sales/subscriptions/plans>` " +"to prefill the quotation instantly, or" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:38 +msgid "" +"Fill out the quotation normally, making sure to select a recurrence and an " +"end date if necessary and adding :doc:`recurrent products " +"</applications/sales/subscriptions/products>`." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:42 +msgid "" +"You can define different invoice and delivery addresses by enabling the " +":doc:`Customer Addresses " +"</applications/finance/accounting/customer_invoices/customer_addresses>` " +"feature." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:48 +msgid "Confirmation" +msgstr "การยืนยัน" + +#: ../../content/applications/sales/subscriptions.rst:50 +msgid "" +"Send the quotation to the customer for confirmation by clicking on " +":guilabel:`Send by email`, or confirm it immediately by clicking on " +":guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:54 +msgid "" +"Click on :guilabel:`Customer Preview` to preview the customer portal where " +"the customer can view their quotation, sign and pay it, and communicate with" +" you." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:60 +msgid "Automatic payments" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:62 +msgid "" +"You can require the customer to set an automatic payment method and pre-pay " +"the subscription's first occurrence before they can confirm their quotation." +" To do so, go to the :guilabel:`Other Info` tab of the quotation and check " +"the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:67 +msgid "" +"If you leave :guilabel:`Payment` unchecked, the customer doesn't have to " +"pre-pay to start the subscription. This means that the payment is not " +"automatic and that the customer must pay each invoice manually." +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:72 +msgid "" +"If the online confirmation requires a pre-payment, your customer can select " +"only the :ref:`payment providers <payment_providers/supported_providers>` " +"that have the :ref:`tokenization feature " +"<payment_providers/features/tokenization>`. This ensures that the customer " +"is automatically charged at each new period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:3 +msgid "Automatic alerts" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:5 +msgid "" +"Now that your subscriptions are up and running, you want to stay up-to-date " +"with your customers. Some automation would be appreciated since you would " +"not want to go through the list of all your subscribers to check how things " +"are going. This is what the *Automatic Alerts* feature is for." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:9 +msgid "" +"For example, when customers subscribe to your magazine, you would probably " +"want to send them an email to welcome them and express your gratitude. Or, " +"if the satisfaction rate of your customers drops below 50%, you would " +"probably want to schedule a call with them to understand the reasons for " +"their dissatisfaction." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:14 +msgid "" +"With **Odoo Subscriptions**, you can set automatic emails, create a \"Call\"" +" task for one of your salespeople so that he/she can try to understand your " +"customer's dissatisfaction, and finally, why not automatically send " +"satisfaction surveys so customers can evaluate your services? All of that is" +" now possible." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:20 +msgid "Create a new automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:22 +msgid "" +"The following example shows how to create a new automatic alert to send " +"satisfaction surveys to your customers, by email, after one month of " +"subscription. To do so, go to :menuselection:`Subscriptions --> " +"Configuration --> Alerts`, and create a new alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "New automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:30 +msgid "" +"On the *Apply on* section, first give the alert a name. Then, you can choose" +" to apply this alert on a subscription template, on a specific customer, or " +"even on a specific product. If you want to add more specifications, you can " +"also specify the value of your MRR, the change rate of your MRR over a " +"certain period of time, the value of the satisfaction rate, and even the " +"stage to which you want to apply this alert." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:37 +msgid "" +"In this example, the alert is applied to a specific product, and the stage " +"goes from *Undefined* to *In Progress*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:40 +msgid "" +"For the *Action* section, specify the *Action* and the *Trigger on*. If the " +"*Trigger on* is set to *Modification*, the action is triggered every time " +"there is a change or anything added to the subscription, and all the " +"conditions on the *Apply on* section are met. Now, if the *Trigger on* is " +"set to *Timed condition*, it means that the action is triggered based on the" +" type of *Trigger date*. After that, you can choose your *Action*. You have " +"the choice between *Create next activity*, *Set a tag on the subscription*, " +"*Set a stage on the subscription*, *Mark as To Renew*, *Send an email to the" +" customer* and *Send an SMS Text Message to the customer*." +msgstr "" +"สำหรับส่วน *การกระทำ* ให้ระบุ *การกระทำ* และ *เปิดการเริ่มต้น* หาก " +"*เปิดการเริ่มต้น* ถูกตั้งค่าเป็น *การแก้ไข* " +"การดำเนินการจะถูกทริกเกอร์ทุกครั้งที่มีการเปลี่ยนแปลงหรือมีอะไรเพิ่มเติมในการสมัครสมาชิก" +" และตรงตามเงื่อนไขทั้งหมดในส่วน *ใช้บน* ตอนนี้ หาก *เปิดการเริ่มต้น* " +"ถูกตั้งค่าเป็น *เงื่อนไขเวลา* " +"หมายความว่าการดำเนินการจะถูกทริกเกอร์ตามประเภทของ *วันที่ทริกเกอร์* " +"หลังจากนั้น คุณสามารถเลือก *การกระทำ* ของคุณได้ คุณมีทางเลือกระหว่าง " +"*สร้างกิจกรรมถัดไป*, *ตั้งค่าแท็กในการสมัครสมาชิก*, " +"*ตั้งค่าขั้นตอนการสมัครสมาชิก*, *ทำเครื่องหมายว่าต้องการต่ออายุ*, " +"*ส่งอีเมลถึงลูกค้า* และ *ส่งข้อความ SMS ข้อความถึงลูกค้า*" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:50 +msgid "" +"In the example above, the *Trigger on* is set to *Timed condition*, " +"therefore, a *Trigger date* and *Delay after trigger* need to be specified. " +"And because the *Send an email to the customer* action was adopted, an " +"*Email template* can be chosen." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:54 +msgid "" +"As a result, this alert will send a rating survey after one month, to the " +"customers who have purchased that specific product. The survey will appear " +"in the chatter of your respective subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "Satisfaction survey in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:63 +msgid "Modify an existing automatic alert" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:65 +msgid "" +"By default, Odoo suggests you an automatic alert called *Take action on less" +" satisfied clients*." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst-1 +msgid "Modify an existing automatic alert in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:71 +msgid "" +"This alert is applied to the *Rating Satisfaction* of your customers, and " +"the action is triggered on *Timed condition*. If their satisfaction rate is " +"lower than 50%, a salesperson contacts the customer. This action is " +"automatically assigned to the salesperson who manages the subscription, and " +"the due date is 5 days after the triggering of this action. This alert " +"ensures that your clients are happy and that you are taking actions if they " +"are not. It helps to keep your customer retention rates very high." +msgstr "" +"การแจ้งเตือนนี้ใช้กับ *ความพึงพอใจในการให้คะแนน* ของลูกค้าของคุณ " +"และการดำเนินการจะถูกเริ่มต้นขึ้นใน *เงื่อนไขตามกำหนดเวลา* " +"หากอัตราความพึงพอใจต่ำกว่า 50% พนักงานขายจะติดต่อกับลูกค้า " +"การดำเนินการนี้ถูกกำหนดให้กับพนักงานขายที่จัดการการสมัครใช้งานโดยอัตโนมัติ " +"และวันครบกำหนดคือ 5 วันหลังจากการเริ่มการกระทำนี้ " +"การแจ้งเตือนนี้ช่วยให้แน่ใจว่าลูกค้าของคุณพึงพอใจ " +"และคุณกำลังดำเนินการทันทีถ้าหากพวกเขาไม่พึงพอใจ " +"มันช่วยให้อัตราการรักษาลูกค้าของคุณสูง" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:79 +msgid "" +"By editing the alert, you can modify the *Apply on*, the *Action* and " +"*Activity* sections, and adapt them to your own needs." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:83 +#: ../../content/applications/sales/subscriptions/closing.rst:105 +#: ../../content/applications/sales/subscriptions/renewals.rst:85 +#: ../../content/applications/sales/subscriptions/reports.rst:120 +#: ../../content/applications/sales/subscriptions/upselling.rst:103 +msgid ":doc:`../subscriptions`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:84 +#: ../../content/applications/sales/subscriptions/closing.rst:106 +#: ../../content/applications/sales/subscriptions/renewals.rst:86 +#: ../../content/applications/sales/subscriptions/reports.rst:121 +#: ../../content/applications/sales/subscriptions/upselling.rst:104 +msgid ":doc:`plans`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:85 +#: ../../content/applications/sales/subscriptions/closing.rst:107 +#: ../../content/applications/sales/subscriptions/renewals.rst:87 +#: ../../content/applications/sales/subscriptions/reports.rst:122 +#: ../../content/applications/sales/subscriptions/upselling.rst:105 +msgid ":doc:`products`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:3 +msgid "Close a subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:5 +msgid "" +"Losing a customer is always difficult, especially if you put a lot of effort" +" into getting them to sign up for your products/services. However, many " +"companies come up with dubious methods to reduce the probability of this " +"happening." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:14 +msgid "" +"If you adopt such methods, you are among companies that actively and " +"indirectly spread the phobia of subscriptions, who do not think about how " +"negatively dissatisfied customers could impact their business and, who " +"frustrate the customers in a way or another. However, at some point, it is " +"understandable that you do not want your customers to be involved in your " +"subscription status." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:19 +msgid "" +"If you do not adopt such methods, you are among companies that continue to " +"evolve in a long-term subscription business model, especially in an era of " +"ultra-fast communications between dissatisfied customers, and who retain " +"their customers by making it easier for them to leave if they want to. By " +"giving them the opportunity to close their own subscriptions, your customers" +" do not feel trapped because they subscribed to your products/services." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:25 +msgid "" +"In summary, the **Odoo Subscriptions** application gives you the " +"**possibility to choose what you want to apply**. Indeed, you can decide " +"whether to give your customers the option to close their subscriptions " +"whenever they want to or to restrict this possibility. It depends on you and" +" we will show you how to do that in our amazing application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:33 +msgid "" +"Go to :menuselection:`Subscriptions --> Configuration --> Subscription " +"templates`. From there, you can create a new *Subscription template* or " +"modify an existing one. When editing your template, underneath the Invoicing" +" tab, you have the possibility to activate the option *Closable by " +"customer*. Once enabled, this option gives your customers the right to close" +" their own subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "Configuration to close your subscription with Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:43 +msgid "" +"Be sure to check out our documentation on how to :doc:`Use subscription " +"templates <plans>` to fully understand the importance of this feature in a " +"basic flow using the **Odoo Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:49 +msgid "Close your first subscription" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:52 +msgid "Administrator view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:54 +msgid "" +"Once confirmed, a quotation becomes a sales order and a new subscription is " +"automatically created. Therefore, this subscription has the status *In " +"progress*. From there, you have the possibility to close the subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"Close your subscription from an administration point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:62 +msgid "" +"By using the smart button *Close*, you have to enter a close reason. For " +"example, \"Subscription too expensive\", \"Subscription does not meet my " +"requirements\", \"Subscription reached its end date\", etc. Immediately " +"after confirming your close reason, you can observe that the status of the " +"subscription is now *Closed* and that the close reason is mentioned on the " +"subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "What happens when you close your subscription with Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:72 +msgid "Customer view" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:74 +msgid "" +"As previously explained in the *Administrator view* part, from the " +"subscription form, you also have the possibility to visualize what your " +"customers see when managing their subscriptions thanks to the *Customer " +"preview* button. In this example, the customer has the choice to close " +"his/her subscription whenever he/she wants to, due to the *Close " +"Subscription* button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"Close your subscription from a customer point of view with Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:83 +msgid "" +"By using this button, the customer can specify the reason for cancelling " +"his/her subscription and he/she can even leave a message." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"What happens when customers close their subscription with Odoo " +"Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:90 +msgid "" +"By confirming the cancellation, the customer is redirected to his/her " +"portal. The administrator is informed of this modification. Indeed, the " +"status of the subscription becomes *Closed* and a note appears in the " +"chatter with the new stage, the end date, the close reason, and the closing " +"text added by the customer." +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst-1 +msgid "" +"What happens when customers close their subscription in Odoo Subscriptions?" +msgstr "" + +#: ../../content/applications/sales/subscriptions/closing.rst:100 +msgid "" +"Before closing a subscription, check out our documentation on how to " +":doc:`Create a quotation using subscription products <../subscriptions>` to " +"understand how subscriptions are managed in the **Odoo Subscriptions** " +"application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:3 +msgid "Use subscriptions in the eCommerce shop" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:5 +msgid "" +"Subscription products can be sold in the Odoo *eCommerce* shop just like " +"regular sales products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:7 +msgid "" +"However, by default, the eCommerce product page only displays the shortest " +"recurrence period listed in the :guilabel:`Time-based pricing` tab of the " +"product form. For example, if a subscription product has *monthly* and " +"*yearly* recurrence periods configured, then only the monthly price appears " +"on the eCommerce page for that product by default." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:12 +msgid "" +"To add more recurrence periods to the eCommerce product page, create a " +"*product variant* for each recurrence period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:16 +msgid "" +":doc:`Configure subscription products " +"</applications/sales/subscriptions/products>`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:17 +msgid "" +":doc:`Product variants " +"</applications/sales/sales/products_prices/products/variants>`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:20 +msgid "Create recurrence periods as product variants" +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:22 +msgid "" +"To set up each recurrence period as a product variant, go to " +":menuselection:`Subscriptions --> Subscriptions --> Products` and select a " +"product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add " +"a line`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:26 +msgid "" +"Create an :guilabel:`Attribute` called `Billing Period` (or something " +"similar) by typing in the name and clicking :guilabel:`Create`. This " +"attribute name appears as the option heading on the product page of the " +"eCommerce shop." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:30 +msgid "" +"Next, create :guilabel:`Values` that correspond to the recurrence periods " +"that are configured in the :guilabel:`Time-based pricing` tab of the product" +" form. Type in the name of the recurrence period, then click " +":guilabel:`Create`. These value names appear as selectable options on the " +"product page of the eCommerce shop." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "" +"Recurrence periods configured as product variants in the \"Attributes & Variants\" tab of\n" +"the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:40 +msgid "" +"Click on the :guilabel:`☁️ (cloud)` icon at the top of the page to save " +"manually. After saving, a :guilabel:`Product Variants` column appears on the" +" :guilabel:`Time-based pricing` tab. Assign the product variants to their " +"corresponding recurrence periods and prices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "Product variants on the \"Time-based pricing\" tab of the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:48 +msgid "" +"The product variants are now available for selection on the eCommerce " +"product page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst-1 +msgid "" +"Recurrence periods configured as product variants on the eCommerce product " +"page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:3 +msgid "Subscription plans" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:5 +msgid "" +"*Subscription plans* are :doc:`quotation templates " +"</applications/sales/sales/send_quotations/quote_template>` used to " +"preconfigure quotations with subscription products. Use subscription plans " +"to quickly create subscription orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:10 +msgid "Configure subscription plans" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:12 +msgid "" +"To configure subscription plans, go to :menuselection:`Subscriptions --> " +"Configuration --> Plans`. Then, click :guilabel:`New` to create a new plan, " +"or select an existing plan to edit it." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:15 +msgid "" +"Since the Odoo *Subscriptions* app is integrated closely with the *Sales* " +"app, subscription plans use the same form as quotation templates." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan (quotation template) configuration form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:22 +msgid "The subscription plan form contains the following options:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:24 +msgid "" +":guilabel:`Name`: Enter a name for the subscription plan at the top of the " +"page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:25 +msgid "" +":guilabel:`Quotation expires after`: Enter the number of days after which " +"the quotation expires, starting from the day the quotation is sent to the " +"customer. Leave this field at zero for the quotation to never expire." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:28 +msgid "" +":guilabel:`Online Confirmation`: Check the boxes next to " +":guilabel:`Signature` or :guilabel:`Payment` to enable the customer to " +"confirm their subscription order by signing or paying for the quotation. " +"Enable both to leave the choice to the customer. Enable neither to only " +"confirm the quotation in the backend." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:32 +msgid "" +":guilabel:`Confirmation Mail`: Select an :doc:`email template " +"</applications/general/email_communication/email_template>` for the " +"confirmation email that is automatically sent to the customer after the " +"quotation is confirmed. Leave this field blank to send nothing." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:37 +msgid "" +"To create a new email template, enter a name for the template, then click " +":guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:39 +msgid "" +"To edit an existing email template, select one from the drop-down menu, then" +" click on the :guilabel:`Internal link` arrow at the end of the line." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:42 +msgid "" +":guilabel:`Recurrence`: Select the recurrence period used for the plan. The " +"recurrence periods available here are the same ones that are configured in " +":menuselection:`Subscriptions --> Configuration --> Recurrence Periods`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:46 +msgid "" +"Selecting a :guilabel:`Recurrence` turns the quotation template into a " +"subscription plan and enables the following additional options:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:49 +msgid "" +":guilabel:`Duration`: Choose whether the subscription plan has no end date " +"(:guilabel:`Forever`) or a :guilabel:`Fixed` duration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:52 +msgid "" +"If the duration is :guilabel:`Forever`, then the subscription plan will " +"continually renew until either the customer or the company manually ends the" +" subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:54 +msgid "" +"If the duration is :guilabel:`Fixed`, then enter an :guilabel:`End After` " +"date, which determines the amount of time after which the subscription will " +"automatically end." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:57 +msgid "" +":guilabel:`Self Closable`: Check this box to enable the customer to " +"terminate their subscription from the :doc:`customer portal " +"</applications/websites/ecommerce/ecommerce_management/customer_accounts>`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:60 +msgid "" +":guilabel:`Automatic Closing`: Enter the number of days after which *unpaid*" +" subscriptions *past* the due date are automatically closed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:62 +msgid "" +":guilabel:`Invoicing Journal`: Select the accounting journal in which " +"invoices for this subscription plan are recorded. Leave this field blank to " +"use the sales journal with the lowest sequence." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan with Recurrence selected." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:70 +msgid "" +"In the :guilabel:`Lines` tab, create the order lines for the quotation. " +"Click :guilabel:`Add a product`, select a product to include in the plan, " +"and then enter the :guilabel:`Quantity` and :guilabel:`Unit of Measure`. Add" +" as many products as desired to the order lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:74 +msgid "" +"In the :guilabel:`Optional Products` tab, enter any optional products that " +"the customer can add to their quotation before confirming the order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:77 +msgid "" +"If the subscription plan has unique :doc:`terms and conditions " +"</applications/finance/accounting/customer_invoices/terms_conditions>`, add " +"them in the :guilabel:`Terms & Conditions` tab. If terms conditions are " +"specified on a plan, these will be used instead of the default terms and " +"conditions set up in the *Sales* app settings." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst-1 +msgid "Subscription plan Terms & Conditions tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:87 +msgid "Use subscription plans on quotations" +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:89 +msgid "" +"Quotations for subscription products can be created in both the " +"*Subscriptions* app and the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:92 +msgid "" +"From the :guilabel:`Subscriptions` dashboard, click :guilabel:`New` to " +"create a new quotation. Then, select a subscription plan in the " +":guilabel:`Subscription Plan` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:95 +msgid "" +"The :guilabel:`Recurrence`, products, and other information from the plan " +"are automatically filled in. The quotation can then be modified further as " +"needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:98 +msgid "" +"From the :guilabel:`Sales` dashboard, click :guilabel:`New` to create a new " +"quotation. Then, select a subscription plan in the :guilabel:`Quotation " +"Template` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions/plans.rst:101 +msgid "" +"All subscription orders will appear on the :guilabel:`Subscriptions` " +"dashboard regardless of whether they were created in the *Subscriptions* app" +" or the *Sales* app." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:3 +msgid "Subscription products" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:5 +msgid "" +"By closely integrating with the Odoo *Sales* app, the *Subscriptions* app " +"enables users to sell subscription products alongside regular sales " +"products. While regular products are sold on a one-time basis, subscription " +"products are sold on a renewing basis, generating recurring revenue." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:9 +msgid "In Odoo, subscription products are also called *recurring* products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:12 +msgid "Configure recurrence periods" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:14 +msgid "" +"To get started with subscriptions, the *recurrence periods* must be properly" +" configured, as needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:16 +msgid "" +"Recurrence periods are the time periods in which subscriptions renew. They " +"designate how often the customer pays for (and receives) subscription " +"products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:19 +msgid "" +"To configure recurrence periods, go to :menuselection:`Subscriptions app -->" +" Configuration --> Recurrence periods`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "The recurrence periods page in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:26 +msgid "" +"The *Subscriptions* app comes with some basic recurrence periods already " +"configured:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:28 +msgid ":guilabel:`Monthly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:29 +msgid ":guilabel:`Quarterly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:30 +msgid ":guilabel:`Weekly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:31 +msgid ":guilabel:`2 Weeks`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:32 +msgid ":guilabel:`Yearly`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:33 +msgid ":guilabel:`3 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:34 +msgid ":guilabel:`5 Years`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:36 +msgid "New recurrence periods can be added and/or edited at any time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:38 +msgid "" +"To create a new recurrence period, click :guilabel:`New` on the " +":guilabel:`Recurrence Periods` page. Doing so reveals a blank recurrence " +"period form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "A recurrence period form in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:45 +msgid "" +"Then, type in the :guilabel:`Name` and :guilabel:`Duration` of the " +"recurrence period, and select the :guilabel:`Unit` that defines the " +"duration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:49 +msgid "" +"The unit :guilabel:`Days` *cannot* be used as a recurrence period on " +"subscriptions. The daily recurrence is meant for rentals, and **cannot** be " +"added on recurring subscription sales orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:52 +msgid "" +"This limitation is there to avoid sales orders that would generate daily " +"invoices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:55 +msgid "Product form configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:57 +msgid "" +"To create a new subscription product, navigate to " +":menuselection:`Subscriptions app --> Products --> Products`, and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:60 +msgid "" +"Doing so reveals a blank product form, which can be configured and " +"customized in a number of ways." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:63 +msgid "" +"By default, the :guilabel:`Recurring` option is already enabled, prompting " +"Odoo to recognize it as a subscription product. Be sure to leave the " +":guilabel:`Recurring` and :guilabel:`Can be Sold` options enabled." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:67 +msgid "" +"The :guilabel:`Product Type` field is set to :guilabel:`Service` by default," +" as well. However, subscription products *can* be set to other types, if " +"needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "A basic subscription product form in Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:75 +msgid "Time-based pricing" +msgstr "การกำหนดราคาตามเวลา" + +#: ../../content/applications/sales/subscriptions/products.rst:77 +msgid "" +"Once the desired fields in the :guilabel:`General Information` tab have been" +" entered, click the :guilabel:`Time-based pricing` tab on the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "" +"The time-based pricing tab on a subscription product form in Odoo " +"Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:84 +msgid "" +"From here, click :guilabel:`Add a price` to begin defining recurring prices." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:86 +msgid "" +"In the :guilabel:`Period` column, select a desired recurrence period. In the" +" :guilabel:`Pricelist` column, select a pricelist, if needed. Then, in the " +":guilabel:`Price` column, enter the price for that recurrence period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:91 +msgid "" +":guilabel:`Daily` and :guilabel:`Hourly` periods **cannot** be used on " +"recurring products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:0 +msgid "The validation error pop-up window that appears in Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:98 +msgid "" +"There is *no limit* to how many lines can be added to the :guilabel:`Time-" +"based pricing` table." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:101 +msgid "" +"An existing product can be made into a subscription product, simply by " +"marking it as :guilabel:`Recurring`, and configuring :guilabel:`Time-based " +"pricing` on the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:104 +msgid "" +"A subscription product can still be sold as a regular product, by adding it " +"to a quotation and *not* selecting a :guilabel:`Recurrence` on the " +"quotation." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:110 +msgid "" +":doc:`Pricelists <../sales/products_prices/prices/pricing>` can be used with" +" subscription products to give special pricing to customers included in " +"pricelists." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:113 +msgid "" +"This can be configured either in the :guilabel:`Time-based pricing` tab of " +"the product form, or on the pricelist form in the *Sales* application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:116 +msgid "" +"To create recurring price rules for specific pricelists in the " +":guilabel:`Time-based pricing` tab of the product form, select a pricelist " +"in the :guilabel:`Pricelist` column." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "Pricelists in the \"Time-based pricing\" tab of the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:123 +msgid "" +"When pricelists are added to the :guilabel:`Time-based pricing` tab, the " +"pricelist form in the *Sales* app is automatically updated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:126 +msgid "" +"Time-based pricing rules can also be configured directly on the pricelist " +"form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:128 +msgid "" +"To do this, go to :menuselection:`Sales app --> Products --> Pricelists`, " +"and select a pricelist (or click :guilabel:`New` to create a new pricelist)." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:132 +msgid "" +"Pricelists are also accessible through the Odoo *Subscriptions* app by " +"following the same menu steps." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:135 +msgid "" +"Then, on the pricelist form, under the :guilabel:`Time-based rules` tab, " +"click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst-1 +msgid "The time-based rules tab on a pricelist form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:142 +msgid "" +"Then, select a subscription product in the :guilabel:`Products` column, and " +"select a recurrence period in the :guilabel:`Period` column. Lastly, enter a" +" :guilabel:`Price` for that particular product and period. Add as many lines" +" as needed." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:146 +msgid "" +"When :guilabel:`Time-based rules` are added to the pricelist form, the " +":guilabel:`Time-based pricing` tab of the product form is automatically " +"updated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/products.rst:150 +msgid ":doc:`ecommerce`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:3 +msgid "Renew subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:5 +msgid "" +"The foundation of any subscription business model is recurring payments. " +"That's when customers reliably pay a regular amount at specific intervals, " +"in exchange for access to a subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:9 +msgid "" +"The renewal of a subscription is the process followed by customers when they" +" willingly choose to continue their participation (and payment) for a " +"subscription product or service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:12 +msgid "" +"Subscribers experience the renewal process at different intervals -- weekly," +" monthly, annually, etc. -- depending on the duration of the agreed-upon " +"contract." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:15 +msgid "" +"Most companies that offer subscriptions prefer to automate the renewals " +"process for customers, but, in some cases, manual subscription renewals are " +"still used." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:18 +msgid "" +"With the Odoo *Subscriptions* application, a company can manage all of their" +" subscriptions in one place. Renewals can be processed automatically or " +"manually, include additional products or upsells per renewal order, and be " +"filtered in batch views to quickly locate customers who need to renew their " +"subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:24 +msgid "Subscription renewals" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:26 +msgid "" +"In order to renew a subscription, a quotation with a subscription product " +"**must** be confirmed, with a configured :guilabel:`Recurring Plan` " +"selected, which turns it into a sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:30 +msgid "Only a singular product is required." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:31 +msgid "" +"A subscription service is still a product (albeit a digital, recurring one)" +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:33 +msgid "" +"Then, that sales order needs to be confirmed, and payment from the customer " +"for the initial subscription has to be invoiced and registered." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:36 +msgid "" +"When those steps are complete, an :guilabel:`In Progress` tag is applied to " +"the sales order form, and a series of buttons appear at the top of the sales" +" order -- including a button titled, :guilabel:`Renew`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Renew button on subscription sales order with Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:44 +msgid "" +"When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new " +"renewal quotation, complete with a :guilabel:`Renewal Quotation` tag." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Renewal quotation in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:51 +msgid "" +"From here, a standard sales flow can occur in order to confirm the " +"quotation. This typically begins by clicking :guilabel:`Send by Email`. This" +" sends a copy of the quotation to the customer, by email, for them to " +"confirm, and eventually, pay for." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:56 +msgid "" +"In the *Chatter* of the :guilabel:`Renewal Quotation`, it is mentioned that " +"this subscription is the renewal of the subscription from the original sales" +" order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:59 +msgid "" +"Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales " +"order, and a :guilabel:`Sales History` smart button appears at the top of " +"the page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "Sales History smart button in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:66 +msgid "" +"When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a " +"separate page, showcasing the different sales orders attached to this " +"subscription, along with their individual :guilabel:`Subscription Status`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:74 +msgid "" +"Additionally, once the :guilabel:`Renewal Quotation` is confirmed, an " +":guilabel:`MRR` smart button also appears at the top of the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst-1 +msgid "MRR smart button in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/renewals.rst:81 +msgid "" +"When clicked, Odoo reveals an :guilabel:`MRR Analysis` page, detailing the " +"monthly recurring revenue related to this specific subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:3 +msgid "Reports" +msgstr "รายงาน" + +#: ../../content/applications/sales/subscriptions/reports.rst:5 +msgid "" +"As we know, understanding how our business is going, and where it is going, " +"is key to success. And particularly so when we offer subscription services " +"or products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:8 +msgid "" +"Before getting to the heart of the matter, it is very important to recall " +"certain essential concepts to the proper understanding of the following " +"reports:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:11 +msgid "" +"**Monthly Recurring Revenue (MRR)**: MRR is arguably the most important " +"metric for subscription businesses. It shows the monthly revenue earned with" +" subscription-based products or services. It is a consistent number used to " +"track all recurring revenue over time, in monthly increments." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:15 +msgid "" +"**Annual Run-Rate (ARR)**: ARR is the yearly version of MRR, which is based " +"on the current MRR, to estimate the coming year's performance. However, this" +" estimation does not take variations and growth into account." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Difference between MRR and ARR in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:23 +msgid "" +"**Non-Recurring Revenue (NRR)**: NRR shows the revenue earned for everything" +" else than subscription-based products or services. This includes gains of a" +" rare or unique nature that are unlikely to occur in the ordinary course of " +"businesses." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:27 +msgid "" +"**Customer Retention**: Practices to engage existing customers to continue " +"buying products or services from your business. Customer retention can be a " +"challenge, because you must prove you are worthy of your customers' trust." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:31 +msgid "" +"**Churn Rate**: Also known as the Rate of Attrition or Customer Churn, the " +"churn rate can be defined, in this case, as the percentage of subscribers " +"who discontinued their subscriptions within a given time period. We can " +"distinguish two types of Churn:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:35 +msgid "**Logo Churn**: It corresponds to the subscription cancellation rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:37 +msgid "" +"**Revenue Churn**: It corresponds to the monthly recurring revenue loss " +"rate." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:40 +msgid "Let's imagine a 2$ increase in a subscription service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:42 +msgid "" +"We lost 3 customers out of the initial 20, which generates a **Logo Churn** " +"of 15%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "" +"Therefore, the 56$ of MRR difference out of the initial 600$ causes a " +"**Revenue Churn**" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "of 9,33%." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:0 +msgid "Difference between logo churn and revenue churn in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:50 +msgid "" +"Reminder: even though they seem to evolve in the same direction most of the " +"time, it might not be the case all the time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:53 +msgid "" +"**Customer Lifetime Value (CLV)**: Indicates how much revenue can be " +"expected for a customer during his/her entire contract. This approach " +"emphasizes the importance of customer retention, shifting our focus from a " +"quarterly or yearly approach to a long-term one." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:57 +msgid "" +"Check out the different kinds of reports you can access from the **Odoo " +"Subscriptions** application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:61 +msgid "Subscriptions analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:63 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Subscriptions`. From " +"there, you can change the *Measures*. By default, Odoo uses the *Monthly " +"Recurring Revenue*. In addition to that, you can choose *Quantity*, " +"*Recurring Price*, *Yearly Recurring Revenue* and *Count*. For this example," +" *Quantity* is added. This way, you can review both of these measures at the" +" same time. You can even *Group By Start Date* and, more precisely, by " +"*Week*, to get a clear view of your report." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Subscriptions analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:74 +msgid "Retention analysis report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:76 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Retention`. The " +"default measure applied is *Count*, but you can change to the appropriate " +"one for you. For the example below, *Monthly Recurring Revenue* was chosen, " +"and the *Month* periodicity remains intact. By using these criteria, you can" +" see the progression of the retention from its start." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Retention analysis report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:86 +msgid "Revenue KPIs report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:88 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Revenue KPIs`. From " +"there, you can check different KPIs: *Monthly Recurring Revenue*, *Net " +"Revenue*, *Non-Recurring Revenue*, *Revenue per Subscription*, *Annual Run-" +"Rate*, *Lifetime Value*, and more. You can also filter this information on " +"subscriptions, companies, and sales teams. This is useful if you are looking" +" for specific information." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Revenue KPIs report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:98 +msgid "" +"The example below shows the *Monthly Recurring Revenue* detailed report. At " +"the moment, there is no data, which is the typical scenario for a new " +"business. But, as your company grows over the months, these graphs get " +"populated with more and more data. Once again, you can filter these specific" +" KPIs on subscriptions, companies, and sales teams." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Detailed MRR report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:108 +msgid "Salesperson dashboard report" +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst:110 +msgid "" +"Go to :menuselection:`Subscriptions --> Reporting --> Salesperson " +"Dashboard`. This page gives you a summary of your *Monthly Recurring " +"Revenue*, *Non-Recurring Revenue*, *Subscription modifications*, and *Non-" +"Recurring Invoices* for each of your salespeople. You can choose the period " +"you want to apply and the salesperson you want to analyze." +msgstr "" + +#: ../../content/applications/sales/subscriptions/reports.rst-1 +msgid "Salesperson dashboard report in Odoo Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:3 +#: ../../content/applications/sales/subscriptions/upselling.rst:44 +msgid "Upsell subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:5 +msgid "" +"Subscriptions are recurrent, and go on indefinitely. As time passes, " +"customers may want to modify them. With that in mind, it's imperative to " +"have the ability to adapt prices, or change quantities, to accommodate any " +"need. That's where the opportunity to upsell a subscription can come into " +"play." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:9 +msgid "Upselling may prove beneficial to the following customer types:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*Loyal Customers*" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "" +"These are customers who already trust the company/brand, and because they " +"have established a pattern of paying for products/services, there's more " +"confidence behind the attempt to sell them a more expensive product/service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "*New Customers*" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:0 +msgid "" +"For brand new customers unfamiliar with the company/brand, a new, attractive" +" tactic must be employed to entice them to purchase a more expensive " +"product/service." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:19 +msgid "" +"In these instances, discounts can be useful. Typically, subscriptions end " +"after a certain period of time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:22 +msgid "" +"So, if these more expensive products/services are offered to new customers " +"at a discount, it can result in a sale, while establishing a strong sense of" +" trust between the customer and the company/brand. In turn, this can " +"increase customer retention, as they'll grow more comfortable and " +"trustworthy over time." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:28 +msgid "Discount configuration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:30 +msgid "" +"In order to have the ability to upsell a subscription to a new customer, " +"with the aid of a discount, the *Discounts* feature **must** be activated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:33 +msgid "" +"To activate the *Discounts* feature, navigate to :menuselection:`Sales app " +"--> Configuration --> Settings`, scroll to the :guilabel:`Pricing` section, " +"and tick the checkbox beside :guilabel:`Discounts`. Then, click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "Activation of the discount option in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:41 +msgid "" +"With that feature activated, the ability to grant discounts on sales order " +"lines." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:46 +msgid "" +"Before upselling a subscription, check out our documentation on how to " +":doc:`Create a quotation <../subscriptions>` using subscription products." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:49 +msgid "" +"When a quotation with a subscription is confirmed, it officially becomes a " +"sales order, and a new subscription is created in the Odoo *Subscriptions* " +"application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:53 +msgid "" +"The subscription sales order **must** be invoiced *before* an upsell can " +"occur." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:55 +msgid "" +"When the subscription sales order is opened, either in the *Sales* or " +"*Subscriptions* application, the ability to upsell that subscription is " +"available, via the :guilabel:`Upsell` button at the top of the sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "Upsell button for subscription sales orders with Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:63 +msgid "" +"When the :guilabel:`Upsell` button is clicked, a new quotation form appears," +" with an :guilabel:`Upsell` status banner in the upper-right corner. The " +"initial subscription product is already in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:67 +msgid "" +"There is also a warning reminding the user that the recurring products are " +"discounted, according to the prorated period of time, located beneath the " +"initial subscription product in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:71 +msgid "" +"From this new upsell quotation form, add new subscription products in the " +":guilabel:`Order Lines` tab, by clicking :guilabel:`Add a product`, and " +"selecting the desired subscription product." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "" +"Adding products to your subscription via the upsell option in Odoo " +"Subscriptions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:78 +msgid "" +"Once the desired upsell subscription product(s) have been added, it can be " +"sent to the customer for approval by clicking the :guilabel:`Send by Email` " +"button." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:82 +msgid "" +"When the quotation is confirmed by the customer, the upsell products are " +"added to the initial subscription. Quotation prices are then prorated to the" +" remaining time of the current invoicing period." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:87 +msgid "" +"Before sending the new quotation to the customer, the unit price, taxes, and" +" even discount can be applied." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:90 +msgid "" +"Once the customer approves, click the :guilabel:`Confirm` button on the " +"quotation, making it a sales order. When that's clicked, a :guilabel:`Sales " +"History` smart button appears, displaying how many sales orders are attached" +" to this initial subscription order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst:94 +msgid "" +"When the :guilabel:`Sales History` smart button is clicked, Odoo reveals a " +"separate page containing a list of the related sales orders, clearly " +"showcasing their individual :guilabel:`Subscription Status`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/upselling.rst-1 +msgid "" +"The related sales order viewable from the Sales History smart button in Odoo" +" Subscriptions." +msgstr "" diff --git a/locale/th/LC_MESSAGES/services.po b/locale/th/LC_MESSAGES/services.po new file mode 100644 index 000000000..ed0181521 --- /dev/null +++ b/locale/th/LC_MESSAGES/services.po @@ -0,0 +1,4074 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/services.rst:5 +msgid "Services" +msgstr "บริการ" + +#: ../../content/applications/services/field_service.rst:8 +msgid "Field Service" +msgstr "การบริการภาคสนาม" + +#: ../../content/applications/services/field_service.rst:11 +msgid "" +"`Odoo Tutorials: Field Service <https://www.odoo.com/slides/field-" +"service-49>`_" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:3 +msgid "User default warehouse" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:5 +msgid "" +"Setting up a **default warehouse** can be useful for field technicians who " +"keep a supply in their van or those who always resupply from the same " +"warehouse. It also allows field workers to switch between warehouses from " +"their profiles." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:9 +msgid "" +"Products in sales orders created during field interventions are always " +"pulled from the default warehouse, keeping the inventory accurate." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:13 +msgid ":doc:`../../inventory_and_mrp/inventory`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:16 +#: ../../content/applications/services/project/project_management.rst:17 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:13 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/services/field_service/default_warehouse.rst:18 +msgid "" +"To set up a user default warehouse, the :doc:`storage locations " +"</applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations>`" +" feature needs to be activated in the **Inventory** app. It is also " +"necessary to have more than one warehouse in your database." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:23 +msgid "" +"You can either set it up :ref:`for your profile <default-warehouse/my-" +"profile>`, or :ref:`for all users <default-warehouse/all-users>`." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:27 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:32 +msgid "For your profile" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:34 +msgid "" +"To set up a default warehouse for yourself, click your **profile icon** in " +"the upper right corner of the screen, then, go to :menuselection:`My Profile" +" --> Preferences --> Default Warehouse`. Select the default warehouse from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:41 +msgid "For all users" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:43 +msgid "" +"To set up a default warehouse for a specific user, go to " +":menuselection:`Settings --> Users --> Manage users`, select a user, then go" +" to the :guilabel:`Preferences` tab. Scroll down to :guilabel:`Inventory`, " +"and select the default warehouse from the drop-down menu." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst-1 +msgid "Selection of a default warehouse on a user profile." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:51 +msgid "Use in field service tasks" +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:53 +msgid "" +"Once a default warehouse has been configured for a user, the materials used " +"for a sales order related to a Field Service task are pulled from that " +"specific warehouse. Open the related sales order, go to the :guilabel:`Other" +" Info` tab, then scroll down to :guilabel:`Delivery`. The default warehouse " +"is applied correctly." +msgstr "" + +#: ../../content/applications/services/field_service/default_warehouse.rst:58 +msgid "" +"Once the Field Service task is marked as done, the stock of the default " +"warehouse is automatically updated." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:3 +msgid "Onsite interventions planning" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:6 +msgid "From a sales order" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:8 +msgid "" +"Allowing your sales team to open onsite interventions creates a seamless " +"experience for your customers. They can receive a quotation they first have " +"to approve before the work even starts." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:11 +msgid "" +"Go to :menuselection:`Field Service --> Configuration --> Products` and " +"create or edit a product." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:13 +msgid "" +"Under the :guilabel:`General Information` tab, select :guilabel:`Service` as" +" :guilabel:`Product Type`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:15 +msgid "" +"Under the :guilabel:`Sales` tab, select :guilabel:`Timesheets on tasks` as " +":guilabel:`Service Invoicing Policy`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:17 +msgid "" +"Select :guilabel:`Create a task in an existing project` as " +":guilabel:`Service Tracking`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:18 +msgid "Select your :guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:19 +msgid "If you use them, select your :guilabel:`Worksheet Template`, and save." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "" +"Product configuration to create tasks from sales orders in Odoo Field " +"Service" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:25 +msgid "" +"From the :doc:`Sales <../../sales/sales>` app, create a quotation with the " +"product and confirm it. A task is automatically set up under your Field " +"Service project. It is directly accessible from the sales order." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Field Service task on a sales order in Odoo Sales" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:34 +msgid "From helpdesk tickets" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:36 +msgid "" +"The integration with the :doc:`Helpdesk <../helpdesk>` app lets your " +"helpdesk team manage intervention requests directly. Planning field service " +"tasks from tickets speeds up your processes." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:40 +msgid "Configure the helpdesk team" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:42 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`. Select" +" a team and enable :guilabel:`Onsite Interventions`." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Onsite interventions settings in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst:49 +msgid "" +"The helpdesk tickets of the team now display the :guilabel:`Plan " +"Intervention` button. Click on it to create a new task under your field " +"service project." +msgstr "" + +#: ../../content/applications/services/field_service/onsite_interventions.rst-1 +msgid "Plan intervention from helpdesk tickets in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:8 +msgid "Helpdesk" +msgstr "ดูแลช่วยเหลือ" + +#: ../../content/applications/services/helpdesk.rst:11 +msgid "`Odoo Tutorials: Helpdesk <https://www.odoo.com/slides/helpdesk-51>`_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced.rst:5 +msgid "Advanced" +msgstr "ขั้นสูง" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:3 +msgid "After-Sales services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:5 +msgid "" +"*After-Sales* services can be configured in the *Helpdesk* application for " +"individual *teams*. Once enabled, users can issue refunds, process returns, " +"generate coupons, and/or schedule repair and field service interventions " +"directly from a ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:10 +msgid "Set up the after-sales services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:12 +msgid "" +"Start by enabling the after-sales services on specific *Helpdesk* team(s), " +"by going to :menuselection:`Helpdesk --> Configuration --> Teams` and " +"selecting which teams(s) these services should be active on. Then, scroll to" +" the :guilabel:`After-Sales` section on the team's settings page, and choose" +" which of the following options to enable:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:17 +msgid "" +":guilabel:`Refunds`: issues credit notes to refund a customer, or adjust the" +" remaining amount due" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:18 +msgid "" +":guilabel:`Coupons`: offers discounts and free products through an existing " +"coupon program" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:19 +msgid "" +":guilabel:`Returns`: initiates a product return from a customer through a " +"reverse transfer" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:20 +msgid "" +":guilabel:`Repairs`: creates repair orders for broken or faulty products" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:21 +msgid "" +":guilabel:`Field Service`: plans onsite intervention through the *Field " +"Service* application" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:26 +msgid "" +"The services that are enabled can vary based on the type of support a team " +"provides." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:29 +msgid "" +"As all of the after-sales services in Odoo require integration with other " +"applications, enabling any of them may result in the installation of " +"additional modules or applications. *Installing a new application on a One-" +"App-Free database will trigger a 15-day trial. At the end of the trial, if a" +" paid subscription has not been added to the database, it will no longer be " +"accessible.*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:35 +msgid "Issue a refund with a credit note" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:37 +msgid "" +"A *credit note* is a document issued to a customer informing them that they " +"have been credited a certain amount of money. They can be used to provide a " +"full refund to a customer, or to adjust any remaining amount due. While they" +" are usually created through the *Accounting* or *Invoicing* applications, " +"they can be created through a *Helpdesk* ticket, as well." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:43 +msgid "Invoices must be posted before a credit note can be generated." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:45 +msgid "" +"To create a credit note, navigate to a ticket on the " +":menuselection:`Helpdesk` application, and click the :guilabel:`Refund` " +"button in the upper-left corner of the ticket dashboard. Then, select the " +"corresponding invoice from the :guilabel:`Invoices to Refund` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a refund creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:53 +msgid "Choose a :guilabel:`Credit Method` from one of the following options:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:55 +msgid "" +":guilabel:`Partial Refund`: the credit note is created in draft and can be " +"edited before being issued" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:57 +msgid "" +":guilabel:`Full Refund`: the credit note is auto-validated and reconciled " +"with the invoice. *This is the option to choose if a validated invoice needs" +" to be canceled*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:59 +msgid "" +":guilabel:`Full refund and new draft invoice`: the credit note is auto-" +"validated and reconciled with the invoice. The original invoice is " +"duplicated as a new draft. *This is the option to choose if a validated " +"invoice needs to be modified*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:64 +msgid "" +"The :guilabel:`Credit Method` options will **not** be available for invoices" +" that have already been paid." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:67 +msgid "" +"Make any necessary changes to the details of the credit note and click " +":guilabel:`Reverse.` Then click :guilabel:`Confirm` to post the credit note." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:70 +msgid "" +"Once the credit note has been posted, a :guilabel:`Credit Notes` smart " +"button will be added to the *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of smart buttons on a ticket focusing on the credit note button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:78 +msgid ":doc:`/applications/finance/accounting/customer_invoices/credit_notes`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:81 +msgid "Generate coupons from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:83 +msgid "" +"Coupons can be used to alter the price of products or orders. The usage " +"constraints of a coupon are defined by conditional rules. *Coupon Programs* " +"are configured in the *Sales* or *Website* applications." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:88 +msgid "" +"The *eCommerce* module must be installed in order to create coupon codes " +"from the *Website*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:90 +msgid "" +"To generate a coupon, open a *Helpdesk* ticket and click on the " +":guilabel:`Coupon` button in the upper left corner. Select an option from " +"the :guilabel:`Coupon Program` drop-down menu, then click " +":guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a coupon generation window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:98 +msgid "" +"The :guilabel:`Coupon Code` can be copied directly from the pop-up window " +"(by clicking the :guilabel:`Copy` button), or sent in an email by clicking " +":guilabel:`Send`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:102 +msgid "" +"When emailing a coupon code, all the followers of the ticket will be added " +"as recipients to the email. Additional recipients can be added to the email " +"as well, in the :guilabel:`Recipients` field of the :guilabel:`Compose " +"Email` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:0 +msgid "View of an email draft window with coupon code." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:110 +msgid "" +"Once a :guilabel:`Coupon Code` has been generated, a :guilabel:`Coupons` " +"smart button will be added to the top of the ticket; click the smart button " +"to view the coupon code, expiration date, and additional information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of the smart buttons on a ticket focusing on the coupon button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:119 +msgid "" +"`Coupons <https://www.odoo.com/slides/slide/coupon-" +"programs-640?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:122 +msgid "Facilitate a product return with a reverse transfer" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:124 +msgid "" +"Returns are completed through *reverse transfers*, which generate new " +"warehouse operations for the returning products. Click the " +":guilabel:`Return` button in the top-left corner of a ticket to open the " +":guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a Helpdesk ticket with the return button highlighted." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:133 +msgid "" +"The :guilabel:`Return` button only appears on a ticket if the customer has a" +" recorded delivery in the database." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:136 +msgid "" +"By default, the quantity will match the validated quantity from the delivery" +" order. Update the :guilabel:`Quantity` field if necessary." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a reverse transfer creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:143 +msgid "" +"Click :guilabel:`Return` to confirm the return. This generates a new " +"warehouse operation for the incoming returned product(s). A " +":guilabel:`Return` smart button will then be added to the top of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of the return smart button on a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:152 +msgid ":doc:`/applications/sales/sales/products_prices/returns`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:155 +msgid "Send products for repair from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:157 +msgid "" +"If the ticket is related to an issue with a faulty or broken product, a " +"repair order can be created from the *Helpdesk* ticket, and managed through " +"the *Repairs* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:160 +msgid "" +"To create a new repair order, open a :menuselection:`Helpdesk` ticket and " +"click on the :guilabel:`Repair` button in the upper left corner." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:163 +msgid "" +"Clicking the :guilabel:`Repair` button opens a blank :guilabel:`Repair " +"Reference` form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a repair reference page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:170 +msgid "" +"If a product was specified in the :guilabel:`Product` field on the ticket, " +"it will be added to the :guilabel:`Product to Repair` field automatically. " +"If not, click into the field to select a product from the drop down." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:174 +msgid "" +"Fill out the :guilabel:`Repair Description` field with a brief explanation " +"of the issue. Click the :guilabel:`Sale Order` field and then select the " +"originating :abbr:`SO (Sales Order)` from which the product is being " +"repaired from. If a return has been initiated for the product, select the " +"reference number from the drop-down in the :guilabel:`Return` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:179 +msgid "" +"Choose an :guilabel:`Invoice Method` from the drop-down. Select " +":guilabel:`Before Repair` or :guilabel:`After Repair` to generate an invoice" +" before or after the work is completed. Selecting :guilabel:`No Invoice` " +"means that an invoice cannot be generated for this service." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:183 +msgid "" +"If parts are required for the repair, they can be added in the " +":guilabel:`Parts` tab. Services can be added as product lines on the " +":guilabel:`Operations` tab. Additional information for the internal repair " +"team can be added to the :guilabel:`Repair Notes` tab. Information for the " +"customer can be added to the :guilabel:`Quotation Notes` tab, and will be " +"automatically added to the PDF of the quotations generated from this " +":guilabel:`Repair Reference`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:189 +msgid "" +"A :guilabel:`Repairs` smart button will be added to the ticket, linking to " +"the repair order." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of smart buttons focusing on repair button." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:196 +msgid "" +"Once a user creates a repair order from a *Helpdesk* ticket, they will be " +"able to access it through the ticket's :guilabel:`Repair` smart button, or " +"from a link in the :guilabel:`Chatter`, even if they do not have access " +"rights to the *Repair* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:201 +msgid "Create a field service task from a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:203 +msgid "" +"On-site interventions can be planned from a ticket and managed through the " +"*Field Service* application. Customers with :doc:`portal access " +"</applications/general/users/portal>` will be able to track the progress of " +"a :guilabel:`Field Service` task just as they would a *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:207 +msgid "" +"To create a new task, navigate to a :menuselection:`Helpdesk` ticket. Click " +":guilabel:`Create Task` to open the :guilabel:`Create a Field Service task` " +"pop-up. Confirm or update the task :guilabel:`Title`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:212 +msgid "" +"The :guilabel:`Project` field on the :guilabel:`Create a Field Service task`" +" pop-up will default to the same *Field Service* project that was identified" +" on the team's settings page. To change the project for this specific task, " +"select one from the :guilabel:`Project` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:216 +msgid "" +"To change the default *Field Service* project for the team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` to select a " +":guilabel:`Team`. Scroll to the :guilabel:`After-Sales` section and choose " +"new project under :guilabel:`Field Service`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:220 +msgid "Click :guilabel:`Create Task` or :guilabel:`Create & View Task`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of a Field Service task creation page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:226 +msgid "" +"After the task is created, a :guilabel:`Tasks` smart button will be added to" +" the ticket, linking the :guilabel:`Field Service` task to the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst-1 +msgid "View of ticket smart buttons focused on task." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/after_sales.rst:234 +msgid "" +"`Field Service <https://www.odoo.com/slides/slide/advanced-" +"settings-862?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:3 +msgid "Closing tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:5 +msgid "" +"Once work has been completed on a *Helpdesk* ticket in Odoo, there are " +"several ways it can be closed. Manually closing solved tickets keeps the " +"pipeline up to date, while automatically closing inactive tickets prevents " +"unnecessary blocking issues. Allowing customers to close their own tickets " +"minimizes confusion around whether an issue is considered solved or not. " +"This results in increased operational capacity for support teams, and higher" +" customer satisfaction." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:12 +msgid "Manually close solved tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:14 +msgid "" +"As work on a ticket progresses, it is moved along to the next stage in the " +"pipeline. Once the issue is solved, the ticket is moved to a *folded* stage." +" This marks the ticket as *closed*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:17 +msgid "" +"To fold a stage, navigate to the :menuselection:`Helpdesk` dashboard and " +"click on a team to open the pipeline. Hover over a stage's heading, and then" +" click the gear icon that appears in the top-right corner of that stage's " +"kanban column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "" +"View of stage on Helpdesk pipeline with emphasis on gear icon and edit stage" +" option." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:26 +msgid "" +"Clicking the gear icon also displays the option to :guilabel:`Fold` the " +"stage. This setting folds the stage *temporarily* to simplify the kanban " +"view. This does *not* close the tickets in this stage. It also does not " +"permanently fold the stage. If a stage needs to be folded so the tickets can" +" be marked as closed, continue following the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:31 +msgid "" +"From the menu that appears, select :guilabel:`Edit Stage`. This will open " +"the stage's settings. Check the box labeled :guilabel:`Folded in Kanban` " +"towards the top of the window, and then :guilabel:`Save & Close` to confirm " +"the changes. Now, tickets that reach this stage will be considered as " +"*closed*." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0 +msgid "Stage settings page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:41 +msgid "Automatically close inactive tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:43 +msgid "" +"Tickets that are inactive for a set period of time can be automatically " +"closed. At that point, they will be moved to a folded stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:46 +msgid "" +"Go to the team's settings page by going to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. Under the :guilabel:`Self-Service` section, enable" +" :guilabel:`Automatic Closing`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:49 +msgid "" +"If one of the team's stages is set to be folded in the kanban view, it will " +"be the default selection in the :guilabel:`Move to Stage` field. If the team" +" has more than one folded stage, the stage that occurs first in the pipeline" +" will be the default. If no stage is folded, the default selection will be " +"the last stage in the pipeline." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:54 +msgid "" +"The :guilabel:`After days of inactivity` field defaults to `7`, but can be " +"adjusted if necessary." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:57 +msgid "" +"The :guilabel:`After days of inactivity` field does **not** take the working" +" calendar into account when tracking the amount of time a ticket has been " +"inactive." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:60 +msgid "" +"If only certain stages should be used to track days of inactivity, they can " +"be added to the :guilabel:`In Stages` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:64 +msgid "A team's pipeline is created with the following stages:" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:66 +msgid "`New`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:67 +msgid "`In Progress`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:68 +msgid "`Customer Feedback`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:69 +msgid "`Closed`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:71 +msgid "" +"Tickets can linger in the :guilabel:`Customer Feedback stage`, because once " +"an issue is solved, customers may not respond immediately. At that point, " +"the tickets can be closed automatically. However, tickets in the " +":guilabel:`New` and :guilabel:`In Progress` stages may remain inactive due " +"to assignment or workload issues. Closing these tickets automatically would " +"result in issues going unsolved." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:77 +msgid "" +"Therefore, the :guilabel:`Automatic Closing` settings would be configured as" +" below\\:\\" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:79 +msgid ":guilabel:`Automatic Closing`: *checked*" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:80 +msgid ":guilabel:`Move to Stage`: `Solved`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:81 +msgid ":guilabel:`After``7`:guilabel:`days of inactivity`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:82 +msgid ":guilabel:`In Stages`: `Customer Feedback`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:0 +msgid "Example of Automatic Closing settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:89 +msgid "Allow customers to close their own tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:91 +msgid "" +"Enabling the :guilabel:`Closure by Customers` setting allows customers to " +"close their own ticket(s) when they determine that their issue has been " +"resolved." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:94 +msgid "" +"Start by navigating to :menuselection:`Helpdesk --> Configuration --> Teams`" +" and select a team. On the team's settings page, scroll to the " +":guilabel:`Self-Service` section and check the box for :guilabel:`Closure by" +" Customers`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Customer closing setting in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:102 +msgid "" +"Once the ticket closing settings are enabled, a :guilabel:`Close Ticket` " +"button will be available for customers when they view their ticket through " +"the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst-1 +msgid "Customer view of ticket closing in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:110 +msgid "" +"Customers are able to view their tickets by clicking the :guilabel:`View the" +" ticket` link they receive by email. The link is included in the " +":guilabel:`Request Acknowledgment` template, which is added to the first " +"stage of a team by default. This link does not require a customer to have " +"access to the portal to view or respond to their ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/close_tickets.rst:115 +msgid "" +"Customers with access to the portal will be able to view their tickets under" +" :menuselection:`My Account --> Tickets`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:3 +msgid "Track and bill time" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:5 +msgid "" +"Odoo *Helpdesk* provides teams with the ability to track the amount of hours" +" spent working on a ticket, and to bill a customer for that time. Through " +"integrations with the *Sales*, *Timesheets* and *Accounting* applications, " +"customers can be charged once the work is completed, or before it has even " +"begun." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:11 +msgid "" +"Since the *Track & Bill Time* features require integration with other " +"applications, enabling them may result in the installation of additional " +"modules (or applications)." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:14 +msgid "" +"Installing a new application on a *One-App-Free* database triggers a 15-day " +"trial. At the end of the trial, if a paid subscription has not been added to" +" the database, it will no longer be active or accessible." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:19 +msgid "Configure track and bill time features" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:21 +msgid "" +"Before a customer can be invoiced for support services, the *Track & Bill " +"Time* features must first be enabled. These features must be enabled on each" +" *Helpdesk* team where they will be utilized." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:25 +msgid "Enable track and bill time on a helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:27 +msgid "" +"To view and enable the :guilabel:`Track & Bill Time` features on a " +"*Helpdesk* team, first navigate to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. Then select a team from the list or :doc:`create a" +" new one </applications/services/helpdesk/overview/getting_started>`. This " +"will reveal a team's settings page." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:32 +msgid "" +"On the team's settings page, scroll to the :guilabel:`Track & Bill Time` " +"section. Check the boxes labeled :guilabel:`Timesheets` and :guilabel:`Time " +"Billing`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:35 +msgid "" +"Once the :guilabel:`Timesheets` box is checked, a new field appears, labeled" +" :guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:37 +msgid "" +"The project selected in this field is where all the timesheets for this " +"team's tickets will be recorded. Click into the drop-down menu to select a " +":guilabel:`Project`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:40 +msgid "" +"To create a new project where the timesheets will be recorded, click into " +"the drop-down menu, type a name for the project, and then click " +":guilabel:`Create`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a helpdesk team settings page emphasizing the track and bill time " +"settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:50 +msgid "Configure service products" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:52 +msgid "" +"When the :guilabel:`Time Billing` feature is enabled, a new product is " +"created in the *Sales* app called :guilabel:`Service on Timesheets`. This " +"product can be found under :menuselection:`Sales --> Products --> Products`." +" Search for `Service on Timesheets` in the :guilabel:`Search...` bar. This " +"is the product that will be used when invoicing for *post-paid support " +"services* after they have been completed." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:58 +msgid "" +"Select :guilabel:`Service on Timesheets` from the product page. This reveals" +" the product detail form. The product is configured with the " +":guilabel:`Product Type` set to :guilabel:`Service` and the " +":guilabel:`Invoicing Policy` set to :guilabel:`Based on Timesheets`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a service product with the invoicing policy set to 'Based on " +"timesheets'." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:66 +msgid "" +"In order to invoice for support services before the work has been completed " +"(also known as *prepaid support services*), a separate product with a " +"different invoicing policy must be created." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:69 +msgid "" +"To create a new service product, go to :menuselection:`Sales --> Products " +"--> Products` and click :guilabel:`New`. This will reveal a blank product " +"detail form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:72 +msgid "" +"On the new product form, add a :guilabel:`Product Name`, and set the " +":guilabel:`Product Type` to :guilabel:`Service`. Then, set the " +":guilabel:`Invoicing Policy` to :guilabel:`Prepaid/Fixed Price`. This means " +"an invoice can be generated and payment can be received for this product " +"before any timesheets entries have been recorded for these services." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of a service product with the invoicing policy set to 'prepaid/fixed'." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:81 +msgid "" +"Finally, set the :guilabel:`Sales Price`, and confirm that the " +":guilabel:`Unit of Measure` is set to :guilabel:`Hours`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:85 +msgid "Invoice prepaid support services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:87 +msgid "" +"When support services are billed on a fixed price, an invoice can be created" +" before any work is completed on the issue. In this case, a service product " +"with the invoicing policy set to :guilabel:`Prepaid/Fixed Price` would be " +"used, just like :ref:`the section above <helpdesk/advanced/configure-" +"service-products>`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:93 +msgid "Create a sales order with prepaid product" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:95 +msgid "" +"To invoice a customer for prepaid support services, first create a sales " +"order (SO) with the support services product. To do this, go to " +":menuselection:`Sales --> Orders --> Quotations --> New`, which reveals a " +"blank quotation form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:99 +msgid "Then, fill out the quotation form with the customer information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:101 +msgid "" +"Go to the :guilabel:`Order Lines` tab of the quotation and click " +":guilabel:`Add a Product`. Then, select the *prepaid services product* " +"configured in the steps above. Update the :guilabel:`Quantity` field with " +"the number of hours." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:105 +msgid "" +"After updating any other necessary information, :guilabel:`Confirm` the " +"quotation. This converts the quotation into an :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:109 +msgid "Create and send an invoice for prepaid services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:111 +msgid "" +"Once the :abbr:`SO (sales order)` has been confirmed, click the " +":guilabel:`Create Invoice` button. This will open a :guilabel:`Create " +"Invoices` pop-up window." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:114 +msgid "" +"If no down payment will be collected, the :guilabel:`Create Invoice` type " +"can remain as :guilabel:`Regular Invoice`. If a down payment will be " +"collected, choose between either :guilabel:`Down payment (percentage)` or " +":guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:118 +msgid "" +"When the necessary information has been entered, click :guilabel:`Create " +"Draft Invoice`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:120 +msgid "The invoice can then be sent to the customer for payment." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:123 +msgid "Create helpdesk ticket for prepaid services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:125 +msgid "" +"To create a *Helpdesk* ticket for prepaid services, navigate to " +":menuselection:`Helpdesk` and click the :guilabel:`Tickets` button to reveal" +" a specific team's pipeline. Click :guilabel:`New` to create a new ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:129 +msgid "" +"On the blank ticket form, create a ticket :guilabel:`Title`, and enter the " +":guilabel:`Customer` information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:132 +msgid "" +"When the customer name is added, the :guilabel:`Sales Order Item` field will" +" automatically populate with the most recent prepaid sales order item that " +"has time remaining." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:136 +msgid "Track hours on helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:138 +msgid "" +"Time spent working on a *Helpdesk* ticket is tracked on the *Timesheets* tab" +" on the specific ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:140 +msgid "" +"On the ticket detail form, click on the :guilabel:`Timesheets` tab and click" +" :guilabel:`Add a line`. Choose an :guilabel:`Employee`, add a " +":guilabel:`Description` of the task, and enter the number of " +":guilabel:`Hours Spent`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144 +msgid "" +"As new lines are added to :guilabel:`Timesheets` tab, the " +":guilabel:`Remaining Hours on SO` field is automatically updated." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "" +"View of the timesheets tab on a ticket with an emphasis on the remaining " +"hours on an SO." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:152 +msgid "" +"If the number of hours on the :guilabel:`Timesheets` tab exceeds the number " +"of hours sold, the :guilabel:`Remaining Hours of SO` will turn red." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:155 +msgid "" +"As hours are added to the :guilabel:`Timesheets` tab, they are automatically" +" updated in the :guilabel:`Delivered` field on the :abbr:`SO (sales order)`," +" as well." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:159 +msgid "Invoice post-paid support services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:161 +msgid "" +"When support services are billed based on the amount of time spent on an " +"issue, an invoice cannot be created before the total number of hours " +"required to solve the problem have been entered on a timesheet. In this " +"case, a service product with the invoicing policy set to :guilabel:`Based on" +" Timesheets` would be used, like the one created above." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:167 +msgid "Create a sales order with a time-tracked product" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:169 +msgid "" +"To invoice a customer for post-paid support services, first create a sales " +"order (SO) with the *support services product*. To do this, go to " +":menuselection:`Sales --> Orders --> Quotations --> New`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:173 +msgid "Fill out the quotation with the customer information." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:175 +msgid "" +"On the :guilabel:`Order Lines` tab, click :guilabel:`Add a Product`. Select " +"the post-paid services product configured in the steps above. After updating" +" any other necessary information, :guilabel:`Confirm` the quotation." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:180 +msgid "" +"Unlike with the prepaid services quotation, Odoo will not allow an invoice " +"to be created at this time. That is because no services have been performed;" +" in other words nothing has been delivered, therefore, there is nothing to " +"invoice." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:185 +msgid "Create a helpdesk ticket for time-tracked services" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:187 +msgid "" +"To record a *Timesheet* entry for time-tracker services, go to " +":menuselection:`Helpdesk` and select the appropriate team for which these " +"services apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:190 +msgid "" +"If there is already an existing ticket for this issue, select it from the " +"kanban view. This will open the ticket details form. If there is no existing" +" ticket for this customer issue, click :guilabel:`New` to create a new " +"ticket and enter the necessary customer information on the blank ticket " +"details form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:195 +msgid "" +"After selecting or creating a ticket, go to the :guilabel:`Sales Order Line`" +" drop-down menu. Select the :abbr:`SO (sales order)` created in the previous" +" step." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:199 +msgid "Track support hours on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:201 +msgid "" +"In order to create an invoice for a product based on timesheets, hours need " +"to be tracked and recorded. At this point, the service is considered " +"*delivered*. To record hours for this support service, click on the " +":guilabel:`Timesheets` tab of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:205 +msgid "" +"Click :guilabel:`Add a Line` to record a new entry. Select an " +":guilabel:`Employee` from the drop-down menu, and record the time spent in " +"the :guilabel:`Hours Spent` column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:208 +msgid "" +"Repeat these steps as needed until all time spent on the issues has been " +"recorded." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of the timesheets tab on a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:215 +msgid "Create an invoice for hours tracked on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:217 +msgid "" +"After the customer's issue has been solved, and it is determined no new " +"timesheet entries will be made, an invoice can be created, and the customer " +"can be billed." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:220 +msgid "" +"To do this, return to the :abbr:`SO (sales order)` by clicking on the " +":guilabel:`Sales Order` smart button at the top of the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:223 +msgid "" +"Before creating the invoice, confirm that the number in the " +":guilabel:`Delivered` column matches the total number of :guilabel:`Hours " +"Spent` listed in the :guilabel:`Timesheets` tab on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of a sales order with emphasis on the delivered column." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:230 +msgid "" +"Then, click :guilabel:`Create Invoice`. This will open a :guilabel:`Create " +"Invoices` pop-up window. If no down payment will be collected, the " +":guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. " +"If a down payment will be collected, choose between either :guilabel:`Down " +"payment (percentage)` or :guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:236 +msgid "" +"Use the :guilabel:`Timesheets Period` field if this invoice should only " +"include timesheets from a certain time period. If this field is left blank, " +"*all* applicable timesheets that have not yet been invoiced will be " +"included." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst-1 +msgid "View of create invoices pop up showing timesheets period fields." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:244 +msgid "" +"When the necessary information has been entered, click :guilabel:`Create " +"Invoice`. The invoice can then be sent to the customer for payment." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview.rst:5 +#: ../../content/applications/services/timesheets/overview.rst:5 +msgid "Overview" +msgstr "ภาพรวม" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:3 +msgid "Getting started with Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:5 +msgid "" +"Odoo :guilabel:`Helpdesk` is a ticket-based customer support application. " +"Teams can track, prioritize, and solve customer issues from their pipeline, " +"which is organized in customizable stages. Multiple teams can be configured " +"and managed in one dashboard." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:10 +msgid "Create Helpdesk teams" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:12 +msgid "" +"Setting up multiple teams allows for tickets to be grouped by location or by" +" support type." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:14 +msgid "" +"To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk --> " +"Configuration --> Teams`. To create a new team, click on the :guilabel:`New`" +" button in the top left of the dashboard. From there, name the new team, and" +" fill out the remaining fields as defined in the following sections on the " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of the Helpdesk teams page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:24 +msgid "Assignment & Visibility" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:27 +msgid "Determine to whom the team will be visible" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:29 +msgid "" +"Under the :guilabel:`Visibility` section, determine who can view this team " +"and its tickets." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:31 +msgid "" +":guilabel:`Invited internal users` have access to the team and tickets they " +"are following. This can be modified on each individual ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:33 +msgid "" +":guilabel:`All internal users` have access to the team and all of its " +"tickets without being a follower." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:35 +msgid "" +":guilabel:`Invited portal users and all internal users` have access to the " +"team without being a follower. Portal users will only be able to access " +"tickets that they are following." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:39 +msgid "" +"A `Customer Support` team intended to handle general issues with shipping " +"and product issues would have the visibility setting :guilabel:`Invited " +"portal users and all internal users`. However, a `Financial Services` team " +"handling tickets related to accounting or tax information would only need to" +" be visible to :guilabel:`Invited internal users`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:45 +msgid "Automatically assign new tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:47 +msgid "" +"When tickets are received, they will need to be assigned to a member of the " +"support team. This can be done manually on each ticket individually, or " +"through :guilabel:`Automatic Assignment`. Check the box next to " +":guilabel:`Automatic Assignment` to enable the feature for this team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of a Helpdesk team settings page emphasizing the assignment and visibility features\n" +"in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:56 +msgid "" +"Select one of the following assignment methods, based on how workload should" +" be allocated across the team:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60 +msgid "" +":guilabel:`Each user is assigned an equal number of tickets` assigns tickets" +" to team members" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:60 +msgid "" +"based on total ticket count, regardless of the number of open or closed " +"tickets they are currently assigned." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:64 +msgid "" +":guilabel:`Each user has an equal number of open tickets` assigned tickets " +"to team members based" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:63 +msgid "" +"on how many open tickets they are currently assigned. This option is useful " +"for automatically delegating a heavier workload to high-performers who tend " +"to close tickets quickly." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:66 +msgid "" +"Finally, add the :guilabel:`Team Members` who will be assigned tickets for " +"this team. Leave the field empty to include all employees who have the " +"proper assignments and access rights configured in their user account " +"settings." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:71 +msgid "" +"If an employee has time off scheduled in the :guilabel:`Time Off` " +"application, they will not be assigned tickets during that time. If no " +"employees are available, the system will look ahead until there is a match." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:76 +msgid ":ref:`Manage users <users/add-individual>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:77 +msgid ":doc:`Access rights </applications/general/users/access_rights>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:80 +msgid "Create or modify kanban stages" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:82 +msgid "" +":guilabel:`Stages` are used to organize the *Helpdesk* pipeline and track " +"the progress of tickets. Stages are customizable, and can be renamed to fit " +"the needs of each team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:85 +msgid "" +"To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk --> " +"Configuration --> Stages`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:88 +msgid "" +":ref:`Developer mode <developer-mode>` must be activated in order to access " +"the stages menu. To activate developer mode go to :menuselection:`Settings " +"--> General Settings --> Developer Tools` and click on :guilabel:`Activate " +"the developer mode`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:92 +msgid "" +"The list view shows an overview of all the stages currently available in " +"Helpdesk. They are listed in the order they appear in the pipeline. To " +"change the order of the stages, use the arrow buttons on the left side of " +"the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:97 +msgid "" +"Change the stage order on the kanban view by dragging and dropping " +"individual columns." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "" +"View of the stage list page emphasizing the option to create a new stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:104 +msgid "" +"To create a new stage, click on the :guilabel:`New` button in the top left " +"of the dashboard. Next, choose a name for the new stage, and add a " +"description (though it is not required). Fill out the remaining fields " +"following the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of a stage's settings page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:113 +msgid "Add email and SMS templates to stages" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:115 +msgid "" +"When an :guilabel:`Email Template` is added to a stage, an email is " +"automatically sent to the the customer when a ticket reaches that specific " +"stage in the helpdesk pipeline. Likewise, adding an :guilabel:`SMS Template`" +" will result in an SMS text message being sent to the customer." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:120 +msgid "" +"SMS Text Messaging is an In-App Purchase (IAP) service that requires prepaid" +" credits to work. Refer to `SMS Pricing FAQ <https://iap-" +"services.odoo.com/iap/sms/pricing>`_ for additional information." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:124 +msgid "" +"To select an existing email template, select it from the :guilabel:`Email " +"Template` field. Click on the arrow key to the right of the field to edit " +"the template." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:127 +msgid "" +"To create a new template, click the field and begin typing a new template " +"title. Then select :guilabel:`Create and edit`, and complete the form " +"details." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:130 +msgid "" +"Follow the same steps to select, edit, or create an :guilabel:`SMS " +"Template`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst-1 +msgid "View of an SMS template setup page in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:137 +#: ../../content/applications/services/helpdesk/overview/ratings.rst:60 +msgid ":doc:`/applications/general/email_communication/email_template`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:140 +msgid "Assign stages to a team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:142 +msgid "" +"Make a selection in the :guilabel:`Teams` field on the :guilabel:`Stages` " +"form. More than one team may be selected, since the same stage(s) can be " +"assigned to multiple teams." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:0 +msgid "View of stage setup emphasizing teams field" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:150 +msgid "Fold a stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:152 +msgid "" +"Check the :guilabel:`Folded in Kanban` box on the :guilabel:`Stages` form to" +" display this stage as *folded* by default in the kanban view for this team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:156 +msgid "" +"Tickets that reach a *folded* stage are considered closed. Closing a ticket " +"before the work is completed can result in reporting and communication " +"issues. This setting should only be enabled for stages that are considered " +"*closing* stages." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:160 +msgid "" +"Alternatively, stages can be temporarily folded in the kanban view, by " +"clicking on the settings icon and selecting :guilabel:`Fold`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/getting_started.rst:164 +msgid "" +"Manually folding a stage from the kanban view will not close the tickets in " +"the stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:3 +msgid "Help center" +msgstr "ศูนย์ช่วยเหลือ" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:5 +msgid "" +"Odoo *Helpdesk* integrates with the *Forum*, *eLearning*, and *Knowledge* " +"apps to create the *help center*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "" +"Overview of the settings page of a team emphasizing the help center " +"features." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:12 +msgid "" +"The *help center* is a centralized location where teams and customers can " +"search for and share detailed information about products and services." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:16 +msgid "" +"In order to activate any of these features on a *Helpdesk* team, (*Forums*, " +"*eLearning*, or *Knowledge*), the :guilabel:`Visibility` of the team has to " +"be set to :guilabel:`Invited portal users and all internal users`. See " +":doc:`Getting Started " +"</applications/services/helpdesk/overview/getting_started>` for more " +"information on *Helpdesk* team settings and configuration." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:23 +msgid "" +"Since all of the *help center* features require integration with other " +"applications, enabling any of them may result in the installation of " +"additional modules or applications." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:26 +msgid "" +"Installing a new application on a *One-App-Free* database will trigger a " +"15-day trial. At the end of the trial, if a paid subscription has not been " +"added to the database, it will no longer be active or accessible." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:31 +msgid "Knowledge" +msgstr "ความรู้" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:33 +msgid "" +"Odoo's *Knowledge* application is a collaborative library where users can " +"store, edit, and share information. The *Knowledge* app is represented " +"throughout the database by a *book* icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a message in Helpdesk focusing on the Knowledge book icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:41 +msgid "Enable Knowledge on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:43 +msgid "" +"To enable the *Knowledge* feature on a *Helpdesk* team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or " +"create a :doc:`new one " +"</applications/services/helpdesk/overview/getting_started>`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:47 +msgid "" +"When a team has been selected or created, Odoo displays that team's detail " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:49 +msgid "" +"On the team's detail form, scroll down to the :guilabel:`Self-Service` " +"section. Click the box next to :guilabel:`Knowledge` to activate the " +"*Knowledge* feature. When clicked, a new field labeled :guilabel:`Article` " +"appears." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:53 +msgid "" +"Clicking the :guilabel:`Article` field reveals a drop-down menu. At first, " +"there is only one option in the drop-down menu titled :guilabel:`Help`, " +"which Odoo provides by default. Select :guilabel:`Help` from the drop-down " +"menu to choose this article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:58 +msgid "" +"To create a new article, go to the :menuselection:`Knowledge app`, then " +"hover the cursor next to the :guilabel:`Workspace` section heading, located " +"in the left sidebar. Moving the cursor there reveals a hidden :guilabel:`➕ " +"(plus sign)` icon." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:62 +msgid "" +"Click the :guilabel:`➕ (plus sign)` to create a new article in the " +":guilabel:`Workspace`. In the upper right corner of the page, click the " +":guilabel:`Share` button, and slide the :guilabel:`Share to Web` toggle " +"switch until it reads :guilabel:`Article Published`. It can then be added to" +" a *Helpdesk* team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:67 +msgid "" +"Once an article has been created and assigned to a *Helpdesk* team, content " +"can be added and organized through the *Knowledge* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:71 +msgid "" +":doc:`Editing Knowledge articles " +"</applications/productivity/knowledge/articles_editing>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:74 +msgid "Search articles from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:76 +msgid "" +"When members of a *Helpdesk* team are trying to solve a ticket, they can " +"search through the content in the *Knowledge* app for more information on " +"the issue." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:79 +msgid "" +"To search *Knowledge* articles, open a ticket — either from the *Helpdesk* " +"app dashboard, or by going to :menuselection:`Helpdesk app --> Tickets --> " +"All Tickets`, and selecting a :guilabel:`Ticket` from the list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:83 +msgid "" +"When a :guilabel:`Ticket` is selected, Odoo reveals that ticket's detail " +"form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:85 +msgid "" +"Click the :guilabel:`Knowledge (book)` icon, located above the chatter to " +"open a search window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of knowledge search window from a helpdesk ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:92 +msgid "" +"*Knowledge* articles can also be searched by pressing :command:`Ctrl + K` to" +" open the command palette, then typing :command:`?`, followed by the name of" +" the desired article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:95 +msgid "" +"When Odoo reveals the desired article, click it, or highlight the " +":guilabel:`Article` title, and press :command:`Enter`. This will open the " +"article in the :guilabel:`Knowledge` application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:98 +msgid "To open the article in a new tab, press :command:`Ctrl + Enter`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:101 +msgid "" +"If a more in-depth search is required, press :command:`Alt + B`. That will " +"reveal a separate page, in which a more detailed search can occur." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:105 +msgid "Share articles to the help center" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:107 +msgid "" +"In order for a *Knowledge* article to be available to customers and website " +"visitors, it has to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:111 +msgid "" +"Even though the *Help* article has been enabled on a team, Odoo will not " +"share all the nested articles to the web. Individual articles intended for " +"customers **must** be published for them to be viewable on the website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:115 +msgid "" +"To publish an article, navigate to the desired article, by following the " +"above steps, and click the :guilabel:`Share` icon in the upper-right corner." +" This will reveal a menu. Slide the toggle button labeled :guilabel:`Share " +"to Web` to read :guilabel:`Article Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a knowledge article focused on sharing and publishing options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:124 +msgid "Solve tickets with templates" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:126 +msgid "" +"*Template* boxes can be added to *Knowledge* articles to allow content to be" +" reused, copied, sent as messages, or added to the description on a ticket. " +"This allows teams to maintain consistency when answering customer tickets, " +"and minimize the amount of time spent on responding to repeat questions." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:131 +msgid "Add templates to articles" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:133 +msgid "" +"To create a template, go to :menuselection:`Knowledge --> Help`. Click on an" +" existing nested article or create a new one by clicking the :guilabel:`➕ " +"(plus sign)` icon next to *Help*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:136 +msgid "" +"Type `/` to open the :guilabel:`Powerbox` and view a list of :doc:`commands " +"</applications/productivity/knowledge/articles_editing>`. Select or type " +"`template`. A gray template block will be added to the page. Add any " +"necessary content to this block." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a template in knowledge with focus on send and copy options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:145 +msgid "" +"Templates will only display the :guilabel:`Use as description` or " +":guilabel:`Send as Message` options if they are accessed directly from " +"*Helpdesk*." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:149 +msgid "Use templates in tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:151 +msgid "" +"Templates can be used to respond directly to a *Helpdesk* ticket as a " +"message, or to add information to the ticket's description." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:154 +msgid "" +"To use templates in a *Helpdesk* ticket, first, open a ticket, either from " +"the :guilabel:`Helpdesk` dashboard or by going to :menuselection:`Helpdesk " +"--> Tickets --> All Tickets` and selecting a :guilabel:`Ticket` from the " +"list." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:158 +msgid "" +"Click on the :guilabel:`Knowledge (book)` icon above the chatter for the " +"ticket. This opens a search window. In this search window, select, or search" +" for the desired article. Doing so reveals that article page in the Odoo " +"*Knowledge* application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:162 +msgid "" +"To use a template to respond to a ticket, click :guilabel:`Send as message` " +"in the upper right corner of the template box, located in the body of the " +"article." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:165 +msgid "" +"Doing so opens a :guilabel:`Compose email` pop-up window. In this window, " +"select the recipients, make any necessary additions or edits to the " +"template, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:169 +msgid "" +"To use a template to add information to a ticket's description, click " +":guilabel:`Use as description` in the upper right corner of the template " +"box, located in the body of the article. Doing so will not replace the " +"existing text in a ticket's description. The template will be added as " +"additional text." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:177 +msgid "Community Forum" +msgstr "ฟอรั่มชุมชน" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:179 +msgid "" +"A *Community Forum* provides a space for customers to answer each other's " +"questions and share information. By integrating a forum with a *Helpdesk* " +"team, tickets submitted by customers can be converted to posts and shared." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:184 +msgid "Enable forums on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:186 +msgid "" +"To enable :guilabel:`Community Forums` on a *Helpdesk* team, start by " +"navigating to :menuselection:`Helpdesk app --> Configuration --> Teams` and " +"select a team, or create a :doc:`new one " +"</applications/services/helpdesk/overview/getting_started>`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:190 +msgid "" +"Selecting or creating a team reveals that team's detail form. Scroll down to" +" the :guilabel:`Self-Service` section of features, and enable " +":guilabel:`Community Forum`, by checking the box beside it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:194 +msgid "" +"When activated, a new field labeled :guilabel:`Forums` appears beneath." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:196 +msgid "" +"Click the empty :guilabel:`Forums` field to reveal a drop-down menu. By " +"default, there is only one option to begin with, labeled :guilabel:`Help`. " +"That is the option Odoo automatically created when the :guilabel:`Community " +"Forums` feature was enabled. Select :guilabel:`Help` from the drop-down menu" +" to enable that forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:201 +msgid "" +"To create a new forum, type a name into the blank :guilabel:`Forums` field, " +"then click the :guilabel:`Create and Edit` option. Multiple forums can be " +"selected in this field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:205 +msgid "" +"Check out the :doc:`Forum documentation <../../../websites/forum>` to learn " +"how to configure, use, and moderate a forum." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:209 +msgid "Create a forum post from a Helpdesk ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:211 +msgid "" +"When a *Helpdesk* team has a *Forum* enabled, tickets submitted to that team" +" can be converted to forum posts." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:214 +msgid "" +"To do that, select a ticket, either from a team's pipeline or from " +":menuselection:`Tickets --> All Tickets` in the :guilabel:`Helpdesk` " +"application." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:217 +msgid "" +"At the top of the ticket detail form, click the :guilabel:`Share on Forum` " +"button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "" +"Overview of the Forums page of a website to show the available ones in Odoo " +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:223 +msgid "" +"When clicked, a pop-up appears. Here, the post and title can be edited to " +"correct any typos, or modified to remove any proprietary or client " +"information. :guilabel:`Tags` can also be added to help organize the post in" +" the forum, making it easier for users to locate during a search. When all " +"adjustments have been made, click :guilabel:`Create and View Post`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:229 +msgid "eLearning" +msgstr "การอบรมออนไลน์" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:231 +msgid "" +"Odoo *eLearning* courses offer customers additional training and content in " +"the form of videos, presentations, and certifications/quizzes. Providing " +"additional training enables customers to work through issues and find " +"solutions on their own. They can also develop a deeper understanding of the " +"services and products they are using." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:237 +msgid "Enable eLearning courses on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:239 +msgid "" +"To enable *eLearning* courses on a *Helpdesk* team, go to " +":menuselection:`Helpdesk --> Configuration --> Teams` and select a team, or " +"create a :doc:`new one " +"</applications/services/helpdesk/overview/getting_started>`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:243 +msgid "" +"On the team's settings page, scroll to the :guilabel:`Self-Service` section," +" and check the box next to :guilabel:`eLearning`. A new field will appear " +"below, labeled :guilabel:`Courses`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:246 +msgid "" +"Click the empty field next to :guilabel:`Courses` beneath the " +":guilabel:`eLearning` feature to reveal a drop-down menu. Select an " +"available course from the drop-down menu, or type a title into the field, " +"and click :guilabel:`Create and edit` to create a new course from this page." +" Multiple courses can be assigned to a single team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:252 +msgid "Create an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:254 +msgid "" +"A new *eLearning* course can be created from the :guilabel:`Helpdesk` team's" +" settings page, as in the step above, or from the *eLearning* app." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:257 +msgid "" +"To create a course directly through the *eLearning* application, navigate to" +" :menuselection:`eLearning --> New`. This reveals a blank course template " +"that can be customized and modified as needed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:261 +msgid "" +"On the course template page, add a :guilabel:`Course Title`, and below that," +" :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:263 +msgid "" +"Click on the :guilabel:`Options` tab. Under :guilabel:`Access Rights`, " +"choose the :guilabel:`Enroll Policy`. This determines which users will be " +"allowed to take the course. Under :guilabel:`Display`, choose the course " +":guilabel:`Type` and :guilabel:`Visibility`. The :guilabel:`Visibility` " +"setting determines whether the course will be available to public site " +"visitors or members." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:269 +msgid "Add content to an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:271 +msgid "" +"To add content to a course, click the :guilabel:`Content` tab and select " +":guilabel:`Add Content`. Choose the :guilabel:`Content Type` from the drop-" +"down menu and upload the file, or paste the link, where instructed. Click " +":guilabel:`Save` when finished. Click :guilabel:`Add Section` to organize " +"the course in sections." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a course being published for Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:281 +msgid "" +"In order to add a certification to a course, go to :menuselection:`eLearning" +" --> Configuration --> Settings`, check the box labeled " +":guilabel:`Certifications`, and :guilabel:`Save` to activate the setting." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:286 +msgid "" +"`Odoo Tutorials: eLearning <https://www.odoo.com/slides/elearning-56>`_" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:289 +msgid "Publish an eLearning course" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:291 +msgid "" +"To allow customers to enroll in a course, both the course and the contents " +"need to be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:293 +msgid "" +"If the course is published, but the contents of the course are not " +"published, customers can enroll in the course on the website, but they won't" +" be able to view any of the course content. Knowing this, it may be " +"beneficial to publish the course first if the course contents are intended " +"to be released over time, such as classes with a weekly schedule." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:298 +msgid "" +"To make the entire course available at once, each piece of course content " +"must be published first, then the course can be published." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:301 +msgid "" +"To publish a course, choose a course from the *eLearning* dashboard. On the " +"course template page, click the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:304 +msgid "" +"This will reveal the front end of the course's web page. At the top of the " +"course web page, move the :guilabel:`Unpublished` toggle switch to " +":guilabel:`Published`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:308 +msgid "Publish eLearning course contents from the back-end" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:310 +msgid "" +"To publish *eLearning* course content from the back-end, choose a course " +"from the *eLearning* dashboard. On the course template page, click the " +":guilabel:`Published Contents` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:313 +msgid "" +"Doing so reveals a separate page displaying all the published content " +"related to that course. Remove the default :guilabel:`Published` filter from" +" the search bar in the upper-right corner, to reveal all the content related" +" to the course - even the non-published content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:317 +msgid "" +"Click the :guilabel:`≣ (List View)` icon in the upper-right corner, directly" +" beneath the search bar to switch to list view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:320 +msgid "" +"While in :guilabel:`List View`, there is a checkbox on the far left of the " +"screen, above the listed courses, to the left of the :guilabel:`Title` " +"column. When that checkbox is clicked, all the course contents are selected " +"at once." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst:324 +msgid "" +"With all the course content selected, double click any of the boxes in the " +":guilabel:`Is Published` column. This reveals a pop-up window, asking for " +"confirmation that all selected records are intended to be published. Click " +":guilabel:`OK` to automatically publish all course content." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/help_center.rst-1 +msgid "View of a course contents being published in Odoo Helpdesk back-end." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:3 +msgid "Customer ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:5 +msgid "" +"Asking customers to rate the support they received from a *Helpdesk* team " +"provides an opportunity to gauge team performance and track customer " +"satisfaction. Ratings can be published to the portal, providing customers " +"with a general overview of the team's performance." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:10 +msgid "Enable customer ratings on a Helpdesk team" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:12 +msgid "" +"To enable *customer ratings* on a helpdesk team by going to " +":menuselection:`Helpdesk --> Configuration --> Teams`. Select a team from " +"the list and navigate to the settings page. Scroll to the " +":guilabel:`Performance` section, and check the box for :guilabel:`Customer " +"Ratings`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"Overview of the settings page of a helpdesk team emphasizing the rating on ticket feature\n" +"in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:22 +msgid "Set a ratings request email template on a stage" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:24 +msgid "" +"To automatically request ratings from customers once their tickets have " +"closed, an email template should be added to the appropriate stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:27 +msgid "" +"Once the :guilabel:`Customer Ratings` setting has been enabled on the team's" +" settings page, (see above) click the :guilabel:`Set an Email Template on " +"Stages` link. Select a stage from the list, or click :guilabel:`New` to " +"create a new stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:32 +msgid "" +"Customers should only be asked to rate tickets once an issue has been " +"resolved and their ticket is closed. Therefore, a *ratings request* email " +"should only be added to a stage that is **folded** in the kanban, as tickets" +" in a *folded stage* are considered closed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:36 +msgid "" +"On the stage's settings page, select `Helpdesk: Ticket Rating Request` in " +"the :guilabel:`Email Template` field. This template has been pre-configured " +"with ratings customers can use to provide feedback. To view the template, " +"click the arrow button to the right of the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:40 +msgid "" +"Once the template has been added to the stage, it will automatically send a " +"message when a ticket is moved to that stage. Customers will be asked to " +"rate the support they received with colored icons." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:43 +msgid "*Green smiling face* - Satisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:44 +msgid "*Yellow neutral face* - Okay" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:45 +msgid "*Red frowning face* - Dissatisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "" +"View of a standard helpdesk customer review email template for Odoo " +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:51 +msgid "" +"After selecting a rating, customers are taken to a webpage where they can " +"provide specific written feedback to support their rating. Once a rating is " +"submitted, it is added to the chatter on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:56 +msgid "" +"Customer ratings can also be viewed through the :guilabel:`Customer Ratings`" +" report. To view this report, go to :menuselection:`Helpdesk --> Reporting " +"--> Customer Ratings`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:63 +msgid "Publish ratings on the customer portal" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:65 +msgid "" +"After enabling the :guilabel:`Customer Ratings` setting, an option to " +"publish ratings on the team's website appears. Enabling this setting " +"provides portal users with an overview of the ratings the team has received " +"over the last thirty days. Specific written feedback will not be included; " +"only statistics of the team's performance will be visible." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:71 +msgid "" +"In order to display ratings on the customer portal, a team has to have their" +" visibility setting set to :guilabel:`Invited portal users and all internal " +"users`. This setting is found on the team's settings page under " +":guilabel:`Visibility`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:75 +msgid "" +"Next, to publish the ratings, go to :menuselection:`Helpdesk --> " +"Configuration --> Teams` and select a team. Scroll to " +":guilabel:`Performance` and enable :guilabel:`Publish this team's ratings on" +" your website`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:79 +msgid "" +"To view the ratings for a team, a customer will log into the portal and " +"navigate to one of their tickets. After clicking on the team name in the " +":guilabel:`Managed By` field, they will be directed to a page with the " +"team's ratings over the past thirty days." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst-1 +msgid "View of the ratings performance overview from the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:88 +msgid "Manually hide individual ratings" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:90 +msgid "" +"Individual ratings can be manually hidden from the portal. This allows for " +"specific ratings to be kept out of the performance metrics that are shown to" +" customers." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:93 +msgid "" +"To make a rating visible only to internal users, navigate to the page for a " +"rating. This can be done in one of the following ways:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:96 +msgid "" +"Go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings` and click" +" on one of the kanban cards for an individual rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:98 +msgid "" +"Navigate to :menuselection:`Helpdesk --> Tickets --> All Tickets` and remove" +" the :guilabel:`Open` filter from the search bar. Then filter by " +":guilabel:`Satisfied`, :guilabel:`Okay` and/or :guilabel:`Dissatisfied`. " +"Select a ticket from the results. Click the :guilabel:`Rating` smart button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:103 +msgid "" +"Once on the rating details page, check the :guilabel:`Visible Internally " +"Only` box." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:110 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:291 +msgid ":doc:`/applications/services/helpdesk/advanced/close_tickets`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/ratings.rst:111 +msgid ":doc:`/applications/services/helpdesk/overview/reports`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:3 +msgid "Start receiving tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:5 +msgid "" +"Odoo *Helpdesk* offers multiple channels where customers can reach out for " +"assistance, such as email, live chat, and through a website's submission " +"form. The variety of these contact options provides customers with multiple " +"opportunities to receive support quickly, while also giving the support team" +" the ability to manage multi-channel support tickets from one central " +"location." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:11 +msgid "Enable channel options to submit tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:13 +msgid "" +"Go to :menuselection:`Helpdesk --> Configuration --> Teams` and choose an " +"existing team, or click :guilabel:`New` to :doc:`create a new team " +"<getting_started>`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:16 +msgid "" +"On the team's settings page, scroll down to :guilabel:`Channels`. Select one" +" or more channel(s) to enable by checking the respective box(es)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:19 +msgid ":guilabel:`Email Alias`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:20 +msgid ":guilabel:`Website Form`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:21 +msgid ":guilabel:`Live Chat`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:24 +msgid "Email Alias" +msgstr "นามแฝงอีเมล" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:26 +msgid "" +"The *Email Alias* setting automatically creates tickets from messages sent " +"to that team's specified email alias." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:29 +msgid "" +"To alter a *Helpdesk* team's email alias, navigate to the :guilabel:`Teams` " +"settings page. Find :guilabel:`Email Alias`, under the :guilabel:`Channels` " +"heading, and then type in the desired team alias in the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:33 +msgid "" +"When a new *Helpdesk* team is created, an :guilabel:`Email Alias` is " +"created, as well. This alias can be changed in the :guilabel:`Alias` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:37 +msgid "" +"If the database does not have a custom domain already configured, click " +":guilabel:`Configure a custom domain` to be redirected to the " +":guilabel:`Settings` page. From there, enable :guilabel:`Custom Email " +"Servers`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the email alias feature in Odoo\n" +"Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:46 +msgid "" +"When an email is received, the subject line from the email becomes the title" +" of a new *Helpdesk* ticket. The body of the email is also added to the " +"ticket under the :guilabel:`Description` tab and in the ticket's " +":guilabel:`Chatter` section." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:51 +msgid "" +"The configuration steps outlined above are for **Odoo Online** and " +"**Odoo.sh** databases. For **On-premise** databases, additional " +"configuration for custom email servers and email aliases may be required." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:56 +msgid "Website Form" +msgstr "แบบฟอร์มเว็บไซต์" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:58 +msgid "" +"Enabling the *Website Form* setting adds a new page to the website with a " +"customizable form. A new ticket is created once the required form fields are" +" filled out and submitted." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:61 +msgid "" +"To activate the website form, navigate to a team's settings page under " +":menuselection:`Configuration --> Teams`. Find the :guilabel:`Website Form` " +"feature under the :guilabel:`Channels` section, and check the box." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:65 +msgid "" +"After the feature is activated, click the :guilabel:`Go to Website` smart " +"button at the top of the that :guilabel:`Teams` settings page to view and " +"edit the new website form, which is created automatically by Odoo." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:70 +msgid "" +"After enabling the website form, the *Teams* settings page may need to be " +"refreshed before the *Go to Website* smart button appears." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:73 +msgid "" +"As well, if a *Help Center* is published, the smart button will navigate " +"there first. Simply click the :guilabel:`Contact Us` button at the bottom of" +" the forum to navigate to the ticket submission form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the settings page of a helpdesk team emphasizing the Go to Website button in\n" +"Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:83 +msgid "Customize the website ticket form" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:85 +msgid "" +"To customize the default ticket submission form, click the :guilabel:`Edit` " +"button in the upper right corner of the page. Then click on one of the " +"fields in the form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:88 +msgid "" +"Add, remove, or update fields as necessary to alter the information " +"submitted by customers. Fields can be made marked as :guilabel:`Required`, " +"by toggling the switch from gray to blue in the website builder's editor " +"window, located under the :guilabel:`Field` section. As well, other " +"pertinent field information can be edited here, such as:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:93 +msgid "" +":guilabel:`Type`: which matches an Odoo model value to the field (e.g. " +"`Customer Name`)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:94 +msgid "" +":guilabel:`Input Type`: to determine what type of input the field should be," +" like `Text`, `Email`, `Telephone` or `URL`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:96 +msgid "" +":guilabel:`Label`: to give the form field a label (e.g. `Full Name`, `Email " +"Address`, etc.). Also control the label position on the form by using the " +"nested :guilabel:`Position` options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:98 +msgid "" +":guilabel:`Description`: which, optionally, adds an editable line under the " +"input box to provide additional contextual information related to the field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:100 +msgid ":guilabel:`Placeholder`: to add a sample input value." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:101 +msgid "" +":guilabel:`Default value`: to add common use case values that most customers" +" would find valuable" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:102 +msgid "" +":guilabel:`Required`: which sets the field as mandatory before the form can " +"be submitted." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:103 +msgid "" +":guilabel:`Visibility`: to allow for absolute or conditional visibility of " +"the field. Nested options, such as device visibility, appear when certain " +"options are selected." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:107 +msgid "" +"Text blocks can be added in the farthest 1/3 column of the ticket form page," +" next to the ticket form. This is an ideal place to include team information" +" such as additional contact details, hours, or common helpful articles that " +"link to the :guilabel:`Forum`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of the unpublished website form to submit a ticket for Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:115 +msgid "" +"Once the form has been optimized and is ready for public use, " +":guilabel:`Save` the changes, and then publish the form by clicking on the " +":guilabel:`Unpublished` button." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:119 +msgid "Live Chat" +msgstr "ไลฟ์แชท" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:121 +msgid "" +"The *Live Chat* feature allows website visitors to connect directly with a " +"support agent or chatbot. During these conversations, *Helpdesk* tickets can" +" be instantly created by using the :doc:`response command " +"</applications/websites/livechat/responses>` `/helpdesk`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:125 +msgid "" +"To enable *Live Chat*, navigate to the :menuselection:`Configuration --> " +"Teams` list view, select a team, and on the :guilabel:`Teams` settings page," +" click the check box next to :guilabel:`Live Chat`, under the " +":guilabel:`Channels` heading." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:130 +msgid "" +"If this is the first time *Live Chat* has been enabled on the database, the " +"page may need to be saved manually and refreshed before any further steps " +"can be taken." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:133 +msgid "" +"With the :guilabel:`Live Chat` setting engaged, click on :guilabel:`View " +"Channels`. Then, on the :guilabel:`Website Live Chat Channels` dashboard, " +"select the kanban card for the channel that was created for the *Helpdesk* " +"team, or create a :guilabel:`New` one if necessary. When a kanban card is " +"selected, additional options await on the channel's form." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:139 +msgid "Customize the live chat channel" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:141 +msgid "" +"When an individual channel is clicked on the :guilabel:`Website Live Chat " +"Channels` dashboard, Odoo directs the page to the channel form. From there, " +"the :guilabel:`Channel Name` can be edited, however Odoo names this to match" +" the *Helpdesk* team's kanban pipeline, by default." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:146 +msgid "" +"If a *Helpdesk* team is named `Customer Care`, a *Live Chat* channel will be" +" created with the same name." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0 +msgid "View of the kanban cards for the available Live Chat channels." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:153 +msgid "On the channel form, navigate through the tabs to complete the setup." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:156 +msgid "Add operators" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:158 +msgid "" +"*Operators* are the users who will act as agents and respond to live chat " +"requests from customers. The user who originally created the live chat " +"channel will be added by default." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:161 +msgid "" +"To add additional users, navigate and click on the live chat channel from " +"the :guilabel:`Website Live Chat Channels` dashboard, and on the " +":guilabel:`Operators` tab, click :guilabel:`ADD`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:164 +msgid "" +"Then, click the check box next to the users to be added, and click " +":guilabel:`SELECT`. :guilabel:`New` operators can be created and added to " +"the list, as well, by filling out the :guilabel:`Create Operators` form and " +"then clicking :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for " +"multiplerecord creations)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:169 +msgid "" +"As well, current operators can be edited or removed by clicking on their " +"respective boxes in the :guilabel:`Operators` tab, and then adjusting their " +"form values, or by using one of the form buttons located at the bottom of " +"the form, such as :guilabel:`REMOVE`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:174 +msgid "" +"Users can add themselves as an operator by clicking the :guilabel:`Join` " +"button on a *Live Chat* channel." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:178 +msgid "Modify channel options" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:180 +msgid "" +"The :guilabel:`Options` tab contains the visual and text settings for the " +"live chat window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:182 +msgid "" +"Change the text in the :guilabel:`Text of the Button` field to update the " +"greeting displayed in the text bubble when the live chat button appears on " +"the website." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:185 +msgid "" +"Edit the :guilabel:`Welcome Message` to change the message a visitor sees " +"when they open the chat window. This message will appear as though it is " +"sent by a live chat operator, and should be an invitation to continue the " +"conversation." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:189 +msgid "" +"Edit the :guilabel:`Chat Input Placeholder` to change the text that appears " +"in the box where visitors will type their replies." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:192 +msgid "" +"Change the :guilabel:`Livechat Button Color` and the :guilabel:`Channel " +"Header Color` by clicking a color bubble to open the color selection window." +" Click the refresh icon to the right of the color bubbles to reset the " +"colors to the default selection." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:197 +msgid "" +"Color selection, for the button or header, can be made manually, or through " +"RGB, HSL or HEX code selection. Different options will be available, " +"depending on your operating system." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:201 +msgid "Create channel rules" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:203 +msgid "" +"The :guilabel:`Channel Rules` tab determines when the live chat window opens" +" on the website by logic of when a :guilabel:`URL Regex` action is triggered" +" (e.g., a page visit)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:206 +msgid "" +"Edit existing rules, or create a new one by clicking :guilabel:`Add a line`," +" and fill out the pop-up form details based on how the rule should apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:209 +msgid "" +"If a :guilabel:`Chatbot` will be included on this channel, select it from " +"the dropdown. If the chatbot will only be active when no operators are " +"available, check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:214 +msgid "" +"If a chatbot is added to a live chat channel, then 3 new smart buttons will " +"appear on the channel settings form: :guilabel:`Chatbots`, " +":guilabel:`Sessions`, and :guilabel:`% Happy`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:217 +msgid "" +"The :guilabel:`Chatbots` smart button is where the chatbot can be programmed" +" with a :guilabel:`Script`. Each line in the :guilabel:`Script` contains a " +":guilabel:`Message`, :guilabel:`Step Type`, :guilabel:`Answers`, and " +"conditional :guilabel:`Only If` logic that applies when certain pre-filled " +"answers are chosen. To create more steps in the :guilabel:`Script`, click " +":guilabel:`Add a line` and fill out the script steps form according to the " +"desired logic." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:223 +msgid "" +":guilabel:`Sessions` is where live chat sessions are recorded in order of " +"descending :guilabel:`Session Date`, by default. Each record includes the " +":guilabel:`Attendees` involved in the live chat session, the :guilabel:`# " +"Messages`, as well as any :guilabel:`Rating` that was received when the " +"session ended." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:227 +msgid "" +"The :guilabel:`% Happy` smart button includes a log of ratings that were " +"left by live chat attendees, and are labeled by date, time, and the support " +"agent who was responsible for the live chat session." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:231 +msgid "" +"Add the URL for the pages this channel will be applied to in the " +":guilabel:`URL Regex` field. If this channel will only be available to users" +" in specific countries, add them to the :guilabel:`Country` field. If this " +"field is left blank, the channel will be available to all site visitors." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:241 +msgid "Use the live chat widget" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:243 +msgid "" +"The :guilabel:`Widget` tab on the live chat channel form offers an " +"embeddable website widget, or a shortcode for instant customer/supplier " +"access to a live chat window." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:246 +msgid "" +"The live chat :guilabel:`Widget` can be applied to websites created through " +"Odoo by navigating to the :menuselection:`Website --> Configuration --> " +"Settings`. Then scroll to the :guilabel:`Live Chat` section, and select the " +"channel to add to the site. Click :guilabel:`Save` to apply." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:250 +msgid "" +"To add the widget to a website created on a third-party platform, click " +":guilabel:`COPY` and paste the code into the `<head>` tag on the site." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:253 +msgid "" +"Likewise, to send a live chat session to a customer or supplier, click the " +"second :guilabel:`COPY` button which contains a link to join directly." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:257 +msgid "Create a support ticket from a live chat session" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:259 +msgid "" +"Once live chat is enabled, operators will be able to communicate with site " +"visitors in real time." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:261 +msgid "" +"During the conversation, an operator can use the shortcut :doc:`command " +"</applications/websites/livechat/responses>` `/helpdesk` to create a ticket " +"without leaving the chat window. The transcript from the conversation will " +"be added to the new ticket, under the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:267 +msgid "Prioritizing tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:269 +msgid "" +"All tickets include a :guilabel:`Priority` field. The highest priority " +"tickets will appear at the top of the kanban and list views." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst-1 +msgid "" +"View of a team's kanban view and the prioritized tasks in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:276 +msgid "The priority levels are represented by stars:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:278 +msgid "0 stars = *Low Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:279 +msgid "1 star = *Medium Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:280 +msgid "2 stars = *High Priority*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:281 +msgid "3 stars = *Urgent*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:283 +msgid "" +"Tickets will be set to low priority (0 stars) by default. To change the " +"priority level, select the appropriate number of stars on the kanban card, " +"or on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:287 +msgid "" +"As priority levels can be used as criteria for assigning :doc:`SLAs <sla>`, " +"changing the priority level of a ticket can alter the :abbr:`SLA (Service " +"Level Agreement)` deadline." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:292 +msgid ":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:293 +msgid ":doc:`/applications/websites/livechat`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:3 +msgid "Reporting" +msgstr "การรายงาน" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:5 +msgid "" +"Odoo *Helpdesk* includes several reports that provide the opportunity to " +"track trends for customer support tickets, identify areas for improvement, " +"manage employee workloads, and confirm when customer expectations are met." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:10 +msgid "Available reports" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:12 +msgid "" +"Details about the reports available in Odoo *Helpdesk* can be found below. " +"To view the different reports, go to :menuselection:`Helpdesk --> " +"Reporting`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:16 +msgid "Ticket Analysis" +msgstr "การวิเคราะห์ทิกเก็ต" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:18 +msgid "" +"The *Ticket Analysis* report (:menuselection:`Helpdesk --> Reporting --> " +"Ticket Analysis`) provides an overview of every customer support ticket in " +"the database. This includes the number of tickets assigned among teams and " +"individual users." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:22 +msgid "" +"This report is useful in identifying where teams are spending the most time," +" and helps determine if there is an uneven workload distribution among the " +"support staff. The default report counts the number of tickets per team and " +"groups them by stage." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of Ticket Analysis report default view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:30 +msgid "" +"Alternative measures can be selected to track where the most time is spent " +"at different points in the workflow. To change the measures used for the " +"report that is currently displayed, or to add more, click the " +":guilabel:`Measures` button, and select one or more options from the drop-" +"down menu:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:35 +msgid "" +":guilabel:`Average Hours to Respond`: average number of working hours " +"between a message sent from the customer and the response from the support " +"team. *This is does not include messages sent when the ticket was in a " +"folded stage*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:38 +msgid "" +":guilabel:`Hours Open`: number of hours between the date the ticket was " +"created and the closed date. If there is no closed date on the ticket, the " +"current date is used. **This measure is not specific to working hours**" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:41 +msgid "" +":guilabel:`Hours Spent`: number of *Timesheet* hours logged on a ticket. " +"*This measure is only available if Timesheets are enabled on a team, and the" +" current user has the access rights to view them*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:44 +msgid "" +":guilabel:`Hours to Assign`: number of working hours between the date on " +"which the ticket was created and when it was assigned to a team member" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:46 +msgid "" +":guilabel:`Hours to Close`: number of working hours between the date on " +"which the ticket was created and the date it was closed" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:48 +msgid "" +":guilabel:`Hours to First Response`: number of working hours between the " +"date on which the ticket was received and the date one which the first " +"message was sent. *This does not include email sent automatically when a " +"ticket reaches a stage*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:51 +msgid "" +":guilabel:`Hours to SLA Deadline`: number of working hours remaining to " +"reach the last :abbr:`SLA (Service Level Agreement)` deadline on a ticket" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:53 +msgid "" +":guilabel:`Rating /5`: number valued assigned to the rating received from a " +"customer (Dissatisfied = 1, Okay/Neutral = 3, Satisfied = 5)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:55 +#: ../../content/applications/services/helpdesk/overview/reports.rst:99 +msgid ":guilabel:`Count`: number of tickets in total" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:58 +msgid "" +"*Working hours* are calculated based on the default working calendar. To " +"view or change the working calendar, go to the :menuselection:`Settings` " +"application and select :menuselection:`Employees --> Company Working Hours`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:63 +msgid "SLA Status Analysis" +msgstr "การวิเคราะห์สถานะ SLA" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:65 +msgid "" +"The *SLA Status Analysis* report (:menuselection:`Helpdesk --> Reporting -->" +" SLA Status Analysis`) tracks how quickly an SLA (Service Level Agreement) " +"is fulfilled, as well as the success rate of individual policies." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:69 +msgid "" +"By default, this report is filtered to show the number of :abbr:`SLAs " +"(Service Level Agreements)` failed, as well as the failure rate over the " +"last 30 days, grouped by team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of Group by options of Ticket Analysis report." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:76 +msgid "" +"To change the measures used for the report that is currently displayed, or " +"to add more, click the :guilabel:`Measures` button, and select one or more " +"options from the drop-down menu:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:79 +msgid "" +":guilabel:`% of Failed SLA`: percentage of tickets that have failed at least" +" one :abbr:`SLA (Service Level Agreement)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:81 +msgid "" +":guilabel:`% of SLA in Progress`: percentage of tickets that have at least " +"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not " +"failed any :abbr:`SLAs (Service Level Agreements)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:84 +msgid "" +":guilabel:`% of Successful SLA`: percentage of tickets where all :abbr:`SLAs" +" (Service Level Agreements)` have been successful" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:86 +msgid "" +":guilabel:`Number of SLA Failed`: number of tickets that have failed at " +"least one :abbr:`SLA (Service Level Agreement)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:88 +msgid "" +":guilabel:`Number of SLA Successful`: number of tickets where all " +":abbr:`SLAs (Service Level Agreements)` have been successful" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:90 +msgid "" +":guilabel:`Number of SLA in Progress`: number of tickets that have at least " +"one :abbr:`SLA (Service Level Agreement)` still in progress, and have not " +"failed any :abbr:`SLAs (Service Level Agreements)`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:93 +msgid "" +":guilabel:`Working Hours to Assign`: number of working hours between the " +"date on which the ticket was created and when it was assigned to a team " +"member" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:95 +msgid "" +":guilabel:`Working Hours to Close`: number of working hours between the date" +" on which the ticket was created and the date it was closed" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:97 +msgid "" +":guilabel:`Working Hours to Reach SLA`: number of working hours between the " +"date on which the ticket was created and the date the :abbr:`SLA (Service " +"Level Agreement)` was satisfied" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:102 +msgid "" +"To see the number of tickets that were able to achieve the stated :abbr:`SLA" +" (Service Level Agreement)` objectives, and track the amount of time it took" +" to achieve those objectives, click :menuselection:`Measures --> Number of " +"SLA Successful` and :menuselection:`Measures --> Working Hours to Reach " +"SLA`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:107 +msgid "" +"To sort these results by the team members assigned to the tickets, select " +":menuselection:`Total --> Assigned to`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:111 +msgid "" +":doc:`Service Level Agreements (SLA) " +"</applications/services/helpdesk/overview/sla>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:114 +msgid "Customer Ratings" +msgstr "การให้คะแนนลูกค้า" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:116 +msgid "" +"The *Customer Ratings* report (:menuselection:`Helpdesk --> Reporting -- " +"Customer Ratings`) displays an overview of the ratings received on " +"individual support tickets, as well as any additional comments submitted " +"with the rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the kanban display in the Customer Ratings report." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:124 +msgid "" +"Click on an individual rating to see additional details about the rating " +"submitted by the customer, including a link to the original ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the details of an individual customer rating." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:132 +msgid "" +"On the rating's details page, select the :guilabel:`Visible Internally Only`" +" option to hide the rating from the customer portal." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:135 +msgid "" +"The *Customer Ratings* report is displayed in a kanban view by default, but " +"can also be displayed in graph, list, or pivot view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:139 +msgid ":doc:`Ratings </applications/services/helpdesk/overview/ratings>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:142 +msgid "View and filter options" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:144 +msgid "" +"On any Odoo report, the view and filter options vary, depending on what data" +" is being analyzed, measured, and grouped. See below for additional " +"information on the available views for the *Helpdesk* reports." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:149 +msgid "" +"Only one measure may be selected at a time for graphs, but pivot tables can " +"include multiple measures." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:153 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:155 +msgid "" +"The *pivot* view presents data in an interactive manner. All three " +"*Helpdesk* reports are available in pivot view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:158 +msgid "" +"The pivot view can be accessed on any report by selecting the " +":guilabel:`grid icon` at the top right of the screen." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the SLA status analysis report in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:165 +msgid "" +"To add a group to a row or column to the pivot view, click the :guilabel:`➕ " +"(plus sign)` next to :guilabel:`Total`, and then select one of the groups. " +"To remove one, click the :guilabel:`➖ (minus sign)` and de-select the " +"appropriate option." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:170 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:172 +msgid "" +"The *graph* view presents data in either a *bar*, *line*, or *pie* chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:174 +msgid "" +"Switch to the graph view by selecting the :guilabel:`line chart icon` at the" +" top right of the screen. To switch between the different charts, select the" +" *related icon* at the top left of the chart, while in graph view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:180 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the SLA status analysis report in bar view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:186 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the Customer Ratings report in line view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:192 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:0 +msgid "View of the Ticket analysis report in pie chart view." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:199 +msgid "" +"Both the *bar chart* and *line chart* can utilize the *stacked* view option." +" This presents two (or more) groups of data on top of each other, instead of" +" next to each other, making it easier to compare data." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:204 +msgid "Save and share a favorite search" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:206 +msgid "" +"The *Favorites* feature found on *Helpdesk* reports allows users to save " +"their most commonly used filters without having to reconstruct them every " +"time they are needed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:209 +msgid "" +"To create and save new *Favorites* on a report, follow the steps below:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:211 +msgid "" +"Set the necessary parameters using the :guilabel:`Filters`, :guilabel:`Group" +" By` and :guilabel:`Measures` options." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:213 +msgid "Click :menuselection:`Favorites --> Save current search`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:214 +msgid "Rename the search." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:215 +msgid "" +"Select :guilabel:`Use by default` to have these filter settings " +"automatically displayed when the report is opened. Otherwise, leave it " +"blank." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:217 +msgid "" +"Select :guilabel:`Share with all users` to make this filter available to all" +" other database users. If this box is not checked, it will only be available" +" to the user who creates it." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:219 +msgid "Click :guilabel:`Save` to preserve the configuration for future use." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst-1 +msgid "View of the save favorites option in Odoo Helpdesk." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:226 +msgid "" +":doc:`Start receiving tickets " +"</applications/services/helpdesk/overview/receiving_tickets>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/reports.rst:227 +msgid ":doc:`Odoo reporting </applications/general/reporting>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:3 +msgid "Service Level Agreements (SLA)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:5 +msgid "" +"A Service Level Agreement (SLA) defines the level of service a customer can " +"expect from a supplier. SLAs provide a timeline that tells customers when " +"they can expect results, and keeps the support team on target." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:10 +msgid "Create a new SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:12 +msgid "" +"To create a new :abbr:`SLA (Service Level Agreement)` Policy, navigate to " +"the team's page under :menuselection:`Helpdesk --> Configuration --> Teams`." +" Select a team, scroll to the :guilabel:`Performance` section, and then " +"check the selection box next to :guilabel:`SLA Policies` to enable it for " +"that specific team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a team page in Helpdesk focusing on the SLA Policies setting" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:22 +msgid "" +"The value indicated next to the :guilabel:`Working Hours` field is used to " +"determine the deadline for :abbr:`SLA (Service Level Agreement)` policies. " +"By default, this is determined by the value set in the :guilabel:`Company " +"Working Hours` field under :menuselection:`Settings app --> Employees --> " +"Work Organization`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:27 +msgid "" +"To create a new policy, click the smart button on the team`s settings page " +"or go to :menuselection:`Helpdesk --> Configuration --> SLA Policies`, and " +"click :guilabel:`New`. Start by entering a :guilabel:`Title` and a " +":guilabel:`Description` for the new policy, and proceed to fill out the form" +" using the steps below." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:33 +msgid "Define the criteria for an SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:35 +msgid "" +"The :guilabel:`Criteria` section is used to identify what tickets this " +"policy will be applied to. Fill out the following fields to adjust the " +"selection criteria:" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:38 +msgid "" +":guilabel:`Team`: a policy can only be applied to one team. *This field is " +"required.*" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:39 +msgid "" +":guilabel:`Priority`: the priority level for a ticket is identified by " +"selecting the number of stars representing the priority level on the kanban " +"card or the ticket itself. The :abbr:`SLA (Service Level Agreement)` will " +"only be applied once the priority level has been updated on the ticket to " +"match the :abbr:`SLA (Service Level Agreement)` criteria. If no selection is" +" made in this field, this policy will only apply to tickets marked as `Low " +"Priority` (zero stars)." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:44 +msgid "" +":guilabel:`Types`: ticket types can be helpful when indicating when a ticket" +" is a customer question, that can be solved with a quick response, or an " +"issue, that may require additional investigation. Multiple ticket types can " +"be selected for this field. If no selection is made, this policy will apply " +"to all ticket types." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:48 +msgid "" +":guilabel:`Tags`: tags are applied to briefly indicate what the ticket is " +"about. Multiple tags can be applied to a single ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:50 +msgid "" +":guilabel:`Customers`: individual contacts or companies may be selected in " +"this field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:51 +msgid "" +":guilabel:`Sales Order Items`: this field is available only if a team has " +"the *Timesheets* app enabled. This allows the ticket to tie directly to a " +"specific line on a sales order, which must be indicated on the ticket in the" +" :guilabel:`Sales Order Item` field." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:56 +msgid "" +"Unless otherwise indicated, multiple selections can be made for each field. " +"(i.e. multiple :guilabel:`Tags` can be included in a policy, but only one " +":guilabel:`Priority` level)" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a blank SLA policy record" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:64 +msgid "Establish a target for an SLA policy" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:66 +msgid "" +"The :guilabel:`Target` is the stage a ticket needs to reach, and the time " +"alloted to reach that stage, in order to satisfy the :abbr:`SLA (Service " +"Level Agreement)` policy. Any stage assigned to a team may be selected for " +"the :guilabel:`Reach Stage` field. Time spent in stages selected in " +":guilabel:`Excluding Stages` will not be included in the calculation of the " +":abbr:`SLA (Service Level Agreement)` deadline." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:73 +msgid "" +"An :abbr:`SLA (Service Level Agreement)` titled `8 Hours to Close` tracks " +"the working time before a ticket is completed, and would have `Solved` as " +"the :guilabel:`Reach Stage`. However, if the :abbr:`SLA (Service Level " +"Agreement)` was titled `2 Days to Start`, it tracks the working time before " +"work on a ticket has begun, and would have `In Progress` as the " +":guilabel:`Reach Stage`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:79 +msgid "Meeting SLA deadlines" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:81 +msgid "" +"Once it is determined that a ticket fits the criteria of an :abbr:`SLA " +"(Service Level Agreement)` policy, a deadline is calculated. The deadline is" +" based on the creation date of the ticket, and the targeted working hours. " +"The deadline is then added to the ticket, as well as a white tag indicating " +"the name of the :abbr:`SLA (Service Level Agreement)` applied." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "" +"View of a ticket's form emphasizing an open SLA deadline on a ticket in Odoo" +" Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:91 +msgid "" +"If a ticket fits the criteria for more than one :abbr:`SLA (Service Level " +"Agreement)`, the earliest occurring deadline will be displayed on the " +"ticket. Once that deadline has passed, the next deadline will be displayed." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:95 +msgid "" +"Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the" +" :abbr:`SLA (Service Level Agreement)` tag turns green, and the " +":guilabel:`Deadline` field disappears from view on the ticket." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:103 +msgid "" +"If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket " +"has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level " +"Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level " +"Agreement)` has failed, the red tag will stay on the ticket, even after the " +"ticket is moved to the :guilabel:`Reach Stage`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "" +"View of a ticket's form with a failing and passing SLA in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:113 +msgid "Analyzing SLA performance" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:115 +msgid "" +"The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA " +"(Service Level Agreement)` is fulfilled, as well as the success rate of " +"individual policies. Navigate to the report and corresponding pivot table by" +" going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:121 +msgid "Using the Pivot view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:123 +msgid "" +"By default, the report is displayed in a :guilabel:`Pivot` view, and is " +"filtered to show the number of SLAs failed and the failure rate over the " +"last 30 days, grouped by team." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of the SLA status analysis report in Odoo Helpdesk" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:130 +msgid "" +"To add the number of SLAs passed or in progress, click the " +":guilabel:`Measures` button to reveal a drop-down menu of reporting " +"criteria, and choose from the options available based on the measurements " +"preferred. Whenever a measurement is picked, a check mark will appear in the" +" drop-down menu to indicate that that measurement is included, and a " +"corresponding new column will emerge in the pivot table to show the relevant" +" calculations." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:136 +msgid "" +"To add a group to a row or column, click the plus :guilabel:` + ` button " +"next to :guilabel:`Total`, and then select one of the groups. To remove one," +" click the minus :guilabel:` - ` button and deselect." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:141 +msgid "Using the Graph view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:143 +msgid "" +"The :guilabel:`Status Analysis` report can also be viewed as a " +":guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between " +"these views by selecting the appropriate icon at the top of the chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:149 +msgid "Bar Chart" +msgstr "แผนภูมิแท่ง" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in bar view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:155 +msgid "Line Chart" +msgstr "แผนภูมิเส้น" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in line view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:161 +msgid "Pie Chart" +msgstr "แผนภูมิวงกลม" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:0 +msgid "View of the SLA status analysis report in pie chart view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:168 +msgid "" +"Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed " +":guilabel:`Stacked`. This presents two or more groups to appear on top of " +"each other instead of next to each other, making it easier to compare data." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:173 +msgid "Using the Cohort view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:175 +msgid "" +"The :guilabel:`Cohort` view is used to track the changes in data over a " +"period of time. To display the :guilabel:`Status Analysis` report in a " +":guilabel:`Cohort` view, click the icon in the top right corner above the " +"chart." +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst-1 +msgid "View of the SLA status analysis report in cohort view" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:184 +msgid ":ref:`Reporting views <reporting/views>`" +msgstr "" + +#: ../../content/applications/services/helpdesk/overview/sla.rst:185 +msgid "" +":doc:`Allow customers to close their tickets " +"</applications/services/helpdesk/advanced/close_tickets>`" +msgstr "" + +#: ../../content/applications/services/project.rst:8 +msgid "Project" +msgstr "โปรเจ็กต์" + +#: ../../content/applications/services/project.rst:10 +msgid "" +"Odoo Project is a tool to manage your ongoing projects. Schedule tasks, " +"assign activities to coworkers, and keep track of each project's " +"profitability." +msgstr "" + +#: ../../content/applications/services/project.rst:14 +#: ../../content/applications/services/timesheets.rst:11 +msgid "" +"`Odoo Tutorials: Project and Timesheets " +"<https://www.odoo.com/slides/project-and-timesheets-21>`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:3 +msgid "Project management" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:5 +msgid "" +"Odoo Project uses the **Kanban** project management system. This means all " +"projects are broken down into tasks, which are categorized on a whiteboard " +"according to what production phase they are in." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:8 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:10 +msgid "" +"The word **Kanban** comes from Japanese and refers to the \"visual board\" " +"management method." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:13 +msgid "" +"`Odoo Tutorials: Kanban Project Management " +"<https://www.odoo.com/slides/slide/kanban-project-management-1664>`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:19 +msgid "" +"Open the **Project** app and click :guilabel:`Create` to start a new " +"project. Enter a :guilabel:`Name` for your project and click " +":guilabel:`Create Project`." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:22 +msgid "" +"You can customize your existing **projects** from the dashboard by clicking " +"the drop-down toggle button (:guilabel:`⋮`) on your project's **card**." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst-1 +msgid "Project card" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:29 +msgid "This enables a new menu divided into four parts:" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:31 +msgid "" +":guilabel:`View`: see an overview of your project's components, such as its " +":guilabel:`Tasks`, :guilabel:`Milestones` and :guilabel:`Project Updates`. " +"Depending on which apps you have activated, more options may be available, " +"such as :guilabel:`Documents`. All uploaded files can be found under this " +"menu, as well as in the **Documents** app, under :guilabel:`Projects`;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:35 +msgid "" +":guilabel:`Reporting`: analyze your project's progress and profitability " +"through graphics and statistics;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:37 +msgid "" +"**Color**: make a line of color appear on the left side of the card so that " +"your project is more recognizable;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:39 +msgid ":guilabel:`Settings`: you can change the following:" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:41 +msgid "the :guilabel:`Name` of the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:42 +msgid "the :guilabel:`Name of the tasks` found under that project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:43 +msgid "the :guilabel:`Customer` for whom the project is intended;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:44 +msgid "the :guilabel:`Tags` used for filtering;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:45 +msgid "the :guilabel:`Company` responsible for the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:46 +msgid "the employee designated as :guilabel:`Project Manager`;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:47 +msgid "the :guilabel:`Planned Date` of the project;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:48 +msgid "the total :guilabel:`Allocated Hours` for that project." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:50 +msgid "" +"Additionally, you can mark the project as :guilabel:`Favorite`, allowing you" +" to find it using the :guilabel:`My Favorites` filter on the Kanban view;" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst-1 +msgid "Project settings" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:58 +msgid "" +"`Odoo Tutorials: Customize projects " +"<https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:61 +msgid "" +"Further settings are available under the :guilabel:`Settings` tab. Most of " +"them are *only* available depending on the activated apps." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:65 +msgid "Scheduling activities" +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:67 +msgid "" +"You can schedule **activities** (ex. :guilabel:`Call`, :guilabel:`Meeting`, " +"etc.) per project by clicking on the **clock** icon on a project. Doing so " +"opens a list with already scheduled activities and allows planning **new** " +"activities by clicking :guilabel:`+ Schedule an activity`. On the pop-up " +"window, select the :guilabel:`Activity Type`, enter a :guilabel:`Summary` " +"for that activity, a :guilabel:`Due Date`, and assign it to an employee. " +"According to the :guilabel:`Activity Type`, you may have **additional " +"options** available." +msgstr "" + +#: ../../content/applications/services/project/project_management.rst:75 +msgid "" +"If an activity is **already** scheduled, the icon may change to a **phone**," +" **group of people**, or other." +msgstr "" + +#: ../../content/applications/services/project/tasks.rst:5 +msgid "Tasks" +msgstr "งาน" + +#: ../../content/applications/services/project/tasks/email_alias.rst:3 +msgid "Create Project's Tasks from an Email Alias" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:5 +msgid "" +"When you already have an email address that customers know from the top of " +"their heads, changing it is the last thing you want to do. Instead, link " +"that address to your project and transform those conversations into " +"structured work. It automatically creates a task in the first stage of a " +"project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:11 +msgid "Set up an incoming email server" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:14 +msgid "" +"On the *Settings* application, enable *External Email Servers* and define " +"the incoming email alias you would like to use." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:15 +msgid "" +"**For more information**: " +":doc:`/applications/general/email_communication/email_servers`" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:18 +msgid "Configure the email alias in your project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:22 +msgid "" +"Now that you have the incoming email server set up, go to " +":menuselection:`Project --> Configuration --> Projects --> Edit`. Under the " +"*Emails* tab, define the wanted email alias and choose the policy to receive" +" a message." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:23 +msgid "In addition, you can now directly set it when creating a new project." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "" +"In the settings of your project, define the emails alias under the tab email" +" in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:30 +msgid "" +"All the recipients of the email (To/Cc/Bcc) are automatically added as " +"followers of the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst:32 +msgid "The email can be seen under the name of your project on the dashboard." +msgstr "" + +#: ../../content/applications/services/project/tasks/email_alias.rst-1 +msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:3 +msgid "Recurring tasks" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:5 +msgid "" +"When handling a project, the same task often needs to be performed several " +"times: for example, weekly meetings or status reports. The **recurring " +"tasks** feature allows you to automate the creation of those tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:10 +msgid "" +"`Odoo Tutorials: Recurring tasks " +"<https://www.odoo.com/slides/slide/recurring-tasks-1946>`_" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:15 +msgid "" +"To enable recurring tasks, go to :menuselection:`Project --> Configuration " +"--> Settings`, then activate :guilabel:`Recurring Tasks`, and press " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:18 +msgid "" +"Recurring tasks are now activated on all existing projects. The feature can " +"be deactivated on an individual project by clicking the drop-down menu " +"button :guilabel:`⋮` next to the project name, then going to " +":menuselection:`Settings --> Settings --> Task Management` and disabling " +":guilabel:`Recurring Tasks`." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:24 +msgid "Set up task recurrence" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:26 +msgid "" +"In an existing task, press the :guilabel:`Recurrent` button next to the " +":guilabel:`Planned date`. Then, configure :guilabel:`Repeat Every` field " +"according to your needs." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:29 +msgid "" +"A new task in recurrence will be created once either of this conditions is " +"met: - Previous task in recurrence has been closed. - On the day of the " +"planned recurrence." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:33 +msgid "" +"The new task is created on your project dashboard with the following " +"configuration:" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:35 +msgid "" +":guilabel:`Stage`: first stage of the project dashboard (:guilabel:`New` or " +"equivalent);" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36 +msgid "" +":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, " +":guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: copied from " +"the original task;" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:38 +msgid "" +":guilabel:`Milestones`, :guilabel:`Deadline`, :guilabel:`Timesheets`, " +":guilabel:`Chatter`, :guilabel:`Activities`, :guilabel:`Subtasks`: those " +"fields are not copied;" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:41 +msgid "" +"A **smart button** on the task displays the total number of existing " +"recurrences." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:44 +msgid "Edit or stop task recurrence" +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:46 +msgid "" +"**To edit** the recurrence, open the last task in recurrence. Any changes " +"made on the task will be applied to the tasks that will be created in the " +"future." +msgstr "" + +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:49 +msgid "" +"**To stop** the recurrence, open the last task in recurrence and press the " +":guilabel:`Recurrent` button next to the :guilabel:`Planned date`." +msgstr "" + +#: ../../content/applications/services/timesheets.rst:8 +msgid "Timesheets" +msgstr "ใบบันทึกเวลา" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:3 +msgid "Create Timesheets upon Time Off Validation" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:5 +msgid "" +"Odoo automatically timesheets on project/tasks upon time off requests. This " +"allows for better overall control over the validation of timesheets, as it " +"does not leave place for forgetfulness and questions after hours that have " +"not been timesheeted by the employee." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:9 +msgid "" +"Activate the :ref:`developer mode <developer-mode>`, go to *Timesheets*, and" +" change the *Project* and *Task* set by default, if you like." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of Timesheets setting enabling the feature record time off in Odoo " +"Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:16 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select" +" or create the needed type, and decide if you would like the requests to be " +"validated or not." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"View of a time off types form emphasizing the time off requests and timesheets section in\n" +"Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:26 +msgid "" +"Now, once the employee has requested his time off and the request has been " +"validated (or not, depending on the setting chosen), the time is " +"automatically allocated on *Timesheets*, under the respective project and " +"task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:27 +msgid "" +"On the example below, the user requested *Paid Time off* from July 13th to " +"15th." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the time off request form in Odoo Time Off" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:33 +msgid "" +"Considering that validation is not required, the requested time off is " +"automatically displayed in *Timesheets*. If validation is necessary, the " +"time is automatically allocated after the responsible person for validating " +"does it so." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "" +"Video of timesheets emphasizing the requested time off from the employee in " +"Odoo Timesheets" +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst:41 +msgid "" +"Click on the magnifying glass, hovering over the concerned cell, to access " +"all the aggregated data on that cell (day), and see details regarding the " +"project/task." +msgstr "" + +#: ../../content/applications/services/timesheets/overview/time_off.rst-1 +msgid "View of the details of a project/task in Odoo Timeheets" +msgstr "" diff --git a/locale/th/LC_MESSAGES/settings.po b/locale/th/LC_MESSAGES/settings.po new file mode 100644 index 000000000..170bf1ecf --- /dev/null +++ b/locale/th/LC_MESSAGES/settings.po @@ -0,0 +1,198 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Wil Odoo, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 14.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2021-05-18 07:12+0200\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Wil Odoo, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/settings.rst:3 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/applications/settings/users_and_features.rst:6 +msgid "Users and Features" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:8 +msgid "" +"As the administrator of your database, you are responsible for its usage. " +"This includes the Apps you install as well as the number of users currently " +"in use." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:12 +msgid "" +"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) " +"but it is *not* a smartphone. You should apply caution when adding/removing " +"features (especially Apps) on your database since this may impact your " +"subscription amount significantly (or switch you from a free account to a " +"paying one on our online platform)." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:18 +msgid "" +"This page contains some information as to how you can manage your Odoo " +"instances. Before carrying any of these procedures, we **strongly** advise " +"to test them on a duplicate of your database first. That way, if something " +"goes wrong, your day-to-day business is not impacted." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:23 +msgid "" +"You can find guides on how to duplicate your databases both for :ref:`online" +" <duplicate_online>` and :ref:`on premise <duplicate_premise>` " +"installations." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:27 +msgid "" +"If you have questions about the content of this page or if you encounter an " +"issue while carrying out these procedures, please contact us through our " +"`support form <https://www.odoo.com/help>`__." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:33 +msgid "Deactivating Users" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:35 +msgid "" +"Make sure you have sufficient **administrative rights** if you want to " +"change the status of any of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:38 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:42 +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|settings|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:42 +msgid "|browse_users|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:45 +msgid "You'll then see the list of your users." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:50 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:55 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:63 +msgid "The user is now deactivated." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:65 +msgid "**Never** deactivate the main user (*admin*)" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:68 +msgid "Uninstalling Apps" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:70 +msgid "" +"Make sure you first test what you are about to do on a :ref:`duplicate " +"<duplicate_online>` of your database before making any changes (*especially*" +" installing/uninstalling apps)." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:74 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:79 +msgid "|browse_apps|" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:82 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:89 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:96 +msgid "" +"Last, after having checked the warning message (if any), click **Confirm**." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:101 +msgid "You have finished uninstalling your application." +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:104 +msgid "Good to know" +msgstr "" + +#: ../../content/applications/settings/users_and_features.rst:106 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:112 +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 "" + +#: ../../content/applications/settings/users_and_features.rst:119 +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/th/LC_MESSAGES/websites.po b/locale/th/LC_MESSAGES/websites.po new file mode 100644 index 000000000..ca37e123e --- /dev/null +++ b/locale/th/LC_MESSAGES/websites.po @@ -0,0 +1,8891 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +# Translators: +# Odoo Thaidev <odoothaidev@gmail.com>, 2024 +# Wichanon Jamwutthipreecha, 2024 +# Wil Odoo, 2024 +# Rasareeyar Lappiam, 2024 +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" +"PO-Revision-Date: 2023-11-08 08:57+0000\n" +"Last-Translator: Rasareeyar Lappiam, 2024\n" +"Language-Team: Thai (https://app.transifex.com/odoo/teams/41243/th/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: th\n" +"Plural-Forms: nplurals=1; plural=0;\n" + +#: ../../content/applications/websites.rst:5 +msgid "Websites" +msgstr "เว็บไซต์" + +#: ../../content/applications/websites/blog.rst:3 +msgid "Blog" +msgstr "บล็อก" + +#: ../../content/applications/websites/blog.rst:5 +msgid "" +"**Odoo Blog** allows you to create and manage blog posts on your website to " +"engage your audience and build a community." +msgstr "" + +#: ../../content/applications/websites/blog.rst:9 +msgid "" +"If the Blog module is not yet installed, click :guilabel:`+New` on the " +"website builder, select :guilabel:`Blog Post`, and click " +":guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:13 +msgid "Creating a blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:15 +msgid "" +"To create or edit a blog, go to :menuselection:`Website --> Configuration " +"--> Blogs: Blogs`. Click :guilabel:`New`, and enter the :guilabel:`Blog " +"Name` and the :guilabel:`Blog Subtitle`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:18 +msgid "" +"The :guilabel:`Blog` menu item is added to your website's menu the first " +"time you create a blog and gathers all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:22 +msgid "Adding a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:24 +msgid "" +"Go to your website, click :guilabel:`+New` in the top-right corner, and " +"select :guilabel:`Blog Post`. In the pop-up, **select the blog** where the " +"post should appear, write the post's :guilabel:`Title`, and " +":guilabel:`Save`. You can then write the post's content and customize the " +"page using the website builder." +msgstr "" + +#: ../../content/applications/websites/blog.rst:30 +msgid "" +"Illustrate your articles with copyright-free images from :doc:`Unsplash " +"<website/configuration/unsplash>`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:32 +msgid "Type `/` in the text editor to format and add elements to your text." +msgstr "" + +#: ../../content/applications/websites/blog.rst:35 +msgid "" +"Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right " +"corner to publish your post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:39 +msgid "Using tags" +msgstr "" + +#: ../../content/applications/websites/blog.rst:41 +msgid "" +"Tags let visitors filter all posts sharing the same tag. By default, they " +"are displayed at the bottom of posts, but can also be displayed on the " +"blog's main page. To do so, click :menuselection:`Edit --> Customize` and " +"enable the :guilabel:`Sidebar`. By default, the sidebar's :guilabel:`Tags " +"List` is enabled." +msgstr "" + +#: ../../content/applications/websites/blog.rst:46 +msgid "" +"To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: " +"Tags` and click :guilabel:`New`. Fill in the:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:49 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/websites/blog.rst:50 +msgid "" +":guilabel:`Category`: tag categories let you group tags displayed on the " +"sidebar by theme." +msgstr "" + +#: ../../content/applications/websites/blog.rst:51 +msgid "" +":guilabel:`Used in`: to apply the tag to existing blog posts, click " +":guilabel:`Add a line`, select the posts, and click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:54 +msgid "" +"You can add and create tags directly from posts by clicking " +":menuselection:`Edit --> Customize` and select the post's cover. Under " +":guilabel:`Tags`, click :guilabel:`Choose a record...`, and select or create" +" a tag." +msgstr "" + +#: ../../content/applications/websites/blog.rst-1 +msgid "Adding a tag to a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:62 +msgid "" +"To manage tag categories, go to :menuselection:`Website --> Configuration " +"--> Blogs: Tag Categories`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:66 +msgid "Customizing blog homepages" +msgstr "" + +#: ../../content/applications/websites/blog.rst:68 +msgid "" +"Customize the content of blog homepages by opening a blog homepage and " +"clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:72 +msgid "Settings apply to **all** blogs homepages." +msgstr "" + +#: ../../content/applications/websites/blog.rst:74 +msgid "" +":guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of " +"the latest post on the top banner, while :guilabel:`Drop Zone for Building " +"Blocks` removes the top banner and lets you use any building block instead." +msgstr "" + +#: ../../content/applications/websites/blog.rst:78 +msgid "" +":guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or " +":guilabel:`List`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:80 +msgid ":guilabel:`Cards`: adds a *card* effect." +msgstr "" + +#: ../../content/applications/websites/blog.rst:81 +msgid ":guilabel:`Increase Readability`: improves the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:83 +msgid "" +":guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` " +"section." +msgstr "" + +#: ../../content/applications/websites/blog.rst:85 +msgid "" +":guilabel:`Archives`: allows visitors to select a month and filter all posts" +" created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:87 +msgid "" +":guilabel:`Follow Us`: displays links to your social media networks. They " +"can be configured using the Social Media building block somewhere on your " +"website." +msgstr "" + +#: ../../content/applications/websites/blog.rst:89 +msgid "" +":guilabel:`Tags List`: displays all tags related to a blog. Visitors can " +"select a tag to filter all related posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:92 +msgid "" +":guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and " +":guilabel:`No Cover` hides them." +msgstr "" + +#: ../../content/applications/websites/blog.rst:95 +msgid ":guilabel:`Author`: displays the posts' authors." +msgstr "" + +#: ../../content/applications/websites/blog.rst:96 +msgid "" +":guilabel:`Comments/Views Stats`: displays the posts' number of comments and" +" views." +msgstr "" + +#: ../../content/applications/websites/blog.rst:97 +msgid "" +":guilabel:`Teaser & Tags`: displays the posts' first sentences and tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:100 +msgid "Customizing blog posts" +msgstr "" + +#: ../../content/applications/websites/blog.rst:102 +msgid "" +"Customize posts by opening a blog post and clicking :menuselection:`Edit -->" +" Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:105 +msgid "Settings apply to **all** posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:107 +msgid "" +":guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside" +" the cover image, and :guilabel:`Title above Cover` displays it above." +msgstr "" + +#: ../../content/applications/websites/blog.rst:110 +msgid ":guilabel:`Increase Readability`: increases the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:112 +msgid "" +":guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional " +"options:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:114 +msgid "" +":guilabel:`Archive`: allows visitors to select a month and filter all posts " +"created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:116 +msgid ":guilabel:`Author`: displays the post's author and creation date." +msgstr "" + +#: ../../content/applications/websites/blog.rst:117 +msgid ":guilabel:`Blog List`: displays links to all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:118 +msgid "" +":guilabel:`Share Links`: displays share buttons to several social networks." +msgstr "" + +#: ../../content/applications/websites/blog.rst:119 +msgid ":guilabel:`Tags`: displays the post's tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:121 +msgid ":guilabel:`Breadcrumb`: displays the path to the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:123 +msgid "" +":guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the " +"bottom, and :guilabel:`Comments` enable visitors to comment on the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:126 +msgid "" +":guilabel:`Select To Tweet`: visitors are offered to tweet the text they " +"select." +msgstr "" + +#: ../../content/applications/websites/blog.rst:129 +msgid "" +"Use :ref:`Plausible <website/analytics/plausible>` to keep track of the " +"traffic on your blog." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:8 +msgid "eCommerce" +msgstr "อีคอมเมิร์ซ" + +#: ../../content/applications/websites/ecommerce.rst:10 +msgid "" +"Run a modern open-source online store with Odoo eCommerce. Learn how to sell" +" online, promote products and increase your average cart sizes." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:14 +#: ../../content/applications/websites/website.rst:14 +msgid "" +"Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to " +"all Odoo Online databases for one year. Visitors can then access your " +"website with an address such as ``www.example.com`` rather than the default " +"``example.odoo.com``." +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:19 +msgid ":doc:`Website Documentation <website>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:20 +#: ../../content/applications/websites/website.rst:20 +msgid "`Odoo Tutorials: Website <https://www.odoo.com/slides/website-25>`_" +msgstr "" + +#: ../../content/applications/websites/ecommerce.rst:21 +#: ../../content/applications/websites/website.rst:21 +msgid "" +"`Odoo Tutorials: eCommerce <https://www.odoo.com/slides/ecommerce-26>`_" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping.rst:5 +msgid "Checkout, payment, and shipping" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:3 +msgid "Add to cart" +msgstr "เพิ่มในตะกร้า" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:5 +msgid "" +"The :guilabel:`Add to Cart` button can be customized in multiple ways. You " +"can:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:7 +msgid "" +"Choose on which page customers go after clicking the 'Add to Cart' button;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:8 +msgid "Hide the 'Add to Cart' button to prevent sales;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:9 +msgid "" +"Add a 'Buy Now' button to skip the cart step and lead customers straight to " +"checkout;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:10 +msgid "Create additional 'Add to Cart / Buy Now' buttons;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:11 +msgid "Add an 'Order Again' button to the customer portal." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:14 +msgid ":doc:`checkout`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:17 +msgid "'Add to Cart' action customization" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:19 +msgid "" +"When customers click on the :guilabel:`Add to Cart` button, the product is " +"added to their cart, and customers remain **by default** on the product's " +"page. However, customers can either immediately be **redirected** to their " +"cart, or given the choice on what to do through a **dialog box**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:23 +msgid "" +"To change the default behavior, go to :menuselection:`Website --> " +"Configuration --> Settings`. Under the :guilabel:`Shop - Checkout Process` " +"section, look for :guilabel:`Add to Cart` and select one of the options." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:28 +msgid "" +"If a product has :doc:`optional products " +"<../managing_products/cross_upselling>`, the **dialog box** will always " +"appear." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:32 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:20 +msgid ":doc:`../managing_products/catalog`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:37 +msgid "Replace 'Add to Cart' button by 'Contact Us' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:39 +msgid "" +"You can replace the 'Add to Cart' button with a 'Contact Us' button which " +"redirects users to the URL of your choice." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:43 +msgid "" +"Hiding the :guilabel:`Add to Cart` button is often used by B2B eCommerces " +"that need to restrict purchases only to :ref:`customers with an account " +"<checkout-sign>`, but still want to display an online product catalog for " +"those without." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:47 +msgid "" +"To do so, go to :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Products` and tick :guilabel:`Prevent Sale of Zero Priced Product`. " +"This creates a new :guilabel:`Button url` field where you can enter the " +"**redirect URL** to be used. Then, set the price of the product to `0.00` " +"either from the **product's template**, or from a :doc:`pricelist " +"<../../../sales/sales/products_prices/prices/pricing>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Contact us button on product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:58 +msgid "" +"The 'Contact Us' button and '*Not Available For Sale*' text can both be " +"modified using the **website builder** on the product's page " +"(:menuselection:`Edit --> Customize`) by clicking on them." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:63 +msgid "Customizable 'Add to Cart' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:65 +msgid "" +"You can also create a customizable 'Add to Cart' button and link it to a " +"specific product. The **customized button** can be added on any page of the " +"website as an **inner content** building block, and is an *additional* " +"button to the regular :guilabel:`Add to Cart` button." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:69 +msgid "" +"To add it, go on the :guilabel:`Shop` page of your choice, click " +":menuselection:`Edit --> Blocks` and place the building block. Once placed, " +"you have the following options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:72 +msgid "" +":guilabel:`Product`: select the product to link the button with. Selecting a" +" product renders the :guilabel:`Action` field available;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:74 +msgid "" +":guilabel:`Action`: choose if the button should :guilabel:`Add to Cart` or " +":guilabel:`Buy Now` (instant checkout)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:84 +msgid "'Buy Now' button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:86 +msgid "" +"You can enable the 'Buy Now' button to instantly take the customer to " +"**checkout** instead of adding the product to the cart. The :guilabel:`Buy " +"Now` button is an *additional* button and does not replace the " +":guilabel:`Add to Cart` button. To enable it, go to :menuselection:`Website " +"--> Configuration --> Settings --> Shop - Checkout Process` and tick " +":guilabel:`Buy Now`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Buy Now button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:97 +msgid "Re-order from portal" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:99 +msgid "" +"Customers have the possibility to **re-order** items from **previous sales " +"orders** on the customer portal. To do so, go to :menuselection:`Website -->" +" Configuration --> Settings --> Shop - Checkout Process` and enable " +":guilabel:`Re-order From Portal`. Customers can find the :guilabel:`Order " +"Again` button on their **sales order** from the **customer portal**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst-1 +msgid "Re-order button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:3 +msgid "Checkout" +msgstr "เช็คเอาท์" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:5 +msgid "" +"You can customize the **checkout steps**, add more content using the " +"**website builder**, and enable additional features such as **express " +"checkout** and **sign in/up at checkout**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:8 +msgid "" +"You can use **building blocks** to add content at any step of the checkout " +"process. To do so, from any **checkout page**, go to :menuselection:`Edit " +"--> Blocks`, and drag and drop **building blocks** to the page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:13 +msgid "" +"Note that content added through building blocks is **specific** to each " +"step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:16 +msgid "Checkout steps" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:19 +msgid "Review order: promo code (and subtotal)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:21 +msgid "" +"If you have enabled :guilabel:`Discounts, Loyalty, & Gift Card` in the " +"settings (:menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products`), you can enable the :guilabel:`Promo Code` field " +"(:menuselection:`Edit --> Customize`) from any checkout page. Customers can " +"then redeem gift cards and promotional codes at the :guilabel:`Review Order`" +" step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:26 +msgid "" +"Furthermore, you can display the subtotal with discounts applied by enabling" +" :guilabel:`Show Discount in Subtotal`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Subtotal discount" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:34 +msgid "Address: B2B fields" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:36 +msgid "" +"Optional :guilabel:`TIN/VAT` and :guilabel:`Company Name` fields can be " +"added to the :guilabel:`Billing Address` form for B2B customers, at the " +":guilabel:`Address` step. To add the fields, go to :menuselection:`Edit --> " +"Customize` from any checkout page, and enable :guilabel:`Show B2B fields`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:42 +msgid "Request extra info (additional step)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:44 +msgid "" +"You can request :guilabel:`Extra Info` from the customer by adding an " +":guilabel:`Extra Info` step between the :guilabel:`Address` and " +":guilabel:`Confirm Order` steps. To do so, go to :menuselection:`Edit --> " +"Customize` from any checkout page, and enable :guilabel:`Extra Step Option`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:53 +msgid "" +"The :guilabel:`Extra Info` step is an online form linked to the quotation or" +" sales order of the customer. The information added during that step can be " +"found on the quotation or sales order of the customer from the back end, in " +"the **Sales** app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:57 +msgid "" +"When enabled, you can remove, add, and modify fields of the form by clicking" +" on :guilabel:`Edit` in the top-right corner, and then clicking on any of " +"the form's fields. All customization options, as well as the :guilabel:`+ " +"Field` button to add new fields, are available at the bottom of the " +":guilabel:`Customize` menu under the :guilabel:`Field` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Online form customization" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:67 +msgid "Confirm order: terms and conditions" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:69 +msgid "" +"You can ask customers to agree to the :guilabel:`Terms & Conditions` in " +"order to confirm their order by enabling :guilabel:`Accept Terms & " +"Conditions` under :menuselection:`Edit --> Customize` on any checkout page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Terms and conditions" +msgstr "เงื่อนไขและข้อกำหนด" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:78 +msgid "Express checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:80 +msgid "" +"You can enable a :guilabel:`Buy Now` button on products' pages which " +"instantly takes the customer to the :guilabel:`Confirm Order` checkout page," +" instead of adding the product to the cart. To do so, go to " +":menuselection:`Website --> Configuration --> Settings --> Shop - Checkout " +"Process section` and tick :guilabel:`Buy Now`. Alternatively, the " +":guilabel:`Buy Now` button can also be enabled from any product's page by " +"going :menuselection:`Edit --> Customize`, in the :guilabel:`Cart` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:86 +msgid "" +"The button can be found next to the :guilabel:`Add to Cart` button on the " +"product's page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst-1 +msgid "Buy now (express checkout) button" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:93 +msgid ":ref:`Product page design: additional functions <ecommerce-functions>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:98 +msgid "Guest and signed-in checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:100 +msgid "" +"It is possible to introduce a **checkout policy** under which customers can " +"either checkout as **guests** or **signed-in users only**. Customers can " +"also checkout as guest, and **optionally sign up later** in order to track " +"their order, if enabled." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:104 +msgid "" +"To select a policy, go to :menuselection:`Website --> Configuration --> " +"Settings --> Shop - Checkout Process`. You can choose between:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:107 +msgid "" +":guilabel:`Optional`: allows guests to checkout and later register from the " +"**order confirmation** email to track their order;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:109 +msgid "" +":guilabel:`Disabled (buy as guest)`: customers can only checkout as guests;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:110 +msgid "" +":guilabel:`Mandatory (no guest checkout)`: customers can only checkout if " +"they have signed-in." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:113 +msgid ":doc:`../ecommerce_management/customer_accounts`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:114 +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:24 +msgid ":doc:`/applications/general/users/portal`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:117 +msgid "B2B access restriction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:119 +msgid "" +"If you wish to restrict checkout only to **selected B2B customers**, enable " +":guilabel:`Mandatory (no guest checkout)` and go to :menuselection:`Website " +"--> eCommerce --> Customers`. Select the customer you wish to **grant access" +" to**, click :menuselection:`Action --> Grant portal access`, and click " +":guilabel:`Grant Access`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:125 +msgid "" +"Settings are **website-specific**, which means you can set up a B2C website " +"allowing **guest** checkout, and another for B2B customers with **mandatory " +"sign-in**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:129 +msgid "" +"Users can only have one portal access per **email**. They *cannot* be " +"granted access to two different portals with the same **email address**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:133 +msgid "Shared customer accounts" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:135 +msgid "" +"If you enable :guilabel:`Shared Customer Accounts` under " +":menuselection:`Website --> Configuration --> Settings --> Privacy section`," +" you can allow or disallow access to *all* websites for one same account." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:3 +msgid "Payment providers" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:5 +msgid "" +"Odoo supports a multitude of online :doc:`payment providers " +"</applications/finance/payment_providers>` for your website, allowing your " +"customers to pay with their preferred payment methods." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:10 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:55 +msgid ":doc:`/applications/sales/sales/products_prices/ewallets_giftcards`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:11 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:12 +msgid ":doc:`../checkout_payment_shipping/checkout`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:14 +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:94 +#: ../../content/applications/websites/website/configuration.rst:5 +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:24 +#: ../../content/applications/websites/website/reporting/link_tracker.rst:10 +msgid "Configuration" +msgstr "การกำหนดค่า" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:16 +msgid "" +"To set up payment providers on the eCommerce app, go to " +":menuselection:`Website --> Configuration --> Payment Providers`. From here," +" :guilabel:`Activate` the payment providers you wish to have available on " +"your shop, and configure them according to your needs." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:20 +msgid "" +"Alternatively, you can access **payment providers** via " +":menuselection:`Website --> Configuration --> Settings`. In the " +":guilabel:`Shop - Payment` section, you can :guilabel:`Configure SEPA Direct" +" Debit` if you wish to use it, as well as :guilabel:`View other providers`. " +"If you use the :guilabel:`Authorize.net` payment provider, the :ref:`Payment" +" Capture Method <payment_providers/features/manual_capture>` can be " +"configured in that same menu." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:27 +msgid "" +"If you are using :doc:`/applications/finance/payment_providers/paypal`, you " +"can also enable and configure it here." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:31 +msgid "Checkout payment options" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:33 +msgid "" +"Once activated, customers can choose the payment provider of their choice " +"during the **checkout process**, at the :guilabel:`Confirm Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst-1 +msgid "Payment provider selection at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:41 +msgid "eWallets and gift cards" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:43 +msgid "" +"When checking out, customers can pay with an eWallet or gift cards. To " +"enable these, go to :menuselection:`Website --> Configuration --> Settings`," +" and in the :guilabel:`Shop-Products` section, enable " +":menuselection:`Discounts, Loyalty & Gift Card`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:47 +msgid "" +"Once enabled, customers can enter their gift card **code** or pay with their" +" eWallet at the checkout step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst-1 +msgid "Enter gift card code to process checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:3 +msgid "Shipping methods" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:5 +msgid "" +"Depending on your shipping strategy, you have the choice to either use your " +":ref:`own shipping methods <ecommerce-own-shipping>`, or use an integration " +"with an :ref:`existing shipping provider <ecommerce-shipping-providers>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:15 +msgid "Own shipping methods" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:17 +msgid "" +"You can create your own custom shipping methods and define rules to compute " +"shipping costs. To do so, go to :menuselection:`Website --> Configuration " +"--> Shipping Methods`, and either select an **existing** shipping method, or" +" :guilabel:`Create` one. When creating a shipping method, you can choose " +"between :doc:`Fixed Price " +"</applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`," +" :doc:`Based on Rules " +"</applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method>`," +" and :guilabel:`Pickup in store`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:26 +msgid "Pickup in store" +msgstr "รับสินค้าที่ร้านค้า" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:28 +msgid "" +":guilabel:`Pickup in store` must first be **enabled** in the settings " +"(:menuselection:`Website --> Configuration --> Settings --> Shipping " +"section)` by checking :guilabel:`On Site Payments & Picking`. Once enabled, " +"you can select and :guilabel:`Customize Pickup Sites`. :guilabel:`Picking " +"sites` can be made **website-specific**, but are by default available for " +"*all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:34 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:35 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:83 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:36 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:85 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:37 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:42 +msgid "Shipping providers" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:44 +msgid "" +"Another solution is to use one of the integrations with an existing shipping" +" provider. The advantage of using an integration is that delivery costs are " +"automatically computed based on each order as well as generating shipping " +"labels." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:49 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:50 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:51 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:52 +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:84 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:55 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:204 +msgid "Website availability" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 +msgid "" +"Shipping methods can be made available on **specific** websites *only*, if " +"desired. To do so, go to :menuselection:`Website --> Configuration --> " +"Settings --> Shipping Methods`, and select the desired **shipping method**. " +"In the :guilabel:`Website` field, set the website you want the shipping " +"method to be restrained to. Leave the field **empty** for the method to be " +"available on *all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:63 +msgid "Delivery method at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:65 +msgid "" +"Customers can choose the shipping method at the end of the checkout process," +" at the :guilabel:`Confirm Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst-1 +msgid "Delivery method choice at checkout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management.rst:5 +msgid "eCommerce management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:3 +#: ../../content/applications/websites/website/configuration/multi_website.rst:130 +msgid "Customer accounts" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:5 +msgid "" +"Having customer accounts on an eCommerce allows customers to access all " +"their documents from a single place. To access their account, customers must" +" be **logged-in** on the eCommerce website, click on their **username** in " +"the top-right corner of the screen, and click :guilabel:`My Account`. From " +"there, customers can access their :guilabel:`quotations`, " +":guilabel:`orders`, :guilabel:`invoices`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst-1 +msgid "Customer account log-in" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:16 +msgid "" +"Customers can only have an account if the :ref:`sign in/up at checkout " +"<checkout-sign>` option allows for accounts creation." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:20 +msgid "" +"Similarly to the rest of the website, the customer account page can be " +"customized with **content blocks** and other features through the **website " +"builder**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:27 +msgid "Access restriction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:29 +msgid "" +"It is possible to allow or restrict the documents to which customers have " +"access through the website builder. Log in your **own** account with your " +"Odoo database credentials, and go to :menuselection:`Edit --> Customize`. " +"From the website builder menu, enable or disable the documents customers can" +" have access to." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst-1 +msgid "Documents to which customers have access to from their account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:39 +msgid "Multi-website account" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_accounts.rst:41 +msgid "" +"If you own multiple websites, you can make customer accounts available " +"across **all** websites. Then, the customer only needs one account. To do " +"so, go to :menuselection:`Website --> Configuration --> Settings --> Privacy" +" section`, and enable :guilabel:`Shared Customer Accounts`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:3 +msgid "Customer interaction" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:5 +msgid "" +"Odoo offers many ways to interact with customers and for customers to " +"interact with your website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:10 +msgid "Product reviews" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:12 +msgid "" +"Customers can give a rating to your products. This is a great way to promote" +" your products or services since reviews can influence purchase processes. " +"To activate the **rating** feature, from your **shop page**, select a " +"product, go to :menuselection:`Edit --> Customize` and enable " +":guilabel:`Rating`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Rating of a product on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:22 +msgid "" +"Only portal users which purchased the product or service can leave ratings." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:25 +msgid "" +"Customer reviews can be hidden by clicking the :guilabel:`Visible` button " +"next to a published review." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:29 +msgid "Live chat" +msgstr "ไลฟ์แชท" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:31 +msgid "" +"A chatbot is available and can simulate a human-like conversation with " +"website visitors via text messages in a chat box." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:35 +msgid ":doc:`../../livechat`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:36 +msgid ":doc:`../../livechat/ratings`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:37 +msgid ":doc:`../../livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:42 +msgid "Contact forms" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:45 +msgid "Helpdesk" +msgstr "ดูแลช่วยเหลือ" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:47 +msgid "" +"Customers may need support after purchasing a product or subscribing to a " +"service. It is possible to create a **contact form**, which, when fulfilled," +" automatically creates a new ticket for your **support team**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Contact form to submit a ticket to the support team" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:55 +msgid "" +"To add a contact form, **create** a new page (:menuselection:`+ New --> " +"Page`) if necessary, and drag and drop a :guilabel:`Form` block from the " +":guilabel:`Dynamic Content` section onto the page. Once placed, click on the" +" form (while in :guilabel:`Edit` mode), and in the :guilabel:`Action` field," +" select :guilabel:`Create a Ticket`. You can then select to which " +":guilabel:`Helpdesk team` the ticket should be assigned." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Action field to create a task upon submitting a form" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:66 +msgid "Contact us" +msgstr "ติดต่อเรา" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:68 +msgid "" +"A 'Contact Us' page makes it easier for customers and prospects to contact " +"your company and get in touch." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:71 +msgid "" +"To have a 'Contact Us' page, create a new page (:menuselection:`+ New --> " +"Page`) if necessary, and click on :menuselection:`Edit --> Customize`. Then," +" drag and drop a :guilabel:`Form` block onto the page. Select the form and " +"define the action to be performed when submitted in the :guilabel:`Action` " +"field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:76 +msgid "" +"When clicking on a field, or when adding a new field (:guilabel:`+ Field`), " +"you can select its :guilabel:`Type`. This enables different options, such as" +" :guilabel:`Multiple Checkboxes`, which customers can use to indicate the " +"services they are interested in, for example." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Tags to be selected on the 'Contact Us' form" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "'Checkboxes' configuration settings" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:89 +msgid "Newsletter" +msgstr "จดหมายข่าว" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:91 +msgid "" +"Customers can get updates on your eCommerce activities by subscribing to a " +"newsletter. Visitors subscribing to the newsletter are automatically added " +"to the mailing list of the **Email Marketing** application. You can either " +"choose a newsletter **block**, a newsletter **popup**, or both." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:95 +msgid "" +"**Popup**: prompts up a newsletter box when visitors scroll down the page;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:96 +msgid "" +"**Block**: displays a field on the page where customers can sign up by " +"entering their email." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:98 +msgid "" +"The newsletter **block** can be configured according to different " +":guilabel:`Templates`. To do so, click the **block** while in " +":menuselection:`Edit --> Customize`, and select a :guilabel:`Template` in " +"the :guilabel:`Newsletter Block` section. There are **three** templates " +"available:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:102 +msgid "" +":guilabel:`Email Subscription`: visitors can sign up by email to the " +"newsletter, without any choice to the content. The content is defined in " +":menuselection:`Edit --> Customize` in the :guilabel:`Newsletter` field;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:105 +msgid "" +":guilabel:`SMS Subscription`: is the same as :guilabel:`Email Subscription`," +" but by SMS;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:106 +msgid "" +":guilabel:`Form Subscription`: allows adding several fields, as well as a " +"checkbox for the visitor to agree to the **GDPR policy** of your website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst-1 +msgid "Form subscription configuration and settings" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/customer_interaction.rst:114 +msgid "" +"Alternatively, you can select :guilabel:`Subscribe to Newsletter` as " +":guilabel:`Action` when creating a :ref:`contact form <contact-form>`, " +"allowing for the same level of customization. Make sure to add a checkbox " +"stating visitors agree to be added to the mailing list." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:3 +msgid "Order handling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:5 +msgid "" +"When a customer orders on your eCommerce, there are **three** record types " +"required to be handle in Odoo:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:8 +msgid ":ref:`Sales orders <handling/sales>`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:9 +msgid ":ref:`Delivery orders <handling/delivery>`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:10 +msgid ":ref:`Invoices & legal requirements <handling/legal>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:15 +msgid "Sales orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:18 +msgid "Order and payment status" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:20 +msgid "" +"The first step when a customer adds a product to his cart is the creation of" +" a quotation. Orders can be managed either from the **Website** or " +":doc:`Sales </applications/sales/sales>` app. eCommerce orders can " +"automatically be assigned to a specific sales team by going to " +":menuselection:`Website --> Configuration --> Settings`. In the **Shop - " +"Checkout Process** section, select a :guilabel:`Sales Team` or " +":guilabel:`Salesperson` to handle eCommerce orders." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst-1 +msgid "Assignment of online orders to a sales team or salesperson" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:30 +msgid "" +"Orders can be found under :menuselection:`Website --> eCommerce --> " +"Orders/Unpaid Orders`. Each order goes through a different status:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:33 +msgid "" +"**Quotation**: a new product is added to the cart, but the customer has " +"*not* gone through the checkout process yet;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:35 +msgid "" +"**Quotation sent**: the customer has gone through the checkout process and " +"confirmed the order, but the payment is not yet confirmed;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:37 +msgid "" +"**Order**: the customer has gone through the checkout process, confirmed the" +" order, and the payment is received." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst-1 +msgid "Statuses of eCommerce orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:45 +msgid "Abandoned cart" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:47 +msgid "" +"An **abandoned cart** represents an order for which the customer did **not " +"finish** the checkout confirmation process. For these orders, it is possible" +" to send an **email reminder** to the customer automatically. To enable that" +" feature, go to :menuselection:`Website --> Configuration --> Settings` and " +"in the :guilabel:`Email & Marketing` section, enable " +":guilabel:`Automatically send abandoned checkout emails`. Once enabled, you " +"can set the **time-lapse** after which the email is sent and customize the " +"**email template** used." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:55 +msgid "" +"For abandoned cart emails, the customer must either have entered their " +"contact details during the checkout process; or be logged-in when they added" +" the product to their cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:61 +msgid "Delivery orders" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:64 +msgid "Delivery flow" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:66 +msgid "" +"Once a quotation has been confirmed, a delivery order is automatically " +"created. The next step is to process this delivery." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:69 +msgid "" +"Packing eCommerce orders usually requires picking the product, preparing the" +" packaging, printing the shipping label(s) and shipping to the customer. " +"Depending on the number of orders, strategy, or resources, those steps can " +"be considered as one or multiple actions in Odoo." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:73 +msgid "" +"An automatic email can be sent to the customer when the transfer status in " +"Odoo is “done”. To do so, enable the feature in the settings of the " +":doc:`Inventory </applications/inventory_and_mrp/inventory>` app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:78 +msgid "" +"If customers are allowed to pay when picking up their order in stores or by " +"wire transfer, the quotation is **not** be confirmed and the stock is " +"**not** be reserved. Orders must be confirmed manually to reserve products " +"in stock." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:88 +msgid "Returns and refunds" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:90 +msgid "" +"Customers can only return an order through an online form. It may not be " +"possible to return products depending on the return strategy or type of " +"product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:93 +msgid "" +"Full refunds can be directly sent to customers from within the order " +"interface. A refund-compatible payment provider needs to be enabled first." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:97 +msgid ":doc:`/applications/sales/sales/products_prices/returns`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:98 +msgid ":doc:`/applications/services/helpdesk/advanced/after_sales`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:99 +msgid ":doc:`/applications/finance/payment_providers`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:104 +msgid "Invoice and legal requirements" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:106 +msgid "" +"The final step of an ecommerce order is to generate the invoice and send it " +"to the customer. Depending on the type of business (B2B or B2C), an invoice " +"can either be generated automatically (B2B) or on demand of the customer " +"(B2C). This process can be automated if (and when) the online payment is " +":ref:`confirmed <handling/sales>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/order_handling.rst:111 +msgid "" +"To automate invoicing, go to :menuselection:`Website --> Configuration --> " +"Settings` and in the :guilabel:`Invoicing` section, enable " +":guilabel:`Automatic Invoice`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:3 +msgid "Performance monitoring" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:5 +msgid "" +"Odoo integrates a variety of tools to analyze and improve the performance of" +" your eCommerce website." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:9 +msgid "Data monitoring" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:11 +msgid "" +"**Website** allows monitoring and analysis of the sales performance of your " +"eCommerce. To access the **reporting view**, go to :menuselection:`Website " +"--> Reporting --> eCommerce`. This dashboard helps you monitor everything " +"related to sales, such as sales performance per product, category, day, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst-1 +msgid "Performance reporting of eCommerce" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:19 +msgid "" +"By clicking :guilabel:`Measures`, you can select the type of measurement " +"used, such as:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:21 +msgid ":guilabel:`Margin`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:22 +msgid ":guilabel:`Qty Invoiced`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:23 +msgid ":guilabel:`Untaxed Total`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:24 +msgid ":guilabel:`Volume`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:25 +msgid "..." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:27 +msgid "" +"Other options include **multiple views (Pivot, etc.), comparison** by " +"periods or years, and directly :guilabel:`insert in spreadsheet`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:31 +#: ../../content/applications/websites/website/configuration/multi_website.rst:153 +msgid "Analytics" +msgstr "การวิเคราะห์" + +#: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:33 +msgid "" +"It is possible to link your Odoo website with " +":ref:`website/analytics/plausible` and :ref:`website/analytics/GA`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products.rst:5 +msgid "Products" +msgstr "สินค้า" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:3 +msgid "Catalog" +msgstr "แคตตาล็อก" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:5 +msgid "" +"The eCommerce catalog is the equivalent of your physical store shelves: it " +"allows customers to see what you have to offer. Clear categories, available " +"options, sorting, and navigation threads help you structure it efficiently." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:10 +msgid "Categorize the product catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:12 +msgid "" +"In Odoo, there is a **specific category model** for your eCommerce. Using " +"eCommerce categories for your products allows you to add a navigation menu " +"on your eCommerce page. Visitors can then use it to view all products under " +"the category they select." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:16 +msgid "" +"To do so, go to :menuselection:`Website --> eCommerce --> Products`, select " +"the product you wish to modify, click on the :guilabel:`Sales` tab, and " +"select the :guilabel:`Categories` you want under :guilabel:`eCommerce Shop`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "eCommerce categories under the \"Sales\" tab" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:25 +msgid "A single product can appear under multiple eCommerce categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:27 +msgid "" +"When your product's categories are configured, go to your **main shop page**" +" and click on :menuselection:`Edit --> Customize tab`. In the " +":guilabel:`Categories` option, you can either enable a menu on the " +":guilabel:`Left`, on the :guilabel:`Top`, or both. If you select the " +":guilabel:`Left` category, the option :guilabel:`Collapsable Category " +"Recursive` appears and allows to render the :guilabel:`Left` category menu " +"collapsable." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Categories options for your eCommerce website" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:38 +msgid ":doc:`products`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:43 +msgid "Browsing" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:45 +msgid "" +"The eCommerce category is the first tool to organize and split your " +"products. However, if you need an extra level of categorization in your " +"catalog, you can activate various **filters** such as attributes or sort-by " +"search." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:50 +msgid "Attributes" +msgstr "คุณลักษณะ" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:52 +msgid "" +"Attributes refer to **characteristics** of a product, such as **color** or " +"**material**, whereas variants are the different combinations of attributes." +" :guilabel:`Attributes and Variants` can be found under " +":menuselection:`Website --> eCommerce --> Products`, select your product, " +"and :guilabel:`Attributes & Variants` tab." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:58 +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:15 +msgid ":doc:`../../../sales/sales/products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Attributes and variants of your product" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:64 +msgid "" +"To enable **attribute filtering**, go to your **main shop page**, click on " +":menuselection:`Edit --> Customize tab` and select either :guilabel:`Left`, " +":guilabel:`Top`, or both. Additionally, you can also enable :guilabel:`Price" +" Filtering` to enable price filters." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:69 +msgid "" +":guilabel:`Price Filter` works independently from **attributes** and, " +"therefore, can be enabled on its own if desired." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:73 +msgid "" +"You can use **attribute filters** even if you do not work with product " +"variants. When adding attributes to your products, make sure only to specify" +" *one* value per attribute. Odoo does not create variants if no combination " +"is possible." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:78 +msgid "Sort-by search" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:80 +msgid "" +"It is possible to allow the user to manually **sort the catalog** using the " +"search bar. From your **main shop page**, click on :menuselection:`Edit --> " +"Customize tab`; you can enable or disable the :guilabel:`Sort-By` option as " +"well as the :guilabel:`Layout` button. You can also select the " +":guilabel:`Default Sort` of the :guilabel:`Sort-By` button. The default sort" +" applies to *all* categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:86 +msgid "The **sorting** options are:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:88 +msgid "Featured" +msgstr "ฟีเจอร์" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:89 +msgid "Newest Arrivals" +msgstr "สินค้ามาใหม่" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:90 +msgid "Name (A-Z)" +msgstr "ชื่อ (A-Z)" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:91 +msgid "Price - Low to High" +msgstr "ราคา - น้อยไปมาก" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:92 +msgid "Price - High to Low" +msgstr "ราคา - มากไปน้อย" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:94 +msgid "" +"In addition, you can **manually edit** the catalog's order of a product by " +"going to **the main shop page** and clicking on the product. Under the " +":guilabel:`Product` section of the :guilabel:`Customize` section, you can " +"rearrange the order by clicking on the arrows. `<<` `>>` move the product to" +" the **extreme** right or left, and `<` `>` move the product by **one** row " +"to the right or left. It is also possible to change the catalog's order of " +"products in :menuselection:`Website --> eCommerce --> Products` and drag-" +"and-dropping the products within the list." +msgstr "" +"นอกจากนี้ คุณสามารถ **แก้ไข** คำสั่งซื้อแคตตาล็อกผลิตภัณฑ์ได้ด้วยตนเอง " +"โดยไปที่ **หน้าร้านค้าหลัก** และคลิกที่ผลิตภัณฑ์ ใต้ส่วน " +":guilabel:`ผลิตภัณ์` ของส่วน :guilabel:`กำหนดเอง` " +"คุณสามารถจัดเรียงลำดับใหม่ได้โดยคลิกที่ลูกศร `<<` `>>` " +"ย้ายผลิตภัณฑ์ไปทางขวาหรือซ้าย **สุดขีด** และ `<` `>` " +"ย้ายผลิตภัณฑ์ไปทางขวาหรือซ้าย **หนึ่ง** แถว " +"นอกจากนี้ยังสามารถเปลี่ยนลำดับผลิตภัณฑ์ของแค็ตตาล็อกได้ใน " +":menuselection:`เว็บไซต์ --> อีคอมเมิร์ซ --> ผลิตภัณฑ์` " +"และลากและวางผลิตภัณฑ์ภายในรายการ" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Product rearrangement in the catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:107 +msgid "Page design" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:110 +msgid "Category page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:112 +msgid "" +"You can customize the layout of the category page using the website builder." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:115 +msgid "" +"Editing the layout of the category page is global; editing one category " +"layout affects *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:118 +msgid "" +"To do so, go on to your :menuselection:`Category page --> Edit --> " +"Customize`. Here, you can choose the layout, the number of columns to " +"display the products, etc. The :guilabel:`Product Description` button makes " +"the product description visible from the category page, underneath the " +"product picture." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Layout options of the category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:127 +msgid "" +"You can choose the size of the grid, but be aware that displaying too many " +"products may affect performance and page loading speed." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:131 +msgid "Product highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:133 +msgid "" +"You can highlight products to make them more visible on the category or " +"product page. On the page of your choice, go to :menuselection:`Edit --> " +"Customize` and click on the product to highlight. In the :guilabel:`Product`" +" section, you can choose the size of the product image by clicking on the " +"grid, and you can also add a **ribbon** or :guilabel:`Badge`. This displays " +"a banner across the product's image, such as:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:139 +msgid "Sale;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:140 +msgid "Sold out;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:141 +msgid "Out of stock;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:142 +msgid "New." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:144 +msgid "" +"Alternatively, you can activate the :doc:`developer mode " +"<../../../general/developer_mode>` on the **product's template**, and under " +"the :guilabel:`Sales` tab, change or create the ribbon from the " +":guilabel:`Ribbon` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:149 +msgid "" +"The :doc:`developer mode <../../../general/developer_mode>` is only intended" +" for experienced users who wish to have access to advanced tools. Using the " +"**developer mode** is *not* recommended for regular users." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Ribbon highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:158 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:160 +msgid "" +"You can access and enable additional feature buttons such as **add to " +"cart**, **comparison list**, or a **wishlist**. To do so, go to your **main " +"shop page**, and at the end of the :guilabel:`Products Page` category, click" +" on the feature buttons you wish to use. All three buttons appear when " +"hovering the mouse over a product's image." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:165 +msgid "" +":guilabel:`Add to Cart`: adds a button to :doc:`add the product to the cart " +"<../checkout_payment_shipping/cart>`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:167 +msgid "" +":guilabel:`Comparison List`: adds a button to **compare** products based on " +"their price, variant, etc.;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:169 +msgid "" +":guilabel:`Wishlist Button`: adds a button to **wishlist** the product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Feature buttons for add to cart, comparison list, and wishlist" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Appearance of buttons when hoovering over the mouse" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:180 +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:112 +msgid "Add content" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:182 +msgid "" +"You can use **building blocks** to add content on the category page, with a " +"variety of blocks ranging from :guilabel:`Structure` to :guilabel:`Dynamic " +"Content`. Specific areas are defined to use blocks are defined and " +"highlighted on the page when **dragging-and-dropping** a block." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst-1 +msgid "Building blocks areas" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:190 +msgid "" +"If you drop a building block **on top** of the product list, it creates a " +"new category header specific to *that* category." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:192 +msgid "" +"If you drop a building **on the top** or **bottom** of the page, it becomes " +"visible on *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:196 +msgid "" +"Adding content to an eCommerce category page is beneficial in terms of " +"**SEO** strategy. Using **keywords** linked to the products or the eCommerce" +" categories improves organic traffic. Additionally, each category has its " +"own specific URL that can be pointed to and is indexed by search engines." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:3 +msgid "Cross-selling and upselling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:5 +msgid "" +"Any sales process is an opportunity to maximize revenues. **Cross-selling " +"and upselling** are sales techniques consisting in selling customers " +"additional or more expensive products and services than what they were " +"originally shopping for. It is a great way to maximize the value of each one" +" of your customers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:10 +msgid "**Cross-selling** can be done via **two** features:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:12 +msgid "" +":ref:`Optional products <cross_upselling/optional>` upon **adding to cart**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:13 +msgid "" +":ref:`Accessory products <cross_upselling/accessory>` on the **checkout " +"page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:15 +msgid "" +"**Upselling** is only done via :ref:`alternative products " +"<cross_upselling/alternative>` on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:19 +msgid ":doc:`catalog`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:22 +msgid "Cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:27 +msgid "Optional products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:29 +msgid "" +"**Optional products** are suggested when customers click :guilabel:`Add to " +"cart`, either from the **product page** or **catalog page**. Upon clicking, " +"a pop-up window opens with the **optional products** displayed in the " +":guilabel:`Available Options` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Optional products cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:37 +msgid "" +"To enable **optional products** go to :menuselection:`Website --> eCommerce " +"--> Products`, select a product, go to the :guilabel:`Sales` tab, and enter " +"the products you wish to feature in the :guilabel:`Optional Products` field." +" Optional products are **linked** to the product(s) they are set up with on " +"the **product template**. They only appear when that product is added to the" +" cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:43 +msgid "" +"You can also access the :guilabel:`Sales` tab of the **product template** by" +" selecting a product on your **main shop page** and clicking " +":guilabel:`Product` in the top-right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:49 +msgid "Accessory products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:51 +msgid "" +"**Accessory products** are displayed in the :guilabel:`Suggested " +"Accessories` section before processing to checkout at the :guilabel:`Review " +"Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Suggested accessories at checkout during cart review" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:58 +msgid "" +"To enable **accessory products**, go to :menuselection:`Website --> " +"eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, " +"and enter the products you wish to feature in the :guilabel:`Accessory " +"Products` field. Suggested accessory products are **linked** to the " +"product(s) they are set up with on the **product template**. They only " +"appear when that product is at the checkout process review." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:65 +msgid "Upselling" +msgstr "การขายเพิ่มยอด" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:70 +msgid "Alternative products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:72 +msgid "" +"**Alternative products** are suggested on the **product page** and usually " +"incentivize customers to buy a more expensive variant or product than the " +"one they were initially shopping for." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst-1 +msgid "Alternative products on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:79 +msgid "" +"To enable **alternative products**, go to :menuselection:`Website --> " +"eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, " +"and enter the products you wish to feature in the :guilabel:`Alternative " +"Products` field. Then, go to the related **product page** by clicking " +":guilabel:`Go To Website`, and click :menuselection:`Edit`. Stay on the " +":guilabel:`Blocks` tab, and scroll down to the :guilabel:`Dynamic Content` " +"section. Then, drag and drop the :guilabel:`Products` building block " +"anywhere on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:86 +msgid "" +"When placed, in :guilabel:`Edit` mode, click the **block** to access various" +" settings for that :guilabel:`Products` building block. In the " +":guilabel:`Filter` field, select :guilabel:`Alternative Products`. You can " +"configure several additional settings, such as how many elements are " +"displayed (:guilabel:`Fetched Elements`), the :guilabel:`Template` used, " +"etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:3 +msgid "Price management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:5 +msgid "" +"Odoo offers multiple options to select the price displayed on your website, " +"as well as condition-specific prices based on set criteria." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:9 +msgid "Taxes" +msgstr "ภาษี" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:12 +msgid "Tax configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:14 +msgid "" +"To add a tax on a product, you can either set a tax in the " +":guilabel:`Customer Taxes` field of the **product template** or use " +":doc:`fiscal positions " +"</applications/finance/accounting/taxes/fiscal_positions>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:19 +msgid ":doc:`/applications/finance/accounting/taxes`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:20 +msgid ":doc:`/applications/finance/accounting/taxes/avatax`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:21 +msgid ":doc:`/applications/finance/accounting/taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:24 +msgid "Tax display" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:26 +msgid "" +"Choosing the displayed price tax usually depends on a country's regulations " +"or the type of customers **(B2B vs. B2C)**. To select the type of price " +"displayed, go to :menuselection:`Website --> Configuration --> Settings`, " +"scroll down to the :guilabel:`Shop - Products` category, and select " +":guilabel:`Tax Excluded` or :guilabel:`Tax Included`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:31 +msgid "" +":guilabel:`Tax Excluded`: the price displayed on the website is **tax-" +"excluded**, and the tax is computed at the cart-review step;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:33 +msgid "" +":guilabel:`Tax Included`: the price displayed on the website is **tax-" +"included**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:36 +msgid "" +"This setting is **global**, and the tax-display type is the same for (all " +"of) your website(s). It is, therefore, not possible to select different tax " +"displays for different websites. This may be a significant point of " +"consideration when implementing a database with multiple ecommerce websites " +"aimed at varying customer types (i.e., B2B and B2C)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:41 +msgid "" +"You can choose to display the type of pricing next to the product price by " +"going to :menuselection:`Website --> Site --> Homepage --> Shop`, selecting " +"a product, and then :menuselection:`Edit --> Customize tab` and enabling " +":guilabel:`Tax Indication`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Tax type displayed on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:50 +msgid ":doc:`/applications/finance/accounting/taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:53 +msgid "Price per unit" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:55 +msgid "" +"It is possible to display a :doc:`price per unit " +"</applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom>`" +" on the product page. To do that, go to :menuselection:`Website --> " +"Configuration --> Settings` and enable :guilabel:`Product Reference Price` " +"under the :guilabel:`Shop - Products` section. When enabled, ensure an " +"amount is set in the :guilabel:`Base Unit Count` field of the **product " +"template**, and in the :guilabel:`Sales Price`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Cost per unit pricing on the product template" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:66 +msgid "" +"The price per unit of measure can be found above the :guilabel:`Add to Cart`" +" button on the product page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Cost per unit pricing on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:74 +msgid "" +"Pay attention that having the price per unit may be **mandatory** in some " +"countries." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:77 +msgid "" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:82 +msgid "Price configuration: pricelists" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:84 +msgid "" +"Pricelists are the primary tool to manage prices on your eCommerce. They " +"allow you to define website-specific prices - different from the price on " +"the product template - based on the **country group**, **currency**, " +"**minimum quantity**, **period**, or **variant**. You can create as many " +"pricelists as needed, but it is mandatory to have at least one pricelist " +"configured per website. If no custom pricelists are added, Odoo defaults to " +"the **Public Pricelist** for all websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:91 +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:119 +msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:96 +msgid "" +"Pricelists can be found under :menuselection:`Website --> eCommerce --> " +"Pricelists`, but must first be activated. For that, head to " +":menuselection:`Website --> Configuration --> Settings` and scroll down to " +"the :guilabel:`Shop - Products` section. There, you can find two options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:100 +msgid ":guilabel:`Multiple prices per product`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:101 +msgid ":guilabel:`Advanced price rules (discounts, formulas)`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:103 +msgid "" +"The **first** option allows you to set different prices per customer " +"*segment*, i.e., registered customers, gold customers, regular customers, " +"etc. The **second** option allows you to set *price change* rules such as " +"**discounts**, **margins**, **roundings**, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:108 +msgid "Foreign currency" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:110 +msgid "" +"If you are selling in **multiple currencies** and have pricelists in foreign" +" currencies, customers can select their corresponding pricelist anywhere on " +"the :guilabel:`Shop` page from the drop-down menu next to the **search " +"bar**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Pricelists selection" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:120 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:123 +msgid "Permanent discount" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:125 +msgid "" +"If you have permanently reduced the price of a product, a popular means to " +"attract customers is the **strikethrough** strategy. The strategy consists " +"in displaying the previous price crossed out and the **new discounted " +"price** next to it." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst-1 +msgid "Price strikethrough" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:133 +msgid "" +"To display a 'striked' price, enable the :guilabel:`Comparison Price` option" +" under :menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products category`. Then, head to the product's template " +"(:menuselection:`Website --> eCommerce --> Products`), and in the " +":guilabel:`Compare to Price` field, enter the **new** price." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:3 +msgid "Product management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:5 +msgid "" +"Odoo allows you to create, import, and manage your products' pages all " +"within the **Website** app." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:8 +msgid "Add products to the catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:10 +msgid "To add a product to your catalog, you can either do it in:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:12 +msgid "" +"From anywhere on your website, click :menuselection:`+ New --> Product`. " +"Enter the name of your product, and :guilabel:`Save`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:14 +msgid ":menuselection:`Website --> eCommerce --> Products --> Create`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:15 +msgid "" +"or by :ref:`importing data <import-data>` using XLSX or CSV files. To do so," +" go to :menuselection:`Website --> eCommerce --> Products`. Click on " +":guilabel:`Favorites` and :ref:`Import records <import-data>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:21 +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16 +msgid ":doc:`../../../sales/sales/products_prices/products/import`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:22 +msgid ":doc:`Product-related documentation <../../../sales/sales>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:25 +msgid "Publish" +msgstr "เผยแพร่" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:27 +msgid "" +"Upon creation, products are defaulted as :guilabel:`Unpublished` in your " +"eCommerce catalog. To make a product visible to visitors, go to " +":menuselection:`Website --> Site --> Homepage`, click on your **main shop** " +"page, select the product, and enable it as :guilabel:`Published` in the top-" +"right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:33 +msgid "" +"To publish **large batches** of products, the most convenient fashion is to " +"go to :menuselection:`Website --> eCommerce --> Products`. Here, remove the " +":guilabel:`Published` filter by clicking on the :guilabel:`x` right to it, " +"and then select the :guilabel:`List` view. Next, click the " +":guilabel:`dropdown toggle` button (located right below the :guilabel:`List`" +" button) and enable :guilabel:`Is published`. Click the :guilabel:`Is " +"Published` column to re-order it either by **published** or **unpublished** " +"products. Finally, select the products to publish by ticking their box on " +"the extreme-right, and tick any box of the selected products in the " +":guilabel:`Is Published` column to publish them all." +msgstr "" +"หากต้องการเผยแพร่ **ผลิตภัณฑ์จำนวนมาก** วิธีที่สะดวกที่สุดคือไปที่ " +":การเลือกเมนู:`เว็บไซต์ --> อีคอมเมิร์ซ --> ผลิตภัณฑ์` ที่นี่ ลบตัวกรอง " +":guilabel:`เผยแพร่แล้ว` โดยคลิกที่ :guilabel:`x` ทางด้านขวา " +"จากนั้นเลือกมุมมอง :guilabel:`รายการ` จากนั้นคลิกปุ่ม " +":guilabel:`สลับแบบเลื่อนลง` (อยู่ด้านล่างปุ่ม :guilabel:`รายการ`) " +"และเปิดใช้งาน :guilabel:`ได้รับการเผยแพร่` คลิกคอลัมน์ " +":guilabel:`ได้รับการเผยแพร่` เพื่อสั่งซื้อใหม่โดยผลิตภัณฑ์ **เผยแพร่** หรือ " +"**ไม่ได้เผยแพร่** สุดท้าย " +"เลือกผลิตภัณฑ์ที่จะเผยแพร่โดยทำเครื่องหมายที่ช่องขวาสุด " +"และทำเครื่องหมายที่ช่องใดๆ ของผลิตภัณฑ์ที่เลือกในคอลัมน์ " +":guilabel:`เผยแพร่แล้ว` เพื่อเผยแพร่ทั้งหมด" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "List and dropdown toggle buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:47 +msgid "Product page design" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:49 +msgid "" +"Once a product is created, you can access its **product page** through the " +":guilabel:`Shop` page by clicking on the product, and then clicking " +":guilabel:`Edit`. Here, you can change the page's **additional functions**, " +"**layout**, **add content**, etc. Note that **enabled functions** apply to " +"*all* product pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:57 +msgid "Additional functions" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:59 +msgid "" +"In the **website builder** window, click :guilabel:`Customize` to enable " +"additional functions:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:61 +msgid "" +":guilabel:`Customers: Rating` allows customers to submit :ref:`product " +"reviews <product-reviews>`; :guilabel:`Share` adds social media and email " +"icon buttons to share the product via those channels;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:64 +msgid "" +":guilabel:`Select Quantity`: if enabled, allows to choose the quantity added" +" to cart;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:65 +msgid "" +":guilabel:`Tax Indication`: notifies if the price is **VAT included** or " +"**excluded**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:66 +msgid "" +":guilabel:`Variants`: shows all possible :doc:`variants " +"</applications/sales/sales/products_prices/products/variants>` of the " +"product as a :guilabel:`Products List`; :guilabel:`Options` as selectable " +"options to compose the variant yourself;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:70 +msgid "" +":guilabel:`Cart`: :guilabel:`Buy Now` adds a :ref:`checkout button " +"<cart/buy-now>` taking the customer directly to the checkout page; " +":guilabel:`Wishlist` allows to add the product to a wishlist;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:73 +msgid "" +":guilabel:`Specification`: allows you to select where the " +":guilabel:`Specifications` section is displayed. This option displays a list" +" of all variant attributes and values of a product, but only works for " +"products *with* variants." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:78 +msgid "" +"To allow **wishlists**, the option must be enabled in " +":menuselection:`Website --> Configuration --> Settings --> Shop - Products`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:80 +msgid "" +"To access the :guilabel:`Variants` options, the :doc:`Product Variants " +"<../../../sales/sales/products_prices/products/variants>` option must first " +"be enabled under :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Products`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:85 +msgid "Layout" +msgstr "เค้าโครง" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:87 +msgid "" +"Within the same :guilabel:`Customize` tab as the :ref:`functions <ecommerce-" +"functions>`, the layout configuration can be changed according to your " +"needs." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:90 +msgid "" +":guilabel:`Images Width`: changes the width of the product images displayed " +"on the page;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:91 +msgid "" +":guilabel:`Layout`: the :guilabel:`Carousel` layout displays a large, main " +"image with smaller ones underneath; whereas the :guilabel:`Grid` displays " +"four images in a square layout (see pictures below);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:94 +msgid "" +":guilabel:`Image Zoom`: choose which image zooms are available, either " +":guilabel:`Pop-up on Click`, when hovering over the image " +"(:guilabel:`Magnifier on hover`), on :guilabel:`Both`, or :guilabel:`None`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:97 +msgid "" +":guilabel:`Thumbnails`: decide how the thumbnails should be aligned, either " +"**vertically** (:guilabel:`Left`), or **horizontally** (:guilabel:`Right`);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:99 +msgid "" +":guilabel:`Main Image`: click :guilabel:`Replace` to change the product's " +"main image;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:100 +msgid "" +":guilabel:`Extra Images`: click :guilabel:`Add` or :guilabel:`Remove all` to" +" add or remove extra product images. You can also add images and videos via " +"**URL**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:104 +msgid "" +"Images must either be in PNG or JPG format. To trigger the zoom, the image " +"has to be bigger than 1024x1024." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Product images layout" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:114 +msgid "" +"You can use **building blocks** (:menuselection:`Edit --> Blocks`) to add " +"content to your product page. These blocks can be used to add extra text and" +" picture galleries, features such as :guilabel:`Call to Actions`, " +":guilabel:`Comparisons`, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:118 +msgid "" +"Depending on *where* you drop the **building block**, it may be available " +"either on the product page *only*, or on the *whole* website. **Building " +"blocks** dropped at the very top or very bottom of the page are available on" +" the *whole* website, where **building blocks** put underneath the product " +"description are only displayed on the *product* page *(see image below)*." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Building blocks on product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:128 +msgid "Download link" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:130 +msgid "" +"To add a downloadable file (ex.: user's manual, notice of use, etc.) on the " +"product page, drag and drop a :guilabel:`Text` block from " +":menuselection:`Edit --> Blocks` on the page. Once placed, click within the " +":guilabel:`Text` block, and under the :guilabel:`Inline Text` section, " +"select either :menuselection:`Insert Media --> Documents` or " +":guilabel:`Insert or edit link` and enter the URL in the :guilabel:`Your " +"URL` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:137 +msgid "" +"The difference with :ref:`digital files <ecommerce-digital-file>` is that " +"digital files can only be downloaded *after* checkout." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Media and link buttons" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:147 +msgid "Digital files" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:149 +msgid "" +"Should your product be sold with a certificate, manual user, or any other " +"relevant document, it is possible to add a download link for customers at " +"the end of the checkout. To do that, first enable :guilabel:`Digital " +"Content` under :menuselection:`Website --> Configuration --> Settings --> " +"Shop - Checkout Process`. Then, on the **product's template**, click on " +":menuselection:`More --> Digital Files` and :guilabel:`Create` a new file." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Digital Files menu" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:159 +msgid "For the configuration:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:161 +msgid ":guilabel:`Name`: the name of your file;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:162 +msgid "" +":guilabel:`Type:` select if it is either a **file** or a **URL**. " +"Accordingly, you either have a :guilabel:`File Content (base64)` field to " +"upload your file, or a :guilabel:`URL` field to enter your URL." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:165 +msgid "" +":guilabel:`Website`: the website on which that file is *available*. If you " +"want it available for *all* websites, leave it empty." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:168 +msgid "" +"The file is then available after checkout in the **purchase order** section " +"found on the customer's portal." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:172 +msgid "Product configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:175 +msgid "Multiple languages" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:177 +msgid "" +"If multiple languages are available on your website and you wish to have the" +" product's information translated, it is necessary to encode this translated" +" information in the **product's template**. Fields with multiple languages " +"available are identifiable by their abbreviation language (ex. :abbr:`EN " +"(English)`) next to their field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Field translation" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:186 +msgid "The **eCommerce-related** fields to translate are:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:188 +msgid ":guilabel:`Product name`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:189 +msgid ":guilabel:`Out-of-Stock Message` (under the :guilabel:`Sales` tab);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:190 +msgid ":guilabel:`Sales Description` (under the :guilabel:`Sales` tab);" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:193 +msgid "" +"Having untranslated content on a web page may be detrimental to the user " +"experience and :doc:`SEO <../../../websites/website/pages/seo>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:196 +msgid "" +"To check the language(s) of your website, go to :menuselection:`Website --> " +"Configuration --> Settings --> Website Info section`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:200 +msgid ":doc:`../../../websites/website/pages/seo`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:201 +msgid ":ref:`Multi-language support <seo-multilanguage>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:206 +msgid "" +"A product can be set available on either *one* or *all* websites, but it is " +"not possible to select *some* websites and not others. To define a product's" +" availability, go to :menuselection:`Website --> eCommerce --> Products`, " +"select your product, and in the :guilabel:`Sales` tab, click the " +":guilabel:`Website` you wish the product to be available on. Leave the field" +" empty for the products to be available on *all* websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:213 +msgid "Stock management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:215 +msgid "" +"Under the :menuselection:`Website --> Configuration --> Settings --> Shop - " +"Products`, you can enable and configure inventory management options." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:219 +msgid "" +"To display the stock level on the product page, the :guilabel:`Product Type`" +" on the **product's form** must be set to :guilabel:`Storable` (only " +"available when the **Inventory** app is installed)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:224 +msgid "Inventory" +msgstr "คลังสินค้า" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:226 +msgid "" +"In the :guilabel:`Inventory Defaults` sub-section, you can select the " +"eCommerce selling strategy of products:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:229 +msgid "" +":guilabel:`Warehouse`: if you have multiple warehouses, you can define the " +"warehouse associated to your website. If you have multiple websites, you can" +" select a different one per website;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:231 +msgid "" +":guilabel:`Out-of-Stock (Continue Selling)`: enabling it allows customers to" +" continue placing orders even when the product is **out-of-stock**. Leave it" +" unchecked to **prevent orders**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:234 +msgid "" +":guilabel:`Show Available Qty`: enabling it displays the available quantity " +"left under a specified threshold on the product page. The available quantity" +" is calculated based on the 'On hand' quantity minus the quantity already " +"reserved for outgoing transfers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:239 +msgid ":ref:`Allow only selected customers to buy <cart/prevent-sale>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:242 +msgid "Selling as kit" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:244 +msgid "" +"If you are selling non-prepackaged kits (i.e., the kits are made of " +"individual products), we recommend you read the related documentation to " +"keep track of your stock." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:248 +msgid "" +":doc:`../../../inventory_and_mrp/manufacturing/management/kit_shipping`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:251 +msgid "Product comparison" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:253 +msgid "" +"You can enable a **product comparison tool** for your eCommerce by going to " +":menuselection:`Website --> Configuration --> Settings --> Shop - Products`," +" and ticking :guilabel:`Product Comparison Tool`. This tool allows to save " +"products' **specifications** and compare them against each other on a single" +" page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:258 +msgid "" +"On the product page, scroll down to the :guilabel:`Specifications` section " +"and click :guilabel:`Compare`. Repeat the same process for all products you " +"wish to compare. Then, click the :guilabel:`Compare` button of the pop-up " +"window at the bottom of the page to reach the comparison summary." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst:264 +msgid "" +"The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes" +" <variants>` are set on the **product's template**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/products.rst-1 +msgid "Product comparison window" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3 +msgid "Product variants" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5 +msgid "" +"Product variants are variations, such as different colors, materials, etc., " +"of the same product. These variations can differ in price and availability " +"from the product. Product variants can either be :doc:`created " +"<../../../sales/sales/products_prices/products/variants>` or :doc:`imported " +"<../../../sales/sales/products_prices/products/import>`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10 +msgid "" +"To use product variants, enable them under :menuselection:`Website --> " +"Configuration --> Settings`, in the :guilabel:`Shop - Products` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14 +msgid ":doc:`../managing_products/products`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19 +msgid "Product configurator" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:21 +msgid "" +"Adding attributes and values to a product template allows the enabling of " +"the **product configurator** on the product page. Customers use it to " +"configure and select the product variant of their choice; or in the case of " +"multiple attributes, combine those to create a specific variant." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Variants configurator" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:29 +msgid "" +"The **display type** of each attribute used in the product configurator can " +"be edited through the **website builder** by clicking :menuselection:`Edit " +"--> Customize` on the product page, and then clicking on one of the " +"attributes. You can then select between four options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:33 +msgid ":guilabel:`Radio`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:34 +msgid ":guilabel:`Pills`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:35 +msgid ":guilabel:`Select`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:36 +msgid ":guilabel:`Color`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Display type options for attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:44 +msgid "" +"Alternatively, the **display type** can be edited through " +":menuselection:`Website --> eCommerce --> Attributes`, selecting an " +"**attribute**, and then choosing a :guilabel:`Display Type`; or through the " +"**product template** by going to :menuselection:`eCommerce --> Products`, " +"selecting a product, and then clicking :guilabel:`Attributes and Variants`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:50 +msgid "" +"Specific combinations of values can be excluded from the product " +"configurator. This way, customers are unable to select the excluded " +"combination of values. To do so, go to :menuselection:`Website --> eCommerce" +" --> Products`, select a product, and go to :guilabel:`Attributes and " +"Variants`. Then, click on an **attribute**, select a **value**, and in the " +":guilabel:`Exclude for` section, select a :guilabel:`Product Template` and " +"the :guilabel:`Attribute Values` to exclude." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:58 +msgid "Product specifications" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:60 +msgid "" +"Values used for each attribute are displayed as a **specification list** at " +"the bottom of the product page. To be visible, the **specification list** " +"must first be enabled on the product page by going to :menuselection:`Edit " +"--> Customize` and selecting a placement for the field " +":guilabel:`Specification`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Specifications list on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:70 +msgid "" +"The product **specification list** can also be used on products without " +"variants. For that, make sure to have no values combination. Products with " +"single values for their attributes do not generate variants." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75 +msgid "Filter catalog by attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:77 +msgid "" +"Customers **can** filter the **catalog** based on product attributes and " +"values, allowing them to :ref:`filter <ecommerce-browsing>` the catalog " +"based only on the attribute(s) of their choice." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:80 +msgid "" +"To enable **attributes filtering**, go to :menuselection:`Edit --> " +"Customize` from your **main shop page** and click on one of the " +":guilabel:`Categories` in the left column. Here, enable either " +":guilabel:`Left`, :guilabel:`Top`, or **both**, in the " +":guilabel:`Attributes` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/managing_products/variants.rst-1 +msgid "Categories buttons" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:3 +msgid "eLearning" +msgstr "การอบรมออนไลน์" + +#: ../../content/applications/websites/elearning.rst:5 +msgid "" +"The **eLearning** app allows you to easily upload content, define learning " +"objectives, manage attendees, assess students' progress, and even set up " +"rewards. Engaging participants in a meaningful learning experience enhances " +"their attentiveness and fosters heightened productivity." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:10 +msgid "" +"You can manage your eLearning content on the **front end** or the **back " +"end**. The **front end** allows you to create content quickly from your " +"website, while the **back end** provides additional options and allows " +"collaboration. This documentation focuses on using the back end to create " +"your content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:16 +msgid "" +"`Odoo Tutorials: eLearning <https://www.odoo.com/slides/elearning-56>`_" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:19 +msgid "Courses" +msgstr "คอร์ส" + +#: ../../content/applications/websites/elearning.rst:21 +msgid "" +"By going to :menuselection:`eLearning --> Courses --> Courses`, you can get " +"an overview of all your courses." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:24 +msgid "" +"Click on a course title to edit your course on the back end. Click on " +":guilabel:`View course` to access your course on the front end." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:28 +msgid "Course creation" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:30 +msgid "" +"Click :guilabel:`New` to create a new course. When the page pops up, you can" +" add your :guilabel:`Course Title` and one or more :guilabel:`Tags` to " +"describe your course. You can add an image to illustrate your course by " +"hovering your mouse on the camera placeholder image and clicking on the edit" +" icon. Four tabs allow you to edit your course further: :ref:`Content " +"<elearning/content>`, :ref:`Description <elearning/description>`, " +":ref:`Options <elearning/options>`, and :ref:`Karma <elearning/karma>`." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Create your elearning course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:44 +msgid "Content tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:46 +msgid "" +"This tab allows you to manage your course content. Click on :guilabel:`Add " +"Section` to divide your course into different sections. Click on " +":guilabel:`Add Content` to create :ref:`content <elearning/create-content>`." +" Click on :guilabel:`Add Certification` to assess the level of understanding" +" of your attendees, certify their skills, and motivate them. " +"**Certification** is part of the :doc:`Surveys " +"<../marketing/surveys/create>` app." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:55 +#: ../../content/applications/websites/elearning.rst:202 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:57 +msgid "" +"You can add a short description or information related to your course in the" +" :guilabel:`Description` tab. It appears under your course title on your " +"website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Add a description to your course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:67 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:69 +msgid "" +"In the :guilabel:`Options` tab, different configurations are available: " +":ref:`Course <elearning/course>`, :ref:`Communication " +"<elearning/communication>`, :ref:`Access rights <elearning/access-rights>`, " +"and :ref:`Display <elearning/display>`." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Overview of the Options tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:80 +msgid "Course" +msgstr "คอร์ส" + +#: ../../content/applications/websites/elearning.rst:82 +msgid "" +"Assign a :guilabel:`Responsible` user for your course. If you have multiple " +"websites, use the :guilabel:`Website` field to only display the course on " +"the selected website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:88 +msgid "Communication" +msgstr "การติดต่อสื่อสาร" + +#: ../../content/applications/websites/elearning.rst:90 +msgid "" +":guilabel:`Allow Reviews`: tick the box to allow attendees to like and " +"comment on your content and to submit reviews on your course;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:92 +msgid "" +":guilabel:`Forum`: add a dedicated forum to your course (only shown if the " +"**Forum** feature is enabled in the app's settings);" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:94 +msgid "" +":guilabel:`New Content Notification`: select an email template sent to your " +"attendees when you upload new content. Click on the internal link button " +"(:guilabel:`➜`) to have access to the email template editor;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:97 +msgid "" +":guilabel:`Completion Notification`: select an email template sent to your " +"attendees once they reach the end of your course. Click on the internal link" +" button (:guilabel:`➜`) to access the email template editor;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:104 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:106 +msgid "" +":guilabel:`Show course to`: define who can access your course and their " +"content between :guilabel:`Everyone`, :guilabel:`Signed In` or " +":guilabel:`Course Attendees`;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:108 +msgid "" +":guilabel:`Enroll Policy`: define how people enroll in your course. Select:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:110 +msgid ":guilabel:`Open`: if you want your course to be available to anyone;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:111 +msgid "" +":guilabel:`On Invitation`: if only people who received an invitation can " +"enroll to your course. If selected, fill in the :guilabel:`Enroll Message` " +"explaining the course's enrollment process. This message appears on your " +"website under the course title;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:114 +msgid "" +":guilabel:`On Payment`: if only people who bought your course can attend it." +" The :guilabel:`Paid Courses` feature must be enabled to get this option. If" +" you select :guilabel:`On Payment`, you must add a :guilabel:`Product` for " +"your course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:119 +msgid "" +"Only products set up with :guilabel:`Course` as their :guilabel:`Product " +"Type` are displayed." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:125 +msgid "Display" +msgstr "แสดง" + +#: ../../content/applications/websites/elearning.rst:127 +msgid "" +":guilabel:`Training`: the course content appears as a training program, and " +"the courses must be taken in the proposed order." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:129 +msgid "" +":guilabel:`Documentation`: the content is available in any order. If you " +"choose this option, you can choose which page should be promoted on the " +"course homepage by using the :guilabel:`Featured Content` field." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:136 +msgid "Karma tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:138 +msgid "This tab is about gamification to make eLearning fun and interactive." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:140 +msgid "" +"In the :guilabel:`Rewards` section, choose how many karma points you want to" +" grant your students when they :guilabel:`Review` or :guilabel:`Finish` a " +"course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:143 +msgid "" +"In the :guilabel:`Access Rights` section, define the karma needed to " +":guilabel:`Add Review`, :guilabel:`Add Comment`, or :guilabel:`Vote` on the " +"course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:147 +msgid "" +"From your course, click the :guilabel:`Contact Attendees` button to reach " +"people who are enrolled in the course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:153 +msgid "Course groups" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:155 +msgid "" +"Use the **Course Groups** to inform users and allow them to filter the " +"courses from the :guilabel:`All Courses` dashboard." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:158 +msgid "" +"You can manage them by going to :menuselection:`Configuration --> Course " +"Groups`. Click :guilabel:`New` to create a new course group. Add the " +":guilabel:`Course Group Name`, tick the :guilabel:`Menu Entry` box to allow " +"users to search by course group on the website, and add tags in the " +":guilabel:`Tag Name` column. For each tag, you can select a corresponding " +"color." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:164 +msgid "Settings" +msgstr "การตั้งค่า" + +#: ../../content/applications/websites/elearning.rst:166 +msgid "" +"You can enable different features to customize your courses by going to " +":menuselection:`eLearning --> Configuration --> Settings`:" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:169 +msgid "" +"**Certifications**: to evaluate the knowledge of your attendees and certify " +"their skills;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:170 +msgid "" +"**Paid courses**: to sell access to your courses on your website and track " +"revenues;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:171 +msgid "" +"**Mailing**: to update all your attendees at once through mass mailings;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:172 +msgid "" +"**Forum**: to create a community and let attendees answer each other's " +"questions." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:177 +msgid "Content" +msgstr "เนื้อหา" + +#: ../../content/applications/websites/elearning.rst:179 +msgid "" +"Manage your content by going to :menuselection:`eLearning --> Courses --> " +"Contents`. Click :guilabel:`New` to create content. Add your " +":guilabel:`Content Title`, and if you want :ref:`Tags <elearning/tags>`, " +"then fill in the related information among the different tabs." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Create your content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:188 +msgid "Document tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:190 +msgid ":guilabel:`Course`: select the course your content belongs to;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:191 +msgid ":guilabel:`Content Type`: select the type of your content;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:192 +msgid ":guilabel:`Responsible`: add a responsible person for your content;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:193 +msgid "" +":guilabel:`Duration`: indicate the time required to complete the course;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:194 +msgid "" +":guilabel:`Allow Download`: allow users to download the content of the " +"slide. This option is only visible when the content is a document;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:196 +msgid ":guilabel:`Allow Preview`: the course is accessible by anyone." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:197 +msgid "" +":guilabel:`# of Public Views`: displays the number of views from non-" +"enrolled participants;" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:198 +msgid "" +":guilabel:`# Total Views`: displays the total number of views (non-enrolled " +"and enrolled participants)." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:204 +msgid "" +"You can add a description of your content that appears front end in the " +":guilabel:`About` section of your course content." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:208 +msgid "Additional Resources tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:210 +msgid "" +"Click :guilabel:`Add a line` to add a link or a file that supports your " +"participants' learning. It appears in the course content on your website." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Additional ressources" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:220 +msgid "Quiz tab" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:222 +msgid "" +"From this tab you can create a quiz to assess your students at the end of " +"the course." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:224 +msgid "" +"The :guilabel:`Points Rewards` section lets you give a specific number of " +"karma points depending on how many tries they need to correctly answer the " +"question. Then, create your questions and the possible answers by clicking " +"on :guilabel:`Add a line`. A new window pops up, add the question by filling" +" in the :guilabel:`Question Name` and add multiple answers by clicking on " +":guilabel:`Add a line`. Tick the :guilabel:`Is correct answer` to mark one " +"or more answers as correct. You can also fill in the :guilabel:`Comment` " +"field to display additional information when the answer is chosen by the " +"participant." +msgstr "" +"ส่วน :guilabel:`คะแนนรางวัล` ช่วยให้คุณสามารถให้คะแนนกรรมตามจำนวนที่กำหนด " +"โดยขึ้นอยู่กับจำนวนครั้งที่พวกเขาต้องพยายามตอบคำถามให้ถูกต้อง จากนั้น " +"สร้างคำถามและคำตอบที่เป็นไปได้โดยคลิกที่ :guilabel:`เพิ่มบรรทัด` " +"หน้าต่างใหม่จะปรากฏขึ้น เพิ่มคำถามโดยกรอก :guilabel:`ชื่อคำถาม` " +"และเพิ่มหลายคำตอบโดยคลิกที่ :guilabel:`เพิ่มบรรทัด` ทำเครื่องหมายที่ " +":guilabel:`เป็นคำตอบที่ถูกต้อง` " +"เพื่อทำเครื่องหมายคำตอบอย่างน้อยหนึ่งข้อว่าถูกต้อง " +"คุณยังสามารถกรอกข้อมูลในช่อง :guilabel:`ความคิดเห็น` " +"เพื่อแสดงข้อมูลเพิ่มเติมเมื่อผู้เข้าร่วมเลือกคำตอบ" + +#: ../../content/applications/websites/elearning.rst:235 +msgid "Content Tags" +msgstr "แท็กเนื้อหา" + +#: ../../content/applications/websites/elearning.rst:237 +msgid "" +"The **Content Tags** help users to classify the content from the " +":guilabel:`Contents` dashboard." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:239 +msgid "" +"You can manage them by going to :menuselection:`eLearning --> Configuration " +"--> Content Tags`. Click :guilabel:`New` to create a new tag." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:243 +msgid "Publish your content" +msgstr "" + +#: ../../content/applications/websites/elearning.rst:245 +msgid "" +"Everything created on the back end needs to be published from the front end." +" Unpublished content is always visible from your website but still needs to " +"be published to be available to your audience." +msgstr "" + +#: ../../content/applications/websites/elearning.rst:248 +msgid "" +"You must be on your website's front end to publish your content. To do so, " +"click on the :guilabel:`Go To Website` smart button, and tick the " +":guilabel:`Publish` option available in the right-hand corner." +msgstr "" + +#: ../../content/applications/websites/elearning.rst-1 +msgid "Publish your content." +msgstr "" + +#: ../../content/applications/websites/forum.rst:3 +msgid "Forum" +msgstr "ฟอรั่ม" + +#: ../../content/applications/websites/forum.rst:5 +msgid "" +"**Odoo Forum** is a question-and-answer forum designed with providing " +"customer support in mind. Adding a forum to a website enables you to build a" +" community, encourage engagement, and share knowledge." +msgstr "" + +#: ../../content/applications/websites/forum.rst:12 +msgid "Create a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:14 +msgid "" +"To create or edit a forum, go to :menuselection:`Website --> Configuration " +"--> Forum: Forums`. Click :guilabel:`New` or select an existing forum and " +"configure the following elements." +msgstr "" + +#: ../../content/applications/websites/forum.rst:17 +msgid ":guilabel:`Forum Name`: add the name of the forum." +msgstr "" + +#: ../../content/applications/websites/forum.rst:19 +msgid "" +":guilabel:`Mode`: select :guilabel:`Questions` to enable marking an answer " +"as best, meaning questions then appear as *solved*, or " +":guilabel:`Discussions` if the feature is not needed." +msgstr "" + +#: ../../content/applications/websites/forum.rst:23 +msgid "" +"Regardless of the selected mode, only **one answer** per user is allowed on " +"a single post. Commenting multiple times is allowed, however." +msgstr "" + +#: ../../content/applications/websites/forum.rst:26 +msgid ":guilabel:`Default Sort`: choose how questions are sorted by default." +msgstr "" + +#: ../../content/applications/websites/forum.rst:28 +msgid ":guilabel:`Newest`: by latest question posting date" +msgstr "" + +#: ../../content/applications/websites/forum.rst:29 +msgid "" +":guilabel:`Last Updated`: by latest posting activity date (answers and " +"comments included)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:30 +msgid ":guilabel:`Most Voted`: by highest vote tally" +msgstr "" + +#: ../../content/applications/websites/forum.rst:31 +msgid ":guilabel:`Relevance`: by post relevancy (determined by a formula)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:32 +msgid "" +":guilabel:`Answered`: by likelihood to be answered (determined by a formula)" +msgstr "" + +#: ../../content/applications/websites/forum.rst:35 +msgid "" +"Users have several sorting options (total replies, total views, last " +"activity) on the forum front end." +msgstr "" + +#: ../../content/applications/websites/forum.rst:38 +msgid "" +":guilabel:`Privacy`: select :guilabel:`Public` to let anyone view the forum," +" :guilabel:`Signed In` to make it visible only for signed-in users, or " +":guilabel:`Some users` to make it visible only for a specific user access " +"group by selecting one :guilabel:`Authorized Group`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:42 +msgid "" +"Next, configure the :ref:`karma gains <forum/karma-gains>` and the " +":ref:`karma-related rights <forum/karma-related-rights>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:48 +msgid "Karma points" +msgstr "" + +#: ../../content/applications/websites/forum.rst:50 +msgid "" +"Karma points can be given to users based on different forum interactions. " +"They can be used to determine which forum functionalities users can access, " +"from being able to vote on posts to having moderator rights. They are also " +"used to set user :ref:`ranks <forum/ranks>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:55 +msgid "" +"A user's karma points are shared across all forums, courses, etc., of a " +"single Odoo website." +msgstr "" + +#: ../../content/applications/websites/forum.rst:56 +msgid "" +"eLearning users can earn karma points through different :ref:`course " +"interactions <elearning/karma>` and by :ref:`completing quizzes " +"<elearning/quiz>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:62 +msgid "Karma gains" +msgstr "" + +#: ../../content/applications/websites/forum.rst:64 +msgid "Several forum interactions can give or remove karma points." +msgstr "" + +#: ../../content/applications/websites/forum.rst:70 +msgid "Interaction" +msgstr "" + +#: ../../content/applications/websites/forum.rst:71 +#: ../../content/applications/websites/forum.rst:129 +msgid "Description" +msgstr "คำอธิบาย" + +#: ../../content/applications/websites/forum.rst:72 +msgid "Default karma gain" +msgstr "" + +#: ../../content/applications/websites/forum.rst:73 +msgid ":guilabel:`Asking a question`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:74 +msgid "You post a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:75 +#: ../../content/applications/websites/forum.rst:90 +msgid "2" +msgstr "" + +#: ../../content/applications/websites/forum.rst:76 +msgid ":guilabel:`Question upvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:77 +msgid "Another user votes for a question you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:78 +#: ../../content/applications/websites/forum.rst:139 +msgid "5" +msgstr "" + +#: ../../content/applications/websites/forum.rst:79 +msgid ":guilabel:`Question downvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:80 +msgid "Another user votes against a question you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:81 +#: ../../content/applications/websites/forum.rst:87 +msgid "-2" +msgstr "" + +#: ../../content/applications/websites/forum.rst:82 +msgid ":guilabel:`Answer upvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:83 +msgid "Another user votes for an answer you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:84 +msgid "10" +msgstr "10" + +#: ../../content/applications/websites/forum.rst:85 +msgid ":guilabel:`Answer downvoted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:86 +msgid "Another user votes against an answer you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:88 +msgid ":guilabel:`Accepting an answer`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:89 +msgid "You mark an answer posted by another user as best." +msgstr "" + +#: ../../content/applications/websites/forum.rst:91 +msgid ":guilabel:`Answer accepted`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:92 +msgid "Another user marks an answer you posted as best." +msgstr "" + +#: ../../content/applications/websites/forum.rst:93 +msgid "15" +msgstr "" + +#: ../../content/applications/websites/forum.rst:94 +msgid ":guilabel:`Answer flagged`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:95 +msgid "" +"A question or an answer you posted is :ref:`marked as offensive " +"<forum/moderation>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:96 +msgid "-100" +msgstr "" + +#: ../../content/applications/websites/forum.rst:99 +msgid "" +"New users receive **three points** upon validating their email address." +msgstr "" + +#: ../../content/applications/websites/forum.rst:101 +msgid "" +"To modify the default values, go to :menuselection:`Website --> " +"Configuration --> Forum: Forums`, select the forum, and go to the " +":guilabel:`Karma Gains` tab. Select a value to edit it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:104 +msgid "" +"If the value is positive (e.g., `5`), the number of points will be added to " +"the user's tally each time the interaction happens on the selected forum. " +"Conversely, if the value is negative (e.g., `-5`), the number of points will" +" be deducted. Use `0` if an interaction should not impact a user's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst:112 +msgid "Karma-related rights" +msgstr "" + +#: ../../content/applications/websites/forum.rst:114 +msgid "" +"To configure how many karma points are required to access the different " +"forum functionalities, go to :menuselection:`Website --> Configuration --> " +"Forum: Forums`, select the forum, and go to the :guilabel:`Karma Related " +"Rights` tab. Select a value to edit it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:119 +msgid "" +"Some functionalities, such as :guilabel:`Edit all posts`, :guilabel:`Close " +"all posts`, :guilabel:`Delete all posts`, :guilabel:`Moderate posts`, and " +":guilabel:`Unlink all comments`, are rather sensitive. Make sure to " +"understand the consequences of giving *any* user reaching the set karma " +"requirements access to such functionalities." +msgstr "" + +#: ../../content/applications/websites/forum.rst:128 +msgid "Functionality" +msgstr "" + +#: ../../content/applications/websites/forum.rst:130 +msgid "Default karma requirement" +msgstr "" + +#: ../../content/applications/websites/forum.rst:131 +msgid ":guilabel:`Ask questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:132 +msgid "Post questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:133 +#: ../../content/applications/websites/forum.rst:136 +msgid "3" +msgstr "" + +#: ../../content/applications/websites/forum.rst:134 +msgid ":guilabel:`Answer questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:135 +msgid "Post answers to questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:137 +msgid ":guilabel:`Upvote`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:138 +msgid "Vote for questions or answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:140 +msgid ":guilabel:`Downvote`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:141 +msgid "Vote against questions or answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:142 +#: ../../content/applications/websites/forum.rst:182 +#: ../../content/applications/websites/forum.rst:188 +msgid "50" +msgstr "50" + +#: ../../content/applications/websites/forum.rst:143 +msgid ":guilabel:`Edit own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:144 +msgid "Edit questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:145 +#: ../../content/applications/websites/forum.rst:176 +#: ../../content/applications/websites/forum.rst:179 +msgid "1" +msgstr "" + +#: ../../content/applications/websites/forum.rst:146 +msgid ":guilabel:`Edit all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:147 +msgid "Edit any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:148 +msgid "300" +msgstr "" + +#: ../../content/applications/websites/forum.rst:149 +msgid ":guilabel:`Close own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:150 +msgid "Close questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:151 +#: ../../content/applications/websites/forum.rst:194 +msgid "100" +msgstr "100" + +#: ../../content/applications/websites/forum.rst:152 +msgid ":guilabel:`Close all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:153 +msgid "Close any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:154 +#: ../../content/applications/websites/forum.rst:157 +#: ../../content/applications/websites/forum.rst:164 +#: ../../content/applications/websites/forum.rst:170 +#: ../../content/applications/websites/forum.rst:185 +#: ../../content/applications/websites/forum.rst:191 +#: ../../content/applications/websites/forum.rst:197 +msgid "500" +msgstr "" + +#: ../../content/applications/websites/forum.rst:155 +msgid ":guilabel:`Delete own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:156 +msgid "Delete questions or answers you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:158 +msgid ":guilabel:`Delete all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:159 +msgid "Delete any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:160 +#: ../../content/applications/websites/forum.rst:200 +msgid "1,000" +msgstr "" + +#: ../../content/applications/websites/forum.rst:161 +msgid ":guilabel:`Nofollow links`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:162 +msgid "" +"If you are under the karma threshold, a *nofollow* attribute tells search " +"engines to ignore links you post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:165 +msgid ":guilabel:`Accept an answer on own questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:166 +msgid "Mark an answer as best on questions you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:167 +msgid "20" +msgstr "20" + +#: ../../content/applications/websites/forum.rst:168 +msgid ":guilabel:`Accept an answer to all questions`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:169 +msgid "Mark an answer as best on any question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:171 +msgid ":guilabel:`Editor Features: image and links`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:172 +msgid "Add links and images to your posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:173 +#: ../../content/applications/websites/forum.rst:206 +msgid "30" +msgstr "30" + +#: ../../content/applications/websites/forum.rst:174 +msgid ":guilabel:`Comment own posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:175 +msgid "Post comments under questions or answers you created." +msgstr "" + +#: ../../content/applications/websites/forum.rst:177 +msgid ":guilabel:`Comment all posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:178 +msgid "Post comments under any question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:180 +msgid ":guilabel:`Convert own answers to comments and vice versa`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:181 +msgid "Convert comments you posted as answers." +msgstr "" + +#: ../../content/applications/websites/forum.rst:183 +msgid ":guilabel:`Convert all answers to comments and vice versa`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:184 +msgid "Convert any comment as answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:186 +msgid ":guilabel:`Unlink own comments`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:187 +msgid "Delete comments you posted." +msgstr "" + +#: ../../content/applications/websites/forum.rst:189 +msgid ":guilabel:`Unlink all comments`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:190 +msgid "Delete any comment." +msgstr "" + +#: ../../content/applications/websites/forum.rst:192 +msgid ":guilabel:`Ask questions without validation`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:193 +msgid "" +"Questions you post do not require to be :ref:`validated <forum/moderation>` " +"first." +msgstr "" + +#: ../../content/applications/websites/forum.rst:195 +msgid ":guilabel:`Flag a post as offensive`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:196 +msgid "Flag a question or answer as offensive." +msgstr "" + +#: ../../content/applications/websites/forum.rst:198 +msgid ":guilabel:`Moderate posts`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:199 +msgid "Access all :ref:`moderation tools <forum/moderation>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:201 +msgid ":guilabel:`Change question tags`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:202 +msgid "" +"Change posted questions' :ref:`tags <forum/tags>` (if you have the right to " +"edit them)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:203 +msgid "75" +msgstr "" + +#: ../../content/applications/websites/forum.rst:204 +msgid ":guilabel:`Create new tags`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:205 +msgid "Create new :ref:`tags <forum/tags>` when posting questions." +msgstr "" + +#: ../../content/applications/websites/forum.rst:207 +msgid ":guilabel:`Display detailed user biography`" +msgstr "" + +#: ../../content/applications/websites/forum.rst:208 +msgid "" +"When a user hovers their mouse on your avatar or username, a popover box " +"showcases your karma points, biography, and number of :ref:`badges " +"<forum/badges>` per level." +msgstr "" + +#: ../../content/applications/websites/forum.rst:210 +msgid "750" +msgstr "" + +#: ../../content/applications/websites/forum.rst:213 +msgid "" +"Track all karma-related activity and add or remove karma manually by " +":ref:`enabling developer mode <developer-mode>` and going to " +":menuselection:`Settings --> Gamification Tools --> Karma Tracking`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:220 +msgid "Gamification" +msgstr "การเล่นเกม" + +#: ../../content/applications/websites/forum.rst:222 +msgid "" +"Ranks and badges can be used to encourage participation. Ranks are based on " +"the total :ref:`karma points <forum/karma>`, while badges can be granted " +"manually or automatically by completing challenges." +msgstr "" + +#: ../../content/applications/websites/forum.rst:229 +msgid "Ranks" +msgstr "อันดับ" + +#: ../../content/applications/websites/forum.rst:231 +msgid "" +"To create new ranks or modify the default ones, go to " +":menuselection:`Website --> Configuration --> Forum: Ranks` and click " +":guilabel:`New` or select an existing rank." +msgstr "" + +#: ../../content/applications/websites/forum.rst:234 +msgid "" +"Add the :guilabel:`Rank Name`, the :guilabel:`Required Karma` points to " +"reach it, its :guilabel:`Description`, a :guilabel:`Motivational` message to" +" encourage users to reach it, and an image." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Default forum ranks" +msgstr "" + +#: ../../content/applications/websites/forum.rst:244 +msgid "Badges" +msgstr "เหรียญรางวัล" + +#: ../../content/applications/websites/forum.rst:246 +msgid "" +"To create new badges or modify the default ones, go to " +":menuselection:`Website --> Configuration --> Forum: Badges` and click " +":guilabel:`New` or select an existing badge." +msgstr "" + +#: ../../content/applications/websites/forum.rst:249 +msgid "Enter the badge name and description, add an image, and configure it." +msgstr "" + +#: ../../content/applications/websites/forum.rst:252 +msgid "Assign manually" +msgstr "" + +#: ../../content/applications/websites/forum.rst:254 +msgid "" +"If the badge should be granted manually, select which users can grant them " +"by selecting one of the following :guilabel:`Allowance to Grant` options:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:257 +msgid "" +":guilabel:`Everyone`: all non-portal users (since badges are granted from " +"the backend)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:258 +msgid "" +":guilabel:`A selected list of users`: users selected under " +":guilabel:`Authorized Users`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:259 +msgid "" +":guilabel:`People having some badges`: users who have been granted the " +"badges selected under :guilabel:`Required Badges`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:262 +msgid "" +"It is possible to restrict how many times per month each user can grant the " +"badge by enabling :guilabel:`Monthly Limited Sending` and entering a " +":guilabel:`Limitation Number`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:266 +msgid "Assign automatically" +msgstr "" + +#: ../../content/applications/websites/forum.rst:268 +msgid "" +"If the badge should be granted **automatically** when certain conditions are" +" met, select :guilabel:`No one, assigned through challenges` under " +":guilabel:`Allowance to Grant`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:271 +msgid "" +"Next, determine how the badge should be granted by clicking :guilabel:`Add` " +"under the :guilabel:`Rewards for challenges` section. Select a challenge to " +"add it or create one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:276 +msgid "" +"It is possible to give the badge a :guilabel:`Forum Badge Level` " +"(:guilabel:`Bronze`, :guilabel:`Silver`, :guilabel:`Gold`) to give it more " +"or less importance." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Default forum badges" +msgstr "" + +#: ../../content/applications/websites/forum.rst:285 +msgid "Tags" +msgstr "แท็ก" + +#: ../../content/applications/websites/forum.rst:287 +msgid "Users can use tags to filter forum posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:289 +msgid "" +"To manage tags, go to :menuselection:`Website --> Configuration --> Forum: " +"Tags`. Click :guilabel:`New` to create a tag and select the related " +":guilabel:`Forum`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:293 +msgid "" +"Use the :guilabel:`Tags` section on the forum's sidebar to filter all " +"questions assigned to the selected tag. Click :guilabel:`View all` to " +"display all tags." +msgstr "" + +#: ../../content/applications/websites/forum.rst:295 +msgid "" +"New tags can be created when posting a new message, provided the user has " +"enough :ref:`karma points <forum/karma-related-rights>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:301 +msgid "Use a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:304 +msgid "" +"Access to many functionalities depends on a user's :ref:`karma points " +"<forum/karma-related-rights>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:310 +msgid "Post questions" +msgstr "" + +#: ../../content/applications/websites/forum.rst:312 +msgid "" +"To create a new post, access the forum's front end, click :guilabel:`New " +"Post`, and fill in the following:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:315 +msgid ":guilabel:`Title`: add the question or the topic of the post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:316 +msgid ":guilabel:`Description`: add a description for the question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:317 +msgid ":guilabel:`Tags`: add up to five :ref:`tags <forum/tags>`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:319 +msgid "Click :guilabel:`Post Your Question`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:324 +msgid "Interact with posts" +msgstr "" + +#: ../../content/applications/websites/forum.rst:326 +msgid "Different actions are possible on a post." +msgstr "" + +#: ../../content/applications/websites/forum.rst:328 +msgid "" +"Mark a question as **favorite** by clicking the star button (:guilabel:`☆`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:329 +msgid "" +"Follow a post and get **notifications** (by email or within Odoo) when it is" +" answered by clicking the bell button (:guilabel:`🔔`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:331 +msgid "" +"**Vote** *for* (up arrow :guilabel:`▲`) or *against* (down arrow " +":guilabel:`▼`) a question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:333 +msgid "" +"Mark an answer as **best** by clicking the check mark button " +"(:guilabel:`✔`). This option is only available if the :guilabel:`Forum Mode`" +" is set to :guilabel:`Questions`." +msgstr "" + +#: ../../content/applications/websites/forum.rst:335 +msgid ":guilabel:`Answer` a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:336 +msgid "" +"**Comment** on a question or answer by clicking the speech bubble button " +"(:guilabel:`💬`)." +msgstr "" + +#: ../../content/applications/websites/forum.rst:337 +msgid "" +"**Share** a question on Facebook, Twitter, or LinkedIn by clicking the " +"*share nodes* button." +msgstr "" + +#: ../../content/applications/websites/forum.rst:339 +msgid "Click the ellipsis button (:guilabel:`...`) to:" +msgstr "" + +#: ../../content/applications/websites/forum.rst:341 +msgid ":guilabel:`Edit` a question or answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:342 +msgid ":guilabel:`Close` a question." +msgstr "" + +#: ../../content/applications/websites/forum.rst:343 +msgid "" +":guilabel:`Delete` a question, answer, or comment. It is possible to " +":guilabel:`Undelete` questions afterward." +msgstr "" + +#: ../../content/applications/websites/forum.rst:345 +msgid ":guilabel:`Flag` a question or answer as offensive." +msgstr "" + +#: ../../content/applications/websites/forum.rst:346 +msgid ":guilabel:`Convert` a comment into an answer." +msgstr "" + +#: ../../content/applications/websites/forum.rst:347 +msgid "" +":guilabel:`View` the related :ref:`Helpdesk ticket <helpdesk/forum>`, if " +"any." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Posts actions" +msgstr "" + +#: ../../content/applications/websites/forum.rst:353 +msgid "" +"By default, 150 karma points are required to view another user's profile. " +"This value can be configured when creating a new website." +msgstr "" + +#: ../../content/applications/websites/forum.rst:359 +msgid "Moderate a forum" +msgstr "" + +#: ../../content/applications/websites/forum.rst:361 +msgid "" +"On the forum's front end, the sidebar's :guilabel:`Moderation tools` section" +" gathers the essential moderator functionalities." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Forum sidebar moderation tools" +msgstr "" + +#: ../../content/applications/websites/forum.rst:367 +msgid "" +":guilabel:`To Validate`: access all questions and answers waiting for " +"validation before being displayed to non-moderator users." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Question to validate" +msgstr "" + +#: ../../content/applications/websites/forum.rst:374 +msgid "" +"A question is pending if a user does not have the required karma. The user " +"is not able to post questions or answers while awaiting validation. Only one" +" pending question per user is allowed per forum." +msgstr "" + +#: ../../content/applications/websites/forum.rst:378 +msgid "" +":guilabel:`Flagged`: access all questions and answers that have been flagged" +" as offensive. Click :guilabel:`Accept` to remove the offensive flag or " +":guilabel:`Offensive` to confirm it, then select a reason and click " +":guilabel:`Mark as offensive`. The post is then hidden from users without " +"moderation rights, and 100 karma points are deducted from the offending " +"user's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst-1 +msgid "Offensive reason selection" +msgstr "" + +#: ../../content/applications/websites/forum.rst:386 +msgid "" +":guilabel:`Closed`: access all questions that have been closed. It is " +"possible to :guilabel:`Delete` or :guilabel:`Reopen` them. To close a " +"question, open it, click the ellipsis button (:guilabel:`...`), then " +":guilabel:`Close`, select a :guilabel:`Close Reason`, and click " +":guilabel:`Close post`. The post is then hidden from users without " +"moderation rights." +msgstr "" + +#: ../../content/applications/websites/forum.rst:392 +msgid "" +"When selecting :guilabel:`Spam or advertising` or :guilabel:`Contains " +"offensive or malicious remarks` as the reason, 100 karma points are deducted" +" from the poster's tally." +msgstr "" + +#: ../../content/applications/websites/forum.rst:396 +msgid "" +"Create and edit close reasons by going to :menuselection:`Website --> " +"Configuration --> Forum: Close Reasons`. Select :guilabel:`Basic` as " +":guilabel:`Reason Type` if the reason should be used when closing a " +"question, and :guilabel:`Offensive` if it should be used for flagged posts." +msgstr "" + +#: ../../content/applications/websites/forum.rst:399 +msgid "" +"Manage all posts by going to :menuselection:`Website --> Configuration --> " +"Forum: Forums`, selecting the forum, and clicking the :guilabel:`Posts` " +"smart button. By clicking the :guilabel:`Actions` button, it is possible to " +":guilabel:`Export`, :guilabel:`Archive`, :guilabel:`Unarchive`, or " +":guilabel:`Delete` one or multiple posts." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:6 +msgid "Live Chat" +msgstr "ไลฟ์แชท" + +#: ../../content/applications/websites/livechat.rst:8 +msgid "" +"Odoo *Live Chat* allows users to communicate with website visitors in real " +"time. With *Live Chat*, leads can be qualified for their sales potential, " +"support questions can be answered quickly, and issues can be directed to the" +" appropriate team for further investigation (or follow up). *Live Chat* also" +" provides the opportunity for instant feedback from customers." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:14 +msgid "Enable Live Chat" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:16 +msgid "" +"In order to enable *Live Chat*, the *Live Chat* application needs to be " +"installed. This can be done in one of two ways." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:19 +msgid "" +"Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:20 +msgid "" +"In the :menuselection:`Website` application, go to " +":menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email " +"& Marketing` section, check the box next to :guilabel:`Livechat`, and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of the settings page and the live chat feature for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:28 +msgid "" +"After the :guilabel:`Live Chat` application is installed, a live chat " +":guilabel:`Channel` will be created by default and automatically selected in" +" the drop-down." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:32 +msgid "Create a new live chat channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:34 +msgid "" +"To create a new live chat *Channel*, go to :menuselection:`Main Odoo " +"Dashboard --> Live Chat app --> New`. This will open a blank channel detail " +"form. Enter the name of the new channel in the :guilabel:`Channel Name` " +"field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a live chat channel form for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:42 +msgid "" +"To configure the remaining tabs on the channel detail form " +"(:guilabel:`Operators`, :guilabel:`Options`, :guilabel:`Channel Rules`, and " +":guilabel:`Widgets`), follow the steps below." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:46 +msgid "Operators" +msgstr "ตัวดำเนินการ" + +#: ../../content/applications/websites/livechat.rst:48 +msgid "" +"*Operators* are the users who will respond to live chat requests from " +"customers. When a user is added as an operator in a live chat channel, they " +"will be able to receive chats from website visitors wherever they are in the" +" database. Chat windows will open in the bottom right corner of the screen." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a live chat pop up window in an Odoo database." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:57 +msgid "" +"The user who originally created the live chat channel will be added as an " +"operator by default." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:59 +msgid "" +"To add additional users, navigate back to the :guilabel:`Website Live Chat " +"Channels` dashboard via the breadcrumbs and click on the appropriate " +":guilabel:`Live Chat Channel`. Then, on the channel detail form, under the " +":guilabel:`Operators` tab, click :guilabel:`ADD` to reveal an " +":guilabel:`Add: Operators` pop-up window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:64 +msgid "" +"In the pop-up window, search for the desired user(s). Then, click the " +"checkbox next to the user(s) to be added, and click :guilabel:`SELECT`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:67 +msgid "" +"New operators can be created and added to the list directly from this pop-" +"up, as well, by clicking :guilabel:`New`, and filling out the " +":guilabel:`Create Operators` pop-up form. When the form is complete, click " +":guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiple record " +"creations)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:72 +msgid "" +"Current operators can be edited (or removed) by clicking on their respective" +" boxes in the :guilabel:`Operators` tab, which reveals a separate " +":guilabel:`Open: Operators` pop-up. In that pop-up, adjust any information " +"as needed, and click :guilabel:`Save`, or click :guilabel:`Remove` to remove" +" that operator from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:78 +msgid "Options" +msgstr "ตัวเลือก" + +#: ../../content/applications/websites/livechat.rst:80 +msgid "" +"The :guilabel:`Options` tab on the live chat channel details form contains " +"the visual and text settings for the live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:84 +msgid "Livechat button" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:86 +msgid "" +"The *Livechat Button* is the icon that appears in the bottom corner of the " +"website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of an Odoo website emphasizing the livechat button." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:92 +msgid "" +"Change the text in the :guilabel:`Text of the Button` field to update the " +"greeting displayed in the text bubble when the live chat button appears on " +"the website." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:95 +msgid "" +"Change the :guilabel:`Livechat Button Color` by clicking a color bubble to " +"open the color selection window. Click the :guilabel:`🔄 (refresh)` icon to " +"the right of the color bubbles to reset the colors to the default selection." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:100 +msgid "" +"Color selection, for the button or header, can be made manually using a " +"slider or through RGB, HSL, or HEX color code entries from the pop-up color " +"selection window that appears when either of the color bubbles are clicked. " +"Different options will be available, depending on your operating system." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:106 +msgid "Livechat window" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:108 +msgid "" +"The *Livechat Window* is the space where the live chat conversation with " +"website visitors takes place." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:111 +msgid "" +"Edit the :guilabel:`Welcome Message` to change the message a visitor sees " +"when they open a new chat session. This message will appear as though it is " +"sent by a live chat operator, and acts as both a greeting and an invitation " +"to continue the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:115 +msgid "" +"Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears " +"in the box where visitors will type their replies." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:118 +msgid "" +"The *Channel Header* is the colored bar at the top of the chat window. The " +":guilabel:`Channel Header Color` can be changed following the same steps as " +"the *Livechat Button Color* above." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:124 +msgid "" +"The Livechat Window with a purple header. The chat input placeholder reads " +"\"Ask Something...\"" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:127 +msgid "Channel rules" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:129 +msgid "" +"The :guilabel:`Channel Rules` tab on the live chat channel details form " +"determines when the *Live Chat Window* opens on the website, by configuring " +"when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:133 +msgid "" +"To create a new channel rule, click :guilabel:`Add a line`. This opens the " +":guilabel:`Open: Rules` pop-up." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of a channel's rules form for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:141 +msgid "Create new rules" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:143 +msgid "" +"Fill out the fields on the :guilabel:`Open: Rules` pop-up as instructed " +"below, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:148 +msgid "Live Chat Button" +msgstr "ปุ่มไลฟ์แชท" + +#: ../../content/applications/websites/livechat.rst:150 +msgid "" +"The *Livechat Button* is the icon that appears in the bottom corner of the " +"website. Select from one of the following display options:" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:153 +msgid ":guilabel:`Show` displays the chat button on the page(s)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:154 +msgid "" +":guilabel:`Show with notification` displays the chat button, as well as a " +"floating text bubble next to the button." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:156 +msgid "" +":guilabel:`Open automatically` displays the button and automatically opens " +"the chat window after a specified amount of time (designated in the " +":guilabel:`Open automatically timer` field)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:159 +msgid ":guilabel:`Hide` hides the chat button on the page(s)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:161 +msgid "Chatbot" +msgstr "แชทบอท" + +#: ../../content/applications/websites/livechat.rst:163 +msgid "" +"If a *Chatbot* will be included on this channel, select it from the " +"dropdown. If the chatbot will only be active when no operators are active, " +"check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:167 +msgid "URL Regex" +msgstr "URL Regex" + +#: ../../content/applications/websites/livechat.rst:169 +msgid "" +"In the :guilabel:`URL Regex` field, input the relative URL of the page where" +" the chat button should appear." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:172 +msgid "Open automatically timer" +msgstr "เปิดตัวจับเวลาอัตโนมัติ" + +#: ../../content/applications/websites/livechat.rst:174 +msgid "" +"This field designates the amount of time (in seconds) a page will be open " +"before the chat window will open. If the :guilabel:`Livechat Button` for " +"this rule is not set to :guilabel:`Open automatically`, this field will be " +"ignored." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:178 +msgid "Country" +msgstr "ประเทศ" + +#: ../../content/applications/websites/livechat.rst:180 +msgid "" +"If this channel should only be available to site visitors in specific " +"countries, add them to the :guilabel:`Country` field. If this field is left " +"blank, the channel will be available to all site visitors, regardless of " +"location." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:185 +msgid "" +"In order to track the geographical location of visitors, :guilabel:`GeoIP` " +"must be installed on the database. While this feature is installed by " +"default on *Odoo Online*, *On-Premise* databases will require additional " +":doc:`setup steps </administration/install/geo_ip>`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:190 +msgid "Widget" +msgstr "วิดเจ็ต" + +#: ../../content/applications/websites/livechat.rst:192 +msgid "" +"The :guilabel:`Widget` tab on the live chat channel details form provides " +"the shortcode for an embeddable website widget. This code can be added to a " +"website to provide access to a live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:196 +msgid "" +"The live chat widget can be added to websites created through Odoo by " +"navigating to the :menuselection:`Website --> Configuration --> Settings`. " +"Then scroll to the :guilabel:`Livechat` section, and select the channel to " +"add to the site. Click :guilabel:`Save` to apply." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:200 +msgid "" +"To add the widget to a website created on a third-party platform, click the " +"first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the " +"code into the `<head>` tag on the site." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:203 +msgid "" +"Likewise, to send a live chat session to a customer, click the second " +":guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent" +" directly to a customer, and once they click the link, it will open a new " +"chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the widget tab for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:212 +msgid "Participate in a conversation" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:214 +msgid "" +"As explained above, *operators* are the users who will respond to live chat " +"requests from customers. The information below outlines the necessary steps " +"for operators participating in live chat conversations on an Odoo database." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:219 +msgid "Set an online chat name" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:221 +msgid "" +"Before participating in a live chat, operators should update their *Online " +"Chat Name*. This is the name that will be displayed to site visitors in the " +"live chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:224 +msgid "" +"To update the :guilabel:`Online Chat Name`, click on the user name in the " +"upper-right corner of any page in the database. Select :guilabel:`My " +"Profile` to open the Profile page. On the right side of the " +":guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field " +"and enter the preferred name." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "View of the My Profile option in Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:233 +msgid "" +"If a users :guilabel:`Online Chat Name` is not set, the name displayed will " +"default to the :guilabel:`User Name`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:237 +msgid "" +"A user has their full name as their :guilabel:`User Name`, but they do not " +"want to include their last name in a live chat conversation. They would then" +" set their :guilabel:`Online Chat Name` to include only their first name." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:0 +msgid "View of user profile in Odoo, emphasizing the Online Chat name field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:246 +msgid "Join or leave a channel" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:248 +msgid "" +"To join a live chat channel, go to the :menuselection:`Live Chat` app and " +"click the :guilabel:`JOIN` button on the kanban card for the appropriate " +"channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:251 +msgid "" +"Any channel where the user is currently active will show a :guilabel:`LEAVE`" +" button. Click this button to disconnect from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of a channel form and the option to join a channel for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:259 +msgid "" +"*Operators* that do not show any activity in Odoo for more than thirty " +"minutes will be considered disconnected, and subsequently removed from the " +"channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:263 +msgid "Manage live chat requests" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:265 +msgid "" +"When an operator is active in a channel, chat windows will open in the " +"bottom right corner of the screen, no matter where they are in the database." +" They can participate in conversations without leaving their current " +"location." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:270 +msgid "" +"Conversations can also be accessed by clicking the :guilabel:`Conversations`" +" icon in the menu bar." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:0 +msgid "View of the menu bar in Odoo emphasizing the conversations icon." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:277 +msgid "" +"Live chat conversations can also be viewed by navigating to " +":menuselection:`Dashboard --> Discuss`. New conversations will appear in " +"bold under the :guilabel:`LIVECHAT` heading along the left panel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst-1 +msgid "" +"View of the discuss application with a message sent through live chat in " +"Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:284 +msgid "" +"Click on a conversation in the left panel to select it. This will open the " +"conversation. From this view, an operator can participate in the chat the " +"same as they would in the normal chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:288 +msgid "" +":doc:`Get Started with Discuss " +"</applications/productivity/discuss/overview/get_started>`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:289 +msgid ":doc:`/applications/websites/livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:3 +msgid "Chatbots" +msgstr "แชทบอท" + +#: ../../content/applications/websites/livechat/chatbots.rst:5 +msgid "" +"A *Chatbot* is a program designed to mimic a conversation with a live human." +" Chatbots are assigned a script of pre-written steps to follow. The scripts " +"are designed to anticipate a visitor's potential response, and lead them " +"through a series of questions and answers the same way a live team member " +"would." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:10 +msgid "" +"Chatbots can be customized to fill various roles, from customer support, to " +"creating leads, to collecting contact information. The goal of the chatbot " +"depends on the page of the website they are assigned, and the messages " +"included in the script, among other criteria." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the chat window with a helpdesk ticket created in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:19 +msgid "Build a chatbot" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:21 +msgid "" +"Before creating a new chatbot, the *Live Chat* application must first be " +"installed on the database. This can be done directly from the " +":menuselection:`Apps` menu by searching for `Live Chat` in the " +":guilabel:`search bar` and clicking :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:25 +msgid "" +"Alternatively, *Live Chat* can be installed and enabled by navigating to the" +" :menuselection:`Website application --> Configuration --> Settings`, and " +"checking the box labeled :guilabel:`Livechat`. Once enabled, the database " +"will refresh, and the *Live Chat* application is accessible." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:29 +msgid "" +"Once the *Live Chat* application has been installed on the database, open " +"it, and go to :menuselection:`Configuration --> Chatbots`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:33 +msgid "" +"When the *Live Chat* app is installed, a sample chatbot is created, named " +"*Welcome Bot*. This chatbot has a pre-configured script that walks through a" +" few basic steps, including asking for a visitor's email address, and " +"forwarding the conversation to an operator." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:37 +msgid "" +"*Welcome Bot* can be used as a starting point. The existing steps can be " +"edited or removed, and new steps can be added to customize the script, as " +"needed." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:40 +msgid "*Welcome Bot* can be deleted (or archived)." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "View of the Welcome Bot script in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:46 +msgid "" +"To create a new chatbot, navigate to the :guilabel:`Chatbot` page " +"(:menuselection:`Live Chat app --> Configuration --> Chatbots`) and click " +":guilabel:`New`. This opens a blank chatbot details page." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:49 +msgid "" +"On the blank chatbot details page, enter a name in the :guilabel:`Chatbot " +"Name` field and click on the :guilabel:`Edit Image` icon in the upper right " +"corner of the form to add a photo." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:53 +msgid "Chatbot scripts" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:55 +msgid "" +"Once the new chatbot has been created and named, the next step is to create " +"a script. Chatbot conversations follow an accompanying script. These scripts" +" are comprised of lines of dialogue, each designed to either deliver or " +"capture information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:59 +msgid "" +"To create a chatbot script, navigate to the :guilabel:`Script` tab of the " +"chatbot details page, and click :guilabel:`Add a Line` to open the " +":guilabel:`Create Script Steps` pop-up form." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:62 +msgid "" +"This form must be filled out for each line of text (dialogue) that the " +"chatbot could potentially deliver during the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:65 +msgid "" +"First, enter the content of the message in the :guilabel:`Message` field. " +"Then, select an option from the :guilabel:`Step Types` drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:69 +msgid "Step types" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:71 +msgid "" +"The :guilabel:`Step Type` selected depends on the intended purpose of the " +"message. The available options in the :guilabel:`Step Type` drop-down are " +"listed below, as well as their use, and any additional information:" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:76 +msgid "Text" +msgstr "ข้อความ" + +#: ../../content/applications/websites/livechat/chatbots.rst:78 +msgid "" +"This step is used for messages where no answer is expected (or necessary). " +"Text steps can be used for greetings and/or to deliver information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:82 +msgid "" +"Text step types are only intended to deliver information, and do not allow " +"for any visitor input. As such, they need to be followed by additional steps" +" to continue the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:86 +msgid "Question" +msgstr "คำถาม" + +#: ../../content/applications/websites/livechat/chatbots.rst:88 +msgid "" +"This step asks a question and provides a set of answers. The visitor clicks " +"on one answer, which either leads to a new step in the conversation, or can " +"lead to an optional link to a new webpage." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:92 +msgid "" +"It is helpful to add a catchall answer to question steps (ex: \"Something " +"else\"). This helps visitors continue the conversation, even if their needs " +"don't exactly fit with any of the other answers." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:97 +msgid "Email" +msgstr "อีเมล" + +#: ../../content/applications/websites/livechat/chatbots.rst:99 +msgid "" +"This step prompts visitors to provide their email address, which is stored " +"and can be used by team members later to follow up with additional " +"information." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:102 +msgid "" +"The only accepted inputs for this step type are email addresses that are in " +"a valid format. If a visitor attempts to enter anything other than a valid " +"email address, the chatbot responds with a message stating it does not " +"recognize the information submitted." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +msgid "View of a chatbot responding to an invalid email." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:111 +msgid "Phone" +msgstr "โทรศัพท์" + +#: ../../content/applications/websites/livechat/chatbots.rst:113 +msgid "" +"Similar to email, this step type prompts the visitor to enter their phone " +"number, which can be used at a later time to follow up with additional " +"information, or to schedule demos, and more." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:117 +msgid "" +"Due to the vast number of formats used for phone numbers worldwide, " +"responses to this step type are **not** validated for formatting." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:121 +msgid "Forward to Operator" +msgstr "ส่งต่อไปยังตัวดำเนินการ" + +#: ../../content/applications/websites/livechat/chatbots.rst:123 +msgid "" +"This step forwards the conversation to an active live chat operator, so that" +" they can continue assisting the visitor. As the conversation transcript is " +"passed on to the operator they are able to pick up where the chatbot left " +"off. This not only saves time for all parties involved, it can also help " +"qualify conversations before they reach live human operators." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:129 +msgid "" +"If no active operator is available on the channel, the chatbot continues the" +" conversation with the visitor. Therefore, additional steps should be added " +"after this one to ensure that there is no abrupt end to the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "" +"View of a chatbot follow up messages when no live chat operator is " +"available." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:138 +msgid "Free Input/Multi-Line" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:140 +msgid "" +"The free input step allows visitors to respond to questions without " +"providing pre-written responses. Information provided in these responses is " +"stored in the chat transcripts." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:143 +msgid "" +"Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-" +"Line)` depending on the type and amount of information being requested from " +"the visitor." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:147 +msgid "Create Lead" +msgstr "สร้างลูกค้าเป้าหมาย" + +#: ../../content/applications/websites/livechat/chatbots.rst:149 +msgid "" +"This step creates a lead in the *CRM* application. Select an option from the" +" :guilabel:`Sales Team` drop-down to assign the created lead to a specific " +"team." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:153 +msgid "Create Ticket" +msgstr "สร้างทิกเก็ต" + +#: ../../content/applications/websites/livechat/chatbots.rst:155 +msgid "" +"This step creates a :doc:`ticket " +"</applications/services/helpdesk/overview/receiving_tickets>` in the " +"*Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` " +"drop-down to assign the created ticket to a specific team." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:160 +msgid "Only if" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:162 +msgid "" +"Chatbot scripts operate on an if/then basis, which means the next question " +"presented to the visitor is determined by the answer they provide to the " +"previous question." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:165 +msgid "" +"To continue the progression of the conversation, the form for a new step " +"contains a field labeled :guilabel:`Only If`. This field is where the " +"progression of questions is defined." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:168 +msgid "" +"If a step is intended to follow all of the previous messages, this field can" +" be left empty. However, if a message should **only** be sent conditionally," +" based on a previous response (or several previous responses), those " +"responses need to be added to this field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:173 +msgid "" +"If there are any selections made in the :guilabel:`Only If` field, the step " +"will **not** be shown in a conversation unless **all** of the answers have " +"been selected. Only include selections in this field if they are necessary " +"for this step to be displayed." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:178 +msgid "" +"In the *Welcome Bot* script, a visitor can ask about pricing information. If" +" the visitor selects this response, a step is included to forward the " +"conversation to an operator. The chatbot first sends a message informing the" +" visitor that it is checking to see if an operator is available to chat." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:183 +msgid "" +"However, this message should **only** be delivered if the visitor requests " +"pricing information. In that situation, the conversation would proceed as " +"below:" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:186 +msgid "Welcome Bot: \"*What are you looking for?*\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:187 +msgid "Visitor: \"**I have a pricing question.**\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:188 +msgid "" +"Welcome Bot: \"*Hmmm, let me check if I can find someone that could help you" +" with that...*\"" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:190 +msgid "" +"In the details form for the :guilabel:`Text` step, the *I have a pricing " +"question* response has been selected in the :guilabel:`Only If` field. As " +"such, this step is **only** shown in conversations where that response has " +"been selected." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:0 +msgid "View of the new message form emphasizing the Only If field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:199 +msgid "Script testing" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:201 +msgid "" +"In order to ensure all visitors have a satisfactory experience with the " +"chatbot, each message needs to lead to a natural conclusion. Chatbot scripts" +" should be tested to confirm there are no dead-ends, and to get an " +"understanding of what the visitor sees when they interact with the chatbot." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:206 +msgid "" +"If there is an answer or input provided by the visitor that is **not** " +"assigned a corresponding follow-up response, the conversation stops (*dead-" +"end*). Since the visitor cannot re-engage the chatbot, they will have to re-" +"start the conversation, by refreshing the chat window, or their browser." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:211 +msgid "" +"To test the performance of a chatbot, first click on the :guilabel:`Test` " +"button at the top-left of the chatbot script page. Then, upon being " +"redirected to the testing screen, answer the chatbot prompts the same way a " +"potential site visitor would." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:215 +msgid "" +"When the script has reached an end-point, the message *Conversation " +"ended...Restart* appears at the bottom of the chat window. To begin the " +"conversation at the beginning of the script, click on :guilabel:`Restart`. " +"To return to the script page, click :guilabel:`Back to edit mode` at the top" +" of the page." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:221 +msgid "Add chatbot to a channel" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:223 +msgid "" +"After a chatbot has been created and tested, it needs to be added to a live " +"chat channel." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:225 +msgid "" +"First, open the :menuselection:`Live Chat` application, and select the " +"kanban card for a :guilabel:`Channel`, or create a :doc:`new one " +"</applications/websites/livechat>`. Click on the :guilabel:`Channel Rules` " +"tab. Then, open an existing rule, or create a new one by clicking " +":guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:230 +msgid "" +"On the :guilabel:`Create Rules` pop-up detail form, choose the appropriate " +"chatbot in the :guilabel:`Chatbot` field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:233 +msgid "" +"If the chatbot should **only** be active if there are no available live chat" +" operators, check the box labeled :guilabel:`Enabled only if no operator`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst-1 +msgid "View of the channel rules emphasizing the chatbot field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:241 +msgid ":doc:`Live chat channel rules </applications/websites/livechat>`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:3 +msgid "Ratings" +msgstr "การให้คะแนน" + +#: ../../content/applications/websites/livechat/ratings.rst:5 +msgid "" +"At the end of a *Live Chat* conversation, customers have the opportunity to " +"rate the quality of support they received from the live chat *operator*. " +"Customers provide ratings as soon as they close the conversation. This " +"allows operators to receive immediate feedback on their performance. It also" +" allows customers the chance to share any final comments before leaving the " +"chat window." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:11 +msgid "Rate live chat conversations" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:13 +msgid "" +"Customers end a *live chat* conversation by clicking the :guilabel:`X` in " +"the upper right-hand corner of the chat window. They are then prompted to " +"select an icon that reflects their level of satisfaction. The icons " +"represent the following ratings:" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:17 +msgid "**Satisfied** - *green smiling face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:18 +msgid "**Okay** - *yellow neutral face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:19 +msgid "**Dissatisfied** - *red frowning face*" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the chat window from a user's side for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:26 +msgid "" +"When customers end a conversation, a field marked :guilabel:`Receive a copy " +"of this conversation` appears under the *ratings* icons. Customers can enter" +" their email either before or after they submit a rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:30 +msgid "" +"If the customer selects :guilabel:`Satisfied (smile)` icon, they are " +"presented with a thank you message and a :guilabel:`Close Conversation` " +"link." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of customer's live chat window with thank you message." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:37 +msgid "" +"If the customer selects either :guilabel:`Okay (neutral)` icon or " +":guilabel:`Dissatisfied (frown)` icon, a text box will appear. Customers can" +" add comments in this text box to explain why they chose this rating. This " +"message will be sent to the live chat operator, along with the rating icon." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of a chat window from an operator's window highlighting a rating for " +"Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:46 +msgid "Publish customer ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:48 +msgid "" +"To publish a channel's ratings on the website, first navigate to a live chat" +" channel's record by going to the :menuselection:`Live Chat` app and " +"clicking on the kanban card for that team. Then click on the :guilabel:`Go " +"to Website` smart button. This will open the :guilabel:`Live Chat Channel " +"Statistics` page." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:53 +msgid "" +"In the upper right corner of the page, click the red :guilabel:`Unpublished`" +" slider. The slider changes from :guilabel:`Unpublished` to " +":guilabel:`Published`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the published ratings on the portal for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:61 +msgid "" +"The customer notes that are submitted with the rating will *not* be " +"published on the website. These are kept internal. Only a statistical " +"overview of the operators' performance for the *channel* appears on the " +"website." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:66 +msgid "Add ratings page to site" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:68 +msgid "" +"Once the rating page has been published, it has to be manually added to the " +"website. To do this, go to the main Odoo dashboard and open the *Website* " +"application. :menuselection:`Website app--> Site --> Content --> Pages`, " +"then click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:72 +msgid "" +"This will open a :guilabel:`New Page` pop-up window. In the :guilabel:`Page " +"Title` field, enter `livechat`. This acts as the URL for the published " +"webpage." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:76 +msgid "" +"The URL *must* be named `livechat` in order for the database to recognize " +"and connect the ratings page. After the page has been published, the page " +"title can be changed later under the :guilabel:`Menu Editor`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:80 +msgid "" +"Click :guilabel:`Create`, and the newly created webpage will open. The " +":guilabel:`Webpage Editor` appears in the right panel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:83 +msgid "" +"The page lists the names of the :guilabel:`Live Chat Channels` whose ratings" +" pages have been published. On the left side of the channel name is a speech" +" bubble icon, which users can click on to go to the ratings' page for the " +"respective channel." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of the webpage for Live Chat ratings emphasizing the channel icon." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:91 +msgid "" +"Make any desired changes or additions to this page, then click " +":guilabel:`Save` in the top right of the webpage editor. The website editor " +"side panel closes, and the webpage remains on the screen." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:94 +msgid "" +"To publish the `livechat` webpage, return to the list of webpages by " +"navigating to :menuselection:`Site --> Content --> Pages`. Click the " +"checkbox to the left of `livechat` in the list of pages to select the page " +"and highlight the line. Then, click the checkbox under the column labeled " +":guilabel:`Is Published`. The field with the checkbox is highlighted in " +"white. Click the checkbox a second time to activate the :guilabel:`Is " +"Published` box. The webpage is now published." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of the list of pages for a website with the 'is published' box " +"emphasized." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:104 +msgid "" +"Once the page has been added to the site, ratings are set to be published by" +" default. However, individual ratings can be manually selected to be hidden " +"from the public. The rating will still be included in internal reports, and " +"can still be viewed by internal teams. However, public website visitors and " +"portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:109 +msgid "" +"See :ref:`Hide individual ratings <livechat/overview/hide-ratings>` for more" +" information." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:112 +msgid "Customer ratings report" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:114 +msgid "" +"The :guilabel:`Customer Ratings` report (:menuselection:`Live Chat --> " +"Report --> Customer Ratings`) displays an overview of the ratings received " +"on individual support tickets, as well as any additional comments submitted " +"with the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "View of the customer ratings report in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:122 +msgid "" +"The report defaults to a kanban view, with each rating represented by a " +"different card. To switch to a different view, click on one of the icons in " +"the upper-right corner of the screen. The report is available in *list* " +"view, *pivot* view, and *graph* view." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:126 +msgid "" +"Click on an individual rating to see additional details about the " +"conversation, and the rating." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:131 +msgid "Hide individual ratings" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:133 +msgid "" +"Ratings are set to be published by default. However, individual ratings can " +"be manually selected to be hidden from the public. The rating will still be " +"included in internal reports, and can still be viewed by internal teams. " +"However, public website visitors and portal users will not have access." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:137 +msgid "" +"To hide a rating, go to :menuselection:`Live Chat app --> Reports --> " +"Customer Ratings`. Click on the kanban card for the rating to be hidden. On " +"the individual rating's detail page, check the box labeled " +":guilabel:`Visible Internally Only`." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst-1 +msgid "" +"View of an individual rating's detail page with the visible internally " +"setting checked." +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:146 +msgid ":doc:`/applications/websites/livechat`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:147 +msgid ":doc:`responses`" +msgstr "" + +#: ../../content/applications/websites/livechat/ratings.rst:148 +msgid ":doc:`/applications/websites/website`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:3 +msgid "Commands and canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:5 +msgid "" +"In the Odoo *Live Chat* application, *commands* allow the user to perform " +"specific actions both inside the chat window, and through other Odoo " +"applications. The *Live Chat* app also includes *canned responses*. These " +"are customized, pre-configured substitutions that allow users to replace " +"shortcut entries in place of longer, well-thought out responses to some of " +"the most common questions and comments." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:11 +msgid "" +"Both commands and canned responses save time, and allow users to maintain a " +"level of consistency throughout their conversations." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:15 +msgid "Execute a command" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:17 +msgid "" +"Live chat *commands* are keywords that trigger pre-configured actions. When " +"a live chat *operator* is participating in a conversation with a customer or" +" website visitor, they can execute a command by typing `/`, followed by the " +"command." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:21 +msgid "" +"Commands, and the resulting actions, are only visible in the conversation " +"window for the live chat operator. A customer will not see any commands that" +" an operator uses in a conversation from their view of the chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:29 +msgid "More information about each available command can be found below." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:32 +msgid "Help" +msgstr "ช่วยเหลือ" + +#: ../../content/applications/websites/livechat/responses.rst:34 +msgid "" +"If an operator types `/help` in the chat window, an informative message that" +" includes the potential entry types an operator can make is displayed." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:37 +msgid "" +"Type `@username` to mention a user in the conversation. A notification will " +"be sent to that user's inbox or email, depending on their notification " +"settings." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:39 +msgid "Type `#channel` to mention a *Discuss* channel." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:40 +msgid "Type `/command` to execute a command." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:41 +msgid "" +"Type `:shortcut` to insert a :ref:`canned response <live-chat/canned-" +"responses>`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the message generated from using the /help command in Odoo Live " +"Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:48 +msgid ":doc:`/applications/productivity/discuss/overview/get_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:49 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:52 +msgid "Helpdesk & Helpdesk search" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:54 +msgid "" +"The `/helpdesk` and `/helpdesk_search` commands allow operators to both " +"create helpdesk tickets directly from a conversation, and search through " +"existing tickets by keyword or ticket number." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:58 +msgid "" +"The `/helpdesk` and `/helpdesk_search` commands can only be used if the " +"*Helpdesk* app has been installed, and *Live Chat* has been activated on a " +"*Helpdesk* team. To activate :guilabel:`Live Chat`, go to " +":menuselection:`Helpdesk application --> Configuration --> Teams`, and " +"select a team. Scroll to the :guilabel:`Channels` section and check the box " +"labeled :guilabel:`Live Chat`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:64 +msgid "Create a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:66 +msgid "" +"If an operator types `/helpdesk` in the chat window, the conversation is " +"used to create a *Helpdesk* ticket." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:70 +msgid "" +"In version 16.3, the command to create a new ticket is `/ticket`. This only " +"applies to databases running version 16.3." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:73 +msgid "" +"After entering the `/helpdesk` command, type a title for the ticket into the" +" chat window, then press `Enter`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the results from a helpdesk search in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:80 +msgid "" +"The newly created ticket will be added to the *Helpdesk* team that has live " +"chat enabled. If more than one team has live chat enabled, the ticket will " +"automatically be assigned based on the team's priority." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:84 +msgid "" +"The transcript from the conversation will be added to the new ticket, under " +"the :guilabel:`Description` tab." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:87 +msgid "" +"To access the new ticket, click on the link in the chat window, or go to the" +" :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on " +"the kanban card for the appropriate team." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:92 +msgid "Search for a ticket from a live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:94 +msgid "" +"If an operator types `/helpdesk_search` in the chat window, they can search " +"through *Helpdesk* tickets by ticket number or keyword." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:98 +msgid "" +"In version 16.3, the command to search through *Helpdesk* tickets is " +"`/search_tickets`. This only applies to databases running version 16.3." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:101 +msgid "" +"After entering the `/helpdesk_search` command, type a keyword or ticket " +"number, then press `Enter`. If one or more related tickets are found, a list" +" of links will be generated in the conversation window." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:110 +msgid "" +"Results from the search command will only be seen by the operator, not the " +"customer." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:113 +msgid "History" +msgstr "ประวัติ" + +#: ../../content/applications/websites/livechat/responses.rst:115 +msgid "" +"If an operator types `/history` in the chat window, it will generate a list " +"of the most recent pages the visitor has viewed on the website (up to 15)." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of the results from a /history command in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:123 +msgid "Lead" +msgstr "ลูกค้าเป้าหมาย" + +#: ../../content/applications/websites/livechat/responses.rst:125 +msgid "" +"By typing `/lead` in the chat window, an operator can create a *lead* in the" +" *CRM* application." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "View of the results from a /lead command in a Live Chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:132 +msgid "" +"The `/lead` command can only be used if the *CRM* app has been installed." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:134 +msgid "" +"After typing `/lead`, create a title for this new lead, then press `Enter`. " +"A link with the lead title appears. Click the link, or navigate to the " +":menuselection:`CRM` app to view the :guilabel:`Pipeline`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:139 +msgid "" +"The link to the new lead can only be seen and accessed by the operator, not " +"the customer." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:141 +msgid "" +"The transcript of that specific live chat conversation (where the lead was " +"created) is added to the :guilabel:`Internal Notes` tab of the lead form." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:144 +msgid "" +"On the :guilabel:`Extra Information` tab of the lead form, the " +":guilabel:`Source` will be listed as :guilabel:`Livechat`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:148 +msgid "Leave" +msgstr "การลา" + +#: ../../content/applications/websites/livechat/responses.rst:150 +msgid "" +"If an operator types `/leave` in the chat window, they can automatically " +"exit the conversation. This command does not cause the customer to be " +"removed from the conversation, nor does it automatically end the " +"conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:155 +msgid ":doc:`/applications/sales/crm/acquire_leads`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:156 +msgid ":doc:`/applications/services/helpdesk/overview/getting_started`" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:161 +msgid "Canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:163 +msgid "" +"*Canned responses* are customizable inputs where a *shortcut* stands in for " +"a longer response. An operator will enter the shortcut, and it will " +"automatically be replaced by the expanded *substitution* response in the " +"conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:168 +msgid "Create canned responses" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:170 +msgid "" +"To create a new canned response, go to :menuselection:`Live Chat app --> " +"Configuration --> Canned Responses --> New`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:173 +msgid "" +"From here, type the shortcut command into the :guilabel:`Shortcut` field." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:175 +msgid "" +"Then, click into the :guilabel:`Substitution` field, and enter the custom " +"message that will be sent to visitors in place of the shortcut. Click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:179 +msgid "" +"Try to connect the shortcut to the topic of the substitution. The easier it " +"is for the operators to remember, the easier it will be to use the canned " +"responses in conversations." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:183 +msgid "Use canned responses in a live chat conversation" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:185 +msgid "" +"To use a canned response during a live chat conversation, type a colon (`:`)" +" into the chat window, followed by the shortcut." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:189 +msgid "" +"An operator is chatting with a visitor. As soon as they type `:` they would " +"see a list of available responses. They can manually select one from the " +"list, or continue to type. If they want to use the canned response `'I am " +"sorry to hear that.'`, they would type `:sorry`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst-1 +msgid "" +"View of a chat window and the use of a canned response in Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:198 +msgid "" +"Typing `:` into a chat window on its own will generate a list of available " +"canned responses. Responses can be manually selected from the list, in " +"addition to the use of shortcuts." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:0 +msgid "View of a chat window and the list of available canned responses." +msgstr "" + +#: ../../content/applications/websites/website.rst:8 +msgid "Website" +msgstr "เว็บไซต์" + +#: ../../content/applications/websites/website.rst:10 +msgid "" +"Discover the best **Open-Source Website Builder** and learn how to build " +"beautiful websites that convert visitors into leads or revenues." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3 +msgid "Address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:5 +msgid "" +"You can use the Google Places API on your website to ensure that your users'" +" delivery addresses exist and are understood by the carrier. The Google " +"Places API allows developers to access detailed information about places " +"using HTTP requests. The autocompletion predicts a list of places when the " +"user starts typing the address." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst-1 +msgid "Address autocomplete example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:13 +msgid "" +"`Google Maps Platform <https://mapsplatform.google.com/maps-products>`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:14 +msgid "" +"`Google Developers Documentation: Google Places API " +"<https://developers.google.com/maps/documentation/places/web-" +"service/autocomplete>`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:18 +msgid "" +"To do so, go to :menuselection:`Website --> Configuration --> Settings` and " +"enable :guilabel:`Address Autocomplete` in the :guilabel:`SEO` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst-1 +msgid "Enable address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:24 +msgid "" +"Insert your :guilabel:`Google Places API key` in the :guilabel:`API Key` " +"field. If you don't have one, create yours on the `Google Cloud Console " +"<https://console.cloud.google.com/getting-started>`_ and follow these steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:28 +msgid "Step 1: Enable the Google Places API" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:30 +msgid "**Create a New Project:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:32 +msgid "" +"To enable the **Google Places API**, you first need to create a project. To " +"do so, click :guilabel:`Select a project` in the top left corner, " +":guilabel:`New Project`, and follow the prompts to set up your project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:34 +msgid "**Enable the Google Places API:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:36 +msgid "" +"Go to the :guilabel:`Enabled APIs & Services` and click :guilabel:`+ ENABLE " +"APIS AND SERVICES.` Search for :guilabel:`\"Places API\"` and select it. " +"Click on the :guilabel:`\"Enable\"` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:39 +msgid "" +"Google's pricing depends on the number of requests and their complexity." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:42 +msgid "Step 2: Create API Credentials" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:44 +msgid "" +"Go to `APIs & Services --> Credentials " +"<https://console.cloud.google.com/apis/credentials>`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:46 +msgid "**Create credentials:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:48 +msgid "" +"To create your credentials, go to :guilabel:`Credentials`, click " +":guilabel:`Create Credentials`, and select :guilabel:`API key`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:50 +msgid "Restrict the API Key (Optional)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:52 +msgid "" +"For security purposes, you can restrict the usage of your API key. You can " +"go to the :guilabel:`API restrictions` section to specify which APIs your " +"key can access. For the Google Places API, you can restrict it to only allow" +" requests from specific websites or apps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:57 +msgid "Save Your API Key: Copy your API key and securely store it." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:58 +msgid "Do not share it publicly or expose it in client-side code." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:3 +msgid "Cookies bar" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:5 +msgid "" +"Cookies are small text files sent to your device when you visit a website. " +"They are processed and stored by your browser and contain information about " +"your visit, such as login data, location, language, etc. There are two main " +"types of cookies:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:9 +msgid "" +"Essential cookies, which are necessary for the website to function properly;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:10 +msgid "" +"Non-essential or optional cookies, which are used to analyze your behavior " +"or display advertisements." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1 +msgid "Example of a cookies bar with the popup layout." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:17 +msgid "" +"Notifying users about data collection, as well as its methods and purposes, " +"is required by data protection laws such as `GDPR <https://gdpr.eu>`_. " +"Cookies bars are commonly used to fulfill this obligation in a user-friendly" +" and transparent manner. They are displayed immediately upon a user's first " +"visit to inform them that the website uses cookies and let them decide " +"whether they want to store non-essential cookies on their device." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:26 +msgid "" +"To enable the cookies bar on your Odoo website, go to " +":menuselection:`Website --> Configuration` and enable :guilabel:`Cookies " +"Bar` in the :guilabel:`Privacy` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:29 +msgid "" +"You can :ref:`customize the appearance of your cookies bar <cookies-" +"bar/customization>` and :ref:`edit the content of the related Cookie Policy " +"page <cookies-bar/policy>`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:35 +msgid "Customization" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:37 +msgid "" +"To adapt the display of the cookies bar, click :guilabel:`Edit` and select " +"the :guilabel:`Cookies Bar` building block in the :guilabel:`Invisible " +"Elements` at the bottom of the panel. Customize it using the options in the " +":guilabel:`Customize` tab in the edit panel. Three :guilabel:`Layouts` are " +"available:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:42 +msgid ":guilabel:`Discrete`: thin bar" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:43 +msgid ":guilabel:`Classic`: banner" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:44 +msgid "" +":guilabel:`Popup`: you can change the popup's :guilabel:`Position` to the " +":guilabel:`Top`, :guilabel:`Middle`, or :guilabel:`Bottom` of the screen." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:47 +msgid "You can also:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:49 +msgid "modify the :guilabel:`Size` of the cookies bar;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:50 +msgid "" +"enable :guilabel:`Backdrop` to gray out the page in the background when the " +"cookies bar is displayed on the screen;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:52 +msgid "" +"further customize the appearance of the cookies bar using :guilabel:`Block` " +"and/or :guilabel:`Column` customization options, which are available after " +"clicking anywhere in the building block." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:56 +msgid "" +"To edit the contents of the cookies bar (i.e., the consent message), click " +"directly in the building block." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst-1 +msgid "Odoo Website's edit panel to customize the cookies bar." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:65 +msgid "Cookie policy" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:67 +msgid "" +"When you enable the cookies bar for your website, Odoo creates the **Cookie " +"Policy** page (`/cookie-policy`) with the list of essential and optional " +"cookies. To access it, click the :guilabel:`Cookie Policy` hyperlink in the " +"cookies bar or open the page from :menuselection:`Website --> Site --> " +"Pages`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:72 +msgid "" +"The contents of the page can be adapted based on your website's features and" +" characteristics if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cookies_bar.rst:76 +msgid "" +"You could add a link providing access to this page, in your website's " +"footer, for example." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:3 +msgid "Multiple websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:5 +msgid "" +"Odoo allows you to create multiple websites from the same database. This can" +" be useful, for example, if you have multiple brands operating under your " +"organization, or to create separate websites for different " +"products/services, or different audiences. In these cases, having different " +"websites can help avoid confusion and make it easier to tailor your digital " +"outreach strategies and reach your target audience." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:11 +msgid "" +"Each website can be designed and configured independently with its own " +":doc:`domain name </administration/maintain/domain_names>`, theme, pages, " +"menus, :doc:`languages <translate>`, :doc:`products " +"<../../ecommerce/managing_products/products>`, assigned sales team, etc. " +"They can also :ref:`share content and pages <multi-" +"website/website_content>`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:18 +msgid "" +"Duplicate content (i.e., pages and content shared between multiple websites)" +" can have a negative impact on :doc:`../pages/seo`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:22 +msgid "Website creation" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:24 +msgid "To create a new website, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:26 +#: ../../content/applications/websites/website/configuration/multi_website.rst:142 +msgid "Go to :menuselection:`Website --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:27 +msgid "Click :guilabel:`+ New Website`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "New website button" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:32 +msgid "" +"Specify the :guilabel:`Website Name` and :guilabel:`Website domain`. Each " +"website must be published under its own :doc:`domain " +"</administration/maintain/domain_names>`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:34 +msgid "" +"Adapt the :guilabel:`Company name`, :guilabel:`Languages` and " +":guilabel:`Default language` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:36 +msgid "Click the :guilabel:`Create` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:38 +msgid "You can then start building your new website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:41 +msgid "" +"By default, all website-related apps that you have installed (e.g. " +"**eCommerce**, **Forum**, **Blog**, etc.) and their related website pages " +"are also available on the new website. You can remove them by amending the " +"website's menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:46 +msgid "Switching websites" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:48 +msgid "" +"To switch from one website to another, click the menu next to the " +":guilabel:`+New` button in the top right corner and select the website you " +"want to switch to." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Website selector" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:55 +msgid "" +"When you switch websites, you are redirected to the other website, to the " +"same page (URL) as the current one. If the page you are currently viewing " +"does not exist on the other website, you are redirected to a 404 error page." +" Once redirected, click :guilabel:`Create page` to create the page." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "Create a page from a 404 error page" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:64 +msgid "Website-specific configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:66 +msgid "" +"Most website settings are website-specific, which means they can be " +"enabled/disabled per website. To adapt the settings for a website, go to " +":menuselection:`Website --> Configuration --> Settings`. Select the desired " +"website in the field :guilabel:`Settings of Website` at the top of the " +":guilabel:`Settings` page, in the **yellow** banner. Then, adapt the options" +" for that specific website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:73 +msgid "" +"Websites are created with the default settings; the settings are not copied " +"from one website to the other." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:75 +msgid "" +"In a :doc:`multi-company environment <../../../general/users/companies>`, " +"each website can be linked to a specific company in your database so that " +"only company-related data (e.g., products, jobs, events, etc.) is displayed " +"on the website. To display company-specific data, set the desired company in" +" the :guilabel:`Company` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:83 +msgid "Content availability" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:85 +msgid "" +"By default, pages, products, events, etc. created from the frontend (using " +"the :guilabel:`+New` button) are only available on the website from which it" +" was created. Records created from the backend, however, are made available " +"on all websites by default. The content's availability can be changed in the" +" backend, in the :guilabel:`Website` field. For example, for products, go to" +" :menuselection:`eCommerce --> Products`, then select the product and go to " +"the :guilabel:`Sales` tab. For forums, go to :menuselection:`Configuration " +"--> Forums`, then select the forum." +msgstr "" +"ตามค่าเริ่มต้น เพจ ผลิตภัณฑ์ กิจกรรม และอื่นๆ ที่สร้างจากส่วนหน้า " +"(โดยใช้ปุ่ม :guilabel:`+สร้าง`) " +"จะพร้อมใช้งานบนเว็บไซต์ที่ถูกสร้างขึ้นเท่านั้น อย่างไรก็ตาม " +"บันทึกที่สร้างจากส่วนหลังจะพร้อมใช้งานบนเว็บไซต์ทั้งหมดตามค่าเริ่มต้น " +"ความพร้อมใช้งานของเนื้อหาสามารถเปลี่ยนแปลงได้ในแบ็กเอนด์ในฟิลด์ " +":guilabel:`เว็บไซต์` ตัวอย่างเช่น สำหรับผลิตภัณฑ์ ไปที่ " +":menuselection:`อีคอมเมิร์ซ --> ผลิตภัณฑ์` จากนั้นเลือกผลิตภัณฑ์และไปที่แท็บ" +" :guilabel:`การขาย` สำหรับฟอรัม ให้ไปที่ :menuselection:`การกำหนดค่า --> " +"ฟอรั่ม` จากนั้นเลือกฟอรัม" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Website field in Forum form" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:98 +msgid "Records and features can be made available:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:100 +msgid "On all websites: leave the :guilabel:`Website` field empty;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:101 +msgid "Only on one website: set the :guilabel:`Website` field accordingly;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:102 +msgid "" +"On some websites: in this case, you should duplicate the item and set the " +":guilabel:`Website` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:106 +msgid "Website pages" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:108 +msgid "" +"To modify the website on which a page is to be published, proceed as " +"follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:110 +msgid "Go to :menuselection:`Website --> Site --> Pages`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:111 +msgid "" +"Open the search panel and select the website on which the page is currently " +"published." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:0 +msgid "Display pages per website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:116 +msgid "Tick the check box next to the page(s) you want to change." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:117 +msgid "" +"Click the :guilabel:`Website` field and select the website, or empty it to " +"publish the page on all websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:121 +msgid "" +"Each website must have its own homepage; you may not use the same homepage " +"for several websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:124 +msgid "eCommerce features" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:126 +msgid "" +"eCommerce features such as products, eCommerce categories, pricelists, " +"discounts, payment providers, etc. can be restricted to :ref:`a specific " +"website <website_field>`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:132 +msgid "" +"You can :doc:`allow your customers to use the same account " +"<../../ecommerce/ecommerce_management/customer_accounts>` on all of your " +"websites by enabling the :guilabel:`Shared Customer Accounts` check box in " +"the website settings." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:137 +msgid "Pricing" +msgstr "กำหนดราคา" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:139 +msgid "" +"Products can be priced differently based on the website using " +":ref:`pricelists <ecommerce/pricelists>`. The following configuration is " +"required:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:143 +msgid "" +"Scroll down to the :guilabel:`Shop - Products` section and select the " +":guilabel:`Pricelists` option :guilabel:`Multiple prices per product`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:145 +msgid "" +"Click :guilabel:`Pricelists` to define new pricelists or edit existing ones." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:146 +msgid "" +"Select the pricelist or click :guilabel:`New` to create a new one, then " +"select the :guilabel:`Configuration` tab and set the :guilabel:`Website` " +"field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:150 +#: ../../content/applications/websites/website/reporting.rst:5 +msgid "Reporting" +msgstr "การรายงาน" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:155 +msgid "" +"Each website has its own :ref:`analytics <website/analytics/plausible>`. To " +"switch between websites, click the buttons in the upper right corner." +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst-1 +msgid "Switch websites in analytics" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:162 +msgid "Other reporting data" +msgstr "" + +#: ../../content/applications/websites/website/configuration/multi_website.rst:164 +msgid "" +"Other reporting data such as eCommerce dashboard data, online sales analyses" +" and visitors can be grouped by website if necessary. Open the search panel " +"and select :guilabel:`Group by --> Website`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:3 +msgid "Forms spam protection" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:5 +msgid "" +":ref:`Cloudflare Turnstile <cloudflare-turnstile>` and :ref:`Google " +"reCAPTCHA v3 <google-recaptcha>` protect website forms against spam and " +"abuse. They attempt to distinguish between human and bot submissions using " +"non-interactive challenges based on telemetry and visitor behavior." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:10 +msgid "" +"**Cloudflare Turnstile is recommended** as it is possible to add an " +"interactive check if the automated check fails. Also, Google reCAPTCHA v3 is" +" limited to `1 million assessments per month per domain " +"<https://developers.google.com/recaptcha/docs/faq#are-there-any-qps-or-" +"daily-limits-on-my-use-of-recaptcha>`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:15 +msgid "" +"All pages using the :guilabel:`Form`, :guilabel:`Newsletter Block`, " +":guilabel:`Newsletter Popup` snippets, and the eCommerce :guilabel:`Extra " +"Step During Checkout` form are protected by both tools." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:20 +msgid "" +"`Cloudflare Turnstile's documentation " +"<https://developers.cloudflare.com/turnstile/>`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:21 +msgid "" +"`Google's reCAPTCHA v3 guide " +"<https://developers.google.com/recaptcha/docs/v3>`_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:26 +msgid "Cloudflare Turnstile configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:29 +msgid "On Cloudflare" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:31 +msgid "" +"`Create <https://dash.cloudflare.com/sign-up>`_ a Cloudflare account or use " +"an existing one and `log in <https://dash.cloudflare.com/login>`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:33 +msgid "On the dashboard navigation sidebar, click :guilabel:`Turnstile`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:34 +msgid "On the :guilabel:`Turnstile Sites` page, click :guilabel:`Add Site`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:35 +msgid "Add a :guilabel:`Site name` to identify it easily." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:36 +msgid "" +"Enter or select the website's :guilabel:`Domain` (e.g., *example.com* or " +"*subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:37 +msgid "Select a :guilabel:`Widget Mode`:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:39 +msgid "" +"The :guilabel:`Managed` mode is **recommended**, as visitors can be prompted" +" to check a box confirming they are human if deemed necessary by Turnstile." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Cloudflare Turnstile human verification widget" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:45 +msgid "" +"For the :guilabel:`Non-interactive` and :guilabel:`Invisible` modes, " +"visitors are never prompted to interact. In :guilabel:`Non-interactive` " +"mode, a loading widget can be displayed to warn visitors that Turnstile " +"protects the form; however, the widget is not supported by Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:50 +msgid "" +"If the Turnstile check fails, visitors are not able to submit the form, and " +"the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Cloudflare Turnstile verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:56 +#: ../../content/applications/websites/website/pages.rst:27 +msgid "Click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "Adding a website to Cloudflare Turnstile" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:61 +msgid "" +"The generated keys are then displayed. Leave the page open for convenience, " +"as copying the keys in Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:65 +#: ../../content/applications/websites/website/configuration/spam_protection.rst:109 +msgid "On Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:67 +msgid "" +"From the database dashboard, click :guilabel:`Settings`. Under " +":guilabel:`Integrations`, enable :guilabel:`Cloudflare Turnstile` and click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:69 +msgid "" +"Open the Cloudflare Turnstile page, copy the :guilabel:`Site Key`, and paste" +" it into the :guilabel:`CF Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:71 +msgid "" +"Open the Cloudflare Turnstile page, copy the :guilabel:`Secret Key`, and " +"paste it into the :guilabel:`CF Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:73 +#: ../../content/applications/websites/website/configuration/spam_protection.rst:125 +#: ../../content/applications/websites/website/configuration/translate.rst:95 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:76 +msgid "" +"Navigate to Turnstile on your Cloudflare account to view the solve rates and" +" access more settings." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:82 +msgid "reCAPTCHA v3 configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:85 +msgid "On Google" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:87 +msgid "" +"Open `the reCAPTCHA website registration page " +"<https://www.google.com/recaptcha/admin/create>`_. Log in or create a Google" +" account if necessary." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:90 +msgid "On the website registration page:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:92 +msgid "Give the website a :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:93 +msgid "Leave the :guilabel:`reCAPTCHA type` on :guilabel:`Score based (v3)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:94 +msgid "" +"Enter one or more :guilabel:`Domains` (e.g., *example.com* or " +"*subdomain.example.com*)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:95 +msgid "" +"Under :guilabel:`Google Cloud Platform`, a project is automatically selected" +" if one was already created with the logged-in Google account. If not, one " +"is automatically created. Click :guilabel:`Google Cloud Platform` to select " +"a project yourself or rename the automatically created project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:99 +msgid "Agree to the terms of service." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:100 +msgid "Click :guilabel:`Submit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "reCAPTCHA website registration example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:105 +msgid "" +"A new page with the generated keys is then displayed. Leave it open for " +"convenience, as copying the keys to Odoo is required next." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:111 +msgid "" +"From the database dashboard, click :guilabel:`Settings`. Under " +":guilabel:`Integrations`, enable :guilabel:`reCAPTCHA` if needed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:115 +msgid "" +"Do not disable the :guilabel:`reCAPTCHA` feature or uninstall the " +":guilabel:`Google reCAPTCHA integration` module, as many other modules would" +" also be removed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:118 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Site key`, and paste it " +"into the :guilabel:`Site Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:120 +msgid "" +"Open the Google reCAPTCHA page, copy the :guilabel:`Secret key`, and paste " +"it into the :guilabel:`Secret Key` field in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:122 +msgid "" +"Change the default :guilabel:`Minimum score` (`0.50`) if necessary, using a " +"value between `1.00` and `0.00`. The higher the threshold is, the more " +"difficult it is to pass the reCAPTCHA, and vice versa." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:127 +msgid "" +"You can notify visitors that reCAPTCHA protects a form. To do so, open the " +"website editor and navigate to the form. Then, click somewhere on the form, " +"and on the right sidebar's :guilabel:`Customize` tab, toggle :guilabel:`Show" +" reCAPTCHA Policy` found under the :guilabel:`Form` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst-1 +msgid "reCAPTCHA policy message displayed on a form" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:136 +msgid "" +"If the reCAPTCHA check fails, the following error message is displayed:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:0 +msgid "Google reCAPTCHA verification error message" +msgstr "" + +#: ../../content/applications/websites/website/configuration/spam_protection.rst:142 +msgid "" +"Analytics and additional settings are available on `Google's reCAPTCHA " +"administration page <https://www.google.com/recaptcha/admin/>`_. For " +"example, you can receive email alerts if Google detects suspicious traffic " +"on your website or view the percentage of suspicious requests, which could " +"help you determine the right minimum score." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:3 +msgid "Translations" +msgstr "การแปล" + +#: ../../content/applications/websites/website/configuration/translate.rst:5 +msgid "" +"The contents of your website pages (i.e., text strings) can be translated " +"into different languages directly on your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:8 +msgid "" +"Your website is displayed in the language that matches the visitor's " +"browser's language, unless that particular language has not been installed. " +"In this case, the website is displayed in the :ref:`default language " +"<translate/default-language>`. The visitor can still select another language" +" in the language menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:14 +msgid "Installing languages" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:16 +msgid "" +"To translate your website, you first have to add the required languages:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:18 +msgid "Go to your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:19 +msgid "Scroll to the bottom of the page to the **language menu**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:20 +msgid "Click the language and select :guilabel:`Add a language`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Add a language to your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:25 +msgid "" +"Click the :guilabel:`Languages` field and select the required language from " +"the drop-down list. Repeat this step for each additional language." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:27 +msgid "Click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:30 +msgid "" +"You can also edit your website's languages from the backend, in the " +":guilabel:`Settings`. Go to :menuselection:`Website –> Configuration –> " +"Settings` and add/remove the required languages in the :guilabel:`Languages`" +" field, in the :guilabel:`Website info` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:37 +msgid "Default language" +msgstr "ค่าเริ่มต้นภาษา" + +#: ../../content/applications/websites/website/configuration/translate.rst:39 +msgid "" +"If the language of the visitor's browser is not installed on your website, " +"the content is displayed in the default language." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:42 +msgid "" +"To define a default language, go to :menuselection:`Website –> Configuration" +" –> Settings`, and select a language in the :guilabel:`Default` field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:46 +msgid "" +"This field is visible only if multiple languages are already configured for " +"your website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:49 +msgid "Translating the contents" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:51 +msgid "" +"Once the languages have been added, you can translate the contents of your " +"website. To do so, go to your website, select the language from the language" +" menu and click the :guilabel:`Translate` button on the right part of the " +"task bar to activate the **translation mode**." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst-1 +msgid "Translate button" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:58 +msgid "As a result:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:60 +msgid "" +"Text strings that have already been translated are highlighted in green;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:61 +msgid "Text strings that need to be translated are highlighted in yellow." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst-1 +msgid "Text to be translated highlighted in yellow" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:66 +msgid "" +"You can then replace the original text with the translation by clicking the " +"block, editing its contents and saving." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:70 +msgid "" +"Once the languages have been installed, you can also translate some items " +"(e.g., the product's name and description) from the backend (e.g., in the " +"product template). To do so, click the language code (e.g., :guilabel:`EN`) " +"next to the text you want to translate (e.g., the product name) and add the " +"translation." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Translate product-related items." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:78 +msgid "" +"You can also :doc:`export/import translations " +"<../../../../developer/howtos/translations>` to translate multiple items " +"(e.g., product names and descriptions) in one go." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:82 +msgid "Language selector menu" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:84 +msgid "To add a language selector menu:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:86 +msgid "Go to your website and click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:87 +msgid "" +"Select the block where you want to add the language selector menu (e.g., the" +" header)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:88 +msgid "Select the :guilabel:`Customize` tab." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:89 +msgid "" +"In the :guilabel:`Navbar` section, set the :guilabel:`Language selector` " +"field to either :guilabel:`Dropdown` or :guilabel:`Inline`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:0 +msgid "Add a language selector menu." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:3 +msgid "Unsplash" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:5 +msgid "" +"**Unsplash** is a recognized stock photography library integrated with Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:7 +msgid "" +"If your database is hosted on **Odoo Online**, you can access Unsplash " +"pictures without configuration." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:10 +msgid "" +"If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:12 +msgid "" +"To **generate an Unsplash access key**, create or sign in to an `Unsplash " +"account <https://unsplash.com>`_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:15 +msgid "" +"Access your `applications dashboard " +"<https://unsplash.com/oauth/applications>`_, click :guilabel:`New " +"Application`, select all checkboxes, and click :guilabel:`Accept terms`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:18 +msgid "" +"In the pop-up window, enter your :guilabel:`Application Name`, starting with" +" the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as" +" an Odoo instance. Then, add a :guilabel:`Description` and click " +":guilabel:`Create application`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:22 +msgid "" +"On the application details page, scroll down to the :guilabel:`Keys` section" +" and copy the :guilabel:`Access Key` and :guilabel:`Application ID`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:25 +msgid "" +"In Odoo, go to :menuselection:`General Settings` and enable the " +":guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash " +":guilabel:`Access Key` and :guilabel:`Application ID`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/unsplash.rst:29 +msgid "" +"As a non-Odoo Online user, you are limited to a test key with a maximum of " +"50 Unsplash requests per hour." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:3 +msgid "Mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:5 +msgid "" +"The **mail groups** feature allows website visitors to have a public " +"discussion by email. They can join a group to receive emails from other " +"group members (i.e., website users who have subscribed to the group) and " +"send new ones to all group members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:9 +msgid "" +"To activate the feature, :ref:`install <general/install>` the " +":guilabel:`Website Mail Group` (`website_mail_group`) module." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:13 +msgid "" +"The **mail groups** feature is not to be confused with the " +":doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing " +"app." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:19 +msgid "Configuring mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:21 +msgid "To configure mail groups, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:23 +msgid "" +"Configure a custom email alias domain by accessing the **General settings**," +" scrolling down to the :guilabel:`Discuss` section, enabling the " +":guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias " +"domain` (e.g., `@mycompany.com`)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:26 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Mailing Lists`, then " +"click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:27 +msgid "" +"Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:28 +msgid "" +"Enable :guilabel:`Moderate this group` and specify the " +":guilabel:`Moderators` if you wish to :ref:`moderate messages " +"<website/mailing_lists/moderate>` from this group. Alternatively, if the " +"group is not moderated, you can define :guilabel:`Responsible Users` who can" +" manage the messages in the group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:32 +msgid "" +"In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:34 +msgid "" +":guilabel:`Everyone`: to make the mail group public so anyone can subscribe " +"to it;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:35 +msgid "" +":guilabel:`Members only`: to only allow users defined as members to " +"subscribe to the mail group;" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:36 +msgid "" +":guilabel:`Selected group of users`: to only allow users from the " +":guilabel:`Authorized group` to subscribe to the mail group." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:39 +msgid "" +"If the mail group is moderated, you can automatically notify authors when " +"their message is pending moderation by enabling :guilabel:`Automatic " +"notification` in the :guilabel:`Notify Members` tab and writing the " +":guilabel:`Notification message`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:42 +msgid "" +"If you wish to send out guidelines to new subscribers, enable " +":guilabel:`Send guidelines to new subscribers` and write them in the " +":guilabel:`Guidelines` tab. This is particularly useful when the mail group " +"is moderated." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:47 +msgid "Using mail groups" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:50 +msgid "Subscribing/unsubscribing" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:52 +msgid "" +"Based on the :ref:`configuration of the mail group " +"<website/mailing_lists/configure_groups>`, users can subscribe to and " +"unsubscribe from mail groups from the website page (`/groups` by default)." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst-1 +msgid "Mail group web page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:58 +msgid "" +"Internal users can also do this from :menuselection:`Website --> " +"Configuration --> Mailing Lists`, using the :guilabel:`Join` and " +":guilabel:`Leave` buttons." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:62 +msgid "Sending messages" +msgstr "กำลังส่งข้อความ" + +#: ../../content/applications/websites/website/mail_groups.rst:64 +msgid "" +"To send messages to a mail group, website users can email the :ref:`mail " +"group's email address <website/mailing_lists/configure_groups>`. Internal " +"users can also create messages directly from Odoo. To do so, go to " +":menuselection:`Website --> Configuration --> Mailing Lists`, select the " +"mail group, click the :guilabel:`Emails` smart button, and click " +":guilabel:`New`. Then, fill in the fields and click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:71 +msgid "" +"The list of messages can also be accessed by selecting the group from the " +"`/groups` website page." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:73 +msgid "" +"Group members can also unsubscribe from the group, access the mail group " +"page, and send emails to the group using the URLs in the footer of any group" +" email they have received." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "URLs in the footer of a group email." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:82 +msgid "Moderating mail group messages" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:84 +msgid "" +"If the :guilabel:`Moderate this group` feature has been enabled for the " +":ref:`mail group <website/mailing_lists/configure_groups>`, one of the " +":guilabel:`Moderators` must approve the group's messages before they are " +"dispatched to the other members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:88 +msgid "" +"To moderate messages, go to :menuselection:`Website --> Configuration --> " +"Mailing Lists`, select the mail group, and click the :guilabel:`To review` " +"smart button. You can moderate messages using the buttons at the end of the " +"message line or select a message to view its content and moderate it " +"accordingly." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:0 +msgid "Moderation buttons in the message line." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:96 +msgid "The following actions are available:" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:98 +msgid "" +":guilabel:`Accept`: to accept the email and send it to the mail group " +"members." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:99 +msgid "" +":guilabel:`Reject`: to reject the email. In the pop-up window that opens, " +"click :guilabel:`Reject Silently` to reject the email without notifying the " +"author, or specify an explanation for rejecting the message, then click " +":guilabel:`Send & Reject` to reject the message and send the explanation to " +"the author." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:103 +msgid "" +":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept " +"all of their emails. As a result, a :ref:`moderation rule " +"<website/mailing_lists/moderate>` is created for the author's email address " +"with the status :guilabel:`Always allow`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:106 +msgid "" +":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all " +"their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban " +"the author without notifying them, or specify an explanation, then click " +":guilabel:`Send & Ban` to ban the author and send them the explanation. As a" +" result, a :ref:`moderation rule <website/mailing_lists/moderate>` is " +"created for the author's email address with the status :guilabel:`Permanent " +"ban`." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:113 +msgid "" +"Messages can also be moderated from the group's list of messages. Go to " +":menuselection:`Website --> Groups --> Mailing List Groups`, select the mail" +" group and click the :guilabel:`Emails` smart button." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:120 +msgid "Whitelisting/Blacklisting authors" +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:122 +msgid "" +"You can whitelist or blacklist an author either directly :ref:`from a mail " +"group message <website/mailing_lists/moderate>`, or by creating a moderation" +" rule. To do so, go to :menuselection:`Website --> Configuration --> " +"Moderation Rules` and click :guilabel:`New`. Then, select the " +":guilabel:`Group`, specify the author's :guilabel:`Email` and set the " +":guilabel:`Status` field." +msgstr "" + +#: ../../content/applications/websites/website/mail_groups.rst:129 +msgid "" +"You can also access the mail group's moderation rules by going to " +":menuselection:`Website --> Configuration --> Mailing Lists`, selecting the " +"group, then clicking the :guilabel:`Moderations` smart button." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:5 +msgid "Pages" +msgstr "หน้า" + +#: ../../content/applications/websites/website/pages.rst:7 +msgid "" +"Odoo allows you to create pages for your website and customize their content" +" and appearance to your needs." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:11 +msgid "" +"*Static* pages are pages that have stable content, such as the homepage. You" +" can manually create new ones, define their URL, adapt their " +":ref:`properties <website/page_properties>`, etc. *Dynamic* pages, on the " +"other hand, are generated dynamically. All pages generated automatically by " +"Odoo, for example when you install an app or module (e.g., `/shop` or " +"`/blog`) or publish a new product or blog post, are dynamic pages and are " +"therefore managed differently." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:18 +msgid "Page creation" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:20 +msgid "" +"Website pages can be created from the **frontend** and the **backend**. To " +"create a new website page, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:23 +msgid "" +"Either open the **Website** app, click :guilabel:`+ New` in the top-right " +"corner, then select :guilabel:`Page`;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:25 +msgid "" +"Or go to :menuselection:`Website --> Site --> Pages` and click " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:26 +msgid "" +"Enter a :guilabel:`Page Title`; this title is used in the menu, as well as " +"in the page's URL." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:28 +msgid "" +"Customize the page's content and appearance using the website builder, then " +"click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:30 +msgid ":ref:`Publish <website/un-publish-page>` the page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:33 +msgid "" +"Disable :guilabel:`Add to menu` if the page should not appear in the menu." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:36 +msgid "Page management" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:41 +msgid "Publishing/unpublishing pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:43 +msgid "" +"Pages need to be published to make them accessible to website visitors. To " +"publish or unpublish a page, access it, then toggle the switch in the upper-" +"right corner from :guilabel:`Unpublished` to :guilabel:`Published`, or vice " +"versa." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst-1 +msgid "Unpublished/Published toggle" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:51 +msgid "It is also possible to:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:53 +msgid "" +"publish/unpublish a page from the :ref:`page properties " +"<website/page_properties>`, where you can define a publishing date and/or " +"restrict the page's visibility if needed;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:55 +msgid "" +"publish/unpublish several pages at once: go to :menuselection:`Website --> " +"Site --> Pages`, select the pages, then, click :guilabel:`Action` and select" +" :guilabel:`Publish` or :guilabel:`Unpublish`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:60 +msgid "Homepage" +msgstr "โฮมเพจ" + +#: ../../content/applications/websites/website/pages.rst:62 +msgid "" +"By default, when you create a website, Odoo creates a dedicated " +":guilabel:`Home` page, but you can define any website page as your homepage." +" To do so, go to :menuselection:`Website --> Configuration --> Settings`, " +"then, in the :guilabel:`Website info` section, define the URL of the desired" +" page in the field :guilabel:`Homepage URL` (e.g., `/shop`)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:67 +msgid "" +"Alternatively, you can define any static page as your homepage by going to " +":menuselection:`Website --> Site --> Properties`. Select the " +":guilabel:`Publish` tab and enable :guilabel:`Use as Homepage`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:73 +msgid "Page properties" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:75 +msgid "" +"To modify a static page's properties, access the page you wish to modify, " +"then go to :menuselection:`Site --> Properties`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:78 +msgid "The :guilabel:`Name` tab allows you to:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:80 +msgid "rename the page using the :guilabel:`Page Name` field;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:81 +msgid "" +"modify the :guilabel:`Page URL`. In this case, you can redirect the old URL " +"to the new one if needed. To do so, enable :guilabel:`Redirect Old URL`, " +"then select the :guilabel:`Type` of :ref:`redirection <website/URL-" +"redirection>`:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:85 +msgid ":guilabel:`301 Moved permanently`: to redirect the page permanently;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:86 +msgid ":guilabel:`302 Moved temporarily`: to redirect the page temporarily." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:0 +msgid "Redirect old URL" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:91 +msgid "" +"You can further adapt the page's properties in the :guilabel:`Publish` tab:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:93 +msgid "" +":guilabel:`Show in Top Menu`: Disable if you don't want the page to appear " +"in the menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:94 +msgid "" +":guilabel:`Use as Homepage`: Enable if you want the page to be the homepage " +"of your website;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:95 +msgid "" +":guilabel:`Indexed`: Disable if you don't want the page to be shown in " +"search engine results;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:96 +msgid ":guilabel:`Published`: Enable to publish the page;" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:97 +msgid "" +":guilabel:`Publishing Date`: To publish the page at a specific moment, " +"select the date, click the clock icon to set the time, then click the green " +"check mark to validate your selection." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:99 +msgid ":guilabel:`Visibility`: Select who can access the page:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:101 +msgid ":guilabel:`All`" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:102 +msgid ":guilabel:`Signed In`" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:103 +msgid "" +":guilabel:`Restricted Group`: Select the :doc:`user access group(s) " +"</applications/general/users/access_rights>` in the :guilabel:`Authorized " +"group` field." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:105 +msgid "" +":guilabel:`With Password`: Enter the password in the :guilabel:`Password` " +"field." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:108 +msgid "" +"*Some* of these properties can also be modified from :menuselection:`Website" +" --> Site --> Pages`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:111 +msgid "Duplicating pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:113 +msgid "" +"To duplicate a page, access the page, then go to :menuselection:`Site --> " +"Properties` and click :guilabel:`Duplicate Page`. Enter a :guilabel:`Page " +"Name`, then click :guilabel:`OK`. By default, the new page is added after " +"the duplicated page in the menu, but you can remove it from the menu or " +"change its position using the :doc:`menu editor <pages/menus>`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:121 +msgid "Deleting pages" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:123 +msgid "To delete a page, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:125 +msgid "" +"Access the page, then go to :menuselection:`Site --> Properties` and click " +":guilabel:`Delete Page`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:127 +msgid "" +"A pop-up window appears on the screen with all links referring to the page " +"you want to delete, organized by category. To ensure website visitors don't " +"land on a 404 error page, you must update all the links on your website " +"referring to the page. To do so, expand a category, then click on a link to " +"open it in a new window. Alternatively, you can set up a :ref:`redirection " +"<website/URL-redirection>` for the deleted page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:132 +msgid "" +"Once you have updated the links (or set up a :ref:`redirection <website/URL-" +"redirection>`), select the :guilabel:`I am sure about this` check box, then " +"click :guilabel:`OK`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:138 +msgid "URL redirects" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:140 +msgid "" +"Redirecting URLs consists in sending visitors and search engines to a URL " +"that is different from the one they originally requested. This technique is " +"used, for example, to prevent broken links when you :ref:`delete a page " +"<website/delete-page>`, :ref:`modify its URL <website/page_properties>`, or " +"move your site to a new :doc:`domain " +"</administration/maintain/domain_names>`. It can also be used to improve " +":doc:`pages/seo`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:146 +msgid "" +"To access existing URL redirections and create new ones, :doc:`activate the " +"developer mode </applications/general/developer_mode>` and go to " +":menuselection:`Website --> Configuration --> Redirects`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:151 +msgid "" +"A record is added automatically every time you :ref:`modify a page's URL " +"<website/page_properties>` and enable :guilabel:`Redirect Old URL`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:153 +msgid "You can set up redirections for static and dynamic pages." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:155 +msgid "" +"To create a new redirection, click the :guilabel:`New` button, then fill in " +"the fields:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:157 +msgid ":guilabel:`Name`: Enter a name to identify the redirect." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:158 +msgid ":guilabel:`Action`: Select the type of redirection:" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:160 +msgid "" +":guilabel:`404 Not found`: visitors are redirected to a 404 error page when " +"they try to access the page." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:162 +msgid "" +":guilabel:`301 Moved Permanently`: for permanent redirections of static " +"pages; the new URL is shown in search engine results and the redirect is " +"cached by browsers." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:164 +msgid "" +":guilabel:`302 Moved Temporarily`: for short-term redirections, for example," +" if you are redesigning or updating the page. The new URL is neither cached " +"by browsers, nor shown in search engine results." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:167 +msgid "" +":guilabel:`308 Redirect / Rewrite`: for permanent redirections of dynamic " +"pages; the new URL is shown in search engine results and the redirect is " +"cached by browsers. Use this redirect type to rename a dynamic page, for " +"example, if you wish to rename `/shop` into `/market`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:171 +msgid "" +":guilabel:`URL from`: Enter the URL to be redirected (e.g., `/about-the-" +"company`) or search for the desired dynamic page and select it from the " +"list." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:173 +msgid "" +":guilabel:`URL to`: For 301, 302 and 308 redirects, enter the URL to be " +"redirected to. If you want to redirect to an external URL, make sure to " +"include the protocol (e.g., `https://`)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:175 +msgid ":guilabel:`Website`: Select a specific website." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:176 +msgid "" +":guilabel:`Sequence`: to define the order in which redirections are " +"performed, e.g., in the case of redirect chains (i.e., a series of redirects" +" where one URL is redirected to another one, which is itself further " +"redirected to another URL)." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:180 +msgid "Toggle the :guilabel:`Activate` switch to deactivate the redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:183 +msgid "" +"404, 301 and 302 redirections only work if the original page has been " +":ref:`unpublished <website/un-publish-page>` or :ref:`deleted " +"<website/delete-page>`." +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:187 +msgid "" +"`Google documentation on redirects and search " +"<https://developers.google.com/search/docs/crawling-" +"indexing/301-redirects>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages.rst:188 +msgid ":doc:`pages/seo`" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:3 +msgid "Menus" +msgstr "เมนู" + +#: ../../content/applications/websites/website/pages/menus.rst:5 +msgid "" +"Menus are used to organize your website’s content and help visitors navigate" +" through your web pages effectively. User-friendly and well-structured " +"website menus also play a crucial role in improving :doc:`search engine " +"rankings <seo>`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:9 +msgid "" +"Odoo allows you to customize the content and appearance of your website's " +"menu to your needs." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:12 +msgid "Menu editor" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:14 +msgid "" +"The menu editor allows you to edit your website's menu and add :ref:`regular" +" menu items <website/regular-menus>` and :ref:`mega menus <website/mega-" +"menus>`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:17 +msgid "" +"To edit your website's menu, go to :menuselection:`Website --> Site --> Menu" +" Editor`. From there, you can:" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:20 +msgid "" +"**rename** a menu item or change its URL using the :guilabel:`Edit Menu " +"Item` icon;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:21 +msgid "**delete** a menu item using the :guilabel:`Delete Menu Item` icon;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:22 +msgid "" +"**move** a menu item by dragging and dropping it to the desired place in the" +" menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:23 +msgid "" +"**create a regular drop-down menu** by dragging and dropping the sub-menu " +"items to the right, underneath their parent menu." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst-1 +msgid "Menu editor with sub-menus" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:31 +msgid "" +"You can also access the menu editor by clicking :guilabel:`Edit`, selecting " +"any menu item and clicking the :guilabel:`Edit Menu` icon." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:0 +msgid "Access the Menu editor while in Edit mode." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:40 +msgid "Adding regular menu items" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:42 +msgid "" +"By default, pages are added to the menu as regular menu items when " +":doc:`they are created <../pages>`. You can also add regular menu items from" +" the menu editor by clicking :guilabel:`Add Menu Item`. Enter the " +":guilabel:`Name` and URL of the related page in the pop-up window that " +"appears on the screen and click :guilabel:`OK`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:48 +msgid "" +"In the :guilabel:`URL or Email` field, you can type `/` to search for a page" +" on your website or `#` to search for an existing custom anchor." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:54 +msgid "Adding mega menus" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:56 +msgid "" +"Mega menus are similar to drop-down menus, but instead of a simple list of " +"sub-menus, they display a panel divided into groups of navigation options. " +"This makes them suitable for websites with large amounts of content, as they" +" can help include all of your web pages in the menu while still making all " +"menu items visible at once. Mega menus can also be structured more visually " +"than regular drop-down menus, for example, through layout, typography, and " +"icons." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst-1 +msgid "Mega menu in the navigation bar." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:65 +msgid "" +"To create a mega menu, go to :menuselection:`Website --> Site --> Menu " +"Editor` and click :guilabel:`Add Mega Menu Item`. Enter the :guilabel:`Name`" +" of the mega menu in the pop-up, click :guilabel:`OK`, then " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:69 +msgid "" +"To adapt the options and layout of the mega menu, click it in the navigation" +" bar, then click :guilabel:`Edit`. Mega menus are composed of building " +"blocks, which means you can customize each component individually using " +"inline formatting, as well as the options available in the " +":guilabel:`Customize` tab in the website builder. For example, you can:" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:74 +msgid "edit the text directly in the building block;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:75 +msgid "" +"edit a menu item's URL by selecting the menu item, then clicking the " +":guilabel:`Edit link` button in the small preview pop-up. Type `/` to search" +" for a page on your website, or `#` to search for an existing custom anchor." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:0 +msgid "Edit a mega menu option." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:82 +msgid "" +"move a menu item by dragging and dropping the related block to the desired " +"position in the mega menu;" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:84 +msgid "delete a menu item by deleting the related block." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:87 +msgid "" +"You can adapt the general layout of the mega menu by selecting the desired " +":guilabel:`Template` and :guilabel:`Size` in the :guilabel:`Mega menu` " +"section in the :guilabel:`Customize` tab in the website builder." +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:92 +msgid "Header and navigation bar appearance" +msgstr "" + +#: ../../content/applications/websites/website/pages/menus.rst:94 +msgid "" +"To customize the appearance of your website's menu, click :guilabel:`Edit`, " +"then select the navigation bar or any menu item. You can then adapt the " +"fields in the :guilabel:`Header` and :guilabel:`Navbar` sections in the " +":guilabel:`Customize` tab in the website builder." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:3 +msgid "Search Engine Optimisation (SEO)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:5 +msgid "" +"Search Engine Optimization (SEO) is a set of good practices to optimize your" +" website so that you get a better ranking in search engines like Google. In " +"short, a good SEO allows you to get more visitors." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:9 +msgid "" +"Some examples of SEO rules: your web pages should load fast, your page " +"should have one and only one title ``<h1>``, meta tags (alt-tag, title-tag) " +"should be consistent with the content, your website should have a " +"``/sitemap.xml`` file, etc." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:15 +msgid "" +"To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo " +"abstracts all the technical complexities of SEO and handles everything for " +"you, in the best possible way. This will be explained here below." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:20 +msgid "" +"But first, let see how you can easily boost your ranking by finetuning the " +"content and the meta tags of your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:24 +msgid "Meta Tags" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:27 +msgid "Title, Description" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:29 +msgid "" +"Every web page should define the ``<title>`` and ``<description>`` meta " +"data. These information elements are used by search engines to promote your " +"website. They are automatically generated based on page title & content, but" +" you can finetune them. Make sure they fit the content of the page, " +"otherwise you will be downgraded by search engines." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:39 +msgid "Keywords" +msgstr "คำสำคัญ" + +#: ../../content/applications/websites/website/pages/seo.rst:41 +msgid "" +"In order to write quality content and boost your traffic, Odoo provides a " +"``<keyword>`` finder. Those keywords are the searches you want to head " +"towards your website. For each keyword, you see how it is used in the " +"content (H1, H2, page title, page description, page content) and what are " +"the related searches in Google. The more keywords are used the better." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:51 +msgid "" +"If your website is in multiple languages, you can use the Promote tool for " +"every language of a single page and set specific title, description and " +"search tags." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:56 +msgid "Content is King" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:58 +msgid "" +"When it comes to SEO, content is usually king. Odoo provides several modules" +" to help you build your website content:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:61 +msgid "**Odoo Blogs**: write great contents." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:63 +msgid "" +"**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their " +"content is automatically indexed on the web page. Example: " +"`odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-" +"channel-1>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:67 +msgid "" +"**Odoo Forum**: let your community create contents for you. Example: " +"`odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com" +" landing pages)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:71 +msgid "" +"**Odoo Mailing List Archive**: publish mailing list archives on your " +"website. Example: `odoo.com/groups/community-59 " +"<https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:77 +msgid "" +"The 404 page is a regular page, that you can edit like any other page in " +"Odoo. That way, you can build a great 404 page to redirect to the top " +"content of your website when visitors get lost in invalid URLs." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:82 +msgid "Use Social Networks" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:84 +msgid "" +"Social media is built for mass sharing. If lots of people share your content" +" on social media, then it's likely more people will link to it, and links " +"are a huge factor for SEO ranking." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:88 +msgid "Odoo embeds several tools to share content through social media:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:91 +msgid "Social Network" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:93 +msgid "" +"Odoo allows to link all your social network accounts in your website footer." +" All you have to do is to refer all your accounts in your company settings." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:100 +msgid "Social Share" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:102 +msgid "" +"Drop the building block *Share* on any page you want your visitors to share." +" By clicking the icon, they are prompted to share the page in their social " +"media wall." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:109 +msgid "" +"Most social media use a picture of the picture to decorate the share post. " +"Odoo uses the website logo by default but you can choose any other image of " +"your page in the Promote tool." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:117 +msgid "Facebook Page" +msgstr "หน้าเพจ Facebook" + +#: ../../content/applications/websites/website/pages/seo.rst:119 +msgid "" +"Drop the building block *Facebook Page* to display a widget of your Facebook" +" business page and encourage visitors to follow it. You can display the " +"timeline, the next events and the messages." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:124 +msgid "Twitter Scroller" +msgstr "ตัวเลื่อนทวิตเตอร์" + +#: ../../content/applications/websites/website/pages/seo.rst:126 +msgid "" +"Display the Twitter feeds with customer satifaction on your website. This " +"will increase the number of tweets and shares." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:130 +msgid "Test Your Website" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:132 +msgid "" +"You can compare how your website rank, in terms of SEO, against Odoo using " +"WooRank free services: `woorank.com <https://www.woorank.com>`_" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:137 +msgid "URLs Handling" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:139 +msgid "This section sheds some light on how Odoo makes URLs SEO-friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:142 +msgid "URLs Structure" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:144 +msgid "A typical Odoo URL will look like this:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:146 +msgid "https://www.mysite.com/fr\\_FR/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:148 +msgid "With the following components:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:150 +msgid "**https://** = Protocol" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:152 +msgid "**www.mysite.com** = your domain name" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:154 +msgid "" +"**/fr\\_FR** = page language. This part of the URL is removed if the visitor" +" browses the main language of the website Thus, the main version of this " +"page is: https://www.mysite.com/shop/product/my-great-product-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:159 +msgid "" +"**/shop/product** = every module defines its own namespace (/shop is for the" +" catalog of the eCommerce module, /shop/product is for a product page)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:163 +msgid "" +"**my-great-product** = by default, this is the slugified title of the " +"product this page refers to. But you can customize it for SEO purposes. A " +"product named \"Pain carré\" will be slugified to \"pain-carre\". Depending " +"on the namespace, this could be different objects (blog post, page title, " +"forum post, forum comment, product category, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:170 +msgid "**-31** = the unique ID of the product" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:172 +msgid "" +"Note that any dynamic component of an URL can be reduced to its ID. As an " +"example, the following URLs all do a 301 redirect to the above URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:175 +msgid "https://www.mysite.com/fr\\_FR/shop/product/31 (short version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:177 +msgid "http://mysite.com/fr\\_FR/shop/product/31 (even shorter version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:179 +msgid "" +"http://mysite.com/fr\\_FR/shop/product/other-product-name-31 (old product " +"name)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:182 +msgid "" +"Some URLs have several dynamic parts, like this one (a blog category and a " +"post):" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:185 +msgid "https://www.odoo.com/blog/company-news-5/post/the-odoo-story-56" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:187 +msgid "In the above example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:189 +msgid "*Company News* is the title of the blog" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:191 +msgid "*The Odoo Story* is the title of a specific blog post" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:193 +msgid "" +"When an Odoo page has a pager, the page number is set directly in the URL " +"(does not have a GET argument). This allows every page to be indexed by " +"search engines. Example:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:197 +msgid "https://www.odoo.com/blog/page/3" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:200 +msgid "Changes in URLs & Titles" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:202 +msgid "" +"When the URL of a page changes (e.g. a more SEO friendly version of your " +"product name), you don't have to worry about updating all links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:205 +msgid "Odoo will automatically update all its links to the new URL." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:207 +msgid "" +"If external websites still points to the old URL, a 301 redirect will be " +"done to route visitors to the new address of the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:210 +msgid "As an example, this URL:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:212 +msgid "http://mysite.com/shop/product/old-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:214 +msgid "Will automatically redirect to:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:216 +msgid "http://mysite.com/shop/product/new-and-better-product-name-31" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:218 +msgid "" +"In short, just change the title of a blog post or the name of a product, and" +" the changes will apply automatically everywhere in your website. The old " +"link still functions when used by external websites, via a 301 redirect, " +"maintaining the SEO link juice." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:224 +msgid "HTTPS" +msgstr "HTTPS" + +#: ../../content/applications/websites/website/pages/seo.rst:226 +msgid "" +"Search engines boost ranking of secure HTTPS/SSL websites. So, by default " +"all Odoo Online instances are fully based on HTTPS. If the visitor accesses " +"your website through a non HTTPS url, it gets a 301 redirect to its HTTPS " +"equivalent." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:232 +msgid "Links: Nofollow Strategy" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:234 +msgid "" +"The more a page is linked from external and quality websites, the better it " +"is for your SEO." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:237 +msgid "Here are Odoo strategies to manage links:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:239 +msgid "" +"Every link you add to your website is \"dofollow\", which means that this " +"link will contribute to the SEO Juice for the linked page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:243 +msgid "" +"Every link posted by a contributor (forum post, blog comment, etc.) that " +"links to your own website is \"dofollow\" too." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:246 +msgid "" +"But every link posted by a contributor that links to an external website is " +"\"nofollow\". In that way, you do not run the risk of people posting links " +"on your website to third-party websites which have a bad reputation." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:251 +msgid "" +"Note that, when using the forum, contributors having a lot of Karma can be " +"trusted. In such case, their links will not have any ``rel=\"nofollow\"`` " +"attribute." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:256 +msgid "Multi-Language Support" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:261 +msgid "Multi-Language URLs" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:263 +msgid "" +"If you run a website in multiple languages, the same content will be " +"available in different URLs, depending on the language used:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:266 +msgid "" +"https://www.mywebsite.com/shop/product/my-product-1 (main language, English " +"here)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:268 +msgid "" +"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1 (French " +"version)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:270 +msgid "" +"In this example, fr\\_FR is the language of the page. You can even have " +"several variations of the same language: pt\\_BR (Portuguese from Brazil) , " +"pt\\_PT (Portuguese from Portugal)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:275 +msgid "Language Annotation" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:277 +msgid "" +"To let search engines know that the second URL is the French translation of " +"the first URL, Odoo will add an HTML link element in the header. In the HTML" +" <head> section of the main version, Odoo automatically adds a link element " +"pointing to the translated versions of that webpage;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:282 +msgid "" +"<link rel=\"alternate\" hreflang=\"fr\" " +"href=\"https://www.mywebsite.com\\/fr\\_FR/shop/product/mon-produit-1\"/>" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:285 +msgid "With this approach:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:287 +msgid "" +"Search engines will redirect to the right language according to the visitor " +"language." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:290 +msgid "" +"You do not get penalized by search engines if your page is not translated " +"yet. Indeed, it's not a duplicated content, but a different version of the " +"same content." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:295 +msgid "Language Detection" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:297 +msgid "" +"When a visitor lands for the first time on your website (e.g. " +"yourwebsite.com/shop), they may automatically be redirected to a translated " +"version according to their browser language preference (e.g. " +"yourwebsite.com/fr\\_FR/shop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:302 +msgid "" +"Next time, it keeps a cookie of the current language to avoid any " +"redirection." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:305 +msgid "" +"To force a visitor to stick to the default language, you can use the code of" +" the default language in your link, example: yourwebsite.com/en\\_US/shop. " +"This will always land visitors to the English version of the page, without " +"using the browser language preferences." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:312 +msgid "Page Speed" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:315 +msgid "Introduction" +msgstr "แนะนำ" + +#: ../../content/applications/websites/website/pages/seo.rst:317 +msgid "" +"The time to load a page is an important criteria for search engines. A " +"faster website not only improves your visitor's experience, but gives you a " +"better page ranking. Some studies have shown that, if you divide the time to" +" load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor " +"abandonment rate is also divided by two. (25% to 12.5%). One extra second to" +" load a page could `cost $1.6b to Amazon in sales " +"<http://www.fastcompany.com/1825005/how-one-second-could-cost-" +"amazon-16-billion-sales>`__." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:328 +msgid "" +"Fortunately, Odoo does all the magic for you. Below, you will find the " +"tricks Odoo uses to speed up your page loading time. You can compare how " +"your website ranks using these two tools:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:332 +msgid "" +"`Google Page Speed " +"<https://developers.google.com/speed/pagespeed/insights/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:334 +msgid "`Pingdom Website Speed Test <http://tools.pingdom.com/fpt/>`__" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:337 +msgid "Images" +msgstr "รูปภาพ" + +#: ../../content/applications/websites/website/pages/seo.rst:339 +msgid "" +"When you upload new images, Odoo automatically compresses them to reduce " +"their sizes (lossless compression for .PNG and .GIF and lossy compression " +"for .JPG)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:343 +msgid "" +"From the upload button, you have the option to keep the original image " +"unmodified if you prefer to optimize the quality of the image rather than " +"performance." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:351 +msgid "" +"Odoo compresses images when they are uploaded to your website, not when " +"requested by the visitor. Thus, it's possible that, if you use a third-party" +" theme, it will provide images that are not compressed efficiently. But all " +"images used in Odoo official themes have been compressed by default." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:357 +msgid "" +"When you click on an image, Odoo shows you the Alt and title attributes of " +"the ``<img>`` tag. You can click on it to set your own title and Alt " +"attributes for the image." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:364 +msgid "When you click on this link, the following window will appear:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:369 +msgid "" +"Odoo's pictograms are implemented using a font (`Font Awesome " +"<https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes)." +" Thus, you can use as many pictograms as you want in your page, they will " +"not result in extra requests to load the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:378 +msgid "Static Resources: CSS" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:380 +msgid "" +"All CSS files are pre-processed, concatenated, minified, compressed and " +"cached (server-side and browser-side). The result:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:383 +msgid "only one CSS file request is needed to load a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:385 +msgid "" +"this CSS file is shared and cached amongst pages, so that when the visitor " +"clicks on another page, the browser doesn't have to even load a single CSS " +"resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:389 +msgid "this CSS file is optimized to be small" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:391 +msgid "" +"**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a " +"theme might use another framework, most of `Odoo themes " +"<https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap " +"directly. Since Odoo supports Less and Sass, you can modify CSS rules " +"instead of overwriting them through extra CSS lines, resulting in a smaller " +"file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:398 +msgid "" +"**Concatenated:** every module or library you might use in Odoo has its own " +"set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having " +"several CSS files is great for the modularity, but not good for the " +"performance because most browsers can only perform 6 requests in parallel " +"resulting in lots of files loaded in series. The latency time to transfer a " +"file is usually much longer than the actual data transfer time, for small " +"files like .JS and .CSS. Thus, the time to load CSS resources depends more " +"on the number of requests to be done than the actual file size." +msgstr "" +"**ต่อกัน:** ทุกโมดูลหรือไลบรารีที่คุณอาจใช้ใน Odoo จะมีชุดไฟล์ CSS, Less " +"หรือ Sass ของตัวเอง (อีคอมเมิร์ซ บล็อก ธีม และอื่นๆ) การมีไฟล์ CSS " +"หลายไฟล์นั้นดีสำหรับการทำงานแบบแยกส่วน แต่ไม่เป็นผลดีต่อประสิทธิภาพ " +"เนื่องจากเบราว์เซอร์ส่วนใหญ่สามารถดำเนินการคำขอแบบขนานได้เพียง 6 " +"ไฟล์เท่านั้น ส่งผลให้มีไฟล์จำนวนมากที่โหลดเป็นชุด " +"เวลาหน่วงในการถ่ายโอนไฟล์มักจะนานกว่าเวลาถ่ายโอนข้อมูลจริงมาก " +"สำหรับไฟล์ขนาดเล็ก เช่น .JS และ .CSS ดังนั้นเวลาในการโหลดทรัพยากร CSS " +"จึงขึ้นอยู่กับจำนวนคำขอที่ต้องทำมากกว่าขนาดไฟล์จริง" + +#: ../../content/applications/websites/website/pages/seo.rst:408 +msgid "" +"To address this issue, all CSS / Less / Sass files are concatenated into a " +"single .CSS file to send to the browser. So a visitor has **only one .CSS " +"file to load** per page, which is particularly efficient. As the CSS is " +"shared amongst all pages, when the visitor clicks on another page, the " +"browser does not even have to load a new CSS file!" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "**Both files in the <head>**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:415 +msgid "**What the visitor gets (only one file)**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +msgid "/\\* From bootstrap.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:417 +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:424 +#: ../../content/applications/websites/website/pages/seo.rst:450 +msgid ".text-muted {" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:418 +#: ../../content/applications/websites/website/pages/seo.rst:425 +#: ../../content/applications/websites/website/pages/seo.rst:451 +msgid "color: #666;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:419 +msgid "color: #777;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:419 +msgid "background: yellow" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:420 +msgid "background: yellow;" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:420 +#: ../../content/applications/websites/website/pages/seo.rst:421 +#: ../../content/applications/websites/website/pages/seo.rst:426 +#: ../../content/applications/websites/website/pages/seo.rst:452 +msgid "}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:423 +msgid "/\\* From my-theme.css \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:429 +msgid "" +"The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. " +"By doing this, additional page views from the same visitor will not have to " +"load CSS files at all. But some modules might include huge CSS/Javascript " +"resources that you do not want to prefetch at the first page because they " +"are too big. In this case, Odoo splits this resource into a second bundle " +"that is loaded only when the page using it is requested. An example of this " +"is the backend that is only loaded when the visitor logs in and accesses the" +" backend (/web)." +msgstr "" +"CSS ที่ส่งโดย Odoo จะรวม CSS / Less / Sass ทั้งหมดของเพจ / โมดูลทั้งหมด " +"เมื่อทำเช่นนี้ " +"การดูหน้าเว็บเพิ่มเติมจากผู้เยี่ยมชมรายเดียวกันจะไม่ต้องโหลดไฟล์ CSS เลย " +"แต่บางโมดูลอาจมีทรัพยากร CSS/Javascript " +"ขนาดใหญ่ที่คุณไม่ต้องการดึงข้อมูลล่วงหน้าที่หน้าแรกเนื่องจากมีขนาดใหญ่เกินไป" +" ในกรณีนี้ Odoo " +"จะแบ่งทรัพยากรนี้ออกเป็นชุดที่สองซึ่งจะโหลดเมื่อมีการร้องขอเพจที่ใช้งานเท่านั้น" +" " +"ตัวอย่างนี้คือแบ็กเอนด์ที่จะโหลดเฉพาะเมื่อผู้เยี่ยมชมเข้าสู่ระบบและเข้าถึงแบ็กเอนด์" +" (/web)" + +#: ../../content/applications/websites/website/pages/seo.rst:439 +msgid "" +"If the CSS file is very big, Odoo will split it into two smaller files to " +"avoid the 4095 selectors limit per sheet of Internet Explorer. But most " +"themes fit below this limit." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:443 +msgid "" +"**Minified:** After being pre-processed and concatenated, the resulting CSS " +"is minified to reduce its size." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "**Before minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:447 +msgid "**After minification**" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid "/\\* some comments \\*/" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:449 +msgid ".text-muted {color: #666}" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:455 +msgid "" +"The final result is then compressed, before being delivered to the browser." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:458 +msgid "" +"Then, a cached version is stored server-side (so we do not have to pre-" +"process, concatenate, minify at every request) and browser-side (so the same" +" visitor will load the CSS only once for all pages they visit)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:464 +msgid "Static Resources: Javascript" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:466 +msgid "" +"As with CSS resources, Javascript resources are also concatenated, minified," +" compressed and cached (server-side and browser-side)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:469 +msgid "Odoo creates three Javascript bundles:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:471 +msgid "" +"One for all pages of the website (including code for parallax effects, form " +"validation, etc.)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:474 +msgid "" +"One for common Javascript code shared among frontend and backend (Bootstrap)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:477 +msgid "" +"One for backend specific Javascript code (Odoo Web Client interface for your" +" employees using Odoo)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:480 +msgid "" +"Most visitors of your website will only need the first two bundles, " +"resulting in a maximum of two Javascript files to load to render one page. " +"As these files are shared across all pages, further clicks by the same " +"visitor will not load any other Javascript resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:486 +msgid "" +"If you work on :ref:`developer mode <developer-mode>`, the CSS and " +"Javascript are neither concatenated, nor minified. Thus, it's much slower. " +"But it allows you to easily debug with the Chrome debugger as CSS and " +"Javascript resources are not transformed from their original versions." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:491 +msgid "CDN" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:493 +msgid "" +"If you activate the CDN feature in Odoo, static resources (Javascript, CSS, " +"images) are loaded from a Content Delivery Network. Using a Content Delivery" +" Network has three advantages:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:497 +msgid "" +"Load resources from a nearby server (most CDN have servers in main countries" +" around the globe)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:500 +msgid "" +"Cache resources efficiently (no computation resources usage on your own " +"server)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:503 +msgid "" +"Split the resource loading on different services allowing to load more " +"resources in parallel (since the Chrome limit of 6 parallel requests is by " +"domain)" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:507 +msgid "" +"You can configure your CDN options from the **Website Admin** app, using the" +" Configuration menu. Here is an example of configuration you can use:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:514 +msgid "HTML Pages" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:516 +msgid "" +"The HTML pages can be compressed, but this is usually handled by your web " +"server (NGINX or Apache)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:519 +msgid "" +"The Odoo Website builder has been optimized to guarantee clean and short " +"HTML code. Building blocks have been developed to produce clean HTML code, " +"usually using Bootstrap and the HTML editor." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:523 +msgid "" +"As an example, if you use the color picker to change the color of a " +"paragraph to the primary color of your website, Odoo will produce the " +"following code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:527 +msgid "``<p class=\"text-primary\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:529 +msgid "" +"Whereas most HTML editors (such as CKEditor) will produce the following " +"code:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:532 +msgid "``<p style=\"color: #AB0201\">My Text</p>``" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:535 +msgid "Responsive Design" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:537 +msgid "" +"Websites that are not mobile-friendly are negatively impacted in search " +"engine rankings. All Odoo themes rely on Bootstrap to render efficiently " +"according to the device: desktop, tablet or mobile." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:544 +msgid "" +"As all Odoo modules share the same technology, absolutely all pages in your " +"website are mobile friendly." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:548 +msgid "Browser Caching" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:550 +msgid "" +"Javascript, images and CSS resources have an URL that changes dynamically " +"when their content change. As an example, all CSS files are loaded through " +"this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css " +"<http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. " +"The ``457-0da1d9d`` part of this URL will change if you modify the CSS of " +"your website." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:557 +msgid "" +"This allows Odoo to set a very long cache delay (XXX) on these resources: " +"XXX secs, while being updated instantly if you update the resource." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:562 +msgid "Scalability" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:564 +msgid "" +"In addition to being fast, Odoo is also more scalable than traditional CMS " +"and eCommerce (Drupal, Wordpress, Magento, Prestashop)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:567 +msgid "" +"Here is the slide that summarizes the scalability of Odoo Website & " +"eCommerce." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:573 +msgid "Search Engines Files" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:576 +msgid "Sitemap" +msgstr "แผนผังเว็บไซต์" + +#: ../../content/applications/websites/website/pages/seo.rst:578 +msgid "" +"The sitemap points out pages to index to search engine robots. Odoo " +"generates a ``/sitemap.xml`` file automatically for you. For performance " +"reasons, this file is cached and updated every 12 hours." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:582 +msgid "" +"By default, all URLs will be in a single ``/sitemap.xml`` file, but if you " +"have a lot of pages, Odoo will automatically create a Sitemap Index file, " +"respecting the `sitemaps.org protocol " +"<http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 " +"chunks per file." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:588 +msgid "Every sitemap entry has 4 attributes that are computed automatically:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:590 +msgid "``<loc>`` : the URL of a page" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:592 +msgid "" +"``<lastmod>`` : last modification date of the resource, computed " +"automatically based on related object. For a page related to a product, this" +" could be the last modification date of the product or the page." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:597 +msgid "" +"``<priority>`` : modules may implement their own priority algorithm based on" +" their content (example: a forum might assign a priority based on the number" +" of votes on a specific post). The priority of a static page is defined by " +"it's priority field, which is normalized (16 is the default)." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:604 +msgid "Structured Data Markup" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:606 +msgid "" +"Structured Data Markup is used to generate Rich Snippets in search engine " +"results. It is a way for website owners to send structured data to search " +"engine robots; helping them understand your content and create well-" +"presented search results." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:611 +msgid "" +"Google supports a number of rich snippets for content types, including: " +"Reviews, People, Products, Businesses, Events and Organizations." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:614 +msgid "" +"Odoo implements micro data as defined in the `schema.org " +"<http://schema.org>`__ specification for events, eCommerce products, forum " +"posts and contact addresses. This allows your product pages to be displayed " +"in Google using extra information like the price and rating of a product:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:624 +msgid "robots.txt" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:626 +msgid "" +"When indexing your website, search engines take a first look at the general " +"indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, " +"etc.). Odoo automatically creates it. Its content is:" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:630 +msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml" +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:633 +msgid "" +"It means that all robots are allowed to index your website and there is no " +"other indexing rule than specified in the sitemap to be found at following " +"address." +msgstr "" + +#: ../../content/applications/websites/website/pages/seo.rst:637 +msgid "" +"You can customize the file *robots* in :ref:`developer mode <developer-" +"mode>` from *Settings --> Technical --> User Interface --> Views* (exclude " +"robots, exclude some pages, redirect to a custom Sitemap). Make the Model " +"Data of the view *Non Updatable* to not reset the file after system " +"upgrades." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:3 +msgid "Website analytics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:5 +msgid "" +"Website analytics helps website owners understand how people use their site." +" It provides data on visitor demographics, behavior, and interactions, " +"helping improve websites and marketing strategies." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:8 +msgid "" +"You can track your Odoo website's traffic using " +":ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We " +"recommend using Plausible.io as it is privacy-friendly, lightweight, and " +"easy to use." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:12 +msgid "" +"The Plausible analytics dashboard is also integrated into Odoo and can be " +"accessed via :menuselection:`Website --> Reporting --> Analytics`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:18 +msgid "Plausible.io" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:20 +msgid "" +"Odoo hosts its own Plausible.io server and provides a free and ready-to-work" +" Plausible.io solution for **Odoo Online** databases. Go to " +":menuselection:`Website --> Configuration --> Settings`, and enable the " +"feature in the :guilabel:`SEO` section. Odoo automatically creates and sets " +"up your account. You can start using it by going to :menuselection:`Website " +"--> Reporting --> Analytics`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:26 +msgid "" +"**If you already have a Plausible.io account** and you want to connect it to" +" your Odoo Online database, you must create two `ir.config.parameters` to " +"use Plausible.io's servers. To do so, enable the :ref:`developer mode " +"<developer-mode>` and go to :menuselection:`General Settings --> Technical " +"-- System Parameters`. Click :guilabel:`New` and fill in the following " +":guilabel:`Key` and :guilabel:`Value` fields:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:35 +msgid "Key" +msgstr "คีย์" + +#: ../../content/applications/websites/website/reporting/analytics.rst:36 +msgid "Value" +msgstr "ค่า" + +#: ../../content/applications/websites/website/reporting/analytics.rst:37 +msgid "`website.plausible_script`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:38 +msgid "`https://plausible.io/js/plausible.js`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:39 +msgid "`website.plausible_server`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:40 +msgid "`https://plausible.io`" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:42 +msgid "" +"Then, follow the steps below to connect your existing account with " +"Plausible.io servers." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:44 +msgid "" +"If your database is hosted on **Odoo.sh** or **On-premise**, or if you wish " +"to use your own Plausible.io account, proceed as follows:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:47 +msgid "" +"Create or sign in to a Plausible account using the following link: " +"`<https://plausible.io/register>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:48 +msgid "" +"If you are creating a new account, go through the registration and " +"activation steps. When asked to provide your website details, add its " +":guilabel:`Domain` without including `www` (e.g., `example.odoo.com`) and " +"change the :guilabel:`Reporting Timezone` if necessary. Click :guilabel:`Add" +" snippet` to proceed to the next step. Ignore the :guilabel:`Add JavaScript " +"snippet` instructions and click :guilabel:`Start collecting data`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:53 +msgid "" +"Once done, click the Plausible logo in the upper-left part of the page to " +"access your `list of websites <https://plausible.io/sites>`_, then click the" +" gear icon next to the website." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Click the gear icon in the list of websites." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:59 +msgid "" +"In the sidebar, select :guilabel:`Visibility`, then click :guilabel:`+ New " +"link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:60 +msgid "" +"Enter a :guilabel:`Name`, leave the :guilabel:`Password` field empty, as the" +" Plausible analytics dashboard integration in Odoo doesn't support it, then " +"click :guilabel:`Create shared link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Credentials creation for the new shared link" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:66 +msgid "Copy the shared link." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Copy the shared link URL from Plausible.io" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:71 +#: ../../content/applications/websites/website/reporting/analytics.rst:118 +msgid "" +"In Odoo, go to :menuselection:`Website --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:72 +msgid "" +"In the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics`, then" +" paste the :guilabel:`Shared Link` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:76 +msgid "" +"If you have :doc:`multiple websites <../configuration/multi_website>`, add " +"your websites to your Plausible.io account by going to " +"`<https://plausible.io/sites>`_ and clicking :guilabel:`+ Add website`. In " +"Odoo, in the **Website settings**, make sure to select the website in the " +":guilabel:`Settings of Website` field before pasting the :guilabel:`Shared " +"link`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:82 +msgid "" +"Odoo automatically pushes two custom goals: `Lead Generation` and `Shop`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:85 +msgid "`Plausible Analytics documentation <https://plausible.io/docs>`_" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:90 +msgid "Google Analytics" +msgstr "Google Analytics" + +#: ../../content/applications/websites/website/reporting/analytics.rst:92 +msgid "To follow your Odoo website's traffic with Google Analytics:" +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:94 +msgid "" +"Create or sign in to a Google account using the following link: " +"`<https://analytics.google.com>`_." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:95 +msgid "" +"If you are setting up Google Analytics for the first time, click " +":guilabel:`Start measuring` and go through the account creation step." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:97 +msgid "" +"If you already have a Google Analytics account, sign in and click the gear " +"icon in the bottom-left corner of the page to access the **Admin** page. " +"Then, click :guilabel:`+ Create Property`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Measurement ID in Google Analytics." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:104 +msgid "" +"Complete the next steps: `property creation " +"<https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_," +" business details, and business objectives." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:106 +msgid "" +"When you reach the **Data collection** step, choose the :guilabel:`Web` " +"platform." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:0 +msgid "Choose a platform for your Google Analytics property." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:111 +msgid "" +"Set up your data stream: Specify your :guilabel:`Website URL` and a " +":guilabel:`Stream name`, then click :guilabel:`Create stream`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:113 +msgid "Copy the :guilabel:`Measurement ID`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:119 +msgid "" +"In the :guilabel:`SEO` section, enable :guilabel:`Google Analytics`, then " +"paste the :guilabel:`Measurement ID` and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:123 +msgid "" +"If you have :doc:`multiple websites <../configuration/multi_website>` with " +"separate domains, it is recommended to create `one property " +"<https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_" +" per domain. In Odoo, in the **Website settings**, make sure to select the " +"website in the :guilabel:`Settings of Website` field before pasting the " +":guilabel:`Measurement ID`." +msgstr "" + +#: ../../content/applications/websites/website/reporting/analytics.rst:129 +msgid "" +"`Google documentation on setting up Analytics for a website " +"<https://support.google.com/analytics/answer/1008015?hl=en/>`_" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:3 +msgid "Link trackers" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:5 +msgid "" +"Link Trackers allow you to track your marketing campaigns (emails, banner " +"ads, blog posts, social media posts, affiliate links, etc.). This way, you " +"are able to identify your best traffic sources and make informed decisions " +"about the distribution of your marketing budget." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:12 +msgid "" +"Go to :menuselection:`Website --> Configuration --> Settings` and activate " +"*Link Trackers*." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of Website settings page emphasizing the link trackers field in Odoo " +"Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:19 +msgid "Set up traceable URLs" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:21 +msgid "" +"Go to :menuselection:`Website --> Go to website --> Promote --> Track this " +"page`. Here, you are able to get a specific tracked URL based on the " +"campaign, medium, and source being used." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "View of the link tracker fields for Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:28 +msgid "" +"**URL**: url of the page you want to track (e.g. the home page or a " +"product's page)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:29 +msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:30 +msgid "" +"**Medium**: channel used to share (deliver) your link (e.g. an email or a " +"Facebook ad)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:31 +msgid "" +"**Source**: platform where the traffic originates (e.g. Google or Twitter)." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:33 +msgid "" +"Now, click on *Get tracked link* to generate a URL that you can post or send" +" by the source you have decided on." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:37 +msgid "Follow-up on tracked links" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:39 +msgid "" +"To look at statistics of your links, go to :menuselection:`Website --> Go to" +" website --> Promote --> Track this page`. Besides being able to see the " +"*Most Clicked* and *Recently Used* links, you can also see complete " +"statistics by clicking on *Stats*, including the number of clicks, and the " +"country of origin for those clicks." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst-1 +msgid "" +"View of the tracked list emphasizing the statistics buttons in Odoo Website" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:50 +msgid "You can also access the link tracker on *odoo.com/r* via your browser." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:51 +msgid "" +"Activate the developer mode (:menuselection:`Settings --> Activate the " +"developer mode`) and get access to the *Link Tracker* module and its back-" +"end functionalities." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:53 +msgid "" +"Integrated with :ref:`website/analytics/GA`, those trackers allow you to see" +" the number of clicks and visitors to keep you on top of your marketing " +"campaigns." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:55 +msgid "" +"The integration with the :doc:`CRM " +"</applications/sales/crm/track_leads/prospect_visits>` application allows " +"you to understand where your leads and opportunities are coming from." +msgstr "" diff --git a/locale/vi/LC_MESSAGES/finance.po b/locale/vi/LC_MESSAGES/finance.po index cccf9557b..5337195a8 100644 --- a/locale/vi/LC_MESSAGES/finance.po +++ b/locale/vi/LC_MESSAGES/finance.po @@ -8,9 +8,9 @@ # Võ Văn Khoa, 2023 # Trần Hà <tranthuha13590@gmail.com>, 2023 # Nancy Momoland <thanh.np2502@gmail.com>, 2023 -# Thi Huong Nguyen, 2023 # Martin Trigaux, 2024 # Wil Odoo, 2024 +# Thi Huong Nguyen, 2024 # #, fuzzy msgid "" @@ -19,7 +19,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Wil Odoo, 2024\n" +"Last-Translator: Thi Huong Nguyen, 2024\n" "Language-Team: Vietnamese (https://app.transifex.com/odoo/teams/41243/vi/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -4104,7 +4104,7 @@ msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:99 msgid "Peppol" -msgstr "" +msgstr "Peppol" #: ../../content/applications/finance/accounting/customer_invoices/electronic_invoicing.rst:101 msgid "" @@ -35567,12 +35567,6 @@ msgid "" "platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/finance.po b/locale/zh_CN/LC_MESSAGES/finance.po index 3f226fa38..d58bec0ed 100644 --- a/locale/zh_CN/LC_MESSAGES/finance.po +++ b/locale/zh_CN/LC_MESSAGES/finance.po @@ -23449,7 +23449,7 @@ msgid "" "Once uploaded, the status changes to :guilabel:`In Use`. At this moment, " "when a transaction is used for this document type, the invoice number takes " "the first folio in the sequence." -msgstr "" +msgstr "上传后，状态将变为 :guilabel:`使用中`。此时，当交易用于此单据类型时，发票号码会在序列中占据第一个对开页码。" #: ../../content/applications/finance/fiscal_localizations/chile.rst:356 msgid "" @@ -36749,12 +36749,6 @@ msgid "" "platform. You only need to do it once." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:94 -msgid "" -"When entering your VAT number, do not add the GB country code. Only the 9 " -"digits are required." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:97 msgid "Periodic submission to HMRC" msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/marketing.po b/locale/zh_CN/LC_MESSAGES/marketing.po index 9e25f4817..971f1f596 100644 --- a/locale/zh_CN/LC_MESSAGES/marketing.po +++ b/locale/zh_CN/LC_MESSAGES/marketing.po @@ -6039,7 +6039,7 @@ msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 msgid "Kanban view" -msgstr "" +msgstr "看板视图" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:393 msgid "" diff --git a/locale/zh_CN/LC_MESSAGES/productivity.po b/locale/zh_CN/LC_MESSAGES/productivity.po index 25150fac8..918ed27b6 100644 --- a/locale/zh_CN/LC_MESSAGES/productivity.po +++ b/locale/zh_CN/LC_MESSAGES/productivity.po @@ -180,7 +180,7 @@ msgstr "" msgid "" "Skip the third step, :menuselection:`Scopes`, by clicking :guilabel:`Save " "and Continue`." -msgstr "" +msgstr "单击 :guilabel:`保存并继续` 跳过第三步，即 :menuselection:`范围` 。" #: ../../content/applications/productivity/calendar/google.rst:74 msgid "" @@ -189,6 +189,8 @@ msgid "" ":guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A " "summary of the app registration appears." msgstr "" +"接下来，如果继续测试模式（外部），请通过点击 :guilabel:`添加用户` 添加在 :guilabel:`测试用户` " +"步骤下配置的电子邮件地址，然后点击 :guilabel:`保存并继续` 按钮。应用程序注册摘要将出现。" #: ../../content/applications/productivity/calendar/google.rst:78 msgid "" @@ -199,7 +201,7 @@ msgstr "最后，滚动到底部，点击 :guilabel:`返回仪表板`。" msgid "" "Now, the OAuth consent has been configured, and it's time to create " "credentials." -msgstr "" +msgstr "现在，OAuth 授权已经配置好了，是时候创建凭据了。" #: ../../content/applications/productivity/calendar/google.rst:83 msgid "Create credentials" @@ -213,6 +215,9 @@ msgid "" ":guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`, " "Google will open a guide to create credentials." msgstr "" +"要将 Google 日历连接到 Odoo，需要 *客户 ID* 和 *客户密钥*。这是 Google 控制台的最后一步。首先点击左侧菜单中的 " +":guilabel:`证书`。然后，单击 :guilabel:`创建凭据`，并选择 :guilabel:`OAuth 客户端 ID`，Google " +"将打开创建凭据的指南。" #: ../../content/applications/productivity/calendar/google.rst:90 msgid "" @@ -220,6 +225,8 @@ msgid "" "application` for the :guilabel:`Application Type` field, and type `My Odoo " "Database` for the :guilabel:`Name`." msgstr "" +"在 :menuselection:`创建 OAuth 客户 ID` 下，为 :guilabel:`应用类型` 字段选择 " +":guilabel:`网站申请`，并为 :guilabel:`名称` 键入 `我的 Odoo 数据库`。" #: ../../content/applications/productivity/calendar/google.rst:93 msgid "" @@ -227,6 +234,8 @@ msgid "" ":guilabel:`+ Add URI` and type the company's Odoo full :abbr:`URL (Uniform " "Resource Locator)` address." msgstr "" +"在 :guilabel:`经授权 JavaScript Origins` 部分，单击 :guilabel:`+ 添加 URI` 并键入公司的 Odoo " +"完整 :abbr:`URL （统一资源定位符）` 地址。" #: ../../content/applications/productivity/calendar/google.rst:95 msgid "" @@ -235,6 +244,9 @@ msgid "" "address followed by `/google_account/authentication`. Finally, click " ":guilabel:`Create`." msgstr "" +"在 :guilabel:`经授权重新定向 URIs` 部分，单击 :guilabel:`+ 添加 URI`，然后键入公司的 Odoo " +":abbr:`URL（统一资源定位符）` 地址，后面跟上`/google_account/authentication`。最后，点击 " +":guilabel:`创建`。" #: ../../content/applications/productivity/calendar/google.rst-1 msgid "" @@ -245,7 +257,7 @@ msgstr "添加授权的 JavaScript 起源和授权的重定向 URI。" msgid "" "A :guilabel:`Client ID` and :guilabel:`Client Secret` will appear, copy " "these to a notepad." -msgstr "" +msgstr "将显示 :guilabel:`客户 ID` 和 :guilabel:`客户密钥`，将其复制到记事本中。" #: ../../content/applications/productivity/calendar/google.rst:106 msgid "Setup in Odoo" @@ -258,6 +270,8 @@ msgid "" "Integrations --> Google Calendar`. Check the box next to :guilabel:`Google " "Calendar`." msgstr "" +"找到 *客户 ID* 和 *客户密钥* 后，打开 Odoo 数据库并转到 :menuselection:`设置 --> 常规设置 --> 整合 --> " +"Google 日历`。选中 :guilabel:`Google 日历` 旁边的复选框。" #: ../../content/applications/productivity/calendar/google.rst-1 msgid "The Google Calendar checkbox in General Settings." @@ -269,16 +283,20 @@ msgid "" " Calendar API credentials page into their respective fields below the " ":guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`." msgstr "" +"接下来，将 Google 日历 API 证书页面中的 *客户 ID* 和 *客户密钥* 复制并粘贴到 :guilabel:`Google 日历` " +"复选框下方的相应字段中。然后，单击 :guilabel:`保存`。" #: ../../content/applications/productivity/calendar/google.rst:121 msgid "Sync calendar in Odoo" -msgstr "" +msgstr "在 Odoo 中同步日历" #: ../../content/applications/productivity/calendar/google.rst:123 msgid "" "Finally, open the :menuselection:`Calendar` app in Odoo and click on the " ":guilabel:`Google` sync button to sync Google Calendar with Odoo." msgstr "" +"最后，打开 Odoo 中的 :menuselection:`日历` 应用程序，点击 :guilabel:`Google` 同步按钮，将 Google " +"日历与 Odoo 同步。" #: ../../content/applications/productivity/calendar/google.rst-1 msgid "" @@ -294,6 +312,9 @@ msgid "" "the app be unverifed), and finally select :guilabel:`Continue` (to give " "permission for the transfer of data)`." msgstr "" +"首次将 Google 日历与 Odoo 同步时，页面将重定向到 Google 账户。在那里，选择应具有访问权限的 " +":guilabel:`电子邮件账户`，然后选择 :guilabel:`继续`（如果应用程序未经验证），最后选择 " +":guilabel:`继续`（允许传输数据）`。" #: ../../content/applications/productivity/calendar/google.rst-1 msgid "Give Odoo permission to access Google Calendar." @@ -310,50 +331,52 @@ msgid "" "before attempting to sync the desired Google Calendar with the user's " "production database." msgstr "" +"Odoo 强烈建议在测试数据库和测试电子邮件地址（不用于任何其他目的）上测试 Google 日历同步，然后再尝试将所需的 Google " +"日历与用户的生产数据库同步。" #: ../../content/applications/productivity/calendar/google.rst:147 msgid "Once a user synchronizes their Google calendar with the Odoo calendar:" -msgstr "" +msgstr "一旦用户将 Google 日历与 Odoo 日历同步后：" #: ../../content/applications/productivity/calendar/google.rst:149 msgid "" "Creating an event in Odoo causes Google to send an invitation to all event " "attendees." -msgstr "" +msgstr "在 Odoo 中创建活动会导致 Google 向所有参与者发送邀请。" #: ../../content/applications/productivity/calendar/google.rst:150 msgid "" "Deleting an event in Odoo causes Google to send a cancellation to all event " "attendees." -msgstr "" +msgstr "在 Odoo 中删除活动会导致 Google 向所有参与者发送取消通知。" #: ../../content/applications/productivity/calendar/google.rst:151 msgid "" "Adding a contact to an event causes Google to send an invitation to all " "event attendees." -msgstr "" +msgstr "将联系人添加到活动会导致 Google 向所有参与者发送邀请。" #: ../../content/applications/productivity/calendar/google.rst:152 msgid "" "Removing a contact from an event causes Google to send a cancellation to all" " event attendees." -msgstr "" +msgstr "从活动中删除联系人会导致 Google 向所有参与者发送取消通知。" #: ../../content/applications/productivity/calendar/google.rst:154 msgid "" "Events can be created in Google Calendar without sending a notification by " "selecting :guilabel:`Don't Send` when prompted to send invitation emails." -msgstr "" +msgstr "在 Google 日历中创建活动时，可在提示发送邀请电子邮件时选择 :guilabel:`不发送`，而不发送通知。" #: ../../content/applications/productivity/calendar/outlook.rst:3 msgid "Outlook Calendar synchronization" -msgstr "" +msgstr "Outlook 日历同步" #: ../../content/applications/productivity/calendar/outlook.rst:5 msgid "" "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping " "track of their tasks and appointments across all related applications." -msgstr "" +msgstr "将用户的 Outlook 日历与 Odoo 同步，有助于追踪所有相关应用程序中的任务和约会。" #: ../../content/applications/productivity/calendar/outlook.rst:9 msgid ":doc:`/applications/general/auth/azure`" @@ -365,7 +388,7 @@ msgstr ":doc:`/administration/maintain/azure_oauth`" #: ../../content/applications/productivity/calendar/outlook.rst:13 msgid "Register the application with Microsoft Azure" -msgstr "" +msgstr "在 Microsoft Azure 注册应用程序" #: ../../content/applications/productivity/calendar/outlook.rst:15 msgid "" @@ -374,6 +397,9 @@ msgid "" "paid for Azure. For more information, `click here " "<https://azure.microsoft.com/en-us/free/?WT.mc_id=A261C142F>`_." msgstr "" +"要将 Outlook 日历与 Odoo 日历同步，需要 Microsoft Azure 账户。对于从未试用过 Azure 或从未支付过 Azure " +"费用的用户来说，创建账户是免费的。欲了解更多信息，请`点击此处 <https://azure.microsoft.com/en-" +"us/free/?WT.mc_id=A261C142F>`_。" #: ../../content/applications/productivity/calendar/outlook.rst:19 msgid "" @@ -383,6 +409,10 @@ msgid "" "Directory (Azure AD)*), which is a representation of an organization to " "manage and register apps." msgstr "" +"关于如何设置 Microsoft Entra ID（正式名称为 *Microsoft Azure Active Directory (Azure " +"AD)*），请参阅 `Microsoft 文档 <https://docs.microsoft.com/en-us/azure/active-" +"directory/ develop/quickstart-create-new-tenant>`_，该 ID " +"是一个组织的代表，用于管理和注册应用程序。" #: ../../content/applications/productivity/calendar/outlook.rst:24 msgid "" @@ -394,6 +424,10 @@ msgid "" "and personal Microsoft accounts (e.g. Skype, Xbox)` option for " ":guilabel:`Supported account types`." msgstr "" +"然后，`注册应用程序<https://docs.microsoft.com/en-us/azure/active-directory/develop/ " +"quickstart-register-app>`_，选择适当的 :guilabel:`支持的账户类型`。希望将 Outlook 日历连接到 Odoo " +"的用户应在:guilabel:`支持的账户类型`中选择:guilabel:`任何组织目录中的账户（任何 Microsoft Entra ID 目录 - " +"多用户）和个人 Microsoft 账户（如 Skype、Xbox）`选项。" #: ../../content/applications/productivity/calendar/outlook.rst:30 msgid "" @@ -401,18 +435,22 @@ msgid "" "copy the Odoo database URI (URL) followed by " "`/microsoft_account/authentication`." msgstr "" +"配置 :guilabel:`重定向 URI` 时，选择 :guilabel:`Web`，然后复制 Odoo 数据库 " +"URI（URL），后面加上`/microsoft_account/authentication`。" #: ../../content/applications/productivity/calendar/outlook.rst:34 msgid "" "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` " "for the :guilabel:`Redirect URI`." msgstr "" +"在 :guilabel:`重定向 URI` 中输入 " +"`https://www.companyname.odoo.com/microsoft_account/authentication`。" #: ../../content/applications/productivity/calendar/outlook.rst-1 msgid "" "The \"Supported account type\" and \"Redirect URI\" settings in the " "Microsoft Entra ID portal." -msgstr "" +msgstr "Microsoft Entra ID 门户中的 \"支持的账户类型\" 和 \"重定向 URI\" 设置。" #: ../../content/applications/productivity/calendar/outlook.rst:41 msgid "" @@ -420,6 +458,8 @@ msgid "" "this page <https://docs. microsoft.com/en-us/azure/active-" "directory/develop/reply-url>`_." msgstr "" +"有关 URI 的限制和约束的更多信息，`请查看此页面 <https://docs. microsoft.com/en-us/azure/active-" +"directory/develop/reply-url>`_。" #: ../../content/applications/productivity/calendar/outlook.rst:44 msgid "" @@ -427,6 +467,7 @@ msgid "" "which allows Odoo to authenticate itself, requiring no interaction from the " "user's side. :guilabel:`Certificates` are optional." msgstr "" +"关于应用程序凭据，用户*必须*添加一个客户端密钥，它允许 Odoo 进行自我验证，用户无需进行任何交互。 :guilabel:`证书` 是可选项。" #: ../../content/applications/productivity/calendar/outlook.rst:48 msgid "" @@ -435,6 +476,8 @@ msgid "" ":guilabel:`Description` and select when the client secret " ":guilabel:`Expires`." msgstr "" +"要添加客户密钥，请单击 :guilabel:`添加证书或密钥`，然后单击 :guilabel:`新建客户密钥`。然后，键入 :guilabel:`描述`" +" 并选择客户密钥 :guilabel:`失效` 的时间。" #: ../../content/applications/productivity/calendar/outlook.rst:52 msgid "" @@ -443,6 +486,8 @@ msgid "" "there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to " "generate the client secret (:guilabel:`Secret ID`)." msgstr "" +"由于重置同步可能比较麻烦，Odoo 建议设置客户密钥的最大允许过期日期（24 个月），这样就无需很快重新同步。最后，点击 :guilabel:`添加` " +"生成客户密钥（:guilabel:`密钥 ID`）。" #: ../../content/applications/productivity/calendar/outlook.rst:57 msgid "Configuration in Odoo" @@ -453,10 +498,11 @@ msgid "" "In the Odoo database, go to :menuselection:`Settings --> General Settings " "--> Integrations` and activate the :guilabel:`Outlook Calendar` setting." msgstr "" +"在 Odoo 数据库中，进入 :menuselection:`设置-->常规设置-->整合`并激活 :guilabel:`Outlook 日历` 设置。" #: ../../content/applications/productivity/calendar/outlook.rst-1 msgid "The \"Outlook Calendar\" setting activated in Odoo." -msgstr "" +msgstr "在 Odoo 中激活 \"Outlook 日历\" 设置。" #: ../../content/applications/productivity/calendar/outlook.rst:66 msgid "" @@ -464,10 +510,12 @@ msgid "" "the application, copy the :guilabel:`Application (Client) ID`, and paste it " "into the :guilabel:`Client ID` field in Odoo." msgstr "" +"从 Microsoft Azure 门户，在应用程序的 :guilabel:`概览` 部分，复制 :guilabel:`应用程序（客户端）ID` " +"并将其粘贴到 Odoo 中的 :guilabel:`客户 ID` 字段。" #: ../../content/applications/productivity/calendar/outlook.rst-1 msgid "The \"Client ID\" in the Microsoft Azure portal." -msgstr "" +msgstr "Microsoft Azure 门户中的 \"客户 ID\"。" #: ../../content/applications/productivity/calendar/outlook.rst:73 msgid "" @@ -475,16 +523,18 @@ msgid "" "section, copy the :guilabel:`Client Secret Value` and paste it into the " ":guilabel:`Client Secret` field in Odoo." msgstr "" +"在 Microsoft Azure 门户的 :guilabel:`认证和密钥` 部分，复制 :guilabel:`客户密钥值` 并粘贴到 Odoo 中的" +" :guilabel:`客户密钥` 字段。" #: ../../content/applications/productivity/calendar/outlook.rst-1 msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." -msgstr "" +msgstr "从 Microsoft 复制到 Odoo 的 \"客户密钥\" 令牌。" #: ../../content/applications/productivity/calendar/outlook.rst:80 msgid "" "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, " "click :guilabel:`Save`." -msgstr "" +msgstr "最后，在 Odoo :menuselection:`设置-->常规设置`页面，单击 :guilabel:`保存`。" #: ../../content/applications/productivity/calendar/outlook.rst:85 msgid "Sync with Outlook" @@ -497,6 +547,8 @@ msgid "" "purpose) before attempting to sync the desired Outlook Calendar with the " "user's production database." msgstr "" +"Odoo 强烈建议在测试数据库和测试电子邮件地址（不用于任何其他目的）上测试 Outlook 日历同步，然后再尝试将所需的 Outlook " +"日历与用户的生产数据库同步。" #: ../../content/applications/productivity/calendar/outlook.rst:93 msgid "" @@ -505,6 +557,8 @@ msgid "" "from Odoo's calendar during the sync as new events, causing an email " "notification to be sent from Outlook to all the event attendees." msgstr "" +"如果用户在同步 Outlook 日历之前在 Odoo 日历上有任何过去、现在或未来的事件，Outlook 会将同步期间从 Odoo " +"日历中提取的事件视为新事件，从而从 Outlook 向所有事件参与者发送电子邮件通知。" #: ../../content/applications/productivity/calendar/outlook.rst:97 msgid "" @@ -513,6 +567,8 @@ msgid "" "Outlook calendar before the first ever sync, delete the events from Odoo, " "and then start the sync." msgstr "" +"为了避免向所有过去、现在和未来的活动参与者发送不必要的电子邮件，用户必须在首次同步之前将 Odoo 日历中的活动添加到 Outlook 日历中，然后从 " +"Odoo 中删除活动，再开始同步。" #: ../../content/applications/productivity/calendar/outlook.rst:101 msgid "" @@ -522,52 +578,54 @@ msgid "" "changed), with no exceptions. This is a limitation that cannot be fixed from" " Odoo's side." msgstr "" +"即使将 Odoo 日历与 Outlook 日历同步后，每次编辑事件（创建、删除、未存档或更改事件日期/时间）时，Outlook " +"仍会向所有事件参与者发送通知，无一例外。这是 Odoo 无法修复的限制。" #: ../../content/applications/productivity/calendar/outlook.rst:106 msgid "" "In summary, once a user synchronizes their Outlook calendar with the Odoo " "calendar:" -msgstr "" +msgstr "总之，一旦用户将其 Outlook 日历与 Odoo 日历同步，Odoo 日历就会自动更新：" #: ../../content/applications/productivity/calendar/outlook.rst:108 msgid "" "Creating an event in Odoo causes Outlook to send an invitation to all event " "attendees." -msgstr "" +msgstr "在 Odoo 中创建活动会导致 Outlook 向所有活动参与者发送邀请。" #: ../../content/applications/productivity/calendar/outlook.rst:109 msgid "" "Deleting an event in Odoo causes Outlook to send a cancellation to all event" " attendees." -msgstr "" +msgstr "在 Odoo 中删除活动会导致 Outlook 向所有活动参与者发送取消通知。" #: ../../content/applications/productivity/calendar/outlook.rst:110 msgid "" "Unarchiving an event in Odoo causes Outlook to send an invitation to all " "event attendees." -msgstr "" +msgstr "在 Odoo 中取消活动存档会导致 Outlook 向所有活动参与者发送邀请。" #: ../../content/applications/productivity/calendar/outlook.rst:111 msgid "" "Archiving an event in Odoo causes Outlook to send a cancellation to all " "event attendees." -msgstr "" +msgstr "在 Odoo 中存档活动会导致 Outlook 向所有活动参与者发送取消通知。" #: ../../content/applications/productivity/calendar/outlook.rst:112 msgid "" "Adding a contact to an event causes Outlook to send an invitation to all " "event attendees." -msgstr "" +msgstr "将联系人添加到活动中会导致 Outlook 向所有活动参与者发送邀请。" #: ../../content/applications/productivity/calendar/outlook.rst:113 msgid "" "Removing a contact from an event causes Outlook to send a cancellation to " "all event attendees." -msgstr "" +msgstr "从活动中删除联系人会导致 Outlook 向所有活动参与者发送取消通知。" #: ../../content/applications/productivity/calendar/outlook.rst:116 msgid "Sync Odoo Calendar and Outlook" -msgstr "" +msgstr "同步 Odoo 日历和 Outlook" #: ../../content/applications/productivity/calendar/outlook.rst:118 msgid "" @@ -576,10 +634,12 @@ msgid "" " page, and the user is asked to log in to their account, if they are not " "already, and grant the required permissions." msgstr "" +"在 Odoo 数据库中，进入 :guilabel:`日历` 模块并点击 :guilabel:`Outlook` 同步按钮。页面将重定向到 " +"Microsoft 登录页面，如果用户尚未登录，则要求其登录到自己的账户，并授予所需的权限。" #: ../../content/applications/productivity/calendar/outlook.rst-1 msgid "The \"Outlook\" sync button in Odoo Calendar." -msgstr "" +msgstr "Odoo 日历中的 \"Outlook\" 同步按钮。" #: ../../content/applications/productivity/calendar/outlook.rst:126 msgid "" @@ -596,14 +656,17 @@ msgid "" " helps the user to manage a specific instance of Microsoft cloud services " "for their internal and external users." msgstr "" +"所有希望使用同步的用户只需 :ref:`将日历与 Outlook 同步 <outlook/sync>`。Microsoft Azure " +"帐户的配置只需完成一次，因为 Microsoft Entra ID 租户的客户 ID " +"和客户保密信息是唯一的，且代表一个组织，可帮助用户为内部和外部用户管理 Microsoft 云服务的特定实例。" #: ../../content/applications/productivity/calendar/outlook.rst:137 msgid ":doc:`../mail_plugins/outlook`" -msgstr "" +msgstr ":doc:`../mail_plugins/outlook`" #: ../../content/applications/productivity/calendar/outlook.rst:138 msgid ":doc:`google`" -msgstr "" +msgstr ":doc:`google`" #: ../../content/applications/productivity/discuss.rst:8 msgid "Discuss" @@ -640,6 +703,9 @@ msgid "" ":guilabel:`Start your free trial`. Verify your email address with Twilio, as" " per their instructions." msgstr "" +"首先，访问 `Twilio <https://www.twilio.com>`_，然后单击 :guilabel:`注册` 创建 Twilio " +"帐户。然后，输入您的姓名和电子邮件地址，创建密码，并接受 Twilio 服务条款。然后，点击 :guilabel:`开始免费试用`。按照提示，在 " +"Twilio 中验证您的电子邮件地址。" #: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 msgid "" @@ -773,6 +839,8 @@ msgid "" "For on-premise instances of Odoo, the package `python3-gevent` is necessary " "for the Discuss module to run calls/video calls on Ubuntu (Linux) servers." msgstr "" +"对于 Odoo 的内部实例，Discuss 模块需要使用软件包 `python3-gevent` 才能在 " +"Ubuntu（Linux）服务器上运行调用/视频调用。" #: ../../content/applications/productivity/discuss/overview.rst:5 msgid "Overview" @@ -780,7 +848,7 @@ msgstr "概述" #: ../../content/applications/productivity/discuss/overview/get_started.rst:3 msgid "Get started with Discuss" -msgstr "" +msgstr "如何开始使用讨论应用" #: ../../content/applications/productivity/discuss/overview/get_started.rst:5 msgid "" @@ -789,20 +857,23 @@ msgid "" " window that works across applications, or through the dedicated *Discuss* " "dashboard." msgstr "" +"Odoo *内部沟通* 是一款内部交流应用程序，允许用户通过跨应用程序的聊天窗口或专用*内部沟通*仪表板，通过消息、笔记和文件共享进行联系。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:12 msgid "Choose notifications preference" -msgstr "" +msgstr "选择通知偏好" #: ../../content/applications/productivity/discuss/overview/get_started.rst:14 msgid "" "Access user-specific preferences for the *Discuss* app by navigating to " ":menuselection:`Settings app --> Users --> User --> Preferences tab`." msgstr "" +"通过导航至 :menuselection:`设置应用程序 --> 用户 --> 用户 --> 偏好选项卡` 访问 *内部沟通* " +"应用程序的特定用户首选项。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "View of the Preferences tab for Odoo Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用的偏好选项卡视图。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:21 msgid "" @@ -814,6 +885,8 @@ msgid "" "stage (if an email\\ is configured to be sent, for example if the task is " "set to :guilabel:`Done`)." msgstr "" +"默认情况下，:guilabel:`通知`字段设置为:guilabel:`通过电子邮件处理`。启用此设置后，每当从聊天窗口发送消息、使用`@`提及（从聊天窗口）发送笔记，或者用户关注的记录发送通知时，Odoo" +" 将发送一封通知电子邮件。当阶段发生变化时（例如，如果配置了发送电子邮件，将任务设置为:guilabel:`已完成`），将触发通知。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:27 msgid "" @@ -825,10 +898,14 @@ msgid "" "pinning the message by selecting :guilabel:`Pin` or even mark the message as" " unread by selecting :guilabel:`Marked as unread`." msgstr "" +"选择 :guilabel:`在 Odoo 中处理`，上述通知就会显示在*内部沟通*应用程序的*收件箱*中。可对消息执行以下操作：点击 " +":guilabel:`添加反应`，用表情符号回复，或点击 :guilabel:`回复`，以回复消息。其他操作包括点击 " +":guilabel:`标记为待办`，将信息加星，或选择 :guilabel:`固定`，将信息固定，甚至选择 " +":guilabel:`标记为未读`，将信息标记为未读。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "View of an inbox message and its action options in Odoo Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用中的收件箱信息及其操作选项视图" #: ../../content/applications/productivity/discuss/overview/get_started.rst:38 msgid "" @@ -836,14 +913,16 @@ msgid "" ":guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the " "message to :guilabel:`History`." msgstr "" +"点击信息上的 :guilabel:`标记为待办`会使其显示在 :guilabel:` 已星标`页面，而点击 :guilabel:`标记为已读` " +"则会将信息移动到 :guilabel:` 历史` 页面。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "View of messages marked as todo in Odoo Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用中标记为待办事项的信息视图。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:46 msgid "Start chatting" -msgstr "" +msgstr "开始聊天" #: ../../content/applications/productivity/discuss/overview/get_started.rst:48 msgid "" @@ -852,18 +931,20 @@ msgid "" "the user will receive push notifications on their desktop for the messages " "they receive, regardless of where the user is in Odoo." msgstr "" +"用户首次登录自己的账户时，OdooBot 会发送一条消息，询问是否允许发送桌面聊天通知。如果用户接受，无论用户在 Odoo " +"的哪个位置，都会在桌面上收到消息推送通知。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "" "View of the messages under the messaging menu emphasizing the request for push\n" "notifications for Odoo Discuss." -msgstr "" +msgstr "消息菜单下的消。息视图，强调为 Odoo 内部沟通应用申请推送通知。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:58 msgid "" "To stop receiving desktop notifications, reset the notifications settings of" " the browser." -msgstr "" +msgstr "要停止接收桌面通知，请重置浏览器的通知设置。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:60 msgid "" @@ -871,22 +952,26 @@ msgid "" ":guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or " ":guilabel:`Channels` in the left menu of the dashboard." msgstr "" +"要开始聊天，请进入 :menuselection:`内部讨论` 应用程序，点击仪表板左侧菜单中 :guilabel:`私信` 或 " +":guilabel:`频道` 旁边的 :guilabel:`+ （加）` 图标。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "" "View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n" "Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用中强调标题渠道和私聊消息的讨论小组视图" #: ../../content/applications/productivity/discuss/overview/get_started.rst:69 msgid "" "A company can also easily create :doc:`public and private channels " "</applications/productivity/discuss/overview/team_communication>`." msgstr "" +"公司还可以轻松创建 " +":doc:`公共和私人频道</applications/productivity/discuss/overview/team_communication>`。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:73 msgid "Mentions in the chat and on the chatter" -msgstr "" +msgstr "沟通栏中和聊天中的提及" #: ../../content/applications/productivity/discuss/overview/get_started.rst:75 msgid "" @@ -895,10 +980,12 @@ msgid "" "their *inbox* or through an email, depending on their communication " "settings." msgstr "" +"要在聊天或聊天室中提及某个用户，请键入 `@user-name`；要提及某个频道，请键入 `#channel-" +"name`。被提及的用户将在其*收件箱*或通过电子邮件收到通知，具体取决于他们的通讯设置。" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "View of a couple of chat window messages for Odoo Discuss." -msgstr "" +msgstr "Odoo内部沟通应用聊天窗口消息视图" #: ../../content/applications/productivity/discuss/overview/get_started.rst:84 msgid "" @@ -907,10 +994,11 @@ msgid "" "record being searched does not match with either a follower or employee, the" " scope of the search becomes all partners." msgstr "" +"当提及用户时，搜索列表（名称列表）会首先根据任务的关注者，其次根据员工建议值。如果正在搜索的记录与关注者或员工都不匹配，搜索范围就会变成所有合作伙伴。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:89 msgid "User status" -msgstr "" +msgstr "用户状态" #: ../../content/applications/productivity/discuss/overview/get_started.rst:91 msgid "" @@ -919,6 +1007,8 @@ msgid "" "left side of a contact's name on the :guilabel:`Discuss` sidebar, on the " "*messaging menu* and when listed in the *chatter*." msgstr "" +"查看同事的*状态*有助于了解他们在做什么，以及他们回复信息的速度。状态显示在 :guilabel:`内部讨论` " +"侧边栏、*消息菜单*和*聊天记录*中，位于联系人姓名的左侧。" #: ../../content/applications/productivity/discuss/overview/get_started.rst:95 msgid "Green = online" @@ -938,15 +1028,15 @@ msgstr "飞机 = 外出" #: ../../content/applications/productivity/discuss/overview/get_started.rst-1 msgid "View of the contacts' status for Odoo Discuss." -msgstr "" +msgstr "Odoo内部沟通应用的联系人状态视图" #: ../../content/applications/productivity/discuss/overview/get_started.rst:106 msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" -msgstr "" +msgstr ":doc:`/applications/productivity/discuss/overview/team_communication`" #: ../../content/applications/productivity/discuss/overview/get_started.rst:107 msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`" -msgstr "" +msgstr ":doc:`/applications/productivity/discuss/overview/plan_activities`" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 msgid "Activities" @@ -959,6 +1049,7 @@ msgid "" "chatter thread, kanban view, list view, or activities view of an " "application." msgstr "" +"*活动*是与 Odoo 数据库中的记录相关联的后续任务。可以在数据库中包含聊天线程、看板视图、列表视图或应用程序活动视图的任何页面上安排活动。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 msgid "Schedule activities" @@ -971,6 +1062,8 @@ msgid "" "pop-up window that appears, select an :guilabel:`Activity Type` from the " "drop-down menu." msgstr "" +"创建活动的方法之一是点击任何记录的*沟通栏*顶部的 :guilabel:`日程活动`按钮。在弹出的窗口中，从下拉菜单中选择 " +":guilabel:`活动类型`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 msgid "" @@ -979,25 +1072,27 @@ msgid "" "*CRM* application, go to :menuselection:`CRM app --> Configuration --> " "Activity Types`." msgstr "" +"每个应用程序都有一个专用于该应用程序的*活动类型*列表。例如，要查看和编辑 *CRM* 应用程序可用的活动，请转到 " +":menuselection:`CRM 应用程序 --> 配置 --> 活动类型`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 msgid "" "Enter a title for the activity in the :guilabel:`Summary` field, located in " "the :guilabel:`Schedule Activity` pop-up window." -msgstr "" +msgstr "在弹出窗口 :guilabel:`活动安排` 中的 :guilabel:`摘要` 字段中输入活动标题。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 msgid "" "To assign the activity to a different user, select a name from the " ":guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the " "activity is automatically assigned." -msgstr "" +msgstr "要将活动分配给不同的用户，请从 :guilabel:`分配给` 下拉菜单中选择一个名称。否则，将自动分配给创建活动的用户。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 msgid "" "Lastly, feel free to add any additional information in the optional " ":guilabel:`Log a note...` field." -msgstr "" +msgstr "最后，请在可选的 :guilabel:`记录备注...`字段中添加其他信息。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 msgid "" @@ -1006,44 +1101,46 @@ msgid "" ":guilabel:`Activity Type`. However, this date can be changed by selecting a " "day on the calendar in the :guilabel:`Due Date` field." msgstr "" +"在弹出的 :guilabel:`活动安排` 窗口中，:guilabel:`截止日期` 字段会根据所选 :guilabel:`活动类型` " +"的配置设置自动填充。但是，可以通过在 :guilabel:`截止日期` 字段中选择日历上的某一天来更改此日期。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 msgid "Lastly, click one of the following buttons:" -msgstr "" +msgstr "最后，点击以下其中一个按钮：" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 msgid "" ":guilabel:`Schedule`: adds the activity to the chatter under " ":guilabel:`Planned activities`." -msgstr "" +msgstr ":guilabel:`计划`：将活动添加到 :guilabel:`计划活动`下的沟通栏。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 msgid "" ":guilabel:`Mark as Done`: adds the details of the activity to the chatter " "under :guilabel:`Today`. The activity is not scheduled, it is automatically " "marked as completed." -msgstr "" +msgstr ":guilabel:`标记为完成`：在 :guilabel:`今天` 沟通栏中添加活动的详细信息。该活动不会被安排，而是自动标记为已完成。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 msgid "" ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` " "marked as done, and opens a new activity window." -msgstr "" +msgstr ":guilabel:`完成 \\& 安排下一个`：将任务标记为已完成并添加到:guilabel:`今天` 下，并打开新的活动窗口。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." -msgstr "" +msgstr ":guilabel:`放弃`：放弃在弹出窗口上所做的任何更改。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 msgid "View of CRM leads and the option to schedule an activity." -msgstr "" +msgstr "CRM 潜在客户和安排活动的选项视图。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 msgid "" "Depending on the activity type, the :guilabel:`Schedule` button may be " "replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` " "button." -msgstr "" +msgstr "根据活动类型，:guilabel:`日程安排`按钮可能会被:guilabel:`保存`按钮或:guilabel:`打开日历`按钮取代。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 msgid "" @@ -1059,19 +1156,19 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 msgid "Kanban view" -msgstr "" +msgstr "看板视图" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 msgid "" "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 " "(clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill " "out the pop-up form." -msgstr "" +msgstr "选择要安排活动的记录。点击 :guilabel:`🕘（时钟）` 图标，然后点击 :guilabel:`安排活动`，接着填写弹出的表格。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 msgid "" "Kanban view of the CRM pipeline and the option to schedule an activity." -msgstr "" +msgstr "CRM 管道的看板视图，以及安排活动的选项。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 msgid "List view" @@ -1084,10 +1181,13 @@ msgid "" "has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 " "(phone)` or an :guilabel:`✉️ (envelope)` icon." msgstr "" +"选择要安排活动的记录。点击 :guilabel:`🕘（时钟）` 图标，然后点击 " +":guilabel:`安排活动`。如果记录已安排活动，时钟图标可能会被:guilabel:`📞（电话）` 或:guilabel:`✉️（信封）` " +"图标取代。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 msgid "List view of the CRM pipeline and the option to schedule an activity." -msgstr "" +msgstr "CRM 管道的列表视图，以及安排活动的选项。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 msgid "Activity view" @@ -1123,33 +1223,33 @@ msgstr "" msgid "" "Activity colors, and their relation to an activity's due date, is consistent" " throughout Odoo, regardless of the activity type, or the view." -msgstr "" +msgstr "活动颜色及其与活动到期日的关系在整个 Odoo 中都是一致的，与活动类型或视图无关。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 msgid "" "Activities that appear in **green** indicate a due date sometime in the " "future." -msgstr "" +msgstr "显示为**绿色**的活动表示截止日期在未来某个时候。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 msgid "**Yellow** indicates that the activity's due date is today." -msgstr "" +msgstr "**黄色**表示活动的截止日期是今天。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 msgid "" "**Red** indicates that the activity is overdue and the due date has passed." -msgstr "" +msgstr "**红色**表示活动已逾期，且已过截止日期。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 msgid "" "For example, if an activity is created for a phone call, and the due date " "passes, the activity appears with a red phone in list view, and a red clock " "on the kanban view." -msgstr "" +msgstr "例如，如果为一个电话创建了一个活动，而截止日期已过，则该活动在列表视图中显示为红色电话，在看板视图中显示为红色时钟。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 msgid "View scheduled activities" -msgstr "" +msgstr "查看预定活动" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 msgid "" @@ -1193,43 +1293,44 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 msgid "Configure activity types" -msgstr "" +msgstr "配置活动类型" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 msgid "" "To configure the types of activities in the database, go to " ":menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." -msgstr "" +msgstr "要配置数据库中的活动类型，请访问 :menuselection:` 设置应用程序 --> 讨论 --> 活动 --> 活动类型`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 msgid "View of the settings page emphasizing the menu activity types." -msgstr "" +msgstr "强调菜单活动类型的设置页面视图。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 msgid "" "Doing so reveals the :guilabel:`Activity Types` page, where the existing " "activity types are found." -msgstr "" +msgstr "这样就会显示 :guilabel:`活动类型` 页面，在这里可以找到现有的活动类型。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 msgid "" "To edit an existing activity type, select it from the list, then click " ":guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." msgstr "" +"要编辑现有活动类型，请从列表中选择该类型，然后单击 :guilabel:`编辑`。要创建新的活动类型，请单击 :guilabel:`创建`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 msgid "" "At the top of a blank activity type form, start by choosing a " ":guilabel:`Name` for the new activity type." -msgstr "" +msgstr "在空白活动类型表单的顶部，首先为新活动类型选择 :guilabel:`名称`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 msgid "New activity type form." -msgstr "" +msgstr "新活动类型表单。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 msgid "Activity settings" -msgstr "" +msgstr "活动设置" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 #: ../../content/applications/productivity/studio/automated_actions.rst:134 @@ -1252,19 +1353,19 @@ msgstr "如果选择:guilabel:`上传文档`，则会在聊天记录中的计划 msgid "" "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users " "have the option to open their calendar to schedule a time for this activity." -msgstr "" +msgstr "如果选择了 :guilabel:`电话呼叫` 或 :guilabel:`会议`，用户就可以选择打开日历，为该活动安排时间。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 msgid "" "If :guilabel:`Request Signature` is selected, a link is added to the planned" " activity in the chatter that opens a signature request pop-up window." -msgstr "" +msgstr "如果选择 :guilabel:`请求签名`，则会在聊天记录中的计划活动上添加链接，弹出签名请求窗口。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 msgid "" "The actions available to select on an activity type vary, depending on the " "applications currently installed in the database." -msgstr "" +msgstr "可选择的活动类型上的操作，会根据当前安装在数据库中的应用程序而有所不同。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 msgid "Default user" @@ -1329,6 +1430,9 @@ msgid "" ":guilabel:`after completion date` or :guilabel:`after previous activity " "deadline`." msgstr "" +"在 :guilabel:`时间安排` 字段中，为这些活动选择默认截止日期。为此，请配置所需的 :guilabel:`日`、 :guilabel:`周` " +"或 :guilabel:`月` 数目。然后，决定它应该发生在 :guilabel:`完成日期之后`，还是在 " +":guilabel:`上一个活动截止日期之后`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 @@ -1340,11 +1444,11 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 msgid "When all configurations are complete, click :guilabel:`Save`." -msgstr "" +msgstr "完成所有配置后，单击 :guilabel:`保存`。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst-1 msgid "Schedule activity popup with emphasis on recommended activities." -msgstr "" +msgstr "活动安排弹出窗口，重点推荐活动。" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 msgid "" @@ -1355,7 +1459,7 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 msgid "Trigger next activity" -msgstr "" +msgstr "触发下一个活动" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 msgid "" @@ -1394,7 +1498,7 @@ msgstr ":doc:`team_communication`" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 msgid "Use channels for team communication" -msgstr "" +msgstr "使用频道进行团队沟通" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:5 msgid "" @@ -1409,7 +1513,7 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:11 msgid "Public and private channels" -msgstr "" +msgstr "公共和私有频道" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:13 msgid "" @@ -1459,7 +1563,7 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:42 msgid "Privacy and Members tabs" -msgstr "" +msgstr "隐私和成员选项卡" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:44 msgid "" @@ -1488,7 +1592,7 @@ msgstr "" #: ../../content/applications/productivity/discuss/overview/team_communication.rst-1 msgid "View of Discuss' option to invite members in Odoo Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用中强调邀请成员选项的讨论工具栏视图" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:60 msgid "" @@ -1531,7 +1635,7 @@ msgstr "" msgid "" "View of the Discuss' sidebar emphasizing the quick search bar in Odoo " "Discuss." -msgstr "" +msgstr "Odoo 内部沟通应用中强调快速搜索栏的讨论工具栏视图" #: ../../content/applications/productivity/discuss/overview/team_communication.rst:81 msgid "Finding channels" @@ -1762,13 +1866,13 @@ msgstr "" #: ../../content/applications/productivity/iot/config/connect.rst:79 msgid "WiFi connection" -msgstr "" +msgstr "WiFi 连接" #: ../../content/applications/productivity/iot/config/connect.rst:81 msgid "" "The following is the process to connect the :abbr:`IoT (Internet of Things)`" " box via a WiFi connection to the Odoo database." -msgstr "" +msgstr "以下是通过 WiFi 将 :abbr:`IoT （物联网）` 盒子连接到 Odoo 数据库的过程。" #: ../../content/applications/productivity/iot/config/connect.rst:84 msgid "" @@ -1777,6 +1881,8 @@ msgid "" " (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, " "etc.)." msgstr "" +"首先，确保没有以太网电缆插入 :abbr:`IoT（物联网）`盒子。然后，将所有有线设备连接到 :abbr:`IoT " +"（物联网）`盒子（:abbr:`USB [通用串行总线]` 设备等）。" #: ../../content/applications/productivity/iot/config/connect.rst:88 msgid "" @@ -1788,6 +1894,10 @@ msgid "" "this will later be used to link the Odoo database to the :abbr:`IoT " "(Internet of Things)` box." msgstr "" +"连接设备后，将 :abbr:`IoT（物联网）` 盒子插入电源。在电脑上，导航到 :menuselection:`物联网应用程序 --> " +"物联网盒子`，然后点击位于 :menuselection:`物联网盒子` 面板左上角的 :guilabel:`连接` " +"按钮。然后从:guilabel:`WiFi 连接`部分复制:guilabel:`令牌`，稍后将用于连接 Odoo 数据库和:abbr:`IoT " +"（物联网）盒子`。" #: ../../content/applications/productivity/iot/config/connect.rst:94 msgid "" @@ -1796,10 +1906,12 @@ msgid "" "dispersed by the :abbr:`IoT (Internet of Things)` box will start with " "`IoTBox-xxxxxxxxxx`." msgstr "" +"回到电脑上，导航到可用的 WiFi 网络，并连接到 :abbr:`IoT （物联网）` 盒子 WiFi 网络。由 :abbr:`IoT （物联网）` " +"盒子提供的 WiFi 网络将以 `IoTBox-xxxxxxxxxx` 开头。" #: ../../content/applications/productivity/iot/config/connect.rst-1 msgid "WiFi networks available on the computer." -msgstr "" +msgstr "计算机上可用的 WiFi 网络。" #: ../../content/applications/productivity/iot/config/connect.rst:102 msgid "" @@ -1809,10 +1921,12 @@ msgid "" "previously copied *token* into the :guilabel:`Server Token` field, and then " "click on :guilabel:`Next`." msgstr "" +"连接到 :abbr:`IoT（物联网）` 盒子 WiFi 后，浏览器会自动跳转到 :menuselection:`配置物联网盒子` 向导。命名 " +":abbr:`IoT（物联网）`盒子，然后将先前复制的*令牌*粘贴到 :guilabel:`服务器令牌`字段，然后点击 :guilabel:`下一步`。" #: ../../content/applications/productivity/iot/config/connect.rst-1 msgid "Enter the server token into the IoT box." -msgstr "" +msgstr "在物联网盒子内输入服务器令牌。" #: ../../content/applications/productivity/iot/config/connect.rst:112 msgid "" @@ -1820,6 +1934,7 @@ msgid "" "start, then see the documentation on :ref:`connecting with a token " "<iot_connect/token>`." msgstr "" +"如果 :abbr:`IoT （物联网）`盒子 WiFi 连接向导没有启动，请参阅 :ref:`连接令牌 <iot_connect/token>` 文档。" #: ../../content/applications/productivity/iot/config/connect.rst:115 msgid "" @@ -1830,10 +1945,13 @@ msgid "" "manually re-connected back to the original WiFi connection, if this does not" " happen automatically." msgstr "" +"现在，选择 :abbr:`IoT（物联网）` 盒子将连接的 WiFi 网络（如有密码，请输入密码），然后点击 " +":guilabel:`连接`。等待几秒钟，浏览器将重定向到 :abbr:`IoT （物联网）` 盒子主页。如果无法自动连接，则可能需要手动重新连接到原始" +" WiFi 连接。" #: ../../content/applications/productivity/iot/config/connect.rst-1 msgid "Configuring the WiFi for the IoT box." -msgstr "" +msgstr "为物联网盒子配置 WiFi。" #: ../../content/applications/productivity/iot/config/connect.rst:124 msgid "" @@ -1841,10 +1959,12 @@ msgid "" "appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo" " database." msgstr "" +"完成每个步骤后，在 Odoo 数据库上导航至 :menuselection:`物联网盒子应用程序 --> 物联网盒子` 时，应出现 :abbr:`IoT" +" （物联网）`盒子。" #: ../../content/applications/productivity/iot/config/connect.rst-1 msgid "The IoT box has been successfully configured on the Odoo database." -msgstr "" +msgstr "已在 Odoo 数据库中成功配置物联网盒子。" #: ../../content/applications/productivity/iot/config/connect.rst:132 msgid "" @@ -1853,10 +1973,12 @@ msgid "" " on the Odoo database. To do so, simply unplug the device and plug it back " "into the power source after ten seconds." msgstr "" +"通过 WiFi 成功连接后，可能需要手动重启:abbr:`IoT（物联网）`盒子，使其显示在 Odoo 数据库的 *物联网* " +"应用程序中。要执行此操作，只需拔下设备插头，并在十秒钟后将其重新插入电源即可。" #: ../../content/applications/productivity/iot/config/connect.rst:139 msgid "Manually connecting the IoT box using the token" -msgstr "" +msgstr "使用令牌手动连接物联网盒子" #: ../../content/applications/productivity/iot/config/connect.rst:141 msgid "" @@ -1865,6 +1987,8 @@ msgid "" "computer. The *token* can be found by navigating to :menuselection:`IoT app " "--> IoT Boxes` and clicking on :guilabel:`Connect`." msgstr "" +"可以使用 *令牌* 从电脑手动连接 :abbr:`IoT（物联网）` 盒子和 :abbr:`IoT（物联网）` 应用程序。可通过导航至 " +":menuselection:`物联网应用程序 --> 物联网盒子` 并点击 :guilabel:`连接` 找到*令牌*。" #: ../../content/applications/productivity/iot/config/connect.rst:145 msgid "" @@ -1873,6 +1997,8 @@ msgid "" ":guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet " "of Things)` box homepage." msgstr "" +"在出现的 :guilabel:`连接物联网盒子` 页面的 :guilabel:`WiFi 连接` 部分，单击 :guilabel:`令牌` 右侧的 " +":guilabel:`复制`。该令牌将被输入到 :abbr:`IoT（物联网）` 盒子主页。" #: ../../content/applications/productivity/iot/config/connect.rst:149 msgid "" @@ -1882,6 +2008,8 @@ msgid "" "the :abbr:`IoT (Internet of Things)` box (preferably by ethernet " "connection)." msgstr "" +"通过与 :abbr:`IoT（物联网）` 盒子位于同一网络的计算机（最好使用以太网连接），在浏览器窗口中输入 :abbr:`IoT （物联网）` 盒子的" +" :abbr:`IP（互联网协议）` 地址，访问 :abbr:`IoT（物联网）`盒子主页。" #: ../../content/applications/productivity/iot/config/connect.rst:154 msgid "" @@ -1891,6 +2019,8 @@ msgid "" "box. A receipt will print out with the :abbr:`IoT (Internet of Things)` " "box's :abbr:`IP (Internet Protocol)` address on it." msgstr "" +"可以通过 :abbr:`IoT（物联网）` 盒子所连接的路由器管理控制台，或通过将收据打印机连接到 :abbr:`IoT（物联网）` 盒子，来访问 " +":abbr:`IP（互联网协议）` 地址。打印出的收据上将标有 :abbr:`IoT（物联网）` 盒子的 :abbr:`IP（互联网协议）` 地址。" #: ../../content/applications/productivity/iot/config/connect.rst:159 msgid "" @@ -1900,30 +2030,33 @@ msgid "" ":guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link" " to the Odoo database." msgstr "" +"在 :guilabel:`物联网（IoT）`盒子主页上，点击 :guilabel:`配置`，在 " +":guilabel:`服务器（Server）`部分输入*令牌*。然后，将 *令牌* 粘贴到 :guilabel:`服务器令牌` 字段，点击 " +":guilabel:`连接`。然后，: abbr:`IoT（物联网）` 盒子将链接到 Odoo 数据库。" #: ../../content/applications/productivity/iot/config/connect.rst:167 msgid "IoT box schema" -msgstr "" +msgstr "图解物联网盒子" #: ../../content/applications/productivity/iot/config/connect.rst:170 msgid "Raspberry Pi 4" -msgstr "" +msgstr "Raspberry Pi 4" #: ../../content/applications/productivity/iot/config/connect.rst:174 msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." -msgstr "" +msgstr "Odoo IoT 盒子（Raspberry Pi 4）图解及其标签。" #: ../../content/applications/productivity/iot/config/connect.rst:177 msgid "Raspberry Pi 3" -msgstr "" +msgstr "Raspberry Pi 3" #: ../../content/applications/productivity/iot/config/connect.rst:181 msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." -msgstr "" +msgstr "Odoo IoT 盒子（Raspberry Pi 3）图解及其标签。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 msgid "Flashing the SD card" -msgstr "" +msgstr "刷写 SD 卡" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 msgid "" @@ -1932,10 +2065,12 @@ msgid "" "(Internet of Things)` image update. This means that the Odoo :abbr:`IoT " "(Internet of Things)` box software may need to be updated." msgstr "" +"在某些情况下，:abbr:`IoT（物联网）`盒子的微型 SD 卡可能需要重新刷写，以便获得 Odoo " +"最新的:abbr:`IoT（物联网）`镜像更新。这意味着 Odoo 的:abbr:`IoT（物联网）`盒子软件可能需要更新。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 msgid "Upgrade from the IoT box home page" -msgstr "" +msgstr "从物联网盒子主页升级" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 msgid "" @@ -1999,6 +2134,8 @@ msgid "" "Then download the version-specific :abbr:`IoT (Internet of Things)` image " "from `nightly <http://nightly.odoo.com/master/iotbox/>`_." msgstr "" +"然后从 `nightly <http://nightly.odoo.com/master/iotbox/>`_ 下载特定版本的 " +":abbr:`IoT（物联网）` 镜像。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 msgid "" @@ -2006,14 +2143,16 @@ msgid "" "<http://nightly.odoo.com/master/iotbox/>`_ website with their corresponding " "Odoo database version:" msgstr "" +"以下是 `nightly <http://nightly.odoo.com/master/iotbox/>`_ 网站上的图片版本及其对应的 Odoo " +"数据库版本：" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 msgid "Odoo V16 --> iotbox-latest.zip" -msgstr "" +msgstr "Odoo V16 --> iotbox-latest.zip" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 msgid "Odoo V15 --> iotboxv21_10.zip" -msgstr "" +msgstr "Odoo V15 --> iotboxv21_10.zip" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 msgid "Odoo V14 --> iotboxv21_04.zip" @@ -2026,7 +2165,7 @@ msgstr "Odoo V13 --> iotboxv20_10.zip" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 msgid "" "The images should be downloaded and extracted to a convenient file location." -msgstr "" +msgstr "应将图像下载并解压缩到一个方便的文件位置。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 msgid "" @@ -2036,10 +2175,13 @@ msgid "" "and extracted. Next, select the drive the image should be burned to. Lastly," " click on :guilabel:`Flash` and wait for the process to finish." msgstr "" +"完成此步骤后，将 :abbr:`IoT（物联网）` 盒子的 micro SD 卡插入计算机或读卡器。打开 *Etcher*，选择 " +":guilabel:`Flashfromfile`，然后找到并选择刚刚下载和提取的映像。接着，选择要将映像刻录到的驱动器。最后，点击 " +":guilabel:`Flash`，等待过程结束。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst-1 msgid "Balena's Etcher software dashboard." -msgstr "" +msgstr "Balena 的 Etcher 软件仪表板。" #: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 msgid "" @@ -2047,14 +2189,16 @@ msgid "" "Imager*. Download the *Raspberry Pi* software `here " "<https://www.raspberrypi.com/software/>`_." msgstr "" +"闪存微型 SD 卡的另一个软件是 *Raspberry Pi Imager*。在 " +"<https://www.raspberrypi.com/software/>``_ 下载 *Raspberry Pi* 软件。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 msgid "HTTPS certificate (IoT)" -msgstr "" +msgstr "HTTPS 证书（物联网）" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 msgid "What is HTTPS?" -msgstr "" +msgstr "什么是 HTTPS？" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 msgid "" @@ -2064,6 +2208,8 @@ msgid "" "(Hypertext Transfer Protocol Secure)` is encrypted in order to increase the " "security of data transfer." msgstr "" +"*超文本传输协议安全版*（HTTPS）是*超文本传输协议*（HTTP）的安全版本，HTTP 是网络浏览器和网站之间来回发送数据的主要协议。 " +"为了提高数据传输的安全性， :abbr:`HTTPS（超文本传输协议安全版）`进行了加密。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 msgid "" @@ -2072,6 +2218,7 @@ msgid "" "Security* (TLS), although formerly it was known as *Secure Sockets Layer* " "(SSL)." msgstr "" +":abbr:`HTTPS（超文本传输协议安全）`使用加密协议对通信进行加密。该协议被称为*传输层安全性协议*（TLS），但以前被称为*安全套接层*（SSL）。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 msgid "" @@ -2080,6 +2227,7 @@ msgid "" "Sockets Layer)` certificates, which verify that a particular provider is who" " they say they are." msgstr "" +":abbr:`HTTPS（超文本传输协议安全）是基于:abbr:`TLS（传输层安全）`/:abbr:`SSL（安全套接字层）`证书的传输而发生的，这些证书可验证特定提供商的真实身份。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 msgid "" @@ -2088,10 +2236,12 @@ msgid "" "certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol " "Secure)` connection." msgstr "" +"在本文档和整个 Odoo 中，\"HTTPS 证书 \"一词将用于定义 :abbr:`SSL （安全套接字层）` 证书有效并允许 " +":abbr:`HTTPS （超文本传输协议安全）` 连接的事实。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 msgid "Why is it needed?" -msgstr "" +msgstr "为什么需要？" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 msgid "" @@ -2101,16 +2251,18 @@ msgid "" "Secure)` certificate isn't valid, some devices won't be able to interact " "with the :abbr:`IoT (Internet of Things)` Box." msgstr "" +"为了与某些网络设备（特别是支付终端）进行通信，必须使用 : abbr:`HTTPS（超文本传输协议安全）`。如果 " +":abbr:`HTTPS（超文本传输协议安全）` 证书无效，某些设备将无法与 :abbr:`IoT（物联网）` 盒子进行交互。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" -msgstr "" +msgstr "如何获取安全超文本传输协议（HTTPS）证书" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 msgid "" "The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " "certificate is automatic." -msgstr "" +msgstr ":abbr:`HTTPS（超文本传输协议安全）`证书是自动生成的。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 msgid "" @@ -2119,63 +2271,66 @@ msgid "" "Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of " "Things)` box and database are eligible." msgstr "" +"如果 :abbr:`IoT（物联网）` 盒子和数据库符合条件，则 :abbr:`IoT（物联网）` 盒子将向 " +"`<https://www.odoo.com>`_ 发送特定请求，而 `<https://www.odoo.com>`_ 将发回 " +":abbr:`HTTPS（超文本传输协议安全）` 证书。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 msgid "Internet of Things (IoT) eligibility" -msgstr "" +msgstr "物联网（IoT）资格" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 msgid "" "The database should be a **production** instance. The database instance " "should not be a copy, a duplicate, a staging, or a development environment." -msgstr "" +msgstr "数据库应为**生产**实例。数据库实例不应是副本、复制件、暂存或开发环境。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 msgid "The Odoo subscription must:" -msgstr "" +msgstr "Odoo 订阅必须：" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 msgid "Have an :guilabel:`IoT Box Subscription` line." -msgstr "" +msgstr "设置 :guilabel:`物联网盒子订阅` 行。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 msgid ":guilabel:`Status` must be :guilabel:`In Progress`." -msgstr "" +msgstr ":guilabel:`状态` 必须为 :guilabel:`进行中`。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 msgid "" "If the subscription is linked to a `<https://www.odoo.com>`_ portal user " "check the information on the portal subscription page." -msgstr "" +msgstr "如果订阅与`<https://www.odoo.com>`_门户用户相关联，请检查门户订阅页面上的信息。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 msgid "Odoo.com portal subscriptions filtered by \"in progress\"." -msgstr "" +msgstr "按 \"进行中\" 筛选的 Odoo.com 门户订阅。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 msgid "" "In this case, both subscriptions are considered \"in progress\" as the " ":guilabel:`Filter By\\: In Progress` was used." -msgstr "" +msgstr "在这种情况下，由于使用了 :guilabel:`筛选项\\: 进行中`，因此两个订阅都被视为 \"进行中\"。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 msgid "" "If the subscription is in question, contact the database's Account Manager " "or Partner regarding the matter." -msgstr "" +msgstr "如果订阅有问题，请联系数据库的客户经理或合作伙伴咨询相关事宜。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 msgid "" "Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate " "errors" -msgstr "" +msgstr "超文本传输协议安全（HTTPS）证书错误的故障排除" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 msgid "" "If anything goes wrong during the process of the \"HTTPS certificate\" " "generation or reception, a specific error will code be given on the " ":abbr:`IoT (Internet of Things)` box home page." -msgstr "" +msgstr "如果在生成或接收 \"HTTPS 证书\" 的过程中出现任何问题，\"IoT（物联网）\"盒子主页上将给出特定的错误代码。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 msgid "" @@ -2185,10 +2340,12 @@ msgid "" " Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home " "page to see if the error disappears." msgstr "" +"访问 :abbr:`IoT（物联网）`盒子主页将检查是否存在 \"HTTPS 证书\"，如果缺少该证书，将尝试生成。因此，如果在 " +":abbr:`IoT（物联网）` 盒子主页上出现错误，请刷新 :abbr:`IoT（物联网）` 主页以查看错误是否消失。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 @@ -2203,7 +2360,7 @@ msgstr "原因：" msgid "" "The configuration regarding the server is missing. In other words, the Odoo " "instance is not connected with the IoT box." -msgstr "" +msgstr "缺少有关服务器的配置。换句话说，Odoo 实例未与 IoT 盒子连接。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 @@ -2212,53 +2369,53 @@ msgstr "" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:159 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 msgid "Solution:" -msgstr "" +msgstr "解决方案：" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 msgid "Ensure that the server is configured." -msgstr "" +msgstr "确保服务器已配置。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 #: ../../content/applications/productivity/iot/config/windows_iot.rst:99 msgid ":doc:`/applications/productivity/iot/config/connect`" -msgstr "" +msgstr ":doc:`/applications/productivity/iot/config/connect`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 msgid "" "An unhandled error happened when trying to read the existing :abbr:`HTTPS " "(Hypertext Transfer Protocol Secure)` certificate." -msgstr "" +msgstr "在尝试读取现有的 :abbr:`HTTPS（超文本传输协议安全）` 证书时发生了一个未处理的错误。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 msgid "" "Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` " "certificate file is readable." -msgstr "" +msgstr "确保 :abbr:`HTTPS（超文本传输协议安全）` 证书文件可读。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 msgid "" "The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is " "missing." -msgstr "" +msgstr "缺少合同和/或数据库 :abbr:`UUID（通用唯一标识符）`。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 msgid "" "Ensure that both values are configured as intended. To modify them, go to " "the :abbr:`IoT (Internet of Things)` box home page, and navigate to " ":guilabel:`Credential`." -msgstr "" +msgstr "确保这两个值均按预期配置。要修改它们，请访问 :abbr:`IoT （物联网）` 合作主页，并导航至 :guilabel:`证书`。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 msgid "" @@ -2266,11 +2423,13 @@ msgid "" "tried to reach `<https://www.odoo.com>`_. The causes are likely due to the " "network infrastructure/configuration:" msgstr "" +"当 :abbr:`IoT（物联网）` 盒子试图访问 " +"`<https://www.odoo.com>`_时，发生了意外错误。原因可能与网络基础设施/配置有关：" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 msgid "" "The :abbr:`IoT (Internet of Things)` box does not have access to internet." -msgstr "" +msgstr ":abbr:`IoT（物联网）` 盒子无法访问互联网。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 msgid "" @@ -2279,24 +2438,27 @@ msgid "" "devices preventing the communication (firewalls, etc.) or the network " "configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." msgstr "" +"网络不允许 :abbr:`IoT （物联网）`盒子与 " +"`<https://www.odoo.com>`_进行通信。这可能是由于网络设备（防火墙等）或网络配置（:abbr:`VPN " +"[虚拟专用网络]`等）阻止了通信。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 msgid "" "More information regarding the error that occurred can be found in the full " "request exception details, which are in the :abbr:`IoT (Internet of Things)`" " box logs." -msgstr "" +msgstr "有关发生错误的更多信息，请参阅完整的请求异常详细信息，这些信息位于:abbr:`IoT（物联网）` 盒子日志中。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 msgid "" "Consult with your system or network administrator should this issue arise. " "This error code depends on the network infrastructure and goes beyond Odoo " "support's service scope." -msgstr "" +msgstr "如果出现此问题，请咨询您的系统或网络管理员。此错误代码取决于网络基础设施，超出了 Odoo 支持的服务范围。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:140 msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:143 msgid "" @@ -2304,6 +2466,8 @@ msgid "" "unusual `HTTP response (status codes) <https://developer.mozilla.org/en-" "US/docs/Web/HTTP/Status>`_." msgstr "" +"IoT-box 能够访问 `<https://www.odoo.com>`_，但收到了异常的 " +"`HTTP响应（状态码）<https://developer.mozilla.org/en-US/docs/Web/HTTP/Status>`_。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:147 msgid "" @@ -2311,18 +2475,20 @@ msgid "" "if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the" " page returned a 404 error, which is the \"Page Not Found\" code." msgstr "" +"该错误代码还会给出 HTTP 响应状态代码。例如，如果错误读数为`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS " +"404`，则表示页面返回 404 错误，即 \"未找到页面\" 代码。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:152 msgid "" "Check if `<https://www.odoo.com>`_ is down using a web browser, as it's " "possible that it is down due to maintenance." -msgstr "" +msgstr "使用网络浏览器检查`<https://www.odoo.com>`_是否关闭，因为有可能是由于维护而关闭。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:155 msgid "" "If `<https://www.odoo.com>`_ is down due to maintenance, unfortunately there" " is nothing that can be done but instead wait for it to recover." -msgstr "" +msgstr "如果 `<https://www.odoo.com>`_ 因维护而停机，很遗憾，我们什么也做不了，只能等待它恢复。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:157 msgid "" @@ -2330,10 +2496,12 @@ msgid "" " ticket <https://www.odoo.com/help>`_ on the matter. Ensure that the 3 " "digits status code next to the code error is included in the support ticket." msgstr "" +"如果 `<https://www.odoo.com>`_ 没有因维护而停机，请就此问题开立一张 `支持工单 " +"<https://www.odoo.com/help>`_。确保支持工单中包含代码错误旁边的 3 位状态代码。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:162 msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" -msgstr "" +msgstr "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:165 msgid "" @@ -2341,6 +2509,8 @@ msgid "" "`<https://www.odoo.com>`_ but it refused to deliver the :abbr:`HTTPS " "(Hypertext Transfer Protocol Secure)` certificate." msgstr "" +":abbr:`IoT（物联网）`盒子能够到达 `<https://www.odoo.com>`_，但它拒绝提供 :abbr:`HTTPS " +"（超文本传输协议安全）`证书。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:169 msgid "" @@ -2351,7 +2521,7 @@ msgstr "" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:173 msgid "How to ensure that the HTTPS certificate is correct" -msgstr "" +msgstr "如何确保 HTTPS 证书正确无误" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:175 msgid "" @@ -2361,42 +2531,45 @@ msgid "" "will appear on the Odoo database, inside of the :menuselection:`IoT` " "application on that specific device's form." msgstr "" +"如果证书已成功应用，一个新的: " +"abbr:`HTTPS（超文本传输协议安全）`:abbr:`URL（统一资源定位符）`的:abbr:`IoT（物联网）`盒子将出现在 Odoo " +"数据库中，在该特定设备表单上的:menuselection:`物联网`应用程序内。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 msgid "Odoo IoT app IoT box with .odoo-iot.com domain." -msgstr "" +msgstr "带有 .odoo-iot.com 域名的 Odoo 物联网应用程序物联网盒子。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:184 msgid "" "When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a" " secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will " "be established." -msgstr "" +msgstr "在浏览器中导航到:abbr:`URL（统一资源定位符）`时，将建立一个安全的:abbr:`HTTPS（超文本传输协议安全）`连接。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 msgid "Example of valid SSL certificate details on the browser." -msgstr "" +msgstr "浏览器上有效 SSL 证书详细信息示例。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 msgid "" "Padlock in Chrome on Windows 10 attesting the fact that the connection is " "secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." -msgstr "" +msgstr "Windows 10 上 Chrome 浏览器中的挂锁，证明连接已通过 :abbr:`HTTPS（超文本传输协议安全）` 加密。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:194 msgid "" "The IoT-box homepage will now display an `OK` status next to `HTTPS " "certificate`. The drop-down menu icon, when clicked, will reveal information" " regarding the certificate." -msgstr "" +msgstr "现在，IoT-box 主页将在`HTTPS 证书`旁边显示`确认`状态。点击下拉菜单图标后，将显示有关证书的信息。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst-1 msgid "IoT box homepage with HTTPS certificate OK status." -msgstr "" +msgstr "物联网盒子主页显示 HTTPS 证书确认状态。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:202 msgid "Domain Name System (DNS) issue" -msgstr "" +msgstr "域名系统（DNS）问题" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:204 msgid "" @@ -2407,6 +2580,9 @@ msgid "" "will give an error code mentioning :abbr:`DNS (Domain Name System)` (like " "`DNS_PROBE_FINISHED_NXDOMAIN`)." msgstr "" +"如果 :abbr:`IoT（物联网）` 盒子可以通过其 :abbr:`IP（内网协议）` 地址访问，但不能访问 Odoo 分配的域：`.odoo-" +"iot.com`；那么 :abbr:`IoT（物联网）` 盒子很可能遇到了 :abbr:`DNS（域名系统）` 问题。在某些浏览器上，它会给出提及 " +":abbr:`DNS（域名系统）` 的错误代码（如 `DNS_PROBE_FINISHED_NXDOMAIN`）。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:209 msgid "" @@ -2416,34 +2592,34 @@ msgstr "" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:213 msgid "Chrome" -msgstr "" +msgstr "Chrome" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:219 msgid "DNS issue on Chrome browser on Windows 10." -msgstr "" +msgstr "Windows 10 上 Chrome 浏览器的 DNS 问题。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:222 msgid "Firefox" -msgstr "" +msgstr "Firefox" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:228 msgid "DNS issue on Firefox browser on Windows 10." -msgstr "" +msgstr "Windows 10 上 Firefox 浏览器的 DNS 问题。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:230 msgid "Edge" -msgstr "" +msgstr "Edge" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:236 msgid "DNS issue on Edge browser on Windows 10." -msgstr "" +msgstr "Windows 10 上 Edge 浏览器的 DNS 问题。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:240 msgid "Domain Name System (DNS) issue solution" -msgstr "" +msgstr "域名系统（DNS）问题解决方案" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:242 msgid "" @@ -2451,6 +2627,8 @@ msgid "" "changed, change the DNS to use `Google DNS " "<https://developers.google.com/speed/public-dns>`_." msgstr "" +"如果路由器允许手动更改 :abbr:`DNS（域名系统）`，请将 DNS 更改为使用 `Google DNS " +"<https://developers.google.com/speed/public-dns>`_。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:244 msgid "" @@ -2462,6 +2640,9 @@ msgid "" "device configuration processes can be found on the website of the device's " "manufacturer." msgstr "" +"如果您的路由器不允许这样做，则需要使用 `Google DNS <https://developers.google.com/speed/public-" +"dns>`_对每台设备的 :abbr:`DNS （域名系统）`设置进行更改。这需要在计划与 :abbr:`IoT （物联网）` " +"盒子（如电脑、平板电脑或手机）进行交互的**每台**设备上进行。各个设备的配置过程可在设备制造商的网站上找到。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:252 msgid "" @@ -2469,17 +2650,19 @@ msgid "" "likely won't need their :abbr:`DNS (Domain Name System)` settings changed as" " they are already configured with custom :abbr:`DNS (Domain Name System)`." msgstr "" +"其他 :abbr:`IoT （物联网）` 设备，如支付终端，可能不需要更改其 :abbr:`DNS （域名系统）` 设置，因为它们已经配置了自定义 " +":abbr:`DNS （域名系统）`。" #: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:257 msgid "" "Consult with your system or network administrator should this issue arise. " "This error code depends on the network infrastructure, and it goes beyond " "Odoo support's service scope." -msgstr "" +msgstr "如果出现此问题，请咨询您的系统或网络管理员。此错误代码取决于网络基础设施，超出了 Odoo 支持的服务范围。" #: ../../content/applications/productivity/iot/config/pos.rst:3 msgid "Use an IoT box with a PoS" -msgstr "" +msgstr "使用带有 PoS 的物联网盒子" #: ../../content/applications/productivity/iot/config/pos.rst:6 msgid "Prerequisites" @@ -2487,33 +2670,33 @@ msgstr "先决条件" #: ../../content/applications/productivity/iot/config/pos.rst:8 msgid "Before starting, make sure the following equipment is available:" -msgstr "" +msgstr "启动前，请确保以下设备已准备就绪：" #: ../../content/applications/productivity/iot/config/pos.rst:10 msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." -msgstr "" +msgstr "带电源适配器的:abbr:`IoT（物联网）`盒子。" #: ../../content/applications/productivity/iot/config/pos.rst:11 msgid "A computer or tablet with an up-to-date web browser." -msgstr "" +msgstr "配备最新网络浏览器的电脑或平板电脑。" #: ../../content/applications/productivity/iot/config/pos.rst:12 msgid "" "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* " "applications installed." -msgstr "" +msgstr "Odoo 云端版或安装了*销售点*和*物联网*应用程序的 Odoo 实例。" #: ../../content/applications/productivity/iot/config/pos.rst:13 msgid "" "A local network set up with :abbr:`DHCP (Dynamic Host Configuration " "Protocol)` (this is the default setting)." -msgstr "" +msgstr "使用 :abbr:`DHCP （动态主机配置协议）` 设置的本地网络（默认设置）。" #: ../../content/applications/productivity/iot/config/pos.rst:15 msgid "" "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already " "built in)." -msgstr "" +msgstr "RJ45 以太网电缆（可选，但优先选择，优于已经内置的WiFi）。" #: ../../content/applications/productivity/iot/config/pos.rst:16 msgid "" @@ -2522,6 +2705,8 @@ msgid "" "supported hardware can be found on the `POS Hardware page " "<https://www.odoo.com/page/point-of-sale-hardware>`_." msgstr "" +"任何支持的硬件（收据打印机、条形码扫描仪、钱箱、支付终端、电子秤、客户显示器等）。支持的硬件列表可在 `POS 硬件页面 " +"<https://www.odoo.com/page/point-of-sale-hardware>`_ 中找到。" #: ../../content/applications/productivity/iot/config/pos.rst:21 msgid "Setup" @@ -2529,7 +2714,7 @@ msgstr "设置" #: ../../content/applications/productivity/iot/config/pos.rst:25 msgid "A suggested configuration for a point of sale system." -msgstr "" +msgstr "销售点系统的建议配置。" #: ../../content/applications/productivity/iot/config/pos.rst:27 msgid "" @@ -2538,12 +2723,14 @@ msgid "" "this, follow these instructions: :doc:`Connect an Internet of Things (IoT) " "box to the Odoo database <connect>`." msgstr "" +"要将硬件连接到 :abbr:`PoS（销售点）`，第一步是将:abbr:`IoT（物联网）`盒子连接到数据库。请按照以下说明操作： " +":doc:`将物联网（IoT）盒子连接到 Odoo 数据库<connect>`。" #: ../../content/applications/productivity/iot/config/pos.rst:31 msgid "" "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)`" " box." -msgstr "" +msgstr "然后，将外围设备连接到 :abbr:`IoT （物联网）` 盒子上。" #: ../../content/applications/productivity/iot/config/pos.rst:37 msgid "Device Name" @@ -2564,27 +2751,29 @@ msgid "" "port or to the network, and power it on. Refer to " ":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." msgstr "" +"将支持的收据打印机连接到 :abbr:`USB（通用串行总线）` 端口或网络，并打开电源。请参阅 " +":doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing` 。" #: ../../content/applications/productivity/iot/config/pos.rst:43 #: ../../content/applications/productivity/iot/config/troubleshooting.rst:391 msgid "Cash drawer" -msgstr "" +msgstr "钱箱" #: ../../content/applications/productivity/iot/config/pos.rst:44 msgid "The cash drawer should be connected to the printer with an RJ25 cable." -msgstr "" +msgstr "应使用 RJ25 电缆将钱箱连接到打印机。" #: ../../content/applications/productivity/iot/config/pos.rst:45 #: ../../content/applications/productivity/iot/config/troubleshooting.rst:359 msgid "Barcode scanner" -msgstr "" +msgstr "条形码扫描器" #: ../../content/applications/productivity/iot/config/pos.rst:46 msgid "" "In order for the barcode scanner to be compatible it must end barcodes with " "an `ENTER` character (keycode 28). This is most likely the default " "configuration of the barcode scanner." -msgstr "" +msgstr "为了与条形码扫描仪兼容，条形码必须以 `ENTER` 字符（键码 28）结束。这很可能是条形码扫描仪的默认配置。" #: ../../content/applications/productivity/iot/config/pos.rst:48 msgid "Scale" @@ -2594,11 +2783,11 @@ msgstr "比例" msgid "" "Connect the scale and power it on. Refer to " ":doc:`/applications/productivity/iot/devices/scale`." -msgstr "" +msgstr "连接电子秤并接通电源。请参阅 :doc:`/applications/productivity/iot/devices/scale`。" #: ../../content/applications/productivity/iot/config/pos.rst:51 msgid "Customer display" -msgstr "" +msgstr "客户显示器" #: ../../content/applications/productivity/iot/config/pos.rst:52 msgid "" @@ -2606,10 +2795,12 @@ msgid "" ":abbr:`PoS (Point of Sale)` order. Refer to " ":doc:`/applications/productivity/iot/devices/screen`." msgstr "" +"将屏幕连接到 :abbr:`IoT（物联网）` 盒子，以显示 :abbr:`PoS （销售点）` 订单。请参阅 " +":doc:`/applications/productivity/iot/devices/screen` 。" #: ../../content/applications/productivity/iot/config/pos.rst:54 msgid "Payment terminal" -msgstr "" +msgstr "支付终端" #: ../../content/applications/productivity/iot/config/pos.rst:55 msgid "" @@ -2617,6 +2808,8 @@ msgid "" "terminals documentation " "</applications/sales/point_of_sale/payment_methods>`." msgstr "" +"连接过程取决于终端。请参阅 :doc:` " +"支付终端文档</applications/sales/point_of_sale/payment_methods>`。" #: ../../content/applications/productivity/iot/config/pos.rst:58 msgid "" @@ -2626,16 +2819,19 @@ msgid "" ":guilabel:`IoT Box` option, and select the devices to be used in this " ":abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." msgstr "" +"完成后，将 :abbr:`IoT（物联网）` 盒子连接到 :menuselection:`PoS` 应用程序。要执行此操作，请进入 " +":menuselection:`销售点 --> 配置 --> PoS`，勾选 :guilabel:`物联网盒子` 选项，并选择要在此 " +":abbr:`PoS（销售点）` 中使用的设备。" #: ../../content/applications/productivity/iot/config/pos.rst-1 msgid "Configuring the connected devices in the POS application." -msgstr "" +msgstr "在 POS 应用程序中配置已连接的设备。" #: ../../content/applications/productivity/iot/config/pos.rst:67 msgid "" "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be " "launched." -msgstr "" +msgstr "设置完成后，就可以启动一个新的 :abbr:`PoS（销售点）` 会话。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 #: ../../content/applications/productivity/iot/config/windows_iot.rst:105 @@ -2644,18 +2840,18 @@ msgstr "故障排除" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 msgid "IoT box connection" -msgstr "" +msgstr "物联网盒子连接" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 msgid "Unable to locate the pairing code to connect the IoT box" -msgstr "" +msgstr "无法找到连接物联网盒子的配对代码" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 msgid "" "The pairing code should be printed on receipt printers connected to the " ":abbr:`IoT (Internet of Things)` box and should also be displayed on " "connected monitors." -msgstr "" +msgstr "配对代码应打印在连接到 :abbr:`IoT （物联网）` 盒子的收据打印机上，还应在连接的显示器上显示。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 msgid "The pairing code doesn't show under the following circumstances:" @@ -2665,19 +2861,19 @@ msgstr "以下情况不显示配对码：" msgid "" "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo " "database." -msgstr "" +msgstr ":abbr:`IoT（物联网）`盒子已连接到 Odoo 数据库。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 msgid "" "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." -msgstr "" +msgstr ":abbr:`IoT（物联网）`盒子没有连接到互联网。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 msgid "" "The code is only valid for 5 minutes after the :abbr:`IoT (Internet of " "Things)` box has started. It's automatically removed from connected displays" " when this time has expired." -msgstr "" +msgstr "代码仅在 :abbr:`IoT （物联网）` 盒子启动后 5 分钟内有效。过期后，它将自动从连接的显示器中移除。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 msgid "" @@ -2687,6 +2883,8 @@ msgid "" " re-flashed to update the image (see :doc:`Flashing the SD Card " "<flash_sdcard>`)." msgstr "" +"物联网盒子镜像的版本太旧。如果 :abbr:`IoT（物联网）` 盒子的映像来自较早的版本，则需要重新刷新 :abbr:`IoT （物联网）` 盒子的 " +"SD 卡以更新映像（请参阅 :doc:`刷写 SD 卡<flash_sdcard>`）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 msgid "" @@ -2708,16 +2906,18 @@ msgid "" "can reach the database and that the server doesn't use a multi-database " "environment." msgstr "" +"当 :abbr:`IoT （物联网）` 盒子连接到数据库时，它可能会重新启动。如果是这样，可能需要至多 5 分钟才能出现在数据库中。如果 5 " +"分钟后仍未显示 :abbr:`IoT（物联网）` 盒子，请确保 :abbr:`IoT（物联网）` 盒子可以访问数据库，并且服务器不使用多数据库环境。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 msgid "" "To access the database from the :abbr:`IoT (Internet of Things)` box, open a" " browser and type in the database address." -msgstr "" +msgstr "要从 :abbr:`IoT（物联网）` 盒子访问数据库，请打开浏览器并输入数据库地址。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 msgid "The IoT box is connected to the Odoo database, but cannot be reached" -msgstr "" +msgstr "我的物联网盒子已连接到我的数据库，但无法访问" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 msgid "" @@ -2725,6 +2925,7 @@ msgid "" "running the browser are located on the same network, as the :abbr:`IoT " "(Internet of Things)` box cannot be reached from outside the local network." msgstr "" +"确保 :abbr:`IoT（物联网）` 盒子和运行浏览器的计算机位于同一网络，因为 :abbr:`IoT（物联网）` 盒子无法从本地网络之外进行访问。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 msgid "The HTTPS certificate doesn't generate" @@ -2752,22 +2953,22 @@ msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 msgid ":doc:`HTTPS certificate (IoT) <https_certificate_iot>`" -msgstr "" +msgstr ":doc:`HTTPS 证书（物联网）<https_certificate_iot>`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 msgid "The printer is not detected" -msgstr "" +msgstr "未检测到打印机" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 msgid "" "If a printer doesn't show up in the devices list, go to the :abbr:`IoT " "(Internet of Things)` box homepage and make sure that it is listed under " ":guilabel:`Printers`." -msgstr "" +msgstr "如果打印机没有显示在设备列表中，请访问:abbr:`IoT（物联网）` 盒子主页，确保它列在:guilabel:`打印机`下。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 msgid "The IoT box Home Page landing page." -msgstr "" +msgstr "物联网盒子主页着陆页。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 msgid "" @@ -2776,10 +2977,12 @@ msgid "" ":guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the " "printer is not present in the list, it's likely not connected properly." msgstr "" +"如果打印机不在 :abbr:`IoT（物联网）`盒子主页，请单击 :guilabel:`打印机服务器`，转到 :guilabel:`管理`选项卡并单击 " +":guilabel:`添加打印机`。如果打印机未出现在列表中，则很可能连接不正确。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 msgid "The printer outputs random text" -msgstr "" +msgstr "我打印机输出随机文本" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 msgid "" @@ -2788,6 +2991,7 @@ msgid "" "not be enough, and if no driver is found, the printer might print random " "characters." msgstr "" +"对于大多数打印机，应自动检测并选择正确的驱动程序。然而，在某些情况下，自动检测机制可能不够，如果没有找到驱动程序，打印机可能会打印随机字符。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 msgid "" @@ -2798,10 +3002,13 @@ msgid "" " Printer`. Follow the steps and select the *make* and *model* corresponding " "to the printer." msgstr "" +"解决方案是手动选择相应的驱动程序。在 :abbr:`IoT（物联网）`盒子主页上，点击 :guilabel:`打印机服务器`，进入 " +":guilabel:`打印机`选项卡并在列表中选择打印机。在 :guilabel:`管理` 下拉菜单中，点击 " +":guilabel:`更改打印机`。按照步骤选择与打印机相对应的*品牌*和*型号*。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 msgid "Edit the printer connected to the IoT box." -msgstr "" +msgstr "编辑连接到物联网盒子的打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:99 msgid "" @@ -2811,7 +3018,7 @@ msgstr "Epson和Star收据打印机和Zebra标签打印机不需要驱动程序 #: ../../content/applications/productivity/iot/config/troubleshooting.rst:103 msgid "Epson configuration special case" -msgstr "" +msgstr "爱普生配置专案" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:105 msgid "" @@ -2819,42 +3026,43 @@ msgid "" "Sale)` using the `GS v 0` command. However, the following Epson printer " "models do not support this command:" msgstr "" +"大多数爱普生打印机都支持使用 `GS v 0` 指令在 Odoo :abbr:`POS（销售点）` 中打印收据。但是，以下爱普生打印机型号不支持此指令：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:108 msgid "TM-U220" -msgstr "" +msgstr "TM-U220" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 msgid "TM-U230" -msgstr "" +msgstr "TM-U230" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 msgid "TM-P60" -msgstr "" +msgstr "TM-P60" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 msgid "TMP-P60II" -msgstr "" +msgstr "TMP-P60II" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:113 msgid "" "Bypass this issue by configuring the printer to use the `ESC *` command " "instead." -msgstr "" +msgstr "将打印机配置为使用 `ESC*` 指令，即可绕过这一问题。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:116 msgid "Process to force ESC * command" -msgstr "" +msgstr "强制执行 ESC * 指令的流程" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:119 msgid "Epson printer compatibility" -msgstr "" +msgstr "爱普生打印机兼容性" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:121 msgid "" "The first step is to check whether the printer is incompatible with `GS v 0`" " command." -msgstr "" +msgstr "第一步是检查打印机是否与 `GS v 0` 指令不兼容。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:125 msgid "" @@ -2862,6 +3070,8 @@ msgid "" "biz.com/modules/ref_escpos/index.php? content_id=94>`_ for `GS v 0` " "compatible printers." msgstr "" +"`Epson GS v 0 文档 <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php? content_id=94>``_ 适用于 `GS v 0` 兼容打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:127 msgid "" @@ -2869,6 +3079,8 @@ msgid "" "biz.com/modules/ref_escpos/index.php ?content_id=88>`_ for `ESC *` " "compatible printers." msgstr "" +"`Epson ESC * 文档 <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php ?content_id=88>`_ 适用于 `ESC *` 兼容打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:130 msgid "" @@ -2877,10 +3089,12 @@ msgid "" "*` command to print, follow this process to configure the printer with the " ":abbr:`IoT (Internet of Things)` box." msgstr "" +"如果打印机不兼容 `ESC *` 指令，则无法执行以下流程。如果打印机兼容使用 `ESC *` 指令打印，请按照以下步骤使用 " +":abbr:`IoT（物联网）` 盒子配置打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:135 msgid "IoT box configuration for ESC *" -msgstr "" +msgstr "用于 ESC* 的物联网盒子配置" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:137 msgid "" @@ -2890,10 +3104,13 @@ msgid "" ":guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of " "Things)` box homepage." msgstr "" +"要配置 :abbr:`IoT（物联网）` 盒子使用 `ESC *` 命令打印，请通过导航至 :menuselection:`物联网应用程序 --> " +"物联网盒子` 进入 :abbr:`IoT（物联网）` 盒子主页。然后点击 :guilabel:`IP地址`，将引导您进入 " +":abbr:`IoT（物联网）` 盒子主页。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:142 msgid "**Choosing the printer**" -msgstr "" +msgstr "**选择打印机**" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:144 msgid "" @@ -2902,39 +3119,41 @@ msgid "" "Printers --> Add Printer`, choose the printer that should be modified, and " "then click :guilabel:`Continue`." msgstr "" +"现在点击 :guilabel:`打印机服务器` 按钮。这将把浏览器重定向到 *CUPS* 页面。接下来，进入 :menuselection:`管理 " +"--> 打印机 --> 添加打印机`，选择要修改的打印机，然后单击 :guilabel:`继续`。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:149 msgid "" "If the name of the printer is still uncertain, take the following steps:" -msgstr "" +msgstr "如果打印机名称仍不确定，请采取以下步骤：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:151 msgid "Take note of the listed printers on the *CUPS* page." -msgstr "" +msgstr "注意*CUPS*页面上列出的打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 msgid "Turn the printer off and refresh the page." -msgstr "" +msgstr "关闭打印机并刷新页面。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:153 msgid "" "Now compare the difference with the first list to see which printer " "disappeared." -msgstr "" +msgstr "现在比较两个列表的差异，查看哪个打印机消失了。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 msgid "Turn the printer back on and refresh the page again." -msgstr "" +msgstr "重新打开打印机，再次刷新页面。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:155 msgid "Double-check the list again to see if the printer re-appears." -msgstr "" +msgstr "再次仔细检查列表，看看打印机是否再次出现。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:156 msgid "" "The printer that disappeared and reappears again on the listed printers is " "the name of the printer in question." -msgstr "" +msgstr "消失并重新出现在打印机列表的就是该打印机名称。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:160 msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." @@ -2958,37 +3177,38 @@ msgid "" "The :guilabel:`Name` should match this convention: " "`<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`" msgstr "" +":guilabel:`名称`应符合以下约定：`<printer_name>__IMC_<param_1>_<param_2>_..._<param_n>__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:172 msgid "A breakdown of the naming convention:" -msgstr "" +msgstr "命名规则的细分：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:174 msgid "" "`printer_name`: This is the printer name. It can be any character as long as" " it does not contain `_`, `/`, `#`, or ` ` (space character)." -msgstr "" +msgstr "`打印机名称`：这是打印机的名称。它可以是任何字符，只要不包含`_`、`/`、`#`、或 ` `（空格字符）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:176 msgid "" "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC " "*`)." -msgstr "" +msgstr "`IMC`：代表*图像模式列*（`ESC *`的简化名称）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 msgid "`param_1`: This stands for the specific parameter:" -msgstr "" +msgstr "`param_1`：代表特定参数：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:179 msgid "" "`SCALE<X>`: Scale of the picture (with the same aspect ratio). `X` should be" " an integer describing the scale percentage that should be used." -msgstr "" +msgstr "`缩放<X>`：图片的缩放比例（保持相同的纵横比）。`X` 应该是一个整数，描述应该使用的缩放百分比。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:183 msgid "" "`100` is the original size, `50` is half the size, `200` is twice the size." -msgstr "" +msgstr "`100` 是原始大小，`50` 是一半大小，`200` 是两倍大小。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:185 msgid "" @@ -3015,10 +3235,12 @@ msgid "" "printer model printer in the table above to see if the printer should set " "these parameters." msgstr "" +"访问 `Epson's ESC * 文档 <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_，并在上面的表格中点击打印机型号，以查看是否应该设置这些参数。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:198 msgid "The following are examples of proper and improper name formatting:" -msgstr "" +msgstr "以下是正确和不正确名称格式的示例：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:200 msgid "Proper name formatting:" @@ -3026,36 +3248,36 @@ msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:202 msgid "`EPSONTMm30II__IMC__`" -msgstr "" +msgstr "`EPSONTMm30II__IMC__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" -msgstr "" +msgstr "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:205 msgid "" "Improper name formatting (this will not prevent printing, but the result " "might not have the expected printed output):" -msgstr "" +msgstr "名称格式不正确（不会妨碍打印，但结果可能不是预期的打印内容）：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:208 msgid "`EPSON TMm 30II` -> The name can't have spaces." -msgstr "" +msgstr "`EPSON TMm 30II` -> 名称不能有空格。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 msgid "" "`EPSONTMm30II` -> The name itself is correct, but it won't use `ESC *`." -msgstr "" +msgstr "`EPSONTMm30II` -> 名称本身是正确的，但不会使用 `ESC*`。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:210 msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." -msgstr "" +msgstr "`EPSONTMm30II__IMC` -> 该名称缺少结尾 `__`。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 msgid "" "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing" " parameters." -msgstr "" +msgstr "`EPSONTMm30II__IMC_XDV__` -> 参数 `XDV` 与任何现有参数不匹配。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:212 msgid "" @@ -3065,7 +3287,7 @@ msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:214 msgid "**Finish adding a printer**" -msgstr "" +msgstr "**完成添加打印机**" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:216 msgid "" @@ -3079,18 +3301,18 @@ msgstr "" msgid "" "After completing these steps, click :guilabel:`Add Printer`. If everything " "was done correctly, the page should redirect to the *Banners* page." -msgstr "" +msgstr "完成这些步骤后，单击 :guilabel:`添加打印机`。如果一切操作正确，页面应重定向到*横幅*页面。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:223 msgid "" "At this point the printer should have been created, now the :abbr:`IoT " "(Internet of Things)` box just needs to detect it and then sync to Odoo's " "server (this could take a few minutes)." -msgstr "" +msgstr "此时，打印机应该已经创建，现在，:abbr:`物联网（IoT）` 盒子只需检测到它，然后同步到 Odoo 服务器（这可能需要几分钟时间）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:226 msgid "**Adding the printer to Odoo PoS**" -msgstr "" +msgstr "**将打印机添加至 Odoo PoS**" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:228 msgid "" @@ -3099,6 +3321,8 @@ msgid "" "of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> " "Connected Devices --> IoT Box --> Receipt Printer --> Save`." msgstr "" +"一旦打印机在 Odoo 数据库中可见，不要忘记在 :abbr:`PoS （销售点）` 配置中将其选为 :abbr:`IoT（物联网）` 打印机。导航至 " +":menuselection:`POS 应用程序 --> 设置 --> 互联设备 --> 物联网盒子 --> 收据打印机 --> 保存`。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:234 msgid "" @@ -3107,10 +3331,12 @@ msgid "" " printer name with *CUPS*. Instead, the above process can be repeated to set" " up another printer from scratch to create one with modified parameters." msgstr "" +"如果打印机设置错误（仍在打印随机文本或打印的收据过大或过小），则不能通过打印机名称 *CUPS* " +"进行修改。相反，可以重复上述过程，从头开始设置另一台打印机，创建一台参数已修改的打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:239 msgid "**Example setup of the Epson TM-U220B printer using ESC**" -msgstr "" +msgstr "**使用 ESC 设置爱普生 TM-U220B 打印机**示例" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:244 msgid "" @@ -3119,27 +3345,28 @@ msgid "" "example of a receipt that is printing correctly due to proper formatting (in" " theory):" msgstr "" +"以下是使用 `ESC *` 命令对 TM-U220B 打印机型号进行故障排除的示例。下图中的收据是由于格式正确（理论上）而正确打印的收据示例：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Properly formatted receipt picture from a demo database." -msgstr "" +msgstr "演示数据库中格式正确的收据图片。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:252 msgid "" "Trying to print this receipt right-away prior to the proper formatting will " "not work as the TM-U220B printer model does not support `GS v 0`. Instead " "random characters will print:" -msgstr "" +msgstr "由于 TM-U220B 打印机型号不支持 `GS v 0`，因此在正确格式化之前立即打印该收据将不起作用。打印出来的将是随机字符：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Printer paper with seemingly random characters." -msgstr "" +msgstr "打印纸上的字符看似随机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:259 msgid "" "To properly configure formatting for the Epson TM-U220B printer model take " "the following steps." -msgstr "" +msgstr "要正确配置 Epson TM-U220B 打印机型号的格式化，请执行以下步骤。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:261 msgid "" @@ -3151,19 +3378,24 @@ msgid "" "indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with " "`ESC *`." msgstr "" +"在查阅了爱普生网站上有关这两种命令的兼容性：`GS v 0 <https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=94>`_ 和`ESC * " +"<https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_之后，可以看到 TM-U220B 确实与`GS" +" v 0` 不兼容，但与`ESC *` 兼容。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Epson compatibility evaluation from Epson website." -msgstr "" +msgstr "爱普生网站上的爱普生兼容性评估。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:270 msgid "" "When adding the printer, *CUPS* will ask which printer should be added:" -msgstr "" +msgstr "添加打印机时，*CUPS* 会询问应添加哪台打印机：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Administration menu, add printer selection." -msgstr "" +msgstr "管理菜单，添加打印机选项。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:276 msgid "" @@ -3176,6 +3408,10 @@ msgid "" "plugging it back in, the printer reappears, so it can be said that this is " "the printer in question." msgstr "" +"在这种情况下，打印机是通过 :abbr:`USB （通用串行总线）`连接的，因此不会出现在 :guilabel:`已发现的网络打印机` " +"中。相反，它可能是 :guilabel:`本地打印机` 下 :guilabel:`未知` 选项的一部分。将打印机的 :abbr:`USB " +"（通用串行总线）`电缆从 " +":guilabel:`IoT（物联网）`框中拔出并刷新页面，:guilabel:`未知`打印机就会消失。重新插入后，打印机将重新出现，因此可以确定这就是所讨论的打印机。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:283 msgid "" @@ -3185,10 +3421,14 @@ msgid "" "biz.com/modules/ref_escpos/index.php?content_id=88>`_ to find out more about" " the *density* parameters." msgstr "" +"关于命名规则，由于需要使用 `ESC *` 命令打印，因此必须添加 `__IMC`。请参考 `Epson's ESC * 网站 " +"<https://reference.epson-" +"biz.com/modules/ref_escpos/index.php?content_id=88>`_ 上的打印机型号，了解有关 *density*" +" 参数的更多信息。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Epson TM-U220 specifications on manufacturer's website." -msgstr "" +msgstr "制造商网站上的爱普生 TM-U220 规格。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:292 msgid "" @@ -3198,6 +3438,8 @@ msgid "" "the `m` value can NOT be 32 or 33 (otherwise there will be random characters" " printed)." msgstr "" +"对于 TM-U220 这种特定型号，`m` 应等于 0 或 1。参考上图中粉色方框下方的 :guilabel:`描述` 时，`m` 值可能是 " +"0、1、32 或 33。因此，在该打印机中，`m`值不能为 32 或 33（否则将打印出随机字符）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:297 msgid "" @@ -3207,17 +3449,19 @@ msgid "" "the *Low Vertical Density* will need to be forced, as this printer model " "does not support *High Vertical Density* for this command `ESC *`." msgstr "" +"表中包括数值： 32 和 33，如果 :guilabel:`垂直数据位数` 设置为 24，它们都会出现。这意味着*垂直密度高*。在配置 Epson " +"TM-U220 时，需要强制使用 *低垂直密度*，因为该打印机型号不支持该命令 `ESC *` 的 *高垂直密度*。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:302 msgid "" "To add a *Low Vertical Density*, add the `LDV` parameter to the naming " "convention." -msgstr "" +msgstr "要添加*低垂直密度*，请在命名规则中添加`LDV`参数。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "" "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." -msgstr "" +msgstr "在命名规则中添加*低垂直密度*（`LDV`参数）。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:308 msgid "" @@ -3228,7 +3472,7 @@ msgstr "" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Epson TM-U220 specifications on manufacturers website." -msgstr "" +msgstr "爱普生 TM-U220 的规格请参见制造商网站。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:315 msgid "" @@ -3237,6 +3481,9 @@ msgid "" " and outside the margin. To resolve this, add a new printer (and naming " "convention) with the `SCALE<X>` parameter to adapt to our receipt size." msgstr "" +"但是，当尝试使用命名规范：`EpsonTMU220B__IMC_LDV__` " +"打印时，虽然可以打印收据，但收据太大，超出了页边距。要解决这个问题，可以添加一个新的打印机（和命名规范），使用 `SCALE<X>` " +"参数来适应我们的收据尺寸。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:319 msgid "Here are some examples:" @@ -3244,49 +3491,49 @@ msgstr "示例如下：" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:324 msgid "Printer Naming Convention" -msgstr "" +msgstr "打印机命名规则" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:325 msgid "`EpsonTMU220B__IMC_LDV__`" -msgstr "" +msgstr "`EpsonTMU220B__IMC_LDV__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:326 msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" -msgstr "" +msgstr "`EpsonTMU220B__IMC_LDV_SCALE75__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:327 msgid "`EpsonTMU220B__IMC_LDV_LDH__`" -msgstr "" +msgstr "`EpsonTMU220B__IMC_LDV_LDH__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:328 msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" -msgstr "" +msgstr "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Receipt example format." -msgstr "" +msgstr "收据示例格式。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." -msgstr "" +msgstr "使用命名约定的收据格式：EpsonTMU220B__IMC_LDV__。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "" "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." -msgstr "" +msgstr "使用命名约定的收据格式： EpsonTMU220B__IMC_LDV_SCALE75__。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." -msgstr "" +msgstr "使用命名约定的收据格式： EpsonTMU220B__IMC_LDV_LDH__。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 msgid "" "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." -msgstr "" +msgstr "使用命名约定的收据格式：EpsonTMU220B__IMC_LDV_LDH_SCALE35__。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:346 msgid "The Zebra printer doesn't print anything" -msgstr "" +msgstr "Zebra 打印机不打印任何东西" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:348 msgid "" @@ -3297,6 +3544,9 @@ msgid "" " Interface --> Views` in :ref:`developer mode <developer-mode>` and look for" " the corresponding template." msgstr "" +"Zebra 打印机对打印的 Zebra " +"编程语言（ZPL）代码的格式非常敏感。如果打印机没有输出任何内容或打印了空白标签，请尝试通过在:ref:`开发者模式<developer-" +"mode>`中访问:menuselection:`设置 --> 技术 --> 用户界面 --> 视图`并查找相应的模板，更改发送到打印机的报表格式。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:355 msgid "" @@ -3304,6 +3554,9 @@ msgid "" "Language)` files `here <https://supportcommunity.zebra.com/s/article/Print-" "a-zpl-file-using-the-Generic-Text-Printer>`_." msgstr "" +"查看 Zebra 打印 :abbr:`ZPL（Zebra 编程语言）` 文件的说明，请点击 " +"<https://supportcommunity.zebra.com/s/article/Print-a-zpl-file-using-the-" +"Generic-Text-Printer>`_。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:362 msgid "The characters read by the barcode scanner don't match the barcode" @@ -3316,6 +3569,9 @@ msgid "" "device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select " "the correct format." msgstr "" +"默认情况下，大多数条形码扫描仪都配置为 US QWERTY " +"格式。如果条形码扫描仪使用不同的布局，请转到设备的窗体视图（:menuselection:`物联网应用程序 --> 设备 --> " +"条形码设备`）并选择正确的格式。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:369 msgid "Nothing happens when a barcode is scanned" @@ -3329,6 +3585,8 @@ msgid "" ":menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> " "Edit`." msgstr "" +"确保在 :menuselection:`POS` 配置中选择了正确的设备，并将条形码配置为在每个条形码末尾发送一个 `ENTER` 字符（关键码 " +"28）。为此，请导航至 :menuselection:`POS 应用程序 --> POS 上的三点菜单 --> 物联网盒子部分 --> 编辑`。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:377 msgid "The barcode scanner is detected as a keyboard" @@ -3339,7 +3597,7 @@ msgid "" "Some barcode scanners do not advertise themselves as barcode scanners but as" " a USB keyboard instead, and will not be recognized by the :abbr:`IoT " "(Internet of Things)` box." -msgstr "" +msgstr "有些条形码扫描仪不标明自己是条形码扫描仪，而是标明自己是 USB 键盘，因此不会被 :abbr:`IoT （物联网）` 盒子识别。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:383 msgid "" @@ -3347,14 +3605,16 @@ msgid "" "(:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the" " :guilabel:`Is scanner` option." msgstr "" +"设备类型可通过进入其表单视图（:menuselection:`物联网应用程序 --> 设备 --> 条码设备`）并激活 :guilabel:`是扫描仪`" +" 选项手动更改。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst-1 msgid "Modifying the form view of the barcode scanner." -msgstr "" +msgstr "修改条形码扫描仪的窗体视图。" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:394 msgid "The cash drawer does not open" -msgstr "" +msgstr "钱箱无法打开" #: ../../content/applications/productivity/iot/config/troubleshooting.rst:396 msgid "" @@ -3364,10 +3624,13 @@ msgid "" "on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer " "checkbox`." msgstr "" +"应将钱箱连接到打印机，并在:abbr:`POS（销售点）`配置中勾选 :guilabel:`钱箱`复选框。要执行此操作，请导航至 " +":menuselection:`POS 应用程序 --> POS 上的三点菜单 --> 物联网盒部分 --> 编辑 --> 收据打印机 --> " +"钱箱复选框`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:3 msgid "Connect Windows IoT Odoo" -msgstr "" +msgstr "连接 Windows 物联网 Odoo" #: ../../content/applications/productivity/iot/config/windows_iot.rst:5 msgid "" @@ -3375,6 +3638,7 @@ msgid "" "installed on a Windows computer. This requires a Windows operating system " "with an Odoo 16 or later database." msgstr "" +"虚拟物联网盒是一个需要下载并安装到 Windows 计算机上的计算机程序。这需要 Windows 操作系统和 Odoo 16 或更高版本的数据库。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:8 msgid "" @@ -3385,20 +3649,22 @@ msgid "" "should be noted that :abbr:`MRP (Material Requirement Planning)` devices are" " not compatible. *These include cameras or measurement tools.*" msgstr "" +"Windows 虚拟 :abbr:`IoT（物联网）`盒子的工作方式与实体 " +":abbr:`IoT（物联网）`盒子相同，能够运行大多数相同的设备。所有:abbr:`POS（销售点）`设备都能与之配合使用，例如秤或打印机。支付终端也可以使用，但需要注意的是，:abbr:`MRP（物料需求计划）`设备不兼容。*这些设备包括照相机或测量工具。*" #: ../../content/applications/productivity/iot/config/windows_iot.rst:15 msgid "Pre-requisites" -msgstr "" +msgstr "预先要求" #: ../../content/applications/productivity/iot/config/windows_iot.rst:17 msgid "" "The following items will be needed to complete the Windows :abbr:`IoT " "(Internet of Things)` installation." -msgstr "" +msgstr "完成 Windows :abbr:`IoT（物联网）`安装需要以下物品。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:20 msgid "Odoo 16 database or any version above." -msgstr "" +msgstr "Odoo 16 数据库或以上任何版本。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:21 msgid "" @@ -3406,10 +3672,12 @@ msgid "" "above). Refer to: `Odoo's compatible IoT devices " "<https://www.odoo.com/app/iot-hardware>`_." msgstr "" +":abbr:`IoT（物联网）`兼容设备（上述设备除外）。请参阅： Odoo " +"兼容的物联网设备<https://www.odoo.com/app/iot-hardware>`_。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:23 msgid "Device drivers for Windows." -msgstr "" +msgstr "Windows 设备驱动程序。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:26 msgid "" @@ -3417,31 +3685,33 @@ msgid "" "as some older operating systems can cause the Windows virtual :abbr:`IoT " "(Internet of Things)` to not work." msgstr "" +"Odoo 建议使用最新版本的 Windows（Windows 10/11），因为某些较旧的操作系统可能导致 Windows " +"虚拟:abbr:`物联网`无法运行。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:29 msgid "Windows computer (laptop, desktop, or server)." -msgstr "" +msgstr "Windows 计算机（笔记本电脑、台式电脑或服务器）。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:30 msgid "" "Odoo :abbr:`IoT (Internet of Things)` subscription. Refer to: :ref:`iot/iot-" "eligibility`." -msgstr "" +msgstr "Odoo :abbr:`IoT（物联网）`订阅。请参阅： :ref:`iot/iot-eligibility`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:33 msgid "Connect the Windows virtual Iot box to an Odoo database" -msgstr "" +msgstr "将 Windows 虚拟物联网盒子连接到 Odoo 数据库" #: ../../content/applications/productivity/iot/config/windows_iot.rst:35 msgid "" "The Windows virtual IoT box is simple to setup in just a few easy steps. " "Follow this process when installing the Windows virtual IoT software for the" " first time." -msgstr "" +msgstr "Windows 虚拟物联网盒子的设置非常简单，只需几步即可完成。首次安装 Windows 虚拟物联网软件时，请遵循以下流程。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:39 msgid "Download and initial installation" -msgstr "" +msgstr "下载和首次安装" #: ../../content/applications/productivity/iot/config/windows_iot.rst:41 msgid "" @@ -3451,67 +3721,70 @@ msgid "" ":file:`.exe` file. After the instructions screen, click :guilabel:`Next` to " "start the installation and agree to the :abbr:`TOS (Terms of Service)`." msgstr "" +"要开始安装，请在 `Odoo 的下载页面 <https://odoo.com/download>`_浏览 Odoo 16 或更高版本的企业或社区 - " +"Windows 版安装包。接下来，安装并设置 Odoo :file:`.exe` 文件。在出现说明屏幕后，点击 :guilabel:`下一步` " +"开始安装，并同意 :abbr:`TOS（服务条款）`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:46 msgid "" "During the next step of the installation, select :guilabel:`Odoo IoT` from " "the :guilabel:`Select the type of install` dropdown." -msgstr "" +msgstr "在下一步安装过程中，从 :guilabel:`选择安装类型` 下拉菜单中选择 :guilabel:`Odoo IoT`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:50 msgid "For reference, the following should be installed:" -msgstr "" +msgstr "便于参考，应安装以下设备：" #: ../../content/applications/productivity/iot/config/windows_iot.rst:52 msgid "**Odoo server**" -msgstr "" +msgstr "**Odoo 服务器**" #: ../../content/applications/productivity/iot/config/windows_iot.rst:53 msgid "**Odoo IoT**" -msgstr "" +msgstr "**Odoo IoT**" #: ../../content/applications/productivity/iot/config/windows_iot.rst:54 msgid "**Nginx WebServer**" -msgstr "" +msgstr "**Nginx WebServer**" #: ../../content/applications/productivity/iot/config/windows_iot.rst:55 msgid "**Ghostscript interpreter**" -msgstr "" +msgstr "**Ghostscript interpreter**" #: ../../content/applications/productivity/iot/config/windows_iot.rst:57 msgid "" "Ensure there is enough space on the computer for the installation and click " ":guilabel:`Next`." -msgstr "" +msgstr "确保计算机上有足够的安装空间，然后单击 :guilabel:`下一步`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:60 msgid "Setting the destination and completing the installation" -msgstr "" +msgstr "设置目的地并完成安装" #: ../../content/applications/productivity/iot/config/windows_iot.rst:62 msgid "" "To complete the installation, select the :guilabel:`Destination Folder` and " "click :guilabel:`Install`." -msgstr "" +msgstr "要完成安装，请选择 :guilabel:`目的地文件夹` 并单击 :guilabel:`安装`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:66 msgid "" "Choosing ``C:\\odoo`` as the install location will allow for the Nginx " "server to start. If the folder doesn't exist, then create it. Otherwise the " "installation files will be spread throughout the hard drive." -msgstr "" +msgstr "选择 ``C:\\odoo`` 作为安装位置将允许 Nginx 服务器启动。如果文件夹不存在，则创建它。否则，安装文件将遍布整个硬盘。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:71 msgid "" "Odoo's Windows virtual IoT software shouldn't be installed inside any of the" " Window's User's directories. Doing so won't allow for Nginx to initialize." -msgstr "" +msgstr "Odoo 的 Windows 虚拟物联网软件不应安装在任何 Window用户目录内。这样做会导致 Nginx 无法初始化。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:74 msgid "" "The installation may take a few minutes. When complete, click " ":guilabel:`Next` to continue." -msgstr "" +msgstr "安装可能需要几分钟时间。完成后，单击 :guilabel:`下一步` 继续。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:76 msgid "" @@ -3520,16 +3793,18 @@ msgid "" "automatically open `http://localhost:8069` on your web browser. The webpage " "should display the :abbr:`IoT (Internet of Things)` box homepage." msgstr "" +"确保选中 :guilabel:`开始 Odoo` 框，然后单击 :guilabel:`完成`。安装完成后，Odoo 服务器将运行并自动在网页浏览器上打开" +" `http://localhost:8069`。网页应显示 :abbr:`IoT（物联网）` 盒子主页。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:81 msgid "" "A restart of the Windows IoT program may be necessary should the web browser" " not display anything. :ref:`iot/restart_windows_iot`" -msgstr "" +msgstr "如果网络浏览器无法显示任何内容，可能需要重新启动 Windows IoT 程序。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:85 msgid "Connecting devices" -msgstr "" +msgstr "连接设备" #: ../../content/applications/productivity/iot/config/windows_iot.rst:87 msgid "" @@ -3538,6 +3813,8 @@ msgid "" "is pre-installed on the computer. If not, search for and install the Windows" " driver for the device." msgstr "" +"接下来，将 :abbr:`IoT物联网`设备连接到 Windows 计算机。Windows " +"应该会自动检测到设备，因为驱动程序已预先安装在电脑上。如果没有，请搜索并安装设备的 Windows 驱动程序。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:91 msgid "" @@ -3546,22 +3823,24 @@ msgid "" "reload the handlers through the :abbr:`IoT (Internet of Things)` box " "homepage." msgstr "" +"将设备连接到计算机后，刷新 :abbr:`IoT（物联网）`盒子主页并验证是否能看到设备。如果没有，请通过 :abbr:`IoT " +"（物联网）`盒子主页重新加载处理程序。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:95 msgid "" "Finally, connect Windows :abbr:`IoT (Internet of Things)` to a database " "using existing instructions (manually using the Token)." -msgstr "" +msgstr "最后，使用现有说明（手动使用令牌）将 Windows :`IoT（物联网）` 连接到数据库。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:101 msgid "" "Now the installation is complete, the devices connected to :abbr:`IoT " "(Internet of Things)` can be used to complete processes/actions." -msgstr "" +msgstr "现在安装已经完成，连接到 :abbr:`IoT （物联网）` 的设备可以用来完成流程/操作。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:110 msgid "Restart Windows IoT box" -msgstr "" +msgstr "重启 Windows 物联网盒子" #: ../../content/applications/productivity/iot/config/windows_iot.rst:112 msgid "" @@ -3571,30 +3850,34 @@ msgid "" "(Internet of Things)` box a manual restart of the Odoo server can resolve " "database connection issues." msgstr "" +"在某些情况下，手动重启物理 :abbr:`IoT（物联网）` 盒子可以解决数据库中未显示 :abbr:`IoT（物联网）` 盒子的问题。对于 " +"Windows 虚拟 :abbr:`IoT（物联网）` 盒子，手动重启 Odoo 服务器可解决数据库连接问题。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:117 msgid "To restart the virtual Windows IoT server:" -msgstr "" +msgstr "重新启动虚拟 Windows IoT 服务器：" #: ../../content/applications/productivity/iot/config/windows_iot.rst:119 msgid "Type `Services` into the Windows :guilabel:`Search Bar`." -msgstr "" +msgstr "在 Windows :guilabel:`搜索栏`中键入`服务`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:120 msgid "" "Select the :menuselection:`Services` App and scroll down to the " ":guilabel:`Odoo` service." -msgstr "" +msgstr "选择 :menuselection:`服务` 应用程序并向下滚动到 :guilabel:`Odoo` 服务。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:121 msgid "" "Right click on :guilabel:`Odoo` and select :guilabel:`Start` or " ":guilabel:`Restart`. This action will manually restart the Odoo IoT server." msgstr "" +"右键单击 :guilabel:`Odoo` 并选择 :guilabel:`开始` 或 :guilabel:`重启`。此操作将手动重启 Odoo " +"物联网服务器。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:125 msgid "Firewalls" -msgstr "" +msgstr "防火墙" #: ../../content/applications/productivity/iot/config/windows_iot.rst:127 msgid "" @@ -3606,6 +3889,9 @@ msgid "" "(Operating System)` or firewall program. Windows has their own firewall as " "do other virus protection programs." msgstr "" +"防火墙可确保设备安全。但有时它们会阻止本应进行的连接。由于防火墙阻止了连接，Windows 虚拟 :abbr:`IoT " +"（物联网）`盒子软件可能无法连接到 :abbr:`LAN（局域网）`。请咨询当地的 IT 支持团队，在 :abbr:`OS （操作系统）` " +"或防火墙程序中设置例外（网络发现）。Windows 和其他病毒防护程序都自带防火墙。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:134 msgid "" @@ -3613,10 +3899,11 @@ msgid "" "the :abbr:`IoT (Internet of Things)` box, yet they cannot access it from " "another computer/mobile device/tablet on the same network." msgstr "" +"客户可能会遇到这样的情况：他们能够访问 :abbr:`IoT（物联网）` 盒子的主页，但却无法从同一网络上的另一台计算机/移动设备/平板电脑访问该主页。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:139 msgid "Making an exception on Windows Defender" -msgstr "" +msgstr "在 Windows Defender 上设置例外" #: ../../content/applications/productivity/iot/config/windows_iot.rst:141 msgid "" @@ -3626,10 +3913,12 @@ msgid "" "through port `8069`. The following process describes the steps to take in " "order to make this exception." msgstr "" +"可以允许其他设备访问 Windows 虚拟 :abbr:`IoT （物联网）` 盒子，同时保持防火墙开启。方法是在 *Windows Defender*" +" 上创建一条规则，允许通过端口 `8069` 进行通信。以下过程描述了设置此例外的步骤。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:147 msgid "Create a rule in Windows Defender" -msgstr "" +msgstr "在 Windows Defender 中创建规则" #: ../../content/applications/productivity/iot/config/windows_iot.rst:149 msgid "" @@ -3638,6 +3927,8 @@ msgid "" ":menuselection:`Windows Defender Firewall` program. In the left-hand menu, " "navigate to :guilabel:`Advanced Settings`." msgstr "" +"首先，通过导航至 :menuselection:`开始菜单`并输入`防火墙`打开*Windows 防火墙*。然后，打开 " +":menuselection:`Windows Defender 防火墙` 程序。在左侧菜单中，导航至 :guilabel:`高级设置`。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:153 msgid "" @@ -3649,7 +3940,7 @@ msgstr "" #: ../../content/applications/productivity/iot/config/windows_iot.rst:158 msgid "Configure new rule" -msgstr "" +msgstr "配置新规则" #: ../../content/applications/productivity/iot/config/windows_iot.rst:160 msgid "" @@ -3660,6 +3951,9 @@ msgid "" "text box, type in `8069`. Finally click :guilabel:`Next` to continue to the " "next step." msgstr "" +"在 :menuselection:`规则类型` 屏幕上，选择 :guilabel:`端口`。然后单击 :guilabel:`下一步`。在 " +":menuselection:`协议和端口` 页面，将规则应用程序保留为 :guilabel:`TCP`。然后，在 :guilabel:`端口` " +"选项中选择 :guilabel:`特定本地端口`。在文本框中键入 `8069`。最后单击 :guilabel:`下一步` 继续。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:165 msgid "" @@ -3672,6 +3966,10 @@ msgid "" "while allowing the selected port to communicate. Click :guilabel:`Next` to " "continue." msgstr "" +"在 :menuselection:`操作` 页面，选择 :guilabel:`允许连接` 并单击 " +":guilabel:`下一步`。:menuselection:`规则配置`向导的下一页是 :guilabel:`配置文件` 页面。在此页面中，选择适用于" +" Windows 机器所运行网络的连接类型。理想情况下，只选择 :guilabel:`私有` 连接。*私有* " +"连接类型是最安全的连接，同时允许所选端口进行通信。单击 :guilabel:`下一步` 继续。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:172 msgid "" @@ -3682,10 +3980,13 @@ msgid "" "devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` " "box." msgstr "" +"最后，为规则指定一个新的唯一名称。例如，名称可以是 `Odoo`。可选择在 :guilabel:`描述` 字段中添加简要说明。单击 " +":guilabel:`完成`，结束:guilabel:`规则配置` 向导。现在，新规则已激活，设备可以连接到 Windows " +"虚拟:abbr:`IoT（物联网）` 盒子。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:178 msgid "Uninstalling Windows IoT" -msgstr "" +msgstr "卸载 Windows 物联网盒子" #: ../../content/applications/productivity/iot/config/windows_iot.rst:180 msgid "" @@ -3695,12 +3996,14 @@ msgid "" "the control panel. Search for `Odoo` and click the :guilabel:`three dot " "menu` to uninstall." msgstr "" +"卸载 Windows 虚拟:abbr:`IoT（物联网）` 盒子可通过 Windows 程序管理器完成。使用任何 Windows 版本，搜索 " +"`程序`。然后，选择控制面板中的 :guilabel:`添加或删除程序`。搜索 `Odoo `并点击:guilabel: `三点菜单` 进行卸载。" #: ../../content/applications/productivity/iot/config/windows_iot.rst:185 msgid "" "Confirm the un-installation and follow the steps to uninstall through the " "Odoo uninstall guide." -msgstr "" +msgstr "确认卸载，并按照 Odoo 卸载指南中的步骤进行卸载。" #: ../../content/applications/productivity/iot/devices.rst:5 msgid "Devices" @@ -3708,7 +4011,7 @@ msgstr "设备" #: ../../content/applications/productivity/iot/devices/camera.rst:3 msgid "Connect a camera" -msgstr "" +msgstr "连接相机" #: ../../content/applications/productivity/iot/devices/camera.rst:5 msgid "" @@ -3720,6 +4023,8 @@ msgid "" "point/check has been reached, or when a specific key is pressed during " "manufacturing." msgstr "" +"只需几个步骤，就可将相机连接到带有 Odoo 数据库的 :abbr:`IoT（物联网）` 盒子。相机连接到 " +":abbr:`IoT（物联网）`盒子后，可用于生产过程，也可连接到质量控制点/质量检查。这样，当达到选定的质量控制点/检查点时，或者在制造过程中按下特定按键时，就可以拍摄照片。" #: ../../content/applications/productivity/iot/devices/camera.rst:12 #: ../../content/applications/productivity/iot/devices/footswitch.rst:14 @@ -3735,6 +4040,7 @@ msgid "" "connect the two via cable. This is usually done with a :abbr:`USB (Universal" " Serial Bus)` cable of some sort." msgstr "" +"要将相机连接到 :abbr:`IoT （物联网）`盒子，只需通过电缆将两者连接起来。通常使用某种 :abbr:`USB（通用串行总线）`电缆来实现。" #: ../../content/applications/productivity/iot/devices/camera.rst:17 msgid "" @@ -3742,14 +4048,16 @@ msgid "" "there is no need to set up anything, as it'll be detected as soon as it's " "connected." msgstr "" +"如果您的相机在 `*支持的设备* <https://www.odoo.com/page/iot-" +"hardware>`_中，则无需进行任何设置，因为一旦连接就会自动检测到。" #: ../../content/applications/productivity/iot/devices/camera.rst-1 msgid "Camera recognized on the IoT box." -msgstr "" +msgstr "识别物联网盒子上的摄像头。" #: ../../content/applications/productivity/iot/devices/camera.rst:25 msgid "Link camera to quality control point in manufacturing process" -msgstr "" +msgstr "将相机与制造过程中的质量控制点连接起来" #: ../../content/applications/productivity/iot/devices/camera.rst:27 msgid "" @@ -3758,6 +4066,8 @@ msgid "" ":menuselection:`Quality app --> Quality Control --> Control Points` and open" " the desired :guilabel:`Control Point` that'll be linked to the camera." msgstr "" +"在 :menuselection:`品控应用程序` 中，可在 :guilabel:`质量控制点` 上设置设备。请导航到 " +":menuselection:`品控应用程序 --> 质量控制 --> 控制点`，然后打开要链接到摄像机的 :guilabel:`控制点`。" #: ../../content/applications/productivity/iot/devices/camera.rst:31 msgid "" @@ -3770,7 +4080,7 @@ msgstr "" #: ../../content/applications/productivity/iot/devices/camera.rst-1 msgid "Setting up the device on the quality control point." -msgstr "" +msgstr "在质量控制点安装设备。" #: ../../content/applications/productivity/iot/devices/camera.rst:40 msgid "" @@ -3790,6 +4100,8 @@ msgid "" " a :guilabel:`Quality Control Points` tab, where they can be added with the " "device." msgstr "" +"还可以通过导航至 :menuselection:`物联网应用程序 --> 设备` " +"访问质量控制点。在此选择设备。有一个:guilabel:`质量控制点`选项卡，可以在其中添加设备。" #: ../../content/applications/productivity/iot/devices/camera.rst:53 msgid "" @@ -3798,22 +4110,27 @@ msgid "" "Quality Control --> Quality Checks --> New` to create a new quality check " "from the :guilabel:`Quality Checks` page." msgstr "" +"在质量检查表单中，检查的 :guilabel:`Type` 类型也可指定为 :guilabel:`拍照`。导航至 " +":menuselection:`品控应用程序 --> 质量控制 --> 质量检查 --> 新建`，从 :guilabel:`质量检查` " +"页面创建新的质量检查。" #: ../../content/applications/productivity/iot/devices/camera.rst:58 #: ../../content/applications/productivity/iot/devices/printer.rst:70 msgid "" ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" #: ../../content/applications/productivity/iot/devices/camera.rst:59 #: ../../content/applications/productivity/iot/devices/printer.rst:71 msgid "" ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" +":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" #: ../../content/applications/productivity/iot/devices/camera.rst:62 msgid "Link camera to a work center in the Manufacturing app" -msgstr "" +msgstr "在制造应用中将相机连接到工作中心" #: ../../content/applications/productivity/iot/devices/camera.rst:64 msgid "" @@ -3824,13 +4141,16 @@ msgid "" "here, add the device in the :guilabel:`IoT Triggers` tab, in the " ":guilabel:`Device` column, by clicking :guilabel:`Add a Line`." msgstr "" +"要将相机连接到操作，首先需要在工作中心上进行配置。导航至 :menuselection:`制造应用程序 --> 配置 --> " +"工作中心`。然后，转到所需的 :guilabel:`工作中心`，该工作中心将使用相机来显示特定工作中心的详细表单。在此，点击 " +":guilabel:`添加行`，在 :guilabel:`联网触发器` 选项卡的 :guilabel:`设备` 列中添加设备。" #: ../../content/applications/productivity/iot/devices/camera.rst:70 msgid "" "Now, the camera device can be linked to the :guilabel:`Action` column drop-" "down option labeled :guilabel:`Take a Picture`. A key can also be added to " "trigger the action." -msgstr "" +msgstr "现在，相机设备可以连接到 :guilabel:`操作` 列中标有 :guilabel:`拍照` 的下拉选项。还可以添加一个键来触发该操作。" #: ../../content/applications/productivity/iot/devices/camera.rst:74 msgid "" @@ -3849,7 +4169,7 @@ msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92 #: ../../content/applications/productivity/iot/devices/printer.rst:95 msgid ":ref:`workcenter_iot`" -msgstr "" +msgstr ":ref:`workcenter_iot`" #: ../../content/applications/productivity/iot/devices/footswitch.rst:3 msgid "Connect a footswitch" @@ -3939,11 +4259,11 @@ msgstr "" msgid "" "Find the list of supported devices here: `Supported devices " "<https://www.odoo.com/page/iot-hardware>`_." -msgstr "" +msgstr "在此查找支持的设备列表：`支持的设备 <https://www.odoo.com/page/iot-hardware>`_。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 msgid "Connect with universal serial bus (USB)" -msgstr "" +msgstr "与通用串行总线（USB）连接" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17 msgid "" @@ -3954,22 +4274,22 @@ msgstr "" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 msgid "Measurement tool recognized on the IoT box." -msgstr "" +msgstr "物联网盒子上识别的测量工具。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 msgid "Connect with bluetooth" -msgstr "" +msgstr "蓝牙连接" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28 msgid "" "Activate the Bluetooth functionality on the device (see the device manual " "for further explanation), and the :abbr:`IoT (Internet of Things)` box " "automatically connects to the device." -msgstr "" +msgstr "激活设备上的蓝牙功能（详见设备手册），:abbr:`IoT（物联网）`盒子就会自动连接到设备。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 msgid "Bluetooth indicator on measurement tool." -msgstr "" +msgstr "测量工具上的蓝牙指示器。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 msgid "" @@ -3984,6 +4304,8 @@ msgid "" "Control Points`, and open the desired control point to which the measurement" " tool should be linked." msgstr "" +"在*品控应用程序*中，可在质量控制点上设置设备。要执行此操作，请导航至 " +":menuselection:`品控应用程序-->质量控制-->控制点`，然后打开所需的控制点，并将测量工具链接到该控制点。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43 msgid "" @@ -3991,6 +4313,8 @@ msgid "" "and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a" " field called :guilabel:`Device`, where the attached device can be selected." msgstr "" +"在这里，选择 :guilabel:`类型` 字段，然后点击下拉菜单中的 :guilabel:`测量`，编辑控制点。这样就会出现一个名为 " +":guilabel:`设备` 的字段，可在此选择连接的设备。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 msgid "" @@ -4003,7 +4327,7 @@ msgid "" "At this point, the measurement tool is linked to the chosen quality control " "point. The value, which usually needs to be changed manually, is " "automatically updated while the tool is being used." -msgstr "" +msgstr "此时，测量工具与所选的质量控制点相连。通常需要手动更改的数值会在工具使用过程中自动更新。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst-1 msgid "Measurement tool input in the Odoo database." @@ -4017,6 +4341,8 @@ msgid "" ":guilabel:`Quality Control Points` tab, where they can be added with the " "device." msgstr "" +"质量控制点也可通过导航至 :menuselection:`物联网应用程序 --> 设备` 访问，然后选择设备。有一个 :guilabel:`质量控制点`" +" 选项卡，可以在其中添加设备。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63 msgid "" @@ -4025,20 +4351,24 @@ msgid "" " navigating to :menuselection:`Quality app --> Quality Control --> Quality " "Checks --> New`." msgstr "" +"在质量检查详细表格中，检查的 :guilabel:`类型` 也可指定为 :guilabel:`测量`。通过导航至 " +":menuselection:`品控应用程序 --> 质量控制 --> 质量检查 --> 新的` 访问新的质量检查详情页。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68 msgid "" ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69 msgid "" ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" +":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 msgid "Link a measurement tool to a work center in the Manufacturing app" -msgstr "" +msgstr "将测量工具链接到制造应用中的工作中心" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74 msgid "" @@ -4047,6 +4377,8 @@ msgid "" " Configuration --> Work Centers`. Then, select the desired work center in " "which the measurement tool will be used." msgstr "" +"要将测量工具链接到操作，首先需要在工作中心配置该工具。要执行此操作，请导航至 :menuselection:`制造应用程序 --> 配置 --> " +"工作中心`。然后，选择需要使用测量工具的工作中心。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78 msgid "" @@ -4056,22 +4388,24 @@ msgid "" " menu option labeled :guilabel:`Take Measure`. A key can be added to trigger" " the action." msgstr "" +"在工作中心页面的 :guilabel:`物联网触发器` 选项卡的 :guilabel:`设备` 栏下，通过选择 :guilabel:`添加行` " +"添加设备。然后，可将测量工具链接到标有 :guilabel:`操作` 的 :guilabel:`测量` 下拉菜单选项。可以添加一个键来触发该操作。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84 msgid "" "It should be noted that the first listed trigger is chosen first. The order " "matters, and these triggers can be dragged into any order." -msgstr "" +msgstr "需要注意的是，先选择第一个列出的触发器。顺序很重要，这些触发器可以按任意顺序拖动。" #: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88 msgid "" "On the :guilabel:`Work Order` screen, a status graphic indicates whether the" " database is correctly connected to the measurement tool." -msgstr "" +msgstr "在 :guilabel:`工单` 屏幕上，状态图形显示数据库是否与测量工具正确连接。" #: ../../content/applications/productivity/iot/devices/printer.rst:3 msgid "Connect a printer" -msgstr "" +msgstr "连接打印机" #: ../../content/applications/productivity/iot/devices/printer.rst:5 msgid "" @@ -4081,6 +4415,8 @@ msgid "" "trigger* during the manufacturing process, or added onto a quality control " "point or a quality check." msgstr "" +"安装打印机只需几个简单的步骤即可完成。打印机可用于打印收据、标签、订单，甚至不同 Odoo " +"应用程序中的报告。此外，在生产过程中，还可将打印机操作指定为*触发器上的操作*，或添加到质量控制点或质量检查中。" #: ../../content/applications/productivity/iot/devices/printer.rst:13 msgid "" @@ -4089,6 +4425,9 @@ msgid "" "`Supported printers <https://www.odoo.com/page/iot-hardware>`__ are detected" " automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." msgstr "" +"物联网盒子支持通过 :abbr:`USB （通用串行总线）`、网络连接或蓝牙连接的打印机。支持的打印机 " +"<https://www.odoo.com/page/iot-hardware>`__ 会被自动检测，并显示在 *物联网应用程序*的 " +":guilabel:`设备`列表中。" #: ../../content/applications/productivity/iot/devices/printer.rst-1 msgid "The printer as it would appear in the IoT app devices list." @@ -4098,21 +4437,21 @@ msgstr "" msgid "" "The printer can take up to two minutes to appear in the *IoT app* devices " "list." -msgstr "" +msgstr "打印机可能需要两分钟才能出现在 *物联网应用程序* 设备列表中。" #: ../../content/applications/productivity/iot/devices/printer.rst:26 msgid "Link printer" -msgstr "" +msgstr "连接打印机" #: ../../content/applications/productivity/iot/devices/printer.rst:29 msgid "Link printer to work orders" -msgstr "" +msgstr "连接打印机与工单" #: ../../content/applications/productivity/iot/devices/printer.rst:31 msgid "" "*Work Orders* can be linked to printers, via a quality control point, to " "print labels for manufactured products." -msgstr "" +msgstr "*工单*可通过质量控制点与打印机连接，为制成品打印标签。" #: ../../content/applications/productivity/iot/devices/printer.rst:34 msgid "" @@ -4121,6 +4460,8 @@ msgid "" "Control Points`, and open the desired control point to which the printer " "will be linked." msgstr "" +"在*质量应用程序*中，可以在质量控制点上设置设备。要执行此操作，请转到 :menuselection:`品控应用程序 --> 质量控制 --> " +"控制点`，然后打开所需的控制点，将打印机链接到该控制点。" #: ../../content/applications/productivity/iot/devices/printer.rst:39 msgid "" @@ -4128,6 +4469,7 @@ msgid "" "to a quality control point before the :guilabel:`Type` field allows for the " ":guilabel:`Print Label` option to be selected." msgstr "" +"在 :guilabel:`类型` 字段允许选择 :guilabel:`打印标签` 选项之前，需要将 *制造操作* 和 *工单操作* 附加到质量控制点。" #: ../../content/applications/productivity/iot/devices/printer.rst:43 msgid "" @@ -4136,17 +4478,19 @@ msgid "" "Doing so reveals a field called :guilabel:`Device`, where the attached " "*device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" +"在这里，选择 :guilabel:`类型` 字段，并从选项下拉菜单中选择 :guilabel:`打印标签` " +"来编辑控制点。如果需要，请:guilabel:`保存`更改。" #: ../../content/applications/productivity/iot/devices/printer.rst-1 msgid "This is the quality control point setup." -msgstr "" +msgstr "这就是质量控制点的设置。" #: ../../content/applications/productivity/iot/devices/printer.rst:52 msgid "" "The printer can now be used with the selected quality control point. When " "the quality control point is reached during the manufacturing process, the " "database presents the option to print labels for a specific product." -msgstr "" +msgstr "现在，打印机可用于选定的质量控制点。在生产过程中达到质量控制点时，数据库会显示为特定产品打印标签的选项。" #: ../../content/applications/productivity/iot/devices/printer.rst:65 msgid "" @@ -4155,10 +4499,12 @@ msgid "" " to :menuselection:`Quality app --> Quality Control --> Quality Checks --> " "New`." msgstr "" +"在质量检查明细表单中，检查的 :guilabel:`类型` 也可指定为 :guilabel:`打印标签`。要创建新的质量检查，请导航至 " +":menuselection:`品控应用程序 --> 质量控制 --> 质量检查 --> 新的`。" #: ../../content/applications/productivity/iot/devices/printer.rst:74 msgid "Link a printer to a work center in the Manufacturing app" -msgstr "" +msgstr "在制造应用程序中将打印机连接到工作中心" #: ../../content/applications/productivity/iot/devices/printer.rst:76 msgid "" @@ -4169,6 +4515,9 @@ msgid "" ":guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by " "selecting :guilabel:`Add a Line`." msgstr "" +"要将打印机与操作连接，首先需要在工作中心配置打印机。请导航至 :menuselection:`制造应用程序 --> 配置 --> " +"工作中心`。在此选择需要使用打印机的工作中心。然后，在 :guilabel:`物联网触发器` 选项卡的 :guilabel:`设备` 列下，通过选择 " +":guilabel:`添加行` 添加设备。" #: ../../content/applications/productivity/iot/devices/printer.rst:82 msgid "" @@ -4177,29 +4526,31 @@ msgid "" ":guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can " "also be added to trigger the action." msgstr "" +"然后，打印机可链接到 :guilabel:`操作` 下拉菜单中的以下任一选项：:guilabel:`打印标签`、:guilabel:`打印操作` 或 " +":guilabel:`打印交货单`。还可以添加一个键来触发操作。" #: ../../content/applications/productivity/iot/devices/printer.rst:87 msgid "" "The first listed trigger on the form will be chosen first. So, the order " "matters, and these triggers can be dragged into any order." -msgstr "" +msgstr "表单中最先列出的触发器将被优先选择。因此，顺序很重要，这些触发器可以按任意顺序拖动。" #: ../../content/applications/productivity/iot/devices/printer.rst:91 msgid "" "On the :guilabel:`Work Order` screen, a status graphic indicates whether the" " database is correctly connected to the printer." -msgstr "" +msgstr "在 :guilabel:`工单` 屏幕上，状态图形显示数据库是否正确连接到打印机。" #: ../../content/applications/productivity/iot/devices/printer.rst:98 msgid "Link printer to reports" -msgstr "" +msgstr "连接打印机与报告" #: ../../content/applications/productivity/iot/devices/printer.rst:100 msgid "" "It's also possible to link a type of report to a certain printer. In the " "*IoT app*, go to the :guilabel:`Devices` menu, and select the desired " "printer that needs to be configured." -msgstr "" +msgstr "还可以将某一类型的报告连接到特定的打印机。在*物联网应用程序*中，进入 :guilabel:`设备`菜单，选择需要配置的打印机。" #: ../../content/applications/productivity/iot/devices/printer.rst:103 msgid "" @@ -4207,23 +4558,26 @@ msgid "" "tab, and select :guilabel:`Add a line`. In the window that appears, check " "all the types of :guilabel:`Reports` that should be linked to this printer." msgstr "" +"从此处单击 :guilabel:`编辑`，转到 :guilabel:`打印机报告`选项卡，然后选择 " +":guilabel:`添加行`。在出现的窗口中，选中应连接到此打印机的所有 :guilabel:`报告` 类型。" #: ../../content/applications/productivity/iot/devices/printer.rst-1 msgid "The printer devices listed in the IoT Devices menu." -msgstr "" +msgstr "物联网设备菜单中列出的打印机设备。" #: ../../content/applications/productivity/iot/devices/printer.rst:111 msgid "" "Now, each time :guilabel:`Print` is selected in the control panel, instead " "of downloading a PDF, Odoo sends the report to the selected printer, and " "automatically prints it." -msgstr "" +msgstr "现在，每次在控制面板中选择 :guilabel:`打印` 时，Odoo 不会下载 PDF 文件，而是将报告发送到选定的打印机，并自动打印。" #: ../../content/applications/productivity/iot/devices/printer.rst:115 msgid "" ":doc:`POS Order Printing " "<../../../sales/point_of_sale/restaurant/kitchen_printing>`" msgstr "" +":doc:`POS 订单打印 <../../../sales/point_of_sale/restaurant/kitchen_printing>`" #: ../../content/applications/productivity/iot/devices/printer.rst:118 msgid "" @@ -4233,10 +4587,13 @@ msgid "" "From here, the individual report can be found in this list, where the " ":guilabel:`IoT Device` can be set on the report." msgstr "" +"在 :ref:`调试模式<developer-mode>` 时，也可以在 :guilabel:`技术菜单` 中配置报告。要执行此操作，请导航至 " +":menuselection:`设置应用程序 --> 技术菜单 --> 操作 --> 报告`。在这里，可以在此列表中找到单个报告，并在报告上设置 " +":guilabel:`物联网设备`。" #: ../../content/applications/productivity/iot/devices/scale.rst:3 msgid "Connect a scale" -msgstr "" +msgstr "连接电子秤" #: ../../content/applications/productivity/iot/devices/scale.rst:5 msgid "" @@ -4245,6 +4602,8 @@ msgid "" "be used to weigh products, which is helpful if their prices are calculated " "based on weight." msgstr "" +"只需几个简单的步骤，就可将电子秤连接到 Odoo " +"数据库上的:abbr:`物联网`盒子。设置完成后，*销售点*应用程序可用于对产品进行称重，这对根据重量计算价格的产品很有帮助。" #: ../../content/applications/productivity/iot/devices/scale.rst:12 msgid "" @@ -4265,6 +4624,8 @@ msgid "" "anything because it will be automatically detected as soon as it is " "connected." msgstr "" +"如果电子秤`兼容 Odoo 物联网盒子 <https://www.odoo.com/page/iot-" +"hardware>`_，则无需进行任何设置，因为电子秤一经连接就会自动检测到。" #: ../../content/applications/productivity/iot/devices/scale.rst-1 msgid "IOT box auto detection." @@ -4278,6 +4639,8 @@ msgid "" "and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load " "Drivers`." msgstr "" +"在某些情况下，可能需要重新启动 :abbr:`IoT（物联网）` 盒子，并将电子秤的驱动程序下载到盒子中。要更新驱动程序，请访问 :abbr:`IoT " +"（物联网）` 盒子主页并点击 :guilabel:`驱动程序列表`。然后，点击 :guilabel:`加载驱动程序`。" #: ../../content/applications/productivity/iot/devices/scale.rst-1 msgid "View of the IoT box settings and driver list." @@ -4289,10 +4652,11 @@ msgid "" " be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of " "Things)` box. In this case, a different scale will need to be used." msgstr "" +"如果加载驱动程序后仍无法使用电子秤，则可能是电子秤与 Odoo :abbr:`IoT（物联网）盒子不兼容。在这种情况下，需要使用其他电子秤。" #: ../../content/applications/productivity/iot/devices/scale.rst:39 msgid "Use a scale in a point of sale (POS) system" -msgstr "" +msgstr "在销售点（POS）系统中使用电子秤" #: ../../content/applications/productivity/iot/devices/scale.rst:41 msgid "" @@ -4301,12 +4665,14 @@ msgid "" "(Internet of Things)` box feature. After this is complete, the scale device " "can be set." msgstr "" +"要在*销售点应用程序*中使用电子秤，请访问 :menuselection:`销售点应用程序 --> PoS 上的三点菜单 --> 设置`，然后启用 " +":abbr:`IoT （物联网）`盒子功能。完成此操作后，即可设置称重设备。" #: ../../content/applications/productivity/iot/devices/scale.rst:45 msgid "" "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then " "click :guilabel:`Save` to save the changes, if required." -msgstr "" +msgstr "从 :guilabel:`电子秤` 下拉菜单中选择刻度。然后点击 :guilabel:`保存`，以保存更改（如需要）。" #: ../../content/applications/productivity/iot/devices/scale.rst-1 msgid "List of the external tools that can be used with PoS and the IoT box." @@ -4319,6 +4685,8 @@ msgid "" ":guilabel:`PoS` screen opens the scale screen, where the cashier can weigh " "the product and add the correct price to the cart." msgstr "" +"现在，在所有 :abbr:`PoS（销售点）` 环节中都可以使用电子秤。如果产品设置了按重量计价，点击 :guilabel:`PoS` " +"屏幕上的产品就会打开称重屏幕，收银员可在此称重产品并将正确的价格添加到购物车。" #: ../../content/applications/productivity/iot/devices/scale.rst-1 msgid "Electronic Scale dashboard view when no items are being weighed." @@ -4333,7 +4701,7 @@ msgid "" "In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a " "screen display. After being configured, the screen can be used to display a " "Point of Sale (PoS) order to a client." -msgstr "" +msgstr "在 Odoo 中，:abbr:`IoT（物联网）`盒子可以连接到屏幕显示器。经过配置后，屏幕可用于向客户显示销售点（PoS）订单。" #: ../../content/applications/productivity/iot/devices/screen.rst:10 msgid "An example of a PoS (point of sale) order on a screen display." @@ -4347,12 +4715,15 @@ msgid "" ":menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet" " of Things)` box homepage link." msgstr "" +"访问:abbr:`IoT（物联网）` 盒子主页并点击 :guilabel:`PoS 显示器` 按钮，即可访问客户显示器。要进入 :abbr:`IoT " +"（物联网）` 盒子主页，请导航至 :menuselection:`物联网应用程序 --> 物联网盒子` 并点击 :abbr:`IoT （物联网）` " +"盒子主页链接。" #: ../../content/applications/productivity/iot/devices/screen.rst:20 msgid "" "The way to connect the screen display to the :abbr:`IoT (Internet of " "Things)` box differs depending on the model." -msgstr "" +msgstr "屏幕显示器与 :abbr:`IoT （物联网）` 盒子的连接方式因型号而异。" #: ../../content/applications/productivity/iot/devices/screen.rst:25 msgid "IoT Box model 4" @@ -4364,6 +4735,8 @@ msgid "" ":abbr:`IoT (Internet of Things)` box. If two screens are connected, they can" " display distinct content (see :ref:`Screen Usage <iot/usage_screen>`)." msgstr "" +"在 :abbr:`IoT（物联网）`盒子的侧面，使用 micro-HDMI 电缆最多可连接两个屏幕。如果连接了两个屏幕，则可以显示不同的内容（参见 " +":ref:`屏幕用法 <iot/usage_screen>`）。" #: ../../content/applications/productivity/iot/devices/screen.rst:31 msgid "IoT Box model 3" @@ -4373,7 +4746,7 @@ msgstr "物联网（IoT）盒子型号3" msgid "" "Connect the screen with an HDMI cable on the side of the :abbr:`IoT " "(Internet of Things)` box." -msgstr "" +msgstr "用:abbr:`IoT（物联网）`盒子侧面的 HDMI 电缆连接屏幕。" #: ../../content/applications/productivity/iot/devices/screen.rst:36 msgid ":ref:`See the Raspberry Pi Schema <iot/connect_schema>`." @@ -4386,13 +4759,15 @@ msgid "" "restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten " "seconds and plugging it back into its power source." msgstr "" +"应在打开 :abbr:`IoT（物联网）` 盒子之前连接屏幕。如果已经打开，请连接屏幕，然后拔下 :abbr:`IoT " +"（物联网）`盒子的插头十秒钟，再将其插回电源，重新启动。" #: ../../content/applications/productivity/iot/devices/screen.rst:44 msgid "" "The usage of HDMI/micro-HDMI adapters may cause issues which will result in " "a blank, black screen on the screen display. Using the specific cable for " "the display connection is recommended." -msgstr "" +msgstr "使用 HDMI/micro-HDMI 适配器可能会导致屏幕显示空白、黑屏等问题。建议使用专用电缆连接显示器。" #: ../../content/applications/productivity/iot/devices/screen.rst:47 msgid "" @@ -4404,7 +4779,7 @@ msgstr "连接成功后，屏幕应显示:guilabel:`销售点客户显示`。" msgid "" "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" "connected to an IoT box." -msgstr "" +msgstr "当屏幕显示器成功连接到物联网盒子时，会出现默认的 \"POS 客户端显示\" 屏幕。" #: ../../content/applications/productivity/iot/devices/screen.rst:55 msgid "" @@ -4412,17 +4787,19 @@ msgid "" ":abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display " "can be seen by accessing :menuselection:`IoT app --> Devices`." msgstr "" +"屏幕也应出现在 :abbr:`IoT （物联网）` 盒子主页上的 :guilabel:`显示` 列表中。此外，也可通过访问 " +":menuselection:`物联网应用程序 --> 设备` 查看显示屏。" #: ../../content/applications/productivity/iot/devices/screen.rst-1 msgid "An example of a screen display name shown on the IoT Box Home Page." -msgstr "" +msgstr "物联网盒子主页上显示的屏幕显示名称示例。" #: ../../content/applications/productivity/iot/devices/screen.rst:64 msgid "" "If no screen is detected, a default display named :guilabel:`Distant " "Display` will be displayed instead. This indicates that there is no hardware" " screen connected." -msgstr "" +msgstr "如果未检测到屏幕，则将显示名为 :guilabel:`远程显示` 的默认显示屏。这表示没有连接硬件屏幕。" #: ../../content/applications/productivity/iot/devices/screen.rst:0 msgid "The \"Distant Display\" screen name will be used if no screen is detected." @@ -4434,7 +4811,7 @@ msgstr "用法" #: ../../content/applications/productivity/iot/devices/screen.rst:77 msgid "Show Point of Sale orders to customers" -msgstr "" +msgstr "向客户显示销售点订单" #: ../../content/applications/productivity/iot/devices/screen.rst:79 msgid "" @@ -4443,12 +4820,14 @@ msgid "" "Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT " "Box` feature." msgstr "" +"要在*销售点应用程序*中使用该屏幕，请转到:menuselection:`销售点-->配置-->销售点`，选择一个: " +"abbr:`PoS（销售点）`，必要时点击:guilabel:`编辑`，并启用:guilabel:`物联网盒子`功能。" #: ../../content/applications/productivity/iot/devices/screen.rst:83 msgid "" "Next, select the screen from the :guilabel:`Customer Display` drop-down " "menu. Then click :guilabel:`Save`, if required." -msgstr "" +msgstr "然后，从 :guilabel:`客户显示屏` 下拉菜单中选择屏幕。然后点击 :guilabel:`保存`（如需要）。" #: ../../content/applications/productivity/iot/devices/screen.rst-1 msgid "Connect the screen display to the Point of Sale app." @@ -4459,19 +4838,19 @@ msgid "" "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A " "screen icon will appear in the menu at the top of the screen to indicate the" " screen's connection status." -msgstr "" +msgstr "屏幕现在可用于 :abbr:`PoS（销售点）` 会话。屏幕顶部的菜单中会出现一个屏幕图标，显示屏幕的连接状态。" #: ../../content/applications/productivity/iot/devices/screen.rst-1 msgid "" "The \"screen\" icon on the Point of Sale display shows the connection status with the\n" "screen." -msgstr "" +msgstr "销售点显示屏上的 \"屏幕\" 图标显示与屏幕的连接状态。" #: ../../content/applications/productivity/iot/devices/screen.rst:98 msgid "" "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders " "and update when changes are made to the order." -msgstr "" +msgstr "屏幕将自动显示 :abbr:`PoS（销售点）`订单，并在订单发生更改时进行更新。" #: ../../content/applications/productivity/iot/devices/screen.rst-1 msgid "An example of a PoS order on a screen display." @@ -4479,7 +4858,7 @@ msgstr "屏幕显示的销售点（PoS）订单示例。" #: ../../content/applications/productivity/iot/devices/screen.rst:106 msgid "Display a website on the screen" -msgstr "" +msgstr "在屏幕上显示网站" #: ../../content/applications/productivity/iot/devices/screen.rst:108 msgid "" @@ -4487,6 +4866,8 @@ msgid "" "--> Customer Display`. This allows the user to choose a particular website " "URL to display on the screen using the :guilabel:`Display URL` field." msgstr "" +"通过访问 :menuselection:`物联网应用程序 --> 设备 --> 客户显示器` 打开屏幕表单视图。这样，用户就可以使用 " +":guilabel:`显示 URL` 字段，选择要在屏幕上显示的特定网站 URL。" #: ../../content/applications/productivity/knowledge.rst:7 #: ../../content/applications/productivity/knowledge/articles_editing.rst:203 @@ -4539,6 +4920,8 @@ msgid "" "change the name of your article later, you must do it manually. To do so, " "click the name on the top bar and proceed to the modification." msgstr "" +"单击顶部栏左侧的 :guilabel:`无标题` 可自动匹配:dfn:`h1 (First-level " +"header)`标题和文章名称。之后如要更改文章名称，必须手动操作。需要单击顶栏上的名称，然后进行修改。" #: ../../content/applications/productivity/knowledge/articles_editing.rst:23 msgid "Text editor" @@ -4631,7 +5014,7 @@ msgstr "将段落更改为标题（1→6）、普通文本、`code`或*引用* #: ../../content/applications/productivity/knowledge/articles_editing.rst:58 msgid "Cover pictures" -msgstr "" +msgstr "封面图片" #: ../../content/applications/productivity/knowledge/articles_editing.rst:60 msgid "" @@ -4676,6 +5059,7 @@ msgid "" "To associate Unsplash with your database, please refer to " ":doc:`../../websites/website/configuration/unsplash`." msgstr "" +"要将Unsplash与数据库关联，请参见 :doc:`../../websites/website/configuration/unsplash`。" #: ../../content/applications/productivity/knowledge/articles_editing.rst:78 msgid "" @@ -5028,7 +5412,7 @@ msgstr "插入你的签名。" #: ../../content/applications/productivity/knowledge/articles_editing.rst:241 msgid "Content from other apps" -msgstr "" +msgstr "来自其他应用程序的内容" #: ../../content/applications/productivity/knowledge/articles_editing.rst:243 msgid "" @@ -5062,7 +5446,7 @@ msgstr "**没有**查看该视图的用户即使可以查看包含该视图的 #: ../../content/applications/productivity/knowledge/management.rst:3 msgid "Articles management" -msgstr "" +msgstr "文章管理" #: ../../content/applications/productivity/knowledge/management.rst:5 msgid "" @@ -5073,21 +5457,24 @@ msgid "" "to :ref:`removal <management/remove>`, through :ref:`sharing " "<management/share>` and :ref:`structure <management/structure>`." msgstr "" +"有效管理文章是最大化知识资源价值的关键，无论是研究项目、考试复习，还是为企业建立知识数据库都是如此。知识库让您全面管理文章，包括:ref:`创建 " +"<management/create>` 、:ref:`移除 <management/remove>`、:ref:`分享 " +"<management/share>` 和 :ref:`组织结构 <management/structure>`。" #: ../../content/applications/productivity/knowledge/management.rst:11 msgid "" "You can find most tools to manage articles by clicking the vertical ellipsis" " button (:guilabel:`⋮`) at the right side of the top bar. From there, you " "can move, lock, delete, or duplicate an article." -msgstr "" +msgstr "点击顶部栏右侧的垂直省略号按钮（:guilabel:`⋮`），可以找到大多数管理文章的工具。在这里，你可以移动、锁定、删除或复制文章。" #: ../../content/applications/productivity/knowledge/management.rst-1 msgid "Menu with tools for the management of articles" -msgstr "" +msgstr "带有文章管理工具的菜单" #: ../../content/applications/productivity/knowledge/management.rst:18 msgid "Creation, sharing, and removal of articles" -msgstr "" +msgstr "创建、分享和删除文章" #: ../../content/applications/productivity/knowledge/management.rst:23 msgid "Creation" @@ -5098,26 +5485,26 @@ msgid "" "To create articles, click the :guilabel:`+ New` button on the right side of " "the top bar or the :guilabel:`+` button next to a category or another " "article." -msgstr "" +msgstr "要创建文章，请单击顶部栏右侧的 :guilabel:`+ 新建` 按钮，或其他文章旁边的 :guilabel:`+` 按钮。" #: ../../content/applications/productivity/knowledge/management.rst:29 msgid "" "Create private articles quickly with the Alt/Option + C keyboard shortcut." -msgstr "" +msgstr "使用 Alt/Option + C 快捷键快速创建私人文章。" #: ../../content/applications/productivity/knowledge/management.rst:34 msgid "Sharing" -msgstr "" +msgstr "分享" #: ../../content/applications/productivity/knowledge/management.rst:36 msgid "" "You can share articles with internal or external users. To do so, open the " "share menu by clicking :guilabel:`Share` in the top-right menu of articles." -msgstr "" +msgstr "您可以与内部或外部用户共享文章。请单击文章右上角菜单中的 :guilabel:`分享`，打开分享菜单。" #: ../../content/applications/productivity/knowledge/management.rst:40 msgid "Invite users" -msgstr "" +msgstr "邀请用户" #: ../../content/applications/productivity/knowledge/management.rst:42 msgid "" @@ -5127,36 +5514,38 @@ msgid "" "rights) <management/categories>` and enter the :guilabel:`Recipients`' name " "or email." msgstr "" +"要与特定用户（内部或外部用户，如合作伙伴或客户）共享文章，请单击 :guilabel:`邀请`。会弹出一个窗口，您可以选择 :guilabel:`允许`" +" :ref:`（即访问权限）<management/categories>`，并输入 :guilabel:`接收人`的姓名或电子邮件。" #: ../../content/applications/productivity/knowledge/management.rst:47 msgid "" "You can also restrict a specific user from accessing the article by " "selecting :guilabel:`No access` permission." -msgstr "" +msgstr "您还可以选择 :guilabel:`无访问权限`，来限制特定用户访问文章。" #: ../../content/applications/productivity/knowledge/management.rst-1 msgid "pop-up window to invite users to access a Knowledge article" -msgstr "" +msgstr "弹出窗口邀请用户访问知识文章" #: ../../content/applications/productivity/knowledge/management.rst:54 msgid "Share online" -msgstr "" +msgstr "在线分享" #: ../../content/applications/productivity/knowledge/management.rst:56 msgid "" "To share articles **online**, activate the :guilabel:`Share to web` button. " "Doing so generates a URL link anyone can use to view the article." -msgstr "" +msgstr "要**在线**分享文章，请激活 :guilabel:`分享到网络` 按钮。这样做会生成一个 URL 链接，任何人都可以用来查看文章。" #: ../../content/applications/productivity/knowledge/management.rst:59 msgid "" "Additionally, the share menu displays the default permission for internal " "members along with all the users who have been granted specific permission." -msgstr "" +msgstr "此外，共享菜单还显示内部成员的默认权限以及所有被授予特定权限的用户。" #: ../../content/applications/productivity/knowledge/management.rst-1 msgid "Sharing menu with URL for online sharing and the list of members." -msgstr "" +msgstr "共享菜单，包括用于在线共享的 URL 和成员名单。" #: ../../content/applications/productivity/knowledge/management.rst:68 msgid "Removal" @@ -5164,7 +5553,7 @@ msgstr "下架" #: ../../content/applications/productivity/knowledge/management.rst:70 msgid "To remove an article, you can either **delete** it or **archive** it." -msgstr "" +msgstr "要移除文章，可以**删除**或**存档**。" #: ../../content/applications/productivity/knowledge/management.rst:72 msgid "" @@ -5173,6 +5562,8 @@ msgid "" "days before being permanently deleted. To restore it, click :guilabel:`Open " "the Trash`, select the article, and click :guilabel:`Restore`." msgstr "" +"要删除文章，请打开文章并单击垂直省略号按钮 :menuselection:`(⋮) --> 删除`。文章会被移至垃圾桶 30 " +"天，然后被永久删除。要恢复它，请单击 :guilabel:`打开垃圾箱`，选择文章，然后单击 :guilabel:`恢复`。" #: ../../content/applications/productivity/knowledge/management.rst:76 msgid "" @@ -5183,17 +5574,20 @@ msgid "" "Filter`, and set :guilabel:`Active` as :guilabel:`is No`). Then, select the " "article(s) and go to :menuselection:`Action --> Unarchive`." msgstr "" +"要将文章存档，请单击:guilabel:`搜索`，选择文章，然后单击:menuselection:`操作-->存档-->存档`。存档文章将从搜索菜单中隐藏。要检索存档文章，请添加自定义筛选器以显示它们（:menuselection:`搜索" +" --> 筛选器 --> 添加自定义是筛选器`，并将 :guilabel:`激活` 设为 :guilabel:`否`）。然后，选择文章并转到 " +":menuselection:`操作 --> 取消存档`。" #: ../../content/applications/productivity/knowledge/management.rst:85 msgid "Structure of articles" -msgstr "" +msgstr "文章结构" #: ../../content/applications/productivity/knowledge/management.rst:87 msgid "" "Articles are organized into a hierarchical structure wherein the article on " "top is a parent article, and those underneath are called nested articles. " "This structure allows the grouping of related articles." -msgstr "" +msgstr "文章按照层级结构进行组织，顶部的文章是上级文章，下面的文章称为嵌套文章。这种结构可以将相关文章进行分组。" #: ../../content/applications/productivity/knowledge/management.rst:91 msgid "" @@ -5204,6 +5598,9 @@ msgid "" ":guilabel:`Move To` on the toolbox and selecting the article to use as a " "parent." msgstr "" +"要建立这种层次结构，可通过单击待上级文章旁边的 :guilabel:`+` " +"按钮创建新文章，或通过拖放现有文章到准上级文章，或单击垂直省略号按钮（:guilabel:`⋮`），单击工具箱中的 " +":guilabel:`移至`，然后选择要用作上级的文章，移动现有文章。" #: ../../content/applications/productivity/knowledge/management.rst:99 msgid "Categories" @@ -5213,7 +5610,7 @@ msgstr "类别" msgid "" "Additionally, articles are divided into four categories that can be found on" " the left sidebar. These categories give articles default **access rights**." -msgstr "" +msgstr "此外，文章分为四个类别，可在左侧边栏找到。这些类别赋予文章默认的**访问权限**。" #: ../../content/applications/productivity/knowledge/management.rst:104 msgid "" @@ -5222,29 +5619,30 @@ msgid "" "of articles. Marking articles as **favorites** is user-specific and does not" " affect other users." msgstr "" +":guilabel:`收藏`：您可以将任何可以访问的文章设为收藏夹。要执行此操作，请单击文章右上角菜单中的星形图标（:guilabel:`★`）。将文章标记为**收藏夹**是用户的特定操作，不会影响其他用户。" #: ../../content/applications/productivity/knowledge/management.rst:107 msgid "" ":guilabel:`Workspace`: Articles displayed in that category are available to " "all internal users. These users have the right to read, modify or share " "these articles." -msgstr "" +msgstr ":guilabel:`工作区`：该类别中显示的文章对所有内部用户开放。这些用户有权阅读、修改或共享这些文章。" #: ../../content/applications/productivity/knowledge/management.rst:109 msgid "" ":guilabel:`Shared`: Articles displayed in that category are those you shared" " with internal users, external users, or shared with you." -msgstr "" +msgstr ":guilabel:`共享`：该类别中显示的文章是您与内部用户、外部用户共享或与您共享的文章。" #: ../../content/applications/productivity/knowledge/management.rst:111 msgid "" ":guilabel:`Private`: Articles displayed in that category are only available " "to you." -msgstr "" +msgstr ":guilabel:`私密`：该类别中显示的文章只对您开放。" #: ../../content/applications/productivity/knowledge/management.rst-1 msgid "Categories displayed in the left sidebar of Odoo Knowledge" -msgstr "" +msgstr "Odoo 知识应用程序左侧边栏显示的类别" #: ../../content/applications/productivity/knowledge/properties.rst:3 #: ../../content/applications/productivity/studio/fields.rst:453 @@ -5750,6 +6148,9 @@ msgid "" ":guilabel:`urlFetchWhitelist` section, replace all the references to " "`odoo.com` with the Odoo customer's unique server domain." msgstr "" +"接下来，在 ZIP 文件中，转到 :menuselection:`mail-client-extensions-master --> " +"gmail`，并打开名为 :guilabel:`appsscript.json` 的文件。在 :guilabel:`urlFetchWhitelist`" +" 部分，将所有对 `odoo.com` 的引用替换为 Odoo 客户的唯一服务器域。" #: ../../content/applications/productivity/mail_plugins/gmail.rst:122 msgid "" @@ -5757,12 +6158,14 @@ msgid "" ":guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` " "file to push the Gmail Plugin files as a Google Project." msgstr "" +"然后，在同一个 :guilabel:`gmail` 文件夹中，打开名为 :guilabel:`README.md` 的文件。按照 " +":guilabel:`README.md` 文件中的说明，将 Gmail 插件文件作为 Google 项目推送。" #: ../../content/applications/productivity/mail_plugins/gmail.rst:126 msgid "" "The computer must be able to run Linux commands in order to follow the " "instructions on the :guilabel:`README.md` file." -msgstr "" +msgstr "计算机必须能够运行 Linux 命令，才能遵循 :guilabel:`README.md` 文件中的说明。" #: ../../content/applications/productivity/mail_plugins/gmail.rst:129 msgid "" @@ -5784,6 +6187,7 @@ msgid "" "database actions from emails. Odoo has a plugin for Outlook that allows for " "the creation of an opportunity from the email panel." msgstr "" +"Outlook 允许第三方应用程序连接，以便通过电子邮件执行数据库操作。Odoo 有一个 Outlook 插件，可通过电子邮件面板创建商机。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:12 msgid "" @@ -5801,6 +6205,8 @@ msgid "" ":menuselection:`Settings --> General Settings --> Integrations`, enable " ":guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." msgstr "" +"首先，在数据库中启用*邮件插件*功能。进入 :menuselection:`设置-->常规设置-->集成`，启用 :guilabel:`邮件插件`，然后" +" :guilabel:`保存`配置。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:25 msgid "Install the Outlook Plugin" @@ -5813,6 +6219,9 @@ msgid "" "`https://download.odoocdn.com/plugins/outlook/manifest.xml " "<https://download.odoocdn.com/plugins/outlook/manifest.xml>`_." msgstr "" +"下载（:menuselection:`Save Page As --> Web Page XML only`）以下 XML " +"文件以便稍后上传：`https://download.odoocdn.com/plugins/outlook/manifest.xml " +"<https://download.odoocdn.com/plugins/outlook/manifest.xml>`_。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:31 msgid "" @@ -5820,6 +6229,8 @@ msgid "" " click on the :guilabel:`More actions` button in the upper right-side and " "select :guilabel:`Get Add-ins`." msgstr "" +"接下来，打开 Outlook 邮箱，选择任何电子邮件。完成此操作后，点击右上角的 :guilabel:`更多操作` 按钮，选择 " +":guilabel:`获取插件`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "More actions button in Outlook" @@ -5828,7 +6239,7 @@ msgstr "Outlook的“更多操作”按钮" #: ../../content/applications/productivity/mail_plugins/outlook.rst:38 msgid "" "Following this step, select the :guilabel:`My add-ins` tab on the left-side." -msgstr "" +msgstr "完成此步骤后，选择左侧的 :guilabel:`我的插件` 选项卡。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "My add-ins in Outlook" @@ -5839,6 +6250,7 @@ msgid "" "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ " "Add a custom add-in`, and then on :guilabel:`Add from file...`" msgstr "" +"在底部的 :guilabel:`自定义插件`下，点击 :guilabel:`+ 添加自定义插件`，然后点击 :guilabel:`从文件中添加...`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Custom add-ins in Outlook" @@ -5850,6 +6262,7 @@ msgid "" "press :guilabel:`OK`. Next, read the warning and click on " ":guilabel:`Install`." msgstr "" +"下一步，附上上文下载的`manifest.xml`文件，然后点击 :guilabel:`确认`。接下来，阅读警告并点击 :guilabel:`安装`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Custom add-in installation warning in Outlook" @@ -5857,7 +6270,7 @@ msgstr "在Outlook中定制附加程序安装警告" #: ../../content/applications/productivity/mail_plugins/outlook.rst:61 msgid "Connect the database" -msgstr "" +msgstr "连接数据库" #: ../../content/applications/productivity/mail_plugins/outlook.rst:63 msgid "" @@ -5865,6 +6278,8 @@ msgid "" "in the Outlook mailbox, click on the :guilabel:`More actions` button in the " "upper right-side, and select :guilabel:`Odoo for Outlook`." msgstr "" +"现在，Outlook 将连接到 Odoo 数据库。首先，打开 Outlook 邮箱中的任何邮件，点击右上角的 :guilabel:`更多操作` " +"按钮，然后选择 :guilabel:`Odoo for Outlook`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Odoo for Outlook add-in button" @@ -5874,11 +6289,11 @@ msgstr "Odoo中的Outlook附加程序按钮" msgid "" "The right-side panel can now display **Company Insights**. At the bottom, " "click on :guilabel:`Login`." -msgstr "" +msgstr "右侧面板现在可以显示**公司洞察**。在底部，点击 :guilabel:`登录`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Logging in the Odoo database" -msgstr "" +msgstr "登录 Odoo 数据库" #: ../../content/applications/productivity/mail_plugins/outlook.rst:79 msgid "" @@ -5893,12 +6308,13 @@ msgid "" "browser cookie settings prevented it from loading. Note that these settings " "also change if the browser is in \"Incognito\" mode." msgstr "" +"如果过了一段时间，面板仍然为空，则可能是浏览器 cookie 设置阻止了面板的加载。请注意，如果浏览器处于 \"隐身\" 模式，这些设置也会发生变化。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:87 msgid "" "To fix this issue, configure the browser to always allow cookies on Odoo's " "plugin page." -msgstr "" +msgstr "要解决这个问题，请将浏览器配置为始终允许在 Odoo 的插件页面上使用 cookies。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:89 msgid "" @@ -5908,22 +6324,26 @@ msgid "" "`download.odoo.com` to the list of :guilabel:`Sites that can always use " "cookies`." msgstr "" +"对于 Google Chrome 浏览器，请按照以下指南更改浏览器 cookie 设置： " +"`https://support.google.com/chrome/answer/95647 " +"<https://support.google.com/chrome/answer/95647>`_，并将 `download.odoo.com` " +"添加到 :guilabel:`Sites that can always use cookies` 的列表中。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:94 msgid "Once this is complete, the Outlook panel needs to be opened again." -msgstr "" +msgstr "完成后，需要再次打开 Outlook 面板。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:96 msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." -msgstr "" +msgstr "现在，输入 Odoo 数据库 URL 并点击 :guilabel:`登录`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Entering the Odoo database URL" -msgstr "" +msgstr "输入 Odoo 数据库 URL" #: ../../content/applications/productivity/mail_plugins/outlook.rst:102 msgid "Next, click on :guilabel:`Allow` to open the pop-up window." -msgstr "" +msgstr "然后，点击 :guilabel:`允许` 打开弹出窗口。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "New window pop-up warning" @@ -5933,7 +6353,7 @@ msgstr "新的警告弹窗" msgid "" "If the user isn't logged into the database, enter the credentials. Click on " ":guilabel:`Allow` to let the Outlook Plugin connect to the database." -msgstr "" +msgstr "如果用户尚未登录数据库，请输入凭据。点击 :guilabel:`允许` 让 Outlook 插件连接到数据库。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Allowing the Outlook Plugin to connect to a database" @@ -5954,7 +6374,7 @@ msgstr "默认情况下，可以从 *更多操作* 菜单打开 Outlook 插件 msgid "" "In the Outlook mailbox, click on :guilabel:`Settings`, then on " ":guilabel:`View all Outlook settings`." -msgstr "" +msgstr "在 Outlook 邮箱中，点击 :guilabel:`设置`，然后点击 :guilabel:`查看所有 Outlook 设置`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Viewing all Outlook settings" @@ -5965,6 +6385,8 @@ msgid "" "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on " ":guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." msgstr "" +"现在，选择 :guilabel:`邮件` 下的 :guilabel:`自定义操作`，点击 :guilabel:`Odoo for " +"Outlook`，然后点击 :guilabel:`保存`。" #: ../../content/applications/productivity/mail_plugins/outlook.rst-1 msgid "Odoo for Outlook customized action" @@ -5972,11 +6394,11 @@ msgstr "Odoo中的Outlook定制操作" #: ../../content/applications/productivity/mail_plugins/outlook.rst:137 msgid "Following this step, open any email; the shortcut should be displayed." -msgstr "" +msgstr "完成此步骤后，打开任何电子邮件，都会显示快捷方式。" #: ../../content/applications/productivity/mail_plugins/outlook.rst:144 msgid "Using the plugin" -msgstr "" +msgstr "使用插件" #: ../../content/applications/productivity/mail_plugins/outlook.rst:146 msgid "" @@ -5987,6 +6409,9 @@ msgid "" "click on :guilabel:`New`. A new window with the created opportunity in the " "Odoo database will populate." msgstr "" +"现在插件已安装并运行，要创建一个线索，只需点击 `O` [Odoo 图标] 或导航至 :guilabel:`更多操作` 并点击 " +":guilabel:`Odoo for Outlook`。侧面板将出现在右侧，在 :guilabel:`商机` 下点击 " +":guilabel:`新建`。新窗口将显示 Odoo 数据库中创建的机会。" #: ../../content/applications/productivity/studio.rst:6 msgid "Studio" @@ -7581,10 +8006,13 @@ msgid "" "right corner of the report, click the vertical ellipsis icon " "(:guilabel:`⋮`), and then select :guilabel:`Duplicate`." msgstr "" +"要编辑标准 PDF 报告，强烈建议**复制**该报告并对复制版本进行更改，因为在 Odoo 升级后，对标准报告所做的更改将被覆盖。要复制报告，请转到 " +":menuselection:`Studio --> " +"报告`。将鼠标指针悬停在报告右上角，单击垂直省略号图标（:guilabel:`⋮`），然后选择:guilabel:`重复`。" #: ../../content/applications/productivity/studio/pdf_reports.rst:0 msgid "Duplicating a PDF report" -msgstr "" +msgstr "复制 PDF 报告" #: ../../content/applications/productivity/studio/pdf_reports.rst:20 msgid "Default layout" @@ -7796,6 +8224,8 @@ msgid "" "app containing the report, then go to :menuselection:`Studio --> Reports -->" " Select or Create a report --> Report --> Select a Paper format`." msgstr "" +"您可以更改个别报告的 :guilabel:`纸张格式`。打开包含报告的应用程序，然后转到 :menuselection:`Studio --> 报告 " +"--> 选择或创建报告 --> 报告 --> 选择纸张格式`。" #: ../../content/applications/productivity/studio/pdf_reports.rst-1 msgid "Configuration pop-up window for the default layout of PDF reports" @@ -7815,6 +8245,10 @@ msgid "" "reports/header-footer/external`, :ref:`studio/pdf-reports/header-" "footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." msgstr "" +"在 Studio 中创建新报告时，必须先从三种报告样式中选择一种，仅用来确定页眉和页脚的显示内容。转到要添加新报告的应用程序，单击 **Toggle " +"Studio** 按钮，然后单击 :guilabel:`报告`。单击 :guilabel:`新建`，然后选择 :ref:`studio/pdf-" +"reports/header-footer/external`、:ref:`studio/pdf-reports/header-" +"footer/internal` 或 :ref:`studio/pdf-reports/header-footer/blank`。" #: ../../content/applications/productivity/studio/pdf_reports.rst:163 msgid "External" @@ -8770,11 +9204,11 @@ msgstr "待办事项" #: ../../content/applications/productivity/to_do.rst:5 msgid "To-do assists you in organizing and managing personal tasks." -msgstr "" +msgstr "待办事项可帮助您组织和管理个人任务。" #: ../../content/applications/productivity/to_do.rst:8 msgid "Creating to-dos" -msgstr "" +msgstr "创建待办事项" #: ../../content/applications/productivity/to_do.rst:10 msgid "" @@ -8782,6 +9216,8 @@ msgid "" "next to a stage name. Add a title to your to-do, then click :guilabel:`Add` " "to save it or :guilabel:`Edit` to access more options." msgstr "" +"要创建待办事项，点击:guilabel:`新建`或阶段名称旁边的加号按钮（:guilabel:`➕`）。为待办事项添加标题，然后点击 " +":guilabel:`添加` 保存，或点击 :guilabel:`编辑` 访问更多选项。" #: ../../content/applications/productivity/to_do.rst:14 msgid "" @@ -8789,16 +9225,18 @@ msgid "" ":guilabel:`Tags`, :guilabel:`Assignees`, or more information using the Odoo " "Editor." msgstr "" +"如果您选择 :guilabel:`编辑` 待办事项，您可以使用 Odoo 编辑器添加 :guilabel:`标签`, :guilabel:`指定人` " +"或更多信息。" #: ../../content/applications/productivity/to_do.rst:18 msgid "Adding :guilabel:`Assignees` shares the to-do with the users selected." -msgstr "" +msgstr "添加 :guilabel:`指定人` 可与所选用户共享待办事项。" #: ../../content/applications/productivity/to_do.rst:19 msgid "" "Type `/` in the editor box to structure and format your content. You can " "also add media, links, and widgets." -msgstr "" +msgstr "在编辑框中键入 `/`，以构建和格式化您的内容。您还可以添加媒体、链接和小工具。" #: ../../content/applications/productivity/to_do.rst:23 msgid "" @@ -8807,14 +9245,16 @@ msgid "" ":guilabel:`Add a To-Do`, or by clicking the clock button and then " ":guilabel:`Add a To-Do`." msgstr "" +"您可以在 Odoo 的任意位置，通过键盘快捷键 ´ctrl+k´ 打开**命令调板工具**，然后单击 " +":guilabel:`添加待办事项`，或单击时钟按钮，然后单击 :guilabel:`添加待办事项`，即时创建新的待办事项。" #: ../../content/applications/productivity/to_do.rst:0 msgid "Adding a to-do on the fly" -msgstr "" +msgstr "即时添加一个待办事项" #: ../../content/applications/productivity/to_do.rst:31 msgid "Converting to-dos into project tasks" -msgstr "" +msgstr "将待办事项转化为项目任务" #: ../../content/applications/productivity/to_do.rst:33 msgid "" @@ -8822,6 +9262,9 @@ msgid "" "dos into project tasks. To do so, open a to-do and click the gear button " "(:guilabel:`⚙`), then :guilabel:`Convert to Task`." msgstr "" +"如果您使用 :doc:`项目应用程序 " +"<../services/project>`，您可以将待办事项转换为项目任务。为此，打开待办事项并单击齿轮按钮（:guilabel:`⚙`），然后单击 " +":guilabel:`转换为任务`。" #: ../../content/applications/productivity/to_do.rst:36 msgid "" @@ -8829,40 +9272,43 @@ msgid "" ":guilabel:`Tags`, then click :guilabel:`Convert to Task`. The to-do is now a" " project task and appears in the selected project." msgstr "" +"接下来，选择 :guilabel:`项目`、:guilabel:`指定人`和 :guilabel:`标签`，然后单击 " +":guilabel:`转换为任务`。待办事项现在是项目任务，出现在选定的项目中。" #: ../../content/applications/productivity/to_do.rst-1 msgid "Converting a to-do into a task" -msgstr "" +msgstr "将待办事项转化为任务" #: ../../content/applications/productivity/to_do.rst:43 msgid "Managing the to-do pipeline" -msgstr "" +msgstr "管理待办事项" #: ../../content/applications/productivity/to_do.rst:45 msgid "" "Your assigned **to-dos** are displayed on the app dashboard. You can drag " "and drop a to-do to move it from one stage to another." -msgstr "" +msgstr "您分配的**待办事项**会显示在应用程序仪表板上。您可以拖放待办事项，将其从一个阶段移动到另一个阶段。" #: ../../content/applications/productivity/to_do.rst-1 msgid "Example of a to-do pipeline" -msgstr "" +msgstr "待办事项流程示例" #: ../../content/applications/productivity/to_do.rst:52 msgid "" "Click the :guilabel:`+ Personal Stage` button on the left of the pipeline to" " create a new stage." -msgstr "" +msgstr "点击管道左侧的 :guilabel:`+ 个人阶段` 按钮，创建一个新阶段。" #: ../../content/applications/productivity/to_do.rst:54 msgid "" "Click the gear button (:guilabel:`⚙`) next to a stage to :guilabel:`Fold`, " ":guilabel:`Edit`, or :guilabel:`Delete` it." msgstr "" +"单击阶段旁边的齿轮按钮（:guilabel:`⚙`）以 :guilabel:`折叠`、:guilabel:`编辑`或 :guilabel:`删除`阶段。" #: ../../content/applications/productivity/to_do.rst:0 msgid "Stage settings button" -msgstr "" +msgstr "阶段设置按钮" #: ../../content/applications/productivity/to_do.rst:61 msgid "Scheduling activities" @@ -8872,11 +9318,11 @@ msgstr "安排活动" msgid "" "To schedule an activity on a to-do, click the clock button on the app " "dashboard, then the :guilabel:`+ Schedule an activity` button." -msgstr "" +msgstr "要在待办事项上安排活动，请单击应用程序仪表板上的时钟按钮，然后单击 :guilabel:`+ 安排活动` 按钮。" #: ../../content/applications/productivity/to_do.rst-1 msgid "Scheduling an activity from the To-do dashboard" -msgstr "" +msgstr "从待办事项仪表板安排活动" #: ../../content/applications/productivity/to_do.rst:69 msgid "To create the activity:" @@ -8884,11 +9330,11 @@ msgstr "" #: ../../content/applications/productivity/to_do.rst:71 msgid "Select an :guilabel:`Activity Type`." -msgstr "" +msgstr "选择 :guilabel:`活动类型`。" #: ../../content/applications/productivity/to_do.rst:72 msgid "Select a :guilabel:`Due date`." -msgstr "" +msgstr "选择 :guilabel:`到期日期`。" #: ../../content/applications/productivity/to_do.rst:73 msgid "Choose who the activity should be :guilabel:`Assigned to`." @@ -8912,13 +9358,15 @@ msgstr "" #: ../../content/applications/productivity/to_do.rst:83 msgid "Viewing to-dos in the Project app" -msgstr "" +msgstr "在项目应用程序中查看待办事项" #: ../../content/applications/productivity/to_do.rst:85 msgid "" "If you use the :doc:`Project app <../services/project>`, your to-dos also " "appear as private tasks under the :guilabel:`My Tasks` view." msgstr "" +"如果您使用 :doc:`项目应用程序 <../services/project>`，您的待办事项也会作为私人任务出现在 :guilabel:`我的任务`" +" 视图下。" #: ../../content/applications/productivity/to_do.rst-1 msgid "Example of a \"My Tasks\" pipeline in the Project app" @@ -8942,54 +9390,63 @@ msgid "" " communicate with their customers by text, send documents and provide " "support." msgstr "" +"**WhatsApp**是一款即时通讯和IP语音应用程序，允许用户发送信息、拨打电话和共享内容。企业可以使用 `WhatsApp Business " +"<https://developers.facebook.com/products/whatsapp/>`_与客户进行文字交流、发送文件和提供支持。" #: ../../content/applications/productivity/whatsapp.rst:10 msgid "" "With the **Odoo WhatsApp** app, a company can connect a WhatsApp Business " "Account (WABA) to an Odoo database, which allows for the following:" msgstr "" +"通过**Odoo WhatsApp** 应用程序，公司可以将 WhatsApp 商业账户（WABA）与 Odoo 数据库连接起来，从而实现以下功能：" #: ../../content/applications/productivity/whatsapp.rst:13 msgid "Receive and reply to WhatsApp messages directly from an Odoo database" -msgstr "" +msgstr "直接从 Odoo 数据库接收和回复 WhatsApp 消息" #: ../../content/applications/productivity/whatsapp.rst:14 msgid "Create new templates with dynamic placeholders/variables" -msgstr "" +msgstr "创建带动态占位符/变量的新模板" #: ../../content/applications/productivity/whatsapp.rst:15 msgid "Send pre-approved templates that use dynamic variables, such as:" -msgstr "" +msgstr "发送预先批准的使用动态变量的模板，如：" #: ../../content/applications/productivity/whatsapp.rst:17 msgid "Quotations from the Sales app" -msgstr "" +msgstr "销售应用程序报价" #: ../../content/applications/productivity/whatsapp.rst:18 msgid "Receipts and invoices from the Point of Sale app" -msgstr "" +msgstr "销售点应用程序中的收据和发票" #: ../../content/applications/productivity/whatsapp.rst:19 msgid "Tickets from the Events app" -msgstr "" +msgstr "活动管理应用程序中的工单" #: ../../content/applications/productivity/whatsapp.rst:22 msgid "" "`Meta Business: create message templates for the WhatsApp Business account " "<https://www.facebook.com/business/help/2055875911147364>`_." msgstr "" +"`Meta Business：为 WhatsApp Business 账户创建消息模板 " +"<https://www.facebook.com/business/help/2055875911147364>`_。" #: ../../content/applications/productivity/whatsapp.rst:24 msgid "" "`Meta Business: connect a phone number to the WhatsApp Business account " "<https://www.facebook.com/business/help/456220311516626>`_." msgstr "" +"`Meta Business：将电话号码连接到 WhatsApp Business 帐户 " +"<https://www.facebook.com/business/help/456220311516626>`_。" #: ../../content/applications/productivity/whatsapp.rst:26 msgid "" "`Meta Business: change the WhatsApp Business display name " "<https://www.facebook.com/business/help/378834799515077>`_." msgstr "" +"`Meta Business：更改 WhatsApp Business 显示名称 " +"<https://www.facebook.com/business/help/378834799515077>`_。" #: ../../content/applications/productivity/whatsapp.rst:29 msgid "" @@ -9000,6 +9457,9 @@ msgid "" "account is configured in Odoo via an :abbr:`API (Application Programming " "Interface)` connection." msgstr "" +"WhatsApp 是由 Facebook 的母公司 Meta 运营的一项信息服务。WhatsApp " +"在许多国家和企业中被普遍用作通信工具。本文档将介绍如何将 WhatsApp 企业账户与 Odoo 整合。公司的 Meta " +"账户是通过:abbr:`API（应用程序编程接口）`连接在 Odoo 中配置的。" #: ../../content/applications/productivity/whatsapp.rst:35 msgid "" @@ -9009,6 +9469,9 @@ msgid "" " to trigger a discussion between the sender and the receiver (a *Discuss* " "chat window will pop up if the customer answers within 15 days)." msgstr "" +"WhatsApp " +"连接器支持两种流程：公司发起和客户发起。公司可以通过向一人或多人发送模板来发起讨论。模板发送后，收件人可以回复，以触发发送方和收件人之间的讨论（如果客户在" +" 15 天内回复，则会弹出*讨论*聊天窗口）。" #: ../../content/applications/productivity/whatsapp.rst:40 msgid "" @@ -9016,51 +9479,52 @@ msgid "" "company's public WhatsApp number), then Odoo will open a group chat with all" " operators responsible for this WhatsApp channel." msgstr "" +"如果讨论是由客户发起的（例如发送到公司的公开 WhatsApp 号码），那么 Odoo 将与负责此 WhatsApp 频道的所有操作员开启群聊。" #: ../../content/applications/productivity/whatsapp.rst:44 msgid "" "It is recommended to set up multiple WhatsApp accounts for different " "departments. For example, the help desk team and sales teams can chat on " "different channels." -msgstr "" +msgstr "建议为不同部门设置多个 WhatsApp 账户。例如，服务台团队和销售团队可以通过不同的渠道聊天。" #: ../../content/applications/productivity/whatsapp.rst:48 msgid "WhatsApp configuration in a Meta" -msgstr "" +msgstr "WhatsApp 在 Meta 中的配置" #: ../../content/applications/productivity/whatsapp.rst:50 msgid "" "A WhatsApp integration with Odoo uses a standard :abbr:`API (Application " "Programming Interface)` connection, and is configured on Meta in the " "following steps:" -msgstr "" +msgstr "WhatsApp 与 Odoo 的整合使用标准的:abbr:`API（应用程序编程接口）`连接，在 Meta 上的配置步骤如下：" #: ../../content/applications/productivity/whatsapp.rst:53 msgid "Create a Meta business account" -msgstr "" +msgstr "创建 Meta 企业账户" #: ../../content/applications/productivity/whatsapp.rst:54 msgid "Create a Meta developer account" -msgstr "" +msgstr "创建 Meta 开发者账户" #: ../../content/applications/productivity/whatsapp.rst:55 msgid "Setup an *app* and WhatsApp *product* on Meta's developer console" -msgstr "" +msgstr "在 Meta 开发人员控制台设置*应用程序*和 WhatsApp *产品*" #: ../../content/applications/productivity/whatsapp.rst:56 msgid "Test the API connection." -msgstr "" +msgstr "测试 API 连接。" #: ../../content/applications/productivity/whatsapp.rst:58 msgid "" "Once connected, messages are then sent and received through Odoo's *Discuss*" " application using the WhatsApp :abbr:`API (Application Programming " "Interface)`." -msgstr "" +msgstr "连接后，可使用 WhatsApp :`API（应用程序编程接口）`通过 Odoo 的 *内部讨论* 应用程序收发消息。" #: ../../content/applications/productivity/whatsapp.rst:62 msgid "Meta business account setup" -msgstr "" +msgstr "Meta 企业账户设置" #: ../../content/applications/productivity/whatsapp.rst:64 msgid "" @@ -9071,25 +9535,31 @@ msgid "" ":guilabel:`Next`, and a pop-up window will appear prompting to confirm the " "email address. After confirming, click :guilabel:`Done` to close the window." msgstr "" +"要在 Meta（Facebook 的所有者）上创建企业账户，请导航至 `Facebook 企业管理平台 " +"<https://business.facebook.com/overview>`_。首先点击 " +":guilabel:`创建账户`，然后输入企业名称、管理员姓名和工作电子邮件地址。然后点击 " +":guilabel:`下一步`，弹出窗口提示确认电子邮件地址。确认后，点击 :guilabel:`完成` 关闭窗口。" #: ../../content/applications/productivity/whatsapp.rst:70 msgid "" "Next, follow the instructions in the email sent by Facebook to confirm the " "creation of the business account and to complete the setup process." -msgstr "" +msgstr "接下来，按照 Facebook 发送的电子邮件中的说明，确认创建企业账户并完成设置过程。" #: ../../content/applications/productivity/whatsapp.rst:74 msgid "" "`Set up a Meta business account " "<https://www.facebook.com/business/help/1710077379203657?id=180505742745347>`_." msgstr "" +"`设立 Meta 企业账户 " +"<https://www.facebook.com/business/help/1710077379203657?id=180505742745347>`_。" #: ../../content/applications/productivity/whatsapp.rst:78 msgid "" "If the business account is linked to a personal Facebook account then the " "administrator must toggle between the personal account to the business " "account for the remainder of the configuration." -msgstr "" +msgstr "如果企业帐户与个人 Facebook 帐户相关联，则管理员必须在个人帐户和企业帐户之间进行切换，以完成剩余的配置。" #: ../../content/applications/productivity/whatsapp.rst:82 msgid "" @@ -9100,10 +9570,13 @@ msgid "" "place in. This will be the account for which Odoo will send and receive " "WhatsApp messages." msgstr "" +"要切换到业务帐户，请导航到 `Facebook 开发人员控制台 " +"<https://developers.facebook.com>`_，然后点击右上角的*帐户名*。在 :guilabel:`企业账户` 标题下，点击 " +"WhatsApp 配置所需的企业。这将是 Odoo 收发 WhatsApp 消息的账户。" #: ../../content/applications/productivity/whatsapp.rst:0 msgid "Toggle between Meta personal and business accounts." -msgstr "" +msgstr "在 Meta 个人账户和企业账户之间切换。" #: ../../content/applications/productivity/whatsapp.rst:93 msgid "" @@ -9112,10 +9585,12 @@ msgid "" "to setting up the Facebook Business account. Trying to create the business " "account prior to this time will result in an error." msgstr "" +"要创建 Meta 企业帐户，用户必须已经拥有个人 Facebook 账户，并且该账户在设置 Facebook " +"商业账户之前至少存在了一个小时。在此时间之前尝试创建商业账户将导致错误。" #: ../../content/applications/productivity/whatsapp.rst:98 msgid "App creation" -msgstr "" +msgstr "应用程序创建" #: ../../content/applications/productivity/whatsapp.rst:100 msgid "" @@ -9123,6 +9598,8 @@ msgid "" "sign in with the Meta developer account. If no account is configured yet, " "link a Facebook account to create a Meta developer account." msgstr "" +"在 `面向开发者的 Meta<https://developers.facebook.com>`_面板上，使用 Meta " +"开发者账户登录。如果尚未配置账户，请链接 Facebook 账户以创建 Meta 开发者账户。" #: ../../content/applications/productivity/whatsapp.rst:105 msgid "" @@ -9131,12 +9608,16 @@ msgid "" " business accounts are **not** as they represent a business and manage all " "of the business's assets in Meta, such as apps." msgstr "" +"Facebook的 *开发者* 账户与 Facebook 的 *商业* 账户是不同的。开发者账户由个人 Facebook " +"账户组成，而商业账户则代表一个企业，并在 Meta 中管理企业的所有资产，如应用程序。" #: ../../content/applications/productivity/whatsapp.rst:110 msgid "" "`Set up the WhatsApp Business Platform " "<https://www.facebookblueprint.com/student/collection/409587/path/360218>`_." msgstr "" +"`设置 WhatsApp 企业平台 " +"<https://www.facebookblueprint.com/student/collection/409587/path/360218>`_。" #: ../../content/applications/productivity/whatsapp.rst:113 msgid "" @@ -9146,10 +9627,13 @@ msgid "" "developer account. Click on :guilabel:`Create App` to begin the process of " "configuring a new Meta application." msgstr "" +"成功登录 Meta 开发者账户后，点击右上角的 " +":guilabel:`我的应用程序`。这将把管理员重定向到开发者在此特定开发者账户中配置的所有应用程序。点击 :guilabel:`创建应用程序` " +"开始配置新的 Meta 应用程序。" #: ../../content/applications/productivity/whatsapp.rst:119 msgid "App type" -msgstr "" +msgstr "应用程序类型" #: ../../content/applications/productivity/whatsapp.rst:121 msgid "" @@ -9161,17 +9645,21 @@ msgid "" "creation and management of the WhatsApp :abbr:`API (Application Programming " "Interface)`." msgstr "" +"在 :menuselection:`创建应用程序` 页面上，在标有 :guilabel:`还在寻找其他东西？` 的部分下选择 " +":guilabel:`其他`，然后点击 :guilabel:`下一步` 进入另一个页面以选择应用程序类型。然后，点击 " +":guilabel:`选择应用程序类型` 标签下的第一个选项，标题为 :guilabel:`企业`。该选项允许创建和管理 WhatsApp " +":abbr:`API（应用程序编程接口）`。" #: ../../content/applications/productivity/whatsapp.rst:127 msgid "" "Now, click :guilabel:`Next` to configure the app, as desired. When the app " "*type* has been configured, the administrator will move onto the app " "*details* section." -msgstr "" +msgstr "现在，点击 :guilabel:`下一步` 按需要配置应用程序。配置应用程序*类型*后，管理员将进入应用程序*详细信息*部分。" #: ../../content/applications/productivity/whatsapp.rst:131 msgid "App details" -msgstr "" +msgstr "应用程序详细信息" #: ../../content/applications/productivity/whatsapp.rst:133 msgid "" @@ -9182,20 +9670,20 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:137 msgid "" "The app name can be changed at a later time in the settings, if necessary." -msgstr "" +msgstr "如有必要，稍后可在设置中更改应用程序名称。" #: ../../content/applications/productivity/whatsapp.rst:140 msgid "" "Trademarks and branded elements may not be used in this text section. These " "include the Meta group of companies. Do not include the word: `WhatsApp` or " "the system will flag this in error." -msgstr "" +msgstr "在此文本部分中，不得使用商标和品牌元素，包括 Meta 集团公司。请勿包含 `WhatsApp` 一词，否则系统将标记为错误。" #: ../../content/applications/productivity/whatsapp.rst:143 msgid "" "Next, enter the developer email address in the field under the " ":guilabel:`App contact email` label." -msgstr "" +msgstr "然后，在 :guilabel:`应用程序联系人电子邮件` 标签下的字段中输入开发者的电子邮件地址。" #: ../../content/applications/productivity/whatsapp.rst:145 msgid "" @@ -9204,6 +9692,8 @@ msgid "" ":guilabel:`Create app`. This action will create the app and prompts the " "*Meta Platform Terms* and *Developer Policies* agreements." msgstr "" +"最后，使用下拉菜单将 :guilabel:`企业账户 - 可选` 字段设置为 Meta 业务账户配置文件。最后，点击 " +":guilabel:`创建应用程序`。此操作将创建应用程序，并提示*Meta 平台条款*和*开发者政策*协议。" #: ../../content/applications/productivity/whatsapp.rst:149 msgid "" @@ -9211,6 +9701,8 @@ msgid "" " and click :guilabel:`Submit` to finalize the app creation. The browser will" " then direct to the :guilabel:`Meta for Developers` dashboard." msgstr "" +"要接受协议，请输入 Facebook 密码以确保安全，然后单击 :guilabel:`提交` 以完成创建应用程序。然后，浏览器将跳转到 " +":guilabel:`Meta 开发者模式` 仪表板。" #: ../../content/applications/productivity/whatsapp.rst:154 msgid "" @@ -9218,16 +9710,20 @@ msgid "" " won't be allowed. To resolve this issue navigate to " "`<https://business.facebook.com/business>`_ for assistance." msgstr "" +"如果 Meta 企业帐户被禁止发布广告，则不允许申请应用程序。要解决此问题，请访问 " +"`<https://business.facebook.com/business>`_ 寻求帮助。" #: ../../content/applications/productivity/whatsapp.rst:157 msgid "" "For more information, see `Meta's documentation on advertising restrictions " "<https://www.facebook.com/business/help/975570072950669>`_." msgstr "" +"更多信息，请参阅 `Meta 关于广告限制的文档 " +"<https://www.facebook.com/business/help/975570072950669>`_。" #: ../../content/applications/productivity/whatsapp.rst:161 msgid "Add a WhatsApp product to the app" -msgstr "" +msgstr "在应用程序中添加 WhatsApp 产品" #: ../../content/applications/productivity/whatsapp.rst:163 msgid "" @@ -9236,18 +9732,21 @@ msgid "" "navigating to `<https://developers.facebook.com/apps>`_, and clicking on the" " app that is being configured." msgstr "" +"应用程序的基本结构已经创建，现在需要向应用程序添加产品。首先访问 Meta 应用程序仪表板，方法是导航到 " +"`<https://developers.facebook.com/apps>`_，然后单击正在配置的应用程序。" #: ../../content/applications/productivity/whatsapp.rst:167 msgid "" "On the next page: since WhatsApp will be used, click :guilabel:`Set up` next" " to the box containing WhatsApp, located towards the bottom of the page." -msgstr "" +msgstr "下一页：由于将使用 WhatsApp，请单击页面底部包含 WhatsApp 的方框旁边的 :guilabel:`设置`。" #: ../../content/applications/productivity/whatsapp.rst:171 msgid "" "`Meta's WhatsApp developer documentation " "<https://developers.facebook.com/docs/whatsapp/>`_." msgstr "" +"`Meta's WhatsApp 开发者文档 <https://developers.facebook.com/docs/whatsapp/>`_。" #: ../../content/applications/productivity/whatsapp.rst:173 msgid "" @@ -9256,22 +9755,24 @@ msgid "" "to be configured for the :guilabel:`Select a Meta Business Account` option, " "and then click :guilabel:`Continue` to confirm the selection." msgstr "" +"然后页面会跳转到 :guilabel:`WhatsApp 企业平台 API` 的配置页面。使用下拉菜单在 :guilabel:`选择 Meta " +"企业账户` 选项中选择要配置的 Meta 业务，然后点击 :guilabel:`继续` 确认选择。" #: ../../content/applications/productivity/whatsapp.rst:178 msgid "" "When :guilabel:`Continue` is clicked, the administrator agrees to Meta's " "terms and conditions as linked on the :guilabel:`Meta App Dashboard`." -msgstr "" +msgstr "点击 :guilabel:`继续`，管理员同意 :guilabel:`Meta 应用程序仪表板`上链接的 Meta 条款和条件。" #: ../../content/applications/productivity/whatsapp.rst:182 msgid "" "Once the WhatsApp product is added to the app, Meta will provide a WhatsApp " "test phone number with 5 test messages." -msgstr "" +msgstr "在应用程序中添加 WhatsApp 产品后，Meta 将提供一个 WhatsApp 测试电话号码和 5 条测试消息。" #: ../../content/applications/productivity/whatsapp.rst:186 msgid "Start using the WhatsApp API" -msgstr "" +msgstr "开始使用 WhatsApp API" #: ../../content/applications/productivity/whatsapp.rst:188 msgid "" @@ -9281,12 +9782,14 @@ msgid "" "begin configuring the WhatsApp API by adding a phone number and then sending" " an initial test message." msgstr "" +"完成之前的 WhatsApp 产品向导并点击 :guilabel:`继续` 后，浏览器应会跳转至 WhatsApp :guilabel:`快速入门` " +"页面；在该 :guilabel:`快速入门` 页面上，您可以添加电话号码并发送初始测试消息，从而开始配置 WhatsApp API。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" "Navigating to the WhatsApp quickstart wizard in Meta for Developer " "dashboard." -msgstr "" +msgstr "在 Meta 开发者模式仪表板中导航到 WhatsApp 快速入门向导。" #: ../../content/applications/productivity/whatsapp.rst:198 msgid "" @@ -9295,6 +9798,9 @@ msgid "" "that is being configured, (the app name is `Odoo` if the instructions above " "were followed)." msgstr "" +"如果浏览器不在 WhatsApp 的 :guilabel:`快速启动` 页面上，请导航至 " +"`<https://developers.facebook.com/apps>`_，然后点击正在配置的应用程序（如果按照上述说明操作，则应用程序名称为 " +"`Odoo`）。" #: ../../content/applications/productivity/whatsapp.rst:202 msgid "" @@ -9302,28 +9808,30 @@ msgid "" "(menu toggle)` icon next to the :guilabel:`WhatsApp` section heading. A " "small menu will open, containing the following options:" msgstr "" +"然后，在页面左侧的菜单中，点击 :guilabel:`v（菜单切换）` 图标，该图标位于 :guilabel:`WhatsApp` " +"部分标题旁边。将打开一个小菜单，其中包含以下选项：" #: ../../content/applications/productivity/whatsapp.rst:206 msgid ":guilabel:`Quickstart`" -msgstr "" +msgstr ":guilabel:`快速入门`" #: ../../content/applications/productivity/whatsapp.rst:207 msgid ":guilabel:`API Setup`" -msgstr "" +msgstr ":guilabel:`API 设置`" #: ../../content/applications/productivity/whatsapp.rst:208 msgid ":guilabel:`Configuration`" -msgstr "" +msgstr ":guilabel:`配置`" #: ../../content/applications/productivity/whatsapp.rst:210 msgid "" "Click the :guilabel:`Quickstart` option, and then click :guilabel:`Start " "using the API`." -msgstr "" +msgstr "单击 :guilabel:`快速启动` 选项，然后单击 :guilabel:`开始使用 API`。" #: ../../content/applications/productivity/whatsapp.rst:213 msgid "API Setup" -msgstr "" +msgstr "API 设置" #: ../../content/applications/productivity/whatsapp.rst:215 msgid "" @@ -9334,6 +9842,9 @@ msgid "" "messages` and click the drop-down menu next to :guilabel:`To`, under " ":guilabel:`Step 1 Select phone numbers`." msgstr "" +"点击 :guilabel:`开始使用 API` 后，页面将导航至 :guilabel:`API 设置`。现在测试号码已经创建，可以发送测试消息以确认 " +"WhatsApp 工作正常。要开始，请导航到页面上标有 :guilabel:`发送和接收消息` 的部分，然后单击 :guilabel:` To` " +"旁边的下拉菜单，在 :guilabel:`第 1 步 选择电话号码` 下方。" #: ../../content/applications/productivity/whatsapp.rst:221 msgid "" @@ -9342,6 +9853,8 @@ msgid "" "to. After entering the appropriate country code and phone number, click on " ":guilabel:`Next`." msgstr "" +"现在，选择唯一可用的选项：:guilabel:`管理电话号码列表`。按照步骤操作，最多添加五个号码以发送免费测试信息。输入相应的国家代码和电话号码后，点击" +" :guilabel:`下一步`。" #: ../../content/applications/productivity/whatsapp.rst:226 msgid "" @@ -9349,6 +9862,7 @@ msgid "" "test to be sent by the terminal. This is critical to ensure the WhatsApp " ":abbr:`API (Application Programming Interface)` is working." msgstr "" +"在此步骤中添加要发送的电话号码，将允许终端发送成功的测试。这对于确保 WhatsApp :abbr:`API（应用程序编程接口）` 正常工作至关重要。" #: ../../content/applications/productivity/whatsapp.rst:230 msgid "" @@ -9357,10 +9871,12 @@ msgid "" "number. Enter the verification code and click :guilabel:`Next` to verify the" " number." msgstr "" +"然后，WhatsApp 企业版会发送验证码，您需要在下一界面输入验证码，以验证号码的所有权。输入验证码并点击 :guilabel:`下一步` " +"以验证号码。" #: ../../content/applications/productivity/whatsapp.rst:235 msgid "Send a test message via terminal" -msgstr "" +msgstr "通过终端发送测试信息" #: ../../content/applications/productivity/whatsapp.rst:237 msgid "" @@ -9369,16 +9885,18 @@ msgid "" "Message`. A test message will then be sent to the phone number that was set " "in the previous section." msgstr "" +"接下来，通过终端发送测试消息。在标有 :guilabel:`第 2 步 使用应用程序接口发送信息` 的部分下，单击 " +":guilabel:`发送信息`。然后，一条测试信息将发送到上一节中设置的电话号码。" #: ../../content/applications/productivity/whatsapp.rst:241 msgid "" "Upon successfully receiving the message to the number, move onto the next " "section to produce and configure webhooks." -msgstr "" +msgstr "在成功接收到发送到号码的信息后，进入下一部分，制作和配置网络钩子。" #: ../../content/applications/productivity/whatsapp.rst:247 msgid "WhatsApp configuration in Odoo" -msgstr "" +msgstr "在 Odoo 中配置 WhatsApp" #: ../../content/applications/productivity/whatsapp.rst:249 msgid "" @@ -9389,6 +9907,8 @@ msgid "" "then used to configure the webhooks (in order to receive messages back into " "the database)." msgstr "" +"本节中配置的下一步全部在 Odoo 数据库中进行。需要在 Odoo 中为令牌、电话号码和账户 ID 配置几个不同的值；这些值对于创建 " +":guilabel:`URL 回调` 和 :guilabel:`网络钩子验证令牌` 必不可少，然后这些值将用于配置网络钩子（以便将消息接收回数据库）。" #: ../../content/applications/productivity/whatsapp.rst:254 msgid "" @@ -9396,6 +9916,8 @@ msgid "" "WhatsApp Business Accounts`. Then click :guilabel:`New` to configure the " "WhatsApp business account in Odoo." msgstr "" +"在 Odoo 中，导航至 :menuselection:`WhatsApp 应用程序 --> 配置 --> WhatsApp 企业帐户`。然后点击 " +":guilabel:`新建` 在 Odoo 中配置 WhatsApp 企业账户。" #: ../../content/applications/productivity/whatsapp.rst:257 msgid "" @@ -9404,6 +9926,8 @@ msgid "" " API Configuration`, and then copy the following values from the Meta " "developer console into the corresponding fields in Odoo:" msgstr "" +"在另一个浏览器选项卡中，导航至 :menuselection:`https://developers.facebook.com --> 我的应用程序 " +"--> WhatsApp --> API 配置`，然后将 Meta 开发者控制台中的以下值复制到 Odoo 中的相应字段：" #: ../../content/applications/productivity/whatsapp.rst:265 #: ../../content/applications/productivity/whatsapp.rst:669 @@ -9412,11 +9936,11 @@ msgstr "名称" #: ../../content/applications/productivity/whatsapp.rst:266 msgid "Meta Console" -msgstr "" +msgstr "Meta 控制台" #: ../../content/applications/productivity/whatsapp.rst:267 msgid "Odoo Interface" -msgstr "" +msgstr "Odoo 界面" #: ../../content/applications/productivity/whatsapp.rst:268 msgid "Phone" @@ -9424,11 +9948,11 @@ msgstr "电话" #: ../../content/applications/productivity/whatsapp.rst:269 msgid ":guilabel:`Phone number ID`" -msgstr "" +msgstr ":guilabel:`电话号码 ID`" #: ../../content/applications/productivity/whatsapp.rst:270 msgid ":guilabel:`Phone Number ID`" -msgstr "" +msgstr ":guilabel:`电话号码 ID`" #: ../../content/applications/productivity/whatsapp.rst:271 msgid "Token" @@ -9436,11 +9960,11 @@ msgstr "令牌" #: ../../content/applications/productivity/whatsapp.rst:272 msgid ":guilabel:`Temporary access token`" -msgstr "" +msgstr ":guilabel:`临时访问令牌`" #: ../../content/applications/productivity/whatsapp.rst:273 msgid ":guilabel:`Access Token`" -msgstr "" +msgstr ":guilabel:`访问令牌`" #: ../../content/applications/productivity/whatsapp.rst:274 msgid "App ID" @@ -9449,7 +9973,7 @@ msgstr "App ID" #: ../../content/applications/productivity/whatsapp.rst:275 #: ../../content/applications/productivity/whatsapp.rst:276 msgid ":guilabel:`App ID`" -msgstr "" +msgstr ":guilabel:`应用程序 ID`" #: ../../content/applications/productivity/whatsapp.rst:277 msgid "Account ID" @@ -9457,11 +9981,11 @@ msgstr "帐户ID" #: ../../content/applications/productivity/whatsapp.rst:278 msgid ":guilabel:`WhatsApp Business Account ID`" -msgstr "" +msgstr ":guilabel:`WhatsApp 企业账户 ID`" #: ../../content/applications/productivity/whatsapp.rst:279 msgid ":guilabel:`Account ID`" -msgstr "" +msgstr ":guilabel:`账户 ID`" #: ../../content/applications/productivity/whatsapp.rst:281 msgid "" @@ -9470,6 +9994,9 @@ msgid "" "Odoo is being configured in. Then in the left-side menu, under " ":guilabel:`App settings`, select :guilabel:`Basic`." msgstr "" +"要检索 :guilabel:`应用程序密钥`，请导航至 Meta " +"开发者控制台，`<https://developers.facebook.com/apps>`_ 并选择正在配置 Odoo 的应用程序。然后在左侧菜单的" +" :guilabel:`App 设置` 下选择 :guilabel:`基本`。" #: ../../content/applications/productivity/whatsapp.rst:285 msgid "" @@ -9479,6 +10006,9 @@ msgid "" "field on the Odoo :guilabel:`WhatsApp Business Account` configuration " "dashboard." msgstr "" +"接下来，单击字段 :guilabel:`应用程序密钥` 旁边的 :guilabel:`显示`，然后输入账户密码以验证所有权。复制 " +":guilabel:`应用程序密钥` 并将复制的值粘贴到 Odoo :guilabel:`WhatsApp 企业账户`配置仪表板上的 " +":guilabel:`应用程序密钥` 字段。" #: ../../content/applications/productivity/whatsapp.rst:290 msgid "" @@ -9487,10 +10017,11 @@ msgid "" "the upper-right corner of the dashboard if the configuration is set " "correctly." msgstr "" +"要在 Odoo 中完成 WhatsApp 企业账户的设置，请单击 :guilabel:`测试连接`。如果配置设置正确，仪表板右上角会弹出绿色的成功消息。" #: ../../content/applications/productivity/whatsapp.rst:295 msgid "Configuring webhooks" -msgstr "" +msgstr "配置网络钩子" #: ../../content/applications/productivity/whatsapp.rst:297 msgid "" @@ -9501,6 +10032,10 @@ msgid "" "Finally go to the section marked :guilabel:`Step 3: Configure webhooks to " "receive messages` and click on :guilabel:`Configure webhooks`." msgstr "" +"要在 Odoo 中配置 WhatsApp 的网络钩子，请导航至 " +"`<https://developers.facebook.com/apps>`_，然后选择正在配置 Odoo 的应用程序。然后在屏幕左侧的 " +":guilabel:`WhatsApp` 菜单标题下，点击 :guilabel:`API 设置` 菜单项。最后进入标有 :guilabel:`第 3 " +"步：配置网络钩子以接收信息` 的部分，点击 :guilabel:`配置网络钩子`。" #: ../../content/applications/productivity/whatsapp.rst:304 msgid "" @@ -9508,10 +10043,12 @@ msgid "" "`<https://developers.facebook.com/apps>`_ and select the app that Odoo is " "being configured in. Then select :guilabel:`Webhooks` in the left hand menu." msgstr "" +"另一种配置 *网络钩子* 的方法是导航至 `<https://developers.facebook.com/apps>`_，然后选择正在配置 Odoo" +" 的应用程序。然后在左侧菜单中选择 :guilabel:`网络钩子`。" #: ../../content/applications/productivity/whatsapp.rst:0 msgid "Manually navigating to the Whatsapp webhooks configuration." -msgstr "" +msgstr "手动导航到 Whatsapp 网络钩子配置。" #: ../../content/applications/productivity/whatsapp.rst:312 msgid "" @@ -9519,6 +10056,8 @@ msgid "" ":guilabel:`Edit`, where both the :guilabel:`Callback URL` and " ":guilabel:`Webhook Verify Token` values from the Odoo will be added." msgstr "" +"在:menuselection:`网络钩子配置`页面，点击:guilabel:`编辑`，其中将添加来自 Odoo 的 :guilabel:`URL " +"回调` 和 :guilabel:`Webhook 验证令牌` 值。" #: ../../content/applications/productivity/whatsapp.rst:316 msgid "" @@ -9526,6 +10065,8 @@ msgid "" "values were automatically populated after clicking on :guilabel:`Test " "Connection` in the previous step." msgstr "" +"在上一步中点击 :guilabel:`测试连接` 后，:guilabel:`URL 回调` 和 :guilabel:`网络钩子验证令牌` " +"值均已自动填充。" #: ../../content/applications/productivity/whatsapp.rst:319 msgid "" @@ -9534,6 +10075,8 @@ msgid "" "Business Accounts` and select the account that is being configured. Locate " "the values under the section labeled :guilabel:`Receiving Messages`." msgstr "" +"在一个单独的浏览器窗口中，通过导航至 :menuselection:`WhatsApp 应用程序--> 配置--> WhatsApp " +"企业账户`并选择正在配置的账户，在 Odoo 中检索必要的值。找到标有 :guilabel:`接收信息` 部分下的值。" #: ../../content/applications/productivity/whatsapp.rst:324 msgid "" @@ -9542,16 +10085,18 @@ msgid "" ":guilabel:`Webhook Verify Token` into the :guilabel:`Verify Token` field on " "the Meta developer console, as well." msgstr "" +"将 Odoo 中的 :guilabel:`URL 回调` 复制并粘贴到 Meta 中的 :guilabel:`URL 回调` 字段。同样，将 " +":guilabel:`网络钩子验证令牌` 复制并粘贴到 Meta 开发者控制台的 :guilabel:`验证令牌` 字段中。" #: ../../content/applications/productivity/whatsapp.rst:328 msgid "" "Finally, click :guilabel:`Verify and save` to record the values in the Meta " "developer console." -msgstr "" +msgstr "最后，单击 :guilabel:`验证并保存` 在 Meta 开发者控制台中记录数值。" #: ../../content/applications/productivity/whatsapp.rst:331 msgid "Webhook fields" -msgstr "" +msgstr "网络钩子字段" #: ../../content/applications/productivity/whatsapp.rst:333 msgid "" @@ -9560,40 +10105,42 @@ msgid "" "pop-up window appears, check the boxes in the :guilabel:`Subscribe` column " "for the following *field names*:" msgstr "" +"现在，在 Meta 开发人员控制台的 :guilabel:`网络钩子字段` 部分输入各个网络钩子字段。单击 " +":guilabel:`管理`，在弹出窗口中勾选 :guilabel:`订阅` 列中的以下*字段名称*：" #: ../../content/applications/productivity/whatsapp.rst:337 msgid "account_update" -msgstr "" +msgstr "account_update" #: ../../content/applications/productivity/whatsapp.rst:338 msgid "message_template_quality_update" -msgstr "" +msgstr "message_template_quality_update" #: ../../content/applications/productivity/whatsapp.rst:339 msgid "message_template_status_update" -msgstr "" +msgstr "message_template_status_update" #: ../../content/applications/productivity/whatsapp.rst:340 msgid "messages" -msgstr "" +msgstr "消息" #: ../../content/applications/productivity/whatsapp.rst:341 msgid "template_category_update" -msgstr "" +msgstr "template_category_update" #: ../../content/applications/productivity/whatsapp.rst:343 msgid "After making the selections, click :guilabel:`Done`." -msgstr "" +msgstr "选择后，点击 :guilabel:`已完成`。" #: ../../content/applications/productivity/whatsapp.rst:345 msgid "" "The finished :guilabel:`Webhooks` configuration will appear like this in the" " Meta developer console:" -msgstr "" +msgstr "已完成的:guilabel:`网络钩子` 配置将在 Meta 开发者控制台中显示如下：" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "WhatsApp webhooks set in the Meta developer console." -msgstr "" +msgstr "在 Meta 开发者控制台中设置 WhatsApp 网络钩子。" #: ../../content/applications/productivity/whatsapp.rst:352 msgid "" @@ -9601,6 +10148,8 @@ msgid "" "confirmed using the :guilabel:`Callback URL` and :guilabel:`Webhook Verify " "Token`." msgstr "" +"只有使用 :guilabel:`URL 回调` 和 :guilabel:`网络钩子验证令牌` 确认订阅后，才会显示 " +":guilabel:`网络钩子`字段。" #: ../../content/applications/productivity/whatsapp.rst:356 msgid "" @@ -9611,7 +10160,7 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:360 msgid "Add phone number" -msgstr "" +msgstr "添加电话号码" #: ../../content/applications/productivity/whatsapp.rst:362 msgid "" @@ -9623,18 +10172,22 @@ msgid "" ":guilabel:`Step 5: Add a phone number`, and click on :guilabel:`Add phone " "number`." msgstr "" +"要在 Odoo 中配置 WhatsApp 使用的电话号码，请导航回 Meta 开发者控制台 " +"(`<https://developers.facebook.com/apps>`_)，并再次选择正在配置 Odoo 的应用程序。在屏幕左侧的 " +":guilabel:`WhatsApp` 菜单标题下，点击 :guilabel:`API 设置` 菜单项。在那里，转到标有:guilabel:`第 5 " +"步：添加电话号码`部分，然后点击:guilabel:`添加电话号码`。" #: ../../content/applications/productivity/whatsapp.rst:368 msgid "" "In the fields, enter a :guilabel:`Business name` as well as a " ":guilabel:`Business website or profile page`." -msgstr "" +msgstr "在字段中输入 :guilabel:`企业名称`以及 :guilabel:`企业网站或简介页面`。" #: ../../content/applications/productivity/whatsapp.rst:372 msgid "" "The :guilabel:`Business website or profile page` field can be a social media" " page's :abbr:`URL (Uniform Resource Locator)`." -msgstr "" +msgstr ":guilabel:`企业网站或简介页面`字段可以是社交媒体页面的:abbr:`URL（统一资源定位符）`。" #: ../../content/applications/productivity/whatsapp.rst:375 msgid "" @@ -9644,28 +10197,31 @@ msgid "" "information is optional. After adding the location, click :guilabel:`Next` " "to continue." msgstr "" +"从 :guilabel:`国家/地区` " +"部分的下拉菜单中选择公司开展业务的国家/地区，完成填写企业信息。如需要，可添加地址，但此信息为可选项。添加地点后，单击 :guilabel:`下一步` " +"继续。" #: ../../content/applications/productivity/whatsapp.rst:380 msgid "" "The following page contains information for the :guilabel:`WhatsApp Business" " profile`. Complete the following sections, accordingly:" -msgstr "" +msgstr "以下页面包含 :guilabel:`WhatsApp 企业简介`的信息。请相应填写以下部分：" #: ../../content/applications/productivity/whatsapp.rst:383 msgid ":guilabel:`WhatsApp Business Profile Display Name`" -msgstr "" +msgstr ":guilabel:`WhatsApp 企业简介显示名称`" #: ../../content/applications/productivity/whatsapp.rst:384 msgid ":guilabel:`Timezone`" -msgstr "" +msgstr ":guilabel:`时区`" #: ../../content/applications/productivity/whatsapp.rst:385 msgid ":guilabel:`Category`" -msgstr "" +msgstr ":guilabel:`类别` " #: ../../content/applications/productivity/whatsapp.rst:386 msgid ":guilabel:`Business description` (optional)" -msgstr "" +msgstr ":guilabel:`企业简介`（可选）" #: ../../content/applications/productivity/whatsapp.rst:388 msgid "" @@ -9674,6 +10230,8 @@ msgid "" "WhatsApp` in the respective field. Here, enter the phone number to configure" " in WhatsApp." msgstr "" +"完成这些部分后，点击 :guilabel:`下一步`。页面会刷新，然后提示管理员在相应字段中，:guilabel:`为 WhatsApp " +"添加电话号码`。在此输入要在 WhatsApp 中配置的电话号码。" #: ../../content/applications/productivity/whatsapp.rst:393 msgid "" @@ -9681,6 +10239,9 @@ msgid "" "<https://developers.facebook.com/docs/whatsapp/cloud-api/get-" "started/migrate-existing-whatsapp- number-to-a-business-account>`_." msgstr "" +"`将现有 WhatsApp 号码迁移到企业账户 " +"<https://developers.facebook.com/docs/whatsapp/cloud-api/get-" +"started/migrate-existing-whatsapp- number-to-a-business-account>`_。" #: ../../content/applications/productivity/whatsapp.rst:397 msgid "" @@ -9688,6 +10249,8 @@ msgid "" ":guilabel:`Text message` or :guilabel:`Phone call`, and then click " ":guilabel:`Next` proceed." msgstr "" +"接下来，选择电话号码的验证方法。选择 :guilabel:`文字短信` 或 :guilabel:`语音电话`，然后点击 :guilabel:`下一步` " +"继续。" #: ../../content/applications/productivity/whatsapp.rst:400 msgid "" @@ -9696,6 +10259,8 @@ msgid "" "that verification code into the :guilabel:`Verification code` field and " "click :guilabel:`Next` to finish." msgstr "" +"输入的电话号码将收到 WhatsApp 发送的短信或电话，其中包含一个验证码（取决于所选的验证方法）。在 :guilabel:`验证码` " +"字段中输入验证码，然后点击 :guilabel:`下一步` 完成。" #: ../../content/applications/productivity/whatsapp.rst:405 msgid "" @@ -9706,6 +10271,9 @@ msgid "" " This is part of Meta's fraud detection system, in order to ensure that the " "account/company are real a payment method is required to proceed." msgstr "" +"如果尚未添加付款方式，则必须这样做。请访问 Meta 的文档，了解如何在 Meta " +"的业务管理<https://www.facebook.com/business/help/915454841921082?id=180505742745347>`_中添加付款方式。这是" +" Meta 欺诈检测系统的一部分，为了确保账户/公司的真实性，需要提供支付方式才能继续进行。" #: ../../content/applications/productivity/whatsapp.rst:412 msgid "" @@ -9713,16 +10281,18 @@ msgid "" "<https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/add-a-" "phone-number>`_." msgstr "" +"`Meta 开发者模式： 添加电话号码 <https://developers.facebook.com/docs/whatsapp/cloud-" +"api/get-started/add-a-phone-number>`_。" #: ../../content/applications/productivity/whatsapp.rst:418 msgid "Permanent token" -msgstr "" +msgstr "永久令牌" #: ../../content/applications/productivity/whatsapp.rst:420 msgid "" "After configuration and testing are complete, a permanent token should be " "created to replace the :guilabel:`Temporary token`." -msgstr "" +msgstr "配置和测试完成后，应创建一个永久令牌来替换 :guilabel:`临时令牌` 。" #: ../../content/applications/productivity/whatsapp.rst:424 msgid "" @@ -9730,6 +10300,9 @@ msgid "" "<https://developers.facebook.com/docs/whatsapp/business-management-api/get-" "started#system-user- access-tokens>`_." msgstr "" +"`Meta 开发者模式： 系统用户访问令牌 " +"<https://developers.facebook.com/docs/whatsapp/business-management-api/get-" +"started#system-user- access-tokens>`_。" #: ../../content/applications/productivity/whatsapp.rst:428 msgid "" @@ -9738,12 +10311,14 @@ msgid "" "existing system user or create a new system user by clicking on " ":guilabel:`Add`." msgstr "" +"首先导航到 `<https://business.facebook.com/>`_，然后转到 :menuselection:`业务设置 --> 用户 " +"--> 系统用户`。选择一个现有的系统用户，或点击 :guilabel:`添加` 创建一个新的系统用户。" #: ../../content/applications/productivity/whatsapp.rst:432 msgid "" "Assets now must be added to the system user and then a permanent token can " "be generated." -msgstr "" +msgstr "现在必须将资产添加到系统用户，然后才能生成永久令牌。" #: ../../content/applications/productivity/whatsapp.rst:434 msgid "" @@ -9755,6 +10330,9 @@ msgid "" "addition of the asset to the system user. Finish by clicking " ":guilabel:`Done`." msgstr "" +"点击 :guilabel:`添加资产`，在弹出窗口中选择 :guilabel:`选择资产类型`下的 :guilabel:`应用程序`。然后，选择 " +"Odoo 应用程序，并在 :guilabel:`完全控制` 选项下将权限切换为 *开启*。点击 " +":guilabel:`保存更改`设置新的权限，此时会出现一个确认窗口，确认已将资产添加到系统用户。点击 :guilabel:`完成`。" #: ../../content/applications/productivity/whatsapp.rst:440 msgid "" @@ -9764,26 +10342,28 @@ msgid "" "Then determine the expiration date of either :guilabel:`60 days` or " ":guilabel:`Never`." msgstr "" +"接下来，将生成永久令牌。点击 :guilabel:`生成新令牌`，弹出窗口会询问应为哪个应用程序生成此令牌。选择此令牌的 " +":guilabel:`应用程序`。然后确定到期日期，可选择:guilabel:`60 天` 或 :guilabel:`永不`。" #: ../../content/applications/productivity/whatsapp.rst:445 msgid "" "Finally, when Meta asks which permissions should the system user allow, add " "all of the following permissions:" -msgstr "" +msgstr "最后，当 Meta 询问系统用户应允许哪些权限时，请添加以下所有权限：" #: ../../content/applications/productivity/whatsapp.rst:448 msgid "WhatsApp_business_messaging" -msgstr "" +msgstr "WhatsApp_business_messaging" #: ../../content/applications/productivity/whatsapp.rst:449 msgid "WhatsApp_business_management" -msgstr "" +msgstr "WhatsApp_business_management" #: ../../content/applications/productivity/whatsapp.rst:451 msgid "" "When permissions are set, click :guilabel:`Generate token`. Copy the token " "value that populates on the screen that follows." -msgstr "" +msgstr "权限设置完成后，点击 :guilabel:`生成令牌`。复制随后屏幕上弹出的令牌值。" #: ../../content/applications/productivity/whatsapp.rst:454 msgid "" @@ -9791,6 +10371,8 @@ msgid "" "WhatsApp business account in Odoo by navigating to :menuselection:`WhatsApp " "app --> Configuration --> WhatsApp Business Accounts`." msgstr "" +"使用该令牌值，通过导航至:menuselection:`WhatsApp 应用程序--> 配置--> WhatsApp 企业账户`，更新 Odoo 中 " +"WhatsApp 企业账户的 :guilabel:`访问令牌` 字段。" #: ../../content/applications/productivity/whatsapp.rst:459 msgid "Go live with the Meta app" @@ -9821,6 +10403,10 @@ msgid "" ":guilabel:`Privacy Policy URL` field of the form. Click :guilabel:`Save " "changes` to apply the privacy policy to the app." msgstr "" +"必须设置隐私政策 URL 才能将应用程序设置为启用。进入 Meta " +"开发者控制台`<https://developers.facebook.com/apps>`_，选择正在配置 Odoo " +"的应用程序。然后，使用屏幕左侧的菜单，转到 :menuselection:`应用程序设置 --> 基础`。然后，在表单的 :guilabel:`隐私政策" +" URL` 字段中输入隐私政策超链接地址。单击 :guilabel:`保存更改` 将隐私政策应用到应用程序。" #: ../../content/applications/productivity/whatsapp.rst:478 msgid "" @@ -9830,14 +10416,14 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:484 msgid "WhatsApp templates" -msgstr "" +msgstr "WhatsApp 模板" #: ../../content/applications/productivity/whatsapp.rst:486 msgid "" "WhatsApp templates are saved messages that are used repeatedly to send " "messages from the database. They allow users to send quality communications," " without having to compose the same text repeatedly." -msgstr "" +msgstr "WhatsApp 模板是已保存的信息，可用于重复发送数据库中的信息。用户无需重复编写相同的文本，即可发送高质量的通信。" #: ../../content/applications/productivity/whatsapp.rst:489 msgid "" @@ -9851,23 +10437,23 @@ msgid "" "WhatsApp templates can be created on both the Odoo and Meta consoles. The " "following process will overview the process for creating templates in Odoo " "and then afterward in Meta." -msgstr "" +msgstr "WhatsApp 模板可在 Odoo 和 Meta 控制台上创建。下面将概述在 Odoo 和 Meta 中创建模板的过程。" #: ../../content/applications/productivity/whatsapp.rst:497 msgid "" "WhatsApp has an approval process that must be completed before the template " "can be used. :ref:`productivity/whatsapp/approval`." -msgstr "" +msgstr "WhatsApp 有审批流程，在使用模板之前必须完成该流程。:ref:`productivity/whatsapp/approval`。" #: ../../content/applications/productivity/whatsapp.rst:503 msgid "Creating templates in Odoo" -msgstr "" +msgstr "在 Odoo 中创建模板" #: ../../content/applications/productivity/whatsapp.rst:505 msgid "" "To access and create WhatsApp templates, begin by navigating to the " ":menuselection:`WhatsApp app --> Templates` dashboard." -msgstr "" +msgstr "要访问和创建 WhatsApp 模板，首先要导航到 :menuselection:`WhatsApp 应用程序-->模板`仪表板。" #: ../../content/applications/productivity/whatsapp.rst:508 msgid "" @@ -9875,6 +10461,8 @@ msgid "" ":guilabel:`Body`, :guilabel:`Buttons`, and :guilabel:`Variables`; these " "three tabs combined create the WhatsApp template." msgstr "" +"在单个模板表单的底部，有三个标签：:guilabel:`正文`、:guilabel:`按钮`和:guilabel:`变量`；这三个标签组合起来就形成了 " +"WhatsApp 模板。" #: ../../content/applications/productivity/whatsapp.rst:512 msgid "" @@ -9884,6 +10472,8 @@ msgid "" "placeholders) in the message (body) is specifically called out and specified" " in the :guilabel:`Variables` tab." msgstr "" +"文本输入到 :guilabel:`正文` 选项卡，在 :guilabel:`正文` 选项卡中调用的动态内容在 :guilabel:`变量` " +"选项卡中指定。信息（正文）中的每个动态内容（如占位符）都会在 :guilabel:`变量` 标签中具体调用和指定。" #: ../../content/applications/productivity/whatsapp.rst:517 msgid "" @@ -9894,6 +10484,7 @@ msgid "" " user's name, call out specific products, or reference a sales order, to " "name a few convenient and impactful variables." msgstr "" +"模板是预制的布局，用户可以利用它向客户发送专业信息。模板能够包含动态数据，这些数据将使用模板配置中设置的变量，填充到最终信息中。例如，信息中可以包含最终用户的姓名、提及特定产品或销售订单等方便而有影响力的变量。" #: ../../content/applications/productivity/whatsapp.rst:523 msgid "" @@ -9901,6 +10492,8 @@ msgid "" "Templates` dashboard and click :guilabel:`New`. On the form, enter a " ":guilabel:`Name` for the template, and select a :guilabel:`Language`." msgstr "" +"要创建 WhatsApp 模板，请进入 :menuselection:`WhatsApp 应用程序-->模板`仪表板并点击 " +":guilabel:`新建`。在表单上输入模板的 :guilabel:`名称`，并选择 :guilabel:`语言`。" #: ../../content/applications/productivity/whatsapp.rst:528 msgid "" @@ -9908,6 +10501,8 @@ msgid "" "to edit the :guilabel:`Applies to` field. See this :doc:`access rights " "documentation <../general/users/access_rights>` for more information." msgstr "" +"要完成下一个任务，需要有管理员访问权限才能编辑 :guilabel:`适用于` 字段。请参阅 :doc:`访问权限文档 " +"<../general/users/access_rights>` 获取更多信息。" #: ../../content/applications/productivity/whatsapp.rst:532 msgid "" @@ -9916,6 +10511,8 @@ msgid "" ":guilabel:`Applies to` field select the *model* the server action will apply" " to for this template." msgstr "" +"在 :guilabel:`账户` 下拉菜单中，选择此模板应链接的*WhatsApp 企业账户*。接下来，在 :guilabel:`适用于` " +"字段下选择服务器操作将适用于该模板的*模型*。" #: ../../content/applications/productivity/whatsapp.rst:537 msgid "" @@ -9926,6 +10523,9 @@ msgid "" " in the backend. Search (using the front-end name) for this model in the " ":guilabel:`Applies to` drop-down menu in the WhatsApp template." msgstr "" +"这些模型也可在 :ref:`开发者模式<developer-mode>` 中访问。在联系表单（或 Odoo " +"中类似的相关表单）上，导航到要引用的模型，并将鼠标悬停在任何字段名称上。后台信息框将显示后台中特定的 Odoo :guilabel:`模型` 名称。在 " +"WhatsApp 模板的 :guilabel:`适用于` 下拉菜单中搜索（使用前端名称）该模型。" #: ../../content/applications/productivity/whatsapp.rst:544 msgid "" @@ -9933,6 +10533,8 @@ msgid "" ":guilabel:`Phone Field` may produce an error The :guilabel:`Phone Field` " "should always be set to the `Phone` or `Mobile` model." msgstr "" +"通常在更改模型或 :guilabel:`适用于` 字段时，:guilabel:`电话字段` 可能会产生错误 :guilabel:`电话字段` " +"应始终设置为`电话`或`手机`模型。" #: ../../content/applications/productivity/whatsapp.rst:548 msgid "" @@ -9941,6 +10543,8 @@ msgid "" "available fields for the model (:guilabel:`Applies to`) that the template is" " created for." msgstr "" +"要搜索可用字段，请在 :guilabel:`搜索...` " +"框中输入前端名称。这将从创建模板的模型（:guilabel:`适用于`）的所有可用字段中找到结果。" #: ../../content/applications/productivity/whatsapp.rst:553 msgid "" @@ -9948,10 +10552,12 @@ msgid "" "in the search results box. Use the :guilabel:`> (right chevron)` and " ":guilabel:`⬅️ (left arrow)` icons to navigate between the menu levels." msgstr "" +"要查找特定字段，可能需要在搜索结果框中浏览多个层级。使用 :guilabel:`>（右箭头）` 和 :guilabel:`⬅️（左箭头）` " +"图标在菜单层级之间导航。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "Searching for the phone field in the search bar." -msgstr "" +msgstr "在搜索栏中搜索电话字段。" #: ../../content/applications/productivity/whatsapp.rst:561 msgid "" @@ -9963,12 +10569,15 @@ msgid "" "set to :guilabel:`Utility` should there be general transactional messages " "being sent (i.e., sales order, event ticket, etc)." msgstr "" +"更改 :guilabel:`类别` 以适用于 :guilabel:`市场营销`, :guilabel:`实用工具`, 或 " +":guilabel:`身份验证` 类别。在大多数情况下，将使用前两个选项，除非用户希望发送密码重置或与安全相关的内容。如果要发送促销信息，请设置为 " +":guilabel:`营销'；如果要发送一般交易信息（如销售订单、活动门票等），请设置为 :guilabel:`实用'。" #: ../../content/applications/productivity/whatsapp.rst:568 msgid "" "Specifying an incorrect category can cause a flag/rejected status from Meta " "during the approval process." -msgstr "" +msgstr "指定不正确的类别可能会导致在审批过程中被 Meta 标记/拒绝。" #: ../../content/applications/productivity/whatsapp.rst:571 msgid "" @@ -9976,10 +10585,11 @@ msgid "" "right-side column, a :guilabel:`Header type` can be configured along with a " ":guilabel:`Header message`, as well." msgstr "" +"添加允许使用此模板的 :guilabel:` 用户`。在右侧栏中，可以配置 :guilabel:`标题类型` 和 :guilabel:`标题信息`。" #: ../../content/applications/productivity/whatsapp.rst:574 msgid "The available :guilabel:`Header types` are as follows:" -msgstr "" +msgstr "可用的 :guilabel:`标题类型`如下：" #: ../../content/applications/productivity/whatsapp.rst:576 msgid "Text" @@ -9999,20 +10609,20 @@ msgstr "文档" #: ../../content/applications/productivity/whatsapp.rst:580 msgid "Location (variables need to be set)" -msgstr "" +msgstr "位置（需要设置变量）" #: ../../content/applications/productivity/whatsapp.rst:582 msgid "" "Navigate to the :guilabel:`Body` tab to configure the main message of the " "template." -msgstr "" +msgstr "导航至 :guilabel:`正文` 选项卡，配置模板的主要信息。" #: ../../content/applications/productivity/whatsapp.rst:584 msgid "" "When all the necessary changes are made to the template, click on the " ":guilabel:`Submit for approval` button in the upper-left corner. This will " "cause the status of the template to change to :guilabel:`Pending`." -msgstr "" +msgstr "对模板进行所有必要更改后，点击左上角的 :guilabel:`提交审批` 按钮。这将使模板的状态变为 :guilabel:`待审批`。" #: ../../content/applications/productivity/whatsapp.rst:588 msgid "" @@ -10021,19 +10631,21 @@ msgid "" " template has been approved (or rejected). The templates will then need to " "be synced from the Odoo database." msgstr "" +"状态将保持为 :guilabel:`待审批`，直到 Meta 做出决定，然后将发送一封确认电子邮件，说明模板已被批准（或拒绝）。然后需要从 Odoo " +"数据库同步模板。" #: ../../content/applications/productivity/whatsapp.rst:592 msgid "" "See this section for more information on :ref:`syncing templates " "<productivity/whatsapp/sync>`." -msgstr "" +msgstr "有关 :ref:`同步模板 <productivity/whatsapp/sync>` 的更多信息，请参阅本节。" #: ../../content/applications/productivity/whatsapp.rst:595 msgid "" "There are pre-configured demo data templates available in Odoo to use or " "modify. These templates can be used as-is or modified to suit a specific " "business need." -msgstr "" +msgstr "Odoo 中有预配置的演示数据模板可供使用或修改。这些模板可按原样使用，也可根据具体业务需求进行修改。" #: ../../content/applications/productivity/whatsapp.rst:598 msgid "" @@ -10042,6 +10654,8 @@ msgid "" " Approval` to start the approval process. An email will be sent to the " "administrator of the Meta account when the template has been approved." msgstr "" +"要使用这些模板，请导航至 :menuselection:`WhatsApp 应用程序 --> 模板` 并选择一个预配置模板。单击 " +":guilabel:`提交审批` 开始审批流程。模板通过审批后，将向 Meta 账户的管理员发送电子邮件。" #: ../../content/applications/productivity/whatsapp.rst:603 msgid "Buttons" @@ -10056,6 +10670,9 @@ msgid "" "(including :guilabel:`Url Type`), depending on the :guilabel:`Type` of " "button." msgstr "" +"按钮可从 :guilabel:`按钮` " +"选项卡添加到信息中。输入:guilabel:`类型`（:guilabel:`访问网站`、:guilabel:`电话号码`或:guilabel:`快速回复`），然后根据按钮的:guilabel:`类型`指定:guilabel:`按钮文本`、:guilabel:`电话号码`或:guilabel:`网站" +" URL`（包括:guilabel:`Url 类型`）。" #: ../../content/applications/productivity/whatsapp.rst:611 msgid "" @@ -10064,10 +10681,13 @@ msgid "" "`<https://business.facebook.com/wa/manage/home>`_. Then go to " ":menuselection:`Account tools --> Message templates`." msgstr "" +"也可在 Meta 企业控制台添加按钮。通过导航至 " +"`<https://business.facebook.com/wa/manage/home>`_，查看 Meta 的 WhatsApp " +"模板仪表板。然后进入 :menuselection:`账户工具 --> 消息模板`。" #: ../../content/applications/productivity/whatsapp.rst:616 msgid "Using placeholders and variables" -msgstr "" +msgstr "使用占位符和变量" #: ../../content/applications/productivity/whatsapp.rst:618 msgid "" @@ -10076,6 +10696,8 @@ msgid "" "variables are encoded to display fields from within the database, " "referencing fields from within a model." msgstr "" +"使用模板时，动态变量会引用 Odoo 数据库中的某些字段，从而在 WhatsApp " +"消息中生成独特的数据。动态变量通过编码显示数据库中的字段，并引用模型中的字段。" #: ../../content/applications/productivity/whatsapp.rst:623 msgid "" @@ -10085,10 +10707,13 @@ msgid "" " For example, a customer's name can be referenced in the email from the " ":guilabel:`Customer` field on the :guilabel:`Sales Order` model." msgstr "" +"许多公司都喜欢在 WhatsApp 上定制个性化的客户信息，以吸引眼球。在 Odoo " +"中，可以通过设置动态变量引用模型中的字段来实现这一目的。例如，可在电子邮件中引用 :guilabel:`销售订单` 模型中 :guilabel:`客户`" +" 字段中的客户姓名。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "WhatsApp message with dynamic variables highlighted." -msgstr "" +msgstr "突出显示动态变量的 WhatsApp 消息。" #: ../../content/applications/productivity/whatsapp.rst:632 msgid "" @@ -10098,30 +10723,32 @@ msgid "" "`{{2}}` and increase incrementally as more placeholders are added to the " "text." msgstr "" +"通过在*文本*中添加 :guilabel:`占位符`，可在 :guilabel:`正文`中添加动态变量。要在 *消息正文* 中添加占位符，请输入以下文字" +" `{{1}}`。第二个占位符输入 `{{2}}`，并随着文本中占位符的增加而递增。" #: ../../content/applications/productivity/whatsapp.rst:637 msgid "*The following is the text from payment receipt template body:*" -msgstr "" +msgstr "*以下是付款收据模板正文中的文字：*" #: ../../content/applications/productivity/whatsapp.rst:639 msgid "Dear {{1}}," -msgstr "" +msgstr "尊敬的 {{1}}，" #: ../../content/applications/productivity/whatsapp.rst:0 msgid "Here is your invoice *{{2}}* from *{{3}}* for a total of *{{4}}{{5}}*." -msgstr "" +msgstr "这是您从*{{3}}*开具的*{{2}}*发票，总金额为*{{4}}{{5}}*。" #: ../../content/applications/productivity/whatsapp.rst:0 msgid "To review your invoice or pay online: {{6}}" -msgstr "" +msgstr "查看发票或在线支付： {{6}}" #: ../../content/applications/productivity/whatsapp.rst:644 msgid "Thank you" -msgstr "" +msgstr "谢谢！" #: ../../content/applications/productivity/whatsapp.rst:647 msgid ":ref:`productivity/whatsapp/templates`." -msgstr "" +msgstr ":ref:`productivity/whatsapp/templates`." #: ../../content/applications/productivity/whatsapp.rst:649 msgid "" @@ -10131,6 +10758,8 @@ msgid "" ":guilabel:`Field of Model`. This allows Odoo to reference a field within a " "model to produce unique data in the message being sent." msgstr "" +"这些占位符必须配置在模板的 :guilabel:`变量` 选项卡上，然后再提交 Meta 审批。要编辑模板上的动态变量，首先将 " +":guilabel:`类型` 更改为 :guilabel:`模型字段`。这将允许 Odoo 引用模型中的字段，从而在发送的消息中生成唯一数据。" #: ../../content/applications/productivity/whatsapp.rst:654 msgid "" @@ -10138,6 +10767,7 @@ msgid "" ":guilabel:`Applies to` field in the template should be edited prior to " "ensure the correct model and field are referenced." msgstr "" +"接下来，编辑动态变量的 :guilabel:`字段`。应先编辑模板中的 :guilabel:`适用于` 字段，以确保引用了正确的模型和字段。" #: ../../content/applications/productivity/whatsapp.rst:657 msgid "" @@ -10146,12 +10776,13 @@ msgid "" " the model (:guilabel:`Applies to`) that the template is created for. There " "may be multiple levels that need to be configured." msgstr "" +"要搜索可用字段，请在搜索框中输入字段的前端名称。这将从创建模板的模型（:guilabel:`适用于`）的所有可用字段中找到结果。可能有多个级别需要配置。" #: ../../content/applications/productivity/whatsapp.rst:662 msgid "" "The following is an example of the variables set for the above placeholders " "in the payment receipt noted above:" -msgstr "" +msgstr "以下是在上述付款收据中为上述占位符设置变量的示例：" #: ../../content/applications/productivity/whatsapp.rst:670 msgid "Sample Value" @@ -10167,11 +10798,11 @@ msgstr "字段" #: ../../content/applications/productivity/whatsapp.rst:673 msgid "body - {{1}}" -msgstr "" +msgstr "正文 - {{1}}" #: ../../content/applications/productivity/whatsapp.rst:674 msgid "Azure Interior" -msgstr "" +msgstr "Azure Interior" #: ../../content/applications/productivity/whatsapp.rst:675 #: ../../content/applications/productivity/whatsapp.rst:679 @@ -10183,23 +10814,23 @@ msgstr "模型领域" #: ../../content/applications/productivity/whatsapp.rst:676 msgid "`Partner`" -msgstr "" +msgstr "`合作伙伴`" #: ../../content/applications/productivity/whatsapp.rst:677 msgid "body - {{2}}" -msgstr "" +msgstr "正文 - {{2}}" #: ../../content/applications/productivity/whatsapp.rst:678 msgid "INV/2022/00001" -msgstr "" +msgstr "INV/2022/00001" #: ../../content/applications/productivity/whatsapp.rst:680 msgid "`Number`" -msgstr "" +msgstr "`数字`" #: ../../content/applications/productivity/whatsapp.rst:681 msgid "body - {{3}}" -msgstr "" +msgstr "正文 - {{3}}" #: ../../content/applications/productivity/whatsapp.rst:682 msgid "My Company" @@ -10207,43 +10838,43 @@ msgstr "我的公司" #: ../../content/applications/productivity/whatsapp.rst:684 msgid "`Company`" -msgstr "" +msgstr "`公司`" #: ../../content/applications/productivity/whatsapp.rst:685 msgid "body - {{4}}" -msgstr "" +msgstr "正文 - {{4}}" #: ../../content/applications/productivity/whatsapp.rst:686 msgid "$" -msgstr "" +msgstr "$" #: ../../content/applications/productivity/whatsapp.rst:688 msgid "`Currency > Symbol`" -msgstr "" +msgstr "`货币 > 符号`" #: ../../content/applications/productivity/whatsapp.rst:689 msgid "body - {{5}}" -msgstr "" +msgstr "正文 - {{5}}" #: ../../content/applications/productivity/whatsapp.rst:690 msgid "4000" -msgstr "" +msgstr "4000" #: ../../content/applications/productivity/whatsapp.rst:692 msgid "`Amount`" -msgstr "" +msgstr "`金额`" #: ../../content/applications/productivity/whatsapp.rst:693 msgid "body - {{6}}" -msgstr "" +msgstr "正文 - {{6}}" #: ../../content/applications/productivity/whatsapp.rst:694 msgid "\\https://.." -msgstr "" +msgstr "\\https://.." #: ../../content/applications/productivity/whatsapp.rst:695 msgid "Portal link" -msgstr "" +msgstr "门户链接" #: ../../content/applications/productivity/whatsapp.rst:699 msgid "" @@ -10253,14 +10884,17 @@ msgid "" "`{{1}}` should be configured to populate the `{{1}}` :guilabel:`Field` with " "the :guilabel:`Customer` name." msgstr "" +"例如，在 :guilabel:`正文` 选项卡中，如果输入以下内容：\"您好 {{{1}},\"，则必须在 :guilabel:`变量` 选项卡中设置 " +"`{{1}}`。在这种特定情况下，信息应按姓名问候客户，因此应配置`{{1}}`，使`{{1}}` :guilabel:`字段` 包含 " +":guilabel:`客户` 姓名。" #: ../../content/applications/productivity/whatsapp.rst:705 msgid "Customizing WhatsApp templates is out of the scope of Odoo Support." -msgstr "" +msgstr "定制 WhatsApp 模板不属于 Odoo 支持的范围。" #: ../../content/applications/productivity/whatsapp.rst:710 msgid "Meta template approval" -msgstr "" +msgstr "Meta 模板审批" #: ../../content/applications/productivity/whatsapp.rst:712 msgid "" @@ -10269,12 +10903,15 @@ msgid "" "Approval` to start the approval process. An email will be sent to the " "administrator of the Meta account when the template has been approved." msgstr "" +"更新模板上的动态变量后，模板需要再次提交给 Meta 进行审批。点击 :guilabel:`提交审批` 开始审批流程。模板通过审批后，Meta " +"账户管理员将收到一封电子邮件。" #: ../../content/applications/productivity/whatsapp.rst:716 msgid "" "Following the approval from Meta, sync the templates again in the Odoo " "database. See this documentation: :ref:`productivity/whatsapp/sync`." msgstr "" +"获得 Meta 批准后，在 Odoo 数据库中再次同步模板。请参阅此文档：:ref:`productivity/whatsapp/sync`。" #: ../../content/applications/productivity/whatsapp.rst:720 msgid "" @@ -10282,10 +10919,12 @@ msgid "" "`<https://business.facebook.com/wa/manage/home>`_. Then go to " ":menuselection:`Account tools --> Message templates`." msgstr "" +"要查看状态，请导航至 `<https://business.facebook.com/wa/manage/home>`_，进入 Meta 的 " +"WhatsApp 模板仪表板。然后进入 :menuselection:`账户工具 --> 消息模板`。" #: ../../content/applications/productivity/whatsapp.rst:727 msgid "Syncing templates" -msgstr "" +msgstr "同步模板" #: ../../content/applications/productivity/whatsapp.rst:729 msgid "" @@ -10297,18 +10936,21 @@ msgid "" "will update the templates that are approved so that they can be utilized " "with various apps in the database." msgstr "" +"模板经 Meta 团队批准后必须同步到 Odoo 数据库。要执行此操作，首先导航至 :menuselection:`WhatsApp 应用程序--> " +"配置--> WhatsApp 企业账户`，然后选择需要同步的配置。在标有 :menuselection:`发送信息` 的部分下，点击底部的 " +":guilabel:`同步模板`。Meta 将更新已批准的模板，以便它们可以与数据库中的各种应用程序一起使用。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" "Syncing Meta WhatsApp templates to the Odoo database, with the 'Sync Templates'\n" "highlighted." -msgstr "" +msgstr "将 Meta WhatsApp 模板同步到 Odoo 数据库，并突出显示 '同步模板'。" #: ../../content/applications/productivity/whatsapp.rst:741 msgid "" "A successful message in green appears in the upper-right corner with the " "number of templates updated." -msgstr "" +msgstr "右上角会出现绿色的成功信息，并显示更新的模板数量。" #: ../../content/applications/productivity/whatsapp.rst:745 msgid "" @@ -10317,10 +10959,12 @@ msgid "" " template to sync. Then, click on the :guilabel:`Sync Template` button " "located in the top menu of the template's form." msgstr "" +"也可以从模板本身单独同步模板。导航至 :menuselection:`WhatsApp " +"应用程序-->模板`仪表板并选择要同步的模板。然后，点击模板表单顶部菜单中的 :guilabel:`同步模板` 按钮。" #: ../../content/applications/productivity/whatsapp.rst:750 msgid "Creating templates in Meta" -msgstr "" +msgstr "在 Meta 中创建模板" #: ../../content/applications/productivity/whatsapp.rst:752 msgid "" @@ -10328,12 +10972,15 @@ msgid "" "<https://business.facebook.com/wa/manage/home>`_, and then go to " ":menuselection:`Account tools --> Message templates`." msgstr "" +"首先，导航到 `Meta 的 WhatsApp 模板仪表板 " +"<https://business.facebook.com/wa/manage/home>`_，然后转到 :menuselection:`账户工具 " +"--> 消息模板`。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" "Account tools highlighted in business manager with the manage templates link" " highlighted." -msgstr "" +msgstr "在业务管理器中突出显示账户工具，并突出显示管理模板链接。" #: ../../content/applications/productivity/whatsapp.rst:760 msgid "" @@ -10344,24 +10991,26 @@ msgid "" "used, unless the user would like to send a password reset or something " "security related." msgstr "" +"要创建 WhatsApp 模板，请点击蓝色的 :guilabel:`创建模板` 按钮，然后选择 :guilabel:`类别`。列出的选项包括 " +":guilabel:`市场营销`、:guilabel:`实用工具`和:guilabel:`身份验证`。大多数情况下会使用前两个选项，除非用户希望发送密码重置或与安全相关的内容。" #: ../../content/applications/productivity/whatsapp.rst:765 msgid "" "Enter the :guilabel:`Name` of the template and then select the " ":guilabel:`Language` for the template." -msgstr "" +msgstr "输入模板的 :guilabel:`名称`，然后选择模板的 :guilabel:`语言`。" #: ../../content/applications/productivity/whatsapp.rst:769 msgid "" "Multiple languages can be selected by typing the language name(s) and " "selecting the other languages as needed." -msgstr "" +msgstr "输入语言名称并根据需要选择其他语言，即可选择多种语言。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" "Template configuration options listed, with Marketing, Utility, Name and Language\n" "highlighted." -msgstr "" +msgstr "列出了模板配置选项，并突出显示了市场营销、实用工具、名称和语言。" #: ../../content/applications/productivity/whatsapp.rst:777 msgid "" @@ -10371,10 +11020,12 @@ msgid "" ":guilabel:`Buttons` are configured. To the right of the template is a " "preview of what the template will look like in production." msgstr "" +"做出适当选择后，点击右上角的 :guilabel:`继续`。页面将重定向到 :guilabel:`编辑模板` 页面。在此可配置 " +":guilabel:`标题`、:guilabel:`正文`、:guilabel:`页脚`和 :guilabel:`按钮`。模板右侧是生产中模板的预览。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "Edit the template using a header, body, footer and buttons." -msgstr "" +msgstr "使用页眉、正文、页脚和按钮编辑模板。" #: ../../content/applications/productivity/whatsapp.rst:786 msgid "" @@ -10384,6 +11035,8 @@ msgid "" "then another window appears stating that the template will be submitted to " "Meta for review and approval." msgstr "" +"对模板进行所有必要修改后，点击右上角的 :guilabel:`提交` 按钮。这时会出现一个确认窗口，点击 " +":guilabel:`确认`语言，然后会出现另一个窗口，说明模板将提交给 Meta 审查和批准。" #: ../../content/applications/productivity/whatsapp.rst:791 msgid "" @@ -10392,6 +11045,8 @@ msgid "" "received approving the template, the templates will need to be synced from " "within the Odoo database." msgstr "" +"模板:guilabel:`状态`将保持为 :guilabel:`审核中`，直到 Meta 作出决定。一旦收到电子邮件确认批准模板，需要在 Odoo " +"数据库内同步模板。" #: ../../content/applications/productivity/whatsapp.rst:796 msgid "" @@ -10400,6 +11055,9 @@ msgid "" "<https://developers.facebook.com/docs/whatsapp/business-management-" "api/message-templates/>`_." msgstr "" +"有关在 Meta 开发者控制台上配置模板的更多信息，请访问 `Meta的 WhatsApp 模板文档 " +"<https://developers.facebook.com/docs/whatsapp/business-management-" +"api/message-templates/>`_。" #: ../../content/applications/productivity/whatsapp.rst:801 msgid "Notifications" @@ -10412,6 +11070,8 @@ msgid "" "customer. By default, notifications are set in the WhatsApp business account" " configuration in Odoo." msgstr "" +"WhatsApp 中的通知处理方式与 Odoo 中的信息对话类似。会弹出一个窗口，显示收到的客户对话。默认情况下，通知设置在 Odoo 的 " +"WhatsApp 企业账户配置中。" #: ../../content/applications/productivity/whatsapp.rst:807 msgid "" @@ -10422,6 +11082,9 @@ msgid "" ":guilabel:`Notify users` heading, type in the field which user(s) should be " "notified for this particular WhatsApp channel." msgstr "" +"通知设置可通过导航至 :menuselection:`WhatsApp 应用程序 --> 配置 --> WhatsApp " +"企业帐户`进行调整。在那里，选择账户并向下滚动到处理通知的 :menuselection:`控制` 部分。在 :guilabel:`通知用户` " +"标题下，在字段中键入此特定 WhatsApp 频道应通知的用户。" #: ../../content/applications/productivity/whatsapp.rst:813 msgid "" @@ -10432,10 +11095,12 @@ msgid "" "customer's reply after the 15 days will populate once again to all the users" " specified in the WhatsApp configuration." msgstr "" +"一旦用户和客户之间开始对话，WhatsApp 企业账户配置中指定的所有用户都不会收到通知。只会向对话中的用户发出通知。如果用户在 15 " +"天内没有回复，那么在 15 天后客户的回复将再次弹出到 WhatsApp 配置中指定的所有用户。" #: ../../content/applications/productivity/whatsapp.rst:820 msgid "Adding users to chat" -msgstr "" +msgstr "将用户添加到聊天" #: ../../content/applications/productivity/whatsapp.rst:822 msgid "" @@ -10444,19 +11109,21 @@ msgid "" "the :guilabel:`👤+ (add user)` icon next to it, and a window appears to " "invite users to the conversation." msgstr "" +"用户可以通过展开 WhatsApp 弹出窗口添加到 WhatsApp 聊天中。WhatsApp 会话位于*内部沟通*应用程序中。点击旁边的 " +":guilabel:`👤+（添加用户）` 图标，就会出现一个窗口邀请用户加入对话。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" "Adding users to a WhatsApp conversation, with the add user icon highlighted." -msgstr "" +msgstr "在 WhatsApp 对话中添加用户，添加用户图标突出显示。" #: ../../content/applications/productivity/whatsapp.rst:831 msgid "WhatsApp API FAQ" -msgstr "" +msgstr "WhatsApp API 常见问题" #: ../../content/applications/productivity/whatsapp.rst:834 msgid "Verification" -msgstr "" +msgstr "验证" #: ../../content/applications/productivity/whatsapp.rst:836 msgid "" @@ -10467,6 +11134,9 @@ msgid "" "<https://developers.facebook.com/docs/development/release/business-" "verification>`_." msgstr "" +"自 2023 年 2 月 1 日起，如果 Meta 应用程序需要高级访问权限，则可能需要完成完整的企业验证。这包括向 Meta " +"提交办公业务文件。`参见此文档<https://developers.facebook.com/docs/development/release/business-" +"verification>`_。" #: ../../content/applications/productivity/whatsapp.rst:842 msgid "" @@ -10474,10 +11144,13 @@ msgid "" "<https://developers.facebook.com/docs/development/release/access-" "verification/>`_." msgstr "" +"`Meta 的 WhatsApp " +"访问验证文档<https://developers.facebook.com/docs/development/release/access-" +"verification/>`_。" #: ../../content/applications/productivity/whatsapp.rst:846 msgid "Template errors" -msgstr "" +msgstr "模板错误" #: ../../content/applications/productivity/whatsapp.rst:848 msgid "" @@ -10487,7 +11160,7 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:852 msgid "Duplicate validation error" -msgstr "" +msgstr "重复验证错误" #: ../../content/applications/productivity/whatsapp.rst:854 msgid "" @@ -10497,6 +11170,8 @@ msgid "" "duplicate template name on Odoo and sync the templates once again by " "following the steps here: :ref:`productivity/whatsapp/sync`." msgstr "" +"在同步模板时，可能会出现 Meta 企业管理平台和 Odoo 中存在多个同名模板的情况。这会导致重复验证错误。要纠正此问题，请重命名 Odoo " +"中的重复模板名称，然后按照以下步骤再次同步模板：:ref:`productivity/whatsapp/sync`。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "User error populated in Odoo when a duplicate template exists." @@ -10504,11 +11179,11 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:864 msgid "Token errors" -msgstr "" +msgstr "令牌错误" #: ../../content/applications/productivity/whatsapp.rst:867 msgid "User error" -msgstr "" +msgstr "用户错误" #: ../../content/applications/productivity/whatsapp.rst:869 msgid "" @@ -10516,6 +11191,8 @@ msgid "" "error will populate in Odoo when testing the connection after sending fails." " To correct this issues see :ref:`productivity/whatsapp/token`." msgstr "" +"如果临时令牌未替换为永久令牌，则在发送失败后测试连接时，Odoo 中将弹出用户错误。要纠正此问题，请参阅 " +":ref:`productivity/whatsapp/token`。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "User error populated in Odoo when token expires." @@ -10523,7 +11200,7 @@ msgstr "" #: ../../content/applications/productivity/whatsapp.rst:878 msgid "System user error 100" -msgstr "" +msgstr "系统用户错误 100" #: ../../content/applications/productivity/whatsapp.rst:880 msgid "" @@ -10536,6 +11213,7 @@ msgid "" "To correct this error, create an :guilabel:`Admin` system user, following " "the process outlined here: :ref:`productivity/whatsapp/token`." msgstr "" +"要纠正这一错误，请按照以下步骤创建一个 :guilabel:`管理` 系统用户：:ref:`productivity/whatsapp/token`。" #: ../../content/applications/productivity/whatsapp.rst-1 msgid "" diff --git a/locale/zh_CN/LC_MESSAGES/sales.po b/locale/zh_CN/LC_MESSAGES/sales.po index 60ebee947..5100b871a 100644 --- a/locale/zh_CN/LC_MESSAGES/sales.po +++ b/locale/zh_CN/LC_MESSAGES/sales.po @@ -6836,7 +6836,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst-1 msgid "enable tips in a POS" -msgstr "" +msgstr "在 POS 中启用小费" #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:25 msgid "Tip products" diff --git a/locale/zh_CN/LC_MESSAGES/websites.po b/locale/zh_CN/LC_MESSAGES/websites.po index 090fd7558..fcc40f713 100644 --- a/locale/zh_CN/LC_MESSAGES/websites.po +++ b/locale/zh_CN/LC_MESSAGES/websites.po @@ -5759,7 +5759,7 @@ msgstr "" #: ../../content/applications/websites/livechat/responses.rst:49 msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" -msgstr "" +msgstr ":doc:`/applications/productivity/discuss/overview/team_communication`" #: ../../content/applications/websites/livechat/responses.rst:52 msgid "Helpdesk & Helpdesk search" diff --git a/locale/zh_TW/LC_MESSAGES/general.po b/locale/zh_TW/LC_MESSAGES/general.po index b87dbc9d4..64b8a2f76 100644 --- a/locale/zh_TW/LC_MESSAGES/general.po +++ b/locale/zh_TW/LC_MESSAGES/general.po @@ -7,16 +7,16 @@ # 敬雲 林 <chingyun@yuanchih-consult.com>, 2023 # Martin Trigaux, 2023 # Wil Odoo, 2023 -# Tony Ng, 2023 +# Tony Ng, 2024 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-21 13:43+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Tony Ng, 2023\n" +"Last-Translator: Tony Ng, 2024\n" "Language-Team: Chinese (Taiwan) (https://app.transifex.com/odoo/teams/41243/zh_TW/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1275,7 +1275,7 @@ msgstr "" #: ../../content/applications/general/digest_emails.rst:95 msgid "Tickets Closed" -msgstr "" +msgstr "支援請求已關閉" #: ../../content/applications/general/digest_emails.rst:95 msgid "`kpi_helpdesk_tickets_closed_value`" @@ -5306,7 +5306,7 @@ msgstr "" #: ../../content/applications/general/users/portal.rst:20 msgid "tickets" -msgstr "" +msgstr "支援請求" #: ../../content/applications/general/users/portal.rst:21 msgid "signatures" diff --git a/locale/zh_TW/LC_MESSAGES/productivity.po b/locale/zh_TW/LC_MESSAGES/productivity.po index 519f3084a..63c09ded8 100644 --- a/locale/zh_TW/LC_MESSAGES/productivity.po +++ b/locale/zh_TW/LC_MESSAGES/productivity.po @@ -7291,7 +7291,7 @@ msgstr "" #: ../../content/applications/productivity/studio/pdf_reports.rst:20 msgid "Default layout" -msgstr "" +msgstr "預設版面設計" #: ../../content/applications/productivity/studio/pdf_reports.rst:22 msgid "" diff --git a/locale/zh_TW/LC_MESSAGES/services.po b/locale/zh_TW/LC_MESSAGES/services.po index d805793c6..76729611b 100644 --- a/locale/zh_TW/LC_MESSAGES/services.po +++ b/locale/zh_TW/LC_MESSAGES/services.po @@ -5,15 +5,16 @@ # # Translators: # Wil Odoo, 2023 +# Tony Ng, 2024 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-11-30 14:44+0000\n" +"POT-Creation-Date: 2024-01-19 15:28+0000\n" "PO-Revision-Date: 2023-11-08 08:57+0000\n" -"Last-Translator: Wil Odoo, 2023\n" +"Last-Translator: Tony Ng, 2024\n" "Language-Team: Chinese (Taiwan) (https://app.transifex.com/odoo/teams/41243/zh_TW/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -66,7 +67,7 @@ msgstr "配置" #: ../../content/applications/services/field_service/default_warehouse.rst:18 msgid "" "To set up a user default warehouse, the :doc:`storage locations " -"<../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations>`" +"</applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations>`" " feature needs to be activated in the **Inventory** app. It is also " "necessary to have more than one warehouse in your database." msgstr "" @@ -79,7 +80,7 @@ msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:27 msgid "" -":doc:`../../inventory_and_mrp/inventory/management/warehouses/warehouses_locations`" +":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`" msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:32 @@ -1296,7 +1297,7 @@ msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248 msgid "" -":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`" +":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" msgstr "" #: ../../content/applications/services/helpdesk/overview.rst:5 @@ -1906,7 +1907,7 @@ msgstr "" #: ../../content/applications/services/helpdesk/overview/help_center.rst:177 msgid "Community Forum" -msgstr "" +msgstr "社群討論區" #: ../../content/applications/services/helpdesk/overview/help_center.rst:179 msgid "" @@ -2949,7 +2950,7 @@ msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:16 msgid "Ticket Analysis" -msgstr "" +msgstr "支援請求分析" #: ../../content/applications/services/helpdesk/overview/reports.rst:18 msgid "" @@ -3048,7 +3049,7 @@ msgstr "" #: ../../content/applications/services/helpdesk/overview/reports.rst:63 msgid "SLA Status Analysis" -msgstr "" +msgstr "SLA狀態分析" #: ../../content/applications/services/helpdesk/overview/reports.rst:65 msgid "" @@ -3787,9 +3788,8 @@ msgstr "" #: ../../content/applications/services/project/project_management.rst:58 msgid "" -"`Odoo Tutorials: Customize your project " -"<https://www.odoo.com/slides/slide/customize-your-" -"project-1662?fullscreen=1>`_" +"`Odoo Tutorials: Customize projects " +"<https://www.odoo.com/slides/slide/customize-projects-3615?fullscreen=1>`_" msgstr "" #: ../../content/applications/services/project/project_management.rst:61